03-28-2008 05:33 PM - edited 07-03-2021 03:36 PM
We upgraded our Wireless LAN Controllers from 3.2.78.4 > 3.2.195.10 > 4.1.185.0 > 4.2.99.0.
We are implementing Vocera and they are requiring that we degrade the Wireless LAN Controllers to 4.2.112.0. Is it possible to degrade without losing any configuration or having any complications?
03-28-2008 07:23 PM
Hi Michael,
You can Downgrade the WLC Release Version, but in this case I believe 4.2.112.0 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
http://www.cisco.com/en/US/docs/wireless/controller/4.1/configuration/guide/c41mfw.html
Cisco 4400 Series Wireless LAN Controllers Release Notes
http://www.cisco.com/en/US/products/ps6366/prod_release_notes_list.html
Hope this helps! Good luck with the Vocera, sounds like a pretty cool product :)
Rob
03-28-2008 08:44 PM
Ah yes! Sorry, it's been a long week with 12 hour shifts. Since we're upgrading from 4.2.99.0 to 4.2.112.0, should we worry about losing the configuration? I would think not, but it's better to ask. :)
What is the difference between the 4.2.112.0 and the 4.2.112.0 BOOT?
Thanks so much for you input!
03-29-2008 08:00 AM
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, 4.2.112.0 and 4.2.112.0 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 4.2.112.0 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 (4.2.112.0 ER.aes) ensures that the boot software modifications in all of the previous and current boot software ER.aes files are installed.
http://www.cisco.com/en/US/docs/wireless/controller/release/notes/crn421120.html
Hope this helps!
Rob
03-29-2008 10:34 AM
I just upgraded to 4.2.112 and no issues.
04-01-2008 08:05 AM
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?
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide