Skip to main content
NetApp Knowledge Base

Takeover not possible: Resolution Guide

  1. Last updated
  2. Save as PDF
Views:
19,959
Visibility:
Public
Votes:
15
Category:
ontap-9
Specialty:
CORE
Last Updated:

Applies to

  • ONTAP 9
  • Except MetroCluster IP solutions

Issue

Takeover not possible, as displayed in the error message:

::> storage failover show -node ClusterA-01 -fields possible
node         possible
------------ --------
ClusterA-01  false

Cause

Follow this resolution guide to locate the solution based on the reason which caused Takeover to disable.

Run the storage failover command to determine the reason:

::>storage failover show –instance –node <node_name>

Example:

::> storage failover show -instance

                            Node: cluster1-01
                    Partner Name: cluster1-02
                   Node NVRAM ID: 5######
                Partner NVRAM ID: 5#####
                Takeover Enabled: true
                         HA Mode: ha
               Takeover Possible: false
    Reason Takeover not Possible: Local node missing partner disks

Solution

 

  Click on the reason causing takeover to disable to get the solution KB  
operator disabling takeover storage failover is disabled version mismatch
degraded mode (mailbox disks) interconnect errors disk shelf being too hot
NVRAM log not synchronized partner node halted after disabling takeover local node already in takeover state
local node about to halt mailbox disks are not healthy HA Interconnect down

local node missing partner disks 

ONTAP Select

local node missing partner disks

CVO

local node missing partner disks 

AFF/FAS
► Click to view Solution in Table Format
Message Solution

operator disabling takeover

 Takeover not possible: operator disabling takeover
storage failover is disabled Takeover not possible: both nodes in HA pair are not joined to cluster
version mismatch Takeover not possible: version mismatch
degraded mode (mailbox disks) Takeover not possible: degraded mode (mailbox disks)
interconnect errors Takeover not possible: interconnect errors
disk shelf being too hot Takeover not possible: disk shelf being too hot
NVRAM log not synchronized Takeover not possible: NVRAM log not synchronized
partner node halted after disabling takeover Takeover not possible: partner node halted after disabling takeover
local node already being in takeover state Takeover not possible: local node already in takeover state
local node about to halt Takeover not possible: local node about to halt
mailbox disks are not healthy Takeover not possible: Mailbox disks are not healthy
HA Interconnect down Takeover not possible: ONTAP Select: cf_diskinventory_sendFailed reason="HA Interconnect down"

local node missing partner disks

Additional Information

N/A

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.