Node Interfaces on Active J Series Chassis Clusters
Normally, on J Series devices, the built-in interfaces are numbered as follows:
ge-0/0/0 | ge-0/0/1 | ge-0/0/2 | ge-0/0/3 | . . . |
![]() | Caution: Layer 2 switching must not be enabled on J Series device when chassis clustering is enabled. If you have enabled Layer 2 switching, make sure you disable it before enabling chassis clustering. |
After you enable chassis clustering and reboot the system, the built-in interface named ge-0/0/2 is repurposed as the management interface and is automatically renamed fxp0. Likewise, the built-in interface named ge-0/0/3 is repurposed as the control interface and is automatically renamed fxp1.
After the devices are connected as a cluster, the slot numbering and thus the interface numbering will change for one device. The cluster determines the slot number for each slot in both nodes using the following formula:
cluster slot number = (node ID * maximum
slots per node) + local slot number
In chassis cluster mode, the interfaces on the secondary node are renumbered internally. For example, the management interface port on the front panel of each J2320 device is still labeled ge-0/0/2, but internally, the node 1 port is referred to as ge-4/0/2.
Table 79 shows the slot numbering, as well as the port and interface numbering, for both of the J Series devices that become node 0 and node 1 of the cluster after the cluster is formed.
Table 79: J Series Chassis Cluster Slot Numbering and Port/Interface Naming
Model | Chassis | Maximum Slots Per Node | Slot Numbering in a Cluster | Management Physical Port/Logical Interface | Control Physical Port/Logical Interface | Fabric Physical Port/Logical Interface |
---|---|---|---|---|---|---|
J2320 | Node 0 | 4 (PIM slots); includes one pre-set slot | 0 — 3 | ge-0/0/2 | ge-0/0/3 | Any Gigabit Ethernet port |
fxp0 | fxp1 | fab0 | ||||
Node 1 | 4 — 7 | ge-4/0/2 | ge-4/0/3 | Any Gigabit Ethernet port | ||
fxp0 | fxp1 | fab1 | ||||
J2350 | Node 0 | 6 (PIM slots); includes one pre-set slot | 0 — 5 | ge-0/0/2 | ge-0/0/3 | Any Gigabit Ethernet port |
fxp0 | fxp1 | fab0 | ||||
Node 1 | 6 — 11 | ge-6/0/2 | ge-6/0/3 | Any Gigabit Ethernet port | ||
fxp0 | fxp1 | fab1 | ||||
J4350 and J6350 | Node 0 | 7 (PIM slots); includes one pre-set slot | 0 — 6 | ge-0/0/2 | ge-0/0/3 | Any Gigabit Ethernet port |
fxp0 | fxp1 | fab0 | ||||
Node 1 | 7 — 13 | ge-7/0/2 | ge-7/0/3 | Any Gigabit Ethernet port | ||
fxp0 | fxp1 | fab1 |
Information about cluster slot numbering is also provided in Figure 93.
![]() | Note: See the J Series Services Routers Hardware Guide for details about J Series devices. The JUNOS Software Interfaces Configuration Guide for Security Devices 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. As a single system, the cluster now has twice as many PIM slots. (See Figure 93.)
Figure 93: PIM Slot Numbering in a J Series Chassis Cluster (J6350 Devices)
Related Topics
- JUNOS Software Feature Support Reference for SRX Series and J Series Devices
- Understanding What Happens When Chassis Cluster Is Enabled
- Node Interfaces on Active SRX Series Chassis Clusters
- Management Interface on an Active Chassis Cluster
- Fabric Interface on an Active Chassis Cluster
- Control Interface on an Active Chassis Cluster