Skip to main content
Cloud Volumes ONTAP
All cloud providers
  • Amazon Web Services
  • Google Cloud
  • Microsoft Azure
  • All cloud providers

Upgrade Cloud Volumes ONTAP software

Contributors netapp-rlithman netapp-bcammett netapp-driley

Upgrade Cloud Volumes ONTAP from BlueXP to gain access to the latest new features and enhancements. You should prepare Cloud Volumes ONTAP systems before you upgrade the software.

Upgrade overview

You should be aware of the following before you start the Cloud Volumes ONTAP upgrade process.

Upgrade from BlueXP only

Upgrades of Cloud Volumes ONTAP must be completed from BlueXP. You should not upgrade Cloud Volumes ONTAP by using System Manager or the CLI. Doing so can impact system stability.

How to upgrade

BlueXP provides two ways to upgrade Cloud Volumes ONTAP:

  • By following upgrade notifications that appear in the working environment

  • By placing the upgrade image at an HTTPS location and then providing BlueXP with the URL

Supported upgrade paths

The version of Cloud Volumes ONTAP that you can upgrade to depends on the version of Cloud Volumes ONTAP that you're currently running.

Current version Versions that you can directly upgrade to

9.14.0

9.14.1

9.13.1

9.14.1

9.14.0

9.13.0

9.13.1

9.12.1

9.13.1

9.13.0

9.12.0

9.12.1

9.11.1

9.12.1

9.12.0

9.11.0

9.11.1

9.10.1

9.11.1

9.11.0

9.10.0

9.10.1

9.9.1

9.10.1

9.10.0

9.9.0

9.9.1

9.8

9.9.1

9.7

9.8

9.6

9.7

9.5

9.6

9.4

9.5

9.3

9.4

9.2

9.3

9.1

9.2

9.0

9.1

8.3

9.0

Note the following:

  • The supported upgrade paths for Cloud Volumes ONTAP are different than they are for an on-premises ONTAP cluster.

  • If you upgrade by following the upgrade notifications that appear in a working environment, BlueXP will prompt you to upgrade to a release that follows these supported upgrade paths.

  • If you upgrade by placing an upgrade image at an HTTPS location, be sure to follow these supported upgrade paths.

  • In some cases, you might need to upgrade a few times to reach your target release.

    For example, if you're running version 9.8 and you want to upgrade to 9.10.1, you first need to upgrade to version 9.9.1 and then to 9.10.1.

Patch releases

Starting in January 2024, patch upgrades are only available in BlueXP if they are a patch release for the three latest versions of Cloud Volumes ONTAP. We use the latest GA release to determine the three latest versions to display in BlueXP. For example, if the current GA release is 9.13.1, patches for 9.11.1-9.13.1 appear in BlueXP. If you want to upgrade to a patch release for versions 9.11.1 or below, you will need to use the manual upgrade procedure by downloading the ONTAP image.

As a general rule for patch (P) releases, you can upgrade from one version release to any P-release of the current version you're running or the next version.

Here are a couple examples:

  • 9.13.0 > 9.13.1P15

  • 9.12.1 > 9.13.1P2

Reverting or downgrading

Reverting or downgrading Cloud Volumes ONTAP to a previous release is not supported.

Support registration

Cloud Volumes ONTAP must be registered with NetApp support in order to upgrade the software using any of the methods described on this page. This applies to both PAYGO and BYOL. You'll need to manually register PAYGO systems, while BYOL systems are registered by default.

Tip A system that isn't registered for support will still receive the software update notifications that appear in BlueXP when a new version is available. But you will need to register the system before you can upgrade the software.

Upgrades of the HA mediator

BlueXP also updates the mediator instance as needed during the Cloud Volumes ONTAP upgrade process.

Upgrades in AWS with c4, m4, and r4 EC2 instance types

Cloud Volumes ONTAP no longer supports the c4, m4, and r4 EC2 instance types. You can upgrade existing deployments to Cloud Volumes ONTAP versions 9.8-9.12.1 with these instance types. Before you upgrade we recommend that you change the instance type. If you can't change the instance type, you need to enable enhanced networking before you upgrade. Read the following sections to learn more about changing the instance type and enabling enhanced networking.

In Cloud Volumes ONTAP running versions 9.13.0 and above, you cannot upgrade with c4, m4, and r4 EC2 instance types. In this case, you need to reduce the number of disks and then change the instance type or deploy a new HA-pair configuration with the c5, m5, and r5 EC2 instance types and migrate the data.

