NVIDIA Docs Hubchevron_right NVIDIA Networkingchevron_right Networking Softwarechevron_right Management Softwarechevron_right

NVIDIA NetQ

NVIDIA NetQ 4.15 Release Notes

Download all 4.15 release notes as .xls

4.15.0 Release Notes

Open Issues in 4.15.0

Issue ID	Description	Affects	Fixed
4521037	The PTP violations summary in the UI might not render properly. To work around this issue, refresh the page in your browser.	4.15.0
4486633	When you run a validation using a `netq check` command, the test results might incorrectly display as passed when the tests were actually skipped. The UI correctly shows which validations were skipped.	4.15.0
4298008	When you upgrade NetQ, any pre-existing validation data will be lost.	4.13.0-4.15.0
4131550	When you run a topology validation, the full-screen topology validation view might not display the latest results. To work around this issue, refresh the page.	4.12.0-4.15.0
4126632	In scale deployments with 1,000 or more switches, BGP validations might take up to five minutes to display results in the UI or CLI.	4.13.0-4.15.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.0
3993538	When you re-position a card on your workbench and then manually refresh the workbench, NetQ might reposition the cards.	4.11.0-4.15.0
3985598	When you configure multiple threshold-crossing events for the same TCA event ID on the same device, NetQ will only display one TCA event for each hostname per TCA event ID, even if both thresholds are crossed or status events are triggered.	4.11.0-4.15.0
3800434	When you upgrade NetQ from a version prior to 4.9.0, What Just Happened data that was collected before the upgrade is no longer present.	4.9.0-4.15.0
3772274	After you upgrade NetQ, data from snapshots taken prior to the NetQ upgrade will contain unreliable data and should not be compared to any snapshots taken after the upgrade. In cluster deployments, snapshots from prior NetQ versions will not be visible in the UI.	4.9.0-4.15.0
3613811	LCM operations using in-band management are unsupported on switches that use eth0 connected to an out-of-band network. To work around this issue, configure NetQ to use out-of-band management in the `mgmt` VRF on Cumulus Linux switches when interface eth0 is in use.	4.8.0-4.15.0

Fixed Issues in 4.15.0

Issue ID	Description	Affects
4466349	When you upgrade an HA cluster deployment from a version that is not part of the supported upgrade path, the upgrade might fail and the UI might not load due to expired control plane certificates on the worker nodes. To check whether the certificates have expired, run `sudo su` followed by `kubeadm certs check-expiration`. If the output displays a date in the past, your certificates are expired. To update the certificates, run `kubeadm certs renew all` on each worker node in the cluster. Next, restart the control plane components with `crictl stop CONTAINER_ID`, followed by `systemctl restart kubelet`.	4.8.0-4.14.0
4402969	When you upgrade a cluster deployment from NetQ 4.13 to 4.14 using Base Command Manager (BCM), the operation might appear to fail with the error message `Warning: Ping to admin app failed. 10.141.0.1 Traceback (most recent call last): File “/usr/bin/netq”, line 404, in rx_reply(sock, sys.argv) File “/usr/bin/netq”, line 126, in rx_reply rx_data = sock.recv(4096) BlockingIOError: [Errno 11] Resource temporarily unavailable`. You can ignore this message and wait for the upgrade to complete. To verify the actual NetQ version and upgrade status, run the `netq show status` command	4.14.0
4310939	When a switch becomes rotten or is connected to a different NetQ server without decommissioning it first, the link health view dashboard displays outdated counter values. To work around this issue, wait for NetQ to update and display accurate counter values.	4.13.0-4.14.0
4309191	In cloud deployments, lifecycle management operations such as device discovery or switch decommissioning might time out and ultimately fail. To work around this issue, restart the LCM executor on the OPTA VM with `lcm_pod=‘kubectl get pod \| grep -m1 lcm \| awk ‘{print $1}’'; kubectl delete pod $lcm_pod`.	4.13.0-4.14.0
4248942	When you assign a role to a switch, NetQ might take up to five minutes to reflect the new or updated role in the queue histogram fabric overview page.	4.13.0-4.14.0