Commands for performing a manual takeover

You must know the commands you can use when initiating a takeover. You can initiate a takeover on a node in an HA pair to perform maintenance on that node while still serving the data on its disks, array LUNs, or both to users.

Command Description
cf takeover Initiates a takeover of the partner of the local node.

Takeover is aborted if a core dump is in progress on the partner (if the cf.takeover.on_panic option is set to off).

Takeover starts either after the partner halts successfully or after a timeout.

cf takeover -f Initiates an immediate takeover of the partner of the local node regardless of whether the partner node is dumping its core

The partner node is not allowed to halt gracefully

cf forcetakeover Tells the HA monitor to ignore some configuration problems that would otherwise prevent a takeover (such as unsynchronized NVRAM due to a faulty HA interconnect connection), and then initiates a takeover of the partner of the local node
cf forcetakeover -d Initiates a takeover of the local partner even in the absence of a quorum of partner mailbox disks or partner mailbox LUNs

The cf forcetakeover -d command is valid only if the remote_syncmirror option is enabled.

Attention: You should only use the -d option after you verify that the partner is down. The -d option is used in conjunction with RAID mirroring to recover from disasters in which one partner is not available. For more information, see the Data ONTAP Data Protection Online Backup and Recovery Guide for 7-Mode.
cf takeover -n Initiates a takeover for a nondisruptive upgrade

For more information, see the Data ONTAP Upgrade and Revert/Downgrade Guide for 7-Mode