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

NE40E V800R010C10SPC500 Configuration Guide - QoS 01

This is NE40E V800R010C10SPC500 Configuration Guide - QoS
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).
Defining a Traffic Behavior and Configuring Actions

Defining a Traffic Behavior and Configuring Actions

This section describes the traffic behaviors supported by the NE40E and how to configure actions.

Context

The NE40E supports various types of traffic behaviors. You can choose one or more behaviors to meet your requirements.

Procedure

  • Configure traffic policing actions.

    Do as follows on the router.

    1. Run system-view

      The system view is displayed.

    2. Run traffic behavior behavior–name

      A traffic behavior is configured, and the traffic behavior view is displayed.

    3. Run car { cir cir-value [ pir pir-value ] } [ cbs cbs-value [ pbs pbs-value ] ] [ adjust adjust-vlaue ] [ green { discard | pass [ remark dscp dscp-value | service-class class color color ] } | yellow { discard | pass [ remark dscp dscp-value | service-class class color color ] } | red { discard | pass [ remark dscp dscp-value | service-class class color color ] } ] * [ summary ] [ color-aware ] [ limit-type pps ]

      A traffic policing action is configured.

      This command is cyclic in nature. If this command is configured for multiple times, only the last configuration takes effect.

      NOTE:

      If the CoS of a packet is re-marked as EF, BE, CS6, or CS7, the packet can be re-marked green only.

    4. Run user-queue cir cir-value [ [ pir pir-value ] | [ flow-queue flow-queue-name ] | [ flow-mapping mapping-name ] | [ user-group-queue group-name ] | [ service-template service-template-name ] ]*

      The class-based HQOS parameters for the specified traffic behavior is configured.

      The outgoing traffic supports class-based HQoS scheduling only when the traffic policy works in unshared mode and is applied to an ETM subcard.
      NOTE:
      The user-queue and car commands cannot be both configured in the same traffic behavior.

    5. (Optional) Run flow-car cir cir-value [ pir pir-value ] [ cbs cbs-value [ pbs pbs-value ] ] identifier { source-ip | destination-ip }

      Flow CAR is implemented for flows with the source or destination IP addresses residing on the specified network segment.

    6. Run commit

      The configuration is committed.

    7. Run bridge-domain bd-idtraffic-policy-action car disable [ exclude ] slot slot-idvxlan-mode

      The CAR function is disabled in the traffic policy in VXLAN mode on a specified board. This command can also be run in the VPN view.

  • Configure forcible traffic classification.

    Do as follows on the router:

    1. Run system-view

      The system view is displayed.

    2. Run traffic behavior behavior-name

      A traffic behavior is configured, and the traffic behavior view is displayed.

    3. Run service-class service-class color color

      Packets with a certain CoS are colored.

    4. Run service-class service-class color color track { master | slave } bfd-session session-name bfd-session-name

      The function of marking matching packets' CoS and color based on the status of the specified BFD session is configured.

    5. Run commit

      The configuration is committed.

  • Set the packet precedence.

    Do as follows on the router.

    1. Run system-view

      The system view is displayed.

    2. Run traffic behavior behavior–name

      A traffic behavior is configured, and the traffic behavior view is displayed.

    3. Perform the following operation as required.

      To re-mark the DSCP value of VXLAN packets, run the remark dscp dscp-value command.

    4. Run commit

      The configuration is committed.

  • Cascading a traffic policy.

    The ACL rules are generally used for redirection in the traffic behavior. However, the specification of ACL rules is limited. When ACL rules defined for MF classification do not meet the live network requirements, you can redirect the traffic behavior to a configured traffic policy to implement cascaded MF classification.

    1. Run system-view

      The system view is displayed.

    2. Run traffic behavior behavior–name

      A traffic behavior is configured, and the traffic behavior view is displayed.

    3. Run traffic-policy policy-name

      The traffic behavior is redirected to the traffic policy.

      • Cascading a traffic policy over another will cause the the device forwarding performance to deteriorate.
      • When the traffic on an interface matches the cascaded traffic policy:
        • The forwarding behavior and cascading a traffic policy are mutually exclusive.
        • If the traffic behaviors in the two traffic policies are different, they can be individually implemented.
        • If the traffic behaviors in the two traffic policies are the same, the specific behavior configuration in the cascaded traffic policy takes effect.
      • The parameters specified for a traffic policy, such as inbound, outbound, link-layer, mpls-layer, and all-layer, are inherited by the cascaded traffic policy.

      • When the traffic behaviors for two-level ACLs are service-class, level-1 service-class preferentially takes effect. However, if level 1 service-class carries no-remark, level-2 service-class preferentially takes effect.

    4. (Optional) Run hierarchical-car enable

      Hierarchical CAR is enabled in a cascaded traffic policy.

      When a traffic policy is configured in a traffic behavior, CAR can also be configured in the traffic policy to implement hierarchical CAR.

    5. Run commit

      The configuration is committed.

Translation
Download
Updated: 2019-01-03

Document ID: EDOC1100055024

Views: 23167

Downloads: 115

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