< Home

Licensing Requirements and Limitations for Mesh

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 1 Mapping between switch versions and AP versions

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

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-1AP for WLAN access controller
  • AP resource license-16AP for WLAN access controller
  • AP resource license-32AP 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 S6700 Series Switches License Usage Guide.

Feature Support in V200R019C10

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.

Feature Limitations

  • The AirEngine 5760-22W, AirEngine 5760-22WD, AirEngine 5760-51, AirEngine 6760R-51, AirEngine 6760R-51E, AirEngine 6760-X1, AirEngine 6760-X1E, AirEngine 8760R-X1, AirEngine 8760R-X1E, AirEngine 8760-X1-PRO, AirEngine 9700D-M (including the mapping RUs), AP7060DN, AD9431DN-24X central AP (including the mapping RUs), AD9430DN-24 central AP (including the mapping RUs), AD9430DN-12 central AP (including the mapping RUs), AP6310SN-GN, AP2010DN, AP2030DN, AP2050DN, AP2050DN-E, AP2050DN-S, AP1010SN, AP7030DE, AP9330DN, AP2030DN-S, AP2051DN, AP2051DN-S, AP2051DN-L-S, AP5510-W-GP, AirEngine 5760-10, WA375DD-CE, and AP2051DN-E do not support the Mesh function.

  • On a WDS or Mesh network, an 802.11ac AP cannot interoperate with non-802.11ac APs regardless of the radio types used by the AP. Only 802.11ac APs can interoperate with each other.

    Among all WDS- or Mesh-capable APs, the AP1050DN-S, AP4050DN, AP4051DN, AP4151DN, AP4050DN-S, AP4051DN-S, AP8050DN, AP8150DN, AP8050DN-S, AP5030DN, AP5130DN, AP8130DN, AP8030DN, AP4030DN, AP430-E, AP4130DN, AP3030DN, AP9131DN, AP9132DN, AP5030DN-S, AP4030DN-E, AP6050DN, AP6150DN, AP7050DE, AP7050DN-E, AP4030TN, AP4050DN-E, AP4050DN-HD, AP4051TN, AP6052DN, AP7052DN, AP7152DN, AP7052DE, AP8050TN-HD, AP8082DN, AP8182DN, AP4050DE-M, AP4050DE-M-S, AP3050DE, AP4050DE-B-S, and AP5050DN-S are 802.11ac APs.

  • If radio 0 of the AP8130DN is configured to work on the 5 GHz frequency band and used for WDS or Mesh services, the software version of the AP connected to the AP8130DN must be V200R005C10 or a later version.

  • This section provides only Mesh configurations. After the Mesh configuration is complete, APs can connect to an AC through Mesh links. To use WLAN services, you still need to configure basic WLAN services. For details, see Example for Configuring WLAN Services on a Small-Scale Network.
  • When Mesh is configured on dual-band APs, any two adjacent APs cannot use radio 0 or radio 1 simultaneously to establish a Mesh link.
  • When configuring the Mesh function, ensure that Mesh nodes use the same bandwidth and channel.

  • The security profile used by WDS or Mesh links supports only the security policy WPA2+PSK+CCMP.

  • You are advised to configure different names for the profiles used to configure the Mesh function than the profiles used to configure the WLAN service. These profiles are the WMM profile, radio profile, and security profile. This configuration facilitates maintenance on the Mesh network and WLAN service.
  • The WLAN Mesh function and WLAN WDS function are mutually exclusive. If the WLAN WDS function has been configured, the WLAN Mesh function cannot be configured.
  • During Mesh network planning, if dual-band APs function as Mesh nodes, AP radios bound to Mesh profiles cannot be configured to work in monitor mode; if single-band APs function as Mesh nodes, AP radios cannot work in monitor mode.
  • Avoid using radar channels to configure Mesh links; otherwise, the following problems may occur:
    • Establishing Mesh links on radar channels takes several minutes or several ten minutes longer than establishing Mesh links on non-radar channels.
    • Radar signals cause disconnection of established Mesh links.
  • If WIDS, spectrum analysis, background neighbor probing, or terminal location is enabled on a radio, the radio cannot be used to establish a WDS bridge or Mesh link.

  • Radio calibration does not take effect on radios enabled with WDS or Mesh functions.
  • In WDS and Mesh scenarios, scanning services are not supported. Functions dependent on neighboring scanning, such as load balancing, smart roaming, and band steering, cannot be used.

  • In V200R006, if you set the CAPWAP heartbeat interval or the number of heartbeat packet transmissions to a small value using the capwap keep-alive interval interval-value or capwap keep-alive times times-value command, WDS or Mesh links may fail to be established. Therefore, you are advised to use the default values.

  • In V200R007 and later versions, if you set the CAPWAP heartbeat interval or the number of heartbeat packet transmissions to a small value using the capwap echo interval interval-value or capwap echo times times-value command, WDS or Mesh links may fail to be established. Therefore, you are advised to use the default values.

  • In V200R006, if WDS or Mesh is enabled simultaneously with dual-link backup, the AC sends CAPWAP heartbeat packets three times at an interval of 25 seconds by default. This may cause unstable WDS or Mesh links and result in user access failures. You are advised to run the capwap keep-alive times times-value command to set the number of heartbeat packet transmissions to 6 or a larger value.

  • In V200R007 and later versions, if WDS or Mesh is enabled simultaneously with dual-link backup, the AC sends CAPWAP heartbeat packets three times at an interval of 25 seconds by default. This may cause unstable WDS or Mesh links and result in user access failures. You are advised to run the capwap echo times times-value command to set the number of heartbeat packet transmissions to 6 or a larger value.

  • If an MP connects to a wired network, ensure that the MP does not communicate with MPPs at Layer 2 through the wired network; otherwise, the MP connects to MPPs through both Mesh links and wired links, which causes a network loop.
  • Starting from V200R007, the Mesh profile supports FWA and vehicle-ground fast link handover, which are mutually exclusive.

  • The antenna alignment VAP function is not available for the AirEngine 8760-X1-PRO, AirEngine 8760R-X1, AirEngine 8760R-X1E, AirEngine 6760-X1, AirEngine 6760-X1E, AirEngine 6760R-51, AirEngine 6760R-51E, AirEngine 5760-51, AirEngine 5760-22W, and AirEngine 5760-22WD.
Copyright © Huawei Technologies Co., Ltd.
Copyright © Huawei Technologies Co., Ltd.
< Previous topic Next topic >