Understanding SRX Series Chassis Cluster Slot Numbering and Physical Port and Logical Interface Naming
See the hardware documentation for your particular model (SRX Series Services Gateways) for details about SRX Series devices. See Interfaces Feature Guide for Security Devices for a full discussion of interface naming conventions.
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.
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.
This topic describes the slot numbering and physical port and logical interface naming conventions for SRX Series devices in a chassis cluster and includes following sections:
Chassis Cluster Slot Numbering and Physical Port and Logical Interface Naming for SRX300, SRX320, SRX340, SRX345, SRX550M, and SRX1500 Devices
For SRX340 and SRX345 devices, the fxp0 interface is a dedicated port. For SRX300 and SRX320 devices, after you enable chassis clustering and reboot the system, the built-in interface named ge-0/0/0 is repurposed as the management interface and is automatically renamed fxp0.
For SRX300, SRX320, SRX340, and SRX345 devices, after you enable chassis clustering and reboot the system, the build-in interface named ge-0/0/1is repurposed as the control interface and is automatically renamed fxp1.
For SRX550M devices, control interfaces are dedicated Gigabit Ethernet ports.
SRX1500 devices have 16 GE interfaces and 4 XE ports.
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: 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 |
|---|---|---|---|---|---|---|
1500 | Node 0 | 1 | 0 | fxp0 | Dedicated Control port | Any Ethernet port |
em0 | fab0 | |||||
Node 1 | 7 | fxp0 | Dedicated Control port | Any Ethernet port | ||
em0 | 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 | ||||
340 and 345 | Node 0 | 5 (PIM slots) | 0—4 | fxp0 | ge-0/0/1 | Any Ethernet port |
fxp0 | fxp1 | fab0 | ||||
Node 1 | 5—9 | fxp0 | ge-5/0/1 | Any Ethernet port | ||
fxp0 | fxp1 | fab1 | ||||
320 | Node 0 | 3 (PIM slots) | 0—2 | ge-0/0/0 | ge-0/0/1 | Any Ethernet port |
fxp0 | fxp1 | fab0 | ||||
Node 1 | 3—5 | ge-3/0/0 | ge-3/0/1 | Any Ethernet port | ||
fxp0 | fxp1 | fab1 | ||||
300 | Node 0 | 1(PIM slot) | 0 | ge-0/0/0 | ge-0/0/1 | Any Ethernet port |
fxp0 | fxp1 | fab0 | ||||
Node 1 | 1 | ge-1/0/0 | ge-1/0/1 | Any Ethernet port | ||
fxp0 | fxp1 | fab1 |
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, and Figure 6.)
Chassis Cluster Slot Numbering and Physical Port and Logical Interface Naming for SRX4600 Devices
The SRX4600 devices use dedicated HA control ports. The dedicated Chassis Cluster fabric ports are not available. Instead, any 40G or 10G traffic ports can be used as chassis cluster fabric ports. The HA dedicated interface on SRX4600 supports 10-Gigabit Ethernet Interface.
Table 2 and Table 3 show 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 2: Chassis Cluster Slot Numbering, and Physical Port and Logical Interface Naming for SRX4600 Devices
Model | Chassis Cluster | Maximum Slots Per Node | Slot Numbering in a Cluster | Management Physical Port/Logical Interface | Control Physical Port/Logical Interface | Fabric Physical Port/Logical Interface |
|---|---|---|---|---|---|---|
SRX4600 | Node 0 | 1 | 0-7 | fxp0 | Dedicated control port, em0 | Dedicated fabric port, fab0 |
Node 1 | 8-15 | Dedicated fabric port, (for dual fabric-link), fab1 40-Gigabit Ethernet port (xe) |
Table 3: Chassis Cluster Interface Renumbering for SRX4600
Device | Renumbering Constant | Node 0 Interface Name | Node 1 Interface Name |
|---|---|---|---|
SRX4600 | 8 | xe-0/0/0 | xe-7/0/0 |
Mix and match of fabric ports are not supported. That is, you cannot use one 10-Gigabit Ethernet interface and one 40-Gigabit Ethernet interface for fabric links configuration. Dedicated fabric link supports only 10-Gigabit Ethernet Interface.
Figure 7 shows the slot numbering for both of the SRX Series devices that become node 0 and node 1 of the chassis cluster after the cluster is formed.
Chassis Cluster Slot Numbering and Physical Port and Logical Interface Naming for SRX4100 and SRX4200 Devices
The SRX4100 and SRX4200 devices use two 1-Gigabit
Ethernet/10-Gigabit Ethernet ports, labeled as CTL and FAB as control port and fabric port respectively.
Supported fabric interface types for SRX4100 and SRX4200 devices are 10-Gigabit Ethernet (xe) (10-Gigabit Ethernet Interface SFP+ slots).
Table 4 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 4: Chassis Cluster Slot Numbering, and Physical Port and Logical Interface Naming for SRX4100 and SRX4200 Devices
Model | Chassis Cluster | Maximum Slots Per Node | Slot Numbering in a Cluster | Management Physical Port/Logical Interface | Control Physical Port/Logical Interface | Fabric Physical Port/Logical Interface |
|---|---|---|---|---|---|---|
SRX4100 | Node 0 | 1 | 0 | fxp0 | Dedicated control port, em0 | Dedicated fabric port, any Ethernet port (for dual fabric-link), fab0 |
Node 1 | 7 | Dedicated fabric port, and any Ethernet port (for dual fabric-link), fab1 | ||||
SRX4200 | Node 0 | 1 | 0 | fxp0 | Dedicated control port,em0 | Dedicated fabric port, and any Ethernet port (for dual fabric-link), fab0 |
Node 1 | 7 | Dedicated fabric port, and any Ethernet port (for dual fabric-link), fab1 |
Figure 8 and Figure 9 shows the slot numbering for both of the SRX Series devices that become node 0 and node 1 of the chassis cluster after the cluster is formed.
The node 1 renumbers its interfaces by adding the total number of system FPCs to the original FPC number of the interface. For example, see Table 5 for interface renumbering on the SRX Series devices (SRX4100 and SRX4200).
Table 5: Chassis Cluster Interface Renumbering for SRX4100 and SRX4200
Device | Renumbering Constant | Node 0 Interface Name | Node 1 Interface Name |
|---|---|---|---|
SRX4100 | 7 | xe-0/0/0 | xe-7/0/0 |
SRX4200 | 7 | xe-0/0/1 | xe-7/0/1 |
On SRX4100 and SRX4200 devices, when the system comes up as chassis cluster, the xe-0/0/8 and xe-7/0/8 interfaces are automatically set as fabric interfaces links as shown in Table 3. You can set up another pair of fabric interfaces using any pair of 10-Gigabit interfaces to serve as the fabric between nodes. Note that, the automatically created fabric interfaces cannot be deleted. However, you can delete the second pair of fabric interfaces (manually configured interfaces).
Chassis Cluster Slot Numbering and Physical Port and Logical Interface Naming for SRX5800, SRX5600, and SRX5400 Devices
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 the SRX5000 line, control interfaces are configured on SPCs.
Table 6 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 6: Chassis Cluster Slot Numbering, and Physical Port and Logical Interface Naming for SRX5000-Line Devices
Model | Chassis Cluster | 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 |
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 10.)
Chassis Cluster Slot Numbering and Physical Port and Logical Interface Naming for SRX3600, SRX3400, and SRX1400
Table 7 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 7: Chassis Cluster Slot Numbering, and Physical Port and Logical Interface Naming for SRX1400, SRX3400, and SRX3600
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 |
|---|---|---|---|---|---|---|
SRX3600 | 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 | ||||
SRX3400 | 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 | ||||
SRX1400 | 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 |
Information about chassis cluster slot numbering is also provided in Figure 11, Figure 12 and Figure 13.
Chassis Cluster Slot Numbering and Physical Port and Logical Interface Naming for SRX650, SRX550, SRX240, SRX210, SRX110, and SRX100
Information about chassis cluster slot numbering is also provided in Figure 14, Figure 15, Figure 16, Figure 17, Figure 18, and Figure 19.
Layer 2 switching must not be enabled on an SRX Series device when chassis clustering is enabled. If you have enabled Layer 2 switching, make sure you disable it before enabling chassis clustering.
The factory default configuration for SRX100, SRX210, and SRX220 devices automatically enables Layer 2 Ethernet switching. Because Layer 2 Ethernet switching is not supported in chassis cluster mode, if you use the factory default configuration for these devices, you must delete the Ethernet switching configuration before you enable chassis clustering. See Disabling Switching on SRX100, SRX210, and SRX220 Devices Before Enabling Chassis Clustering.
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 SRX240, SRX550, and SRX650, 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.
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.
FPC Slot Numbering in SRX Series Device Cards
SRX5600 and SRX5800 devices have Flex I/O Cards (Flex IOCs) that have two slots to accept the following port modules:
SRX-IOC-4XGE-XFP 4-Port XFP
SRX-IOC-16GE-TX 16-Port RJ-45
SRX-IOC-16GE-SFP 16-Port SFP
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
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 SRX5K-MPC cards. The SRX5K-MPC cards also have two slots to accept the following port modules:
SRX-MIC-10XG-SFPP 10-port-SFP+ (xe)
SRX-MIC-20GE-SFP 20-port SFP (ge)
SRX-MIC-1X100G-CFP 1-port CFP (et)
SRX-MIC-2X40G-QSFP 2-port QSFP (et)
See the hardware guide for your specific SRX Series model (SRX Series Services Gateways).