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

Changes by create-pull-request action

Author: mergify[bot]

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

@@ -20,7 +20,7 @@ pdfhidden: True
 | <a name="4895247"></a> [4895247](#4895247) <a name="4895247"></a> <br /> | PTM does not refresh certain entries and the PTM's neighbor status command (ptmctl -d) continues to show a neighbor that is already gone. This condition clears when the expected neighbor gets discovered. | 5.15.1-5.16.1 | |
 | <a name="4889939"></a> [4889939](#4889939) <a name="4889939"></a> <br /> | In an MLAG configuration, when the MLAG node receives MLAG peer keepalives from an IP address that is not configured as the peer IP address, a peer IP address mismatch conflict occurs. Even after the conflict is resolved,  you sometimes see that the MLAG session still retains the peer IP mismatch conflict. | 5.14.0-5.16.1 | |
 | <a name="4885553"></a> [4885553](#4885553) <a name="4885553"></a> <br /> | If ZTP uses a proxy server for image download using <code>onie-install</code>, the image install fails with signing issues. | 5.12.0-5.16.1 | |
-| <a name="4885474"></a> [4885474](#4885474) <a name="4885474"></a> <br /> | During warm boot, a transient error "ERR Failed to enable ipv4-mc for VRF tbl-id:0 vr-id:1" appears in the <code>switchd</code> log. You can ignore this error; VRF configuration is not affected. | 5.16.0-5.16.1 | |
+| <a name="4885474"></a> [4885474](#4885474) <a name="4885474"></a> <br /> | During warm boot, a transient error <code>ERR Failed to enable ipv4-mc for VRF tbl-id:0 vr-id:1</code> appears in the <code>switchd</code> log. You can ignore this error; VRF configuration is not affected. | 5.16.0-5.16.1 | |
 | <a name="4882392"></a> [4882392](#4882392) <a name="4882392"></a> <br /> | If you run the <code>nv show evpn access-vlan-info vlan</code>  command after deleting a bond interface, which is part of a bridge, the server encounters an internal error.  | 5.9.1-5.16.1 | |
 | <a name="4879165"></a> [4879165](#4879165) <a name="4879165"></a> <br /> | When you configure dynamic NAT and traffic enters the switch on a bridge port that is routed through a VLAN SVI (the standard MLAG bridge topology), NAT flows are not offloaded to the ASIC. An upstream kernel change clears an internal flag during the bridge-to-host handoff that the NAT offload path depends on to signal the hardware. As a result, all dynamic NAT flows fall back to software forwarding on the CPU, reducing throughput by over 99%. Static NAT and deployments using direct layer 3 ports (no bridge) are not affected. | 5.14.0-5.16.1 | |
 | <a name="4875640"></a> [4875640](#4875640) <a name="4875640"></a> <br /> | A rare timing scenario results in the following error log in <code>switchd</code>:<br><pre>ERR bulk_counter_transaction_set DISABLE failed: Driver's Return Status is Non-Zero</pre> | 5.16.0-5.16.1 | |
@@ -161,6 +161,7 @@ pdfhidden: True
 | <a name="4923647"></a> [4923647](#4923647) <a name="4923647"></a> <br /> | The graceful restart helper node experiences temporary traffic loss when the peer goes under warm boot. | 5.16.0 | |
 | <a name="4923036"></a> [4923036](#4923036) <a name="4923036"></a> <br /> | When an SDK health monitoring or <code>switchd</code> watchdog event occurs, the switch might generate the following error message and does not recover automatically:<br><pre>hal_mlx_port.c:3919 ERR port state set failed for port <#>: Driver's Return Status is Non-Zero </pre> | 5.16.0 | |
 | <a name="4922108"></a> [4922108](#4922108) <a name="4922108"></a> <br /> | The vtysh <code>show bgp ipv4 unreachability <prefix> json</code> and <code>show bgp ipv6 unreachability <prefix> json</code> commands do not display BGP community attributes (including <code>graceful-shutdown</code>) in the JSON output even though they are shown correctly in the non-JSON text output.<br>Network automation tools and scripts relying on JSON output might not detect the <code>graceful-shutdown</code> community on unreachability routes, making it difficult to identify routes that are withdrawn due to graceful shutdown procedures. | 5.16.0 | |
+| <a name="4922106"></a> [4922106](#4922106) <a name="4922106"></a> <br /> | The NVUE <code>nv show system dot1x ipv6-profile</code> command does not show the correct <code>preserve-on-link-down</code> status. To work around this issue, use the <code>--applied</code> option (<code>nv show system dot1x ipv6-profile --applied</code>). | 5.16.0 | |
 | <a name="4922105"></a> [4922105](#4922105) <a name="4922105"></a> <br /> | The JSON output for the vtysh <code>show bgp <address-family> unreachability> summary</code> reports peers as <code>Established</code> even when the AFI or SAFI is not negotiated, while the plain summary shows <code>NoNeg</code>. This causes JSON to misrepresent  the per‑AFI or SAFI state for established sessions. | 5.16.0 | |
 | <a name="4922104"></a> [4922104](#4922104) <a name="4922104"></a> <br /> | When the system is under load and the <code>wd_keepalive</code> process is running at the default rate of one time per minute, the switch might reboot due to starvation of the <code>wd_keepalive</code> process. | 5.13.1-5.16.0 | |
 | <a name="4922099"></a> [4922099](#4922099) <a name="4922099"></a> <br /> | In a highly volatile network, frequent churn of SOO‑tagged routes can generate a large volume of SOO NHG sync messages to Zebra. When Zebra becomes congested while processing these NHG updates, its memory usage can grow significantly. | 5.14.0-5.16.0 | |
@@ -181,6 +182,7 @@ pdfhidden: True
 | <a name="4923647"></a> [4923647](#4923647) <a name="4923647"></a> <br /> | The graceful restart helper node experiences temporary traffic loss when the peer goes under warm boot. | 5.16.0 | |
 | <a name="4923036"></a> [4923036](#4923036) <a name="4923036"></a> <br /> | When an SDK health monitoring or <code>switchd</code> watchdog event occurs, the switch might generate the following error message and does not recover automatically:<br><pre>hal_mlx_port.c:3919 ERR port state set failed for port <#>: Driver's Return Status is Non-Zero </pre> | 5.16.0 | |
 | <a name="4922108"></a> [4922108](#4922108) <a name="4922108"></a> <br /> | The vtysh <code>show bgp ipv4 unreachability <prefix> json</code> and <code>show bgp ipv6 unreachability <prefix> json</code> commands do not display BGP community attributes (including <code>graceful-shutdown</code>) in the JSON output even though they are shown correctly in the non-JSON text output.<br>Network automation tools and scripts relying on JSON output might not detect the <code>graceful-shutdown</code> community on unreachability routes, making it difficult to identify routes that are withdrawn due to graceful shutdown procedures. | 5.16.0 | |
+| <a name="4922106"></a> [4922106](#4922106) <a name="4922106"></a> <br /> | The NVUE <code>nv show system dot1x ipv6-profile</code> command does not show the correct <code>preserve-on-link-down</code> status. To work around this issue, use the <code>--applied</code> option (<code>nv show system dot1x ipv6-profile --applied</code>). | 5.16.0 | |
 | <a name="4922105"></a> [4922105](#4922105) <a name="4922105"></a> <br /> | The JSON output for the vtysh <code>show bgp <address-family> unreachability> summary</code> reports peers as <code>Established</code> even when the AFI or SAFI is not negotiated, while the plain summary shows <code>NoNeg</code>. This causes JSON to misrepresent  the per‑AFI or SAFI state for established sessions. | 5.16.0 | |
 | <a name="4922104"></a> [4922104](#4922104) <a name="4922104"></a> <br /> | When the system is under load and the <code>wd_keepalive</code> process is running at the default rate of one time per minute, the switch might reboot due to starvation of the <code>wd_keepalive</code> process. | 5.13.1-5.16.0 | |
 | <a name="4922099"></a> [4922099](#4922099) <a name="4922099"></a> <br /> | In a highly volatile network, frequent churn of SOO‑tagged routes can generate a large volume of SOO NHG sync messages to Zebra. When Zebra becomes congested while processing these NHG updates, its memory usage can grow significantly. | 5.14.0-5.16.0 | |
@@ -193,7 +195,7 @@ pdfhidden: True
 | <a name="4895247"></a> [4895247](#4895247) <a name="4895247"></a> <br /> | PTM does not refresh certain entries and the PTM's neighbor status command (ptmctl -d) continues to show a neighbor that is already gone. This condition clears when the expected neighbor gets discovered. | 5.15.1-5.16.0 | |
 | <a name="4889939"></a> [4889939](#4889939) <a name="4889939"></a> <br /> | In an MLAG configuration, when the MLAG node receives MLAG peer keepalives from an IP address that is not configured as the peer IP address, a peer IP address mismatch conflict occurs. Even after the conflict is resolved,  you sometimes see that the MLAG session still retains the peer IP mismatch conflict. | 5.14.0-5.16.0 | |
 | <a name="4885553"></a> [4885553](#4885553) <a name="4885553"></a> <br /> | If ZTP uses a proxy server for image download using <code>onie-install</code>, the image install fails with signing issues. | 5.12.0-5.16.0 | |
-| <a name="4885474"></a> [4885474](#4885474) <a name="4885474"></a> <br /> | During warm boot, a transient error "ERR Failed to enable ipv4-mc for VRF tbl-id:0 vr-id:1" appears in the <code>switchd</code> log. You can ignore this error; VRF configuration is not affected. | 5.16.0 | |
+| <a name="4885474"></a> [4885474](#4885474) <a name="4885474"></a> <br /> | During warm boot, a transient error <code>ERR Failed to enable ipv4-mc for VRF tbl-id:0 vr-id:1</code> appears in the <code>switchd</code> log. You can ignore this error; VRF configuration is not affected. | 5.16.0 | |
 | <a name="4882392"></a> [4882392](#4882392) <a name="4882392"></a> <br /> | If you run the <code>nv show evpn access-vlan-info vlan</code>  command after deleting a bond interface, which is part of a bridge, the server encounters an internal error.  | 5.9.1-5.16.0 | |
 | <a name="4879165"></a> [4879165](#4879165) <a name="4879165"></a> <br /> | When you configure dynamic NAT and traffic enters the switch on a bridge port that is routed through a VLAN SVI (the standard MLAG bridge topology), NAT flows are not offloaded to the ASIC. An upstream kernel change clears an internal flag during the bridge-to-host handoff that the NAT offload path depends on to signal the hardware. As a result, all dynamic NAT flows fall back to software forwarding on the CPU, reducing throughput by over 99%. Static NAT and deployments using direct layer 3 ports (no bridge) are not affected. | 5.14.0-5.16.0 | |
 | <a name="4875640"></a> [4875640](#4875640) <a name="4875640"></a> <br /> | A rare timing scenario results in the following error log in <code>switchd</code>:<br><pre>ERR bulk_counter_transaction_set DISABLE failed: Driver's Return Status is Non-Zero</pre> | 5.16.0 | |

content/cumulus-linux-516/rn.xml

@@ -46,7 +46,7 @@
 </tr>
 <tr>
 <td>4885474</td>
-<td>During warm boot, a transient error "ERR Failed to enable ipv4-mc for VRF tbl-id:0 vr-id:1" appears in the {{switchd}} log. You can ignore this error; VRF configuration is not affected.</td>
+<td>During warm boot, a transient error {{ERR Failed to enable ipv4-mc for VRF tbl-id:0 vr-id:1}} appears in the {{switchd}} log. You can ignore this error; VRF configuration is not affected.</td>
 <td>5.16.0-5.16.1</td>
 <td></td>
 </tr>
@@ -935,6 +935,11 @@ hal_mlx_port.c:3919 ERR port state set failed for port &lt;#&gt;: Driver's Retur
 <td>5.16.0</td>
 </tr>
 <tr>
+<td>4922106</td>
+<td>The NVUE {{nv show system dot1x ipv6-profile}} command does not show the correct {{preserve-on-link-down}} status. To work around this issue, use the {{--applied}} option ({{nv show system dot1x ipv6-profile --applied}}).</td>
+<td>5.16.0</td>
+</tr>
+<tr>
 <td>4922105</td>
 <td>The JSON output for the vtysh {{show bgp &lt;address-family&gt; unreachability&gt; summary}} reports peers as {{Established}} even when the AFI or SAFI is not negotiated, while the plain summary shows {{NoNeg}}. This causes JSON to misrepresent  the per‑AFI or SAFI state for established sessions.</td>
 <td>5.16.0</td>
@@ -1021,6 +1026,12 @@ hal_mlx_port.c:3919 ERR port state set failed for port &lt;#&gt;: Driver's Retur
 <td></td>
 </tr>
 <tr>
+<td>4922106</td>
+<td>The NVUE {{nv show system dot1x ipv6-profile}} command does not show the correct {{preserve-on-link-down}} status. To work around this issue, use the {{--applied}} option ({{nv show system dot1x ipv6-profile --applied}}).</td>
+<td>5.16.0</td>
+<td></td>
+</tr>
+<tr>
 <td>4922105</td>
 <td>The JSON output for the vtysh {{show bgp &lt;address-family&gt; unreachability&gt; summary}} reports peers as {{Established}} even when the AFI or SAFI is not negotiated, while the plain summary shows {{NoNeg}}. This causes JSON to misrepresent  the per‑AFI or SAFI state for established sessions.</td>
 <td>5.16.0</td>
@@ -1096,7 +1107,7 @@ hal_mlx_port.c:3919 ERR port state set failed for port &lt;#&gt;: Driver's Retur
 </tr>
 <tr>
 <td>4885474</td>
-<td>During warm boot, a transient error "ERR Failed to enable ipv4-mc for VRF tbl-id:0 vr-id:1" appears in the {{switchd}} log. You can ignore this error; VRF configuration is not affected.</td>
+<td>During warm boot, a transient error {{ERR Failed to enable ipv4-mc for VRF tbl-id:0 vr-id:1}} appears in the {{switchd}} log. You can ignore this error; VRF configuration is not affected.</td>
 <td>5.16.0</td>
 <td></td>
 </tr>