NetApp AFF A300 User manual

AFF A300 systems
ONTAP Systems
NetApp
January 28, 2022
This PDF was generated from https://docs.netapp.com/us-en/ontap-systems/a300/install-worksheet-
linkout.html on January 28, 2022. Always check docs.netapp.com for the latest.

Table of Contents
AFF A300 System Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê1
Install and setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê1
Maintain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê1

AFF A300 System Documentation
Install and setup
Cluster configuration worksheet - AFF A300
You can use the worksheet to gather and record your site-specific IP addresses and other information required
when configuring an ONTAP cluster.
Cluster Configuration Worksheet
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.
For MetroCluster configurations, see either:
•Install MetroCluster IP configuration
•Install MetroCluster Fabric-Attached configuration
Installation and setup PDF poster - AFF A300
You can use the PDF poster to install and set up your new system. The PDF poster provides step-by-step
instructions with live links to additional content.
AFF A300 Installation and Setup Instructions
Installation and setup video - AFF A300
The following video shows end-to-end software configuration for systems running ONTAP 9.2.
AFF A300 Setup Video
Maintain
Boot media
Replace the boot media - AFF A300
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
either a nondisruptive or disruptive replacement.
1

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 keys as needed - AFF A300
Prior to shutting down the impaired node and checking the status of the onboard
encryption keys, you must check the status of the impaired node, disable automatic
giveback, and check what version of ONTAP the system is running.
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
node shows false for eligibility and health, you must correct the issue before shutting down the impaired node;
see the NetApp Encryption overview with the CLI.
Steps
1. Check the status of the impaired node:
◦If the impaired node is at the login prompt, log in as admin.
◦If the impaired node is at the LOADER prompt and is part of HA configuration, log in as admin on the
healthy node.
◦If the impaired node 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 node if up, or on the partner node if the
impaired node is down, using the version -v command:
◦If <lno-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.5, go to
[Option 1: Checking NVE or NSE on systems running ONTAP 9.5 and earlier].
2

◦If <lno-DARE> is not displayed in the command output, and the system is running ONTAP 9.6 or later,
go to [Option 2: Checking NVE or NSE on systems running ONTAP 9.6 and later].
4. If the impaired node is part of an HA configuration, disable automatic giveback from the healthy node:
storage failover modify -node local -auto-giveback false or storage failover
modify -node local -auto-giveback-after-panic false
Option 1: Check NVE or NSE on systems running ONTAP 9.5 and earlier
Before shutting down the impaired node, you need to check whether the system has either NetApp Volume
Encryption (NVE) or NetApp Storage Encryption (NSE) enabled. If so, you need to verify the configuration.
Steps
1. Connect the console cable to the impaired node.
2. Check whether NVE is configured 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.
3. Check whether NSE is configured: 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.
◦If NVE and NSE are not configured, it’s safe to shut down the impaired node.
Verify NVE configuration
Steps
1. Display the key IDs of the authentication keys that are stored on the key management servers: security
key-manager query
◦If the Restored column displays yes and all key managers display available, it’s safe to shut down
the impaired node.
◦If the Restored column displays anything other than yes, or if any key manager displays
unavailable, you need to complete some additional steps.
◦If you see the message This command is not supported when onboard key management is enabled,
you need to complete some other additional steps.
2. If the Restored column displayed anything other than yes, or if any key manager displayed
unavailable:
a. Retrieve and restore all authentication keys and associated key IDs: security key-manager
restore -address *
If the command fails, contact NetApp Support.
mysupport.netapp.com
b. Verify that the Restored column displays yes for all authentication keys and that all key managers
display available: security key-manager query
c. Shut down the impaired node.
3. If you saw the message This command is not supported when onboard key management is enabled,
display the keys stored in the onboard key manager: security key-manager key show -detail
3

