diff --git a/content/cumulus-linux-516/Whats-New/rn.md b/content/cumulus-linux-516/Whats-New/rn.md index 197e425f23..e91e627652 100644 --- a/content/cumulus-linux-516/Whats-New/rn.md +++ b/content/cumulus-linux-516/Whats-New/rn.md @@ -14,10 +14,9 @@ pdfhidden: True | Issue ID | Description | Affects | Fixed | |--- |--- |--- |--- | +| 5240456 | BGP peer sessions might repeatedly flap and re-establish. During outbound TCP connect, the BGP service might clear the local nexthop information for the peer and fail nexthop setup when the remote endpoint is not yet available, which resets the session. Logs might show nexthop_set failed with remote: (null) and Transport endpoint is not.... | 5.16.1, 5.16.5-5.18.0 | | | 5225576, 5236486 | After an optimized image upgrade from Cumulus Linux 5.13.1 or earlier to a later release, the install step fails with a permission error if the image being installed is already present in the /var/images directory before the upgrade. In this state, the nv show system image files command might not list any images. To work around this issue, fetch the image with the nv action fetch system image command before installing it. Alternatively, correct the directory permissions with sudo chmod 0755 /var/images. | 5.16.6-5.18.0 | | | 5224270 | On switches with TACACS+ servers configured by hostname (FQDN) instead of IP address, the switch might generate an excessive rate of DNS queries for the configured TACACS+ server names, including for local user or UID lookups that never actually need to contact a TACACS+ server. | 5.16.1, 5.16.5-5.18.0 | | -| 5221592 | Adaptive routing ECMP updates during route deletion sometimes result in ECMP database corruption followed by ECMP operation failures. | 5.16.5-5.18.0 | | -| 5221589 | In rare cases, you cannot cancel bulk counter session(MOCS). This issue results in missing GNMI metrics during export. | 5.16.5-5.18.0 | | | 5217147, 5225676 | When you perform a factory reset after an optimized image upgrade, the switch loses record of its model information. | 5.16.6-5.18.0 | | | 5199525 | When EVPN prefixes learned from a BGP neighbor are withdrawn, the gNMI EVPN installed-prefix count does not decrease. | 5.16.1, 5.16.5-5.18.0 | | | 5183442 | If the running version of Cumulus Linux is not the newest, installing packages in cumulus-local-apt-archive (RADIUS or TACACS+ packages) might bring in a newer version from remote locations that does not match the running version of Cumulus Linux. To avoid this problem add an /etc/apt/preferences.d/10_prefer_cumulus_local_apt_archive file with the following content (if not already present) before doing a package update:
Package: *
Pin: release a=cumulus-local-apt-archive
Pin-Priority: 992
| 5.16.5-5.18.0 | | @@ -116,6 +115,7 @@ pdfhidden: True | 4850784 | The unsupported gNOI set-package RPC request does not fail. The supported RPCs are FILE Stat/Remove/Get/Put, Reboot, OS Install, OS Activate. | 5.16.0-5.16.1, 5.16.5-5.16.7 | 5.17.0-5.18.0| | 4850780 | After you remove 802.1X IPv6 profile configuration for dynamic IPv6 multi-tenancy, IPv6 addresses and summary routes remain in FRR.
To recover from this state, manually delete the residual files or reauthenticate through the IPV6 profile with hostapd on the affected interfaces.
To avoid this issue, detach the IPv6 profile from the interfaces and apply the configuration, then remove the global 802.1X configuration. | 5.16.0-5.16.1, 5.16.5-5.16.7 | 5.17.0-5.18.0| | 4850539 | When you update the SOO NHG, FRR sends redundant route updates to the kernel for every route that uses SOO. | 5.16.0-5.16.1, 5.16.5-5.16.7 | 5.17.0-5.18.0| +| 4850225 | The NVUE nv show even vin command and the vtysh show evpn vni command do not display VLAN information for newly added VNIs. | 5.16.0-5.16.1, 5.16.5-5.16.7 | 5.17.0-5.18.0| | 4841491 | When the Management-Privilege-Level or Cisco-Avpair is not found, a user is created with privilege level 0 instead of privilege level 1. | 5.16.0-5.16.1, 5.16.5-5.18.0 | | | 4840271 | When you configure a static SRv6 Static SID, NVUE does not enable SRv6 automatically and requires you to run the nv set router segment-routing srv6 state enabled command manually. | 5.16.0-5.16.1, 5.16.5-5.16.7 | 5.17.0-5.18.0| | 4830228, 4799012 | When you configure RoCE lossless priority groups and you use ISSU to perform a hitless upgrade, switchd restarts and ISSU fails. | 5.15.1, 5.16.0-5.16.1, 5.16.5-5.16.7 | 5.17.0-5.18.0| @@ -244,12 +244,12 @@ pdfhidden: True |--- |--- |--- | | 5221604, 5179671 | After an optimized image upgrade, the startup.yaml file is empty on the new partition. | | | | 5221379, 5221588 | In rare scenarios, a link fault recovery sequence might trigger a switchd watchdog timeout on Spectrum-4 switches. | 5.16.5-5.16.6 | | -| 5221130 | When multiple gNMI bulk counter sessions are requested frequently, gNMI metric export might fail. | 5.16.5-5.16.6 | | +| 5221130, 5221589 | When multiple gNMI bulk counter sessions are requested frequently, gNMI metric export might fail. | 5.16.5-5.16.6 | | | 5217109, 4925514, 4919006 | Core processing services such as cumulus-core.service and cumulus-core.path might enter a failed state due to systemd start rate limiting caused by rapid start and stop cycles. This issue can prevent core files from being included in subsequent automatically generated cl-support collections even after you reactivate automatic cl-support generation after deactivation due to a chain of faults. Newly generated core files might accumulate, potentially leading to /var partition exhaustion. To recover from this condition, run the sudo systemctl reset-failed cumulus-core.service cumulus-core.path command. | 5.16.1, 5.16.5-5.16.6 | | | 5217108, 5182789, 5221590, 5216045, 5215790 | BGP peer sessions might repeatedly flap and re-establish. During outbound TCP connect, the BGP service might clear the local nexthop information for the peer and fail nexthop setup when the remote endpoint is not yet available, which resets the session. Logs might show nexthop_set failed with remote: (null) and Transport endpoint is not.... | 5.16.1, 5.16.5-5.16.6 | | | 5217107, 5183514, 5221591 | The NVUE set command returns a traceback in the output when the per user repo_incarnation file (/home/$USER/.local/share/nvue/repo_incarnation) is non-writable. | 5.16.1, 5.16.5-5.16.6 | | | 5217106, 4922221 | If the core generator service enters a busy loop, the switch cannot auto generate a cl-support file and core files might accumulate, which consume disk space. To work around this issue, restart the core generator service with the sudo systemctl restart cumulus-core.path and sudo systemctl restart cumulus-core.service commands so that it can start processing newly generated cores. | 5.16.0-5.16.1, 5.16.5-5.16.6 | | -| 5217101 | AR ECMP updates during route deletion might result in ECMP database corruption and ECMP operation failures resulting in the following log messages:
switchd[23072]: hal_mlx_sdk_nexthop_wrap.c:789 ERR ECMP: AR cmd CREATE failed: Entry Already Exists, nexthops 18
switchd[23072]: hal_mlx_sdk_nexthop_wrap.c:934 ERR ECMP: failed to CREATE adaptive ecmp in hw
switchd[23072]: hal_mlx_ecmp.c:2426 ERR ECMP: error allocating AR ecmp
switchd[23072]: hal_mlx_sdk_nexthop_wrap.c:707 ERR ECMP: Failed to set adaptive container attributes for ecmp
| 5.16.5-5.16.6 | | +| 5217101, 5221592 | AR ECMP updates during route deletion might result in ECMP database corruption and ECMP operation failures resulting in the following log messages:
switchd[23072]: hal_mlx_sdk_nexthop_wrap.c:789 ERR ECMP: AR cmd CREATE failed: Entry Already Exists, nexthops 18
switchd[23072]: hal_mlx_sdk_nexthop_wrap.c:934 ERR ECMP: failed to CREATE adaptive ecmp in hw
switchd[23072]: hal_mlx_ecmp.c:2426 ERR ECMP: error allocating AR ecmp
switchd[23072]: hal_mlx_sdk_nexthop_wrap.c:707 ERR ECMP: Failed to set adaptive container attributes for ecmp
| 5.16.5-5.16.6 | | | 5217097, 5179671, 5221593, 5221604 | After optimized image upgrade, /run/tmpfs, which holds the upgraded partition, runs out of space. As a result, the switch does not migrate all the certificates to the new partition. This issue prevents NVUE from installing the user defined certificates defaulting to a self signed certificate. | 5.16.5-5.16.6 | | | 5217095, 5172073 | The LLDP Chassis ID might be non-unique when front-panel ports share MAC addresses. | 5.16.5-5.16.6, 5.17.0 | | | 5217094, 5167708 | When an ACL policy is reinstalled while ACL rule counter statistics are being collected, a kernel panic can occur and the switch might reboot unexpectedly. The panic occurs because the ACL counter buffer is released while the hardware counter read for that buffer is still in progress. | 5.16.5-5.16.6 | | @@ -264,18 +264,18 @@ pdfhidden: True |--- |--- |--- |--- | | 5225576, 5236486 | After an optimized image upgrade from Cumulus Linux 5.13.1 or earlier to a later release, the install step fails with a permission error if the image being installed is already present in the /var/images directory before the upgrade. In this state, the nv show system image files command might not list any images. To work around this issue, fetch the image with the nv action fetch system image command before installing it. Alternatively, correct the directory permissions with sudo chmod 0755 /var/images. | 5.16.6-5.18.0 | | | 5224270 | On switches with TACACS+ servers configured by hostname (FQDN) instead of IP address, the switch might generate an excessive rate of DNS queries for the configured TACACS+ server names, including for local user or UID lookups that never actually need to contact a TACACS+ server. | 5.16.1, 5.16.5-5.18.0 | | -| 5221592 | Adaptive routing ECMP updates during route deletion sometimes result in ECMP database corruption followed by ECMP operation failures. | 5.16.5-5.18.0 | | -| 5221589 | In rare cases, you cannot cancel bulk counter session(MOCS). This issue results in missing GNMI metrics during export. | 5.16.5-5.18.0 | | -| 5221130 | When multiple gNMI bulk counter sessions are requested frequently, gNMI metric export might fail. | 5.16.5-5.16.6 | 5.16.7-5.18.0| +| 5221130, 5221589 | When multiple gNMI bulk counter sessions are requested frequently, gNMI metric export might fail. | 5.16.5-5.16.6 | 5.16.7-5.18.0| | 5217147, 5225676 | When you perform a factory reset after an optimized image upgrade, the switch loses record of its model information. | 5.16.6-5.18.0 | | -| 5217101 | AR ECMP updates during route deletion might result in ECMP database corruption and ECMP operation failures resulting in the following log messages:
switchd[23072]: hal_mlx_sdk_nexthop_wrap.c:789 ERR ECMP: AR cmd CREATE failed: Entry Already Exists, nexthops 18
switchd[23072]: hal_mlx_sdk_nexthop_wrap.c:934 ERR ECMP: failed to CREATE adaptive ecmp in hw
switchd[23072]: hal_mlx_ecmp.c:2426 ERR ECMP: error allocating AR ecmp
switchd[23072]: hal_mlx_sdk_nexthop_wrap.c:707 ERR ECMP: Failed to set adaptive container attributes for ecmp
| 5.16.5-5.16.6 | 5.16.7-5.18.0| +| 5217101, 5221592 | AR ECMP updates during route deletion might result in ECMP database corruption and ECMP operation failures resulting in the following log messages:
switchd[23072]: hal_mlx_sdk_nexthop_wrap.c:789 ERR ECMP: AR cmd CREATE failed: Entry Already Exists, nexthops 18
switchd[23072]: hal_mlx_sdk_nexthop_wrap.c:934 ERR ECMP: failed to CREATE adaptive ecmp in hw
switchd[23072]: hal_mlx_ecmp.c:2426 ERR ECMP: error allocating AR ecmp
switchd[23072]: hal_mlx_sdk_nexthop_wrap.c:707 ERR ECMP: Failed to set adaptive container attributes for ecmp
| 5.16.5-5.16.6 | 5.16.7-5.18.0| | 5215201, 5221379, 5221588 | In rare scenarios, a link fault recovery sequence might trigger a switchd watchdog timeout on Spectrum-4 switches. | 5.16.5-5.16.6 | 5.16.7-5.18.0| | 5200160, 5215402, 5221596 | During an optimized image upgrade, the configuration restore step copies the files in /etc/hw-management-thermal/ from the previous release onto the new partition. These files do not contain the settings that Cumulus Linux requires to select the current thermal control algorithm, so the switch runs the previous algorithm instead. That algorithm does not apply the transceiver temperature setpoint or the module temperature cap, so the fan curve follows the transceivers' own factory temperature limits instead of the configured values. | 5.16.6 | 5.16.7-5.18.0| | 5199525 | When EVPN prefixes learned from a BGP neighbor are withdrawn, the gNMI EVPN installed-prefix count does not decrease. | 5.16.1, 5.16.5-5.18.0 | | +| 5197572, 5183241 | In rare cases, you cannot cancel bulk counter session(MOCS), which results in missing GNMI metrics during export. To work around this issue, reboot the switch. | 5.16.5-5.16.6 | 5.16.7-5.18.0| | 5183514, 5217107, 5221591 | The NVUE set command returns a traceback in the output when the per user repo_incarnation file (/home/$USER/.local/share/nvue/repo_incarnation) is non-writable. | 5.16.1, 5.16.5-5.16.6 | 5.16.7-5.18.0| | 5183442 | If the running version of Cumulus Linux is not the newest, installing packages in cumulus-local-apt-archive (RADIUS or TACACS+ packages) might bring in a newer version from remote locations that does not match the running version of Cumulus Linux. To avoid this problem add an /etc/apt/preferences.d/10_prefer_cumulus_local_apt_archive file with the following content (if not already present) before doing a package update:
Package: *
Pin: release a=cumulus-local-apt-archive
Pin-Priority: 992
| 5.16.5-5.18.0 | | -| 5182789, 5217108, 5221590, 5216045, 5215790 | BGP peer sessions might repeatedly flap and re-establish. During outbound TCP connect, the BGP service might clear the local nexthop information for the peer and fail nexthop setup when the remote endpoint is not yet available, which resets the session. Logs might show nexthop_set failed with remote: (null) and Transport endpoint is not.... | 5.16.1, 5.16.5-5.16.6 | 5.16.7-5.18.0| +| 5182789, 5217108, 5221590, 5216045, 5215790, 5240456 | BGP peer sessions might repeatedly flap and re-establish. During outbound TCP connect, the BGP service might clear the local nexthop information for the peer and fail nexthop setup when the remote endpoint is not yet available, which resets the session. Logs might show nexthop_set failed with remote: (null) and Transport endpoint is not.... | 5.16.1, 5.16.5-5.16.6 | 5.16.7-5.18.0| | 5179671, 5217097, 5221593, 5221604 | After optimized image upgrade, /run/tmpfs, which holds the upgraded partition, runs out of space. As a result, the switch does not migrate all the certificates to the new partition. This issue prevents NVUE from installing the user defined certificates defaulting to a self signed certificate. | 5.16.5-5.16.6 | 5.16.7-5.18.0| +| 5179104 | Adaptive routing ECMP updates during route deletion might sometimes result in ECMP database corruption followed by ECMP operation failures. | 5.16.5-5.16.6 | 5.16.7-5.18.0| | 5175518, 5217093, 5221594 | The switchd watchdog crashes due to a netlink buffer overflow triggered by continuous next hop group churn. | 5.16.1, 5.16.5-5.16.6, 5.18.0 | 5.16.7| | 5172157 | The nv config apply command fails to apply configuration changes because NVUE fails to handle stale sessions and does not prompt you to clear them. To work around this issue, run the nv config detach command to clear the stale session, then run the nv config replace command if there is a stale pending revision. | 5.16.5-5.17.0 | 5.18.0| | 5172073, 5217095 | The LLDP Chassis ID might be non-unique when front-panel ports share MAC addresses. | 5.16.5-5.16.6, 5.17.0 | 5.16.7, 5.18.0| @@ -376,6 +376,7 @@ pdfhidden: True | 4850784 | The unsupported gNOI set-package RPC request does not fail. The supported RPCs are FILE Stat/Remove/Get/Put, Reboot, OS Install, OS Activate. | 5.16.0-5.16.1, 5.16.5-5.16.7 | 5.17.0-5.18.0| | 4850780 | After you remove 802.1X IPv6 profile configuration for dynamic IPv6 multi-tenancy, IPv6 addresses and summary routes remain in FRR.
To recover from this state, manually delete the residual files or reauthenticate through the IPV6 profile with hostapd on the affected interfaces.
To avoid this issue, detach the IPv6 profile from the interfaces and apply the configuration, then remove the global 802.1X configuration. | 5.16.0-5.16.1, 5.16.5-5.16.7 | 5.17.0-5.18.0| | 4850539 | When you update the SOO NHG, FRR sends redundant route updates to the kernel for every route that uses SOO. | 5.16.0-5.16.1, 5.16.5-5.16.7 | 5.17.0-5.18.0| +| 4850225 | The NVUE nv show even vin command and the vtysh show evpn vni command do not display VLAN information for newly added VNIs. | 5.16.0-5.16.1, 5.16.5-5.16.7 | 5.17.0-5.18.0| | 4841491 | When the Management-Privilege-Level or Cisco-Avpair is not found, a user is created with privilege level 0 instead of privilege level 1. | 5.16.0-5.16.1, 5.16.5-5.18.0 | | | 4840271 | When you configure a static SRv6 Static SID, NVUE does not enable SRv6 automatically and requires you to run the nv set router segment-routing srv6 state enabled command manually. | 5.16.0-5.16.1, 5.16.5-5.16.7 | 5.17.0-5.18.0| | 4830228, 4799012 | When you configure RoCE lossless priority groups and you use ISSU to perform a hitless upgrade, switchd restarts and ISSU fails. | 5.15.1, 5.16.0-5.16.1, 5.16.5-5.16.7 | 5.17.0-5.18.0| @@ -518,7 +519,7 @@ pdfhidden: True | 5145970 | After a power event, many links on the switch do not directly lose power but show bad EEPROM errors and you need to reset the links manually. | 5.16.1, 5.16.5 | | | 5145963, 5135953 | The Date-Time column in the nv show interface telemetry histogram ... snapshot output shows the same timestamp for every snapshot row when you set monitor temporality to cumulative. Each snapshot now displays the actual capture time. | 5.16.1, 5.16.5 | | | 5145960, 5140761 | A switch reboot might drop the management VRF static route intermittently from the kernel, causing a loss of management-plane reachability. To work around this issue, remove and re-add the route or restart FRR. | 5.16.1, 5.16.5 | | -| 5145959 | During a switch reboot with SRv6 enabled, there is an ordering race that occasionally results in the nginx-authenticator.service only listening on the IPv6 loopback IP address. As result, the gNMI server Envoy instance, which uses the nginx-authenticator.service to validate the username and password in requests from the gNMI client fails to connect and you see the error rpc error: code = Unavailable desc = Authentication service unavailable. | 5.16.1, 5.16.5 | | +| 5145959, 5142608 | A race condition causes gNMI subscriptions to fail on bootup because the gNMI Envoy gRPC proxy is unable to reach the nginx-authenticator service to authenticate users if SRv6 is enabled. This occurs if the nginx-authenticator service is only listening on the IPv6 loopback address, while Envoy is trying to reach it on the IPv4 loopback address. | 5.16.1, 5.16.5 | | | 4933966 | When moving from split 4 to split 2 on a port, FIFO corruption occurs, causing packets to become stuck in the egress queue. | 5.16.0-5.16.1, 5.16.5 | | ## 5.16.5 Release Notes @@ -527,16 +528,16 @@ pdfhidden: True | Issue ID | Description | Affects | Fixed | |--- |--- |--- |--- | | 5224270 | On switches with TACACS+ servers configured by hostname (FQDN) instead of IP address, the switch might generate an excessive rate of DNS queries for the configured TACACS+ server names, including for local user or UID lookups that never actually need to contact a TACACS+ server. | 5.16.1, 5.16.5-5.18.0 | | -| 5221592 | Adaptive routing ECMP updates during route deletion sometimes result in ECMP database corruption followed by ECMP operation failures. | 5.16.5-5.18.0 | | -| 5221589 | In rare cases, you cannot cancel bulk counter session(MOCS). This issue results in missing GNMI metrics during export. | 5.16.5-5.18.0 | | -| 5221130 | When multiple gNMI bulk counter sessions are requested frequently, gNMI metric export might fail. | 5.16.5-5.16.6 | 5.16.7-5.18.0| -| 5217101 | AR ECMP updates during route deletion might result in ECMP database corruption and ECMP operation failures resulting in the following log messages:
switchd[23072]: hal_mlx_sdk_nexthop_wrap.c:789 ERR ECMP: AR cmd CREATE failed: Entry Already Exists, nexthops 18
switchd[23072]: hal_mlx_sdk_nexthop_wrap.c:934 ERR ECMP: failed to CREATE adaptive ecmp in hw
switchd[23072]: hal_mlx_ecmp.c:2426 ERR ECMP: error allocating AR ecmp
switchd[23072]: hal_mlx_sdk_nexthop_wrap.c:707 ERR ECMP: Failed to set adaptive container attributes for ecmp
| 5.16.5-5.16.6 | 5.16.7-5.18.0| +| 5221130, 5221589 | When multiple gNMI bulk counter sessions are requested frequently, gNMI metric export might fail. | 5.16.5-5.16.6 | 5.16.7-5.18.0| +| 5217101, 5221592 | AR ECMP updates during route deletion might result in ECMP database corruption and ECMP operation failures resulting in the following log messages:
switchd[23072]: hal_mlx_sdk_nexthop_wrap.c:789 ERR ECMP: AR cmd CREATE failed: Entry Already Exists, nexthops 18
switchd[23072]: hal_mlx_sdk_nexthop_wrap.c:934 ERR ECMP: failed to CREATE adaptive ecmp in hw
switchd[23072]: hal_mlx_ecmp.c:2426 ERR ECMP: error allocating AR ecmp
switchd[23072]: hal_mlx_sdk_nexthop_wrap.c:707 ERR ECMP: Failed to set adaptive container attributes for ecmp
| 5.16.5-5.16.6 | 5.16.7-5.18.0| | 5215201, 5221379, 5221588 | In rare scenarios, a link fault recovery sequence might trigger a switchd watchdog timeout on Spectrum-4 switches. | 5.16.5-5.16.6 | 5.16.7-5.18.0| | 5199525 | When EVPN prefixes learned from a BGP neighbor are withdrawn, the gNMI EVPN installed-prefix count does not decrease. | 5.16.1, 5.16.5-5.18.0 | | +| 5197572, 5183241 | In rare cases, you cannot cancel bulk counter session(MOCS), which results in missing GNMI metrics during export. To work around this issue, reboot the switch. | 5.16.5-5.16.6 | 5.16.7-5.18.0| | 5183514, 5217107, 5221591 | The NVUE set command returns a traceback in the output when the per user repo_incarnation file (/home/$USER/.local/share/nvue/repo_incarnation) is non-writable. | 5.16.1, 5.16.5-5.16.6 | 5.16.7-5.18.0| | 5183442 | If the running version of Cumulus Linux is not the newest, installing packages in cumulus-local-apt-archive (RADIUS or TACACS+ packages) might bring in a newer version from remote locations that does not match the running version of Cumulus Linux. To avoid this problem add an /etc/apt/preferences.d/10_prefer_cumulus_local_apt_archive file with the following content (if not already present) before doing a package update:
Package: *
Pin: release a=cumulus-local-apt-archive
Pin-Priority: 992
| 5.16.5-5.18.0 | | -| 5182789, 5217108, 5221590, 5216045, 5215790 | BGP peer sessions might repeatedly flap and re-establish. During outbound TCP connect, the BGP service might clear the local nexthop information for the peer and fail nexthop setup when the remote endpoint is not yet available, which resets the session. Logs might show nexthop_set failed with remote: (null) and Transport endpoint is not.... | 5.16.1, 5.16.5-5.16.6 | 5.16.7-5.18.0| +| 5182789, 5217108, 5221590, 5216045, 5215790, 5240456 | BGP peer sessions might repeatedly flap and re-establish. During outbound TCP connect, the BGP service might clear the local nexthop information for the peer and fail nexthop setup when the remote endpoint is not yet available, which resets the session. Logs might show nexthop_set failed with remote: (null) and Transport endpoint is not.... | 5.16.1, 5.16.5-5.16.6 | 5.16.7-5.18.0| | 5179671, 5217097, 5221593, 5221604 | After optimized image upgrade, /run/tmpfs, which holds the upgraded partition, runs out of space. As a result, the switch does not migrate all the certificates to the new partition. This issue prevents NVUE from installing the user defined certificates defaulting to a self signed certificate. | 5.16.5-5.16.6 | 5.16.7-5.18.0| +| 5179104 | Adaptive routing ECMP updates during route deletion might sometimes result in ECMP database corruption followed by ECMP operation failures. | 5.16.5-5.16.6 | 5.16.7-5.18.0| | 5175518, 5217093, 5221594 | The switchd watchdog crashes due to a netlink buffer overflow triggered by continuous next hop group churn. | 5.16.1, 5.16.5-5.16.6, 5.18.0 | 5.16.7| | 5172157 | The nv config apply command fails to apply configuration changes because NVUE fails to handle stale sessions and does not prompt you to clear them. To work around this issue, run the nv config detach command to clear the stale session, then run the nv config replace command if there is a stale pending revision. | 5.16.5-5.17.0 | 5.18.0| | 5172073, 5217095 | The LLDP Chassis ID might be non-unique when front-panel ports share MAC addresses. | 5.16.5-5.16.6, 5.17.0 | 5.16.7, 5.18.0| @@ -550,7 +551,7 @@ pdfhidden: True | 5152149, 5154742 | Zebra might crash when recovering routes after a temporary failure to install forwarding next hops. During interface instability or link flapping, some routes might fail to install. Zebra caches those routes for later retry. If a cached route is removed before the next hop is installed successfully, zebra might later access invalid memory while retrying installation and then crash. | 5.11.3-5.15.1, 5.16.0-5.16.1, 5.16.5-5.17.0 | 5.18.0| | 5152101, 5154662 | When you use NVUE flexible snippets to add custom Debian APT mirrors or sources under /etc/apt/sources.list.d/*, the nv config apply command fails because NVUE incorrectly blocks adding snippeted files under /etc/apt/sources.list.d/*. | 5.16.1, 5.16.5 | 5.16.6-5.18.0| | 5145970 | After a power event, many links on the switch do not directly lose power but show bad EEPROM errors and you need to reset the links manually. | 5.16.1, 5.16.5 | 5.16.6-5.18.0| -| 5145959 | During a switch reboot with SRv6 enabled, there is an ordering race that occasionally results in the nginx-authenticator.service only listening on the IPv6 loopback IP address. As result, the gNMI server Envoy instance, which uses the nginx-authenticator.service to validate the username and password in requests from the gNMI client fails to connect and you see the error rpc error: code = Unavailable desc = Authentication service unavailable. | 5.16.1, 5.16.5 | 5.16.6-5.18.0| +| 5142608, 5145959 | A race condition causes gNMI subscriptions to fail on bootup because the gNMI Envoy gRPC proxy is unable to reach the nginx-authenticator service to authenticate users if SRv6 is enabled. This occurs if the nginx-authenticator service is only listening on the IPv6 loopback address, while Envoy is trying to reach it on the IPv4 loopback address. | 5.16.1, 5.16.5 | 5.16.6-5.18.0| | 5140761, 5145960 | A switch reboot might drop the management VRF static route intermittently from the kernel, causing a loss of management-plane reachability. To work around this issue, remove and re-add the route or restart FRR. | 5.16.1, 5.16.5 | 5.16.6-5.18.0| | 5135953, 5145963 | The Date-Time column in the nv show interface telemetry histogram ... snapshot output shows the same timestamp for every snapshot row when you set monitor temporality to cumulative. Each snapshot now displays the actual capture time. | 5.16.1, 5.16.5 | 5.16.6-5.18.0| | 5135125 | On switches with the Spectrum-4 ASIC, a port configured with a breakout might encounter a firmware (SDK or FW) fatal event when traffic first begins forwarding on the broken-out port. The switch resets the ASIC automatically and restarts switchd to recover. | 5.16.1, 5.16.5-5.17.0 | 5.18.0| @@ -655,6 +656,7 @@ pdfhidden: True | 4850784 | The unsupported gNOI set-package RPC request does not fail. The supported RPCs are FILE Stat/Remove/Get/Put, Reboot, OS Install, OS Activate. | 5.16.0-5.16.1, 5.16.5-5.16.7 | 5.17.0-5.18.0| | 4850780 | After you remove 802.1X IPv6 profile configuration for dynamic IPv6 multi-tenancy, IPv6 addresses and summary routes remain in FRR.
To recover from this state, manually delete the residual files or reauthenticate through the IPV6 profile with hostapd on the affected interfaces.
To avoid this issue, detach the IPv6 profile from the interfaces and apply the configuration, then remove the global 802.1X configuration. | 5.16.0-5.16.1, 5.16.5-5.16.7 | 5.17.0-5.18.0| | 4850539 | When you update the SOO NHG, FRR sends redundant route updates to the kernel for every route that uses SOO. | 5.16.0-5.16.1, 5.16.5-5.16.7 | 5.17.0-5.18.0| +| 4850225 | The NVUE nv show even vin command and the vtysh show evpn vni command do not display VLAN information for newly added VNIs. | 5.16.0-5.16.1, 5.16.5-5.16.7 | 5.17.0-5.18.0| | 4841491 | When the Management-Privilege-Level or Cisco-Avpair is not found, a user is created with privilege level 0 instead of privilege level 1. | 5.16.0-5.16.1, 5.16.5-5.18.0 | | | 4840271 | When you configure a static SRv6 Static SID, NVUE does not enable SRv6 automatically and requires you to run the nv set router segment-routing srv6 state enabled command manually. | 5.16.0-5.16.1, 5.16.5-5.16.7 | 5.17.0-5.18.0| | 4830228, 4799012 | When you configure RoCE lossless priority groups and you use ISSU to perform a hitless upgrade, switchd restarts and ISSU fails. | 5.15.1, 5.16.0-5.16.1, 5.16.5-5.16.7 | 5.17.0-5.18.0| @@ -818,7 +820,7 @@ pdfhidden: True | 5224270 | On switches with TACACS+ servers configured by hostname (FQDN) instead of IP address, the switch might generate an excessive rate of DNS queries for the configured TACACS+ server names, including for local user or UID lookups that never actually need to contact a TACACS+ server. | 5.16.1, 5.16.5-5.18.0 | | | 5199525 | When EVPN prefixes learned from a BGP neighbor are withdrawn, the gNMI EVPN installed-prefix count does not decrease. | 5.16.1, 5.16.5-5.18.0 | | | 5183514, 5217107, 5221591 | The NVUE set command returns a traceback in the output when the per user repo_incarnation file (/home/$USER/.local/share/nvue/repo_incarnation) is non-writable. | 5.16.1, 5.16.5-5.16.6 | 5.16.7-5.18.0| -| 5182789, 5217108, 5221590, 5216045, 5215790 | BGP peer sessions might repeatedly flap and re-establish. During outbound TCP connect, the BGP service might clear the local nexthop information for the peer and fail nexthop setup when the remote endpoint is not yet available, which resets the session. Logs might show nexthop_set failed with remote: (null) and Transport endpoint is not.... | 5.16.1, 5.16.5-5.16.6 | 5.16.7-5.18.0| +| 5182789, 5217108, 5221590, 5216045, 5215790, 5240456 | BGP peer sessions might repeatedly flap and re-establish. During outbound TCP connect, the BGP service might clear the local nexthop information for the peer and fail nexthop setup when the remote endpoint is not yet available, which resets the session. Logs might show nexthop_set failed with remote: (null) and Transport endpoint is not.... | 5.16.1, 5.16.5-5.16.6 | 5.16.7-5.18.0| | 5175518, 5217093, 5221594 | The switchd watchdog crashes due to a netlink buffer overflow triggered by continuous next hop group churn. | 5.16.1, 5.16.5-5.16.6, 5.18.0 | 5.16.7| | 5167882 | In rare cases switchd crashes and the cl-support file triggers twice, which interrupts legacy mlxlink collection and causes multiple per port mlxlink support files to generate. | 5.16.1, 5.16.5-5.18.0 | | | 5159856 | On the Spectrum-4 switch, you might encounter capacitor failures caused by high temperatures; as a result, ports remain down. Thermal algorithm updates are provided to increase cooling fans speed. | 5.16.1, 5.16.5 | 5.16.6-5.18.0| @@ -828,7 +830,7 @@ pdfhidden: True | 5152149, 5154742 | Zebra might crash when recovering routes after a temporary failure to install forwarding next hops. During interface instability or link flapping, some routes might fail to install. Zebra caches those routes for later retry. If a cached route is removed before the next hop is installed successfully, zebra might later access invalid memory while retrying installation and then crash. | 5.11.3-5.15.1, 5.16.0-5.16.1, 5.16.5-5.17.0 | 5.18.0| | 5152101, 5154662 | When you use NVUE flexible snippets to add custom Debian APT mirrors or sources under /etc/apt/sources.list.d/*, the nv config apply command fails because NVUE incorrectly blocks adding snippeted files under /etc/apt/sources.list.d/*. | 5.16.1, 5.16.5 | 5.16.6-5.18.0| | 5145970 | After a power event, many links on the switch do not directly lose power but show bad EEPROM errors and you need to reset the links manually. | 5.16.1, 5.16.5 | 5.16.6-5.18.0| -| 5145959 | During a switch reboot with SRv6 enabled, there is an ordering race that occasionally results in the nginx-authenticator.service only listening on the IPv6 loopback IP address. As result, the gNMI server Envoy instance, which uses the nginx-authenticator.service to validate the username and password in requests from the gNMI client fails to connect and you see the error rpc error: code = Unavailable desc = Authentication service unavailable. | 5.16.1, 5.16.5 | 5.16.6-5.18.0| +| 5142608, 5145959 | A race condition causes gNMI subscriptions to fail on bootup because the gNMI Envoy gRPC proxy is unable to reach the nginx-authenticator service to authenticate users if SRv6 is enabled. This occurs if the nginx-authenticator service is only listening on the IPv6 loopback address, while Envoy is trying to reach it on the IPv4 loopback address. | 5.16.1, 5.16.5 | 5.16.6-5.18.0| | 5140761, 5145960 | A switch reboot might drop the management VRF static route intermittently from the kernel, causing a loss of management-plane reachability. To work around this issue, remove and re-add the route or restart FRR. | 5.16.1, 5.16.5 | 5.16.6-5.18.0| | 5135953, 5145963 | The Date-Time column in the nv show interface telemetry histogram ... snapshot output shows the same timestamp for every snapshot row when you set monitor temporality to cumulative. Each snapshot now displays the actual capture time. | 5.16.1, 5.16.5 | 5.16.6-5.18.0| | 5135125 | On switches with the Spectrum-4 ASIC, a port configured with a breakout might encounter a firmware (SDK or FW) fatal event when traffic first begins forwarding on the broken-out port. The switch resets the ASIC automatically and restarts switchd to recover. | 5.16.1, 5.16.5-5.17.0 | 5.18.0| @@ -949,6 +951,7 @@ pdfhidden: True | 4850784 | The unsupported gNOI set-package RPC request does not fail. The supported RPCs are FILE Stat/Remove/Get/Put, Reboot, OS Install, OS Activate. | 5.16.0-5.16.1, 5.16.5-5.16.7 | 5.17.0-5.18.0| | 4850780 | After you remove 802.1X IPv6 profile configuration for dynamic IPv6 multi-tenancy, IPv6 addresses and summary routes remain in FRR.
To recover from this state, manually delete the residual files or reauthenticate through the IPV6 profile with hostapd on the affected interfaces.
To avoid this issue, detach the IPv6 profile from the interfaces and apply the configuration, then remove the global 802.1X configuration. | 5.16.0-5.16.1, 5.16.5-5.16.7 | 5.17.0-5.18.0| | 4850539 | When you update the SOO NHG, FRR sends redundant route updates to the kernel for every route that uses SOO. | 5.16.0-5.16.1, 5.16.5-5.16.7 | 5.17.0-5.18.0| +| 4850225 | The NVUE nv show even vin command and the vtysh show evpn vni command do not display VLAN information for newly added VNIs. | 5.16.0-5.16.1, 5.16.5-5.16.7 | 5.17.0-5.18.0| | 4841491 | When the Management-Privilege-Level or Cisco-Avpair is not found, a user is created with privilege level 0 instead of privilege level 1. | 5.16.0-5.16.1, 5.16.5-5.18.0 | | | 4840271 | When you configure a static SRv6 Static SID, NVUE does not enable SRv6 automatically and requires you to run the nv set router segment-routing srv6 state enabled command manually. | 5.16.0-5.16.1, 5.16.5-5.16.7 | 5.17.0-5.18.0| | 4830228, 4799012 | When you configure RoCE lossless priority groups and you use ISSU to perform a hitless upgrade, switchd restarts and ISSU fails. | 5.15.1, 5.16.0-5.16.1, 5.16.5-5.16.7 | 5.17.0-5.18.0| @@ -1192,6 +1195,7 @@ pdfhidden: True | 4850784 | The unsupported gNOI set-package RPC request does not fail. The supported RPCs are FILE Stat/Remove/Get/Put, Reboot, OS Install, OS Activate. | 5.16.0-5.16.1, 5.16.5-5.16.7 | 5.17.0-5.18.0| | 4850780 | After you remove 802.1X IPv6 profile configuration for dynamic IPv6 multi-tenancy, IPv6 addresses and summary routes remain in FRR.
To recover from this state, manually delete the residual files or reauthenticate through the IPV6 profile with hostapd on the affected interfaces.
To avoid this issue, detach the IPv6 profile from the interfaces and apply the configuration, then remove the global 802.1X configuration. | 5.16.0-5.16.1, 5.16.5-5.16.7 | 5.17.0-5.18.0| | 4850539 | When you update the SOO NHG, FRR sends redundant route updates to the kernel for every route that uses SOO. | 5.16.0-5.16.1, 5.16.5-5.16.7 | 5.17.0-5.18.0| +| 4850225 | The NVUE nv show even vin command and the vtysh show evpn vni command do not display VLAN information for newly added VNIs. | 5.16.0-5.16.1, 5.16.5-5.16.7 | 5.17.0-5.18.0| | 4841491 | When the Management-Privilege-Level or Cisco-Avpair is not found, a user is created with privilege level 0 instead of privilege level 1. | 5.16.0-5.16.1, 5.16.5-5.18.0 | | | 4840271 | When you configure a static SRv6 Static SID, NVUE does not enable SRv6 automatically and requires you to run the nv set router segment-routing srv6 state enabled command manually. | 5.16.0-5.16.1, 5.16.5-5.16.7 | 5.17.0-5.18.0| | 4830228, 4799012 | When you configure RoCE lossless priority groups and you use ISSU to perform a hitless upgrade, switchd restarts and ISSU fails. | 5.15.1, 5.16.0-5.16.1, 5.16.5-5.16.7 | 5.17.0-5.18.0| diff --git a/content/cumulus-linux-516/rn.xml b/content/cumulus-linux-516/rn.xml index 4fbd07f810..c5c71422a6 100644 --- a/content/cumulus-linux-516/rn.xml +++ b/content/cumulus-linux-516/rn.xml @@ -7,6 +7,12 @@ Fixed +5240456 +BGP peer sessions might repeatedly flap and re-establish. During outbound TCP connect, the BGP service might clear the local nexthop information for the peer and fail nexthop setup when the remote endpoint is not yet available, which resets the session. Logs might show {{nexthop_set failed with remote: (null) and Transport endpoint is not...}}. +5.16.1, 5.16.5-5.18.0 + + + 5225576, 5236486 After an optimized image upgrade from Cumulus Linux 5.13.1 or earlier to a later release, the install step fails with a permission error if the image being installed is already present in the {{/var/images}} directory before the upgrade. In this state, the {{nv show system image files}} command might not list any images. To work around this issue, fetch the image with the {{nv action fetch system image <remote-url>}} command before installing it. Alternatively, correct the directory permissions with {{sudo chmod 0755 /var/images}}. 5.16.6-5.18.0 @@ -19,18 +25,6 @@ -5221592 -Adaptive routing ECMP updates during route deletion sometimes result in ECMP database corruption followed by ECMP operation failures. -5.16.5-5.18.0 - - - -5221589 -In rare cases, you cannot cancel bulk counter session(MOCS). This issue results in missing GNMI metrics during export. -5.16.5-5.18.0 - - - 5217147, 5225676 When you perform a factory reset after an optimized image upgrade, the switch loses record of its model information. 5.16.6-5.18.0 @@ -638,6 +632,12 @@ where only the aggregate should be advertised. 5.17.0-5.18.0 +4850225 +The NVUE {{nv show even vin <vni-id>}} command and the vtysh {{show evpn vni <vni-id>}} command do not display VLAN information for newly added VNIs. +5.16.0-5.16.1, 5.16.5-5.16.7 +5.17.0-5.18.0 + + 4841491 When the Management-Privilege-Level or Cisco-Avpair is not found, a user is created with privilege level 0 instead of privilege level 1. 5.16.0-5.16.1, 5.16.5-5.18.0 @@ -1436,7 +1436,7 @@ cumulus@switch:~$ sudo ethtool -s swp1 speed 100000 autoneg off lanes 2 5.16.5-5.16.6 -5221130 +5221130, 5221589 When multiple gNMI bulk counter sessions are requested frequently, gNMI metric export might fail. 5.16.5-5.16.6 @@ -1461,7 +1461,7 @@ cumulus@switch:~$ sudo ethtool -s swp1 speed 100000 autoneg off lanes 2 5.16.0-5.16.1, 5.16.5-5.16.6 -5217101 +5217101, 5221592 AR ECMP updates during route deletion might result in ECMP database corruption and ECMP operation failures resulting in the following log messages: switchd[23072]: hal_mlx_sdk_nexthop_wrap.c:789 ERR ECMP: AR cmd CREATE failed: Entry Already Exists, nexthops 18 @@ -1522,19 +1522,7 @@ switchd[23072]: hal_mlx_sdk_nexthop_wrap.c:707 ERR ECMP: Failed to set adaptive -5221592 -Adaptive routing ECMP updates during route deletion sometimes result in ECMP database corruption followed by ECMP operation failures. -5.16.5-5.18.0 - - - -5221589 -In rare cases, you cannot cancel bulk counter session(MOCS). This issue results in missing GNMI metrics during export. -5.16.5-5.18.0 - - - -5221130 +5221130, 5221589 When multiple gNMI bulk counter sessions are requested frequently, gNMI metric export might fail. 5.16.5-5.16.6 5.16.7-5.18.0 @@ -1546,7 +1534,7 @@ switchd[23072]: hal_mlx_sdk_nexthop_wrap.c:707 ERR ECMP: Failed to set adaptive -5217101 +5217101, 5221592 AR ECMP updates during route deletion might result in ECMP database corruption and ECMP operation failures resulting in the following log messages: switchd[23072]: hal_mlx_sdk_nexthop_wrap.c:789 ERR ECMP: AR cmd CREATE failed: Entry Already Exists, nexthops 18 @@ -1576,6 +1564,12 @@ switchd[23072]: hal_mlx_sdk_nexthop_wrap.c:707 ERR ECMP: Failed to set adaptive +5197572, 5183241 +In rare cases, you cannot cancel bulk counter session(MOCS), which results in missing GNMI metrics during export. To work around this issue, reboot the switch. +5.16.5-5.16.6 +5.16.7-5.18.0 + + 5183514, 5217107, 5221591 The NVUE set command returns a traceback in the output when the per user repo_incarnation file ({{/home/$USER/.local/share/nvue/repo_incarnation}}) is non-writable. 5.16.1, 5.16.5-5.16.6 @@ -1591,7 +1585,7 @@ Pin-Priority: 992 -5182789, 5217108, 5221590, 5216045, 5215790 +5182789, 5217108, 5221590, 5216045, 5215790, 5240456 BGP peer sessions might repeatedly flap and re-establish. During outbound TCP connect, the BGP service might clear the local nexthop information for the peer and fail nexthop setup when the remote endpoint is not yet available, which resets the session. Logs might show {{nexthop_set failed with remote: (null) and Transport endpoint is not...}}. 5.16.1, 5.16.5-5.16.6 5.16.7-5.18.0 @@ -1603,6 +1597,12 @@ Pin-Priority: 992 5.16.7-5.18.0 +5179104 +Adaptive routing ECMP updates during route deletion might sometimes result in ECMP database corruption followed by ECMP operation failures. +5.16.5-5.16.6 +5.16.7-5.18.0 + + 5175518, 5217093, 5221594 The {{switchd}} watchdog crashes due to a netlink buffer overflow triggered by continuous next hop group churn. 5.16.1, 5.16.5-5.16.6, 5.18.0 @@ -2219,6 +2219,12 @@ where only the aggregate should be advertised. 5.17.0-5.18.0 +4850225 +The NVUE {{nv show even vin <vni-id>}} command and the vtysh {{show evpn vni <vni-id>}} command do not display VLAN information for newly added VNIs. +5.16.0-5.16.1, 5.16.5-5.16.7 +5.17.0-5.18.0 + + 4841491 When the Management-Privilege-Level or Cisco-Avpair is not found, a user is created with privilege level 0 instead of privilege level 1. 5.16.0-5.16.1, 5.16.5-5.18.0 @@ -3089,8 +3095,8 @@ Workaround: Restarting switchd temporarily restores metrics. 5.16.1, 5.16.5 -5145959 -During a switch reboot with SRv6 enabled, there is an ordering race that occasionally results in the {{nginx-authenticator.service}} only listening on the IPv6 loopback IP address. As result, the gNMI server Envoy instance, which uses the {{nginx-authenticator.service}} to validate the username and password in requests from the gNMI client fails to connect and you see the error {{rpc error: code = Unavailable desc = Authentication service unavailable}}. +5145959, 5142608 +A race condition causes gNMI subscriptions to fail on bootup because the gNMI Envoy gRPC proxy is unable to reach the {{nginx-authenticator}} service to authenticate users if SRv6 is enabled. This occurs if the {{nginx-authenticator}} service is only listening on the IPv6 loopback address, while Envoy is trying to reach it on the IPv4 loopback address. 5.16.1, 5.16.5 @@ -3113,25 +3119,13 @@ Workaround: Restarting switchd temporarily restores metrics. -5221592 -Adaptive routing ECMP updates during route deletion sometimes result in ECMP database corruption followed by ECMP operation failures. -5.16.5-5.18.0 - - - -5221589 -In rare cases, you cannot cancel bulk counter session(MOCS). This issue results in missing GNMI metrics during export. -5.16.5-5.18.0 - - - -5221130 +5221130, 5221589 When multiple gNMI bulk counter sessions are requested frequently, gNMI metric export might fail. 5.16.5-5.16.6 5.16.7-5.18.0 -5217101 +5217101, 5221592 AR ECMP updates during route deletion might result in ECMP database corruption and ECMP operation failures resulting in the following log messages: switchd[23072]: hal_mlx_sdk_nexthop_wrap.c:789 ERR ECMP: AR cmd CREATE failed: Entry Already Exists, nexthops 18 @@ -3155,6 +3149,12 @@ switchd[23072]: hal_mlx_sdk_nexthop_wrap.c:707 ERR ECMP: Failed to set adaptive +5197572, 5183241 +In rare cases, you cannot cancel bulk counter session(MOCS), which results in missing GNMI metrics during export. To work around this issue, reboot the switch. +5.16.5-5.16.6 +5.16.7-5.18.0 + + 5183514, 5217107, 5221591 The NVUE set command returns a traceback in the output when the per user repo_incarnation file ({{/home/$USER/.local/share/nvue/repo_incarnation}}) is non-writable. 5.16.1, 5.16.5-5.16.6 @@ -3170,7 +3170,7 @@ Pin-Priority: 992 -5182789, 5217108, 5221590, 5216045, 5215790 +5182789, 5217108, 5221590, 5216045, 5215790, 5240456 BGP peer sessions might repeatedly flap and re-establish. During outbound TCP connect, the BGP service might clear the local nexthop information for the peer and fail nexthop setup when the remote endpoint is not yet available, which resets the session. Logs might show {{nexthop_set failed with remote: (null) and Transport endpoint is not...}}. 5.16.1, 5.16.5-5.16.6 5.16.7-5.18.0 @@ -3182,6 +3182,12 @@ Pin-Priority: 992 5.16.7-5.18.0 +5179104 +Adaptive routing ECMP updates during route deletion might sometimes result in ECMP database corruption followed by ECMP operation failures. +5.16.5-5.16.6 +5.16.7-5.18.0 + + 5175518, 5217093, 5221594 The {{switchd}} watchdog crashes due to a netlink buffer overflow triggered by continuous next hop group churn. 5.16.1, 5.16.5-5.16.6, 5.18.0 @@ -3260,8 +3266,8 @@ Pin-Priority: 992 5.16.6-5.18.0 -5145959 -During a switch reboot with SRv6 enabled, there is an ordering race that occasionally results in the {{nginx-authenticator.service}} only listening on the IPv6 loopback IP address. As result, the gNMI server Envoy instance, which uses the {{nginx-authenticator.service}} to validate the username and password in requests from the gNMI client fails to connect and you see the error {{rpc error: code = Unavailable desc = Authentication service unavailable}}. +5142608, 5145959 +A race condition causes gNMI subscriptions to fail on bootup because the gNMI Envoy gRPC proxy is unable to reach the {{nginx-authenticator}} service to authenticate users if SRv6 is enabled. This occurs if the {{nginx-authenticator}} service is only listening on the IPv6 loopback address, while Envoy is trying to reach it on the IPv4 loopback address. 5.16.1, 5.16.5 5.16.6-5.18.0 @@ -3908,6 +3914,12 @@ where only the aggregate should be advertised. 5.17.0-5.18.0 +4850225 +The NVUE {{nv show even vin <vni-id>}} command and the vtysh {{show evpn vni <vni-id>}} command do not display VLAN information for newly added VNIs. +5.16.0-5.16.1, 5.16.5-5.16.7 +5.17.0-5.18.0 + + 4841491 When the Management-Privilege-Level or Cisco-Avpair is not found, a user is created with privilege level 0 instead of privilege level 1. 5.16.0-5.16.1, 5.16.5-5.18.0 @@ -4869,7 +4881,7 @@ kernel: [899873.236610] sxd_kernel: dev_id=1: Health-Check: New maximum time bet 5.16.7-5.18.0 -5182789, 5217108, 5221590, 5216045, 5215790 +5182789, 5217108, 5221590, 5216045, 5215790, 5240456 BGP peer sessions might repeatedly flap and re-establish. During outbound TCP connect, the BGP service might clear the local nexthop information for the peer and fail nexthop setup when the remote endpoint is not yet available, which resets the session. Logs might show {{nexthop_set failed with remote: (null) and Transport endpoint is not...}}. 5.16.1, 5.16.5-5.16.6 5.16.7-5.18.0 @@ -4929,8 +4941,8 @@ kernel: [899873.236610] sxd_kernel: dev_id=1: Health-Check: New maximum time bet 5.16.6-5.18.0 -5145959 -During a switch reboot with SRv6 enabled, there is an ordering race that occasionally results in the {{nginx-authenticator.service}} only listening on the IPv6 loopback IP address. As result, the gNMI server Envoy instance, which uses the {{nginx-authenticator.service}} to validate the username and password in requests from the gNMI client fails to connect and you see the error {{rpc error: code = Unavailable desc = Authentication service unavailable}}. +5142608, 5145959 +A race condition causes gNMI subscriptions to fail on bootup because the gNMI Envoy gRPC proxy is unable to reach the {{nginx-authenticator}} service to authenticate users if SRv6 is enabled. This occurs if the {{nginx-authenticator}} service is only listening on the IPv6 loopback address, while Envoy is trying to reach it on the IPv4 loopback address. 5.16.1, 5.16.5 5.16.6-5.18.0 @@ -5680,6 +5692,12 @@ where only the aggregate should be advertised. 5.17.0-5.18.0 +4850225 +The NVUE {{nv show even vin <vni-id>}} command and the vtysh {{show evpn vni <vni-id>}} command do not display VLAN information for newly added VNIs. +5.16.0-5.16.1, 5.16.5-5.16.7 +5.17.0-5.18.0 + + 4841491 When the Management-Privilege-Level or Cisco-Avpair is not found, a user is created with privilege level 0 instead of privilege level 1. 5.16.0-5.16.1, 5.16.5-5.18.0 @@ -7146,6 +7164,12 @@ where only the aggregate should be advertised. 5.17.0-5.18.0 +4850225 +The NVUE {{nv show even vin <vni-id>}} command and the vtysh {{show evpn vni <vni-id>}} command do not display VLAN information for newly added VNIs. +5.16.0-5.16.1, 5.16.5-5.16.7 +5.17.0-5.18.0 + + 4841491 When the Management-Privilege-Level or Cisco-Avpair is not found, a user is created with privilege level 0 instead of privilege level 1. 5.16.0-5.16.1, 5.16.5-5.18.0 diff --git a/content/cumulus-linux-517/Whats-New/rn.md b/content/cumulus-linux-517/Whats-New/rn.md index df0d06f46b..dfc42d7869 100644 --- a/content/cumulus-linux-517/Whats-New/rn.md +++ b/content/cumulus-linux-517/Whats-New/rn.md @@ -14,10 +14,9 @@ pdfhidden: True | Issue ID | Description | Affects | Fixed | |--- |--- |--- |--- | +| 5240456 | BGP peer sessions might repeatedly flap and re-establish. During outbound TCP connect, the BGP service might clear the local nexthop information for the peer and fail nexthop setup when the remote endpoint is not yet available, which resets the session. Logs might show nexthop_set failed with remote: (null) and Transport endpoint is not.... | 5.16.1, 5.16.5-5.18.0 | | | 5225576, 5236486 | After an optimized image upgrade from Cumulus Linux 5.13.1 or earlier to a later release, the install step fails with a permission error if the image being installed is already present in the /var/images directory before the upgrade. In this state, the nv show system image files command might not list any images. To work around this issue, fetch the image with the nv action fetch system image command before installing it. Alternatively, correct the directory permissions with sudo chmod 0755 /var/images. | 5.16.6-5.18.0 | | | 5224270 | On switches with TACACS+ servers configured by hostname (FQDN) instead of IP address, the switch might generate an excessive rate of DNS queries for the configured TACACS+ server names, including for local user or UID lookups that never actually need to contact a TACACS+ server. | 5.16.1, 5.16.5-5.18.0 | | -| 5221592 | Adaptive routing ECMP updates during route deletion sometimes result in ECMP database corruption followed by ECMP operation failures. | 5.16.5-5.18.0 | | -| 5221589 | In rare cases, you cannot cancel bulk counter session(MOCS). This issue results in missing GNMI metrics during export. | 5.16.5-5.18.0 | | | 5217147, 5225676 | When you perform a factory reset after an optimized image upgrade, the switch loses record of its model information. | 5.16.6-5.18.0 | | | 5199525 | When EVPN prefixes learned from a BGP neighbor are withdrawn, the gNMI EVPN installed-prefix count does not decrease. | 5.16.1, 5.16.5-5.18.0 | | | 5183442 | If the running version of Cumulus Linux is not the newest, installing packages in cumulus-local-apt-archive (RADIUS or TACACS+ packages) might bring in a newer version from remote locations that does not match the running version of Cumulus Linux. To avoid this problem add an /etc/apt/preferences.d/10_prefer_cumulus_local_apt_archive file with the following content (if not already present) before doing a package update:
Package: *
Pin: release a=cumulus-local-apt-archive
Pin-Priority: 992
| 5.16.5-5.18.0 | | @@ -26,6 +25,7 @@ pdfhidden: True | 5172071 | When you apply a BGP configuration change that renumbers the IP addresses of peers in a peer group and at removes another peer group at the same time, FRR reload fails. As a result, the FRR service does not reload or restart cleanly and the configuration apply rolls back. | 5.16.5-5.17.0 | 5.18.0| | 5167882 | In rare cases switchd crashes and the cl-support file triggers twice, which interrupts legacy mlxlink collection and causes multiple per port mlxlink support files to generate. | 5.16.1, 5.16.5-5.18.0 | | | 5152149, 5154742 | Zebra might crash when recovering routes after a temporary failure to install forwarding next hops. During interface instability or link flapping, some routes might fail to install. Zebra caches those routes for later retry. If a cached route is removed before the next hop is installed successfully, zebra might later access invalid memory while retrying installation and then crash. | 5.11.3-5.15.1, 5.16.0-5.16.1, 5.16.5-5.17.0 | 5.18.0| +| 5146439 | When the BMC power restore policy is set to AlwaysOff, a BMC-only reboot causes the running switch host to be powered off even though no AC power loss occurs. To work around this issue, set the power restore policy to AlwaysOn or LastState. | 5.17.0-5.18.0 | | | 5146168 | OTEL export fails if you configure the gRPC endpoint with an IPv6 address. | 5.17.0 | 5.18.0| | 5146058 | On the Spectrum-6 switch, the l1-show command output does not show eyes and grades for bonus or service port swp65s0 and swp65s1. | 5.17.0 | 5.18.0| | 5135125 | On switches with the Spectrum-4 ASIC, a port configured with a breakout might encounter a firmware (SDK or FW) fatal event when traffic first begins forwarding on the broken-out port. The switch resets the ASIC automatically and restarts switchd to recover. | 5.16.1, 5.16.5-5.17.0 | 5.18.0| @@ -306,6 +306,7 @@ pdfhidden: True | 4850784 | The unsupported gNOI set-package RPC request does not fail. The supported RPCs are FILE Stat/Remove/Get/Put, Reboot, OS Install, OS Activate. | 5.16.0-5.16.1, 5.16.5-5.16.7 | | | 4850780 | After you remove 802.1X IPv6 profile configuration for dynamic IPv6 multi-tenancy, IPv6 addresses and summary routes remain in FRR.
To recover from this state, manually delete the residual files or reauthenticate through the IPV6 profile with hostapd on the affected interfaces.
To avoid this issue, detach the IPv6 profile from the interfaces and apply the configuration, then remove the global 802.1X configuration. | 5.16.0-5.16.1, 5.16.5-5.16.7 | | | 4850539 | When you update the SOO NHG, FRR sends redundant route updates to the kernel for every route that uses SOO. | 5.16.0-5.16.1, 5.16.5-5.16.7 | | +| 4850225 | The NVUE nv show even vin command and the vtysh show evpn vni command do not display VLAN information for newly added VNIs. | 5.16.0-5.16.1, 5.16.5-5.16.7 | | | 4840271 | When you configure a static SRv6 Static SID, NVUE does not enable SRv6 automatically and requires you to run the nv set router segment-routing srv6 state enabled command manually. | 5.16.0-5.16.1, 5.16.5-5.16.7 | | | 4830228, 4799012 | When you configure RoCE lossless priority groups and you use ISSU to perform a hitless upgrade, switchd restarts and ISSU fails. | 5.15.1, 5.16.0-5.16.1, 5.16.5-5.16.7 | | | 4824902, 4944347 | NVUE no longer supports the nv set system docker state and nv show system docker state commands. Docker remains enabled because core services such as UMF, gNMI and WJH run in containers. | 5.16.0-5.16.1, 5.16.5-5.16.7 | | diff --git a/content/cumulus-linux-517/rn.xml b/content/cumulus-linux-517/rn.xml index 2e93c87587..26f4560527 100644 --- a/content/cumulus-linux-517/rn.xml +++ b/content/cumulus-linux-517/rn.xml @@ -7,6 +7,12 @@ Fixed +5240456 +BGP peer sessions might repeatedly flap and re-establish. During outbound TCP connect, the BGP service might clear the local nexthop information for the peer and fail nexthop setup when the remote endpoint is not yet available, which resets the session. Logs might show {{nexthop_set failed with remote: (null) and Transport endpoint is not...}}. +5.16.1, 5.16.5-5.18.0 + + + 5225576, 5236486 After an optimized image upgrade from Cumulus Linux 5.13.1 or earlier to a later release, the install step fails with a permission error if the image being installed is already present in the {{/var/images}} directory before the upgrade. In this state, the {{nv show system image files}} command might not list any images. To work around this issue, fetch the image with the {{nv action fetch system image <remote-url>}} command before installing it. Alternatively, correct the directory permissions with {{sudo chmod 0755 /var/images}}. 5.16.6-5.18.0 @@ -19,18 +25,6 @@ -5221592 -Adaptive routing ECMP updates during route deletion sometimes result in ECMP database corruption followed by ECMP operation failures. -5.16.5-5.18.0 - - - -5221589 -In rare cases, you cannot cancel bulk counter session(MOCS). This issue results in missing GNMI metrics during export. -5.16.5-5.18.0 - - - 5217147, 5225676 When you perform a factory reset after an optimized image upgrade, the switch loses record of its model information. 5.16.6-5.18.0 @@ -82,6 +76,12 @@ Pin-Priority: 992 5.18.0 +5146439 +When the BMC power restore policy is set to {{AlwaysOff}}, a BMC-only reboot causes the running switch host to be powered off even though no AC power loss occurs. To work around this issue, set the power restore policy to {{AlwaysOn}} or {{LastState}}. +5.17.0-5.18.0 + + + 5146168 OTEL export fails if you configure the gRPC endpoint with an IPv6 address. 5.17.0 @@ -1717,6 +1717,11 @@ where only the aggregate should be advertised. 5.16.0-5.16.1, 5.16.5-5.16.7 +4850225 +The NVUE {{nv show even vin <vni-id>}} command and the vtysh {{show evpn vni <vni-id>}} command do not display VLAN information for newly added VNIs. +5.16.0-5.16.1, 5.16.5-5.16.7 + + 4840271 When you configure a static SRv6 Static SID, NVUE does not enable SRv6 automatically and requires you to run the {{nv set router segment-routing srv6 state enabled}} command manually. 5.16.0-5.16.1, 5.16.5-5.16.7 diff --git a/content/cumulus-linux-518/Whats-New/rn.md b/content/cumulus-linux-518/Whats-New/rn.md index 3782fc5f1c..ba8e755eff 100644 --- a/content/cumulus-linux-518/Whats-New/rn.md +++ b/content/cumulus-linux-518/Whats-New/rn.md @@ -14,11 +14,11 @@ pdfhidden: True | Issue ID | Description | Affects | Fixed | |--- |--- |--- |--- | +| 5240456 | BGP peer sessions might repeatedly flap and re-establish. During outbound TCP connect, the BGP service might clear the local nexthop information for the peer and fail nexthop setup when the remote endpoint is not yet available, which resets the session. Logs might show nexthop_set failed with remote: (null) and Transport endpoint is not.... | 5.16.1, 5.16.5-5.18.0 | | +| 5231079 | BGP does not update an already-established BFD session when it later resolves the peer through a different interface. Affected BFD sessions are left bound to the wrong interface and never come up. | 5.18.0 | | | 5225576, 5236486 | After an optimized image upgrade from Cumulus Linux 5.13.1 or earlier to a later release, the install step fails with a permission error if the image being installed is already present in the /var/images directory before the upgrade. In this state, the nv show system image files command might not list any images. To work around this issue, fetch the image with the nv action fetch system image command before installing it. Alternatively, correct the directory permissions with sudo chmod 0755 /var/images. | 5.16.6-5.18.0 | | | 5224270 | On switches with TACACS+ servers configured by hostname (FQDN) instead of IP address, the switch might generate an excessive rate of DNS queries for the configured TACACS+ server names, including for local user or UID lookups that never actually need to contact a TACACS+ server. | 5.16.1, 5.16.5-5.18.0 | | | 5221595 | In certain cases, the switch does not forward traffic on some interfaces in an ECMP group. To work around this issue, flap the affected interface. | 5.18.0 | | -| 5221592 | Adaptive routing ECMP updates during route deletion sometimes result in ECMP database corruption followed by ECMP operation failures. | 5.16.5-5.18.0 | | -| 5221589 | In rare cases, you cannot cancel bulk counter session(MOCS). This issue results in missing GNMI metrics during export. | 5.16.5-5.18.0 | | | 5220910 | NVUE accepts invalid telemetry snapshot file paths; however, the corresponding show commands fail with an error in the NVUE logs. | 5.18.0 | | | 5217147, 5225676 | When you perform a factory reset after an optimized image upgrade, the switch loses record of its model information. | 5.16.6-5.18.0 | | | 5217091 | In some scenarios after configuration bring-up or an interface carrier transition, traffic might not be forwarded on some interfaces in an ECMP group. To work around this issue, flap the affected interface. | 5.18.0 | 5.16.7| @@ -26,10 +26,13 @@ pdfhidden: True | 5199525 | When EVPN prefixes learned from a BGP neighbor are withdrawn, the gNMI EVPN installed-prefix count does not decrease. | 5.16.1, 5.16.5-5.18.0 | | | 5197214 | If the cumulus-platform-common package is updated, login notification might fail on each login and show errors. | 5.18.0 | | | 5190122 | On a Spectrum-6 switch (such as the SN6600-LD), gNMI reports an incorrect shared-buffer cell size of 192 bytes at /qos/shared-buffer/state/cell-size instead of the correct 256 bytes for Spectrum-6. Because this cell size is used to convert internal buffer cell counts into byte values, several shared-buffer telemetry values derived from it (such as per-queue or traffic-class buffer usage and maximum occupancy) report incorrectly over gNMI. The values are inconsistent with the values that NVUE reports and the hardware buffer counters. | 5.18.0 | | +| 5185670 | NVUE incorrectly formats the usb0 operational link attributes as speed 0G and oper-status unknown. | 5.18.0 | | +| 5185505 | On the Spectrum-6 switch, NVUE fails to display per-interface counters for usb0 although the interface and its counters are shown in the global counters view. | 5.18.0 | | | 5184005 | In certain SRv6 configuration rollback scenarios, Zebra might fail to restore all explicit SRv6 SIDs. This can occur when multiple SRv6 locators share the same parent SID block and one of the locators is replayed during rollback. To work around this issue, restart FRR to clear the stale in-memory SRv6 SID allocation state, then reapply the intended configuration if needed. | 5.18.0 | | | 5183654, 5234851 | When you upgrade gNMI with package upgrade, the nv-gnmi.service fails and the switch collects a tech support bundle after the first step of the process (nv action upgrade system packages to latest. The package upgrade process triggers a switch reboot straight afterwards as a second and final step. There is no functional impact after switch reboot completes. | 5.18.0 | | | 5183442 | If the running version of Cumulus Linux is not the newest, installing packages in cumulus-local-apt-archive (RADIUS or TACACS+ packages) might bring in a newer version from remote locations that does not match the running version of Cumulus Linux. To avoid this problem add an /etc/apt/preferences.d/10_prefer_cumulus_local_apt_archive file with the following content (if not already present) before doing a package update:
Package: *
Pin: release a=cumulus-local-apt-archive
Pin-Priority: 992
| 5.16.5-5.18.0 | | | 5180032, 5180016 | Running a transceiver query with the ethtool -m or nv show interface transceiver command might intermittently discard the reply, causing the command to hang for approximately 30 seconds and fail with netlink error: Connection timed out before recovering. | 5.18.0 | | +| 5177678 | In an EVPN deployment using downstream VNIs (D-VNIs), when all EVPN route-target imports are withdrawn from a VRF, switchd fails to free exactly one of the D-VNI entries. | 5.18.0 | | | 5175518, 5217093, 5221594 | The switchd watchdog crashes due to a netlink buffer overflow triggered by continuous next hop group churn. | 5.16.1, 5.16.5-5.16.6, 5.18.0 | 5.16.7| | 5174873 | On an EVPN MH topology with route leaking, if we enable Layer 3 VXLAN Device Mode from existing Single VXLAN Device for All Layer 3 VNIs model, FDB/mac entry is not installed in hardware for some remote VTEP router macs. This affects L3 VxLAN traffic through the VTEPs whose RMACs are not installed on the DUT. | 5.18.0 | | | 5174595, 5233487 | On an EVPN MH topology with route leaking, if we enable Layer 3 VXLAN Device Mode from existing Single VXLAN Device for All Layer 3 VNIs model, cl-route-check errors are observed. Neighbor entry is not resolved for the next hop and hence traffic on the routes shown in cl-route-check errors will be impacted. | 5.18.0 | | @@ -39,6 +42,7 @@ pdfhidden: True | 5159852, 4667526 | When you configure multiple parallel IPv6 numbered eBGP sessions between the same pair of switches, some sessions can remain in an Idle state during simultaneous link or session bringup. Affected sessions repeatedly report Cease/Connection Collision Resolution. To work around this issue, configure update-source separately for every numbered IPv6 BGP neighbor on both switches, using the local IPv6 address assigned to that neighbor’s link.
Do not configure a single shared source on the peer group when each parallel link has a different local address. After applying the configuration, clear the affected BGP sessions to remove any existing incorrectly associated connections. | 5.18.0 | | | 5159368, 5170404 | When the Spectrum 1 switch with scaled configuration collects a cl-support file, the collection might timeout for certain modules and lose system and networking data. | 5.18.0 | | | 5158643 | The nv show evpn l3vxi --output json command returns an empty dictionary ({}). To work around this issue, run the nv show evpn l3vxi --rev=applied --output json command instead. | 5.18.0 | | +| 5146439 | When the BMC power restore policy is set to AlwaysOff, a BMC-only reboot causes the running switch host to be powered off even though no AC power loss occurs. To work around this issue, set the power restore policy to AlwaysOn or LastState. | 5.17.0-5.18.0 | | | 5146376 | If the remote server is unreachable, rsyslog generates internal error messages that flood syslog. | 5.18.0 | | | 5146099 | When operating at 100 percent line rate traffic runs from IXIA, the system experiences packet loss or latency in different traffic RFC tests. To work around this issue, configure the line rate at 99.9 percent and use ports from different IXIA Resource Groups. | 5.18.0 | | | 5107338 | onie-install, onie-select, and cl-image-upgrade now allow only one instance of each to run at the same time, except for read (status check), which you can use at any time. | 5.18.0 | | @@ -182,6 +186,7 @@ pdfhidden: True | 5152101, 5154662 | When you use NVUE flexible snippets to add custom Debian APT mirrors or sources under /etc/apt/sources.list.d/*, the nv config apply command fails because NVUE incorrectly blocks adding snippeted files under /etc/apt/sources.list.d/*. | 5.16.1, 5.16.5 | | | 5146168 | OTEL export fails if you configure the gRPC endpoint with an IPv6 address. | 5.17.0 | | | 5146058 | On the Spectrum-6 switch, the l1-show command output does not show eyes and grades for bonus or service port swp65s0 and swp65s1. | 5.17.0 | | +| 5142608, 5145959 | A race condition causes gNMI subscriptions to fail on bootup because the gNMI Envoy gRPC proxy is unable to reach the nginx-authenticator service to authenticate users if SRv6 is enabled. This occurs if the nginx-authenticator service is only listening on the IPv6 loopback address, while Envoy is trying to reach it on the IPv4 loopback address. | 5.16.1, 5.16.5 | | | 5140761, 5145960 | A switch reboot might drop the management VRF static route intermittently from the kernel, causing a loss of management-plane reachability. To work around this issue, remove and re-add the route or restart FRR. | 5.16.1, 5.16.5 | | | 5135953, 5145963 | The Date-Time column in the nv show interface telemetry histogram ... snapshot output shows the same timestamp for every snapshot row when you set monitor temporality to cumulative. Each snapshot now displays the actual capture time. | 5.16.1, 5.16.5 | | | 5135125 | On switches with the Spectrum-4 ASIC, a port configured with a breakout might encounter a firmware (SDK or FW) fatal event when traffic first begins forwarding on the broken-out port. The switch resets the ASIC automatically and restarts switchd to recover. | 5.16.1, 5.16.5-5.17.0 | | diff --git a/content/cumulus-linux-518/rn.xml b/content/cumulus-linux-518/rn.xml index fb5adadd00..d45c078ee8 100644 --- a/content/cumulus-linux-518/rn.xml +++ b/content/cumulus-linux-518/rn.xml @@ -7,6 +7,18 @@ Fixed +5240456 +BGP peer sessions might repeatedly flap and re-establish. During outbound TCP connect, the BGP service might clear the local nexthop information for the peer and fail nexthop setup when the remote endpoint is not yet available, which resets the session. Logs might show {{nexthop_set failed with remote: (null) and Transport endpoint is not...}}. +5.16.1, 5.16.5-5.18.0 + + + +5231079 +BGP does not update an already-established BFD session when it later resolves the peer through a different interface. Affected BFD sessions are left bound to the wrong interface and never come up. +5.18.0 + + + 5225576, 5236486 After an optimized image upgrade from Cumulus Linux 5.13.1 or earlier to a later release, the install step fails with a permission error if the image being installed is already present in the {{/var/images}} directory before the upgrade. In this state, the {{nv show system image files}} command might not list any images. To work around this issue, fetch the image with the {{nv action fetch system image <remote-url>}} command before installing it. Alternatively, correct the directory permissions with {{sudo chmod 0755 /var/images}}. 5.16.6-5.18.0 @@ -25,18 +37,6 @@ -5221592 -Adaptive routing ECMP updates during route deletion sometimes result in ECMP database corruption followed by ECMP operation failures. -5.16.5-5.18.0 - - - -5221589 -In rare cases, you cannot cancel bulk counter session(MOCS). This issue results in missing GNMI metrics during export. -5.16.5-5.18.0 - - - 5220910 NVUE accepts invalid telemetry snapshot file paths; however, the corresponding show commands fail with an error in the NVUE logs. 5.18.0 @@ -79,6 +79,18 @@ +5185670 +NVUE incorrectly formats the usb0 operational link attributes as speed 0G and {{oper-status}} unknown. +5.18.0 + + + +5185505 +On the Spectrum-6 switch, NVUE fails to display per-interface counters for usb0 although the interface and its counters are shown in the global counters view. +5.18.0 + + + 5184005 In certain SRv6 configuration rollback scenarios, Zebra might fail to restore all explicit SRv6 SIDs. This can occur when multiple SRv6 locators share the same parent SID block and one of the locators is replayed during rollback. To work around this issue, restart FRR to clear the stale in-memory SRv6 SID allocation state, then reapply the intended configuration if needed. 5.18.0 @@ -106,6 +118,12 @@ Pin-Priority: 992 +5177678 +In an EVPN deployment using downstream VNIs (D-VNIs), when all EVPN route-target imports are withdrawn from a VRF, {{switchd}} fails to free exactly one of the D-VNI entries. +5.18.0 + + + 5175518, 5217093, 5221594 The {{switchd}} watchdog crashes due to a netlink buffer overflow triggered by continuous next hop group churn. 5.16.1, 5.16.5-5.16.6, 5.18.0 @@ -160,6 +178,12 @@ Pin-Priority: 992 +5146439 +When the BMC power restore policy is set to {{AlwaysOff}}, a BMC-only reboot causes the running switch host to be powered off even though no AC power loss occurs. To work around this issue, set the power restore policy to {{AlwaysOn}} or {{LastState}}. +5.17.0-5.18.0 + + + 5146376 If the remote server is unreachable, {{rsyslog}} generates internal error messages that flood syslog. 5.18.0 @@ -1038,6 +1062,11 @@ cumulus@switch:~$ sudo ethtool -s swp1 speed 100000 autoneg off lanes 2 5.17.0 +5142608, 5145959 +A race condition causes gNMI subscriptions to fail on bootup because the gNMI Envoy gRPC proxy is unable to reach the {{nginx-authenticator}} service to authenticate users if SRv6 is enabled. This occurs if the {{nginx-authenticator}} service is only listening on the IPv6 loopback address, while Envoy is trying to reach it on the IPv4 loopback address. +5.16.1, 5.16.5 + + 5140761, 5145960 A switch reboot might drop the management VRF static route intermittently from the kernel, causing a loss of management-plane reachability. To work around this issue, remove and re-add the route or restart FRR. 5.16.1, 5.16.5