This knowledge base has moved to the documentation site. Please visit the knowledge base here for the most up to date content. This site is no longer maintained.

Cumulus Linux 3.1.2 Release Notes



These release notes support Cumulus Linux 3.1.2 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.


What's New in Cumulus Linux 3.1.2

Cumulus Linux 3.1.2 includes bug fixes as well as the following early access feature.

Early Access Features

Cumulus Linux 3.1.2 provides early access support for the Edge-Core 5812-54X platform.



Cumulus Linux is licensed on a per-instance basis. Each network system is fully operational, enabling any capability to be utilized on the switch with the exception of forwarding on switch panel ports. Only eth0 and console ports are activated on an un-licensed instance of Cumulus Linux. Enabling front panel ports requires a license.

You should have received a license key from Cumulus Networks or an authorized reseller. To install the license, read the Cumulus Linux Quick Start Guide.

Installing Version 3.1.2

If you are upgrading from version 3.0.0 or later, use apt-get to update the software.

  1. Run apt-get update.
  2. Run apt-get upgrade.
  3. Reboot the switch.

New Install or Upgrading from Versions Older than 3.0.0

If you are upgrading from a version older than 3.0.0, or installing Cumulus Linux for the first time, download the Cumulus Linux 3.1.1 installer for Broadcom or Mellanox switches from the Cumulus Networks website, then use ONIE to perform a complete install, following the instructions in the quick start guide.

Note: This method is destructive; any configuration files on the switch will not be saved, so please copy them to a different server before upgrading via ONIE.

Important! After you install, run apt-get update, then apt-get upgrade on your switch to make sure you update Cumulus Linux to include any important or other package updates.

Updating a Deployment that Has MLAG Configured

If you are using MLAG to dual connect two switches in your environment, and those switches are still running Cumulus Linux 2.5 ESR or any other release earlier than 3.0.0, the switches will not be dual-connected after you upgrade the first switch. To ensure a smooth upgrade, follow these steps:

  1. Run cl-img-select -fr to boot the switch in the secondary role into ONIE, then reboot the switch.
  2. Install Cumulus Linux 3.1.2 onto the secondary switch using ONIE. At this time, all traffic is going to the switch in the primary role.
  3. After the install, copy the license file and all the configuration files you backed up, then restart the switchd and networking services.
    cumulus@switch:~$ sudo systemctl restart switchd.service
    cumulus@switch:~$ sudo systemctl restart networking.service
    All traffic is still going to the primary switch.
  4. Run cl-img-select -fr to boot the switch in the primary role into ONIE, then reboot the switch. Now, all traffic is going to the switch in the secondary role that you just upgraded to version 3.1.2.
  5. Install Cumulus Linux 3.1.2 onto the primary switch using ONIE. 
  6. After the install, copy the license file and all the configuration files you backed up, then restart the switchd and networking services.
    cumulus@switch:~$ sudo systemctl restart switchd.service
    cumulus@switch:~$ sudo systemctl restart networking.service
  7. Now the two switches are dual-connected again and traffic flows to both switches.

 SNMP Not Supported in Quagga

There is no SNMP support for Quagga in Cumulus Linux. However, it's possible to get it via SNMP by:

  • Using Nagios
  • Writing a pass persist script in Perl or Python by filling in the OSPF or BGP (rfc) MIBs manually.
  • Creating your own private MIB for the information you need.

Due to this circumstance, you must remove all references to smux in each of the following configuration files. You must also remove these references before upgrading Cumulus Linux using apt-get. If the smux entries are present in the configuration files, the daemons in the 2.5 packaged version of Quagga will not start.

  1. cd /etc/quagga
  2. grep smux *
  3. Delete all lines in the config files containing the smux keyword.

The references to smux that must be removed are:

  • In bgpd.conf, remove this line:
    smux peer quagga_bgpd
  • In ospf6d.conf, remove this line:
    smux peer quagga_ospf6d
  • In ospfd.conf, remove this line:
    smux peer quagga_ospfd
  • In zebra.conf, remove this line:
    smux peer quagga_zebra

 Perl, Python and BDB Modules

Any Perl scripts that use the DB_File module or Python scripts that use the bsddb module won't run under Cumulus Linux 3.1.2.


You can read the technical documentation here.

Issues Fixed in Cumulus Linux 3.1.2

The following is a list of issues fixed in Cumulus Linux 3.1.2 from earlier versions of Cumulus Linux.

Release Note ID Summary Description

RN-487 (CM-12500)
Trident SBUSDMA Timeout Issues

Some Trident II and Trident II+ switches exhibit SBUSDMA timeout issues with a maximum payload of 128B, and occasionally with 256B.

This issue has been fixed.

RN-499 (CM-12998)
refcnt Handling Error When Configuring dhcrelay

When configuring dhcpd (or dhcrelay) with interface listings that either didn't exist, had a socket failure, or did not have an IP assigned, an error occurred that caused the interface object to have a refcnt of 1, which subsequently goes to 0 when a netlink event occurs and the netlink handler moves the object from one list to another. The refcnt handling has been fixed.

