NetApp ASA C Series Instruction sheet

ASA C-series systems
Install and maintain
NetApp
October 20, 2023
This PDF was generated from https://docs.netapp.com/us-en/ontap-systems/asa-c250/install-setup.html
on October 20, 2023. Always check docs.netapp.com for the latest.

Table of Contents
All SAN Array (ASA) C-series Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê1
ASA C250 systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê1

All SAN Array (ASA) C-series Systems
ASA 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 - ASA 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:
•English: ASA A250 Installation and Setup Instructions
•Japanese: ASA A250 Systems Installation and Setup Instructions
•Chinese: ASA A250 Systems Installation and Setup Instructions
Videos - ASA C250
The following video shows how to install and cable your new system.
Animation - Installation and Setup of an AFF A250
The ASA C250 uses the same installation procedure as the AFF A250 system.
Detailed steps - ASA C250
This section gives detailed step-by-step instructions for installing an ASA C250 system.
1

Step 1: Prepare for installation
To install your AFF A250 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.
Customers with specific power requirements must check HWU for their configuration options.
Before you begin
•Make sure you have access to the NetApp Hardware Universe (HWU) for information about site
requirements.
•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 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;
X66240-2 (112-00573), 2m
Cluster interconnect network
X66240A-2 (112-00598), 2m;
X66240A-5 (112-00600), 5m
Data
100 GbE cable X66211-2 (112-00574), 2m;
X66211-5 (112-00576), 5m
Storage
2

