Advertisement
Shut down or take over the impaired controller using the appropriate procedure for
your configuration.
== Option 1: Shut down the controllers when replacing a chassis
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
Before you begin
You need:
• Local administrator credentials for ONTAP.
• NetApp onboard key management (OKM) cluster-wide passphrase if using storage encryption.
• SP/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
performing this procedure.
If using FlexArray array LUNs, follow the specific vendor storage array documentation for
the shutdown procedure to perform for those systems after performing this procedure.
If using SSDs, refer to
failure and data loss if powered off for more than two months
As a best practice before shutdown, you should:
• Perform additional
• Upgrade ONTAP to a recommended release for the system.
• Resolve any
Active IQ Wellness Alerts and
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 off line:
system node autosupport invoke -node * -type all -messages "MAINT=8h Power
Maintenance"
3. Identify the SP/BMC address of all nodes:
system service-processor show -node * -fields address
4. Exit the cluster shell:
230
SU490: (Impact: Critical) SSD Best Practices: Avoid risk of drive
system health
checks.
exit
Risks.
cluster.
after
Advertisement
