NVIDIA NetQ 4.2 Release Notes
Download all 4.2 release notes as .xls4.2.0 Release Notes
Open Issues in 4.2.0
| Issue ID | Description | Affects | Fixed |
|---|---|---|---|
| 3739222 | The opta-check command does not properly validate if the required 16 CPU cores are present on the system for NetQ. The command only presents an error if there are fewer than 8 CPU cores detected. | 4.2.0-4.8.0 | 4.9.0 |
| 3442456 | When an event notification is resolved or acknowledged, the NetQ UI might display a duplicate event with the original notification content and timestamp. | 4.2.0-4.6.0 | 4.7.0-4.9.0 |
| 3157803 | The netq show commands to view MACs, IP addresses, neighbors, and routes might show a higher value compared to the corresponding entries in the NetQ UI. The netq show commands display additional values from the NetQ server or OPTA in addition to monitored devices in the NetQ inventory. | 4.2.0-4.3.0 | 4.4.0-4.9.0 |
| 3136898 | On switches running Cumulus Linux 5.2.0 and NetQ agent 4.2.0 or earlier, NetQ commands might fail and errors are logged to /var/log/netq-agent.log. To work around this issue, use NetQ agent version 4.3.0. | 4.2.0 | 4.3.0-4.9.0 |
| 3131311 | Sensor validation checks might still reflect a failure in NetQ after the sensor failure has recovered. | 4.2.0-4.3.0 | 4.4.0-4.9.0 |
| 3085064 | When you attempt to install NetQ on a device using LCM and configure the incorrect VRF, the installation will be reflected as successful but the switch will not be present in the inventory in the LCM UI. | 4.1.0-4.3.0 | 4.4.0-4.9.0 |
| 3085017 | When you hover over a device with WJH events in the flow analysis graph, the number of WJH packet drops in the event summary might display 0 drops. This is because the device did not detect any WJH events on the selected path. To view the WJH events, select different paths to display any WJH events for that device. | 4.2.0 | 4.3.0-4.9.0 |
| 3053143 | The MLAG Session card might not show all MLAG events. | 4.2.0-4.3.0 | 4.4.0-4.9.0 |
| 3047149 | When you reboot the OPTA, the NetQ validation summary might show an incorrect number of validations. This condition will resolve itself within an hour of the reboot. | 4.2.0 | 4.3.0-4.9.0 |
| 3015875 | NetQ trace might report incomplete route information when there are multiple default routes in a VRF in the path between the source and destination. | 4.1.0-4.4.1 | 4.5.0-4.9.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.9.0 |
Fixed Issues in 4.2.0
| Issue ID | Description | Affects |
|---|---|---|
| 3011307 | NetQ Agent: The NetQ Agent fails to start in Cumulus Linux on switches with ARM CPUs. The log files show the following message:systemd: netq-agent.service: Main process exited, code=exited, status=1/FAILURE | 4.1.1 |
| 2896825 | WJH monitoring fails to start with netq-agent on Cumulus Linux 5.0. To work around this issue, reinstall the netq-agent package and configure the netq agent to start monitoring:1. Add the gpg key for the repository:wget -qO - https://apps3.cumulusnetworks.com/setup/cumulus-apps-deb.pubkey | sudo apt-key add -2. Add the repository to /etc/apt/sources.list:echo ‘deb https://apps3.cumulusnetworks.com/repos/deb CumulusLinux-4 netq-latest’ | sudo tee -a /etc/apt/sources.list3. Reinstall the netq-agent package:sudo apt-get update && sudo apt-get install –reinstall netq-agent | 4.1.0-4.1.1 |
| 2885440 | After upgrading to NetQ 4.1.0, validation checks might show intermittent errors that are not valid while the validation application processess pending messages after upgrade. This condition will clear once all messages are processed. | 4.1.0-4.1.1 |
| 2843640 | In NetQ clustered environments, the network snapshot feature may fail. | 4.0.0-4.1.1 |
| 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 |
| 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 |