What's New
This document supports the Cumulus Linux 5.12 release, and lists new platforms, features, and enhancements.
- For a list of open and fixed issues in Cumulus Linux 5.12, see the Cumulus Linux 5.12 Release Notes.
- To upgrade to Cumulus Linux 5.12, follow the steps in Upgrading Cumulus Linux.
What’s New in Cumulus Linux 5.12
Platforms
- SN5610 (800G Spectrum-4)
- SN5400 ITU-T G.82732 Class C compliant
New Features and Enhancements
- 1G (optical) supported with SyncE on the SN5400 switch
- Ability to ugrade from Cumulus Linux 5.11 with Optimized Image Upgrade
- RoCE single shared buffer pool
- Graceful BGP shutdown on a peer group
- Software module reset
- Clear dynamic MAC address entries from the forwarding database
- BGP Prefix Independent Convergence
- ECMP Resource Sharing During Next Hop Group Updates
- RADIUS user command accounting support for multiple servers with first response option
- IPV6 Stateless Address Auto-Configuration
- OTLP new routing metrics
- Support different sample rate for OTLP exporter destinations
- Create a single CLI service check for OTLP exporters
- Support for defining APT sources
- NVUE
To align with a long-term vision of a common interface between Cumulus Linux, Nvidia OS (NVOS), and Host-Based Networking, certain NVUE commands in Cumulus Linux 5.12 have changed. Before you upgrade to 5.12, review the list of changed and removed NVUE commands above and be sure to make any necessary changes to your automation.
Release Considerations
Review the following considerations before you upgrade to Cumulus Linux 5.12.
Linux Configuration Files Overwritten
If you use Linux commands to configure the switch, read the following information before you upgrade to Cumulus Linux 5.12.0 or later.
Cumulus Linux includes a default NVUE startup.yaml file. In addition, NVUE configuration auto save is enabled by default. As a result, Cumulus Linux overwrites any manual changes to Linux configuration files on the switch when the switch reboots after upgrade or you change the cumulus user account password with the Linux passwd command.
These issues occur only if you use Linux commands to configure the switch. If you use NVUE commands to configure the switch, these issues do not occur and no action is needed.
To prevent Cumulus Linux from overwriting manual changes to the Linux configuration files when the switch reboots or when changing the cumulus user account password with the passwd command, follow the steps below before you upgrade to 5.12.0 or later, or after a new binary image installation:
- Disable NVUE auto save:
cumulus@switch:~$ nv set system config auto-save state disabled
cumulus@switch:~$ nv config apply
cumulus@switch:~$ nv config save
-
Delete the
/etc/nvue.d/startup.yamlfile:cumulus@switch:~$ sudo rm -rf /etc/nvue.d/startup.yaml -
Add the
PASSWORD_NVUE_SYNC=noline to the/etc/default/nvuedfile:cumulus@switch:~$ sudo nano /etc/default/nvued PASSWORD_NVUE_SYNC=no
DHCP Lease with the host-name Option
When a Cumulus Linux switch with NVUE enabled receives a DHCP lease containing the host-name option, it ignores the received hostname and does not apply it. For details, see this knowledge base article.
NVUE Commands After Upgrade
Cumulus Linux 5.12 includes the NVUE object model. After you upgrade to Cumulus Linux 5.12, running NVUE configuration commands might override configuration for features that are now configurable with NVUE and removes configuration you added manually to files or with automation tools like Ansible, Chef, or Puppet. To keep your configuration, you can do one of the following:
- Update your automation tools to use NVUE.
- Configure NVUE to ignore certain underlying Linux files when applying configuration changes.
- Use Linux and FRR (vtysh) commands instead of NVUE for all switch configuration.