DR with remote cluster - networking bits

[ciroiriarte]

Just wanted to elaborate more on the network implications of starting a VM restored in another cluster/site.

What are the usual tricks used on that case with nodeweaver?. Having to change the IP of 20 or 60 VM in a mixed environment (Windows/Linux) can be cumbersome. If we are replicating the network on both sites, connection between them must be filtered somehow.

Might contextualization work?, DDNS+DHCP?, just configuring two subnets within each VM to be moved between sites?

[cdaffara]

Contextualization works great; the simplest approach is to have replicated virtual networks with the same ID or name but different gateways and/or IPs for the main and DR networks. Contextualized network will then push the VM network configs. In alternative, a VM with the same name on both sides (not replicated) that provides the “real” gateway for the network to the internet. VMs will connect using the same ip and gateway, and the gateway provides the necessary redirection.
It is possible to provide additional complexity, if both VM runs at all time - like a VPN between the two clusters, so the VM on both sides can see themselves.

[ciroiriarte]

Thanks Carlo. Are there any provisions for that in NW network components or should I just spin a VM and do the magic inside (gateway VM option) ?

Curious about why it needs to have the same name…

[cdaffara]

Only through contextualization - it is enough for most cases. You can leverage virtual routers or dedicated VMs for more complex configuration.
You need the same name only if you want to replicate 1:1 the virtual networks from one cluster to the other.