classifier-name: Specifies a traffic class by its name, a case-sensitive string of 1 to 31 characters. If you do not specify a traffic class, this command displays all traffic classes.

slot slot-number: Specifies a card by its slot number. If you do not specify a card, this command displays the traffic classes for the active MPU. (In standalone mode.)

chassis chassis-number slot slot-number: Specifies a card on an IRF member device. The chassis-number argument represents the member ID of the IRF member device. The slot-number argument represents the slot number of the card. If you do not specify this option, the command displays the traffic classes for the global active MPU. (In IRF mode.)

cpu cpu-number: Specifies a CPU by its number. This option is available only if multiple CPUs are available on the specified slot.

Examples

# Display all user-defined traffic classes.

<Sysname> display traffic classifier user-defined

User-defined classifier information:

Classifier: 1 (ID 100)

Operator: AND

Rule(s) :

If-match acl 2000

Classifier: 2 (ID 101)

Operator: AND

Rule(s) :

If-match protocol ipv6

Classifier: 3 (ID 102)

Operator: AND

Rule(s) :

-none-

# Display the system-defined traffic class (default-class).

<Sysname> display traffic classifier system-defined default-class

System-defined classifier information:

Classifier: default-class (ID 0)

Operator: AND

Rule(s) :

If-match any

Table 1 Command output

Field	Description
Classifier	Traffic class name and its match criteria.
Operator	Match operator you set for the traffic class. If the operator is AND, the traffic class matches the packets that match all its match criteria. If the operator is OR, the traffic class matches the packets that match any of its match criteria.
Rule(s)	Match criteria.

if-match

Use if-match to define a match criterion.

Use undo if-match to delete a match criterion.

Syntax

if-match [ not ] match-criteria

undo if-match [ not ] match-criteria

Default

No match criterion is configured.

Views

Traffic class view

Predefined user roles

network-admin

context-admin

vsys-admin

Parameters

not: Matches packets that do not conform to the specified criterion.

match-criteria: Specifies a match criterion. Table 2 shows the available match criteria.

Table 2 Available match criteria

Option	Description
acl [ ipv6 \| mac \| user-defined ] { acl-number \| name acl-name }	Matches an ACL. The value range for the acl-number argument is as follows: · 2000 to 3999 for IPv4 ACLs. · 2000 to 3999 for IPv6 ACLs. The acl-name argument is a case-insensitive string of 1 to 63 characters, which must start with an English letter. To avoid confusion, make sure the argument is not all. If no VPN instance is specified in an ACL rule, the ACL rule takes effect on only non-VPN packets.
app-group group-name	Matches an application group. The group-name argument specifies an application group by its name. The application group must have been created. A nonexistent application group cannot match packets. For more information about creating application groups, see APR in Security Configuration Guide.
application app-name	Matches an application. The app-name argument specifies a user-created application by its name.
any	Matches all packets.
classifier classifier-name	Matches a class. The classifier-name argument specifies a class by its name.
control-plane protocol protocol-name&<1-8>	Matches control plane protocols. The protocol-name&<1-8> argument specifies a space-separated list of up to eight system-defined control plane protocols. For available system-defined control plane protocols, see Table 3.
control-plane protocol-group protocol-group-name	Matches a control plane protocol group. The protocol-group-name argument can be critical, important, management, monitor, or normal.
customer-dot1p dot1p-value&<1-8>	Matches 802.1p priority values in inner VLAN tags of double-tagged packets. The dot1p-value&<1-8> argument specifies a space-separated list of up to eight 802.1p priority values. The value range for the dot1p-value argument is 0 to 7.
customer-vlan-id vlan-id-list	Matches VLAN IDs in inner VLAN tags of double-tagged packets. The vlan-id-list argument specifies a space-separated list of up to 10 VLAN items. Each item specifies a VLAN or a range of VLANs in the form of vlan-id1 to vlan-id2. The value for vlan-id2 must be greater than or equal to the value for vlan-id1. The value range for the vlan-id argument is 1 to 4094.
destination-mac mac-address	Matches a destination MAC address. This option takes effect only on Ethernet interfaces.
dscp dscp-value&<1-8>	Matches DSCP values. The dscp-value&<1-8> argument specifies a space-separated list of up to eight DSCP values. The value range for the dscp-value argument is 0 to 63 or keywords shown in Table 5.
inbound-interface interface-type interface-number	Matches an input interface specified by its type and number. If this option is configured in a traffic class with logic AND operator, the traffic class is no longer in effect after the card or subcard where the input interface resides is removed. After the removed card or subcard is reinserted, the traffic class takes effect again. If you do not reinsert the card or subcard and add other match criteria to the traffic class, the traffic class does not take effect again.
ip-precedence ip-precedence-value&<1-8>	Matches IP precedence values. The ip-precedence-value&<1-8> argument specifies a space-separated list of up to eight IP precedence values. The value range for the ip-precedence-value argument is 0 to 7.
mpls-exp exp-value&<1-8>	Matches MPLS EXP values. The exp-value&<1-8> argument specifies a space-separated list of up to eight EXP values. The value range for the exp-value argument is 0 to 7. MPLS packets do not support IP-related match criteria.
packet-length { min min-value \| max max-value } *	Matches the packet length. The min-value argument specifies the minimum packet length in bytes. The max-value argument specifies the maximum packet length in bytes. The maximum packet length must be greater than or equal to the minimum packet length.
protocol protocol-name	Matches a protocol. The protocol-name argument can be ip or ipv6.
qos-local-id local-id-value	Matches a local QoS ID in the range of 1 to 4095.
rtp start-port start-port-number end-port end-port-number	Matches RTP protocol ports. The value ranges for the start-port-number and end-port-number arguments are both 2000 to 65535. This criterion matches RTP packets with an even UDP destination port number in the specified RTP port number range.
source-mac mac-address	Matches a source MAC address. This option takes effect only on Ethernet interfaces.

Table 3 Available system-defined control plane protocols

Protocol	Description
default	Protocol packets other than the following packet types
arp	ARP packets
bgp	BGP packets
bgp4+	IPv6 BGP packets
dhcp	DHCP packets
dhcp6	IPv6 DHCP packets
ftp	FTP packets
http	HTTP packets
https	HTTPS packets
icmp	ICMP packets
icmpv6	ICMPv6 packets
isis	IS-IS packets
ldp	LDP packets
ldp6	IPv6 LDP packets
msdp	MSDP packets
ntp	NTP packets
ospf-multicast	OSPF multicast packets
ospf-unicast	OSPF unicast packets
ospf3-multicast	OSPFv3 multicast packets
ospf3-unicast	OSPFv3 unicast packets
pim-multicast	PIM multicast packets
pim-unicast	PIM unicast packets
pim6-multicast	IPv6 PIM multicast packets
pim6-unicast	IPv6 PIM unicast packets
radius	RADIUS packets
rip	RIP packets
ripng	RIPng packets
rsvp	RSVP packets
snmp	SNMP packets
ssh	SSH packets
tacacs	TACACS packets
telnet	Telnet packets
tftp	TFTP packets
vrrp	VRRP packets
vrrp6	IPv6 VRRP packets

‌

Usage guidelines

In a traffic class with the logical OR operator, you can configure multiple if match commands for any of the available match criteria.

When you configure a match criterion that can have multiple values in one if-match command, follow these restrictions and guidelines:

· You can specify up to eight values for any of the following match criteria in one if-match command:

· If a packet matches one of the specified values, it matches the if-match command.

· To delete a criterion that has multiple values, the specified values in the undo if-match command must be the same as those specified in the if-match command. The order of the values can be different.

When you configure ACL-based match criteria, follow these restrictions and guidelines:

· The ACL must already exist.

· If the ACL contains deny rules, the if-match command is ignored and the matching process continues.

You can use both AND and OR operators to define the match relationships between the criteria for a class. For example, you can define relationships among three match criteria in traffic class classA as follows:

traffic classifier classB operator and

if-match criterion 1

if-match criterion 2

traffic classifier classA operator or

if-match criterion 3

if-match classifier classB

Examples

# Define a match criterion for traffic class class1 to match the packets with a destination MAC address of 0050-ba27-bed3.

<Sysname> system-view

[Sysname] traffic classifier class1

[Sysname-classifier-class1] if-match destination-mac 0050-ba27-bed3

# Define a match criterion for traffic class class2 to match the packets with a source MAC address of 0050-ba27-bed2.

<Sysname> system-view

[Sysname] traffic classifier class2

[Sysname-classifier-class2] if-match source-mac 0050-ba27-bed2

# Define a match criterion for traffic class class1 to match the double-tagged packets with 802.1p priority 3 in the inner VLAN tag.

<Sysname> system-view

[Sysname] traffic classifier class1

[Sysname-classifier-class1] if-match customer-dot1p 3

# Define a match criterion for traffic class class1 to match advanced ACL 3101.

<Sysname> system-view

[Sysname] traffic classifier class1

[Sysname-classifier-class1] if-match acl 3101

# Define a match criterion for traffic class class1 to match the ACL named flow.

<Sysname> system-view

[Sysname] traffic classifier class1

[Sysname-classifier-class1] if-match acl name flow

# Define a match criterion for traffic class class1 to match advanced IPv6 ACL 3101.

<Sysname> system-view

[Sysname] traffic classifier class1

[Sysname-classifier-class1] if-match acl ipv6 3101

# Define a match criterion for traffic class class1 to match the IPv6 ACL named flow.

<Sysname> system-view

[Sysname] traffic classifier class1

[Sysname-classifier-class1] if-match acl ipv6 name flow

# Define a match criterion for traffic class class1 to match all packets.

<Sysname> system-view

[Sysname] traffic classifier class1

[Sysname-classifier-class1] if-match any

# Define a match criterion for traffic class class1 to match the packets with a DSCP value of 1, 6, or 9.

<Sysname> system-view

[Sysname] traffic classifier class1 operator or

[Sysname-classifier-class1] if-match dscp 1 6 9

# Define a match criterion for traffic class class1 to match the packets with an IP precedence value of 1 or 6.

<Sysname> system-view

[Sysname] traffic classifier class1 operator or

[Sysname-classifier-class1] if-match ip-precedence 1 6

# Define a match criterion for traffic class class1 to match IP packets.

<Sysname> system-view

[Sysname] traffic classifier class1

[Sysname-classifier-class1] if-match protocol ip

# Define a match criterion for traffic class class1 to match the RTP packets with even UDP destination port numbers in the range of 16384 to 32767.

<Sysname> system-view

[Sysname] traffic classifier class1 operator or

[Sysname-classifier-class1] if-match rtp start-port 16384 end-port 32767

# Define a match criterion for traffic class class1 to match double-tagged packets with VLAN ID 1, 6, or 9 in the inner VLAN tag.

<Sysname> system-view

[Sysname] traffic classifier class1 operator or

[Sysname-classifier-class1] if-match customer-vlan-id 1 6 9

# Define a match criterion for traffic class class1 to match the packets with a local QoS ID of 3.

<Sysname> system-view

[Sysname] traffic classifier class1

[Sysname-classifier-class1] if-match qos-local-id 3

# Define a match criterion for traffic class class1 to match the packets of the application group multimedia.

<Sysname> system-view

[Sysname] traffic classifier class1

[Sysname-classifier-class1] if-match app-group multimedia

# Define a match criterion for traffic class class1 to match the packets of the application 3link.

<Sysname> system-view

[Sysname] traffic classifier class1

[Sysname-classifier-class1] if-match application 3link

# Define a match criterion for traffic class class1 to match packets with the length in the range of 100 to 200 bytes.

<Sysname> system-view

[Sysname] traffic classifier class1

[Sysname-classifier-class1] if-match packet-length min 100 max 200

traffic classifier

Use traffic classifier to create a traffic class and enter its view, or enter the view of an existing traffic class.

Use undo traffic classifier to delete a traffic class.

Syntax

traffic classifier classifier-name [ operator { and | or } ]

undo traffic classifier classifier-name

Default

No traffic classes exist.

Views

System view

Predefined user roles

network-admin

context-admin

vsys-admin

Parameters

classifier-name: Specifies a name for the traffic class, a case-sensitive string of 1 to 31 characters.

operator: Sets the operator to logic AND (the default) or OR for the traffic class.

and: Specifies the logic AND operator. The traffic class matches the packets that match all its criteria.

or: Specifies the logic OR operator. The traffic class matches the packets that match any of its criteria.

Examples

# Create a traffic class named class1.

<Sysname> system-view

[Sysname] traffic classifier class1

[Sysname-classifier-class1]

Related commands

display traffic classifier

Traffic behavior commands

accounting

Use accounting to configure a traffic accounting action in a traffic behavior.

Use undo accounting to restore the default.

Syntax

accounting [ byte | packet ]

undo accounting

Default

No traffic accounting action is configured.

Views

Traffic behavior view

Predefined user roles

network-admin

context-admin

Parameters

byte: Counts traffic in bytes.

packet: Counts traffic in packets.

