'fence_vmware_soap' fencing is working on command line and 'fence_node' is failing.
Issue
- 'fence_vmware_soap' fencing is working on command line and 'fence_node' is failing.
Nodes are getting rebooted with the commands
fence_vmware_soap -a 192.168.1.254 -l administrator -p <password> -z --action reboot -U 111111-111-1111-111-111111
fence_vmware_soap -a 192.168.1.254 -l administrator -p <password> -z --action reboot -U 22222-222-2222-222-222222
and 'fence_node" fails as
[root@node02 ~]# fence_node node01
fence node01 failed
Configuration in /etc/cluster/cluster.conf file is seen as
<fencedevices>
<fencedevice agent="fence_vmware_soap" ipaddr="node01" login="administrator" name="Fence_node01" passwd="***" ssl="1"/>
<fencedevice agent="fence_vmware_soap" ipaddr="node02" login="administrator" name="Fence_node02" passwd="***" ssl="1"/>
</fencedevices>
Environment
- Red Hat Enterprise Linux Server 5 (with the High Availability and Resilient Storage Add Ons)
- fence_vmware_soap fencing agent
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.