Messages

If it is a temporary solution (and will really be temporary) I would use whatever the hardware I had that could do. If I didn't have anything then L2TPv3 can be done in Linux. Just spin up a box on either side with a couple interfaces. One interface for the L2TP tunnel source/end point, and one interface to accept a trunk port from the network to send over the tunnel.

If it going to be a permanent solution I would go with VXLAN, and setup everything as leaf/spine. Even if I had to procure, and put in extra effort to do so.

-Otanx

Thank you Otanx!

I'm looking to migrate all VMs from one DC to another one. This will be temporary solution. I have redundancy on the Internet, but I will need to have for the all L2 link.

Both DCs connected to the Internet, to the same ISP.
The idea to have L2 over Internet (VPN). If I can use 6509 for L2 it will be great, if not, probably I will need to have some devices for GRE/L2TPv3/VXLAN.

Just wondering what will be the easiest way to set up L2, to send multi VLANs across L2?
Any preference to use on of these methods GRE/L2TPv3/VXLAN?

Hello guys,

I'm looking for a way to connect two data centers with layer 2 (about 50 VLANs).
I have VPN tunnel between two locations. I have Cisco 6509 in both locations, if it makes sense maybe I can use it for L2 tunneling.
Wondering what method the most reliable to send L2 traffic between two locations.
 

I see there are a few options to extend L2:
VXLAN
GRE Tunnel
L2 Tunneling

If you have such experience, could you please share it? What will be the proffered way?
Unfortunately I don't  way to test it, except the production environment

Thanks!

Thanks guys for your input!
Probably I will need to go with DNS solution, like f5 GSLB. In this case both sites can be active, and the traffic will be sent based on node/service availability.

Thanks again for you help.

Are you having the DCs act as both being active or will the secondary be syncing up with the primary?

Will this also have to work with multiple outbound links from the sites?

Would you want to do this with a load balancing or link balancing solution inline?


Second one will be standby, yes, will be syncing up with the primary.

Yes, each DC will have:
MPLS - telco company will create cascading failover between two MPLS circuits in primary DC and another one in second DC.
Internet - each location will have independent Internet connectivity.
Vendors external connectivity - each vendor will install at least one router at each location.

I thought to use LB for internal application, and some routing protocol to share the same subnets between two data centers (for connectivity with the vendors).

What will be the best approach to have the redundancy in place?

[0]

Thank you Otanx! Probably there will be 3-4 networks (/28) for vendors and about 7-8 application networks (/24)

/23 is a good option. But I see you have different /24 subnets in each DC x.y.0.0/24 vs x.y.1.0/24
In case vendor's device (or circuit) is down, they will be sending the traffic to our second network, right?

Can I advertise network from primary DC, and just in case this network is down, the same network will be advertised from second DC?

Hello guys,


I'm working on a project to plan full redundancy for our client. There are going to be two data centers (primary and standby).

Each DC will have MPLS connectivity to the client's locations, Internet connectivity, connectivity to different vendors (each vendor will install and manage their own router at each DC). There is going to be L2 link between two DCs.

How can I advertise the network/networks from primary data center and in case of some router is down start advertising it from second data center?



Many thanks!