Usage guidelines

If you do not specify the byte or packet keyword, the device counts packets in both bytes and packets.

The accounting action in a QoS policy does not take effect if the QoS policy is applied globally.

Examples

# Configure a traffic accounting action in traffic behavior database to count traffic in bytes.

<Sysname> system-view

[Sysname] traffic behavior database

[Sysname-behavior-database] accounting byte

car

Use car to configure a CAR action in absolute value in a traffic behavior.

Use undo car to restore the default.

Syntax

car cir committed-information-rate [ cbs committed-burst-size [ ebs excess-burst-size ] ] [ green action | red action | yellow action ] *

car cir committed-information-rate [ cbs committed-burst-size ] pir peak-information-rate [ ebs excess-burst-size ] [ green action | red action | yellow action ] *

undo car

Default

No CAR action is configured.

Views

Traffic behavior view

Predefined user roles

network-admin

context-admin

vsys-admin

Parameters

cir committed-information-rate: Specifies the committed information rate (CIR) in kbps, which is an average traffic rate. The value range for committed-information-rate is 8 to 1000000000.

cbs committee-burst-sizee: Specifies the committed burst size (CBS) in the range of 1000 to 4000000000 bytes. The default value for this argument is the product of 62.5 and the CIR.

ebs excess-burst-size: Specifies the excess burst size (EBS) in the range of 0 to 4000000000 bytes. The default EBS is 0.

pir peak-information-rate: Specifies the peak information rate (PIR) in the range of 8 to 100000000 kbps. The PIR must be specified in the same unit as the CIR.

green action: Specifies the action to take on packets that conform to the CIR. The default setting is pass.

red action: Specifies the action to take on packets that conform to neither CIR nor PIR. The default setting is discard.

yellow action: Specifies the action to take on packets that conform to the PIR but not to the CIR. The default setting is pass.

action: Sets the action to take on the packet:

· discard: Drops the packet.

· pass: Permits the packet to pass through.

· remark-dot1p-pass new-cos: Sets the 802.1p priority value of the 802.1p packet to new-cos and permits the packet to pass through. The new-cos argument is in the range of 0 to 7.

· remark-dscp-pass new-dscp: Sets the DSCP value of the packet to new-dscp and permits the packet to pass through. The new-dscp argument is in the range of 0 to 63.

· remark-mpls-exp-pass new-exp: Sets the EXP field value of the MPLS packet to new-exp and permits the packet to pass through. The new-exp argument is in the range of 0 to 7.

· remark-prec-pass new-precedence: Sets the IP precedence of the packet to new-precedence and permits the packet to pass through. The new-precedence argument is in the range of 0 to 7.

Usage guidelines

To use two rates for traffic policing, configure the car command with the pir peak-information-rate option. To use one rate for traffic policing, configure the car command without the pir peak-information-rate option.

If you execute the car command multiple times in the same traffic behavior, the most recent configuration takes effect.

Examples

# Configure a CAR action in traffic behavior database:

· Set the CIR to 200 kbps, CBS to 51200 bytes, and EBS to 0.

· Transmit the conforming packets, and mark the excess packets with DSCP value 0 and transmit them.

<Sysname> system-view

[Sysname] traffic behavior database

[Sysname-behavior-database] car cir 200 cbs 51200 ebs 0 green pass red remark-dscp-pass 0

car percent

Use car percent to configure a CAR action in percentage in a traffic behavior.

Use undo car to restore the default.

Syntax

car cir percent cir-percent [ cbs cbs-time [ ebs ebs-time ] ] [ green action | red action | yellow action ] *

car cir percent cir-percent [ cbs cbs-time ] pir percent pir-percent [ ebs ebs-time ] [ green action | red action | yellow action ] *

undo car

Default

No percentage-based CAR action is configured.

Views

Traffic behavior view

Predefined user roles

network-admin

context-admin

Parameters

cir percent cir-percent: Specifies the CIR in percentage, in the range of 1 to 100. The actual CIR value is cir-percent × interface bandwidth.

cbs cbs-time: Specifies the CBS in milliseconds. The actual CBS value is cbs-time × the actual CIR value. The value range for the cbs-time argument is 50 to 2000. The default CBS is 500.

ebs ebs-time: Specifies the EBS in milliseconds. The actual EBS value is ebs-time × the actual CIR value. The value range for the ebs-time argument is 0 to 2000. The default EBS is 0.

pir percent pir-percent: Specifies the PIR in percentage, in the range of 1 to 100. The PIR value must be greater than or equal to the CIR value.

green action: Specifies the action to take on packets that conform to the CIR. The default is pass.

red action: Specifies the action to take on packets that conform to neither CIR nor PIR. The default is discard.

yellow action: Specifies the action to take on packets that conform to the PIR but not to the CIR. The default is pass.

action: Sets the action to take on the packet:

· discard: Drops the packet.

· pass: Permits the packet to pass through.

· remark-dot1p-pass new-cos: Sets the 802.1p priority value of the packet to new-cos and permits the packet to pass through. The new-cos argument is in the range of 0 to 7.

· remark-dscp-pass new-dscp: Sets the DSCP value of the packet to new-dscp and permits the packet to pass through. The new-dscp argument is in the range of 0 to 63. Alternatively, you can specify the new-dscp argument with af11, af12, af13, af21, af22, af23, af31, af32, af33, af41, af42, af43, cs1, cs2, cs3, cs4, cs5, cs6, cs7, default, or ef.

· remark-mpls-exp-pass new-exp: Sets the EXP field value of the MPLS packet to new-exp and permits the packet to pass through. The new-exp argument is in the range of 0 to 7.

· remark-prec-pass new-precedence: Sets the IP precedence of the packet to new-precedence and permits the packet to pass through. The new-precedence argument is in the range of 0 to 7.

Usage guidelines

To use two rates for traffic policing, configure the car percent command with the pir percent pir-percent option. To use one rate for traffic policing, configure the car percent command without the pir percent pir-percent option.

A QoS policy that uses a traffic behavior configured with percentage-based CAR can be applied in the inbound or outbound direction of an interface.

If you execute the car percent command multiple times in the same traffic behavior, the most recent configuration takes effect.

A QoS policy that uses a behavior configured with percentage-based CAR can be applied only to interfaces.

The actual CIR value is cir-percent × bandwidth. The actual PIR value is pir-percent × bandwidth. For a physical interface, the bandwidth is the actual interface bandwidth. For a virtual interface(for example, tunnel interface and Layer 3 aggregate interface), you must set its expected bandwidth (the default expected bandwidth is 0 kbps). For more information about the expected bandwidth, see Ethernet interface commands in Interface Command Reference. In the policy nesting case, the bandwidth used for the CIR and PIR calculations is determined by using the following rules:

· The top policy uses the interface bandwidth.

· A child policy uses the CIR value in GTS configured in the behavior of the child policy.

· If the CIR value is not available in the behavior, the child policy uses the CIR value in GTS configured in the behavior of the higher-level policy.

· If the CIR value is not available in the behavior of the higher-level policy, the child policy uses the interface bandwidth.

Examples

# Configure a CAR action in percentage in traffic behavior database. The CAR parameters are as follows: CIR is 20% and CBS is 100 ms.

<Sysname> system-view

[Sysname] traffic behavior database

[Sysname-behavior-database] car cir percent 20 cbs 100

display traffic behavior

Use display traffic behavior to display traffic behaviors.

Syntax

In standalone mode:

display traffic behavior { system-defined | user-defined } [ behavior-name ] [ slot slot-number [ cpu cpu-number ] ]

In IRF mode:

display traffic behavior { system-defined | user-defined } [ behavior-name ] [ chassis chassis-number slot slot-number [ cpu cpu-number ] ]

Views

Any view

Predefined user roles

network-admin

network-operator

context-admin

context-operator

vsys-admin

vsys-operator

Parameters

system-defined: Specifies system-defined traffic behaviors.

user-defined: Specifies user-defined traffic behaviors.

behavior-name: Specifies a behavior by its name, a case-sensitive string of 1 to 31 characters. If you do not specify a traffic behavior, this command displays all traffic behaviors.

slot slot-number: Specifies a card by its slot number. If you do not specify a card, this command displays traffic behaviors for the active MPU. (In standalone mode.)

cpu cpu-number: Specifies a CPU by its number. This option is available only if multiple CPUs are available on the specified slot.

Examples

# Display all user-defined traffic behaviors.

<Sysname> display traffic behavior user-defined

User-defined behavior information:

Behavior: 1 (ID 100)

Committed Access Rate:

CIR 2222 (kbps), CBS 22222222 (Bytes), EBS 0 (Bytes)

Green action : pass

Yellow action : pass

Red action : discard

# Display all system-defined traffic behaviors.

<Sysname> display traffic behavior system-defined

System-defined behavior information:

Behavior: be (ID 0)

-none-

Behavior: af (ID 1)

Assured Forwarding:

Bandwidth 20 (%)

Discard Method: Tail

Behavior: ef (ID 2)

Expedited Forwarding:

Bandwidth 20 (%) Cbs-ratio 25

Behavior: be-flow-based (ID 3)

Flow based Weighted Fair Queue:

Max number of hashed queues: 256

Discard Method: IP Precedence based WRED

Exponential Weight: 9

Pre Low High Dis-prob

-------------------------

0 10 30 10

1 10 30 10

2 10 30 10

3 10 30 10

4 10 30 10

5 10 30 10

6 10 30 10

7 10 30 10

Table 4 Command output

Field	Description
Behavior	Name and contents of a traffic behavior.
Marking	Information about priority marking.
Remark dscp	Action of setting the DSCP value for packets.
Committed Access Rate	Information about the CAR action.
Green action	Action to take on green packets.
Yellow action	Action to take on yellow packets.
Red action	Action to take on red packets.
Filter enable	Traffic filtering action.
Remark mpls-exp	Action of setting the MPLS EXP value for packets.
none	No other traffic behavior is configured.
Exponential Weight	Exponent for average queue size calculation
Pre	IP precedence.
Low	Lower threshold of the queue.
High	Upper threshold of the queue.
Dis-prob	Denominator for drop probability calculation.

‌

filter

Use filter to configure a traffic filtering action in a traffic behavior.

Use undo filter to restore the default.

Syntax

filter { deny | permit }

undo filter

Default

No traffic filtering action is configured.

Views

Traffic behavior view

Predefined user roles

network-admin

context-admin

Parameters

deny: Drops packets.

permit: Transmits packets.

Examples

# Configure a traffic filtering action as deny in traffic behavior database.

<Sysname> system-view

[Sysname] traffic behavior database

[Sysname-behavior-database] filter deny

gts

Use gts to configure a GTS action in absolute value in a traffic behavior.

Use undo gts to restore the default.

Syntax

gts cir committed-information-rate [ cbs committed-burst-size [ ebs excess-burst-size ] ] [ queue-length queue-length ]

undo gts

Default

No GTS action is configured.

Views

Traffic behavior view

Predefined user roles

network-admin

context-admin

Parameters

cir committed-information-rate: Sets the CIR in kbps, which specifies the average traffic rate. The value range for committed-information-rate is 8 to 10000000.

cbs committed-burst-size: Sets the CBS in bytes, which specifies the size of bursty traffic when the actual average rate is not greater than the CIR. The value range for committed-burst-size is 1000 to 1000000000. The default CBS is the product of 62.5 and the CIR.

ebs excess-burst-size: Sets the EBS in bytes. The value range for excess-burst-size is 0 to 1000000000. The default EBS is 0.

queue-length queue-length: Sets the maximum number of packets allowed in the queue. The default is 50. The value range for queue-length is 1 to 1024.

Usage guidelines

A QoS policy that uses a behavior configured with GTS can be applied only to the outbound direction of an interface.

A QoS policy that uses a behavior configured with GTS overwrites the qos gts command on the interface, if both are configured.

If you execute the gts command multiple times in the same traffic behavior, the most recent configuration takes effect.

Examples

# Configure a GTS action in absolute value in traffic behavior database. The GTS parameters are as follows: CIR is 200 kbps, CBS is 51200 bytes, EBS is 0, and the maximum queue length is 100.

<Sysname> system-view

[Sysname] traffic behavior database

[Sysname-behavior-database] gts cir 200 cbs 51200 ebs 0 queue-length 100

Related commands

gts percent

Use gts percent to configure a GTS action in percentage in a traffic behavior.

Use undo gts to restore the default.

Syntax

gts percent cir cir-percent [ cbs cbs-time [ ebs ebs-time ] ] [ queue-length queue-length ]

undo gts

Default

No percentage-based GTS action is configured.

Views

Traffic behavior view

Predefined user roles

network-admin

context-admin

Parameters

cir cir-percent: Specifies the CIR in percentage, in the range of 1 to 100. The actual CIR value is cir-percent × interface bandwidth.

cbs cbs-time: Specifies the CBS in milliseconds. The default cbs-time is 500 milliseconds. The actual CBS value is cbs-time × the actual CIR value. The value range for cbs-time is 50 to 2000. The default CBS is 500.

