Skip to main content
NetApp Stage KB

SVM (vserver) stopped during head upgrade procedure in a MetroCluster

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

Applies to

  • MetroCluster
  • ONTAP 9.5+
  • FC-VI link cross cabled
  • mgwd.log containing the follow sequence
    • has_remote_cluster_done_switchover was retried. Retry count : 9
    • has_remote_cluster_done_switchover failed with err = FCVI Interconnect might be down. For fabric configurations, use "storage switch add" to start monitoring the switches.

Issue

  • During a head upgrade all SVMs are entering a stopped state.
  • Vserver start command fails with error:

    Failed to determine if the remote cluster has done a switchover. Reason :
    Internal error occurred on node "ClusterA-02" in cluster "ClusterA".
    Details: (FCVI Interconnect might be down. For fabric configurations, use
    "storage switch add" to start monitoring the switches. Then run "storage switch
    show -port" to verify that the status of the used port is "online", and run
    "storage switch show -san-config" to verify that the fabric configuration
    (vsan/zone) is appropriate. For Stretch configurations, verify the FCVI
    cabling.).

 

 

 

 

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.
0e772073-26c8-40c8-b65a-e9ad787483d7