Showing results for 
Show  only  | Search instead for 
Did you mean: 

IBM PVU Scanning a vCenter

Hi All,  I've been having some trouble with the IBM PVU VMWare cluster scanning recently.  The VMWareInventory.log  shows:

2020-06-04 15:05:25,202 [.VirtualizationVisitor|rules-2] [INFO ] Queued virtualization inventory execution on device '<ipv4.vcenter.address>' using protocol https and port 443
2020-06-04 15:06:41,226 [.VirtualizationVisitor|rules-2] [INFO ] ---------------------------------------------------------------------------------------------------------------------
2020-06-04 15:06:41,226 [.VirtualizationVisitor|rules-2] [INFO ] Finished processing task of type 'TaskType_V12nInventory' on target '<ipv4.vcenter.address>' with result '-1'
2020-06-04 15:06:41,226 [.VirtualizationVisitor|rules-2] [INFO ] Result of type 'TaskType_V12nInventory' on target '<ipv4.vcenter.address>':
<TaskStatus Result="Failed" StartDateTime="2020-06-04T15:05:25" Type="VirtualInventory" Status="VMwareInfrastructureConnectFailed" Duration="75.00">
<Message>Failed to retrieve contents from web service https://<ipv4.vcenter.address>:443/sdk</Message>
<Message>An error occured in HTTP processing</Message>
<Message>HTTP response code 504</Message>

Our vCenters are using 6.7u3f  update version.   The url https://<ipv4.vcenter.address>:443/sdk   doesn't seem to be a valid URL in this version of the vCenter.  Is there a known problem with gathering vm info using this API on this vCenter version? I know the vCenter is up and running and has many VM's on it.

(1) Reply
By Level 6 Flexeran
Level 6 Flexeran

The 504 error being seen looks to be a timeout error

The server, while acting as a gateway or proxy, did not receive a timely response from an upstream server it needed to access in order to complete the request.

To troubleshoot HTTP 504 errors you can check the configurations on your firewall, proxy, and security groups and the best way to test if the Inventory Beacon Server has access to the VMware vCenter/Host is through a Web Browser with the following link, while having any Internet Proxies disabled (vimService.wsdl is case sensitive!):

https://IPAddress:PortNumber/sdk/vimService.wsdl (e.g.

If you get an xml-formatted page or a login screen, then the test passed. If you get a "page not found" error, try the following to make sure it's not a firewall issue which this link should ask you for a login if it passed the firewall:

https://IPAddress:PortNumber/MOB (e.g.

Additional information can be found in the KB article below: