0% found this document useful (0 votes)

352 views97 pages

AFF C250 Systems

The document provides installation and maintenance instructions for the AFF C250 systems from NetApp, detailing the steps for setup, hardware installation, and cabling configurations. It includes quick, video, and detailed steps for users to follow, as well as specific requirements for hardware and network connections. Users are advised to check the NetApp Hardware Universe for site requirements and cable types necessary for installation.

Uploaded by

A J

We take content rights seriously. If you suspect this is your content, claim it here.

Available Formats

Download as PDF, TXT or read online on Scribd

0% found this document useful (0 votes)

352 views97 pages

AFF C250 Systems

Uploaded by

A J

We take content rights seriously. If you suspect this is your content, claim it here.

Available Formats

Download as PDF, TXT or read online on Scribd

You are on page 1/ 97

AFF C250 systems

Install and maintain

NetApp
March 21, 2025

This PDF was generated from https://docs.netapp.com/us-en/ontap-systems/c250/install-setup.html on

March 21, 2025. Always check docs.netapp.com for the latest.
Table of Contents
AFF C250 systems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
Install and setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
Start here: Choose your installation and setup experience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
Quick steps - AFF C250 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
Video steps - AFF C250 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
Detailed steps - AFF C250 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
Maintain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Maintain AFF C250 hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Boot media . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Chassis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Replace a DIMM - AFF C250 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
Replace SSD drive - AFF C250 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
Replace a fan - AFF C250 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
Replace or install a mezzanine card - AFF C250. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
Replace the NVMEM battery - AFF C250 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
Replace a power supply - AFF C250 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Replace the real-time clock battery - AFF C250 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
AFF C250 systems
Install and setup
Start here: Choose your installation and setup experience
For most configurations, you can choose from different content formats.
• Quick steps

A printable PDF of step-by-step instructions with live links to additional content.

• Video steps

Video step-by-step instructions.

• Detailed steps

Online step-by-step instructions with live links to additional content.

If your system is in a MetroCluster IP configuration, see the Install MetroCluster IP Configuration instructions.

Quick steps - AFF C250

This section gives graphic instructions for a typical installation of your system from
racking and cabling, through initial system bring-up. Use this guide if you are familiar with
installing NetApp systems.
Access the Installation and Setup Instructions PDF poster:

AFF C250 Installation and Setup Instructions

Video steps - AFF C250

The following video shows how to install and cable your new system.
Animation - Installation and Setup of an AFF C250

If you have a MetroCluster configuration, use the MetroCluster installation content.

MetroCluster Documentation

Detailed steps - AFF C250

This procedure gives detailed step-by-step instructions for installing an AFF C250 storage
system.
If you have a MetroCluster configuration, use the MetroCluster Documentation.

1
Step 1: Prepare for installation

To install your AFF C250 system, you need to create an account and register the system. You also need to
inventory the appropriate number and type of cables for your system and collect specific network information.

Before you begin

• Make sure you have access to the NetApp Hardware Universe (HWU) for information about site
requirements.
• Customers with specific power requirements must check HWU for configuration options.
• Make sure you have access to the Release Notes for your version of ONTAP for more information about
this system.
• You need to provide the following at your site:
◦ Rack space for the storage system
◦ Phillips #2 screwdriver
◦ Additional networking cables to connect your system to your network switch and laptop or console with
a Web browser.

Steps
1. Unpack the contents of all boxes.
2. Record the system serial number from the controllers.

3. Set up your account:

a. Log in to your existing account or create an account.
b. Register (NetApp Product Registration) your system.
4. Download and install NetApp Downloads: Config Advisor on your laptop.
5. Inventory and make a note of the number and types of cables you received.

The following table identifies the types of cables you might receive. If you receive a cable not listed in the
table, see the NetApp Hardware Universe to locate the cable and identify its use.

Type of cable… Part number and length Connector type For…

25 GbE cable X66240A-05 (112-00595), 0.5m; Cluster interconnect network

X66240-2 (112-00573), 2m

X66240A-2 (112-00598), 2m; Data

X66240A-5 (112-00600), 5m

100 GbE cable X66211-2 (112-00574), 2m; Storage

X66211-5 (112-00576), 5m

2
Type of cable… Part number and length Connector type For…
RJ-45 (order Not applicable Management network (BMC and
dependent) wrench port) and Ethernet data
(e0a and e0b)

Fibre Channel X66250-2 (112-00342) 2m;

X66250-5 (112-00344) 5m;

X66250-15 (112-00346) 15m;

X66250-30 (112-00347) 30m

Micro-USB Not applicable Console connection during

console cable software setup

Power cables Not applicable Powering up the system

6. Review the ONTAP Configuration Guide and collect the required information listed in that guide.

Step 2: Install the hardware

You need to install your system in a 4-post rack or NetApp system cabinet, as applicable.

Steps
1. Install the rail kits, as needed.
2. Install and secure your system using the instructions included with the rail kit.

You need to be aware of the safety concerns associated with the weight of the system.

3. Identify and manage cables because this system does not have a cable management device.
4. Place the bezel on the front of the system.

Step 3: Cable controllers to cluster

Cable the controllers to a cluster by using the two-node switchless cluster method or by using the cluster
interconnect network.

3
Option 1: Two-node switchless cluster
The management, Fibre Channel, and data or host network ports on the controller modules are
connected to switches. The cluster interconnect ports are cabled on both controller modules.

Before you begin

• Contact your network administrator for information about connecting the system to the switches.
• Be sure to check the illustration arrow for the proper cable connector pull-tab orientation.

As you insert the connector, you should feel it click into place; if you do not feel it click,
remove it, turn it around and try again.

About this task

Use the animation or the tabulated steps to complete the cabling between the controllers and the
switches. Perform the steps on each controller.

Animation - Cable a two-node switchless cluster

Steps
1. Cable the cluster interconnect ports e0c to e0c and e0d to e0d with the 25GbE cluster interconnect
cables.

2. Cable the wrench ports to the management network switches with the RJ45 cables.

4
DO NOT plug in the power cords at this point.

Option 2: Switched cluster

All ports on the controllers are connected to switches; cluster interconnect, management, Fibre Channel,
and data or host network switches.

Before you begin

• Contact your network administrator for information about connecting the system to the switches.
• Be sure to check the illustration arrow for the proper cable connector pull-tab orientation.

As you insert the connector, you should feel it click into place; if you do not feel it click,
remove it, turn it around and try again.

About this task

Use the animation or the tabulated steps to complete the cabling between the controllers and the
switches. Perform the steps on each controller.

Animation - Cable a switched cluster

Steps
1. Cable the cluster interconnect ports e0c and e0d to the 25 GbE cluster interconnect switches.

5
2. Cable the wrench ports to the management network switches with the RJ45 cables.

DO NOT plug in the power cords at this point.

Step 4: Cable to host network or storage (Optional)

You have configuration-dependent optional cabling to the Fibre Channel or iSCSI host networks or direct-
attached storage. This cabling is not exclusive; you can have cabling to a host network and storage.

NetApp Hardware Universe slot priority for host network cards (Fibre Channel or 25GbE) is slot
2. However, if you have both cards, the Fibre Channel card goes in slot 2 and the 25GbE card
goes in slot 1 (as shown in the options below). If you have an external shelf, the storage card
goes in slot 1, the only supported slot for shelves.

6
Option 1: Cable to Fibre Channel host network
Fibre Channel ports on the controllers are connected to Fibre Channel host network switches.

Before you begin

• Contact your network administrator for information about connecting the system to the switches.
• Be sure to check the illustration arrow for the proper cable connector pull-tab orientation.

As you insert the connector, you should feel it click into place; if you do not feel it click,
remove it, turn it around and try again.

About this task

Perform the step on each controller module.

Steps
1. Cable ports 2a through 2d to the FC host switches.

Option 2: Cable to a 25GbE data or host network

25GbE ports on the controllers are connected to 25GbE data or host network switches.

Before you begin

• Contact your network administrator for information about connecting the system to the switches.
• Be sure to check the illustration arrow for the proper cable connector pull-tab orientation.

7
As you insert the connector, you should feel it click into place; if you do not feel it click,
remove it, turn it around and try again.

About this task

Perform the step on each controller module.

Steps
1. Cable ports e4a through e4d to the 10GbE host network switches.

Option 3: Cable controllers to single drive shelf

Cable each controller to the NSM modules on the NS224 drive shelf.

Before you begin

Be sure to check the illustration arrow for the proper cable connector pull-tab orientation.

As you insert the connector, you should feel it click into place; if you do not feel it click,
remove it, turn it around and try again.

About this task

Use the animation or the tabulated steps to complete the cabling between the controllers and the single
shelf. Perform the steps on each controller module.

8
Animation - Cable the controllers to a single NS224

Steps
1. Cable controller A to the shelf.

2. Cable controller B to the shelf.

Step 5: Complete system setup

Complete the system setup and configuration using cluster discovery with only a connection to the switch and
laptop, or by connecting directly to a controller in the system and then connecting to the management switch.

9
Option 1: If network discovery is enabled
If you have network discovery enabled on your laptop, you can complete system setup and configuration
using automatic cluster discovery.

Steps
1. Use the following animation to power on and set shelf IDs for one or more drive shelves:

For NS224 drive shelves, shelf IDs are pre-set to 00 and 01. If you want to change the shelf IDs, use
the straightened end of a paperclip, or narrow tipped ball point pen to access the shelf ID button
behind the faceplate.

Animation - Set drive shelf IDs

2. Plug the power cords into the controller power supplies, and then connect them to power sources on
different circuits.

The system begins to boot. Initial booting may take up to eight minutes.

3. Make sure that your laptop has network discovery enabled.

See your laptop’s online help for more information.

4. Connect your laptop to the Management switch:

5. Select an ONTAP icon listed to discover:

a. Open File Explorer.

b. Click Network in the left pane.

10
c. Right-click and select refresh.
d. Double-click either ONTAP icon and accept any certificates displayed on your screen.

XXXXX is the system serial number for the target node.

System Manager opens.

6. Use System Manager guided setup to configure your system using the data you collected in the
ONTAP Configuration Guide.
7. Set up your account and download Active IQ Config Advisor:
a. Log in to your existing account or create an account.

NetApp Support Registration

b. Register your system.

NetApp Product Registration

c. Download Active IQ Config Advisor.

NetApp Downloads: Config Advisor

8. Verify the health of your system by running Config Advisor.

9. After you have completed the initial configuration, go to ONTAP 9 documentation for information about
configuring additional features in ONTAP.

Option 2: If network discovery is not enabled

If network discovery is not enabled on your laptop, you must complete the configuration and setup using
this task.

Steps
1. Cable and configure your laptop or console:
a. Set the console port on the laptop or console to 115,200 baud with N-8-1.

See your laptop or console’s online help for how to configure the console port.

b. Connect the laptop or console to the management switch.

c. Assign a TCP/IP address to the laptop or console, using one that is on the management switch.
2. Use the following animation to power on and set shelf IDs for one or more drive shelves:

11
Animation - Set drive shelf IDs

3. Plug the power cords into the controller power supplies, and then connect them to power sources on
different circuits.

The system begins to boot. Initial booting may take up to eight minutes.

4. Assign an initial node management IP address to one of the nodes.

If the management network Then…

has DHCP…
Configured Record the IP address assigned to the new controllers.

Not configured a. Open a console session using PuTTY, a terminal server, or the
equivalent for your environment.

Check your laptop or console’s online help if

you do not know how to configure PuTTY.

b. Enter the management IP address when prompted by the

script.

5. Using System Manager on your laptop or console, configure your cluster:

a. Point your browser to the node management IP address.

The format for the address is https://x.x.x.x.

