Service Manual

Default Granularity for rate is Mbps unless you use the kbps option.
Command Modes CONFIGURATION
Command History
Version Description
9.7(0.0) Introduced on the S6000-ON.
9.3(0.0) Added support for committed rate and committed burst size, and for conguration
of rate limits on the S6000 platform.
Usage Information If you specify the pps keyword after the rate-shape command, the peak rate, peak burst, committed rate
and committed burst are all considered to be values as a measure of packets. If you do not specify the pps
or kbps keyword, the peak and committed rate settings are considered to be values in Mbps. Similarly, if
you enter the
kbps keyword, the peak and committed rate settings are treated as values in Kbps.
You cannot congure the committed rate settings to use a dierent metric or unit from the metric that is set
for peak rate attributes because when you use the rate-shape kbps command, it denotes the metric
for peak and committed rate attributes). Similarly, if you use the rate-shape pps option , it denotes the
metric for peak rate and committed rate attributes.
If you attempt to dene the committed rate to be less than the peak rate, an error message is displayed
stating that the peak rate cannot be lower than the committed rate. You can congure all the rate shaping
parameters to be either in bytes or packets measure for each queue. The rate and burst parameters for both
minimum and maximum settings for a queue can be either in packets or bytes. You cannot congure some of
rate shaping attributes to be in bytes measure and the remaining rate shaping attributes to be in packets
measure; all the rate shaping attributes must contain the same metric or unit of measure.
Example
Dell (conf-qos-policy-out) #rate-shape pps 100 100 peak pps 1000 200
Dell (conf-qos-policy-out) #rate-shape kbps 1024 100 peak kbps 102400 75
Dell (conf-qos-policy-out) # rate-shape 100 100 peak 1000 750
Dell(conf-qos-policy-in)#rate-police 100 25 peak 80 500
% Error: Peak rate cannot be less than committed rate.
service-pool wred
A global buer pool that is a shared buer pool accessed by multiple queues when the minimum guaranteed buers for the queue
are consumed can be congured on the S6000 and Z9000 platforms.
Create a global buer pool that is a shared buer pool accessed by multiple queues when the minimum guaranteed buers for the
queue are consumed. S4810, S4820T, S6000, and Z9000 platforms support four global service-pools in the egress direction. Two
service pools are used—one for lossy queues and the other for lossless (priority-based ow control (PFC)) queues. You can enable
WRED and ECN conguration on the global service-pools. You can dene WRED proles and weight on each of the global service-
pools for both lossy and lossless (PFC) service-pools.
Syntax
[No] service-pool wred {green | weight | yellow} {[pool0 number/string] |
[pool1 number/string]}
Parameters
service-pool Dene the mapping between the service class and policy-based QoS or routing.
wred Specify WRED curve parameters for a queue.
green Specify green (low) drop precedence to a queue.
weight Specify a weight factor to a queue.
1112
Quality of Service (QoS)