This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
- Extreme Networks
- Community List
- Wireless
- ExtremeWireless (WiNG)
- Clustered NX9600 and NX5500 Upgrade from 5.8 to 7....
Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
Clustered NX9600 and NX5500 Upgrade from 5.8 to 7.4.0.2
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
10-11-2020 01:56 AM
Hello All
I have 2 cluster NX5500 and NX9600. I need to upgrade them from Wing 5.8 to 7.4.0.2.
I have couple of questions if anyone could help .
- What is the upgrade path from 5.8 to 7.4.0.2 . Should I upgrade to 7.1.0 then 7.4.0.2 ?
- what is the best way to do cluster upgrade ? should I do standby first reboot and then primary ?
- All our APs are AP-8533 and has code 5.8. Will all AP upgraded to 7.4.0.2 directly after I upgrade the controller ? This is a new deployment so Will it be a problem after controllers upgraded to 7.4.0.2 or I will able to upgrade the APs from controllers directly from 5.8 to 7.4.0.2?
Thanks
Salaque
Solved! Go to Solution.
1 ACCEPTED SOLUTION
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
10-12-2020 03:38 PM
Salaque,
- According to the Release Notes, for the 8533 APs, the upgrade path to 7.4.x would require the 8533’s first be running 5.8.4 and newer.
- For upgrading the cluster, I don’t believe that there is an official recommendation on the upgrade order. If the APs do not need an configuration changes and you want to minimize the amount of traffic flow between the APs and controller cluster, you could just first upgrade the Secondary, disconnect the Secondary from the network, upgrade the Primary controller, and then reconnect the Secondary again...and ensure that the controller cluster rebuilds.
- You could also upgrade the Primary first - which would then cause the AP’s adoptions to fail-over to the Secondary controller. Then upgrade the Secondary, which by default will cause the APs to return back to the Primary.
- You could upgrade the Secondary first. Then upgrade the Primary which will briefly cause the APs to fail over to the Secondary while the Primary is rebooting. Once the Primary is rebooted, the cluster should reform and the APs will return to the Primary.
- Automatic upgrade of APs by controllers has been disabled in WiNG, so after an upgrade from v5.8.4 to 7.4.x, you will have to start an AP upgrade via the controller. According to the Release Notes, you should be able to upgrade directly from v5.8.4 to 7.4.x.
1 REPLY 1
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
10-12-2020 03:38 PM
Salaque,
- According to the Release Notes, for the 8533 APs, the upgrade path to 7.4.x would require the 8533’s first be running 5.8.4 and newer.
- For upgrading the cluster, I don’t believe that there is an official recommendation on the upgrade order. If the APs do not need an configuration changes and you want to minimize the amount of traffic flow between the APs and controller cluster, you could just first upgrade the Secondary, disconnect the Secondary from the network, upgrade the Primary controller, and then reconnect the Secondary again...and ensure that the controller cluster rebuilds.
- You could also upgrade the Primary first - which would then cause the AP’s adoptions to fail-over to the Secondary controller. Then upgrade the Secondary, which by default will cause the APs to return back to the Primary.
- You could upgrade the Secondary first. Then upgrade the Primary which will briefly cause the APs to fail over to the Secondary while the Primary is rebooting. Once the Primary is rebooted, the cluster should reform and the APs will return to the Primary.
- Automatic upgrade of APs by controllers has been disabled in WiNG, so after an upgrade from v5.8.4 to 7.4.x, you will have to start an AP upgrade via the controller. According to the Release Notes, you should be able to upgrade directly from v5.8.4 to 7.4.x.
