Skip to main content
NetApp Knowledge Base

Adding or editing an SVM in SC fails with "API invoke failed"

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

Applies to

  • SnapCenter Server (SC)
  • SnapCenter Plug-in for VMware vSphere (SCV)
  • Adding or editing an SVM

Issue

Adding or editing an SVM in SC or SCV fails with error: 

Netapp Error. Failed to connect to storage system <FQDN> API Invoke failed

Whenever a SSL connection cannot be established between SCV and SVM's hosting datastores/VM's inside an existing SCV Resource Group (RG), SCV may also fail to backup those RG's and Trying to edit the Resource Group will fail too with the following error, depending on whether or not the credential cache in SCV expired or not:

Following entities could not be added to resource group:nfs2
These are possible reasons for this error:
1) All the Datastores and VMDK files used by VM are not on supported storage.
2) All NetApp Storage Virtual Machines (SVMs) related to Datastore or VM are not registered within SnapCenter and/or SCV.

 

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.