Chassis Cluster Slot Numbering and Physical Port and Logical Interface Naming
Chassis Cluster Slot Numbering and Physical Port and Logical Interface Naming for SRX4600 Firewalls
Chassis Cluster Slot Numbering and Physical Port and Logical Interface Naming for SRX2300, SRX4120, SRX4100, SRX4200, and SRX4300 Devices
Chassis Cluster Slot Numbering and Physical Port and Logical Interface Naming for SRX5000 Line of Firewalls
FPC Slot Numbering in Firewall Cards

Slot Numbering and Logical Interface Naming

This topic explains the slot numbering, physical port naming, and logical interface naming conventions for Firewalls operating in a chassis cluster.

Use Feature Explorer to confirm platform and release support for specific features.

Review the Platform-Specific Chassis Cluster Slot Numbering Behavior section for notes related to your platform.

In chassis cluster mode, the interfaces on the firewall operating as node 1 are internally renumbered.

After the devices are connected to form a cluster, the slot numbering on the firewall acting as node 1 changes, and as a result, the interface numbering also changes. For more information, see Interfaces User Guide for Security Devices for detailed interface naming conventions.

The slot number for each slot on both nodes is calculated using the following formula:

cluster slot number = (node ID * maximum slots per node) + local slot number

Chassis Cluster Slot Numbering and Physical Port and Logical Interface Naming

Table 1 shows the slot numbering, and the physical port and logical interface numbering, for both the Firewalls after they are formed into a chassis cluster as node 0 and node 1.

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
SRX1600	Node 0	3	0	fxp0	Dedicated dual Control links with MACsec support	Dual fabric links
	Node 0		0	fxp0	em0/em1	fab0
	Node 1		7	fxp0	Dedicated dual Control links with MACsec support	Dual fabric links
	Node 1		7	fxp0	em0/em1	fab1
SRX1500	Node 0	3	0	fxp0	Dedicated Control port	Any Ethernet port
	Node 0		0	fxp0	em0	fab0
	Node 1		7	fxp0	Dedicated Control port	Any Ethernet port
	Node 1		7	fxp0	em0	fab1
SRX340,SRX345, and SRX380	Node 0	5 (PIM slots)	0—4	fxp0	ge-0/0/1	Any Ethernet port
	Node 0		0—4	fxp0	fxp1	fab0
	Node 1		5—9	fxp0	ge-5/0/1	Any Ethernet port
	Node 1		5—9	fxp0	fxp1	fab1
SRX320	Node 0	3 (PIM slots)	0—2	ge-0/0/0	ge-0/0/1	Any Ethernet port
	Node 0		0—2	fxp0	fxp1	fab0
	Node 1		3—5	ge-3/0/0	ge-3/0/1	Any Ethernet port
	Node 1		3—5	fxp0	fxp1	fab1
SRX300	Node 0	1(PIM slot)	0	ge-0/0/0	ge-0/0/1	Any Ethernet port
	Node 0		0	fxp0	fxp1	fab0
	Node 1		1	ge-1/0/0	ge-1/0/1	Any Ethernet port
	Node 1		1	fxp0	fxp1	fab1

Table 2: Chassis Cluster Fabric Interface Details for SRX1600
Interfaces	Used as Fabric Port?	Supports Z-Mode Traffic?	Supports MACsec?
16X1Gigabit Ethernet Interface -BASE-T RJ45	Yes	Yes	No
2x 25G SFP28	Yes	Yes	No
4x 10G SFP+	Yes	Yes	No

After chassis clustering is enabled, the two joined chassis no longer operate as independent devices and instead function as a single system. As a result, the cluster has twice the number of slots. (See Figure 1, Figure 2, Figure 3, Figure 4, and Figure 6.)

Figure 1: Slot Numbering in SRX300 Chassis Cluster Two Juniper SRX300 devices labeled Node 0 and Node 1 in a chassis cluster availability setup with Ethernet ports 0/0 to 0/7, console, and USB ports.

Two Juniper SRX300 devices labeled Node 0 and Node 1 in a chassis cluster availability setup with Ethernet ports 0/0 to 0/7, console, and USB ports.

Figure 2: Slot Numbering in SRX320 Chassis Cluster Front panel of Juniper Networks SRX320 in dual-node configuration with labeled nodes and slots for connectivity and expansion.

Front panel of Juniper Networks SRX320 in dual-node configuration with labeled nodes and slots for connectivity and expansion.

Figure 3: Slot Numbering in SRX340 Chassis Cluster Diagram of Juniper Networks SRX340 device with labeled slots and nodes for network interfaces.

Diagram of Juniper Networks SRX340 device with labeled slots and nodes for network interfaces.

Figure 4: Slot Numbering in SRX345 Chassis Cluster Front panel layout of Juniper Networks SRX345 Services Gateway showing slots Slot 0 to Slot 9 and nodes Node 0 and Node 1 for port assignments.

