Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Configuring CoS on an MX Series Aggregation Device in Junos Fusion

 

Junos Fusion significantly expands the number of available network interfaces on an aggregation device by allowing the aggregation device to add interfaces through interconnections with satellite devices. The entire system—the interconnected aggregation device and satellite devices—is called Junos Fusion. Junos Fusion simplifies network administration by appearing in the network topology as a single device, and the single device is managed from a single IP address.

This topic describes how to configure CoS on the different types of ports in Junos Fusion.

This topic covers:

Configuring Behavior Aggregate Classifiers on Satellite Device Extended Ports

Normally, you apply a behavior aggregate (BA) classifier to a logical interface on an MX Series device at the [edit class-of-service interfaces interface-name unit logical-unit-number] hierarchy level. When traffic from a satellite device extended port reaches the aggregation device, the BA classifier configured for the logical interface level of the satellite device extended port is applied the same as it is for traffic from other non-extended ports to help determine the forwarding class of the traffic; policers and multifield classifiers can also factor in determining the forwarding class of the traffic. When the aggregation devices sends the traffic out to the satellite device, the forwarding class is carried in the 801.2BR header. The satellite device then uses the forwarding class to select the output queue at the egress extended port.

You can also apply a BA classifier at the physical interface level of an extended port. This classifier is used to determine the output queue at the uplink port of the satellite device.

Note

IP precedence classifiers are not supported on extended ports at the physical interface level. DSCP classifiers are supported, however.

Note

You cannot apply a physical interface-level classifier on an MX Series local port.

To add a behavior aggregate classifier to the physical interface level of a satellite device extended port in Junos Fusion:

  1. Define the classifier.
  2. Apply the classifier to the physical extended port.
  3. Commit the changes and then confirm the configuration.

In the above configuration example, packets entering port xe-100/0/33 with a DSCP value of 001010 will be assigned a forwarding class of best-effort-3 to select the output queue at the uplink port as the packet travels from the satellite device to the aggregation device.

Configuring Rewrite Rules on Satellite Device Extended Ports

You apply rewrite rules to logical interfaces on satellite device extended ports.

To add a rewrite rule to a satellite device extended port in a Junos Fusion:

  1. Define the rewrite rule.
  2. Apply the rewrite rule to a logical interface.
  3. Commit the changes and then confirm the configuration.

In Junos OS, rewrite rules only look at the forwarding class and packet loss priority of the packet (as assigned by a behavior aggregate or multifield classifier at ingress), not at the incoming CoS value, to determine the CoS value to write to the packet header at egress. The above configuration means that, for any packet exiting the xe-108/0/47.0 interface that has a forwarding class of best-effort and a packet loss priority of low, the ieee-802.1 CoS value will be rewritten to 010.

Configuring CoS Hierarchical Port Scheduling with Enhanced Transmission Selection on Satellite Device Ports

You can configure enhanced transmision selection (ETS) for both extended ports and uplink ports on satellite devices. The configuration is done on the aggregation device. To configure ETS for a satellite device port in Junos Fusion:

  1. Define the traffic control profiles.
  2. Define the forwarding class sets.
  3. Apply the forwarding class sets to a satellite device port.
  4. Commit the changes and then confirm the configuration.
  5. Run show interfaces queue egress interface name to show the statistics of transmitted and dropped packets for each queue on the satellite device port.
    Note

    Queued statistics for each queue are not available for satellite device ports and will always show 0.

Changing the Default Scheduling Policy on an Aggregated Device Cascade Port

When a cascade port is created, two logical interfaces are automatically created:

  • One in-band management logical interface (assigned unit 32769) for traffic that only flows between the aggregation device and the satellite devices, such as keepalives, for provisioning information, and for software updates.

  • One for data logical interface (assigned unit 32770) for regular traffic that flows into and out of Junos Fusion.

Let’s say, for example, that interface xe-0/0/1 is configured as a cascade port. The command show interfaces xe-0/0/1 terse produces output similar to the following:

The control logical interface (unit 32769) is automatically assigned an internal traffic control profile (__cp_control_tc_prof) that guarantees 50 Mbps of bandwidth for the logical interface, a 10 percent shaping rate, and the default scheduling policy. The default scheduling policy is applied to the data logical interface. For example:

and:

You can create custom forwarding classes and schedulers for the data logical interface by applying a customer scheduler map to that logical interface. For example, to apply a customer scheduler policy to the data logical interface:

  1. Create customer schedulers.
  2. Create a scheduler map.
  3. Apply the scheduler map to the data logical interface.
  4. Commit the changes and then confirm the configuration.
  5. Verify your changes.

    and: