- Table of Contents
- Related Documents
-
| Title | Size | Download |
|---|---|---|
| 02-QoS commands | 350.97 KB |
Contents
display qos policy control-plane
display qos policy control-plane management
display qos policy control-plane management pre-defined
display qos policy control-plane pre-defined
reset qos policy control-plane
reset qos policy control-plane management
Hardware congestion management commands
display qos queue wfq interface
Queue scheduling profile commands
display qos qmprofile configuration
display qos qmprofile interface·
Queue-based accounting commands
QoS policy commands
In this document, the EB, EC2, FD, and FG cards refer to the cards with silkscreens ending with EB, FD, EC2, and FG, respectively.
In this document, the basic ACL mode is an ACL hardware mode. For more information, see ACL and QoS Configuration Guide.
Traffic class commands
display traffic classifier
Use display traffic classifier to display traffic classes.
Syntax
In standalone mode:
display traffic classifier user-defined [ classifier-name ] [ slot slot-number ]
In IRF mode:
display traffic classifier user-defined [ classifier-name ] [ chassis chassis-number slot slot-number ]
Views
Any view
Predefined user roles
network-admin
network-operator
mdc-admin
mdc-operator
Parameters
user-defined: Specifies user-defined traffic classes.
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 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 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 on 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-
|
Field |
Description |
|
Classifier |
Traffic class name and its match criteria. |
|
Operator |
Match operator you set for the traffic class. If the operator is AND, the traffic class matches the packets that match all its match criteria. If the operator is OR, the traffic class matches the packets that match any of its match criteria. |
|
Rule(s) |
Match criteria. |
if-match
Use if-match to define a match criterion.
Use undo if-match to delete a match criterion.
Syntax
if-match match-criteria
undo if-match match-criteria
Default
No match criterion is configured.
Views
Traffic class view
Predefined user roles
network-admin
mdc-admin
Parameters
match-criteria: Specifies a match criterion. Table 2 shows the available match criteria.
Table 2 Available match criteria
|
Option |
Description |
|
acl [ ipv6 ] { acl-number | name acl-name } |
Matches an ACL. The value range for the acl-number argument is 2000 to 5999 for IPv4 ACLs, and 2000 to 3999 or 10000 to 42767 for IPv6 ACLs. The acl-name argument is a case-insensitive string of 1 to 63 characters, which must start with an English letter. To avoid confusion, make sure the argument is not all. If a QoS policy uses a user-defined ACL for traffic classification, the user-defined ACL takes effect only when the QoS policy is applied to the inbound direction. On an EB, EC2, or FD card operating in basic ACL mode, a QoS policy does not support a class that uses IPv6 ACLs or user-defined ACLs as match criteria. |
|
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. If a QoS policy that uses this match criterion in a class is to be applied to the control plane, the following restrictions apply: · The class cannot use any other match criterion. · The traffic behavior for the class can only have the rate limiting action configured by using the packet-rate command. If a QoS policy that uses this match criterion in a class is to be applied to the management interface control plane, the class cannot use any other match criterion, and the traffic behavior for the class can only have the traffic policing action (configured by using the car command). |
|
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. This option is not supported in a global or VLAN QoS policy. On an EB, EC2, or FD card operating in basic ACL mode, a QoS policy does not support a class that uses the 802.1p priority values in inner VLAN tags as match criteria. |
|
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. This option is not supported in a global or VLAN QoS policy. On an EB, EC2, or FD card operating in basic ACL mode, a QoS policy does not support a class that uses the VLAN IDs in inner VLAN tags as match criteria. |
|
destination-mac mac-address |
Matches a destination MAC address. On an EB, EC2, or FD card operating in basic ACL mode, suppose a QoS policy contains a class using a destination MAC address as a match criterion. · If the QoS policy is applied to the incoming traffic, the class does not take effect on IPv4 packets. · If the QoS policy is applied to the outgoing traffic, the class does not take effect on IPv4 or IPv6 packets. · If the QoS policy is applied to the incoming or outgoing traffic, the class does not take effect on ARP packets. |
|
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. |
|
forwarding-layer { bridge | route } |
Matches Layer 2 forwarded packets or Layer 3 forwarded packets. · bridge—Matches Layer 2 forwarded packets. · route—Matches Layer 3 forwarded packets. |
|
inbound-interface interface-type interface-number |
Matches an input interface specified by its type and number. A QoS policy configured with this match criterion can be applied only to control planes. To apply the QoS policy successfully, make sure the input interface specified and the control plane to which you apply the QoS policy belong to the same card. When you use this match criterion for a class, you can only configure a traffic filtering (filter) or traffic policing (car) action in the behavior associated with the class. |
|
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. On EB, EC2, or FD card operating in basic ACL mode, a QoS policy applied to the outgoing traffic does not support a class that uses MPLS EXP values as match criteria. |
|
mpls-label { label-value&<1-8> | label-value1 to label-value2 } |
Matches MPLS label values. The label-value&<1-8> argument specifies a list of up to eight MPLS label values. The label-value1 to label-value2 option specifies a range of MPLS label values. The value for label-value1 must be greater than or equal to the value for label-value2. The value range for the label-value argument is 0 to 1048575. On an EB, EC2, or FD card operating in basic ACL mode, a QoS policy does not support a class that uses MPLS labels as match criteria. |
|
protocol protocol-name |
Matches a protocol. The protocol-name argument can be arp, ip, or ipv6. On an EB, EC2, or FD card operating in basic ACL mode, a QoS policy does not support a class that uses the IPv6 protocol as a match criterion. |
|
second-mpls-exp exp-value&<1-8> |
Matches inner 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. On an EB, EC2, or FD card operating in basic ACL mode, a QoS policy does not support a class that uses inner MPLS EXP values as match criteria. |
|
second-mpls-label { label-value&<1-8> | label-value1 to label-value2 } |
Matches inner MPLS label values. The label-value&<1-8> argument specifies a list of up to eight MPLS label values. The label-value1 to label-value2 option specifies a range of MPLS label values. The value for label-value1 must be greater than or equal to the value for label-value2. The value range for the label-value argument is 0 to 1048575. On an EB, EC2, or FD card operating in basic ACL mode, a QoS policy does not support a class that uses inner MPLS labels as match criteria. |
|
service-dot1p dot1p-value&<1-8> |
Matches 802.1p priority values in outer VLAN tags. The dot1p-value&<1-8> argument specifies a space-separated list of up to eight 802.1p priority values. The value range for the dot1p-value argument is 0 to 7. |
|
service-vlan-id vlan-id-list |
Matches VLAN IDs in outer VLAN tags. The vlan-id-list argument specifies a space-separated list of up to 10 VLAN items. Each item specifies a VLAN or a range of VLANs in the form of vlan-id1 to vlan-id2. The value for vlan-id2 must be greater than or equal to the value for vlan-id1. The value range for the vlan-id argument is 1 to 4094. |
|
source-mac mac-address |
Matches a source MAC address. On an EB, EC2, or FD card operating in basic ACL mode, suppose a QoS policy contains a class using a source MAC address as a match criterion. · If the QoS policy is applied to the incoming traffic, the class does not take effect on IPv4 packets. · If the QoS policy is applied to the outgoing traffic, the class does not take effect on IPv4 or IPv6 packets. · If the QoS policy is applied to the incoming or outgoing traffic, the class does not take effect on ARP packets. |
Table 3 Available system-defined control plane protocols
|
Protocol |
Description |
|
default |
Protocol packets other than those listed in this table |
|
ARP packets |
|
|
BGP packets |
|
|
IPv6 BGP packets |
|
|
dhcp |
DHCP packets |
|
DHCP snooping packets |
|
|
IPv6 DHCP packets |
|
|
DLDP packets |
|
|
ftp |
FTP packets |
|
MVRP packets |
|
|
HTTP packets |
|
|
HTTPS packets |
|
|
ICMP packets |
|
|
ICMPv6 packets |
|
|
IGMP packets |
|
|
IS-IS packets |
|
|
LACP packets |
|
|
ldp |
LDP packets |
|
LLDP packets |
|
|
mld |
MLD packets |
|
ntp |
NTP packets |
|
oam |
OAM packets |
|
OSPF multicast packets |
|
|
OSPF unicast packets |
|
|
OSPFv3 multicast packets |
|
|
OSPFv3 unicast packets |
|
|
PIM multicast packets |
|
|
PIM unicast packets |
|
|
IPv6 PIM multicast packets |
|
|
IPv6 PIM unicast packets |
|
|
Portal packets |
|
|
RADIUS packets |
|
|
RIP packets |
|
|
RIPng packets |
|
|
SNMP packets |
|
|
ssh |
SSH packets |
|
STP packets |
|
|
TACACS packets |
|
|
Telnet packets |
|
|
tftp |
TFTP packets |
|
UDP helper packets |
|
|
VRRP packets |
Usage guidelines
When defining match criteria, use the usage guidelines described in these subsections.
Defining an ACL-based match criterion
· If the ACL as a match criterion does not exist, the traffic class cannot be applied to hardware.
· You can configure multiple ACL-based match criteria for a class.
· In a class with the operator as OR, you can add two if-match statements that use the same ACL as the match criterion. In one statement, specify the ACL by its name. In the other statement, specify the ACL by its number. In a class with the operator as AND, you can add only one if-match statement that uses an ACL as a match criterion by specifying the name or number of the ACL.
· The deny action in an ACL rule means not executing the behavior of the corresponding class-behavior association. The permit action in an ACL rule means executing the behavior of the corresponding class-behavior association.
Defining a criterion to match a destination MAC address
· You can configure multiple destination MAC address match criteria for a traffic class.
· A destination MAC address match criterion is significant only to Ethernet interfaces.
Defining a criterion to match a source MAC address
· You can configure multiple source MAC address match criteria for a traffic class.
· A criterion to match a source MAC address is significant only to Ethernet interfaces.
Defining a criterion to match DSCP values
· You can configure multiple DSCP match criteria for a traffic class. All defined DSCP values are automatically sorted in ascending order.
· You can configure up to eight DSCP values in one command line. If the same DSCP value is specified multiple times, the system considers the values as one. If a packet matches one of the defined DSCP values, it matches the if-match clause.
· To delete a criterion that matches DSCP values, the specified DSCP values must be identical with those defined in the criterion (the sequence can be different).
Defining a criterion to match 802.1p priority
· You can configure multiple 802.1p priority match criteria for a traffic class. All the defined 802.1p values are automatically arranged in ascending order.
· You can configure up to eight 802.1p priority values in one command line. If the same 802.1p priority value is specified multiple times, the system considers the values as one. If a packet matches one of the defined 802.1p priority values, it matches the if-match clause.
· To delete a criterion that matches 802.1p priority values, the specified 802.1p priority values in the command must be identical with those defined in the criterion (the sequence can be different).
Defining a criterion to match IP precedence values
· You can configure multiple IP precedence match criteria for a traffic class. The defined IP precedence values are automatically arranged in ascending order.
· You can configure up to eight IP precedence values in one command line. If the same IP precedence value is specified multiple times, the system considers the values as one. If a packet matches one of the defined IP precedence values, it matches the if-match clause.
· To delete a criterion that matches IP precedence values, the specified IP precedence values in the command must be identical with those defined in the criterion (the sequence can be different).
Defining a criterion to match MPLS EXP values
· You can configure multiple MPLS EXP match criteria for a traffic class. The defined MPLS EXP values are automatically arranged in ascending order.
· You can configure up to eight MPLS EXP values in one command line. If the same MPLS EXP value is specified multiple times, the system considers the values as one. If a packet matches one of the defined MPLS EXP values, it matches the if-match clause.
· To delete a criterion that matches MPLS EXP values, the specified MPLS EXP values in the command must be identical with those defined in the criterion (the sequence can be different).
· The MPLS EXP field exists only in MPLS packets, so this match criterion takes effect only on MPLS packets.
· As for software forwarding QoS, MPLS packets do not support IP-related matching rules.
Defining a criterion to match MPLS labels
· You can configure multiple MPLS label match criteria for a traffic class. The defined MPLS labels are automatically arranged in ascending order.
· You can configure multiple MPLS label values in one command. If the same MPLS label value is specified multiple times, the system considers the values as one. If a packet matches one of the defined MPLS label values, it matches the if-match clause.
· To delete a criterion that matches MPLS label values, the specified MPLS label values in the command must be identical with those defined in the criterion (the sequence can be different).
Defining a criterion to match VLAN IDs in inner or outer VLAN tags
· You can configure multiple VLAN ID match criteria for a traffic class. The defined VLAN IDs are automatically arranged in ascending order.
· You can configure multiple VLAN IDs in one command line. If the same VLAN ID is specified multiple times, the system considers the VLAN IDs as one. If a packet matches one of the defined VLAN IDs, it matches the if-match clause.
· To delete a criterion that matches VLAN IDs, the specified VLAN IDs in the command must be identical with those defined in the criterion (the sequence can be different).
· You can use the VLAN ID in the outer VLAN tag to match single-tagged packets.
Defining a criterion to match control plane protocols
· You can configure multiple control plane protocol match criteria for a traffic class.
· You can configure up to eight control plane protocols in one command line for a class with the operator as OR. If the same control plane protocol is specified multiple times, the system considers them as one. If a packet matches one of the defined control plane protocols, it matches the if-match clause.
· To delete a criterion that matches control plane protocols, the specified control plane protocols in the command must be identical with those defined in the criterion (the sequence can be different).
· If you specify different rate limit values for the same protocol in multiple class-behavior associations, the smallest rate limit value takes effect.
Examples
# Define a match criterion for traffic class class1 to match the packets with 0050-ba27-bed3 as their destination MAC address.
<Sysname> system-view
[Sysname] traffic classifier class1
[Sysname-classifier-class1] if-match destination-mac 0050-ba27-bed3
# Define a match criterion for traffic class class2 to match the packets with 0050-ba27-bed2 as their source MAC address.
<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 an 802.1p priority of 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 an 802.1p priority of 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 the packets with a DSCP value of 1.
<Sysname> system-view
[Sysname] traffic classifier class1
[Sysname-classifier-class1] if-match dscp 1
# Define a match criterion for traffic class class1 to match the packets with an IP precedence value of 6.
<Sysname> system-view
[Sysname] traffic classifier class1
[Sysname-classifier-class1] if-match ip-precedence 6
# Define a match criterion for traffic class class1 to match the packets with a local precedence value of 1.
<Sysname> system-view
[Sysname] traffic classifier class1
[Sysname-classifier-class1] if-match local-precedence 1
# Define a match criterion for traffic class class1 to match IP packets.
<Sysname> system-view
[Sysname] traffic classifier class1
[Sysname-classifier-class1] if-match protocol ip
# Define a match criterion for traffic class class1 to match the double-tagged packets with a VLAN ID of 6 in the inner VLAN tag.
<Sysname> system-view
[Sysname] traffic classifier class1
[Sysname-classifier-class1] if-match customer-vlan-id 6
# Define a match criterion for traffic class class1 to match the packets with a VLAN ID of 7 in the outer VLAN tag.
<Sysname> system-view
[Sysname] traffic classifier class1
[Sysname-classifier-class1] if-match service-vlan-id 7
# Define a match criterion for traffic class class1 to match packets with an MPLS label of 1.
<Sysname> system-view
[Sysname] traffic classifier class1
[Sysname-classifier-class1] if-match mpls-label 1
# Define a match criterion for traffic class class1 to match Layer 2 forwarded packets.
<Sysname> system-view
[Sysname] traffic classifier class1
[Sysname-classifier-class1] if-match forwarding-layer bridge
# Define a match criterion for the traffic class class1 to match ARP packets.
<Sysname> system-view
[Sysname] traffic classifier class1
[Sysname-classifier-class1] if-match control-plane protocol arp
traffic classifier
Use traffic classifier to create a traffic class and enter traffic class view.
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 class exists.
Views
System view
Predefined user roles
network-admin
mdc-admin
Parameters
classifier-name: Specifies the name of the traffic class to be created, 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 delete the action.
Syntax
accounting { byte | packet }
undo accounting
Default
No traffic accounting action is configured.
Views
Traffic behavior view
Predefined user roles
network-admin
mdc-admin
Parameters
byte: Counts traffic in bytes.
packet: Counts traffic in packets. This keyword affects the unit of CAR statistics.
Examples
# Configure a traffic accounting action in traffic behavior database to count traffic in bytes.
<Sysname> system-view
[Sysname] traffic behavior database
[Sysname-behavior-database] accounting byte
car
Use car to configure a CAR action in a traffic behavior.
Use undo car to delete the action.
Syntax
car cir committed-information-rate [ cbs committed-burst-size [ ebs excess-burst-size ] ] [ red action ]
car cir committed-information-rate [ cbs committed-burst-size ] pir peak-information-rate [ ebs excess-burst-size ] [ red action ]
undo car
Default
No CAR action is configured.
Views
Traffic behavior view
Predefined user roles
network-admin
mdc-admin
Parameters
cir committed-information-rate: Specifies the committed information rate (CIR), an average traffic rate. The value range for committed-information-rate is 1 to 100000000 kbps.
cbs committed-burst-size: Specifies the committed burst size (CBS) in bytes, in the range of 1553 to 2147450880. By default, the CBS is the amount of traffic transmitted at the rate of CIR over 500 milliseconds. The CBS must be greater than the maximum packet length. If the traffic transmitted at the rate of CIR over 500 milliseconds is smaller than 1553, the default CBS is 1553.
ebs excess-burst-size: Specifies the excess burst size (EBS) in bytes, in the range of 0 to 2147450880 and defaulting to 0.
pir peak-information-rate: Specifies the peak information rate (PIR) in the range of 1 to 100000000 kbps.
red action: Specifies the action to take on the packet that conforms to neither CIR nor PIR. The default is discard.
action: Sets the action to take on the packet:
· discard: Drops the packet.
· pass: Permits the packet to pass through.
Usage guidelines
To use two rates for traffic policing, configure the car command with the pir peak-information-rate option. To use one rate for traffic policing, configure the car command without the pir peak-information-rate option.
A QoS policy that uses a CAR action can be applied to either the inbound or outbound direction of an interface.
If you configure the car command multiple times in the same traffic behavior, the most recent configuration takes effect.
H3C recommends that you set the committed-burst-size argument, if necessary, to be greater than 6.25 times the committed-information-rate argument to accommodate traffic bursts.
Examples
# Configure a CAR action in traffic behavior database as follows:
· Set the CIR to 200 kbps and CBS to 50000 bytes.
· Transmit the conforming packets, and discard the excess packets.
<Sysname> system-view
[Sysname] traffic behavior database
[Sysname-behavior-database] car cir 200 cbs 50000 red discard
display traffic behavior
Use display traffic behavior to display traffic behaviors.
Syntax
In standalone mode:
display traffic behavior user-defined [ behavior-name ] [ slot slot-number ]
In IRF mode:
display traffic behavior user-defined [ behavior-name ] [ chassis chassis-number slot slot-number ]
Views
Any view
Predefined user roles
network-admin
network-operator
mdc-admin
mdc-operator
Parameters
user-defined: Specifies user-defined traffic behaviors.
behavior-name: Specifies a traffic 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 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 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 traffic behaviors on the global active MPU. (In IRF mode.)
Examples
# Display all user-defined traffic behaviors.
<Sysname> display traffic behavior user-defined
User-defined behavior information:
Behavior: 1 (ID 100)
Marking:
Remark dscp 3
Committed Access Rate:
CIR 112 (kbps), CBS 7000 (Bytes), EBS 512 (Bytes)
Red action : discard
Primap pre-defined color table: dot1p-lp
Behavior: 2 (ID 101)
Accounting enable: Packet
Filter enable: Permit
Marking:
Remark mpls-exp 4
Redirecting:
Redirect to the CPU
Mirroring:
Mirror to the VLAN: VLAN 1000
Behavior: 3 (ID 102)
-none-
|
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. |
|
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. |
|
Redirecting |
Information about traffic redirecting. |
|
Mirroring |
Information about traffic mirroring. |
|
none |
No other traffic behavior is configured. |
filter
Use filter to configure a traffic filtering action in a traffic behavior.
Use undo filter to delete the action.
Syntax
filter { deny | permit }
undo filter
Default
No traffic filtering action is configured.
Views
Traffic behavior view
Predefined user roles
network-admin
mdc-admin
Parameters
deny: Drops packets.
permit: Transmits packets.
Examples
# Configure a traffic filtering action as deny in traffic behavior database.
<Sysname> system-view
[Sysname] traffic behavior database
[Sysname-behavior-database] filter deny
nest top-most
Use nest top-most to configure a VLAN tag adding action in a traffic behavior.
Use undo nest top-most to delete the action.
Syntax
nest top-most vlan vlan-id
undo nest top-most
Default
No VLAN tag adding action is configured.
Views
Traffic behavior view
network-admin
mdc-admin
Parameters
vlan-id vlan-id: Specifies the VLAN ID to be added, in the range of 1 to 4094.
Usage guidelines
If a QoS policy contains a VLAN tag adding action, apply it only to the incoming traffic of an interface.
If the traffic behavior already contains a VLAN tag adding action, the new one overwrites the old one.
Examples
# Configure traffic behavior b1 to add VLAN tag 123.
<Sysname> system-view
[Sysname] traffic behavior b1
[Sysname-behavior-b1] nest top-most vlan 123
packet-rate
Use packet-rate to configure a protocol packet rate limiting action in a traffic behavior.
Use undo packet-rate to delete the action.
packet-rate value
undo packet-rate
View
Traffic behavior view
Predefined user roles
network-admin
mdc-admin
Parameters
value: Specifies the protocol packet rate in the range of 1 to 1048575 pps.
Usage guidelines
The protocol packet rate limiting function limits the rate of protocol packets sent to the CPU, and it guarantees the normal operation of the CPU.
Examples
# Configure the behavior copp to rate-limit the protocol packets sent to the CPU to 1600 pps.
<Sysname> system-view
[Sysname] traffic behavior copp
[Sysname-behavior-copp] packet-rate 1600
primap pre-defined color
Use primap pre-defined color to configure an 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
mdc-admin
Parameters
pre-defined: Pre-defined priority mapping table.
color: Uses colored priority mapping tables for priority mapping.
The switch provides the following types of priority maps.
Table 5 Priority maps
|
Priority map |
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
You must use the primap pre-defined color command together 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
display qos map-table color
redirect
Use redirect to configure a traffic redirecting action in a traffic behavior.
Use undo redirect to delete the action.
Syntax
redirect { cpu | interface interface-type interface-number [ track-oap ] [ vlan vlan-id ] }
undo redirect { cpu | interface interface-type interface-number }
Default
No traffic redirecting action is configured.
Views
Traffic behavior view
Predefined user roles
network-admin
mdc-admin
Parameters
cpu: Redirects traffic to the CPU.
interface: Redirects traffic to an interface.
interface-type interface-number: Specifies an interface by its type and number. Only Layer 2 Ethernet interfaces and Layer 2 aggregate interfaces are supported.
track-oap: Redirects traffic only when OAP clients are present.
vlan vlan-id: Tags traffic redirected to an interface with the VLAN tag specified by vlan-id. The value range for vlan-id is 1 to 4094.
Usage guidelines
Redirecting traffic to the CPU and redirecting traffic to an interface are mutually exclusive with each other in the same traffic behavior. The most recently configured redirecting action takes effect.
If you specify the track-oap keyword, the switch detects the presence of OAP clients and redirects traffic to the interface only when OAP clients are present.
In IRF mode, the switch does not support redirecting traffic to an aggregate interface.
In IRF mode, the switch supports multichassis redirecting only for OAP cards. Multichassis redirecting refers to redirecting traffic to an outgoing interface on a different IRF member device than the incoming interface.
Examples
# Configure redirecting traffic to GigabitEthernet 3/0/1 in traffic behavior database.
<Sysname> system-view
[Sysname] traffic behavior database
[Sysname-behavior-database] redirect interface gigabitethernet 3/0/1
Related commands
· classifier behavior
· qos policy
· traffic behavior
remark dot1p
Use remark dot1p to configure an 802.1p priority marking action in a traffic behavior.
Use undo remark dot1p to delete the action.
Syntax
remark dot1p dot1p-value
undo remark dot1p
Default
No 802.1p priority marking action is configured.
Views
Traffic behavior view
Predefined user roles
network-admin
mdc-admin
Parameters
dot1p-value: Specifies the 802.1p priority to be marked for packets, in the range of 0 to 7.
Examples
# Configure traffic behavior database to mark matching traffic with 802.1p priority 2.
<Sysname> system-view
[Sysname] traffic behavior database
[Sysname-behavior-database] remark dot1p 2
remark drop-precedence
Use remark drop-precedence to configure a drop priority marking action in a traffic behavior.
Use undo remark drop-precedence to delete the action.
Syntax
remark drop-precedence drop-precedence-value
undo remark drop-precedence
Default
No drop priority marking action is configured.
Views
Traffic behavior view
Predefined user roles
network-admin
mdc-admin
Parameters
drop-precedence-value: Specifies the drop priority to be marked for packets, in the range of 0 to 2.
Usage guidelines
The command applies only to incoming traffic.
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 delete the action.
Syntax
remark dscp dscp-value
undo remark dscp
Default
No DSCP marking action is configured.
Views
Traffic behavior view
Predefined user roles
network-admin
mdc-admin
Parameters
dscp-value: Specifies a DSCP value, which can be a number from 0 to 63 or a keyword in Table 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 |
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 local-precedence
Use remark local-precedence to configure a local precedence marking action in a traffic behavior.
Use undo remark local-precedence to delete the action.
Syntax
remark local-precedence local-precedence-value
undo remark local-precedence
Default
No local precedence marking action is configured.
Views
Traffic behavior view
Predefined user roles
network-admin
mdc-admin
Parameters
local-precedence-value: Specifies the local precedence to be marked for packets, in the range of 0 to 7.
Examples
# Configure traffic behavior database to mark matching traffic with local precedence 2.
<Sysname> system-view
[Sysname] traffic behavior database
[Sysname-behavior-database] remark local-precedence 2
remark service-vlan-id
Use remark service-vlan-id to configure an SVLAN marking action in a traffic behavior.
Use undo remark service-vlan-id to delete the action.
Syntax
remark service-vlan-id vlan-id
undo remark service-vlan-id
Default
No SVLAN marking action is configured.
Views
Traffic behavior view
Predefined user roles
network-admin
mdc-admin
Parameters
vlan-id: Specifies an SVLAN ID in the range of 1 to 4094.
Examples
# Configure traffic behavior b1 to mark matching packets with SVLAN 222.
<Sysname> system-view
[Sysname] traffic behavior b1
[Sysname-behavior-b1] remark service-vlan-id 222
traffic behavior
Use traffic behavior to create a traffic behavior and enter traffic behavior view.
Use undo traffic behavior to delete a traffic behavior.
Syntax
traffic behavior behavior-name
undo traffic behavior behavior-name
Default
No traffic behavior exists.
Views
System view
Predefined user roles
network-admin
mdc-admin
Parameters
behavior-name: Specifies a name for the traffic behavior, a case-sensitive string of 1 to 31 characters.
Examples
# Create a traffic behavior named behavior1.
<Sysname> system-view
[Sysname] traffic behavior behavior1
[Sysname-behavior-behavior1]
Related commands
display traffic behavior
QoS policy commands
classifier behavior
Use classifier behavior to associate a traffic behavior with a traffic class in a QoS policy.
Use undo classifier to remove a traffic class from a QoS policy.
Syntax
classifier classifier-name behavior behavior-name [ mode dcbx ]
undo classifier classifier-name
Default
No traffic behavior is associated with a traffic class.
Views
QoS policy view
Predefined user roles
network-admin
mdc-admin
Parameters
classifier-name: Specifies a traffic class by its name, a case-sensitive string of 1 to 31 characters.
behavior-name: Specifies a traffic behavior by its name, a case-sensitive string of 1 to 31 characters.
mode dcbx: Indicates that the class-behavior association applies only to DCBX. For more information about DCBX, see Layer 2—LAN Switching Configuration Guide.
Usage guidelines
A traffic class can be associated with only 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
Related commands
qos policy
control-plane
Use control-plane to enter control plane view.
Syntax
In standalone mode:
control-plane slot slot-number
In IRF mode:
control-plane chassis chassis-number slot slot-number
Views
System view
Predefined user roles
network-admin
mdc-admin
Parameters
slot slot-number: Specifies a card by its slot number. (In standalone mode.)
chassis chassis-number slot slot-number: Specifies a card on an IRF member device. The chassis-number argument represents the ID of the IRF member device. The slot-number argument represents the slot number of the card. (In IRF mode.)
Examples
# (In standalone mode.) Enter the control plane view of card 3.
<Sysname> system-view
[Sysname] control-plane slot 3
[Sysname-cp-slot3]
# (In IRF mode.) Enter the control plane view of card 3 on IRF member device 1.
<Sysname> system-view
[Sysname] control-plane chassis 1 slot 3
[Sysname-cp-chassis1-slot3]
control-plane management
Use control-plane management to enter management interface control plane view.
Syntax
control-plane management
Views
System view
Predefined user roles
network-admin
mdc-admin
Examples
# Enter management interface control plane view.
<Sysname> system-view
[Sysname] control-plane management
[Sysname-cp-management]
display qos policy
Use display qos policy to display the configuration of 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
mdc-admin
mdc-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 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 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 on the global active MPU. (In IRF mode.)
Examples
# Display the configuration of all user-defined QoS policies.
<Sysname> display qos policy user-defined
User Defined QoS Policy Information:
Policy: qpolicy (ID 100)
Classifier: tc1 (ID 0)
Behavior: tb1
Marking:
Remark dot1p 5
Committed Access Rate:
CIR 1000 (kbps), CBS 100000 (Bytes), EBS 0 (Bytes)
Red action: discard
For the output description, see Table 1 and Table 4.
display qos policy control-plane
Use display qos policy control-plane to display the QoS policy applied to the control plane of a card.
Syntax
In standalone mode:
display qos policy control-plane slot slot-number
In IRF mode:
display qos policy control-plane chassis chassis-number slot slot-number
Views
Any view
Predefined user roles
network-admin
network-operator
mdc-admin
mdc-operator
Parameters
slot slot-number: Specifies a card by its slot number. (In standalone mode.)
chassis chassis-number slot slot-number: Specifies a card on an IRF member device. The chassis-number argument represents the ID of the IRF member device. The slot-number argument represents the slot number of the card. (In IRF mode.)
Examples
# Display the QoS policy applied to the control plane of the card in slot 3.
<Sysname> display qos policy control-plane slot 3
Control plane slot 3
Direction: Inbound
Policy: 1
Classifier: 2
Operator: AND
Rule(s) :
If-match acl 2000
Behavior: 2
Committed Access Rate:
CIR 128 (kbps), CBS 8000 (Bytes), EBS 0 (Bytes)
Red Action : discard
Green :12928(Bytes)
Yellow:7936(Bytes)
Red :43904(Bytes)
Table 7 Command output
|
Field |
Description |
|
Direction |
Direction to which the QoS policy is applied. |
|
Red Action |
Action taken on red packets. |
|
Green packets |
Statistics about green packets. |
|
Yellow packets |
Statistics about yellow packets. |
|
Red packets |
Statistics about red packets. |
display qos policy control-plane management
Use display qos policy control-plane management to display the QoS policy applied to the management interface control plane.
Syntax
display qos policy control-plane management
Views
Any view
Predefined user roles
network-admin
network-operator
mdc-admin
mdc-operator
Examples
# Display the QoS policy applied to the management interface control plane.
<Sysname> display qos policy control-plane management
Control plane management
Direction: Inbound
Policy: test
Classifier: test
Operator: AND
Rule(s) :
If-match control-plane protocol arp
Behavior: test
Committed Access Rate:
CIR 8 (kbps), CBS 1553 (Bytes), EBS 0 (Bytes)
Red action : discard
Green packets : 0 (Packets) 0 (Bytes)
Red packets : 0 (Packets) 0 (Bytes)
Table 8 Command output
|
Field |
Description |
|
Direction |
Direction to which the QoS policy is applied. |
|
Red Action |
Action taken on red packets. |
|
Green packets |
Statistics about green packets. |
|
Yellow packets |
Statistics about yellow packets. |
|
Red packets |
Statistics about red packets. |
display qos policy control-plane management pre-defined
Use display qos policy control-plane management pre-defined to display the predefined QoS policy applied to the management interface control plane.
Syntax
display qos policy control-plane management pre-defined
Views
Any view
Predefined user roles
network-admin
network-operator
mdc-admin
mdc-operator
Examples
# Display the predefined QoS policy applied to the management interface control plane.
<Sysname> display qos policy control-plane management pre-defined
Pre-defined policy information
Protocol Priority Bandwidth (kbps) Group
Default N/A 100000 N/A
ARP N/A 100000 normal
BGP N/A 100000 critical
BGPv6 N/A 100000 critical
HTTP N/A 100000 management
HTTPS N/A 100000 management
ICMP N/A 100000 monitor
ICMPv6 N/A 100000 monitor
OSPF Multicast N/A 100000 critical
OSPF Unicast N/A 100000 critical
OSPFv3 Multicast N/A 100000 critical
OSPFv3 Unicast N/A 100000 critical
PIM Multicast N/A 100000 critical
PIM Unicast N/A 100000 critical
PIMv6 Multicast N/A 100000 critical
PIMv6 Unicast N/A 100000 critical
RADIUS N/A 100000 management
RIP N/A 100000 critical
RIPng N/A 100000 critical
SNMP N/A 100000 management
SSH N/A 100000 management
TELNET N/A 100000 management
FTP N/A 100000 management
TFTP N/A 100000 management
Table 9 Command output
|
Field |
Description |
|
Pre-defined control plane policy management |
Predefined QoS policy applied to the management interface control plane. |
|
Protocol |
System-defined protocol packet type. |
|
Group |
Protocol group to which the protocol belongs. This field is not supported in the current software version and is reserved for future support. |
display qos policy control-plane pre-defined
Use display qos policy control-plane pre-defined to display predefined QoS policies applied to control planes 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
mdc-admin
mdc-operator
Parameters
slot slot-number: Specifies a card by its slot number. If you do not specify a card, this command displays the predefined QoS policy applied to the control plane of each in-position card. (In standalone mode.)
chassis chassis-number slot slot-number: Specifies a card on an IRF member device. The chassis-number argument represents the 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 predefined QoS policy applied to the control plane of each in-position card on each member device of the IRF fabric. (In IRF mode.)
Examples
# (In standalone mode.) Display the predefined QoS policy applied to the control plane of card 3.
<Sysname> display qos policy control-plane pre-defined slot 3
Pre-defined control plane policy slot 3
Protocol Priority Bandwidth (pps) Group
ARP 2 1000 normal
BGP 5 400 critical
DHCP 0 600 normal
DHCP Snooping 0 600 redirect
DHCPv6 0 600 normal
DLDP 7 100 critical
MVRP 7 100 critical
ICMP 6 500 monitor
ICMPv6 6 500 monitor
IGMP 3 2048 important
IS-IS 5 1500 critical
LACP 7 100 critical
LDP 4 600 critical
LLDP 7 200 important
MLD 3 500 important
NTP 4 200 important
OAM 7 100 critical
OSPF Multicast 5 1500 critical
OSPF Unicast 5 1000 critical
PIM Multicast 4 2500 critical
PIM Unicast 4 2000 critical
PORTAL 1 200 management
RIP 5 300 critical
RIPng 5 300 critical
SNMP 1 200 management
STP 7 200 critical
TACACS 4 300 management
UDP Helper 3 500 redirect
VRRP 4 2500 important
TELNET 4 700 management
# (In IRF mode.) Display the predefined QoS policy applied to the control plane of card 3 in IRF member device 1.
<Sysname> display qos policy control-plane pre-defined chassis 1 slot 3
Pre-defined control plane policy chassis 1 slot 3
Protocol Priority Bandwidth (pps) Group
ARP 2 1000 normal
BGP 5 400 critical
DHCP 0 600 normal
DHCP Snooping 0 600 redirect
DHCPv6 0 600 normal
DLDP 7 100 critical
MVRP 7 100 critical
ICMP 6 500 monitor
ICMPv6 6 500 monitor
IGMP 3 2048 important
IS-IS 5 1500 critical
LACP 7 100 critical
LDP 4 600 critical
LLDP 7 200 important
MLD 3 500 important
NTP 4 200 important
OAM 7 100 critical
OSPF Multicast 5 1500 critical
OSPF Unicast 5 1000 critical
PIM Multicast 4 2500 critical
PIM Unicast 4 2000 critical
PORTAL 1 200 management
RIP 5 300 critical
RIPng 5 300 critical
SNMP 1 200 management
STP 7 200 critical
TACACS 4 300 management
UDP Helper 3 500 redirect
VRRP 4 2500 important
TELNET 4 700 management
Table 10 Command output
|
Field |
Description |
|
Group |
Protocol group to which the protocol belongs. This field is not supported in the current software version and is reserved for future support. |
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
mdc-admin
mdc-operator
Parameters
inbound: Specifies the QoS policy applied globally in the inbound direction.
outbound: Specifies the QoS policy applied globally in the outbound direction.
slot slot-number: Specifies a card by its slot number. If you do not specify a card, this command displays globally applied QoS policies on the MPU. (In standalone mode.)
chassis chassis-number slot slot-number: Specifies a card on an IRF member device. The chassis-number argument represents the ID of the IRF member device, and the slot-number argument represents the slot number of the card. If you do not specify this option, the command displays globally applied QoS policies on 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 the QoS policy applied globally in the inbound direction.
<Sysname> display qos policy global inbound
Direction: Inbound
Policy: qpolicy
Classifier: tc1
Operator: AND
Rule(s) : If-match acl 2000
Behavior: tb1
Marking:
Remark dot1p 5
Committed Access Rate:
CIR 1000 (kbps), CBS 100000 (Bytes), EBS 0 (Bytes)
Red action: discard
Table 11 Command output
|
Field |
Description |
|
Direction |
Direction (inbound or outbound ) to which the QoS policy is applied. |
For the description of other fields, see Table 1 and Table 4.
display qos policy interface
Use display qos policy interface to display QoS policies applied to interfaces.
Syntax
display qos policy interface [ interface-type interface-number ] [ inbound | outbound ]
Views
Any view
Predefined user roles
network-admin
network-operator
mdc-admin
mdc-operator
Parameters
interface-type interface-number: Specifies an interface by its type and number.
inbound: Specifies QoS policies applied in the inbound direction.
outbound: Specifies QoS policies applied in the outbound direction.
Usage guidelines
If you do not specify a direction, this command displays QoS policies applied in the inbound direction and QoS policies applied in the outbound direction.
Examples
# Display the QoS policy applied to the incoming traffic of GigabitEthernet 3/0/1.
<Sysname> display qos policy interface gigabitethernet 3/0/1 inbound
Interface: GigabitEthernet3/0/1
Direction: Inbound
Policy: qpolicy
Classifier: tc1
Operator: AND
Rule(s) : If-match acl 2000
Behavior: tb1
Marking:
Remark dot1p 5
Committed Access Rate:
CIR 1000 (kbps), CBS 100000 (Bytes), EBS 0 (Bytes)
Red action: discard
Table 12 Command output
|
Field |
Description |
|
Direction |
Direction to which the QoS policy is applied on the interface. |
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
mdc-admin
mdc-operator
Parameters
name policy-name: Specifies a QoS policy by its name, a case-sensitive string of 1 to 31 characters.
vlan vlan-id: Specifies a VLAN by its ID.
inbound: Specifies QoS policies applied in the inbound direction.
outbound: Specifies QoS policies applied in the outbound direction.
slot slot-number: Specifies a card by its slot number. If you do not specify a card, this command displays QoS policies applied to VLANs 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 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 on the global active MPU. (In IRF mode.)
Usage guidelines
If you do not specify a direction, this command displays QoS policies applied in the inbound direction and QoS policies applied in the outbound direction.
Examples
# Display QoS policies applied to VLAN 2.
<Sysname> display qos vlan-policy vlan 2
Vlan 2
Direction: Inbound
Policy: qpolicy
Classifier: tc1
Operator: AND
Rule(s) : If-match acl 2000
Behavior: tb1
Marking:
Remark dot1p 5
Committed Access Rate:
CIR 1000 (kbps), CBS 100000 (Bytes), EBS 0 (Bytes)
Red action: discard
Table 13 Command output
|
Field |
Description |
|
Direction |
Direction to which the QoS policy is applied for the VLAN. |
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, a control plane, or the management interface control plane.
Use undo qos apply policy to remove the applied QoS policy.
Syntax
qos apply policy policy-name { inbound | outbound }
undo qos apply policy policy-name { inbound | outbound }
Default
No QoS policy is applied to an interface, a control plane, or the management interface control plane.
Views
Interface view, control plane view, control plane management view
Predefined user roles
network-admin
mdc-admin
Parameters
policy-name: Specifies a QoS policy by its name, a case-sensitive string of 1 to 31 characters.
inbound: Applies the QoS policy to incoming traffic.
outbound: Applies the QoS policy to outgoing traffic.
Usage guidelines
QoS policies cannot be applied to VLAN or aggregate interfaces.
In a QoS policy, do not configure the car cir or filter deny command in the associated traffic behavior of a class when the following conditions exist:
· In the class, an Ethernet frame header ACL with a rule that permits all packets is used as the match criterion.
· The QoS policy is to be applied to the control plane of the card where an IRF physical port resides.
Otherwise, an IRF split might occur.
Examples
# Apply the QoS policy USER1 to the incoming traffic of GigabitEthernet 3/0/1.
<Sysname> system-view
[Sysname] interface gigabitethernet 3/0/1
[Sysname-GigabitEthernet3/0/1] qos apply policy USER1 outbound
# Apply the 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 the QoS policy bbb to the incoming traffic of the management interface control plane.
<Sysname> system-view
[Sysname] control-plane management
[Sysname-cp-management] qos apply policy bbb inbound
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 }
undo qos apply policy policy-name global { inbound | outbound }
Default
No QoS policy is applied globally.
Views
System view
Predefined user roles
network-admin
mdc-admin
Parameters
policy-name: Specifies a QoS policy by its name, a case-sensitive string of 1 to 31 characters.
inbound: Applies the QoS policy in the inbound direction.
outbound: Applies the QoS policy in the outbound direction.
Usage guidelines
A QoS policy globally applied takes effect on all incoming or outgoing traffic, depending on the direction in which the QoS policy is applied.
If the hardware resources of an interface card are insufficient, applying a QoS policy globally might fail on the interface card. In this case, the system does not automatically roll back the QoS policy configuration already applied to the MPU or other interface cards. To ensure consistency, you must manually remove the QoS policy configuration applied to them. Do the same thing if a global QoS policy fails to update on an interface card after being dynamically modified.
Examples
# Apply the QoS policy user1 globally in the inbound direction.
<Sysname> system-view
[Sysname] qos apply policy user1 global inbound
qos policy
Use qos policy to create a QoS policy and enter QoS policy view.
Use undo qos policy to delete a QoS policy.
Syntax
qos policy policy-name
undo qos policy policy-name
Default
No QoS policy exists.
Views
System view
Predefined user roles
network-admin
mdc-admin
Parameters
policy-name: Specifies 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 it 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
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
mdc-admin
Usage guidelines
VLAN QoS policies will be applied globally to all interface cards. If the hardware resources of an interface card are insufficient, applying a QoS policy to VLANs might fail on the interface card. In this case, the system does not automatically roll back the QoS policy configuration already applied to the MPU or other interface cards. To ensure consistency, you must manually remove the QoS policy configuration applied to them. Do the same thing if a VLAN QoS policy fails to update on an interface card after being dynamically modified.
Parameters
policy-name: Specifies a QoS policy by its name, a case-sensitive string of 1 to 31 characters.
vlan-id-list: Specifies a space-separated list of up to eight VLAN IDs or a VLAN ID range in the form of vlan-id1 to vlan-id2. The value for vlan-id2 must be greater than or equal to the value for vlan-id1. The value range for the vlan-id argument is 1 to 4094.
inbound: Applies the QoS policy to incoming packets.
outbound: Applies the QoS policy to outgoing packets.
Examples
# Apply the 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 statistics for the QoS policy applied to a control plane.
Syntax
In standalone mode:
reset qos policy control-plane slot slot-number
In IRF mode:
reset qos policy control-plane chassis chassis-number slot slot-number
Views
User view
Predefined user roles
network-admin
mdc-admin
Parameters
slot slot-number: Specifies a card by its slot number. (In standalone mode.)
chassis chassis-number slot slot-number: Specifies a card on an IRF member device. The chassis-number argument represents the ID of the IRF member device. The slot-number argument represents the slot number of the card. (In IRF mode.)
Examples
# (In standalone mode.) Clear statistics for the QoS policy applied to the control plane of card 3.
<Sysname> reset qos policy control-plane slot 3
# (In IRF mode.) Clear statistics for the QoS policy applied to the control plane of card 3 on IRF member device 1.
<Sysname> reset qos policy control-plane chassis 1 slot 3
reset qos policy control-plane management
Use reset qos policy control-plane management to clear statistics for the QoS policy applied to the management interface control plane.
Syntax
reset qos policy control-plane management
Views
User view
Predefined user roles
network-admin
mdc-admin
Examples
# Clear statistics for the QoS policy applied to the management interface control plane.
<Sysname> reset qos policy control-plane management
reset qos policy global
Use reset qos policy global to clear statistics for QoS policies applied globally.
Syntax
reset qos policy global [ inbound | outbound ]
Views
User view
Predefined user roles
network-admin
mdc-admin
Parameters
inbound: Specifies the QoS policy applied in the inbound direction.
outbound: Specifies the QoS policy applied in the outbound direction.
Usage guidelines
If you do not specify a direction, this command clears statistics for both QoS policies applied globally.
Examples
# Clear statistics for the QoS policy applied globally in the inbound direction.
<Sysname> reset qos policy global inbound
reset qos vlan-policy
Use reset qos vlan-policy to clear statistics for QoS policies applied to VLANs.
Syntax
reset qos vlan-policy [ vlan vlan-id ] [ inbound | outbound ]
Views
User view
Predefined user roles
network-admin
mdc-admin
Parameters
vlan vlan-id: Specifies a VLAN by its ID in the range of 1 to 4094.
inbound: Specifies QoS policies applied in the inbound direction.
outbound: Specifies QoS policies applied in the outbound direction.
Usage guidelines
If you do not specify a direction, this command clears statistics for QoS policies applied in the inbound direction and QoS policies applied in the outbound direction.
Examples
# Clear statistics for QoS policies applied to VLAN 2.
<Sysname> reset qos vlan-policy vlan 2
Priority map commands
display qos map-table
Use display qos map-table to display the configuration of priority maps.
Syntax
display 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-lp ] ]
Views
Any view
Predefined user roles
network-admin
network-operator
mdc-admin
mdc-operator
Parameters
inbound: Specifies the priority maps for incoming packets.
The switch provides the following types of 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-lp |
EXP-local priority map. |
Usage guidelines
If you do not specify a priority map, this command displays the configuration of all priority maps.
If you do not specify any parameters, this command displays all priority maps (including colored priority maps).
Examples
# Display the configuration of the inbound 802.1p-local priority map.
<Sysname> display qos map-table inbound dot1p-lp
MAP-TABLE NAME: dot1p-lp TYPE: pre-define DIRECTION: inbound
IMPORT : EXPORT
0 : 2
1 : 0
2 : 1
3 : 3
4 : 4
5 : 5
6 : 6
7 : 7
Table 15 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 colored priority maps.
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 ] }
network-admin
network-operator
mdc-admin
mdc-operator
green: Specifies green packets.
yellow: Specifies yellow packets.
red: Specifies red packets.
inbound: Specifies the priority maps for incoming packets.
outbound: Specifies the priority maps for outgoing packets.
The switch provides the following types of colored priority maps.
Table 16 Colored priority maps
|
Colored 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. |
Packets processed by traffic policing are colored green, yellow, or red. To perform priority mapping for packets in different colors, the switch 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 priority map, this command displays the configuration of all colored priority maps.
· If you do not specify a color, this command displays the configuration of all colored priority maps.
# 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
|
Priority map name. |
|
|
Priority map type. |
|
|
Priority map color. |
|
|
Direction of the priority map. |
|
|
Input values of the priority map. |
|
|
Output values of the priority map. |
import
Use import to configure mappings for a priority map.
Use undo import to restore the specified or all mappings to the default for a priority map.
Syntax
import import-value-list export export-value
undo import { import-value-list | all }
Default
The default priority maps are used. For more information, see ACL and QoS Configuration Guide.
Views
Priority map view
Predefined user roles
network-admin
mdc-admin
Parameters
import-value-list: Specifies a list of input values.
export-value: Specifies the output value.
all: Restores all mappings in the priority map to the default.
Examples
# In the inbound direction, 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 inbound dot1p-dp
[Sysname-maptbl-in-dot1p-dp] import 4 5 export 1
Related commands
· display qos map-table
· display qos map-table color
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-lp } }
Views
System view
Predefined user roles
network-admin
mdc-admin
Parameters
inbound: Specifies the priority map for incoming packets.
For the description of other keywords, see Table 14.
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
mdc-admin
Parameters
green: Specifies green packets.
yellow: Specifies yellow packets.
red: Specifies red packets.
inbound: Specifies the priority maps for incoming packets.
outbound: Specifies the priority maps for outgoing packets.
For the description of other keywords, see Table 16.
Usage guidelines
Packets processed by traffic policing are colored green, yellow, or red. To perform priority mapping for packets in different colors, the switch 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.
Examples
# 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
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 | dp | dscp | exp | lp } priority-value
undo qos priority { dot1p | dp | dscp | exp | lp }
Default
The default is 2 for local precedence and 0 for drop priority, and the other priorities do not have defaults.
Views
Interface view
Predefined user roles
network-admin
mdc-admin
Parameters
priority-value: Specifies a port priority value. 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 |
N/A |
|
DSCP |
0 to 63 |
N/A |
|
EXP |
0 to 7 |
N/A |
|
Drop priority |
0 to 2 |
A packet with a higher drop priority value is dropped more preferentially. |
|
Local precedence |
0 to 7 |
A packet with a higher local precedence value is assigned to a queue with a higher priority, and has a higher scheduling priority. |
Usage guidelines
You can assign one value to each type of port priority on an interface. For each type of port priority, the most recent configuration takes effect.
Examples
# Set the DSCP port priority of interface GigabitEthernet 3/0/1 to 20.
<Sysname> system-view
[Sysname] interface gigabitethernet 3/0/1
[Sysname-GigabitEthernet3/0/1] qos priority dscp 20
Related commands
display qos trust interface
Priority trust mode commands
display qos trust interface
Use display qos trust interface to display priority trust mode and port priority information on an interface.
Syntax
display qos trust interface [ interface-type interface-number ]
Views
Any view
Predefined user roles
network-admin
network-operator
mdc-admin
mdc-operator
Parameters
interface-type interface-number: Specifies an interface by its type and number. If you do not specify an interface, this command displays priority trust mode and port priority information of all interfaces.
Examples
# Display the priority trust mode and port priority information of GigabitEthernet 3/0/1.
<Sysname> display qos trust interface GigabitEthernet 3/0/1
Interface: GigabitEthernet3/0/1
Port priority information
Port dot1p priority: -
Port dp priority: 0
Port dscp priority: -
Port exp priority: -
Port lp priority: 2
Port priority trust type: none, Override: disable
Table 19 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 dp priority |
Drop priority of the port. |
|
Port exp priority |
EXP value of the port. |
|
Port lp priority |
Local precedence of the port. |
|
Port priority trust type |
Priority trust mode: auto, dot11e, dot1p, dscp, exp, or none. If the trust mode is none, the port priority is used for priority mapping. |
|
Override |
Whether the trusted priority in received packets is used directly for priority mapping: disable—Yes. enable—No. |
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 | exp } [ override ]
undo qos trust
Default
The port priority is trusted for priority mapping.
Views
Interface view
Predefined user roles
network-admin
mdc-admin
Parameters
auto: Uses the priority in incoming packets for priority mapping:
· 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.
dot1p: Uses the 802.1p priority in incoming packets for priority mapping.
dscp: Uses the DSCP value in incoming packets for priority mapping.
exp: Uses the EXP value in incoming MPLS packets for priority mapping.
override: Maps the trusted priority, and then uses the mapped value for other priority mappings. Without this keyword, the trusted priority carried in the packet is directly used for priority mapping. This keyword is incompatible with the exp keyword.
Examples
# Set the trusted packet priority type to 802.1p priority on GigabitEthernet 3/0/1.
<Sysname> system-view
[Sysname] interface gigabitethernet 3/0/1
[Sysname-GigabitEthernet3/0/1] qos trust dot1p
Related commands
display qos gts interface
Use display qos gts interface to display generic traffic shaping (GTS) configuration and statistics on interfaces.
Syntax
display qos gts interface [ interface-type interface-number ]
Views
Any view
Predefined user roles
network-admin
network-operator
mdc-admin
mdc-operator
Parameters
interface-type interface-number: Specifies an interface by its type and number. If you do not specify an interface, this command displays the GTS configuration and statistics on all interfaces.
Examples
# Display the GTS configuration and statistics on all interfaces.
<Sysname> display qos gts interface
Interface : GigabitEthernet3/0/1
Rule: If-match any
CIR 1000 (kbps), CBS 100000 (Bytes)
Table 20 Command output
|
Field |
Description |
|
Interface |
Interface type and interface number. |
|
Rule |
Match criterion. |
|
CIR |
CIR in kbps. |
|
CBS |
CBS in bytes, which specifies the depth of the token bucket for holding bursty traffic. |
qos gts
Use qos gts any to set GTS parameters for all the traffic on an interface.
Use qos gts queue to set GTS parameters for the packets in a queue on an interface.
Use undo qos gts to delete the GTS configuration for a traffic class or all the traffic on an interface.
Syntax
qos gts { any | queue queue-id } cir committed-information-rate [ cbs committed-burst-size ]
undo qos gts { any | queue queue-id }
Default
No GTS parameters are configured on an interface.
Views
Interface view
Predefined user roles
network-admin
mdc-admin
Parameters
any: Shapes all packets.
queue queue-id: Specifies a queue by its ID in the range of 0 to 7.
cir committed-information-rate: Specifies the CIR in kbps. The value range for committed-information-rate varies by interface type as follows:
· 1000 to 1000000 for GE interfaces.
· 2500 to 10000000 for 10-GE interfaces.
· 1000 to 40000000 for 40-GE interfaces.
· 1000 to 100000000 for 100-GE interfaces.
cbs committed-burst-size: Specifies the CBS in the range of 16384 to 16777215 bytes. By default, the CBS is the amount of traffic transmitted at the rate of CIR over 500 milliseconds.
Usage guidelines
H3C recommends that you set the committed-burst-size argument, if necessary, to be greater than 6.25 times the committed-information-rate argument to accommodate traffic bursts.
Examples
# Shape the packets matching ACL 2001 on GigabitEthernet 3/0/1. The GTS parameters are as follows: CIR is 1200 kbps, and CBS is 50000 bytes.
<Sysname> system-view
[Sysname] interface gigabitethernet 3/0/1
[Sysname-GigabitEthernet3/0/1] qos gts any cir 1200 cbs 50000
WFQ commands
display qos queue wfq interface
Use display qos queue wfq interface to display the WFQ configuration of interfaces.
Syntax
display qos queue wfq interface [ interface-type interface-number ]
Views
Any view
Predefined user roles
network-admin
network-operator
mdc-admin
mdc-operator
Parameters
interface-type interface-number: Specifies an interface by its type and number. If you do not specify an interface, this command displays the WFQ configuration of all interfaces.
Examples
# Display the WFQ configuration of GigabitEthernet 2/0/1.
<Sysname> display qos queue wfq interface gigabitethernet 2/0/1
Interface: GigabitEthernet2/0/1
Output queue: Hardware Weighted Fair Queuing
Queue ID Weight Min-Bandwidth
----------------------------------------------------------------
be 2 40
af1 1 40
af2 1 40
af3 1 40
af4 1 40
ef 1 40
cs6 1 40
cs7 1 40
Table 21 Command output
|
Field |
Description |
|
Interface |
Interface type and interface number. |
|
Output queue |
Type of the current output queue. |
|
Min-Bandwidth |
Minimum guaranteed bandwidth in kbps. |
qos bandwidth queue
Use qos bandwidth queue to set the minimum guaranteed bandwidth for a queue on an interface.
Use undo qos bandwidth queue to restore the default.
Syntax
qos bandwidth queue queue-id min bandwidth-value
undo qos bandwidth queue queue-id
Default
The minimum guaranteed bandwidth of a WFQ queue is 40 kbps.
Views
Interface view
Predefined user roles
network-admin
mdc-admin
Parameters
queue-id: Specifies a queue by a number or keyword. Table 22 shows the number-keyword mapping.
Table 22 Number-keyword mapping
|
Keyword |
Number |
|
af1 |
1 |
|
af2 |
2 |
|
af3 |
3 |
|
af4 |
4 |
|
be |
0 |
|
cs6 |
6 |
|
cs7 |
7 |
|
ef |
5 |
min bandwidth-value: Sets the minimum guaranteed bandwidth in kbps for a queue when the interface is congested. The value range for the bandwidth-value argument varies by interface type as follows:
· 40 to 1000000 for GE interfaces.
· 40 to 10000000 for 10-GE interfaces.
· 40 to 40000000 for 40-GE interfaces.
· 40 to 100000000 for 100-GE interfaces.
Usage guidelines
You must use the qos wfq command to enable WFQ before you can configure this command on an interface.
Make sure the sum of the minimum guaranteed bandwidth configured for multiple queues on an interface is no greater than either of the following:
· The CIR configured on the interface by using the qos gts any cir committed-information-rate command.
· The interface bandwidth.
Examples
# Set the minimum guaranteed bandwidth to 100 kbps for queue 0 on GigabitEthernet 2/0/1.
<Sysname> system-view
[Sysname] interface GigabitEthernet 2/0/1
[Sysname-GigabitEthernet2/0/1] qos wfq weight
[Sysname-GigabitEthernet2/0/1] qos bandwidth queue 1 min 100
Related commands
qos wfq
qos wfq
Use qos wfq to enable weight-based WFQ.
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
mdc-admin
Parameters
weight: Allocates bandwidth to queues based on their weights.
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.
After WFQ is enabled on an interface, all queues on the interface have a default scheduling weight of 1 and a default minimum guaranteed bandwidth of 40 kbps.
Examples
# Enable weight-based WFQ on GigabitEthernet 3/0/1.
<Sysname> system-view
[Sysname] interface gigabitethernet 3/0/1
[Sysname-GigabitEthernet3/0/1] qos wfq weight
Related commands
display qos queue wfq interface
qos wfq weight
Use qos wfq weight to set a scheduling weight for a WFQ queue.
Use undo qos wfq to restore the default.
Syntax
qos wfq queue-id weight schedule-value
undo qos wfq queue-id
Default
A WFQ queue has a scheduling weight of 1.
Views
Interface view
Predefined user roles
network-admin
mdc-admin
Parameters
queue-id: Specifies a queue by a number or keyword. For the number-keyword mapping, see Table 22.
weight: Allocates bandwidth to queues based on their weights.
schedule-value: Specifies a scheduling weight in the range of 1 to 63.
Usage guidelines
You must use the qos wfq command to enable WFQ before you configure this command.
Examples
# Configure scheduling weights 20 and 30 for queues 3 and 4 on GigabitEthernet 2/0/1, respectively.
<Sysname> system-view
[Sysname] interface gigabitethernet 2/0/1
[Sysname-GigabitEthernet2/0/1] qos wfq
[Sysname-GigabitEthernet2/0/1] qos wfq 3 weight 20
[Sysname-GigabitEthernet2/0/1] qos wfq 4 weight 30
Related commands
· display qos queue wfq interface
· qos bandwidth queue
· qos wfq
Queue scheduling profile commands
display qos qmprofile configuration
Use display qos qmprofile configuration to display the configuration of queue scheduling profiles.
Syntax
In standalone mode:
display qos qmprofile configuration [ profile-name ] [ slot slot-number ]
In IRF mode:
display qos qmprofile configuration [ profile-name ] [ chassis chassis-number slot slot-number ]
Views
Any view
Predefined user roles
network-admin
network-operator
mdc-admin
mdc-operator
Parameters
profile-name: Specifies a queue scheduling profile by its name, a string of 1 to 31 case-sensitive 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 configuration of queue scheduling profiles 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 ID of the IRF member device. The slot-number argument represents the slot number of the card. If you do not specify this option, the command displays the configuration of queue scheduling profiles on 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-unit Schedule-value Bandwidth
---------------------------------------------------------------------------
be SP N/A N/A N/A N/A
af1 WRR 1 byte-count 1 N/A
af2 SP N/A N/A N/A N/A
af3 SP N/A N/A N/A N/A
af4 SP N/A N/A N/A N/A
ef SP N/A N/A N/A N/A
cs6 SP N/A N/A N/A N/A
cs7 SP N/A N/A N/A N/A
|
Field |
Description |
|
Queue management profile |
Queue scheduling profile name. |
|
Type |
Queue scheduling type: SP or WRR. |
|
Group |
Priority group to which the queue belongs. N/A indicates this field is insignificant for the queue. |
|
Scheduling unit: byte-count. N/A indicates that this field is ignored. |
|
|
N/A indicates that this field is ignored. |
|
|
Bandwidth |
Minimum guaranteed bandwidth. N/A indicates that this field is ignored. |
display qos qmprofile interface
Use display qos qmprofile interface to display the queue scheduling profile applied to an interface.
Syntax
display qos qmprofile interface [ interface-type interface-number ]
Views
Any view
Predefined user roles
network-admin
network-operator
mdc-admin
mdc-operator
Parameters
interface-type interface-number: Specifies an interface by its type and number. If you do not specify an interface, this command displays the queue scheduling profiles applied to all interfaces.
Examples
# Display the queue scheduling profile applied to GigabitEthernet 3/0/1.
<Sysname> display qos qmprofile interface gigabitethernet 3/0/1
Interface: GigabitEthernet3/0/1
Queue management profile: myprofile
Table 24 Command output
|
Field |
Description |
|
Interface |
Interface name. |
|
Queue management profile |
Name of the queue scheduling profile applied to the interface. |
qos apply qmprofile
Use qos apply qmprofile to apply a queue scheduling profile to an interface.
Use undo qos apply qmprofile to restore the default.
Syntax
qos apply qmprofile profile-name
undo qos apply qmprofile
Default
No queue scheduling profile is applied to an interface.
Views
Interface view
Predefined user roles
network-admin
mdc-admin
Parameters
profile-name: Specifies a queue scheduling profile by its name, a case-sensitive string of 1 to 31 characters.
Usage guidelines
You can apply only one queue scheduling profile to an interface.
Examples
# Apply the queue scheduling profile myprofile to GigabitEthernet 3/0/1.
<Sysname> system-view
[Sysname] interface gigabitethernet 3/0/1
[Sysname-GigabitEthernet3/0/1] qos apply qmprofile myprofile
Related commands
display qos qmprofile interface
qos qmprofile
Use qos qmprofile to create a queue scheduling profile and enter queue scheduling profile view.
Use undo qos qmprofile to delete a queue scheduling profile.
Syntax
qos qmprofile profile-name
undo qos qmprofile profile-name
Default
No queue scheduling profile exists.
Views
System view
Predefined user roles
network-admin
mdc-admin
Parameters
profile-name: Specifies the name of the queue scheduling profile, a case-sensitive string of 1 to 31 characters.
Usage guidelines
To delete a queue scheduling profile already applied to an interface, first remove it from the interface.
Examples
# Create a queue scheduling profile myprofile and enter queue scheduling profile view.
<Sysname> system-view
[Sysname] qos qmprofile myprofile
[Sysname-qmprofile-myprofile]
Related commands
· display qos qmprofile interface
· queue
queue
Use queue to configure queue scheduling parameters.
Use undo queue to restore the default.
Syntax
queue queue-id { sp | wrr group group-id byte-count schedule-value }
undo queue queue-id
Default
A newly created queue scheduling profile uses SP queuing for all queues.
Views
Queue scheduling profile view
Predefined user roles
network-admin
mdc-admin
Parameters
queue-id: Specifies a queue by a number or keyword. For the number-keyword mapping, see Table 22.
sp: Enables SP for the queue.
wrr: Enables WRR for the queue.
group-id: Specifies a WRR group by its ID. The value range is 1 and 2.
byte-count: Allocates bandwidth based on the number of bytes.
schedule-value: Specifies a scheduling weight in the range of 1 to 250.
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 as follows:
· Configure queue 1 to use WRR.
· Assign queue 1 to WRR group 1.
· Set the scheduling weight to 10 for queue 1.
<Sysname> system-view
[Sysname] qos qmprofile myprofile
[Sysname-qmprofile-myprofile] queue 1 wrr group 1 byte-count 100
Related commands
· display qos qmprofile interface
· qos qmprofile
Low-latency queuing command
queue low-latency enable
Use queue low-latency enable to enable low-latency queuing.
Use undo queue low-latency enable to disable low-latency queuing.
Syntax
queue low-latency enable
undo queue low-latency enable
Default
Low-latency queuing is disabled.
Views
System view
Predefined user roles
network-admin
mdc-admin
Usage guidelines
In a scenario requiring a low forwarding delay, you can enable low-latency queuing, so that the switch can reduce the forwarding delay.
This command is supported only by the default MDC. For more information about MDCs, see Virtual Technologies Configuration Guide.
Examples
# Enable low-latency queuing.
<Sysname> system-view
[Sysname] queue low-latency enable
car name
Use car name to use a global CAR action in a traffic behavior.
Use undo car to remove a global CAR action from a traffic behavior.
Syntax
car name car-name
undo car
Default
No global CAR action is used in a traffic behavior.
Views
Traffic behavior view
Predefined user roles
network-admin
mdc-admin
Parameters
car-name: Specifies the name of an aggregate CAR action, a case-sensitive string of 1 to 31 characters. This argument must start with a letter.
Usage guidelines
The used global CAR action must already exists.
Examples
# Use the aggregate CAR action aggcar-1 in the traffic behavior be1.
<Sysname> system-view
[Sysname] traffic behavior be1
[Sysname-behavior-be1] car name aggcar-1
· display qos car name
· display traffic behavior user-defined
display qos car name
Use display qos car name to display the configuration of a global CAR action.
Syntax
display qos car name [ car-name ]
Views
Any view
Predefined user roles
network-admin
network-operator
mdc-admin
mdc-operator
Parameters
car-name: Specifies a global CAR action by its name, a case-sensitive string of 1 to 31 characters. This argument must start with a letter. If you do not specify a CAR action, this command displays the configuration of all global CAR actions.
Examples
# Display the configuration of all global CAR actions.
<Sysname> display qos car name
Name: agg1
Mode: aggregative
CIR 1000 (kbps), CBS 10000 (Bytes), PIR 10000 (kbps), EBS 625000 (Bytes)
Red action : discard
Table 25 Command output
|
Field |
Description |
|
Name |
Name of the global CAR action. |
|
Mode |
Type of the CAR action: aggregative. |
|
CIR CBS PIR EBS |
Parameters for the CAR action. |
|
Red action |
Action to take on red packets: · discard—Drops the packets. · pass—Permits the packets to pass through. |
qos car
Use qos car 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 ] ] [ red action ]
qos car car-name aggregative cir committed-information-rate [ cbs committed-burst-size ] pir peak-information-rate [ ebs excess-burst-size ] [ red action ]
undo qos car car-name
Default
No aggregate CAR action is configured.
Views
System view
Predefined user roles
network-admin
mdc-admin
Parameters
car-name: Specifies the name of the global CAR action. This argument must start with a letter, and is a case-sensitive string of 1 to 31 characters.
aggregative: Specifies the global CAR action as an aggregate CAR action. Only this mode is supported.
cir committed-information-rate: Specifies the CIR in the range of 1 to 100000000 kbps.
cbs committed-burst-size: Specifies the CBS in bytes, the size of bursty traffic when the actual average rate is no greater than CIR. The value range for the committed-burst-size argument is 1553 to 2147450880. The specified CBS must be larger than the maximum packet length. By default, the CBS is the amount of traffic transmitted at the rate of CIR over 500 milliseconds. If the traffic transmitted at the rate of CIR over 500 milliseconds is smaller than 1553, the default CBS is 1553.
ebs excess-burst-size: Specifies the EBS in the range of 0 to 2147450880 bytes.
pir peak-information-rate: Specifies the PIR in the range of 1 to 100000000 kbps.
red action: Specifies the action to take on packets that conform to neither CIR nor PIR. The default setting is discard.
action: Specifies the action to take on packets:
· discard: Drops the packet.
· pass: Permits the packet to pass through.
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.
An aggregate CAR action takes effect only after it is used in a QoS policy.
H3C recommends that you set the committed-burst-size argument, if necessary, to be greater than 6.25 times the committed-information-rate argument to accommodate traffic bursts.
Examples
# Configure the aggregate CAR action aggcar-1, where CIR is 200, CBS is 2000, and red packets are dropped.
<Sysname> system-view
[Sysname] qos car aggcar-1 aggregative cir 200 cbs 2000 red discard
display qos car name
reset qos car name
Use reset qos car name to clear statistics for global CAR actions.
Syntax
reset qos car name [ car-name ]
Views
User view
Predefined user roles
network-admin
mdc-admin
Parameters
car-name: Specifies a global CAR action by its name, a case-sensitive string of 1 to 31 characters. This argument must start with a letter. If you do not specify a global CAR action, this command clears statistics for all global CAR actions.
Examples
# Clear statistics for the global CAR action aggcar-1.
<Sysname> reset qos car name aggcar-1
display qos traffic-counter
Use display qos traffic-counter to display the traffic statistics collected by the specified counter and display the counter configuration.
Syntax
In standalone mode:
display qos traffic-counter { inbound | outbound } { counter0 | counter1 } slot slot-number
In IRF mode:
display qos traffic-counter { inbound | outbound } { counter0 | counter1 } chassis chassis-number slot slot-number
Views
Any view
Predefined user roles
network-admin
network-operator
mdc-admin
mdc-operator
Parameters
inbound: Inbound direction.
outbound: Outbound direction.
counter0: Counter 0.
counter1: Counter 1.
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 ID of the IRF member device, and the slot-number argument represents the slot number of the card. (In IRF mode.)
Examples
# Display the outbound traffic statistics of counter 0 on card 4.
<Sysname> display qos traffic-counter outbound counter0 slot 4
Slot 4 outbound counter0 mode:
Interface: all
VLAN: all
Local precedence: all
Drop priority: all
Traffic-counter summary:
Unicast: 1 packets
Multicast: 1 packets
Broadcast: 1 packets
Control packets: 1 packets
Bridge egress filtered packets: 1 packets
Tail drop packets: 1 packets
Tail drop multicast packets: 1 packets
Forwarding restrictions packets: 1 packets
Table 26 Command output
|
Field |
Description |
|
Slot 4 outbound counter0 mode |
Monitored objects of the counter in the outbound direction of a card. |
|
Interface |
Interfaces monitored by the counter. |
|
VLAN |
VLANs monitored by the counter. |
|
Local precedence |
Local precedence values monitored by the counter. |
|
Drop priority |
Drop priority values monitored by the counter. |
|
Traffic-counter summary |
Summary statistics collected by the counter. |
|
Unicast |
Number of unicast packets. |
|
Multicast |
Number of multicast packets. |
|
Broadcast |
Number of broadcast packets. |
|
Control packets |
Number of control packets. |
|
Bridge egress filtered packets |
Number of packets filtered in the egress direction of the bridge. |
|
Tail drop packets |
Number of packets dropped by tail drop. |
|
Tail drop multicast packets |
Number of multicast packets dropped by tail drop. |
|
Forwarding restrictions packets |
Number of packets that are prevented from being forwarded. This field is not supported. |
# Display the inbound traffic statistics of counter 0 on card 1.
<Sysname> display qos traffic-counter inbound counter0 slot 1
Slot 1 inbound counter0 mode:
Interface: all
VLAN: all
Traffic-counter summary:
Summary inbound: 0 packets
Dropped of local filtering: 0 packets
Dropped of VLAN filtering: 0 packets
Dropped of security filtering: 0 packets
Table 27 Command output
|
Field |
Description |
|
Slot 1 outbound counter0 mode |
Monitored objects of the counter in the outbound direction of a card. |
|
Interface |
Interfaces monitored by the counter. |
|
VLAN |
VLANs monitored by the counter. |
|
Traffic-counter summary |
Summary statistics collected by the counter. |
|
Summary inbound |
Number of packets received by the bridge (Layer 2). |
|
Dropped of local filtering |
Number of packets dropped on the bridge (Layer 2) for reasons other than bridge security filtering and VLAN ingress filtering. |
|
Dropped of VLAN filtering |
Number of packets dropped by VLAN ingress filtering. |
|
Dropped of security filtering |
Number of packets dropped by bridge (Layer 2) security filtering. |
qos traffic-counter
Use qos traffic-counter to enable the traffic accounting function and specify the type of traffic.
Use undo qos traffic-counter to disable the traffic accounting function.
Syntax
In standalone mode:
qos traffic-counter { inbound | outbound } { counter0 | counter1 } slot slot-number [ drop-priority drop-priority | interface interface-type interface-number | vlan vlan-id ] *
undo qos traffic-counter { inbound | outbound } { counter0 | counter1 } slot slot-number
In IRF mode:
qos traffic-counter { inbound | outbound } { counter0 | counter1 } chassis chassis-number slot slot-number [ drop-priority drop-priority | interface interface-type interface-number | vlan vlan-id ] *
undo qos traffic-counter { inbound | outbound } { counter0 | counter1 } chassis chassis-number slot slot-number
Default
The traffic accounting function is disabled.
Views
System view
Predefined user roles
network-admin
mdc-admin
Parameters
inbound: Inbound direction.
outbound: Outbound direction.
counter0: Counter 0.
counter1: Counter 1.
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 ID of the IRF member device. The slot-number argument represents the slot number of the card. (In IRF mode.)
drop-priority drop-priority: Specifies a drop priority in the range of 0 to 2.
interface interface-type interface-number: Specifies an interface by its type and number.
vlan vlan-id: Specifies a VLAN by its ID in the range of 1 to 4094.
Usage guidelines
A card provides two counters for traffic accounting. The monitored object can be an interface, a VLAN, or a drop priority value.
· If you do not specify an interface, the traffic of all the interfaces on the card is monitored.
· If you do not specify a VLAN, the traffic of all the VLANs is monitored.
· If you do not specify a drop priority value, the traffic with any drop priority value is monitored.
When you redefine the monitored object on a card with the qos traffic-counter command, the counter resets automatically.
The drop-priority keyword supports only the outbound direction.
FD and FG cards support counting only traffic on a specific interface, but not traffic of VLANs, drop priority values, or all interfaces. To specify an interface, specify the slot number and interface number.
Examples
# (In standalone mode.) Enable counter 0 of card 4 to collect statistics about the outbound traffic on GigabitEthernet 3/0/1.
<Sysname> system-view
[Sysname] qos traffic-counter outbound counter0 slot 4 interface gigabitethernet 3/0/1
# (n IRF mode.) Enable counter 0 of card 4 on IRF member device 1 to collect statistics about the outbound traffic on GigabitEthernet 1/3/0/1.
<Sysname> system-view
[Sysname] qos traffic-counter outbound counter0 chassis 1 slot 4 interface gigabitethernet 1/3/0/1
reset qos traffic-counter
Use reset qos traffic-counter to clear the traffic statistics collected by a counter.
Syntax
In standalone mode:
reset qos traffic-counter { inbound | outbound } { counter0 | counter1 } slot slot-number
In IRF mode:
reset qos traffic-counter { inbound | outbound } { counter0 | counter1 } chassis chassis-number slot slot-number
Views
User view
Predefined user roles
network-admin
mdc-admin
Parameters
inbound: Inbound direction.
outbound: Outbound direction.
counter0: Counter 0.
counter1: Counter 1.
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 ID of the IRF member device. The slot-number argument represents the slot number of the card. (In IRF mode.)
Examples
# (In standalone mode.) Clear the outbound traffic statistics collected by counter 0 on card 4.
<Sysname> reset qos traffic-counter outbound counter0 slot 4
# (In IRF mode.) Clear the outbound traffic statistics collected by counter 0 on card 4 on IRF member device 1.
<Sysname> reset qos traffic-counter outbound counter0 chassis 1 slot 4
display qos queue-statistics interface outbound
Use display qos queue-statistics interface outbound to display queue-based outbound traffic statistics for an interface.
Syntax
display qos queue-statistics interface [ interface-type interface-number ] outbound
Views
Any view
Predefined user roles
Parameters
interface-type interface-number: Specifies an interface by its type and number. If you do not specify an interface, this command displays the queue-based outbound traffic statistics for all interfaces on an MDC.
Usage guidelines
This command displays statistics only for the packets on FD cards, FG cards, and OAA cards LST1FW3C1 and LST1NSM2C1.
FD cards refer to cards suffixed with FD, for example, LST1XP48LFD1. FG cards refer to cards suffixed with FG.
Examples
# Display queue-based outbound traffic statistics for Ten-GigabitEthernet 3/0/1.
<Sysname> display qos queue-statistics interface Ten-GigabitEthernet3/0/1 outbound
Interface: Ten-GigabitEthernet3/0/1
Direction: outbound
Forwarded: 0 packets, 0 bytes
Dropped: 0 packets, 0 bytes
Queue 0
Forwarded: 0 packets, 0 bytes
Dropped: 0 packets, 0 bytes
Queue 1
Forwarded: 0 packets, 0 bytes
Dropped: 0 packets, 0 bytes
Queue 2
Forwarded: 0 packets, 0 bytes
Dropped: 0 packets, 0 bytes
Queue 3
Forwarded: 0 packets, 0 bytes
Dropped: 0 packets, 0 bytes
Queue 4
Forwarded: 0 packets, 0 bytes
Dropped: 0 packets, 0 bytes
Queue 5
Forwarded: 0 packets, 0 bytes
Dropped: 0 packets, 0 bytes
Queue 6
Forwarded: 0 packets, 0 bytes
Dropped: 0 packets, 0 bytes
Queue 7
Forwarded: 0 packets, 0 bytes
Dropped: 0 packets, 0 bytes
Table 28 Command output
|
Field |
Description |
|
Interface |
Interface for which queue-based traffic statistics are displayed. |
|
Direction |
Direction of traffic for which statistics are collected. |
|
Forwarded |
Counts forwarded traffic on the interface both in packets and in bytes. |
|
Dropped |
Counts dropped traffic on the interface both in packets and in bytes. |
qos queue-statistics outbound
Use qos queue-statistics outbound to enable queue-based accounting in the outbound direction of all interfaces.
Use undo qos queue-statistics outbound to disable queue-based accounting in the outbound direction of all interfaces.
Syntax
qos queue-statistics outbound
undo qos queue-statistics outbound
Default
Queue-based accounting is enabled in the outbound direction of all interfaces.
Views
System view
Predefined user roles
network-admin
Usage guidelines
The qos queue-statistics outbound command is supported only by the default MDC. After you configure this command on the default MDC, the configuration also takes effect on non-default MDCs. For more information about MDCs, see Virtual Technologies Configuration Guide.
This command can collect statistics only for known unicast packets received on FD and FG cards. This command cannot collect statistics for unknown unicast packets, broadcast packets, multicast packets, or protocol packets.
Examples
# Enable queue-based traffic accounting in the outbound direction of all interfaces.
[Sysname] qos queue-statistics outbound
Related commands
display qos queue-statistics interface outbound
