OT - Quagga/CARP

[Dima Dorfman]

Michael DeMan <michael at staff.openaccess.org> wrote:
> Anyway, thanks very much for the information.  I'm going to have to  
> figure out some kind of workaround on my architecture.  In the worst  
> case, I can shut off OSPF on the edge routers and use static routes  
> upstream and OSPF from there, but that is going to be a real  
> nightmare for network maintenance over the long haul.

You're talking about using CARP and OSPF on the edge routers, right?

Can you explain a little more why CARP and zebra/ospfd don't play well
together? I understand the problem about having two copies of the same
route in the FIB, but I don't think it should prevent redundancy from
working. I am planning to deploy FreeBSD-based access routers in the
near future, and I'd like to have an idea of what issues I'll be
facing.

The scenario I have in mind is two FreeBSD boxes connected to the rest
of the network on one side and clients (using carp) on the other. CARP
is supposed to protect the client against one of the routers failing.
I tried this on some test boxes today, and it looks like it should
work. Both boxes are configured as OSPF neighbors and share a CARP
vhid. When both links are up, each router has a route through the
physical interface (it also sees the OSPF route, but the connected
route is better). If one of the links fails (any condition that causes
the physical interface to be down), the routes are withdrawn, the
other box takes over the VIP, and the first box installs the OSPF
route. Everything is still reachable.

Am I missing an obvious problem or a case where this doesn't work?
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 155 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-net/attachments/20060325/539b3d47/attachment.pgp