Table of Contents
Advertisement
Configuring the Switch for Access Point Discovery
• To provide an upgrade path from Cisco products that use LWAPP to next-generation Cisco products
• To manage RFID readers and similar devices
• To enable switchs to interoperate with third-party access points in the future
Viewing Access Point Join Information
Join statistics for an access point that sends a CAPWAP discovery request to the switch at least once are
maintained on the switch even if the access point is rebooted or disconnected. These statistics are removed
only when the switch is rebooted or when you choose to clear the statistics.
Troubleshooting the Access Point Join Process
Access points can fail to join a switch for many reasons such as a RADIUS authorization is pending, self-signed
certificates are not enabled on the switch, the access point and switch's regulatory domains do not match, and
so on.
You can configure the access points to send all CAPWAP-related errors to a syslog server. You do not need
to enable any debug commands on the switch because all of the CAPWAP error messages can be viewed
from the syslog server itself.
The state of the access point is not maintained on the switch until it receives a CAPWAP join request from
the access point, so it can be difficult to determine why the CAPWAP discovery request from a certain access
point was rejected. In order to troubleshoot such joining issues without enabling CAPWAP debug commands
on the switch, the switch collects information for all access points that send a discovery message to this switch
and maintains information for any access points that have successfully joined this switch.
The switch collects all join-related information for each access point that sends a CAPWAP discovery request
to the switch. Collection begins when the first discovery message is received from the access point and ends
when the last configuration payload is sent from the switch to the access point.
When the switch is maintaining join-related information for the maximum number of access points, it does
not collect information for any more access points.
You can also configure a DHCP server to return a syslog server IP address to the access point using option 7
on the server. The access point then starts sending all syslog messages to this IP address.
You can configure the syslog server IP address through the access point CLI, if the access point is not connected
to the switch by entering the capwap ap log-server syslog_server_IP_address command.
When the access point joins a switch for the first time, the switch pushes the global syslog server IP address
(the default is 255.255.255.255) to the access point. After that, the access point sends all syslog messages to
this IP address, until it is overridden by one of the following scenarios:
• The access point is still connected to the same switch, and you changed the global syslog server IP
• The access point is still connected to the same switch, and you configured a specific syslog server IP
OL-28697-01
that use CAPWAP
address configuration on the switch by using the ap syslog host Syslog_Server_IP_Address command.
In this case, the switch pushes the new global syslog server IP address to the access point.
address for the access point on the switch by using the ap name Cisco_AP syslog host
Syslog_Host_IP_Address command. In this case, the switch pushes the new specific syslog server IP
address to the access point.
Lightweight Access Point Configuration Guide, Cisco IOS XE Release 3SE (Catalyst 3650 Switches)
Viewing Access Point Join Information
21
Advertisement
Table of Contents
