Complete these steps if the RFID tags are not seen:
Verify that the Location Appliance server runs. Secure Shell (SSH) to it, and use the getserverinfo command in the command line interface (CLI). A response must appear.
Verify that the Location Appliance is added to the Wireless Control System (WCS) in Locate > Add Server. The default username and password are both admin.
Verify that the WCS and the Location Appliance are synchronized for both the Network Designs, or maps, and the controllers. In order to do this, choose WCS > Locate > Location Servers > Synchronize Servers.
Verify that the Location Appliance polls for the tags/clients. Choose WCS > Location Servers > [server name] > Polling Parameters.
Verify that the controller sees the tags/clients. In order to do this, use the show rfid summary command from the CLI of the controller.
Verify that there is not a Simple Network Management Protocol (SNMP) Community filter that includes only the WCS IP address. The Location Appliance also needs SNMP access to the controller.
If the clients appear but not the tags, this can be because the controllers do not track tags by default. SSH to the controller, and from the CLI, use the show rfid config command. If necessary, enable tag tracking with the config rfid status enable command, and save the configuration.
In the WCS, change the message level to trace, reproduce the problem and collect the logs. In order to do this, complete these steps:
Choose Admin > Logging and choose Trace as the Message Level.
Check the client statspoll check box.
Choose execute now from the dropdown.
Choose Admin > Logging, and click Download from the Download Logs section in order to get the logs.
After the logs are collected, return the Message Level to Error, because Trace degrades performance.
Hi All I am currently in the process of setting up TACACS+ for a new WLC 9800 deployment and have come across a 'feature' where only standard ASCII characters are permitted in passwords. This isn't particularly helpful for deployments outside t...
Hello, We just installed a new 9800-CL controller and updated to prime 3.9 for support of it. Pime says AP Discovery is complete and Telemetry Status is a success but it has not found any of our AP's yet. We have 2702's and we have C9115A...
linux_iosd-image is getting its CPU resource allotment maxed out on a 9800-40 (e.g. from output of "show proc cpu history" due to a large amount of SNMP. Concerned that this will cause problems with wireless RADIUS, is there any way to tune the CPU ...
I have an ap (3702e) that is stuck in a wlc 9800 even when the ap is disconnected.
The problem is that now the ap cannot connect back.
Is their a way to force delete/kick the stuck ap without rebooting the controller?