NetApp AFF A700s Manual de usuario

Boot media

ONTAP Systems

NetApp

June 13, 2022

This PDF was generated from https://docs.netapp.com/us-en/ontap-systems/a700s/bootmedia-replace-

overview.html on June 13, 2022. Always check docs.netapp.com for the latest.

Table of Contents

Boot media . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê1

Overview of boot media replacement - AFF A700s . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê1

Check onboard encryption keys - AFF A700s . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê1

Shut down the controller - AFF A700s . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê8

Replace the boot media - AFF A700s . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê8

Transfer the boot image to the boot media - AFF A700s . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê12

Boot the recovery image - AFF A700s . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê17

Restore OKM, NSE, and NVE as needed - AFF A700s . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê19

Return the failed part to NetApp - AFF A700s . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê25

Boot media

Overview of boot media replacement - AFF A700s

The primary boot media stores the ONTAP boot image that the system uses when it

boots. You can restore the primary boot media image by using the ONTAP image on the

secondary boot media, or if necessary, by using a USB flash drive.

If your secondary boot media has failed or is missing the image.tgz file, you must restore the primary boot

media using a USB flash drive. The drive must be formatted to FAT32 and must have the appropriate amount

of storage to hold the image_xxx.tgz file.

•The replacement process restores the var file system from the secondary boot media or USB flash drive to

the primary boot media.

•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 controller is the controller on which you are performing maintenance.

◦The healthy controller is the HA partner of the impaired controller.

Check onboard encryption keys - AFF A700s

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 the version of ONTAP that 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

controller shows false for eligibility and health, you must correct the issue before shutting down the impaired

controller; see the NetApp Encryption overview with the CLI.

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.

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

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

Option 1: Check NVE or NSE on systems running ONTAP 9.5 and earlier

Before shutting down the impaired controller, 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 controller.

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

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

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

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

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

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

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

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

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

Option 2: 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.

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

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

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

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.

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

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

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.

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

Shut down the controller - AFF A700s

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.

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

Replace the boot media - AFF A700s

You must remove the controller module from the chassis, open it, and then replace the

failed boot media.

Step 1: Remove the controller module

You must remove the controller module from the chassis when you replace the controller

module or replace a component inside 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. Unplug the controller module power supply from the source, and then unplug the cable from the power

supply.

Otros manuales para AFF A700s

Tabla de contenidos

Otros manuales de Almacenamiento de NetApp

NetApp

NetApp EF550 Manual de usuario

NetApp

NetApp AltaVault AVA400 Manual de instrucciones

NetApp

NetApp FAS9000 Manual

NetApp

NetApp StorageGRID Webscale 10.4 Manual del producto

NetApp

NetApp FAS2020 Manual

NetApp

NetApp FAS2240-2 Manual de usuario

NetApp

NetApp FAS9500 Manual de usuario

NetApp

NetApp AFF A800 Manual de instrucciones

NetApp

NetApp AFF A900 Manual

NetApp

NetApp E Series Manual de usuario

NetApp

NetApp DiskShelf14mk4 FC Manual de usuario

NetApp

NetApp FAS8300 Manual de usuario

NetApp

NetApp DS4486 Manual

NetApp

NetApp HCI Manual de usuario

NetApp

NetApp SolidFire C-Series Manual

NetApp

NetApp SOLIDFIRE Manual de usuario

NetApp

NetApp SG100 Hoja de instrucciones

NetApp

NetApp DE6900 Manual de usuario

NetApp

NetApp FAS500f Manual de usuario

NetApp

NetApp StorageGRID SG5600 Series Manual de funcionamiento

NetApp

NetApp StorageGRID Webscale SG5700 Series Manual de funcionamiento

NetApp

NetApp StorageGRID SD100 Manual de usuario

NetApp

NetApp NearStore R100 Manual de usuario

NetApp

NetApp E-Series 3040 40U Manual de usuario

Manuales populares de Almacenamiento de otras marcas

QNAP

QNAP TS 32PXU Series Manual de usuario

LaCie

LaCie RUGGED RAID Manual de usuario

Freecom

Freecom CLS DOCK Manual de usuario

PNY

PNY Attache P-FD64MBATT3 Manual de usuario

HP StorageWorks MSL2024 Manual de usuario

OLT

OLT 6x6 Maximizer Manual de usuario

Transcend

Transcend JetFlash 160 Manual de usuario

LaCie

LaCie RUGGED MINI Manual de usuario

Thunderbolt

Thunderbolt 600 Manual de usuario

Panasonic

Panasonic LB-DH8 series Manual

Intel

Intel RAID High Availability Manual de usuario

LaCie

LaCie 12big Thunderbolt 3 Manual de usuario

Spectra Logic

Spectra Logic T-Series Spectra T50e Manual de usuario

Panasonic

Panasonic LKM-F931-1 Manual de usuario

Tabernus

Tabernus Enterprise Erase E2400 Manual de usuario

Rocstor

Rocstor COMMANDER 3F series Manual de usuario

HP P9000 Manual de usuario

Western Digital

Western Digital Ultrastar Data60 Manual de usuario