Hi All - 
 
I've spent some time searching some threads on how to get drac5 and stonith 
working properly.
 
I've seen the post from Thomas Paschy who modified the drac3 module to make it 
work for drac5.  I'm not a programmer or developer but thought I take a shot at 
compiling the program.  I tried a gcc on the drac5.c but that didn't seem to 
work.
 
So, I moved onto trying the ipmilan stonith device, but this produced 
segmentation faults and it looks like from previous posts that ipmilan has been 
buggy but possibly fixed recently from a post in Feb from Martin Bene. 
 
I than saw a post from Peter Clapham on how he wrote his own shell script to be 
an external stonith module.  The script called ipmitool.  But this was for 
heartbeat 2.  I'm using heartbeat 1.  However, this gave me a clue that I could 
probably due something very similar for heartbeat one.
 
Here's my setup for implementing external stonith device for drac5 using 
heartbeat version 1.
 
1) Install ipmitool rpm package.
2) Enable IPMI on DRAC Card - Its disabled by default. 
3) Add these 2 lines to /etc/ha.d/ha.cf
            # Warning: stonith.drac must be different by referencing the other 
node in the cluster.
            stonith external /etc/ha.d/conf/stonith.drac
4) Add this line to /etc/ha.d/conf/stonith.drac
            node2 ipmitool -I lan -H drac-node2 -U user -P password chassis 
power cycle
 
To manually test the stonith type:
 
stonith -t external -F /etc/ha.d/conf/stonith.drac node2
 
To test if called properly from heartbeat, I simulated a kernel panic by 
issuing this command
on one of the nodes in the cluster.
 
echo 1 > /proc/sys/kernel/sysrq
echo d > /proc/sysrq-trigger.
 
I than watched from the drac console and confirmed that stonith power cycled 
the other server.
 
One downside to this method is having to manage separate copies of stonith.drac 
on each node.  
 
This has been tested on SLES 9 SP3 32bit.  heartbeat-stonith-1.2.3-2.9, 
heartbeat-1.2.3-2.9
Hopefully someone out there will find this setup useful.
 
Best Regards,
 
Dave
_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems

Reply via email to