[pve-devel] ha cluster with dell servers and drac fencing config + some remarks

Alexandre DERUMIER aderumier at odiso.com
Sat Jan 14 14:39:40 CET 2012

Hi, I have finished to test ha cluster with dell servers and drac card as fencing devices.
It's working great (and it's easy) !

Fencing works with drac card (tested with drac5, but it must work with drac6 with same syntax), through ssh.(enabled by default on drac card)

Here the config. 

    <fencedevice agent="fence_drac5" ipaddr="X.X.X.X" login="root" name="node1-drac" passwd="XXXX" secure="1"/>
    <fencedevice agent="fence_drac5" ipaddr="X.X.X.X" login="root" name="node2-drac" passwd="XXXX" secure="1"/>
    <fencedevice agent="fence_drac5" ipaddr="X.X.X.X" login="root" name="node3-drac" passwd="XXXX" secure="1"/>
    <clusternode name="node1" nodeid="1" votes="1">
       <method name="1">
        <device name="node1-drac"/>
    <clusternode name="node2" nodeid="2" votes="1">
       <method name="1">
        <device name="node2-drac"/>
   <clusternode name="node3" nodeid="3" votes="1">
       <method name="1">
        <device name="node3-drac"/>

Some remarks about HA :


It would by great to fence manually a dead node with pve-manager, if something goes wrong with fencing device or for users without fencing devices.
I can be done with command : "fence_ack_manual deadnodename"

So maybe add a right click option on a dead node,to manually fence it.


If I stop manually a vm managed by ha. (for maintenance by exemple, or maybe if don't need to have it started all the day), the node is restarted by HA automatically. I could be great if we could really stop it without remove the vm from ha management.

Not related to HA, but if a node goes down, we can't restart or move the vms manually on another node (with pve-manager).

-------------- next part --------------
A non-text attachment was scrubbed...
Name: aderumier.vcf
Type: text/x-vcard
Size: 183 bytes
Desc: not available
URL: <http://lists.proxmox.com/pipermail/pve-devel/attachments/20120114/79ad9275/attachment.vcf>

More information about the pve-devel mailing list