[Contents] [Prev] [Next] [Index] [Report an Error]

Configuring Enhanced Queuing DPC Rate Limits

You can rate-limit the strict-high and high queues on the Enhanced Queuing DPC. Without this limiting, traffic in higher priority queues can block the transmission of lower priority packets. Unless limited, higher priority traffic will always be sent before lower priority traffic, causing the lower priority queues to “starve” and cause timeouts and unnecessarily resent packets.

On the Enhnced Queuing DPC you can rate-limit queues before the packets are queued for output. All packets exceeding the configured rate limit are dropped, so care is required when establishing this limit. This model is also supported on IQ2 PICs. For more information about configuring CoS on IQ2 PICs, see Configuring CoS on Ethernet IQ2 Interfaces.

This example limits the transmit rate of a strict-high expedited-forwarding queue to 1 Mbps. The scheduler and scheduler map are defined, and then applied to the traffic at the [edit interfaces] and [edit class-of-service] hierarchy levels:



[edit class-of-service]
schedulers {


scheduler-1 {
transmit-rate 1m rate-limit; # This establishes the limit
priority strict-high;
}


}
scheduler-maps {


scheduler-map-1 {
forwarding-class expedited-forwarding scheduler scheduler-1;
}


}

[edit interfaces]
s0-2/2/0 {
per-unit-scheduler;
encapsulation frame-relay;


unit 0 {
dlci 1;
}


}

[edit class-o-f-service]
interfaces {


so-2/2/0 {


unit 0 {
scheduler-map scheduler-map-1;
shaping-rate 2m;
}


}


}

You can issue the following operational mode commands to verify your configuration (the first shows the rate limit in effect):

show class-of-service scheduler-map scheduler-map-name
show class-of-service interface interface-name

[Contents] [Prev] [Next] [Index] [Report an Error]