NetApp ASA A400 User manual

ASA A400 systems
Install and maintain
NetApp
July 28, 2023
This PDF was generated from https://docs.netapp.com/us-en/ontap-systems/asa400/install-setup.html on
July 28, 2023. Always check docs.netapp.com for the latest.

Table of Contents
ASA A400 systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê1
Install and setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê1
Maintain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê13

ASA A400 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.
For MetroCluster configurations, see either:
•Install MetroCluster IP configuration
•Install MetroCluster Fabric-Attached configuration
Quick guide - ASA A400
This page 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 A400 Installation and Setup Instructions
The ASA A400 uses the same installation procedure as the AFF A400 system.
Videos - ASA A400
There are two videos; one showing how to rack and cable your system and one showing
an example of using the System Manager Guided Setup to perform initial system
configuration.
Video one of two: Hardware installation and cabling
The following video shows how to install and cable your new system.
Animation - AFF A400 Installation and setup instructions
1

The ASA A400 uses the same installation procedure as the AFF A400 system.
Video two of two: Perform end-to-end software configuration
The following video shows end-to-end software configuration for systems running ONTAP 9.2 and later.
[] | https://img.youtube.com/vi/WAE0afWhj1c?/maxresdefault.jpg
Detailed guide - ASA A400
This page provides detailed step-by-step instructions for installing a typical NetApp
system. Use this guide if you want more detailed installation instructions.
Step 1: Prepare for installation
To install your system, you need to create an account, register the system, and get license keys. You also need
to inventory the appropriate number and type of cables for your system and collect specific network
information.
Before you begin
You need to have access to the Hardware Universe for information about site requirements as well as
additional information on your configured system. You might also want to have access to the Release Notes for
your version of ONTAP for more information about this system.
NetApp Hardware Universe
Find the Release Notes for your version of ONTAP 9
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. 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 Hardware Universe to locate the cable and identify its use.
NetApp Hardware Universe
2

