Release notes
Recable and give back the controller - AFF C30 and AFF C60
Suggest changes
-
PDF of this doc site
Collection of separate PDF docs
Creating your file...
Return control of storage resources to the replacement controller so your AFF C30 or AFF C60 system can resume normal operation. The give back procedure varies based on the encryption type used by your system: no encryption, Onboard Key Manager (OKM) encryption, or External Key Manager (EKM) encryption.
Reset encryption if enabled and return the controller to normal operation.
Return the impaired controller to normal operation by giving back its storage.
-
From the LOADER prompt, enter
boot_ontap. -
Press <enter> when console messages stop.
-
If you see the login prompt, go to the next step at the end of this section.
-
If you see Waiting for giveback, press the <enter> key, log into the partner node, and then go to the next step at the end of this section.
-
-
Return the impaired controller to normal operation by giving back its storage:
storage failover giveback -ofnode impaired_node_name -
If automatic giveback was disabled, reenable it:
storage failover modify -node local -auto-giveback true -
If AutoSupport is enabled, restore/unsuppress automatic case creation:
system node autosupport invoke -node * -type all -message MAINT=END
Reset onboard encryption and return the controller to normal operation.
-
From the LOADER prompt, enter
boot_ontap maint. -
Boot to the ONTAP menu from the LOADER prompt
boot_ontap menuand select option 10. -
Enter the OKM passphrase.
You are prompted twice for the passphrase. -
Enter the backup key data when prompted.
-
At the boot menu, enter option
1for normal boot. -
Press <enter> when Waiting for giveback is displayed.
-
Move the console cable to the partner node and login as
admin. -
Give back only the CFO aggregates (the root aggregate):
storage failover giveback -fromnode local -only-cfo-aggregates true-
If you encounter errors, contact NetApp Support.
-
-
Wait 5 minutes after the giveback report completes, and check failover status and giveback status:
storage failover showandstorage failover show-giveback. -
Synchronize and verify status of the keys:
-
Move the console cable back to the replacement controller.
-
Synchronize missing keys:
security key-manager onboard sync
You are prompted for the cluster-wide passphrase of OKM for the cluster. -
Verify status of the keys:
security key-manager key query -restored falseThe output should show no results when when properly synchronized.
If the output shows results (the key IDs of keys that are not present in the system's internal key table), contact NetApp Support.
-
-
Return the impaired controller to normal operation by giving back its storage:
storage failover giveback -ofnode impaired_node_name -
If automatic giveback was disabled, reenable it:
storage failover modify -node local -auto-giveback true -
If AutoSupport is enabled, restore/unsuppress automatic case creation:
system node autosupport invoke -node * -type all -message MAINT=END
Reset encryption and return the controller to normal operation.
-
If the root volume is encrypted with External Key Manager and the console cable is connected to the replacement node, enter
boot_ontap menuand select option11. -
Answer
yornto the following questions:Do you have a copy of the /cfcard/kmip/certs/client.crt file? {y/n}
Do you have a copy of the /cfcard/kmip/certs/client.key file? {y/n}
Do you have a copy of the /cfcard/kmip/certs/CA.pem file? {y/n}
OR
Do you have a copy of the /cfcard/kmip/servers.cfg file? {y/n}
Do you know the KMIP server address? {y/n}
Do you know the KMIP port? {y/n}
Contact NetApp Support if you have issues. -
Supply the information for:
-
The client certificate (client.crt) file contents
-
The client key (client.key) file contents
-
The KMIP server CA(s) (CA.pem) file contents
-
The IP address for the KMIP server
-
The port for the KMIP server
-
-
Once the system processes, you see the Boot Menu. Select '1' for normal boot.
-
Check the takeover status:
storage failover show -
Ensure any core dumps on the repaired node are saved by going to advanced mode
set -privilege advancedand thenrun local partner nosavecore. -
Return the impaired controller to normal operation by giving back its storage:
storage failover giveback -ofnode impaired_node_name -
If automatic giveback was disabled, reenable it:
storage failover modify -node local -auto-giveback true -
If AutoSupport is enabled, restore/unsuppress automatic case creation:
system node autosupport invoke -node * -type all -message MAINT=END
After you've transferred the ownership of storage resources back to the replacement controller, you need to complete the controller replacement procedure.
