Dell Data Domain Storage discovery error : Connection to DDMC could not be established

[Rupam_P]

I am trying to discover Dell Data domain Storage devices by referring to below documentation 
Dell Data Domain storage discovery using Patterns

But getting error "Connection to DDMC could not be established or DDMC was not found! Terminating the pattern execution!" 
Discovery pattern error says as below

"Exception occurred while executing operation Dell DataDomain Operation. Custom operation Failed to run script due to the following error: JAVASCRIPT_CODE_FAILURE: com.snc.sw.exception.CommandFailureException: Failed to invoke HTTP call. Error Message: Connection failure for https://<ip_address>:port  (script_include:DellDataDomainApiCall; line 56)" 
{ip_address contanis target device ip and port value contains 3009 or 443 as configured. }

I have tried ping, telnet(3009, 443) from midserver to target device and they are successful. I also verified the credentials (username & password [type: BasicAuth]) by logging into device by midserver and I am able to login on target device using the credentials via direct url i.e. https://<ip_address>:port.

I am also not able to find the script include in my instance pointed in the pattern error i.e. "script_include:DellDataDomainApiCall; line 56". I am not sure if any such script include exists or not.

I have not done any customisation. Everything configured is OOB provided by servicenow.

Does anyone have any lead on what I might be missing or what I can do to resolve this error ? Any help would be appreciated.

Thanks in advance !

[Kieran Anson]

Hi,

The script include is a MID server script include which are stored in the ecc_agent_script_include table. Your error is occuring in the checkResponseAuth function because no response is being received as part of the 

HTTPRequest.post method.

You can enable additional logging, and view the MID logs to see whether the connection is timing out / being refused

[chaithra10]

I have the same exact problem.. did u find a solution yet?

[Rupam_P]

It was a SSL handshake failure, basically unsupported/untrusted certificate issue. Midserver was not supporting self-signed certificate from dell data management storage servers. A globally know CA signed certificate needs to be procured and uploaded in the cacerts file of midserver and also configured on target server. 

Once the appropriate certificates are in place, connection will be established.

Just to verify and test whether if its certificate issue only prior to procuring a signed certificate, a midserver security policy can be created to omit the certificate check {Name : IP of target / target fqdn ; Certifcate check : False}. 

Please accept the solution if you find it helpful.