vSphere Replication Status Shows as Inaccessible in Site Recovery UI with Error: 'The vSphere Replication Management Server is Not Accessible. Check the Site Recovery Integration Plug-in for Possible Causes'"

Products

• VMware Live Recovery

Issue/Introduction

Symptoms:

• An error is displayed on the Site Recovery UI, indicating that the site is inaccessible.

• The vCenters are operating in Enhanced Linked Mode.
• The Site Recovery plugin in vCenter shows as deployed.
• Replication is functioning correctly, with no issues reported in the replication process.
• The reconfiguration of the vSphere Replication appliance completes successfully without any errors, but the Site Recovery UI still reports the site as inaccessible.

Validate vSphere Replication Appliance Logs to identify any errors related to connectivity. You can find the relevant logs in the following location:

Log file path: /opt/vmware/support/logs/dr-client-plugin/drplugin.log

2025-01-09 07:25:33,316 [srm-reactive-thread-20] WARN com.vmware.dr.plugin.utils.ConnectionUtils - Problem occurred while checking connection to https://#######srm01.############.#######:5480/configurejava.net.SocketTimeoutException: Connect timed out
2025-01-09 07:25:33,316 [srm-reactive-thread-20] WARN  com.vmware.dr.plugin.utils.ConnectionUtils 7e8b7d42-cfbc-456c-a98a-f61e4642f124 - Problem occurred while checking connection to https://#########srm01.#####.#####:5480/configurejava.net.SocketTimeoutException: Connect timed out
java.base/sun.nio.ch.NioSocketImpl.timedFinishConnect(Unknown Source)      
 at java.base/sun.nio.ch.NioSocketImpl.connect(Unknown Source)      
 at java.base/java.net.SocksSocketImpl.connect(Unknown Source)        
at java.base/java.net.Socket.connect(Unknown Source)        
at java.base/sun.security.ssl.SSLSocketImpl.connect(Unknown Source)        
at java.base/sun.net.NetworkClient.doConnect(Unknown Source)        
at java.base/sun.net.www.http.HttpClient.openServer(Unknown Source)        
at java.base/sun.net.www.http.HttpClient.openServer(Unknown Source)        
at java.base/sun.net.www.protocol.https.HttpsClient.<init>(Unknown Source)        
at java.base/sun.net.www.protocol.https.HttpsClient.New(Unknown Source)        
at java.base/sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.getNewHttpClient(Unknown Source)        
at java.base/sun.net.www.protocol.http.HttpURLConnection.plainConnect0(Unknown Source)        
at java.base/sun.net.www.protocol.http.HttpURLConnection.plainConnect(Unknown Source)

This indicates a timeout error when attempting to connect to port 5480 (It might show for SRM or vSphere replication appliances)

Environment

Site Recovery 8.x 
Site Recovery 9.x
vCenter 8.x 
vSphere replication 8.x
vSphere replication 9.x

Cause

The issue is primarily related to connectivity problems between Site Recovery Manager (SRM) and the vSphere Replication Management (VRM) servers. Specifically, the problem arises when attempting to establish a connection to port 5480, which is essential for managing vSphere Replication.
Possible causes include:

• Network Connectivity Issues:

Network timeouts or firewall rules might be blocking communication between the Site Recovery Manager and the vSphere Replication appliances, causing the connection to fail.

• Plugin Integration Issues:

The Site Recovery Integration Plugin may not be communicating correctly with the vSphere Replication Management Server, leading to issues with the Site Recovery UI showing the site as inaccessible.

• Configuration or Version Mismatch:

Mismatched versions of vSphere Replication, Site Recovery Manager, or vCenter can cause discrepancies in the integration, leading to inconsistencies in the Site Recovery UI and connectivity failures.

Resolution

Validate Connectivity to the vSphere Replication Appliance

Ensure that there is proper connectivity between the SRM and the vSphere Replication appliance. Run the following command from the vSphere Replication and SRM appliance to test the connectivity.

admin@vr01 [ ~ ]$ curl -v telnet://vr02:5480
  Trying vr02:5480...
Connected to vr02 (vr02) port 5480 (#0)

admin@vr01 [ ~ ]$ curl -v telnet://vr03:5480
  Trying vr03:5480...
connect to vr03 port 5480 failed: No route to host
Failed to connect to vr03 port 5480 after 3097 ms: Couldn't connect to server
Closing connection 0
curl: (7) Failed to connect to vr03 port 5480 after 3097 ms: Couldn't connect to server

admin@vr01 [ ~ ]$ curl -v telnet://srm03:5480
  Trying srm03:5480...
connect to srm03 port 5480 failed: No route to host
Failed to connect to srm03 port 5480 after 3097 ms: Couldn't connect to server
Closing connection 0
curl: (7) Failed to connect to srm03 port 5480 after 3097 ms: Couldn't connect to server

Port 5480 is crucial for communication between the Site Recovery Manager and the vSphere Replication appliance. Verify that the required ports are open and that there are no firewall rules blocking communication.

For details on the required ports and services used by vSphere Replication, refer to the following VMware documentation:

Services, Ports, and External Interfaces That the vSphere Replication Virtual Appliance Uses