No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

Configuration Guide - WLAN-AC

S5700 and S6720 V200R012C00

This document describes the configurations of WLAN, including WLAN Service Configuration, Radio Resource Management, Roaming, WLAN QoS, WLAN Security, WDS, Mesh, Location, Hotspot 2.0, Dual-Link Cold Backup, N+1 Backup.
Rate and give feedback :
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document. Note: Even the most advanced machine translation cannot match the quality of professional translators. Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
Licensing Requirements and Limitations for Roaming

Licensing Requirements and Limitations for Roaming

Involved Network Elements

AP
  • APs mentioned in this document are Huawei AP products. You are advised to use Huawei APs to connect to the AC.
  • You can run the display ap-type all command to check the default AP types supported by the device.
  • When central APs and RUs are used, ensure that their versions are the same. For example, if the central AP version is V200R007C10, the RU version must be V200R007C10.
Table 8-4  Mapping between switch versions and AP versions

Product Software Version

AP Software Version

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

Client
  • To implement the fast roaming feature, the client must support fast roaming technology.

Licensing Requirements

When the device is used as a WLAN AC, the number of online APs supported by the device is controlled by licenses. The device supports a maximum of 16 online APs. To increase the number of online APs supported by the device, apply for and purchase a license from the agent.
  • AP resource license-16AP for WLAN access controller
  • AP resource license-64AP for WLAN access controller
  • AP resource license-128AP for WLAN access controller
  • AP resource license-512AP for WLAN access controller

For details about how to apply for a license, see Obtaining Licenses in the S1720, S5700, and S6720 Series Switches License Usage Guide.

Version Requirements

Table 8-5  Products and minimum version supporting roaming

Series

Product Model

Minimum Version Required

S2700 series switches

-

Not supported

S3700 series switches

-

Not supported

S5700 series switches

S5720HI, S5730HI

S5720HI: V200R006

S5730HI: V200R012

S6700 series switches

S6720HI

V200R012

Feature Limitations

  • The APs on which WLAN roaming is implemented must use the same SSID and security profiles, and the security profiles must have the same configurations.
  • 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.

    You can use either of the following methods to enable STA address learning according to the version of your product:
    • Run the learn client ip-address enable command in the service set view.
  • IEEE 802.11r supports open system, WPA2-PSK, and 802.1X authentication.
  • The 802.11r fast roaming and Protected Management Frame (PMF) functions are mutually exclusive. If the 802.11r fast roaming function has been configured, the PMF function cannot be configured.
  • STAs that are not compatible with 802.11r cannot associate with WLANs on which the 802.11 fast roaming function is enabled. To guarantee normal network services for users, replace the earlier STA model with the one that supports 802.11r, or create two VAPs using the same SSID with one enabling 802.11r and the other disabling it, and retain other configurations.
  • When 802.1X authentication is used for 802.11r, some STAs may get offline and online again during reauthentication due to compatibility issues if 802.1X reauthentication is enabled.
  • Pay attention to the following precautions when configuring agile distributed SFN roaming:
    • 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.

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

  • Pay attention to the following points when configuring inter-AC roaming:
    • Inter-AC roaming is supported only in distributed VXLAN gateway scenarios, and only Layer 2 inter-AC roaming is supported.
    • ACs in the same mobility group must run the same system software of the C version. Otherwise, inter-AC roaming may fail.
    • The mobility group name and IP address for establishing an inter-AC tunnel must be configured on each AC in the mobility group. ACs must be added to the mobility group.
    • The IP addresses used for establishing an inter-AC tunnel between ACs in a mobility group must be the CAPWAP source IP addresses of the ACs. When multiple CAPWAP source IP addresses are configured, only on CAPWAP source IP address can be used to establish an inter-AC tunnel.
    • The mobility group name must be the same on each AC.
    • A maximum of 16 ACs can be added to a mobility group, and one AC can be added only to one mobility group.
Translation
Download
Updated: 2018-12-24

Document ID: EDOC1100038361

Views: 109868

Downloads: 368

Average rating:
This Document Applies to these Products
Related Documents
Related Version
Share
Previous Next