Cisco AP1200 core dump

Hi

I have just had a radio failure on one of our Cisco AIR-AP1231G-E-K9 access points. A reload fixed it but I would like to try and figure out what happened. Can anyone suggest what might be the problem? Here the log contents prior to the reload :-

ap0#sh logging Syslog logging: enabled (0 messages dropped, 3 messages rate-limited, 0 flushes, 0 overruns, xml disabled, filtering disabled) Console logging: level debugging, 1876 messages logged, xml disabled, filtering disabled Monitor logging: level debugging, 0 messages logged, xml disabled, filtering disabled Buffer logging: level debugging, 1878 messages logged, xml disabled, filtering disabled Logging Exception size (4096 bytes) Count and timestamp logging messages: disabled Trap logging: level informational, 981 message lines logged

Log Buffer (4096 bytes): OT11-7-AUTH_FAILED: Station 0012.f0cc.151a Authentication failed Nov 16

14:13:42.036: %DOT11-7-AUTH_FAILED: Station 0012.f0cc.151a Authentication failed Nov 16 14:30:43.553: %DOT11-6-ASSOC: Interface Dot11Radio0, Station 000c.f15e.5bab Associated KEY_MGMT[WPA] Nov 16 14:36:36.103: %DOT11-6-DISASSOC: Interface Dot11Radio0, Deauthenticating Station 000c.f15e.5bab Reason: Previous authentication no longer valid Nov 16 14:56:48.878: %DOT11-7-AUTH_FAILED: Station 0011.956c.e612 Authentication failed Nov 16 15:25:20.523: %DOT11-6-ASSOC: Interface Dot11Radio0, Station 000d.88fa.7605 Associated KEY_MGMT[NONE] Nov 16 15:25:48.659: %DOT11-4-MAXRETRIES: Packet to client 000d.88fa.7605 reached max retries, removing the client Nov 16 15:25:48.660: %DOT11-6-DISASSOC: Interface Dot11Radio0, Deauthenticating Station 000d.88fa.7605 Reason: Previous authentication no longer valid Nov 16 15:25:49.299: %DOT11-6-ASSOC: Interface Dot11Radio0, Station 000d.88fa.7605 Associated KEY_MGMT[NONE] Nov 16 15:25:53.600: %DOT11-4-MAXRETRIES: Packet to client 000d.88fa.7605 reached max retries, removing the client Nov 16 15:25:56.672: %DOT11-6-ASSOC: Interface Dot11Radio0, Station 000d.88fa.7605 Associated KEY_MGMT[NONE] Nov 16 15:28:29.843: %DOT11-4-MAXRETRIES: Packet to client 000d.88fa.7605 reached max retries, removing the client Nov 16 15:28:29.843: %DOT11-6-DISASSOC: Interface Dot11Radio0, Deauthenticating Station 000d.88fa.7605 Reason: Previous authentication no longer valid Nov 16 15:37:02.776: %DOT11-4-MAXRETRIES: Packet to client 0011.956c.e612 reached max retries, removing the client Nov 16 15:37:02.776: Client 0011.956c.e612 failed: reached maximum retries Nov 16 15:44:27.370: %DOT11-6-ASSOC: Interface Dot11Radio0, Station 0011.956c.e612 Associated KEY_MGMT[WPA] Nov 16 15:57:42.644: %DOT11-6-ASSOC: Interface Dot11Radio0, Station 0090.4bf4.8747 Associated KEY_MGMT[WPA] Nov 16 16:12:53.686: %DOT11-6-ASSOC: Interface Dot11Radio0, Station 0011.24a3.b8b1 Associated KEY_MGMT[WPA] Nov 16 16:45:10.273: %DOT11-7-AUTH_FAILED: Station 0014.a516.2207 Authentication failed Nov 16 17:15:27.888: %DOT11-6-DISASSOC: Interface Dot11Radio0, Deauthenticating Station 0011.24a3.b8b1 Reason: Previous authentication no longer valid Nov 16 17:15:58.436: %DOT11-7-AUTH_FAILED: Station 0011.24a3.b8b1 Authentication failed Nov 16 17:57:55.434: %DOT11-7-AUTH_FAILED: Station 0009.2d0d.bd66 Authentication failed Nov 16 17:58:14.182: %DOT11-6-ASSOC: Interface Dot11Radio0, Station 0009.2d0d.bd66 Associated KEY_MGMT[WPA] Nov 16 18:06:03.817: %DOT11-6-DISASSOC: Interface Dot11Radio0, Deauthenticating Station 0011.956c.e612 Reason: Disassociated because sending station is leavin Nov 16 18:12:03.641: *** Not encrypted dot1x packet from 0090.4bf4.8747 has been discarded Nov 16 18:12:29.391: %DOT11-6-DISASSOC: Interface Dot11Radio0, Deauthenticating Station 0090.4bf4.8747 Reason: Previous authentication no longer valid Nov 16 18:26:43.741: %DOT11-6-DISASSOC: Interface Dot11Radio0, Deauthenticating Station 0009.2d0d.bd66 Reason: Previous authentication no longer valid Nov 20 13:26:14.495: Writing radio coredump to 'flash:/r12_58012_6BE0_79903C43.rcore' Nov 20 13:26:29.484: Writing radio coredump to 'flash:/r12_58012_6BE0_7A74F3F1.rcore' Nov 20 13:26:34.500: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to down Nov 20 13:26:35.500: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to down Nov 20 13:26:36.099: %DOT11-2-RADIO_FAILED: Interface Dot11Radio0, failed - Driver transmit queue stuck -Traceback= 45F980 4621BC 45F3DC 158AA0 Nov 20 13:26:36.102: %DOT11-4-LOADING_RADIO: Interface Dot11Radio0, loading the radio firmware (flash:/c1200-k9w7-mx.123-7.JA1/5101.img) Nov 20 13:26:36.161: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset Nov 20 13:26:36.909: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to up Nov 20 13:26:37.909: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to up Nov 20 13:50:29.242: %DOT11-7-AUTH_FAILED: Station 0012.f0ef.12bd Authentication failed ap0#
Reply to
B Thompson
Loading thread data ...