ebs ebs-time: Specifies the EBS in milliseconds. The default ebs-time is 0 milliseconds. The actual EBS value is ebs-time × the actual CIR value. The value range for ebs-time is 0 to 2000. The default EBS is 0.

queue-length queue-length: Specifies the maximum number of packets allowed in the queue. The default is 50. The value range for queue-length is 1 to 1024.

Usage guidelines

A QoS policy that uses a behavior configured with percentage-based GTS can be applied only to the outbound direction of an interface.

A QoS policy that uses a behavior configured with percentage-based GTS overwrites the qos gts command on the interface, if both configured.

If you execute the gts percent command multiple times in the same traffic behavior, the most recent configuration takes effect.

Examples

# Configure a GTS action in percentage in traffic behavior database. The GTS parameters are as follows: CIR is 50 and CBS is 200 ms.

<Sysname> system-view

[Sysname] traffic behavior database

[Sysname-behavior-database] gts percent cir 50 cbs 200

Related commands

gts

redirect

Use redirect to configure a traffic redirecting action in a traffic behavior.

Use undo redirect to restore the default.

Syntax

redirect { failover-group group-name [ channel channel-id ] | interface interface-type interface-number }

undo redirect { failover-group group-name | interface interface-type interface-number }

Default

No traffic redirecting action is configured.

Views

Traffic behavior view

Predefined user roles

network-admin

context-admin

Parameters

failover group group-name: Redirects traffic to a failover group specified by its name, a case-sensitive string of 1 to 63 characters.

channel channel-id: Redirects traffic to a Blade interface specified by its channel ID. The channel ID can be 0 or 1. The default is 0.

interface interface-type interface-number: Redirects traffic to an interface specified by its type and number.

Usage guidelines

If you execute the redirect command multiple times in the same traffic behavior, the most recent configuration takes effect.

Examples

# Configure redirecting traffic to GigabitEthernet 1/0/1 in traffic behavior database.

<Sysname> system-view

[Sysname] traffic behavior database

[Sysname-behavior-database] redirect interface gigabitethernet 1/0/1

# Configure redirecting traffic to failover group bakgrp1 in traffic behavior database.

<Sysname> system-view

[Sysname] traffic behavior database

[Sysname-behavior-database] redirect failover-group bakgrp1

Related commands

classifier behavior

qos policy

traffic behavior

remark dot1p

Use remark dot1p to configure an 802.1p priority marking action or an inner-to-outer tag priority copying action in a traffic behavior.

Use undo remark dot1p to restore the default.

Syntax

remark dot1p dot1p-value

undo remark dot1p

Default

No 802.1p priority markingaction is configured.

Views

Traffic behavior view

Predefined user roles

network-admin

context-admin

Parameters

dot1p-value: Specifies the 802.1p priority to be marked for packets, in the range of 0 to 7.

Examples

# Configure traffic behavior database to mark matching traffic with 802.1p 2.

<Sysname> system-view

[Sysname] traffic behavior database

[Sysname-behavior-database] remark dot1p 2

remark dscp

Use remark dscp to configure a DSCP marking action in a traffic behavior.

Use undo remark dscp to restore the default.

Syntax

remark dscp dscp-value

undo remark dscp

Default

No DSCP marking action is configured.

Views

Traffic behavior view

Predefined user roles

network-admin

context-admin

Parameters

dscp-value: Specifies a DSCP value, which can be a number from 0 to 63 or a keyword in Table 5.

Table 5 DSCP keywords and values

Keyword	DSCP value (binary)	DSCP value (decimal)
af11	001010	10
af12	001100	12
af13	001110	14
af21	010010	18
af22	010100	20
af23	010110	22
af31	011010	26
af32	011100	28
af33	011110	30
af41	100010	34
af42	100100	36
af43	100110	38
cs1	001000	8
cs2	010000	16
cs3	011000	24
cs4	100000	32
cs5	101000	40
cs6	110000	48
cs7	111000	56
default	000000	0
ef	101110	46

Usage guidelines

If you execute the remark dscp command multiple times in the same traffic behavior, the most recent configuration takes effect.

Examples

# Configure traffic behavior database to mark matching traffic with DSCP 6.

<Sysname> system-view

[Sysname] traffic behavior database

[Sysname-behavior-database] remark dscp 6

remark ip-precedence

Use remark ip-precedence to configure an IP precedence marking action in a traffic behavior.

Use undo remark ip-precedence to restore the default.

Syntax

remark ip-precedence ip-precedence-value

undo remark ip-precedence

Default

No IP precedence marking action is configured.

Views

Traffic behavior view

Predefined user roles

network-admin

context-admin

Parameters

ip-precedence-value: Specifies the IP precedence value to be marked for packets, in the range of 0 to 7.

Usage guidelines

If you execute the remark ip-precedence command multiple times in the same traffic behavior, the most recent configuration takes effect.

Examples

# Set the IP precedence to 6 for packets.

<Sysname> system-view

[Sysname] traffic behavior database

[Sysname-behavior-database] remark ip-precedence 6

remark qos-local-id

Use remark qos-local-id to configure a local QoS ID marking action in a traffic behavior.

Use undo remark qos-local-id to restore the default.

Syntax

remark qos-local-id local-id-value

undo remark qos-local-id

Default

No local QoS ID marking action is configured.

Views

Traffic behavior view

Predefined user roles

network-admin

context-admin

Parameters

local-id-value: Specifies the local QoS ID to be marked for packets, in the range of 1 to 4095.

Usage guidelines

You can use one QoS policy to mark the local QoS ID for packets in the inbound direction. Then, you can use another QoS policy to apply other QoS features in the outbound direction based on the marked local QoS ID.

If you execute the remark qos-local-id command multiple times in the same traffic behavior, the most recent configuration takes effect.

Examples

# Configure the action of marking packets with local QoS ID 2.

<Sysname> system-view

[Sysname] traffic behavior database

[Sysname-behavior-database] remark qos-local-id 2

traffic behavior

Use traffic behavior to create a traffic behavior and enter its view, or enter the view of an existing traffic behavior.

Use undo traffic behavior to delete a traffic behavior.

Syntax

traffic behavior behavior-name

undo traffic behavior behavior-name

Default

No traffic behaviors exist.

Views

System view

Predefined user roles

network-admin

context-admin

vsys-admin

Parameters

behavior-name: Specifies a name for the traffic behavior, a case-sensitive string of 1 to 31 characters.

Examples

# Create a traffic behavior named behavior1.

<Sysname> system-view

[Sysname] traffic behavior behavior1

[Sysname-behavior-behavior1]

Related commands

display traffic behavior

traffic-policy

Use traffic-policy to nest a policy in a traffic behavior.

Use undo traffic-policy to remove child policies from a traffic behavior.

Syntax

traffic-policy policy-name

undo traffic-policy

Default

No policy is nested in a traffic behavior.

Views

Traffic behavior view

Predefined user roles

network-admin

context-admin

Parameters

policy-name: Specifies a policy by its name, a string of 1 to 31 characters. If the policy does not exist, it is automatically created.

Usage guidelines

After you nest a child policy in a behavior of a parent policy, the system performs the following operations:

· Performs the associated behavior defined in the parent policy for a class of traffic.

· Uses the child policy to further classify the class of traffic and performs the behaviors defined in the child policy.

When you nest QoS policies, follow these guidelines:

· A parent policy can nest up to two layers of child policies. This child policy cannot be the parent policy itself.

· You can nest only one child policy at one layer of a behavior.

· To configure CBQ in the child policy successfully, configure GTS in the parent policy. Make sure the configured GTS bandwidth is greater than CBQ bandwidth configured in the child policy.

· If GTS bandwidth is set in percentage in the parent policy, you must set CBQ bandwidth in percentage in the child policy. If GTS bandwidth is set as an absolute value in the parent policy, you can set CBQ bandwidth in either format in the child policy.

· A child policy cannot contain GTS actions.

· Policy nesting is available for IPv4 and IPv6 packets.

· To delete the child policy after you apply the parent policy to an interface, first remove the child policy from the parent policy.

Examples

# Nest child policy child in traffic behavior database of the parent policy.

<Sysname> system-view

[Sysname] traffic behavior database

[Sysname-behavior-database] traffic-policy child

Related commands

traffic behavior

traffic classifier

QoS policy commands

classifier behavior

Use classifier behavior to associate a traffic behavior with a traffic class in a QoS policy.

Use undo classifier to delete a class-behavior association from a QoS policy.

Syntax

classifier classifier-name behavior behavior-name [ mode inner-redirect-ignore | insert-before before-classifier-name ]

undo classifier classifier-name

Default

No traffic behavior is associated with a traffic class.

Views

QoS policy view

Predefined user roles

network-admin

context-admin

vsys-admin

Parameters

classifier-name: Specifies a traffic class by its name, a case-sensitive string of 1 to 31 characters.

behavior-name: Specifies a traffic behavior by its name, a case-sensitive string of 1 to 31 characters.

mode inner-redirect-ignore: Specifies that the class-behavior association ignores traffic redirection inside the device. The matching packets will not be hit after they are redirected. This mode is reuquired in scenarios where a traffic rediretion action is configured.

insert-before before-classifier-name: Inserts the new traffic class before an existing traffic class in the QoS policy. The before-classifier-name argument specifies an existing traffic class by its name, a case-sensitive string of 1 to 31 characters. If you do not specify the insert-before before-classifier-name option, the new traffic class is placed at the end of the QoS policy.

Usage guidelines

A traffic class can be associated only with one traffic behavior in a QoS policy.

If the specified traffic class or traffic behavior does not exist, the system defines a null traffic class or traffic behavior.

Examples

# Associate traffic class database with traffic behavior test in QoS policy user1.

<Sysname> system-view

[Sysname] qos policy user1

[Sysname-qospolicy-user1] classifier database behavior test

# Associate traffic class database with traffic behavior test in QoS policy user1, and insert traffic class database before an existing traffic class named class-a.

<Sysname> system-view

[Sysname] qos policy user1

[Sysname-qospolicy-user1] classifier database behavior test insert-before class-a

Related commands

qos policy

control-plane

Use control-plane to enter control plane view.

Syntax

In standalone mode:

control-plane slot slot-number [ cpu cpu-number ]

In IRF mode:

control-plane chassis chassis-number slot slot-number [ cpu cpu-number ]

Views

System view

Predefined user roles

network-admin

context-admin

Parameters

slot slot-number: Specifies a card by its slot number. (In standalone mode.)

cpu cpu-number: Specifies a CPU by its number. This option is available only if multiple CPUs are available on the specified slot.

Examples

# (In standalone mode.) Enter the control plane view of slot 3.

<Sysname> system-view

[Sysname] control-plane slot 3

[Sysname-cp-slot3]

control-plane management

Use control-plane management to enter control-plane management view.

Syntax

control-plane management

Views

System view

Predefined user roles

network-admin

context-admin

Usage guidelines

A QoS policy applied in control-plane management view takes effect on the packets sent from the management interface to the control plane.

Examples

# Enter control-plane management view.

<Sysname> system-view

[Sysname] control-plane management

[Sysname-cp-management]

display qos policy

Use display qos policy to display QoS policies.

Syntax

In standalone mode:

display qos policy { system-defined | user-defined } [ policy-name [ classifier classifier-name ] ] [ slot slot-number [ cpu cpu-number ] ]

In IRF mode:

display qos policy { system-defined | user-defined } [ policy-name [ classifier classifier-name ] ] [ chassis chassis-number slot slot-number [ cpu cpu-number ] ]

Views

Any view

Predefined user roles

network-admin

network-operator

context-admin

context-operator

vsys-admin

vsys-operator

Parameters

system-defined: Specifies system-defined QoS policies.

user-defined: Specifies user-defined QoS policies.

policy-name: Specifies a QoS policy by its name, a case-sensitive string of 1 to 31 characters. If you do not specify a QoS policy, this command displays all user-defined QoS policies.

classifier classifier-name: Specifies a traffic class by its name, a case-sensitive string of 1 to 31 characters. If you do not specify a traffic class, this command displays all traffic classes.

slot slot-number: Specifies a card by its slot number. If you do not specify a card, this command displays the QoS policies for the active MPU. (In standalone mode.)

chassis chassis-number slot slot-number: Specifies a card on an IRF member device. The chassis-number argument represents the member ID of the IRF member device. The slot-number argument represents the slot number of the card. If you do not specify this option, the command displays the QoS policies for the global active MPU. (In IRF mode.)

cpu cpu-number: Specifies a CPU by its number. This option is available only if multiple CPUs are available on the specified slot.

Examples

# Display all user-defined QoS policies.

<Sysname> display qos policy user-defined

User-defined QoS policy information:

Policy: 1 (ID 100)

Classifier: 1 (ID 100)

Behavior: 1

Marking:

Remark dscp 3

Committed Access Rate:

