vSphere Replication appliance VAMI fails to load with Unexpected status code 503

Products

• VMware Live Recovery

Issue/Introduction

Symptoms:

• vSphere Replication appliance VAMI fails to load after upgrading from VR 8.7, 21591677 > 9.0.2, 24171210
• The summary page shows "Unexpected status code: 503"

 

From VRMS, /var/log/vmware/drconfigui/dr-config.log

2024-09-30 14:38:02,978 [srm-reactive-thread-252] WARN  com.vmware.dr.configservice.summary.GetConnectedToCloudData 65635f66-b092-408f-b80d-bf34f8b9fa21 getConnectedToCloudData - Failed to get active agent:

com.vmware.vim.vmomi.client.common.UnexpectedStatusCodeException: Unexpected status code: 503
        at com.vmware.vim.vmomi.client.common.Response$Status.getStatus(Response.java:61)
        at com.vmware.vim.vmomi.client.http.impl.HttpExchangeBase.parseResponse(HttpExchangeBase.java:267)
        at com.vmware.vim.vmomi.client.http.impl.HttpAsyncExchange$1$2.invokeWithinScope(HttpAsyncExchange.java:166)
        at com.vmware.vim.vmomi.core.tracing.NoopTracer$NoopSpan.runWithinSpanContext(NoopTracer.java:120)
        at com.vmware.vim.vmomi.client.http.impl.TracingScopedRunnable.run(TracingScopedRunnable.java:17)
        at com.vmware.dr.ui.tools.utilities.ThreadContext.lambda$wrap$1(ThreadContext.java:55)
        at com.vmware.dr.ui.tools.utilities.ThreadContext.execute(ThreadContext.java:209)
        at com.vmware.dr.ui.tools.utilities.ThreadContext.execute(ThreadContext.java:185)
        at com.vmware.dr.ui.tools.utilities.ThreadContext.setupContext(ThreadContext.java:76)
        at com.vmware.dr.ui.tools.utilities.ThreadContext.setupContext(ThreadContext.java:105)
        at com.vmware.dr.ui.tools.utilities.ExecutorUtils.lambda$wrap$1(ExecutorUtils.java:36)
        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)

Environment

VMware vSphere Replication 8.x
VMware vSphere Replication 9.x

Cause

Incorrect IP/FQDN of the vCenter Server Appliance (VCSA) in  the /opt/vmware/hms/conf/hms-configuration.xml file of the appliance can cause such errors.

 

Resolution

1. Verify the hms-ls-url and hms-localvc-address in /opt/vmware/hms/conf/hms-configuration.xml.

     root@VRMDR [ /opt/vmware/hms/conf ]# less hms-configuration.xml | grep -i hms-ls-url
   <hms-ls-url>https://192.#.#.#:443/lookupservice/sdk</hms-ls-url>
   root@VRMDR [ /opt/vmware/hms/conf ]# less hms-configuration.xml | grep -i hms-localvc-address
   <hms-localvc-address>192.#.#.#</hms-localvc-address>

2. If the IP/FQDN address is updated incorrectly, modify the HMS configuration to use the correct vCenter FQDN/VC IP address.

3. Restart dr-configurator service:

   # systemctl restart dr-configurator

4. Login to VRMS page and then reconfigure the appliance - To Reconfigure the VRMS appliance

Additional Information

Finding SHA-1 and SHA-256 thumbprints for ESXi, vCenter, vSphere Replication and Site Recovery Manager appliances