layout-3 layout-6 layout-1 layout-top
NVIDIA Docs Hubchevron_right NVIDIA Networkingchevron_right Networking Softwarechevron_right Management Softwarechevron_right

NVIDIA NetQ

layout-top layout-6 layout-1

A newer version of this product documentation is available. If you are redirected to the main page of the user guide, then this page might have been renamed or removed.

NVIDIA NetQ 3.3 Release Notes

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

3.3.1 Release Notes

Open Issues in 3.3.1

Issue ID Description Affects Fixed
2893000
CVE-2021-44228: Apache Log4j2 <=2.14.1 JNDI features used in configuration, log messages, and parameters do not protect against attacker controlled LDAP and other JNDI related endpoints. 2.4.0-4.0.1 4.1.0-4.13.0
2690469
While upgrading an on-premises deployment from version 2.4.x to 3.x.y then to 4.x, the upgrade fails during the NetQ application stage
To work around this issue, run the following command on the NetQ telemetry server, then start the upgrade again:‘netq install opta activate-job config-key EhVuZXRxLWVuZHBvaW50LWdhdGV3YXkYsagDIiw3T2sweW9kR3Y4Wk9sTHU3MkwrQTRjNkhhQkU3bVpBNVlZVjEvWWgyZGJBPQ==’		 3.2.1-4.0.1 4.1.0-4.13.0
2556754
netq-agent installed on Cumulus Linux might slowly leak memory during sustained layer two network events at high scale. 3.3.0-3.3.1 4.0.0-4.13.0
2555197
NetQ CLI: Occasionally, when a command response contains a large number of objects to be displayed the NetQ CLI does not display all results in the console. When this occurs, view all results using the json format option. 3.3.0-3.3.1 4.0.0-4.13.0
2553453
The netqd daemon logs a traceback to /var/log/netqd.log when the OPTA server is unreachable and netq show commands are run. 3.1.0-3.3.1 4.0.0-4.13.0
2549319
NetQ UI: The legend and segment colors on Switches and Upgrade History card graphs sometimes do not match. These cards appear on the lifecycle management dashboard (Manage Switch Assets view). Hover over graph to view the correct values. 3.0.0-3.3.1 4.0.0-4.13.0

Fixed Issues in 3.3.1

Issue ID Description Affects
2556545
NetQ Agent: When upgrading to NetQ 3.3.0, sometimes the NetQ Agent fails to complete the upgrade on Broadcom-based swtiches. To work around this issue, update the following file on the switch where the NetQ Agent is running:
Open the armel-netq-commands.yml file in the /etc/netq/commands/ directory for editing.
Copy and append the following to the file:
 - service: “inventory”
   commands:
     - key: “os-release”
       command: “cat /etc/os-release”
       isactive: true
       parser: “local”
     - key: “eprom”
       command: “/usr/cumulus/bin/decode-syseeprom -j”
       isactive: true
       parser: “local”
     - key: “lscpu”
       command: “/usr/bin/lscpu”
       isactive: true
       parser: “local”
     - key: “meminfo”
       command: “cat /proc/meminfo”
       isactive: true
       parser: “local”
     - key: “lsblk”
       command: “lsblk -d -n -o name,size,type,vendor,tran,rev,model”
       isactive: true
       parser: “local”
     - key: “dmicode”
       command: “dmidecode -t 17”
       isactive: true
       parser: “local”
     - key: “is-opta”
       command: “cat /etc/app-release”
       isactive: true
       parser: “local”
Remove the existing generated command file
cumulus@switch:~$ rm /var/run/netq/netq-commands.yml
Restart the NetQ Agent
cumulus@switch:~$ netq config restart agent
 3.3.0
