Re: Best practice for BGP session/ full routes for customer

[Jason Lixfeld <jason () lixfeld ca>]

1.  You already know that multihop is very ugly.  If it's for a one-off, it's probably fine.  But building a product 
around multi-hop wouldn't be my first choice.

2.  Most of the router/switch vendors that can support a full table are pretty expensive, per port.  Your best bet here 
might be to look into some way of transparently dragging customer traffic from the PE to the BGP speaker, which leads 
me to:

3.  If your network is MPLS enabled, you can do a routed pseudowire from a BGP speaking router with a full table to the 
access router (PE).  Other tunnelling technologies can probably do the same thing; GRE, L2TPv3 and also a plain'ol VLAN 
can do it too, depending on your network topology.  Do some sort of OAM over top of either of those (if your platform 
supports it) and it looks just like a wire to the end customer.

On Jul 7, 2014, at 2:33 PM, Anurag Bhatia <me () anuragbhatia com> wrote:

> Hello everyone!
>
>
> I have quick question on how you provide full BGP table to downstream
> customers?
>
>
> Most of large networks have few border routers ("Internet gateways") which
> get full table feed and then they have "Access routers" on which customers
> are terminated. Now I don't think it makes sense to push full routing table
> on the "access routers" and simply their default points to border routers.
>
>
> In this scenario what is best practice for giving full table to downstream?
>
>
>   1. Having multi-hop BGP session with a loopback on "border router" for
>   injecting full table in customer router and another BGP session with access
>   router for receiving routes? (messy!)
>
>
>   2. Injecting full table in just all access routers so that it can be
>   provided whenever needed?
>
>   3. Any other?
>
>
>
>
> Thanks in advance!
>
> -- 
>
>
> Anurag Bhatia
> anuragbhatia.com
>
> Linkedin <http://in.linkedin.com/in/anuragbhatia21> | Twitter
> <https://twitter.com/anurag_bhatia>
> Skype: anuragbhatia.com
>
> PGP Key Fingerprint: 3115 677D 2E94 B696 651B 870C C06D D524 245E 58E2