vSphere Replication 9.x
We see this type of behavior after a vSphere Replication certificate renewal.
As a result, one of the vSphere Replication appliances has a stale certificate and thumbprint entry in it's 'hbrserverentity' datastore.
This stale certificate and thumbprint entry will cause communications issues between the paired vSphere Replication appliance and the ESXi hosts on the paired site.
Review the certificate being presented on the local side vSphere Replications hms.log for the paired vSphere Replication appliance.
Review this certificate against the output of the 'openssl' command ran on the paired vSphere Replication appliance.
If these certificates do not match, open up a support request with Broadcom Support for further assistance.
Reviewing the certificate in the the hms log file:
=====================
Run the following command on the vSphere Replication appliance that does not have the enhanced replication mappings errors:
echo | openssl s_client -connect xx.xx.xx.xx:443
*Note: The IP address used in the command above needs to match the IP address you searched for in the hms.log.
=====================
Review both certificates to ensure that they match. You can review either the beginning or ending section of the certificate.