If you are using the current version of Cumulus NetQ, the content on this page may not be up to date. The current version of the documentation is available here. If you are redirected to the main page of the user guide, then this page may have been renamed; please search for it there.

Cumulus NetQ 3.1 Release Notes

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

3.1.0 Release Notes

Open issues in 3.1.0

Issue IDDescriptionAffectsFixed
2555854
NETQ-8245
NetQ Agent: 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.1
2553453
NETQ-7318
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
2551790
NETQ-6732
CLI: Upgrade to NetQ 3.1.0 using the CLI fails due to an authentication issue. To work around this issue, run the netq bootstrap master upgrade command as usual, then use the Admin UI to complete the upgrade at https://<netq-appl-vm-hostname-or-ipaddr>:8443.3.1.0-3.1.13.2.0-3.3.1
2551641
NETQ-6673
Infra: NetQ VM installation fails if the designated disk size is greater than 2TB. To work around this issue, specify the disk for cloud deployments to be between 256GB and 2TB SSD, and for on-premises deployments to be between 32 GB and 2TB.2.4.0-3.1.13.2.0-3.3.1
2551569
NETQ-6650
CLI: When a proxy server is configured for NetQ Cloud access and lifecycle management (LCM) is enabled, the associated LCM CLI commands fail due to incorrect port specification. To work around this issue, configure the NetQ Collector to connect directly to NetQ Cloud without a proxy.3.1.0-3.1.13.2.0-3.3.1
2551545
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.1
2549649
NETQ-5737
NetQ 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.1
2549344
NETQ-5591
UI: The lifecycle management feature does not present general alarm or info events; however, errors related to the upgrade process are reported within the NetQ UI.3.0.0-3.1.13.2.0-3.3.1
2549319
NETQ-5571
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
2549246
NETQ-5529
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.13.3.0-3.3.1
2543867
NETQ-3451
NetQ UI: If either the hostname or the ASN of a BGP peer 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.1

Fixed Issues in 3.1.0

Issue IDDescriptionAffects
2549842
NETQ-5833
Switch upgrade of Cumulus Linux in the lifecycle management feature fails when attempted by a user with a standard or sudo user role and custom password credentials. To work around this issue, upgrades should be performed by users with root or sudo user role and an SSH key. Optionally, upgrade using a root user role with custom password.3.0.0-3.0.1
2549787
NETQ-5808
When upgrading to NetQ 3.0.0, if you are using NetQ Agent 2.3.1 or earlier and have MLAG configured, the MLAG service becomes unresponsive. To resolve this issue, upgrade your NetQ Agents to version 3.0.0.3.0.0-3.0.1
2549721
NETQ-5774
When installing NetQ on switches running in Cumulus Linux 3.7.x with management VRF configured, the CLI and Agent server are configured as follows:
netq config add cli server <ipaddr> vrf mgmtnetq config restart clinetq config add agent server <ipaddr> vrf mgmtnetq config restart agent
This results in netqd running in both default and management VRF and the NetQ Agent running in default VRF. In this scenario, the NetQ Agent status is not reported correctly to the management VRF. To workaround this issue: If you have management VRF configured, run the following commands:
systemctl stop netqd.servicesystemctl disable netqd.servicesystemctl enable netqd@mgmt.servicesystemctl restart netqd@mgmt.service
If you have default VRF configured, run the following commands:
systemctl stop netqd@mgmt.servicesystemctl disable netqd@mgmt.servicesystemctl enable netqd.servicesystemctl restart netqd.service
3.0.0-3.0.1
2549704
NETQ-5768
When multiple premises are deployed and Cumulus Linux upgrades have been performed on switches using the lifecycle management feature, the Upgrade History card displays history for all premises rather than only those for the selected premises.3.0.0-3.0.1
2549682
NETQ-5752
Performing an upgrade using the lifecycle management feature fails intermittently when SSH key switch access authorization is used. To work around this issue, use basic authentication or retry an upgrade job that uses SSH key authorization.3.0.0-3.0.1
2547642
NETQ-4927
Admin UI: If the Master Installation phase fails during NetQ installation, refreshing the page causes the error log to be lost. On failure, download the error log, then run netq bootstrap reset followed by netq bootstrap master interface on the node before restarting the installation process.2.4.1-3.0.1