300-430 · Question #217
A wireless administrator receives this information to complete a CMX deployment in high availability by using version 10.6 to gather analytics. - IP address of the primary server - IP address of the s
The correct answer is A. Insert the cmxadmin password of the secondary server.. CMX 10.6 HA configuration requires the cmxadmin application-level password of the secondary server, not the Linux root password; using the root password causes the HA pairing authentication to fail.
Question
A wireless administrator receives this information to complete a CMX deployment in high availability by using version 10.6 to gather analytics.
- IP address of the primary server
- IP address of the secondary server
- failover mode to be configured as automatic
- root password of the secondary server
- email ID for NOC notifications
Enabling high availability fails when these parameters are used. Which action resolves the issue?
Options
- AInsert the cmxadmin password of the secondary server.
- BUse IP protocol 4242 for the controller to reach the CMX server.
- CPlace primary and secondary servers in different subnets.
- DEnable the virtual IP address of the primary server.
How the community answered
(53 responses)- A70% (37)
- B4% (2)
- C9% (5)
- D17% (9)
Why each option
CMX 10.6 HA configuration requires the cmxadmin application-level password of the secondary server, not the Linux root password; using the root password causes the HA pairing authentication to fail.
The CMX HA setup process authenticates to the secondary server using the cmxadmin account, which is the dedicated application-level administrative user, rather than the OS-level root account. When the root password is supplied instead of the cmxadmin password, authentication against the secondary node fails and the HA pairing process cannot complete. Correcting the credential to the cmxadmin password resolves the failure.
There is no IP protocol 4242 requirement in CMX; WLC-to-CMX communication uses NMSP over TCP port 16113, and protocol 4242 has no relevance to CMX HA configuration or controller connectivity.
CMX HA is designed to operate with primary and secondary servers sharing a virtual IP on the same subnet; placing them in different subnets is not required and would complicate virtual IP failover rather than enable it.
The virtual IP address serves as the client-facing service endpoint after HA is active and is not a prerequisite that must be configured before the HA pairing process can succeed; the immediate cause of failure here is the incorrect password type.
Concept tested: CMX high availability setup - required cmxadmin credential
Source: https://www.cisco.com/c/en/us/td/docs/wireless/mse/10-6/cmx_config/b_cmx_configuration_guide_10_6/high_availability.html
Topics
Community Discussion
No community discussion yet for this question.