b. Configure the system using the data you collected in the ONTAP Configuration Guide.
6. Set up your account and download Active IQ Config Advisor:
a. Log in to your existing account or create an account.
b. Register your system.
c. Download Active IQ Config Advisor.
7. Verify the health of your system by running Config Advisor.
8. After you have completed the initial configuration, go to ONTAP 9 documentation for information about
configuring additional features in ONTAP.

Maintain
Maintain AFF C250 hardware
For the AFF C250 storage system, you can perform maintenance procedures on the
following components.

12
Boot media

The boot media stores a primary and secondary set of boot image files that the system uses when it boots.

Chassis

The chassis is the physical enclosure housing all the controller components such as the controller/CPU unit,
power supply, and I/O.

Controller

A controller consists of a board, firmware, and software. It controls the drives and implements the ONTAP
functions.

DIMM

You must replace a DIMM (dual in-line memory module) when a memory mismatch is present, or you have a
failed DIMM.

Drive

A drive is a device that provides the physical storage media for data.

Fan

The fan cools the controller.

Mezzanine card

A Mezzanine card is a printed circuit board that plugs directly into another plug-in card.

NVMEM battery

A battery is included with the controller and preserves cached data if the AC power fails.

Power supply

A power supply provides a redundant power source in a controller shelf.

Real time clock battery

A real time clock battery preserves system date and time information if the power is off.

Boot media

Overview of boot media replacement - AFF C250

The boot media stores a primary and secondary set of system (boot image) files that the
system uses when it boots.
Before you begin
• You must have a USB flash drive, formatted to MBR/FAT32, with the appropriate amount of storage to hold
the image_xxx.tgz file.

13
• You also must copy the image_xxx.tgz file to the USB flash drive for later use in this procedure.

About this task

• The nondisruptive and disruptive methods for replacing a boot media both require you to restore the var
file system:
◦ For nondisruptive replacement, the HA pair must be connected to a network to restore the var file
system.
◦ For disruptive replacement, you do not need a network connection to restore the var file system, but
the process requires two reboots.
• You must replace the failed component with a replacement FRU component you received from your
provider.
• It is important that you apply the commands in these steps on the correct controller:
◦ The impaired node is the controller on which you are performing maintenance.
◦ The healthy node is the HA partner of the impaired controller.

Check encryption key support and status - AFF C250

To ensure data security on your storage system, you need to verify the encryption key
support and status on your boot media. Check if your ONTAP version supports NetApp
Volume Encryption (NVE), and before you shut down the controller check if the key
manager is active.

Step 1: Check if your version of ONTAP supports NetApp Volume Encryption

Check whether your ONTAP version supports NetApp Volume Encryption (NVE). This information is crucial for
downloading the correct ONTAP image.

1. Determine if your ONTAP version supports encryption by running the following command:

version -v

If the output includes 1Ono-DARE, NVE is not supported on your cluster version.

2. Depending on whether NVE is supported on your system, take one of the following actions:
◦ If NVE is supported, download the ONTAP image with NetApp Volume Encryption.
◦ If NVE is not supported, download the ONTAP image without NetApp Volume Encryption.

Step 2: Determine if it is safe to shut down the controller

To safely shut down a controller, first identify whether the External Key Manager (EKM) or the Onboard Key
Manager (OKM) is active. Then, verify the key manager in use, display the appropriate key information, and
take action based on the status of the authentication keys.

1. Determine which key manager is enabled on your system:

14
ONTAP version Run this command
ONTAP 9.14.1 or later security key-manager keystore show

• If EKM is enabled, EKM is listed in the command output.

• If OKM is enabled, OKM is listed in the command output.
• If no key manager is enabled, No key manager keystores
configured is listed in the command output.

ONTAP 9.13.1 or earlier security key-manager show-key-store

• If EKM is enabled, external is listed in the command output.

• If OKM is enabled, onboard is listed in the command output.
• If no key manager is enabled, No key managers configured
is listed in the command output.

2. Depending on whether a key manger is configured on your system, select one of the following options.

No key manager configured

You can safely shut down the impaired controller. Go to shutdown the impaired controller.

External or Onboard key manager configured

a. Enter the following query command to display the status of the authentication keys in your key
manager.

security key-manager key query

b. Check the output for the value in the Restored column for your key manager.

This column indicates whether the authentication keys for your key manager (either EKM or OKM)
have been successfully restored.

3. Depending on whether your system is using the External Key Manager or Onboard Key Manager, select
one of the following options.

15
External Key Manager
Depending on the output value displayed in the Restored column, follow the appropriate steps.

Output value in Restored Follow these steps…

column

true You can safely shut down the impaired controller. Go to shutdown
the impaired controller.

Anything other than true a. Restore the external key management authentication keys to
all nodes in the cluster using the following command:

security key-manager external restore

If the command fails, contact NetApp Support.

b. Verify that the Restored column displays true for all

authentication keys by entering the security key-manager
key query command.

If all the authentication keys are true, you can safely shut
down the impaired controller. Go to shutdown the impaired
controller.

Onboard Key Manager

Depending on the output value displayed in the Restored column, follow the appropriate steps.

Output value in Restored Follow these steps…

column

true Manually back up the OKM information.

a. Go to the advanced mode by entering set -priv

advanced and then enter Y when prompted.
b. Enter the following command to display the key management
information:

security key-manager onboard show-backup

c. Copy the contents of the backup information to a separate file

or your log file.

You’ll need it in disaster scenarios where you might need to

manually recover OKM.

d. You can safely shut down the impaired controller. Go to

shutdown the impaired controller.

16
Output value in Restored Follow these steps…
column

Anything other than true a. Enter the onboard security key-manager sync command:

security key-manager onboard sync

b. Enter the 32 character, alphanumeric onboard key

management passphrase when prompted.

If the passphrase cannot be provided, contact NetApp

Support.

c. Verify the Restored column displays true for all

authentication keys:

security key-manager key query

d. Verify that the Key Manager type displays onboard, and

then manually back up the OKM information.
e. Enter the command to display the key management backup
information:

security key-manager onboard show-backup

f. Copy the contents of the backup information to a separate file

or your log file.

You’ll need it in disaster scenarios where you might need to

manually recover OKM.

g. You can safely shut down the impaired controller. Go to

shutdown the impaired controller.

Shut down the controller - AFF C250

Option 1: Most systems

After completing the NVE or NSE tasks, you need to complete the shutdown of the
impaired controller.
Steps
a. Take the impaired controller to the LOADER prompt:

If the impaired controller Then…

displays…
The LOADER prompt Go to Remove controller module.

17
If the impaired controller Then…
displays…

Waiting for giveback… Press Ctrl-C, and then respond y when prompted.

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.

b. From the LOADER prompt, enter: printenv to capture all boot environmental variables. Save the output
to your log file.

This command may not work if the boot device is corrupted or non-functional.

Option 2: Systems in a MetroCluster

After completing the NVE or NSE tasks, you need to complete the shutdown of the impaired controller.

Do not use this procedure if your system is in a two-node MetroCluster configuration.

• 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 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 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 the next step.

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

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 boot media - AFF C250

To replace the boot media, you must remove the impaired controller module, install the
replacement boot media, and transfer the boot image to a USB flash drive.

Step 1: Remove the controller module

To access components inside the controller module, 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 controller module power supplies from the source.
3. Release the power cable retainers, and then unplug the cables from the power supplies.
4. Insert your forefinger into the latching mechanism on either side of the controller module, press the lever
with your thumb, and gently pull the controller a few inches out of the chassis.

If you have difficulty removing the controller module, place your index fingers through the
finger holes from the inside (by crossing your arms).

19
Lever

Latching mechanism

5. Using both hands, grasp the controller module sides and gently pull it out of the chassis and set it on a flat,
stable surface.
6. Turn the thumbscrew on the front of the controller module anti-clockwise and open the controller module
cover.

Thumbscrew

Controller module cover.

7. Lift out the air duct cover.

20
Step 2: Replace the boot media

You locate the failed boot media in the controller module by removing the air duct on the controller module
before you can replace the boot media.

You need a #1 magnetic Phillips head screwdriver to remove the screw that holds the boot media in place. Due
to the space constraints within the controller module, you should also have a magnet to transfer the screw on
to so that you do not lose it.

You can use the following video or the tabulated steps to replace the boot media:

Animation - Replace the boot media

1. Locate and replace the impaired boot media from the controller module.

21
Remove the screw securing the boot media to the motherboard in the
controller module.

Lift the boot media out of the controller module.

2. Using the #1 magnetic screwdriver, remove the screw from the impaired boot media, and set it aside safely
on the magnet.
3. Gently lift the impaired boot media directly out of the socket and set it aside.
4. Remove the replacement boot media from the antistatic shipping bag and align it into place on the
controller module.
5. Using the #1 magnetic screwdriver, insert and tighten the screw on the boot media.

Do not apply force when tightening the screw on the boot media; you might crack it.

Step 3: Transfer the boot image to the boot media

The replacement boot media that you installed is without a boot image so you need to transfer a boot image
using a USB flash drive.

• You must have a USB flash drive, formatted to MBR/FAT32, with at least 4GB capacity
• A copy of the same image version of ONTAP as what the impaired controller was running. You can
download the appropriate image from the Downloads section on the NetApp Support Site
◦ If NVE is enabled, download the image with NetApp Volume Encryption, as indicated in the download

22
button.
◦ If NVE is not enabled, download the image without NetApp Volume Encryption, as indicated in the
download button.
• If your system is an HA pair, you must have a network connection.
• If your system is a stand-alone system you do not need a network connection, but you must perform an
additional reboot when restoring the var file system.

1. Download and copy the appropriate service image from the NetApp Support Site to the USB flash
drive.
2. Download the service image to your work space on your laptop.
3. Unzip the service image.

If you are extracting the contents using Windows, do not use winzip to extract the
netboot image. Use another extraction tool, such as 7-Zip or WinRAR.

There are two folders in the unzipped service image file:

▪ boot
▪ efi
4. Copy the efi folder to the top directory on the USB flash drive.

If the service image has no efi folder, see EFI folder missing from Service Image download
file used for boot device recovery for FAS and AFF models^ .

+ The USB flash drive should have the efi folder and the same Service Image (BIOS) version of what the
impaired controller is running.

1. Remove the USB flash drive from your laptop.

2. If you have not already done so, install the air duct.

23
3. Close the controller module cover and tighten the thumbscrew.

24
Controller module cover

Thumbscrew

4. Align the end of the controller module with the opening in the chassis, and then gently push the
controller module halfway into the system.
5. Insert the USB flash drive into the USB slot on the controller module.

Make sure that you install the USB flash drive in the slot labeled for USB devices, and not in the USB
console port.

6. Push the controller module all the way into the chassis:
7. Place your index fingers through the finger holes from the inside of the latching mechanism.
8. Press your thumbs down on the orange tabs on top of the latching mechanism and gently push the
controller module over the stop.
9. Release your thumbs from the top of the latching mechanisms and continue pushing until the latching
mechanisms snap into place.

The controller module should be fully inserted and flush with the edges of the chassis.

10. Plug the power cords into the power supplies, reinstall the power cable locking collar, and then connect
the power supplies to the power source.

The controller module begins to boot as soon as power is restored. Be prepared to interrupt the boot
process.

11. Interrupt the boot process to stop at the LOADER prompt by pressing Ctrl-C when you see Starting
AUTOBOOT press Ctrl-C to abort….

If you miss this message, press Ctrl-C, select the option to boot to Maintenance mode, and then halt
the controller to boot to LOADER.

12. For systems with one controller in the chassis, reconnect the power and turn on the power supplies.

The system begins to boot and stops at the LOADER prompt.

Boot the recovery image - AFF C250

After installing the new boot media device in your system, you can boot the recovery
image from a USB drive and restore the configuration from the partner node.
Steps
1. From the LOADER prompt, boot the recovery image from the USB flash drive: boot_recovery

