Commands for performing and monitoring manual takeovers

You can manually initiate the takeover of a node in an HA pair to perform maintenance on that node while it is still serving the data on its disks, array LUNs, or both to users.

The following table lists and describes the commands you can use when initiating a takeover:

If you want to... Use this command...
Take over the partner node storage failover takeover
Monitor the progress of the takeover as the partner's aggregates are moved to the node doing the takeover storage failover show-takeover
Display the storage failover status for all nodes in the cluster storage failover show
Take over the partner node without migrating LIFs storage failover takeover -skip-lif-migration-before-takeover true
Take over the partner node even if there is a disk mismatch storage failover takeover -allow-disk-inventory-mismatch
Take over the partner node even if there is an ONTAP version mismatch
Note: This option is only used during the nondisruptive ONTAP upgrade process.
storage failover takeover -option allow-version-mismatch
Take over the partner node without performing aggregate relocation storage failover takeover -bypass-optimization true
Take over the partner node before the partner has time to close its storage resources gracefully storage failover takeover -option immediate
Note: Before you issue the storage failover command with the immediate option, you must migrate the data LIFs to another node by using the following command: network interface migrate-all -node node
  • If you specify the storage failover takeover -option immediate command without first migrating the data LIFs, data LIF migration from the node is significantly delayed even if the skip-lif-migration-before-takeover option is not specified.
  • Similarly, if you specify the immediate option, negotiated takeover optimization is bypassed even if the bypass-optimization option is set to false.