Skip to main content
Hitachi Vantara Knowledge

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:

  • 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 provides information on the requirements and considerations for replacing nodes.

Server replacement requirements

Consider the following server replacement requirements:

  • Much of the process required for a server replacement is the same as what is covered in installation and configuration training.
  • Determine which replacement scenario is being encountered. The replacement process is different for each scenario.

NoteReplacement servers are shipped without an embedded system management unit (SMU), so you must install the SMU before you can connect to a stand-alone server.

You can use a keyboard, video, and mouse (KVM) device or a serial cable to connect to the serial port. Bring these with you just in case they are needed when the unit arrives. If you connect to the serial port, use the following SSH client settings:

  • 115,200 b/s
  • 8 data bits
  • 1 stop bit
  • No parity
  • No flow control
  • VT100 emulation

Swapping components

The server can be replaced onsite, however, some components are not included in your replacement server. You must remove those components from the original server and use them in the replacement server. There are a minimum of three parts to be reused in the replacement server.

The components that can be swapped include:

  • Power supplies
  • Bezel
  • Rack mounting guides

Model selection

The software for all server models is pre-loaded on the replacement server before it is shipped from either the factory or depot location.

If for any reason the model selection does not match that which is required for replacement, then an upgrade process may be required in the field.

The upgrade process is outside the scope of this document and documented separately. Contact Hitachi Vantara Support Connect for upgrade information.

MAC ID and license keys

The replacement server has a new MAC ID, which means that you are required to have new license keys regardless of whether you are replacing a single node or a complete cluster.

As part of the field replacement process, Hitachi Vantara recommends that you obtain temporary keys to enable quick delivery and implementation. However, any temporary keys must eventually be replaced with a permanent key. This is required for all field scenarios, except when replacing a single node in a cluster.

NoteIf the scenario is a single node or an all-cluster node replacement, use the span-allow-access command to attach the storage when the MAC ID changes.

Previous backups

A system backup preserves two critical components of information:

  • SMU configuration
  • Server configuration

The backup form for an embedded SMU is different than one from an external SMU. Depending on the replacement scenario severity, different limitations might exist for the system recovery.

ImportantIt is assumed that customers are frequently establishing backups somewhere safely off the platform for recovery purposes. If there is no backup, and the system to be replaced is nonfunctional, a manual recovery process is required to re-establish a functional system. The duration of this manual recovery is directly related to the complexity of the original configuration. All data and file systems are preserved independent of a backup.

Upgrades

Replacement servers can be down or above a revision, and not at the expected level of firmware required at the customer site. An upgrade is typically required during the replacement process, which is not covered in this document. It is assumed that all services personnel performing a replacement have already been trained, and know where to get this information within their respective organization.

Manually installing an embedded SMU (if necessary)

HNAS 3080/3090 spare or replacement units are shipped without the embedded SMU installed.

Before you begin

The SMU software will need to be manually installed in the following case:

  • If the HNAS (all versions) is a spare/replacement and the field installer requires the embedded SMU to configure the replacement prior to adding to a cluster (or replacing a single node that has no external SMU). However, once added to the cluster, the embedded SMU should be uninstalled (smu-uninstall from the CLI of the newly added node). Note, when added to a cluster, the external SMU will disable the embedded SMU on the replacement node, but it is recommended to fully uninstall the embedded SMU.

Procedure

  1. Obtain a copy of the SMUsetup .iso file and copy the file into /tmp

    scp /tmp/SMUsetup.iso
  2. As 'root' on the node:

    cd /tmp
    mount –o loop SMUsetup.iso /mnt/cdrom
    /mnt/cdrom/autorun 
    
    NoteSMU iso images can be downloaded from Support Connect.

Replacing a single server with an embedded SMU

If a single server with an embedded SMU is non-functioning, and does not have a recent backup saved off platform, then a challenging and manual recovery process is necessary. If this circumstance is encountered, call the support organization for a copy of the system's latest diagnostics files. If available, these files can be used as a guide in reestablishing the system manually. The data and file systems will remain intact independent of the replacement and without a backup.

NoteReplacement 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.
ImportantSet expectations up front with the customer that this will delay time to recovery, and that some aspects of the systems configuration might never be recovered.

Obtaining backups, diagnostics, firmware levels, and license keys

On the old server:

