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 the slot number of the device, which is fixed at 1.

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-

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 match-criteria

undo if-match match-criteria

Default

No match criterion is configured.

Views

Traffic class view

Predefined user roles

network-admin

Parameters

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. · 4000 to 4999 for Layer 2 MAC ACLs. · 5000 to 5999 for user-defined 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 both non-VPN packets and VPN packets.
any	Matches all packets.
control-plane protocol protocol-name&<1-8>	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, normal, or redirect.
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 subcard where the input interface resides is removed. After the removed subcard is reinserted, the traffic class takes effect again. If you do not reinsert the 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.
outbound-interface interface-type interface-number	Matches an output interface specified by its type and number. This option does not take effect on incoming Layer 3 packets.
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.
rocev2 { opcode opcode-value \| dst-qpair dst-qpair-value \| src-qpair src-qpair-value \| nack nack-value } *	Matches an RoCEv2 protocol: · opcode opcode-value: Matches the OpCode field in the BTH header. The opcode-value argument specifies an OpCode value in the range of 0 to 255. · dst-qpair dst-qpair-value: Matches the Destination QP field in the BTH header. The dst-qpair-value argument specifies a destination QP value in the range of 0 to 16777215. · src-qpair src-qpair-value: Matches the Source QP field in the DETH header. The src-qpair-value argument specifies a source QP value in the range of 0 to 16777215. · nack nack-value: Matches the lowest five bits in the Syndrome field in the NACK packets. The nack-value argument specifies a value for the lowest five bits in the Syndrome field, in the range of 0 to 31.
service-dot1p dot1p-value&<1-8>	Matches 802.1p priority values in outer VLAN tags. 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.
service-vlan-id vlan-id-list	Matches VLAN IDs in outer VLAN tags. 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. You can use this option to match single-tagged packets.
source-mac mac-address	Matches a source MAC address. This option takes effect only on Ethernet interfaces.
traffic-type { unicast \| unknown-unicast \| broadcast \| multicast }	Matches the packet type: · unicast—Matches unicast packets. · unknown-unicast—Matches unknown unicast packets. · broadcast—Matches broadcast packets. · multicast—Matches multicast packets. For a traffic class to match multiple packet types, you must specify the OR operator when creating the class.
tunnel-id tunnel-id	Matches a VXLAN tunnel ID. For the traffic class to take effect, the tunnel must be a VXLAN tunnel.
vxlan { any \| vxlan-id }	Matches a VXLAN ID.

Table 3 Available system-defined control plane protocols

Protocol	Description
arp	ARP packets
arp-snooping	ARP snooping packets
bfd	BFD packets
bgp	BGP packets
bgp4+	IPv6 BGP
dhcp	DHCP packets
dhcp-snooping	DHCP snooping packets
dhcp6	IPv6 DHCP packets
dldp	DLDP packets
dot1x	802.1p packets
drcp	DRCP packets.
https	HTTPS packets
http	HTTP packets
https	HTTPS packets
icmp	ICMP packets
icmpv6	ICMPv6 packets
igmp	IGMP packets
ip-option	IPv4 packets with the Options field
ipv6-option	IPv6 packets with the Options field
isis	IS-IS packets
lacp	LACP packets
lldp	LLDP packets
mvrp	MVRP packets (including GVRP packets)
nd	ND 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
snmp	SNMP packets
ssh	SSH packets
stp	STP packets
tacacs	TACACS packets
telnet	Telnet packets
ttl-expires	TTL expire 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:

¡ Control plane protocol.

¡ 802.1p priority.

¡ DSCP.

¡ IP precedence.

¡ VLAN ID.

· 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.

· When you define a match criterion to match the fields in RoCEv2 packets, because the opcode field values represent different RoCEv2 packet service types and only some types of RoCEv2 packets contain the src-qpair and nack fields, make sure their mappings are valid:

¡ If you specify both the opcode field and src-qpair field, the value for the opcode field must be 100 or 101, which specifies the UD service type. Otherwise, packets cannot be matched.

¡ If you specify both the opcode field and nack field, the value for the opcode field must be 17 (RC service) or 177 (XRC service). Otherwise, packets cannot be matched.

· The ACL is used for classification only and the permit/deny actions in ACL rules are ignored. Actions taken on matching packets are defined in traffic behaviors.

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

When the traffic class of a QoS policy matches a field without IPv4 or IPv6 characteristics, another traffic class of the QoS policy does not take effect in either of the following conditions:

· The traffic class matches an IPv4 address or IPv6 address, but is not configured with the if match protocol ip or if match protocol ipv6 command.

· The traffic class does not match an IPv4 or IPv6 address, but is configured with the if match protocol ip or if match protocol ipv6 command.

As a best practice, when a traffic class is configured to match a field without IPv4 or IPv6 characteristics, add the if match protocol ip or if match protocol ipv6 command to avoid this issue.

You can use a QoS policy to match and filter protocol packets by source or destination port (such as SSH, BGP, NTP, or LDP) sent to the control plane.

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 the packets with 802.1p priority 5 in the outer VLAN tag.

<Sysname> system-view

[Sysname] traffic classifier class1

[Sysname-classifier-class1] if-match service-dot1p 5

# 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 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 VLAN ID 2, 7, or 10 in the outer VLAN tag.

<Sysname> system-view

[Sysname] traffic classifier class1 operator or

[Sysname-classifier-class1] if-match service-vlan-id 2 7 10

# 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 ARP protocol packets.

<Sysname> system-view

[Sysname] traffic classifier class1

[Sysname-classifier-class1] if-match control-plane protocol arp

# Define a match criterion for traffic class class1 to match packets of the protocols in protocol group normal.

<Sysname> system-view

[Sysname] traffic classifier class1

[Sysname-classifier-class1] if-match control-plane protocol-group normal

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

<Sysname> system-view

[Sysname] traffic classifier class1

[Sysname-classifier-class1] if-match traffic-type multicast

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

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

Parameters

byte: Counts traffic in bytes.

packet: Counts traffic in packets.

Usage guidelines

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

If you do not specify the byte or packet keyword, the device collects statistics in packets. If you specify both the byte and packet keywords in one command line, the device collects statistics in both packets and bytes.

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 [ pps ] committed-information-rate [ cbs committed-burst-size [ ebs excess-burst-size ] ] [ green action | red action | yellow action ] *

car cir [ pps ] committed-information-rate [ cbs committed-burst-size ] pir [ pps ] 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

Parameters

cir committed-information-rate: Specifies the committed information rate (CIR) in the range of 8 to 4294967288 kbps or in the range of 1 to 160000000 pps. If you specify the pps keyword, the CIR is specified in pps. If you do not specify the pps keyword, the CIR is specified in kbps.

cbs committed-burst-size: Specifies the committed burst size (CBS). If you do not specify the pps keyword, the CBS is specified in bytes. If you specify the pps keyword, the CBS is specified in packets. The value range for committed-burst-size is 512 to 256000000, in increments of 512. The default value for this argument is the product of 62.5 and the CIR and must be an integral multiple of 512. When the product is not an integral multiple of 512, it is rounded up to the nearest integral multiple of 512 that is greater than the product. A default value greater than 256000000 is converted to 256000000.

ebs excess-burst-size: Specifies the excess burst size (EBS) in bytes. The value range for excess-burst-size is 0 to 256000000, in increments of 512. If the PIR is configured, the default EBS is the product of 62.5 and the PIR and must be an integral multiple of 512. When the product is not an integral multiple of 512, it is rounded up to the nearest integral multiple of 512. A default value greater than 256000000 is converted to 256000000.

pir peak-information-rate: Specifies the peak information rate (PIR) in the range of 8 to 4294967288 kbps, in increments of 8, or in the range of 1 to 160000000 pps. If you specify the pps keyword, the PIR is specified in pps. If you do not specify the pps keyword, the PIR is specified in 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-lp-pass new-local-precedence: Sets the local precedence value of the packet to new-local-precedence and permits the packet to pass through. The new-local-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 256 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 256 cbs 51200 ebs 0 green pass red remark-dscp-pass 0

display traffic behavior

Use display traffic behavior to display traffic behaviors.

Syntax

display traffic behavior user-defined [ behavior-name ] [ slot slot-number ]

Views

Any view

Predefined user roles

network-admin

network-operator

Parameters

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 the slot number of the device, which is fixed at 1.

Examples

# Display all user-defined traffic behaviors.

<Sysname> display traffic behavior user-defined

User-defined behavior information:

Behavior: 1 (ID 100)

Marking:

Remark dscp 3

Committed Access Rate:

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

Green action : pass

Yellow action : pass

Red action : discard

Behavior: 2 (ID 101)

Accounting enable: Packet

Filter enable: Permit

Redirecting:

Redirect to the CPU

Behavior: 3 (ID 102)

-none-

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.
Accounting enable	Class-based accounting action.
Filter enable	Traffic filtering action.
Redirecting	Information about traffic redirecting.
Mirroring	Information about traffic mirroring.
none	No other traffic behavior is configured.

‌

filter

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

Use undo filter to restore the default.

Syntax

filter { deny | none | permit }

undo filter

Default

No traffic filtering action is configured.

Views

Traffic behavior view

Predefined user roles

network-admin

Parameters

deny: Drops matching packets.

none: Permits matching packets. The matching packets are not processed by other class-behavior associations in the same QoS policy.

permit: Permits matching packets. The matching packets can also be processed by other class-behavior associations in the same QoS policy.

Examples

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

<Sysname> system-view

[Sysname] traffic behavior database

[Sysname-behavior-database] filter deny

mac-address mac-learning enable

Use mac-address mac-learning enable to enable MAC address learning for a traffic behavior.

Use undo mac-address mac-learning enable to disable MAC address learning for a traffic behavior.

Syntax

mac-address mac-learning enable

undo mac-address mac-learning enable

Default

MAC address learning is enabled for a traffic behavior.

Views

Traffic behavior view

Predefined user roles

network-admin

Usage guidelines

To prevent the MAC address table from being saturated when the device is experiencing attacks, disable MAC address learning. For example, you can disable MAC address learning to prevent the device from being attacked by a large number of frames with different source MAC addresses.

Disabling MAC address learning in a traffic behavior takes effect only if the QoS policy is applied to the inbound direction of an interface or globally.

Disabling MAC address learning has the following impacts:

· The device does not learn new MAC addresses of packets that match the QoS policy and therefore cannot update MAC address changes in real time.

· The device floods packets that do not match an entry in the MAC address table.

· The device does not delete existing MAC addresses until the aging timer expires. To delete the existing MAC addresses, delete them manually or wait for the aging timer to expire.

Examples

# Disable MAC address learning in traffic behavior data.

<Sysname> system-view

[Sysname] traffic behavior data

[Sysname-behavior-data] undo mac-address mac-learning enable

nest top-most

Use nest top-most to configure an outer VLAN tag adding action in a traffic behavior.

Use undo nest top-most to restore the default.

Syntax

nest top-most vlan vlan-id

undo nest top-most

Default

No outer VLAN tag adding action is configured.

Views

Traffic behavior view

Predefined user roles

network-admin

Parameters

vlan-id vlan-id: Specifies the VLAN ID to be added in the outer VLAN tag, in the range of 1 to 4094.

Usage guidelines

If a QoS policy contains an outer VLAN tag adding action, apply it only to the incoming traffic of an interface.

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

Examples

# Configure traffic behavior b1 to add an outer VLAN tag with VLAN ID 123.

<Sysname> system-view

[Sysname] traffic behavior b1

[Sysname-behavior-b1] nest top-most vlan 123

redirect

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

Use undo redirect to restore the default.

Syntax

redirect { cpu | interface interface-type interface-number }

undo redirect { cpu | interface interface-type interface-number }

Default

No traffic redirecting action is configured.

Views

Traffic behavior view

Predefined user roles

network-admin

Parameters

cpu: Redirects traffic to the CPU.

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.

The action of redirecting traffic to an interface takes effect only on Layer 2 packets.

Examples

# Configure redirecting traffic to HundredGigE 1/1/1 in traffic behavior database.

<Sysname> system-view

[Sysname] traffic behavior database

[Sysname-behavior-database] redirect interface hundredgige 1/1/1

Related commands

classifier behavior

qos policy

traffic behavior

remark customer-vlan-id

Use remark customer-vlan-id to configure a CVLAN marking action in a traffic behavior.

Use undo remark customer-vlan-id to restore the default.

Syntax

remark customer-vlan-id vlan-id

undo remark customer-vlan-id

Default

No CVLAN marking action is configured.

Views

Traffic behavior view

Predefined user roles

network-admin

Parameters

vlan-id: Specifies a CVLAN ID in the range of 1 to 4094.

Examples

# Configure traffic behavior b1 to mark matching packets with CVLAN 111.

<Sysname> system-view

[Sysname] traffic behavior b1

[Sysname-behavior-b1] remark customer-vlan-id 111

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 [ green | red | yellow ] dot1p dot1p-value

undo remark [ green | red | yellow ] dot1p

remark dot1p customer-dot1p-trust

undo remark dot1p

Default

No 802.1p priority marking action or inner-to-outer tag priority copying action is configured.

Views

Traffic behavior view

Predefined user roles

network-admin

Parameters

green: Specifies green packets.

red: Specifies red packets.

yellow: Specifies yellow packets.

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

customer-dot1p-trust: Copies the 802.1p priority value in the inner VLAN tag to the outer VLAN tag.

Usage guidelines

The remark dot1p dot1p-value and remark dot1p customer-dot1p-trust commands override each other in the same traffic behavior. The remark dot1p customer-dot1p-trust command does not take effect on single-tagged packets.

If you execute the remark dot1p dot1p-value command multiple times for the same color, the most recent configuration takes effect.

If you do not specify a color, packets of all colors are marked.

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

# Configure an inner-to-outer tag priority copying action in traffic behavior database.

<Sysname> system-view

[Sysname] traffic behavior database

[Sysname-behavior-database] remark dot1p customer-dot1p-trust

remark drop-precedence

Use remark drop-precedence to configure a drop priority marking action in a traffic behavior.

Use undo remark drop-precedence to restore the default.

Syntax

remark drop-precedence drop-precedence-value

undo remark drop-precedence

Default

No drop priority marking action is configured.

Views

Traffic behavior view

Predefined user roles

network-admin

Parameters

drop-precedence-value: Specifies the drop priority to be marked for packets, in the range of 0 to 2.

Usage guidelines

A drop priority marking action takes effect only when the QoS policy is applied to the inbound direction.

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

Examples

# Configure traffic behavior database to mark matching traffic with drop priority 2.

<Sysname> system-view

[Sysname] traffic behavior database

[Sysname-behavior-database] remark drop-precedence 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 [ green | red | yellow ] dscp dscp-value

undo remark [ green | red | yellow ] dscp

Default

No DSCP marking action is configured.

Views

Traffic behavior view

Predefined user roles

network-admin

Parameters

green: Specifies green packets.

red: Specifies red packets.

yellow: Specifies yellow packets.

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

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

Parameters

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

Examples

# Set the IP precedence to 6 for packets.

<Sysname> system-view

[Sysname] traffic behavior database

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

remark local-precedence

Use remark local-precedence to configure a local precedence marking action in a traffic behavior.

Use undo remark local-precedence to restore the default.

Syntax

remark [ green | red | yellow ] local-precedence local-precedence-value

undo remark [ green | red | yellow ] local-precedence

Default

No local precedence marking action is configured.

Views

Traffic behavior view

Predefined user roles

network-admin

Parameters

green: Specifies green packets.

red: Specifies red packets.

yellow: Specifies yellow packets.

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

