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?
A.
443 (TCP)
B.
443 (UDP)
C.
902 (TCP)
D.
902 (UDP)
Explanation:
Explanation/Reference:
D is correct.
902 – vSphere Client access to virtual machine consoles, outgoing UDP from the ESXi host
https://pubs.vmware.com/vsphere-60/index.jsp#com.vmware.vsphere.install.doc/GUID-5071C86E-FF1E-4E54-A424-A20917401160.html
0
1
The question is NOT about vSphere Client at all, let alone access to VM consoles…
It’s about seeing in Web Client the status of an ESX host. As such, communications between vCS and the “problem” host is what needs to be addressed.
0
0
https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1029919
0
0
Interestingly, the referenced article says:
Ensure that these ports are open in the firewall between vCenter Server and the ESXi/ESX hosts: 902 – UDP & TCP; 443 – TCP
which makes A, C, and D correct ! Thanks VMware Edu – you folks rock !… 🙁
1
0
I would say 902 UDP (D) as an obvious answer as the question states “After successfully adding a new ESXi 6.x host to vCenter Server” meaning the connection works on on 443 TCP and 902 TCP – Client connections while 902 UDP is used for vCenter Server agent (source: https://docs.vmware.com/en/VMware-vSphere/6.0/com.vmware.vsphere.install.doc/GUID-171B99EA-15B3-4CC5-8B9A-577D8336FAA0.html) and this is where the questions states it is failing “Not Responding in the vSphere Web Client interface”
1
0
D
https://pubs.vmware.com/vsphere-60/index.jsp#com.vmware.vsphere.install.doc/GUID-925370DD-E3D1-455B-81C7-CB28AAF20617.html
Managed hosts also send a regular heartbeat over UDP port 902 to the vCenter Server system. This port must not be blocked by firewalls between the server and the hosts or between hosts.
0
0
Both TCP/UDP 902 are listed there, but apparently the key word there is “heartbeat” which does not require a stateful protocol like TCP. THat being the case, UDP 902 is the answer indeed.
0
0
Hi
Detailed Port info here:
Heartbeat – 902 UDP
https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2106283
0
0