What's New
This document supports the Cumulus Linux 5.15 release, and lists new platforms, features, and enhancements.
- For a list of open and fixed issues in Cumulus Linux 5.15, see the Cumulus Linux 5.15 Release Notes.
- To upgrade to Cumulus Linux 5.15, first check the Release Considerations below, then follow the steps in Upgrading Cumulus Linux.
What’s New in Cumulus Linux 5.15
Cumulus Linux 5.15.0 contains new platforms, new features and improvements, and provides bug fixes.
Platforms
- NVIDIA SN5640
New Features and Enhancements
- Packet Trimming counters
- FRR-based BFD support
- Support 256 BGP sessions and 256-way ECMP on Spectrum-4
- Switch latency monitoring
- Support for docker-container
- FIPS mode
- 802.1x Dynamic IPv6 Multi-tenancy
- SSH cipher configuration
- Support for maintenance releases
- Users must re-authenticate when changing authenticators
- Radius user Hardening
- Changes in DSCP to traffic class mapping for MRC QOS template
- Offline package upgrade
- MRC QoS profile change in DSCP to traffic mapping
- Random hash support for adaptive routing eligible traffic
- Telemetry
- You can now run OTLP and gNMI streaming at the same time
- gNOI operational commands
- BGP graceful shutdown metric for OLTP
- ACL metrics for OTLP
- ACL metrics for gNMI streaming
- PHY metrics for gNMI streaming (Number of bit errors corrected and upper boundary of the bin)
- High frequency telemetry Nsight Integration
- Telemetry Parity between OpenTelemetry and gNMI (Phase 1)
- NVUE
- Secure Mount Directory Encryption
- Changed command syntax and output
--expandoption for nv config diff command, nv config show command, and nv config find commandexpand=trueparameter for API calls to View differences between configurations, view a configuration, and search for a specific configuration- Routing | Operational revision needs to be supported for parts of the CL Object model(Phase 2)
- Aging time added to neighbor information
- Login brute forcing via API
- Timestamp format in
nv showcommand output changed from UTC to duration (days, hour:minutes:seconds) - Refactor system aaa and tacacs to common model
- Batch execution support for CLI commands through the API
- Customize autocomplete
Release Considerations
Review the following considerations before you upgrade to Cumulus Linux 5.15.
New, Changed, and Deprecated NVUE Commands
To align with a long-term vision of a common interface between Cumulus Linux, Nvidia OS (NVOS), and Host-Based Networking, many NVUE commands in Cumulus Linux 5.15 have changed. Before you upgrade to 5.15, review the list of New, Changed, and Deprecated NVUE Commands and be sure to make any necessary changes to your automation.
Upgrade Requirements
You can use optimized image upgrade to upgrade the switch to Cumulus Linux 5.15 from Cumulus Linux 5.12 and later.
You can use package upgrade to upgrade the switch to Cumulus Linux 5.15 from the following releases. Package upgrade supports ISSU (warm boot) for these upgrade paths.
- Cumulus Linux 5.14.0
- Cumulus Linux 5.13.1
- Cumulus Linux 5.13.0
To upgrade to Cumulus Linux 5.15 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 includes an option to set the maximum number of revisions after which NVUE deletes older revisions automatically. The default setting is 100. If you upgrade to Cumulus Linux 5.15 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.15.
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.15 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
After you upgrade to Cumulus Linux, 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.
Cumulus VX
NVIDIA no longer releases Cumulus VX as a standalone image. To simulate a Cumulus Linux switch, use NVIDIA AIR.