2V0-622 · Question #197
An administrator enables High Availability (HA) on a Virtual SAN cluster. There are four vmkernel port groups with the following IP addresses assigned: Management: 192.168.12.10 vMotion: 192.168.13.10
The correct answer is C. 192.168.14.10. When vSphere HA is enabled on a Virtual SAN cluster, HA traffic is automatically directed over the vSAN vmkernel network rather than the management network.
Question
An administrator enables High Availability (HA) on a Virtual SAN cluster. There are four vmkernel port groups with the following IP addresses assigned:
Management: 192.168.12.10 vMotion: 192.168.13.10 Virtual SAN: 192.168.14.10 Fault TolerancE. 192.168.15.10 Which IP address will HA use for traffic?
Options
- A192.168.12.10
- B192.168.13.10
- C192.168.14.10
- D192.168.15.10
How the community answered
(33 responses)- A12% (4)
- B9% (3)
- C76% (25)
- D3% (1)
Why each option
When vSphere HA is enabled on a Virtual SAN cluster, HA traffic is automatically directed over the vSAN vmkernel network rather than the management network.
192.168.12.10 is the management vmkernel address; while HA uses the management network in non-vSAN clusters, on a vSAN cluster it switches to the vSAN vmkernel adapter.
192.168.13.10 is the vMotion vmkernel address; vMotion is a separate traffic type and is never used for HA communication.
On a vSAN-enabled cluster, vSphere HA automatically uses the vmkernel adapter tagged for Virtual SAN traffic (192.168.14.10) for its communication. VMware designed this behavior so that HA piggybacks on the vSAN network, avoiding reliance on the management network and ensuring consistent behavior within the hyper-converged stack.
192.168.15.10 is the Fault Tolerance vmkernel address; FT logging traffic is distinct from HA communication and is not selected by HA for its own traffic.
Concept tested: vSphere HA network selection on vSAN cluster
Source: https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.vsan.doc/GUID-82565B82-C911-42F7-85B1-E9EF973EE90C.html
Topics
Community Discussion
No community discussion yet for this question.