Supported Platforms
Node Interfaces on Active SRX Series Chassis Clusters
Normally, on SRX Series devices, the built-in interfaces are numbered as follows:
For Most SRX Series Devices | ge-0/0/0 | ge-0/0/1 | ge-0/0/2 | ge-0/0/3 | . . . |
For SRX210 Devices | ge-0/0/0 | ge-0/0/1 | fe-0/0/2 | fe-0/0/3 | . . . |
For SRX100 Devices | fe-0/0/0 | fe-0/0/1 | fe-0/0/2 | fe-0/0/3 | . . . |
 | Note: On SRX210, SRX220, SRX240, SRX550, and SRX650 devices, Layer 2 Ethernet switching is supported in chassis cluster mode. |
For chassis clustering, all SRX Series devices have a built-in management interface named fxp0. For most SRX Series devices, the fxp0 interface is a dedicated port. For SRX100, SRX210, and SRX220 devices, after you enable chassis clustering and reboot the system, the built-in interface named fe-0/0/6 is repurposed as the management interface and is automatically renamed fxp0.
For the SRX5000 line, control interfaces are configured on SPCs. For the SRX3000 line and the SRX240, SRX550, SRX650, and SRX1400 devices, control interfaces are dedicated Gigabit Ethernet ports. For SRX100, SRX210, and SRX220 devices, after you enable chassis clustering and reboot the system, the built-in interface named fe-0/0/7 is repurposed as the control interface and is automatically renamed fxp1.
After the devices are connected as a cluster, the slot numbering on one device changes and thus the interface numbering will change. The slot number for each slot in both nodes is determined 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 SRX210 device is still labeled fe-0/0/6, but internally, the node 1 port is referred to as fe-2/0/6.
In chassis cluster mode, all FPC related configuration is performed under edit chassis node node-id fpc hierarchy. In non-cluster mode, the FPC related configuration is performed under edit chassis fpc hierarchy.
Table 1 shows the slot numbering, as well as the physical port and logical interface numbering, for both of the SRX Series devices that become node 0 and node 1 of the chassis cluster after the cluster is formed.
Table 1: SRX Series Chassis Cluster Slot Numbering, and Physical Port and Logical 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 |
|---|---|---|---|---|---|---|
5800 | Node 0 | 12 (FPC slots) | 0 — 11 | Dedicated Gigabit Ethernet port | Control port on an SPC | Any Ethernet port |
fxp0 | em0 | fab0 | ||||
Node 1 | 12 — 23 | Dedicated Gigabit Ethernet port | Control port on an SPC | Any Ethernet port | ||
fxp0 | em0 | fab1 | ||||
5600 | Node 0 | 6 (FPC slots) | 0 — 5 | Dedicated Gigabit Ethernet port | Control port on an SPC | Any Ethernet port |
fxp0 | em0 | fab0 | ||||
Node 1 | 6 — 11 | Dedicated Gigabit Ethernet port | Control port on an SPC | Any Ethernet port | ||
fxp0 | em0 | fab1 | ||||
5400 | Node 0 | 3 (FPC slots) | 0 — 2 | Dedicated Gigabit Ethernet port | Control port on an SPC | Any Ethernet port |
fxp0 | em0 | fab0 | ||||
Node 1 | 3 — 5 | Dedicated Gigabit Ethernet port | Control port on an SPC | Any Ethernet port | ||
fxp0 | em0 | fab1 | ||||
3600 | Node 0 | 13 (CFM slots) | 0 — 12 | Dedicated Gigabit Ethernet port | Dedicated Gigabit Ethernet port | Any Ethernet port |
fxp0 | em0 | fab0 | ||||
Node 1 | 13 — 25 | Dedicated Gigabit Ethernet port | Dedicated Gigabit Ethernet port | Any Ethernet port | ||
fxp0 | em0 | fab1 | ||||
3400 | Node 0 | 8 (CFM slots) | 0 — 7 | Dedicated Gigabit Ethernet port | Dedicated Gigabit Ethernet port | Any Ethernet port |
fxp0 | em0 | fab0 | ||||
Node 1 | 8 — 15 | Dedicated Gigabit Ethernet port | Dedicated Gigabit Ethernet port | Any Ethernet port | ||
fxp0 | em0 | fab1 | ||||
1400 | Node 0 | 4 (FPC slots) | 0 — 3 | Dedicated Gigabit Ethernet port | Dedicated Gigabit Ethernet port | Any Ethernet port |
fxp0 | em0 | fab0 | ||||
Node 1 | 4 — 7 | Dedicated Gigabit Ethernet port | Dedicated Gigabit Ethernet port | Any Ethernet port | ||
fxp0 | em0 | fab1 | ||||
650 | Node 0 | 9 (PIM slots) | 0 — 8 | ge-0/0/0 | ge-0/0/1 | Any Ethernet port |
fxp0 | fxp1 | fab0 | ||||
Node 1 | 9 — 17 | ge-9/0/0 | ge-9/0/1 | Any Ethernet port | ||
fxp0 | fxp1 | fab1 | ||||
550 | Node 0 | 9 (PIM slots) | 0 — 8 | ge-0/0/0 | ge-0/0/1 | Any Ethernet port |
fxp0 | fxp1 | fab0 | ||||
Node 1 | 9 — 17 | ge-9/0/0 | ge-9/0/1 | Any Ethernet port | ||
fxp0 | fxp1 | fab1 | ||||
240 | Node 0 | 5 (PIM slots) | 0 — 4 | ge-0/0/0 | ge-0/0/1 | Any Ethernet port |
fxp0 | fxp1 | fab0 | ||||
Node 1 | 5 — 9 | ge-5/0/0 | ge-5/0/1 | Any Ethernet port | ||
fxp0 | fxp1 | fab1 | ||||
220 | Node 0 | 3 (PIM slots) | 0 — 2 | ge-0/0/6 | ge-0/0/7 | Any Ethernet port |
fxp0 | fxp1 | fab0 | ||||
Node 1 | 3 — 5 | ge-3/0/6 | ge-3/0/7 | Any Ethernet port | ||
fxp0 | fxp1 | fab1 | ||||
210 | Node 0 | 2 (PIM slots) | 0 and 1 | fe-0/0/6 | fe-0/0/7 | Any Ethernet port |
fxp0 | fxp1 | fab0 | ||||
Node 1 | 2 and 3 | fe-2/0/6 | fe-2/0/7 | Any Ethernet port | ||
fxp0 | fxp1 | fab1 | ||||
100 | Node 0 | 1(PIM slot) | 0 | fe-0/0/6 | fe-0/0/7 | Any Ethernet port |
fxp0 | fxp1 | fab0 | ||||
Node 1 | 1 | fe-1/0/6 | fe-1/0/7 | Any Ethernet port | ||
fxp0 | fxp1 | fab1 |
Information about chassis cluster slot numbering is also provided in Figure 1, Figure 2, Figure 3, Figure 4, Figure 5, Figure 6, Figure 7, Figure 8, and Figure 9.
| Note: See the hardware documentation for your particular model (links here:SRX Series Services Gateways) for details about SRX Series devices. See Junos OS Interfaces Library for Security Devices for a full discussion of interface naming conventions. |
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 slots. (See Figure 1, Figure 2, Figure 3,Figure 4, Figure 5, Figure 6, Figure 7, Figure 8, and Figure 9.)
Figure 1: FPC Slot Numbering in an SRX Series Chassis Cluster (SRX5800 Devices)
| Note: SRX5600 and SRX5800 devices have Flex I/O Cards (Flex IOCs) that have two slots to accept the following port modules:
You can use these port modules to add from 4 to 16 Ethernet ports to your SRX Series device. Port numbering for these modules is slot/port module/port where slot is the number of the slot in the device in which the Flex IOC is installed; port module is 0 for the upper slot in the Flex IOC or 1 for the lower slot when the card is vertical, as in an SRX5800 device; and port is the number of the port on the port module. When the card is horizontal, as in an SRX5400 or SRX5600 device, port module is 0 for the left-hand slot or 1 for the right-hand slot. SRX5400 devices support only on SRX5K-MPC cards. The SRX5K-MPC cards also have two slots to accept the following port modules:
See the hardware guide for your specific SRX Series model (links here:SRX Series Services Gateways). |
Figure 2: Slot Numbering in an SRX Series Chassis Cluster (SRX3400 Devices)
Figure 3: Slot Numbering in an SRX Series Chassis Cluster (SRX1400 Devices)
Figure 4: Slot Numbering in an SRX Series Chassis Cluster (SRX650 Devices)
Figure 5: Slot Numbering in an SRX Series Chassis Cluster (SRX550 Devices)
Figure 6: Slot Numbering in an SRX Series Chassis Cluster (SRX240 Devices)
Figure 7: Slot Numbering in an SRX Series Chassis Cluster (SRX220 Devices)
Figure 8: Slot Numbering in an SRX Series Chassis Cluster (SRX210 Devices)
Figure 9: Slot Numbering in an SRX Series Chassis Cluster (SRX100 Devices)
Modified: 2016-07-28
Supported Platforms
Related Documentation
- SRX Series
- Results of Enabling Chassis Cluster
- Management Interface on an Active Chassis Cluster
- Fabric Interface on an Active Chassis Cluster
- Control Interface on an Active Chassis Cluster
- Additional Information
- Chassis Cluster Feature Guide for Security Devices
