Skip to main content
Install and maintain

Replace the system management module - AFF A70 and AFF A90

Contributors netapp-jsnyder dougthomp
PDFs

Replace the System Management module in your AFF A70 or AFF A90 system when it becomes defective or its firmware is corrupted. The replacement process involves shutting down the controller, replacing the failed System Management module, rebooting the controller, updating the license keys, and returning the failed part to NetApp.

The System Management module, located at the back of the controller in slot 8, contains onboard components for system management, as well as ports for external management. The target controller must be shut down to replace an impaired System Management module or to replace the boot media.

Before you begin

  • Make sure all other system components are working properly.

  • Make sure that the partner controller is able to take over the impaired controller.

  • Make sure you replace the failed component with a replacement component you received from NetApp.

About this task

This procedure uses the following terminology:

  • The impaired controller is the controller on which you are performing maintenance.

  • The healthy controller is the HA partner of the impaired controller.

Step 1: Shut down the impaired controller

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.

About this task

  • If you have a SAN system, you must have checked event messages (cluster kernel-service show) for the impaired controller SCSI blade. The cluster kernel-service show command (from priv advanced mode) 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.

Steps

  1. If AutoSupport is enabled, suppress automatic case creation by invoking an AutoSupport message:

    system node autosupport invoke -node * -type all -message MAINT=<# of hours>h

    The following AutoSupport message suppresses automatic case creation for two hours:

    cluster1:> system node autosupport invoke -node * -type all -message MAINT=2h

  2. Disable automatic giveback:

    1. Enter the following command from the console of the healthy controller:

      storage failover modify -node impaired_node_name -auto-giveback false

    2. Enter y when you see the prompt Do you want to disable auto-giveback?

  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

    Take over or halt the impaired controller from the healthy controller:

    storage failover takeover -ofnode impaired_node_name -halt true

    The -halt true parameter brings you to the LOADER prompt.
Option 2: Controller is in a MetroCluster

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.

  • 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 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

  2. Disable automatic giveback:

    1. Enter the following command from the console of the healthy controller:

      storage failover modify -node local -auto-giveback false

    2. Enter y when you see the prompt Do you want to disable auto-giveback?

  3. Take the impaired controller to the LOADER prompt:

    If the impaired controller is displaying…​ Then…​

    The LOADER prompt

    Go to the next section.

    Waiting for giveback…​

    Press Ctrl-C, and then respond y when prompted.

    System prompt or password prompt (enter system password)

    Take over or halt the impaired controller from the healthy controller:

    storage failover takeover -ofnode impaired_node_name -halt true

    The -halt true parameter brings you to the LOADER prompt.

Step 2: Replace the System Management module

Replace the impaired system management module.

Steps

  1. Ensure that all drives in the chassis are firmly seated against the midplane by using your thumbs to push each drive until you feel a positive stop.

    Seat disk drives

  2. Make sure NVRAM destage has completed before proceeding. When the LED on the NV module is off, NVRAM is destaged. If the LED is flashing, wait for the flashing to stop. If flashing continues for longer than 5 minutes, contact Technical Support for assistance.

    NVRAM attention and status LED location graphic

    Callout number 1

    NVRAM status LED

    Callout number 2

    NVRAM attention LED

    • If the NV LED is off, go to the next step.

    • If the NV LED is flashing, wait for the flashing to stop. If flashing continues for longer than 5 minutes, contact Technical Support for assistance.

  3. Go to the rear of the chassis. If you are not already grounded, properly ground yourself.

  4. Unplug the controller's PSUs.

    Note If your system has DC power, disconnect the power block from the PSUs.

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

  6. Remove any cables connected to the System Management module. Make sure that label where the cables were connected, so that you can connect them to the correct ports when you reinstall the module.

    Replace the System Management module
    Callout number 1

    System Management module cam latch

  7. Remove the System Management module:

    1. Depress the system management cam button. The cam lever moves away from the chassis.

    2. Rotate the cam lever all the way down.

    3. Loop your finger into the cam lever and pull the module straight out of the system.

    4. Place the System Management module on an anti-static mat, so that the boot media is accessible.

  8. Move the boot media to the replacement System Management module:

    Boot media replace
    Callout number 1

    System Management module cam latch
    Callout number 2

    Boot media locking button
    Callout number 3

    Boot media

    1. Press the blue locking button. The boot media rotates slightly upward.

    2. Rotate the boot media up, slide it out of the socket.

    3. Install the boot media in the replacement System Management module:

      1. Align the edges of the boot media with the socket housing, and then gently push it squarely into the socket.

      2. Rotate the boot media down toward until it engages the locking button. Depress the blue locking if necessary.

  9. Install the system management module:

    1. Align the edges of the replacement System Management module with the system opening and gently push it into the controller module.

    2. Gently slide the module into the slot until the cam latch begins to engage with the I/O cam pin, and then rotate the cam latch all the way up to lock the module in place.

  10. Recable the System Management module.

  11. Plug the power cords into the power supplies. The controller reboots as soon as power is restored.

    Note If you have DC power supplies, reconnect the power block to the power supplies.

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

Step 3: Reboot the controller

Reboot the controller module.

Steps

  1. Enter bye at the LOADER prompt.

  2. Return the controller to normal operation by giving back its storage:

    storage failover giveback -ofnode impaired_node_name

  3. Restore automatic giveback:

    storage failover modify -node local -auto-giveback true

  4. If an AutoSupport maintenance window was triggered, end it:

    system node autosupport invoke -node * -type all -message MAINT=END

Step 4: Install licenses and register serial number

You must install new licenses for the node if the impaired node was using ONTAP features that require a standard (node-locked) license. For features with standard licenses, each node in the cluster should have its own key for the feature.

About this task

Until you install license keys, features requiring standard licenses continue to be available to the node. However, if the node was the only node in the cluster with a license for the feature, no configuration changes to the feature are allowed. Also, using unlicensed features on the node might put you out of compliance with your license agreement, so you should install the replacement license key or keys on the for the node as soon as possible.

Before you begin

The licenses keys must be in the 28-character format.

You have a 90-day grace period in which to install the license keys. After the grace period, all old licenses are invalidated. After a valid license key is installed, you have 24 hours to install all of the keys before the grace period ends.

Note If your system was initially running ONTAP 9.10.1 or later, use the procedure documented in Post Motherboard Replacement Process to update Licensing on a AFF/FAS system. If you are unsure of the initial ONTAP release for your system, see NetApp Hardware Universe for more information.
Steps

  1. If you need new license keys, obtain replacement license keys on the NetApp Support Site in the My Support section under Software licenses.

    Note The new license keys that you require are automatically generated and sent to the email address on file. If you fail to receive the email with the license keys within 30 days, you should contact technical support.

  2. Install each license key: system license add -license-code license-key, license-key...

  3. Remove the old licenses, if desired:

    1. Check for unused licenses: license clean-up -unused -simulate

    2. If the list looks correct, remove the unused licenses: license clean-up -unused

  4. Register the system serial number with NetApp Support.

    • If AutoSupport is enabled, send an AutoSupport message to register the serial number.

    • If AutoSupport is not enabled, call NetApp Support to register the serial number.

Step 5: 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.