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).
Configuring Interface-Based Traffic Policing

Configuring Interface-Based Traffic Policing

By means of traffic policing, you can control the total traffic and burst traffic that enter or leave a network from a specified link. When some pre-defined condition occurs, traffic policing controls the traffic from that link. For example, if the traffic volume from a specified link is over a set amount, traffic policing decreases traffic from that link by dropping some packets or lowering the priority of processing packets from that link.

Usage Scenario

If users' traffic is not limited, continuous burst data from numerous users congest the network. To fully utilize network resources and better serve more users, user traffic must be limited. Traffic policing is a traffic control method that limits network traffic and controls the usage of network resources by monitoring traffic properties on the network. You can implement traffic policing on both inbound and outbound interfaces.

Interface-based traffic policing controls all traffic that enters an interface without considering the types of packet. This method is used on the router located at the core of a network. The router has the following features in interface-based traffic policing.

The NE40E supports the configuration of traffic policing for both the incoming and outgoing traffic on a Layer 3 main interface. Traffic policing is one of two types: traffic policing using a single token bucket and traffic policing using two token buckets. You can choose the type of traffic policing based on your network conditions.

  • If the network traffic is simple, you can configure the single-bucket traffic policing, using the parameters cir and cbs.

  • If the network traffic is complex, you can configure the two-bucket traffic policing, using the parameters cir, pir, cbs, and pbs.

Pre-configuration Tasks

Before configuring the interface-based traffic policing, complete the following tasks:

  • Configure the physical parameters of interfaces.

  • Configure the link layer attributes of interfaces to ensure their operation.

  • Configure IP addresses for interfaces.

  • Enable routing protocols and ensure that routers interwork with each other.

Procedure

  1. Run system-view

    The system view is displayed.

  2. Perform the following operations based on the interfaces on which traffic policing will be used:

    • On a Layer 3 interface:
      1. To enter the Layer 3 interface view, run the interface interface-type interface-number command.

    • On a 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.

        Perform either of the following operations to add the Layer 2 interface to VLANs:

        • To add the Layer 2 interface to a specific VLAN, run the port default vlan vlan-id command.
          NOTE:
          Before running the port default vlan vlan-id command, ensure that the specific VLAN has been created.
        • To configure a range of VLANs from which packets are allowed to pass through the interface, run the port trunk allow-pass vlan { { vlan-id1 [ to vlan-id2 ] } & <1-10> | all } command.

  3. Run qos car { { cir cir-value [ pir pir-value ] } | { cir-percentage cir-percentage-value [ pir-percentage pir-percentage-value ] } } [ cbs cbs-value [ pbs pbs-value ] ] [ green { discard | pass [ service-class class color color ] } | yellow { discard | pass [ service-class class color color ] } | red { discard | pass [ service-class class color color ] } ] * { inbound | outbound } [ vlan { vlan-id1 [ to vlan-id2 ] & <1-10> } ] [ identifier { none | vid | ce-vid | vid-ce-vid } ] [ color-aware ]

    CAR is configured on the interface.

    NOTE:
    • The parameter [ vlan { vlan-id1 [ to vlan-id2 & <1–10> ] configures traffic policing for VLAN packets and takes effect only for Layer 2 interfaces. If you run this command on a Layer 3 interface, you cannot specify VLAN IDs in this command. If this command is run on a Layer 2 interface, you must specify VLAN IDs in this command.
    • When an interface is configured with both interface-based CAR and traffic classification-based CAR actions, the number of packets and bytes on which traffic classification-based CAR actions are performed is not counted in the interface-based CAR statistics.
    • When both MF-based CAR and interface-based CAR are configured, MF-based CAR takes effect, and then interface-based CAR does. When both broadcast suppression and interface-based CAR are configured, interface-based CAR applies only to known unicast packets, and broadcast suppression applies to broadcast packets. when CAR is configured for both packets sent to the CPU and packets sent to the interface, only the CAR statistics on packets sent to the CPU are collected.
    • Interface-based CAR cannot be configured on the member interface of trunk.
    • The cir and pir are expressed in kbit/s, the cbs and pbs are expressed in bytes.

  4. Run commit

    The configuration is committed.

Checking the Configuration

Perform the following operations to check the previous configuration:

  • Run the display interface [ interface-type [ interface-number ]] command to check the traffic information of the interface.

  • Run the display car statistics interface interface-type interface-number { inbound | outbound } command to check CAR statistics in a specific direction on a specific Layer 3 interface.

  • Run the display car statistics interface interface-type interface-number vlan vlan-id { inbound | outbound } command to check CAR statistics in a specific direction on a specific Layer 2 interface.

If the configuration is successful, you can view statistics on traffic in the specified direction on a specified interface by running the display car statistics interface interface-type interface-number { inbound | outbound } command. The statistics include the amount of passed traffic and the rate at which the traffic is forwarded, in packets and bytes, and the amount of discarded traffic and the rate at which the traffic is discarded, in packets and bytes.

<HUAWEI> display car statistics interface gigabitethernet 1/0/0 outbound
interface GigabitEthernet1/0/0
   outbound
     Committed Access Rate:
   CIR 200(Kbps), PIR 0(Kbps), CBS 400(byte), PBS 500(byte)
   Conform Action: pass
   Yellow Action: pass
   Exceed Action: discard
      Passed: 840 bytes, 15 packets
      Dropped: 56 bytes, 1 packets
      Last 30 seconds passed rate: 0 bps, 0 pps
      Last 30 seconds dropped rate: 0 bps, 0 pps  
Translation
Download
Updated: 2019-01-03

Document ID: EDOC1100055024

Views: 21950

Downloads: 112

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