Cumulus NetQ 1.3.0 Release Notes

Follow

Overview

These release notes support Cumulus NetQ 1.3.0, and describe currently available features and known issues.

Stay up to Date 

  • Please sign in and click Follow above so you can receive a notification when we update these release notes.
  • Subscribe to our product bulletin mailing list to receive important announcements and updates about issues that arise in our products.
  • Subscribe to our security announcement mailing list to receive alerts whenever we update our software for security issues.

{{table_of_contents}}

What's New in Cumulus NetQ 1.3.0

Cumulus NetQ 1.3.0 includes the following features:

Early Access Support

NetQ 1.3.0 also includes these early access features:

  • NetQ Query Language: Search for even more NetQ data using the SQL-like NetQ Query Language (NetQL). Run your own custom analyses or simply extend NetQ functionality for your specific environment.
  • Collecting interface statistics: NetQ provides the ability to collect counters for network interfaces.

EVPN

Cumulus NetQ includes support for EVPN through the addition of netq check evpn, and by enhancing existing commands to verify address families are configured correctly throughout the network fabric.

Caveats and Errata

  • Cumulus NetQ EVPN support can only be used with Cumulus Linux 3.4 and later releases. This is because netq show bgp evpn vni requires JSON output support, or import-rt field values will not be listed.
  • NetQ does not provide functionality to measure HER rate. This will be added in a later release.
  • MTU checking to ensure jumbo frames is not provided.
  • import-rt and export-rt checking is not enforced.
  • Cumulus NetQ 1.3 does not support measuring excessive MAC moves.

Upgrading NetQ

To upgrade, NetQ, read the user guide.

Documentation

You can read the technical documentation here.

Issues Fixed in Cumulus NetQ 1.3.0

The following is a list of issues fixed in Cumulus NetQ 1.3.0 from earlier versions of Cumulus NetQ.

Release Note ID Summary Description

RN-844 (CM-19129)
NetQ Agent does not support multiple DNS server names in HA mode

In HA mode, you can't add multiple DNS names when configuring an agent.

To work around this issue, use the server IP address when configuring the agent instead of the DNS name.

This issue is fixed in Cumulus NetQ 1.3.0


RN-845 (CM-20035)
NetQ Agent stops while processing netlink messages

The NetQ Agent stops while processing netlink messages due to a timing issue and an exception occurs when trying to access data, such as VLAN to VNI mapping.

This issue is fixed in Cumulus NetQ 1.3.0


RN-846 (CM-20013)
When a query is run on a large dataset, a memory error occurs in the tabulate call 

When you run a query on a large data set, for example if you run netq show macs with 500k entries, a memory error occurs.

This issue is fixed in Cumulus NetQ 1.3.0


RN-847 (CM-19679)
NetQ Notifier generates port empty and plugged messages even though optics are not removed or inserted

NetQ Notifier generates port empty and plugged messages periodically for multiple switches and random interfaces even though no optics have been removed or reinserted on the switch.

This issue is fixed in Cumulus NetQ 1.3.0


RN-848 (CM-19621)
NetQ Notifier generates frequent port empty and plugged messages

NetQ Notifier generates port empty and plugged messages repeatedly after you remove and re-insert optics on the switch.

This issue is fixed in Cumulus NetQ 1.3.0


RN-849 (CM-19557)
The 'netq check clag' command reports an  anycast IP and bridge ID mismatch when they do actually match

When you run the netq check clag command, you see warnings that there is an anycast IP and bridge ID mismatch; however the strings do actually match.

This issue is fixed in Cumulus NetQ 1.3.0


RN-850 (CM-19516)
NetQ package installation succeeds on unsupported OS releases

NetQ package installation succeeds on unsupported OS releases, then crashes while starting. Package installation should fail with a message clearly stating that the OS is not supported.

This issue is fixed in Cumulus NetQ 1.3.0


RN-851 (CM-19441)
Tagging a user in Slack notifications does not work  in NetQ Notifier

Tagging a user in Slack notifications is not working in NetQ Notifier.

This issue is fixed in Cumulus NetQ 1.3.0


RN-852 (CM-19216)
NetQ Agent crashes when the interface alias contains unicode characters

Configuring an interface alias that contains unicode characters causes the NetQ Agent to crash.

This issue is fixed in Cumulus NetQ 1.3.0


