NVIDIA NetQ 5.1 Release Notes
Download all 5.1 release notes as .xls
5.1.0 Release Notes
Open Issues in 5.1.0
| Issue ID | Description | Affects | Fixed |
|---|---|---|---|
| 4854041 |
When you upgrade a NetQ for NVLink and Ethernet deployment using the data backup and restoration workflow, NetQ does not preserve NVLink data. | 5.1.0 | |
| 4850991 |
The NetQ NVLink Swagger REST API enforces a minimum telemetry collection interval of 30 seconds, but values below 30 seconds are accepted without being flagged as invalid in the Swagger interface. | 5.1.0 | |
| 4845405 |
NetQ does not support performing a backup on version 5.1.0 and restoring it to the same version (5.1.0). | 5.1.0 | |
| 4839716 |
You cannot perform lifecycle management operations immediately after backing up an HA scale cluster deployment. To work around this issue, wait several hours before initiating LCM operations. | 5.1.0 | |
| 4794266 |
Power sensor (PSU) events might show inconsistent sensor names. Additionally, NetQ might not generate PSU events reliably. | 5.1.0 | |
| 4784336 |
The NetQ for NVLink deployment option is not supported in air-gapped environments. | 5.0.0-5.1.0 | |
| 4687477 |
When you run a validation against a group of devices with specific labels, NetQ ignores any pre-configured filters. | 5.0.0-5.1.0 | |
| 4681581 |
The netq bootstrap reset purge-db command might take up to 60 minutes to complete on Base Command Manager scale deployments. |
5.0.0-5.1.0 | |
| 4399074 |
When connecting a switch to NMX-T or NMX-C through the service registration workflow, use either the IP address or the hostname. Using both creates duplicate registrations, and the operation does not fail as expected. | 5.0.0-5.1.0 | |
| 4100882 |
When you attempt to export a file that is larger than 200MB, your browser might crash or otherwise prevent you from exporting the file. To work around this issue, use filters in the UI to decrease the size of the dataset that you intend to export. | 4.12.0-4.15.1, 5.0.0-5.1.0 |
Fixed Issues in 5.1.0
| Issue ID | Description | Affects |
|---|---|---|
| 4786996 |
To use lifecycle management in NMC or BCM environments, you must edit the master node IP address in the configuration manager to match the cluster’s head node IP address. Use the kubectl edit cm -n netq-eth netq-master-node-ip command to edit the configuration. In the configuration file, change the data/master_node field to the cluster’s head node IP address. |
5.0.0 |
| 4693161 |
In cluster and scale cluster deployments, the snapshot comparison feature may time out when comparing MAC addresses. | 5.0.0 |
| 4689932 |
Node reservation for NetQ is not supported in shared multi-node clusters. To work around this issue, deploy NetQ in a dedicated single-node or three-node cluster first, and then scale the deployment by adding nodes for other applications. | 5.0.0 |
| 4687241 |
The activity log in the UI might display multiple entries with “unknown” or “anonymous” usernames. | 5.0.0 |
| 4683830 |
The Cable Validation Tool might fail to load in the NetQ UI. To work around this issue, log out of NetQ and then log back in. | 5.0.0 |
| 4668341 |
When you a create an LDAP server configuration, the NetQ UI incorrectly allows you to modify the default server ports. Only the standard ports (389 for insecure and 636 for secure) are permitted. | 5.0.0 |
| 4667571 |
NetQ might return inconsistent results when queries use the regular expression wildcard. | 5.0.0 |
| 4637749 |
When the master node is down, the netq show status command might report an incorrect status. |
5.0.0 |
| 4573427 |
The link health view utilization chart might display incorrect values for the top 5 links when multiple links share the same value. | 5.0.0 |
| 4527529 |
When there is a high volume of concurrent API requests to NetQ, some requests may fail. | 4.15.0-5.0.0 |