upgrade the VX9000 controller including 1400+ AP

  • 0
  • 1
  • Question
  • Updated 2 months ago
  • Answered
  • (Edited)
Hi All, i am upgrading the VX9000 controller including 1400+ AP including. after upgrade controller would be 5.8.4 and AP would be in 5.8.0 until all AP upgrade is complete. if any site lost power does AP will be able to register to higher version if controller does higher version controller support lower version AP? if upgrade take 5 to 7 days for all AP to upgrade does they able to work togeter with different code?

Photo of Dinesh Thakur

Dinesh Thakur

  • 114 Points 100 badge 2x thumb

Posted 2 months ago

  • 0
  • 1
Photo of Ronald Dvorak

Ronald Dvorak, Embassador

  • 49,992 Points 20k badge 2x thumb
I'm not a WiNG expert but in general that is how centralized solutions work = support APs with lower software till they are on the same software (if they are not too far from each other).

1400+ APs isn't a small deployment (at least for me) so how about you invest in a lab controller to test things like that before doing it in the production environment.
Photo of Dinesh Thakur

Dinesh Thakur

  • 114 Points 100 badge 2x thumb
Thanks Ronald...Yes we are doing testing for this but Lab don't have that much devices which is creating issue.
Photo of Chris Kelly

Chris Kelly, Employee

  • 1,070 Points 1k badge 2x thumb
Question, if you upgrade the RFS4000 (currently running 5.8.0), why would you only upgrade to 5.8.4?  What model APs

To answer your question though:
If you upgrade the RFS4000 but do NOT upgrade the APs, the APs will still be adopted, but you will not be able to manage the APs (you will not be able to use the RFS4000 to push out configuration changes to the APs)

If a site loses power, the APs will function normally.  They will continue to operate using the version of WiNG they are running (5.8.0).

Regarding the upgrade process taking 5-7 days:
If it will take this long, my recommendation would be to use the RFS4000 to send the firmware updates to all the APs first.  Instruct the RFS4000 to *NOT* reboot the APs though (this is a configuration option when upgrading APs).  Wait until the firmware has been received by all of the APs.  During that time, there is no disruption of service. 
Once that process finishes, you can then manually instruct the APs to reboot, which will then complete the AP upgrade process.
There are multiple options when upgrading though.  This is just one way of doing it.  It just depends on your requirements.
Photo of Dinesh Thakur

Dinesh Thakur

  • 114 Points 100 badge 2x thumb
Hi Chris, Thank for your input,

we have taken 5.8.4 to resolve the Krack Venerability and some of the hardware are old like AP7181 and RFS7000 which does not support version above 5.8.4 so have no choice but to go head with 5.8.4 at the moment.

As this is three layer architecture we are planing to update the VM(Cluster of 3 two work as active/active and one is standby) for WAM (master controller) 1st and then from there we will push the code to RF-domain manager which are different for site like for smaller it might be AP with additional role and bigger site its RFS6000 and RFS7000. just one more query if WAM have new code and RFS also got new code AP will still be able to register user and BAU will work no authentication or other issue. just new configuration can't be updated without code upgrade.



Photo of Chris Kelly

Chris Kelly, Employee

  • 1,070 Points 1k badge 2x thumb
Dinesh, I thought something like that might have been the case (reason for 5.8.4).
So it sounds like you have a hierarchical topology also (VX9000 adopting site-controllers (RFS6000/7000 at some sites).

But to confirm:  Yes, You can upgrade the controller separately from the APs.  If the controller and APs are using different versions of WiNG, this just prevents you from being able to make configuration changes to the APs using the controller and then pushing those changes out from the controller.  This is 100% intentional and is done to protect the operation of the APs.  (*Sometimes* there are code differences between WiNG versions and there might be a case that if you pushed out a configuration change to an AP, the new config might contain a setting that the AP will not be compatible with the WiNG version on the AP)
Photo of Dinesh Thakur

Dinesh Thakur

  • 114 Points 100 badge 2x thumb
Thanks Chris
Photo of Chris Kelly

Chris Kelly, Employee

  • 1,070 Points 1k badge 2x thumb
In addition, because it sounds like it might be applicable here:

if the network links between the APs and controller are very slow you can adjust a setting to help prevent the upgrade process from timing-out (default value is 30 minutes, so if pushing out firmware to an AP takes more than 30 minutes, the update would time out). 

In the RFS4000 management policy, you can set an idle-session-timeout value.  NOTE: The new value only applies to new sessions.
Photo of Christoph S.

Christoph S., Employee

  • 3,430 Points 3k badge 2x thumb
You might want to have a look at this article with recommendations on this type of upgrade: https://gtacknowledge.extremenetworks.com/articles/How_To/Recommendations-for-upgrading-WiNG-5-wirel...
Photo of Dinesh Thakur

Dinesh Thakur

  • 114 Points 100 badge 2x thumb
Thanks Chris !!!