VMware vCenter Server
Note: Before starting, see Restarting the Management agents on an ESX Server for important information on restarting the mgmt-vmware service.
The ESXi hosts disconnect because they store the IP address of the vCenter Server in configuration files on each of the individual servers. This incorrect address continues to be used for heartbeat packets to vCenter Server.
There are two methods to get the ESXi hosts connected again. Try each one in the order specified, testing the results each time.
Before performing either method, ensure that the Managed IP Address of the vCenter Server is updated to reflect the new IP address being used. For more information, see Verifying the vCenter Server Managed IP Address.
Method 1 - edit the vpxa configuration
vpxa.cfg
file using a text editor and change the serverIp
parameter to the new IP of the vCenter Server.
/etc/vmware/vpxa/vpxa.cfg
.vpxa.cfg
file no longer exists, as the vpxa configuration was moved to the ESXi config store. Therefore, in the event that /etc/vmware/vpxa/vpxa.cfg
cannot be found on ESXi 7.0, follow these steps instead:configstorecli config current get -c esx -g services -k vpxa_solution_user_config -outfile vpxa.json
rm -f vpxa.json.bak; cp vpxa.json vpxa.json.bak -f
sed -e 's/ "server_ip".*/ "server_ip": "<vcenter_ip>
",/g' -i vpxa.json
configstorecli config current update -c esx -g services -k vpxa_solution_user_config -infile vpxa.json
configstorecli config current get -c esx -g services -k vpxa_solution_user_config
/etc/init.d/vpxa restart
Method 2 - disconnect/reconnect the ESXi in vSphere Client
Note: Do not remove the ESXi host from vCenter inventory if the host is attached to a Distributed Switch (vDS). For more information, see Moving an ESX/ESXi host with vDS from one vCenter Server to another.
vpxa_solution_user_config
" is reverting back to old VC IP: configstorecli config current get -c esx -g services -k vpxa_solution_user_config
Verify that vCenter Server Settings - > Runtime settings -> vCenter Server managed address is reflecting the OLD IP address, update with the new IP address and restart the vCenter Server.
If an incorrect Managed IP Address is configured for VirtualCenter.AutoManagedIPV4
and VirtualCenter.AutoManagedIPV6
, the vCenter Server does not receive heartbeats from the ESX/ESXi host causing it to go into a disconnected state.
For related information, see Verifying the VirtualCenter Managed IP Address.