If you are using the current version of Cumulus NetQ, the content on this page may not be up to date. The current version of the documentation is available here. If you are redirected to the main page of the user guide, then this page may have been renamed; please search for it there.

NVIDIA NetQ 4.3 Release Notes

Download 4.3 Release Notes xls    Download all 4.3 release notes as .xls

4.3.0 Release Notes

Open Issues in 4.3.0

Issue IDDescriptionAffectsFixed
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-
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-
When you install NetQ onto your VM, the installation fails with the following messages:
05:57:33.023618: master-node-installer: Installed Debian …	[ FAILED ]————————————–ERROR: Failed to install the master node
This is due to an expired key in the installation tarball. For assistance working around this issue, contact NVIDIA support.
When you run the netq show opta-health command, it might fail and produce the following error:
ERROR: Expecting value: line 1 column 1 (char 0)
TLS versions 1.0 and 1.1 are enabled for the OPTA API Gateway listening on TCP port 32708. Only TLS versions 1.2 and 1.3 should be enabled.
In an OPTA clustered environment, NetQ agents might appear as rotten after upgrading to NetQ 4.3.0. To work around this issue, configure the spice: false parameter in /etc/netq/netq.yml.
Upgrading Cumulus Linux with NetQ LCM fails when you upgrade a switch with the MLAG primary role.
In some high scale environments, NetQ agents might appear as rotten during high load.
The NetQ agent does not collect VLAN information from WJH data. This has been resolved, however when you upgrade to a NetQ version with the fix, historical WJH data will not be displayed in the UI.4.3.0-
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-
Sensor validation checks might still reflect a failure in NetQ after the sensor failure has recovered.4.2.0-
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-
The MLAG Session card might not show all MLAG events.4.2.0-
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-
Sort functionality is disabled when the number of records exceeds 10,000 entries in a full-screen, tabular view.

Fixed Issues in 4.3.0

Issue IDDescriptionAffects
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
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
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
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