Login
- Table of Contents
- Related Documents
-
| Title | Size | Download |
|---|---|---|
| 04-HQoS commands | 121.05 KB |
forwarding-group (forwarding group match criterion view)
display qos forwarding-profile
display qos scheduler-policy diagnosis interface
display qos scheduler-policy interface
forwarding-group profile (scheduler-policy match criterion view)
qos apply scheduler-policy outbound
HQoS commands
Forwarding class commands
display qos forwarding-class
Use display qos forwarding-class to display forwarding classes.
Syntax
display qos forwarding-class [ name fc-name ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
name fc-name: Specifies a forwarding class by its name, a case-sensitive string of 1 to 31 characters. If you do not specify a forwarding class, the command displays all forwarding classes.
Examples
# Display forwarding class BE.
<Sysname> display qos forwarding-class name BE
Forwarding class: BE, ID: 0
# Display all forwarding classes.
<Sysname> display qos forwarding-class
Forwarding class: BE, ID: 0
Forwarding class: AF, ID: 1
Forwarding class: EF, ID: 2
Forwarding class: NC, ID: 3
remark forwarding-class
Use remark forwarding-class to configure an action of marking a forwarding class.
Use undo remark forwarding-class to restore the default.
Syntax
remark forwarding-class { id fc-id | name fc-name }
undo remark forwarding-class
Default
No action of marking forwarding classes is configured.
Views
Traffic behavior view
Predefined user roles
network-admin
Parameters
id fc-id: Specifies a forwarding class by its ID. The value range for fc-id varies by device model. Only predefined forwarding classes can be specified.
name fc-name: Specifies a forwarding class by its name, a case-sensitive string of 1 to 31 characters. Only predefined forwarding classes can be specified.
Usage guidelines
If you execute this command multiple times in the same traffic behavior, the most recent configuration takes effect.
Examples
# Mark traffic with forwarding class BE.
<Sysname> system-view
[Sysname] traffic behavior testtb
[Sysname-behavior-testtb] remark forwarding-class name BE
Forwarding group commands
display qos forwarding-group
Use display qos forwarding-group to display forwarding groups.
Syntax
display qos forwarding-group [ name fg-name ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
name fg-name: Specifies a forwarding group by its name, a case-sensitive string of 1 to 31 characters. If you do not specify a forwarding group, the command displays all forwarding groups.
Examples
# Display forwarding group testfg1, which has child forwarding groups.
<Sysname> display qos forwarding-group name testfg1
Forwarding group: testfg1, ID: 10
match service-vlan-id 1 to 10
Forwarding group: subfg1, ID: 1, profile: fgprofile1
match service-vlan-id 11 to 20
Forwarding group: subfg2, ID: 2, profile: fgprofile2
# Display forwarding group testfg2, which has nested forwarding classes.
<Sysname> display qos forwarding-group name testfg2
Forwarding group: testfg2, ID: 10
Forwarding class: BE, ID: 0, profile: fcprofile1
Forwarding class: AF, ID: 1, profile: fcprofile2
Forwarding class: EF, ID: 2, profile: fcprofile3
Forwarding class: NC, ID: 3, profile: fcprofile4
forwarding-class
Use forwarding-class to nest a forwarding class in a forwarding group and specify a forwarding profile for the forwarding class.
Use undo forwarding-class to remove a nested forwarding class from a forwarding group.
Syntax
forwarding-class fc-name profile fp-name
undo forwarding-class fc-name
Default
A user-defined forwarding group does not have nested forwarding classes.
Views
Forwarding group view
Predefined user roles
network-admin
Parameters
fc-name: Specifies a forwarding class by its name, a case-sensitive string of 1 to 31 characters. Only predefined forwarding classes can be specified.
profile fp-name: Specifies a forwarding profile by its name, a case-sensitive string of 1 to 31 characters.
Usage guidelines
You cannot modify or remove the predefined forwarding classes nested in the predefined forwarding group.
The forwarding profile to be associated must already exist.
You cannot nest a forwarding class in a forwarding group with child forwarding groups nested.
Examples
# Nest forwarding class BE in forwarding group testfg and specify forwarding profile testfp for this forwarding class.
<Sysname> system-view
[Sysname] qos forwarding-group testfg
[Sysname-hqos-fg-testfg] forwarding-class BE profile testfp
forwarding-group (forwarding group match criterion view)
Use forwarding-group to perform the following tasks:
· Nest a forwarding group (child) in a match criterion of another forwarding group (parent).
· Specify a forwarding profile for the child forwarding group.
Use undo forwarding-group to remove the nested forwarding group.
Syntax
forwarding-group sub-fg-name profile fp-name
undo forwarding-group sub-fg-name
Default
A user-defined forwarding group does not have child forwarding groups.
Views
Forwarding group match criterion view
Predefined user roles
network-admin
Parameters
sub-fg-name: Specifies a child forwarding group by its name, a case-sensitive string of 1 to 31 characters.
profile fp-name: Specifies a forwarding profile by its name, a case-sensitive string of 1 to 31 characters.
Usage guidelines
The child forwarding group and the forwarding profile to be specified must already exist.
You cannot nest a forwarding group in a forwarding group with forwarding classes nested.
A forwarding group with forwarding groups nested cannot be nested in another forwarding group.
Examples
# Configure the match criterion local QoS ID 2 for forwarding group testfg. Nest forwarding group subfg in forwarding group testfg, and specify forwarding profile testfp for forwarding group subfg.
<Sysname> system-view
[Sysname] qos forwarding-group testfg
[Sysname-hqos-fg-testfg] match qos-local-id 2
[Sysname-hqos-fg-testfg-match] forwarding-group subfg profile testfp
match
Use match to configure a match criterion for a parent forwarding group and enter forwarding group match criterion view, or enter the view of an existing match criterion.
Use undo match to delete the configured match criterion.
Syntax
match match-criteria
undo match match-criteria
Default
No match criteria exist.
Views
Forwarding group view
Predefined user roles
network-admin
Parameters
match-criteria: Specifies a match criterion. Table 1 shows the available match criteria.
Table 1 Available match criteria
|
Option |
Description |
|
qos-local-id local-id-list |
Matches a local QoS ID. The local-id-list argument specifies a space-separated list of up to 8 local QoS ID items. Each item specifies a local QoS ID or a range of local QoS IDs in the form of local-id1 to local-id2. The value range for local QoS IDs is 1 to 4095. The ID for local-id2 must be equal to or greater than the ID for local-id1. |
Usage guidelines
Executing the match command only leads you to the forwarding group match criterion view. The configured match criterion takes effect only after a child forwarding group is configured in that view.
You cannot configure the group mode for a forwarding group with forwarding classes nested.
Removing a match criterion also removes the child forwarding group and its associated forwarding profile.
Examples
# Configure the match criterion local QoS ID 2 and enter forwarding group match criterion view.
<Sysname> system-view
[Sysname] qos forwarding-group testfg
[Sysname-hqos-fg-testfg] match qos-local-id 2
[Sysname-hqos-fg-testfg-match]
Related commands
forwarding-group profile (scheduler-policy match criterion view)
qos forwarding-group
Use qos forwarding-group to create a user-defined forwarding group and enter its view, or enter the view of an existing forwarding group.
Use undo qos forwarding-group to delete a user-defined forwarding group.
Syntax
qos forwarding-group fg-name
undo qos forwarding-group fg-name
Default
No user-defined forwarding groups exist.
Views
System view
Predefined user roles
network-admin
Parameters
fg-name: Specifies a forwarding group name, a case-sensitive string of 1 to 31 characters. This argument cannot be the name of the predefined forwarding group (default).
Usage guidelines
You cannot modify or delete the predefined forwarding group default (numbered 0).
The system supports a maximum number of 8191 user-defined forwarding groups.
To delete a forwarding group nested in another forwarding group or a scheduler policy, first remove the nesting.
Examples
# Create a forwarding group named testfg.
<Sysname> system-view
[Sysname] qos forwarding-group testfg
[Sysname-hqos-fg-testfg]
Drop profile commands
display qos drop-profile
Use display qos drop-profile to display drop profiles.
Syntax
display qos drop-profile [ name dp-name ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
name dp-name: Specifies a drop profile by its name, a case-sensitive string of 1 to 31 characters. If you do not specify a drop profile, the command displays all drop profiles.
Examples
# Display drop profile testdp.
<Sysname> display qos drop-profile name testdp
Drop profile: testdp, ID: 10
Green thresholds: 50/60/30(min/max/prob)
Yellow thresholds: 50/60/30(min/max/prob)
Red thresholds: 50/60/30(min/max/prob)
Weighting constant: 2
Table 2 Command output
|
Field |
Description |
|
Green thresholds |
Drop parameters for green packets. |
|
Yellow thresholds |
Drop parameters for yellow packets. |
|
Red thresholds |
Drop parameters for red packets. |
|
min/max/prob |
Lower threshold, upper threshold, and drop probability. When the average queue length reaches the lower threshold, newly arriving packets are randomly dropped at the drop probability When the average queue length reaches the upper threshold, all newly arriving packets are dropped. |
|
Weighting constant |
Exponent for average queue length calculation. |
green
Use green to set drop parameters for green packets.
Use undo green to restore the default.
Syntax
green low-limit low-limit high-limit high-limit discard-probability discard-prob
undo green
Default
The lower threshold is 0, the upper threshold is 512, and the drop probability is 10.
Views
Drop profile view
Predefined user roles
network-admin
Parameters
low-limit low-limit: Specifies the lower threshold in the range of 0 to 912000 packets. When the average queue length reaches the threshold, newly arriving packets are randomly dropped.
high-limit high-limit: Specifies the upper threshold in the range of 0 to 912000 packets. When the average queue length reaches the upper threshold, all newly arriving packets are dropped. The upper threshold must be higher than the lower threshold.
discard-probability discard-prob: Specifies the drop probability in percentage, in the range of 0 to 100. Setting discard-prob to 100 causes tail drop to take effect.
Examples
# Configure drop parameters for green packets.
<Sysname> system-view
[Sysname] qos drop-profile testdp
[Sysname-hqos-dp-testdp] green low-limit 500 high-limit 700 discard-probability 40
qos drop-profile
Use qos drop-profile to create a user-defined drop profile and enter its view, or enter the view of an existing drop profile.
Use undo qos drop-profile to delete a user-defined drop profile.
Syntax
qos drop-profile dp-name
undo qos drop-profile dp-name
Default
No user-defined drop profiles exist.
Views
System view
Predefined user roles
network-admin
Parameters
dp-name: Specifies a drop profile name, a case-sensitive string of 1 to 31 characters. This argument cannot be the name of the predefined drop profile (default).
Usage guidelines
You cannot modify or delete the predefined drop profile default (numbered 0).
To delete a drop profile referenced by a forwarding profile, first remove the drop profile from the forwarding profile.
Examples
# Create a drop profile named testdp.
<Sysname> system-view
[Sysname] qos drop-profile testdp
[Sysname-dp-testdp]
red
Use red to configure drop parameters for red packets.
Use undo red to restore the default.
Syntax
red low-limit low-limit high-limit high-limit discard-probability discard-prob
undo red
Default
The lower threshold is 0, the upper threshold is 512, and the drop probability is 10.
Views
Drop profile view
Predefined user roles
network-admin
Parameters
low-limit low-limit: Specifies the lower threshold in the range of 0 to 912000 packets. When the average queue length reaches the lower threshold, newly arriving packets are randomly dropped.
high-limit high-limit: Specifies the upper threshold in the range of 0 to 912000 packets. When the average queue length reaches the upper threshold, all newly arriving packets are dropped. The upper threshold must be higher than the lower threshold.
discard-probability discard-prob: Specifies the drop probability in percentage, in the range of 0 to 100. Setting discard-prob to 100 causes tail drop to take effect.
Examples
# Configure drop parameters for red packets.
<Sysname> system-view
[Sysname] qos drop-profile testdp
[Sysname-hqos-dp-testdp] red low-limit 500 high-limit 700 discard-probability 40
weighting-constant
Use weighting-constant to set the exponent for average queue length calculation.
Use undo weighting-constant to restore the default.
Syntax
weighting-constant exponent
undo weighting-constant
Default
The exponent for average queue length calculation is 8.
Views
Drop profile view
Predefined user roles
network-admin
Parameters
exponent: Specifies the exponent for average queue length calculation, in the range of 1 to 16.
Usage guidelines
The greater the exponent, the less sensitive the average queue length is to real-time queue length changes.
Examples
# Set the exponent for average queue length calculation to 2.
<Sysname> system-view
[Sysname] qos drop-profile testdp
[Sysname-hqos-dp-testdp] weighting-constant 2
yellow
Use yellow to configure drop parameters for yellow packets.
Use undo yellow to restore the default.
Syntax
yellow low-limit low-limit high-limit high-limit discard-probability discard-prob
undo yellow
Default
The lower threshold is 0, the upper threshold is 512, and the drop probability is 10.
Views
Drop profile view
Predefined user roles
network-admin
Parameters
low-limit low-limit: Specifies the lower threshold in the range of 0 to 912000 packets. When the average queue length reaches the lower threshold, newly arriving packets are randomly dropped.
high-limit high-limit: Specifies the upper threshold in the range of 0 to 912000 packets. When the average queue length reaches the upper threshold, all newly-arriving packets are dropped. The upper threshold must be higher than the lower threshold.
discard-probability discard-prob: Specifies the drop probability in percentage, in the range of 0 to 100. Setting discard-prob to 100 causes tail drop to take effect.
Examples
# Configure drop parameters for yellow packets.
<Sysname> system-view
[Sysname] qos drop-profile testdp
[Sysname-hqos-dp-testdp] yellow low-limit 500 high-limit 700 discard-probability 40
Forwarding profile commands
bandwidth
Use bandwidth to set the minimum guaranteed bandwidth for a forwarding profile.
Use undo bandwidth to restore the default.
Syntax
bandwidth bandwidth-value
undo bandwidth
Default
No minimum guaranteed bandwidth is set in a forwarding profile.
Views
Forwarding profile view
Predefined user roles
network-admin
Parameters
bandwidth-value: Specifies the minimum guaranteed bandwidth in the range of 8 to 10000000 kbps.
Examples
# Set the minimum guaranteed bandwidth to 2000 kbps for forwarding profile testfp.
<Sysname> system-view
[Sysname] qos forwarding-profile testfp
[Sysname-hqos-fp-testfp] bandwidth 2000
display qos forwarding-profile
Use display qos forwarding-profile to display forwarding profiles.
Syntax
display qos forwarding-profile [ name fp-name ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
name fp-name: Specifies a forwarding profile by its name, a case-sensitive string of 1 to 31 characters. If you do not specify a forwarding profile, the command displays all forwarding profiles.
Examples
# Display forwarding profile testfp.
<Sysname> display qos forwarding-profile name testfp
Forwarding profile: testfp, ID: 10
GTS: CIR 100(kbps), CBS 50(Bytes)
Bandwidth: 1000(kbps)
Drop profile: default
Table 3 Command output
|
Field |
Description |
|
Bandwidth |
Minimum guaranteed bandwidth. |
drop-profile
Use drop-profile to use a drop profile in a forwarding profile.
Use undo drop-profile to restore the default.
Syntax
drop-profile dp-name
undo drop-profile
Default
A forwarding profile does not use any drop profile and uses tail drop.
Views
Forwarding profile view
Predefined user roles
network-admin
Parameters
dp-name: Specifies an existing drop profile by its name, a case-sensitive string of 1 to 31 characters.
Examples
# Use drop profile testdp in forwarding profile testfp.
<Sysname> system-view
[Sysname] qos forwarding-profile testfp
[Sysname-hqos-fp-testfp] drop-profile testdp
gts
Use gts to configure GTS parameters for a forwarding profile.
Use undo gts to restore the default.
Syntax
gts cir cir-value [ cbs cbs-value ] [ pir pir-value ]
undo gts
Default
No GTS configuration exists in a forwarding profile.
Views
Forwarding profile view
Predefined user roles
network-admin
Parameters
cir-value: Specifies the CIR in the range of 300 to 10000000 kbps.
cbs cbs-value: Specifies the CBS in the range of 4096 to 16000000 bytes.
pir pir-value: Specifies the PIR in the range of 300 to 10000000 kbps. If the PIR is not configured, only one rate is used for traffic policing.
Examples
# Configure GTS parameters for forwarding profile testfp.
<Sysname> system-view
[Sysname] qos forwarding-profile testfp
[Sysname-hqos-fp-testfp] gts cir 1000 cbs 1000 pir 2000
qos forwarding-profile
Use qos forwarding-profile to create a user-defined forwarding profile and enter its view, or enter the view of an existing forwarding profile.
Use undo qos forwarding-profile to delete a user-defined forwarding profile.
Syntax
qos forwarding-profile fp-name
undo qos forwarding-profile fp-name
Default
No user-defined forwarding profiles exist.
Views
System view
Predefined user roles
network-admin
Parameters
fp-name: Specifies a forwarding profile name, a case-sensitive string of 1 to 31 characters. This argument cannot be the name of the predefined forwarding profile (default).
Usage guidelines
You cannot modify or delete the predefined forwarding profile default.
To delete a forwarding group nested in another forwarding group or a scheduler policy, first remove the nesting.
Examples
# Create a forwarding profile named testfp.
<Sysname> system-view
[Sysname] qos forwarding-profile testfp
sp
Use sp to enable SP queuing for a forwarding profile.
Use undo sp to restore the default.
Syntax
sp
undo sp
Default
No SP queuing configuration exists in a forwarding profile.
Views
Forwarding profile view
Predefined user roles
network-admin
Examples
# Enable SP queuing for forwarding profile testfp.
<Sysname> system-view
[Sysname] qos forwarding-profile testfp
[Sysname-hqos-fp-testfp] sp
wfq
Use wfq to configure WFQ queuing for a forwarding profile.
Use undo wfq to restore the default.
Syntax
wfq [ weight weight-value ]
undo wfq
Default
No WFQ queuing configuration exists in a forwarding profile.
Views
Forwarding profile view
Predefined user roles
network-admin
Parameters
weight weight-value: Specifies the scheduling weight in the range of 1 to 63. The default value is 1.
Usage guidelines
WFQ queues with the same priority are scheduled according to their weights. The weight of a WFQ queue determines the percentage of bandwidth assigned to the queue.
Examples
# Configure WFQ queuing for forwarding profile testfp.
<Sysname> system-view
[Sysname] qos forwarding-profile testfp
[Sysname-hqos-fp-testfp] wfq weight 2
Scheduler policy commands
display qos scheduler-policy
Use display qos scheduler-policy to display scheduler policies.
Syntax
display qos scheduler-policy [ name sp-name ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
name sp-name: Specifies a scheduler policy by its name, a case-sensitive string of 1 to 31 characters. If you do not specify a scheduler policy, the command displays all scheduler policies.
Examples
# Display scheduler policy test_sp.
<Sysname> display qos scheduler-policy name test_sp
SP -- Scheduler policy FG -- Forwarding group FC -- Forwarding class
FP -- Forwarding profile L -- Layer
--------------------------------------------------------------------------
SP: test_sp (0)
| Scheduler unit: byte-count
|
| Match: group
+--FG(L1): default(0)
| | FP: default(0)
| |
| +--FC: BE(0)
| | FP: default(0)
| |
| +--FC: L2(1)
| | FP: default(0)
| |
| +--FC: AF(2)
| | FP: default(0)
| |
| +--FC: L1(3)
| | FP: default(0)
| |
| +--FC: H2(4)
| | FP: default(0)
| |
| +--FC: EF(5)
| | FP: default(0)
| |
| +--FC: H1(6)
| | FP: default(0)
| |
| +--FC: NC(7)
| FP: default(0)
|
| Match: group
+--FG(L1): fg1-1(101)
| | FP: fp1-1(10)
| |
| | Match: qos-local-id 2 to 10
| +--FG(L2): fg2-1(1)
| | | FP: fp2(9)
| | |
| | +--FC: BE(0)
| | | FP: fp3-0(1)
| | |
| | +--FC: L2(1)
| | | FP: fp3-1(2)
| | |
| | +--FC: AF(2)
| | | FP: fp3-2(3)
| | |
| | +--FC: L1(3)
| | | FP: fp3-3(4)
| | |
| | +--FC: H2(4)
| | | FP: fp3-4(5)
| | |
| | +--FC: EF(5)
| | | FP: fp3-5(6)
| | |
| | +--FC: H1(6)
| | | FP: fp3-6(7)
| | |
| | +--FC: NC(7)
| | FP: fp3-7(8)
| |
| | Match: qos-local-id 11 to 20
| +--FG(L2): fg2-2(2)
| | FP: fp2(9)
| |
| +--FC: BE(0)
| | FP: fp3-0(1)
| |
| +--FC: L2(1)
| | FP: fp3-1(2)
| |
| +--FC: AF(2)
| | FP: fp3-2(3)
| |
| +--FC: L1(3)
| | FP: fp3-3(4)
| |
| +--FC: H2(4)
| | FP: fp3-4(5)
| |
| +--FC: EF(5)
| | FP: fp3-5(6)
| |
| +--FC: H1(6)
| | FP: fp3-6(7)
| |
| +--FC: NC(7)
| FP: fp3-7(8)
|
| Match: qos-local-id 21 to 30
+--FG(L1): fg1-2(102)
| FP: fp1-2(11)
|
| Match: qos-local-id 21 to 30
+--FG(L2): fg2-3(3)
| FP: fp2(9)
|
+--FC: BE(0)
| FP: fp3-0(1)
|
+--FC: L2(1)
| FP: fp3-1(2)
|
+--FC: AF(2)
| FP: fp3-2(3)
|
+--FC: L1(3)
| FP: fp3-3(4)
|
+--FC: H2(4)
| FP: fp3-4(5)
|
+--FC: EF(5)
| FP: fp3-5(6)
|
+--FC: H1(6)
| FP: fp3-6(7)
|
+--FC: NC(7)
FP: fp3-7(8)
Table 4 Command output
|
Field |
Description |
|
match |
The match mode is used for configuring match criteria. |
|
group |
The group mode is used for configuring match criteria. |
|
qos-local-id |
Local QoS ID. |
|
Number in the brackets |
ID of the field (forwarding class/forwarding group/forwarding profile/scheduler policy). |
display qos scheduler-policy diagnosis interface
Use display qos scheduler-policy diagnosis interface to display diagnosis information about scheduler policies applied to interfaces.
Syntax
In standalone mode:
display qos scheduler-policy diagnosis interface [ interface-type interface-number ] [ slot slot-number ] [ outbound ]
In IRF mode:
display qos scheduler-policy diagnosis interface [ interface-type interface-number ] [ chassis chassis-number slot slot-number ] [ outbound ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
interface-type interface-number: Specifies an interface by its type and number.
slot slot-number: Specifies a card by its slot number. This option is available only if the specified interface is a logical interface (for example, a VLAN interface). (In standalone mode.)
chassis chassis-number slot slot-number: Specifies a card on an IRF member device. The chassis-number argument represents the member ID of the IRF member device. The slot-number argument represents the slot number of the card. This option is available only if the specified interface is a logical interface (for example, a VLAN interface). (In IRF mode.)
outbound: Specifies scheduler policies applied to the outbound direction. The command execution result is the same if you do not specify this keyword.
Usage guidelines
If you do not specify an interface, the command displays diagnosis information about scheduler policies applied to all interfaces.
Examples
# Display diagnosis information about the scheduler policy applied to the outbound direction of GigabitEthernet 3/1/1.
<Sysname> display qos scheduler-policy diagnosis interface gigabitethernet 3/1/1 outbound
SP -- Scheduler policy FG -- Forwarding group FC -- Forwarding class
FP -- Forwarding profile L -- Layer
--------------------------------------------------------------------------
Interface: GigabitEthernet3/1/1
Direction: Outbound
SP: 1(0)
|
| Match: group
+--FG(L1): default(0)
| | FP: default(0)
| | Status: Success
| |
| +--FC: BE(0)
| | FP: default(0)
| | Status: Success
| |
| +--FC: L2(1)
| | FP: default(0)
| | Status: Success
| |
| +--FC: AF(2)
| | FP: default(0)
| | Status: Success
| |
| +--FC: L1(3)
| | FP: default(0)
| | Status: Success
| |
| +--FC: H2(4)
| | FP: default(0)
| | Status: Success
| |
| +--FC: EF(5)
| | FP: default(0)
| | Status: Success
| |
| +--FC: H1(6)
| | FP: default(0)
| | Status: Success
| |
| +--FC: NC(7)
| FP: default(0)
| Status: Success
|
| Match: group
+--FG(L1): fg1-1(101)
| | FP: fp1-1(10)
| | Status: Success
| |
| | Match: qos-local-id 2 to 10
| +--FG(L2): fg2-1(1)
| | | FP: fp2(9)
| | | Status: Success
| | |
| | +--FC: BE(0)
| | | FP: fp3-0(1)
| | | Status: Success
| | |
| | +--FC: L2(1)
| | | FP: fp3-1(2)
| | | Status: Success
| | |
| | +--FC: AF(2)
| | | FP: fp3-2(3)
| | | Status: Success
| | |
| | +--FC: L1(3)
| | | FP: fp3-3(4)
| | | Status: Success
| | |
| | +--FC: H2(4)
| | | FP: fp3-4(5)
| | | Status: Success
| | |
| | +--FC: EF(5)
| | | FP: fp3-5(6)
| | | Status: Success
| | |
| | +--FC: H1(6)
| | | FP: fp3-6(7)
| | | Status: Success
| | |
| | +--FC: NC(7)
| | FP: fp3-7(8)
| | Status: Success
| |
| | Match: qos-local-id 11 to 20
| +--FG(L2): fg2-2(2)
| | FP: fp2(9)
| | Status: Success
| |
| +--FC: BE(0)
| | FP: fp3-0(1)
| | Status: Success
| |
| +--FC: L2(1)
| | FP: fp3-1(2)
| | Status: Success
| |
| +--FC: AF(2)
| | FP: fp3-2(3)
| | Status: Success
| |
| +--FC: L1(3)
| | FP: fp3-3(4)
| | Status: Success
| |
| +--FC: H2(4)
| | FP: fp3-4(5)
| | Status: Success
| |
| +--FC: EF(5)
| | FP: fp3-5(6)
| | Status: Success
| |
| +--FC: H1(6)
| | FP: fp3-6(7)
| | Status: Success
| |
| +--FC: NC(7)
| FP: fp3-7(8)
| Status: Success
|
| Match: qos-local-id 21 to 30
+--FG(L1): fg1-2(102)
| FP: fp1-2(11)
| Status: Success
|
| Match: qos-local-id 21 to 30
+--FG(L2): fg2-3(3)
| FP: fp2(9)
| Status: Success
|
+--FC: BE(0)
| FP: fp3-0(1)
| Status: Success
|
+--FC: L2(1)
| FP: fp3-1(2)
| Status: Success
|
+--FC: AF(2)
| FP: fp3-2(3)
| Status: Success
|
+--FC: L1(3)
| FP: fp3-3(4)
| Status: Success
|
+--FC: H2(4)
| FP: fp3-4(5)
| Status: Success
|
+--FC: EF(5)
| FP: fp3-5(6)
| Status: Success
|
+--FC: H1(6)
| FP: fp3-6(7)
| Status: Success
|
+--FC: NC(7)
FP: fp3-7(8)
Status: Success
Table 5 Command output
|
Field |
Description |
|
Status |
Issuing status of a forwarding profile: · Incomplete—Incomplete match criteria. · Success—All contents have been issued successfully. · Inactive—A forwarding profile does not take effect. · If a forwarding profile has failed to be issued completely, the following possible reasons are displayed: ¡ GTS Failed—The GTS parameters failed to be issued to a forwarding class or forwarding group. ¡ WRED Failed—The WRED parameters failed to be issued to a forwarding class or forwarding group. ¡ Queue Failed—The queuing algorithm failed to be issued to a forwarding class or forwarding group. ¡ Bandwidth Failed—The minimum guaranteed bandwidth failed to be issued to a forwarding class or forwarding group. |
display qos scheduler-policy interface
Use display qos scheduler-policy interface to display the statistics and configuration for scheduler policies applied to interfaces.
Syntax
display qos scheduler-policy interface [ interface-type interface-number ] [ outbound ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
interface-type interface-number: Specifies an interface by its type and number.
outbound: Specifies scheduler policies applied to the outbound direction. The command execution result is the same if you do not specify this keyword.
Usage guidelines
If you do not specify an interface, the command displays the statistics and configuration for scheduler policies applied to all interfaces.
If per-queue traffic accounting is disabled on an interface, the command displays only the configuration for scheduler policies.
Examples
# Display the configuration and statistics for the scheduler policy applied to the outbound direction of GigabitEthernet 3/1/1.
<Sysname> display qos scheduler-policy interface gigabitethernet 3/1/1 outbound
SP -- Scheduler policy FG -- Forwarding group FC -- Forwarding class
FP -- Forwarding profile L -- Layer
--------------------------------------------------------------------------
Interface: Ten-GigabitEthernet3/1/1
Direction: Outbound
SP: sp(0)
|
| Match: group
+--FG(L1): default(0)
| FP: default(0)
| Forwarded: 0 packets, 0 bytes
| Forwarded green: 0 packets, 0 bytes
| Forwarded yellow: 0 packets, 0 bytes
| Forwarded red: 0 packets, 0 bytes
| Dropped: 0 packets, 0 bytes
| Dropped green: 0 packets, 0 bytes
| Dropped yellow: 0 packets, 0 bytes
| Dropped red: 0 packets, 0 bytes
|
+--FC: BE(0)
| FP: default(0)
| Current queue length: 0 packets
| Forwarded: 0 packets, 0 bytes
| Forwarded green: 0 packets, 0 bytes
| Forwarded yellow: 0 packets, 0 bytes
| Forwarded red: 0 packets, 0 bytes
| Dropped: 0 packets, 0 bytes
| Dropped green: 0 packets, 0 bytes
| Dropped yellow: 0 packets, 0 bytes
| Dropped red: 0 packets, 0 bytes
|
+--FC: L2(1)
| FP: default(0)
| Current queue length: 0 packets
| Forwarded: 0 packets, 0 bytes
| Forwarded green: 0 packets, 0 bytes
| Forwarded yellow: 0 packets, 0 bytes
| Forwarded red: 0 packets, 0 bytes
| Dropped: 0 packets, 0 bytes
| Dropped green: 0 packets, 0 bytes
| Dropped yellow: 0 packets, 0 bytes
| Dropped red: 0 packets, 0 bytes
|
+--FC: AF(2)
| FP: default(0)
| Current queue length: 0 packets
| Forwarded: 0 packets, 0 bytes
| Forwarded green: 0 packets, 0 bytes
| Forwarded yellow: 0 packets, 0 bytes
| Forwarded red: 0 packets, 0 bytes
| Dropped: 0 packets, 0 bytes
| Dropped green: 0 packets, 0 bytes
| Dropped yellow: 0 packets, 0 bytes
| Dropped red: 0 packets, 0 bytes
|
+--FC: L1(3)
| FP: default(0)
| Current queue length: 0 packets
| Forwarded: 0 packets, 0 bytes
| Forwarded green: 0 packets, 0 bytes
| Forwarded yellow: 0 packets, 0 bytes
| Forwarded red: 0 packets, 0 bytes
| Dropped: 0 packets, 0 bytes
| Dropped green: 0 packets, 0 bytes
| Dropped yellow: 0 packets, 0 bytes
| Dropped red: 0 packets, 0 bytes
|
+--FC: H2(4)
| FP: default(0)
| Current queue length: 0 packets
| Forwarded: 0 packets, 0 bytes
| Forwarded green: 0 packets, 0 bytes
| Forwarded yellow: 0 packets, 0 bytes
| Forwarded red: 0 packets, 0 bytes
| Dropped: 0 packets, 0 bytes
| Dropped green: 0 packets, 0 bytes
| Dropped yellow: 0 packets, 0 bytes
| Dropped red: 0 packets, 0 bytes
|
+--FC: EF(5)
| FP: default(0)
| Current queue length: 0 packets
| Forwarded: 0 packets, 0 bytes
| Forwarded green: 0 packets, 0 bytes
| Forwarded yellow: 0 packets, 0 bytes
| Forwarded red: 0 packets, 0 bytes
| Dropped: 0 packets, 0 bytes
| Dropped green: 0 packets, 0 bytes
| Dropped yellow: 0 packets, 0 bytes
| Dropped red: 0 packets, 0 bytes
|
+--FC: H1(6)
| FP: default(0)
| Current queue length: 0 packets
| Forwarded: 0 packets, 0 bytes
| Forwarded green: 0 packets, 0 bytes
| Forwarded yellow: 0 packets, 0 bytes
| Forwarded red: 0 packets, 0 bytes
| Dropped: 0 packets, 0 bytes
| Dropped green: 0 packets, 0 bytes
| Dropped yellow: 0 packets, 0 bytes
| Dropped red: 0 packets, 0 bytes
|
+--FC: NC(7)
FP: default(0)
Current queue length: 0 packets
Forwarded: 0 packets, 0 bytes
Forwarded green: 0 packets, 0 bytes
Forwarded yellow: 0 packets, 0 bytes
Forwarded red: 0 packets, 0 bytes
Dropped: 0 packets, 0 bytes
Dropped green: 0 packets, 0 bytes
Dropped yellow: 0 packets, 0 bytes
Dropped red: 0 packets, 0 bytes
Table 6 Command output
|
Field |
Description |
|
Forwarded green |
Number of forwarded green packets/bytes. |
|
Forwarded yellow |
Number of forwarded yellow packets/bytes. |
|
Forwarded red |
Number of forwarded red packets/bytes. |
|
Dropped |
Number of dropped packets/bytes. |
|
Tail dropped |
Number of tail-dropped packets/bytes. |
|
Dropped green |
Number of dropped green packets/bytes. |
|
Dropped yellow |
Number of dropped yellow packets/bytes. |
|
Dropped red |
Number of dropped red packets/bytes. |
forwarding-group profile (scheduler-policy match criterion view)
Use forwarding-group profile to nest a forwarding group in a match criterion of a scheduler policy and specify a forwarding profile for the forwarding group.
Use undo forwarding-group to remove the nested forwarding group from a match criterion of a scheduler policy.
Syntax
forwarding-group fg-name profile fp-name
undo forwarding-group fg-name
Default
The predefined forwarding group is nested in a scheduler policy in group mode.
Views
Scheduler policy match criterion view
Predefined user roles
network-admin
Parameters
fg-name: Specifies a forwarding group by its name, a case-sensitive string of 1 to 31 characters.
profile fp-name: Specifies a forwarding profile by its name, a case-sensitive string of 1 to 31 characters.
Usage guidelines
The forwarding group to be nested in a scheduler policy and the forwarding profile to be specified for the forwarding group must already exist.
You cannot remove the predefined forwarding group automatically nested in a scheduler policy.
Examples
# Configure the match criterion local QoS ID 1 for scheduler policy testsp. Nest forwarding group testfg in scheduler policy testsp, and specify the forwarding profile testfp for forwarding group testfg.
<Sysname> system-view
[Sysname] qos scheduler-policy testsp
[Sysname-hqos-sp-testsp] match qos-local-id 1
[Sysname-hqos-sp-testsp-match] forwarding-group testfg profile testfp
Related commands
match
match
Use match to configure a match criterion for a scheduler policy and enter its view, or enter the view of an existing scheduler policy match criterion.
Use undo match to delete the configured match criteria.
Syntax
match { match-criteria | group }
undo match { match-criteria | group }
Default
A user-defined scheduler policy has no match criteria.
Views
Scheduler policy view
Predefined user roles
network-admin
Parameters
match-criteria: Specifies a match criterion. For the available match criteria, see Table 1.
group: Specifies that a Layer 1 forwarding group uses the union of the match criteria of its Layer 2 forwarding groups.
Usage guidelines
Executing the match command only leads you to the scheduler policy match criterion view. The configured match criterion takes effect only after a child forwarding group is configured in that view.
Removing a match criterion for a scheduler policy also removes the nested forwarding groups and their associated forwarding profiles for the scheduler policy.
A forwarding group with nested forwarding classes cannot uses the group mode. The predefined forwarding group nested in a scheduler policy has used the group mode by default. You cannot modify or remove the match criteria of the predefined forwarding group.
Examples
# Configure the match criterion local QoS IDs 1 to 4 for scheduler policy testsp.
<Sysname> system-view
[Sysname] qos scheduler-policy testsp
[Sysname-hqos-sp-testsp] match qos-local-id 1 to 4
[Sysname-hqos-sp-testsp-match]
Related commands
forwarding-group profile (scheduler-policy match criterion view)
qos apply scheduler-policy outbound
Use qos apply scheduler-policy outbound to apply a scheduler policy to the outbound direction of an interface.
Use undo qos apply scheduler-policy outbound to remove a scheduler policy from an interface.
Syntax
qos apply scheduler-policy sp-name outbound
undo qos apply scheduler-policy sp-name outbound
Default
No scheduler policy is applied to an interface.
Views
Interface view
Predefined user roles
network-admin
Parameters
sp-name: Specifies a scheduler policy by its name, a case-sensitive string of 1 to 31 characters.
Usage guidelines
Only one scheduler policy can be applied to an interface.
The scheduler policy applied to an interface is mutually exclusive with the following QoS features configured on the interface:
· Queue-based GTS.
· WRED.
· Hardware congestion management.
Examples
# Apply scheduler policy testsp to the outbound direction of GigabitEthernet 3/1/1.
<Sysname> system-view
[Sysname] interface gigabitethernet 3/1/1
[Sysname-GigabitEthernet3/1/1] qos apply scheduler-policy testsp outbound
qos scheduler-policy
Use qos scheduler-policy to create a user-defined scheduler policy and enter its view, or enter the view of an existing scheduler policy.
Use undo qos scheduler-policy to delete a user-defined scheduler policy.
Syntax
qos scheduler-policy sp-name
undo qos scheduler-policy sp-name
Default
No user-defined scheduler policies exist.
Views
System view
Predefined user roles
network-admin
Parameters
sp-name: Specifies a scheduler policy name, a case-sensitive string of 1 to 31 characters.
Usage guidelines
The system supports a maximum number of 256 user-defined scheduler policies.
Examples
# Create a scheduler policy named testsp.
<Sysname> system-view
[Sysname] qos scheduler-policy testsp
scheduler-unit
Use scheduler-unit to specify the scheduling unit for a scheduler policy.
Use undo scheduler-unit to restore the default.
Syntax
qos scheduler-unit { byte-count | weight }
undo scheduler-unit
Default
The scheduling unit for a scheduler policy is byte-count.
Views
Scheduler policy view
Predefined user roles
network-admin
Parameters
byte-count: Allocates bandwidth based on the number of bytes.
weight: Allocates bandwidth based on the number of packets. This keyword is not supported in the current software version.
Examples
# Set the scheduling unit to byte-count for scheduler policy named testsp.
<Sysname> system-view
[Sysname] qos scheduler-policy testsp
[Sysname-hqos-sp-testsp] scheduler-unit byte-count
