Articles in this section

Upgrading to VAST Cluster 3.2.x

Sara Levy
  • Updated
Follow

Note

The procedural instructions on this page are based on VAST Cluster 3.0.6. If you are upgrading a cluster from a different release, some of the instructions may vary slightly.

Plan the Upgrade

Note these points before upgrading.

Upgrade Paths

Upgrading to VAST Cluster 3.2.x is supported from VAST Cluster 3.0.x .

If the cluster is running an earlier release, upgrade to VAST Cluster 3.0.x before following the instructions on this page to upgrade to VAST Cluster 3.2.x.

Impact and Scheduling

By default, the upgrade runs as a non disruptive upgrade (NDU). There is an alternative option to run a cold upgrade instead.

The duration of the main upgrade process depends on the cluster's workload and size. Expect a cluster upgrade to take at least one hour for the smallest size cluster (1 DBox and 1CBox) and proportionally longer for larger clusters.

We recommend not to run any other carrier replacements, server expansions or other such field operations in parallel to the upgrade.

During NDU, clients can continue to write data to the cluster. However, the following operations are blocked:

  • Creating, modifying and deleting VIP Pools

  • Uploading a support bundle

  • Setting a password

  • Enabling or disabling a CNode or DNode

  • Creating or modifying a view policy

  • Enabling or disabling an SSD or NVRAM

  • Creating a user.

There are a few post upgrade tasks that continue for a while after the NDU is complete. During that post upgrade phase, the following activities are blocked:

  • Another upgrade (which could be a software upgrade or an NVRAM upgrade)

  • Certain VMS operations the modify metadata, such as setting quotas.

 

Check VAST OS Versions

Cluster upgrade to 3.2.x minimally requires VAST OS 10.0.10 on all CNodes and DNodes in the cluster. We also recommend upgrading for any OS earlier than 10.0.25 in order to benefit from the full functionality of the release.

CNode OS upgrade is an optional upgrade that you can select to run together with the cluster upgrade.

DNode OS upgrade is unavailable via VAST Web UI or VAST CLI. In case of DNodes running an OS version prior to 10.0.10, please ask VAST Data Support to help you upgrade the DNode OS before you begin the cluster upgrade.

Should you wish to upgrade DNodes that are currently running VAST OS 10.0.10 or later, please ask VAST Data Support to help you upgrade the DNodes after the cluster upgrade is complete.

To check CNode and DNode OS versions from the VAST Web UI:

  1. In the VAST Web UI, open the menu from the menu button (menu_button.png) at the top left and select the Maintenance page.

  2. Select the CNodes tab.

  3. For each CNode, find the OS listed in the OS column.

To check CNode and DNode OS versions from the VAST CLI:

  1. From the VAST CLI, run cnode list.

  2. For each CNode listed, find the OS listed in the OS-Version column of the command output.

 

Obtain a Target Release Package Download Link

Obtain a link for downloading the target release package. Links may be available in the version release notes. Otherwise, please request a link from VAST Data Support.

The package file contains images for all components you might upgrade, including for example, the OS that runs on the CNodes and DNodes, which is not upgraded by default.

 

Upgrade via VAST Web UI or VAST CLI

Upgrading from 3.0.x to 3.2.x Using the VAST Web UI

  1. Download the package file to your local machine.

  2. Connect to the VAST Web UI.

  3. From the menu, (click menu_button.png at the top left), select the Maintenance page.

  4. On the Clusters tab, click the upgrade button (upgrade_button.png) for the cluster.

    Maintenance_upgrade_button_3-0-6_2.png

    The Upgrade Cluster dialog appears.

    UpgradeClusterDialog_3-0-6_b.png

  5. Click Upload a File and browse to the package file you downloaded.

  6. Enable options as needed:

    • Cold. Deactivates the cluster during upgrade. When not selected, cluster operation continues without disruption.

    • Force. Forces upgrade regardless of version or upgrade state. Use this option if you need to upgrade to the same version as already installed or if a previous upgrade failed without the upgrade state clearing.

    • OS. Upgrades the OS on the CNodes. Be sure to check this if you need to upgrade the CNode OS.

    • NVRAM. Do not enable this option for this procedure. This option upgrades the NVRAM firmware without upgrading the core platform software.

    • DR. Enables data reduction on upgrade for a cluster that doesn't yet have data reduction enabled.

  7. Wait patiently for upgrade to complete. Upgrade progress is displayed as an activity:

    upgrade_in_progress.png

  8. Switch to the Activities page to see live log updates as the upgrade progresses.

 

Upgrading from 3.0.x to 3.2.x Using the VAST CLI

  1. Connect to the Management CNode using the local IP (not the VMS VIP).

  2. Download the package file to the Management CNode, placing it under /vast/bundles. For example:

    aws s3 cp <package file path>  /vast/bundles/<package file name>

    Note

    It is important that the file is specifically copied to /vast/bundles and not to any other location.

  3. Run the following command to start VAST CLI:

    vcli -u <username> -p <password>

  4. From the VAST CLI run the cluster upgrade command.

    For example, if CNode OS upgrade is not needed:

    cluster upgrade --build-package /vast/bundles/release-<release number>-<pipeline number>.vast.tar.gz

    Alternatively, with CNode OS upgrade:

    cluster upgrade --build-package /vast/bundles/release-<release number>-<pipeline number>.vast.tar.gz --os-upgrade

  5. Wait patiently for upgrade to complete.

    Initially, the build file is extracted and imported, which takes some time. Once that stage is complete, the upgrade begins and the progress is displayed in the CLI.

 
 
 

Related articles

Comments

0 comments

Article is closed for comments.