Routers typically contain several different types of interfaces suited to various functions. For the interfaces on a routing platform to function, you must configure them, specifying properties such as the interface location (that is, the slot in which the Flexible PIC Concentrator [FPC] or Dense Port Concentrator [DPC] is installed, and the location where the Physical Interface Card [PIC] is installed), the interface type (such as SONET/SDH, Asynchronous Transfer Mode [ATM], or Ethernet), encapsulation, and interface-specific properties. You can configure the interfaces that are currently present in the routing platform, and you can also configure interfaces that are not currently present but that you might add in the future. When a configured interface appears, the JUNOS software detects its presence and applies the appropriate configuration to it.
To determine which interfaces are currently installed in the routing platform, issue the show interfaces terse operational mode command. If an interface is listed in the output, it is installed in the routing platform. If an interface is not listed in the output, it is not installed in the routing platform.
For information about which PICs are supported on your platform, see your platform’s PIC guide.
You can configure JUNOS class-of-service (CoS) properties to provide a variety of classes of service for different applications, including multiple forwarding classes for managing packet transmission, congestion management, and CoS-based forwarding. For more information about configuring CoS properties, see the JUNOS Class of Service Configuration Guide.
This chapter discusses the following topics: