Skip to main content
NetApp Knowledge Base

SnapCenter verification fails when same NFS IP used in different SVMs

  1. Last updated
  2. Save as PDF
Views:
114
Visibility:
Public
Votes:
0
Category:
snapcenter
Specialty:
snapx
Last Updated:

Applies to

SnapCenter

Issue

SnapCenter complains about cloning a volume for verification from a different SVM, rather than SVM owning the original volume:
 

2023-11-02T01:10:11.7795198+01:00 Verbose SAL PID=[5308] TID=[10632] SVM: <SVM_IP> ---- Wrong SVM
2023-11-02T01:10:11.7795198+01:00 Verbose SAL PID=[5308] TID=[10632] ++StorageSystemManager::GetStorageSystemIdFromCache
2023-11-02T01:10:11.7795198+01:00 Verbose SAL PID=[5308] TID=[10632] SVM: <SVM_IP> ---- Wrong SVM
2023-11-02T01:10:11.7795198+01:00 Verbose SAL PID=[5308] TID=[10632] The storage is not in the storage systemId cache: Available cached

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.