Cumulus VX 3.1.1 Release Notes

Follow

Overview

Cumulus VX is a community-supported virtual environment for cloud and network administrators to test the latest technology from Cumulus Networks, removing all organizational and economic barriers to getting started with open networking in your own time, at your own pace, and within your own environment.

The environment can be used to learn about, and evaluate, Cumulus Linux, anytime and anywhere, producing sandbox environments for prototype assessment, pre-production rollouts, and script development.

These release notes support Cumulus VX 3.1.1 and describe its features and known issues.

Stay up to date: Click Follow above so you can receive a notification when we update these release notes.

{{table_of_contents}}

What's New

Cumulus VX 3.1.1 includes bug fixes only.

Cumulus VX 3.1.z is a significant departure from 2.y.z releases. See the user guide for details on new behaviors and functionality.

Downloading Cumulus VX

You can download any of the of the four Cumulus VX images: 

  • An OVA disk image for use with VirtualBox.
  • A VMware-specific OVA disk image.
  • A qcow2 disk image for use with KVM.
  • A Box image for use with Vagrant.

Configuration Notes

Keep in mind the following issues when you are running your Cumulus VX virtual machine.

SNMP Not Supported in Quagga

There is no SNMP support for Quagga in Cumulus VX. However, it's possible to get it via SNMP by:

  • Using Nagios
  • Writing a pass persist script in Perl or Python by filling in the OSPF or BGP (rfc) MIBs manually.
  • Creating your own private MIB for the information you need.

Due to this circumstance, you must remove all references to smux in each of the following configuration files. If the smux entries are present in the configuration files, the daemons in the 2.5 packaged version of Quagga will not start.

  1. cd /etc/quagga
  2. grep smux *
  3. 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 VX.

Documentation

You can read the technical documentation here.

Community Support

If you have any questions or feedback about Cumulus VX, visit the Cumulus VX community for further support. 

Issues Fixed in the Cumulus VX 3.1.1 Update 2016-10-12

Cumulus Networks has made important package updates available for Cumulus VX 3.1.1 that resolve the issues listed below. These fixes were applied to the Cumulus Networks repository on October 12, 2016.

Release Note ID Summary Description

RN-486 (CM-13048)
LNV active-active mode: Adding peerlink to bridge after clagd connected results in looping packets

When clagd connects, it should install an ACL to prevent decapsulated BUM traffic from crossing the peerlink. However, when the peerlink is not in the bridge, it fails to install the ACL, allowing BUM to cross the peerlink and back out the VXLAN.

This issue is fixed in an update to Cumulus VX 3.1.1.


RN-488 (CM-12984)
MLAG with LNV active-active does not work with LACP bypass

When a bond slave is in LACP bypass state, it is removed from the hardware bond structure so that it can act as an individual port. In case the bridge is VXLAN enabled, a hardware VXLAN logical port must be created for this individual bond slave, but it isn't.

This issue is fixed in an update to Cumulus VX 3.1.1.


RN-491 (CM-11955)
Layer 3 traffic from non-VXLAN endpoint gets dropped when VXLAN is configured

Layer 3 forwarding does not work for VXLAN hosts directly connected to the gateway switch. The gateway switch must be a dedicated layer 3 gateway; the switch cannot be a top of rack switch that also provides layer 2 end-station functionality.

This issue is fixed in an update to Cumulus VX 3.1.1.

Issues Fixed in Cumulus VX 3.1.1

The following is a list of issues fixed in Cumulus VX 3.1.1 from earlier versions of Cumulus VX.

Release Note ID Summary Description

RN-465 (CM-11480)
IPv6 next hop global and peer addresses are ignored in favor of the link local address

When receiving a route from an IPv6 eBGP neighbor, Cumulus VX always installs the link local address instead of the peer address or the global address, even with a route map. This can cause issues in circumstances like when the neighbor router is advertising a virtual IP address as the next hop for a load balancer, whereas the next hop must be the global address, not a link local address.

This issue is fixed in Cumulus VX 3.1.1 — now the link local address no longer appears in the BGP table entry and the next hop is set to the globally-defined address.


RN-470 (CM-12687)
Buffer overflow in zebra

This issue is fixed in Cumulus VX 3.1.1.


RN-472 (CM-12390)
Expected routes not installed from bgpd to zebra

In some environments, multiple routes present in the BGP received-routes list and BGP table were not present within zebra or the kernel. To resolve this issue, iBGP peerings are now brought down upon link down, if they are tracked by single-hop BFD peering. This ensures many of the interim state transitions that caused the issues no longer take place.

Note: iBGP BFD sessions are treated as multi-hop by default in 2.5.x. The session will need to be explicitly configured as single hop.

This issue is fixed in Cumulus VX 3.1.1.


RN-476 (CM-12820)
switchd ignores neighbor table netlink messages

