Upgrading the System Software

Review the following checklist before you upgrade the system software.

Pre-Upgrade Checklist

For the latest information about upgrade paths and restrictions, see the Release Notes: Automated Uptime Layer with Smart Exchange Release WIN-2.1.0.1 (Windows).

If Hyper-V is enabled on your ztC Endurance system, ensure that you have backed up and shut down all of your virtual machines before performing an upgrade. If the virtual machines are properly configured to autostart, they restart immediately after the initial host reboot. If the ztC Endurance console​ prompts you to reboot again, the BIOS needs to be upgraded, and you will need to shut down your virtual machines again unless you configured them in advance to shut down with the system. The total downtime for the virtual machines is approximately 1 hour.

Prepare to accept the end-user license agreements (EULAs) that are presented during the upgrade process. To locate and read the text of the EULAs you must accept before upgrading Automated Uptime Layer with Smart Exchange, see End-User License Agreements and Warranty. You should not perform the upgrade if you cannot accept the EULAs or are not authorized to accept them. The upgrade process terminates if you decline any EULAs.

Use the ztC Endurance console​ to do the following:

With the ztC Endurance system shut down, detach most peripheral devices from the system (exceptions are noted below). Devices to detach include:

Before scheduling a maintenance window, qualify your upgrade kit to ensure it is ready to apply. The Qualify button becomes active after you download an upgrade kit and add it to the ztC Endurance console​Upgrade Kits page as described in the following sections.

If you do not have an account on the Penguin Solutions Customer Service Portal, create one.

Downloading an upgrade kit requires access to the Penguin Solutions Customer Service Portal.

To download the Automated Uptime Layer with Smart Exchange upgrade kit

1. Click the following link to access the Penguin Solutions Customer Service Portal:

   https://support.penguinsolutions.com/csm

2. Click Login, enter your credentials, and click Sign In.

3. On the Welcome to Customer Service page, click Software Downloads.

4. On the Software Downloads page, select the following values:

   1. Under Product, select ztC Endurance.

   2. Under Operating System, select Windows.

   3. Under Model, select the desired model.

   ztC Endurance - Windows Downloads is displayed.

5. Click Upgrade Kit.

6. Scroll down to locate the files for System Software Build 2.1.x.x (where x.x represents the release of the upgrade files). Download the following files, all of which are required for the upgrade process:

   • System Software Build 2.1.x.x for Windows Upgrade Kit (the upgrade kit (.kit))

   • System Software Build 2.1.x.x for Windows Upgrade Kit SHA256sum (the upgrade kit checksum file (.sha256))

   • System Software Build 2.1.x.x for Windows zenupgrade executable (the zenupgrade-win program)

7. Log in with your Windows Administrator credentials, if you have not already done so, and open the Windows command line or PowerShell. Ensure that you are in the C:\Users\Administrator directory, which contains the zenupgrade-win program, the upgrade kit, and the upgrade kit SHA256sum file. For example:

   PS cd C:\Users\Administrator

8. Run the following commands to verify the integrity of the upgrade kit (.kit) and executable files by comparing their checksum to the one provided in the SHA256sum (.sha256) file. (The following example uses 2.1.0.0, but replace it with the release number of the upgrade files you are using.)

   PS C:\Users\Administrator> (Get-FileHash 'ztcEndurance_upgrade_win_2.1.0.0-110.kit').Hash -eq (Get-Content 
   ztcEndurance_upgrade_win_2.1.0.0-110.sha256sum)
   
   True
   
   PS C:\Users\Administrator> (Get-FileHash 'zenupgrade-win_2.1.0.0-110.exe').Hash -eq (Get-Content 
   zenupgrade-win_2.1.0.0-110.sha256sum)
   
   True

   If the checksum matches, the command responds with True. If the checksum does not match, delete the kit file, download a new copy, and repeat this step.

After downloading and verifying the upgrade files, upload the files to the C:\Users\Administrator directory on the Windows host.

To upload the upgrade files if you are upgrading from 2.0.x to 2.1.x or higher

Because the ztC Endurance console​ does not contain an Upgrade Kits page in Release 2.0.x to download the upgrade files directly to Windows host, you must manually transfer the upgrade files from a remote management computer to the Windows host.

Use one of the following methods to upload the upgrade files:

• To upload the upgrade files over the network, use a secure copy (SCP) utility such as WinSCP. For information about downloading an SCP utility to use for file transfers, see Configuring SSH for Remote System Management.

• To upload the upgrade files with a USB storage device:

  1. Use Windows commands to copy the files to an NTFS-formatted USB storage device.

  2. Plug the USB storage device into one of the USB 3.0 ports on the front of the ztC Endurance system (Figure 5 shows the location of the ports).

  3. Use Windows commands to copy the files to the C:\Users\Administrator directory on the Windows host.

  4. Remove the USB storage device.

