Skip to main content
Install and maintain

Replace the FlashCache module carrier or a caching module - FAS70 and FAS90

Contributors dougthomp netapp-jsnyder netapp-martyh
PDFs

The NVMe SSD FlashCache module carrier contains one or two FlashCache modules (caching modules) with a single SSD FlashCache drive integrated into each caching module.

The FAS70 supports 2TB caching modules and FAS90 supports 4TB caching modules. You cannot mix caching modules of different capacity in the FlashCache module carrier.

You can perform either of the following procedures depending on what needs to be replaced: the entire Flashcache module carrier or a caching module.

Replace the FlashCache module carrier

The FlashCache module carrier is located in slot 6 and houses up to two FlashCache modules. You cannot hot-swap the FlashCache module carrier

Before you begin

  • Ensure your storage system has the appropriate operating system for the replacement FlashCache module carrier.

  • Confirm all other components are functioning properly; if not, you must contact technical support.

Step 1: Shut down the impaired node

Shut down or take over the impaired controller using one of the following options.

Option 1 Most systems

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.

Before you begin

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.

Steps

  1. If AutoSupport is enabled, suppress automatic case creation by invoking an AutoSupport message command: system node autosupport invoke -node * -type all -message MAINT=number_of_hours_downh

    The following AutoSupport command suppresses automatic case creation for two hours: cluster1:*> system node autosupport invoke -node * -type all -message MAINT=2h

  2. 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.

    System prompt or password prompt (enter system password)

    Halt or take over 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 y.
Option 2 MetroCluster configuration
Note Do not use this procedure if your system is in a two-node MetroCluster 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 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 you have a MetroCluster configuration, you must have confirmed that the MetroCluster Configuration State is configured and that the nodes are in an enabled and normal state (metrocluster node show).

Steps

  1. If AutoSupport is enabled, suppress automatic case creation by invoking an AutoSupport command: system node autosupport invoke -node * -type all -message MAINT=number_of_hours_downh

    The following AutoSupport command suppresses automatic case creation for two hours: cluster1:*> system node autosupport invoke -node * -type all -message MAINT=2h

  2. 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.

    System prompt or password prompt (enter system password)

    Halt or take over 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 y.

Step 2: Replace the FlashCache module carrier

Perform the following steps to replace the FlashCache module carrier.

Steps

  1. If you are not already grounded, properly ground yourself.

  2. Locate the failed FlashCache module carrier, in slot 6, by the lit amber Attention LED on the front of the FlashCache module carrier.

    Remove the FlashCache module carrier

    Callout number 1

    FlashCache module carrier

    Callout number 2

    Caching module slot numbers

    Callout number 3

    FlashCache module carrier cam handle

    Callout number 4

    FlashCache module carrier fault LED

  3. Remove the failed FlashCache module carrier:

    1. Rotate the cable management tray down by pulling the buttons on both sides on the inside of the cable management tray and then rotate the tray down.

    2. Pinch the blue tab at the bottom of the FlashCache module carrier.

    3. Rotate the tab away from the module.

  4. Pull the FlashCache module carrier out of the controller module and set it on an antistatic mat.

  5. Move the caching modules to the replacement FlashCache module carrier:

    1. Pinch the Terra Cotta tab at the top of the caching module and rotate the cam handle away from the caching module.

    2. Remove the module from the enclosure by hooking your finger into the cam lever opening and pulling the module out of the FlashCache module carrier.

    3. Install the caching module into the same slot in the replacement FlashCache module carrier and rotate the cam handle to the closed position on the caching module to lock it in place.

  6. Repeat these steps if there is a second caching module.

  7. Install the replacement FlashCache module carrier into the system:

    1. Align the module with the edges of the enclosure slot opening.

    2. Gently slide the module into the slot all the way into the enclosure, and then rotate the cam latch all the way up to lock the module in place.

    3. Rotate the cable management tray up to the closed position.

