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-511/Whats-New/rn.md
-4Lines changed: 0 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -175,7 +175,6 @@ pdfhidden: True
175
175
| <aname="4797691"></a> [4797691](#4797691) <aname="4797691"></a> <br /> | The message that the switch displays when you generate a cl-support file or as a post login banner contains an invalid Cumulus Support email address, which is no longer the formal channel for reporting support issues. | 5.0.0-5.15.1 ||
176
176
| <aname="4789097"></a> [4789097](#4789097) <aname="4789097"></a> <br /> | The switch deletes a static blackhole route even when the blackhole type specified in the delete command does not match the configured type. | 5.9.4-5.15.1 ||
177
177
| <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 ||
178
-
| <aname="4771874"></a> [4771874](#4771874) <aname="4771874"></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 ||
179
178
| <aname="4771521"></a> [4771521](#4771521) <aname="4771521"></a> <br /> | Layer 3 multicast traffic does not forward when OMF (Optimized Multicast Flooding) and PIM is enabled. To work around this issue, flap the router port. | 5.9.2-5.15.1 ||
180
179
| <aname="4722539"></a> [4722539](#4722539) <aname="4722539"></a> <br /> | Optimized image upgrade with warm boot mode is supported in Cumulus Linux 5.13 and later. When you try to run the <code>nv action boot-next</code> command during optimized image upgrade in Cumulus Linux 5.12 and earlier to any target release while the system is in warm boot mode, the <code>boot-next</code> operation fails with the following error:<br><pre>cumulus@switch:~$ nv action boot-next system image other<br>Error: Action failed with the following issue:>br><br /> Failed to set boot-next due to Unknown error</pre><br>To work around this issue, verify system boot mode with the <code>nv show system reboot</code> command before you perform optimized image upgrade and switch to cold boot mode if necessary with the <code>nv set system reboot mode cold</code> command. You can then proceed with the optimized image upgrade <code>boot-next</code> operation. | 5.11.4-5.15.1 ||
181
180
| <aname="4721298"></a> [4721298](#4721298) <aname="4721298"></a> <br /> | When node or VM migration occurs between the MLAG pair and the EVPN-MH pair, the MLAG MAC database becomes out of sync with kernel FDB. The migrated MAC addresses remain as local in MLAG MAC database whereas in the kernel, all MAC addresses are updated correctly as remote with the layer 2 next hop ID. To work around this issue, flap the MLAG bond interface to clear the MLAG local database. | 5.11.0-5.15.1 ||
@@ -334,7 +333,6 @@ pdfhidden: True
334
333
| <aname="4797691"></a> [4797691](#4797691) <aname="4797691"></a> <br /> | The message that the switch displays when you generate a cl-support file or as a post login banner contains an invalid Cumulus Support email address, which is no longer the formal channel for reporting support issues. | 5.0.0-5.15.1 ||
335
334
| <aname="4789097"></a> [4789097](#4789097) <aname="4789097"></a> <br /> | The switch deletes a static blackhole route even when the blackhole type specified in the delete command does not match the configured type. | 5.9.4-5.15.1 ||
336
335
| <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 ||
337
-
| <aname="4771874"></a> [4771874](#4771874) <aname="4771874"></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 ||
338
336
| <aname="4771521"></a> [4771521](#4771521) <aname="4771521"></a> <br /> | Layer 3 multicast traffic does not forward when OMF (Optimized Multicast Flooding) and PIM is enabled. To work around this issue, flap the router port. | 5.9.2-5.15.1 ||
339
337
| <aname="4721298"></a> [4721298](#4721298) <aname="4721298"></a> <br /> | When node or VM migration occurs between the MLAG pair and the EVPN-MH pair, the MLAG MAC database becomes out of sync with kernel FDB. The migrated MAC addresses remain as local in MLAG MAC database whereas in the kernel, all MAC addresses are updated correctly as remote with the layer 2 next hop ID. To work around this issue, flap the MLAG bond interface to clear the MLAG local database. | 5.11.0-5.15.1 ||
340
338
| <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 ||
@@ -492,7 +490,6 @@ pdfhidden: True
492
490
| <aname="4797691"></a> [4797691](#4797691) <aname="4797691"></a> <br /> | The message that the switch displays when you generate a cl-support file or as a post login banner contains an invalid Cumulus Support email address, which is no longer the formal channel for reporting support issues. | 5.0.0-5.15.1 ||
493
491
| <aname="4789097"></a> [4789097](#4789097) <aname="4789097"></a> <br /> | The switch deletes a static blackhole route even when the blackhole type specified in the delete command does not match the configured type. | 5.9.4-5.15.1 ||
494
492
| <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 ||
495
-
| <aname="4771874"></a> [4771874](#4771874) <aname="4771874"></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 ||
496
493
| <aname="4771521"></a> [4771521](#4771521) <aname="4771521"></a> <br /> | Layer 3 multicast traffic does not forward when OMF (Optimized Multicast Flooding) and PIM is enabled. To work around this issue, flap the router port. | 5.9.2-5.15.1 ||
497
494
| <aname="4721298"></a> [4721298](#4721298) <aname="4721298"></a> <br /> | When node or VM migration occurs between the MLAG pair and the EVPN-MH pair, the MLAG MAC database becomes out of sync with kernel FDB. The migrated MAC addresses remain as local in MLAG MAC database whereas in the kernel, all MAC addresses are updated correctly as remote with the layer 2 next hop ID. To work around this issue, flap the MLAG bond interface to clear the MLAG local database. | 5.11.0-5.15.1 ||
498
495
| <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 ||
@@ -689,7 +686,6 @@ pdfhidden: True
689
686
| <aname="4797691"></a> [4797691](#4797691) <aname="4797691"></a> <br /> | The message that the switch displays when you generate a cl-support file or as a post login banner contains an invalid Cumulus Support email address, which is no longer the formal channel for reporting support issues. | 5.0.0-5.15.1 ||
690
687
| <aname="4789097"></a> [4789097](#4789097) <aname="4789097"></a> <br /> | The switch deletes a static blackhole route even when the blackhole type specified in the delete command does not match the configured type. | 5.9.4-5.15.1 ||
691
688
| <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 ||
692
-
| <aname="4771874"></a> [4771874](#4771874) <aname="4771874"></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 ||
693
689
| <aname="4771521"></a> [4771521](#4771521) <aname="4771521"></a> <br /> | Layer 3 multicast traffic does not forward when OMF (Optimized Multicast Flooding) and PIM is enabled. To work around this issue, flap the router port. | 5.9.2-5.15.1 ||
694
690
| <aname="4721298"></a> [4721298](#4721298) <aname="4721298"></a> <br /> | When node or VM migration occurs between the MLAG pair and the EVPN-MH pair, the MLAG MAC database becomes out of sync with kernel FDB. The migrated MAC addresses remain as local in MLAG MAC database whereas in the kernel, all MAC addresses are updated correctly as remote with the layer 2 next hop ID. To work around this issue, flap the MLAG bond interface to clear the MLAG local database. | 5.11.0-5.15.1 ||
695
691
| <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 ||
<td>When you poll optical module data with {{ethtool -m}}, {{switchd}} might crash due to a firmware timeout that triggers a fatal health-check failure.</td>
999
-
<td>5.11.1-5.15.1</td>
1000
-
<td></td>
1001
-
</tr>
1002
-
<tr>
1003
997
<td>4771521</td>
1004
998
<td>Layer 3 multicast traffic does not forward when OMF (Optimized Multicast Flooding) and PIM is enabled. To work around this issue, flap the router port.</td>
1005
999
<td>5.9.2-5.15.1</td>
@@ -1970,12 +1964,6 @@ NOTICE CORE_ASYNC: Error at pre send callback status [Resource is in use]</td>
1970
1964
<td></td>
1971
1965
</tr>
1972
1966
<tr>
1973
-
<td>4771874</td>
1974
-
<td>When you poll optical module data with {{ethtool -m}}, {{switchd}} might crash due to a firmware timeout that triggers a fatal health-check failure.</td>
1975
-
<td>5.11.1-5.15.1</td>
1976
-
<td></td>
1977
-
</tr>
1978
-
<tr>
1979
1967
<td>4771521</td>
1980
1968
<td>Layer 3 multicast traffic does not forward when OMF (Optimized Multicast Flooding) and PIM is enabled. To work around this issue, flap the router port.</td>
<td>When you poll optical module data with {{ethtool -m}}, {{switchd}} might crash due to a firmware timeout that triggers a fatal health-check failure.</td>
2942
-
<td>5.11.1-5.15.1</td>
2943
-
<td></td>
2944
-
</tr>
2945
-
<tr>
2946
2928
<td>4771521</td>
2947
2929
<td>Layer 3 multicast traffic does not forward when OMF (Optimized Multicast Flooding) and PIM is enabled. To work around this issue, flap the router port.</td>
2948
2930
<td>5.9.2-5.15.1</td>
@@ -4121,12 +4103,6 @@ nv config apply -y</td>
4121
4103
<td></td>
4122
4104
</tr>
4123
4105
<tr>
4124
-
<td>4771874</td>
4125
-
<td>When you poll optical module data with {{ethtool -m}}, {{switchd}} might crash due to a firmware timeout that triggers a fatal health-check failure.</td>
4126
-
<td>5.11.1-5.15.1</td>
4127
-
<td></td>
4128
-
</tr>
4129
-
<tr>
4130
4106
<td>4771521</td>
4131
4107
<td>Layer 3 multicast traffic does not forward when OMF (Optimized Multicast Flooding) and PIM is enabled. To work around this issue, flap the router port.</td>
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
@@ -19,7 +19,6 @@ pdfhidden: True
19
19
| <aname="4789562"></a> [4789562](#4789562) <aname="4789562"></a> <br /> | A switch running Nvidia Cumulus Linux may improperly forward routed packets out of an access port or on the native vlan of a trunk with an 802.1Q tag imposed on the packet. | 5.12.1-5.15.1 ||
20
20
| <aname="4789097"></a> [4789097](#4789097) <aname="4789097"></a> <br /> | The switch deletes a static blackhole route even when the blackhole type specified in the delete command does not match the configured type. | 5.9.4-5.15.1 ||
21
21
| <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 ||
22
-
| <aname="4771874"></a> [4771874](#4771874) <aname="4771874"></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 ||
23
22
| <aname="4771521"></a> [4771521](#4771521) <aname="4771521"></a> <br /> | Layer 3 multicast traffic does not forward when OMF (Optimized Multicast Flooding) and PIM is enabled. To work around this issue, flap the router port. | 5.9.2-5.15.1 ||
24
23
| <aname="4751060"></a> [4751060](#4751060) <aname="4751060"></a> <br /> | If the switch filesystem is overloaded or memory is exhausted, you see very slow responses from the filesystem and the SDK might fail with a fatal error similar to:<br><pre>sxd_kernel: Health-Check: new failure (dev=1, severity='Fatal', cause=10 ['SDK thread issue'], irisc=255, desc='Health check: SDK thread [sxSniffer] TID [0x7f81cffff6c0] bit [4] does not respond [5] seconds')</pre> | 5.12.0-5.15.1 ||
25
24
| <aname="4748176"></a> [4748176](#4748176) <aname="4748176"></a> <br /> | Unsupported hardware modules might cause SDK and firmware health event and traffic loss. | 5.12.1-5.15.1 ||
@@ -213,7 +212,6 @@ pdfhidden: True
213
212
| <aname="4797691"></a> [4797691](#4797691) <aname="4797691"></a> <br /> | The message that the switch displays when you generate a cl-support file or as a post login banner contains an invalid Cumulus Support email address, which is no longer the formal channel for reporting support issues. | 5.0.0-5.15.1 ||
214
213
| <aname="4789097"></a> [4789097](#4789097) <aname="4789097"></a> <br /> | The switch deletes a static blackhole route even when the blackhole type specified in the delete command does not match the configured type. | 5.9.4-5.15.1 ||
215
214
| <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 ||
216
-
| <aname="4771874"></a> [4771874](#4771874) <aname="4771874"></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 ||
217
215
| <aname="4771521"></a> [4771521](#4771521) <aname="4771521"></a> <br /> | Layer 3 multicast traffic does not forward when OMF (Optimized Multicast Flooding) and PIM is enabled. To work around this issue, flap the router port. | 5.9.2-5.15.1 ||
218
216
| <aname="4751060"></a> [4751060](#4751060) <aname="4751060"></a> <br /> | If the switch filesystem is overloaded or memory is exhausted, you see very slow responses from the filesystem and the SDK might fail with a fatal error similar to:<br><pre>sxd_kernel: Health-Check: new failure (dev=1, severity='Fatal', cause=10 ['SDK thread issue'], irisc=255, desc='Health check: SDK thread [sxSniffer] TID [0x7f81cffff6c0] bit [4] does not respond [5] seconds')</pre> | 5.12.0-5.15.1 ||
219
217
| <aname="4722539"></a> [4722539](#4722539) <aname="4722539"></a> <br /> | Optimized image upgrade with warm boot mode is supported in Cumulus Linux 5.13 and later. When you try to run the <code>nv action boot-next</code> command during optimized image upgrade in Cumulus Linux 5.12 and earlier to any target release while the system is in warm boot mode, the <code>boot-next</code> operation fails with the following error:<br><pre>cumulus@switch:~$ nv action boot-next system image other<br>Error: Action failed with the following issue:>br><br /> Failed to set boot-next due to Unknown error</pre><br>To work around this issue, verify system boot mode with the <code>nv show system reboot</code> command before you perform optimized image upgrade and switch to cold boot mode if necessary with the <code>nv set system reboot mode cold</code> command. You can then proceed with the optimized image upgrade <code>boot-next</code> operation. | 5.11.4-5.15.1 ||
Copy file name to clipboardExpand all lines: content/cumulus-linux-512/rn.xml
-12Lines changed: 0 additions & 12 deletions
Original file line number
Diff line number
Diff line change
@@ -37,12 +37,6 @@
37
37
<td></td>
38
38
</tr>
39
39
<tr>
40
-
<td>4771874</td>
41
-
<td>When you poll optical module data with {{ethtool -m}}, {{switchd}} might crash due to a firmware timeout that triggers a fatal health-check failure.</td>
42
-
<td>5.11.1-5.15.1</td>
43
-
<td></td>
44
-
</tr>
45
-
<tr>
46
40
<td>4771521</td>
47
41
<td>Layer 3 multicast traffic does not forward when OMF (Optimized Multicast Flooding) and PIM is enabled. To work around this issue, flap the router port.</td>
<td>When you poll optical module data with {{ethtool -m}}, {{switchd}} might crash due to a firmware timeout that triggers a fatal health-check failure.</td>
1238
-
<td>5.11.1-5.15.1</td>
1239
-
<td></td>
1240
-
</tr>
1241
-
<tr>
1242
1230
<td>4771521</td>
1243
1231
<td>Layer 3 multicast traffic does not forward when OMF (Optimized Multicast Flooding) and PIM is enabled. To work around this issue, flap the router port.</td>
0 commit comments