To upload the upgrade kit if you are upgrading from 2.1.x to 2.1.x or higher

1. Log in to the ztC Endurance console​ as the zenadmin user.

2. In the ztC Endurance console​, click Upgrade Kits in the left-hand navigation panel.

3. On the Upgrade Kits page, click the Add a kit button beneath the masthead, which opens the Kit Upload Wizard.

4. In the Kit Upload Wizard dialog box, click Choose File (in Google Chrome) or Browse (in Firefox or Microsoft Edge), and then browse to select a .kit file.

5. After you have selected a .kit file, click Upload, Import, or Finish (they perform the same function). A message such as Uploading file (DO NOT CLOSE WIZARD) may appear while the file is uploading to the C:\Users\Administrator directory. The upload may require up to two minutes for a file stored locally, to ten or more minutes for a file stored over a network. If the upload fails, the wizard displays the message Failed to upload file.

6. After the upload is complete, the wizard closes and the Upgrade Kits page lists the state and version number of the upgrade kit. The Upgrade and Delete buttons also appear with the Add a kit button.

7. If more than one upgrade kit is loaded, select the one to use.

After uploading the upgrade kit, perform one of the following upgrade procedures:

• If you are upgrading from Release 2.0.x.x to 2.1.x.x or higher, see Upgrading from Release 2.0.x.x to 2.1.x.x or Higher, followed by Completing the Upgrade.

• If you are upgrading from Release 2.1.x.x to a later version, see Upgrading from Release 2.1.x.x to a Later Version, followed by Completing the Upgrade.

  Caution: Do not use SSH during this upgrade process because network connectivity is disconnected when the network drives are upgraded, and the upgrade may not complete. Instead, use Remote Desktop or the BMC KVM interface (Remote Control).
  Notice: In the following upgrade procedures, the system prompts you to reboot if the BIOS requires an upgrade. This can occur immediately after the host software has been upgraded or after the standby compute module has been fully upgraded. In either case, respond to the prompt to continue the upgrade.

Upgrading from Release 2.0.x.x to 2.1.x.x or Higher

This section describes how to use the zenupgrade-win program to upgrade from Automated Uptime Layer with Smart Exchange Release 2.0.x.x to 2.1.x.x or higher.

The upgrade program, zenupgrade-win, is located in C:\Users\Administrator.

Upgrade program usage:

Usage : zenupgrade-win_version {options}

Options:
-k filename   ztC Endurance upgrade kit (.kit) file
-p password   ztC Endurance console​ administrative password
-u username   ztC Endurance console​ administrative username
              (for example, the default admin account)

To upgrade from Automated Uptime Layer with Smart Exchange Release 2.0.x.x to 2.1.x.x or higher

1. Enter the zenupgrade-win command. For example:

   PS C:\Users\Administrator> .\zenupgrade-win_2.1.0.0-121.exe -k ztcEndurance_upgrade_win_2.1.0.0-021.kit  -u admin 
      -p mypassword

2. When prompted, read the ztC Endurance Service Terms and Conditions. For links to the full text of this and other agreements associated with ztC Endurance, see End-User License Agreements and Warranty. To accept the terms, type yes and press Enter.

   Caution: When the zenupgrade-win program upgrades the Windows host software, the Windows host will prompt you to restart Windows to apply the changes; however, you must ignore the prompt and allow the zenupgrade-win program to automatically restart the Windows host at the correct time. If you manually restart the system while the zenupgrade-win program is still working on subsequent tasks, the upgrade might fail and leave the system in an unusable state.

3. The zenupgrade-win program prepares the software upgrade components and upgrades Automated Uptime Layer with Smart Exchange. When the upgrade program completes these initial tasks, which take about 10 minutes, the system prompts you to press Enter to reboot the Windows host.

   Notes:  

   • At this point, the zenupgrade-win program has completed, and the management service performs the remaining upgrade steps after Windows reboots.

   • You lose access to the ztC Endurance console​ for several minutes when the standby compute module restarts.

   • Refresh your web browser and log in again to display the new ztC Endurance console​ pages included with this release, including the new Upgrade Kits page that you can use to monitor upgrade progress. The Upgrade Kits page does not appear in the user interface until you refresh the web browser.

4. Perform the steps described in Completing the Upgrade.

Upgrading from Release 2.1.x.x to a Later Version

This section describes how to use the ztC Endurance console​ to upgrade from Automated Uptime Layer with Smart Exchange Release 2.1.x.x to a later version.

To upgrade from Automated Uptime Layer with Smart Exchange Release 2.1.x.x to a later version

1. Click Upgrade Kits in the left-hand navigation panel.

2. The upgrade kit that you uploaded earlier should appear on this page in the Ready state. Select this upgrade kit and click Upgrade to start the upgrade. Click Yes to confirm.

   Notice: If you click Upgrade and a pop-up window appears with the message Upgrade Is Disabled as well as explanatory text, click Yes in the pop-up window. Otherwise, the upgrade cannot continue.
   
   

