Network Queue QoS Policies
248
Quality of Service Guide
3HE 11014 AAAC TQZZA Edition: 01
Parameters sub-rate — the egress rate in kb/s
Values 1 to 10000000
include-fcs — the egress rate limit is applied to the traffic rate egressing the port with
the 4-byte Ethernet FCS field included. This option must be selected if the allow-eth-
bn-rate-changes option is selected; otherwise, the dynamically changed bandwidth
will not match the intended rate.
allow-eth-bn-rate-changes — enables the Y.1731 ETH-BN client MEP option on the
port. The egress rate will be dynamically changed to the bandwidth indicated in
messages received from an ETH-BN server MEP. When enabled, the received rate
overrides the configured sub-rate for the port.
hold-time — configures the hold time for egress rate bandwidth changes based on a
received BNM, in seconds
Values 1 to 600
Default 5
scheduler-mode
Syntax scheduler-mode {profile | 4-priority | 16-priority}
Context config>port>ethernet>network
Description This command selects the network-side scheduling option for Ethernet ports on the
equipment listed in Table 10 and Table 12.
On the 6-port Ethernet 10Gbps Adapter card and the 7705 SAR-X, scheduler-mode is
permanently set to support 4-priority-hqos and is not user-configurable. There is no keyword
to configure 4-priority-hqos.
With profiled (or rate-based) scheduling, both in-profile and out-of-profile scheduling are
supported. Packets with a flow rate that is less than or equal to the CIR value of a queue are
scheduled as in-profile. Packets with a flow rate that exceeds the CIR value but is less than
the PIR value of a queue are scheduled as out-of-profile. In-profile traffic has strict priority
over out-of-profile traffic.
Profiled scheduling does not take queue type into consideration. With queue type-based
scheduling, queues are divided into two categories – those that are serviced by the Expedited
scheduler and those that are serviced by the Best Effort scheduler. The Expedited scheduler
has precedence over the Best Effort scheduler.
Four-priority scheduling combines both profiled and queue type-based scheduling. The
combination provides four scheduling priorities. Packets are scheduled in the following order,
in strict priority fashion:
• Expedited in-profile packets
• Best-effort in-profile packets
• Expedited out-of-profile packets