If your system is in… Then…

A stand-alone configuration a. Exit Maintenance mode:

halt

b. Go to "Completing the replacement process.

An HA pair with a second Exit Maintenance mode:

controller module halt

The LOADER prompt appears.

Step 2: Run system-level diagnostics

After installing a new chassis, you should run interconnect diagnostics.

Your system must be at the LOADER prompt to start System Level Diagnostics.

All commands in the diagnostic procedures are issued from the controller where the component is being
replaced.

1. If the controller to be serviced is not at the LOADER prompt, perform the following steps:
a. Select the Maintenance mode option from the displayed menu.
b. After the controller boots to Maintenance mode, halt the controller:

halt

After you issue the command, you should wait until the system stops at the LOADER prompt.

During the boot process, you can safely respond y to prompts:

2. Repeat the previous step on the second controller if you are in an HA configuration.

Both controllers must be in Maintenance mode to run the interconnect test.

3. At the LOADER prompt, access the special drivers specifically designed for system-level diagnostics to
function properly:

boot_diags

During the boot process, you can safely respond y to the prompts until the Maintenance mode prompt (*>)
appears.

4. Enable the interconnect diagnostics tests from the Maintenance mode prompt:

sldiag device modify -dev interconnect -sel enable

The interconnect tests are disabled by default and must be enabled to run separately.

38
5. Run the interconnect diagnostics test from the Maintenance mode prompt:

sldiag device run -dev interconnect

You only need to run the interconnect test from one controller.

6. Verify that no hardware problems resulted from the replacement of the chassis:

sldiag device status -dev interconnect -long -state failed

System-level diagnostics returns you to the prompt if there are no test failures, or lists the full status of
failures resulting from testing the component.

7. Proceed based on the result of the preceding step.

If the system-level diagnostics Then…

tests…
Were completed without any a. Clear the status logs:
failures
sldiag device clearstatus

b. Verify that the log was cleared:

sldiag device status

The following default response is displayed:

SLDIAG: No log messages are present.

c. Exit Maintenance mode on both controllers:

halt

The system displays the LOADER prompt.

You must exit Maintenance mode on both

controllers before proceeding any further.

d. Enter the following command on both controllers at the LOADER

prompt:

bye

e. Return the controller to normal operation:

39
 If your system is running Then…
ONTAP…
With two nodes in the cluster Issue these commands:

node::> cluster ha modify -configured true

node::> storage failover modify -node node0

-enabled true

With more than two nodes in the Issue this command:

cluster
node::> storage failover modify -node node0
-enabled true

In a stand-alone configuration You have no further steps in this particular task.

You have completed system-level diagnostics.

Resulted in some test failures Determine the cause of the problem.

a. Exit Maintenance mode:

halt

b. Perform a clean shutdown, and then disconnect the power

supplies.
c. Verify that you have observed all of the considerations identified
for running system-level diagnostics, that cables are securely
connected, and that hardware components are properly installed
in the storage system.
d. Reconnect the power supplies, and then power on the storage
system.
e. Rerun the system-level diagnostics test.

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

Controller

Overview of controller module replacement - AFF C190

You must review the prerequisites for the replacement procedure and select the correct
one for your version of the ONTAP operating system.
• All drive shelves must be working properly.
• If your system is in an HA pair, the healthy controller must be able to take over the controller that is being
replaced (referred to in this procedure as the “impaired controller”).

40
 • This procedure includes steps for automatically or manually reassigning drives to the replacement
controller, depending on your system’s configuration.
• You should perform the drive reassignment as directed in the procedure.
• You must replace the failed component with a replacement FRU component you received from your
provider.
• You must be replacing a controller module with a controller module of the same model type. You cannot
upgrade your system by just replacing the controller module.
• You cannot change any drives or drive shelves as part of this procedure.
• In this procedure, the boot device is moved from the impaired controller to the replacement controller so
that the replacement controller will boot up in the same version of ONTAP as the old controller module.
• It is important that you apply the commands in these steps on the correct systems:
◦ The impaired controller is the controller that is being replaced.
◦ The replacement controller is the new controller that is replacing the impaired controller.
◦ The healthy controller is the surviving controller.
• You must always capture the controller’s console output to a text file.

This provides you a record of the procedure so that you can troubleshoot any issues that you might
encounter during the replacement process.

Shut down the controller - AFF C190

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.

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_down_h

The following AutoSupport message suppresses automatic case creation for two hours: cluster1:*>
system node autosupport invoke -node * -type all -message MAINT=2h

2. If the impaired controller is part of an HA pair, 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 Then…

displaying…
The LOADER prompt Go to Remove controller module..

41
 If the impaired controller is Then…
displaying…
Waiting for giveback… Press Ctrl-C, and then respond y.

System prompt or password Take over or halt the impaired controller from the healthy controller:
prompt (enter system password) storage failover takeover -ofnode
impaired_node_name

When the impaired controller shows Waiting for giveback…, press

Ctrl-C, and then respond y.

Replace the controller module hardware - AFF C190

To replace the controller module, you must remove the impaired controller, move FRU
components to the replacement controller module, install the replacement controller
module in the chassis, and then boot the system to Maintenance mode.

Step 1: Remove controller module

To replace the controller module, you must first remove the old controller module from the chassis.

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

2. Loosen the hook and loop strap binding the cables to the cable management device, and then unplug the
system cables and SFPs (if needed) from the controller module, keeping track of where the cables were
connected.

Leave the cables in the cable management device so that when you reinstall the cable management
device, the cables are organized.

3. Remove and set aside the cable management devices from the left and right sides of the controller module.