a. If the Restored column displays yes manually back up the onboard key management information:
▪Go to advanced privilege mode and enter ywhen prompted to continue: set -priv advanced
▪Enter the command to display the OKM backup information: security key-manager backup
show
▪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.
▪Return to admin mode: set -priv admin
▪Shut down the impaired node.
b. If the Restored column displays anything other than yes:
▪Run the key-manager setup wizard: security key-manager setup -node
target/impaired node name
Enter the customer’s onboard key management passphrase at the prompt. If the
passphrase cannot be provided, contact mysupport.netapp.com
▪Verify that the Restored column displays yes for all authentication key: security key-
manager key show -detail
▪Go to advanced privilege mode and enter ywhen prompted to continue: set -priv advanced
▪Enter the command to display the OKM backup information: security key-manager backup
show
▪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.
▪Return to admin mode: set -priv admin
▪You can safely shutdown the node.
Verify NSE configuration
Steps
1. Display the key IDs of the authentication keys that are stored on the key management servers: security
key-manager query
◦If the Restored column displays yes and all key managers display available, it’s safe to shut down
the impaired node.
◦If the Restored column displays anything other than yes, or if any key manager displays
unavailable, you need to complete some additional steps.
◦If you see the message This command is not supported when onboard key management is enabled,
you need to complete some other additional steps
2. If the Restored column displayed anything other than yes, or if any key manager displayed
unavailable:
a. Retrieve and restore all authentication keys and associated key IDs: security key-manager
restore -address *
If the command fails, contact NetApp Support.
4

mysupport.netapp.com
b. Verify that the Restored column displays yes for all authentication keys and that all key managers
display available: security key-manager query
c. Shut down the impaired node.
3. If you saw the message This command is not supported when onboard key management is enabled,
display the keys stored in the onboard key manager: security key-manager key show -detail
a. If the Restored column displays yes, manually back up the onboard key management information:
▪Go to advanced privilege mode and enter ywhen prompted to continue: set -priv advanced
▪Enter the command to display the OKM backup information: security key-manager backup
show
▪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.
▪Return to admin mode: set -priv admin
▪Shut down the impaired node.
b. If the Restored column displays anything other than yes:
▪Run the key-manager setup wizard: security key-manager setup -node
target/impaired node name
Enter the customer’s OKM passphrase at the prompt. If the passphrase cannot be
provided, contact mysupport.netapp.com
▪Verify that the Restored column shows yes for all authentication keys: security key-
manager key show -detail
▪Go to advanced privilege mode and enter ywhen prompted to continue: set -priv advanced
▪Enter the command to back up the OKM information: security key-manager backup show
Make sure that OKM information is saved in your log file. This information will be
needed in disaster scenarios where OKM might need to be manually recovered.
▪Copy the contents of the backup information to a separate file or your log. You’ll need it in disaster
scenarios where you might need to manually recover OKM.
▪Return to admin mode: set -priv admin
▪You can safely shut down the node.
Option 2: Check NVE or NSE on systems running ONTAP 9.6 and later
Before shutting down the impaired node, 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 configured 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.
5

2. Verify whether NSE is configured: 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.
◦If no disks are shown, NSE is not configured.
◦If NVE and NSE are not configured, it’s safe to shut down the impaired node.
Verify NVE configuration
1. Display the key IDs of the authentication keys that are stored on the key management servers: security
key-manager query
◦If the Key Manager type displays external and the Restored column displays yes, it’s safe to shut
down the impaired node.
◦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.
d. Return to admin mode: set -priv admin
e. Shut down the impaired node.
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 node.
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
6

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 node.
Verify NSE configuration
1. Display the key IDs of the authentication keys that are stored on the key management servers: security
key-manager query
◦If the Key Manager type displays external and the Restored column displays yes, it’s safe to shut
down the impaired node.
◦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 node.
3. If the Key Manager type displays external and the Restored column displays anything other than
yes:
a. Enter the onboard security key-manager sync command: security key-manager external
sync
If the command fails, contact NetApp Support.
mysupport.netapp.com
7

b. Verify that the Restored column equals yes for all authentication keys: security key-manager
key query
c. You can safely shut down the node.
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 node.
Shut down the impaired controller - AFF A300
You can shut down or take over the impaired controller using different procedures,
depending on the storage system hardware configuration.
Option 1: Most configurations
After completing the NVE or NSE tasks, you need to complete the shutdown of the impaired node.
Steps
1. If the impaired node isn’t at the LOADER prompt:
If the impaired node displays… Then…
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 node from the healthy node: storage
failover takeover -ofnode impaired_node_name
+
When the impaired node shows Waiting for giveback…, press Ctrl-C,
and then respond y.
+
8

