Other Topic Library Versions

Replacing a K2 Media Server

The requirements for replacing a K2 Media Server on an existing K2 SAN are as follows:

  • You must be logged in to the K2Config application with permissions equivalent to K2 administrator or higher.

Use this procedure if a K2 Media Server in a working system is faulty or otherwise needs to be replaced with a new K2 Media Server.

Note: If you are replacing a non-redundant media file system/metadata server, you lose all media during the replacement process.
  1. If the server hosts an iSCSI interface adapter, copy down iSCSI bandwidth settings for K2 clients and other iSCSI clients that use the faulty server as their iSCSI target, as follows:
    1. In the K2Config application, select the K2 SAN in the tree view and then click the button in the toolbar to view client iSCSI assignments. A page opens that displays each client’s primary and secondary iSCSI targets.
    2. In the tree view, select one of the clients that have the faulty server as a primary or secondary iSCSI target.
    3. Open the client’s iSCSI Initiator Configuration page and click Modify. The Bandwidth Input dialog box opens.
    4. Copy down the bandwidth settings configured for that client and then close the Bandwidth Input dialog box.
    5. Repeat these steps for each client that has the faulty server as a primary or secondary iSCSI target.
  2. If the server hosts an iSCSI interface adapter, in the K2 System Configuration application, for the faulty K2 Media Server, open the iSCSI bridge page and make a note of the IP addresses.
  3. Copy down network and hostname settings for the faulty K2 Media Server. You can do this from SiteConfig or from the K2Config application Network Configuration page.
  4. Save a copy of the host table from the faulty K2 Media Server. You can use SiteConfig hosts file features or you can find the host table at the following location on the K2 Media Server: C:\WINDOWS\system32\drivers\etc\hosts
  5. If the server hosts an iSCSI interface adapter, in the K2Config application, remove the K2 clients and other iSCSI clients that use the faulty server as their iSCSI target, as determined earlier in this procedure.
  6. Stop all media access and power down all K2 clients and other iSCSI clients.
  7. If the faulty server is a media file system/metadata server, take the K2 Media Server out of service. If it is a redundant server, it must be the backup before you take it out of service.
  8. In the K2Config application, remove the faulty K2 Media Server as follows:
    1. In the tree view, select the K2 Media Server
    2. Click Remove and Yes to confirm. The K2 Media Server is removed from the tree view.
  9. In SiteConfig, remove the K2 Media Server.
  10. Physically remove the faulty K2 Media Server and put the replacement server in its place. Reconnect all cables to the replacement server as they were to the faulty server.

    Note: If the replacement server was previously configured on a K2 SAN, you must restart it before adding it to a K2 SAN or in any other way reconfiguring it for use.
  11. In SiteConfig, add, discover, and assign the replacement server. Configure the hostname and all network settings on the replacement server to be the same as they were on the faulty server.
  12. Copy the host table onto the replacement server. You can use SiteConfig for this task.
  13. In the K2Config application, add and configure the replacement server. Refer to the installation chapter for the level of your system earlier in this manual for specific procedures, with the following special instructions:
    1. Add the server to the K2 SAN, using the Add Device button.
    2. Configure the replacement server so that its settings are all the same as they were on the faulty server.
      • On the Define Server Roles page, assign the same roles.
      • On the Network Configuration page, verify the same network settings for the FTP network.
      • If the server hosts an iSCSI interface adapter, on the iSCSI Bridge Server Configuration page, verify the same settings.
    3. After completing the configuration, restart the machine to put changes into effect.
  14. If the server hosts an iSCSI interface adapter, in the K2 System Configuration application, add the clients that you removed in step 5 earlier in this procedure, with the following special instructions:
    1. Add the client with the highest iSCSI bandwidth first.
    2. On each client, configure iSCSI bandwidth settings so they are the same as they were before.
  15. Power up all K2 clients and other iSCSI clients and test media access.

The replacing a server procedure is complete.


Copyright © 2016 Grass Valley Canada. All rights reserved. K2 Summit 9.6 gvtp_20160520_13:06:36