[Linux-cluster] iLo3 and RedHat 5.5 : Unable to connect/login to fencing device

[Mika i]

this works:
ipmitool -H xxxxxilo -I lanplus -U admin -P xxxxxx chassis power cycle
Server is rebooted.....

but not this:
root at fff fence_ipmilan -a xxxxxxxxlo -l admin -p xxxxxxxxx -M 'cycle' -v
Rebooting machine @ IPMI:xxixxxxxilo...Spawning: '/usr/bin/ipmitool -I lan
-H 'xxxxxxx' -U 'admin' -P 'xxxxx41!' -v chassis power status'...
Spawning: '/usr/bin/ipmitool -I lan -H 'xxxxxxx' -U 'admin' -P 'xxxxxx1!' -v
chassis power cycle'...
Failed

cluster.conf
....
                                <method name="1">
                                        <device lanplus="1"
name="xxxxxx_xxxxdev" timeout="20"/>
......

<fencedevice agent="fence_ipmilan" auth="none" ipaddr="xxxxxxxilo"
login="admin" method="cycle" name="xxxxuxx32_fencedev" passwd="xxxxx!"/>






2011/3/3 שלום קלמר <sklemer at gmail.com>

> Hi.
> for ilo3 testing you can use :
> # fence_ipmilan -a 17x.3x.7x.1xx -p "password" -o status
>
>   fence_ipmilan -h
> usage: fence_ipmilan <options>
>    -A <authtype>  IPMI Lan Auth type (md5, password, or none)
>    -a <ipaddr>    IPMI Lan IP to talk to
>    -i <ipaddr>    IPMI Lan IP to talk to (deprecated, use -a)
>    -p <password>  Password (if required) to control power on
>                   IPMI device
>    -P             Use Lanplus
>    -S <path>      Script to retrieve password (if required)
>    -l <login>     Username/Login (if required) to control power
>                   on IPMI device
>    -o <op>        Operation to perform.
>                   Valid operations: on, off, reboot, status
>    -t <timeout>   Timeout (sec) for IPMI operation (default 20)
>    -C <cipher>    Ciphersuite to use (same as ipmitool -C parameter)
>    -M <method>    Method to fence (onoff or cycle (default onoff)
>    -V             Print version and exit
>    -v             Verbose mode
>
> If no options are specified, the following options will be read
> from standard input (one per line):
>
>    auth=<auth>           Same as -A
>    ipaddr=<#>            Same as -a
>    passwd=<pass>         Same as -p
>    passwd_script=<path>  Same as -S
>    lanplus               Same as -P
>    login=<login>         Same as -u
>    option=<op>           Same as -o
>    operation=<op>        Same as -o
>    action=<op>           Same as -o
>    timeout=<timeout>     Same as -t
>    cipher=<cipher>       Same as -C
>    method=<method>       Same as -M
>    verbose               Same as -v
>
>
> On Thu, Mar 3, 2011 at 12:21 PM, Mika i <mika68vaan at gmail.com> wrote:
>
>> hmm.
>> Okey: have someone good installation instructions to get this fence_ipmilan to
>> work.
>> 1. active IPMI/DCMI over LAN in iLo3
>> 2. what should i install in server to get fence_ipmilan to work
>> Now if i test connection it shows like this.
>>
>> ipmitool -v -H 17x.3x.7x.1xx -I lanplus -U admin mc info
>> Password:
>> Get Auth Capabilities error
>> Get Auth Capabilities error
>> Error issuing Get Channel Authentication Capabilies request
>> Error: Unable to establish IPMI v2 / RMCP+ session
>> Get Device ID command failed
>>
>> Can someone help me!
>> 2011/3/2 <Jason_Henderson at mitel.com>
>>
>>>
>>>
>>> linux-cluster-bounces at redhat.com wrote on 03/02/2011 10:07:38 AM:
>>>
>>> > Hi
>>>  >
>>> > Is there a way to get cluster-suite Fence to work with Rhel 5.5 and
>>> iLo3
>>> > I have now in both clusters rhel 5.5 version with:
>>> > kernel 2.6.18-194.el5
>>> > cman-2.0.115-68.el5_6.1
>>> >
>>> > But in fence state i get allways message: Unable to connect/login to
>>> > fencing device
>>> >
>>> > Any help - or must i update the cluster to rhel 5.6?
>>>
>>> What fence agent are you using, fence_ilo?
>>> You will need to use the fence_ipmilan agent for iLO3.
>>> --
>>> Linux-cluster mailing list
>>> Linux-cluster at redhat.com
>>> https://www.redhat.com/mailman/listinfo/linux-cluster
>>>
>>
>>
>> --
>> Linux-cluster mailing list
>> Linux-cluster at redhat.com
>> https://www.redhat.com/mailman/listinfo/linux-cluster
>>
>
>
> --
> Linux-cluster mailing list
> Linux-cluster at redhat.com
> https://www.redhat.com/mailman/listinfo/linux-cluster
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/linux-cluster/attachments/20110303/3832ad3f/attachment.htm>