nerdexam
Broadcom-VMware

2V0-622D · Question #249

The vSphere HA agent has been in the "Agent Unreachable" state on a single slave ESXi host for over a minute. The master and slave ESXi hosts are connected to the vCenter Server Appliance. Which shoul

The correct answer is D. Log into the vCenter Server Appliance via console or SSH and attempt to ping the affected slave. When a vSphere HA slave agent is unreachable, the first network validation step is to confirm whether vCenter itself can reach the affected host, establishing a baseline for network reachability from the management plane.

Section 6 – Administer vSphere 6.5 Availability

Question

The vSphere HA agent has been in the "Agent Unreachable" state on a single slave ESXi host for over a minute. The master and slave ESXi hosts are connected to the vCenter Server Appliance. Which should be the first step for validation the network configuration?

Options

  • ALog into the affected slave ESXi host via console or SSH and attempt to ping the master ESXi
  • BLog into the master ESXi host via console or SSH and attempt to ping the vCenter Server
  • CLog into the affected slave ESXi host via console or SSH and attempt to ping the vCenter Server
  • DLog into the vCenter Server Appliance via console or SSH and attempt to ping the affected slave

How the community answered

(52 responses)
  • A
    6% (3)
  • B
    2% (1)
  • C
    10% (5)
  • D
    83% (43)

Why each option

When a vSphere HA slave agent is unreachable, the first network validation step is to confirm whether vCenter itself can reach the affected host, establishing a baseline for network reachability from the management plane.

ALog into the affected slave ESXi host via console or SSH and attempt to ping the master ESXi

Logging into the slave and pinging the master tests the opposite direction of the reported failure and does not explain why the master cannot reach the slave agent.

BLog into the master ESXi host via console or SSH and attempt to ping the vCenter Server

Pinging vCenter from the master tests master-to-vCenter connectivity, not the master-to-slave path where the HA agent failure is actually occurring.

CLog into the affected slave ESXi host via console or SSH and attempt to ping the vCenter Server

Pinging vCenter from the slave does not test the network path between the master and the slave, which is the relevant communication channel for the HA agent.

DLog into the vCenter Server Appliance via console or SSH and attempt to ping the affected slaveCorrect

vCenter Server is the central management point for the cluster and communicates independently with all ESXi hosts. Pinging the affected slave from vCenter first determines whether the host is reachable on the management network at all, before isolating whether the issue is specific to the HA master-slave communication path or a broader network failure affecting the host.

Concept tested: vSphere HA agent unreachable network troubleshooting

Source: https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.avail.doc/GUID-E0161CB5-BD3F-425F-A7E0-BF83B005FECA.html

Topics

#vSphere HA#agent unreachable#network troubleshooting#vCSA

Community Discussion

No community discussion yet for this question.

Sign up to join the discussion
Full 2V0-622D Practice