After successfully adding a new ESXi 6.x host to vCenter Server, an administrator sees it as Not Responding in the vSphere Web Client interface a few minutes later. If the issue is caused by a network firewall blocking traffic, which port must be opened to correct this specific problem?

Question

Accepted Answer

D. 902 (UDP) vCenter Server sends UDP heartbeat probes to ESXi hosts on port 902 to continuously verify host reachability. When a firewall blocks this UDP traffic, vCenter stops receiving heartbeat acknowledgments and marks the host as Not Responding, even though the host itself is healthy.

Answer

A. 443 (TCP) TCP 443 carries HTTPS management API traffic between vCenter and ESXi; blocking it would impair management operations but is not the specific port responsible for the heartbeat that drives the Not Responding state.

Answer

B. 443 (UDP) UDP 443 is not a defined VMware communication port for vCenter-to-ESXi traffic and is not relevant to host availability monitoring.

Answer

C. 902 (TCP) TCP 902 is used for virtual machine remote console (VMRC) data transfer, not for the heartbeat mechanism that determines host connectivity status.

After successfully adding a new ESXi 6.x host to vCenter Server, an administrator sees it as Not Responding in the vSphere Web Client interface a few minutes later. If the issue is caused by a…

Question

Options

How the community answered

Why each option

Topics

Community Discussion