So, I'm interested to hear how others are using Soalrwinds NPM to do monitoring of access points, be they thin or be they not It seems to me there are at least a couple of approaches depending on technology in use, configuration and noise generated.
Some of the options that I see are: (for ease of typing, where I say monitor then presume it will also alert)
1.
Monitor the IP of every AP as its own node, and also monitor the interface it is attached to. Can generate a lot of alert noise and multiple alerts per single AP going down.
2.
As for 1, but only monitor the AP as a direct IP (node). Can reduce the noise (quantity) of alerts
3.
Only monitor the interface, and rely on being able to poll the WLC for up / downs. Possibly the best (?) compromise but would still generate two alerts per every down.
4.
Only monitor the up/downs from the WLC if they are Thin APs. Ignores the physical interface the devices are connected to, reduces noise but makes identifying the interface hard if documentation is not accurate.
5.
A combination of all the above. Monitor the AP as a node, monitor the interface, and alert on traps. This clearly would be the noisiest in terms of alerts.
-- ++ --
I'm sure there are other options I'm not immediately seeing but talk to me.
Tell me what your approach is as I'm inetrested to hear?
Let me also give you a scenario that may or may not help responses:
A client has >4000 Thin APs managed via a WLC but due to configuration the actual IP of each device is not visible except from or through the GUI of the WLC. Due to the nature of the setup, Solarwinds also sees every device twice as different SSIDs appear on different WLC's.. Solarwinds is seeing the Thin AP up / down traps and the physical interafces where the device is patched is monitored (but not consistently). To assist troubleshooting a weekly report is run that generates a "show CDP Neighbor" (sic) outpt for all switches - however this is not without its own pitfalls including not picking up on incorrectly deployed APs. To cap it all, the clients end users constantly move APs around for various reasons, and there is no central listing of where each AP is meant to be physically installed.
So I guess two immediate questions:
- How do you monitor 1000's of APs
- And how would you monitor given the above scenario (if any different)
And go...