Configuring Hierarchical Traffic Policing

Prerequisites

MQC has been configured to implement traffic policing for service flows, for which hierarchical traffic policing is to be configured. For details, see Configuring MQC to Implement Traffic Policing.

Context

The device supports hierarchical traffic policing. After the system uses MQC to implement traffic policing (level-1 CAR) for service flows matching a traffic classifier in a traffic policy, the system aggregates all the service flows matching the traffic classifiers associated with the level-1 CAR in the same traffic policy and performs traffic policing (level-2 CAR) for the aggregated flow. Hierarchical traffic policing implements statistical multiplexing of traffic and fine-grained service control.

Procedure

1. Run system-view

   The system view is displayed.

2. Run qos car car-name cir cir-value [ cbs cbs-value [ pbs pbs-value ] | pir pir-value [ cbs cbs-value pbs pbs-value ] ]

   A QoS CAR profile is created and CAR parameters are configured.

3. Run traffic behavior behavior-name

   The traffic behavior view is displayed.

4. Run traffic behavior behavior-name

   The traffic behavior view is displayed.

5. Run car car-name share

   The aggregated CAR action is configured.

   Before configuring the aggregated CAR action, you need to configure a CAR action in the traffic behavior view. Since a CAR action has been configured during configuration of MQC for traffic policing, you do not need to configure it again.

   

   • Only the S5720-EI, S5720-HI, S5730-HI, S5731-H, S5731-S, S5731S-H, S5731S-S, S5732-H, S6720-HI, S6730-H, S6730S-H, S6730-S, and S6730S-S support aggregated CAR.

   • The traffic policy defining the aggregated CAR action can be used only in the inbound direction.

   • After aggregated CAR is configured, all the rules in the traffic classifiers bound to the same traffic behavior share the CAR index. The system aggregates all the flows matching these traffic classifiers and uses CAR to limit the rate of the flows. If the traffic classifiers define both Layer 2 and Layer 3 information, the aggregated CAR configuration is invalid.

Verifying the Configuration

• Run the display traffic classifier user-defined [ classifier-name ] command to check the traffic classifier configuration.
• Run the display traffic behavior user-defined [ behavior-name ] command to check the traffic behavior configuration.

• Run the display traffic policy user-defined [ policy-name [ classifier classifier-name ] ] command to check the configuration of a specified user-defined traffic policy.

• Run the display traffic-applied [ interface [ interface-type interface-number ] | vlan [ vlan-id ] ] { inbound | outbound } [ verbose ] command to check information about ACL-based simplified and MQC-based traffic policies applied to the system, a VLAN, or an interface.

  

  The display traffic-applied command cannot be used to check information about ACL-based simplified and MQC-based traffic policies applied to a sub-interface. However, traffic policies can be applied to a sub-interface.

• Run the display traffic policy { interface [ interface-type interface-number [.subinterface-number ] ] | vlan [ vlan-id ] | ssid-profile [ ssid-profile-name ] | global } [ inbound | outbound ] command to check the traffic policy configuration.

  

  Only the S5720-EI, S5720-HI, S5730-HI, S5731-H, S5731-S, S5731S-H, S5731S-S, S5732-H, S6720-EI, S6720-HI, S6720S-EI, S6730-H, S6730S-H, S6730-S, and S6730S-S support sub-interfaces.

  Only the S5720-HI, S5730-HI, S5731-H, S5731S-H, S5732-H, S6720-HI, S6730S-H, and S6730-H support ssid-profile [ ssid-profile-name ].

• Run the display traffic-policy applied-record [ policy-name ] command to check the application records of a specified traffic policy.