03-16-2015 04:51 AM - edited 07-05-2021 02:42 AM
Have 1142 LAP AP's installed in each floor, All AP in One specific Floor are rebooting. After reboot most AP are joining WLC but few are unable to Join WLC. Logs in WLC shows AP has Crashed due to
"Unexpected exception to CPUvector 2000, PC = 0x49DFE8 , LR = 0x49DFFC : Unexpected exception to CPUvector 2000, PC = 0x49DFE8 , LR = 0x49DFFC"
and
"Last AP disconnect details
- Reason for last AP connection failure.................... Data transfer message received from an unsupported AP
"
Would like to i) debug further for reason of AP reload ii) Reason for AP not joining WLC after reload /crash.
Is there way to collect AP debugs from WLC ? Any suggestion to prevent reloads from happening.
03-16-2015 02:01 PM
This is bug CSCtx92385, No workaround yet
03-16-2015 02:55 PM
This is bug CSCtx92385, No workaround yet
Saurav,
Whoever created updated the bug needs to review the accuracy of the content. Under the Details > Product it states AP is a 2700. Under Details > Known Affected Release it states "7.0(116.0)".
03-16-2015 02:03 PM
All AP in One specific Floor are rebooting.
Check the port and uplink configuration of the switch connected to the APs. Maybe they're in the wrong VLAN and can't get an IP address.
Is/Are the AP(s) getting a valid IP address prior to crashing?
03-17-2015 02:57 AM
AP's are getting valid IP address and joining WLC, Clients are successfully associated with AP. But at Random time AP Reboots/Crashes.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide