[EOS Lifecycle Policy Updated as of Jan 1, 2020]

Arista Networks' EOS™ Software Release Policy and Life Cycle guidelines help customers and partners facilitate EOS migration and plan multi-year infrastructure deployment. Arista will support each major EOS software release for up to 36 months from the date of initial posting for a particular train.

To assist customers in selecting the right EOS software release for their environments, Arista follows a standard naming convention for EOS releases. The naming convention identifies if a particular release is integrating new feature functionality, or has reached software maintenance mode.

Each EOS software release is identified with either the letter "F" indicating that the release contains new Functionality or "M", denoting that the release is in the Maintenance phase. An M release only receives incremental fixes and no new functionality is added.

New Feature Phase

  • EOS software releases will be identified with the letter "F" indicating that the release contains new feature/functionality.
  • TAC support available

Maintenance Phase

  • EOS software release will be identified with the letter "M" for maintenance phase An M release only receives incremental fixes and no new functionality is added
  • TAC support available

Support Only Phase

  • Ongoing TAC support
  • Software upgrade required for bug fixes

 

The following diagram depicts the release phases using an example as well as the Arista TAC support mapping across this timeline.

The following table depicts the Arista EOS release support matrix, including the timelines for each major Arista EOS software train (based on the 36 month lifecycle policy) and includes current state of TAC support for each train.

If you need assistance with EOS software migration options, please contact your Arista sales representative or contact us at sales@arista.com