7. At the Boot Menu select the option for Normal Boot.
The system boots to
Waiting for giveback… prompt.
8. Move the console cable to the partner controller and login as admin.
9.
Confirm the target controller is ready for giveback with the
storage failover show command.
10.
Give back only the CFO aggregates with the storage failover giveback
-fromnode local -only
-cfo-aggregates true
command.
◦ If the command fails because of a failed disk, physically disengage the failed disk, but leave the
disk in the slot until a replacement is received.
◦ If the command fails because of an open CIFS session, check with the customer on how to close
out CIFS sessions.
Terminating CIFS can cause loss of data.
◦ If the command fails because the partner is "not ready", wait 5 minutes for the NVMEMs to
synchronize.
◦ If the command fails because of an NDMP, SnapMirror, or SnapVault process, disable the
process. See the appropriate Documentation Center for more information.
11.
Once the giveback completes, check the failover and giveback status with the
storage failover
show
and `storage failover show-giveback` commands.
Only the CFO aggregates (root aggregate and CFO style data aggregates) will be shown.
12. Move the console cable to the target controller.
13. If you are running ONTAP 9.5 and earlier, run the key-manager setup wizard:
a.
Start the wizard using the
security key-manager setup -nodenodename command, and
then enter the passphrase for onboard key management when prompted.
b.
Enter the
key-manager key show -detail command to see a detailed view of all keys
stored in the onboard key manager and verify that the
Restored column = yes for all
authentication keys.
If the Restored column = anything other than yes, contact Customer Support.
c. Wait 10 minutes for the key to synchronize across the cluster.
14. If you are running ONTAP 9.6 or later:
a.
Run the
security key-manager onboard sync command and then enter the passphrase
when prompted.
b.
Enter the
security key-manager key query command to see a detailed view of all keys
stored in the onboard key manager and verify that the
Restored column = yes/true for all
authentication keys.
If the Restored column = anything other than yes/true, contact Customer
Support.
c. Wait 10 minutes for the key to synchronize across the cluster.
239