Why Client Devices Fail to be Displayed on Cisco WCS Floor Maps

AC.

When a client device fails to be displayed on a Cisco WCS (Wireless Control System) floor map, there can be several reasons for it. Let's take a look at the two statements that are true in this case:

A. NMSP communication has failed between the Cisco MSE and Cisco WCS: The Cisco MSE (Mobility Services Engine) is responsible for providing context-aware services such as location tracking and analytics. The Cisco WCS communicates with the Cisco MSE over the NMSP (Network Mobility Services Protocol) to obtain information about client devices and their location. If there is a failure in the NMSP communication between the Cisco MSE and Cisco WCS, client devices will not be displayed on the floor map.

B. Filtering parameters have not been configured for the context-aware service: The context-aware service provided by the Cisco MSE uses a set of filtering parameters to identify and track client devices. If these parameters are not configured correctly, client devices may not be displayed on the floor map. For example, if the MAC address of a client device is not included in the filter, the device will not be displayed on the map.

C. Network designs and controllers have not been assigned to the Cisco MSE: This statement is false, as it does not relate to the issue of client devices not being displayed on the floor map.

D. LOCP communication has failed between the Cisco MSE and Cisco WCS: The LOCP (Location Context Protocol) is another protocol used by the Cisco MSE and Cisco WCS to exchange information about client devices and their location. However, this protocol is not used for displaying client devices on the floor map. Therefore, this statement is also false.

In summary, the two statements that are true about why client devices fail to be displayed on a Cisco WCS floor map are:

• NMSP communication has failed between the Cisco MSE and Cisco WCS.
• Filtering parameters have not been configured for the context-aware service.