Change the instance type

c4, m4, and r4 EC2 instance types allow for more disks per node than the c5, m5, and r5 EC2 instance types. If the disk count per node for the c4, m4, or r4 EC2 instance you're running is below the max disk allowance per node for c5, m5, and r5 instances, you can change the EC2 instance type to c5, m5, or r5.

Check disk and tiering limits by EC2 instance
Change the EC2 instance type for Cloud Volumes ONTAP

If you can't change the instance type, follow the steps in Enable enhanced networking.

Enable enhanced networking

To upgrade to Cloud Volumes ONTAP versions 9.8 and later, you must enable enhanced networking on the cluster running the c4, m4, or r4 instance type. To enable ENA, refer to the Knowledge Base article "How to enable Enhanced networking like SR-IOV or ENA on AWS Cloud Volumes ONTAP instances".

Prepare to upgrade

Before performing an upgrade, you must verify that your systems are ready and make any required configuration changes.

Plan for downtime

When you upgrade a single-node system, the upgrade process takes the system offline for up to 25 minutes, during which I/O is interrupted.

In many cases, upgrading an HA pair is nondisruptive and I/O is uninterrupted. During this nondisruptive upgrade process, each node is upgraded in tandem to continue serving I/O to clients.

Session-oriented protocols might cause adverse effects on clients and applications in certain areas during upgrades. For details, refer to ONTAP documentation

Verify that automatic giveback is still enabled

Automatic giveback must be enabled on a Cloud Volumes ONTAP HA pair (this is the default setting). If it isn't, then the operation will fail.

ONTAP 9 Documentation: Commands for configuring automatic giveback

Suspend SnapMirror transfers

If a Cloud Volumes ONTAP system has active SnapMirror relationships, it is best to suspend transfers before you update the Cloud Volumes ONTAP software. Suspending the transfers prevents SnapMirror failures. You must suspend the transfers from the destination system.

Note Even though BlueXP backup and recovery uses an implementation of SnapMirror to create backup files (called SnapMirror Cloud), backups do not need to be suspended when a system is upgraded.
About this task

These steps describe how to use System Manager for version 9.3 and later.

Steps

  1. Log in to System Manager from the destination system.

    You can log in to System Manager by pointing your web browser to the IP address of the cluster management LIF. You can find the IP address in the Cloud Volumes ONTAP working environment.

    Note The computer from which you are accessing BlueXP must have a network connection to Cloud Volumes ONTAP. For example, you might need to log in to BlueXP from a jump host that's in your cloud provider network.

  2. Click Protection > Relationships.

  3. Select the relationship and click Operations > Quiesce.

Verify that aggregates are online

Aggregates for Cloud Volumes ONTAP must be online before you update the software. Aggregates should be online in most configurations, but if they are not, then you should bring them online.

About this task

These steps describe how to use System Manager for version 9.3 and later.

Steps

  1. In the working environment, click the Aggregates tab.

  2. Under the aggregate title, click the ellipse button, and then select View Aggregate details.

    Screen shot: Shows the State field when you view information for an aggregate.

  3. If the aggregate is offline, use System Manager to bring the aggregate online:

    1. Click Storage > Aggregates & Disks > Aggregates.

    2. Select the aggregate, and then click More Actions > Status > Online.

Verify that all LIFs are on home ports

Before you upgrade, all LIFs must be on home ports. Refer to ONTAP documentation to verify that all LIFs are on home ports.

If an upgrade failure error occurs, refer to the Knowledge Base article "Cloud Volumes ONTAP upgrade fails".

Upgrade Cloud Volumes ONTAP

BlueXP notifies you when a new version is available for upgrade. You can start the upgrade process from this notification. For details, see Upgrade from BlueXP notifications.

Another way to perform software upgrades by using an image on an external URL. This option is helpful if BlueXP can't access the S3 bucket to upgrade the software or if you were provided with a patch. For details, see Upgrade from an image available at a URL.

Upgrade from BlueXP notifications

BlueXP displays a notification in Cloud Volumes ONTAP working environments when a new version of Cloud Volumes ONTAP is available:

Screen shot: Shows the New version available notification which displays in the Canvas page after you select a working environment.

You can start the upgrade process from this notification, which automates the process by obtaining the software image from an S3 bucket, installing the image, and then restarting the system.

