< Home

sfn-roam enable

Function

The sfn-roam enable command enables agile distributed SFN roaming.

The undo sfn-roam enable command disables agile distributed SFN roaming.

By default, agile distributed SFN roaming is disabled.

Format

sfn-roam enable

undo sfn-roam enable

Parameters

None

Views

VAP profile view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

In the agile distributed Wi-Fi networking, some scenarios require high network connection stability, such as healthcare scenarios. In this case, you can run the sfn-roam enable command to enable agile distributed SFN roaming. All RUs are deployed to work on the same channel and use the same BSSID for communicating with STAs. When the STAs move within the signal coverage of the same SSID, they are not aware of roaming and services are not interrupted.

Precautions

  • Network planning precautions:

    • 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:
      • Between the R230D and R240D (Note: Only the 2.4 GHz radio of the R230D and R240D supports agile distributed SFN roaming, and the 5 GHz radio does not support.)
      • Among the R250D, R250D-E, R251D, R251D-E and R450D
    • 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.

  • Configuration precautions:

    • 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:

      • SSID

      • VAP profile and VAP ID

      • Security policy. Agile distributed SFN roaming supports these encryption modes: WPA+PSK, WPA2+PSK, WPA-WPA2+PSK, WPA+802.1X (EAP authentication), WPA2+802.1X (EAP authentication), WPA-WPA2+802.1X (EAP authentication), and Portal+PSK.

Example

# Enable agile distributed SFN roaming.

<HUAWEI> system-view
[HUAWEI] wlan 
[HUAWEI-wlan-view] vap-profile name vap1
[HUAWEI-wlan-vap-prof-vap1] sfn-roam enable
Warning: This feature requires that radios work on the same channel. Enabling th
is feature will disable the channel calibration, channel scanning, and smart roa
ming functions on the AP and disconnect STAs connected to the VAP. Open, WEP, an
d WAPI encryption modes are not supported. The PSK + WPA2 mode is recommended. A
 radio allows SFN to be enabled only for one VAP. Continue?[Y/N]:y
Copyright © Huawei Technologies Co., Ltd.
Copyright © Huawei Technologies Co., Ltd.
< Previous topic Next topic >