Merge branch 'test' into ania-stage

Author: cumulusAnia

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

@@ -229,7 +229,6 @@ pdfhidden: True
 | 4066219 | Some STP interfaces might remain in a blocking state when there are large numbers of discontiguous VLANs enabled on a port. | 5.8.0-5.9.3, 5.10.0-5.10.1 | 5.9.4, 5.11.0-5.15.1, 5.16.0-5.16.1|
 | 4065849 | A firmware upgrade on certain Innolight cables might get stuck or fail. | 5.10.0 | 5.10.1-5.15.1, 5.16.0-5.16.1|
 | 4065847 | Due to internal definition changes in Module firmware, ISSU on Spectrum-4 switches from earlier releases to Cumulus Linux 5.10.1 is not supported. | 5.10.0 | 5.10.1-5.15.1, 5.16.0-5.16.1|
-| 4062271, 4048679 | ASIC monitoring histogram collection might not work because of a crash in the <code>asic-monitor</code> service. To work around this issue, see the <a href="https://docs.nvidia.com/networking-ethernet-software/cumulus-linux-510/Whats-New/#release-considerations">Release Considerations section of the What’s New</a>. | 5.10.0 | 5.10.1-5.15.1, 5.16.0-5.16.1|
 | 4062001 | With VM migration from one VTEP to another, traffic loss might occur during a MAC move as locally learned MAC addresses are frequently refreshed in the kernel.  | 5.8.0-5.10.1 | 5.11.0-5.15.1, 5.16.0-5.16.1|
 | 4061534 | When you remove a secondary OTLP collector, there is a telemetry spike and existing connections with OTLP exporters reset. When new connections with the OTLP collector re-establish, the server experiences a high CPU and memory leak, which can bring down the telemetry collection service. | 5.10.0-5.10.1 | 5.11.0-5.15.1, 5.16.0-5.16.1|
 | 4052578 | When you perform a binary upgrade from Cumulus Linux 5.8 or earlier to 5.9.0 or later with a pre-staged <code>startup.yaml</code> file, the cumulus user password is reset to the default password because there is no default <code>startup.yaml</code> file present in 5.8.0 or earlier. To work around this issue, generate the <code>startup.yaml</code> file from the existing NVUE configuration.  | 5.9.2-5.11.5 | 5.12.0-5.15.1, 5.16.0-5.16.1|
@@ -239,18 +238,19 @@ pdfhidden: True
 | 4048583 | 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, 5.16.0-5.16.1|
 | 4047829, 4040901, 4040916 | 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, 5.16.0-5.16.1|
 | 4047798 | 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, 5.16.0-5.16.1 | |
-| 4043575 | 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.9.2, 5.10.1-5.15.1, 5.16.0-5.16.1|
 | 4042657 | 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, 5.16.0-5.16.1|
 | 4042262 | The <code>switchd</code> service goes down and there is a FW Long Command Timeout. | 5.10.0 | 5.10.1-5.15.1, 5.16.0-5.16.1|
 | 4040024 | After network churn, the <code>watchfrr</code> process might restart FRR because zebra is unresponsive. | 5.9.1-5.10.0 | 5.10.1-5.15.1, 5.16.0-5.16.1|
 | 4039850 | 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, 5.16.0-5.16.1|
 | 4037462 | The Open telemetry interface statistic description for <code>nvswitch_histogram_interface_egress_buffer</code> has a typographical error; engress should be egress. | 5.10.0 | 5.10.1-5.15.1, 5.16.0-5.16.1|
 | 4037315 | 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, 5.16.0-5.16.1|
+| 4037224, 4048679 | ASIC monitoring histogram collection might not work because of a crash in the <code>asic-monitor</code> service. To work around this issue, see the <a href="https://docs.nvidia.com/networking-ethernet-software/cumulus-linux-510/Whats-New/#release-considerations">Release Considerations section of the What’s New</a>. | 5.10.0 | 5.10.1-5.15.1, 5.11.0-5.15.1, 5.16.0-5.16.1|
 | 4030380 | 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, 5.16.0-5.16.1 | |
 | 4023318 | If you run <code>nv set</code> commands after you perform an upgrade but before a reboot, NVUE creates a revision based off the pre-upgrade version. After reboot, the revision contains pre-upgrade data that might cause it to fail during <code>config apply</code>.  To work around this issue, detach the stale revision after upgrade with the <code>nv config detach</code> command. | 5.10.0-5.10.1 | 5.11.0-5.15.1, 5.16.0-5.16.1|
 | 4022906 | If you use NVUE to configure a bond, apply a port mirror on the bond, then run the <code>nv config apply</code> command, the validation fails.<br>To work around this issue, configure the bond with a separate <code>nv config apply</code> command before you configure the port mirror on the bond. | 5.10.0-5.10.1 | 5.11.0-5.15.1, 5.16.0-5.16.1|
 | 4019257 | Some switches start booting but stop at the boot menu because console‑port noise is misinterpreted as input. | 5.9.1-5.10.1 | 5.11.0-5.15.1, 5.16.0-5.16.1|
 | 4019256 | If you change  the switch hostname, the histogram data producer service restarts. | 5.10.0-5.12.1 | 5.13.0-5.15.1, 5.16.0-5.16.1|
