Skip to content

Commit 815caa7

Browse files
author
Cumulus Docs Auto Merge
committed
Merge remote-tracking branch 'origin/stage'
2 parents 267ef76 + 1d330d6 commit 815caa7

File tree

27 files changed

+524
-1086
lines changed

27 files changed

+524
-1086
lines changed

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

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -195,13 +195,13 @@ pdfhidden: True
195195
| <a name="4423248"></a> [4423248](#4423248) <a name="4423248"></a> <br /> | If you unset an interface static IP address when the interface IP gateway is configured, the <code>nv config apply</code> command fails with an <code>ifreload.service</code> error. To work around this issue, unset both the static IP address and gateway together. | 5.9.0-5.16.1 | |
196196
| <a name="4423244"></a> [4423244](#4423244) <a name="4423244"></a> <br /> | When you enable, then disable adaptive routing, the BGP neighbors might go down because of an unresolved MAC address. To work around this issue, configure another attribute on the interface. | 5.9.0-5.16.1 | |
197197
| <a name="4422898, 4497128"></a> [4422898, 4497128](#4422898, 4497128) <a name="4422898, 4497128"></a> <br /> | When displaying BGP neighbor advertised routes in JSON format with very large routing tables, the process consumes excessive memory resulting in out of memory crashes. | 5.0.0-5.13.1 | 5.14.0-5.16.1|
198-
| <a name="4220147"></a> [4220147](#4220147) <a name="4220147"></a> <br /> | When you bring STP down, then up on the primary MLAG peer, the STP state machine restarts and the peerlink operational edge resets. As a result, the secondary MLAG peer ends up in an STP discarding state. To work around this issue, restart the <code>clagd</code> service. | 5.8.0-5.11.0 | 5.11.1-5.16.1, 5.12.0-5.16.1|
198+
| <a name="4281099"></a> [4281099](#4281099) <a name="4281099"></a> <br /> | When you bring STP down, then up on the primary MLAG peer, the STP state machine restarts and the peerlink operational edge resets. As a result, the secondary MLAG peer ends up in an STP discarding state. To work around this issue, restart the <code>clagd</code> service. | 5.8.0-5.11.5 | 5.12.0-5.16.1|
199+
| <a name="4260012"></a> [4260012](#4260012) <a name="4260012"></a> <br /> | If all of the neighbors returned in the <code>nv show vrf <vrf> router bgp neighbor</code> command output have no <code>address-family</code> configuration, you see an internal error when the nested table in the output is being rendered. | 5.10.0-5.11.5 | 5.12.0-5.16.1|
200+
| <a name="4259980"></a> [4259980](#4259980) <a name="4259980"></a> <br /> | After you reboot the switch, the ifplugd.service fails to start monitoring the interface. | 5.8.0-5.9.3, 5.10.0-5.11.5 | 5.9.4, 5.12.0-5.16.1|
201+
| <a name="4223451"></a> [4223451](#4223451) <a name="4223451"></a> <br /> | When you change the VRR MAC address, <code>switchd</code> crashes. This occurs because deleting an old VRR MAC address triggers a neighbor update that changes the ECMP container resolution, which results in route entry updates<br />This happens in async mode, where the end notification expected after an end of operation is missing. | 5.9.2-5.11.5 | 5.12.0-5.16.1|
202+
| <a name="4200961"></a> [4200961](#4200961) <a name="4200961"></a> <br /> | If you use a bridge name other than <code>br_default</code>, PTP neighbors fail to establish because the PTP packets are sourced from an unexpected IP address.<br>To work around this issue, configure the <code>base-interface</code> for the VLAN interface with the <code>nv set interface <VLAN-id> base-interface <interface-id></code> command. | 5.10.0-5.11.5 | 5.12.0-5.16.1|
199203
| <a name="4195240"></a> [4195240](#4195240) <a name="4195240"></a> <br /> | Cumulus Linux installs and runs the <code>atftpd</code> program by default but cannot access it because a <code>/tftpboot</code> directory is missing. | 5.9.2-5.11.5 | 5.12.0-5.16.1|
200-
| <a name="4185962"></a> [4185962](#4185962) <a name="4185962"></a> <br /> | When you change the VRR MAC address, <code>switchd</code> crashes. This occurs because deleting an old VRR MAC address triggers a neighbor update that changes the ECMP container resolution, which results in route entry updates<br />This happens in async mode, where the end notification expected after an end of operation is missing. | 5.9.2-5.11.0 | 5.11.1-5.16.1, 5.12.0-5.16.1|
201204
| <a name="4178578"></a> [4178578](#4178578) <a name="4178578"></a> <br /> | An unexpected thermal reboot occurs due to an incorrect firmware status in the i2c driver. | 5.10.0-5.11.0 | 5.11.1-5.16.1|
202-
| <a name="4175695"></a> [4175695](#4175695) <a name="4175695"></a> <br /> | If all of the neighbors returned in the <code>nv show vrf <vrf> router bgp neighbor</code> command output have no <code>address-family</code> configuration, you see an internal error when the nested table in the output is being rendered. | 5.10.0-5.11.0 | 5.11.1-5.16.1, 5.12.0-5.16.1|
203-
| <a name="4170628"></a> [4170628](#4170628) <a name="4170628"></a> <br /> | If you use a bridge name other than <code>br_default</code>, PTP neighbors fail to establish because the PTP packets are sourced from an unexpected IP address.<br>To work around this issue, configure the <code>base-interface</code> for the VLAN interface with the <code>nv set interface <VLAN-id> base-interface <interface-id></code> command. | 5.10.0-5.11.0 | 5.11.1-5.16.1, 5.12.0-5.16.1|
204-
| <a name="4151336"></a> [4151336](#4151336) <a name="4151336"></a> <br /> | After you reboot the switch, the ifplugd.service fails to start monitoring the interface. | 5.8.0-5.9.3, 5.10.0-5.11.0 | 5.9.4, 5.11.1-5.16.1, 5.12.0-5.16.1|
205205
| <a name="4144021"></a> [4144021](#4144021) <a name="4144021"></a> <br /> | Shutting down port 65 or 66 on the NVIDIA Spectrum-4 switch leaves the opposite port up when using MLNX SFP-T and RJ45 connections. Spectrum-4 switches do not support SFP-T modules on ports 65 and 66. | 5.10.0-5.12.1 | 5.13.0-5.16.1|
206206
| <a name="4142857"></a> [4142857](#4142857) <a name="4142857"></a> <br /> | The switch drops PTP packets received with extra ethernet padding and you see syslog <code>&#91;ptp4l.ERR&#93; messages. | 5.10.0-5.16.1 | |
207207
| <a name="4129699, 3790461"></a> [4129699, 3790461](#4129699, 3790461) <a name="4129699, 3790461"></a> <br /> | <code>switchd</code> crashes because the hardware MAC limit is higher than the maximum. | 5.8.0-5.10.1 | 5.11.0-5.16.1|

‎content/cumulus-linux-510/rn.xml‎

Lines changed: 26 additions & 26 deletions
Original file line numberDiff line numberDiff line change
@@ -1103,47 +1103,47 @@ To work around this issue, power cycle the switch.</td>
11031103
<td>5.14.0-5.16.1</td>
11041104
</tr>
11051105
<tr>
1106-
<td>4220147</td>
1106+
<td>4281099</td>
11071107
<td>When you bring STP down, then up on the primary MLAG peer, the STP state machine restarts and the peerlink operational edge resets. As a result, the secondary MLAG peer ends up in an STP discarding state. To work around this issue, restart the {{clagd}} service.</td>
1108-
<td>5.8.0-5.11.0</td>
1109-
<td>5.11.1-5.16.1, 5.12.0-5.16.1</td>
1108+
<td>5.8.0-5.11.5</td>
1109+
<td>5.12.0-5.16.1</td>
11101110
</tr>
11111111
<tr>
1112-
<td>4195240</td>
1113-
<td>Cumulus Linux installs and runs the {{atftpd}} program by default but cannot access it because a {{/tftpboot}} directory is missing.</td>
1114-
<td>5.9.2-5.11.5</td>
1112+
<td>4260012</td>
1113+
<td>If all of the neighbors returned in the {{nv show vrf &lt;vrf&gt; router bgp neighbor}} command output have no {{address-family}} configuration, you see an internal error when the nested table in the output is being rendered.</td>
1114+
<td>5.10.0-5.11.5</td>
11151115
<td>5.12.0-5.16.1</td>
11161116
</tr>
11171117
<tr>
1118-
<td>4185962</td>
1118+
<td>4259980</td>
1119+
<td>After you reboot the switch, the ifplugd.service fails to start monitoring the interface.</td>
1120+
<td>5.8.0-5.9.3, 5.10.0-5.11.5</td>
1121+
<td>5.9.4, 5.12.0-5.16.1</td>
1122+
</tr>
1123+
<tr>
1124+
<td>4223451</td>
11191125
<td>When you change the VRR MAC address, {{switchd}} crashes. This occurs because deleting an old VRR MAC address triggers a neighbor update that changes the ECMP container resolution, which results in route entry updates.
11201126
This happens in async mode, where the end notification expected after an end of operation is missing.</td>
1121-
<td>5.9.2-5.11.0</td>
1122-
<td>5.11.1-5.16.1, 5.12.0-5.16.1</td>
1127+
<td>5.9.2-5.11.5</td>
1128+
<td>5.12.0-5.16.1</td>
11231129
</tr>
11241130
<tr>
1125-
<td>4178578</td>
1126-
<td>An unexpected thermal reboot occurs due to an incorrect firmware status in the i2c driver.</td>
1127-
<td>5.10.0-5.11.0</td>
1128-
<td>5.11.1-5.16.1</td>
1131+
<td>4200961</td>
1132+
<td>If you use a bridge name other than {{br_default}}, PTP neighbors fail to establish because the PTP packets are sourced from an unexpected IP address.To work around this issue, configure the {{base-interface}} for the VLAN interface with the {{nv set interface &lt;VLAN-id&gt; base-interface &lt;interface-id&gt;}} command.</td>
1133+
<td>5.10.0-5.11.5</td>
1134+
<td>5.12.0-5.16.1</td>
11291135
</tr>
11301136
<tr>
1131-
<td>4175695</td>
1132-
<td>If all of the neighbors returned in the {{nv show vrf &lt;vrf&gt; router bgp neighbor}} command output have no {{address-family}} configuration, you see an internal error when the nested table in the output is being rendered.</td>
1133-
<td>5.10.0-5.11.0</td>
1134-
<td>5.11.1-5.16.1, 5.12.0-5.16.1</td>
1137+
<td>4195240</td>
1138+
<td>Cumulus Linux installs and runs the {{atftpd}} program by default but cannot access it because a {{/tftpboot}} directory is missing.</td>
1139+
<td>5.9.2-5.11.5</td>
1140+
<td>5.12.0-5.16.1</td>
11351141
</tr>
11361142
<tr>
1137-
<td>4170628</td>
1138-
<td>If you use a bridge name other than {{br_default}}, PTP neighbors fail to establish because the PTP packets are sourced from an unexpected IP address.To work around this issue, configure the {{base-interface}} for the VLAN interface with the {{nv set interface &lt;VLAN-id&gt; base-interface &lt;interface-id&gt;}} command.</td>
1143+
<td>4178578</td>
1144+
<td>An unexpected thermal reboot occurs due to an incorrect firmware status in the i2c driver.</td>
11391145
<td>5.10.0-5.11.0</td>
1140-
<td>5.11.1-5.16.1, 5.12.0-5.16.1</td>
1141-
</tr>
1142-
<tr>
1143-
<td>4151336</td>
1144-
<td>After you reboot the switch, the ifplugd.service fails to start monitoring the interface.</td>
1145-
<td>5.8.0-5.9.3, 5.10.0-5.11.0</td>
1146-
<td>5.9.4, 5.11.1-5.16.1, 5.12.0-5.16.1</td>
1146+
<td>5.11.1-5.16.1</td>
11471147
</tr>
11481148
<tr>
11491149
<td>4144021</td>

0 commit comments

Comments
 (0)