The vCenter Server services cannot be started automatically on boot, and services need to be started manually

Products

• VMware vCenter Server

Issue/Introduction

Symptoms:

(1) Log in to vSphere Client shows no healthy upstream.
(2) If the VC is in Linked Mode, enter the following command in the CLI:

usr/lib/vmware-vmdir/bin/vdcrepadmin -f showpartnerstatus -h localhost -u administrator -w passwd 

The command output is as follows:

Partner: vc1_fqdn
Host available:  Yes
Status available: No

(3) Enter the same command in the CLI for Linked Mode center node (star topology) and get the following results:

Partner: vc2_fqdn
Host available:  Yes
Status available: Yes
My last change number:       25151
Partner has seen my change number: 25151
Partner is 0 changes behind.

The active status of the central node VC is not available on problematic VC. But the central node can get the active status of problematic VC.

 

Environment

VMware vCenter Server 7.0.x
VMware vCenter Server 8.0.x

Cause

The VC's PNID is FQDN and the DNS server set by the VC cannot provide domain name resolution properly, causing the VC service to fail to start.
VC cannot resolve the domain name of Linked Mode partner VC.

Resolution

(1) Verify the DNS connectivity of the VC

ping dns_server_ip

If the ping does not work, it means that there is a problem with the network, first exclude the network problem, and then do the next step.

(2) Verify DNS resolution function

nslookup vc_fqdn_ip

# or

dig vc_fqdn_ip

Verify if the VC domain name and the domain name of VC in linked mode can be resolved properly.
If it cannot resolve, please check the content of the relevant A record in the DNS server.

(3) After fixing DNS problems, restart VCSA.

Before reboot, take a memory snapshot or file-based backup for the VC. If it is a linked mode VC, you need to take a shutdown snapshot of all VCs before operation.

Workaround:
You can start by adding domain name resolution records to the VC's /etc/hosts directory until the DNS service returns to normal.

Additional Information

Impact/Risks:

After VC reboot, most services cannot start automatically and need to start the unrunning services manually. An exception occurs in Linked Mode status.