Skip to main content
Install and maintain

Add I/O module - AFF A70, AFF A90

Contributors dougthomp netapp-jsnyder
PDFs

You can add an I/O module to your storage system by either adding a new I/O module into a storage system with empty slots or by replacing an I/O module with a new one in a fully-populated storage system.

Before you begin

  • Check the NetApp Hardware Universe to make sure that the new I/O module is compatible with your storage system and version of ONTAP you're running.

  • If multiple slots are available, check the slot priorities in NetApp Hardware Universe and use the best one available for your I/O module.

  • Make sure that all other components are functioning properly.

Option 1: Add an I/O module to a storage system with empty slots

You can add an I/O module into an empty module slot in your storage system.

Step 1: Shut down the impaired controller module

Shut down or take over the impaired controller module 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 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: Controller is in a MetroCluster
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: Add I/O modules

  1. On the front of the chassis, use your thumbs to firmly push each drive in until you feel a positive stop. This ensures that the drives are firmly seated against the chassis midplane.

    Note Make sure NVRAM destage has completed before proceeding.
    drw a800 drive seated IEOPS 960

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

  3. Disconnect power by pulling the controller module out about three inches:

    1. Press down on both of the locking latches, and then rotate both latches downward at the same time.

    2. Pull the controller module about 3 inches out of the chassis to disengage power.

  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. Remove the target slot blanking module from the chassis:

    Note This following illustration shows removing a horizontal and vertical I/O module. Typically, you will only remove one I/O module.
    Remove an I/O module

    Callout number 1

    Cam locking button

    1. Depress the cam latch on the blanking module in the target slot.

    2. Rotate the cam latch down as far as it will go. For horizontal modules, rotate the cam away from the module as far as it will go.

    3. Remove the blanking module.

  6. Install the I/O module:

    1. Align the I/O module with the edges of the controller module slot opening.

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

  7. Cable the I/O module.

    If the I/O module is a NIC, cable the module to the data switches.

    If the I/O module is a storage module, cable it to the NS224 shelf.

    Note Make sure that any unused I/O slots have blanks installed to prevent possible thermal issues.

  8. Reinstall the controller module into the chassis.

    Note If you have DC PSUs, reconnect the cable blocks to the PSUs.

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

  10. Reboot the controller from the LOADER prompt: bye

    Note This reinitializes the PCIe cards and other components and reboots the node.

  11. Give back the controller from the partner controller: storage failover giveback -ofnode target_node_name

  12. Repeat these steps for controller B.

  13. Restore automatic giveback if you disabled it by using the storage failover modify -node local -auto-giveback true command.

  14. If AutoSupport is enabled, restore/unsuppress automatic case creation by using the system node autosupport invoke -node * -type all -message MAINT=END command.

  15. If you installed a storage I/O module, install and cable your NS224 shelves, as described in Hot-adds a shelf.

Option 2: Add an I/O module in a storage system with no empty slots

You can change an I/O module in an I/O slot in a fully-populated system by removing an existing I/O module and replacing it with a different I/O module.

  1. If you are:

    Replacing a…​ Then…​

    NIC I/O module with the same the same number of ports

    The LIFs will automatically migrate when its controller module is shut down.

    NIC I/O module with fewer ports

    Permanently reassign the ASAected LIFs to a different home port. See Migrating a LIF for information about using System Manager to permanently move the LIFs.

    NIC I/O module with a storage I/O module

    Use System Manager to permanently migrate the LIFs to different home ports, as described in Migrating a LIF.

Step 1: Shut down the impaired controller module

Shut down or take over the impaired controller module 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 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: Controller is in a MetroCluster
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 an I/O module

To replace an I/O module, locate it within the controller module and follow the specific sequence of steps.

  1. On the front of the chassis, use your thumbs to firmly push each drive in until you feel a positive stop. This ensures that the drives are firmly seated against the chassis midplane.

    drw a800 drive seated IEOPS 960

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

  3. Disconnect power by pulling the controller module out about three inches:

    Note If your storage system has DC power supplies, disconnect the power cable block from the PSU.

    1. Press down on both of the locking latches, and then rotate both latches downward at the same time.

    2. Pull the controller module about 3 inches out of the chassis to disengage power.

  4. Unplug any cabling on the target I/O module.

  5. Rotate the cable management tray down by pulling the buttons on the inside of the cable management tray and rotating it down.

  6. Remove the target I/O module from the chassis:

    Note This following illustration shows removing a horizontal and vertical I/O module. Typically, you will only remove one I/O module.
    Remove an I/O module

    Callout number 1

    Cam locking button

    1. Depress the cam latch button.

      The cam latch moves away from the chassis.

    2. Rotate the cam latch down as far as it will go. For horizontal modules, rotate the cam away from the module as far as it will go.

    3. Remove the module from the chassis by hooking your finger into the cam lever opening and pulling the module out of the chassis.

      Make sure that you keep track of which slot the I/O module was in.

  7. Install the I/O module into the target slot:

    1. Align the I/O module with the edges of the slot.

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

  8. Cable the I/O module.

  9. Repeat the remove and install steps to replace additional modules for the controller module.

  10. Reinstall the controller module into the chassis.

    Note If you have DC PSUs, reconnect the cable blocks to the PSUs.

  11. Rotate the cable management tray into the locked position.

  12. Reboot the controller module from the LOADER prompt:_bye_

    1. Check the version of BMC on the controller: system service-processor show

    2. Update the BMC firmware if needed: system service-processor image update

    3. Reboot the node: bye

      Note This reinitializes the PCIe cards and other components and reboots the node.
      Note If you encounter an issue during reboot, see BURT 1494308 - Environment shutdown might be triggered during I/O module replacement

  13. Give back the controller module from the partner controller module. storage failover giveback -ofnode target_node_name

  14. Enable automatic giveback if it was disabled: storage failover modify -node local -auto-giveback true

  15. If you added:

    If I/O module is a…​ Then…​

    NIC module

    Use the storage port modify -node *<node name> -port *<port name> -mode network command for each port.

    Storage module

    Install and cable your NS224 shelves, as described in Hot-add a shelf.

  16. Repeat these steps for controller B.