Node Interfaces on J-series Chassis Clusters

Normally, on J-series devices, the built-in interfaces are numbered as follows:

After you enable chassis clustering and reboot the system, two of the built-in interfaces are repurposed as the management and control interfaces and are automatically renamed fxp0 and fxp1, respectively. Table 59 shows how these interfaces are renamed and how they are renumbered for a chassis cluster for the various J-series devices.

Table 59: J-series Chassis Cluster Interface Naming Scheme

Note: See the JUNOS Software with Enhanced Services Hardware Guide for details about J-series devices. The JUNOS Software Interfaces and Routing Configuration Guide provides a full discussion of the interface naming convention.

After you enable chassis clustering, the two chassis joined together cease to exist as individuals and now represent a single system. Internally, the cluster models a dual Routing Engine device. The primary Routing Engine propagates all its network and configuration settings and the current session information to the secondary. The secondary Routing Engine serves as the backup. As a single system, the cluster now has twice as many PIM slots. (See Figure 68.)

Figure 68: PIM Slot Numbering in a J-series Chassis Cluster (J6350 Devices)

Copyright © 2008, Juniper Networks, Inc. All rights reserved. Trademark Notice.