I've been trying to deploy the witness for a 12-node Stretched vSAN 6.6 cluster and having some L3 problems getting the vSAN vmk interfaces used by the data nodes to connect to the witness host vSAN vmk interface. Data nodes are at two different data centers connected by stretched L2. And witness is at a 3rd/separate location and using the VM appliance as a witness host.
I was able to get the witness to work by having vmk0 on the witness ESXi host do both Management and vSAN traffic. (after I un-checked the box for vSAN from vmk1 on the witness ESXi host)
I added a static route on my data nodes so their vSAN vmk interfaces (vmk1) can ping to the witness IP for Management and now vSAN. And from the witness I can ping the IPs of the data nodes vSAN vmk interfaces.
I was able to successfully configure the stretched cluster and add the witness. The healthchecks are green.
My question is if having both Management *and* vSAN traffic on the witness vmk0 is a supported configuration. There is a link on Storagehub for Witness Traffic Separation (WTS) that describes this configuration. But isn't clear to me if this is supported for Stretched Cluster or only for 2 Node Direct Connect cluster.
Thanks!