[an error occurred while processing this directive][an error occurred while processing this directive]

Configuring the JUNOS Software to Support FPC to FEB Connectivity on M120 Routers

The M120 router supports six Forwarding Engine Boards (FEBs) and six Flexible PIC Concentrators (FPCs). The supported FPCs include:

  • Two compact FPCs:
    • OC192 compact FPC (supported only on the D4 chip-based compact FPC)
    • 10-Gigabit Ethernet compact FPC
  • Up to four Type 1, Type 2, or Type 3 FPCs

On the M120 router, you can map a connection between any FPC and any FEB. This capability allows you to configure resources for a chassis that contains empty slots, supporting configurations where the FPC and FEB pairs are not in slot order. You do not have to populate every empty slot position, but you must configure a FEB for every FPC.

If you do not want to map a connection between an FPC and a FEB, you must explicitly configure the FPC not to connect to the FEB. To do so, include the none option at the [edit chassis fpc-feb-connectivity fpc number feb] hierarchy level. If you do not configure FPC and FEB connectivity, it is automatically assigned in the following order: FPC 0 to FEB 0, FPC 1 to FEB 1, and so on.

For each FEB, you can map a maximum of two Type 1 FPCs or one Type 2, Type 3, or compact FPC.

The following restrictions apply when you configure FPC and FEB connectivity:

  • When an FPC is configured not to connect to any FEB, interfaces on that FPC are not created.
  • If a PIC comes online, but the FEB to which the FPC is configured to connect is not online, the physical interfaces for the PIC are not created. For example, PIC  1 on FPC 2 comes online. The configuration specifies that FPC 2 connects to FEB 3. If FEB 3 is not online at the time PIC 1 comes online, the physical interfaces corresponding to PIC 1 on FPC 2 are not created. If FEB 3 subsequently comes online, the physical interfaces are created.
  • If a FEB is brought offline or removed, any interfaces on the FPCs connected to the FEB are deleted. If the FEB is subsequently brought back online, the interfaces are restored.
  • FPCs and FEBs might reboot following a change in the FPC and FEB connectivity configuration. If an FPC connects to a different FEB as a result of the configuration change, the FPC is rebooted following the commit. As a result of the reboot, interfaces on the FPC are deleted.
  • If a FEB connects to a different FPC or set of FPCs after a connectivity configuration change, the FEB is rebooted. The exception is if the FEB is already connected to one or two Type 1 FPCs and the change only results in the FEB being connected either to one additional or one fewer Type 1 FPC.

To configure a connection between an FPC and a FEB, include the fpc-feb-connectivity statement at the [edit chassis] hierarchy level:

[edit chassis]fpc-feb-connectivity {fpc number feb (slot-number | none);}

For fpc number, enter a value from 0 through 5. For feb slot-number, enter a value from 0 through 5 or none. The none option disconnects the FPC from the FEB.

To view the current FPC and FEB mapping and the status of each FPC and FEB, issue the show chassis fpc-feb-connectivity operational mode command. For more information, see the JUNOS System Basics and Services Command Reference.

Note: FPC-to-FEB connectivity is supported only on the M120 router.

In this example, FPC 3 is already mapped to FEB 3 by default. You are also mapping a connection between FPC 2 and FEB 3.

[edit chassis]fpc-feb-connectivity {fpc 2 feb 3;}

However, this configuration results in a mismatch between the FPC type and the FEB type. For example, FPC 3 is not a Type 1 FPC. You can map only one FPC that is not a Type 1 FPC to a FEB. Use the fpc-feb-connectivity statement to explicitly disconnect FPC 3 from FEB 3. To do so, include the none option at the [edit chassis fpc-feb-connectivity fpc number feb] hierarchy level:

[edit chassis]fpc-feb-connectivity {fpc 2 feb 3;fpc 3 feb none;}

Published: 2010-04-26

[an error occurred while processing this directive]