Re: carp fail over

[Steve Pribyl <spribyl%peel.com@localhost>]

Thanks again,

However, a quick test verifies that arpbalnce is not the culprit.

As for the MASTER/BACKUP labels.
If I just pull the plug it the MASTER stays MASTER and the BACKUP goes to 
BACKUP.
It recovers when I put the cable back.
But only on the single carp interface.

If I do a
  # ifconfig carp2 down
The master goes to INIT and the BACKUP goes to MASTER.
And recovers with
  # ifconfig carp2 up
But only on the single carp interface.

This is on a 4.0 system.

Steve Pribyl
Senior Infrastructure Practitioner
Peel, Inc
990 Grove St. Suite 204
Evanston, IL 60201
Phone: 847-424-0954 ex 14
Cell: 847-343-2349
Fax: 847-424-0986
spribyl%peel.com@localhost


On 05/29/2008 02:40 PM, Manuel Bouyer wrote:
> On Thu, May 29, 2008 at 02:10:10PM -0500, Steve Pribyl wrote:
> > Good Afternoon,
> >
> > Thanks for the concise answer.
> >
> > What have I missed then?
> > When I pull the plug on one nic and only one carp interface fails over.
> >
> > If more info is required please just ask.
> > ips and passwords have been changed to protect the guilty
> >
> > MASTER NODE
> > from /etc/pf.ctl
> > pass quick proto carp all keep state
> >
> > #ifconcig sysctl -a | grep arp
> > net.inet.carp.preempt = 1
> > net.inet.carp.arpbalance = 1
>
> I'm not sure net.inet.carp.arpbalance is compatible with preempt. I'm
> not using net.inet.carp.arpbalance myself.
>
> Do the output of ifconfig (MASTER vs BACKUP) change on both nodes
> when you unplug one cable ?
> In my case, the BACKUP becomes master, but I don't remember if
> MASTER switch to BACKUP, or if it remains MASTER. It's OK for
> MASTER to stay MASTER, because is then has a lower priority than
> the other host.