chassis from the equipment rack or system cabinet and install the replacement chassis in
its place.
All other components in the system must be functioning properly; if not, you must contact technical support.
• You can use this procedure with all versions of ONTAP supported by your system.
• This procedure is written with the assumption that you are moving the bezel, NVMe drives, and controller
modules to the new chassis, and that the replacement chassis is a new component from NetApp.
• This procedure is disruptive. For a two-node cluster, you will have a complete service outage and a
partial outage in a multi-node cluster.
Shut down the controllers - AFF A70, AFF A90
This procedure is for 2-node, non-MetroCluster configurations only. If you have a system
with more than two nodes, see
How to perform a graceful shutdown and power up of one
HA pair in a 4-node cluster
.
Before you begin
You need:
• Local administrator credentials for ONTAP.
• NetApp onboard key management (OKM) cluster-wide passphrase if using storage encryption or
NVE/NAE.
• BMC accessability for each controller.
• Stop all clients/host from accessing data on the NetApp system.
• Suspend external backup jobs.
• Necessary tools and equipment for the replacement.
If the system is a NetApp StorageGRID or ONTAP S3 used as FabricPool cloud tier, refer to the
Gracefully shutdown and power up your storage system Resolution Guide after performing this
procedure.
If using SSDs, refer to SU490: (Impact: Critical) SSD Best Practices: Avoid risk of drive failure
and data loss if powered off for more than two months
As a best practice before shutdown, you should:
• Perform additional
system health checks.
• Upgrade ONTAP to a recommended release for the system.
• Resolve any
Active IQ Wellness Alerts and Risks. Make note of any faults presently on the system, such as
LEDs on the system components.
Steps
1. Log into the cluster through SSH or log in from any node in the cluster using a local console cable and a
laptop/console.
2. Turn off AutoSupport and indicate how long you expect the system to be offline:
20