RN-853 (CM-19135)
Parsing error when NTP service is stopped but enabled

Stopping the NTP service but not disabling it causes a parsing error on the output of a command such as sudo systemctl show -p MainPID ntp.

This issue is fixed in Cumulus NetQ 1.3.0


RN-854 (CM-19060)
No support for timesyncd on ubuntu 16.04

The timesyncd daemon is not supported in NetQ on Ubuntu.

This issue is fixed in Cumulus NetQ 1.3.0. NetQ now supports timesyncd.

Known Issues in Cumulus NetQ 1.3.0

Issues are categorized for easy review. Some issues are fixed but will be available in a later release.

Release Note ID Summary Description

RN-622 (CM-14421)
NetQ does not support traditional mode bridges Support for traditional mode bridges should come in a future release of NetQ.

RN-692 (CM-18623)
When running NetQ on a chassis, `netq show inventory` does not show ASIC and port information

When NetQ is running on a Facebook Backpack chassis, the netq show inventory brief command displays "N/A" in the ASIC and Ports columns.

cumulus@10-0-2-32:~$ netq show inventory brief 
Matching inventory records:
Hostname        Switch    OS             CPU     ASIC    Ports
--------------  --------  -------------  ------  ------  -------
cel-bs02-fc1    FAB       Cumulus Linux  x86_64  N/A     N/A
cel-bs02-fc2    FAB       Cumulus Linux  x86_64  N/A     N/A
cel-bs02-lc101  LC        Cumulus Linux  x86_64  N/A     N/A
cel-bs02-lc102  LC        Cumulus Linux  x86_64  N/A     N/A
cel-bs02-lc201  LC        Cumulus Linux  x86_64  N/A     N/A
hosts-11        N/A       Ubuntu         x86_64  N/A     N/A
hosts-12        N/A       CentOS Linux   x86_64  N/A     N/A
hosts-13        N/A       Ubuntu         x86_64  N/A     N/A
hosts-14        N/A       CentOS Linux   x86_64  N/A     N/A
hosts-21        N/A       Ubuntu         x86_64  N/A     N/A
hosts-22        N/A       CentOS Linux   x86_64  N/A     N/A
hosts-23        N/A       Ubuntu         x86_64  N/A     N/A
hosts-24        N/A       CentOS Linux   x86_64  N/A     N/A

This is a known issue that is currently being investigated.


RN-693 (CM-18794)
When NetQ detects an auto-edge interface, traversing stops, resulting in an incomplete STP topology tree

Running netq show stp topology displays an incomplete STP topology tree. When NetQ detects an interface as auto-edge, it stops traversing before verifying with the other side whether or not it is an edge. In the example below, the topology tree for spine2 to edge1 and edge2 is incomplete:

cumulus@switch:~$ netq spine1 show stp  topology
Root(spine1) -- spine1:sw_clag200 -- leaf1:EdgeIntf(sng_hst2) -- hsleaf11
                                  -- leaf1:EdgeIntf(dual_host2) -- hdleaf2
                                  -- leaf1:EdgeIntf(dual_host1) -- hdleaf1
                                  -- leaf1:ClagIsl(peer-bond1) -- leaf2
                                  -- leaf2:EdgeIntf(sng_hst2) -- hsleaf21
                                  -- leaf2:EdgeIntf(dual_host2) -- hdleaf2
                                  -- leaf2:EdgeIntf(dual_host1) -- hdleaf1
                                  -- leaf2:ClagIsl(peer-bond1) -- leaf1
             -- spine1:ClagIsl(peer-bond1) -- spine2
             -- spine1:sw_clag300 -- edge2:EdgeIntf(sng_hst2) -- hsedge21
                                  -- edge2:EdgeIntf(dual_host2) -- hdedge2
                                  -- edge2:EdgeIntf(dual_host1) -- hdedge1
                                  -- edge2:ClagIsl(peer-bond1) -- edge1
                                  -- edge1:EdgeIntf(sng_hst2) -- hsedge11
                                  -- edge1:EdgeIntf(dual_host2) -- hdedge2
                                  -- edge1:EdgeIntf(dual_host1) -- hdedge1
                                  -- edge1:ClagIsl(peer-bond1) -- edge2
