80xx systems Replacing a boot device For all operating

80xx systems Replacing a boot device For all operating
80xx systems
For all operating environments
Replacing a boot device
The boot device stores a primary and secondary set of system files (also called the boot image) that the system uses when it
boots. The steps you follow to replace a boot device differ depending on whether your system is running clustered Data ONTAP
or 7-Mode.
Before you begin
Before extracting the compressed system files during the boot device installation process, you must make sure that the utility
you use is set to suppress any automatic CR/LF conversions in the extracted files.
If you experience any problems during netboot, you can verify the integrity of the files extracted from the package by comparing
the md5sum values stored in the MD5SUMS file.
About this task
•
You must replace the failed component with a replacement FRU component you received from your provider.
•
The steps for replacing a boot device in a system running 7-Mode are different than for a system running clustered Data
ONTAP.
You must use the correct procedure for your version of Data ONTAP 8.x.
•
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.
Choices
• Replacing a boot device in a system running in 7-Mode on page 1
• Replacing a boot device in a system running clustered Data ONTAP on page 13
Replacing a boot device in a system running in 7-Mode
Replacing a boot device running in 7-Mode involves shutting down the system, removing the old boot device, and transferring
the system files to the new boot device.
About this task
This procedure is for systems running in 7-Mode. If your system is running clustered Data ONTAP, you cannot use this
procedure and must use the procedure for clustered Data ONTAP instead.
Steps
1.
2.
3.
4.
Shutting down a node operating in 7-Mode on page 2
Opening the system on page 3
Removing the boot device from the controller module on page 4
Installing the boot device on page 6
215-08011_B0
August 2015
Copyright © 2015 NetApp, Inc. All rights reserved.
Web: www.netapp.com • Feedback: doccomments@netapp.com
1
Shutting down a node operating in 7-Mode
When performing maintenance on a system operating in 7-Mode, you must shut down the node. Depending on your system's
configuration, you might also need to turn off the power supplies.
About this task
Your system's configuration determines whether you turn off the power supplies after shutting down the node:
•
If you have one controller module in the chassis that is either part of an HA pair or in a stand-alone configuration, you must
turn off the power supplies in the impaired node chassis.
Shutting down a node in an HA pair
To shut down the node, you must determine the status of the node and, if necessary, take over the node so that the partner
continues to serve data from the node's storage.
Steps
1. Check the HA status of the impaired node by entering the following command from either node in the HA pair that is
displaying the Data ONTAP prompt:
cf status
2. Take the appropriate action based on the takeover status of the node.
If the impaired node...
Then...
Has been taken over by the healthy
node and is halted
Go to the next step.
Has not been taken over by the healthy
node and is running
Take over the impaired node from the prompt of the healthy node:
cf takeover
3. Wait at least two minutes after takeover of the impaired node to ensure that the takeover was completed successfully.
4. If the impaired node is not at the LOADER prompt and is showing Waiting for giveback, press Ctrl-C and respond Y
to halt the node.
5. With the impaired node showing the Waiting for giveback message or halted, shut it down, depending on your
configuration:
If the Service Processor (SP)...
Then...
Is configured
Log in to the SP, and then enter the following command:
system power off
Is not configured, and the system is in
a dual-chassis HA pair in which each
controller is in a separate chassis
Manually shut down the power supplies on the impaired node.
Is not configured, and the system is in
a single-chassis HA pair in which both
controllers are in the same chassis and
share power supplies
At the prompt of the impaired node, press Ctrl-C and respond Y to halt the node.
6. If the nodes are in a dual-chassis HA pair, unplug the impaired node power cords from the power source.
2
Replacing a boot device
Shutting down a node in a stand-alone configuration
For a node that is not configured with a high-availability (HA) partner, you must perform a clean shutdown (ensuring that all
data has been written to disk) and disconnect the power supplies.
Steps
1. Shut down the node if it is not already shut down:
halt -t 0
2. Shut down the power supplies, and then unplug both power cords from the source.
The system is ready for maintenance.
Opening the system
If you want to access components inside the controller module, you must open the system.
Steps
1. If you are not already grounded, properly ground yourself.
2. Loosen the hook and loop strap binding the cables to the cable management device, and then unplug the system cables and
SFPs (if needed) from the controller module, and keep track of where the cables were connected.
Leave the cables in the cable management device so that when you reinstall the cable management device, the cables are
organized.
3. Remove the cable management device from the controller module and set it aside.
Note: The 8020 controller module uses cable management arms, while the rest of the 80xx family uses a cable
management tray.
4. Loosen the thumbscrew on the cam handle of the controller module .
1
2
8020 controller module cam handle
1
2
Thumbscrew
Cam handle
Replacing a boot device in a system running in 7-Mode
3
1
2
Any other 80xx controller module cam handle
1
2
Thumbscrew
Cam handle
5. Pull the cam handle downward and begin to slide the controller module out of the chassis.
If you have...
Then...
A 8020 system
Slide the controller module completely out of the system.
Note: Make sure that you support the bottom of the controller module with your free hand
and set it aside.
Any other 80xx model
Slide the controller module out of the system until it catches, press the release latch on the left
side of the controller module, and then slide the controller module out of the system and set it
aside.
Note: Make sure that you support the bottom of the controller module with your free hand.
Removing the boot device from the controller module
You must remove the old or failed boot device from the impaired node in your system prior to installing the new or replacement
boot device.
Steps
1. If you are not already grounded, properly ground yourself.
2. Remove the controller module and locate the boot device holder.
Use the FRU map on the controller module or the following illustrations to help you locate the boot device enclosure:
4
Replacing a boot device
1
2
8020 controller module
1
2
Boot device
Boot device holder; not removable
Replacing a boot device in a system running in 7-Mode
5
1
1
9
2
Other 80xx controller modules
1
2
Boot device
Boot device holder; not removable
3. Open the boot device cover and hold the boot device by its edges at the notches in the boot device housing, gently lift it
straight up and out of the housing.
Attention: Always lift the boot device straight up out of the housing. Lifting it out at an angle can bend or break the
connector pins in the boot device.
4. Set the boot device aside.
Installing the boot device
After you remove the old boot device, you must transfer system files and restore configuration information to your replacement
boot device.
Choices
• Installing the boot device and transferring system files nondisruptively using netboot in systems running Data ONTAP 8.2.1
and later on page 7
• Installing the boot device and transferring system files disruptively using netboot on page 10
6
Replacing a boot device
Installing the boot device and transferring system files nondisruptively using netboot in systems running Data
ONTAP 8.2.1 and later
You can transfer the system files and restore configuration information to your HA pair nondisruptively by using netboot and the
healthy node.
Before you begin
•
You must have the blank replacement boot device that you received from your provider.
•
You must have a network interface to the HA pair healthy node.
•
You must have a separate IP address to use to netboot the impaired node.
About this task
The following procedure is written with the assumption that the impaired node has been taken over by the healthy node and that
the impaired node has booted to the LOADER prompt after the takeover has been completed.
Steps
1. Download and extract the file used for performing the netboot of your system:
a. Download the appropriate netboot.tgz file for your platform from the NetApp Support Site to a web-accessible
directory.
b. Change to the web-accessible directory.
c. Extract the contents of the netboot.tgz file to the target directory by entering the following command:
tar -zxvf netboot.tgz
Your directory listing should contain the following directory:
netboot/
2. Download the image.tgz file from the NetApp Support Site to the web-accessible directory.
Your directory listing should contain the following file and directory:
image.tgz netboot/
3. If you are not already grounded, properly ground yourself.
4. Turn the controller module so that you can locate the boot device holder.
Use the FRU map on the controller module to help you locate the boot device holder.
5. Open the boot device cover, if applicable.
6. Align the boot device with the boot device socket or connector, and then firmly push the boot device straight down into the
socket or connector.
Important: Always install the boot device by aligning the front of the boot device squarely over the pins in the socket at
the front of the boot device housing. Installing the boot device at an angle or over the rear plastic pin first can bend or
damage the pins in the boot device connector.
7. Check the boot device to make sure that it is seated squarely and completely in the socket or connector.
If necessary, remove the boot device and reseat it into the socket.
8. Close the boot device cover.
9. Align the end of the controller module with the opening in the chassis, and then gently push the controller module halfway
into the system.
Replacing a boot device in a system running in 7-Mode
7
10. Recable the controller module as needed, and then push the controller module all the way into the chassis.
11. Tighten the thumb screw on the cam handle, reinstall the cable management device, and then tighten the hook and loop strap
that binds the cables together.
12. The next step depends on your system configuration:
If your system has...
Then...
One controller module in the chassis
Complete the following substeps:
Two controller modules in the chassis
a.
Reconnect the power cables to the power supplies and to the power sources, and then turn
on the power.
The system begins to boot and stops at the LOADER prompt.
b.
Go to the next step.
The node already began rebooting and stops at the LOADER prompt; go to the next step.
13. Depending on your network configuration, enter one of the following commands at the LOADER prompt:
If you...
Then...
Have DHCP enabled
Enter the following command:
ifconfig e0M -auto
Do not have DHCP enabled
Enter the following command:
ifconfig e0M -addr=filer_addr -mask=netmask -gw=gateway dns=dns_addr -domain=dns_domain
filer_addr is the IP address of the storage system.
netmask is the network mask of the storage system.
gateway is the gateway for the storage system.
dns_addr is the IP address of a name server on your network.
dns_domain is the Domain Name System (DNS) domain name. If you use this optional
parameter, you do not need a fully qualified domain name in the netboot server URL; you
need only the server’s host name.
Note: To netboot the node when your system is running in 7-Mode Data ONTAP, use an IP
address that is not the management IP address for the target. If your system is running
clustered Data ONTAP, you can use the management IP address.
Note: Other parameters might be necessary for your interface. For details, use the help
ifconfig command at the LOADER prompt.
14. At the LOADER prompt, netboot the kernel:
netboot http://path_to_web-accessible_directory/netboot/kernel
15. Select the Install new software first option from the displayed menu.
This menu option downloads and installs the new Data ONTAP image to the boot device.
•
Select y when prompted with the message that this procedure is not supported for non-disruptive upgrade on an HA pair
active/active configuration .
•
Select y when warned that this process will replace existing Data ONTAP software with new software.
•
Enter the path as follows when prompted for the URL of the image.tgz file:
http://path_to_the_web-accessible_directory/image.tgz
8
Replacing a boot device
16. Enter y when prompted regarding non-disruptive upgrade or replacement of the software.
17. Enter the path to the image.tgz file when you see the following prompt:
What is the URL for the package?
http://path_to_web-accessible_directory/image.tgz
18. Restore the backup configuration on the impaired node by entering y and then entering the IP address of the server
containing the varfs.tgz file when you see the following screen:
****************************************************************
*
Restore Backup Configuration
*
* This procedure only applies to storage controllers that
*
* are configured as an HA pair.
*
*
*
* Choose Yes to restore the "varfs" backup configuration
*
* from the SSH server. Refer to the Boot Device Replacement *
* guide for more details.
*
* Choose No to skip the backup and recovery and return to the *
* boot menu.
*
****************************************************************
Do you want to restore the backup configuration
now? {y|n} y
Start the restore_backup procedure on this node's HA partner.
19. Restore the backup configuration:
restore_backup target_node.netboot_ip.address
20. Restore the configuration from the varfs.tgz file and reboot the impaired node, as shown in the following example:
Example
The restore configuration has been copied
from the HA partner to this node,
would you like to use this restored copy
now? {y|n} y
Boot device: /dev/da0 found...
Checking /dev/da0s1 file system... success.
Mounting /dev/da0s1 to /cfcard... success.
Checking /cfcard/x86_64/freebsd mount point... success.
Gzip checking /var/home/root/varfs.tgz... success.
Restoring backup configuration...
Backup Configuration from Thu Jun 19 18:01:53 UTC 2014 successfully restored
The node must be rebooted to start using the newly installed software. Do you
want to reboot now? {y|n} y
21. After the impaired node has rebooted and is displaying the Waiting for giveback message, complete the procedure by
giving back the node from the healthy node console:
cf giveback
Replacing a boot device in a system running in 7-Mode
9
Installing the boot device and transferring system files disruptively using netboot
You can transfer the system files and restore configuration information to your system by using netboot to copy the system files
to the replacement boot device.
Before you begin
•
You must have the blank replacement boot device you received from your provider.
•
You must have access to an HTTP server.
•
You must have access to the NetApp Support Site at mysupport.netapp.com.
This enables you to download the necessary system files for your platform and version of Data ONTAP running on it.
About this task
You can use this disruptive procedure in either a stand-alone system or an HA configuration during scheduled maintenance on
the system or if the healthy node is not fully functional.
This procedure is disruptive, even when using it with a system in an HA configuration, because an immediate giveback and retakeover occur during the procedure. If possible, you should use the nondisruptive procedure for HA configurations for your
version of Data ONTAP software operating in 7-Mode.
Steps
1. Download and extract the file used for performing the netboot of your system:
a. Download the appropriate netboot.tgz file for your platform from the NetApp Support Site to a web-accessible
directory.
b. Change to the web-accessible directory.
c. Extract the contents of the netboot.tgz file to the target directory by entering the following command:
tar -zxvf netboot.tgz
Your directory listing should contain the following directory:
netboot/
2. Download the image.tgz file from the NetApp Support Site to the web-accessible directory.
Your directory listing should contain the following file and directory:
image.tgz netboot/
3. If you are not already grounded, properly ground yourself.
4. Turn the controller module so that you can locate the boot device holder.
Use the FRU map on the controller module to help you locate the boot device holder.
5. Open the boot device cover, if applicable.
6. Align the boot device with the boot device socket or connector, and then firmly push the boot device straight down into the
socket or connector.
Important: Always install the boot device by aligning the front of the boot device squarely over the pins in the socket at
the front of the boot device housing. Installing the boot device at an angle or over the rear plastic pin first can bend or
damage the pins in the boot device connector.
7. Check the boot device to make sure that it is seated squarely and completely in the socket or connector.
If necessary, remove the boot device and reseat it into the socket.
10
Replacing a boot device
8. Close the boot device cover.
9. Align the end of the controller module with the opening in the chassis, and then gently push the controller module halfway
into the system.
10. Recable the controller module as needed, and then push the controller module all the way into the chassis.
11. Tighten the thumb screw on the cam handle, reinstall the cable management device, and then tighten the hook and loop strap
that binds the cables together.
12. The next step depends on your system configuration:
If your system has...
Then...
One controller module in the chassis
Complete the following substeps:
Two controller modules in the chassis
a.
Reconnect the power cables to the power supplies and to the power sources, and then turn
on the power.
The system begins to boot and stops at the LOADER prompt.
b.
Go to the next step.
The node already began rebooting and stops at the LOADER prompt; go to the next step.
13. Depending on your network configuration, enter one of the following commands at the LOADER prompt:
If you...
Then...
Have DHCP enabled
Enter the following command:
ifconfig e0M -auto
Do not have DHCP enabled
Enter the following command:
ifconfig e0M -addr=filer_addr -mask=netmask -gw=gateway dns=dns_addr -domain=dns_domain
filer_addr is the IP address of the storage system.
netmask is the network mask of the storage system.
gateway is the gateway for the storage system.
dns_addr is the IP address of a name server on your network.
dns_domain is the Domain Name System (DNS) domain name. If you use this optional
parameter, you do not need a fully qualified domain name in the netboot server URL; you
need only the server’s host name.
Note: To netboot the node when your system is running in 7-Mode Data ONTAP, use an IP
address that is not the management IP address for the target. If your system is running
clustered Data ONTAP, you can use the management IP address.
Note: Other parameters might be necessary for your interface. For details, use the help
ifconfig command at the LOADER prompt.
14. At the LOADER prompt, enter the following command:
netboot http://path_to_the_web-accessible_directory/netboot/kernel
The system begins to boot, but stops at the Boot menu.
15. Select the Install new software first option from the displayed menu.
This menu option downloads and installs the new Data ONTAP image to the boot device.
•
Select y when prompted with the message that this procedure is not supported for non-disruptive upgrade on an HA pair
active/active configuration .
Replacing a boot device in a system running in 7-Mode
11
•
Select y when warned that this process will replace existing Data ONTAP software with new software.
•
Enter the path as follows when prompted for the URL of the image.tgz file:
http://path_to_the_web-accessible_directory/image.tgz
16. Complete the following substeps:
a. Enter n to skip the backup recovery when you see the following prompt:
**************************************************************
*
Restore Backup Configuration
*
* This procedure only applies to storage controllers that
*
* are configured as an HA pair.
*
*
*
* Choose Yes to restore the 'varfs' backup configuration
*
* from a TFTP server. Refer to the Boot Device Replacement *
* guide for more details.
*
* Choose No to skip the back up recovery and return to the *
* boot menu.
*
**************************************************************
Do you want to restore the backup configuration
now? {y|n} n
b. Reboot the node by entering y when you see the following prompt:
The node must be rebooted to start using the newly installed
software. Do you want to reboot now? {y/n} y
The controller module reboots, but stops at the Boot menu because the boot device was reformatted and the configuration
data needs to be restored.
17. Select the Update flash from backup config option from the displayed menu.
18. Enter y when you see the following prompt:
This will replace all flash-based configuration with the last backup to
disk. Are you sure you want to continue?: y
The system automatically reboots when the update flash (syncflash) process is complete.
19. Your next step depends on your system configuration.
If your system is...
Description
A stand-alone configuration
You can begin using your system after the node reboots to complete restoring the backup
configuration.
An HA pair
Complete the following substeps after the impaired node is displaying the Waiting for
Giveback... message:
a.
Enter the following command from the healthy node:
cf giveback
The impaired node takes back its storage, completes booting up, and then reboots and is
again taken over by the healthy node.
b.
Enter the following command from the healthy node:
cf giveback
The impaired node takes back its storage and completes booting up with the restored
configuration.
12
Replacing a boot device
Replacing a boot device in a system running clustered Data ONTAP
Replacing a boot device in clustered Data ONTAP involves shutting down the node, removing the old boot device, and
transferring the system files to the new boot device.
About this task
This procedure is for systems running clustered Data ONTAP. If your system is running Data ONTAP 7-Mode, you must use
that procedure instead.
Steps
1.
2.
3.
4.
Shutting down the target controller on page 13
Opening the system on page 17
Removing the boot device from the controller module on page 19
Installing the boot device on page 20
Shutting down the target controller
You shut down or take over the target controller using different procedures, depending on the storage system hardware
configuration.
Choices
• Shutting down a node operating in clustered Data ONTAP on page 13
• Shutting down a node in a two-node MetroCluster configuration on page 16
Shutting down a node operating in clustered Data ONTAP
To shut down the impaired node, you must determine the status of the node and, if necessary, take over the node so that the
healthy node continues to serve data from the impaired node storage.
Steps
1. If the system is running clustered Data ONTAP, check the status of the nodes in the cluster:
a. Change to the advance privilege level:
set -privilege advanced
b. Enter the following command at the system console of either node:
cluster show -epsilon *
The command produces output similar to the following:
Node
-----------node1
node2
node3
node4
Health
------true
true
true
true
Eligibility
Epsilon
------------ -----------true
true
true
false
true
false
true
false
4 entries were displayed.
Note: Epsilon must not be on a node to be replaced.
Replacing a boot device in a system running clustered Data ONTAP
13
Note: In a cluster with a single HA pair, Epsilon will not be assigned to either node.
c. Take one of the following actions, depending on the result of the command:
If...
All nodes show true for both health
and eligibility and Epsilon is not
assigned to the impaired node.
Then...
a.
set -privilege admin
b.
All nodes show true for both health
and eligibility and Epsilon is assigned
to the impaired node
Exit advanced mode:
Proceed to Step 3.
Complete the following steps to move Epsilon:
a.
Remove Epsilon from the node:
cluster modify -node node1 -epsilon false
b.
Assign Epsilon to a node in the cluster:
cluster modify -node node4 -epsilon true
c.
Exit advanced mode:
set -privilege admin
d.
The impaired node shows false for
health and is the Epsilon node.
Go to Step 3.
Complete the following steps:
a.
Change to the advance privilege level:
set -privilege advanced
b.
Remove Epsilon from the node:
cluster modify -node node1 -epsilon false
c.
Assign Epsilon to a node in the cluster:
cluster modify -node node4 -epsilon true
d.
Exit advanced mode:
set -privilege admin
The impaired node shows false for
health and is not the Epsilon node.
e.
Proceed to the next step.
a.
Exit advanced mode:
set -privilege admin
Any nodes show false for eligibility.
b.
Proceed to the next step.
a.
Resolve any cluster issues as needed before continuing with this procedure.
b.
Exit advanced mode:
set -privilege admin
Any nodes other than the impaired
node show false for health.
a.
Correct the problems that cause the health issues on the nodes before continuing with this
procedure.
b.
Exit advanced mode:
set -privilege admin
14
Replacing a boot device
2. If the impaired node is part of an HA pair, disable auto-giveback from the console of the healthy node:
storage failover modify -node local -auto-giveback false
3. Bring the impaired node to the LOADER prompt:
If the impaired node is in...
Then...
A stand-alone configuration and is
running
Halt the impaired node:
A stand-alone configuration and is not
running and not at the LOADER
prompt
Resolve any issues that caused the node to quit running, power cycle it, and then halt the boot
process by entering Ctrl-C and responding Y to take the node to the LOADER prompt.
An HA pair
If the impaired node is at the LOADER prompt, it is ready for service. Otherwise, take the
applicable action:
system -node halt impaired_node_name
•
If the impaired node is showing the Data ONTAP prompt, take over the impaired node
over from the healthy node and be prepared to interrupt the reboot:
storage failover takeover -ofnode impaired_node_name
When prompted to interrupt the reboot, press Ctrl-C to go to the LOADER prompt.
Note: In a two-node cluster, if the impaired node holds Epsilon, you must move it to
the healthy node before halting the impaired node.
•
If the impaired node display is showing Waiting for giveback, press
Ctrl-C
and respond Y to take the node to the LOADER prompt.
•
If the impaired node is not showing Waiting for giveback or is not showing a
Data ONTAP prompt, power cycle the node.
Contact technical support if the node does not respond to the power cycle.
4. Shut down the impaired node.
Note: If the system is in an HA pair the node should be at the LOADER prompt.
The method you use to shut down the node depends on whether remote management through a Service Processor (SP) is
used, and whether the system is in a dual-chassis or single-chassis configuration.
If the SP is...
Then...
Configured
Log in to the impaired node SP and turn off the power using the following command:
system power off
Not configured, and the system is in a
dual-chassis HA pair in which each
controller is in a separate chassis
Manually shut down the power supplies on the impaired node.
Not configured, and the system is in a
single-chassis HA pair in which both
controllers are in the same chassis and
share power supplies
At the impaired node prompt, press Ctrl-C and respond Y to halt the node.
5. If the system is in a dual-chassis HA pair or stand-alone configuration, turn off the power supplies, and then unplug the
impaired node power cords from the power source.
Replacing a boot device in a system running clustered Data ONTAP
15
Shutting down a node in a two-node MetroCluster configuration
To shut down the impaired node, you must determine the status of the node and, if necessary, switch over the node so that the
healthy node continues to serve data from the impaired node's storage.
Steps
1. Check the MetroCluster status to determine if the impaired node has automatically switched over to the healthy node:
metrocluster show
2. Depending on whether an automatic switchover has occurred, proceed according to the following table:
If the impaired node...
Then...
Has automatically switched over
Proceed to the next step.
Has not automatically switched over
Perform a planned switchover operation from the healthy node:
metrocluster switchover
Has not automatically switched over
and planned switchover with the
metrocluster switchover
command fails
a.
Halt the impaired controller:
system node halt
b.
Perform a forced switchover operation:
metrocluster switchover -forced on disaster true
3. Resynchronize the data aggregates by running the metrocluster heal -phase aggregates command from the
surviving cluster.
Example
controller_A_1::> metrocluster heal -phase aggregates
[Job 130] Job succeeded: Heal Aggregates is successful.
If the healing is vetoed, you have the option of reissuing the metrocluster heal command with the –override-vetoes
parameter. If you use this optional parameter, the system overrides any soft vetoes that prevent the healing operation.
4. Verify that the operation has been completed by running the metrocluster operation show command.
Example
controller_A_1::> metrocluster operation show
Operation: heal-aggregates
State: successful
Start Time: 7/25/2014 18:45:55
End Time: 7/25/2014 18:45:56
Errors: -
5. Check the state of the aggregates by running the storage aggregate show command.
Example
controller_A_1::> storage aggregate show
Aggregate
Size Available Used% State
#Vols Nodes
RAID Status
--------- -------- --------- ----- ------- ------ ---------------- -----------...
aggr_b2
227.1GB
227.1GB
0% online
0 mcc1-a2
raid_dp, mirrored,
normal...
16
Replacing a boot device
6. Heal the root aggregates by running the metrocluster heal -phase root-aggregates command.
Example
mcc1A::> metrocluster heal -phase root-aggregates
[Job 137] Job succeeded: Heal Root Aggregates is successful
If the healing is vetoed, you have the option of reissuing the metrocluster heal command with the –override-vetoes
parameter. If you use this optional parameter, the system overrides any soft vetoes that prevent the healing operation.
7. Ensure that the heal operation is complete by running the metrocluster operation show command on the destination
cluster:
Example
mcc1A::> metrocluster operation show
Operation: heal-root-aggregates
State: successful
Start Time: 7/29/2014 20:54:41
End Time: 7/29/2014 20:54:42
Errors: -
8. Wipe clean the impaired node's NVRAM:
a. Enter the following command at the LOADER prompt: boot_diags
b. Enter the following command at the diagnostics prompt:
sldiag version
c. Enter the following command at the diagnostics prompt:
sldiag option modify nvram_wipeclean enable
d. Enter the following command at the diagnostics prompt:
sldiag option modify nvram_wipeclean run
When you see NVRAM wipe-clean is DONE, go to the next step.
9. Shut down the impaired node.
The method you use to shut down the node depends on whether remote management through a Service Processor (SP) is
used, and whether the system is in a dual-chassis or single-chassis configuration.
If the SP is...
Then...
Configured
Log in to the impaired node SP and turn off the power using the following command:
system power off
Not configured
Manually shut down the power supplies on the impaired node.
Opening the system
If you want to access components inside the controller module, you must open the system.
Steps
1. If you are not already grounded, properly ground yourself.
Replacing a boot device in a system running clustered Data ONTAP
17
2. Loosen the hook and loop strap binding the cables to the cable management device, and then unplug the system cables and
SFPs (if needed) from the controller module, and keep track of where the cables were connected.
Leave the cables in the cable management device so that when you reinstall the cable management device, the cables are
organized.
3. Remove the cable management device from the controller module and set it aside.
Note: The 8020 controller module uses cable management arms, while the rest of the 80xx family uses a cable
management tray.
4. Loosen the thumbscrew on the cam handle of the controller module .
1
2
8020 controller module cam handle
1
2
Thumbscrew
Cam handle
1
2
Any other 80xx controller module cam handle
1
2
Thumbscrew
Cam handle
5. Pull the cam handle downward and begin to slide the controller module out of the chassis.
18
Replacing a boot device
If you have...
Then...
A 8020 system
Slide the controller module completely out of the system.
Note: Make sure that you support the bottom of the controller module with your free hand
and set it aside.
Any other 80xx model
Slide the controller module out of the system until it catches, press the release latch on the left
side of the controller module, and then slide the controller module out of the system and set it
aside.
Note: Make sure that you support the bottom of the controller module with your free hand.
Removing the boot device from the controller module
You must remove the old or failed boot device from the impaired node in your system prior to installing the new or replacement
boot device.
Steps
1. If you are not already grounded, properly ground yourself.
2. Remove the controller module and locate the boot device holder.
Use the FRU map on the controller module or the following illustrations to help you locate the boot device enclosure:
1
2
8020 controller module
1
Boot device
Replacing a boot device in a system running clustered Data ONTAP
19
2
Boot device holder; not removable
1
1
9
2
Other 80xx controller modules
1
2
Boot device
Boot device holder; not removable
3. Open the boot device cover and hold the boot device by its edges at the notches in the boot device housing, gently lift it
straight up and out of the housing.
Attention: Always lift the boot device straight up out of the housing. Lifting it out at an angle can bend or break the
connector pins in the boot device.
4. Set the boot device aside.
Installing the boot device
After you remove the old boot device, you must transfer system files and restore configuration information to your replacement
boot device.
Choices
• Installing the boot device and transferring system files nondisruptively using netboot in systems running Data ONTAP 8.2.1
and later on page 21
20
Replacing a boot device
• Installing the boot device and transferring system files disruptively using netboot on page 24
Installing the boot device and transferring system files nondisruptively using netboot in systems running Data
ONTAP 8.2.1 and later
You can transfer the system files and restore configuration information to your HA pair nondisruptively by using netboot and the
healthy node.
Before you begin
•
You must have the blank replacement boot device you received from your provider.
•
You must have a network interface to the HA pair healthy node.
•
You must have a separate IP address to use to netboot the impaired node.
About this task
The following procedure is written with the assumption that the impaired node has been taken over by the healthy node and that
the impaired node has booted to the LOADER after the takeover has been completed.
Steps
1. Download and extract the file used for performing the netboot of your system:
a. Download the appropriate netboot.tgz file for your platform from the NetApp Support Site to a web-accessible
directory.
b. Change to the web-accessible directory.
c. Extract the contents of the netboot.tgz file to the target directory by entering the following command:
tar -zxvf netboot.tgz
Your directory listing should contain the following directory:
netboot/
2. Download the image.tgz file from the NetApp Support Site to the web-accessible directory.
Your directory listing should contain the following file and directory:
image.tgz netboot/
3. If you are not already grounded, properly ground yourself.
4. Turn the controller module so that you can locate the boot device holder.
Use the FRU map on the controller module to help you locate the boot device holder.
5. Open the boot device cover, if applicable.
6. Align the boot device with the boot device socket or connector, and then firmly push the boot device straight down into the
socket or connector.
Important: Always install the boot device by aligning the front of the boot device squarely over the pins in the socket at
the front of the boot device housing. Installing the boot device at an angle or over the rear plastic pin first can bend or
damage the pins in the boot device connector.
7. Check the boot device to make sure that it is seated squarely and completely in the socket or connector.
If necessary, remove the boot device and reseat it into the socket.
8. Close the boot device cover.
Replacing a boot device in a system running clustered Data ONTAP
21
9. Align the end of the controller module with the opening in the chassis, and then gently push the controller module halfway
into the system.
10. Recable the controller module as needed, and then push the controller module all the way into the chassis.
11. Tighten the thumb screw on the cam handle, reinstall the cable management device, and then tighten the hook and loop strap
that binds the cables together.
12. The next step depends on your system configuration:
If your system has...
Then...
One controller module in the chassis
Complete the following substeps:
Two controller modules in the chassis
a.
Reconnect the power cables to the power supplies and to the power sources, and then turn
on the power.
The system begins to boot and stops at the LOADER prompt.
b.
Go to the next step.
The node already began rebooting and stops at the LOADER prompt; go to the next step.
13. Set boot environment variables as needed:
If you are...
Then...
Running Data ONTAP 8.2.1 and later
Set the following boot environment variable at the LOADER prompt on the impaired node
console:
setenv bootarg.init.boot_clustered true
Running Data ONTAP 8.3.x and later
on an AFF system
Set the following boot environment variable on the impaired node:
setenv bootarg.init.flash_optimized true
14. Depending on your network configuration, enter one of the following commands at the LOADER prompt:
If you...
Then...
Have DHCP enabled
Enter the following command:
ifconfig e0M -auto
Do not have DHCP enabled
Enter the following command:
ifconfig e0M -addr=filer_addr -mask=netmask -gw=gateway dns=dns_addr -domain=dns_domain
filer_addr is the IP address of the storage system.
netmask is the network mask of the storage system.
gateway is the gateway for the storage system.
dns_addr is the IP address of a name server on your network.
dns_domain is the Domain Name System (DNS) domain name. If you use this optional
parameter, you do not need a fully qualified domain name in the netboot server URL; you
need only the server’s host name.
Note: To netboot the node when your system is running in 7-Mode Data ONTAP, use an IP
address that is not the management IP address for the target. If your system is running
clustered Data ONTAP, you can use the management IP address.
Note: Other parameters might be necessary for your interface. For details, use the help
ifconfig command at the LOADER prompt.
15. At the LOADER, enter the following command:
22
Replacing a boot device
netboot http://path_to_web-accessible_directory/netboot/kernel
16. Select the Install new software first option from the displayed menu.
This menu option downloads and installs the new Data ONTAP image to the boot device.
•
Select y when prompted with the message that this procedure is not supported for non-disruptive upgrade on an HA pair
active/active configuration .
•
Select y when warned that this process will replace existing Data ONTAP software with new software.
•
Enter the path as follows when prompted for the URL of the image.tgz file:
http://path_to_the_web-accessible_directory/image.tgz
17. Enter y when prompted regarding non-disruptive upgrade or replacement of the software.
18. Enter the path to the image.tgz file when you see the following prompt:
What is the URL for the package?
http://path_to_web-accessible_directory/image.tgz
19. Restore the backup configuration by entering y when you see the following screen:
Example
****************************************************************
*
Restore Backup Configuration
*
* This procedure only applies to storage controllers that
*
* are configured as an HA pair.
*
*
*
* Choose Yes to restore the "varfs" backup configuration
*
* from the SSH server. Refer to the Boot Device Replacement *
* guide for more details.
*
* Choose No to skip the backup recovery and return to the
*
* boot menu.
*
****************************************************************
Do you want to restore the backup configuration
now? {y|n} y
****************************************************************
Perform the restore backup procedure on this node's HA partner *
****************************************************************
20. In advanced mode, restore the backup by completing the following substeps:
a. Set the healthy node to advanced level:
set -privilege advanced
b. Run the restore backup command:
system node restore-backup -node healthy_node_name -target_ip impaired_node_IP_address
c. Return the node to admin level:
set -privilege admin
21. Restore the configuration from the varfs.tgz and reboot the impaired node, as shown in the following example:
Replacing a boot device in a system running clustered Data ONTAP
23
Example
The restore configuration has been copied
from the HA partner to this node,
would you like to use this restored copy
now? {y|n} y
Boot device: /dev/da0 found...
Checking /dev/da0s1 file system... success.
Mounting /dev/da0s1 to /cfcard... success.
Checking /cfcard/x86_64/freebsd mount point... success.
Gzip checking /var/home/root/varfs.tgz... success.
Restoring backup configuration...
Backup Configuration from Thu Jun 19 18:01:53 UTC 2014 successfully restored
The node must be rebooted to start using the newly installed software. Do you
want to reboot now? {y|n} y
22. After the impaired node has rebooted, complete the procedure by entering the following command on the healthy node
console:
storage failover giveback -ofnode partner_node_name
If the giveback is vetoed, you can consider forcing giveback by issuing the following command:
storage failover giveback -ofnode partner_node_name -require-partner-waiting true -overridevetoes true
See the Clustered Data ONTAP High-Availability Configuration Guide on the NetApp Support Site for information on
giveback vetoes.
Installing the boot device and transferring system files disruptively using netboot
You can transfer the system files and restore configuration information to your HA pair disruptively by performing a netboot to
copy the system files to the replacement boot device.
Before you begin
•
You must have the blank replacement boot device that you received from your provider.
•
You must have access to an HTTP server.
•
You must have access to NetApp Support.
This enables you to download the necessary system files for your platform and version of Data ONTAP that is running on it.
About this task
You can use this disruptive procedure in either a stand-alone system or an HA configuration during scheduled maintenance on
the system, or if the controller module is not fully functional.
This procedure is disruptive, even when using it with a system in an HA configuration because an immediate giveback and retakeover occur during the procedure. If possible, you should use the nondisruptive procedure for HA configurations for your
version of Data ONTAP software.
Steps
1. Download and extract the file used for performing the netboot of your system:
a. Download the appropriate netboot.tgz file for your platform from the NetApp Support Site to a web-accessible
directory.
b. Change to the web-accessible directory.
c. Extract the contents of the netboot.tgz file to the target directory by entering the following command:
24
Replacing a boot device
tar -zxvf netboot.tgz
Your directory listing should contain the following directory:
netboot/
2. Download the image.tgz file from the NetApp Support Site to the web-accessible directory.
Your directory listing should contain the following file and directory:
image.tgz netboot/
3. If you are not already grounded, properly ground yourself.
4. Turn the controller module so that you can locate the boot device holder.
Use the FRU map on the controller module to help you locate the boot device holder.
5. Open the boot device cover, if applicable.
6. Align the boot device with the boot device socket or connector, and then firmly push the boot device straight down into the
socket or connector.
Important: Always install the boot device by aligning the front of the boot device squarely over the pins in the socket at
the front of the boot device housing. Installing the boot device at an angle or over the rear plastic pin first can bend or
damage the pins in the boot device connector.
7. Check the boot device to make sure that it is seated squarely and completely in the socket or connector.
If necessary, remove the boot device and reseat it into the socket.
8. Close the boot device cover.
9. Align the end of the controller module with the opening in the chassis, and then gently push the controller module halfway
into the system.
10. Recable the controller module as needed, and then push the controller module all the way into the chassis.
11. Tighten the thumb screw on the cam handle, reinstall the cable management device, and then tighten the hook and loop strap
that binds the cables together.
12. The next step depends on your system configuration:
If your system has...
Then...
One controller module in the chassis
Complete the following substeps:
Two controller modules in the chassis
a.
Reconnect the power cables to the power supplies and to the power sources, and then turn
on the power.
The system begins to boot and stops at the LOADER prompt.
b.
Go to the next step.
The node already began rebooting and stops at the LOADER prompt; go to the next step.
13. Set boot environment variables as needed:
If you are...
Then...
Running Data ONTAP 8.2.x and later
Set the following boot environment variable at the LOADER prompt on the impaired node
console:
setenv bootarg.init.boot_clustered true
Running Data ONTAP 8.3.x and later
on an AFF system
Set the following boot environment variable on the impaired node:
setenv bootarg.init.flash_optimized true
Replacing a boot device in a system running clustered Data ONTAP
25
14. Depending on your network configuration, enter one of the following commands at the LOADER prompt:
If you...
Then...
Have DHCP enabled
Enter the following command:
ifconfig e0M -auto
Do not have DHCP enabled
Enter the following command:
ifconfig e0M -addr=filer_addr -mask=netmask -gw=gateway dns=dns_addr -domain=dns_domain
filer_addr is the IP address of the storage system.
netmask is the network mask of the storage system.
gateway is the gateway for the storage system.
dns_addr is the IP address of a name server on your network.
dns_domain is the Domain Name System (DNS) domain name. If you use this optional
parameter, you do not need a fully qualified domain name in the netboot server URL; you
need only the server’s host name.
Note: To netboot the node when your system is running in 7-Mode Data ONTAP, use an IP
address that is not the management IP address for the target. If your system is running
clustered Data ONTAP, you can use the management IP address.
Note: Other parameters might be necessary for your interface. For details, use the help
ifconfig command at the LOADER prompt.
15. At the LOADER prompt, enter the following command:
netboot http://path_to_the_web-accessible_directory/netboot/kernel
The system begins to boot, but stops at the Boot menu.
16. Select the Install new software first option from the displayed menu.
This menu option downloads and installs the new Data ONTAP image to the boot device.
•
Select y when prompted with the message that this procedure is not supported for non-disruptive upgrade on an HA pair
active/active configuration .
•
Select y when warned that this process will replace existing Data ONTAP software with new software.
•
Enter the path as follows when prompted for the URL of the image.tgz file:
http://path_to_the_web-accessible_directory/image.tgz
17. Complete the following substeps:
a. Enter n to skip the backup recovery when you see the following prompt:
**************************************************************
*
Restore Backup Configuration
*
* This procedure only applies to storage controllers that
*
* are configured as an HA pair.
*
*
*
* Choose Yes to restore the 'varfs' backup configuration
*
* from a TFTP server. Refer to the Boot Device Replacement *
* guide for more details.
*
* Choose No to skip the back up recovery and return to the *
* boot menu.
*
26
Replacing a boot device
**************************************************************
Do you want to restore the backup configuration
now? {y|n} n
b. Reboot the node by entering y when you see the following prompt:
The node must be rebooted to start using the newly installed
software. Do you want to reboot now? {y/n} y
After reboot, if prompted to update firmware and BIOS, enter y to accept.
The controller module displays the Boot menu because the boot device was reformatted and the configuration data needs
to be restored.
18. Select the Update flash from backup config option from the displayed menu.
If you are asked to continue with the update, enter y when prompted.
19. Your next step depends on your system configuration.
If your system is...
Description
A stand-alone configuration
You can begin using your system after the node reboots to complete restoring the backup
configuration.
HA pair
Complete the following substeps after the impaired node is displaying the Waiting for
Giveback... message:
a.
Enter the following command from the healthy node:
storage failover giveback -ofnode partner_node_name
The impaired node takes back its storage, completes booting up, and then reboots and is
again taken over by the healthy node.
Note: If the giveback is vetoed, you can consider overriding the vetoes.
Find the High-Availability Configuration Guide for your version of Data ONTAP 8
If the impaired node displays Waiting for Giveback..., give back the impaired
node from the healthy node:
storage failover giveback -ofnode replacement_node_name
b.
Enter the storage failover show-giveback command to monitor the progress
of the giveback operation.
c.
After the giveback operation is complete, enter the storage failover show
command to confirm that the HA pair is healthy and takeover is possible.
Completing the replacement process
After you replace the part, you can return the failed part to NetApp, as described in the RMA instructions shipped with the kit.
Contact technical support at NetApp Support, 888-463-8277 (North America), 00-800-44-638277 (Europe), or
+800-800-80-800 (Asia/Pacific) if you need the RMA number or additional help with the replacement procedure.
Copyright information
Copyright © 1994–2015 NetApp, Inc. All rights reserved. Printed in the U.S.
Completing the replacement process
27
No part of this document covered by copyright may be reproduced in any form or by any means—graphic, electronic, or
mechanical, including photocopying, recording, taping, or storage in an electronic retrieval system—without prior written
permission of the copyright owner.
Software derived from copyrighted NetApp material is subject to the following license and disclaimer:
THIS SOFTWARE IS PROVIDED BY NETAPP "AS IS" AND WITHOUT ANY EXPRESS OR IMPLIED WARRANTIES,
INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A
PARTICULAR PURPOSE, WHICH ARE HEREBY DISCLAIMED. IN NO EVENT SHALL NETAPP BE LIABLE FOR
ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING,
BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR
PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER
IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
NetApp reserves the right to change any products described herein at any time, and without notice. NetApp assumes no
responsibility or liability arising from the use of products described herein, except as expressly agreed to in writing by NetApp.
The use or purchase of this product does not convey a license under any patent rights, trademark rights, or any other intellectual
property rights of NetApp.
The product described in this manual may be protected by one or more U.S. patents, foreign patents, or pending applications.
RESTRICTED RIGHTS LEGEND: Use, duplication, or disclosure by the government is subject to restrictions as set forth in
subparagraph (c)(1)(ii) of the Rights in Technical Data and Computer Software clause at DFARS 252.277-7103 (October 1988)
and FAR 52-227-19 (June 1987).
Trademark information
NetApp, the NetApp logo, Go Further, Faster, AltaVault, ASUP, AutoSupport, Campaign Express, Cloud ONTAP, Clustered
Data ONTAP, Customer Fitness, Data ONTAP, DataMotion, Fitness, Flash Accel, Flash Cache, Flash Pool, FlashRay,
FlexArray, FlexCache, FlexClone, FlexPod, FlexScale, FlexShare, FlexVol, FPolicy, GetSuccessful, LockVault, Manage
ONTAP, Mars, MetroCluster, MultiStore, NetApp Insight, OnCommand, ONTAP, ONTAPI, RAID DP, RAID-TEC, SANtricity,
SecureShare, Simplicity, Simulate ONTAP, Snap Creator, SnapCenter, SnapCopy, SnapDrive, SnapIntegrator, SnapLock,
SnapManager, SnapMirror, SnapMover, SnapProtect, SnapRestore, Snapshot, SnapValidator, SnapVault, StorageGRID, Tech
OnTap, Unbound Cloud, and WAFL and other names are trademarks or registered trademarks of NetApp, Inc., in the United
States, and/or other countries. All other brands or products are trademarks or registered trademarks of their respective holders
and should be treated as such. A current list of NetApp trademarks is available on the web at http://www.netapp.com/us/legal/
netapptmlist.aspx.
How to send comments about documentation and receive
update notifications
You can help us to improve the quality of our documentation by sending us your feedback. You can receive automatic
notification when production-level (GA/FCS) documentation is initially released or important changes are made to existing
production-level documents.
If you have suggestions for improving this document, send us your comments by email to doccomments@netapp.com. To help
us direct your comments to the correct division, include in the subject line the product name, version, and operating system.
If you want to be notified automatically when production-level documentation is released or important changes are made to
existing production-level documents, follow Twitter account @NetAppDoc.
You can also contact us in the following ways:
•
28
NetApp, Inc., 495 East Java Drive, Sunnyvale, CA 94089 U.S.
Replacing a boot device
•
Telephone: +1 (408) 822-6000
•
Fax: +1 (408) 822-4501
•
Support telephone: +1 (888) 463-8277
How to send comments about documentation and receive update notifications
29
Was this manual useful for you? yes no
Thank you for your participation!

* Your assessment is very important for improving the work of artificial intelligence, which forms the content of this project

Download PDF

advertising