Skip to main content
Install and maintain

Replace system management module - AFX 1K

Contributors netapp-driley netapp-jsnyder
PDFs

Replace the System Management module in your AFX 1K storage 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 to the left of slot 8, contains onboard components for system management, as well as ports for external management. The target controller must be shut down and powered off to replace an impaired System Management module or replace the boot media.

The System Management module has the following onboard components:

  • Boot media, allowing boot media replacement without removing the controller module.

  • BMC

  • Management switch

The System Management module also contains the following ports for external management:

  • RJ45 Serial

  • USB Serial (Type-C)

  • USB Type-A (Boot recovery)

  • RJ45 Ethernet service port for e0M and BMC network access

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.

To shut down the impaired controller, you must determine the status of the controller and, if necessary, perform a storage failover takeover of 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 four nodes, it must be in quorum. To view cluster information about your nodes, use the cluster show command. For more information about the cluster show command, see View node-level details in an ONTAP cluster.

  • If the cluster is not in quorum or if the health or eligibility of any controller (other than the impaired controller) shows as false, 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 from the console of the impaired controller:

    storage failover modify -node impaired-node -auto-giveback-of false

    Note When you see Do you want to disable auto-giveback?, enter y.

    1. If you are running ONTAP version 9.17.1 and the impaired controller cannot be brought up or is already taken over, you must take the HA interconnect link down from the healthy controller before booting up the impaired controller. This prevents the impaired controller from performing automatic giveback.

      system ha interconnect link off -node healthy-node -link 0

      system ha interconnect link off -node healthy-node -link 1

      Note If you are not running ONTAP version 9.17.1, skip the above step and go to step 3.

  3. Take the impaired controller to the LOADER prompt:

    If the impaired controller is displaying…​ Then…​

    The LOADER prompt

    Go to the next step.

    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 the impaired node to the LOADER prompt.

Step 2: Replace the impaired System Management module

Replace the impaired system management module.

  1. Remove the System Management module:

    Note 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.
    Replace the System Management module
    Callout number 1

    System Management module cam latch

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

    2. Unplug the power supply cables from the PSUs.

    3. Remove any cables connected to the System Management module. Label the cables where they were connected, so you can reconnect them to the correct ports when reinstalling the module.

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

    5. Depress the cam button on the System Management module.

    6. Rotate the cam lever down as far as it will go.

    7. Loop your finger into the hole on the cam lever and pull the module straight out of the system.

    8. Place the System Management module on an anti-static mat to access the boot media.

  2. 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 boot media locking button in the impaired System Management module.

    2. Rotate the boot media up and 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 until it touches the locking button.

    3. Depress the blue locking and rotate the boot media all the way down and release the blue locking button.

  4. Install the replacement System Management module into the enclosure:

    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.

  5. Rotate the cable management arm up to the closed position.

  6. Recable the System Management module.

Step 3: Reboot the controller module

Reboot the controller module.

  1. Plug the power cables back into the PSU.

    The system reboots, typically to the LOADER prompt.

  2. Enter bye at the LOADER prompt.

  3. Press <enter> when console messages stop.

    • If you see the login prompt, go to the next step.

    • If you do not see login prompt, log into the partner node.

  4. Give back only the root with override-destination-checks option:

    storage failover giveback -ofnode impaired-node -only-root true -override -destination-checks true

    Note The following command is only available in the Diagnostic mode privilege level. For more information on privilege levels, see Understand the privilege levels for ONTAP CLI commands.

    If you encounter errors, contact NetApp Support.

  5. Wait 5 minutes after the giveback report completes, then check the failover and giveback statuses:

    storage failover show and storage failover show-giveback

    Note The following command is only available in the Diagnostic mode privilege level.

  6. If the HA internconnect links were taken down, bring them back up:

    system ha interconnect link on -node healthy-node -link 0

    system ha interconnect link on -node healthy-node -link 1

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

    storage failover giveback -ofnode impaired_node_name

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

  9. If AutoSupport is enabled, restore/unsuppress automatic case creation: system node autosupport invoke -node * -type all -message MAINT=END.

Step 4: Install licenses and register serial number

When you replace the system management module, the controller's system serial number (SSN) changes. 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

A NetApp License File (NLF) for the new system serial number is required. For more information on NetApp License Files, see ONTAP 9.10.1 and later licensing overview.

You have 90 days to install the license keys, after which all old licenses become invalid. After you install a valid license key, you have 24 hours to install all of the keys before the grace period ends.

Note If your system was initially running ONTAP 9.15.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 through ONTAP System Manager.

    For more information, see Enable new features by adding license keys with ONTAP System Manager.

  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.