NetApp AFF - Page 83

Maintain
Boot media
Overview of boot media replacement - AFF A200
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.
What you’ll need
You must have a USB flash drive, formatted to FAT32, with the appropriate amount of storage to hold the
image_xxx.tgz file.
Before you begin
• 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 controller:
◦ The impaired controller is the controller on which you are performing maintenance.
◦ The healthy controller is the HA partner of the impaired controller.
Check onboard encryption keys - AFF A200
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
81