Usage guidelines

A local precedence marking action takes effect only when the QoS policy is applied to the inbound direction.

Examples

# Configure traffic behavior database to mark matching traffic with local precedence 2.

<Sysname> system-view

[Sysname] traffic behavior database

[Sysname-behavior-database] remark local-precedence 2

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 [ egress-active ] local-id-value

undo remark qos-local-id [ egress-active ]

Default

No local QoS ID marking action is configured.

Views

Traffic behavior view

Predefined user roles

network-admin

Parameters

egress-active: Specifies that the local QoS ID marking action takes effect only in the outbound direction.

local-id-value: Specifies the local QoS ID to be marked for packets, in the range of 1 to 4095. If the egress-active keyword is specified, the value range is 1 to 128.

Usage guidelines

A local QoS ID marking action applied to the inbound direction takes effect only in the inbound direction. For such a local QoS ID marking action to also take effect only in the outbound direction, specify the egress-active keyword.

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

If MAC authentication is configured, the local QoS ID must be smaller than 3000. For more information about MAC authentication, see Security Configuration Guide.

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

remark service-vlan-id

Use remark service-vlan-id to configure an SVLAN marking action in a traffic behavior.

Use undo remark service-vlan-id to restore the default.

Syntax

remark service-vlan-id vlan-id

undo remark service-vlan-id

Default

No SVLAN marking action is configured.

Views

Traffic behavior view

Predefined user roles

network-admin

Parameters

vlan-id: Specifies an SVLAN ID in the range of 1 to 4094.

Examples

# Configure traffic behavior b1 to mark matching packets with SVLAN 222.

<Sysname> system-view

[Sysname] traffic behavior b1

[Sysname-behavior-b1] remark service-vlan-id 222

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

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

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 { dcbx | loose | qppb-manipulation } | 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

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 dcbx: Specifies that the class-behavior association applies only to the DCBX. For more information about DCBX, see Layer 2—LAN Switching Configuration Guide.

mode loose: Specifies that a class-behavior association is in loose mode. This mode takes effect only when a QoS policy is applied to a control plane.

mode qppb-manipulation: Specifies that the class-behavior association applies only to QPPB. The if-match qos-local-id command in the class sets the same local QoS ID as the apply qos-local-id command in the BGP routing policy. For more information about routing policies, see Layer 3—IP Routing Configuration Guide.

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.

The loose mode can match all packets sent to the control plane, including those packets that cannot be identified, such as ARP packets.

IMPORTANT:

Use the loose mode with caution, because it might mistakenly match protocol packets.

The mode loose keyword allows you to limit the rate of all protocol packets from a specific interface to the control plane. The configuration procedure is as follows:

1. Create an ACL, and configure a rule to match protocol packets.

2. Create a traffic class with AND operator, and execute the commands in the if-match acl and if-match inbound-interface traffic class.

3. Create a traffic behavior, configure an action.

4. Create a QoS policy, and associate the traffic class and the traffic behavior and specify the mode loose keyword.

5. Apply the QoS policy to a control plane.

The applied QoS policy takes effect on only the protocol packets from the interface specified in the if-match inbound-interface command to the control plane.

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 specify that the class-behavior association applies only to QPPB.

<Sysname> system-view

[Sysname] qos policy user1

[Sysname-qospolicy-user1] classifier database behavior test mode qppb-manipulation

# 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

control-plane slot slot-number

Views

System view

Predefined user roles

network-admin

Parameters

slot slot-number: Specifies the slot number of the device, which is fixed at 1.

Examples

# Enter the control plane view of slot 1.

<Sysname> system-view

[Sysname] control-plane slot 1

[Sysname-cp-slot1]

display qos policy

Use display qos policy to display QoS policies.

Syntax

display qos policy user-defined [ ipv6-matching | accounting | mirroring | remarking ] [ policy-name [ classifier classifier-name ] ] [ slot slot-number ]

Views

Any view

Predefined user roles

network-admin

network-operator

Parameters

user-defined: Specifies user-defined QoS policies.

ipv6-matching: Specifies IPv6-matching QoS policies.

accounting: Specifies accounting-type QoS policies.

mirroring: Specifies mirroring-type QoS policies.

remarking: Specifies marking-type 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 the slot number of the device, which is fixed at 1.

Usage guidelines

If you do not specify the ipv6-matching, accounting, mirroring, or remarking keyword, this command displays generic QoS policies.

Examples

# Display all user-defined generic 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-

# Display user-defined accounting-type QoS policies.

<Sysname> display qos policy user-defined accounting

User-defined QoS policy information:

Accounting policy: 1 (ID 100)

Classifier: 1 (ID 100)

Behavior: 1

Accounting enable: Packet

# Display user-defined mirroring-type QoS policies.

<Sysname> display qos policy user-defined mirroring

User-defined QoS policy information:

Mirroring policy: 1 (ID 100)

Classifier: 1 (ID 100)

Behavior: 1

Mirroring:

Mirror to the CPU

# Display user-defined marking-type QoS policies.

<Sysname> display qos policy user-defined remarking

User-defined QoS policy information:

Marking policy: 1 (ID 100)

Classifier: 1 (ID 100)

Behavior: 1

Marking:

Remark dscp 3

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.
IPv6 Matching policy	User-defined IPv6-matching QoS policy name.
Accounting policy	User-defined accounting-type QoS policy name.
Mirroring policy	User-defined mirroring-type QoS policy name.
Marking policy	User-defined marking-type QoS policy name.

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

display qos policy control-plane slot slot-number

Views

Any view

Predefined user roles

network-admin

network-operator

Parameters

slot slot-number: Specifies the slot number of the device, which is fixed at 1.

Examples

# 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.

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

display qos policy control-plane pre-defined

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

Syntax

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

Views

Any view

Predefined user roles

network-admin

network-operator

Parameters

slot slot-number: Specifies the slot number of the device, which is fixed at 1.

Examples

# 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 Group

Default N/A 3000 (pps) N/A

IS-IS 20 2000 (pps) critical

VRRP 19 2000 (pps) important

OSPF Multicast 18 2000 (pps) critical

OSPF Unicast 18 2000 (pps) critical

PIM Multicast 12 1000 (pps) critical

PIM Unicast 12 1000 (pps) critical

IGMP 11 1500 (pps) important

PIMv6 Multicast 12 600 (pps) critical

PIMv6 Unicast 12 600 (pps) critical

OSPFv3 Unicast 18 2000 (pps) critical

OSPFv3 Multicast 18 2000 (pps) critical

VRRPv6 19 2000 (pps) important

ARP 2 3000 (pps) normal

DHCP Snooping 10 600 (pps) redirect

DHCP 10 600 (pps) normal

802.1x 3 1000 (pps) important

STP 17 600 (pps) critical

LACP 22 600 (pps) critical

MVRP 15 600 (pps) critical

BGP 16 4000 (pps) critical

ICMP 3 1000 (pps) monitor

TTL Expires 4 600 (pps) monitor

IPOPTION 4 600 (pps) normal

BGPv6 16 3000 (pps) critical

ND 2 3000 (pps) critical

Hop Limit Expires 4 600 (pps) monitor

IPOPTIONv6 4 600 (pps) normal

LLDP 14 600 (pps) important

DLDP 16 600 (pps) critical

TELNET 1 1600 (pps) management

SSH 1 1600 (pps) management

TACACS 1 1600 (pps) management

RADIUS 1 1600 (pps) management

SNMP 4 1600 (pps) management

ARP Snooping 2 3000 (pps) redirect

ICMPv6 3 600 (pps) monitor

DHCPv6 10 600 (pps) normal

BFD 21 3500 (pps) critical

DRCP 12 400 (pps) critical

Table 8 Command output

Field	Description
Pre-defined control plane policy	Contents of the predefined control plane QoS policy.
Default	Protocols other than those listed.
Group	Protocol group of the protocol.

For descriptions of other fields, see Table 3.

display qos policy diagnosis control-plane

Use display qos policy diagnosis control-plane to display diagnostic information about QoS policies applied to a control plane.

Syntax

display qos policy diagnosis control-plane slot slot-number

Views

Any view

Predefined user roles

network-admin

network-operator

Parameters

slot slot-number: Specifies the slot number of the device, which is fixed at 1.

Examples

# Display diagnostic information about the QoS policy applied to the control plane of slot 2.

<Sysname> display qos policy diagnosis control-plane slot 2

Control plane slot 2

Direction: Inbound

Policy: 1

Classifier: 1 (Incomplete)

Operator: AND

Rule(s) :

If-match acl 2000 (Incomplete)

Failed Rule ID: 0, 3, 5, 50

Behavior: 1

Marking:

Remark dscp 3

Committed Access Rate:

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

Green action : pass

Yellow action : pass

Red action : discard

Classifier: 2

Operator: AND

Rule(s) :

If-match not protocol ipv6

Behavior: 2

Accounting enable:

Filter enable: Permit

Marking:

Remark dscp 4

Classifier: 3

Operator: AND

Rule(s) :

-none-

Behavior: 3

-none-

Table 9 Command output

Field	Description
Direction	Direction in which the QoS policy is applied.
Classifier: 1 (Incomplete)	Traffic class application result: · Incomplete—Some contents of the traffic class were applied successfully. · Failed—All contents of the traffic class failed to be applied.
If-match acl 2000 (Incomplete)	Match criterion application result: · Incomplete—Some contents of the match criterion were applied successfully. · Failed—All contents of the match criterion failed to be applied.
Failed rule ID	ACL rules that failed to be applied.

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

display qos policy diagnosis global

Use display qos policy diagnosis global to display diagnostic information about QoS policies applied globally.

Syntax

display qos [ ipv6-matching | accounting | mirroring | remarking ] policy diagnosis global [ slot slot-number ] [ inbound | outbound ]

Views

Any view

Predefined user roles

network-admin

network-operator

Parameters

ipv6-matching: Specifies IPv6-matching QoS policies.

accounting: Specifies accounting-type QoS policies.

mirroring: Specifies mirroring-type QoS policies.

remarking: Specifies marking-type QoS policies.

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

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

slot slot-number: Specifies the slot number of the device, which is fixed at 1.

Usage guidelines

If you do not specify the ipv6-matching, accounting, mirroring, or remarking keyword, this command displays diagnostic information about generic QoS policies.

If you do not specify a direction, this command displays diagnostic information about both QoS policies.

Examples

# Display diagnostic information about generic QoS policies applied globally.

<Sysname> display qos policy diagnosis global

Direction: Inbound

Policy: 1

Classifier: 1 (Incomplete)

Operator: AND

Rule(s) :

If-match acl 2000 (Incomplete)

Failed Rule ID: 0, 3, 5, 50

Behavior: 1

Marking:

Remark dscp 3

Committed Access Rate:

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

Green action : pass

Yellow action : pass

Red action : discard

Classifier: 2

Operator: AND

Rule(s) :

If-match not protocol ipv6

Behavior: 2

Accounting enable:

Filter enable: Permit

Marking:

Remark dscp 4

Classifier: 3

Operator: AND

Rule(s) :

-none-

Behavior: 3

-none-

# Display diagnostic information about accounting-type QoS policies applied globally.

<Sysname> display qos accounting policy diagnosis global

Direction: Inbound

Accounting policy: 1

Classifier: 1

Operator: AND

Rule(s) :

If-match protocol ipv4

Behavior: 1

Accounting enable: Packet

# Display diagnostic information about mirroring-type QoS policies applied globally.

<Sysname> display qos mirroring policy diagnosis global

Direction: Inbound

Mirroring policy: 1

Classifier: 1

Operator: AND

Rule(s) :

If-match protocol ipv4

Behavior: 1

Mirroring:

Mirror to the CPU

# Display diagnostic information about marking-type QoS policies applied globally.

<Sysname> display qos remarking policy diagnosis global

Direction: Inbound

Marking policy: 1

Classifier: 1

Operator: AND

Rule(s) :

If-match protocol ipv4

Behavior: 1

Marking:

Remark dscp 3

Table 10 Command output

Field	Description
Direction	Direction in which the QoS policy is applied.
Policy	User-defined generic QoS policy name.
IPv6 Matching policy	User-defined IPv6-matching QoS policy name.
Accounting policy	User-defined accounting-type QoS policy name.
Mirroring policy	User-defined mirroring-type QoS policy name.
Marking policy	User-defined marking-type QoS policy name.
Classifier: 1 (Incomplete)	Traffic class application result: · Incomplete—Some contents of the traffic class were applied successfully. · Failed—All contents of the traffic class failed to be applied.
If-match acl 2000 (Incomplete)	Match criterion application result: · Incomplete—Some contents of the match criterion were applied successfully. · Failed—All contents of the match criterion failed to be applied.
Failed rule ID	ACL rules that failed to be applied.

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

display qos policy diagnosis interface

Use display qos policy diagnosis interface to display diagnostic information about the QoS policies applied to interfaces.

Syntax

display qos [ ipv6-matching | accounting | mirroring | remarking ] policy diagnosis interface [ interface-type interface-number ] [ slot slot-number ] [ inbound | outbound ]

Views

Any view

Predefined user roles

network-admin

network-operator

Parameters

ipv6-matching: Specifies IPv6-matching QoS policies.

accounting: Specifies accounting-type QoS policies.

mirroring: Specifies mirroring-type QoS policies.

remarking: Specifies marking-type QoS policies.

interface-type interface-number: Specifies an interface by its type and number.

slot slot-number: Specifies the slot number of the device, which is fixed at 1.

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 the ipv6-matching, accounting, mirroring, or remarking keyword, this command displays diagnostic information about generic QoS policies.

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

Examples

# Display diagnostic information about the generic QoS policy applied to the incoming traffic of HundredGigE 1/1/1.

<Sysname> display qos policy diagnosis interface hundredgige 1/1/1 inbound

Interface: HundredGigE1/1/1

Direction: Inbound

Policy: 1

Classifier: 1 (Incomplete)

Operator: AND

Rule(s) :

If-match acl 2000 (Incomplete)

Failed Rule ID: 0, 3, 5, 50

Behavior: 1

Marking:

Remark dscp 3

Committed Access Rate:

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

Green action : pass

Yellow action : pass

Red action : discard

Classifier: 2

Operator: AND

Rule(s) :

If-match not protocol ipv6

Behavior: 2

Filter enable: Permit

Marking:

Remark dscp 4

Classifier: 3

Operator: AND

Rule(s) :

-none-

Behavior: 3

-none-

# Display diagnostic information about the accounting-type QoS policy applied to the incoming traffic of HundredGigE 1/1/1.

<Sysname> display qos accounting policy diagnosis interface hundredgige 1/1/1 inbound

Interface: HundredGigE1/1/1

Direction: Inbound

Accounting policy: 1

Classifier: 1 (Incomplete)

Operator: AND

Rule(s) :

If-match acl 2000 (Incomplete)

Failed Rule ID: 0, 3, 5, 50

Behavior: 1

Accounting enable: Packet

# Display diagnostic information about the mirroring-type QoS policy applied to the incoming traffic of HundredGigE 1/1/1.

<Sysname> display qos mirroring policy diagnosis interface hundredgige 1/1/1 inbound

Interface: HundredGigE1/1/1

Direction: Inbound

Mirroring policy: 1

Classifier: 1 (Incomplete)

Operator: AND

Rule(s) :

If-match acl 2000 (Incomplete)

Failed Rule ID: 0, 3, 5, 50

Behavior: 1

Mirroring:

Mirror to the CPU

# Display diagnostic information about the marking-type QoS policy applied to the incoming traffic of HundredGigE 1/1/1.

