4402 Upgraded to 5.0.148.0 & my APs(1200) are rebooting

[larry.milliken]

I upgraded from v4.0.217.0..the APs upgraded to that version..once i upgraded the controller to v5.0.148, the APs(1200s) are in a state of constant rebooting & won't upgrade.

[Andrew.Prescott]

Can you get any debug info from the controler also can you get a console connection into one of the re-booting APs and record the error messages.

[larry.milliken]

i cannot console into to the APs

[Rob Huffman]

Hi Larry,

It sounds like you may be hitting this Level 1 (Catastrophic) bug first found in 5.0.148.0

CSCso93216 Bug Details

LWAPP APs crash

Symptom:

LWAPP APs crashes many times a day.

Conditions:

Happens to WLC running 005.000(148.000) and all the lwapp APs associated to the WLC e.g. it happens in C1240 Software (C1240-K9W8-M), Version 12.4(13d)JA, and C1130 Software (C1130-K9W8-M), Version 12.4(13d)JA

Workaround:

reboot each AP

Further Problem Description:

This is an AP crash. The AP crashes and then reboots. The AP reboot is hitting the bug CSCsm70189. Status

Open

Severity

1 - catastrophic

Last Modified

In Last month

Product

Cisco 4400 Series Wireless LAN Controllers

Technology

1st Found-In

5.0(148.0)

CSCsm70189 Bug Details

Access Point reboots continuously

Symptom:

AP will crashes as soon as IOS boots before the "Press RETURN to get started."

prompt can be seen on the console.

Conditions:

This should only happen on 124-13d.JA images.

Workaround:

Power cycle the AP.

Further Problem Description:

The problem is triggered by an crash. If the AP crashes for other reason, it will be

stuck in this state and refuse to boot up. The only way to clear the problem is to

power cycle the AP. If the AP is rebooted normally, it should not encounter this

issue. Only if the AP crashes due to another reason will the AP be stuck in this

endless crash state. Status

Fixed

Severity

2 - severe

Last Modified

In Last month

Product

Cisco 4400 Series Wireless LAN Controllers

Technology

1st Found-In

5.1(53.0)

5.0(148.0)

Fixed-In

12.4(13d)JA0.20080302

Related Bug Information LWAPP AP1130 in tight crash loop

Symptom: An access point may get into a condition where it crashes continuously immediately after reloading. The console log will show messages similar to the following: Unexpected exception to CPUvector 2000, PC = 0x167764 , LR = 0x167758 -Traceback= 0x167764 0x1A3E04 0x55540 0x55A50 0x1A0CD0 Conditions: AP running in LWAPP mode, with a controller running 5.0.148.0 Workaround: Configure the boot loader to boot the recovery image: ap: set BOOT flash:/c1130-rcvk9w8-mx/c1130-rcvk9w8-mx ap: boot Let the AP join the controller and re-download the 12.4(13d)JA image. When it rejoins the controller, it should be OK. If not, then downgrade the controller and repeat the process.

Hope this helps! Sorry man!

Rob

[larry.milliken]

I have power-cycled the APs & still no joy..

[ericgarnel]

Can you roll back to 4.2.112 or 4.2.130?

Are there features in 5.x that you need?

[Rob Huffman]

Hi Larry,

I'm very sorry to hear that (this is a real bummer). Have you opened a case with Tac?

The other recommendation from the "workaround";

"When it rejoins the controller, it should be OK. If not, then downgrade the controller and repeat the process."

Hope this helps! I know this is not what you wanted to hear.

Rob

[larry.milliken]

i rolled back the controller to v4.2.130, when i look at the APs they did not update..when i put in the primary controller info on the AP & 'apply', the AP disappears (im assuming its rebooting)..about 1 min later it comes back with the primary controller info blank

[Rob Huffman]

Hi Larry,

You may have to try rolling back to 4.0.217 (the last working release)

I was looking at these release notes;

Upgrade Path to Controller Software Release 5.0.148.0

3.2.78.0 or later 3.2 release

Upgrade to a 4.1 release before upgrading to 5.0.148.0.

4.0.155.5 or later 4.0 release

Upgrade to a 4.1 or 4.2 release before upgrading to 5.0.148.0

4.1.171.0 or later 4.1 release

You can upgrade directly to 5.0.148.0.

4.2.61.0 or later 4.2 release

You can upgrade directly to 5.0.148.0.

http://www.cisco.com/en/US/docs/wireless/controller/release/notes/crn501480.html#wp233853

Did you ever open a Tac Case?

Rob

[dennischolmes]

Open a TAC case. This is a known issue with certain code releases. For those of you running later versions of 4.2 and 5x please note that there is also a bug floating around on WLANs configured for Platinum QoS. In platinum your voice packets should be tagged priority 6 when they leave the AP. In some cases they are tagged 0 for best effort. This usually won't effect Cisco phones due to the SCCP being so lean. For SIP phones however, if the AP is under a load, the result could be one way communication with the SIP based phone. See service request SR 606360283 for details. I still do not suggest 5x code to customers.

[larry.milliken]

Thanks to everyone for their help..I will open a TAC case..FYI, the most stable version for me is 4.0.219

[Rob Huffman]

Hi Larry,

You are most welcome :) Best of luck with this recovery. I hope things smooth out a bit for you here.

Let us know,

Rob

[larry.milliken]

Found the problem....

I found this info on 'Release Notes for Cisco Wireless Controller & LWAP v4.1.171.0

Our APs are AS1200s..The latest working version that i was able to upgrade to is v4.0.219.0, the next version after that is 4.1.171.0.

Whenever i attempted to upgrade beyond that, the controller upgrades fine, but all the APs just continuously reboot..

** Other Changes

These additional changes are applicable to controller software release 4.1.171.0:

•The Airespace AS1200 is not supported for use with controller software release 4.1.171.0. The Airespace AS1200 (not to be confused with the Cisco Aironet AP1200) was never sold by Cisco and predates Cisco's acquisition of Airespace. If you attempt to connect an Airespace AS1200 to a controller running this software, the access point reboots continuously.

Thanks..

[dennischolmes]

oops a bunch of us should have seen that. our bad. AS1200s are early models of the Cisco 1000 series and the 1000 series are not supported in 5x code.