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

Excess Bandwidth and Rate Limiting on the MultiServices PIC

On the MultiServices PICs, you can limit the transmit rate of the MultiServices PIC logical interface (lsq-) in the same way as other types of queuing PICs. You can also assign a percentage of the excess bandwidth to MultiServices PIC logical interfaces. As with other types of PICs, the strict-high queue (voice) can “starve” low and medium priority queues. To prevent the strict-high queue from starving other queues, you should rate-limit the queue.

To rate-limit the MultiServices PIC logical interface, include the transmit-rate statement with the rate-limit option at the [edit class-of-service schedulers scheduler-name] hierarchy level.

You can also make the excess strict-high bandwidth available for other queues. You can split the excess bandwidth among multiple queues, but the total excess bandwidth assigned to these queues can only add up to 100 percent. The excess-bandwidth priority statement option is not supported on the MultiServices PIC. For more information about excess bandwidth sharing, see Configuring IQE PIC Excess Bandwidth Sharing.

To share excess bandwidth among MultiServices PIC logical interfaces, include the excess-rate statement at the [edit class-of-service schedulers scheduler-name] hierarchy level.

Both of these rate-limiting and excess bandwidth sharing features apply to egress traffic only, and only for per-unit schedulers. There is no hierarchical scheduler or shared-scheduler support.

You must still complete the configuration by configuring the scheduler map and applying it to the MultiServices PIC interface.

This example configures a rate limit and excess bandwidth sharing for a Multiservices PIC interface.



[edit class-of-service schedulers]
scheduler0 {
transmit-rate percent 10 rate-limit;
priority strict-high;
excess-rate percent 30;
}
scheduler1 {
transmit-rate percent 1m rate-limit;
priority high;
excess-rate percent 70;
}

[edit class-of-service scheduler-maps]
scheduler0 {
forwarding-calss ef scheduler scheduler0;
forwarding-calss af scheduler scheduler1;
}

[edit class-of-service interfaces lsq-1/3/0] 
unit 0 {
scheduler-map scheduler0;
}
unit 1 {
scheduler-map scheduler1;
}

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