When one or more network users report that they are having problems, your first course of action should be to gather more information. Begin with a broad perspective and then try to ask pointed questions that will narrow the scope of possible causes. You do not want to panic or similarities in the answers you receive.
For example, if you get reports from many people in the same area, perhaps an AP is misconfigured or malfunctioning. Reports from many areas or from a single service set is identifier (SSID) may indicate problems with a controller configuration. However, if you receive a report of only one wireless user having problems, it might not make sensse to spend time troubleshooting a controller, where many users are supported. Instead, you should focus on that one user's client device and its interaction with an AP.
As you prepare to troubleshoot a single wireless client, think about all of the things a client needs to join and use the network. The following conditions that must be met for a successful association:
* Client is within RF range of an AP, asks to associate
* Client authenticates
* Client request and receives an IP address
Troubleshooting Clients from the Controller
As a wireless client probes and attempts to associate with an AP, it is essentially communicating with the controller. You can access a wealth of troubleshooting information from the controller, as long as you know the client's MAC address.
You can view a client's current status by navigating to Monitor > Clients. The controller will display every client that is associated to any of its APs. To find a specific client in the long list of clients, click the Change Filter link. You can then filter the list based on MAC address, AP name, WLAN profile or SSID, client status, client radio type, and so on.
Issue a show client summary and show client detail <mac-address> on the WLC to view the associated wireless clients.
A wireless LAN controller maintains two types of logs that can be useful for troubleshooting:
* A trap log, which records events such as detected rogue devices, AP changes, channel changes, and invalid settings
* A messge log, which contains system conditions for the controller as a whole You can view the logs with the controller GUI and the CLI.
Methods to Display Controller Log Contents
Log Type GUI Menu CLI Command
Trap log Monitor > Most Recent Traps > View All show traplog
Message log Management > Logs > Message Logs show msglog
Verifying WLC Remote Management Settings
You use the show interface summary command to verify the management IP address and VLAN ID. If management interface VLAN ID is untagged, the native VLAN ID configured on the adjacent switch trunk will be used as its 802.1Q tag.
Verifying Client WLAN Settings
If an end user reports a problem connecting to the wireless network, you should verify that the client device has been configured with wireless settings that match those of the WLAN. If the two do not match, then the association will fail. View the wireless connection settings on the client and look for the SSID and the wireless security parameters.
Verifying AP-to-WLC Connectivity
First, verify the connectivity between an AP and a controller. Usually you will do this when a new AP is installed, to make sure it is able to discover and join a controller before clients arrive and try to use the wireless network. You can also do this at any time as a quick check of the AP's health.
The easiest approach is to simply look for the AP in the list of live APs that have joined the controller. If you know which controller the AP should join, open a management session to it. Navigate to Wireless > All APs > Change Filter, and then enter the AP's MAC address or some portion of its name. If the search reveals a live AP that is joined to the controller, verify the IP address that the AP is using and make sure that the AP Uptime shows a valid working duration
Issue a show ap summary to view the associated APs on the WLC. You can use the debug capwap events enable to troubleshoot AP association on the WLC and debug capwap events disable to disable it. There's no terminal monitor command on a WLC when viewing debug output remotely via telnet or SSH. An output is shown if it hits the debug criteria.
(Cisco Controller) >debug capwap ?
detail Configures debug of CAPWAP detail
dtls-keepalive Configures debug of CAPWAP Data DTLS keep alive packets
errors Configures debug of CAPWAP errors
events Configures debug of CAPWAP events and state
hexdump Configures debug of CAPWAP payloads
info Configures debug of CAPWAP info
packet Configures debug of CAPWAP packet
payload Configures debug of CAPWAP payloads
(Cisco Controller) >debug capwap events ?
disable Disables debug.
enable Enables debug.
(Cisco Controller) >debug capwap events enable
(Cisco Controller) >*spamApTask2: Aug 13 00:49:29.915: 0c:68:03:d7:bf:90 apfSpamProcessStateChangeInSpamContext: Down LWAPP event for AP 0c:68:03:d7:bf:90 slot 0
*spamApTask2: Aug 13 00:49:29.916: 0c:68:03:d7:bf:90 apfSpamProcessStateChangeInSpamContext: Down LWAPP event for AP 0c:68:03:d7:bf:90 slot 1
*spamApTask2: Aug 13 00:49:29.916: 0c:68:03:d7:bf:90 Finding DTLS connection to delete for AP (192:168:1:16/28194)
*spamApTask2: Aug 13 00:49:29.916: 0c:68:03:d7:bf:90 Disconnecting DTLS Capwap-Ctrl session 0x17d38f60 for AP (192:168:1:16/28194)
*spamApTask2: Aug 13 00:49:29.916: 0c:68:03:d7:bf:90 CAPWAP State: Dtls tear down
*spamApTask2: Aug 13 00:49:29.916: acDtlsPlumbControlPlaneKeys: lrad:192.168.1.16(28194) mwar:192.168.1.4(5246)
*spamApTask2: Aug 13 00:49:29.916: 0c:68:03:d7:bf:90 DTLS keys for Control Plane deleted successfully for AP 192.168.1.16
*apfReceiveTask: Aug 13 00:49:29.919: 0c:68:03:d7:bf:90 Received LWAPP Down event for AP 0c:68:03:d7:bf:90 slot 0!
*apfReceiveTask: Aug 13 00:49:29.919: 0c:68:03:d7:bf:90 Received LWAPP Down event for AP 0c:68:03:d7:bf:90 slot 1!
*spamApTask2: Aug 13 00:49:29.925: 0c:68:03:d7:bf:90 DTLS connection closed event receivedserver (192.168.1.4/5246) client (192.168.1.16/28194)
*spamApTask2: Aug 13 00:49:29.925: 0c:68:03:d7:bf:90 Entry exists for AP (192.168.1.16/28194)
*apfReceiveTask: Aug 13 00:49:29.925: 0c:68:03:d7:bf:90 Deregister LWAPP event for AP 0c:68:03:d7:bf:90 slot 0
*spamApTask2: Aug 13 00:49:29.929: 0c:68:03:d7:bf:90 apfSpamProcessStateChangeInSpamContext: Deregister LWAPP event for AP 0c:68:03:d7:bf:90 slot 0
*apfReceiveTask: Aug 13 00:49:29.929: 0c:68:03:d7:bf:90 Deregister LWAPP event for AP 0c:68:03:d7:bf:90 slot 1
*spamApTask2: Aug 13 00:49:29.929: 0c:68:03:d7:bf:90 apfSpamProcessStateChangeInSpamContext: Deregister LWAPP event for AP 0c:68:03:d7:bf:90 slot 1
*spamApTask2: Aug 13 00:49:29.930: update ap status:0c:68:03:d7:bf:90 ,index:1
(Cisco Controller) >*spamApTask2: Aug 13 00:49:29.930: 0c:68:03:d7:bf:90 No AP entry exist in temporary database for 192.168.1.16:28194
*spamApTask1: Aug 13 00:50:32.546: 0c:68:03:d7:bf:90 Discovery Request from 192.168.1.16:28193
*spamApTask1: Aug 13 00:50:32.546: 0c:68:03:d7:bf:90 Join Priority Processing status = 0, Incoming Ap's Priority 1, MaxLrads = 15, joined Aps =0
*spamApTask1: Aug 13 00:50:32.546: apModel: AIR-CAP2602I-S-K9
*spamApTask1: Aug 13 00:50:32.546: apType = 27 apModel: AIR-CAP2602I-S-K9
*spamApTask1: Aug 13 00:50:32.546: apType: Ox1b bundleApImageVer: 8.0.133.0
*spamApTask1: Aug 13 00:50:32.546: version:8 release:0 maint:133 build:0
*spamApTask1: Aug 13 00:50:32.546: 0c:68:03:d7:bf:90 Discovery Response sent to 192.168.1.16 port 28193
*spamApTask1: Aug 13 00:50:32.546: 0c:68:03:d7:bf:90 Discovery Response sent to 192.168.1.16:28193
*spamApTask1: Aug 13 00:50:32.547: 0c:68:03:d7:bf:90 Discovery Request from 192.168.1.16:28193
*spamApTask1: Aug 13 00:50:32.547: 0c:68:03:d7:bf:90 Join Priority Processing status = 0, Incoming Ap's Priority 1, MaxLrads = 15, joined Aps =0
*spamApTask1: Aug 13 00:50:32.547: apModel: AIR-CAP2602I-S-K9
*spamApTask1: Aug 13 00:50:32.547: apType = 27 apModel: AIR-CAP2602I-S-K9
*spamApTask1: Aug 13 00:50:32.547: apType: Ox1b bundleApImageVer: 8.0.133.0
*spamApTask1: Aug 13 00:50:32.547: version:8 release:0 maint:133 build:0
*spamApTask1: Aug 13 00:50:32.547: 0c:68:03:d7:bf:90 Discovery Response sent to 192.168.1.16 port 28193
*spamApTask1: Aug 13 00:50:32.547: 0c:68:03:d7:bf:90 Discovery Response sent to 192.168.1.16:28193
*spamApTask1: Aug 13 00:50:32.547: 0c:68:03:d7:bf:90 Discovery Request from 192.168.1.16:28193
*spamApTask1: Aug 13 00:50:32.547: 0c:68:03:d7:bf:90 Join Priority Processing status = 0, Incoming Ap's Priority 1, MaxLrads = 15, joined Aps =0
*spamApTask1: Aug 13 00:50:32.547: apModel: AIR-CAP2602I-S-K9
*spamApTask1: Aug 13 00:50:32.547: apType = 27 apModel: AIR-CAP2602I-S-K9
*spamApTask1: Aug 13 00:50:32.547: apType: Ox1b bundleApImageVer: 8.0.133.0
*spamApTask1: Aug 13 00:50:32.547: version:8 release:0 maint:133 build:0
*spamApTask1: Aug 13 00:50:32.547: 0c:68:03:d7:bf:90 Discovery Response sent to 192.168.1.16 port 28193
*spamApTask1: Aug 13 00:50:32.547: 0c:68:03:d7:bf:90 Discovery Response sent to 192.168.1.16:28193
*spamApTask1: Aug 13 00:50:42.545: f8:72:ea:a6:e2:03 DTLS connection not found, creating new connection for 192:168:1:16 (28193) 192:168:1:4 (5246)
*spamApTask1: Aug 13 00:50:42.973: acDtlsPlumbControlPlaneKeys: lrad:192.168.1.16(28193) mwar:192.168.1.4(5246)
*spamApTask1: Aug 13 00:50:42.973: f8:72:ea:a6:e2:03 Allocated index from main list, Index: 2
*spamApTask1: Aug 13 00:50:42.974: f8:72:ea:a6:e2:03 Using CipherSuite AES128-SHA
*spamApTask1: Aug 13 00:50:42.974: f8:72:ea:a6:e2:03 DTLS keys for Control Plane are plumbed successfully for AP 192.168.1.16. Index 3
*spamApTask1: Aug 13 00:50:42.975: f8:72:ea:a6:e2:03 DTLS Session established server (192.168.1.4:5246), client (192.168.1.16:28193)
*spamApTask1: Aug 13 00:50:42.975: f8:72:ea:a6:e2:03 Starting wait join timer for AP: 192.168.1.16:28193
*spamApTask1: Aug 13 00:50:42.977: 0c:68:03:d7:bf:90 Join Request from 192.168.1.16:28193
*spamApTask1: Aug 13 00:50:42.977: f8:72:ea:a6:e2:03 Deleting AP entry 192.168.1.16:28193 from temporary database.
*spamApTask1: Aug 13 00:50:42.978: 0c:68:03:d7:bf:90 Dropping request or response packet to AP :192.168.1.16 (28193) by Controller: 192.168.1.4 (5246), message Capwap_wtp_event_response, state Capwap_no_state
*spamApTask1: Aug 13 00:50:42.978: 0c:68:03:d7:bf:90 Message type Capwap_wtp_event_response is not allowed to send in state Capwap_no_state for AP 192.168.1.16
*spamApTask1: Aug 13 00:50:42.979: 0c:68:03:d7:bf:90 Join Version: = 134251776
*spamApTask1: Aug 13 00:50:42.979: apModel: AIR-CAP2602I-S-K9
*spamApTask1: Aug 13 00:50:42.979: apType = 27 apModel: AIR-CAP2602I-S-K9
*spamApTask1: Aug 13 00:50:42.979: apType: Ox1b bundleApImageVer: 8.0.133.0
*spamApTask1: Aug 13 00:50:42.979: version:8 release:0 maint:133 build:0
*spamApTask1: Aug 13 00:50:42.979: 0c:68:03:d7:bf:90 Join resp: CAPWAP Maximum Msg element len = 81
*spamApTask1: Aug 13 00:50:42.980: 0c:68:03:d7:bf:90 Join Response sent to 192.168.1.16:28193
*spamApTask1: Aug 13 00:50:42.980: 0c:68:03:d7:bf:90 CAPWAP State: Join
*spamApTask1: Aug 13 00:50:42.980: 0c:68:03:d7:bf:90 capwap_ac_platform.c:1547 - Operation State 0 ===> 4
*apfReceiveTask: Aug 13 00:50:42.980: 0c:68:03:d7:bf:90 Register LWAPP event for AP 0c:68:03:d7:bf:90 slot 0
*apfReceiveTask: Aug 13 00:50:42.980: apModel: AIR-CAP2602I-S-K9
*apfReceiveTask: Aug 13 00:50:42.980: Wlan Feature status 0 for AP:0c:68:03:d7:bf:90 (slotID 0)
*apfReceiveTask: Aug 13 00:50:42.980: Split tunnel status (Disabled) encoded in the vap payload for WLAN(1), AP:0c:68:03:d7:bf:90 (slotID 0)
*apfReceiveTask: Aug 13 00:50:42.981: apModel: AIR-CAP2602I-S-K9
*apfReceiveTask: Aug 13 00:50:42.981: Wlan Feature status 0 for AP:0c:68:03:d7:bf:90 (slotID 0)
*apfReceiveTask: Aug 13 00:50:42.981: Split tunnel status (Disabled) encoded in the vap payload for WLAN(2), AP:0c:68:03:d7:bf:90 (slotID 0)
*apfReceiveTask: Aug 13 00:50:42.981: 0c:68:03:d7:bf:90 Register LWAPP event for AP 0c:68:03:d7:bf:90 slot 1
*apfReceiveTask: Aug 13 00:50:42.981: apModel: AIR-CAP2602I-S-K9
*apfReceiveTask: Aug 13 00:50:42.981: Wlan Feature status 0 for AP:0c:68:03:d7:bf:90 (slotID 1)
*apfReceiveTask: Aug 13 00:50:42.981: Split tunnel status (Disabled) encoded in the vap payload for WLAN(1), AP:0c:68:03:d7:bf:90 (slotID 1)
*apfReceiveTask: Aug 13 00:50:42.981: apModel: AIR-CAP2602I-S-K9
*apfReceiveTask: Aug 13 00:50:42.981: Wlan Feature status 0 for AP:0c:68:03:d7:bf:90 (slotID 1)
*apfReceiveTask: Aug 13 00:50:42.981: Split tunnel status (Disabled) encoded in the vap payload for WLAN(2), AP:0c:68:03:d7:bf:90 (slotID 1)
*spamApTask1: Aug 13 00:50:43.228: 0c:68:03:d7:bf:90 Configuration Status from 192.168.1.16:28193
*spamApTask1: Aug 13 00:50:43.228: 0c:68:03:d7:bf:90 CAPWAP State: Configure
*spamApTask1: Aug 13 00:50:43.228: 0c:68:03:d7:bf:90 Updating IP info for AP 0c:68:03:d7:bf:90 -- static 0, 192.168.1.16/255.255.255.0, gtw 192.168.1.1
*spamApTask1: Aug 13 00:50:43.228: 0c:68:03:d7:bf:90 Updating IP 192.168.1.16 ===> 192.168.1.16 for AP 0c:68:03:d7:bf:90
*spamApTask1: Aug 13 00:50:43.229: 0c:68:03:d7:bf:90 Setting MTU to 1485
*spamApTask1: Aug 13 00:50:43.276: 0c:68:03:d7:bf:90 Configuration Status Response sent to 192:168:1:16
*spamApTask1: Aug 13 00:50:45.228: 0c:68:03:d7:bf:90 Change State Event Request from 192.168.1.16:28193
*spamApTask1: Aug 13 00:50:45.229: 0c:68:03:d7:bf:90 Radio state change for slot: 0 state: 2 cause: 0 detail cause: 0
*spamApTask1: Aug 13 00:50:45.229: 0c:68:03:d7:bf:90 Change State Event Response sent to 192.168.1.16:28193
*spamApTask1: Aug 13 00:50:45.229: 0c:68:03:d7:bf:90 CAPWAP State: Run
*spamApTask1: Aug 13 00:50:45.229: 0c:68:03:d7:bf:90 Sending the remaining config to AP 192.168.1.16:28193
*spamApTask1: Aug 13 00:50:45.229: 0c:68:03:d7:bf:90 Configuration update request for Init VAP-DATA for slot 0 sent to 192.168.1.16:28193
*spamApTask1: Aug 13 00:50:45.229: 0c:68:03:d7:bf:90 Configuration update request for Init VAP-DATA for slot 0 sent to 192.168.1.16:28193
*spamApTask1: Aug 13 00:50:45.230: 0c:68:03:d7:bf:90 Configuration update request for Init VAP-DATA for slot 1 sent to 192.168.1.16:28193
*spamApTask1: Aug 13 00:50:45.230: 0c:68:03:d7:bf:90 Configuration update request for Init VAP-DATA for slot 1 sent to 192.168.1.16:28193
*spamApTask1: Aug 13 00:50:45.230: 0c:68:03:d7:bf:90 Configuration update request for set/reset telnet message sent to 192.168.1.16:28193
*spamApTask1: Aug 13 00:50:45.230: 0c:68:03:d7:bf:90 Configuration update request for set/reset telnet message sent to 192.168.1.16:28193
*spamApTask1: Aug 13 00:50:45.230: 0c:68:03:d7:bf:90 Configuration update request for configuring association limit params sent to 192.168.1.16:28193
*spamApTask1: Aug 13 00:50:45.230: 0c:68:03:d7:bf:90 Configuration update request for GAS mgmt action frame rate limit params enable=0, interval=500, gasLimit=25, sent to 192.168.1.16:28193
*spamApTask1: Aug 13 00:50:45.230: 0c:68:03:d7:bf:90 Configuration update request for AutoImmune message sent to 192.168.1.16:28193
*spamApTask1: Aug 13 00:50:45.230: 0c:68:03:d7:bf:90 Configuration update request for Band Select Cfg sent to 192.168.1.16:28193
*spamApTask1: Aug 13 00:50:45.230: 0c:68:03:d7:bf:90 Configuration update request for HaConfig message sent to 192.168.1.16:28193
*spamApTask1: Aug 13 00:50:45.230: Ignoring Global LRAD MTU update existing 1485 mtu 1485
*apfReceiveTask: Aug 13 00:50:45.231: 0c:68:03:d7:bf:90 Received LWAPP Up event for AP 0c:68:03:d7:bf:90 slot 0!
*spamReceiveTask: Aug 13 00:50:45.231: 0c:68:03:d7:bf:90 Configuration update request for PHY payload sent to 192:168:1:16
*spamReceiveTask: Aug 13 00:50:45.231: 0c:68:03:d7:bf:90 Configuration update request for RrmInterferenceCtrl payload sent to 192:168:1:16
*spamReceiveTask: Aug 13 00:50:45.231: 0c:68:03:d7:bf:90 Configuration update request for RrmNeighbourCtrl payload sent to 192.168.1.16
*spamReceiveTask: Aug 13 00:50:45.232: 0c:68:03:d7:bf:90 Configuration update request for RrmReceiveCtrl payload sent to 192:168:1:16
*spamReceiveTask: Aug 13 00:50:45.232: 0c:68:03:d7:bf:90 Configuration update request for CcxRmMeas payload sent to 192.168.1.16
*spamReceiveTask: Aug 13 00:50:45.232: 0c:68:03:d7:bf:90 Configuration update for Addba sent to 192.168.1.16:28193
*spamApTask1: Aug 13 00:50:45.350: 0c:68:03:d7:bf:90 Change State Event Request from 192.168.1.16:28193
*spamApTask1: Aug 13 00:50:45.351: 0c:68:03:d7:bf:90 Radio state change for slot: 1 state: 2 cause: 0 detail cause: 0
*spamApTask1: Aug 13 00:50:45.351: 0c:68:03:d7:bf:90 Change State Event Response sent to 192.168.1.16:28193
*spamApTask1: Aug 13 00:50:45.351: 0c:68:03:d7:bf:90 CAPWAP State: Run
*spamApTask1: Aug 13 00:50:45.351: 0c:68:03:d7:bf:90 Sending the remaining config to AP 192.168.1.16:28193
*spamApTask1: Aug 13 00:50:45.351: Ignoring Global LRAD MTU update existing 1485 mtu 1485
*spamApTask1: Aug 13 00:50:45.351: 0c:68:03:d7:bf:90 Configuration Update Response from 192.168.1.16:28193
*apfReceiveTask: Aug 13 00:50:45.352: 0c:68:03:d7:bf:90 Received LWAPP Up event for AP 0c:68:03:d7:bf:90 slot 1!
*spamReceiveTask: Aug 13 00:50:45.352: 0c:68:03:d7:bf:90 Configuration update request for PHY payload sent to 192:168:1:16
*spamReceiveTask: Aug 13 00:50:45.352: 0c:68:03:d7:bf:90 Configuration update request for RrmInterferenceCtrl payload sent to 192:168:1:16
*spamReceiveTask: Aug 13 00:50:45.352: 0c:68:03:d7:bf:90 Configuration update request for RrmNeighbourCtrl payload sent to 192.168.1.16
*spamReceiveTask: Aug 13 00:50:45.352: 0c:68:03:d7:bf:90 Configuration update request for RrmReceiveCtrl payload sent to 192:168:1:16
*spamReceiveTask: Aug 13 00:50:45.352: 0c:68:03:d7:bf:90 Configuration update request for CcxRmMeas payload sent to 192.168.1.16
*spamApTask1: Aug 13 00:50:45.372: 0c:68:03:d7:bf:90 Change State Event Request from 192.168.1.16:28193
*spamApTask1: Aug 13 00:50:45.372: 0c:68:03:d7:bf:90 Change State Event Response sent to 192.168.1.16:28193
*spamApTask1: Aug 13 00:50:45.372: 0c:68:03:d7:bf:90 CAPWAP State: Run
*spamApTask1: Aug 13 00:50:45.372: 0c:68:03:d7:bf:90 Sending the remaining config to AP 192.168.1.16:28193
*spamApTask1: Aug 13 00:50:45.372: Ignoring Global LRAD MTU update existing 1485 mtu 1485
*spamApTask1: Aug 13 00:50:45.372: 0c:68:03:d7:bf:90 Configuration Update Response from 192.168.1.16:28193
*spamApTask1: Aug 13 00:50:45.373: 0c:68:03:d7:bf:90 WTP Event Request from 192.168.1.16:28193
*spamApTask1: Aug 13 00:50:45.373: 0c:68:03:d7:bf:90 WTP Event Response sent to 192.168.1.16:28193
*spamApTask1: Aug 13 00:50:45.374: 0c:68:03:d7:bf:90 Configuration Update Response from 192.168.1.16:28193
*spamApTask1: Aug 13 00:50:45.375: 0c:68:03:d7:bf:90 WTP Event Request from 192.168.1.16:28193
*spamApTask1: Aug 13 00:50:45.375: 0c:68:03:d7:bf:90 WTP Event Response sent to 192.168.1.16:28193
*spamApTask1: Aug 13 00:50:45.376: 0c:68:03:d7:bf:90 Configuration Update Response from 192.168.1.16:28193
*spamApTask1: Aug 13 00:50:45.376: 0c:68:03:d7:bf:90 WTP Event Request from 192.168.1.16:28193
*spamApTask1: Aug 13 00:50:45.377: 0c:68:03:d7:bf:90 WTP Event Response sent to 192.168.1.16:28193
*spamApTask1: Aug 13 00:50:45.377: 0c:68:03:d7:bf:90 Configuration Update Response from 192.168.1.16:28193
*spamApTask1: Aug 13 00:50:45.378: 0c:68:03:d7:bf:90 WTP Event Request from 192.168.1.16:28193
*spamApTask1: Aug 13 00:50:45.378: 0c:68:03:d7:bf:90 WTP Event Response sent to 192.168.1.16:28193
*spamApTask1: Aug 13 00:50:45.445: 0c:68:03:d7:bf:90 Configuration Update Response from 192.168.1.16:28193
*spamApTask1: Aug 13 00:50:45.445: 0c:68:03:d7:bf:90 WTP Event Request from 192.168.1.16:28193
*spamApTask1: Aug 13 00:50:45.445: 0c:68:03:d7:bf:90 Updated Link Latency control for AP 0c:68:03:d7:bf:90
*spamApTask1: Aug 13 00:50:45.445: 0c:68:03:d7:bf:90 WTP Event Response sent to 192.168.1.16:28193
*spamApTask1: Aug 13 00:50:45.506: 0c:68:03:d7:bf:90 Configuration Update Response from 192.168.1.16:28193
*spamApTask1: Aug 13 00:50:45.508: 0c:68:03:d7:bf:90 WTP Event Request from 192.168.1.16:28193
*spamApTask1: Aug 13 00:50:45.509: 0c:68:03:d7:bf:90 WTP Event Response sent to 192.168.1.16:28193
*spamApTask1: Aug 13 00:50:45.509: 0c:68:03:d7:bf:90 Configuration Update Response from 192.168.1.16:28193
*spamApTask1: Aug 13 00:50:45.510: 0c:68:03:d7:bf:90 WTP Event Request from 192.168.1.16:28193
*spamApTask1: Aug 13 00:50:45.510: 0c:68:03:d7:bf:90 WTP Event Response sent to 192.168.1.16:28193
*spamApTask1: Aug 13 00:50:45.510: 0c:68:03:d7:bf:90 Configuration Update Response from 192.168.1.16:28193
*spamApTask1: Aug 13 00:50:45.511: 0c:68:03:d7:bf:90 WTP Event Request from 192.168.1.16:28193
*spamApTask1: Aug 13 00:50:45.512: 0c:68:03:d7:bf:90 Configuration Update Response from 192.168.1.16:28193
*spamApTask1: Aug 13 00:50:45.515: 0c:68:03:d7:bf:90 Configuration Update Response from 192.168.1.16:28193
*spamApTask1: Aug 13 00:50:45.516: 0c:68:03:d7:bf:90 Configuration Update Response from 192.168.1.16:28193
*spamApTask1: Aug 13 00:50:45.517: 0c:68:03:d7:bf:90 Configuration Update Response from 192.168.1.16:28193
*spamApTask1: Aug 13 00:50:45.519: 0c:68:03:d7:bf:90 Configuration Update Response from 192.168.1.16:28193
*spamApTask1: Aug 13 00:50:45.520: 0c:68:03:d7:bf:90 Configuration Update Response from 192.168.1.16:28193
*spamApTask1: Aug 13 00:50:45.524: 0c:68:03:d7:bf:90 Configuration Update Response from 192.168.1.16:28193
*spamApTask1: Aug 13 00:50:45.525: 0c:68:03:d7:bf:90 Configuration Update Response from 192.168.1.16:28193
*spamApTask1: Aug 13 00:50:45.526: 0c:68:03:d7:bf:90 Configuration Update Response from 192.168.1.16:28193
*spamApTask1: Aug 13 00:50:45.584: 0c:68:03:d7:bf:90 Configuration Update Response from 192.168.1.16:28193
*spamApTask1: Aug 13 00:50:45.585: 0c:68:03:d7:bf:90 Configuration Update Response from 192.168.1.16:28193
*spamApTask1: Aug 13 00:50:45.586: 0c:68:03:d7:bf:90 Configuration Update Response from 192.168.1.16:28193
*spamApTask1: Aug 13 00:50:45.587: 0c:68:03:d7:bf:90 Configuration Update Response from 192.168.1.16:28193
*spamApTask1: Aug 13 00:50:45.588: 0c:68:03:d7:bf:90 Configuration Update Response from 192.168.1.16:28193
*spamApTask1: Aug 13 00:50:45.588: 0c:68:03:d7:bf:90 Configuration Update Response from 192.168.1.16:28193
*spamApTask1: Aug 13 00:50:45.589: 0c:68:03:d7:bf:90 Configuration Update Response from 192.168.1.16:28193
*spamApTask1: Aug 13 00:50:45.590: 0c:68:03:d7:bf:90 Configuration Update Response from 192.168.1.16:28193
*spamApTask1: Aug 13 00:50:45.591: 0c:68:03:d7:bf:90 Configuration Update Response from 192.168.1.16:28193
*spamApTask1: Aug 13 00:50:45.592: 0c:68:03:d7:bf:90 Configuration Update Response from 192.168.1.16:28193
*spamApTask1: Aug 13 00:50:45.593: 0c:68:03:d7:bf:90 Configuration Update Response from 192.168.1.16:28193
*spamApTask1: Aug 13 00:50:45.593: 0c:68:03:d7:bf:90 Configuration Update Response from 192.168.1.16:28193
*spamApTask1: Aug 13 00:50:48.508: 0c:68:03:d7:bf:90 Duplicate sequence number in request message
*spamApTask1: Aug 13 00:50:48.509: 0c:68:03:d7:bf:90 WTP Event Request from 192.168.1.16:28193
*spamApTask1: Aug 13 00:50:48.509: 0c:68:03:d7:bf:90 WTP Event Response sent to 192.168.1.16:28193
*spamApTask1: Aug 13 00:50:48.510: 0c:68:03:d7:bf:90 WTP Event Request from 192.168.1.16:28193
*spamApTask1: Aug 13 00:50:48.510: 0c:68:03:d7:bf:90 WTP Event Response sent to 192.168.1.16:28193
*spamApTask1: Aug 13 00:50:48.511: 0c:68:03:d7:bf:90 WTP Event Request from 192.168.1.16:28193
*spamApTask1: Aug 13 00:50:48.511: 0c:68:03:d7:bf:90 WTP Event Response sent to 192.168.1.16:28193
*spamApTask1: Aug 13 00:50:48.512: 0c:68:03:d7:bf:90 WTP Event Request from 192.168.1.16:28193
*spamApTask1: Aug 13 00:50:48.513: 0c:68:03:d7:bf:90 WTP Event Response sent to 192.168.1.16:28193
*spamApTask1: Aug 13 00:50:48.514: 0c:68:03:d7:bf:90 Change State Event Request from 192.168.1.16:28193
*spamApTask1: Aug 13 00:50:48.514: 0c:68:03:d7:bf:90 Change State Event Response sent to 192.168.1.16:28193
*spamApTask1: Aug 13 00:50:48.514: 0c:68:03:d7:bf:90 CAPWAP State: Run
*spamApTask1: Aug 13 00:50:48.515: 0c:68:03:d7:bf:90 Sending the remaining config to AP 192.168.1.16:28193
*spamApTask1: Aug 13 00:50:48.516: Ignoring Global LRAD MTU update existing 1485 mtu 1485
*spamApTask1: Aug 13 00:50:48.516: 0c:68:03:d7:bf:90 Change State Event Request from 192.168.1.16:28193
*apfReceiveTask: Aug 13 00:50:48.517: 0c:68:03:d7:bf:90 Received LWAPP Down event for AP 0c:68:03:d7:bf:90 slot 1!
*spamApTask1: Aug 13 00:50:48.517: 0c:68:03:d7:bf:90 apfSpamProcessStateChangeInSpamContext: Down LWAPP event for AP 0c:68:03:d7:bf:90 slot 1
*spamApTask1: Aug 13 00:50:48.517: 0c:68:03:d7:bf:90 Radio state change for slot: 1 state: 1 cause: 0 detail cause: 37
*spamApTask1: Aug 13 00:50:48.519: 0c:68:03:d7:bf:90 Change State Event Response sent to 192.168.1.16:28193
*spamApTask1: Aug 13 00:50:48.519: 0c:68:03:d7:bf:90 CAPWAP State: Run
*spamApTask1: Aug 13 00:50:48.520: 0c:68:03:d7:bf:90 Sending the remaining config to AP 192.168.1.16:28193
*spamApTask1: Aug 13 00:50:48.520: Ignoring Global LRAD MTU update existing 1485 mtu 1485
*spamApTask1: Aug 13 00:50:48.520: 0c:68:03:d7:bf:90 Change State Event Request from 192.168.1.16:28193
*spamApTask1: Aug 13 00:50:48.520: 0c:68:03:d7:bf:90 Change State Event Response sent to 192.168.1.16:28193
*spamApTask1: Aug 13 00:50:48.520: 0c:68:03:d7:bf:90 CAPWAP State: Run
*spamApTask1: Aug 13 00:50:48.520: 0c:68:03:d7:bf:90 Sending the remaining config to AP 192.168.1.16:28193
*spamApTask1: Aug 13 00:50:48.520: Ignoring Global LRAD MTU update existing 1485 mtu 1485
*spamApTask1: Aug 13 00:50:48.523: 0c:68:03:d7:bf:90 WTP Event Request from 192.168.1.16:28193
*spamApTask1: Aug 13 00:50:48.523: 0c:68:03:d7:bf:90 WTP Event Response sent to 192.168.1.16:28193
*spamApTask1: Aug 13 00:50:48.524: 0c:68:03:d7:bf:90 Change State Event Request from 192.168.1.16:28193
*apfReceiveTask: Aug 13 00:50:48.525: 0c:68:03:d7:bf:90 Received LWAPP Up event for AP 0c:68:03:d7:bf:90 slot 1!
*spamApTask1: Aug 13 00:50:48.525: 0c:68:03:d7:bf:90 Radio state change for slot: 1 state: 2 cause: 0 detail cause: 37
*spamApTask1: Aug 13 00:50:48.527: 0c:68:03:d7:bf:90 Change State Event Response sent to 192.168.1.16:28193
*spamApTask1: Aug 13 00:50:48.527: 0c:68:03:d7:bf:90 CAPWAP State: Run
*spamApTask1: Aug 13 00:50:48.528: 0c:68:03:d7:bf:90 Sending the remaining config to AP 192.168.1.16:28193
*spamApTask1: Aug 13 00:50:48.528: Ignoring Global LRAD MTU update existing 1485 mtu 1485
*spamApTask1: Aug 13 00:50:48.528: 0c:68:03:d7:bf:90 Change State Event Request from 192.168.1.16:28193
*apfReceiveTask: Aug 13 00:50:48.528: 0c:68:03:d7:bf:90 Received LWAPP Down event for AP 0c:68:03:d7:bf:90 slot 0!
*spamApTask1: Aug 13 00:50:48.528: 0c:68:03:d7:bf:90 apfSpamProcessStateChangeInSpamContext: Down LWAPP event for AP 0c:68:03:d7:bf:90 slot 0
*spamApTask1: Aug 13 00:50:48.528: 0c:68:03:d7:bf:90 Radio state change for slot: 0 state: 1 cause: 0 detail cause: 37
*spamApTask1: Aug 13 00:50:48.529: 0c:68:03:d7:bf:90 Change State Event Response sent to 192.168.1.16:28193
*spamApTask1: Aug 13 00:50:48.529: 0c:68:03:d7:bf:90 CAPWAP State: Run
*spamApTask1: Aug 13 00:50:48.529: 0c:68:03:d7:bf:90 Sending the remaining config to AP 192.168.1.16:28193
*spamApTask1: Aug 13 00:50:48.529: Ignoring Global LRAD MTU update existing 1485 mtu 1485
*spamApTask1: Aug 13 00:50:48.533: 0c:68:03:d7:bf:90 Change State Event Request from 192.168.1.16:28193
*spamApTask1: Aug 13 00:50:48.533: 0c:68:03:d7:bf:90 Change State Event Response sent to 192.168.1.16:28193
*spamApTask1: Aug 13 00:50:48.533: 0c:68:03:d7:bf:90 CAPWAP State: Run
*spamApTask1: Aug 13 00:50:48.533: 0c:68:03:d7:bf:90 Sending the remaining config to AP 192.168.1.16:28193
*spamApTask1: Aug 13 00:50:48.533: Ignoring Global LRAD MTU update existing 1485 mtu 1485
*spamApTask1: Aug 13 00:50:48.534: 0c:68:03:d7:bf:90 WTP Event Request from 192.168.1.16:28193
*spamApTask1: Aug 13 00:50:48.534: 0c:68:03:d7:bf:90 WTP Event Response sent to 192.168.1.16:28193
*spamApTask1: Aug 13 00:50:48.535: 0c:68:03:d7:bf:90 Change State Event Request from 192.168.1.16:28193
*apfReceiveTask: Aug 13 00:50:48.535: 0c:68:03:d7:bf:90 Received LWAPP Up event for AP 0c:68:03:d7:bf:90 slot 0!
*spamApTask1: Aug 13 00:50:48.535: 0c:68:03:d7:bf:90 Radio state change for slot: 0 state: 2 cause: 0 detail cause: 37
*spamApTask1: Aug 13 00:50:48.536: 0c:68:03:d7:bf:90 Change State Event Response sent to 192.168.1.16:28193
*spamApTask1: Aug 13 00:50:48.536: 0c:68:03:d7:bf:90 CAPWAP State: Run
*spamApTask1: Aug 13 00:50:48.536: 0c:68:03:d7:bf:90 Sending the remaining config to AP 192.168.1.16:28193
*spamApTask1: Aug 13 00:50:48.536: Ignoring Global LRAD MTU update existing 1485 mtu 1485
*apfMsConnTask_7: Aug 13 00:50:53.448: sending spamAddMobile aclName =
*spamApTask1: Aug 13 00:50:53.449: 0c:68:03:d7:bf:90 Successful transmission of LWAPP Add-Mobile to AP 0c:68:03:d7:bf:90
*spamApTask1: Aug 13 00:50:53.451: 0c:68:03:d7:bf:90 Configuration Update Response from 192.168.1.16:28193
*spamApTask1: Aug 13 00:50:53.453: 0c:68:03:d7:bf:90 Configuration Update Response from 192.168.1.16:28193
(Cisco Controller) >debug capwap events disable
As long as the controller shows the AP with an appropriate IP address, you can assume that there is a working CAPWAP tunnel between the two. If clients are reporting problems with one SSID that they have in common, you should review the WLAN configuration on the controller to make sure it is bound to the correct controller interface and to the correct VLAN.
Another common issue is the AP's regulatory domain or country to select on the WLC. Here's a link for the AP and country compatibility matrix. You can change the country code on the WLC by going to Wireless > Country. I wasn't able to initially register my AIR-CAP2602I since the WLC country code is configured to US. I've checked the WLC syslogs and mentioned an invalid country code error for the AP (base radio MAC address 0c:68:03:d7:bf:90). I issued a show cdp neighbor detail on the switch and saw an -S on its platform. I searched for the AP-to-country compatibility matrix and you can set the country to SG Singapore on the WLC.
.597: %LWAPP-3-RD_ERR7: spam_lrad.c:11196 The system detects an invalid country code () for AP 0c:68:03:d7:bf:90
*spamApTask2: Aug 12 22:57:39.841: %CAPWAP-3-POST_DECODE_ERR: capwap_ac_sm.c:5957 Post decode processing failed for Config status from AP 0c:68:03:d7:bf:90
*spamApTask2: Aug 12 22:57:39.834: %LWAPP-3-RD_ERR4: capwap_ac_sm.c:3316 The system detects an invalid regulatory domain 802.11bg:-A 802.11a:-AB for AP 0c:68:03:d7:bf:90
SW1#show cdp neighbor detail
-------------------------
Device ID: APf872.eaa6.e203
Entry address(es):
IP address: 192.168.1.16
IPv6 address: FE80::FA72:EAFF:FEA6:E203 (link-local)
Platform: cisco AIR-CAP2602I-S-K9, Capabilities: Trans-Bridge Source-Route-Bridge IGMP
Interface: FastEthernet0/14, Port ID (outgoing port): GigabitEthernet0
Holdtime : 166 sec
Version :
Cisco IOS Software, C2600 Software (AP3G2-K9W8-M), Version 15.3(3)JA8, RELEASE SOFTWARE (fc1)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2016 by Cisco Systems, Inc.
Compiled Fri 22-Apr-16 05:48 by prod_rel_team
advertisement version: 2
Duplex: full
Power drawn: 15.400 Watts
Power request id: 32785, Power management id: 3
Power request levels are:15400 13000 0 0 0
Management address(es):
IP address: 192.168.1.16
You can't directly change the country and all radio network (a/b/g/n/ac) must be disabled first. Go to Wireless > 802.11x/x/x > uncheck Enabled on the Network Status option > click Apply.
You can use the show ap join stats summary all and show ap join stats detailed <AP MAC address> commands on a WLC to verify the AP join status. The AP Status was Not Joined since I re-configured my wireless lab. I re-configured the new NTP server IP (which is my router).
kit-7869#clock set 22:18:00 1 Sep 2016
kit-7869#show clock
.22:18:02.699 UTC Thu Sep 1 2016
The AP Status went to Joined and it registered (REG) to the WLC.
Verifying AP-to-Network Connectivity
If you do not find the AP joined to a controller, you will have to move your focus further away from the controller and onto the AP and its wired connection Before an AP can boot up and operate correctly, it must have a power source. Most likely, an AP gets its power from the access layer switch as Power over Ethernet (PoE) over the Ethernet cabling. The more radios an AP supports, the more power it can consume.
Therefore, different AP models can require different amounts of power. You should verify the minimum PoE requirements of an AP and compare that with the PoE capability of the switch The 802.3af standard specifies that a PoE switch can provide up to 15.4 watts to a PoE device. Switch ports using the 802.3at standard can offer up to 30 watts PoE on an interface. When you look for the AP power requirements, be sure that the required power includes all radios in operation.
Once the AP has sufficient power, does it have an IP address? Without the help of a controller, you might have to connect to the AP console and watch the logging information scroll by as the AP tries to boot, get an address, and find a controller to join. You can also query the DHCP server to see whether the AP has an active address lease. If it is not able to get an address from a DHCP server, check the address scope on the server to ensure that the address space is not exhausted.
Tip: To connect to the CLI of an AP, you need to enter some credentials. By default, log in with username Cisco and password Cisco. The default enable secret password is also Cisco.
If the AP is having trouble joining a controller, verify that the switch port configuration where the AP is connected. A lightweight AP needs only a single VLAN to support the CAPWAP tunnel. All WLANs are transported over the tunnel without the need for separate VLANs. In contrast, an autonomous AP has no CAPWAP tunnel, so it needs a trunk link that can carry individual WLANs over VLANs.
Lightweight AP (Access Link)
interface gigabitethernet1/0/1
switchport // NEED TO ISSUE THIS ON AP CONNECTED TO WCM (3650/3850)
switchport access vlan 100
switchport mode access
spanning-tree portfast
no shutdown
Autonomous AP (Trunk Link)
interface gigabitethernet1/0/1
switchport
switchport trunk allowed vlan 100,101,102,103
switchport trunk native vlan 100
switchport trunk encapsulation dot1q
switchport mode trunk
no shutdown
Checking the RF Environment
To investigate problems that could involve things like 802.11 traffic, client roaming, RF interference, or co-channel or adjacent channel interference, you might need to leverage some third-party tools. Wi-Fi scanning tools are more useful for quick scans and walkthrough surveys of an area, to see all of the active APs and their channel use. Typical examples are MetaGeek inSSIDer Office, Android Wifi Analyzer, and Fluke AirMagnet WiFi Analyzer,
Here's what inSSIDer looks like and the wireless network (SSID) around my house. You could also narrow down on which radio band (2.4 GHz or 5G Hz) to be displayed.
For example, if you get reports from many people in the same area, perhaps an AP is misconfigured or malfunctioning. Reports from many areas or from a single service set is identifier (SSID) may indicate problems with a controller configuration. However, if you receive a report of only one wireless user having problems, it might not make sensse to spend time troubleshooting a controller, where many users are supported. Instead, you should focus on that one user's client device and its interaction with an AP.
As you prepare to troubleshoot a single wireless client, think about all of the things a client needs to join and use the network. The following conditions that must be met for a successful association:
* Client is within RF range of an AP, asks to associate
* Client authenticates
* Client request and receives an IP address
Troubleshooting Clients from the Controller
As a wireless client probes and attempts to associate with an AP, it is essentially communicating with the controller. You can access a wealth of troubleshooting information from the controller, as long as you know the client's MAC address.
You can view a client's current status by navigating to Monitor > Clients. The controller will display every client that is associated to any of its APs. To find a specific client in the long list of clients, click the Change Filter link. You can then filter the list based on MAC address, AP name, WLAN profile or SSID, client status, client radio type, and so on.
Issue a show client summary and show client detail <mac-address> on the WLC to view the associated wireless clients.
A wireless LAN controller maintains two types of logs that can be useful for troubleshooting:
* A trap log, which records events such as detected rogue devices, AP changes, channel changes, and invalid settings
* A messge log, which contains system conditions for the controller as a whole You can view the logs with the controller GUI and the CLI.
Methods to Display Controller Log Contents
Log Type GUI Menu CLI Command
Trap log Monitor > Most Recent Traps > View All show traplog
Message log Management > Logs > Message Logs show msglog
Verifying WLC Remote Management Settings
You go to Management tab to verify remote management settings to the WLC.
Use the show
network summary in CLI to verify the WLC management settings.
You use the show interface summary command to verify the management IP address and VLAN ID. If management interface VLAN ID is untagged, the native VLAN ID configured on the adjacent switch trunk will be used as its 802.1Q tag.
Verifying Client WLAN Settings
If an end user reports a problem connecting to the wireless network, you should verify that the client device has been configured with wireless settings that match those of the WLAN. If the two do not match, then the association will fail. View the wireless connection settings on the client and look for the SSID and the wireless security parameters.
Verifying AP-to-WLC Connectivity
First, verify the connectivity between an AP and a controller. Usually you will do this when a new AP is installed, to make sure it is able to discover and join a controller before clients arrive and try to use the wireless network. You can also do this at any time as a quick check of the AP's health.
The easiest approach is to simply look for the AP in the list of live APs that have joined the controller. If you know which controller the AP should join, open a management session to it. Navigate to Wireless > All APs > Change Filter, and then enter the AP's MAC address or some portion of its name. If the search reveals a live AP that is joined to the controller, verify the IP address that the AP is using and make sure that the AP Uptime shows a valid working duration
Issue a show ap summary to view the associated APs on the WLC. You can use the debug capwap events enable to troubleshoot AP association on the WLC and debug capwap events disable to disable it. There's no terminal monitor command on a WLC when viewing debug output remotely via telnet or SSH. An output is shown if it hits the debug criteria.
(Cisco Controller) >debug capwap ?
detail Configures debug of CAPWAP detail
dtls-keepalive Configures debug of CAPWAP Data DTLS keep alive packets
errors Configures debug of CAPWAP errors
events Configures debug of CAPWAP events and state
hexdump Configures debug of CAPWAP payloads
info Configures debug of CAPWAP info
packet Configures debug of CAPWAP packet
payload Configures debug of CAPWAP payloads
(Cisco Controller) >debug capwap events ?
disable Disables debug.
enable Enables debug.
(Cisco Controller) >debug capwap events enable
(Cisco Controller) >*spamApTask2: Aug 13 00:49:29.915: 0c:68:03:d7:bf:90 apfSpamProcessStateChangeInSpamContext: Down LWAPP event for AP 0c:68:03:d7:bf:90 slot 0
*spamApTask2: Aug 13 00:49:29.916: 0c:68:03:d7:bf:90 apfSpamProcessStateChangeInSpamContext: Down LWAPP event for AP 0c:68:03:d7:bf:90 slot 1
*spamApTask2: Aug 13 00:49:29.916: 0c:68:03:d7:bf:90 Finding DTLS connection to delete for AP (192:168:1:16/28194)
*spamApTask2: Aug 13 00:49:29.916: 0c:68:03:d7:bf:90 Disconnecting DTLS Capwap-Ctrl session 0x17d38f60 for AP (192:168:1:16/28194)
*spamApTask2: Aug 13 00:49:29.916: 0c:68:03:d7:bf:90 CAPWAP State: Dtls tear down
*spamApTask2: Aug 13 00:49:29.916: acDtlsPlumbControlPlaneKeys: lrad:192.168.1.16(28194) mwar:192.168.1.4(5246)
*spamApTask2: Aug 13 00:49:29.916: 0c:68:03:d7:bf:90 DTLS keys for Control Plane deleted successfully for AP 192.168.1.16
*apfReceiveTask: Aug 13 00:49:29.919: 0c:68:03:d7:bf:90 Received LWAPP Down event for AP 0c:68:03:d7:bf:90 slot 0!
*apfReceiveTask: Aug 13 00:49:29.919: 0c:68:03:d7:bf:90 Received LWAPP Down event for AP 0c:68:03:d7:bf:90 slot 1!
*spamApTask2: Aug 13 00:49:29.925: 0c:68:03:d7:bf:90 DTLS connection closed event receivedserver (192.168.1.4/5246) client (192.168.1.16/28194)
*spamApTask2: Aug 13 00:49:29.925: 0c:68:03:d7:bf:90 Entry exists for AP (192.168.1.16/28194)
*apfReceiveTask: Aug 13 00:49:29.925: 0c:68:03:d7:bf:90 Deregister LWAPP event for AP 0c:68:03:d7:bf:90 slot 0
*spamApTask2: Aug 13 00:49:29.929: 0c:68:03:d7:bf:90 apfSpamProcessStateChangeInSpamContext: Deregister LWAPP event for AP 0c:68:03:d7:bf:90 slot 0
*apfReceiveTask: Aug 13 00:49:29.929: 0c:68:03:d7:bf:90 Deregister LWAPP event for AP 0c:68:03:d7:bf:90 slot 1
*spamApTask2: Aug 13 00:49:29.929: 0c:68:03:d7:bf:90 apfSpamProcessStateChangeInSpamContext: Deregister LWAPP event for AP 0c:68:03:d7:bf:90 slot 1
*spamApTask2: Aug 13 00:49:29.930: update ap status:0c:68:03:d7:bf:90 ,index:1
(Cisco Controller) >*spamApTask2: Aug 13 00:49:29.930: 0c:68:03:d7:bf:90 No AP entry exist in temporary database for 192.168.1.16:28194
*spamApTask1: Aug 13 00:50:32.546: 0c:68:03:d7:bf:90 Discovery Request from 192.168.1.16:28193
*spamApTask1: Aug 13 00:50:32.546: 0c:68:03:d7:bf:90 Join Priority Processing status = 0, Incoming Ap's Priority 1, MaxLrads = 15, joined Aps =0
*spamApTask1: Aug 13 00:50:32.546: apModel: AIR-CAP2602I-S-K9
*spamApTask1: Aug 13 00:50:32.546: apType = 27 apModel: AIR-CAP2602I-S-K9
*spamApTask1: Aug 13 00:50:32.546: apType: Ox1b bundleApImageVer: 8.0.133.0
*spamApTask1: Aug 13 00:50:32.546: version:8 release:0 maint:133 build:0
*spamApTask1: Aug 13 00:50:32.546: 0c:68:03:d7:bf:90 Discovery Response sent to 192.168.1.16 port 28193
*spamApTask1: Aug 13 00:50:32.546: 0c:68:03:d7:bf:90 Discovery Response sent to 192.168.1.16:28193
*spamApTask1: Aug 13 00:50:32.547: 0c:68:03:d7:bf:90 Discovery Request from 192.168.1.16:28193
*spamApTask1: Aug 13 00:50:32.547: 0c:68:03:d7:bf:90 Join Priority Processing status = 0, Incoming Ap's Priority 1, MaxLrads = 15, joined Aps =0
*spamApTask1: Aug 13 00:50:32.547: apModel: AIR-CAP2602I-S-K9
*spamApTask1: Aug 13 00:50:32.547: apType = 27 apModel: AIR-CAP2602I-S-K9
*spamApTask1: Aug 13 00:50:32.547: apType: Ox1b bundleApImageVer: 8.0.133.0
*spamApTask1: Aug 13 00:50:32.547: version:8 release:0 maint:133 build:0
*spamApTask1: Aug 13 00:50:32.547: 0c:68:03:d7:bf:90 Discovery Response sent to 192.168.1.16 port 28193
*spamApTask1: Aug 13 00:50:32.547: 0c:68:03:d7:bf:90 Discovery Response sent to 192.168.1.16:28193
*spamApTask1: Aug 13 00:50:32.547: 0c:68:03:d7:bf:90 Discovery Request from 192.168.1.16:28193
*spamApTask1: Aug 13 00:50:32.547: 0c:68:03:d7:bf:90 Join Priority Processing status = 0, Incoming Ap's Priority 1, MaxLrads = 15, joined Aps =0
*spamApTask1: Aug 13 00:50:32.547: apModel: AIR-CAP2602I-S-K9
*spamApTask1: Aug 13 00:50:32.547: apType = 27 apModel: AIR-CAP2602I-S-K9
*spamApTask1: Aug 13 00:50:32.547: apType: Ox1b bundleApImageVer: 8.0.133.0
*spamApTask1: Aug 13 00:50:32.547: version:8 release:0 maint:133 build:0
*spamApTask1: Aug 13 00:50:32.547: 0c:68:03:d7:bf:90 Discovery Response sent to 192.168.1.16 port 28193
*spamApTask1: Aug 13 00:50:32.547: 0c:68:03:d7:bf:90 Discovery Response sent to 192.168.1.16:28193
*spamApTask1: Aug 13 00:50:42.545: f8:72:ea:a6:e2:03 DTLS connection not found, creating new connection for 192:168:1:16 (28193) 192:168:1:4 (5246)
*spamApTask1: Aug 13 00:50:42.973: acDtlsPlumbControlPlaneKeys: lrad:192.168.1.16(28193) mwar:192.168.1.4(5246)
*spamApTask1: Aug 13 00:50:42.973: f8:72:ea:a6:e2:03 Allocated index from main list, Index: 2
*spamApTask1: Aug 13 00:50:42.974: f8:72:ea:a6:e2:03 Using CipherSuite AES128-SHA
*spamApTask1: Aug 13 00:50:42.974: f8:72:ea:a6:e2:03 DTLS keys for Control Plane are plumbed successfully for AP 192.168.1.16. Index 3
*spamApTask1: Aug 13 00:50:42.975: f8:72:ea:a6:e2:03 DTLS Session established server (192.168.1.4:5246), client (192.168.1.16:28193)
*spamApTask1: Aug 13 00:50:42.975: f8:72:ea:a6:e2:03 Starting wait join timer for AP: 192.168.1.16:28193
*spamApTask1: Aug 13 00:50:42.977: 0c:68:03:d7:bf:90 Join Request from 192.168.1.16:28193
*spamApTask1: Aug 13 00:50:42.977: f8:72:ea:a6:e2:03 Deleting AP entry 192.168.1.16:28193 from temporary database.
*spamApTask1: Aug 13 00:50:42.978: 0c:68:03:d7:bf:90 Dropping request or response packet to AP :192.168.1.16 (28193) by Controller: 192.168.1.4 (5246), message Capwap_wtp_event_response, state Capwap_no_state
*spamApTask1: Aug 13 00:50:42.978: 0c:68:03:d7:bf:90 Message type Capwap_wtp_event_response is not allowed to send in state Capwap_no_state for AP 192.168.1.16
*spamApTask1: Aug 13 00:50:42.979: 0c:68:03:d7:bf:90 Join Version: = 134251776
*spamApTask1: Aug 13 00:50:42.979: apModel: AIR-CAP2602I-S-K9
*spamApTask1: Aug 13 00:50:42.979: apType = 27 apModel: AIR-CAP2602I-S-K9
*spamApTask1: Aug 13 00:50:42.979: apType: Ox1b bundleApImageVer: 8.0.133.0
*spamApTask1: Aug 13 00:50:42.979: version:8 release:0 maint:133 build:0
*spamApTask1: Aug 13 00:50:42.979: 0c:68:03:d7:bf:90 Join resp: CAPWAP Maximum Msg element len = 81
*spamApTask1: Aug 13 00:50:42.980: 0c:68:03:d7:bf:90 Join Response sent to 192.168.1.16:28193
*spamApTask1: Aug 13 00:50:42.980: 0c:68:03:d7:bf:90 CAPWAP State: Join
*spamApTask1: Aug 13 00:50:42.980: 0c:68:03:d7:bf:90 capwap_ac_platform.c:1547 - Operation State 0 ===> 4
*apfReceiveTask: Aug 13 00:50:42.980: 0c:68:03:d7:bf:90 Register LWAPP event for AP 0c:68:03:d7:bf:90 slot 0
*apfReceiveTask: Aug 13 00:50:42.980: apModel: AIR-CAP2602I-S-K9
*apfReceiveTask: Aug 13 00:50:42.980: Wlan Feature status 0 for AP:0c:68:03:d7:bf:90 (slotID 0)
*apfReceiveTask: Aug 13 00:50:42.980: Split tunnel status (Disabled) encoded in the vap payload for WLAN(1), AP:0c:68:03:d7:bf:90 (slotID 0)
*apfReceiveTask: Aug 13 00:50:42.981: apModel: AIR-CAP2602I-S-K9
*apfReceiveTask: Aug 13 00:50:42.981: Wlan Feature status 0 for AP:0c:68:03:d7:bf:90 (slotID 0)
*apfReceiveTask: Aug 13 00:50:42.981: Split tunnel status (Disabled) encoded in the vap payload for WLAN(2), AP:0c:68:03:d7:bf:90 (slotID 0)
*apfReceiveTask: Aug 13 00:50:42.981: 0c:68:03:d7:bf:90 Register LWAPP event for AP 0c:68:03:d7:bf:90 slot 1
*apfReceiveTask: Aug 13 00:50:42.981: apModel: AIR-CAP2602I-S-K9
*apfReceiveTask: Aug 13 00:50:42.981: Wlan Feature status 0 for AP:0c:68:03:d7:bf:90 (slotID 1)
*apfReceiveTask: Aug 13 00:50:42.981: Split tunnel status (Disabled) encoded in the vap payload for WLAN(1), AP:0c:68:03:d7:bf:90 (slotID 1)
*apfReceiveTask: Aug 13 00:50:42.981: apModel: AIR-CAP2602I-S-K9
*apfReceiveTask: Aug 13 00:50:42.981: Wlan Feature status 0 for AP:0c:68:03:d7:bf:90 (slotID 1)
*apfReceiveTask: Aug 13 00:50:42.981: Split tunnel status (Disabled) encoded in the vap payload for WLAN(2), AP:0c:68:03:d7:bf:90 (slotID 1)
*spamApTask1: Aug 13 00:50:43.228: 0c:68:03:d7:bf:90 Configuration Status from 192.168.1.16:28193
*spamApTask1: Aug 13 00:50:43.228: 0c:68:03:d7:bf:90 CAPWAP State: Configure
*spamApTask1: Aug 13 00:50:43.228: 0c:68:03:d7:bf:90 Updating IP info for AP 0c:68:03:d7:bf:90 -- static 0, 192.168.1.16/255.255.255.0, gtw 192.168.1.1
*spamApTask1: Aug 13 00:50:43.228: 0c:68:03:d7:bf:90 Updating IP 192.168.1.16 ===> 192.168.1.16 for AP 0c:68:03:d7:bf:90
*spamApTask1: Aug 13 00:50:43.229: 0c:68:03:d7:bf:90 Setting MTU to 1485
*spamApTask1: Aug 13 00:50:43.276: 0c:68:03:d7:bf:90 Configuration Status Response sent to 192:168:1:16
*spamApTask1: Aug 13 00:50:45.228: 0c:68:03:d7:bf:90 Change State Event Request from 192.168.1.16:28193
*spamApTask1: Aug 13 00:50:45.229: 0c:68:03:d7:bf:90 Radio state change for slot: 0 state: 2 cause: 0 detail cause: 0
*spamApTask1: Aug 13 00:50:45.229: 0c:68:03:d7:bf:90 Change State Event Response sent to 192.168.1.16:28193
*spamApTask1: Aug 13 00:50:45.229: 0c:68:03:d7:bf:90 CAPWAP State: Run
*spamApTask1: Aug 13 00:50:45.229: 0c:68:03:d7:bf:90 Sending the remaining config to AP 192.168.1.16:28193
*spamApTask1: Aug 13 00:50:45.229: 0c:68:03:d7:bf:90 Configuration update request for Init VAP-DATA for slot 0 sent to 192.168.1.16:28193
*spamApTask1: Aug 13 00:50:45.229: 0c:68:03:d7:bf:90 Configuration update request for Init VAP-DATA for slot 0 sent to 192.168.1.16:28193
*spamApTask1: Aug 13 00:50:45.230: 0c:68:03:d7:bf:90 Configuration update request for Init VAP-DATA for slot 1 sent to 192.168.1.16:28193
*spamApTask1: Aug 13 00:50:45.230: 0c:68:03:d7:bf:90 Configuration update request for Init VAP-DATA for slot 1 sent to 192.168.1.16:28193
*spamApTask1: Aug 13 00:50:45.230: 0c:68:03:d7:bf:90 Configuration update request for set/reset telnet message sent to 192.168.1.16:28193
*spamApTask1: Aug 13 00:50:45.230: 0c:68:03:d7:bf:90 Configuration update request for set/reset telnet message sent to 192.168.1.16:28193
*spamApTask1: Aug 13 00:50:45.230: 0c:68:03:d7:bf:90 Configuration update request for configuring association limit params sent to 192.168.1.16:28193
*spamApTask1: Aug 13 00:50:45.230: 0c:68:03:d7:bf:90 Configuration update request for GAS mgmt action frame rate limit params enable=0, interval=500, gasLimit=25, sent to 192.168.1.16:28193
*spamApTask1: Aug 13 00:50:45.230: 0c:68:03:d7:bf:90 Configuration update request for AutoImmune message sent to 192.168.1.16:28193
*spamApTask1: Aug 13 00:50:45.230: 0c:68:03:d7:bf:90 Configuration update request for Band Select Cfg sent to 192.168.1.16:28193
*spamApTask1: Aug 13 00:50:45.230: 0c:68:03:d7:bf:90 Configuration update request for HaConfig message sent to 192.168.1.16:28193
*spamApTask1: Aug 13 00:50:45.230: Ignoring Global LRAD MTU update existing 1485 mtu 1485
*apfReceiveTask: Aug 13 00:50:45.231: 0c:68:03:d7:bf:90 Received LWAPP Up event for AP 0c:68:03:d7:bf:90 slot 0!
*spamReceiveTask: Aug 13 00:50:45.231: 0c:68:03:d7:bf:90 Configuration update request for PHY payload sent to 192:168:1:16
*spamReceiveTask: Aug 13 00:50:45.231: 0c:68:03:d7:bf:90 Configuration update request for RrmInterferenceCtrl payload sent to 192:168:1:16
*spamReceiveTask: Aug 13 00:50:45.231: 0c:68:03:d7:bf:90 Configuration update request for RrmNeighbourCtrl payload sent to 192.168.1.16
*spamReceiveTask: Aug 13 00:50:45.232: 0c:68:03:d7:bf:90 Configuration update request for RrmReceiveCtrl payload sent to 192:168:1:16
*spamReceiveTask: Aug 13 00:50:45.232: 0c:68:03:d7:bf:90 Configuration update request for CcxRmMeas payload sent to 192.168.1.16
*spamReceiveTask: Aug 13 00:50:45.232: 0c:68:03:d7:bf:90 Configuration update for Addba sent to 192.168.1.16:28193
*spamApTask1: Aug 13 00:50:45.350: 0c:68:03:d7:bf:90 Change State Event Request from 192.168.1.16:28193
*spamApTask1: Aug 13 00:50:45.351: 0c:68:03:d7:bf:90 Radio state change for slot: 1 state: 2 cause: 0 detail cause: 0
*spamApTask1: Aug 13 00:50:45.351: 0c:68:03:d7:bf:90 Change State Event Response sent to 192.168.1.16:28193
*spamApTask1: Aug 13 00:50:45.351: 0c:68:03:d7:bf:90 CAPWAP State: Run
*spamApTask1: Aug 13 00:50:45.351: 0c:68:03:d7:bf:90 Sending the remaining config to AP 192.168.1.16:28193
*spamApTask1: Aug 13 00:50:45.351: Ignoring Global LRAD MTU update existing 1485 mtu 1485
*spamApTask1: Aug 13 00:50:45.351: 0c:68:03:d7:bf:90 Configuration Update Response from 192.168.1.16:28193
*apfReceiveTask: Aug 13 00:50:45.352: 0c:68:03:d7:bf:90 Received LWAPP Up event for AP 0c:68:03:d7:bf:90 slot 1!
*spamReceiveTask: Aug 13 00:50:45.352: 0c:68:03:d7:bf:90 Configuration update request for PHY payload sent to 192:168:1:16
*spamReceiveTask: Aug 13 00:50:45.352: 0c:68:03:d7:bf:90 Configuration update request for RrmInterferenceCtrl payload sent to 192:168:1:16
*spamReceiveTask: Aug 13 00:50:45.352: 0c:68:03:d7:bf:90 Configuration update request for RrmNeighbourCtrl payload sent to 192.168.1.16
*spamReceiveTask: Aug 13 00:50:45.352: 0c:68:03:d7:bf:90 Configuration update request for RrmReceiveCtrl payload sent to 192:168:1:16
*spamReceiveTask: Aug 13 00:50:45.352: 0c:68:03:d7:bf:90 Configuration update request for CcxRmMeas payload sent to 192.168.1.16
*spamApTask1: Aug 13 00:50:45.372: 0c:68:03:d7:bf:90 Change State Event Request from 192.168.1.16:28193
*spamApTask1: Aug 13 00:50:45.372: 0c:68:03:d7:bf:90 Change State Event Response sent to 192.168.1.16:28193
*spamApTask1: Aug 13 00:50:45.372: 0c:68:03:d7:bf:90 CAPWAP State: Run
*spamApTask1: Aug 13 00:50:45.372: 0c:68:03:d7:bf:90 Sending the remaining config to AP 192.168.1.16:28193
*spamApTask1: Aug 13 00:50:45.372: Ignoring Global LRAD MTU update existing 1485 mtu 1485
*spamApTask1: Aug 13 00:50:45.372: 0c:68:03:d7:bf:90 Configuration Update Response from 192.168.1.16:28193
*spamApTask1: Aug 13 00:50:45.373: 0c:68:03:d7:bf:90 WTP Event Request from 192.168.1.16:28193
*spamApTask1: Aug 13 00:50:45.373: 0c:68:03:d7:bf:90 WTP Event Response sent to 192.168.1.16:28193
*spamApTask1: Aug 13 00:50:45.374: 0c:68:03:d7:bf:90 Configuration Update Response from 192.168.1.16:28193
*spamApTask1: Aug 13 00:50:45.375: 0c:68:03:d7:bf:90 WTP Event Request from 192.168.1.16:28193
*spamApTask1: Aug 13 00:50:45.375: 0c:68:03:d7:bf:90 WTP Event Response sent to 192.168.1.16:28193
*spamApTask1: Aug 13 00:50:45.376: 0c:68:03:d7:bf:90 Configuration Update Response from 192.168.1.16:28193
*spamApTask1: Aug 13 00:50:45.376: 0c:68:03:d7:bf:90 WTP Event Request from 192.168.1.16:28193
*spamApTask1: Aug 13 00:50:45.377: 0c:68:03:d7:bf:90 WTP Event Response sent to 192.168.1.16:28193
*spamApTask1: Aug 13 00:50:45.377: 0c:68:03:d7:bf:90 Configuration Update Response from 192.168.1.16:28193
*spamApTask1: Aug 13 00:50:45.378: 0c:68:03:d7:bf:90 WTP Event Request from 192.168.1.16:28193
*spamApTask1: Aug 13 00:50:45.378: 0c:68:03:d7:bf:90 WTP Event Response sent to 192.168.1.16:28193
*spamApTask1: Aug 13 00:50:45.445: 0c:68:03:d7:bf:90 Configuration Update Response from 192.168.1.16:28193
*spamApTask1: Aug 13 00:50:45.445: 0c:68:03:d7:bf:90 WTP Event Request from 192.168.1.16:28193
*spamApTask1: Aug 13 00:50:45.445: 0c:68:03:d7:bf:90 Updated Link Latency control for AP 0c:68:03:d7:bf:90
*spamApTask1: Aug 13 00:50:45.445: 0c:68:03:d7:bf:90 WTP Event Response sent to 192.168.1.16:28193
*spamApTask1: Aug 13 00:50:45.506: 0c:68:03:d7:bf:90 Configuration Update Response from 192.168.1.16:28193
*spamApTask1: Aug 13 00:50:45.508: 0c:68:03:d7:bf:90 WTP Event Request from 192.168.1.16:28193
*spamApTask1: Aug 13 00:50:45.509: 0c:68:03:d7:bf:90 WTP Event Response sent to 192.168.1.16:28193
*spamApTask1: Aug 13 00:50:45.509: 0c:68:03:d7:bf:90 Configuration Update Response from 192.168.1.16:28193
*spamApTask1: Aug 13 00:50:45.510: 0c:68:03:d7:bf:90 WTP Event Request from 192.168.1.16:28193
*spamApTask1: Aug 13 00:50:45.510: 0c:68:03:d7:bf:90 WTP Event Response sent to 192.168.1.16:28193
*spamApTask1: Aug 13 00:50:45.510: 0c:68:03:d7:bf:90 Configuration Update Response from 192.168.1.16:28193
*spamApTask1: Aug 13 00:50:45.511: 0c:68:03:d7:bf:90 WTP Event Request from 192.168.1.16:28193
*spamApTask1: Aug 13 00:50:45.512: 0c:68:03:d7:bf:90 Configuration Update Response from 192.168.1.16:28193
*spamApTask1: Aug 13 00:50:45.515: 0c:68:03:d7:bf:90 Configuration Update Response from 192.168.1.16:28193
*spamApTask1: Aug 13 00:50:45.516: 0c:68:03:d7:bf:90 Configuration Update Response from 192.168.1.16:28193
*spamApTask1: Aug 13 00:50:45.517: 0c:68:03:d7:bf:90 Configuration Update Response from 192.168.1.16:28193
*spamApTask1: Aug 13 00:50:45.519: 0c:68:03:d7:bf:90 Configuration Update Response from 192.168.1.16:28193
*spamApTask1: Aug 13 00:50:45.520: 0c:68:03:d7:bf:90 Configuration Update Response from 192.168.1.16:28193
*spamApTask1: Aug 13 00:50:45.524: 0c:68:03:d7:bf:90 Configuration Update Response from 192.168.1.16:28193
*spamApTask1: Aug 13 00:50:45.525: 0c:68:03:d7:bf:90 Configuration Update Response from 192.168.1.16:28193
*spamApTask1: Aug 13 00:50:45.526: 0c:68:03:d7:bf:90 Configuration Update Response from 192.168.1.16:28193
*spamApTask1: Aug 13 00:50:45.584: 0c:68:03:d7:bf:90 Configuration Update Response from 192.168.1.16:28193
*spamApTask1: Aug 13 00:50:45.585: 0c:68:03:d7:bf:90 Configuration Update Response from 192.168.1.16:28193
*spamApTask1: Aug 13 00:50:45.586: 0c:68:03:d7:bf:90 Configuration Update Response from 192.168.1.16:28193
*spamApTask1: Aug 13 00:50:45.587: 0c:68:03:d7:bf:90 Configuration Update Response from 192.168.1.16:28193
*spamApTask1: Aug 13 00:50:45.588: 0c:68:03:d7:bf:90 Configuration Update Response from 192.168.1.16:28193
*spamApTask1: Aug 13 00:50:45.588: 0c:68:03:d7:bf:90 Configuration Update Response from 192.168.1.16:28193
*spamApTask1: Aug 13 00:50:45.589: 0c:68:03:d7:bf:90 Configuration Update Response from 192.168.1.16:28193
*spamApTask1: Aug 13 00:50:45.590: 0c:68:03:d7:bf:90 Configuration Update Response from 192.168.1.16:28193
*spamApTask1: Aug 13 00:50:45.591: 0c:68:03:d7:bf:90 Configuration Update Response from 192.168.1.16:28193
*spamApTask1: Aug 13 00:50:45.592: 0c:68:03:d7:bf:90 Configuration Update Response from 192.168.1.16:28193
*spamApTask1: Aug 13 00:50:45.593: 0c:68:03:d7:bf:90 Configuration Update Response from 192.168.1.16:28193
*spamApTask1: Aug 13 00:50:45.593: 0c:68:03:d7:bf:90 Configuration Update Response from 192.168.1.16:28193
*spamApTask1: Aug 13 00:50:48.508: 0c:68:03:d7:bf:90 Duplicate sequence number in request message
*spamApTask1: Aug 13 00:50:48.509: 0c:68:03:d7:bf:90 WTP Event Request from 192.168.1.16:28193
*spamApTask1: Aug 13 00:50:48.509: 0c:68:03:d7:bf:90 WTP Event Response sent to 192.168.1.16:28193
*spamApTask1: Aug 13 00:50:48.510: 0c:68:03:d7:bf:90 WTP Event Request from 192.168.1.16:28193
*spamApTask1: Aug 13 00:50:48.510: 0c:68:03:d7:bf:90 WTP Event Response sent to 192.168.1.16:28193
*spamApTask1: Aug 13 00:50:48.511: 0c:68:03:d7:bf:90 WTP Event Request from 192.168.1.16:28193
*spamApTask1: Aug 13 00:50:48.511: 0c:68:03:d7:bf:90 WTP Event Response sent to 192.168.1.16:28193
*spamApTask1: Aug 13 00:50:48.512: 0c:68:03:d7:bf:90 WTP Event Request from 192.168.1.16:28193
*spamApTask1: Aug 13 00:50:48.513: 0c:68:03:d7:bf:90 WTP Event Response sent to 192.168.1.16:28193
*spamApTask1: Aug 13 00:50:48.514: 0c:68:03:d7:bf:90 Change State Event Request from 192.168.1.16:28193
*spamApTask1: Aug 13 00:50:48.514: 0c:68:03:d7:bf:90 Change State Event Response sent to 192.168.1.16:28193
*spamApTask1: Aug 13 00:50:48.514: 0c:68:03:d7:bf:90 CAPWAP State: Run
*spamApTask1: Aug 13 00:50:48.515: 0c:68:03:d7:bf:90 Sending the remaining config to AP 192.168.1.16:28193
*spamApTask1: Aug 13 00:50:48.516: Ignoring Global LRAD MTU update existing 1485 mtu 1485
*spamApTask1: Aug 13 00:50:48.516: 0c:68:03:d7:bf:90 Change State Event Request from 192.168.1.16:28193
*apfReceiveTask: Aug 13 00:50:48.517: 0c:68:03:d7:bf:90 Received LWAPP Down event for AP 0c:68:03:d7:bf:90 slot 1!
*spamApTask1: Aug 13 00:50:48.517: 0c:68:03:d7:bf:90 apfSpamProcessStateChangeInSpamContext: Down LWAPP event for AP 0c:68:03:d7:bf:90 slot 1
*spamApTask1: Aug 13 00:50:48.517: 0c:68:03:d7:bf:90 Radio state change for slot: 1 state: 1 cause: 0 detail cause: 37
*spamApTask1: Aug 13 00:50:48.519: 0c:68:03:d7:bf:90 Change State Event Response sent to 192.168.1.16:28193
*spamApTask1: Aug 13 00:50:48.519: 0c:68:03:d7:bf:90 CAPWAP State: Run
*spamApTask1: Aug 13 00:50:48.520: 0c:68:03:d7:bf:90 Sending the remaining config to AP 192.168.1.16:28193
*spamApTask1: Aug 13 00:50:48.520: Ignoring Global LRAD MTU update existing 1485 mtu 1485
*spamApTask1: Aug 13 00:50:48.520: 0c:68:03:d7:bf:90 Change State Event Request from 192.168.1.16:28193
*spamApTask1: Aug 13 00:50:48.520: 0c:68:03:d7:bf:90 Change State Event Response sent to 192.168.1.16:28193
*spamApTask1: Aug 13 00:50:48.520: 0c:68:03:d7:bf:90 CAPWAP State: Run
*spamApTask1: Aug 13 00:50:48.520: 0c:68:03:d7:bf:90 Sending the remaining config to AP 192.168.1.16:28193
*spamApTask1: Aug 13 00:50:48.520: Ignoring Global LRAD MTU update existing 1485 mtu 1485
*spamApTask1: Aug 13 00:50:48.523: 0c:68:03:d7:bf:90 WTP Event Request from 192.168.1.16:28193
*spamApTask1: Aug 13 00:50:48.523: 0c:68:03:d7:bf:90 WTP Event Response sent to 192.168.1.16:28193
*spamApTask1: Aug 13 00:50:48.524: 0c:68:03:d7:bf:90 Change State Event Request from 192.168.1.16:28193
*apfReceiveTask: Aug 13 00:50:48.525: 0c:68:03:d7:bf:90 Received LWAPP Up event for AP 0c:68:03:d7:bf:90 slot 1!
*spamApTask1: Aug 13 00:50:48.525: 0c:68:03:d7:bf:90 Radio state change for slot: 1 state: 2 cause: 0 detail cause: 37
*spamApTask1: Aug 13 00:50:48.527: 0c:68:03:d7:bf:90 Change State Event Response sent to 192.168.1.16:28193
*spamApTask1: Aug 13 00:50:48.527: 0c:68:03:d7:bf:90 CAPWAP State: Run
*spamApTask1: Aug 13 00:50:48.528: 0c:68:03:d7:bf:90 Sending the remaining config to AP 192.168.1.16:28193
*spamApTask1: Aug 13 00:50:48.528: Ignoring Global LRAD MTU update existing 1485 mtu 1485
*spamApTask1: Aug 13 00:50:48.528: 0c:68:03:d7:bf:90 Change State Event Request from 192.168.1.16:28193
*apfReceiveTask: Aug 13 00:50:48.528: 0c:68:03:d7:bf:90 Received LWAPP Down event for AP 0c:68:03:d7:bf:90 slot 0!
*spamApTask1: Aug 13 00:50:48.528: 0c:68:03:d7:bf:90 apfSpamProcessStateChangeInSpamContext: Down LWAPP event for AP 0c:68:03:d7:bf:90 slot 0
*spamApTask1: Aug 13 00:50:48.528: 0c:68:03:d7:bf:90 Radio state change for slot: 0 state: 1 cause: 0 detail cause: 37
*spamApTask1: Aug 13 00:50:48.529: 0c:68:03:d7:bf:90 Change State Event Response sent to 192.168.1.16:28193
*spamApTask1: Aug 13 00:50:48.529: 0c:68:03:d7:bf:90 CAPWAP State: Run
*spamApTask1: Aug 13 00:50:48.529: 0c:68:03:d7:bf:90 Sending the remaining config to AP 192.168.1.16:28193
*spamApTask1: Aug 13 00:50:48.529: Ignoring Global LRAD MTU update existing 1485 mtu 1485
*spamApTask1: Aug 13 00:50:48.533: 0c:68:03:d7:bf:90 Change State Event Request from 192.168.1.16:28193
*spamApTask1: Aug 13 00:50:48.533: 0c:68:03:d7:bf:90 Change State Event Response sent to 192.168.1.16:28193
*spamApTask1: Aug 13 00:50:48.533: 0c:68:03:d7:bf:90 CAPWAP State: Run
*spamApTask1: Aug 13 00:50:48.533: 0c:68:03:d7:bf:90 Sending the remaining config to AP 192.168.1.16:28193
*spamApTask1: Aug 13 00:50:48.533: Ignoring Global LRAD MTU update existing 1485 mtu 1485
*spamApTask1: Aug 13 00:50:48.534: 0c:68:03:d7:bf:90 WTP Event Request from 192.168.1.16:28193
*spamApTask1: Aug 13 00:50:48.534: 0c:68:03:d7:bf:90 WTP Event Response sent to 192.168.1.16:28193
*spamApTask1: Aug 13 00:50:48.535: 0c:68:03:d7:bf:90 Change State Event Request from 192.168.1.16:28193
*apfReceiveTask: Aug 13 00:50:48.535: 0c:68:03:d7:bf:90 Received LWAPP Up event for AP 0c:68:03:d7:bf:90 slot 0!
*spamApTask1: Aug 13 00:50:48.535: 0c:68:03:d7:bf:90 Radio state change for slot: 0 state: 2 cause: 0 detail cause: 37
*spamApTask1: Aug 13 00:50:48.536: 0c:68:03:d7:bf:90 Change State Event Response sent to 192.168.1.16:28193
*spamApTask1: Aug 13 00:50:48.536: 0c:68:03:d7:bf:90 CAPWAP State: Run
*spamApTask1: Aug 13 00:50:48.536: 0c:68:03:d7:bf:90 Sending the remaining config to AP 192.168.1.16:28193
*spamApTask1: Aug 13 00:50:48.536: Ignoring Global LRAD MTU update existing 1485 mtu 1485
*apfMsConnTask_7: Aug 13 00:50:53.448: sending spamAddMobile aclName =
*spamApTask1: Aug 13 00:50:53.449: 0c:68:03:d7:bf:90 Successful transmission of LWAPP Add-Mobile to AP 0c:68:03:d7:bf:90
*spamApTask1: Aug 13 00:50:53.451: 0c:68:03:d7:bf:90 Configuration Update Response from 192.168.1.16:28193
*spamApTask1: Aug 13 00:50:53.453: 0c:68:03:d7:bf:90 Configuration Update Response from 192.168.1.16:28193
(Cisco Controller) >debug capwap events disable
As long as the controller shows the AP with an appropriate IP address, you can assume that there is a working CAPWAP tunnel between the two. If clients are reporting problems with one SSID that they have in common, you should review the WLAN configuration on the controller to make sure it is bound to the correct controller interface and to the correct VLAN.
Another common issue is the AP's regulatory domain or country to select on the WLC. Here's a link for the AP and country compatibility matrix. You can change the country code on the WLC by going to Wireless > Country. I wasn't able to initially register my AIR-CAP2602I since the WLC country code is configured to US. I've checked the WLC syslogs and mentioned an invalid country code error for the AP (base radio MAC address 0c:68:03:d7:bf:90). I issued a show cdp neighbor detail on the switch and saw an -S on its platform. I searched for the AP-to-country compatibility matrix and you can set the country to SG Singapore on the WLC.
.597: %LWAPP-3-RD_ERR7: spam_lrad.c:11196 The system detects an invalid country code () for AP 0c:68:03:d7:bf:90
*spamApTask2: Aug 12 22:57:39.841: %CAPWAP-3-POST_DECODE_ERR: capwap_ac_sm.c:5957 Post decode processing failed for Config status from AP 0c:68:03:d7:bf:90
*spamApTask2: Aug 12 22:57:39.834: %LWAPP-3-RD_ERR4: capwap_ac_sm.c:3316 The system detects an invalid regulatory domain 802.11bg:-A 802.11a:-AB for AP 0c:68:03:d7:bf:90
SW1#show cdp neighbor detail
-------------------------
Device ID: APf872.eaa6.e203
Entry address(es):
IP address: 192.168.1.16
IPv6 address: FE80::FA72:EAFF:FEA6:E203 (link-local)
Platform: cisco AIR-CAP2602I-S-K9, Capabilities: Trans-Bridge Source-Route-Bridge IGMP
Interface: FastEthernet0/14, Port ID (outgoing port): GigabitEthernet0
Holdtime : 166 sec
Version :
Cisco IOS Software, C2600 Software (AP3G2-K9W8-M), Version 15.3(3)JA8, RELEASE SOFTWARE (fc1)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2016 by Cisco Systems, Inc.
Compiled Fri 22-Apr-16 05:48 by prod_rel_team
advertisement version: 2
Duplex: full
Power drawn: 15.400 Watts
Power request id: 32785, Power management id: 3
Power request levels are:15400 13000 0 0 0
Management address(es):
IP address: 192.168.1.16
You can't directly change the country and all radio network (a/b/g/n/ac) must be disabled first. Go to Wireless > 802.11x/x/x > uncheck Enabled on the Network Status option > click Apply.
You can use the show ap join stats summary all and show ap join stats detailed <AP MAC address> commands on a WLC to verify the AP join status. The AP Status was Not Joined since I re-configured my wireless lab. I re-configured the new NTP server IP (which is my router).
kit-7869#clock set 22:18:00 1 Sep 2016
kit-7869#show clock
.22:18:02.699 UTC Thu Sep 1 2016
The AP Status went to Joined and it registered (REG) to the WLC.
Verifying AP-to-Network Connectivity
If you do not find the AP joined to a controller, you will have to move your focus further away from the controller and onto the AP and its wired connection Before an AP can boot up and operate correctly, it must have a power source. Most likely, an AP gets its power from the access layer switch as Power over Ethernet (PoE) over the Ethernet cabling. The more radios an AP supports, the more power it can consume.
Therefore, different AP models can require different amounts of power. You should verify the minimum PoE requirements of an AP and compare that with the PoE capability of the switch The 802.3af standard specifies that a PoE switch can provide up to 15.4 watts to a PoE device. Switch ports using the 802.3at standard can offer up to 30 watts PoE on an interface. When you look for the AP power requirements, be sure that the required power includes all radios in operation.
Once the AP has sufficient power, does it have an IP address? Without the help of a controller, you might have to connect to the AP console and watch the logging information scroll by as the AP tries to boot, get an address, and find a controller to join. You can also query the DHCP server to see whether the AP has an active address lease. If it is not able to get an address from a DHCP server, check the address scope on the server to ensure that the address space is not exhausted.
Tip: To connect to the CLI of an AP, you need to enter some credentials. By default, log in with username Cisco and password Cisco. The default enable secret password is also Cisco.
If the AP is having trouble joining a controller, verify that the switch port configuration where the AP is connected. A lightweight AP needs only a single VLAN to support the CAPWAP tunnel. All WLANs are transported over the tunnel without the need for separate VLANs. In contrast, an autonomous AP has no CAPWAP tunnel, so it needs a trunk link that can carry individual WLANs over VLANs.
Lightweight AP (Access Link)
interface gigabitethernet1/0/1
switchport // NEED TO ISSUE THIS ON AP CONNECTED TO WCM (3650/3850)
switchport access vlan 100
switchport mode access
spanning-tree portfast
no shutdown
Autonomous AP (Trunk Link)
interface gigabitethernet1/0/1
switchport
switchport trunk allowed vlan 100,101,102,103
switchport trunk native vlan 100
switchport trunk encapsulation dot1q
switchport mode trunk
no shutdown
Checking the RF Environment
To investigate problems that could involve things like 802.11 traffic, client roaming, RF interference, or co-channel or adjacent channel interference, you might need to leverage some third-party tools. Wi-Fi scanning tools are more useful for quick scans and walkthrough surveys of an area, to see all of the active APs and their channel use. Typical examples are MetaGeek inSSIDer Office, Android Wifi Analyzer, and Fluke AirMagnet WiFi Analyzer,
Here's what inSSIDer looks like and the wireless network (SSID) around my house. You could also narrow down on which radio band (2.4 GHz or 5G Hz) to be displayed.