<Sysname> display qos remarking policy diagnosis interface hundredgige 1/1/1 inbound

Interface: HundredGigE1/1/1

Direction: Inbound

Marking policy: 1

Classifier: 1 (Incomplete)

Operator: AND

Rule(s) :

If-match acl 2000 (Incomplete)

Failed Rule ID: 0, 3, 5, 50

Behavior: 1

Marking:

Remark dscp 3

Table 11 Command output

Field	Description
Direction	Direction in which the QoS policy is applied.
Policy	User-defined generic QoS policy name.
IPv6 Matching policy	User-defined IPv6-matching QoS policy name.
Accounting policy	User-defined accounting-type QoS policy name.
Mirroring policy	User-defined mirroring-type QoS policy name.
Marking policy	User-defined marking-type QoS policy name.
Classifier: 1 (Incomplete)	Traffic class application result: · Incomplete—Some contents of the traffic class were applied successfully. · Failed—All contents of the traffic class failed to be applied.
If-match acl 2000 (Incomplete)	Match criterion application result: · Incomplete—Some contents of the match criterion were applied successfully. · Failed—All contents of the match criterion failed to be applied.
Failed rule ID	ACL rules that failed to be applied.

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

display qos policy diagnosis user-profile

Use display qos policy diagnosis user-profile to display diagnostic information about QoS policies applied to user profiles.

Syntax

display qos policy diagnosis user-profile [ name profile-name ] [ user-id user-id ] [ slot slot-number ] [ inbound | outbound ]

Views

Any view

Predefined user roles

network-admin

network-operator

Parameters

name profile-name: Specifies a user profile by its name, a case-sensitive string of 1 to 31 characters. Valid characters include English letters, digits, and underscores (_). The name must start with an English letter and must be unique. If you do not specify a user profile, this command displays diagnostic information about QoS policies applied to all user profiles.

user-id user-id: Specifies an online user by a system-assigned, hexadecimal ID in the range of 0 to fffffffe. If you do not specify an online user, this command displays diagnostic information about QoS policies applied to user profiles for all online users.

slot slot-number: Specifies the slot number of the device, which is fixed at 1.

inbound: Specifies QoS policies applied to incoming traffic.

outbound: Specifies QoS policies applied to outgoing traffic.

Usage guidelines

If you do not specify a direction, this command displays diagnostic information about QoS policies applied in the inbound direction and QoS policies applied in the outbound direction.

Examples

# Display diagnostic information about the QoS policy applied to user profile abc for a global user.

<Sysname> display qos policy user-profile name abc user-id 30000000 inbound

User-Profile: abc

User ID: 0x30000000(global)

Direction: Inbound

Policy: 1

Classifier: 1 (Incomplete)

Operator: AND

Rule(s) :

If-match acl 2000 (Incomplete)

Failed Rule ID: 0, 3, 5, 50

Behavior: 1

Marking:

Remark dscp 3

Committed Access Rate:

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

Green action : pass

Yellow action : pass

Red action : discard

Classifier: 2

Operator: AND

Rule(s) :

If-match not protocol ipv6

Behavior: 2

Filter enable: Permit

Marking:

Remark dscp 4

Classifier: 3

Operator: AND

Rule(s) :

-none-

Behavior: 3

-none-

Table 12 Command output

Field	Description
Direction	Direction in which the QoS policy is applied.
Classifier: 1 (Incomplete)	Traffic class application result: · Incomplete—Some contents of the traffic class were applied successfully. · Failed—All contents of the traffic class failed to be applied.
If-match acl 2000 (Incomplete)	Match criterion application result: · Incomplete—Some contents of the match criterion were applied successfully. · Failed—All contents of the match criterion failed to be applied.
Failed rule ID	ACL rules that failed to be applied.

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

display qos policy global

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

Syntax

display qos [ ipv6-matching | accounting | mirroring | remarking ] policy global [ slot slot-number ] [ inbound | outbound ]

Views

Any view

Predefined user roles

network-admin

network-operator

Parameters

ipv6-matching: Specifies IPv6-matching QoS policies.

accounting: Specifies accounting-type QoS policies.

mirroring: Specifies mirroring-type QoS policies.

remarking: Specifies marking-type QoS policies.

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

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

slot slot-number: Specifies the slot number of the device, which is fixed at 1.

Usage guidelines

If you do not specify the ipv6-matching, accounting, mirroring, or remarking keyword, this command displays information about generic QoS policies.

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

Examples

# Display generic 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-

# Display information about accounting-type QoS policies applied globally.

<Sysname> display qos accounting policy global

Direction: Inbound

Accounting policy: 1

Classifier: 1

Operator: AND

Rule(s) :

If-match acl 2000

Behavior: 1

Accounting enable: Packet

# Display information about mirroring-type QoS policies applied globally.

<Sysname> display qos mirroring policy global

Direction: Inbound

Mirroring policy: 1

Classifier: 1

Operator: AND

Rule(s) :

If-match acl 2000

Behavior: 1

Mirroring:

Mirror to the CPU

# Display information about marking-type QoS policies applied globally.

<Sysname> display qos remarking policy global

Direction: Inbound

Marking policy: 1

Classifier: 1

Operator: AND

Rule(s) :

If-match acl 2000

Behavior: 1

Marking:

Remark dscp 3

# Display information about IPv6-matching QoS policies applied globally.

<Sysname> display qos ipv6-matching policy global

Direction: Inbound

IPv6 Matching policy: 1

Classifier: 1

Operator: AND

Rule(s) :

If-match acl ipv6 3000

Behavior: 1

Marking:

Remark dscp 3

Table 13 Command output

Field	Description
Direction	Direction in which the QoS policy is applied.
Policy	User-defined generic QoS policy name.
IPv6 Matching policy	User-defined IPv6-matching QoS policy name.
Accounting policy	User-defined accounting-type QoS policy name.
Mirroring policy	User-defined mirroring-type QoS policy name.
Marking policy	User-defined marking-type QoS policy name.
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

display qos [ ipv6-matching | accounting | mirroring | remarking ] policy interface [ interface-type interface-number ] [ slot slot-number ] [ inbound | outbound ]

Views

Any view

Predefined user roles

network-admin

network-operator

Parameters

ipv6-matching: Specifies IPv6-matching QoS policies.

accounting: Specifies accounting-type QoS policies.

mirroring: Specifies mirroring-type QoS policies.

remarking: Specifies marking-type QoS policies.

interface-type interface-number: Specifies an interface by its type and number.

slot slot-number: Specifies the slot number of the device, which is fixed at 1.

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 the ipv6-matching, accounting, mirroring, or remarking keyword, this command displays generic QoS policies applied.

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.

Examples

# Display the generic QoS policy applied to the incoming traffic of HundredGigE 1/1/1.

<Sysname> display qos policy interface hundredgige 1/1/1 inbound

Interface: HundredGigE1/1/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)

Filter enable: Permit

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-

# Display information about the accounting-type QoS policy applied to the incoming traffic of HundredGigE 1/1/1.

<Sysname> display qos accounting policy interface hundredgige 1/1/1 inbound

Interface: HundredGigE1/1/1

Direction: Inbound

Accounting Policy: 1

Classifier: 1

Operator: AND

Rule(s) :

If-match acl 2000

Behavior: 1

Accounting enable:

0 (Packets)

# Display information about the marking-type QoS policy applied to the incoming traffic of HundredGigE 1/1/1.

<Sysname> display qos remarking policy interface hundredgige 1/1/1 inbound

Interface: HundredGigE1/1/1

Direction: Inbound

Marking policy: 1

Classifier: 1

Operator: AND

Rule(s) :

If-match acl 2000

Behavior: 1

Marking:

Remark dscp 3

# Display information about the mirroring-type QoS policy applied to the incoming traffic of HundredGigE 1/1/1.

<Sysname> display qos mirroring policy interface hundredgige 1/1/1 inbound

Interface: HundredGigE1/1/1

Direction: Inbound

Mirroring policy: 1

Classifier: 1

Operator: AND

Rule(s) :

If-match acl 2000

Behavior: 1

Mirroring:

Mirror to the CPU

# Display the generic QoS policies applied to all interfaces.

<Sysname> display qos policy interface

Interface: HundredGigE1/1/1

Direction: Inbound

Policy: a

Classifier: a

Operator: AND

Rule(s) :

If-match any

Behavior: a

Mirroring:

Mirror to the interface: HundredGigE1/1/2

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: HundredGigE1/1/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: HundredGigE1/1/4

Direction: Inbound

Policy: a

Classifier: a

Operator: AND

Rule(s) :

If-match any

Behavior: a

Mirroring:

Mirror to the interface: HundredGigE1/1/5

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 14 Command output

Field	Description
Direction	Direction in which the QoS policy is applied.
IPv6 Matching policy	User-defined IPv6-matching QoS policy name.
Accounting policy	User-defined accounting-type QoS policy name.
Mirroring policy	User-defined mirroring-type QoS policy name.
Marking policy	User-defined marking-type QoS policy name.
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.

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

display qos policy user-profile

Use display qos policy user-profile to display QoS policies applied to user profiles.

Syntax

display qos policy user-profile [ name profile-name ] [ user-id user-id ] [ slot slot-number ] [ inbound | outbound ]

Views

Any view

Predefined user roles

network-admin

network-operator

Parameters

user-id user-id: Specifies an online user by a system-assigned, hexadecimal ID in the range of 0 to fffffffe. If you do not specify an online user, this command displays QoS policies applied to user profiles for all online users.

slot slot-number: Specifies the slot number of the device, which is fixed at 1.

inbound: Specifies QoS policies applied to incoming traffic.

outbound: Specifies QoS policies applied to outgoing traffic.

Usage guidelines

If you do not specify a direction, this command displays QoS policies applied in the inbound direction and QoS policies applied in the outbound direction.

Examples

# Display the QoS policy applied to user profile abc for a global user.

<Sysname> display qos policy user-profile name abc user-id 30000000 inbound

User-Profile: abc

User ID: 0x30000000(global)

Direction: Inbound

Policy: p1

Classifier: default-class

Matched : 0 (Packets) 0 (Bytes)

Operator: AND

Rule(s) :

If-match any

Behavior: be

-none-

# Display the QoS policy applied to user profile abc for a local user.

<Sysname> display qos policy user-profile name abc user-id 30000001 inbound

User-Profile: abc

slot 2:

User ID: 0x30000001(local)

Direction: Inbound

Policy: p1

Classifier: default-class

Matched : 0 (Packets) 0 (Bytes)

Operator: AND

Rule(s) :

If-match any

Behavior: be

-none-

Table 15 Command output

Field	Description
global	Indicates a global user, who comes online from a global interface such as an aggregate interface.
local	Indicates a local user, who comes online from a physical interface.
Matched	Number of packets that meet match criteria.
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 vlan-policy

Use display qos vlan-policy to display QoS policies applied to VLANs.

Syntax

display qos vlan-policy { name policy-name | vlan [ vlan-id ] } [ slot slot-number ] [ inbound | outbound ]

Views

Any view

Predefined user roles

network-admin

network-operator

Parameters

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

vlan vlan-id: Specifies a VLAN by its ID in the range of 1 to 4094.

inbound: Displays QoS policies applied to incoming traffic.

outbound: Displays QoS policies applied to outgoing traffic.

slot slot-number: Specifies the slot number of the device, which is fixed at 1.

Usage guidelines

If you do not specify a direction, this command displays QoS policies applied to VLANs in both the inbound and outbound directions.

Examples

# Display QoS policies applied to VLAN 2.

<Sysname> display qos vlan-policy vlan 2

