To troubleshoot this issue, ensure that bidirectional heartbeat communications are functioning correctly.
The default port for this communication is UDP 902, but be sure to verify the configured port in the
vpxa.cfg
file on the host. This file also defines the IP address, which manages the host.
Confirm vCenter Server managed IP address
Confirm the vCenter Server managed IP address continuity throughout the environment.
- Determine the managed IP address of the vCenter Server:
- Connect to vCenter Server with the vSphere Client.
- Click Administration > vCenter Server Settings > Advanced Settings.
- Make a note of the IP address in the
ManagedIP
row.
- Determine the IP address configured for vCenter Server:
For vCenter Server installed on a Windows Server:
- From a console or RDP session to the vCenter Server desktop, open a command prompt.
- Run the command:
ipconfig
- Make a note of the IP address and ensure that it matches the managed IP address found in step 1.
For vCenter Server Appliance:
- From a console or SSH session to the vCenter Server Appliance, open a shell prompt. For more information, see Opening a command or shell prompt (1003892).
Note: From the console of the vCenter Server Appliance, press enter on Login.
- Run the command:
ifconfig
- Make a note of the IP address next to inet addr: and ensure that it matches the managed IP address found in step 1.
- Determine the IP address and port that the ESXi host is using for heartbeat traffic:
- Connect to the same host using SSH.
- Check the
vpxa.cfg
file for the heartbeat traffic port by running the command:
- On ESXi 6.x:
grep -i serverport /etc/vmware/vpxa/vpxa.cfg
- Ensure that the port number matches the default heartbeat port of 902.
- Check the
vpxa.cfg
file for the managed IP address by running the command:
- On ESXi 6.x:
grep -i serverIp /etc/vmware/vpxa/vpxa.cfg
-
- Ensure that the IP address matches the managed IP address found in Step 1.
Note: If the IP address is not the same as the one noted in Step 1, see vCenter Server IP address change causes ESX hosts to disconnect (1001493).
Connectivity
Test connectivity between vCenter Server and the ESXihost through the heartbeat network.
Using
telnet
and
netcat
, test connectivity over the heartbeat network through the configured heartbeat port (default 902). For more information, see:
Congestion
Test network congestion:
Other troubleshooting areas