vSphere Replication management server could not establish connection to remote vSphere replication management server at 'unknown'
Unable to retrieve pairs from extension server at https://########.##:8043.Unable to connect to HBR Management Server at https://########.##::8043.Reason:Java.net.UnknownHostException:########.##::Name or Service not known
No matching pair server found. Operation ID:#######-####_####_####_#######
VMware vSphere Replication 8.x
VMware vSphere Replication 9.x
VMware Site Recovery Manager 8.x
VMware Live Site Recovery 9.x
The issue is caused by incorrect/short FQDN updated for vSphere Replication. The FQDN is essential for certificate, hence short names are not allowed.
Using Fully Qualified Domain Names (FQDNs) for vCenter Server and ESXi hosts is essential for DNS resolution, SSL certificate management, and smooth network communication, ensuring reliable access to and management of the virtual infrastructure.
For Reference:
For B Site, Hostname is updated with short name.
For A Site, Hostname updated with complete FQDN.
The vSphere Replication is unable to communicate with the vCenter Server because a short hostname was configured on the B site, instead of the fully qualified domain name (FQDN), leading to DNS issues.
Steps to follow:
Log in to the VAMI of the SRM and VR appliance.
Navigate to Summary and verify the Hostname and vCenter Server details.
Go to Networking and check if the Hostname is correctly updated or if it is using a short FQDN.
If incorrect, click Edit and update it with the correct FQDN.
Update the certificate:
Click Change Certificate and proceed with the update.
Reconfigure the appliance.
Once reconfiguration is complete, the connection to the VR and SRM servers will be re-established.
Below is the document to reconfigure the vSphere replication network settings: