beautypg.com

10 queue-rate – CANOGA PERKINS 9175 Command Reference User Manual

Page 582

background image

CanogaOS Command Reference

32-7

Network Egress Policy Configuration

Usage

1. The total-rate should be at least be the sum rate of queue-rate of queue 1 - queue 3.

2. A network egress policy can be associated with multiple EVCs, the total-rate is not to limit the total

traffic of all EVCs, but to rate-limit the maximum allowed bandwidth at egress NNI for each EVC

separately.

Examples

In the following example, the total-rate command is used to shape a EVC’s total traffic in conforming to

20Mbps at the egress NNI direction.

Switch(config)# qos net-egress evc110-policy-at-egress-nni

Switch(config-net-egress)# total-rate 20000

Related Commands

None

32.10 queue-rate

Use this command to configure queue shaping rates for the three high priority queues, i.e., queue 1 -

queue 3, in network egress policy. The queue shaping rate-limits the de-queue rate for each queue of an

EVC at egress NNI direction. Queue 0, the lowest priority queue, always be given the least chance to be

scheduled, is not necessary to be configured with a queue shaping rate because it is only allowed to

utilize the residual bandwidth after the high priority queues consuming the configured bandwidth.

Command Syntax

queue-rate RATE1 RATE2 RATE3

RATE1: The shaping rate of queue 1, whose value ranges from 0 to 1000, 000 kbps.

RATE2: The shaping rate of queue 2, whose value ranges from 0 to 1000, 000 kbps.

RATE3: The shaping rate of queue 3, whose value ranges from 0 to 1000, 000 kbps.

Command Mode

Network Egress Policy Configuration

Usage

1. The sum queue-rate of queue 1 - queue 3 can not be greater than the total-rate.

2. Each queue will be assigned with a class. Queues in the highest class will be given the most chance

to be scheduled, and following down, queues in the lowest class can only use the residual bandwidth

after the queues in higher classes consuming the bandwidth.

3. In network egress policy, queue i is bound to class i internally. Unlike the interface queues, this

queue-class relationship is immutable and not allowed to be altered.