NVIDIA NetQ 3.3 Release Notes

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

3.3.0 Release Notes

Open issues in 3.3.0

Issue IDDescriptionAffectsFixed
NETQ-8396 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
NETQ-8317 NetQ Infra: When adding a data source with the Grafana plugin, an error message appears “Cannot read property ‘status’ of undefined” implying the data source is not added when, in fact, it has been. Ignore the error and continue with configuring the plugin.3.3.0
NETQ-8312 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:
  1. Open the netqui YAML file for editing.

    kubectl edit netquis netqui

  2. Locate the misc section. For example:

    misc:
    cassandraReconnectLogOnly: "true"
    clusterName: netq
    forgotPasswordLink: /link/to/set/password

    smtpSSL: "true"
    tlsEnabled: "true"

  3. 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"

  4. Save the file.
3.3.0
NETQ-8245 If a NetQ Agent is downgraded to the 3.0.0 version from any higher release, the default commands file present in the /etc/netq/commands/ also needs to be updated to prevent the NetQ Agent from becoming rotten.3.0.0-3.3.0
NETQ-8117 NetQ UI: Switches with LLDP enabled only on eth0 are not shown on the topology diagram.3.3.0
NETQ-7966 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
NETQ-6640 Infra: Rarely, after a node is restarted, Kubernetes pods do not synchronize properly and the output of netq show opta-health shows failures. Node operation is not functionally impacted. You can safely remove the failures by running kubectl get pods \| grep MatchNodeSelector \| cut -f1 -d' ' \| xargs kubectl delete pod. To work around the issue, do not label nodes using the API. Instead label nodes through local configuration using kubelet flag "--node-labels".3.1.0-3.3.0
NETQ-5737 UI: Warnings might appear during the post-upgrade phase for a Cumulus Linux switch upgrade job. They are caused by services that have not yet been restored by the time the job is complete. Cumulus Networks recommend waiting five minutes, creating a network snapshot, then comparing that to the pre-upgrade snapshot. If the comparison shows no differences for the services, the warnings can be ignored. If there are differences, then troubleshooting the relevant service(s) is recommended.3.0.0-3.3.0
NETQ-5571 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.0
NETQ-3451 UI: If either the peer_hostname or the peer_asn is invalid, the full screen BGP Service card does not provide the ability to open cards for a selected BGP session.2.3.0-2.4.1, 3.0.0-3.3.0

Fixed Issues in 3.3.0

Issue IDDescriptionAffects
NETQ-8311NetQ 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
NETQ-5529UI: 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