The issue occurs because the kernel neighbor table gets out of sync with the neighbor table in the hardware.

This issue is fixed in Cumulus VX 3.1.1.


RN-479 (CM-12030)
ARP entries for bridge get out of sync when MAC address changes, causing network drop

When VRR is configured, a v0 device is created for the bridge. Both interfaces, bridge and bridge-v0, keep ARP entries for hosts in that subnet. These need to be in sync as the reply path comes from bridge.

However, when a host changes its MAC address — which is common for tagged bonds in Ubuntu 16.04 — and comes up to ping the default gateway only the bridge-v0 ARP entry is updated, this leaves traffic blackholed until the bridge ARP entry expires and ARPs for the address with new MAC address or the hosts sends traffic to the bridge's actual IP address; this is uncommon as most times the traffic from the host is sent to the virtual address.

This issue is fixed in Cumulus VX 3.1.1.


RN-480 (CM-12161)
ovs-vtepd process results in high memory and CPU utilization

After a few days of running, it was reported that the ovs-vtepd process consumes over 500MB memory and generates high CPU usage. Restarting OVSDB services solves the issues only temporarily.

This issue is fixed in Cumulus VX 3.1.1.


RN-481 (CM-12798)
ifupdown2 error when bridge subinterface has both IPv4 and IPv6 addresses

When an interface has both IPv4 and IPv6 addresses, executing ifreload -a causes errors like the following to be displayed for both subinterfaces:

cumulus@switch:~$ sudo ifreload -a
error: bridge.200: cmd 'ip -force -batch - [addr add 10.50.103.193/26 dev bridge.200
addr add 2a01:75e0:0000:09b1::1/64 dev bridge.200
]' failed: returned 1 (RTNETLINK answers: File exists
Command failed -:1
)
error: bridge.100: cmd 'ip -force -batch - [addr add 10.50.103.129/26 dev bridge.100
addr add 2a01:75e0:0000:09b0::1/64 dev bridge.100
]' failed: returned 1 (RTNETLINK answers: File exists
Command failed -:1
)

This issue is fixed in Cumulus VX 3.1.1.

Known Issues in Cumulus VX 3.1.1

Issues are categorized for easy review. Some issues are fixed but will be available in a later release.

Release Note ID Summary Description

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-77 (CM-265)
New routes/ECMPs can evict existing/installed Cumulus VX 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: 52 
That translates to about 77 routes with ECMP NHs, if every route has the maximum ECMP NHs.

Monitoring this in Cumulus VX 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 / 512
The resource to monitor is the ecmp_nexthops. If this count is close to 4044, new ECMPs may evict existing routes.

RN-121 (CM-2123)
ptmd: When a physical interface is in a PTM FAIL state, its subinterface still exchanges information

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 VX cannot exceed 16 characters

Device names, including interface names, in Cumulus VX cannot exceed 16 characters – including the terminator. Cumulus VX 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-199 (CM-2624)
When a Quagga route-map is modified, the switch could use the partial map before edits are completed

Cumulus VX triggers a route-map update before the user finishes editing the route map, resulting in an incorrect route map being used. The route-map update trigger should only occur when user finishes editing the map.

Cumulus Networks is working to fix this issue.


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 VX at this time.

RN-275 (CM-5794)
BGP import-check fails for IPv6 route if static routes to null0 are used

The path that Cumulus VX originates should not be invalid since there is a matching route in the RIB. The import check works fine for IPv4 routes.


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-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 redistribute bgp route-map redist-map-name, you would enable redistribution without a route-map by following these steps in OSPF configuration mode:

  1. no redistribute bgp
  2. redistribute bgp

You would perform a similar sequence of commands for redistribution changes in BGP as well.


RN-351 (CM-7829)
Installing LNV

The LNV packages are not installed when you upgrade Cumulus VX. You can get the latest version of LNV for this release of Cumulus VX by installing the LNV packages for the registration and service node daemons using apt-get install vxfld-vxrd and/or apt-get install vxfld-vxsnd, depending upon how you intend to use LNV.


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-380 (CM-6110)
ifupdown2: adjust VLAN subinterface MTU based on MTU settings specified under lowerdev by the user

The following kernel error occurs when the MTU is specified under a subinterface rather than under the VLAN interface:

root@dell-s3000-04:~# ifreload -a -X eth0
warning: failed to execute cmd 'ip -force -batch - [addr add 1.1.4.1/24 dev swp52.100
link set dev swp52.100 mtu 9000 
]'(RTNETLINK answers: Numerical result out of range
Command failed -:2)

This issue is being investigated.


RN-382 (CM-6692)
Quagga: Removing bridge via ifupdown2 does not remove it from Quagga Removing a bridge using ifupdown2 does not remove it from the Quagga configuration files. This issue is being investigated; however, restarting Quagga will successfully remove the bridge.

