Replace the caching module - FAS8200
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 might want to erase the contents of your caching module before replacing it.
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:
Erase the data on the caching module:
system controller flash-cache secure-erase run -node node name localhost -device-id device_number
system controller flash-cache showcommand if you don’t know the flashcache device ID.
Verify that the data has been erased from the caching module:
system controller flash-cache secure-erase show
You must replace the failed component with a replacement FRU component you received from your provider.
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.
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.
If you are using NetApp Storage Encryption, you must have reset the MSID using the instructions in the Returning SEDs to unprotected mode.
If you have a SAN system, you must have checked event messages (
cluster kernel-service show) for impaired controller SCSI blade. The
cluster kernel-service showcommand displays the node name, quorum status of that node, availability status of that node, and operational status of that node.
Each SCSI-blade process should be in quorum with the other nodes in the cluster. Any issues must be resolved before you proceed with the replacement.
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.
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:
cluster1:> system node autosupport invoke -node * -type all -message MAINT=2h
Disable automatic giveback from the console of the healthy controller:
storage failover modify –node local -auto-giveback false
When you see Do you want to disable auto-giveback?, enter
Take the impaired controller to the LOADER prompt:
If the impaired controller is displaying… Then…
The LOADER prompt
Go to Remove controller module.
Waiting for giveback…
Press Ctrl-C, and then respond
System prompt or password prompt
Take over or halt the impaired controller from the healthy controller:
storage failover takeover -ofnode impaired_node_name
When the impaired controller shows Waiting for giveback…, press Ctrl-C, and then respond
To shut down the impaired controller, you must determine the status of the controller and, if necessary, switch over the controller so that the healthy controller continues to serve data from the impaired controller storage.
If you are using NetApp Storage Encryption, you must have reset the MSID using the instructions in the "Return a FIPS drive or SED to unprotected mode" section of NetApp Encryption overview with the CLI.
You must leave the power supplies turned on at the end of this procedure to provide power to the healthy controller.
Check the MetroCluster status to determine whether the impaired controller has automatically switched over to the healthy controller:
Depending on whether an automatic switchover has occurred, proceed according to the following table:
If the impaired controller… Then…
Has automatically switched over
Proceed to the next step.
Has not automatically switched over
Perform a planned switchover operation from the healthy controller:
Has not automatically switched over, you attempted switchover with the
metrocluster switchovercommand, and the switchover was vetoed
Review the veto messages and, if possible, resolve the issue and try again. If you are unable to resolve the issue, contact technical support.
Resynchronize the data aggregates by running the
metrocluster heal -phase aggregatescommand from the surviving cluster.
controller_A_1::> metrocluster heal -phase aggregates [Job 130] Job succeeded: Heal Aggregates is successful.
If the healing is vetoed, you have the option of reissuing the
metrocluster healcommand with the
-override-vetoesparameter. If you use this optional parameter, the system overrides any soft vetoes that prevent the healing operation.
Verify that the operation has been completed by using the metrocluster operation show command.
controller_A_1::> metrocluster operation show Operation: heal-aggregates State: successful Start Time: 7/25/2016 18:45:55 End Time: 7/25/2016 18:45:56 Errors: -
Check the state of the aggregates by using the
storage aggregate showcommand.
controller_A_1::> storage aggregate show Aggregate Size Available Used% State #Vols Nodes RAID Status --------- -------- --------- ----- ------- ------ ---------------- ------------ ... aggr_b2 227.1GB 227.1GB 0% online 0 mcc1-a2 raid_dp, mirrored, normal...
Heal the root aggregates by using the
metrocluster heal -phase root-aggregatescommand.
mcc1A::> metrocluster heal -phase root-aggregates [Job 137] Job succeeded: Heal Root Aggregates is successful
If the healing is vetoed, you have the option of reissuing the
metrocluster healcommand with the -override-vetoes parameter. If you use this optional parameter, the system overrides any soft vetoes that prevent the healing operation.
Verify that the heal operation is complete by using the
metrocluster operation showcommand on the destination cluster:
mcc1A::> metrocluster operation show Operation: heal-root-aggregates State: successful Start Time: 7/29/2016 20:54:41 End Time: 7/29/2016 20:54:42 Errors: -
On the impaired controller module, disconnect the power supplies.
Step 2: Open the controller module
To access components inside the controller, you must first remove the controller module from the system and then remove the cover on the controller module.
If you are not already grounded, properly ground yourself.
Loosen the hook and loop strap binding the cables to the cable management device, and then unplug the system cables and SFPs (if needed) from the controller module, keeping track of where the cables were connected.
Leave the cables in the cable management device so that when you reinstall the cable management device, the cables are organized.
Remove and set aside the cable management devices from the left and right sides of the controller module.
Loosen the thumbscrew on the cam handle on the controller module.
Pull the cam handle downward and begin to slide the controller module out of the chassis.
Make sure that you support the bottom of the controller module as you slide it out of the chassis.
Step 3: Replace or add a caching module
To replace or add a caching module referred to as the M.2 PCIe card on the label on your controller, locate the slots inside the controller and follow the specific sequence of steps.
Your storage system must meet certain criteria depending on your situation:
It must have the appropriate operating system for the caching module you are installing.
It must support the caching capacity.
All other components in the storage system must be functioning properly; if not, you must contact technical support.
Locate the caching module at the rear of the controller module and remove it.
Press the release tab.
Remove the heatsink.
The storage system comes with two slots available for the caching module and only one slot is occupied, by default.
If you are adding a caching module, go to the next step; if you are replacing the caching module, gently pull it straight out of the housing.
Align the edges of the caching module with the socket in the housing, and then gently push it into the socket.
Verify that the caching module is seated squarely and completely in the socket.
If necessary, remove the caching module and reseat it into the socket.
Reseat and push the heatsink down to engage the locking button on the caching module housing.
Repeat the steps if you have a second caching module. Close the controller module cover, as needed.
Step 4: Reinstall the controller
After you replace a component within the controller module, you must reinstall the controller module in the system chassis.
Align the end of the controller module with the opening in the chassis, and then gently push the controller module halfway into the system.
Do not completely insert the controller module in the chassis until instructed to do so.
Recable the system, as needed.
If you removed the media converters (QSFPs or SFPs), remember to reinstall them if you are using fiber optic cables.
Complete the reinstallation of the controller module:
The controller module begins to boot as soon as it is fully seated in the chassis
With the cam handle in the open position, firmly push the controller module in until it meets the midplane and is fully seated, and then close the cam handle to the locked position.
Do not use excessive force when sliding the controller module into the chassis to avoid damaging the connectors.
Tighten the thumbscrew on the cam handle on back of the controller module.
If you have not already done so, reinstall the cable management device.
Bind the cables to the cable management device with the hook and loop strap.
Step 5: Switch back aggregates in a two-node MetroCluster configuration
After you have completed the FRU replacement in a two-node MetroCluster configuration, you can perform the MetroCluster switchback operation. This returns the configuration to its normal operating state, with the sync-source storage virtual machines (SVMs) on the formerly impaired site now active and serving data from the local disk pools.
This task only applies to two-node MetroCluster configurations.
Verify that all nodes are in the
metrocluster node show
cluster_B::> metrocluster node show DR Configuration DR Group Cluster Node State Mirroring Mode ----- ------- -------------- -------------- --------- -------------------- 1 cluster_A controller_A_1 configured enabled heal roots completed cluster_B controller_B_1 configured enabled waiting for switchback recovery 2 entries were displayed.
Verify that resynchronization is complete on all SVMs:
metrocluster vserver show
Verify that any automatic LIF migrations being performed by the healing operations were completed successfully:
metrocluster check lif show
Perform the switchback by using the
metrocluster switchbackcommand from any node in the surviving cluster.
Verify that the switchback operation has completed:
The switchback operation is still running when a cluster is in the
cluster_B::> metrocluster show Cluster Configuration State Mode -------------------- ------------------- --------- Local: cluster_B configured switchover Remote: cluster_A configured waiting-for-switchback
The switchback operation is complete when the clusters are in the
cluster_B::> metrocluster show Cluster Configuration State Mode -------------------- ------------------- --------- Local: cluster_B configured normal Remote: cluster_A configured normal
If a switchback is taking a long time to finish, you can check on the status of in-progress baselines by using the
metrocluster config-replication resync-status showcommand.
Reestablish any SnapMirror or SnapVault configurations.
Step 6: Complete the replacement process
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.