Root(spine2) -- spine2:sw_clag200 -- leaf2:EdgeIntf(sng_hst2) -- hsleaf21
                                  -- leaf2:EdgeIntf(dual_host2) -- hdleaf2
                                  -- leaf2:EdgeIntf(dual_host1) -- hdleaf1
                                  -- leaf2:ClagIsl(peer-bond1) -- leaf1
                                  -- leaf1:EdgeIntf(sng_hst2) -- hsleaf11
                                  -- leaf1:EdgeIntf(dual_host2) -- hdleaf2
                                  -- leaf1:EdgeIntf(dual_host1) -- hdleaf1
                                  -- leaf1:ClagIsl(peer-bond1) -- leaf2
             -- spine2:ClagIsl(peer-bond1) -- spine1
             -- spine2:EdgeIntf(sw_clag300) -- edge1
             -- spine2:EdgeIntf(sw_clag300) -- edge2

This is a known issue that is currently being investigated.

 

RN-694 (CM-18852)
The `netq show vlan` command does not return the status of an SVI

NetQ correctly shows that an SVI is present on a switch, but the netq show vlan command doesn't return its status. For example:

cumulus@leaf01:~$ netq leaf01 show vlan
Matching vlan records:
Hostname         VLAN   Ports                                      SVI  Last Changed
---------------- ------ ------------------------------------------ ---- ----------------
leaf01           100    hostbond6, hostbond4, hostbond5, hostbond3 yes  43m:25.184s
leaf01           101    hostbond6, hostbond4, hostbond5, hostbond3 yes  43m:25.185s
leaf01           102    hostbond6, hostbond4, hostbond5, hostbond3 yes  43m:25.185s
leaf01           103    hostbond6, hostbond4, hostbond5, hostbond3 yes  43m:25.185s
leaf01           104    hostbond6, hostbond4, hostbond5, hostbond3 yes  43m:25.185s
leaf01           105    hostbond6, hostbond4, hostbond5, hostbond3 yes  43m:25.185s
leaf01           106    hostbond6, hostbond4, hostbond5, hostbond3 yes  43m:25.185s
leaf01           1000   vx-33, hostbond6, hostbond4, hostbond5,    yes  43m:25.185s
                        hostbond3
leaf01           1001   hostbond6, hostbond4, hostbond5,           yes  43m:25.185s
                        hostbond3, vx-34
leaf01           1002   hostbond6, hostbond4, hostbond5,           yes  43m:25.185s
                        hostbond3, vx-35
leaf01           1003   hostbond6, hostbond4, hostbond5, vx-36,    yes  43m:25.185s
                        hostbond3
leaf01           1004   hostbond6, hostbond4, hostbond5, vx-37,    yes  43m:25.185s
                        hostbond3
leaf01           1005   hostbond6, vx-38, hostbond4, hostbond5,    yes  43m:25.185s
                        hostbond3
cumulus@leaf01:~$ 

But netq show vlan does not display any information about the SVI:

cumulus@leaf01:~$ netq show vlan | grep 'SVI\|leaf01'
Hostname    VLANs              SVIs                 Last Changed
leaf01      100-106,1000-1005  -                    44m:59.102s
cumulus@leaf01:~$ 

This is a known issue that is currently being investigated.

 

RN-855 (CM-20057)
The 'netq check evpn' command does not show correct results The netq check evpn command does not provide correct layer 3 EVPN information. The VNI membership for symmetric routing is incorrect.
This is a known issue that is currently being investigated.

RN-856 (CM-18940)
The NTP agent state does not sync when management VRF is enabled

The NTP Agent State column does not change to Yes after you move the NetQ Agent from the default VRF to the management VRF.

This is a known issue that is currently being investigated.


RN-857 (CM-18325)
No support for custom sentinel ports in HA mode

There is currently no support for custom sentinel ports in HA configuration; only the default port 26379 is supported.

This is a known issue that is currently being investigated.


RN-858 (CM-20383)
Docker connectivity and adjacent options are not shown

NetQ does not show connectivity or adjacency information for a given Docker node in a swarm cluster.

This is a known issue that is currently being investigated.


RN-859 (CM-20425)
The Telemetry Server GUI Portainer does not support user names with a dash (-) If a username contains a dash (-), an error is seen when logging in through the Portainer GUI.
This is a known issue that is currently being investigated.
Have more questions? Submit a request

Comments

Powered by Zendesk