Hi Nikita, On 2 December 2010 08:27, Nikita Michalko <[email protected]> wrote: > Hi Pavlos! > > Am Dienstag, 30. November 2010 22:28 schrieb Pavlos Parissis: >> Hi Nikita, >> >> On 30 November 2010 08:42, Nikita Michalko <[email protected]> > wrote:
>> > - what about configure monitor operation of IP in cib.xml - sth. like >> > this: <resources> >> > <primitive id="IPaddr_194_37_40_42" class="ocf" provider="heartbeat" >> > type="IPaddr"> >> > <meta_attributes id="primitive-IPaddr_194_37_40_42meta"/> >> > <operations> >> > <op name="monitor" interval="60s" id="IPaddr_194_37_40_42_mon" >> > timeout="60s"/> >> > </operations> >> > >> > - it works for me very well ;-) >> >> Mia has reported on this thread that having monitor enabled is not >> enough for reporting problems on the link. >> What do you mean works for you? Have you tried to pull out the network >> cable from an interface on which you have an IPaddr2 resource running? > > - I use the "IPaddr" RA, not IPaddr2. And of course did I test it thoroughly - > succesfully ;-) aha I didn't see that you are using IPaddr,that explains a lot. I am going to test it as well. > You can also use "ifconfig ethx down " to simulate cable pull out ... > >> Does that action cause a failure on the IPaddr2 resource? > > - on IPaddr YES! Now, I am wondering why it has been mentioned in the list ( I think in Pacemaker list) that we shouldn't use IPaddr2 and not IPaddr. Thanks, Pavlos _______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
