What's New
This document supports the Cumulus Linux 5.14 release, and lists new platforms, features, and enhancements.
- For a list of open and fixed issues in Cumulus Linux 5.14, see the Cumulus Linux 5.14 Release Notes.
- To upgrade to Cumulus Linux 5.14, first check the Release Considerations below, then follow the steps in Upgrading Cumulus Linux.
What’s New in Cumulus Linux 5.14
Cumulus Linux 5.14.0 contains several new features and improvements, and provides bug fixes.
New Features and Enhancements
- Erase all data from the switch now generally available
- Link speed setting and auto-negotiation behavior change
- Transceiver thermal control
- Clear physical layer error counters for an interface
- Configure different DHCP servers per interface for DHCP relay
- Domain name configuration
- Adaptive routing default profiles profile-1 and profile-2 removed and replaced with one profile that uses the default profile settings for your switch ASIC type
- JWT Based Authentication for REST API
- gNMI:
- Packet trimming
- RoCE lossy multi TC profile
- SRv6 configuration and Clear SRv6 statistics
- You can now bind TACACS per-command authorization to the default VRF (in previous releases, you must specify the egress interface you use in the default VRF)
- NVUE
Release Considerations
Review the following considerations before you upgrade to Cumulus Linux 5.14.
Upgrade Requirements
You can use optimized image upgrade to upgrade the switch to Cumulus Linux 5.14 from Cumulus Linux 5.12.0 and later.
You can use package upgrade to upgrade the switch to Cumulus Linux 5.14 from the following releases. Package upgrade supports ISSU (warm boot) for these upgrade paths.
- Cumulus Linux 5.13.0
- Cumulus Linux 5.13.1
- Cumulus Linux 5.12.0
- Cumulus Linux 5.12.1
To upgrade to Cumulus Linux 5.14 from a release that does not support package upgrade or optimized image upgrade, you can install an image with ONIE.
Maximum Number of NVUE Revisions
Cumulus Linux 5.13 and later includes a new option to set the maximum number of revisions after which NVUE deletes older revisions automatically. The default setting is 100. After upgrading to Cumulus Linux 5.14 from 5.12, the first time you run nv set or nv unset commands, NVUE deletes older revisions if the number of revisions on the switch is greater than 100.
Linux Configuration Files Overwritten
If you use Linux commands to configure the switch, read the following information before you upgrade to Cumulus Linux 5.14 or later.
NVUE includes a default startup.yaml file. In addition, NVUE enables configuration auto save by default. As a result, NVUE 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.
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.14 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.14 includes the NVUE object model. After you upgrade to Cumulus Linux 5.14, 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.
DHCP Relay Configuration
Cumulus Linux 5.14 introduces server groups. In Cumulus Linux 5.13 and earlier, DHCP relay does not use server groups, but instead, forwards all DHCP client requests to every DHCP server within the same VRF. Cumulus Linux 5.14 no longer provides the nv show service dhcp-relay default server commands.
If you have configured DHCP relay in Cumulus Linux 5.13 or earlier, the upgrade process migrates the configuration to a new default configuration file called isc-dhcp-relay-<server-group-id>-<vrf-id> in the /etc/default directory and selects the uplink and downlink interfaces automatically. After upgrade, make sure to review the new configuration and adjust as needed.
Cumulus VX
NVIDIA no longer releases Cumulus VX as a standalone image. To simulate a Cumulus Linux switch, use NVIDIA AIR.