NetApp FAS9500 Feuille d'instructions

Boot media

Install and maintain

NetApp

July 14, 2023

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

systems/fas9500/bootmedia_replace_overview.html on July 14, 2023. Always check docs.netapp.com for

the latest.

Table of Contents

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

Replace the boot media - FAS9500 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê1

Pre-shutdown checks for onboard encryption keys - FAS9500 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê1

Shut down the impaired controller - FAS9500 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê5

Remove the controller, replace the boot media, and transfer the boot image - FAS9500 . . . . . . . . . . . . . . . . Ê6

Boot the recovery image - FAS9500 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê11

Post boot media replacement steps for OKM, NSE, and NVE - FAS9500 . . . . . . . . . . . . . . . . . . . . . . . . . . Ê13

Return the failed part to NetApp - FAS9500. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê17

Boot media

Replace the boot media - FAS9500

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 does not require connection to a network to restore the var

file system. The HA pair in a single chassis has an internal e0S connection, which is used to transfer

var config between them.

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

Pre-shutdown checks for onboard encryption keys -

FAS9500

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 Synchronize a node with the cluster.

Steps

1. Check the status of the impaired controller:

◦If the impaired controller is at the login prompt, log in as admin.

◦If the impaired controller is at the LOADER prompt and is part of HA configuration, log in as admin on

the healthy controller.

◦If the impaired controller is in a standalone configuration and at LOADER prompt, contact

mysupport.netapp.com.

2. If AutoSupport is enabled, suppress automatic case creation by invoking an AutoSupport message:

system node autosupport invoke -node * -type all -message

MAINT=number_of_hours_downh

The following AutoSupport message suppresses automatic case creation for two hours: cluster1:*>

system node autosupport invoke -node * -type all -message MAINT=2h

3. Check the version of ONTAP the system is running on the impaired controller if up, or on the partner

controller if the impaired controller is down, using the version -v command:

◦If <lno-DARE> or <1Ono-DARE> is displayed in the command output, the system does not support

NVE, proceed to shut down the controller.

ONTAP 9.6 and later

Before shutting down the impaired controller, you need to verify whether the system has either NetApp Volume

Encryption (NVE) or NetApp Storage Encryption (NSE) enabled. If so, you need to verify the configuration.

1. Verify whether NVE is in use for any volumes in the cluster: volume show -is-encrypted true

If any volumes are listed in the output, NVE is configured and you need to verify the NVE configuration. If

no volumes are listed, check whether NSE is configured and in use.

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

◦If the command output lists the drive details with Mode & Key ID information, NSE is configured and

you need to verify the NSE configuration and in use.

◦If no disks are shown, NSE is not configured.

◦If NVE and NSE are not configured, no drives are protected with NSE keys, it’s safe to shut down the

impaired controller.

Verify NVE configuration

1. Display the key IDs of the authentication keys that are stored on the key management servers: security

key-manager key query

After the ONTAP 9.6 release, you may have additional key manager types. The types are

KMIP, AKV, and GCP. The process for confirming these types is the same as confirming

external or onboard key manager types.

◦If the Key Manager type displays external and the Restored column displays yes, it’s safe to shut

down the impaired controller.

◦If the Key Manager type displays onboard and the Restored column displays yes, you need to

complete some additional steps.

◦If the Key Manager type displays external and the Restored column displays anything other than

yes, you need to complete some additional steps.

◦If the Key Manager type displays onboard and the Restored column displays anything other than

yes, you need to complete some additional steps.

2. If the Key Manager type displays onboard and the Restored column displays yes, manually back up

the OKM information:

a. Go to advanced privilege mode and enter ywhen prompted to continue: set -priv advanced

b. Enter the command to display the key management information: security key-manager onboard

show-backup

c. Copy the contents of the backup information to a separate file or your log file. You’ll need it in disaster

scenarios where you might need to manually recover OKM.

d. Return to admin mode: set -priv admin

e. Shut down the impaired controller.

3. If the Key Manager type displays external and the Restored column displays anything other than

yes:

a. Restore the external key management authentication keys to all nodes in the cluster: security key-

manager external restore

If the command fails, contact NetApp Support.

mysupport.netapp.com

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

key query

c. Shut down the impaired controller.

4. If the Key Manager type displays onboard and the Restored column displays anything other than yes:

a. Enter the onboard security key-manager sync command: security key-manager onboard sync

Enter the customer’s onboard key management passphrase at the prompt. If the

passphrase cannot be provided, contact NetApp Support. mysupport.netapp.com

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

query

c. Verify that the Key Manager type shows onboard, and then manually back up the OKM information.

d. Go to advanced privilege mode and enter ywhen prompted to continue: set -priv advanced

e. Enter the command to display the key management backup information: security key-manager

onboard show-backup

f. Copy the contents of the backup information to a separate file or your log file. You’ll need it in disaster

scenarios where you might need to manually recover OKM.

g. Return to admin mode: set -priv admin

h. You can safely shut down the controller.

Verify NSE configuration

1. Display the key IDs of the authentication keys that are stored on the key management servers: security

key-manager key query -key-type NSE-AK

After the ONTAP 9.6 release, you may have additional key manager types. The types are

KMIP, AKV, and GCP. The process for confirming these types is the same as confirming

external or onboard key manager types.

