8. Enter the
sd-list
command to verify the system drive statuses are OK and that
access is allowed.
9. Use the CLI to verify that the new node has access to the system drives. Use
sd-
list
from the node that you have just replaced.
For example:
pn x sd-list
where x is the node number in the cluster.
FSS-HNAS-1:$ sd-list
Device Status Alw GiByte Mirror In span Span Cap
----- ------ --- ------ ------ ------- --------
0 OK Yes 1607 Pri FSS_Pool_1 3214
1 OK Yes 1607 Pri FSS_Pool_1 3214
4 OK Yes 390 Pri FSS_AMS200 1560
5 OK Yes 390 Pri FSS_AMS200 1560
6 OK Yes 390 Pri FSS_AMS200 1560
7 OK Yes 390 Pri FSS_AMS200 1560
10. Enter
span-list
to verify the storage pools (spans) are accessible.
Note: In this instance, cluster is synonymous with the stand-alone
server.
11. Enter the
span-list-cluster-uuids
span_label
command to display the
cluster serial number (UUID) to which the storage pool belongs.
The UUID is written into the storage pool 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 the
span-assign-to-cluster
span_label
command to assign all the
spans to the new server.
13. If EVS mapping or balancing is required, select the EVS to migrate, assign it to the
preferred node, then click migrate.
Finalizing and verifying the replacement server configuration
Chapter 7: Server replacement procedures
Hitachi NAS Platform Series 5000 Hardware Reference
57
