Skip to main content
Install and maintain

Add an I/O module - ASA A900

Contributors netapp-jsnyder
PDFs

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

Before you begin

  • Check the NetApp Hardware Universe to make sure that the new I/O module is compatible with your 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.

  • To non-disruptively add an I/O module, you must take over the target controller, remove the slot blanking cover in the target slot or remove an existing I/O module, add the new or replacement I/O module, and then giveback the target controller.

  • Make sure that all other components are functioning properly.

Option 1: Add the I/O module to a system with open slots

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

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.

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. If you are not already grounded, properly ground yourself.

  2. Remove the target slot blanking cover:

    1. Depress the lettered and numbered cam latch.

    2. Rotate the cam latch down until it is the open position.

    3. Remove the blanking cover.

  3. Install the I/O module:

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

    2. Slide the I/O module into the slot until the lettered and numbered I/O cam latch begins to engage with the I/O cam pin.

    3. Push the I/O cam latch all the way up to lock the module in place.

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

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

  5. Reboot the controller from the LOADER prompt: bye

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

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

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

  8. If you are using slots 3 and/or 7 for networking, use the storage port modify -node <node name> -port <port name> -mode network command to convert the slot for networking use.

  9. Repeat these steps for controller B.

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

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

If your system is fully populated, you can change an I/O module in an I/O slot 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 affected 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 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.

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 I/O modules

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

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

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

    1. Depress the lettered and numbered cam latch.

      The cam latch moves away from the chassis.

    2. Rotate the cam latch down until it is in a horizontal position.

      The I/O module disengages from the chassis and moves about 1/2 inch out of the I/O slot.

    3. Remove the I/O module from the chassis by pulling on the pull tabs on the sides of the module face.

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

      Animation - Remove or replacing an I/O module

      Removing a PCIe module

      Callout number 1

      Lettered and numbered I/O cam latch

      Callout number 2

      I/O cam latch completely unlocked

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

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

    2. Slide the I/O module into the slot until the lettered and numbered I/O cam latch begins to engage with the I/O cam pin.

    3. Push the I/O cam latch all the way up to lock the module in place.

  5. Repeat the remove and install steps to replace additional modules for controller A.

  6. If the replacement I/O module is a NIC, cable the module or modules to the data switches.

  7. Reboot the controller from the LOADER prompt:

    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

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

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

  10. If you added:

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

    NIC module in slots 3 or 7,

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

  11. Repeat these steps for controller B.