Other Topic Library Versions

Triggering an intentional failover

DANGER
Do not attempt this procedure except under the supervision of qualified Grass Valley personnel.

The following procedure renders the primary K2 Media Server unqualified to carry out its role in managing the K2 SAN. The backup K2 Media Server detects this condition and triggers a failover in which it takes the primary server out of service and takes control of the K2 SAN. Therefore, before using these procedures, verify that the backup K2 Media Server is fully operational and qualified to take control of the K2 SAN. Be aware that the failover capabilities of the -K2 SAN are degraded until you place the machine back into service as the backup K2 Media Server.

You should stop all media access before attempting this procedure. If media access is underway, there will be period of time in which media loss will occur.

In the following procedures, K2server1 and K2server2 represent your redundant K2 Media Servers. The procedure begins with K2server1 acting as the primary K2 Media Server.

  1. Verify primary/backup roles and make sure K2server2 (the backup) is qualified and ready to become primary.
  2. From the K2Config application, open Server Control Panel.
  3. In Server Control Panel for K2server1 click Stop. This triggers the failover process. K2server1 shuts down. K2server2 detects (via the absence of the heartbeat signal on the serial cable) that K2server1 is gone, so K2server2 takes over as primary.
  4. Allow the failover process to complete, until K2server2 is operating correctly in its new role as the primary K2 Media Server for the K2 SAN.
  5. Verify K2server2 as primary.
  6. Start up K2server1. It is now out of service. If you need to do service work on K2server1, you can do it now. After your work is complete, proceed with the next step.
  7. If there are K2 Media Servers with role of iSCSI bridge or Fibre Channel switches on the same redundant “side” as K2server1, start or restart them.
  8. In Server Control Panel, for K2server1, click Start. This notifies K2server2 (via a heartbeat signal on the serial cable) that K2server1 is coming online as backup.
  9. Verify K2server1 as backup.
  10. All failover processes are complete. All media management mechanisms are now running and K2server1 is now qualified and acting as the backup.

Copyright © 2015 Grass Valley USA, LLC. All rights reserved. K2 Summit 9.4 gvtp_20150218_00:14:46