Summary:
This article provides information on how interfaces are assigned on J-Series and SRX platforms, when the chassis cluster is enabled.
Symptoms:
When the chassis cluster mode is enabled on J-Series and 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 the 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
|
| J2320 |
ge-0/0/2 |
ge-0/0/3 => fxp1 |
Any available GE Interface |
| J2350 |
ge-0/0/2 |
ge-0/0/3 => fxp1 |
Any available GE Interface |
| J4350 & J6350 |
ge-0/0/2 |
ge-0/0/3 => fxp1 |
Any available GE Interface |
| 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 |
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
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
and
any Ethernet Port (for dual fabric) |
| SRX4200 |
| SRX4600 |
Mgmt |
Dedicated Control Ports => em0
(xe-0/0/0 & xe-0/0/1) |
Any available QSFP, GE or XE Interface *1 |
| SRX5400 |
Ethernet Port on RE |
Chassis Cluster Control
Ports have to be configured
Port 0 (fiber only) on SPC => em0
Port 1 (fiber only) on SPC => em1 |
Any available GE or XE Interface
(fiber only) |
| SRX5600 |
| SRX5800 |
| vSRX |
NIC1 / eth0 => fxp0 |
NIC2 / eth1 => em0 |
Any available
NIC3 / eth2 maps to ge-0/0/0 |
*1 - SRX4600 provides dedicated fabric ports (xe-0/0/2 & xe-0/0/3), however as of 6/13/2019 these are currently unsupported for fabric use.
The table refers to the physical ports on each member node. The port number from Junos CLI will actually change on each node (that is, on J-Series, eg. J4350 or J6450,
node0 will have
ge-0/0/2 and
node1 will have
ge-7/0/2 ).
The other interfaces are also renamed on the secondary device. For example, on a J2320 router, the
ge-0/0/0 interface on
node 0 is renamed as
ge-4/0/0 on
node 1.
For detailed port information you can refer to the following links:
J-Series - J2320, J2350, J4350, J6350
SRX Branch Series - SRX100, SRX110, SRX210, SRX220, SRX240, SRX550, SRX650
SRX Next Gen Series - SRX300, SRX320, SRX340, SRX345, SRX1500
SRX High End Series - SRX4100, SRX4200
SRX High End Series - SRX1400, SRX3400, SRX3600, SRX5400, SRX5600, SRX5800
For troubleshooting any issue with the chassis cluster for SRX, refer to the following guide:
Resolution Guide SRX Chassis Cluster (High Availablity)
6/13/2019 Added information about SRX4600 as well with current limitation on Dedicated Fabric
6/18/2019 Added port mappings for vSRX
Related Links:
[KB15356] Show Article Properties
[KB15356] Hide Article Properties
