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 V200R013C00 Configuration Guide - QoS

This document describes the configurations of QoS functions, including MQC, priority mapping, traffic policing, traffic shaping, interface-based rate limiting, congestion avoidance, congestion management, packet filtering, redirection, traffic statistics, ACL-based simplified traffic policy, and HQoS.
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).
Applying a Traffic Policy

Applying a Traffic Policy

Pre-configuration Tasks

Before applying a traffic policy, configure the traffic policy.

Procedure

  • Applying a traffic policy to an interface
    1. Run system-view

      The system view is displayed.

    2. Run interface interface-type interface-number[.subinterface-number ]

      The interface view or sub-interface view is displayed.

      NOTE:
      • Only the E series, X series, and SC series cards on the S12700 support Ethernet sub-interface configuration. For details about the cards, see Cards in the Hardware Description.

      • Only hybrid and trunk interfaces on the preceding series of cards support Ethernet sub-interface configuration.
      • After you run the undo portswitch command to switch Layer 2 interfaces on the preceding series of cards into Layer 3 interfaces, you can configure Ethernet sub-interfaces on the interfaces.

      • The SA series cards do not support Ethernet sub-interface configuration and cannot forward IP traffic to Ethernet sub-interfaces on other cards.

      • You are advised to add a member interface to an Eth-Trunk and then configure an Eth-Trunk sub-interface. The Eth-Trunk sub-interface can be successfully configured only when the card on which the member interface locates supports Ethernet sub-interface configuration.

      • VLAN termination sub-interfaces cannot be created on a VCMP client.
    3. Run traffic-policy policy-name { inbound | outbound }

      A traffic policy is applied to the interface or sub-interface.

      A traffic policy can only be applied to one direction on an interface but can be applied to different directions on different interfaces. After a traffic policy is applied to an interface, the system performs traffic policing for all the incoming or outgoing packets that match traffic classification rules on the interface.

      NOTE:
      • Sub-interfaces support only inbound.

      • You are not advised to apply a traffic policy containing remark 8021p, remark cvlan-id, or remark vlan-id to the outbound direction of an untagged interface. This configuration may cause incorrect information in the packets.

      • On the ET1D2L02QSC0 card, when an interface among interfaces 1-20 and an interface among interfaces 21-40 are added to the same Eth-Trunk or VLAN, and outgoing traffic of the Eth-Trunk or VLAN is rate-limited by car, the outgoing traffic rate is 2 times the CAR value.

      • Applying traffic policies consumes ACL resources. If ACL resources are insufficient, some traffic policies will fail to be applied. For example, if an if-match rule in a traffic policy occupies one ACL, one ACL is occupied for each interface to which the traffic policy is applied. When a traffic policy is applied to L VLANs on a device with N LPUs, L*N ACLs are occupied. When a traffic policy is applied globally on a device with N LPUs, N ACLs are occupied. For details about ACLs occupied by if-match rules, see Table 3 in "Licensing Requirements and Limitations for MQC."

  • Applying a traffic policy to a VLAN
    1. Run system-view

      The system view is displayed.

    2. Run vlan vlan-id

      The VLAN view is displayed.

    3. Run traffic-policy policy-name { inbound | outbound }

      A traffic policy is applied to the VLAN.

      Only one traffic policy can be applied to the inbound or outbound direction of a VLAN.

      The system performs traffic policing for the packets that belong to the VLAN and match traffic classification rules in the inbound or outbound direction. However, the traffic policy does not take effect for packets in VLAN 0.

  • Applying a traffic policy to a VLANIF interface
    1. Run system-view

      The system view is displayed.

    2. Run interface vlanif vlan-id

      The VLANIF interface view is displayed.

    3. Run traffic-policy policy-name inbound

      A traffic policy is applied to the VLANIF interface.

      Only one traffic policy can be applied to the inbound direction on a VLANIF interface, but a traffic policy can be applied to the inbound direction on different VLANIF interfaces.

      A traffic policy cannot be applied to a VLANIF interface corresponding to the super-VLAN or MUX VLAN.

      On X series cards, a traffic policy applied to a VLANIF interface takes effect only for unicast packets on the VLANIF interface. For other cards, a traffic policy applied to a VLANIF interface takes effect only for unicast packets and Layer 3 multicast packets on the VLANIF interface.

      NOTE:
      A traffic policy cannot be applied to a VLANIF interface when the bound traffic behaviors define the following actions:
      • remark vlan-id
      • remark cvlan-id
      • add-tag vlan-id
      • remark 8021p
      • remark flow-id
      • mac-address learning disable
  • Applying a traffic policy to the system or an LPU
    1. Run system-view

      The system view is displayed.

    2. Run traffic-policy policy-name global { inbound | outbound } [ slot slot-id ]

      A traffic policy is applied to the system or an LPU.

      Only one traffic policy can be applied to one direction in the system or LPU. A traffic policy cannot be applied to the same direction in the system and LPU simultaneously.

Translation
Download
Updated: 2019-04-08

Document ID: EDOC1100065653

Views: 18822

Downloads: 45

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