[Linux-cluster] problems with fence_vmware_soap and vCenter server 4 / ESX 4
andreas at hastexo.com
Wed Dec 28 23:03:42 UTC 2011
On 12/27/2011 11:20 PM, Matias Kreder wrote:
> hi all,
> I am having troubles while using fence_vmware_soap to get the VM list
> and any other operation.
> fence_vmware_soap -l user -p pass -a 192.168.1.11 -o list -z
> My user has full admin privileges. 192.168.1.11 is the vCenter IP
> address running on Windows 2008. vCenter is controlling only 1 ESX 4
from the man page ...
fence_vmware_soap is an I/O Fencing agent which can be used with the
virtual machines managed by VMWare products that have SOAP API v4.1+.
... v4.1+ ... you have "plain" 4? Don't even know if the version is
directly related to ESX version, but looks "suspicious" to me ;-)
hth - regards,
Need help with Pacemaker?
> Doing the same thing against the ESX shows the same issue:
> fence_vmware_soap -l root -p pass -a 192.168.1.12 -o list -z
> Failed: Unable to obtain correct plug status or plug is not available
> Looks like it is connecting and authenticating properly because if I
> use a fake password it fails with "Unable to connect/login to fencing
> Please advice
> Matias Kreder
> Linux-cluster mailing list
> Linux-cluster at redhat.com
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 286 bytes
Desc: OpenPGP digital signature
More information about the Linux-cluster