RN-500 (CM-12982)
bond0 interface error when VRF and address-virtual are configured

An error occurred when issuing an ifdown on a bond0 interface configured with both address-virtual and vrf. Two paths from the bridge to the VRF device caused ifdown to hang, forcing the switch to be rebooted. An update has corrected this issue.

RN-501 (CM-8736)
Unexpected MTU sizes on SVI interface after ifreload By default, ifupdown2 will adjust logical devices MTU based on the physical interface they are running on top of. To disable this behavior, set the adjust_logical_dev_mtu flag to 0.

RN-502 (CM-12906)
ifupdown2 accepts subinterface on VLAN-aware bridge, programs as traditional bridge When a port subinterface was configured as a bridge-port on a VLAN-aware bridge, ifupdown2 programmed it as a traditional bridge instead. How ifupdown2 parses interfaces has been corrected, and this error has been fixed.

RN-503 (CM-12942)
Spectrum Boxes Failed Acoustic Testing An issue occurred where spectrum boxes were failing acoustic testing due to incorrect temp_max and temp_crit values. This has been corrected.

RN-504 (CM-13344)
Install fails due to partition layout on attached usb storage The Cumulus Linux installer would fail when a USB stick containing the Dell S4000 ONIE recovery ISO was inserted. This was caused by a recursive partition error from partprobe, as the ISO contains its own partitions. partprobe now only checks the install device, rather than all devices, and the error has been resolved.

RN-505 (CM-13343)
switchd memory seems to leak resulting in oom-killer after continued swp transitions/fdb churn Continued interface changes and the generation of fdb entries caused a gradual reduction in free memory, resulting in oom-killer bringing down switchd. This issue has been fixed.

RN-506 (CM-13237)
CVE-2016-5195: Dirty CoW Vulnerability

A Linux kernel vulnerability was found, that allowed for the copy-on-write mechanism to be exploited in order to escalate privileges. This security issue has been fixed upstream, and included in Cumulus 3.1.2.

For more information, refer here:

RN-507 (CM-13169)
LACP bypass on tagged bridges with VXLAN member not working Several connected defects related to VXLAN active-active and LACP-bypass caused a number of different errors. These issues have been corrected, and all errors are resolved.

RN-508 (CM-12588)
Dell S6000 - portwd: invalid SFF identifier: 0x00 syslog showed repeated portwd: invalid SFF identifier: 0x00 errors on Dell S6000s running Cumulus Linux 3.0.0. This was determined to be the result of the setup time allocated to the module. This issue has now been corrected.

RN-510 (CM-13329)
switchd VLAN Entry not found Several connected defects related to VXLAN active-active and LACP-bypass caused a number of different errors. These issues have been corrected, and all errors are resolved.

Issues Fixed in Cumulus Linux 3.1.2 Update

Cumulus Networks has made important package updates available for Cumulus Linux 3.1.2 that resolve the issues listed below.

Cumulus Networks strongly recommends you upgrade your Cumulus Linux distribution to avoid these issues (do not do a binary install). Follow these steps:

  1. Run apt-get update.
  2. Run apt-get upgrade.
  3. While not required, it's a good idea to reboot the switch.
Release Note ID Summary Description

RN-275 (CM-5794)
BGP import-check fails for IPv6 route if static routes to null0 are used

The path that Cumulus Linux originates should not be invalid since there is a matching route in the RIB. The import check works fine for IPv4 routes.

RN-477 (CM-12827)
switchd dumps core on Edge-Core AS5712-54X switch

This issue was seen when a vxlan-local-tunnelip address was configured for a VTEP.

This issue is fixed in Cumulus Linux 3.1.1.

RN-511 (CM-13137)
SNMP cumulus-counters MIB doesn't support 64 bit counters

The cumulus-counters MIB only supported 32-bit counters, which is not sufficient for higher bandwidth interfaces.

This issue has been fixed in the update to the 3.1.2 repository.

RN-512 (CM-12458)
snmpd does not correctly populate the BRIDGE-MIB when the bridge interface is named "bridge"

This has two unintended consequences:

  • A message was logged indicating that more than one bridge was found.
  • An interface was found to be a member of "bridge" instead of an interface type of bridge

This issue has been fixed in the update to the 3.1.2 repository.

RN-513 (CM-12821)
SNMP BGP MIB has incorrect bgpPeerLocalAddr, bgp4PathAttrASPathSegment and bgpPeerLastError elements

This issue resulted in these effects:

  • The bgpPeerLocalAddr was being returned as 0 instead of
  • bgp4PathAttrASPathSegment and bgpPeerLastError were returning strings instead of octet strings

This issue has been fixed in the update to the 3.1.2 repository.

RN-514 (CM-12163)
Q-BRIDGE-MIB dot1qVlanMib class missing some table entries

This issue has been fixed in the update to the 3.1.2 repository.

