NVIDIA NetQ 4.10 Release Notes

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

4.10.0 Release Notes

Open Issues in 4.10.0

Issue IDDescriptionAffectsFixed
When NetQ validates BGP neighbors in your network, numbered BGP neighbors pass validation with mismatched values configured.4.10.0
When you perform an LCM switch discovery on a Cumulus Linux 5.9.0 switch in your network that was already added in the NetQ inventory on a prior Cumulus Linux version, the switch will appear as Rotten in the NetQ UI. To work around this issue, decommission the switch first,and run LCM discovery again after the switch is upgraded.4.10.0
When the NetQ master node in a cluster is down, the NetQ kafka-connect pods might crash on other cluster nodes, preventing data collection. To work around this issue, bring the master node back into service.4.10.0
After you run an LCM switch discovery in a NetQ cluster environment, NetQ CLI commands on switches might fail with the message Failed to process command.4.10.0
The netq-opta package fails to install on Cumulus Linux 5.9.0. On-switch OPTA is not supported on Cumulus Linux
After you upgrade NetQ, devices that were in a rotten state before the upgrade might not appear in the UI or CLI after the upgrade. To work around this issue, decommission rotten devices before performing the upgrade.4.9.0-4.10.0
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.10.0
In a NetQ cluster environment, if your master node goes offline and is restored, subsequent NetQ validations for MLAG and EVPN might unexpectedly indicate failures. To work around this issue, either restart NetQ agents on devices in the inventory or wait up to 24 hours for the issue to clear.4.9.0-4.10.0
When you install a NetQ cluster deployment on a subnet with other NetQ clusters or other devices using VRRP, there might be connectivity loss to the cluster virtual IP (VIP). The VIP is established using the VRRP protocol, and during cluster installation a virtual router ID (VRID) is selected. If another device on the subnet running VRRP selects the same VRID, connectivity issues may occur. To work around this issue, avoid multiple VRRP speakers on the subnet, or ensure the VRID used on all VRRP devices is unique. To validate the VRID used by NetQ, check the assigned virtual_router_id value in /mnt/keepalived/keepalived.conf.4.9.0-4.10.0
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.10.0
When there is a NetQ interface validation failure for admin state mismatch, the validation failure might clear unexpectedly while one side of the link is still administratively down.4.9.0-4.10.0
When you run a NetQ trace and specify MAC addresses for the source and destination, NetQ displays the message “No valid path to destination” and does not display trace data.4.9.0-4.10.0
After you decommission a switch, the switch’s interfaces are still displayed in the NetQ UI in the Interfaces view.4.9.0-4.10.0
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.10.0

Fixed Issues in 4.10.0

Issue IDDescriptionAffects
When you upgrade an on-premises NetQ deployment, the upgrade might fail with the following message:
master-node-installer: Upgrading NetQ Appliance with tarball : /mnt/installables/NetQ-4.9.0.tgz
master-node-installer: Migrating H2 db list index out of range.
To work around this issue, re-run the netq upgrade command.
When you upgrade NetQ cluster deployments with DPUs in the device inventory, the DPUs might not be visible in the NetQ UI after the upgrade. To work around this issue, restart the DTS container on the DPUs in your network.4.9.0
When you upgrade NetQ cluster deployments, the configured LCM credential profile assigned to switches in the inventory is reset to the default access profile. To work around this issue, reconfigure the correct access profile on switches before managing them with LCM after the upgrade.4.9.0
When you attempt to delete a scheduled trace using the NetQ UI, the trace record is not deleted.4.7.0-4.9.0
When you perform a switch discovery by specifying an IP range, an error message is displayed if switches included in the range have different credentials. To work around this issue, batch switches based on their credentials and run a switch discovery for each batch.4.9.0
When you perform a NetQ upgrade, the upgrade might fail with the following error message:
Command ‘[‘kubectl’, ‘version –client’]’ returned non-zero exit status 1.
To work around this issue, run the netq bootstrap reset keep-db command and then reinstall NetQ using the netq install command for your deployment.
When you perform a netq bootstrap reset on a NetQ cluster VM and perform a fresh install with the netq install command, the install might fail with the following error:
 master-node-installer: Running sanity check on cluster_vip: Virtual IP is already used
To work around this issue, run the netq install command again.
When you upgrade a switch running Cumulus Linux using NetQ LCM, any configuration files in /etc/cumulus/switchd.d for adaptive routing or other features are not restored after the upgrade. To work around this issue, manually back up these files and restore them after the upgrade.4.9.0
When you reconfigure a VNI to map to a different VRF or remove and recreate a VNI in the same VRF, NetQ EVPN validations might incorrectly indicate a failure for the VRF consistency test.4.9.0
When you export events from NetQ to a CSV file, the timestamp of the exported events does not match the timestamp reported in the NetQ UI based on the user profile’s time zone setting.4.9.0
When you export digital optics table data from NetQ, some fields might be visible in the UI that are not exported to CSV or JSON files.4.9.0
When you upgrade a Cumulus Linux switch configured for TACACS authentication using NetQ LCM, the switch’s TACACS configuration is not restored after upgrade.4.8.0-4.9.0