Type of cable… Part number and length Connector type For…
RJ-45 (order
dependent)
Not applicable Management network (BMC and
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
console cable
Not applicable Console connection during
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 method.
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 two-node switchless cluster
Steps
1. Use the the 25GbE cluster interconnect cable to connect the cluster interconnect ports e0c to e0c and
e0d to e0d.
:
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 steps to complete the cabling between the controllers and the switches. Perform
the steps on each controller.
Animation - Cable switched cluster
Steps
1. Cable the cluster interconnect ports e0c and e0d to the 25 GbE cluster interconnect switches.
2. Cable the wrench ports to the management network switches with the RJ45 cables.
5

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 following step on each controller module.
Steps
1. Cable ports 2a through 2d to the FC host switches.
Option 2: Cable to 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 following 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.
Animation - Cable the controllers to a single NS224
Steps
1. Cable controller A to the shelf.
8

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. 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.
2. Make sure that your laptop has network discovery enabled.
See your laptop’s online help for more information.
3. Use the animation to connect your laptop to the Management switch:
Animation - Connect your laptop to the Management switch
4. Select an ONTAP icon listed to discover:
a. Open File Explorer.
b. Click Network in the left pane.
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.
5. Use System Manager guided setup to configure your system using the data you collected in the
ONTAP Configuration Guide.
6. Verify the health of your system by running Config Advisor.
7. After you have completed the initial configuration, go to the ONTAP & ONTAP System Manager
10

Documentation Resources page 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 switch on the management subnet.
c. Assign a TCP/IP address to the laptop or console, using one that is on the management subnet.
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. Assign an initial node management IP address to one of the nodes.
If the management network
has DHCP…
Then…
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.
4. 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.
11

b. Configure the system using the data you collected in the ONTAP Configuration Guide.
5. Verify the health of your system by running Config Advisor.
6. After you have completed the initial configuration, go to the ONTAP & ONTAP System Manager
Documentation Resources page for information about configuring additional features in ONTAP.
Maintain
Maintain ASA C250 hardware
For the ASA C250 storage system, you can perform maintenance procedures on the
following components.
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.
NVEM 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.
12

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 - ASA 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.
•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 onboard encryption keys - ASA C250
Prior to shutting down the impaired controller and checking the status of the onboard
encryption keys, you must check the status of the impaired controller, disable automatic
giveback, and check which version of ONTAP is running on the system.
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 the Synchronize a node with the cluster.
Steps
1. Check the status of the impaired controller:
◦If the impaired controller is at the login prompt, log in as admin.
◦If the impaired controller is at the LOADER prompt and is part of HA configuration, log in as admin on
the healthy controller.
◦If the impaired controller is in a standalone configuration and at LOADER prompt, contact
mysupport.netapp.com.
2. If AutoSupport is enabled, suppress automatic case creation by invoking an AutoSupport message:
13

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
3. Check the version of ONTAP the system is running on the impaired controller if up, or on the partner
controller if the impaired controller is down, using the version -v command:
◦If <lno-DARE> or <1Ono-DARE> is displayed in the command output, the system does not support
NVE, proceed to shut down the controller.
◦If <lno-DARE> is not displayed in the command output, and the system is running ONTAP 9.6 or later,
go to the next section.
4. If the impaired controller is part of an HA configuration, disable automatic giveback from the healthy
controller: storage failover modify -node local -auto-giveback false or storage
failover modify -node local -auto-giveback-after-panic false
Check NVE or NSE on systems running ONTAP 9.6 and later
Before shutting down the impaired controller, you need to verify whether the system has either NetApp Volume
Encryption (NVE) or NetApp Storage Encryption (NSE) enabled. If so, you need to verify the configuration.
1. Verify whether NVE is in use for any volumes in the cluster: volume show -is-encrypted true
If any volumes are listed in the output, NVE is configured and you need to verify the NVE configuration. If
no volumes are listed, check whether NSE is configured and in use.
2. Verify whether NSE is configured and in use: storage encryption disk show
◦If the command output lists the drive details with Mode & Key ID information, NSE is configured and
you need to verify the NSE configuration and in use.
◦If no disks are shown, NSE is not configured.
◦If NVE and NSE are not configured, no drives are protected with NSE keys, it’s safe to shut down the
impaired controller.
Verify NVE configuration
1. Display the key IDs of the authentication keys that are stored on the key management servers: security
key-manager key query
After the ONTAP 9.6 release, you may have additional key manager types. The types are
KMIP, AKV, and GCP. The process for confirming these types is the same as confirming
external or onboard key manager types.
◦If the Key Manager type displays external and the Restored column displays yes, it’s safe to shut
down the impaired controller.
◦If the Key Manager type displays onboard and the Restored column displays yes, you need to
complete some additional steps.
◦If the Key Manager type displays external and the Restored column displays anything other than
yes, you need to complete some additional steps.
14

◦If the Key Manager type displays onboard and the Restored column displays anything other than
yes, you need to complete some additional steps.
2. If the Key Manager type displays onboard and the Restored column displays yes, manually back up
the OKM information:
a. Go to advanced privilege mode and enter ywhen prompted to continue: set -priv advanced
b. Enter the 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. Return to admin mode: set -priv admin
e. Shut down the impaired controller.
3. If the Key Manager type displays external and the Restored column displays anything other than
yes:
a. Restore the external key management authentication keys to all nodes in the cluster: security key-
manager external restore
If the command fails, contact NetApp Support.
mysupport.netapp.com
b. Verify that the Restored column equals yes for all authentication keys: security key-manager
key query
c. Shut down the impaired controller.
4. If the Key Manager type displays onboard and the Restored column displays anything other than yes:
a. Enter the onboard security key-manager sync command: security key-manager onboard sync
Enter the customer’s 32 character, alphanumeric onboard key management passphrase
at the prompt. If the passphrase cannot be provided, contact NetApp Support.
mysupport.netapp.com
b. Verify the Restored column shows yes for all authentication keys: security key-manager key
query
c. Verify that the Key Manager type shows onboard, and then manually back up the OKM information.
d. Go to advanced privilege mode and enter ywhen prompted to continue: set -priv advanced
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. Return to admin mode: set -priv admin
h. You can safely shut down the controller.
15

Verify NSE configuration
1. Display the key IDs of the authentication keys that are stored on the key management servers: security
key-manager key query -key-type NSE-AK
After the ONTAP 9.6 release, you may have additional key manager types. The types are
KMIP, AKV, and GCP. The process for confirming these types is the same as confirming
external or onboard key manager types.
◦If the Key Manager type displays external and the Restored column displays yes, it’s safe to shut
down the impaired controller.
◦If the Key Manager type displays onboard and the Restored column displays yes, you need to
complete some additional steps.
◦If the Key Manager type displays external and the Restored column displays anything other than
yes, you need to complete some additional steps.
◦If the Key Manager type displays external and the Restored column displays anything other than
yes, you need to complete some additional steps.
2. If the Key Manager type displays onboard and the Restored column displays yes, manually back up
the OKM information:
a. Go to advanced privilege mode and enter ywhen prompted to continue: set -priv advanced
b. Enter the 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. Return to admin mode: set -priv admin
e. You can safely shut down the controller.
3. If the Key Manager type displays external and the Restored column displays anything other than
yes:
a. Restore the external key management authentication keys to all nodes in the cluster: security key-
manager external restore
If the command fails, contact NetApp Support.
mysupport.netapp.com
b. Verify that the Restored column equals yes for all authentication keys: security key-manager
key query
c. You can safely shut down the controller.
4. If the Key Manager type displays onboard and the Restored column displays anything other than yes:
a. Enter the onboard security key-manager sync command: security key-manager onboard sync
Enter the customer’s 32 character, alphanumeric onboard key management passphrase at the prompt.
If the passphrase cannot be provided, contact NetApp Support.
mysupport.netapp.com
16

b. Verify the Restored column shows yes for all authentication keys: security key-manager key
query
c. Verify that the Key Manager type shows onboard, and then manually back up the OKM information.
d. Go to advanced privilege mode and enter ywhen prompted to continue: set -priv advanced
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. Return to admin mode: set -priv admin
h. You can safely shut down the controller.
Shut down the controller - ASA 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
displays…
Then…
The LOADER prompt Go to Remove controller module.
Waiting for giveback… Press Ctrl-C, and then respond ywhen prompted.
System prompt or password
prompt (enter system password)
Take over or halt the impaired controller from the healthy controller:
storage failover takeover -ofnode
impaired_node_name
When the impaired controller shows Waiting for giveback…, press
Ctrl-C, and then respond y.
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.
17

To shut down the impaired controller, you must determine the status of the controller and, if necessary, take
over the controller so that the healthy controller continues to serve data from the impaired controller storage.
•If you have a cluster with more than two nodes, it must be in quorum. If the cluster is not in quorum or a
healthy controller shows false for eligibility and health, you must correct the issue before shutting down the
impaired controller; see Synchronize a node with the cluster.
•If you have a MetroCluster configuration, you must have confirmed that the MetroCluster Configuration
State is configured and that the nodes are in an enabled and normal state (metrocluster node show).
Steps
1. If AutoSupport is enabled, suppress automatic case creation by invoking an AutoSupport 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
displaying…
Then…
The LOADER prompt Go to Remove controller module.
Waiting for giveback… Press Ctrl-C, and then respond ywhen prompted.
System prompt or password
prompt (enter system password)
Take over or halt the impaired controller from the healthy controller:
storage failover takeover -ofnode
impaired_node_name
When the impaired controller shows Waiting for giveback…, press
Ctrl-C, and then respond y.
Replace the boot media - ASA 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.
18