Skip to main content
NetApp Knowledge Base

Node fails to boot with error message "mcc.drsom.fsm.invalidState" in MetroCluster system

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

Applies to

  • MetroCluster
  • ONTAP 9

Issue

A node of MetroCluster fails to boot with error message mcc.drsom.fsm.invalidState

Example:
 
NetApp Data ONTAP 9.1P2
 
Trying to mount root from msdosfs:/dev/da0s1 [ro]...
md0 attached to /X86_64/freebsd/image2/rootfs.img
Trying to mount root from ufs:/env/md0.uzip []...
mountroot: waiting for device /env/md0.uzip ...
Copyright (C) 1992-2017 NetApp.
All rights reserved.
Writing loader environment to the boot device.
Loader environment has been saved to the boot device.
*******************************
* *
* Press Ctrl-C for Boot Menu. *
* *
*******************************
Attempting to use existing varfs on /dev/nvrd1
No SVM keys found.
Firewall rules loaded.
Feb 08 22:51:22 Battery charge capacity: 3328 mA*hr. Power outage protection flash de-staging cycles: 100
Feb 08 22:52:42 [cluster:fcvi.update.link.state:notice]: FC-VI adapter: Physical link is up on port 1a.
Ipspace "ACP" created
Feb 08 22:52:42 [cluster:fcvi.update.link.state:notice]: FC-VI adapter: Physical link is up on port 1b.
Feb 08 22:52:42 [cluster:fcvi.qlgc.rmt.link.up:notice]: FC-VI adapter: Link to partner node over port 1a is up. Partner port id = 0xe8, partner node's system id = 0.
Feb 08 22:52:42 [cluster:fcvi.qlgc.rmt.link.up:notice]: FC-VI adapter: Link to partner node over port 1b is up. Partner port id = 0xe8, partner node's system id = 0.
Feb 08 22:52:42 [cluster:fcvi.qlgc.received.reject:notice]: FC-VI adapter: Connect request rejected on port 1b. QP name = Control, QP index = 1, Remote node's system id = xxxxxx.
WAFL CPLEDGER is enabled. Checklist = 0x7ff841ff
Feb 08 22:52:49 [cluster:mcc.drsom.fsm.invalidState:error]: DRSOM FSM event (set_sb_recovery_pending) generated in state (switchover_complete) will cause an invalid FSM state transition.
Uptime: 2m1s
System halting...

 

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.