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 not protocol ipv6

Classifier: 3 (ID 102)

Operator: AND

Rule(s) :

-none-

Table 1 Command output

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

if-match

Use if-match to define a match criterion.

Use undo if-match to delete a match criterion.

Syntax

if-match match-criteria

undo if-match match-criteria

Default

No match criterion is configured.

Views

Traffic class view

Predefined user roles

network-admin

Parameters

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

Table 2 Available match criteria

Option	Description
acl [ ipv6 \| mac ] { acl-number \| name acl-name }	Matches an ACL. The value range for the acl-number argument is 2000 to 5999 for IPv4 and IPv6 ACLs and 4000 to 4999 for Layer 2 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.
any	Matches all packets. Only CSPC (except CSPC-GE16XP4L-E, CSPC-GE24L-E, and CSPC-GP24GE8XP2L-E) and CMPE-1104 cards support this keyword.
authenticated-user	Matches the packets of users that have passed IPoE, portal, or PPPoE authentication.
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. This option matches only the protocol packets that use well-known port numbers.
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. CSPC (except CSPC-GE16XP4L-E, CSPC-GE24L-E, and CSPC-GP24GE8XP2L-E) and CMPE-1104 cards do not support this option.
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.
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 6.
inbound-interface interface-type interface-number	Matches an input interface specified by its type and number.
ip-precedence ip-precedence-value&<1-8>	Matches IP precedence values. The ip-precedence-value&<1-8> argument specifies a space-separated list of up to eight IP precedence values. The value range for the ip-precedence-value argument is 0 to 7.
mpls-exp exp-value&<1-8>	Matches MPLS EXP values. The exp-value&<1-8> argument specifies a space-separated list of up to eight EXP values. The value range for the exp-value argument is 0 to 7. This option is available only on CSPC-GE16XP4L-E, CSPC-GE24L-E, CSPC-GP24GE8XP2L-E, CSPEX, and CEPC cards.
protocol protocol-name	Matches a protocol. The protocol-name argument can be arp, ipv6, or ip.
qos-local-id local-id-value	Matches a local QoS ID in the range of 1 to 4095.
service-dot1p dot1p-value&<1-8>	Matches 802.1p priority values in outer VLAN tags. The dot1p-value&<1-8> argument is 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. This option is supported only in standard mode. For more information about system operating modes see device management in Fundamentals Configuration Guide.

Table 3 Available system-defined control plane protocols

Protocol	Description
default	Protocol packets other than the following packet types
arp	ARP packets
arp-snooping	ARP snooping packets
bfd	BFD packets
bgp	BGP packets
bgp4+	IPv6 BGP packets
bpdu-tunnel	BPDU tunnel packets
cdp	CDP packets
cfd	CFD packets
dhcp	DHCP packets
dhcp-snooping	DHCP snooping packets
dhcpv6	IPv6 DHCP packets
dldp	DLDP packets
dot1x	802.1X packets
ftp	FTP packets
gmrp	GMRP packets
hoplimit-expires	Hop-limit expire packets
http	HTTP packets
https	HTTPS packets
icmp	ICMP packets
icmpv6	ICMPv6 packets
igmp	IGMP packets
igmp-snooping	IGMP snooping packets
ip-option	IPv4 packets with the Options field
ipv6-option	IPv6 packets with the Options field
irdp	IRDP 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)
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
pppoe-negotiation	PPPoE negotiation packets
pvst	PVST packets
radius	RADIUS packets
rip	RIP packets
ripng	RIPng packets
rrpp	RRPP packets
rsvp	RSVP packets
smart-link	SmartLink packets
snmp	SNMP packets
ssh	SSH packets
stp	STP packets
tacacs	TACACS packets
telnet	Telnet packets
tftp	TFTP packets
ttl-expires	TTL expire packets
udld	UDLD packets
udp-helper	UDP helper packets
vrrp	VRRP packets
vrrp6	IPv6 VRRP packets
vtp	VTP packets

‌

Usage guidelines

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

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

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

¡ 802.1p priority.

¡ DSCP.

¡ IP precedence.

¡ MPLS EXP.

¡ 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 used as a match criterion must already exist.

· The ACL is used for classification only and the permit/deny actions in ACL rules are ignored.

Examples

# 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 the 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 the advanced IPv6 ACL 3101.

<Sysname> system-view

[Sysname] traffic classifier class1

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

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

<Sysname> system-view

[Sysname] traffic classifier class1

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

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

<Sysname> system-view

[Sysname] traffic classifier class1

[Sysname-classifier-class1] if-match any

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

<Sysname> system-view

[Sysname] traffic classifier class1 operator or

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

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

<Sysname> system-view

[Sysname] traffic classifier class1 operator or

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

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

<Sysname> system-view

[Sysname] traffic classifier class1

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

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

<Sysname> system-view

[Sysname] traffic classifier class1 operator or

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

# Define a match criterion for traffic class class1 to match the packets with VLAN ID 2, 7, or 10 in the outer VLAN tag.

<Sysname> system-view

[Sysname] traffic classifier class1 operator or

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

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

<Sysname> system-view

[Sysname] traffic classifier class1

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

traffic classifier

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

Use undo traffic classifier to delete a traffic class.

Syntax

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

undo traffic classifier classifier-name

Default

No traffic classes exist.

Views

System view

Predefined user roles

network-admin

Parameters

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

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

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

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

Examples

# Create a traffic class named class1.

<Sysname> system-view

[Sysname] traffic classifier class1

[Sysname-classifier-class1]

Related commands

display traffic classifier

Traffic behavior commands

accounting

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

Use undo accounting to restore the default.

Syntax

accounting { byte | packet }

undo accounting

Default

No traffic accounting action is configured.

Views

Traffic behavior view

Predefined user roles

network-admin

Parameters

byte: Counts traffic in bytes.

packet: Counts traffic in packets.

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

bind nat-instance

Use bind nat-instance to configure a NAT instance binding action in a traffic behavior.

Use undo bind nat-instance to restore the default.

Syntax

bind nat-instance instance-name

undo bind nat-instance instance-name

Default

No NAT instance binding action is configured.

Views

Traffic behavior view

Predefined user roles

network-admin

Parameters

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

Usage guidelines

NAT supports interface-based NAT and global NAT. By redirecting traffic that requires NAT to the specified NAT instance, this command implements global NAT. For more information about NAT, see Layer 3—IP Services Configuration Guide.

This command and the redirect failover-group command are mutually exclusive.

Examples

# Configure a NAT instance binding action in traffic behavior database.

<Sysname> system-view

[Sysname] traffic behavior database

[Sysname-behavior-database] bind nat-instance test

Related commands

nat instance (Layer 3—IP Services Command Reference)

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

Parameters

cir committed-information-rate: Specifies the committed information rate (CIR) in the range of 1 to 160000000 kbps.

cbs committed-burst-size: Specifies the committed burst size (CBS) in the range of 512 to 256000000 bytes. The default is the product of 62.5 and the CIR value.

ebs excess-burst-size: Specifies the excess burst size (EBS) in the range of 0 to 256000000 bytes. If the PIR is not specified, the value range for excess-burst-size is 0 to 256000000, and the default is 0. If the PIR is specified, the value range for excess-burst-size is 512 to 256000000.

pir peak-information-rate: Specifies the peak information rate (PIR) in the range of 1 to 160000000 kbps.

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

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

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

action: Sets the action to take on the packet:

· discard: Drops the packet.

· pass: Permits the packet to pass through.

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

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

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

Usage guidelines

Only the pass action is supported for green packets and yellow packets on CSPC-GE16XP4L-E, CSPC-GE24L-E, CSPC-GP24GE8XP2L-E, CSPEX, and CEPC cards.

Only the discard and pass actions are supported for red packets on CSPC-GE16XP4L-E, CSPC-GE24L-E, CSPC-GP24GE8XP2L-E, CSPEX, and CEPC cards.

If you set the cir committed-information-rate option to a value in the range of 1 to 8 kbps on CSPEX cards (except CSPEX-1204 and CSPEX-1104-E) and CEPC cards, the actual setting takes effect. If you set the cir committed-information-rate option to a value in the range of 1 to 8 on any other card, 8 kbps always takes effect.

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.

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

In a traffic policing action applied to a control plane, the supported value range for the cir committed-information-rate option is 8 to 10000 kbps.

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

Examples

# Configure a CAR action in traffic behavior database:

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

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

<Sysname> system-view

[Sysname] traffic behavior database

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

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

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

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

Primap pre-defined table: dscp-dp

Behavior: 2 (ID 101)

Accounting enable: Packet

Filter enable: Permit

Marking:

Remark mpls-exp 4

Behavior: 3 (ID 102)

-none-

Behavior: 4 (ID 103)

Mirroring:

Mirror to the interface: Ten-GigabitEthernet3/1/1 pop-label

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.
Primap pre-defined color table	Information about pre-defined colored priority maps. For more information, see "Priority map commands."
Accounting enable	Traffic accounting action.
Filter enable	Traffic filtering action.
Remark mpls-exp	Action of setting the MPLS EXP value for 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

Parameters

deny: Drops packets.

permit: Transmits packets.

Examples

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

<Sysname> system-view

[Sysname] traffic behavior database

[Sysname-behavior-database] filter deny

free account

Use free account to configure the traffic permission action in a traffic behavior.

Use undo free account to restore the default.

Syntax

free account

undo free account

Default

The traffic permission action is not configured.

Views

Traffic behavior view

Predefined user roles

network-admin

Examples

# Configure the traffic permission action in traffic behavior database.

<Sysname> system-view

[Sysname] traffic behavior database

[Sysname-behavior-database] free account

primap color-map-dp

Use primap color-map-dp to configure the action of mapping packet colors to drop priority values in a traffic behavior.

Use undo primap color-map-dp to restore the default.

Syntax

primap color-map-dp

undo primap color-map-dp

Default

No priority mapping action is configured in a traffic behavior.

Views

Traffic behavior view

Predefined user roles

network-admin

Usage guidelines

This command must be used in conjunction with the car command.

The packet color-to-drop priority mappings are fixed.

· The red color is mapped to drop priority 2.

· The yellow color is mapped to drop priority 1.

· The green color is mapped to drop priority 0.

Examples

# Configure the action of mapping packet colors to drop priority values in traffic behavior behavior1.

<Sysname> system-view

[Sysname] traffic behavior behavior1

[Sysname-behavior-behavior1] car cir 1600

[Sysname-behavior-behavior1] primap color-map-dp

Related commands

primap pre-defined color

Use primap pre-defined color to configure the action of mapping source precedence to target precedence through the specified colored priority mapping table for a traffic behavior.

Use undo primap pre-defined color to delete the action.

Syntax

primap pre-defined color { dot1p-dot1p | dot1p-dp | dot1p-dscp | dot1p-exp | dot1p-lp | dscp-dot1p | dscp-dp | dscp-dscp | dscp-exp | dscp-lp | exp-dot1p | exp-dp | exp-dscp | exp-exp | exp-lp }

undo primap pre-defined color { dot1p-dot1p | dot1p-dp | dot1p-dscp | dot1p-exp | dot1p-lp | dscp-dot1p | dscp-dp | dscp-dscp | dscp-exp | dscp-lp | exp-dot1p | exp-dp | exp-dscp | exp-exp | exp-lp }

Default

No priority mapping action is configured in a traffic behavior.

Views

Traffic behavior view

Predefined user roles

network-admin

Parameters

pre-defined: Specifies predefined priority mapping tables.

color: Uses colored priority mapping tables for priority mapping.

The device provides the following types of priority map.

Table 5 Priority maps

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

Usage guidelines

This command must be used in conjunction with the car command.

Examples

# Configure the action of mapping DSCP values to drop priority through the colored DSCP-to-drop mapping table in traffic behavior behavior1.

<Sysname> system-view

[Sysname] traffic behavior behavior1

[Sysname-behavior-behavior1] car cir 1600

[Sysname-behavior-behavior1] primap pre-defined color dscp-dp

Related commands

display qos map-table color

primap color-map-dp

redirect

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

Use undo redirect to restore the default.

Syntax

In standalone mode:

redirect { access-vpn vpn-instance vpn-instance-name | cpu | failover-group group-name | http-to-cpu | https-to-cpu | interface interface-type interface-number | next-hop [ vpn-instance vpn-instance-name ] { ipv4-add1 [ track track-entry-number ] [ ipv4-add2 [ track track-entry-number ] ] | ipv6-add1 [ track track-entry-number ] [ ipv6-add2 [ track track-entry-number ] ] } | slot slot-number }

undo redirect { access-vpn | cpu | failover-group group-name | http-to-cpu | https-to-cpu | interface interface-type interface-number | next-hop | slot slot-number }

In IRF mode:

undo redirect { access-vpn | cpu | failover-group group-name | http-to-cpu | https-to-cpu | interface interface-type interface-number | next-hop | chassis chassis-number slot slot-number }

Default

No traffic redirecting action is configured.

Views

Traffic behavior view

Predefined user roles

network-admin

Parameters

access-vpn vpn-instance vpn-instance-name: Redirects traffic to an MPLS L3VPN instance specified by its name, a case-sensitive string of 1 to 31 characters.

cpu: Redirects traffic to the CPU.

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

http-to-cpu: Redirects HTTP requests to the CPU.

https-to-cpu: Redirects HTTPS requests to the CPU.

interface interface-type interface-number: Redirects traffic to an interface specified by its type and number. To redirect traffic to a tunnel interface, set the interface type to tunnel. To redirect traffic to a Layer 2 aggregate interface, set the interface type to bridge-aggregation. To redirect traffic to a Layer 3 aggregate interface, set the interface type to route-aggregation.

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.

vpn-instance vpn-instance-name: Specifies the MPLS L3VPN instance to which the next hop belongs. The vpn-instance-name argument represents the VPN instance name, a case-sensitive string of 1 to 31 characters. If the next hop belongs to the public network, do not specify this option.

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

slot slot-number: Redirects traffic to a card specified by its slot number. (In standalone mode.)

chassis chassis-number slot slot-number: Redirects traffic to 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. (In IRF mode.)

Usage guidelines

If you execute the redirect command multiple times in the same traffic behavior, all configured actions take effect at the same time. Exceptions are that the redirect cpu, redirect http-to-cpu, and redirect https-to-cpu commands are mutually exclusive.

For IPoE Web authentication, you must configure the redirect http-to-cpu or redirect https-to-cpu command. If a user performs IPoE Web authentication through the Web browser but the HTTP request is not destined for the portal Web server, the access device redirects the request to the CPU. The CPU pushes the Web authentication page to the user.

To prevent the CPU from receiving a large number of HTTP requests during IPoE Web authentication, use the ip subscriber http-fast-reply enable command to enable the HTTP request fast reply function. This function reduces the CPU load by identifying HTTP requests in hardware and automatically replying with HTTP responses. For more information about the ip subscriber http-fast-reply enable command, see IPoE commands in Layer 2—WAN Access Command Reference.

Only CSPEX (except CSPEX-1204 and CSPEX-1104-E) and CEPC cards support redirecting traffic to Layer 3 Ethernet interfaces and loopback interfaces, and they do not support redirecting traffic to Layer 3 aggregate interfaces.

