Qualified Devices and NOS Versions

Recommended qualified NOS versions and device (series) are listed below. Other versions in the same code train that contain only bug fixes are also expected to work. This is usually indicated with version numbers that differ only by the last digit; however, this is not strictly guaranteed by the NOS vendors.

If you plan to use a device or NOS version close to the qualified ones but not listed, it is highly recommended that you review the NOS release notes to ensure no backward incompatible or breaking changes are listed. We strongly advise testing the new version thoroughly in a staging environment before deploying it to production.

To request consideration for qualification for a release train not listed, contact your Juniper Apstra Sales representative.

Only Bug Fix NOS versions Examples:

• Junos and Junos Evolved

  • 20.2R2-S1 > 20.2R2-S3.5 (reason: only service release number change)

  • 20.2R2 > 20.2R3 (reason: R2 > R3 expected to contain only bugfixes)

• Arista EOS

  • 4.25.4M > 4.25.5M (reason: same code train, last digit change and M indicates Maintenance release)

• Cisco NXOS

  • 10.2(9)M > 10.2(10)M (reason: same code train, last digit change and M indicates Maintenance release)

Non-Bug Fix Examples:

• Junos and Junos Evolved

  • 20.2R1 > 20.2R2 (reason: R1 > R2 can have new features + bugfixes)

  • 20.2R2 > 20.4R2 (reason: different release trains)

• Arista EOS

  • 4.25.4M > 4.26.5M (reason: different release trains)

• Cisco NXOS

  • 10.2(1)F > 10.2(3)F (reason: multiple last digit change, F indicates Feature release)