Site Recovery plugin UI shows vSphere Replication Servers "Not accessible". VM Replications are not affected.

Products

VMware Live Recovery

Issue/Introduction

Symptoms:

Logging into the Site Recovery Plugin shows the vSphere Replication server status as "Not accessible"

Environment

vSphere Replication 8.x
vSphere Replication 9.x
VMware Live Site Recovery 9.x

Cause

The issue is caused by a communication failure between SRM appliances over TCP port 5480. In an ELM environment, the SRM UI plugin requires bidirectional connectivity on port 5480 across all SRM appliances ( Also vSphere Replication Appliances if in use) of the linked group to aggregate site information.

Resolution

Validate connectivity between VLSR/SRM appliance and vSphere Replication appliance on port 5480.

Using nc command:

-- SSH to VLSR/SRM appliance:
# nc -z [vSphere Replication Appliance] 5480
Using curl command can also be used to validate the endpoint destination.

-- SSH to VLSR/SRM appliance:

curl -k -v https://FQDN-of-vSphere-Replication-appliance:5480/configureserver/health/hms?ui=1

If there is no connection then the firewall will need to be open to allow the communication across that port.

Additional Information

SRM drplugin.log shows similar entries

2025-10-07 17:03:01,136 [srm-reactive-thread-2330] WARN com.vmware.dr.plugin.handlers.dashboard.VrHealthStatusHandler #-#-#-#-# - DrRequestHandlerError:
java.lang.Exception: Unable to get VR health status at URL: https://FQDN-of-vsphere-replication-appliance:5480/configureserver/health/hms?ui=1.
at com.vmware.dr.plugin.handlers.dashboard.VrHealthStatusHandler$RequestCallback.fail(VrHealthStatusHandler.java:180)
at com.vmware.dr.plugin.handlers.dashboard.VrHealthStatusHandler$RequestCallback.failed(VrHealthStatusHandler.java:158)
at org.apache.http.concurrent.BasicFuture.failed(BasicFuture.java:137)
at org.apache.http.impl.nio.client.DefaultClientExchangeHandlerImpl.executionFailed(DefaultClientExchangeHandlerImpl.java:101)
at org.apache.http.impl.nio.client.AbstractClientExchangeHandler.failed(AbstractClientExchangeHandler.java:432)
at org.apache.http.impl.nio.client.AbstractClientExchangeHandler.connectionRequestFailed(AbstractClientExchangeHandler.java:352)
at org.apache.http.impl.nio.client.AbstractClientExchangeHandler.access$100(AbstractClientExchangeHandler.java:64)
at org.apache.http.impl.nio.client.AbstractClientExchangeHandler$1.failed(AbstractClientExchangeHandler.java:396)
at org.apache.http.concurrent.BasicFuture.failed(BasicFuture.java:137)
at org.apache.http.impl.nio.conn.PoolingNHttpClientConnectionManager$1.failed(PoolingNHttpClientConnectionManager.java:318)
at org.apache.http.concurrent.BasicFuture.failed(BasicFuture.java:137)
at org.apache.http.nio.pool.RouteSpecificPool.timeout(RouteSpecificPool.java:169)
at org.apache.http.nio.pool.AbstractNIOConnPool.requestTimeout(AbstractNIOConnPool.java:632)
at org.apache.http.nio.pool.AbstractNIOConnPool$InternalSessionRequestCallback.timeout(AbstractNIOConnPool.java:898)
at org.apache.http.impl.nio.reactor.SessionRequestImpl.timeout(SessionRequestImpl.java:198)
at org.apache.http.impl.nio.reactor.DefaultConnectingIOReactor.processTimeouts(DefaultConnectingIOReactor.java:213)
at org.apache.http.impl.nio.reactor.DefaultConnectingIOReactor.processEvents(DefaultConnectingIOReactor.java:158)
at org.apache.http.impl.nio.reactor.AbstractMultiworkerIOReactor.execute(AbstractMultiworkerIOReactor.java:351)
at org.apache.http.impl.nio.conn.PoolingNHttpClientConnectionManager.execute(PoolingNHttpClientConnectionManager.java:221)
at org.apache.http.impl.nio.client.CloseableHttpAsyncClientBase$1.run(CloseableHttpAsyncClientBase.java:64)
at java.base/java.lang.Thread.run(Unknown Source)
Caused by: java.net.ConnectException: Timeout connecting to [FQDN-of-vsphere-replication-appliance/#.#.#.#:5480]
... 10 more

For the same kind of problem with linked mode vCenters see https://knowledge.broadcom.com/external/article/400280/site-recovery-plugin-ui-shows-vsphere-re.html