On 1/5/06, Marcin Miksowski <[EMAIL PROTECTED]> > # cat /etc/hostname.carp0 > inet 192.168.0.5 255.255.255.0 192.168.0.255 vhid 1 carpdev em1 > advskew 1 pass 31337 > # cat /etc/hostname.carp1 > inet 111.111.111.13 255.255.255.0 111.111.111.255 vhid 2 carpdev em0 > advskew 1 pass 31337 > # cat /etc/hostname.carp2 > inet 111.111.111.14 255.255.255.0 111.111.111.255 vhid 3 carpdev em0 > advskew 1 pass 31337 > # cat /etc/hostname.carp3 > inet 111.111.111.16 255.255.255.0 111.111.111.255 vhid 4 carpdev em0 > advskew 1 pass 31337 > > > > > fw2: > # ls -l /etc/hostname.carp* | wc -l > 48 > > # cat /etc/hostname.carp0 > inet 192.168.0.5 255.255.255.0 192.168.0.255 vhid 1 carpdev em1 > advskew 240 pass 31337 > # cat /etc/hostname.carp1 > inet 111.111.111.13 255.255.255.0 111.111.111.255 vhid 2 carpdev em0 > advskew 240 pass 31337 > # cat /etc/hostname.carp2 > inet 111.111.111.14 255.255.255.0 111.111.111.255 vhid 3 carpdev em0 > advskew 240 pass 31337 > # cat /etc/hostname.carp3 > inet 111.111.111.16 255.255.255.0 111.111.111.255 vhid 4 carpdev em0 > advskew 240 pass 31337
I noticed in your original email that fw2 had advskews of 10's and 100's. This suggests that CARP may not be setup the way you think it is (based on the asvskew 240 in the hostname files). BTW, if carp detects an interface failure it sets it's advskew to 240, in this case your secondary will still not preempt the primary. I'd suggest setting your advskew on the secondary a little lower (I usually put mine at 10 for primary and 100 for secondary). --Bill
