Merge branch 'cl-doc-fixes' into ania-stage

build_trigger.txt

@@ -1 +1 @@
-build...
+build.....

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
 

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
 

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
 

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
 

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

@@ -333,6 +333,7 @@ pdfhidden: True
 | <a name="3917528"></a> [3917528](#3917528) <a name="3917528"></a> <br /> | 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 | |
 | <a name="3915842"></a> [3915842](#3915842) <a name="3915842"></a> <br /> | A kernel crash due to memory corruption might occur due to a <code>netfilter</code> error. The log message from <code>netfilter</code> might contain a warning similar to the following:<br><pre>kernel: WARNING: CPU: 1 PID: 0 at net/netfilter/nf_conntrack_core.c:1210 __nf_conntrack_confirm+0x5c7/0x6b0 &#91;nf_conntrack&#93;kernel: RIP: 0010:__nf_conntrack_confirm+0x5c7/0x6b0 &#91;nf_conntrack&#93;</pre> | 5.9.0-5.9.1 | |
 | <a name="3904516"></a> [3904516](#3904516) <a name="3904516"></a> <br /> | 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 | |
+| <a name="3897227"></a> [3897227](#3897227) <a name="3897227"></a> <br /> | 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 | |
 | <a name="3896967"></a> [3896967](#3896967) <a name="3896967"></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.9.1 | |
 | <a name="3895042"></a> [3895042](#3895042) <a name="3895042"></a> <br /> | After an NMS station does a full SNMP walk on the switch, you see the following message every 5 minutes:<br> <pre> snmp : command not allowed ; TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/usr/cumulus/bin/poectl -j -a </pre><br>This issue occurs because <code>poectl</code> is called on non-PoE switches. To work around this issue, remove or comment out the <code>poetcl</code> call from the <code>/etc/snmpd.conf</code> file, then restart the <code>snmpd</code> process with the <code>sudo systemctl snmpd restart</code> command<br /><br> <pre> #snmp ALL = NOPASSWD: /usr/cumulus/bin/poectl -j -a </pre> | 4.4.0-5.9.1 | |
 | <a name="3895017"></a> [3895017](#3895017) <a name="3895017"></a> <br /> | 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 | |

content/cumulus-linux-510/rn.xml

@@ -1927,6 +1927,11 @@ kernel: RIP: 0010:__nf_conntrack_confirm+0x5c7/0x6b0 [nf_conntrack]</td>
 <td>5.9.0-5.9.1</td>
 </tr>
 <tr>
+<td>3897227</td>
+<td>During an LLDP update storm while deleting or adding LLPD neighbors, PTMD crashes as a result of mishandling multi-threaded LLPD processing.</td>
+<td>5.5.1-5.9.2</td>
+</tr>
+<tr>
 <td>3896967</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.9.1</td>

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
 

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 {{<link url="Interface-Configuration-and-Management/#loopback-interface" text="Interface Configuration and Management">}}.
 
 ## Show Platform and System Settings

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
 

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 {{<link url="Interface-Configuration-and-Management/#loopback-interface" text="Interface Configuration and Management">}}.
 
 ## Show Platform and System Settings

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
 

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
 

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
 

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
 

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

@@ -20,6 +20,7 @@ pdfhidden: True
 | <a name="3982226"></a> [3982226](#3982226) <a name="3982226"></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.9.1 | 5.9.2-5.12.0, 5.10.0-5.12.0|
 | <a name="3980941"></a> [3980941](#3980941) <a name="3980941"></a> <br /> | After an NMS station does a full SNMP walk on the switch, you see the following message every 5 minutes:<br> <pre> snmp : command not allowed ; TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/usr/cumulus/bin/poectl -j -a </pre><br>This issue occurs because <code>poectl</code> is called on non-PoE switches. To work around this issue, remove or comment out the <code>poetcl</code> call from the <code>/etc/snmpd.conf</code> file, then restart the <code>snmpd</code> process with the <code>sudo systemctl snmpd restart</code> command<br /><br> <pre> #snmp ALL = NOPASSWD: /usr/cumulus/bin/poectl -j -a </pre> | 4.4.0-5.9.1 | 5.9.2-5.12.0, 5.10.0-5.12.0|
 | <a name="3965573"></a> [3965573](#3965573) <a name="3965573"></a> <br /> | 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|
+| <a name="3897227"></a> [3897227](#3897227) <a name="3897227"></a> <br /> | 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|
 | <a name="3773177"></a> [3773177](#3773177) <a name="3773177"></a> <br /> | 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.<br><pre>cumulus&#64;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<br>cumulus&#64;switch:~$ sudo apt install ./cumulus-archive-keyring_4-cl5.6.0u5_all.deb<br>cumulus&#64;switch:~$ sudo apt update<br>cumulus&#64;switch:~$ sudo apt upgrade</pre> | 4.0.0-4.4.5, 5.0.0-5.12.0 | |
 | <a name="3765395"></a> [3765395](#3765395) <a name="3765395"></a> <br /> | The <code>nv unset nve vxlan flooding</code> and <code>nv set nve vxlan flooding enable off</code> commands do not disable BUM flooding. To work around this issue, disable BUM flooding with vtysh commands:<br><pre>leaf01# configure terminal<br>leaf01(config)# router bgp <br>leaf01(config-router)# address-family l2vpn evpn<br>leaf01(config-router-af)# flooding disable<br>leaf01(config-router-af)# end<br>leaf01# write memory<br>leaf01# exit</pre> | 5.5.0-5.8.0 | 5.9.0-5.12.0|
 | <a name="3751952"></a> [3751952](#3751952) <a name="3751952"></a> <br /> | <code>ifupdown2</code> 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|

content/cumulus-linux-55/rn.xml

@@ -46,6 +46,12 @@ This issue occurs because {{poectl}} is called on non-PoE switches. To work arou
 <td>5.9.2-5.12.0, 5.10.0-5.12.0</td>
 </tr>
 <tr>
+<td>3897227</td>
+<td>During an LLDP update storm while deleting or adding LLPD neighbors, PTMD crashes as a result of mishandling multi-threaded LLPD processing.</td>
+<td>5.5.1-5.9.2</td>
+<td>5.10.0-5.12.0</td>
+</tr>
+<tr>
 <td>3773177</td>
 <td>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.
 

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
 

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

@@ -23,6 +23,7 @@ pdfhidden: True
 | <a name="3982226"></a> [3982226](#3982226) <a name="3982226"></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.9.1 | 5.9.2-5.12.0, 5.10.0-5.12.0|
 | <a name="3980941"></a> [3980941](#3980941) <a name="3980941"></a> <br /> | After an NMS station does a full SNMP walk on the switch, you see the following message every 5 minutes:<br> <pre> snmp : command not allowed ; TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/usr/cumulus/bin/poectl -j -a </pre><br>This issue occurs because <code>poectl</code> is called on non-PoE switches. To work around this issue, remove or comment out the <code>poetcl</code> call from the <code>/etc/snmpd.conf</code> file, then restart the <code>snmpd</code> process with the <code>sudo systemctl snmpd restart</code> command<br /><br> <pre> #snmp ALL = NOPASSWD: /usr/cumulus/bin/poectl -j -a </pre> | 4.4.0-5.9.1 | 5.9.2-5.12.0, 5.10.0-5.12.0|
 | <a name="3965573"></a> [3965573](#3965573) <a name="3965573"></a> <br /> | 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|
+| <a name="3897227"></a> [3897227](#3897227) <a name="3897227"></a> <br /> | 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|
 | <a name="3863858"></a> [3863858](#3863858) <a name="3863858"></a> <br /> | VRR interfaces might show <code>dadfailed</code> on their IPv6 link-local address. | 5.6.0-5.8.0 | 5.9.0-5.12.0|
 | <a name="3824750"></a> [3824750](#3824750) <a name="3824750"></a> <br /> | With the <code>nvidia.nvue</code> 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|
 | <a name="3782996"></a> [3782996](#3782996) <a name="3782996"></a> <br /> | If you have installed a large number ACLs,  you might see a <code>switchd</code> memory leak over a period of time that stops the <code>switchd</code> process because it is out of memory . | 5.6.0-5.8.0 | 5.9.0-5.12.0|

content/cumulus-linux-56/rn.xml

@@ -64,6 +64,12 @@ This issue occurs because {{poectl}} is called on non-PoE switches. To work arou
 <td>5.9.2-5.12.0, 5.10.0-5.12.0</td>
 </tr>
 <tr>
+<td>3897227</td>
+<td>During an LLDP update storm while deleting or adding LLPD neighbors, PTMD crashes as a result of mishandling multi-threaded LLPD processing.</td>
+<td>5.5.1-5.9.2</td>
+<td>5.10.0-5.12.0</td>
+</tr>
+<tr>
 <td>3863858</td>
 <td>VRR interfaces might show {{dadfailed}} on their IPv6 link-local address.</td>
 <td>5.6.0-5.8.0</td>

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