and use any packaging materials for shipping that are supplied to you.
5.2. Caching module
5.2.1. Replace the caching module - DM3010H
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.
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.
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
-node node name localhost -device-id device_number
Run the system controller flash-cache show command if you don’t
know the flashcache device ID.
b.
Verify that the data has been erased from the caching module:
system controller flash-
cache secure-erase show
The output should display the caching module status as erased.
2.
If AutoSupport is enabled, suppress automatic case creation by invoking an AutoSupport
message:
system node autosupport invoke -node * -type all -message
MAINT=number_of_hours_downh
The following AutoSupport message suppresses automatic case creation for two hours:
44
To Next Page
Loading...
