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

CLI-based Configuration Guide - QoS

AR100-S, AR110-S, AR120-S, AR150-S, AR160-S, AR200-S, AR1200-S, AR2200-S, and AR3200-S V200R009

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 a Traffic Policy

Configuring a Traffic Policy

Context

A traffic classifier in the traffic policy differentiates users. Before configuring a traffic policy, ensure that the sub traffic policy has been configured.

You can configure either of the following combinations in the traffic behavior of the traffic policy when traffic policy nesting is configured in the outbound direction on an interface:

  • GTS + sub traffic policy: User packets are evenly scheduled and the interface bandwidth is evenly distributed to users.

  • GTS + AF + sub traffic policy: You can configure AF and set the percentage of assured bandwidth to the available bandwidth of the interface.

    This combination is recommended so that you can configure assured bandwidth for each user.

  • AF + sub traffic policy: You can configure AF and set the percentage of assured bandwidth to the available bandwidth of the interface.

  • EF + sub traffic policy: When a traffic policy is bound to EF queues, subscriber queues are scheduled in PQ mode. User packets with higher priorities are forwarded first.

When traffic policy nesting is configured in the outbound direction on a sub-interface:
  • If other QoS actions except traffic shaping, adaptive traffic shaping, congestion management, and congestion avoidance are configured in the traffic behavior of the sub traffic policy, you can configure only traffic shaping + sub traffic policy, traffic shaping + AF + sub traffic policy, or EF + sub traffic policy in the traffic behavior of the traffic policy.

  • If traffic shaping, congestion management, or congestion avoidance is configured in the traffic behavior of the sub traffic policy, only the default traffic classifier default-class or any can be configured in the traffic classifier of the traffic policy and only traffic shaping can be configured in the traffic behavior associated with the default traffic classifier.

To apply traffic policy nesting to the inbound direction of an interface or a sub-interface, the traffic behavior of a traffic policy only can be statistic and sub traffic policy.

NOTE:

The sub traffic policy configured for a traffic behavior of a traffic policy cannot be the same as the traffic policy.

