Skip to main content
Install and maintain

Add an I/O module - AFF C30 and AFF C60

Contributors netapp-lisa netapp-jsnyder
PDFs

Add an I/O module to your AFF C30 or AFF C60 storage system to enhance network connectivity and expand your system’s ability to handle data traffic.

You can add an I/O module to your AFF C30 and AFF C60 storage systems when there are slots available or when all slots are fully populated.

About this task

If needed, you can turn on the storage system location (blue) LEDs to aid in physically locating the affected storage system. Log into the BMC using SSH and enter the system location-led on command.

A storage system has three location LEDs: one on the operator display panel and one on each controller. Location LEDs remain illuminated for 30 minutes.

You can turn them off by entering the system location-led off command. If you are unsure if the LEDs are on or off, you can check their state by entering the system location-led show command.

Step 1: Shut down the impaired controller module

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

  • 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: Add the new I/O module

If the storage system has available slots, install the new I/O module into one of the available slots. If all slots are occupied, remove an existing I/O module to make space and then install the new one.

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.

  • All other components in the storage system must be functioning properly; if not, contact NetApp Support before continuing with this procedure.

Add I/O module to an available slot

You can add a new I/O module into a storage system with available slots.

Steps

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

  2. On the impaired controller, remove the I/O blanking module from the target slot.

    Unused I/O slots should have blanking module installed to prevent possible thermal issues and for EMC compliance.

    Remove an I/O blanking module

    Callout number 1

    On the I/O blanking module, turn the thumbscrew counterclockwise to loosen.

    Callout number 2

    Pull the I/O blanking module out of the controller using the tab on the left and the thumbscrew.

  3. Install the new I/O module:

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

    2. Gently push the I/O module all the way into the slot, making sure to properly seat the module into the connector.

      You can use the tab on the left and the thumbscrew to push in the I/O module.

    3. Turn the thumbscrew clockwise to tighten.

  4. Cable the I/O module to the designated devices.

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

  5. Reboot the impaired controller from the LOADER prompt: bye

    Rebooting the impaired controller also reinitializes the I/O modules and other components.

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

    storage failover giveback -ofnode impaired_node_name.

  7. Repeat these steps to add an I/O module to the other controller.

  8. Restore automatic giveback from the console of the healthy controller:

    storage failover modify -node local -auto-giveback true

  9. If AutoSupport is enabled, restore (unsuppress) automatic case creation:

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

Add I/O module to a fully-populated system

You can add an I/O module to a fully-populated system by removing an existing I/O module and installing a new one in its place.

About this task

Make sure you understand the following scenarios for adding a new I/O module to a fully-populated system:

Scenario Action required

NIC to NIC (same number of ports)

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

NIC to NIC (different number of ports)

Permanently reassign the selected LIFs to a different home port. See Migrating a LIF for more information.

NIC to storage I/O module

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

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

  2. On the impaired controller, unplug any cabling on the target I/O module.

  3. Remove the target I/O module from the controller:

    Remove an I/O module

    Callout number 1

    Turn the I/O module thumbscrew counterclockwise to loosen.

    Callout number 2

    Pull the I/O module out of the controller using the port label tab on the left and the thumbscrew.

  4. Install the new I/O module into the target slot:

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

    2. Gently push the I/O module all the way into the slot, making sure to properly seat the module into the connector.

      You can use the tab on the left and the thumbscrew to push in the I/O Module.

    3. Turn the thumbscrew clockwise to tighten.

  5. Cable the I/O module to the designated devices.

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

  6. Repeat the I/O module remove and install steps to add any additional I/O modules in the controller.

  7. Reboot the impaired controller from the LOADER prompt:

    bye

    Rebooting the impaired controller also reinitializes the I/O modules and other components.

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

    storage failover giveback -ofnode impaired_node_name

  9. Restore automatic giveback from the console of the healthy controller:

    storage failover modify -node local -auto-giveback true

  10. If AutoSupport is enabled, restore (unsuppress) automatic case creation:

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

  11. If you installed a NIC module, specify the usage mode for each port as network:

    storage port modify -node node_name -port port_name -mode network

  12. Repeat these steps for the other controller.