We plan to deploy VMware vCenter SRM failover between two buildings.
To achieve a successful failover of the VMs from the Protected Site Vlan (Production Site) to the Recovery Vlan (Disaster Recovery Site) and have all the virtual machines come up in the Disaster Recovery Site using the same IP as the Production Site is to stretch the Protected Vlan to the Recovery Site.
How do we stretch Vlans across a Layer 3 link?
Do we just create the same Protected Vlan configuration in the Recovery Site (DR) switch?
The link between the buildings is private dark fiber.
Building I and Building II have layer 3 switch and the link between the buildings is routed, Layer 3.
ip address 172.31.254.1 255.255.255.252
ip address 172.31.254.2 255.255.255.252
If it is dark fiber, you can just 802.1q trunk between the two. VMWare makes us break all of the networking design rules that have been pounded into us over the years. Obviously, be concerned about latency and bottlenecks. Also, you might look at something lilt otv.
Stretch it across a routed link? Could one use MPLS for that? You could easily convert your link to L2 and have the same subnet it both buildings, just remember that you span your broadcast domains across that link as well. So if a broadcast storm happens at one site, chances are it will happen at the other. Of course, there are things you can do to keep this from happening.
The alternative is an L2 tunnel between the L3 end points in the buildings. Preserves your L3 connectivity while also providing L2 access.
My question is, if you have privately-owned dark fiber, do you have extra pairs? If so, turn up a new L2 link between the buildings, and prune it down to ONLY your VMWare VLANs.