NetApp FAS8200 Series Manuel utilisateur

Maintain

ONTAP Systems

NetApp

November 23, 2021

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

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

Table of Contents

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

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

Replace the caching module - FAS8200 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê25

Chassis. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê36

Controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê50

Replace a DIMM - FAS8200 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê77

Swap out a fan - FAS8200 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê89

Replace the NVMEM battery - FAS8200 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê91

Replace a PCIe card - FAS8200 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê102

Swap out a power supply - FAS8200 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê111

Replace the real-time clock battery - FAS8200 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê113

Maintain

Boot media

Replace the boot media - FAS8200

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

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

Verifying 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

a. If the Restored column displays yes manually backup 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.

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

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 backup 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 backup the OKM information:security key-manager backup show

Make sure that OKM information is saved in your log file. This info 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 shutdown 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.

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.

Option 1: Most systems

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:

Autres manuels pour FAS8200 Series

Ce manuel convient aux modèles suivants

Table des matières

Autres manuels NetApp Stockage

NetApp

NetApp AFF A400 Manuel utilisateur

NetApp

NetApp AFF A200 Manuel utilisateur

NetApp

NetApp AltaVault Cloud Integrated Storage 4.1 Instructions d'installation et d'entretien

NetApp

NetApp FAS2020 Manuel

NetApp

NetApp AFF A200 Manuel de l'opérateur

NetApp

NetApp AFF A400 Manuel utilisateur

NetApp

NetApp FAS2700 Series Manuel

NetApp

NetApp DE6600 Manuel utilisateur

NetApp

NetApp DS4243 Manuel

NetApp

NetApp NearStore R100 Manuel utilisateur

NetApp

NetApp SOLIDFIRE Manuel utilisateur

NetApp

NetApp AFF A250 Manuel utilisateur

NetApp

NetApp AltaVault System Manuel

NetApp

NetApp E Series Manuel utilisateur

NetApp

NetApp EF550 Manuel utilisateur

NetApp

NetApp E Series Manuel utilisateur

NetApp

NetApp FAS8300 Manuel utilisateur

NetApp

NetApp StorageGRID Webscale SG6000 Series Manuel utilisateur

NetApp

NetApp E Series Instructions d'utilisation

NetApp

NetApp AFF A400 Manuel utilisateur

NetApp

NetApp SG1000 Manuel d'utilisation

NetApp

NetApp SolidFire C-Series Manuel

NetApp

NetApp H410S Manuel

NetApp

NetApp FAS500f Manuel utilisateur

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