vCenter not visible in Enhanced Linked Mode

Products

• VMware vCenter Server

Issue/Introduction

After upgrade of multiple vCenter's in environment some of vCenter's are not visible in UI.

Checking partner status following Determining replication agreements and status with the Platform Services Controller (PSC)  returns 0 changes behind.

 

On vCenter that is not seeing missing node you see following in logs :

In var/log/vmware/vsphere-ui/logs/vsphere_client_virgo.log you will see similar task mentioned.

Task will reference all visible nodes being added to group. 

FQDN and IDs are unique to environment

 

 [INFO ] vim-authentication-pool-432  70001045 100086 200037 c.v.vise.vim.commons.extensions.impl.Linked
VcGroupRegistryImpl    Added a linked VC group to registry. Endpoints: https://XXX.XXX.XX:443/sdk(33333#####,vsphere.local(44444#####)),https://ZZZ.ZZZ.ZZ:443/sdk(55555######,vsphere.local(66666#########)),

 

In var/log/vmware/vsphere-ui/logs/catalina.log :

[http-nio-127.0.0.1-5090-exec-8] com.vmware.vum.client.exceptions.GlobalExceptionHandler.logException ServiceUnavailable (com.vmware.vapi.std.errors.service_unavailable) =>
 {
    messages = [LocalizableMessage (com.vmware.vapi.std.localizable_message) => {
    id = apigw.error.vcenterIdNotFound,
    defaultMessage = vCenter not found: 11111#####
    args = [],
    params = <null>,
    localized = <null>
}],
    data = <null>,
    errorType = SERVICE_UNAVAILABLE
}

 

Checking logs on vCenter that see all nodes in var/log/vmware/vsphere-ui/logs/vsphere_client_virgo.log you will see similar task :

This task will list all nodes in environment:

[INFO ] vim-authentication-pool-432  70001045 100086 200037 c.v.vise.vim.commons.extensions.impl.Linked
VcGroupRegistryImpl    Added a linked VC group to registry. Endpoints: https://XXX.XXX.XX:443/sdk(11111#####,vsphere.local(22222#####)),https://ZZZ.ZZZ.ZZ:443/sdk(33333######,vsphere.local(44444#########)),https://YYY.YYY.YY:443/sdk(55555#####,,vsphere.local(66666#####))

This task will reference missing vCenter and it will contain same ID mentioned in catalina.log on vCenter that is not seeing all nodes.

 

 

Environment

vCenter Server 8.x

Cause

The service registration  "vcenterserver"  is missing in VMDir 

 

Resolution

Connect to the affected vCenter using SSH.

• Run this command to enable access the Bash shell:

Type shell and press Enter

To create a text file with a list of the services registered within the vCenters , run this command:

/usr/lib/vmware-lookupsvc/tools/lstool.py list --url http://localhost:7090/lookupservice/sdk --type vcenterserver > /tmp/psc_services.txt --no-check-cert

In the generated file search for vcenterserver services :

grep "vcenterserver" /tmp/psc_services.txt

You should have one Service Type: vcenterserver by vCenter registered in the  linked mode environment

If you are missing one of the service registration:

Run fixpsc rebuild against healthy node in environment:

Fix PSC/vmdir inconsistencies using fixpsc python script