RN-515 (CM-13427)
snmpd script fails to run due to traceback

The script returned a traceback when running in debug mode.

This issue has been fixed in the update to the 3.1.2 repository.

RN-516 (CM-13497)
SNMP BGP4 MIB doesn't show bgpPeerLocalAddr correctly

The peer local IP address was displayed as all zeros, not the actual IP address.

This issue has been fixed in the update to the 3.1.2 repository.

RN-517 (CM-12486)
switchd crash on Helix4 switches

An issue with IPMC init on Helix4 switches caused switchd to crash.

This issue has been fixed in the update to the 3.1.2 repository.

RN-518 (CM-13328)
Quagga sometimes installs a duplicate static route

After a Cumulus Linux switch with VRF routes installed was rebooted, the VRF routes were present in the kernel but not installed into hardware. Restarting Quagga resolved the issue.

This issue has been fixed in the update to the 3.1.2 repository.

Known Issues in Cumulus Linux 3.1.2

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

Release Note ID Summary Description

RN-52 (CM-997,
Parameters like the router ID and DR priority cannot be changed while OSPFv2/v3 is running Router ID and DR priority can only be changed by shutting down OSPFv2/v3, changing the ID, and restarting the OSPF process.

A change to the DR priority may not properly be reflected in the LSAs that are still aging out.

RN-56 (CM-343)
IPv4/IPv6 forwarding disabled mode not recognized

If either of the following is configured:

net.ipv4.ip_forward == 0 


net.ipv6.conf.all.forwarding == 0 

The hardware still forwards packets if there is a neighbor table entry pointing to the destination.

RN-77 (CM-265)
New routes/ECMPs can evict existing/installed Cumulus Linux syncs routes between the kernel and the switching silicon. If the required resource pools in hardware fill up, new kernel routes can cause existing routes to move from being fully allocated to being partially allocated.

In order to avoid this, routes in the hardware should be monitored and kept below the ASIC limits.

For example, on systems with Trident+ chips, the limits are as follows:
routes: 16384 <<<< if all routes are ipv4 
 long mask routes 256 <<<< i.e., routes with a mask longer 
       than the route mask limit 
 route mask limit 64
 host_routes: 8192 
 ecmp_nhs: 4044 
 ecmp_nhs_per_route: 52 
That translates to about 77 routes with ECMP NHs, if every route has the maximum ECMP NHs.

Monitoring this in Cumulus Linux is performed via the cl-resource-query command:
cumulus@switch:~$ sudo cl-resource-query
 hosts : 3 
 all routes : 29 
 IP4 routes : 17 
 IP6 routes : 12 
 nexthops : 3 
 ecmp_groups : 0
 ecmp_nexthops : 0
 mac entries : 0 / 131072 
 bpdu entries : 500 / 512
The resource to monitor is the ecmp_nexthops. If this count is close to 4044, new ECMPs may evict existing routes.

RN-120 (CM-477)
ethtool LED blinking does not work with switch ports Linux uses ethtool -p to identify the physical port backing an interface, or to identify the switch itself. Usually this identification is by blinking the port LED until ethtool -p is stopped.

This feature does not apply to switch ports (swpX) in Cumulus Linux.

RN-121 (CM-2123)
PTMD: When a physical interface is in a PTM FAIL state, its subinterface still exchanges information Issue:
When PTMD is incorrectly in a failure state and the Zebra interface is enabled, PIF BGP sessions are not establishing the route, but the subinterface on top of it does establish routes.

If the subinterface is configured on the physical interface and the physical interface is incorrectly marked as being in a PTM FAIL state, routes on the physical interface are not processed in Quagga, but the subinterface is working.

Steps to reproduce:
cumulus@switch:$ sudo vtysh -c 'show int swp8' 
Interface swp8 is up, line protocol is up 
PTM status: fail
index 10 metric 1 mtu 1500 
 HWaddr: 44:38:39:00:03:88 
 inet broadcast 
 inet6 2001:cafe:0:38::1/64 
 inet6 fe80::4638:39ff:fe00:388/64 
cumulus@switch:$ ip addr show | grep swp8 
  mtu 1500 qdisc pfifo_fast state UP qlen 500 
  inet brd scope global swp8 
 104: swp8.2049@swp8: <BROADCAST,MULTICAST,UP,LOWER_UP> 
  mtu 1500 qdisc noqueue state UP 
  inet brd scope global swp8.2049 
 105: swp8.2050@swp8: <BROADCAST,MULTICAST,UP,LOWER_UP> 
  mtu 1500 qdisc noqueue state UP 
  inet brd scope global swp8.2050 
 106: swp8.2051@swp8: <BROADCAST,MULTICAST,UP,LOWER_UP> 
  mtu 1500 qdisc noqueue state UP 
  inet brd scope global swp8.2051 
 107: swp8.2052@swp8: <BROADCAST,MULTICAST,UP,LOWER_UP> 
  mtu 1500 qdisc noqueue state UP 
  inet brd scope global swp8.2052 
 108: swp8.2053@swp8: <BROADCAST,MULTICAST,UP,LOWER_UP>
  mtu 1500 qdisc noqueue state UP 
  inet brd scope global swp8.2053 
 109: swp8.2054@swp8: <BROADCAST,MULTICAST,UP,LOWER_UP> 
  mtu 1500 qdisc noqueue state UP 
  inet brd scope global swp8.2054
 110: swp8.2055@swp8: <BROADCAST,MULTICAST,UP,LOWER_UP>
  mtu 1500 qdisc noqueue state UP 
  inet brd scope global swp8.2055
cumulus@switch:$ bgp sessions: ,4 ,64057 , 958 , 1036 , 0 , 0 , 0 ,15:55:42, 0, 10472 ,4 ,64058 , 958 , 1016 , 0 , 0 , 0 ,15:55:46, 187, 10285 ,4 ,64059 , 958 , 1049 , 0 , 0 , 0 ,15:55:40, 187, 10285 ,4 ,64060 , 958 , 1039 , 0 , 0 , 0 ,15:55:45, 187, 10285 ,4 ,64061 , 958 , 1014 , 0 , 0 , 0 ,15:55:46, 187, 10285 ,4 ,64062 , 958 , 1016 , 0 , 0 , 0 ,15:55:46, 187, 10285 ,4 ,64063 , 958 , 1029 , 0 , 0 , 0 ,15:55:43, 187, 10285 ,4 ,64064 , 958 , 1036 , 0 , 0 , 0 ,15:55:44, 187, 10285 

RN-125 (CM-1576)
Network LSA with an old router ID isn't flushed out by the originator
When the router ID is changed, the router should remove the previous network LSA (link-state advertisement) that it generated based on the IP address on the interface in the Network LSA.

Cumulus Networks doesn't remove this LSA, so it will be naturally aged out.

RN-132 (CM-2272)
You must run "apt-get update" before running any apt-get commands or after changing sources.list

Before running any apt-get commands or after changing the source.list file in /etc/apt, you need to run apt-get update.

RN-133 (CM-2273)
Interface names in Cumulus Linux cannot exceed 16 characters

Device names, including interface names, in Cumulus Linux cannot exceed 16 characters – including the terminator. Cumulus Linux truncates longer interface names.

To avoid this issue, do not assign long names to your interfaces.

The following example configuration reproduces this issue:

cumulus@switch:/sys/class/net$ grep 'iface br' /etc/network/interfaces 
iface br2-pubmgmt inet static
iface br3-prvmgmt inet manual
iface br400-quarantine inet manual
iface br401-peering-1k5 inet manual
iface br402-peering-9k inet manual
iface br500-pi-exa inet manual
iface br501-akamai-exa inet manual
iface br502-exa-internetfactory inet manual
cumulus@switch:/sys/class/net$ brctl show | grep br
bridge name	bridge id	 STP enabled	interfaces
br2-pubmgmt	 8000.089e01cebe37	no	 bond0.2
br3-prvmgmt	 8000.089e01cebe3a	no	 bond0.3
br400-quarantin	 8000.089e01cebe37	no	 bond0.400
br401-peering-1	 8000.089e01cebe3a	no	 bond0.401 <<<

RN-198 (CM-3290)
Port LEDs behave differently on different switch models

It's been observed that port LEDs behave differently depending upon the make and model of the switch. For example:

  • Agema AG-7448CU: the LED is off when the link is up. It blinks on briefly when there is traffic.
  • Edge-Core AS4600-54T: the LED is off when the link is up. It blinks on briefly when there is traffic.
  • QuantaMesh T3048-LY2R: the LED is on when the link is up. It blinks off briefly when there is traffic.

Cumulus Networks is currently working to fix this issue.

RN-199 (CM-2624)
When a Quagga route-map is modified, the switch could use the partial map before edits are completed

Cumulus Linux triggers a route-map update before the user finishes editing the route map, resulting in an incorrect route map being used. The route-map update trigger should only occur when user finishes editing the map.

Cumulus Networks is working to fix this issue.

RN-221 (CM-4501)
BGP graceful restart, including helper mode, not fully supported If you encounter issues with this, please submit a support request and include the output from cl-support with your ticket.

RN-227 (CM-3388)
BGP dynamic capability is not supported BGP peer sessions with dynamic capability are not supported under any version of Cumulus Linux at this time.

RN-322 (CM-7387)
Interfaces disabled using iproute2 become enabled after restarting Quagga By default, all interfaces have a "no shutdown" associated with them in Quagga. Thus, when you restart Quagga, it enables the interfaces. This is expected behavior in Quagga. There is no workaround at this time.

RN-327 (CM-4290)
Changing the route-map parameter of the redistribute command in OSPF and BGP doesn't affect the state of the resulting redistribution in those protocols

To work around this issue, remove any old redistribute command configurations before adding a new one with or without route-map as a parameter.

For example, if OSPF has a redistribute configuration such as redistribute bgp route-map redist-map-name, you would enable redistribution without a route-map by following these steps in OSPF configuration mode:

  1. no redistribute bgp
  2. redistribute bgp

You would perform a similar sequence of commands for redistribution changes in BGP as well.

RN-355 (CM-7994)
OSPFv2 Area ID being implicitly translated from Integer format to dotted decimal format

While OSPF area ID configuration in Quagga allows for the value to be specified in either dotted decimal format, or as an integer, values specified as an integer will be converted into dotted decimal format when displayed, causing potential confusion for the operator.

This issue does not impact OSPF functionality; only the display output. However, it is recommended that the OSPF area ID is specified in dotted decimal format for consistency.


RN-380 (CM-6110)
ifupdown2: adjust VLAN subinterface MTU based on MTU settings specified under lowerdev by the user

The following kernel error occurs when the MTU is specified under a subinterface rather than under the VLAN interface:

root@dell-s3000-04:~# ifreload -a -X eth0
warning: failed to execute cmd 'ip -force -batch - [addr add dev swp52.100
link set dev swp52.100 mtu 9000 
]'(RTNETLINK answers: Numerical result out of range
Command failed -:2)

