Cloud Managed Networks

I recently moved a couple of controllers out of one cluster and into another to balance requirements. The relevant Airwave instance is refusing to show clients or traffic from the moved controllers. I've picked over config on each moved controller  to check that SNMP and MON receiver settings are correct/updated after the move (including SNMPv3 username and passwd on both Controllers and AW), but I'm failing to see where the problem is. Airwave is reflecting the APs on each controller, but that's all.
Anyone got an idea what I've missed?
Thanks.

A bit more of a dig yields
https://community.arubanetworks.com/discussion/new-controller-on-airwave-no-clientusage-data

https://community.arubanetworks.com/community-home/librarydocuments/viewdocument?DocumentKey=1f85df6d-88d5-4762-888e-8829247038ee&CommunityKey=96609c68-a98a-4a35-b790-987564d4402d&tab=librarydocuments

The datapath session uses the controller's correct IP address (that of its management interface VLAN, shown correcty in ip interface brief) and the IP addresses configured in Airwave when checking for the controller IP address under 'Manage' for the controller device is also correct.

I've run the qlog debug, but something I've not been able to view is the qlog output. When I enter 'vi amon' I get told '.....is not allowed.'



Any thoughts that might help?
Thanks

I seem to be having very similar issues, recently abandoned our older AW server, and upgraded TWO NEW servers to the new AW 8.3.0 'redhat' version.  It appears all the devices (controllers and APs) seen in both AW servers, but I am not seeing any information on client devices.  

It looks like our problem was the result of a poor setting in AMP Setup>General>Performance

Originally for this server the processes was set to 3. On our other 2 AW it is set to 15.

This setting was generating errors on the System>Performance page (which I hadn't looked at, could have saved myself a lot of time here, no idea why/how it got set to 3)

After this the server had to rebooted as it dropped and didn't recapture any data from the controllers. After a reboot, and giving some time for polling, we ended up with clients being reported and usage being recorded where previously we only saw '0'.

We finally have Glass pretty much in line with the MC now, reporting almost accurately for each of the 3 clusters. I guess the variance with the MC is now down to Glass polling the AW instances.

We still have problems with this AW server (link up link down 16386 alerts being generated) but clients and usage appears fixed.