MSE/ContextAware : some notifications don't arrive to my third party application

[compterds]

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.       

Observation :

• 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)

Analysis : 

• 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):

00:0c:cc:70:28:29-TAGS-00:1e:bd:67:91:20-0-0-0,
  -87

00:0c:cc:70:28:29-TAGS-00:1e:bd:67:c4:10-0-0-0,
  -88

00:0c:cc:70:28:29-TAGS-00:1e:bd:67:c3:d0-0-0-0,
  -76 

03/28/14
  15:53:14.394 DEBUG [LocationDataCacheImpl.AggregationTask-0] Previous RSSI
  set from controller (ApKey, rssi)

00:0c:cc:70:28:29-TAGS-00:1e:bd:67:91:20-0-0-0,
  -87

00:0c:cc:70:28:29-TAGS-00:1e:bd:67:c4:10-0-0-0,
  -93

00:0c:cc:70:28:29-TAGS-00:1e:bd:67:c3:d0-0-0-0,
  -77 

03/28/14
  15:53:14.394 DEBUG [LocationDataCacheImpl.AggregationTask-0] Fresh RSSI Map
  (Apkey, rssi, lastHeardsecs, currentTimeStamp, timeReceivedbyLoc,
  timestampReportedbyWLC ):

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
  15:53:14.394 DEBUG [LocationDataCacheImpl.AggregationTask-0] Non Fresh RSSI
  Map (Apkey, rssi, lastHeardsecs, currentTimeStamp, timeReceivedbyLoc,
  timestampReportedbyWLC ):  

03/28/14
  15:53:14.394 DEBUG [LocationDataCacheImpl.AggregationTask-0] Common RSSI
  keys:

[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
  15:53:14.394 DEBUG [LocationDataCacheImpl.AggregationTask-0] Difference in
  individual threshold for ApKey:
  00:0c:cc:70:28:29-TAGS-00:1e:bd:67:91:20-0-0-0 = 0

03/28/14
  15:53:14.394 DEBUG [LocationDataCacheImpl.AggregationTask-0] Difference in
  individual threshold for ApKey:
  00:0c:cc:70:28:29-TAGS-00:1e:bd:67:c4:10-0-0-0 = 2

03/28/14
  15:53:14.394 DEBUG [LocationDataCacheImpl.AggregationTask-0] Difference in
  individual threshold for ApKey:
  00:0c:cc:70:28:29-TAGS-00:1e:bd:67:c3:d0-0-0-0 = 1

03/28/14
  15:53:14.394 DEBUG [LocationDataCacheImpl.AggregationTask-0] The previous and
  the current fresh set(in the 15 second window) state after individual RSSI
  compare (similar:boolean): true

03/28/14
  15:53:14.394 DEBUG [LocationDataCacheImpl.AggregationTask-0] Difference in
  aggregated threshold: 1.2909944487358056

03/28/14
  15:53:14.394 DEBUG [LocationDataCacheImpl.AggregationTask-0] The previous and
  the current fresh set(in the 15 sec window) state after aggregate RSSI
  compare (similar:boolean): true

03/28/14
  15:53:14.394 DEBUG [LocationDataCacheImpl.AggregationTask-0] Non fresh
  previous AP RSSI keys: []

03/28/14
  15:53:14.394 DEBUG [LocationDataCacheImpl.AggregationTask-0] No new or
  missing entries. Replace previous with new and skip calculation

03/28/14
  15:53:14.394 DEBUG [LocationDataCacheImpl.AggregationTask-0] Empty Chosen
  RSSI Map

03/28/14
  15:53:14.394 DEBUG [LocationDataCacheImpl.AggregationTask-0] Skipping
  location calculation for macAddress: 00:0c:cc:70:28:29 

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

[Geevarghese Cheria]

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