layout-3layout-6layout-1layout-top
layout-toplayout-6layout-1

NVIDIA NetQ 4.6 Release Notes

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

4.6.0 Release Notes

Open Issues in 4.6.0

Issue IDDescriptionAffectsFixed
3355892
When you use NetQ LCM to upgrade a switch from a Cumulus Linux 5 release to a later version and have not saved your NVUE configuration with the nv config save command, the NetQ UI will present the following warning:
There are unsaved changes in the NVUE config file on switch . Consider saving the changes before upgrading.
4.6.0
3429528
EVPN and RoCE validation cards in the NetQ UI might not display data when Cumulus Linux switches are configured with high VNI scale.4.6.0
3435373
If your NetQ on-premises VM is not configured with at least 16 vCPUs, upgrades from NetQ 4.5.0 to 4.6.0 using the netq upgrade bundle command fail with the following message:
Job upgrade failed or timed out
To work around this issue, reconfigure your VM to use 16 vCPUs before upgrading.		4.5.0-4.6.0
3436299
RoCE validations might not display data in the NetQ UI and CLI for Cumulus Linux switches when the NVUE service is not running. This issue will resolve itself within 24 hours after the next full status update from the NetQ agent.4.6.0
2885312
EVPN Validation Type 2 checks might show false Duplicate MAC events for MAC addresses that are not duplicated. An example of this is shown below:
EVPN Type 2 Test details:
  Hostname          Peer Name         Peer Hostname     Reason                                        Last Changed
  —————– —————– —————– ——————————————— ————————-
  torc-11           -                 -                 Duplicate Mac 00:02:00:00:00:55 VLAN 1249 at  Sun Dec  5 18:26:14 2021
                                                        torc-21:vx-282 and torc-11:peerlink-3
4.1.0-4.6.0
3431386
When you upgrade your NetQ VM from NetQ 4.5.0 to 4.6.0 using the netq upgrade bundle command, certain pods are not correctly retagged. To work around this issue, retag and restart the affected pods with the following commands for your deployment:

On-premises VMs:
sudo docker tag localhost:5000/fluend-aggregator-opta:1.14.3 docker-registry:5000/fluend-aggregator-opta:1.14.3
sudo docker push docker-registry:5000/fluend-aggregator-opta:1.14.3
sudo kubectl get pods -n default|grep -i fluend-aggregator-opta|awk ‘{print $1}'|xargs kubectl delete pod -n default

sudo docker tag localhost:5000/cp-schema-registry:7.2.0 docker-registry:5000/cp-schema-registry:7.2.0
sudo docker push docker-registry:5000/cp-schema-registry:7.2.0
sudo kubectl get pods -n default|grep -i cp-schema-registry|awk ‘{print $1}'|xargs kubectl delete pod -n default

sudo docker tag localhost:5000/cp-kafka:7.2.0 docker-registry:5000/cp-kafka:7.2.0
sudo docker push docker-registry:5000/cp-kafka:7.2.0
sudo kubectl get pods -n default|grep -i kafka-broker|awk ‘{print $1}'|xargs kubectl delete pod -n default

Cloud VMs:
sudo docker tag localhost:5000/fluend-aggregator-opta:1.14.3 docker-registry:5000/fluend-aggregator-opta:1.14.3
sudo docker push docker-registry:5000/fluend-aggregator-opta:1.14.3
sudo kubectl get pods -n default|grep -i fluend-aggregator-opta|awk ‘{print $1}'|xargs kubectl delete pod -n default
4.6.0
3446351
When you perform an apt upgrade from NetQ 4.5.0 to version 4.6.0, the sudo apt upgrade command fails with the following message:
Setting up shim-signed (1.40.9+15.7-0ubuntu1) …
mount: /var/lib/grub/esp: special device /dev/vda15 does not exist.
dpkg: error processing package shim-signed (–configure):
installed shim-signed package post-installation script subprocess returned error exit status 32

Errors were encountered while processing:

shim-signed

E: Sub-process /usr/bin/dpkg returned an error code (1)
To work around this issue, run the sudo apt remove -y shim-signed grub-efi-amd64-bin –allow-remove-essential command and rerun the sudo apt upgrade command.		4.6.0
3442456
When an event notification is resolved or acknowledged, the NetQ UI might display a duplicate event with the original notification content and timestamp.4.2.0-4.6.0
3454057
When you configure more than one TCA rule referencing the same TCA event type, adding additional TCA rules fails with the following message:
Failed to add/update TCA http status_code: 409		4.5.0-4.6.0

Fixed Issues in 4.6.0

Issue IDDescriptionAffects
3438973
When you install NetQ onto your VM, the installation fails with the following messages:
05:57:33.023618: master-node-installer: Installed Debian …	[ FAILED ]————————————–ERROR: Failed to install the master node
This is due to an expired key in the installation tarball. For assistance working around this issue, contact NVIDIA support.		4.3.0-4.5.0
3395385
When you use NetQ LCM to upgrade a Cumulus Linux switch in an MLAG pair, the upgrade might fail.4.4.1-4.5.0
3367267
When you upgrade a switch with NetQ LCM using the root user, the upgrade fails with the following message:
 Destination /home/root does not exist.
To work around this issue, perform the upgrade using a different user account.		4.5.0
3362224
When you configure a new access profile with SSH authentication using the CLI, the command fails with the following log message:
Expecting value: line 1 column 1 (char 0)
To work around this issue, use the NetQ UI to configure the access profile.		4.5.0
3360627
When the switch RoCE egress pool buffer limit is configured as unlimited, the maximum buffer usage for RoCE counters might display incorrect values in the NetQ UI.4.4.1-4.5.0