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

Changes by create-pull-request action

content/cumulus-linux-510/rn.xml

@@ -7,12 +7,48 @@
 <th> Fixed </th>
 </tr>
 <tr>
+<td>4037224</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></td>
+</tr>
+<tr>
+<td>4035681</td>
+<td>The {{nv show interface &lt;interface&gt;}} commands show RX and TX Power values from the wrong lanes on breakout ports.</td>
+<td>5.8.0-5.10.0</td>
+<td></td>
+</tr>
+<tr>
+<td>4023318</td>
+<td>If you run {{nv set}} 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 {{config apply}}.  To work around this issue, detach the stale revision after upgrade with the {{nv config detach}} command.</td>
+<td>5.10.0</td>
+<td></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></td>
+</tr>
+<tr>
+<td>4007613</td>
+<td>If there are multiple relay switches in the path reaching the DHCP server, DHCP packets are duplicated at each transit relay switch and the server receives duplicate packets.</td>
+<td>5.9.1-5.10.0</td>
+<td></td>
+</tr>
+<tr>
 <td>4005422</td>
 <td>When you upgrade Cumulus Linux 5.9.1 to Cumulus Linux 5.10 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</td>
 <td></td>
 </tr>
 <tr>
+<td>4005261</td>
+<td> On a Spectrum-4 switch, if you use PTP on a 800G link, jumbo frames traversing the same link might cause a degradation in PTP performance.</td>
+<td>5.9.0-5.10.0</td>
+<td></td>
+</tr>
+<tr>
 <td>4004898</td>
 <td>When you configure the SNMP server listening address to a VRF that has no interfaces, {{snmp.service}} fails.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.</td>
 <td>5.10.0</td>
@@ -40,6 +76,12 @@ To work around this issue, use the {{-q}} option with {{wget}}.</td>
 <td></td>
 </tr>
 <tr>
+<td>3861745</td>
+<td>On UEFI hardware (where the {{/sys/firmware/efi}} directory exists), using the update-grub program might generate a {{/boot/grub/grub.cfg}} that is incorrect for booting ONIE if the ONIE option is selected on the console while booting. To work around this issue, run {{mount LABEL="EFI System" /boot/efi}} before using update-grub.</td>
+<td>5.9.0-5.10.0</td>
+<td></td>
+</tr>
+<tr>
 <td>3844670</td>
 <td>When you configure TACACS with NVUE or merge in an NVUE configuration file including TACACS configuration with the {{nv config patch}} command, you see an unrecoverable error when running additional NVUE commands. To work around this issue, restart the NVUE service with the {{systemctl restart nvued.service}} command.</td>
 <td>5.9.0-5.10.0</td>
@@ -364,6 +406,11 @@ Fixed: 2.6.0+dfsg.1-1+deb10u1</td>
 <th> Affects </th>
 </tr>
 <tr>
+<td>4023637</td>
+<td>When you disable dynamic NAT manually in the {{/etc/cumulus/switchd.conf}} file instead of using NVUE commands but the dynamic NAT rules still exist in the {{/etc/cumulus/acl/policy,d/.rules}} file, the switch encounters a memory leak. To work around this issue, remove dynamic NAT rules in rules files in {{/etc/cumulus/acl/policy.d}} before you disable dynamic NAT in the {{/etc/cumulus/switchd.conf}} file.</td>
+<td>5.9.0-5.9.1</td>
+</tr>
+<tr>
 <td>4015327</td>
 <td>If you change the hostname in the {{/etc/hostname}} file after the {{asic_monitor@vrf}} service starts, the hostname  is not reflected in the Open Telemetry  exported resource attribute. To work around this issue, restart the {{asic_monitor@vrf}} service.</td>
 <td></td>
@@ -411,7 +458,7 @@ kernel: RIP: 0010:__nf_conntrack_confirm+0x5c7/0x6b0 [nf_conntrack]</td>
 </tr>
 <tr>
 <td>3966673</td>
