NVIDIA NetQ 4.5 Release Notes

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

4.5.0 Release Notes

Open Issues in 4.5.0

Issue IDDescriptionAffectsFixed
When you configure a new access profile with SSH authentication using the CLI, the command fails with the following log message:
Expecting value: line 1 column 1 (char 0) 
To work around this issue, use the NetQ UI to configure the access profile.
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.4.3.0-4.5.0
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.4.3.0-4.5.0
Upgrading Cumulus Linux with NetQ LCM fails when you upgrade a switch with the MLAG primary role.4.3.0-4.5.0
In some high scale environments, NetQ agents might appear as rotten during high load.4.3.0-4.5.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-4.5.0
Sensor validation checks might still reflect a failure in NetQ after the sensor failure has recovered.4.2.0-4.5.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-4.5.0
The MLAG Session card might not show all MLAG events.4.2.0-4.5.0
EVPN Validation Type 2 checks might show false Duplicate MAC events for MAC addresses that are not duplicated. An example of this is shown below:
EVPN Type 2 Test details:
Hostname Peer Name Peer Hostname Reason Last Changed
—————– —————– —————– ——————————————— ————————-
torc-11 - - Duplicate Mac 00:02:00:00:00:55 VLAN 1249 at Sun Dec 5 18:26:14 2021
torc-21:vx-282 and torc-11:peerlink-3
When a NetQ agent sends messages with validation check data, there might be a delay of up to 120 seconds before the new data is displayed in streaming validation checks.4.2.0-4.5.0
Sort functionality is disabled when the number of records exceeds 10,000 entries in a full-screen, tabular view.4.3.0-4.5.0

Fixed Issues in 4.5.0

Issue IDDescriptionAffects
When you perform a netq trace between two hosts, the following message might be printed in the output even when the trace is successful:
argument of type ‘NoneType’ is not iterable
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)
When you back up NetQ data with the backuprestore.sh script, the operation fails with the following log messages:
Failed to clear all earlier snapshot for keyspace:master. Exiting!command terminated with exit code 1Failed to execute /opt/backuprestore/createbackup.sh script on cassandra pod
Failed to proceed ahead with backup procedure. Exiting !
Contact NVIDIA support for assistance performing a backup.
When a NetQ agent sends your NetQ server or OPTA an unexpectedly large number for switch interface counters, netq check and netq show commands might fail with the following message:
local variable ‘url’ referenced before assignment
When you start the netq-agent service, the WJH service is enabled by default. However, when you run the netq config show agent wjh command, the output might reflect the WJH service as disabled.
When you attempt to reinstall NetQ on a server with an existing NetQ installation using the netq install [opta] command, the installation fails with the following messages:
master-node-installer: Plugged in release bundle …    [ FAILED ]————————————–ERROR: Failed to install the master nodeCommand ‘['/usr/bin/dpkg’, ‘-i’, ‘']’ returned non-zero exit status 2
To work around this issue, run the netq bootstrap reset command before attempting to reinstall NetQ on your existing server.
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-4.4.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-4.4.0