Open for Voting

Manage thin access points more like nodes (dependencies, group population, alerting, etc.)

I would like to see that thin access point could be manage more like nodes so you can populate them to groups, set dependencies, custom properties, create better alerting etc. for them.

The solution today for thin access points is a bit thin and it feels like you always ends up with the conclusion that I can't solve my problems because they are only objects to the wireless controllers and can't be managed like nodes.

This future should give a more robust monitoring for our environment in NPM!

  • Not sure if anyone ever checks these, but yes, there is a need to be able to enable or disable the monitoring of a Thin Client like we would do with Volumes, Interfaces, Hardware Sensors, etc...

  • It seems this would be possibly useful if your organization supports only a small point of AP's, which could be configured to allow SSH access into them for configuration control & management.

    But can NPM truly "Manage" AP's like a Cisco 5000 or 8000 series Wireless Controller can--set AP groups, set SSID's, define access, manage HA migrations of AP's between controllers, discover rogues and noise and show clients in real-time on HEAT maps, and push new IOS code upgrades out to the AP's?

    If NPM can do that, then Cisco PRIME could be on its way out!

    On the other hand, managing individual AP's via https or SSH was a major inconvenience, and a security risk, and we disabled it--although it's easy enough to turn back on for a specific device's troubleshooting needs.  I manage 2300 AP's with Prime and a pair of HA 8540 wireless controllers and life is remarkably easy--a couple of clicks and things are upgraded, diagnosed, migrated.

    How 'bout this, community?  Can NPM do for Cisco AP's what PRIME can for them?