See https://access.redhat.com/kb/docs/DOC-39336
2011/3/3 <jason_hender...@mitel.com>: > > > linux-cluster-boun...@redhat.com 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 שלום קלמר <skle...@gmail.com> >> 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 <mika68v...@gmail.com> 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 שלום קלמר <skle...@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 <mika68v...@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_hender...@mitel.com> >> >> >> linux-cluster-boun...@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@redhat.com >> https://www.redhat.com/mailman/listinfo/linux-cluster >> >> >> -- >> Linux-cluster mailing list >> Linux-cluster@redhat.com >> https://www.redhat.com/mailman/listinfo/linux-cluster >> >> >> -- >> Linux-cluster mailing list >> Linux-cluster@redhat.com >> https://www.redhat.com/mailman/listinfo/linux-cluster >> >> >> -- >> Linux-cluster mailing list >> Linux-cluster@redhat.com >> https://www.redhat.com/mailman/listinfo/linux-cluster >> >> >> -- >> Linux-cluster mailing list >> Linux-cluster@redhat.com >> https://www.redhat.com/mailman/listinfo/linux-cluster >> -- >> Linux-cluster mailing list >> Linux-cluster@redhat.com >> https://www.redhat.com/mailman/listinfo/linux-cluster > -- > Linux-cluster mailing list > Linux-cluster@redhat.com > https://www.redhat.com/mailman/listinfo/linux-cluster > -- Linux-cluster mailing list Linux-cluster@redhat.com https://www.redhat.com/mailman/listinfo/linux-cluster