The Cisco MSE (Mobility Service Engine) provides two master services

1. Context Aware Services (CAS)
Ability to rails the physical location of Network Devices, both wired and wireless, using wireless LAN controllers (WLCs) and Cisco Aironet Lightweight Admission Points (LAPs). This solution allows a client to runway any Wi-Fi device, including clients, agile RFID tags, and rogue clients and access points (APs).

2. Adaptive Wireless Intrusion Prevention System (wIPS)
wIPS software provides visibility and comprehensive threat prevention for the mobility network through monitoring, alerts, classifying, and remediation of wireless and wired network vulnerabilities

Below diagram shows the typical interaction between MSE , WLC & WCS.MSE-WCS-WLC-02

Advice among the system components involves the following protocols:
1. Control and Provisioning of Wireless Access Points (CAPWAP)—This protocol is the successor to LWAPP and is used for communication betwixt access points and controllers.
ii. Network Mobility Services Protocol (NMSP)—The protocol handles advice between controllers and the mobility services engine. In a wIPS deployment, this protocol provides a pathway for alarm information to be aggregated from controllers and forwarded to the mobility services engine and for wIPS configuration information to be pushed to the controller. This protocol is encrypted.
–Controller TCP Port: 16113
3. Simple Object Access Protocol (SOAP/XML)—The method of advice between the mobility services engine and WCS. This protocol is used to distribute configuration parameters to the wIPS service running on the mobility services engine.
–MSE TCP Port: 443
4. Simple Network Management Protocol (SNMP)—This protocol is used to forward wIPS alarm information from the mobility services engine to the WCS. It is also employed to communicate rogue admission point information from the controller to WCS.

Full listing of protocol/port used for MSE-WLC-WCS can be found from below link (Cisco Document ID 113344)
Cisco Unified Wireless Network Protocol and Port Matrix

Here are some settings of Context Aware Service (CAS) deployment.

Following shows the historical information you tin keep within MSE. You accept to configure which parameters you need to record & how long that data to be kept.MSE-WCS-WLC-03

in WCS nether "Services-> Mobility Services -> Context Aware Services->Location Parameters", you can change location specific information. An chemical element is declared "inactive" if it is remain inactive for 1 hour.If it remain inactive for 24 hours (Absent Data Cleanup Interval) information technology is removed from the tracking table. But element's history will be in MSE for 30 days by default.MSE-WCS-WLC-04

The RSSI Cutoff is an important field that can be tuned for a particular environment. This field specifies the minimum RSSI value below which the MSE ignores when it calculates the location for a given element. This value is simply applicable to track clients, that is, it does not use to tag tracking.

If you specify a very high RSSI Cutoff, such equally -lx or -50 with low AP density, information technology leads to poor location calculation since the MSE excludes RSSI values of reliable hearing APs from its calculation.

If you use a depression RSSI Cutoff, such as -85 of -90 and operate in an open up infinite surface area or with low walls, inter-floor attenuation areas pb to poor location calculation because the MSE includes RSSI values from outlying APs in its calculation.

Yous tin change Tracking Parameter values as shown in the value.MSE-WCS-WLC-05

If you lot want to configure notifications to send to 3rd party system (Northbound Notifications) you can do this under Notification Parameters in Advanced Settings of CAS.MSE-WCS-WLC-06

Here are few reference guides I found useful when configuring  MSE. Please feel free to read it & understand different settings on this platform.

1. Cisco Mobility Services Engine – Context Aware Mobility Solution Deployment Guide

2. Cisco Adaptive Wireless Intrusion Prevention System Configuration Guide Release vii.0

three. Cisco Context-Aware Service Configuration Guide Release 7.0

Related Posts

1. Wired Client Tracking in MSE
2.