Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I'm trying to demo (and learn) a Red Hat Cluster on ESXi 3.5 update2.I've set a shared fencing device with the info for my ESXi server. I try fencing a node from Luci, but it only tells me that fencing failed. Messages log has following agent "fence_vmware" reports: Unable to connec/login to fencing device. I checked and rechecked password and the connection properties.

Any ideas why this is happening. Is it possible to use ESXi as fencing?

share|improve this question
up vote 0 down vote accepted

I believe it is possible but ESXi's management interfaces might not respond quickly or reliably enough to make this as robust as it needs to be. There's some info on this here which seems to indicate that it's very much a work in progress but you may have something more supported that you are trying.

Since all you really need to do with Fencing is be able to trigger a VM reboot when certain conditions are met I don't see why it shouldn't work provided the fence scripts are sufficiently well written to be able to deal with the "latency" of the VCLI\VIX commands. One thing I have noticed with the various CLI tools is that authentication delays can be troublesome and may make this quite difficult.

share|improve this answer

Have you tried to manually run the script? The output might be a clue as to why it fails

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.