Procedure

  1. If the server is online, using NAS Manager, navigate to Home Server Settings Configuration Backup & Restore, click backup, and then select a location to save the backup file.

    Ensure you save the backup file to a safe location off platform so that you can access it after the storage system is offline.

    The backup process performed by the embedded SMU will automatically capture both the SMU and server configuration files in one complete set.

  2. Navigate to Home Status & Monitoring Diagnostics download to download the diagnostic test results.

  3. Navigate to Home SMU Administration Upgrade SMU to verify SMU type and firmware release level.

    Both the server and SMU firmware versions must match those on the failed server; otherwise, the server cannot properly restore from the backup file. See the release notes and the Hitachi NAS Platform and Hitachi Unified Storage File Module System Installation Guide for release-specific requirements.
  4. Navigate to Home Server Settings Firmware Package Management to verify the existing server (SU) firmware release level.

  5. Navigate to Home Server Settings License Keys to check the license keys to ensure you have the correct set of new license keys.

Shutting down the server you are replacing

On the server that you are replacing:

Procedure

  1. From the server console, issue the command: shutdown --ship --powerdown

    Wait until the console displays Information: Server has shut down, and the rear panel LEDs turn off. The PSU and server fans continue to run until you remove the power cables from the PSU module. See the appropriate system component section for more information.
    NoteThis specific powerdown command prepares the system for both shipping, and potential long-term, post-replacement storage.
  2. Unplug the power cords from the power supplies.

  3. Wait approximately 15 seconds, and then confirm the NVRAM status LED is off.

    If the LED is flashing or fixed, press and hold the reset button for five seconds until the LED starts flashing. The battery disables when you release the reset button.
  4. Use the following rear panel figure and table to identify and label the cabling placement on the existing server.

  5. If cables are not labeled, label them before removing them from the server.

  6. Remove all cables from the server, and remove the server from the rack.

  7. Remove the rail mounts from the old server, and install them on the new server.

  8. Remove the battery from the old server, and install it in the new server.

  9. Remove the bezel from the old server, and install it on the new server.

  10. Insert the new server into the rack, and connect the power cords to the power supplies.

    NoteDo not make any other cable connections at this time.

Configuring the replacement server

Before you begin

Obtain the necessary IP addresses to be used for the replacement server. Servers shipped from the factory have not yet had the nas-preconfig script run on them, so a replacement server will not have any IP addresses pre-configured for your use. You need IP addresses for the following:

  • 192.0.2.200/24 eth1 (cluster IP)
  • 192.0.2.2/24 eth1 (testhost private IP)
  • 192.168.4.120/24 eth0 (testhost external IP, which might vary)

When you run the nas-preconfig script, it reconfigures the server to the previous settings. This step allows the SMU to recognize the server as the same and allows it to be managed. Reconfigured settings:

  • IP addresses for Ethernet ports 0 and 1
  • Gateway
  • Domain name
  • Host name

On the replacement server:

Procedure

  1. Log in to the server.

  2. Run the nas-preconfig script.

  3. Reboot if you are instructed to by the script.

  4. Log in to the SMU using one of the IP addresses you obtained.

  5. Use a KVM (keyboard, video, and mouse) or a serial cable to connect to the serial port on the server.

    Alternatively, you can connect by way of SSH using the following settings:
    • 115,200 b/s
    • 8 data bits
    • 1 stop bit
    • No parity
    • No flow control
    • VT100 emulation
  6. Log in as root and enter ssc localhost to access the BALI level command prompt.

  7. Enter evs list to obtain the IP configuration for the server.

  8. Using a supported browser, launch the NAS Manager using either of the IP addresses acquired from the EVS list output.

  9. Click Yes, and log in as admin.

  10. Verify and, if necessary, convert the new server to the model profile required.

    This step requires a separate process, training, and license keys. Contact Hitachi Vantara if the incorrect model arrives for replacement.
  11. Navigate to Home SMU Administration Upgrade SMU to verify and, if necessary, upgrade the embedded SMU to the latest SMU release.

  12. Navigate to Home Server Settings Firmware Package Management to verify and, if necessary, upgrade the new server to the latest SU release.

  13. Navigate to Home Server Settings Configuration Backup & Restore, select the desired backup file, and click restore to restore the system from that backup file.

  14. Reboot the server.

  15. Reconnect the data cables to the server.

