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

Changes by create-pull-request action

Author: mergify[bot]

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

@@ -18,6 +18,7 @@ pdfhidden: True
 | <a name="4797691"></a> [4797691](#4797691) <a name="4797691"></a> <br /> | The message that the switch displays when you generate a cl-support file or as a post login banner contains an invalid Cumulus Support email address, which is no longer the formal channel for reporting support issues. | 5.0.0-5.15.1 | |
 | <a name="4789097"></a> [4789097](#4789097) <a name="4789097"></a> <br /> | The switch deletes a static blackhole route even when the blackhole type specified in the delete command does not match the configured type. | 5.9.4-5.15.1 | |
 | <a name="4771521"></a> [4771521](#4771521) <a name="4771521"></a> <br /> | Layer 3 multicast traffic does not forward when OMF (Optimized Multicast Flooding) and PIM is enabled. To work around this issue, flap the router port. | 5.9.2-5.15.1 | |
+| <a name="4717753"></a> [4717753](#4717753) <a name="4717753"></a> <br /> | When you add or remove routes in a virtual router with numerous configured routes, you might see incorrect routing of certain IP addresses. This can result in packets exiting through incorrect ports or being discarded. | 5.3.1-5.15.1 | |
 | <a name="4714845"></a> [4714845](#4714845) <a name="4714845"></a> <br /> | The switch installs suboptimal routes in the routing table and advertises them out. | 5.9.2-5.15.1 | |
 | <a name="4647646"></a> [4647646](#4647646) <a name="4647646"></a> <br /> | If you configure policy-based routing (PBR) rules for more than 32 interfaces, only the rules assigned to the first 32 interfaces are installed in the kernel.  | 4.4.2-5.14.0 | 5.15.0-5.15.1|
 | <a name="4637200"></a> [4637200](#4637200) <a name="4637200"></a> <br /> | When more than one IPv4 and/or IPv6 addresses are configured on a remote interface, NVUE LLDP commands such as <code>nv show interface lldp-detail</code> only reflect one address. To work around this issue, use <code>lldpctl</code> to view LLDP information. For example, <code>sudo lldpctl -d -f json swp1</code>.  | 5.9.0-5.14.0 | 5.15.0-5.15.1|
@@ -73,7 +74,7 @@ pdfhidden: True
 | <a name="4049213"></a> [4049213](#4049213) <a name="4049213"></a> <br /> | When there are routes that point to a single next hop, an ECMP entry is created in the SDK. After the single next hop from the route is removed, the ECMP entry might stay in the SDK until the time the next hop is present in the kernel. | 5.9.2-5.15.1 | |
 | <a name="4048583"></a> [4048583](#4048583) <a name="4048583"></a> <br /> | If there are failures in MSTPD or a port is not updated in the database, the NVUE <code>nv show bridge domain <bridge-id> stp</code> command might not work and might produce errors even when STP has data for other working ports or VLANs. This is a display issue only and does not impact functionality. | 5.10.0-5.12.1 | 5.13.0-5.15.1|
 | <a name="4047829"></a> [4047829](#4047829) <a name="4047829"></a> <br /> | Ports can be operationally down if the <code>switchd</code> service fails to come UP due to certain firmware failures and you the following <code>switchd.log</code> messages:<br><pre>PDDR long process T.O<br>MCIA no response<br>FW assert &#91;0x8C91&#93; detected</pre><br>To work around this issue, power-cycle the switch. | 5.10.0-5.10.1 | 5.11.0-5.15.1|
-| <a name="4047798"></a> [4047798](#4047798) <a name="4047798"></a> <br /> | Packet distribution based on ECMP hash is not working for VXLAN on top of rack switches where it is encapped. To work around this issue, enable lag hashing with gtp-teid to distribute the VXLAN encapped packets across egress interfaces. | 5.10.0-5.15.1 | |
+| <a name="4047798"></a> [4047798](#4047798) <a name="4047798"></a> <br /> | Packet distribution based on ECMP hashing using GTP-TEID does not function as expected in an EVPN Clos topology.  | 5.10.0-5.15.1 | |
 | <a name="4039850"></a> [4039850](#4039850) <a name="4039850"></a> <br /> | When the MAC address of the neighbor changes, a possible crash might occur because the pointer to which the MAC address points is freed, resulting in a dangling pointer. | 5.3.1-5.10.1 | 5.11.0-5.15.1|
 | <a name="4037315"></a> [4037315](#4037315) <a name="4037315"></a> <br /> | NVUE fails to enforce the password length limitation of 512 characters or fewer. | 5.10.0-5.10.1 | 5.11.0-5.15.1|
 | <a name="4030380"></a> [4030380](#4030380) <a name="4030380"></a> <br /> | When you roll back interface configuration to the default setting with the <code>nv unset interface</code> command, NVUE removes the complete entry for the interface from the <code>/etc/network/interface</code> file, and puts the interface in admin down. As a result, you cannot configure FEC on the interface at the lower layers. | 5.10.0-5.15.1 | |
@@ -176,6 +177,7 @@ pdfhidden: True
 | <a name="4797691"></a> [4797691](#4797691) <a name="4797691"></a> <br /> | The message that the switch displays when you generate a cl-support file or as a post login banner contains an invalid Cumulus Support email address, which is no longer the formal channel for reporting support issues. | 5.0.0-5.15.1 | |
 | <a name="4789097"></a> [4789097](#4789097) <a name="4789097"></a> <br /> | The switch deletes a static blackhole route even when the blackhole type specified in the delete command does not match the configured type. | 5.9.4-5.15.1 | |
 | <a name="4771521"></a> [4771521](#4771521) <a name="4771521"></a> <br /> | Layer 3 multicast traffic does not forward when OMF (Optimized Multicast Flooding) and PIM is enabled. To work around this issue, flap the router port. | 5.9.2-5.15.1 | |
+| <a name="4717753"></a> [4717753](#4717753) <a name="4717753"></a> <br /> | When you add or remove routes in a virtual router with numerous configured routes, you might see incorrect routing of certain IP addresses. This can result in packets exiting through incorrect ports or being discarded. | 5.3.1-5.15.1 | |
 | <a name="4714845"></a> [4714845](#4714845) <a name="4714845"></a> <br /> | The switch installs suboptimal routes in the routing table and advertises them out. | 5.9.2-5.15.1 | |
 | <a name="4647646"></a> [4647646](#4647646) <a name="4647646"></a> <br /> | If you configure policy-based routing (PBR) rules for more than 32 interfaces, only the rules assigned to the first 32 interfaces are installed in the kernel.  | 4.4.2-5.14.0 | 5.15.0-5.15.1|
 | <a name="4637200"></a> [4637200](#4637200) <a name="4637200"></a> <br /> | When more than one IPv4 and/or IPv6 addresses are configured on a remote interface, NVUE LLDP commands such as <code>nv show interface lldp-detail</code> only reflect one address. To work around this issue, use <code>lldpctl</code> to view LLDP information. For example, <code>sudo lldpctl -d -f json swp1</code>.  | 5.9.0-5.14.0 | 5.15.0-5.15.1|
@@ -228,7 +230,7 @@ pdfhidden: True
 | <a name="4049213"></a> [4049213](#4049213) <a name="4049213"></a> <br /> | When there are routes that point to a single next hop, an ECMP entry is created in the SDK. After the single next hop from the route is removed, the ECMP entry might stay in the SDK until the time the next hop is present in the kernel. | 5.9.2-5.15.1 | |
 | <a name="4048583"></a> [4048583](#4048583) <a name="4048583"></a> <br /> | If there are failures in MSTPD or a port is not updated in the database, the NVUE <code>nv show bridge domain <bridge-id> stp</code> command might not work and might produce errors even when STP has data for other working ports or VLANs. This is a display issue only and does not impact functionality. | 5.10.0-5.12.1 | 5.13.0-5.15.1|
 | <a name="4047829"></a> [4047829](#4047829) <a name="4047829"></a> <br /> | Ports can be operationally down if the <code>switchd</code> service fails to come UP due to certain firmware failures and you the following <code>switchd.log</code> messages:<br><pre>PDDR long process T.O<br>MCIA no response<br>FW assert &#91;0x8C91&#93; detected</pre><br>To work around this issue, power-cycle the switch. | 5.10.0-5.10.1 | 5.11.0-5.15.1|
-| <a name="4047798"></a> [4047798](#4047798) <a name="4047798"></a> <br /> | Packet distribution based on ECMP hash is not working for VXLAN on top of rack switches where it is encapped. To work around this issue, enable lag hashing with gtp-teid to distribute the VXLAN encapped packets across egress interfaces. | 5.10.0-5.15.1 | |
+| <a name="4047798"></a> [4047798](#4047798) <a name="4047798"></a> <br /> | Packet distribution based on ECMP hashing using GTP-TEID does not function as expected in an EVPN Clos topology.  | 5.10.0-5.15.1 | |
 | <a name="4043575"></a> [4043575](#4043575) <a name="4043575"></a> <br /> | If a ZTP script includes a directive to reboot, the reboot might stop the running ZTP process before it is able to disable itself from running again. As a result, the ZTP process starts again when the system comes back up. To work around this issue, run <code>shutdown -r +1</code> to schedule a reboot after one minute so that the ZTP process can successfully complete disabling the <code>ztp.service</code> systemd service. | 5.10.0-5.10.1 | 5.9.2, 5.11.0-5.15.1|
 | <a name="4042657"></a> [4042657](#4042657) <a name="4042657"></a> <br /> | The SDK times out with a FW FATAL health event, which requires a reboot of the system to recover.  | 5.9.1-5.10.0 | 5.10.1-5.15.1|
 | <a name="4042262"></a> [4042262](#4042262) <a name="4042262"></a> <br /> | The <code>switchd</code> service goes down and there is a FW Long Command Timeout. | 5.10.0 | 5.10.1-5.15.1|

content/cumulus-linux-510/rn.xml

@@ -31,6 +31,12 @@
 <td></td>
 </tr>
 <tr>
+<td>4717753</td>
+<td>When you add or remove routes in a virtual router with numerous configured routes, you might see incorrect routing of certain IP addresses. This can result in packets exiting through incorrect ports or being discarded.</td>
+<td>5.3.1-5.15.1</td>
+<td></td>
+</tr>
+<tr>
 <td>4714845</td>
 <td>The switch installs suboptimal routes in the routing table and advertises them out.</td>
 <td>5.9.2-5.15.1</td>
@@ -386,7 +392,7 @@ To work around this issue, power-cycle the switch.</td>
 </tr>
 <tr>
 <td>4047798</td>
-<td>Packet distribution based on ECMP hash is not working for VXLAN on top of rack switches where it is encapped. To work around this issue, enable lag hashing with gtp-teid to distribute the VXLAN encapped packets across egress interfaces.</td>
+<td>Packet distribution based on ECMP hashing using GTP-TEID does not function as expected in an EVPN Clos topology. </td>
 <td>5.10.0-5.15.1</td>
 <td></td>
 </tr>
@@ -985,6 +991,12 @@ cumulus@switch:~$ sudo ethtool -s swp1 speed 100000 autoneg off lanes 2
 <td></td>
 </tr>
 <tr>
+<td>4717753</td>
+<td>When you add or remove routes in a virtual router with numerous configured routes, you might see incorrect routing of certain IP addresses. This can result in packets exiting through incorrect ports or being discarded.</td>
+<td>5.3.1-5.15.1</td>
+<td></td>
+</tr>
+<tr>
 <td>4714845</td>
 <td>The switch installs suboptimal routes in the routing table and advertises them out.</td>
 <td>5.9.2-5.15.1</td>
@@ -1320,7 +1332,7 @@ To work around this issue, power-cycle the switch.</td>
 </tr>
 <tr>
 <td>4047798</td>
-<td>Packet distribution based on ECMP hash is not working for VXLAN on top of rack switches where it is encapped. To work around this issue, enable lag hashing with gtp-teid to distribute the VXLAN encapped packets across egress interfaces.</td>
+<td>Packet distribution based on ECMP hashing using GTP-TEID does not function as expected in an EVPN Clos topology. </td>
 <td>5.10.0-5.15.1</td>
 <td></td>
 </tr>