Has anyone had any luck with the drac3 stonith plugin on RAC firmwares newer than 3.10 (Build 12.15)?
I'm using the drac3 plugin from the RHEL5 RPM heartbeat-common version 2.99.2 release 8.1 which I got from http://download.opensuse.org/repositories/server:/ha-clustering/RHEL_5 . When I first tried to run stonith -t drac3 host=[myip] login=root password=[mypass] -l on a drac3 IP, it complained of unresolved symbols in drac3.so - base64_to_binary and binary_to_base64. I was able to fix those problems by getting the SRPM from the above link and changing line 87 of lib/plugins/stonith/Makefile from am_drac3_la_OBJECTS = drac3.lo drac3_command.lo drac3_hash.lo \ to: am_drac3_la_OBJECTS = drac3.lo drac3_command.lo drac3_hash.lo ../../ clplumbing/base64.lo \ I then did a make clean && make in lib/plugins/stonith (after the normal rpmbuild --recompile had finished, of course) and voila - nm reported that base64_to_binary and binary_to_base64 were no longer undefined in drac3.so. Afterwards, stonith -t drac3 host=[myip] login=root password=[mypass] - l would succeed and print out the IP address of the host I connected to for a drac3 with firmware 3.10, but on a drac3 with firmware 3.38 (Build 12.14) it says: ** (process:13013): CRITICAL **: drac3_status: cannot log into Dell DRACIII Card at 137.238.4.167 137.238.4.167 RMC Webserver 2.0: error 411 occured malformed (Adding the -v flag to stonith doesn't add any output) My guess is that somewhere along the line Dell changed their authentication mechanism. I poked around the drac3 stonith source code a bit and it looks like there's a local function that hashes (or "does something") to the user/password. I scoured Dell's support site for documentation on drac3 but was unable to find anything about their authentication scheme. I've tried to downgrade the drac back to 3.10 only to experience strange issues: unresponsiveness to the point where I had to use the racadm command-line utility to hard-reset the drac, and the drac reporting unknown service tag/hardware model. I don't we're meant to downgrade the firmware on these guys. Has anyone else run into this problem? -David _______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
