NetApp AFF A150 - Page 542

4. Set the I/O module aside.
5. Install the replacement I/O module into the chassis by gently sliding 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, and then push the I/O cam
latch all the way up to lock the module in place.
6. Recable the I/O module, as needed.
Step 3: Reboot the controller after I/O module replacement
After you replace an I/O module, you must reboot the controller module.
If the new I/O module is not the same model as the failed module, you must first reboot the
BMC.
Steps
1. Reboot the BMC if the replacement module is not the same model as the old module:
a.
From the LOADER prompt, change to advanced privilege mode: priv set advanced
b.
Reboot the BMC:
sp reboot
2.
From the LOADER prompt, reboot the node:
bye
This reinitializes the PCIe cards and other components and reboots the node.
3. If your system is configured to support 10 GbE cluster interconnect and data connections on 40 GbE NICs
or onboard ports, convert these ports to 10 GbE connections by using the
nicadmin convert command
from Maintenance mode.
Be sure to exit Maintenance mode after completing the conversion.
4.
Return the node to normal operation:
storage failover giveback -ofnode impaired_node_name
5.
If automatic giveback was disabled, reenable it:
storage failover modify -node local -auto
-giveback true
If your system is in a two-node MetroCluster configuration, you must switch back the
aggregates as described in the next step.
Step 4: Switch back aggregates in a two-node MetroCluster configuration
After you have completed the FRU replacement in a two-node MetroCluster configuration, you can perform the
MetroCluster switchback operation. This returns the configuration to its normal operating state, with the sync-
source storage virtual machines (SVMs) on the formerly impaired site now active and serving data from the
local disk pools.
This task only applies to two-node MetroCluster configurations.
Steps
1.
Verify that all nodes are in the
enabled state: metrocluster node show
540