Vlan 2

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 5120 (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 16 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 vlan-policy diagnosis

Use display qos vlan-policy diagnosis to display diagnostic information about QoS policies applied to VLANs.

Syntax

display qos vlan-policy diagnosis vlan [ vlan-id ] [ slot slot-number ] [ inbound | outbound ]

Views

Any view

Predefined user roles

network-admin

network-operator

Parameters

vlan vlan-id: Specifies a VLAN by its ID in the range of 1 to 4094.

inbound: Specifies QoS policies applied to incoming traffic.

outbound: Specifies QoS policies applied to outgoing traffic.

slot slot-number: Specifies the slot number of the device, which is fixed at 1.

Usage guidelines

If you do not specify a direction, this command displays diagnostic information about QoS policies applied to VLANs in both the inbound and outbound directions.

Examples

# Display diagnostic information about QoS policies applied to VLAN 2.

<Sysname> display qos vlan-policy diagnosis vlan 2

Vlan 2

Direction: Outbound

Type : Extension

Policy: 1

Classifier: 1 (Incomplete)

Operator: AND

Rule(s) :

If-match acl 2000 (Incomplete)

Failed Rule ID: 0, 3, 5, 50

Behavior: 1

Marking:

Remark dscp 3

Committed Access Rate:

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

Green action : pass

Yellow action : pass

Red action : discard

Classifier: 2

Operator: AND

Rule(s) :

If-match not protocol ipv6

Behavior: 2

Accounting enable:

Filter enable: Permit

Marking:

Remark dscp 4

Classifier: 3

Operator: AND

Rule(s) :

-none-

Behavior: 3

-none-

Table 17 Command output

Field	Description
Direction	Direction in which the QoS policy is applied.
Classifier: 1 (Incomplete)	Traffic class application result: · Incomplete—Some contents of the traffic class were applied successfully. · Failed—All contents of the traffic class failed to be applied.
If-match acl 2000 (Incomplete)	Match criterion application result: · Incomplete—Some contents of the match criterion were applied successfully. · Failed—All contents of the match criterion failed to be applied.
Failed rule ID	ACL rules that failed to be applied.

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

qos apply policy (interface view, control plane view)

Use qos apply policy to apply a QoS policy to an interface or control plane.

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

Syntax

qos apply [ ipv6-matching | accounting | mirroring | remarking ] policy policy-name { inbound | outbound } [ longest-match | share-mode ] *

undo qos apply [ ipv6-matching | accounting | mirroring | remarking ] policy policy-name { inbound | outbound }

Default

No QoS policy is applied.

Views

Control plane view

Interface view

Predefined user roles

network-admin

Parameters

ipv6-matching: Specifies an IPv6-matching QoS policy. This keyword is supported only in interface view.

accounting: Specifies an accounting-type QoS policy. This keyword is supported only in interface view.

mirroring: Specifies a mirroring-type QoS policy. This keyword is supported only in interface view.

remarking: Specifies a marking-type QoS policy. This keyword is supported only in interface view.

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. This keyword is not supported in the outbound direction of control plane view.

longest-match: First matches the traffic class with a source or destination IP address with the longest mask and takes the actions in the associated traffic behavior if a match is found.

share-mode: Applies the QoS policy in sharing mode to a Layer 2 or Layer 3 Ethernet interface. In this mode, all interfaces with the same QoS policy applied in one direction share one QoS and ACL resource.

Usage guidelines

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.

If you specify the share-mode keyword when applying a QoS policy to an interface, follow these restrictions and guidelines:

· All interfaces with the QoS policy applied in one direction share one QoS and ACL resource.

If the share-mode keyword is not specified, each interface uses one QoS and ACL resource in one direction.

· All interfaces that share one QoS and ACL resource evenly share the set CIR if a traffic policing action is configured in the QoS policy.

If the share-mode keyword is not specified, the bandwidth of each interface can be limited to the CIR.

· You cannot specify the share-mode keyword when applying an ACL to the same direction of the interface. For more information about applying an ACL to an interface, see the packet-filter (interface view) command in ACL commands.

Suppose a packet filter, QoS policy, or routing policy in sharing mode is applied in the outbound direction of an Ethernet interface. When this interface is assigned to an aggregation group with a QoS policy in non-sharing mode applied in the outbound direction, the QoS policy does not take effect on the Ethernet interface.

The display qos policy interface command output for an interface also contains packet statistics for all interfaces that share the QoS and ACL resource with the interface.

You cannot change the sharing mode dynamically after a QoS policy is applied to an interface. To change the sharing mode for an applied QoS policy, perform the following steps:

1. Remove the QoS policy from the interface.

2. Reapply the QoS policy with or without the share-mode keyword specified.

A maximum of five QoS policies (one for each type) can be applied to the same direction of an interface. Different actions can be taken on the same traffic class if QoS policies of different types are applied to an interface.

Layer 3 Ethernet subinterfaces do not support applying QoS policies in the outbound direction.

Examples

# Apply generic QoS policy TEST1 to the outgoing traffic of HundredGigE 1/1/1.

<Sysname> system-view

[Sysname] interface hundredgige 1/1/1

[Sysname-HundredGigE1/1/1] qos apply policy TEST1 outbound

# Apply accounting-type QoS policy TEST2 to the outgoing traffic of HundredGigE 1/1/1.

<Sysname> system-view

[Sysname] interface hundredgige 1/1/1

[Sysname-HundredGigE1/1/1] qos apply accounting policy TEST2 outbound

# Apply mirroring-type QoS policy TEST3 to the outgoing traffic of HundredGigE 1/1/1.

<Sysname> system-view

[Sysname] interface hundredgige 1/1/1

[Sysname-HundredGigE1/1/1] qos apply mirroring policy TEST3 outbound

# Apply marking-type QoS policy TEST4 to the outgoing traffic of HundredGigE 1/1/1.

<Sysname> system-view

[Sysname] interface hundredgige 1/1/1

[Sysname-HundredGigE1/1/1] qos apply remarking policy TEST4 outbound

# Apply generic QoS policy TEST5 to the incoming traffic of the control plane of slot 3.

<Sysname> system-view

[Sysname] control-plane slot 3

[Sysname-cp-slot3] qos apply policy TEST5 inbound

# Apply generic QoS policy TEST10 in sharing mode to the outgoing traffic of HundredGigE 1/1/1.

<Sysname> system-view

[Sysname] interface hundredgige 1/1/1

[Sysname-HundredGigE1/1/1] qos apply policy TEST10 outbound share-mode

# Apply IPv6-matching QoS policy TEST13 to the outgoing traffic of HundredGigE 1/1/1.

<Sysname> system-view

[Sysname] interface hundredgige 1/1/1

[Sysname-HundredGigE1/1/1] qos apply ipv6-matching policy TEST13 outbound

qos apply policy (user profile view)

Use qos apply policy to apply a QoS policy to a user profile.

Use undo qos apply policy to remove a QoS policy applied to a user profile.

Syntax

qos apply policy policy-name { inbound | outbound }

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

Default

No QoS policy is applied to a user profile.

Views

User profile view

Predefined user roles

network-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 traffic of the device (traffic sent by online users).

outbound: Applies the QoS policy to the outgoing traffic of the device (traffic received by online users).

Usage guidelines

Deleting a user profile also removes the QoS policies applied to the user profile.

For a user profile to be active, the QoS policy applied in user profile view cannot be empty. A user profile supports only the car and accounting actions in a QoS policy.

Examples

# Apply QoS policy test to outgoing traffic for user profile user.

<Sysname> system-view

[Sysname] user-profile user

[Sysname-user-profile-user] qos apply policy test outbound

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 [ ipv6-matching | accounting | mirroring | remarking ] policy policy-name global { inbound | outbound } [ longest-match ]

undo qos apply [ ipv6-matching | accounting | mirroring | remarking ] policy policy-name global { inbound | outbound }

Default

No QoS policy is applied globally.

Views

System view

Predefined user roles

network-admin

Parameters

ipv6-matching: Specifies an IPv6-matching QoS policy.

accounting: Specifies an accounting-type QoS policy.

mirroring: Specifies a mirroring-type QoS policy.

remarking: Specifies a marking-type QoS policy.

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.

longest-match: First matches the traffic class with a source or destination IP address with the longest mask and takes the actions in the associated traffic behavior if a match is found.

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.

A maximum of five QoS policies (one generic, one IPv6-matching, one accounting-type, one mirroring-type, and one marking-type) can be applied to one direction globally.

If you do not specify the longest-match keyword, the system matches traffic against traffic classes in the order class-behavior associations are configured. When the traffic matches a traffic class, the matching process stops, and the actions in the associated traffic behavior are taken on the matching traffic.

If you specify the longest-match keyword, the system first matches the traffic class with a source or destination address with the longest mask and takes the actions in the associated traffic behavior. Suppose three class-behavior associations are configured in a QoS policy. ACL 3001 in the traffic class of the first class-behavior association is not configured with a source or destination address. ACL 3002 in the traffic class of the second class-behavior association is configured with destination address 10.10.10.0/24. ACL 3003 in the traffic class of the third class-behavior association is configured with destination address 10.10.10.10/32. The match order of the three class-behavior associations is the third class-behavior association, the second class-behavior association, the first class-behavior association.

If both source and destination addresses exist in ACLs of different traffic classes, the system matches destination addresses before matching source addresses.

If you do not specify the ipv6-matching, accounting, mirroring, or remarking keyword, this command applies a generic QoS policy globally.

Examples

# Globally apply generic QoS policy user1 to the incoming traffic.

<Sysname> system-view

[Sysname] qos apply policy user1 global inbound

# Globally apply mirroring-type QoS policy user2 to the incoming traffic.

<Sysname> system-view

[Sysname] qos apply mirroring policy user2 global inbound

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 [ ipv6-matching | accounting | mirroring | remarking ] policy policy-name

undo qos [ ipv6-matching | accounting | mirroring | remarking ] policy policy-name

Default

No QoS policies exist.

Views

System view

Predefined user roles

network-admin

Parameters

ipv6-matching: Identifies the QoS policy as an IPv6-matching QoS policy.

accounting: Identifies the QoS policy as an accounting-type QoS policy.

mirroring: Identifies the QoS policy as a mirroring-type QoS policy.

remarking: Identifies the QoS policy as a marking-type QoS policy.

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

Usage guidelines

If you do not specify the ipv6-matching, accounting, mirroring, or remarking keyword when creating a QoS policy, a generic QoS policy is created.

QoS policies of different types cannot use the same policy name.

Do not use the ipv6-matching, accounting, mirroring, or remarking word or the first letters of any one of them as a policy name. If you do so, no information is displayed when you execute the display qos policy user-defined policy-name command, because the system will recognize such a policy name as a command keyword.

A generic QoS policy can be applied to all supported destinations and can contain all actions. An IPv6-matching QoS policy can be applied to only interfaces or globally and is used for traffic classes containing IPv6 ACL match criteria.An accounting-type QoS policy can be applied to only interfaces or globally and can contain only class-based accounting actions.A mirroring-type QoS policy can only be applied to interfaces or globally and can contain only mirroring actions.A marking-type QoS policy can be applied to only interfaces or globallyand can contain only marking actions.

An IPv6-matching QoS policy is used for traffic classes containing IPv6 ACL match criteria. Other QoS policy types do not distinguish between IPv4 and IPv6.

In some scenarios, you need to apply a QoS policy for matching IPv4 packets and a QoS policy for matching IPv6 packets to the same direction of the same object. In this case, you use a generic QoS policy for matching IPv4 packets and an IPv6-matching QoS policy.

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 generic QoS policy named user1.

<Sysname> system-view

[Sysname] qos policy user1

[Sysname-qospolicy-user1]

# Create an accounting-type QoS policy named user2.

<Sysname> system-view

[Sysname] qos accounting policy user2

[Sysname-qospolicy-user2]

# Create a marking-type QoS policy named user3.

<Sysname> system-view

[Sysname] qos remarking policy user3

[Sysname-qospolicy-user3]

# Create a mirroring-type QoS policy named user4.

<Sysname> system-view

[Sysname] qos mirroring policy user4

[Sysname-qospolicy-user4]

# Create an IPv6-matching QoS policy named user6.

<Sysname> system-view

[Sysname] qos ipv6-matching policy user6

[Sysname-qospolicy-user6]

Related commands

classifier behavior

qos apply policy

qos apply policy global

qos vlan-policy

Use qos vlan-policy to apply a QoS policy to the specified VLANs.

Use undo qos vlan-policy to remove a QoS policy from the specified VLANs.

Syntax

qos vlan-policy policy-name vlan vlan-id-list { inbound | outbound } [ longest-match ]

undo qos vlan-policy policy-name vlan vlan-id-list { inbound | outbound }

Default

No QoS policy is applied to a VLAN.

Views

System view

Predefined user roles

network-admin

Parameters

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

vlan vlan-id-list: Specifies a space-separated list of up to eight VLAN IDs or a VLAN ID range 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.

inbound: Applies the QoS policy to incoming packets.

outbound: Applies the QoS policy to outgoing packets.

longest-match: First matches the traffic class with a source or destination IP address with the longest mask and takes the actions in the associated traffic behavior if a match is found.

Examples

# Apply QoS policy test to the incoming traffic of VLAN 200, VLAN 300, VLAN 400, and VLAN 500.

<Sysname> system-view

[Sysname] qos vlan-policy test vlan 200 300 400 500 inbound

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

reset qos policy control-plane slot slot-number

Views

User view

Predefined user roles

network-admin

Parameters

slot slot-number: Specifies the slot number of the device, which is fixed at 1.

Examples

# Clear the statistics of the QoS policy applied to the control plane of slot 1.

<Sysname> reset qos policy control-plane slot 1

reset qos policy global

Use reset qos policy global to clear statistics for QoS policies applied globally.

Syntax

reset qos [ ipv6-matching | accounting | mirroring | remarking ] policy global [ inbound | outbound ]

Views

User view

Predefined user roles

network-admin

Parameters

ipv6-matching: Specifies IPv6-matching QoS policies.

accounting: Specifies accounting-type QoS policies.

mirroring: Specifies mirroring-type QoS policies.

remarking: Specifies marking-type QoS policies.

inbound: Specifies the QoS policy applied to the inbound direction globally.

outbound: Specifies the QoS policy applied to the outbound direction globally.

Usage guidelines

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

If you do not specify the ipv6-matching, accounting, mirroring, or remarking keyword, this command clears statistics for generic QoS policies.

Examples

# Clear statistics for the generic QoS policy applied to the inbound direction globally.

<Sysname> reset qos policy global inbound

# Clear statistics for the mirroring-type QoS policy applied to the inbound direction globally.

<Sysname> reset qos mirroring policy global inbound

reset qos vlan-policy

Use reset qos vlan-policy to clear the statistics for QoS policies applied to VLANs.

Syntax

reset qos vlan-policy [ vlan vlan-id ] [ inbound | outbound ]

Views

User view

Predefined user roles

network-admin

Parameters

vlan vlan-id: Specifies a VLAN ID in the range of 1 to 4094.

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 clears the statistics of the QoS policies in both directions of the VLAN.

Examples

# Clear the statistics of QoS policies applied to VLAN 2.

<Sysname> reset qos vlan-policy vlan 2

QoS SNMP notification commands

snmp-agent trap enable qos

Use snmp-agent trap enable qos to enable SNMP notifications for QoS.

Use undo snmp-agent trap enable qos to disable SNMP notifications for QoS.

Syntax

snmp-agent trap enable qos

undo snmp-agent trap enable qos

Default

SNMP notifications are disabled for QoS.

Views

System view

Predefined user roles

network-admin

Usage guidelines

Execute this command to report critical QoS events by sending SNMP notifications.

For QoS notifications to be sent correctly, you must also configure SNMP on the device. For more information about SNMP configuration, see the network management and monitoring configuration guide for the device.

Examples

# Enable SNMP notifications for QoS.

<Sysname> system-view

[Sysname] snmp-agent trap enable qos

Priority mapping commands

Priority map commands

display qos map-table

Use display qos map-table to display the configuration of priority maps.

Syntax

Views

Any view

Predefined user roles

network-admin

network-operator

Parameters

The device provides the following types of priority map.

Table 18 Priority maps

Priority mapping	Description
dot1p-dp	802.1p-drop priority map.
dot1p-exp	802.1p-EXP priority map.
dot1p-lp	802.1p-local priority map.
dscp-dot1p	DSCP-802.1p priority map.
dscp-dp	DSCP-drop priority map.
dscp-dscp	DSCP-DSCP priority map.
exp-dot1p	EXP-802.1p priority map.
exp-dp	EXP-drop priority map.

‌

Usage guidelines

If you do not specify a priority map, this command displays the configuration of all priority maps.

Examples

# Display the configuration of the 802.1p-local priority map.

<Sysname> display qos map-table dot1p-lp

MAP-TABLE NAME: dot1p-lp TYPE: pre-define

IMPORT : EXPORT

0 : 2

1 : 0

2 : 1

3 : 3

4 : 4

5 : 5

6 : 6

7 : 7

Table 19 Command output

Field	Description
MAP-TABLE NAME	Name of the priority map.
TYPE	Type of the priority map.
IMPORT	Input values of the priority map.
EXPORT	Output values of the priority map.

import

Use import to configure mappings for a priority map.

Use undo import to restore the specified or all mappings to the default for a priority map.

Syntax

import import-value-list export export-value

undo import { import-value-list | all }

Default

The default priority maps are used. For more information, see ACL and QoS Configuration Guide.

Views

Priority map view

Predefined user roles

network-admin

Parameters

import-value-list: Specifies a list of input values.

export-value: Specifies the output value.

all: Restores all mappings in the priority map to the default.

Examples

# Configure the 802.1p-local priority map to map 802.1p priority values 4 and 5 to local priority 1.

<Sysname> system-view

[Sysname] qos map-table dot1p-lp

[Sysname-maptbl-dot1p-lp] import 4 5 export 1

Related commands

display qos map-table

qos map-table

Use qos map-table to enter the specified priority map view.

Syntax

qos map-table { dot1p-dp | dot1p-exp | dot1p-lp | dscp-dot1p| dscp-dp | dscp-dscp | dscp-exp | exp-dot1p | exp-dp }

Views

System view

Predefined user roles

network-admin

Parameters

For the description of other keywords, see Table 18.

Examples

# Enter 802.1p-local priority map view.

<Sysname> system-view

[Sysname] qos map-table dot1p-lp

[Sysname-maptbl-dot1p-lp]

Related commands

display qos map-table

import

Priority trust mode commands

display qos trust interface

Use display qos trust interface to display the priority trust mode and port priorities of an interface.

Syntax

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

Views

Any view

Predefined user roles

network-admin

network-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 priority trust mode and port priorities of all interfaces.

Examples

# Display the priority trust mode and port priority of HundredGigE 1/1/1.

<Sysname> display qos trust interface hundredgige 1/1/1

Interface: HundredGigE1/1/1

Port priority information

Port priority: 4

Port dscp priority: -

Port priority trust type: dscp

Table 20 Command output

Field	Description
Interface	Interface type and interface number.
Port priority	Port priority set for the interface.
Port dscp priority	DSCP value rewritten for packets. If you have not rewritten the DSCP value of packets, this field displays a hyphen (-).
Port priority trust type	Priority trust mode on the interface: · dot1p—Uses the 802.1p priority of received packets for mapping. · dscp—Uses the DSCP precedence of received IP packets for mapping. · none—Trusts no packet priority.

qos trust

Use qos trust to configure the priority trust mode for an interface.

Use undo qos trust to restore the default.

Syntax

qos trust { dot1p | dscp }

undo qos trust

Default

An interface does not trust any packet priority and uses the port priority as the 802.1p priority for mapping.

Views

Layer 2/Layer 3 Ethernet interface view

Predefined user roles

network-admin

Parameters

dot1p: Uses the 802.1p priority in incoming packets for priority mapping.

dscp: Uses the DSCP value in incoming packets for priority mapping.

Examples

# Set the priority trust mode to 802.1p priority on HundredGigE 1/1/1.

<Sysname> system-view

[Sysname] interface hundredgige 1/1/1

[Sysname-HundredGigE1/1/1] qos trust dot1p

Related commands

display qos trust interface

qos trust (system view)

Use qos trust to configure the global priority trust mode for VXLAN packets.

Use undo qos trust to restore the default.

Syntax

qos trust { tunnel-dot1p | tunnel-dscp }

undo qos trust { tunnel-dot1p | tunnel-dscp }

Default

The global priority trust mode for VXLAN packets is not configured.

Views

System view

Predefined user roles

network-admin

Parameters

tunnel-dot1p: Trusts the 802.1p priority in the outer Ethernet header of VXLAN packets for priority mapping.

tunnel-dscp: Trusts the DSCP value in the outer IP header of VXLAN packets for priority mapping.

Usage guidelines

For a VXLAN tunnel interface to trust the DSCP priority in the outer IP header of VXLAN packets, you must also configure the qos trust dscp command on its physical interface.

For a VXLAN tunnel interface to trust the 802.1p priority in the outer Ethernet header of VXLAN packets, you must also configure the qos trust dot1p command on its physical interface.

For PFC to take effect on an overlay network, configure the qos trust tunnel-dot1p command on all VTEPs. For information about overlay networks, see VXLAN Configuration Guide. For information about PFC, see Ethernet interface configuration in Layer 2—LAN Switching Configuration Guide.

Examples

# Configure the switch to trust the DSCP priority in the outer IP header of VXLAN packets.

<Sysname> system-view

[Sysname] qos trust tunnel-dscp

# Configure the switch to trust the 802.1p priority in the outer Ethernet header of VXLAN packets.

<Sysname> system-view

[Sysname] qos trust tunnel-dot1p

Port priority commands

qos priority

Use qos priority to change the port priority of an interface.

Use undo qos priority to restore the default.

Syntax

qos priority [ dscp ] priority-value

undo qos priority [ dscp ]

Default

The port priority is 0, and the DSCP value of packets is not modified.

Views

Layer 2/Layer 3 Ethernet interface view

Predefined user roles

network-admin

Parameters

priority-value: Specifies a priority value. If the dscp keyword is not specified, this argument specifies the port priority in the range of 0 to 7. If the dscp keyword is specified, this argument specifies the DSCP value to be set for packets, in the range of 0 to 63.

Examples

# Set the port priority of HundredGigE 1/1/1 to 2, and modify the DSCP value of Layer 3 packets to 20.

<Sysname> system-view

[Sysname] interface hundredgige 1/1/1

[Sysname-HundredGigE1/1/1] qos priority 2

[Sysname-HundredGigE1/1/1] qos priority dscp 20

Related commands

display qos trust interface

Global priority commands

qos mirroring local-precedence

Use qos mirroring local-precedence to set the local precedence of mirrored packets.

Use undo qos mirroring local-precedence to restore the default.

Syntax

qos mirroring local-precedence local-precedence-value

undo qos mirroring local-precedence

Default

The local precedence of a mirrored packet is the same as that of the original packet.

Views

System view

Predefined user roles

network-admin

Parameters

local-precedence-value: Specifies a local precedence value in the range of 0 to 7. The greater the value, the higher the priority.

Usage guidelines

On the mirroring source device, both mirrored packets and service packets might exist on the egress port. To schedule service packets preferentially, perform this task to set the local precedence of mirrored packets to a smaller value, for example, 0. In this case, when congestion occurs, less service packets will be dropped.

This command takes effect on packets mirrored by both port mirroring and flow mirroring.

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

Examples

# Set the local precedence of mirrored packets to 5.

<Sysname> system-view

[Sysname] qos mirroring local-precedence 5

GTS and rate limit commands

GTS commands

display qos gts interface

Use display qos gts interface to display the GTS configuration for interfaces.

Syntax

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

Views

Any view

Predefined user roles

network-admin

network-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 GTS configuration for all interfaces.

Examples

# Display the GTS configuration for all interfaces.

<Sysname> display qos gts interface

Interface: HundredGigE1/1/1

Rule: If-match queue 1

CIR 512 (kbps), CBS 51200 (Bytes)

Table 21 Command output

Field	Description
Interface	Interface name, including the interface type and interface number.
Rule	Match criteria.
CIR	CIR in kbps.
CBS	CBS in bytes.

qos gts

Use qos gts to set GTS parameters on an interface.

Use undo qos gts to delete the GTS configuration on an interface.

Syntax

qos gts queue queue-id cir committed-information-rate [ cbs committed-burst-size ]

undo qos gts queue queue-id

Default

No GTS parameters are configured.

Views

Layer 2/Layer 3 Ethernet interface view

Predefined user roles

network-admin

Parameters

queue queue-id: Shapes the packets in a queue specified by its ID. The value range for queue-id is 0 to 7.

cir committed-information-rate: Specifies the CIR in kbps. The value range for committed-information-rate is 8 to 100000000 for 100-GE interfaces and 8 to 400000000 for 400-GE interfaces. This value must be a multiple of 8.

cbs committed-burst-size: Specifies the CBS in bytes. The value range for committed-burst-size is 512 to 16000000, in increments of 512. The default value for this argument is the product of 62.5 and the CIR and must be a multiple of 512. When the product is not a multiple of 512, it is rounded up to the nearest integral multiple of 512 that is greater than the product. A default value greater than 16000000 is converted to 16000000.

Examples

# Shape the packets in queue 1 on HundredGigE 1/1/1. The GTS parameters are as follows:

· The CIR is 6400 kbps.

· The CBS is 51200 bytes.

<Sysname> system-view

[Sysname] interface hundredgige 1/1/1

[Sysname-HundredGigE1/1/1] qos gts queue 1 cir 6400 cbs 51200

Rate limit commands

display qos lr interface

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

Syntax

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

Views

Any view

Predefined user roles

network-admin

network-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 for all interfaces.

Examples

# Display the rate limit configuration for all interfaces.

<Sysname> display qos lr interface

Interface: HundredGigE1/1/1

Direction: Outbound

CIR 2000 (kbps), CBS 20480 (Bytes)

Table 22 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.
CBS	CBS in bytes.

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 ]

