Table of Contents
Advertisement
Appendix A: Server replacement procedures
The replacement of the server as part of a field service process can take several forms
depending on how the system was originally deployed. The typical field deployment
scenarios documented for service replacement include:
Single stand-alone server using an embedded SMU for management
■
Single stand-alone server using an external SMU for management
■
Two-node cluster using an external SMU for management-replacing only one node
■
Two-node cluster using an external SMU for management-replacing both nodes
■
Important: This document does not treat migration scenarios between
different configurations at the time of replacement.
Replacement procedure overview
This section highlights the requirements and considerations when replacing nodes.
Requirements
Any personnel attempting the following procedures must have completed the necessary
training before proceeding. Much of the process required for a server replacement is the same
process covered in installation and configuration training. No personnel should attempt to
replace a unit without adequate training and authorization.
Determine which replacement scenario is being encountered in advance. The
replacement process is different for each scenario.
Acquire the temporary license keys before arriving onsite to expedite the server
replacement. The license keys are necessary because they are based on the unique MAC
ID for the server or cluster. New license keys are not required when replacing one server
in a cluster.
Note: Replacement servers are shipped without an embedded system
management unit (SMU), so you must have a SMU installed before you can
connect to a standalone server.
Hitachi NAS Platform 3080 and 3090 G2 Hardware Reference
Appendix A: Server replacement procedures
76
Advertisement
Table of Contents
