AMP version : 8.0.11
Issue reported : Client count discrepancy between controller and Airwave when preferred AMON is enabled.
Client count discrepancy between controller and Airwave when preferred amon is enabled.
1. We may not see any crash or error message in Amp logs related to the client count discrepancy.
2. But we will see Amon data loss from the system performance page,
4. From the rabbitmq list queues we could notice that the amon messages are getting filled up. Example from the below output the AMP_papi_facade is filling up with huge amon messages.
[root@airwave log]# rabbitmqctl list_queues
Listing queues ...
This issue happens with only controllers upgraded to the version 184.108.40.206 and later. Since the amon buffer size is reduced in those codes to 1400 so AMP continuously receive amon messages which packs the rabbitmq list queue.
Note: Upgrading the controller to 220.127.116.11 will still hold amon buffer size as 1400, only new install of 18.104.22.168 will have the amon buffer size as 32000.
To resolve this issue instantly without upgrading the controller we can increase the amon msg buffer size by executing the following command on the controller,
#amon msg-buffer-size 32000
After increasing the amon msg buffer size to 32000 on controller we can monitor AMP for the accurate client count.