Chapter 1 FAQs and Troubleshooting
Devices FAQs and Troubleshooting
Symptom SNMP Unreachable faults are displayed more frequently than the set polling interval.
Possible Cause When the WLSE polls for any faults, it also checks if the device is SNMP reachable. If the device is unreachable, it will generate an SNMP Unreachable fault no matter what the SNMP Reachable poll interval is.
Recommended Action None.
Devices FAQs and Troubleshooting
•Devices FAQs, page
•Devices Troubleshooting, page
Devices FAQs
•Q.Can the WLSE auto rename new APs to a unique name - for example incrementally in the form of ap01, ap02 and so on?
•Q.Why is hostname (device name), sysContact, and sysLocation information not updated in the WLSE after I change these parameters on the access points?
•Q.What is an invalid CDP seed?
•Q.Can I discover devices if CDP is disabled?
•Q.What are the extra inventories listed in the Run Now folder?
•Q.What are the results of adding or removing an interface from an access point?
•Q.Can the WLSE discover access points that are connected to
•Q.Can I register an access point as an AAA server to be monitored by the WLSE?
•Q.How does the WLSE handle duplicate IP addresses on APs?
•Q.Will the WLSE discover a router or switch that has no access points connected to it?
Q.Can the WLSE auto rename new APs to a unique name - for example incrementally in the form of ap01, ap02 and so on?
A.Auto assigning incremental names to APs is not possible, but a workaround could be to select Devices > Discover > Discover > Advanced Options, and use the Name Format field. Click Learn About Name Format to understand the various options.
Q.Why is hostname (device name), sysContact, and sysLocation information not updated in the WLSE after I change these parameters on the access points?
A.The hostname (device name), sysContact, and sysLocation parameters are updated during discovery, not during inventory. You should rediscover the devices (without deleting them), after making the changes on the access points.
FAQ and Troubleshooting Guide for the CiscoWorks Wireless LAN Solution Engine
|
| ||
|
|