diff --git a/content/cumulus-linux-510/Whats-New/rn.md b/content/cumulus-linux-510/Whats-New/rn.md
index 16d23303de..cf154c4336 100644
--- a/content/cumulus-linux-510/Whats-New/rn.md
+++ b/content/cumulus-linux-510/Whats-New/rn.md
@@ -14,10 +14,10 @@ pdfhidden: True
| Issue ID | Description | Affects | Fixed |
|--- |--- |--- |--- |
+| [4175217](#4175217)
| When there is a large number of discontiguous VTEP to VLAN mappings, switchd
crashes with a Netlink error similar to the following:
| 5.10.1-5.11.0 | | | [4173498](#4173498)
netlink.c:409 CRIT nlroute: nl_cache_mngr_data_ready failed: Kernel reported truncated message
watchfrr
process might restart FRR because zebra is unresponsive. | 5.9.1-5.11.0 | |
| [4170628](#4170628) br_default
, NVUE generates incorrect ptp4l.conf files. | 5.10.0-5.11.0 | |
| [4170598](#4170598) switchd
crashes with a Netlink error similar to the following:| 5.10.1-5.11.0 | | | [4142857](#4142857)
netlink.c:409 CRIT nlroute: nl_cache_mngr_data_ready failed: Kernel reported truncated message
[ptp4l.ERR] messages. | 5.10.0-5.11.0 | |
| [4137492](#4137492)
| Accessing NVIDIA Spectrum-4 SPICE from multiple applications to the same path in parallel might cause a kernel crash. | 5.10.1 | 5.11.0|
| [4135919](#4135919)
| You might experience a memory leak in ospfd
when processing next hops due to network changes. | 5.9.1-5.11.0 | |
diff --git a/content/cumulus-linux-510/rn.xml b/content/cumulus-linux-510/rn.xml
index 2fc48ebea8..1d3dbb281a 100644
--- a/content/cumulus-linux-510/rn.xml
+++ b/content/cumulus-linux-510/rn.xml
@@ -7,6 +7,13 @@
Fixed
+4175217
+When there is a large number of discontiguous VTEP to VLAN mappings, {{switchd}} crashes with a Netlink error similar to the following:
+netlink.c:409 CRIT nlroute: nl_cache_mngr_data_ready failed: Kernel reported truncated message
+5.10.1-5.11.0
+
+
+
4173498
After network churn, the {{watchfrr}} process might restart FRR because zebra is unresponsive.
5.9.1-5.11.0
@@ -25,13 +32,6 @@
-4150508
-When there is a large number of discontiguous VTEP to VLAN mappings, {{switchd}} crashes with a Netlink error similar to the following:
-netlink.c:409 CRIT nlroute: nl_cache_mngr_data_ready failed: Kernel reported truncated message
-5.10.1-5.11.0
-
-
-
4142857
The switch drops PTP packets received with extra ethernet padding and you see syslog {{[ptp4l.ERR] messages.
5.10.0-5.11.0
diff --git a/content/cumulus-linux-511/Whats-New/rn.md b/content/cumulus-linux-511/Whats-New/rn.md
index e60c10ae5e..0cb2f94614 100644
--- a/content/cumulus-linux-511/Whats-New/rn.md
+++ b/content/cumulus-linux-511/Whats-New/rn.md
@@ -14,8 +14,8 @@ pdfhidden: True
| Issue ID | Description | Affects | Fixed |
|--- |--- |--- |--- |
+| [4175217](#4175217)
| When there is a large number of discontiguous VTEP to VLAN mappings, switchd
crashes with a Netlink error similar to the following:
netlink.c:409 CRIT nlroute: nl_cache_mngr_data_ready failed: Kernel reported truncated message
| 5.10.1-5.11.0 | |
| [4170628](#4170628)
| If you use a bridge name that isn't br_default
, NVUE generates incorrect ptp4l.conf files. | 5.10.0-5.11.0 | |
-| [4150508](#4150508)
| When there is a large number of discontiguous VTEP to VLAN mappings, switchd
crashes with a Netlink error similar to the following:
netlink.c:409 CRIT nlroute: nl_cache_mngr_data_ready failed: Kernel reported truncated message
| 5.10.1-5.11.0 | |
| [4142857](#4142857)
| The switch drops PTP packets received with extra ethernet padding and you see syslog [ptp4l.ERR] messages. | 5.10.0-5.11.0 | |
| [4135543](#4135543)
| Under certain rare scenarios, the operational status of a switch port interface shows as UP
after you administratively configure it to stay down with the nv set interface link status down
command. To clear this condition, toggle the admin status on the interface once. | 5.11.0 | |
| [4134174](#4134174)
| If you configure a route map by attaching it to a specific protocol, then you detach it from that protocol, if you then attach the same route map to all protocols, then detach it from all protocols, Cumulus Linux deletes routes from the forwarding table.
To work around this issue, either attach the route map to all protocols or attach the route map to each protocol you want to use. For example, to attach the route map to all protocols, run the nv set vrf router rib fib-filter route-map
command. To attach the route map to each protocol you want to use, run the nv set vrf router rib fib-filter protocol route-map
command. | 5.11.0 | |
diff --git a/content/cumulus-linux-511/rn.xml b/content/cumulus-linux-511/rn.xml
index ab930d977f..51f743cf98 100644
--- a/content/cumulus-linux-511/rn.xml
+++ b/content/cumulus-linux-511/rn.xml
@@ -7,19 +7,19 @@
Fixed
-4170628
-If you use a bridge name that isn't {{br_default}}, NVUE generates incorrect ptp4l.conf files.
-5.10.0-5.11.0
-
-
-
-4150508
+4175217
When there is a large number of discontiguous VTEP to VLAN mappings, {{switchd}} crashes with a Netlink error similar to the following:
netlink.c:409 CRIT nlroute: nl_cache_mngr_data_ready failed: Kernel reported truncated message
5.10.1-5.11.0
+4170628
+If you use a bridge name that isn't {{br_default}}, NVUE generates incorrect ptp4l.conf files.
+5.10.0-5.11.0
+
+
+
4142857
The switch drops PTP packets received with extra ethernet padding and you see syslog {{[ptp4l.ERR] messages.
5.10.0-5.11.0