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

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

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

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

mdc-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 ] { acl-number \| name acl-name } [ inner ]	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. 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 you use the rule [ rule-id ] { deny \| permit } command to match packets, the inner keyword matches the inner header information of VXLAN packets. If you do not specify this keyword, the ACL matches the header information of non-encapsulated packets or the outer header information of VXLAN packets. If you use the rule [ rule-id ] { deny \| permit } vxlan command to match inner header information of VXLAN packets, you cannot specify the inner keyword in the if-match acl command. 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>	Matches control plane protocols. The protocol-name&<1-8> argument specifies a space-separated list of up to eight system-defined control plane protocols. For available system-defined control plane protocols, see Table 3.
control-plane protocol-group protocol-group-name	Matches a control plane protocol group. The protocol-group-name argument can be critical, important, management, monitor, 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 [ mac-address-mask ]	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.
forwarding-layer { bridge \| route }	Matches Layer 2 forwarded packets or Layer 3 forwarded packets. · bridge—Matches Layer 2 forwarded packets. · route—Matches Layer 3 forwarded packets.
inbound-interface interface-type interface-number	Only the SC modules prefixed with LSCM2, SD interface modules, and SF interface modules support this option. Matches an input interface specified by its type and number. If this option is configured in a traffic class with logic AND operator, the traffic class is no longer in effect after the card or subcard where the input interface resides is removed. After the removed card or subcard is reinserted, the traffic class takes effect again. If you do not reinsert the card or subcard and add other match criteria to the traffic class, the traffic class does not take effect again.
ip-precedence ip-precedence-value&<1-8>	Matches IP precedence values. The ip-precedence-value&<1-8> argument specifies a space-separated list of up to eight IP precedence values. The value range for the ip-precedence-value argument is 0 to 7.
outbound-interface interface-type interface-number	Matches an output interface specified by its type and number. This option take effects only on outgoging packets of Layer 2 Ethernet interfaces and Layer 3 Ethernet interfaces.
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 384 on an SF interface module or 1 to 32 on an SC module prefixed with LSCM2 or an SD interface module. This option is supported only in the inbound direction. This option is not supported in the VXLAN M-LAG environment.
qos-local-id egress-active local-id-value	Matches a local QoS ID in the outbound direction, in the range of 1 to 128. · If you use the remark qos-local-id egress-active command to mark packets and the command takes effect only in the outbound direction, you must use the if-match egress-active qos-local-id command to match the packets in the outbound direction. · If you use the remark qos-local-id command to mark packets and the command takes effect on both directions, you must use the if-match egress-active qos-local-id command to match packets.
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.
tunnel-id tunnel-id	Matches a tunnel ID. For SF interface cards: · Only VXLAN tunnel IDs can be matched. · A QoS policy containing this option cannot be applied to Ethernet service instances or tunnel interfaces. · A DSCP marking action is not supported if this option is configured. Cards other than SF interface cards support applying a QoS policy containing this option to only the inbound direction.

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 packets
dhcp	DHCP packets
dhcp-snooping	DHCP snooping packets
dhcp6	IPv6 DHCP packets
dldp	DLDP packets
dot1x	802.1X packets
icmp	ICMP packets
icmp6	ICMPv6 packets
isis	IS-IS packets
lacp	LACP packets
ldp	LDP packets
ldp6	IPv6 LDP packets
lldp	LLDP packets
mld	MLD packets
msdp	MSDP packets
mvrp	MVRP packets (including GVRP packets)
nd	ND packets
ntp	NTP packets
oam	OAM 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
portal	Portal packets
pvst	PVST packets
rip	RIP packets
ripng	RIPng packets
rrpp	RRPP packets
rsvp	RSVP packets
smart-link	SmartLink packets
snmp	SNMP packets
stp	STP packets
udp-helper	UDP helper packets
vrrp	VRRP packets
vrrp6	IPv6 VRRP packets

‌

Usage guidelines

If a Layer 2 ACL rule contains a MAC address match criterion, the ACL rule cannot match IPv6 packets in a QoS policy applied to the outbound direction.

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:

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

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

For a QoS policy to match IPv6 packets in the outbound direction of interfaces on an SF interface card or IPv6 packets on an SE interface card, you must specify IPv6 packet match criteria (for example, configure a rule to match the IPv6 protocol type) in the corresponding traffic classes.

For a QoS policy to match MPLS packets on an LSCM1GT48SC0 card, you must specify MPLS packet match criteria (for example, configure an ACL to match the MPLS protocol type) in the corresponding traffic classes.

On an SF interface card:

· For passing VXLAN packets, a QoS policy applied in the inbound direction cannot match the source MAC address, customer-vlan-id , or customer-dot1p.

· For passing GRE and NVGRE packets, a QoS policy applied in the inbound direction cannot match the source MAC or customer-vlan-id.

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 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 the packets with tunnel ID 2.

<Sysname> system-view

[Sysname] traffic classifier class1

[Sysname-classifier-class1] if-match tunnel-id 2

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

mdc-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

mdc-admin

Parameters

byte: Counts traffic in bytes.

packet: Counts traffic in packets.

Usage guidelines

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

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

Examples

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

<Sysname> system-view

[Sysname] traffic behavior database

[Sysname-behavior-database] accounting byte

car

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

Use undo car to restore the default.

Syntax

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

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

undo car

Default

No CAR action is configured.

Views

Traffic behavior view

Predefined user roles

network-admin

mdc-admin

Parameters

cir committed-information-rate: Specifies the committed information rate (CIR) in the range of 16 to 100000000, which must be a multiple of 8.

cbs committee-burst-size: Specifies the committed burst size (CBS) in bytes. The value range for committed-burst-size is 512 to 67092480, 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 67092480 is converted to 67092480.

ebs excess-burst-size: Specifies the excess burst size (EBS) in the range of 512 to 67092480 bytes. The value must be an integral multiple of 512.

pir peak-information-rate: Specifies the peak information rate (PIR) in the range of 16 to 100000000 kbps, in increments of 8. The PIR and CIR must be configured in the same measurement unit.

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.

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.

<Sysname> system-view

[Sysname] traffic behavior database

[Sysname-behavior-database] car cir 256 cbs 51200

display traffic behavior

Use display traffic behavior to display traffic behaviors.

Syntax

In standalone mode:‌

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

In IRF mode:

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

Views

Any view

Predefined user roles

network-admin

network-operator

mdc-admin

mdc-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 a card by its slot number. If you do not specify a card, this command displays traffic behaviors for the active MPU. (In standalone mode.)

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

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.
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 | permit }

undo filter

Default

No traffic filtering action is configured.

Views

Traffic behavior view

Predefined user roles

network-admin

mdc-admin

Parameters

deny: Drops packets.

permit: Transmits packets. The permitted packets can be processed by other class-behavior associations in the same QoS policy.

Usage guidelines

The keywords in the command have different meanings:

· deny—If a packet matches a traffic class, it is directly dropped and will no longer be affected by actions from lower-priority features.

· permit—If a packet matches a traffic class, the QoS policy does not affect the packet. If the packet is processed by other lower-priority features, whether it is dropped will depend on the actions of those lower-priority features.

Examples

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

<Sysname> system-view

[Sysname] traffic behavior database

[Sysname-behavior-database] filter deny

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

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

Do not apply a QoS policy contains an outer VLAN tag adding action to member ports of an aggregation group, VSIs, or VCs.

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

For a packet added with an outer VLAN tag to be correctly forwarded, make sure the inner VLAN ID of the packet is also allowed by the output interface.

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

packet-rate

Use packet-rate to configure a protocol packet rate limiting action in a traffic behavior.

Use undo packet-rate to restore the default.

Syntax

packet-rate { value | attack-defense-threshold threshold-value } *

undo packet-rate

Default

No protocol packet rate limiting action is configured.

Views

Traffic behavior view

Predefined user roles

network-admin

mdc-admin

Parameters

value: Specifies the protocol packet rate in pps. The value range for this argument is 1 to 30000.

attack-defense-threshold threshold-value: Specifies the attack defense threshold for protocol packets, in pps. The value range for the threshold-value argument is 1 to 30000.

Usage guidelines

Only the SC modules prefixed with LSCM2, SD interface modules, and SF interface modules support this command.

Protocol packet rate limiting can protect the CPU against protocol packet attacks.

By default, the device uses the predefined QoS policy for the control plane to limit the packets of each protocol to the CPU.

The device automatically enables rate limiting on the interface that sends the packets to the CPU if both of the following conditions exist:

· The packet rate of a protocol reaches or exceeds the rate limit.

· The configured attack defense threshold is greater than the configured protocol packet rate.

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

Examples

# Configure traffic behavior copp to rate limit the protocol packets sent to the CPU to 1600 pps.

<Sysname> system-view

[Sysname] traffic behavior copp

[Sysname-behavior-copp] packet-rate 1600

# Configure traffic behavior copp1 to rate limit the protocol packets sent to the CPU to 1600 pps and configure the attack defense threshold for protocol packets as 1400 pps.

<Sysname> system-view

[Sysname] traffic behavior copp1

[Sysname-behavior-copp1] packet-rate 1600 attack-defense-threshold 1400

Related commands

display qos policy

display qos policy control-plane

display qos policy control-plane pre-defined

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 | next-hop { ipv4-add1 [ track track-entry-number ] [ ipv4-add2 [ track track-entry-number ] ] | ipv6-add1 [ track track-entry-number ] [ ipv6-add2 [ track track-entry-number ] ] } [ fail-action { discard | forward } ] }

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

Default

No traffic redirecting action is configured.

Views

Traffic behavior view

Predefined user roles

network-admin

mdc-admin

Parameters

cpu: Redirects traffic to the CPU.

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

next-hop: Redirects traffic to a next hop. For successful traffic redirection, make sure the next hop IP address is reachable. If both primary and secondary next hop IP addresses are specified, make sure a minimum of one IP address is reachable. The redirection feature periodically looks up the routing table to verify the reachability of next hop IP addresses. If track entries are specified, the redirection feature verifies the reachability of the next hop IP addresses based on the Track detection result. If both primary and secondary next hop IP addresses are unreachable, traffic redirection to a next hop does not take effect.

ipv4-add1: Specifies the primary next hop IPv4 address. If traffic fails to be redirected to this IPv4 address, the traffic is redirected to the secondary IPv4 address.

ipv4-add2: Specifies the secondary next hop IPv4 address.

ipv6-add1: Specifies the primary next hop IPv6 address. If traffic fails to be redirected to this IPv6 address, the traffic is redirected to the secondary IPv6 address.

ipv6-add2: Specifies the secondary next hop IPv6 address.

track track-entry-number: Specifies a track entry by its ID in the range of 1 to 1024. Different track entries can be specified for primary and secondary IP addresses. By specifying track entries, you can associate traffic redirection with detection modules, such as NQA and BFD (see High Availability Configuration Guide).

fail-action: Specifies the action to take on packets if the next hop IP address does not exist. Without this parameter configured, the device forwards packets if the next hop IP address does not exist.

discard: Discards packets.

forward: Forwards packets.

Usage guidelines

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

A traffic redirecting action takes effect only when the QoS policy is applied to the inbound direction.

Examples

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

<Sysname> system-view

[Sysname] traffic behavior database

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

# Configure redirecting traffic to a next hop in traffic behavior database.

<Sysname> system-view

[Sysname] traffic behavior database

[Sysname-behavior-database] redirect next-hop 10.55.66.1 track 1 10.55.88.1 track 2 fail-action discard

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

mdc-admin

Parameters

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

Usage guidelines

A CVLAN marking action in a QoS policy takes effect only when it is applied to the inbound direction.

On the SC modules prefixed with LSCM2, SD interface modules, and SF interface modules, do not apply a QoS policy contains a CVLAN marking action to member ports of an aggregation group, VSIs, or VCs.

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 in a traffic behavior.

Use undo remark dot1p to restore the default.

Syntax

remark dot1p dot1p-value

undo remark dot1p

Default

No 802.1p priority marking action is configured.

Views

Traffic behavior view

Predefined user roles

network-admin

mdc-admin

Parameters

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

Usage guidelines

An 802.1p priority marking action in a QoS policy takes effect only when it is applied to the inbound direction.

Examples

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

<Sysname> system-view

[Sysname] traffic behavior database

[Sysname-behavior-database] remark dot1p 2

remark 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

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

A QoS policy with a drop priority marking action takes effect only on the SC modules prefixed with LSCM2 and SE modules.

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 dscp dscp-value

undo remark dscp

Default

No DSCP marking action is configured.

Views

Traffic behavior view

Predefined user roles

network-admin

mdc-admin

Parameters

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

Table 5 DSCP keywords and values

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

Usage guidelines

On non-SF interface modules, a QoS policy with a DSCP marking action can be applied only in the inbound direction.

When you apply a QoS policy to the outbound direction on an SF interface module, follow these restrictions and guidelines:

· The QoS policy is supported only when packets are forwarded within a chip.

