• You must replace the failed component with a replacement FRU component you received from your
provider.
Step 1: Shut down the impaired controller
Shut down or take over the impaired controller using the appropriate procedure for your
configuration.
Option 1: Most configurations
To shut down the impaired controller, you must determine the status of the controller and,
if necessary, take over the controller so that the healthy controller continues to serve data
from the impaired controller storage.
About this task
If you have a cluster with more than two nodes, it must be in quorum. If the cluster is not in quorum or a healthy
controller shows false for eligibility and health, you must correct the issue before shutting down the impaired
controller.
+
ONTAP 9 System Administration Reference
You might want to erase the contents of your caching module before replacing it.
Steps
1. Although data on the caching module is encrypted, you might want to erase any data from the impaired
caching module and verify that the caching module has no data:
a. Erase the data on the caching module:
system controller flash-cache secure-erase run
b. Verify that the data has been erased from the caching module:
system controller flash-cache
secure-erase show -node node_name
The output should display the caching module status as erased.
2. If the impaired controller is part of an HA pair, disable automatic giveback from the console of the healthy
controller:
storage failover modify -node local -auto-giveback false
3. Take the impaired controller to the LOADER prompt:
If the impaired controller is
displaying…
Then…
The LOADER prompt
Go to the next step.
Waiting for giveback…
Press Ctrl-C, and then respond
y
when prompted.
220
