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

Changes by create-pull-request action

Author: mergify[bot]

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

@@ -51,6 +51,7 @@ pdfhidden: True
 | 4926427, 4926426 | When you run the <code>nv config apply</code> command or the <code>sudo systemctl reload frr.service</code> command on a switch configured with VRF route leaking that has many BGP peers, VRFs, and BGP learned prefixes, FRR reload might time out. To work around this issue, run <code>sudo systemctl edit frr.service</code> to change the <code>TimeoutSec=2m</code> to a higher value and apply the changes with <code>sudo systemctl daemon-reload</code>. | 5.15.0-5.16.1 | 5.9.5|
 | 4925514, 4919006 | Core processing services such as <code>cumulus-core.service</code> and <code>cumulus-core.path</code> might enter a failed state due to <code>systemd</code> start rate limiting caused by rapid start and stop cycles. This issue can prevent core files from being included in subsequent automatically generated cl-support collections even after you reactivate automatic cl-support generation after deactivation due to a chain of faults. Newly generated core files might accumulate, potentially leading to <code>/var</code> partition exhaustion. To recover from this condition, run the <code>sudo systemctl reset-failed cumulus-core.service cumulus-core.path</code> command. | 5.16.1 | |
 | 4925316 | Known registered multicast traffic is duplicated to receivers behind an EVPN-MH dual-homed access switch. | 5.16.0-5.16.1 | |
+| 4925207 | The graceful restart helper node experiences temporary traffic loss when the peer goes under warm boot. | 5.16.0-5.16.1 | |
 | 4924838 | When the a BGP neighbor is up for more than a day (24 hours), the uptime depicts correctly but the reset time which indicates the last connection reset time, does not account for the time elapsed past a day after the BGP neighbor resets. This is a display issue in NVUE; there is no direct traffic or functional impact. | 5.16.0-5.16.1 | |
 | 4924486, 4924487 | A fatal SDK event might occur during i2c or cable read events, observed with the following <code>switchd</code> log message:<br><pre>hal_mlx_host_ifc.c:3531 CRIT Restarting switchd to recover from fatal SDK health event: FW health issue</pre> | 5.12.1-5.16.1 | |
 | 4922188 | If you add a static default route, then delete it, the switch removes the default route in the ASIC. | 5.16.0-5.16.1 | |
@@ -286,6 +287,7 @@ pdfhidden: True
 | 4926427, 4926426 | When you run the <code>nv config apply</code> command or the <code>sudo systemctl reload frr.service</code> command on a switch configured with VRF route leaking that has many BGP peers, VRFs, and BGP learned prefixes, FRR reload might time out. To work around this issue, run <code>sudo systemctl edit frr.service</code> to change the <code>TimeoutSec=2m</code> to a higher value and apply the changes with <code>sudo systemctl daemon-reload</code>. | 5.15.0-5.16.1 | 5.9.5|
 | 4925515 | When you exceed the maximum number of ports allowed (30) in an 802.1x IPv6 profile, IPv6 addresses are not allocated to additional ports even if authentication is successful. To work around this issue, create additional profiles with the same configuration, associating no more than 30 interfaces to each profile. | 5.16.0 | 5.16.1|
 | 4925316 | Known registered multicast traffic is duplicated to receivers behind an EVPN-MH dual-homed access switch. | 5.16.0-5.16.1 | |
+| 4925207 | The graceful restart helper node experiences temporary traffic loss when the peer goes under warm boot. | 5.16.0-5.16.1 | |
 | 4924838 | When the a BGP neighbor is up for more than a day (24 hours), the uptime depicts correctly but the reset time which indicates the last connection reset time, does not account for the time elapsed past a day after the BGP neighbor resets. This is a display issue in NVUE; there is no direct traffic or functional impact. | 5.16.0-5.16.1 | |
 | 4924486, 4924487 | A fatal SDK event might occur during i2c or cable read events, observed with the following <code>switchd</code> log message:<br><pre>hal_mlx_host_ifc.c:3531 CRIT Restarting switchd to recover from fatal SDK health event: FW health issue</pre> | 5.12.1-5.16.1 | |
 | 4923828 | When cl-support files generate in quick succession due to a chain of faults, the cl-support files are not generated correctly. | 5.16.0 | 5.16.1|

content/cumulus-linux-516/rn.xml

@@ -241,6 +241,12 @@ nv config apply -y</td>
 <td></td>
 </tr>
 <tr>
+<td>4925207</td>
+<td>The graceful restart helper node experiences temporary traffic loss when the peer goes under warm boot.</td>
+<td>5.16.0-5.16.1</td>
+<td></td>
+</tr>
+<tr>
 <td>4924838</td>
 <td>When the a BGP neighbor is up for more than a day (24 hours), the uptime depicts correctly but the reset time which indicates the last connection reset time, does not account for the time elapsed past a day after the BGP neighbor resets. This is a display issue in NVUE; there is no direct traffic or functional impact.</td>
 <td>5.16.0-5.16.1</td>
@@ -1660,6 +1666,12 @@ ERR bulk_counter_transaction_set DISABLE failed: Driver's Return Status is Non-Z
 <td></td>
 </tr>
 <tr>
+<td>4925207</td>
+<td>The graceful restart helper node experiences temporary traffic loss when the peer goes under warm boot.</td>
+<td>5.16.0-5.16.1</td>
+<td></td>
+</tr>
+<tr>
 <td>4924838</td>
 <td>When the a BGP neighbor is up for more than a day (24 hours), the uptime depicts correctly but the reset time which indicates the last connection reset time, does not account for the time elapsed past a day after the BGP neighbor resets. This is a display issue in NVUE; there is no direct traffic or functional impact.</td>
 <td>5.16.0-5.16.1</td>