Automatic Failover switch to Secondary MC when the Primary MC is unresponsive

Products

• Management Center

Issue/Introduction

• When the Primary MC is shut down, Failover is automatically disabled on the Secondary MC by the system.
• When powering powering back on the Primary MC, the following error is seen:
  
  • ERROR: Host at xx.x.xxx.xx (secondary) is not reachable
• Once logging into the Secondary MC, ran command “failover view” and receive the following message:
  
  • Status: disabled automated on xxx-xx-xx xx:xx:xx by system

Environment

Configure Automatic Failover with a Virtual IP Address on the Primary and Secondary Management Center server 

Resolution

By design, the Primary system will drop out of Failover sync due to the communication failure between the Primary and Secondary systems.  The Secondary system becomes active once the Primary system is no longer in a Failover state.

In a Failover scenario, if the main system fails, it should no longer be accessible, and the Failover configuration is expected to be disrupted. 

After recovering the failed system, the next step is to reconfigure Failover. You have the option to choose the first system or the previous Secondary system as the Primary system in the event of Failover by following the same steps to enable Failover.