CIR 112 (kbps), CBS 51200 (Bytes), EBS 512 (Bytes)

Green action : pass

Yellow action : pass

Red action : discard

Classifier: 2 (ID 101)

Behavior: 2

Accounting enable: Packet

Filter enable: Permit

Marking:

Remark dot1p 4

Classifier: 3 (ID 102)

Behavior: 3

-none-

Classifier: 4 (ID 103)

Behavior: 4

Redirecting:

Redirect to SR-TE policy:

Endpoint: 10.0.0.3

Color : 123464

Redirect to SRv6-TE policy:

Endpoint: 56::44

Color : 123464

SID : 5a::13

# Display the system-defined QoS policy (default).

<Sysname> display qos policy system-defined

System-defined QoS policy information:

Policy: default (ID 0)

Classifier: default-class (ID 0)

Behavior: be

-none-

Classifier: ef (ID 1)

Behavior: ef

Expedited Forwarding:

Bandwidth 20 (%) Cbs-ratio 25

Classifier: af1 (ID 2)

Behavior: af

Assured Forwarding:

Bandwidth 20 (%)

Discard Method: Tail

Classifier: af2 (ID 3)

Behavior: af

Assured Forwarding:

Bandwidth 20 (%)

Discard Method: Tail

Classifier: af3 (ID 4)

Behavior: af

Assured Forwarding:

Bandwidth 20 (%)

Discard Method: Tail

Classifier: af4 (ID 5)

Behavior: af

Assured Forwarding:

Bandwidth 20 (%)

Discard Method: Tail

Table 6 Command output

Field	Description
User-defined QoS policy information	Information about a user-defined QoS policy.
System-defined QoS policy information	Information about a system-defined QoS policy.
Policy	User-defined QoS policy name.
Mode	Association mode of a class-behavior association: · DCBX—Indicates that the class-behavior association applies only to DCBX. For more information about DCBX, see Layer 2—LAN Switching Configuration Guide. · qppb-manipulation—Indicates that the class-behavior association applies only to matching the apply qos-local-id command configuration in a BGP routing policy. For more information, see Layer 3—IP Routing Configuration Guide. · inner-redirect-ignore—Indicates that the class-behavior association ignores traffic redirection inside the device.

For the description of other fields, see Table 1 and Table 4.

display qos policy control-plane

Use display qos policy control-plane to display QoS policies applied to a control plane.

Syntax

In standalone mode:

display qos policy control-plane slot slot-number [ cpu cpu-number ]

In IRF mode:

display qos policy control-plane chassis chassis-number slot slot-number [ cpu cpu-number ]

Views

Any view

Predefined user roles

network-admin

network-operator

context-admin

context-operator

Parameters

slot slot-number: Specifies a card by its slot number. (In standalone mode.)

cpu cpu-number: Specifies a CPU by its number. This option is available only if multiple CPUs are available on the specified slot.

Examples

# (In standalone mode.) Display the QoS policy applied to the control plane of slot 1.

<Sysname> display qos policy control-plane slot 1

Control plane slot 1

Direction: Inbound

Policy: 1

Classifier: 1

Operator: AND

Rule(s) :

If-match acl 2000

Behavior: 1

Marking:

Remark dscp 3

Committed Access Rate:

CIR 112 (kbps), CBS 51200 (Bytes), EBS 512 (Bytes)

Green action : pass

Yellow action : pass

Red action : discard

Green packets : 0 (Packets) 0 (Bytes)

Yellow packets: 0 (Packets) 0 (Bytes)

Red packets : 0 (Packets) 0 (Bytes)

Classifier: 2

Operator: AND

Rule(s) :

If-match protocol ipv6

Behavior: 2

Accounting enable:

0 (Packets)

Filter enable: Permit

Marking:

Remark dscp 3

Classifier: 3

Operator: AND

Rule(s) :

-none-

Behavior: 3

-none-

Table 7 Command output

Field	Description
Direction	Direction in which the QoS policy is applied.
Green packets	Statistics about green packets.
Yellow packets	Statistics about yellow packets.
Red packets	Statistics about red packets.

For the description of other fields, see Table 1 and Table 4.

display qos policy control-plane management

Use display qos policy control-plane management to display the QoS policies applied in control-plane management view.

Syntax

display qos policy control-plane management

Views

Any view

Predefined user roles

network-admin

network-operator

context-admin

context-operator

Examples

# Display the QoS policy applied in control-plane management view.

<Sysname> display qos policy control-plane management

Control plane management

Direction: Inbound

Policy: a

Classifier: default-class

Matched : 0 (Packets) 0 (Bytes)

Operator: AND

Rule(s) :

If-match any

Behavior: be

-none-

Classifier: a

Matched : 3 (Packets) 180 (Bytes)

Operator: OR

Rule(s) :

If-match control-plane protocol arp

If-match control-plane protocol rip

If-match control-plane protocol-group critical

If-match acl 3001

If-match control-plane protocol bgp

If-match control-plane protocol bgp4+

If-match control-plane protocol ftp

If-match control-plane protocol http https icmp icmp6 ripng snmp

Behavior: a

Committed Access Rate:

CIR 128 (kbps), CBS 51200 (Bytes), EBS 0 (Bytes)

Green action : pass

Yellow action : pass

Red action : discard

Green packets : 3 (Packets) 180 (Bytes)

Yellow packets: 0 (Packets) 0 (Bytes)

Red packets : 0 (Packets) 0 (Bytes)

Table 8 Command output

Field	Description
Direction	Direction in which the QoS policy is applied.
Green packets	Statistics about green packets.
Yellow packets	Statistics about yellow packets.
Red packets	Statistics about red packets.

For the description of other fields, see Table 1 and Table 4.

display qos policy control-plane management pre-defined

Use display qos policy control-plane management pre-defined to display the predefined QoS policy applied in control-plane management view.

Syntax

display qos policy control-plane management pre-defined

Views

Any view

Predefined user roles

network-admin

network-operator

context-admin

context-operator

Examples

# Display the predefined QoS policy applied in control-plane management view.

<Sysname> display qos policy control-plane management pre-defined

Pre-defined control plane policy management

Protocol Priority Bandwidth Group

Default N/A 100000 (bps) N/A

ARP N/A 128 (bps) normal

BGP N/A 256 (bps) critical

BGPv6 N/A 256 (bps) critical

HTTP N/A 512 (bps) management

HTTPS N/A 512 (bps) management

ICMP N/A 128 (bps) monitor

ICMPv6 N/A 128 (bps) monitor

OSPF Multicast N/A 256 (bps) critical

OSPF Unicast N/A 256 (bps) critical

OSPFv3 Multicast N/A 256 (bps) critical

OSFPv3 Unicast N/A 256 (bps) critical

RIP N/A 1024 (bps) critical

RIPng N/A 256 (bps) critical

SNMP N/A 512 (bps) management

SSH N/A 512 (bps) management

TELNET N/A 512 (bps) management

FTP N/A 512 (bps) management

TFTP N/A 512 (bps) management

Table 9 Command output

Field	Description
Pre-defined control plane policy management	Predefined QoS policy applied in control-plane management view.
Protocol	System-defined protocol packet type.
Group	Protocol group to which the protocol belongs.

display qos policy control-plane pre-defined

Use display qos policy control-plane pre-defined to display predefined control plane QoS policies.

Syntax

In standalone mode:

display qos policy control-plane pre-defined [ slot slot-number [ cpu cpu-number ] ]

In IRF mode:

display qos policy control-plane pre-defined [ chassis chassis-number slot slot-number [ cpu cpu-number ] ]

Views

Any view

Predefined user roles

network-admin

network-operator

context-admin

context-operator

Parameters

slot slot-number: Specifies a card by its slot number. If you do not specify a card, this command displays the predefined control plane QoS policies for all cards. (In standalone mode.)

chassis chassis-number slot slot-number: Specifies a card on an IRF member device. The chassis-number argument represents the member ID of the IRF member device. The slot-number argument represents the slot number of the card. If you do not specify this option, the command displays predefined control plane QoS policies for all cards. (In IRF mode.)

cpu cpu-number: Specifies a CPU by its number. This option is available only if multiple CPUs are available on the specified slot.

Examples

# (In standalone mode.) Display the predefined control plane QoS policy of slot 1.

<Sysname> display qos policy control-plane pre-defined slot 1

Pre-defined policy information slot 1

Protocol Priority Bandwidth (pps) Group

Default N/A 1000 N/A

ARP N/A 500 normal

BGP N/A 500 critical

BGPv6 N/A 500 critical

HTTP N/A 500 management

HTTPS N/A 500 management

ICMP N/A 500 monitor

ICMPv6 N/A 500 monitor

IGMP N/A 500 important

IS-IS N/A 500 critical

LDP N/A 500 critical

LDPv6 N/A 500 critical

MSDP N/A 500 critical

NTP N/A 500 important

OSPF Multicast N/A 500 critical

OSPF Unicast N/A 500 critical

OSPFv3 Multicast N/A 500 critical

OSPFv3 Unicast N/A 500 critical

PIM Multicast N/A 500 critical

PIM Unicast N/A 500 critical

PIMv6 Multicast N/A 500 critical

PIMv6 Unicast N/A 500 critical

RADIUS N/A 500 management

RIP N/A 500 critical

RIPng N/A 500 critical

RSVP N/A 500 critical

SNMP N/A 500 management

TACACS N/A 500 management

VRRP N/A 500 important

VRRPv6 N/A 500 important

SSH N/A 500 management

TELNET N/A 500 management

FTP N/A 500 management

TFTP N/A 500 management

# (In IRF mode.) Display the predefined control plane QoS policy of slot 3 in chassis 1.

<Sysname> display qos policy control-plane pre-defined chassis 1 slot 3

Pre-defined policy information chassis 1 slot 3

Protocol Priority Bandwidth (pps) Group

Default N/A 1000 N/A

ARP N/A 500 normal

BGP N/A 500 critical

BGPv6 N/A 500 critical

HTTP N/A 500 management

HTTPS N/A 500 management

ICMP N/A 500 monitor

ICMPv6 N/A 500 monitor

IGMP N/A 500 important

IS-IS N/A 500 critical

LDP N/A 500 critical

LDPv6 N/A 500 critical

MSDP N/A 500 critical

NTP N/A 500 important

OSPF Multicast N/A 500 critical

OSPF Unicast N/A 500 critical

OSPFv3 Multicast N/A 500 critical

OSPFv3 Unicast N/A 500 critical

PIM Multicast N/A 500 critical

PIM Unicast N/A 500 critical

PIMv6 Multicast N/A 500 critical

PIMv6 Unicast N/A 500 critical

RADIUS N/A 500 management

RIP N/A 500 critical

RIPng N/A 500 critical

RSVP N/A 500 critical

SNMP N/A 500 management

TACACS N/A 500 management

VRRP N/A 500 important

VRRPv6 N/A 500 important

SSH N/A 500 management

TELNET N/A 500 management

FTP N/A 500 management

TFTP N/A 500 management

Table 10 Command output

Field	Description
Pre-defined control plane policy	Contents of the predefined control plane QoS policy.
Group	Protocol group of the protocol.

For descriptions of other fields, see Table 3.

display qos policy global

Use display qos policy global to display QoS policies applied globally.

Syntax

In standalone mode:

display qos policy global [ slot slot-number [ cpu cpu-number ] ] [ inbound | outbound ]

In IRF mode:

display qos policy global [ chassis chassis-number slot slot-number [ cpu cpu-number ] ] [ inbound | outbound ]

Views

Any view

Predefined user roles

network-admin

network-operator

context-admin

context-operator

Parameters

inbound: Specifies the QoS policy applied in the inbound direction.

outbound: Specifies the QoS policy applied in the outbound direction.

slot slot-number: Specifies a card by its slot number. If you do not specify a card, this command displays global QoS policies for the active MPU. (In standalone mode.)

chassis chassis-number slot slot-number: Specifies a card on an IRF member device. The chassis-number argument represents the member ID of the IRF member device. The slot-number argument represents the slot number of the card. If you do not specify this option, the command displays global QoS policies for the global active MPU. (In IRF mode.)

cpu cpu-number: Specifies a CPU by its number. This option is available only if multiple CPUs are available on the specified slot.

Usage guidelines

If you do not specify a direction, this command displays both inbound and outbound global QoS policies.

Examples

# Display QoS policies applied globally.

<Sysname> display qos policy global

Direction: Inbound

Policy: 1

Classifier: 1

Operator: AND

Rule(s) :

If-match acl 2000

Behavior: 1

Marking:

Remark dscp 3

Committed Access Rate:

CIR 112 (kbps), CBS 51200 (Bytes), EBS 512 (Bytes)

Green action : pass

Yellow action : pass

Red action : discard

Green packets : 0 (Packets) 0 (Bytes)

Yellow packets: 0 (Packets) 0 (Bytes)

Red packets : 0 (Packets) 0 (Bytes)

Classifier: 2

Operator: AND

Rule(s) :

