Skip to main content
NetApp Knowledge Base

Node goes down when attempting to perform takeover

  1. Last updated
    Oct 8, 2020
  2. Save as PDF
Views:
871
Visibility:
Public
Votes:
0
Category:
clustered-data-ontap-8
Specialty:
core
Last Updated:
10/8/2020, 8:39:03 AM

Applies to

  • ONTAP 8.3 Cluster Mode
  • Takeover in progress

Issue

  • When shutting down a node, the HA partner panics when trying to perform takeover
SP console log
PANIC: Failover Monitor: unable to transit - takeover process is hung (wafl) in SK process cf_main on release 8.3 (C) on Mon Sep 21 16:22:12 CEST 2020
version: 8.3: Mon Mar  9 19:20:57 PDT 2015
 
  • The takeover fails and becomes disabled on reboot
EMS log
[Node1: cf_main: cf.fm.givebackForced:alert]: Failover monitor: forcing reboot to clear state
[Node1: cf_main: cf.fm.panicToInProgress:alert]: Failover monitor: Panic during takeover; takeover will be disabled on reboot.
 
  • Low memory message seen in EMS
[Node-1: scsit_lu_1: wafl.memory.statusLowMemory:warning]: WAFL is running low on memory, with 771MB remaining.

 

 

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.