02-01-2018 01:49 AM - edited 07-05-2021 08:11 AM
Hi All
I just realized that 8.5.120.0 has been released.
Release notes: https://www.cisco.com/c/en/us/td/docs/wireless/controller/release/notes/crn85mr2.html
What surprised me though, there is no upgrade path for 8.2 and older. Is this missing in the documentation or indeed correct?!?
Current Software Release |
Upgrade Path to 8.5.120.0 Software |
---|---|
8.3.x.0 |
You can upgrade directly to Release 8.5.120.0 |
8.4.100.0 |
You can upgrade directly to Release 8.5.120.0 |
That's it, the whole (current) table. There also aren't any notes for older releases.
02-01-2018 02:00 AM
02-01-2018 02:20 AM
02-13-2018 08:42 AM
I just have managed to sucessfully upgrade from version 8.2 to 8.5 and currrently i have no issues.
02-28-2018 11:16 AM
I'm looking into upgrading from 8.2.161 to 8.5.120 as well, I have one primary concern you may be able to answer..... I have ISE 2.1 for a RADIUS server, they recommend 2.2 or 2.3 in the release notes. Do you have ISE running in your environment and if so, is it 2.1? I'm just concerned with losing our 802.1x authentication over wireless if I upgrade to 8.5....
02-28-2018 11:41 PM
03-01-2018 05:33 AM
03-02-2018 03:08 PM
03-02-2018 03:54 PM - edited 03-02-2018 03:57 PM
@Freerk Terpstra wrote:
In case you decide to go ahead my advice would be to check out this link once a week to stay informed about new found issues.
There has been a strange "policy shift" in regards to Cisco documentation (including Bug IDs)h
For one, the Release Notes no longer lists down all the Open or Fixed Caveats. Not all Critical bugs are published in the Release Notes.
Next, the only way to find out what bugs are Open or Fixed is to use the temperimental Cisco Bug Toolkit or Cisco Bug Search Tool (or whatever it is called this month).
Finally, once you've zeroed in to the bug, it is not guarantee that 40% of the details in the bug are accurate or up-to-date. Recently, I've been observing that the information found in the Bug IDs are not really that accurate (or makes any sense) and never/rarely updated. The only thing that gets automatically updated is the amount of Support Cases that the bug get mentioned.
Now this isn't just happening in the wireless "silo" but it is widespread. I've seen this in LAN and WAN.
My recommendation to anyone reading this is this: If in doubt, raise a TAC Case.
(I understand that by doing so will tax TAC but I don't see any way out.)
03-04-2018 11:43 PM
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