· The QoS policy is available only globally, for Layer 2 interfaces, and for Layer 3 Ethernet interfaces.

· When you apply the QoS policy to a Layer 2 or Layer 3 Ethernet interface, it takes effect only on unicast packets.

· When you apply the QoS policy to a Layer 3 Ethernet interface, it also takes effect on traffic of subinterfaces of the Layer 3 Ethernet interface.

· If the packet characteristics change during forwarding and a traffic class matches the changing fields (for example, source MAC address), this feature does not take effect.

· The local QoS ID match criterion is not supported.

The new DSCP value marked on the input interface for a packet does not take effect when it is forwarded out of the output interface if either of the following conditions exists:

· The input interface and output interface are on different interface modules.

· The input interface and output interface are on the same interface module but the values of the LchipId field in the display hardware internal port mapping command output are different.

A DSCP marking action is not supported if the QoS policy is applied to a member port in an aggregation group or if the input interface match criterion is configured to match a member port in an aggregation group.

For SF interface modules:

· A DSCP marking action does not take effect on ECMP traffic if the QoS policy is applied to the outbound direction or the if-match outbound-interface command is used in the traffic class.

· A traffic behavior containing the remark dscp command does not take effect if either of the following conditions exist:

¡ The if-match outbound-interface command is used in the associated traffic class to match a member port of an aggregation group.

¡ The QoS policy is applied to a member port of an aggregation group.

· A DSCP marking action does not take effect if the if-match egress-active qos-local-id command is used in the traffic class and the QoS policy is applied to the outbound direction.

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

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

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

Default

No local precedence marking action is configured.

Views

Traffic behavior view

Predefined user roles

network-admin

mdc-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 15.

green: Marks packets as green packets.

red: Marks packets as red packets.

yellow: Marks packets as yellow packets.

Usage guidelines

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

A local precedence marking action takes effect only on incoming packets on the SC modules prefixed with LSCM2.

Operating mechanism

A local precedence marking action assigns packets matching a traffic class to the specified queue, implementing differentiated services for packets. You can use the command to view outbound traffic statistics for queues.

When using this command to mark the local precedence for packets, you can also assign colors to the packets. By combining 16 different local precedence values with red, yellow, and green, you can use a total of 48 different markings for packets.

You can apply a QoS policy containing this command to mark the local precedence and color for packets on the input interface. Then, you can use the qos map-table color lp-tunnel-dscp command to modify the outer DSCP value of the packets on the output interface.

Restrictions and guidelines

The qos map-table color lp-tunnel-dscp command takes effect only on outgoing packets of VXLAN tunnels or VXLAN-DCI tunnels.

If you specify a local precedence value in the range of 8 to 15, you must specify a color to be marked for the packets.

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

mdc-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 takes effect only when a OoS policy is applied to the inbound direction.

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

Examples

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

<Sysname> system-view

[Sysname] traffic behavior database

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

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

mdc-admin

Parameters

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

Usage guidelines

An SVLAN marking action in a QoS policy takes effect only when it is applied to the inbound direction.

On the SC modules prefixed with LSCM2, SD interface modules, and SF interface modules, do not apply a QoS policy contains a CVLAN marking action to member ports of an aggregation group, VSIs, or VCs.

For a packet with its SVLAN ID marked to be sent out of the output interface, make sure the SVLAN ID before marking is allowed on the output interface and the VLAN tag is not removed.

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

remark source-mac

Use remark source-mac to configure a source MAC address marking action in a traffic behavior.

Use undo remark source-mac to restore the default.

Syntax

remark source-mac mac-address

undo remark source-mac

Default

No source MAC address marking action is configured.

Views

Traffic behavior view

Predefined user roles

network-admin

mdc-admin

Parameters

mac-address: Specifies the source MAC address to be marked for packets, in the format of H-H-H.

Examples

# Configure traffic behavior behavior1 to mark matching traffic with source MAC address 600b-038a-a395.

<Sysname> system-view

[Sysname] traffic behavior behavior1

[Sysname-behavior-behavior1] remark source-mac 600b-038a-a395

Related commands

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

mdc-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 loose | 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

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

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

Usage guidelines

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

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

Examples

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

<Sysname> system-view

[Sysname] qos policy user1

[Sysname-qospolicy-user1] classifier database behavior test

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

<Sysname> system-view

[Sysname] qos policy user1

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

Related commands

qos policy

control-plane

Use control-plane to enter control plane view.

Syntax

In standalone mode:‌

control-plane slot slot-number

In IRF mode:

control-plane chassis chassis-number slot slot-number

Views

System view

Predefined user roles

network-admin

mdc-admin

Parameters

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

Examples

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

<Sysname> system-view

[Sysname] control-plane slot 3

[Sysname-cp-slot3]

control-plane management

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

Syntax

control-plane management

Views

System view

Predefined user roles

network-admin

mdc-admin

Usage guidelines

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

Examples

# Enter control-plane management view.

<Sysname> system-view

[Sysname] control-plane management

[Sysname-cp-management]

display qos policy

Use display qos policy to display QoS policies.

Syntax

In standalone mode:‌

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

In IRF mode:

display qos policy { user-defined [ ipv6-matching | accounting | mirroring | remarking | tcp-erspan ] } [ policy-name [ classifier classifier-name ] ] [ chassis chassis-number slot slot-number ]

Views

Any view

Predefined user roles

network-admin

network-operator

mdc-admin

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

tcp-erspan: Specifies TCP ERSPAN-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 a card by its slot number. If you do not specify a card, this command displays the QoS policies for the active MPU. (In standalone mode.)

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

Usage guidelines

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

Examples

# Display all user-defined QoS policies.

<Sysname> display qos policy user-defined

User-defined QoS policy information:

Policy: 1 (ID 100)

Classifier: 1 (ID 100)

Behavior: 1

Marking:

Remark dscp 3

Committed Access Rate:

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

Green action : pass

Yellow action : pass

Red action : discard

Classifier: 2 (ID 101)

Behavior: 2

Accounting enable: Packet

Filter enable: Permit

Marking:

Remark dot1p 4

Classifier: 3 (ID 102)

Behavior: 3

-none-

# 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

# Display user-defined TCP ERSPAN-type QoS policies.

<Sysname> display qos policy user-defined tcp-erspan

User-defined QoS policy information:

TCP ERSPAN policy: 1 (ID 100)

Classifier: 1 (ID 100)

Behavior: 1

Mirroring:

Mirror to the interface: Ten-GigabitEthernet3/0/1

Table 6 Command output

Field	Description
User-defined QoS policy information	Information about a user-defined QoS policy.
System-defined QoS policy information	Information about a system-defined QoS policy.
Policy	User-defined QoS policy name.
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.
TCP ERSPAN policy	User-defined TCP ERSPAN-type QoS policy name.

For the description of other fields, see Table 1 .

display qos policy control-plane

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

Syntax

In standalone mode:‌

display qos policy control-plane slot slot-number

In IRF mode:

display qos policy control-plane chassis chassis-number slot slot-number

Views

Any view

Predefined user roles

network-admin

network-operator

mdc-admin

mdc-operator

Parameters

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

Examples

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

<Sysname> display qos policy control-plane slot 1

Control plane slot 1

Direction: Inbound

Policy: 1

Classifier: 1

Operator: AND

Rule(s) :

If-match acl 2000

Behavior: 1

Marking:

Remark dscp 3

Committed Access Rate:

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

Green action : pass

Yellow action : pass

Red action : discard

Green packets : 0 (Packets) 0 (Bytes)

Yellow packets: 0 (Packets) 0 (Bytes)

Red packets : 0 (Packets) 0 (Bytes)

Classifier: 2

Operator: AND

Rule(s) :

If-match protocol ipv6

Behavior: 2

Accounting enable:

0 (Packets), 0 (Bytes)

0 (pps), 0 (bps)

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 management

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

Syntax

display qos policy control-plane management

Views

Any view

Predefined user roles

network-admin

network-operator

mdc-admin

mdc-operator

Examples

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

<Sysname> display qos policy control-plane management

Control plane management

Direction: Inbound

Policy: a

Classifier: default-class

Matched : 0 (Packets) 0 (Bytes)

Operator: AND

Rule(s) :

If-match any

Behavior: be

-none-

Classifier: a

Matched : 3 (Packets) 180 (Bytes)

Operator: OR

Rule(s) :

If-match control-plane protocol arp

If-match control-plane protocol rip

If-match control-plane protocol-group critical

If-match acl 3001

If-match control-plane protocol bgp

If-match control-plane protocol bgp4+

If-match control-plane protocol ftp

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

Behavior: a

Committed Access Rate:

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

Green action : pass

Yellow action : pass

Red action : discard

Green packets : 3 (Packets) 180 (Bytes)

Yellow packets: 0 (Packets) 0 (Bytes)

Red packets : 0 (Packets) 0 (Bytes)

Table 8 Command output

Field	Description
Direction	Direction in which the QoS policy is applied.

For the description of other fields, see the display traffic classifier and display traffic behavior commands.

display qos policy control-plane management pre-defined

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

Syntax

display qos policy control-plane management pre-defined

Views

Any view

Predefined user roles

network-admin

network-operator

mdc-admin

mdc-operator

Examples

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

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

Pre-defined control plane policy management

Protocol Priority Bandwidth Group

Default N/A 100000 (bps) N/A

ARP N/A 128 (bps) normal

BGP N/A 256 (bps) critical

BGPv6 N/A 256 (bps) critical

HTTP N/A 512 (bps) management

HTTPS N/A 512 (bps) management

ICMP N/A 128 (bps) monitor

ICMPv6 N/A 128 (bps) monitor

OSPF Multicast N/A 256 (bps) critical

OSPF Unicast N/A 256 (bps) critical

OSPFv3 Multicast N/A 256 (bps) critical

OSFPv3 Unicast N/A 256 (bps) critical

RIP N/A 1024 (bps) critical

RIPng N/A 256 (bps) critical

SNMP N/A 512 (bps) management

SSH N/A 512 (bps) management

TELNET N/A 512 (bps) management

FTP N/A 512 (bps) management

TFTP N/A 512 (bps) management

Table 9 Command output

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

display qos policy control-plane pre-defined

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

Syntax

In standalone mode:‌

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

In IRF mode:

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

Views

Any view

Predefined user roles

network-admin

network-operator

mdc-admin

mdc-operator

Parameters

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

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

Examples

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

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

Pre-defined policy information slot 1

Protocol Priority Bandwidth Group

Default N/A 1000 (pps) N/A

IS-IS 18 1000 (pps) critical

VRRP 19 1000 (pps) important

OSPF Multicast 18 1000 (pps) critical

OSPF Unicast 18 1000 (pps) critical

IGMP 11 500 (pps) important

OSPFv3 Unicast 18 1000 (pps) critical

OSPFv3 Multicast 18 1000 (pps) critical

VRRPv6 19 1000 (pps) important

ARP 2 1000 (pps) normal

DHCP Snooping 10 300 (pps) redirect

DHCP 10 300 (pps) normal

802.1x 3 500 (pps) important

STP 17 300 (pps) critical

LACP 22 300 (pps) critical

MVRP 15 300 (pps) critical

BGP 16 1000 (pps) critical

ICMP 3 500 (pps) monitor

TTL Expires 5 300 (pps) monitor

IPOPTION 5 300 (pps) normal

BGPv6 16 1000 (pps) critical

Hop Limit Expires 5 300 (pps) monitor

IPOPTIONv6 5 300 (pps) normal

LLDP 14 300 (pps) important

DLDP 16 300 (pps) critical

TELNET 1 800 (pps) management

SSH 1 800 (pps) management

TACACS 1 800 (pps) management

RADIUS 1 800 (pps) management

HTTP 3 500 (pps) management

HTTPS 3 500 (pps) management

SNMP 4 800 (pps) management

ARP Snooping 2 1000 (pps) redirect

ICMPv6 3 300 (pps) monitor

DHCPv6 10 300 (pps) normal

BFD 21 1000 (pps) critical

Table 10 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 4.

display qos policy control-plane rule-statistics

Use display qos policy control-plane rule-statistics to display statistics for the QoS policy applied to a control plane.

Syntax

In standalone mode:‌

display qos policy control-plane slot slot-number rule-statistics

In IRF mode:

display qos policy control-plane chassis chassis-number slot slot-number rule-statistics

Views

Any view

Predefined user roles

network-admin

network-operator

mdc-admin

mdc-operator

Parameters

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

In IRF mode:‌

Usage guidelines

This command displays traffic statistics for an ACL match criterion on a per-rule basis. To display the traffic statistics, you must execute the accounting command in the traffic behavior to configure a traffic accounting action.

Examples

# (In standalone mode.) ‌Display statistics for the QoS policy applied to the control plane in slot 0.In standalone mode:‌

<Sysname> display qos policy control-plane slot 0 rule-statistics

Control plane slot 0

Direction: Inbound, Policy: p1, Status: Succeed

