When the SSL certificate on the vCenter is updated the thumbprint changes.
In SRM you have to reconfigure to the vCenter again to update the SSL certificated.
Some times this does not happen and the vmware-dr.log file shows entries similar to these:
2024-04-08T13:44:57.599-07:00 info vmware-dr[92978] [SRM@6876 sub=IO.Http] Set user agent error; state: 1, (null), N7Vmacore3Ssl18SSLVerifyExceptionE(SSL Exception: Verification parameters:
--> PeerThumbprint: 01:23:45:67:89:AB:CD:EF:01:23:45:67:89:AB:CD:EF:01:23:45:67:89:AB:CD:EF:01:23:45:67:89:AB:CD:EF
--> ExpectedThumbprint: FE:DC:BA:98:76:54:32:10:FE:DC:BA:98:76:54:32:10:FE:DC:BA:98:76:54:32:10:FE:DC:BA:98:76:54:32:10
--> ExpectedPeerName: vmwareVC01.local.com
--> The remote host certificate has these problems:
-->
--> * unable to get local issuer certificate)
--> [context]zKq7AVECAAQAAMX4YgELdm13YXJlLWRyAADM6xtsaWJ2bWFjb3JlLnNvAACkbjMAmV0zAGkEMwAgIDMA9iEzAN5INQDiYTUAsItKAbCOAGxpYnB0aHJlYWQuc28uMAAC7/oPbGliYy5zby42AA==[/context]
2024-04-08T13:44:57.601-07:00 error vmware-dr[92978] [SRM@6876 sub=IO.Http] User agent failed to send request; (null), N7Vmacore3Ssl18SSLVerifyExceptionE(SSL Exception: Verification parameters:
--> PeerThumbprint: 01:23:45:67:89:AB:CD:EF:01:23:45:67:89:AB:CD:EF:01:23:45:67:89:AB:CD:EF:01:23:45:67:89:AB:CD:EF
--> ExpectedThumbprint: FE:DC:BA:98:76:54:32:10:FE:DC:BA:98:76:54:32:10:FE:DC:BA:98:76:54:32:10:FE:DC:BA:98:76:54:32:10
--> ExpectedPeerName: vmwarexx.local.com
--> The remote host certificate has these problems:
-->
--> * unable to get local issuer certificate)
{Note: the above screen and log file entries are examples only; your entries will look different for the dates in the logs and the specific thumbprints for your vCenter}
VMware Site Recovery Manager 8.x
VMware Site Recovery Manager 9.x
The reconfigure handshake fails and is unable to register to the new thumbprint due to the mis-match. This does not always happen and may be due to a environmental issue on the SRM appliance.
Perform a power cycle of the SRM appliance and proceed with the reconfiguration, as this should resolve the issue.
If the issue persists after the power cycle please contact Broadcom Support to investigate further.