Aironet 1210 an 1130s hang

[scoe]

Customer has about 30 Aironet 1210 and 1130 APs and WLSE. APs are version 12.3(7)JA1 and WLSE is 2.12. The APs randomly hang. It happens one at a time, perhaps one a day on average.

The switch that the AP is connected to seas the AP via CDP but there is no IP connectivity to the AP and wireless clients can't associate to it.

On the console it responds to commands and can see CDP neighbors.

A reboot fixes it.

Any idea anyone?

[s.jankowski]

not sure of the issue, check the following troubleshooting link and see if it helps :

http://cco-rtp-1.cisco.com/en/US/products/hw/wireless/ps458/products_tech_note09186a00800a86d7.shtml

[Aaron]

If you are having APs hanging/locking up/crashing in 12.3(7)JA or 7JA1, I would most definitely upgrade to 12.3(7)JA2. The earlier 7JA releases were prone to more than their share of such problems; we worked pretty hard on JA2 to get it stable.

[sethgarnar]

Aaron is right you should upgrade to 12.3-7JA2 I had alot of problems with AP's crashing and making corefiles on the flash filling it up and hanging the AP. Currently I have 230 1121/31 AP's running 12.3-7JA2 and havent encountered any issues. I suggest you also enable the creation of crashinfo files, that will give you a better idea of why your AP's are locking up.

[editora_redes]

hi!

I have been reading the messages, because I have the same problem, with my almost 10 AP's in my local network, I have this ios version 12.3-7JA1. But also another 20 AP in other cities with the same ios version but without the problem, only my AP's hangs and I have to reset them because they lost layer 3 connectiviy.

[rrrobinson]

I've seen the exact same thing....very frustrating. TAC was unable to provide a coherent explanation so we're testing out the 12.3(7)JA2 code. One of the bugfixes that JA2 addresses is master WDS AP lockups due to a memory leak. If you enable the WLSE to do threshold monitoring for the AP's, you will see the AP's memory utilization pass 80% about a day or two before they lockup.

Since I haven't had this version installed for very long, I'm not 100% certain that JA2 fixes this issue.

[fpiedrafit]

Yes, it's really frustrating! Something similar happens to us. We have about 60 accesspoints (1200/1300) with IOS 12.3(7)JA2 and WLSE version 2.15. 8 are roots and the other ones are repeaters. Some of them, those that support more associations and disassociations, puts down the radio interface ramdonly. The last entries in system log always says:

Jan 24 05:27:53.348: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to down

Jan 24 05:27:53.630: %DOT11-4-UPLINK_ESTABLISHED: Interface Dot11Radio0, Associated To AP F2BAR126 0012.431a.6890 [None]

Jan 24 05:27:53.632: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to up

Jan 24 05:28:00.317: %DOT11-4-UPLINK_DOWN: Interface Dot11Radio0, parent lost: Too many retries

Jan 24 05:28:00.322: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to down

Jan 24 05:28:00.465: %DOT11-4-UPLINK_ESTABLISHED: Interface Dot11Radio0, Associated To AP F2BAR089 0012.43f9.4150 [None]

Jan 24 05:28:00.467: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to up

Jan 24 05:28:02.234: %DOT11-6-ASSOC: Interface Dot11Radio0, Station F20W1404 000f.f84d.7fcb Reassociated KEY_MGMT[NONE]

Jan 24 05:28:03.534: %WLCCP_AP-6-INFRA: WLCCP Infrastructure Authenticated

Jan 24 05:28:11.943: %DOT11-4-MAXRETRIES: Packet to client 000f.f84d.7fcb reached max retries, removing the client

Jan 24 05:28:11.945: %DOT11-6-DISASSOC: Interface Dot11Radio0, Deauthenticating Station 000f.f84d.7fcb Reason: Previous authentication no longer valid

Jan 24 05:28:11.952: %DOT11-4-UPLINK_DOWN: Interface Dot11Radio0, parent lost: Too many retries

Jan 24 05:28:11.970: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to down

Sometimes crashinfo file is generated with similar text:

Jan 24 05:28:11.952: %DOT11-4-UPLINK_DOWN: Interface Dot11Radio0, parent lost: Too many retries

Jan 24 05:28:11.970: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to down

Unexpected exception to CPUvector 1100, PC = 662A68

-Traceback= 662A68 661510 6619C8 14606C

The accesspoints doesn't reboot theirself, they just stay with radio interface down until somebody reboots the accesspoint.

Any idea?

Thank you in advance.