-<td>In an EVPN multihoming configuration, if you enable multihoming without any local ESI configuration, {{arp-nd-redirect}} remains disabled unless you restart FRR with the {{sudo systemctl restart frr.service}} command.</td>
+<td>In an EVPN multihoming deployment, if you enable multihoming without any local ESI configuration, {{arp-nd-redirect}} remains disabled unless you restart FRR.</td>
 <td>5.9.1</td>
 </tr>
 <tr>
@@ -491,7 +538,7 @@ kernel: RIP: 0010:__nf_conntrack_confirm+0x5c7/0x6b0 [nf_conntrack]</td>
 </tr>
 <tr>
 <td>3927016</td>
-<td>Following an EVPN extended mobility event, where a host with IP address A and MAC address A moves within the fabric and now resides at IP address A and MAC address B, you might see traffic destined to this host experience drops as the flow is software forwarded on the egress VTEP.</td>
+<td>Following an EVPN extended mobility event, where a host with IPA and MACA moves within the fabric and now resides at IPA MACB, you might see traffic destined to this host experience drops as the flow is being software forwarded on the egress VTEP.</td>
 <td>5.9.1</td>
 </tr>
 <tr>
@@ -559,6 +606,11 @@ This issue occurs because {{poectl}} is called on non-PoE switches. To work arou
 <td>5.9.0-5.9.1</td>
 </tr>
 <tr>
+<td>3878166</td>
+<td>The NVUE {{nv show interface eth0}} and {{nv show vrf}} commands take more than two minutes to run if you have configured hundreds of interfaces because NVUE makes repetitive system calls to get {{vlan/link/tunnel}} bridge information.</td>
+<td>5.9.0-5.9.1</td>
+</tr>
+<tr>
 <td>3875589</td>
 <td>MLAG bonds might report an incorrect DOWN reason of {{lacp partner mac mismatch}} when the bond is out of service for another reason.</td>
 <td>5.9.0-5.9.1</td>
@@ -599,6 +651,18 @@ This issue occurs because {{poectl}} is called on non-PoE switches. To work arou
 <td>5.7.0-5.9.1</td>
 </tr>
 <tr>
+<td>3711913</td>
+<td>When you set an IPv4 ACL with a log action, logs do not appear under syslog after a match. This issue affects bridged packets when the rule is installed in iptables. To work around this issue, set the ACL with a MAC rule type so that it is installed in ebtables and the packets are logged correctly in {{syslog}}.The following shows an example configuration:
+cumulus@switch:~$ nv set acl one rule 1 action log log-prefix NVIDIA
+cumulus@switch:~$ nv set acl one rule 1 match ip protocol udp
+cumulus@switch:~$ nv set acl one rule 1 match ip source-ip 10.0.14.2
+cumulus@switch:~$ nv set acl one rule 1 match ip udp source-port 34
+cumulus@switch:~$ nv set acl one rule 1 match mac protocol ipv4
+cumulus@switch:~$ nv set acl one type mac
+</td>
+<td>5.7.0-5.9.1</td>
+</tr>
+<tr>
 <td>3636266</td>
 <td>When an unresolved next hop is present in a next hop group, especially over an SVI interface, the switch checks if the neighbor MAC address is in the forwarding table. If the neighbor's MAC address is not there, the switch skips this next hop from backend programming and you see the {{switchd}} error {{ERR NH: l3 nhg v6 l3 nhg contains one or more unresolvable nexthops}}. There is no impact to switch functionality as unresolved neighbors are not programmed in hardware until they are resolved.</td>
 <td>5.7.0-5.9.1</td>

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