2556434
NetQ UI: When switches are running NetQ but hosts are not, the topology does not display the spine and leaf layers as separate tiers. 3.3.0
2556275
NetQ UI: The full-screen BGP Validation card for the default validation can become unresponsive when a very large number of sessions or errors are present. 3.3.0
2556268
NetQ UI: When assigning a switch configuration profile to a switch using the lifecycle management, you cannot save the per-switch variable data. This prevents you from applying the switch configuration. Upgrade to NetQ 3.3.1 to take advantage of this feature. 3.3.0
2556227
Admin UI: For cloud deployments, clicking the Open NetQ link at the bottom of the Admin UI NetQ Health page returns an error default backend - 404 as it attempts to open the NetQ UI on the on-site NetQ Cloud Appliance or VM running the NetQ Collector software. In cloud deployments, the NetQ UI is run in the Cloud rather than locally, thus causing the error. To open the NetQ UI and view your data, enter _https://netq.cumulusnetworks.com/_ into the address bar of your browser. 3.3.0
2556205
NetQ CLI: User cannot remove a notification channel when threshold-based event rules are configured. 3.2.1-3.3.0
2556192
NetQ UI: In multi-site on-premises deployments, when a new premises (created using the Premises card) is selected from the dropdown in the application header, the NetQ UI becomes unresponsive for many navigation tabs. To work around this issue, manually update the database as follows:
In a terminal window, open the database shell (cqlsh)
$ CASSANDRA_POD=‘kubectl get pods | grep cassandra | cut -f1 -d" “’ ; kubectl exec -it $CASSANDRA_POD – cqlsh
Display the premises table
cqlsh> select opid,name,namespace from master.premises ;
The resulting output would be similar to this, with new premises having an empty namespace:

opid  | name  | namespace——-+——-+———–
20001 | site1 |      null
    0 | OPID0 |      null
20002 | site2 |          
20000 | site0 |      null
20003 | site3 |          (5 rows)
For each new premises, insert a null value into the database to resolve the issue. For example the new premises site3 has an empty namespace value, run following query against its opid 20003 to change the value
cqlsh> insert into master.premises (opid,namespace) values (20003,null);
Verify the new premises now have null values in the database
cqlsh> select opid,name,namespace from master.premises ;
opid  | name  | namespace——-+——-+———–
20001 | site1 |      null
    0 | OPID0 |      null
20002 | site2 |      null     
20000 | site0 |      null
20003 | site3 |      null(5 rows)
 3.3.0
2556117
NetQ Infra: The NetQ Agent fails to start when switch is running Cumulus Linux version 4.1.1 or 4.2.0. To work around this issue, run the following on each switch:
For CL 4.1.1, rename the WJH types file to the 4.3.3260 version:
cumulus@switch:~$ sudo mv /usr/lib/cumulus/wjh/wjh_types_4.4.3260.py /usr/lib/cumulus/wjh/wjh_types_4.3.3260.py
Then restart the NetQ Agent:
cumulus@switch:~$ netq config restart agent
For CL 4.2.0, edit the following line in the /usr/sbin/netq-agent-prestart script to change the version from 4.4.095 to 4.4.0952:
elif [ $sx_sdk_ver == “4.4.0952” ] || [  $sx_sdk_ver == “4.4.1624” ] || [ $sx_sdk_ver == “4.3.3260” ];
Then restart the NetQ Agent:
cumulus@switch:~$ netq config restart agent
 3.3.0
2556007
NetQ API: Several APIs are presenting the following error when viewed in Swagger UI:
Fetch errorundefined https://api.prod2.netq.cumulusnetworks.com/netq/telemetry/v1/api-docs/events/swagger.json
To correct this presentation issue:Open the netqui YAML file for editing
kubectl edit netquis netqui
Locate the misc section. For example:
misc:
 cassandraReconnectLogOnly: “true”
 clusterName: netq
 forgotPasswordLink: /link/to/set/password
 …
 smtpSSL: “true”
 tlsEnabled: “true”
Add the document_namespace parameter below the tlsEnabled parameter
misc:
 cassandraReconnectLogOnly: “true”
 clusterName: netq
 forgotPasswordLink: /link/to/set/password
 …
 smtpSSL: “true”
 tlsEnabled: “true”
 document_namespace: “default”
Save the file.		 3.3.0
2555848
NetQ Infra: It is important to plan your upgrade to NetQ 3.3.0 because the NetQ Appliance or VM becomes unavailable for approximately an hour during the process. No data is lost in the process. 3.3.0
2555617
NetQ Infra: Upgrading the NetQ Agent before upgrading the NetQ CLI for version 3.3.0 causes the NetQ CLI to fail the upgrade. To work around this issue, upgrade the NetQ CLI first, then follow with the NetQ Agent upgrade. 3.3.0
2555587
NetQ UI: Switches with LLDP enabled only on eth0 are not shown on the topology diagram. 3.3.0

3.3.0 Release Notes

Open Issues in 3.3.0

