[VpxLRO] -- ERROR vpxa -- vpxapi.VpxaService.searchDatastore: :vim.fault.FileNotFoundVpxa[2099709] --> Result:Vpxa[2099709] --> (vim.fault.FileNotFound) { --> faultCause = (vmodl.MethodFault) null, --> faultMessage = <unset>, --> file = "ds:///vmfs/volumes/vvol:####/naa.####"--> msg = ""--> }--> Args:-->--> Arg url:--> "ds:///vmfs/volumes/vvol:####/naa.####"--> Arg recursive:VVold[####] [Originator@6876 sub=Default IpcCtx=####] SI::QueryVirtualVolumeInt Empty responseVVold[####] [Originator@6876 sub=IpcSvc IpcCtx=####] HandleRequest: Error handling function QueryUuidForFriendlyName: Empty responseVMware ESXi 8.0.3 build-24585383
HPE VVOL
The above 'empty response' message indicates the expected data path is no longer present from Virtual Center's perspective.
This is due to a communication problem following the HPE SAN OS upgrade, as the VASA API is no longer on appropriate version matching the array side VASA. This version mismatch leads to the communication issue.
To resolve the VASA API version mismatch in the Virtual Center, please follow the steps below:
Please Note: If the VASA certificate is expired, ensure the certificate is refreshed/renewed after re-adding the storage provider.