topic Re: what behavior will vc do when mismatch version adoptee join the rf-domain? in ExtremeWireless (WiNG)

what behavior will vc do when mismatch version adoptee join the rf-domain?

zlinuxboy — Thu, 07 Aug 2025 08:25:59 GMT

I got 3 ap7522, A is act as vc, under A's cli, I upgrade firmware on B and C to 7.7.1.12 with:

1. upload new firmware 7.7.1.12 to vc:

#device-upgrade load-image ap7522 tftp://192.168.9.56/AP7522-7.7.1.12-003R.img

device-upgrade rf-domain hkjm ap7522 no-reboot

ref: https://extreme-networks.my.site.com/ExtrArticleDetail?an=000081743&q=how%20to%20upgrade%20firmware%20when%20an%20ap%20join%20rfdm%20wing

I just want the other partition contain 7.7.1.12 firmware as backup, not to use it right now. so A is still running 5.9.8
After B and C finished firmware upgrade, I put both of them's next boot partition to 5.9.8 and reload the ap, but after reload and join rfdm again, vc automatically instruct them to download 7.7.1.12 and reload it again to 7.7.1.12 partition, why?

Re: what behavior will vc do when mismatch version adoptee join the rf-domain?

zlinuxboy — Thu, 07 Aug 2025 08:49:45 GMT

ap7522-044FA8>show adoption status
Adoption Mode: CONTROLLER
--------------------------------------------------------------------------------------------------------------------------------
DEVICE-NAME VERSION CFG-STAT MSGS ADOPTED-BY LAST-ADOPTION UPTIME IPv4-ADDRESS
--------------------------------------------------------------------------------------------------------------------------------
ap7522-01E3EC 7.7.1.12-003R version-mismatch No ap7522-044FA8 0 days 00:03:53 0 days 00:35:11 192.168.9.90
ap7522-A1AE58 7.7.1.12-003R version-mismatch No ap7522-044FA8 0 days 00:04:10 0 days 00:35:22 192.168.9.72
---------------------------------------------------------------------------------------------------------------------------------
Total number of devices displayed: 2

ap7522-044FA8#show adoption status
Adoption Mode: CONTROLLER
--------------------------------------------------------------------------------------------------------------------------------
DEVICE-NAME VERSION CFG-STAT MSGS ADOPTED-BY LAST-ADOPTION UPTIME IPv4-ADDRESS
--------------------------------------------------------------------------------------------------------------------------------
ap7522-01E3EC 5.9.8.4-002R configured No ap7522-044FA8 0 days 00:00:15 0 days 00:03:01 192.168.9.90
---------------------------------------------------------------------------------------------------------------------------------
Total number of devices displayed: 1

ap7522-044FA8#show device-upgrade status
Number of devices currently being upgraded : 0
Number of devices waiting in queue to be upgraded : 2
Number of devices currently being rebooted : 0
Number of devices waiting in queue to be rebooted : 0
Number of devices failed upgrade : 0
---------------------------------------------------------------------------------------------------------
DEVICE STATE UPGRADE TIME REBOOT TIME PROGRESS RETRIES LAST UPDATE ERROR UPGRADED BY
---------------------------------------------------------------------------------------------------------
ap7522-01E3EC waiting immediate immediate 0 0 - ap7522-044FA8
ap7522-A1AE58 waiting immediate immediate 0 0 - ap7522-044FA8
---------------------------------------------------------------------------------------------------------
ap7522-044FA8#show device-upgrade status
Number of devices currently being upgraded : 2
Number of devices waiting in queue to be upgraded : 0
Number of devices currently being rebooted : 0
Number of devices waiting in queue to be rebooted : 0
Number of devices failed upgrade : 0
--------------------------------------------------------------------------------------------------------------
DEVICE STATE UPGRADE TIME REBOOT TIME PROGRESS RETRIES LAST UPDATE ERROR UPGRADED BY
--------------------------------------------------------------------------------------------------------------
ap7522-01E3EC downloading immediate immediate 0 0 - ap7522-044FA8
ap7522-A1AE58 downloading immediate immediate 0 0 - ap7522-044FA8
--------------------------------------------------------------------------------------------------------------
ap7522-044FA8#show de
debug debugging device-upgrade
ap7522-044FA8#show device-upgrade versions
--------------------------------------------------------------------------------
CONTROLLER DEVICE-TYPE VERSION
--------------------------------------------------------------------------------
ap7522-044FA8 ap7522 7.7.1.12-003R
ap7522-044FA8 ap7532 7.7.1.12-003R
ap7522-044FA8 ap7562 7.7.1.12-003R
--------------------------------------------------------------------------------

