Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
Search instead for
Did you mean:
Cisco Mobility Services Engine (MSE) unable to discover clients and rogues
In CAS infrastructure, Cisco Mobility Services Engine (MSE) is unable to track clients and rogues but able to track the tags. MSE Partner Engine is running and Tags are positioned in maps with both permanent licenses and demo license.
Prime Infrastructure: 188.8.131.52
Wireless clients are not counted while tags are counted. However, there are active clients in the page below but they do not show up in the map screen.
On PI, under mobility service engine ->context aware services, the following screen is shown which indicates that clients are tracked:
Under mobility service engine-> General, the following screen is shown: the client should be tracked even if the Cisco CAS engine shows status down.
MSE is already added to the floor plan map and synced:
Reinstall MSE application on server didn't help.
The MSE is a Virtual Machine.
Below is the output from mse status:
Context Aware Service
Total Active Elements(Wireless Clients, Tags, Rogue APs, Rogue Clients, Interferers, Wir
ed Clients): 27
Active Wireless Clients: 0
Active Tags: 27
Active Rogue APs: 0
Active Rogue Clients: 0
Active Interferers: 0
Active Wired Clients: 0
Active Elements(Wireless Clients, Rogue APs, Rogue Clients, Interferers, Wired Clients)
Active Tag Limit: 100
Active Sessions: 1
Wireless Clients Not Tracked due to the limiting: 0
Tags Not Tracked due to the limiting: 0
Rogue APs Not Tracked due to the limiting: 0
Rogue Clients Not Tracked due to the limiting: 0
Interferers Not Tracked due to the limiting: 0
Wired Clients Not Tracked due to the limiting: 0
Total Elements(Wireless Clients, Rogue APs, Rogue Clients, Interferers, Wired Clients) N
ot Tracked due to the limiting: 0
Context Aware Sub Services
Subservice Name: Aeroscout Tag Engine
Admin Status: Enabled
Operation Status: Up
Subservice Name: Cisco Tag Engine
Admin Status: Disabled
Operation Status: Down
So the heatmap key created is: 84:78:ac:f0:84:b0-2.4-1 but the one asked for is: 84:78:ac:f0:84:b0-5.0-0
The problem seems to be an incompatibility (read a bug) in the MSE that does not handle RSSI measurements coming from single band Access Points (2.4 GHz). When we received a dual band Access Point from Cisco, things started to work as expected. This behavior is consistent with the logs displayed further up in this post.