This issue is being investigated.

RN-382 (CM-6692)
Quagga: Removing bridge via ifupdown2 does not remove it from Quagga Removing a bridge using ifupdown2 does not remove it from the Quagga configuration files. This issue is being investigated; however, restarting Quagga will successfully remove the bridge.

RN-383 (CM-7196)
admin down of link deletes IPv6 nexthop static route entry, but not for IPv4

When a link is admin down and carrier is on, the IPv4 nexthop entry is marked dead, but the IPv6 nexthop entry is deleted, and will not be restored when the link is admin up. However, if carrier is off, the IPv6 nexthop is marked dead and not deleted. This inconsistency in admin down behavior is being investigated.

RN-384 (CM-7684)
Keeping VXLAN single-connected devices up on MLAG secondary node In the current MLAG secondary design, if the VXLAN device is not dual-connected, it is kept in a protodown state. You can keep them up with individual IP addresses rather than anycast IPs when the peerlink is down, so that all single-connected hosts will have connectivity. Further investigation regarding this issue is underway.

RN-387 (CM-8163)
Quagga appears to not honor passive interfaces if VRR is active

In a VRR configuration, any interface-specific routing configuration (e.g., OSPF mode of operation) specified on the subinterface having a virtual IP address does not take effect. This is because when an operator has specified a virtual IP on a bridge, the system creates another internal interface bridge with the virtual IP and MAC. These two interfaces are treated distinctly by Quagga, so any interface-specific routing configuration on the bridge does not get carried over to the second bridge.

