| 4621868 |
NetQ might generate event notifications for BGP reset time changes even when no actual changes have occurred. |
4.14.0-4.15.1 |
5.0.0-5.1.0 |
| 4612457 |
The process monitoring dashboard may display inaccurate CPU utilization values for the NetQ agent. |
4.11.0-4.15.1 |
5.0.0-5.1.0 |
| 4537675 |
The NetQ UI might not display pagination controls for large tables with multiple entries. |
4.14.0-4.15.1 |
5.0.0-5.1.0 |
| 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 |
4.15.0-4.15.1 |
| 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 |
4.15.0-4.15.1 |
| 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 |
4.15.0-4.15.1 |
| 4309191, 4309888, 4343075, 4351684, 4411619, 4291885, 4493616 |
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 |
4.15.0-4.15.1 |
| 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 |
4.15.0-4.15.1 |
| 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.1 |
|
| 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.1.0 |
|
| 4023716, 4022819, 4282514 |
NetQ might display duplicate validations results. |
4.11.0-4.15.1 |
5.0.0-5.1.0 |
| 3993538, 4379389 |
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.1 |
5.0.0-5.1.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.1 |
|
| 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.1 |
|
| 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.1 |
|
Download all 4.14 release notes as .xls