Issue ID Description Affects Fixed
2893000
CVE-2021-44228: Apache Log4j2 <=2.14.1 JNDI features used in configuration, log messages, and parameters do not protect against attacker controlled LDAP and other JNDI related endpoints. 2.4.0-4.0.1 4.1.0-4.13.0
2690469
While upgrading an on-premises deployment from version 2.4.x to 3.x.y then to 4.x, the upgrade fails during the NetQ application stage
To work around this issue, run the following command on the NetQ telemetry server, then start the upgrade again:‘netq install opta activate-job config-key EhVuZXRxLWVuZHBvaW50LWdhdGV3YXkYsagDIiw3T2sweW9kR3Y4Wk9sTHU3MkwrQTRjNkhhQkU3bVpBNVlZVjEvWWgyZGJBPQ==’		 3.2.1-4.0.1 4.1.0-4.13.0
2556754
netq-agent installed on Cumulus Linux might slowly leak memory during sustained layer two network events at high scale. 3.3.0-3.3.1 4.0.0-4.13.0
2556545
NetQ Agent: When upgrading to NetQ 3.3.0, sometimes the NetQ Agent fails to complete the upgrade on Broadcom-based swtiches. To work around this issue, update the following file on the switch where the NetQ Agent is running:
Open the armel-netq-commands.yml file in the /etc/netq/commands/ directory for editing.
Copy and append the following to the file:
 - service: “inventory”
   commands:
     - key: “os-release”
       command: “cat /etc/os-release”
       isactive: true
       parser: “local”
     - key: “eprom”
       command: “/usr/cumulus/bin/decode-syseeprom -j”
       isactive: true
       parser: “local”
     - key: “lscpu”
       command: “/usr/bin/lscpu”
       isactive: true
       parser: “local”
     - key: “meminfo”
       command: “cat /proc/meminfo”
       isactive: true
       parser: “local”
     - key: “lsblk”
       command: “lsblk -d -n -o name,size,type,vendor,tran,rev,model”
       isactive: true
       parser: “local”
     - key: “dmicode”
       command: “dmidecode -t 17”
       isactive: true
       parser: “local”
     - key: “is-opta”
       command: “cat /etc/app-release”
       isactive: true
       parser: “local”
Remove the existing generated command file
cumulus@switch:~$ rm /var/run/netq/netq-commands.yml
Restart the NetQ Agent
cumulus@switch:~$ netq config restart agent
 3.3.0 3.3.1
2556434
NetQ UI: When switches are running NetQ but hosts are not, the topology does not display the spine and leaf layers as separate tiers. 3.3.0 3.3.1
2556275
NetQ UI: The full-screen BGP Validation card for the default validation can become unresponsive when a very large number of sessions or errors are present. 3.3.0 3.3.1
2556268
NetQ UI: When assigning a switch configuration profile to a switch using the lifecycle management, you cannot save the per-switch variable data. This prevents you from applying the switch configuration. Upgrade to NetQ 3.3.1 to take advantage of this feature. 3.3.0 3.3.1
2556227
Admin UI: For cloud deployments, clicking the Open NetQ link at the bottom of the Admin UI NetQ Health page returns an error default backend - 404 as it attempts to open the NetQ UI on the on-site NetQ Cloud Appliance or VM running the NetQ Collector software. In cloud deployments, the NetQ UI is run in the Cloud rather than locally, thus causing the error. To open the NetQ UI and view your data, enter _https://netq.cumulusnetworks.com/_ into the address bar of your browser. 3.3.0 3.3.1
2556205
NetQ CLI: User cannot remove a notification channel when threshold-based event rules are configured. 3.2.1-3.3.0 3.3.1
2556192
NetQ UI: In multi-site on-premises deployments, when a new premises (created using the Premises card) is selected from the dropdown in the application header, the NetQ UI becomes unresponsive for many navigation tabs. To work around this issue, manually update the database as follows:
In a terminal window, open the database shell (cqlsh)
$ CASSANDRA_POD=‘kubectl get pods | grep cassandra | cut -f1 -d” “’ ; kubectl exec -it $CASSANDRA_POD – cqlsh
Display the premises table
cqlsh> select opid,name,namespace from master.premises ;
The resulting output would be similar to this, with new premises having an empty namespace:

opid  | name  | namespace——-+——-+———–
20001 | site1 |      null
    0 | OPID0 |      null
