Cumulus Linux 4.1 Release Notes

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

4.1.1 Release Notes

Open issues in 4.1.1

Issue IDDescriptionAffectsFixed
CM-29760 Several vulnerabilities were discovered in BIND, a DNS server implementation.
bind9-host (containing only /usr/bin/host) and some libraries from the bind9 source package are installed on the switch by default; the BIND server referred to in these vulnerabilities is not installed by default but is available in the repository for optional installation.
CVE-2019-6477: It was discovered that TCP-pipelined queries can bypass tcp-client limits resulting in denial of service.
CVE-2020-8616: It was discovered that BIND does not sufficiently limit the number of fetches performed when processing referrals. An attacker can take advantage of this flaw to cause a denial of service (performance degradation) or use the recursing server in a reflection attack with a high amplification factor.
CVE-2020-8617: It was discovered that a logic error in the code which checks TSIG validity can be used to trigger an assertion failure, resulting in denial of service.
Vulnerable: 9.11.5.P4+dfsg-5.1
Fixed: 9.11.5.P4+dfsg-5.1+deb10u1
4.0.0-4.1.1
CM-29759 When you use nginx and restserver in management VRF to provide a REST API for the switch, nginx starts but restserver fails to start.
To work around this issue, comment out the Requires= line in the /lib/systemd/system/restserver.service. For example:
#Requires=nginx.service restserver.socket