3. While an upgrade is in progress, the Upgrade Kits page lists the state of the Host (Windows), Compute Module A, and Compute Module B as Pending, Updating packages, or Up to date. You can also monitor the progress of the upgrade through alerts displayed on the Dashboard page and by looking for Autoburn Status under the Summary tab on the Hardware page.

4. When the ztC Endurance console​ prompts you to reboot, click Yes. Click Yes again to confirm.

   Notice: As the system upgrades the Windows host, the network briefly disconnects. When the network returns, refresh the Upgrade Kits page so that the progress displayed is up-to-date.

5. After the Windows host reboots, the following screens appear:

   1. The ztC Endurance console​ login screen appears. Do nothing.

   2. A window displaying This site can't be reached appears. Do nothing.

   3. When the ztC Endurance console appears again, log in. If the login fails, wait a few minutes until the system is fully booted and try again.

6. Perform the steps described in Completing the Upgrade.

Completing the Upgrade

This section describes how to monitor and complete the upgrade.

To complete the upgrade

1. Continue to monitor the upgrade progress by opening the Upgrade Kits page. While an upgrade is in progress, the Upgrade Kits page lists the state of the Host (Windows), Compute Module A, and Compute Module B as Pending, Updating packages, or Up to date. You can also monitor the progress of the upgrade through alerts displayed on the Dashboard page and by looking for Autoburn Status under the Summary tab on the Hardware page.

   Notice: The Upgrade Kits page notifies you if any upgrade step fails. If you encounter an error, contact Penguin Solutions Customer Service for assistance with clearing the error condition and issuing the sysupdate -reset system command. After the error is cleared, the upgrade resumes and displays the Apply in progress status again.
   Caution: The Upgrade Kits page allows you to monitor the upgrade; however, there will still be long periods when it appears that there is no progress even while the upgrade continues in the background. Do not interfere with the upgrade or restart the system; otherwise, you might leave the system in an unusable state. If the upgrade takes longer than 3 hours with no signs of progress on the Upgrade Kits page, contact your authorized Penguin Solutions service representative for assistance before proceeding any further.

2. The system automatically completes the following tasks:

   • Puts the standby compute module into maintenance mode

   • Shuts down the Standby OS on the standby compute module

   • Upgrades the BMC and BIOS firmware on the standby compute module if necessary

   • Upgrades the Standby OS software (Ubuntu) on the standby compute module

   • Restarts the standby compute module

3. When the standby compute module is up to date, the system initiates a reboot exchange after you respond to the prompt in the ztC Endurance console​:

   • Automatically shuts down the Windows host

   • Takes the upgraded compute module out of maintenance mode

   • Performs a reboot exchange to reprovision the storage and devices​ to the upgraded compute module

   • Starts the Windows host on the upgraded (that is, the former standby) compute module, which is now the active compute module

4. When the ztC Endurance console​ prompts you to reboot, click OK and then click yes. At this point, the system begins to shut down the Windows host in preparation for the reboot exchange.

   Notes:  

   • You lose access to the ztC Endurance console​ for up to 20 minutes. After the Windows host restarts, refresh your web browser and log in again.
   • After the reboot exchange, no further downtime is needed.

5. Wait for the reboot exchange to complete. When the Windows host is running on the newly upgraded compute module, software, and firmware, the system:

   • Puts the standby compute module into maintenance mode

   • Shuts down the Standby OS on the standby compute module

   • Upgrades the BMC and BIOS firmware on the standby compute module if necessary

   • Upgrades the Standby OS software (Ubuntu) on the standby compute module

   • Restarts the standby compute module

   • Takes the standby compute module out of maintenance mode

6. Continue monitoring the upgrade progress on the Upgrade Kits page of the ztC Endurance console​. At this point, the Upgrade Kits page displays the state of the Host (Windows) and the newly upgraded Compute Module x as Up to date, and it displays the state of the standby Compute Module x as Updating packages. You can also view the state of the compute modules on the Dashboard page.

7. After the system upgrades the standby compute module, the upgrade process is complete. On the Upgrade Kits page, the upgrade kit State changes to Applied.

1. In the ztC Endurance console​, verify that the system is healthy with no outstanding alerts. Resolve and clear any alerts before continuing.

2. Optionally, delete the upgrade kit from the ztC Endurance console​ as described in the Upgrade Kits Page.

3. If you need to use ASNConnect to allow service personnel to remotely diagnose your system as described in Enabling ASNConnect , the system must have an active license installed before you enable the ASNConnect software.

4. If the ztC Endurance console​ alerts you to register, you should register the system, download a license file, and apply the license file as described in Registering the System.

5. Verify that your system is functioning properly on the new software.

6. Verify that your virtual machines are functioning properly. If you disabled autostart for any virtual machines, remember to re-enable it.