Nick Jefferson
asked on
2504 WLC Code Update - WPA2 Vulnerability
Hi there,
I have a 2504 WLC at a remote site overseas currently on code 8.3.121.4. I need to update the code on it due to the KRACK vulnerability, but wasn't sure what the best route was to go on this. Cisco's suggested release is 8.2.166.0 (ED), but I'm hesitant to downgrade the code as I've heard some horror stories (losing configs, etc.) and I don't have an onsite resource there in case things to to hell. Cisco TACs recommended 8.3 release is 8.3.133.0... would I be better off just upgrading to that version instead? Would that be safer for a remote update?
Any input is appreciated, thanks!
I have a 2504 WLC at a remote site overseas currently on code 8.3.121.4. I need to update the code on it due to the KRACK vulnerability, but wasn't sure what the best route was to go on this. Cisco's suggested release is 8.2.166.0 (ED), but I'm hesitant to downgrade the code as I've heard some horror stories (losing configs, etc.) and I don't have an onsite resource there in case things to to hell. Cisco TACs recommended 8.3 release is 8.3.133.0... would I be better off just upgrading to that version instead? Would that be safer for a remote update?
Any input is appreciated, thanks!
should you be too scared to act remotely and downgrading, you may as well want to wait for Cisco to release a new "Suggested" firmware which you will upgrade (instead of downgrading).
max
max
ASKER
Yeah, unfortunately I can't really wait on suggested update that's an upgrade. Thanks for the input.
No don't go down. Go with the latest version in the same train or go up to 8.5.
Well,
I have done a few downgrades in the past, due to legacy access points that customers wanted to keep using and not compatible with firmware on board, and it went all fine. Of course we had less functionalities, but everything worked out fine: downgrade was processed at the same manner of upgrade, from wlc point of view.
max
I have done a few downgrades in the past, due to legacy access points that customers wanted to keep using and not compatible with firmware on board, and it went all fine. Of course we had less functionalities, but everything worked out fine: downgrade was processed at the same manner of upgrade, from wlc point of view.
max
Fair enough, but you could introduce problems which were fixed in later code, for example. Also you may lose support, for the older version, quicker.
It's far safer to go up instead of down where Cisco WLC code is concerned.
It's far safer to go up instead of down where Cisco WLC code is concerned.
This question needs an answer!
Become an EE member today
7 DAY FREE TRIALMembers can start a 7-Day Free trial then enjoy unlimited access to the platform.
View membership options
or
Learn why we charge membership fees
We get it - no one likes a content blocker. Take one extra minute and find out why we block content.
I'd go with suggested 8.2.166.0 (see attached image)
The worst you should expect is some functionality that does not work well after downgrade, but I believe the wlc will start and be functional.
good luck anyway
max