Print | Rate this content

HPE StoreOnce 3.16.x - Upgrading StoreOnce Software

Upgrading StoreOnce software

NOTE: The upgrade from version 3.13.x converts the StoreOnce operating system and cannot be reversed.

Prerequisites

Verify that all prerequisites have been met, as described in Planning the software upgrade and Preparing for the software upgrade.

Procedure

  1. Transfer the upgrade package to the StoreOnce appliance

  2. Update the StoreOnce software with the CLI

  3. Verify that the software update was successful

  4. Apply firmware updates

  5. Complete the upgrade process

top

Copying the upgrade package to the StoreOnce server

In the following instructions:

  • <Management IP Address> is the IP address normally used to log on to the StoreOnce GUI or CLI.

  • <Package RPM> is the file name of the upgrade package RPM file.

Procedure

  • Using Linux

    1. sftp Admin@ <Management IP Address>

    2. cd repository

    3. put <Package RPM>

    4. exit sftp

  • Using a Windows sftp client

    1. Ensure the File Protocol is set to SFTP, not SCP or FTP.

    2. Log in to the Management IP address as Admin.

    3. Copy <Package RPM> to repository.

top

Updating the StoreOnce software

Use the StoreOnce CLI to update the StoreOnce software and log in as an Admin user. On a StoreOnce 6x00 system, enter the commands on the active node.

NOTE: When upgrading from 3.13.x, you will run the system update packages command twice. Between the two instances of this command, there is an additional manual step that ensures the existing configuration is stored safely before the upgrade runs and the underlying operating system is converted.

If you encounter an error during the upgrade process, Troubleshooting the upgrade process on the following article.

Click here to access the Troubleshooting the upgrade process .

Prerequisites

Prerequisites for StoreOnce 6x00 systems:

  • Service sets are stopped and failover is disabled. Once the software upgrade has completed successfully, failover can be enabled manually. Service sets restart automatically.

  • You are connected to the StoreOnce 6x00 system through a physical IP address.

    The system update packages command will fail if you are connected through the VIF address and the error message will display the correct IP address for login.

Procedure

  1. Log in to the SSH as an Admin User and run system show repository to list the rpm file you copied over. Verify that it is the correct file.

  2. Distribute the package across all nodes in the cluster and unpack them.

    system load package <Package RPM>

    <Package RPM> is the filename of the upgrade package and is found in the release notes.

  3. Verify that the packages are staged and ready for update.

    system show packages

    NOTE: The name of the package once it is loaded and unpacked is in the following format:

    Package Version State
    ---------- ------------- -----
    D2D_Master 3.1x.x-xxxx.x staged

  4. On StoreOnce 6x00 systems, stop service sets and disable failover.

  5. On all StoreOnce Systems, run system update packages.

    NOTE: To protect customer data, the upgrade utility will check the status of the Product Hardware, Service Sets, and Event Database size. If any elements are in a degraded or nonfunctional state, the upgrade utility will not carry out the requested software and\or firmware upgrades. If the upgrade utility will not upgrade the software or firmware, continue using the system with the existing software and contact HPE Support for further help.

    When upgrading from 3.13.x, the first time that this command is run, it creates and saves a saved_config.tgz file to the saved_config directory on the node that is running Active Fusion Manager. The upgrade process will automatically use this file to rebuild your configuration and data stores after the operating system has been converted. The system displays a series of messages.

    Saving the system configuration. Can take 20 minutes to complete.
    System configuration successfully saved. 18 minutes elapsed.
    ....
    Cleaning up old packages
    The OS conversion is not yet complete.
    Do not use the system for any other purpose until the update is complete.
    The current system configuration has been saved and it is available at
    /saved_config/saved_config.tgz
    Please use sftp to copy this off the system, save it and then run
    “system update packages” again.
    Your CLI session has expired. Please exit the current session and login again.

    NOTE: HPE Support will be able to restore your system using this file if you encounter any problems with the subsequent upgrade.
  6. When upgrading from 3.13.x only, save a copy of the configuration file and then run system update packages again.

    NOTE: When upgrading from 3.14.x or later, system update packages is only run once.
    1. Copy the saved_config.tgz file and its hashsum file from the saved_config directory to a safe location.

      Use sftp to copy the file and then use the hashsum file to verify the contents of saved_config.tgz.

      If the file is not visible, refresh your FTP client.

    2. Log back in to SSH as Admin user.

    3. Run system update packages for a second time to begin the process to upgrade and reboot all the nodes in the cluster.

      Service sets will restart automatically at startup.

      Required services started successfully.
      Saving the system configuration. Can take 20 minutes to complete.
      System configuration successfully saved. 4 minutes elapsed.
      Start reboot of the system.
      Processing,,,
      Broadcast message from root (Mon Xxx 13 16:52:18 20xx):
      System rebooting to complete the update process.
      The system is going down for reboot NOW!
      Update will complete after rebooting.
      SSh connection will be lost. Allow 20–30 minutes for reboot to
      complete before reconnecting.
      # Connection to 1.1.1.1 closed by remote host.
      Connection to 1.1.1.1 closed.

      The StoreOnce System reboots and initiates the OS conversion, which completes automatically.

  7. Verify that the update was successful.

  8. Apply firmware updates.

  9. On StoreOnce 6x00 Systems only, re-enable failover.

    1. Run the StoreOnce CLI command system enable failover.

    2. Run the StoreOnce CLI command hardware show node status and verify that HA (failover) is reported as turned on for all nodes in the cluster.

