Cisco Maintenance Releases - Degrading Wireless LAN Controller

Unanswered Question
Mar 28th, 2008

We upgraded our Wireless LAN Controllers from > > >

We are implementing Vocera and they are requiring that we degrade the Wireless LAN Controllers to Is it possible to degrade without losing any configuration or having any complications?

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Rob Huffman Fri, 03/28/2008 - 19:23

Hi Michael,

You can Downgrade the WLC Release Version, but in this case I believe is actually the newest release in the 4.2 train (just released March 17), if you do have to downgrade a WLC Version be careful of this note;

Caution: If you require a 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.

Managing Controller Software and Configurations

Cisco 4400 Series Wireless LAN Controllers Release Notes

Hope this helps! Good luck with the Vocera, sounds like a pretty cool product :)


djgizmo250 Fri, 03/28/2008 - 20:44

Ah yes! Sorry, it's been a long week with 12 hour shifts. Since we're upgrading from to, should we worry about losing the configuration? I would think not, but it's better to ask. :)

What is the difference between the and the BOOT?

Thanks so much for you input!

Rob Huffman Sat, 03/29/2008 - 08:00

Hi Michael,

No worries, I know the feeling ;-)

You should be fine in regards to losing the config (best to back it up just in case) With this upgrade you will require both files, and Boot. The Bootloader upgrade is required to mitigate the two bugs listed below;

Cisco requires you to install the Cisco Unified Wireless Network Controller Boot Software ER.aes file on the following controllers: 4400 series, Cisco WiSM, and Catalyst 3750G Wireless LAN Controller Switch. It is optional on other controller platforms. This file resolves CSCso00774 and CSCso02733 and is necessary to ensure proper operation of the controller. If you do not install the ER.aes file, your controller does not obtain the fixes for these two defects.


Note When you install the ER.aes file, a new bootloader file is also loaded. This is true for all controllers except the 2106 controller, for which the bootloader is not upgradable.



Note The ER .aes files are independent from the controller software files. You can run any controller software file with any ER.aes file. However, installing the latest boot software file ( ER.aes) ensures that the boot software modifications in all of the previous and current boot software ER.aes files are installed.

Hope this helps!


raun.williams Tue, 04/01/2008 - 08:05

This is off topic, but am curious if your a hospital deploying Vocera and what kind of issues your running into, or any one else for that matter. Vocera has been deployed here 8months, and my personal opinion is that it's a piece o'crap. We have a very dense AP deployment in our ED area to handle all of the mobile devices, and they all work fine. Vocera on the other hand doesn't seem to do to well. What badge are you starting with? B or B/G?


This Discussion



Trending Topics - Security & Network