Classifier: c1, Operator: AND, Behavior: b1, State: Succeed

Accounting: Enabled, Car: Enabled

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

if-match source-mac 0001-0001-0001

if-match local-precedence 1

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

if-match acl 3000

rule 0 permit ip source 1.1.1.1 0

Passed packets 500, Passed pps 5

Dropped packets 500, Dropped pps 5

Passed bytes 5000, Passed bps 50

Dropped bytes 5000, Dropped bps 50

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

if-match acl 3000

rule 5 permit ip destination 2.2.2.2 0

Passed packets 500, Passed pps 5

Dropped packets 500, Dropped pps 5

Passed bytes 5000, Passed bps 50

Dropped bytes 5000, Dropped bps 50

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

Table 11 Command output

Field	Description
Direction	Direction in which the QoS policy is applied.
Status	QoS policy application result: · Succeed—The QoS policy is applied successfully. · Failed—The QoS policy fails to be applied. The statistics cannot be displayed.
Operator	Logical relationship between match criteria. Options include: · AND—A packet is counted only if it matches all match criteria configured by using if-match commands in a traffic class. The logical relationship between ACL rules in an ACL match criterion configured by using an if-match acl command is OR. · OR—A packet is counted if it matches any one of the match criteria configured by using if-match commands in a traffic class.
State	State of the class-behavior association: · Succeed—The class-behavior association is normal. · Failed—The class-behavior association is abnormal. For example, the traffic class contains match criteria that cannot both take effect or the traffic behavior contains conflicting actions. If the class-behavior association is abnormal, the statistics cannot be displayed.
Accounting	Indicates whether a traffic accounting action is configured in the traffic behavior. If a traffic accounting action is not configured, the traffic statistics cannot be displayed.
Car	Indicates whether a traffic policing action is configured in the traffic behavior. If a traffic policing action is not configured, the traffic statistics cannot be displayed.
Passed packets	Total number of forwarded packets. This field is displayed only if the accounting packet command is executed in the traffic behavior.
Passed bytes	Total number of forwarded bytes. This field is displayed only if the accounting byte command is executed in the traffic behavior.
Passed pps	Number of packets forwarded per second. This field is displayed only if the accounting packet command is executed in the traffic behavior.
Passed bps	Number of bytes forwarded per second. This field is displayed only if the accounting byte command is executed in the traffic behavior.
Dropped packets	Total number of dropped packets. This field is displayed only if the accounting packet command is executed in the traffic behavior.
Dropped bytes	Total number of forwarded bytes. This field is displayed only if the accounting byte command is executed in the traffic behavior.
Dropped pps	Number of packets dropped per second. This field is displayed only if the accounting packet command is executed in the traffic behavior.
Dropped bps	Number of bytes dropped per second. This field is displayed only if the accounting byte command is executed in the traffic behavior.

Related commands

accounting

qos apply policy (control plane view)

display qos policy global

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

Syntax

In standalone mode:‌

In IRF mode:

Views

Any view

Predefined user roles

network-admin

network-operator

mdc-admin

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

tcp-erspan: Specifies TCP ERSPAN-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 a card by its slot number. If you do not specify a card, this command displays global QoS policies for the active MPU. (In standalone mode.)

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

Usage guidelines

If you do not specify the ipv6-matching, accounting, mirroring, remarking, or tcp-erspan 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 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

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

# Display information about TCP ERSPAN-matching QoS policies applied globally.

<Sysname> display qos tcp-erspan policy global

Direction: Inbound

TCP ERSPAN policy: 1

Classifier: 1

Operator: AND

Rule(s) :

If-match acl 3000

Behavior: 1

Mirroring:

Mirror to the interface: Ten-GigabitEthernet3/0/1

Table 12 Command output

Field	Description
Direction	Direction in which the QoS policy is applied.
Policy	User-defined 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.
TCP ERSPAN policy	User-defined TCP ERSPAN-type QoS policy name.

For the description of other fields, see Table 1 .

display qos policy global rule-statistics

Use display qos policy global rule-statistics to display statistics for QoS policies applied globally.

Syntax

In standalone mode:‌

In IRF mode:

Views

Any view

Predefined user roles

network-admin

network-operator

mdc-admin

mdc-operator

Parameters

ipv6-matching: Specifies the IPv6 matching-type QoS policy.

accounting: Specifies the accounting-type QoS policy.

mirroring: Specifies the mirroring-type QoS policy.

remarking: Specifies the marking-type QoS policy.

tcp-erspan: Specifies the TCP ERSPAN-type QoS policy.

inbound: Specifies the inbound direction.

outbound: Specifies the outbound direction.

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

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

Usage guidelines

If you do not specify a direction, this command displays statistics for QoS policies applied in each direction.

Examples

# (In standalone mode.) ‌Display statistics for the QoS policies applied globally in the inbound direction in slot 0.In standalone mode:‌

<Sysname> display qos policy global slot 0 inbound rule-statistics

Slot 0

Direction: Inbound, Policy: p1, Status: Succeed

Classifier: c1, Operator: AND, Behavior: b1, State: Succeed

Accounting: Enabled, Car: Enabled

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

if-match source-mac 0001-0001-0001

if-match local-precedence 1

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

if-match acl 3000

rule 0 permit ip source 1.1.1.1 0

Passed packets 500, Passed pps 5

Dropped packets 500, Dropped pps 5

Passed bytes 5000, Passed bps 50

Dropped bytes 5000, Dropped bps 50

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

if-match acl 3000

rule 5 permit ip destination 2.2.2.2 0

Passed packets 500, Passed pps 5

Dropped packets 500, Dropped pps 5

Passed bytes 5000, Passed bps 50

Dropped bytes 5000, Dropped bps 50

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

Table 13 Command output

Field	Description
Direction	Direction in which the QoS policy is applied.
Status	QoS policy application result: · Succeed—The QoS policy is applied successfully. · Failed—The QoS policy fails to be applied. The statistics cannot be displayed.
Operator	Logical relationship between match criteria. Options include: · AND—A packet is counted only if it matches all match criteria configured by using if-match commands in a traffic class. The logical relationship between ACL rules in an ACL match criterion configured by using an if-match acl command is OR. · OR—A packet is counted if it matches any one of the match criteria configured by using if-match commands in a traffic class.
State	State of the class-behavior association: · Succeed—The class-behavior association is normal. · Failed—The class-behavior association is abnormal. For example, the traffic class contains match criteria that cannot both take effect or the traffic behavior contains conflicting actions. If the class-behavior association is abnormal, the statistics cannot be displayed.
Accounting	Indicates whether a traffic accounting action is configured in the traffic behavior. If a traffic accounting action is not configured, the traffic statistics cannot be displayed.
Car	Indicates whether a traffic policing action is configured in the traffic behavior. If a traffic policing action is not configured, the traffic statistics cannot be displayed.
Passed packets	Total number of forwarded packets. This field is displayed only if the accounting packet command is executed in the traffic behavior.
Passed bytes	Total number of forwarded bytes. This field is displayed only if the accounting byte command is executed in the traffic behavior.
Passed pps	Number of packets forwarded per second. This field is displayed only if the accounting packet command is executed in the traffic behavior.
Passed bps	Number of bytes forwarded per second. This field is displayed only if the accounting byte command is executed in the traffic behavior.
Dropped packets	Total number of dropped packets. This field is displayed only if the accounting packet command is executed in the traffic behavior.
Dropped bytes	Total number of forwarded bytes. This field is displayed only if the accounting byte command is executed in the traffic behavior.
Dropped pps	Number of packets dropped per second. This field is displayed only if the accounting packet command is executed in the traffic behavior.
Dropped bps	Number of bytes dropped per second. This field is displayed only if the accounting byte command is executed in the traffic behavior.

Related commands

accounting

qos apply policy global

display qos policy interface

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

Syntax

In standalone mode:‌

In IRF mode:

Views

Any view

Predefined user roles

network-admin

network-operator

mdc-admin

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

tcp-erspan: Specifies TCP ERSPAN-type QoS policies.

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

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

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

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, remarking, or tcp-erspan 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 QoS policy applied to the incoming traffic of Ten-GigabitEthernet 3/0/1.

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

Interface: Ten-GigabitEthernet3/0/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

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

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 Ten-GigabitEthernet 3/0/1.

<Sysname> display qos accounting policy interface ten-gigabitethernet 3/0/1 inbound

Interface: Ten-GigabitEthernet3/0/1

Direction: Inbound

Accounting Policy: 1

Classifier: 1

Operator: AND

Rule(s) :

If-match acl 2000

Behavior: 1

Accounting enable:

0 (Packets), 0 (Bytes)

0 (pps), 0 (bps)

# Display information about the marking-type QoS policy applied to the incoming traffic of Ten-GigabitEthernet 3/0/1.

<Sysname> display qos remarking policy interface ten-gigabitethernet 3/0/1 inbound

Interface: Ten-GigabitEthernet3/0/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 Ten-GigabitEthernet 3/0/1.

<Sysname> display qos mirroring policy interface ten-gigabitethernet 3/0/1 inbound

Interface: Ten-GigabitEthernet3/0/1

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 the TCP ERSPAN-type QoS policy applied to the incoming traffic of Ten-GigabitEthernet 3/0/1.

<Sysname> display qos tcp-erspan policy interface ten-gigabitethernet 3/0/1 inbound

Interface: Ten-GigabitEthernet3/0/1

Direction: Inbound

TCP ERSPAN policy: 1

Classifier: 1

Operator: AND

Rule(s) :

If-match acl 2000

Behavior: 1

Mirroring:

Mirror to the interface: Ten-GigabitEthernet3/0/2

# Display the QoS policies applied to all interfaces.

<Sysname> display qos policy interface

Interface: Ten-GigabitEthernet3/0/1

Direction: Inbound

Mode : Share

Policy: a

Classifier: a

Operator: AND

Rule(s) :

If-match any

Behavior: a

Mirroring:

Mirror to the interface: Ten-GigabitEthernet3/0/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: Ten-GigabitEthernet3/0/3

Direction: Inbound

Policy: b

Classifier: b

Operator: AND

Rule(s) :

If-match any

Behavior: b

Committed Access Rate:

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

Green action : pass

Yellow action : pass

Red action : discard

Green packets : 0(Packets)

Red packets : 0 (Packets)

Interface: Ten-GigabitEthernet3/0/4

Direction: Inbound

Mode : Share

Policy: a

Classifier: a

Operator: AND

Rule(s) :

If-match any

Behavior: a

Mirroring:

Mirror to the interface: Ten-GigabitEthernet3/0/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.
Policy	User-defined 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.
TCP ERSPAN policy	User-defined TCP ERSPAN-type QoS policy name.
Mode	Sharing mode for QoS and ACL resources. This field appears only if a QoS policy is applied with the share-mode keyword.
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 are available only if an accounting action has been configured. Traffic statistics for green packets.
Yellow packets	Traffic statistics are available only if an accounting action has been configured. Traffic statistics for yellow packets.
Red packets	Traffic statistics are available only if an accounting action has been configured. Traffic statistics for red packets.

display qos policy interface rule-statistics

Use display qos policy interface rule-statistics to display statistics for QoS policies applied to interfaces.

Syntax

In standalone mode:‌

In IRF mode:

Views

Any view

Predefined user roles

network-admin

network-operator

mdc-admin

mdc-operator

Parameters

ipv6-matching: Specifies the IPv6 matching-type QoS policy.

accounting: Specifies the accounting-type QoS policy.

mirroring: Specifies the mirroring-type QoS policy.

remarking: Specifies the marking-type QoS policy.

tcp-erspan: Specifies the TCP ERSPAN-type QoS policy.

interface-type interface-number: Specifies an interface by its type and number. If you do not specify an interface, this command displays statistics for QoS policies applied to each interface.

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

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

inbound: Specifies the inbound direction.

outbound: Specifies the outbound direction.

Usage guidelines

If you do not specify a direction, this command displays statistics for QoS policies applied in each direction.

Examples

# (In standalone mode.) ‌Display statistics for the QoS policies applied to the inbound direction of each interface in slot 1.In standalone mode:‌

<Sysname> display qos policy global slot 1 inbound rule-statistics

Slot 1

Interface: GigabitEthernet1/0/1

Direction: Inbound, Policy: p1, Status: Succeed

Classifier: c1, Operator: AND, Behavior: b1, State: Succeed

Accounting: Enabled, Car: Enabled

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

if-match source-mac 0001-0001-0001

if-match local-precedence 1

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

if-match acl 3000

rule 0 permit ip source 1.1.1.1 0

Passed packets 500, Passed pps 5

Dropped packets 500, Dropped pps 5

Passed bytes 5000, Passed bps 50

Dropped bytes 5000, Dropped bps 50

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

if-match acl 3000

rule 5 permit ip destination 2.2.2.2 0

Passed packets 500, Passed pps 5

Dropped packets 500, Dropped pps 5

Passed bytes 5000, Passed bps 50

