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

Failed to retrieve pairs from Site Recovery Manager Server: The tolerance is 30000 milliseconds. (77235)

Last Updated: 7/6/2023Categories: TroubleshootingTotal Views: 10789Language:
Chinese (Simplified)JapaneseEnglish

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

Pairing an SRM server from vCenter results with the following error message:

Failed to retrieve pairs from Site Recovery Manager Server at https://<srm_server_ip_or _hostname>:9086/vcdr/vmomi/sdk. The received single sign-on token is valid from ‘<YYYY-MM-DD HH:MM:SS.MSS>’ to ‘<YYYY-MM-DD HH:MM:SS.MSS>’. it is currently ‘<YYYY-MM-DD HH:MM:SS.MSS>’. The tolerance is 30000 milliseconds.

When you compare the time on vCenter and Site Recovery Manager, you see a difference of greater than 30 seconds. See the three methods for checking the precise time below:

vCenter or Site Recovery Manager VAMI | Check current time:

Browse to the VAMIs of the vCenter and/or SRM servers:

vCenter Server: https://<vcenter_ip_or_hostname>:5480

SRM Server: https://<srm_ip_or_hostname>:5480

Browse to the Time section. If comparing two VAMIs, try to refresh each VAMI as close to the same time as possible.

Photon Linux command line | Check current time:

# date

Purpose

This article provides aids in diagnosing and resolving a time synchronization issue between vCenter and the Site Recovery Manager.

Cause

Time drift is a normal occurrence on all operating systems. Embedded services within the operatings systems are generally designed to synchronize, on a regular schedule, to an external authoritative time source. If synchronization is not occurring regularly or effectively, drift can occur between two or more systems causing any number of issues including authentication failures and network session disconnects.

If vCenter Server and Site Recovery Manager have time drifted to more than a 30 second difference, vCenter will not authenticate to Site Recovery Manager.

Resolution

Synchronize the time on either (or both) the vCenter and Site Recovery Manager servers to their respective NTP time server sources to bring them to +/- 30 seconds of each other.

Example Procedure:

Compare the NTP or time sources for both vCenter and Site Recovery Manager to validate proper configuration and to help determine which system is out of sync. Ideally, both servers should have the same source, synchronized to the ESXI hosts that each are hosted on.

vCenter 6.7 or higher Photon Linux deployment

Access the vCenter Server Appliance Web Console (VAMI) through a web browser:

https://<vcenter_ip_or_hostname>:5480

Login as root

Select Time

Note the ip address(es) and/or hostname(s) under Time Synchronization / Time Servers

Site Recovery Manager 8.4 and higher Appliance (Photon deployment)

Access the SRM Server Appliance Web Console (VAMI) through a web browser:

https://<srm_ip_or_hostname>:5480

Login as root

Select Time

Note the ip address(es) and/or hostname(s) under Time Synchronization / Time Servers

Compare the time on the vCenter and Site Recovery Manager servers to the NTP source for each.

Synchronize the out-of-sync server to its source.

Photon Linux (vCenter or SRM Photon Linux deployment)

Run the following commands to stop the ntpd service, synchronize it with an NTP server, and restart the service.

# service ntpd stop

# ntpd -gq

# service ntpd start

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
Chinese (Simplified)JapaneseEnglish

Attachments

Additional Resources

KB
•
具有 vGPU 和大量内存的虚拟机在 vMotion 期间变得无响应 (77212)

KB
•
[VMC on AWS] VMC SDDC 内のコンピューティング ワークロードの NTP サーバとして Amazon Time Sync Service を使用する (77306)

KB
•
vCloud Director テナント ポータルのメイン メニューに vCloud Availability プラグインがない (77180)

Results 1-3 of 3

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware vSphere Replication

VMware vSphere

VMware Site Recovery Manager

Related Versions:

Take Our Survey

Support Assistant