A network administrator just completed the basic implementation of Cisco CMX and tries to implement location tracking. The administrator is having trouble establishing connectivity between one of the

Permanent licenses on the CMX server govern feature entitlement and device capacity but have no bearing on whether the NMSP transport-layer session can be established between CMX and the WLC.

NMSP uses TCP port 16113 for all communication between the CMX server and the WLC. If a firewall or ACL blocks this port between the two devices, the NMSP session cannot be initiated or sustained regardless of other configuration. The firewall policy must explicitly permit TCP 16113 bidirectionally between CMX and the WLC.

NMSP is disabled by default on Cisco WLC and must be manually activated under the Management configuration section of the controller. Without enabling NMSP on the WLC, the controller will not respond to NMSP connection attempts from CMX even if port 16113 is open on the firewall. Enabling NMSP is a mandatory prerequisite for any CMX location or analytics functionality.

Rebooting CMX after adding a WLC is not required; the NMSP connection is negotiated dynamically once the correct port access and WLC configuration are in place.

Providing the CMX server MAC address and SSC key on the WLC is not a standard requirement for NMSP connectivity in current CMX deployments; WLC-CMX trust is established through IP address and shared secret configuration, not MAC or SSC entries.