Per-Priority Shaping on MIC and MPC Interfaces Overview

There are five scheduler priorities:

• Guaranteed high (GH)

• Guaranteed medium (GM)

• Guaranteed low (GL)

• Excess high (EH)

• Excess low (EL)

The five scheduler priorities support a shaping rate for each priority:

• Shaping rate priority high (GH)

• Shaping rate priority medium (GM)

• Shaping rate priority low (GL)

• Shaping rate excess high (EH)

• Shaping rate excess low (EL)

On MPC7E (MPC7E-MRATE and MPC7E-10G), MPC8E (MX2K-MPC8E), MPC9E(MX2K-MPC9E), and PTX series, when you enable the enhanced priority mode feature, additional scheduler priorities and shaping rates are supported. For more information on the enhanced priority mode feature, see enhanced-priority-mode.

The additional scheduler priorities supported when you enable the enhanced priority mode feature:

• Shaping rate priority strict high (GHL)

• Shaping rate priority medium low (GML)

• Shaping rate excess medium high (EMH)

• Shaping rate excess medium low (EML)

When you enable the enhanced priority mode feature, the queue priorities are mapped to the priorities of the MPCs :

If each service is represented by a forwarding class queued at a separate priority, then assigning a per-priority shaping rate to higher priority services accomplishes the goal of preventing the starvation of lower priority services.

To configure per-priority shaping rates, include the shaping-rate-excess-high rate <burst-size burst>, shaping-rate-excess-low rate <burst-size burst>, shaping-rate-priority-high rate <burst-size burst>, shaping-rate-priority-low rate <burst-size burst>, or shaping-rate-priority-medium rate <burst-size burst> at the [edit class-of-service traffic-control-profiles tcp-name] hierarchy level and apply the traffic control profile at the [edit interfaces] hierarchy level. You can specify the rate in absolute values, or by using k (kilo-), m (mega-) or g (giga-) units.

You can include one or more of the per-priority shaping statements in a traffic control profile:

There are several important points about per-priority shaping rates:

• Per-priority shaping rates are only supported on MIC and MPC interfaces (with the exception of the 10-Gigabit Ethernet MPC with SFP+).

• Per-priority shaping is only available for level 1 and level 2 scheduler nodes. (For more information on hierarchical schedulers, see Configuring Hierarchical Schedulers for CoS.)

• Per-priority shaping rates are supported when level 1 or level 2 scheduler nodes have static or dynamic interfaces above them.

• Per-priority shaping rates are supported on aggregated Ethernet (AE) interfaces.

• Per-priority shaping rates are only supported in traffic control profiles.

Per-priority shaping rates can be helpful when the MX Series 5G Universal Routing Platform is in a position between subscriber traffic on an access network and the carrier network, playing the role of a broadband services router. In that case, the MX Series router provides quality-of-service parameters on the subscriber access network so that each subscriber receives a minimum bandwidth (determined by the guaranteed rate) and a maximum bandwidth (determined by the shaping rate). This allows the devices closer to the carrier network to operate more efficiently and more simply and reduces operational network expenses because it allows more centralized network management.

One architecture for using per-priority shaping on the MX Series router is shown in Figure 1. In the figure, subscribers use residential gateways with various traffic classes to support voice, video, and data services. The MX Series router sends this traffic from the carrier network to the digital subscriber line access multiplexer (DSLAM) and from the DSLAM on to the residential gateway devices.

Figure 1: Architecture for MIC and MPC Interface Per-Priority Shaping

One way that the MX Series router can provide service classes for this physical network topology is shown in Figure 2. In the figure, services such as voice and video are placed in separate forwarding classes and the services at different priority levels. For example:

• All expedited-forwarding queues are voice services at a priority level of guaranteed high.

• All assured-forwarding queues are video services at a priority level of guaranteed medium.

• All better-than-best-effort queues are services at a priority level of excess high.

• All best-effort queues are services at a priority level of excess low.

Figure 2: Scheduling Hierarchy for Per-Priority Shaping

Aggregated voice traffic in this topology is shaped by applying a high-priority shaper to the port. Aggregated video traffic is shaped in the same way by applying a medium-priority shaper to the port. As long as the sum of the high- and medium-priority shapers is less than the port speed, some bandwidth is reserved for best-effort and better-than-best-effort traffic. So assured-forwarding and expedited-forwarding voice and video cannot starve best-effort and better-than-best-effort data services. One possible set of values for high-priority (guaranteed high) and medium-priority (guaranteed medium) traffic is shown in Figure 2.

Per-priority shaping statements:

Apply (attach) the traffic control profile to the physical interface (port) at the [edit class-of-services interfaces] hierarchy level:

Traffic control profiles with per-priority shaping rates can only be attached to interfaces that support per-priority shaping.

You can apply per-priority shaping to levels other than the level 1 physical interface (port) of the scheduler hierarchy. Per-priority shaping can also be applied at level 2, the interface set level, which would typically represent the digital subscriber link access multiplexer (DSLAM). At this level you could use per-priority shaping to limit to total amount of video traffic reaching a DSLAM, for example.

You apply (attach) the traffic control profile to an interface set at the [edit class-of-services interfaces] hierarchy level:

You can configure per-priority shaping for the traffic remaining with the output-traffic-control-profile-remaining statement on a physical port (a level 2 node) but not for an interface set (a level 3 node).