If the next hop for redirection is in an MPLS network, IP TTL is always copied to the inner label TTL for packets redirected to the next hop. For more information about TTL propagation, see basic MPLS in MPLS Configuration Guide.

Examples

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

<Sysname> system-view

[Sysname] traffic behavior database

[Sysname-behavior-database] redirect interface gigabitethernet 3/1/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

# Configure redirecting traffic to VPN instance vpn1 in traffic behavior database.

<Sysname> system-view

[Sysname] traffic behavior database

[Sysname-behavior-database] redirect access-vpn vpn-instance vpn1

Related commands

classifier behavior

qos policy

traffic behavior

remark account-level

Use remark account-level to configure an accounting level marking action in a traffic behavior.

Use undo remark account-level to restore the default.

Syntax

remark account-level account-level

undo remark account-level

Default

No accounting level marking action is configured.

Views

Traffic behavior view

Predefined user roles

network-admin

Parameters

account-level: Specifies an accounting level in the range of 1 to 8. Do not specify accounting level 1. The traffic for this accounting level also includes non-ITA service traffic, and accounting for ITA service traffic will be inaccurate.

Usage guidelines

If QoS policies that contain accounting level marking actions are applied globally, to an interface, and to a user profile, configure an ITA policy for each accounting level. For information about ITA policies, see AAA in Security Configuration Guide and Security Command Reference.

The remark account-level command takes effect only on packets from users that are configured with the same accounting level in an ITA policy.

This command is available only on CSPEX (except CSPEX-1204) and CEPC cards.

Examples

# Configure traffic behavior database to mark matching packets with accounting level 3.

<Sysname> system-view

[Sysname] traffic behavior database

[Sysname-behavior-database] remark account-level 3

remark dot1p

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

Use undo remark dot1p to restore the default.

Syntax

remark [ green | red | yellow ] dot1p dot1p-value

undo remark [ green | red | yellow ] dot1p

remark dot1p customer-dot1p-trust

undo remark dot1p

Default

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

Views

Traffic behavior view

Predefined user roles

network-admin

Parameters

green: Specifies green packets. CSPC-GE16XP4L-E, CSPC-GE24L-E, CSPC-GP24GE8XP2L-E, CSPEX, and CEPC cards do not support this keyword.

red: Specifies red packets. CSPC-GE16XP4L-E, CSPC-GE24L-E, CSPC-GP24GE8XP2L-E, CSPEX, and CEPC cards do not support this keyword.

yellow: Specifies yellow packets. CSPC-GE16XP4L-E, CSPC-GE24L-E, CSPC-GP24GE8XP2L-E, CSPEX, and CEPC cards do not support this keyword.

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

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

Usage guidelines

The remark dot1p dot1p-value and remark dot1p customer-dot1p-trust commands override each other in the same traffic behavior.

The remark dot1p customer-dot1p-trust command does not take effect on single-tagged packets.

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

Examples

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

<Sysname> system-view

[Sysname] traffic behavior database

[Sysname-behavior-database] remark dot1p 2

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

<Sysname> system-view

[Sysname] traffic behavior database

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

remark drop-precedence

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

Use undo remark drop-precedence to restore the default.

Syntax

remark drop-precedence drop-precedence-value

undo remark drop-precedence

Default

No drop priority marking action is configured.

Views

Traffic behavior view

Predefined user roles

network-admin

Parameters

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

Usage guidelines

On CSPC (except CSPC-GE16XP4L-E, CSPC-GE24L-E, and CSPC-GP24GE8XP2L-E) and CMPE-1104 cards, a drop priority marking action takes effect only when the QoS policy is applied to the inbound direction.

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

Examples

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

<Sysname> system-view

[Sysname] traffic behavior database

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

remark dscp

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

Use undo remark dscp to restore the default.

Syntax

remark [ green | red | yellow ] dscp dscp-value

undo remark [ green | red | yellow ] dscp

Default

No DSCP marking action is configured.

Views

Traffic behavior view

Predefined user roles

network-admin

Parameters

green: Specifies green packets. CSPC-GE16XP4L-E, CSPC-GE24L-E, CSPC-GP24GE8XP2L-E, CSPEX, and CEPC cards do not support this keyword.

red: Specifies red packets. CSPC-GE16XP4L-E, CSPC-GE24L-E, CSPC-GP24GE8XP2L-E, CSPEX, and CEPC cards do not support this keyword.

yellow: Specifies yellow packets. CSPC-GE16XP4L-E, CSPC-GE24L-E, CSPC-GP24GE8XP2L-E, CSPEX, and CEPC cards do not support this keyword.

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

Table 6 DSCP keywords and values

Keyword	DSCP value (binary)	DSCP value (decimal)
default	000000	0
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
ef	101110	46

Usage guidelines

The remark tunnel-dscp command is mutually exclusive with the remark dscp command in a traffic behavior.

Colored packets are not marked on CSPC-GE16XP4L-E, CSPC-GE24L-E, CSPC-GP24GE8XP2L-E, CSPEX, or CEPC cards.

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

Examples

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

<Sysname> system-view

[Sysname] traffic behavior database

[Sysname-behavior-database] remark dscp 6

remark ip-precedence

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

Use undo remark ip-precedence to restore the default.

Syntax

remark ip-precedence ip-precedence-value

undo remark ip-precedence

Default

No IP precedence marking action is configured.

Views

Traffic behavior view

Predefined user roles

network-admin

Parameters

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

Usage guidelines

The remark tunnel-dscp command is mutually exclusive with the remark ip-precedence command in a traffic behavior.

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

Examples

# Set the IP precedence to 6 for packets.

<Sysname> system-view

[Sysname] traffic behavior database

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

remark local-precedence

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

Use undo remark local-precedence to restore the default.

Syntax

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

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

Default

No local precedence marking action is configured.

Views

Traffic behavior view

Predefined user roles

network-admin

Parameters

green: Specifies green packets. CSPC-GE16XP4L-E, CSPC-GE24L-E, CSPC-GP24GE8XP2L-E, CSPEX, and CEPC cards do not support this keyword.

red: Specifies red packets. CSPC-GE16XP4L-E, CSPC-GE24L-E, CSPC-GP24GE8XP2L-E, CSPEX, and CEPC cards do not support this keyword.

yellow: Specifies yellow packets. CSPC-GE16XP4L-E, CSPC-GE24L-E, CSPC-GP24GE8XP2L-E, CSPEX, and CEPC cards do not support this keyword.

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

Usage guidelines

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

By marking the local precedence, you assign matching packets to the queue corresponding to the local precedence value. You can use the display qos queue-statistics interface outbound command to display outgoing traffic statistics collected for interfaces on a per-queue basis. The outgoing traffic statistics are displayed only if you have enabled queue-based traffic accounting in the outbound direction.

On CSPC (except CSPC-GE16XP4L-E, CSPC-GE24L-E, and CSPC-GP24GE8XP2L-E) and CMPE-1104 cards, a local precedence marking action takes effect only when the QoS policy is applied to the inbound direction.

Colored packets are not marked on CSPC-GE16XP4L-E, CSPC-GE24L-E, CSPC-GP24GE8XP2L-E, CSPEX, or CEPC cards.

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

Related commands

display qos queue-statistics interface outbound

qos queue-statistics

remark qos-local-id

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

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

Syntax

remark qos-local-id local-id-value

undo remark qos-local-id

Default

No local QoS ID marking action is configured.

Views

Traffic behavior view

Predefined user roles

network-admin

Parameters

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

Usage guidelines

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

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

On CSPEX cards (except CSPEX-1204 and CSPEX-1104-E) and CEPC cards, a local QoS ID marking action takes effect only when the QoS policy is applied to the outbound direction.

Examples

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

<Sysname> system-view

[Sysname] traffic behavior database

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

remark service-class

Use remark service-class to configure an action of marking the MPLS TE service class in a traffic behavior.

Use undo remark service-class to restore the default.

Syntax

remark service-class service-class-value

undo remark service-class

Default

No MPLS TE service class marking action is configured.

Views

Traffic behavior view

Predefined user roles

network-admin

Parameters

service-class-value: Specifies the MPLS TE service class in the range of 1 to 15.

Usage guidelines

If the remark service-class command is configured in a QoS policy:

· The QoS policy can only be applied to the inbound direction of an interface.

· Only one MPLS TE service class marking action can be configured for packets with the same MPLS EXP value on an interface. To modify the MPLS TE service class to be marked, you must remove the existing service class setting and configure a new service class value.

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

You can use the mpls te service-class command to set the MPLS TE service class. For more information, see MPLS TE commands in MPLS Command Reference.

This command is available only on CSPEX (except CSPEX-1204 and CSPEX-1104-E) and CEPC cards.

Examples

# Configure an action of marking the MPLS TE service class as 2.

<Sysname> system-view

[Sysname] traffic behavior data

[Sysname-behavior-data] remark service-class 2

remark service-id

Use remark service-id to configure an action of marking the EDSG service ID in a traffic behavior.

Use undo remark service-id to restore the default.

Syntax

remark service-id service-id

undo remark service-id

Default

No EDSG service ID marking action is configured.

Views

Traffic behavior view

Predefined user roles

network-admin

Parameters

service-id: Specifies the EDSG service ID in the range of 1 to 8. Only the values 1 through 4 are supported in the current software version.

Usage guidelines

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

The remark service-id command takes effect only when the QoS policy is applied to an interface or globally.

The remark service-id command takes effect only on packets from users that use the EDSG service ID specified in the remark service-id command.

This command is available only on CSPEX (except CSPEX-1204 and CSPEX-1104-E) and CEPC cards.

Examples

# Configure an action of marking the EDSG service ID as 2.

<Sysname> system-view

[Sysname] traffic behavior database

[Sysname-behavior-database] remark service-id 2

Related commands

service policy (BRAS Services Command Reference)

service-id (BRAS Services Command Reference)

remark tunnel-dscp

Use remark tunnel-dscp to configure an outer DSCP marking action in a traffic behavior.

Use undo remark tunnel-dscp to restore the default.

Syntax

remark tunnel-dscp dscp-value

undo remark tunnel-dscp

Default

No outer DSCP marking action is configured.

Views

Traffic behavior view

Predefined user roles

network-admin

Parameters

dscp-value: Specifies the DSCP value to be set for the outer IP header of tunneled packets. The DSCP value can be a number from 0 to 63 or a keyword in Table 6.

Usage guidelines

This command takes effect on GRE packets and VXLAN packets.

The outer DSCP value marking action takes effect only when the QoS policy is applied to an interface or globally.

The remark tunnel-dscp command is mutually exclusive with the remark dscp or remark ip-precedence command in one traffic behavior.

If the tunnel tos command is configured on a VXLAN tunnel interface, the ToS value in the outer IP header for broadcast and multicast packets received from local sites cannot be modified by using the remark tunnel-dscp command. For more information about the tunnel tos command, see tunneling commands in Layer 3—IP Services Command Reference.

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

This command is available only on CSPEX (except CSPEX-1204 and CSPEX-1104-E) and CEPC cards.

Examples

# Configure traffic behavior data to mark matching packets with DSCP value 2 in the outer IP header of tunneled packets.

<Sysname> system-view

[Sysname] traffic behavior data

[Sysname-behavior-data] remark tunnel-dscp 2

traffic behavior

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

Use undo traffic behavior to delete a traffic behavior.

Syntax

traffic behavior behavior-name

undo traffic behavior behavior-name

Default

No traffic behaviors exist.

Views

System view

Predefined user roles

network-admin

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 qppb-manipulation | insert-before before-classifier-name ] *

undo classifier classifier-name

Default

No traffic behavior is associated with a traffic class.

Views

QoS policy view

Predefined user roles

network-admin

Parameters

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

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

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

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

Usage guidelines

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

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

Examples

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

<Sysname> system-view

[Sysname] qos policy user1

[Sysname-qospolicy-user1] classifier database behavior test

# Associate traffic class database with traffic behavior test in QoS policy user1, and specify that the class-behavior association applies only to QPPB.

<Sysname> system-view

[Sysname] qos policy user1

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

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

<Sysname> system-view

[Sysname] qos policy user1

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

Related commands

qos policy

control-plane

Use control-plane to enter control plane view.

Syntax

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

Parameters

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

Usage guidelines

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

Examples

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

<Sysname> system-view

[Sysname] control-plane slot 3

[Sysname-cp-slot3]

display qos policy

Use display qos policy to display QoS policies.

Syntax

In standalone mode:

display qos policy user-defined [ policy-name [ classifier classifier-name ] ] [ slot slot-number ]

In IRF mode:

display qos policy user-defined [ policy-name [ classifier classifier-name ] ] [ chassis chassis-number slot slot-number ]

Views

Any view

Predefined user roles

network-admin

network-operator

Parameters

user-defined: Specifies user-defined QoS policies.

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

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

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

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

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 5120 (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 mpls-exp 4

Classifier: 3 (ID 102)

Behavior: 3

-none-

For the output description, see Table 1 and Table 4.

display qos policy control-plane

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

Syntax

In standalone mode:

display qos policy control-plane slot slot-number

In IRF mode:

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

Views

Any view

Predefined user roles

network-admin

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

<Sysname> display qos policy control-plane slot 2

Control plane slot 2

Direction: Inbound

Policy: 1

Classifier: 1

Operator: AND

Rule(s) :

If-match acl 2000

Behavior: 1

Marking:

Remark dscp 3

Committed Access Rate:

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

Green action : pass

Yellow action : pass

Red action : discard

Green packets : 0 (Bytes)

0 (bps)

Yellow packets: 0 (Bytes)

0 (bps)

Red packets : 0 (Bytes)

Classifier: 2

Operator: AND

Rule(s) :

If-match protocol ipv6

Behavior: 2

Accounting enable:

3268134 (Packets)

1000 (pps)

Filter enable: Permit

Marking:

Remark mpls-exp 4

Classifier: 3

Operator: AND

Rule(s) :

-none-

Behavior: 3

-none-

Table 7 Command output

Field	Description
Direction	Inbound direction on the control plane.
Green packets	Total number of bytes for green packets and average rate of green packets in the most recent statistics collection interval. The interval is set by using the flow-interval command (see Ethernet interface commands in Interface Command Reference).
Yellow packets	Total number of bytes for yellow packets and average rate of yellow packets in the most recent statistics collection interval. The interval is set by using the flow-interval command (see Ethernet interface commands in Interface Command Reference).
Red packets	Total number of bytes for red packets and average rate of red packets in the most recent statistics collection interval. The interval is set by using the flow-interval command (see Ethernet interface commands in Interface Command Reference).

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

display qos policy control-plane pre-defined

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

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

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

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

Pre-defined policy information slot 3

Protocol Priority Bandwidth Group

Default N/A 7168 (kbps) N/A

IS-IS 29 8192 (kbps) critical

VRRP 36 512 (kbps) important

OSPF Multicast 30 5120 (kbps) critical

IGMP 18 512 (kbps) important

OSPFv3 Unicast 30 5120 (kbps) critical

OSPFv3 Multicast 30 5120 (kbps) critical

VRRPv6 36 512 (kbps) important

ARP 12 1024 (kbps) normal

DHCP Snooping 18 3072 (kbps) redirect

802.1x 12 128 (kbps) important

STP 36 256 (kbps) critical

LACP 36 64 (kbps) critical

MVRP 18 256 (kbps) critical

TTL Expires 18 64 (kbps) monitor

IPOPTION 18 64 (kbps) normal

BGPv6 24 1024 (kbps) critical

Hop Limit Expires 18 64 (kbps) monitor

IPOPTIONv6 18 64 (kbps) normal

LLDP 24 64 (kbps) important

DLDP 24 64 (kbps) critical

ARP Snooping 18 1024 (kbps) redirect

DHCPv6 18 3072 (kbps) normal

Table 8 Command output

Field	Description
Pre-defined control plane policy	Contents of the predefined control plane QoS policy.

display qos policy global

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

Syntax

In standalone mode:

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

In IRF mode:

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

Views

Any view

Predefined user roles

network-admin

network-operator

Parameters

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

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

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 a direction, this command displays both QoS policies applied globally.

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 5120 (Bytes), EBS 512 (Bytes)

Green action : pass

Yellow action : pass

Red action : discard

Green packets : 0 (Bytes)

0 (bps)

Yellow packets: 0 (Bytes)

0 (bps)

Red packets : 0 (Bytes)

0 (bps)

Table 9 Command output

Field	Description
Direction	Direction (inbound or outbound ) in which the QoS policy is applied.
Green packets	Total number of bytes for green packets and average rate of green packets in the most recent statistics collection interval. The interval is set by using the flow-interval command (see Ethernet interface commands in Interface Command Reference).
Yellow packets	Total number of bytes for yellow packets and average rate of yellow packets in the most recent statistics collection interval. The interval is set by using the flow-interval command (see Ethernet interface commands in Interface Command Reference).
Red packets	Total number of bytes for red packets and average rate of red packets in the most recent statistics collection interval. The interval is set by using the flow-interval command (see Ethernet interface commands in Interface Command Reference).

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

display qos policy interface

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

Syntax

In standalone mode:

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

In IRF mode:

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

Views

Any view

Predefined user roles

network-admin

network-operator

Parameters

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

slot slot-number: Specifies a card by its slot number. Only virtual interfaces such as aggregate interfaces support this option. If you do not specify a card, this command displays QoS policies on 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 a card, this command displays QoS policies on the global active MPU. Only virtual interfaces such as aggregate interfaces support this option. (In IRF mode.)

all: Displays information about QoS policies applied to a logical interface on all cards. If you do not specify this keyword, the command displays information about QoS policies applied to a logical interface on the global active MPU.

inbound: Specifies the QoS policies applied to the inbound direction.

outbound: Specifies the QoS policies applied to the outbound direction.

Usage guidelines

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

Examples

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

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

Interface: GigabitEthernet3/1/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 5120 (Bytes), EBS 512 (Bytes)

Green action : pass

Yellow action : pass

Red action : discard

Green packets : 0 (Bytes)

0 (bps)

Yellow packets: 0 (Bytes)

0 (bps)

Red packets : 0 (Bytes)

0 (bps)

# Display the QoS policy applied to the incoming traffic of interface Route-Aggregation1 on all cards.

<Sysname> display qos accounting policy interface Route-Aggregation 1 all inbound

slot 1:

Interface: Route-Aggregation1

Direction: Inbound

Policy: p

Classifier: c

Operator: AND

Rule(s) :

If-match any

Behavior: b

Marking:

Remark dscp af11

slot 2:

Interface: Route-Aggregation1

Direction: Inbound

Policy: p

Classifier: c

Operator: AND

Rule(s) :

If-match any

Behavior: b

Marking:

Remark dscp af11

# Display the QoS policies applied to all interfaces.

<Sysname> display qos policy interface

Interface: GigabitEthernet3/1/1

Direction: Inbound

Mode : Share

Policy: a

Classifier: a

Operator: AND

Rule(s) :

If-match any

Behavior: a

Committed Access Rate:

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

Green action : pass

Yellow action : pass

Red action : discard

Green packets : 0 (Bytes)

0 (bps)

Yellow packets: 0 (Bytes)

0 (bps)

Red packets : 0 (Bytes)

0 (bps)

Table 10 Command output

Field	Description
Direction	Direction in which the QoS policy is applied to the interface.
Mode	Sharing mode for QoS and ACL resources. This field appears only if a QoS policy is applied with the share-mode keyword specified.
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	Total number of bytes for green packets and average rate of green packets in the most recent statistics collection interval. The interval is set by using the flow-interval command (see Ethernet interface commands in Interface Command Reference).
Yellow packets	Total number of bytes for yellow packets and average rate of yellow packets in the most recent statistics collection interval. The interval is set by using the flow-interval command (see Ethernet interface commands in Interface Command Reference).
Red packets	Total number of bytes for red packets and average rate of red packets in the most recent statistics collection interval. The interval is set by using the flow-interval command (see Ethernet interface commands in Interface Command Reference).
Redirect to next-hop	Redirect traffic to a next hop. If the next hop does not exist, this field is displayed as Redirect to next-hop N/A.

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

display qos vlan-policy

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

Syntax

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

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: Specifies the QoS policies applied to the inbound direction.

outbound: Specifies the QoS policies applied to the outbound direction.

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 the QoS policies applied to the inbound direction and the QoS policies applied to the outbound direction.

Examples

# Display QoS policies applied to VLAN 2.

<Sysname> display qos vlan-policy vlan 2

Vlan 2

Direction: Outbound

Policy: 1

Classifier: 1

Operator: AND

Rule(s) :

If-match acl 2000

Behavior: 1

Marking:

Remark dscp 3

Committed Access Rate:

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

Green action : pass

Yellow action : pass

Red action : discard

Green packets : 0 (Bytes)

0 (bps)

Yellow packets: 0(Bytes)

0 (bps)

Red packets : 0(Bytes)

0 (bps)

Classifier: 2

Operator: AND

Rule(s) :

If-match protocol ipv6

Behavior: 2

3268134 (Packets)

1000 (pps)

Filter enable: Permit

Marking:

Classifier: 3

Operator: AND

Rule(s) :

-none-

Behavior: 3

-none-

Table 11 Command output

Field	Description
Direction	Direction in which the QoS policy is applied for the VLAN.
Green packets	Total number of bytes for green packets and average rate of green packets in the most recent statistics collection interval. The interval is set by using the flow-interval command (see Ethernet interface commands in Interface Command Reference).
Yellow packets	Total number of bytes for yellow packets and average rate of yellow packets in the most recent statistics collection interval. The interval is set by using the flow-interval command (see Ethernet interface commands in Interface Command Reference).
Red packets	Total number of bytes for red packets and average rate of red packets in the most recent statistics collection interval. The interval is set by using the flow-interval command (see Ethernet interface commands in Interface Command Reference).

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

qos apply policy

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

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

Syntax

qos apply policy policy-name { inbound | outbound } [ preorder preorder-value ] [ share-mode ]

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

Default

No QoS policy is applied.

Views

Control plane view

Interface view

Predefined user roles

network-admin

Parameters

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

inbound: Applies the QoS policy to the inbound direction.

outbound: Applies the QoS policy to the outbound direction. This keyword is not supported in control plane view.

preorder preorder-value: Specifies the priority that the traffic behavior in a QoS policy is executed. The greater the priority value, the higher the priority. The preorder-value argument can only be 1 in the current software version. This option is not supported in control plane view.

share-mode: Applies the QoS policy in sharing mode. If you do not specify this keyword, this command applies the QoS policy in non-sharing mode. This keyword is not supported in control plane view.

Usage guidelines

A QoS policy applied to the inbound direction of an interface cannot contain any of these queuing actions: queue ef, queue af, or queue wfq.

On the following cards, if you apply QoS policies separately to an aggregate interface and a member port of the aggregate interface, the QoS policy applied to the aggregate interface effect:

· CEPC.

· CSPEX.

· CSPC-GE16XP4L-E, CSPC-GE24L-E, and CSPC-GP24GE8XP2L-E.

The QoS policy applied to the member port takes effect after it leaves the aggregation group.

A QoS policy configured with CBQ is not supported in control plane view.

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

· if-match control-plane protocol

· if-match control-plane protocol-group

· if-match acl

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

¡ The used ACL must be an advanced ACL.

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

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

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

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

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

· The total bandwidth of all interfaces that share one QoS and ACL resource cannot exceed 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.

If you specify the preorder preorder-value option when applying a QoS policy, follow these restrictions and guidelines:

· This option is supported only in the inbound direction of interfaces on CSPEX and CEPC cards.

· Packets preferentially match the traffic classes in the QoS policy.

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.

Examples

# Apply QoS policy USER1 to the outgoing traffic of GigabitEthernet 3/1/1.

<Sysname> system-view

[Sysname] interface gigabitethernet 3/1/1

[Sysname-GigabitEthernet3/1/1] qos apply policy USER1 outbound

# Apply QoS policy aaa 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 aaa inbound

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

<Sysname> system-view

[Sysname] interface gigabitethernet 3/1/1

[Sysname-GigabitEthernet3/1/1]qos apply policy aaa outbound share-mode

qos apply policy global

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

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

Syntax

qos apply policy policy-name global { inbound | outbound } [ preorder preorder-value ]

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

Default

No QoS policy is applied globally.

Views

System view

Predefined user roles

network-admin

Parameters

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

inbound: Applies the QoS policy to the inbound direction.

outbound: Applies the QoS policy to the outbound direction.

preorder preorder-value: Specifies the order in which QoS policies applied in the same direction are executed. The greater the value, the higher the priority. The preorder-value argument can only be 1 in the current software version. A QoS policy configured with this option is executed before a QoS policy that is not configured with this option. This option takes effect only in the inbound direction on CSPEX and CEPC cards.

Usage guidelines

A QoS policy applied globally takes effect on traffic of all interfaces.

Examples

# Globally apply QoS policy user1 to the incoming traffic.

<Sysname> system-view

[Sysname] qos apply policy user1 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 policy policy-name

undo qos policy policy-name

Default

No QoS policies exist.

Views

System view

Predefined user roles

network-admin

Parameters

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

Usage guidelines

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

Examples

# Create a QoS policy named user1.

<Sysname> system-view

[Sysname] qos policy user1

[Sysname-qospolicy-user1]

Related commands

classifier behavior

qos apply policy

qos apply policy global

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 }

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

Default

No QoS policy is applied to a VLAN.

Views

System view

Predefined user roles

network-admin

Parameters

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

vlan vlan-id-list: Specifies a space-separated list of up to eight VLAN IDs or a VLAN ID range in the form of vlan-id1 to vlan-id2. The value for vlan-id2 must be greater than or equal to the value for vlan-id1. The value range for the vlan-id argument is 1 to 4094.

inbound: Applies the QoS policy to the inbound direction.

outbound: Applies the QoS policy to the outbound direction.

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

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

<Sysname> reset qos policy control-plane slot 3

reset qos policy global

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

Syntax

reset qos policy global [ inbound | outbound ]

Views

User view

Predefined user roles

network-admin

Parameters

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 the statistics for both QoS policies applied globally.

Examples

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

<Sysname> reset qos policy global inbound

reset qos vlan-policy

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

Syntax

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

Views

User view

Predefined user roles

network-admin

Parameters

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

inbound: Specifies the QoS policies applied to the inbound direction.

outbound: Specifies the QoS policies applied to the outbound direction.

Usage guidelines

If you do not specify a direction, this command clears the statistics for both the QoS policies applied to the inbound direction and the QoS policies applied to the outbound direction .

Examples

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

<Sysname> reset qos vlan-policy vlan 2

Exclusive bandwidth commands

display qos exclusive-bandwidth interface outbound

Use display qos exclusive-bandwidth interface outbound to display exclusive bandwidth settings in the outbound direction of interfaces.

Syntax

In standalone mode:

display qos exclusive-bandwidth interface [ interface-type interface-number ] outbound [ slot slot-number ]

In IRF mode:

display qos exclusive-bandwidth interface [ interface-type interface-number ] outbound [ chassis chassis-number slot slot-number ]

Views

Any view

Predefined user roles

network-admin

network-operator

Parameters

interface-type interface-number: Specifies an interface by its type and number. If you do not specify an interface, this command displays exclusive bandwidth settings for all interfaces.

slot slot-number: Specifies a card by its slot number. Only virtual interfaces such as aggregate interfaces support this option. (In standalone mode.)

Examples

# Display the exclusive bandwidth setting for Ten-GigabitEthernet 3/1/1.

<Sysname> display qos exclusive-bandwidth interface ten-gigabitethernet 3/1/1 outbound

Ten-GigabitEthernet3/1/1 exclusive-bandwidth: 500 kbps

Outbound traffic statistics:

Total passed: 1 packets, 2 bytes

Total discarded: 3 packets, 4 bytes

Last 30 seconds pass rate: 0 pps, 0 bps

Last 30 seconds discard rate: 0 pps, 0 bps

Table 12 Command output

Field	Description
Total passed	Total number of packets and total number of bytes allowed to pass.
Total discarded	Total number of packets and total number of bytes dropped.
Last 30 seconds pass rate	Number of packets and number of bytes allowed to pass per second in the last 30 seconds.
Last 30 seconds discard rate	Number of packets and number of bytes dropped per second in the last 30 seconds.

Related commands

qos exclusive-bandwidth

Use qos exclusive-bandwidth to set the exclusive bandwidth on an interface.

Use undo qos exclusive-bandwidth to cancel the exclusive bandwidth setting on an interface.

Syntax

qos exclusive-bandwidth bandwidth-value

undo qos exclusive-bandwidth

Default

No exclusive bandwidth is set on an interface.

Views

Layer 3 Ethernet interface view

Layer 3 aggregate interface view

Predefined user roles

network-admin

Parameters

bandwidth-value: Specifies the exclusive bandwidth value in kbps. The value range for this argument is:

· 300 to 950000 for GE interfaces.

· 300 to 9500000 for 10-GE interfaces.

· 300 to 38000000 for 40-GE interfaces.

· 300 to 95000000 for 100-GE interfaces.

· 300 to 95000000 for Layer 3 aggregate interfaces.

Usage guidelines

This command is available only on CSPEX (except CSPEX-1204 and CSPEX-1104-E) and CEPC cards.

The exclusive bandwidth on an interface is reserved for specific features and cannot be shared with other features. The amount of exclusive bandwidth is deducted from the interface bandwidth. For example, if you set the exclusive bandwidth for CRLSP, the exclusive bandwidth can only be used by CRLSP. For more information about the CRLSP exclusive bandwidth, see static CRLSP configuration in MPLS Configuration Guide.

The exclusive bandwidth feature is mutually exclusive with the HQoS feature. If one feature has been configured on an interface, the other feature cannot be configured successfully.

Examples

# Set the exclusive bandwidth to 500 kbps on Ten-GigabitEthernet 3/1/1.

<Sysname> system-view

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

[Sysname-Ten-GigabitEthernet3/1/1] qos exclusive-bandwidth 500

Related commands

display qos exclusive-bandwidth interface outbound

Priority mapping commands

Priority map commands

display qos map-table

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

Syntax

Views

Any view

Predefined user roles

network-admin

network-operator

Parameters

inbound: Specifies priority maps for the inbound direction.

The device provides the following types of priority map.

Table 13 Priority maps

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

Usage guidelines

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

If you do not specify any parameters, the command (namely, the display qos map-table command) displays the configuration of all priority maps in both directions, including colored and uncolored 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 DIRECTION: inbound