3.7.12, 4.0.0-4.1.1
CM-29667 After installing Cumulus Linux on the Mellanox SN2100 switch, if you break out a port (for example, if you break out swp1 into four ports: swp1s0, swp1s1, swp1s2, swp1s3) in the /etc/cumulus/ports.conf file, then run the systemctl start switchd command, the update does not take effect.
To work around this issue, run the systemctl restart switchd command.
3.7.12, 4.0.0-4.1.1
CM-29603 When you move an interface from one VRF to another and modify the description in the same configuration operation, FRR crashes and restarts during a service reload. If these two changes occur in separate reloads, FRR does not crash.4.1.1
CM-29594 When you run an Ansible script to replace the /etc/network/interfaces file, then run the ifreload -a command, you see errors similar to the following:
error: swp1s1.2: netlink: cannot set link swp1s1.2 up: operation failed with ‘Network is down’ (100)
warning: cmd ‘/bin/ip addr del 10.0.0.1/24 dev eth0’ failed: returned 2 (RTNETLINK answers: Cannot assign requested address

To work around this issue, run the ifreload -a command a second time.
3.7.12, 4.0.0-4.1.1
CM-29591 When you add an IPv4 route with an IPv6 next hop, switchd crashes.4.1.0-4.1.1
CM-29576 The Conntrack table fills up with OFFLOAD entries for flows that do not match the NAT rules in iptables.4.1.0-4.1.1
CM-29568 When NAT is configured, non-NAT traffic is incorrectly forwarded to the CPU.4.1.0-4.1.1
CM-29562 If you have an SVI with multiple VRR IP addresses and try to delete one of the VRR configurations, net commit or ifreload -a returns an error.3.7.12, 4.1.1
CM-29556 CVE-2020-11868: ntpd in ntp before 4.2.8p14 and 4.3.x before 4.3.100 allows an off-path attacker to block unauthenticated synchronization via a server mode packet with a spoofed source IP address, because transmissions are rescheduled even when a packet lacks a valid origin timestamp.
This affects: ntp-4.2.8p12 (possibly earlier) and ntp-4.2.8p13
The fix for https://bugs.ntp.org/3445 introduced a bug whereby a system that is running ntp-4.2.8p12 or p13 that only has one unauthenticated time source can be attacked in a way that causes the victim’s next poll to its source to be delayed, for as long as the attack is maintained.
http://support.ntp.org/bin/view/Main/NtpBug3592 gives the following mitigations if it is not possible to upgrade to a version with the fix:
  • Use authentication with symmetric peers.
  • Have enough sources of time. The default NTP configuration in Cumulus Linux has four time sources.
3.0.0-3.7.12, 4.0.0-4.1.1
CM-29546 In vtysh, if you configure, then remove a layer 3 VNI for a VRF, the VNI is removed from zebra even if the VNI interface still exists in the kernel.
If you configure a layer 2 VNI as a layer 3 VNI by mistake, removing the layer 3 VNI binding removes it from zebra but EVPN-learned MACs and neighbors are not installed into the kernel.
To work around this issue, delete, then re-add the missing VNI. For example:
cumulus@switch:~$ sudo ifdown vni10100
cumulus@switch:~$ sudo ifup vni10100

If you flap the link with the ip link set vni10100 down; ip link set vni10100 up commands, zebra does not re-add the VNI.
3.7.12, 4.0.0-4.1.1
CM-29525 The asic-monitor.service fails when you configure /etc/cumulus/datapath/monitor.conf with monitor.histogram_pg.collect.port_group_list = <span class="error">&#91;all_packet_pg&#93;</span> and there is traffic passing through the buffer. When the service fails, you see the following traceback in journalctl:
asic-monitor[7389]: asic-monitor-module INFO: 2020-05-01 18:28:12.548734: Egress queue(s) greater than 500 bytes in monitor port group histogram_pg
asic-monitor[7389]: asic-monitor ERROR: ASIC monitor exception: sx_api_port_counter_tc_get failed: Parameter Error
asic-monitor[7389]: File “/usr/bin/asic-monitor”, line 139, in
asic-monitor[7389]: main(sys.argv[1:])
asic-monitor[7389]: File “/usr/bin/asic-monitor”, line 126, in main
asic-monitor[7389]: traceback.print_stack()
asic-monitor[7389]: Traceback (most recent call last):
asic-monitor[7389]: File “/usr/bin/asic-monitor”, line 117, in main
asic-monitor[7389]: monitor.run()
asic-monitor[7389]: File “/usr/lib/python2.7/dist-packages/cumulus/asic_monitor.py”, line 158, in run


3.7.11-3.7.12, 4.1.1
CM-29519 The JSON format output of the net show bgp l2vpn evpn summary command shows the incorrect neighbour state.3.7.12, 4.0.0-4.1.1
CM-29513 Configuration of interfaces fails to apply when you set FEC. You see a message similar to the following:
cmd ‘/sbin/ethtool –set-fec  encoding rs’ failed: returned 255      (Cannot set FEC settings: Connection timed out

To work around this issue, reapply the configuration with NCLU and run the net commit or ifreload -a a second time to allow the interface configuration to apply.
4.1.1
CM-29492 When you create SPAN or ERSPAN rules in ebtables, the action fails to install if it is not in lowercase. Make sure that the SPAN or ERSPAN action is all lowercase; for example:
[ebtables]
-A FORWARD –in-interface swp10 -j span –dport swp1

3.7.12, 4.1.1
CM-29485 The following vulnerability affects the openldap package:
CVE-2020-12243: A vulnerability was discovered in OpenLDAP, a free implementation of the Lightweight Directory Access Protocol. LDAP search filters with nested boolean expressions can result in denial of service (slapd daemon crash).
Vulnerable: <= 2.4.47+dfsg-3+deb10u1
Fixed: 2.4.47+dfsg-3+deb10u2
4.0.0-4.1.1
CM-29468 On the Dell S4148T optical module, the low power polarity bit is set incorrectly and the switch port does not come up.
To work around this issue, edit the /etc/hw_init.d/S10qsfp_init.sh file and change the lpmode line to be 0x3f instead of 0x00:
# disable lpmode, reset all QSFP+/QSFP28 ports
echo 0x3f > ${master_cpld}/qsfp_30_25_lpmode
echo 0x3f > ${master_cpld}/qsfp_30_25_modsel
echo 0x3f > ${master_cpld}/qsfp_30_25_reset

Reboot the switch and check that the switch port comes up.
Important: Before upgrading Cumulus Linux 4.x with Debian packages that includes a fix for this problem, you must change the lpmode line back to 0x00.
4.1.0-4.1.1
CM-29460 The following security vulnerabilities affect qemu packages, which are available for optional installation on Cumulus Linux:
CVE-2019-12068: In QEMU 1:4.1-1, 1:2.1+dfsg-12+deb8u6, 1:2.8+dfsg-6+deb9u8, 1:3.1+dfsg-8~deb10u1, 1:3.1+dfsg-8+deb10u2, and 1:2.1+dfsg-12+deb8u12 (fixed), when executing script in lsi_execute_script(), the LSI scsi adapter emulator advances ‘s->dsp’ index to read next opcode. This can lead to an infinite loop if the next opcode is empty. Move the existing loop exit after 10k iterations so that it covers no-op opcodes as well.
CVE-2019-15034: hw/display/bochs-display.c in QEMU 4.0.0 does not ensure a sufficient PCI config space allocation, leading to a buffer overflow involving the PCIe extended config space.
CVE-2019-20382: QEMU 4.1.0 has a memory leak in zrle_compress_data in ui/vnc-enc-zrle.c during a VNC disconnect operation because libz is misused, resulting in a situation where memory allocated in deflateInit2 is not freed in deflateEnd.
CVE-2020-1983: A use after free vulnerability in ip_reass() in ip_input.c of libslirp 4.2.0 and prior releases allows crafted packets to cause a denial of service.
Vulnerable: <= 3.1+dfsg-8+deb10u4
Fixed: 3.1+dfsg-8+deb10u5
4.0.0-4.1.1
CM-29420 When you configure the management interface class (as shown below), eth0 remains in an admin down state on subsequent reboots:
allow-mgmt eth0
iface eth0 inet dhcp
vrf mgmt
allow-mgmt mgmt
iface mgmt
address 127.0.0.1/8
address ::1/128
vrf-table auto

4.1.0-4.1.1
CM-29385 The following vulnerability affects the openssl package:
CVE-2020-1967: Bernd Edlinger discovered that malformed data passed to the SSL_check_chain() function during or after a TLS 1.3 handshake could cause a NULL dereference, resulting in denial of service.
Vulnerable: <= 1.1.1d-0+deb10u2
Fixed: 1.1.1d-0+deb10u3
4.0.0-4.1.1
CM-29367 On switches with the Trident3 ASIC, PFC is not working as expected. If you set the PFC for only one CoS, pause frames are sent for all CoS traffic.3.7.11-3.7.12, 4.0.0-4.1.1
CM-29319 When you configure an RD or RT with NCLU, you see duplicate VNI stanzas in the /etc/frr/frr.conf file.
To work around this issue, manually edit the etc/frr/frr.conf file to define advertise-all-vni before the RD or RT configuration within the l2vpn EVPN address family, then reload the FRR service with the sudo systemctl reload frr command.
4.1.0-4.1.1
CM-29312 FRR incorrectly orders advertise-all-vni to be later in the configuration than manual rd or route-target definitions. This causes the rd or route-target configuration to be misapplied or not applied at all.
To work around this issue, when you manually configure the rd or route-target for a VNI, you must manually edit the /etc/frr/frr.conf file to define advertise-all-vni before the rd or route-target configuration within the l2vpn evpn address family.
4.0.0-4.1.1
CM-29309 When Optimized Multicast Flooding (OMF) is enabled with the bridge.optimized_mcast_flood = TRUE setting in the /etc/cumulus/swichd.conf file, the switch continues to flood IPv6 multicast traffic to all slave ports when there is no MLD join receive.3.7.11-3.7.12, 4.0.0-4.1.1
CM-29296 The following vulnerabilities have been announced in git, which is available in the repository for optional installation:
CVE-2020-5260: Felix Wilhelm of Google Project Zero discovered a flaw in git, a fast, scalable, distributed revision control system. With a crafted URL that contains a newline, the credential helper machinery can be fooled to return credential information for a wrong host.
CVE-2020-11008: Carlo Arenas discovered a flaw in git, a fast, scalable, distributed revision control system. With a crafted URL that contains a newline or empty host, or lacks a scheme, the credential helper machinery can be fooled into providing credential information that is not appropriate for the protocol in use and host being contacted.
Vulnerable: <= 2.20.1-2+deb10u1 (CVE-2020-5260) <= 2.20.1-2+deb10u2 (CVE-2020-11008)
Fixed: 2.20.1-2+deb10u3
4.0.0-4.1.1
CM-29284 The following vulnerabilities affect git, which is available in the repository for optional installation:
CVE-2020-5260: Felix Wilhelm of Google Project Zero discovered a flaw in git, a fast, scalable, distributed revision control system. With a crafted URL that contains a newline, the credential helper machinery can be fooled to return credential information for a wrong host.
CVE-2020-11008: Carlo Arenas discovered a flaw in git, a fast, scalable, distributed revision control system. With a crafted URL that contains a newline or empty host, or lacks a scheme, the credential helper machinery can be fooled into providing credential information that is not appropriate for the protocol in use and host being contacted.
3.0.0-3.7.12, 4.0.0-4.1.1
CM-29270 On Mellanox switches with the Spectrum-2 ASIC, when you use more than 16 bonds on the switch, you might experience forwarding issues or see an error similar to the following in switchd.log:
2020-04-07T15:59:27.345421+10:00 le-266-q14-2-res switchd[8422]: hal_mlx_bond.c:1696 ERR member_fwd_update_cb spartan-bm87 collector set failed for swp3s0: Driver’s Return Status is Non-Zero
2020-04-07T15:59:27.345557+10:00 le-266-q14-2-res switchd[8422]:
2020-04-07T15:59:27.348432+10:00 le-266-q14-2-res switchd[8422]: hal_mlx_bond.c:1705 ERR member_fwd_update_cb spartan-bm87 distributor set failed for swp3s0: Driver’s Return Status is Non-Zero

To work around this issue, configure fewer than 16 bonds on a switch.
4.1.0-4.1.1
CM-29259 You might see the following gport error messages in switchd.log:

2020-04-10T19:50:01.011224+09:00 E1PDX0V1ELF0001 6 switchd[925]: hal_bcm_mdb.c:530 gport 0x800007a find failed
2020-04-10T19:50:01.011631+09:00 E1PDX0V1ELF0001 6 switchd[925]: hal_bcm_mdb.c:530 gport 0x8000009 find failed

These messages are harmless and can be ignored.
3.7.12, 4.0.0-4.1.1
CM-29183 On the Mellanox SN2010 and SN2100 switch, the fan speed might ramp up and down.4.1.0-4.1.1
CM-29178 On Mellanox switches, the thermal monitoring script starts in suspended mode and, as a result, the fans run at sixty percent. You also see the following log message:
hw-management.sh[847]: Thermal algorithm is manually suspend.

To work around this issue, run the following command to enable thermal monitoring:
cumulus@switch:~$ sudo echo 0 > /var/run/hw-management/config/suspend

4.0.0-4.1.1
CM-29165 With FRR or OSPF, you might see an inconsistent link-state advertisement. For example, when you configure the OSPF default originate route as metric-type 1 with a specific metric, Cumulus Linux shows the default originate route as an external metric-type 2 route with the default metric in the database. This issue typically occurs when both IPv4 and IPv6 default routes exist in the routing table.3.7.12, 4.0.0-4.1.1
CM-29145 If you try to remove BFD configuration with a reload, the FRR service fails. The reload action results in a TypeError: expected string or bytes-like object error.
You see this issue only if there is default configuration, such as configuration in the /etc/frr/frr.conf file that is suppressed from view in the FRR running configuration.
To work around this issue, remove the default configuration lines; for example:
username cumulus nopassword

4.1.0-4.1.1
CM-29131 NTP does not start when you use the default VRF instead of the management VRF.4.1.0-4.1.1
CM-29068 On the Broadcom switch with the Trident3 ASIC, packet priority remark values assigned from each internal CoS value continue to work with default values; if you change the internal CoS value, the change does not take effect.3.7.11-3.7.12, 4.0.0-4.1.1
CM-29044 A large number of flapping peers causes FRR to require a corresponding update to internal data structures that track peer information. Updating this internal data structure does not delete links that are down due to the flapping. The size of this array then grows to contain both current peers as well as peers that should have been deleted during the flap processing. The contents of this array is processed by FRR to poll the links, which consumes CPU for all items in the array. This additional polling consumes more CPU than necessary but has no functional impact.
To work around this issue, restart FRR.
3.7.11-3.7.12, 4.0.0-4.1.1
CM-29043 When a multipath route that contains an EVPN path exists together with an IPv4 BGP path in the VRF, the RMAC to VTEP binding is incorrect. This invalid entry occurs because Cumulus Linux treats IPv4 routes received over the eBGP IPv4 peering incorrectly in the VRF.
To work around this issue, remove the unnecessary eBGP IPv4 peering.
3.7.12, 4.0.0-4.1.1
CM-28995 After you flap an MLAG peerlink, a rare condition might occur where routes and neighbors for VXLAN-enabled VLANs are misprogrammed as non-VXLAN routes and neighbors due to VNI state transitions. This results in a forwarding failure for traffic destined to these misprogrammed routes and neighbors.
Note: Do not flap a VNI interface manually. The only expected time for a VNI interface to go down is when the MLAG secondary switch brings the VNIs protodown during a peer link failure where the backup IP address is still active.
To recover from this condition, restart switchd with the sudo systemctl restart switchd command.
3.7.10-3.7.12, 4.1.0-4.1.1
CM-28982 On the EdgeCore Minipack-AS8000, when you try to configure ROCEv2, you see errors indicating that PFC is not working properly.4.0.0-4.1.1
CM-28948 Cumulus Linux supports a maximum of 300 ACLs for use with 802.1X interfaces. This limit encompasses the default ACLs, pre-auth ACLs and dynamic ACLs. Exceeding this limit can affect the performance of the switch.4.1.0-4.1.1
CM-28944 A change in a route map prefix list that should remove a route might not be reflected in the ospf6 database or in peers, and the route might not be deleted.
To work around this issue, reenter the redistribute <connected\|static> route-map <route-map-name> statement in the configuration.
3.6.2-3.7.12, 4.0.0-4.1.1
CM-28940 If you configure aggregate-address <address> summary-only before a component of the same aggregate is injected into the BGP table with the network or redistribute command, when you remove the aggregate-address configuration, the component stays suppressed; it is not advertised to peers. For example:
Existing configuration:
router bgp 1
address-family ipv4 unicast
aggregate-address 50.0.0.0/8 summary-only
exit-address-family

If you add network 50.0.0.1/32, you see the following (expected) BGP table entries:
Status codes: s suppressed, d damped, h history, * valid, > best, = multipath,
i internal, r RIB-failure, S Stale, R Removed
Origin codes: i - IGP, e - EGP, ? - incomplete
Network Next Hop Metric LocPrf Weight Path
*> 50.0.0.0 0.0.0.0 32768 i
s> 50.0.0.1/32 0.0.0.0 0 32768 i

Removing aggregate-address 50.0.0.0/8 summary-only at this point results in the following (unexpected) BGP table entry:
Status codes: s suppressed, d damped, h history, * valid, > best, = multipath,
i internal, r RIB-failure, S Stale, R Removed
Origin codes: i - IGP, e - EGP, ? - incomplete
Network Next Hop Metric LocPrf Weight Path
s> 50.0.0.1/32 0.0.0.0 0 32768 i

To work around this issue, remove, then re-add the component prefix routes.
3.7.12, 4.0.0-4.1.1
CM-28938 When you install an ACL LOG/DROP rule on a layer 3 ingress interface that is a member of a VRF, traffic that matches this rule is not logged and is still forwarded.
To work around this issue, apply the ACL LOG/DROP rule to the VRF device itself or to the layer 2 VNI.
3.7.6-3.7.12, 4.0.0-4.1.1
CM-28925 The global MTU setting in the mtu.json file does not take effect on SVI interfaces after ifreload -a.
To work around this issue, run sudo systemctl restart networking or restart the switch.
Note: A network restart is a disruptive operation.
4.1.0-4.1.1
CM-28900 You might see a core file in FRRouting related to OSPFv3 if the switch is configured as both an OSPFv3 ABR and ASBR, and other switches in the same area are also configured as both ABR and ASBR. This issue is not seen with a single ABR or ASBR in an area or if there are multiple ASBRs in an area not acting as ABRs. To work around this issue, do not perform redistribution on more than one ABR in the same area.4.0.0-4.1.1
CM-28867 The QuantaMesh BMS T3048-LY8 switch shows a low fan RPM in syslog.3.7.5-3.7.12, 4.0.0-4.1.1
CM-28821 When configuring VRF route leaking, if you define import vrf route-map <name> but do not have any imported VRFs, the route map command displays incorrectly, and as a result, FRR fails to reload.4.0.0-4.1.1
CM-28816 The following security advisory has been announced for bash:
CVE-2019-18276 Qualys scan QID 372268 setuid vulnerability
When bash or bash scripts are run setuid, bash is supposed to drop privileges, but does so incorrectly, so that an attacker with command access to the shell can use enable -f for runtime loading of a new builtin that calls setuid() to regain dropped privileges.
To work around this issue, do not make bash or bash scripts setuid.
3.0.0-3.7.12, 4.0.0-4.1.1
CM-28770 The net add routing route-map <name> permit <seq> set community <comm> command does not add the set statement into the /etc/frr/frr.conf file.4.0.0-4.1.1
CM-28754 On switches with the Trident2+ ASIC, adding SPAN rules disables PBR rules.3.7.3-3.7.12, 4.0.0-4.1.1
CM-28682 On the Mellanox Spectrum switch in an EVPN symmetric configuration with MLAG, simultaneously shutting down the layer 3 interfaces that serve as uplinks to the VXLAN fabric might result in traffic loss of up to 15 seconds.4.1.0-4.1.1
CM-28656 In OVSDB VLAN-aware mode, removing a VTEP binding on the NSX controller fails to clean up all interfaces associated with the logical switch.3.7.12, 4.0.0-4.1.1
CM-28613 In EVPN Active-Active (MLAG) environments, rebooting one member of an MLAG pair should result in the local MAC mobility sequence number reverting to 0. Sometimes a reboot of one MLAG peer results in the local MAC mobility sequence number being set to a non-zero value despite that no more mobility events occur. This issue is cosmetic only, as BGP does not advertise the incorrect sequence number and forwarding entries correctly point to the remote VTEP where the MAC is now located.3.7.12, 4.0.0-4.1.1
CM-28611 In an EVPN Active-Active (MLAG) environment, sometimes a local-to-remote MAC mobility event results in the local sequence number appearing higher than the remote sequence number in zebra. This issue is cosmetic only, as BGP does not advertise the incorrect sequence number and forwarding entries correctly point to the remote VTEP where the MAC is now located.3.7.12, 4.0.0-4.1.1
CM-28497 QinQ across VXLAN on a traditional bridge does not work.4.1.0-4.1.1
CM-28489 The following CVEs were announced for rsyslog:
CVE-2019-17041 CVE-2019-17042rsyslogd, when receiving remote log messages (not enabled by default on Cumulus Linux) with the pmaisforwardedfrom or pmcisconames optional log parsers (also not enabled by default on Cumulus Linux), is vulnerable to CVE-2019-17041 and CVE-2019-17042 where malicious messages that appear to be from AIX or Cisco respectively may be caused to skip sanity checks, resulting in incorrect negative lengths causing heap overflows.
Vulnerable: 8.1901.0-1Recommendation:Do not enable receiving syslog messages from other hosts by the network (with $UDPServerRun or $InputTCPServerRun). Also, do not enable (with $ModLoad) the vulnerable parsers pmaixforwardedfrom or pmcisconames. The default /etc/rsyslog.conf file on Cumulus Linux does not enable any of these.
4.0.0-4.1.1
CM-28465 When you try to configure link-down on a parent interface of a subinterface configured in a VRF, you encounter an error.3.7.11-3.7.12, 4.0.0-4.1.1
CM-28458 NCLU incorrectly allows you to configure port security on bond/MLAG interfaces.
Port security is not supported on bond/MLAG interfaces.
4.0.0-4.1.1
CM-28442 PTM mis-detects incorrect hostnames of LLDP neighbors and does not fail them as expected. Instead they end up in an N/A cabling status.3.7.11-3.7.12, 4.0.0-4.1.1
CM-28441 If a LLDP neighbor advertises a PortDescr that contains commas, ptmctl -d splits the string on the commas and misplaces its components in other columns.3.7.11-3.7.12, 4.0.0-4.1.1
CM-28393 On the Dell S5232F-ON switch, EVPN and dynamic VRF route leaking results in the CPU forwarding traffic to newly-learned type-2 routes.
To work around this issue, restart FRR.
3.7.9-3.7.12, 4.0.0-4.1.1
CM-28376 On the Dell S5232F-ON switch, the output of ledmgrd shows amber_blinking but smonctl shows all OK.3.7.11-3.7.12, 4.0.0-4.1.1
CM-28340 Mellanox switches with the Spectrum A0 ASIC that are integrated with VMware NSX experience BFD connectivity issues with service nodes. As a result, VXLAN tunnels do not work.
Mellanox switches with the Spectrum A1 ASIC do not have this issue.
3.7.11-3.7.12, 4.0.0-4.1.1
CM-28249 On the Mellanox switch, when you modify the buffer and queue configuration without restarting switchd, you might see a one second interruption in forwarding.4.0.0-4.1.1
CM-28226 When you restart the hsflowd service, you see a systemd warning message similar to the following:
Warning: The unit file, source configuration file or drop-ins of hsflowd@mgmt.service changed on disk. Run ‘systemctl daemon-reload’.

4.0.0-4.1.1
CM-28189 When host-resources and ucd-snmp-mib are polled, you see permission denied messages similar to the following:
Jan 30 19:22:53 switch123 snmpd[23172]: Cannot statfs /sys/kernel/debug/tracing: Permission denied

4.0.0-4.1.1
CM-28136 The MLAG switch pair has VLANs defined that are not used on MLAG bonds. These VLANs still synchronize MAC addresses across to the peer switch. This results in log messages that indicate a MAC address is installed and the VLAN is not defined; for example:
RTM_NEWNEIGH with unconfigured vlan XXXX on port peerlink

3.7.10-3.7.12, 4.0.0-4.1.1
CM-28080 TACACS+ through ClearPass is not currently supported. Cumulus Linux sends authorization before authentication, but ClearPass does not accept an authorization before the user is authenticated.3.7.11-3.7.12, 4.0.0-4.1.1
CM-28078 On the Broadcom switch with the Trident3 ASC, packet priority remark values assigned from each internal CoS value continue to work with default values; if you change the internal CoS value, the change does not take effect.3.7.11-3.7.12, 4.0.0-4.1.1
CM-28061 On switches with the Trident3 ASIC, PFC is not working as expected. If you set the PFC for only one CoS, pause frames are sent for all CoS traffic.3.7.11-3.7.12, 4.0.0-4.1.1
CM-28003 The FRR service does not provide a way for automation to know if the configuration applied properly.
To work around this issue, execute the vtysh -f <file> command in the automation file before starting the FRR service to validate the functional configuration and return an error code.
3.7.11-3.7.12, 4.0.0-4.1.1
CM-27999 On the EdgeCore AS7326-56X switch, the PSU fans show constant LOW warnings.3.7.10-3.7.12, 4.0.0-4.1.1
CM-27982 On Broadcom switches, switchd crashes when dynamic VRF route leaking is enabled and the following is true:
  • The default route is leaked from VRF1 to VRF2
  • Hardware-based dynamic VRF route leaking is configured (vrf_route_leak_enable_dynamic is set to TRUE in the /etc/cumulus/switchd.conf file).
    You might see logs similar to the following in /var/log/syslog:
    kernel: [159400.526241] switchd[21374]: segfault at 1229cdd84 ip 00000000004142ca sp 00007ffd557a86d0 error 4 in switchd[400000+71000]

    To work around this issue, use a route map to filter the default route (the source VRF is imported into the destination VRF).
3.7.10-3.7.12, 4.0.0-4.1.1
CM-27957 If you have configured a higher number of ports and VLANs (ports x VLANs) or the switch is a lower-powered (CPU) platform, the switchd service might fail to send a systemd keepalive within the watchdog timeout value (2 minutes by default) and you see an error similar to the following:
bq. systemd[1]: switchd.service watchdog timeout (limit 2min)!

To workaround this issue, either reduce the number of configured interfaces and, or VLANs, or increase the systemd timeout for switchd.service.
To increase the systemd timeout:
  1. Edit the /etc/systemd/system/switchd.service.d/override.conf file and increase the WatchdogSec parameter.
  2. Restart the switchd service with the sudo systemctl restart switchd.service command.
    systemd will attempt to restart the switchd service automatically (after the watchdog timeout). If the restart fails multiple times in a short time period, run the sudo systemctl reset-failed command followed by the sudo systemctl restart switchd command.
3.7.11-3.7.12, 4.0.0-4.1.1
CM-27950 On the Dell S5232F, S5248F, S5296F, and S3048 switch, using the poweroff or halt commands does not fully power off the switch.4.0.0-4.1.1
CM-27753 The EdgeCore Minipack-AS8000 switch supports FEC RS by default; you cannot disable this setting. However, the ethtool --show-fec command output indicates that FEC is disabled. Also, if you try to change the FEC setting, Cumulus Linux reports an error. For example:
cumulus@switch:~$  net add interface swp23 link speed 100000
cumulus@switch:~$ net add interface swp23 link autoneg off
cumulus@switch:~$ net add interface swp23 link fec rs
”/sbin/ifreload -a” failed:
error: swp23: cmd ‘/sbin/ethtool –set-fec swp23 encoding rs’ failed: returned 255 (Cannot set FEC settings: Operation not supported)
Command ‘['/sbin/ifreload’, ‘-a’]’ returned non-zero exit status 1

4.0.0-4.1.1
CM-27678 The net show bridge macs command returns an empty interface column.
To work around this issue, run the bridge fdb show command to show the interface.
4.0.0-4.1.1
CM-27642 The following CVEs were announced that affect the libssh package:
CVE-2019-14889 has been announced in the libssh library, where unsanitized user-provided scp command lines could allow an attacker to execute arbitrary commands on the server.
The libssh library is not installed on Cumulus Linux by default, but is available in the Cumulus Linux 4 repository for optional installation. Note that libssh is distinct from libssh2 and openssh, which are present on the switches and in the repositories.
See the following for more information:
https://www.libssh.org/security/advisories/CVE-2019-14889.txt
https://security-tracker.debian.org/tracker/CVE-2019-14889
4.0.0-4.1.1
CM-27637 On the EdgeCore Minipack-AS8000 switch, a 100G DAC link does not come up when auto-negotiation is enabled on the neighbor. This switch does not support 100G DAC auto-negotiation at this time.4.0.0-4.1.1
CM-27581 On the Delta AG-6248C PoE switch, when you run the apt upgrade command, the upgrade does not work. Cumulus Linux uses uboot directly instead of grub to boot the kernel. Uboot needs a special header to boot the kernel, which is not present. Without this header, when you use the apt upgrade command to upgrade Linux packages, uboot is unable to boot up the kernel.
To work around this issue, upgrade Cumulus Linux by installing the Cumulus Linux image. Run the onie-select command to go into ONIE, and then use the nos-install command in ONIE to install a new image.
This workaround only works when an out-of-band network is present.
3.7.11-3.7.12, 4.0.0-4.1.1
CM-27444 If you use the NCLU commands to configure NTP and run the net add time ntp source <interface> command before you run the net add time ntp server <server> iburst command, the /etc/ntp.conf file is misconfigured.
To work around this issue, run the net add time ntp server <server> iburst command before you run the net add time ntp source <interface> command.
3.7.10-3.7.11, 4.0.0-4.1.13.7.12
CM-27254 On the Mellanox switch with the Spectrum and Spectrum-2 ASIC, IPv6 egress ACLs are not supported on subinterfaces.4.0.0-4.1.1
CM-27243 The length of the netlink message is not set properly for non-bridge family type messages. The same length is used for both bridge and non-bridge even though the bridge family type message has an extra attribute. This causes extra bytes to be left over in non-bridge family type netlink messages.3.7.10, 4.0.0-4.1.13.7.11-3.7.12
CM-27143 On the Dell S5248F-ON switch, the CPU core temperature sensors show ABSENT.4.0.0-4.1.1
CM-27136 With a high number of active routes (20K or more), when you perform a networking restart, the FRR log files might become flooded with error messages associated with the restart. These logs are normal and are not directly a problem. However, the large number of messages can cause the logs to rotate away any previous history, which prevents you from tracing back events leading up to the restart. In a troubleshooting environment, this can be problematic.4.0.0-4.1.1
CM-27099 On the Mellanox switch with the Spectrum-2 ASIC, Precision Time Protocol (PTP) is not currently supported.4.0.0-4.1.1
CM-27094 On the Delta AG9032v1 switch, smonctl and sensors report inaccurate PSU current and power.3.5.0-3.7.12, 4.0.0-4.1.1
CM-27049 On the Mellanox switch with the Spectrum 2 ASIC, interfaces using 100G or 200G Direct Attach Cables (DACs) do not come up with the interface default configuration.
To work around this issue and bring the interfaces up, perform the following configuration on both sides of the link:
  • Set the interface speed to the desired speed
  • Set link auto-negotiation to off
  • Set link FEC to RS mode
4.0.0-4.1.1
CM-27018 If you configure more than one VRR interface on an SVI interface, deleting one of the VRR addresses does not remove the interface/address.3.7.10-3.7.12, 4.0.0-4.1.1
CM-26942 Port security is not currently supported on VX. The NCLU commands produce errors.4.0.0-4.1.1
CM-26921 If you delete an undefined bond, then add a bond slave, the net commit command fails.3.7.9-3.7.12, 4.0.0-4.1.1
CM-26913 FRR configuration commands for an SVI interface might have the \n misplaced in the output. For example:
sudo sh -c “printf ‘interface 50\nvrf TEST description L3 routing interface\n’ » /etc/frr/frr.conf"

should be:
sudo sh -c “printf ‘interface 50 vrf TEST\ndescription L3 routing interface\n’ » /etc/frr/frr.conf"

To work around this issue, configure the interface manually in the /etc/frr/frr.conf file.
3.7.9-3.7.12, 4.0.0-4.1.1
CM-26907 NCLU incorrectly allows you to apply port security configuration on layer 2 and layer 3 ports that are not part of a bridge.4.0.0-4.1.1
CM-26905 When you update the hostname of a switch with the NCLU net add hostname <hostname> command, then run net commit, the lldpd service does not restart and other devices still see the old hostname.
To work around this issue, run the sudo systemctl restart lldpd.service command.
3.7.10-3.7.12, 4.0.0-4.1.1
CM-26875 After you delete an IPv6 numbered BGP peer group neighbor, Cumulus Linux might continue to send route advertisements.
To work around this issue, restart FRR after removing the IPv6 numbered configuration.
3.7.9-3.7.12, 4.0.0-4.1.1
CM-26860 When you run the NCLU net show commit last or net show commit <number> command, where <number> is the last commit, no output is shown.4.0.0-4.1.1
CM-26841 In the ethool -m output, the Revision Compliance field might show Unallocated when the SFF-8363 Revision Compliance value is SFF-8636 version 2.8 or later.4.0.0-4.1.1
CM-26769 Setting ProtoDown on ports populated with SFP modules providing RJ-45 1000BASE-T interfaces does not cause the carrier to be dropped. The kernel shows carrier down; however, the remote device still shows a link.3.7.6-3.7.10, 4.0.0-4.1.13.7.11-3.7.12
CM-26702 On the Mellanox switch with the Spectrum-2 ASIC, policy-based routing (PBR) is not currently supported.4.0.0-4.1.1
CM-26655 If you reconfigure an NTP server with NCLU using different trailing options after the IP address (such as iburst), an invalid configuration is added to the /etc/ntp.conf file. For example:
net add time ntp server 1.2.3.4 iburst
net commit
net add time ntp server 1.2.3.4
net commit

If you need to alter existing server configurations, first remove the server, commit, then re-add the server with any trailing options.
3.7.9-3.7.12, 4.0.0-4.1.1
CM-26599 Auto-negotiation does not work with the QSFP28 cables and a remote system operating at 10G. Attempting to enable auto-negotiation with ethtool -s swp<#> autoneg on returns Operation not supported.
To work around this issue, do not use auto-negotiation and set the local port speed to 10G.
3.7.9-3.7.12, 4.0.0-4.1.1
CM-26595 The NCLU net show lldp command displays the speed of a ganged port group as the speed of one of the individual links, rather than the sum of their speeds.3.7.9-3.7.12, 4.0.0-4.1.1
CM-26516 Applying a policy-based routing (PBR) rule for all traffic from a host might disrupt ARP refresh for that connected host.3.7.5-3.7.12, 4.0.0-4.1.1
CM-26423 NCLU requires you to specify an interface with multiple address-virtual statements in ascending MAC address order.3.7.5-3.7.12, 4.0.0-4.1.1
CM-26412 Mac learning is not disabled by default on a double tagged peer link interface resulting in the MAC address changing between the MLAG bond and the peer link.
To work around this issue, disable MAC learning on QinQ VLANs by adding bridge-learning off to the VLAN stanza in the etc/network/interfaces file.
3.7.9-3.7.12, 4.0.0-4.1.1
CM-26308 An interface alias configured outside FRR using iproute2 is imported into the FRR running configuration and overrides the internal description. After an FRR reload, this causes FRR to delete the interface alias in an inefficient way. Depending on how many interfaces with aliases you have configured, this can cause a FRR reload to time out.
To work around this issue, remove the interface alias description from iproute2.
3.7.8-3.7.10, 4.0.0-4.1.13.7.11-3.7.12
CM-26288 On the Mellanox switch, static VXLAN tunnels incorrectly allow traffic from any remote tunnel IP address.3.7.8-3.7.12, 4.0.0-4.1.1
CM-26256 The net show evpn vni detail json command includes an extra empty dictionary at the end of the output.3.7.8-3.7.12, 4.0.0-4.1.1
CM-26241 On the Dell S5248F-ON switch, smond might generate syslog messages indicating that the fan input RPM is lower than the normal low speed of 2500 RPM. Speeds as low as 1700 RPM are acceptable in normal thermal environments; therefore, you can ignore these messages.3.7.6-3.7.11, 4.0.0-4.1.13.7.12
CM-26217 NCLU does not allow you to configure OSPF NSSAs. For example:
cumulus@switch:~$ net add ospf area 0.0.0.1 nssa 
ERROR: Command not found.
net add ospf area 0.0.0.1 nssa

To work around this issue, use FRR instead. For example:
switch# configure terminal 
switch(config)# router ospf
switch(config-router)# area 0.0.0.1 nssa

3.7.7-3.7.10, 4.0.0-4.1.13.7.11-3.7.12
CM-26179 If a hostname contains utf-8 characters, the NCLU net show lldp command outputs the following error:
ERROR: ‘ascii’ codec can’t encode character u’\xe9’ in position 3: ordinal not in range(128) 
See /var/log/netd.log for more details.

3.7.7-3.7.10, 4.0.0-4.1.13.7.11-3.7.12
CM-26147 On the EdgeCore AS4610 switch, the ping command fails unless you run the command with sudo.
To work around this issue, run the following commands:
 cumulus@switch:~$ sudo setcap cap_net_raw+ep /usr/share/mgmt-vrf/bin/ping 
cumulus@switch:~$ sudo setcap cap_net_raw+ep /usr/share/mgmt-vrf/bin/ping6

Run the following command to verify the workaround:
 
cumulus@switch:~$ getcap /usr/share/mgmt-vrf/bin/ping*

You should see the following output:
 
/usr/share/mgmt-vrf/bin/ping = cap_net_raw+ep
/usr/share/mgmt-vrf/bin/ping6 = cap_net_raw+ep

3.7.6-3.7.10, 4.1.0-4.1.13.7.11-4.0.0
CM-26139 Selective ERSPAN does not work when you specify a bridge port.3.7.6-3.7.12, 4.0.0-4.1.1
CM-26138 You cannot specify a source and destination MAC address in an ERSPAN ebtables rule. For example, the following rule does not work:
-A FORWARD -i swp5 -s 00:25:90:b2:bd:9d -d 50:6b:4b:96:c4:04 -j erspan –src-ip 100.1.1.2 –dst-ip 100.1.1.1 –ttl 64

3.7.6-3.7.12, 4.0.0-4.1.1
CM-26137 ERSPAN in ebtables does not work for VNIs. For example, the following rule does not work:
-A FORWARD -i vni10 -j erspan –src-ip 100.1.1.2 –dst-ip 100.1.1.1 –ttl 64

3.7.6-3.7.12, 4.0.0-4.1.1
CM-26136 In an ebtables rule, ERSPAN (upper case) does not work. You need to specify erspan (lower case).3.7.6-3.7.12, 4.0.0-4.1.1
CM-25986 On the Mellanox Spectrum-2 switch, the time required to establish a link (from the time a link is set to admin up until the link becomes operationally up) can take up to 15 seconds on 40G interfaces and up to 30 seconds on 100G interfaces.
To work around this issue, wait up to 15 seconds on 40G interfaces and 30 seconds on 100G interfaces for the link to establish.
4.0.0-4.1.1
CM-25923 The default route injected through OSPF when you configure default-information originate always is unreliable and might age out unexpectedly.
To work around this issue, rely on a different source of default route other than injection with default-information originate.
3.7.8-3.7.12, 4.0.0-4.1.1
CM-25890 In some cases, the switchd service might warn of excessive MAC moves from one switch port to itself (for example, from swp18 to swp18).3.7.0-3.7.12, 4.0.0-4.1.1
CM-25859 The MTU of an SVI cannot be higher than the MTU on the bridge. Changing the MTU on the SVI with NCLU does not update the bridge MTU. The net commit command succeeds even though the MTU is not changed as expected.
To work around this issue, change the MTU on all SVIs and the bridge manually in the /etc/network/interfaces file, then apply the change with the ifreload -a command.
3.7.7-3.7.12, 4.0.0-4.1.1
CM-25815 When an SVI with a virtual MAC is configured with a layer 2 VNI in an EVPN environment, if you replace the /etc/network/interfaces file with a different file that does not have the SVI and layer 2 VNI configuration, the original virtual MAC is not populated through the EVPN route until FRR is restarted.3.7.6-3.7.12, 4.0.0-4.1.1
CM-25766 On the Dell-N3048EP-ON switch, when you run the sudo -E apt upgrade command, the upgrade does not work.3.7.7-3.7.12, 4.0.0-4.1.1
CM-25740 On the Broadcom Maverick switch with a QinQ configuration, the packets coming into the CPU might be tagged incorrectly; for example, 802.1ad + 802.1q tags are expected in the packets but the packets have 802.1q + 802.1q tags.
To work around this issue, configure the bridge with bridge-vlan-protocol 802.1ad:
cumulus@switch:~$ net add bridge mybridge vlan-protocol 802.1ad 

3.7.6-3.7.12, 4.0.0-4.1.1
CM-25694 If a packet is policed by ebtables, it does not increment an ACL drop on the ingress interface. Instead, it increments the TDBGC3/6 drop counter to the CPU.3.7.6-3.7.12, 4.0.0-4.1.1
CM-25674 On Mellanox switches, policer iptables are not working as expected. For example, when using a policer with mode KB/MB/GB to rate-limit interfaces, the syntax is accepted but the data plane transfer speed is not affected by the rule.3.7.6-3.7.8, 4.0.0-4.1.13.7.9-3.7.12
CM-25400 If an SVI exists in the configuration before you assign it an IP address, when you do assign the IP address with the NCLU command, the vlan-id and the raw-device bridge stanzas are not added automatically.3.7.6-3.7.12, 4.0.0-4.1.1
CM-25397 When first creating a bond and enslaving an interface, NCLU hides some of the bridge command suggestions, although they are still accepted.3.7.3-3.7.12, 4.0.0-4.1.1
CM-24894 The maximum-prefix configuration under the IPv4 address family has an optional restart value, which you can configure. This configuration is ignored and, instead of restarting the sessions every x minutes, the peer constantly changes between established and idle due to the prefix count being exceeded.3.7.5-3.7.12, 4.0.0-4.1.1
CM-24803 On the Dell N3048EP-ON or the Delta AG6248 switch, when you execute the following command, the switch reboots and then comes right back into Cumulus Linux without installing the new image. The Cumulus Linux image is still in /var/lib/cumulus/installer, which causes issues with cl-support.
 
cumulus@switch:~$ sudo onie-install -fai http://
cumulus@switch:~$ sudo reboot

To work around this issue, use the onie-select command to access ONIE, and then use the nos-install command in ONIE to install a new Cumulus Linux image.
The workaround only works when an out-of-band network is present.
3.7.6-3.7.12, 4.0.0-4.1.1
CM-24799 On switches with the Trident2 ASIC, 802.1Q-encapsulated control plane traffic received on an interface with 802.1AD configured subinterfaces might be dropped.
This issue only affects QinQ configurations.
3.7.5-3.7.12, 4.0.0-4.1.1
CM-24751 On the QuantaMesh T4048-IX8 or EdgeCore AS7326-56X switch, when using a 1000BASE-T SFP module, the module LEDs do not light to reflect link status.3.7.3-3.7.12, 4.0.0-4.1.1
CM-24652 In an EVPN environment, the centralized MAC address is not installed on the MLAG pair because Cumulus Linux does not perform an SVI MAC check per VLAN.
This issue does not affect a pure distributed routing (symmetric or asymmetric) environment or a pure centralized routing environment.
3.7.0-3.7.12, 4.0.0-4.1.1
CM-24618 If the interface alias contains a single or double quotation mark, or an apostrophe, the net show configuration commands fail with the following error:
  ERROR: No closing quotation  See /var/log/netd.log for more details.  

3.6.1-3.7.12, 4.0.0-4.1.1
CM-24473 SNMP incorrectly requires engine ID specification.3.7.4-3.7.12, 4.0.0-4.1.1
CM-24435 When you use NCLU to configure a route map, the parser allows for glob matching of interfaces for a match interface condition when there can only be a single interface matched. The proper syntax is to use multiple route map clauses, each matching a single interface, instead of a single clause matching multiple interfaces.
For example, this command is incorrect:
  net add routing route-map Proxy-ARP permit 25 match interface swp9-10  

These commands are correct:
  net add routing route-map Proxy-ARP permit 25 match interface swp9  net add routing route-map Proxy-ARP permit 30 match interface swp10  

3.7.2-3.7.12, 4.0.0-4.1.1
CM-24426 NCLU allows for the configuration of addresses on VRF interfaces, but tab completion for the net add vrf <name> command just displays . For example:
 
cumulus@switch:~$ net add vrf mgmt


Tab completion for the net add vrf <name> ip address <address> command works correctly.
3.7.4-3.7.12, 4.0.0-4.1.1
CM-24379 On the Maverick switch, CPU forwarded packets might be dropped when there is no route to a leaked host route.3.7.5-3.7.12, 4.0.0-4.1.1
CM-24343 The net del bridge bridge mcsnoop yes command does not return the value to the default of disabled.
To work around this issue, use the net add bridge bridge mcsnoop no command to delete the mcsnoop attribute and return to the default value.
3.7.4-3.7.12, 4.0.0-4.1.1
CM-24332 On the Broadcom switch, when moving configuration from bridged to routed (or toggling from routed to bridged to routed), some traffic is not seen by the kernel. This can cause BGP to not establish on a transit node.3.7.3-3.7.12, 4.0.0-4.1.1
CM-24272 When you try to configure the VRRP priority and advertisement-interval with NCLU on a traditional mode bridge, the net commit command fails.
To work around this issue, use the vtysh command (inside FRR) to change the VRRP priority or advertisement-interval on traditional bridges. For example:
  cumulus@switch:~$ sudo vtysh  switch# configure terminal  switch(config)# interface br0.100  switch(config-if)# vrrp 1 priority 110  switch(config-if)# vrrp 1 advertisement-interval  switch(config-if)# end  switch# write memory  switch# exit  cumulus@switch:~  

3.7.4-3.7.12, 4.0.0-4.1.1
CM-24271 On SVIs in a VLAN-aware bridge, you cannot change the VRRP priority with NCLU.
To work around this issue, run the vtysh command inside FRR to change the default priority. For example:
  cumulus@switch:~$ sudo vtysh  switch# configure terminal  switch(config)# interface vlan100  switch(config-if)# vrrp 1 priority 110  switch(config-if)# end  switch# write memory  switch# exit  cumulus@switch:~  

3.7.4-3.7.12, 4.0.0-4.1.1
CM-24270 Cumulus Linux uses VRRPv3 as the default version, and enables both preempt and accept mode by default. You cannot change these default values with NCLU.
To work around this issue, run the vtysh commands (inside FRR) to change the default values. For example:
  cumulus@switch:~$ sudo vtysh  switch# configure terminal  switch(config)# interface swp4  switch(config-if)# vrrp 1 version 2  switch(config-if)# no vrrp 1 preempt  switch(config-if)# end  switch# write memory  switch# exit  cumulus@switch:~  

3.7.4-3.7.12, 4.0.0-4.1.1
CM-24262 NCLU does not honor auto all in the /etc/network/interfaces file and removes the existing configuration if no individual auto <iface> lines exist.3.7.3-3.7.12, 4.0.0-4.1.1
CM-24241 When you try to remove a BGP peer group configuration with NCLU, the command fails but no warning message is shown. For example:
  cumulus@switch:~$ net del bgp neighbor fabric peer-group  ‘router bgp 65001’ configuration does not have ‘neighbor fabric peer-group’  

3.7.2-3.7.12, 4.0.0-4.1.1
CM-24222 When an LDAP user that does not have NCLU privileges (either in the netshow or netedit group, or in the /etc/netd.conf file) runs an NCLU command, a traceback occurs instead of a permissions error.3.7.0-3.7.12, 4.0.0-4.1.1
CM-24035 On the Edgecore 4610-54P switch, automatic medium-dependent interface crossover (auto-MDIX) stops working on a 100M full duplex interface and does not detect the required cable connection type.3.7.2-3.7.12, 4.0.0-4.1.1
CM-23825 The net add interface <interface> ptm-enable command adds no ptm-enable for that interface in the frr.conf file.
Running the net add or the net del command does not remove no ptm-enable from the frr.conf file. You have to remove it manually using vtysh.
3.7.2-3.7.12, 4.0.0-4.1.1
CM-23665 NCLU automatically adds the VLAN ID (for the layer 3 VNI/SVI) to the bridge when you run net add vxlan <layer3-vni> bridge access <vlan>. This configuration breaks network connectivity in an EVPN symmetric routing configuration using MLAG.
To restore connectivity, remove the VLAN ID from the bridge.
3.7.2-3.7.12, 4.0.0-4.1.1
CM-23661 On the Mellanox switch, when you configure a GRE tunnel, the traffic behind the local tunnel endpoint destined through the GRE tunnel is software-forwarded.3.7.2-3.7.12, 4.0.0-4.1.1
CM-23651 In an EVPN symmetric routing configuration, when an IP address is frozen, kernel neighbor table information and kernel VRF routing table information about the frozen IP address might be out-of-sync.3.7.3-3.7.12, 4.0.0-4.1.1
CM-23584 When you configure a control plane ACL to define permit and deny rules destined to the local switch, NCLU programs the control plane ACL rules into the FORWARD chain.3.7.2-3.7.12, 4.0.0-4.1.1
CM-23570 On an RMP/1G-T switch, when you remove link-speed 100 with the NCLU command or by editing the etc/network/interfaces file to revert the 100M interface to the default (1G auto), the interface fails to recover and does not come back up.
After you remove the link-speed, ethtool shows the advertised link modes as not reported and Speed/Duplex as unknown.
To work around this issue and bring the interface back up, either restart switchd or use ethtool to configure the speed, advertised, duplex or MDI-X settings.
Note: The advertised link mode gets set incorrectly if you include 1000baseT/Half. The port will come up successfully at 1G.
3.7.2-3.7.12, 4.0.0-4.1.1
CM-23418 For QSFP modules, the sudo ifdown command does not disable the Tx laser.3.7.2-3.7.12, 4.0.0-4.1.1
CM-23417 If you use NCLU to create an iBGP peering across the peer link, running the net add bgp l2vpn evpn neighbor peerlink.4094 activate command creates a new eBGP neighborship when one has already been configured for iBGP. This is unexpected; the existing iBGP configuration is valid.3.7.0-3.7.12, 4.0.0-4.1.1
CM-23311 In an EVPN centralized routing configuration, where the layer 2 network extends beyond VTEPs, (for example, a host with bridges), the gateway MAC address does not get refreshed in the network when ARP suppression is enabled on the gateway.
To work around this issue, disable ARP suppression on the centralized gateway.
4.0.0-4.1.1
CM-23075 There is a limitation on the number of SVI interfaces you can specify as DHCP relay interfaces in the /etc/default/isc-dhcp-relay file. For example, 1500 SVI interfaces causes the dhcrelay service to exit without a core file and logs similar to the following are generated for the interfaces:
  2018-11-10T23:35:30.992370-08:00 Dev dhcrelay: Listening on LPF/vlan.101/a0:00:00:00:00:51  2018-11-10T23:35:30.993472-08:00 Dev dhcrelay: Sending on LPF/vlan.101/a0:00:00:00:00:51  

Eventually the dhcrelay service stops.
3.7.1-3.7.12, 4.0.0-4.1.1
CM-23021 When you run the mstpctl command, you might see the bridge-port state as blocking when it is actually disabled. You might see the same incorrect bridge-port state when other programs or tools use the output of mstpctl; for example, SNMP output from the BRIDGE-MIB.3.7.1-3.7.12, 4.0.0-4.1.1
CM-22554 If you try to bring down several members of a bond remotely at the same time, the link state of one of the interfaces might not transition correctly to the down state; however, all links show down in hardware.3.6.2-3.7.12, 4.0.0-4.1.1
CM-22386 The BFD packet redirection logic used by OVSDB server high availability mode redirects BUM packets across the peer link. The iptables rule for redirection does differentiate between BFD and non-BFD VXLAN inner packets because the service node sends all frames with its own IP address as the tunnel source IP address. The VXLAN encapsulated BUM packets do not get forwarded to the CPU and do not go through the iptable redirection rule; only VXLAN encapsulated BFD packets get forwarded to the CPU due to the inner MAC DA lookup in hardware.3.7.0-3.7.12, 4.0.0-4.1.1
CM-22301 For an unresolved address, the IPROUTER default policer rule has been modified to not match on packets exiting a TUNNEL and headed to the CPU to resolve the address via ARP. As a result, the following default rule no longer matches TUNNEL ingress packets.
  A $INGRESS_CHAIN –in-interface $INGRESS_INTF -m addrtype –dst-type  IPROUTER -j POLICE –set-mode pkt –set-rate 400 –set-burst 100  

These packets are now policed by catch all rules.
To work around this issue, the VPORT value on a TRIDENT switch must be changed from binary 011 to 100.
3.6.1-3.7.12, 4.0.0-4.1.1
CM-22287 On the EdgeCore AS7712 (Tomahawk) switch running in atomic mode, when a layer 3 ECMP path is brought down, traffic traversing the path stops working for about four seconds. When the switch is changed to non-atomic mode, the delay is less than one second. This issue is seen across OSPF and static ECMP routes.3.6.2-3.7.12, 4.0.0-4.1.1
CM-22228 On switches with the Trident 2+ ASIC, counters associated with VLANs and VRFs are not working.3.7.0-3.7.12, 4.0.0-4.1.1
CM-22041 At a high CPU transmit traffic rate (for example, if there is unexpected CPU generated flooding or replication in software), when the ASIC packet driver cannot keep up with the transmit rate because there are no free DMA buffers, it can back pressure by suspending the switch port transmit queues. This can fill up the application socket buffers resulting in No buffer space available error messages on protocol sockets.
When the driver recovers, it automatically resumes the transmit queues. In most cases these error messages are transient. In rare cases, the hardware queues might get stuck, which you can recover with a switchd restart.
3.4.3-3.7.12, 4.0.0-4.1.1
CM-22020 On the Trident3 switch, static PIM with IIF based on a layer 2 bridge does not work reliably. PIM Join via signaling is required for IPMC to work properly.
To work around this issue, use dynamic signaling (joins) to manage IP multicast traffic.
3.7.0-3.7.12, 4.0.0-4.1.1
CM-21927 When running ifreload on Mellanox Spectrum devices, after updating an interface configuration, sometimes VLANs are not programmed into the hardware data plane. The Linux control plane looks normal but the VLAN has not been programmed into the hardware and packets that arrive for the VLAN might be dropped.
To work around this issue, remove and re-add the affected VLANs from the port.
3.5.3-3.7.12, 4.0.0-4.1.1
CM-21785 The source address of the ICMPv6 time exceeded message (traceroute hop) is sourced from the wrong VRF when the traceroute target resides on the same switch but in a different VRF.3.6.2-3.7.12, 4.0.0-4.1.1
CM-21769 On the Mellanox switch, GRE tunneling does not work if the tunnel source is configured on an SVI interface. If the tunnel source is configured on a physical switch port, then tunneling works as expected.3.6.1-3.7.12, 4.0.0-4.1.1
CM-21678 On a Dell switch with a Maverick ASIC, NetQ might receive false alerts like the following via PagerDuty:
  cumulus@switch:~$ netq show sensors temp changes | grep absent | grep -v psu  P2Leaf01 temp9 networking asic die temp sensor absent 43 105 100 5 Unable to find driver path: /cumulu Add 7d:22h:1m:41s  P2Leaf01 temp6 networking asic die temp sensor absent 45 105 100 5 Unable to find driver path: /cumulu Add 7d:22h:1m:41s  P2Leaf01 temp6 networking asic die temp sensor absent 47 105 100 5 Unable to read temp4_highest Add 9d:23h:26m:6s  P2Leaf01 temp6 networking asic die temp sensor absent 45 105 100 5 Unable to read temp4_highest Add 14d:22h:46m:45s  

This message might occur as a result of a timeout at the hardware level, or the switch might be reporting a failure to get a response.
3.5.3-3.7.12, 4.0.0-4.1.1
CM-21667 FRR does not add BGP ttl-security to either the running configuration or to the /etc/frr/frr.conf file when configured on a peer group instead of a specific neighbor.
To work around this issue, add ttl-security to individual neighbors instead of the peer group.
3.6.1-3.7.12, 4.0.0-4.1.1
CM-21278 The net show lldp command sometimes shows the port description in the Remote Port field. The net show interface command shows the correct value in the Remote Host field.
To work around this issue, use net show interface command for LLDP output when connected to Cisco equipment.
3.5.3-3.7.10, 4.0.0-4.1.13.7.11-3.7.12
CM-21055 On the Mellanox switch, the destination MAC address of ERSPAN GRE packets is set to all zeros; therefore, the first transit switch might drop packets.3.6.0-3.7.12, 4.0.0-4.1.1
CM-20813 Span rules matching the out-interface as a bond do not mirror packets.3.6.0-3.7.12, 4.0.0-4.1.1
CM-20508 The Cumulus-Resource-Query-MIB defines the ability to gather buffer utilization status but when these objects are polled, they return nothing.3.5.3-3.7.12, 4.0.0-4.1.1
CM-20033 The VLAN interface stays up even though the physical link carrying the VLAN is admin or carrier down.3.5.2-3.7.12, 4.0.0-4.1.1
CM-19724 PIM and MSDP entries are set to the internal COS value of 6 so they are grouped together with the bulk traffic priority group in the default traffic.conf file. However, PIM, IGMP, and MSDP are considered control-plane and should be set to the internal COS value of 7.3.5.2-3.7.12, 4.0.0-4.1.1
CM-19454 When you use NCLU to bring a bond admin down (net add bond <bond> link down), the bond interface goes into admin down state but the switch ports enslaved to the bond remain UP. If you are using bond-lacp-bypass-allow or balance-xor mode, the host might continue to send traffic. This traffic will be dropped because although the bond slaves are UP, they are not members of the bridge.
To work around this issue, use the sudo ifdown <bondname> command.
3.5.0-3.7.12, 4.0.0-4.1.1
CM-18192 In FRR, bgp_snmp does not show all BGP peers when peer groups used.3.7.11-3.7.12, 4.0.0-4.1.1
CM-17934 FRR tracks interface speed based on the value it learns from the Linux kernel for that interface. If the interface speed changes, FRR does not update its interface speed cache. This can lead to issues for routing protocols that derive metrics from interface speed as the cost can become out of sync with the interface speed.
To work around this issue, manually define the routing protocol metric for these interfaces or restart FRR.
3.7.6-3.7.12, 4.0.0-4.1.1
CM-17494 In certain cases, a peer device sends an ARP request from a source IP address that is not on the connected subnet and the switch creates a STALE neighbor entry. Eventually, the switch attempts to keep the entry fresh and sends ARP requests to the host. If the host responds, the switch has REACHABLE neighbor entries for hosts that are not on the connected subnet.
To work around this issue, change the value of arp_ignore to 2. See Default ARP Settings in Cumulus Linux for more information.
3.3.2-3.7.12, 4.0.0-4.1.1
CM-16571 NCLU cannot manage rsyslog to addresses routed via a VRF. In Cumulus Linux 4.0.0 and later, management VRF is enabled by default. To work around this issue, update the /etc/network/interfaces file to disable management VRF.3.4.3-3.7.12, 4.0.0-4.1.1
CM-15812 Multicast forwarding fails for IP addresses whose DMAC overlaps with reserved DIPs.3.2.1-3.7.12, 4.0.0-4.1.1

Fixed issues in 4.1.1

Issue IDDescriptionAffects
CM-29151The following security vulnerability in the gnutls28 / libgnutls* packages has been announced for Cumulus Linux 4.x (Cumulus Linux 3.x is not vulnerable):
CVE-2020-15501: GnuTLS 3.6.x before 3.6.13 uses incorrect cryptography for DTLS. The earliest affected version is 3.6.3 (2018-07-16) because of an error in a 2017-10-06 commit. The DTLS client always uses 32 ‘\0’ bytes instead of a random value, and thus contributes no randomness to a DTLS negotiation. This breaks the security guarantees of the DTLS protocol.
Vulnerable: <= 3.6.7-4+deb10u2
Not vulnerable: 3.6.7-4+deb10u3
4.0.0-4.1.0
CM-29111Due to a packaging error, all switches installed from the same Cumulus Linux image have the same SSH host keys. This affects switches originally installed with Cumulus Linux 4.0.0 and 4.1.0 from a disk image only (including those that were upgraded by apt to a later release).As a result, this issue allows an attacker to more easily bypass remote host verification when a user connects by SSH to what is believed to be a previously used remote host but is really the attacker’s host. For example, this issue can be exploited by a spoofing or man-in-the-middle attack.To resolve this issue, generate new SSH host keys for any switch that has Cumulus Linux 4.0.0 or 4.1.0 installed on it:

cumulus@switch:~$ sudo rm /etc/ssh/ssh_host*
cumulus@switch:~$ sudo dpkg-reconfigure openssh-server
cumulus@switch:~$ sudo systemctl restart ssh

After generating new SSH host keys, SSH clients that have previously logged into that switch will see a warning that the switch’s SSH host key changed; this is expected behavior. Be sure to inform anyone who may log in to the switch that you generated new SSH host keys. These users must log in to the affected switches with their SSH clients, where they will be given instructions on how to remove the old SSH host keys from the known hosts files to avoid a spoofing or man-in-the-middle attack directed at their SSH clients.Notes
  • This issue is fixed in Cumulus Linux 4.1.1. However, Cumulus Networks recommends you generate new SSH host keys as this is the most reliable solution.
  • If you upgrade from Cumulus Linux 4.0.0 or 4.1.0 to version 4.1.1 or later using apt-get and you didn’t generate new SSH host keys, you will need to generate new SSH host keys after the upgrade.
  • If you perform a fresh install of Cumulus Linux 4.1.1 or later using a disk image, you will lose your existing local configuration.
4.0.0-4.1.0
CM-29057The following vulnerability was reported in the bluez package. No bluez packages are installed by default on Cumulus Linux 4.x, but libbluetooth3 is available from the repository for optional installation.
CVE-2020-0556: It was reported that the BlueZ’s HID and HOGP profile implementations
don’t specifically require bonding between the device and the host.
Malicious devices can take advantage of this flaw to connect to a target
host and impersonate an existing HID device without security or to cause
an SDP or GATT service discovery to take place which would allow HID
reports to be injected to the input subsystem from a non-bonded source.
4.0.0-4.1.0
CM-29033When using apt-get update && apt-get upgrade to upgrade from Cumulus Linux 4.0.0 or 4.1.0 to version 4.1.1 or later, a message similar to the following may appear.
Reading package lists… Done
E: Repository ‘http://apt.cumulusnetworks.com/repo CumulusLinux-4-latest InRelease’ changed its ‘Label’ value from ‘cumulus-repository-4.0.0’ to ‘cumulus-repository-4.1.0'
E: Repository ‘http://apt.cumulusnetworks.com/repo CumulusLinux-4-latest InRelease’ changed its ‘Codename’ value from ‘CumulusLinux-4.0.0’ to ‘CumulusLinux-4.1.0'
N: This must be accepted explicitly before updates for this repository can be applied. See apt-secure(8) manpage for details.

To work around this issue and proceed with the upgrade, run apt-get update --allow-releaseinfo-change.
4.0.0-4.1.0
CM-28992The following security vulnerability has been announced:
CVE-2020-10531: An issue was discovered in International Components for Unicode (ICU) for C/C++ through 66.1. An integer overflow, leading to a heap-based buffer overflow, exists in the UnicodeString::doAppend() function in common/unistr.cpp.
3.0.0-4.1.0

4.1.0 Release Notes

Open issues in 4.1.0

Issue IDDescriptionAffectsFixed
CM-29760 Several vulnerabilities were discovered in BIND, a DNS server implementation.
bind9-host (containing only /usr/bin/host) and some libraries from the bind9 source package are installed on the switch by default; the BIND server referred to in these vulnerabilities is not installed by default but is available in the repository for optional installation.
CVE-2019-6477: It was discovered that TCP-pipelined queries can bypass tcp-client limits resulting in denial of service.
CVE-2020-8616: It was discovered that BIND does not sufficiently limit the number of fetches performed when processing referrals. An attacker can take advantage of this flaw to cause a denial of service (performance degradation) or use the recursing server in a reflection attack with a high amplification factor.
CVE-2020-8617: It was discovered that a logic error in the code which checks TSIG validity can be used to trigger an assertion failure, resulting in denial of service.
Vulnerable: 9.11.5.P4+dfsg-5.1
Fixed: 9.11.5.P4+dfsg-5.1+deb10u1
4.0.0-4.1.1
CM-29759 When you use nginx and restserver in management VRF to provide a REST API for the switch, nginx starts but restserver fails to start.
To work around this issue, comment out the Requires= line in the /lib/systemd/system/restserver.service. For example:
#Requires=nginx.service restserver.socket

3.7.12, 4.0.0-4.1.1
CM-29667 After installing Cumulus Linux on the Mellanox SN2100 switch, if you break out a port (for example, if you break out swp1 into four ports: swp1s0, swp1s1, swp1s2, swp1s3) in the /etc/cumulus/ports.conf file, then run the systemctl start switchd command, the update does not take effect.
To work around this issue, run the systemctl restart switchd command.
3.7.12, 4.0.0-4.1.1
CM-29594 When you run an Ansible script to replace the /etc/network/interfaces file, then run the ifreload -a command, you see errors similar to the following:
error: swp1s1.2: netlink: cannot set link swp1s1.2 up: operation failed with ‘Network is down’ (100)
warning: cmd ‘/bin/ip addr del 10.0.0.1/24 dev eth0’ failed: returned 2 (RTNETLINK answers: Cannot assign requested address

To work around this issue, run the ifreload -a command a second time.
3.7.12, 4.0.0-4.1.1
CM-29591 When you add an IPv4 route with an IPv6 next hop, switchd crashes.4.1.0-4.1.1
CM-29576 The Conntrack table fills up with OFFLOAD entries for flows that do not match the NAT rules in iptables.4.1.0-4.1.1
CM-29568 When NAT is configured, non-NAT traffic is incorrectly forwarded to the CPU.4.1.0-4.1.1
CM-29556 CVE-2020-11868: ntpd in ntp before 4.2.8p14 and 4.3.x before 4.3.100 allows an off-path attacker to block unauthenticated synchronization via a server mode packet with a spoofed source IP address, because transmissions are rescheduled even when a packet lacks a valid origin timestamp.
This affects: ntp-4.2.8p12 (possibly earlier) and ntp-4.2.8p13
The fix for https://bugs.ntp.org/3445 introduced a bug whereby a system that is running ntp-4.2.8p12 or p13 that only has one unauthenticated time source can be attacked in a way that causes the victim’s next poll to its source to be delayed, for as long as the attack is maintained.
http://support.ntp.org/bin/view/Main/NtpBug3592 gives the following mitigations if it is not possible to upgrade to a version with the fix:
  • Use authentication with symmetric peers.
  • Have enough sources of time. The default NTP configuration in Cumulus Linux has four time sources.
3.0.0-3.7.12, 4.0.0-4.1.1
CM-29546 In vtysh, if you configure, then remove a layer 3 VNI for a VRF, the VNI is removed from zebra even if the VNI interface still exists in the kernel.
If you configure a layer 2 VNI as a layer 3 VNI by mistake, removing the layer 3 VNI binding removes it from zebra but EVPN-learned MACs and neighbors are not installed into the kernel.
To work around this issue, delete, then re-add the missing VNI. For example:
cumulus@switch:~$ sudo ifdown vni10100
cumulus@switch:~$ sudo ifup vni10100

If you flap the link with the ip link set vni10100 down; ip link set vni10100 up commands, zebra does not re-add the VNI.
3.7.12, 4.0.0-4.1.1
CM-29519 The JSON format output of the net show bgp l2vpn evpn summary command shows the incorrect neighbour state.3.7.12, 4.0.0-4.1.1
CM-29485 The following vulnerability affects the openldap package:
CVE-2020-12243: A vulnerability was discovered in OpenLDAP, a free implementation of the Lightweight Directory Access Protocol. LDAP search filters with nested boolean expressions can result in denial of service (slapd daemon crash).
Vulnerable: <= 2.4.47+dfsg-3+deb10u1
Fixed: 2.4.47+dfsg-3+deb10u2
4.0.0-4.1.1
CM-29468 On the Dell S4148T optical module, the low power polarity bit is set incorrectly and the switch port does not come up.
To work around this issue, edit the /etc/hw_init.d/S10qsfp_init.sh file and change the lpmode line to be 0x3f instead of 0x00:
# disable lpmode, reset all QSFP+/QSFP28 ports
echo 0x3f > ${master_cpld}/qsfp_30_25_lpmode
echo 0x3f > ${master_cpld}/qsfp_30_25_modsel
echo 0x3f > ${master_cpld}/qsfp_30_25_reset

Reboot the switch and check that the switch port comes up.
Important: Before upgrading Cumulus Linux 4.x with Debian packages that includes a fix for this problem, you must change the lpmode line back to 0x00.
4.1.0-4.1.1
CM-29460 The following security vulnerabilities affect qemu packages, which are available for optional installation on Cumulus Linux:
CVE-2019-12068: In QEMU 1:4.1-1, 1:2.1+dfsg-12+deb8u6, 1:2.8+dfsg-6+deb9u8, 1:3.1+dfsg-8~deb10u1, 1:3.1+dfsg-8+deb10u2, and 1:2.1+dfsg-12+deb8u12 (fixed), when executing script in lsi_execute_script(), the LSI scsi adapter emulator advances ‘s->dsp’ index to read next opcode. This can lead to an infinite loop if the next opcode is empty. Move the existing loop exit after 10k iterations so that it covers no-op opcodes as well.
CVE-2019-15034: hw/display/bochs-display.c in QEMU 4.0.0 does not ensure a sufficient PCI config space allocation, leading to a buffer overflow involving the PCIe extended config space.
CVE-2019-20382: QEMU 4.1.0 has a memory leak in zrle_compress_data in ui/vnc-enc-zrle.c during a VNC disconnect operation because libz is misused, resulting in a situation where memory allocated in deflateInit2 is not freed in deflateEnd.
CVE-2020-1983: A use after free vulnerability in ip_reass() in ip_input.c of libslirp 4.2.0 and prior releases allows crafted packets to cause a denial of service.
Vulnerable: <= 3.1+dfsg-8+deb10u4
Fixed: 3.1+dfsg-8+deb10u5
4.0.0-4.1.1
CM-29420 When you configure the management interface class (as shown below), eth0 remains in an admin down state on subsequent reboots:
allow-mgmt eth0
iface eth0 inet dhcp
vrf mgmt
allow-mgmt mgmt
iface mgmt
address 127.0.0.1/8
address ::1/128
vrf-table auto

4.1.0-4.1.1
CM-29385 The following vulnerability affects the openssl package:
CVE-2020-1967: Bernd Edlinger discovered that malformed data passed to the SSL_check_chain() function during or after a TLS 1.3 handshake could cause a NULL dereference, resulting in denial of service.
Vulnerable: <= 1.1.1d-0+deb10u2
Fixed: 1.1.1d-0+deb10u3
4.0.0-4.1.1
CM-29367 On switches with the Trident3 ASIC, PFC is not working as expected. If you set the PFC for only one CoS, pause frames are sent for all CoS traffic.3.7.11-3.7.12, 4.0.0-4.1.1
CM-29319 When you configure an RD or RT with NCLU, you see duplicate VNI stanzas in the /etc/frr/frr.conf file.
To work around this issue, manually edit the etc/frr/frr.conf file to define advertise-all-vni before the RD or RT configuration within the l2vpn EVPN address family, then reload the FRR service with the sudo systemctl reload frr command.
4.1.0-4.1.1
CM-29312 FRR incorrectly orders advertise-all-vni to be later in the configuration than manual rd or route-target definitions. This causes the rd or route-target configuration to be misapplied or not applied at all.
To work around this issue, when you manually configure the rd or route-target for a VNI, you must manually edit the /etc/frr/frr.conf file to define advertise-all-vni before the rd or route-target configuration within the l2vpn evpn address family.
4.0.0-4.1.1
CM-29309 When Optimized Multicast Flooding (OMF) is enabled with the bridge.optimized_mcast_flood = TRUE setting in the /etc/cumulus/swichd.conf file, the switch continues to flood IPv6 multicast traffic to all slave ports when there is no MLD join receive.3.7.11-3.7.12, 4.0.0-4.1.1
CM-29296 The following vulnerabilities have been announced in git, which is available in the repository for optional installation:
CVE-2020-5260: Felix Wilhelm of Google Project Zero discovered a flaw in git, a fast, scalable, distributed revision control system. With a crafted URL that contains a newline, the credential helper machinery can be fooled to return credential information for a wrong host.
CVE-2020-11008: Carlo Arenas discovered a flaw in git, a fast, scalable, distributed revision control system. With a crafted URL that contains a newline or empty host, or lacks a scheme, the credential helper machinery can be fooled into providing credential information that is not appropriate for the protocol in use and host being contacted.
Vulnerable: <= 2.20.1-2+deb10u1 (CVE-2020-5260) <= 2.20.1-2+deb10u2 (CVE-2020-11008)
Fixed: 2.20.1-2+deb10u3
4.0.0-4.1.1
CM-29284 The following vulnerabilities affect git, which is available in the repository for optional installation:
CVE-2020-5260: Felix Wilhelm of Google Project Zero discovered a flaw in git, a fast, scalable, distributed revision control system. With a crafted URL that contains a newline, the credential helper machinery can be fooled to return credential information for a wrong host.
CVE-2020-11008: Carlo Arenas discovered a flaw in git, a fast, scalable, distributed revision control system. With a crafted URL that contains a newline or empty host, or lacks a scheme, the credential helper machinery can be fooled into providing credential information that is not appropriate for the protocol in use and host being contacted.
3.0.0-3.7.12, 4.0.0-4.1.1
CM-29270 On Mellanox switches with the Spectrum-2 ASIC, when you use more than 16 bonds on the switch, you might experience forwarding issues or see an error similar to the following in switchd.log:
2020-04-07T15:59:27.345421+10:00 le-266-q14-2-res switchd[8422]: hal_mlx_bond.c:1696 ERR member_fwd_update_cb spartan-bm87 collector set failed for swp3s0: Driver’s Return Status is Non-Zero
2020-04-07T15:59:27.345557+10:00 le-266-q14-2-res switchd[8422]:
2020-04-07T15:59:27.348432+10:00 le-266-q14-2-res switchd[8422]: hal_mlx_bond.c:1705 ERR member_fwd_update_cb spartan-bm87 distributor set failed for swp3s0: Driver’s Return Status is Non-Zero

To work around this issue, configure fewer than 16 bonds on a switch.
4.1.0-4.1.1
CM-29259 You might see the following gport error messages in switchd.log:

2020-04-10T19:50:01.011224+09:00 E1PDX0V1ELF0001 6 switchd[925]: hal_bcm_mdb.c:530 gport 0x800007a find failed
2020-04-10T19:50:01.011631+09:00 E1PDX0V1ELF0001 6 switchd[925]: hal_bcm_mdb.c:530 gport 0x8000009 find failed

These messages are harmless and can be ignored.
3.7.12, 4.0.0-4.1.1
CM-29183 On the Mellanox SN2010 and SN2100 switch, the fan speed might ramp up and down.4.1.0-4.1.1
CM-29178 On Mellanox switches, the thermal monitoring script starts in suspended mode and, as a result, the fans run at sixty percent. You also see the following log message:
hw-management.sh[847]: Thermal algorithm is manually suspend.

To work around this issue, run the following command to enable thermal monitoring:
cumulus@switch:~$ sudo echo 0 > /var/run/hw-management/config/suspend

4.0.0-4.1.1
CM-29165 With FRR or OSPF, you might see an inconsistent link-state advertisement. For example, when you configure the OSPF default originate route as metric-type 1 with a specific metric, Cumulus Linux shows the default originate route as an external metric-type 2 route with the default metric in the database. This issue typically occurs when both IPv4 and IPv6 default routes exist in the routing table.3.7.12, 4.0.0-4.1.1
CM-29151 The following security vulnerability in the gnutls28 / libgnutls* packages has been announced for Cumulus Linux 4.x (Cumulus Linux 3.x is not vulnerable):
CVE-2020-15501: GnuTLS 3.6.x before 3.6.13 uses incorrect cryptography for DTLS. The earliest affected version is 3.6.3 (2018-07-16) because of an error in a 2017-10-06 commit. The DTLS client always uses 32 ‘\0’ bytes instead of a random value, and thus contributes no randomness to a DTLS negotiation. This breaks the security guarantees of the DTLS protocol.
Vulnerable: <= 3.6.7-4+deb10u2
Not vulnerable: 3.6.7-4+deb10u3
4.0.0-4.1.04.1.1
CM-29145 If you try to remove BFD configuration with a reload, the FRR service fails. The reload action results in a TypeError: expected string or bytes-like object error.
You see this issue only if there is default configuration, such as configuration in the /etc/frr/frr.conf file that is suppressed from view in the FRR running configuration.
To work around this issue, remove the default configuration lines; for example:
username cumulus nopassword

4.1.0-4.1.1
CM-29131 NTP does not start when you use the default VRF instead of the management VRF.4.1.0-4.1.1
CM-29111 Due to a packaging error, all switches installed from the same Cumulus Linux image have the same SSH host keys. This affects switches originally installed with Cumulus Linux 4.0.0 and 4.1.0 from a disk image only (including those that were upgraded by apt to a later release).As a result, this issue allows an attacker to more easily bypass remote host verification when a user connects by SSH to what is believed to be a previously used remote host but is really the attacker’s host. For example, this issue can be exploited by a spoofing or man-in-the-middle attack.To resolve this issue, generate new SSH host keys for any switch that has Cumulus Linux 4.0.0 or 4.1.0 installed on it:

cumulus@switch:~$ sudo rm /etc/ssh/ssh_host*
cumulus@switch:~$ sudo dpkg-reconfigure openssh-server
cumulus@switch:~$ sudo systemctl restart ssh

After generating new SSH host keys, SSH clients that have previously logged into that switch will see a warning that the switch’s SSH host key changed; this is expected behavior. Be sure to inform anyone who may log in to the switch that you generated new SSH host keys. These users must log in to the affected switches with their SSH clients, where they will be given instructions on how to remove the old SSH host keys from the known hosts files to avoid a spoofing or man-in-the-middle attack directed at their SSH clients.Notes
  • This issue is fixed in Cumulus Linux 4.1.1. However, Cumulus Networks recommends you generate new SSH host keys as this is the most reliable solution.
  • If you upgrade from Cumulus Linux 4.0.0 or 4.1.0 to version 4.1.1 or later using apt-get and you didn’t generate new SSH host keys, you will need to generate new SSH host keys after the upgrade.
  • If you perform a fresh install of Cumulus Linux 4.1.1 or later using a disk image, you will lose your existing local configuration.
4.0.0-4.1.04.1.1
CM-29068 On the Broadcom switch with the Trident3 ASIC, packet priority remark values assigned from each internal CoS value continue to work with default values; if you change the internal CoS value, the change does not take effect.3.7.11-3.7.12, 4.0.0-4.1.1
CM-29057 The following vulnerability was reported in the bluez package. No bluez packages are installed by default on Cumulus Linux 4.x, but libbluetooth3 is available from the repository for optional installation.
CVE-2020-0556: It was reported that the BlueZ’s HID and HOGP profile implementations
don’t specifically require bonding between the device and the host.
Malicious devices can take advantage of this flaw to connect to a target
host and impersonate an existing HID device without security or to cause
an SDP or GATT service discovery to take place which would allow HID
reports to be injected to the input subsystem from a non-bonded source.
4.0.0-4.1.04.1.1
CM-29044 A large number of flapping peers causes FRR to require a corresponding update to internal data structures that track peer information. Updating this internal data structure does not delete links that are down due to the flapping. The size of this array then grows to contain both current peers as well as peers that should have been deleted during the flap processing. The contents of this array is processed by FRR to poll the links, which consumes CPU for all items in the array. This additional polling consumes more CPU than necessary but has no functional impact.
To work around this issue, restart FRR.
3.7.11-3.7.12, 4.0.0-4.1.1
CM-29043 When a multipath route that contains an EVPN path exists together with an IPv4 BGP path in the VRF, the RMAC to VTEP binding is incorrect. This invalid entry occurs because Cumulus Linux treats IPv4 routes received over the eBGP IPv4 peering incorrectly in the VRF.
To work around this issue, remove the unnecessary eBGP IPv4 peering.
3.7.12, 4.0.0-4.1.1
CM-29033 When using apt-get update && apt-get upgrade to upgrade from Cumulus Linux 4.0.0 or 4.1.0 to version 4.1.1 or later, a message similar to the following may appear.
Reading package lists… Done
E: Repository ‘http://apt.cumulusnetworks.com/repo CumulusLinux-4-latest InRelease’ changed its ‘Label’ value from ‘cumulus-repository-4.0.0’ to ‘cumulus-repository-4.1.0'
E: Repository ‘http://apt.cumulusnetworks.com/repo CumulusLinux-4-latest InRelease’ changed its ‘Codename’ value from ‘CumulusLinux-4.0.0’ to ‘CumulusLinux-4.1.0'
N: This must be accepted explicitly before updates for this repository can be applied. See apt-secure(8) manpage for details.

To work around this issue and proceed with the upgrade, run apt-get update --allow-releaseinfo-change.
4.0.0-4.1.04.1.1
CM-28995 After you flap an MLAG peerlink, a rare condition might occur where routes and neighbors for VXLAN-enabled VLANs are misprogrammed as non-VXLAN routes and neighbors due to VNI state transitions. This results in a forwarding failure for traffic destined to these misprogrammed routes and neighbors.
Note: Do not flap a VNI interface manually. The only expected time for a VNI interface to go down is when the MLAG secondary switch brings the VNIs protodown during a peer link failure where the backup IP address is still active.
To recover from this condition, restart switchd with the sudo systemctl restart switchd command.
3.7.10-3.7.12, 4.1.0-4.1.1
CM-28992 The following security vulnerability has been announced:
CVE-2020-10531: An issue was discovered in International Components for Unicode (ICU) for C/C++ through 66.1. An integer overflow, leading to a heap-based buffer overflow, exists in the UnicodeString::doAppend() function in common/unistr.cpp.
3.0.0-4.1.04.1.1
CM-28982 On the EdgeCore Minipack-AS8000, when you try to configure ROCEv2, you see errors indicating that PFC is not working properly.4.0.0-4.1.1
CM-28948 Cumulus Linux supports a maximum of 300 ACLs for use with 802.1X interfaces. This limit encompasses the default ACLs, pre-auth ACLs and dynamic ACLs. Exceeding this limit can affect the performance of the switch.4.1.0-4.1.1
CM-28944 A change in a route map prefix list that should remove a route might not be reflected in the ospf6 database or in peers, and the route might not be deleted.
To work around this issue, reenter the redistribute <connected\|static> route-map <route-map-name> statement in the configuration.
3.6.2-3.7.12, 4.0.0-4.1.1
CM-28940 If you configure aggregate-address <address> summary-only before a component of the same aggregate is injected into the BGP table with the network or redistribute command, when you remove the aggregate-address configuration, the component stays suppressed; it is not advertised to peers. For example:
Existing configuration:
router bgp 1
address-family ipv4 unicast
aggregate-address 50.0.0.0/8 summary-only
exit-address-family

If you add network 50.0.0.1/32, you see the following (expected) BGP table entries:
Status codes: s suppressed, d damped, h history, * valid, > best, = multipath,
i internal, r RIB-failure, S Stale, R Removed
Origin codes: i - IGP, e - EGP, ? - incomplete
Network Next Hop Metric LocPrf Weight Path
*> 50.0.0.0 0.0.0.0 32768 i
s> 50.0.0.1/32 0.0.0.0 0 32768 i

Removing aggregate-address 50.0.0.0/8 summary-only at this point results in the following (unexpected) BGP table entry:
Status codes: s suppressed, d damped, h history, * valid, > best, = multipath,
i internal, r RIB-failure, S Stale, R Removed
Origin codes: i - IGP, e - EGP, ? - incomplete
Network Next Hop Metric LocPrf Weight Path
s> 50.0.0.1/32 0.0.0.0 0 32768 i

To work around this issue, remove, then re-add the component prefix routes.
3.7.12, 4.0.0-4.1.1
CM-28938 When you install an ACL LOG/DROP rule on a layer 3 ingress interface that is a member of a VRF, traffic that matches this rule is not logged and is still forwarded.
To work around this issue, apply the ACL LOG/DROP rule to the VRF device itself or to the layer 2 VNI.
3.7.6-3.7.12, 4.0.0-4.1.1
CM-28925 The global MTU setting in the mtu.json file does not take effect on SVI interfaces after ifreload -a.
To work around this issue, run sudo systemctl restart networking or restart the switch.
Note: A network restart is a disruptive operation.
4.1.0-4.1.1
CM-28900 You might see a core file in FRRouting related to OSPFv3 if the switch is configured as both an OSPFv3 ABR and ASBR, and other switches in the same area are also configured as both ABR and ASBR. This issue is not seen with a single ABR or ASBR in an area or if there are multiple ASBRs in an area not acting as ABRs. To work around this issue, do not perform redistribution on more than one ABR in the same area.4.0.0-4.1.1
CM-28867 The QuantaMesh BMS T3048-LY8 switch shows a low fan RPM in syslog.3.7.5-3.7.12, 4.0.0-4.1.1
CM-28821 When configuring VRF route leaking, if you define import vrf route-map <name> but do not have any imported VRFs, the route map command displays incorrectly, and as a result, FRR fails to reload.4.0.0-4.1.1
CM-28816 The following security advisory has been announced for bash:
CVE-2019-18276 Qualys scan QID 372268 setuid vulnerability
When bash or bash scripts are run setuid, bash is supposed to drop privileges, but does so incorrectly, so that an attacker with command access to the shell can use enable -f for runtime loading of a new builtin that calls setuid() to regain dropped privileges.
To work around this issue, do not make bash or bash scripts setuid.
3.0.0-3.7.12, 4.0.0-4.1.1
CM-28770 The net add routing route-map <name> permit <seq> set community <comm> command does not add the set statement into the /etc/frr/frr.conf file.4.0.0-4.1.1
CM-28754 On switches with the Trident2+ ASIC, adding SPAN rules disables PBR rules.3.7.3-3.7.12, 4.0.0-4.1.1
CM-28682 On the Mellanox Spectrum switch in an EVPN symmetric configuration with MLAG, simultaneously shutting down the layer 3 interfaces that serve as uplinks to the VXLAN fabric might result in traffic loss of up to 15 seconds.4.1.0-4.1.1
CM-28656 In OVSDB VLAN-aware mode, removing a VTEP binding on the NSX controller fails to clean up all interfaces associated with the logical switch.3.7.12, 4.0.0-4.1.1
CM-28613 In EVPN Active-Active (MLAG) environments, rebooting one member of an MLAG pair should result in the local MAC mobility sequence number reverting to 0. Sometimes a reboot of one MLAG peer results in the local MAC mobility sequence number being set to a non-zero value despite that no more mobility events occur. This issue is cosmetic only, as BGP does not advertise the incorrect sequence number and forwarding entries correctly point to the remote VTEP where the MAC is now located.3.7.12, 4.0.0-4.1.1
CM-28611 In an EVPN Active-Active (MLAG) environment, sometimes a local-to-remote MAC mobility event results in the local sequence number appearing higher than the remote sequence number in zebra. This issue is cosmetic only, as BGP does not advertise the incorrect sequence number and forwarding entries correctly point to the remote VTEP where the MAC is now located.3.7.12, 4.0.0-4.1.1
CM-28497 QinQ across VXLAN on a traditional bridge does not work.4.1.0-4.1.1
CM-28489 The following CVEs were announced for rsyslog:
CVE-2019-17041 CVE-2019-17042rsyslogd, when receiving remote log messages (not enabled by default on Cumulus Linux) with the pmaisforwardedfrom or pmcisconames optional log parsers (also not enabled by default on Cumulus Linux), is vulnerable to CVE-2019-17041 and CVE-2019-17042 where malicious messages that appear to be from AIX or Cisco respectively may be caused to skip sanity checks, resulting in incorrect negative lengths causing heap overflows.
Vulnerable: 8.1901.0-1Recommendation:Do not enable receiving syslog messages from other hosts by the network (with $UDPServerRun or $InputTCPServerRun). Also, do not enable (with $ModLoad) the vulnerable parsers pmaixforwardedfrom or pmcisconames. The default /etc/rsyslog.conf file on Cumulus Linux does not enable any of these.
4.0.0-4.1.1
CM-28465 When you try to configure link-down on a parent interface of a subinterface configured in a VRF, you encounter an error.3.7.11-3.7.12, 4.0.0-4.1.1
CM-28458 NCLU incorrectly allows you to configure port security on bond/MLAG interfaces.
Port security is not supported on bond/MLAG interfaces.
4.0.0-4.1.1
CM-28442 PTM mis-detects incorrect hostnames of LLDP neighbors and does not fail them as expected. Instead they end up in an N/A cabling status.3.7.11-3.7.12, 4.0.0-4.1.1
CM-28441 If a LLDP neighbor advertises a PortDescr that contains commas, ptmctl -d splits the string on the commas and misplaces its components in other columns.3.7.11-3.7.12, 4.0.0-4.1.1
CM-28393 On the Dell S5232F-ON switch, EVPN and dynamic VRF route leaking results in the CPU forwarding traffic to newly-learned type-2 routes.
To work around this issue, restart FRR.
3.7.9-3.7.12, 4.0.0-4.1.1
CM-28376 On the Dell S5232F-ON switch, the output of ledmgrd shows amber_blinking but smonctl shows all OK.3.7.11-3.7.12, 4.0.0-4.1.1
CM-28340 Mellanox switches with the Spectrum A0 ASIC that are integrated with VMware NSX experience BFD connectivity issues with service nodes. As a result, VXLAN tunnels do not work.
Mellanox switches with the Spectrum A1 ASIC do not have this issue.
3.7.11-3.7.12, 4.0.0-4.1.1
CM-28249 On the Mellanox switch, when you modify the buffer and queue configuration without restarting switchd, you might see a one second interruption in forwarding.4.0.0-4.1.1
CM-28226 When you restart the hsflowd service, you see a systemd warning message similar to the following:
Warning: The unit file, source configuration file or drop-ins of hsflowd@mgmt.service changed on disk. Run ‘systemctl daemon-reload’.

4.0.0-4.1.1
CM-28189 When host-resources and ucd-snmp-mib are polled, you see permission denied messages similar to the following:
Jan 30 19:22:53 switch123 snmpd[23172]: Cannot statfs /sys/kernel/debug/tracing: Permission denied

4.0.0-4.1.1
CM-28136 The MLAG switch pair has VLANs defined that are not used on MLAG bonds. These VLANs still synchronize MAC addresses across to the peer switch. This results in log messages that indicate a MAC address is installed and the VLAN is not defined; for example:
RTM_NEWNEIGH with unconfigured vlan XXXX on port peerlink

3.7.10-3.7.12, 4.0.0-4.1.1
CM-28080 TACACS+ through ClearPass is not currently supported. Cumulus Linux sends authorization before authentication, but ClearPass does not accept an authorization before the user is authenticated.3.7.11-3.7.12, 4.0.0-4.1.1
CM-28078 On the Broadcom switch with the Trident3 ASC, packet priority remark values assigned from each internal CoS value continue to work with default values; if you change the internal CoS value, the change does not take effect.3.7.11-3.7.12, 4.0.0-4.1.1
CM-28061 On switches with the Trident3 ASIC, PFC is not working as expected. If you set the PFC for only one CoS, pause frames are sent for all CoS traffic.3.7.11-3.7.12, 4.0.0-4.1.1
CM-28003 The FRR service does not provide a way for automation to know if the configuration applied properly.
To work around this issue, execute the vtysh -f <file> command in the automation file before starting the FRR service to validate the functional configuration and return an error code.
3.7.11-3.7.12, 4.0.0-4.1.1
CM-27999 On the EdgeCore AS7326-56X switch, the PSU fans show constant LOW warnings.3.7.10-3.7.12, 4.0.0-4.1.1
CM-27982 On Broadcom switches, switchd crashes when dynamic VRF route leaking is enabled and the following is true:
  • The default route is leaked from VRF1 to VRF2
  • Hardware-based dynamic VRF route leaking is configured (vrf_route_leak_enable_dynamic is set to TRUE in the /etc/cumulus/switchd.conf file).
    You might see logs similar to the following in /var/log/syslog:
    kernel: [159400.526241] switchd[21374]: segfault at 1229cdd84 ip 00000000004142ca sp 00007ffd557a86d0 error 4 in switchd[400000+71000]

    To work around this issue, use a route map to filter the default route (the source VRF is imported into the destination VRF).
3.7.10-3.7.12, 4.0.0-4.1.1
CM-27957 If you have configured a higher number of ports and VLANs (ports x VLANs) or the switch is a lower-powered (CPU) platform, the switchd service might fail to send a systemd keepalive within the watchdog timeout value (2 minutes by default) and you see an error similar to the following:
bq. systemd[1]: switchd.service watchdog timeout (limit 2min)!

To workaround this issue, either reduce the number of configured interfaces and, or VLANs, or increase the systemd timeout for switchd.service.
To increase the systemd timeout:
  1. Edit the /etc/systemd/system/switchd.service.d/override.conf file and increase the WatchdogSec parameter.
  2. Restart the switchd service with the sudo systemctl restart switchd.service command.
    systemd will attempt to restart the switchd service automatically (after the watchdog timeout). If the restart fails multiple times in a short time period, run the sudo systemctl reset-failed command followed by the sudo systemctl restart switchd command.
3.7.11-3.7.12, 4.0.0-4.1.1
CM-27950 On the Dell S5232F, S5248F, S5296F, and S3048 switch, using the poweroff or halt commands does not fully power off the switch.4.0.0-4.1.1
CM-27753 The EdgeCore Minipack-AS8000 switch supports FEC RS by default; you cannot disable this setting. However, the ethtool --show-fec command output indicates that FEC is disabled. Also, if you try to change the FEC setting, Cumulus Linux reports an error. For example:
cumulus@switch:~$  net add interface swp23 link speed 100000
cumulus@switch:~$ net add interface swp23 link autoneg off
cumulus@switch:~$ net add interface swp23 link fec rs
”/sbin/ifreload -a” failed:
error: swp23: cmd ‘/sbin/ethtool –set-fec swp23 encoding rs’ failed: returned 255 (Cannot set FEC settings: Operation not supported)
Command ‘['/sbin/ifreload’, ‘-a’]’ returned non-zero exit status 1

4.0.0-4.1.1
CM-27678 The net show bridge macs command returns an empty interface column.
To work around this issue, run the bridge fdb show command to show the interface.
4.0.0-4.1.1
CM-27642 The following CVEs were announced that affect the libssh package:
CVE-2019-14889 has been announced in the libssh library, where unsanitized user-provided scp command lines could allow an attacker to execute arbitrary commands on the server.
The libssh library is not installed on Cumulus Linux by default, but is available in the Cumulus Linux 4 repository for optional installation. Note that libssh is distinct from libssh2 and openssh, which are present on the switches and in the repositories.
See the following for more information:
https://www.libssh.org/security/advisories/CVE-2019-14889.txt
https://security-tracker.debian.org/tracker/CVE-2019-14889
4.0.0-4.1.1
CM-27637 On the EdgeCore Minipack-AS8000 switch, a 100G DAC link does not come up when auto-negotiation is enabled on the neighbor. This switch does not support 100G DAC auto-negotiation at this time.4.0.0-4.1.1
CM-27581 On the Delta AG-6248C PoE switch, when you run the apt upgrade command, the upgrade does not work. Cumulus Linux uses uboot directly instead of grub to boot the kernel. Uboot needs a special header to boot the kernel, which is not present. Without this header, when you use the apt upgrade command to upgrade Linux packages, uboot is unable to boot up the kernel.
To work around this issue, upgrade Cumulus Linux by installing the Cumulus Linux image. Run the onie-select command to go into ONIE, and then use the nos-install command in ONIE to install a new image.
This workaround only works when an out-of-band network is present.
3.7.11-3.7.12, 4.0.0-4.1.1
CM-27444 If you use the NCLU commands to configure NTP and run the net add time ntp source <interface> command before you run the net add time ntp server <server> iburst command, the /etc/ntp.conf file is misconfigured.
To work around this issue, run the net add time ntp server <server> iburst command before you run the net add time ntp source <interface> command.
3.7.10-3.7.11, 4.0.0-4.1.13.7.12
CM-27254 On the Mellanox switch with the Spectrum and Spectrum-2 ASIC, IPv6 egress ACLs are not supported on subinterfaces.4.0.0-4.1.1
CM-27243 The length of the netlink message is not set properly for non-bridge family type messages. The same length is used for both bridge and non-bridge even though the bridge family type message has an extra attribute. This causes extra bytes to be left over in non-bridge family type netlink messages.3.7.10, 4.0.0-4.1.13.7.11-3.7.12
CM-27143 On the Dell S5248F-ON switch, the CPU core temperature sensors show ABSENT.4.0.0-4.1.1
CM-27136 With a high number of active routes (20K or more), when you perform a networking restart, the FRR log files might become flooded with error messages associated with the restart. These logs are normal and are not directly a problem. However, the large number of messages can cause the logs to rotate away any previous history, which prevents you from tracing back events leading up to the restart. In a troubleshooting environment, this can be problematic.4.0.0-4.1.1
CM-27099 On the Mellanox switch with the Spectrum-2 ASIC, Precision Time Protocol (PTP) is not currently supported.4.0.0-4.1.1
CM-27094 On the Delta AG9032v1 switch, smonctl and sensors report inaccurate PSU current and power.3.5.0-3.7.12, 4.0.0-4.1.1
CM-27049 On the Mellanox switch with the Spectrum 2 ASIC, interfaces using 100G or 200G Direct Attach Cables (DACs) do not come up with the interface default configuration.
To work around this issue and bring the interfaces up, perform the following configuration on both sides of the link:
  • Set the interface speed to the desired speed
  • Set link auto-negotiation to off
  • Set link FEC to RS mode
4.0.0-4.1.1
CM-27018 If you configure more than one VRR interface on an SVI interface, deleting one of the VRR addresses does not remove the interface/address.3.7.10-3.7.12, 4.0.0-4.1.1
CM-26942 Port security is not currently supported on VX. The NCLU commands produce errors.4.0.0-4.1.1
CM-26921 If you delete an undefined bond, then add a bond slave, the net commit command fails.3.7.9-3.7.12, 4.0.0-4.1.1
CM-26913 FRR configuration commands for an SVI interface might have the \n misplaced in the output. For example:
sudo sh -c “printf ‘interface 50\nvrf TEST description L3 routing interface\n’ » /etc/frr/frr.conf"

should be:
sudo sh -c “printf ‘interface 50 vrf TEST\ndescription L3 routing interface\n’ » /etc/frr/frr.conf"

To work around this issue, configure the interface manually in the /etc/frr/frr.conf file.
3.7.9-3.7.12, 4.0.0-4.1.1
CM-26907 NCLU incorrectly allows you to apply port security configuration on layer 2 and layer 3 ports that are not part of a bridge.4.0.0-4.1.1
CM-26905 When you update the hostname of a switch with the NCLU net add hostname <hostname> command, then run net commit, the lldpd service does not restart and other devices still see the old hostname.
To work around this issue, run the sudo systemctl restart lldpd.service command.
3.7.10-3.7.12, 4.0.0-4.1.1
CM-26875 After you delete an IPv6 numbered BGP peer group neighbor, Cumulus Linux might continue to send route advertisements.
To work around this issue, restart FRR after removing the IPv6 numbered configuration.
3.7.9-3.7.12, 4.0.0-4.1.1
CM-26860 When you run the NCLU net show commit last or net show commit <number> command, where <number> is the last commit, no output is shown.4.0.0-4.1.1
CM-26841 In the ethool -m output, the Revision Compliance field might show Unallocated when the SFF-8363 Revision Compliance value is SFF-8636 version 2.8 or later.4.0.0-4.1.1
CM-26769 Setting ProtoDown on ports populated with SFP modules providing RJ-45 1000BASE-T interfaces does not cause the carrier to be dropped. The kernel shows carrier down; however, the remote device still shows a link.3.7.6-3.7.10, 4.0.0-4.1.13.7.11-3.7.12
CM-26702 On the Mellanox switch with the Spectrum-2 ASIC, policy-based routing (PBR) is not currently supported.4.0.0-4.1.1
CM-26655 If you reconfigure an NTP server with NCLU using different trailing options after the IP address (such as iburst), an invalid configuration is added to the /etc/ntp.conf file. For example:
net add time ntp server 1.2.3.4 iburst
net commit
net add time ntp server 1.2.3.4
net commit

If you need to alter existing server configurations, first remove the server, commit, then re-add the server with any trailing options.
3.7.9-3.7.12, 4.0.0-4.1.1
CM-26599 Auto-negotiation does not work with the QSFP28 cables and a remote system operating at 10G. Attempting to enable auto-negotiation with ethtool -s swp<#> autoneg on returns Operation not supported.
To work around this issue, do not use auto-negotiation and set the local port speed to 10G.
3.7.9-3.7.12, 4.0.0-4.1.1
CM-26595 The NCLU net show lldp command displays the speed of a ganged port group as the speed of one of the individual links, rather than the sum of their speeds.3.7.9-3.7.12, 4.0.0-4.1.1
CM-26516 Applying a policy-based routing (PBR) rule for all traffic from a host might disrupt ARP refresh for that connected host.3.7.5-3.7.12, 4.0.0-4.1.1
CM-26423 NCLU requires you to specify an interface with multiple address-virtual statements in ascending MAC address order.3.7.5-3.7.12, 4.0.0-4.1.1
CM-26412 Mac learning is not disabled by default on a double tagged peer link interface resulting in the MAC address changing between the MLAG bond and the peer link.
To work around this issue, disable MAC learning on QinQ VLANs by adding bridge-learning off to the VLAN stanza in the etc/network/interfaces file.
3.7.9-3.7.12, 4.0.0-4.1.1
CM-26308 An interface alias configured outside FRR using iproute2 is imported into the FRR running configuration and overrides the internal description. After an FRR reload, this causes FRR to delete the interface alias in an inefficient way. Depending on how many interfaces with aliases you have configured, this can cause a FRR reload to time out.
To work around this issue, remove the interface alias description from iproute2.
3.7.8-3.7.10, 4.0.0-4.1.13.7.11-3.7.12
CM-26288 On the Mellanox switch, static VXLAN tunnels incorrectly allow traffic from any remote tunnel IP address.3.7.8-3.7.12, 4.0.0-4.1.1
CM-26256 The net show evpn vni detail json command includes an extra empty dictionary at the end of the output.3.7.8-3.7.12, 4.0.0-4.1.1
CM-26241 On the Dell S5248F-ON switch, smond might generate syslog messages indicating that the fan input RPM is lower than the normal low speed of 2500 RPM. Speeds as low as 1700 RPM are acceptable in normal thermal environments; therefore, you can ignore these messages.3.7.6-3.7.11, 4.0.0-4.1.13.7.12
CM-26217 NCLU does not allow you to configure OSPF NSSAs. For example:
cumulus@switch:~$ net add ospf area 0.0.0.1 nssa 
ERROR: Command not found.
net add ospf area 0.0.0.1 nssa

To work around this issue, use FRR instead. For example:
switch# configure terminal 
switch(config)# router ospf
switch(config-router)# area 0.0.0.1 nssa

3.7.7-3.7.10, 4.0.0-4.1.13.7.11-3.7.12
CM-26179 If a hostname contains utf-8 characters, the NCLU net show lldp command outputs the following error:
ERROR: ‘ascii’ codec can’t encode character u’\xe9’ in position 3: ordinal not in range(128) 
See /var/log/netd.log for more details.

3.7.7-3.7.10, 4.0.0-4.1.13.7.11-3.7.12
CM-26147 On the EdgeCore AS4610 switch, the ping command fails unless you run the command with sudo.
To work around this issue, run the following commands:
 cumulus@switch:~$ sudo setcap cap_net_raw+ep /usr/share/mgmt-vrf/bin/ping 
cumulus@switch:~$ sudo setcap cap_net_raw+ep /usr/share/mgmt-vrf/bin/ping6

Run the following command to verify the workaround:
 
cumulus@switch:~$ getcap /usr/share/mgmt-vrf/bin/ping*

You should see the following output:
 
/usr/share/mgmt-vrf/bin/ping = cap_net_raw+ep
/usr/share/mgmt-vrf/bin/ping6 = cap_net_raw+ep

3.7.6-3.7.10, 4.1.0-4.1.13.7.11-4.0.0
CM-26139 Selective ERSPAN does not work when you specify a bridge port.3.7.6-3.7.12, 4.0.0-4.1.1
CM-26138 You cannot specify a source and destination MAC address in an ERSPAN ebtables rule. For example, the following rule does not work:
-A FORWARD -i swp5 -s 00:25:90:b2:bd:9d -d 50:6b:4b:96:c4:04 -j erspan –src-ip 100.1.1.2 –dst-ip 100.1.1.1 –ttl 64

3.7.6-3.7.12, 4.0.0-4.1.1
CM-26137 ERSPAN in ebtables does not work for VNIs. For example, the following rule does not work:
-A FORWARD -i vni10 -j erspan –src-ip 100.1.1.2 –dst-ip 100.1.1.1 –ttl 64

3.7.6-3.7.12, 4.0.0-4.1.1
CM-26136 In an ebtables rule, ERSPAN (upper case) does not work. You need to specify erspan (lower case).3.7.6-3.7.12, 4.0.0-4.1.1
CM-25986 On the Mellanox Spectrum-2 switch, the time required to establish a link (from the time a link is set to admin up until the link becomes operationally up) can take up to 15 seconds on 40G interfaces and up to 30 seconds on 100G interfaces.
To work around this issue, wait up to 15 seconds on 40G interfaces and 30 seconds on 100G interfaces for the link to establish.
4.0.0-4.1.1
CM-25923 The default route injected through OSPF when you configure default-information originate always is unreliable and might age out unexpectedly.
To work around this issue, rely on a different source of default route other than injection with default-information originate.
3.7.8-3.7.12, 4.0.0-4.1.1
CM-25890 In some cases, the switchd service might warn of excessive MAC moves from one switch port to itself (for example, from swp18 to swp18).3.7.0-3.7.12, 4.0.0-4.1.1
CM-25859 The MTU of an SVI cannot be higher than the MTU on the bridge. Changing the MTU on the SVI with NCLU does not update the bridge MTU. The net commit command succeeds even though the MTU is not changed as expected.
To work around this issue, change the MTU on all SVIs and the bridge manually in the /etc/network/interfaces file, then apply the change with the ifreload -a command.
3.7.7-3.7.12, 4.0.0-4.1.1
CM-25815 When an SVI with a virtual MAC is configured with a layer 2 VNI in an EVPN environment, if you replace the /etc/network/interfaces file with a different file that does not have the SVI and layer 2 VNI configuration, the original virtual MAC is not populated through the EVPN route until FRR is restarted.3.7.6-3.7.12, 4.0.0-4.1.1
CM-25766 On the Dell-N3048EP-ON switch, when you run the sudo -E apt upgrade command, the upgrade does not work.3.7.7-3.7.12, 4.0.0-4.1.1
CM-25740 On the Broadcom Maverick switch with a QinQ configuration, the packets coming into the CPU might be tagged incorrectly; for example, 802.1ad + 802.1q tags are expected in the packets but the packets have 802.1q + 802.1q tags.
To work around this issue, configure the bridge with bridge-vlan-protocol 802.1ad:
cumulus@switch:~$ net add bridge mybridge vlan-protocol 802.1ad 

3.7.6-3.7.12, 4.0.0-4.1.1
CM-25694 If a packet is policed by ebtables, it does not increment an ACL drop on the ingress interface. Instead, it increments the TDBGC3/6 drop counter to the CPU.3.7.6-3.7.12, 4.0.0-4.1.1
CM-25674 On Mellanox switches, policer iptables are not working as expected. For example, when using a policer with mode KB/MB/GB to rate-limit interfaces, the syntax is accepted but the data plane transfer speed is not affected by the rule.3.7.6-3.7.8, 4.0.0-4.1.13.7.9-3.7.12
CM-25400 If an SVI exists in the configuration before you assign it an IP address, when you do assign the IP address with the NCLU command, the vlan-id and the raw-device bridge stanzas are not added automatically.3.7.6-3.7.12, 4.0.0-4.1.1
CM-25397 When first creating a bond and enslaving an interface, NCLU hides some of the bridge command suggestions, although they are still accepted.3.7.3-3.7.12, 4.0.0-4.1.1
CM-24894 The maximum-prefix configuration under the IPv4 address family has an optional restart value, which you can configure. This configuration is ignored and, instead of restarting the sessions every x minutes, the peer constantly changes between established and idle due to the prefix count being exceeded.3.7.5-3.7.12, 4.0.0-4.1.1
CM-24803 On the Dell N3048EP-ON or the Delta AG6248 switch, when you execute the following command, the switch reboots and then comes right back into Cumulus Linux without installing the new image. The Cumulus Linux image is still in /var/lib/cumulus/installer, which causes issues with cl-support.
 
cumulus@switch:~$ sudo onie-install -fai http://
cumulus@switch:~$ sudo reboot

To work around this issue, use the onie-select command to access ONIE, and then use the nos-install command in ONIE to install a new Cumulus Linux image.
The workaround only works when an out-of-band network is present.
3.7.6-3.7.12, 4.0.0-4.1.1
CM-24799 On switches with the Trident2 ASIC, 802.1Q-encapsulated control plane traffic received on an interface with 802.1AD configured subinterfaces might be dropped.
This issue only affects QinQ configurations.
3.7.5-3.7.12, 4.0.0-4.1.1
CM-24751 On the QuantaMesh T4048-IX8 or EdgeCore AS7326-56X switch, when using a 1000BASE-T SFP module, the module LEDs do not light to reflect link status.3.7.3-3.7.12, 4.0.0-4.1.1
CM-24652 In an EVPN environment, the centralized MAC address is not installed on the MLAG pair because Cumulus Linux does not perform an SVI MAC check per VLAN.
This issue does not affect a pure distributed routing (symmetric or asymmetric) environment or a pure centralized routing environment.
3.7.0-3.7.12, 4.0.0-4.1.1
CM-24618 If the interface alias contains a single or double quotation mark, or an apostrophe, the net show configuration commands fail with the following error:
  ERROR: No closing quotation  See /var/log/netd.log for more details.  

3.6.1-3.7.12, 4.0.0-4.1.1
CM-24473 SNMP incorrectly requires engine ID specification.3.7.4-3.7.12, 4.0.0-4.1.1
CM-24435 When you use NCLU to configure a route map, the parser allows for glob matching of interfaces for a match interface condition when there can only be a single interface matched. The proper syntax is to use multiple route map clauses, each matching a single interface, instead of a single clause matching multiple interfaces.
For example, this command is incorrect:
  net add routing route-map Proxy-ARP permit 25 match interface swp9-10  

These commands are correct:
  net add routing route-map Proxy-ARP permit 25 match interface swp9  net add routing route-map Proxy-ARP permit 30 match interface swp10  

3.7.2-3.7.12, 4.0.0-4.1.1
CM-24426 NCLU allows for the configuration of addresses on VRF interfaces, but tab completion for the net add vrf <name> command just displays . For example:
 
cumulus@switch:~$ net add vrf mgmt


Tab completion for the net add vrf <name> ip address <address> command works correctly.
3.7.4-3.7.12, 4.0.0-4.1.1
CM-24379 On the Maverick switch, CPU forwarded packets might be dropped when there is no route to a leaked host route.3.7.5-3.7.12, 4.0.0-4.1.1
CM-24343 The net del bridge bridge mcsnoop yes command does not return the value to the default of disabled.
To work around this issue, use the net add bridge bridge mcsnoop no command to delete the mcsnoop attribute and return to the default value.
3.7.4-3.7.12, 4.0.0-4.1.1
CM-24332 On the Broadcom switch, when moving configuration from bridged to routed (or toggling from routed to bridged to routed), some traffic is not seen by the kernel. This can cause BGP to not establish on a transit node.3.7.3-3.7.12, 4.0.0-4.1.1
CM-24272 When you try to configure the VRRP priority and advertisement-interval with NCLU on a traditional mode bridge, the net commit command fails.
To work around this issue, use the vtysh command (inside FRR) to change the VRRP priority or advertisement-interval on traditional bridges. For example:
  cumulus@switch:~$ sudo vtysh  switch# configure terminal  switch(config)# interface br0.100  switch(config-if)# vrrp 1 priority 110  switch(config-if)# vrrp 1 advertisement-interval  switch(config-if)# end  switch# write memory  switch# exit  cumulus@switch:~  

3.7.4-3.7.12, 4.0.0-4.1.1
CM-24271 On SVIs in a VLAN-aware bridge, you cannot change the VRRP priority with NCLU.
To work around this issue, run the vtysh command inside FRR to change the default priority. For example:
  cumulus@switch:~$ sudo vtysh  switch# configure terminal  switch(config)# interface vlan100  switch(config-if)# vrrp 1 priority 110  switch(config-if)# end  switch# write memory  switch# exit  cumulus@switch:~  

3.7.4-3.7.12, 4.0.0-4.1.1
CM-24270 Cumulus Linux uses VRRPv3 as the default version, and enables both preempt and accept mode by default. You cannot change these default values with NCLU.
To work around this issue, run the vtysh commands (inside FRR) to change the default values. For example:
  cumulus@switch:~$ sudo vtysh  switch# configure terminal  switch(config)# interface swp4  switch(config-if)# vrrp 1 version 2  switch(config-if)# no vrrp 1 preempt  switch(config-if)# end  switch# write memory  switch# exit  cumulus@switch:~  

3.7.4-3.7.12, 4.0.0-4.1.1
CM-24262 NCLU does not honor auto all in the /etc/network/interfaces file and removes the existing configuration if no individual auto <iface> lines exist.3.7.3-3.7.12, 4.0.0-4.1.1
CM-24241 When you try to remove a BGP peer group configuration with NCLU, the command fails but no warning message is shown. For example:
  cumulus@switch:~$ net del bgp neighbor fabric peer-group  ‘router bgp 65001’ configuration does not have ‘neighbor fabric peer-group’  

3.7.2-3.7.12, 4.0.0-4.1.1
CM-24222 When an LDAP user that does not have NCLU privileges (either in the netshow or netedit group, or in the /etc/netd.conf file) runs an NCLU command, a traceback occurs instead of a permissions error.3.7.0-3.7.12, 4.0.0-4.1.1
CM-24035 On the Edgecore 4610-54P switch, automatic medium-dependent interface crossover (auto-MDIX) stops working on a 100M full duplex interface and does not detect the required cable connection type.3.7.2-3.7.12, 4.0.0-4.1.1
CM-23825 The net add interface <interface> ptm-enable command adds no ptm-enable for that interface in the frr.conf file.
Running the net add or the net del command does not remove no ptm-enable from the frr.conf file. You have to remove it manually using vtysh.
3.7.2-3.7.12, 4.0.0-4.1.1
CM-23665 NCLU automatically adds the VLAN ID (for the layer 3 VNI/SVI) to the bridge when you run net add vxlan <layer3-vni> bridge access <vlan>. This configuration breaks network connectivity in an EVPN symmetric routing configuration using MLAG.
To restore connectivity, remove the VLAN ID from the bridge.
3.7.2-3.7.12, 4.0.0-4.1.1
CM-23661 On the Mellanox switch, when you configure a GRE tunnel, the traffic behind the local tunnel endpoint destined through the GRE tunnel is software-forwarded.3.7.2-3.7.12, 4.0.0-4.1.1
CM-23651 In an EVPN symmetric routing configuration, when an IP address is frozen, kernel neighbor table information and kernel VRF routing table information about the frozen IP address might be out-of-sync.3.7.3-3.7.12, 4.0.0-4.1.1
CM-23584 When you configure a control plane ACL to define permit and deny rules destined to the local switch, NCLU programs the control plane ACL rules into the FORWARD chain.3.7.2-3.7.12, 4.0.0-4.1.1
CM-23570 On an RMP/1G-T switch, when you remove link-speed 100 with the NCLU command or by editing the etc/network/interfaces file to revert the 100M interface to the default (1G auto), the interface fails to recover and does not come back up.
After you remove the link-speed, ethtool shows the advertised link modes as not reported and Speed/Duplex as unknown.
To work around this issue and bring the interface back up, either restart switchd or use ethtool to configure the speed, advertised, duplex or MDI-X settings.
Note: The advertised link mode gets set incorrectly if you include 1000baseT/Half. The port will come up successfully at 1G.
3.7.2-3.7.12, 4.0.0-4.1.1
CM-23418 For QSFP modules, the sudo ifdown command does not disable the Tx laser.3.7.2-3.7.12, 4.0.0-4.1.1
CM-23417 If you use NCLU to create an iBGP peering across the peer link, running the net add bgp l2vpn evpn neighbor peerlink.4094 activate command creates a new eBGP neighborship when one has already been configured for iBGP. This is unexpected; the existing iBGP configuration is valid.3.7.0-3.7.12, 4.0.0-4.1.1
CM-23311 In an EVPN centralized routing configuration, where the layer 2 network extends beyond VTEPs, (for example, a host with bridges), the gateway MAC address does not get refreshed in the network when ARP suppression is enabled on the gateway.
To work around this issue, disable ARP suppression on the centralized gateway.
4.0.0-4.1.1
CM-23075 There is a limitation on the number of SVI interfaces you can specify as DHCP relay interfaces in the /etc/default/isc-dhcp-relay file. For example, 1500 SVI interfaces causes the dhcrelay service to exit without a core file and logs similar to the following are generated for the interfaces:
  2018-11-10T23:35:30.992370-08:00 Dev dhcrelay: Listening on LPF/vlan.101/a0:00:00:00:00:51  2018-11-10T23:35:30.993472-08:00 Dev dhcrelay: Sending on LPF/vlan.101/a0:00:00:00:00:51  

Eventually the dhcrelay service stops.
3.7.1-3.7.12, 4.0.0-4.1.1
CM-23021 When you run the mstpctl command, you might see the bridge-port state as blocking when it is actually disabled. You might see the same incorrect bridge-port state when other programs or tools use the output of mstpctl; for example, SNMP output from the BRIDGE-MIB.3.7.1-3.7.12, 4.0.0-4.1.1
CM-22554 If you try to bring down several members of a bond remotely at the same time, the link state of one of the interfaces might not transition correctly to the down state; however, all links show down in hardware.3.6.2-3.7.12, 4.0.0-4.1.1
CM-22386 The BFD packet redirection logic used by OVSDB server high availability mode redirects BUM packets across the peer link. The iptables rule for redirection does differentiate between BFD and non-BFD VXLAN inner packets because the service node sends all frames with its own IP address as the tunnel source IP address. The VXLAN encapsulated BUM packets do not get forwarded to the CPU and do not go through the iptable redirection rule; only VXLAN encapsulated BFD packets get forwarded to the CPU due to the inner MAC DA lookup in hardware.3.7.0-3.7.12, 4.0.0-4.1.1
CM-22301 For an unresolved address, the IPROUTER default policer rule has been modified to not match on packets exiting a TUNNEL and headed to the CPU to resolve the address via ARP. As a result, the following default rule no longer matches TUNNEL ingress packets.
  A $INGRESS_CHAIN –in-interface $INGRESS_INTF -m addrtype –dst-type  IPROUTER -j POLICE –set-mode pkt –set-rate 400 –set-burst 100  

These packets are now policed by catch all rules.
To work around this issue, the VPORT value on a TRIDENT switch must be changed from binary 011 to 100.
3.6.1-3.7.12, 4.0.0-4.1.1
CM-22287 On the EdgeCore AS7712 (Tomahawk) switch running in atomic mode, when a layer 3 ECMP path is brought down, traffic traversing the path stops working for about four seconds. When the switch is changed to non-atomic mode, the delay is less than one second. This issue is seen across OSPF and static ECMP routes.3.6.2-3.7.12, 4.0.0-4.1.1
CM-22228 On switches with the Trident 2+ ASIC, counters associated with VLANs and VRFs are not working.3.7.0-3.7.12, 4.0.0-4.1.1
CM-22041 At a high CPU transmit traffic rate (for example, if there is unexpected CPU generated flooding or replication in software), when the ASIC packet driver cannot keep up with the transmit rate because there are no free DMA buffers, it can back pressure by suspending the switch port transmit queues. This can fill up the application socket buffers resulting in No buffer space available error messages on protocol sockets.
When the driver recovers, it automatically resumes the transmit queues. In most cases these error messages are transient. In rare cases, the hardware queues might get stuck, which you can recover with a switchd restart.
3.4.3-3.7.12, 4.0.0-4.1.1
CM-22020 On the Trident3 switch, static PIM with IIF based on a layer 2 bridge does not work reliably. PIM Join via signaling is required for IPMC to work properly.
To work around this issue, use dynamic signaling (joins) to manage IP multicast traffic.
3.7.0-3.7.12, 4.0.0-4.1.1
CM-21927 When running ifreload on Mellanox Spectrum devices, after updating an interface configuration, sometimes VLANs are not programmed into the hardware data plane. The Linux control plane looks normal but the VLAN has not been programmed into the hardware and packets that arrive for the VLAN might be dropped.
To work around this issue, remove and re-add the affected VLANs from the port.
3.5.3-3.7.12, 4.0.0-4.1.1
CM-21785 The source address of the ICMPv6 time exceeded message (traceroute hop) is sourced from the wrong VRF when the traceroute target resides on the same switch but in a different VRF.3.6.2-3.7.12, 4.0.0-4.1.1
CM-21769 On the Mellanox switch, GRE tunneling does not work if the tunnel source is configured on an SVI interface. If the tunnel source is configured on a physical switch port, then tunneling works as expected.3.6.1-3.7.12, 4.0.0-4.1.1
CM-21678 On a Dell switch with a Maverick ASIC, NetQ might receive false alerts like the following via PagerDuty:
  cumulus@switch:~$ netq show sensors temp changes | grep absent | grep -v psu  P2Leaf01 temp9 networking asic die temp sensor absent 43 105 100 5 Unable to find driver path: /cumulu Add 7d:22h:1m:41s  P2Leaf01 temp6 networking asic die temp sensor absent 45 105 100 5 Unable to find driver path: /cumulu Add 7d:22h:1m:41s  P2Leaf01 temp6 networking asic die temp sensor absent 47 105 100 5 Unable to read temp4_highest Add 9d:23h:26m:6s  P2Leaf01 temp6 networking asic die temp sensor absent 45 105 100 5 Unable to read temp4_highest Add 14d:22h:46m:45s  

This message might occur as a result of a timeout at the hardware level, or the switch might be reporting a failure to get a response.
3.5.3-3.7.12, 4.0.0-4.1.1
CM-21667 FRR does not add BGP ttl-security to either the running configuration or to the /etc/frr/frr.conf file when configured on a peer group instead of a specific neighbor.
To work around this issue, add ttl-security to individual neighbors instead of the peer group.
3.6.1-3.7.12, 4.0.0-4.1.1
CM-21278 The net show lldp command sometimes shows the port description in the Remote Port field. The net show interface command shows the correct value in the Remote Host field.
To work around this issue, use net show interface command for LLDP output when connected to Cisco equipment.
3.5.3-3.7.10, 4.0.0-4.1.13.7.11-3.7.12
CM-21055 On the Mellanox switch, the destination MAC address of ERSPAN GRE packets is set to all zeros; therefore, the first transit switch might drop packets.3.6.0-3.7.12, 4.0.0-4.1.1
CM-20813 Span rules matching the out-interface as a bond do not mirror packets.3.6.0-3.7.12, 4.0.0-4.1.1
CM-20508 The Cumulus-Resource-Query-MIB defines the ability to gather buffer utilization status but when these objects are polled, they return nothing.3.5.3-3.7.12, 4.0.0-4.1.1
CM-20033 The VLAN interface stays up even though the physical link carrying the VLAN is admin or carrier down.3.5.2-3.7.12, 4.0.0-4.1.1
CM-19724 PIM and MSDP entries are set to the internal COS value of 6 so they are grouped together with the bulk traffic priority group in the default traffic.conf file. However, PIM, IGMP, and MSDP are considered control-plane and should be set to the internal COS value of 7.3.5.2-3.7.12, 4.0.0-4.1.1
CM-19454 When you use NCLU to bring a bond admin down (net add bond <bond> link down), the bond interface goes into admin down state but the switch ports enslaved to the bond remain UP. If you are using bond-lacp-bypass-allow or balance-xor mode, the host might continue to send traffic. This traffic will be dropped because although the bond slaves are UP, they are not members of the bridge.
To work around this issue, use the sudo ifdown <bondname> command.
3.5.0-3.7.12, 4.0.0-4.1.1
CM-18192 In FRR, bgp_snmp does not show all BGP peers when peer groups used.3.7.11-3.7.12, 4.0.0-4.1.1
CM-17934 FRR tracks interface speed based on the value it learns from the Linux kernel for that interface. If the interface speed changes, FRR does not update its interface speed cache. This can lead to issues for routing protocols that derive metrics from interface speed as the cost can become out of sync with the interface speed.
To work around this issue, manually define the routing protocol metric for these interfaces or restart FRR.
3.7.6-3.7.12, 4.0.0-4.1.1
CM-17494 In certain cases, a peer device sends an ARP request from a source IP address that is not on the connected subnet and the switch creates a STALE neighbor entry. Eventually, the switch attempts to keep the entry fresh and sends ARP requests to the host. If the host responds, the switch has REACHABLE neighbor entries for hosts that are not on the connected subnet.
To work around this issue, change the value of arp_ignore to 2. See Default ARP Settings in Cumulus Linux for more information.
3.3.2-3.7.12, 4.0.0-4.1.1
CM-16571 NCLU cannot manage rsyslog to addresses routed via a VRF. In Cumulus Linux 4.0.0 and later, management VRF is enabled by default. To work around this issue, update the /etc/network/interfaces file to disable management VRF.3.4.3-3.7.12, 4.0.0-4.1.1
CM-15812 Multicast forwarding fails for IP addresses whose DMAC overlaps with reserved DIPs.3.2.1-3.7.12, 4.0.0-4.1.1

Fixed issues in 4.1.0

Issue IDDescriptionAffects
CM-28825hostapd is not installed in Cumulus Linux 4.0.0 by default.
To work around this issue, run the following commands to install the package:
cumulus@switch:~$ sudo apt-get update -y
cumulus@switch:~$ sudo apt-get install hostapd -y

4.0.0
CM-28794When the NETQ agent is active, you see the following errors in in the FFR log file:
2020-03-05T16:00:05.036398+09:00 [switch01][bgpd][err] [EC 100663314] Attempting to process an I/O event but for fd: 29(4) no thread to handle this!
2020-03-05T16:01:30.841455+09:00 [switch01[bgpd][err] [EC 100663314] Attempting to process an I/O event but for fd: 29(4) no thread to handle this!

You also see the following errors in the ptmd log file:
2020-03-05T15:59:12.877549+09:00 [switch01][ptmd][info] New client connection fd[17] tot[1]
2020-03-05T15:59:12.899906+09:00 [switch01][ptmd][info] Free client connection fd[17] tot[0]

You can ignore these errors.
4.0.0
CM-28658The OVSDB log contains duplicate MAC addresses with the well-known BFD MAC address (00:23:20:00:00:01). This is mainly cosmetic, but clutters the log.3.7.12-4.0.0
CM-28655When you remove, then re-add an NSX VTEP binding, the VXLAN VTEP interface is not recreated.3.6.1-4.0.0
CM-28609On the Delta AG9032v1 switch, swp5 does not link up using 100G SR4 modules.
To work around this issue, use a different port for 100G SR4 modules.
CM-28533On the Lenovo NE0152T switch, one power supply (PSU2) always show as ABSENT in smonctl.3.7.11-4.0.0
CM-28510The following vulnerabilities were discovered in cURL, an URL transfer library.
CVE-2019-5481: Thomas Vegas discovered a double-free in the FTP-KRB code, triggered by a malicious server sending a very large data block.
CVE-2019-5482: Thomas Vegas discovered a heap buffer overflow that could be triggered when a small non-default TFTP blocksize is used.
Vulnerable: 7.64.0-4
Fixed: 7.64.0-4+deb10u1
4.0.0
CM-28451An error similar to the following shows in syslog for Mellanox switches:
2020-02-12T19:59:22.208012+08:00 leaf01 sx_sdk: RM_TABLE: No resources available to add 1 entries to KVD hash Table HW resource
2020-02-12T19:59:22.208124+08:00 leaf01 sx_sdk: PORT: __port_vport_fid_set err = (No More Resources)

To work around this issue, reboot the switch.
3.7.11-4.0.0
CM-28374When traffic from a double tag interface (facing a different site) is forwarded through VXLAN, the inner tag is not removed. The destination does not know this tag, so it discards it.3.7.8-4.0.0
CM-28372On the EdgeCore AS7326-56X switch, the default fan speed, which is defined in the thermal specification, results in excessive fan noise.3.7.11-4.0.0
CM-28331When you add a route map to advertise IPv4 unicast in a BGP EVPN configuration and the route map contains a set operation, BGP crashes.3.7.11-4.0.0
CM-28313On the EdgeCore Wedge100 and Facebook Wedge-100S switch, certain physical ports are not correctly mapped to the logical ones. For example:
Logical swp39 controls physical swp41
Logical swp40 controls physical swp42
Logical swp43 controls physical swp45
Logical swp44 controls physical swp46
This might causes incorrect forwarding behavior.
3.7.11, 4.0.0
CM-28276When a Trident3 switch receives packets containing an IP checksum value that is not compliant with RFC 1624, the TTL is decremented after a routing operation but the checksum is not recalculated. This results in the IP checksum value being invalid as the packet leaves the switch.3.7.10-3.7.11, 4.0.0
CM-28221The following security vulnerabilities have been announced in qemu, which is not installed by default on Cumulus Linux but is available in the repository for optional installation:
CVE-2019-15890 CVE-2020-7039 CVE-2020-1711: security issues have been found in the SLiRP networking implementation of QEMU, a fast processor emulator, which could result in the execution of arbitrary code or denial of service.
https://security-tracker.debian.org/tracker/source-package/qemu
Vulnerable: <= 3.1+dfsg-8+deb10u3
Fixed: 3.1+dfsg-8+deb10u4
4.0.0
CM-28218The following security vulnerability affects libidn2, which is installed by default on Cumulus Linux:
CVE-2019-18224: A heap-based buffer overflow vulnerability was discovered in the idn2_to_ascii_4i() function in libidn2, the GNU library for Internationalized Domain Names (IDNs), which could result in denial of service, or the execution of arbitrary code when processing a long domain string. For more information, see:
https://security-tracker.debian.org/tracker/libidn2
https://security-tracker.debian.org/tracker/CVE-2019-18224
Vulnerable: 2.0.5-1
Fixed: 2.0.5-1+deb10u1
4.0.0
CM-28200The Mellanox SN3700C switch experiences a kernel memory leak in the bridge IPv4 multicast receive function. When IGMP snooping is disabled, received IGMP packets are cloned and the clone is not freed, causing a memory leak.
Because this memory leak is in the kernel, you cannot clear it by restarting a service; you must reboot the switch to clear the allocated memory.
4.0.0
CM-28169On the Dell Z9264F-ON switch, the CPU core temperature sensors report ABSENT.3.7.11, 4.0.0
CM-28160On the Broadcom Trident3 switch with DHCP relay, where the DHCP server is reachable through the EVPN overlay, DHCP discover packets forwarded to the CPU might appear corrupt and might not get forwarded.3.7.9-4.0.0
CM-28156NCLU crashes when you run the net add interface storage-optimized pfc command because non-ascii quotes exist in the datapath.conf file.
To work around this issue, manually edit the /usr/lib/python2.7/dist-packages/cumulus/__chip_config/mlx/datapath.conf file and replace the non-ascii single quotes with ascii single quotes (standard single quote on the keyboard).
4.0.0
CM-28150On the Broadcom switch with the Trident3 ASIC, the ECN-CE bit is set by default on transit traffic. This might result in hosts adjusting traffic behavior if they are configured for the ECN feature.4.0.0
CM-28119On the Delta AG6248C switch, the NCLU net show system sensors command shows an error:
Could not collect output from command: ['/usr/sbin/smonctl’]

To work around this issue, run the net show system sensors json command instead.
4.0.0
CM-28090Two security issues were found in the Python interface to the apt package manager, which is installed by default on Cumulus Linux; package downloads from unsigned repositories were incorrectly rejected (CVE-2019-15796) and the hash validation relied on MD5 (CVE-2019-15795).
For more information, see https://security-tracker.debian.org/tracker/source-package/python-apt
Vulnerable: 1.8.4
Fixed: 1.8.4.1
4.0.0
CM-28087The last eight ports of the EdgeCore AS4610-54P switch (swp41 through swp48) do not power UPOE access points.3.7.11, 4.0.0
CM-28086The ospfd daemon might crash with the following kernel trace:
2019-11-06T23:00:08.261749+09:00 cumulus ospfd[5339]: Assertion ‘node’ failed in file ospfd/ospf_packet.c, line 671, function ospf_write

3.7.11-4.0.0
CM-28081The cumulus-overrides package contains the /etc/apt/preferences.d/20_prefer_cumulus file that pins packages from specific release names. The pinning file contains the wrong name.
To work around this issue, use the origin instead of the release name.
4.0.0
CM-28077An unhandled exception might occur after you run the sudo poectl -i command. In addition, random poed daemon restarts can occur without any unhandled exceptions but with an invalid response length error. Both issues can occur due to a SerialException.
To work around this issue, power cycle the switch. A software reboot does not resolve the issue.
3.7.10-3.7.11, 4.0.0
CM-28076After you hot swap a PSU, the decode-syseeprom -t psuX command shows the old PSU information (such as the serial number), until you run the decode-syseeprom --init command.3.6.0-4.0.0
CM-28048On the Lenovo NE2580 switch, the fan speeds are higher than expected within normal operating conditions.3.7.11, 4.0.0
CM-28038After you convert a bond back to a layer 2 access port, ifupdown2 changes all SVI MTUs to 1500.
To work around this issue, run ifreload -a a second time.
3.7.11, 4.0.0
CM-28016On the Mellanox Spectrum switch, switchd can sometimes fail when PBR rules are installed or removed from hardware if the rule is setting a next hop learned via a routing protocol.3.7.7-3.7.11, 4.0.0
CM-28007When you configure Cumulus Linux with a /32 address on a switch port with a configured peer address (for example, to connect to a device using IP unnumbered), the switch sends GARPs for the peer address.3.7.5-3.7.11
CM-28000The following security advisory has been announced for the libxen packages, which are not installed by default in Cumulus Linux but are available in the repository for installation:
Debian Security Advisory DSA-4602-1
CVE-2019-17349 CVE-2019-17350 CVE-2019-18420 CVE-2019-18421
CVE-2019-18422 CVE-2019-18423 CVE-2019-18424 CVE-2019-18425
CVE-2019-19577 CVE-2019-19578 CVE-2019-19579 CVE-2019-19580
CVE-2019-19581 CVE-2019-19582 CVE-2019-19583 CVE-2018-12207
CVE-2018-12126 CVE-2018-12127 CVE-2018-12130 CVE-2019-11091
CVE-2019-11135 CVE-2019-17348 CVE-2019-17347 CVE-2019-17346
CVE-2019-17345 CVE-2019-17344 CVE-2019-17343 CVE-2019-17342
CVE-2019-17341 CVE-2019-17340
Multiple vulnerabilities have been discovered in the Xen hypervisor, which
could result in denial of service, guest-to-host privilege escalation or
information leaks.
In addition this update provides mitigations for the “TSX Asynchronous Abort"
speculative side channel attack. For additional information, refer to
https://xenbits.xen.org/xsa/advisory-305.html
For more information, see https://security-tracker.debian.org/tracker/xen .
Fixed version: 4.11.3+24-g14b62ab3e5-1~deb10u1.
4.0.0
CM-27995When enabled on an egress interface, SPAN does not work.
CM-27947Broadcom Field Alert - SID - MMU 2B Errors
A few of the MMU memories on Broadcom switches are grouped together with single parity control. During SER correction when a parity error occurs on one of those groups, other memory in that group might also report a SER error. This occurs when the memory is accessed either by a packet hit or through a schan operation. This issue can cause SER errors in other memory and cause traffic mis-forwarding or a packet drop.
3.7.0-3.7.11, 4.0.0
CM-27875The Mellanox SN3700C switch does not forward LLDP or LACP traffic.4.0.0
CM-27855The FRR cl-support module times out on switches on the ARM platform even when the switch is not under heavy load.
To work around this issue, run the cl-support -M command to disable timeouts.
3.7.0-3.7.11, 4.0.0
CM-27814A traditional bridge with QinQ and a VNI does not work for tagged traffic.3.7.10-4.0.0
CM-27801On the Mellanox SN3700C switch, if you try to break out 100G switch ports into 2x50G, the configuration fails and switchd does not restart. Breaking out the ports into 4x25G works without issue.4.0.0
CM-27793A security vulnerability has been announced in the cyrus-sasl2 (libsasl2-2 and libsasl2-modules) package. The libraries are installed by default on Cumulus Linux.
CVE-2019-19906: Stephan Zeisberg reported an out-of-bounds write vulnerability in the _sasl_add_string() function in cyrus-sasl2, a library implementing the Simple Authentication and Security Layer. A remote attacker can take advantage of this issue to cause denial-of-service conditions for applications using the library.
Vulnerable: 2.1.27+dfsg-1
Fixed: 2.1.27+dfsg-1+deb10u1
3.0.0-4.0.0
CM-27764On the EdgeCore AS7326-56X switch, eth0 and swp1 use the same MAC address.3.7.9-3.7.11, 4.0.0
CM-27740When you run the NCLU net del all command to delete all configuration on the switch, you see an error similar to the following:
ERROR: [Errno 2] No such file or directory: ‘/cumulus/switchd/config/interface//port_security/enable’#012Traceback

4.0.0
CM-27737On the EdgeCore AS7326-56X switch, you might see the RPM of certain fans run over the maximum threshold.3.7.11
CM-27719Several vulnerabilities have been discovered in the interpreter for the Ruby language, which could result in unauthorized access by bypassing intended path matchings, denial of service, or the execution of arbitrary code.
These vulnerabilities affect the ruby2.5 package that is available for optional installation in Cumulus Linux 4.x, but is not installed by default.
CVE-2019-15845: Ruby through 2.4.7, 2.5.x through 2.5.6, and 2.6.x through 2.6.4 mishandles path checking within File.fnmatch functions.
CVE-2019-16201: WEBrick::HTTPAuth::DigestAuth in Ruby through 2.4.7, 2.5.x through 2.5.6, and 2.6.x through 2.6.4 has a regular expression Denial of Service cause by looping/backtracking. A victim must expose a WEBrick server that uses DigestAuth to the Internet or a untrusted network.
CVE-2019-16254: Ruby through 2.4.7, 2.5.x through 2.5.6, and 2.6.x through 2.6.4 allows HTTP Response Splitting. If a program using WEBrick inserts untrusted input into the response header, an attacker can exploit it to insert a newline character to split a header, and inject malicious content to deceive clients.
CVE-2019-16255: Ruby through 2.4.7, 2.5.x through 2.5.6, and 2.6.x through 2.6.4 allows code injection if the first argument (aka the “command” argument) to Shell#[] or Shell#test in lib/shell.rb is untrusted data. An attacker can exploit this to call an arbitrary Ruby method.
Vulnerable: 2.5.5-3
4.0.0
CM-27699In a default VX instance, a ping to a device’s hostname fails.
To work around this issue, edit the /etc/gai.conf file and uncomment precedence ::ffff:0:0/96 10.
4.0.0
CM-27670A memory leak in switchd might occur, which causes switchd to restart.3.7.10-3.7.11, 4.0.0
CM-27645Several vulnerabilities have been discovered in git, a fast, scalable,
distributed revision control system, which is installed by default on Cumulus Linux 4.x.
CVE-2019-1348: export-marks is insecure, fix is to disable by default.
CVE-2019-1349: .git / git~1 filename vulnerability on NTFS
CVE-2019-1352: .git vulnerability with NTFS Alternate Streams Accesses
CVE-2019-1353: NTFS filesystem protection should be on by default
CVE-2019-1387: dubiously-nested submodule git directories should be disallowed
CVE-2019-19604: submodule update repository code execution vulnerability
Vulnerable: <= 2.20.1-2
Fixed: 2.20.1-2+deb10u1
4.0.0
CM-27644Ifupdown2 does not set up the front panel interface for the dhclient to accept the DHCP OFFER.
To work around this issue, restart the networking service after ifreload -a with the systemctl restart networking command.
3.7.10-3.7.11, 4.0.0
CM-27619The following security vulnerabilities have been announced in the nss/libnss3 library, which is not installed by default but is available in the repository:
CVE-2019-11745: Out-of-bounds write when passing an output buffer smaller than the block size to NSC_EncryptUpdate
CVE-2019-17007: nss: Handling of Netscape Certificate Sequences in CERT_DecodeCertPackage() may crash with a NULL deref leading to DoS
See https://security-tracker.debian.org/tracker/source-package/nss for more information.
Vulnerable: <= 3.42.1-1+deb10u1
4.0.0
CM-27586CPU usage might be higher than normal if you have a high number of interfaces x VLANs and lldpd is active. This issue is introduced with code changes in Cumulus Linux 3.7.11, where VLAN information is now available for LLDP to advertise to neighbors (https://docs.cumulusnetworks.com/version/cumulus-linux-37/Layer-2/Link-Layer-Discovery-Protocol/#vlan-dot1-tlv). You might see high CPU usage even if VLAN (dot1) TLV configuration is disabled.
To check if lldpd is the heavy CPU resource user, run the following command:
cumulus@switch:~$  ps -eo user,pid,ppid,cmd,%mem,%cpu –sort=-%cpu | head

Alternatively, check for messages in the /var/log/syslog directory similar to:
2020-02-20T15:02:12.137857-05:00 leaf01 sysmonitor: High CPU use: 87%
2020-02-20T15:02:12.482398-05:00 leaf01 sysmonitor: PID USER PR VIRT RES %CPU %MEM TIME+ COMMAND
2020-02-20T15:02:12.483112-05:00 leaf01 sysmonitor: 1570 _lldpd 20 73244 13800 76.6 0.3 4:43.06 lldpd

Note: The exact amount of CPU usage varies in each network based on a number of factors; however, it is unusual for lldpd to consume more than 30% CPU for an extended period of time.
To work around this issue, you can do one of the following:
  • If the large number of VLANs is not absolutely necessary, manually prune the VLAN allowed list (if you use the range 1-2999, modify the bridge-vids list to include the VLANs being used).
  • Stop the lldpd service. (This approach might be undesirable if the switch is providing services that rely on LLDP such as Voice VLAN.) To stop the lldpd service (runtime setting), run the sudo systemctl stop lldpd.service command. To disable the lldpd service upon boot, run sudo systemctl disable lldpd.service.
3.7.11-4.0.0
CM-27547Trident2+ switches do not enable DFE for 10G and 4x10G DACs. As a result, longer or marginal 10G DACs might not link up reliably.
To work around this issue, run the following command after a reboot.
On the SFP side:
echo CR > /cumulus/switchd/config/interface/swp${port}/interface_mode ; done

On the QSFP side:
echo CR > /cumulus/switchd/config/interface/swp${port}/interface_mode ; done

4.0.0
CM-27517When hsflowd is used on the switch, you might experience a kernel panic.4.0.0
CM-27507The ports.conf file on the Dell S5248F-ON switch does not show port ganging or breakout options.3.7.10-3.7.11
CM-27496All Broadcom Trident3 X7 switches contain PCIE firmware, which is programmed by the vendor when the switch is manufactured. The latest version of this firmware (2.6) is incompatible with Cumulus Linux 3.7.11 and earlier, and Cumulus Linux 4.0.
To work around this issue, downgrade the Broadcom ASIC firmware to an earlier version.
3.7.11, 4.0.0
CM-27457If you delete, then re-add a PBR policy on an interface, the configured PBR policy is not programmed in the kernel or switchd.3.7.9-3.7.10, 4.0.0
CM-27456After making a series of PBR configuration changes using NCLU commands, the stale PBR entry is still present in the kernel.3.7.9-3.7.10, 4.0.0
CM-27367On the Mellanox switch with the Spectrum or Spectrum-2 ASIC, switchd might crash, then restart under certain conditions.4.0.0
CM-27354On the Celestica Pebble switch, if you use IPv6 routes with mask /65 to /127, the switchd log fills with errors.3.7.10-4.0.0
CM-27351On rare occasions, after rebooting the MLAG secondary switch, one MLAG device might see the peer as down, which can cause traffic disruption to connected hosts.3.7.7-3.7.10
CM-27299The protocol daemon bgpd crashes when a link/neighbor flaps if static routes pointing to Null0 are advertising through BGP.
To work around this issue, reboot the switch, then remove the static routes or stop advertising these routes.
3.7.9-3.7.10, 4.0.0
CM-27295IPv6 table rules might affect forwarding. For example, if you create the following rule in the /etc/cumulus/acl/policy.d/03-sshd.rules file, the rule counter increments but IPv4 SSH traffic might be dropped.
[ip6tables]
-A INPUT -p tcp –dport 22 -j DROP

3.7.2-3.7.11, 4.0.0
CM-27275CVE-2018-12207: Improper invalidation for page table updates by a virtual guest operating system for multiple Intel(R) Processors may allow an authenticated user to potentially enable denial of service of the host system via local access.
Running hypervisors for virtual guest operating systems is not supported on Cumulus Linux. Additionally, an affected package qemu is not included in the image, although it is available on upstream repo mirrors.
4.0.0
CM-27229On a traditional bridge, VLAN tagged traffic is not discarded when it exceeds the port security MAC limit.4.0.0
CM-27193The l1-show command prints a traceback for switch ports that have sub-interfaces configured. There is no functional impact to traffic but the l1-show troubleshooting and validation command does not execute on switch ports that have VLAN sub-interfaces.3.7.10, 4.0.0
CM-27184With the port security feature, if you change the number of MAC addresses allowed to access a port with the NCLU net add interface <port> port-security mac-limit <number> command, the net show configuration commands command might fail.4.0.0
CM-27173On the Trident3 switch, unicast ARP packets received on a VNI and forwarded to the CPU are not policed.3.7.10-4.0.0
CM-27118The Broadcom switch with the Tomahawk3 ASIC, such as the EdgeCore Minipack AS8000, might not learn all MAC address on a port configured for bridging when the hardware MAC table is near the maximum capacity.4.0.0
CM-27096On the Edgecore AS6812 switch, you might see rare I2C errors.3.7.2-3.7.10, 4.0.0
CM-27025On the Mellanox switch, ACL lookups are performed for VLAN matches when no rules with UNTAGGED match are present.3.7.2-3.7.10, 4.0.0
CM-26996On the Mellanox switch with the Spectrum ASIC, the --set-burst parameter in an iptables rule does not take effect.3.7.10, 4.0.0
CM-26968When networking fails to start properly, an MLAG memory leak occurs, which might cause memory issues.3.7.9-3.7.10, 4.0.0
CM-26961On the Mellanox switch, error messages with hw-management-thermal-events.sh are displayed on shutdown.4.0.0
CM-26839On the Dell S5248F-ON switch, CPU core temp sensors may show as ABSENT.4.0.0
CM-26838You might experience a bgpd memory usage increase and significant update exchanges due to host moves between VTEPs.3.7.7-3.7.10, 4.0.0
CM-26525When an MLAG peerlink frequently alternates states between learning and blocking, an excessive number of TCP sessions might be created, which results in the following error display:
OSError: [Errno 24] Too many open files

3.6.2-3.7.10, 4.0.0
CM-26450Cumulus Linux poed generates excessive debug log entries. These will be reduced in a future release.3.7.3-3.7.10, 4.0.0
CM-26448Traffic sent to the SVI IP address of a switch might be lost if all of the following conditions are met:
  • The switch is a member of an MLAG pair
  • The traffic is sourced from a layer 2 adjacent host
  • The host is located within a VRF of the MLAG pair
  • The traffic from the source crosses the peer link
  • VXLAN is configured on the MLAG pair
This issue does not impact transit traffic or traffic that does not meet all of the described conditions.
To workaround this issue, restart switchd.
3.7.9-3.7.10, 4.0.0
CM-26225On the EdgeCore AS5712, AS6712, AS5812 and AS6812 switch, support for multiple PSU types results in log messages similar to the following:
2019-09-05T05:15:17.246597+00:00 hp-6712-03 decode-syseeprom: Unable to find eeprom at /sys/bus/i2c/devices/11-0050/eeprom for psu2
2019-09-05T05:15:17.274521+00:00 hp-6712-03 decode-syseeprom: Unable to find eeprom at /sys/bus/i2c/devices/12-0053/eeprom for psu2
2019-09-05T05:15:17.469556+00:00 hp-6712-03 decode-syseeprom: Unable to find eeprom at /sys/bus/i2c/devices/11-0050/eeprom for psu2
2019-09-05T05:15:17.497514+00:00 hp-6712-03 decode-syseeprom: Unable to find eeprom at /sys/bus/i2c/devices/12-0053/eeprom for psu2

3.7.9-4.0.0
CM-26200The following CVEs were announced that affect the systemd-resolved package.
Cumulus Linux does not enable systemd-resolved by default, so Cumulus Linux is not vulnerable as shipped.
CVE-2019-15718
Missing access controls on systemd-resolved’s D-Bus interface
Source Package Release Version Status: buster 241-7 vulnerable
For the detailed security status, refer to the security tracker page at:
https://security-tracker.debian.org/tracker/CVE-2019-15718
4.0.0
CM-26158On the Mellanox switch, UFT profiles are unable to support the documented capacity for routes to addresses that are more than 64 bits in length. The listed capacities assume 64-bit destination IP addresses.3.7.8-3.7.10, 4.0.0
CM-26024On switches with the Spectrum ASIC, the underlay hashes VXLAN packets for a given overlay flow randomly.
To work around this issue, configure the ECMP hash seed to the same value on the EVPN egress leaf switches.
3.7.7-4.0.0
CM-25693After you issue the NCLU net del bgp vrf <vrf> autonomous-system <AS> command and commit the change, Cumulus Linux does not remove the configuration from the /etc/frr/frr.conf file or the net show config commands.3.7.3-3.7.10, 4.0.0
CM-25665On the Broadcom Trident 3 switch, VXLAN encapsulated packets are dropped on the ingress port (tagged layer 2 port) during transit forwarding (the local switch does not terminate the VXLAN tunnel). An example of where this two-layer VXLAN inside VXLAN encapsulation might occur:
  • VXLAN tunnel (#1) between two servers (different racks) to provide layer 2 extension for containers or VM hosts.
  • VXLAN tunnel (#2) between the TOR switch in rack 1 to the TOR switch located in the remote rack.
To work around this issue, either:
  • Configure the edge port (facing the servers) to be an access port (instead of a trunk/tagged port)
  • Change the destination port from 4789 to something else (VXLAN tunnel terminated by the servers)
3.7.5-3.7.11, 4.0.0
CM-25641If the BMC operating system fails to respond to IPMI, you see a traceback in bmcd and all the sensors might report ABSENT devices in smonctl.
To work around this issue, power cycle the switch.
3.7.6-4.0.0
CM-25505In EVPN symmetric or centralized configurations with BGP peering over a peer link, VXLAN routed packets transiting an MLAG peer are dropped until the clagd init-delay timer expires during the bring-up sequence following a reboot.
The problem is caused by a race condition when programming the anycast IP address (used to terminate VXLAN tunnels), where the hardware is programmed before the software by clagd.
To work around this issue, configure the BGP path across the peer link to be less preferred. The example below uses AS path prepending and the MLAG switches are iBGP neighbors. However, other BGP configurations achieve the same result.
In the /etc/frr/frr.conf file, make a new AS path access list and route map to apply BGP pre-pending of the local ASN one or more times. For example:
 
ip as-path access-list MY_ASN permit ^$

route-map peerlink-add-asn permit 10
match as-path MY_ASN
set as-path prepend 4200000101
route-map peerlink-add-asn permit 20

3.7.6-3.7.10, 4.0.0
CM-24993When you try to change the NTP time zone with the NCLU net add time zone <timezone> command or by editing the /etc/timezone file manually, the configuration does not take effect.
To work around this issue, change the time zone with the sudo timedatectl set-timezone <timezone> command. For example:
cumulus@switch:~$ sudo timedatectl set-timezone US/Eastern

4.0.0
CM-23397On the Broadcom switch, when a link-local multicast frame is received on an access port with a VNI in the bridge, two copies of the packet are sent across the VNI to remote VTEPs and the receiving hosts observe duplicate packets.3.6.2-4.0.0
CM-22794The Dell S5048F-ON switch (with reverse airflow, rear to front), shows the Temp-3 sensor as absent.3.6.2-4.0.0
CM-22591CVE-2018-5391 (FragmentSmack) is a network vulnerability where an attacker can trigger time and calculation expensive fragment reassembly with specially crafted packets, leading to a denial of service. On a Cumulus Linux switch, the impact is limited to control plane and management plane traffic. Any control plane traffic coming in the front panel ports will be limited by existing policer ACLs.
To work around this issue, create a file called /etc/sysctl.d/ip.conf and add these settings:
net.ipv4.ipfrag_low_thresh = 196608
net.ipv6.ip6frag_low_thresh = 196608
net.ipv4.ipfrag_high_thresh = 262144
net.ipv6.ip6frag_high_thresh = 262144

3.7.0-3.7.11, 4.0.0
CM-22277On the Broadcom switch with the Trident3 ASIC, the ECN-CE bit is set by default on transit traffic. This might result in hosts adjusting traffic behavior if they are configured for the ECN feature.
In Cumulus Linux 3.7.11, the default behavior changed; the ECN-CE bit is no longer set by default on transit traffic.
3.7.3-3.7.10, 4.0.0
CM-21898On a Trident3 switch, IGMP packets are not policed by the police rule in the 00control ACL file. The packets are policed by the catchall policer in the 99control ACL file instead.
-A $INGRESS_CHAIN -p ipv4 -d 01:00:5e:00:00:00/ff:ff:ff:80:00:00 -j police --set-mode pkt --set-rate 100 --set-burst 100
To work around this issue, let the CPU bound IGMP packet hit the following rule and change the policer rate to a desired value for IGMP packets:
-A $INGRESS_CHAIN -p ipv4 -d 01:00:5e:00:00:00/ff:ff:ff:80:00:00 -j police --set-mode pkt --set-rate 100 --set-burst 100
Typically, the destination MAC address 01:00:5e:xx:xx:xx is used only for PIM/IGMP control and data stream packets. However, this workaround cannot handle data stream multicast packets that are not TCP/UDP; this is not typically done.
3.6.2-4.0.0
CM-19788If you configure a VLAN under a VLAN-aware bridge and create a subinterface of the same VLAN on one of the bridge ports, the bridge and interface compete for the same VLAN and if the interface is flapped, it stops working. Correcting the configuration and running the ifreload command does not resolve the conflict.
To work around this issue, correct the bridge VIDs and restart switchd or delete the subinterface.
3.5.0-4.0.0
CM-18727On the Mellanox SN-2100 switch, unicast packets are counted in multicast queue counters.3.4.3-3.7.10