Supported Platforms
Related Documentation
- MX Series
- Class of Service Overview for Virtual Chassis Ports
- Guidelines for Configuring Class of Service for Virtual Chassis Ports
- Additional Information
- Junos OS Class of Service Configuration Guide
Example: Configuring Class of Service for Virtual Chassis Ports on MX Series 3D Universal Edge Routers
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.
Table 1: Sample CoS Scheduler Hierarchy for Virtual Chassis Ports
Traffic Type | Queue Number | Priority | Transmit 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 master router:
- Associate forwarding classes with queue 0 through queue 3, and configure a fabric priority value for each queue.
- Configure an output traffic control profile named tcp-vcp-ifd to define traffic scheduling parameters, and associate a scheduler map named sm-vcp-ifd with 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-ifd scheduler 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, and s-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:
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 master 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-classes
- Associate 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 lowuser@host# set queue 1 assured-forwarding priority lowuser@host# set queue 2 expedited-forwarding priority highuser@host# set queue 3 network-control priority high
- Return 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# up
- Configure 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-ifd
- Apply 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-ifd
- Specify that you want to configure the scheduler map.{master:member0-re0} [edit class-of-service]user@host# edit scheduler-maps sm-vcp-ifd
- Associate 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-priorityuser@host# set forwarding-class expedited-forwarding scheduler s-high-priorityuser@host# set forwarding-class assured-forwarding scheduler s-high-weightuser@host# set forwarding-class best-effort scheduler s-low-weight
- Return 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 2
- Configure 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 10user@host# set schedulers s-high-priority priority high excess-priority high transmit-rate percent 90user@host# set schedulers s-low-priority priority lowuser@host# set schedulers s-high-weight excess-rate percent 99user@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.
If you are done configuring CoS on the master router, enter commit from configuration mode.
Related Documentation
- MX Series
- Class of Service Overview for Virtual Chassis Ports
- Guidelines for Configuring Class of Service for Virtual Chassis Ports
- Additional Information
- Junos OS Class of Service Configuration Guide
Published: 2013-02-11
Supported Platforms
Related Documentation
- MX Series
- Class of Service Overview for Virtual Chassis Ports
- Guidelines for Configuring Class of Service for Virtual Chassis Ports
- Additional Information
- Junos OS Class of Service Configuration Guide