300-430 Question 176
Single answerAn enterprise has deployed Cisco CMX in a high-availability (HA) configuration to ensure location services are always available. However, clients report inconsistent location tracking after a failover occurs. Upon investigation, you notice that the CMX services do not synchronize properly between the primary and secondary nodes. What is the most likely cause of this issue?
- A
The primary and secondary CMX nodes are running different software versions.
- B
The CMX nodes are not configured with the same NTP server.
- C
The wireless controllers are not configured to send location data to the secondary CMX node.
- D
The CMX HA configuration requires a manual synchronization of historical data between nodes.
Show answer and explanation
Correct answer: B
Explanation
In a Cisco CMX high-availability setup, both nodes must be synchronized with the same NTP server to ensure proper communication and data consistency. Time discrepancies can result in failures during failover, causing inconsistent location tracking. This is a critical prerequisite for successful CMX HA functionality.
- A. Incorrect.
If the primary and secondary CMX nodes are running different software versions, it can cause compatibility issues, but it would not specifically lead to synchronization problems after failover. Both nodes should be at the same software level, but this scenario points to a time sync issue.
- B. Correct.
CMX nodes rely on accurate time synchronization using NTP for HA functionality to work properly. If the nodes are not using the same NTP server, time discrepancies can cause synchronization failures, leading to inconsistent behavior after failover.
- C. Incorrect.
While wireless controllers need to send location data to CMX nodes, this configuration is typically already in place prior to enabling HA. This is not the root cause of the synchronization issue described.
- D. Incorrect.
CMX does not require manual synchronization of historical data for HA to function. Synchronization of data between nodes happens automatically when HA is correctly configured, assuming all prerequisites are met.