What's New
This document supports the Cumulus Linux 5.13 release, and lists new platforms, features, and enhancements.
- For a list of open and fixed issues in Cumulus Linux 5.13, see the Cumulus Linux 5.13 Release Notes.
- To upgrade to Cumulus Linux 5.13, follow the steps in Upgrading Cumulus Linux.
What’s New in Cumulus Linux 5.13
Platforms
- NVIDIA SN5600D (200G Spectrum-4)
New Features and Enhancements
- NVIDIA SN5400 ITU-T G.8273.2 Class C (Compliance)
- Erase SSD before switch RMA
- OTLP Phase 4
- gNMI support
- Default AR profile update
- New maintenance mode commands
- 802.1 option to keep port in current state when RADIUS server is unreachable
- System health commands
- Recovery mechanism for CPLD thermal shutdown
- Export per transceiver temperature and power
- Filters for RSYSLOG log per facility level
- 802.1x on router ports with dynamic VRF assignments
- Optimized upgrade supports warmboot
- Ability to disconnect or disable remote access to the switch
- Enable RADIUS for multiple VRFs
- Support Docker container
- DHCP IP reservation per port for a single host
- Show SNR for transceivers
- Reflect switch hardware revision
- Enable ssh public key only
- OTLP
- Device level configuration of histogram
- Buffer Occupancy and watermark metrics
- gNMI support
- NVUE
- Enable CRL support
- SSH certificate-based authorization
- .1x support for NAS-IP-Address and NAS-Identifier
- ls command
- Get the hash for a file
- Additional FRR filters
Release Considerations
Review the following considerations before you upgrade to Cumulus Linux 5.13.
Linux Configuration Files Overwritten
If you use Linux commands to configure the switch, read the following information before you upgrade to Cumulus Linux 5.13 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.13 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.yaml
file:cumulus@switch:~$ sudo rm -rf /etc/nvue.d/startup.yaml
-
Add the
PASSWORD_NVUE_SYNC=no
line to the/etc/default/nvued
file: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.13 includes the NVUE object model. After you upgrade to Cumulus Linux 5.13, 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.