[c-nsp] Conditional BGP

[Church, Charles]

If you want to only give them a default, they could use static object
tracking to override your default with their own provider.  If that
provider drops, the static that's tracked (with an AD lower than BGP)
will go away, and your default would now be used. 

Chuck 

-----Original Message-----
From: cisco-nsp-bounces at puck.nether.net
[mailto:cisco-nsp-bounces at puck.nether.net] On Behalf Of Paul Stewart
Sent: Tuesday, September 23, 2008 9:13 AM
To: kratzers at pa.net; cisco-nsp at puck.nether.net
Subject: Re: [c-nsp] Conditional BGP


Thank you ... so really the best solution for us to offer is what we
already
do - full table.

Also, since we support a full list of communities the customer has
complete
control over when/where they get advertised.  Or a simple approach for
the
customers would be heavy prepending and low local-pref (which would keep
the
traffic down but not zero due to our peering etc).

Thanks very much,

Paul


-----Original Message-----
From: Stephen Kratzer [mailto:kratzers at pa.net] 
Sent: September 23, 2008 9:00 AM
To: cisco-nsp at puck.nether.net
Cc: Paul Stewart
Subject: Re: [c-nsp] Conditional BGP

On Tuesday 23 September 2008 08:37:56 Paul Stewart wrote:
> Hi folks..
>
>
>
> We have a couple of customers that are looking to purchase an Internet
> connection from us - this will be a BGP feed to each customer as they
are
> multihomed today etc.
>
>
>
> Normally, we would just supply a full table and let them decide what
to do
> with it.  In this scenario, they both wish to use us as a backup
provider
> and wish to ONLY use our network if their primary provider (Cogent) is
> down.
>
>
>
> What is common practice for this scenario?  We would still prefer to
just
> send a full table and put the control into their hands but I'm also
> concerned if they will have the technical expertise to accomplish
this.. 
> On their side, what would be common practice?  I've been looking at
> conditional BGP advertisements using route-maps but don't believe
that's
> the best solution..
>
>
>
> Thanks for your input.
>
>
>
> Paul

Paul,

Most providers offer three options: full routes, partial (customer)
routes, 
and default route only. Allowing the customer to select from these
options 
allows them to choose the option that they can best support. To
implement 
these options, you can create as-path access list and prefix list
templates 
and apply them outbound as needed.

Stephen Kratzer
Network Engineer
CTI Networks, Inc.


_______________________________________________
cisco-nsp mailing list  cisco-nsp at puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/