From: Mohan Sundaram <mohan.tux@gmail.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Best setup for redundant routers.
Date: Fri, 07 Dec 2007 02:30:56 +0000 [thread overview]
Message-ID: <4758AD90.1060505@vsnl.com> (raw)
In-Reply-To: <7C454E01C5FAE748BEFE65F4C6B7FD8BFD2128@s-marcell.hemc.coop>
Grant Taylor wrote:
> 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.
*nod*
>
> 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.
Would be interesting to know how they perform.
> 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).
Either is good. For just 2 routers, most dynamic protocols work well.
Older protocols failed in scaling to larger networks. AFAIR, OSPF
support discovered route cost propogation which is useful in route
selection/ load balancing/ECMP etc. Do not remember if IBGP does it. Has
been a while and so a little rusty on finer details.
> 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.
For just 2 routers, the decision is pretty simple - any. I'd go with
OSPF or IBGP depending on comfort, skillset and support at locations needed.
Mohan
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
prev parent reply other threads:[~2007-12-07 2:30 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
2007-12-07 2:19 ` Grant Taylor
2007-12-07 2:30 ` Mohan Sundaram [this message]
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=4758AD90.1060505@vsnl.com \
--to=mohan.tux@gmail.com \
--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.