controller_A_1::> metrocluster operation show

Operation: heal-aggregates
State: successful
Start Time: 7/25/2016 18:45:55
End Time: 7/25/2016 18:45:56
Errors: -

5. Check the state of the aggregates by using the storage aggregate show command.

controller_A_1::> storage aggregate show

Aggregate Size Available Used% State #Vols Nodes
RAID Status
--------- -------- --------- ----- ------- ------ ----------------
------------
...
aggr_b2 227.1GB 227.1GB 0% online 0 mcc1-a2
raid_dp, mirrored, normal...

6. Heal the root aggregates by using the metrocluster heal -phase root-aggregates
command.

mcc1A::> metrocluster heal -phase root-aggregates

[Job 137] Job succeeded: Heal Root Aggregates is successful

If the healing is vetoed, you have the option of reissuing the metrocluster heal command with
the -override-vetoes parameter. If you use this optional parameter, the system overrides any soft
vetoes that prevent the healing operation.

7. Verify that the heal operation is complete by using the metrocluster operation show command
on the destination cluster:

mcc1A::> metrocluster operation show

Operation: heal-root-aggregates
State: successful
Start Time: 7/29/2016 20:54:41
End Time: 7/29/2016 20:54:42
Errors: -

8. On the impaired controller module, disconnect the power supplies.

798
Step 2: Remove the controller module

To access components inside the controller, you must first remove the controller module
from the system and then remove the cover on the controller module.
Steps
1. If you are not already grounded, properly ground yourself.
2. Unplug the cables from the impaired controller module, and keep track of where the cables were
connected.
3. Slide the orange button on the cam handle downward until it unlocks.

Cam handle release button

Cam handle

4. Rotate the cam handle so that it completely disengages the controller module from the chassis, and then
slide the controller module out of the chassis.

799
 Make sure that you support the bottom of the controller module as you slide it out of the chassis.

5. Place the controller module lid-side up on a stable, flat surface, press the blue button on the cover, slide
the cover to the back of the controller module, and then swing the cover up and lift it off of the controller
module.

Controller module cover locking button

Step 3: Replace the RTC battery

To replace the RTC battery, you must locate the failed battery in the controller module,
remove it from the holder, and then install the replacement battery in the holder.
Steps
1. If you are not already grounded, properly ground yourself.
2. Locate the RTC battery.

800
 RTC battery

RTC battery housing

3. Gently push the battery away from the holder, rotate it away from the holder, and then lift it out of the
holder.

Note the polarity of the battery as you remove it from the holder. The battery is marked with
a plus sign and must be positioned in the holder correctly. A plus sign near the holder tells
you how the battery should be positioned.

4. Remove the replacement battery from the antistatic shipping bag.

5. Locate the empty battery holder in the controller module.
6. Note the polarity of the RTC battery, and then insert it into the holder by tilting the battery at an angle and
pushing down.
7. Visually inspect the battery to make sure that it is completely installed into the holder and that the polarity is
correct.
8. Reinstall the controller module cover.

Step 4: Reinstall the controller module and set time/date

After you replace a component within the controller module, you must reinstall the
controller module in the system chassis, reset the time and date on the controller, and
then boot it.

801
Steps
1. If you have not already done so, close the air duct or controller module cover.
2. Align the end of the controller module with the opening in the chassis, and then gently push the controller
module halfway into the system.

Do not completely insert the controller module in the chassis until instructed to do so.

3. Recable the system, as needed.

If you removed the media converters (QSFPs or SFPs), remember to reinstall them if you are using fiber
optic cables.

4. If the power supplies were unplugged, plug them back in and reinstall the power cable retainers.
5. Complete the reinstallation of the controller module:
a. With the cam handle in the open position, firmly push the controller module in until it meets the
midplane and is fully seated, and then close the cam handle to the locked position.

Do not use excessive force when sliding the controller module into the chassis to avoid
damaging the connectors.