Type of cable… Part number and length Connector type For…
100 GbE cable
(QSF(28)
X66211A-05 (112-00595), 0.5m
X66211A-1 (112-00573), 1m
X66211A-2 (112-00574), 2m
X66211A-5 (112-00574), 5m
Storage, cluster interconnect/HA,
and Ethernet data (order-
dependent)
25 GbE cable
(SFP28s)
X66240-2 (112-00598), 2m
X66240-5 (112-00639), 5m
GbE network connection (order-
dependent)
32 Gb FC
(SFP+ Op)
X66250-2 (112-00342), 2m
X66250-5 (112-00344), 5m
X66250-15 (112-00346), 15m
FC network connection
Storage Cables X66030A (112-00435), .5m
X66031A (112-00436), 1m
X66032A (112-00437), 2m
X66033A (112-00438), 3m
mini-SAS HD to mini-SAS HD
cables (order-dependent)
Optical cables X66250-2-N-C (112-00342) 16 Gb FC or 25GbE cables for
mezzanine cards (order-
dependent)
RJ-45 (order
dependent)
X6585-R6 (112-00291), 3m
X6562-R6 (112-00196), 5m
Management network
Micro-USB
console cable
Not applicable Console connection used during
software setup if laptop or console
does not support network
discovery.
Power cables Not applicable Powering up the system
4. Review the NetApp ONTAP Configuration Guide and collect the required information listed in that guide.
ONTAP Configuration Guide
Step 2: Install the hardware
You need to install your system in a 4-post rack or NetApp system cabinet, as applicable.
3

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. Attach cable management devices (as shown).
4. Place the bezel on the front of the system.
Step 3: Cable controllers to your network
You can cable the controllers to your network by using the two-node switchless cluster method or by using the
cluster interconnect network.
If the port labels on the card are not visible, check the card installation orientation (the PCIe
connector socket is on the left side of the card slot in the A400 and FAS8300/8700), and then
look for the card, by part number, in the NetApp Hardware Universe for a graphic of the bezel
which will show the port labels. The card part number can be found using the sysconfig -a
command or on the system packing list.
If you are cabling an MetroCluster IP configuration, ports e0a/e0b are available for hosting data
LIFs (usually in Default IPSpace).
Option 1: Cable a two-node switchless cluster
The optional data ports, optional NIC cards, and management ports on the controller modules are connected to
switches. The cluster interconnect and HA ports are cabled on both controller modules.
You must have contacted your network administrator for information about connecting the system to the
switches.
Be sure to check the direction of the cable pull-tabs when inserting the cables in the ports. Cable pull-tabs are
up for all onboard ports and down for expansion (NIC) cards.
4

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.
Steps
1. Use the animation or illustration to complete the cabling between the controllers and to the switches:
Animation - Two-node switchless cluster cabling
2. Go to Step 4: Cable controllers to drive shelves for drive shelf cabling instructions.
Option 2: Cable a switched cluster
The optional data ports, optional NIC cards, mezzanine cards, and management ports on the controller
modules are connected to switches. The cluster interconnect and HA ports are cabled on to the cluster/HA
switch.
You must have contacted your network administrator for information about connecting the system to the
switches.
Be sure to check the direction of the cable pull-tabs when inserting the cables in the ports. Cable pull-tabs are
up for all onboard ports and down for expansion (NIC) cards.
5

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.
Steps
1. Use the animation or illustration to complete the cabling between the controllers and to the switches:
Animation - Switched cluster cabling
2. Go to Step 4: Cable controllers to drive shelves for drive shelf cabling instructions.
Step 4: Cable controllers to drive shelves
You can cable either NSS224 or SAS shelves to you system.
6

Option 1: Cable the controllers to a single drive shelf
You must cable each controller to the NSM modules on the NS224 drive shelf.
Be sure to check the illustration arrow for the proper cable connector pull-tab orientation. The cable pull-tab for
the NS224 are up.
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.
Steps
1. Use the following animation or illustration to cable your controllers to a single drive shelf.
Animation - Cable the controllers to one NS224 drive shelf
2. Go to Step 5: Complete system setup and configuration to complete system setup and configuration.
Option 2: Cable the controllers to two drive shelves
You must cable each controller to the NSM modules on both NS224 drive shelves.
Be sure to check the illustration arrow for the proper cable connector pull-tab orientation. The cable pull-tab for
the NS224 are up.
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.
Steps
1. Use the following animation or illustration to cable your controllers to two drive shelves.
Animation - Cable the controllers to one NS224 drive shelf
2. Go to Step 5: Complete system setup and configuration to complete system setup and configuration.
Option 3: Cable the controllers to SAS drive shelves
You must cable each controller to the IOM modules on both SAS drive shelves.
8

Be sure to check the illustration arrow for the proper cable connector pull-tab orientation. The cable pull-tab for
the DS224-C are down.
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.
Steps
1. Use the following illustration to cable your controllers to two drive shelves.
Animation - Cable the controllers to SAS drive shelves
9

2. Go to Step 5: Complete system setup and configuration to complete system setup and configuration.
Step 5: Complete system setup and configuration
You can 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.
Option 1: Completing system setup and configuration 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.
1. Use the following animation to set one or more drive shelf IDs:
10

If your system has NS224 drive shelves, the shelves are pre-set to shelf ID 00 and 01. If you want to
change the shelf IDs, you must create a tool to insert into the hole where button is located.
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.
3. Make sure that your laptop has network discovery enabled.
See your laptop’s online help for more information.
4. Use the following animation to connect your laptop to the Management switch.
Animation - 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.
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 NetApp
ONTAP Configuration Guide.
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
11

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 the ONTAP & ONTAP System Manager
Documentation Resources page for information about configuring additional features in ONTAP.
Option 2: Completing system setup and configuration 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.
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 console cable to the laptop or console using the console cable that came with your
system, and then connect the laptop to the management 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. Use the following animation to set one or more drive shelf IDs:
Animation - Set drive shelf IDs
If your system has NS224 drive shelves, the shelves are pre-set to shelf ID 00 and 01. If you want to
change the shelf IDs, you must create a tool to insert into the hole where button is located.
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.
FAS8300 and FAS8700 shown.
Animation - Power on the controllers
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 has
DHCP…
Then…
Configured Record the IP address assigned to the new controllers.
12

If the management network has
DHCP…
Then…
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 NetApp ONTAP Configuration guide.
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.
NetApp Support Registration
b. Register your system.
NetApp Product Registration
c. Download Active IQ Config Advisor.
NetApp Downloads: Config Advisor
7. Verify the health of your system by running Config Advisor.
8. 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 A400 hardware
For the ASA A400 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.
13

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.
Fan
The fan cools the controller.
NVDIMM battery
A NVDIMM battery is responsible for maintaining power to the NVDIMM module.
NVDIMM
The NVDIMM (non-volatile dual in-line memory module) manages the data
transfer from the volatile memory to the non-volatile storage, and
maintains data integrity in the event of a power loss or system shutdown.
PCIe or Mezzanine card
A PCIe (peripheral component interconnect express) card is an expansion card that plugs into the PCIe slot on
the motherboard.
A Mezzanine card is an expansion card that is designed to be inserted into a specialized slot on the
motherboard.
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 - ASA A400
The boot media stores a primary and secondary set of system (boot image) files that the
system uses when it boots. Depending on your network configuration, you can perform
14

either a nondisruptive or disruptive replacement.
You must have a USB flash drive, formatted to 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.
•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 node:
◦The impaired node is the node on which you are performing maintenance.
◦The healthy node is the HA partner of the impaired node.
Check onboard encryption - ASA A400
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:
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.
15

◦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.
◦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.
16

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

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