[c-nsp] Looking for suggestions on how to link old colo with the new colo for routing purposes until new circuits are in place

[Dan Troxel]

We are in the process of merging three colo facilities into one new
facility. However, we are getting into heavy delays from two of our telco
providers. We are looking for a solution for IP traffic (subnet) routing
while we are in the process of the move, and during our "waiting" period
from our telco providers.

 

At our current three colo facilities, we have a mix of DS3 ATM circuits (for
Frame, ATM, xDSL customers), PTP DS3s, and multi channel DS3s for our T1
customers. We have 100 meg connections at two of the three facilities. The
third has a DS3 connected to one facility, and a DS3 ATM connection to the
other. BGP is implemented to two different backbones (one at each of two
facilities - the third uses IGP to determine a path out to the internet).
All of the T1's are subnet's of /24s (/25-30). The dsl's are a mix of single
IP host networks or tiny subnets (/29-30,/32).

 

At the new facility, we currently have in place a gig connection to a couple
of backbones (new backbone providers, not ones we are currently using at the
three old facilities). 

 

Issue: We are waiting on fiber, at our new facility, (possible additional
30-90 days) for our customer based multi channel T1's, and also for ATM
connectivity for our frame and xDSL customers. 

 

Problem: Since we cannot run BGP on any network smaller than a /24, how do
we connect all the networks together, so that we can route internet
connectivity to the small subnets (smaller than class C)? 

 

Possible solution: Someone suggested setting up VPN's between the four
locations, so that these smaller nets can be temporarily routed until the
new circuits are in at the new facility. Is this a reasonable solution? Will
the latency be too great (>100ms)?

 

Any ideas would be greatly appreciated.

 

 

----

Dan Troxel