Note: When vSphere Replication Management Server (VRMS) tries to validate the SSL certificate of vCenter Server, it is either unable to connect to vCenter Server because of DNS resolution or SSL is invalid because it is against the FQDN and not the IP address.
To resolve this issue, use one of these options:
- Ensure that there is no DNS issues and the FQDN of vCenter Server can be resolved from inside the VR appliance.
- Add a static entry to /etc/hosts of the VR appliance to point to vCenter Server:
echo "xxx.xxx.xxx.xxx vcenter_FQDN.domain.local vcenter_FQDN" >>/etc/hosts
After performing one of the preceding options, re-register the appliance using the FQDN of vCenter Server.
To re-register the appliance using the FQDN of vCenter Server:
- Log in to the VR server as the root user.
- Run this command to change the directory to /opt/vmware/hms/libs:
# cd /opt/vmware/hms/libs
- Run this command to re-register the appliance:
# java -jar va-util.jar -cmd certauth -host VC_FQDN -port 80 -user VC_username -pass VC_password -extkey com.vmware.vcHms -keystore /opt/vmware/hms/security/hms-keystore.jks -keystorealias jetty -keystorepass vmware
Note: In VMware vSphere Replication 6.0.x, the default keystore password is random. The password vmware no longer applies. To acquire the password, run this command:
cat /opt/vmware/hms/conf/hms-configuration.xml | grep keystore
- Restart the VRMS service using this command:
# service hms restart
Note: If the IP address of vCenter Server is changed, you have to edit the /etc/hosts file and update (or remove if you are able to fix the DNS) the entry added earlier.