Loading

×Sorry to interrupt
Uncaught ReferenceError: addCTracking is not defined
throws at https://kb.vmware.com/resource/KM_TealiumTrackingJS?v=0.5:100:1

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

Site Recovery Manager or vSphere Replication cannot complete a site pair operation. The received single sign-on token is valid from XX to YY (78313)

Last Updated: 3/16/2024Categories: TroubleshootingTotal Views: 399Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

1. When we login to remote site vcenter within SRM UI, an error is displayed:

"Failed trying to retrieve token: ns0:RequestFailed: EndTime: Thu Nov 14 11:16:07 CST 2019 is not after startTime: Thu Jan 09 15:36:50 CST 2020". The date is probably different.

2. SRM UI displays the error below when trying to pair sites:

ERROR
Operation Failed
SRM server 'Memphis' cannot complete a pair operation. The received single sign-on token is valid from '2024-03-15 14:35:18.862' to '2024-03-15 22:35:18.862'. It is currently '2024-03-15 14:34:07.285'. The tolerance is 30000 milliseconds.
Operation ID: 32662462-9cbb-43c3-92ac-e173b1caa71e
3/15/24, 9:35:19 PM +0700

3. From vCenter, vmware-identity-sts.log on remote vCenter, below log messages can be seen:

[2020-01-09T15:36:50.531+08:00 tomcat-http--43 vsphere.prd 8ac53787-3eb2-412a-8c32-16a0add01c47 DEBUG com.vmware.identity.sts.impl.HoKConditionsAnalyzer] Found HoK certificate [
[
Version: V1
Subject: OU=Site Recovery Manager client, O=VMware vSphere Client, C=US
Signature Algorithm: SHA256withRSA, OID = 1.2.840.113549.1.1.11

Key: Sun RSA public key, 2048 bits
modulus: 26584583412174822090806596074634626235292534271726185542202376482549797065149045088447816850404034771759725273421613115401514482358184897091417150792312990801617108210774900292912087961585096411776099985171583447223194199838220638292779801159740619851739001817375494943253704807011777299676604573163468982754146370538969804640016845886088456290907675282514774846922746232994309075209445683945273800365501026275323792787570369388464911734329087864805565520139549955581234034124130958632594892800628123347200151364961638765297220660199483410880838092273881612533044809866049381909541331146300764356286346868367636437251
public exponent: 65537
Validity: [From: Tue Nov 14 11:16:07 CST 2017,
To: Thu Nov 14 11:16:07 CST 2019]
Issuer: OU=Site Recovery Manager client, O=VMware vSphere Client, C=US
SerialNumber: [ 01671038 08b4]

]

4. From /var/opt/apache-tomcat/logs/dr.log:

2020-01-09 07:36:50,592 [srm-reactive-thread-12] INFO  com.vmware.vim.sso.client.impl.SecurityTokenServiceImpl$RequestResponseProcessor 30ba2fc4-635e-4dfb-8be9-178d1214ba45 pairLogin - Failed trying to retrieve token: ns0:RequestFailed: EndTime: Thu Nov 14 11:16:07 CST 2019 is not after startTime: Thu Jan 09 15:36:50 CST 2020

5. Time synchronization looks good on vCenter/SRM/VR.

6. Restarting vCenter, SRM or vSphere Replication won't help.

Cause

The issue is can be caused by expired SRM & VR certificates or services.

Resolution

NOTE: Take a normal snapshot of the appliance you are renewing the certificate on.

Try the steps in the order mentioned below and check if it works after each step.

1. Renew the certificates of SRM or VR, if you find them to be expired

Change the Site Recovery Manager Appliance Certificate
Change the SSL Certificate of the vSphere Replication Appliance 

2. Restart the dr-client & hms service in vSphere replication appliance

3. Restart the dr-client & srm-server service in Site Recovery Manager appliance

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

KB
•
End Of General Availability of the Free vSphere Hypervisor (ESXi 7.x and 8.x) (2107518)

KB
•
「AMQP ブローカ接続のテスト：失敗 - ACCESS_REFUSED - 認証メカニズム PLAIN を使用したログインが拒否されました。詳細については、ブローカのログ ファイルを参照してください。(Test AMQP Broker Connection: Failed - ACCESS_REFUSED - Login was refused using authentication mechanism PLAIN. For details see the broker logfile.)」 (76149)

Results 1-2 of 2

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware vSphere Replication

VMware vSphere

Related Versions:

VMware vSphere Replication 8.x

Take Our Survey

Support Assistant