- play_arrow Understanding How Virtual Chassis Provides Interchassis Redundancy
- play_arrow Understanding How a Virtual Chassis Works
- play_arrow Configuring a Virtual Chassis
- Configuring Interchassis Redundancy for MX Series 5G Universal Routing Platforms Using a Virtual Chassis
- Preparing for a Virtual Chassis Configuration
- Creating and Applying Configuration Groups for a Virtual Chassis
- Configuring Preprovisioned Member Information for a Virtual Chassis
- Configuring Enhanced IP Network Services for a Virtual Chassis
- Configuring Enhanced LAN Mode for a Virtual Chassis
- Enabling Graceful Routing Engine Switchover and Nonstop Active Routing for a Virtual Chassis
- Configuring Member IDs for a Virtual Chassis
- Configuring an MX2020 Member Router in an Existing MX Series Virtual Chassis
- Switching the Global Primary and Backup Roles in a Virtual Chassis Configuration
- Deleting Member IDs in a Virtual Chassis Configuration
- Example: Replacing a Routing Engine in a Virtual Chassis Configuration for MX Series 5G Universal Routing Platforms
- Deleting a Virtual Chassis Configuration for MX Series 5G Universal Routing Platforms
- Example: Deleting a Virtual Chassis Configuration for MX Series 5G Universal Routing Platforms
- Upgrading an MX Virtual Chassis SCB or SCBE to SCBE2
- play_arrow Configuring Virtual Chassis Ports to Interconnect Member Devices
- play_arrow Configuring Locality Bias to Conserve Bandwidth on Virtual Chassis Ports
- play_arrow Configuring Redundancy Mechanisms on Aggregated Ethernet Interfaces in a Virtual Chassis
- Redundancy Mechanisms on Aggregated Ethernet Interfaces in a Virtual Chassis
- Configuring Module Redundancy for a Virtual Chassis
- Configuring Chassis Redundancy for a Virtual Chassis
- Multichassis Link Aggregation in a Virtual Chassis
- Targeted Traffic Distribution on Aggregated Ethernet Interfaces in a Virtual Chassis
- Understanding Support for Targeted Distribution of Logical Interface Sets of Static VLANs over Aggregated Ethernet Logical Interfaces
- play_arrow Upgrading Junos OS in a Virtual Chassis Configuration for MX Series 5G Universal Routing Platforms by Rebooting the Routing Engines
- play_arrow Upgrading Junos OS in an MX Series Virtual Chassis by Performing a Unified In-Service Software Upgrade (ISSU)
- play_arrow Upgrading Junos OS in an MX Series Virtual Chassis by Performing a Sequential Upgrade
- play_arrow Monitoring an MX Series Virtual Chassis
- Accessing the Virtual Chassis Through the Management Interface
- Verifying the Status of Virtual Chassis Member Routers or Switches
- Verifying the Operation of Virtual Chassis Ports
- Verifying Neighbor Reachability for Member Routers or Switches in a Virtual Chassis
- Verifying Neighbor Reachability for Hardware Devices in a Virtual Chassis
- Determining GRES Readiness in a Virtual Chassis Configuration
- Viewing Information in the Virtual Chassis Control Protocol Adjacency Database
- Viewing Information in the Virtual Chassis Control Protocol Link-State Database
- Viewing Information About Virtual Chassis Port Interfaces in the Virtual Chassis Control Protocol Database
- Viewing Virtual Chassis Control Protocol Routing Tables
- Viewing Virtual Chassis Control Protocol Statistics for Member Devices and Virtual Chassis Ports
- Verifying and Managing the Virtual Chassis Heartbeat Connection
- Inline Flow Monitoring for Virtual Chassis Overview
- Managing Files on Virtual Chassis Member Routers or Switches
- Virtual Chassis SNMP Traps
- Virtual Chassis Slot Number Mapping for Use with SNMP
- Example: Determining Member Health Using an MX Series Virtual Chassis Heartbeat Connection with Member Routers in the Same Subnet
- Example: Determining Member Health Using an MX Series Virtual Chassis Heartbeat Connection with Member Routers in Different Subnets
- play_arrow Tracing Virtual Chassis Operations for Troubleshooting Purposes
- Tracing Virtual Chassis Operations for MX Series 5G Universal Routing Platforms
- Configuring the Name of the Virtual Chassis Trace Log File
- Configuring Characteristics of the Virtual Chassis Trace Log File
- Configuring Access to the Virtual Chassis Trace Log File
- Using Regular Expressions to Refine the Output of the Virtual Chassis Trace Log File
- Configuring the Virtual Chassis Operations to Trace
- play_arrow Configuration Statements and Operational Commands
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.
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.
content_copy zoom_out_map{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.
content_copy zoom_out_map{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.content_copy zoom_out_map{master:member0-re0} [edit class-of-service forwarding-classes] user@host# upConfigure an output traffic-control profile and associate it with a scheduler map.
content_copy zoom_out_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.
content_copy zoom_out_map{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.
content_copy zoom_out_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.
content_copy zoom_out_map{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.content_copy zoom_out_map{master:member0-re0} [edit class-of-service scheduler-maps sm-vcp-ifd] user@host# up 2Configure parameters for the schedulers.
content_copy zoom_out_map{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.