Open a case with the Cisco TAC as your AP has logged a traceback which typically means an IOS bug.

Nov 20 13:26:36.099: %DOT11-2-RADIO_FAILED: Interface Dot11Radio0, failed - Driver transmit queue stuck -Traceback=

45F980 4621BC 45F3DC 158AA0 Nov 20 13:26:36.102: %DOT11-4-LOADING_RADIO: Interface Dot11Radio0, loading the radio firmware (flash:/c1200-k9w7-mx.123-7.JA1/5101.img)
Reply to
Merv

Hi

Thanks for that. Do we need to pay for a soupport contract or something to get access to the TAC area on the website? When I tried it just now I got the following message :-

Tools & Resources TAC Service Request Tool Invalid Login

  • Our records indicate that you do not have access to this tool. You can send e-mail to snipped-for-privacy@cisco.com to check the status of your Cisco.com profile.

Cheers

Ben

Reply to
B Thompson

You need a Smartnet support contract unless you have had the AP1200 for less than 3 months in which case you can call the TAC and give them the serial number.

ou would acquire the Smartnet contract from whomever sold you the AP1200..

Reply to
Merv

What Merv writes is correct.

A simple workaround is downgrading the IOS from 12.3(7)JA1 to 12.3(4)JA1 or 12.3(2)JA5. Both are known working stable, and are feature complete.

12.3(7)JA1 is still crashed very often (compared to earlier release which crashed from never to only very rare)
Reply to
Uli Link

Hi

Thanks for that. What about 12.3(7)JA instead of 12.3(7)JA1? Is there a difference between the JA and JA1 versions or is it just a revision number?

Cheers

Ben

Reply to
B Thompson

B Thompson schrieb:

Same features, (x)JA1 is the first bugfixing-only rebuild of (x)JA.

12.3(7)JA is even worse than 12.3(7)JA1 and deferred.
Reply to
Uli Link

JA , JA1 and now JA2 are maintenance releases of 12.3(7).

The release you are using is quite new. Whyare you using it? Was it the release shipped with the product or did you upgrade to get some particular feature...

I agree with Uli recommendation to downgrade to a known stable release.

Reply to
Merv

Cabling-Design.com Forums website is not affiliated with any of the manufacturers or service providers discussed here. All logos and trade names are the property of their respective owners.