During a disaster recovery test, the Secondary Citrix ADC is not taking over as Primary. What could be a likely cause related to networking?

During a disaster recovery test, the Secondary Citrix ADC is not taking over as Primary. What could be a likely cause related to networking?

• A. HA monitoring is enabled on a disabled interface of the Primary Node.
• B. The Independent network configuration (INC) mode is enabled on the Primary Node.
• C. HA heartbeats are only seen on some enabled interfaces of the Secondary Node.
• D. HA monitoring is enabled on an interface of the Secondary Node that shows as ENABLED, DOWN.

Answer: (D)

In Citrix ADC high availability, failover depends on a reliable HA heartbeat path between the primary and secondary. If the Secondary has an interface configured for HA monitoring that is currently ENABLED but DOWN, that heartbeat channel is effectively broken on the Secondary side. Without a functioning heartbeat on its monitoring interface, the Secondary cannot reliably detect the Primary’s failure or promote itself, so it won’t take over as Primary during a disaster recovery test. The fix is to bring that interface up (administratively and physically) or reconfigure HA monitoring to use an interface that is up and reachable between the nodes. Other options would either not directly block the failover path or indicate partial connectivity, which is less definitive than a down monitoring interface on the Secondary.

In Citrix ADC high availability, failover depends on a reliable HA heartbeat path between the primary and secondary. If the Secondary has an interface configured for HA monitoring that is currently ENABLED but DOWN, that heartbeat channel is effectively broken on the Secondary side. Without a functioning heartbeat on its monitoring interface, the Secondary cannot reliably detect the Primary’s failure or promote itself, so it won’t take over as Primary during a disaster recovery test. The fix is to bring that interface up (administratively and physically) or reconfigure HA monitoring to use an interface that is up and reachable between the nodes. Other options would either not directly block the failover path or indicate partial connectivity, which is less definitive than a down monitoring interface on the Secondary.