Step 3: Reboot the controller

After you replace the FlashCache module carrier, you must reboot the controller module.

Steps

  1. From the LOADER prompt, reboot the node: bye

    Note This reinitializes the I/O cards and other components and reboots the node.

  2. Return the node to normal operation: storage failover giveback -ofnode impaired_node_name

  3. If automatic giveback was disabled, reenable it: storage failover modify -node local -auto-giveback true

Step 4: Return the failed part to NetApp

Return the failed part to NetApp, as described in the RMA instructions shipped with the kit. See the Part Return and Replacements page for further information.

Replace the caching module

Before you begin

The FlashCache modules (caching modules) are located in slot 6-1 or in slot 6-2 or in both slot 6-1 and slot 6-2.

You can hot-swap the individual caching modules with caching modules of the same capacity from the same vendor or from a different supported vendor.

Before you begin

  • Ensure the replacement caching module has the same capacity as the failed one, from the same vendor or from a different supported vendor.

  • Confirm all other components are functioning properly; if not, you must contact technical support.

  • The drives in the caching modules are not field replaceable units (FRU). You must replace the entire caching module.

Steps

  1. If you are not already grounded, properly ground yourself.

  2. Locate the failed caching module, in slot 6, by the lit amber Attention LED on the front of the caching module.

  3. Prepare the caching module slot for replacement as follows:

    1. Record the caching module capacity, part number, and serial number on the target node: system node run local sysconfig -av 6

    2. In admin privilege level, prepare the target caching module slot for removal, responding y when prompted whether to continue: system controller slot module remove -node node_name -slot slot_number The following command prepares slot 6-1 on node1 for removal, and displays a message that it is safe to remove:

      ::> system controller slot module remove -node node1 -slot 6-1

Warning: SSD module in slot 6-1 of the node node1 will be powered off for removal.
Do you want to continue? (y|n): _y_
The module has been successfully removed from service and powered off. It can now be safely removed.

    3. Display the slot status with the system controller slot module show command.

      The caching module slot status displays powered-off in the screen output for the caching module that needs replacing.

    Note See the Command man pages for your version of ONTAP for more details.

  4. Remove the caching module:

    Remove the caching module

    Callout number 1

    Caching module cam handle

    Callout number 2

    Caching module fault LED

    1. Rotate the cable management tray down by pulling the buttons on both sides on the inside of the cable management tray and then rotate the tray down.

    2. Press the terra cotta release button on the front of the caching module.

    3. Rotate the cam handle as far as it will go.

    4. Remove the caching module module from the enclosure by hooking your finger into the cam lever opening and pulling the module out of the FlashCache module carrier.

      Be sure to support the caching module as you remove it from the FlashCache module carrier.

  5. Install the replacement caching module:

    1. Align the edges of the caching module with the opening in the controller module.

    2. Gently push the caching module into the bay until the cam handle engages.

    3. Rotate the cam handle until it locks into place.

    4. Rotate the cable management tray up to the closed position.

  6. Bring the replacement caching module online by using the system controller slot module insert command as follows:

    The following command prepares slot 6-1 on node1 for power-on, and displays a message that it is powered on:

    ::> system controller slot module insert -node node1 -slot 6-1

Warning: NVMe module in slot 6-1 of the node localhost will be powered on and initialized.
Do you want to continue? (y|n): `y`

The module has been successfully powered on, initialized and placed into service.

  7. Verify the slot status using the system controller slot module show command.

    Make sure that command output reports status for the as powered-on and ready for operation.

  8. Verify that the replacement caching module is online and recognized, and then visually confirm that the amber attention LED is not lit: sysconfig -av slot_number

    Note If you replace the caching module with a caching module from a different vendor, the new vendor name is displayed in the command output.

  9. Return the failed part to NetApp, as described in the RMA instructions shipped with the kit. See the Part Return and Replacements page for further information.