Re: iLo3 and RedHat 5.5 : Unable to connect/login to fencing device

×××× ×××× <sklemer@xxxxxxxxx> · Thu, 3 Mar 2011 19:25:12 +0200

H.
Maybe iLo3 dont support cycle. why not to use the default , which is "onoff" . Try it

I think its good enough .

-M method
ÂÂ Â Â Â Â Â ÂMethod to fence (onoff or cycle). Default is onoff. Use cycle in
ÂÂ Â Â Â Â Â Âcase Âyour management card will power off with default method so
ÂÂ Â Â Â Â Â Âthere will be no chance to power machine on by IPMI.

On Thu, Mar 3, 2011 at 3:53 PM, Mika i <mika68vaan@xxxxxxxxx> wrote:

this works:
ipmitool -H xxxxxilo -I lanplus -U admin -P xxxxxx chassis power cycle
Server is rebooted.....
Â
but not this:
root@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@xxxxxxxxx>

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="" Â Â Â Â Â 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@xxxxxxxxx> 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@xxxxxxxxx>

linux-cluster-bounces@xxxxxxxxxx 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@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/linux-cluster

--
Linux-cluster mailing list
Linux-cluster@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/linux-cluster

--
Linux-cluster mailing list
Linux-cluster@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/linux-cluster

--

Linux-cluster mailing list

Linux-cluster@xxxxxxxxxx

https://www.redhat.com/mailman/listinfo/linux-cluster

--
Linux-cluster mailing list
Linux-cluster@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/linux-cluster