Overview

Why are the vCenter names inconsistent when using discovery?

vCenter discovery

There are two type of vCenter discovery.

I.  vCenter is hosted on a Windows Server

II.  vCenter is on a linux appliance

Example

I.  When vCenter is installed on a Windows server. 

1. You will need to have the Windows Server Credentials as well as the vCenter Credentials
2. The windows credentials is to discovery the Windows server and check to see if there are any running process containing "vpxd
3. If it detects the process "vpxd" it kick off the process classifier "vCenter"

           http://instance.service-now.com/discovery_classy_proc.do?sys_id=9d5166150a0a0baf385aeb20686568b0&sysparm_record_target=discovery_classy_proc&sysparm_record_row=1&sysparm_record_rows=1&sysparm_record_list=nameCONTAINSvcenter%5EORDERBYorder

Since, vCenter is discovered via the process classifier name will be given in the following format vCenter@hostname

II.  When vCenter is an appliance on a Linux Server

1. We do not need the localhost credentials, only the vCenter credential
2. Since we do not discover the host system we do not get the name of the host system.
3. Since it's discovered without the discovering the host system the name will be vCenter@ip_address