+| 4016216 | 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.9.2, 5.10.1-5.15.1, 5.11.0-5.15.1, 5.16.0-5.16.1|
 | 4005422, 4015452 | When you upgrade Cumulus Linux 5.9.1 to Cumulus Linux 5.10 or later with package upgrade, the NTP service stops. To restart the NTP service, enable, then restart the service in the VRF in which it was running with the <code>systemctl enable ntpsec&#64;<vrf></code> and <code>systemctl restart ntpsec&#64;<vrf></code> commands. | 5.10.0-5.15.1, 5.16.0-5.16.1 | |
 | 4004898 | When you configure the SNMP server listening address to a VRF that has no interfaces, <code>snmp.service</code> fails.<br>To recover from the failure, set the SNMP server listening address back to the VRF that has interfaces. If you really want to move the SNMP server to the VRF with no interfaces, assign an interface to the VRF and move the SNMP server to the VRF. | 5.10.0-5.10.1 | 5.9.4, 5.11.0-5.15.1, 5.16.0-5.16.1|
 | 3985682 | On Spectrum-4 switches, multicast flows containing packets smaller than 512 bytes might not reach full line rate. Cumulus Linux supports 512 byte and larger multicast packets. | 5.10.0-5.15.1, 5.16.0-5.16.1 | |

content/cumulus-linux-510/rn.xml

@@ -1317,12 +1317,6 @@ Save the file, run the {{nv config patch vlan-aware_bridge_snippet.yaml}} comman
 <td>5.10.1-5.15.1, 5.16.0-5.16.1</td>
 </tr>
 <tr>
-<td>4062271, 4048679</td>
-<td>ASIC monitoring histogram collection might not work because of a crash in the {{asic-monitor}} service. To work around this issue, see the &lt;a href="https://docs.nvidia.com/networking-ethernet-software/cumulus-linux-510/Whats-New/#release-considerations"&gt;Release Considerations section of the What’s New&lt;/a&gt;.</td>
-<td>5.10.0</td>
-<td>5.10.1-5.15.1, 5.16.0-5.16.1</td>
-</tr>
-<tr>
 <td>4062001</td>
 <td>With VM migration from one VTEP to another, traffic loss might occur during a MAC move as locally learned MAC addresses are frequently refreshed in the kernel. </td>
 <td>5.8.0-5.10.1</td>
@@ -1385,12 +1379,6 @@ To work around this issue, power-cycle the switch.</td>
 <td></td>
 </tr>
 <tr>
-<td>4043575</td>
-<td>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 {{shutdown -r +1}} to schedule a reboot after one minute so that the ZTP process can successfully complete disabling the {{ztp.service}} systemd service.</td>
-<td>5.10.0</td>
-<td>5.9.2, 5.10.1-5.15.1, 5.16.0-5.16.1</td>
-</tr>
-<tr>
 <td>4042657</td>
 <td>The SDK times out with a FW FATAL health event, which requires a reboot of the system to recover. 
 </td>
@@ -1428,6 +1416,12 @@ To work around this issue, power-cycle the switch.</td>
 <td>5.11.0-5.15.1, 5.16.0-5.16.1</td>
 </tr>
 <tr>
+<td>4037224, 4048679</td>
+<td>ASIC monitoring histogram collection might not work because of a crash in the {{asic-monitor}} service. To work around this issue, see the &lt;a href="https://docs.nvidia.com/networking-ethernet-software/cumulus-linux-510/Whats-New/#release-considerations"&gt;Release Considerations section of the What’s New&lt;/a&gt;.</td>
+<td>5.10.0</td>
+<td>5.10.1-5.15.1, 5.11.0-5.15.1, 5.16.0-5.16.1</td>
+</tr>
+<tr>
 <td>4030380</td>
 <td>When you roll back interface configuration to the default setting with the {{nv unset interface}} command, NVUE removes the complete entry for the interface from the {{/etc/network/interface}} file, and puts the interface in admin down. As a result, you cannot configure FEC on the interface at the lower layers.</td>
 <td>5.10.0-5.15.1, 5.16.0-5.16.1</td>
@@ -1458,6 +1452,12 @@ To work around this issue, power-cycle the switch.</td>
 <td>5.13.0-5.15.1, 5.16.0-5.16.1</td>
 </tr>
 <tr>
+<td>4016216</td>
+<td>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 {{shutdown -r +1}} to schedule a reboot after one minute so that the ZTP process can successfully complete disabling the {{ztp.service}} systemd service.</td>
+<td>5.10.0</td>
+<td>5.9.2, 5.10.1-5.15.1, 5.11.0-5.15.1, 5.16.0-5.16.1</td>
+</tr>
+<tr>
 <td>4005422, 4015452</td>
 <td>When you upgrade Cumulus Linux 5.9.1 to Cumulus Linux 5.10 or later with package upgrade, the NTP service stops. To restart the NTP service, enable, then restart the service in the VRF in which it was running with the {{systemctl enable ntpsec@&lt;vrf&gt;}} and {{systemctl restart ntpsec@&lt;vrf&gt;}} commands.</td>
 <td>5.10.0-5.15.1, 5.16.0-5.16.1</td>