Wireless_Rogue_AP_Detection.UnDP

Version 2

    Even though Wireless Rogue detection is built into NPM Wireless Polling, it weirdly only gives you the WLC that detected the Rogue AP, not the actual Access Points that discovered the Rogue signal, even though in the SNMP MIB's all of that data is gathered.  Often I have clients who use a single WLC to manage APs in multiple sites.  Knowing which AP on the WLC detected the rogue signal is imperative for this feature to be useful.  Unless of course I'm missing something and its there and I completely wasted my time building this...  But oh well, its built.

     

    I built and tested this UnDP against a Cisco Wireless LAN Controller model 5508, but I imagine it would work with any Cisco WLC.  For other manufacturer's it will depend on whether they support the OID's that are used in this poller.

     

    Because this poller can return a TON of results (the client I was working with had couple dozen AP's spread out across 24 locations in 4 states, so we were seeing approximately 3,000 rogue AP's detected in total), the traditional Tabular Poller view resource table didn't cut it.  Especially since if a rogue AP signal is detected that doesn't have a name, the Tabular table resource puts the Row ID in that column, which is long and ugly.  So, I also created a Custom Query Resource that allows searching on the Rogue AP/SSID name, the AP that the signal was detected on name, and the channel. 

     

    Instructions:

     

    - Download and Import this UnDP file into your Universal Device Poller application on your Primary Orion Polling Engine.

    - Assign it to the Wireless Controller(s) you wish to get additional Rogue AP info from

    - Go to the Orion Web Console and edit the "Wireless LAN Controller Details View" (obviously if you don't want this resource to display on all of the WLC's in your environment, or you haven't assigned the UnDP to all of your WLC's, you'll want to go into Manage Views and Copy the Wireless LAN Controller Details View and edit that copy.  Put the "Custom Query" resource on the new edited copy you just may and then go assign the new view either by Device Type or in the Edit Properties section of the WLC(s) you assigned the UnDP to.)

    - Go to this link (COMING SOON) and follow the rest of the instructions for adding the SWQL query into the Custom Query resource.