If you have a tiny budget and your topology and upstream providers allow
it, land the transit BGP sessions on some virtual route reflectors, use
multi hop eBGP for example or use a /29 on the peering link so the RRs
don't need to sit in the data path.
Then you don't needy some fancy OpenStack clus
On 2 Nov 2015 12:43, "James Blessing" wrote:
>
> On 2 November 2015 at 11:06, Alistair Key wrote:
> > Hi All,
> >
> > Does anybody have any experience with practical ways to trim down the
size
> > of the global routing table in terms of prefixes?
>
> Feeling brave? http://route-aggregation.net/
>
