Skip to main content
NetApp Knowledge Base

Error  during MetroCluster FC to IP transition, prevents the transition

Views:
29
Visibility:
Public
Votes:
0
Category:
metrocluster
Specialty:
metrocluster
Last Updated:

Applies to

  • MetroCluster FC
  • MetroCluster IP
  • Transition FC to IP

Issue

Prior to start the transition, the command 

metrocluster transition enable -transition-mode non-disruptive

was not run as requested in the documentation.
 
Further steps done:
  1. Moving cluster interfaces on the old nodes to the new switches
  2. Adding  the new nodes into the cluste
If you run the command later in the process, there will be error similar to the one bellow

Error: command failed: This operation is supported only on a MetroCluster over FC configuration

Trying to create MEtrocluster interfaces on the new nodes will show the error:cluster01::> metrocluster configuration-settings interface create -cluster-name cluster1 -home-node node01 -home-port e2a -address xx.x.x.x -netmask 255.255.255.0

Error: command failed: One or more nodes in cluster "cluster1" do not have HAOSC set to "mccip". Use the "ha-config modify chassis mccip" and "ha-config modify controller mccip" commands in maintenance mode to change the HAOSC settings on nodes in cluster "cluster1", and try the command again

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.