From 344fbf38728894196230d97a6e755edf51031f41 Mon Sep 17 00:00:00 2001 From: cumulusAnia Date: Wed, 5 Feb 2025 15:27:13 -0800 Subject: [PATCH 1/4] trigger build --- build_trigger.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/build_trigger.txt b/build_trigger.txt index a132f34023..4441a0af9e 100644 --- a/build_trigger.txt +++ b/build_trigger.txt @@ -1 +1 @@ -build... +build..... From e010e99ec9744161fb08d857fb23cb1d86e1ff0b Mon Sep 17 00:00:00 2001 From: cumulusAnia Date: Wed, 5 Feb 2025 23:28:30 +0000 Subject: [PATCH 2/4] Automated release note commit --- content/cumulus-linux-510/Whats-New/rn.md | 1 + content/cumulus-linux-510/rn.xml | 5 +++++ content/cumulus-linux-55/Whats-New/rn.md | 1 + content/cumulus-linux-55/rn.xml | 6 ++++++ content/cumulus-linux-56/Whats-New/rn.md | 1 + content/cumulus-linux-56/rn.xml | 6 ++++++ content/cumulus-linux-57/Whats-New/rn.md | 1 + content/cumulus-linux-57/rn.xml | 6 ++++++ content/cumulus-linux-58/Whats-New/rn.md | 1 + content/cumulus-linux-58/rn.xml | 6 ++++++ content/cumulus-linux-59/Whats-New/rn.md | 3 +++ content/cumulus-linux-59/rn.xml | 18 ++++++++++++++++++ 12 files changed, 55 insertions(+) diff --git a/content/cumulus-linux-510/Whats-New/rn.md b/content/cumulus-linux-510/Whats-New/rn.md index 411bc812c6..a085939a35 100644 --- a/content/cumulus-linux-510/Whats-New/rn.md +++ b/content/cumulus-linux-510/Whats-New/rn.md @@ -333,6 +333,7 @@ pdfhidden: True | [3917528](#3917528)
| With LACP bypass enabled, Cumulus Linux does not program the MAC address in the bridge FDB for VLAN unaware tagged ports. With EVPN, the address is not advertised and the remote side might flood the packet instead of unicast. | 5.8.0-5.9.1 | | | [3915842](#3915842)
| A kernel crash due to memory corruption might occur due to a netfilter error. The log message from netfilter might contain a warning similar to the following:
kernel: WARNING: CPU: 1 PID: 0 at net/netfilter/nf_conntrack_core.c:1210 __nf_conntrack_confirm+0x5c7/0x6b0 [nf_conntrack]kernel: RIP: 0010:__nf_conntrack_confirm+0x5c7/0x6b0 [nf_conntrack]
| 5.9.0-5.9.1 | | | [3904516](#3904516)
| With Optimized Multicast Flooding (OMF), when you unset multiple multicast router ports in a single commit, multicast traffic still floods one of the ports. To work around this issue, unset multicast router ports one by one instead of in a single commit. | 5.9.0-5.9.1 | | +| [3897227](#3897227)
| During an LLDP update storm while deleting or adding LLPD neighbors, PTMD crashes as a result of mishandling multi-threaded LLPD processing. | 5.5.1-5.9.2 | | | [3896967](#3896967)
| 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.9.1 | | | [3895042](#3895042)
| After an NMS station does a full SNMP walk on the switch, you see the following message every 5 minutes:
 snmp : command not allowed ; TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/usr/cumulus/bin/poectl -j -a

This issue occurs because poectl is called on non-PoE switches. To work around this issue, remove or comment out the poetcl call from the /etc/snmpd.conf file, then restart the snmpd process with the sudo systemctl snmpd restart command

 #snmp ALL = NOPASSWD: /usr/cumulus/bin/poectl -j -a
| 4.4.0-5.9.1 | | | [3895017](#3895017)
| When ARP suppression is off, remote EVPN VTEPs duplicate ARP packets from local hosts and each remote host receives two copies of the ARP packets. The issue also applies to IPv6 ND packets. | 5.8.0-5.9.1 | | diff --git a/content/cumulus-linux-510/rn.xml b/content/cumulus-linux-510/rn.xml index c8407a4be3..59b32ed5e3 100644 --- a/content/cumulus-linux-510/rn.xml +++ b/content/cumulus-linux-510/rn.xml @@ -1927,6 +1927,11 @@ kernel: RIP: 0010:__nf_conntrack_confirm+0x5c7/0x6b0 [nf_conntrack] 5.9.0-5.9.1 +3897227 +During an LLDP update storm while deleting or adding LLPD neighbors, PTMD crashes as a result of mishandling multi-threaded LLPD processing. +5.5.1-5.9.2 + + 3896967 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.9.1 diff --git a/content/cumulus-linux-55/Whats-New/rn.md b/content/cumulus-linux-55/Whats-New/rn.md index 0a914fec73..45eaba28a6 100644 --- a/content/cumulus-linux-55/Whats-New/rn.md +++ b/content/cumulus-linux-55/Whats-New/rn.md @@ -20,6 +20,7 @@ pdfhidden: True | [3982226](#3982226)
| 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.9.1 | 5.9.2-5.12.0, 5.10.0-5.12.0| | [3980941](#3980941)
| After an NMS station does a full SNMP walk on the switch, you see the following message every 5 minutes:
 snmp : command not allowed ; TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/usr/cumulus/bin/poectl -j -a

This issue occurs because poectl is called on non-PoE switches. To work around this issue, remove or comment out the poetcl call from the /etc/snmpd.conf file, then restart the snmpd process with the sudo systemctl snmpd restart command

 #snmp ALL = NOPASSWD: /usr/cumulus/bin/poectl -j -a
| 4.4.0-5.9.1 | 5.9.2-5.12.0, 5.10.0-5.12.0| | [3965573](#3965573)
| If you use NVUE to create an SNMP user with a password, then delete and recreate the user with additional encryption passwords (such as DES or AES), SNMP authorization fails for that user. | 5.3.1-5.9.1 | 5.9.2-5.12.0, 5.10.0-5.12.0| +| [3897227](#3897227)
| During an LLDP update storm while deleting or adding LLPD neighbors, PTMD crashes as a result of mishandling multi-threaded LLPD processing. | 5.5.1-5.9.2 | 5.10.0-5.12.0| | [3773177](#3773177)
| When you try to upgrade a switch from Cumulus Linux 5.5 or earlier to 5.8.0 or later with package upgrade, you see errors for expired GPG keys that prevent you from upgrading. To work around this issue, install the new keys with the following commands, then upgrade the switch.
cumulus@switch:~$ wget https://download.nvidia.com/cumulus/apt.cumulusnetworks.com/repo/pool/cumulus/c/cumulus-archive-keyring/cumulus-archive-keyring_4-cl5.6.0u5_all.deb
cumulus@switch:~$ sudo apt install ./cumulus-archive-keyring_4-cl5.6.0u5_all.deb
cumulus@switch:~$ sudo apt update
cumulus@switch:~$ sudo apt upgrade
| 4.0.0-4.4.5, 5.0.0-5.12.0 | | | [3765395](#3765395)
| The nv unset nve vxlan flooding and nv set nve vxlan flooding enable off commands do not disable BUM flooding. To work around this issue, disable BUM flooding with vtysh commands:
leaf01# configure terminal
leaf01(config)# router bgp 
leaf01(config-router)# address-family l2vpn evpn
leaf01(config-router-af)# flooding disable
leaf01(config-router-af)# end
leaf01# write memory
leaf01# exit
| 5.5.0-5.8.0 | 5.9.0-5.12.0| | [3751952](#3751952)
| ifupdown2 tries to set the multicast database hash elasticity (bridge-hashel attribute) with a value of 4096. However, this attribute is now deprecated in the Linux kernel and the value is always 16. | 5.5.1-5.7.0 | 5.8.0-5.12.0| diff --git a/content/cumulus-linux-55/rn.xml b/content/cumulus-linux-55/rn.xml index 30b085de22..b9ab386b7a 100644 --- a/content/cumulus-linux-55/rn.xml +++ b/content/cumulus-linux-55/rn.xml @@ -46,6 +46,12 @@ This issue occurs because {{poectl}} is called on non-PoE switches. To work arou 5.9.2-5.12.0, 5.10.0-5.12.0 +3897227 +During an LLDP update storm while deleting or adding LLPD neighbors, PTMD crashes as a result of mishandling multi-threaded LLPD processing. +5.5.1-5.9.2 +5.10.0-5.12.0 + + 3773177 When you try to upgrade a switch from Cumulus Linux 5.5 or earlier to 5.8.0 or later with package upgrade, you see errors for expired GPG keys that prevent you from upgrading. To work around this issue, install the new keys with the following commands, then upgrade the switch. diff --git a/content/cumulus-linux-56/Whats-New/rn.md b/content/cumulus-linux-56/Whats-New/rn.md index 046cfd7e3e..faf1c211f6 100644 --- a/content/cumulus-linux-56/Whats-New/rn.md +++ b/content/cumulus-linux-56/Whats-New/rn.md @@ -23,6 +23,7 @@ pdfhidden: True | [3982226](#3982226)
| 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.9.1 | 5.9.2-5.12.0, 5.10.0-5.12.0| | [3980941](#3980941)
| After an NMS station does a full SNMP walk on the switch, you see the following message every 5 minutes:
 snmp : command not allowed ; TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/usr/cumulus/bin/poectl -j -a

This issue occurs because poectl is called on non-PoE switches. To work around this issue, remove or comment out the poetcl call from the /etc/snmpd.conf file, then restart the snmpd process with the sudo systemctl snmpd restart command

 #snmp ALL = NOPASSWD: /usr/cumulus/bin/poectl -j -a
| 4.4.0-5.9.1 | 5.9.2-5.12.0, 5.10.0-5.12.0| | [3965573](#3965573)
| If you use NVUE to create an SNMP user with a password, then delete and recreate the user with additional encryption passwords (such as DES or AES), SNMP authorization fails for that user. | 5.3.1-5.9.1 | 5.9.2-5.12.0, 5.10.0-5.12.0| +| [3897227](#3897227)
| During an LLDP update storm while deleting or adding LLPD neighbors, PTMD crashes as a result of mishandling multi-threaded LLPD processing. | 5.5.1-5.9.2 | 5.10.0-5.12.0| | [3863858](#3863858)
| VRR interfaces might show dadfailed on their IPv6 link-local address. | 5.6.0-5.8.0 | 5.9.0-5.12.0| | [3824750](#3824750)
| With the nvidia.nvue Ansible module, NVUE honors input from the Ansible module only; if you do not provide the full configuration, NVUE generates an exception. To work around this issue, always provide the full configuration. | 5.6.0-5.8.0 | 5.9.0-5.12.0| | [3782996](#3782996)
| If you have installed a large number ACLs, you might see a switchd memory leak over a period of time that stops the switchd process because it is out of memory . | 5.6.0-5.8.0 | 5.9.0-5.12.0| diff --git a/content/cumulus-linux-56/rn.xml b/content/cumulus-linux-56/rn.xml index ca30455088..81b464ea07 100644 --- a/content/cumulus-linux-56/rn.xml +++ b/content/cumulus-linux-56/rn.xml @@ -64,6 +64,12 @@ This issue occurs because {{poectl}} is called on non-PoE switches. To work arou 5.9.2-5.12.0, 5.10.0-5.12.0 +3897227 +During an LLDP update storm while deleting or adding LLPD neighbors, PTMD crashes as a result of mishandling multi-threaded LLPD processing. +5.5.1-5.9.2 +5.10.0-5.12.0 + + 3863858 VRR interfaces might show {{dadfailed}} on their IPv6 link-local address. 5.6.0-5.8.0 diff --git a/content/cumulus-linux-57/Whats-New/rn.md b/content/cumulus-linux-57/Whats-New/rn.md index e7258ec648..af3504f424 100644 --- a/content/cumulus-linux-57/Whats-New/rn.md +++ b/content/cumulus-linux-57/Whats-New/rn.md @@ -25,6 +25,7 @@ pdfhidden: True | [3982226](#3982226)
| 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.9.1 | 5.9.2-5.12.0, 5.10.0-5.12.0| | [3980941](#3980941)
| After an NMS station does a full SNMP walk on the switch, you see the following message every 5 minutes:
 snmp : command not allowed ; TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/usr/cumulus/bin/poectl -j -a

This issue occurs because poectl is called on non-PoE switches. To work around this issue, remove or comment out the poetcl call from the /etc/snmpd.conf file, then restart the snmpd process with the sudo systemctl snmpd restart command

 #snmp ALL = NOPASSWD: /usr/cumulus/bin/poectl -j -a
| 4.4.0-5.9.1 | 5.9.2-5.12.0, 5.10.0-5.12.0| | [3965573](#3965573)
| If you use NVUE to create an SNMP user with a password, then delete and recreate the user with additional encryption passwords (such as DES or AES), SNMP authorization fails for that user. | 5.3.1-5.9.1 | 5.9.2-5.12.0, 5.10.0-5.12.0| +| [3897227](#3897227)
| During an LLDP update storm while deleting or adding LLPD neighbors, PTMD crashes as a result of mishandling multi-threaded LLPD processing. | 5.5.1-5.9.2 | 5.10.0-5.12.0| | [3863858](#3863858)
| VRR interfaces might show dadfailed on their IPv6 link-local address. | 5.6.0-5.8.0 | 5.9.0-5.12.0| | [3832116](#3832116)
| When you configure a SPAN session either with the NVUE nv set system port-mirror session command or in the /etc/cumulus/switchd.d/port-mirror.conf file and the default route is configured to 0.0.0.0/0, the SPAN session might not work as expected. To work around this issue, remove the default route 0.0.0.0/0 and use alternate routes instead. | 5.7.0-5.8.0 | 5.9.0-5.12.0| | [3824750](#3824750)
| With the nvidia.nvue Ansible module, NVUE honors input from the Ansible module only; if you do not provide the full configuration, NVUE generates an exception. To work around this issue, always provide the full configuration. | 5.6.0-5.8.0 | 5.9.0-5.12.0| diff --git a/content/cumulus-linux-57/rn.xml b/content/cumulus-linux-57/rn.xml index 9840fb731d..943c326ce0 100644 --- a/content/cumulus-linux-57/rn.xml +++ b/content/cumulus-linux-57/rn.xml @@ -76,6 +76,12 @@ This issue occurs because {{poectl}} is called on non-PoE switches. To work arou 5.9.2-5.12.0, 5.10.0-5.12.0 +3897227 +During an LLDP update storm while deleting or adding LLPD neighbors, PTMD crashes as a result of mishandling multi-threaded LLPD processing. +5.5.1-5.9.2 +5.10.0-5.12.0 + + 3863858 VRR interfaces might show {{dadfailed}} on their IPv6 link-local address. 5.6.0-5.8.0 diff --git a/content/cumulus-linux-58/Whats-New/rn.md b/content/cumulus-linux-58/Whats-New/rn.md index 7fbf4a3111..99738f1494 100644 --- a/content/cumulus-linux-58/Whats-New/rn.md +++ b/content/cumulus-linux-58/Whats-New/rn.md @@ -40,6 +40,7 @@ pdfhidden: True | [3980938](#3980938)
| When ARP suppression is off, remote EVPN VTEPs duplicate ARP packets from local hosts and each remote host receives two copies of the ARP packets. The issue also applies to IPv6 ND packets. | 5.8.0-5.9.1 | 5.9.2-5.12.0, 5.10.0-5.12.0| | [3980925](#3980925)
| When you configure the bridge.kernel_mac_refresh_interval parameter in the switchd.conf file, a switchd restart fails with a core dump. | 5.8.0-5.9.1 | 5.9.2-5.12.0, 5.10.0-5.12.0| | [3965573](#3965573)
| If you use NVUE to create an SNMP user with a password, then delete and recreate the user with additional encryption passwords (such as DES or AES), SNMP authorization fails for that user. | 5.3.1-5.9.1 | 5.9.2-5.12.0, 5.10.0-5.12.0| +| [3897227](#3897227)
| During an LLDP update storm while deleting or adding LLPD neighbors, PTMD crashes as a result of mishandling multi-threaded LLPD processing. | 5.5.1-5.9.2 | 5.10.0-5.12.0| | [3875419](#3875419)
| The cleanup scrip inadvertently removes the active LTTng session directory used by lttng-sessiond for trace dumping. This issue occurs under specific conditions when more than five LTTng trace folders are present, leading to intermittent failures in trace logging. To work around this issue, manually move the timestamped lttng logs to a different directory. | 5.8.0 | 5.9.0-5.12.0| | [3863858](#3863858)
| VRR interfaces might show dadfailed on their IPv6 link-local address. | 5.6.0-5.8.0 | 5.9.0-5.12.0| | [3863063](#3863063)
| When simultaneously changing the maxage and forward-delay bridge timers in RSTP for VLAN-aware bridges, the commands might not be accepted if the 2xfdelay-1 is less than the previously configured maxage timer because ifupdown2 configures the forward delay first.
To work around this issue, run the ifreload -a command again to process the forward-delay command after the new maxage configuration has been accepted.
You have to repeat the ifreload -a command after a reboot to set the forward delay correctly in the bridge. | 5.8.0 | 5.9.0-5.12.0| diff --git a/content/cumulus-linux-58/rn.xml b/content/cumulus-linux-58/rn.xml index b3915932d7..0e5b7844c5 100644 --- a/content/cumulus-linux-58/rn.xml +++ b/content/cumulus-linux-58/rn.xml @@ -166,6 +166,12 @@ This issue occurs because {{poectl}} is called on non-PoE switches. To work arou 5.9.2-5.12.0, 5.10.0-5.12.0 +3897227 +During an LLDP update storm while deleting or adding LLPD neighbors, PTMD crashes as a result of mishandling multi-threaded LLPD processing. +5.5.1-5.9.2 +5.10.0-5.12.0 + + 3875419 The cleanup scrip inadvertently removes the active LTTng session directory used by {{lttng-sessiond}} for trace dumping. This issue occurs under specific conditions when more than five LTTng trace folders are present, leading to intermittent failures in trace logging. To work around this issue, manually move the timestamped {{lttng}} logs to a different directory. 5.8.0 diff --git a/content/cumulus-linux-59/Whats-New/rn.md b/content/cumulus-linux-59/Whats-New/rn.md index d5021c4d4a..9b99df12cc 100644 --- a/content/cumulus-linux-59/Whats-New/rn.md +++ b/content/cumulus-linux-59/Whats-New/rn.md @@ -51,6 +51,7 @@ pdfhidden: True | [3990135](#3990135)
| 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. | 5.9.1-5.12.0 | | | [3985600](#3985600)
| NTP initialization issues prevent the NTP service from starting on a non-default VRF. | 5.9.0-5.9.2 | 5.10.0-5.12.0| | [3915878](#3915878)
| If you configure remote syslog export through a non-default VRF, you might see repeated error logs from the rsyslog process while the switch is booting:
rsyslogd: create UDP socket bound to device failed: No such device [v8.2302.0]rsyslogd: No UDP socket could successfully be initialized, some functionality may be disabled.  [v8.2302.0]

The logs occur because the rsyslog service starts before the networking service creates the configured VRF for syslog export. There is no functional impact with this issue. | 5.9.0-5.12.0 | | +| [3897227](#3897227)
| During an LLDP update storm while deleting or adding LLPD neighbors, PTMD crashes as a result of mishandling multi-threaded LLPD processing. | 5.5.1-5.9.2 | 5.10.0-5.12.0| | [3890993](#3890993)
| On the NVIDIA spectrum-4 switch, l1-show command output does not show Eye opening information for an interface port. | 5.9.0-5.9.2 | 5.10.0-5.12.0| | [3879809](#3879809)
| What Just Happened (WJH) does not work on Spectrum-4 switches. | 5.9.0-5.12.0 | | | [3878699](#3878699)
| In an EVPN multihoming configuration, when the VXLAN device associated with a layer 2 VNI flaps, there is a route entry in the tenant VRF associated with the locally learned host. | 5.9.0-5.10.1 | 5.11.0-5.12.0| @@ -243,6 +244,7 @@ pdfhidden: True | [3915878](#3915878)
| If you configure remote syslog export through a non-default VRF, you might see repeated error logs from the rsyslog process while the switch is booting:
rsyslogd: create UDP socket bound to device failed: No such device [v8.2302.0]rsyslogd: No UDP socket could successfully be initialized, some functionality may be disabled.  [v8.2302.0]

The logs occur because the rsyslog service starts before the networking service creates the configured VRF for syslog export. There is no functional impact with this issue. | 5.9.0-5.12.0 | | | [3915842](#3915842)
| A kernel crash due to memory corruption might occur due to a netfilter error. The log message from netfilter might contain a warning similar to the following:
kernel: WARNING: CPU: 1 PID: 0 at net/netfilter/nf_conntrack_core.c:1210 __nf_conntrack_confirm+0x5c7/0x6b0 [nf_conntrack]kernel: RIP: 0010:__nf_conntrack_confirm+0x5c7/0x6b0 [nf_conntrack]
| 5.9.0-5.9.1 | 5.9.2-5.12.0| | [3904516](#3904516)
| With Optimized Multicast Flooding (OMF), when you unset multiple multicast router ports in a single commit, multicast traffic still floods one of the ports. To work around this issue, unset multicast router ports one by one instead of in a single commit. | 5.9.0-5.9.1 | 5.9.2-5.12.0| +| [3897227](#3897227)
| During an LLDP update storm while deleting or adding LLPD neighbors, PTMD crashes as a result of mishandling multi-threaded LLPD processing. | 5.5.1-5.9.2 | 5.10.0-5.12.0| | [3896967](#3896967)
| 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.9.1 | 5.9.2-5.12.0| | [3895042](#3895042)
| After an NMS station does a full SNMP walk on the switch, you see the following message every 5 minutes:
 snmp : command not allowed ; TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/usr/cumulus/bin/poectl -j -a

This issue occurs because poectl is called on non-PoE switches. To work around this issue, remove or comment out the poetcl call from the /etc/snmpd.conf file, then restart the snmpd process with the sudo systemctl snmpd restart command

 #snmp ALL = NOPASSWD: /usr/cumulus/bin/poectl -j -a
| 4.4.0-5.9.1 | 5.9.2-5.12.0| | [3895017](#3895017)
| When ARP suppression is off, remote EVPN VTEPs duplicate ARP packets from local hosts and each remote host receives two copies of the ARP packets. The issue also applies to IPv6 ND packets. | 5.8.0-5.9.1 | 5.9.2-5.12.0| @@ -370,6 +372,7 @@ pdfhidden: True | [3915842](#3915842)
| A kernel crash due to memory corruption might occur due to a netfilter error. The log message from netfilter might contain a warning similar to the following:
kernel: WARNING: CPU: 1 PID: 0 at net/netfilter/nf_conntrack_core.c:1210 __nf_conntrack_confirm+0x5c7/0x6b0 [nf_conntrack]kernel: RIP: 0010:__nf_conntrack_confirm+0x5c7/0x6b0 [nf_conntrack]
| 5.9.0-5.9.1 | 5.9.2-5.12.0| | [3915829](#3915829)
| General improvements to overall software stability. | 5.9.0 | 5.9.1-5.12.0| | [3904516](#3904516)
| With Optimized Multicast Flooding (OMF), when you unset multiple multicast router ports in a single commit, multicast traffic still floods one of the ports. To work around this issue, unset multicast router ports one by one instead of in a single commit. | 5.9.0-5.9.1 | 5.9.2-5.12.0| +| [3897227](#3897227)
| During an LLDP update storm while deleting or adding LLPD neighbors, PTMD crashes as a result of mishandling multi-threaded LLPD processing. | 5.5.1-5.9.2 | 5.10.0-5.12.0| | [3896967](#3896967)
| 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.9.1 | 5.9.2-5.12.0| | [3895042](#3895042)
| After an NMS station does a full SNMP walk on the switch, you see the following message every 5 minutes:
 snmp : command not allowed ; TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/usr/cumulus/bin/poectl -j -a

This issue occurs because poectl is called on non-PoE switches. To work around this issue, remove or comment out the poetcl call from the /etc/snmpd.conf file, then restart the snmpd process with the sudo systemctl snmpd restart command

 #snmp ALL = NOPASSWD: /usr/cumulus/bin/poectl -j -a
| 4.4.0-5.9.1 | 5.9.2-5.12.0| | [3895017](#3895017)
| When ARP suppression is off, remote EVPN VTEPs duplicate ARP packets from local hosts and each remote host receives two copies of the ARP packets. The issue also applies to IPv6 ND packets. | 5.8.0-5.9.1 | 5.9.2-5.12.0| diff --git a/content/cumulus-linux-59/rn.xml b/content/cumulus-linux-59/rn.xml index 694fa24a69..ef0ac690a5 100644 --- a/content/cumulus-linux-59/rn.xml +++ b/content/cumulus-linux-59/rn.xml @@ -242,6 +242,12 @@ The logs occur because the {{rsyslog}} service starts before the networking serv +3897227 +During an LLDP update storm while deleting or adding LLPD neighbors, PTMD crashes as a result of mishandling multi-threaded LLPD processing. +5.5.1-5.9.2 +5.10.0-5.12.0 + + 3890993 On the NVIDIA spectrum-4 switch, {{l1-show}} command output does not show Eye opening information for an interface port. 5.9.0-5.9.2 @@ -1370,6 +1376,12 @@ kernel: RIP: 0010:__nf_conntrack_confirm+0x5c7/0x6b0 [nf_conntrack] 5.9.2-5.12.0 +3897227 +During an LLDP update storm while deleting or adding LLPD neighbors, PTMD crashes as a result of mishandling multi-threaded LLPD processing. +5.5.1-5.9.2 +5.10.0-5.12.0 + + 3896967 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.9.1 @@ -2142,6 +2154,12 @@ kernel: RIP: 0010:__nf_conntrack_confirm+0x5c7/0x6b0 [nf_conntrack] 5.9.2-5.12.0 +3897227 +During an LLDP update storm while deleting or adding LLPD neighbors, PTMD crashes as a result of mishandling multi-threaded LLPD processing. +5.5.1-5.9.2 +5.10.0-5.12.0 + + 3896967 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.9.1 From 5d1d3f016aae4f95c2d77b29aca8169e83f515c2 Mon Sep 17 00:00:00 2001 From: Stu Clark Date: Thu, 6 Feb 2025 12:49:12 -0500 Subject: [PATCH 3/4] Correct ZTP cascade directive - CL44-CL512 --- .../Installation-Management/Zero-Touch-Provisioning-ZTP.md | 2 +- .../Installation-Management/Zero-Touch-Provisioning-ZTP.md | 2 +- .../Installation-Management/Zero-Touch-Provisioning-ZTP.md | 2 +- .../Installation-Management/Zero-Touch-Provisioning-ZTP.md | 2 +- .../Installation-Management/Zero-Touch-Provisioning-ZTP.md | 2 +- .../Installation-Management/Zero-Touch-Provisioning-ZTP.md | 2 +- .../Installation-Management/Zero-Touch-Provisioning-ZTP.md | 2 +- .../Installation-Management/Zero-Touch-Provisioning-ZTP.md | 2 +- .../Installation-Management/Zero-Touch-Provisioning-ZTP.md | 2 +- .../Installation-Management/Zero-Touch-Provisioning-ZTP.md | 2 +- .../Installation-Management/Zero-Touch-Provisioning-ZTP.md | 2 +- .../Installation-Management/Zero-Touch-Provisioning-ZTP.md | 2 +- .../Installation-Management/Zero-Touch-Provisioning-ZTP.md | 2 +- .../Installation-Management/Zero-Touch-Provisioning-ZTP.md | 2 +- 14 files changed, 14 insertions(+), 14 deletions(-) diff --git a/content/cumulus-linux-44/Installation-Management/Zero-Touch-Provisioning-ZTP.md b/content/cumulus-linux-44/Installation-Management/Zero-Touch-Provisioning-ZTP.md index 01f1349020..5f7985ab0a 100644 --- a/content/cumulus-linux-44/Installation-Management/Zero-Touch-Provisioning-ZTP.md +++ b/content/cumulus-linux-44/Installation-Management/Zero-Touch-Provisioning-ZTP.md @@ -189,7 +189,7 @@ exit 0 ## Continue Provisioning -Typically ZTP exits after executing the script locally and does not continue. To continue with provisioning so that you do not have to intervene manually or embed an Ansible callback into the script, you can add the `CUMULUS-AUTOPROVISION-CASCADE` directive. +Typically ZTP exits after executing the script locally and does not continue. To continue with provisioning so that you do not have to intervene manually or embed an Ansible callback into the script, you can add the `CUMULUS-AUTOPROVISIONING-CASCADE` directive. ## Best Practices diff --git a/content/cumulus-linux-50/Installation-Management/Zero-Touch-Provisioning-ZTP.md b/content/cumulus-linux-50/Installation-Management/Zero-Touch-Provisioning-ZTP.md index 4279169a36..501f30fa42 100644 --- a/content/cumulus-linux-50/Installation-Management/Zero-Touch-Provisioning-ZTP.md +++ b/content/cumulus-linux-50/Installation-Management/Zero-Touch-Provisioning-ZTP.md @@ -186,7 +186,7 @@ exit 0 ## Continue Provisioning -Typically ZTP exits after executing the script locally and does not continue. To continue with provisioning so that you do not have to intervene manually or embed an Ansible callback into the script, you can add the `CUMULUS-AUTOPROVISION-CASCADE` directive. +Typically ZTP exits after executing the script locally and does not continue. To continue with provisioning so that you do not have to intervene manually or embed an Ansible callback into the script, you can add the `CUMULUS-AUTOPROVISIONING-CASCADE` directive. ## Best Practices diff --git a/content/cumulus-linux-51/Installation-Management/Zero-Touch-Provisioning-ZTP.md b/content/cumulus-linux-51/Installation-Management/Zero-Touch-Provisioning-ZTP.md index 903d55e932..f7d176ec7b 100644 --- a/content/cumulus-linux-51/Installation-Management/Zero-Touch-Provisioning-ZTP.md +++ b/content/cumulus-linux-51/Installation-Management/Zero-Touch-Provisioning-ZTP.md @@ -186,7 +186,7 @@ exit 0 ## Continue Provisioning -Typically ZTP exits after executing the script locally and does not continue. To continue with provisioning so that you do not have to intervene manually or embed an Ansible callback into the script, you can add the `CUMULUS-AUTOPROVISION-CASCADE` directive. +Typically ZTP exits after executing the script locally and does not continue. To continue with provisioning so that you do not have to intervene manually or embed an Ansible callback into the script, you can add the `CUMULUS-AUTOPROVISIONING-CASCADE` directive. ## Best Practices diff --git a/content/cumulus-linux-510/Installation-Management/Zero-Touch-Provisioning-ZTP.md b/content/cumulus-linux-510/Installation-Management/Zero-Touch-Provisioning-ZTP.md index dab15d3c26..f0a6942516 100644 --- a/content/cumulus-linux-510/Installation-Management/Zero-Touch-Provisioning-ZTP.md +++ b/content/cumulus-linux-510/Installation-Management/Zero-Touch-Provisioning-ZTP.md @@ -194,7 +194,7 @@ trap error ERR ``` ### Continue Provisioning -Typically ZTP exits after executing the script locally and does not continue. To continue with provisioning so that you do not have to intervene manually or embed an Ansible callback into the script, you can add the `CUMULUS-AUTOPROVISION-CASCADE` directive. +Typically ZTP exits after executing the script locally and does not continue. To continue with provisioning so that you do not have to intervene manually or embed an Ansible callback into the script, you can add the `CUMULUS-AUTOPROVISIONING-CASCADE` directive. ## Best Practices diff --git a/content/cumulus-linux-511/Installation-Management/Zero-Touch-Provisioning-ZTP.md b/content/cumulus-linux-511/Installation-Management/Zero-Touch-Provisioning-ZTP.md index ec9215dafd..2136c411ac 100644 --- a/content/cumulus-linux-511/Installation-Management/Zero-Touch-Provisioning-ZTP.md +++ b/content/cumulus-linux-511/Installation-Management/Zero-Touch-Provisioning-ZTP.md @@ -370,7 +370,7 @@ trap error ERR ``` ### Continue Provisioning -Typically ZTP exits after executing the script locally and does not continue. To continue with provisioning so that you do not have to intervene manually or embed an Ansible callback into the script, you can add the `CUMULUS-AUTOPROVISION-CASCADE` directive. +Typically ZTP exits after executing the script locally and does not continue. To continue with provisioning so that you do not have to intervene manually or embed an Ansible callback into the script, you can add the `CUMULUS-AUTOPROVISIONING-CASCADE` directive. ## Best Practices diff --git a/content/cumulus-linux-512/Installation-Management/Zero-Touch-Provisioning-ZTP.md b/content/cumulus-linux-512/Installation-Management/Zero-Touch-Provisioning-ZTP.md index e48391d065..8e451f841f 100644 --- a/content/cumulus-linux-512/Installation-Management/Zero-Touch-Provisioning-ZTP.md +++ b/content/cumulus-linux-512/Installation-Management/Zero-Touch-Provisioning-ZTP.md @@ -371,7 +371,7 @@ trap error ERR ### Continue Provisioning -Typically ZTP exits after executing the script locally and does not continue. To continue with provisioning so that you do not have to intervene manually or embed an Ansible callback into the script, you can add the `CUMULUS-AUTOPROVISION-CASCADE` directive. +Typically ZTP exits after executing the script locally and does not continue. To continue with provisioning so that you do not have to intervene manually or embed an Ansible callback into the script, you can add the `CUMULUS-AUTOPROVISIONING-CASCADE` directive. ## Best Practices diff --git a/content/cumulus-linux-52/Installation-Management/Zero-Touch-Provisioning-ZTP.md b/content/cumulus-linux-52/Installation-Management/Zero-Touch-Provisioning-ZTP.md index 68b621f614..f63aa1a423 100644 --- a/content/cumulus-linux-52/Installation-Management/Zero-Touch-Provisioning-ZTP.md +++ b/content/cumulus-linux-52/Installation-Management/Zero-Touch-Provisioning-ZTP.md @@ -190,7 +190,7 @@ exit 0 ## Continue Provisioning -Typically ZTP exits after executing the script locally and does not continue. To continue with provisioning so that you do not have to intervene manually or embed an Ansible callback into the script, you can add the `CUMULUS-AUTOPROVISION-CASCADE` directive. +Typically ZTP exits after executing the script locally and does not continue. To continue with provisioning so that you do not have to intervene manually or embed an Ansible callback into the script, you can add the `CUMULUS-AUTOPROVISIONING-CASCADE` directive. ## Best Practices diff --git a/content/cumulus-linux-53/Installation-Management/Zero-Touch-Provisioning-ZTP.md b/content/cumulus-linux-53/Installation-Management/Zero-Touch-Provisioning-ZTP.md index 00ba8ec7e4..aeee3701ba 100644 --- a/content/cumulus-linux-53/Installation-Management/Zero-Touch-Provisioning-ZTP.md +++ b/content/cumulus-linux-53/Installation-Management/Zero-Touch-Provisioning-ZTP.md @@ -190,7 +190,7 @@ exit 0 ## Continue Provisioning -Typically ZTP exits after executing the script locally and does not continue. To continue with provisioning so that you do not have to intervene manually or embed an Ansible callback into the script, you can add the `CUMULUS-AUTOPROVISION-CASCADE` directive. +Typically ZTP exits after executing the script locally and does not continue. To continue with provisioning so that you do not have to intervene manually or embed an Ansible callback into the script, you can add the `CUMULUS-AUTOPROVISIONING-CASCADE` directive. ## Best Practices diff --git a/content/cumulus-linux-54/Installation-Management/Zero-Touch-Provisioning-ZTP.md b/content/cumulus-linux-54/Installation-Management/Zero-Touch-Provisioning-ZTP.md index 00ba8ec7e4..aeee3701ba 100644 --- a/content/cumulus-linux-54/Installation-Management/Zero-Touch-Provisioning-ZTP.md +++ b/content/cumulus-linux-54/Installation-Management/Zero-Touch-Provisioning-ZTP.md @@ -190,7 +190,7 @@ exit 0 ## Continue Provisioning -Typically ZTP exits after executing the script locally and does not continue. To continue with provisioning so that you do not have to intervene manually or embed an Ansible callback into the script, you can add the `CUMULUS-AUTOPROVISION-CASCADE` directive. +Typically ZTP exits after executing the script locally and does not continue. To continue with provisioning so that you do not have to intervene manually or embed an Ansible callback into the script, you can add the `CUMULUS-AUTOPROVISIONING-CASCADE` directive. ## Best Practices diff --git a/content/cumulus-linux-55/Installation-Management/Zero-Touch-Provisioning-ZTP.md b/content/cumulus-linux-55/Installation-Management/Zero-Touch-Provisioning-ZTP.md index 00ba8ec7e4..aeee3701ba 100644 --- a/content/cumulus-linux-55/Installation-Management/Zero-Touch-Provisioning-ZTP.md +++ b/content/cumulus-linux-55/Installation-Management/Zero-Touch-Provisioning-ZTP.md @@ -190,7 +190,7 @@ exit 0 ## Continue Provisioning -Typically ZTP exits after executing the script locally and does not continue. To continue with provisioning so that you do not have to intervene manually or embed an Ansible callback into the script, you can add the `CUMULUS-AUTOPROVISION-CASCADE` directive. +Typically ZTP exits after executing the script locally and does not continue. To continue with provisioning so that you do not have to intervene manually or embed an Ansible callback into the script, you can add the `CUMULUS-AUTOPROVISIONING-CASCADE` directive. ## Best Practices diff --git a/content/cumulus-linux-56/Installation-Management/Zero-Touch-Provisioning-ZTP.md b/content/cumulus-linux-56/Installation-Management/Zero-Touch-Provisioning-ZTP.md index 00ba8ec7e4..aeee3701ba 100644 --- a/content/cumulus-linux-56/Installation-Management/Zero-Touch-Provisioning-ZTP.md +++ b/content/cumulus-linux-56/Installation-Management/Zero-Touch-Provisioning-ZTP.md @@ -190,7 +190,7 @@ exit 0 ## Continue Provisioning -Typically ZTP exits after executing the script locally and does not continue. To continue with provisioning so that you do not have to intervene manually or embed an Ansible callback into the script, you can add the `CUMULUS-AUTOPROVISION-CASCADE` directive. +Typically ZTP exits after executing the script locally and does not continue. To continue with provisioning so that you do not have to intervene manually or embed an Ansible callback into the script, you can add the `CUMULUS-AUTOPROVISIONING-CASCADE` directive. ## Best Practices diff --git a/content/cumulus-linux-57/Installation-Management/Zero-Touch-Provisioning-ZTP.md b/content/cumulus-linux-57/Installation-Management/Zero-Touch-Provisioning-ZTP.md index 00ba8ec7e4..aeee3701ba 100644 --- a/content/cumulus-linux-57/Installation-Management/Zero-Touch-Provisioning-ZTP.md +++ b/content/cumulus-linux-57/Installation-Management/Zero-Touch-Provisioning-ZTP.md @@ -190,7 +190,7 @@ exit 0 ## Continue Provisioning -Typically ZTP exits after executing the script locally and does not continue. To continue with provisioning so that you do not have to intervene manually or embed an Ansible callback into the script, you can add the `CUMULUS-AUTOPROVISION-CASCADE` directive. +Typically ZTP exits after executing the script locally and does not continue. To continue with provisioning so that you do not have to intervene manually or embed an Ansible callback into the script, you can add the `CUMULUS-AUTOPROVISIONING-CASCADE` directive. ## Best Practices diff --git a/content/cumulus-linux-58/Installation-Management/Zero-Touch-Provisioning-ZTP.md b/content/cumulus-linux-58/Installation-Management/Zero-Touch-Provisioning-ZTP.md index 804649259c..a33e5960a1 100644 --- a/content/cumulus-linux-58/Installation-Management/Zero-Touch-Provisioning-ZTP.md +++ b/content/cumulus-linux-58/Installation-Management/Zero-Touch-Provisioning-ZTP.md @@ -191,7 +191,7 @@ exit 0 ## Continue Provisioning -Typically ZTP exits after executing the script locally and does not continue. To continue with provisioning so that you do not have to intervene manually or embed an Ansible callback into the script, you can add the `CUMULUS-AUTOPROVISION-CASCADE` directive. +Typically ZTP exits after executing the script locally and does not continue. To continue with provisioning so that you do not have to intervene manually or embed an Ansible callback into the script, you can add the `CUMULUS-AUTOPROVISIONING-CASCADE` directive. ## Best Practices diff --git a/content/cumulus-linux-59/Installation-Management/Zero-Touch-Provisioning-ZTP.md b/content/cumulus-linux-59/Installation-Management/Zero-Touch-Provisioning-ZTP.md index a9cb9cf581..19b2b319d2 100644 --- a/content/cumulus-linux-59/Installation-Management/Zero-Touch-Provisioning-ZTP.md +++ b/content/cumulus-linux-59/Installation-Management/Zero-Touch-Provisioning-ZTP.md @@ -208,7 +208,7 @@ trap error ERR ``` ### Continue Provisioning -Typically ZTP exits after executing the script locally and does not continue. To continue with provisioning so that you do not have to intervene manually or embed an Ansible callback into the script, you can add the `CUMULUS-AUTOPROVISION-CASCADE` directive. +Typically ZTP exits after executing the script locally and does not continue. To continue with provisioning so that you do not have to intervene manually or embed an Ansible callback into the script, you can add the `CUMULUS-AUTOPROVISIONING-CASCADE` directive. ## Best Practices From 2d3851c37d972ae30f06e8d70d4c2775066a7912 Mon Sep 17 00:00:00 2001 From: cumulusAnia Date: Fri, 7 Feb 2025 15:58:32 -0800 Subject: [PATCH 4/4] update get started --- content/cumulus-linux-511/Quick-Start-Guide/_index.md | 4 ---- content/cumulus-linux-512/Quick-Start-Guide/_index.md | 4 ---- 2 files changed, 8 deletions(-) diff --git a/content/cumulus-linux-511/Quick-Start-Guide/_index.md b/content/cumulus-linux-511/Quick-Start-Guide/_index.md index 967fced9ae..c1933d50f4 100644 --- a/content/cumulus-linux-511/Quick-Start-Guide/_index.md +++ b/content/cumulus-linux-511/Quick-Start-Guide/_index.md @@ -452,10 +452,6 @@ iface lo inet loopback {{< /tab >}} {{< /tabs >}} -{{%notice note%}} -If you configure an IP address without a subnet mask, it becomes a /32 IP address. For example, 10.10.10.1 is 10.10.10.1/32. -{{%/notice%}} - You can add multiple loopback addresses. For more information, see {{}}. ## Show Platform and System Settings diff --git a/content/cumulus-linux-512/Quick-Start-Guide/_index.md b/content/cumulus-linux-512/Quick-Start-Guide/_index.md index 66a3709bd8..cdf87a9d1f 100644 --- a/content/cumulus-linux-512/Quick-Start-Guide/_index.md +++ b/content/cumulus-linux-512/Quick-Start-Guide/_index.md @@ -452,10 +452,6 @@ iface lo inet loopback {{< /tab >}} {{< /tabs >}} -{{%notice note%}} -If you configure an IP address without a subnet mask, it becomes a /32 IP address. For example, 10.10.10.1 is 10.10.10.1/32. -{{%/notice%}} - You can add multiple loopback addresses. For more information, see {{}}. ## Show Platform and System Settings