NetApp FAS500f Manuel utilisateur

Maintain

ONTAP Systems

NetApp

July 19, 2022

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

overview.html on July 19, 2022. Always check docs.netapp.com for the latest.

Table of Contents

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

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

Chassis. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê20

Controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê25

Replace a DIMM - FAS500f . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê44

Replace SSD Drive or HDD Drive - AFF C190 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê51

Replace a fan — FAS500f . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê55

Replace or install a mezzanine card - FAS500f . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê60

Replace the NVMEM battery - FAS500f. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê65

Replace a power supply - FAS500f . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê71

Replace the real-time clock battery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê73

Maintain

Boot media

Overview of boot media replacement - FAS500f

The boot media stores a primary and secondary set of system (boot image) files that the

system uses when it boots.

You must have a USB flash drive, formatted to MBR/FAT32, with the appropriate amount of storage to hold the

image_xxx.tgz file.

•You 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 - FAS500f

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 what version of ONTAP the system is running.

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

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

After completing the NVE or NSE tasks, you need to complete the shutdown of the

impaired controller. Shut down or take over the impaired controller using the appropriate

procedure for your configuration.

Option 1: Most configurations

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.

Option 2: Controller is in a MetroCluster

Do not use this procedure if your system is in a two-node MetroCluster configuration.

To shut down the impaired controller, you must determine the status of the controller and, if necessary, take

over the controller so that the healthy controller continues to serve data from the impaired controller storage.

•If you have a cluster with more than two nodes, it must be in quorum. If the cluster is not in quorum or a

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

impaired controller; see 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 controller: storage failover modify

–node local -auto-giveback false

3. Take the impaired controller to the LOADER prompt:

If the impaired controller is

displaying…

Then…

The LOADER prompt Go to Remove controller module.

Waiting for giveback… Press Ctrl-C, and then respond ywhen prompted.

System prompt or password

prompt (enter system password)

Take over or halt the impaired controller from the healthy controller:

storage failover takeover -ofnode

impaired_node_name

When the impaired controller shows Waiting for giveback…, press

Ctrl-C, and then respond y.

Replace the boot media - FAS500f

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

You must remove the controller module from the chassis when you replace a component inside the controller

module.

Make sure that you label the cables so that you know where they came from.

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

2. Unplug the controller module power supplies from the source.

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

4. Insert your forefinger into the latching mechanism on either side of the controller module, press the lever

with your thumb, and gently pull the controller a few inches out of the chassis.

If you have difficulty removing the controller module, place your index fingers through the

finger holes from the inside (by crossing your arms).

Lever

Latching mechanism

5. Using both hands, grasp the controller module sides and gently pull it out of the chassis and set it on a flat,

stable surface.

6. Turn the thumbscrew on the front of the controller module anti-clockwise and open the controller module

cover.

Thumbscrew

Controller module cover.

7. Lift out the air duct cover.

Autres manuels pour FAS500f

Ce manuel convient aux modèles suivants

Table des matières

Autres manuels NetApp Stockage

NetApp

NetApp AFF A400 Manuel utilisateur

NetApp

NetApp FAS2020 Manuel

NetApp

NetApp StorageGRID Webscale SG6000 Series Manuel d'utilisation

NetApp

NetApp AFF A400 Manuel utilisateur

NetApp

NetApp StorageGRID Webscale 10.4 Manuel du produit

NetApp

NetApp AFF A800 Manuel utilisateur

NetApp

NetApp AFF A900 Manuel

NetApp

NetApp H600S Series Manuel

NetApp

NetApp StorageGRID Webscale SG5700 Series Manuel d'utilisation

NetApp

NetApp FAS8200 Series Manuel

NetApp

NetApp AFF A400 Manuel

NetApp

NetApp E-Series 3040 40U Manuel utilisateur

NetApp

NetApp DE6600 Manuel utilisateur

NetApp

NetApp E Series Manuel utilisateur

NetApp

NetApp FAS2500 Manuel d'utilisation et d'entretien

NetApp

NetApp E Series Manuel utilisateur

NetApp

NetApp StorageGRID Webscale SG5700 Series Feuille d'instructions

NetApp

NetApp SOLIDFIRE Manuel utilisateur

NetApp

NetApp FAS9500 Manuel utilisateur

NetApp

NetApp E5700 Manuel utilisateur

NetApp

NetApp FAS25 Series Manuel utilisateur

NetApp

NetApp EF550 Manuel utilisateur

NetApp

NetApp H410S Manuel

NetApp

NetApp FAS2800 Manuel

Manuels Stockage populaires d'autres marques

QNAP

QNAP TS 32PXU Series Manuel utilisateur

LaCie

LaCie RUGGED RAID Manuel utilisateur

Freecom

Freecom CLS DOCK Manuel utilisateur

PNY

PNY Attache P-FD64MBATT3 Manuel utilisateur

HP StorageWorks MSL2024 Manuel utilisateur

OLT

OLT 6x6 Maximizer Manuel utilisateur

Transcend

Transcend JetFlash 160 Manuel utilisateur

LaCie

LaCie RUGGED MINI Manuel utilisateur

Thunderbolt

Thunderbolt 600 Manuel utilisateur

Panasonic

Panasonic LB-DH8 series Manuel

Intel

Intel RAID High Availability Manuel utilisateur

LaCie

LaCie 12big Thunderbolt 3 Manuel utilisateur

Spectra Logic

Spectra Logic T-Series Spectra T50e Manuel utilisateur

Panasonic

Panasonic LKM-F931-1 Manuel utilisateur

Tabernus

Tabernus Enterprise Erase E2400 Manuel utilisateur

Rocstor

Rocstor COMMANDER 3F series Manuel utilisateur

HP P9000 Manuel utilisateur

Western Digital

Western Digital Ultrastar Data60 Manuel utilisateur