Configuring Traffic Control Profiles for Shared Scheduling and Shaping

date_range 15-Mar-23

arrow_backward

arrow_forward

Shared scheduling and shaping allows you to allocate separate pools of shared resources to subsets of logical interfaces belonging to the same physical port. You configure shared scheduling and shaping by first creating a traffic-control profile, which specifies a shaping rate and references a scheduler map. You must then share this set of shaping and scheduling resources by applying an instance of the traffic-control profile to a subset of logical interfaces. You can apply a separate instance of the same (or a different) traffic-control profile to another subset of logical interfaces, thereby allocating separate pools of shared resources.

Before you start this procedure:

Make sure you define a scheduler map. For information about configuring schedulers and scheduler maps, see Configuring Schedulers and Configuring Scheduler Maps. Gigabit Ethernet IQ2 interfaces support up to eight forwarding classes and queues.

To configure a traffic-control profile, perform the following steps:

Create the traffic control profile and configure a shaping rate for it.
```
[edit]
user@host# edit class-of-service traffic-control-profiles profile-name
user@host# set shaping-rate (percent percentage | rate)
```
You can configure the shaping rate as a percentage from 1 through 100 or as an absolute rate from 1000 through 6,400,000,000,000 bits per second (bps). The shaping rate corresponds to a peak information rate (PIR). For more information, see Oversubscribing Interface Bandwidth.
Define an association between the traffic-control profile and a previously configured scheduler map by including the scheduler-map statement at the [edit class-of-service traffic-control-profiles profile-name] hierarchy level.
```
[edit class-of-service traffic-control-profiles profile-name]
user@host# set scheduler-map map-name;
```
Configure the delay-buffer rate.
If you do not include this statement, the delay-buffer rate is based on the guaranteed rate if one is configured, or on the shaping rate if no guaranteed rate is configured.
```
[edit class-of-service traffic-control-profiles profile-name]
user@host# set delay-buffer-rate (percent percentage | rate)
```
You can configure the delay-buffer rate as a percentage from 1 through 100 or as an absolute rate from 1000 through 6,400,000,000,000 bits per second. The delay-buffer rate controls latency. For more information, see Oversubscribing Interface Bandwidth and Providing a Guaranteed Minimum Rate.
Configure a guaranteed minimum rate for the traffic-control profile.
```
[edit class-of-service traffic-control-profiles profile-name]
user@host# set guaranteed-rate (percent percentage | rate)
```
You can configure the guaranteed rate as a percentage from 1 through 100 or as an absolute rate from 1000 through 6,400,000,000,000 bps. The guaranteed rate corresponds to a committed information rate (CIR). For more information, see Providing a Guaranteed Minimum Rate.

You must now share an instance of the traffic-control profile.
Enable shared-scheduling on the interface.
```
[edit]
user@host# edit interfaces interface-name
user@host# set shared-scheduler
```
This statement enables logical interfaces belonging to the same physical port to share one set of shaping and scheduling resources.

Note:
On each physical interface, the shared-scheduler and per-unit-scheduler statements are mutually exclusive. Even so, you can configure one logical interface for each shared instance. This effectively provides the functionality of per-unit scheduling.

(Optional) Apply the traffic-control profile to an input interface.

content_copy zoom_out_map
[edit]
user@host# edit class-of-service interfaces interface-name unit logical-unit-number
user@host# set input-traffic-control-profile profile-name shared-instance instance-name

These statements are explained in Step 7.

(Optional) Apply the traffic-control profile to an output interface.
```
[edit]
user@host# edit class-of-service interfaces interface-name unit logical-unit-number
user@host# set output-traffic-control-profile profile-name shared-instance instance-name
```
The profile name references the traffic-control profile you configured in Step 1 through Step 4. The shared-instance name does not reference a configuration. It can be any text string you wish to apply to multiple logical interfaces that you want to share the set of resources configured in the traffic-control profile. Each logical interface shares a set of scheduling and shaping resources with other logical interfaces that are on the same physical port and that have the same shared-instance name applied.

This concept is demonstrated in Example: Configuring Shared Resources on Ethernet IQ2 Interfaces.

Note:
You cannot include the output-traffic-control-profile statement in the configuration if either the scheduler-map or shaping-rate statement is included in the logical interface configuration.

arrow_backward PREVIOUS Applying Scheduler Maps to Physical Interfaces

NEXT arrow_forward Configuring an Input Scheduler on an Interface

Class of Service User Guide (Routers and EX9200 Switches)

Configuring Traffic Control Profiles for Shared Scheduling and Shaping

Stay in touch

Helped me install or use the product
Accelerated my deployment

Discuss the product with a co-worker
Make a purchase inquiry

Class of Service User Guide (Routers and EX9200 Switches)

Configuring Traffic Control Profiles for Shared Scheduling and Shaping

Related Documentation

Stay in touch