If-match protocol ipv6

Behavior: 2

Accounting enable:

0 (Packets)

Filter enable: Permit

Marking:

Remark dscp 3

Classifier: 3

Operator: AND

Rule(s) :

-none-

Behavior: 3

-none-

Table 11 Command output

Field	Description
Direction	Direction in which the QoS policy is applied.
Type	Mode in which the QoS policy is applied globally, which can only be Enhancement (enhanced mode). If you do not specify the mode when applying a QoS policy globally, this field does not appear.
Green packets	Statistics about green packets.
Yellow packets	Statistics about yellow packets.
Red packets	Statistics about red packets.

For the description of other fields, see Table 1 and Table 4.

display qos policy interface

Use display qos policy interface to display the QoS policies applied to interfaces.

Syntax

In standalone mode:

display qos policy interface [ interface-type interface-number ] [ slot slot-number [ cpu cpu-number ] ] [ inbound | outbound ]

In IRF mode:

display qos policy interface [ interface-type interface-number ] [ chassis chassis-number slot slot-number [ cpu cpu-number ] ] [ inbound | outbound ]

Views

Any view

Predefined user roles

network-admin

network-operator

context-admin

context-operator

vsys-admin

vsys-operator

Parameters

interface-type interface-number: Specifies an interface by its type and number. If you do not specify an interface, this command displays QoS policies applied to all interfaces except VA interfaces. For information about VA interfaces, see PPP in PPP and PPPoE Configuration Guide.

slot slot-number: Specifies a card by its slot number. If you do not specify a card, this command displays QoS policies on the active MPU. Only logical interfaces support this option. (In standalone mode.)

chassis chassis-number slot slot-number: Specifies a card on an IRF member device. The chassis-number argument represents the member ID of the IRF member device. The slot-number argument represents the slot number of the card. If you do not specify a card, this command displays QoS policies on the global active MPU. Only logical interfaces support this option. (In IRF mode.)

cpu cpu-number: Specifies a CPU by its number. This option is available only if multiple CPUs are available on the specified slot.

inbound: Specifies the QoS policy applied to incoming traffic.

outbound: Specifies the QoS policy applied to outgoing traffic.

Usage guidelines

If you do not specify a direction, this command displays the QoS policy applied to incoming traffic and the QoS policy applied to outgoing traffic.

If you specify a VT interface, this command displays the QoS policies applied to each VA interface of the VT interface. It does not display QoS information about the VT interface.

Examples

# Display the QoS policy applied to the incoming traffic of GigabitEthernet 1/0/1.

<Sysname> display qos policy interface gigabitethernet 1/0/1 inbound

Interface: GigabitEthernet1/0/1

Direction: Inbound

Policy: 1

Classifier: 1

Matched : 0 (Packets) 0 (Bytes)

5-minute statistics:

Forwarded: 0/0 (pps/bps)

Dropped : 0/0 (pps/bps)

Operator: AND

Rule(s) :

If-match acl 2000

Behavior: 1

Marking:

Remark dscp 3

Committed Access Rate:

CIR 112 (kbps), CBS 51200 (Bytes), EBS 512 (Bytes)

Green action : pass

Yellow action : pass

Red action : discard

Green packets : 0 (Packets) 0 (Bytes)

Yellow packets: 0 (Packets) 0 (Bytes)

Red packets : 0 (Packets) 0 (Bytes)

Classifier: 2

Matched : 0 (Packets) 0 (Bytes)

5-minute statistics:

Forwarded: 0/0 (pps/bps)

Dropped : 0/0 (pps/bps)

Operator: AND

Rule(s) :

If-match protocol ipv6

Behavior: 2

Accounting enable:

0 (Packets)

Marking:

Remark dscp 3

Classifier: 3

Matched : 0 (Packets) 0 (Bytes)

5-minute statistics:

Forwarded: 0/0 (pps/bps)

Dropped : 0/0 (pps/bps)

Operator: AND

Rule(s) :

-none-

Behavior: 3

-none-

Classifier: 4

Matched : 10 (Packets) 8000 (Bytes)

5-minute statistics:

Forwarded: 0/0 (pps/bps)

Dropped : 0/0 (pps/bps)

Operator: AND

Rule(s) :

If-match acl 3001

Behavior: 4

Redirecting:

Redirect to SR-TE policy:

NID : 123464

Redirect to SRv6-TE policy:

Forwarding ID: 123464

SID : 25::5a

# Display the QoS policies applied to all interfaces.

<Sysname> display qos policy interface

Interface: GigabitEthernet1/0/1

Direction: Inbound

Type : Enhancement

Policy: a

Classifier: a

Operator: AND

Rule(s) :

If-match any

Behavior: a

Committed Access Rate:

CIR 112 (kbps), CBS 51200 (Bytes), EBS 0 (Bytes)

Green action : pass

Yellow action : pass

Red action : discard

Green packets : 0 (Packets)

Red packets : 0 (Packets)

Interface: GigabitEthernet1/0/3

Direction: Inbound

Policy: b

Classifier: b

Operator: AND

Rule(s) :

If-match any

Behavior: b

Committed Access Rate:

CIR 112 (kbps), CBS 51200 (Bytes), EBS 0 (Bytes)

Green action : pass

Yellow action : pass

Red action : discard

Green packets : 0(Packets)

Red packets : 0 (Packets)

Interface: GigabitEthernet1/0/3

Direction: Inbound

Type : Enhancement

Policy: a

Classifier: a

Operator: AND

Rule(s) :

If-match any

Behavior: a

Committed Access Rate:

CIR 112 (kbps), CBS 51200 (Bytes), EBS 0 (Bytes)

Green action : pass

Yellow action : pass

Red action : discard

Green packets : 0 (Packets)

Red packets : 0 (Packets)

Table 12 Command output

Field	Description
Direction	Direction in which the QoS policy is applied.
Policy	User-defined QoS policy name or system-defined QoS policy name.
Type	Mode in which the QoS policy is applied to an interface, which can only be Enhancement. If you do not specify the mode when applying a QoS policy to an interface, this field does not appear.
Matched	Number of matching packets.
Forwarded	Average rate of successfully forwarded matching packets in a statistics collection period.
Dropped	Average rate of dropped matching packets in a statistics collection period.
Green packets	Traffic statistics for green packets.
Yellow packets	Traffic statistics for yellow packets.
Red packets	Traffic statistics for red packets.
Redirect to SR-TE policy	Redirect traffic to an SR-MPLS TE policy. The NID field indicates the Next Hop Label Forwarding Entry (NHLFE) entry index of the SR-MPLS TE policy.
Redirect to SRv6-TE policy	Redirect traffic to an SRv6 TE policy: · Forwarding ID—Forwarding entry index of the SRv6 TE policy. · SID—SRv6 SID of the egress node.

For the description of other fields, see Table 1, Table 4, and Table 6.

qos apply policy (interface view, control plane view, control-plane management view)

Use qos apply policy to apply a QoS policy to an interface.

Use undo qos apply policy to remove an applied QoS policy.

Syntax

qos apply policy policy-name { inbound [ postposition | enhancement ] | outbound [ enhancement ] }

undo qos apply policy policy-name { inbound [ postposition | enhancement ] | outbound [ enhancement ] }

Default

No QoS policy is applied.

Views

Interface view

Predefined user roles

network-admin

context-admin

vsys-admin

Parameters

policy-name: Specifies a QoS policy by its name, a case-sensitive string of 1 to 31 characters.

inbound: Applies the QoS policy to incoming traffic.

outbound: Applies the QoS policy to outgoing traffic.

enhancement: Applies the QoS policy in enhanced mode.

postposition: Matches VPN traffic in the outbound direction on an input interface. If you do not specify this keyword, a QoS policy can match only inbound VPNs.

Usage guidelines

When you apply a QoS policy to an interface, follow these rules:

· The bandwidth assigned to AF and EF queues in the QoS policy must be smaller than the available bandwidth of the interface. Otherwise, the QoS policy cannot be successfully applied to the interface.

· If you modify the available bandwidth of the interface to be smaller than the bandwidth for AF and EF queues, the applied QoS policy is removed.

· An inbound QoS policy cannot contain any of these queuing actions: queue ef, queue af, or queue wfq.

If the action is redirecting traffic to a security card, the QoS policy must be applied in enhanced mode.

If a packet carries VPN information (such as MPLS label) when entering an interface, it indicates that the packet comes from a VPN in the inbound direction. If a packet carries VPN information (such as MPLS label) when leaving an interface, it indicates that the packet goes to a VPN in the outbound direction. Typically, when a packet enters an interface, the device executes a QoS policy before performing a routing table lookup for forwarding. In this case, the device can obtain the inbound VPN information instead of outbound VPN information. If you specify the postposition keyword, the device will perform a routing table lookup for an incoming packet to obtain outbound VPN information before executing a QoS policy. This can match outbound VPN traffic on the input interface.

If the device forwards traffic received on multiple interfaces to one VPN in the outbound direction, you can apply a QoS policy to each of the input interfaces with the postposition keyword. This can improve the matching performance of the QoS policy. The postposition keyword is supported only when a QoS policy is applied to an interface.

You can use the following commands to match protocol packets sent to the CPU for a QoS policy applied to a control plane:

· if-match control-plane protocol

· if-match control-plane protocol-group

· if-match acl

When you use the if-match acl command to match protocol packets sent to the CPU, follow these restrictions and guidelines:

¡ The used ACL must be an advanced ACL.

¡ You must specify TCP or UDP for the protocol argument in the rule.

¡ You must specify a source port or destination port by using the eq operator in the rule.

For example, an IPv4 advanced ACL that contains a rule permit tcp source-port eq 80 statement can match TCP packets sent to the CPU.

Examples

# Apply QoS policy USER1 to the incoming traffic of GigabitEthernet 1/0/1.

<Sysname> system-view

[Sysname] interface gigabitethernet 1/0/1

[Sysname-GigabitEthernet1/0/1] qos apply policy USER1 inbound

# Apply QoS policy bbb to the incoming traffic of the management interface control plane.

<Sysname> system-view

[Sysname] control-plane management

[Sysname-cp-management] qos apply policy bbb inbound

# Apply QoS policy aaa to the outgoing traffic of GigabitEthernet 1/0/1 in enhanced mode.

<Sysname> system-view

[Sysname] interface gigabitethernet 1/0/1

[Sysname-GigabitEthernet1/0/1]qos apply policy aaa outbound enhancement

qos apply policy global

Use qos apply policy global to apply a QoS policy globally.

Use undo qos apply policy global to remove a globally applied QoS policy.

Syntax

qos apply policy policy-name global { inbound | outbound } enhancement

undo qos apply policy policy-name global { inbound | outbound }

Default

No QoS policy is applied globally.

Views

System view

Predefined user roles

network-admin

context-admin

Parameters

policy-name: Specifies a QoS policy by its name, a case-sensitive string of 1 to 31 characters.

inbound: Applies the QoS policy to the incoming packets on all interfaces.

outbound: Applies the QoS policy to the outgoing packets on all interfaces.

enhancement: Applies the QoS policy in enhanced mode. A QoS policy applied with the enhancement keyword efficiently processes packets but supports fewer parameters than that applied without the enhancement keyword.

Usage guidelines

A global QoS policy takes effect on all incoming or outgoing traffic depending on the direction in which the QoS policy is applied.

Examples

# Globally apply QoS policy user1 to the incoming trafficin enhanced mode.

<Sysname> system-view

[Sysname] qos apply policy user1 global inbound enhancement

qos policy

Use qos policy to create a QoS policy and enter its view, or enter the view of an existing QoS policy.

Use undo qos policy to delete a QoS policy.

Syntax

qos policy policy-name

undo qos policy policy-name

Default

No QoS policies exist.

Views

System view

Predefined user roles

network-admin

context-admin

vsys-admin

Parameters

policy-name: Specifies a name for the QoS policy, a case-sensitive string of 1 to 31 characters.

Usage guidelines

To delete a QoS policy that has been applied to an object, you must first remove the QoS policy from the object.

Examples

# Create a QoS policy named user1.

<Sysname> system-view

[Sysname] qos policy user1

[Sysname-qospolicy-user1]

Related commands

classifier behavior

qos apply policy

· qos apply policy global

reset qos policy control-plane

Use reset qos policy control-plane to clear the statistics of the QoS policy applied to a control plane.

Syntax

In standalone mode:

reset qos policy control-plane slot slot-number [ cpu cpu-number ]

In IRF mode:

reset qos policy control-plane chassis chassis-number slot slot-number [ cpu cpu-number ]

Views

User view

Predefined user roles

network-admin

context-admin

Parameters

slot slot-number: Specifies a card by its slot number.

cpu cpu-number: Specifies a CPU by its number. This option is available only if multiple CPUs are available on the specified slot.

Examples

# (In standalone mode.) Clear the statistics of the QoS policy applied to the control plane of slot 1.

<Sysname> reset qos policy control-plane slot 1

