Multi site BGP Routing design
maillist at webjogger.net
Sat Jun 6 13:37:48 UTC 2009
We actually have a very similar setup to what Justin asked about, with the
exception that we advertise only some of our netblocks to one provider and
the rest to the other. If one of the providers fails, we then advertise all
netblocks through the provider which is still up. If the private link
between our two locations fails, the two halves of our network communicate
via the Internet.
>From what Justin described, I would think he would be able to keep a single
ASN and configure his network so that if the private link goes down, the two
newly disconnected halves of his network advertise only the netblocks they
can still "see" (i.e. the ones on their half). As long as his internal
network is set up with dynamic routing (iBGP / OSPF) the two halves should
realize they have to get to the other half via the Internet.
In our case, we don't get full routing tables from our providers, just
default routes. Perhaps in Justin's case something as simple as a floating
static route via the Internet to the other half of the network would take
care of any ASN weirdness. It doesn't sound like he really needs his border
routers to speak BGP with each other while the private link is down. If he
wanted to remove the BGP session entirely under these circumstances, he
could do the iBGP peering between RFC 1918 addresses and thus force the iBGP
session to go down if the private link fails.
----- Original Message -----
From: "Saqib Ilyas" <msaqib at gmail.com>
To: <nanog at nanog.org>
Sent: Saturday, June 06, 2009 8:21 AM
Subject: Re: Multi site BGP Routing design
> For a given interconnection between the upstream ISPs for the two site,
> the direct link goes down, the time required for site A to learn the new
> route to site B and vice versa would be different with the different
> proposed solutions, right?
> Thanks and best regards
> On Sat, Jun 6, 2009 at 12:40 PM, Ivan Pepelnjak <ip at ioshints.info> wrote:
>> > To rephrase the OP's question, would it be BCP to acquire a
>> > second ASN, and without further de-aggregating, continue
>> > advertising each site's IP space to the DFZ, but from
>> > dissimilar ASs as opposed to the same one?
>> This would definitely be the best approach. You're not introducing new IP
>> prefixes and you're not extending AS paths, so the net effect on the
>> BGP routing is zero (OK, you might have to use the 4 byte AS number :).
>> Just make sure that both ISPs you connect to allow you to advertise
>> "transit" prefixes. If site A public link goes down, but the private link
>> up, site B will advertise its own address space plus site A's address
>> with an extra AS number in the AS path (and the upstream ISP might filter
> Muhammad Saqib Ilyas
> PhD Student, Computer Science and Engineering
> Lahore University of Management Sciences
More information about the NANOG