This knowledge base has moved to the documentation site. Please visit the knowledge base here for the most up to date content. This site is no longer maintained.

Cumulus Linux Release Versioning and Support Policy


This article outlines the release version numbering structure, and support policies, for:

  • Cumulus Linux 4.0 and later
  • Cumulus Linux and Cumulus RMP 3.0 and later (including 3.7 ESR and later)

Important: Earlier releases of Cumulus Linux and Cumulus RMP are no longer supported.


Version Definitions

The Cumulus Linux installation file name includes the version number, in the form of CumulusLinux_x.y.z; for Cumulus RMP, it is CumulusRMP_x.y.z.

  • x represents the major release version number. An increased major release version means that the release may include:
    • Significant architectural or engineering changes.
    • New hardware platforms, including new ASICs or chipsets.
    • New functionality and features.
    • Bug fixes.
    • Security updates.
  • y represents the minor release version number. An increased minor release version means that the release may include:
    • New hardware platforms, including new ASICs or chipsets.
    • New functionality and features.
    • Bug fixes.
    • Security updates.
  • z represents the maintenance release version number. An increased maintenance release version may include:
    • New hardware platforms for existing ASICs or chipsets.
    • Bug fixes and updates.
    • Security updates.

Release, Support Lifecycle and Support Policy

Cumulus Networks supports both mainline and Extended Support Releases (ESRs). This support mechanism allows us to maintain our desire to innovate, while providing customers with stable releases once the architectural needs are met.

Consistent with this two-pronged approach, the mainline and ESR code branches are separate code bases. As such, issues and fixes in one branch are independent of the other. The ESR branch is prioritized for stability first and foremost, so any fixes there are focused on critical-impact security fixes and urgent bug fixes. This ensures customers deploying an ESR release can experience minimal disruption in their day to day network operations.

The following diagram illustrates the ESR and mainline branches, and the table below it describes the characteristics of each.


  Mainline Extended-Support Release (ESR)
Functionality Latest features No new functionality
Stability Stable and robust Highly stable and robust
Frequency Minor releases quarterly; maintenance releases as needed Maintenance releases as needed
Support Duration (Software updates and support)

ESR branch, before ESR is released: Software updates and Global Support Services (GSS) support

ESR branch, after ESR is released: 12 months GSS support only from date of ESR release

3 years from release date of version
Software Updates New functionality, security updates, bug fixes Security updates and critical bug fixes
Security Updates ASAP ASAP

Product End of Life

Cumulus Linux and Cumulus RMP 3.7.12 has transitioned into the extended support phase (ESR). Customers can choose to continue using Cumulus Linux 3.7 ESR, a mature and stable operating system, or they can upgrade to Cumulus Linux 4.y.z, with the latest and greatest features. Cumulus Networks will continue support and maintain Cumulus Linux and Cumulus RMP 3.7 ESR for 3 years, until 21 February, 2023.

Cumulus Linux Version ESR Start Date End of Life Date
4.y.z TBD TBD
3.7.12 - 3.7.z ESR 21 February, 2020 21 February, 2023
3.0.0 - 3.7.11 N/A 31 December, 2020
2.5.6 - 2.5.12 2 February, 2016 2 February, 2019
2.5.5 and earlier N/A 31 December, 2016

Upgrade Process

For information regarding upgrading from previous Cumulus Linux releases, refer to the Cumulus Linux upgrade documentation.


This support portal has moved

Cumulus Networks is now part of the NVIDIA Networking Business Unit! The NVIDIA Cumulus Global Support Services (GSS) team has merged its operations with the NVIDIA Mellanox support services team.

You can access NVIDIA Cumulus support content from the Mellanox support portal.

You open and update new cases on the Mellanox support portal. Any previous cases that have been closed have been migrated to the Mellanox support portal.

Cases that are still open on the Cumulus portal will continue to be managed on the Cumulus portal. Once these cases close, they will be moved to the Mellanox support portal.

Powered by Zendesk