Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
 

per-unit-scheduler

Syntax

Hierarchy Level

Description

Enable the association of scheduler maps with logical interfaces.

CAUTION:

Turning on per-unit scheduling causes the interface to reinitialize, which means all logical interfaces (units) on the interface are deleted and recreated.

When including the per-unit-scheduler statement, you must also include the vlan-tagging statement or the flexible-vlan-tagging statement (to apply scheduling to VLANs) or the encapsulation frame-relay statement (to apply scheduling to DLCIs) at the [edit interfaces interface-name] hierarchy level.

When including the per-unit-scheduler statement, you must also include the guaranteed-rate statement to ensure a minimum guaranteed rate for the logical interfaces.

Note:

To enable per-unit scheduling on MX80 and MX104 routers, configure the per-unit-scheduler statement at each member physical interface level of a particular aggregated Ethernet interface as well as at that aggregated Ethernet interface level. On other routing platforms, it is enough if you include this statement at the aggregated Ethernet interface level.

Note:

Per-unit scheduling is not supported on T1 interfaces configured on the Channelized OC12 IQ PIC.

Note:

On Gigabit Ethernet IQ2 and IQ2-E PICs without the per-unit-scheduler statement, the entire PIC supports 4071 VLANs and the user can configure all the VLANs on the same port.

On Gigabit Ethernet IQ2 and IQ2-E PICs with the per-unit-scheduler statement, the entire PIC supports 1024 – 2 * number of ports (1024 minus two times the number of ports), because each port is allocated two default schedulers.

Required Privilege Level

interface—To view this statement in the configuration.

interface-control—To add this statement to the configuration.

Release Information

Statement introduced before Junos OS Release 7.4.