This article explains the prerequisite and troubleshooting steps for device discovery in Juniper Security Director Cloud.

• Unable to add a device to Security Director Cloud

• Device discovery job not initiating

• Device Connection Status displaying Discovery Not Initiated

For more details, see Add Devices to Juniper Security Director Cloud.

Before adding, you must open the following ports of your device so that it communicates with Juniper Security Director Cloud:
 

• TCP/53 (DNS) - (IP: 8.8.8.8) to allow google DNS server

• UDP/53 (DNS) - (IP: 8.8.4.4) to allow google DNS server

Troubleshoot to check connectivity from an SRX device to the Security Director Cloud server:

1. Ensure that the SRX device can reach the Internet:

> ping 8.8.8.8

2. Check if 7804 port is open (from the SRX device):

> telnet srx.sdcloud.juniperclouds.net port 7804

3. Check if the SRX device is resolving the SD Cloud host:

> ping srx.sdcloud.juniperclouds.net

4. Check if the name server (DNS) is configured in the SRX device.

> show configuration | display set | grep name-server

5. Check the connection after committing the outbound-ssh configuration on SRX:

> show system connections | match 7804

6. Check for any configured filter on the SRX device, it should not block the outbound or inbound connection for Juniper Security Director Cloud portal from the out going interface.

> show configuration | display set | match filter

7. You can also check log messages on the SRX device:

> show log messages | last 20

8. Check if the device you are adding is supported and on the supported Junos version:

See Juniper Security Director Cloud Release Notes for more information about supported platforms.
 

9. If you are adding an SRX cluster then make sure it does have outbound-ssh configuration only at group level.

10. If you are discovering an SRX cluster with management from a routing-instance. 

        Check the routes and test connectivity:

            > show route srx.sdcloud.juniperclouds.net

            > telnet srx.sdcloud.juniperclouds.net port 7804 routing-instance <routing-instance Name>

    
        Configure the outbound-ssh to the correct routing-instance: 

            set groups node0 system services outbound-ssh routing-instance <routing-instance Name>
            set groups node1 system services outbound-ssh routing-instance <routing-instance Name>

    
    Note: Check KB35686 > SRX345 DNS query through fxp0 does not work when fxp0 belongs to routing instance mgmt_junos [juniper.net]

    
        For Security log add the working routing-instance:

            set security log stream sd-cloud-logs host routing-instance <routing-instance Name>

If the issue continues, please contact Juniper Support.
 

2024-02-05 : Article Created
2024-04-26: Added a line for SRX Cluster
2024-05-16: typo cleared
2024-08-25: Added additional region's FQDN

2025-09-10: Adding SRX cluster with routing-instance

https://www.juniper.net/documentation/us/en/software/sd-cloud/sd-cloud/topics/topic-map/sd-cloud-devices-onboarding.html