These release notes support Cumulus RMP 3.0.1 and describe currently available features and known issues.
Stay up to Date
- Please sign in and click Follow above so you can receive a notification when we update these release notes.
- Subscribe to our product bulletin mailing list to receive important announcements and updates about issues that arise in our products.
- Subscribe to our security announcement mailing list to receive alerts whenever we update our software for security issues.
What's New in Cumulus RMP 3.0.1
Cumulus RMP 3.0.1 includes bug fixes only.
Cumulus RMP 3.0.z is a significant departure from earlier releases. See the user guide for details on new behaviors and functionality.
- Disk image slots
/mnt/persist: For information and strategies on how to preserve your network configuration across software upgrades, read the Upgrading Cumulus RMP chapter.
cl-brctl. This utility was simply a symlink to
brctl, which is what you should use to configure bridges, VLANs and the like.
Installing Version 3.0.1
If you are upgrading from version 3.0.0, use
apt-get to update the software.
- Reboot the switch.
New Install or Upgrading from Versions Older than 3.0.0
If you are upgrading from a version older than 3.0.0, or installing Cumulus RMP for the first time, download the Cumulus RMP 3.0.1 installer from the Cumulus Networks website, then use ONIE to perform a complete install, following the instructions in the user guide.
Note: This method is destructive; any configuration files on the switch will not be saved, so please copy them to a different server before upgrading via ONIE.
Important! After you install, run
apt-get update, then
apt-get upgrade on your switch to make sure you update Cumulus RMP to include any important or other package updates.
You can read the technical documentation here.
Issues Fixed in Cumulus RMP 3.0.1
The following is a list of issues fixed in Cumulus RMP 3.0.1 from earlier versions of Cumulus RMP.
Known Issues in Cumulus RMP 3.0.1
Issues are categorized for easy review. Some issues are fixed but will be available in a later release.
|Release Note ID||Summary||Description|
|IPv4/IPv6 forwarding disabled mode not recognized||
If either of the following is configured:
net.ipv4.ip_forward == 0
net.ipv6.conf.all.forwarding == 0
The hardware still forwards packets if there is a neighbor table entry pointing to the destination.
|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.
|ethtool LED blinking does not work with switch ports||Linux uses
This feature does not apply to switch ports (swpX) in Cumulus RMP.
|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:
[email protected]:$ 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 22.214.171.124/30 broadcast 126.96.36.199 inet6 2001:cafe:0:38::1/64 inet6 fe80::4638:39ff:fe00:388/64 [email protected]:$ ip addr show | grep swp8 10: swp8: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 500 inet 188.8.131.52/30 brd 184.108.40.206 scope global swp8 104: [email protected]: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP inet 220.127.116.11/30 brd 18.104.22.168 scope global swp8.2049 105: [email protected]: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP inet 22.214.171.124/30 brd 126.96.36.199 scope global swp8.2050 106: [email protected]: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP inet 188.8.131.52/30 brd 184.108.40.206 scope global swp8.2051 107: [email protected]: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP inet 220.127.116.11/30 brd 18.104.22.168 scope global swp8.2052 108: [email protected]: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP inet 22.214.171.124/30 brd 126.96.36.199 scope global swp8.2053 109: [email protected]: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP inet 188.8.131.52/30 brd 184.108.40.206 scope global swp8.2054 110: [email protected]: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP inet 220.127.116.11/30 brd 18.104.22.168 scope global swp8.2055 [email protected]:$ bgp sessions: 22.214.171.124 ,4 ,64057 , 958 , 1036 , 0 , 0 , 0 ,15:55:42, 0, 10472 126.96.36.199 ,4 ,64058 , 958 , 1016 , 0 , 0 , 0 ,15:55:46, 187, 10285 188.8.131.52 ,4 ,64059 , 958 , 1049 , 0 , 0 , 0 ,15:55:40, 187, 10285 184.108.40.206 ,4 ,64060 , 958 , 1039 , 0 , 0 , 0 ,15:55:45, 187, 10285 220.127.116.11 ,4 ,64061 , 958 , 1014 , 0 , 0 , 0 ,15:55:46, 187, 10285 18.104.22.168 ,4 ,64062 , 958 , 1016 , 0 , 0 , 0 ,15:55:46, 187, 10285 22.214.171.124 ,4 ,64063 , 958 , 1029 , 0 , 0 , 0 ,15:55:43, 187, 10285 126.96.36.199 ,4 ,64064 , 958 , 1036 , 0 , 0 , 0 ,15:55:44, 187, 10285
|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.
|Interface names in Cumulus RMP cannot exceed 15 characters||
Device names, including interface names, in Cumulus RMP cannot exceed 16 characters – including the terminator. Cumulus RMP truncates longer interface names.
To avoid this issue, do not assign long names to your interfaces.
The following example configuration reproduces this issue:
[email protected]:/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 [email protected]:/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 <<<
|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.|
|Default route not removed on
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
|While upgrading Cumulus RMP, a prompt to configure grub-pc appears||
While upgrading to the latest version of Cumulus RMP from version 2.5.5 or earlier, a prompt appears, asking you to choose onto which partitions to install the GRUB boot loader.
... 1. /dev/mmcblk0 (3783 MB; ???) 3. /dev/dm-2 (1610 MB; CUMULUS-SYSROOT1) 2. - /dev/mmcblk0p3 (268 MB; /boot) 4. none of the above (Enter the items you want to select, separated by spaces.) GRUB install devices: ...
This prompt should not appear, and the issue will be fixed in a future release.
In the meantime, to work around this issue, choose option 1, /dev/mmcblk0 and continue the upgrade.
|default.target is set to graphical.target||
The default.target for systemd is mistakenly set to graphical.target in this release, instead of multi-user.target. You may see this message in the journal or syslog at system boot:
systemd: Cannot add dependency job for unit display-manager.service, ignoring: Unit display-manager.service failed to load: No such file or directory.
You should ignore this message, as the correct systemd state is reached, since the
This issue will be fixed in a future release of Cumulus RMP.
|ifupdown2: IP address scope is not working; all addresses considered global||
ifupdown2 does not honor the configured IP address scope setting in /etc/network/interfaces, and it does not report an error. Consider this example configuration:
auto swp2 iface swp2 address 188.8.131.52/30 address 3101:21:20::31/80 scope link
When you run ifreload -a on this configuration, ifupdown2 considers all IP addresses as global.
[email protected]:~$ ip addr show swp2 5: swp2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000 link/ether 74:e6:e2:f5:62:82 brd ff:ff:ff:ff:ff:ff inet 184.108.40.206/30 scope global swp2 valid_lft forever preferred_lft forever inet6 3101:21:20::31/80 scope global valid_lft forever preferred_lft forever inet6 fe80::76e6:e2ff:fef5:6282/64 scope link valid_lft forever preferred_lft forever
To work around this issue, configure the IP address scope using post-up ip address add <address> dev <interface> scope <scope>. In continuing with the previous example:
auto swp6 iface swp6 post-up ip address add 220.127.116.11/32 dev swp6 scope site
Now, when you run ifreload -a on this configuration, it has the correct scope:
[email protected]:~$ ip addr show swp6 9: swp6: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000 link/ether 74:e6:e2:f5:62:86 brd ff:ff:ff:ff:ff:ff inet 18.104.22.168/32 scope site swp6 valid_lft forever preferred_lft forever inet6 fe80::76e6:e2ff:fef5:6286/64 scope link valid_lft forever preferred_lft forever
|When the sx_sdk service is restarted manually or during a package upgrade, switchd receives "Invalid Handle" errors||
2016-05-20T20:05:15.144736+00:00 mlx-2700-01 switchd: hal_mlx.c:4620 [SX_API_INTERNAL ]: Invalid handle: handle is not valid. 2016-05-20T20:05:15.145099+00:00 mlx-2700-01 switchd: hal_mlx_port.c:1789 ERR port_pfc_stats_get failed for lid 0x13c00 prio 2: Invalid Handle 2016-05-20T20:05:15.145460+00:00 mlx-2700-01 switchd: hal_mlx.c:4620 [SX_API_INTERNAL ]: Invalid handle: handle is not valid. 2016-05-20T20:05:15.145847+00:00 mlx-2700-01 switchd: hal_mlx_port.c:1789 ERR port_pfc_stats_get failed for lid 0x13c00 prio 3: Invalid Handle
These error messages are being investigated, but in the meantime, you should restart
|Kernel source not added to Cumulus Networks repository||
Kernel source (
You can retrieve these packages manually with
[email protected]:~$ sudo apt-get install linux-source-4.1
The archive file is stored at
|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
|The ZTP daemon shuts itself down after 5 minutes of inactivity||
The zero touch provisioning (ZTP) daemon
This can affect deployments where a switch might be powered up in a remote data center for weeks without ever being configured. In such a case, there is no way to automatically initiate the ZTP process.
This is a known issue that will be fixed in a future release of Cumulus RMP.