Applying Scheduler Maps to Physical Interfaces
After you have defined a scheduler map, as described in Configuring Scheduler Maps, you can apply
it to an output interface. Include the scheduler-map statement
at the [edit class-of-service interfaces interface-name] hierarchy level:
[edit class-of-service interfaces interface-name] scheduler-map map-name;
Interface wildcards are supported. However, scheduler maps using wildcard interfaces are not checked against routing device interfaces at commit time and can result in a configuration that is incompatible with installed hardware. Fully specified interfaces, on the other hand, check the configuration against the hardware and report errors or warning if the hardware does not support the configuration.
Generally, you can associate schedulers with physical interfaces only. For some IQ interfaces, you can also associate schedulers with the logical interface. For more information, see Applying Scheduler Maps and Shaping Rate to DLCIs and VLANs.
For original Channelized OC12 PICs, limited CoS functionality is supported. For more information, contact Juniper Networks customer support.
When you apply a scheduler map to a physical interface, or when you modify the configuration of a scheduler map that is already applied to a physical interface, packets already in the output queues of the interface might get dropped. The amount of packet loss is not deterministic and depends on the offered traffic load at the time you apply or modify the scheduler map.