2. 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: Controller is in a MetroCluster configuration
After completing the NVE or NSE tasks, you need to complete the shutdown of the impaired node.
Do not use this procedure if your system is in a two-node MetroCluster configuration.
To shut down the impaired node, you must determine the status of the node and, if necessary, take over the
node so that the healthy node continues to serve data from the impaired node 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 node shows false for eligibility and health, you must correct the issue before shutting down the
impaired node; see the Administration overview with the CLI.
•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 node: storage failover modify –node
local -auto-giveback false
3. Take the impaired node to the LOADER prompt:
If the impaired node 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 node from the healthy node: storage
failover takeover -ofnode impaired_node_name
+
When the impaired node shows Waiting for giveback…, press Ctrl-C,
and then respond y.
+
9

Option 3: Controller is in a two-node MetroCluster
After completing the NVE or NSE tasks, you need to complete the shutdown of the impaired node.
To shut down the impaired node, you must determine the status of the node and, if necessary, switch over the
node so that the healthy node continues to serve data from the impaired node storage.
About this task
•If you are using NetApp Storage Encryption, you must have reset the MSID using the instructions in the
"Return a FIPS drive or SED to unprotected mode" section of NetApp Encryption overview with the CLI.
•You must leave the power supplies turned on at the end of this procedure to provide power to the healthy
node.
Steps
1. Check the MetroCluster status to determine whether the impaired node has automatically switched over to
the healthy node: metrocluster show
2. Depending on whether an automatic switchover has occurred, proceed according to the following table:
If the impaired node… Then…
Has automatically switched over Proceed to the next step.
Has not automatically switched
over
Perform a planned switchover operation from the healthy node:
metrocluster switchover
Has not automatically switched
over, you attempted switchover
with the metrocluster
switchover command, and the
switchover was vetoed
Review the veto messages and, if possible, resolve the issue and try
again. If you are unable to resolve the issue, contact technical
support.
3. Resynchronize the data aggregates by running the metrocluster heal -phase aggregates
command from the surviving cluster.
controller_A_1::> metrocluster heal -phase aggregates
[Job 130] Job succeeded: Heal Aggregates is successful.
If the healing is vetoed, you have the option of reissuing the metrocluster heal command with the
-override-vetoes parameter. If you use this optional parameter, the system overrides any soft vetoes
that prevent the healing operation.
4. Verify that the operation has been completed by using the metrocluster operation show command.
10

controller_A_1::> metrocluster operation show
Ê Operation: heal-aggregates
Ê State: successful
Start Time: 7/25/2016 18:45:55
Ê End Time: 7/25/2016 18:45:56
Ê Errors: -
5. Check the state of the aggregates by using the storage aggregate show command.
controller_A_1::> storage aggregate show
Aggregate Size Available Used% State #Vols Nodes RAID
Status
--------- -------- --------- ----- ------- ------ ----------------
------------
...
aggr_b2 227.1GB 227.1GB 0% online 0 mcc1-a2
raid_dp, mirrored, normal...
6. Heal the root aggregates by using the metrocluster heal -phase root-aggregates command.
mcc1A::> metrocluster heal -phase root-aggregates
[Job 137] Job succeeded: Heal Root Aggregates is successful
If the healing is vetoed, you have the option of reissuing the metrocluster heal command with the
-override-vetoes parameter. If you use this optional parameter, the system overrides any soft vetoes that
prevent the healing operation.
7. Verify that the heal operation is complete by using the metrocluster operation show command on
the destination cluster:
mcc1A::> metrocluster operation show
Ê Operation: heal-root-aggregates
Ê State: successful
ÊStart Time: 7/29/2016 20:54:41
Ê End Time: 7/29/2016 20:54:42
Ê Errors: -
8. On the impaired controller module, disconnect the power supplies.
Remove the controller module, replace the boot media and transfer the boot image to the boot media -
AFF A300
To replace the boot media, you must remove the impaired controller module, install the
11

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, you must first remove the controller module from the system and
then remove the cover on the controller module.
1. If you are not already grounded, properly ground yourself.
2. Loosen the hook and loop strap binding the cables to the cable management device, and then unplug the
system cables and SFPs (if needed) from the controller module, keeping track of where the cables were
connected.
Leave the cables in the cable management device so that when you reinstall the cable management
device, the cables are organized.
3. Remove and set aside the cable management devices from the left and right sides of the controller module.
4. Loosen the thumbscrew on the cam handle on the controller module.
Thumbscrew
Cam handle
5. Pull the cam handle downward and begin to slide the controller module out of the chassis.
Make sure that you support the bottom of the controller module as you slide it out of the chassis.
12

