Juniper Apstra servers in EVE-NG
The Apstra server (AOS), its ZTP server and Apstra Flow all appear in Add Node in your CloudLabBox workspace. Check what each one needs before you plan a lab: they range from 2 GB to 64 GB of memory.
Choose a planCheck it in the free demo
- Vendor
- Juniper
- In Add Node
- 19 images
- Templates
apstra-aosapstra-ztpclbapstraflow- Newest
apstra-aos-5.1.0-117
Installed versions
Every Apstra name in the Add Node image list, exactly as you’ll pick it.
Started in our checksEach links to the tested tip below.
Template apstra-aos
Apstra server (AOS)
apstra-aos-5.1.0-117apstra-aos-5.0.1-1apstra-aos-5.0.0-64apstra-aos-4.2.2-2apstra-aos-4.2.1.1-10apstra-aos-4.2.0-236apstra-aos-4.1.2-269apstra-aos-4.1.1-287apstra-aos-4.0.2-142apstra-aos-4.0.0-314
Template apstra-ztp
Apstra ZTP server
apstra-ztp-5.1.0-7Started in our checksapstra-ztp-5.0.0-10apstra-ztp-4.2.1-21apstra-ztp-4.2.0-34apstra-ztp-4.1.2-8apstra-ztp-4.1.1-8apstra-ztp-4.0.1-11apstra-ztp-2.0.0-61
Template clbapstraflow
Apstra Flow
clbapstraflow-apstra-flow-5.1.0
Add it to a lab
In Add Node, choose the template, then the image. The template fills in these settings; change them before you start the node.
| Image | Template | CPU | RAM | Interfaces | Console |
|---|---|---|---|---|---|
| Apstra server (AOS) | apstra-aos | 8 | 65536 MB | 1 interface | VNC |
| Apstra ZTP server | apstra-ztp | 1 | 2048 MB | 1 interface | VNC |
| Apstra Flow | clbapstraflow | 8 | 32768 MB | 1 interface | VNC |
EVE-NG admits a node by the CPU and RAM set on it, so a running node counts against your plan at these values. The largest of these templates starts nodes at 8 vCPU and 65,536 MB, more than the free demo’s 6 vCPU and 8 GB, so use the demo to find the image and a plan to run it.
A ZTP provisioning network with two switches
Put the Apstra ZTP server and two Arista vEOS switches on their own isolated lab network, then watch the switches look for zero-touch provisioning as they boot. Finishing the onboarding needs your Apstra controller.
The Apstra server (AOS) template starts at 8 vCPU and 65536 MB. That's more memory than the largest CloudLabBox plan includes, so an AOS node can't start at its baseline allocation.
- 1×Apstra ZTP server
apstra-ztp1 vCPU, 2048 MB - 2×vEOS
veos2 vCPU, 6144 MB each
Added with these defaults, the lab uses 5 vCPU and 14 GB of RAM. The smallest plan that fits is Standard, with 12 vCPU and 16 GB: £5 a day, or £1.25 an hour On-Demand.
Licences are yours to bring
Apstra and Apstra Flow need Juniper entitlements, which CloudLabBox doesn't provide. Use your own, and request any activation or update destinations from your Account page.
The images run only inside your CloudLabBox workspace; they aren’t available to download.
Questions about Apstra
What is Juniper Apstra?
Juniper Apstra builds and runs data centre fabrics from intent. The Apstra server (AOS) holds the design and manages the switches, the ZTP server onboards new switches, and Apstra Flow collects and analyses flow data.
Can I run the Apstra server (AOS) on CloudLabBox?
Its template starts at 8 vCPU and 65536 MB, the 64 GB baseline the node tip describes. The largest CloudLabBox plan has 48 GB, so an AOS node won't start at that allocation; the ZTP server and Apstra Flow are smaller.
What does the Apstra ZTP server do?
It answers new switches as they boot and hands them their first configuration, which is how Apstra brings devices under management. It runs a DHCP server, so keep its provisioning network isolated from the rest of your lab.
Juniper: what does the Apstra ZTP server need?
apstra-ztp-5.1.0-7 reached its graphical Ubuntu 22.04.5 login screen. Apstra ZTP uses a separate profile from the controller: 1 vCPU, 2 GB RAM and a VNC console. Connect its provisioning interface to an isolated lab network because it runs a DHCP server. Configure its connection to your Apstra controller and the devices you intend to provision.
Juniper: how much memory should I plan for the Apstra AOS controller?
The Apstra AOS controller profile uses 8 vCPUs and 64 GB RAM as its baseline allocation. Check your account's available resources before starting it. The controller is separate from the much smaller Apstra ZTP server. More managed devices or off-box agents can change its resource needs; an available profile does not mean controller setup is complete.
Apstra Flow: which profile and resources should I use?
Use the dedicated Apstra Flow profile, separate from Apstra AOS and ZTP. The small profile starts at 8 CPUs and 32 GB RAM. The retained 5.1.0 appliance has a 1000 GiB disk; Juniper's documented small production deployment specifies 4 TB. Size your flow collection and retention accordingly, and use your own required entitlement.
Which Apstra images are installed?
19 images (10 Apstra server (AOS), 8 Apstra ZTP server, 1 Apstra Flow), all listed on this page exactly as Add Node shows them. The newest is apstra-aos-5.1.0-117.
How much CPU and RAM does a Apstra node use?
When you add one, the apstra-aos template adds 8 vCPU and 65536 MB of RAM; the apstra-ztp template adds 1 vCPU and 2048 MB of RAM; the clbapstraflow template adds 8 vCPU and 32768 MB of RAM. You can change both in Add Node, and your plan counts what each running node is set to.
More images
CloudLabBox is independent of the vendors named on this page. Their names identify the images in the workspace’s Add Node list.