The image is downloaded from the USB flash drive.

2. When prompted, either enter the name of the image or accept the default image displayed inside the
brackets on your screen.

25
3. Restore the var file system:

Option 1: ONTAP 9.16.0 or earlier

a. On the impaired controller, press Y when you see Do you want to restore the backup
configuration now?
b. On the impaired controller, press Y when prompted to overwrite /etc/ssh/ssh_host_ecdsa_key.
c. On the healthy partner controller, set the impaired controller to advanced privilege level: set
-privilege advanced.
d. On the healthy partner controller, run the restore backup command: system node restore-
backup -node local -target-address impaired_node_IP_address .

NOTE: If you see any message other than a successful restore, contact NetApp Support.

e. On the healthy partner controller, return the impaired controller to admin level: set -privilege
admin.
f. On the impaired controller, press Y when you see Was the restore backup procedure
successful?.
g. On the impaired controller, press Y when you see …would you like to use this
restored copy now?.
h. On the impaired controller, press Y when prompted to reboot the impaired controller and press
ctrl-c for the Boot Menu.
i. If the system does not use encryption, select Option 1 Normal Boot., otherwise go to Restore
encryption.

Option 2: ONTAP 9.16.1 or later

a. On the impaired controller, press Y when prompted to restore the backup configuration.

After restore procedure is successful, this message will be seen on the console -
syncflash_partner: Restore from partner complete.

b. On the impaired controller, press Y when prompted to confirm if the restore backup was
successful.
c. On the impaired controller, press Y when prompted to use the restored configuration.
d. On the impaired controller, press Y when prompted to reboot the node.
e. On the impaired controller, press Y when prompted to reboot the impaired controller and press
ctrl-c for the Boot Menu.
f. If the system does not use encryption, select Option 1 Normal Boot., otherwise go to Restore
encryption.

4. Connect the console cable to the partner controller.

5. Give back the controller using the storage failover giveback -fromnode local command.
6. Restore automatic giveback if you disabled it by using the storage failover modify -node local
-auto-giveback true command.

26
7. If AutoSupport is enabled, restore/unsuppress automatic case creation by using the system node
autosupport invoke -node * -type all -message MAINT=END command.

NOTE: If the process fails, contact NetApp Support.

Restore encryption - AFF C250

Restore encryption on the replacement boot media.

You must complete steps specific to systems that have Onboard Key Manager (OKM), NetApp Storage
Encryption (NSE) or NetApp Volume Encryption (NVE) enabled using the settings that you captured at the
beginning of the boot media replace procedure.

Depending on which a key manger is configured on your system, select one of the following options to restore
it from the boot menu.

• Option 1: Restore the Onboard Key Manager configuration

• Option 2: Restore the External Key Manager configuration

Option 1: Restore the Onboard Key Manager configuration

Restore the Onboard Key Manager (OKM) configuration from the ONTAP boot menu.

Before you begin

• Make sure you have following information while restoring the OKM configuration:
◦ Cluster-wide passphrase entered while enabling onboard key management.
◦ Backup information for the Onboard Key Manager.
• Perform the How to verify onboard key management backup and cluster-wide passphrase procedure
before proceeding.

Steps
1. Connect the console cable to the target controller.
2. From the ONTAP boot menu select the appropriate option from the boot menu.

27
ONTAP version Select this option
ONTAP 9.8 or later Select option 10.

Show example boot menu

Please choose one of the following:

(1) Normal Boot.

(2) Boot without /etc/rc.
(3) Change password.
(4) Clean configuration and initialize
all disks.
(5) Maintenance mode boot.
(6) Update flash from backup config.
(7) Install new software first.
(8) Reboot node.
(9) Configure Advanced Drive
Partitioning.
(10) Set Onboard Key Manager recovery
secrets.
(11) Configure node for external key
management.
Selection (1-11)? 10

28
ONTAP version Select this option
ONTAP 9.7 and earlier Select the hidden option recover_onboard_keymanager

Show example boot menu

Please choose one of the following:

(1) Normal Boot.

3. Confirm that you want to continue the recovery process.

Show example prompt

This option must be used only in disaster recovery procedures. Are you
sure? (y or n):

4. Enter the cluster-wide passphrase twice.

While entering the passphrase the console will not show any input.

Show example prompt

Enter the passphrase for onboard key management:

Enter the passphrase again to confirm:

5. Enter the backup information.

a. Paste the entire content from the BEGIN BACKUP line through the END BACKUP line.

29
Show example prompt

Enter the backup data:

--------------------------BEGIN BACKUP--------------------------
0123456789012345678901234567890123456789012345678901234567890123
1234567890123456789012345678901234567890123456789012345678901234
2345678901234567890123456789012345678901234567890123456789012345
3456789012345678901234567890123456789012345678901234567890123456
4567890123456789012345678901234567890123456789012345678901234567
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
0123456789012345678901234567890123456789012345678901234567890123
1234567890123456789012345678901234567890123456789012345678901234
2345678901234567890123456789012345678901234567890123456789012345
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA

---------------------------END BACKUP---------------------------

b. Press the enter key twice at the end of the input.

The recovery process completes.

30
Show example prompt

Trying to recover keymanager secrets....

Setting recovery material for the onboard key manager
Recovery secrets set successfully
Trying to delete any existing km_onboard.wkeydb file.

Successfully recovered keymanager secrets.

*****************************************************************
******************
* Select option "(1) Normal Boot." to complete recovery process.
*
* Run the "security key-manager onboard sync" command to
synchronize the key database after the node reboots.
*****************************************************************
******************

Do not proceed if the displayed output is anything other than Successfully recovered
keymanager secrets. Perform troubleshooting to correct the error.

6. Select option 1 from the boot menu to continue booting into ONTAP.

31
Show example prompt

********************************************************************
***************
* Select option "(1) Normal Boot." to complete the recovery process.
*
********************************************************************
***************

(1) Normal Boot.

(2) Boot without /etc/rc.
(3) Change password.
(4) Clean configuration and initialize all disks.
(5) Maintenance mode boot.
(6) Update flash from backup config.
(7) Install new software first.
(8) Reboot node.
(9) Configure Advanced Drive Partitioning.
(10) Set Onboard Key Manager recovery secrets.
(11) Configure node for external key management.
Selection (1-11)? 1

7. Confirm that the controller’s console displays the following message.

Waiting for giveback…(Press Ctrl-C to abort wait)

8. From the partner node, giveback the partner controller by entering the following command.

storage failover giveback -fromnode local -only-cfo-aggregates true.

9. After booting with only the CFO aggregate, run the following command.

security key-manager onboard sync

10. Enter the cluster-wide passphrase for the Onboard Key Manager.

32
Show example prompt

Enter the cluster-wide passphrase for the Onboard Key Manager:

All offline encrypted volumes will be brought online and the

corresponding volume encryption keys (VEKs) will be restored
automatically within 10 minutes. If any offline encrypted volumes
are not brought online automatically, they can be brought online
manually using the "volume online -vserver <vserver> -volume
<volume_name>" command.

If the sync is successful the cluster prompt is returned with no additional messages. If the
sync fails an error message appears before returning to the cluster prompt. Do not continue
until the the error is corrected and the sync runs successfully.

11. Ensure that all keys are synced by entering the following command.

security key-manager key query -restored false.

There are no entries matching your query.

No results should appear when filtering for false in the restored parameter.

12. Giveback the node from the partner by entering the following command.

storage failover giveback -fromnode local

13. Restore automatic giveback, if you disabled it, by entering the following command.

storage failover modify -node local -auto-giveback true

14. If AutoSupport is enabled, restore automatic case creation by entering the following command.

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

Option 2: Restore the External Key Manager configuration

Restore the External Key Manager configuration from the ONTAP boot menu.

Before you begin

You need the following information for restoring the External Key Manager (EKM) configuration.

• A copy of the /cfcard/kmip/servers.cfg file from another cluster node or the following information:
◦ The KMIP server address.
◦ The KMIP port.
• A copy of the /cfcard/kmip/certs/client.crt file from another cluster node or the client certificate.

33
• A copy of the /cfcard/kmip/certs/client.key file from another cluster node or the client key.
• A copy of the /cfcard/kmip/certs/CA.pem file from another cluster node or the KMIP server CA(s).

Steps
1. Connect the console cable to the target controller.
2. Select option 11 from the ONTAP boot menu.

Show example boot menu

(1) Normal Boot.

(2) Boot without /etc/rc.
(3) Change password.
(4) Clean configuration and initialize all disks.
(5) Maintenance mode boot.
(6) Update flash from backup config.
(7) Install new software first.
(8) Reboot node.
(9) Configure Advanced Drive Partitioning.
(10) Set Onboard Key Manager recovery secrets.
(11) Configure node for external key management.
Selection (1-11)? 11

3. When prompted, confirm you have gathered the required information.

Show example prompt

Do you have a copy of the /cfcard/kmip/certs/client.crt file? {y/n}

Do you have a copy of the /cfcard/kmip/certs/client.key file? {y/n}
Do you have a copy of the /cfcard/kmip/certs/CA.pem file? {y/n}
Do you have a copy of the /cfcard/kmip/servers.cfg file? {y/n}

4. When prompted, enter the client and server information.

Show prompt

Enter the client certificate (client.crt) file contents:

Enter the client key (client.key) file contents:
Enter the KMIP server CA(s) (CA.pem) file contents:
Enter the server configuration (servers.cfg) file contents:

34
Show example

Enter the client certificate (client.crt) file contents:

-----BEGIN CERTIFICATE-----
<certificate_value>
-----END CERTIFICATE-----

Enter the client key (client.key) file contents:

-----BEGIN RSA PRIVATE KEY-----
<key_value>
-----END RSA PRIVATE KEY-----

Enter the KMIP server CA(s) (CA.pem) file contents:

-----BEGIN CERTIFICATE-----
<certificate_value>
-----END CERTIFICATE-----

Enter the IP address for the KMIP server: 10.10.10.10

Enter the port for the KMIP server [5696]:

System is ready to utilize external key manager(s).

Trying to recover keys from key servers....
kmip_init: configuring ports
Running command '/sbin/ifconfig e0M'
..
..
kmip_init: cmd: ReleaseExtraBSDPort e0M

After you enter the client and server information, the recovery process completes.

Show example

System is ready to utilize external key manager(s).

Trying to recover keys from key servers....
Performing initialization of OpenSSL
Successfully recovered keymanager secrets.

5. Select option 1 from the boot menu to continue booting into ONTAP.

35
Show example prompt

********************************************************************
*******
* Select option "(1) Normal Boot." to complete the recovery process.
*
********************************************************************
*******

(1) Normal Boot.

(2) Boot without /etc/rc.
(3) Change password.
(4) Clean configuration and initialize all disks.
(5) Maintenance mode boot.
(6) Update flash from backup config.
(7) Install new software first.
(8) Reboot node.
(9) Configure Advanced Drive Partitioning.
(10) Set Onboard Key Manager recovery secrets.
(11) Configure node for external key management.
Selection (1-11)? 1

6. Restore automatic giveback if you disabled it.

storage failover modify -node local -auto-giveback true

7. If AutoSupport is enabled, restore automatic case creation by entering the following command.

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

Return the failed part to NetApp - AFF C250

Return the failed part to NetApp, as described in the RMA instructions shipped with the
kit. See the Part Return and Replacements page for further information.

Chassis

Overview of chassis replacement - AFF C250

To replace the chassis, you must move the bezel, controller modules, and NVMe drives
from the impaired chassis to the replacement chassis, and then remove the impaired
chassis from the equipment rack or system cabinet and install the replacement chassis in
its place.
About this task

