vCenter UI reports SRM or VRMS plugin as undefined after the upgrade.

Products

VMware Live Recovery

Issue/Introduction

Symptoms:

* Site Recovery plug-in shows invalid from vCenter home icon after upgrading to SRM 9.0.2

VRMS plugin after upgrade:

vCenter shows successful status under Client Plugins for VMware Site Recovery. Reconfiguration of SRM is success.

Example

From below SRM or VRMS logs shows issue with hostname <hostname>.<domain> and pointing to validate SRM certificates.

/opt/vmware/support/logs/dr-client-plugin/drplugin.logs:

2025-01-14 05:42:51,481 [srm-reactive-thread-61] WARN  com.vmware.dr.plugin.utils.ConnectionUtils 791215dd-7e59-4769-9129-51a2639061bb  - Problem occurred while checking connection to https://<hostname>:5480/configure
java.io.IOException: HTTPS hostname wrong:  should be <hostname>.<domain>

        at java.base/sun.net.www.protocol.https.HttpsClient.checkURLSpoofing(Unknown Source)
        at java.base/sun.net.www.protocol.https.HttpsClient.afterConnect(Unknown Source)
        at java.base/sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.connect(Unknown Source)
        at java.base/sun.net.www.protocol.https.HttpsURLConnectionImpl.connect(Unknown Source)
---
        at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
        at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
        at java.base/java.lang.Thread.run(Unknown Source)

* This scenario can also occur if a previously configured vSphere Replication appliance is unregistered, suddenly leaving the SRM appliance to serve the recovery UI client.
If the SRM certificate encounters the same CN hostname issue, the plugins will suddenly appear as 'undefined' in VC.

Environment

Site Recovery manager 8.x

vSphere Replication 8.x

vSphere Live Site Recovery 9.x

vSphere Replication 9.x

Cause

1. Site Recovery Manager or VRMS certificates shows incorrect Hostname and IP, causing DNS issue.

Note: The FQDN should be valid for example - ABC.XYZlocal is incorrect it should be ABC.XYZ.local

For example, validated the IP and Hostname it was different from the below certificate screenshot.

2.SRM or VRMS Recovery page is accessible using https://<SRMFQDN>/dr or https://<VRMSFQDN>/dr link.

Resolution

SRM or VRMS certificates had incorrect IP and FQDN values; recreating the certificates from the UI resolved the issue. The following steps were utilized to reach the solution.

Log in to the Site Recovery Manager Appliance Management Interface as admin (or the VRMS Appliance Management Interface).
Click Certificates and then click Change.

Select a certificate type.

Menu item	Description
Generate a self-signed certificate	Use an automatically generated certificate. Enter text values for your organization and organization unit, typically your company name, and the name of your group in the company. Accept the default FQDN and IP values. Note: Using a self-signed certificate is only recommended for non-production environments.
Use a PKCS #12 certificate file	Use a custom certificate. Click Browse, navigate to the certificate file, and click Open. The certificate file must contain exactly one certificate with exactly one private key matching the certificate. (Optional) Enter the optional private key encryption password.
Use a CA-signed certificate generated from CSR	Use a CA-signed certificate generated from a CSR. In the Certificate file row, click Browse, navigate to the certificate file, and click Open. (Optional) In the CA chain row, click Browse, navigate to the CA chain, and click Open.

Click Change.
Refresh The VAMI page. Re-login using admin credentials.
Reconfigure the appliance from Summary -> Reconfigure.

Additional Information

Below Document link can be referred for changing the certificate in SRM,

Change the Site Recovery Manager Appliance Certificate

Below Document link can be referred for changing the certificate in VRMS,

Change the VRMS Appliance Certificate