top

Stopping service sets and disabling failover (6x00 systems only)

Stop service sets and disable failover before running system update packages.

Procedure

  1. Stop service sets using the StoreOnce CLI command serviceset stop all.

    It might take several minutes for all service sets to stop.

  2. Verify that all service sets have stopped.

    If service sets are still running, wait one minute and try again, until the status is Not Running.

    service show status

    The following example is from a two-node cluster.

    # service show status
    Service Set 1 Status
    ------------- -------
    Overall : Not Running
    Service Set 2 Status
    ------------- -------
    Overall : Not Running
    #

  3. Disable failover by running the StoreOnce CLI command system disable failover.

  4. Verify that HA (failover) is reported off for all nodes in the cluster by running the StoreOnce CLI command hardware show node status.

top

Verifying that the software update was successful

Once access returns to the Management interface, verify that the process has completed successfully.

Prerequisites

The system has rebooted.

NOTE: The update process can take up to 30 minutes for StoreOnce 6x00 Systems and up to 15 minutes for all other products.

Procedure

  1. Use the StoreOnce CLI command system show packages to verify that all packages are now installed, as well as staged.

    The output is in the following format:

    Package Version State
    ---------- ------------- -----
    D2D_Master <version> installed

    NOTE: When upgrading from 3.13.x, only the installed version is displayed.
  2. On the StoreOnce GUI, verify that the software reversion number reported in the System Information details has updated to the software version listed in the release notes.

  3. On the StoreOnce GUI, verify that the Event log has a software upgrade confirmation message (Event Code: E01070016).

    Update D2D_Master-<version> completed successfully

top

Applying firmware updates

HPE recommends updating system firmware when updating StoreOnce software.

You can use the StoreOnce GUI or the StoreOnce CLI to carry out this task. See the user guide for your product for information about using the StoreOnce GUI.

Prerequisites

This procedure does not apply to VSA.

  • Use a supported web browser when using the StoreOnce GUI to run firmware management.

    Firmware management does not work with the Internet Explorer 8 web browser. Supported browsers include:

    • Internet Explorer 9, 10 and 11

    • Mozilla Firefox v23 and above

    • Firefox ESR24 and above

    Refer to the user guide for your StoreOnce System for more details.

  • If the system is using StoreOnce Remote Support, disable remote event reporting during the upgrade process, using the StoreOnce CLI command system enable remoteeventssuppression "firmware update started".

  • Before updating all other components in the system, the Storage_Ctlr firmware must be at version 2.50 or higher.

    On StoreOnce version 3.16.0 and later, you can update the firmware for all of the storage controllers, run the CLI command hardware update firmware Storage_Ctlr.

  • Updating firmware for a multi-node system requires a coordinated reboot. Once the system has rebooted, update the firmware for the remaining components as required.

top

Updating firmware from the StoreOnce GUI

Procedure

  1. Select Firmware to view the firmware versions for hardware components, and to update firmware versions if required.

    The Firmware window appears with the following tabs:

    • Server: Contains firmware details for all server components.

    • Storage: Contains firmware details for all storage components.

    • Switch: Contains firmware details for all switch components on StoreOnce 6600 and 6500 systems only.

  2. Click Scan to perform a check on the currently installed firmware versions for all components. This will populate the firmware tabs and may take several minutes to run.

    NOTE: The scan will fail if a firmware update is already in progress.
  3. After you have run a Scan, the Recommended Action field in the component list is updated to show whether individual components require an upgrade or a downgrade. Components requiring an upgrade are automatically selected. A downgrade takes longer to complete and is optional for some components, such as hard drives. If downgrades are identified, the user may either select them to be included or decide to carry them out separately, if required, after the upgrade has completed.

    NOTE: When the firmware updates are initiated, the backup devices will be taken offline. Before performing this step, check that there are no outstanding backup jobs pending.

    Do not shut down or reboot your system or any system component until the final step. Special instructions may apply.

  4. Click Update Selected or Update All. (Update All will attempt to update all components that are in the state where there is an update recommended; it will not try to update components that do not need an update.)

  5. The Status field will show which components are being updated and which updates have been completed

  6. In some cases, when firmware has been loaded, you will need to perform a reboot to complete the firmware update. A pop-up message will appear on your GUI screen after loading is completed, if a reboot is required. The message will also advise what type of reboot is required.

    • If a software reboot is needed, you will see a message asking if you want to reboot your system now or later. If you click Yes, your system will be rebooted.

    • A power cycle, or cold reboot, requires that the system must be shut down for at least 60 seconds before powering on using the Power-On buttons on the appliance.

    • A coordinated reboot is a corner case with StoreOnce 6600 and 6500 Systems and requires assistance from HPE Support.

