portvmware-vcentervmware-vsphere
We are currently setting up a new vmware environement based on ESXi 5.5, with the virtual appliance and vSphere client. After a lot of research (maybe I didn't searched well), I couldn't manage to find which ports needs to be open between the vSphere client and the vCenter (to get the communication ok and the vm consoles). I found some articles but they are rather a list of all the used ports on VMWare.
Do you have any idea ? Thanks in advance,
brian, if you're still out there, it would be great to have feed-back from you.
In regards to the biggest problem with vSphere Client vCenter Customization Specification IP address information not sticking when I load a Sysprep XML file, I confirmed with VMware that it's a known bug since ESX 4.0 (http://kb.vmware.com/kb/1029174) that causes this problem with WinVista-2008-7-2008R2. The VMware tech support person said this issue was supposed to be fixed in ESX 5.0, but has been pushed back until ESX 6.0, at least. It's just too bad their Customization Specification Wizard doesn't alert you to this issue.
Brian
Hmm... vDS, NFS and LACP work great for me. However, it seems like you're jumping in pretty deep with a high-end set of vSphere features. Most installations don't really require LACP, but I can understand the appeal of trying to use it...
None of the vDS and other features matter if the QNAP isn't allowing the mount...
vmkping, but should probably try it with the jumbo MTU: vmkping -s 9000 10.1.2.100 (no need to specify interface). Ensure that works.ip.address:/share/VM//var/log/vobd.log on the ESXi host. If it says something like "The mount request was denied by the NFS server.", the issue is the QNAP.Your screenshot of the vDS configuration looks like it's one host's worth of info. Verify that your config has LACP and the right load balancing modes set. It should look like the following:
Best Answer
This looks like the doc you need. Start at page 130 http://pubs.vmware.com/vsphere-55/topic/com.vmware.ICbase/PDF/vsphere-esxi-vcenter-server-55-security-guide.pdf
Looks like mostly TCP 443, 9443, 9090, 902 but there is a whole table on pg 132
I think this is the part you were asking about:
Connecting Through vCenter Server with the vSphere Client
When you are connecting with the vSphere Client, the required ports depend on whether you connect directly to the ESXi host or you connect to a vCenter Server system.
Port 443
Port 443 connects clients such as the vSphere Web Services SDK to ESXi through the Tomcat Web service or the SDK. The host process multiplexes port 443 data to the appropriate recipient for processing. When the vSphere SDK is connected directly to ESXi, it can use this port to support any management functions related to the host and its virtual machines. Port 443 is the port that clients such as the vSphere SDK assume is available when sending data to ESXi. VMware does not support configuring a different port for these connections.
Port 902
This is the port that vCenter Server assumes is available for receiving data from ESXi. Port 902 connects vCenter Server to the host through the VMware Authorization Daemon (vmware-authd). This daemon multiplexes port 902 data to the appropriate recipient for processing. VMware does not support configuring a different port for this connection
Connecting Directly with the vSphere Client
With the vSphere Client, you can connect directly to an ESXi host.
Port 902
The vSphere Client uses this port to provide a connection for guest operating system MKS activities on virtual machines. It is through this port that users interact with the guest operating systems and applications of the virtual machine. VM