c. If an environment variable is not set as expected, modify it with the
setenvenvironment_variable_name changed_value command.
d.
Save your changes using the
saveenv command.
5. The next depends on your system configuration:
◦ If your system has onboard keymanager, NSE or NVE configured, go to
Post boot media replacement
steps for OKM, NSE, and NVE
◦ If your system does not have onboard keymanager, NSE or NVE configured, complete the steps in this
section.
6.
From the LOADER prompt, enter the
boot_ontap command.
If you see… Then…
The login prompt Go to the next step.
Waiting for giveback… a. Log into the partner node.
b.
Confirm the target node is ready for giveback with the
storage
failover show
command.
7. Connect the console cable to the partner node.
8.
Give back the node using the
storage failover giveback -fromnode local command.
9.
At the cluster prompt, check the logical interfaces with the
net int -is-home false command.
If any interfaces are listed as "false", revert those interfaces back to their home port using the
net int
revert
command.
10.
Move the console cable to the repaired node and run the
version -v command to check the ONTAP
versions.
11.
Restore automatic giveback if you disabled it by using the
storage failover modify -node local
-auto-giveback true
command.
Post boot media replacement steps for OKM, NSE, and NVE - FAS9500
Once environment variables are checked, you must complete steps specific to restore
Onboard Key Manager (OKM), NetApp Storage Encryption (NSE) and NetApp Volume
Encryption (NVE).
1. Determine which section you should use to restore your OKM, NSE, or NVE configurations: If NSE or NVE
are enabled along with Onboard Key Manager you must restore settings you captured at the beginning of
this procedure.
◦ If NSE or NVE are enabled and Onboard Key Manager is enabled, go to
Restore NVE or NSE when
Onboard Key Manager is enabled
.
◦ If NSE or NVE are enabled for ONTAP 9.6, go to
Restore NSE/NVE on systems running ONTAP 9.6
and later
.
716
To Next Page
