Cisco Wireless: Troubleshooting Lightweight AP Connectivity Issues

I have been having an issue with a Cisco AP 2600 rebooting every time (sometimes after 30 minutes, other times after 1 – 2 hours ). Troubleshooting the error using debugs did not provide any good leads. Opened a Case with Cisco TAC, and they also could not see what the issue was. The only thing that we noticed was the traceback below but TAC informed me that he could not see any bugs for that.

Apr 23 10:24:46.707: %EVT-3-ERR_TRACE: Power Table corruption: Domain
-Traceback= 1450B40z 1815760z 17C0500z 17C07D4z 1B6C934z 1B6CBA0z 1B74714z 1B99BE0z 1AEC348z 1AA4298z 1AB9450z 1AD5824z 132B15Apr 23 10:24:46.907: %EVT-5-CFG: Slot1: tx power level 1

Another person with a similar issue regarding the Cisco 1600 AP and 5700 series controller (mine was the 5500 series) had opened a TAC case too but they could not find the issue. A simple reboot resolved the issue.

I had rebooted the Controller several times since the issue occurred so I was rather reluctant in doing it again know that it would not help. But, I said, lets just try that again.

So I reboot the WLC again and guess what, the AP has been up for the last 15 hours!!!


I know its too early to be happy, but thats record time. Will monitor it and update you 🙂


Useful debug commands on the controller – these were rather clean in my case

#debug mac <AP - mac:address>
#debug capwap events enable
#debug capwap error enable
#debug capwap detail enable
#debug capwap info enable
#debug dtls all enable

This AP command is the one that helped us catch the traceback

#show evtlog

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s