Virtual Volumes - RFC File was not found
Article ID: 378777
Updated On:
Products
Issue/Introduction
1. You can see the files within the vVol datastore but cannot browse it.
Operation failed!
Task name Search datastore
Target Test-vVol
Status File [Test-vVol] rfc41XX.d1XXXe16-cXX6-4XXa-8XX7-76XX3cb7eXf1 was not found
2. You cannot create new files in the vVol datastore.
Operation failed!
Cannot complete file creation operation.
Operation failed, diagnostics report: Test (Cannot Create File)
Hide errors for this session.
SEND DETAILS TO VMWARE
3. Protocol Endpoints may be missing
4. The host may be configured with both iSCSI and FC protocols
vvold.log:
2024-07-25T15:32:32.754Z info vvold[3617863] [Originator@6876 sub=Default opID=esxcli-host] HostManager::DiscoverSCSIPEs peVec.size=2, _peMap.size=4, setPEContextScheduled=false
2024-07-25T15:32:32.755Z info vvold[3617863] [Originator@6876 sub=Default opID=esxcli-host] HostManager::DiscoverNFS3PEs peVec.size=2, _peMap.size=4, setPEContextScheduled=false
2024-07-25T15:32:32.755Z info vvold[3617863] [Originator@6876 sub=Default opID=esxcli-host] HostManager::DiscoverNFS4xPEs peVec.size=2, _peMap.size=4, setPEContextScheduled=false
2024-07-25T15:32:32.755Z info vvold[3617863] [Originator@6876 sub=Default opID=esxcli-host] HostManager::RefreshPEMap needSetPEContext=false
2024-07-25T15:32:32.770Z info vvold[3617863] [Originator@6876 sub=Default opID=esxcli-host] HostManager::RefreshScsiNamesAndPorts: Adding FC HBA 'vmhba1' (fc.20000000018:2000000018, wwn:20:00:00:20:00:X port:20:00:00:00:X) claimed by 'nfnic'.
2024-07-25T15:32:32.770Z info vvold[3617863] [Originator@6876 sub=Default opID=esxcli-host] HostManager::RefreshScsiNamesAndPorts: Adding FC HBA 'vmhba2' (fc.20000000018:2000000018, wwn:20:00:00:20:00:X port:20:00:00:00:X) claimed by 'nfnic'.
2024-07-25T15:32:32.772Z info vvold[3617863] [Originator@6876 sub=Default opID=esxcli-host] RefreshScsiNamesAndPorts: Adding iSCSI HBA 'vmhba64' [iqn:iqn.1999-01.com.vmware:host-VMware-esx01-5ca0e007] claimed by 'iscsi_vmk'.
2024-07-25T15:32:40.040Z warning vvold[3617862] [Originator@6876 sub=Default] ProtocolEndpoint::GetPEInfo PE info (
2024-07-25T15:32:40.040Z warning vvold[3617862] [Originator@6876 sub=Default] ProtocolEndpoint::GetPEInfo PE info (
2024-07-25T15:32:44.914Z info vvold[3617863] [Originator@6876 sub=Default] SI:QueryUuidForFriendlyName uuid:rfc41XX.d1XXXe16-cXX6-4XXa-8XX7-76XX3cb7eXf1 name:.vSphere-HA containerId:cXXX0d57-4XX8-cXX6-eXX5-060XXXXbced cached:true
2024-07-25T15:32:44.915Z info vvold[3617863] [Originator@6876 sub=Default] Came to SI::BindVirtualVolume: esxContainerId cXXX0d57-4XX8-cXX6-eXX5-060XXXXbced VVol Id rfc41XX.d1XXXe16-cXX6-4XXa-8XX7-76XX3cb7eXf1 bindType Normal (isConfigVvol: true)
2024-07-25T15:32:44.915Z info vvold[3617863] [Originator@6876 sub=Default] VasaOp::BindVirtualVolume [#24]: ===> Issuing 'bindVirtualVolume' to VP [host.vmware.com-ct0:Connected (Outstanding 0/5)]
2024-07-25T15:32:44.937Z error vvold[3617863] [Originator@6876 sub=Default] VasaOp::IsSuccessful [#24]: bindVirtualVolume transient failure: 22 (STORAGE_FAULT / No Protocol Endpoint is registered / )
2024-07-25T15:32:44.937Z warning vvold[3617863] [Originator@6876 sub=Default] VasaOp[#24] ===> Transient failure bindVirtualVolume VP (host.vmware.com-ct0) retry=false, batchOp=false container=cXXX0d57-4XX8-cXX6-eXX5-060XXXXbced timeElapsed=22 msecs (#outstanding 0)
2024-07-25T15:32:44.937Z error vvold[3617863] [Originator@6876 sub=Default] VasaOp[#24] ===> FINAL FAILURE bindVirtualVolume, error (STORAGE_FAULT / No Protocol Endpoint is registered / ) VP (host.vmware.com-ct0) Container (cXXX0d57-4XX8-cXX6-eXX5-060XXXXbced) timeElapsed=22 msecs (#outstanding 0)
2024-07-25T15:33:00.040Z warning vvold[3617870] [Originator@6876 sub=Default] ProtocolEndpoint::GetPEInfo PE info
2024-07-25T15:33:00.041Z warning vvold[3617870] [Originator@6876 sub=Default] ProtocolEndpoint::GetPEInfo PE info
Environment
VMware ESXi 7.0
VMware ESXi 8.0
Cause
VMware support has seen this issue to occur when the storage is configured for both iSCSI and FC.
Resolution
NOTE: The array generates the RFC-ID and ESXi validates its format.
If you are seeing (STORAGE_FAULT / No Protocol Endpoint is registered) errors in the ESXi logs, please log a case with your storage vendor first as it turns out this is pre-dominantly a storage problem but VMware support would be there to assist you in answering any questions that the Storage vendor may have that falls under VMware's scope of support.
Feedback
