Is the Node Polling Interval or Statistics Collection interval of controller used to determine AP available status? We are running v10.5.
If you've added in your AP's as separate nodes into Orion, then it will be using Node Polling interval to check the status. But if you are looking at the AP's as part of your WLC, then it's using Statistics Collection interval to get details on the AP.
Thanks superfly99! That’s what I suspected. We look at the APs as part of the WLC using the default Statistics Collection interval (10 min). We didn’t think there was much gain monitoring thin APs as a node. Now that I know the monitoring is based off the Statistics interval, we may consider cutting the statistics interval to 5 min on WLCs to recognize APs down/up sooner. Thanks again for your help!
Might want to create an idea for SOlarwinds to accept traps from the AP controllers indicating the state of an AP so NPM can flag them as down immediately the controller says they are instead of having to poll the controller. I have over 9500 wireless APs (on fail-over clusters so NPM thinks I have more than twice this number). polling/Alerting for APs status is slow (and unreliable) when they are failing over to other controllers)
RichardLetts wrote:Might want to create an idea for SOlarwinds to accept traps from the AP controllers indicating the state of an AP so NPM can flag them as down immediately the controller says they are instead of having to poll the controller. I have over 9500 wireless APs (on fail-over clusters so NPM thinks I have more than twice this number). polling/Alerting for APs status is slow (and unreliable) when they are failing over to other controllers)
RichardLetts wrote:
Does it log a syslog when this occurs? If yes, then you could use that to monitor the AP's.
RichardLetts: I'm very curious to know how you are monitoring the AP status now. How you configured the alerts? is it on Traps or polled status?
I too am curious about this and would be keen to learn how you've got it configured - Please share