Dropped bytes 5000, Dropped bps 50

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

Table 15 Command output

Field	Description
Direction	Direction in which the QoS policy is applied.
Status	QoS policy application result: · Succeed—The QoS policy is applied successfully. · Failed—The QoS policy fails to be applied. The statistics cannot be displayed.
Operator	Logical relationship between match criteria. Options include: · AND—A packet is counted only if it matches all match criteria configured by using if-match commands in a traffic class. The logical relationship between ACL rules in an ACL match criterion configured by using an if-match acl command is OR. · OR—A packet is counted if it matches any one of the match criteria configured by using if-match commands in a traffic class.
State	State of the class-behavior association: · Succeed—The class-behavior association is normal. · Failed—The class-behavior association is abnormal. For example, the traffic class contains match criteria that cannot both take effect or the traffic behavior contains conflicting actions. If the class-behavior association is abnormal, the statistics cannot be displayed.
Accounting	Indicates whether a traffic accounting action is configured in the traffic behavior. If a traffic accounting action is not configured, the traffic statistics cannot be displayed.
Car	Indicates whether a traffic policing action is configured in the traffic behavior. If a traffic policing action is not configured, the traffic statistics cannot be displayed.
Passed packets	Total number of forwarded packets. This field is displayed only if the accounting packet command is executed in the traffic behavior.
Passed bytes	Total number of forwarded bytes. This field is displayed only if the accounting byte command is executed in the traffic behavior.
Passed pps	Number of packets forwarded per second. This field is displayed only if the accounting packet command is executed in the traffic behavior.
Passed bps	Number of bytes forwarded per second. This field is displayed only if the accounting byte command is executed in the traffic behavior.
Dropped packets	Total number of dropped packets. This field is displayed only if the accounting packet command is executed in the traffic behavior.
Dropped bytes	Total number of forwarded bytes. This field is displayed only if the accounting byte command is executed in the traffic behavior.
Dropped pps	Number of packets dropped per second. This field is displayed only if the accounting packet command is executed in the traffic behavior.
Dropped bps	Number of bytes dropped per second. This field is displayed only if the accounting byte command is executed in the traffic behavior.

Related commands

accounting

qos apply policy (interface view)

display qos policy l2vpn-ac

Use display qos policy l2vpn-ac to display the QoS policies applied to Ethernet service instances.

Syntax

In standalone mode:‌

display qos [ ipv6-matching | accounting | mirroring | remarking ] policy l2vpn-ac [ interface interface-type interface-number [ service-instance instance-id ] [ slot slot-number ] ] [ inbound ]

In IRF mode:

display qos [ ipv6-matching | accounting | mirroring | remarking ] policy l2vpn-ac [ interface interface-type interface-number [ service-instance instance-id ] [ chassis chassis-number slot slot-number ] ] [ inbound ]

Views

Any view

Predefined user roles

network-admin

network-operator

mdc-admin

mdc-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 interface-type interface-number: Specifies an interface by its type and number. If you do not specify an interface, this command displays QoS policies applied to Ethernet service instances on all interfaces.

service-instance instance-id: Specifies an Ethernet service instance by its ID in the range of 1 to 4096. If you do not specify an Ethernet service instance, this command displays QoS policies applied to all Ethernet service instances on an interface.

slot slot-number: Specifies a card by its slot number. If you do not specify a card, this command displays QoS policy information for all cards. Only Layer 2 aggregate interfaces support this option. (In standalone mode.)

chassis chassis-number slot slot-number: Specifies a card on an IRF member device. The chassis-number argument represents the member ID of the IRF member device. The slot-number argument represents the slot number of the card. If you do not specify this option, the command displays QoS policy information for all cards. Only Layer 2 aggregate interfaces support this option. (In IRF mode.) ‌

inbound: Specifies the QoS policies applied to incoming traffic. If you do not specify this keyword, the command execution results are the same.

Examples

# Display the QoS policy applied to the incoming traffic of Ethernet service instance 1 on Ten-GigabitEthernet 3/0/1.

<Sysname> display qos policy l2vpn-ac interface ten-gigabitethernet 3/0/1 service-instance 1 inbound

Interface: Ten-GigabitEthernet3/0/1 Service instance ID: 1

Direction: Inbound

Policy: p

Classifier: c

Operator: AND

Rule(s) :

If-match any

Behavior: b

Committed Access Rate:

CIR 88 (kbps), CBS 5632 (Bytes), EBS 0 (Bytes)

Green action : pass

Yellow action : pass

Red action : discard

Green packets : 0 (Packets)

Red packets : 0 (Packets)

Table 16 Command output

Field	Description
Direction	Direction in which the QoS policy is applied.
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 l2vpn-ac rule-statistics

Use display qos policy l2vpn-ac rule-statistics to display statistics for QoS policies applied to Ethernet service instances.

Syntax

In standalone mode:‌

display qos [ ipv6-matching | accounting | mirroring | remarking ] policy l2vpn-ac [ interface interface-type interface-number [ service-instance instance-id ] [ slot slot-number ] ] [ inbound | outbound ] rule-statistics

In IRF mode:

Views

Any view

Predefined user roles

network-admin

network-operator

mdc-admin

mdc-operator

Parameters

ipv6-matching: Specifies the IPv6 matching-type QoS policy.

accounting: Specifies the accounting-type QoS policy.

mirroring: Specifies the mirroring-type QoS policy.

remarking: Specifies the marking-type QoS policy.

interface interface-type interface-number: Specifies an interface by its type and number. If you do not specify an interface, this command displays statistics for QoS policies applied to Ethernet service instances on each interface.

service-instance instance-id: Specifies an Ethernet service instance by its ID in the range of 1 to 4094. If you do not specify an Ethernet service instance, this command displays statistics for QoS policies applied to each Ethernet service instance.

slot slot-number: Specifies a card by its slot number. If you do not specify a card, this command displays Ethernet service instance-based QoS policy statistics for each card. (In standalone mode.)

chassis chassis-number slot slot-number: Specifies a card on an IRF member device. The chassis-number argument represents the member ID of the IRF member device. The slot-number argument represents the slot number of the card. If you do not specify this option, the command displays Ethernet service instance-based QoS policy statistics for each card. (In IRF mode.) ‌

inbound: Specifies the inbound direction.

outbound: Specifies the outbound direction.

Usage guidelines

If you do not specify a direction, this command displays statistics for QoS policies applied in each direction.

Examples

# (In standalone mode.) ‌Display statistics for QoS policies applied to each Ethernet service instance on Ten-GigabitEthernet 3/0/1 in slot 1Ten-GigabitEthernet3/0/1.In standalone mode:‌

<Sysname> display qos policy l2vpn-ac interface ten-gigabitethernet 3/0/1 slot 1 inbound rule-statistics

Slot 1

Interface: Ten-GigabitEthernet3/0/1 Service instance ID: 1

Direction: Inbound, Policy: p1, Status: Succeed

Classifier: c1, Operator: AND, Behavior: b1, State: Succeed

Accounting: Enabled, Car: Enabled

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

if-match source-mac 0001-0001-0001

if-match local-precedence 1

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

if-match acl 3000

rule 0 permit ip source 1.1.1.1 0

Passed packets 500, Passed pps 5

Dropped packets 500, Dropped pps 5

Passed bytes 5000, Passed bps 50

Dropped bytes 5000, Dropped bps 50

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

if-match acl 3000

rule 5 permit ip destination 2.2.2.2 0

Passed packets 500, Passed pps 5

Dropped packets 500, Dropped pps 5

Passed bytes 5000, Passed bps 50

Dropped bytes 5000, Dropped bps 50

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

Table 17 Command output

Field	Description
Service instance ID	Ethernet service instance ID.
Direction	Direction in which the QoS policy is applied.
Status	QoS policy application result: · Succeed—The QoS policy is applied successfully. · Failed—The QoS policy fails to be applied. The statistics cannot be displayed.
Operator	Logical relationship between match criteria. Options include: · AND—A packet is counted only if it matches all match criteria configured by using if-match commands in a traffic class. The logical relationship between ACL rules in an ACL match criterion configured by using an if-match acl command is OR. · OR— A packet is counted if it matches any one of the match criteria configured by using if-match commands in a traffic class.
State	State of the class-behavior association: · Succeed—The class-behavior association is normal. · Failed—The class-behavior association is abnormal. For example, the traffic class contains match criteria that cannot both take effect or the traffic behavior contains conflicting actions. If the class-behavior association is abnormal, the statistics cannot be displayed.
Accounting	Indicates whether a traffic accounting action is configured in the traffic behavior. If a traffic accounting action is not configured, the traffic statistics cannot be displayed.
Car	Indicates whether a traffic policing action is configured in the traffic behavior. If a traffic policing action is not configured, the traffic statistics cannot be displayed.
Passed packets	Total number of forwarded packets. This field is displayed only if the accounting packet command is executed in the traffic behavior.
Passed bytes	Total number of forwarded bytes. This field is displayed only if the accounting byte command is executed in the traffic behavior.
Passed pps	Number of packets forwarded per second. This field is displayed only if the accounting packet command is executed in the traffic behavior.
Passed bps	Number of bytes forwarded per second. This field is displayed only if the accounting byte command is executed in the traffic behavior.
Dropped packets	Total number of dropped packets. This field is displayed only if the accounting packet command is executed in the traffic behavior.
Dropped bytes	Total number of forwarded bytes. This field is displayed only if the accounting byte command is executed in the traffic behavior.
Dropped pps	Number of packets dropped per second. This field is displayed only if the accounting packet command is executed in the traffic behavior.
Dropped bps	Number of bytes dropped per second. This field is displayed only if the accounting byte command is executed in the traffic behavior.

Related commands

accounting

qos apply policy (Ethernet service instance view)

display qos vlan-policy

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

Syntax

In standalone mode:‌

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

In IRF mode:

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

Views

Any view

Predefined user roles

network-admin

network-operator

mdc-admin

mdc-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 a card by its slot number. If you do not specify a card, this command displays QoS policies applied to VLANs for the active MPU. (In standalone mode.)

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

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

Classifier: 2

Operator: AND

Rule(s) :

If-match protocol ipv6

Behavior: 2

Filter enable: Permit

Marking:

Remark dscp 3

Classifier: 3

Operator: AND

Rule(s) :

-none-

Behavior: 3

-none-

Table 18 Command output

Field	Description
Direction	Direction in which the QoS policy is applied.

display qos vlan-policy rule-statistics

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

Syntax

In standalone mode:‌

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

In IRF mode:

display qos vlan-policy vlan [ vlan-id ] [ chassis chassis-number slot slot-number ] [ inbound | outbound ] rule-statistics

Views

Any view

Predefined user roles

network-admin

network-operator

mdc-admin

mdc-operator

Parameters

vlan vlan-id: Specifies a VLAN by its ID. The value range for the vlan-id argument is 1 4094.

inbound: Specifies the inbound direction.

outbound: Specifies the outbound direction.

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

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

Usage guidelines

If you do not specify a direction, this command displays statistics for QoS policies applied in each direction.

Examples

# (In standalone mode.) ‌Display statistics for the QoS policy applied to the inbound direction of VLAN 10 in slot 1.In standalone mode:‌

<Sysname> display qos vlan-policy vlan 10 slot 1 inbound rule-statistics

Slot 0

Vlan 10

Direction: Inbound, Policy: p1, Status: Succeed

Classifier: c1, Operator: AND, Behavior: b1, State: Succeed

Accounting: Enabled, Car: Enabled

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

if-match source-mac 0001-0001-0001

if-match local-precedence 1

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

if-match acl 3000

rule 0 permit ip source 1.1.1.1 0

Passed packets 500, Passed pps 5

Dropped packets 500, Dropped pps 5

Passed bytes 5000, Passed bps 50

Dropped bytes 5000, Dropped bps 50

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

if-match acl 3000

rule 5 permit ip destination 2.2.2.2 0

Passed packets 500, Passed pps 5

Dropped packets 500, Dropped pps 5

Passed bytes 5000, Passed bps 50

Dropped bytes 5000, Dropped bps 50

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

Table 19 Command output

