Date: Wed, 14 Aug 1996 09:37:14 -0500 (CDT) From: Joe Greco <jgreco@brasil.moneng.mei.com> To: jdd@vbc.net (Jim Dixon) Cc: mike@networx.ie, freebsd-isp@freebsd.org Subject: Re: gated config for ospf and bgp Message-ID: <199608141437.JAA11682@brasil.moneng.mei.com> In-Reply-To: <Pine.BSD/.3.91.960813234129.28349A-100000@uk1.vbc.net> from "Jim Dixon" at Aug 13, 96 11:43:07 pm
next in thread | previous in thread | raw e-mail | index | archive | help
> On Tue, 13 Aug 1996, Michael Ryan wrote:
>
> > Has anybody got a sample gated config file which shows how
> > to configure it for OSPF and BGP?
> >
> > If anybody replies, could you please also indicate your
> > router topology, so I can understand the config file?
>
> OSPF and BGP4 can both get complex. What is your intended configuration?
I don't know about Michael, but I'm looking to provide internal and external
redundancy.
Internally I'd like to provide dual backbone Ethernets and probably do some
basic load balancing between them, but set it up so that in case of a hub or
switch failure, or problem with an Ethernet NIC or something, the load
automatically switches to the "good" network.
>From an implementation point of view, customers here are generally connected
via a single circuit, and connect to a border router. Our outbound
connection to the Internet is done the same way. Our core routers either
connect to other local equipment (DNS, mail, news servers, etc) or to core
routers at other POP's.
What I would like to see...
--------
net1-> o-----|Core1 |
-------------------------| --------
| |
| |-------------------------------------------------------------------------|
| | | | | | | | |
| -------- -------- -------- -------- -------- -------- -------- --------
| |Border| |Border| |Border| |Border| |Border| |Border| |Border| |Border|
| -------- -------- -------- -------- -------- -------- -------- --------
| | | | | | | | |
| |-------------------------------------------------------------------------|
| |
| --------
-------------------------------|Core2 |
--------
where some number "n" of the border routers connect to backbone service
providers (and speak BGP4), others speak to customers, and independent
core routers duplicate services (i.e. multiple nets, to which both core
routers connect, such as net1 above). The strategy is obviously to attempt
to provide continuous IP connectivity through a single point of failure.
Externally, I would like to peer with multiple service providers, and I do
not want to do so off of the same border router.
That's _my_ goal. :-)
... JG
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199608141437.JAA11682>