2VB-601 · Question #17
When using vSAN in a two-node direct connect configuration, how do data nodes communicate with the vSAN witness appliance?
The correct answer is B. An alternate VMkernel interface that has connectivity to the vSAN witness must be tagged with a. Traditional vSAN 2 Node configurations require connectivity between the vSAN tagged VMkernel ports, and the vSAN Witness Appliance's VSAN tagged VMkernel port. 2 Node Direct Connect Witness Traffic Separation provides the ability to directly connect vSAN data nodes in a 2 Node…
Question
When using vSAN in a two-node direct connect configuration, how do data nodes communicate with the vSAN witness appliance?
Options
- AThe vCenter Server acts as a proxy between data nodes and the vSAN witness.
- BAn alternate VMkernel interface that has connectivity to the vSAN witness must be tagged with a
- CTwo-node direct connect does NOT require connectivity to the vSAN witness appliance.
- DIf the data node management VMkernel interfaces that are tagged for management traffic only
How the community answered
(53 responses)- A4% (2)
- B70% (37)
- C9% (5)
- D17% (9)
Explanation
Traditional vSAN 2 Node configurations require connectivity between the vSAN tagged VMkernel ports, and the vSAN Witness Appliance's VSAN tagged VMkernel port. 2 Node Direct Connect Witness Traffic Separation provides the ability to directly connect vSAN data nodes in a 2 Node configuration. Traffic destined for the Witness host can be tagged on an alternative interface from the directly connected vSAN tagged interface. https://blogs.vmware.com/virtualblocks/2016/10/18/2nodedirectconnect/
Topics
Community Discussion
No community discussion yet for this question.