You say RHEL6 cannot deal with external/ipmi ?
In cluster-glue-1.0.5-2.el6.x86_64.rpm you can
find /usr/lib64/stonith/plugins/external/ipmi
which is just a wrapper for ipmitool.
Around line 65 is : ${IPMITOOL} -I ${interface} -H ${ipaddr} -U "${userid}"
-P "${passwd}" ${action}
That can go with iDrac6, I tested it with FC17 for example.
Use with :
primitive stonith-vroip1 stonith:external/ipmi \
params hostname="ares1" ipaddr="192.168.10.253" userid="root"
passwd="p@ssw0rd" interface="lan" \
pcmk_host_check="static-list" pcmk_host_list="ares1" \
op start interval="0" timeout="60s" requires="nothing" \
op monitor interval="3600s" timeout="20s" requires="nothing"
2012/10/26 Marco Passerini <[email protected]>
> Hi,
>
> I'm trying to configure Stonith with Pacemaker on Dell servers (iDRAC7)
> and RHEL6.
> I'm new to the Stonith concept and I'm a bit confused as the
> configuration seems to be different on different OSes, hardware and
> pacemaker versions.
>
> Here's what I tried to do:
>
> First, I found this post in which they explained how to configure
> stonith with iDRAC6:
> http://lists.linux-ha.org/pipermail/linux-ha/2011-March/042779.html
>
> I added those settings with "racadm", however RHEL6 does not support
> stonith:external/ipmi.
>
> So I checked what is available and tried the following:
>
> # crm ra list stonith
> fence_pcmk
>
> ######################################
> [root@oss1 ~]# crm ra meta stonith:fence_pcmk
> stonith:fence_pcmk
>
> <!-- no value -->
>
> Parameters (* denotes required, [] the default):
>
> action (string, [reboot]): Fencing action (null, off, on, [reboot],
> status, hostlist, devstatus)
> stonith-timeout (time, [60s]): How long to wait for the STONITH action
> to complete.
> Overrides the stonith-timeout cluster property
>
> priority (integer, [0]): The priority of the stonith resource. The lower
> the number, the higher the priority.
> pcmk_host_argument (string, [port]): Advanced use only: An alternate
> parameter to supply instead of 'port'
> Some devices do not support the standard 'port' parameter or may
> provide additional ones.
> Use this to specify an alternate, device-specific, parameter that
> should indicate the machine to be fenced.
> A value of 'none' can be used to tell the cluster not to supply any
> additional parameters.
>
> pcmk_host_map (string): A mapping of host names to ports numbers for
> devices that do not support host names.
> Eg. node1:1;node2:2,3 would tell the cluster to use port 1 for
> node1 and ports 2 and 3 for node2
>
> pcmk_host_list (string): A list of machines controlled by this device
> (Optional unless pcmk_host_check=static-list).
> pcmk_host_check (string, [dynamic-list]): How to determin which machines
> are controlled by the device.
> Allowed values: dynamic-list (query the device), static-list (check
> the pcmk_host_list attribute), none (assume every device can fence every
> machine)
>
> pcmk_reboot_action (string, [reboot]): Advanced use only: An alternate
> command to run instead of 'reboot'
> Some devices do not support the standard commands or may provide
> additional ones.
> Use this to specify an alternate, device-specific, command that
> implements the 'reboot' action.
>
> pcmk_poweroff_action (string, [poweroff]): Advanced use only: An
> alternate command to run instead of 'poweroff'
> Some devices do not support the standard commands or may provide
> additional ones.
> Use this to specify an alternate, device-specific, command that
> implements the 'poweroff' action.
>
> pcmk_list_action (string, [list]): Advanced use only: An alternate
> command to run instead of 'list'
> Some devices do not support the standard commands or may provide
> additional ones.
> Use this to specify an alternate, device-specific, command that
> implements the 'list' action.
>
> pcmk_monitor_action (string, [monitor]): Advanced use only: An alternate
> command to run instead of 'monitor'
> Some devices do not support the standard commands or may provide
> additional ones.
> Use this to specify an alternate, device-specific, command that
> implements the 'monitor' action.
>
> pcmk_status_action (string, [status]): Advanced use only: An alternate
> command to run instead of 'status'
> Some devices do not support the standard commands or may provide
> additional ones.
> Use this to specify an alternate, device-specific, command that
> implements the 'status' action.
>
> Operations' defaults (advisory minimum):
>
> start timeout=20
> stop timeout=15
> status timeout=20
> monitor interval=3600 timeout=20
> ##########################################
>
>
> # crm configure primitive stonith_oss2 stonith:fence_pcmk \
> params pcmk_host_list="192.168.100.102"
>
>
> # stonith_admin -L
> stonith_oss1
> 1 devices found
>
> # stonith_admin -I
> fence_pcmk
> 1 devices found
>
> #crm_mon
> [...]
> stonith_oss1 (stonith:fence_pcmk): Started oss1
>
>
>
> What next? I'm not sure how to continue debugging the configuration.
>
> Wasn't I supposed to configure a userid and passwd on the fence_pcmk
> resource?
>
> Am I totally out of track?
>
> --
> Marco Passerini
> System Specialist
> CSC IT Center for Science
> Mobile: +358 50 381 8424
> E-Mail: [email protected]
>
> _______________________________________________
> Linux-HA mailing list
> [email protected]
> http://lists.linux-ha.org/mailman/listinfo/linux-ha
> See also: http://linux-ha.org/ReportingProblems
>
_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems
