You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: content/cumulus-linux-512/Whats-New/rn.md
-2Lines changed: 0 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -32,7 +32,6 @@ pdfhidden: True
32
32
| <aname="4667010"></a> [4667010](#4667010) <aname="4667010"></a> <br /> | When streaming telemetry is enabled, additional logs containing <code>ERROR BULK_COUNTER</code> might be generated by the switch, unexpectedly bypassing log suppression rules. | 5.12.1-5.14.0 | 5.15.0-5.15.1|
33
33
| <aname="4647646"></a> [4647646](#4647646) <aname="4647646"></a> <br /> | If you configure policy-based routing (PBR) rules for more than 32 interfaces, only the rules assigned to the first 32 interfaces are installed in the kernel. | 4.4.2-5.14.0 | 5.15.0-5.15.1|
34
34
| <aname="4643537"></a> [4643537](#4643537) <aname="4643537"></a> <br /> | The <code>nv action clear interface <port></code> command does not clear the in and out packet counters under <code>interface/<port>/link/stats</code>. | 5.12.1-5.14.0 | 5.15.0-5.15.1|
35
-
| <aname="4641326"></a> [4641326](#4641326) <aname="4641326"></a> <br /> | Trying to apply a hashed password of '*' blocks access to the switch instead of rejecting the password and showing an error. | 5.12.0-5.15.1 ||
36
35
| <aname="4640126"></a> [4640126](#4640126) <aname="4640126"></a> <br /> | LLDP session flaps might result in a PTMD process crash due to a double free memory block. | 5.11.2-5.14.0 | 5.15.0-5.15.1|
37
36
| <aname="4637200"></a> [4637200](#4637200) <aname="4637200"></a> <br /> | When more than one IPv4 and/or IPv6 addresses are configured on a remote interface, NVUE LLDP commands such as <code>nv show interface lldp-detail</code> only reflect one address. To work around this issue, use <code>lldpctl</code> to view LLDP information. For example, <code>sudo lldpctl -d -f json swp1</code>. | 5.9.0-5.14.0 | 5.15.0-5.15.1|
38
37
| <aname="4633514"></a> [4633514](#4633514) <aname="4633514"></a> <br /> | When the switch processes large numbers of mroute updates in an MLAG configuration, FRR might crash. | 5.8.0-5.14.0 | 5.15.0-5.15.1|
@@ -225,7 +224,6 @@ pdfhidden: True
225
224
| <aname="4714845"></a> [4714845](#4714845) <aname="4714845"></a> <br /> | The switch installs suboptimal routes in the routing table and advertises them out. | 5.9.2-5.15.1 ||
226
225
| <aname="4686865"></a> [4686865](#4686865) <aname="4686865"></a> <br /> | An invalid hashed-password string for a local NVUE user causes all <code>nv config apply</code> operations (including unrelated changes) to fail health checks and raise tracebacks when NVUE attempts to recreate the user. | 5.12.0-5.14.0 | 5.15.0-5.15.1|
227
226
| <aname="4647646"></a> [4647646](#4647646) <aname="4647646"></a> <br /> | If you configure policy-based routing (PBR) rules for more than 32 interfaces, only the rules assigned to the first 32 interfaces are installed in the kernel. | 4.4.2-5.14.0 | 5.15.0-5.15.1|
228
-
| <aname="4641326"></a> [4641326](#4641326) <aname="4641326"></a> <br /> | Trying to apply a hashed password of '*' blocks access to the switch instead of rejecting the password and showing an error. | 5.12.0-5.15.1 ||
229
227
| <aname="4640126"></a> [4640126](#4640126) <aname="4640126"></a> <br /> | LLDP session flaps might result in a PTMD process crash due to a double free memory block. | 5.11.2-5.14.0 | 5.15.0-5.15.1|
230
228
| <aname="4637200"></a> [4637200](#4637200) <aname="4637200"></a> <br /> | When more than one IPv4 and/or IPv6 addresses are configured on a remote interface, NVUE LLDP commands such as <code>nv show interface lldp-detail</code> only reflect one address. To work around this issue, use <code>lldpctl</code> to view LLDP information. For example, <code>sudo lldpctl -d -f json swp1</code>. | 5.9.0-5.14.0 | 5.15.0-5.15.1|
231
229
| <aname="4633514"></a> [4633514](#4633514) <aname="4633514"></a> <br /> | When the switch processes large numbers of mroute updates in an MLAG configuration, FRR might crash. | 5.8.0-5.14.0 | 5.15.0-5.15.1|
Copy file name to clipboardExpand all lines: content/cumulus-linux-513/Whats-New/rn.md
-2Lines changed: 0 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -37,7 +37,6 @@ pdfhidden: True
37
37
| <aname="4643537"></a> [4643537](#4643537) <aname="4643537"></a> <br /> | The <code>nv action clear interface <port></code> command does not clear the in and out packet counters under <code>interface/<port>/link/stats</code>. | 5.12.1-5.14.0 | 5.15.0-5.15.1|
38
38
| <aname="4641341"></a> [4641341](#4641341) <aname="4641341"></a> <br /> | The neighbor manager service memory usage increases significantly after the number of entries in the kernel neighbor table exceeds the <code>gc_threshold</code>. | 5.13.1-5.15.1 ||
39
39
| <aname="4641340"></a> [4641340](#4641340) <aname="4641340"></a> <br /> | The neighbor manager service memory usage increases significantly after the number of entries in the kernel neighbor table exceeds the <code>gc_threshold</code>. | 5.13.1-5.15.1 ||
40
-
| <aname="4641326"></a> [4641326](#4641326) <aname="4641326"></a> <br /> | Trying to apply a hashed password of '*' blocks access to the switch instead of rejecting the password and showing an error. | 5.12.0-5.15.1 ||
41
40
| <aname="4641291"></a> [4641291](#4641291) <aname="4641291"></a> <br /> | In rare circumstances, the switch stops streaming telemetry data for interface counters, buffers, or phy. | 5.13.1-5.14.0 | 5.15.0-5.15.1|
42
41
| <aname="4640126"></a> [4640126](#4640126) <aname="4640126"></a> <br /> | LLDP session flaps might result in a PTMD process crash due to a double free memory block. | 5.11.2-5.14.0 | 5.15.0-5.15.1|
43
42
| <aname="4637200"></a> [4637200](#4637200) <aname="4637200"></a> <br /> | When more than one IPv4 and/or IPv6 addresses are configured on a remote interface, NVUE LLDP commands such as <code>nv show interface lldp-detail</code> only reflect one address. To work around this issue, use <code>lldpctl</code> to view LLDP information. For example, <code>sudo lldpctl -d -f json swp1</code>. | 5.9.0-5.14.0 | 5.15.0-5.15.1|
@@ -261,7 +260,6 @@ pdfhidden: True
261
260
| <aname="4667010"></a> [4667010](#4667010) <aname="4667010"></a> <br /> | When streaming telemetry is enabled, additional logs containing <code>ERROR BULK_COUNTER</code> might be generated by the switch, unexpectedly bypassing log suppression rules. | 5.12.1-5.14.0 | 5.15.0-5.15.1|
262
261
| <aname="4647646"></a> [4647646](#4647646) <aname="4647646"></a> <br /> | If you configure policy-based routing (PBR) rules for more than 32 interfaces, only the rules assigned to the first 32 interfaces are installed in the kernel. | 4.4.2-5.14.0 | 5.15.0-5.15.1|
263
262
| <aname="4643537"></a> [4643537](#4643537) <aname="4643537"></a> <br /> | The <code>nv action clear interface <port></code> command does not clear the in and out packet counters under <code>interface/<port>/link/stats</code>. | 5.12.1-5.14.0 | 5.15.0-5.15.1|
264
-
| <aname="4641326"></a> [4641326](#4641326) <aname="4641326"></a> <br /> | Trying to apply a hashed password of '*' blocks access to the switch instead of rejecting the password and showing an error. | 5.12.0-5.15.1 ||
265
263
| <aname="4640126"></a> [4640126](#4640126) <aname="4640126"></a> <br /> | LLDP session flaps might result in a PTMD process crash due to a double free memory block. | 5.11.2-5.14.0 | 5.15.0-5.15.1|
266
264
| <aname="4637200"></a> [4637200](#4637200) <aname="4637200"></a> <br /> | When more than one IPv4 and/or IPv6 addresses are configured on a remote interface, NVUE LLDP commands such as <code>nv show interface lldp-detail</code> only reflect one address. To work around this issue, use <code>lldpctl</code> to view LLDP information. For example, <code>sudo lldpctl -d -f json swp1</code>. | 5.9.0-5.14.0 | 5.15.0-5.15.1|
267
265
| <aname="4633514"></a> [4633514](#4633514) <aname="4633514"></a> <br /> | When the switch processes large numbers of mroute updates in an MLAG configuration, FRR might crash. | 5.8.0-5.14.0 | 5.15.0-5.15.1|
Copy file name to clipboardExpand all lines: content/cumulus-linux-514/Whats-New/rn.md
-1Lines changed: 0 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -65,7 +65,6 @@ pdfhidden: True
65
65
| <aname="4641343"></a> [4641343](#4641343) <aname="4641343"></a> <br /> | The switch sends out IPv6 neighbor discovery (ND) router advertisement through an interface that does not have router advertisement enabled. To prevent this issue, do not change or remove the remote-as of a peer-group that is used by BGP unnumbered peers. To work around this issue, restart FRR. | 5.14.0-5.15.1 ||
66
66
| <aname="4641341"></a> [4641341](#4641341) <aname="4641341"></a> <br /> | The neighbor manager service memory usage increases significantly after the number of entries in the kernel neighbor table exceeds the <code>gc_threshold</code>. | 5.13.1-5.15.1 ||
67
67
| <aname="4641340"></a> [4641340](#4641340) <aname="4641340"></a> <br /> | The neighbor manager service memory usage increases significantly after the number of entries in the kernel neighbor table exceeds the <code>gc_threshold</code>. | 5.13.1-5.15.1 ||
68
-
| <aname="4641326"></a> [4641326](#4641326) <aname="4641326"></a> <br /> | Trying to apply a hashed password of '*' blocks access to the switch instead of rejecting the password and showing an error. | 5.12.0-5.15.1 ||
69
68
| <aname="4641291"></a> [4641291](#4641291) <aname="4641291"></a> <br /> | In rare circumstances, the switch stops streaming telemetry data for interface counters, buffers, or phy. | 5.13.1-5.14.0 | 5.15.0-5.15.1|
70
69
| <aname="4640126"></a> [4640126](#4640126) <aname="4640126"></a> <br /> | LLDP session flaps might result in a PTMD process crash due to a double free memory block. | 5.11.2-5.14.0 | 5.15.0-5.15.1|
71
70
| <aname="4638802"></a> [4638802](#4638802) <aname="4638802"></a> <br /> | When you attempt to set a new BGP peer group on a neighbor with a current peer group configured, NVUE fails to apply the new configuration. To work around this issue, remove the existing peer group before configuring the new one. | 5.14.0 | 5.15.0-5.15.1|
Copy file name to clipboardExpand all lines: content/cumulus-linux-515/Whats-New/rn.md
+3Lines changed: 3 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -171,6 +171,8 @@ pdfhidden: True
171
171
172
172
| Issue ID | Description | Affects | Fixed |
173
173
|--- |--- |--- |--- |
174
+
| <aname="4875599"></a> [4875599](#4875599) <aname="4875599"></a> <br /> | When you configure authentication for a BGP dynamic neighbor, removing the configuration does not bring back the sessions. | 5.15.0-5.15.1 ||
175
+
| <aname="4873853"></a> [4873853](#4873853) <aname="4873853"></a> <br /> | TACACS authentication is not working with flat files. The Cumulus Linux user guide is missing the <code>sudo pam-auth-update --enable tacplus</code> command. | 5.15.0-5.15.1 ||
174
176
| <aname="4859201"></a> [4859201](#4859201) <aname="4859201"></a> <br /> | When the VNI changes on a VRF, from the old VNI to the new VNI, the VNI in the SVD VNI hash table or in the single‑VNI (SVD) in the VNI info is deleted. Therefore, when there are further updates to the old VNI, the lookup fails and causes the zebra core to crash. | 5.14.0-5.15.1 ||
175
177
| <aname="4850551"></a> [4850551](#4850551) <aname="4850551"></a> <br /> | The switch installs suboptimal routes in the routing table and advertises them out. | 5.9.2-5.15.1 ||
176
178
| <aname="4850188"></a> [4850188](#4850188) <aname="4850188"></a> <br /> | Signal quality degradation is observed during SR4-100G to 4×25G breakout using an adapter. | 5.15.0-5.15.1 ||
@@ -193,6 +195,7 @@ pdfhidden: True
193
195
| <aname="4781498"></a> [4781498](#4781498) <aname="4781498"></a> <br /> | When you use a text-based patch file with <code>nv config patch cmd.txt</code> or <code>nv config replace cmd.txt</code>, if the <code>cmd.txt</code> file contains any of the following CLI commands, the patch operation fails and triggers an exception in NVUE:<br><pre>nv set system aaa auth order radius <array><br>nv set system ssh-server ciphers <array><br>nv set system ssh-server macs <array><br>nv set system ssh-server kex-algorithms <array><br>nv set system ssh-server pubkey-accepted-algorithms <array><br>nv set system ssh-server host-key-algorithms <array></pre> <br>To work around this issue, use a YAML file instead of a text-based patch file or run the <code>nv set</code> commands manually. | 5.15.0-5.15.1 ||
194
196
| <aname="4776471"></a> [4776471](#4776471) <aname="4776471"></a> <br /> | In Cumulus Linux 5.15.0, NTP and DNS configuration commands changed from <code>nv set service</code> to <code>nv set system</code>. However, after upgrading the switch to Cumulus Linux 5.15.1, the <code>nv set service</code> command might still appear in the configuration output because a stale <code>nv set service</code> command remains after the configuration is translated during the upgrade. If you save the configuration with the <code>nv config show -o commands</code>, then reapply the configuration with <code>nv config replace</code>, the command fails if the stale <code>nv set service</code> command is present.<br>To workaround this issue, before applying the configuration with <code>nv config replace</code>, remove any stale <code>nv set service</code> commands from the saved configuration file, then reapply the configuration with the <code>nv config replace <config-file></code> command. | 5.15.0-5.15.1 ||
195
197
| <aname="4776470"></a> [4776470](#4776470) <aname="4776470"></a> <br /> | In Cumulus Linux 5.15.0, NTP and DNS configuration commands changed from <code>nv set service</code> to <code>nv set system</code>. However, after upgrading the switch to Cumulus Linux 5.15.1, the <code>nv set service</code> command might still appear in the configuration output because a stale <code>nv set service</code> command remains after the configuration is translated during the upgrade. If you save the configuration with the <code>nv config show -o commands</code>, then reapply the configuration with <code>nv config replace</code>, the command fails if the stale <code>nv set service</code> command is present.<br>To workaround this issue, before applying the configuration with <code>nv config replace</code>, remove any stale <code>nv set service</code> commands from the saved configuration file, then reapply the configuration with the <code>nv config replace <config-file></code> command. | 5.15.0-5.15.1 ||
198
+
| <aname="4776444"></a> [4776444](#4776444) <aname="4776444"></a> <br /> | In rare cases when telemetry is configured on a switch with high interface scale, the following log message might be generated and lead to a kernel crash event:<br><pre>interface_stats_collector[27979]: ERROR intf_stats_collector.go:485 WaitBulkCounterDone error: unable to receive trap info after 15 iterations</pre> | 5.15.0-5.15.1 ||
196
199
| <aname="4776390"></a> [4776390](#4776390) <aname="4776390"></a> <br /> | gNMI subscription changes for interface counters, buffer, packet trim, latency or any other statistics produced by the <code>prometheus-sdk-stats</code> service leads to a change in the service configuration file causing the load interval configuration to be removed. This results in a rate calculation done with an interval of 60s instead of the interval configured in NVUE. | 5.15.0-5.15.1 ||
197
200
| <aname="4771875"></a> [4771875](#4771875) <aname="4771875"></a> <br /> | When you poll optical module data with <code>ethtool -m</code>, <code>switchd</code> might crash due to a firmware timeout that triggers a fatal health-check failure. | 5.11.1-5.15.1 ||
198
201
| <aname="4771865"></a> [4771865](#4771865) <aname="4771865"></a> <br /> | When you change the RADIUS privilege level, all affected existing RADIUS users are not updated in the next session to the relevant privilege level. | 5.15.0-5.15.1 ||
<td>When you configure authentication for a BGP dynamic neighbor, removing the configuration does not bring back the sessions.</td>
966
+
<td>5.15.0-5.15.1</td>
967
+
<td></td>
968
+
</tr>
969
+
<tr>
970
+
<td>4873853</td>
971
+
<td>TACACS authentication is not working with flat files. The Cumulus Linux user guide is missing the {{sudo pam-auth-update --enable tacplus}} command.</td>
972
+
<td>5.15.0-5.15.1</td>
973
+
<td></td>
974
+
</tr>
975
+
<tr>
964
976
<td>4859201</td>
965
977
<td>When the VNI changes on a VRF, from the old VNI to the new VNI, the VNI in the SVD VNI hash table or in the single‑VNI (SVD) in the VNI info is deleted. Therefore, when there are further updates to the old VNI, the lookup fails and causes the zebra core to crash. </td>
966
978
<td>5.14.0-5.15.1</td>
@@ -1105,6 +1117,15 @@ To work around this issue, use a YAML file instead of a text-based patch file or
1105
1117
<td></td>
1106
1118
</tr>
1107
1119
<tr>
1120
+
<td>4776444</td>
1121
+
<td>In rare cases when telemetry is configured on a switch with high interface scale, the following log message might be generated and lead to a kernel crash event:
1122
+
1123
+
interface_stats_collector[27979]: ERROR intf_stats_collector.go:485 WaitBulkCounterDone error: unable to receive trap info after 15 iterations
1124
+
</td>
1125
+
<td>5.15.0-5.15.1</td>
1126
+
<td></td>
1127
+
</tr>
1128
+
<tr>
1108
1129
<td>4776390</td>
1109
1130
<td>gNMI subscription changes for interface counters, buffer, packet trim, latency or any other statistics produced by the {{prometheus-sdk-stats}} service leads to a change in the service configuration file causing the load interval configuration to be removed. This results in a rate calculation done with an interval of 60s instead of the interval configured in NVUE.</td>
0 commit comments