AFTER A WHILE

ap7522-044FA8#show device-upgrade status
Number of devices currently being upgraded : 0
Number of devices waiting in queue to be upgraded : 0
Number of devices currently being rebooted : 0
Number of devices waiting in queue to be rebooted : 0
Number of devices failed upgrade : 0
------------------------------------------------------------------------------------------
DEVICE STATE UPGRADE TIME REBOOT TIME PROGRESS RETRIES LAST UPDATE ERROR UPGRADED BY
------------------------------------------------------------------------------------------
------------------------------------------------------------------------------------------
ap7522-044FA8#show adoption status
Adoption Mode: CONTROLLER
--------------------------------------------------------------------------------------------------------------------------------
DEVICE-NAME VERSION CFG-STAT MSGS ADOPTED-BY LAST-ADOPTION UPTIME IPv4-ADDRESS
--------------------------------------------------------------------------------------------------------------------------------
ap7522-01E3EC 7.7.1.12-003R version-mismatch No ap7522-044FA8 0 days 00:04:32 0 days 00:06:42 192.168.9.90
ap7522-A1AE58 7.7.1.12-003R version-mismatch No ap7522-044FA8 0 days 00:04:40 0 days 00:06:43 192.168.9.72
---------------------------------------------------------------------------------------------------------------------------------
Total number of devices displayed: 2
ap7522-044FA8#
ap7522-044FA8#
ap7522-044FA8#
ap7522-044FA8#
ap7522-044FA8#dir flash:/upgrade
Directory of flash:/upgrade

-rw- 39904402 Thu Aug 7 14:37:12 2025 birch.img

if the adoptee's running firmware is not match with vc's flash:/upgrade/birch.img, vc will automatically upgrade it to the match firmware and reload it?
how to end this loop action? delete the firmware on vc flash:/upgarde/birch.img?

Re: what behavior will vc do when mismatch version adoptee join the rf-domain?

zlinuxboy — Thu, 07 Aug 2025 09:06:38 GMT

After I delete the vc's flash:/upgrade/birch.img, the upgrade and reload loop end. but it's just a workaround, any correct configuration to avoid this behavior?

Re: what behavior will vc do when mismatch version adoptee join the rf-domain?

Daren_E — Thu, 07 Aug 2025 13:10:44 GMT

@zlinuxboy
Can you advise what the end game is?
Should all 3 APs be configured for 5.9.x and have the secondary partition loaded with 7.7.1.12
Or are you trying to have all 3 APs load 7.7.1.12 on both the primary and secondary partition.

Note:
The default behavior of the VC AP is to upgrade APs to the image loaded in flash if there is a mismatch.
If you would rather manually trigger the upgrading of the APs, you will need to disable this feature on the AP designated as the VC.
>en
#self
#no device-upgrade auto
#com wr

Re: what behavior will vc do when mismatch version adoptee join the rf-domain?

zlinuxboy — Thu, 07 Aug 2025 13:32:36 GMT

yes, all 3 APs be configured for 5.9.x and have the secondary partition loaded with 7.7.1.12
but I would like to stick with 5.9.x on active boot.

The default behavior of the VC AP is to upgrade APs to the image loaded in flash if there is a mismatch.
---
this is what I want to know, thanks.
That mean no matter which version I run on vc, the flash firmware is the standard, if the adoptee's running firmware is not match with it, vc will instruct adoptee to upgrade the inactive partition and reload to it. is that right?

Re: what behavior will vc do when mismatch version adoptee join the rf-domain?

Daren_E — Thu, 07 Aug 2025 14:28:29 GMT

Correct that is the default (out the box) behavior.

Re: what behavior will vc do when mismatch version adoptee join the rf-domain?

Angelo_Cargnel — Thu, 07 Aug 2025 14:33:22 GMT

As Daren_Elis already mentioned you should disable "device-upgrade auto" in the virtual controller:
en
self
no device-upgrade auto
com wr

Best regards,
Angelo

Re: what behavior will vc do when mismatch version adoptee join the rf-domain?

Angelo_Cargnel — Fri, 08 Aug 2025 07:14:41 GMT

Once the device-upgrade auto is disabled you can upgrade the AP firmware manually.
Therefore, you can choose youself which firmware the APs will have in each partition and which to run.
This is under your (manual) control.