09-08-2021 09:47 PM
Hello,
We have a customer who is wanting us to upgrade their NX5500 to the new WiNG 7 version due to deploying some newer APs soon. I have a couple of questions regarding this upgrade.
Thank you!
Solved! Go to Solution.
09-09-2021 01:23 AM
Hi,
Here are the answers to your questions:
1- Your understanding is correct, the new firmware will only load after a controller reload/reboot. If it's a centralized/NOC type of deployment where controller is only used for mgmt., traffic is locally bridged, no tunneled data, no Captive Portal/Radius proxy/DHCP on the controller, then you can safely reload the controller even during the office hours since data and control planes are local to APs in that case. Otherwise,you should reload it after work hours.
2- The first and most important thing you must check is that all the AP models you are using have an upgrade path to WiNG7. If they do, you can first upgrade the controller, APs will stay adopted and functional with firmware mismatch. It depends on how the APs are deployed, if you have multiple RF-Domains you can upgrade APs by RF-Domains. There are few caveats when the APs are in firmware mismatch state:
a) No new configuration can be pushed to the APs while they are in firmware mismatch state.
b) You may experience issues with client auth if you are using the controller either as a Radius Server or a Captive Portal server.
3- It is not recommended to have both WiNG5 and WiNG7 APs on the same controller, and more importantly on the same site if it's a single site deployment. The sooner you can upgrade all the APs to WiNG7 the better. In terms of functionality it may not break the system but there are services like Smart-RF, statistics aggregation etc. which will be affected while you run two different versions of WiNG on the APs.
Regards,
Ovais
09-09-2021 12:21 PM
Here’s a link with upgrade instructions which may be helpful in your situation:
https://extremeportal.force.com/ExtrArticleDetail?an=000081743
Thank you,
09-09-2021 01:23 AM
Hi,
Here are the answers to your questions:
1- Your understanding is correct, the new firmware will only load after a controller reload/reboot. If it's a centralized/NOC type of deployment where controller is only used for mgmt., traffic is locally bridged, no tunneled data, no Captive Portal/Radius proxy/DHCP on the controller, then you can safely reload the controller even during the office hours since data and control planes are local to APs in that case. Otherwise,you should reload it after work hours.
2- The first and most important thing you must check is that all the AP models you are using have an upgrade path to WiNG7. If they do, you can first upgrade the controller, APs will stay adopted and functional with firmware mismatch. It depends on how the APs are deployed, if you have multiple RF-Domains you can upgrade APs by RF-Domains. There are few caveats when the APs are in firmware mismatch state:
a) No new configuration can be pushed to the APs while they are in firmware mismatch state.
b) You may experience issues with client auth if you are using the controller either as a Radius Server or a Captive Portal server.
3- It is not recommended to have both WiNG5 and WiNG7 APs on the same controller, and more importantly on the same site if it's a single site deployment. The sooner you can upgrade all the APs to WiNG7 the better. In terms of functionality it may not break the system but there are services like Smart-RF, statistics aggregation etc. which will be affected while you run two different versions of WiNG on the APs.
Regards,
Ovais