Configuring a Separate Input Scheduler for Each 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.
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 separate input scheduler on the physical interface, include the input-scheduler-map statement at the [edit class-of-service interfaces interface-name] hierarchy level:
To configure a separate input scheduler on a logical interface, perform the following steps:
- Include the input-scheduler-map statement at
the [edit class-of-service interfaces interface-name unit logical-unit-number] hierarchy level:[edit class-of-service interfaces interface-name unit logical-unit-number]input-scheduler-map map-name;
- For the corresponding physical interface, you must also
include the per-unit-scheduler statement at the [edit interfaces interface-name] hierarchy level:[edit interfaces interface-name]per-unit-scheduler;
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.
