[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: CARP failure: Juniper arp timeouts?
- To: misc_(_at_)_openbsd_(_dot_)_org
- Subject: Re: CARP failure: Juniper arp timeouts?
- From: Eric Eekhof <eric_(_at_)_eekhof_(_dot_)_net>
- Date: Tue, 20 Apr 2004 11:51:13 +0200
- Organization: Eric Conspiracy Secret Labs
- Reply-to: eric_(_at_)_eekhof_(_dot_)_net
On Tue, Apr 20, 2004 at 11:08:09AM +0200, Wild Karl-Heinz wrote:
> In message "CARP failure: Juniper arp timeouts?"
> on 20.04.2004, Eric Eekhof <eric_(_at_)_eekhof_(_dot_)_net> writes:
>
> EE> FW 1
> EE> ----
> EE> /etc/hostname.carp0:
> EE> vhid 1 pass mekmitasdigoat 192.168.0.2
> ^^^^^^^^^^^
>
> EE> /etc/hostname.carp1:
> EE> vhid 2 pass mekmitasdigoat 192.168.0.2
> ^^^^^^^^^^^
> Make this sense?
According to the carp manpage it does:
<QUOTE>
First the carp interfaces on Host A are configured. The advskew of 100
on the second virtual host means that it's advertisements will be sent
out slightly less frequently.
# ifconfig carp0 create
# ifconfig carp0 vhid 1 pass mekmitasdigoat 192.168.1.10
# ifconfig carp1 create
# ifconfig carp1 vhid 2 advskew 100 pass mekmitasdigoat
# 192.168.1.10
The configuration for host B is identical, except the skew is on virtual
host 1 rather than virtual host 2.
# ifconfig carp0 create
# ifconfig carp0 vhid 1 advskew 100 pass mekmitasdigoat
# 192.168.1.10
# ifconfig carp1 create
# ifconfig carp1 vhid 2 pass mekmitasdigoat 192.168.1.10
</QUOTE>
However, I tested the setup also with only carp0 active. Didn't change a
thing.
Regards,
Eric
Visit your host, monkey.org