Front panel layout of Juniper Networks SRX345 Services Gateway showing slots Slot 0 to Slot 9 and nodes Node 0 and Node 1 for port assignments.

Figure 5: Slot Numbering in SRX380 Chassis Cluster Juniper Networks SRX4600 front panel with Node 0 Slots 0-4 and Node 1 Slots 5-9 for network connectivity.

Juniper Networks SRX4600 front panel with Node 0 Slots 0-4 and Node 1 Slots 5-9 for network connectivity.

Figure 6: Slot Numbering in SRX1500 Chassis Cluster Juniper Networks SRX1500 devices labeled Node 0 and Node 1 configured in a cluster for redundancy with Slot 0 and Slot 7 identified for connectivity.

Juniper Networks SRX1500 devices labeled Node 0 and Node 1 configured in a cluster for redundancy with Slot 0 and Slot 7 identified for connectivity.

Figure 7: Slot Numbering in SRX1600 Chassis Cluster Rear view of a Juniper Networks chassis showing Node 0 with Slot 0 and Node 1 with Slot 7, highlighting modular network design.

Rear view of a Juniper Networks chassis showing Node 0 with Slot 0 and Node 1 with Slot 7, highlighting modular network design.

Chassis Cluster Slot Numbering and Physical Port and Logical Interface Naming for SRX4600 Firewalls

Table 3 and Table 4 show the slot numbering, as well as the physical port and logical interface numbering, for both of the Firewalls that become node 0 and node 1 of the chassis cluster after the cluster is formed.

Table 3: Chassis Cluster Slot Numbering, and Physical Port and Logical Interface Naming for SRX4600 Firewalls
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-6	fxp0	Dual (redundant) MACsec-enabled HA control ports (10GbE) are xe-0/0/0, xe-0/0/1, xe-7/0/0, and xe-7/0/1. It uses 1-Gigabit Ethernet SFP as control port.	Dual (redundant) MACsec-enabled HA fabric ports (10GbE) Dual Fabric ports with macsec enabled are xe-0/0/2 and xe-0/0/3
SRX4600	Node 1	1	7-13	fxp0

Table 4: Chassis Cluster Interface Renumbering for SRX4600
Device	Renumbering Constant	Node 0 Interface Name	Node 1 Interface Name
SRX4600	7	xe-1/0/0	xe-8/0/0

Table 5: Chassis Cluster Fabric Interface Details for SRX4600
Interfaces	Used as Fabric Port?	Supports Z-Mode Traffic?	Supports MACsec?
Dedicated fabric ports	Yes	Yes	Yes
8X10-Gigabit Ethernet Interface SFPP ports	Yes	Yes	No
4X40-Gigabit Ethernet Interface QSFP28 ports	Yes	Yes	No
4x10-Gigabit Ethernet Interface SFPP ports	Yes	Yes	No
2X100-Gigabit Ethernet Interface QSFP28 slots	No	No	No

Mixing different types of fabric ports is not supported. For example, you cannot configure a fabric link using one 10-Gigabit Ethernet interface and one 40-Gigabit Ethernet interface. Dedicated fabric links support only 10-Gigabit Ethernet interfaces.

Figure 8 shows the slot numbering for both of the Firewalls that become node 0 and node 1 of the chassis cluster after the cluster is formed.

Figure 8: Slot Numbering in SRX4600 Chassis Cluster Rear panel of Juniper SRX4600 with nodes labeled Node 0 and Node 1 in HA cluster. Features: control and fabric ports, interface slots for 40G/100G I/O, management ports, SSD drives, timing ports, alarm indicators, and power supply units.

Rear panel of Juniper SRX4600 with nodes labeled Node 0 and Node 1 in HA cluster. Features: control and fabric ports, interface slots for 40G/100G I/O, management ports, SSD drives, timing ports, alarm indicators, and power supply units.

Chassis Cluster Slot Numbering and Physical Port and Logical Interface Naming for SRX2300, SRX4120, SRX4100, SRX4200, and SRX4300 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.

The SRX4300 devices supports 1-Gigabit Ethernet labeled as CTL control port.

Supported fabric interface types for SRX4100 and SRX4200 devices are 10-Gigabit Ethernet (xe) (10-Gigabit Ethernet Interface SFP+ slots).

Table 6: Chassis Cluster Fabric Interface Details for SRX2300 and SRX4120
Ports with Port Speed	Used as Fabric Port?	Supports Z-Mode Traffic?	Supports MACsec?
8X 1/2.5/5/10-Gigabit Ethernet Interface SFPP	Yes	Yes	Yes
8x 1/10-Gigabit Ethernet Interface BASE-T RJ45	Yes	Yes	Yes
4X 1/10/25-Gigabit Ethernet Interface SFP28	Yes	Yes	Yes
2X 40/100-Gigabit Ethernet Interface QSFP28	Yes	No	Yes

