These release notes support Cumulus RMP 3.3.2 and describe currently available features and known issues.
Stay up to Date
- Please sign in and click Follow above so you can receive a notification when we update these release notes.
- Subscribe to our product bulletin mailing list to receive important announcements and updates about issues that arise in our products.
- Subscribe to our security announcement mailing list to receive alerts whenever we update our software for security issues.
What's New in Cumulus RMP 3.3.2
Cumulus RMP 3.3.2 includes bug fixes only.
Installing Version 3.3.2
If you are upgrading from version 3.0.0 or later, use
apt-get to update the software.
Cumulus Networks recommends you use the
-E option with
sudo whenever you run any
apt-get command. This option preserves your environment variables — such as HTTP proxies — before you install new packages or upgrade your distribution.
- 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.3.2 installer for Broadcom switches 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.3.2 Update 2017-07-14
Cumulus Networks has made important package updates available for Cumulus RMP 3.3.2 that resolve the issues listed below. These fixes were applied to the Cumulus Networks repository on July 14, 2017.
Cumulus Networks strongly recommends you upgrade your Cumulus RMP distribution to avoid these issues (do not do a binary install). Follow these steps:
Issues Fixed in Cumulus RMP 3.3.2
The following is a list of issues fixed in Cumulus RMP 3.3.2 from earlier versions of Cumulus RMP.
Known Issues in Cumulus RMP 3.3.2
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.
|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 220.127.116.11/30 broadcast 18.104.22.168 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 22.214.171.124/30 brd 126.96.36.199 scope global swp8 104: [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.2049 105: [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.2050 106: [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.2051 107: [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.2052 108: [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.2053 109: [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.2054 110: [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.2055 [email protected]:$ bgp sessions: 220.127.116.11 ,4 ,64057 , 958 , 1036 , 0 , 0 , 0 ,15:55:42, 0, 10472 18.104.22.168 ,4 ,64058 , 958 , 1016 , 0 , 0 , 0 ,15:55:46, 187, 10285 22.214.171.124 ,4 ,64059 , 958 , 1049 , 0 , 0 , 0 ,15:55:40, 187, 10285 126.96.36.199 ,4 ,64060 , 958 , 1039 , 0 , 0 , 0 ,15:55:45, 187, 10285 188.8.131.52 ,4 ,64061 , 958 , 1014 , 0 , 0 , 0 ,15:55:46, 187, 10285 184.108.40.206 ,4 ,64062 , 958 , 1016 , 0 , 0 , 0 ,15:55:46, 187, 10285 220.127.116.11 ,4 ,64063 , 958 , 1029 , 0 , 0 , 0 ,15:55:43, 187, 10285 18.104.22.168 ,4 ,64064 , 958 , 1036 , 0 , 0 , 0 ,15:55:44, 187, 10285
|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.
|sFlow doesn't generate flow samples to sflowd on Tomahawk-based switches||At this time,
|DHCRELAY automatically binds to eth0 when not specified in the configuration||
This behavior is expected, due to upstream configuration. The packet is dropped later in the process, as it is not coming from a configured port.
|sFlow ifSpeed incorrect in counter samples||
Counter samples for an 80G bond (2 x 40G) exported from the switch show an interface speed (ifSpeed) of 14.464Gbps.
This issue is currently being investigated.
|Unable to change the bond-modes using ifup or ifreload||When the bond mode is changed from
2017-03-23 21:39:37,495: DEBUG: autolib.netobjects: [[email protected]:1042] sudo: ('ifup bond1',) 2017-03-23 21:39:37,926: DEBUG: autolib.netobjects: warning: error writing to file /sys/class/net/bond1/bonding/mode([Errno 39] Directory not empty)
This issue is being addressed in a later release.
|No reply to SNMP request (silently dropped) if the request is received on multiple interfaces||
When an SNMP server has multiple network paths to reach the switch, it is expected behavior that the SNMP request would arrive at multiple interfaces. However, it has been seen that Cumulus RMP silently drops any SNMP requests that arrive at an interface that does not match the return RIB lookup.
This issue occurs only if asymmetric routing is configured, where an SNMP request is received on multiple interfaces of the polled object.
To work around this issue, avoid asymmetric routing to the interfaces in question and configure a static route to pin the traffic to one link/bundle.
|The dhcpd process crashes when an interface request performs a DHCP request||
In certain conditions, if an interface attempts to send a DHCP request packet before the kernel port structures are fully initialized, the
To work around this issue, remove the
This issue is being investigated.