Finalizing and verifying the replacement server configuration

The Fibre Channel (FC) link speed varies according to the server model. Use the appropriate speed for your model.

Model Fibre Channel link speed
4 Gbps

On the replacement server:

NoteThe following steps show the FC link speed as 8 Gbps as an example.

Procedure

  1. Navigate to Home Server Settings License Keys to load the license keys.

  2. Remove the previous license keys in the backup file, and add the new keys.

  3. Use fc-link-speed to verify and, if necessary, configure the FC port speed as required.; for example:

    1. Enter fc-link-speed to display the current settings.

    2. Enter fc-link-speed -i port_number -s speed for each port.

    3. Enter fc-link-speed to verify the settings.

  4. Use the fc-link-type command to configure the server in fabric (N) or loop (NL) mode.

  5. Modify zoning and switches with the new WWPN, if you are using WWN-based zoning.

    If you are using port-based zoning, the no modifications are necessary for the switches configurations.
  6. Open Storage Navigator and reconfigure LUN mapping and host group on the storage system that is dedicated to the server with the new WWPNs. Perform this step for every affected server port.

  7. If the server does not recognize the system drives, enter fc-link-reset to reset the fiber paths.

  8. Enter sdpath to display the path to the devices (system drives) and which hport and storage port are used.

  9. Enter sd-list to verify the system drives statuses as OK and access is allowed.

  10. Enter span-list to verify the storage pools (spans) are accessible.

    NoteIn this instance, cluster is synonymous with the standalone server.
  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 single server with an external SMU

Note that if it is a single server with an external SMU that is nonfunctioning, and does not have a recent backup saved off platform, then a challenging and manual recovery process is necessary. If this circumstance is encountered, call the support organization for a copy of the system's latest diagnostics files, if available, to be used as a guide in reestablishing the system manually. The data and file systems will remain intact independent of the replacement and without a backup.

NoteReplacement 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.
ImportantSet expectations up front with the customer that this will delay time to recovery, and that some aspects of the systems configuration might never be recovered.

Obtaining backups, diagnostics, firmware levels, and license keys

On the old server:

Procedure

  1. If the server is online, using NAS Manager, navigate to Home Server Settings Configuration Backup & Restore, click backup, and then select a location to save the backup file.

    Ensure you save the backup file to a safe location off platform so that you can access it after the storage system is offline.

    The backup process performed by the embedded SMU will automatically capture both the SMU and server configuration files in one complete set.

  2. Navigate to Home Status & Monitoring Diagnostics download to download the diagnostic test results.

  3. Navigate to Home Server Settings Firmware Package Management to verify the existing server (SU) firmware release level.

    The server firmware version must match the failed server; otherwise, the server cannot properly restore from the backup file. See the release notes and system installation guide for release-specific requirements.
  4. Navigate to Home Server Settings License Keys to check the license keys to ensure you have the correct set of new license keys.

  5. Record the following information:

    • IP addresses for Ethernet ports 0 and 1
    • Gateway
    • Domain name
    • Host name

Shutting down the server you are replacing

On the server that you are replacing:

Procedure

  1. From the server console, issue the command: shutdown --ship --powerdown

    Wait until the console displays Information: Server has shut down, and the rear panel LEDs turn off. The PSU and server fans continue to run until you remove the power cables from the PSU module. See the appropriate system component section for more information.
    NoteThis specific powerdown command prepares the system for both shipping, and potential long-term, post-replacement storage.
  2. Unplug the power cords from the power supplies.

  3. Wait approximately 15 seconds, and then confirm the NVRAM status LED is off.

    If the LED is flashing or fixed, press and hold the reset button for five seconds until the LED starts flashing. The battery disables when you release the reset button.
  4. Use the following rear panel figure and table to identify and label the cabling placement on the existing server.

  5. If cables are not labeled, label them before removing them from the server.

  6. Remove all cables from the server, and remove the server from the rack.

  7. Remove the rail mounts from the old server, and install them on the new server.

  8. Remove the battery from the old server, and install it in the new server.

  9. Remove the bezel from the old server, and install it on the new server.

  10. Insert the new server into the rack, and connect the power cords to the power supplies.

    NoteDo not make any other cable connections at this time.

Configuring the replacement server

Before you begin