4. If you left the SFP modules in the system after removing the cables, move them to the new controller
module.
5. Squeeze the latch on the cam handle until it releases, open the cam handle fully to release the controller
module from the midplane, and then, using two hands, pull the controller module out of the chassis.

42
 6. Turn the controller module over and place it on a flat, stable surface.
7. Open the cover by sliding in the blue tabs to release the cover, and then swing the cover up and open.

Step 2: Move the boot media

You must locate the boot media and follow the directions to remove it from the old controller module and insert
it in the new controller module.

43
 1. Locate the boot media using the following illustration or the FRU map on the controller module:

2. Press the blue button on the boot media housing to release the boot media from its housing, and then
gently pull it straight out of the boot media socket.

Do not twist or pull the boot media straight up, because this could damage the socket or the
boot media.

3. Move the boot media to the new controller module, align the edges of the boot media with the socket
housing, and then gently push it into the socket.
4. Check the boot media to make sure that it is seated squarely and completely in the socket.

If necessary, remove the boot media and reseat it into the socket.

5. Push the boot media down to engage the locking button on the boot media housing.

Step 3: Move the NVMEM battery

To move the NVMEM battery from the old controller module to the new controller module, you must perform a
specific sequence of steps.

1. Check the NVMEM LED:

◦ If your system is in an HA configuration, go to the next step.
◦ If your system is in a stand-alone configuration, cleanly shut down the controller module, and then
check the NVRAM LED identified by the NV icon.

44
 The NVRAM LED blinks while destaging contents to the flash memory when you halt the
system. After the destage is complete, the LED turns off.

▪ If power is lost without a clean shutdown, the NVMEM LED flashes until the destage is complete,
and then the LED turns off.
▪ If the LED is on and power is on, unwritten data is stored on NVMEM.

This typically occurs during an uncontrolled shutdown after ONTAP has successfully booted.

2. Locate the NVMEM battery in the controller module.

3. Locate the battery plug and squeeze the clip on the face of the battery plug to release the plug from the
socket, and then unplug the battery cable from the socket.
4. Grasp the battery and press the blue locking tab marked PUSH, and then lift the battery out of the holder
and controller module.
5. Move the battery to the replacement controller module.
6. Loop the battery cable around the cable channel on the side of the battery holder.
7. Position the battery pack by aligning the battery holder key ribs to the “V” notches on the sheet metal side
wall.
8. Slide the battery pack down along the sheet metal side wall until the support tabs on the side wall hook into
the slots on the battery pack, and the battery pack latch engages and clicks into the opening on the side
wall.

Step 4: Move the DIMMs

To move the DIMMs, you must follow the directions to locate and move them from the old controller module
into the replacement controller module.

45
You must have the new controller module ready so that you can move the DIMMs directly from the impaired
controller module to the corresponding slots in the replacement controller module.

1. Locate the DIMMs on your controller module.

2. Note the orientation of the DIMM in the socket so that you can insert the DIMM in the replacement
controller module in the proper orientation.
3. Eject the DIMM from its slot by slowly pushing apart the two DIMM ejector tabs on either side of the DIMM,
and then slide the DIMM out of the slot.

Carefully hold the DIMM by the edges to avoid pressure on the components on the DIMM
circuit board.

The number and placement of system DIMMs depends on the model of your system.

The following illustration shows the location of system DIMMs:

4. Repeat these steps to remove additional DIMMs as needed.

5. Verify that the NVMEM battery is not plugged into the new controller module.
6. Locate the slot where you are installing the DIMM.
7. Make sure that the DIMM ejector tabs on the connector are in the open position, and then insert the DIMM
squarely into the slot.

The DIMM fits tightly in the slot, but should go in easily. If not, realign the DIMM with the slot and reinsert it.

Visually inspect the DIMM to verify that it is evenly aligned and fully inserted into the slot.

8. Repeat these steps for the remaining DIMMs.

9. Locate the NVMEM battery plug socket, and then squeeze the clip on the face of the battery cable plug to
insert it into the socket.

46
 Make sure that the plug locks down onto the controller module.

Step 5: Install the controller module

After you install the components from the old controller module into the new controller module, you must install
the new controller module into the system chassis and boot the operating system.

For HA pairs with two controller modules in the same chassis, the sequence in which you install the controller
module is especially important because it attempts to reboot as soon as you completely seat it in the chassis.

The system might update system firmware when it boots. Do not abort this process. The
procedure requires you to interrupt the boot process, which you can typically do at any time after
prompted to do so. However, if the system updates the system firmware when it boots, you must
wait until after the update is complete before interrupting the boot process.

1. If you have not already done so, replace the cover on the controller module.
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. Cable the management and console ports only, so that you can access the system to perform the tasks in
the following sections.

You will connect the rest of the cables to the controller module later in this procedure.

4. Complete the reinstallation of the controller module. The controller module begins to boot as soon as it is
fully seated in the chassis. Be prepared to interrupt the boot process.
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.

The controller begins to boot as soon as it is seated in the chassis.

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. Interrupt the boot process only after determining the correct timing:

You must look for an Automatic firmware update console message. If the update message appears, do
not press Ctrl-C to interrupt the boot process until after you see a message confirming that the
update is complete.

Only press Ctrl-C when you see the message Press Ctrl-C for Boot Menu.

If the firmware update is aborted, the boot process exits to the LOADER prompt. You
must run the update_flash command and then exit LOADER and boot to Maintenance
mode by pressing Ctrl-C when you see Starting AUTOBOOT press Ctrl-C to abort.

47