undo qos lr outbound

Default

No rate limit is configured.

Views

Layer 2/Layer 3 Ethernet interface view

Predefined user roles

network-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 is 8 to 100000000 (only 32 to 100000000 is supported) for 100-GE interfaces and 8 to 400000000 (only 32 to 400000000 is supported)for 100-GE interfaces. The specified value must be a multiple of 8.

cbs committed-burst-size: Specifies the CBS in bytes. The value range for committed-burst-size is 512 to 128000000, in increments of 512. The default value for this argument is the product of 62.5 and the CIR and must be a multiple of 512. When the product is not a multiple of 512, it is rounded up to the nearest integral multiple of 512 that is greater than the product. A default value greater than 128000000 is converted to 128000000.

Examples

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

<Sysname> system-view

[Sysname] interface hundredgige 1/1/1

[Sysname-HundredGigE1/1/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

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.

Examples

# Display the queuing information for all interfaces.

<Sysname> display qos queue interface

Interface: HundredGigE1/1/1

Output queue: Weighted Round Robin queuing

Queue ID Queue name Group Byte count

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

0 be 1 1

1 af1 1 2

2 af2 1 3

3 af3 1 4

4 af4 1 5

5 ef 1 9

6 cs6 1 13

7 cs7 1 15

Interface: HundredGigE1/1/2

Output queue: Weighted Round Robin queuing

Queue ID Queue name Group Byte count

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

0 be 1 1

1 af1 1 2

2 af2 1 3

3 af3 1 4

4 af4 1 5

5 ef 1 9

6 cs6 1 13

7 cs7 1 15

…

Table 23 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.

SP commands

display qos queue sp interface

Use display qos queue sp interface to display the SP queuing configuration of an interface.

Syntax

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

Views

Any view

Predefined user roles

network-admin

network-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 SP queuing configuration of all interfaces.

Examples

# Display the SP queuing configuration of HundredGigE 1/1/1.

<Sysname> display qos queue sp interface hundredgige 1/1/1

Interface: HundredGigE1/1/1

Output queue: Strict Priority queuing

Table 24 Command output

Field	Description
Interface	Interface type and interface number.
Output queue	Type of the current output queue.

qos sp (interface view)

Use qos sp to enable SP queuing on an interface.

Use undo qos sp to restore the default.

Syntax

qos sp

undo qos sp

Default

An interface uses byte-count WRR queuing.

Views

Layer 2/Layer 3 Ethernet interface view

Predefined user roles

network-admin

Examples

# Enable SP queuing on HundredGigE 1/1/1.

<Sysname> system-view

[Sysname] interface hundredgige 1/1/1

[Sysname-HundredGigE1/1/1] qos sp

Related commands

display qos queue sp interface

WRR commands

display qos queue wrr interface

Use display qos queue wrr interface to display the WRR queuing configuration of an interface.

Syntax

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

Views

Any view

Predefined user roles

network-admin

network-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 WRR queuing configuration of all interfaces.

Examples

# Display the WRR queuing configuration of HundredGigE 1/1/1.

<Sysname> display qos queue wrr interface hundredgige 1/1/1

Interface: HundredGigE1/1/1

Output queue: Weighted Round Robin queuing

Queue ID Queue name Group Weight

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

0 be 1 1

1 af1 1 1

2 af2 1 1

3 af3 1 1

4 af4 1 1

5 ef 1 1

6 cs6 1 1

7 cs7 sp N/A

Table 25 Command output

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

‌

qos wrr (interface view)

Use qos wrr to enable WRR queuing on an interface.

Use undo qos wrr to restore the default.

Syntax

qos wrr { byte-count | weight }

undo qos wrr { byte-count | weight }

Default

An interface uses byte-count WRR queuing.

Views

Layer 2/Layer 3 Ethernet interface view

Predefined user roles

network-admin

Parameters

byte-count: Allocates bandwidth to queues in bytes.

weight: Allocates bandwidth to queues in packets.

Usage guidelines

You must use the qos wrr command to enable WRR queuing before you can configure WRR queuing parameters for a queue on an interface.

Configuring WRR on an interface will cause transient packet loss.

Examples

# Enable packet-count WRR queuing on HundredGigE 1/1/1.

<Sysname> system-view

[Sysname] interface hundredgige 1/1/1

[Sysname-HundredGigE1/1/1] qos wrr weight

# Enable byte-count WRR queuing on HundredGigE 1/1/1.

<Sysname> system-view

[Sysname] interface hundredgige 1/1/1

[Sysname-HundredGigE1/1/1] qos wrr byte-count

Related commands

display qos queue wrr interface

qos wrr { byte-count | weight }

Use qos wrr { byte-count | weight } to configure the WRR queuing parameters for a queue on an interface.

Use undo qos wrr to restore the default.

Syntax

qos wrr queue-id group 1 { byte-count | weight } schedule-value

undo qos wrr queue-id

Default

All queues on a WRR-enabled interface are in WRR group 1, and queues 0 through 7 have a byte-count or packet-based weight of 1, 2, 3, 4, 5, 6, 7, and 8, respectively.

Views

Layer 2/Layer 3 Ethernet interface view

Predefined user roles

network-admin

Parameters

queue-id: Specifies a queue by its ID. The value range for this argument is 0 to 7 or keywords in Table 26.

Table 26 The number-keyword map for the queue-id argument

Number	Keyword
0	be
1	af1
2	af2
3	af3
4	af4
5	ef
6	cs6
7	cs7

group 1: Specifies WRR group 1. Only WRR group 1 is supported in the current software version.

byte-count: Allocates bandwidth to queues in bytes.

weight: Allocates bandwidth to queues in packets.

schedule-value: Specifies a scheduling weight. The value range for this argument is 1 to 127.

Usage guidelines

You must use the qos wrr command to enable WRR queuing before you can configure WRR queuing parameters for a queue on an interface.

Configuring WRR on an interface will cause transient packet loss.

Examples

# Enable byte-count WRR queuing on HundredGigE 1/1/1, assign queue 0 to WRR group 1, and specify scheduling weight 10 for queue 0.

<Sysname> system-view

[Sysname] interface hundredgige 1/1/1

[Sysname-HundredGigE1/1/1] qos wrr byte-count

[Sysname-HundredGigE1/1/1] qos wrr 0 group 1 byte-count 10

Related commands

display qos queue wrr interface

qos wrr

qos wrr group sp

Use qos wrr group sp to assign a queue to the SP group.

Use undo qos wrr group sp to remove a queue from the SP group.

Syntax

qos wrr queue-id group sp

undo qos wrr queue-id

Default

All queues on a WRR-enabled interface are in WRR group 1.

Views

Layer 2/Layer 3 Ethernet interface view

Predefined user roles

network-admin

Parameters

queue-id: Specifies a queue by its ID. The value range for this argument is 0 to 7 or keywords in Table 26.

Usage guidelines

This command is available only on a WRR-enabled interface. Queues in the SP group are scheduled with SP. The SP group has higher scheduling priority than the WRR groups.

You must use the qos wrr command to enable WRR queuing before you can configure this command on an interface.

Examples

# Enable WRR queuing on HundredGigE 1/1/1, and assign queue 0 to the SP group.

<Sysname> system-view

[Sysname] interface hundredgige 1/1/1

[Sysname-HundredGigE1/1/1] qos wrr weight

[Sysname-HundredGigE1/1/1] qos wrr 0 group sp

Related commands

display qos queue wrr interface

qos wrr

WFQ commands

display qos queue wfq interface

Use display qos queue wfq interface to display the WFQ configuration of an interface.

Syntax

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

Views

Any view

Predefined user roles

network-admin

network-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 WFQ configuration of all interfaces.

Examples

# Display the WFQ configuration of HundredGigE 1/1/1.

<Sysname> display qos wfq interface hundredgige 1/1/1

Interface: HundredGigE1/1/1

Output queue: Hardware Weighted Fair Queuing

Queue ID Queue name Group Byte count Min Bandwidth

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

0 be 1 1 64

1 af1 1 1 64

2 af2 1 1 64

3 af3 1 1 64

4 af4 1 1 64

5 ef 1 1 64

6 cs6 1 1 64

7 cs7 1 1 64

Table 27 Command output

Field	Description
Interface	Interface type and interface number.
Output queue	Type of the current output queue.
Group	ID of the group that holds the queue.
Byte-count	Byte-count scheduling weight of the queue. N/A is displayed for a queue that uses the SP scheduling algorithm.
Weight	Packet-count queue scheduling weight of the queue. N/A is displayed for a queue that uses the SP scheduling algorithm.
Min Bandwidth	Minimum guaranteed bandwidth for the queue.

qos bandwidth queue

Use qos bandwidth queue to set the minimum guaranteed bandwidth for a queue on an interface.

Use undo qos bandwidth queue to restore the default.

Syntax

qos bandwidth queue queue-id min bandwidth-value

undo qos bandwidth queue queue-id

Default

The minimum guaranteed bandwidth for a WFQ queue is 64 kbps.

Views

Layer 2/Layer 3 Ethernet interface view

Predefined user roles

network-admin

Parameters

queue-id: Specifies a queue by its ID. The value range for this argument is 0 to 7 or keywords in Table 26.

min bandwidth-value: Sets the minimum guaranteed bandwidth in kbps. The value range for the bandwidth-value argument is 8 to 100000000.

Usage guidelines

The minimum guaranteed bandwidth is the amount of bandwidth guaranteed for a queue when the interface is congested.

You must use the qos wfq command to enable WFQ before you can configure this command on an interface.

Examples

# Set the minimum guaranteed bandwidth to 100 kbps for queue 0 on HundredGigE 1/1/1.

<Sysname> system-view

[Sysname] interface hundredgige 1/1/1

[Sysname-HundredGigE1/1/1] qos wfq weight

[Sysname-HundredGigE1/1/1] qos bandwidth queue 0 min 100

Related commands

qos wfq

qos wfq (interface view)

Use qos wfq to enable WFQ on an interface.

Use undo qos wfq to restore the default.

Syntax

qos wfq { byte-count | weight }

undo qos wfq { byte-count | weight }

Default

An interface uses byte-count WRR queuing.

Views

Layer 2/Layer 3 Ethernet interface view

Predefined user roles

network-admin

Parameters

byte-count: Allocates bandwidth to queues in bytes.

weight: Allocates bandwidth to queues in packets.

Usage guidelines

You must use the qos wfq command to enable WFQ before you can configure WFQ queuing parameters for a queue on an interface.

Configuring WFQ on an interface will cause transient packet loss.

Examples

# Enable packet-count WFQ on HundredGigE 1/1/1.

<Sysname> system-view

[Sysname] interface hundredgige 1/1/1

[Sysname-HundredGigE1/1/1] qos wfq weight

# Enable byte-count WFQ on HundredGigE 1/1/1.

<Sysname> system-view

[Sysname] interface hundredgige 1/1/1

[Sysname-HundredGigE1/1/1] qos wfq byte-count

Related commands

display qos queue wfq interface

qos wfq { byte-count | weight }

Use qos wfq { byte-count | weight } to assign a queue to a WFQ group with a certain scheduling weight.

Use undo qos wfq to restore the default.

Syntax

qos wfq queue-id group 1 { byte-count | weight } schedule-value

undo qos wfq queue-id

Default

All queues on a WFQ-enabled interface are in WFQ group 1, and each queue has a weight of 1.

Views

Layer 2/Layer 3 Ethernet interface view

Predefined user roles

network-admin

Parameters

queue-id: Specifies a queue by its ID. The value range for this argument is 0 to 7 or keywords in Table 26.

group 1: Specifies WFQ group 1. Only WFQ group 1 is supported in the current software version.

byte-count: Allocates bandwidth to queues in bytes.

weight: Allocates bandwidth to queues in packets.

schedule-value: Specifies a scheduling weight. The value range is 1 to 127.

Usage guidelines

You must use the qos wfq command to enable WFQ before you configure this command.

Configuring WFQ will cause transient packet loss.

Examples

# Enable byte-count WFQ on HundredGigE 1/1/1, and specify scheduling weight 10 for queue 0.

<Sysname> system-view

[Sysname] interface hundredgige 1/1/1

[Sysname-HundredGigE1/1/1] qos wfq byte-count

[Sysname-HundredGigE1/1/1] qos wfq 0 group 1 byte-count 10

Related commands

display qos queue wfq interface

qos bandwidth queue

qos wfq

qos wfq group sp

Use qos wfq group sp to assign a queue to the SP group.

Use undo qos wfq group sp to remove a queue from the SP group.

Syntax

qos wfq queue-id group sp

undo qos wfq queue-id

Default

All queues on a WFQ-enabled interface are in WFQ group 1, and each queue has a weight of 1.

Views

Layer 2/Layer 3 Ethernet interface view

Predefined user roles

network-admin

Parameters

queue-id: Specifies a queue by its ID. The value range for this argument is 0 to 7 or keywords in Table 26.

Usage guidelines

This command is available only on a WFQ-enabled interface. Queues in the SP group are scheduled with SP, instead of WFQ. The SP group has higher scheduling priority than the WFQ groups.

You must use the qos wfq command to enable WFQ before you configure this command.

Examples

# Enable WFQ on HundredGigE 1/1/1, and assign queue 0 to the SP group.

<Sysname> system-view

[Sysname] interface hundredgige 1/1/1

[Sysname-HundredGigE1/1/1] qos wfq weight

[Sysname-HundredGigE1/1/1] qos wfq 0 group sp

Related commands

display qos queue wfq interface

qos bandwidth queue

qos wfq

Queue scheduling profile commands

bandwidth queue

Use bandwidth queue to set the minimum guaranteed bandwidth for a WFQ queue.

Use undo bandwidth queue to restore the default.

Syntax

bandwidth queue queue-id min bandwidth-value

undo bandwidth queue queue-id

Default

The minimum guaranteed bandwidth is 64 kbps for a WFQ queue.

Views

Queue scheduling profile view

Predefined user roles

network-admin

Parameters

queue-id: Specifies a queue by its ID. The value range for this argument is 0 to 7 or keywords in Table 26.

min bandwidth-value: Specifies the minimum guaranteed bandwidth in kbps. The value range for the bandwidth-value argument is 8 to 100000000.

Usage guidelines

You must configure a queue as a WFQ queue before you set the minimum guaranteed bandwidth for the queue.

The minimum guaranteed bandwidth is the amount of bandwidth guaranteed for a queue when the interface is congested.

Examples

# Configure queue 0 as a WFQ queue, and set the minimum guaranteed bandwidth to 100 kbps for queue 0.

<Sysname> system-view

[Sysname] qos qmprofile myprofile

[Sysname-qmprofile-myprofile] queue 0 wfq group 1 weight 1

[Sysname-qmprofile-myprofile] bandwidth queue 0 min 100

display qos qmprofile configuration

Use display qos qmprofile configuration to display the queue scheduling profile configuration.

Syntax

display qos qmprofile configuration [ profile-name ] [ slot slot-number ]

Views

Any view

Predefined user roles

network-admin

network-operator

Parameters

profile-name: Specifies a queue scheduling profile by its name, a case-sensitive string of 1 to 31 characters. If you do not specify a queue scheduling profile, this command displays the configuration of all queue scheduling profiles.

slot slot-number: Specifies the slot number of the device, which is fixed at 1.

Examples

# Display the configuration of queue scheduling profile myprofile.

<Sysname> display qos qmprofile configuration myprofile

Queue scheduling profile: myprofile (ID 1)

Queue ID Type Group Schedule Schedule Min Max

unit value bandwidth bandwidth

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

be WRR 1 weight 1 N/A N/A

af1 WRR 1 weight 2 N/A N/A

af2 WRR 1 weight 3 N/A N/A

af3 WRR 1 weight 4 N/A N/A

af4 WRR 1 weight 5 N/A N/A

ef WRR 1 weight 9 N/A N/A

cs6 WRR 1 weight 13 N/A N/A

cs7 WRR 1 weight 15 N/A N/A

Table 28 Command output

Field	Description
Queue scheduling profile	Queue scheduling profile name.
Type	Queue scheduling type: · SP. · WRR. · WFQ.
Group	Priority group to which the queue belongs. The value can only be 1. N/A indicates this field is ignored.
Schedule unit	Scheduling unit: weight or byte-count. N/A indicates that this field is ignored.
Schedule value	This field indicates: · Number of packets for the weight scheduling unit. · Number of bytes for the byte-count scheduling unit. N/A indicates that this field is ignored.
Min bandwidth	Minimum guaranteed bandwidth for the queue. N/A indicates that this field is ignored.
Max bandwidth	This field is not supported in the current software version. Maximum allowed bandwidth for the queue. N/A indicates that this field is ignored.

‌

display qos qmprofile interface

Use display qos qmprofile interface to display the queue scheduling profile applied to an interface.

Syntax

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

Views

Any view

Predefined user roles

network-admin

network-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 queue scheduling profiles applied to all interfaces.

Examples

# Display the queue scheduling profile applied to HundredGigE 1/1/1.

<Sysname> display qos qmprofile interface hundredgige 1/1/1

Interface: HundredGigE1/1/1

Direction: Outbound

Queue scheduling profile: myprofile

Table 29 Command output

Field	Description
Direction	Direction in which the queue scheduling profile is applied.
Queue scheduling profile	Name of the queue scheduling profile applied to the interface.

qos apply qmprofile

Use qos apply qmprofile to apply a queue scheduling profile to the outbound direction of an interface.

Use undo qos apply qmprofile to restore the default.

Syntax

qos apply qmprofile profile-name

undo qos apply qmprofile

Default

No queue scheduling profile is applied to an interface.

Views

Layer 2/Layer 3 Ethernet interface view

Predefined user roles

network-admin

Parameters

profile-name: Specifies a queue scheduling profile by its name, a case-sensitive string of 1 to 31 characters.

Usage guidelines

You can apply only one queue scheduling profile to an interface.

Examples

# Apply queue scheduling profile myprofile to the outbound direction of HundredGigE 1/1/1.

<Sysname> system-view

[Sysname] interface hundredgige 1/1/1

[Sysname-HundredGigE1/1/1] qos apply qmprofile myprofile

Related commands

display qos qmprofile interface

qos qmprofile

Use qos qmprofile to create a queue scheduling profile and enter its view, or enter the view of an existing queue scheduling profile.

Use undo qos qmprofile to delete a queue scheduling profile.

Syntax

qos qmprofile profile-name

undo qos qmprofile profile-name

Default

No user-created queue scheduling profiles exist.

Views

System view

Predefined user roles

network-admin

Parameters

profile-name: Specifies a name for the queue scheduling profile, a case-sensitive string of 1 to 31 characters.

Usage guidelines

To delete a queue scheduling profile already applied to an object, first remove it from the object.

Examples

# Create a queue scheduling profile named myprofile and enter queue scheduling profile view.

<Sysname> system-view

[Sysname] qos qmprofile myprofile

[Sysname-qmprofile-myprofile]

Related commands

display qos qmprofile interface

queue

Use queue to configure queue scheduling parameters.

Use undo queue to delete queue scheduling parameter settings.

Syntax

queue queue-id { sp | wfq group group-id { weight | byte-count } schedule-value | wrr group group-id { weight | byte-count } schedule-value }

undo queue queue-id

Default

All queues in a queue scheduling profile are WRR queues, and queues 0 through 7 have a packet-count weight of 1, 2, 3, 4, 5, 9, 13, and 15, respectively.

Views

Queue scheduling profile view

Predefined user roles

network-admin

Parameters

queue-id: Specifies a queue by its ID. The value range for this argument is 0 to 7 or keywords in Table 26.

sp: Enables SP for the queue.

wfq: Enables WFQ for the queue.

wrr: Enables WRR for the queue.

group group-id: Specifies a WFQ or WRR group by its ID. The group ID can only be 1.

byte-count: Allocates bandwidth to queues in bytes.

weight: Allocates bandwidth to queues in packets.

schedule-value: Specifies the scheduling weight. The value range is 1 to 127.

Examples

# Create a queue scheduling profile named myprofile, and configure queue 0 to use SP.

<Sysname> system-view

[Sysname] qos qmprofile myprofile

[Sysname-qmprofile-myprofile] queue 0 sp

# Create a queue scheduling profile named myprofile. Configure queue 1 to meet the following requirements:

· The WRR queuing is used.

· The WRR group is group 1.

· The scheduling weight is 10.

<Sysname> system-view

[Sysname] qos qmprofile myprofile

[Sysname-qmprofile-myprofile] queue 1 wrr group 1 weight 10

Related commands

display qos qmprofile interface

qos qmprofile

Queue-based accounting commands

display qos queue-statistics interface outbound

Use display qos queue-statistics interface outbound to display queue-based outgoing traffic statistics for interfaces.

Syntax

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

Views

Any view

Predefined user roles

network-admin

network-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 queue-based outgoing traffic statistics for all interfaces.

Examples

# Display queue-based outgoing traffic statistics for HundredGigE 1/1/1.

<Sysname> display qos queue-statistics interface hundredgige 1/1/1 outbound

Interface: HundredGigE1/1/1

Direction: outbound

Forwarded: 0 packets, 0 bytes

Dropped: 0 packets, 0 bytes

Queue 0

Forwarded: 0 packets, 0 bytes, 0 pps, 0 bps

Dropped: 0 packets, 0 bytes

Current queue length: 0 packets

Queue 1

Forwarded: 0 packets, 0 bytes, 0 pps, 0 bps

Dropped: 0 packets, 0 bytes

Current queue length: 0 packets

Queue 2

Forwarded: 0 packets, 0 bytes, 0 pps, 0 bps

Dropped: 0 packets, 0 bytes

Current queue length: 0 packets

Queue 3

Forwarded: 0 packets, 0 bytes, 0 pps, 0 bps

Dropped: 0 packets, 0 bytes

Current queue length: 0 packets

Queue 4

Forwarded: 0 packets, 0 bytes, 0 pps, 0 bps

Dropped: 0 packets, 0 bytes

Current queue length: 0 packets

Queue 5

Forwarded: 0 packets, 0 bytes, 0 pps, 0 bps

Dropped: 0 packets, 0 bytes

Current queue length: 0 packets

Queue 6

Forwarded: 0 packets, 0 bytes, 0 pps, 0 bps

Dropped: 0 packets, 0 bytes

Current queue length: 0 packets

Queue 7

Forwarded: 0 packets, 0 bytes, 0 pps, 0 bps

Dropped: 0 packets, 0 bytes

Current queue length: 0 packets

Table 30 Command output

Field	Description
Interface	Interface for which queue-based traffic statistics are displayed.
Direction	Direction of traffic for which statistics are collected.
Forwarded	Counts forwarded traffic both in packets and in bytes.
Dropped	Counts dropped traffic both in packets and in bytes.
Current queue length	Number of packets in the queue.

Related commands

reset counters interface (Layer 2—LAN Switching Command Reference)

reset qos queue-statistics interface outbound

Use reset qos queue-statistics interface outbound to clear queue-based outgoing traffic statistics for interfaces.

Syntax

reset qos queue-statistics interface [ interface-type interface-number ] outbound

Views

User view

Predefined user roles

network-admin

Parameters

interface-type interface-number: Specifies an interface by its type and number. If you do not specify an interface, this command clears the queue-based outgoing traffic statistics for all interfaces.

Examples

# Clear queue-based outgoing traffic statistics for all interfaces.

<Sysname> reset qos queue-statistics interface outbound

# Clear queue-based outgoing traffic statistics for HundredGigE 1/1/1.

<Sysname> reset qos queue-statistics interface hundredgige 1/1/1 outbound

Congestion avoidance commands

WRED commands

display qos wred interface

Use display qos wred interface to display the WRED information for interfaces.

Syntax

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

Views

Any view

Predefined user roles

network-admin

network-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 WRED information for all interfaces.

Examples

# Display the WRED information for all interfaces.

<Sysname> display qos wred interface

Interface: HundredGigE1/1/3

Current WRED configuration:

Applied WRED table name: q1

Table type: Queue based WRED

QID gmin gmax gpro ymin ymax ypro rmin rmax rpro exp ECN

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

0 100 1000 10 100 1000 10 100 1000 10 9 N

1 100 1000 10 100 1000 10 100 1000 10 9 N

2 100 1000 10 100 1000 10 100 1000 10 9 N

3 100 1000 10 100 1000 10 100 1000 10 9 N

4 100 1000 10 100 1000 10 100 1000 10 9 N

5 100 1000 10 100 1000 10 100 1000 10 9 N

6 100 1000 10 100 1000 10 100 1000 10 9 N

7 100 1000 10 100 1000 10 100 1000 10 9 N

Table 31 Command output

Field	Description
Interface	Interface type and interface number.
Table type	Type of a WRED table.
QID	Queue ID.
gmin	Lower limit for green packets.
gmax	Upper limit for green packets.
gprob	Drop probability for green packets.
ymin	Lower limit for yellow packets.
ymax	Upper limit for yellow packets.
yprob	Drop probability for yellow packets.
rmin	Lower limit for red packets.
rmax	Upper limit for red packets.
rprob	Drop probability for red packets.
exp	Exponent for average queue length calculation.
ECN	Indicates whether ECN is enabled for the queue: · Y—Enabled. · N—Disabled.

‌

display qos wred table

Use display qos wred table to display the WRED table configuration.

Syntax

display qos wred table [ name table-name ] [ slot slot-number ]

Views

Any view

Predefined user roles

network-admin

network-operator

Parameters

name table-name: Specifies a WRED table by its name, a case-sensitive string of 1 to 32 characters. If you do not specify a WRED table, this command displays the configuration of all WRED tables.

slot slot-number: Specifies the slot number of the device, which is fixed at 1.

Examples

# Display the configuration of WRED table 1.

<Sysname> display qos wred table name 1

Table name: 1

Table type: Queue based WRED

QID gmin gmax gpro ymin ymax ypro rmin rmax rpro exp ECN

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

0 100 1000 10 100 1000 10 100 1000 10 9 N

1 100 1000 10 100 1000 10 100 1000 10 9 N

2 100 1000 10 100 1000 10 100 1000 10 9 N

3 100 1000 10 100 1000 10 100 1000 10 9 N

4 100 1000 10 100 1000 10 100 1000 10 9 N

5 100 1000 10 100 1000 10 100 1000 10 9 N

6 100 1000 10 100 1000 10 100 1000 10 9 N

7 100 1000 10 100 1000 10 100 1000 10 9 N

Table 32 Command output

Field	Description
Table name	Name of a WRED table.
Table type	Type of a WRED table.
QID	Queue ID.
gmin	Lower limit for green packets.
gmax	Upper limit for green packets.
gprob	Drop probability for green packets.
ymin	Lower limit for yellow packets.
ymax	Upper limit for yellow packets.
yprob	Drop probability for yellow packets.
rmin	Lower limit for red packets.
rmax	Upper limit for red packets.
rprob	Drop probability for red packets.
exp	Exponent for average queue length calculation.
ECN	Indicates whether ECN is enabled for the queue: · Y—Enabled. · N—Disabled.

qos wred apply

Use qos wred apply to apply a WRED table to an interface.

Use undo qos wred apply to restore the default.

Syntax

qos wred apply [ table-name ]

undo qos wred apply

Default

No WRED table is applied to an interface, and the tail drop mode is used on an interface.

Views

Layer 2/Layer 3 Ethernet interface view

Predefined user roles

network-admin

Parameters

table-name: Specifies a WRED table by its name, a case-sensitive string of 1 to 32 characters. If you do not specify a WRED table, this command applies the default WRED table to the interface.

Usage guidelines

Applying a WRED table to an interface will cause transient packet loss.

Examples

# Apply WRED table table1 to HundredGigE 1/1/1.

<Sysname> system-view

[Sysname] interface hundredgige 1/1/1

[Sysname-HundredGigE1/1/1] qos wred apply table1

Related commands

display qos wred interface

display qos wred table

qos wred queue table

qos wred smart-ecn enable

qos wred queue

Use qos wred queue to configure the WRED parameters for a queue.

Use undo qos wred queue to restore the default.

Syntax

qos wred queue queue-id low-limit low-limit high-limit high-limit [ discard-probability discard-prob ] [ ecn ] [ weighting-constant exponent ]

qos wred queue queue-id [ drop-level drop-level ] low-limit low-limit high-limit high-limit [ discard-probability discard-prob ]

undo qos wred queue { queue-id [ drop-level drop-level ] | all }

Default

WRED parameters are not set for a queue.

Views

Interface view

Predefined user roles

network-admin

Parameters

queue-id: Specifies a queue by its ID. The value range is 0 to 7.

low-limit low-limit: Specifies the lower limit for the average queue length. The value range for low-limit is 0 ro 130000 in 254 bytes (cell resources).

high-limit high-limit: Specifies the upper limit for the average queue length. The upper limit must be greater than the lower limit. The value range for high-limit is 0 to 130000 in 254 bytes (cell resources) and must be higher than the lower limit.

discard-probability discard-prob: Specifies the denominator for drop probability calculation. The greater the denominator, the greater the calculated drop probability. The value range for discard-prob is 0 to 100.

ecn: Enables ECN.

weighting-constant exponent: Specifies the WRED exponent for average queue length calculation. The default is 9 and the value range is 0 to 15.

drop-level drop-level: Specifies a drop level. This argument is a consideration for dropping packets. The value 0 corresponds to green packets, the value 1 corresponds to yellow packets, and the value 2 corresponds to red packets. If you do not specify a drop level, the subsequent configuration takes effect on the packets in the queue regardless of the drop level.

all: Specifies all queues.

Usage guidelines

When the average queue size is smaller than the lower threshold, no packet is dropped. When the average queue size is between the lower threshold and the upper threshold, the packets are dropped at random. The longer the queue is, the higher the drop probability is. When the average queue size exceeds the upper threshold, subsequent packets are dropped.

Specifying the ecn keyword in this command has the same effect as executing the qos wred queue ecn command.

Specifying the weighting-constant exponent keyword in this command has the same effect as executing the qos wred queue weighting-constant command.

This command and the qos wred apply command are mutually exclusive.

Examples

# Configure the following WRED parameters for in queue 1 on HundredGigE 1/1/1:

· The drop level is 1.

· The lower limit for the average queue length is 10.

· The upper limit for the average queue length is 20.

· The drop probability is 30%.

<Sysname> system-view

[Sysname] interface hundredgige 1/1/1

[Sysname-HundredGigE1/1/1] qos wred queue 1 drop-level 1 low-limit 10 high-limit 20 discard-probability 30

Related commands

display qos wred interface

qos wred queue ecn

Use qos wred queue ecn to enable ECN for a queue.

Use undo qos wred queue ecn to restore the default.

Syntax

qos wred queue queue-id ecn

undo qos wred queue queue-id ecn

Default

ECN is disabled for a queue.

Views

Interface view

Predefined user roles

network-admin

Parameters

queue-id: Specifies a queue by its ID. The value range for this argument is 0 to 7.

Usage guidelines

When both the receiver and sender support ECN, the device can notify the peer end of the congestion status by identifying and setting the ECN flag. ECN avoids deteriorating congestion.

Executing this command has the same effect as specifying the ecn keyword in the qos wred queue command.

To enable ECN, do not specify ToS field bit 6 or 7 as the flag bit in iNQA, and vice versa. For more information about iNQA, see Network Management and Monitoring Configuration Guide.

Examples

# Enable ECN for queue 1 on HundredGigE 1/1/1.

<Sysname> system-view

[Sysname] interface hundredgige 1/1/1

[Sysname-HundredGigE1/1/1] qos wred queue 1 ecn

Related commands

display qos wred interface

qos wred smart-ecn enable

qos wred queue

qos wred queue table

Use qos wred queue table to create a WRED table and enter its view, or enter the view of an existing WRED table.

Use undo qos wred queue table to delete a WRED table.

Syntax

qos wred queue table table-name

undo qos wred queue table table-name

Default

No WRED tables exist.

Views

System view

Predefined user roles

network-admin

Parameters

table table-name: Specifies a name for the WRED table, a case-sensitive string of 1 to 32 characters.

Usage guidelines

You cannot delete a WRED table in use. To delete it, first remove it from the specified interface.

You can use the display qos wred table command to display the default WRED table, which cannot be modified or deleted.

Examples

# Create a queue-based WRED table named queue-table1.

<Sysname> system-view

[Sysname] qos wred queue table queue-table1

[Sysname-wred-table-queue-table1]

Related commands

display qos wred table

qos wred queue weighting-constant

Use qos wred queue weighting-constant to specify an exponent for average queue length calculation for a queue.

Use undo qos wred queue weighting-constant to restore the default.

Syntax

qos wred queue queue-id weighting-constant exponent

undo qos wred queue queue-id weighting-constant

Default

The exponent for average queue length calculation is 9 for a queue.

Views

Interface view

Predefined user roles

network-admin

Parameters

queue-id: Specifies a queue by its ID. The value range for this argument is 0 to 7.

weighting-constant exponent: Specifies the WRED exponent for average queue length calculation. The value range for exponent is 0 to 15.

Usage guidelines

The bigger the exponent is, the less sensitive the average queue size is to real-time queue size changes. The average queue size is calculated using the formula:

Average queue size = previous average queue size × (1-2-n) + current queue size × 2-n,

where n can be configured with the qos wred weighting-constant command.

Executing this command has the same effect as specifying the weighting-constant exponent option in the qos wred queue command.

Examples

# Set the exponent for average queue length calculation to 12 for queue 1 on HundredGigE 1/1/1.

<Sysname> system-view

[Sysname] interface hundredgige 1/1/1

[Sysname-HundredGigE1/1/1] qos wred queue 1 weighting-constant 12

Related commands

display qos wred interface

qos wred queue

qos wred smart-ecn enable

Use qos wred smart-ecn enable to enable Smart ECN globally.

Use undo qos wred smart-ecn enable to disable Smart ECN globally.

Syntax

qos wred smart-ecn [ queue queue-id ] enable

undo qos wred smart-ecn [ queue queue-id ] enable

Default

Smart ECN is disabled globally.

Views

System view

Predefined user roles

network-admin

Parameters

queue queue-id: Specifies a queue by its ID. The value range for this argument is 0 to 7. If you do not specify a queue, this command enables Smart ECN for all queues.

Usage guidelines

This function is mutually exclusive with the function of applying a WRED table to an interface.

On a queue, this function is mutually exclusive with the function of enabling ECN.

This function is mutually exclusive with the global ECN function.

You can enable Smart ECN for a single queue or for all queues, but you cannot perform both tasks.

Examples

# Enable Smart ECN for queue 1.

<Sysname> system-view

[Sysname] qos wred smart-ecn queue 1 enable

# Enable Smart ECN for all queues.

<Sysname> system-view

[Sysname] qos wred smart-ecn enable

Related commands

qos wred apply

qos wred ecn enable

qos wred queue ecn

queue (WRED table view)

Use queue to configure the drop-related parameters for a queue in the queue-based WRED table.

Use undo queue to restore the default.

Syntax

queue queue-id [ drop-level drop-level ] low-limit low-limit high-limit high-limit [ discard-probability discard-prob ]

undo queue { queue-id [ drop-level drop-level ] | all }

Default

The lower limit is 100, the upper limit is 1000, and the drop probability is 10%.

Views

WRED table view

Predefined user roles

network-admin

Parameters

all: Specifies all queues.

queue-id: Specifies a queue by its ID. The value range for this argument is 0 to 7.

low-limit low-limit: Specifies the lower limit for the average queue length. The value range for is 0 to 130000 in 254 bytes (cell resources).

Usage guidelines

Examples

# In queue-based WRED table queue-table1, configure the following drop-related parameters for packets in queue 1:

· The drop level is 1.

· The lower limit for the average queue length is 10.

· The upper limit for the average queue length is 20.

· The drop probability is 30%.

<Sysname> system-view

[Sysname] qos wred queue table queue-table1

[Sysname-wred-table-queue-table1] queue 1 drop-level 1 low-limit 10 high-limit 20 discard-probability 30

Related commands

display qos wred table

qos wred queue table

queue ecn

Use queue ecn to enable ECN for a queue.

Use undo queue ecn to restore the default.

Syntax

queue queue-id ecn

undo queue queue-id ecn

Default

ECN is disabled for a queue.

Views

WRED table view

Predefined user roles

network-admin

Parameters

queue-id: Specifies a queue by its ID in the range of 0 to 7.

Usage guidelines

When both the receiver and sender support ECN, the device can notify the peer end of the congestion status by identifying and setting the ECN flag. ECN avoids deteriorating congestion.

To enable ECN, do not specify ToS field bit 6 or 7 as the flag bit in iNQA, and vice versa. For more information about iNQA, see Network Management and Monitoring Configuration Guide.

Examples

# In WRED table queue-table1, enable ECN for queue 1.

<Sysname> system-view

[Sysname] qos wred queue table queue-table1

[Sysname-wred-table-queue-table1] queue 1 ecn

Related commands

display qos wred table

qos wred queue table

queue weighting-constant

Use queue weighting-constant to specify an exponent for average queue length calculation for a queue.

Use undo queue weighting-constant to restore the default.

Syntax

queue queue-id weighting-constant exponent

undo queue queue-id weighting-constant

Default

The exponent for average queue length calculation is 9.

Views

WRED table view

Predefined user roles

network-admin

Parameters

queue-id: Specifies a queue by its ID. The value range for this argument is 0 to 7.

weighting-constant exponent: Specifies the WRED exponent for average queue length calculation. The value range for exponent is 0 to 15.

Usage guidelines

The bigger the exponent is, the less sensitive the average queue size is to real-time queue size changes. The average queue size is calculated using the formula:

Average queue size = previous average queue size × (1-2-n) + current queue size × 2-n,

where n can be configured with the qos wred weighting-constant command.

Examples

# In WRED table queue-table1, set the exponent for average queue length calculation to 12 for queue 1.

<Sysname> system-view

[Sysname] qos wred queue table queue-table1

[Sysname-wred-table-queue-table1] queue 1 weighting-constant 12

Related commands

display qos wred table

qos wred queue table

Aggregate CAR commands

car name

Use car name to use an aggregate CAR action in a traffic behavior.

Use undo car to restore the default.

Syntax

car name car-name

undo car

Default

No aggregate CAR action is configured in a traffic behavior.

Views

Traffic behavior view

Predefined user roles

network-admin

Parameters

car-name: Specifies the name of an aggregate CAR action. This argument must start with a letter, and is a case-sensitive string of 1 to 31 characters.

Examples

# Use aggregate CAR action aggcar-1 in traffic behavior be1.

<Sysname> system-view

[Sysname] traffic behavior be1

[Sysname-behavior-be1] car name aggcar-1

Related commands

display qos car name

display traffic behavior user-defined

display qos car name

Use display qos car name to display information about aggregate CAR actions.

Syntax

display qos car name [ car-name ]

Views

Any view

Predefined user roles

network-admin

network-operator

Parameters

car-name: Specifies an aggregate CAR action by its name. This argument must start with a letter, and is a case-sensitive string of 1 to 31 characters. If you do not specify an aggregate CAR action, this command displays information about all aggregate CAR actions.

Examples

# Display information about all aggregate CAR actions.

<Sysname> display qos car name

Name: a

Mode: aggregative

CIR 32 (kbps) CBS: 2048 (Bytes) PIR: 888 (kbps) EBS: 0 (Bytes)

Green action : pass

Yellow action : pass

Red action : discard

Table 33 Command output

Field	Description
Name	Name of the aggregate CAR action.
Mode	Type of the CAR action, which can be aggregative.
CIR CBS PIR EBS	Parameters for 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.

qos car

Use qos car aggregative to configure an aggregate CAR action.

Use undo qos car to delete an aggregate CAR action.

Syntax

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

qos car car-name aggregative 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 car-name

Default

No aggregate CAR action is configured.

Views

System view

Predefined user roles

network-admin

Parameters

car-name: Specifies the name of the aggregate CAR action. This argument must start with a letter, and is a case-sensitive string of 1 to 31 characters.

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

cbs committed-burst-size: Specifies the CBS in bytes. The value range for committed-burst-size is 512 to 256000000, in increments of 512. The default value for this argument is the product of 62.5 and the CIR and must be an integral multiple of 512. When the product is not an integral multiple of 512, it is rounded up to the nearest integral multiple of 512 that is greater than the product. A default value greater than 256000000 is converted to 256000000.

ebs excess-burst-size: Specifies the EBS in bytes. The value range for excess-burst-size is 0 to 256000000, in increments of 512. If the PIR is configured, the default EBS is the product of 62.5 and the PIR and must be an integral multiple of 512. When the product is not an integral multiple of 512, it is rounded up to the nearest integral multiple of 512. A default value greater than 256000000 is converted to 256000000.

pir peak-information-rate: Specifies the PIR in kbps. The value range for peak-information-rate is 8 to 4294967288, in increments of 8.

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

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

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

action: Specifies the action to take on packets:

· discard: Drops the packet.

· pass: Permits the packet to pass through.

· 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.

Usage guidelines

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

An aggregate CAR action takes effect only after it is used in a QoS policy.

Examples

# Configure aggregate CAR action aggcar-1, where CIR is 25600, CBS is 512000, and red packets are dropped.

<Sysname> system-view

[Sysname] qos car aggcar-1 aggregative cir 25600 cbs 512000 red discard

Related commands

display qos car name

reset qos car name

Use reset qos car name to clear the statistics about aggregate CAR actions.

Syntax

reset qos car name [ car-name ]

Views

User view

Predefined user roles

network-admin

Parameters

Examples

# Clear the statistics about aggregate CAR action aggcar-1.

<Sysname> reset qos car name aggcar-1

Elephant and mice flows distinguishing commands

elephant-flow action

Use elephant-flow action to configure an action to take on elephant flows.

Use undo elephant-flow action to restore the default.

Syntax

elephant-flow action { drop-precedence drop-precedence-value | dot1p dot1p-value | local-precedence local-precedence-value | none }

undo elephant-flow action

Default

No action is configured.

Views

Elephant/mice flow view

Predefined user roles

network-admin

Parameters

drop-precedence drop-precedence-value: Specifies a drop precedence value in the range of 0 to 2.

dot1p dot1p-value: Specifies an 802.1p priority value in the range of 0 to 7.

local-precedence local-precedence-value: Specifies a local precedence value in the range of 0 to 7.

none: Takes no action.

Examples

# Specify drop precedence 2 for elephant flows.

<Sysname> system-view

[Sysname] qos mice-elephant-flow

[Sysname-mice-elephant-flow] elephant-flow action drop-precedence 2

Related commands

elephant-flow rate

Use elephant-flow rate to configure the traffic thresholds to identify elephant flows.

Use undo elephant-flow rate to remove traffic threshold settings.

Syntax

elephant-flow rate rate [ gbps | kbps | mbps ] [ size size [ bytes | kbytes | mbytes ] ]

undo elephant-flow rate

Default

No traffic thresholds are configured.

Views

Elephant/mice flow view

Predefined user roles

network-admin

Parameters

rate [ gbps | kbps | mbps ]: Specifies the traffic rate threshold in Gbps, kbps, or Mbps. The default unit is kbps. The value range for the rate argument is 1 to 1000.

size size [ bytes | kbytes | mbytes ]: Specifies the traffic size threshold in bytes, KB, or MB. The default unit is byte. The value range for the rate argument is 1 to 1000.

Usage guidelines

The device assigns the drop precedence value specified the elephant-flow action command to the identified elephant flows and keeps the drop precedence of mice flows unchanged. When congestion occurs, packets with a lower or no drop precedence are preferentially forwarded.

Examples

# Specify the traffic thresholds as 20 kbps and 100 KB for identifying elephant flows.

<Sysname> system-view

[Sysname] qos mice-elephant-flow

[Sysname-mice-elephant-flow] elephant-flow rate 20 kbps size 100 kbytes

Related commands

elephant-flow action

agile-buffer enable

Use agile-buffer enable to enable the flexible buffer for elephant and mice flows.

Use undo agile-buffer enable to disable the flexible buffer for elephant and mice flows.

Syntax

agile-buffer enable

undo agile-buffer enable

Default

The flexible buffer for elephant and mice flows is disabled.

Views

Elephant/mice flow view

Predefined user roles

network-admin

Usage guidelines

Prerequisites

For the flexible buffer for elephant and mice flows to take effect, you must configure the following features:

· Enable the feature of distinguishing elephant and mice flows as follows:

a. Execute the elephant-flow rate command to configure the parameters for identifying elephant flows.

b. Execute the elephant-flow action command with the local-precedence keyword specified to configure the local precedence of elephant flows.

· Apply a predefined flow group in mice-elephant-flow mode. For more information about flow groups in mice-elephant-flow mode, see flow group commands in Telemetry Command Reference

Application scenarios

The feature of distinguishing and scheduling elephant flows and mice flows statically configures parameters (for example, flow rate and size) to identify elephant flows in network traffic. Additionally, this feature specifies a lower drop priority, local priority, or 802.1p priority to these elephant flows. In the event of congestion, the device preferentially drops elephant flows based on the assigned priority to ensure fast forwarding of mice flows. The feature of distinguishing elephant and mice flows can partially resolve the issue that mice flows are blocked by elephant flows. However, in scenarios where the vast majority of traffic in the network contains mice flows or in scenarios of bursty traffic, the optimization effect of the elephant and mice flow distinguishing feature, which identifies flows through statically configured parameters, is not ideal. For example, in data center networks, where the majority of traffic contains mice flows that are more sensitive to delay. In the preceding scenarios, you can enable the flexible buffer for elephant and mice flows.

Operating mechanism

On the device, mice flow queues and elephant flow queues share a buffer space to schedule packets. This feature dynamically adjusts the size of the shared buffer space occupied by the mice flow queues and the elephant flow queues. When the network is congested and packets are dropped, the system dynamically reduces the upper limit of the shared buffer space available for elephant flow queues while ensuring high throughput of the elephant flows. In this case, the upper limit of the shared buffer space available for mice flow queues is increased, allowing the shared buffer space to accommodate as much mice flow traffic as possible, avoiding packet loss and reducing delay for mice flows. The device operates as follows after the flexible buffer for elephant and mice flows is enabled:

1. By default, both the elephant flow queues and the mice flow queues use the tail-drop method to drop packets. In this case, when the length of either elephant flow queues or mice flow queues occupies the entire buffer space, all new packets entering the buffer space will be dropped.

2. When the network is congested and packet loss occurs in the mice flow queues, the system triggers the flexible buffer feature for the elephant flows. In this case, the elephant flows use the WRED drop threshold. The system reduces the drop threshold of the elephant flow queues and uses the WRED method to drop elephant flow packets with a certain probability. As a result, the space for mice flow packets in the shared buffer increases.

3. If the device still detects packet loss for mice flows after a certain detection period, this feature further lowers the WRED drop threshold for the elephant flow queues to increase the space for mice flow packets in the shared buffer.

4. If no packet loss occurs in the mice flows during a detection period, this feature gradually restores the drop threshold of the elephant flow queues to the default tail drop method of the system.

Restrictions and guidelines

With this feature enabled, the system will dynamically set the WRED drop threshold (the lower limit of the queue length) for the elephant flow queues. Therefore, this feature conflicts with the statically configured WRED parameters or a WRED table applied on an interface. If you both configure this feature and configure static WRED parameters or apply a WRED table, the static WRED parameters or applied WRED table takes precedence.

Examples

# Enable the flexible buffer for elephant and mice flows.

<Sysname> system-view

[Sysname] qos mice-elephant-flow

[Sysname-mice-elephant-flow] agile-buffer enable

Related commands

elephant-flow action

elephant-flow rate

qos mice-elephant-flow

Use qos mice-elephant-flow to enter elephant/mice flow view.

Syntax

qos mice-elephant-flow

Views

System view

Predefined user roles

network-admin

Examples

# Enter elephant/mice flow view.

<Sysname> system-view

[Sysname] qos mice-elephant-flow

[Sysname-mice-elephant-flow]

Interface packet accounting commands

display qos packet-statistics interface

Use display qos packet-statistics interface to display interface packet statistics.

Syntax

display qos packet-statistics interface interface-type interface-number inbound

Views

Any view

Predefined user roles

network-admin

network-operator

Parameters

interface-type interface-number: Specifies an interface by its type and number.

inbound: Specifies the inbound direction.

Examples

# Display inbound packet statistics for HundredGigE 1/1/1.

<Sysname> display qos packet-statistics interface hundredgige 1/1/1 inbound

Interface: HundredGigE1/1/1

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

DSCP ECN Statistics

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

0 0 1 packets, 100 bytes

0 1 1 packets, 100 bytes

0 2 1 packets, 100 bytes

0 3 1 packets, 100 bytes

…

63 3 1 packets, 100 bytes

qos packet-statistics

Use qos packet-statistics to configure packet accounting on an interface.

Use undo qos packet-statistics to restore the default.

Syntax

qos packet-statistics inbound { dscp | ecn } *

undo qos packet-statistics inbound

Default

Packet accounting is disabled on an interface.

Views

Interface view

Predefined user roles

network-admin

Parameters

inbound: Specifies the inbound direction.

dscp: Counts packets with the DSCP priority.

ecn: Counts ECN packets.

Usage guidelines

If you specify both the dscp and ecn keywords, the device counts ECN packets with the DSCP priority.

If you enable accounting for both DSCP packets and ECN packets, the device will count all non-IP packets as packets with DSCP 0 and ECN 0.

Examples

# Enable packet accounting for ECN packets with the DSCP priority in the inbound direction of HundredGigE 1/1/1.

<Sysname> system-view

[Sysname] interface hundredgige 1/1/1

[Sysname-HundredGigE1/1/1] qos packet-statistics inbound dscp ecn

reset qos packet-statistics interface

Use reset qos packet-statistics interface to clear interface packet statistics.

Syntax

reset qos packet-statistics interface interface-type interface-number inbound

Views

User view

Predefined user roles

network-admin

Parameters

interface-type interface-number: Specifies an interface by its type and number.

inbound: Specifies the inbound direction.

Examples

# Clear inbound packet statistics for HundredGigE 1/1/1.

<Sysname> reset qos packet-statistics interface hundredgige 1/1/1 inbound

QPPB commands

bgp-policy

Use bgp-policy to enable QPPB, which transmits the apply ip-precedence and apply qos-local-id configuration through BGP routing policies.

Use undo bgp-policy to restore the default.

Syntax

bgp-policy { destination | source } { ip-prec-map | ip-qos-map } *

undo bgp-policy { destination | source } [ ip-prec-map | ip-qos-map ] *

Default

QPPB is disabled.

Views

Layer 3 Ethernet interface view

VLAN interface view

Predefined user roles

network-admin

Parameters

destination: Searches the routing table by destination IP address.

source: Searches the routing table by source IP address. If the source keyword is specified, the source IP address is used as the destination address for inverse lookup.

ip-prec-map: Sets an IP precedence value for matching packets.

ip-qos-map: Sets a local QoS ID for matching packets.

Usage guidelines

The bgp-policy command applies only to the incoming traffic of an interface.

In an MPLS L3VPN, the bgp-policy command is executed after the QoS features are performed in the inbound direction of the PE's public network interface. In any other case, the bgp-policy command is executed before the QoS features.

If you configure either of the following bgp-policy command pairs, both commands in the pair take effect:

· bgp-policy destination ip-prec-map and bgp-policy source ip-qos-map.

· bgp-policy source ip-prec-map and bgp-policy destination ip-qos-map.

If you configure either of the following bgp-policy command pairs, the command with the destination keyword in the pair takes effect:

· bgp-policy destination ip-prec-map and bgp-policy source ip-prec-map.

· bgp-policy destination ip-qos-map and bgp-policy source ip-qos-map.

Examples

# Configure HundredGigE 1/1/1 to get the IP precedence and local QoS ID by looking up routes based on destination IP address.

<Sysname> system-view

[Sysname] interface hundredgige 1/1/1

[Sysname-HundredGigE1/1/1] bgp-policy destination ip-prec-map ip-qos-map

Related commands

apply ip-precedence (Layer 3—IP Routing Command Reference)

apply qos-local-id (Layer 3—IP Routing Command Reference)

route-policy (Layer 3—IP Routing Command Reference)

Control plane packet-drop logging commands

qos control-plane logging interval

Use qos control-plane logging interval to set the interval for sending control plane packet-drop logs.

Use undo qos control-plane logging interval to restore the default.

Syntax

qos control-plane logging interval interval

undo qos control-plane logging interval

Default

The interval for sending control plane packet-drop logs is 5 seconds.

Views

System view

Predefined user roles

network-admin

Parameters

interval: Specifies the interval for sending control plane packet-drop logs, in the range of 5 to 60 seconds.

Usage guidelines

This command take effect on all control plane protocols enabled with packet-drop logging. A control plane packet-drop log contains only the number of packets dropped during the interval. If no packets are dropped during an interval, no log is sent.

Examples

# Set the interval for sending control plane packet-drop logs to 10 seconds.

<Sysname> system-view

[Sysname] qos control-plane logging interval 10

Related commands

qos control-plane protocol logging enable

qos control-plane logging protocol enable

Use qos control-plane logging protocol enable to enable packet-drop logging for control plane protocols.

Use undo qos control-plane logging protocol enable to disable packet-drop logging for control plane protocols.

Syntax

qos control-plane logging protocol { protocol-list&<1-8> | all } enable

undo qos control-plane logging protocol { protocol-list&<1-8> | all } enable

Default

Packet-drop logging is disabled for all control plane protocols.

Views

System view

Predefined user roles

network-admin

Parameters

protocol-list&<1-8>: Specifies a space-separated list of up to eight control plane protocol items. Each item specifies a control plane protocol or a range of control plane protocol s in the form of protocol-name1 to protocol-name2.

all: Specifies all control plane protocols.

Usage guidelines

A device provides the user plane and the control plane.

· User plane—The units at the user plane are responsible for receiving, transmitting, and switching (forwarding) packets, such as various dedicated forwarding chips. They deliver super processing speeds and throughput.

· Control plane—The units at the control plane are processing units running most routing and switching protocols. They are responsible for protocol packet resolution and calculation, such as CPUs. Compared with user plane units, the control plane units allow for great packet processing flexibility but have lower throughput.

If protocol packets sent to the control plane are dropped, the protocol operation will be affected. You can configure control plane packet-drop logging. The device regularly generates and sends logs to the information center. For information about configuring the information center, see Network Management and Monitoring Configuration Guide.

Examples

# Enable packet-drop logging for all control plane protocols.

<Sysname> system-view

[Sysname] qos control-plane logging protocol all enable

Related commands

qos control-plane logging interval

07-ACL and QoS Command Reference

QoS policy commands

display traffic classifier

remark ip-precedence

remark qos-local-id

qos apply policy (interface view, control plane view)

display qos lr interface

display qos queue sp interface

qos sp (interface view)

qos wrr (interface view)

qos wrr { byte-count | weight }

qos bandwidth queue

qos wfq (interface view)

qos wfq { byte-count | weight }

qos wfq group sp

Queue scheduling profile commands

display qos qmprofile interface

qos qmprofile

Intelligent Terminal Products

Product Support Services

Technical Service Solutions

Resource Center

Policy

Online Help

Become a Partner

Partner Policy & Program

Global Learning

Partner Sales Resources

Service Business