disconnected or enter Not Responding state for 90 seconds repeatedly.VirtualCenter.AutoManagedIPV4 parameter from vCenter object > Configure > Advanced Settings may point to a different IP address than what is assigned to the vCenter configstorecli commands and then reviewing it shows that it keeps reverting to the previous vCenter IP addressconfigstorecli config current set -c esx -g services -k vpxa_solution_user_config --path /server_ip --value "<vcenter_ip>"configstorecli config current get -c esx -g services -k vpxa_solution_user_config --path /server_ip/opt/vmware/vpostgres/current/bin/psql -d VCDB -U postgres and executing the below query shows the management_ip and local_ip_address columns dont contain the current vCenter IP addressselect * from vpx_parameter where name like '%Managed%';select id, dns_name, management_ip, local_ip_address from vpx_host;vCenter 7.x, 8.x, 9.x
The issue occurs in scenarios where the newly updated ip address of the vCenter which was edited via Management Interface ( VAMI ) did not get properly updated in the vCenter database.
To resolve the issue, update the vCenter current IP address on the VCDB by following below steps:
service-control --stop vmware-vpxd/opt/vmware/vpostgres/current/bin/psql -d VCDB -U postgresupdate vpx_parameter set value = '#.#.#.#' where name = 'VirtualCenter.AutoManagedIPV4';update vpx_parameter set value = '#.#.#.#' where name = 'VirtualCenter.ManagedIP';update vpx_host set management_ip = '#.#.#.#' where id > '0';update vpx_host set local_ip_address = '#.#.#.#' where id > '0';\qservice-control --start vmware-vpxd