Skip to main content
NetApp Knowledge Base

Modify Storage Connection fails by error "Failed to find storage system"

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

Applies to

  • SnapCenter Server 4.1P2
  • Storage system was registered as IP address and it was unable to be resolved to storage virtual machine (SVM) name at that time
  • The IP address can be resolved to SVM name as of now

Issue

  • Modify Storage Connection fails by error "Failed to find storage system".
 
17cf98c0-eee9-44e4-99d4-3db38f1fe427.jpg

  • Error message "Failed to find storage system" is detected in SnapManagerWeb.log.

ERROR SnapManagerWeb PID=[3544] TID=[51] ErrorCode (102), ErrorMessage (Failed to find storage system)
INFO  SnapManagerWeb PID=[3544] TID=[51] Setting storage connection is completed on host(s)

  • No connection error is detected in SnapDriveSALDebug.log.

  • Executing Connect-NcController from PowerShell in SnapCenter Server returns correct SVM information by specifying the same credentials as specified in Modify Storage Connection page.

Example:
> Import-Module "C:\Program Files\NetApp\SMCore\SAL\PSToolkit\DataONTAP.C.dll"
> Connect-NcController -Port 443 ＜SVM_MGMT_IP＞

 

 

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.