[c-nsp] BGP transit selection from source customer network

[David Freedman]

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

On 01/08/11 15:35, Alexandre Durand wrote:
> Hi Andrew,
> 
> Tnhan you for you answer. Actually youa re right about the inbound
> traffic in which I can easily advetise this network with a preference to
> my "ISPA", this is fine and already done.
> 
> The issue here is about the oubound traffic, when my customer traffic is
> going back out to ISP, I can also you weight on the router where I host
> this "ISPA" and use no-advertise attribute so I don t advertise
> prefixes to others iBGP routers, fine but others customer traffic will
> also be routed via ISPA because the shortest ISP path is going throught
> this router too...
> 

I think what you are saying sounds like this:

|Your Network---Internet---------|

[Cust1]--( N )
         ( E )--[ISPA]-(N)-[Cust4]
[Cust2]--( T )         (E)
         ( W )--[ISPB]-(T)-[Cust5]
[Cust3]--( K )



I take it you want to do :

- - Predetermined outbound path Cust1->Cust4 via ISPA
- - Predetermined outbound path Cust2->Cust5 via ISPB
- - Cust3 -> Cust4/5 via any/best path

What you are talking about is essentially policy routing at your edge
(i.e using your own criteria, like customer ID to influence outbound
routing, not metrics)

you can do this simply with PBR at the edge but it won't be very
reliable, but you might want to look at OER/PFR

(http://www.cisco.com/en/US/products/ps8787/products_ios_protocol_option_home.html)

Dave.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk42zL4ACgkQtFWeqpgEZrK2BgCgwGU7nRzRPklKNII9L69uA00I
w5YAoKkhzi8L8Roo5oONsg/6z1aNW0ka
=lLQt
-----END PGP SIGNATURE-----