ON THIS PAGE
Example: Configuring Class of Service for Virtual Chassis Ports on MX Series 5G Universal Routing Platforms
This example illustrates a typical class of service (CoS) configuration that you might want to use for the Virtual Chassis ports in an MX Series Virtual Chassis.
Requirements
Before you begin:
Configure a Virtual Chassis consisting of two MX Series routers.
Overview
By default, all Virtual Chassis ports in an MX Series Virtual Chassis use a default CoS configuration specifically tailored for Virtual Chassis ports. The default configuration, which applies to all Virtual Chassis ports in the Virtual Chassis, includes classifiers, forwarding classes, rewrite rules, and schedulers. This default CoS configuration prioritizes internal Virtual Chassis Control Protocol (VCCP) traffic that traverses the Virtual Chassis port interfaces, and prioritizes control traffic over user traffic on the Virtual Chassis ports. In most cases, the default CoS configuration is adequate for your needs without requiring any additional CoS configuration.
In some cases, however, you might want to customize the traffic-control
profile configuration on Virtual Chassis ports. For example, you might
want to assign different priorities and excess rates to different
forwarding classes. To create a nondefault CoS configuration, you
can create an output traffic-control profile that defines a set of
traffic scheduling resources and references a scheduler map. You then
apply the output traffic-control profile to all Virtual Chassis port
interfaces at once by using vcp-* as the interface name
representing all Virtual Chassis ports. You cannot configure CoS for
Virtual Chassis ports on an individual basis.
Table 1 shows the nondefault CoS scheduler hierarchy configured in this example for the Virtual Chassis ports.
Traffic Type |
Queue Number |
Priority |
Transmit Rate/Excess Rate |
|---|---|---|---|
Network control (VCCP traffic) |
3 |
Medium |
90% |
Expedited forwarding (voice traffic) |
2 |
High |
10% |
Assured forwarding (video traffic) |
1 |
Excess Low |
99% |
Best effort (data traffic) |
0 |
Excess Low |
1% |
In this example, you create a nondefault CoS configuration for Virtual Chassis ports by completing the following tasks on the Virtual Chassis primary router:
Associate forwarding classes with
queue 0throughqueue 3, and configure a fabric priority value for each queue.Configure an output traffic control profile named
tcp-vcp-ifdto define traffic scheduling parameters, and associate a scheduler map namedsm-vcp-ifdwith the traffic control profile.Apply the output traffic-control profile to the
vcp-*interface, which represents all Virtual Chassis port interfaces in the Virtual Chassis.Associate the
sm-vcp-ifdscheduler map with the forwarding classes and scheduler configuration.Configure the parameters for schedulers
s-medium-priority,s-high-priority,s-low-priority,s-high-weight, ands-low-weight.
Configuration
CLI Quick Configuration
To quickly create a nondefault CoS configuration for Virtual Chassis ports, copy the following commands and paste them into the router terminal window:
[edit] set class-of-service forwarding-classes queue 0 best-effort set class-of-service forwarding-classes queue 0 priority low set class-of-service forwarding-classes queue 1 assured-forwarding set class-of-service forwarding-classes queue 1 priority low set class-of-service forwarding-classes queue 2 expedited-forwarding set class-of-service forwarding-classes queue 2 priority high set class-of-service forwarding-classes queue 3 network-control set class-of-service forwarding-classes queue 3 priority high set class-of-service traffic-control-profiles tcp-vcp-ifd scheduler-map sm-vcp-ifd set class-of-service interfaces vcp-* output-traffic-control-profile tcp-vcp-ifd set class-of-service scheduler-maps sm-vcp-ifd forwarding-class network-control scheduler s-medium-priority set class-of-service scheduler-maps sm-vcp-ifd forwarding-class expedited-forwarding scheduler s-high-priority set class-of-service scheduler-maps sm-vcp-ifd forwarding-class assured-forwarding scheduler s-high-weight set class-of-service scheduler-maps sm-vcp-ifd forwarding-class best-effort scheduler s-low-weight set class-of-service schedulers s-medium-priority transmit-rate percent 90 set class-of-service schedulers s-medium-priority priority medium-high set class-of-service schedulers s-medium-priority excess-priority high set class-of-service schedulers s-high-priority transmit-rate percent 10 set class-of-service schedulers s-high-priority priority high set class-of-service schedulers s-high-priority excess-priority high set class-of-service schedulers s-low-priority priority low set class-of-service schedulers s-high-weight excess-rate percent 99 set class-of-service schedulers s-low-weight excess-rate percent 1
Procedure
Step-by-Step Procedure
To create a nondefault CoS configuration for Virtual Chassis ports in an MX Series Virtual Chassis:
Log in to the console on the primary router of the Virtual Chassis.
Specify that you want to configure CoS forwarding classes.
{master:member0-re0} [edit] user@host# edit class-of-service forwarding-classesAssociate a forwarding class with each queue name and number, and configure a fabric priority value for each queue.
{master:member0-re0} [edit class-of-service forwarding-classes] user@host# set queue 0 best-effort priority low user@host# set queue 1 assured-forwarding priority low user@host# set queue 2 expedited-forwarding priority high user@host# set queue 3 network-control priority highReturn to the
[edit class-of-service]hierarchy level to configure an output traffic-control profile.{master:member0-re0} [edit class-of-service forwarding-classes] user@host# upConfigure an output traffic-control profile and associate it with a scheduler map.
{master:member0-re0} [edit class-of-service] user@host# set traffic-control-profiles tcp-vcp-ifd scheduler-map sm-vcp-ifdApply the output traffic-control profile to all Virtual Chassis port interfaces in the Virtual Chassis.
{master:member0-re0} [edit class-of-service] user@host# set interfaces vcp-* output-traffic-control-profile tcp-vcp-ifdSpecify that you want to configure the scheduler map.
{master:member0-re0} [edit class-of-service] user@host# edit scheduler-maps sm-vcp-ifdAssociate the scheduler map with the scheduler configuration and forwarding classes.
{master:member0-re0} [edit class-of-service scheduler-maps sm-vcp-ifd] user@host# set forwarding-class network-control scheduler s-medium-priority user@host# set forwarding-class expedited-forwarding scheduler s-high-priority user@host# set forwarding-class assured-forwarding scheduler s-high-weight user@host# set forwarding-class best-effort scheduler s-low-weightReturn to the
[edit class-of-service]hierarchy level to configure the schedulers.{master:member0-re0} [edit class-of-service scheduler-maps sm-vcp-ifd] user@host# up 2Configure parameters for the schedulers.
{master:member0-re0} [edit class-of-service] user@host# set schedulers s-medium-priority priority medium-high excess-priority high transmit-rate percent 90 user@host# set schedulers s-high-priority priority high excess-priority high transmit-rate percent 10 user@host# set schedulers s-low-priority priority low user@host# set schedulers s-high-weight excess-rate percent 99 user@host# set schedulers s-low-weight excess-rate percent 1
Results
From the [edit class-of-service] hierarchy
level in configuration mode, confirm the results of your configuration
by issuing the show statement. If the output does not display
the intended configuration, repeat the configuration instructions
in this example to correct it.
{master:member0-re0} [edit class-of-service]
user@host# show
forwarding-classes {
queue 0 best-effort priority low;
queue 1 assured-forwarding priority low;
queue 2 expedited-forwarding priority high;
queue 3 network-control priority high;
}
traffic-control-profiles {
tcp-vcp-ifd {
scheduler-map sm-vcp-ifd;
}
}
interfaces {
vcp-* {
output-traffic-control-profile tcp-vcp-ifd;
}
}
scheduler-maps {
sm-vcp-ifd {
forwarding-class network-control scheduler s-medium-priority;
forwarding-class expedited-forwarding scheduler s-high-priority;
forwarding-class assured-forwarding scheduler s-high-weight;
forwarding-class best-effort scheduler s-low-weight;
}
}
schedulers {
s-medium-priority {
transmit-rate percent 90;
priority medium-high;
excess-priority high;
}
s-high-priority {
transmit-rate percent 10;
priority high;
excess-priority high;
}
s-low-priority {
priority low;
}
s-high-weight {
excess-rate percent 99;
}
s-low-weight {
excess-rate percent 1;
}
}
If you are done configuring CoS on the primary router, enter commit from configuration mode.