AIR-CAP2602I-E-K9 booting all the time / crashes with "Unexpected exception to CPU:"

[Erich Schommarz]

Hello Together

I need a second opinion to a issue I'm facing actual at a customer. We have one access point AIR-CAP2602I-E-K9 which boots, gets ip, joins controller but short after that crashes with a Unexpected exception to CPU and reboots.

Anybody else had already once such a issue? Do you think more a software issue or hardware issue?

Enclosed partial part of the log which ends with a crash. Complete output see attachement.

Thanks for any feedback on this topic.

Erich

Log Output:

Mar  1 00:01:03.267: Logging LWAPP message to 10.0.10.116.
 
*Mar  1 00:01:11.947: %CDP_PD-4-POWER_OK: Full power - NEGOTIATED inline power source
*Mar  1 00:01:13.047: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to up
*Mar  1 00:01:14.047: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to up
*Mar  1 00:01:14.143: %LINK-6-UPDOWN: Interface Dot11Radio1, changed state to up
*Mar  1 00:01:15.143: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio1, changed state to up
*Mar  1 00:01:19.295: %DHCP-6-ADDRESS_ASSIGN: Interface BVI1 assigned DHCP address 10.0.50.75, mask 255.255.255.0, hostname AP885a.92c0.c82f
 
Translating "CISCO-CAPWAP-CONTROLLER.zis.local"...domain server (10.0.10.123) [OK]
 
*Mar  1 00:01:29.251: %CAPWAP-3-ERRORLOG: Did not get log server settings from DHCP.
*Mar  1 00:01:39.251: %CAPWAP-3-ERRORLOG: Go join a capwap controller
*Sep 30 11:54:23.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 10.0.10.7 peer_port: 5246
*Sep 30 11:54:23.471: %CAPWAP-5-DTLSREQSUCC: DTLS connection created sucessfully peer_ip: 10.0.10.7 peer_port: 5246
*Sep 30 11:54:23.471: %CAPWAP-5-SENDJOIN: sending Join Request to 10.0.10.7
*Sep 30 11:54:28.471: %CAPWAP-5-SENDJOIN: sending Join Request to 10.0.10.7
*Sep 30 11:54:28.931: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to down
*Sep 30 11:54:29.007: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset
*Sep 30 11:54:29.083: %CAPWAP-5-JOINEDCONTROLLER: AP has joined controller WAD_5508_C302_01
*Sep 30 11:54:29.155: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to up
*Sep 30 11:54:29.311: %WIDS-6-ENABLED: IDS Signature is loaded and enabled
*Sep 30 11:54:29.383: %CAPWAP-3-ERRORLOG: Received a upload request from controller for type 1
 
*Sep 30 11:54:29.931: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to down
*Sep 30 11:54:30.043: %LINK-6-UPDOWN: Interface Dot11Radio1, changed state to down
*Sep 30 11:54:30.051: %LINK-5-CHANGED: Interface Dot11Radio1, changed state to reset
*Sep 30 11:54:30.155: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio1, changed state to down
*Sep 30 11:54:31.031: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to up
*Sep 30 11:54:31.075: %DOT11-6-DFS_SCAN_START: DFS: Scanning frequency 5280 MHz for 60 seconds.
*Sep 30 11:54:31.079: %LINK-6-UPDOWN: Interface Dot11Radio1, changed state to up
*Sep 30 11:54:31.091: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to down
*Sep 30 11:54:31.099: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset
*Sep 30 11:54:32.079: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio1, changed state to up
*Sep 30 11:54:32.091: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to down
*Sep 30 11:54:32.123: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to up
*Sep 30 11:54:32.819: %CAPWAP-3-ERRORLOG: capwap_data_upload_proc: copy flash:/crashinfo_20150930-115017-UTC to capwap:/crashinfo complete
*Sep 30 11:54:33.123: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to up
*Sep 30 11:54:58.799: %CLEANAIR-6-STATE: Slot 0 enabled
*Sep 30 11:55:00.579: %CLEANAIR-6-STATE: Slot 1 enabled
 
 11:55:20 UTC Wed Sep 30 2015: Unexpected exception to CPU: vector 200, PC = 0x12B7264 , LR = 0x12B7204
 
-Traceback= 0x12B7264z 0x12B7A48z 0x12B8714z 0x1ED921Cz 0x17FB3D0z 0x17FC844z 0x17FE118z 0x17D18BCz 0x143F330z 0x143AB6Cz 0x143AB6Cz 0x143F3F8z 0x1310378z 0x13101A8z 0x1312204z 0x1318CA8z
 
CPU Register Context:
MSR = 0x00029200  CR  = 0x28824024  CTR = 0x017F5C34  XER   = 0x20000000
R0  = 0x00000001  R1  = 0x05C5B668  R2  = 0x00010001  R3    = 0x00000002
R4  = 0x0326ED4C  R5  = 0x039A0000  R6  = 0xE0040000  R7    = 0x00029200
R8  = 0x03020000  R9  = 0x03650000  R10 = 0x00000000  R11   = 0x0000420E
R12 = 0x28824022  R13 = 0x2080F303  R14 = 0x00000000  R15   = 0x04260000
R16 = 0x761FCA4F  R17 = 0x03652E1C  R18 = 0x042E5980  R19   = 0x05EDEF18
R20 = 0x05FA02B4  R21 = 0x05EF02B4  R22 = 0x05EF02B4  R23   = 0x00000000
R24 = 0x00000050  R25 = 0x05FA02B4  R26 = 0x00000000  R27   = 0x0662A710
R28 = 0x00000002  R29 = 0x00000004  R30 = 0x00000002  R31   = 0x0662A5C0

[Leo Laohoo · Accepted solution]

Whether a SmartNet was purchased on the AP or not, it is still covered under Cisco Limited Lifetime Warranty.  My recommendation is to RMA the AP.

[Erich Schommarz]

Hi Leo

Thanks for the second opinion. LLW I know. But as a Partner I only want to RMA devices if really necessary.

It was also my first thought to do RMA and now I have also a second opinion and will proceed with that way.

Greetings and thanks for your recommendation

Erich.