May 2nd, 2008 16:00

No is the short answer for multiple reasons :

 

(1) A T1 link will have a HDLC(Cisco default) or PPP encapsulation format, different to Ethernet frame and therefore have to re-foramted to the outbound interface type.

 

(2) Essentially you are descbribing trying to Bridge VLANs over the WAN - which is not a good idea - as your "expensive WAN link" would be swamped or used up with LAN multicast and broadcast traffic.....rather than useful data traffic.

 

(3) If you try to do it the way you describe, you will get strange routing problems - as you can't have the same networks  in two different geographical locations at the same time.....you'll get black holing or split subnet scenarios and lost connectivity.

 

(4) If you wish to "route" aross the WAN - which is the config you have actually annotated above - then yes you can do this......although the remote VLANS woudl have to be completely different subnets - i.e not just copied from Site A.

 

So "Route" not "Bridge"

2 Posts

May 5th, 2008 14:00

Thank you for your response. I was basically thinking that, but wasn't sure. What we are trying to do is replicate virtual machines to a CoLo and then be able to turn them on their incase of an emergency. I realize I could just script them to change their IP's at bootup, but we have a few servers that really don't like their IP to change mainly SharePoint.

 

Thanks again,

Travis

No Events found!

Top