Symptoms
- When an ESXi 5.0 host is added to vCenter Server 5.0, the host is added correctly but approximately 60 seconds later it is marked as
Not Responding
. - Disabling the ESXi 5.0 firewall allows the host to connect.
- When ESXi 3.x and 4.x hosts are added, they do not exhibit the same behavior.
Cause
Resolution
There are two methods to resolve this issue:
Note: Before beginning the resolution steps, determine which port vCenter Server is currently using to send traffic.
To determine the traffic port in use:
- Connect to the ESXi 5.0 host using SSH. For more information, see Using ESXi Shell in ESXi 5.0 and 5.1 (2004746).
- Use the
less
orgrep
command to to determine the port in use:less /etc/vmware/vpxa/vpxa.cfg
or:grep serverPort /etc/vmware/vpxa/vpxa.cfg
The port number in use is contained in theserverPort
tags. For example:<vpxa>
<bundleVersion>1000000</bundleVersion>
<datastorePrincipal>root</datastorePrincipal>
<hostIp>xxx.xxx.xxx.xxx</hostIp>
<hostKey>52db3386-b766-889a-d778-da0c8851c81e</hostKey>
<hostPort>443</hostPort>
<licenseExpiryNotificationThreshold>15</licenseExpiryNotificationThreshold>
<memoryCheckerTimeInSecs>30</memoryCheckerTimeInSecs>
<serverIp>xxx.xxx.xxx.xxx</serverIp>
<serverPort> 9020</serverPort>
</vpxa>
In this example,serverPort
is set to9020
, instead of the default port number902
.
Method 1: Add a firewall rule to the ESXi host to allow traffic on the alternate heartbeat port
To add a firewall rule to the ESXi host:
- Connect to the ESXi 5.0 host using SSH. For more information, see Using ESXi Shell in ESXi 5.0 and 5.1 (2004746).
- Navigate to the
/etc/vmware/firewall/
directory:cd /etc/vmware/firewall/
- Create and edit a new file named
heartbeat.xml
using thevi
command:vi heartbeat.xml
- Enter the configuration info into the file as shown in this example:
<!-- Firewall configuration sample -->
<ConfigRoot>
<service>
<id>nondefheartbeat</id>
<rule id='0000'>
<direction>inbound</direction>
<protocol>udp</protocol>
<porttype>dst</porttype>
<port> 9020</port>
</rule>
<rule id='0001'>
<direction>outbound</direction>
<protocol>udp</protocol>
<porttype>dst</porttype>
<port> 9020</port>
</rule>
<enabled>false</enabled>
<required>false</required>
</service>
</ConfigRoot>
Note: The alternate port number used in this example is9020
. Be sure to use the port number you determined earlier for your configuration. - Save and close the file.
- Enable the new firewall rule by running these commands:
esxcli network firewall unload
esxcli network firewall load
esxcli network firewall refresh
Method 2: Configure vCenter Server to use the default port number 902
Note s:
- Ensure that the heartbeat firewall rule is also set to default port 902 prior to changing the port for vCenter Server.
- Before changing the port number back to the default 902, ensure that no other application installed on vCenter Server is using this port.
- This procedure modifies the Windows registry. Before making any registry modifications, ensure that you have a current and valid backup of the registry and the virtual machine. For more information on backing up and restoring the registry, see the Microsoft Knowledge Base article 136393.
The preceding link was correct as of April 16, 2013. If you find the link is broken, provide feedback and a VMware employee will update the link.
To configure vCenter Server to use port number 902:
- Stop the VMware VirtualCenter Server service. For more information, see Stopping, starting, or restarting vCenter services (1003895).
- Click Start > Run, type regedit, and click OK. The Registry Editor window opens.
- Navigate to:
HKEY_LOCAL_MACHINE\SOFTWARE\VMware, Inc.\VMware VirtualCenter
- Modify the registry key
heartbeatport
and change the value to902
. - Change the windows firewall to accept port 902:
- Navigate to Windows Firewall > Allow a program or feature through Windows firewall.
- Select VMware vCenter Server > Host Heartbeat.
- Click Details and change the port to 902 .
- Start the VMware VirtualCenter Server service.
Note: The ESXi host may show as disconnected. Reconnect the host so that the new configuration info is saved to thevpxa.cfg
file.
Source:-
http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2020100
No comments:
Post a Comment