Hi all, I really hope someone can help here.
We have 3 ESXi 5.1 hypervisor boxes. They are all external to our office location. They are located in 3 DC's.
We run vcenter server on a box within our office lan, 192.168.10.10 (private)
All 3 esxi boxes are locked down on public IP space, with firewalling on each, and our vcenter server in the office sits behind our office FW of course.
Our vcenter server (192.168.10.10) will happily talk to the 3 esxi boxes (public) for management of vm's, console, hardware management etc, as we have set up the correct rules in firewalls in the office and in the 3 DC's
This is the problem when we are trying to use update manger:
Our vcenter server install is on machine 192.168.10.10 and it also has update manager installed on it, so its all on one box. The vcenter server/update manger can go out to the internet to get patches/updates, talk to the three esxi boxes etc, however in the update manager settings, the only option you have to set the address of update manager is to set the IP address to either 192.168.10.10, or to its local machine name, ie vcenter, you cant set the public IP of the office
What this means is that the agents running on the ESXi hosts are told to get updates from 192.168.10.10, which of course being private IP they can never get to.
How do we make the ESXi boxes actually get talking to the update manager? Im not talking about repoos here, im talking about the SOAP connection between ESXi and update manager. Its weird why update manager does not work the same way vcenter does?
Im not sure if im missing something here, but there seems no way to tell the ESXi boxes to talk to our office public IP address when dealing with update manager.