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)
- what behavior will vc do when mismatch version ado...
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
what behavior will vc do when mismatch version adoptee join the rf-domain?
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
4 weeks ago
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
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?
Solved! Go to Solution.
1 ACCEPTED SOLUTION
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
4 weeks ago
@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
7 REPLIES 7
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
4 weeks ago
@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
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
3 weeks ago
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.
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
4 weeks ago - last edited 4 weeks ago
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?
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
4 weeks ago
Correct that is the default (out the box) behavior.
