Description

An SRX cluster was upgraded from Junos 25.2 to 25.4 using Security Director Cloud (SDC).

After the upgrade:

  • The primary cluster member (node0) was UP and connected to SDC.
  • The secondary cluster member (node1) was shown as Down in the SDC GUI.



Symptoms

On node1, show system services outbound-ssh clients detail showed that the service-deployment subsystem was not running.

Attempts to restart the service failed, and rebooting node1 did not resolve the issue.


Solution

This behavior is expected in Junos 25.4.

As confirmed by the SRX Engineering team, a code change was introduced in Junos 25.4 that prevents the SDXD service, which handles the outbound SSH client configuration, from running on the backup SRX cluster member.

Consequently, the secondary member cannot establish an outbound SSH connection to SDC and is therefore displayed as Down in the SDC portal.


Impact

This behavior does not impact SDC functionality.

SDC communicates with the SRX cluster through the active cluster member. Operations such as:

  • Policy updates
  • Signature database updates
  • Other SDC-to-SRX communications

continue to function normally.

Therefore, no action is required to start the SDXD or service-deployment subsystem on the backup cluster member.

Modification History

2026-09-24 : Article Created