◦
If the
Key Manager type
=
onboard
and the
Restored
column = anything other than
yes/true
,
use the
security key-manager onboard sync
command to re-sync the Key Manager type.
Use the security key-manager key query to verify that the
Restored
column =
yes/true
for all
authentication keys.
11. Connect the console cable to the partner controller.
12. Give back the controller using the
storage failover giveback -fromnode local
command.
13. Restore automatic giveback if you disabled it by using the
storage failover modify -node local
-auto-giveback true
command.
Return the failed part to NetApp - FAS2600
After you replace the part, you can return the failed part to NetApp, as described in the
RMA instructions shipped with the kit. Contact technical support at
, 888-
463-8277 (North America), 00-800-44-638277 (Europe), or +800-800-80-800
(Asia/Pacific) if you need the RMA number or additional help with the replacement
procedure.
Replace the caching module - FAS2600
You must replace the caching module in the controller module when your system
registers a single AutoSupport (ASUP) message that the module has gone offline; failure
to do so results in performance degradation.
• You must replace the failed component with a replacement FRU component you received from your
provider.
AFF FAS2600 caching module replacement video
Step 1: Shut down the impaired controller
You can shut down or take over the impaired controller using different procedures, depending on the storage
system hardware configuration.
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.
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
115
