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

S12700 V200R010C00 Configuration Guide - WLAN-AC

This document describes native AC (hereinafter referred to as WLAN AC) configuration procedures and provides configuration examples.
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).
RU Online Process

RU Online Process

An agile distributed WLAN is composed of an AC, a central AP, and RUs. The AC centrally manages the central AP and RUs. The central AP and its connected RUs must be reachable at Layer 2. RUs are connected to a central AP, and receive and send 802.11 packets through the air interface. A central AP takes over some of an AC's work to perform central management and collaboration of RUs, such as STA going online, configuration delivery, and STA roaming between RUs. The central AP and RUs need to go online before being managed and controlled by the AC.

See AP Online Process for the online process of the central AP.

IP Address Allocation

An RU obtains an IP address in any of the following modes:
  • Static mode: An IP address is manually configured for an RU. CAPWAP packets between the central AP and RUs are forwarded at Layer 2 and are independent of IP addresses on an agile distributed WLAN. Therefore, the configuration of a static IP address does not affect the RU going online. Ensure that a route is reachable between the IP address of the RU and the central AP source address. Otherwise, services involving IP addresses may be affected, for example, Telnet.
  • DHCP mode: An RU functions as a DHCP client and requests an IP address from a DHCP server.

CAPWAP Tunnel Establishment

The AC manages and controls RUs in a centralized manner through Control and Provisioning of Wireless Access Points (CAPWAP) tunnels. CAPWAP tunnels provide the following functions:
  • Maintain connectivity states between the AC and RUs.
  • Help the AC to manage and deliver configurations to RUs.
  • Transmit service data to the AC for centralized forwarding.
Management packets between the AC and RUs are transmitted through CAPWAP control tunnels between them. A CAPWAP control tunnel between an RU and AC consists of the CAPWAP control tunnel between the AC and central AP associated with the RU and that between the RU and central AP.
  • See AP Online Process for the process of establishing a CAPWAP control tunnel between the AC and central AP.
  • See Figure 5-11 for the process of establishing a CAPWAP control tunnel between the central AP and RU.

Service data packets between the AC and RUs are transmitted through the MAC-IN-MAC data tunnel between the central AP and RUs and the CAPWAP data tunnel between the central AP and AC. See AP Online Process for the process of establishing a CAPWAP data tunnel between the AC and central AP.

When RUs are connected to an AD9430DN-12 or AD9430DN-24: Service data packets between the AC and RUs are transmitted through the MAC-IN-MAC data tunnel between the central AP and RUs and the CAPWAP data tunnel between the central AP and AC. When RUs are connected to an AD9431DN-24X: In tunnel forwarding mode, the RUs set up CAPWAP tunnels with the AC; in direct forwarding mode, services are forwarded directly at Layer 2, without the CAPWAP tunnel. See AP Online Process for the process of establishing a CAPWAP data tunnel between the AC and central AP or between the central AP and RUs.

Figure 5-11  CAPWAP tunnel establishment between the central AP and RUs

The process of establishing a CAPWAP tunnel is as follows:
  1. An RU sends a Discovery Request packet to find a central AP. (Discovery Phase)

    NOTE:

    In Discovery phase, the central AP determines whether to permit access from an RU based on the Discovery Request packet that the RU sends and will not respond to Discovery Request packets of RUs not permitted for access. The process is similar to Figure 5-12.

    An RU can discover a central AP in either of the following two modes.
    • When no IP address list of central APs is configured on an RU or an RU does not receive any Discovery Response packet after sending unicast Discovery Request packets ten consecutive times, the RU will broadcast Discovery Request packets to automatically discover a central AP in the same network segment and then selects a central AP to establish a CAPWAP tunnel according to the returned Discovery Response packets.

    • A static IP address list of central APs is preconfigured on an RU. When the RU goes online, it sends a unicast Discovery Request packet to each central AP whose IP address is specified in the IP address list. After receiving the Discovery Request packet, the central APs return Discovery Response packets to the RU. The RU then selects a central AP to establish a CAPWAP tunnel.

  2. The RU establishes a CAPWAP tunnel with a central AP.

    CAPWAP tunnels include data tunnels and control tunnels.
    • Data tunnel: transmits service data from the RU to an AC for centralized forwarding.
    • Control tunnel: transmits control packets between the RU and central AP or between the RU and AC. You can choose to enable datagram transport layer security (DTLS) encryption over the control tunnel to ensure security of CAPWAP control packets. Subsequently, all CAPWAP control packets will be encrypted and decrypted through DTLS, ensuring integrity and privacy of the CAPWAP control packets.

CAPWAP Tunnel Maintenance

The RU and central AP exchange Keepalive packets to detect the data tunnel connectivity.

The RU and central AP exchange Echo packets to detect the control tunnel connectivity.

RU Access Control

When an RU requests to access the AC, the central AP sends an Authentication Request packet to the AC. The AC then determines whether to allow the RU access and returns an Authentication Response packet to the AP. The Authentication Response packet carries the RU software upgrade mode and RU version.

Figure 5-12 shows a flowchart depicting the process for RU access control.

Figure 5-12  RU access control flowchart

RU Software Upgrade

The RU determines whether its system software version is the same as that specified on the AC according to parameters in the received Authentication Response packet.

  • If so, the RU goes to the next stage.

  • If not, the RU upgrades its version in the upgrade mode carried in the Authentication Response packets. The upgrade mode includes the AC mode, FTP mode, and SFTP mode.

    After the software version is updated, the RU restarts and repeats the preceding steps.

AC Configuration Delivery

The AC sends a Configuration Update Request packet to the central AP, which then replies with a Configuration Update Response packet. The AC then delivers service configurations of RUs to the central AP, and the central AP delivers the service configurations to the RUs.

Translation
Download
Updated: 2019-04-20

Document ID: EDOC1000142094

Views: 120255

Downloads: 119

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