This article explains what all to check if you are not able to onboard the device to SDOP.

Device onboarding fails on SDOP.

Device remains in Unknown state even after copy and paste of the config to the device.

Device discovery job not initiating

Device Connection Status displaying Discovery Not Initiated

Check for the following in such cases:

• Ensure that the SRX device can reach the SDOP Device Connection IP address

> ping <SDoP device connection IP>

In some cases, this may be blocked. So you need to check if telnet is working. 

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

> telnet <SDoP device connection IP> port 7804

This is a must.

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

> show system connections | match 7804

If there are any stale entries, clear the connection with the command:

clear system outbound-ssh client connection all

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

> show configuration | display set | match filter

• You can also check log messages on the SRX device: 

> show log messages | last 20

If the log messages do not show the sduser even attempting to connect to the SRX, then that means that the SDoP is not able to reach the device using ssh. Check for any firewalls in between which could be blocking the connection.