Fujitsu ETERNUS HX2000 Series Operating and safety instructions
A3CA08733-A309-01
Fujitsu Storage ETERNUS HX2000 and AX2100
systems
Replacing the chassis
|Contents|
Contents
Workflow diagram.......................................................................................... 3
Replacing the chassis..................................................................................... 4
Shutting down the controllers when replacing a chassis....................................................................... 4
Shutting down the node.............................................................................................................4
Shutting down a node in a two-node MetroCluster configuration...............................................5
Swapping out a power supply................................................................................................................6
Removing the controller module............................................................................................................6
Moving drives to the new chassis.......................................................................................................... 7
Replacing a chassis from within the equipment rack or system cabinet.................................................8
Installing the controller........................................................................................................................ 8
Verifying and setting the HA state of the chassis.................................................................................. 9
Running system-level diagnostics........................................................................................................ 10
Switching back aggregates in a two-node MetroCluster configuration................................................. 12
Completing the replacement process................................................................................................... 13
Copyright............................................................................................................................14
Trademark.......................................................................................................................... 15
How to send comments about documentation and receive update notifications...........16
ii
Workflow diagram
This diagram shows the workflow of the chassis replacement procedure.
3
|Replacing the chassis|
Replacing the chassis
To replace the chassis, you must move the power supplies, hard drives, and controller module or modules
from the impaired chassis to the new chassis, and swap out the impaired chassis from the equipment rack or
system cabinet with the new chassis of the same model as the impaired chassis.
Before you begin
All other components in the system must be functioning properly; if not, you must contact technical support.
About this task
• You can use this procedure with all versions of ETERNUS AX/HX Series supported by your system.
• This procedure is written with the assumption that you are moving all drives and controller module or
modules to the new chassis, and that the chassis is a new component from Fujitsu.
• This procedure is disruptive. For a two-node cluster, you will have a complete service outage and a partial
outage in a multi-node cluster.
Shutting down the controllers when replacing a chassis
You must shut down the controllers before replacing the chassis.
Shutting down the node
You must shut down the node or nodes in the chassis prior to moving them to the new chassis.
Before you begin
• 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.
Procedure
1. If your system has two controller modules, disable the HA pair.
If your system is running clustered ETERNUS AX/
HX Series with...
Then...
Two nodes in the cluster cluster ha modify -configured false
storage failover modify -node node0
-enabled false
More than two nodes in the cluster storage failover modify -node node0
-enabled false
2. Halt the node, pressing y when you are prompted to confirm the halt: system node halt -node
node_name
The confirmation message looks like the following:
Warning: Rebooting or halting node
"node_name" in an HA-enabled cluster may result in client disruption or
data access
failure. To ensure continuity of service, use the "storage
failover takeover" command. Are you sure you want to halt node
"node_name"? {y|n}:
Attention: You must perform a clean system shutdown before replacing the chassis to avoid
losing unwritten data in the nonvolatile memory (NVMEM). If the NVMEM LED is flashing, there is
content in the NVMEM that has not been saved to disk. You need to reboot the node and start from
4
|Replacing the chassis|
the beginning of this procedure. If repeated attempts to cleanly shut down the node fail, be aware
that you might lose any data that was not saved to disk.
3. Where applicable, halt the second node to avoid a possible quorum error message in an HA pair
configuration:: system node halt -node second_node_name -ignore-quorum-warnings
true
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 storage.
About this task
You must leave the power supplies turned on at the end of this procedure to provide power to the healthy
node.
Procedure
1. Check the MetroCluster status to determine whether 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, 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.
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.
5
|Replacing the chassis|
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.
Swapping out a power supply
Swapping out a power supply when replacing a chassis involves turning off, disconnecting, and removing the
power supply from the old chassis and installing and connecting it on the replacement chassis.
Procedure
1. If you are not already grounded, properly ground yourself.
2. Turn off the power supply and disconnect the power cables:
a) Turn off the power switch on the power supply.
b) Open the power cable retainer, and then unplug the power cable from the power supply.
c) Unplug the power cable from the power source.
3. Squeeze the latch on the power supply cam handle, and then open the cam handle to fully release the
power supply from the mid plane.
4. Use the cam handle to slide the power supply out of the system.
CAUTION: When removing a power supply, always use two hands to support its weight.
5. Repeat the preceding steps for any remaining power supplies.
6. Using both hands, support and align the edges of the power supply with the opening in the system
chassis, and then gently push the power supply into the chassis using the cam handle.
The power supplies are keyed and can only be installed one way.
Attention: Do not use excessive force when sliding the power supply into the system. You can
damage the connector.
7. Close the cam handle so that the latch clicks into the locked position and the power supply is fully seated.
8. Reconnect the power cable and secure it to the power supply using the power cable locking mechanism.
Attention: Only connect the power cable to the power supply. Do not connect the power cable to a
power source at this time.
Removing the controller module
To replace the chassis, you must remove the controller module or modules from the old chassis.
6
|Replacing the chassis|
Procedure
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, 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.
3. Remove and set aside the cable management devices from the left and right sides of the controller
module.
4. Squeeze the latch on the cam handle until it releases, open the cam handle fully to release the controller
module from the midplane, and then, using two hands, pull the controller module out of the chassis.
5. Set the controller module aside in a safe place, and repeat these steps if you have another controller
module in the chassis.
Moving drives to the new chassis
You need to move the drives from each bay opening in the old chassis to the same bay opening in the new
chassis.
Procedure
1. Gently remove the bezel from the front of the system.
2. Remove the drives:
a) Press the release button at the top of the carrier face below the LEDs.
b) Pull the cam handle to its fully open position to unseat the drive from the midplane, and then gently
slide the drive out of the chassis.
The drive should disengage from the chassis, allowing it to slide free of the chassis.
7
|Replacing the chassis|
Attention: When removing a drive, always use two hands to support its weight.
Attention: Drives are fragile. Handle them as little as possible to prevent damage to them.
3. Align the drive from the old chassis with the same bay opening in the new chassis.
4. Gently push the drive into the chassis as far as it will go.
The cam handle engages and begins to rotate upward.
5. Firmly push the drive the rest of the way into the chassis, and then lock the cam handle by pushing it up
and against the drive holder.
Be sure to close the cam handle slowly so that it aligns correctly with the front of the drive carrier. It click
when it is secure.
6. Repeat the process for the remaining drives in the system.
Replacing a chassis from within the equipment rack or system cabinet
You must remove the existing chassis from the equipment rack or system cabinet before you can install the
replacement chassis.
Procedure
1. Remove the screws from the chassis mount points.
2. With the help of two or three people, slide the old chassis off the rack rails in a system cabinet or L
brackets in an equipment rack, and then set it aside.
3. If you are not already grounded, properly ground yourself.
4. Using two or three people, install the replacement chassis into the equipment rack or system cabinet by
guiding the chassis onto the rack rails in a system cabinet or L brackets in an equipment rack.
5. Slide the chassis all the way into the equipment rack or system cabinet.
6. Secure the front of the chassis to the equipment rack or system cabinet, using the screws you removed
from the old chassis.
Installing the controller
After you install the controller module and any other components into the new chassis, boot it to a state
where you can run the interconnect diagnostic test.
About this task
For HA pairs with two controller modules in the same chassis, the sequence in which you install the controller
module is especially important because it attempts to reboot as soon as you completely seat it in the chassis.
Procedure
1. If you are not already grounded, properly ground yourself.
2. Align the end of the controller module with the opening in the chassis, and then gently push the controller
module halfway into the system.
Note: Do not completely insert the controller module in the chassis until instructed to do so.
3. Recable the console to the controller module, and then reconnect the management port.
4. Repeat the preceding steps if there is a second controller to install in the new chassis.
5. Complete the installation of the controller module:
8
|Replacing the chassis|
If your system is in... Then perform these steps...
An HA pair a. With the cam handle in the open position,
firmly push the controller module in until
it meets the midplane and is fully seated,
and then close the cam handle to the locked
position.
Attention: Do not use excessive force
when sliding the controller module
into the chassis to avoid damaging the
connectors.
b. If you have not already done so, reinstall the
cable management device.
c. Bind the cables to the cable management
device with the hook and loop strap.
d. Repeat the preceding steps for the second
controller module in the new chassis.
A stand-alone configuration a. With the cam handle in the open position,
firmly push the controller module in until
it meets the midplane and is fully seated,
and then close the cam handle to the locked
position.
Attention: Do not use excessive force
when sliding the controller module
into the chassis to avoid damaging the
connectors.
b. If you have not already done so, reinstall the
cable management device.
c. Bind the cables to the cable management
device with the hook and loop strap.
d. Reinstall the blanking panel and then go to the
next step.
6. Connect the power supplies to different power sources, and then turn them on.
7. Boot each node to Maintenance mode:
a) As each node starts the booting, press Ctrl-C to interrupt the boot process when you see the
message Press Ctrl-C for Boot Menu.
Note: If you miss the prompt and the controller modules boot to ETERNUS AX/HX Series, enter halt,
and then at the LOADER prompt enter boot_ETERNUS AX/HX Series, press Ctrl-C when
prompted, and then repeat this step.
b) From the boot menu, select the option for Maintenance mode.
Verifying and setting the HA state of the chassis
You must verify the HA state of the chassis, and, if necessary, update the state to match your system
configuration.
Procedure
1. In Maintenance mode, from either controller module, display the HA state of the local controller module
and chassis: ha-config show
The HA state should be the same for all components.
2. If the displayed system state for the chassis does not match your system configuration:
a) Set the HA state for the chassis: ha-config modify chassis HA-state
9
|Replacing the chassis|
The value for HA-state can be one of the following:
•ha
•mcc
•mcc-2n
•non-ha
b) Confirm that the setting has changed: ha-config show
3. If you have not already done so, recable the rest of your system.
4. The next step depends on your system configuration.
If your system is in... Then...
A stand-alone configuration a. Exit Maintenance mode: halt
b. Go to "Completing the replacement process.
An HA pair with a second controller module Exit Maintenance mode: halt
The LOADER prompt appears.
Running system-level diagnostics
After installing a new chassis, you should run interconnect diagnostics.
Before you begin
Your system must be at the LOADER prompt to start System Level Diagnostics.
About this task
All commands in the diagnostic procedures are issued from the node where the component is being replaced.
Procedure
1. If the node to be serviced is not at the LOADER prompt, perform the following steps:
a) Select the Maintenance mode option from the displayed menu.
b) After the node boots to Maintenance mode, halt the node: halt
After you issue the command, you should wait until the system stops at the LOADER prompt.
Important: During the boot process, you can safely respond y to prompts:
2. Repeat the previous step on the second node if you are in an HA configuration.
Note: Both controllers must be in Maintenance mode to run the interconnect test.
3. At the LOADER prompt, access the special drivers specifically designed for system-level diagnostics to
function properly: boot_diags
During the boot process, you can safely respond y to the prompts until the Maintenance mode prompt
(*>) appears.
4. Enable the interconnect diagnostics tests from the Maintenance mode prompt: sldiag device
modify -dev interconnect -sel enable
The interconnect tests are disabled by default and must be enabled to run separately.
5. Run the interconnect diagnostics test from the Maintenance mode prompt: sldiag device run -
dev interconnect
You only need to run the interconnect test from one controller.
6. Verify that no hardware problems resulted from the replacement of the chassis: sldiag device
status -dev interconnect -long -state failed
10
|Replacing the chassis|
System-level diagnostics returns you to the prompt if there are no test failures, or lists the full status of
failures resulting from testing the component.
7. Proceed based on the result of the preceding step.
If the system-level diagnostics tests... Then...
Were completed without any failures a. Clear the status logs: sldiag device
clearstatus
b. Verify that the log was cleared: sldiag
device status
The following default response is displayed:
SLDIAG: No log messages are
present.
c. Exit Maintenance mode on both controllers:
halt
The system displays the LOADER prompt.
Attention: You must exit Maintenance
mode on both controllers before
proceeding any further.
d. Enter the following command on both
controllers at the LOADER prompt: bye
e. Return the node to normal operation:
If your system is
running ETERNUS
AX/HX Series...
Then...
With two nodes in the
cluster
Issue these
commands:
node::> cluster
ha modify -
configured true
node::> storage
failover modify
-node node0 -
enabled true
With more than two
nodes in the cluster
Issue this command:
node::> storage
failover modify
-node node0 -
enabled true
In a two-node
MetroCluster
configuration
Proceed to the next
step.
The MetroCluster
switchback procedure
is done in the
next task in the
replacement process.
In a stand-alone
configuration
You have no further
steps in this particular
task.
You have completed system-level diagnostics.
Resulted in some test failures Determine the cause of the problem.
11
|Replacing the chassis|
If the system-level diagnostics tests... Then...
a. Exit Maintenance mode: halt
b. Perform a clean shutdown, and then disconnect
the power supplies.
c. Verify that you have observed all of the
considerations identified for running system-
level diagnostics, that cables are securely
connected, and that hardware components are
properly installed in the storage system.
d. Reconnect the power supplies, and then power
on the storage system.
e. Rerun the system-level diagnostics test.
Switching back aggregates in a two-node MetroCluster configuration
After you have completed the FRU replacement in a two-node MetroCluster configuration, you can perform
the MetroCluster operation. This returns the configuration to its normal operating state, with the sync-source
storage virtual machines (SVMs) on the formerly impaired site now active and serving data from the local disk
pools.
About this task
This task only applies to two-node MetroCluster configurations.
Procedure
1. Verify that all nodes are in the enabled state: metrocluster node show
cluster_B::> metrocluster node show
DR Configuration DR
Group Cluster Node State Mirroring Mode
----- ------- -------------- -------------- --------- --------------------
1 cluster_A
controller_A_1 configured enabled heal roots completed
cluster_B
controller_B_1 configured enabled waiting for switchback recovery
2 entries were displayed.
2. Verify that resynchronization is complete on all SVMs: metrocluster vserver show
3. Verify that any automatic LIF migrations being performed by the healing operations were completed
successfully: metrocluster check lif show
4. Perform the switchback by using the metrocluster switchback command from any node in the
surviving cluster.
5. Verify that the switchback operation has completed: metrocluster show
The switchback operation is still running when a cluster is in the waiting-for-switchback state:
cluster_B::> metrocluster show
Cluster Configuration State Mode
-------------------- ------------------- ---------
Local: cluster_B configured switchover
Remote: cluster_A configured waiting-for-switchback
The switchback operation is complete when the clusters are in the normal state.:
cluster_B::> metrocluster show
Cluster Configuration State Mode
-------------------- ------------------- ---------
Local: cluster_B configured normal
Remote: cluster_A configured normal
If a switchback is taking a long time to finish, you can check on the status of in-progress baselines by using
the metrocluster config-replication resync-status show command.
6. Reestablish any SnapMirror or SnapVault configurations.
12
|Replacing the chassis|
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 , 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.
13
|Copyright|
Copyright
Copyright 2020 FUJITSU LIMITED. All rights reserved.
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 Fujitsu material is subject to the following license and disclaimer:
THIS SOFTWARE IS PROVIDED BY FUJITSU "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 FUJITSU 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.
Fujitsu reserves the right to change any products described herein at any time, and without notice. Fujitsu
assumes no responsibility or liability arising from the use of products described herein, except as expressly
agreed to in writing by Fujitsu. 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 Fujitsu.
14
|How to send comments about documentation and receive update notifications|
How to send comments about documentation and receive
update notifications
The latest version of this document and the latest information related to this device are available at the
following site.
https://www.fujitsu.com/global/support/products/computing/storage/manuals-list.html
If necessary, refer to the manuals for your model.
16
Fujitsu Storage ETERNUS HX2000 and AX2100 systems
Replacing the chassis
A3CA08733-A309-01
Date of issuance: April 2020
Issuance responsibility: FUJITSU LIMITED
• The content of this manual is subject to change without notice.
• This manual was prepared with the utmost attention to detail.
However, Fujitsu shall assume no responsibility for any operational problems as the result of errors, omissions, or the
use of information in this manual.
• Fujitsu assumes no liability for damages to third party copyrights or other rights arising from the use of any information
in this manual.
• The content of this manual may not be reproduced or distributed in part or in its entirety without prior permission from
Fujitsu.
This manual suits for next models
1
Table of contents
Other Fujitsu Chassis manuals
