You can configure class of service (CoS) for all subscribers
that successfully establish connection to the broadband network. After
you create the CoS profile, you can attach it to subscriber interfaces
using a dynamic profile.
Configuring a CoS profile includes
the following general steps:
Configuring forwarding classes.
Configuring schedulers.
Configuring scheduler maps.
Configuring classifiers.
Configuring CoS interface properties.
In this configuration, we configure three forwarding
classes, each with its own scheduler, and an IP precedence classifier
for the traffic destined for the access network. Table 6 provides an overview of the queue
configuration:
Table 6: Class of Service
Queue Configuration
Differentiated Services Classification
Bandwidth
Priority
Purpose
Expedited forwarding (EF)
128 Kbps
strict high
voice traffic
Assured forwarding (AF)
29.4 Mbps
low
video traffic
Best effort (BE)
remainder
low
data traffic
Configuring CoS Fowarding Classes
Forwarding classes identify output queues
for packets. For a classifier to assign an output queue to each packet,
it must associate the packet with one of the following forwarding
classes:
Assured forwarding (AF)—Provides a group of values
you can define and includes four subclasses: AF1, AF2, AF3, and AF4,
each with three drop probabilities: low, medium, and high.
Best effort (BE)—Provides no service profile. For
the BE forwarding class, loss priority is typically not carried in
a class-of-service (CoS) value, and random early detection (RED) drop
profiles are more aggressive.
Network control (NC)—This class is typically high
priority because it supports protocol control.
Note:
The MX-series router enables you to configure up to eight
forwarding class queues.
CoS schedulers define the properties of output queues.
These properties can include the amount of interface bandwidth assigned
to the queue, the size of the memory buffer allocated for storing
packets, the priority of the queue, and the random early detection
(RED) drop profiles associated with the queue.
To configure CoS schedulers for
the existing queues:
Create a scheduler and name it for the best effort traffic.
Configuring CoS interface properties
enables the router to throttle and classify the traffic from the Internet
that is sent to subscriber local loops. Limiting the traffic to the
access network ensures that the traffic sent to the subscriber local
loops does not exceed the current data transmission rate of those
lines. Limiting traffic also ensures that changes to subscriber local
loop speeds do not cause bandwidth contention at the subscriber’s
residential gateway. You apply the classifier to the core-facing interface
to classify incoming traffic for the queues you are using in the access
network.
To configure CoS interfaces:
Edit the core CoS interface you want to configure.