NVIDIA NetQ 5.3 Release Notes
Download all 5.3 release notes as .xls
5.3.0 Release Notes
Open Issues in 5.3.0
| Issue ID | Description | Affects | Fixed |
|---|---|---|---|
| 4965251 | When BlueField DPUs are in the default, embedded mode, the output of the netq check roce command might produce duplicate entries for the same device (one for the host and one for the DPU). This issue can also affect the calculations for the RoCE Mode Consistency and DSCP Classification tests. Additionally, the netq show roce-config host command might display DPU interfaces alongside host interfaces. This issue does not affect DPUs that are configured in separated mode. |
5.2.1-5.3.0 | |
| 4867933 | Threshold-crossing events created before version 5.1.0 may not display event values correctly after you upgrade NetQ. | 5.1.0-5.3.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.3.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.3.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.3.0 | |
| 4100882, 4119697 | 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.3.0 |
Fixed Issues in 5.3.0
| Issue ID | Description | Affects |
|---|---|---|
| 5073537 | After uninstalling a NetQ cluster, the cluster VIP address is not released from the network interface. On a subsequent reinstall, the installer detects the VIP as still reachable and exits with the error cluster-vip address , even though the cluster is no longer runningThis issue affects deployments that use a VLAN interface (for example, bond0.100) rather than the management IP for the cluster VIP. It does not affect first-time installs, but blocks every uninstall-reinstall cycle until the VIP is manually removedTo work around this issue, manually remove the VIP from the interface before reinstalling with sudo ip addr del |
5.2.1 |
| 4989796 | When you send a POST request to nmx/v1/support-packages with a tech-support bundle larger than 1 MB, the operation fails. |
5.0.1-5.2.1 |
| 4986372 | After installing NetQ for Ethernet and NVLink, the UI might fail to load and display the message No route matched with those values.. To work around this issue, restart the Kong-CP and Kong-DP deployments with kubectl rollout restart deployment -n netq-infra kong-cp-kongsleep 300, followed by kubectl rollout restart deployment -n netq-infra kong-dp-kongIf the issue persists, run cd /tmp/netq-infra/kube-config/build/data-infra, followed by kubectl apply -f deck-sync-job.yaml. |
5.2.1 |
| 4943571 | After you register NVLink services, it might take up to an hour for the scheduler service to run and return data. | 5.2.1 |
| 4854663 | When specifying a cluster VIP on an invalid or incorrect subnet, the installer displays an error indicating that master_ip should be different than cluster_ip without indicating which IP address is invalid. |
5.1.0-5.2.1 |
| 4682275 | NVLink cluster installations do not validate that each node has a unique hostname. If two nodes share a common hostname, NetQ does not flag the issue after the installation completes. | 5.0.0-5.2.1 |
| 4389662 | When a cluster installation fails a cluster VIP validation check, the installer generates an opta-support archive and prompts you to send it to NVIDIA support instead of prompting you to fix the initial error. | 4.15.0-5.2.1 |
| 4122430 | When the master node is unreachable, a worker node might report the output of netq show status as Not Installed instead of indicating that the cluster was degraded. |
4.12.0-5.2.1 |