NFS vVol datastore is inaccessible - Host cannot see Protocol Endpoint mounts

Products

• VMware vSphere ESXi
• VMware vCenter Server

Issue/Introduction

A power outage causes the hosts to lose access to their NFS PEs 

vVol datastores become inaccessible 

Environment

VMware ESXi 
VMware vCenter Server 

Cause

The logs show that the PEs are associated with the new array and not the old one, therefore it can't connect to the vVols that the old VASA provider was exposing.  

vvold.log:

2025-04-30T07:26:23.502Z In(166) VVold[2402912]: [Originator@6876 sub=Default OpId=Session] ProtocolEndpoint::InitializeFromVasaPE Initing NFS PE (9bfdddddcc0f4ed3b82c0000009898db) with peMapKey (NFSv3PE_172.#.#.#__)
2025-04-30T07:26:23.502Z In(166) VVold[2402912]: [Originator@6876 sub=Default OpId=Session] HostManager::AddPEs@779  PE updated in map:
2025-04-30T07:26:23.502Z In(166) VVold[2402884]: --> NFS PE, ID (host: 65ccf3db-b28eaea6, vasa: 9bfdddddcc0f4ed3b82c0000009898db) (accessible, configured)
2025-04-30T07:26:23.502Z In(166) VVold[2402884]: --> ArrayIds:NetApp.clustered.Data.ONTAP.VP:a9566#######4e57a01e######9898a8
2025-04-30T07:26:23.502Z In(166) VVold[2402884]: -->  IP Address: 172.#.#.#, Server Mount: /
2025-04-30T07:26:23.502Z In(166) VVold[2402912]: [Originator@6876 sub=Default OpId=Session] ProtocolEndpoint::InitializeFromVasaPE Initing NFS PE (9bf#####cc0f4ed3b82c######9898d8) with peMapKey (NFSv3PE_172.#.#.#__)
2025-04-30T07:26:23.502Z In(166) VVold[2402912]: [Originator@6876 sub=Default OpId=Session] HostManager::AddPEs@779  PE updated in map:
2025-04-30T07:26:23.502Z In(166) VVold[2402884]: --> NFS PE, ID (host: df44b9ae-0659b537, vasa: 9bf#####cc0f4ed3b82c######9898d8) (accessible, configured)
2025-04-30T07:26:23.502Z In(166) VVold[2402884]: --> ArrayIds:NetApp.clustered.Data.ONTAP.VP:a9566#######4e57a01e######9898a8

2025-04-30T16:58:06.622Z Wa(164) VVold[2334400]: [Originator@6876 sub=Default IpcCtx=2099540-38 OpId=HB-host-5016@2907-447e9abe-30dc109c-47-6163] StorageContainer::GetCurrentVpRef Storage container is not initialized.
2025-04-30T16:58:06.623Z In(166) VVold[2334426]: [Originator@6876 sub=Default IpcCtx=2099540-42 OpId=HB-host-5016@2907-447e9abe-30dc109c-47-6163] SI:ListVasaProvider@2513
2025-04-30T16:58:06.623Z In(166) VVold[2334404]: [Originator@6876 sub=Libs OpId=HB-host-5016@2907-447e9abe-30dc109c-47-6163] SlowRefresh: path /vmfs/volumes/df44b9ae-0659b537 total blocks 1020055552 used blocks 2367488forceRefresh = 0
2025-04-30T16:58:06.623Z In(166) VVold[2334404]: [Originator@6876 sub=Libs OpId=HB-host-5016@2907-447e9abe-30dc109c-47-6163] Refresh: Done. Volume NFSv3PE_172.16.12.20__ accessible 1 vaaiSupport 1
2025-04-30T16:58:06.624Z Wa(164) VVold[2334426]: [Originator@6876 sub=Default IpcCtx=2099540-38 OpId=HB-host-5016@2907-447e9abe-30dc109c-47-6163] StorageContainer::GetCurrentVpRef Storage container is not initialized.

Resolution

When deploying a new NetApp ONTAP tools (Appliance), ensure a successful migration of the database from the old appliance to the new one; otherwise, issues outlined in this article may occur.

Contact the NetApp Storage vendor for further assistance.