vCenter probe hangs when target does not respond on port and causes discovery schedule to be cancelled - Support and Troubleshooting

vCenter probe hangs when target does not respond on port and causes discovery schedule to be cancelled Description Overview vCenter probes may be triggered incorrectly when discovering IPs where there is no vcenter application. The probe then hangs when the target does not respond. This will cause the discovery schedule to be cancelled if there is a maximum time configured, or be stuck if a maximum time is not configured.

Steps to reproduce Open "Discovery Definition > IP Services" Search for records where name contains "vmap" and collect the number from the port column Discover a device where such ports are open but no vcenter application is installed The probes will be triggered and hang Root Cause The first phase of discovery, Shazzam, checks for open ports on a target IP address. Probes will be triggered accordingly depending on the open ports. Such ports can be configured under "Discovery Definition > IP Services".

Solution The issue is resolved via PRB1073935 in Kingston. Starting in kingston, a probe parameter was created to pre-validate the vcenter application before sending requests.

To turn on pre-validation:

Go to "Discovery Definition > Probes" Open the "VMWare - vCenter Datacenters" probe Add parameter prevalidate_vcenter = true For versions prior to Kingston, or depending on the kingston release, the fix can be back ported as follows:

Warning: Any changes should be tested in non-production instances first

Add prevalidate_vcenter = true parameter to "VMWare - vCenter Datacenters" probe Go to "MID Server > Script Includes" Open "AVMWareProbe" Add the following code before the line containing "this._getServiceInstance();" if (this.getParameter('prevalidate_vcenter') == 'true') { request = new Packages.com.glide.communications.HTTPRequest(this.vmHost + '/vimservice.wsdl'); request.setContentType('application/xml'); request.setHttpTimeout(30000); response = request.post(' ' + ' 'xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" ' + 'xmlns:xsd="http://www.w3.org/2001/XMLSchema" ' + 'xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">' + ' ' + ' ServiceInstance ' + ' ');

if (!response || (response.getStatusCode() != 200)) { this.setError('Not exploring as vCenter: unable to fetch WSDL. The WSDL check is controller by the probe parameter "check_wsdl".'); return; } }