Home > HowTo, Linux > ESX Loses Connection to VC

ESX Loses Connection to VC

January 28th, 2010 Leave a comment Go to comments

ERROR:
warning ‘Heartbeat’] Failed to bind heartbeat socket (-1). Using any IP.

Our ESX server is in a remote site using NAT to connect to the Virtual Center and it loses connection because the ports are not open and the IP NAT is not configured.

From the ESX host to the VCenter you will need the following ports
5989 TCP (CIM Client)
902 UDP  (heathbeat)
ICMP

To force the NAT IP you will need to add <preserveServerIp>true</preserveServerIp> and
enter the IP
# vi /etc/opt/vmware/vpxa/vpxa.cfg
<vpxa>
<bundleVersion>15</bundleVersion>
<datastorePrincipal>root</datastorePrincipal>
<hostIp>10.5.61.27</hostIp>
<hostKey>52e73f23-0b8d-81f0-4a5f-800f884754c3</hostKey>
<hostPort>443</hostPort>
<licenseExpiryNotificationThreshold>15</licenseExpiryNotificationThreshold>
<memoryCheckerTimeInSecs>30</memoryCheckerTimeInSecs>
<serverIp>10.5.62.1</serverIp>
<serverPort>902</serverPort>
<preserveServerIp>true</preserveServerIp>
</vpxa>
:wq
# service mgmt-vmware restart

On the VC:
click Administration > vCenter Server Settings.
Click Runtime Settings.
Under Managed IP address, type the IP address of the external address of the NAT device.
Reconnect the ESX host.
Keep an eye on the log:
tail -f /var/log/vmware/vpx/vpxa.log

References:
http://kb.vmware.com/kb/1012382
http://kb.vmware.com/kb/1010652

Categories: HowTo, Linux Tags: , , , , , , , ,
  1. No comments yet.
  1. No trackbacks yet.

VAMOVE *

*