Scheduling on Aggregated Ethernet Interfaces
Learn how to configure shared scheduling on aggregated Ethernet interfaces in link-protection mode or without link protection.
Scheduling on an aggregate interface allows you to configure class-of-service parameters, such as shaping and queuing, for the interface. You can configure these parameters for per-unit, hierarchical, or physical and logical interface schedulers.
Configuring Scheduler on Aggregated Ethernet Interfaces Without Link Protection
On aggregated Ethernet interfaces, you can configure scheduler in non–link-protect mode on the following platforms:
MX-Series
M120 and M320 with IQ2 PIC
T-series platforms (T620 and T320) with IQ2 PIC
The scheduler functions supported are:
Per unit scheduler
Hierarchical scheduler
Shaping at the physical interface
To configure the hierarchical scheduler on aggregated Ethernet
interfaces in the non link-protect mode, include the hierarchical-scheduler statement at the [edit interfaces aeX] hierarchy level:
[edit interfaces aeX hierarchical-scheduler]
Prior to Junos OS Release 9.6, the hierarchical scheduler mode
on these models required the aggregated-ether-options statement link-protection option. If a link-protection option
is not specified, the scheduler is configured in non-link-protect
mode.
To specify the member link bandwidth derivation based on the
equal division model (scale) or the replication model (replicate) on aggregated Ethernet interfaces, include the member-link-scheduler (scale | replicate) option at the [edit class-of-service interfaces aeX] hierarchy level. The default setting is scale.
[edit class-of-service interfaces aeX member-link-scheduler (scale | replicate)]
In link-protect mode, only one link is active at a time and the other link acts as the backup link, whereas in a non link-protect mode, all the links of the aggregate bundle are active at the same time. There is no backup link. If a link goes down or a new link is added to the bundle, traffic redistribution occurs.