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

Fat AP and Cloud AP V200R008C00 CLI-based Configuration Guide

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).
Configuring WLAN QoS

Configuring WLAN QoS

Configuring WMM

Pre-configuration Tasks

Before configuring WMM, perform the task of WLAN Service Configuration Guide (Common AP).

Procedure

  1. Run:

    system-view

    The system view is displayed.

  2. Run:

    wlan

    The WLAN view is displayed.

  3. Run:

    radio-2g-profile name profile-name or radio-5g-profile name profile-name

    The 2G or 5G radio profile view is displayed.

  4. Run:

    undo wmm disable

    WMM is enabled.

    By default, WMM is enabled.

    NOTE:

    802.11n and 802.11ac STAs must support WMM. If the WMM function is disabled in a radio, 802.11n and 802.11ac cannot work and STAs can access the network only in 802.11a/b/g mode.

    If the WMM function is disabled, the access of non-HT STAs fails to be denied.

  5. (Optional) Run:

    wmm mandatory enable

    STAs that do not support WMM are forbidden to connect to a WMM-enabled AP.

    By default, STAs that do not support WMM are allowed to connect to a WMM-enabled AP.

    On a WLAN, wireless channels are open and all STAs have an equal chance to occupy the wireless channels. You can configure WMM to assign different priorities to packets and enable high-priority packets to preferentially use wireless channel resources, meeting differentiated service requirements. You can also disable STAs that do not support WMM from connecting to a WMM-enabled AP, which prevents those STAs from preempting channels of WMM-capable STAs.

  6. Run:

    wmm edca-ap { ac-vo | ac-vi | ac-be | ac-bk } { aifsn aifsn-value | ecw ecwmin ecwmin-value ecwmax ecwmax-value | txoplimit txoplimit-value | ack-policy { normal | noack } } *

    EDCA parameters and ACK policies are set for APs.

    Table 27-11 lists the default EDCA parameter settings and ACK policies for APs.
    Table 27-11  Default EDCA parameter settings and ACK policies for APs
    Packet Type ECWmax ECWmin AIFSN TXOPLimit ACK Policy
    AC_VO 3 2 1 47 normal
    AC_VI 4 3 1 94 normal
    AC_BE 6 4 3 0 normal
    AC_BK 10 4 7 0 normal

    As shown in the table, queues of AC_VO, AC_VI, AC_BE, and AC_BK are in descending order of priority.

    NOTE:
    After the high-density function is enabled on an AP, the AP will optimize EDCA parameters of AC_BE packets, for example, adjusting the contention window size. In this way, the probability of user collisions will be reduced, and users can enjoy better service experience in high-density scenarios. If you configure EDCA parameters in the WMM profile on the AP, the configuration does not take effect on AC_BE packets.

  7. Run:

    quit

    Return to the WLAN view.

  8. Run:

    ssid-profile name profile-name

    The SSID profile view is displayed.

  9. Run:

    wmm edca-client { ac-vo | ac-vi | ac-be | ac-bk } { aifsn aifsn-value | ecw ecwmin ecwmin-value ecwmax ecwmax-value | txoplimit txoplimit-value } *

    EDCA parameters are set for STAs.

    Table 27-12 lists the default EDCA parameter settings for STAs.
    Table 27-12  Default EDCA parameter settings for STAs
    Packet Type ECWmax ECWmin AIFSN TXOPLimit
    AC_VO 3 2 2 47
    AC_VI 4 3 2 94
    AC_BE 10 4 3 0
    AC_BK 10 4 7 0

    As shown in the table, queues of AC_VO, AC_VI, AC_BE, and AC_BK are in descending order of priority.

Verifying the Configuration
  • Run the display radio-5g-profile name profile-name or display radio-2g-profile name profile-name command to check the WMM configuration in a radio profile.

  • Run the display ssid-profile name profile-name command to check the WMM configuration in an SSID profile.

