Lenovo ThinkSystem DM3010H - Maintenance Procedures; 5.1. Boot Media Replacement

Chapter 5. Maintain
5.1. Boot media
5.1.1. Overview of boot media replacement - DM3010H
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 file.
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.
5.1.2. Check onboard encryption keys - DM3010H
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
Synchronize a node with the cluster.
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.
30