Obtain the necessary IP addresses to be used for the replacement server. Servers shipped from the factory have not yet had the nas-preconfig script run on them, so a replacement server will not have any IP addresses pre-configured for your use. You need IP addresses for the following:

  • 192.0.2.200/24 eth1 (cluster IP)
  • 192.0.2.2/24 eth1 (testhost private IP)
  • 192.168.4.120/24 eth0 (testhost external IP, which might vary)

When you run the nas-preconfig script, it reconfigures the server to the previous settings. This step allows the SMU to recognize the server as the same and allows it to be managed. Reconfigured settings:

  • IP addresses for Ethernet ports 0 and 1
  • Gateway
  • Domain name
  • Host name

On the replacement server:

Procedure

  1. Log in to the server.

  2. Run the nas-preconfig script.

  3. Reboot if you are instructed to by the script.

  4. Log in to the SMU using one of the IP addresses you obtained once they can successfully connect using ssc localhost.

  5. Use a KVM (keyboard, video, and mouse) or a serial cable to connect to the serial port on the server.

    Alternatively, you can connect by way of SSH using the following settings:
    • 115,200 b/s
    • 8 data bits
    • 1 stop bit
    • No parity
    • No flow control
    • VT100 emulation
  6. Log in as root, and enter ssc localhost to access the BALI level command prompt.

  7. Enter evs list to obtain the IP configuration for the server.

  8. Using a supported browser, launch the NAS Manager using either of the IP addresses acquired from the EVS list output.

  9. Click Yes to proceed past the Security Alert, and log in as admin.

  10. Verify and, if necessary, convert the new server to the model profile required.

    This step requires a separate process, training, and license keys. Contact Hitachi Vantara Support Connect if the incorrect model arrives for replacement.
  11. Navigate to Home Server Settings Firmware Package Management to verify and, if necessary, upgrade the new server to the latest SU release.

  12. Navigate to Home Server Settings Configuration Backup & Restore, select the backup file you want, and click restore to restore the system from that backup file.

  13. Reboot the server.

  14. Reconnect the data cables to the server.

  15. To uninstall the embedded SMU, log in as root and issue the command: smu-uninstall

  16. Navigate to Home Server Settings License Keys to load the license keys.

  17. Remove the previous license keys and add the new keys.

Finalizing and verifying the replacement server configuration

The Fibre Channel (FC) link speed varies according to the server model. Use the appropriate speed for your model.

Model Fibre Channel link speed
4 Gbps

On the replacement server:

NoteThe following steps show the FC link speed as 8 Gbps as an example.

Procedure

  1. Navigate to Home Server Settings License Keys to load the license keys.

  2. Remove the previous license keys in the backup file, and add the new keys.

  3. Use fc-link-speed to verify and, if necessary, configure the FC port speed as required.; for example:

    1. Enter fc-link-speed to display the current settings.

    2. Enter fc-link-speed -i port_number -s speed for each port.

    3. Enter fc-link-speed to verify the settings.

  4. Use the fc-link-type command to configure the server in fabric (N) or loop (NL) mode.

  5. Modify zoning and switches with the new WWPN, if you are using WWN-based zoning.

    If you are using port-based zoning, the no modifications are necessary for the switches configurations.
  6. Open Storage Navigator and reconfigure LUN mapping and host group on the storage system that is dedicated to the server with the new WWPNs. Perform this step for every affected server port.

  7. If the server does not recognize the system drives, enter fc-link-reset to reset the fiber paths.

  8. Enter sdpath to display the path to the devices (system drives) and which hport and storage port are used.

  9. Enter sd-list to verify the system drives statuses as OK and access is allowed.

  10. Enter span-list to verify the storage pools (spans) are accessible.

    NoteIn this instance, cluster is synonymous with the standalone server.
  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.

    Information of the node to be replaced
    Node Number
    Softwear Version
    ETH0 Node IP Address
    ETH0 Subnet Mask
    ETH1 IP Address (if applicable)
    WWN-Port 1
    WWN-Port 2
    WWN-Port 3
    WWN-Port 4
  2. How is the current node connected to the storage?

    Direct Connected SAN Connected
  3. Is the storage using Host Group Security?

    No Yes

Preparing the new node

Prepare the new node prior to installation.

