MSE/ContextAware : some notifications don't arrive to my third party application
I’m doing a lot of tests and i have a pb : some emergency notifications don't arrive to my third party application
Test conditions (the different layers used in the scenario) :
1 AeroScout Tag T4b configured in unidirectional mode (CCX)
CISCO AP, CISCO Controller
CISCO MSE 7.4
CISCO Context Aware Engine
1 Context Aware Notification is created to notify my third party application (triggered by the “emergency” condition)
My third party application is a low level socket reading SOAP/XML messages and returning an ack. (HTTP 200 + empty SAOP message), as mentioned in the CISCO documentation.
When pushing the button of the tag, sometimes, “emergency” notifications are well arriving on my application (through the different layers previously mentioned)
The problem is that the notifications don’t arrive all the time (about 75% arrive on my application, 25% not)
I think a have isolated the pb ; it seems like the MSE decides to aggregate some messages under some unknown (for me) conditions ; this appears clearly in this log (log downloaded from the MSE > System > Logs and filtered by the MAC address (00:0c:cc:70:28:29) of my tag) :
03/28/14 15:53:08.568 DEBUG [AesServerThreadPool-LOCATION_MODULE_TASKS-197] Failed to find heatmap for AP Interface : 00:1e:bd:66:7a:c0-2.4-0
03/28/14 15:53:08.570 DEBUG [AesServerThreadPool-LOCATION_MODULE_TASKS-197] Failed to find heatmap for AP Interface : 00:1e:bd:67:4f:00-2.4-0
03/28/14 15:53:10.544 DEBUG [AesServerThreadPool-LOCATION_MODULE_TASKS-207] Failed to find heatmap for AP Interface : 00:1e:bd:66:7a:c0-2.4-0
03/28/14 15:53:10.544 DEBUG [AesServerThreadPool-LOCATION_MODULE_TASKS-207] Failed to find heatmap for AP Interface : 00:1e:bd:67:4f:00-2.4-0
03/28/14 15:53:14.394 DEBUG [LocationDataCacheImpl.AggregationTask-0] New RSSI set from controller (ApKey, RSSI):
Re: MSE/ContextAware : some notifications don't arrive to my third party application
Tag notification frame interval for stationary tag 3-5 minutes Tag notification frame interval for moving tags <10sec WLC NMSP aggregation window is 2 sec by default Correct aggregation window should be set to make sure that WLC has received updates from all the APs, before sending data to MSE via NMSP. From WLC CLI aggregation window can be set independently for clients, tags, rogue APs, rogue clients and Rfids (Cisco Controller) >config nmsp notification interval rssi ? clients Measurement interval for clients. rfid Measurement interval for rfid tags. rogues Measurement interval for rogue APs and rogue clients
This article will consider the options for using the CMX API to solve business tasks and also some features of using JSON data obtained from CMX.Thanks to the Cisco CMX solutions, Wi-Fi, as an usual network access tool, can turn into a powerful analytics ...
Just completed a demo project to use the Meraki Dashboard APIs with Node-RED.The goal was to build a simple web form that could send the information to Meraki. I thoughtbuilding an Admin tool would be helpful. It can easily be adjusted as a registration f...
Get the Meraki Postman Collection!Postman Collection: Meraki Dashboard Prov APIDashboard Docs: Meraki DashboardAboutMeraki has an API for managing your cloud network. Although the Dashboard website is very powerful, you may want to manage your network in ...
What is whereis?Earlier this year I created the whereis Spark Bot (firstname.lastname@example.org) to address a challenge I faced in the new Cisco North Sydney office (see - The Australian). While the space gives maximum flexibility in work style, and the technology...