Cumulus NetQ 1.2.0 Release Notes

Follow

Overview

These release notes support Cumulus NetQ 1.2.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.2.0

Cumulus NetQ 1.2.0 includes the following features:

  • High availability: Configure the NetQ telemetry server in high availability mode for redundancy and better robustness.

Early Access Support

NetQ 1.2.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 now 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 uses FRRouting as its routing suite; NetQ 1.1 does not work with Quagga or Cumulus Routing on the Host. 
  • 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.1 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.2.0

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

Release Note ID Summary Description

RN-619 (CM-16684)
`netq NODE show stp topology` shows wrong information when on node bridge link is down

When the hard node bridge link is brought down, running netq NODE show stp topology displays incorrect information. The expected output should be similar to what is displayed when mstpd is stopped:

No bridges found

This issue is fixed in Cumulus NetQ 1.2.0.


RN-620 (CM-16432)
When stopping and starting mstpd, `netq show services changes` displays two events

In this instance, the NetQ agent is reporting two events, because one reports the service is in "error" and the other says the service is "failed". However, in both cases the service is actually stopped, so the NetQ CLI shows the status as "n/a", causing them to look like two events without any difference.

While the issue is benign, it can potentially trigger an alarm event, even when the service did not actually change state.

cumulus@leaf01:~$ sudo systemctl stop mstpd ; sudo systemctl start mstpd 
cumulus@leaf01:~$ netq mlx-2700-03 show services mstpd changes 
Matching services records are:
Node         Service      PID  VRF      Enabled    Active    Monitored    Status    Up Time    DbState    Last Changed
-----------  ---------  -----  -------  ---------  --------  -----------  --------  ---------  ---------  --------------
mlx-2700-03  mstpd      10917  default  yes        yes       yes          ok        14s ago    Add        2s ago
mlx-2700-03  mstpd          0  default  yes        no        yes          n/a       22m ago    Add        14s ago
mlx-2700-03  mstpd          0  default  yes        no        yes          n/a       22m ago    Add        17s ago
mlx-2700-03  mstpd       9211  default  yes        yes       yes          ok        22m ago    Add        22m ago
mlx-2700-03  mstpd          0  default  yes        no        yes          n/a       24m ago    Add        22m ago
mlx-2700-03  mstpd          0  default  yes        no        yes          n/a       24m ago    Add        22m ago
mlx-2700-03  mstpd       9015  default  yes        yes       yes          error     24m ago    Add        22m ago
mlx-2700-03  mstpd       9015  default  yes        yes       yes          ok        24m ago    Add        24m ago
mlx-2700-03  mstpd          0  default  yes        no        yes          n/a       56m ago    Add        24m ago
mlx-2700-03  mstpd          0  default  yes        no        yes          n/a       56m ago    Add        24m ago
mlx-2700-03  mstpd        429  default  yes        yes       yes          ok        56m ago    Add        37m ago
mlx-2700-03  mstpd        429  default  yes        yes       no           ok        56m ago    Add        37m ago
mlx-2700-03  mstpd        429  default  yes        yes       yes          ok        56m ago    Add        50m ago
mlx-2700-03  mstpd        429  default  yes        yes       no           ok        56m ago    Add        50m ago

This issue is fixed in Cumulus NetQ 1.2.0.


RN-621 (CM-16710)
The regular expression for hostname does not work with the `netq NODE show agents command`

The regular expression syntax between Python and the backend database are different, causing support for more complex regular expressions difficult at this time.

To work around this issue, use tab completion to get the full hostname and specify it directly.

The regular expressions that are usable are:

    - '*': matches zero or more of any char, so leaf* matches leaf01, leaf02 ...
    - '?': matches exactly zero or one char
    - [0-9]: matches exactly one char that is a number between 0-9
    - [a-zA-Z]: matches exactly one char that is a letter between a-z or A-Z
    - [-1-2]*: matches zero or more chars that are either -, 1 or 2

This issue is fixed in Cumulus NetQ 1.2.0.


RN-625 (CM-16717)
NetQ does not support high availability (HA) mode HA support is available in NetQ 1.2.0.