@@ -43,6 +43,7 @@ pdfhidden: True
 | <a name="3713420"></a> [3713420](#3713420) <a name="3713420"></a> <br /> | When you run the <code>systemctl restart switchd.service</code> command or reboot the switch after you set the host route preference option with the NVUE <code>nv set system forwarding host-route-preference</code> command or manually in the <code>/etc/cumulus/switchd.conf</code> file, <code>switchd</code> crashes and creates core files. | 5.7.0 | 5.8.0-5.10.0|
 | <a name="3713419"></a> [3713419](#3713419) <a name="3713419"></a> <br /> | When monitoring system statistics and network traffic with sFlow, an aggressive link flap might produce a memory leak in the sFlow service <code>hsflowd</code>. | 5.1.0-5.7.0 | 5.8.0-5.10.0|
 | <a name="3712007"></a> [3712007](#3712007) <a name="3712007"></a> <br /> | In RSTP mode when there is a bridge port flap, Cumulus Linux flushes, then re-adds dynamic MAC addresses on the peer link, which might cause short traffic disruption. | 5.6.0-5.7.0 | 5.8.0-5.10.0|
+| <a name="3711913"></a> [3711913](#3711913) <a name="3711913"></a> <br /> | When you set an IPv4 ACL with a log action, logs do not appear under syslog after a match. This issue affects bridged packets when the rule is installed in iptables. To work around this issue, set the ACL with a MAC rule type so that it is installed in ebtables and the packets are logged correctly in <code>syslog</code>.<br>The following shows an example configuration:<br><pre>cumulus&#64;switch:~$ nv set acl one rule 1 action log log-prefix NVIDIAcumulus&#64;switch:~$ nv set acl one rule 1 match ip protocol udpcumulus&#64;switch:~$ nv set acl one rule 1 match ip source-ip 10.0.14.2cumulus&#64;switch:~$ nv set acl one rule 1 match ip udp source-port 34cumulus&#64;switch:~$ nv set acl one rule 1 match mac protocol ipv4cumulus&#64;switch:~$ nv set acl one type mac</pre> | 5.7.0-5.9.1 | 5.10.0|
 | <a name="3710396"></a> [3710396](#3710396) <a name="3710396"></a> <br /> | In an eBGP multihop configuration with dynamic neighbors, Cumulus Linux does not update the configured TTL but uses the MAXTTL instead. This issue is only observed with dynamic peers. | 5.6.0-5.7.0 | 5.8.0-5.10.0|
 | <a name="3702431"></a> [3702431](#3702431) <a name="3702431"></a> <br /> | Traditional SNMP snippets do not take effect unless you first enable SNMP with the NVUE <code>nv set service snmp-server enable on</code> and <code>nv set service snmp-server listening-address</code> commands. Alternatively, you can use the equivalent REST API methods. | 5.4.0-5.8.0 | 5.9.0-5.10.0|
 | <a name="3698680"></a> [3698680](#3698680) <a name="3698680"></a> <br /> | If you run the <code>ifreload -a</code> command when ACLs exist but nonatomic update mode is set in the <code>switchd.conf</code> file, traffic pauses on unaffected interfaces. | 5.6.0-5.7.0 | 5.8.0-5.10.0|

content/cumulus-linux-57/rn.xml

@@ -201,6 +201,19 @@ leaf01# exit</td>
 <td>5.8.0-5.10.0</td>
 </tr>
 <tr>
+<td>3711913</td>
+<td>When you set an IPv4 ACL with a log action, logs do not appear under syslog after a match. This issue affects bridged packets when the rule is installed in iptables. To work around this issue, set the ACL with a MAC rule type so that it is installed in ebtables and the packets are logged correctly in {{syslog}}.The following shows an example configuration:
+cumulus@switch:~$ nv set acl one rule 1 action log log-prefix NVIDIA
+cumulus@switch:~$ nv set acl one rule 1 match ip protocol udp
+cumulus@switch:~$ nv set acl one rule 1 match ip source-ip 10.0.14.2
+cumulus@switch:~$ nv set acl one rule 1 match ip udp source-port 34
+cumulus@switch:~$ nv set acl one rule 1 match mac protocol ipv4
+cumulus@switch:~$ nv set acl one type mac
+</td>
+<td>5.7.0-5.9.1</td>
+<td>5.10.0</td>
+</tr>
+<tr>
 <td>3710396</td>
 <td>In an eBGP multihop configuration with dynamic neighbors, Cumulus Linux does not update the configured TTL but uses the MAXTTL instead. This issue is only observed with dynamic peers.</td>
 <td>5.6.0-5.7.0</td>

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

@@ -14,8 +14,10 @@ pdfhidden: True
 
 |  Issue ID 	|   Description	|   Affects	|   Fixed |
 |---	        |---	        |---	    |---	                |
+| <a name="4035681"></a> [4035681](#4035681) <a name="4035681"></a> <br /> | The <code>nv show interface <interface></code> commands show RX and TX Power values from the wrong lanes on breakout ports. | 5.8.0-5.10.0 | |
 | <a name="4007614"></a> [4007614](#4007614) <a name="4007614"></a> <br />None | Static ARP configured with NVUE commands is deleted when the relevant layer 3 interface flaps. | 5.8.0-5.10.0 | |
 | <a name="4004453"></a> [4004453](#4004453) <a name="4004453"></a> <br />None | The NVUE commands to delete SNMP users, and change authentication passwords and encryption passphrases are not successful. | 4.3.0-4.4.5, 5.0.0-5.10.0 | |
+| <a name="3982242"></a> [3982242](#3982242) <a name="3982242"></a> <br /> | PTP does not come up with IPv6 over a trunk port because the IPv6 VLAN tag is not sent. PTP over an IPv4 trunk works fine. | 5.8.0-5.10.0 | |
 | <a name="3982222"></a> [3982222](#3982222) <a name="3982222"></a> <br /> | When SPAN is enabled on a bridge member, an ARP or Gratuitous ARP received during a failover event between locally attached redundant devices such as load balancers might fail to update the bridge MAC table to point to the interface with the newly active load balancer. | 5.4.0-5.10.0 | |
 | <a name="3970626"></a> [3970626](#3970626) <a name="3970626"></a> <br /> | When you configure the <code>bridge.kernel_mac_refresh_interval</code> parameter in the <code>switchd.conf</code> file, a <code>switchd</code> restart fails with core dump. | 5.8.0-5.9.1 | 5.10.0|
 | <a name="3956091"></a> [3956091](#3956091) <a name="3956091"></a> <br />None | When you modify the default QoS configuration on top of the base RoCE configuration, NVUE reports an <code>Invalid</code> exception in the <code>nv show qos roce</code> command output even when the configuration is valid. | 5.8.0-5.10.0 | |
@@ -60,6 +62,7 @@ pdfhidden: True
 | <a name="3739159"></a> [3739159](#3739159) <a name="3739159"></a> <br /> | Disabling adaptive routing globally or on interfaces and performing ISSU, has a significant traffic outage. The issue recovers after ISSU completes. | 5.7.0-5.10.0 | |
 | <a name="3739008"></a> [3739008](#3739008) <a name="3739008"></a> <br /> | The Lenovo MSN4600-VS2RC (PN SSG7B27990 Back-to-Front/C2P Airflow) might run the fan tray fans at a high speed because the software believes the PSU fans are running in the wrong direction. | 5.5.1-5.8.0 | 5.9.0-5.10.0|
 | <a name="3730904"></a> [3730904](#3730904) <a name="3730904"></a> <br /> | When sending untagged frames to the CPU with an MTU higher than the SVD (single VXLAN device) MTU, the kernel might crash. | 5.4.0-5.8.0 | 5.9.0-5.10.0|
+| <a name="3711913"></a> [3711913](#3711913) <a name="3711913"></a> <br /> | When you set an IPv4 ACL with a log action, logs do not appear under syslog after a match. This issue affects bridged packets when the rule is installed in iptables. To work around this issue, set the ACL with a MAC rule type so that it is installed in ebtables and the packets are logged correctly in <code>syslog</code>.<br>The following shows an example configuration:<br><pre>cumulus&#64;switch:~$ nv set acl one rule 1 action log log-prefix NVIDIAcumulus&#64;switch:~$ nv set acl one rule 1 match ip protocol udpcumulus&#64;switch:~$ nv set acl one rule 1 match ip source-ip 10.0.14.2cumulus&#64;switch:~$ nv set acl one rule 1 match ip udp source-port 34cumulus&#64;switch:~$ nv set acl one rule 1 match mac protocol ipv4cumulus&#64;switch:~$ nv set acl one type mac</pre> | 5.7.0-5.9.1 | 5.10.0|
 | <a name="3702431"></a> [3702431](#3702431) <a name="3702431"></a> <br /> | Traditional SNMP snippets do not take effect unless you first enable SNMP with the NVUE <code>nv set service snmp-server enable on</code> and <code>nv set service snmp-server listening-address</code> commands. Alternatively, you can use the equivalent REST API methods. | 5.4.0-5.8.0 | 5.9.0-5.10.0|
 | <a name="3685007"></a> [3685007](#3685007) <a name="3685007"></a> <br /> | Cumulus Linux does not support 802.1X dynamic VLANs on PEAP with MS Windows-based supplicants. | 5.7.0-5.10.0 | |
 | <a name="3679478"></a> [3679478](#3679478) <a name="3679478"></a> <br /> | During switch boot, you see the following messages in the syslog:<br><pre>2024-03-04T10:34:49.650950+00:00 cumulus sx_sdk: 2262 &#91;TELE&#93; &#91;ERROR  &#93;: Tele impl module is already initialized2024-03-04T10:34:49.651041+00:00 cumulus sx_sdk: 2262 &#91;TELE&#93; &#91;ERROR  &#93;: sdk_tele_init failed, for chip type CHIP_TYPE_SWITCH_SPECTRUM3, err = Already initialized</pre><br>This is due to both the ASIC Monitoring service and the What Just Happened (WJH) service trying to initialize the SDK TELE module. You can ignore the messages because the TELE service has already initialized properly. | 5.7.0-5.8.0 | 5.9.0-5.10.0|

content/cumulus-linux-58/rn.xml

@@ -7,6 +7,12 @@
 <th> Fixed </th>
 </tr>
 <tr>
+<td>4035681</td>
+<td>The {{nv show interface &lt;interface&gt;}} commands show RX and TX Power values from the wrong lanes on breakout ports.</td>
+<td>5.8.0-5.10.0</td>
+<td></td>
+</tr>
+<tr>
 <td>4007614</td>
 <td>Static ARP configured with NVUE commands is deleted when the relevant layer 3 interface flaps.</td>
 <td>5.8.0-5.10.0</td>
@@ -19,6 +25,12 @@
 <td></td>
 </tr>
 <tr>
+<td>3982242</td>
+<td>PTP does not come up with IPv6 over a trunk port because the IPv6 VLAN tag is not sent. PTP over an IPv4 trunk works fine.</td>
+<td>5.8.0-5.10.0</td>
+<td></td>
+</tr>
+<tr>
 <td>3982222</td>
 <td>When SPAN is enabled on a bridge member, an ARP or Gratuitous ARP received during a failover event between locally attached redundant devices such as load balancers might fail to update the bridge MAC table to point to the interface with the newly active load balancer.</td>
 <td>5.4.0-5.10.0</td>
@@ -307,6 +319,19 @@ leaf01# exit</td>
 <td>5.9.0-5.10.0</td>
 </tr>
 <tr>
+<td>3711913</td>
+<td>When you set an IPv4 ACL with a log action, logs do not appear under syslog after a match. This issue affects bridged packets when the rule is installed in iptables. To work around this issue, set the ACL with a MAC rule type so that it is installed in ebtables and the packets are logged correctly in {{syslog}}.The following shows an example configuration:
+cumulus@switch:~$ nv set acl one rule 1 action log log-prefix NVIDIA
+cumulus@switch:~$ nv set acl one rule 1 match ip protocol udp
+cumulus@switch:~$ nv set acl one rule 1 match ip source-ip 10.0.14.2
+cumulus@switch:~$ nv set acl one rule 1 match ip udp source-port 34
+cumulus@switch:~$ nv set acl one rule 1 match mac protocol ipv4
+cumulus@switch:~$ nv set acl one type mac
+</td>
+<td>5.7.0-5.9.1</td>
+<td>5.10.0</td>
+</tr>
+<tr>
 <td>3702431</td>
 <td>Traditional SNMP snippets do not take effect unless you first enable SNMP with the NVUE {{nv set service snmp-server enable on}} and {{nv set service snmp-server listening-address}} commands. Alternatively, you can use the equivalent REST API methods.</td>
 <td>5.4.0-5.8.0</td>