e. Release the latches to lock the controller module into place.
f. If you have not already done so, reinstall the cable management device.
8. Interrupt the boot process by pressing Ctrl-C to stop at the LOADER prompt.
If you miss this message, press Ctrl-C, select the option to boot to Maintenance mode, and then halt
the node to boot to LOADER.
9.
From the LOADER prompt, boot the recovery image from the USB flash drive:
boot_recovery
The image is downloaded from the USB flash drive.
10. When prompted, either enter the name of the image or accept the default image displayed inside the
brackets on your screen.
11. After the image is installed, start the restoration process:
a. Record the IP address of the impaired node that is displayed on the screen.
b.
Press
y when prompted to restore the backup configuration.
c.
Press
y when prompted to overwrite /etc/ssh/ssh_host_dsa_key.
12. From the partner node in advanced privilege level, start the configuration synchronization using the IP
address recorded in the previous step:
system node restore-backup -node local -target
-address impaired_node_IP_address
13.
If the restore is successful, press
y on the impaired node when prompted to use the restored copy?.
14.
Press
y when you see confirm backup procedure was successful, and then press y when prompted to
reboot the node.
15. Verify that the environmental variables are set as expected.
a. Take the node to the LOADER prompt.
From the ONTAP prompt, you can issue the command system node halt -skip-lif-migration-before
-shutdown true -ignore-quorum-warnings true -inhibit-takeover true.
b.
Check the environment variable settings with the
printenv command.
c.
If an environment variable is not set as expected, modify it with the
setenv environment-
variable-name changed-value
command.
d.
Save your changes using the
savenv command.
e. Reboot the node.
16.
With the rebooted impaired node displaying the
Waiting for giveback… message, perform a
giveback from the healthy node:
512
To Next Page
Loading...
