Skip to main content
NetApp Knowledge Base

Missing LUNs, VMDK disks or RDM disks in SnapCenter due to name resolution issue

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

Applies to

  • SnapCenter 
  • SnapCenter plug-in for Windows (SCW)
  • SnapCenter plug-in for VMware vSphere (SCV)

Issue

  • LUNs, VMDK disks or RDM disks are not listed in the Hosts -> Disks page

1071156_1.png

  • Refresh Disks in the Hosts -> Disks doesn't discover LUNs, VMDK disks or RDM disks.
  • SnapDriveSALDebug.log on the SCW host shows warnings with SVM name resolution:

2019-02-26T19:12:53.4192832+08:00 Warning SAL PID=[17756] TID=[21544] No such host is known at System.Net.Dns.InternalGetHostByName(String hostName, Boolean includeIPv6)
at System.Net.Dns.GetHostByName(String hostName)
at SnapDrive.Nsf.Common.Infrastructure.NetworkResourceIdCache.ResolveWithDns(String hostName)

2019-02-26T19:12:53.4192832+08:00 Verbose SAL PID=[17756] TID=[21544] --NetworkResourceIdCache::ResolveWithDns
2019-02-26T19:12:53.4192832+08:00 Warning SAL PID=[17756] TID=[21544] Error resolving hostname: Failed to resolve <SVM_NAME> by HostByName, at: at SnapDrive.Nsf.Common.Infrastructure.NetworkResourceIdCache.ResolveWithDns(String hostName)
at SnapDrive.Nsf.Common.Infrastructure.NetworkResourceIdCache.Resolve(String hostName)

  • SMCore.log on the SnapCenter Server (in case of VMDK enumeration) shows a name resolution issue with the data network interface:

2024-07-31T11:01:44.8745889-05:00 DEBUG SMCore_XXXXXXX PID=[XXXX] TID=[XXX] hostResource is type of SDnfsShare.
2024-07-31T11:01:44.8745889-05:00 DEBUG SMCore_XXXXXXX PID=[XXXX] TID=[XXX] ++NetworkResourceIdCache::Resolve
2024-07-31T11:01:44.8755946-05:00 DEBUG SMCore_XXXXXXX PID=[XXXX] TID=[XXX] ++NetworkResourceIdCache::ResolveWithDns
2024-07-31T11:01:44.8755946-05:00 DEBUG SMCore_XXXXXXX PID=[XXXX] TID=[XXX] Resolving Network Resource : <NFS_DATA_LIF_NAME>
2024-07-31T11:01:44.8765884-05:00 WARN  SMCore_XXXXXXX PID=[XXXX] TID=[XXX]
Message    : No such host is known
Source     : System
StackTrace :    at System.Net.Dns.GetAddrInfo(String name)
   at System.Net.Dns.InternalGetHostByName(String hostName, Boolean includeIPv6)
   at System.Net.Dns.GetHostEntry(String hostNameOrAddress)
   at SnapDrive.Nsf.Common.Infrastructure.NetworkResourceIdCache.ResolveWithDns(String hostName)

2024-07-31T11:01:44.8765884-05:00 DEBUG SMCore_XXXXXXX PID=[XXXX] TID=[XXX] --NetworkResourceIdCache::ResolveWithDns
2024-07-31T11:01:44.8765884-05:00 WARN  SMCore_XXXXXXX PID=[XXXX] TID=[XXX] Error resolving hostname: Failed to resolve <NFS_DATA_LIF_NAME> by HostByName, at:    at SnapDrive.Nsf.Common.Infrastructure.NetworkResourceIdCache.ResolveWithDns(String hostName)
   at SnapDrive.Nsf.Common.Infrastructure.NetworkResourceIdCache.Resolve(String hostName)

2024-07-31T11:01:44.8775894-05:00 DEBUG SMCore_XXXXXXX PID=[XXXX] TID=[XXX] --NFStoStrorageConverter::Convert
2024-07-31T11:01:44.8775894-05:00 DEBUG SMCore_XXXXXXX PID=[XXXX] TID=[XXX] --HostToStorageConverter::GetStorageFootprint
2024-07-31T11:01:44.8775894-05:00 DEBUG SMCore_XXXXXXX PID=[XXXX] TID=[XXX] SDGetStorageResponse : SDGetStorageResponse :
 Result : SDGetStorageResult : HostResource : /<DATASTORE_FOLDER_NAME>
No storage footprint available. Error : Failed to get the storage system for host resource : Name : /<DATASTORE_FOLDER_NAME>, Type: SDNASDir, Code : 104

 

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.