Upgrade Procedure

You are here:

Upgrade Procedure

This upgrade procedure applies to A10 Control deployed on virtual machines using VMware or KVM hypervisors. Ensure all the prerequisites are completed before proceeding. For more information, see Upgrade A10 Control .

Upgrade Methods

The upgrade can be performed in two ways, depending on your access preference:

Using Virtual Console (Hypervisor Access)

Log in to the A10 Control Virtual Machine console as super-admin user.
Run the following command to start the upgrade:
```
sudo /usr/bin/a10-control_upgrade.sh a10-control-X.X.X.XXX-upgrade.tar.gz
```
Replace the X.X.X.XXX in the filename with the actual version number of the upgrade package you downloaded. For example, if the upgrade package file name is a10-control-1.5.0.178-upgrade.tar.gz, run the following command:
```
sudo /usr/bin/a10-control_upgrade.sh a10-control-1.5.0.178-upgrade.tar.gz
```
Wait for the upgrade package to extract (untar process).

After extraction, the console prompts:
```
Press Y to proceed with the upgrade.
```
```
Press N to cancel the upgrade.
```
Press Y to continue with the upgrade.

Using SSH Session

Log in to the A10 Control Virtual Machine console through SSH as the super-admin user.
Start a new tmux session for the upgrade:
```
tmux new -s a10c-upgrade-session
```
Run the following command to start the upgrade:
```
sudo /usr/bin/a10-control_upgrade.sh a10-control-X.X.X.XXX-upgrade.tar.gz
```
Replace the X.X.X.XXX in the filename with the actual version number of the upgrade package you downloaded. For example, if the upgrade package file name is a10-control-1.5.0.178-upgrade.tar.gz, run the following command:
```
sudo /usr/bin/a10-control_upgrade.sh a10-control-1.5.0.178-upgrade.tar.gz
```
Wait for the upgrade package to extract.

After extraction, the console prompts:
```
Press Y to proceed with the upgrade.
```
```
Press N to cancel the upgrade.
```
To detach from tmux session without stopping the upgrade, press Ctrl+b, then d
If the SSH connection is interrupted or the tmux session is detached, reattach to tmux session to monitor the upgrade progress:
- Reconnect over SSH as super-admin user.
- Reattach to the running tmux session:
```
tmux attach -t a10c-upgrade-session
```
After the upgrade completes, follow any on-screen instructions.
Session Cleanup:
- If the upgrade does not require an immediate reboot, clean up the tmux session:
  - Detach from the session: Ctrl+b, then d
  - Remove the session:
```
tmux kill-session -t a10c-upgrade-session
```
- If the upgrade instructions require a reboot of the A10 Control Virtual Machine, do not remove the tmux session manually. Rebooting the Virtual Machine will automatically terminate the tmux session.

Monitor Logs

To monitor logs while the upgrade is in progress:

tail -f upgrade_controller_YYYY-MM-xxx:xx.log

It displays real-time progress updates from the controller.

The upgrade typically takes 30–60 minutes per node, depending on cluster size and available resources.

Verify Upgrade

To verify the upgrade:

After the upgrade is complete, review the installer logs at:
```
/opt/symphony-installer/logs
```
Confirm upgrade status:
- If successful, the console shows Upgrade Successful message and displays the vesrsion.
- If failed, review the console and installer logs, and contact A10 Networks Support Team.
Confirm that all services and clusters are healthy.

Verify that licenses are preserved across the upgrade.
If the setup includes ACOS devices being upgraded from 6.x to 7.x, check that a valid RHEL Support license is available and imported.

Reboot

A reboot is required after the upgrade to ensure all the features and services work seamlessly. After verifying the upgrade, reboot all nodes from the GUI.

To reboot all nodes from GUI see Reboot or Shut Down All Nodes (Cluster-Level) Through GUI.