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|
|Take over the partner node before the partner has time to close its storage resources gracefully
Note: If possible, migrate the data LIFs to another node before specifying this option.
|storage failover takeover -option immediate|
|Take over the partner node without migrating LIFs||storage failover takeover -skip-lif-migration 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 a Data ONTAP version mismatch
Note: This option is only used during the nondisruptive Data 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|
|Monitor the progress of the takeover as the partner's aggregates are moved to the node doing the takeover||storage failover show-takeover|
See the man page for each command for more information. For a mapping of the cf options and commands used in Data ONTAP operating in 7-Mode to the storage failover commands, refer to the Data ONTAP 7-Mode to Clustered Data ONTAP Command Map. When in clustered Data ONTAP, you should always use the storage failover commands rather than issuing an equivalent 7-Mode command via the nodeshell (using the system node run command).