Grass Valley iControl V.4.43 - Manual (Page 599)

iControl
User Guide
589
• If you would like your Backup to take on the IP address of your Main, make sure that all
Application Servers are in the same subnet.
• It is important that the Broadcast IP address is configured correctly, since this is used by
the heartbeat mechanism.
• It is important that you activate both eth0 and eth1 at start-up and that they are both
operational. A Redundancy Group assumes two working network interfaces.
• It is important that the Main network is over the eth0 interface.
• It is important the Heartbeat network is over the eth1 interface.
• In order for redundancy to be fully functional, ONE of the following conditions must be
true:
• ALL the Application Servers within the Redundancy Group have iControl version 4.10
or later installed.
• ALL the Application Servers within the Redundancy Group have versions of software
earlier (and not including) iControl version 4.10 installed.
One implication of this is that when upgrading an Application Server to version 4.10 or
higher, you must similarly upgrade ALL Application Servers within the Redundancy Group
in order to ensure redundancy is fully functional.
Configuring and Managing a Redundancy Group
IMPORTANT: Dell PowerEdge R200, R210, and R310 Port Labels
If your Application Server is a Dell PowerEdge R200, R210, or R310, please
read the section regarding Ethernet port labels (see
"Ethernet Port Labeling
on the R210 and R310 Application Servers" , on page 53).
REQUIREMENTS
Make sure you meet the following conditions before beginning this procedure:
• Upon failover or takeover, if you would like your Backup to take over the IP address of the
Main Application Server, then all Application Servers you would like to assign to a
Redundancy Group are on the same subnet.
• None of your Application Servers currently belong to a Redundancy Group.
• Each Application Server’s eth0 and eth1 interfaces are connected.
• All eth1 interfaces are connected together on the Heartbeat network (and can
successfully ping other eth1 IP addresses).
• All eth0 interfaces are connected together on the Main network (and can successfully
ping other eth0 IP addresses).
• Your network is properly configured on both eth0 and eth1, specifically:
• Make sure the Broadcast IP (used by the Heartbeat mechanism) is correct
• Make sure both eth0 and eth1 are activated on boot.
• Make sure the Backup Application Server has enough hard drive space left to
replicate the Main Application Servers.