A new MSE with wIPS service has been installed and no alarm information appears to be reaching the MSE from controllers. Which protocol must be allowed to reach the MSE from the controllers?

The Network Mobility Services Protocol (NMSP) is a Cisco-proprietary protocol that facilitates communication between a Cisco Wireless LAN Controller (WLC) and a Cisco Mobility Services Engine (MSE). This protocol is essential for the MSE to receive data for services such as wIPS (Wireless Intrusion Prevention System) and Context-Aware Services (CMX). The WLC collects security event information from its managed access points and forwards this data, including wIPS alarms and rogue device information, to the MSE over an NMSP connection. If this protocol is blocked by a firewall or an access control list, the MSE will not receive any alarm data.

A. SOAP/XML: This is a messaging protocol used for API integrations, often with management platforms like Cisco Prime Infrastructure, not for the primary, real-time wIPS data stream between a WLC and MSE.
C. CAPWAP: The Control and Provisioning of Wireless Access Points protocol is used for communication between access points and the WLC, not between the WLC and the MSE.
D. SNMP: While WLCs can send SNMP traps for general network monitoring, NMSP is the specific, stateful protocol required for the continuous exchange of detailed information needed by the wIPS service on the MSE.

1. Cisco Wireless LAN Controller Configuration Guide, Release 8.10, "Mobility Services Engine" Chapter: "The controller communicates with the mobility services engine using the Network Mobility Services Protocol (NMSP)." It further specifies, "The controller and mobility services engine must be able to reach each other through the network. For this reason, you must ensure that any firewalls or access control lists between them are configured to allow NMSP traffic."

2. Enterprise Mobility 8.5 Design Guide, "Cisco MSE and Cisco CMX Design" Chapter: "The communication between the Cisco WLC and the Cisco MSE is based on the Cisco proprietary Network Mobility Services Protocol (NMSP). The Cisco WLC acts as a proxy for the information sent by the APs and forwards it to the Cisco MSE using the NMSP protocol."

3. Cisco Connected Mobile Experiences (CMX) Configuration Guide, Release 10.6, "Adding Controllers" Section: "The Network Mobility Services Protocol (NMSP) is used for communication between Cisco WLC and Cisco CMX. The NMSP connection must be enabled on the Cisco WLC before adding it to Cisco CMX." (Note: CMX is the evolution of MSE services, and the underlying protocol remains NMSP).