NVIDIA Cumulus NetQ 4.0 Release Notes
Download all 4.0 release notes as .xls
4.0.1 Release Notes
Open Issues in 4.0.1
| Issue ID | Description | Affects | Fixed |
|---|---|---|---|
| 2893000 |
CVE-2021-44228: Apache Log4j2 <=2.14.1 JNDI features used in configuration, log messages, and parameters do not protect against attacker controlled LDAP and other JNDI related endpoints. | 2.4.0-4.0.1 | 4.1.0-4.12.0 |
| 2843640 |
In NetQ clustered environments, the network snapshot feature may fail. | 4.0.0-4.1.1 | 4.2.0-4.12.0 |
| 2817749 |
If you configure an event suppression rule with is_active false, the event will no longer be displayed with the netq show events-config command. |
4.0.1-4.2.0 | 4.3.0-4.12.0 |
| 2815596 |
The NetQ Cloud VM for KVM hypervisors installer and opta-check fail because the minimum disk requirements do not meet the default image settings. To work around this issue, increase the disk space from 32GB to 64GB before you run the netq bootstrap command1. 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-401-cloud:~$ df -hm / Filesystem 1M-blocks Used Available Use% Mounted on /dev/vda1 31583 1192 30375 4% /2. Shutdown the VM 3. Check the size of the existing disk on the server hosting the VM to confirm it is 32 GB. In this example, the size appears in the virtual size field: root@server:/var/lib/libvirt/images# qemu-img info netq-4.0.1-ubuntu-18.04-tscloud-qemu.qcow2 image: netq-4.0.1-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: false4. Add 32 GB to the image: root@server:/var/lib/libvirt/images# qemu-img resize netq-4.0.1-ubuntu-18.04-tscloud-qemu.qcow2 +32G Image resized.5. Verify the change root@server:/var/lib/libvirt/images# qemu-img info netq-4.0.1-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: false6. Start the VM and log back in 7. Run the following commands on the partition, referencing the filesystem /dev/vda1 obtained in step 1: cumulus@netq-401-cloud:~$ sudo growpart /dev/vda 1 CHANGED: partition=1 start=227328 old: size=66881503 end=67108831 new: size=133990367,end=134217695 cumulus@netq-401-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.8. 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-401-cloud:~$ df -hm / Filesystem 1M-blocks Used Available Use% Mounted on /dev/vda1 63341 1193 62132 2% / |
4.0.1-4.1.1 | 4.2.0-4.12.0 |
| 2711101 |
When RoCE (RDMA over Converged Ethernet) data collection is enabled in Cumulus Linux 4.3.z and 4.4.z, you can experience high dual uplink convergence times To work around this issue, disable RoCE monitoring:1. Edit ‘/etc/netq/commands/cl4-netq-commands.yml’ and comment out the following lines: #- period: “60” # key: “roce” # isactive: true # command: “/usr/lib/cumulus/mlxcmd –json roce counters” # parser: “local"2. Delete the ‘/var/run/netq/netq_commands.yml’ file: $ sudo rm /var/run/netq/netq_commands.yml3. Restart the NetQ agent: $ netq config agent restart |
4.0.0-4.1.1 | 4.2.0-4.12.0 |
| 2690469 |
While upgrading an on-premises deployment from version 2.4.x to 3.x.y then to 4.x, the upgrade fails during the NetQ application stage To work around this issue, run the following command on the NetQ telemetry server, then start the upgrade again:‘netq install opta activate-job config-key EhVuZXRxLWVuZHBvaW50LWdhdGV3YXkYsagDIiw3T2sweW9kR3Y4Wk9sTHU3MkwrQTRjNkhhQkU3bVpBNVlZVjEvWWgyZGJBPQ==’ |
3.2.1-4.0.1 | 4.1.0-4.12.0 |
Fixed Issues in 4.0.1
| Issue ID | Description | Affects |
|---|
4.0.0 Release Notes
Open Issues in 4.0.0
| Issue ID | Description | Affects | Fixed |
|---|---|---|---|
| 2893000 |
CVE-2021-44228: Apache Log4j2 <=2.14.1 JNDI features used in configuration, log messages, and parameters do not protect against attacker controlled LDAP and other JNDI related endpoints. | 2.4.0-4.0.1 | 4.1.0-4.12.0 |
| 2843640 |
In NetQ clustered environments, the network snapshot feature may fail. | 4.0.0-4.1.1 | 4.2.0-4.12.0 |
| 2711101 |
When RoCE (RDMA over Converged Ethernet) data collection is enabled in Cumulus Linux 4.3.z and 4.4.z, you can experience high dual uplink convergence times To work around this issue, disable RoCE monitoring:1. Edit ‘/etc/netq/commands/cl4-netq-commands.yml’ and comment out the following lines: #- period: “60” # key: “roce” # isactive: true # command: “/usr/lib/cumulus/mlxcmd –json roce counters” # parser: “local"2. Delete the ‘/var/run/netq/netq_commands.yml’ file: $ sudo rm /var/run/netq/netq_commands.yml3. Restart the NetQ agent: $ netq config agent restart |
4.0.0-4.1.1 | 4.2.0-4.12.0 |
| 2690469 |
While upgrading an on-premises deployment from version 2.4.x to 3.x.y then to 4.x, the upgrade fails during the NetQ application stage To work around this issue, run the following command on the NetQ telemetry server, then start the upgrade again:‘netq install opta activate-job config-key EhVuZXRxLWVuZHBvaW50LWdhdGV3YXkYsagDIiw3T2sweW9kR3Y4Wk9sTHU3MkwrQTRjNkhhQkU3bVpBNVlZVjEvWWgyZGJBPQ==’ |
3.2.1-4.0.1 | 4.1.0-4.12.0 |
Fixed Issues in 4.0.0
| Issue ID | Description | Affects |
|---|---|---|
| 2611898 |
Fixed an issue where deleting a snapshot does not remove the snapshot card from the workbench. However, the workbench might refresh before the deleted snapshot’s card is removed. During the refresh, you may notice a brief flashing. This is expected behavior and you can safely ignore the flashing. | |
| 2556754 |
netq-agent installed on Cumulus Linux might slowly leak memory during sustained layer two network events at high scale. | 3.3.0-3.3.1 |
| 2555197 |
NetQ CLI: Occasionally, when a command response contains a large number of objects to be displayed the NetQ CLI does not display all results in the console. When this occurs, view all results using the json format option. |
3.3.0-3.3.1 |
| 2553453 |
The netqd daemon logs a traceback to /var/log/netqd.log when the OPTA server is unreachable and netq show commands are run. |
3.1.0-3.3.1 |
| 2549319 |
NetQ UI: The legend and segment colors on Switches and Upgrade History card graphs sometimes do not match. These cards appear on the lifecycle management dashboard (Manage Switch Assets view). Hover over graph to view the correct values. | 3.0.0-3.3.1 |