I have a question on the VMs / IP's
I have two sites, A and B.
3 hosts . 10 VM's - VM IPs 192.168.1.0/24
3 hosts - used in case of failure in site A. IP's 18.104.22.168/24
what would happen to the VM's once they boot in site B - as they have a static IP of 192.168.0.1/24 subnet ?
This is design related query and is not specific to vSAN functionality. As far as vSAN Stretched Cluster is concerned, your VMs will boot on Site-B hosts. The point here is if you don't have 192.168.0.1/24 network on Site-B then VMs will not be accessible which means there will be a DU situation as the workloads running on those VMs will not make any sense as they are not accessible over the network.
You need to take care of the network design part so that VMs are accessible in both the cases (running on Site-A and running on Site-B)
Was your question answered correctly? If so, please remember to mark your question as "Correct" or "Helpful" when you get the correct answer. This helps others searching for a similar issue.
you would require Network Layer 2 extension technology such as OTV in Site B. so that your VM can work with out any issue
You said "3 hosts - used in case of failure in site A. IP's 22.214.171.124/24". Is this IP management IP ?
I was just coming here to discuss something very close to this. We have L2 stretched across the two sites (also running vSAN stretched cluster). So, If site A goes down, when the VMs boot in site B, they will be on the correct subnet, but let's say that site A's entire rack went down, taking the L3 gateway with it. Now the VMs in site B have an unreachable gateway. Would VRRP be a recommended way of handling that?
VRRP is a perfectly fine solution to handle this. Just as HSRP, GLBP or anycast gateway.
Keep in mind that each solution has it's pros and cons. Some offer the feature to have to gateway active on both sites at the same time, while others only have a active/standby configuration. This could have impact on the route your network traffic takes.