I have a situation where one of my remote sites will be relocated to a different physical location in the next few weeks.
Their current location is connected to mine via a T1 line across two 3640 routers.
Using fake private IP numbers, it would look like:
Main campus subnet (10.0.30.0/23)
Remote subnet (10.0.14.0/23)
Main 6506 SUP1(10.0.30.1)---(10.0.30.2)eth0/0 Main 3640
Main 3640 S0/0 (10.0.10.1)----- (10.0.10.2) S0/0 Remote 3640
Remote 3640 eth0/0 (10.0.14.1)----remote switches.
The new location connects via an 8oGHz wireless link to 3750E switches.
Since the new setup no longer involves routing, I plan to use the switches' layer 3 capabilities to allow retention of the remote site's subnet. That allows me to avoid reconfiguring servers, printers, etc.
Is there a way to "share" that subnet across the two remote locations via VLAN or some other mechanism?
The goal is to have the same subnet present at both locations simultaneously.
This will allow me to move the servers to the new location while maintaining the user's connectivity at the present site.
Once the move is made, the old remote link will be dismantled.
I'm trying to avoid having to reconfigure the servers with new IP addresses, security certs, etc.
Possible or pipe dream?
I think the real issue is the move overlapping your vacations. If you want, I can come over and make it for you, August in Hawaii must be magnificent :)
Anyway, if you could put two additional routers (anything would do), you could work out something like bridging over GRE, hoping the reduced MTU do not cause to many problems.