This article describes the issue of  the SRX device not being manageable via the fxp0 interface, when the node is in the disable state.

• If the device goes into the disable state, it disables all the interfaces on the data plane.
• As it does not have a dedicated management interface (SRX high-end devices have a dedicated revenue interface for fxp0) , it will not be able to access the disabled node due to all the interfaces being disabled.
• It is by design. When the firewall goes into the disable state, it will detect that something went wrong with the data plane; as a result, it will become isolated from the network.
• For example, if the device is in the disable state due to fab link failure, the control links will still communicate with themselves and announce the other node as disabled.
• So, the data plane will be in the disable mode; but the control plane will still work. You can see from the output of show chassis cluster statistics that the heart beat will be exchanged between the two nodes.

If management access via the fxp0 interface of the disabled node is lost, you can still access the disabled node via the primary node.

Temporary workaround :

1. Logon to the primary node via SSH.
2. Execute the following command:
   

   request routing-engine login node 1 (id for disable-node)

3. Now, you will be able to logon to the disabled node (you can reboot the device via the CLI).