VC ip setup and host ip setup for remote datacenters

[beckhamk]

We are looking to setup a VI3 setup with VC and several host servers at our remote datacenter. We wanted to know the best way to handle the main ip's for the host servers and VC. We expected to give the VC server a public external ip address, and then let the VC communicate with the host servers locally using internal private ip's. Will that work or cause more problems in the long run. We figured we could connect and manage all of the host servers from our local pc using the VI client to the VC server and let it access the host servers.But that is the fuzzy area for us as I believe that should work unless the VI client needs direct communication access to the hosts (which would then mean the hosts servers require an external ip address also.

Thanks for the response in advance!

[beckhamk]

Anyone?

[Dave_Mishchenko · Accepted solution]

There's a list of ports need for communication of VC / ESX and the client here.

http://communities.vmware.com/thread/90174

As noted, you would need access from the VI client directly to the ESX hosts to run remote console sessions and you don't want to start putting your ESX hosts onto the Internet with a public IP (or your VC server for that matter). Are you able to get some sort of VPN connection to the remote data center? Ideally you would put the VC / ESX hosts on a seperate management LAN to seperate these from the VM's LAN. If a VPN connection is not an option, you could run the VI client on a Citrix / Terminal Services server in the remote DC as well.

[beckhamk]

vpn - good idea!