vCenter Discovery

Amit39 · ‎01-31-2018

Hi,

I am trying to setup discovery for vCenter. So I am currently working with respective team to get the read only access to vCenter.

Do I need to work on credential stuff for vCenter discovery and may I know the next steps i need to follow to setup a successful discovery for vCenter.

Appreciate your quick help.

Thank you.

Regards,
Amit

Patrick DeCarl1 · ‎01-31-2018

Hi,

For vCenter, you just need a read only user within vcenter, create cred within SN and run a scan against the vcenter IP. SN discovery will do the rest.

"VMWare — vCenter credentials require a read only user that will be used to query the vCenter API when found as a running process or as a discovered vCenter appliance. "

Take a look at vCenter Discovery and process flow

View solution in original post

Patrick DeCarl1 · ‎02-05-2018

The message

Authentication failure with the local MID server service credential.

- Failed to access target system. Please check credentials and firewall settings on the target system to ensure accessibility: Access is denied

Means you don't have access to the Vcenter host device. Do you have correct access to the host that is running vcenter?

Amit39 · ‎02-05-2018

I can able to login to the vCenter with the provided IP using the credential used for discovery. While looking at the completed activities I can see the below details.

Discovery Status-> Devices-> Under CMDB CI (it's showing all the vcenters in this format "vCenter@X.X.X.X)

Completed activities showing "Active, couldn't classify: No WMI connection"

Tried these tests from source MID server.

1. gwmi win32_operatingsystem -Computer hostname -Credential domain\username

2. wbemtest

both gets "RPC is unavailable error"

3. From source MID machine, telnet is successful for 443, 135port.

May I also know if 445, 5985, 5986 9443 ports are also required to be open.

Patrick DeCarl1 · ‎02-05-2018

That is not how vcenter discovery works. SN will discover a devices, see that a running process for vcenter and then make the call the vcenter. So if you cant discovery the vcenter host devices then you won't kick off the probe for vcenter.

Ashutosh Munot1 · ‎02-05-2018

HI,

I agree, if you are not able to enter how it will execute a command, give back the xml to mid server and then probes will trigger and then other process.

What i recommend is to use Putty for you test.

Thanks

Amit39 · ‎02-05-2018

Thank you for the information. So it means the IP of vCenter where I got read only access with the community domain account is not enough. May I know the next step please and what and where I need to make fix this to make successful discovery.

Appreciate your help.