Skip to main content
NetApp Knowledge Base

Why is the giveback of an ONTAP aggregate vetoed?

Views:
10,357
Visibility:
Public
Votes:
5
Category:
ontap-9
Specialty:
core
Last Updated:

Applies to

Issue

Any attempt to giveback aggregates in ONTAP may be vetoed to prevent disruption. Use the following command to determine which module the veto came from:

storage failover show-giveback

Example:

::> storage failover show-giveback
               Partner
Node           Aggregate Giveback Status
-------------- ----------------- ---------------------------------------------
  
Warning: Unable to list entries on node NodeA. RPC: Couldn't make connection
         [from mgwd on node "NodeB" (VSID: -1) to mgwd at 169.254.127.139]
NodeB
       CFO Aggregates    Failed module: autosupport. Giveback vetoed:
                                 AutoSupport collection is still in progress.
                                 Allow up to 20 minutes for AutoSupport
                                 processing after a takeover. Use the
                                 "storage failover giveback -override-vetoes
                                 true" command to override all veto checks,
                                 including AutoSupport collection.
                                 
                                 Warning: Overriding vetoes to perform a giveback can    
                                 be disruptive.
                                 
               NodeA_data01      Not attempted yet
2 entries were displayed.

Use the failed module name and review the following table for links to troubleshooting articles. 

Solution

The following is a list of common vetos and how to troubleshoot them:

Veto  Failed Module Name Solution

Autosupport

autosupport

Disk Inventory

disk_inventory

Dump / Restore

dump

Key Manager

keymanager

Lock Manager

lock_manager

RAID

raid

Snapmirror

replication_engine

 

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.