I’m messing around with some stuff in my lab and have a couple of AP/Sensors (dual function) adopted to an RFS4K….and am using these devices in ADSP (8.1.3b2) for LiveRF testing. Not managing the AP/Sensors in ADSP, only using them for polling data for LiveRF.
Everything seems to be working except that I’m seeing the AP portion of the AP/Sensor devices going Online/Offline. (Sensors seem to be consistently staying online in ADSP) For the small number of devices that are being polled, I’ve got the polling intervals set pretty lax (5min/10min).
Any ideas of why this might be happening?
5 Replies
In my customer's case, ADSP is managing about 2000 remote AP5131m, but I have the same issue. Quite a lot of them are showing Offline status, while they are properly up and running: Ping response is about 50 ms, which is fine. Both https, snmp and ssh work fine on them. However, they keep on being displayed as Offline, and they just can't get audited. I set SNMP timeout to 999 (maximum allowed, not 9999 by the way!) and 5 retries, to no avail. Could I maybe increase this timeout via CLI? Thanks!
So far, has not helped. In fact, the Online/Offline ratio has basically swapped. The AP I'm monitoring is now Online for about 4minutes and then Offline for 50minutes. Keeps repeating this pattern.
From an ADSP configuration standpoint, if I only poll the RFS in order to gather up/down states and collect data for LiveRF, do I need to apply a WLAN Mgmt license to each of the adopted APs (on the RFS)? Or, if I still need the licenses on the APs, should I simply configured ADSP so that it doesn't know how to talk to the APs by modifying the Communications Profile? I'm testing this right now, but it seems like if I 'broke' ADSP's ability to talk to the APs, it's going to interpret the communications failure as the AP being Offline. [EDIT] I've gone through and setup everything according to your response. I'll report back later after it's had a few chances to go through the long delays for polling.
As long as you have LiveRF licenses applied the data that is need for coverage visualizations in LiveRF will be collected from the controller. WLAN management licenses are not required.
Increasing the time out will be the most effective way to keep consistent data collection from a 5.2.x or a 5.3.x WiNG 5.x Controller. Please make sure you have the following values set on ADSP and your problems should go away. ADSP Communication Profile Settings
1) SNMP timeout – Increase the timeout value 10 seconds (9999ms). The larger the timeout, the more reliable the system operation will be.
ADSP Polling Profile Settings
2) Data Poll Interval –
a) Status poll interval -- 30 minutes or more.
b) Data Collection interval -- 60 minutes or more.
ADSP Polling
3) In a network topology where there are controllers in the network, the polling should be set up only on the RFS Controllers, and not directly to the Access Points – that is not a supported configuration. It is only necessary to poll the controller which has all required information for the network. Configure ADSP to poll only the controllers, and not the APs.