IMPORT : EXPORT

0 : 0

1 : 1

2 : 2

3 : 3

4 : 4

5 : 5

6 : 6

7 : 7

Table 14 Command output

Field	Description
MAP-TABLE NAME	Name of the priority map.
TYPE	Type of the priority map.
DIRECTION	Direction 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 ] { inbound [ dot1p-dot1p | dot1p-dp | dot1p-dscp | dot1p-exp | dot1p-lp | dscp-dot1p | dscp-dp | dscp-dscp | dscp-exp | dscp-lp | exp-dot1p | exp-dp | exp-dscp | exp-exp | exp-lp ] | outbound [ dot1p-dot1p | dot1p-dscp | dot1p-exp | dscp-dot1p | dscp-dscp | dscp-exp | exp-dot1p | exp-dscp | exp-exp ] }

Views

Any view

Predefined user roles

network-admin

network-operator

Parameters

green: Specifies green packets.

yellow: Specifies yellow packets.

red: Specifies red packets.

inbound: Specifies priority maps for the inbound direction.

outbound: Specifies priority maps for the outbound direction.

For the description of other keywords, see Table 13.

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 priority map, this command displays the configuration of all colored priority maps.

Examples

# Display the configuration of the EXP-local priority map for incoming green packets.

<Sysname> display qos map-table color green inbound exp-lp

MAP-TABLE NAME: exp-lp TYPE: pre-define COLOR: green DIRECTION: inbound

IMPORT : EXPORT

0 : 0

1 : 1

2 : 2

3 : 3

4 : 4

5 : 5

6 : 6

7 : 7

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

display qos map-table interface

Use display qos map-table interface to display flexible priority maps applied to interfaces.

Syntax

In standalone mode:

display qos map-table interface [ interface-type interface-number ] [ slot slot-number ] [ inbound | outbound ]

In IRF mode:

display qos map-table interface [ interface-type interface-number ] [ chassis chassis-number slot slot-number ] [ inbound | outbound ]

Views

Any view

Predefined user roles

network-admin

network-operator

Parameters

interface-type interface-number: Specifies an interface by its type and number. If you do not specify an interface, this command displays flexible priority maps applied to all interfaces.

slot slot-number: Specifies a card by its slot number. If you do not specify a card, this command displays the flexible priority maps applied on 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 the flexible priority maps applied on all cards. (In IRF mode.)

inbound: Specifies flexible priority maps applied to the inbound direction.

outbound: Specifies flexible priority maps applied to the outbound direction.

Usage guidelines

If you do not specify a direction, this command displays both the flexible priority maps applied to the inbound direction and the flexible priority maps applied to the outbound direction.

Examples

# Display the flexible priority map applied to GigabitEthernet 3/1/1.

<Sysname> display qos map-table interface gigabitethernet 3/1/1

Interface: GigabitEthernet3/1/1

Direction: Inbound

Map table name: user1

Related commands

display qos map-table name

qos map-table name

display qos map-table name

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

Syntax

display qos map-table name [ map-table-name ]

Views

Any view

Predefined user roles

network-admin

network-operator

Parameters

map-table-name: Specifies a flexible priority map by its name, a case-sensitive string of 1 to 31 characters. If you do not specify a flexible priority map, this command displays the configuration of all flexible priority maps.

Examples

# Display the configuration of flexible priority map user1.

<Sysname> display qos map-table name user1

Map table name: user1 Item: 4

Type Import Export

dot1p-lp 0 2

dot1p-lp 1 0

dscp-dp 2 1

dscp-dp 3 3

Related commands

display qos map-table interface

qos map-table name

import (flexible priority map view)

Use import to configure mappings for a flexible priority map.

Use undo import to delete mappings of a flexible priority map.

Syntax

{ dot1p-dot1p | dot1p-dp | dot1p-dscp | dot1p-exp | dot1p-lp | dscp-dot1p | dscp-dp | dscp-dscp | dscp-exp | dscp-lp | exp-dot1p | exp-dp | exp-dscp | exp-exp | exp-lp | lp-dot1p | lp-dp | lp-dscp | lp-exp | lp-phb } import import-value-list export export-value

undo { dot1p-dot1p | dot1p-dp | dot1p-dscp | dot1p-exp | dot1p-lp | dscp-dot1p | dscp-dp | dscp-dscp | dscp-exp | dscp-lp | exp-dot1p | exp-dp | exp-dscp | exp-exp | exp-lp | lp-dot1p | lp-dp | lp-dscp | lp-exp | lp-phb } import import-value-list

Default

No mappings exist in a flexible priority map.

Views

Flexible priority map view

Predefined user roles

network-admin

Parameters

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

export-value: Specifies the output value.

For the description of other parameters, see Table 16.

Table 16 Priority maps

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

Usage guidelines

If you execute this command multiple times and enter the same input values for one priority map, the most recent configuration takes effect.

Examples

# Configure a mapping from DSCP 2 to local precedence 4 for flexible priority map user1.

<Sysname> system-view

[Sysname] qos map-table name user1

[Sysname-flexmaptbl-user1] dscp-lp import 2 export 4

Related commands

display qos map-table interface

qos map-table name

import (priority map view)

Use import to configure mappings for a priority map.

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

Syntax

import import-value-list export export-value

undo import { import-value-list | all }

Default

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

Views

Priority map view

Predefined user roles

network-admin

Parameters

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

export-value: Specifies the output value.

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

Examples

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

<Sysname> system-view

[Sysname] qos map-table dot1p-dp

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

Related commands

display qos map-table

display qos map-table color

qos apply map-table name

Use qos apply map-table name to apply a flexible priority map to an interface.

Use undo qos apply map-table name to remove a flexible priority map from an interface.

Syntax

qos apply map-table name map-table-name [ inbound | outbound ]

undo qos apply map-table name map-table-name [ inbound | outbound ]

Default

No flexible priority map is applied to an interface.

Views

Interface view

Predefined user roles

network-admin

Parameters

map-table-name: Specifies a flexible priority map by its name, a case-sensitive string of 1 to 31 characters. The specified flexible priority map must already exist.

inbound: Applies the flexible priority map to the inbound direction.

outbound: Applies the flexible priority map to the outbound direction.

Usage guidelines

If you do not specify a direction, this command applies the flexible priority map to the inbound direction. Only one flexible priority map can be applied to one direction of an interface.

If you both configure a priority map in priority map view and apply a flexible priority map to an interface, the flexible priority map takes effect on the interface.

· Only the following priority maps can be applied to the inbound direction of an interface:

· dot1p-dot1p

· dot1p-dp

· dot1p-dscp

· dot1p-exp

· dot1p-lp

· dscp-dot1p

· dscp-dp

· dscp-dscp

· dscp-exp

· dscp-lp

· exp-dot1p

· exp-dp

· exp-dscp

· exp-exp

· exp-lp

Only the following priority maps can be applied to the outbound direction of an interface:

· lp-dot1p

· lp-dp

· lp-dscp

· lp-exp

· lp-php

Examples

# Apply flexible priority map user1 to GigabitEthernet 3/1/1.

<Sysname> system-view

[Sysname] interface gigabitethernet 3/1/1

[Sysname-GigabitEthernet3/1/1] qos apply map-table name user1 outbound

Related commands

display qos map-table interface

qos map-table name

qos map-table

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

Syntax

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

Views

System view

Predefined user roles

network-admin

Parameters

inbound: Specifies the priority map for the inbound direction.

outbound: Specifies the priority map for the outbound direction.

For the description of other keywords, see Table 13.

Usage guidelines

CSPC (except CSPC-GE16XP4L-E, CSPC-GE24L-E, and CSPC-GP24GE8XP2L-E) and CMPE-1104 cards do not support the dot1p-dot1p, dot1p-dscp, dot1p-exp, dscp-exp, dscp-lp, exp-dscp, exp-dp, exp-exp, or exp-lp priority map.

Examples

# Enter the inbound 802.1p-drop priority map view.

<Sysname> system-view

[Sysname] qos map-table inbound dot1p-dp

[Sysname-maptbl-in-dot1p-dp]

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 } { inbound { dot1p-dot1p | dot1p-dp | dot1p-dscp | dot1p-exp | dot1p-lp | dscp-dot1p | dscp-dp | dscp-dscp | dscp-exp | dscp-lp | exp-dot1p | exp-dp | exp-dscp | exp-exp | exp-lp } | outbound { dot1p-dot1p | dot1p-dscp | dot1p-exp | dscp-dot1p | dscp-dscp | dscp-exp | exp-dot1p | exp-dscp | exp-exp } }

Views

System view

Predefined user roles

network-admin

Parameters

green: Specifies green packets.

yellow: Specifies yellow packets.

red: Specifies red packets.

inbound: Specifies the priority map for the inbound direction.

outbound: Specifies the priority map for the outbound direction.

For the description of other keywords, see Table 13.

Usage guidelines

For a type of colored priority mapping, two priority maps exist: one for the inbound direction and one for the outbound direction.

CSPC (except CSPC-GE16XP4L-E, CSPC-GE24L-E, and CSPC-GP24GE8XP2L-E) and CMPE-1104 cards do not support this command.

Examples

# Enter the view of the EXP-local priority map for incoming green packets..

<Sysname> system-view

[Sysname] qos map-table color green inbound exp-lp

[Sysname-maptbl-green-in-exp-lp]

# Enter the view of the DSCP-local priority map for incoming red packets.

<Sysname> system-view

[Sysname] qos map-table color red inbound dscp-lp

[Sysname-maptbl-red-in-dscp-lp]

Related commands

display qos map-table color

import

qos map-table name

Use qos map-table name to create a flexible priority map and enter its view, or enter the view of an existing flexible priority map.

Use undo qos map-table name to delete a flexible priority map.

Syntax

qos map-table name map-table-name

undo qos map-table name map-table-name

Default

No flexible priority maps exist.

Views

System view

Predefined user roles

network-admin

Parameters

map-table-name: Specifies a flexible priority map name, a case-sensitive string of 1 to 31 characters.

Usage guidelines

A flexible priority map applied to an interface cannot be deleted directly. To delete an applied flexible priority map, first remove the flexible priority map from the interface by using the undo qos apply map-table name command.

Examples

# Create a flexible priority map named user1 and enter its view.

<Sysname> system-view

[Sysname] qos map-table name user1

[Sysname-map-tbl-user1]

Related commands

display qos map-table name

qos apply map-table name

Priority trust mode commands

display qos trust interface

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

Syntax

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

Views

Any view

Predefined user roles

network-admin

network-operator

Parameters

interface-type interface-number: Specifies an interface by its type and number. If you do not specify an interface, this command displays the priority trust mode and port priorities of all interfaces.

Examples

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

<Sysname> display qos trust interface gigabitethernet 3/1/1

Interface: GigabitEthernet3/1/1

Port priority information

Port priority: 0

Port dot1p priority: -

Port dscp priority: -

Port exp priority: -

Port priority trust type: none

Table 17 Command output

Field	Description
Interface	Interface type and interface number.
Port dot1p priority	802.1p priority of the port.
Port dscp priority	DSCP value of the port.
Port exp priority	EXP value of the port.
Port priority trust type	Priority trust mode: auto or none. If the trust mode is none, the port priority is used for priority 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 { auto | dot1p | dscp | inner-dot1p } [ override ]

undo qos trust

Default

An interface trusts the port priority for priority mapping.

Views

Interface view

Predefined user roles

network-admin

Parameters

auto: Uses the priority in incoming packets for priority mapping.

On CSPC (except CSPC-GE16XP4L-E, CSPC-GE24L-E, and CSPC-GP24GE8XP2L-E) and CMPE-1104 cards:

· For non-IP packets, the 802.1p priority is used.

· For IP packets, the IP precedence is used.

· For MPLS packets, the EXP value is used.

On CSPC-GE16XP4L-E, CSPC-GE24L-E, CSPC-GP24GE8XP2L-E, CSPEX, and CEPC cards:

· For Layer 2 packets, the 802.1p priority is used.

· For Layer 3 packets, the IP precedence is used.

· For MPLS packets, the EXP value is used.

dot1p: Uses the 802.1p priority of received packets for mapping.

dscp: Uses the DSCP precedence of received IP packets for mapping.

inner-dot1p: Uses the inner 802.1p priority of received QinQ packets for mapping.

override: Uses the priority derived through priority mapping to overwrite the original priority carried in the packet. By default, this feature is disabled.

Usage guidelines

On SPC and MPE-1104 cardsSPC, CSPC (except CSPC-GE16XP4L-E, CSPC-GE24L-E, and CSPC-GP24GE8XP2L-E), and CMPE-1104 cardsCSPC (except CSPC-GE16XP4L-E, CSPC-GE24L-E, and CSPC-GP24GE8XP2L-E) and CMPE-1104 cards, you must specify the override keyword when configuring the qos trust auto command.

You must specify the override keyword when configuring the qos trust auto command on the following cards:

· CSPC cards.

· CMPE-1104 cards.

· CSPEX-1104-E and CSPEX-1104-E cards.

The dot1p, dscp, and inner-dot1p keywords are available only on CSPEX (except CSPEX-1204 and CSPEX-1104-E) and CEPC cards.

When an IP packet enters an MPLS network, the device populates the EXP field with the EXP value derived from a priority map even if the override keyword is not specified.

For a Layer 3 packet, the device overwrites the 802.1p priority value in the packet with the 802.1p priority value derived from a priority map even if the override keyword is not specified.

For an MPLS packet that comes from the public network, he device uses the EXP value in the packet for priority mapping instead of trusting the configured 802.1p or DSCP priority.

Examples

# Set the priority trust mode to auto on GigabitEthernet 3/1/1.

<Sysname> system-view

[Sysname] interface gigabitethernet 3/1/1

[Sysname-GigabitEthernet3/1/1] qos trust auto

Related commands

display qos trust interface

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 [ dot1p | dscp | exp ] priority-value

undo qos priority [ dot1p | dscp | exp ]

Default

The port priority is 0.

Views

Interface view

Predefined user roles

network-admin

Parameters

priority-value: Specifies the port priority value.

· If no port priority type is specified, the port priority is in the range of 0 to 7.

· If a card supports multiple port priority types, see Table 18 for the value range for each type of port priority.

Table 18 Value ranges for different types of port priority

Port priority type	Value range	Remarks
802.1p	0 to 7	The dot1p keyword is available only on CSPC-GE16XP4L-E, CSPC-GE24L-E, CSPC-GP24GE8XP2L-E, CSPEX, and CEPC cards.
DSCP	0 to 63	The dscp keyword is available only on CSPC-GE16XP4L-E, CSPC-GE24L-E, CSPC-GP24GE8XP2L-E, CSPEX, and CEPC cards.
EXP	0 to 7	The exp keyword is available only on CSPC-GE16XP4L-E, CSPC-GE24L-E, CSPC-GP24GE8XP2L-E, CSPEX, and CEPC cards.

Examples

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

<Sysname> system-view

[Sysname] interface gigabitethernet 3/1/1

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

# Set the DSCP priority of GigabitEthernet 3/1/1 to 2.

<Sysname> system-view

[Sysname] interface gigabitethernet 3/1/1

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

Related commands

display qos trust interface

Traffic policing, GTS, and rate limit commands