Step 2: Replace the boot media - AFF A300
You must locate the boot media in the controller and follow the directions to replace it.
1. If you are not already grounded, properly ground yourself.
2. Locate the boot media using the following illustration or the FRU map on the controller module:
3. Press the blue button on the boot media housing to release the boot media from its housing, and then
gently pull it straight out of the boot media socket.
Do not twist or pull the boot media straight up, because this could damage the socket or the
boot media.
4. Align the edges of the replacement boot media with the boot media socket, and then gently push it into the
socket.
5. Check the boot media to make sure that it is seated squarely and completely in the socket.
If necessary, remove the boot media and reseat it into the socket.
6. Push the boot media down to engage the locking button on the boot media housing.
7. Close the controller module cover.
13

Step 3: Transfer the boot image to the boot media
You can install the system image to the replacement boot media using a USB flash drive with the image
installed on it. However, you must restore the var file system during this procedure.
•You must have a USB flash drive, formatted to 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
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. Align the end of the controller module with the opening in the chassis, and then gently push the
controller module halfway into the system.
2. Reinstall the cable management device and recable the system, as needed.
When recabling, remember to reinstall the media converters (SFPs) if they were removed.
3. 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.
4. Push the controller module all the way into the system, making sure that the cam handle clears the
USB flash drive, firmly push the cam handle to finish seating the controller module, push the cam
handle to the closed position, and then tighten the thumbscrew.
The node begins to boot as soon as it is completely installed into the chassis.
5. 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 node to boot to LOADER.
6. 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.
7. Although the environment variables and bootargs are retained, you should check that all required boot
environment variables and bootargs are properly set for your system type and configuration using the
printenv bootarg name command and correct any errors using the setenv variable-name
<value> command.
a. Check the boot environment variables:
▪bootarg.init.boot_clustered
▪partner-sysid
14

▪bootarg.init.flash_optimized
▪bootarg.init.switchless_cluster.enable
b. If External Key Manager is enabled, check the bootarg values, listed in the kenv ASUP output:
▪bootarg.storageencryption.support <value>
▪bootarg.keymanager.support <value>
▪kmip.init.interface <value>
▪kmip.init.ipaddr <value>
▪kmip.init.netmask <value>
▪kmip.init.gateway <value>
c. If Onboard Key Manager is enabled, check the bootarg values, listed in the kenv ASUP output:
▪bootarg.storageencryption.support <value>
▪bootarg.keymanager.support <value>
▪bootarg.onboard_keymanager <value>
d. Save the environment variables you changed with the savenv command
e. Confirm your changes using the printenv variable-name command.
8. Set your network connection type at the LOADER prompt:
▪If you are configuring DHCP: ifconfig e0a -auto
The target port you configure is the target port you use to communicate with the
impaired node from the healthy node during var file system restore with a network
connection. You can also use the e0M port in this command.
▪If you are configuring manual connections: ifconfig e0a -addr=filer_addr
-mask=netmask -gw=gateway-dns=dns_addr-domain=dns_domain
▪filer_addr is the IP address of the storage system.
▪netmask is the network mask of the management network that is connected to the HA partner.
▪gateway is the gateway for the network.
▪dns_addr is the IP address of a name server on your network.
▪dns_domain is the Domain Name System (DNS) domain name.
If you use this optional parameter, you do not need a fully qualified domain name in the netboot
server URL. You need only the server’s host name.
Other parameters might be necessary for your interface. You can enter help
ifconfig at the firmware prompt for details.
9. If the controller is in a stretch or fabric-attached MetroCluster, you must restore the FC adapter
configuration:
a. Boot to Maintenance mode: boot_ontap maint
15