Field	Description
Direction	Direction in which the QoS policy is applied.
Status	QoS policy application result: · Succeed—The QoS policy is applied successfully. · Failed—The QoS policy fails to be applied. The statistics cannot be displayed.
Operator	Logical relationship between match criteria. Options include: · AND—A packet is counted only if it matches all match criteria configured by using if-match commands in a traffic class. The logical relationship between ACL rules in an ACL match criterion configured by using an if-match acl command is OR. · OR—A packet is counted if it matches any one of the match criteria configured by using if-match commands in a traffic class.
State	State of the class-behavior association: · Succeed—The class-behavior association is normal. · Failed—The class-behavior association is abnormal. For example, the traffic class contains match criteria that cannot both take effect or the traffic behavior contains conflicting actions. If the class-behavior association is abnormal, the statistics cannot be displayed.
Accounting	Indicates whether a traffic accounting action is configured in the traffic behavior. If a traffic accounting action is not configured, the traffic statistics cannot be displayed.
Car	Indicates whether a traffic policing action is configured in the traffic behavior. If a traffic policing action is not configured, the traffic statistics cannot be displayed.
Passed packets	Total number of forwarded packets. This field is displayed only if the accounting packet command is executed in the traffic behavior.
Passed bytes	Total number of forwarded bytes. This field is displayed only if the accounting byte command is executed in the traffic behavior.
Passed pps	Number of packets forwarded per second. This field is displayed only if the accounting packet command is executed in the traffic behavior.
Passed bps	Number of bytes forwarded per second. This field is displayed only if the accounting byte command is executed in the traffic behavior.
Dropped packets	Total number of dropped packets. This field is displayed only if the accounting packet command is executed in the traffic behavior.
Dropped bytes	Total number of forwarded bytes. This field is displayed only if the accounting byte command is executed in the traffic behavior.
Dropped pps	Number of packets dropped per second. This field is displayed only if the accounting packet command is executed in the traffic behavior.
Dropped bps	Number of bytes dropped per second. This field is displayed only if the accounting byte command is executed in the traffic behavior.

Related commands

accounting

qos vlan-policy

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

Use qos apply policy to apply a QoS policy to a control plane, control-plane management view, Ethernet service instance or interface.

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

Syntax

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

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

Default

No QoS policy is applied.

Views

Control plane view/control-plane management view

Ethernet service instance view

Interface view

Predefined user roles

network-admin

mdc-admin

Parameters

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

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

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

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

tcp-erspan: Specifies a TCP ERSPAN-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 Ethernet service instance view or VSI 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.

For configuration commands for Ethernet service instances, see MPLS L2VPN or VPLS in MPLS Command Reference or see VXLAN Command Reference.

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.

The longest-match keyword is supported only when a QoS policy is applied to an interface, a VSI, or the inbound direction of an Ethernet service instance.

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

· All interfaces on an interface module 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.

· Only SF interface modules support the share-mode keyword.

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 tasks:

1. Remove the QoS policy from the interface.

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

A maximum of six QoS policies (one for each type) can be applied to one 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.

For LSCM2XPG24SF0 and LSCM2XPT24SF0 cards, ONU interfaces do not support QoS policies and packet filtering, and OLT interfaces and ONU subinterfaces support QoS policies and packet filtering.

If you apply a QoS policy to a tunnel interface on an SF interface module, it takes effect only when the tunnel interface is one of the following tunnel modes:

· IPv4 VXLAN.

· IPv6 VXLAN.

· IPv4 VXLAN-DCI.

· IPv6 VXLAN-DCI.

Examples

# Apply QoS policy TEST1 to the outgoing traffic of Ten-GigabitEthernet 3/0/1.

<Sysname> system-view

[Sysname] interface ten-gigabitethernet 3/0/1

[Sysname-Ten-GigabitEthernet3/0/1] qos apply policy TEST1 outbound

# Apply accounting-type QoS policy TEST2 to the outgoing traffic of Ten-GigabitEthernet 3/0/1.

<Sysname> system-view

[Sysname] interface ten-gigabitethernet 3/0/1

[Sysname-Ten-GigabitEthernet3/0/1] qos apply accounting policy TEST2 outbound

# Apply mirroring-type QoS policy TEST3 to the outgoing traffic of Ten-GigabitEthernet 3/0/1.

<Sysname> system-view

[Sysname] interface ten-gigabitethernet 3/0/1

[Sysname-Ten-GigabitEthernet3/0/1] qos apply mirroring policy TEST3 outbound

# Apply marking-type QoS policy TEST4 to the outgoing traffic of Ten-GigabitEthernet 3/0/1.

<Sysname> system-view

[Sysname] interface ten-gigabitethernet 3/0/1

[Sysname-Ten-GigabitEthernet3/0/1] qos apply remarking policy TEST4 outbound

# Apply TCP ERSPAN-type QoS policy TEST4 to the outgoing traffic of Ten-GigabitEthernet 3/0/1.

[Sysname] interface ten-gigabitethernet 3/0/1

[Sysname-Ten-GigabitEthernet3/0/1] qos apply tcp-erspan policy TEST4 outbound

# Apply 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 TEST9 to the incoming traffic of Ethernet service instance 200.

<Sysname> system-view

[Sysname] interface ten-gigabitethernet 3/0/1

[Sysname-Ten-GigabitEthernet3/0/1] service-instance 200

[Sysname-Ten-GigabitEthernet3/0/1-srv200] qos apply policy TEST9 inbound

# Apply IPv6-matching QoS policy TEST13 to the outgoing traffic of Ten-GigabitEthernet 3/0/1.

<Sysname> system-view

[Sysname] interface ten-gigabitethernet 3/0/1

[Sysname-Ten-GigabitEthernet3/0/1] qos apply ipv6-matching policy TEST13 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 | tcp-erspan ] policy policy-name global { inbound | outbound } [ longest-match ]

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

Default

No QoS policy is applied globally.

Views

System view

Predefined user roles

network-admin

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

tcp-erspan: Specifies a TCP ERSPAN-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 six QoS policies (one generic, one IPv6-matching, one accounting-type, one mirroring-type, one marking-type, and one TCP ERSPAN-type) can be applied to one direction globally.

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

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 | tcp-erspan ] policy policy-name

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

Default

No QoS policies exist.

Views

System view

Predefined user roles

network-admin

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

tcp-erspan: Identifies the QoS policy as a TCP ERSPAN 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, remarking, or tcp-erspan 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, remarking, or tcp-erspan 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, Ethernet service instances, or globally and is used for traffic classes containing IPv6 ACL match criteria. An accounting-type QoS policy can be applied to only interfaces, Ethernet service instances, or globally and can contain only class-based accounting actions. A mirroring-type QoS policy can only be applied to interfaces, Ethernet service instances, or globally and can contain only mirroring actions. A marking-type QoS policy can be applied to only interfaces ,Ethernet service instances, or globally and can contain only marking actions. A TCP ERSPAN-type QoS policy can be applied to only interfaces or globally and can contain only ERSPAN actions.

In a TCP ERSPAN-type QoS policy, a traffic class matches TCP flags (including ACK, FIN, PSH, RST, SYN, and URG), and a traffic behavior contains an ERSPAN action. For more information about flow mirroring ERSPAN, see Network Management and Monitoring Configuration Guide.

To perform both flow mirroring and rate limiting for traffic, you can configure a generic QoS policy to rate limit traffic and configure a TCP ERSPAN-type QoS policy to perform flow mirroring for traffic. The two types of QoS policies are independent of each other in hardware resources.

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

Examples

# Create a QoS policy named user1.

<Sysname> system-view

[Sysname] qos policy user1

[Sysname-qospolicy-user1]

# 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

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

Usage guidelines

You can apply a QoS policy to one direction of a VLAN in either extended mode or common mode, but not both. A QoS policy applied in extended mode uses more hardware resources but supports limited parameters.

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

In standalone mode:‌

reset qos policy control-plane slot slot-number

In IRF mode:

reset qos policy control-plane chassis chassis-number slot slot-number

Views

User view

Predefined user roles

network-admin

mdc-admin

Parameters

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

Examples

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

<Sysname> reset qos policy control-plane slot 1

reset qos policy control-plane management

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

Syntax

reset qos policy control-plane management

Views

User view

Predefined user roles

network-admin

mdc-admin

Examples

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

<Sysname> reset qos policy control-plane management

reset qos policy global

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

Syntax

Views

User view

Predefined user roles

network-admin

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

tcp-erspan: Specifies TCP ERSPAN-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, remarking, or tcp-erspan keyword, this command clears statistics for generic QoS policies.

Examples

# Clear statistics for the 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 policy l2vpn-ac

Use reset qos policy l2vpn-ac to clear the QoS policies applied to Ethernet service instances.

Syntax

reset qos [ ipv6-matching | accounting | mirroring | remarking ]policy l2vpn-ac [ interface interface-type interface-number [ service-instance instance-id ] ] [ inbound ]

Views

User view

Predefined user roles

network-admin

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

interface interface-type interface-number: Specifies an interface by its type and number. If you do not specify an interface, this command clears QoS policies applied to Ethernet service instances on all interfaces.

service-instance instance-id: Specifies an Ethernet service instance by its ID in the range of 1 to 4096. If you do not specify an Ethernet service instance, this command clears QoS policies applied to all Ethernet service instances on an interface.

inbound: Specifies the QoS policies applied to incoming traffic.

Examples

# Clear the QoS policies applied to the inbound direction of Ethernet service instance 1 on Ten-GigabitEthernet 3/0/1.

<Sysname> reset qos policy l2vpn-ac interface ten-gigabitethernet 3/0/1 service-instance 1 inbound

# Clear the IPv6-matching QoS policy applied to the inbound direction of Ethernet service instance 1 on Ten-GigabitEthernet 3/0/1.

<Sysname> reset qos ipv6-matching policy l2vpn-ac interface ten-gigabitethernet 3/0/1 service-instance 1 inbound

Related commands

display qos policy l2vpn-ac

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

mdc-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

mdc-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

mdc-admin

mdc-operator

Parameters

The device provides the following types of priority map.

Table 20 Priority maps

Priority mapping	Description
dot1p-dp	802.1p-drop priority map.
dot1p-lp	802.1p-local priority map.
dscp-dp	DSCP-drop priority map.
dscp-lp	DSCP-local priority map.
dscp-dscp	DSCP-DSCP priority map.
exp-lp	EXP-local priority map.
lp-exp	Local-EXP 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 21 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.

display qos map-table color

Use display qos map-table color to display the configuration of a colored priority map.

Syntax

display qos map-table color [ green | yellow | red ] [ lp-tunnel-dscp ]

Views

Any view

Predefined user roles

network-admin

network-operator

mdc-admin

mdc-operator

Parameters

green: Specifies green packets.

yellow: Specifies yellow packets.

red: Specifies red packets.

The device provides the following types of priority map.

Table 22 Priority maps

Priority mapping	Description
lp-tunnel-dscp	Local-outer DSCP priority map. This map is used for packets forwarded through a VXLAN tunnel or VXLAN-DCI tunnel. This map must be used together with the qos vxlan-dci-tunnel outer dscp or vxlan-tunnel outer dscp command (see VXLAN Command Reference). After the command is executed, this map applies to all VXLAN packets.

Priority mapping

Description

lp-tunnel-dscp

Local-outer DSCP priority map. This map is used for packets forwarded through a VXLAN tunnel or VXLAN-DCI tunnel.

This map must be used together with the qos vxlan-dci-tunnel outer dscp or vxlan-tunnel outer dscp command (see VXLAN Command Reference). After the command is executed, this map applies to all VXLAN packets.

‌

Usage guidelines

Packets processed by traffic policing are colored green, yellow, or red. To perform priority mapping for packets in different colors, the device provides colored priority maps, each of which is a priority map specific to a color. For how traffic policing processes and colors packets, see ACL and QoS Configuration Guide.

If you do not specify a color, this command displays the configuration of priority maps for all three colors.

If you do not specify a direction, this command displays the configuration of the inbound and outbound priority maps.

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

Examples

# Display the configuration of the local-outer DSCP priority map for green packets.

<Sysname> display qos map-table color green lp-tunnel-dscp

MAP-TABLE NAME: lp-tunnel-dscp TYPE: pre-define COLOR: green

IMPORT : EXPORT

0 : 3

1 : 7

2 : 11

3 : 15

4 : 19

5 : 23

6 : 27

7 : 31

8 : 35

9 : 39

10 : 43

11 : 47

12 : 51

13 : 55

14 : 59

15 : 63

Table 23 Command output

Field	Description
MAP-TABLE NAME	Priority map name.
TYPE	Priority map type.
COLOR	Priority map color.
DIRECTION	Direction of the priority map.
IMPORT	Input values of the priority map.
EXPORT	Output values of the priority map.

Related commands

vxlan-dci-tunnel outer dscp (VXLAN Command Reference)

vxlan-tunnel outer dscp (VXLAN Command Reference)

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

mdc-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-lp | dscp-dp | dscp-dscp | dscp-lp | exp-lp | lp-exp }

Views

System view

Predefined user roles

network-admin

mdc-admin

Parameters

For the description of keywords, see Table 20.

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

qos map-table color

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

Syntax

qos map-table color { green | yellow | red } lp-tunnel-dscp

Views

System view

Predefined user roles

network-admin

mdc-admin

Parameters

green: Specifies green packets.

yellow: Specifies yellow packets.

red: Specifies red packets.

The device provides the following types of priority map.

Table 24 Priority maps

Priority mapping	Description
lp-tunnel-dscp	Local-outer DSCP priority map. This map is used for packets forwarded through a VXLAN tunnel or VXLAN-DCI tunnel. This map must be used together with the qos vxlan-dci-tunnel outer dscp or vxlan-tunnel outer dscp command (see VXLAN Command Reference). After the command is executed, this map applies to all VXLAN packets.