In a VRR deployment needing any interface-specific routing configuration on the interface with a virtual IP address, the routing configuration has to be specified against the internally-created virtual interface also.

RN-389 (CM-8410)
switchd supports only port 4789 as the UDP port for VXLAN packets

switchd currently allows only the standard port 4789 as the UDP port for VXLAN packets. There are cases where a hypervisor could be using non-standard UDP port, which would cause VXLAN exchanges with the hardware VTEP to not work. In such a case, packets would not be terminated and encapsulated packets would be sent out on UDP port 4789.

RN-390 (CM-9055)
If you’re logged into the serial console and type reboot, the system may hang indefinitely

In Cumulus Linux, if the serial console terminal settings are changed and clocal (modem carrier) is turned off,  systemd may do all of the following:

  • Block and stop handling systemctl changes
  • Fail to start or restart services
  • Prevent reboot and shutdown

For example, running the /usr/bin/reset command may cause this problem when run on the serial console. Once in this state, a new login session will not be started on the serial console (/dev/ttyS0 or ttyS1) after logout, and systemd will not respond to systemctl commands, including reboot.

To work around this issue, whenever you are logged in to the serial console and run reset, run stty clocal afterwards.

RN-391 (CM-9631)
Dell S4048 unresponsive after TX Unit Hang detected

After booting a Dell S4048 switch, the switch becomes unresponsive and errors like the following appear in the console log:

[ 1206.440277] igb 0000:00:14.0: Detected Tx Unit Hang
[ 1206.440277]   Tx Queue             <0>
[ 1206.440277]   TDH                  <2d>
[ 1206.440277]   TDT                  <2e>
[ 1206.440277]   next_to_use          <2e>
[ 1206.440277]   next_to_clean        <2d>
[ 1206.440277] buffer_info[next_to_clean]
[ 1206.440277]   time_stamp           <1000dcd20>
[ 1206.440277]   next_to_watch        <ffff88007d81b2d0>
[ 1206.440277]   jiffies              <1000dd5d4>
[ 1206.440277]   desc.status          <300000>
[ 1208.439856] igb 0000:00:14.0: Detected Tx Unit Hang
[ 1208.439856]   Tx Queue             <0>
[ 1208.439856]   TDH                  <2d>
[ 1208.439856]   TDT                  <2e>
[ 1208.439856]   next_to_use          <2e>
[ 1208.439856]   next_to_clean        <2d>
[ 1208.439856] buffer_info[next_to_clean]
[ 1208.439856]   time_stamp           <1000dcd20>
[ 1208.439856]   next_to_watch        <ffff88007d81b2d0>
[ 1208.439856]   jiffies              <1000ddda4>
[ 1208.439856]   desc.status          <300000>
[ 1210.439414] igb 0000:00:14.0: Detected Tx Unit Hang
[ 1210.439414]   Tx Queue             <0>
[ 1210.439414]   TDH                  <2d>
[ 1210.439414]   TDT                  <2e>
[ 1210.439414]   next_to_use          <2e>
[ 1210.439414]   next_to_clean        <2d>
[ 1210.439414] buffer_info[next_to_clean]
[ 1210.439414]   time_stamp           <1000dcd20>
[ 1210.439414]   next_to_watch        <ffff88007d81b2d0>
[ 1210.439414]   jiffies              <1000de574>
[ 1210.439414]   desc.status          <300000>
[ 1212.438966] igb 0000:00:14.0: Detected Tx Unit Hang
[ 1212.438966]   Tx Queue             <0>
[ 1212.438966]   TDH                  <2d>
[ 1212.438966]   TDT                  <2e>
[ 1212.438966]   next_to_use          <2e>
[ 1212.438966]   next_to_clean        <2d>
[ 1212.438966] buffer_info[next_to_clean]
[ 1212.438966]   time_stamp           <1000dcd20>
[ 1212.438966]   next_to_watch        <ffff88007d81b2d0>
[ 1212.438966]   jiffies              <1000ded44>
[ 1212.438966]   desc.status          <300000>
[ 1212.490329] igb 0000:00:14.0 eth0: Reset adapter

Rebooting the switch again stops the behavior.

RN-404 (CM-4407)
Aggregating routes in BGP with as-set can result in high CPU usage

When BGP is configured with aggregate addresses with as-set configuration and there are many routes to be aggregated, the BGP process gets into high CPU usage.

To work around this issue, do not specify the as-set parameter for the aggregate-address configuration.

RN-409 (CM-10054)
BGP may show an inaccessible path as the best path

Existing BGP issues caused peering between a VRF device and a loopback BGP session to stay up if the loopback session doesn’t advertise its local address.

This issue will be fixed in a future release.

RN-412 (CM-11162)
Spectrum switches have a CPU RX burst size of 128 packets per queue

On switches with Mellanox Spectrum ASICs the burst size for packets received at the CPU is limited to 128 packets per queue. Larger bursts can result in packet drops until packets are drained from the queue.


RN-414 (CM-11175)
Kernel source not added to Cumulus Networks repository

Kernel source (linux<vers>.orig.tar.xz and linux<vers>.debian.tar.xz) files are not being added properly to the Cumulus Networks repository.

You can retrieve these packages manually with apt-get source <package name>. For example, to retrieve the Cumulus Networks linux-image source package, run:

cumulus@switch:~$ sudo apt-get install linux-source-4.1

The archive file is stored at /usr/src/linux-source-4.1.tar.xz.

RN-445 (CM-12370)
An interface cannot have both inet and inet6 DHCP configurations

If you configure an interface so it can to obtain both IPv4 and IPv6 IP addresses via DHCP, ifupdown2 will honor only the first configuration and ignore the second.

In the following example configuration, ifupdown2 will only issue an IPv4 DHCP address for swp1, but not the IPv6 address.

auto swp1
iface swp1 inet dhcp
    link-speed 10000
    link-duplex full
    link-autoneg off

auto swp1
iface swp1 inet6 dhcp

This is a known issue that should be fixed in a future release of Cumulus Linux.

RN-446 (CM-10513)
Redistribute neighbor does not work with more than 1024 interfaces

The rdnbrd service crashes because it cannot work with more than 1024 interfaces.

This issue should be fixed in a future release of Cumulus Linux.

RN-447 (CM-11280)
"portwd: invalid SFF identifier: 0x0c" messages appear continuously in syslog

The following SFF message appears every 5 seconds in syslog:

cumulus@switch:~$ tail -f /var/log/syslog 
2016-08-06T12:18:56.095606-04:00 cumulus portwd: invalid SFF identifier: 0x0c
2016-08-06T12:19:01.113397-04:00 cumulus portwd: invalid SFF identifier: 0x0c
2016-08-06T12:19:01.121068-04:00 cumulus portwd: invalid SFF identifier: 0x0c
2016-08-06T12:19:01.121698-04:00 cumulus portwd: invalid SFF identifier: 0x0c
2016-08-06T12:19:06.139373-04:00 cumulus portwd: invalid SFF identifier: 0x0c
2016-08-06T12:19:06.147045-04:00 cumulus portwd: invalid SFF identifier: 0x0c
2016-08-06T12:19:06.147677-04:00 cumulus portwd: invalid SFF identifier: 0x0c
2016-08-06T12:19:11.165355-04:00 cumulus portwd: invalid SFF identifier: 0x0c
2016-08-06T12:19:11.173134-04:00 cumulus portwd: invalid SFF identifier: 0x0c
2016-08-06T12:19:11.173747-04:00 cumulus portwd: invalid SFF identifier: 0x0c
2016-08-06T12:19:16.191418-04:00 cumulus portwd: invalid SFF identifier: 0x0c
2016-08-06T12:19:16.199154-04:00 cumulus portwd: invalid SFF identifier: 0x0c
2016-08-06T12:19:16.199805-04:00 cumulus portwd: invalid SFF identifier: 0x0c

This is a known issue that should be fixed in a future version of Cumulus Linux.

RN-448 (CM-11302)
Using the json option in the "show ip bgp" command causes peer session flaps

This issue causes peer session flaps on Penguin Arctica 4806XP and Supermicro SSE-X3648S switches. It occurs with 16K IPv4 prefixes and only when you run show ip bgp json.

However, on switches with Tomahawk ASICs, with 61K IPv4 prefixes and default timers, the same show ip bgp json command causes all peer sessions to go down.

This is a known issue that should be fixed in a future release of Cumulus Linux.

RN-449 (CM-11584)
In traditional bridge mode, clagd syncs MAC addresses in the wrong VLAN when the peerlink is tagged and the bond is native

When a traditional mode bridge is configured and the peerlink is tagged but the clagd bonds are native VLANs, clagd appears to try and sync the MAC addresses learned using the VLAN tag from the peerlink.

This causes the MAC address not to be synced correctly on the peer.

This is a known issue that should be fixed in a future release of Cumulus Linux.

RN-450 (CM-12252)
802.1p remark in traffic.conf behaves differently on Mellanox vs. Broadcom switches

The 802.1p remark defined in traffic.conf acts differently on a Mellanox switch when compared to a Broadcom switch.

On the Mellanox platform, the remark defined in the traffic.conf file takes precedence even if there is an ACL rule that is matched.

On the Broadcom platform, the ACL rule takes precedence over the remark defined in the traffic.conf file.

RN-451 (CM-12344)
Mellanox switch rejects SPAN ACL rule for an output interface that is a subinterface

This is a known issue at this time.

RN-452 (CM-12363)
Mellanox switch rejects ACL rule in ebtables with both -d and -o options

On a Mellanox switch, cl-acltool rejects an ebtables rule that contains both the destination MAC address and the output interface.

This is a known issue.

RN-453 (CM-12564)
Default routes learned via DHCP are moved to the management VRF even if they are not in the management VRF

The mgmt-vrf package has a dhclient exit hook that incorrectly assumes that DHCP is used only with the management interface. If management VRF is enabled, it inserts default routes from the DHCP server into the management table.

Until this issue is resolved, do not use DHCP with the front panel (switch) ports. If you need DHCP for a switch port, disable Management VRF and assign the port to a VRF.

RN-454 (CM-12565)
When VRF is enabled, the ICMP "need to fragment" is not respected

Cumulus Linux defaults to using PMTU to discover if a path has a lower MTU than what is set on its local interfaces. If an ICMP - Fragmentation Needed packet is received on an interface associated with a VRF, the MTU change for the remote address is not properly handled. The end result is that packets exceeding the MTU going through that network segment are dropped.

To work around this issue until it is resolved, do one of the following:

  • Disable PMTU. This does not set the "don't fragment" bit in the IP header, allowing nodes to fragment the packet if needed.
    cumulus@switch:~$ sudo sysctl -w net.ipv4.ip_no_pmtu_disc=1
  • Manually reduce the MTU on the interface. Add mtu <value> to the stanza for that interface in /etc/network/interfaces.

RN-455 (CM-12578)
The cumulus-poe package is not installed on ARM switches after upgrading to version 3.1

After upgrading Cumulus Linux to version 3.1, the cumulus-poe package does not get installed on ARM-based switches. THe following message appears after you reboot the switch:

[ OK ] Stopped Cumulus Linux POE Daemon.
Starting Cumulus Linux POE Daemon...
[FAILED] Failed to start Cumulus Linux POE Daemon.

In order to use Power over Ethernet (PoE) on an ARM switch, you need to install the cumulus-poe package:

cumulus@switch:~$ sudo apt-get update
cumulus@switch:~$ sudo apt-get install cumulus-poe
cumulus@switch:~$ sudo apt-get upgrade

RN-489 (CM-12643)
IGMP snooping doesn't prevent flooding of unregistered multicast data packets

When broadcast video is sent over multicast with a number of senders running, the flooding approaches caused major issues, as the maximum available bandwidth was saturated on an individual port, and started dropping. This issue is being further investigated.

RN-509 (CM-12654)
hsflowd - packet samples missing and default nflog group not set since 3.x

