firstly thank you for your comitment to the community. I’m facing a Understanding diffeculty with vSAN RoBo deployment direct connect. following configuration
2x 10Gb nic each node
VMK1 as vSAN traffic (default IP-Stack)
VMK2 as vMotion traffic (vMotion Stack)
DvPortGroup vSAN Uplinnk5, Uplink6 A/A
DvPortGroup vMotion Uplinnk5, Uplink6 A/A
Routing based on Physical Nic
with this configuration the vmks are spreeded over the Uplinks, till now everything is fine. Now when an uplink fails on one node the vmk of that nic is changed to the working one and then vMotion do not work. In a Activ Standby also the same when an Uplink fails and the vmk is moved to the surviving nic, there is no vMotion then. Can you suggest how i can handel Redundancy in that case???
Thank you in advance
In my configuration I have configured a LAG for the two uplinks, and I have done some testing on this and vMotion seems to work fine even with a NIC failure. My question is how are you testing the NIC Failure?
I hope this is the correct way to ask questions,
my Company is new to the vSAN world, and we are a bit cautious about the Installation. We are currently deployind a 2 Node Cluster. this will be used for VDIs. We are leaning to the layer 2 Witness constellation, using VLANs and Kernel Ports for the Separation. Another Consultant recommended the Layer 3 Witness Setup. Do you have a Preference? Or can you at least give me some pros/cons to the variations?
many thanks in advance!
The witness has to exist on a different subnet to the actual ESXi hosts, this is to prevent vSAN I/O traffic traversing through the witness
You must be logged in to post a comment.
This site uses Akismet to reduce spam. Learn how your comment data is processed.