36
• All other components in the system must be functioning properly; if not, you must contact technical support.
• You can use this procedure with all versions of ONTAP supported by your system.
• This procedure is written with the assumption that you are moving the bezel, NVMe drives, and controller
modules to the new chassis, and that the replacement chassis is a new component from NetApp.
• This procedure is disruptive. For a two-node cluster, you will have a complete service outage and a partial
outage in a multi-node cluster.

Shut down the controllers - AFF C250

This procedure is for systems with two node configurations. For more information about
graceful shutdown when servicing a cluster, see Gracefully shutdown and power up your
storage system Resolution Guide - NetApp Knowledge Base.
Before you begin
• Make sure you have the necessary permissions and credentials:
◦ Local administrator credentials for ONTAP.
◦ BMC accessability for each controller.
• Make sure you have the necessary tools and equipment for the replacement.
• As a best practice before shutdown, you should:
◦ Perform additional system health checks.
◦ Upgrade ONTAP to a recommended release for the system.
◦ Resolve any Active IQ Wellness Alerts and Risks. Make note of any faults presently on the system,
such as LEDs on the system components.

Steps
1. Log into the cluster through SSH or log in from any node in the cluster using a local console cable and a
laptop/console.
2. Stop all clients/host from accessing data on the NetApp system.
3. Suspend external backup jobs.
4. If AutoSupport is enabled, suppress case creation and indicate how long you expect the system to be
offline:

system node autosupport invoke -node * -type all -message "MAINT=2h Replace
chassis"

5. Identify the SP/BMC address of all cluster nodes:

system service-processor show -node * -fields address

6. Exit the cluster shell:

exit

7. Log into SP/BMC over SSH using the IP address of any of the nodes listed in the output from the previous
step to monitor progress.

If you are using a console/laptop, log into the controller using the same cluster administrator credentials.

37
8. Halt the two nodes located in the impaired chassis:

system node halt -node <node1>,<node2> -skip-lif-migration-before-shutdown

true -ignore-quorum-warnings true -inhibit-takeover true

For clusters using SnapMirror synchronous operating in StrictSync mode: system node
halt -node <node1>,<node2> -skip-lif-migration-before-shutdown true
-ignore-quorum-warnings true -inhibit-takeover true -ignore-strict
-sync-warnings true

9. Enter y for each controller in the cluster when you see:

Warning: Are you sure you want to halt node <node_name>? {y|n}:

10. Wait for each controller to halt and display the LOADER prompt.

Replace hardware - AFF C250

To replace the chassis, you move the power supplies, hard drives, and controller module
from the impaired chassis to the new chassis, and swap out the impaired chassis from
with the new chassis of the same model as the impaired chassis.

Step 1: Remove the controller modules

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

Use the following video or the tabulated steps to replace the chassis; it assumes the removal and replacement
of the bezel:

Animation - Replace the chassis

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

2. Unplug the controller module power supplies from the source.
3. Release the power cable retainers, and then unplug the cables from the power supplies.
4. Insert your forefinger into the latching mechanism on either side of the controller module, press the lever
with your thumb, and gently pull the controller a few inches out of the chassis.

If you have difficulty removing the controller module, place your index fingers through the
finger holes from the inside (by crossing your arms).

38
Lever

Latching mechanism

5. Using both hands, grasp the controller module sides and gently pull it out of the chassis and set it on a flat,
stable surface.
6. Set the controller module aside in a safe place, and repeat these steps for the other controller module in
the chassis.

Step 2: Move drives to the new chassis

You need to move the drives from each bay opening in the old chassis to the same bay opening in the new
chassis.

1. Gently remove the bezel from the front of the system.

2. Remove the drives:
a. Press the release button at the top of the carrier face below the LEDs.
b. Pull the cam handle to its fully open position to unseat the drive from the midplane, and then gently
slide the drive out of the chassis.

The drive should disengage from the chassis, allowing it to slide free of the chassis.

When removing a drive, always use two hands to support its weight.

Drives are fragile. Handle them as little as possible to prevent damage to them.

3. Align the drive from the old chassis with the same bay opening in the new chassis.
4. Gently push the drive into the chassis as far as it will go.

The cam handle engages and begins to rotate upward.

5. Firmly push the drive the rest of the way into the chassis, and then lock the cam handle by pushing it up
and against the drive holder.

39
Be sure to close the cam handle slowly so that it aligns correctly with the front of the drive carrier. It clicks
when it is secure.

6. Repeat the process for the remaining drives in the system.

Step 3: Replace a chassis from within the equipment rack or system cabinet

You must remove the existing chassis from the equipment rack or system cabinet before you can install the
replacement chassis.

1. Remove the screws from the chassis mount points.

2. With two people, slide the old chassis off the rack rails in a system cabinet or equipment rack, and then set
it aside.
3. If you are not already grounded, properly ground yourself.
4. Using two people, install the replacement chassis into the equipment rack or system cabinet by guiding the
chassis onto the rack rails in a system cabinet or equipment rack.
5. Slide the chassis all the way into the equipment rack or system cabinet.
6. Secure the front of the chassis to the equipment rack or system cabinet, using the screws you removed
from the old chassis.
7. If you have not already done so, install the bezel.

Step 4: Install the controller modules

After you install the controller modules into the new chassis, you need to boot the 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.

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

2. Recable the console to the controller module, and then reconnect the management port.
3. Insert the controller module into the chassis:

a. Ensure the latching mechanism arms are locked in the fully extended position.
b. Using both hands, align and gently slide the controller module into the latching mechanism arms until it
stops.
c. Place your index fingers through the finger holes from the inside of the latching mechanism.
d. Press your thumbs down on the orange tabs on top of the latching mechanism and gently push the
controller module over the stop.
e. Release your thumbs from the top of the latching mechanisms and continue pushing until the latching
mechanisms snap into place.
The controller module should be fully inserted and flush with the edges of the chassis.

a. Plug the power cords into the power supplies, reinstall the power cable locking collar, and then connect
the power supplies to the power source.

40
The controller module begins to boot as soon as power is restored. Be prepared to interrupt the boot
process.

4. Repeat the preceding steps to install the second controller into the new chassis.

Complete the restoration and replacement process - AFF C250

You must verify the HA state of the chassis, and return the failed part to NetApp, as
described in the RMA instructions shipped with the kit.

Step 1: Verify and set the HA state of the chassis

You must verify the HA state of the chassis, and, if necessary, update the state to match your system
configuration.

1. In Maintenance mode, from either controller module, display the HA state of the local controller module and
chassis: ha-config show

The HA state should be the same for all components.

2. If the displayed system state for the chassis does not match your system configuration:
a. Set the HA state for the chassis: ha-config modify chassis HA-state

The value for HA-state can be one of the following:

▪ ha
▪ mcc
▪ mccip
▪ non-ha
b. Confirm that the setting has changed: ha-config show
3. If you have not already done so, recable the rest of your system.
4. Reinstall the bezel on the front of the system.

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

Controller

Overview of controller module replacement- AFF C250

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 a MetroCluster configuration, you must review the section Choosing the correct
recovery procedure to determine whether you should use this procedure.

41
• 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 impaired controller module - AFF C250

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.

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 from the console of the healthy controller: storage failover modify
-node local -auto-giveback false

When you see Do you want to disable auto-giveback?, enter y.

3. Take the impaired controller to the LOADER prompt:

42
If the impaired controller is Then…
displaying…
The LOADER prompt Go to the next step.

Waiting for giveback… Press Ctrl-C, and then respond y when prompted.

System prompt or password Take over or halt the impaired controller from the healthy controller:
prompt 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 C250

To replace the controller module hardware, 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 the controller module

You must remove the controller module from the chassis when you replace a component inside the controller
module.

Make sure that you label the cables so that you know where they came from.

Use the following video or the tabulated steps to replace a controller module:

Animation - Replace a controller module

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

If you have difficulty removing the controller module, place your index fingers through the
finger holes from the inside (by crossing your arms).

43
Lever

Latching mechanism

44
Thumbscrew

Controller module cover.

7. Lift out the air duct cover.

Step 2: Move the power supply

You must move the power supply from the impaired controller module to the replacement controller module
when you replace a controller module.

1. Disconnect the power supply.

2. Open the power cable retainer, and then unplug the power cable from the power supply.
3. Unplug the power cable from the power source.
4. Rotate the cam handle such that it can be used to pull power supply out of the controller module while
pressing the locking tab.

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

The power supply is short. Always use two hands to support it when removing it from the controller module
so that it does not suddenly swing free from the controller module and injure you.

45
Blue power supply locking tab

Power supply

5. Move the power supply to the new controller module, and then install it.
6. Using both hands, support and align the edges of the power supply with the opening in the controller
module, and then gently push the power supply into the controller module until the locking tab clicks into
place.

The power supplies will only properly engage with the internal connector and lock in place one way.

To avoid damaging the internal connector, do not use excessive force when sliding the
power supply into the system.

Step 3: Move the fans

You must move the fans from the impaired controller module to the replacement module when replacing a
failed controller module.

1. Remove the fan module by pinching the side of the fan module, and then lifting the fan module straight out
of the controller module.

46
Fan module

2. Move the fan module to the replacement controller module, and align the edges of the fan module with the
opening in the controller module, and then slide the fan module in.
3. Repeat these steps for the remaining fan modules.

Step 4: Move the boot media

You must move the boot media device from the impaired controller module to the replacement controller
module.

1. Locate and move the boot media from the impaired controller module to the replacement controller module.

The boot media is located under the air duct cover you removed earlier in this procedure.

47
Remove the screw securing the boot media to the motherboard in the impaired
controller module.

Lift the boot media out of the impaired controller module.

2. Using the #1 magnetic screwdriver, remove the screw from the boot media, and set it aside safely on the
magnet.
3. Gently lift the boot media directly out of the socket and align it into place in the replacement controller
module.
4. Using the #1 magnetic screwdriver, insert and tighten the screw on the boot media.

Do not apply force when tightening the screw on the boot media; you might crack it.

Step 5: Move the DIMMs

To move the DIMMs, locate and move them from the impaired controller into the replacement controller and
follow the specific sequence of steps.

48
Install each DIMM into the same slot it occupied in the impaired controller module.

1. Slowly push apart the DIMM ejector tabs on either side of the DIMM, and slide the DIMM out of the slot.

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

2. Locate the corresponding DIMM slot on the replacement controller module.

3. Make sure that the DIMM ejector tabs on the DIMM socket are in the open position, and then insert the
DIMM squarely into the socket.

The DIMMs fit tightly in the socket. If not, reinsert the DIMM to realign it with the socket.

4. Visually inspect the DIMM to verify that it is evenly aligned and fully inserted into the socket.
5. Repeat these steps for the remaining DIMM.

Step 6: Move a mezzanine card

To move a mezzanine card, you must remove the cabling and any QSFPs and SFPs from the ports, move the
mezzanine card to the replacement controller, reinstall any QSFPs and SFPs onto the ports, and cable the
ports.

1. Locate and move the mezzanine cards from your impaired controller module.

49
Remove screws on the face of the controller module.

Loosen the screw in the controller module.

Move the mezzanine card.

2. Unplug any cabling associated with the mezzanine card.

Make sure that you label the cables so that you know where they came from.

a. Remove any SFP or QSFP modules that might be in the mezzanine card and set it aside.
b. Using the #1 magnetic screwdriver, remove the screws from the face of the impaired controller module
and from the mezzanine card, and set them aside safely on the magnet.
c. Gently lift the mezzanine card out of the socket and move it to the same position in the replacement
controller.
d. Gently align the mezzanine card into place in the replacement controller.
e. Using the #1 magnetic screwdriver, insert and tighten the screws on the face of the replacement
controller module and on the mezzanine card.

Do not apply force when tightening the screw on the mezzanine card; you might crack it.

3. Repeat these steps if there is another mezzanine card in the impaired controller module.