RN-655 (CM-17909)
When node is rotten, various sensors commands fail with this error: "Value s_input(0) should be of type(s) <type 'float'> but is of type <type 'int'>"

If a node is identified by NetQ as "rotten," the following sensors commands fail with this message: "Value s_input(0) should be of type(s) <type 'float'> but is of type <type 'int'>"

  • netq show sensors all
  • netq show sensors temp
  • netq <hostname of rotten node> show sensors all
  • netq <hostname of rotten node> show sensors temp

To work around this issue, you can view sensors for individual hosts that are not rotten. For example:

cumulus@leaf01:~$ netq <hostname> show sensors all

This issue is fixed in Cumulus NetQ 1.2.0.

Known Issues in Cumulus NetQ 1.2.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-618 (CM-16660)
Some platforms display "N/A" when `netq show inventory asic` is run

NetQ does not return data for certain platforms when netq show inventory asic is run. The text "N/A" appears instead:

cumulus@leaf01:~$ netq show inventory asic
Node                Vendor    Model     Model ID    Core B/W    Ports
------------------  --------  --------  ----------  ----------  -----------------------------
act-7412-03         N/A       N/A       N/A         N/A         N/A
dell-s4000-04       Broadcom  Trident2  BCM56854    720G        48 x 10G-SFP+ & 6 x 40G-QSFP+
dell-s4000-05       Broadcom  Trident2  BCM56854    720G        48 x 10G-SFP+ & 6 x 40G-QSFP+
dell-z9100-03       Broadcom  Tomahawk  BCM56960    2.0T        32 x 100G-QSFP28
mlx-2700b-01        N/A       N/A       N/A         N/A         N/A
qct-ix1-08          N/A       N/A       N/A         N/A         N/A
qct-ly9rangeley-06  Broadcom  Trident2  BCM56854    720G        48 x 10G-T & 6 x 40G-QSFP+
qct-ly9rangeley-07  Broadcom  Trident2  BCM56854    720G        48 x 10G-T & 6 x 40G-QSFP+

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-623 (CM-14541)
Rotten nodes are not highlighted in `netq show` commands  

If a node is in rotten state, it doesn't get highlighted in any netq show output. For example:

cumulus@leaf01:~$ netq show ip route 1.2.3.4
Route info about prefix 1.2.3.4 on host *
Origin Table    IP               Node             Nexthops                  Last Changed
------ -------- ---------------- ---------------- ------------------------- ----------------
0      DataVrf1 0.0.0.0/0        msp1             Blackhole                 47m ago
       080
0      DataVrf1 0.0.0.0/0        msp2             Blackhole                 47m ago  >> From rotten node
       080
0      DataVrf1 0.0.0.0/0        superm-redxp-01  Blackhole                 46m ago  >> From rotten node
       080
0      DataVrf1 0.0.0.0/0        torb1            Blackhole                 46m ago
       080

RN-624 (CM-16342)
You cannot pipe a `netq` command to another `netq` command

Attempting to pipe a netq command into another netq command results in an interrupt in the console. For example:

cumulus@oob-mgmt-server:~$ netq show ip routes |netq resolve
^CTraceback (most recent call last):
  File "/usr/bin/netq", line 316, in 
    reply = rx_reply(sock)
  File "/usr/bin/netq", line 131, in rx_reply
    ready = select([sock], [], [], timeout)
KeyboardInterrupt

RN-626 (TSG-20)
Issues resizing NetQ Service Console window

The NetQ Service Console does not handle resizing of the browser window very well, which may cause text in the console to wrap.

To work around this issue, do not resize the browser window once you launch the console.


RN-627
No synchronization between users added via the service console and the telemetry server users

Users created in the NetQ Service Console are not synchronized with the users for the NetQ Telemetry Server.

To work around this issue, you must manually sync the user IDs between the telemetry server and the service console.


RN-628
The NetQ CLI and NetQ Notifier are supported on x86 platforms only At this time, the NetQ command line interface and NetQ Notifier can run on x86 switches and hosts only.

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

 
Have more questions? Submit a request

Comments

Powered by Zendesk