Configuring Priority Mapping

Pre-configuration Tasks

Before configuring priority mapping, perform the task of WLAN Service Configuration Guide (Common AP).

Procedure

  1. Run:

    system-view

    The system view is displayed.

  2. Run:

    wlan

    The WLAN view is displayed.

  3. Run:

    traffic-profile name profile-name

    A traffic profile is created and the traffic profile view is displayed.

    By default, the system provides the traffic profile default.

  4. Configure priority mapping as required.

    • Configure priority mapping for packets sent to an AP from upper-layer devices.

      1. Run the priority-map downstream trust { dot1p | dscp } command to configure a trusted priority type used in mapping from 802.3 packets to 802.11 packets.

        By default, the DSCP priority is used in mapping from 802.3 packets to 802.11 packets when packets are sent to an AP from upper-layer devices.

      2. Configure priority mapping.

        • When the DSCP priority is specified as the trusted priority type, perform the following configuration:

          Run the priority-map downstream dscp { dscp-value1 [ to dscp-value2 ] } &<1-10> dot11e dot11e-value command to configure mapping from the DSCP priority of 802.3 packets to the user priority of 802.11 packets when packets are sent to an AP from upper-layer devices.

          Table 27-13 describes the default mapping from the DSCP priority of 802.3 packets to the user priority of 802.11 packets.
          Table 27-13  Default mapping from the DSCP priority of 802.3 packets to the user priority of 802.11 packets

          DSCP

          UP

          0-7

          0

          8-15

          1

          16-23

          2

          24-31

          3

          32-39

          4

          40-47

          5

          48-55

          6

          56-63

          7

        • When the 802.1p priority is specified as the trusted priority type, perform the following configuration:

          Run the priority-map downstream dot1p { dot1p-value1 [ to dot1p-value2 ] } &<1-7> dot11e dot11e-value command to configure mapping from the 802.1p priority of 802.3 packets to the user priority of 802.11 packets when packets are sent to an AP from upper-layer devices.

          By default, 802.1p priority 0 of 802.3 packets maps to user priority 0 of 802.11 packets, 802.1p priority 1 to user priority 1, and similarly, 802.1p priority 7 to user priority 7.

  5. Run:

    quit

    Return to the WLAN view.

  6. Run:

    vap-profile name profile-name

    The VAP profile view is displayed.

  7. Run:

    traffic-profile profile-name

    The traffic profile is bound to the VAP profile.

    By default, the traffic profile default is bound to a VAP profile.

Verifying the Configuration
  • Run the display traffic-profile { all | name profile-name } command to check the priority mapping configuration in a traffic profile.

Configuring Traffic Policing

Context

To protect network resources and prevent network congestion, configure traffic policing to limit the rate of traffic entering the WLAN.

Traffic policing on a WLAN can be configured in a traffic profile or user profile.

Monitored Object

Description

Command

Rate limiting for a single VAP

If the rate limit in a traffic profile is set to limit, the total bandwidth of all the STAs associating with a single VAP with this SSID profile bound does not exceed limit.

rate-limit vap { up | down } rate-value

QoS CAR for a single STA

If the QoS CAR in a user profile is set to car-value, the bandwidth of a single STA associating with a VAP with this SSID profile bound does not exceed car-value.

qos car (user profile view)

Rate limiting for a single STA

If the rate limit in a traffic profile is set to limit, the bandwidth of a single STA with a VAP with this SSID profile bound does not exceed limit.

rate-limit client { up | down } rate-value

Pre-configuration Tasks

Before configuring traffic policing, perform the task of WLAN Service Configuration Guide (Common AP).

