VM is inaccessible during vmotion, it stuck on 20% and then stop responding to ping.
search cancel

VM is inaccessible during vmotion, it stuck on 20% and then stop responding to ping.

book

Article ID: 395115

calendar_today

Updated On:

Products

VMware vCenter Server

Issue/Introduction

VMs operating on VVOLs could not be migrated between hosts. The migration tasks consistently stall at 20%, causing the VMs to lose network connectivity and fail to respond to pings

Environment

vSphere ESXi 7.x
vSphere ESXi 8.x 

VMware vVOL

Cause

Multiple storage containers and PEs are reported as 'Not Accessible,' accompanied by APD events for the VVOL datastores. 

Validation Steps:  

  • The vVOl storage containers showing Accessible false

# esxcli storage vvol storagecontainer list 

    StorageContainer Name     UUID                                    Array                           Size      Free      Accessible  Default Policy
    ---------------------     ----                                    -----                           ----      ----      ----------  --------------
    Example-vVols             vvol:0000000200004003-8##############5  NimbleStorage:3##############5  83886080  61007115  false       not_in_txt_file
    Example-vVols             vvol:0000000200004001-8##############8  NimbleStorage:1##############8  83886080  62600684  false       not_in_txt_file

  • The Protocol End point shows Accessible False 

# esxcli storage vvol protocolendpoint list 

    Lun Id                                Array Id                        Type  Accessible  Configured  Storage Containers
    -------                               --------                        ----  ----------  ----------  ------------------
    eui.0a#############################8  NimbleStorage:1##############8  SCSI  false       false       00000002-0000-4001-8c55-d###########8
    eui.1a#############################6  NimbleStorage:3##############5  SCSI  false       false       00000002-0000-4003-82db-8###########5

  • Where as the vasa provider shows in sync and active 

# esxcli storage vvol vasaprovider list

Example-nimble01:
   VP Name: Example-nimble01
   URL: https://##.##.#.#05:8443/vasa/version.xml
   Status: online
   Arrays:
         Arrays:
            ArrayId: NimbleStorage:3##############5
            Is Active: true
            Priority: 0

  • Logs shows PE showing inaccessible: 

2025-04-02T14:22:55.633Z warning vvold[624387958] [Originator@6876 sub=Default] HostManager::GetContainerPEAccessibility arrayId: NimbleStorage:40c4d430e6b10b22, cid: 00000001-0000-4004-80c4-d430e6b10b22, accessible: 0,checkAllPEsAccessibility: false containerType: SCSI, APD: 0

  • This indicates that the host is able to communicate with the VASA provider but unable to access the Protocol End point and Storage container. Indicates an issue with the communication from VSA provider to Storage. 

Resolution

Assistance from the storage vendor is required to investigate the issue and determine whether these events can be resolved. The problem lies outside the ESXi host.