24 Jul
2013
24 Jul
'13
2:06 p.m.
On 7/24/13 1:02 PM, Neil Johnson wrote:
I'm a network engineer at another University in
the midwest US and I
*might* be able to convince our routing guru to let us be a BGP peer and I
could setup another tunnel end point box.
I would need explicit details on how this would work and a the potential
risks and plans for their mitigation before I approach him.
We don't have earthquakes, just tornados and floods :-)
No promises however.
We have really two networks here. The internal 44-net and the external
internet facing net.
I'd propose to have a few points around the globe where we can peer the whole
44 internet facing net. Each of these locations would announce 44/8 and more
specific routes for what's close to them.
Behind this in the 44-net internal the gateway routers would be meshed over
GRE tunnels running an IGP (IS-IS). There of course would need to be IBGP
sessions between all the BGP speakers, but this would allow end user networks
to tunnel to a given 44/net router, and not need to keep a full route table of
the 44-net internal space. (I hate end stations needing to do routing, that's
why we have routers!)
This would provide full access to the 44/net from outside, easy access from
the AMPR users, and full visibility between directly routed netblocks and the
rest of 44-net with out having to maintain a full mesh.
I'd imagine the more specific announcements from the peering points would be
statically configured, but there is a way to do a limited redistribution from
the IGP into the BGP. I think it would be easier to do it manually (and more
stable), but given some time in the lab at work I could get this going.
Thoughts?
--
Bryan Fields
727-409-1194 - Voice
727-214-2508 - Fax
http://bryanfields.net