Traffic policing commands

display qos car control-plane whitelist

Use display qos car control-plane whitelist to display whitelist-based control plane CAR configuration and statistics.

Syntax

In standalone mode:

display qos car control-plane whitelist [ ipv6 ] slot slot-number

In IRF mode:

display qos car control-plane whitelist [ ipv6 ] chassis chassis-number slot slot-number

Views

Any view

Predefined user roles

network-admin

network-operator

Parameters

ipv6: Specifies the IPv6 dynamic whitelist. If you do not specify this keyword, the command displays IPv4 whitelist-based control plane CAR configuration and statistics.

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

Usage guidelines

After you enable whitelist-based traffic policing for the control plane, you can use this command to display whitelist-based control plane CAR configuration and statistics by queue.

This command is available only on CSPEX (except CSPEX-1204 and CSPEX-1104-E) and CEPC cards.

Examples

# (In standalone mode.) Display whitelist-based control plane CAR configuration and statistics for slot 2.

<Sysname> display qos car control-plane whitelist slot 2

Slot 2

Whitelist-based traffic policing: Enabled

Queue name: default

CIR 30720 (kbps), CBS 8192 (Bytes)

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

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

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

Queue name: ftp

CIR 1024 (kbps), CBS 8192 (Bytes)

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

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

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

Queue name: telnet

CIR 1024 (kbps), CBS 8192 (Bytes)

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

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

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

Queue name: ssh

CIR 1024 (kbps), CBS 8192 (Bytes)

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

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

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

Queue name: http

CIR 1024 (kbps), CBS 8192 (Bytes)

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

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

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

Queue name: https

CIR 1024 (kbps), CBS 8192 (Bytes)

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

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

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

Queue name: ldp

CIR 15360 (kbps), CBS 8192 (Bytes)

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

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

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

Queue name: bgp

CIR 30720 (kbps), CBS 8192 (Bytes)

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

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

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

Queue name: snmp

CIR 1024 (kbps), CBS 8192 (Bytes)

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

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

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

Queue name: bfd

CIR 30720 (kbps), CBS 8192 (Bytes)

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

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

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

Table 19 Command output

Field	Description
Failed rule ID	IDs of rules that failed to take effect.

Related commands

display acl whitelist

qos car whitelist enable

qos car (control plane view)

Use qos car to configure a CAR policy for a control plane.

Use undo qos car to delete a CAR policy from a control plane.

Syntax

qos car { any | user } cir committed-information-rate [ cbs committed-burst-size [ ebs excess-burst-size ] ]

qos car { any | user } cir committed-information-rate [ cbs committed-burst-size ] pir peak-information-rate [ ebs excess-burst-size ]

undo qos car { any | user }

Default

No CAR policy is configured.

Views

Control plane view

Predefined user roles

network-admin

Parameters

any: Performs CAR for all control plane traffic.

user: Performs CAR for the control plane traffic from all online users.

cir committed-information-rate: Specifies the CIR in kbps. The committed-information-rate argument has the following value ranges:

· 8 to 160000000 for traffic policing for all control plane traffic. Only the range 8 to 1000000 is supported in the current software version.

· 8 to 160000000 for online user-based traffic policing.

· 8 to 160000000 for whitelist-based traffic policing. Only the range 8 to 100000 is supported in the current software version.

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

ebs excess-burst-size: Specifies the EBS in bytes. If the PIR is not specified, the value range for excess-burst-size is 0 to 256000000, and the default is 0. If the PIR is specified, the value range for excess-burst-size is 512 to 256000000.

pir peak-information-rate: Specifies the PIR in kbps. The peak-information-rate argument has the following value ranges:

· 8 to 160000000 for traffic policing for all control plane traffic. Only the range 8 to 1000000 is supported in the current software version.

· 8 to 160000000 for online user-based traffic policing.

Usage guidelines

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

For online user-based traffic policing, the CIR is the rate of control plane traffic from each online user.

This command is available only on CSPEX (except CSPEX-1204 and CSPEX-1104-E) and CEPC cards.

Examples

# Perform CAR for all control plane traffic for slot 3. The CAR parameters are as follows:

· The CIR is 2000 kbps.

· The CBS is 150000 bytes.

· The EBS is 0 bytes.

<Sysname> system-view

[Sysname] control-plane slot 3

[Sysname-cp-slot3] qos car any cir 2000 cbs 150000 ebs 0

# Perform CAR for the control plane traffic from all online users for slot 3. The CAR parameters are as follows:

· The CIR is 200 kbps.

· The CBS is 15000 bytes.

· The EBS is 0 bytes.

<Sysname> system-view

[Sysname] control-plane slot 3

[Sysname-cp-slot3] qos car user cir 200 cbs 15000 ebs 0

qos car any (user profile view)

Use qos car any to configure a CAR policy for all packets of a user profile.

Use undo qos car to delete a CAR policy from a user profile.

Syntax

qos car { inbound | outbound } any cir committed-information-rate [ cbs committed-burst-size [ ebs excess-burst-size ] ]

qos car { inbound | outbound } any cir committed-information-rate [ cbs committed-burst-size ] pir peak-information-rate [ ebs excess-burst-size ]

undo qos car { inbound | outbound }

Default

No CAR policy is configured for a user profile.

Views

User profile view

Predefined user roles

network-admin

Parameters

inbound: Performs CAR in the inbound direction.

outbound: Performs CAR in the outbound direction.

cir committed-information-rate: Specifies the CIR in the range of 8 to 160000000 kbps.

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

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

pir peak-information-rate: Specifies the PIR in the range of 8 to 160000000 kbps.

Usage guidelines

The conforming traffic is permitted to pass through, and the excess traffic is dropped.

If you execute the qos car command multiple times for the same user profile or session group profile, the most recent configuration takes effect.

This command is available only on CSPEX (except CSPEX-1204) and CEPC cards.

Examples

# Perform CAR for packets received by user profile user. The CAR parameters are as follows:

· The CIR is 200 kbps.

· The CBS is 51200 bytes.

<Sysname> system-view

[Sysname] user-profile user

[Sysname-user-profile-user] qos car outbound any cir 200 cbs 51200

qos car whitelist enable

Use qos car whitelist enable to enable whitelist-based traffic policing for the control plane.

Use undo qos car whitelist enable to disable whitelist-based traffic policing for the control plane.

Syntax

qos car whitelist [ ipv6 ] enable

undo qos car whitelist [ ipv6 ] enable

Default

Whitelist-based traffic policing is enabled, and the device uses the default rate limit values to police matching traffic.

Views

Control plane view

Predefined user roles

network-admin

Parameters

ipv6: Enables whitelist-based traffic policing for the IPv6 dynamic whitelist. If you do not specify this keyword, the command enables whitelist-based traffic policing for the IPv4 dynamic whitelist.

Usage guidelines

After you execute this command, the system dynamically generates a whitelist according to existing TCP connections or other protocol sessions. The whitelist contains ACL rules used to match traffic. You can use the display acl whitelist command to display the ACL rules in the whitelist.

Examples

# Enable whitelist-based traffic policing for the control plane of slot 3.

<Sysname> system-view

[Sysname] control-plane slot 3

[Sysname-cp-slot3] qos car whitelist enable

reset qos car control-plane whitelist

Use reset qos car control-plane whitelist to clear whitelist-based control plane CAR statistics.

Syntax

In standalone mode:

reset qos car control-plane whitelist [ ipv6 ] slot slot-number

In IRF mode:

reset qos car control-plane whitelist [ ipv6 ] chassis chassis-number slot slot-number

Views

User view

Predefined user roles

network-admin

Parameters

ipv6: Specifies the IPv6 dynamic whitelist. If you do not specify this keyword, the command clears IPv4 whitelist-based control plane CAR statistics.

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

Usage guidelines

This command is available only on CSPEX (except CSPEX-1204 and CSPEX-1104-E) and CEPC cards.

Examples

# (In standalone mode.) Clear whitelist-based control plane CAR statistics for slot 2.

<Sysname> reset qos car control-plane whitelist slot 2

GTS commands

display qos gts interface

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

Syntax

In standalone mode:

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

In IRF mode:

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

Views

Any view

Predefined user roles

network-admin

network-operator

Parameters

interface-type interface-number: Specifies an interface by its type and number. If you do not specify an interface, this command displays the GTS configuration for all interfaces.

