Qualified Devices and NOS Versions
Device Roles and Definitions
Device Role | Definition |
---|---|
Access |
|
IP Forwarder Only |
|
EVPN Leaf |
|
Apstra Release 4.2.2 & 4.2.1
- Juniper - Apstra 4.2.2 & 4.2.1
- SONiC - Apstra 4.2.2 & 4.2.1
- Cisco NX-OS - Apstra 4.2.2 & 4.2.1
- Arista - Apstra 4.2.2 & 4.2.1
Juniper - Apstra 4.2.2 & 4.2.1
- Juniper Junos OS - Apstra 4.2.2 & 4.2.1
- Juniper Junos OS Evolved - Apstra 4.2.2 & 4.2.1
- Line Cards for Modular Chassis - Apstra 4.2.2 & 4.2.1
Juniper Junos OS - Apstra 4.2.2 & 4.2.1
Device Role |
Qualified NOS Version |
Supported Devices (Series) |
---|---|---|
Access |
|
Refer to IP Forwarder or EVPN Leaf section below for devices. (Any Junos leaf device can be an Access.) |
IP Forwarder Only |
|
|
IP Forwarder or EVPN Leaf |
|
Note:
The EX4400-series switches are primarily designed for campus environments and have scalability limitations when used as leaf devices in data center deployments. This can negatively impact the entire fabric. However, they can be safely utilized in smaller data center deployments. Refer to our Juniper Validated Design (JVD) notes and tables for additional details and guidance. |
Interconnect Gateway Leaf |
22.4R3 |
|
Juniper Junos OS Evolved - Apstra 4.2.2 & 4.2.1
Device Role |
Qualified NOS Versions |
Supported Devices (Series) |
---|---|---|
IP Forwarder Only
|
|
|
IP Forwarder or EVPN Leaf |
|
|
IP Forwarder Only - Tech Preview |
Tech Preview -contact Juniper sales team |
|
IP Forwarder or EVPN Leaf - Tech Preview |
Tech Preview - contact Juniper sales team |
|
Interconnect Gateway Leaf |
22.4R3-EVO |
|
Line Cards for Modular Chassis - Apstra 4.2.2 & 4.2.1
Device Model |
Line Cards |
---|---|
PTX10004/8/16 |
|
QFX10002/8/16 |
|
QFX5700 |
|
SONiC - Apstra 4.2.2 & 4.2.1
Device Role |
Qualified NOS Versions |
Supported Device Series |
---|---|---|
Check vendor documentation for feature capabilities of the desired device |
|
If you need a device not listed below, reach out to an Apstra Specialist or PLM.
|
Cisco NX-OS - Apstra 4.2.2 & 4.2.1
Device Role |
Qualified NOS Versions |
Supported Device Series |
---|---|---|
Check vendor documentation for feature capabilities of the desired device |
|
If you need a device not listed below, reach out to an Apstra Specialist or PLM.
|
Arista - Apstra 4.2.2 & 4.2.1
Device Role |
Qualified NOS Versions |
Supported Device Series |
---|---|---|
Check vendor documentation for feature capabilities of the desired device |
|
If you need a device not listed below, reach out to an Apstra Specialist or PLM.
|
Apstra Release 4.2.0
Device Operating System | Device Role | Qualified NOS Versions | Supported Devices (Series) |
---|---|---|---|
Juniper Junos OS | Access |
|
Refer to IP Forwarder or EVPN Leaf section below for devices. (Any Junos leaf device can be an Access.) |
IP Forwarder Only |
|
|
|
IP Forwarder or EVPN Leaf |
|
Note:
The EX4400-series switches are primarily designed for campus environments and have scalability limitations when used as leaf devices in data center deployments. This can negatively impact the entire fabric. However, they can be safely utilized in smaller data center deployments. Refer to our Juniper Validated Design (JVD) notes and tables for additional details and guidance. |
|
Juniper Junos OS Evolved | IP Forwarder Only |
|
|
IP Forwarder or EVPN Leaf |
IP Forwarder
IP Forwarder or EVPN Leaf
|
|
|
Enterprise SONiC | Check vendor documentation for feature capabilities of the desired device |
|
If you need a device not listed below, reach out to an Apstra
Specialist or PLM.
|
Cisco NX-OS | Check vendor documentation for feature capabilities of the desired device |
|
If you need a device not listed below, reach out to an Apstra
Specialist or PLM.
|
Arista EOS | Check vendor documentation for feature capabilities of the desired device |
|
If you need a device not listed below, reach out to an Apstra
Specialist or PLM.
|
NOS Versions that are not Qualified
NOS versions that are not in the table above are also expected to work if they are in the same code train and contain only bug fixes. 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, we highly recommend 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.
Examples of Only Bug Fix NOS versions:
-
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)
-
Examples of Non-Bug Fix Versions:
-
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)
-