Upgrade NetQ Appliances and Virtual Machines
The first step in upgrading your NetQ installation to NetQ 3.3.1 is to upgrade your NetQ appliances or VMs. This topic describes how to upgrade this for both on-premises and remote deployments.
Prepare for Upgrade
Three important steps are required to prepare for upgrade of your NetQ Platform:
- Download the necessary software tarballs
- Update the Debian packages on physical server and VMs
- For Cloud VM deployments, increase the root volume disk image size
Optionally, you can choose to back up your NetQ Data before performing the upgrade.
To complete the preparation:
-
For on-premises deployments only, optionally back up your NetQ data. Refer to Back Up and Restore NetQ.
-
Download the relevant software.
Access to the software downloads depends on whether you were an existing customer before September 1, 2020 or whether you are a newer customer. Please follow the instructions accordingly.
Existing customer who has downloaded NetQ software before September 1, 2020:- On the MyMellanox Downloads page, select NetQ from the Software -> Cumulus Software list.
- Click 3.3 from the Version list, and then select 3.3.1 from the submenu.
- Select the relevant software from the HyperVisor/Platform list:
If you are upgrading NetQ Platform software for a NetQ On-premises Appliance or VM, select Appliance to download the NetQ-3.3.1.tgz file. If you are upgrading NetQ Collector software for a NetQ Cloud Appliance or VM, select Appliance (Cloud) to download the NetQ-3.3.1-opta.tgz file.
- Scroll down to view the image, and click Download on the on-premises or cloud NetQ Appliance image.
You can ignore the note on the image card because, unlike during installation, you do not need to download the bootstrap file for an upgrade.
- On the My Mellanox support page, log in to your account. If needed create a new account and then log in.
Your username is based on your Email address. For example, user1@domain.com.mlnx. - Open the Downloads menu.
- Click Software.
- Open the Cumulus Software option.
- Click All downloads next to Cumulus NetQ.
- Select 3.3.1 from the NetQ Version dropdown.
- Select the relevant software from the HyperVisor/Platform list:
If you are upgrading NetQ Platform software for a NetQ On-premises Appliance or VM, select Appliance to download the NetQ-3.3.1.tgz file. If you are upgrading NetQ Collector software for a NetQ Cloud Appliance or VM, select Appliance (Cloud) to download the NetQ-3.3.1-opta.tgz file.
- Click Show Download.
- Verify this is the correct image, then click Download.
Ignore the Firmware, Documentation, and More files options as these do not apply to NetQ.
-
Copy the file to the
/mnt/installables/
directory on your appliance or VM. -
Update
/etc/apt/sources.list.d/cumulus-netq.list
to netq-3.3 as follows:cat /etc/apt/sources.list.d/cumulus-netq.list deb [arch=amd64] https://apps3.cumulusnetworks.com/repos/deb bionic netq-3.3
-
Update the NetQ
debian
packages.cumulus@<hostname>:~$ sudo apt-get update Get:1 http://apps3.cumulusnetworks.com/repos/deb bionic InRelease [13.8 kB] Get:2 http://apps3.cumulusnetworks.com/repos/deb bionic/netq-3.3 amd64 Packages [758 B] Hit:3 http://archive.ubuntu.com/ubuntu bionic InRelease Get:4 http://security.ubuntu.com/ubuntu bionic-security InRelease [88.7 kB] Get:5 http://archive.ubuntu.com/ubuntu bionic-updates InRelease [88.7 kB] ... Get:24 http://archive.ubuntu.com/ubuntu bionic-backports/universe Translation-en [1900 B] Fetched 4651 kB in 3s (1605 kB/s) 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 (3.3.1-ub18.04u33~1614767175.886b337) ... ... Unpacking netq-apps (3.3.1-ub18.04u33~1614767175.886b337) ... Setting up netq-apps (3.3.1-ub18.04u33~1614767175.886b337) ... Setting up netq-agent (3.3.1-ub18.04u33~1614767175.886b337) ... Processing triggers for rsyslog (8.32.0-1ubuntu4) ... Processing triggers for man-db (2.8.3-2ubuntu0.1) ...
-
If you are upgrading NetQ as a VM in the cloud from version 3.1.0 or earlier, you must increase the root volume disk image size for proper operation of the lifecycle management feature.
-
Check the size of the existing disk in the VM to confirm it is 32 GB. In this example, the number of 1 MB blocks is 31583, or 32 GB.
cumulus@netq-310-cloud:~$ df -hm / Filesystem 1M-blocks Used Available Use% Mounted on /dev/sda1 31583 4771 26797 16% /
-
Shutdown the VM.
- After the VM is shutdown (Shut down button is grayed out), click Edit.
- In the Edit settings > Virtual Hardware > Hard disk field, change the 32 to 64 on the server hosting the VM.
-
Click Save.
-
Start the VM, log back in.
-
From step 1 we know the name of the root disk is /dev/sda1. Use that to run the following commands on the partition.
cumulus@netq-310-cloud:~$ sudo growpart /dev/sda 1 CHANGED: partition=1 start=227328 old: size=66881503 end=67108831 new: size=133990367,end=134217695 cumulus@netq-310-cloud:~$ sudo resize2fs /dev/sda1 resize2fs 1.44.1 (24-Mar-2018) Filesystem at /dev/sda1 is mounted on /; on-line resizing required old_desc_blocks = 4, new_desc_blocks = 8 The filesystem on /dev/sda1 is now 16748795 (4k) blocks long.
-
Verify the disk is now configured with 64 GB. In this example, the number of 1 MB blocks is now 63341, or 64 GB.
cumulus@netq-310-cloud:~$ df -hm / Filesystem 1M-blocks Used Available Use% Mounted on /dev/sda1 63341 4772 58554 8% /
-
Check the size of the existing hard disk in the VM to confirm it is 32 GB. In this example, the number of 1 MB blocks is 31583, or 32 GB.
cumulus@netq-310-cloud:~$ df -hm / Filesystem 1M-blocks Used Available Use% Mounted on /dev/vda1 31583 1192 30375 4% /
-
Shutdown the VM.
-
Check the size of the existing disk on the server hosting the VM to confirm it is 32 GB. In this example, the size is shown in the virtual size field.
root@server:/var/lib/libvirt/images# qemu-img info netq-3.1.0-ubuntu-18.04-tscloud-qemu.qcow2 image: netq-3.1.0-ubuntu-18.04-tscloud-qemu.qcow2 file format: qcow2 virtual size: 32G (34359738368 bytes) disk size: 1.3G cluster_size: 65536 Format specific information: compat: 1.1 lazy refcounts: false refcount bits: 16 corrupt: false
-
Add 32 GB to the image.
root@server:/var/lib/libvirt/images# qemu-img resize netq-3.1.0-ubuntu-18.04-tscloud-qemu.qcow2 +32G Image resized.
-
Verify the change.
root@server:/var/lib/libvirt/images# qemu-img info netq-3.1.0-ubuntu-18.04-tscloud-qemu.qcow2 image: netq-3.1.0-ubuntu-18.04-tscloud-qemu.qcow2 file format: qcow2 virtual size: 64G (68719476736 bytes) disk size: 1.3G cluster_size: 65536 Format specific information: compat: 1.1 lazy refcounts: false refcount bits: 16 corrupt: false
-
Start the VM and log back in.
-
From step 1 we know the name of the root disk is /dev/vda 1. Use that to run the following commands on the partition.
cumulus@netq-310-cloud:~$ sudo growpart /dev/vda 1 CHANGED: partition=1 start=227328 old: size=66881503 end=67108831 new: size=133990367,end=134217695 cumulus@netq-310-cloud:~$ sudo resize2fs /dev/vda1 resize2fs 1.44.1 (24-Mar-2018) Filesystem at /dev/vda1 is mounted on /; on-line resizing required old_desc_blocks = 4, new_desc_blocks = 8 The filesystem on /dev/vda1 is now 16748795 (4k) blocks long.
-
Verify the disk is now configured with 64 GB. In this example, the number of 1 MB blocks is now 63341, or 64 GB.
cumulus@netq-310-cloud:~$ df -hm / Filesystem 1M-blocks Used Available Use% Mounted on /dev/vda1 63341 1193 62132 2% /
-
You can now upgrade your appliance using the NetQ Admin UI, in the next section. Alternately, you can upgrade using the CLI here: Upgrade Your Platform Using the NetQ CLI.
Upgrade Older Platforms Using the NetQ Admin UI
If you are upgrading from NetQ 3.1.1 or earlier, after completing the preparation steps, upgrading your NetQ On-premises or Cloud Appliances or VMs is simple using the Admin UI.
To upgrade your NetQ software:
-
Run the bootstrap CLI to upgrade the Admin UI application.
cumulus@<hostname>:~$ netq bootstrap master upgrade /mnt/installables/NetQ-3.3.1.tgz 2020-04-28 15:39:37.016710: master-node-installer: Extracting tarball /mnt/installables/NetQ-3.3.1.tgz 2020-04-28 15:44:48.188658: master-node-installer: Upgrading NetQ Admin container 2020-04-28 15:47:35.667579: master-node-installer: Removing old images ----------------------------------------------- Successfully bootstrap-upgraded the master node
netq bootstrap master upgrade /mnt/installables/NetQ-3.3.1-opta.tgz
-
Open the Admin UI by entering http://<hostname-or-ipaddress>:8443 in your browser address field.
-
Enter your NetQ credentials to enter the application.
The default username is admin and the default password in admin.
-
Click Upgrade.
-
Enter NetQ-3.3.1.tgz or NetQ-3.3.1-opta.tgz and click .
The is only visible after you enter your tar file information.
-
Monitor the progress. Click to monitor each step in the jobs.
The following example is for an on-premises upgrade. The jobs for a cloud upgrade are slightly different.
-
When it completes, click to be returned to the Health dashboard.
Upgrade Your Platform Using the NetQ CLI
After completing the preparation steps, upgrading your NetQ On-premises/Cloud Appliance(s) or VMs is simple using the NetQ CLI.
To upgrade:
- Run the appropriate
netq upgrade
command.
netq upgrade bundle /mnt/installables/NetQ-3.3.1.tgz
netq upgrade bundle /mnt/installables/NetQ-3.3.1-opta.tgz
-
After the upgrade completes, confirm the upgrade was successful.
cumulus@<hostname>:~$ cat /etc/app-release BOOTSTRAP_VERSION=3.3.1 APPLIANCE_MANIFEST_HASH=74ac3017d5 APPLIANCE_VERSION=3.3.1