•
ct1—Channelized T1 IQ interface (configured on the Channelized DS3 IQ PIC or
Channelized OC12 IQ PIC).
•
ct3—Channelized T3 IQ interface (configured on the Channelized DS3 IQ PIC or
Channelized OC12 IQ PIC).
•
ce1—Channelized E1 IQ interface (configured on the Channelized E1 IQ PIC or Channelized
STM1 IQ PIC).
•
dsc—Discard interface.
•
fxp—Management and internal Ethernet interfaces.
•
lo—Loopback interface. This interface is internally generated.
•
pe—Encapsulates packets destined for the rendezvous point routing device. This
interface is present on the first-hop routing device.
•
pd—De-encapsulates packets at the rendezvous point. This interface is present on the
rendezvous point.
•
vt—Virtual loopback tunnel interface.
NOTE: For channelized interfaces, you can configure CoS on channels, but
not at the controller level. For a complex configuration example, see the
Junos OS Feature Guides.
VPLS and Default CoS Classification
A VPLS routing instance with the no-tunnel-services option configured has a default
classifier applied to the label-switched interface for all VPLS packets coming from the
remote VPLS PE. This default classifier is modifiable only on MX Series routers. On T
Series, when no-tunnel-services option is configured, the custom classifier for VPLS
instances is not supported.
NOTE: With no-tunnel-services configured, custom classifier for VPLS routing
instances on T Series and LMNR based FPC for M320 is not supported. When
a wild card configuration or an explicit routing instances are configured for
VPLS on CoS CLI, the custom classifier binding results in default classifier
binding on Packet Forwarding Engine (PFE).
For example, on routing devices with eight queues (Juniper Networks M120 and M320
Multiservice Edge Routers, MX Series 3D Universal Edge Routers, and T Series Core
Routers), the default classification applied to no-tunnel-services VPLS packets are shown
in Table 3 on page 11.
Copyright © 2013, Juniper Networks, Inc.10
Class of Service Overview and Examples for EX9200 Switches