If polling intervals are set too fast, AirWave won't be able to process all the data it gets, and will end up dropping data sets in order to keep up. Whenever there are multiple similar data sets queued up (ie rogue data from Controller1 received at 11:00am and rogue data from Controller1 received at 11:15am) we drop the older data and only process the newer data.
It's possible to enable some advanced debugging to determine how often AirWave is dropping these packets.
ENABLE/DISABLE LOGGING
# qlog enable work_queue_profile
# qlog disable work_queue_profile
COUNT THE INSTANCES WHERE DATA WAS DROPPED BECAUSE IT WAS STALE
# parse_qlog_wq_profile.pl
# parse_qlog_wq_profile.pl -s "Jun 1 2010" -e "Jun 2 2010"
That outputs something like this:
-----begin output-----
Filtering for dates between:
Tue Jun 1 00:00:00 2010
and Wed Jun 2 00:00:00 2010
Clobber Count Topic
59 dns_response
28 thin_ap_radio
23 thin_ap_client
20 thin_ap_status
20 aruba_local_controller_discovery
19 device_resources
18 controller_role
2 thin_ap_discovery
2 thin_ap_mesh
-----end output-----
If data is getting dropped (aka clobbered), the two best changes to make are:
1. Slow down polling intervales on the Groups -> Monitoring pages.
2. Increase Client Monitoring processes on the AMP Setup page.