slot slot-number: Specifies a card by its slot number. If you do not specify a card, this command displays the GTS configuration for the active MPU. This option is available only for aggregate interfaces. (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 GTS configuration for the global active MPU. This option is available only for aggregate interfaces. (In IRF mode.)

Examples

# Display the GTS configuration for all interfaces.

<Sysname> display qos gts interface

Interface: GigabitEthernet3/1/1

Rule: If-match queue 1

CIR 10000 (kbps), CBS 625000 (Bytes)

Table 20 Command output

Field	Description
Interface	Interface name, including the interface type and interface number.
Rule	Match criteria.

display qos queue-statistics user-id

Use display queue-statistics user-id to display queue-based statistics for a home user.

Syntax

In standalone mode:

display qos queue-statistics user-id user-id [ slot slot-number ] outbound

In IRF mode:

display qos queue-statistics user-id user-id [ chassis chassis-number slot slot-number ] outbound

Views

Any view

Predefined user roles

network-admin

network-operator

Parameters

user-id user-id: Specifies a home user by a system-assigned, hexadecimal ID in the range of 0 to fffffffe.

slot slot-number: Specifies a card by its slot number. If you do not specify a card, this command displays information 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 information for all cards. (In IRF mode.)

outbound: Specifies queue-based statistics for the outbound direction.

Usage guidelines

A user that comes online on a physical interface is called a local user. A user that comes online on a logical interface is called a global user. If you do not specify a slot for a global user, the command displays queue-based statistics for all slots associated with the logical interface.

Examples

# Display queue-based statistics for the home user with a user ID of 48000009.

<Sysname> display qos queue-statistics user-id 48000009 outbound

slot 2

User ID: 0x48000009 (global)

Direction: Outbound

Forwarded: 6756832 packets, 891901824 bytes

Dropped: 49648521 packets, 6553604772 bytes

Queue 0

Forwarded: 1333037 packets, 175960884 bytes

Dropped: 5721125 packets, 755188500 bytes

Green forwarded: 1333037 packets, 175960884 bytes

Green dropped: 0 packets, 0 bytes

Yellow forwarded: 0 packets, 0 bytes

Yellow dropped: 0 packets, 0 bytes

Red forwarded: 0 packets, 0 bytes

Red dropped: 5721125 packets, 755188500 bytes

Current queue length: 999 packets

Queue 1

Forwarded: 162933 packets, 21507156 bytes

Dropped: 6888203 packets, 909242796 bytes

Green forwarded: 162933 packets, 21507156 bytes

Green dropped: 0 packets, 0 bytes

Yellow forwarded: 0 packets, 0 bytes

Yellow dropped: 0 packets, 0 bytes

Red forwarded: 0 packets, 0 bytes

Red dropped: 6888203 packets, 909242796 bytes

Current queue length: 4092 packets

Queue 2

Forwarded: 162945 packets, 21508740 bytes

Dropped: 6888260 packets, 909250320 bytes

Green forwarded: 162945 packets, 21508740 bytes

Green dropped: 0 packets, 0 bytes

Yellow forwarded: 0 packets, 0 bytes

Yellow dropped: 0 packets, 0 bytes

Red forwarded: 0 packets, 0 bytes

Red dropped: 6888260 packets, 909250320 bytes

Current queue length: 4092 packets

Queue 3

Forwarded: 162956 packets, 21510192 bytes

Dropped: 6888315 packets, 909257580 bytes

Green forwarded: 162956 packets, 21510192 bytes

Green dropped: 0 packets, 0 bytes

Yellow forwarded: 0 packets, 0 bytes

Yellow dropped: 0 packets, 0 bytes

Red forwarded: 0 packets, 0 bytes

Red dropped: 6888315 packets, 909257580 bytes

Current queue length: 4092 packets

Queue 4

Forwarded: 163895 packets, 21634140 bytes

Dropped: 6887445 packets, 909142740 bytes

Green forwarded: 163895 packets, 21634140 bytes

Green dropped: 0 packets, 0 bytes

Yellow forwarded: 0 packets, 0 bytes

Yellow dropped: 0 packets, 0 bytes

Red forwarded: 0 packets, 0 bytes

Red dropped: 6887445 packets, 909142740 bytes

Current queue length: 4092 packets

Queue 5

Forwarded: 475882 packets, 62816424 bytes

Dropped: 6575525 packets, 867969300 bytes

Green forwarded: 475882 packets, 62816424 bytes

Green dropped: 0 packets, 0 bytes

Yellow forwarded: 0 packets, 0 bytes

Yellow dropped: 0 packets, 0 bytes

Red forwarded: 0 packets, 0 bytes

Red dropped: 6575525 packets, 867969300 bytes

Current queue length: 4092 packets

Queue 6

Forwarded: 1986335 packets, 262196220 bytes

Dropped: 5065139 packets, 668598348 bytes

Green forwarded: 1986335 packets, 262196220 bytes

Green dropped: 0 packets, 0 bytes

Yellow forwarded: 0 packets, 0 bytes

Yellow dropped: 0 packets, 0 bytes

Red forwarded: 0 packets, 0 bytes

Red dropped: 5065139 packets, 668598348 bytes

Current queue length: 4092 packets

Queue 7

Forwarded: 2308849 packets, 304768068 bytes

Dropped: 4734509 packets, 624955188 bytes

Green forwarded: 2308849 packets, 304768068 bytes

Green dropped: 0 packets, 0 bytes

Yellow forwarded: 0 packets, 0 bytes

Yellow dropped: 0 packets, 0 bytes

Red forwarded: 0 packets, 0 bytes

Red dropped: 4734509 packets, 624955188 bytes

Current queue length: 12276 packets

slot 4

User ID: 0x48000009 (global)

Direction: Outbound

Forwarded: 6756832 packets, 891901824 bytes

Dropped: 49648521 packets, 6553604772 bytes

Queue 0

Forwarded: 1333037 packets, 175960884 bytes

Dropped: 5721125 packets, 755188500 bytes

Green forwarded: 1333037 packets, 175960884 bytes

Green dropped: 0 packets, 0 bytes

Yellow forwarded: 0 packets, 0 bytes

Yellow dropped: 0 packets, 0 bytes

Red forwarded: 0 packets, 0 bytes

Red dropped: 5721125 packets, 755188500 bytes

Current queue length: 999 packets

Queue 1

Forwarded: 162933 packets, 21507156 bytes

Dropped: 6888203 packets, 909242796 bytes

Green forwarded: 162933 packets, 21507156 bytes

Green dropped: 0 packets, 0 bytes

Yellow forwarded: 0 packets, 0 bytes

Yellow dropped: 0 packets, 0 bytes

Red forwarded: 0 packets, 0 bytes

Red dropped: 6888203 packets, 909242796 bytes

Current queue length: 4092 packets

Queue 2

Forwarded: 162945 packets, 21508740 bytes

Dropped: 6888260 packets, 909250320 bytes

Green forwarded: 162945 packets, 21508740 bytes

Green dropped: 0 packets, 0 bytes

Yellow forwarded: 0 packets, 0 bytes

Yellow dropped: 0 packets, 0 bytes

Red forwarded: 0 packets, 0 bytes

Red dropped: 6888260 packets, 909250320 bytes

Current queue length: 4092 packets

Queue 3

Forwarded: 162956 packets, 21510192 bytes

Dropped: 6888315 packets, 909257580 bytes

Green forwarded: 162956 packets, 21510192 bytes

Green dropped: 0 packets, 0 bytes

Yellow forwarded: 0 packets, 0 bytes

Yellow dropped: 0 packets, 0 bytes

Red forwarded: 0 packets, 0 bytes

Red dropped: 6888315 packets, 909257580 bytes

Current queue length: 4092 packets

Queue 4

Forwarded: 163895 packets, 21634140 bytes

Dropped: 6887445 packets, 909142740 bytes

Green forwarded: 163895 packets, 21634140 bytes

Green dropped: 0 packets, 0 bytes

Yellow forwarded: 0 packets, 0 bytes

Yellow dropped: 0 packets, 0 bytes

Red forwarded: 0 packets, 0 bytes

Red dropped: 6887445 packets, 909142740 bytes

Current queue length: 4092 packets

Queue 5

Forwarded: 475882 packets, 62816424 bytes

Dropped: 6575525 packets, 867969300 bytes

Green forwarded: 475882 packets, 62816424 bytes

Green dropped: 0 packets, 0 bytes

Yellow forwarded: 0 packets, 0 bytes

Yellow dropped: 0 packets, 0 bytes

Red forwarded: 0 packets, 0 bytes

Red dropped: 6575525 packets, 867969300 bytes

Current queue length: 4092 packets

Queue 6

Forwarded: 1986335 packets, 262196220 bytes

Dropped: 5065139 packets, 668598348 bytes

Green forwarded: 1986335 packets, 262196220 bytes

Green dropped: 0 packets, 0 bytes

Yellow forwarded: 0 packets, 0 bytes

Yellow dropped: 0 packets, 0 bytes

Red forwarded: 0 packets, 0 bytes

Red dropped: 5065139 packets, 668598348 bytes

Current queue length: 4092 packets

Queue 7

Forwarded: 2308849 packets, 304768068 bytes

Dropped: 4734509 packets, 624955188 bytes

Green forwarded: 2308849 packets, 304768068 bytes

Green dropped: 0 packets, 0 bytes

Yellow forwarded: 0 packets, 0 bytes

Yellow dropped: 0 packets, 0 bytes

Red forwarded: 0 packets, 0 bytes

Red dropped: 4734509 packets, 624955188 bytes

Current queue length: 12276 packets

Table 21 Command output

Field	Description
Forwarded	Total number of packets forwarded and total number of bytes forwarded.
Dropped	Total number of packets dropped and total number of bytes dropped.
Green forwarded	Number of green packets forwarded and number of bytes forwarded for green packets.
Green dropped	Number of green packets dropped and number of bytes dropped for green packets.
Yellow forwarded	Number of yellow packets forwarded and number of bytes forwarded for yellow packets.
Yellow dropped	Number of yellow packets dropped and number of bytes dropped for yellow packets.
Red forwarded	Number of red packets forwarded and number of bytes forwarded for red packets.
Red dropped	Number of red packets dropped and number of bytes dropped for red packets.
Current queue length	Number of packets in the queue.

qos gts (interface view)

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

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 committed-information-rate argument has the following value ranges:

· 300 to 1000000 for GE interfaces.

· 300 to 10000000 for 10-GE interfaces.

· 2500 to 100000000 for 100-GE interfaces. Only the range 2500 to 10000000 is supported in the current software version.

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

Usage guidelines

On CSPC-GE16XP4L-E, CSPC-GE24L-E, CSPC-GP24GE8XP2L-E, CSPEX-1104-E, and CSPEX-1204 cards, you cannot configure both queue-based GTS and a queue scheduling profile with WRR queuing for the same interface.

Examples

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

· The CIR is 6400 kbps.

· The CBS is 51200 bytes.

<Sysname> system-view

[Sysname] interface gigabitethernet 3/1/1

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

qos gts (session group profile view)

Use qos gts to set GTS parameters for a session group profile.

Use undo qos gts to delete GTS settings for a session group profile.

Syntax

qos gts { any | queue queue-id } cir committed-information-rate [ cbs committed-burst-size [ ebs excess-burst-size ] ] [ queue-length queue-length ]

qos gts { any | queue queue-id } cir committed-information-rate [ cbs committed-burst-size ] pir peak-information-rate [ ebs excess-burst-size ] [ queue-length queue-length ]

undo qos gts { any | queue queue-id }

Default

No GTS parameters are set.

Views

Session group profile view

Predefined user roles

network-admin

Parameters

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

cir committed-information-rate: Specifies the CIR in the range of 300 to 100000000 kbps.

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

ebs excess-burst-size: Specifies the EBS in the range of 0 to 256000000 bytes.

pir peak-information-rate: Specifies the PIR in the range of 300 to 100000000 kbps. The PIR cannot be smaller than the CIR.

queue-length queue-length: Specifies the maximum number of packets that can be queued, in the range of 1 to 12582912. The default is 4096. The queue length cannot be greater than the integer that is closest to and greater than the CIR multiplied by 0.078125.

Usage guidelines

This command takes effect only on outgoing traffic.

This command is available only on CSPEX (except CSPEX-1204 and CSPEX-1104-E) and CEPC cards.

Examples

# Shape the packets received by session group profile aaa in queue 1. The GTS parameters are as follows:

· The CIR is 400 kbps.

· The CBS is 51200 bytes.

<Sysname> system-view

[Sysname] user-profile aaa type session-group

[Sysname-session-group-profile-aaa] qos gts queue 1 cir 400 cbs 51200

qos gts (user group profile view)

Use qos gts to set GTS parameters for a user group profile.

Use undo qos gts to delete GTS settings for a user group profile.

Syntax

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

qos gts any cir committed-information-rate [ cbs committed-burst-size ] pir peak-information-rate [ ebs excess-burst-size ] [ queue-length queue-length ]

undo qos gts any

Default

No GTS parameters are set.

Views

User group profile view

Predefined user roles

network-admin

Parameters

any: Shapes all packets.

cir committed-information-rate: Specifies the CIR in the range of 300 to 100000000 kbps.

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

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

pir peak-information-rate: Specifies the PIR in the range of 300 to 100000000 kbps. The PIR cannot be smaller than the CIR.

Usage guidelines

This command takes effect only on outgoing traffic.

This command is available only on CSPEX (except CSPEX-1204 and CSPEX-1104-E) and CEPC cards.

Examples

# Shape the packets received by user group profile aaa. The GTS parameters are as follows:

· The CIR is 400 kbps.

· The CBS is 51200 bytes.

<Sysname> system-view

[Sysname] user-group-profile aaa

[Sysname-user-group-profile-aaa] qos gts any cir 400 cbs 51200

Rate limit commands

display qos lr

Use display qos lr to display the rate limit information for interfaces.

Syntax

In standalone mode:

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

In IRF mode:

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

Views

Any view

Predefined user roles

network-admin

network-operator

Parameters

interface-type interface-number: Specifies an interface by its type and number. If you do not specify an interface, this command displays the rate limit information for all interfaces.

slot slot-number: Specifies a card by its slot number. Only virtual interfaces such as aggregate interfaces support this option. (In standalone mode.)

Examples

# Display the rate limit information for all interfaces.

<Sysname> display qos lr interface

Interface: GigabitEthernet3/1/1

Direction: Outbound

CIR 10000 (kbps), CBS 625000 (Bytes)

Table 22 Command output

Field	Description
Interface	Interface name, including the interface type and interface number.
Direction	Direction to which the rate limit configuration is applied: inbound or outbound.

qos lr

Use qos lr to configure outbound rate limiting on an interface.

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

Syntax

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

undo qos lr outbound

Default

No rate limit is configured.

Views

Interface view

Predefined user roles

network-admin

Parameters

cir committed-information-rate: Specifies the CIR in kbps. The committed-information-rate argument has the following value ranges:

· 300 to 1000000 for GE interfaces.

· 300 to 10000000 for 10-GE interfaces.

· 2500 to 100000000 for 100-GE interfaces.

· 160 to 100000000 for Layer 3 aggregate interfaces.

cbs committed-burst-size: Specifies the CBS in bytes. The committed-burst-size argument has the following value ranges:

· 1024 to 133169152 for Layer 3 aggregate interfaces.

· 4096 to 133169152 for other interfaces.

The default is the product of 62.5 and the CIR value.

Examples

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

<Sysname> system-view

[Sysname] interface gigabitethernet 3/1/1

[Sysname-GigabitEthernet3/1/1] qos lr outbound cir 400 cbs 51200

Hardware congestion management commands

Common commands

display qos queue interface

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

Syntax

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

Views

Any view

Predefined user roles

network-admin

network-operator

Parameters

interface-type interface-number: Specifies an interface by its type and number. If you do not specify an interface, this command displays the queuing information for all interfaces.

Examples

# Display the queuing information for all interfaces.

<Sysname> display qos queue interface

Interface: GigabitEthernet3/1/1

Output queue: Strict Priority queuing

Interface: GigabitEthernet3/1/2

Output queue: Strict Priority queuing

Interface: GigabitEthernet3/1/3

Output queue: Strict Priority queuing

Interface: GigabitEthernet3/1/4

Output queue: Strict Priority queuing

Interface: GigabitEthernet3/1/5

Output queue: Strict Priority queuing

Interface: GigabitEthernet3/1/6

Output queue: Strict Priority queuing

Table 23 Command output

Field	Description
Interface	Interface name, including the interface type and interface number.

display qos-queue resource

Use display qos-queue resource to display the QoS queue resource usage for a card.

Syntax

In standalone mode:

display qos-queue resource slot slot-number { inbound | outbound }

In IRF mode:

display qos-queue resource chassis chassis-number slot slot-number { inbound | outbound }

Views

Any view

Predefined user roles

network-admin

network-operator

Parameters

slot slot-number: Specifies a card by its slot number. (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. (In IRF mode.)

inbound: Specifies the inbound direction.

outbound: Specifies the outbound direction.

Usage guidelines

If a card does not support collecting QoS queue resource usage statistics, this command displays no queue resource usage statistics for the card.

Examples

# Display the QoS queue resource usage for the card in slot 3 in the outbound direction.

[Sysname] display qos-queue resource slot 3 outbound

Chip 0

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

Res-Pool Type Total Used Free

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

TM0 UserGroup 22126 0 22126 (share with each other)

Hqos 22126 0 22126 (share with each other)

PortQos 22126 0 22126 (share with each other)

AdvancedUser22126 0 22126 (share with each other)

BasicUser 33174 0 33174 (share with each other)

Table 24 Command output

Field	Description
Res-Pool	TM chip for the resources.
Type	Resource type.
Total	Total number of resources.
Used	Number of resources that have been used.
Free	Number of resources that you can use.

SP commands

display qos queue sp interface

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

Syntax

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

Views

Any view

Predefined user roles

network-admin

network-operator

Parameters

interface-type interface-number: Specifies an interface by its type and number. If you do not specify an interface, this command displays the SP queuing configuration for all interfaces.

Examples

# Display the SP queuing configuration of GigabitEthernet 3/1/1.

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

Interface: GigabitEthernet3/1/1

Output queue: Strict Priority queuing

Table 25 Command output

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

qos sp

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

Usage guidelines

This command is available only on the following cards:

· CSPC cards (except CSPC-GE16XP4L-E, CSPC-GE24L-E, and CSPC-GP24GE8XP2L-E).

· CMPE cards.

Examples

# Enable SP queuing on GigabitEthernet 3/1/1.

<Sysname> system-view

[Sysname] interface gigabitethernet 3/1/1

[Sysname-GigabitEthernet3/1/1] qos sp

Related commands

display qos queue sp interface

WRR commands

CSPC-GE16XP4L-E, CSPC-GE24L-E, CSPC-GP24GE8XP2L-E, CSPEX, and CEPC cards do not support WRR.

display qos queue wrr interface

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

Syntax

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

Views

Any view

Predefined user roles

network-admin

network-operator

Parameters

interface-type interface-number: Specifies an interface by its type and number. If you do not specify an interface, this command displays the WRR queuing configuration for all interfaces.

Examples

# Display the WRR queuing configuration of GigabitEthernet 3/1/1.

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

Interface: GigabitEthernet3/1/1

Output queue: Weighted Round Robin queuing

Queue ID Queue name Group Weight

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

0 be 1 1

1 af1 1 2

2 af2 1 3

3 af3 1 4

4 af4 1 5

5 ef 1 6

6 cs6 1 7

7 cs7 1 8

Table 26 Command output

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

qos wrr

Use qos wrr to enable WRR queuing on an interface.

Use undo qos wrr to restore the default.

Syntax

qos wrr weight

undo qos wrr weight

Default

An interface uses SP queuing.

Views

Interface view

Predefined user roles

network-admin

Parameters

weight: Allocates bandwidth to queues based on packet count.

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 weight-based WRR queuing on GigabitEthernet 3/1/1.

<Sysname> system-view

[Sysname] interface gigabitethernet 3/1/1

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

Related commands

display qos queue wrr interface

qos wrr weight

Use qos wrr weight to configure the WRR queuing parameters for a queue on an interface.

Use undo qos wrr to restore the default for a queue.

Syntax

qos wrr queue-id group 1 weight schedule-value

undo qos wrr queue-id

Default

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

Views

Interface view

Predefined user roles

network-admin

Parameters

queue-id: Specifies a queue by its ID in the range of 0 to 7 or by a keyword listed in Table 27.

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

weight: Allocates bandwidth to queues based on packet count.

schedule-value: Specifies the number of packets that can be sent each time, in the range of 1 to 310. Only the range 1 to 63 is supported in the current software version.

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.

This command is available only on CSPC (except CSPC-GE16XP4L-E, CSPC-GE24L-E, and CSPC-GP24GE8XP2L-E) and CMPE-1104 cards

Examples

# Enable packet-count WRR queuing on GigabitEthernet 3/1/1, and assign queue 0, with the scheduling weight 10, to WRR group 1.

<Sysname> system-view

[Sysname] interface gigabitethernet 3/1/1

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

[Sysname-GigabitEthernet3/1/1] qos wrr 0 group 1 weight 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 the WRR group.

Views

Interface view

Predefined user roles

network-admin

Parameters

queue-id: Specifies a queue by its ID in the range of 0 to 7 or by a keyword listed in Table 27.

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

<Sysname> system-view

[Sysname] interface gigabitethernet 3/1/1

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

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

Related commands

display qos queue wrr interface

qos wrr

WFQ commands

CSPC-GE16XP4L-E, CSPC-GE24L-E, CSPC-GP24GE8XP2L-E, CSPEX, and CEPC cards do not support WFQ.

Layer 3 Ethernet subinterfaces on CSPC (except CSPC-GE16XP4L-E, CSPC-GE24L-E, and CSPC-GP24GE8XP2L-E) and CMPE-1104 cards do not support WFQ.

display qos queue wfq interface

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

Syntax

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

Views

Any view

Predefined user roles

network-admin

network-operator

Parameters

interface-type interface-number: Specifies an interface by its type and number. If you do not specify an interface, this command displays the WFQ configuration for all interfaces.

Examples

# Display the WFQ configuration of GigabitEthernet 3/1/1.

<Sysname> display qos wfq interface gigabitethernet 3/1/1

Interface: GigabitEthernet3/1/1

Output queue: Hardware Weighted Fair Queuing

Queue ID Queue name Weight Min bandwidth

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

0 be 1 0

1 af1 1 0

2 af2 1 0

3 af3 1 0

4 af4 1 0

5 ef 1 0

6 cs6 1 0

7 cs7 1 0

Table 28 Command output

Field	Description
Interface	Interface type and interface number.
Output queue	Type of the current output queue.
Group	Number of the group that holds the queue.
Weight	Packet-count scheduling weight of the queue.
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

No minimum guaranteed bandwidth is provided.

Views

Interface view

Predefined user roles

network-admin

Parameters

queue-id: Specifies a queue by its ID in the range of 0 to 7 or by a keyword listed in Table 27.

min bandwidth-value: Sets the minimum guaranteed bandwidth in kbps. The value range for the bandwidth-value argument is 300 to 1000000 for GE interfaces, 300 to 10000000 for 10-GE interfaces, 300 to 40000000 for 10-GE interfaces, and 300 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.

Examples

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

<Sysname> system-view

[Sysname] interface gigabitethernet 3/1/1

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

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

Related commands

qos wfq

Use qos wfq to enable WFQ on an interface.

Use undo qos wfq to restore the default.

Syntax

qos wfq weight

undo qos wfq weight

Default

An interface uses SP queuing.

Views

Interface view

Predefined user roles

network-admin

Parameters

weight: Allocates bandwidth to queues based on packet count.

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 weight-based WFQ on GigabitEthernet 3/1/1.

<Sysname> system-view

[Sysname] interface gigabitethernet 3/1/1

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

Related commands

display qos queue wfq interface

qos wfq weight

Use qos wfq weight to configure the scheduling weight of a queue.

Use undo qos wfq to restore the default for a queue.

Syntax

qos wfq queue-id weight schedule-value

undo qos wfq queue-id

Default

All queues on a WFQ-enabled interface have a weight of 1.

Views

Interface view

Predefined user roles

network-admin

Parameters

queue-id: Specifies a queue by its ID in the range of 0 to 7 or by a keyword listed in Table 27.

schedule-value: Specifies the number of packets that can be sent each time, in the range of 1 to 310. Only the range 1 to 63 is supported in the current software version.

Usage guidelines

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

Examples

# Enable packet-count WFQ on GigabitEthernet 3/1/1, and set the scheduling weight to 10 for queue 0.

<Sysname> system-view

[Sysname] interface gigabitethernet 3/1/1

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

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

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

Use undo bandwidth queue to restore the default.

Syntax

bandwidth queue queue-id min bandwidth-value

undo bandwidth queue queue-id

Default

No minimum guaranteed bandwidth is set for a queue.

Views

Queue scheduling profile view

Predefined user roles

network-admin

Parameters

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

min bandwidth-value: Specifies the minimum guaranteed bandwidth in the range of 300 to 100000000 kbps.

Usage guidelines

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

Examples

# Set the minimum guaranteed bandwidth to 128 kbps for queue 1.

<Sysname> system-view

[Sysname] qos qmprofile myprofile

[Sysname-qmprofile-myprofile] bandwidth queue 1 min 128

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

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 Max

unit value bandwidth bandwidth

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

be SP N/A N/A N/A 0 N/A

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

af2 SP N/A N/A N/A 1000 N/A

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

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

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

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

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

Table 29 Command output

Field	Description
Queue management profile	Queue scheduling profile name.
Basic	This word indicates a basic queue scheduling profile. If this word is absent, the queue scheduling profile is advanced.
Type	Queue scheduling type: · SP. · WRR.
Group	Priority group to which the queue belongs. N/A indicates this field is ignored.
Schedule unit	Scheduling unit. N/A indicates that this field is ignored.
Schedule value	This field indicates the number of packets that can be scheduled each time. N/A indicates that this field is ignored.
Min bandwidth	Minimum guaranteed bandwidth for the queue.
Max bandwidth	Maximum allowed bandwidth for the queue.

display qos qmprofile interface

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

Syntax

In standalone mode:

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

In IRF mode:

display qos qmprofile interface [ interface-type interface-number [ chassis chassis-number slot slot-number ] ] [ inbound ]

Views

Any view

Predefined user roles

network-admin

network-operator

Parameters

interface-type interface-number: Specifies an interface by its type and number. If you do not specify an interface, this command displays the queue scheduling profiles applied to all interfaces.

slot slot-number: Specifies a card by its slot number. If you do not specify a card, this command displays the queue scheduling profile information for the active MPU. This option is available only for aggregate interfaces. (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 information for the global active MPU. This option is available only for aggregate interfaces. (In IRF mode.)

inbound: Specifies the queue scheduling profile applied to the inbound direction. If you do not specify this keyword, the command displays the queue scheduling profile applied to the outbound direction. This keyword is not supported in the current software version.

Usage guidelines

This command is available only on CSPEX and CEPC cards.

Examples

# Display the queue scheduling profile applied to GigabitEthernet 3/1/1.

<Sysname> display qos qmprofile interface gigabitethernet 3/1/1

Interface: GigabitEthernet3/1/1

Direction: Outbound

Queue management profile: myprofile

Table 30 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 (interface view)

Use qos apply qmprofile to apply a queue scheduling profile to an interface.

Use undo qos apply qmprofile to restore the default.

Syntax

qos apply qmprofile profile-name [ inbound ]

undo qos apply qmprofile [ inbound ]

Default

An interface uses SP queuing.

Views

Interface view

Predefined user roles

network-admin

Parameters

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

inbound: Applies the queue scheduling profile to the inbound direction. If you do not specify this keyword, the command applies the queue scheduling profile to the outbound direction. This keyword is not supported in the current software version.

Usage guidelines

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

On a CSPEX-1204 card, you cannot configure both queue-based GTS and a queue scheduling profile with WRR queuing for the same interface.

Examples

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

<Sysname> system-view

[Sysname] interface gigabitethernet 3/1/1

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

Related commands

display qos qmprofile interface

qos apply qmprofile (session group profile view, user profile view)

Use qos apply qmprofile to apply a queue scheduling profile to a session group profile or user profile.

Use undo qos apply qmprofile to restore the default.

Syntax

qos apply qmprofile profile-name [ inbound ]

undo qos apply qmprofile [ inbound ]

Default

No queue scheduling profile is applied to a session group profile or user profile.

Views

Session group profile view

User profile view

Predefined user roles

network-admin

Parameters

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

inbound: Applies the queue scheduling profile to the packets sent by the session group profile or user profile. If you do not specify this keyword, the command applies the queue scheduling profile to the packets received by the session group profile or user profile. This keyword is not supported in the current software version.

Usage guidelines

You can apply only one queue scheduling profile to one direction of a session group profile or user profile.

To delete a queue scheduling profile applied to a session group profile or user profile, first remove the queue scheduling profile from the session group profile or user profile.

The queue scheduling profile to be applied to a session group profile or user profile must already exist.

This command is available only on CSPEX (except CSPEX-1204) and CEPC cards.

Examples

# Apply queue scheduling profile myprofile to the packets received by session group profile a123.

<Sysname> system-view

[Sysname] user-profile a123 type session-group

[Sysname-session-group-profile-a123] qos apply qmprofile myprofile

# Apply queue scheduling profile myprofile to the packets received by user profile a123.

<Sysname> system-view

[Sysname] user-profile a123

[Sysname-user-profile-a123] qos apply qmprofile myprofile

qos apply qmprofile fabric

Use qos apply qmprofile fabric to apply a queue scheduling profile to the switching fabric module.

Use undo qos apply qmprofile fabric to restore the default.

Syntax

qos apply qmprofile profile-name fabric

undo qos apply qmprofile profile-name fabric

Default

No queue scheduling profile is applied to the switching fabric module.

Views

System view

Predefined user roles

network-admin

Parameters

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

Examples

# Apply queue scheduling profile myprofile to the switching fabric module.

<Sysname> system-view

[Sysname] qos apply qmprofile myprofile fabric

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 [ basic ]

undo qos qmprofile profile-name

Default

No user-created queue scheduling profiles exist.

Views

System view

Predefined user roles

network-admin

Parameters

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

basic: Specifies the queue scheduling profile as basic. If you do not specify this keyword, the command creates an advanced queue scheduling profile. This keyword is not supported in the current software version.

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 | wrr group group-id weight schedule-value } [ max-bandwidth bandwidth-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

Parameters

queue-id: Specifies a queue by its ID in the range of 0 to 7 or by a keyword listed in Table 27.

sp: Enables SP for the queue.

wrr: Enables WRR for the queue.

group group-id: Specifies a WRR group by its ID in the range of 1 to 4.

weight: Allocates bandwidth to queues based on packet count.

schedule-value: Specifies the number of packets that can be sent each time, in the range of 1 to 310. The CSPEX-1204 card supports only the range 1 to 63.

max-bandwidth bandwidth-value: Specifies the maximum allowed bandwidth in the range of 300 to 100000000 kbps. This option is supported only on CSPEX (except CSPEX-1204 and CSPEX-1104-E) and CEPC cards.

Usage guidelines

This command is available only on CSPC-GE16XP4L-E, CSPC-GE24L-E, CSPC-GP24GE8XP2L-E, CSPEX, and CEPC cards.

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

<Sysname> system-view

[Sysname] qos qmprofile myprofile

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

Related commands

display qos qmprofile interface

qos qmprofile

CBQ commands

queue af

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

Use undo queue af to restore the default.

Syntax

queue af bandwidth { bandwidth [ pir peak-information-rate ] | pct percentage }

undo queue af

Default

AF is not configured.

Views

Traffic behavior view

Predefined user roles

network-admin

Parameters

bandwidth: Specifies the minimum guaranteed bandwidth in the range of 64 to 100000000 kbps.

pir peak-information-rate: Specifies the PIR in the range of 64 to 100000000 kbps. CMPE-1104 cards do not support this option.

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

Usage guidelines

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

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

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

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

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

You cannot configure the queue af command together with the queue ef or queue wfq command in the same traffic behavior.

CSPC (except CSPC-GE16XP4L-E, CSPC-GE24L-E, and CSPC-GP24GE8XP2L-E) cards do not support the queue af command.

Examples

# Enable AF in traffic behavior database and set the minimum guaranteed bandwidth to 200 kbps for AF.

<Sysname> system-view

[Sysname] traffic behavior database

[Sysname-behavior-database] queue af bandwidth 200

queue ef

Use queue ef to enable expedited forwarding (EF) and set the guaranteed bandwidth for EF.

Use undo queue ef to restore the default.

Syntax

queue ef bandwidth { bandwidth [ cbs burst ] [ pir peak-information-rate ] | pct percentage [ cbs-ratio ratio ] }

undo queue ef

Default

EF is not configured.

Views

Traffic behavior view

Predefined user roles

network-admin

Parameters

bandwidth: Specifies the guaranteed bandwidth in the range of 64 to 100000000 kbps.

cbs burst: Specifies the CBS in the range of 1600 to 1000000000 bytes. The default is the bandwidth value multiplied by 25. To accommodate bursts, you must set the CBS to be greater than the amount of traffic transmitted at the bandwidth over 50 milliseconds.

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

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

pir peak-information-rate: Specifies the PIR in the range of 64 to 100000000 kbps. CMPE-1104 cards do not support this option.

Usage guidelines

This command and the queue af command are mutually exclusive in one traffic behavior.

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

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

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

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

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

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

CSPC (except CSPC-GE16XP4L-E, CSPC-GE24L-E, and CSPC-GP24GE8XP2L-E) cards do not support the queue ef command.

Examples

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

<Sysname> system-view

[Sysname] traffic behavior database

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

queue wfq

Use queue wfq to configure WFQ for the default class.

Use undo queue wfq to restore the default.

Syntax

queue wfq

undo queue wfq

Default

WFQ is not configured for the default class.

Views

Traffic behavior view

Predefined user roles

network-admin

Usage guidelines

CSPC (except CSPC-GE16XP4L-E, CSPC-GE24L-E, and CSPC-GP24GE8XP2L-E) cards do not support this command.

You cannot configure the queue wfq command together with the queue af or queue ef command in the same traffic behavior.

Examples

# Configure the default class to use WFQ.

<Sysname> system-view

[Sysname] traffic behavior test

[Sysname-behavior-test] queue wfq

weight

Use weight to set the WFQ weight.

Use undo weight to restore the default.

Syntax

weight weight-value

undo weight

Default

On CMPE-1104 cards, the WFQ weight is 1 for AF and BE queues, and the WFQ weight is 0 for the EF queue.

On CSPC-GE16XP4L-E, CSPC-GE24L-E, CSPC-GP24GE8XP2L-E, CSPEX (except CSPEX-1204), and CEPC cards, the WFQ weight is 1 for AF and EF queues, and the WFQ weight is 0 for the BE queue.

For POS interfaces and Ethernet interfaces on the CSPEX-1204 card, the WFQ weight is 1 for AF and EF queues, and the WFQ weight is 0 for the BE queue. For other interface types and subinterfaces on the CSPEX-1204 card, SP queuing is used.

Views

Traffic behavior view

Predefined user roles

network-admin

Parameters

weight-value: Specifies the weight value in the range of 1 to 63.

Usage guidelines

The following traffic is scheduled by using WFQ:

· Traffic between the minimum guaranteed bandwidth and PIR.

· Traffic between the maximum bandwidth and PIR.

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

This command must be used together with the queue af, queue ef, or queue wfq command.

CSPC (except CSPC-GE16XP4L-E, CSPC-GE24L-E, and CSPC-GP24GE8XP2L-E) cards do not support this command.

This command is available only on SPEX, CSPEX, and CEPC cardsCSPEX cardsCSPEX and CEPC cards if it is used together with the queue ef command.

On CMPE-1104 cards, the AF traffic exceeding its minimum guaranteed bandwidth and BE traffic are scheduled according to the WFQ weights. If remaining bandwidth is available, the EF traffic exceeding its minimum bandwidth can be sent.

On CSPEX (except CSPEX-1204) and CEPC cards, the AF traffic exceeding its minimum guaranteed bandwidth, EF traffic exceeding its guaranteed bandwidth, and BE traffic are scheduled according to the WFQ weights.

For POS interfaces and Ethernet interfaces on the CSPEX-1204 card, the AF traffic exceeding its minimum guaranteed bandwidth, EF traffic exceeding its guaranteed bandwidth, and BE traffic are scheduled according to the WFQ weights. For other interface types and subinterfaces on the CSPEX-1204 card, the following traffic types are in descending order of priority:

· EF traffic within the guaranteed bandwidth.

· AF traffic within the minimum guaranteed bandwidth.

· AF traffic exceeding the minimum guaranteed bandwidth.

· BE traffic.

· EF traffic exceeding the guaranteed bandwidth.

Examples

# Configure traffic behavior database as follows:

· Enable AF, and set the minimum guaranteed bandwidth to 200 kbps.

· Set the WFQ weight to 10 for traffic exceeding 200 kbps.

<Sysname> system-view

[Sysname] traffic behavior database

[Sysname-behavior-database] queue af bandwidth 200

[Sysname-behavior-database] weight 10

Congestion avoidance commands

WRED table commands

display qos wred interface

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

Syntax

In standalone mode:

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

In IRF mode:

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

Views

Any view

Predefined user roles

network-admin

network-operator

Parameters

interface-type interface-number: Specifies an interface by its type and number. If you do not specify an interface, this command displays the WRED information for all interfaces.

slot slot-number: Specifies a card by its slot number. This option is available only for aggregate interfaces. If you do not specify a member device, this command displays the WRED information for the master device. This option is available only for aggregate interfaces. (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. This option is available only for aggregate interfaces. If you do not specify this option, the command displays the WRED information for the global active MPU. This option is available only for aggregate interfaces. (In IRF mode.)

Examples

# Display the WRED information for all interfaces.

<Sysname> display qos wred interface

Interface: GigabitEthernet3/1/1

Current WRED configuration:

Applied WRED table name: queue-table1

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

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 gpro ymin ymax ypro rmin rmax rpro exp ECN

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

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

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

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

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

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

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

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

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

Table 32 Command output

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

qos wred apply

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

Use undo qos wred apply to restore the default.

Syntax

qos wred apply [ table-name ]

undo qos wred apply

Default

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

Views

Interface view

Predefined user roles

network-admin

Parameters

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

Examples

# Apply WRED table table1 to GigabitEthernet 3/1/1.

<Sysname> system-view

[Sysname] interface gigabitethernet 3/1/1

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

Related commands

display qos wred interface

display qos wred table

qos wred table

qos wred queue table

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

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

Syntax

qos wred queue table table-name

undo qos wred queue table table-name

Default

No WRED tables exist.

Views

System view

Predefined user roles

network-admin

Parameters

queue: Creates a queue-based WRED table, which drops packets based on the queue when congestion occurs.

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.

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

queue

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

Default

The low-limit argument is 100, the high-limit argument is 1000, and the discard-prob argument is 10.

Views

WRED table view

Predefined user roles

network-admin

Parameters

all: Specifies all queues.

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

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.

low limit low-limit: Specifies the lower limit for the average queue length, in the range of 0 to 12582912 packets.

high-limit high-limit: Specifies the upper limit for the average queue length, in the range of 0 to 12582912 packets. The value for the high-limit argument must be greater than the value for the low-limit argument.

discard-probability discard-prob: Specifies the drop probability in percentage, in the range of 0 to 100. When the average queue size is between the lower limit and the upper limit, packets are dropped according to this drop probability. This option is not configurable on CSPEX or CEPC cards.

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.

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 table

queue ecn

Use queue ecn to enable ECN for a queue.

Use undo queue ecn to restore the default.

Syntax

queue queue-id ecn

undo queue queue-id ecn

Default

ECN is disabled for a queue.

Views

WRED table view

Predefined user roles

network-admin

Parameters

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

Usage guidelines

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

CSPEX and CEPC cards do not support this command.

Examples

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

<Sysname> system-view

[Sysname] qos wred queue table queue-table1

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

Related commands

display qos wred table

qos wred table

queue weighting-constant

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

Use undo queue weighting-constant to restore the default.

Syntax

queue queue-id weighting-constant exponent

undo queue queue-id weighting-constant

Default

The exponent for average queue length calculation is 9.

Views

WRED table view

Predefined user roles

network-admin

Parameters

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

weighting-constant exponent: Specifies the WRED exponent for average queue length calculation, in the range of 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.

This command does not take effect on CSPEX or CEPC cards.

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

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

Parameters

car-name: Specifies a global CAR action by its name, which can be an aggregate CAR action or a hierarchical CAR action. 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

# Display information about all aggregate CAR actions.

<Sysname> display qos car name

Name: a

Mode: aggregative

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

Table 33 Command output

Field	Description
Name	Name of the global CAR action.
Mode	Type of the CAR action.
CIR CBS PIR EBS	Parameters for the CAR action.

qos car

Use qos car aggregative to configure an aggregate CAR action.

Use undo qos car to delete an aggregate CAR action.

Syntax

qos car car-name aggregative cir committed-information-rate [ cbs committed-burst-size [ ebs excess-burst-size ] ]

qos car car-name aggregative cir committed-information-rate [ cbs committed-burst-size ] pir peak-information-rate [ ebs excess-burst-size ]

undo qos car car-name

Default

No aggregate CAR action is configured.

Views

System view

Predefined user roles

network-admin

Parameters

car-name: Specifies the name of the 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 the range of 1 to 160000000 kbps.

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

ebs excess-burst-size: Specifies the EBS in the range of 0 to 256000000 bytes. The default is 512.

pir peak-information-rate: Specifies the PIR in the range of 1 to 160000000 kbps.

Usage guidelines

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

If you set the cir committed-information-rate option to a value in the range of 1 to 8 kbps on CSPEX cards (except CSPEX-1204 and CSPEX-1104-E) and CEPC cards, the actual setting takes effect. If you set this option to a value in the range of 1 to 8 kbps on any other card, 8 kbps always takes effect.

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

Examples

# Configure aggregate CAR action aggcar-1, where CIR is 200 and CBS is 2048.

<Sysname> system-view

[Sysname] qos car aggcar-1 aggregative cir 200 cbs 2048

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

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 clears statistics for all global CAR actions.

Examples

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

<Sysname> reset qos car name aggcar-1

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

In standalone mode:

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

In IRF mode:

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

Views

Any view

Predefined user roles

network-admin

network-operator

Parameters

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

slot slot-number: Specifies a card by its slot number. This option is available only for aggregate interfaces. If you do not specify a member device, this command displays the outgoing traffic statistics for the master device. This option is available only for aggregate interfaces. (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. This option is available only for aggregate interfaces. If you do not specify this option, the command displays the outgoing traffic statistics for the global active MPU. This option is available only for aggregate interfaces. (In IRF mode.)

Usage guidelines

Only the following traffic statistics can be displayed in the current software version:

· The number of forwarded green packets, the number of bytes forwarded for green packets, and the average rate of green packets in the most recent statistics collection interval.

· The number of dropped red packets, the number of bytes dropped for red packets, and the average rate of red packets in the most recent statistics collection interval.

On CSPEX-1204 cards, only the number of forwarded green packets and the number of bytes forwarded for green packets can be displayed.

Examples

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

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

Interface: GigabitEthernet3/1/1

Direction: Outbound

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

Dropped: 0 packets, 0 bytes, 0 pps, 0 bps

Queue 0

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

Dropped: 0 packets, 0 bytes, 0 pps, 0 bps

Green forwarded: 61 packets, 4758 bytes, 0 pps, 0 bps

Green dropped: 0 packets, 0 bytes, 0 pps, 0 bps

Yellow forwarded: 0 packets, 0 bytes, 0 pps, 0 bps

Yellow dropped: 0 packets, 0 bytes, 0 pps, 0 bps

Red forwarded: 0 packets, 0 bytes, 0 pps, 0 bps

Red dropped: 0 packets, 0 bytes, 0 pps, 0 bps

Total queue length: 0 packets

Current queue length: 0 packets

Queue 1

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

Dropped: 0 packets, 0 bytes, 0 pps, 0 bps

Green forwarded: 0 packets, 0 bytes, 0 pps, 0 bps

Green dropped: 0 packets, 0 bytes, 0 pps, 0 bps

Yellow forwarded: 0 packets, 0 bytes, 0 pps, 0 bps

Yellow dropped: 0 packets, 0 bytes, 0 pps, 0 bps

Red forwarded: 0 packets, 0 bytes, 0 pps, 0 bps

Red dropped: 0 packets, 0 bytes, 0 pps, 0 bps

Total queue length: 0 packets

Current queue length: 0 packets

Queue 2

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

Dropped: 0 packets, 0 bytes, 0 pps, 0 bps

Green forwarded: 0 packets, 0 bytes, 0 pps, 0 bps

Green dropped: 0 packets, 0 bytes, 0 pps, 0 bps

Yellow forwarded: 0 packets, 0 bytes, 0 pps, 0 bps

Yellow dropped: 0 packets, 0 bytes, 0 pps, 0 bps

Red forwarded: 0 packets, 0 bytes, 0 pps, 0 bps

Red dropped: 0 packets, 0 bytes, 0 pps, 0 bps

Total queue length: 0 packets

Current queue length: 0 packets

Queue 3

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

Dropped: 0 packets, 0 bytes, 0 pps, 0 bps

Green forwarded: 0 packets, 0 bytes, 0 pps, 0 bps

Green dropped: 0 packets, 0 bytes, 0 pps, 0 bps

Yellow forwarded: 0 packets, 0 bytes, 0 pps, 0 bps

Yellow dropped: 0 packets, 0 bytes, 0 pps, 0 bps

Red forwarded: 0 packets, 0 bytes, 0 pps, 0 bps

Red dropped: 0 packets, 0 bytes, 0 pps, 0 bps

Total queue length: 0 packets

Current queue length: 0 packets

Queue 4

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

Dropped: 0 packets, 0 bytes, 0 pps, 0 bps

Green forwarded: 0 packets, 0 bytes, 0 pps, 0 bps

Green dropped: 0 packets, 0 bytes, 0 pps, 0 bps

Yellow forwarded: 0 packets, 0 bytes, 0 pps, 0 bps

Yellow dropped: 0 packets, 0 bytes, 0 pps, 0 bps

Red forwarded: 0 packets, 0 bytes, 0 pps, 0 bps

Red dropped: 0 packets, 0 bytes, 0 pps, 0 bps

Total queue length: 0 packets

Current queue length: 0 packets

Queue 5

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

Dropped: 0 packets, 0 bytes, 0 pps, 0 bps

Green forwarded: 0 packets, 0 bytes, 0 pps, 0 bps

Green dropped: 0 packets, 0 bytes, 0 pps, 0 bps

Yellow forwarded: 0 packets, 0 bytes, 0 pps, 0 bps

Yellow dropped: 0 packets, 0 bytes, 0 pps, 0 bps

Red forwarded: 0 packets, 0 bytes, 0 pps, 0 bps

Red dropped: 0 packets, 0 bytes, 0 pps, 0 bps

Total queue length: 0 packets

Current queue length: 0 packets

Queue 6

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

Dropped: 0 packets, 0 bytes, 0 pps, 0 bps

Green forwarded: 0 packets, 0 bytes, 0 pps, 0 bps

Green dropped: 0 packets, 0 bytes, 0 pps, 0 bps

Yellow forwarded: 0 packets, 0 bytes, 0 pps, 0 bps

Yellow dropped: 0 packets, 0 bytes, 0 pps, 0 bps

Red forwarded: 0 packets, 0 bytes, 0 pps, 0 bps

Red dropped: 0 packets, 0 bytes, 0 pps, 0 bps

Total queue length: 0 packets

Current queue length: 0 packets

Queue 7

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

Dropped: 0 packets, 0 bytes, 0 pps, 0 bps

Green forwarded: 0 packets, 0 bytes, 0 pps, 0 bps

Green dropped: 0 packets, 0 bytes, 0 pps, 0 bps

Yellow forwarded: 0 packets, 0 bytes, 0 pps, 0 bps

Yellow dropped: 0 packets, 0 bytes, 0 pps, 0 bps

Red forwarded: 0 packets, 0 bytes, 0 pps, 0 bps

Red dropped: 0 packets, 0 bytes, 0 pps, 0 bps

Total queue length: 0 packets

Current queue length: 0 packets

Table 34 Command output

Field	Description
Interface	Interface for which queue-based traffic statistics are displayed.
Direction	Direction of traffic for which statistics are collected.
Forwarded	Total number of forwarded packets, total number of bytes for forwarded packets, and average rate of forwarded packets in the most recent statistics collection interval. The interval is set by using the flow-interval command.
Dropped	Total number of dropped packets, total number of bytes for dropped packets, and average rate of dropped packets in the most recent statistics collection interval. The interval is set by using the flow-interval command.
Green forwarded	Total number of forwarded green packets, total number of bytes for forwarded green packets, and average rate of forwarded green packets in the most recent statistics collection interval. The interval is set by using the flow-interval command.
Green dropped	Total number of dropped green packets, total number of bytes for dropped green packets, and average rate of dropped green packets in the most recent statistics collection interval. The interval is set by using the flow-interval command.
Yellow forwarded	Total number of forwarded yellow packets, total number of bytes for forwarded yellow packets, and average rate of forwarded yellow packets in the most recent statistics collection interval. The interval is set by using the flow-interval command.
Yellow dropped	Total number of dropped yellow packets, total number of bytes for dropped yellow packets, and average rate of dropped yellow packets in the most recent statistics collection interval. The interval is set by using the flow-interval command.
Red forwarded	Total number of forwarded red packets, total number of bytes for forwarded red packets, and average rate of forwarded red packets in the most recent statistics collection interval. The interval is set by using the flow-interval command.
Red dropped	Total number of dropped red packets, total number of bytes for dropped red packets, and average rate of dropped red packets in the most recent statistics collection interval. The interval is set by using the flow-interval command.
Current queue length	Number of packets in the queue.

Related commands

reset counters interface (Interface Command Reference)

qos queue-statistics

Use qos queue-statistics to enable queue-based traffic accounting.

Use undo qos queue-statistics to disable queue-based traffic accounting.

Syntax

qos queue-statistics { inbound | outbound }

undo qos queue-statistics { inbound | outbound }

Default

Queue-based traffic accounting is enabled.

Views

System view

Predefined user roles

network-admin

Parameters

inbound: Specifies the inbound direction. You can configure this keyword, but it does not take effect.

outbound: Specifies the outbound direction.

Usage guidelines

This command is available only on CSPEX and CEPC cards.

Examples

# Enable queue-based outgoing traffic accounting.

<Sysname> system-view

[Sysname] qos queue-statistics outbound

Related commands

display qos queue-statistics interface outbound

QPPB commands

bgp-policy

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

Use undo bgp-policy to restore the default.

Syntax

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

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

Default

QPPB is disabled.

Views

Interface view

Predefined user roles

network-admin

Parameters

destination: Searches the routing table by destination IP address.

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

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

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

Usage guidelines

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

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

If you configure two bgp-policy commands by using the source and destination keywords, the newly entered command overwrites the previously entered command.

This command is available only on CSPEX (except CSPEX-1204) and CEPC cards.

Examples

# Configure Ten-GigabitEthernet 3/1/1 to get the IP precedence and local QoS ID by looking up routes based on source IP address.

<Sysname> system-view

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

[Sysname-Ten-GigabitEthernet3/1/1] bgp-policy source ip-prec-map ip-qos-map

Related commands

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

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

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

11-ACL and QoS Command Reference

QoS policy commands

display traffic classifier

remark ip-precedence

remark qos-local-id

import (priority map view)

qos gts (interface view)

display qos queue sp interface

qos wrr weight

qos bandwidth queue

qos wfq

qos wfq weight

Queue scheduling profile commands

display qos qmprofile interface

qos apply qmprofile (interface view)

qos apply qmprofile fabric

display qos queue-statistics interface outbound

Cloud & AI

InterConnect

Intelligent Terminal Products

Product Support Services

Technical Service Solutions

Resource Center

Policy

Online Help

Become a Partner

Partner Resources

Partner Business Management

Company Information

News & Events

Contact Us