b. If you have not already done so, reinstall the cable management device.
c. Bind the cables to the cable management device with the hook and loop strap.
d. Reconnect the power cables to the power supplies and to the power sources, and then turn on the
power to start the boot process.
e. Halt the controller at the LOADER prompt.
6. Reset the time and date on the controller:
a. Check the date and time on the healthy node with the show date command.
b. At the LOADER prompt on the target node, check the time and date.
c. If necessary, modify the date with the set date mm/dd/yyyy command.
d. If necessary, set the time, in GMT, using the set time hh:mm:ss command.
e. Confirm the date and time on the target node.
7. At the LOADER prompt, enter bye to reinitialize the PCIe cards and other components and let the node
reboot.
8. Return the node to normal operation by giving back its storage: storage failover giveback
-ofnode impaired_node_name
9. If automatic giveback was disabled, reenable it: storage failover modify -node local -auto
-giveback true

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

802
Steps
1. Verify that all nodes are in the enabled state: metrocluster node show

cluster_B::> metrocluster node show

DR Configuration DR
Group Cluster Node State Mirroring Mode
----- ------- -------------- -------------- ---------
--------------------
1 cluster_A
controller_A_1 configured enabled heal roots
completed
cluster_B
controller_B_1 configured enabled waiting for
switchback recovery
2 entries were displayed.

2. Verify that resynchronization is complete on all SVMs: metrocluster vserver show

3. Verify that any automatic LIF migrations being performed by the healing operations were completed
successfully: metrocluster check lif show
4. Perform the switchback by using the metrocluster switchback command from any node in the
surviving cluster.
5. Verify that the switchback operation has completed: metrocluster show

The switchback operation is still running when a cluster is in the waiting-for-switchback state:

cluster_B::> metrocluster show

Cluster Configuration State Mode
-------------------- ------------------- ---------
Local: cluster_B configured switchover
Remote: cluster_A configured waiting-for-switchback

The switchback operation is complete when the clusters are in the normal state.:

cluster_B::> metrocluster show

Cluster Configuration State Mode
-------------------- ------------------- ---------
Local: cluster_B configured normal
Remote: cluster_A configured normal

If a switchback is taking a long time to finish, you can check on the status of in-progress baselines by using
the metrocluster config-replication resync-status show command.

803
 6. Reestablish any SnapMirror or SnapVault configurations.

Step 6: 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
& Replacements page for further information.

X91148A module

Overview of adding an X91148A module - AFF A9000

You can add an I/O module to your system by either replacing a NIC or storage adapter with a new one in a
fully-populated system, or by adding a new NIC or storage adapter into an empty chassis slot in your 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 takeover 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.

Add an X91148A module in an AFF A700 with open slots - AFF A700 and FAS9000

You can add an X91148A module into an empty module slot in your system as either a
100GbE NIC or a storage module for the NS224 storage shelves.
• Your system must be running ONTAP 9.8 and later.
• To non-disruptively add the X91148A module, you must takeover the target controller, remove the slot
blanking cover in the target slot, add the module, and then giveback the target controller.
• There must be one or more open slots available on your system.
• If multiple slots are available, install the module according to the slot priority matrix for the X91148A module
in the Hardware Universe.

NetApp Hardware Universe

• If you are adding the X91148A module as a storage module, you must install the module slots 3 and/or 7.
• If you are adding the X91148A module as a 100GbE NIC, you can use any open slot. However, by default,
slots 3 and 7 are set as storage slots. If you wish to use those slots as network slots and will not add
NS224 shelves, you must modify the slots for networking use with the storage port modify -node
node name -port port name -mode network command. See the Hardware Universe for other slots
that can be used by the X91148A module for networking.

NetApp Hardware Universe

• All other components in the system must be functioning properly; if not, you must contact technical support.

804
Option 1: Add an X91148A module as a NIC module in a system with open slots

To add an X91148A module as a NIC module in a system with open slots, you must follow
the specific sequence of steps.
Steps
1. Shutdown controller A:
a. Disable automatic giveback: storage failover modify -node local -auto-giveback
false
b. Take over the target node: storage failover takeover -ofnode target_node_name

