Related Documentation
- J, M, MX, PTX, T Series
- Types of Interfaces Overview
- Permanent Interfaces Overview
- Understanding Management Ethernet Interfaces
- Understanding Internal Ethernet Interfaces
- Interface Encapsulations Overview
- Interface Descriptors Overview
- Interface Naming Overview
- Displaying Interface Configurations Overview
- J, M, MX, T Series
- Understanding Services Interfaces
- Container Interfaces Overview
- M, MX, PTX, T Series
- Supported Routing Engines by Chassis
Understanding Transient Interfaces
The M Series, MX Series, and T Series routers contain slots for installing FPCs. PICs can be installed in FPCs. The number of PICs that can be installed varies by router and type of FPC. The PICs provide the actual physical interfaces to the network. The MX Series routers contain slots for installing either DPC boards that provide the physical interfaces to the network or for installing FPCs in which PICs can be installed. These physical interfaces are transient interfaces of the router. They are referred to as transient because you can hot-swap a DPC or FPC and its PICs at any time.
You can insert any DPC or FPC into any slot that supports them in the appropriate router. Typically, you can place any combination of PICs, compatible with your router, in any location on an FPC. (You are limited by the total FPC bandwidth, and by the fact that some PICs physically require two or four of the PIC locations on the FPC. In some cases, power limitations or microcode limitations may also apply.) To determine DPC and PIC compatibility, see the Hardware Guide, DPC Guide, and PIC Guide for your router.
You must configure each transient interface based on the slot in which the FPC is installed, the location in which the PIC is installed, and for multiple port PICs, the port to which you are connecting.
You can configure the interfaces on PICs that are already installed in the router as well as interfaces on PICs that you plan to install later. The Junos OS detects which interfaces are actually present, so when the software activates its configuration, it activates only the present interfaces and retains the configuration information for the interfaces that are not present. When the Junos OS detects that an FPC containing PICs has been inserted into the router, the software activates the configuration for those interfaces.
Related Documentation
- J, M, MX, PTX, T Series
- Types of Interfaces Overview
- Permanent Interfaces Overview
- Understanding Management Ethernet Interfaces
- Understanding Internal Ethernet Interfaces
- Interface Encapsulations Overview
- Interface Descriptors Overview
- Interface Naming Overview
- Displaying Interface Configurations Overview
- J, M, MX, T Series
- Understanding Services Interfaces
- Container Interfaces Overview
- M, MX, PTX, T Series
- Supported Routing Engines by Chassis
Published: 2013-02-13
Related Documentation
- J, M, MX, PTX, T Series
- Types of Interfaces Overview
- Permanent Interfaces Overview
- Understanding Management Ethernet Interfaces
- Understanding Internal Ethernet Interfaces
- Interface Encapsulations Overview
- Interface Descriptors Overview
- Interface Naming Overview
- Displaying Interface Configurations Overview
- J, M, MX, T Series
- Understanding Services Interfaces
- Container Interfaces Overview
- M, MX, PTX, T Series
- Supported Routing Engines by Chassis
