vCenter probe timeout when target IP does not respond - Support and Troubleshooting

vCenter probe timeout when target IP does not respond Issue  Symptoms During discovery, VMWarevCenterDatacentersProbe launches and never finishes, thus causing the discovery schedule to terminate after its max run time.

Cause During discovery, Shazzam probe may have identified an IP with 5480 or 9443 port open. This IP may not respond if this is not a vCenter and may cause VMWarevCenterDatacentersProbe to never respond and discovery would timeout subsequently.

Resolution As the IP is not a vCenter IP, port 5480 or 9443 should be disabled on suspected IP. For any reason, if disabling these ports is not an option, a new probe parameter named "prevalidate_vcenter" can be added to "VMWare - vCenter Datacenters" probe. This is used to validate if the vCenter is responding with an HTTP request timeout of 30000 milliseconds by default. Follow below steps to set this property. Navigate to Discovery Definition --> Probes Search and open probe " VMWare - vCenter Datacenters " Goto Probe Parameters related list. If not available configure to have this added Add new property " prevalidate_vcenter " with value = "true" to the parameters list.