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

Configuring Strict-High Priority on J-series Platforms

On J-series Services Routers, you can configure one queue per interface to have strict-high priority, which causes delay-sensitive traffic, such as voice traffic, to be dequeued and forwarded with minimum delay. Packets that are queued in a strict priority queue are dequeued before packets in other queues, including high priority queues.

The JUNOS software implementation of strict priority queuing on J-series platforms allows you to configure traffic policing that prevents lower-priority queues from being starved. The strict priority queue does not cause starvation of other queues because the configured policer allows the queue to exceed the configured bandwidth only when other queues are not congested. If the interface is congested, the software polices strict priority queues to the configured bandwidth.

To prevent queue starvation of other queues, you must configure an egress policer that defines a limit for the amount of traffic that the queue can service. The software services all traffic in the strict priority queue that is under the defined limit. When strict priority traffic exceeds the limit, the policer marks the traffic in excess of the limit as out-of-profile. If the output port is congested, the software drops out-of-profile traffic.

If you wish, you can configure a second policer with an upper limit. When strict priority traffic exceeds the upper limit, the software drops the traffic in excess of the upper limit, regardless of whether the output port is congested. This upper-bound policer is not a requirement for preventing starvation of the lower priority queues. The policer for the lower bound, which marks the packets as out-of-profile, is sufficient to prevent starvation of other queues.

Following is a step-by-step description of how strict priority queuing and policing works on J-series Services Routers:

  1. To identify delay-sensitive traffic, configure a behavior aggregate (BA) or multifield (MF) classifier.
  2. To minimize delay, assign all delay-sensitive packets to the strict priority queue.
  3. To prevent starvation on other queues, configure a policer that checks the data stream entering the strict priority queue. The policer defines a lower bound, marks the packets that exceed the lower bound as out-of-profile, and drops the out-of-profile packets if the physical interface is congested. If there is no congestion, the software forwards all packets, including the out-of-profile packets.
  4. Optionally, you can configure another policer that defines an upper bound and drops the packets that exceed the upper bound, regardless of congestion on the physical interface.

To configure strict priority queuing and prevent starvation of other queues, include the priority strict-high statement at the [edit class-of-service schedulers scheduler-name] hierarchy level and the if-exceeding and then out-of-profile statements at the [edit firewall policer policer-name] hierarchy level:

[edit class-of-service schedulers scheduler-name]
priority strict-high;
 
[edit firewall policer policer-name]
if-exceeding {
bandwidth-limit bps;
bandwidth-percent number;
burst-size-limit bytes;
}
then out-of-profile;

To verify your configuration, you can issue the following operational mode commands:

Use a BA classifier to classify traffic based on the IP precedence of the packet. The classifier defines IP precedence value 101 as voice traffic and 000 as data traffic.

Configure two policers on the output interface that identify excess voice traffic belonging to the voice-class forwarding class. If the traffic exceeds 1 Mbps, a policer marks the traffic in excess of 1 Mbps as out-of-profile. If the traffic exceeds 2 Mbps, the second policer discards the traffic in excess of 2 Mbps.

Configure a BA Classifier

class-of-service {
classifiers {
inet-precedence corp-traffic {
forwarding-class voice-class {
loss-priority low code-points 101;
}
forwarding-class data-class {
loss-priority high code-points 000;
}
}
}

Configure the Forwarding Classes

forwarding-classes {
queue 0 voice-class;
queue 1 data-class;
}

Configure the Scheduler Map

scheduler-maps {
corp-map {
forwarding-class voice-class scheduler voice-sched;
forwarding-class data-class scheduler data-sched;
}
}

Configure the Schedulers

schedulers {
voice-sched {
priority strict-high;
}
data-sched {
priority low;
}
}

Apply the BA Classifier to an Input Interface

interfaces {
fe-0/0/0 {
unit 0 {
classifiers {
inet-precedence corp-traffic;
}
}
}

Apply the Scheduler Map to an Output Interface

e1-1/0/1 {
scheduler-map corp-map;
}
}
}

Configure Two Policers

firewall {
policer voice-excess {
if-exceeding {
bandwidth-limit 1m;
burst-size-limit 200k;
}
then out-of-profile;
}
policer voice-drop {
if-exceeding {
bandwidth-limit 2m;
burst-size-limit 200k;
}
then discard;
}
filter voice-term {
term 01 {
from {
forwarding-class voice-class;
}
then {
policer voice-drop;
next term;
}
}
term 02 {
from {
forwarding-class voice-class;
}
then policer voice-excess;
}
term 03 {
then accept;
}
}
}

Apply the Filter to the Output Interface

interfaces {
e1-1/0/1 {
unit 0 {
family inet {
filter {
output voice-term;
}
address 11.1.1.1/24;
}
}
}
}
[Contents] [Prev] [Next] [Index] [Report an Error]

Copyright © 2008, Juniper Networks, Inc. All rights reserved. Trademark Notice.