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) :
Observation :
Analysis :
03/28/14 03/28/14 03/28/14 03/28/14 03/28/14 00:0c:cc:70:28:29-TAGS-00:1e:bd:67:91:20-0-0-0, 00:0c:cc:70:28:29-TAGS-00:1e:bd:67:c4:10-0-0-0, 00:0c:cc:70:28:29-TAGS-00:1e:bd:67:c3:d0-0-0-0, 03/28/14 00:0c:cc:70:28:29-TAGS-00:1e:bd:67:91:20-0-0-0, 00:0c:cc:70:28:29-TAGS-00:1e:bd:67:c4:10-0-0-0, 00:0c:cc:70:28:29-TAGS-00:1e:bd:67:c3:d0-0-0-0, 03/28/14 00:0c:cc:70:28:29-TAGS-00:1e:bd:67:91:20-0-0-0,-87,5,3716922,3716918,1 00:0c:cc:70:28:29-TAGS-00:1e:bd:67:c4:10-0-0-0,-88,5,3716922,3716918,1 00:0c:cc:70:28:29-TAGS-00:1e:bd:67:c3:d0-0-0-0,-76,5,3716922,3716918,1 03/28/14 03/28/14 [00:0c:cc:70:28:29-TAGS-00:1e:bd:67:91:20-0-0-0, 03/28/14 03/28/14 03/28/14 03/28/14 03/28/14 03/28/14 03/28/14 03/28/14 03/28/14 03/28/14 |
As you can see, the “LocationDataCacheImpl.AggregationTask” skips the message (and then the notification is not created by the MSE and not sent to my application) !
Can anybody help me ? Where and how configure this “aggregation” ?
Thank you !
Stéphane GUEDEU
Hi Stephane,
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
Refer Configuring Link Aggregation for more detials
Thanks and Regards,
Geevarghese