A newly deployed 9.x vSphere replication manager is failing to register with vCenter.
While trying to configure appliance the registration is failing with error
ERROR
Operation Failed:A general system error occurred: Failed to register VRMS.
Operation ID: 41bf9981-xxxx-xxxx-xxxx-9a4368f2242d
VLSR 9.x
The issue is caused due to mismatch of the vCenter CN with the address being used to register from the VRMS.
The drconfig.log on the vSphere replication appliance has following entries.
Caused by: javax.net.ssl.SSLException: Certificate for <VC IP> doesn't match common name of the certificate subject: VC FQDN
--> at org.apache.http.conn.ssl.AbstractVerifier.verify(AbstractVerifier.java:185)
--> at org.apache.http.conn.ssl.StrictHostnameVerifier.verify(StrictHostnameVerifier.java:68)
--> at org.apache.http.conn.ssl.AbstractVerifier.verify(AbstractVerifier.java:153)
--> at com.vmware.vim.vmomi.client.http.impl.ThumbprintTrustManager$HostnameVerifier.verify(ThumbprintTrustManager.java:534)
--> faultCause = (vmodl.MethodFault) null,
--> faultMessage = <unset>,
--> reason = "Failed to register VRMS."
--> msg = ""
Verify the vCenter certificate is registered by FQDN or IP and use the same CN to configure the newly deployed appliance.
Example:
In the current scenario the configure appliance was being done using the vCenter IP however the vCenter certificate was using the CN as vCenter FQDN.