20002 | site2 |          
20000 | site0 |      null
20003 | site3 |          (5 rows)
For each new premises, insert a null value into the database to resolve the issue. For example the new premises site3 has an empty namespace value, run following query against its opid 20003 to change the value
cqlsh> insert into master.premises (opid,namespace) values (20003,null);
Verify the new premises now have null values in the database
cqlsh> select opid,name,namespace from master.premises ;
opid  | name  | namespace——-+——-+———–
20001 | site1 |      null
    0 | OPID0 |      null
20002 | site2 |      null     
20000 | site0 |      null
20003 | site3 |      null(5 rows)
 3.3.0 3.3.1
2556117
NetQ Infra: The NetQ Agent fails to start when switch is running Cumulus Linux version 4.1.1 or 4.2.0. To work around this issue, run the following on each switch:
For CL 4.1.1, rename the WJH types file to the 4.3.3260 version:
cumulus@switch:~$ sudo mv /usr/lib/cumulus/wjh/wjh_types_4.4.3260.py /usr/lib/cumulus/wjh/wjh_types_4.3.3260.py
Then restart the NetQ Agent:
cumulus@switch:~$ netq config restart agent
For CL 4.2.0, edit the following line in the /usr/sbin/netq-agent-prestart script to change the version from 4.4.095 to 4.4.0952:
elif [ $sx_sdk_ver == “4.4.0952” ] || [  $sx_sdk_ver == “4.4.1624” ] || [ $sx_sdk_ver == “4.3.3260” ];
Then restart the NetQ Agent:
cumulus@switch:~$ netq config restart agent
 3.3.0 3.3.1
2556007
NetQ API: Several APIs are presenting the following error when viewed in Swagger UI:
Fetch errorundefined https://api.prod2.netq.cumulusnetworks.com/netq/telemetry/v1/api-docs/events/swagger.json
To correct this presentation issue:Open the netqui YAML file for editing
kubectl edit netquis netqui
Locate the misc section. For example:
misc:
 cassandraReconnectLogOnly: “true”
 clusterName: netq
 forgotPasswordLink: /link/to/set/password
 …
 smtpSSL: “true”
 tlsEnabled: “true”
Add the document_namespace parameter below the tlsEnabled parameter
misc:
 cassandraReconnectLogOnly: “true”
 clusterName: netq
 forgotPasswordLink: /link/to/set/password
 …
 smtpSSL: “true”
 tlsEnabled: “true”
 document_namespace: “default”
Save the file.		 3.3.0 3.3.1
2555848
NetQ Infra: It is important to plan your upgrade to NetQ 3.3.0 because the NetQ Appliance or VM becomes unavailable for approximately an hour during the process. No data is lost in the process. 3.3.0 3.3.1
2555617
NetQ Infra: Upgrading the NetQ Agent before upgrading the NetQ CLI for version 3.3.0 causes the NetQ CLI to fail the upgrade. To work around this issue, upgrade the NetQ CLI first, then follow with the NetQ Agent upgrade. 3.3.0 3.3.1
2555587
NetQ UI: Switches with LLDP enabled only on eth0 are not shown on the topology diagram. 3.3.0 3.3.1
2555197
NetQ CLI: Occasionally, when a command response contains a large number of objects to be displayed the NetQ CLI does not display all results in the console. When this occurs, view all results using the json format option. 3.3.0-3.3.1 4.0.0-4.13.0
2553453
The netqd daemon logs a traceback to /var/log/netqd.log when the OPTA server is unreachable and netq show commands are run. 3.1.0-3.3.1 4.0.0-4.13.0
2549319
NetQ UI: The legend and segment colors on Switches and Upgrade History card graphs sometimes do not match. These cards appear on the lifecycle management dashboard (Manage Switch Assets view). Hover over graph to view the correct values. 3.0.0-3.3.1 4.0.0-4.13.0

Fixed Issues in 3.3.0

Issue ID Description Affects
2556006
NetQ Infra: Customers with cloud deployments who wish to use the lifecycle management (LCM) feature in NetQ 3.3.0 must upgrade their NetQ Cloud Appliance or Virtual Machine as well as the NetQ Agent. 3.2.1
2549246
NetQ UI: Snapshot comparison cards may not render correctly after navigating away from a workbench and then returning to it. If you are viewing the Snapshot comparison card(s) on a custom workbench, refresh the page to reload the data. If you are viewing it on the Cumulus Default workbench, after refreshing the page you must recreate the comparison(s). 2.4.0-3.2.1

    Copyright © 2025  NVIDIA Corporation