An issue occurrs where only counter samples are generated when hsflowd is configured correctly, but no sFlow sampled packets left the switch.

Manually calling portsamp and specifying an NFLOG group causes the ingress samples to leave the switch. You do this in /proc/bcm/knet/sample_groups:

cumulus@switch:~$ cat /proc/bcm/knet/sample_groups 
Sample NFLOG group (unit 0): 

RN-525 (CM-12715)
On a Quanta IX1 switch, 100G OSI LR4 module (QSFP28-LR4-OSI) doesn't advertise 40G in transceiver codes, so cannot be used at 40G speed

Cumulus Linux can only support speeds on modules that are advertised in each module's transceiver codes. You can determine this by running ethtool -m:

cumulus@switch:~$ sudo ethtool -m

    Transceiver codes                       : 0x80 0x00 0x00 0x00 0x00 0x00 0x00 0x00
    Transceiver type                        : 100G Ethernet: 100G Base-LR4


The example above shows that this module supports only 100G; it cannot support 40G speeds. Similarly, if a module advertises 40G support only, it cannot support 100G speeds.

RN-526 (CM-13037)
Upgrading the clag package fails when logrotate contains an invalid date

While upgrading from Cumulus Linux 3.0.1 to 3.1.z, the clag package does not update if the logrotate file contains an invalid date. This can occur due to bad batteries in the switch or RTC clock chip issues. The error may look like the following:

error: bad year 1929 for file /var/log/boot.log in state file /var/lib/logrotate/status
dpkg: error processing package clag (--configure):
 subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
E: Sub-process /usr/bin/dpkg returned an error code (1)

You can work around this issue by removing the /var/lib/logrotate/status file, and forcing a logrotate. After you do this, the upgrade should be successful.

RN-527 (CM-13588)
Cannot set MTU to 9216 on a Mellanox switch

Setting the MTU to 9216 on a Mellanox switch returns the following error after running ifreload -a to reload the updated configuration:

error: swp1: cmd 'ip -force -batch - [link set dev swp1 mtu 9216
]' failed: returned 1 (RTNETLINK answers: Invalid argument
Command failed -:1

This issue is currently being investigated.

RN-528 (CM-13254)
Links don't come up with 100G AOC cables connected to QLogic 100G NIC (QL45611HLCU-CK) on Tomahawk-based switches

QLogic only supports DAC and SR optics with these NICs; the QLogic QL45611HLCU-CK NIC does not support AOC and LR optics.

This has been noted in the list of unsupported cables and optics.

RN-529 (CM-13243)
Links don't come up between Intel XL710 40G NICs and Tomahawk-based switches while using non-Intel-branded 40G-SR4 optics

If you see this error: "there was an unqualified module detected on the server", please refer to the list of supported fiber modules for the XL710-QDA2 NIC.

Links work fine between XL710 NICs and Tomahawk-based switches with any DAC cables.

This has been noted in the list of unsupported cables and optics.

RN-530 (CM-13255)
Links don't come up between Tomahawk switches and ConnectX-4 NICs while using 100G LR4 optics

Mellanox ConnectX-4 NICs do not support LR4 optics when connected to third party hardware, such as a Broadcom ASIC. 

This has been noted in the list of unsupported cables and optics.

RN-550 (CM-13674)
The ZTP daemon shuts itself down after 5 minutes of inactivity

The zero touch provisioning (ZTP) daemon ztpd shuts itself down after 5 minutes of inactivity but the service remains enabled for the next reboot.

This can affect deployments where a switch might be powered up in a remote data center for weeks without ever being configured. In such a case, there is no way to automatically initiate the ZTP process.

This is a known issue that will be fixed in a future release of Cumulus Linux.

RN-576 (CM-14908)
TACACS sends authentication requests out of the default VRF, not the management VRF

If a management VRF if configured, TACACS won't send authentication requests out of the management VRF. Instead, it sends these requests out of the default VRF.

To work around this issue, run the following commands, which restrict inbound SSH to only the management VRF interface and disable inbound SSH via the switch ports. Note that using SSH via the front panel ports is not a workaround.

cumulus@switch:~$ sudo systemctl disable ssh.service
cumulus@switch:~$ sudo systemctl stop ssh.service
cumulus@switch:~$ sudo systemctl enable ssh@mgmt.service
cumulus@switch:~$ sudo systemctl start ssh@mgmt.service


This support portal has moved

Cumulus Networks is now part of the NVIDIA Networking Business Unit! The NVIDIA Cumulus Global Support Services (GSS) team has merged its operations with the NVIDIA Mellanox support services team.

You can access NVIDIA Cumulus support content from the Mellanox support portal.

You open and update new cases on the Mellanox support portal. Any previous cases that have been closed have been migrated to the Mellanox support portal.

Cases that are still open on the Cumulus portal will continue to be managed on the Cumulus portal. Once these cases close, they will be moved to the Mellanox support portal.

Powered by Zendesk