vCenter discovery fails - "None of url, username can be null"

[Tone2]

I have a problem discovering a particular vCenter. I have VMware credentials, and when I test these credentials against the vCenter they are successfully validated. But when I attempt discovery of the vCenter, it fails.

The input payload to the VMWareProbe contains these results:

error="Unable to establish connection to https://xx.xx.xx.xx/sdk: java.lang.NullPointerException: None of url, username can be null." probe_time="6345" result_code="900000"

The vCenter is on SUSE Linux - most of our other vCenters are on Windows so possibly there's some requirement I'm missing here?

[VivekSattanatha]

Hi Tone,

Your vCenter is an Linux appliance is not an issue. Ask your VMware team to provide your vCenter's web client URL. If you are able to access the URL from your MID Server then you are OK, otherwise this could be an firewall issue. 

Regards,

Vivek

[Tone2]

Hi Vivek

Thanks for your reply.

I've checked connectivity from the MID server and opening a web browser, navigating to the web client URL, and logging in with the credentials I'm using for discovery all works fine.

It's a mystery 😕

[VivekSattanatha]

Are you using 9443 port, when you open from web client or different port?

If it is different port then you have to configure accordingly because ServiceNow looks for 9443 only

https://docs.servicenow.com/bundle/kingston-it-operations-management/page/product/discovery/task/t_ConfigureAlternatePortForVCenter.html

Regards,

Vivek

[Tone2]

It's using the default ports as far as I'm aware. Perhaps I need to get more info about the vCenter configuration.

Thanks for your help.