This article explains why the management access to a SRX Chassis Cluster node is lost when it goes to Disable state.

Management access to a SRX Chassis Cluster node is lost after it goes to Disable state.

When there is a control link failure in a Chassis Cluster environment the node acting as Secondary for Redundancy-group 0 will go into the Disable state and its onboard interfaces are disabled in order to avoid a split brain scenario in the network.

The following SRX branch devices do not have a dedicated management port so when they are set to cluster mode, its fxp0 interface is defined through an onboard port and because these ports are disabled in the Disabled state, the management access to this node will be lost.

SRX100
SRX110
SRX210
SRX220
SRX240      For example, when SRX240 is set for Chassis Cluster its ge-0/0/0 interface becomes the fxp0 interface. 
SRX300
SRX320
SRX550
SRX650

The mentioned problem is only noticed in the above platforms.

This is a design limitation and will occur as long as the node is in the Disable state.

If control-link-recovery  is not configured, the only way to recover a node from the Disabled state is by manually rebooting it.




 

2020-06-29: Refreshed article with the latest models and added more clarity.