50
4. Insert the SFP or QSFP modules that were removed onto the mezzanine card.

Step 7: Move the NV battery

When replacing the controller module, you must move the NV battery from the impaired controller module to
the replacement controller module.

1. Locate and move the NVMEM battery from your impaired controller module to the replacement controller
module.

Squeeze the clip on the face of the battery plug.

Unplug the battery cable from the socket.

Grasp the battery and press the blue locking tab marked PUSH.

Lift the battery out of the holder and controller module.

51
to the battery holder.
5. Insert the NV battery plug into the socket.
6. 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.
7. Press firmly down on the battery pack to make sure that it is locked into place.

Step 8: Install the controller module

After all of the components have been moved from the impaired controller module to the replacement controller
module, you must install the replacement controller module into the chassis, and then boot it to Maintenance
mode.

You can use the following illustrations or the written steps to install the replacement controller module in the
chassis.

1. If you have not already done so, install the air duct.

2. Close the controller module cover and tighten the thumbscrew.

52
Controller module cover

Thumbscrew

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

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

5. Insert the controller module into the chassis:

53
mechanisms snap into place.

The controller module should be fully inserted and flush with the edges of the chassis.

f. Plug the power cords into the power supplies, reinstall the power cable locking collar, and then connect
the power supplies to the power source.

The controller module begins to boot as soon as power is restored. Be prepared to interrupt the boot
process.

Restore and verify the system configuration - AFF C250

After completing the hardware replacement and booting to Maintenance mode, you verify
the low-level system configuration of the replacement controller and reconfigure system
settings as necessary.

Step 1: Set and verify system time after replacing the controller

You should check the time and date on the replacement controller module against the healthy controller
module in an HA pair, or against a reliable time server in a stand-alone configuration. If the time and date do
not match, you must reset them on the replacement controller module to prevent possible outages on clients
due to time differences.

About this task

It is important that you apply the commands in the steps on the correct systems:

• The replacement node is the new node that replaced the impaired node as part of this procedure.
• The healthy node is the HA partner of the replacement node.

Steps
1. If the replacement node is not at the LOADER prompt, halt the system to the LOADER prompt.
2. On the healthy node, check the system time: cluster date show

The date and time are based on the configured timezone.

3. At the LOADER prompt, check the date and time on the replacement node: show date

The date and time are given in GMT.

4. If necessary, set the date in GMT on the replacement node: set date mm/dd/yyyy
5. If necessary, set the time in GMT on the replacement node: set time hh:mm:ss
6. At the LOADER prompt, confirm the date and time on the replacement node: show date

The date and time are given in GMT.

Step 2: Verify and set the HA state of the controller

You must verify the HA state of the controller module and, if necessary, update the state to match your system
configuration.

54
1. In Maintenance mode from the new controller module, verify that all components display the same HA
state: ha-config show

The HA state should be the same for all components.

2. If the displayed system state of the controller module does not match your system configuration, set the HA
state for the controller module: ha-config modify controller ha-state

The value for HA-state can be one of the following:

◦ ha
◦ mcc
◦ mccip
◦ non-ha
3. If the displayed system state of the controller module does not match your system configuration, set the HA
state for the controller module: ha-config modify controller ha-state
4. Confirm that the setting has changed: ha-config show

Recable the system and reassign disks - AFF C250

Continue the replacement procedure by recabling the storage and confirming disk
reassignment.

Step 1: Recable the system

Verify the controller module’s storage and network connections.

Steps
1. Verify that the cabling is correct by using Active IQ Config Advisor.
a. Download and install Config Advisor.
b. Enter the information for the target system, and then click Collect Data.
c. Click the Cabling tab, and then examine the output. Make sure that all disk shelves are displayed and
all disks appear in the output, correcting any cabling issues you find.
d. Check other cabling by clicking the appropriate tab, and then examining the output from Config Advisor.

Step 2: Reassign disks

If the storage system is in an HA pair, the system ID of the new controller module is automatically assigned to
the disks when the giveback occurs at the end of the procedure. You must confirm the system ID change when
you boot the replacement controller and then verify that the change was implemented.

This procedure applies only to systems running ONTAP in an HA pair.

