this needed to active in cluster.conf, then everything started to work.
power_wait="15"
-Mika
2011/3/4 Omer Faruk SEN <omerfsen@xxxxxxxxx>
See https://access.redhat.com/kb/docs/DOC-39336
2011/3/3 Â<Jason_Henderson@xxxxxxxxx>:
>
>
> linux-cluster-bounces@xxxxxxxxxx wrote on 03/03/2011 02:44:18 PM:
>
>> When i added -P likeÂdownÂhere:
>> fence_ipmilan -P -a xxxxxxxxlo -l admin -p xxxxxxxxx -M 'cycle' -v
>> Everything works, server reboots. But how do i get this "-P" option
>> included in fence_ipmilan.
>> How should my cluster.conf look like..that's the question...
>
> Here is an example with passwords removed:
>
> <cluster name="88423a6c34c04d" config_version="3">
>
> Â <totem token="10000"/>
> Â <cman port="6809" expected_votes="1" two_node="1" broadcast="no"/>
> Â <logging syslog_facility="local3"/>
>
> Â <fencedevices>
> Â Â <fencedevice name="manual" agent="fence_manual"/>
> Â Â <fencedevice name="ilo" agent="fence_ipmilan"/>
> Â Â <fencedevice name="ilom" agent="fence_npm_ilom"/>
> Â </fencedevices>
>
> Â <clusternodes>
> Â Â <clusternode name="node1" votes="1" nodeid="1">
> Â Â Â <fence>
> Â Â Â Â <method name="method1">
> Â Â Â Â Â <device name="ilo" passwd="12345678" lanplus="1" method="cycle"
> login="user" ipaddr="10.39.170.233"/>
> Â Â Â Â </method>
> Â Â Â </fence>
> Â Â </clusternode>
> Â Â <clusternode name="node2" votes="1" nodeid="2">
> Â Â Â <fence>
> Â Â Â Â <method name="method2">
> Â Â Â Â Â <device name="ilo" passwd="12345678" lanplus="1" method="cycle"
> login="user" ipaddr="10.39.170.234"/>
> Â Â Â Â </method>
> Â Â Â </fence>
> Â Â </clusternode>
> Â </clusternodes>
>
> </cluster>
>
>
>> 2011/3/3 ×××× ×××× <sklemer@xxxxxxxxx>
>> 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 defaultmethod
>> 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
>> --
>> 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
