EOS Life Cycle Policy

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 30 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 will be identified with either the letter "F" indicating that it contains new Functionality release or "M", denoting that the release is in the Maintenance phase. An M release only receives incremental fixes and no new functionality is added.

Arista EOS software release numbering will follow the following example:

4.X.0F : First release
4.X.1F : Next Feature Release
4.X.2F : Addition of new features as required
4.X.YM : First release containing bug fixes only followed by ongoing active maintenance
4.X.ZM : Last maintenance release

 

The following diagram depicts the release phases and numbering 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 30 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

*Naming convention was started as of Arista EOS release 4.13