Wireless Controller 4402 Crash

Unanswered Question
Feb 4th, 2009
User Badges:


I will make an abbreviation report about my case. My WLC 4402 was running version. There are 18 access point work with local. It's work fine.

To a new project, we will add a access point 1522 and others 1242 to extend the range to a small building using mesh indoor (enterprise mesh).

To make this I read that I need use 5.2 version on WLC. So, I upgrade the WLC (locally) to release 4-2-176-0 and It's work fine (I don't install the new access points yet).

After, I upgrade the WLC to release 5-2-157-0 and install a 5-2-157-0-ER, according to document release. After reboot of new release 5.2, the WLC begin crash and reboot.

I make a downgrade to 4-2-176-0 because my client needed to work, and it's work fine.

In attached is the “tech-support” of Controller.

More one information! I too have a WCS that was with release and I upgrade to 5.2.110, before upgrade the controller.

Sorry, because my English is not so good.



  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Anonymous (not verified) Tue, 02/10/2009 - 15:33
User Badges:

If you downgrade from one release to another, you may lose the configuration from your current release. The workaround is to reload the previous controller configuration files saved on the backup server or to reconfigure the controller.

Before upgrading your controller to software release 5.2 in a mesh network, check the boot variable setting before updating the boot. If the boot system image is visible, then no boot variable update is required. If the boot system image is missing, then you must update the boot variable. Refer the below URL for more information on how to check boot variable setting.



This Discussion



Trending Topics: Other Wireless Mobility

client could not be authenticated
Network Analysis Module (NAM) Products
Cisco 6500 nam
reason 440 driver failure
Cisco password cracker
Cisco Wireless mode