Applying Scheduler Maps Overview
Physical interfaces (for example, t3-0/0/0, t3-0/0/0:0, and ge-0/0/0) support scheduling
with any encapsulation type pertinent to that physical interface.
For a single port, you cannot apply scheduling to the physical interface
if you have applied scheduling to one or more of the associated logical
interfaces.
Logical interfaces (for example, t3-0/0/0 unit 0 and ge-0/0/0 unit 0) support scheduling on
data link connection identifiers (DLCIs) or VLANs only.
In the Junos OS implementation, the term logical interfaces generally refers to interfaces you configure by including the unit statement at the [edit interfaces interface-name] hierarchy level. Logical interfaces have the .logical descriptor at the end of the interface name,
as in ge-0/0/0.1 or t1-0/0/0:0.1, where the
logical unit number is 1.
Although channelized interfaces are generally thought of as
logical or virtual, the Junos OS sees T3, T1, and NxDS0 interfaces within a channelized IQ PIC as physical interfaces.
For example, both t3-0/0/0 and t3-0/0/0:1 are
treated as physical interfaces by the Junos OS. In contrast, t3-0/0/0.2 and t3-0/0/0:1.2 are considered logical
interfaces because they have the .2 at the end of the interface
names.
Within the [edit class-of-service] hierarchy level,
you cannot use the .logical descriptor
when you assign properties to logical interfaces. Instead, you must
include the unit statement in the configuration. For example:
[edit class-of-service] user@host# set interfaces t3-0/0/0 unit 0 scheduler-map map1