Resolving Platform Services Controller connection problems
The Platform Services Controller server hosts the VMware Lookup Service that registers the location of vSphere components and handles the vCenter Single Sign On process.
Symptoms
If the Platform Services Controller cannot be reached, the tag information will not be displayed in the IBM Data Protection extension. Virtual machine backup operations will also fail.
Resolving the problem
- Ensure that the Platform Services Controller and the vCenter server are installed on the same host.
- Ensure that the Platform Services Controller host is powered on and accessible over the network.
- Ensure that the VMware Lookup Service is active and accepting connections at the following address: https://PSC-FQDN/lookupservice/sdk, where PSC-FQDN is the fully qualified domain name of the Platform Services Controller host.
- Ensure that a data mover is installed on the same server that hosts the Data Protection for VMware vSphere GUI. The data mover node must be configured so that the vCenter server credentials are saved, for example, by using the dsmc set password command in the backup-archive command-line.
For Linux data mover nodes, ensure that
the default password file (/etc/adsm/TSM.PWD) is used.- Ensure that client option vmchost is set by using the same value and format that was used for the vCenter server field during the installation of Data Protection for VMware. The preferred format for the vCenter server address is the vCenter server's fully qualified domain name (FDQN). Use the vCenter server IP address only if it was used during the registration of the vCenter, although the IP address is not preferred by VMware.
- The system time on the data mover host must be in sync with the system time on the Platform
Services Controller and vCenter. The system time and time zone must be set correctly on all three
systems. Otherwise, a Platform Services Controller connection error occurs. The following message is
typical of this type of error:
ANS2378E Single Sign On login to the vSphere Server failed in function visdkGetSecurityToken - Issue. "The time now Wed Apr 20 21:31:58 UTC 2016 does not fall in the request lifetime interval extended with clock tolerance of 600000 ms: [ Wed Apr 20 16:20:46 UTC 2016; Wed Apr 20 16:50:46 UTC 2016). This might be due to a clock skew problem."
ANS2373E The VMware vCloud Suite plug-in library failed to connect to the Platform Services Controller (PSC) and perform a single sign-on session.
If you need to trace this problem, on the backup-archive client command line, enable the client tracing feature by using the VCLOUD trace flag, then run the command again and analyze the trace for additional messages. For example:
04/20/2016 12:30:50.253 : ..\common\vcloudSuiteReturnValue.cpp( 108): vcloudSuiteReturnValue::HandleReturnValue: exception description:TRACEFLAGS VCLOUD TRACEFILE c:\temp\tracex64.txtconnect(): Connections to all Platform Service Controllers failed. The following exceptions were encountered: https://psc.home.lan/sts/STSService/vsphere.local: javax.xml.ws.soap.SOAPFaultException: The time now Wed Apr 20 17:32:02 EDT 2016 does not fall in the request lifetime interval extended with clock tolerance of 600000 ms: [ Wed Apr 20 12:20:50 EDT 2016; Wed Apr 20 12:50:50 EDT 2016). This might be due to a clock skew problem.
- For more information about messages that occurred, see Messages for the IBM Data Protection extension.