diff --git a/content/cumulus-linux-43/Whats-New/rn.md b/content/cumulus-linux-43/Whats-New/rn.md index edf8201404..2f4f6ff83b 100644 --- a/content/cumulus-linux-43/Whats-New/rn.md +++ b/content/cumulus-linux-43/Whats-New/rn.md @@ -1062,14 +1062,14 @@ pdfhidden: True | [3390022](#3390022)
| When you restore the switch configuration after upgrading from Cumulus Linux 4.2.x to 4.4.5 and later with ONIE, the configuration lines under the peerlink.4095 interface stanza are duplicated. Subsequent ifreloads, or net commit commands fail until you manually remove the duplicated lines from this interface and run ifreload -a. | 4.2.1-4.4.5 | | | [3376798](#3376798)
| On Broadcom switches, Cumulus Linux does not create the hardware bridging domain for a traditional bridge with a VXLAN interface during switchd restart. The /var/log/switchd.log file includes the following exception logs shortly after switchd restarts:
switchd[30158]: hal_bcm_l3.c:1617 find_egr_path_if_vxlan_overlay:vxlan overlay : nh PORT: port <#>, vlan . not yet ready
MAC learning looks correct, but traffic does not flow as expected. | 3.7.0-4.3.1 | 4.3.2-4.4.5| | [3364996](#3364996)
| Under certain conditions, BGP can allow a combination of EVPN and non-EVPN paths to be put into a multipath group together. This results in erroneous programming of EVPN symmetric next hops and RMACs, which can result in momentary traffic drops. | 4.3.0-4.3.1 | 4.3.2-4.4.5| -| [3364717](#3364717)
| On the Trident 2+ and Trident 3 switch when using VXLAN layer 2 VPNs and sending tunneled traffic where the inner IP header has a TTL of 1, the egress VTEP incorrectly forwards this traffic through the software path instead of the hardware data plane. This traffic is rate-limited to 100pps by default. To work around this issue, ensure that the traffic traversing the layer 2 tunnel has an inner IP header TTL value that is more than 1. If this workaround is not possible, contact Nvidia Support to determine other options. | 4.3.0-4.3.1 | 4.3.2-4.4.5| -| [3358865](#3358865)
| When you reboot a Broadcom switch with a static default route configured, the route might be installed in hardware without a next hop. This results in forwarded traffic to the CPU and drops. To recover from this issue, remove the default route configuration and reapply it. To prevent this issue, before rebooting the switch, split the default route configuration into two routes as below:
ip route 0.0.0.0/1 10.1.1.1ip route 128.0.0.0/1 10.1.1.1
| 4.3.1 | 4.3.2-4.4.5| | [3339249](#3339249)
| The sensors.conf files in Cumulus Linux are out of date. | 4.2.1-4.4.5 | | +| [3336590](#3336590)
| On the Trident 2+ and Trident 3 switch when using VXLAN layer 2 VPNs and sending tunneled traffic where the inner IP header has a TTL of 1, the egress VTEP incorrectly forwards this traffic through the software path instead of the hardware data plane. This traffic is rate-limited to 100pps by default. To work around this issue, ensure that the traffic traversing the layer 2 tunnel has an inner IP header TTL value that is more than 1. If this workaround is not possible, contact Nvidia Support to determine other options. | 4.3.0-4.3.1 | 4.3.2-4.4.5| | [3334031](#3334031)
| When you configure or unconfigure a BGP peer and interface towards a host, memory corruption can cause BGP to crash. | 4.3.0-4.3.1 | 4.3.2-4.4.5| | [3330705](#3330705)
| When using TACACS+, a TACACS+ server name that returns more than one IP address, such as an IPv6 and IPv4 address, is counted many times against the limit of seven TACACS+ servers, which might cause some of the later listed servers to be ignored as over the limit. To work around this issue, you can set the prefer_ip_version configuration option (the default value is 4) to choose between an IPv4 or IPv6 address if both are present. | 3.7.0-5.3.1 | 5.4.0-5.15.1| | [3327477](#3327477)
| If you use su to change to a user specified through TACACS+, the user becomes the local tacacs0 thru tacacs15 user instead of the named user to run sudo commands. As a result, the named user password might not match the local tacacs0 thru tacacs15 user password. | 3.7.0-3.7.16, 4.0.0-4.4.5, 5.0.0-5.15.1 | | | [3319919](#3319919)
| Currently, the default core dump size limit on Cumulus Linux is 256M but the SDK generates core dumps around 800M. To avoid incomplete core files, you can increase the core dump size limit. | 4.2.1-4.3.1, 4.4.0-5.3.1 | 4.3.2, 5.4.0-5.15.1| | [3288385](#3288385)
| On the EdgeCore AS7326-56X and AS7726-32X switch, the fan speed reports a minimum threshold in the logs. | 4.3.1 | 4.3.2-4.4.5| +| [3288343](#3288343)
| When you reboot a Broadcom switch with a static default route configured, the route might be installed in hardware without a next hop. This results in forwarded traffic to the CPU and drops. To recover from this issue, remove the default route configuration and reapply it. To prevent this issue, before rebooting the switch, split the default route configuration into two routes as below:
ip route 0.0.0.0/1 10.1.1.1ip route 128.0.0.0/1 10.1.1.1
| 4.3.1 | 4.3.2-4.4.5| | [3267353](#3267353)
| In a QinQ configuration, if the VLAN priority is a non-zero value, double-tagged packets are translated to triple-tagged packets. | 4.3.1 | 4.3.2-4.4.5| | [3235956](#3235956)
| With certain triggers on Broadcom switches, such as adding or deleting a VNI or reloading the network, Cumulus Linux might consider the underlay routes as overlay routes. In this case, switchd allocates the overlay next hop, which is incorrect and might affect traffic forwarding. | 4.3.0-4.3.1 | 4.3.2-4.4.5| | [3218207](#3218207)
| Certain routes on tenant VRFs have missing next hop entries because the router MAC address is missing in the bridge forwarding database table that corresponds to the remote VTEP. As a result, traffic forwarding is affected for these routes. | 4.3.0-5.2.1 | 5.3.0-5.15.1| @@ -1380,8 +1380,8 @@ pdfhidden: True | [3390022](#3390022)
| When you restore the switch configuration after upgrading from Cumulus Linux 4.2.x to 4.4.5 and later with ONIE, the configuration lines under the peerlink.4095 interface stanza are duplicated. Subsequent ifreloads, or net commit commands fail until you manually remove the duplicated lines from this interface and run ifreload -a. | 4.2.1-4.4.5 | | | [3376798](#3376798)
| On Broadcom switches, Cumulus Linux does not create the hardware bridging domain for a traditional bridge with a VXLAN interface during switchd restart. The /var/log/switchd.log file includes the following exception logs shortly after switchd restarts:
switchd[30158]: hal_bcm_l3.c:1617 find_egr_path_if_vxlan_overlay:vxlan overlay : nh PORT: port <#>, vlan . not yet ready
MAC learning looks correct, but traffic does not flow as expected. | 3.7.0-4.3.1 | 4.3.2-4.4.5| | [3364996](#3364996)
| Under certain conditions, BGP can allow a combination of EVPN and non-EVPN paths to be put into a multipath group together. This results in erroneous programming of EVPN symmetric next hops and RMACs, which can result in momentary traffic drops. | 4.3.0-4.3.1 | 4.3.2-4.4.5| -| [3364717](#3364717)
| On the Trident 2+ and Trident 3 switch when using VXLAN layer 2 VPNs and sending tunneled traffic where the inner IP header has a TTL of 1, the egress VTEP incorrectly forwards this traffic through the software path instead of the hardware data plane. This traffic is rate-limited to 100pps by default. To work around this issue, ensure that the traffic traversing the layer 2 tunnel has an inner IP header TTL value that is more than 1. If this workaround is not possible, contact Nvidia Support to determine other options. | 4.3.0-4.3.1 | 4.3.2-4.4.5| | [3339249](#3339249)
| The sensors.conf files in Cumulus Linux are out of date. | 4.2.1-4.4.5 | | +| [3336590](#3336590)
| On the Trident 2+ and Trident 3 switch when using VXLAN layer 2 VPNs and sending tunneled traffic where the inner IP header has a TTL of 1, the egress VTEP incorrectly forwards this traffic through the software path instead of the hardware data plane. This traffic is rate-limited to 100pps by default. To work around this issue, ensure that the traffic traversing the layer 2 tunnel has an inner IP header TTL value that is more than 1. If this workaround is not possible, contact Nvidia Support to determine other options. | 4.3.0-4.3.1 | 4.3.2-4.4.5| | [3334031](#3334031)
| When you configure or unconfigure a BGP peer and interface towards a host, memory corruption can cause BGP to crash. | 4.3.0-4.3.1 | 4.3.2-4.4.5| | [3330705](#3330705)
| When using TACACS+, a TACACS+ server name that returns more than one IP address, such as an IPv6 and IPv4 address, is counted many times against the limit of seven TACACS+ servers, which might cause some of the later listed servers to be ignored as over the limit. To work around this issue, you can set the prefer_ip_version configuration option (the default value is 4) to choose between an IPv4 or IPv6 address if both are present. | 3.7.0-5.3.1 | 5.4.0-5.15.1| | [3327477](#3327477)
| If you use su to change to a user specified through TACACS+, the user becomes the local tacacs0 thru tacacs15 user instead of the named user to run sudo commands. As a result, the named user password might not match the local tacacs0 thru tacacs15 user password. | 3.7.0-3.7.16, 4.0.0-4.4.5, 5.0.0-5.15.1 | | diff --git a/content/cumulus-linux-43/rn.xml b/content/cumulus-linux-43/rn.xml index 1d5f0540e6..79d9d6193a 100644 --- a/content/cumulus-linux-43/rn.xml +++ b/content/cumulus-linux-43/rn.xml @@ -7630,28 +7630,18 @@ MAC learning looks correct, but traffic does not flow as expected. 4.3.2-4.4.5 -3364717 -On the Trident 2+ and Trident 3 switch when using VXLAN layer 2 VPNs and sending tunneled traffic where the inner IP header has a TTL of 1, the egress VTEP incorrectly forwards this traffic through the software path instead of the hardware data plane. This traffic is rate-limited to 100pps by default. To work around this issue, ensure that the traffic traversing the layer 2 tunnel has an inner IP header TTL value that is more than 1. If this workaround is not possible, contact Nvidia Support to determine other options. -4.3.0-4.3.1 -4.3.2-4.4.5 - - -3358865 -When you reboot a Broadcom switch with a static default route configured, the route might be installed in hardware without a next hop. This results in forwarded traffic to the CPU and drops. To recover from this issue, remove the default route configuration and reapply it. To prevent this issue, before rebooting the switch, split the default route configuration into two routes as below: - -ip route 0.0.0.0/1 10.1.1.1 -ip route 128.0.0.0/1 10.1.1.1 - -4.3.1 -4.3.2-4.4.5 - - 3339249 The {{sensors.conf}} files in Cumulus Linux are out of date. 4.2.1-4.4.5 +3336590 +On the Trident 2+ and Trident 3 switch when using VXLAN layer 2 VPNs and sending tunneled traffic where the inner IP header has a TTL of 1, the egress VTEP incorrectly forwards this traffic through the software path instead of the hardware data plane. This traffic is rate-limited to 100pps by default. To work around this issue, ensure that the traffic traversing the layer 2 tunnel has an inner IP header TTL value that is more than 1. If this workaround is not possible, contact Nvidia Support to determine other options. +4.3.0-4.3.1 +4.3.2-4.4.5 + + 3334031 When you configure or unconfigure a BGP peer and interface towards a host, memory corruption can cause BGP to crash. 4.3.0-4.3.1 @@ -7682,6 +7672,16 @@ ip route 128.0.0.0/1 10.1.1.1 4.3.2-4.4.5 +3288343 +When you reboot a Broadcom switch with a static default route configured, the route might be installed in hardware without a next hop. This results in forwarded traffic to the CPU and drops. To recover from this issue, remove the default route configuration and reapply it. To prevent this issue, before rebooting the switch, split the default route configuration into two routes as below: + +ip route 0.0.0.0/1 10.1.1.1 +ip route 128.0.0.0/1 10.1.1.1 + +4.3.1 +4.3.2-4.4.5 + + 3267353 In a QinQ configuration, if the VLAN priority is a non-zero value, double-tagged packets are translated to triple-tagged packets. 4.3.1 @@ -9823,18 +9823,18 @@ MAC learning looks correct, but traffic does not flow as expected. 4.3.2-4.4.5 -3364717 -On the Trident 2+ and Trident 3 switch when using VXLAN layer 2 VPNs and sending tunneled traffic where the inner IP header has a TTL of 1, the egress VTEP incorrectly forwards this traffic through the software path instead of the hardware data plane. This traffic is rate-limited to 100pps by default. To work around this issue, ensure that the traffic traversing the layer 2 tunnel has an inner IP header TTL value that is more than 1. If this workaround is not possible, contact Nvidia Support to determine other options. -4.3.0-4.3.1 -4.3.2-4.4.5 - - 3339249 The {{sensors.conf}} files in Cumulus Linux are out of date. 4.2.1-4.4.5 +3336590 +On the Trident 2+ and Trident 3 switch when using VXLAN layer 2 VPNs and sending tunneled traffic where the inner IP header has a TTL of 1, the egress VTEP incorrectly forwards this traffic through the software path instead of the hardware data plane. This traffic is rate-limited to 100pps by default. To work around this issue, ensure that the traffic traversing the layer 2 tunnel has an inner IP header TTL value that is more than 1. If this workaround is not possible, contact Nvidia Support to determine other options. +4.3.0-4.3.1 +4.3.2-4.4.5 + + 3334031 When you configure or unconfigure a BGP peer and interface towards a host, memory corruption can cause BGP to crash. 4.3.0-4.3.1 diff --git a/content/cumulus-linux-50/Whats-New/rn.md b/content/cumulus-linux-50/Whats-New/rn.md index cd68a7f95d..4bf72fbbd7 100644 --- a/content/cumulus-linux-50/Whats-New/rn.md +++ b/content/cumulus-linux-50/Whats-New/rn.md @@ -65,8 +65,9 @@ pdfhidden: True | [3136983](#3136983)
| When a layer 3 neighbor entry resolves to a bridge FDB entry that does not exist in the kernel, switchd might contribute to high CPU load while it continues to try to sync and resolve the neighbor entry. This results in many sync_l3_nexthop messages printed to /var/log/switchd.log. | 5.0.1-5.1.0 | 5.2.0-5.15.1| | [3131423](#3131423)
| During EVPN multihoming bond failover, ARP and ND redirection fails if you configure layer 2 VNIs and ES bonds before you configure the loopback IP address of the switch. To work around this issue, configure the loopback IP address, then restart FRR with the systemctl restart frr command. | 4.3.0-5.1.0 | 5.2.0-5.15.1| | [3123965](#3123965)
| Under heavy system load, when many forwarding resources (routes, neighbors, ECMP groups, and so on) are removed from hardware, subsequent attempts to configure additional forwarding resources might fail and you see the following log message:
sx_sdk: EMAD_RX_THREAD: EMAD transaction FW error
| 4.4.0-5.1.0 | 5.2.0-5.15.1| -| [3120423](#3120423)
| When you configure an interface in FRR to send IPv6 RAs before you configure the interface in the /etc/network/interfaces file, the switch does not process IPv6 RAs. To work around this issue, remove the interface configuration in FRR and reapply it. | 3.7.15-4.3.0, 4.4.0-5.1.0 | 4.3.1, 5.2.0-5.15.1| +| [3123556](#3123556)
| When you configure an interface in FRR to send IPv6 RAs before you configure the interface in the /etc/network/interfaces file, the switch does not process IPv6 RAs. To work around this issue, remove the interface configuration in FRR and reapply it. | 3.7.15-4.3.0, 4.4.0-4.4.5, 5.0.0-5.15.1 | 4.3.1| | [3119673](#3119673)
| If the switch receives an EVPN route with multiple RTs that match the import policy for a local VNI, the bgpd service crashes. | 5.0.0-5.1.0 | 5.2.0-5.15.1| +| [3119615](#3119615)
| In an MLAG configuration, if you put a single connected interface into an admin down state, any dynamic MAC addresses on the peer link are flushed, then added back, which causes momentary traffic disruption. | 3.7.15-3.7.16, 4.3.0-4.4.5, 5.0.0-5.15.1 | | | [3117340](#3117340)
| When you edit the /usr/share/openvswitch/scripts/ovs-ctl-vtep file to change the ovs-vtepd configuration between vlan-aware and vlan-unaware mode, ovs-vtepd crashes when you restart the service. To recover, restart the networking service with the sudo systemctl restart networking command. | 4.3.0-5.1.0 | 5.2.0-5.15.1| | [3115415](#3115415)
| In the Cumulus-BGPVRF-MIB, the bgpPeerFsmEstablishedTime OID does not correctly report the time since a BGP session goes down. | 4.4.4-5.1.0 | 5.2.0-5.15.1| | [3112971](#3112971)
| When you configure a VRF static route using the legacy command syntax in FRR (for example: ip route 10.0.0.0/8 172.16.1.1 vrf vrf-red), then make subsequent VRF or route configuration changes, FRR might crash. To avoid this problem, use the current method for configuring VRF routes within the VRF stanza:
vrf vrf-red
 ip route 10.0.0.0/8 172.16.1.1 vrf vrf-redend vrf
| 4.4.3-5.1.0 | 5.2.0-5.15.1| @@ -78,7 +79,6 @@ pdfhidden: True | [3077547](#3077547)
| When you configure multiple multicast RPs with groups matched by prefix lists, Cumulus Linux selects only one of the RPs and this selection is incorrect. | 5.0.1-5.1.0 | 5.2.0-5.15.1| | [3077513](#3077513)
| When a MAC address is moved to a new VTEP in an EVPN MAC mobility scenario using traditional bridges, there might be up to 30 seconds of convergence delay. | 5.0.1-5.1.0 | 5.2.0-5.15.1| | [3074390](#3074390)
| You can not apply NVUE configurations when TACACS is enabled for user authentication. To work around this issue, add the nvue account to the exclude_users line in /etc/tacplus_nss.conf:
exclude_users=root,daemon,nobody,cron,radius_user,radius_priv_user,sshd,cumulus,quagga,frr,nvue,snmp,www-data,ntp,man,_lldpd,*
| 5.0.1-5.3.1 | 5.4.0-5.15.1| -| [3072674](#3072674)
| In an MLAG configuration, if you put a single connected interface into an admin down state, any dynamic MAC addresses on the peer link are flushed, then added back, which causes momentary traffic disruption. | 3.7.15-5.1.0 | 5.2.0-5.15.1| | [3066664](#3066664)
| In an EVPN-MH configuration, the switch fails to redirect tagged frames with the CoS bits set. | 4.4.0-4.4.3, 5.0.0-5.1.0 | 4.4.4-4.4.5, 5.2.0-5.15.1| | [3061445](#3061445)
| When you run the NVUE command to change the minimum interval between received BFD control packets or the minimum interval for sending BFD control packets, the configuration apply fails
cumulus@switch:~$ nv set vrf default router bgp neighbor 10.10.10.2 bfd min-rx-interval 400cumulus@switch:~$ nv config apply2022-05-04T21:36:10.800975+00:00 switch frrinit.sh16431: Stopped watchfrr
| 5.0.1-5.1.0 | 5.2.0-5.15.1| | [3059566](#3059566)
| When you add an interface to a layer 3 bond, traffic does not forward and you see errors similar to the following:
2022-05-02T13:14:40.118597+00:00 cumulus sx_sdk: ROUTER: Failed to delete router interface(27) ref count isn’t 0, err= Resource is in use
| 4.4.2-4.4.3, 5.0.1-5.1.0 | 4.4.4-4.4.5, 5.2.0-5.15.1| @@ -99,7 +99,7 @@ pdfhidden: True | [3021897](#3021897)
| After you remove the port from the EVPN-MH bond, the port stays in the PRTDN state with the protodown flag ON. | 4.4.3, 5.0.0-5.15.1 | 4.4.4-4.4.5| | [3021838](#3021838)
| PBR rules that you apply to interfaces in the default VRF install in the kernel with the action lookup local. As a result, packets that match this rule only perform a route lookup in the local table (which contains special routes for local IP addresses and broadcast addresses) but not in the main table (which contains unicast routes). As a result, policy routing might be applied to traffic incorrectly. | 4.4.2-5.0.1 | 5.1.0-5.15.1| | [3021696](#3021696)
| On the NVIDIA SN4600C switch, when you run the /usr/share/snmp/resq_pp.py script used by SNMP, you see the following log message in syslog regardless of the forwarding table profile set in the /etc/cumulus/datapath/traffic.conf file
resq_pp: EXCEPTION=invalid literal for int() with base 10: 'v4-lpm-heavy'
| 4.4.0-4.4.3, 5.0.0-5.15.1 | 4.4.4-4.4.5| -| [3020254](#3020254)
| When ARP suppression is off, GARPs from neighmgrd for remote neighbors are sent over VXLAN. | 3.7.15-4.3.0, 4.4.0-4.4.3, 5.0.0-5.1.0 | 4.3.1, 4.4.4-4.4.5, 5.2.0-5.15.1| +| [3021693](#3021693)
| When ARP suppression is off, GARPs from neighmgrd for remote neighbors are sent over VXLAN. | 3.7.15-4.3.0, 4.4.0-4.4.3, 5.0.0-5.15.1 | 4.3.1, 4.4.4-4.4.5| | [3017127](#3017127)
| After you convert a port from a layer 2 bond member to a layer 3 port, the switch drops transmitted untagged packets as egress VLAN membership discards. | 4.4.2-4.4.3, 5.0.0-5.0.1 | 4.4.4-4.4.5, 5.1.0-5.15.1| | [3016882](#3016882)
| In certain cases, when you power cycle the switch, the NVUE configuration might become corrupted, which prevents NVUE from running. You see a critical error in the log file similar to:
CRITICAL: cue_versions_v1.repo: The NVUE internal data store is corrupted or has been initialized incorrectly. The is an unrecoverable error
To work around this issue, remove the /var/lib/nvue/config and /var/lib/nvue/meta directories, then restart the nvued service with the sudo systemctl start nvued command. If possible, NVUE recovers user configuration and saves it in the /etc/nvue.d directory. The recovered configuration will be saved as YAML files, which are named as nvue-recovery-.yaml. You can reapply the recovered configuration with the nv config patch nvue-recovery-.yaml followed by nv config apply commands. | 5.0.1-5.1.0 | 5.2.0-5.15.1| | [3014664](#3014664)
| On the NVIDIA SN3420, the smonctl command output shows the maximum PSU temperature higher than the critical temperature. | 4.4.2-4.4.3, 5.0.0-5.1.0 | 4.4.4-4.4.5, 5.2.0-5.15.1| @@ -203,8 +203,9 @@ pdfhidden: True | [3138057](#3138057)
| When the next hop interface for EVPN type 5 routes flaps, FRR might uninstall the routes and Route install failed appears in /var/log/frr/frr.log. To work around this problem, restart FRR with the sudo systemctl restart frr command. | 4.4.0-5.2.1 | 5.3.0-5.15.1| | [3131423](#3131423)
| During EVPN multihoming bond failover, ARP and ND redirection fails if you configure layer 2 VNIs and ES bonds before you configure the loopback IP address of the switch. To work around this issue, configure the loopback IP address, then restart FRR with the systemctl restart frr command. | 4.3.0-5.1.0 | 5.2.0-5.15.1| | [3123965](#3123965)
| Under heavy system load, when many forwarding resources (routes, neighbors, ECMP groups, and so on) are removed from hardware, subsequent attempts to configure additional forwarding resources might fail and you see the following log message:
sx_sdk: EMAD_RX_THREAD: EMAD transaction FW error
| 4.4.0-5.1.0 | 5.2.0-5.15.1| -| [3120423](#3120423)
| When you configure an interface in FRR to send IPv6 RAs before you configure the interface in the /etc/network/interfaces file, the switch does not process IPv6 RAs. To work around this issue, remove the interface configuration in FRR and reapply it. | 3.7.15-4.3.0, 4.4.0-5.1.0 | 4.3.1, 5.2.0-5.15.1| +| [3123556](#3123556)
| When you configure an interface in FRR to send IPv6 RAs before you configure the interface in the /etc/network/interfaces file, the switch does not process IPv6 RAs. To work around this issue, remove the interface configuration in FRR and reapply it. | 3.7.15-4.3.0, 4.4.0-4.4.5, 5.0.0-5.15.1 | 4.3.1| | [3119673](#3119673)
| If the switch receives an EVPN route with multiple RTs that match the import policy for a local VNI, the bgpd service crashes. | 5.0.0-5.1.0 | 5.2.0-5.15.1| +| [3119615](#3119615)
| In an MLAG configuration, if you put a single connected interface into an admin down state, any dynamic MAC addresses on the peer link are flushed, then added back, which causes momentary traffic disruption. | 3.7.15-3.7.16, 4.3.0-4.4.5, 5.0.0-5.15.1 | | | [3117340](#3117340)
| When you edit the /usr/share/openvswitch/scripts/ovs-ctl-vtep file to change the ovs-vtepd configuration between vlan-aware and vlan-unaware mode, ovs-vtepd crashes when you restart the service. To recover, restart the networking service with the sudo systemctl restart networking command. | 4.3.0-5.1.0 | 5.2.0-5.15.1| | [3115415](#3115415)
| In the Cumulus-BGPVRF-MIB, the bgpPeerFsmEstablishedTime OID does not correctly report the time since a BGP session goes down. | 4.4.4-5.1.0 | 5.2.0-5.15.1| | [3112971](#3112971)
| When you configure a VRF static route using the legacy command syntax in FRR (for example: ip route 10.0.0.0/8 172.16.1.1 vrf vrf-red), then make subsequent VRF or route configuration changes, FRR might crash. To avoid this problem, use the current method for configuring VRF routes within the VRF stanza:
vrf vrf-red
 ip route 10.0.0.0/8 172.16.1.1 vrf vrf-redend vrf
| 4.4.3-5.1.0 | 5.2.0-5.15.1| @@ -212,7 +213,6 @@ pdfhidden: True | [3102128](#3102128)
| When you configure a new VNI, the VLAN 1 VNI mapping is removed from the VXLAN device. To work around this issue, set the VNI interface mapped to VLAN 1 down and up again. | 5.0.0-5.1.0 | 5.2.0-5.15.1| | [3084476](#3084476)
| After you disable traffic shaping in the /etc/cumulus/datapath/qos/qos_features.conf file, the default QOS traffic shaping configuration does not restore. To work around this issue, restart switchd. | 4.4.3, 5.0.0-5.15.1 | 4.4.4-4.4.5| | [3084027](#3084027)
| Under a high load, you might see ingress drop counters increase. The drops are classified as HwIfInDiscards in ethtool and shown as ingress_general in hardware. | 4.3.0-4.4.5, 5.0.0-5.15.1 | | -| [3072674](#3072674)
| In an MLAG configuration, if you put a single connected interface into an admin down state, any dynamic MAC addresses on the peer link are flushed, then added back, which causes momentary traffic disruption. | 3.7.15-5.1.0 | 5.2.0-5.15.1| | [3066664](#3066664)
| In an EVPN-MH configuration, the switch fails to redirect tagged frames with the CoS bits set. | 4.4.0-4.4.3, 5.0.0-5.1.0 | 4.4.4-4.4.5, 5.2.0-5.15.1| | [3059135](#3059135)
| In an OSPF configuration, after you change the IPv6 subnet mask, the old address remains in the RIB as a connected OSPF route
To resolve this issue, restart FRR with the sudo systemctl restart frr command. | 4.3.0-5.1.0 | 5.2.0-5.15.1| | [3054869](#3054869)
| When you run NVUE commands as part of ZTP scripts, the commands fail with errors that indicate a missing $HOME environment variable. The issue has been fixed where the ZTP module initializes the $HOME environment variable before launching the ZTP scripts. However, if you are running older releases, before you use any NVUE commands in the ZTP script, add a section and define the HOME environment variable. Populate the variable with the default expected root user home directory value (/root), then export the HOME variable so it is available globally for NVUE to use
HOME=/rootexport HOME
| 5.0.0-5.1.0 | 5.2.0-5.15.1| @@ -225,7 +225,7 @@ pdfhidden: True | [3021897](#3021897)
| After you remove the port from the EVPN-MH bond, the port stays in the PRTDN state with the protodown flag ON. | 4.4.3, 5.0.0-5.15.1 | 4.4.4-4.4.5| | [3021838](#3021838)
| PBR rules that you apply to interfaces in the default VRF install in the kernel with the action lookup local. As a result, packets that match this rule only perform a route lookup in the local table (which contains special routes for local IP addresses and broadcast addresses) but not in the main table (which contains unicast routes). As a result, policy routing might be applied to traffic incorrectly. | 4.4.2-5.0.1 | 5.1.0-5.15.1| | [3021696](#3021696)
| On the NVIDIA SN4600C switch, when you run the /usr/share/snmp/resq_pp.py script used by SNMP, you see the following log message in syslog regardless of the forwarding table profile set in the /etc/cumulus/datapath/traffic.conf file
resq_pp: EXCEPTION=invalid literal for int() with base 10: 'v4-lpm-heavy'
| 4.4.0-4.4.3, 5.0.0-5.15.1 | 4.4.4-4.4.5| -| [3020254](#3020254)
| When ARP suppression is off, GARPs from neighmgrd for remote neighbors are sent over VXLAN. | 3.7.15-4.3.0, 4.4.0-4.4.3, 5.0.0-5.1.0 | 4.3.1, 4.4.4-4.4.5, 5.2.0-5.15.1| +| [3021693](#3021693)
| When ARP suppression is off, GARPs from neighmgrd for remote neighbors are sent over VXLAN. | 3.7.15-4.3.0, 4.4.0-4.4.3, 5.0.0-5.15.1 | 4.3.1, 4.4.4-4.4.5| | [3017127](#3017127)
| After you convert a port from a layer 2 bond member to a layer 3 port, the switch drops transmitted untagged packets as egress VLAN membership discards. | 4.4.2-4.4.3, 5.0.0-5.0.1 | 4.4.4-4.4.5, 5.1.0-5.15.1| | [3014664](#3014664)
| On the NVIDIA SN3420, the smonctl command output shows the maximum PSU temperature higher than the critical temperature. | 4.4.2-4.4.3, 5.0.0-5.1.0 | 4.4.4-4.4.5, 5.2.0-5.15.1| | [3008388](#3008388)
| When you set vlan-bridge-binding on for a VLAN interface, the VLAN interface status does not change to down even when all bridge member ports are down. | 4.4.3-5.0.1 | 5.1.0-5.15.1| diff --git a/content/cumulus-linux-50/rn.xml b/content/cumulus-linux-50/rn.xml index dc623f0729..7dfb60b435 100644 --- a/content/cumulus-linux-50/rn.xml +++ b/content/cumulus-linux-50/rn.xml @@ -349,10 +349,10 @@ sx_sdk: EMAD_RX_THREAD: EMAD transaction FW error 5.2.0-5.15.1 -3120423 +3123556 When you configure an interface in FRR to send IPv6 RAs before you configure the interface in the {{/etc/network/interfaces}} file, the switch does not process IPv6 RAs. To work around this issue, remove the interface configuration in FRR and reapply it. -3.7.15-4.3.0, 4.4.0-5.1.0 -4.3.1, 5.2.0-5.15.1 +3.7.15-4.3.0, 4.4.0-4.4.5, 5.0.0-5.15.1 +4.3.1 3119673 @@ -361,6 +361,12 @@ sx_sdk: EMAD_RX_THREAD: EMAD transaction FW error 5.2.0-5.15.1 +3119615 +In an MLAG configuration, if you put a single connected interface into an {{admin down}} state, any dynamic MAC addresses on the peer link are flushed, then added back, which causes momentary traffic disruption. +3.7.15-3.7.16, 4.3.0-4.4.5, 5.0.0-5.15.1 + + + 3117340 When you edit the {{/usr/share/openvswitch/scripts/ovs-ctl-vtep}} file to change the {{ovs-vtepd}} configuration between {{vlan-aware}} and {{vlan-unaware}} mode, {{ovs-vtepd}} crashes when you restart the service. To recover, restart the networking service with the {{sudo systemctl restart networking}} command. 4.3.0-5.1.0 @@ -441,12 +447,6 @@ exclude_users=root,daemon,nobody,cron,radius_user,radius_priv_user,sshd,cumulus, 5.4.0-5.15.1 -3072674 -In an MLAG configuration, if you put a single connected interface into an {{admin down}} state, any dynamic MAC addresses on the peer link are flushed, then added back, which causes momentary traffic disruption. -3.7.15-5.1.0 -5.2.0-5.15.1 - - 3066664 In an EVPN-MH configuration, the switch fails to redirect tagged frames with the CoS bits set. 4.4.0-4.4.3, 5.0.0-5.1.0 @@ -590,10 +590,10 @@ resq_pp: EXCEPTION=invalid literal for int() with base 10: 'v4-lpm-heavy' 4.4.4-4.4.5 -3020254 +3021693 When ARP suppression is off, GARPs from {{neighmgrd}} for remote neighbors are sent over VXLAN. -3.7.15-4.3.0, 4.4.0-4.4.3, 5.0.0-5.1.0 -4.3.1, 4.4.4-4.4.5, 5.2.0-5.15.1 +3.7.15-4.3.0, 4.4.0-4.4.3, 5.0.0-5.15.1 +4.3.1, 4.4.4-4.4.5 3017127 @@ -1246,10 +1246,10 @@ sx_sdk: EMAD_RX_THREAD: EMAD transaction FW error 5.2.0-5.15.1 -3120423 +3123556 When you configure an interface in FRR to send IPv6 RAs before you configure the interface in the {{/etc/network/interfaces}} file, the switch does not process IPv6 RAs. To work around this issue, remove the interface configuration in FRR and reapply it. -3.7.15-4.3.0, 4.4.0-5.1.0 -4.3.1, 5.2.0-5.15.1 +3.7.15-4.3.0, 4.4.0-4.4.5, 5.0.0-5.15.1 +4.3.1 3119673 @@ -1258,6 +1258,12 @@ sx_sdk: EMAD_RX_THREAD: EMAD transaction FW error 5.2.0-5.15.1 +3119615 +In an MLAG configuration, if you put a single connected interface into an {{admin down}} state, any dynamic MAC addresses on the peer link are flushed, then added back, which causes momentary traffic disruption. +3.7.15-3.7.16, 4.3.0-4.4.5, 5.0.0-5.15.1 + + + 3117340 When you edit the {{/usr/share/openvswitch/scripts/ovs-ctl-vtep}} file to change the {{ovs-vtepd}} configuration between {{vlan-aware}} and {{vlan-unaware}} mode, {{ovs-vtepd}} crashes when you restart the service. To recover, restart the networking service with the {{sudo systemctl restart networking}} command. 4.3.0-5.1.0 @@ -1306,12 +1312,6 @@ To work around this issue, set the VNI interface mapped to VLAN 1 down and up ag -3072674 -In an MLAG configuration, if you put a single connected interface into an {{admin down}} state, any dynamic MAC addresses on the peer link are flushed, then added back, which causes momentary traffic disruption. -3.7.15-5.1.0 -5.2.0-5.15.1 - - 3066664 In an EVPN-MH configuration, the switch fails to redirect tagged frames with the CoS bits set. 4.4.0-4.4.3, 5.0.0-5.1.0 @@ -1392,10 +1392,10 @@ resq_pp: EXCEPTION=invalid literal for int() with base 10: 'v4-lpm-heavy' 4.4.4-4.4.5 -3020254 +3021693 When ARP suppression is off, GARPs from {{neighmgrd}} for remote neighbors are sent over VXLAN. -3.7.15-4.3.0, 4.4.0-4.4.3, 5.0.0-5.1.0 -4.3.1, 4.4.4-4.4.5, 5.2.0-5.15.1 +3.7.15-4.3.0, 4.4.0-4.4.3, 5.0.0-5.15.1 +4.3.1, 4.4.4-4.4.5 3017127 diff --git a/content/cumulus-linux-51/Whats-New/rn.md b/content/cumulus-linux-51/Whats-New/rn.md index 342da1f9b3..e86c07cf02 100644 --- a/content/cumulus-linux-51/Whats-New/rn.md +++ b/content/cumulus-linux-51/Whats-New/rn.md @@ -87,8 +87,9 @@ pdfhidden: True | [3135070](#3135070)
| After you configure the NVIDIA SN2010 series switch for the first time with NVUE, you see the fan speed at 100 percent. To work around this issue, run the sudo systemctl restart hw-management.service command to restart the hardware management service. | 5.1.0 | 5.2.0-5.15.1| | [3131423](#3131423)
| During EVPN multihoming bond failover, ARP and ND redirection fails if you configure layer 2 VNIs and ES bonds before you configure the loopback IP address of the switch. To work around this issue, configure the loopback IP address, then restart FRR with the systemctl restart frr command. | 4.3.0-5.1.0 | 5.2.0-5.15.1| | [3123965](#3123965)
| Under heavy system load, when many forwarding resources (routes, neighbors, ECMP groups, and so on) are removed from hardware, subsequent attempts to configure additional forwarding resources might fail and you see the following log message:
sx_sdk: EMAD_RX_THREAD: EMAD transaction FW error
| 4.4.0-5.1.0 | 5.2.0-5.15.1| -| [3120423](#3120423)
| When you configure an interface in FRR to send IPv6 RAs before you configure the interface in the /etc/network/interfaces file, the switch does not process IPv6 RAs. To work around this issue, remove the interface configuration in FRR and reapply it. | 3.7.15-4.3.0, 4.4.0-5.1.0 | 4.3.1, 5.2.0-5.15.1| +| [3123556](#3123556)
| When you configure an interface in FRR to send IPv6 RAs before you configure the interface in the /etc/network/interfaces file, the switch does not process IPv6 RAs. To work around this issue, remove the interface configuration in FRR and reapply it. | 3.7.15-4.3.0, 4.4.0-4.4.5, 5.0.0-5.15.1 | 4.3.1| | [3119673](#3119673)
| If the switch receives an EVPN route with multiple RTs that match the import policy for a local VNI, the bgpd service crashes. | 5.0.0-5.1.0 | 5.2.0-5.15.1| +| [3119615](#3119615)
| In an MLAG configuration, if you put a single connected interface into an admin down state, any dynamic MAC addresses on the peer link are flushed, then added back, which causes momentary traffic disruption. | 3.7.15-3.7.16, 4.3.0-4.4.5, 5.0.0-5.15.1 | | | [3117340](#3117340)
| When you edit the /usr/share/openvswitch/scripts/ovs-ctl-vtep file to change the ovs-vtepd configuration between vlan-aware and vlan-unaware mode, ovs-vtepd crashes when you restart the service. To recover, restart the networking service with the sudo systemctl restart networking command. | 4.3.0-5.1.0 | 5.2.0-5.15.1| | [3115419](#3115419)
| When you configure conditional advertisement, BGP might crash when you run show commands or during a steady state. | 5.1.0 | 5.2.0-5.15.1| | [3115415](#3115415)
| In the Cumulus-BGPVRF-MIB, the bgpPeerFsmEstablishedTime OID does not correctly report the time since a BGP session goes down. | 4.4.4-5.1.0 | 5.2.0-5.15.1| @@ -105,7 +106,6 @@ pdfhidden: True | [3077547](#3077547)
| When you configure multiple multicast RPs with groups matched by prefix lists, Cumulus Linux selects only one of the RPs and this selection is incorrect. | 5.0.1-5.1.0 | 5.2.0-5.15.1| | [3077513](#3077513)
| When a MAC address is moved to a new VTEP in an EVPN MAC mobility scenario using traditional bridges, there might be up to 30 seconds of convergence delay. | 5.0.1-5.1.0 | 5.2.0-5.15.1| | [3074390](#3074390)
| You can not apply NVUE configurations when TACACS is enabled for user authentication. To work around this issue, add the nvue account to the exclude_users line in /etc/tacplus_nss.conf:
exclude_users=root,daemon,nobody,cron,radius_user,radius_priv_user,sshd,cumulus,quagga,frr,nvue,snmp,www-data,ntp,man,_lldpd,*
| 5.0.1-5.3.1 | 5.4.0-5.15.1| -| [3072674](#3072674)
| In an MLAG configuration, if you put a single connected interface into an admin down state, any dynamic MAC addresses on the peer link are flushed, then added back, which causes momentary traffic disruption. | 3.7.15-5.1.0 | 5.2.0-5.15.1| | [3071652](#3071652)
| On rare occasions, after you reboot or restart switchd on a Spectrum 1 switch, any 25G connections with Direct Attach Copper (DAC) cables that connect from the switch to a non-NVIDIA device might flap continuously. To work around this issue, bring the affected link administratively down for a few seconds on the non-NVIDIA device, then bring the link back up. | 4.4.4-4.4.5, 5.1.0-5.15.1 | | | [3069069](#3069069)
| When you run the systemctl reload switchd command, there is momentary traffic loss after a port configured with lossless buffers goes down. This is only temporary and the traffic stabilizes after the initial drops. | 5.1.0-5.5.1 | 5.6.0-5.15.1| | [3066664](#3066664)
| In an EVPN-MH configuration, the switch fails to redirect tagged frames with the CoS bits set. | 4.4.0-4.4.3, 5.0.0-5.1.0 | 4.4.4-4.4.5, 5.2.0-5.15.1| @@ -126,7 +126,7 @@ pdfhidden: True | [3037824](#3037824)
| The NVUE nv show interface link state command shows an empty table instead of showing the port link state. | 5.0.0-5.3.1 | 5.4.0-5.15.1| | [3034435](#3034435)
| In an MLAG EVPN deployment when either of the MLAG peers reboots, FRR incorrectly programs the local host entries in the ARP table as remote. To work around this issue, either restart FRR or use BGP policies to mark and drop routes within an MLAG pair. Both MLAG peers must have an outbound policy that add a community representing the unique MLAG pair to Type-2 EVPN routes and an inbound policy to match and drop that community. | 4.4.4-5.4.0 | 5.5.0-5.15.1| | [3023345](#3023345)
| When you run NVUE commands to unset one or more options associated with a field, the command fails with an error. For example:
cumulus@switch:~$ nv unset system forwarding ecmp-hash source-portusage: nv unset system forwarding ecmp-hash [options]nv unset system forwarding ecmp-hash: error: unrecognized arguments: source-port
| 5.1.0 | 5.2.0-5.15.1| -| [3020254](#3020254)
| When ARP suppression is off, GARPs from neighmgrd for remote neighbors are sent over VXLAN. | 3.7.15-4.3.0, 4.4.0-4.4.3, 5.0.0-5.1.0 | 4.3.1, 4.4.4-4.4.5, 5.2.0-5.15.1| +| [3021693](#3021693)
| When ARP suppression is off, GARPs from neighmgrd for remote neighbors are sent over VXLAN. | 3.7.15-4.3.0, 4.4.0-4.4.3, 5.0.0-5.15.1 | 4.3.1, 4.4.4-4.4.5| | [3016882](#3016882)
| In certain cases, when you power cycle the switch, the NVUE configuration might become corrupted, which prevents NVUE from running. You see a critical error in the log file similar to:
CRITICAL: cue_versions_v1.repo: The NVUE internal data store is corrupted or has been initialized incorrectly. The is an unrecoverable error
To work around this issue, remove the /var/lib/nvue/config and /var/lib/nvue/meta directories, then restart the nvued service with the sudo systemctl start nvued command. If possible, NVUE recovers user configuration and saves it in the /etc/nvue.d directory. The recovered configuration will be saved as YAML files, which are named as nvue-recovery-.yaml. You can reapply the recovered configuration with the nv config patch nvue-recovery-.yaml followed by nv config apply commands. | 5.0.1-5.1.0 | 5.2.0-5.15.1| | [3015393](#3015393)
| The NVUE nv show interface command shows the operational state of the tunnel as down even though the tunnel is up, and encapsulation and decapsulation occurs correctly. | 5.1.0-5.3.1 | 5.4.0-5.15.1| | [3014664](#3014664)
| On the NVIDIA SN3420, the smonctl command output shows the maximum PSU temperature higher than the critical temperature. | 4.4.2-4.4.3, 5.0.0-5.1.0 | 4.4.4-4.4.5, 5.2.0-5.15.1| diff --git a/content/cumulus-linux-51/rn.xml b/content/cumulus-linux-51/rn.xml index 6a245ec670..6ecf492f95 100644 --- a/content/cumulus-linux-51/rn.xml +++ b/content/cumulus-linux-51/rn.xml @@ -499,10 +499,10 @@ sx_sdk: EMAD_RX_THREAD: EMAD transaction FW error 5.2.0-5.15.1 -3120423 +3123556 When you configure an interface in FRR to send IPv6 RAs before you configure the interface in the {{/etc/network/interfaces}} file, the switch does not process IPv6 RAs. To work around this issue, remove the interface configuration in FRR and reapply it. -3.7.15-4.3.0, 4.4.0-5.1.0 -4.3.1, 5.2.0-5.15.1 +3.7.15-4.3.0, 4.4.0-4.4.5, 5.0.0-5.15.1 +4.3.1 3119673 @@ -511,6 +511,12 @@ sx_sdk: EMAD_RX_THREAD: EMAD transaction FW error 5.2.0-5.15.1 +3119615 +In an MLAG configuration, if you put a single connected interface into an {{admin down}} state, any dynamic MAC addresses on the peer link are flushed, then added back, which causes momentary traffic disruption. +3.7.15-3.7.16, 4.3.0-4.4.5, 5.0.0-5.15.1 + + + 3117340 When you edit the {{/usr/share/openvswitch/scripts/ovs-ctl-vtep}} file to change the {{ovs-vtepd}} configuration between {{vlan-aware}} and {{vlan-unaware}} mode, {{ovs-vtepd}} crashes when you restart the service. To recover, restart the networking service with the {{sudo systemctl restart networking}} command. 4.3.0-5.1.0 @@ -623,12 +629,6 @@ exclude_users=root,daemon,nobody,cron,radius_user,radius_priv_user,sshd,cumulus, 5.4.0-5.15.1 -3072674 -In an MLAG configuration, if you put a single connected interface into an {{admin down}} state, any dynamic MAC addresses on the peer link are flushed, then added back, which causes momentary traffic disruption. -3.7.15-5.1.0 -5.2.0-5.15.1 - - 3071652 On rare occasions, after you reboot or restart {{switchd}} on a Spectrum 1 switch, any 25G connections with Direct Attach Copper (DAC) cables that connect from the switch to a non-NVIDIA device might flap continuously. To work around this issue, bring the affected link administratively down for a few seconds on the non-NVIDIA device, then bring the link back up. 4.4.4-4.4.5, 5.1.0-5.15.1 @@ -790,10 +790,10 @@ nv unset system forwarding ecmp-hash: error: unrecognized arguments: source-port 5.2.0-5.15.1 -3020254 +3021693 When ARP suppression is off, GARPs from {{neighmgrd}} for remote neighbors are sent over VXLAN. -3.7.15-4.3.0, 4.4.0-4.4.3, 5.0.0-5.1.0 -4.3.1, 4.4.4-4.4.5, 5.2.0-5.15.1 +3.7.15-4.3.0, 4.4.0-4.4.3, 5.0.0-5.15.1 +4.3.1, 4.4.4-4.4.5 3016882 diff --git a/content/cumulus-linux-53/Whats-New/rn.md b/content/cumulus-linux-53/Whats-New/rn.md index 9986a932e9..19af8f6a1b 100644 --- a/content/cumulus-linux-53/Whats-New/rn.md +++ b/content/cumulus-linux-53/Whats-New/rn.md @@ -106,7 +106,6 @@ pdfhidden: True | [3226525](#3226525)
| When using TACACS+, if you configure per-command authorization with the tacplus-restrict command, NVUE configuration commands fail for any user with a privilege level lower than 15. This occurs because NVUE is not able to create a .local user directory. | 5.2.0-5.3.1 | 5.4.0-5.15.1| | [3226506](#3226506)
| The l1-show eth0 command does not show port information and is not supported in this release. | 5.3.0-5.15.1 | | | [3221628](#3221628)
| Cumulus Linux VX images might include an incorrect entry at the end of /etc/apt/sources.list, which produces warnings when you run apt update. Remove this entry to avoid these warnings. | 5.2.0-5.6.0 | 5.7.0-5.15.1| -| [3192808](#3192808)
| When a switch receives an LLDP frame from a Cisco router right after a ptmd restart, the ptmd service crashes. | 4.3.0-4.3.1, 4.4.0-4.4.5, 5.0.1-5.15.1 | 4.3.2| | [3187469](#3187469)
| At high scale with 160 VRFs and 10 VLANs per VRF (a total of 1600 VLANs), you see traffic loss during primary switch reboot. To work around this issue, reduce the scale to 40 VRFs with no more than 400 VLANs in the configuration, and use a common MAC address. | 5.1.0-5.5.1 | 5.6.0-5.15.1| | [3178090](#3178090)
| The cl-support generation script causes TC filter collection to run as a background process for each interface, which can lead to memory exhaustion on a high scale configuration and on a switch with a small memory footprint. | 5.1.0-5.5.1 | 5.6.0-5.15.1| | [3172682](#3172682)
| On rare occasions, when you query the system hostname through the hostnamctl application, you see a timeout. NVUE uses the hostnamctl application to determine the system hostname, which can result in an nv config apply command failure. | 5.2.0-5.5.1 | 5.6.0-5.15.1| diff --git a/content/cumulus-linux-53/rn.xml b/content/cumulus-linux-53/rn.xml index 38bf185a6e..3a42946852 100644 --- a/content/cumulus-linux-53/rn.xml +++ b/content/cumulus-linux-53/rn.xml @@ -601,12 +601,6 @@ Can't set non-static MAC address for non-vPort 0x0001006B when VID is VFID. 5.7.0-5.15.1 -3192808 -When a switch receives an LLDP frame from a Cisco router right after a {{ptmd}} restart, the {{ptmd}} service crashes. -4.3.0-4.3.1, 4.4.0-4.4.5, 5.0.1-5.15.1 -4.3.2 - - 3187469 At high scale with 160 VRFs and 10 VLANs per VRF (a total of 1600 VLANs), you see traffic loss during primary switch reboot. To work around this issue, reduce the scale to 40 VRFs with no more than 400 VLANs in the configuration, and use a common MAC address. 5.1.0-5.5.1