Upgrading Harmony Controller deployed on Custom Resources

Two configurations are supported in this case.

  • 1-node upgrade
    Upgrade on one physical or virtual machine.
  • 3-node upgrade
    Upgrade on three physical or virtual machines.

Upgrading Harmony Controller deployed on Single Node

In this case Harmony Controller is upgraded only on one physical or virtual machine.

Before You Begin

  1. You need to have an existing installation of A10 Harmony Controller version 4.0.0 or 4.0.1.
  2. You must have root privilege to run the upgrade_harmony_controller.sh script.

Keep following information handy as this will be needed during the upgrade process:

  1. Internal Subnet
    Assign an internal IP address range of 256 IP address to be used for all internal networks.

Download Upgrade Bundle and Other Packages

Upgrade script bundle needs to be downloaded from the share file location provided in the email from A10. The sharefile location contains Release Notes and Getting Started guide for the requested version of software. Please read them carefully as the information (options, requirements, compatibility etc.) specified in Getting Started guide take precedence over the information provided in this documentation.

Required Docker images and other packages also need to be downloaded and placed in the NodeZero before running the upgrade script. To avoid running out of space during upgrade, the downloaded files should be kept in the same storage volume where the upgrade is planned. Download location is available in Getting Started Guide that is at the same place where the installer package is.

Upgrade Harmony Controller Software

Run the following commands to unpack upgrade script bundle and extract the script:

$ tar -zxvf HarmonyController-4.1.0p1-upgrade.tar.gz
$ cd upgrade_package/

Run the following command for upgrading the controller software:

$ ./upgrade_harmony_controller.sh

The script will ask questions about the required information.

Note: Harmony Controller services will be unavailable during upgrade. It may take about 90 minutes. However, application traffic will not be impacted.

It is recommended to contact the A10 Customer Support in case of any issues during upgrade.

Next Steps

  • If not already done, configure SSL certificates for FQDN and email server information using A10 Harmony Controller Operator Console in the Certificate section under Configuration Management.
  • FQDN should be mapped to NodeZero IP address.
  • Configure Network Time Protocol (NTP) using A10 Harmony Controller Operator Console in the Network Time Protocol section under Configuration Management.
  • Setup scripts for transferring scheduled backup files to external storage as described in maintenance information.

Upgrading Harmony Controller deployed on Three Nodes

In this case Harmony Controller is upgraded on three physical or virtual machines.

Before You Begin

  1. You need to have an existing installation of A10 Harmony Controller version 4.0.0 or 4.0.1.
  2. You must have root privilege to run the upgrade_harmony_controller.sh script.

With this upgrade, the concept of Master node will be removed and all three nodes will become equal. Now they will be called nodezero, nodeone and nodetwo in a 3 node controller deployment.

Keep following information handy as this will be needed during the upgrade process:

  1. Floating IP Address

    A floating IP address is assigned to the elected master node. In case this node fails, the floating IP address is automatically moved to the next elected master node. All external communication happens through the floating IP address. This IP address must be an unused IP address in the same subnet as nodes.

    Note: This feature is not available in cloud environments (AWS, Azure, GCP, OpenStack, etc.).

  2. IP address of NodeZero

    This IP address is assigned to the NodeZero after it is created and note that the IP address cannot be changed.

  3. Internal Subnet

    Assign an internal IP address range of 256 IP address to be used for all internal networks.

Download Upgrade Bundle and Other Packages

Upgrade script bundle needs to be downloaded from the share file location provided in the email from A10. The sharefile location contains Release Notes and Getting Started guide for the requested version of software. Please read them carefully as the information (options, requirements, compatibility etc.) specified in Getting Started guide take precedence over the information provided in this documentation.

Required Docker images and other packages also need to be downloaded and placed in the NodeZero before running the upgrade script. To avoid running out of space during upgrade, the downloaded files should be kept in the same storage volume where the upgrade is planned. Download location is available in Getting Started Guide that is at the same place where the installer package is.

Upgrade Harmony Controller Software

Run the following commands to unpack upgrade script bundle and extract the script:

$ tar -zxvf HarmonyController-4.1.0p1-upgrade.tar.gz
$ cd upgrade_package/

Run the following command for upgrading the controller software:

$ ./upgrade_harmony_controller.sh

The script will ask questions about the required information.

Note: Harmony Controller services will be unavailable during upgrade. It may take about 90 minutes. However, application traffic will not be impacted.

It is recommended to contact the A10 Customer Support in case of any issues during upgrade.

Next Steps

  • If not already done, configure SSL certificates for FQDN and email server information using A10 Harmony Controller Operator Console in the Certificate section under Configuration Management.
  • FQDN should be mapped to NodeZero IP address in cloud environments (AWS, Azure, GCP, OpenStack, etc.) and mapped to floating IP address in non-cloud environment.
  • Configure Network Time Protocol (NTP) using A10 Harmony Controller Operator Console in the Network Time Protocol section under Configuration Management.
  • Setup scripts for transferring scheduled backup files to external storage as described in maintenance information.