RN-383 (CM-7196)
admin down of link deletes IPv6 nexthop static route entry, but not for IPv4

When a link is admin down and carrier is on, the IPv4 nexthop entry is marked dead, but the IPv6 nexthop entry is deleted, and will not be restored when the link is admin up. However, if carrier is off, the IPv6 nexthop is marked dead and not deleted. This inconsistency in admin down behavior is being investigated.


RN-384 (CM-7684)
Keeping VXLAN single-connected devices up on MLAG secondary node In the current MLAG secondary design, if the VXLAN device is not dual-connected, it is kept in a protodown state. You can keep them up with individual IP addresses rather than anycast IPs when the peerlink is down, so that all single-connected hosts will have connectivity. Further investigation regarding this issue is underway.

RN-387 (CM-8163)
Quagga appears to not honor passive interfaces if VRR is active

In a VRR configuration, any interface-specific routing configuration (e.g., OSPF mode of operation) specified on the subinterface having a virtual IP address does not take effect. This is because when an operator has specified a virtual IP on a bridge, the system creates another internal interface bridge with the virtual IP and MAC. These two interfaces are treated distinctly by Quagga, so any interface-specific routing configuration on the bridge does not get carried over to the second bridge.

In a VRR deployment needing any interface-specific routing configuration on the interface with a virtual IP address, the routing configuration has to be specified against the internally-created virtual interface also.


RN-389 (CM-8410)
switchd supports only port 4789 as the UDP port for VXLAN packets

switchd currently allows only the standard port 4789 as the UDP port for VXLAN packets. There are cases where a hypervisor could be using non-standard UDP port, which would cause VXLAN exchanges with the hardware VTEP to not work. In such a case, packets would not be terminated and encapsulated packets would be sent out on UDP port 4789.


RN-390 (CM-9055)
If you’re logged into the serial console and type reboot, the system may hang indefinitely

In Cumulus VX 3.1.1, systemd may block and stop handling systemctl changes, and fail to start or restart services, if the serial console columns or rows are changed. For example, running stty rows 30 columns 96 may cause this. In this state, a new login session will not be started on the serial console (/dev/ttyS0) after logout.

To verify whether systemd is hung in this manner, run cat /proc/1/stack; you should see output similar to the following:

[<ffffffff81466f5d>] tty_port_block_til_ready+0x1bd/0x330
[<ffffffff81093e90>] ? wait_woken+0x90/0x90
[<ffffffff8147abbb>] ? uart_startup.part.16+0xbb/0x1f0
[<ffffffff8147adef>] uart_open+0xff/0x180
[<ffffffff8145f025>] tty_open+0xf5/0x660
[<ffffffff811a3ad8>] chrdev_open+0xa8/0x1a0
[<ffffffff811a3a30>] ? cdev_put+0x30/0x30
[<ffffffff8119cc79>] do_dentry_open.isra.15+0x159/0x310
[<ffffffff8119e183>] vfs_open+0x53/0x60
[<ffffffff811acfd9>] do_last+0x249/0x11f0
[<ffffffff811af7c0>] path_openat+0x80/0x5f0
[<ffffffff811ec90e>] ? locks_dispose_list+0x3e/0x50
[<ffffffff811edae0>] ? __posix_lock_file+0xe0/0x630
[<ffffffff811b129a>] do_filp_open+0x3a/0xb0
[<ffffffff813cb8aa>] ? find_next_zero_bit+0x1a/0x30
[<ffffffff811bd8fe>] ? __alloc_fd+0x7e/0x120
[<ffffffff8119e52c>] do_sys_open+0x12c/0x220
[<ffffffff8119e63e>] SyS_open+0x1e/0x20
[<ffffffff816fdc57>] system_call_fastpath+0x12/0x6a

At this point it is necessary to power cycle or otherwise reset the switch to recover. A reboot or shutdown command will block, because systemd is hung.


RN-404 (CM-4407)
Aggregating routes in BGP with as-set can result in high CPU usage 

When BGP is configured with aggregate addresses with as-set configuration and there are many routes to be aggregated, the BGP process gets into high CPU usage.

To work around this issue, do not specify the as-set parameter for the aggregate-address configuration.


RN-409 (CM-10054)
BGP may show an inaccessible path as the best path

Existing BGP issues caused peering between a VRF device and a loopback BGP session to stay up if the loopback session doesn’t advertise its local address.

This issue will be fixed in a future release.


RN-414 (CM-11175)
Kernel source not added to Cumulus Networks repository

Kernel source (linux<vers>.orig.tar.xz and linux<vers>.debian.tar.xz) files are not being added properly to the Cumulus Networks repository.

You can retrieve these packages manually with apt-get source <package name>. For example, to retrieve the Cumulus Networks linux-image source package, run:

cumulus@switch:~$ sudo apt-get install linux-source-4.1

The archive file is stored at /usr/src/linux-source-4.1.tar.xz.


RN-454 (CM-12370)
An interface cannot have both inet and inet6 DHCP configurations

If you configure an interface so it can to obtain both IPv4 and IPv6 IP addresses via DHCP, ifupdown2 will honor only the first configuration and ignore the second.

In the following example configuration, ifupdown2 will only issue an IPv4 DHCP address for swp1, but not the IPv6 address.

auto swp1
iface swp1 inet dhcp
    link-speed 10000
    link-duplex full
    link-autoneg off

auto swp1
iface swp1 inet6 dhcp

This is a known issue that should be fixed in a future release of Cumulus VX.


RN-446 (CM-10513)
Redistribute neighbor does not work with more than 1024 interfaces

The rdnbrd service crashes because it cannot work with more than 1024 interfaces.

This issue should be fixed in a future release of Cumulus VX.


RN-447 (CM-11280)
"portwd: invalid SFF identifier: 0x0c" messages appear continuously in syslog

The following SFF message appears every 5 seconds in syslog:

cumulus@switch:~$ tail -f /var/log/syslog 
2016-08-06T12:18:56.095606-04:00 cumulus portwd: invalid SFF identifier: 0x0c
2016-08-06T12:19:01.113397-04:00 cumulus portwd: invalid SFF identifier: 0x0c
2016-08-06T12:19:01.121068-04:00 cumulus portwd: invalid SFF identifier: 0x0c
2016-08-06T12:19:01.121698-04:00 cumulus portwd: invalid SFF identifier: 0x0c
2016-08-06T12:19:06.139373-04:00 cumulus portwd: invalid SFF identifier: 0x0c
2016-08-06T12:19:06.147045-04:00 cumulus portwd: invalid SFF identifier: 0x0c
2016-08-06T12:19:06.147677-04:00 cumulus portwd: invalid SFF identifier: 0x0c
2016-08-06T12:19:11.165355-04:00 cumulus portwd: invalid SFF identifier: 0x0c
2016-08-06T12:19:11.173134-04:00 cumulus portwd: invalid SFF identifier: 0x0c
2016-08-06T12:19:11.173747-04:00 cumulus portwd: invalid SFF identifier: 0x0c
2016-08-06T12:19:16.191418-04:00 cumulus portwd: invalid SFF identifier: 0x0c
2016-08-06T12:19:16.199154-04:00 cumulus portwd: invalid SFF identifier: 0x0c
2016-08-06T12:19:16.199805-04:00 cumulus portwd: invalid SFF identifier: 0x0c

This is a know issue that should be fixed in a future version of Cumulus VX.


RN-449 (CM-11584)
In traditional bridge mode, clagd syncs MAC addresses in the wrong VLAN when the peerlink is tagged and the bond is native

When a traditional mode bridge is configured and the peerlink is tagged but the clagd bonds are native VLANs, clagd appears to try and sync the MAC addresses learned using the VLAN tag from the peerlink.

This causes the MAC address not to be synced correctly on the peer.

This is a known issue that should be fixed in a future release of Cumulus VX.


RN-453 (CM-12564)
Default routes learned via DHCP are moved to the management VRF even if they are not in the management VRF

The mgmt-vrf package has a dhclient exit hook that incorrectly assumes that DHCP is used only with the management interface. If management VRF is enabled, it inserts default routes from the DHCP server into the management table.

Until this issue is resolved, do not use DHCP with the front panel (switch) ports. If you need DHCP for a switch port, disable Management VRF and assign the port to a VRF.


RN-454 (CM-12565)
When VRF is enabled, the ICMP "need to fragment" is not respected

Cumulus VX defaults to using PMTU to discover if a path has a lower MTU than what is set on its local interfaces. If an ICMP - Fragmentation Needed packet is received on an interface associated with a VRF, the MTU change for the remote address is not properly handled. The end result is that packets exceeding the MTU going through that network segment are dropped.

To work around this issue until it is resolved, do one of the following:

  • Disable PMTU. This does not set the "don't fragment" bit in the IP header, allowing nodes to fragment the packet if needed.
    cumulus@switch:~$ sudo sysctl -w net.ipv4.ip_no_pmtu_disc=1
  • Manually reduce the MTU on the interface. Add mtu <value> to the stanza for that interface in /etc/network/interfaces.

RN-462 (CM-12631)
VX on Vbox - can't script the upgrade to 3.1.1 via apt-get update -y due to grub-pc dialog

Due to hypervisor behavior, upgrades to the grub-pc package may require manual intervention on VX platforms. This is specific to VX and will not occur on hardware platforms.

To resolve the problem, select "/dev/sda" from the interactive menu and continue installation.

Have more questions? Submit a request

Comments

Powered by Zendesk