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).
Applying a Traffic Policy

Applying a Traffic Policy

A class-based policy does not take effect unless it is applied to an interface.

Context

Do as follows on the router:

Procedure

  1. Run system-view

    The system view is displayed.

  2. Run interface interface-type interface-number

    The interface view is displayed.

  3. Perform the following operations based on the interfaces on which a traffic policy is used:

    • Apply an MF classification-based traffic policy on a Layer 3 interface.
      1. To enter the Layer 3 interface view, run the interface interface-type interface-number command.
      2. To apply a traffic policy to the Layer 3 interface, run the traffic-policy policy-name { inbound | outbound } [ all-layer | link-layer | mpls-layer ] command.
        NOTE:

        If you specify link-layer, the router matches Layer 2 information about packets with the traffic policy and performs a corresponding action.

        If you specify mpls-layer, the router performs MF classification based on MPLS packet header information.

    • Apply an MF classification-based traffic policy on a Layer 2 interface. You can specify a VLAN ID range to apply the traffic policy on the Layer 2 interface.
      1. To enter the Layer 3 interface view, run the interface interface-type interface-number command.
      2. To change the interface mode from Layer 3 to Layer 2, run the portswitch command.
      3. To add the Layer 2 interface to specific VLANs in tagged mode, run the port trunk allow-pass vlan { { vlan-id1 [ to vlan-id2 ] } &<1-10> | all } command.
      4. To apply a traffic policy on the Layer 2 interface, run the traffic-policy policy-name { inbound | outbound } vlan vlan-id1 [ to vlan-id2 ] [ all-layer | link-layer | mpls-layer ] command.
    • Apply an MF classification-based traffic policy on a EVC Layer 2 sub-interface. You can specify a bandwidth allocation type to apply the traffic policy on the EVC Layer 2 sub-interface.
      1. To enter the EVC Layer 2 sub-interface view, run the interface interface-type interface-number.subnum mode l2 command.
      2. To apply a traffic policy on the EVC Layer 2 sub-interface, run the traffic-policy policy-name { inbound | outbound } identifier { none | vid | ce-vid | vid-ce-vid } [ all-layer | link-layer | mpls-layer ] command.
        NOTE:

        The parameter identifier specified bandwidth allocation type must be the same with the one configured on the EVC Layer 2 sub-interface.

    • Apply an MF classification-based traffic policy on a QinQ termination sub-interface. You can specify a PVLAN ID and CVLAN ID range to apply the traffic policy on the QinQ termination sub-interface.
      1. To enter the sub-interface view, run the interface interface-type interface-number.subinterface-number command.
      2. To set a VLAN ID range for the sub-interface and configure the sub-interface to remove the tags from double-tagged packets, run the encapsulation qinq-termination [ local-switch | rt-protocol ] command.
      3. To configure the sub-interface as a QinQ termination sub-interface, run the qinq termination pe-vid pe-vid [ to high-pe-vid ] ce-vid { low-ce-vid [ to high-ce-vid ] } [ vlan-group group-id ] command.
      4. To apply a traffic policy on the QinQ termination sub-interface, run the traffic-policy policy-name { inbound | outbound } pe-vid pe-vid ce-vid ce-vid1 [ to ce-vid2 ] [ all-layer | link-layer | mpls-layer ] command.
    • Apply an MF traffic classification-based traffic policy on a VBDIF interface.
      1. To create a bridge domain, run the bridge-domain bd-id command.
      2. To create a VBDIF interface and display the VBDIF interface view, run the interface vbdif bd-id command.
      3. To apply a traffic policy on the VBDIF interface, run the traffic-policy policy-name { inbound | outbound } command.
      NOTE:

      If traffic received by a VBDIF interface comes from multiple interfaces that reside on different forwarding chips and the policy CAR is applied, the limited bandwidth of each forwarding chip is the configured limited bandwidth, and the actual valid limited bandwidth of the VBDIF interface is the sum of the bandwidth of each forwarding chip.

    • (Optional) To apply a traffic policy to a VPN instance, perform the following operations:
      1. Run the ip vpn instance vpn-instance-name command to enter the VPN instance view.
      2. Run the traffic-policy policy-name network inbound command to apply a traffic policy to the VPN instance.
    • (Optional) To apply a traffic policy to a VSI, perform the following operations:
      1. Run the vsi vsi-instance-name command to enter the VSI view.
      2. Perform either of the following operations as required:
        • Run the traffic-policy policy-name network inbound link-layer command to apply a network-side traffic policy to the VSI.
        • Run the traffic-policypolicy-name ac-mode { inbound | outbound } [ link-layer | all-layer ] command to apply a user-side traffic policy to the VSI.
    • (Optional) To apply a traffic policy to a VSI, perform the following operations:
      1. Run the evpn vpn-instance vpn-instance-name bd-mode command to enter the EVPN view.
      2. Run the traffic-policy policy-name network inbound link-layer command to apply a traffic policy to the EVPN.

  4. (Optional) Run qos traffic-car member-link-scheduler distribute

    When CAR is configured on a trunk interface, the sum of all the member interfaces' bandwidth complies with the CAR settings.

  5. Run commit

    The configuration is committed.

Translation
Download
Updated: 2019-01-03

Document ID: EDOC1100055024

Views: 22049

Downloads: 114

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