04-05-2013 08:39 AM - edited 07-03-2021 11:51 PM
Hello.
I have a problem with MSE tracking client in my network.
What we have:
PI 1.3 with evaluation license (temporary)
MSE 7.4.100 with 3k device licenses (hardware appliance 3355)
WLC 5508 7.4.100
For now MSE is reacheble from PI and WLC, all setings are synchronized, NMSP status is active, mse assigned for maps and synchronized, on map we have 3 APs, but in Contex Aware tab we didnt see any tracking devices, all counts 0.
Any suggestions why it can be ?
Thank you very much.
Solved! Go to Solution.
08-30-2013 09:24 PM
MSE not discovering Clients with CISCO SINGLE BAND AP
Description
Symptom:
MSE discovery is not working with Single Band AP
Conditions:
Single Band AP
Workaround:
change Single band AP with Dual Band
This issue is captured in the following document:
Cisco Mobility Services Engine (MSE) unable to discover clients and rogues
Regards,
Vinay Sharma
Community Manager
04-05-2013 09:00 AM
Can you console into the MSE and post the: /etc/init.d/msed status
Thanks,
Scott
Help out other by using the rating system and marking answered questions as "Answered"
04-05-2013 09:06 AM
Yes, only in monday, but as i remember all status is fine.
04-05-2013 09:12 AM
You have the Context Aware status enabled on PI? If so, try removing it and enabling it back.
Thanks,
Scott
Help out other by using the rating system and marking answered questions as "Answered"
04-05-2013 09:17 AM
i will try
04-08-2013 04:25 AM
Hello.
Nothing can help: re-enable, restart, remove.
Here status
]0;root@mse:~ [root@mse ~]# /etc/init.d/msed status
STATUS:
Health Monitor is running
Starting MSE Platform, Waiting to check the status.
MSE services are up, getting the status
-------------
Server Config
-------------
Product name: Cisco Mobility Service Engine
Version: 7.4.100.0
Health Monitor Ip Address: 1.1.1.1
High Availability Role: 1
Hw Version: V01
Hw Product Identifier: AIR-MSE-3355-K9
Use HTTP: false
Legacy HTTPS: false
Legacy Port: 8001
Log Modules: -1
Log Level: INFO
Days to keep events: 2
Session timeout in mins: 30
DB backup in days: 2
[7m--More-- [27m
[K
-------------
Services
-------------
Service Name: Context Aware Service
Service Version: 7.4.0.38
Admin Status: Enabled
Operation Status: Up
Service Name: WIPS
Service Version: 1.0.4041.0
Admin Status: Disabled
Operation Status: Down
Service Name: Mobile Concierge Service
Service Version: 2.0.0.37
Admin Status: Disabled
Operation Status: Down
Service Name: Location Analytics Service
Service Version: 1.0.0.12
Admin Status: Disabled
Operation Status: Down
--------------
Server Monitor
--------------
Server start time: Fri Apr 05 12:22:05 MSK 2013
Server current time: Mon Apr 08 10:38:43 MSK 2013
Server timezone: Europe/Moscow
Server timezone offset: 14400000
Restarts: 7
Used Memory (bytes): 136924360
Allocated Memory (bytes): 533528576
Max Memory (bytes): 1908932608
DB virtual memory (kbytes): 0
DB virtual memory limit (bytes): 0
DB disk memory (bytes): 2184652416
DB free size (kbytes): 0
---------------
Active Sessions
[7m--More-- [27m
---------------
Session ID: 23444
Session User ID: 1
Session IP Address: 172.30.0.70
Session start time: Fri Apr 05 12:45:28 MSK 2013
Session last access time: Mon Apr 08 10:37:44 MSK 2013
----------------------------
Default Trap Destinations
----------------------------
Trap Destination - 1
-----------------
IP Address: 172.30.0.100
Last Updated: Thu Apr 04 15:49:32 MSK 2013
-------------
Context Aware Service
-------------
Total Active Elements(Wireless Clients, Tags, Rogue APs, Rogue Clients, Interferers, Wired Clients): 0
Active Wireless Clients: 0
Active Tags: 0
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, Tags) Limit: 3000
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) Not Tracked due to the limiting: 0
-------------------------
Context Aware Sub Services
-------------------------
Subservice Name: Aeroscout Tag Engine
Admin Status: Disabled
[7m--More-- [27m
Operation Status: Down
Subservice Name: Cisco Tag Engine
Admin Status: Enabled
Operation Status: Up
And today i found few strange info messages
4/08/13 10:45:53.80 INFO[location] [33] Failed to find heatmap for AP interface 34:a8:4e:4e:07:d0-5.0-0
4/08/13 10:45:53.80 INFO[location] [33] Failed to find heatmap for AP interface 34:a8:4e:4e:07:d0-5.0-0
4/08/13 10:45:53.80 INFO[location] [33] Failed to find heatmap for AP interface 34:a8:4e:c2:72:d0-5.0-0
4/08/13 10:45:53.80 INFO[location] [33] Failed to find heatmap for AP interface 34:a8:4e:c2:72:d0-5.0-0
4/08/13 10:45:53.80 INFO[location] [33] Failed to find heatmap for AP interface 34:a8:4e:c2:f8:50-5.0-0
4/08/13 10:45:53.80 INFO[location] [33] Failed to find heatmap for AP interface 34:a8:4e:c2:f8:50-5.0-0
Any idea?
04-09-2013 02:05 AM
Hi,
We also have the same problems with MSE and experience the exact same log messages in the logs.
Looking forward to find the solution to this problem.
regards
Knut Eilif Husa
04-08-2013 06:17 AM
The operational service is down as it shows on what you posted. Did you enable the service in Prime?
Sent from Cisco Technical Support iPhone App
04-08-2013 06:20 AM
which service exactly?
04-08-2013 06:26 AM
04-08-2013 10:09 AM
I was looking at the wrong service.... so you do have it up but the MSE doesn't show any clients... The only thing I would try is to remove the MSE and add teh MSE back to PI. There is nothing else you can do especially if the WLC5508 has clients authenticated to itself. The WLc sends the info to PI and then MSE handles it from there.
Thanks,
Scott
Help out other by using the rating system and marking answered questions as "Answered"
04-08-2013 10:13 AM
had a similar issue with my internal MSE. I had to default it, and then run throught the setup script again. Once I did that I started tracking clients
HTH,
Steve
------------------------------------------------------------------------------------------------
Please remember to rate useful posts, and mark questions as answered
08-30-2013 09:24 PM
MSE not discovering Clients with CISCO SINGLE BAND AP
Description
Symptom:
MSE discovery is not working with Single Band AP
Conditions:
Single Band AP
Workaround:
change Single band AP with Dual Band
This issue is captured in the following document:
Cisco Mobility Services Engine (MSE) unable to discover clients and rogues
Regards,
Vinay Sharma
Community Manager
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide