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

Changes by create-pull-request action
CumulusNetworks · Dec 7, 2023 · 1bc599b · 1bc599b
2 parents 53acb94 + e4bfd90
commit 1bc599b
Show file tree

Hide file tree

Showing 4 changed files with 99 additions and 0 deletions.
diff --git a/content/cumulus-linux-55/Whats-New/rn.md b/content/cumulus-linux-55/Whats-New/rn.md
@@ -14,6 +14,8 @@ pdfhidden: True
 
 |  Issue ID 	|   Description	|   Affects	|   Fixed |
 |---	        |---	        |---	    |---	                |
+| <a name="3695541"></a> [3695541](#3695541) <a name="3695541"></a> <br /> | When applying a full configuration with NVUE that includes VRRP and BGP in VRFs, the VRRP configuration does not come up after you run <code>nv config apply</code>.  BGP routes might also be missing.  This issue only happens during the initial <code>nv config apply</code> of a full configuration, not during a normal initialization during a reboot or FRR restart. To work around this issue, reboot or restart FRR. | 5.5.1 | 5.6.0|
+| <a name="3668939"></a> [3668939](#3668939) <a name="3668939"></a> <br /> | When you enable MIB 1.3.6.1.4.1.40310.1 in the <code>snmpd.conf</code> file, you might see high CPU usage by the <code>snmpd</code> service. | 5.5.1-5.6.0 | |
 | <a name="3663182"></a> [3663182](#3663182) <a name="3663182"></a> <br /> | Changing non-default BGP timers with NCLU or vtysh commands sets the hold time and keep alive interval to 0 seconds. To work around this issue, restart the FRR service with the <code>sudo systemctl restart frr.service</code> command. | 5.3.1-5.6.0 | |
 | <a name="3647426"></a> [3647426](#3647426) <a name="3647426"></a> <br />None | If BGP <code>remote-as</code> is set to an integer and you try to configure the <code>local-as</code> for a BGP instance, you see the following error:<pre>% AS specified for local as is the same as the remote as and this is not allowed<br /></pre>This configuration is not allowed; it is considered to be eBGP and local preference is not advertised. | 5.0.0-5.5.1 | 4.3.2-4.4.5, 5.6.0|
 | <a name="3630492"></a> [3630492](#3630492) <a name="3630492"></a> <br /> | On the NVIDIA SN2201 switch, the <code>ledmgrd -d</code> command output shows the system and PSU LED status as orange when the physical LED is green. | 5.5.1-5.6.0 | |
@@ -42,6 +44,7 @@ pdfhidden: True
 | <a name="3534718"></a> [3534718](#3534718) <a name="3534718"></a> <br /> | The BGP command to suppress longer prefixes inside the aggregate address before sending updates (<code>nv set vrf <vrf> router bgp address-family <address-family> aggregate-route <address> summary-only</code> or vtysh <code>router bgp <asn> aggregate-address <address> summary-only</code>) does not suppress more specific routes from being exported into the EVPN routing table and advertised as EVPN type-5 routes. To work around this issue, announce EVPN type-5 routes by adding an additional outbound policy or export policy to filter out the more specific routes. | 5.5.0-5.6.0 | |
 | <a name="3528359"></a> [3528359](#3528359) <a name="3528359"></a> <br /> | A <code>switchd</code> assertion crash occurs after KVD resource exhaustion in the SDK because entries are in a pending delete state, which causes an ECMP allocation failure. | 5.5.0-5.5.1 | 5.6.0|
 | <a name="3526004"></a> [3526004](#3526004) <a name="3526004"></a> <br /> | For layer 3 VNIs, Cumulus Linux automatically creates an SVI name that includes an underscore (for example, <code>vlan4036_l3</code>), which is not allowed in SVI names. As a result, commands such as <code>nv show interface</code> for the SVI show an error. The underscore (_) character is now allowed in SVI names. | 5.5.0-5.5.1 | 5.6.0|
+| <a name="3522524"></a> [3522524](#3522524) <a name="3522524"></a> <br /> | FRR does not allow eBGP multi hop configuration on unnumbered BGP neighbors.  | 5.5.0-5.6.0 | |
 | <a name="3520511"></a> [3520511](#3520511) <a name="3520511"></a> <br /> | If you apply EVPN multihoming configuration such as <code>es-df-pref</code>, <code>es-id</code> and <code>es-sys-mac</code> with vtysh after you remove a bond interface that is part of a bridge and run <code>ifreload -a</code>, FRR crashes. To work around this issue, do not remove a bond from a bridge before you configure EVPN multihoming with vtysh. | 5.5.1 | 5.6.0|
 | <a name="3517376"></a> [3517376](#3517376) <a name="3517376"></a> <br /> | When you use CMIS specification based optics,  the <code>l1-show</code> command output provides incorrect values for digital diagnostics (TX Power and RX Power). To work around this issue, run the <code>mlxlink</code> command with either the <code>-m</code> or <code>--cable --ddm</code> flags. | 5.5.0-5.5.1 | 5.6.0|
 | <a name="3509445"></a> [3509445](#3509445) <a name="3509445"></a> <br /> | If a BGP numbered session is in a non-established state, SNMP walk commands to the system might time out when the BGPVRF MIB is included in the OIDs to collect. In addition, FRR might report warnings about AgentX in the log files. | 5.5.0-5.5.1 | 5.6.0|
@@ -163,6 +166,7 @@ pdfhidden: True
 | <a name="3534718"></a> [3534718](#3534718) <a name="3534718"></a> <br /> | The BGP command to suppress longer prefixes inside the aggregate address before sending updates (<code>nv set vrf <vrf> router bgp address-family <address-family> aggregate-route <address> summary-only</code> or vtysh <code>router bgp <asn> aggregate-address <address> summary-only</code>) does not suppress more specific routes from being exported into the EVPN routing table and advertised as EVPN type-5 routes. To work around this issue, announce EVPN type-5 routes by adding an additional outbound policy or export policy to filter out the more specific routes. | 5.5.0-5.6.0 | |
 | <a name="3528359"></a> [3528359](#3528359) <a name="3528359"></a> <br /> | A <code>switchd</code> assertion crash occurs after KVD resource exhaustion in the SDK because entries are in a pending delete state, which causes an ECMP allocation failure. | 5.5.0-5.5.1 | 5.6.0|
 | <a name="3526004"></a> [3526004](#3526004) <a name="3526004"></a> <br /> | For layer 3 VNIs, Cumulus Linux automatically creates an SVI name that includes an underscore (for example, <code>vlan4036_l3</code>), which is not allowed in SVI names. As a result, commands such as <code>nv show interface</code> for the SVI show an error. The underscore (_) character is now allowed in SVI names. | 5.5.0-5.5.1 | 5.6.0|
+| <a name="3522524"></a> [3522524](#3522524) <a name="3522524"></a> <br /> | FRR does not allow eBGP multi hop configuration on unnumbered BGP neighbors.  | 5.5.0-5.6.0 | |
 | <a name="3517376"></a> [3517376](#3517376) <a name="3517376"></a> <br /> | When you use CMIS specification based optics,  the <code>l1-show</code> command output provides incorrect values for digital diagnostics (TX Power and RX Power). To work around this issue, run the <code>mlxlink</code> command with either the <code>-m</code> or <code>--cable --ddm</code> flags. | 5.5.0-5.5.1 | 5.6.0|
 | <a name="3509445"></a> [3509445](#3509445) <a name="3509445"></a> <br /> | If a BGP numbered session is in a non-established state, SNMP walk commands to the system might time out when the BGPVRF MIB is included in the OIDs to collect. In addition, FRR might report warnings about AgentX in the log files. | 5.5.0-5.5.1 | 5.6.0|
 | <a name="3498939"></a> [3498939](#3498939) <a name="3498939"></a> <br /> | In an EVPN environment, VM migration (IP and MAC address migration) might not work because the new local VTEP to which the VM migrates does not install the entry in the kenel. To work around this issue, restart the <code>switchd</code> service. | 5.4.0-5.5.1 | 5.6.0|

diff --git a/content/cumulus-linux-55/rn.xml b/content/cumulus-linux-55/rn.xml
@@ -7,6 +7,18 @@
 <th> Fixed </th>
 </tr>
 <tr>
+<td>3695541</td>
+<td>When applying a full configuration with NVUE that includes VRRP and BGP in VRFs, the VRRP configuration does not come up after you run {{nv config apply}}.  BGP routes might also be missing.  This issue only happens during the initial {{nv config apply}} of a full configuration, not during a normal initialization during a reboot or FRR restart. To work around this issue, reboot or restart FRR.</td>
+<td>5.5.1</td>
+<td>5.6.0</td>
+</tr>
+<tr>
+<td>3668939</td>
+<td>When you enable MIB 1.3.6.1.4.1.40310.1 in the {{snmpd.conf}} file, you might see high CPU usage by the {{snmpd}} service.</td>
+<td>5.5.1-5.6.0</td>
+<td></td>
+</tr>
+<tr>
 <td>3663182</td>
 <td>Changing non-default BGP timers with NCLU or vtysh commands sets the hold time and keep alive interval to 0 seconds. To work around this issue, restart the FRR service with the {{sudo systemctl restart frr.service}} command.</td>
 <td>5.3.1-5.6.0</td>
@@ -187,6 +199,13 @@ For Cumulus Linux 4.3.2, the /usr/bin/ssh-agent program has all permissions turn
 <td>5.6.0</td>
 </tr>
 <tr>
+<td>3522524</td>
+<td>FRR does not allow eBGP multi hop configuration on unnumbered BGP neighbors. 
+</td>
+<td>5.5.0-5.6.0</td>
+<td></td>
+</tr>
+<tr>
 <td>3520511</td>
 <td>If you apply EVPN multihoming configuration such as {{es-df-pref}}, {{es-id}} and {{es-sys-mac}} with vtysh after you remove a bond interface that is part of a bridge and run {{ifreload -a}}, FRR crashes. To work around this issue, do not remove a bond from a bridge before you configure EVPN multihoming with vtysh.</td>
 <td>5.5.1</td>
@@ -955,6 +974,13 @@ For Cumulus Linux 4.3.2, the /usr/bin/ssh-agent program has all permissions turn
 <td>5.6.0</td>
 </tr>
 <tr>
+<td>3522524</td>
+<td>FRR does not allow eBGP multi hop configuration on unnumbered BGP neighbors. 
+</td>
+<td>5.5.0-5.6.0</td>
+<td></td>
+</tr>
+<tr>
 <td>3517376</td>
 <td>When you use CMIS specification based optics,  the {{l1-show}} command output provides incorrect values for digital diagnostics (TX Power and RX Power). To work around this issue, run the {{mlxlink}} command with either the {{-m}} or {{--cable --ddm}} flags.</td>
 <td>5.5.0-5.5.1</td>