Header Only - DO NOT REMOVE - Extreme Networks

AP7532 VC smart-rf can't manage the AP6532's radios

Userlevel 2
Hello community!

As far as I know RFDM can manage the radios of the other ap type also.
So I does a test with AP7532 VC + smart-rf with AP6532 stanalone. AP7532 is RFDM but he is can't manage the radios of the AP6532.
I don't talking about adoption, but managing smart rf radios!!!

It means that AP7532 can manage the radios of the AP6532 ONLY when the AP7532 is adopted by RFS/NX/VX and assigned as RFDM ?



5 replies

Userlevel 5
RF Domain Manager is elected Automatically elected with automatic failover:
  • If it has the highest RFDM priority
rf-domain-manager priority [1 – 255]
  • If it has the highest CPU
(eg. NX9600 > NX5500 > AP8533 > AP6522)
  • If it has the lowest MiNT ID (show mint id)
(eg. when all devices are the same type)
Userlevel 5
Hello Aviv,

if the AP is not adopted by the VC, then no management is made to that AP whatsoever, including smart-RF management. If smart-RF is enabled on both the VC and the AP6532, scanning will occur and smart-rf will adjust the parameters on both APs according to a what they are set in the smart-rf policy on each device independently.

Only APs listed below are supported in a heterogenous AP VC deployment, all other scenarios require a controller for the management of smart-rf in rf-domains with heterogenous AP (not listed below). The AP with the highest CPU will be elected as RFDM and manage the rest of them at that site.

AP 8533
AP 8432
AP 7632/AP 7662/AP 7612
AP 7622/AP 7602
AP 7532/AP 7522/AP 7562

Thank you,

Userlevel 5
The RF Domain Manager is responsible for:

  • Collecting Statistics
  • SMART-RF & WIPS coordination
  • Remote Troubleshooting
  • Data tunneling aggregation (optionally for MINT/L2TPv3 tunnels)
  • Distributing firmware & config to other Access Points in the RF Domain
Userlevel 3
Hello Aviv,

The behavior you are seeing in the VC scenario described is an expected one.
Please note the following regarding VC deployments..

An Independent Access Point operating as a Virtual Controller only provides management / configuration functions and not data switching for other Independent Access Points.
An Independent Access Point operating as a Virtual Controller provides:
 RF Management (Smart-RF)
 Firmware Updates adopted Access Points
 Configuration Management for adopted Access Points (24 Max / 64 for 802.11ac platforms except AP7502)
 Statistics Collection and Aggregation
 Troubleshooting adopted Access Points.
No tunneled VLANs are supported.

WiNG, support on the Virtual Controller (VC) AP to adopt and manage heterogeneous AP models for the 802.11ac AP platforms was added.

The following AP models can be deployed in a heterogenous AP VC scenario:
AP 8533
AP 8432
AP 7632/AP 7662/AP 7612
AP 7622/AP7602
AP 7532/AP 7522/AP 7562

The following are the supported adoption hierarchies:
AP 7662/7632 can adopt AP 7662/7632/7612
AP 8533/8432 can adopt AP 8533/8432/7562/7532/7522/7662/7632/7622/7612/7602
AP7532/AP7522/AP7562 can be managed by AP8533/AP8432 but not by AP7632/AP7662

Image upload capability will only be enabled on the AP that is elected as VC
VC can manage up to 64 APs
AP65xx APs do not support heterogeneous AP adoption and management.
Userlevel 2
Thank you all, guys.

Just like I thought.

In case of AP7532 + AP6532 both of them are adopted by controller, AP7532 can manage smart rf of the AP6532 also. But not without RFS/NX/VX.