Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?


Configuring an Input Scheduler on an Interface

As an alternative to shared input traffic-control profiles, you can configure each interface to use its own input scheduler. For each physical interface, you can apply an input scheduler map to the physical interface or its logical interfaces, but not both.

Input scheduler maps are supported on the following Ethernet interfaces:

  • IQ2 and IQ2E PICs

  • DPCs and MPCs that support Enhanced Queuing (Q/EQ)

  • MX80 with support for per-VLAN queuing

Before you start this procedure:

  • Define a scheduler map at the [edit class-of-service scheduler-maps] hierarchy level.

To configure a separate input scheduler on the physical interface:

  • Specify the name of the physical interface and the scheduler map.

To configure a separate input scheduler on a logical interface:

  1. Specify the name of the physical and logical interface and scheduler map.
  2. Enable the association of the scheduler map name and interface.

    The per-unit-scheduler statement enables one set of output queues for each logical interface configured under the physical interface.

    On Gigabit Ethernet IQ2 PIC interfaces, configuration of the per-unit-scheduler statement requires that you configure VLAN tagging also. When you include the per-unit-scheduler statement, the maximum number of VLANs supported is 768 on a single-port Gigabit Ethernet IQ PIC. On a dual-port Gigabit Ethernet IQ PIC, the maximum number is 384.