300-430 Question 178
Select 4A network administrator has deployed Cisco CMX in a high-availability (HA) setup. After a power outage, the primary CMX server failed to come back online, and the secondary server did not take over as expected. Which of the following troubleshooting steps would help identify and resolve the issue?
- A
Verify that the primary and secondary CMX servers have synchronized their databases.
- B
Check whether the secondary CMX server is properly configured with the virtual IP (VIP) address.
- C
Ensure that both CMX servers are running the same software version and patch level.
- D
Inspect the HA settings to confirm that failover monitoring is enabled.
- E
Reboot the network devices providing connectivity to the CMX servers.
Show answer and explanation
Correct answers: A, B, C, D
Explanation
In a Cisco CMX HA setup, the secondary server is designed to take over when the primary fails. For this to occur, the servers must have synchronized databases, the same software version, and correctly configured virtual IP settings. Additionally, failover monitoring must be enabled to detect failures. Troubleshooting these aspects will help identify and resolve the issue, whereas rebooting network devices is not a primary step in resolving CMX HA problems.
- A. Correct.
Database synchronization is critical for proper CMX HA operation. If the databases are not synchronized, the failover process might fail or cause data integrity issues.
- B. Correct.
The secondary CMX server must be correctly configured with the virtual IP (VIP) address for it to assume the primary role during a failover event.
- C. Correct.
Both CMX servers must be running the same software version and patch level to ensure compatibility and seamless HA operation.
- D. Correct.
Failover monitoring must be enabled in the HA settings to detect when the primary server goes offline. If this setting is disabled, the failover process will not be triggered.
- E. Incorrect.
Rebooting network devices is unlikely to address the issue unless there is a specific connectivity problem. This step is not directly related to CMX HA troubleshooting.