top

Updating firmware using the StoreOnce CLI

Procedure

  1. Run the StoreOnce CLI command to show the current status of firmware.

    # hardware show firmware <nodeX|storageX|switch|all>

    NOTE: X is the number of the node or storage to which the command should be applied. You must run the command for each component separately, but for the switch (only applicable to StoreOnce 6600 and 6500 Systems), the command lists or upgrades the firmware versions for all network switch components.
  2. Check the Action column to see if any firmware needs upgrading.

    NOTE: Do not shutdown or reboot your system or any system component until the final step. Special instructions may apply.
  3. Use the hardware update firmware command, as required.

    The command syntax is:

    hardware update firmware <nodeX|storageX|switch|all>

    The all parameter updates all firmware components in parallel, in the sequence: switch, node, storage. If you use one of the other parameters, be aware that you must repeat the command for each node and storage component in your system. All switches are updated concurrently.

    There may be instances where replacement hardware may need a firmware downgrade to bring it in line with the supported firmware version of the installed StoreOnce software on the system being maintained. Use the force parameter in the command to enable this, but be aware that the update will take longer to complete.

    NOTE: Update the firmware on all nodes, storage components and switches before shutting down or rebooting the system. Please refer to Customer Notice c04682361 for full details on performing firmware upgrades on StoreOnce Systems.
  4. In some cases, when firmware has been loaded, you will need to perform a reboot to complete the firmware update. A message is displayed in the CLI output after successful completion, if a reboot is required. The message will also advise what type of reboot is required.

    • Reboot the system using the StoreOnce CLI command: system reboot

    • Power down the nodes using the StoreOnce CLI command: system shutdown

      After the system has completely shut down, wait at least 60 seconds before powering on using the Power-On buttons on the appliance.

    • A coordinated reboot is a corner case with StoreOnce 6600 and 6500 Systems and requires assistance from HPE Support.

  5. On StoreOnce 6600 and 6500 Systems only, enable failover using the StoreOnce CLI command, system enable failover

top

Completing the update

Procedure

  1. Clear the browser cache, enable TLS 1.1 or 1.2 in settings, and reopen the browser.

  2. Collect a support ticket and save for future reference.

  3. Back up the system configuration using the StoreOnce CLI command, config save devices.

  4. If using encrypted VTL, NAS or StoreOnce Catalyst stores, back up the key configuration using the StoreOnce CLI command, config save keystore.

  5. On AIX systems, reconfigure the StoreOnce Catalyst over FC port Host Emulation from “Default” to “AIX” in the StoreOnce GUI.

top

Verifying the DNS configuration when using remote support

Procedure

  1. Update the Enterprise Server URL and verify the DNS configuration.

    1. On the StoreOnce GUI page for Remote Support, ensure that the Enterprise Server URL is set to the new URL.

    2. Verify that the DNS server allows storage-support.glb.itcs.hpe.com to resolve to one of the following:

      • 16.248.72.63 - storage-support1.itcs.hpe.com

      • 16.250.72.82 - storage-support2.itcs.hpe.com

    3. For Outbound Connectivity (File transfer from StoreOnce to HPE), verify that port 443 (https) is open (outbound) between the StoreOnce IP and the following IP addresses:

      • 16.248.72.63 - storage-support1.itcs.hpe.com

      • 16.250.72.82 - storage-support2.itcs.hpe.com

  2. Optionally re-enable event reporting.

    Remote event reporting will be re-enabled on reboot. If the system has not been rebooted, you can use the StoreOnce CLI command, system disable remoteeventsuppression "firmware update complete", or wait 24 hours for it to be automatically re-enabled.

top

Legal Disclaimer: Products sold prior to the November 1, 2015 separation of Hewlett-Packard Company into Hewlett Packard Enterprise Company and HP Inc. may have older product names and model numbers that differ from current models.

Provide feedback

Please rate the information on this page to help us improve our content. Thank you!
Document title: HPE StoreOnce 3.16.x - Upgrading StoreOnce Software
Document ID: emr_na-a00043185en_us-1
How helpful was this document?
How can we improve this document?
Note: Only English language comments can be accepted at this time.
Please wait while we process your request.