Procedure

  1. Configure a traffic classifier.

    Configure a traffic classifier by selecting appropriate traffic classification rules. For details, see Configuring a Traffic Classifier.

  2. Configure a traffic behavior.

    • When traffic policy nesting is configured in the outbound direction of a main interface, perform the following operations.

      • Configure GTS + sub traffic policy.
        1. Run system-view

          The system view is displayed.

        2. Run traffic behavior behavior-name

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

        3. Run gts cir { cir-value [ cbs cbs-value ] | pct pct-value } [ queue-length queue-length ] or gts adaptation-profile adaptation-profile-name

          The GTS action is configured in the traffic behavior.

        4. Run traffic-policy policy-name

          A sub traffic policy is bound to the traffic behavior.

        5. (Optional) Run statistic enable

          The traffic statistics function is enabled.

        6. Run quit

          Exit from the traffic behavior view.

      • Configure GTS + AF + sub traffic policy.
        1. Run system-view

          The system view is displayed.

        2. Run traffic behavior behavior-name

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

        3. Run gts cir { cir-value [ cbs cbs-value ] | pct pct-value } [ queue-length queue-length ] or gts adaptation-profile adaptation-profile-name

          The GTS action is configured in the traffic behavior.

        4. Run queue af bandwidth { bandwidth | pct percentage }

          AF and the minimum bandwidth are configured.

        5. Run traffic-policy policy-name

          A sub traffic policy is bound to the traffic behavior.

        6. (Optional) Run statistic enable

          The traffic statistics function is enabled.

        7. Run quit

          Exit from the traffic behavior view.

      • Configure AF + sub traffic policy.
        1. Run system-view

          The system view is displayed.

        2. Run traffic behavior behavior-name

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

        3. Run queue af bandwidth { bandwidth | pct percentage }

          AF and the minimum bandwidth are configured.

        4. Run traffic-policy policy-name

          A sub traffic policy is bound to the traffic behavior.

        5. (Optional) Run statistic enable

          The traffic statistics function is enabled.

        6. Run quit

          Exit from the traffic behavior view.

      • Configure EF + sub traffic policy.
        1. Run system-view

          The system view is displayed.

        2. Run traffic behavior behavior-name

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

        3. Run queue ef bandwidth { bandwidth [ cbs cbs-value ] | pct percentage [ cbs cbs-value ] }

          EF and the minimum bandwidth are configured.

        4. Run traffic-policy policy-name

          A sub traffic policy is bound to the traffic behavior.

        5. (Optional) Run statistic enable

          The traffic statistics function is enabled.

        6. Run quit

          Exit from the traffic behavior view.

    • When traffic policy nesting is configured in the outbound direction of a sub-interface, perform the following operations.

      • Configure traffic shaping + sub traffic policy.
        1. Run system-view

          The system view is displayed.

        2. Run traffic behavior behavior-name

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

        3. Run gts cir { cir-value [ cbs cbs-value ] | pct pct-value } [ queue-length queue-length ]

          Traffic shaping is configured.

        4. Run traffic-policy policy-name

          A sub traffic policy is bound to the traffic behavior.

        5. (Optional) Run statistic enable

          The traffic statistics function is enabled.

        6. Run quit

          Exit from the traffic behavior view.

      • Configure traffic shaping + AF + sub traffic policy.
        1. Run system-view

          The system view is displayed.

        2. Run traffic behavior behavior-name

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

        3. Run gts cir { cir-value [ cbs cbs-value ] | pct pct-value } [ queue-length queue-length ]

          Traffic shaping is configured.

        4. Run queue af bandwidth { bandwidth | pct percentage }

          AF and the minimum bandwidth are configured.

        5. Run traffic-policy policy-name

          A sub traffic policy is bound to the traffic behavior.

        6. (Optional) Run statistic enable

          The traffic statistics function is enabled.

        7. Run quit

          Exit from the traffic behavior view.

      • Configure EF + sub traffic policy.
        1. Run system-view

          The system view is displayed.

        2. Run traffic behavior behavior-name

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

        3. Run queue ef bandwidth { bandwidth [ cbs cbs-value ] | pct percentage [ cbs cbs-value ] }

          EF and the minimum bandwidth are configured.

        4. Run traffic-policy policy-name

          A sub traffic policy is bound to the traffic behavior.

        5. (Optional) Run statistic enable

          The traffic statistics function is enabled.

        6. Run quit

          Exit from the traffic behavior view.

      • Configure traffic shaping.
        1. Run system-view

          The system view is displayed.

        2. Run traffic behavior behavior-name

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

        3. Run gts cir { cir-value [ cbs cbs-value ] | pct pct-value } [ queue-length queue-length ]

          Traffic shaping is configured.

        4. (Optional) Run statistic enable

          The traffic statistics function is enabled.

        5. Run quit

          Exit from the traffic behavior view.

    • Configure traffic policy nesting in the inbound direction of an interface or a sub-interface.
      • Configure statistic + sub traffic policy.
        1. Run system-view

          The system view is displayed.

        2. Run traffic behavior behavior-name

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

        3. Run statistic enable

          The traffic statistics function is enabled in a traffic behavior.

        4. Run traffic-policy policy-name

          A sub traffic policy is bound to the traffic behavior.

        5. Run quit

          Exit from the traffic policy view.

  3. Associate the traffic classifier and the traffic behavior with the traffic policy.

    Create a traffic policy, and associate the traffic classifier and traffic behavior with the traffic policy. For details, see Configuring a Traffic Policy.

    NOTE:
    • Each traffic policy or sub traffic policy supports a maximum of 1024 pairs of traffic classifiers and traffic behaviors.
    • Each traffic behavior in the traffic policy can be bound to only one sub traffic policy, whereas different traffic behaviors can be bound to different sub traffic policies.
    • If a traffic policy is bound to multiple pairs of traffic classifiers and traffic behaviors, matching rules in the traffic classifiers must be different. If matching rules are the same, packets of the same type are processed incorrectly because different actions are taken for these packets.

Translation
Download
Updated: 2019-05-17

Document ID: EDOC1000174115

Views: 39892

Downloads: 28

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