Skip to main content
NetApp Knowledge Base

SnapCenter fails to resolve LUNs that show up as VMware NVMe disks

Views:
203
Visibility:
Public
Votes:
0
Category:
snapcenter
Specialty:
snapx
Last Updated:

Applies to

SnapCenter Plug-in for Windows (SCW)

Issue

RDM 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.

Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.