Before you begin

BlueXP operations such as volume or aggregate creation must not be in progress on the Cloud Volumes ONTAP system.

Steps

  1. From the left navigation menu, select Storage > Canvas.

  2. Select a working environment.

    A notification appears in the Overview tab if a new version is available:

    A screenshot that shows the "Upgrade now!" link under the Overview tab.

  3. If a new version is available, click Upgrade Now!

    Note Before you can upgrade Cloud Volumes ONTAP through the BlueXP notification, you must have a NetApp Support Site account.

  4. In the Upgrade Cloud Volumes ONTAP page, read the EULA, and then select I read and approve the EULA.

  5. Click Upgrade.

    Note The Upgrade Cloud Volumes ONTAP page selects the latest available Cloud Volumes ONTAP version for upgrade by default. If available, older versions of Cloud Volumes ONTAP can instead be selected for your upgrade by clicking Select older versions.
    Refer to the Supported upgrade paths list for the appropriate upgrade path based on your current Cloud Volumes ONTAP version.

    A screenshot of the Upgrade Cloud Volumes ONTAP version page.

  6. To check the status of the upgrade, click the Settings icon and select Timeline.

Result

BlueXP starts the software upgrade. You can perform actions on the working environment when the software update is complete.

After you finish

If you suspended SnapMirror transfers, use System Manager to resume the transfers.

Upgrade from an image available at a URL

You can place the Cloud Volumes ONTAP software image on the Connector or on an HTTP server and then initiate the software upgrade from BlueXP. You might use this option if BlueXP can't access the S3 bucket to upgrade the software.

Before you begin

  • BlueXP operations such as volume or aggregate creation must not be in progress on the Cloud Volumes ONTAP system.

  • If you use HTTPS to host ONTAP images, the upgrade can fail due to SSL authentication issues, which are caused by missing certificates. The workaround is to generate and install a CA-signed certificate to be used for authentication between ONTAP and BlueXP.

    Go to the NetApp Knowledge Base to view step-by-step instructions:

    NetApp KB: How to configure BlueXP as an HTTPS server to host upgrade images

Steps

  1. Optional: Set up an HTTP server that can host the Cloud Volumes ONTAP software image.

    If you have a VPN connection to the virtual network, you can place the Cloud Volumes ONTAP software image on an HTTP server in your own network. Otherwise, you must place the file on an HTTP server in the cloud.

  2. If you use your own security group for Cloud Volumes ONTAP, ensure that the outbound rules allow HTTP connections so Cloud Volumes ONTAP can access the software image.

    Note The predefined Cloud Volumes ONTAP security group allows outbound HTTP connections by default.

  3. Obtain the software image from the NetApp Support Site.

  4. Copy the software image to a directory on the Connector or on an HTTP server from which the file will be served.

    Two paths are available. The correct path depends on your Connector version.

    • /opt/application/netapp/cloudmanager/docker_occm/data/ontap/images/

    • /opt/application/netapp/cloudmanager/ontap/images/

  5. From the working environment in BlueXP, click the …​ (ellipse icon), and then click Update Cloud Volumes ONTAP.

  6. On the Update Cloud Volumes ONTAP version page, enter the URL, and then click Change Image.

    If you copied the software image to the Connector in the path shown above, you would enter the following URL:

    http://<Connector-private-IP-address>/ontap/images/<image-file-name>

    Note In the URL, image-file-name must follow the format "cot.image.9.13.1P2.tgz".

  7. Click Proceed to confirm.

Result

BlueXP starts the software update. You can perform actions on the working environment once the software update is complete.

After you finish

If you suspended SnapMirror transfers, use System Manager to resume the transfers.

Fix download failures when using a Google Cloud NAT gateway

The Connector automatically downloads software updates for Cloud Volumes ONTAP. The download can fail if your configuration uses a Google Cloud NAT gateway. You can correct this issue by limiting the number of parts that the software image is divided into. This step must be completed by using the BlueXP API.

Step

  1. Submit a PUT request to /occm/config with the following JSON as body:

{
  "maxDownloadSessions": 32
}

The value for maxDownloadSessions can be 1 or any integer greater than 1. If the value is 1, then the downloaded image will not be divided.

Note that 32 is an example value. The value that you should use depends on your NAT configuration and the number of sessions that you can have simultaneously.

Learn more about the /occm/config API call.