<tt>linux-cluster-bounces@redhat.com wrote on 03/03/2011 02:44:18 PM: > When i added -P like down here:</tt> <tt>> fence_ipmilan -P -a xxxxxxxxlo -l admin -p xxxxxxxxx -M 'cycle' -v</tt> <tt>> Everything works, server reboots. But how do i get this "-P" option > included in fence_ipmilan.</tt> <tt>> How should my cluster.conf look like..that's the question...</tt> <tt>Here is an example with passwords removed:</tt> <tt><cluster name="88423a6c34c04d" config_version="3"></tt> <tt> <totem token="10000"/></tt> <tt> <cman port="6809" expected_votes="1" two_node="1" broadcast="no"/></tt> <tt> <logging syslog_facility="local3"/></tt> <tt> <fencedevices></tt> <tt> <fencedevice name="manual" agent="fence_manual"/></tt> <tt> <fencedevice name="ilo" agent="fence_ipmilan"/></tt> <tt> <fencedevice name="ilom" agent="fence_npm_ilom"/></tt> <tt> </fencedevices></tt> <tt> <clusternodes></tt> <tt> <clusternode name="node1" votes="1" nodeid="1"></tt> <tt> <fence></tt> <tt> <method name="method1"></tt> <tt> <device name="ilo" passwd="12345678" lanplus="1" method="cycle" login="user" ipaddr="10.39.170.233"/></tt> <tt> </method></tt> <tt> </fence></tt> <tt> </clusternode></tt> <tt> <clusternode name="node2" votes="1" nodeid="2"></tt> <tt> <fence></tt> <tt> <method name="method2"></tt> <tt> <device name="ilo" passwd="12345678" lanplus="1" method="cycle" login="user" ipaddr="10.39.170.234"/></tt> <tt> </method></tt> <tt> </fence></tt> <tt> </clusternode></tt> <tt> </clusternodes></tt> <tt></cluster></tt> <tt>> 2011/3/3 שלום קלמר <sklemer@gmail.com></tt> <tt>> H. </tt> <tt>> > Maybe iLo3 dont support cycle. why not to use the default , which is > "onoff" . Try it</tt> <tt>> > I think its good enough .</tt> <tt>> > -M method</tt> <tt>> Method to fence (onoff or cycle). Default is onoff. Use cycle in</tt> <tt>> case your management card will power off with defaultmethod so</tt> <tt>> there will be no chance to power machine on by IPMI.</tt> <tt>> > On Thu, Mar 3, 2011 at 3:53 PM, Mika i <mika68vaan@gmail.com> wrote:</tt> <tt>> this works:</tt> <tt>> ipmitool -H xxxxxilo -I lanplus -U admin -P xxxxxx chassis power cycle > Server is rebooted.....</tt> <tt>> </tt> <tt>> but not this:</tt> <tt>> root@fff fence_ipmilan -a xxxxxxxxlo -l admin -p xxxxxxxxx -M 'cycle' -v</tt> <tt>> 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</tt> <tt>> </tt> <tt>> cluster.conf</tt> <tt>> ....</tt> <tt>> <method name="1"> > <device lanplus="1" > name="xxxxxx_xxxxdev" timeout="20"/> > ......</tt> <tt>> </tt> <tt>> <fencedevice agent="fence_ipmilan" auth="none" ipaddr="xxxxxxxilo" > login="admin" method="cycle" name="xxxxuxx32_fencedev" passwd="xxxxx!"/></tt> <tt>> </tt> <tt>> </tt> <tt>> </tt> <tt>> </tt> <tt>> > </tt> <tt>> 2011/3/3 שלום קלמר <sklemer@gmail.com> </tt> <tt>> > Hi. </tt> <tt>> for ilo3 testing you can use :</tt> <tt>> # fence_ipmilan -a 17x.3x.7x.1xx -p "password" -o status</tt> <tt>> > fence_ipmilan -h</tt> <tt>> usage: fence_ipmilan <options></tt> <tt>> -A <authtype> IPMI Lan Auth type (md5, password, or none)</tt> <tt>> -a <ipaddr> IPMI Lan IP to talk to</tt> <tt>> -i <ipaddr> IPMI Lan IP to talk to (deprecated, use -a)</tt> <tt>> -p <password> Password (if required) to control power on</tt> <tt>> IPMI device</tt> <tt>> -P Use Lanplus</tt> <tt>> -S <path> Script to retrieve password (if required)</tt> <tt>> -l <login> Username/Login (if required) to control power</tt> <tt>> on IPMI device</tt> <tt>> -o <op> Operation to perform.</tt> <tt>> Valid operations: on, off, reboot, status</tt> <tt>> -t <timeout> Timeout (sec) for IPMI operation (default 20)</tt> <tt>> -C <cipher> Ciphersuite to use (same as ipmitool -C parameter)</tt> <tt>> -M <method> Method to fence (onoff or cycle (default onoff)</tt> <tt>> -V Print version and exit</tt> <tt>> -v Verbose mode</tt> <tt>> > If no options are specified, the following options will be read</tt> <tt>> from standard input (one per line):</tt> <tt>> > auth=<auth> Same as -A</tt> <tt>> ipaddr=<#> Same as -a</tt> <tt>> passwd=<pass> Same as -p</tt> <tt>> passwd_script=<path> Same as -S</tt> <tt>> lanplus Same as -P</tt> <tt>> login=<login> Same as -u</tt> <tt>> option=<op> Same as -o</tt> <tt>> operation=<op> Same as -o</tt> <tt>> action=<op> Same as -o</tt> <tt>> timeout=<timeout> Same as -t</tt> <tt>> cipher=<cipher> Same as -C</tt> <tt>> method=<method> Same as -M</tt> <tt>> verbose Same as -v</tt> <tt>> > On Thu, Mar 3, 2011 at 12:21 PM, Mika i <mika68vaan@gmail.com> wrote:</tt> <tt>> hmm.</tt> <tt>> Okey: have someone good installation instructions to get this > fence_ipmilan to work.</tt> <tt>> 1. active IPMI/DCMI over LAN in iLo3</tt> <tt>> 2. what should i install in server to get fence_ipmilan to work</tt> <tt>> Now if i test connection it shows like this.</tt> <tt>> </tt> <tt>> 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!</tt> <tt>> 2011/3/2 <Jason_Henderson@mitel.com></tt> <tt>> > > linux-cluster-bounces@redhat.com wrote on 03/02/2011 10:07:38 AM: > > > Hi </tt> <tt>> > > > 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? </tt> <tt>> What fence agent are you using, fence_ilo? > You will need to use the fence_ipmilan agent for iLO3.</tt> <tt>> -- > Linux-cluster mailing list > Linux-cluster@redhat.com > https://www.redhat.com/mailman/listinfo/linux-cluster</tt> <tt>> > > -- > Linux-cluster mailing list > Linux-cluster@redhat.com > https://www.redhat.com/mailman/listinfo/linux-cluster</tt> <tt>> > > -- > Linux-cluster mailing list > Linux-cluster@redhat.com > https://www.redhat.com/mailman/listinfo/linux-cluster</tt> <tt>> > > -- > Linux-cluster mailing list > Linux-cluster@redhat.com > https://www.redhat.com/mailman/listinfo/linux-cluster</tt> <tt>> > > -- > Linux-cluster mailing list > Linux-cluster@redhat.com > https://www.redhat.com/mailman/listinfo/linux-cluster</tt> <tt>> -- > Linux-cluster mailing list > Linux-cluster@redhat.com > https://www.redhat.com/mailman/listinfo/linux-cluster</tt>