All vCenters are not listed in Enhanced Linked Mode in VMware vCenter Server 6.0

Products

• VMware vCenter Server

Issue/Introduction

Symptoms:

• One or more vCenter is missing in vCenter Inventory which is configured in Enhanced Linked Mode
• vCenter web Client reports error "Login failed due to invalid credentials for one or more vCenter Server systems vcenter"
• Missing vCenter's vmware-identity-sts.log reports clock skew errors

[2015-09-15T21:00:57.407Z tomcat-http--28 vcsa.domain.local fb028187-####-####-####-########ad5 DEBUG com.vmware.identity.sts.impl.STSFactoryImpl] Get STS for tenant: <domain_name>
[2015-09-15T21:00:57.407Z tomcat-http--28 vcsa.domain.local fb028187-####-####-####-########ad5 TRACE com.vmware.identity.sts.impl.STSImpl] issue() token...
[2015-09-15T21:00:57.407Z tomcat-http--28 vcsa.domain.local fb028187-####-####-####-########ad5 DEBUG com.vmware.identity.sts.impl.STSImpl] Validation of request
[2015-09-15T21:00:57.407Z tomcat-http--28 vcsa.domain.local fb028187-####-####-####-########ad5 DEBUG com.vmware.identity.sts.impl.STSImpl] The request received is valid from 2015-09-15T20:37:18.882Z till 2015-09-15T20:47:18.882Z and now is: Tue Sep 15 21:00:57 UTC 2015
[2015-09-15T21:00:57.415Z tomcat-http--28 vcsa.domain.local fb028187-####-####-####-########ad5 TRACE com.vmware.identity.perf] 'idm.getClockTolerance' took 8 ms.
[2015-09-15T21:00:57.415Z tomcat-http--28 vcsa.domain.local fb028187-####-####-####-########ad5 TRACE com.vmware.identity.sts.impl.LifetimeConvertor] Gets date object from request for datetime: 2015-09-5T20:37:18.882Z
[2015-09-15T21:00:57.415Z tomcat-http--28 vcsa.domain.local fb028187-####-####-####-########ad5 TRACE com.vmware.identity.sts.impl.LifetimeConvertor] Gets date object from request for datetime: 2015-09-5T20:47:18.882Z
[2015-09-15T21:00:57.415Z tomcat-http--28 vcsa.domain.local fb028187-####-####-####-########ad5 ERROR com.vmware.identity.sts.impl.STSImpl] The current time Tue Sep 15 21:00:57 UTC 2015 does not fall in the requestlifetime interval extended with clock tolerance of 600000 ms: [Tue Sep 15 20:27:18 UTC 2015; Tue Sep 15 20:57:18 UTC 2015). This might be due to a clock skew problem.
[2015-09-15T21:00:57.416Z tomcat-http--28 vcsa.domain.local fb028187-####-####-####-########ad5 DEBUG com.vmware.identity.sts.ws.StsServiceImpl] com.vmware.identity.sts.RequestExpiredException: The time now Tue Sep 15 21:00:57 UTC 2015 does not fall in the request lifetime interval extended with clock tolerance of 600000 ms: [ Tue Sep 15 20:27:18 UTC 2015; Tue Sep 15 20:57:18 UTC 2015). This might be due to a clock skew problem.

• This issue may appear after a network issue

Environment

VMware vCenter Server 6.0.x

Cause

This issue occurred because of the time skew between the PSC and other vCenter Servers

Resolution

To resolve this issue we have to fix the time skew problem between the vCenters and PSC.

 

In order to avoid time skew issues it's recommended to configure NTP on Guest Operating System where vCenter is installed or on vCenter appliance.

 

To configure NTP on a vCenter Appliance 6.0 follow the article Configuring NTP on the vCenter Server Appliance 6.0 (2113610)

 

In most cases, the missing vCenter Server will not be set with proper time.

Additional Information

Configuring NTP on the vCenter Server Appliance 6.0