# (In IRF mode.) Clear the statistics of the QoS policy applied to the control plane of slot 3 in chassis 1.

<Sysname> reset qos policy control-plane chassis 1 slot 3

reset qos policy control-plane management

Use reset qos policy control-plane management to clear the statistics of the QoS policy applied in control-plane management view.

Syntax

reset qos policy control-plane management

Views

User view

Predefined user roles

network-admin

context-admin

Examples

# Clear the statistics of the QoS policy applied in control-plane management view.

<Sysname> reset qos policy control-plane management

reset qos policy global

Use reset qos policy global to clear the statistics of a global QoS policy.

Syntax

reset qos policy global [ inbound | outbound ]

Views

User view

Predefined user roles

network-admin

context-admin

Parameters

inbound: Clears the statistics of the global QoS policy applied to incoming traffic globally.

outbound: Clears the statistics of the global QoS policy applied to outgoing traffic globally.

Usage guidelines

If you do not specify a direction, this command clears the statistics of the global QoS policies in both directions.

Examples

# Clear the statistics of the global QoS policy applied to the incoming traffic globally.

<Sysname> reset qos policy global inbound

QoS policy-based traffic rate statistics collection period commands

qos flow-interval

Use qos flow-interval to set the QoS policy-based traffic rate statistics collection period for an interface.

Use undo qos flow-interval to restore the default.

Syntax

qos flow-interval interval

undo qos flow-interval

Default

The QoS policy-based traffic rate statistics collection period is 5 minutes on an interface.

Views

Interface view

Predefined user roles

network-admin

context-admin

Parameters

interval: Sets the QoS policy-based traffic rate statistics collection period in minutes. The value range for this argument is 1 to 10.

Usage guidelines

You can enable collection of per-class traffic statistics over a period of time, including the average forwarding rate and drop rate. For example, if you set the statistics collection period to 10 minutes, the system performs the following operations:

· Collects traffic statistics for the most recent 10 minutes.

· Refreshes the statistics every 10/5 minutes, 2 minutes.

The traffic rate statistics collection period of a subinterface is the same as the period configured on the main interface.

Examples

# Set the QoS policy-based traffic rate statistics collection period to 10 minutes on GigabitEthernet 1/0/1.

<Sysname> system-view

[Sysname] interface gigabitethernet 1/0/1

[Sysname-GigabitEthernet1/0/1] qos flow-interval 10

Related commands

display qos policy interface

Traffic policing commands

display qos car interface

Use display qos car interface to display the CAR configuration and statistics for interfaces.

Syntax

display qos car interface [ interface-type interface-number ]

Views

Any view

Predefined user roles

network-admin

network-operator

context-admin

context-operator

Parameters

interface-type interface-number: Specifies an interface by its type and number. If you do not specify an interface, this command displays the CAR configuration and statistics for all interfaces except VA interfaces. For information about VA interfaces, see PPP in PPP and PPPoE Configuration Guide.

Usage guidelines

If you specify a VT interface, this command displays the CAR configuration and statistics of each VA interface of the VT interface. It does not display QoS information about the VT interface.

Examples

# Display the CAR configuration and statistics for GigabitEthernet 1/0/1.

<Sysname> display qos car interface gigabitethernet 1/0/1

Interface: GigabitEthernet1/0/1

Direction: inbound

Rule: If-match any

CIR 128 (kbps), CBS 5120 (Bytes), PIR 128 (kbps), EBS 512 (Bytes)

Green action : pass

Yellow action : pass

Red action : discard

Green packets : 0 (Packets), 0 (Bytes)

Yellow packets: 0 (Packets), 0 (Bytes)

Red packets : 0 (Packets), 0 (Bytes)

Direction: outbound

Overhead compensation length: 14

Rule: If-match acl 2000

CIR 1000 (kbps), CBS 62500 (Bytes), EBS 0 (Bytes)

Green action : pass

Yellow action : pass

Red action : discard

Green packets : 0 (Packets), 0 (Bytes)

Yellow packets: 0 (Packets), 0 (Bytes)

Red packets : 0 (Packets), 0 (Bytes)

# Display the CAR information on GigabitEthernet 1/0/2.

<Sysname> display qos car interface gigabitethernet 1/0/2

Interface: GigabitEthernet1/0/2

Direction: inbound

Rule: If-match any

CIR 50 (%), CBS 600 (ms), EBS 0 (ms), PIR 50 (%)

Green action : pass

Yellow action : pass

Red action : discard

Green packets : 0 (Packets), 0 (Bytes)

Yellow packets: 0 (Packets), 0 (Bytes)

Red packets : 0 (Packets), 0 (Bytes)

# Display the configuration and statistics for dynamic traffic policing on GigabitEthernet 1/0/1.

<Sysname> display qos car interface gigabitethernet 1/0/1

Interface: GigabitEthernet1/0/1

Direction: inbound

Rule: If-match carl 1

CIR 128 (kbps), CBS 5120 (Bytes)

Max CIR 500 (kbps) (Active)

Bandwidth utilization threshold: 5000 (kbps)

Online session count : 10

CurrentCIR : 200 (kbps)

Current bandwidth : 2000 (kbps)

Green action : pass

Yellow action : pass

Red action : discard

Green packets : 0 (Packets), 0 (Bytes)

Yellow packets: 0 (Packets), 0 (Bytes)

Red packets : 0 (Packets), 0 (Bytes)

Table 13 Command output

Field	Description
Interface	Interface name, including interface type and interface number.
Direction	Direction in which traffic policing is applied.
Rule	Match criteria.
CIR	CIR in kbps.
CBS	CBS in bytes.
EBS	EBS in bytes.
Max CIR	Maximum CIR in kbps: · Active—Dynamic traffic policing has taken effect. · Inactive—Dynamic traffic policing has not taken effect.
PIR	PIR in kbps.
Green action	Action to take on green packets.
Yellow action	Action to take on yellow packets.
Red action	Action to take on red packets.
Overhead compensation length	Packet compensation length in bytes for outbound traffic policing.
Online session count	Number of current online sessions.
Current CIR	CIR in kbps after dynamic adjustment.
Current bandwidth	The actual total traffic rate in kbps for all online sessions. This value might be greater than the current CIR multiplied by the number of current online sessions.
Bandwidth utilization threshold	Maximum bandwidth threshold in kbps. · If the bandwidth command is not executed on the interface, this value is the actual interface bandwidth multiplied by the maximum bandwidth percentage. · If the bandwidth command is executed on the interface, this value is the configured interface bandwidth multiplied by the maximum bandwidth percentage.

Related commands

bandwidth (Interface Command Reference)

qos car (interface view)

qos carl

qos car bandwidth-refresh-interval

qos car bandwidth-utilization-threshold

display qos carl

Use display qos carl to display CAR lists.

Syntax

In standalone mode:

display qos carl [ carl-index ] [ slot slot-number [ cpu cpu-number ] ]

In IRF mode:

display qos carl [ carl-index ] [ chassis chassis-number slot slot-number [ cpu cpu-number ] ]

Views

Any view

Predefined user roles

network-admin

network-operator

context-admin

context-operator

Parameters

carl-index: Specifies a CAR list by its number in the range of 1 to 199. If you do not specify a CAR list, this command displays all CAR lists.

slot slot-number: Specifies a card by its slot number. If you do not specify a card, this command displays the CAR lists for the active MPU. (In standalone mode.)

chassis chassis-number slot slot-number: Specifies a card on an IRF member device. The chassis-number argument represents the member ID of the IRF member device. The slot-number argument represents the slot number of the card. If you do not specify this option, the command displays the CAR lists for the global active MPU. (In IRF mode.)

cpu cpu-number: Specifies a CPU by its number. This option is available only if multiple CPUs are available on the specified slot.

Examples

# Display all CAR lists.

<Sysname> display qos carl

List Rules

1 destination-ip-address range 1.1.1.1 to 1.1.1.2 per-address shared-bandwidth

2 destination-ip-address subnet 1.1.1.1 22 per-address shared-bandwidth

4 dscp 1 2 3 4 5 6 7 cs1

5 mac 0000-0000-0000

6 mpls-exp 0 1 2

9 precedence 0 1 2 3 4 5 6 7

10 source-ip-address range 1.1.1.1 to 1.1.1.2

11 source-ip-address subnet 1.1.1.1 31

qos car

Use qos car to configure a CAR policy on an interface.

Use undo qos car to delete a CAR policy from an interface.

Syntax

qos car { inbound | outbound } { any | acl [ ipv6 ] acl-number | carl carl-index } cir committed-information-rate [ cbs committed-burst-size [ ebs excess-burst-size ] ] [ green action | red action | yellow action ] *

qos car { inbound | outbound } { any | acl [ ipv6 ] acl-number | carl carl-index } cir committed-information-rate [ cbs committed-burst-size ] pir peak-information-rate [ ebs excess-burst-size ] [ green action | red action | yellow action ] *

undo qos car { inbound | outbound } { any | acl [ ipv6 ] acl-number | carl carl-index }

Default

No CAR policy is configured.

Views

Interface view

Predefined user roles

network-admin

context-admin

Parameters

inbound: Performs CAR for incoming packets on the interface.

outbound: Performs CAR for outgoing packets on the interface.

any: Performs CAR for all IP packets in the specified direction.

acl [ ipv6 ] acl-number: Performs CAR for packets matching an ACL specified by its number. The value range for the acl-number argument is 2000 to 2999 for basic ACLs and 3000 to 3999 for advanced ACLs. If you do not specify ipv6, this option specifies an IPv4 ACL. If you specify ipv6, this option specifies an IPv6 ACL.

carl carl-index: Performs CAR for packets matching a CAR list specified by its number in the range of 1 to 199.

cir committed-information-rate: Specifies the CIR in kbps. The value range for committed-information-rate is 8 to 10000000.

cbs committed-burst-size: Specifies the CBS in bytes, which is the size of bursty traffic when the actual average rate is not greater than the CIR. The value range for committed-burst-size is 1875 to 19375000. The default CBS is the product of 62.5 and the CIR.

ebs excess-burst-size: Specifies the EBS in bytes. The value range for excess-burst-size is 0 to 19375000. The default EBS is 0.

pir peak-information-rate: Specifies the PIR in kbps. The value range for peak-information-rate is 8 to 10000000.

green: Specifies the action to take on packets when the traffic rate conforms to the CIR. The default is pass.

red: Specifies the action to take on packets when the traffic rate conforms to neither CIR nor PIR. The default is discard.

yellow: Specifies the action to take on packets when the traffic rate exceeds the CIR but conforms to the PIR. The default is pass.

action: Specifies the action to take on packets:

· continue: Continues to process the packet by using the next CAR policy.

· discard: Drops the packet.

· pass: Permits the packet to pass through.

· remark-dot1p-continue new-cos: Sets the 802.1p priority value of the 802.1p packet to new-cos and continues to process the packet by using the next CAR policy. The new-cos argument is in the range of 0 to 7.

· remark-dot1p-pass new-cos: Sets the 802.1p priority value of the 802.1p packet to new-cos and permits the packet to pass through. The new-cos argument is in the range of 0 to 7.

· remark-dscp-continue new-dscp: Remarks the packet with a new DSCP value and continues to process the packet by using the next CAR policy. The new-dscp argument is in the range of 0 to 63. Alternatively, you can specify the new-dscp argument with af11, af12, af13, af21, af22, af23, af31, af32, af33, af41, af42, af43, cs1, cs2, cs3, cs4, cs5, cs6, cs7, default, or ef.

· remark-dscp-pass new-dscp: Remarks the packet with a new DSCP value and permits the packet to pass through. The new-dscp argument is in the range of 0 to 63. Alternatively, you can specify the new-dscp argument with af11, af12, af13, af21, af22, af23, af31, af32, af33, af41, af42, af43, cs1, cs2, cs3, cs4, cs5, cs6, cs7, default, or ef.

· remark-mpls-exp-continue new-exp: Sets the EXP field value of the MPLS packet to new-exp and continues to process the packet by using the next CAR policy. The new-exp argument is in the range of 0 to 7.

· remark-mpls-exp-pass new-exp: Sets the EXP field value of the MPLS packet to new-exp and permits the packet to pass through. The new-exp argument is in the range of 0 to 7.

· remark-prec-continue new-precedence: Remarks the packet with a new IP precedence and continues to process the packet by using the next CAR policy. The new-precedence argument is in the range of 0 to 7.

· remark-prec-pass new-precedence: Remarks the packet with a new IP precedence and permits the packet to pass through. The new-precedence argument is in the range of 0 to 7.

Usage guidelines

To use two rates for traffic policing, configure the qos car command with the pir peak-information-rate option. To use one rate for traffic policing, configure the qos car command without the pir peak-information-rate option.

You can configure multiple qos car commands on an interface to define multiple CAR policies. These CAR policies are executed in their configuration order.

Examples

# Perform CAR for all packets in the outbound direction of GigabitEthernet 1/0/1. The CAR parameters are as follows:

