[c-nsp] BGP Routing Failover for multiple classes of customers

Bruce Pinsky bep at whack.org
Wed Sep 7 02:24:34 EDT 2005


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Richard J. Sears wrote:
> Hello Everyone - 
> 
> We are working on a project and we have hit a stump, hopefully someone
> can come up with some ideas different that we have.
> 
> We have a router (router_1) connected via BGP to two providers.
> Provider_1 and Provider_2. We are receiving full routes from both
> providers.
> 
> We have three type of customers connected directly to router_1 (which
> happens to be a 6509 running a SUP720-3BXL engine). 
> 
> Customer 1 we would like to only get to provider_1 (this works)
> 
> Customer 2 we would like to be able to get to both provider_1 and _2
> (this works)
> 
> Its customer three we have a problem with. We want customer 3 to only go
> out provider_1 unless provider_1 fails, then be able to go out
> provider_2. 
> 
> Inbound traffic will be handled with prepending and is not a problem.
> 

Well, it could depend on how you are achieving 1 and 2.  For example, you
could use VRFs for each customer type.  In VRF 1, you only import
provider_1 routes.  In VRF 2, you import all the routes from both providers
with equal preference.  In VRF 3, you import all the routes, but local pref
provider_1 routes.  The interfaces for each customer type are associated
with the appropriate VRF.

You might also use VRFs for type 1 and 3, but allow type 2 to route off the
global table.

As with many things in networking, there are several ways to "skin the cat".

- --
=========
bep

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (MingW32)

iD8DBQFDHoeiE1XcgMgrtyYRAl87AJ9bUH3yoM+V6dXghBD3LVtXqChzTwCglFnq
jqcRxUdEpxPNthYn02LEUKs=
=pmf3
-----END PGP SIGNATURE-----


More information about the cisco-nsp mailing list