1. If the replacement controller is in Maintenance mode (showing the *> prompt, exit Maintenance mode and
go to the LOADER prompt: halt
2. From the LOADER prompt on the replacement controller, boot the controller, entering y if you are prompted
to override the system ID due to a system ID mismatch:
3. Wait until the Waiting for giveback… message is displayed on the replacement controller console and

55
then, from the healthy controller, verify that the new partner system ID has been automatically assigned:
storage failover show

In the command output, you should see a message that the system ID has changed on the impaired
controller, showing the correct old and new IDs. In the following example, node2 has undergone
replacement and has a new system ID of 151759706.

node1> `storage failover show`

Takeover
Node Partner Possible State Description
------------ ------------ --------
-------------------------------------
node1 node2 false System ID changed on
partner (Old:
151759755, New:
151759706), In takeover
node2 node1 - Waiting for giveback
(HA mailboxes)

4. From the healthy controller, verify that any coredumps are saved:
a. Change to the advanced privilege level: set -privilege advanced

You can respond Y when prompted to continue into advanced mode. The advanced mode prompt
appears (*>).

b. Save any coredumps: system node run -node local-node-name partner savecore
c. Wait for the `savecore`command to complete before issuing the giveback.

You can enter the following command to monitor the progress of the savecore command: system
node run -node local-node-name partner savecore -s

d. Return to the admin privilege level: set -privilege admin

5. If your storage system has Storage or Volume Encryption configured, you must restore Storage or Volume
Encryption functionality by using one of the following procedures, depending on whether you are using
onboard or external key management:
◦ Restore onboard key management encryption keys
◦ Restore external key management encryption keys
6. Give back the controller:
a. From the healthy controller, give back the replaced controller’s storage: storage failover
giveback -ofnode replacement_node_name

The replacement controller takes back its storage and completes booting.

If you are prompted to override the system ID due to a system ID mismatch, you should enter y.

If the giveback is vetoed, you can consider overriding the vetoes.

56
Find the High-Availability Configuration content for your version of ONTAP 9

b. After the giveback has been completed, confirm that the HA pair is healthy and that takeover is
possible: storage failover show

The output from the storage failover show command should not include the System ID changed
on partner message.

7. Verify that the disks were assigned correctly: storage disk show -ownership

The disks belonging to the replacement controller should show the new system ID. In the following
example, the disks owned by node1 now show the new system ID, 1873775277:

node1> `storage disk show -ownership`

Disk Aggregate Home Owner DR Home Home ID Owner ID DR Home ID

Reserver Pool
----- ------ ----- ------ -------- ------- ------- -------
--------- ---
1.0.0 aggr0_1 node1 node1 - 1873775277 1873775277 -
1873775277 Pool0
1.0.1 aggr0_1 node1 node1 1873775277 1873775277 -
1873775277 Pool0
.
.
.

8. If the system is in a MetroCluster configuration, monitor the status of the controller: metrocluster node
show

The MetroCluster configuration takes a few minutes after the replacement to return to a normal state, at
which time each controller will show a configured state, with DR Mirroring enabled and a mode of normal.
The metrocluster node show -fields node-systemid command output displays the old system
ID until the MetroCluster configuration returns to a normal state.

9. If the controller is in a MetroCluster configuration, depending on the MetroCluster state, verify that the DR
home ID field shows the original owner of the disk if the original owner is a controller on the disaster site.

This is required if both of the following are true:

◦ The MetroCluster configuration is in a switchover state.

◦ The replacement controller is the current owner of the disks on the disaster site.

Disk ownership changes during HA takeover and MetroCluster switchover in a four-node MetroCluster
configuration

10. If your system is in a MetroCluster configuration, verify that each controller is configured: metrocluster
node show - fields configuration-state

57
node1_siteA::> metrocluster node show -fields configuration-state

dr-group-id cluster node configuration-state

----------- ---------------------- --------------
-------------------
1 node1_siteA node1mcc-001 configured
1 node1_siteA node1mcc-002 configured
1 node1_siteB node1mcc-003 configured
1 node1_siteB node1mcc-004 configured

4 entries were displayed.

11. Verify that the expected volumes are present for each controller: vol show -node node-name
12. If you disabled automatic takeover on reboot, enable it from the healthy controller: storage failover
modify -node replacement-node-name -onreboot true

Complete system restoration - AFF C250

To restore your system to full operation, you must restore the NetApp Storage Encryption
configuration (if necessary), and install licenses for the new controller, and return the
failed part to NetApp, as described in the RMA instructions shipped with the kit.

Step 1: Install licenses for the replacement controller in ONTAP

You must install new licenses for the replacement node if the impaired node was using ONTAP features that
require a standard (node-locked) license. For features with standard licenses, each node in the cluster should
have its own key for the feature.

About this task

Until you install license keys, features requiring standard licenses continue to be available to the replacement
node. However, if the impaired node was the only node in the cluster with a license for the feature, no
configuration changes to the feature are allowed.

Also, using unlicensed features on the node might put you out of compliance with your license agreement, so
you should install the replacement license key or keys on the replacement node as soon as possible.

Before you begin

The licenses keys must be in the 28-character format.

You have a 90-day grace period in which to install the license keys. After the grace period, all old licenses are
invalidated. After a valid license key is installed, you have 24 hours to install all of the keys before the grace
period ends.

If your system was initially running ONTAP 9.10.1 or later, use the procedure documented in
Post Motherboard Replacement Process to update Licensing on a AFF/FAS system. If you are
unsure of the initial ONTAP release for your system, see NetApp Hardware Universe for more
information.

Steps

58
1. If you need new license keys, obtain replacement license keys on the NetApp Support Site in the My
Support section under Software licenses.

The new license keys that you require are automatically generated and sent to the email
address on file. If you fail to receive the email with the license keys within 30 days, you
should contact technical support.

2. Install each license key: system license add -license-code license-key, license-key...
3. Remove the old licenses, if desired:
a. Check for unused licenses: license clean-up -unused -simulate
b. If the list looks correct, remove the unused licenses: license clean-up -unused

Step 2: Verify LIFs and registering the serial number

Before returning the replacement node to service, you should verify that the LIFs are on their home ports, and
register the serial number of the replacement node if AutoSupport is enabled, and reset automatic giveback.

Steps
1. Verify that the logical interfaces are reporting to their home server and ports: network interface show
-is-home false

If any LIFs are listed as false, revert them to their home ports: network interface revert -vserver
* -lif *

2. Register the system serial number with NetApp Support.

◦ If AutoSupport is enabled, send an AutoSupport message to register the serial number.
◦ If AutoSupport is not enabled, call NetApp Support to register the serial number.
3. Check the health of your cluster. See the How to perform a cluster health check with a script in ONTAP KB
article for more information.
4. If an AutoSupport maintenance window was triggered, end it by using the system node autosupport
invoke -node * -type all -message MAINT=END command.
5. If automatic giveback was disabled, reenable it: storage failover modify -node local -auto
-giveback true

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
and Replacements page for further information.

Replace a DIMM - AFF C250

You must replace a DIMM in the controller when your storage system encounters errors
such as, excessive CECC (Correctable Error Correction Codes) errors that are based on
Health Monitor alerts or uncorrectable ECC errors, typically caused by a single DIMM
failure preventing the storage system from booting ONTAP.
About this task
All other components in the system must be functioning properly; if not, you must contact technical support.

59
You must replace the failed component with a replacement FRU component you received from your provider.

Step 1: Shut down the impaired controller

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.

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 from the console of the healthy controller: storage failover modify
-node local -auto-giveback false

When you see Do you want to disable auto-giveback?, enter y.

3. Take the impaired controller to the LOADER prompt:

If the impaired controller is Then…

displaying…
The LOADER prompt Go to the next step.

Waiting for giveback… Press Ctrl-C, and then respond y when prompted.

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

When the impaired controller shows Waiting for giveback…, press

Ctrl-C, and then respond y.

60
Step 2: Remove the controller module

You must remove the controller module from the chassis when you replace a component inside the controller
module.

Make sure that you label the cables so that you know where they came from.

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

If you have difficulty removing the controller module, place your index fingers through the
finger holes from the inside (by crossing your arms).

Lever

Latching mechanism

61
Thumbscrew

Controller module cover.

7. Lift out the air duct cover.

62
Step 3: Replace a DIMM

To replace a DIMM, you must locate it in the controller module using the DIMM map label on top of the air duct
and then replace it following the specific sequence of steps.

Use the following video or the tabulated steps to replace a DIMM:

Animation - Replace a DIMM

1. Replace the impaired DIMM on your controller module.

The DIMMs are in slot 3 or 1 on the motherboard. Slot 2 and 4 are left empty. Do not attempt to install
DIMMs into these slots.

63
2. Note the orientation of the DIMM in the socket so that you can insert the replacement DIMM in the proper
orientation.
3. Slowly push apart the DIMM ejector tabs on either side of the DIMM, and slide the DIMM out of the slot.
4. Leave DIMM ejector tabs on the connector in the open position.
5. Remove the replacement DIMM from the antistatic shipping bag, hold the DIMM by the corners, and align it
to the slot.

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

6. Insert the replacement DIMM squarely into the slot.

The DIMMs fit tightly in the socket. If not, reinsert the DIMM to realign it with the socket.

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

Step 4: Install the controller module

After you have replaced the component in the controller module, you must reinstall the controller module into
the chassis, and then boot it.

You can use the following illustrations or the written steps to install the replacement controller module in the
chassis.

1. If you have not already done so, install the air duct.

64
2. Close the controller module cover and tighten the thumbscrew.

65
Controller module cover

Thumbscrew

3. Insert the controller module into the chassis:

The controller module should be fully inserted and flush with the edges of the chassis.

4. Plug the power cords into the power supplies, reinstall the power cable locking collar, and then connect the
power supplies to the power source.

The controller module begins to boot as soon as power is restored. Be prepared to interrupt the boot
process.

5. Recable the system, as needed.

6. Return the controller to normal operation by giving back its storage: storage failover giveback
-ofnode impaired_node_name
7. If automatic giveback was disabled, reenable it: storage failover modify -node local -auto
-giveback true

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

Replace SSD drive - AFF C250

You can replace a failed SSD drive nondisruptively while I/O is in progress.
When a drive fails, the platform logs a warning message to the system console indicating which drive has
failed. In addition, both the fault LED on the operator display panel and the fault LED on the failed drive are
illuminated.

Before you begin

• Follow best practice and install the current version of the Disk Qualification Package (DQP) before
replacing a drive.
• Identify the failed disk drive by running the storage disk show -broken command from the system
console.

66
The failed drive appears in the list of failed drives. If it does not, you should wait, and then run the
command again.

It can take up to several hours for the drive to appear in the list of failed drives.

• Determine whether SED authentication is enabled.

How you replace the disk depends on how the disk drive is being used. If SED authentication is enabled,
you must use the SED replacement instructions in the ONTAP 9 NetApp Encryption Power Guide. These
Instructions describe additional steps you must perform before and after replacing an SED.

• Make sure the replacement drive is supported by your platform. See the NetApp Hardware Universe.
• Make sure all other components in the system are functioning properly; if not, you must contact technical
support.

About this task

Drive firmware is automatically updated (nondisruptively) on new drives that have non-current firmware
versions.

When replacing several disk drives, you must wait 70 seconds between the removal of each failed disk drive
and the insertion of the replacement disk drive to allow the storage system to recognize the existence of each
new disk.

Steps
1. If you want to manually assign drive ownership for the replacement drive, you need to disable automatic
drive assignment replacement drive, if it is enabled

You manually assign drive ownership and then reenable automatic drive assignment later in
this procedure.

a. Verify whether automatic drive assignment is enabled: storage disk option show

You can enter the command on either controller module.

If automatic drive assignment is enabled, the output shows on in the “Auto Assign” column (for each
controller module).

b. If automatic drive assignment is enabled, disable it: storage disk option modify -node
node_name -autoassign off

You must disable automatic drive assignment on both controller modules.

2. Properly ground yourself.

3. Physically identify the failed drive.

When a drive fails, the system logs a warning message to the system console indicating which drive failed.
Additionally, the attention (amber) LED on the drive shelf operator display panel and the failed drive
illuminate.

The activity (green) LED on a failed drive can be illuminated (solid), which indicates that the
drive has power, but should not be blinking, which indicates I/O activity. A failed drive has no
I/O activity.

67
4. Remove the failed drive:
a. Press the release button on the drive face to open the cam handle.
b. Slide the drive out of the shelf using the cam handle and supporting the drive with your other hand.
5. Wait a minimum of 70 seconds before inserting the replacement drive.

This allows the system to recognize that a drive was removed.

6. Insert the replacement drive:

a. With the cam handle in the open position, use both hands to insert the replacement drive.
b. Push until the drive stops.
c. Close the cam handle so that the drive is fully seated into the midplane and the handle clicks into
place.

Be sure to close the cam handle slowly so that it aligns correctly with the face of the drive.

7. Verify that the drive’s activity (green) LED is illuminated.

When the drive’s activity LED is solid, it means that the drive has power. When the drive’s activity LED is
blinking, it means that the drive has power and I/O is in progress. If the drive firmware is automatically
updating, the LED blinks.

8. If you are replacing another drive, repeat Steps 3 through 7.

9. If you disabled automatice drive assignment in Step 1, then, manually assign drive ownership and then
reenable automatic drive assignment if needed.
a. Display all unowned drives: storage disk show -container-type unassigned

You can enter the command on either controller module.

b. Assign each drive: storage disk assign -disk disk_name -owner node_name

You can enter the command on either controller module.

You can use the wildcard character to assign more than one drive at once.

c. Reenable automatic drive assignment if needed: storage disk option modify -node
node_name -autoassign on

You must reenable automatic drive assignment on both controller modules.

10. Return the failed part to NetApp, as described in the RMA instructions shipped with the kit.

Contact technical support at NetApp Support, 888-463-8277 (North America), 00-800-44-638277 (Europe),
or +800-800-80-800 (Asia/Pacific) if you need the RMA number or additional help with the replacement
procedure.

Replace a fan - AFF C250

To replace a fan, remove the failed fan module and replace it with a new fan module.

68
Step 1: Shut down the impaired controller

About this task

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.

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 from the console of the healthy controller: storage failover modify
-node local -auto-giveback false

When you see Do you want to disable auto-giveback?, enter y.

3. Take the impaired controller to the LOADER prompt:

If the impaired controller is Then…

displaying…
The LOADER prompt Go to the next step.

Waiting for giveback… Press Ctrl-C, and then respond y when prompted.

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

When the impaired controller shows Waiting for giveback…, press

Ctrl-C, and then respond y.

Step 2: Remove the controller module

You must remove the controller module from the chassis when you replace a component inside the controller
module.

69
Make sure that you label the cables so that you know where they came from.

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

If you have difficulty removing the controller module, place your index fingers through the
finger holes from the inside (by crossing your arms).

Lever

Latching mechanism

70
Thumbscrew

Controller module cover

Step 3: Replace a fan

To replace a fan, remove the failed fan module and replace it with a new fan module.

Use the following video or the tabulated steps to replace a fan:

Animation - Replace a fan

1. Identify the fan module that you must replace by checking the console error messages or by locating the lit
LED for the fan module on the motherboard.
2. Remove the fan module by pinching the side of the fan module, and then lifting the fan module straight out
of the controller module.

71
Fan module

3. Align the edges of the replacement fan module with the opening in the controller module, and then slide the
replacement fan module into the controller module.

Step 4: Reinstall the controller module

After you replace a component within the controller module, you must reinstall the controller module in the
system chassis and boot it.

1. Close the controller module cover and tighten the thumbscrew.

72
Controller module cover

Thumbscrew

2. Insert the controller module into the chassis:

The controller module should be fully inserted and flush with the edges of the chassis.

f. Plug the power cords into the power supplies, reinstall the power cable locking collar, and then connect
the power supplies to the power source.

The controller module begins to boot as soon as power is restored. Be prepared to interrupt the boot
process.

3. Recable the system, as needed.

73
4. Return the controller to normal operation by giving back its storage: storage failover giveback
-ofnode impaired_node_name
5. If automatic giveback was disabled, reenable it: storage failover modify -node local -auto
-giveback true

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

Replace or install a mezzanine card - AFF C250

To replace a failed mezzanine card, you must remove the cables and any SFP or QSFP
modules, replace the card, reinstall the SFP or QSFP modules and recable the cards. To
install a new mezzanine card, you must have the appropriate cables and SFP or QSFP
modules.
About this task
• You can use this procedure with all versions of ONTAP supported by your system
• All other components in the system must be functioning properly; if not, you must contact technical support.

Step 1: Shut down the impaired controller

About this task

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.

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 from the console of the healthy controller: storage failover modify
-node local -auto-giveback false

When you see Do you want to disable auto-giveback?, enter y.

74
3. Take the impaired controller to the LOADER prompt:

If the impaired controller is Then…

displaying…
The LOADER prompt Go to the next step.

Waiting for giveback… Press Ctrl-C, and then respond y when prompted.

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

When the impaired controller shows Waiting for giveback…, press

Ctrl-C, and then respond y.

Step 2: Remove the controller module

Remove the controller module from the chassis when you replace a component inside the controller module.

Make sure that you label the cables so that you know where they came from.

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

If you have difficulty removing the controller module, place your index fingers through the
finger holes from the inside (by crossing your arms).

Lever

75
Latching mechanism

Thumbscrew

Controller module cover.

Step 3: Replace or install a mezzanine card

To replace a mezzanine card, you must remove the impaired card and install the replacement card; to install a
mezzanine card, you must remove the faceplate and install the new card.

Use the following video or the tabulated steps to replace a mezzanine card:

Animation - Replace a mezzanine card

1. To replace a mezzanine card:

2. Locate and replace the impaired mezzanine card on your controller module.

76
Remove screws on the face of the controller
module.

Loosen the screw in the controller module.

Remove the mezzanine card.

a. Unplug any cabling associated with the impaired mezzanine card.

Make sure that you label the cables so that you know where they came from.

b. Remove any SFP or QSFP modules that might be in the impaired mezzanine card and set it aside.
c. Using the #1 magnetic screwdriver, remove the screws from the face of the controller module and set
them aside safely on the magnet.
d. Using the #1 magnetic screwdriver, loosen the screw on the impaired mezzanine card.
e. Using the #1 magnetic screwdriver, gently lift the impaired mezzanine card directly out of the socket
and set it aside.
f. Remove the replacement mezzanine card from the antistatic shipping bag and align it to the inside face
of the controller module.
g. Gently align the replacement mezzanine card into place.
h. Using the #1 magnetic screwdriver, insert and tighten the screws on the face of the controller module
and on the mezzanine card.

77
Do not apply force when tightening the screw on the mezzanine card; you might crack it.

i. Insert any SFP or QSFP modules that were removed from the impaired mezzanine card to the
replacement mezzanine card.
3. To install a mezzanine card:
4. You install a new mezzanine card if your system does not have one.
a. Using the #1 magnetic screwdriver, remove the screws from the face of the controller module and the
faceplate covering the mezzanine card slot, and set them aside safely on the magnet.
b. Remove the mezzanine card from the antistatic shipping bag and align it to the inside face of the
controller module.
c. Gently align the mezzanine card into place.
d. Using the #1 magnetic screwdriver, insert and tighten the screws on the face of the controller module
and on the mezzanine card.

Do not apply force when tightening the screw on the mezzanine card; you might crack it.

Step 4: Reinstall the controller module

After you replace a component within the controller module, you must reinstall the controller module in the
system chassis and boot it.

1. Close the controller module cover and tighten the thumbscrew.

78
Controller module cover

Thumbscrew

2. Insert the controller module into the chassis:

The controller module should be fully inserted and flush with the edges of the chassis.

f. Plug the power cords into the power supplies, reinstall the power cable locking collar, and then connect
the power supplies to the power source.

The controller module begins to boot as soon as power is restored. Be prepared to interrupt the boot
process.

3. Recable the system, as needed.

4. Return the controller to normal operation by giving back its storage: storage failover giveback
-ofnode impaired_node_name
5. If automatic giveback was disabled, reenable it: storage failover modify -node local -auto
-giveback true

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

Replace the NVMEM battery - AFF C250

To replace an NVMEM battery in the system, you must remove the controller module from
the system, open it, replace the battery, and close and replace the controller module.
All other components in the system must be functioning properly; if not, you must contact technical support.

Step 1: Shut down the impaired controller

About this task

• If you have a SAN system, you must have checked event messages (cluster kernel-service show)

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

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 from the console of the healthy controller: storage failover modify
-node local -auto-giveback false

When you see Do you want to disable auto-giveback?, enter y.

3. Take the impaired controller to the LOADER prompt:

If the impaired controller is Then…

displaying…
The LOADER prompt Go to the next step.

Waiting for giveback… Press Ctrl-C, and then respond y when prompted.

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

When the impaired controller shows Waiting for giveback…, press

Ctrl-C, and then respond y.

Step 2: Remove the controller module

You must remove the controller module from the chassis when you replace a component inside the controller
module.

Make sure that you label the cables so that you know where they came from.

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

2. Unplug the controller module power supplies from the source.
3. Release the power cable retainers, and then unplug the cables from the power supplies.

80
4. Insert your forefinger into the latching mechanism on either side of the controller module, press the lever
with your thumb, and gently pull the controller a few inches out of the chassis.

If you have difficulty removing the controller module, place your index fingers through the
finger holes from the inside (by crossing your arms).

Lever

Latching mechanism

81
Thumbscrew

Controller module cover.

Step 3: Replace the NVMEM battery

To replace the NVMEM battery, you must remove the failed battery from the controller module and install the
replacement battery into the controller module.

Use the following video or the tabulated steps to replace the NVMEM battery:

Animation - Replace the NVMEM battery

1. Locate and replace the impaired NVMEM battery on your controller module.

It is recommended that you follow the illustrated instructions in the order listed.

82
Squeeze the clip on the face of the battery plug.

Unplug the battery cable from the socket.

Grasp the battery and press the blue locking tab

marked PUSH.

Lift the battery out of the holder and controller

module.

2. Locate the battery plug and squeeze the clip on the face of the battery plug to release the plug from the
socket.
3. Grasp the battery and press the blue locking tab marked PUSH, and then lift the battery out of the holder
and controller module and set it aside.
4. Remove the replacement NV battery from the antistatic shipping bag and align it to the battery holder.
5. Insert the replacement NV battery plug into the socket.
6. 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.
7. Press firmly down on the battery pack to make sure that it is locked into place.

83
Step 4: Install the controller module

After you have replaced the component in the controller module, you must reinstall the controller module into
the chassis, and then boot it.

You can use the following illustration or the written steps to install the replacement controller module in the
chassis.

1. Close the controller module cover and tighten the thumbscrew.

Controller module cover

Thumbscrew

2. Insert the controller module into the chassis:

84
The controller module should be fully inserted and flush with the edges of the chassis.

f. Plug the power cords into the power supplies, reinstall the power cable locking collar, and then connect
the power supplies to the power source.

The controller module begins to boot as soon as power is restored. Be prepared to interrupt the boot
process.

3. Recable the system, as needed.

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

Replace a power supply - AFF C250

Replacing a power supply (PSU) involves disconnecting the target PSU from the power
source, unplugging the power cable, removing the old PSU and installing the replacement
PSU, and then reconnecting it to the power source.
• The power supplies are redundant and hot-swappable.
• This procedure is written for replacing one PSU at a time.

It is a best practice to replace the PSU within two minutes of removing it from the chassis.
The system continues to function, but ONTAP sends messages to the console about the
degraded PSU until the PSU is replaced.

• Power supplies are auto-ranging.

Do not mix PSUs with different efficiency ratings. Always replace like for like.

Use the appropriate procedure for your type of PSU; AC or DC.

85
Option 1: Replace an AC PSU
Use the following video or the tabulated steps to replace the PSU:

Animation - Replace the AC PSU

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

2. Identify the PSU you want to replace, based on console error messages or through the red Fault LED
on the PSU.
3. Disconnect the PSU:
a. Open the power cable retainer, and then unplug the power cable from the PSU.
4. Remove the PSU by rotating the handle up, press the locking tab, and then pull the PSU out of the
controller module.

The PSU is short. Always use two hands to support it when removing it from the
controller module so that it does not suddenly swing free from the controller module
and injure you.

Blue PSU locking tab

Power supply

5. Install the replacement PSU in the controller module:

a. Using both hands, support and align the edges of the PSU with the opening in the controller
module.

86
b. Gently push the PSU into the controller module until the locking tab clicks into place.

The power supplies will only properly engage with the internal connector and lock in place one
way.

To avoid damaging the internal connector, do not use excessive force when sliding
the PSU into the system.

6. Reconnect the PSU cabling:

a. Reconnect the power cable to the PSU.

b. Secure the power cable to the PSU using the power cable retainer.
Once power is restored to the PSU, the status LED should be green.

7. Return the failed part to NetApp, as described in the RMA instructions shipped with the kit. See the
Part Return and Replacements page for further information.

Option 2: Replace a DC PSU

To replace a DC PSU, complete the following steps.

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

2. Identify the PSU you want to replace, based on console error messages or through the red Fault LED
on the PSU.
3. Disconnect the PSU:
a. Unscrew the D-SUB DC power cable connector using the thumb screws on the plug.
b. Unplug the power cable from the PSU and set it aside.
4. Remove the PSU by rotating the handle up, press the locking tab, and then pull PSU out of the
controller module.

The PSU is short. Always use two hands to support it when removing it from the
controller module so that it does not suddenly swing free from the controller module
and injure you.

Thumb screws

D-SUB DC power cable connector

87
Power supply handle

Blue PSU locking tab

5. Install the replacement PSU in the controller module:

a. Using both hands, support and align the edges of the PSU with the opening in the controller
module.
b. Gently push the PSU into the controller module until the locking tab clicks into place.

The power supplies will only properly engage with the internal connector and lock in place one
way.

To avoid damaging the internal connector, do not use excessive force when sliding
the PSU into the system.

6. Reconnect the D-SUB DC power cable:

a. Plug the power cable connector into the PSU.
b. Secure the power cable to the PSU with the thumbscrews.

Once power is restored to the PSU, the status LED should be green.

7. Return the failed part to NetApp, as described in the RMA instructions shipped with the kit. See the
Part Return and Replacements page for further information.

Replace the real-time clock battery - AFF C250

You replace the real-time clock (RTC) battery in the controller module so that your
system’s services and applications that depend on accurate time synchronization
continue to function.
• You can use this procedure with all versions of ONTAP supported by your system
• All other components in the system must be functioning properly; if not, you must contact technical support.

Step 1: Shut down the impaired controller

About this task

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.

88
• 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 from the console of the healthy controller: storage failover modify
-node local -auto-giveback false

When you see Do you want to disable auto-giveback?, enter y.

3. Take the impaired controller to the LOADER prompt:

If the impaired controller is Then…

displaying…
The LOADER prompt Go to the next step.

Waiting for giveback… Press Ctrl-C, and then respond y when prompted.

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

When the impaired controller shows Waiting for giveback…, press

Ctrl-C, and then respond y.

Step 2: Remove the controller module

You must remove the controller module from the chassis when you replace a component inside the controller
module.

Make sure that you label the cables so that you know where they came from.

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

If you have difficulty removing the controller module, place your index fingers through the
finger holes from the inside (by crossing your arms).

89
Lever

Latching mechanism

90
Thumbscrew

Controller module cover.

7. Lift out the air duct cover.

Step 3: Replace the RTC battery

To replace the RTC battery, locate it inside the controller and follow the specific sequence of steps.

Use the following video or the tabulated steps to replace the RTC battery:

Animation - Replace the RTC battery

1. Locate the RTC battery between the heatsink and the midplane and remove it exactly as shown in the
graphic.

91
Gently pull tab away from the battery housing. Attention: Pulling it away
aggressively might displace the tab.

Lift the battery up. Note: Make a note of the polarity of the battery.

The battery should eject out.

The battery will be ejected out.

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

3. Locate the RTC battery holder between the heatsink and the midplane and insert it exactly as shown in the
graphic.

92
With positive polarity face up, slide the battery under
the tab of the battery housing.

Push the battery gently into place and make sure

the tab secures it to the housing.

Pushing it in aggressively might

cause the battery to eject out again.

4. Visually inspect the battery to make sure that it is completely installed into the holder and that the polarity is
correct.

Step 4: Reinstall the controller module and setting time/date after RTC battery replacement

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.

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

93
optic cables.

4. Insert the controller module into the chassis:

The controller module begins to boot as soon as power is restored. Be prepared to interrupt the boot
process.

g. Halt the controller at the LOADER prompt.

5. Reset the time and date on the controller:
a. Check the date and time on the healthy controller with the show date command.
b. At the LOADER prompt on the target controller, 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 controller.
6. At the LOADER prompt, enter bye to reinitialize the PCIe cards and other components and let the
controller reboot.
7. Return the controller to normal operation by giving back its storage: storage failover giveback
-ofnode impaired_node_name
8. If automatic giveback was disabled, reenable it: storage failover modify -node local -auto
-giveback true

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

94
Copyright information

Copyright © 2025 NetApp, Inc. All Rights Reserved. Printed in the U.S. No part of this document covered by
copyright may be reproduced in any form or by any means—graphic, electronic, or mechanical, including
photocopying, recording, taping, or storage in an electronic retrieval system—without prior written permission
of the copyright owner.

Software derived from copyrighted NetApp material is subject to the following license and disclaimer:

THIS SOFTWARE IS PROVIDED BY NETAPP “AS IS” AND WITHOUT ANY EXPRESS OR IMPLIED
WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY
AND FITNESS FOR A PARTICULAR PURPOSE, WHICH ARE HEREBY DISCLAIMED. IN NO EVENT SHALL
NETAPP BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE
GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER
CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

NetApp reserves the right to change any products described herein at any time, and without notice. NetApp
assumes no responsibility or liability arising from the use of products described herein, except as expressly
agreed to in writing by NetApp. The use or purchase of this product does not convey a license under any
patent rights, trademark rights, or any other intellectual property rights of NetApp.

The product described in this manual may be protected by one or more U.S. patents, foreign patents, or
pending applications.

LIMITED RIGHTS LEGEND: Use, duplication, or disclosure by the government is subject to restrictions as set
forth in subparagraph (b)(3) of the Rights in Technical Data -Noncommercial Items at DFARS 252.227-7013
(FEB 2014) and FAR 52.227-19 (DEC 2007).

Data contained herein pertains to a commercial product and/or commercial service (as defined in FAR 2.101)
and is proprietary to NetApp, Inc. All NetApp technical data and computer software provided under this
Agreement is commercial in nature and developed solely at private expense. The U.S. Government has a non-
exclusive, non-transferrable, nonsublicensable, worldwide, limited irrevocable license to use the Data only in
connection with and in support of the U.S. Government contract under which the Data was delivered. Except
as provided herein, the Data may not be used, disclosed, reproduced, modified, performed, or displayed
without the prior written approval of NetApp, Inc. United States Government license rights for the Department
of Defense are limited to those rights identified in DFARS clause 252.227-7015(b) (FEB 2014).

Trademark information

NETAPP, the NETAPP logo, and the marks listed at http://www.netapp.com/TM are trademarks of NetApp, Inc.
Other company and product names may be trademarks of their respective owners.

Veritas NetBackup Backup Planning and Performance Tuning Guide
No ratings yet
Veritas NetBackup Backup Planning and Performance Tuning Guide
172 pages
Feature Briefing - NetBackup 7 1 - Auto Image Replication
No ratings yet
Feature Briefing - NetBackup 7 1 - Auto Image Replication
9 pages
NetBackup Version Comparison Chart
No ratings yet
NetBackup Version Comparison Chart
8 pages
ActiveCluster Requirements and Best Practices
No ratings yet
ActiveCluster Requirements and Best Practices
11 pages
NetBackup101 AdminGuideI Server
No ratings yet
NetBackup101 AdminGuideI Server
1,283 pages
Nim Upgrade and Advanced Topics
No ratings yet
Nim Upgrade and Advanced Topics
49 pages
Config Advisor 4.4 Installation and Administration Guide
No ratings yet
Config Advisor 4.4 Installation and Administration Guide
122 pages
DR Solutions Guide
No ratings yet
DR Solutions Guide
16 pages
Data Domain and Symantec NetBackup 7.0 and Later Integration Guide
No ratings yet
Data Domain and Symantec NetBackup 7.0 and Later Integration Guide
42 pages
NetBackup10 EEB Guide
No ratings yet
NetBackup10 EEB Guide
124 pages
TRG Template - Backup
No ratings yet
TRG Template - Backup
98 pages
NetBackup Upgrade and Migration Guide
No ratings yet
NetBackup Upgrade and Migration Guide
7 pages
6-66880-17 RevA I6k Maint Guide I13
No ratings yet
6-66880-17 RevA I6k Maint Guide I13
776 pages
NetBackup Catalog Overview Guide
No ratings yet
NetBackup Catalog Overview Guide
3 pages
Architecture & Consideration
No ratings yet
Architecture & Consideration
7 pages
Netbackup 8.0 Blueprint Exchange
No ratings yet
Netbackup 8.0 Blueprint Exchange
36 pages
CVTSP24 - Module 06 - Metallic Introduction
No ratings yet
CVTSP24 - Module 06 - Metallic Introduction
20 pages
VCS-285 NBU10.x App5.x ExamPreparationGuide
No ratings yet
VCS-285 NBU10.x App5.x ExamPreparationGuide
8 pages
Veritas Netbackup 8.0 Blueprint Accelerator
No ratings yet
Veritas Netbackup 8.0 Blueprint Accelerator
29 pages
HPE StoreOnce Catalyst Store Overview
No ratings yet
HPE StoreOnce Catalyst Store Overview
6 pages
Configuring Local Storage
No ratings yet
Configuring Local Storage
28 pages
NetBackup SLP & AIR Guide
No ratings yet
NetBackup SLP & AIR Guide
40 pages
4112-3 ONTAP Select Fundamentals - Architecture, Performance, Value
No ratings yet
4112-3 ONTAP Select Fundamentals - Architecture, Performance, Value
35 pages
NetBackup Training Module1
100% (1)
NetBackup Training Module1
35 pages
MetroCluster FC FAQ-9.7 - v1.10 PDF
No ratings yet
MetroCluster FC FAQ-9.7 - v1.10 PDF
30 pages
EMC Networker and EMC Data Domain Boost Duplication Devices
No ratings yet
EMC Networker and EMC Data Domain Boost Duplication Devices
108 pages
Customer Presentation - Unity Overview4
No ratings yet
Customer Presentation - Unity Overview4
26 pages
Clustered Data ONTAP 82 Network Management Guide
No ratings yet
Clustered Data ONTAP 82 Network Management Guide
109 pages
STRHW ILT COMNESES FinalAssessment StudentHandout
0% (1)
STRHW ILT COMNESES FinalAssessment StudentHandout
18 pages
HPE StoreEasy 1870 Storage With Microsoft Windows Server IoT 2022 Data sheet-PSN1014773236UAEN
No ratings yet
HPE StoreEasy 1870 Storage With Microsoft Windows Server IoT 2022 Data sheet-PSN1014773236UAEN
5 pages
Overview of Storage in Windows Server 2016
No ratings yet
Overview of Storage in Windows Server 2016
49 pages
DS8 STS 20feb2012 PDF
No ratings yet
DS8 STS 20feb2012 PDF
525 pages
VMware AirWatch Database Migration Guide
No ratings yet
VMware AirWatch Database Migration Guide
43 pages
Veritas Backup Exec 9.0 For Windows Servers Administartor's Guide
No ratings yet
Veritas Backup Exec 9.0 For Windows Servers Administartor's Guide
1,296 pages
M100 - Quickstart Guide PDF
No ratings yet
M100 - Quickstart Guide PDF
4 pages
Overview of System Center DPM 2019
No ratings yet
Overview of System Center DPM 2019
7 pages
Detailed Course Outline Netapp C-Mode
No ratings yet
Detailed Course Outline Netapp C-Mode
2 pages
PureDisk Best Practices
No ratings yet
PureDisk Best Practices
32 pages
IBM Systems Storage Toolbox V4
100% (1)
IBM Systems Storage Toolbox V4
44 pages
NetBackup Error Code 84: Media Write Issues
No ratings yet
NetBackup Error Code 84: Media Write Issues
6 pages
Dell Emc Powerprotect DD Virtual Edition On Microsoft Azure: Technical White Paper
No ratings yet
Dell Emc Powerprotect DD Virtual Edition On Microsoft Azure: Technical White Paper
28 pages
h7296 Data Domain Boost Openstorage WP PDF
No ratings yet
h7296 Data Domain Boost Openstorage WP PDF
45 pages
Hedvig Architecture Overview PDF
No ratings yet
Hedvig Architecture Overview PDF
27 pages
RecoverPoint Deployment FAQs and Considerations
No ratings yet
RecoverPoint Deployment FAQs and Considerations
15 pages
NetApp Storage RFP for Nanaimo
100% (1)
NetApp Storage RFP for Nanaimo
42 pages
HPE Ransomware Protection Strategies
No ratings yet
HPE Ransomware Protection Strategies
62 pages
Metrocluster Ip Architecture and Design en
No ratings yet
Metrocluster Ip Architecture and Design en
34 pages
VASCM10 Exam Study Guide
No ratings yet
VASCM10 Exam Study Guide
7 pages
Dynamic Root Disk A.3.13 Administrator's Guide: HP-UX 11i v2, HP-UX 11i v3
No ratings yet
Dynamic Root Disk A.3.13 Administrator's Guide: HP-UX 11i v2, HP-UX 11i v3
67 pages
NetBackup Copilot Configuration Guide - 2.7.3
No ratings yet
NetBackup Copilot Configuration Guide - 2.7.3
50 pages
NetBackup 7.7.3 Upgrade Guide
No ratings yet
NetBackup 7.7.3 Upgrade Guide
130 pages
NetApp Data ONTAP Features Guide
No ratings yet
NetApp Data ONTAP Features Guide
2 pages
What Is A SAN: UC434S G.00
No ratings yet
What Is A SAN: UC434S G.00
33 pages
Centrify DC Directcontrol Express Admin Guide
No ratings yet
Centrify DC Directcontrol Express Admin Guide
178 pages
Veeam Backup 9 0 Summary
No ratings yet
Veeam Backup 9 0 Summary
4 pages
AFF A400/C400 Controller Replacement Guide
No ratings yet
AFF A400/C400 Controller Replacement Guide
103 pages
AFF A400 Installation and Setup Guide
No ratings yet
AFF A400 Installation and Setup Guide
123 pages
FAS9500 Systems
No ratings yet
FAS9500 Systems
99 pages
AFF A400 Systems: Installation and Setup Instructions
No ratings yet
AFF A400 Systems: Installation and Setup Instructions
5 pages
AFF A220 & FAS2700 Setup Guide
No ratings yet
AFF A220 & FAS2700 Setup Guide
4 pages
Timing The Rotax
No ratings yet
Timing The Rotax
3 pages
Sushant's Java Based Technology Blog - 22. Profile Options Related To OAF
No ratings yet
Sushant's Java Based Technology Blog - 22. Profile Options Related To OAF
3 pages
Can We Teach Robots Ethics
No ratings yet
Can We Teach Robots Ethics
3 pages
Crazy Hoop Manual 2 EAECDD679CDEE
No ratings yet
Crazy Hoop Manual 2 EAECDD679CDEE
38 pages
Brochure Adtechno HD10UTR 100M Extender
No ratings yet
Brochure Adtechno HD10UTR 100M Extender
2 pages
Fifth Generation Computer
No ratings yet
Fifth Generation Computer
15 pages
Component-Based Software Engineering
No ratings yet
Component-Based Software Engineering
7 pages
Green IT Recycling Center - Company Profile
No ratings yet
Green IT Recycling Center - Company Profile
8 pages
CS 300 Data Structures: Sabancı University Faculty of Engineering and Natural Sciences
No ratings yet
CS 300 Data Structures: Sabancı University Faculty of Engineering and Natural Sciences
6 pages
Case Study
No ratings yet
Case Study
5 pages
Engineering Drawings Service Proposal - 11282022
No ratings yet
Engineering Drawings Service Proposal - 11282022
2 pages
Indua Bulls Co Cat List
50% (2)
Indua Bulls Co Cat List
2,418 pages
Network Reconnaissance Tools Lab
No ratings yet
Network Reconnaissance Tools Lab
4 pages
Redthread Learning Technology Ecosystems - 092019
100% (2)
Redthread Learning Technology Ecosystems - 092019
38 pages
Compressor - NJ2212GJ (LBP) - Datasheet
100% (1)
Compressor - NJ2212GJ (LBP) - Datasheet
5 pages
Women Safety Device and Application-FEMME
No ratings yet
Women Safety Device and Application-FEMME
7 pages
Nam June Paik: Pioneer of Video Art
100% (2)
Nam June Paik: Pioneer of Video Art
4 pages
Green Engine Technology Overview
No ratings yet
Green Engine Technology Overview
23 pages
Full Stack Web Development Specialization v2 Brochure
No ratings yet
Full Stack Web Development Specialization v2 Brochure
21 pages
University Management System (Ums) in Powepoint
No ratings yet
University Management System (Ums) in Powepoint
16 pages
MCS-022 Solved Assignment 2024-25
No ratings yet
MCS-022 Solved Assignment 2024-25
23 pages
Compact Home: Technical Catalog
No ratings yet
Compact Home: Technical Catalog
48 pages
KRCL Experience Certificate
No ratings yet
KRCL Experience Certificate
3 pages
Display Data Channel Command Interface (DDC/CI) Standard
No ratings yet
Display Data Channel Command Interface (DDC/CI) Standard
43 pages
Instruction and Maintenance Manual Bay Valves 90001
No ratings yet
Instruction and Maintenance Manual Bay Valves 90001
39 pages
Huawei Cloud Certification Guide
No ratings yet
Huawei Cloud Certification Guide
56 pages
U3 l1 Transistor at Low Frequencies
No ratings yet
U3 l1 Transistor at Low Frequencies
8 pages
Chapter 4 Protection of Alternator Transformer
No ratings yet
Chapter 4 Protection of Alternator Transformer
33 pages
PowerFlex 40 Backdoor Password
No ratings yet
PowerFlex 40 Backdoor Password
2 pages
Chapter 2 (Netacad Quiz)
No ratings yet
Chapter 2 (Netacad Quiz)
8 pages