- Mismatch in NTP (Network Time Protocol) configuration across the following components:
• Site Recovery Manager (SRM)
• vCenter Server
• ESXi Hosts
- This leads to authentication token errors due to out-of-sync system clocks.
vmware-dr.log :
2025-06-05T19:30:13.162Z error vmware-dr[02744] [SRM@6876 sub=DrSiteSiteManager opID=xxxx-xxxx-xxxx-xxxx-xxxx-pairSrm-remotePa
irSrm] Failed to pair with SRM server at LS++ with url 'https://srmserver:443/lookupservice/sdk', thumbprint 'xx:xx:
xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx', VC 'b340b039-878e-4c48-a063-3be35ddb39e1'
--> (dr.fault.InvalidTokenLifetime) {
--> faultCause = (vmodl.MethodFault) null,
--> faultMessage = <unset>,
--> from = "2025-06-05T19:30:12.997Z",
--> to = "2025-06-06T03:30:12.997Z",
--> now = "2025-06-05T19:28:55.776395Z",
--> tolerance = "30000"
--> msg = "Received SOAP response fault from [<SSL(<io_obj p:0x00007fac400086f0, h:34, <TCP '192.168.110.155 : 40584'>, <TCP '172.17.0.
17 : 443'>>), /drserver/vcdr/vmomi/sdk>]: loginByToken
--> The received single sign-on token is valid from '2025-06-05 19:30:12.997' to '2025-06-06 03:30:12.997'. It is currently '2025-06-05 19
:28:55.776'. The tolerance is 30000 milliseconds."
--> }
--> [context]zKq7AVECAAQAAMX4YgEKdm13YXJlLWRyAADM6xtsaWJ2bWFjb3JlLnNvAAF6/1ZsaWJkci10eXBlcy5zbwAB9vNJAuHsIWxpYnZtb21pLnNvAAKz9SEA3kg1AOJhN
QCwi0oDsI4AbGlicHRocmVhZC5zby4wAATv+g9saWJjLnNvLjYA[/context]