NetApp ASA C400 Hoja de instrucciones
Controller
Install and maintain
NetApp
October 20, 2023
This PDF was generated from https://docs.netapp.com/us-en/ontap-systems/asa-c400/controller-replace-
overview.html on October 20, 2023. Always check docs.netapp.com for the latest.
Table of Contents
Controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê1
Overview of controller module replacement - ASA C400 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê1
Shut down the impaired controller - ASA C400 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê1
Replace the controller module hardware - ASA C400 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê5
Restore and verify the system configuration - ASA C400 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê14
Recable the system and reassign disks - ASA C400 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê15
Complete system restoration - ASA C400 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê18
Controller
Overview of controller module replacement - ASA C400
You must review the prerequisites for the replacement procedure and select the correct
one for your version of the ONTAP operating system.
•All drive shelves must be working properly.
•If your system is in a MetroCluster configuration, you must review the section Choosing the correct
recovery procedure to determine whether you should use this procedure.
If this is the procedure you should use, note that the controller replacement procedure for a controller in a
four or eight node MetroCluster configuration is the same as that in an HA pair. No MetroCluster-specific
steps are required because the failure is restricted to an HA pair and storage failover commands can be
used to provide nondisruptive operation during the replacement.
•You must replace the failed component with a replacement FRU component you received from your
provider.
•You must be replacing a controller module with a controller module of the same model type. You cannot
upgrade your system by just replacing the controller module.
•You cannot change any drives or drive shelves as part of this procedure.
•In this procedure, the boot device is moved from the impaired controller to the replacement controller so
that the replacement controller will boot up in the same version of ONTAP as the old controller module.
•It is important that you apply the commands in these steps on the correct systems:
◦The impaired controller is the controller that is being replaced.
◦The replacement node is the new controller that is replacing the impaired controller.
◦The healthy controller is the surviving controller.
•You must always capture the controller’s console output to a text file.
This provides you a record of the procedure so that you can troubleshoot any issues that you might
encounter during the replacement process.
Shut down the impaired controller - ASA C400
Shut down or take over the impaired controller using the appropriate procedure for your
configuration.
1
Option 1: Most systems
To shut down the impaired controller, you must determine the status of the controller and, if necessary,
take over the controller so that the healthy controller continues to serve data from the impaired controller
storage.
About this task
•If you are using NetApp Storage Encryption, you must have reset the MSID using the instructions in
the Returning SEDs to unprotected mode.
•If you have a SAN system, you must have checked event messages (cluster kernel-service
show) for impaired controller SCSI blade. The cluster kernel-service show command
displays the node name, quorum status of that node, availability status of that node, and operational
status of that node.
Each SCSI-blade process should be in quorum with the other nodes in the cluster. Any issues must
be resolved before you proceed with the replacement.
•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. 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
2. Disable automatic giveback from the console of the healthy controller: storage failover modify
–node local -auto-giveback false
When you see Do you want to disable auto-giveback?, enter y.
3. Take the impaired controller to the LOADER prompt:
If the impaired controller is
displaying…
Then…
The LOADER prompt Go to Remove controller module.
Waiting for giveback… Press Ctrl-C, and then respond ywhen prompted.
System prompt or password
prompt
Take over or halt the impaired controller from the healthy
controller: storage failover takeover -ofnode
impaired_node_name
When the impaired controller shows Waiting for giveback…, press
Ctrl-C, and then respond y.
2
Option 2: Controller is in a two-node MetroCluster
To shut down the impaired controller, you must determine the status of the controller and, if necessary,
switch over the controller so that the healthy controller continues to serve data from the impaired
controller storage.
About this task
•If you are using NetApp Storage Encryption, you must have reset the MSID using the instructions in
the "Return a FIPS drive or SED to unprotected mode" section of NetApp Encryption overview with
the CLI.
•You must leave the power supplies turned on at the end of this procedure to provide power to the
healthy controller.
Steps
1. Check the MetroCluster status to determine whether the impaired controller has automatically
switched over to the healthy controller: metrocluster show
2. Depending on whether an automatic switchover has occurred, proceed according to the following
table:
If the impaired controller… Then…
Has automatically switched over Proceed to the next step.
Has not automatically switched
over
Perform a planned switchover operation from the healthy
controller: metrocluster switchover
Has not automatically switched
over, you attempted switchover
with the metrocluster
switchover command, and
the switchover was vetoed
Review the veto messages and, if possible, resolve the issue and
try again. If you are unable to resolve the issue, contact technical
support.
3. Resynchronize the data aggregates by running the metrocluster heal -phase aggregates
command from the surviving cluster.
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 using the metrocluster operation show command.
3
controller_A_1::> metrocluster operation show
Ê Operation: heal-aggregates
Ê State: successful
Start Time: 7/25/2016 18:45:55
Ê End Time: 7/25/2016 18:45:56
Ê Errors: -
5. Check the state of the aggregates by using the storage aggregate show command.
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...
6. Heal the root aggregates by using the metrocluster heal -phase root-aggregates
command.
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. Verify that the heal operation is complete by using the metrocluster operation show command
on the destination cluster:
mcc1A::> metrocluster operation show
Ê Operation: heal-root-aggregates
Ê State: successful
ÊStart Time: 7/29/2016 20:54:41
Ê End Time: 7/29/2016 20:54:42
Ê Errors: -
8. On the impaired controller module, disconnect the power supplies.
4
Replace the controller module hardware - ASA C400
To replace the controller module hardware, you must remove the impaired controller,
move FRU components to the replacement controller module, install the replacement
controller module in the chassis, and then boot the system to Maintenance mode.
Step 1: Remove the controller module
To access components inside the controller module, you must remove the controller module from the chassis.
You can use the following , illustration, or the written steps to remove the controller module from the chassis.
Animation - Remove the controller module
1. If you are not already grounded, properly ground yourself.
2. Release the power cable retainers, and then unplug the cables from the power supplies.
3. 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, keeping 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.
4. Remove the cable management device from the controller module and set it aside.
5. Press down on both of the locking latches, and then rotate both latches downward at the same time.
The controller module moves slightly out of the chassis.
5
Locking latches
Controller moves slightly out of chassis
6. Slide the controller module out of the chassis.
Make sure that you support the bottom of the controller module as you slide it out of the chassis.
7. Place the controller module on a stable, flat surface.
8. On the replacement controller module, open the air duct and remove the empty risers from the controller
module using the animation, illustration, or the written steps:
Animation - Remove the empty risers from the replacement controller module
Riser release latches
a. Press the locking tabs on the sides of the air duct in toward the middle of the controller module.
b. Slide the air duct toward the back of the controller module, and then rotate it upward to its completely open
position.
c. Rotate the riser locking latch on the left side of riser 1 up and toward air duct, lift the riser up, and then set it
aside.
d. Repeat the previous step for the remaining risers.
Step 2: Move the power supplies
You must move the power supply from the impaired controller module to the replacement controller module
when you replace a controller module.
You can use the following animation, illustration, or the written steps to move the power supplies to the
replacement controller module.
Animation - Move the power supplies
6
1. Remove the power supply:
PSU locking tab
Power cable retainer
a. Rotate the cam handle so that it can be used to pull the power supply out of the chassis.
b. Press the blue locking tab to release the power supply from the chassis.
c. Using both hands, pull the power supply out of the chassis, and then set it aside.
1. Move the power supply to the new controller module, and then install it.
2. Using both hands, support and align the edges of the power supply with the opening in the controller
module, and then gently push the power supply into the controller module until the locking tab clicks
into place.
The power supplies will only properly engage with the internal connector and lock in place one way.
To avoid damaging the internal connector, do not use excessive force when sliding the
power supply into the system.
3. Repeat the preceding steps for any remaining power supplies.
Step 3: Move the NVDIMM battery
To move the NVDIMM battery from the impaired controller module to the replacement controller module, you
7
must perform a specific sequence of steps.
You can use the following animation, illustration, or the written steps to move the NVDIMM battery from the
impaired controller module to the replacement controller module.
Animation - Move the NVDIMM battery
NVDIMM battery plug
NVDIMM battery locking tab
NVDIMM battery
1. Open the air duct:
a. Press the locking tabs on the sides of the air duct in toward the middle of the controller module.
b. Slide the air duct toward the back of the controller module, and then rotate it upward to its completely
open position.
2. Locate the NVDIMM battery in the controller module.
3. Locate the battery plug and squeeze the clip on the face of the battery plug to release the plug from the
socket, and then unplug the battery cable from the socket.
4. Grasp the battery and press the blue locking tab marked PUSH, and then lift the battery out of the holder
and controller module.
5. Move the battery to the replacement controller module.
6. Align the battery module with the opening for the battery, and then gently push the battery into slot until it
locks into place.
Do not plug the battery cable back into the motherboard until instructed to do so.
8
Este manual sirve para los siguientes modelos
10
Tabla de contenidos
Otros manuales de Controladores de NetApp