· CIR is 200 kbps.

· CBS is 5120 bytes.

· EBS is 0.

· Conforming packets are transmitted.

· Excess packets are set with an IP precedence of 0 and transmitted.

<Sysname> system-view

[Sysname] interface gigabitethernet 1/0/1

[Sysname-GigabitEthernet1/0/1] qos car outbound any cir 200 cbs 5000 ebs 0 green pass red remark-prec-pass 0

Related commands

display qos car interface

qos carl

Use qos carl to create or modify a CAR list.

Use undo qos carl to delete a CAR list.

Syntax

qos carl carl-index { dscp dscp-list | mac mac-address | mpls-exp mpls-exp-value | precedence precedence-value | { destination-ip-address | source-ip-address } { range start-ip-address to end-ip-address | subnet ip-address mask-length } [ per-address [ shared-bandwidth ] ] }

undo qos carl carl-index

Default

No CAR list is configured.

Views

System view

Predefined user roles

network-admin

context-admin

Parameters

carl-index: Specifies a CAR list by its number in the range of 1 to 199.

dscp dscp-list: Specifies a list of DSCP values. A DSCP value can be a number from 0 to 63 or any of the following keywords af11, af12, af13, af21, af22, af23, af31, af32, af33, af41, af42, af43, cs1, cs2, cs3, cs4, cs5, cs6, cs7, default, or ef. You can configure up to eight DSCP values in one command line. If the same DSCP value is specified multiple times, the system considers the values to be one value. If a packet matches one of the defined DSCP values, it matches the if-match clause.

mac mac-address: Specifies a MAC address in hexadecimal format.

mpls-exp mpls-exp-value: Specifies an MPLS EXP value in the range of 0 to 7. You can configure up to eight MPLS EXP values in one command line. If the same MPLS EXP value is specified multiple times, the system considers the values to be one value. If a packet matches one of the defined MPLS EXP values, it matches the if-match clause.

precedence precedence: Specifies a precedence value in the range of 0 to 7. You can configure up to eight IP precedence values in one command line. If the same IP precedence value is specified multiple times, the system considers the values to be one value. If a packet matches one of the defined IP precedence values, it matches the if-match clause.

destination-ip-address: Configures a destination IP address-based CAR list.

source-ip-address: Configures a source IP address-based CAR list.

range start-ip-address to end-ip-address: Specifies an IP address range by the start address and end address. The value for end-ip-address must be greater than the value for start-ip-address.

subnet ip-address mask-length: Specifies a subnet by the IP subnet address and IP subnet address mask length.

per-address: Performs per-IP address rate limiting within the network segment. When this keyword is specified, the CIR is dedicated bandwidth for each IP address and is not shared by any other IP address. If you do not specify this keyword, the following events occur:

· Rate limiting is performed for the entire network segment.

· All of the CIR is allocated among all IP addresses in proportion to the traffic load of each IP address.

shared-bandwidth: Specifies that traffic of all IP addresses within the network segment shares the remaining bandwidth (the CIR). If you specify this keyword, all of the CIR is allocated evenly among all IP addresses with traffic load.

Usage guidelines

You can create a CAR list based on IP precedence, MAC address, MPLS EXP, DSCP, or IP network segment.

If you execute this command multiple times for the same CAR list, the most recent configuration takes effect. If you execute this command multiple times for different CAR lists, multiple CAR lists are created.

To perform rate limiting for a single IP address, use the qos car acl command in interface view.

Examples

# Apply CAR list 1 to the outbound direction of GigabitEthernet 1/0/1 to meet the following requirements:

· The rate of each host on the subnet 1.1.1.0/24 is limited to 512 kbps.

· Traffic of IP addresses in the subnet does not share the remaining bandwidth.

<Sysname> system-view

[Sysname] qos carl 1 source-ip-address subnet 1.1.1.0 24 per-address

[Sysname] interface gigabitethernet 1/0/1

[Sysname-GigabitEthernet1/0/1] qos car outbound carl 1 cir 512 cbs 5120 ebs 0 green pass red discard

# Apply CAR list 2 to the outbound direction of GigabitEthernet 1/0/1 to meet the following requirements:

· The rate of each host in the IP address range of 1.1.2.100 to 1.1.2.199 is limited to 5 Mbps.

· Traffic of IP addresses in the subnet shares the remaining bandwidth.

<Sysname> system-view

[Sysname] qos carl 2 source-ip-address range 1.1.2.100 to 1.1.2.199 per-address shared-bandwidth

[Sysname] interface gigabitethernet 1/0/1

[Sysname-GigabitEthernet1/0/1] qos car outbound carl 2 cir 5120 cbs 51200 ebs 51200 green pass red discard

Related commands

display qos carl

qos car

Rate limit commands

display qos lr

Use display qos lr to display the rate limit configuration and statistics for interfaces.

Syntax

display qos lr interface [ interface-type interface-number ]

Views

Any view

Predefined user roles

network-admin

network-operator

context-admin

context-operator

Parameters

interface-type interface-number: Specifies an interface by its type and number. If you do not specify an interface, this command displays the rate limit configuration and statistics for all interfaces except VA interfaces. For information about VA interfaces, see PPP in PPP and PPPoE Configuration Guide.

Usage guidelines

If you specify a VT interface, this command displays the rate limit configuration and statistics of each VA interface of the VT interface. It does not display QoS information about the VT interface.

Examples

# Display the rate limit configuration and statistics for all interfaces.

<Sysname> display qos lr interface

Interface: GigabitEthernet1/0/1

Direction: Outbound

CIR 2000 (kbps), CBS 20480 (Bytes), EBS 0 (Bytes)

Passed : 1000 (Packets) 1000 (Bytes)

Discarded: 1000 (Packets) 1000 (Bytes)

Delayed : 1000 (Packets) 1000 (Bytes)

Active shaping: No

Interface: GigabitEthernet1/0/2

Direction: Outbound

CIR 64 (kbps), CBS 512 (Bytes), EBS 0 (Bytes)

Passed : 1000 (Packets) 1000 (Bytes)

Discarded: 1000 (Packets) 1000 (Bytes)

Delayed : 1000 (Packets) 1000 (Bytes)

Active shaping: No

Table 14 Command output

Field	Description
Interface	Interface name, including the interface type and interface number.
Direction	Direction in which the rate limit configuration is applied.
CIR	CIR in kbps (if the CIR is specified in absolute value) or in percentage (if the CIR is specified in percentage).
CBS	CBS in bytes (if the CBS is specified in absolute value) or in ms (if the CBS is specified in milliseconds). When the CBS is specified in milliseconds, the actual CBS value is cbs-time × the actual CIR value.
EBS	EBS in bytes (if the EBS is specified in absolute value) or in ms (if the EBS is specified in milliseconds). When the EBS is specified in milliseconds, the actual EBS value is ebs-time × the actual CIR value.
Passed	Number and bytes of packets that have passed.
Discarded	Number and bytes of dropped packets.
Delayed	Number and bytes of delayed packets.
Active shaping	Indicates whether the rate limit configuration is activated: · Yes—Activated. · No—Not activated.

qos lr

Use qos lr to configure rate limiting on an interface.

Use undo qos lr to delete the rate limit configuration on an interface.

Syntax

qos lr outbound cir committed-information-rate [ cbs committed-burst-size [ ebs excess-burst-size ] ]

undo qos lr outbound

Default

No rate limit is configured.

Views

Interface view

Predefined user roles

network-admin

context-admin

Parameters

outbound: Limits the rate of outgoing packets.

cir committed-information-rate: Specifies the CIR in kbps. The value range for committed-information-rate varies by device view.

cbs committed-burst-size: Specifies the CBS in the range of 1875 to 19375000 bytes. The default CBS is the product of 62.5 and the CIR.

ebs excess-burst-size: Specifies the EBS in bytes, which is the traffic exceeding CBS when two token buckets are used. The value range for excess-burst-size is 0 to 19375000. The default EBS is 0.

Examples

# Limit the rate of outgoing packets on GigabitEthernet 1/0/1, with CIR 256 kbps and CBS 51200 bytes.

<Sysname> system-view

[Sysname] interface gigabitethernet 1/0/1

[Sysname-GigabitEthernet1/0/1] qos lr outbound cir 256 cbs 51200

Congestion management commands

Common commands

display qos queue interface

Use display qos queue interface to display the queuing information for interfaces.

Syntax

display qos queue interface [ interface-type interface-number ]

Views

Any view

Predefined user roles

network-admin

network-operator

context-admin

context-operator

Parameters

interface-type interface-number: Specifies an interface by its type and number. If you do not specify an interface, this command displays the queuing information for all interfaces except VA interfaces. For information about VA interfaces, see PPP in PPP and PPPoE Configuration Guide.

Usage guidelines

If you specify a VT interface, this command displays the queuing information of each VA interface of the VT interface. It does not display QoS information about the VT interface.

Examples

# Display the queuing information for all interfaces.

<Sysname> display qos queue interface

Interface: GigabitEthernet1/0/1

Output queue - Urgent queuing: Size/Length/Discards 0/100/0

Output queue - Protocol queuing: Size/Length/Discards 0/500/0

Output queue - Weighted Fair queuing: Size/Length/Discards 0/64/0

Weight: IP Precedence

Queues: Active/Max active/Total 0/0/128

Interface: GigabitEthernet1/0/2

Output queue - Urgent queuing: Size/Length/Discards 0/100/0

Output queue - Protocol queuing: Size/Length/Discards 0/500/0

Output queue - FIFO queuing: Size/Length/Discards 0/75/0

Table 15 Command output

Field	Description
Interface	Interface name, including the interface type and interface number.
Output queue	Type of the current output queue.
Group	Number of the group that holds the queue.
Weight	Packet-count scheduling weight of the queue. N/A is displayed for a queue that uses the SP scheduling algorithm.
Byte-count	Byte-count scheduling weight of the queue. N/A is displayed for a queue that uses the SP scheduling algorithm.

FIFO queuing commands

display qos queue fifo

Use display qos queue fifo to display the FIFO information for interfaces.

Syntax

display qos queue fifo interface [ interface-type interface-number ]

Views

Any view

Predefined user roles

network-admin

network-operator

context-admin

context-operator

Parameters

interface-type interface-number: Specifies an interface by its type and number. If you do not specify an interface, this command displays the FIFO information for all interfaces except VA interfaces. For information about VA interfaces, see PPP in PPP and PPPoE Configuration Guide.

Usage guidelines

If you specify a VT interface, this command displays the FIFO information of each VA interface of the VT interface. It does not display QoS information about the VT interface.

Examples

# Display the FIFO information for all interfaces.

<Sysname> display qos queue fifo interface

Interface: GigabitEthernet1/0/2

Output queue - Urgent queuing: Size/Length/Discards 0/100/0

Output queue - Protocol queuing: Size/Length/Discards 0/500/0

Output queue - FIFO queuing: Size/Length/Discards 0/75/0

Table 16 Command output

Field	Description
Interface	Interface name, including the interface type and interface number.
Size	Total number of bytes of packets in all queues.
Length	Number of packets allowed in each queue.
Discards	Number of packets dropped.

qos fifo queue-length

Use qos fifo queue-length to set the FIFO queue length for an an interface.

Use undo qos fifo queue-length to restore the default.

Syntax

qos fifo queue-length queue-length

undo qos fifo queue-length

Default

The FIFO queue length is 75.

Views

Interface view

Predefined user roles

network-admin

context-admin

Parameters

queue-length: Specifies the maximum number of packets allowed in the FIFO queue, in the range of 1 to 1024.

Usage guidelines

For FIFO queuing to take effect on a subinterface, you must configure the rate limit on the subinterface.

Examples

# Set the FIFO queue length to 100.

<Sysname> system-view

[Sysname] interface gigabitethernet 1/0/1

[Sysname-GigabitEthernet1/0/1] qos fifo queue-length 100

Related commands

display qos queue fifo interface

CBQ commands

display qos queue cbq

Use display qos queue cbq to display the CBQ information for interfaces.

Syntax

display qos queue cbq interface [ interface-type interface-number ]

Views

Any view

Predefined user roles

network-admin

network-operator

context-admin

context-operator

Parameters

interface-type interface-number: Specifies an interface by its type and number. If you do not specify an interface, this command the CBQ information for all interfaces except VA interfaces. For information about VA interfaces, see PPP in PPP and PPPoE Configuration Guide.

Usage guidelines

If you specify a VT interface, this command displays the CBQ information for all VA interfaces of the VT interface. It does not display QoS information about the VT interface.

Examples

# Display the CBQ information for all interfaces.

<Sysname> display qos queue cbq interface

Interface: GigabitEthernet1/0/1

Output queue - Urgent queuing: Size/Length/Discards 0/100/0

Output queue - Protocol queuing: Size/Length/Discards 0/500/0

Output queue - Class Based Queuing: Size/Discards 0/0

Queue Size: EF/AF/BE 0/0/0

BE Queues: Active/Max active/Total 0/0/256

