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

iControl
User Guide
591
4. If you would like to reconfigure the configured Main Application Server in a Backup role,
see "Reconfiguring an Offline, Configured Main Application Server in a Backup Role" , on
page 609.
5. If you would like to replace a failed Main Application Server, see "Replacing an Application
Server in a Redundancy Group" , on page 615.
Troubleshooting an Auto-failover or Manual Takeover Operation
Scenario 1
If an Auto-failover or Manual Takeover event occurs when there is no Extra IP configured, the
Main Application Server assumes the factory default IP (
10.0.3.6 ). If the factory default is not
on the same subnet as the Application Servers in your Redundancy Group, you will not be able
to access this Application Server through the network.
To troubleshoot Scenario 1
Recovering from the failover or takeover requires a direct connection with a crossover cable
from the configured Backup to your laptop.
Creating a Redundancy Group
You can create a Redundancy Group either by starting with a Main Application Server or a
Backup Application Server.
Creating a Redundancy Group with a First Application Server in the Role of Main
IMPORTANT: Miranda recommends you configure an Extra IP in your Redundancy Group
To ensure the situation of this scenario does not occur in the future, Miranda
recommends you configure an Extra IP (within the same subnet as the other
Application Servers) for your Redundancy Group.
REQUIREMENTS
Make sure you meet the following conditions before beginning this procedure:
• You have opened iControl for one of the Application Servers you would like to add to the
Redundancy Group (see page 696 ).
• If you are creating the Redundancy Group using an Application Server whose intended
role is Backup, you have already stopped all iControl services on this Application Server
(see
"Stopping iControl Services on the Intended Backup Application Server" , on
page 604).
• You have navigated to the Redundancy Configuration Form for the Application Server
mentioned in the requirement before this one (see page 712 ).
• Cabling for eth0 and eth1 interfaces is properly connected.
• Network settings for eth0 and eth1 have been properly configured on each Application
Server you would like to add to the Redundancy Group (e.g. IP broadcast, Netmask,
IP address, Host name).