Shared Interfaces

A single Physical Interface Card (PIC) can host a physical interface that is shared by different Protected System Domains (PSDs). The Flexible PIC Concentrator (FPC) and the physical shared interface are owned by the Root System Domain (RSD). However, the logical interfaces configured under the shared interface are assigned to and owned by different PSDs. By sharing a single interface among multiple PSDs, the cost of traffic forwarding is reduced and resources can be allocated flexibly at a more granular level.

Any FPC that has not been assigned to a specific PSD can be used to host shared interfaces. On the RSD, multiple logical interfaces are configured on the physical interface and each individual logical interface is assigned to a different PSD. On the PSD, each assigned logical interface is configured and peered with an uplink tunnel interface (ut-fpc/pic/slot), which transports packets between the PSD and the shared interface on the RSD. See Figure 2.

Figure 2: Shared Interfaces

When applied to shared interfaces: JUNOS features that are configured under logical interfaces, such as class-of-service (CoS) classifiers and rewrites, firewall filters, and policers, are configured on the PSD. JUNOS features that are configured under physical interfaces, such as drop profiles and schedule maps, are configured on the RSD.

The packets belonging to a shared interface pass between the Packet Forwarding Engine on the PIC in the RSD and the Packet Forwarding Engine on the uplink tunnel PIC in the PSD through a cross-connect in the forwarding fabric.

Traffic flow from the PSD to the RSD over a shared interface is as follows:

1. A packet destined for the shared PIC at the RSD is received on an interface at the PSD and sent to the Packet Forwarding Engine on the PSD’s tunnel PIC. (The tunnel PIC is configured to peer with the shared PIC at the RSD.)
2. The packet is sent out of the tunnel interface.
3. The tunnel PIC loops the packet back to the input side of its Packet Forwarding Engine and the packet is sent over the switch fabric to the Packet Forwarding Engine on the shared PIC at the RSD.
4. The packet is then sent out the shared interface.

Traffic flow from the RSD to the PSD is as follows:

1. The Packet Forwarding Engine on the shared PIC at the RSD determines on which logical interface the packet arrived.
2. Based on the RSD configuration, the PSD that is associated with this logical interface is known and the packet is sent over the switch fabric to the tunnel PIC at that PSD.
3. The packet is sent out the tunnel interface.
4. The tunnel PIC loops the packet back to the input side of its Packet Forwarding Engine and the packet is then handled as if it had arrived on a directly-connected PIC.

Table 3 lists the PICs that support shared interfaces:

Table 3: PICs Supporting Shared Interfaces

Note: Only SONET PICs that are installed on an Enhanced Services (ES) FPC on a T320 router or on a T1600 routing node can support shared interfaces.

Related Topics

• JCS 1200 Chassis and T-series Routers as a Single Platform
• Root System Domains
• Protected System Domains
• Connections Between JCS 1200 and T-series Chassis
• Benefits of JCS 1200 and T-series as a Single Platform