Upgrade NetQ Virtual Machines
This page describes how to upgrade your NetQ virtual machines. Note that the upgrade instructions vary depending on NetQ version you’re currently running.
For deployments running:
- 4.11, 4.10.1: upgrade directly to NetQ 4.12
- 4.10.0 or earlier: back up your NetQ data and perform a new installation
During the upgrade process, NetQ will be temporarily unavailable.
Before You Upgrade
- Verify that Kubernetes is running and the admin app is up:
cumulus@masternode:~$ /home/cumulus# kubectl get pods|grep admin
netq-app-admin-masternode 1/1 Running 0 15m
If the output of this command displays errors or returns an empty response, you will not be able to upgrade NetQ. Try waiting and then re-run the command. If after several attempts the command continues to fail, reset the NetQ server with netq bootstrap reset keep-db
and perform a fresh installation of the tarball with the appropriate netq install command for your deployment type. For more information, refer to Troubleshoot NetQ Installation and Upgrade Issues.
- Back up your NetQ data. This is an optional step for on-premises deployments. NVIDIA automatically creates backups for NetQ cloud deployments.
Update NetQ Debian Packages
Update
/etc/apt/sources.list.d/cumulus-netq.list
to netq-4.12:cat /etc/apt/sources.list.d/cumulus-netq.list deb [arch=amd64] https://apps3.cumulusnetworks.com/repos/deb focal netq-4.12
Update the NetQ
debian
packages. In cluster deployments, update the packages on the master and all worker nodes:cumulus@<hostname>:~$ wget -qO - https://apps3.cumulusnetworks.com/setup/cumulus-apps-deb.pubkey | sudo apt-key add cumulus@<hostname>:~$ sudo apt-get update Get:1 https://apps3.cumulusnetworks.com/repos/deb focal InRelease [13.8 kB] Get:2 https://apps3.cumulusnetworks.com/repos/deb focal/netq-4.12 amd64 Packages [758 B] Hit:3 http://archive.ubuntu.com/ubuntu focal InRelease Get:4 http://security.ubuntu.com/ubuntu focal-security InRelease [88.7 kB] Get:5 http://archive.ubuntu.com/ubuntu focal-updates InRelease [88.7 kB] ... Reading package lists... Done
cumulus@<hostname>:~$ sudo apt-get install -y netq-agent netq-apps Reading package lists... Done Building dependency tree Reading state information... Done ... The following NEW packages will be installed: netq-agent netq-apps ... Fetched 39.8 MB in 3s (13.5 MB/s) ... Unpacking netq-agent (4.12.0-ub20.04u49~1731404061.ffa541ea6) ... ... Unpacking netq-apps (4.12.0-ub20.04u49~1731404061.ffa541ea6) ... Setting up netq-apps (4.12.0-ub20.04u49~1731404061.ffa541ea6) ... Setting up netq-agent (4.12.0-ub20.04u49~1731404061.ffa541ea6) ... Processing triggers for rsyslog (8.32.0-1ubuntu4) ... Processing triggers for man-db (2.8.3-2ubuntu0.1) ...
Download the Upgrade Software
Download the upgrade tarball.
- On the NVIDIA Application Hub, log in to your account.
- Select NVIDIA Licensing Portal.
- Select Software Downloads from the menu.
- Click Product Family and select NetQ.
- Select the relevant software for your hypervisor:
If you are upgrading NetQ software for a NetQ on-premises VM, select NetQ SW 4.12.0 Appliance to download the NetQ-4.12.0.tgz file. If you are upgrading NetQ software for a NetQ cloud VM, select NetQ SW 4.12.0 Appliance Cloud to download the NetQ-4.12.0-opta.tgz file. - If prompted, read the license agreement and proceed with the download.
For enterprise customers, if you do not see a link to the NVIDIA Licensing Portal on the NVIDIA Application Hub, contact NVIDIA support.
For NVIDIA employees, download NetQ directly from the NVIDIA Licensing Portal.
- On the NVIDIA Application Hub, log in to your account.
Copy the tarball to the
/mnt/installables/
directory on your NetQ VM.
Run the Upgrade
Perform the following steps using the cumulus
user account.
Pre-installation Checks
Verify the following items before upgrading NetQ.
Confirm your VM is configured with 16 vCPUs. If your VM is configured with fewer than 16 vCPUs, power off your VM, reconfigure your hypervisor to allocate 16 vCPUs, then power the VM on before proceeding. For cluster deployments, verify these requirements on each node in the cluster.
Check if there is sufficient disk space:
cumulus@<hostname>:~$ df -h /
Filesystem Size Used Avail Use% Mounted on
/dev/sda1 248G 70G 179G 28% /
cumulus@netq-appliance:~$
NVIDIA recommends proceeding with the installation only if the Use%
is less than 70%. You can delete previous software tarballs in the /mnt/installables/
directory to regain some space. If you cannot decrease disk usage to under 70%, contact the NVIDIA support team.
Confirm that the NetQ CLI is properly configured. The
netq show agents
command should complete successfully and display agent status.Ensure that the necessary ports are open according to your deployment model.
Upgrade Using the NetQ CLI
- Run the appropriate commands for your deployment type:
cumulus@<hostname>:~$ netq upgrade bundle /mnt/installables/NetQ-4.12.0.tgz
If this step fails for any reason, run the netq bootstrap reset keep-db
command and perform a fresh installation of the tarball with the netq install standalone full command.
cumulus@<hostname>:~$ netq upgrade bundle /mnt/installables/NetQ-4.12.0.tgz
If this step fails for any reason, run the netq bootstrap reset keep-db
command and perform a fresh installation of the tarball with the netq install cluster full command.
cumulus@<hostname>:~$ netq upgrade bundle /mnt/installables/NetQ-4.12.0-opta.tgz
If this step fails for any reason, run the netq bootstrap reset keep-db
command and perform a fresh installation of the tarball with the netq install opta standalone full command.
Run the netq upgrade
command, specifying the current version’s tarball and your cluster’s virtual IP address. The virtual IP address must be:
- An unused IP address allocated from the same subnet assigned to the default interface for your master and worker nodes. The default interface is the interface you specified in the
netq install
command. - A different IP address than the primary IP assigned to the default interface.
cumulus@<hostname>:~$ netq upgrade bundle /mnt/installables/NetQ-4.12.0-opta.tgz cluster-vip <vip-ip>
If you are upgrading from a NetQ 4.8 or later high availability, cloud cluster with a virtual IP address, you do not need to include the cluster-vip
option in the upgrade command. Specifying a virtual IP address that is different from the virtual IP address used during the installation process will cause the upgrade to fail.
If this step fails for any reason, run the netq bootstrap reset keep-db
command and perform a fresh installation of the tarball with the netq install opta cluster full command.
- Confirm the upgrade was successful:
```
cumulus@<hostname>:~$ cat /etc/app-release
BOOTSTRAP_VERSION=4.12.0
APPLIANCE_MANIFEST_HASH=c664236fb1d732b3633ab83662575c35f397bc6ac3a9970632523827097c8415
APPLIANCE_VERSION=4.12.0
APPLIANCE_NAME=NetQ On-premises Appliance
```
```
cumulus@<hostname>:~$ cat /etc/app-release
BOOTSTRAP_VERSION=4.12.0
APPLIANCE_MANIFEST_HASH=370ffbe3195aa1c4cc969668441b124e7714f7eaa980962ff4cc438fcec31b87
APPLIANCE_VERSION=4.12.0
APPLIANCE_NAME=NetQ cloud Appliance
```