Product Software Version |
AP Software Version |
---|---|
V200R019C10 |
V200R019C10 V200R019C00 V200R010C00 V200R009C00 V200R008C10 V200R008C00 V200R007C20 V200R007C10 V200R006C20 V200R006C10 |
V200R019C00 |
V200R019C00 V200R010C00 V200R009C00 V200R008C10 V200R008C00 V200R007C20 V200R007C10 V200R006C20 V200R006C10 |
V200R013C00 |
V200R010C00 V200R009C00 V200R008C10 V200R008C00 V200R007C20 V200R007C10 V200R006C20 V200R006C10 |
V200R012C00 |
V200R009C00 V200R008C10 V200R008C00 V200R007C20 V200R007C10 V200R006C20 V200R006C10 |
V200R011C10 |
V200R008C10 V200R008C00 V200R007C20 V200R007C10 V200R006C20 V200R006C10 |
V200R011C00 |
V200R007C20 V200R007C10 V200R006C20 V200R006C10 |
V200R010C00 |
V200R007C10 V200R006C20 V200R006C10 |
V200R009C00 |
V200R006C20 V200R006C10 |
V200R008C00 |
V200R005C30 V200R005C20 V200R005C10 |
V200R007 |
V200R005C20 V200R005C10 |
V200R006 |
V200R005C00 |
For details about how to apply for a license, see Obtaining Licenses in the S1720, S5700, and S6700 Series Switches License Usage Guide.
This feature is supported only by the following models: S5720-HI, S5730-HI, S5731-H, S5731S-H, S5732-H, S6720-HI, S6730S-H, and S6730-H.
In direct forwarding mode, if the ARP entry of a user is not aged out in time on the access device connected to the AP after the user roams, services of the user will be temporarily interrupted. You are advised to enable STA address learning on the AC. After the function is enabled, the AP will send a gratuitous ARP packet to the access device so that the access device can update ARP entries in a timely manner. This ensures nonstop service transmission during user roaming.
Agile distributed SFN roaming is supported only by the AD9430DN-12 (including matching RUs) and AD9430DN-24 (including matching RUs). RUs support agile distributed SFN roaming in the following combination modes:
For the central AP, after agile distributed SFN roaming is enabled, the total number of agile distributed SFN roaming STAs on a single frequency band (2.4 GHz or 5 GHz) of all RUs does not exceed 128, and that of STAs associated with other VAPs on the same band does not exceed 128.
After agile distributed SFN roaming is enabled, configure all RUs to work on the same channel. When agile distributed SFN roaming is enabled on the 5 GHz frequency band, configure non-radar channels.
RUs involved in roaming must be associated with the same central AP but do not support agile distributed SFN roaming between central APs.
Inter-RU roaming is Layer 2 roaming within a central AP. Agile distributed SFN roaming is not performed on Layer 3.
When agile distributed SFN roaming is enabled for both the 2.4 GHz and 5 GHz radios, it is recommended that different SSIDs be used. Otherwise, the radio switchover may occur, affecting user experience.
Agile distributed SFN roaming can be enabled only on one VAP of a radio. If multiple VAPs are configured on a radio, it is recommended that the total VAP rate limit on all VAPs with agile distributed SFN roaming disabled be set to 5 Mbit/s.
If agile distributed SFN roaming is enabled on a VAP of a radio in an AP group, the roaming tracks of all the STAs that are connected to the central AP and associated with the radio may carry the s flag.
Radios enabled with agile distributed SFN roaming do not support channel scanning, channel calibration, or smart roaming.
Agile distributed SFN roaming can be configured based only on AP groups but not based on APs.
RUs involved in agile distributed SFN roaming need to have the following items configured the same: