Overview
These release notes support Cumulus Linux 2.5.10 and describe currently available features and known issues.
Extended Support Release
This version of Cumulus Linux is an Extended Support Release (ESR). Cumulus Linux 2.5 ESR started with Cumulus Linux 2.5.6 and all future releases in the 2.5 product family will all be ESR releases. To learn about ESR, please read this article.
Stay up to Date
- Please sign in and click Follow above so you can receive a notification when we update these release notes.
- Subscribe to our product bulletin mailing list to receive important announcements and updates about issues that arise in our products.
- Subscribe to our security announcement mailing list to receive alerts whenever we update our software for security issues.
{{table_of_contents}}
Licensing
Cumulus Linux is licensed on a per-instance basis. Each network system is fully operational, enabling any capability to be utilized on the switch with the exception of forwarding on switch panel ports. Only eth0 and console ports are activated on an un-licensed instance of Cumulus Linux. Enabling front panel ports requires a license.
You should have received a license key from Cumulus Networks or an authorized reseller. To install the license, read the Cumulus Linux quick start guide.
Installing Version 2.5.10
If you are upgrading from version 2.5.0 through 2.5.9, use apt-get
to update the software.
- Run
apt-get update
. - Run
apt-get dist-upgrade
. - Reboot the switch.
Caution: While this method doesn't overwrite the target image slot, it may require additional disk space in the slot. This is especially true for PowerPC-based platforms, which use overlayfs.
New Install or Upgrading from Versions Older than 2.5.0
If you are upgrading from a version older than 2.5.0, or installing Cumulus Linux for the first time, choose one of the following methods. They are ordered from the most recommended method to least recommended.
-
Download Cumulus Linux 2.5.10 (for x86, ARM or PowerPC) from the Downloads page of the Cumulus Networks website, then use
cl-img-install
to install the software.Note: Do not use
cl-img-install -u
to upgrade Cumulus Linux. This feature has been deprecated.Warning: This method overwrites the target image slot, so if you want to preserve your configuration, you should create a persistent configuration on
/mnt/persist
. -
Download Cumulus Linux 2.5.10 (for x86, ARM or PowerPC) from the Downloads page of the Cumulus Networks website, then use ONIE to perform a complete install, following the instructions in the quick start guide.
Warning: This method is destructive; any configuration files on the switch will not be saved, so please copy them to a different server before upgrading via ONIE.
Important! After you install, run apt-get update
, then apt-get dist-upgrade
on your switch to make sure you update Cumulus Linux to include any important or other package updates.
SNMP Not Supported in Quagga
There is no SNMP support for Quagga in this release (see RN 88 below). Due to this circumstance, you must remove all references to smux
in each of the following configuration files. You must also remove these references before upgrading Cumulus Linux using apt-get
. If the smux
entries are present in the configuration files, the daemons in the 2.5 packaged version of Quagga will not start.
cd /etc/quagga
grep smux *
- Delete all lines in the config files containing the smux keyword.
The references to smux
that must be removed are:
- In
bgpd.conf
, remove this line:smux peer 1.3.6.1.4.1.3317.1.2.2 quagga_bgpd
- In
ospf6d.conf
, remove this line:smux peer 1.3.6.1.4.1.3317.1.2.6 quagga_ospf6d
- In
ospfd.conf
, remove this line:smux peer 1.3.6.1.4.1.3317.1.2.5 quagga_ospfd
- In
zebra.conf
, remove this line:smux peer 1.3.6.1.4.1.3317.1.2.1 quagga_zebra
Perl, Python and BDB Modules
Any Perl scripts that use the DB_File
module or Python scripts that use the bsddb
module won't run under Cumulus Linux 2.5.10.
What's New in Cumulus Linux 2.5.10
Cumulus Linux 2.5.10 includes a number of bug fixes only. See the list of fixed issues below.
Experimental Features
The following experimental features are included in Cumulus Linux 2.5.10:
- BGP add-path RX
- Quagga automation optimization (applies configuration modifications only)
- Redistribute neighbor
Deprecated Features
cl-img-install -u
: This experimental feature was introduced in Cumulus Linux 2.5.0 to assist with upgrading Cumulus Linux. Based on customer feedback, we deprecated this feature; we plan to introduce upgrade enhancements in future releases.cl-ns-mgmt
: This experimental feature was introduced in Cumulus Linux 2.1.1 to help users separate their management network from the in-band network. You should use management VRF instead.
Documentation
You can read the technical documentation here.
Issues Fixed in Cumulus Linux 2.5.10
The following is a list of issues fixed in Cumulus Linux 2.5.10 from earlier versions of Cumulus Linux.
Known Issues in Cumulus Linux 2.5.10
Issues are categorized for easy review. Some issues are fixed but will be available in a later release.
Release Note ID | Summary | Description |
![]() RN-4 (FR-53) |
ifup/ifdown must be used for interfaces with IPv6 addresses defined in /etc/network/interfaces , otherwise the global IPv6 address will not be restored |
Two scenarios are shown below; one with ifup/ifdown, the other with ifconfig down. With ifup/ifdown: swp1 Link encap:Ethernet HWaddr 44:38:39:00:01:81 inet addr:11.0.0.2 Bcast:11.0.0.255 Mask:255.255.255.0 inet6 addr: fe80::4638:39ff:fe00:181/64 Scope:Link inet6 addr: fec0:1000:1000:1000::2/10 Scope:Site UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:4231 errors:0 dropped:0 overruns:0 frame:0 TX packets:4342 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:500 RX bytes:412115 (402.4 KiB) TX bytes:425688 (415.7 KiB) cumulus@switch$ sudo ifdown swp1 cumulus@switch$ sudo ifconfig swp1 swp1 Link encap:Ethernet HWaddr 44:38:39:00:01:81 BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:4248 errors:0 dropped:0 overruns:0 frame:0 TX packets:4356 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:500 RX bytes:413990 (404.2 KiB) TX bytes:427074 (417.0 KiB) cumulus@switch$ sudo ifconfig swp1 swp1 Link encap:Ethernet HWaddr 44:38:39:00:01:81 BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:4248 errors:0 dropped:0 overruns:0 frame:0 TX packets:4356 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:500 RX bytes:413990 (404.2 KiB) TX bytes:427074 (417.0 KiB) cumulus@switch$ sudo ifup swp1 ADDRCONF(NETDEV_UP): swp1: link is not ready cumulus@switch$ sudo ifconfig swp1ADDRCONF(NETDEV_CHANGE): swp1: / link becomes ready swp1 Link encap:Ethernet HWaddr 44:38:39:00:01:81 inet addr:11.0.0.2 Bcast:11.0.0.255 Mask:255.255.255.0 inet6 addr: fe80::4638:39ff:fe00:181/64 Scope:Link inet6 addr: fec0:1000:1000:1000::2/10 Scope:Site UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:4250 errors:0 dropped:0 overruns:0 frame:0 TX packets:4362 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:500 RX bytes:414178 (404.4 KiB) TX bytes:427610 (417.5 KiB) cumulus@switch$ With ifconfig down: cumulus@switch:~$ sudo ifconfig swp1 swp1 Link encap:Ethernet HWaddr 44:38:39:00:01:81 inet addr:11.0.0.2 Bcast:11.0.0.255 Mask:255.255.255.0 inet6 addr: fe80::4638:39ff:fe00:181/64 Scope:Link inet6 addr: fec0:1000:1000:1000::2/10 Scope:Site UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:98 errors:0 dropped:0 overruns:0 frame:0 TX packets:111 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:500 RX bytes:13310 (12.9 KiB) TX bytes:12786 (12.4 KiB) cumulus@switch$ sudo ifconfig swp1 down cumulus@switch$ sudo ifconfig swp1 swp1 Link encap:Ethernet HWaddr 44:38:39:00:01:81 inet addr:11.0.0.2 Bcast:11.0.0.255 Mask:255.255.255.0 BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:126 errors:0 dropped:0 overruns:0 frame:0 TX packets:138 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:500 RX bytes:16998 (16.5 KiB) TX bytes:15998 (15.6 KiB) cumulus@switch$ sudo ifconfig swp1 up ADDRCONF(NETDEV_UP): swp1: link is not ready cumulus@switch$ sudo ifconfig swp1ADDRCONF(NETDEV_CHANGE): swp1: link becomes ready swp1 Link encap:Ethernet HWaddr 44:38:39:00:01:81 inet addr:11.0.0.2 Bcast:11.0.0.255 Mask:255.255.255.0 inet6 addr: fe80::4638:39ff:fe00:181/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:130 errors:0 dropped:0 overruns:0 frame:0 TX packets:149 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:500 RX bytes:17474 (17.0 KiB) TX bytes:17154 (16.7 KiB) |
![]() RN-10 (CM-528) |
cl-phy-update doesn't support aggregated ports |
Ports can be aggregated into a larger interface in Cumulus Linux. Unfortunately support for aggregated ports is not yet supported when running cl-phy-update. |
![]() RN-52 (CM-997, CM-1013) |
Parameters like the router ID and DR priority cannot be changed while OSPFv2/v3 is running | Router ID and DR priority can only be changed by shutting down OSPFv2/v3, changing the ID, and restarting the OSPF process. A change to the DR priority may not properly be reflected in the LSAs that are still aging out. |
![]() RN-56 (CM-343) |
IPv4/IPv6 forwarding disabled mode not recognized |
If either of the following is configured: net.ipv4.ip_forward == 0 or: net.ipv6.conf.all.forwarding == 0 The hardware still forwards packets if there is a neighbor table entry pointing to the destination. |
![]() RN-58 (CM-747) |
IPv6 route is installed and active in the routing table when the associated interface is down | If an IPv6 address is assigned to a "down" interface, the associated route is still installed into the route table. Also, the type of IPv6 address doesn't matter. Link local, site local, and global all exhibit the same problem. If the interface is bounced up and down, then the routes are no longer in the route table. |
![]() RN-61 (CM-1004) |
BGP4 notifications missing for several conditions |
In certain conditions, Quagga's |
![]() RN-64 (CM-1153) |
Configuring route-reflector-client requires specific order | In configuring a route to be a route reflector client, the Quagga configuration must be specified in a specific order; otherwise, the router will not be a route reflector client. The "neighbor <IPv4/IPV6> route-reflector-client" command must be done after the "neighbor <IPV4/IPV6> Activate" command; otherwise, the route-reflector-client command is ignored. Sample configuration: router bgp 65000 bgp router-id 0.0.0.4 bgp log-neighbor-changes no bgp default ipv4-unicast bgp cluster-id 0.0.0.4 bgp bestpath as-path multipath-relax redistribute connected neighbor 14.0.0.1 remote-as 65000 neighbor 14.0.0.1 route-reflector-client neighbor 14.0.0.1 activate neighbor 14.0.0.1 next-hop-self neighbor 14.0.0.9 remote-as 65000 neighbor 14.0.0.9 activate neighbor 14.0.0.9 next-hop-self neighbor 2001:ded:beef::1 remote-as 65000 neighbor 2001:ded:beef:2::1 remote-as 65000 maximum-paths 4 maximum-paths ibgp 4 ! address-family ipv6 redistribute connected neighbor 2001:ded:beef::1 activate neighbor 2001:ded:beef::1 next-hop-self neighbor 2001:ded:beef:2::1 route-reflector-client neighbor 2001:ded:beef:2::1 activate neighbor 2001:ded:beef:2::1 next-hop-self maximum-paths 4 maximum-paths ibgp 4 exit-address-family At runtime: cumulus@switch:$ show ip bgp neighbor 14.0.0.1 BGP neighbor is 14.0.0.1, remote AS 65000, local AS 65000, internal link BGP version 4, remote router ID 0.0.0.6 BGP state = Established, up for 00:23:49 Last read 23:31:36, hold time is 180, keepalive interval is 60 seconds Neighbor capabilities: 4 Byte AS: advertised and received Route refresh: advertised and received(old & new) Address family IPv4 Unicast: advertised and received Message statistics: Inq depth is 0 Outq depth is 0 Sent Rcvd Opens: 2 0 Notifications: 0 0 Updates: 1 1 Keepalives: 25 24 Route Refresh: 0 0 Capability: 0 0 Total: 28 25 Minimum time between advertisement runs is 5 seconds For address family: IPv4 Unicast >>>>>>>>>>>>>>>>>>>>>> ROUTE REFLECTOR CLIENT NOT DISPLAYED NEXT_HOP is always this router Community attribute sent to this neighbor(both) 6 accepted prefixes Connections established 1; dropped 0 Last reset never Local host: 14.0.0.2, Local port: 179 Foreign host: 14.0.0.1, Foreign port: 40290 Nexthop: 14.0.0.2 Nexthop global: 2001:ded:beef::2 Nexthop local: fe80::202:ff:fe00:4 BGP connection: non shared network Read thread: on Write thread: off cumulus@switch:$ Workaround: Define in following order address-family ipv4 unicast neighbor 14.0.0.9 activate neighbor 14.0.0.9 next-hop-self neighbor 14.0.0.9 route-reflector-client >>> Must be after Activate exit-address-family neighbor 2001:ded:beef:2::1 remote-as 65000 address-family ipv6 unicast redistribute connected maximum-paths 4 maximum-paths ibgp 4 neighbor 2001:ded:beef:2::1 activate neighbor 2001:ded:beef:2::1 next-hop-self neighbor 2001:ded:beef:2::1 route-reflector-client >>> Must be after activate exit-address-family Runtime status after change: cumulus@switch:$ show ip bgp neighbors 14.0.0.9 BGP neighbor is 14.0.0.9, remote AS 65000, local AS 65000, internal link BGP version 4, remote router ID 0.0.0.7 BGP state = Established, up for 00:13:59 Last read 22:35:13, hold time is 180, keepalive interval is 60 seconds Neighbor capabilities: 4 Byte AS: advertised and received Route refresh: advertised and received(old & new) Address family IPv4 Unicast: advertised and received Message statistics: Inq depth is 0 Outq depth is 0 Sent Rcvd Opens: 1 1 Notifications: 0 0 Updates: 2 1 Keepalives: 15 14 Route Refresh: 0 0 Capability: 0 0 Total: 18 16 Minimum time between advertisement runs is 5 seconds For address family: IPv4 Unicast Route-Reflector Client >>>>>>>>>> PLEASE NOTE ME NEXT_HOP is always this router Community attribute sent to this neighbor(both) 6 accepted prefixes Connections established 1; dropped 0 Last reset never Local host: 14.0.0.10, Local port: 38813 Foreign host: 14.0.0.9, Foreign port: 179 Nexthop: 14.0.0.10 Nexthop global: 2001:ded:beef:2::2 Nexthop local: fe80::202:ff:fe00:6 BGP connection: non shared network Read thread: on Write thread: off cumulus@switch:$ |
![]() RN-70 (CM-1166) |
ACL: Bridge traffic that matches a LOG ACTION rule is not logged in syslog | For example, a bridge with switch ports swp1, swp2, swp3 as bridge members is configured. ACL rules to LOG and DROP for icmp traffic are configured. Ping requests are sent from host1 on swp1 to host3 on swp3, and the following was observed: * Counters for both LOG and DROP ACL rules are incrementing properly, but the packets are not showing up on /var/log/syslog. * Packets that are copied to the CPU from hardware for the LOG rule are dropped due to the check in kernel to disable software bridging for hardware bridged packets. |
![]() RN-77 (CM-265) |
New routes/ECMPs can evict existing/installed | Cumulus Linux syncs routes between the kernel and the switching silicon. If the required resource pools in hardware fill up, new kernel routes can cause existing routes to move from being fully allocated to being partially allocated. In order to avoid this, routes in the hardware should be monitored and kept below the ASIC limits. For example, on systems with Trident+ chips, the limits are as follows: routes: 16384 <<<< if all routes are ipv4 long mask routes 256 <<<< i.e., routes with a mask longer than the route mask limit route mask limit 64 host_routes: 8192 ecmp_nhs: 4044 ecmp_nhs_per_route: 52That translates to about 77 routes with ECMP NHs, if every route has the maximum ECMP NHs. Monitoring this in Cumulus Linux is performed via the cl-resource-query command: cumulus@switch:~$ sudo cl-resource-query hosts : 3 all routes : 29 IP4 routes : 17 IP6 routes : 12 nexthops : 3 ecmp_groups : 0 ecmp_nexthops : 0 mac entries : 0 / 131072 bpdu entries : 500 / 512The resource to monitor is the ecmp_nexthops. If this count is close to 4044, new ECMPs may evict existing routes. |
![]() RN-88 (CM-1200) |
SNMP support for Quagga is NOT provided in Cumulus Linux |
Cumulus Linux does not provide SNMP support for Quagga. You can get this information via Nagios. However, it's possible to get it via SNMP by:
|
![]() RN-120 (CM-477) |
ethtool LED blinking does not work with switch ports | Linux uses ethtool -p to identify the physical port backing an interface, or to identify the switch itself. Usually this identification is by blinking the port LED until ethtool -p is stopped. This feature does not apply to switch ports (swpX) in Cumulus Linux. |
![]() RN-121 (CM-2123) |
PTMD: When a physical interface is in a PTM FAIL state, its subinterface still exchanges information | Issue: When PTMD is incorrectly in a failure state and the Zebra interface is enabled, PIF BGP sessions are not establishing the route, but the subinterface on top of it does establish routes. If the subinterface is configured on the physical interface and the physical interface is incorrectly marked as being in a PTM FAIL state, routes on the physical interface are not processed in Quagga, but the subinterface is working. Steps to reproduce: cumulus@switch:$ sudo vtysh -c 'show int swp8' Interface swp8 is up, line protocol is up PTM status: fail index 10 metric 1 mtu 1500 flags: <UP,BROADCAST,RUNNING,MULTICAST> HWaddr: 44:38:39:00:03:88 inet 12.0.0.225/30 broadcast 12.0.0.227 inet6 2001:cafe:0:38::1/64 inet6 fe80::4638:39ff:fe00:388/64 cumulus@switch:$ ip addr show | grep swp8 10: swp8: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 500 inet 12.0.0.225/30 brd 12.0.0.227 scope global swp8 104: swp8.2049@swp8: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP inet 12.0.0.229/30 brd 12.0.0.231 scope global swp8.2049 105: swp8.2050@swp8: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP inet 12.0.0.233/30 brd 12.0.0.235 scope global swp8.2050 106: swp8.2051@swp8: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP inet 12.0.0.237/30 brd 12.0.0.239 scope global swp8.2051 107: swp8.2052@swp8: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP inet 12.0.0.241/30 brd 12.0.0.243 scope global swp8.2052 108: swp8.2053@swp8: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP inet 12.0.0.245/30 brd 12.0.0.247 scope global swp8.2053 109: swp8.2054@swp8: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP inet 12.0.0.249/30 brd 12.0.0.251 scope global swp8.2054 110: swp8.2055@swp8: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP inet 12.0.0.253/30 brd 12.0.0.255 scope global swp8.2055 cumulus@switch:$ bgp sessions: 12.0.0.226 ,4 ,64057 , 958 , 1036 , 0 , 0 , 0 ,15:55:42, 0, 10472 12.0.0.230 ,4 ,64058 , 958 , 1016 , 0 , 0 , 0 ,15:55:46, 187, 10285 12.0.0.234 ,4 ,64059 , 958 , 1049 , 0 , 0 , 0 ,15:55:40, 187, 10285 12.0.0.238 ,4 ,64060 , 958 , 1039 , 0 , 0 , 0 ,15:55:45, 187, 10285 12.0.0.242 ,4 ,64061 , 958 , 1014 , 0 , 0 , 0 ,15:55:46, 187, 10285 12.0.0.246 ,4 ,64062 , 958 , 1016 , 0 , 0 , 0 ,15:55:46, 187, 10285 12.0.0.250 ,4 ,64063 , 958 , 1029 , 0 , 0 , 0 ,15:55:43, 187, 10285 12.0.0.254 ,4 ,64064 , 958 , 1036 , 0 , 0 , 0 ,15:55:44, 187, 10285 |
![]() RN-125 (CM-1576) |
Network LSA with an old router ID isn't flushed out by the originator | When the router ID is changed, the router should remove the previous network LSA (link-state advertisement) that it generated based on the IP address on the interface in the Network LSA. Cumulus Networks doesn't remove this LSA, so it will be naturally aged out. |
![]() RN-132 (CM-2272) |
You must run "apt-get update" before running any apt-get commands or after changing sources.list |
Before running any apt-get commands or after changing the source.list file in /etc/apt, you need to run apt-get update. |
![]() RN-133 (CM-2273) |
Interface names in Cumulus Linux cannot exceed 16 characters |
Device names, including interface names, in Cumulus Linux cannot exceed 16 characters – including the terminator. Cumulus Linux truncates longer interface names. To avoid this issue, do not assign long names to your interfaces. The following example configuration reproduces this issue: cumulus@switch:/sys/class/net$ grep 'iface br' /etc/network/interfaces iface br2-pubmgmt inet static iface br3-prvmgmt inet manual iface br400-quarantine inet manual iface br401-peering-1k5 inet manual iface br402-peering-9k inet manual iface br500-pi-exa inet manual iface br501-akamai-exa inet manual iface br502-exa-internetfactory inet manual cumulus@switch:/sys/class/net$ brctl show | grep br bridge name bridge id STP enabled interfaces br2-pubmgmt 8000.089e01cebe37 no bond0.2 br3-prvmgmt 8000.089e01cebe3a no bond0.3 br400-quarantin 8000.089e01cebe37 no bond0.400 br401-peering-1 8000.089e01cebe3a no bond0.401 <<< |
![]() RN-134 (CM-2303) |
Installing Chef under Cumulus Linux |
The Cumulus Linux 2.2 repository contains two versions of Chef, the automation tool: 11.6.2 (the current version) and 10.30.4. To install the latest version, connect to the switch and use cumulus@switch:~$ sudo apt-get install chef To install 10.30.4, connect to the switch and use apt-get: cumulus@switch:~$ sudo apt-get install chef=10.30.4-0.debian.7.3 |
![]() RN-163 (CM-2499) |
VXLAN: ovsdb-server cannot select loopback interface as source IP address, causing TOR registration to the controller to fail |
In a VXLAN using VMware NSX, ovsdb-server cannot select the loopback interface as the source IP address. This causes TOR registration to the controller to fail. To work around this issue, run: cl-bgp redistribute add connected |
![]() RN-179 (CM-3410) |
10GTek 10G SR cables exhibit high rate of errors on Penguin Arctica 4804X switch |
Some PHY-less Penguin Arctica 4804X platforms using 10GTek 10G MM SR cables exhibit high rates of errors and low bandwidth one direction. |
![]() RN-183 (CM-3141) |
Link not coming up (NO-CARRIER) on Penguin Arctica 4804xp with CAB-10GSFP-P9M 10Gtek 9 meter cable |
The link does not come up on a Penguin Arctica 4804xp 720G PHY-less switch with 10Gtek 9 meter cables (CAB-10GSFP-P9M). You can determine this by running: cumulus@switch:~$ ip link show swp15 17: swp15: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN mode DEFAULT qlen 500 link/ether 44:38:39:00:70:a1 brd ff:ff:ff:ff:ff:ff Cumulus Linux supports copper passive cables no longer than 7m. |
![]() RN-192 (CM-3340) |
PTM may crash when a large topology file has a syntax error |
If there is a syntax error in a large (~ 4000 entries) |
![]() RN-196 (CM-2499) |
For a VXLAN in NSX, ovsdb-server cannot select a loopback interface as the SRC IP |
As a result, the TOR registration to the controller fails. To work around this issue, run: cl-bgp redistribute add connected |
![]() RN-198 (CM-3290) |
Port LEDs behave differently on different switch models |
It's been observed that port LEDs behave differently depending upon the make and model of the switch. For example:
Cumulus Networks is currently working to fix this issue. |
![]() RN-199 (CM-2624) |
When a Quagga route-map is modified, the switch could use the partial map before edits are completed |
Cumulus Linux triggers a Cumulus Networks is working to fix this issue. |
![]() RN-217 (CM-4207) |
LNV: Network restart removes vxsnd anycast IP address from loopback interface |
Given the following conditions:
When you restart networking (with service networking restart), the anycast IP address gets removed from the loopback interface. To prevent this issue from occurring, you should specify an anycast IP address for the loopback interface in both |
![]() RN-218 (CM-4432) |
On Quanta T5048-LY8 and T3048-LY9 switches, "Operation timed out" error occurs while removing and reinserting QSFP module | The QSPFx2 module cannot be removed while the switch is powered on, as it is not hot-swappable. |
![]() RN-221 (CM-4501) |
BGP graceful restart, including helper mode, not fully supported | If you encounter issues with this, please submit a support request and include the output from cl-support with your ticket. |
![]() RN-227 (CM-3388) |
BGP dynamic capability is not supported | BGP peer sessions with dynamic capability are not supported under any version of Cumulus Linux at this time. |
![]() RN-228 (CM-4384) |
ifupdown2 doesn't bring up loopback interface (lo) by default |
One effect is that since |
![]() RN-229 (CM-4433) |
When a bond subinterface that is part of a traditional bridge is brought down, it flaps that bridge | This issue has been encountered in environments where both VLAN-aware and traditional bridges are in use, where a traditional bridge has a subinterface of a bond that is present as a normal interface in a VLAN-aware bridge. |
![]() RN-230 (CM-4327) |
bond-min-links defaults to 0, which causes the bond carrier to be incorrectly up when no slaves are active |
Even though |
![]() RN-246 (CM-5261) |
10GTek QSFP-SR4 optical cable on QuantaMesh BMS T3048-LY9 switches exhibits low traffic rate |
For QuantaMesh BMS T3048-LY9 switches, the 10GTek QSFP-SR4 optical cable is not supported in Cumulus Linux 2.5.10. Use the JDSU JQP-04SWAA1 or comparable Multi-Mode QSFP+ cable instead. Cumulus Networks is working to support this transceiver in a future release. |
![]() RN-249 (CM-5073) |
x86 switch stuck in RC.Script failure during switchd init time |
Under rare and unusual conditions on various x86 Trident II platforms (such as the Penguin Computing Arctica 4806XP, MiimTimeOut:soc_miim_write, timeout (id=0x1da addr=0x1f data=0x8630) system_init: Device reset failed: Operation timed out PORT: Error: bcm ports not initialized Error: file /etc/bcm.d/rc.ports_0: line 42 (error code -1): script terminated ERROR loading rc script on unit 0 loading of rc script failed, aborting! This condition is extremely rare, and does not occur if the switch booted correctly and is operational. |
![]() RN-268 (CM-5296) |
bridge fdb add command IP address type options inconsistent with Debian |
The
|
![]() RN-270 (CM-973) |
inotify support |
|
![]() RN-273 (CM-6002) |
VXLAN BUM: When a next-hop port is elected as the forwarding port, multiple cables with the same next-hop cannot work with full ECMP capacity |
As a best practice for when multiple next-hops are going to the same switch, you should configure a bond with an uplink port. |
![]() RN-275 (CM-5794) |
BGP import-check fails for IPv6 route if static routes to null0 are used |
The path that Cumulus Linux originates should not be invalid since there is a matching route in the RIB. The import check works fine for IPv4 routes. |
![]() RN-279 (CM-6012) |
STP not supported on bonds in LACP bypass all-active mode |
Cumulus Linux does not support STP on bonds in LACP bypass all active mode. To avoid this issue, enable STP BPDU guard for all bonds in LACP bypass all-active mode. For information, read this document. |
![]() RN-281 (CM-5118) |
Default route not removed on ifup after removing gateway statement from eth0 configuration |
If you try to remove the default route from eth0 (either by commenting out or removing the gateway statement in the eth0 configuration), the route remains after running To work around this issue, first run |
![]() RN-282 (CM-4837) |
Dell S3048-ON has a limit of 24576 MAC address entries, instead of 32K |
Other 1G switches support 32K (32768) entries. This is a known issue that should be fixed in a future release of Cumulus Linux. |
![]() RN-287 (CM-6286) |
Inconsistent /etc/passwd file after upgrading from a Cumulus Linux version earlier than 2.5.3 |
If you upgraded from a Cumulus Linux version earlier than 2.5.3 using cumulus@switch:~ $ sudo lldpcli show neighbors ------------------------------------------------------------------------------- LLDP neighbors: 2015-06-08T20:11:34 [WARN/control] unable to connect to socket /var/run/lldpd.socket: Permission denied 2015-06-08T20:11:34 [WARN/lldpctl] not able to get the list of interfaces. Unable to connect to lldpd daemon ------------------------------------------------------------------------------- Note: If you upgrade using To work around this issue, after you overwrite the cumulus@switch:~ $ sudo chown _lldpd /usr/sbin/lldpcli cumulus@switch:~ $ cumulus@switch:~ $ sudo service lldpd restart [ ok ] Restarting LLDP daemon: lldpd. cumulus@switch:~ $ Another side effect of this issue is that the owner for the Quagga log file, cumulus@switch:~$ sudo chown quagga:quagga /var/log/quagga |
![]() RN-315 (CM-7318) |
Dell S4048-ON: Various power off commands render the switch unusable |
Issuing a
Issuing a This issue affects only Dell S4048-ON switches with BIOS version 3.21.0.2 or earlier. To determine the BIOS version of the switch, run: cumulus@switch:~$ sudo dmidecode -s system-version 3.21.0.2 This is a known issue, and Dell is issuing a fix soon. |
![]() RN-317 (CM-5913) |
When management VRF is enabled, the MLAG backup IP address does not work over front panel ports |
When you enable management VRF, the To work around this issue, use a backup IP address that is reachable over eth0. |
![]() RN-318 (CM-7574) |
In VXLAN tunnel processing, for certain traffic patterns when cut-though is enabled and link pause is asserted, you experience line errors like overflow and underflow |
With cut-though mode enabled and link pause is asserted, Cumulus Linux generates an TOVR and TUFL ERROR; certain error counters increment on given physical port. cumulus@switch:~$ sudo ethtool -S swp49 | grep Error HwIfInDot3LengthErrors: 0 HwIfInErrors: 0 HwIfInDot3FrameErrors: 0 SoftInErrors: 0 SoftInFrameErrors: 0 HwIfOutErrors: 35495749 SoftOutErrors: 0 cumulus@switch:~$ sudo ethtool -S swp50 | grep Error HwIfInDot3LengthErrors: 3038098 HwIfInErrors: 297595762 HwIfInDot3FrameErrors: 293710518 To work around this issue, disable link pause or disable cut-through in To disable link pause, comment out the cumulus@switch:~$ sudo nano /etc/cumulus/datapath/traffic.conf #link_pause.port_group_list = [port_group_0] #link_pause.port_group_0.port_set = swp45-swp54 #link_pause.port_group_0.rx_enable = true #link_pause.port_group_0.tx_enable = true To enable store and forward switching, set cumulus@switch:~$ sudo nano /etc/cumulus/datapath/traffic.conf cut_through_enable = false |
![]() RN-322 (CM-7387) |
Interfaces disabled using iproute2 become enabled after restarting Quagga |
By default, all interfaces have a "no shutdown" associated with them in Quagga. Thus, when you restart Quagga, it enables the interfaces. This is expected behavior in Quagga. There is no workaround at this time. |
![]() RN-324 (CM-7228) |
On Edge-Core AS4610-54P, the Power over Ethernet poectl service reports 5V difference in power consumption | The voltage reported by the poectl -i command and measured through a power meter connected to the device varies by 5V. The current and power readings are correct and no difference is seen for them. |
![]() RN-326 (CM-7030) |
Cumulus RMP/Hurricane2 CPU: ACL rule fails silently if it cannot be installed in hardware |
The Hurricane2 chipset used on Cumulus RMP switches does not support ACL rules that specify ICMP type or code. These rules are ignored and are not installed in hardware without providing any feedback to the user. Cumulus Networks is aware of this issue but there is no known workaround at this time. |
![]() RN-327 (CM-4290) |
Changing the route-map parameter of the redistribute command in OSPF and BGP doesn't affect the state of the resulting redistribution in those protocols |
To work around this issue, remove any old redistribute command configurations before adding a new one with or without route-map as a parameter. For example, if OSPF has a redistribute configuration such as
You would perform a similar sequence of commands for redistribution changes in BGP as well. |
![]() RN-331 (CM-7711) |
Do not use the reboot -f command except in extreme circumstances |
When performing a fast reboot (using the You should only use this command under abnormal circumstances, because it bypasses normal shutdown. |
![]() RN-333 (CM-5925) |
Edge-Core AS6701-32X switch fails to link to Intel XL710-QDA1 NIC through 40G Amphenol QSFP DAC |
Link may fail to come up between Edge-Core AS6701-32X switches and Intel Fortville XL710-based NICs when used with 40G DACs. To correct this issue, upgrade to the most recent Intel i40e NIC driver (greater than version 1.3.49) and firmware (greater than 5.02 0x80002281 0.0.0). The updated NIC drivers may be available through the Linux distribution installed on the server, or alternatively are available from Intel directly. |
![]() RN-334 (CM-7276) |
Full file system results in nonfunctioning switch |
Running out of disk space can render a switch non-functional if the file system becomes full. This issue particularly affects PowerPC switches with small disk drives (1GB of capacity or less), which include the following:
One action that can consume a lot of disk space is upgrading Cumulus Linux. Before you upgrade, you should determine how much free space is on your switch. Run cumulus@switch:~$ df -m Filesystem 1M-blocks Used Available Use% Mounted on dev 10 0 10 0% /dev /dev/sysroot1 96 96 0 100% /mnt/root-ro /dev/mmcblk0p3 1212 414 737 36% /mnt/root-rw overlayfs:root 1212 414 737 36% / tmpfs 10 1 10 1% /run tmpfs 10 0 10 0% /run/lock tmpfs 100 0 100 0% /tmp tmpfs 100 1 100 1% /var/tmp tmpfs 980 0 980 0% /run/shm initramfs 980 3 978 1% /mnt/initramfs /dev/persist 119 2 111 2% /mnt/persist If your hard disk has less than 200MB and you want to upgrade Cumulus Linux using |
![]() RN-337 (CM-7623) |
Adding IPv6 default route with src address on eth0 fails without adding delay |
Attempting to install an IPv6 default route on eth0 with a source address fails at reboot or when running The first execution of cumulus@switch:~$ sudo ifup -dv eth0 warning: eth0: post-up cmd '/sbin/ip route add default via 2001:620:5ca1:160::1 / src 2001:620:5ca1:160::45 dev eth0' failed (RTNETLINK answers: Invalid argument)<<<<<<<<<< Running There are two ways you can work around this issue.
|
![]() RN-338 (CM-7917) |
Purging existing addresses for an interface with multiple iface stanzas is not supported |
Cumulus Linux does not support the purging existing addresses on interfaces with multiple This behavior is documented in the Cumulus Linux user guide. |
![]() RN-341 (CM-5568) |
switchd and ptmd log file changes |
Starting with Cumulus Linux 2.5.4, the
|
![]() RN-351 (CM-7829) |
Installing LNV |
The LNV packages are not installed when you upgrade Cumulus Linux. You can get the latest version of LNV for this release of Cumulus Linux in one of two ways:
|
![]() RN-352 (CM-7444) |
Accessing DOM data for SFP used with a QSFP cage |
In Cumulus Linux 2.5.4 and earlier, if an SFP+ is plugged into a QSFP-to-SFP adapter (such as the Mellanox MAM1Q00A-QSA), then DOM data from SFP+ was not available. Starting with Cumulus Linux 2.5.5, DOM data for an SFP+ plugged into a QSFP-to-SFP adapter is now available, however, not by default. In order to see the DOM data using
|
![]() RN-353 (CM-7937) |
vxsnd and vxrd incompatibility between Cumulus Linux 2.5.4 and 2.5.5 and later |
Starting with Cumulus Linux 2.5.5, a change in the
To work around this issue, ensure you upgrade the |
![]() RN-355 (CM-7994) |
OSPFv2 Area ID being implicitly translated from Integer format to dotted decimal format |
While OSPF area ID configuration in Quagga allows for the value to be specified in either dotted decimal format, or as an integer, values specified as an integer will be converted into dotted decimal format when displayed, causing potential confusion for the operator. This issue does not impact OSPF functionality; only the display output. However, it is recommended that the OSPF area ID is specified in dotted decimal format for consistency. |
![]() RN-356 (CM-5745) |
Quagga reload broken with BGP unnumbered and external ASN keyword |
Deleting a line where a neighbor or peer is associated with a peer group, but the neighbor doesn't have a remote-as specified as part of the peer group specification, causes To work around this issue, delete the line that says |
![]() RN-357 (CM-7638) |
MGMT-VRF doesn't support DNS lookup in static case |
DNS is not handled correctly for static IP addresses by the current implementation of management VRF, as it is built around DHCP use cases. While static IP addresses will generally work, rules need to be set to point the entries in |
![]() RN-358 (CM-7106) |
cl-mgmtvrf: "ip route show" output is inconsistent with "ip route get" |
An incorrect result can be returned when using ip route get 10.1.2.2 from 10.0.0.1 |
![]() RN-359 (CM-6219) |
isc-dhcp-server service should be off by default |
The [FAIL] startpar: service(s) returned failure: isc-dhcp-server ... failed! This issue is harmless and has no functionality impact. |
![]() RN-361 (CM-8646) |
ifupdown2: ifreload -av doesn't restart clagd after initial failure; jdoo cannot monitor clagd |
If One result is that you cannot monitor
|
![]() RN-372 (CM-9360) |
Security Update for CVE-2015-7547: glibc getaddrinfo Stack-based Buffer Overflow Vulnerability |
For details on this issue and how to upgrade, read this article. |
![]() RN-402 (CM-9627) |
smond PSU warnings on Supermicro X3648S |
The Supermicro X3648S uses a different PSU (DPS-550) than the equivalent Penguin Arctica 4806XP switch (DPS-460). Cumulus Linux was written to work with the DPS-460, but the DPS-550 behaves differently. On the Penguin Arctica 4806XP, a PWM value is written to the DPS-460 fan, and the power supply fan remains at that setting. But on the Supermicro X3648S, when a PWM value is written to the DPS-550 fan, the power supply fan initially goes to the setting; however, after five seconds, it may revert back to its internal setting. As a result, you will see smond warning messages that the fan input RPM is lower than expected, which can be safely ignored. |
![]() RN-426 (CM-5970) |
isc-dhcp-relay must be restarted after flapping an interface or if logical interface is down |
There are two known issues regarding
To work around the issue, apply the following configuration to each interface specified in INTERFACES from post-up test -e /var/run/boot.done && service isc-dhcp-relay restart |
Comments