It has a section with a title as "Upgrading from Cisco MSE Release 7.4.x to Cisco MSE 8.0.120 through 220.127.116.11". First, what the mean of this tile? The TAC thinks it indicating that the upgrading path is 7.4.x>8.0.120>18.104.22.168. But I don't agree. In the content of this section, it doesn't state if upgrading from 7.4.x to 22.214.171.124 directly is supported or not. The whole document didn't mention upgrading path for 7.6.x at all, can I assume every applies to 7.4.x applies to 7.6.x? Disappointed on the quality of the MSE 126.96.36.199 release notes.
I open a TAC case, the TAC told me that the upgrading path is: MSE 188.8.131.52>MSE 184.108.40.206>MSE 8.0.140.X>8.0.150.X. I feel the answer is not accurate.
Anybody know what is the correct path for upgrading MSE 220.127.116.11 to MSE 18.104.22.168?
Re: What is the correct MSE 7.6.x to 8.0.150.x upgrade path?
How I read it, you need to go to 22.214.171.124 first. If you have a virtual, why not just build a new instance and start from scratch. Upgrade doesn’t always work as expected, so don’t be shocked if you have to get TAC involved if you decide to upgrade.
I have a few AIR-CAP3502E-A-K9 access points that I want to change to Lightweight mode. I did a lot of researching and found that I needed the ap3g1-k9w7-tar.153-3.JAB.tar file or a similar version of it.I do have that file and I was able to upload ...
WLAN Poller provides functionality to:
Bulk data/debug collection from Controllers and APs. Execute the commands on regular intervals.
DFS statistics and debug collection
IOS AP Flash health check and memory
AP cert check with generating reports
My report tells you a simple viewpoint to understand the evolution of the wireless LAN from 1997 to the 2020s. You can also get basic knowledge on an uplink of Wi-Fi6, the latest IEEE 802.11ax standard. Data analysis results based on our experimental s...
WLAN controller newb here. A power outage took out my home network but upon return my two SSIDs came back and my three APs went blue... everything WiFi related was working as expected. Sometime later I logged into the WLAN Controller web-page to see I hav...