Table 7: Chassis Cluster Fabric Interface Details for SRX4300
Ports with Port Speed	Used as Fabric Port?	Supports Z-Mode Traffic?	Supports MACsec?
8x1/2.5/5/10-Gigabit Ethernet Interface BASE-T RJ45.	Yes	Yes	Yes
8X1/10-Gigabit Ethernet Interface SFPP.	Yes	Yes	Yes
4X1/10/25-Gigabit Ethernet Interface SFP28.	Yes	Yes	Yes
6X 40/100-Gigabit Ethernet Interface QSFP28.	Yes	No	Yes
2X1-Gigabit Ethernet Interface SFP HA.	No	No	Yes

Table 8 shows the slot numbering, as well as the physical port and logical interface numbering, for both of the Firewalls that become node 0 and node 1 of the chassis cluster after the cluster is formed

Table 8: Chassis Cluster Slot Numbering, and Physical Port and Logical Interface Naming for SRX2300, SRX4120, SRX4100, SRX4200, and SRX4300 Firewalls
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
SRX2300 and SRX4120	Node 0	1	0	fxp0	Dedicated control port, em0/em1	Revenue interfaces are used for dual fabric links, fab0.
SRX2300 and SRX4120	Node 1	1	7	fxp0	Dedicated control port, em0/em1	Revenue interfaces are used for dual fabric links, fab1.
SRX4100	Node 0	1	0	fxp0	Dedicated control port, em0	Dedicated fabric port, any Ethernet port (for dual fabric-link), fab0
SRX4100	Node 1	1	7	fxp0	Dedicated control port, em0	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
SRX4200	Node 1	1	7	fxp0	Dedicated control port,em0	Dedicated fabric port, and any Ethernet port (for dual fabric-link), fab1
SRX4300	Node 0	1	0	fxp0	Dedicated control port, em0/em1	Revenue interfaces are used for dual fabric links, fab0
SRX4300	Node 1	1	7	fxp0	Dedicated control port, em0/em1	Revenue interfaces for dual fabric links, fab1

Figure 10 and Figure 11 shows the slot numbering for both of the Firewalls that become node 0 and node 1 of the chassis cluster after the cluster is formed.

Figure 9: Slot Numbering in SRX2300 and SRX4120 Rear view of Juniper Networks device showing Node 0 with green network interface modules in Slot 0 and Node 1 in Slot 7.

Rear view of Juniper Networks device showing Node 0 with green network interface modules in Slot 0 and Node 1 in Slot 7.

Figure 10: Slot Numbering in SRX4100 Chassis Cluster Front panel layout of two Juniper SRX4100 devices, Node 0 with Slot 0 and Node 1 with Slot 7, showing MGMT and Console ports for admin access and network interface ports for connectivity.

Front panel layout of two Juniper SRX4100 devices, Node 0 with Slot 0 and Node 1 with Slot 7, showing MGMT and Console ports for admin access and network interface ports for connectivity.

Figure 11: Slot Numbering in SRX4200 Chassis Cluster Front panel of two Juniper Networks SRX4200 devices labeled Node 0 and Node 1 in a cluster with slots and network ports for connectivity.

Front panel of two Juniper Networks SRX4200 devices labeled Node 0 and Node 1 in a cluster with slots and network ports for connectivity.

Figure 12: Slot Numbering in SRX4300 Chassis Cluster Rear view of a Juniper Networks device with two nodes labeled Node 0 in Slot 0 and Node 1 in Slot 7. Multiple network ports in green, management interfaces, and status LEDs are visible.

Rear view of a Juniper Networks device with two nodes labeled Node 0 in Slot 0 and Node 1 in Slot 7. Multiple network ports in green, management interfaces, and status LEDs are visible.

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 9 for interface renumbering on the Firewalls (SRX4100, SRX4200, and SRX4300).

Table 9: Chassis Cluster Interface Renumbering for SRX1600, SRX2300, SRX4120, SRX4100, SRX4200, and SRX4300
Device	Renumbering Constant	Node 0 Interface Name	Node 1 Interface Name
SRX1600	7	xe-0/1/0	xe-7/1/0
SRX2300 and SRX4120	7	xe-0/2/0	xe-7/2/0
SRX4100	7	xe-0/0/0	xe-7/0/0
SRX4200	7	xe-0/0/1	xe-7/0/1
SRX4300	7	xe-0/1/0	xe-7/1/0

On SRX4100 and SRX4200 devices, when the system boots in chassis cluster mode, the xe-0/0/8 and xe-7/0/8 interfaces are automatically configured as fabric links. You can configure an additional pair of fabric interfaces by using any supported pair of 10-Gigabit Ethernet interfaces to provide fabric connectivity between the nodes.