Procedure

  1. Obtain the HNAS Factory Reset code for the required level to be installed on the node.

  2. Complete a factory reset of the new node per the documented procedure in order to install the node at the desired code level.

  3. Run nas-preconfig on the node, entering the required information to allow BALI to start following a reboot of the new node.

    For the Admin EVS, enter a valid IP address that is available for use temporarily. Once this node is joined to the cluster this address will be removed and the existing Admin IP address in the cluster will be used.
  4. Ensure that the new node boots, and that you can connect to it via SSH and login to BALI.

  5. Use the CLI hport-wwn command to get the WWN information for the new node.

    Record the new WWN information for the new node.
    WWN Information
    WWN-Port 1
    WWN-Port 2
    WWN-Port 3
    WWN-Port 4

Preparing the old node for removal

Prepare the old node for removal before installing the new node.

Procedure

  1. Backup the SMU.

  2. Backup the Node Registry.

  3. If the node that you are replacing is still running, login to the SMU GUI.

  4. Migrate EVSs to an alternate node.

  5. Shut down the node.

  6. Once the node is shut down, go to Home Server Settings Cluster Configuration and delete the entry for the node that you are replacing.

  7. Label the cables connected to each of the ports on the node, and disconnect the cables once they have been labelled. Ensure that you use dust covers where required.

  8. Remove the old node from the rack.

  9. Place the old node into the packaging that the new node was shipped in and mark it as a bad part.

Installing the new node

You are now ready to install the new node.

Procedure

  1. Physically rack the new node into the place of the old node.

  2. Connect the cables to the new node, according your labelling.

  3. Power up the new node and ensure that BALI loads again.

  4. If the customer is using SAN attached, and/or host group security, update this to reflect the changes that are being made to the WWN, as you documented previously in Preparing the node, step 5.

  5. Add the new node as a managed server on the SMU.

  6. From the drop down in the SMU, select the existing Cluster.

  7. Go into Home Sever Settings Cluster Configuration and click on AddCluster node.

  8. Complete the add cluster node wizard, selecting the new node which will appear in the selection box, and enter the supervisor password where prompted (the default is supervisor). Upon completion of the wizard, the new node will reboot and join the cluster.

Finalizing and verifying the server configuration

On the new server:

Procedure

  1. Navigate to Home Status & Monitoring System Monitor to 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 new server will be provided within 15 days.
    • If the server is not operating normally for any reason, contact support for assistance.
  2. Navigate to Home Server Settings Cluster Configuration to verify the cluster configuration status. Ensure that the cluster is shown as Online and Robust and has the correct number of nodes.

  3. Use 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
           
  4. If EVS mapping or balancing is required, select the EVS to migrate, assign it to the preferred node, and then click migrate.

  5. To set the preferred node for any remaining EVSs, navigate to Home Server Settings EVS Management EVS Details.

  6. Select the node from the Preferred Cluster Node list, and then click apply.

  7. Navigate to Home Status & Monitoring Event Logs, and then click Clear Event Logs.

  8. 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 all servers within a cluster

If both servers with an external SMU that are nonfunctioning, and does not have a recent backup saved off platform, then a challenging and manual recovery process is necessary. If this circumstance is encountered, call the support organization for a copy of the system's latest diagnostics files, if available, to be used as a guide in reestablishing the system manually. The data and file systems will remain intact independent of the replacement and without a backup.

ImportantSet expectations up front with the customer that this will delay time to recovery, and that some aspects of the systems configuration might never be recovered.

Obtaining backups, diagnostics, firmware levels, and license keys

On the old server:

Procedure

  1. If the server is online, using NAS Manager, navigate to Home Server Settings Configuration Backup & Restore, click backup, and then select a location to save the backup file.

    Ensure you save the backup file to a safe location off platform so that you can access it after the storage system is offline.

    The backup process performed by the embedded SMU will automatically capture both the SMU and server configuration files in one complete set.

  2. Navigate to Home Status & Monitoring Diagnostics download to download the diagnostic test results.

    Select the devices for which diagnostics are required by checking the appropriate boxes. Then click download.
  3. Navigate to Home Server Settings Firmware Package Management to verify the existing server (SU) firmware release level.

    The new server firmware version must match the failed server; otherwise, the server cannot properly restore from the backup file. See the release notes and the System Installation Guide for release-specific requirements.

  4. Navigate to Home Server Settings IP Addresses to obtain:

    • Admin IP address and name
    • Cluster node IP address

    The evs list command also displays these IP addresses.

