Recovering from network isolation

Last Updated : May 14, 2015 |

About this task

Media servers might become network isolated for the following reasons:

  • Network switch failure or misconfiguration

  • Network interface card (NIC) failure

  • Network cables damaged or removed

When servers that are part of a 1+1 High Availability cluster are isolated from the network, they cannot communicate with each other. Both servers then enter the active High Availability state. However, only one of the servers is actually processing sessions.

To prevent loss of user sessions when the server is recovering from a network isolation condition, you must lock the High Availability state on the server that you determine is active and processing the sessions.

After the network isolation issue is resolved and both servers are back on the network, unlock the High Availability state in both servers to provide failover redundancy.

Use this procedure to recover High Availability servers from network isolation.

Procedure

  1. Gain access to the server with the active sessions and navigate to EM > Cluster Configuration > High Availability.

    The server with active sessions is usually the only one you can access.

  2. Lock the High Availability state of the server processing the sessions by selecting Local High Availability State Lock.
  3. Perform the necessary hardware or network changes to recover the peer server from network isolation.
  4. Unlock the High Availability state of the server processing the sessions by unselecting Local High Availability State Lock.
  5. Click Save.
  6. Click Confirm.