AF Queues: Allocated 1

Bandwidth(kbps): Available/Max reserve 74992/75000

Table 17 Command output

Field	Description
Interface	Interface name, including the interface type and interface number.
Size	Total number of bytes of packets in all queues.
Length	Number of packets allowed in each queue.
Discards	Number of dropped packets.
EF	EF queue.
AF	AF queue.
BE	BE queue.
Active	Number of active BE queues.
Max active	Maximum number of active BE queues allowed.
Total	Total number of BE queues.
Available	Available bandwidth for CBQ.
Max reserve	Maximum reserved bandwidth for CBQ.

qos reserved-bandwidth

Use qos reserved-bandwidth to set the maximum reserved bandwidth as a percentage of available bandwidth on the interface.

Use undo qos reserved-bandwidth to restore the default.

Syntax

qos reserved-bandwidth pct percent

undo qos reserved-bandwidth

Default

The maximum reserved bandwidth is 80% of available bandwidth on the interface.

Views

Interface view

Predefined user roles

network-admin

context-admin

Parameters

percent: Specifies the percentage of available bandwidth to be reserved. The value range for this argument is 1 to 100.

Usage guidelines

The maximum reserved bandwidth is set on a per-interface or per-PVC basis. It decides the maximum bandwidth assignable for the QoS queues on an interface or PVC. It is typically set no greater than 80% of available bandwidth, considering the bandwidth for control traffic and Layer 2 frame headers.

Use the default maximum reserved bandwidth setting in most situations. If you adjust the setting, make sure the Layer 2 frame header plus the data traffic is under the maximum available bandwidth of the interface.

The maximum available bandwidth of an interface can be set by using the bandwidth command. For more information about this command, see Interface Command Reference.

If you execute the qos reserved-bandwidth pct command multiple times, the most recent configuration takes effect.

Examples

# Set the maximum reserved bandwidth to 70% of available bandwidth on GigabitEthernet 1/0/1.

<Sysname> system-view

[Sysname] interface gigabitethernet 1/0/1

[Sysname-GigabitEthernet1/0/1] qos reserved-bandwidth pct 70

queue af

Use queue af to enable assured-forwarding (AF) and set its minimum guaranteed bandwidth.

Use undo queue af to restore the default.

Syntax

queue af bandwidth { bandwidth | pct percentage | remaining-pct remaining-percentage }

undo queue af

Default

AF is not configured.

Views

Traffic behavior view

Predefined user roles

network-admin

context-admin

Parameters

bandwidth: Specifies the bandwidth in kbps. The value range for this argument is 8 to 10000000.

pct percentage: Specifies the percentage of the available bandwidth, in the range of 1 to 100.

remaining-pct remaining-percentage: Specifies the percentage of the remaining bandwidth, in the range of 1 to 100.

Usage guidelines

To associate the traffic behavior configured with the queue af command with a class in a policy, you must follow these requirements:

· The total bandwidth assigned to AF and EF queues in a policy cannot exceed the maximum available bandwidth of the interface where the policy is applied.

· The total percentage of bandwidth assigned to AF and EF in a policy cannot exceed 100.

· The bandwidth assigned to AF and EF in a policy must use the same form, either as an absolute bandwidth value or as a percentage.

If you execute the queue af command multiple times, the most recent configuration takes effect.

Examples

# Configure AF in traffic behavior database and assign the minimum guaranteed bandwidth 200 kbps to it.

<Sysname> system-view

[Sysname] traffic behavior database

[Sysname-behavior-database] queue af bandwidth 200

Related commands

display qos queue cbq interface

traffic behavior

queue ef

Use queue ef to configure expedited forwarding (EF) and assign its maximum bandwidth.

Use undo queue ef to restore the default.

Syntax

queue ef bandwidth { bandwidth [ cbs burst ] | pct percentage [ cbs-ratio ratio ] }

undo queue ef

Default

EF is not configured.

Views

Traffic behavior view

Predefined user roles

network-admin

context-admin

Parameters

bandwidth: Specifies the bandwidth in kbps. The value range for this argument is 8 to 10000000.

cbs burst: Sets the CBS in bytes. The value range for this argument is 32 to 1000000000. The default is bandwidth × 25.

pct percentage: Specifies the percentage of the available bandwidth, in the range of 1 to 100.

cbs-ratio ratio: Sets the allowed burst ratio in the range of 25 to 500. This default is 25.

Usage guidelines

You cannot use this command in conjunction with the queue af or queue-length command in the same traffic behavior.

In a policy, the default class cannot be associated with the traffic behavior that has the queue ef command.

The total bandwidth assigned to AF and EF in a policy cannot exceed the maximum available bandwidth of the interface where the policy is applied.

The total percentage of the maximum available bandwidth assigned to AF and EF in a policy cannot exceed 100.

The bandwidths assigned to AF and EF in a policy must have the same type, bandwidth or percentage.

After the queue ef bandwidth pct percentage [ cbs-ratio ratio ] command is used, CBS equals (Interface available bandwidth × percentage × ratio)/100/1000.

After the queue ef bandwidth bandwidth [ cbs burst ] command is used, CBS equals burst. If the burst argument is not specified, CBS equals bandwidth × 25.

If you execute the queue ef command multiple times, the most recent configuration takes effect.

Examples

# Configure EF in traffic behavior database, with the maximum bandwidth as 200 kbps and CBS as 5000 bytes.

<Sysname> system-view

[Sysname] traffic behavior database

[Sysname-behavior-database] queue ef bandwidth 200 cbs 5000

Related commands

display qos queue cbq interface

traffic behavior

queue wfq

Use queue wfq to configure WFQ for the default class.

Use undo queue wfq to restore the default.

Syntax

queue wfq [ queue-number total-queue-number ]

undo queue wfq

Default

WFQ is not configured for the default class.

Views

Traffic behavior view

Predefined user roles

network-admin

context-admin

Parameters

queue-number total-queue-number: Specifies the number of fair queues, which can be 16, 32, 64, 128, 256, 512, 1024, 2048, or 4096. The default is 256.

Usage guidelines

The traffic behavior configured with this command can only be associated with the default class. This command can be used in conjunction with the queue-length or wred command in the same traffic behavior.

Examples

# Configure the default class to use WFQ with 16 queues.

<Sysname> system-view

[Sysname] traffic behavior test

[Sysname-behavior-test] queue wfq queue-number 16

[Sysname] qos policy user1

[Sysname-qospolicy-user1] classifier default-class behavior test

Related commands

display qos queue cbq interface

traffic behavior

queue-length

Use queue-length to set the queue length used for tail drop.

Use undo queue-length to restore the default.

Syntax

queue-length queue-length

undo queue-length

Default

The queue length used for tail drop is 64.

Views

Traffic behavior view

Predefined user roles

network-admin

context-admin

Parameters

queue-length: Specifies the maximum number of packets allowed in the FIFO queue. The value range for this argument is 1 to 1024.

Usage guidelines

Before configuring this command, make sure the queue af command or the queue wfq command has been configured.

The undo queue af or undo queue wfq command deletes the queue length configured by using the queue-length command.

If you execute the queue-length command multiple times, the most recent configuration takes effect.

Examples

# Set the maximum queue length to 16 and specify tail drop for AF.

<Sysname> system-view

[Sysname] traffic behavior database

[Sysname-behavior-database] queue af bandwidth 200

[Sysname-behavior-database] queue-length 16

Related commands

queue af

queue wfq

wred

Use wred to enable WRED.

Use undo wred to restore the default.

Syntax

wred [ dscp | ip-precedence ]

undo wred

Default

WRED is disabled.

Views

Traffic behavior view

Predefined user roles

network-admin

context-admin

Parameters

dscp: Uses the DSCP value for calculating the drop probability for a packet.

ip-precedence: Uses the IP precedence value for calculating the drop probability for a packet. This is the default.

Usage guidelines

You can configure this command only after you have configured the queue af or queue wfq command.

This command and the queue-length command are mutually exclusive in a traffic behavior. After you configure one command, the other command cannot take effect.

The undo wred command also deletes other WRED settings.

Examples

# Enable WRED in traffic behavior database and calculate the drop probabilities based on IP precedence values.

<Sysname> system-view

[Sysname] traffic behavior database

[Sysname-behavior-database] queue wfq

[Sysname-behavior-database] wred

Related commands

queue af

queue wfq

wred dscp

Use wred dscp to set the lower limit, upper limit, and drop probability denominator for packets with a DSCP value.

Use undo wred dscp to delete the settings for a DSCP value.

Syntax

wred dscp dscp-value low-limit low-limit high-limit high-limit [ discard-probability discard-prob ]

undo wred dscp dscp-value

Default

The lower limit is 10, and the upper limit is 30.

Views

Traffic behavior view

Predefined user roles

network-admin

context-admin

Parameters

dscp-value: Specifies a DSCP value in the range of 0 to 63. This argument can also be represented by using one of the keywords listed in Table 5.

low-limit low-limit: Specifies the lower WRED limit (in packets) in the range of 1 to 1024.

high-limit high-limit: Specifies the upper WRED limit (in packets) in the range of 1 to 1024.

discard-probability discard-prob: Specifies the denominator for drop probability calculation, in the range of 1 to 255. The default is 10.

Usage guidelines

Before configuring this command, make sure DSCP-based WRED is enabled by using the wred command.

The wred dscp command configuration is deleted when the undo wred command is executed.

Removing the queue af or queue wfq command configuration also removes the WRED-related parameters.

Examples

# Set the following parameters for packets with DSCP value 3: lower limit 20, upper limit 40, and drop probability denominator 15.

<Sysname> system-view

[Sysname] traffic behavior database

[Sysname-behavior-database] queue wfq

[Sysname-behavior-database] wred dscp

[Sysname-behavior-database] wred dscp 3 low-limit 20 high-limit 40 discard-probability 15

Related commands

queue af

queue wfq

wred

wred ip-precedence

Use wred ip-precedence to set the lower limit, upper limit, and drop probability denominator for packets with an IP precedence value.

Use undo wred ip-precedence to delete the settings for an IP precedence value.

Syntax

wred ip-precedence precedence low-limit low-limit high-limit high-limit [ discard-probability discard-prob ]

undo wred ip-precedence precedence

Default

The lower limit is 10, and the upper limit is 30.

Views

Traffic behavior view

Predefined user roles

network-admin

context-admin

Parameters

precedence: Specifies an IP precedence value in the range of 0 to 7.

low-limit low-limit: Specifies the lower WRED limit (in packets) in the range of 1 to 1024.

high-limit high-limit: Specifies the upper WRED limit (in packets) in the range of 1 to 1024.

discard-probability discard-prob: Specifies the denominator for drop probability calculation, in the range of 1 to 255. The default is 10.

Usage guidelines

Before configuring this command, make sure IP precedence-based WRED is enabled by using the wred command.

The wred ip-precedence command configuration is deleted when the undo wred command is executed.

Removing the queue af or queue wfq command configuration also removes the WRED-related parameters.

Examples

# Configure the following parameters for packets with IP precedence value 3: lower limit 20, upper limit 40, and drop probability denominator 15.

<Sysname> system-view

[Sysname] traffic behavior database

[Sysname-behavior-database] queue wfq

[Sysname-behavior-database] wred ip-precedence

[Sysname-behavior-database] wred ip-precedence 3 low-limit 20 high-limit 40 discard-probability 15

Related commands

queue af

queue wfq

wred

wred weighting-constant

Use wred weighting-constant to set the exponent for WRED to calculate the average queue size.

Use undo wred weighting-constant to restore the default.

Syntax

wred weighting-constant exponent

undo wred weighting-constant

Default

The exponent for WRED to calculate the average queue size is 9.

Views

Traffic behavior view

Predefined user roles

network-admin

context-admin

Parameters

exponent: Specifies the exponent in the range of 1 to 16.

Usage guidelines

Before configuring this command, make sure the queue af or queue wfq command is configured and WRED is enabled by using the wred command.

The wred weighting-constant command configuration is deleted when the undo wred command is executed.

If you execute the wred weighting-constant command multiple times, the most recent configuration takes effect.

Examples

# Set the WRED exponent to calculate the average queue size to 6.

<Sysname> system-view

[Sysname] traffic behavior database

[Sysname-behavior-database] queue af bandwidth 200

[Sysname-behavior-database] wred ip-precedence

[Sysname-behavior-database] wred weighting-constant 6

Related commands

queue af

queue wfq

wred

13-ACL and QoS Command Reference

QoS policy commands

display traffic classifier

remark ip-precedence

remark qos-local-id

control-plane management

qos apply policy (interface view, control plane view, control-plane management view)

QoS policy-based traffic rate statistics collection period commands

display qos lr

wred dscp

Cloud & AI

InterConnect

Intelligent Terminal Products

Product Support Services

Technical Service Solutions

Resource Center

Policy

Online Help

Become a Partner

Partner Resources

Partner Business Management

Company Information

News & Events

Contact Us