b. Set the MetroCluster ports as initiators: ucadmin modify -m fc -t initiator
adapter_name
c. Halt to return to Maintenance mode: halt
The changes will be implemented when the system is booted.
Boot the recovery image - AFF A300
The procedure for booting the impaired node from the recovery image depends on
whether the system is in a two-node MetroCluster configuration.
Option 1: Most systems
You must boot the ONTAP image from the USB drive, restore the file system, and verify the environmental
variables.
This procedure applies to systems that are not in a two-node MetroCluster configuration.
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.
3. Restore the var file system:
If your system has… Then…
A network connection a. Press ywhen prompted to restore the backup configuration.
b. Set the healthy node to advanced privilege level: set
-privilege advanced
c. Run the restore backup command: system node restore-
backup -node local -target-address
impaired_node_IP_address
d. Return the node to admin level: set -privilege admin
e. Press ywhen prompted to use the restored configuration.
f. Press ywhen prompted to reboot the node.
No network connection a. Press nwhen prompted to restore the backup configuration.
b. Reboot the system when prompted by the system.
c. Select the Update flash from backup config (sync flash) option
from the displayed menu.
If you are prompted to continue with the update, press y.
4. Ensure that the environmental variables are set as expected:
16

a. Take the node to the LOADER prompt.
b. Check the environment variable settings with the printenv command.
c. If an environment variable is not set as expected, modify it with the setenv environment-
variable-name changed-value command.
d. Save your changes using the savenev command.
5. The next depends on your system configuration:
◦If your system has onboard keymanager, NSE or NVE configured, go to Restore OKM, NSE, and NVE
as needed
◦If your system does not have onboard keymanager, NSE or NVE configured, complete the steps in this
section.
6. From the LOADER prompt, enter the boot_ontap command.
If you see… Then…
The login prompt Go to the next Step.
Waiting for giveback… a. Log into the partner node.
b. Confirm the target node is ready for giveback with the storage
failover show command.
7. Connect the console cable to the partner node.
8. Give back the node using the storage failover giveback -fromnode local command.
9. At the cluster prompt, check the logical interfaces with the net int -is-home false command.
If any interfaces are listed as "false", revert those interfaces back to their home port using the net int
revert command.
10. Move the console cable to the repaired node and run the version -v command to check the ONTAP
versions.
11. Restore automatic giveback if you disabled it by using the storage failover modify -node local
-auto-giveback true command.
Option 2: Controller is in a two-node MetroCluster
You must boot the ONTAP image from the USB drive and verify the environmental variables.
This procedure applies to systems in a two-node MetroCluster configuration.
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.
3. After the image is installed, start the restoration process:
17

a. Press nwhen prompted to restore the backup configuration.
b. Press ywhen prompted to reboot to start using the newly installed software.
You should be prepared to interrupt the boot process when prompted.
4. As the system boots, press Ctrl-C after you see the Press Ctrl-C for Boot Menu message., and
when the Boot Menu is displayed select option 6.
5. Verify that the environmental variables are set as expected.
a. Take the node to the LOADER prompt.
b. Check the environment variable settings with the printenv command.
c. If an environment variable is not set as expected, modify it with the setenv environment-
variable-name changed-value command.
d. Save your changes using the savenev command.
e. Reboot the node.
Switch back aggregates in a two-node MetroCluster configuration - AFF A300
After you have completed the FRU replacement in a two-node MetroCluster
configuration, you can perform the MetroCluster switchback operation. This returns the
configuration to its normal operating state, with the sync-source storage virtual machines
(SVMs) on the formerly impaired site now active and serving data from the local disk
pools.
This task only applies to two-node MetroCluster configurations.
Steps
1. Verify that all nodes are in the enabled state: metrocluster node show
cluster_B::> metrocluster node show
DR Configuration DR
Group Cluster Node State Mirroring Mode
----- ------- -------------- -------------- ---------
--------------------
1 cluster_A
Ê controller_A_1 configured enabled heal roots
completed
Ê cluster_B
Ê controller_B_1 configured enabled waiting for
switchback recovery
2 entries were displayed.
2. Verify that resynchronization is complete on all SVMs: metrocluster vserver show
3. Verify that any automatic LIF migrations being performed by the healing operations were completed
18