Procedure

  • Configure traffic policing in a traffic profile.
    1. Run:

      system-view

      The system view is displayed.

    2. Run:

      wlan

      The WLAN view is displayed.

    3. Run:

      traffic-profile name profile-name

      A traffic profile is created and the traffic profile view is displayed.

    4. Run:

      rate-limit { client | vap } { up | down } rate-value

      The rate limit is configured for upstream and downstream traffic of all STAs or a single STA on a VAP.

      • By default, the rate limit for upstream and downstream traffic of all STAs on a VAP is 4294967295 kbit/s.

      • By default, the rate limit for upstream and downstream traffic of a single STA on a VAP is 4294967295 kbit/s.

    5. Run:

      quit

      Exit from the traffic profile view.

    6. Run:

      vap-profile name profile-name

      The VAP profile view is displayed.

    7. Run:

      traffic-profile profile-name

      A traffic profile is bound to the VAP profile.

      By default, the traffic profile default is bound to a VAP profile.

  • Configure traffic policing in a user profile.
    1. Run:

      system-view

      The system view is displayed.

    2. Run:

      qos car car-name cir cir-value [ cbs cbs-value [ pbs pbs-value  ] | pir pir-value [ cbs cbs-value pbs pbs-value ] ]

      A QoS CAR profile is created.

    3. Run:

      wlan

      The WLAN view is displayed.

    4. Run:

      user-profile name profile-name

      A user profile is created and the user profile view is displayed.

    5. Run:

      qos car { inbound | outbound } car-profile

      A QoS CAR profile is bound to the user profile.

      By default, no QoS CAR profile is bound to a user profile.

    6. Run:

      quit

      Exit from the user profile view.

    7. Run:

      vap-profile name profile-name

      The VAP profile view is displayed.

    8. Run:

      user-profile profile-name

      A user profile is bound to the VAP profile.

      By default, no user profile is bound to a VAP profile.

Verifying the Configuration
  • Run the display traffic-profile { all | name profile-name } command to check the configuration of the rate limit for upstream and downstream traffic of the STAs on the VAP in the traffic profile.

  • Run the display user-profile { all | name profile-name } command to check the user profile configuration.

Configuring Airtime Fair Scheduling

Context

Airtime fair scheduling computes wireless channel occupation time of users in the same VAP and preferentially schedules users who occupy the channel for a relatively short time. In this way, each user is assigned equal time to occupy the channel, ensuring fairness in channel usage.
Pre-configuration Tasks

Before configuring airtime fair scheduling, perform the task of WLAN Service Configuration Guide (Common AP).

Procedure

  1. Run:

    system-view

    The system view is displayed.

  2. Run:

    wlan

    The WLAN view is displayed.

  3. Run:

    rrm-profile name profile-name

    An RRM profile is created and the RRM profile view is displayed.

  4. Run:

    airtime-fair-schedule enable

    Airtime fair scheduling is enabled on an AP radio.

    By default, airtime fair scheduling is disabled on an AP radio.

Verifying the Configuration
  • Run the display rrm-profile { all | name profile-name } command to check airtime fair scheduling status in a RRM profile.

Configuring ACL-based Packet Filtering

Context

When ACL-based packet filtering is configured in a traffic profile, the device permits or denies packets based on ACL rules, therefore controlling network traffic.

Pre-configuration Tasks

Before configuring ACL-based packet filtering, complete the following tasks:

  • Perform the task of WLAN Service Configuration Guide (Common AP).

  • Create corresponding ACL rules.

    The traffic-filter command can reference a numbered ACL that is not configured. You can configure the referenced ACL after running this command.

