6
Configuring the System for Failover
This chapter explains how to enable the software for a failover using two System Directors.
n
For true redundancy it is recommended that you connect the second System Director to a
different engine than the first System Director. The Active and the Standby System Directors must
be the same model server, you cannot mix SR2400s, SR2500s, and AS3000 servers.
n
This feature requires an Application Key or software licensing software be installed on both the
Active and Standby System Directors.
System Director Failover
When using two System Directors, one is referred to as Active System Director and the other one
is the Standby System Director. The File System on the Standby System Director is kept
up-to-date with the Active System Director. There might be a brief interruption in client
connectivity but all clients re-connect automatically when the Standby System Director becomes
active. In an attempt to keep the procedure easy to use, we use the following nomenclature:
•
When adding a new System Director to an existing Avid ISIS system or creating a failover
system configuration, the original System Director is called the existing System Director and
the new System Director is called new.
•
When installing two new System Directors to create a failover system configuration, one
System Director is called Active and the other Standby.
Each System Director must connect to right and left sides of the engine to allow both of the
System Directors to reach the two internal subnets. Connect the two System Directions under the
following conditions:
•
After you have physically configured the system and loaded the Avid ISIS software on both
System Directors.
•
When the System Director service is stopped on both systems.
•
Connect the Ethernet port of the Active System Director to connection 1 on the left side of
the engine (from the rear). Connect the Ethernet port of the Standby System Director to
connection 1 on the right side of the engine (from the rear).
