Merge pull request #3008 from CumulusNetworks/create-pull-request/patch

Changes by create-pull-request action

Author: mergify[bot]

content/cumulus-linux-43/Whats-New/rn.md

@@ -759,14 +759,14 @@ pdfhidden: True
 | <a name="3390022"></a> [3390022](#3390022) <a name="3390022"></a> <br /> | 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 <code>peerlink.4095</code> interface stanza are duplicated. Subsequent <code>ifreloads</code>, or <code>net commit</code> commands fail until you manually remove the duplicated lines from this interface and run <code>ifreload -a</code>. | 4.2.1-4.4.5 | |
 | <a name="3376798"></a> [3376798](#3376798) <a name="3376798"></a> <br /> | On Broadcom switches, Cumulus Linux does not create the hardware bridging domain for a traditional bridge with a VXLAN interface during <code>switchd</code> restart. The <code>/var/log/switchd.log</code> file includes the following exception logs shortly after <code>switchd</code> restarts:<pre>switchd&#91;30158&#93;: hal_bcm_l3.c:1617 find_egr_path_if_vxlan_overlay:vxlan overlay : nh PORT: port <#>, vlan <x>.<y> not yet ready</pre>MAC learning looks correct, but traffic does not flow as expected. | 3.7.0-4.3.1 | 4.3.2-4.4.5|
 | <a name="3364996"></a> [3364996](#3364996) <a name="3364996"></a> <br /> | 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|
-| <a name="3364717"></a> [3364717](#3364717) <a name="3364717"></a> <br /> | 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|
-| <a name="3358865"></a> [3358865](#3358865) <a name="3358865"></a> <br /> | 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:<pre>ip route 0.0.0.0/1 10.1.1.1ip route 128.0.0.0/1 10.1.1.1</pre> | 4.3.1 | 4.3.2-4.4.5|
 | <a name="3339249"></a> [3339249](#3339249) <a name="3339249"></a> <br /> | The <code>sensors.conf</code> files in Cumulus Linux are out of date. | 4.2.1-4.4.5 | |
+| <a name="3336590"></a> [3336590](#3336590) <a name="3336590"></a> <br /> | 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|
 | <a name="3334031"></a> [3334031](#3334031) <a name="3334031"></a> <br /> | 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|
 | <a name="3330705"></a> [3330705](#3330705) <a name="3330705"></a> <br /> | 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 <code>prefer_ip_version</code> 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|
 | <a name="3327477"></a> [3327477](#3327477) <a name="3327477"></a> <br /> | If you use <code>su</code> to change to a user specified through TACACS+, the user becomes the local tacacs0 thru tacacs15 user instead of the named user to run <code>sudo</code> 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 | |
 | <a name="3319919"></a> [3319919](#3319919) <a name="3319919"></a> <br /> | 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|
 | <a name="3288385"></a> [3288385](#3288385) <a name="3288385"></a> <br /> | 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|
+| <a name="3288343"></a> [3288343](#3288343) <a name="3288343"></a> <br /> | 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:<pre>ip route 0.0.0.0/1 10.1.1.1ip route 128.0.0.0/1 10.1.1.1</pre> | 4.3.1 | 4.3.2-4.4.5|
 | <a name="3267353"></a> [3267353](#3267353) <a name="3267353"></a> <br /> | 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|
 | <a name="3235956"></a> [3235956](#3235956) <a name="3235956"></a> <br /> | 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, <code>switchd</code> 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|
 | <a name="3218207"></a> [3218207](#3218207) <a name="3218207"></a> <br /> | 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|
@@ -1077,8 +1077,8 @@ pdfhidden: True
 | <a name="3390022"></a> [3390022](#3390022) <a name="3390022"></a> <br /> | 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 <code>peerlink.4095</code> interface stanza are duplicated. Subsequent <code>ifreloads</code>, or <code>net commit</code> commands fail until you manually remove the duplicated lines from this interface and run <code>ifreload -a</code>. | 4.2.1-4.4.5 | |
 | <a name="3376798"></a> [3376798](#3376798) <a name="3376798"></a> <br /> | On Broadcom switches, Cumulus Linux does not create the hardware bridging domain for a traditional bridge with a VXLAN interface during <code>switchd</code> restart. The <code>/var/log/switchd.log</code> file includes the following exception logs shortly after <code>switchd</code> restarts:<pre>switchd&#91;30158&#93;: hal_bcm_l3.c:1617 find_egr_path_if_vxlan_overlay:vxlan overlay : nh PORT: port <#>, vlan <x>.<y> not yet ready</pre>MAC learning looks correct, but traffic does not flow as expected. | 3.7.0-4.3.1 | 4.3.2-4.4.5|
 | <a name="3364996"></a> [3364996](#3364996) <a name="3364996"></a> <br /> | 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|
-| <a name="3364717"></a> [3364717](#3364717) <a name="3364717"></a> <br /> | 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|
 | <a name="3339249"></a> [3339249](#3339249) <a name="3339249"></a> <br /> | The <code>sensors.conf</code> files in Cumulus Linux are out of date. | 4.2.1-4.4.5 | |
+| <a name="3336590"></a> [3336590](#3336590) <a name="3336590"></a> <br /> | 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|
 | <a name="3334031"></a> [3334031](#3334031) <a name="3334031"></a> <br /> | 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|
 | <a name="3330705"></a> [3330705](#3330705) <a name="3330705"></a> <br /> | 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 <code>prefer_ip_version</code> 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|
 | <a name="3327477"></a> [3327477](#3327477) <a name="3327477"></a> <br /> | If you use <code>su</code> to change to a user specified through TACACS+, the user becomes the local tacacs0 thru tacacs15 user instead of the named user to run <code>sudo</code> 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 | |

content/cumulus-linux-43/rn.xml

@@ -5391,28 +5391,18 @@ MAC learning looks correct, but traffic does not flow as expected.</td>
 <td>4.3.2-4.4.5</td>
 </tr>
 <tr>
-<td>3364717</td>
-<td>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.</td>
-<td>4.3.0-4.3.1</td>
-<td>4.3.2-4.4.5</td>
-</tr>
-<tr>
-<td>3358865</td>
-<td>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
-</td>
-<td>4.3.1</td>
-<td>4.3.2-4.4.5</td>
-</tr>
-<tr>
 <td>3339249</td>
 <td>The {{sensors.conf}} files in Cumulus Linux are out of date.</td>
 <td>4.2.1-4.4.5</td>
 <td></td>
 </tr>
 <tr>
+<td>3336590</td>
+<td>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.</td>
+<td>4.3.0-4.3.1</td>
+<td>4.3.2-4.4.5</td>
+</tr>
+<tr>
 <td>3334031</td>
 <td>When you configure or unconfigure a BGP peer and interface towards a host, memory corruption can cause BGP to crash.</td>
 <td>4.3.0-4.3.1</td>
@@ -5443,6 +5433,16 @@ ip route 128.0.0.0/1 10.1.1.1
 <td>4.3.2-4.4.5</td>
 </tr>
 <tr>
+<td>3288343</td>
+<td>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
+</td>
+<td>4.3.1</td>
+<td>4.3.2-4.4.5</td>
+</tr>
+<tr>
 <td>3267353</td>
 <td>In a QinQ configuration, if the VLAN priority is a non-zero value, double-tagged packets are translated to triple-tagged packets. </td>
 <td>4.3.1</td>
@@ -7584,18 +7584,18 @@ MAC learning looks correct, but traffic does not flow as expected.</td>
 <td>4.3.2-4.4.5</td>
 </tr>
 <tr>
-<td>3364717</td>
-<td>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.</td>
-<td>4.3.0-4.3.1</td>
-<td>4.3.2-4.4.5</td>
-</tr>
-<tr>
 <td>3339249</td>
 <td>The {{sensors.conf}} files in Cumulus Linux are out of date.</td>
 <td>4.2.1-4.4.5</td>
 <td></td>
 </tr>
 <tr>
+<td>3336590</td>
+<td>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.</td>
+<td>4.3.0-4.3.1</td>
+<td>4.3.2-4.4.5</td>
+</tr>
+<tr>
 <td>3334031</td>
 <td>When you configure or unconfigure a BGP peer and interface towards a host, memory corruption can cause BGP to crash.</td>
 <td>4.3.0-4.3.1</td>