Rate and give feedback:  Feedback Received. Thank You!

Rate and give feedback: 

X

This document helped resolve my issue

Yes No

Additional Comments

800 characters remaining

May we contact you if necessary?

Name:  

E-mail: 

Enter a valid Email ID

Need product assistance? Contact Juniper Support

Submit

This site is protected by hCaptcha and its Privacy Policy and Terms of Service apply.

English  

English

Managing Excess Bandwidth Distribution for Dynamic CoS on MIC and MIC Interfaces

Service providers often used tiered services that must utilize excess bandwidth as traffic patterns vary. By default, excess bandwidth between a configured guaranteed rate and shaping rate is shared equally among all queues with the same excess priority value, which might not be optimal for all subscribers to a service.

This feature is supported for MIC and MPC interfaces on MX Series routers.

1. Configure the parameters for the interface.
   1. Configure the guaranteed and shaping rates.
      1. Configure the guaranteed rate:
         [edit dynamic-profiles profile-name class-of-service traffic-control-profiles profile-name]user@host# set guaranteed-rate(rate | $junos-cos-guaranteed-rate) <burst-size (bytes | $junos-cos-guaranteed-rate-burst)>
      2. Configure the shaping rate:
         [edit dynamic-profiles profile-name class-of-service traffic-control-profiles profile-name]user@host# set shaping-rate (rate | $junos-cos-shaping-rate) <burst-size (bytes | $junos-cos-shaping-rate-burst)>

      Tip: On MPC/MIC interfaces, the guaranteed rate and the shaping rate share the value specified for the burst size. If the guaranteed rate has a burst size specified, it is used for the shaping rate; if the shaping rate has a burst size specified, it is used for the guaranteed rate. If you have specified a burst for both rates, the system uses the lesser of the two values.

   2. Configure a rate for excess bandwidth.

      You can configure an excess rate for all priorities of traffic:

      [edit dynamic-profiles profile-name class-of-service traffic-control-profiles profile-name]user@host# set excess-rate (percent percentage | $junos-cos-excess-rate) | proportion value )

      Optionally, you can configure an excess rate specifically for high- and low-priority traffic. When you configure the excess-rate statement for an interface, you cannot also configure the excess-rate-low and excess-rate-high statements.

      [edit dynamic-profiles profile-name class-of-service traffic-control-profiles profile-name]user@host# set excess-rate-high(percent percentage | $junos-cos-excess-rate-high) | proportion value )user@host# set excess-rate-low (percent percentage | $junos-cos-excess-rate-low) | proportion value )

      Best Practice: We recommend that you configure either a percentage or a proportion of the excess bandwidth for all schedulers with the same parent in the hierarchy. For example, if you configure interface 1.1 with twenty percent of the excess bandwidth, configure interface 1.2 with eighty percent of the excess bandwidth.

2. (Optional) Configure parameters for the queue.
   1. Configure the shaping rate.
      [edit dynamic-profiles profile-name class-of-service scheduler scheduler-name]user@host#set shaping-rate (rate | $junos-cos-scheduler-shaping-rate) <burst-size bytes>
   2. Configure the excess rate.
      [edit dynamic-profiles profile-name class-of-service scheduler scheduler-name]user@host#set excess-rate (percent percentage | percent $junos-cos-scheduler-excess-rate)
   3. (Optional) Configure the priority of excess bandwidth for the queue.
      [edit dynamic-profiles profile-name class-of-service scheduler scheduler-name]user@host#set excess-priority (low | high | $junos-cos-scheduler-excess-priority | none)

      For queues, you cannot configure the excess rate or excess priority in these cases: When the transmit-rate exact statement is configured. In this case, the shaping rate is equal to the transmit rate and the queue does not operate in the excess region. When the scheduling priority is configured as strict-high. In this case, the queue gets all available bandwidth and never operates in the excess region. Tip: By default, when traffic exceeds the shaping or guaranteed rates, the system demotes traffic configured with high or medium priority. To disable priority demotion, specify the none option. You cannot configure this option for queues configured with transmit-rate expressed as a percent and when the parent’s guaranteed rate is set to zero.