NetApp FAS9500 Manual de usuario

Maintain

ONTAP Systems

NetApp

July 19, 2022

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

systems/fas9500/add_io_module.html on July 19, 2022. Always check docs.netapp.com for the latest.

Table of Contents

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

Add an I/O module - FAS9500 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê1

Boot media . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê4

Hot-swap a caching module - FAS9500. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê20

Chassis. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê22

Controller module. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê35

Replace a DIMM - FAS9500 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê52

Replace the Destage Control Power Module containing the NVRAM11 battery - FAS9500 . . . . . . . . . . . . . Ê60

Swap out a fan - FAS9500 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê62

Replace an I/O module - FAS9500 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê63

Replace an LED USB module - FAS9500 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê65

Replace the NVRAM module and/or NVRAM DIMMs - FAS9500 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê66

Swap out a power supply - FAS9500 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê74

Replace the real-time clock battery - FAS9500 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê76

Maintain

Add an I/O module - FAS9500

You can add an I/O module to your system by either replacing a NIC or storage adapter

with a new one in a fully-populated system, or by adding a new NIC or storage adapter

into an empty chassis slot in your system.

Before you begin

•Check the NetApp Hardware Universe to make sure that the new I/O module is compatible with your

system and version of ONTAP you’re running.

•If multiple slots are available, check the slot priorities in NetApp Hardware Universe and use the best one

available for your I/O module.

•To non-disruptively add an I/O module, you must take over the target controller, remove the slot blanking

cover in the target slot or remove an existing I/O module, add the new or replacement I/O module, and then

giveback the target controller.

•Make sure that all other components are functioning properly.

Option 1: Add the I/O module to a system with open slots

You can add an I/O module into an empty module slot in your system as either a NIC or a storage module for

the SAS storage shelves.

1. Shutdown controller A:

a. Disable automatic giveback: storage failover modify -node local -auto-giveback

false

b. Take over the target node: storage failover takeover -ofnode target_node_name

The console connection shows that the node drops to the LOADER prompt when the take over is

complete.

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

3. Remove the target slot blanking cover:

a. Depress the lettered and numbered cam button.

b. Rotate the cam latch down until it is the open position.

c. Remove the blanking cover.

4. Install the I/O module:

a. Align the I/O module with the edges of the slot.

b. Slide the I/O module into the slot until the lettered and numbered I/O cam latch begins to engage with

the I/O cam pin.

c. Push the I/O cam latch all the way up to lock the module in place.

5. If the replacement I/O module is a NIC, cable the module to the data switches.

Make sure that any unused I/O slots have blanks installed to prevent possible thermal

issues.

6. Reboot the node from the LOADER prompt: bye

7. Give back the node from the partner node. storage failover giveback -ofnode

target_node_name

8. Enable automatic giveback if it was disabled: storage failover modify -node local -auto

-giveback true

9. If you are using slots 3 and/or 7 for networking, use the storage port modify -node <node name>

-port <port name> -mode network command to convert the slot for networking use.

10. Repeat these steps for controller B.

11. If you installed a storage I/O module, install and cable your SAS shelves, as described in Hot-adding a

SAS shelf.

Option 2: Add an I/O module in a system with no open slots

You must remove one or more existing NIC or storage modules in your system in order to install one or more

I/O modules into your fully-populated system.

1. If you are:

Replacing a… Then…

NIC I/O module with the same the

same number of ports

The LIFs will automatically migrate when its controller module is shut

down.

NIC I/O module with fewer ports Permanently reassign the affected LIFs to a different home port. See

Migrating a LIF for information about using System Manager to

permanently move the LIFs.

NIC I/O module with a storage I/O

module

Use System Manager to permanently migrate the LIFs to different

home ports, as described in Migrating a LIF.

2. Shut down controller A:

a. Disable automatic giveback: storage failover modify -node local -auto-giveback

false

b. Take over the target node: storage failover takeover -ofnode target_node_name

The console connection shows that the node drops to the LOADER prompt when the take over is

complete.

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

4. Unplug any cabling on the target I/O module.

5. Remove the target I/O module from the chassis:

a. Depress the lettered and numbered cam button.

The cam button moves away from the chassis.

b. Rotate the cam latch down until it is in a horizontal position.

The I/O module disengages from the chassis and moves about 1/2 inch out of the I/O slot.

c. Remove the I/O module from the chassis by pulling on the pull tabs on the sides of the module face.

Make sure that you keep track of which slot the I/O module was in.

Animation - Replacing an I/O module

Lettered and numbered I/O cam latch

I/O cam latch completely unlocked

6. Install the I/O module into the target slot:

a. Align the I/O module with the edges of the slot.

b. Slide the I/O module into the slot until the lettered and numbered I/O cam latch begins to engage with

the I/O cam pin.

c. Push the I/O cam latch all the way up to lock the module in place.

7. Repeat the remove and install steps to replace additional modules for controller A.

8. If the replacement I/O module is a NIC, cable the module or modules to the data switches.

9. Reboot the node from the LOADER prompt: bye

10. Give back the node from the partner node. storage failover giveback -ofnode

target_node_name

11. Enable automatic giveback if it was disabled: storage failover modify -node local -auto

-giveback true

12. If you added:

If I/O module is a… Then…

NIC module in slots 3 or 7, Use the storage port modify -node *<node name> -port

*<port name> -mode network command for each port.

If I/O module is a… Then…

Storage module Install and cable your SAS shelves, as described in Hot-adding a SAS

shelf.

13. Repeat these steps for controller B.

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

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 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” section of the ONTAP 9 NetApp Encryption Power Guide.

ONTAP 9 NetApp Encryption Power Guide

•If you have a SAN system, you must have checked event messages (event log show) for impaired

controller SCSI blade.

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

Otros manuales para FAS9500

Este manual sirve para los siguientes modelos

Tabla de contenidos

Otros manuales de Almacenamiento de NetApp

NetApp

NetApp SteelStore 30 Series Manual de usuario

NetApp

NetApp FAS2020 Manual

NetApp

NetApp DE6600 Manual de usuario

NetApp

NetApp HCI Manual de usuario

NetApp

NetApp FAS2700 Series Manual

NetApp

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

NetApp

NetApp E Series Manual de usuario

NetApp

NetApp DS2246 Manual

NetApp

NetApp FAS9500 Manual

NetApp

NetApp AFF A200 Manual de usuario

NetApp

NetApp DS4243 Manual

NetApp

NetApp AltaVault AVA400 Manual de instrucciones

NetApp

NetApp E Series Manual de usuario

NetApp

NetApp StorageGRID Webscale SG5700 Series Manual de funcionamiento

NetApp

NetApp StorageGRID SG5600 Series Manual de funcionamiento

NetApp

NetApp FAS2800 Manual

NetApp

NetApp AltaVault System Manual

NetApp

NetApp H410S Manual del propietario

NetApp

NetApp FAS500f Manual de usuario

NetApp

NetApp NearStore R100 Manual de usuario

NetApp

NetApp E Series Instrucciones de uso

NetApp

NetApp EF550 Manual de usuario

NetApp

NetApp FAS8700 Hoja de instrucciones

NetApp

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