In a warm failover setup, an Active IP Availability Manager, IP Availability and Performance Manager or IP Performance Manager run on the Active host, and a Standby IP Availability Manager, IP Availability and Performance Manager or IP Performance Manager run on the Standby host. Preference is given to Location A for the Active IP Manager if no IP Manager is registered with the Broker. If any IP Manager is already registered with the Broker, that IP Manager is marked as Active.
Both Active and Standby IP Managers can poll the network. Failover occurs when the Active Domain Manager fails and the Standby Domain Manager becomes the Active Domain Manager with its current loaded topology (RPS). The monitoring process will be enabled in the newly-promoted Active Domain Manager, and it will start polling the devices. Only the Active Domain Manager actively polls the network. Failover Manager disables polling in the Standby IP Manager. The Standby Domain Manager only synchronizes network topology with the Active Domain Manager.
When the failed Domain Manager starts up, it becomes the Standby Domain Manager. Then, the backup actions happen from current Active Domain Manager to the current Standby Domain Manager.
The Configuration Manager itself does not participate in failover and, as a result, has only one instance. “Troubleshooting IP Configuration Manager when the Tomcat service fails over” on page 69 describes the affect of service failover if you are using the Configuration Manager in the VMware M&R UI to control discovery configuration settings. The Configuration Manager service must be installed to be registered with both primary EDAA and secondary EDAA.
