29 Jan
2014
29 Jan
'14
3:04 p.m.
On 1/29/14 2:05 PM, Steve Wright wrote:
This mesh crap really needs to be binned, or at the
very least not try and
do anything important over it, such as route an entire /16. If you want to
connect a /24 with it to make a neat local play toy then go for it, but
using it as an enterprise routing tool is absurd at the very least, and at
it's WORST, it's very likely to just completely stop anyone from trying to
build anything new over it because it's connectivity and throughput sucks.
This.
So this is how I'd see it work, I need to write up a proposal for it.
You have regional BGP routers that route subnets to the internet. These could
then tunnel the subnets to end users via GRE. End users could route via an
IGP over this tunnel to the regional speaker(s). Multiple tunnels would give
redundancy.
The regional speakers would have a tunnel between them.
In the event of an outage the other BGP speakers would route subnets.
Multiple links from end users to other BGP speakers (or non-speakers that are
aggravation routers) would provide redundancy to the end users.
Of course nothing prevents having a direct BGP speaker with an RF link to end
users, most data centers will not have roof rights however.
We could setup redistribution that would pull announcements from BGP if end
nodes went down.
Each BGP speaker could announce the subnets it knows about and a /8 providing
we have a mesh of the backbone bgp speakers.
Thoughts?
--
Bryan Fields
727-409-1194 - Voice
727-214-2508 - Fax
http://bryanfields.net