HCX Bulk/RAV migration failed with error, "Storage not accessible error observed".
search cancel

HCX Bulk/RAV migration failed with error, "Storage not accessible error observed".

book

Article ID: 403908

calendar_today

Updated On:

Products

VMware HCX

Issue/Introduction

  • HCX Bulk/RAV Migrations are not progressing beyond 0% with the state Base Sync Initiated. 


  • Below log snippet is observed from HCX Manager log file (/common/logs/admin/app.log)
    2025-07-04 06:56:01.549 UTC [ReplicationTransferService_SvcThread-1847, Ent: HybridityAdmin, , TxId: <Transaction ID of the migration>] WARN  c.v.h.s.r.j.ReplicationTransferMonitor- Current bytes transferred value 0 is not greater than the already transferred bytes value 0, hencenot updating for transfer <Migration ID>
  • Following log snippet is observed under IX cloud side's HBR logs (login to HCX manager CLI with admin user and then type following: ccli -> go <appliance-ID of IX appliance> -> cd /var/log/vmware -> less hbrsrv.log
    2025-07-01 06:47:41.955 UTC [InterconnectService_SvcThread-46395, Ent: HybridityAdmin, , TxId: <transaction ID of the migration] ERROR c.v.v.h.s.i.ThumbprintExchanger- ThumbprintExchanger Job: (<Job ID>) encountered error
    java.lang.RuntimeException: ["Error connecting to HBR server <IP-Address of the HBR server>:8123. Reason: NoRouteToHostException"]
            at com.vmware.vchs.hybridity.service.interconnect.ThumbprintExchanger.doExchangeThumbprint(ThumbprintExchanger.java:319)
            at com.vmware.vchs.hybridity.service.interconnect.ThumbprintExchanger.run(ThumbprintExchanger.java:87)
            at com.vmware.vchs.hybridity.messaging.LoggingJobWrapper.run(LoggingJobWrapper.java:41)
            at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
            at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
  • Data-Plane Diagnostics confirmed the required ports for replication were whitelisted and looks good.

Environment

VMware HCX

Cause

vSphere vmkernel adapter used for replication network was configured on separate VDS (Virtual Distributed Switch) connected to uplinks which did not have the required L2 or L3 configuration to traverse the data to the other endpoints in replication network.

Resolution

Migrate the IX replication network vmkernel to a valid VDS(Virtual Distributed Switch), where the other endpoints like ESXi host are reachable over replication network. Reference article on how to migrate vmkernel adapter to a distributed switch.