NetApp AFF A400 Manual de usuario

Maintain

ONTAP Systems

NetApp

November 23, 2021

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

overview.html on November 23, 2021. Always check docs.netapp.com for the latest.

Table of Contents

Maintain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê1

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

Chassis. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê21

Controller module. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê30

Replace a DIMM - AFF A400 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê52

Hot-swap a fan module - AFF A400 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê62

Replace the NVDIMM battery - AFF A400 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê64

Replace an NVDIMM - AFF A400 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê73

Replace a PCIe or mezzanine card - AFF A400 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê84

Replacing a power supply - AFF A400 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê95

Replace the real-time clock battery - AFF A400. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê96

Maintain

Boot media

Replace the boot media - AFF 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

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.

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 A400

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 NetApp Support.

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.6 or later,

go to the next section.

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

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.

2. Verify whether NSE is configured: storage encryption disk show

◦If the command output list 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 backup

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

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, manually backup 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 shutdown 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 backup

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

b. Verify that the Restored column equals yes for all authentication keys: security key-manager

key query

c. You can safely shutdown 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, manually backup 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 shutdown the node.

Shut down the impaired controller - AFF A400

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:

•For an HA pair, take over 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.

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

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:

•For an HA pair, take over 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.

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

"Returning SEDs to unprotected mode" section of Administration 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

If the impaired node… Then…

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.

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 A400

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 remove the controller

module from the chassis.

You can use the following animation, illustration, or the written steps to remove the controller module from the

chassis.

Removing the controller module

Steps

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

2. Release the power cable retainers, and then unplug the cables from the power supplies.

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

4. Remove the cable management device from the controller module and set it aside.

5. Press down on both of the locking latches, and then rotate both latches downward at the same time.

The controller module moves slightly out of the chassis.

Otros manuales para AFF A400

Tabla de contenidos

Otros manuales de Almacenamiento de NetApp

NetApp

NetApp AFF A400 Manual de usuario

NetApp

NetApp EF550 Manual de usuario

NetApp

NetApp AFF A320 Manual de usuario

NetApp

NetApp FAS25 Series Manual de usuario

NetApp

NetApp H600S Series Manual

NetApp

NetApp H410S Manual del propietario

NetApp

NetApp DE6900 Manual de usuario

NetApp

NetApp DS2246 Manual

NetApp

NetApp E Series Manual de usuario

NetApp

NetApp FAS8300 Manual

NetApp

NetApp FAS2700 Series Manual

NetApp

NetApp AFF A700s Manual de usuario

NetApp

NetApp AltaVault Cloud Integrated Storage 4.1 Instrucciones de instalación y mantenimiento

NetApp

NetApp DE5600 Manual de usuario

NetApp

NetApp AFF A300 Manual de usuario

NetApp

NetApp AFF A400 Manual

NetApp

NetApp FAS9500 Manual

NetApp

NetApp DiskShelf14mk4 FC Manual de usuario

NetApp

NetApp AFF A250 Manual de usuario

NetApp

NetApp SG1000 Manual de funcionamiento

NetApp

NetApp EF550 Manual de usuario

NetApp

NetApp FAS500f Manual de usuario

NetApp

NetApp FAS26 Series Manual

NetApp

NetApp E Series Instrucciones de uso

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