SnapCenter fails to resolve LUNs that show up as VMware NVMe disks
Applies to
- SnapCenter Plug-in for Windows (SCW)
- SnapCenter Plug-in for VMware vSphere (SCV)
- NVME
- RDM/VMDK disks
Issue
- RDM/VMDK disks attached to the Windows VM on an NVMe controller do not get recognized as being on NetApp storage.
- The most telling errors showing up are found in SCWDebug.log on the Windows host:
Verbose SDW PID=[<PID>] TID=[<TID>] Failed to get vmfs datastore name for disk 'VMWare NVME_0000'.
Verbose SDW PID=[<PID>] TID=[<TID>] Get VMFS Datastore failed for disk 'VMWare NVME_0000' - exception. reason = Failed to get vmfs datastore name for disk 'VMWare NVME_0000'.- Further error messages in the SCW_JOB-ID.log will show the following:
Error SDW PID=[<PID>] TID=[<TID>] Error: Failed to get shared disks
Error SDW PID=[<PID>] TID=[<TID>] Failed to get resource object graphs using SMAPI. Error code: 0. Details: Failed to enumerate the disks.
Error SDW PID=[<PID>] TID=[<TID>] Errror: The resource graph is null/empty- Any SQL or Exchange databases on the host will not show up under the resources under these conditions.