Note that the automatically created fabric interfaces cannot be deleted. However, the second pair of fabric interfaces that you can configure manually can be removed if needed.

Chassis Cluster Slot Numbering and Physical Port and Logical Interface Naming for SRX5000 Line of Firewalls

For chassis clustering, all Firewalls include a built-in management interface named fxp0. On most Firewalls, the fxp0 interface is a dedicated port.

For SRX5000 line of Firewalls, control interfaces are configured on SPCs.

Table 10 shows the slot numbering, as well as the physical port and logical interface numbering, for both of the Firewalls that become node 0 and node 1 of the chassis cluster after the cluster is formed.

Table 10: Chassis Cluster Slot Numbering, and Physical Port and Logical Interface Naming for SRX5000 Line of Firewalls
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
SRX5800	Node 0	12 (FPC slots)	0—11	Dedicated Gigabit Ethernet port	Control port on an SPC	Any Ethernet port
	Node 0		0—11	fxp0	em0	fab0
	Node 1		12—23	Dedicated Gigabit Ethernet port	Control port on an SPC	Any Ethernet port
	Node 1		12—23	fxp0	em0	fab1
SRX5600	Node 0	6 (FPC slots)	0—5	Dedicated Gigabit Ethernet port	Control port on an SPC	Any Ethernet port
	Node 0		0—5	fxp0	em0	fab0
	Node 1		6—11	Dedicated Gigabit Ethernet port	Control port on an SPC	Any Ethernet port
	Node 1		6—11	fxp0	em0	fab1
SRX5400	Node 0	3 (FPC slots)	0—2	Dedicated Gigabit Ethernet port	Control port on an SPC	Any Ethernet port
	Node 0		0—2	fxp0	em0	fab0
	Node 1		3—5	Dedicated Gigabit Ethernet port	Control port on an SPC	Any Ethernet port
	Node 1		3—5	fxp0	em0	fab1

Figure 13: Slot Numbering in SRX5800 Chassis Cluster Diagram of server hardware chassis with two nodes labeled Node 0 and Node 1, showing multiple numbered slots for modules.

Diagram of server hardware chassis with two nodes labeled Node 0 and Node 1, showing multiple numbered slots for modules.

FPC Slot Numbering in Firewall Cards

SRX5600 and SRX5800 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 Firewall. 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, port module is 0 for the left-hand slot or 1 for the right-hand slot.

SRX5400 Firewall 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)

Platform-Specific Chassis Cluster Slot Numbering Behavior

Use Feature Explorer to confirm platform and release support for specific features.

Use the following table to review platform-specific behaviors for your platform.

Platform	Difference
SRX Series	SRX340 and SRX345 Firewalls that support slot numbering, the fxp0 interface is a dedicated port. SRX300 and SRX320 Firewalls that support slot numbering, when 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. SRX300, SRX320, SRX340, SRX345, and SRX380 Firewalls that support slot numbering, when you enable chassis clustering and reboot the system, the built-in interface named ge-0/0/1 is repurposed as the control interface and is automatically renamed fxp1. SRX300, SRX320, SRX340, SRX345 and SRX380 Firewalls support only Gigabit Ethernet ports as the fabric link. SRX1500 Firewall that support slot numbering, includes 16 GE interfaces and 4 XE ports. SRX1600 Firewall that support slot numbering, includes 16 (1G), 4 (10G), 2 (25G), 2 (1G) ports. The 2 (1G) ports are HA control ports and are not used for forwarding traffic. SRX4600 Firewall that support slot numbering use dedicated HA control and fabric ports. SRX4100, SRX4200, and SRX4300 Firewalls support slot numbering but do not support direct attach copper (DAC) cables for chassis cluster control.

Platform

Difference

SRX Series

SRX340 and SRX345 Firewalls that support slot numbering, the fxp0 interface is a dedicated port.
SRX300 and SRX320 Firewalls that support slot numbering, when 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.
SRX300, SRX320, SRX340, SRX345, and SRX380 Firewalls that support slot numbering, when you enable chassis clustering and reboot the system, the built-in interface named ge-0/0/1 is repurposed as the control interface and is automatically renamed fxp1.
SRX300, SRX320, SRX340, SRX345 and SRX380 Firewalls support only Gigabit Ethernet ports as the fabric link.
SRX1500 Firewall that support slot numbering, includes 16 GE interfaces and 4 XE ports.
SRX1600 Firewall that support slot numbering, includes 16 (1G), 4 (10G), 2 (25G), 2 (1G) ports. The 2 (1G) ports are HA control ports and are not used for forwarding traffic.
SRX4600 Firewall that support slot numbering use dedicated HA control and fabric ports.
SRX4100, SRX4200, and SRX4300 Firewalls support slot numbering but do not support direct attach copper (DAC) cables for chassis cluster control.

ON THIS PAGE