-perdida de conectividad entre los site por enlace WAN
-el servidor activo esta demasiado ocupado para responder las peticiones de heartbeat
-mala configuracion de heartbeat en alguno o ambos de los extremos.
Os dejo una guía para solucionarlo en caso de que se produzca:
Primero identificaremos cual es el vCenter con mas datos actualizados:
1 Check the date and time of files on both servers. Make the most up-to-date server the active server.
2 From a client PC on a LAN, run nbtstat -A 192.168.1.1 where the IP address is the Principal (Public) IP address of the server. This can help identify the MAC address of the server currently visible to client machines.
Después, seguiremos estos pasos para restablecer el activo-pasivo:
1 Identify the server with the most up-to-date data or the server to make active.
2 Shut down vCenter Server Heartbeat on both servers (if running).
3 On the server to make passive, right-click the Task bar icon, and select the Server Configuration wizard.
4 Click the Machine tab and set the server role to passive. Do not change the identity of the server (Primary
or Secondary).
5 Click Finish.
6 Restart this server.
7 Start vCenter Server Heartbeat, if required, and check that the Task bar icon now reflects the changes by
showing P / - (Primary and Passive) or S / - (Secondary and Passive).
8 On the active server, right-click the Task bar icon and select the Server Configuration wizard.
9 Click the Machine tab and verify that the server role is set to active. Do not change the identity of the
server (Primary or Secondary).
10 Click Finish.
11 Restart this server. As the server restarts, it connects to the passive server and starts replication. The active server overwrites data on the passive server.
12 Start vCenter Server Heartbeat, if required, and check that the Task bar icon now reflects the changes by showing P / A (Primary and active) or S / A (Secondary and active).
13 Start vCenter Server Heartbeat Console.
14 Check that the servers have connected and replication has started.
