EasyManua.ls Logo

NetApp ASA A150 - Replace the Caching Module - ASA A150

NetApp ASA A150
87 pages
Print Icon
To Next Page IconTo Next Page
To Next Page IconTo Next Page
To Previous Page IconTo Previous Page
To Previous Page IconTo Previous Page
Loading...
If the command fails, contact Customer Support.
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.
14.
Restore Autosupport if it was disabled by using the
system node autosupport invoke -node *
-type all -message MAINT=END
Return the failed part to NetApp - ASA A150
Return the failed part to NetApp, as described in the RMA instructions shipped with the
kit. See the
Part Return & Replacements page for further information.
Replace the caching module - ASA A150
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.
Replace the failed component with a replacement FRU component you received from your provider.
Step 1: Shut down the impaired controller
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; see
Synchronize a node with the cluster.
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
21

Related product manuals