2V0-15.25 · Question #18
An administrator is troubleshooting network connectivity issues on a VMware ESX host configured with a dedicated VMware vSAN vSphere Distributed Switch (vDS) port group. The VMware vSAN vDS port…
The correct answer is C. A physical adapter is set to "Not Used" in the vDS configuration. In vSAN ESA or OSA networking configured through a dedicated vSphere Distributed Switch (vDS), each vSAN vmkernel port must have at least one Active physical uplink available at all times. The scenario describes a vDS with two physical adapters and two uplinks, but after…
Question
An administrator is troubleshooting network connectivity issues on a VMware ESX host configured with a dedicated VMware vSAN vSphere Distributed Switch (vDS) port group. The VMware vSAN vDS port group has two physical adapters and two uplinks assigned. After a failure of the active physical adapter, the vSAN vDS connection over the vSAN network was lost. What is the cause of the issue?
Options
- AThe vSAN storage policies are misconfigured.
- BVLAN tagging is not correctly configured on the vDS.
- CA physical adapter is set to "Not Used" in the vDS configuration.
- DThe vDS failover policy does not allow fallback.
How the community answered
(42 responses)- A5% (2)
- B7% (3)
- C74% (31)
- D14% (6)
Explanation
In vSAN ESA or OSA networking configured through a dedicated vSphere Distributed Switch (vDS), each vSAN vmkernel port must have at least one Active physical uplink available at all times. The scenario describes a vDS with two physical adapters and two uplinks, but after failure of the active uplink, vSAN traffic was lost. This only occurs when the second physical NIC is not actually assigned to the vSAN port group--typically because its uplink is set to "Unused". In such a misconfiguration: vSAN traffic only uses the single active uplink. When that uplink fails, vSAN has no failover path, causing immediate connectivity loss.
Topics
Community Discussion
No community discussion yet for this question.