Restore key-manager configuration on the upgraded node1
Suggest changes
-
PDF of this doc site
-
Upgrade by using ARL
- Use "system controller replace" commands to upgrade controller models in the same chassis
-
Upgrade by using ARL
Collection of separate PDF docs
Creating your file...
This may take a few minutes. Thanks for your patience.
Your file is ready
If you are using NetApp Aggregate Encryption (NAE) or NetApp Volume Encryption (NVE) to encrypt volumes on the system you are upgrading, the encryption configuration must be synchronized to the new nodes. If you do not resynchronize the key-manager, when you relocate the node1 aggregates from node2 to the upgraded node1 by using ARL, failures might occur because node1 does not have the required encryption keys to bring encrypted volumes and aggregates online.
About this task
Synchronize the encryption configuration to the new nodes by performing the following steps:
Steps
-
Run the following command from node1:
security key-manager onboard sync
-
Verify that the SVM-KEK key is restored to "true" on node1 before you relocate the data aggregates:
::> security key-manager key query -node node1 -fields restored -key-type SVM-KEK
Example::> security key-manager key query -node node1 -fields restored -key-type SVM-KEK node vserver key-server key-id restored -------- --------- ----------- --------------------------------------- -------- node1 svm1 "" 00000000000000000200000000000a008a81976 true 2190178f9350e071fbb90f00000000000000000