From: Grant Taylor <gtaylor@riverviewtech.net>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Best setup for redundant routers.
Date: Thu, 06 Dec 2007 17:15:54 +0000 [thread overview]
Message-ID: <47582E4A.1060102@riverviewtech.net> (raw)
In-Reply-To: <7C454E01C5FAE748BEFE65F4C6B7FD8BFD2128@s-marcell.hemc.coop>
This looks to be a general routing related question rather than a "Linux
Advanced Routing and Traffic Control" (a.k.a. LARTC) question and thus
may be better answered elsewhere.
On 12/06/07 10:43, Shane McKinley wrote:
> I am setting up 2 Vyatta routers that will serve as redundant
> failover core routers out to the backbone of our ISP. They will be
> serving for routing between other branches and the ISP and bandwidth
> management.
Ok...
> I am trying to differentiate between the plethora of information
> about having redundant, automatic failover routers and pretty much
> decided on VRRP for the IP address failover mechanism.
VRRP is a good idea. I don't think I'd rely on one virtual redundant
router through. I would make router B be redundant for router A *AND
router A be redundant for router B. This way, your branch offices can
see two different routers that have the same capabilities. This way you
could route some load through one router and the rest through the other
while having both be redundant for each other.
> I am having a bit of a problem sorting out what will work best for
> automatic routing propagation between the two units and have been
> looking at the possibility of using OSPF to accomplish this to avoid
> having to enter routes into two different routers.
Yes, an interior routing protocol would be good. Based on my limited
experience I would recommend that you use either (preferably) OSPF or
possibly Interior BGP (a.k.a. IBGP).
> Would OSPF work well for this? Are there better options?
You could look at things like RIP or ISIS, but neither of them will be
as good or bandwidth friendly as either OSPF or IBGP.
> Thanks for any info,
You are welcome.
Grant. . . .
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
next prev parent reply other threads:[~2007-12-06 17:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-06 16:43 [LARTC] Best setup for redundant routers Shane McKinley
2007-12-06 17:15 ` Grant Taylor [this message]
2007-12-07 2:19 ` Grant Taylor
2007-12-07 2:30 ` Mohan Sundaram
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=47582E4A.1060102@riverviewtech.net \
--to=gtaylor@riverviewtech.net \
--cc=lartc@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.