Shutting down the servers you are replacing

On the servers that you are replacing:

Procedure

  1. From the server console, issue the command: cn node shutdown --ship --powerdown

    (where node represents the targeted node)

    Wait until the console displays Information: Server has shut down, and the rear panel LEDs turn off. The PSU and server fans continue to run until you remove the power cables from the PSU module. See the appropriate system component section for more information.

    NoteThis specific powerdown command prepares the system for both shipping, and potential long-term, post-replacement storage.
  2. Unplug the power cords from the power supplies.

  3. Wait approximately 15 seconds, and then confirm the NVRAM status LED is off.

    If the LED is flashing or fixed, press and hold the reset button for five seconds or until the LED starts flashing. The battery disables when you release the reset button.
  4. Use the following rear panel figure and table to identify and label the cabling placement on the existing server.

  5. If cables are not labeled, label them before removing them from the server.

  6. Remove all cables from the server, and remove the server from the rack.

  7. Remove the rail mounts from the old server, and install them on the new server.

  8. Remove the battery from the old server, and install it in the new server.

  9. Remove the bezel from the old server, and install it on the new server.

  10. Insert the new server into the rack, and connect the power cords to the power supplies.

    NoteDo not make any other cable connections at this time.

Configuring the replacement servers

Before you begin

Obtain the necessary IP addresses to be used for the replacement server. Servers shipped from the factory have not yet had the nas-preconfig script run on them, so a replacement server will not have any IP addresses pre-configured for your use. You need IP addresses for the following:

  • Eth1 (cluster IP)
  • Eth1 (testhost private IP)
  • Eth0 (testhost external IP)
  • 192.0.2.200/24 eth1 (cluster IP)
  • 192.0.2.2/24 eth1 (testhost private IP)
  • 192.168.4.120/24 eth0 (testhost external IP, which might vary)
On a replacement server:

Procedure

  1. Log in to the server.

  2. Run the nas-preconfig script.

    The IP addresses are assigned at this step.
  3. Reboot if you are instructed to by the script.

  4. Log in to the SMU using one of the IP addresses you obtained once they can successfully connect using ssc localhost.

  5. Use a KVM (keyboard, video, and mouse) or a serial cable to connect to the serial port on the server.

    Alternatively, you can connect by way of SSH using the following settings:
    • 115,200 b/s
    • 8 data bits
    • 1 stop bit
    • No parity
    • No flow control
    • VT100 emulation
  6. Log in as root, and enter ssc localhost to access the BALI level command prompt.

  7. Enter evs list to see the IP configuration for the server.

  8. Using a supported browser, launch the NAS Manager using either one of the IP addresses acquired from the EVS list output.

  9. Click Yes to proceed past Security Alert, and log in as admin.

  10. Verify and, if necessary, convert the new server to the model profile required.

    This step requires a separate process, training, and license keys. Contact Hitachi Vantara if the incorrect model arrives for replacement.
  11. Navigate to Home Server Settings Firmware Package Management to verify and, if necessary, upgrade the new server to the latest SU release.

  12. Navigate to Home Server Settings Cluster Wizard, and promote the node to the cluster.

  13. Enter the cluster name, cluster node IP address, subnet, and select a quorum device.

    Note that the node reboots several times during this process.
  14. When prompted, add the second node to the cluster.

  15. Enter the physical node IP address, log in as supervisor, and click finish.

    Wait for the system to reboot.
  16. Enter smu-uninstall to uninstall the embedded SMU.

  17. Navigate to Home Server Settings Configuration Backup & Restore, locate the desired backup file, and then click restore.

  18. Reconfigure the server to the previous settings:

    • IP addresses for Ethernet ports 0 and 1
    • Gateway
    • Domain name
    • Host name

    The SMU should recognize the node as the same and allow it to be managed.

  19. Navigate to Home Server Settings License Keys to load the license keys.

  20. Repeat steps for any other replacement servers to be configured.

Finalizing and verifying the system configuration

On the new server:

Procedure

  1. Navigate to Home Status & Monitoring System Monitor to 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 new server will be provided within 15 days.
    • If the server is not operating normally for any reason, contact support for assistance.
  2. Navigate to Home Status & Monitoring Event Logs, and then click Clear Event Logs.

  3. 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.