Using NPM 11.5. Anyone know how to set up alerts on Wireless Thin Access Point's ? Having difficulty getting alert messages to display thin client info in the alert message field.
Unfortunately the Thin AP's don't have any smarts about them.
Are you looking to see when an AP goes down? You could add each AP in as a node check by ICMP. This would mean setting reserved DHCP addresses on your AP's.
If not, what are you hoping to see?
We use Cisco Prime to manage our WLC's. This will alert me if an AP disassociates itself from a WLC.
Like superfly99, we use Cisco PRIME to handle our Thin APs and their notifications.
Now understand that I haven't yet pointed NPM and my WLC 5508's at each other, but the 5508's put out so much syslog data that I'm just about ready to go out on a limb and say that NPM can probably duplicate any lightweight AP status change that PRIME can show--and probably show it in a number of more flexible options.
And do it prettier than PRIME can, too.
It's on my list of things to test & learn . . .
Why would you have Prime when you already have Solarwinds or vice versa? The main selling point of Solarwinds is, non vendor centric - but i guess in terms of thin AP monitoring - it defeats the purpose of the product. We are also in the process of looking at alternative monitoring platforms like Prime and Zabbix to monitor our 40k+ AP estate (who knows we end up moving the entire monitoring suite), but good to know that we are not the only ones to suffer the thin AP monitoring and alerting aspect
Hope Solarwinds takes an action soon as WiFi and especially thin (controlled AP's) are becoming the requirement of the day and unfortunately a lot of other competitors have already sussed this out in their new releases.
Cisco Prime is the result of wireless and wired management tool mergers (Cisco WCS and CiscoWorks). The predecessor to Prime we used to use was wireless only. It aggregated our 5508 WLCs in one overseeing device to aggregate data and reports for everything. It also has the ability to push out configuration templates for the WLCs, which helps assure the settings are the same across multiple WLCs. There are a number of reports available and more charts of wireless usage than I was able to get in NPM.
The WLCs can go into NPM for monitoring, and will report some data like rogue APs and what APs you have attached to the WLCs. We used SNMP for this. There was a canned alert for thin client down also. NPM/NCM doesn't do the templates or all the reports, at least not yet. We still needed Cisco Prime for that, or work the settings directly on the WLCs with the risk of human error and not getting the WLCs identically configured.
I found sending WLC syslog to NPM to be way too much data, and a lot of it not important so I didn't really use that data.
Amen to that--WLC syslog information is more than NPM's Syslog solution can handle, and contains far more information than a Network Analyst needs. It's as if it's permanently in debug mode.
