Network Management
Missing access points(APs) on wireless controller in NPM
This article discusses an issue with wireless controller where access points(APs) do not show up in the List of Thin Access Points widget
First published date
Last published date
Overview
Product section
Cause
- Wireless Controller information is not enabled for polling under List Resources
- Wireless controller may be very recently added to monitoring and thus, NPM still discovers the access points connected to it
- Collector service failed - if you notice the following error in the collector logs then you need to check the steps in the link in resolution 2.
-
ERROR SolarWinds.Collector.PollingController.PollingPlanResolver - Resolve polling plan failed!! We will try to resolve it in the next round System.IO.FileNotFoundException: Could not load file or assembly 'SolarWinds.CloudMonitoring.Shared, Version=2020.2.6.50015, Culture=neutral, PublicKeyToken=null' or one of its dependencies. The system cannot find the file specified.
-
- OIDs required by NPM to display adequate information about access points are missing in SNMP
Resolution
Resolution 1 - Enable Wireless Controller information under List Resources
-
Go to Settings > Manage Nodes
-
Check the affected wireless controller, and click 'List Resources'
-
(If shown) Hit 'Force Refresh' to update the resources listed
-
Check Wireless Controller to enable it, and click 'Submit'
Wait for two hours to allow NPM to rediscover the wireless controller
By default, NPM rediscovers a node such as a wireless controller every 30 minutes. Two hours of data collection should be enough for NPM to build access point(AP) information
Resolution 2 - Collector service crashing and unable to collect Thin AP information as well as other information in Orion
Please, refer to the documentation below that explains steps to fix the collector service in case you encounter the mentioned error:
Resolution 3 - Verify SNMP data provided by wireless controller thru the OIDs required by NPM using SNMP walk
- Run SNMPWalk on the affected wireless controller
- Compare the resulting file with the OIDs required by NPM