vSphere Replication - Ul error: Unknown error
search cancel

vSphere Replication - Ul error: Unknown error

book

Article ID: 428986

calendar_today

Updated On:

Products

VMware vSphere ESXi

Issue/Introduction

While accessing the vSphere replication on the site pairing page below error is displayed. 

Environment

vSphere Replication 9.x

Cause

The issue is caused by connectivity failure  between the two vSphere Replication appliance over the port 443.

The port 443 might be blocked by the firewall.

The below logs on the vSphere replication appliance shows the timeout error

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

java.lang.Exception: Unable to get DRaaS check flag at URL: https://destination VR IP/draas/isvmc.
        at com.vmware.dr.plugin.handlers.dashboard.DraasCheckHandler$RequestCallback.fail(DraasCheckHandler.java:113)
        at com.vmware.dr.plugin.handlers.dashboard.DraasCheckHandler$RequestCallback.failed(DraasCheckHandler.java:98)
        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 [/destination VR IP:443]

This can be verified by running the below command on either vSphere Replication

root@sourcevr# openssl s_client -connect destination VR IP:443
C0112267E37F0000:error:8000006E:system library:BIO_connect:Connection timed out:crypto/bio/bio_sock2.c:114:calling connect()
C0112267E37F0000:error:10000067:BIO routines:BIO_connect:connect error:crypto/bio/bio_sock2.c:116:
connect:errno=110

Resolution

The fix is to validate if the port 443 is block or there is a  connectivity issue between the Source and the  Destination vSphere Replication Appliance.

It can be validated with the internal network or firewall team.