Procedure

  1. Run:

    system-view

    The system view is displayed.

  2. Run:

    wlan

    The WLAN view is displayed.

  3. Run:

    traffic-profile name profile-name

    The traffic profile view is displayed.

    By default, the system provides the traffic profile default.

  4. Run:

    traffic-filter { inbound | outbound } { ipv4 | l2 } acl { acl-number | name acl-name } or traffic-filter { inbound | outbound } ipv4 acl { acl-number | name acl-name } l2 acl { acl-number | name acl-name }

    The ACL-based packet filtering in the traffic profile is configured.

    By default, ACL-based packet filtering is not configured in a traffic profile.

    You can only configure a maximum of eight ACL rules in the same direction. The sequence in which ACL rules takes effect follows the sequence in which the rules are configured. To change the current packet filtering rules, delete all the related configurations and reconfigure the ACL-based packet filtering.

    When multiple traffic-filter commands are configured for ACL-based packet filtering in the same direction in the same traffic profile, packets are matched against the next rule in the sequence in which the commands are configured. If packets match a rule, the device executes the specified policy and stops the matching process. Otherwise, the device continues to match packets against the next rule. If no rule is matched, the packets are allowed to pass through.

  5. Run:

    quit

    Return to the WLAN view.

  6. Run:

    vap-profile name profile-name

    The VAP profile view is displayed.

  7. Run:

    traffic-profile profile-name

    The traffic profile is bound to the VAP profile.

    By default, the traffic profile default is bound to a VAP profile.

Checking the Configuration
  • Run the display traffic-filter applied-record command to check all application information of ACL-based packet filtering.

Configuring ACL-based Priority Remarking

Context

By configuring ACL-based priority remarking, the device remarks the priorities of wireless packets matching ACL rules to provide differentiated services.

Pre-configuration Tasks

Before configuring ACL-based priority remarking, complete the following tasks:

Procedure

  1. Run:

    system-view

    The system view is displayed.

  2. Run:

    wlan

    The WLAN view is displayed.

  3. Run:

    traffic-profile name profile-name

    A traffic profile is created and the traffic profile view is displayed.

    By default, the system provides the traffic profile default.

  4. Run the traffic-remark { inbound | outbound } { ipv4 | l2 } acl { acl-number | name acl-name } { dot11e dot11e-value | dscp dscp-value } to configure ACL-based priority remarking in the traffic profile.

    By default, ACL-based priority re-marking is not configured in a traffic profile.

    The traffic-remark command can reference a numbered ACL rule that is not configured. You can configure the referenced ACL rule after running this command.

    You can only configure a maximum of eight ACL-based packet re-marking rules in the same direction. The sequence in which ACL rules takes effect follows the rule configuration sequence. To change the current packet re-marking rules, delete all the related configurations and reconfigure the ACL-based packet re-marking.

  5. Run:

    quit

    Return to the WLAN view.

  6. Run:

    vap-profile name profile-name

    The VAP profile view is displayed.

  7. Run:

    traffic-profile profile-name

    The traffic profile is bound to the VAP profile.

    By default, the traffic profile default is bound to a VAP profile.

Checking the Configuration
  • Run the display traffic-remark applied-record command to check all application information about ACL-based priority remarking on the AC.

Configuring User Isolation on a VAP

Context

In a traffic profile, user isolation prevents packets of users on a VAP from being forwarded to each other. That is, users on a VAP cannot communicate with each other after user isolation is enabled. This improves user communication security and enables the gateway to centrally forward user traffic, facilitating user management.

Procedure

  1. Run:

    system-view

    The system view is displayed.

  2. Run:

    wlan

    The WLAN view is displayed.

  3. Run:

    traffic-profile name profile-name

    A traffic profile is created, and the traffic profile view is displayed.

    By default, the system provides the traffic profile default.

  4. Run:

    user-isolate { l2 | all }

    The user isolation function is enabled.

    By default, user isolation is disabled in a traffic profile.

  5. Run:

    quit

    Return to the WLAN view.

  6. Run:

    vap-profile name profile-name

    The VAP profile view is displayed.

  7. Run:

    traffic-profile profile-name

    The traffic profile is bound to the VAP profile.

    By default, the traffic profile default is bound to a VAP profile.

Verifying the Configuration
  • Run the display traffic-profile { all | name profile-name } command to check the user isolation configuration in a traffic profile.

Translation
Download
Updated: 2019-01-11

Document ID: EDOC1000176006

Views: 119055

Downloads: 309

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