2V0-622 · Question #127
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
The correct answer is D. 902 (UDP). UDP port 902 carries heartbeat traffic from ESXi hosts to vCenter Server, and blocking it causes the host to appear as Not Responding.
Question
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?
Options
- A443 (TCP)
- B443 (UDP)
- C902 (TCP)
- D902 (UDP)
How the community answered
(45 responses)- A11% (5)
- B2% (1)
- C7% (3)
- D80% (36)
Why each option
UDP port 902 carries heartbeat traffic from ESXi hosts to vCenter Server, and blocking it causes the host to appear as Not Responding.
TCP 443 is used for HTTPS-based management API communication, not for the heartbeat mechanism that triggers Not Responding status.
Port 443 is exclusively used over TCP in vSphere; there is no defined UDP 443 role in VMware networking.
TCP 902 is used for VM console access and provisioning operations, not for the heartbeat traffic that determines host responsiveness in vCenter.
vCenter Server monitors ESXi host availability using UDP port 902 for heartbeat signals sent by the VMware vCenter Agent (vpxa) on each host. When a firewall blocks UDP 902, vCenter stops receiving these heartbeats and marks the host as Not Responding, even though the host itself may be fully operational.
Concept tested: vCenter to ESXi heartbeat port requirement UDP 902
Source: https://docs.vmware.com/en/VMware-vSphere/6.7/com.vmware.vsphere.security.doc/GUID-AE6B9F9E-2D4E-48D5-B73C-3B6E5EEE3C7A.html
Topics
Community Discussion
No community discussion yet for this question.