Maintain
Boot media
Replace the boot media - FAS8200
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 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 node:
◦
The
impaired
node is the node on which you are performing maintenance.
◦
The
healthy node
is the HA partner of the impaired node.
Check onboard encryption keys as needed - FAS8200
Prior to shutting down the impaired node and checking the status of the onboard
encryption keys, you must check the status of the impaired node, disable automatic
giveback, and check what version of ONTAP the system 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
node shows false for eligibility and health, you must correct the issue before shutting down the impaired node;
see the
NetApp Encryption overview with the CLI
Steps
1. Check the status of the impaired node:
◦
If the impaired node is at the login prompt, log in as
admin
.
◦
If the impaired node is at the LOADER prompt and is part of HA configuration, log in as
admin
on the
healthy node.
◦
If the impaired node is in a standalone configuration and at LOADER prompt, contact NetApp Support.
2. If AutoSupport is enabled, suppress automatic case creation by invoking an AutoSupport message:
system node autosupport invoke -node * -type all -message
1
