Skip to main content
NetApp Knowledge Base

OnCommand System Manager displays error: "license is not available" when attempting to create a SnapVault or SnapMirror relationship

Views:
536
Visibility:
Public
Votes:
0
Category:
not set
Specialty:
legacy
Last Updated:

Applies to

  • OnCommand System Manager 3.1.2
  • OnCommand System Manager 8.3.x
  • OnCommand System Manager 9.x

Issue

OnCommand System Manager (OCSM) displays the 'license is not available' error message when selecting a peered cluster from the cluster drop-down in the protection relationship creation wizard. This error is displayed while attempting to create a SnapVault or SnapMirror relationship in OCSM when selecting a cluster from the drop-down list in the relationship creation wizard, even though the SnapVault or SnapMirror license is confirmed to be valid.

  • SnapMirror license is not available
  • SnapVault license is not available

Note: Creating Data Protection relationships via Cluster Ontap CLI is successful.

In addition to the "SnapMirror License is not available" error message, the admin will note that when they attempt to modify a Data Protection relationship, the resulting screen will display error:

  • Data ONTAP API Failed :RPC: Unable to receive (13001) ​

OR

  • Data ONTAP API Failed [HTTP Error:{502}] :502 Bad Gateway

 

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.