Table of Contents
Advertisement
11. Enter span-list-cluster-uuids span_label to display the cluster serial
number (UUID) to which the storage pool belongs.
The UUID is written into the storage pool's configuration on disk (COD). The COD is a
data structure stored in every SD, which provides information how the different SDs
are combined into different stripesets and storage pools.
12. Enter span-assign-to-cluster span_label to assign all the spans to the new
server.
13. Verify the IP routes, and enable all the EVSs for file services in case they are
disabled.
14. Reconfigure any required tape backup application security.
15. Navigate to Home > Status & Monitoring > Event Logs, and click Clear Event
Logs.
16. Navigate to Home > Status & Monitoring > System Monitor and verify the server
status:
If the server is operating normally, and is not displaying any alarm conditions,
■
run a backup to capture the revised configuration, and then download another
diagnostic to support. Permanent license keys for the replacement server are
normally provided within 7 days.
If the server is not operating normally for any reason, contact support for
■
assistance.
17. Confirm all final settings, IP addresses, customer contact information, service
restarts, client access, and that customer expectations are all in place. Features such
as replication and data migration should all be confirmed as working, and all file
systems and storage pools should be online.
Replacing a node within a cluster
Replacing a single node within a cluster assumes only two-node clusters and the
presence of an external SMU, which acts as a quorum device. This helps to simplify the
replacement process because a cluster preserves operational state of the entire system
beyond any single node failure.
Because you are replacing an existing node from a cluster, you do not require any
additional licenses, since the cluster will retain the licenses used from the existing node
and the Cluster MAC-ID does not change, even if you are replacing node 1.
Capturing information from the existing node
To start, capture and record information from the existing node.
Procedure
1. Use the table below to record the information of the node to be replaced. This table
will help you later during the node replacement process, by providing all the needed
information.
Hitachi NAS Platform 3080 and 3090 G2 Hardware Reference
Appendix A: Server replacement procedures
Replacing a node within a cluster
95
Advertisement
Table of Contents
