Description

This article provides information on how interfaces are assigned on SRX platforms when the chassis cluster is enabled.

 

Symptoms

When chassis cluster mode is enabled on SRX platforms, certain interfaces are required for chassis cluster interconnection and out-of-band management. So, it is important to know how the interfaces are assigned in chassis cluster mode to avoid inadvertently using any of the assigned interfaces incorrectly.

 

Solution

Refer to the following table:

Device

Management (fxp0)

HA Control
(fxp1 or em0/em1)

Fabric (fab0 & fab1)
Must be configured

SRX100

fe-0/0/6 fe-0/0/7 => fxp1 Any available FE Interface

SRX110

NA NA NA

SRX210

fe-0/0/6 fe-0/0/7 => fxp1 Any available FE or GE Interface

SRX220

ge-0/0/6 ge-0/0/7 => fxp1 Any available GE Interface

SRX240

ge-0/0/0 ge-0/0/1 => fxp1 Any available GE Interface

SRX550 & SRX550HM

ge-0/0/0

ge-0/0/1 => fxp1

Any available GE or XE Interface
(copper or fiber)

SRX650 ge-0/0/0 ge-0/0/1 => fxp1 Any available GE or XE Interface
(copper of fiber)

SRX300

ge-0/0/0

ge-0/0/1 => fxp1

Any available GE Interface

SRX320

ge-0/0/0 ge-0/0/1 => fxp1 Any available GE Interface

SRX340, SRX345
SRX380

Mgmt ge-0/0/1 => fxp1 Any available GE Interface

SRX1400

RE Ethernet Port on SYSIO

ge-0/0/10(copper or fiber) on SYSIO => em0
ge-0/0/11 (fiber only) on SYSIO          => em1

Any available GE or XE Interface
(copper or filber)

SRX1500

Mgmt Dedicated Control Port => em0

Any available GE or XE Interface
(copper or fiber)

SRX3400 RE Ethernet port 0 on SFB

Chassis Cluster Control *1
Port 0 (copper or fiber) on SFB    => em0
Port 1 (copper or fiber) on SFB    => em1 

Any available GE or XE Interface
(copper or fiber)

SRX3600
SRX4100 Mgmt Dedicated Control Port => em0

Dedicated Fabric Port
or
Any Ethernet Port (for dual fabric)

SRX4200
SRX4600 Mgmt Dedicated Control Ports => em0
(xe-0/0/0 & xe-0/0/1)

Dedicated XE Fabric *2
or
Any available QSFP Interface

SRX5400 Ethernet Port on RE

Chassis Cluster Control

   Note: SPC / Port is based on config


Port 0 on SPC    => em0 (fiber only) 

   set chassis cluster control-ports fpc X port 0


Port 1 on SPC    => em1 (fiber only) *3 

  set chassis cluster control-ports fpc X port 1
 Any available GE or XE Interface
(fiber only)
SRX5600
SRX5800
vSRX NIC1 / eth0 => fxp0 NIC2 / eth1 => em0

Any available

 

  • *1 - SRX3k supports dual control links when equipped with Chassis Redundancy Modules (CRM).

  • *2 - SRX4600 provides dedicated fabric ports (xe-0/0/2 & xe-0/0/3) as of Junos OS 18.3R3, 18.4R3, 19.1R2, 19.2R2, 19.3R1, and later codes which have to be configured explicitly.

  • *3 - Secondary Control link available for SRX5600 and SRX5800 when using dual routing-engines.

 

For detailed port information, you can refer to the following links:

For troubleshooting any issue with the chassis cluster for SRX, refer to the following guide:

 

Modification History

  • 2020-07-17: Added information that SRX4600 dedicated fabric port has to be configured explicitly

  • 2020-04-27: Updated related links for Slot Numbering

  • 2020-04-10: Updated link information for SRX380 and clarity on dual control link supported devices

  • 2020-01-16: Removed J-Series information; updated support for SRX4600 Dedicated Fabric links

  • 2019-06-18: Added port mappings for vSRX

  • 2019-06-13: Added information about SRX4600 as well with current limitation on Dedicated Fabric

 

Related Information