Priority mapping

Description

lp-tunnel-dscp

Local-outer DSCP priority map. This map is used for packets forwarded through a VXLAN tunnel or VXLAN-DCI tunnel.

‌

Usage guidelines

For a type of colored priority mapping, the following priority maps exist:

· One for inbound traffic.

· One for outbound traffic.

· One for traffic in both directions.

If you do not specify a direction, the priority map for traffic in both directions applies.

Examples

# Enter the view of the local-outer DSCP priority map for green packets.

<Sysname> system-view

[Sysname] qos map-table color green lp-tunnel-dscp

[Sysname-maptbl-green-lp-tunnel-dscp]

Related commands

display qos map-table color

import

vxlan-dci-tunnel outer dscp (VXLAN Command Reference)

vxlan-tunnel outer dscp (VXLAN Command Reference)

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

mdc-admin

mdc-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 Ten-GigabitEthernet 3/0/1.

<Sysname> display qos trust interface ten-gigabitethernet 3/0/1

Interface: Ten-GigabitEthernet3/0/1

Port priority information

Port priority: 4

Port dscp priority: -

Port priority trust type: dscp

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

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 trusts the 802.1p priority in incoming packets.

Views

Interface view

Predefined user roles

network-admin

mdc-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 Ten-GigabitEthernet 3/0/1.

<Sysname> system-view

[Sysname] interface ten-gigabitethernet 3/0/1

[Sysname-Ten-GigabitEthernet3/0/1] qos trust dot1p

Related commands

display qos trust interface

qos trust tunnel-dscp (system view)

Use qos trust tunnel-dscp to configure trusting the DSCP priority in the outer IP header of VXLAN packets.

Use undo qos trust tunnel-dscp to restore the default.

Syntax

qos trust tunnel-dscp

undo qos trust tunnel-dscp

Default

No priority trust mode is configured for VXLAN packets.

Views

System view

Predefined user roles

network-admin

mdc-admin

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.

The qos trust tunnel-dscp command is not supported when the system operating mode is standard. For more information about system operating modes, see device management in Fundamentals 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

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.

Views

Interface view

Predefined user roles

network-admin

mdc-admin

Parameters

priority-value: Specifies a port priority value in the range of 0 to 7. If the device supports a DSCP port priority value, the value range is 0 to 63.

Examples

# Set the port priority of Ten-GigabitEthernet 3/0/1 to 2.

<Sysname> system-view

[Sysname] interface ten-gigabitethernet 3/0/1

[Sysname-Ten-GigabitEthernet3/0/1] qos priority 2

Related commands

display qos trust interface

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

mdc-admin

mdc-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: Ten-GigabitEthernet3/0/1

Rule: If-match queue 1

CIR 512 (kbps), CBS 51200 (Bytes)

Table 26 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

Interface view

Predefined user roles

network-admin

mdc-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 10 to 1000000 for GE interfaces, 10 to 10000000 for 10-GE interfaces, 10 to 40000000 for 40-GE interfaces, and 10 to 100000000 for 100-GE interfaces. This value must be a multiple of 10.

cbs committed-burst-size: Specifies the CBS in bytes. The value range for committed-burst-size is 512 to 8355840, 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 8355840 is converted to 8355840.

Usage guidelines

Only outgoing traffic on an interface is shaped.

Examples

# Shape the packets in queue 1 on Ten-GigabitEthernet 3/0/1. The GTS parameters are as follows:

· The CIR is 260 kbps.

· The CBS is 51200 bytes.

<Sysname> system-view

[Sysname] interface ten-gigabitethernet 3/0/1

[Sysname-Ten-GigabitEthernet3/0/1] qos gts queue 1 cir 260 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

mdc-admin

mdc-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: Ten-GigabitEthernet3/0/1

Direction: Outbound

CIR 2000 (kbps), CBS 20480 (Bytes)

Table 27 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 { inbound | outbound } cir committed-information-rate [ cbs committed-burst-size ]

undo qos lr { inbound | outbound }

Default

No rate limit is configured.

Views

Interface view

Predefined user roles

network-admin

mdc-admin

Parameters

inbound: Limits the rate of incoming packets.

outbound: Limits the rate of outgoing packets.

cbs committee-burst-size: Specifies the committed burst size (CBS) in bytes. The value range for committed-burst-size is 512 to 8355840, 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 8355840 is converted to 8355840.

Examples

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

<Sysname> system-view

[Sysname] interface ten-gigabitethernet 3/0/1

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

Congestion management commands

Common commands

display qos queue interface

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

Syntax

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

Views

Any view

Predefined user roles

network-admin

network-operator

mdc-admin

mdc-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: Ten-GigabitEthernet3/0/1

Output queue: Strict Priority queuing

Interface: Ten-GigabitEthernet3/0/2

Output queue: Strict Priority queuing

…

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

mdc-admin

mdc-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 Ten-GigabitEthernet 3/0/1.

<Sysname> display qos queue sp interface ten-gigabitethernet 3/0/1

Interface: Ten-GigabitEthernet3/0/1

Output queue: Strict Priority queuing

Table 29 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 SP queuing.

Views

Interface view

Predefined user roles

network-admin

mdc-admin

Examples

# Enable SP queuing on Ten-GigabitEthernet 3/0/1.

<Sysname> system-view

[Sysname] interface ten-gigabitethernet 3/0/1