◦If the Key Manager type displays external and the Restored column displays yes, it’s safe to shut

down the impaired controller.

◦If the Key Manager type displays onboard and the Restored column displays yes, you need to

complete some additional steps.

◦If the Key Manager type displays external and the Restored column displays anything other than

yes, you need to complete some additional steps.

◦If the Key Manager type displays external and the Restored column displays anything other than

yes, you need to complete some additional steps.

2. If the Key Manager type displays onboard and the Restored column displays yes, manually back up

the OKM information:

a. Go to advanced privilege mode and enter ywhen prompted to continue: set -priv advanced

b. Enter the command to display the key management information: security key-manager onboard

show-backup

c. Copy the contents of the backup information to a separate file or your log file. You’ll need it in disaster

scenarios where you might need to manually recover OKM.

d. Return to admin mode: set -priv admin

e. You can safely shut down the controller.

3. If the Key Manager type displays external and the Restored column displays anything other than

yes:

a. Restore the external key management authentication keys to all nodes in the cluster: security key-

manager external restore

If the command fails, contact NetApp Support.

mysupport.netapp.com

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

key query

c. You can safely shut down the controller.

4. If the Key Manager type displays onboard and the Restored column displays anything other than yes:

a. Enter the onboard security key-manager sync command: security key-manager onboard sync

Enter the customer’s onboard key management passphrase at the prompt. If the passphrase cannot be

provided, contact NetApp Support.

mysupport.netapp.com

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

query

c. Verify that the Key Manager type shows onboard, and then manually back up the OKM information.

d. Go to advanced privilege mode and enter ywhen prompted to continue: set -priv advanced

e. Enter the command to display the key management backup information: security key-manager

onboard show-backup

f. Copy the contents of the backup information to a separate file or your log file. You’ll need it in disaster

scenarios where you might need to manually recover OKM.

g. Return to admin mode: set -priv admin

h. You can safely shut down the controller.

Shut down the impaired controller - FAS9500

Shut down or take over the impaired controller using one of the following options.

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

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.

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.

•If you have a SAN system, you must have checked event messages (cluster kernel-service show)

for impaired controller SCSI blade. The cluster kernel-service show command displays the node

name, quorum status of that node, availability status of that node, and operational status of that node.

Each SCSI-blade process should be in quorum with the other nodes in the cluster. Any issues must be

resolved before you proceed with the replacement.

•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 Synchronize a node with the cluster.

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

When you see Do you want to disable auto-giveback?, enter y.

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.

If the impaired controller is

displaying…

Then…

System prompt or password

prompt

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.

Remove the controller, replace the boot media, and transfer

the boot image - FAS9500

You must remove and open the controller module, locate and replace the boot media in

the controller, and then transfer the image to the replacement boot media.

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.

Steps

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

2. Unplug the cables from the impaired controller module, and keep track of where the cables were

connected.

3. Slide the terra cotta button on the cam handle downward until it unlocks.

Animation - Remove controller module

A10

A11

Cam handle release button

Cam handle

4. Rotate the cam handle so that it completely disengages the controller module from the chassis, and then

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.

5. Place the controller module lid-side up on a stable, flat surface, press the blue button on the cover, slide

the cover to the back of the controller module, and then swing the cover up and lift it off of the controller

module.

Controller module cover locking button

Step 2: Replace the boot media

You must locate the boot media in the controller and follow the directions to replace it.

Steps

1. Lift the black air duct at the back of the controller module and then locate the boot media using the

following illustration or the FRU map on the controller module:

Animation - Replace boot media

Press release tab

Boot media

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

3. Align the edges of the replacement boot media with the boot media socket, and then gently push it into the

socket.

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

5. Push the boot media down to engage the locking button on the boot media housing.

Autres manuels pour FAS9500

Table des matières

Autres manuels NetApp Stockage

NetApp

NetApp E-Series 3040 40U Manuel utilisateur

NetApp

NetApp SG1000 Manuel d'utilisation

NetApp

NetApp FAS2240-2 Manuel utilisateur

NetApp

NetApp FAS8700 Feuille d'instructions

NetApp

NetApp DiskShelf14mk4 FC Manuel utilisateur

NetApp

NetApp AFF A700s Manuel utilisateur

NetApp

NetApp AFF A200 Manuel utilisateur

NetApp

NetApp DE6900 Manuel utilisateur

NetApp

NetApp FAS2500 Manuel d'utilisation et d'entretien

NetApp

NetApp FAS500f Manuel utilisateur

NetApp

NetApp E5700 Manuel utilisateur

NetApp

NetApp NearStore R100 Manuel utilisateur

NetApp

NetApp SolidFire C-Series Manuel

NetApp

NetApp StorageGRID Webscale 10.4 Manuel du produit

NetApp

NetApp StorageGRID SG5600 Series Manuel d'utilisation

NetApp

NetApp StorageGRID Webscale SG5700 Series Manuel d'utilisation

NetApp

NetApp E Series Instructions d'utilisation

NetApp

NetApp AFF A200 Manuel de l'opérateur

NetApp

NetApp EF550 Manuel utilisateur

NetApp

NetApp AFF A400 Manuel utilisateur

NetApp

NetApp SG100 Feuille d'instructions

NetApp

NetApp FAS9000 Manuel

NetApp

NetApp FAS2800 Manuel

NetApp

NetApp FAS8300 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