![NetApp AFF A700s Manual Download Page 3](http://html1.mh-extra.com/html/netapp/aff-a700s/aff-a700s_manual_1669877003.webp)
Boot media
Overview of boot media replacement - AFF A700s
The primary boot media stores the ONTAP boot image that the system uses when it
boots. You can restore the primary boot media image by using the ONTAP image on the
secondary boot media, or if necessary, by using a USB flash drive.
If your secondary boot media has failed or is missing the image.tgz file, you must restore the primary boot
media using a USB flash drive. The drive must be formatted to FAT32 and must have the appropriate amount
of storage to hold the image_xxx.tgz file.
• The replacement process restores the var file system from the secondary boot media or USB flash drive to
the primary boot media.
• 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 A700s
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
.
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:
1