Hi, I`m trying to use STONITH over HP iLO Interfaces for a XEN cluster with 2 Nodes.
I configured a STONITH resource for each iLO Interface as a clone resource with clone_max=1 and clone_node_max=1. Then i used order constraints to run the iLO resource to reboot xen node 2 on xen node 1. This works ok for me, but if I reboot or STONITH one node the STONITH resource which should run on this host doesn`t come back online. I have to manuely run a "Cleanup Resource" via the hb_gui and then the resource comes back online on this host. The STONITH resource can only run on one node in the cluster. If I reboot this node heartbeat tries to start the resource on the other node and that fails. How can I tell heartbeat that it should not try to start the STONITH resource an the other node? It should always stay on it node which it was configured for even if this node goes down. I`m using heartbeat-2.1.4 on SLES10SP2 with iLO2 interfaces of HP DL380G5 server. Can you perhaps give me an advice? Regards, Mario _______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
