Hi, On Mon, Jan 05, 2009 at 03:53:43PM +0100, Arndt Roth wrote: > Hi *, > > > > we have configured IPaddr(esses) as resources in a three node HA2 > cluster. While testing the failover I can see that the virtual > interfaces numbers are incremented every time: from the2:0 to eth2:1 to > eth2:2 and so on. > > > > I shut the interface down by "ifconfig eth2:4 down" and heartbeat brings > it up again immediately as eth2:5. > > > > Here is the log: > > > > Jan 5 15:43:23 server2crmd: [29033]: info: process_lrm_event: LRM > operation IPaddr_10_231_8_221_monitor_3000 (call=147, rc=7) complete > > Jan 5 15:43:24 server2crmd: [29033]: info: do_lrm_rsc_op: Performing > op=IPaddr_10_231_8_221_stop_0 > key=6:90256:0:fc279b6a-f154-44d6-bd85-3a8cb5053323) > > Jan 5 15:43:24 server2lrmd: [29030]: info: rsc:IPaddr_10_231_8_221: > stop > > Jan 5 15:43:24 server2crmd: [29033]: info: process_lrm_event: LRM > operation IPaddr_10_231_8_221_monitor_3000 (call=147, rc=-2) Cancelled > > Jan 5 15:43:24 server2lrmd: [29030]: info: RA output: > (IPaddr_10_231_8_221:stop:stdout) In IP Stop > > Jan 5 15:43:24 server2crmd: [29033]: info: process_lrm_event: LRM > operation IPaddr_10_231_8_221_stop_0 (call=148, rc=0) complete > > Jan 5 15:43:25 server2crmd: [29033]: info: do_lrm_rsc_op: Performing > op=IPaddr_10_231_8_221_start_0 > key=44:90256:0:fc279b6a-f154-44d6-bd85-3a8cb5053323) > > Jan 5 15:43:25 server2lrmd: [29030]: info: rsc:IPaddr_10_231_8_221: > start > > Jan 5 15:43:25 server2IPaddr[10674]: INFO: Using calculated netmask for > 10.231.8.221: 255.255.255.0 > > Jan 5 15:43:25 server2IPaddr[10674]: INFO: eval ifconfig eth2:5 > 10.231.8.221 netmask 255.255.255.0 broadcast 10.231.8.255 > > Jan 5 15:43:25 server2crmd: [29033]: info: process_lrm_event: LRM > operation IPaddr_10_231_8_221_start_0 (call=149, rc=0) complete > > Jan 5 15:43:25 server2crmd: [29033]: info: do_lrm_rsc_op: Performing > op=IPaddr_10_231_8_221_monitor_3000 > key=5:90256:0:fc279b6a-f154-44d6-bd85-3a8cb5053323) > > Jan 5 15:43:26 server2crmd: [29033]: info: process_lrm_event: LRM > operation IPaddr_10_231_8_221_monitor_3000 (call=150, rc=0) complete > > > > > > Here is the configuration. > > > > <primitive id="IPaddr_10_231_8_221" class="ocf" type="IPaddr" > provider="heartbeat" > > > > > <operations> > > <op id="IPaddr_10_231_8_221_monitor" name="monitor" > interval="3s" timeout="2s" disabled="false"/> > > </operations> > > > > <instance_attributes id="IPaddr_10_231_8_221_inst_attr"> > > <attributes> > > <nvpair id="IPaddr_10_231_8_221_attr_0" name="ip" > value="10.231.8.221"/> > > <nvpair id="IPaddr_10_231_8_221_attr_1" name="nic" > value="eth2"/> > > <nvpair id="IPaddr_10_231_8_221_attr_2" name="netmask" > value="24"/> > > </attributes> > > </instance_attributes> > > > > </primitive> > > > > > > > > Is there a better way to test this without provoking the increment? > > > > How do I reset the virtual interfaces number now and what actually > causes it?
That's the way IPaddr work. AFAIK, can't be prevented. Thanks, Dejan > > > > > Thanks for any advice, > > > > > > Arndt > > > > > > > _______________________________________________ > Linux-HA mailing list > [email protected] > http://lists.linux-ha.org/mailman/listinfo/linux-ha > See also: http://linux-ha.org/ReportingProblems _______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
