Discovery of vCenter thru a firewall - ports needed?

[David77]

We've successfully Discovered vCenters w/in our firewall, but now need to do one outside our firewall. 
To date, I requested to have the following ports opened, however, (Jakarta) Discovery is still failing, so am asking which ports must be opened for a successful credentialed Discovery?  

TCP/22 - SSH

TCP/135 - WMi

TCP/445 - WMi 

TCP/443 - vCenter

TCP 902 - vCenter

The expectation is we will start with the vCenter and then move on to a few stand-alone physical servers running Windows or UNIX. 

Thanks. 

[stevefrancis]

vCenter discovery can be triggered in two different ways: from a process classifier or from a port probe.  If the process classifier is triggering it then 443 is the only port you need open.  If it's being triggered by a port probe then you also need port 9443 open.

[David77]

Steve, thanks ... how would I know if Discovery is doing a port probe or process classifier on my vCenter environment?  We are on Jakarta.   

[Ankush13]

AFAIK process classifier determines if vCenter process is running on the host being discovered. If that is true, subsequent probe VMWareProbe-VMWare - vCenter Datacenters is launched against the vCenter to get:

VMs, explored by the "VMWare - vCenter VMs" probe,
clusters, explored by the "VMWare - vCenter Clusters" probe,
datastores, explored by the "VMWare - vCenter Datastores" probe, and
networks, explored by the "VMWare - vCenter Networks" probe.

This probe's implementation is located in a MID server script include named VMWarevCenterDatacentersProbe.

[David77]

Thanks ... I have our SN admin see if he can look at the code to determine which ports it goes after. 

[Ankush13 · Accepted solution]

By default, the VMWare - vCenter Datacenters probe runs on port 443, which is the standard port for the https protocol. The port probes for vCenter run on these ports:

• vmapp6_https: 9443
• vmapp_https: 5480