Anda di halaman 1dari 3

Using NAT between the vCenter Server system and ESXi/ESX hosts (1...

https://kb.vmware.com/selfservice/microsites/search.do?language=en_...

Knowledge Base

Using NAT between the vCenter Server system and ESXi/ESX hosts (1010652)
Details
Each time you add an ESXi/ESX host to vCenter Server, the IP address of vCenter Server is recorded on the ESXi/ESX host. If the host is behind a NAT
and the vCenter Server is on a different network (and thus the address is not accessible due to the NAT), the host disconnects from vCenter Server after
about a minute.
For example, the vCenter Server system might be on the main network (10.10.10.0), and a few of the ESXi/ESX hosts might be behind a firewall in the
192.168.5.x network. The hosts cannot reach the main network and thus become disconnected from vCenter Server.

Solution
Using NAT between the vCenter Server system and ESXi/ESX hosts is an unsupported configuration. For more information on network requirements, see
the
section under the
section in the
vSphere Installation and Setup (https://www.vmware.com/support/pubs/vsphere-esxi-vcenter-server-pubs.html) guide.

Workaround
Note: This workaround is provided to aid customers in complex environments. It is an unsupported configuration. VMware will only provide best effort
support for this configuration.
As a workaround, for each ESXi/ESX host you can specify a reachable address that the host can use to communicate back to vCenter Server. In this case,
the reachable address is the NAT address, which you configure to redirect the communication back to vCenter Server.
To configure the IP address to use, you can use two settings named serverIP and preserveServerIp. With these settings, you can statically set an
IP address, which the ESXi/ESX host will use to communicate back to the vCenter Server.
Note: For ESX 3.5 and VirtualCenter 2.5, Update 3 supports this solution. Install Update 3 before implementing this solution.

1. Ensure that the NAT device is configured to redirect UDP traffic on port 902 to the vCenter Server.
2. Add the ESXi/ESX host to the vCenter Server inventory.
Note: This causes the vCenter agent (vpxa) service to be installed on the host.
3. Log in to the ESXi/ESX host as root.
4. Navigate to the /etc/opt/vmware/vpxa/ directory in the ESXi/ESX file system.
Note: In ESXi 5.x/6.0, navigate to /etc/vmware/vpxa.
5. Open the vpxa.cfg file using an text editor.
6. In the file, change the serverIp setting and add the preserveServerIp setting. For the serverIP tag, enter the NAT IP address.
For example:

1 of 3

7/18/2016 8:30 PM

Using NAT between the vCenter Server system and ESXi/ESX hosts (1...

2 of 3

https://kb.vmware.com/selfservice/microsites/search.do?language=en_...

<config>
<vpxa>
...
<serverIp>
</serverIP>
<preserveServerIp>true</preserveServerIp>
</vpxa>
...
</config>
7. Save the changes and close the file.
8. Restart the vCenter agent service by running this command in the ESXi/ESX service console/SSH session:
For ESX:
# service vmware-vpxa restart
For ESXi:
# services.sh restart
9. Reconnect the ESXi/ESX host.
Note: Consider this scenario: The ESXi/ESX host and the vCenter Server are behind different NATs, the main subnet is 10.10.10.0, the ESXi/ESX host is
behind a firewall in the 192.168.5.x network, and the vCenter Server is behind a firewall in the 172.18.20.x network. If you have the underlying network
configured so that the 172.x network knows where to direct traffic from the 192.x network, the configuration might work. However, the general use case
for this article is not a double NAT.

Additional Information
For translated versions of this article, see:
: vCenter Server ESXi/ESX NAT (2083643) (/selfservice/search.do?cmd=displayKC&docType=kc&docTypeID=DT_KB_1_1&
externalId=2083643)

: vCenter Server ESXi/ESX NAT (2087917) (/selfservice/search.do?cmd=displayKC&docType=kc&docTypeID=DT_KB_1_1&


externalId=2087917)

Tags
nat-vcenter-esx-esxi

Update History
05/25/2010 - Emphasized that using NAT between the vCenter Server system and ESX hosts is an unsupported configuration.
11/28/2011 - Added ESXi 5.x to Products
01/19/2016 - Added ESXi and vCenter Server 6.0 to Products.

Request a Product Feature


To request a new product feature or to provide feedback on a VMware product, please visit the Request a Product Feature (http://www.vmware.com/contact
/contactus.html?department=prod_request) page.
Permalink to: Using NAT between the vCenter Server system and ESXi/ESX hosts (https://kb.vmware.com/kb/1010652)
Read our blog (http://blogs.vmware.com/kb/)
Watch KBTV (http://blogs.vmware.com/kbtv/)
Content (http://www.vmware.com/landing_pages/knowledgebase-content-request.html)

Follow us (https://twitter.com/vmwarecares)

Request New

1 (javascript:void( rate(1,this) ))
2 (javascript:void( rate(2,this) ))
3 (javascript:void( rate(3,this) ))

7/18/2016 8:30 PM

Using NAT between the vCenter Server system and ESXi/ESX hosts (1...

3 of 3

https://kb.vmware.com/selfservice/microsites/search.do?language=en_...

4 (javascript:void( rate(4,this) ))
5 (javascript:void( rate(5,this) ))
34 Ratings

Actions
Bookmark Document (javascript:addBookmark(actionBoxUtil.docURL, actionBoxUtil.docTitle);)
Print Document (javascript:window.print())
Subscribe to Document (/selfservice/microsites/microsite.do?cmd=displayKC&docType=kc&docTypeID=DT_KB_1_1&externalId=1010652&format=rss)
(https://www.addthis.com/bookmark.php?v=250&username=xa-4b5f42f36e60a29e)

KB: 1010652
Updated: Jun 22, 2016
Categories:
How to
Troubleshooting
Languages:
English

Product(s):
VMware ESX
VMware ESXi
VMware VirtualCenter
VMware vCenter Server

Product Version(s):
VMware ESX 3.5.x
VMware ESX 4.0.x
VMware ESX 4.1.x
VMware ESXi 3.5.x Embedded
VMware ESXi 3.5.x Installable
VMware ESXi 4.0.x Embedded
VMware ESXi 4.0.x Installable
VMware ESXi 4.1.x Embedded
VMware ESXi 4.1.x Installable
VMware ESXi 5.0.x
VMware ESXi 5.1.x
VMware ESXi 5.5.x
VMware ESXi 6.0.x
VMware VirtualCenter 2.5.x
VMware vCenter Server 4.0.x
VMware vCenter Server 4.1.x
VMware vCenter Server 5.0.x
VMware vCenter Server 5.1.x
VMware vCenter Server 5.5.x
VMware vCenter Server 6.0.x

7/18/2016 8:30 PM

Anda mungkin juga menyukai