The console connection shows that the node drops to the LOADER prompt when the takeover is
complete.

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

3. Remove the target slot blanking cover:
a. Depress the lettered and numbered cam button.
b. Rotate the cam latch down until it is in a horizontal position.
c. Remove the blanking cover.
4. Install the X91148A module:
a. Align the X91148A module with the edges of the slot.
b. Slide the X91148A module into the slot until the lettered and numbered I/O cam latch begins to engage
with the I/O cam pin.
c. Push the I/O cam latch all the way up to lock the module in place.
5. Cable the module to the data switches.
6. Reboot controller A: boot_ontap
7. Giveback the node from the partner node: storage failover giveback -ofnode
target_node_name
8. Enable automatic giveback if it was disabled: storage failover modify -node local -auto
-giveback true
9. Repeat these steps for controller B.

Option 2: Add an X91148A module as a storage module in a system with open slots

To add an X91148A module as a storage module in a system with open slots, you must
follow the specific sequence of steps.
• This procedure presumes slots 3 and/or 7 are open.

Steps
1. Shut down controller A:
a. Disable automatic giveback: storage failover modify -node local -auto-giveback
false
b. Take over the target node: storage failover takeover -ofnode target_node_name

805
 The console connection shows that the node drops to the LOADER prompt when the takeover is
complete.

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

3. Remove the target slot blanking cover:
a. Depress the lettered and numbered cam button.
b. Rotate the cam latch down until it is in a horizontal position.
c. Remove the blanking cover.
4. Install the X91148A module into slot 3:
a. Align the X91148A module with the edges of the slot.
b. Slide the X91148A module into the slot until the lettered and numbered I/O cam latch begins to engage
with the I/O cam pin.
c. Push the I/O cam latch all the way up to lock the module in place.
d. If you are installing a second X91148A module for storage, repeat this step for the module in slot 7.
5. Reboot controller A: boot_ontap
6. Giveback the node from the partner node: storage failover giveback -ofnode
target_node_name
7. Enable automatic giveback if it was disabled: storage failover modify -node local -auto
-giveback true
8. Repeat these steps for controller B.
9. Install and cable your NS224 shelves, as described in Hot-add - NS224 shelves.

Add an X91148A storage module in a system with no open slots - AFF A700 and FAS9000

You must remove one more or more existing NIC or storage modules in your system in
order to install one or more X91148A storage modules into your fully-populated system.
• Your system must be running ONTAP 9.8 and later.
• To non-disruptively add the X91148A module, you must takeover the target controller, add the module, and
then giveback the target controller.
• If you are adding the X91148A module as a storage adapter, you must install the module in slots 3 and/or
7.
• If you are adding the X91148A module as a 100GbE NIC, you can use any open slot. However, by default,
slots 3 and 7 are set as storage slots. If you wish to use those slots as network slots and will not add
NS224 shelves, you must modify the slots for networking use with the storage port modify -node
node name -port port name -mode network command for each port. See the Hardware Universe
for other slots that can be used by the X91148A module for networking.

NetApp Hardware Universe

• All other components in the system must be functioning properly; if not, you must contact technical support.

Option 1: Add an X91148A module as a NIC module in a system with no open slots

You must remove one or more existing NIC or storage modules in your system in order to

806
install one or more X91148A NIC modules into your fully-populated system.
Steps
1. If you are adding an X91148A module into a slot that contains a NIC module with the same number of ports
as the X91148A module, the LIFs will automatically migrate when its controller module is shut down. If the
NIC module being replaced has more ports than the X91148A module, you must 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
2. Shut down controller A:
a. Disable automatic giveback: storage failover modify -node local -auto-giveback
false
b. Take over the target node: storage failover takeover -ofnode target_node_name

The console connection shows that the node drops to the LOADER prompt when the takeover is
complete.

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

4. Unplug any cabling on the target I/O module.
5. Remove the target I/O module from the chassis:
a. Depress the lettered and numbered cam button.

The cam button moves away from the chassis.

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

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

807