Cumulus Linux 4.3 Release Notes
4.3.0 Release Notes
Open issues in 4.3.0
|CM-33398||CVE-2021-0326: An issue has been found in wpa, a set of tools to support WPA and WPA2 (IEEE 802.11i). Missing validation of data can result in a buffer over-write, which might lead to a DoS of the wpa_supplicant process or potentially arbitrary code execution.|
Vulnerable: <= 2.8.0-cl3.7.14u1, <= 2.8.0-cl4.2.1u1
|CM-33395||CVE-2021-26937: A flaw in the handling of combining characters in screen, a terminal multiplexer with VT100/ANSI terminal emulation can result in denial of service, or potentially the execution of arbitrary code via a specially crafted UTF-8 character sequence.|
|CM-33394||CVE-2021-27212: A vulnerability in the Certificate List Exact Assertion validation was discovered in OpenLDAP, a free implementation of the Lightweight Directory Access Protocol. An unauthenticated remote attacker can take advantage of this flaw to cause a denial of service (slapd daemon crash) via specially crafted packets.|
Vulnerable: <= 2.4.47+dfsg-3+deb10u5
|CM-33393||DSA-4859-1 (no CVE): zstd, a compression utility, was vulnerable to a race condition: it temporarily exposed, during a very short timeframe, a world-readable version of its input even if the original file had restrictive permissions.|
Vulnerable: <= 1.3.8+dfsg-3+deb10u1
|CM-33385||In a configuration with both traditional and vlan-aware bridges, the VLAN membership check on a vlan-aware switch does not drop PVST BPBUs that come from a traditional bridge.||3.7.14-188.8.131.52, 4.0.0-4.3.0|
|CM-33359||CVE-2020-8625: A buffer overflow vulnerability was discovered in the SPNEGO implementation affecting the GSSAPI security policy negotiation in BIND, a DNS server implementation, which could result in denial of service (daemon crash), or potentially the execution of arbitrary code.|
Vulnerable: <= 9.11.5.P4+dfsg-5.1+deb10u2
|CM-33334||The following vulnerabilities have been announced in the openssl packages:|
CVE-2021-23840: Calls to EVP_CipherUpdate, EVP_EncryptUpdate and EVP_DecryptUpdate may overflow the output length argument in some cases where the input length is close to the maximum permissable length for an integer on the platform. In such cases the return value from the function call will be 1 (indicating success), but the output length value will be negative. This could cause applications to behave incorrectly or crash.
CVE-2021-23841: The OpenSSL public API function X509_issuer_and_serial_hash() attempts to create a unique hash value based on the issuer and serial number data contained
within an X509 certificate. However it fails to correctly handle any errors that may occur while parsing the issuer field (which might occur if the issuer field is maliciously constructed). This may subsequently result in a NULL pointer deref and a crash leading to a potential denial of service attack.
CVE-2019-1551: There is an overflow bug in the x64_64 Montgomery squaring procedure used in exponentiation with 512-bit moduli. No EC algorithms are affected. Analysis suggests that attacks against 2-prime RSA1024, 3-prime RSA1536, and DSA1024 as a result of this defect would be very difficult to perform and are not believed likely. Attacks against DH512 are considered just feasible. However, for an attack the target would have to re-use the DH512 private key, which is not recommended anyway. Also applications directly using the low level API BN_mod_exp may be affected if they use BN_FLG_CONSTTIME.
Vulnerable: <= 1.1.1d-0+deb10u4
|CM-33315||CVE-2020-35498: A vulnerability was found in openvswitch. A limitation in the implementation of userspace packet parsing can allow a malicious user to send a specially crafted packet causing the resulting megaflow in the kernel to be too wide, potentially causing a denial of service. The highest threat from this vulnerability is to system availability.|
Vulnerable: <= 2.8.90-1-cl4u5
|CM-33283||DSA-4850-1 (no CVE): libzstd adds read permissions to files while being compressed or uncompressed.|
root@spine01:mgmt:~# ethtool -m swp51
To work around this issue, run the
|CM-33262||When you change a VRR MAC address, the associated virtual interface goes down.|
To work around this issue, run the
|CM-33258||Cumulus Linux does not support bond members at 200G or greater.||4.0.0-4.3.0|
|CM-33240||On the on the Mellanox SN2410 switch, when you restart |
[ 1446.599850] switch 2-0048: HW semaphore is not released
This is a cosmetic issue and does not affect operation of the switch.
|CM-33237||CVE-2020-36221, CVE-2020-36222, CVE-2020-36223, CVE-2020-36224, CVE-2020-36225, CVE-2020-36226, CVE-2020-36227, CVE-2020-36228, CVE-2020-36229, CVE-2020-36230: Several vulnerabilities were discovered in OpenLDAP, a free implementation of the Lightweight Directory Access Protocol. An unauthenticated remote attacker can take advantage of these flaws to cause a denial of service (slapd daemon crash, infinite loops) via specially crafted packets.|
Vulnerable: <= 2.4.47+dfsg-3+deb10u4
|CM-33196||If you use NCLU to configure an ACL for eth0, you can’t designate it as an INPUT rule; the rule is automatically created as a FORWARD rule in the |
To work around this issue, manually create an ACL in the
|CM-33185||In vtysh you can enable and disable debugs from either exec mode or global configuration mode (config t). When disabling OSPF debugs from exec mode, the debug is disabled at runtime but left in the running-configuration.|
To work around this issue, disable OSPF debugs from global configuration mode (config t).
|CM-33167||On the Mellanox SN4700 switch, if you use the CREDO CABLE with a 4x100 configuration, the system experiences issues accessing the ASIC Thermal sensors.||4.3.0|
|CM-33139||On a Mellanox switch, the ||4.3.0|
|CM-33112||The MTU size configured under a layer 2 VNI interface is not applied for VXLAN traffic.||4.2.1-4.3.0|
|CM-33050||The NCLU |
cumulus@leaf01:~$ net del vrf 55
|CM-33049||You cannot set the time zone can with NCLU commands.||4.1.1-4.3.0|
|CM-33035||EAP-TLS fail on wired connections when the reachability to the RADIUS server does not use the eth0 (mgmt) VRF interface.||4.2.1-4.3.0|
|CM-33032||On Edgecore AS4610 switches, the historic CPU usage displayed in ||3.7.12-184.108.40.206, 4.2.1-4.3.0|
|CM-32953||On Mellanox switches, you can’t ping the SVI of the MLAG peer over the peer link after the packet is VXLAN decapsulated.||4.2.1-4.3.0|
|CM-32951||When the EVPN primary IP address and advertise SVI IP address options are both configured, the SVI ARP is not forwarded between MLAG switches.||4.2.1-4.3.0|
|CM-32914||On Mellanox switches, egress ACLs with VLAN keys do not filter layer 2 multicast or broadcast traffic.||4.3.0|
|CM-32861||The NCLU |
ERROR: — /run/nclu/frr/frr.conf.scratchpad.baseline 2021-01-04 17:23:59.250463331 +0000
To work around this issue, use the FRR command to delete a neighbor.
# net show configuration commands
The correct NCLU command to disable IPv6 forwarding is
|CM-32612||If you try to enable BGP graceful restart when it is already enabled, you see an error similar to the following in the |
2020-12-07T19:20:26.004333+00:00 cumulus bgpd: VRF default: Handle GR command GLOBAL_GR_CMD, current GR state GLOBAL_GR, new GR state GLOBAL_INVALID
This error has no functional impact.
|CM-32588||On the Mellanox SN2700 and SN2410 switch, the MTEF-PSF-AC-I and MTEF-PSR-AC-I PSUs incorrectly show 460W instead of the correct 550W. This is a cosmetic issue that does not affect the actual wattage or throughput of the power supplies.||4.3.0|
|CM-32545||If the FRR and MSTP processes go down, an SNMP TRAP is not generated even with the following configuration in the |
|CM-32516||When using NCLU to add new BGP neighbors to existing configurations, the existence of address-family statements are ignored and the neighbors are added at the end of these lines. This might cause a problem if you try to activate these new neighbors in any of the existing address-family configurations.|
To work around this issue, configure the new BGP neighbors with vtysh.
|CM-32296||If the RMAC of a layer 3 SVI changes, the ||4.2.1-4.3.0|
|CM-32286||On the Mellanox SN3700C switch, PIM multicast packets are duplicated at the egress VTEP.||4.2.0-4.3.0|
|CM-32274||If you apply an outbound route map to a BGP peer that uses |
This might trigger AS path loop prevention on the peer, where the peer ignores locally-originated prefixes.
|CM-32217||The IP address specified in the |
To work around this issue, configure
|CM-32169||OpenSSH is vulnerable to CVE-2020-14145, as described in https://www.fzi.de/fileadmin/user_upload/2020-06-26-FSA-2020-2.pdf.|
This is an information leak in algorithm negotiation that can allow man-in-the-middle attacks on initial connection attempts without a previously stored server host key on the client. If desired, mitigation using UpdateHostKeys and HostKeyAlgorithms is also given in that paper.
|CM-32144||On switches with the Maverick ASIC, control traffic is dropped due to receive buffering.||4.2.0-4.3.0|
|CM-32112||On the ARM platform, NTP peer associations slowly increase to larger offsets (~500ms).||4.0.0-4.3.0|
|CM-32068||Kernel routes added by |
To work around this issue, configure a static route in FRR.
|CM-32055||During a graceful restart of a peer router, if the link between the local system (Helper) and the restarting router flaps, the stale routes announced by the restarting router are no longer used for forwarding by the Helper router even though they remain in the BGP RIB.||4.3.0|
|CM-31962||In a VRRP configuration, BGP unnumbered sessions for VRFs fail to establish after a networking restart.||4.2.0-4.3.0|
|CM-31928||On the Mellanox SN3700C switch, |
2020-10-01T17:48:09.558200+09:00 [sn3700c1][kernel][err] [25666.121068] mlxsw_minimal 2-0048: Could not acquire lock
|CM-31921||The NCLU command to enable bridge learning fails.|
As a work around, enable bridge learning in the
|CM-31917||MLAG packets received on the peer link are dropped instead of routed.||4.2.0-4.3.0|
|CM-31904||The output of the ||4.2.1-4.3.0|
|CM-31605||When you configure an SNMPv3 user with the |
cumulus@switch:mgmt-vrf:~$ sudo net-snmp-config –create-snmpv3-user -a shaauthpass -x aesprivpass -A SHA -X AES userSHAwithAES
To work around this issue, use the NCLU command to configure SNMPv3 user parameters; for example:
cumulus@switch:mgmt-vrf:~$ net add snmp-server username user999 auth-md5 user999password encrypt-des user999encryption
Alternatively, directly edit the
|CM-31418||The default NTP configuration is to use eth0 as the NTP source interface. In Cumulus Linux 4.0 and later, eth0 is in the management VRF by default; therefore the NTP service runs automatically in the management VRF.|
NVIDIA does not recommend running NTP with a source interface other than eth0 as this can expose a security vulnerability. Changing the NTP source interface name with NCLU to a non-management VRF interface might result in NTP not functioning because the NTP service is still running in the management VRF.
|CM-31414||On the Mellanox SN4700 switch, 8x50G port breakout is not supported currently.||4.2.1-4.3.0|
|CM-31404||On the Delta AG7648 switch, the System LED and the Power LED do not display correctly.||3.7.13-220.127.116.11, 4.0.0-4.3.0|
|CM-31327||After you manually edit the |
To work around this issue, run the
|CM-31300||If a neighbour contains a special character in PortID for LLDP, the ||3.7.10-18.104.22.168, 4.2.0-4.3.0|
|CM-31111||On the EdgeCore AS4610 switch, the eth0 interface remains down when physically connected to a 1G interface.|
To work around this issue, configure the link speed to 1000 and set auto-negotiation on for the eth0 interface, then flap eth0 with the
|CM-30987||On the Mellanox switch, RoCE with PFC configuration is not applied to all ports in hardware when a range is used in the |
To work around this issue, use NCLU to configure RoCE with PFC or list individual ports in the
|CM-30879||NCLU restarts FRR when removing a BGP VRF IPv4 aggregate-address command.||3.7.12-22.214.171.124, 4.0.0-4.3.0|
|CM-30863||OpenSSH scp is vulnerable to CVE-2020-15778, where clients that have authorized access to the SSH server can execute commands on the server by copying maliciously named files.|
The two scenarios where an exploit may be useful to an attacker:
-The user is authorized to
-An attacker plants a maliciously named file in a directory tree that someone later uses
Be aware that restricting users to
If you want to use
To disable scp completely, use
|CM-30473||If you modify an interface name, then reuse the previous interface name for a different VLAN, the |
|CM-30422||When you configure a bridge in the ||3.7.12-126.96.36.199, 4.0.0-4.3.0|
|CM-30414||If you toggle VRRP priority values between VRRP routers, then run a |
To work around this issue, remove, then add the VRRP configuration with NCLU commands or vtysh in FRR.
|CM-30312||When TACACS+ is configured and the management VRF is enabled, users with privilege level 13 are prevented from running ||4.0.0-4.3.0|
|CM-30296||The ||3.7.12-188.8.131.52, 4.1.0-4.3.0|
|CM-30280||On a Mellanox SN2010 switch, the Locator LED is on after you upgrade Cumulus Linux.||4.1.0-4.3.0|
|CM-30195||On the Dell S3000 switch, after installing the Cumulus Linux 4.1.1 disk image without a license, the switch sends a link beat if a remote host port is configured.||3.7.11-184.108.40.206, 4.1.1-4.3.0|
|CM-30165||When you use a phone with EAP and voice VLAN is configured (and MAB is not configured), after the phone authenticates, all tagged traffic from the phone is dropped.|
To work around this issue, enable MAB on the interface.
|CM-30101||The NCLU ||3.7.12-220.127.116.11, 4.0.0-4.3.0|
|CM-30089||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.3.0|
|CM-30052||Configuring the subinterface of a VXLAN uplink under another traditional bridge, which also has the VXLAN VNI enslaved, causes |
To work around this issue, do not enslave the subinterface of a VXLAN layer 3 uplink under a traditional bridge in a VXLAN configuration.
|CM-29978||The received PVST BPDU for a VLAN is flooded even though the ingress port doesn’t have the VLAN tagged.||3.7.8-18.104.22.168, 4.0.0-4.3.0|
|CM-29890||Multiple paths to identical EVPN prefixes are either not displayed or not accepted into the l2vpn evpn table if they are received from a different AS.||3.7.12-22.214.171.124, 4.1.1-4.3.0|
|CM-29872||Tab completion for the |
To work around this issue, run the
To work around this issue, look for your string in the output of the
|CM-29759||When you use |
To work around this issue, comment out the
|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 |
To work around this issue, run the
|CM-29652||The ACCTON-DIAG option under the Cumulus Linux GRUB menu does not work. When you select this option, you see the following error:|
error: invalid signature.
|CM-29594||When you run an Ansible script to replace the |
error: swp1s1.2: netlink: cannot set link swp1s1.2 up: operation failed with ‘Network is down’ (100)
To work around this issue, run the
|CM-29562||If you have an SVI with multiple VRR IP addresses and try to delete one of the VRR configurations, ||3.7.12-126.96.36.199, 4.1.1-4.3.0|
|CM-29519||The JSON format output of the ||3.7.12-188.8.131.52, 4.0.0-4.3.0|
|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:|
|CM-29319||When you configure an RD or RT with NCLU, you see duplicate VNI stanzas in the |
To work around this issue, manually edit the
|CM-29309||When Optimized Multicast Flooding (OMF) is enabled with the ||3.7.11-184.108.40.206, 4.0.0-4.3.0|
|CM-29146||On the EdgeCore Minipack AS8000, storm control does not restrict unknown unicast, broadcast, or multicast traffic.||4.1.1-4.3.0|
|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
To work around this issue, do not make bash or bash scripts
|CM-28754||On switches with the Trident2+ ASIC, adding SPAN rules disables PBR rules.||3.7.3-220.127.116.11, 4.0.0-4.3.0|
|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-18.104.22.168, 4.0.0-4.3.0|
|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-22.214.171.124, 4.0.0-4.3.0|
|CM-28497||QinQ across VXLAN on a traditional bridge does not work.||4.1.0-4.3.0|
|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.
|CM-28458||NCLU incorrectly allows you to configure port security on bond/MLAG interfaces.|
Port security is not supported on bond/MLAG interfaces.
|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.
|CM-28249||On the Mellanox switch, when you modify the buffer and queue configuration without restarting ||4.0.0-4.3.0|
|CM-28226||When you restart the |
Warning: The unit file, source configuration file or drop-ins of email@example.com changed on disk. Run ‘systemctl daemon-reload’.
|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-126.96.36.199, 4.0.0-4.3.0|
|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
|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 |
bq. systemd: switchd.service watchdog timeout (limit 2min)!
To workaround this issue, either reduce the number of configured interfaces and, or VLANs, or increase the
To increase the
|CM-27950||On the Dell S5232F, S5248F, S5296F, and S3048 switch, using the ||4.0.0-4.3.0|
|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:
|CM-27444||If you use the NCLU commands to configure NTP and run the |
To work around this issue, run the
|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.3.0||3.7.11-3.7.14|
|CM-27143||On the Dell S5248F-ON switch, the CPU core temperature sensors show ||4.0.0-4.3.0|
|CM-27099||On the Mellanox switch with the Spectrum-2 ASIC, Precision Time Protocol (PTP) is not currently supported.||4.0.0-4.3.0|
|CM-27094||On the Delta AG9032v1 switch, smonctl and sensors report inaccurate PSU current and power.||3.5.0-188.8.131.52, 4.0.0-4.3.0|
|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-184.108.40.206, 4.0.0-4.3.0|
|CM-26942||Port security is not currently supported on VX. The NCLU commands produce errors.||4.0.0-4.3.0|
|CM-26921||If you delete an undefined bond, then add a bond slave, the ||3.7.9-220.127.116.11, 4.0.0-4.3.0|
|CM-26913||FRR configuration commands for an SVI interface might have the |
sudo sh -c “printf ‘interface 50\nvrf TEST description L3 routing interface\n’ » /etc/frr/frr.conf"
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
|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.3.0|
|CM-26905||When you update the hostname of a switch with the NCLU |
To work around this issue, run the
|CM-26860||When you run the NCLU ||4.0.0-4.3.0|
|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.3.0||3.7.11-3.7.14|
|CM-26599||Auto-negotiation does not work with the QSFP28 cables and a remote system operating at 10G. Attempting to enable auto-negotiation with |
To work around this issue, do not use auto-negotiation and set the local port speed to 10G.
|CM-26595||The NCLU ||3.7.9-18.104.22.168, 4.0.0-4.3.0|
|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-22.214.171.124, 4.0.0-4.3.0|
|CM-26423||NCLU requires you to specify an interface with multiple ||3.7.5-126.96.36.199, 4.0.0-4.3.0|
|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
|CM-26308||An interface alias configured outside FRR using |
To work around this issue, remove the interface alias description from
|CM-26288||On the Mellanox switch, static VXLAN tunnels incorrectly allow traffic from any remote tunnel IP address.||3.7.8-188.8.131.52, 4.0.0-4.3.0|
|CM-26256||The ||3.7.8-184.108.40.206, 4.0.0-4.3.0|
|CM-26241||On the Dell S5248F-ON switch, ||3.7.6-3.7.11, 4.0.0-4.3.0||3.7.12-3.7.14|
|CM-26217||NCLU does not allow you to configure OSPF NSSAs. For example:|
cumulus@switch:~$ net add ospf area 0.0.0.1 nssa
To work around this issue, use FRR instead. For example:
switch# configure terminal
|CM-26179||If a hostname contains utf-8 characters, the NCLU |
ERROR: ‘ascii’ codec can’t encode character u’\xe9’ in position 3: ordinal not in range(128)
|CM-26136||In an ebtables rule, ERSPAN (upper case) does not work. You need to specify erspan (lower case).||3.7.6-220.127.116.11, 4.0.0-4.3.0|
|CM-25890||In some cases, the ||3.7.0-18.104.22.168, 4.0.0-4.3.0|
|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 |
To work around this issue, change the MTU on all SVIs and the bridge manually in the
|CM-25815||When an SVI with a virtual MAC is configured with a layer 2 VNI in an EVPN environment, if you replace the ||3.7.6-22.214.171.124, 4.0.0-4.3.0|
|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
cumulus@switch:~$ net add bridge mybridge vlan-protocol 802.1ad
|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-126.96.36.199, 4.0.0-4.3.0|
|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.3.0||3.7.9-3.7.14|
|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 ||3.7.6-188.8.131.52, 4.0.0-4.3.0|
|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-184.108.40.206, 4.0.0-4.3.0|
|CM-24894||The ||3.7.5-220.127.116.11, 4.0.0-4.3.0|
|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.
|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.
|CM-24618||If the interface alias contains a single or double quotation mark, or an apostrophe, the |
ERROR: No closing quotation See /var/log/netd.log for more details.
|CM-24473||SNMP incorrectly requires engine ID specification.||3.7.4-18.104.22.168, 4.0.0-4.3.0|
|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
|CM-24426||NCLU allows for the configuration of addresses on VRF interfaces, but tab completion for the |
Tab completion for the
|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-22.214.171.124, 4.0.0-4.3.0|
To work around this issue, use the
|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-126.96.36.199, 4.0.0-4.3.0|
|CM-24272||When you try to configure the VRRP priority and advertisement-interval with NCLU on a traditional mode bridge, the |
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:~
|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:~
|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:~
|CM-24262||NCLU does not honor ||3.7.3-188.8.131.52, 4.0.0-4.3.0|
|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:|
|CM-24222||When an LDAP user that does not have NCLU privileges (either in the ||3.7.0-184.108.40.206, 4.0.0-4.3.0|
|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-220.127.116.11, 4.0.0-4.3.0|
|CM-23665||NCLU automatically adds the VLAN ID (for the layer 3 VNI/SVI) to the bridge when you run |
To restore connectivity, remove the VLAN ID from the bridge.
|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-18.104.22.168, 4.0.0-4.3.0|
|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-22.214.171.124, 4.0.0-4.3.0|
|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-126.96.36.199, 4.0.0-4.3.0|
|CM-23570||On an RMP/1G-T switch, when you remove |
After you remove the link-speed,
To work around this issue and bring the interface back up, either restart
Note: The advertised link mode gets set incorrectly if you include 1000baseT/Half. The port will come up successfully at 1G.
|CM-23418||For QSFP modules, the ||3.7.2-188.8.131.52, 4.0.0-4.3.0|
|CM-23417||If you use NCLU to create an iBGP peering across the peer link, running the ||3.7.0-184.108.40.206, 4.0.0-4.3.0|
|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.
|CM-23075||There is a limitation on the number of SVI interfaces you can specify as DHCP relay interfaces in the |
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
|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-220.127.116.11, 4.0.0-4.3.0|
|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-18.104.22.168, 4.0.0-4.3.0|
|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.
|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-22.214.171.124, 4.0.0-4.3.0|
|CM-22228||On switches with the Trident 2+ ASIC, counters associated with VLANs and VRFs are not working.||3.7.0-126.96.36.199, 4.0.0-4.3.0|
|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 |
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
|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.
|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-188.8.131.52, 4.0.0-4.3.0|
|CM-21678||On a Dell switch with a Maverick ASIC, NetQ might receive false alerts like the following via PagerDuty:||3.5.3-184.108.40.206, 4.0.0-4.3.0|
|CM-21667||FRR does not add BGP |
To work around this issue, add
To work around this issue, use
|CM-20813||Span rules matching the out-interface as a bond do not mirror packets.||3.6.0-220.127.116.11, 4.0.0-4.3.0|
|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-18.104.22.168, 4.0.0-4.3.0|
|CM-20033||The VLAN interface stays up even though the physical link carrying the VLAN is admin or carrier down.||3.5.2-22.214.171.124, 4.0.0-4.3.0|
|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 ||3.5.2-126.96.36.199, 4.0.0-4.3.0|
|CM-19454||When you use NCLU to bring a bond admin down (|
To work around this issue, use the
|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.
|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
|CM-16571||NCLU cannot manage ||3.4.3-188.8.131.52, 4.0.0-4.3.0|
|CM-15812||Multicast forwarding fails for IP addresses whose DMAC overlaps with reserved DIPs.||3.2.1-184.108.40.206, 4.0.0-4.3.0|
Fixed Issues in 4.3.0
|CM-33160||CVE-2021-3156: A serious heap-based buffer overflow has been discovered in sudo that is exploitable by any local user. It has been given the name Baron Samedit by its discoverer. The bug can be leveraged to elevate privileges to root, even if the user is not listed in the sudoers file. User authentication is not required to exploit the bug.|
Vulnerable: <= 1.8.27-1+deb10u2
|CM-33115||When you run any of the vtysh ||4.2.1|
|CM-32994||On Broadcom switches, after repeated VLAN or VXLAN configuration changes, ||3.7.14, 4.0.0-4.2.1|
|CM-32860||The following vulnerabilities were announced in the p11-kit (libp11-kit0) packages:|
CVE-2020-29361: Multiple integer overflows have been discovered in the array allocations in the p11-kit library and the p11-kit list command, where overflow checks are missing before calling realloc or calloc.
CVE-2020-29362: A heap-based buffer over-read has been discovered in the RPC protocol used by thep11-kit server/remote commands and the client library. When the remote entity supplies a byte array through a serialized PKCS#11 function call, the receiving entity may allow the reading of up to 4 bytes of memory past the heap allocation.
CVE-2020-29363: A heap-based buffer overflow has been discovered in the RPC protocol used by p11-kit server/remote commands and the client library. When the remote entity supplies a serialized byte array in a CK_ATTRIBUTE, the receiving entity may not allocate sufficient length for the buffer to store the deserialized value.
|CM-32829||The NET-SNMP-EXTEND-MIB, disabled in Cumulus Linux 4.2.1 and 3.7.14 to prevent security vulnerability CVE-2020-15862, is re-enabled read-only.||3.7.14-4.2.1|
|CM-32774||You can’t delete a BGP community list created with NCLU.||4.2.1|
|CM-32753||QinQ (802.1Q) packets routed to a layer 3 subinterface are still double tagged with the VLAN of the subinterface and the original inner VLAN when they leave the subinterface.||4.2.0-4.2.1|
|CM-32750||In an EVPN Active/Active configuration, when one of the peers reboots and begins to refresh IP neighbor entries shared by the MLAG peer, some of these ARP messages might be dropped by the MLAG peer’s ARP policer.|
To work around this issue, increase the burst value of the ARP policers to 200 or higher.
|CM-32733||CVE-2020-29479 CVE-2020-29480 CVE-2020-29481 CVE-2020-29482 CVE-2020-29483 CVE-2020-29484 CVE-2020-29485 CVE-2020-29486 CVE-2020-29566 CVE-2020-29570 CVE-2020-29571|
Several security issues affecting Xenstore could result in cross domain access (denial of service, information leaks or privilege escalation) or denial of service against xenstored.
Additional vulnerabilities could result in guest-to-host denial of
Vulnerable: <= 4.11.4+57-g41a822c392-1
|CM-32728||On Broadcom switches, when WARN level ||3.7.14|
|CM-32683||When you change the SVI |
This operation is not supported in the kernel without recreating the SVI. To apply the change, run
|CM-32681||Broadcom switches running Cumulus Linux do not support EVPN Multihoming. When a BGP update with EVPN multihoming attributes is received, |
EVPN Multihoming is supported on Mellanox switches only.
|CM-32661||On the Edgecore AS7312 switch, eth0 and swp use the same MAC address.||3.7.14-4.2.1|
|CM-32647||When you start ||4.2.1|
|CM-32641||CVE-2020-27350: Missing input validation in the ar/tar implementations of APT, the high level package manager, could cause out-of-bounds reads or infinite loops, resulting in denial of service when processing malformed deb files.|
CVE-2020-27351: Various memory and file descriptor leaks were discovered in the Python interface to the APT package management runtime library, which could result in denial of service.
Vulnerable: apt <= 220.127.116.11, python-apt <= 18.104.22.168
Fixed: apt 22.214.171.124, python-apt 126.96.36.199
|CM-32622||The following vulnerability has been announced in OpenSSL:|
CVE-2020-1971: A flaw in the GENERAL_NAME_cmp() function could cause a NULL dereference when both GENERAL_NAMEs contain an EDIPARTYNAME, resulting in denial of service. More information can be found at https://www.openssl.org/news/secadv/20201208.txt .
Vulnerable: <= 1.1.1d-0+deb10u3
|CM-32592||CVE-2020-27670 CVE-2020-27671 CVE-2020-27672 CVE-2020-27674 CVE-2020-28368: Multiple vulnerabilities have been discovered in the Xen hypervisor, which could result in denial of service, privilege escalation or information leaks.|
Vulnerable: < 4.11.4+57-g41a822c392-1
|CM-32554||An EVPN route map filter matching a VNI on egress on the originating router might not set a large-community correctly:|
route-map TEST-TAG permit 10
To work around this issue, remove the VNI match to allow the tag to be applied on egress.
The VNI match works if applied at some other non-originating router either in the ingress or egress direction.
|CM-32532||CVE-2020-8927: A buffer overflow exists in the Brotli library versions prior to 1.0.8 where an attacker controlling the input length of a “one-shot” decompression request to a script can trigger a crash, which happens when copying over chunks of data larger than 2 GiB. If one cannot update to a fixed version, we recommend to use the “streaming” API as opposed to the “one-shot” API, and impose chunk size limits.|
|CM-32420||When running traditional mode bridges at scale (for example, when you have more than 200 bridges and a large number of MAC addresses), MLAG bonds flap intermittently from dual to single connected, then back to dual connected, which causes a layer 2 loop and STP state changes.|
To work around this issue, either shut down one side of the MLAG bond or prune out VLANS over the bond.
|CM-32412||CVE-2020-28196: MIT Kerberos 5 (aka krb5) before 1.17.2 and 1.18.x before 1.18.3 allows unbounded recursion via an ASN.1-encoded Kerberos message because the lib/krb5/asn.1/asn1_encode.c support for BER indefinite lengths lacks a recursion limit.|
|CM-32329||On the Mellanox SN3420 switch, 1000BaseT and 1000Base-SX/LX modules do not link up.||4.2.1|
|CM-32311||CVE-2020-25709, CVE-2020-25710: Two vulnerabilities in the certificate list syntax verification and in the handling of CSN normalization were discovered in OpenLDAP, a free implementation of the Lightweight Directory Access Protocol. An unauthenticated remote attacker can take advantage of these flaws to cause a denial of service (slapd daemon crash) via specially crafted packets.|
Vulnerable: <= 2.4.47+dfsg-3+deb10u3
|CM-32294||Some non-Mellanox ethernet modules do not link up on the Mellanox SN3420 switch with Cumulus PSID in the Hardware revision. To see if a Mellanox SN3420 switch has the Cumulus PSID, check the output of |
To work around this issue, use Mellanox ethernet modules with the Mellanox SN3420 switch,
|CM-32275||After you reboot a Broadcom switch, |
|CM-32235||In an EVPN multihoming configuration, reloading FRR causes brief traffic loss.||4.2.1|
|CM-32219||On the Mellanox SN3700C switch, running ||4.2.1|
|CM-32215||On the Dell S5048F-ON switch, optical transceivers do not come up and the modules are in reset mode.||4.0.0-4.2.1|
|CM-32149||If you try reconfigure a DHCP server after you delete the switch configuration with the |
To work around this issue, edit the
|CM-32110||CVE-2020-25692: A vulnerability in the handling of normalization with modrdn was discovered in OpenLDAP, a free implementation of the Lightweight Directory Access Protocol. An unauthenticated remote attacker can use this flaw to cause a denial of service (slapd daemon crash) via a specially crafted packet.|
The slapd package is not present in the image or repository, although the OpenLDAP libraries are present.
Vulnerable: <= 2.4.47+dfsg-3+deb10u2
|CM-32086||If the peer link does not trunk all VLANs on an MLAG bond, all FDB entries learned through that MLAG bond are not redirected over the peer link when the MLAG bond goes down. As a result, traffic destined to the MAC addresses that arrives on the MLAG peer with the downed MLAG port is dropped.|
To work around this issue, ensure that the peer link trunks all VLANs that exist on all MLAG bonds.
|CM-32030||On the Mellanox SN4600C switch, the fan speed fluctuates when only one PSU is plugged in.|
To work around this issue, use both PSUs.
|CM-32006||Certain Dell S4048-ON switches show an incorrect vendor name and hang when you issue the ||3.7.12-4.2.1|
|CM-31982||The INPUT chain POLICE target acts as ACCEPT instead of continue.||4.2.1|
|CM-31968||The following vulnerability has been announced in freetype:|
CVE-2020-15999: Sergei Glazunov discovered a heap-based buffer overflow vulnerability in the handling of embedded PNG bitmaps in FreeType. Opening malformed fonts may result in denial of service or the execution of arbitrary code.
Vulnerable: <= 2.9.1-3+deb10u1
|CM-31959||With traditional bridges, a race condition occurs when Cumulus Linux tries to derive MAC addresses.|
To work around this issue, use a static MAC address; specify a MAC address in the
|CM-31954||A security issue was discovered in the MariaDB database server.|
|CM-31942||After upgrading the Mellanox SN2410 switch, the FAN is set to full speed.||4.2.1|
|CM-31936||When you back up and restore a configuration using the conf-backup utility, the switch might hang when rebooted.||4.1.1-4.2.1|
|CM-31864||CVE-2020-14355: Multiple buffer overflow vulnerabilities were found in the QUIC image decoding process of the SPICE remote display system, before spice-0.14.2-1.|
Both the SPICE client (spice-gtk) and server are affected by these flaws. These flaws allow a malicious client or server to send specially crafted messages that, when processed by the QUIC image compression algorithm, result in a process crash or potential code execution.
|CM-31697||Multiple vulnerabilities have been discovered in the Xen hypervisor, which could result in denial of service, guest-to-host privilege escalation or information leaks. These include the following:CVE-2020-25595, CVE-2020-25596, CVE-2020-25597, CVE-2020-25599, CVE-2020-25600, CVE-2020-25601, CVE-2020-25602, CVE-2020-25603, CVE-2020-25604.|
Vulnerable: < 4.11.4+37-g3263f257ca-1
|CM-31627||On switches with the Spectrum ASIC, the IPv6 default route is present in the kernel but missing in hardware.||3.7.11-4.2.1|
|CM-31623||The next hop for static routes configured in a non-default VRF might be incorrectly flagged as inactive. Remove and reconfigure the static VRF route to recover from this condition.||4.2.1|
|CM-31618||A ping via a dual-connected bond fails, and the audio stream is not routed or encapsulated through the layer 3 VNI.||3.7.12-3.7.13, 4.0.0-4.2.1|
|CM-31565||Multicast traffic on a VPN is sent to remote VTEPs that are not part of the VPN and the remote VTEPs receive multicast traffic encapsulated in a VXLAN ID that doesn’t exist.|
To work around this issue, disable IGMP snooping on the switch.
|CM-31560||After a MAC address moves from one remote VTEP to another, the MAC address continues to point to the old VTEP IP address in hardware.||4.1.1-4.2.1|
|CM-31545||In an MLAG configuration with a layer 3 VNI, when you bounce the peer link, all layer 2 VNIs listed under the layer 3 VNI are duplicated.|
To work around this issue, restart FRR with the
|CM-31504||On the the Dell N3248-PXE switch, when you insert two PSUs at different times, the newly inserted PSU is detected as OK but the fan and temp sensors are ABSENT.|
To work around this issue, remove power to both PSUs at the same time, then reinsert power simultaneously.
|CM-31469||When you delete a layer 2 VNI and VLAN, the layer 3 VNI reports an incorrect layer 2 VNI number.|
To work around this issue, either restart FRR or delete the VNI interface first, then delete the VLAN/SVI.
|CM-31441||Leaked routes are sometimes missing from the destination VRF after a reboot.||4.2.0-4.2.1|
|CM-31412||On the Dell N3248PXE switch, RJ45 fixed copper ports that auto-negotiate with a 100M or 10M neighbor incorrectly negotiate a half-duplex link that generates errors. Half duplex modes are not supported on this platform.||3.7.12-3.7.13, 4.2.1|
|CM-31407||You cannot configure SNMPv3 trap-destinations in non-default VRFs with an authentication username that contains fewer than eight characters.||3.7.12-4.2.1|
|CM-31358||The Dell 100G-LR4 (Innolight) transceiver cannot link up due to a power budget exceeded error on the Mellanox SN4600C switch.||4.2.0-4.2.1|
|CM-31263||RX_DRP on a bond interface increases without any data traffic while the slave port does not increase.||3.7.12-4.2.1|
|CM-31238||IPv6 TCP or UDP connections (sourcing from an ephemeral port in the range 34048 to 35071) are not forwarded if the switch has more than one layer 2 VNI defined. The traffic might be locally switched on the bridge and dropped.|
To work around this issue, disable ARP/ND suppression to remove the internal ACL rule that affects the ports.
|CM-31231||On the Dell N3048EP switch, the module information from SFP ports is not displayed in the |
To work around this issue, use the
|CM-31222||Tenant VRF BGP peers appear in the EVPN RMAC and nexthop tables, which causes the kernel RMAC to point at invalid IP address.||3.7.12-4.2.1|
|CM-31150||On the Mellanox SN2410 switch, you see |
To work around this issue, restart
|CM-31125||The MLAG bonds on a secondary switch do not change to a unique MAC address on the peerlink. As a result, a backup double failure can occur where both peers go down.||4.2.0-4.2.1|
|CM-31120||In a traditional bridge configuration with ||3.7.10-4.2.1|
|CM-31107||When you boot Cumulus VX 4.2 for the first time, ZTP does not execute because it thinks that the |
To work around this issue, boot the switch, manually change the password, then run
|CM-31073||When you set the |
To work around this issue, when you create a new virtual interface, set
|CM-31028||Ingress SPAN/ERSPAN does not mirror packets when the next hop is EVPN encapsulated.||3.7.7-3.7.13, 4.0.0-4.2.1|
|CM-30916||On the Mellanox SN4700 switch, you might see Bad signal integrity issues on 200G and 400G ports.||4.2.1|
|CM-30832||The Mellanox SN2700 and SN2410 switch intermittently reports PSU fan state changes with ||3.7.11-3.7.14, 4.1.1-4.2.1|
|CM-30555||If you have an existing community list of any type, redefining the same sequence number results in the entire community list being deleted.|
To work around this issue, delete the community list sequence before trying to adjust it.
|CM-30514||In OVSDB high availability mode, deleting > 200 VLAN bindings might cause ||3.7.12-3.7.13, 4.0.0-4.2.1|
|CM-30485||When you run ||4.2.0-4.2.1|
|CM-30361||On Mellanox switches with the Spectrum-2 switch, the lpm-balanced forwarding profile does not work.||4.1.1-4.2.1|
|CM-30247||dot1qVlanIndex in the dot1qVlanStaticTable of the SNMP Q-BRIDGE-MIB does not use VLAN ID and does not comply with RFC 4363.||4.1.1-4.2.1|
|CM-30231||When the dynamic or static flag on a bridge fdb (MAC) entry is changed to the opposite state, the new flag is not set appropriately in hardware. This can allow a static fdb entry to be unexpectedly learned dynamically on a different interface, or can prevent a dynamic entry from being updated or learned elsewhere.|
This condition can occur during a manual replacement of a local MAC address or when EVPN updates a dynamic MAC address to add or remove the Sticky Mac flag. Either situation results in the MAC address keeping the original flag in hardware.
To work around this issue, delete or withdraw the fdb entry, then add the static MAC address directly. For example:
bridge fdb del 50:6b:4b:ee:ee:ee dev swp31 vlan 24 master
If you are unable to delete an EVPN-learned remote MAC address, you can replace the dynamic MAC address with a local static one, then delete the static MAC address. For example:
bridge fdb replace 50:6b:4b:ee:ee:ee dev swp31 vlan 24 master static
|CM-30230||If a remote EVPN Sticky MAC [Static MAC address] is unexpectedly learned dynamically on a local interface, the selected entries in zebra and BGP are in an inconsistent state.|
zebra increments the local MAC mobility sequence number and considers the MAC address to be local, but BGP maintains the remote Sticky MAC as the best path selected. This results in zebra installing the local MAC address and BGP not updating the route for the MAC address.
|CM-30194||After you enable ROCE with the ||4.1.1-4.2.1|
To work around this issue, you must update the file from https://www.ietf.org/timezones/data/leap-seconds.list or upgrade the
|CM-30159||After you delete a bond, the deleted bond members have the deleted bond MAC address instead of their original MAC address, which might result in traffic being discarded.|
To work around this issue, perform a full switch restart.
|CM-30103||On a Broadcom switch with the Trident2+ ASIC, ACL rules for VLANs are not applied after a reboot and the counters remain at zero.|
To work around this issue, either do not set
|CM-29838||CPU utilization may increase when clag-managed bond interfaces are operationally/LACP down but the physical carrier remains up on the bond member switchports. This condition occurs when clag bond redirection is enabled and bond members remain up while the parent bond does not negotiate LACP.This issue is resolved in Cumulus Linux 3.7.14.||3.7.9-3.7.13, 4.0.0-4.2.1|
|CM-29779||In LLDP, the |
All the information from
|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
If you flap the link with the
|CM-29520||On Mellanox switches, when the networking service and ||4.1.0-4.2.1|
|CM-29259||You might see the following ||3.7.12-4.2.1|
|CM-29148||On MLX switches that contain an OSPF IP unnumbered neighborship with a high scale of prefixes being learned, a link flap might cause the neighbor entry to not be programmed in hardware.||3.7.11-4.2.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.
|CM-29035||When you upgrade Cumulus Linux on the EdgeCore AS7726-32X or AS7326-56X switch, you might see firmware errors similar to the following:|
W: Possible missing firmware /lib/firmware/tigon/tg3_tso5.bin for module tg3
You can safely ignore these error messages.
|CM-28940||If you configure |
router bgp 1
If you add
Status codes: s suppressed, d damped, h history, * valid, > best, = multipath,
Status codes: s suppressed, d damped, h history, * valid, > best, = multipath,
To work around this issue, remove, then re-add the component prefix routes.
|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 188.8.131.52 –dst-ip 184.108.40.206 –ttl 64
|CM-25986||On the Mellanox Spectrum-2 switch, the time required to establish a link (from the time a link is set to |
To work around this issue, wait up to 15 seconds on 40G interfaces and 30 seconds on 100G interfaces for the link to establish.
|CM-23021||When you run the ||3.7.1-4.2.1|
|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.13, 4.0.0-4.2.1|