[Sysname-Ten-GigabitEthernet3/0/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

mdc-admin

mdc-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 Ten-GigabitEthernet 3/0/1.

<Sysname> display qos queue wrr interface ten-gigabitethernet 3/0/1

Interface: Ten-GigabitEthernet3/0/1

Output queue: Weighted Round Robin queuing

Queue ID Queue name Group Byte count

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

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 30 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 SP queuing.

Views

Interface view

Predefined user roles

network-admin

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

Examples

# Enable packet-count WRR queuing on Ten-GigabitEthernet 3/0/1.

<Sysname> system-view

[Sysname] interface ten-gigabitethernet 3/0/1

[Sysname-Ten-GigabitEthernet3/0/1] qos wrr weight

# Enable byte-count WRR queuing on Ten-GigabitEthernet 3/0/1.

<Sysname> system-view

[Sysname] interface ten-gigabitethernet 3/0/1

[Sysname-Ten-GigabitEthernet3/0/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 | 2 } { 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 weight of 1, 2, 3, 4, 5, 6, 7, and 8, respectively.

Views

Interface view

Predefined user roles

network-admin

mdc-admin

Parameters

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

Table 31 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 | 2 }: Specifies WRR group 1 or 2. If you do not specify a group, group 1 applies. Group 1 has higher scheduling priority than group 2. Queues in group 2 are serviced only when all queues in group 1 are empty.

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.

Examples

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

<Sysname> system-view

[Sysname] interface ten-gigabitethernet 3/0/1

[Sysname-Ten-GigabitEthernet3/0/1] qos wrr byte-count

[Sysname-Ten-GigabitEthernet3/0/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

Interface view

Predefined user roles

network-admin

mdc-admin

Parameters

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

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 Ten-GigabitEthernet 3/0/1, and assign queue 0 to the SP group.

<Sysname> system-view

[Sysname] interface ten-gigabitethernet 3/0/1

[Sysname-Ten-GigabitEthernet3/0/1] qos wrr byte-count

[Sysname-Ten-GigabitEthernet3/0/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

mdc-admin

mdc-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 Ten-GigabitEthernet 3/0/1.

<Sysname> display qos wfq interface ten-gigabitethernet 3/0/1

Interface: Ten-GigabitEthernet3/0/1

Output queue: Hardware Weighted Fair Queuing

Queue ID Queue name Group Byte count Min Bandwidth

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

0 be 1 1 0

1 af1 1 1 0

2 af2 1 1 0

3 af3 1 1 0

4 af4 1 1 0

5 ef 1 1 0

6 cs6 1 1 0

7 cs7 1 1 0

Table 32 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 is not set.

Views

Interface view

Predefined user roles

network-admin

mdc-admin

Parameters

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

min bandwidth-value: Sets the minimum guaranteed bandwidth in kbps. The value range for committed-information-rate is 8 to 1000000 for GE interfaces, 8 to 10000000 for 10-GE interfaces, 8 to 40000000 for 40-GE interfaces, and 8 to 100000000 for 100-GE interfaces.

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.

For SE interface modules, only queue 5, queue 6, and queue 7 support the minimum guaranteed bandwidth.

Examples

# Set the minimum guaranteed bandwidth to 100 kbps for queue 7 on Ten-GigabitEthernet 3/0/1.

<Sysname> system-view

[Sysname] interface ten-gigabitethernet 3/0/1

[Sysname-Ten-GigabitEthernet3/0/1] qos wfq byte-count

[Sysname-Ten-GigabitEthernet3/0/1] qos bandwidth queue 7 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 SP queuing.

Views

Interface view

Predefined user roles

network-admin

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

Examples

# Enable packet-count WFQ on Ten-GigabitEthernet 3/0/1.

<Sysname> system-view

[Sysname] interface ten-gigabitethernet 3/0/1

[Sysname-Ten-GigabitEthernet3/0/1] qos wfq weight

# Enable byte-count WFQ on Ten-GigabitEthernet 3/0/1.

<Sysname> system-view

[Sysname] interface ten-gigabitethernet 3/0/1

[Sysname-Ten-GigabitEthernet3/0/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 | 2 } { byte-count | weight } schedule-value

undo qos wfq queue-id

Default

All queues on a WFQ-enabled interface are in WFQ group 1 and have a weight of 1.

Views

Interface view

Predefined user roles

network-admin

mdc-admin

Parameters

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

group { 1 | 2 }: Specifies WFQ group 1 or 2. If you do not specify a group, group 1 applies. Group 1 has higher scheduling priority than group 2. Queues in group 2 are serviced only when all queues in group 1 are empty.

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.

Examples

# Enable byte-count WFQ on Ten-GigabitEthernet 3/0/1, assign queue 0 to WFQ group 1, and specify scheduling weight 10 for queue 0.

<Sysname> system-view

[Sysname] interface ten-gigabitethernet 3/0/1

[Sysname-Ten-GigabitEthernet3/0/1] qos wfq byte-count

[Sysname-Ten-GigabitEthernet3/0/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.

Views

Interface view

Predefined user roles

network-admin

mdc-admin

Parameters

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

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 Ten-GigabitEthernet 3/0/1, and assign queue 7 to the SP group.

<Sysname> system-view

[Sysname] interface ten-gigabitethernet 3/0/1

[Sysname-Ten-GigabitEthernet3/0/1] qos wfq byte-count

[Sysname-Ten-GigabitEthernet3/0/1] qos wfq 7 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 not set.

Views

Queue scheduling profile view

Predefined user roles

network-admin

mdc-admin

Parameters

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

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.

On type-SE cards, you can set the minimum guaranteed bandwidth only for queues 5, 6, and 7.

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

<Sysname> system-view

[Sysname] qos qmprofile myprofile

[Sysname-qmprofile-myprofile] queue 0 wfq group 1 byte-count 1

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

display qos qmprofile configuration

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

Syntax

In standalone mode:‌

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

In IRF mode:

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

Views

Any view

Predefined user roles

network-admin

network-operator

mdc-admin

mdc-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 a card by its slot number. If you do not specify a card, this command displays the queue scheduling profile configuration for the active MPU. (In standalone mode.)

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

Examples

# Display the configuration of queue scheduling profile myprofile.

<Sysname> display qos qmprofile configuration myprofile

Queue management profile: myprofile (ID 1)

Queue ID Type Group Schedule Schedule Min

unit value bandwidth

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

be WFQ 1 byte-count 1 0

af1 SP N/A N/A N/A 0

af2 SP N/A N/A N/A 0

af3 SP N/A N/A N/A 0

af4 SP N/A N/A N/A 0

ef SP N/A N/A N/A 0

cs6 SP N/A N/A N/A 0

cs7 SP N/A N/A N/A 0

Table 33 Command output

Field	Description
Queue management profile	Queue scheduling profile name.
Type	Queue scheduling type: · SP. · WRR. · WFQ.
Group	Priority group to which the queue belongs. 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.

‌

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

mdc-admin

mdc-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 Ten-GigabitEthernet 3/0/1.

<Sysname> display qos qmprofile interface ten-gigabitethernet 3/0/1

Interface: Ten-GigabitEthernet3/0/1

Direction: Outbound

Queue management profile: myprofile

Table 34 Command output

Field	Description
Direction	Direction in which the queue scheduling profile is applied.
Queue management 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

Interface view

Predefined user roles

network-admin

mdc-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 one direction of an interface.

Examples

# Apply queue scheduling profile myprofile to the outbound direction of Ten-GigabitEthernet 3/0/1.

<Sysname> system-view

[Sysname] interface ten-gigabitethernet 3/0/1

[Sysname-Ten-GigabitEthernet3/0/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

mdc-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 SP queues.

Views

Queue scheduling profile view

Predefined user roles

network-admin

mdc-admin

Parameters

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

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 be 1 or 2.

byte-count: Allocates bandwidth to queues in bytes.

weight: Allocates bandwidth to queues in packets.

schedule-value: Specifies the scheduling weight. The value range for this argument 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 byte-count 10

Related commands

display qos qmprofile interface

qos qmprofile

Congestion avoidance commands

WRED commands

display qos wred fabric

Use display qos wred fabric to display the configuration of WRED tables applied to internal interfaces.

Syntax

In standalone mode:‌

display qos wred fabric [ slot slot-number ] [ inbound | outbound ]

In IRF mode:

display qos wred fabric [ chassis chassis-number slot slot-number ] [ inbound | outbound ]

Views

Any view

Predefined user roles

network-admin

network-operator

mdc-admin

mdc-operator

Parameters

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

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

[ inbound | outbound ]: Specifies a WRED table applied to the inbound or outbound direction. If you do not specify a direction, this command displays the configuration of the WRED tables applied to the inbound and outbound directions. The direction from an interface card to a switching fabric module is the inbound direction. The reverse direction is the outbound direction.

Examples

# Display the configuration of the WRED table applied to internal interfaces for slot 1.

<Sysname> display qos wred fabric slot 1

Slot: 1

Inbound:

Current WRED configuration:

Applied WRED table name: q1 Application status: Successful

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

Outbound:

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

Field	Description
Application status	Application status: Successful or Failed.
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.

‌

Related commands

qos wred apply fabric

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

mdc-admin

mdc-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: Ten-GigabitEthernet3/0/3

Current WRED configuration:

Applied WRED table name: q1

Table 36 Command output

Field	Description
Interface	Interface type and interface number.

‌

display qos wred table

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

Syntax

In standalone mode:‌

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

In IRF mode:

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

Views

Any view

Predefined user roles

network-admin

network-operator

mdc-admin

mdc-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 a card by its slot number. If you do not specify a card, this command displays the WRED table configuration for the active MPU. (In standalone mode.)

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

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 gprob ymin ymax yprob rmin rmax rprob exponent 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 37 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.
exponent	Exponent for average queue length calculation.
ECN	This field is not supported in the current software version. 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

Interface view

Predefined user roles

network-admin

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

Examples

# Apply WRED table table1 to Ten-GigabitEthernet 3/0/1.

<Sysname> system-view

[Sysname] interface ten-gigabitethernet 3/0/1

[Sysname-Ten-GigabitEthernet3/0/1] qos wred apply table1

Related commands

display qos wred interface

display qos wred table

qos wred queue table

qos wred apply fabric

Use qos wred apply fabric to apply a WRED table to internal interfaces.

Use undo qos wred apply fabric to restore the default.

Syntax

In standalone mode:‌

qos wred apply table-name fabric

undo qos wred apply fabric

In IRF mode:

qos wred apply [ table-name ] fabric [ chassis chassis-number slot slot-id { inbound | outbound } ]

undo qos wred apply fabric [ chassis chassis-number slot slot-id { inbound | outbound } ]

Default

No WRED table is applied to internal interfaces, and tail drop is used on internal interfaces.

Views

System view

Predefined user roles

network-admin

mdc-admin

Parameters

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

Usage guidelines

An interface module and a switching fabric module will use internal interfaces to exchange packets when necessary. Congestion might occur on internal interfaces. In this case, you can perform this task to address congestion issues.

For the S12500G-AF switch series, this command takes effect only on SF and SG interface modules and do not take effect on IRF ports. For more information about IRF, see Virtual Technologies Configuration Guide.

Examples

# Apply WRED table table1 to all internal interfaces.

<Sysname> system-view

[Sysname] qos wred apply table1 fabric

Related commands

display qos wred fabric

qos wred ecn enable

Use qos wred ecn enable to enable ECN globally.

Use undo qos wred ecn enable to disable ECN globally.

Syntax

qos wred ecn enable

undo qos wred ecn enable

Default

ECN is disabled globally.

Views

System view

Predefined user roles

network-admin

mdc-admin

Usage guidelines

This function enables ECN on all queues configured with WRED parameters. The queues can be queues configured with the qos wred queue commands in interface view and queues configured in a WRED table.

This command takes effect only on TCP packets and UDP packets on the following modules:

· SC modules prefixed with LSCM2.

· SD interface modules.

Examples

# Enable WRED on Ten-GigabitEthernet 3/0/1, and use the IP precedence for drop probability calculation.

<Sysname> system-view

[Sysname] interface ten-gigabitethernet 3/0/1

[Sysname-Ten-GigabitEthernet3/0/1] qos wfq queue-length 100 queue-number 512

[Sysname-Ten-GigabitEthernet3/0/1] qos wred ip-precedence enable

Related commands

queue

queue ecn

qos wred queue

qos wred queue ecn

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

The default for this command varies by device model.

Views

Interface view

Predefined user roles

network-admin

mdc-admin

Parameters

queue-id: Specifies a queue by its ID. The value range for this argument varies by device model.

low-limit low-limit: Specifies the lower limit for the average queue length. The value range for low-limit varies by device model.

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 varies by device model.

discard-probability discard-prob: Specifies the denominator for drop probability calculation. The greater the denominator, the greater the calculated drop probability. The default and the value range for discard-prob vary by device model.

ecn: Enables ECN.

weighting-constant exponent: Specifies the WRED exponent for average queue length calculation. The value range for exponent varies by device model.

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 Ten-GigabitEthernet 3/0/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 ten-gigabitethernet 3/0/1

[Sysname-Ten-GigabitEthernet3/0/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

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

mdc-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 default for this command vary by device model.

Views

Interface view

Predefined user roles

network-admin

mdc-admin

Parameters

queue-id: Specifies a queue by its ID. The value range for this argument varies by device model.

weighting-constant exponent: Specifies the WRED exponent for average queue length calculation. The value range for exponent varies by device model.

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 Ten-GigabitEthernet 3/0/1.

<Sysname> system-view

[Sysname] interface ten-gigabitethernet 3/0/1

[Sysname-Ten-GigabitEthernet3/0/1] qos wred queue 1 weighting-constant 12

Related commands

display qos wred interface

qos wred queue

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

mdc-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 low-limit is 0 to 69632. The value is in 288 bytes on the SC modules prefixed with LSCM2 and SE modules and in 256 bytes on LSCM1GT48SC0 cards.

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 69632. The value is in 288 bytes on the SC modules prefixed with LSCM2 and SE modules and in 256 bytes on LSCM1GT48SC0 cards.

Usage guidelines

The SC modules prefixed with LSCM2 and SD interface modules support only the range 0 to 10496 for the lower limit and upper limit for the average queue length. SE interface modules support only the range 0 to 22016. LSCM1GT48SC0 cards support only the range 0 to 10496.

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

mdc-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

Global CAR commands

car name

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

Use undo car to restore the default.

Syntax

car name car-name

undo car

Default

No global CAR action is configured in a traffic behavior.

Views

Traffic behavior view

Predefined user roles

network-admin

mdc-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 global CAR actions.

Syntax

display qos car name [ car-name ]

Views

Any view

Predefined user roles

network-admin

network-operator

mdc-admin

mdc-operator

Parameters

car-name: Specifies a global 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 a global CAR action, this command displays information about all global CAR actions.

Examples

# (In standalone mode.) ‌Display information about all global 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

Slot 0:

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

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

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

Table 38 Command output

Field	Description
Name	Name of the global 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.
Green packets	Statistics about green packets.
Yellow packets	Statistics about yellow packets.
Red packets	Statistics about red packets.

qos car (system view)

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

mdc-admin

Parameters

car-name: Specifies the name of the global 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 16 to 100000000, in increments of 8.

ebs excess-burst-size: Specifies the excess burst size (EBS) in bytes. The value range for excess-burst-size is 0 to 67092480, 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 67092480 is converted to 67092480.

pir peak-information-rate: Specifies the PIR in kbps. The value range for peak-information-rate is 16 to 100000000, 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-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. This action takes effect only in the inbound direction on the SC modules prefixed with LSCM2.

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. A QoS policy containing an aggregate CAR action can be applied to only one direction in the same view.

If the action for yellow packets is configured as discard, the action for red packets can only be configured as discard.

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 global CAR actions.

Syntax

reset qos car name [ car-name ]

Views

User view

Predefined user roles

network-admin

mdc-admin

Parameters

Examples

# Clear the statistics about global 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. How elephant flows are processed depends on the device model.

No action is configured.

Views

Elephant/mice flow view

Predefined user roles

network-admin

mdc-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

mdc-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

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

· Create a flow group in mice-elephant-flow mode or 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:

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

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

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

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

mdc-admin

Examples

# Enter elephant/mice flow view.

<Sysname> system-view

[Sysname] qos mice-elephant-flow

[Sysname-mice-elephant-flow]

Traffic Matrix commands

display traffic-matrix

Use display traffic-matrix to display the flow tables of Traffic Matrix.

Syntax

In standalone mode:‌

display traffic-matrix [ dynamic ] [ ip | ipv6 ] [ slot slot-number ]

In IRF mode:

display traffic-matrix [ dynamic ] [ ip | ipv6 ] [ chassis chassis-number slot slot-number ]

Views

Any view

Predefined user roles

network-admin

network-operator

mdc-admin

mdc-operator

Parameters

dynamic: Displays dynamically generated Traffic Matrix flow entries in adaptive routing scenarios. If you do not specify this keyword, the command displays statically configured Traffic Matrix flow entries.

ip: Specifies the IPv4 flow table. If you do not specify this keyword and the ipv6 keyword, the command displays both IPv4 and IPv6 flow tables.

ipv6: Specifies the IPv6 flow table. If you do not specify this keyword and the ip keyword, the command displays both IPv4 and IPv6 flow tables.

slot slot-number: Specifies a card by its slot number. The slot-number argument represents the slot number of the card. If you do not specify a card, the command displays Traffic Matrix flow entries for all cards. (In standalone mode.)

chassis chassis-number slot slot-number: Specifies a card on an IRF member device. The chassis-number argument represents the member ID of the IRF member device. The slot-number argument represents the slot number of the card. If you do not specify a card, the command displays Traffic Matrix flow entries for all cards. (In IRF mode.) ‌

Usage guidelines

Traffic Matrix flow entries can be statically configured or dynamically generated.

· Static configuration—You can use the ipv6 source destination or ip source destination command to generate a Traffic Matrix flow entry.

· Dynamic generation—In adaptive routing scenarios, the device automatically collects network node congestion data and dynamically generates Traffic Matrix flow entries.

Examples

# Display all statically configured flow entries.

<Sysname> display traffic-matrix

Slot : 0

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

Protocol : 17

SPort : 4791 SIP : 1.1.1.1

DPort : 4791 DIP : 2.2.2.2

Traffic path: GE1/0/1 Next hop: 1.1.1.2

Status : Active Reason : -

Protocol : 17

SPort : - SIP : 1.1.1.1

DPort : - DIP : 2.2.2.2

Traffic path: GE1/0/1 Next hop: 1.1.1.2

Status : Inactive Reason : Interface down

Protocol : -

SPort : - SIP : 1.1.1.1

DPort : - DIP : 2.2.2.2

Traffic path: GE1/0/1 Next hop: 1.1.1.2

Status : Inactive Reason : Destination unreachable

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

Slot : 1

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

Protocol : 17

SPort : 4791 SIP : 1.1.1.1

DPort : 4791 DIP : 2.2.2.2

Traffic path: GE1/0/1 Next hop: 1.1.1.2

Status : Active Reason : -

Protocol : 17

SPort : - SIP : 1.1.1.1

DPort : - DIP : 2.2.2.2

Traffic path: GE1/0/1 Next hop: 1.1.1.2

Status : Inactive Reason : ARP/ND unreachable

Protocol : -

SPort : - SIP : 1.1.1.1

DPort : - DIP : 2.2.2.2

Traffic path: GE1/0/1 Next hop: 1.1.1.2

Status : Inactive Reason : Remote path failure

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

# Display dynamically generated Traffic Matrix flow entries.

<Sysname> display traffic-matrix dynamic

Slot : 0

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

Protocol : 17

SPort : 4791 SIP : 1.1.1.1

DPort : 4791 DIP : 2.2.2.2

Traffic path: GE1/0/1 Next hop: 1.1.1.2

Status : Active Reason : -

Aging : 5 minutes remaining

Table 39 Command output

Field	Description
Protocol	Protocol number,
SPort	Source port number.
SIP	Source IP address.
DPort	Destination port number.
DIP	Destination IP address.
Traffic path	Output interface to which traffic is redirected.
Next hop	Next-hop address to which traffic is redirected.
Status	Effective state of a flow entry: · Active—The flow entry is effective. · Inactive—The flow entry is ineffective.
Reason	Reason why a flow entry fails to take effect: · Interface down—The output interface is down. · Destination Unreachable—The next-hop address is unreachable. · ARP/ND unreachable—The ARP or ND entry is unavailable. · Remote path failure—BGP detects a remote path failure. · Resource not enough—Resources are insufficient. · Not ready—The device driver is not ready. The device driver might be ready after a moment. You can execute the command later. · -—The flow entry takes effect.
Aging	Aging time of a dynamically generated Traffic Matrix flow entry: · x minutes remaining—Number of minutes remaining before the flow entry is aged out. · Aged—The flow entry has been aged out. · -—Traffic is continuously present before half of the aging time elapses.

‌

ip source destination

Use ip source destination to configure an IPv4 flow entry for Traffic Matrix.

Use undo ip source destination to delete an IPv4 flow entry for Traffic Matrix.

Syntax

ip [ protocol protocol ] source source-address destination dest-address [ source-port port destination-port port ] traffic-path interface interface-type interface-number next-hop ip-address

undo ip [ protocol protocol ] source source-address destination dest-address [ source-port port destination-port port ]

Default

Traffic Matrix does not have an IPv4 flow entry.

Views

Traffic Matrix View

Predefined user roles

network-admin

mdc-admin

Parameters

protocol protocol: Specify a protocol type by its number in the range of 0 to 255. If you do not specify a protocol type, any protocol type can be matched.

source source-address: Specifies a source IPv4 address.

destination dest-address: Specifies a destination IPv4 address.

source-port port: Specifies a source port in the range of 0 to 65535. If you do not specify a source port, any source port can be matched.

destination-port port: Specifies a destination port in the range of 0 to 65535. If you do not specify a destination port, any destination port can be matched.

traffic-path interface interface-type interface-number: Redirect matching traffic to the specified interface for forwarding.

next-hop ip-address: Redirects matching traffic to the specified next-hop IP address. The next-hop IP address can be an IPv4 address or an IPv6 address.

Usage guidelines

Operating mechanism

Use this command to redirect traffic to the specified output interface and next hop for forwarding. The redirected traffic must match the source address, destination address, source port number, destination port number, and protocol type specified in this command.

Restrictions and guidelines

Multiple IPv4 flow entries can be configured for Traffic Matrix. If you configure multiple IPv4 flow entries with the same 5-tuple, the most recent configuration takes effect.

In the Traffic Matrix feature, the source address, destination address, and next-hop address of an IPv4 flow entry must all be valid unicast addresses.

The Traffic Matrix feature regularly queries the routing table to identify whether the next-hop address specified in the ip source destination command is reachable in the routing table. If the next-hop address is unreachable, the ip source destination command will no longer be effective.

If the same flow can match multiple IPv4 flow entries in the Traffic Matrix feature, the priority order for IPv4 flow entries is as follows:

7. The IPv4 flow entry that is configured with the 5-tuple has the highest priority.

8. Other IPv4 flow entries are matched in their order of configuration. When a match is found, the matching process stops.

As a best practice to prevent the same flow from being forwarded through different paths before and after the device reboots or the interface flaps, do not configure two flow entries with the same source address and destination address and other overlapping match items. Suppose you configure one flow entry with a protocol, a source address, and a destination address, and the other flow entry with the same source address and destination address but without a protocol. The flow that can match the two entries might match different flow entries and is forwarded through different paths before and after the device reboots or the interface flaps.

Examples

# Configure an IPv4 flow entry.

<Sysname> system-view

[Sysname] traffic-matrix

[Sysname-traffic-matrix] ip protocol 80 source 1.1.1.1 destination 2.2.2.2 source-port 8080 destination-port 8080 traffic-path interface gigabitethernet 1/0/1 next-hop 3.3.3.3

Related commands

display traffic-matrix

ipv6 source destination

Use ipv6 source destination to configure an IPv6 flow entry for Traffic Matrix.

Use undo ipv6 source destination to delete an IPv6 flow entry.

Syntax

ipv6 [ protocol protocol ] source source-address destination dest-address [ source-port port destination-port port ] traffic-path interface interface-type interface-number next-hop ip-address

undo ipv6 [ protocol protocol ] source source-address destination dest-address [ source-port port destination-port port ]

Default

Traffic Matrix does not have an IPv6 flow entry.

Views

Traffic Matrix view

Predefined user roles

network-admin

mdc-admin

Parameters

protocol protocol: Specifies a protocol type by its number in the range of 0 to 255. If you do not specify a protocol type, any protocol type can be matched.

source source-address: Specifies a source IPv6 address.

destination dest-address: Specifies a destination IPv6 address.

source-port port: Specifies a source port in the range of 0 to 65535. If you do not specify a source port, any source port can be matched.

destination-port port: Specifies a destination port in the range of 0 to 65535. If you do not specify a destination port, any destination port can be matched.

traffic-path interface interface-type interface-number: Redirects matching traffic to the specified interface for forwarding.

next-hop ip-address: Redirects matching traffic to the specified next-hop IP address. The next-hop IP address can be an IPv4 address or an IPv6 address.

Usage guidelines

Operating mechanism

Restrictions and guidelines

Multiple IPv6 flow entries can be configured for Traffic Matrix. If you configure multiple IPv6 flow entries with the same 5-tuple, the most recent configuration takes effect.

In the Traffic Matrix feature, the source address, destination address, and next-hop address in an IPv6 flow entry must all be valid unicast addresses.

The Traffic Matrix feature regularly queries the routing table to identify whether the next-hop address specified in the ipv6 source destination command is reachable in the routing table. If the next-hop address is unreachable, the ipv6 source destination command will no longer be effective.

If the same flow can match multiple IPv6 flow entries in the Traffic Matrix feature, the priority order for IPv6 flow entries is as follows:

9. The IPv6 flow entry that is configured with the 5-tuple has the highest priority.

10. Other IPv6 flow entries are matched in their order of configuration. When a match is found, the matching process stops.

Examples

# Configure an IPv6 flow entry.

<Sysname> system-view

[Sysname] traffic-matrix

[Sysname-traffic-matrix] ipv6 protocol 80 source 1::1 destination 2::2 source-port 8080 destination-port 8080 traffic-path interface gigabitethernet 1/0/1 next-hop 3::3

Related commands

display traffic-matrix

traffic-matrix

Use traffic-matrix to enable the Traffic Matrix feature and enter Traffic Matrix view.

Use undo traffic-matrix to disable the Traffic Matrix feature and delete all its flow tables.

Syntax

traffic-matrix

undo traffic-matrix

Default

The Traffic Matrix feature is disabled.

Views

System view

Predefined user roles

network-admin

mdc-admin

Usage guidelines

Application scenarios

In scenarios where AI model training occurs in data center networks or intelligent lossless networks, there are fewer traffic flows, but each flow has long transmission time and large data volumes. When traffic load sharing is conducted using the hash algorithm through equal-cost multi-path (ECMP), load imbalance can easily occur. To address uneven traffic load, enable the Traffic Matrix feature. The controller, based on the 5-tuple, deploys flow entries to leaf or spine devices to redirect traffic. Traffic is redirected to the specified path for forwarding, thus achieving manually controlled load sharing.

Operating mechanism

Traffic Matrix flow entries can be statically configured or dynamically generated.

· Static configuration—You can use the ipv6 source destination or ip source destination command to generate a Traffic Matrix flow entry. A flow that matches a flow entry is forwarded according to the specified output interface and next hop.

· Dynamic generation—In adaptive routing scenarios, the device automatically collects network node congestion data and dynamically generates Traffic Matrix flow entries.

Restrictions and guidelines

Statically configured Traffic Matrix flow entries have higher priority than dynamically generated ones.

The device forwards traffic first according to the path defined in the flow table. If the defined path is invalid (for example, the output interface fails or the next hop is unreachable), the traffic is then forwarded by looking up the routing table.

Examples

# Enable the Traffic Matrix feature and enter Traffic Matrix view.

<Sysname> system-view

[Sysname] traffic-matrix

[Sysname-traffic-matrix]

Related commands

display traffic-matrix

ip source destination

ipv6 source destination

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 | outbound }

Views

Any view

Predefined user roles

network-admin

network-operator

mdc-admin

mdc-operator

Parameters

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

inbound: Specifies the inbound direction.

outbound: Specifies the outbound direction.

Examples

# Display inbound packet statistics for Ten-GigabitEthernet 3/0/1.

<Sysname> display qos packet-statistics interface ten-gigabitethernet 3/0/1 inbound

Interface: Ten-GigabitEthernet3/0/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 | outbound } ecn

undo qos packet-statistics { inbound | outbound }

Default

Packet accounting is disabled on an interface.

Views

Interface view

Predefined user roles

network-admin

mdc-admin

mdc-operator

Parameters

inbound: Specifies the inbound direction.

outbound: Specifies the outbound direction.

ecn: Counts ECN packets.

Examples

# Enable packet accounting for ECN packets with the DSCP priority in the inbound direction of Ten-GigabitEthernet 3/0/1.

<Sysname> system-view

[Sysname] interface ten-gigabitethernet 3/0/1

[Sysname-Ten-GigabitEthernet3/0/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 | outbound }

Views

User view

Predefined user roles

network-admin

mdc-admin

Parameters

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

inbound: Specifies the inbound direction.

outbound: Specifies the outbound direction.

Usage guidelines

If you do not specify a direction, this command clears interface packet statistics for both directions.

Examples

# Clear inbound packet statistics for Ten-GigabitEthernet 3/0/1.

<Sysname> reset qos packet-statistics interface ten-gigabitethernet 3/0/1 inbound

Queue-based accounting commands

display qos queue-statistics interface outbound

Use display qos queue-statistics interface outbound to display outgoing traffic statistics collected for interfaces on a per-queue basis.

Syntax

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

Views

Any view

Predefined user roles

network-admin

network-operator

mdc-admin

mdc-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 outgoing traffic statistics for all interfaces.

Usage guidelines

The function of displaying queue-based outgoing traffic statistics is supported only on the SF interface modules.

To use the queue-based accounting feature, you must enable AI ECN.

If you enable AI ECN for the specified queue, byte statistics will be collected for all queues.

Queue-based byte accounting does not support IPv6 packets.

Queue-based byte accounting does not count inter-frame gaps. The smaller the byte count, the less the displayed bps value accurately reflects the actual traffic flow.

The queue-based byte statistics are refreshed every three seconds. If you obtain the statistics multiple times within the period, the byte count and bps value do not change.

Examples

# Display queue-based outgoing traffic statistics of Ten-GigabitEthernet 3/0/1.

<Sysname> display qos queue-statistics interface ten-gigabitethernet 3/0/1 outbound

Interface: Ten-GigabitEthernet3/0/1

Direction: outbound

Forwarded: 0 packets, 0 bytes

Queue 0

Forwarded: 0 packets, 0 bytes

Current queue length: 0 packets

Queue 1

Forwarded: 0 packets, 0 bytes

Current queue length: 0 packets

Queue 2

Forwarded: 0 packets, 0 bytes

Current queue length: 0 packets

Queue 3

Forwarded: 0 packets, 0 bytes

Current queue length: 0 packets

Queue 4

Forwarded: 0 packets, 0 bytes

Current queue length: 0 packets

Queue 5

Forwarded: 0 packets, 0 bytes

Current queue length: 0 packets

Queue 6

Forwarded: 0 packets, 0 bytes

Current queue length: 0 packets

Queue 7

Forwarded: 0 packets, 0 bytes

Current queue length: 0 packets

Table 40 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 the number of packets and in the number of bytes.
Current queue length	Current number of packets in the queue.

Related commands

reset counters interface (Interface Command Reference)

qos queue-statistics byte-count

Use qos queue-statistics byte-count to configure the unit for queue-based traffic accounting as byte count.

Use undo qos queue-statistics byte-count to restore the default.

Syntax

qos queue-statistics byte-count

undo qos queue-statistics byte-count

Default

Queue-based traffic accounting is not performed in bytes.

Views

Interface view

System view

Predefined user roles

network-admin

mdc-admin

Usage guidelines

After you execute this command, you can use the display qos queue-statistics interface command to view queue-based traffic statistics in bytes.

If you configure the unit for queue-based traffic accounting as byte count in system view, the configuration takes effect on all interfaces. Even if an interface is configured with the undo qos queue-statistics byte-count command, it can still perform queue-based traffic accounting in bytes.

Executing this command in system view will consume a large number of ACL resources. To save ACL resources, execute this command in interface view.

Examples

# Configure the unit for queue-based traffic accounting as byte count in system view.

<Sysname> system-view

[Sysname] qos queue-statistics byte-count

Related commands

display qos queue-statistics interface outbound

10-ACL and QoS Command Reference

QoS policy commands

display traffic classifier

remark ip-precedence

remark qos-local-id

control-plane management

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

GTS commands

SP commands

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

Congestion avoidance commands

display qos queue-statistics interface outbound

Intelligent Terminal Products

Product Support Services

Technical Service Solutions

Resource Center

Policy

Online Help

Become a Partner

Partner Policy & Program