Skip to main content
NetApp Knowledge Base

VM Node Boot Failure in ONTAP Select MetroCluster – FM State 5

Views:
37
Visibility:
Public
Votes:
0
Category:
ontap-select
Specialty:
metrocluster
Last Updated:

Applies to

  • ONTAP Select MetroCluster (2-node configuration)
  • ONTAP 9.11 and later
  • VMware-based ONTAP Select clusters

Issue

  • One VM node in an ONTAP Select MetroCluster failed to boot after a network issue. The node displayed the following error repeatedly in the console:
panaintmc03::> storage failover show
                              Takeover
Node           Partner        Possible State Description
-------------- -------------- -------- -------------------------------------
panaintmc03n0101
               panaintmc03n04 false    In takeover
               01
panaintmc03n0401
               panaintmc03n01 -        Kernel loaded
               01
2 entries were displayed.
  • ONTAP node reporting below error
Entering FM state: 5 because mbFound: 0 local inhead swap: 0
Waiting for giveback... (Press Ctrl-C to abort wait)
  • Cluster management IP was inaccessible, and only one node was operational. The cluster was running in a degraded state.

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.