Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
 

Required Server Resources

Apstra server VM resource requirements are based on the size of the network (blueprint), the scaling of offbox agents and the use of Intent Based Analytics (IBA). If one VM is insufficient for your needs, you can increase capacity by adding worker nodes with Apstra VM Clusters. Both the controller node and each worker node support a maximum of 25 offbox agents.

CAUTION:

Although Apstra server VMs might run with fewer resources than recommended, depending on the size of the network, the CPU and RAM allocations may be insufficient. The system could encounter errors or a critical "segmentation fault" (core dump). If this happens, delete the VM and redeploy it with additional resources.
Table 1: Recommended VM Resources
Resource Recommendation
Memory 64 GB RAM + 500 MB per installed offbox agent*
CPU 8 vCPU
Disk 160 GB**
Network 1 network adapter, initially configured with DHCP

* Container memory usage is dependent on the number of IBA collectors enabled. At a minimum, you'll need to change the application weight for Juniper offbox agents after installation is complete and you're in the Apstra environment.

** Apstra images ship with an 80 GB disk by default. As of Apstra version 4.1.2, ESXi images ship with a second "empty" disk. On first boot, Apstra automatically runs aos_extend_disk, and if space is available, it extends /(root), /var, /var/log, and /var/log/aos/db to the new disk. (Shipping with an 80 GB disk instead of 160 GB keeps the image size reasonable.)

If you deploy Linux KVM QCOW2 or Microsoft Hyper-V VHDX, the second disk isn’t included so the default is 80 GB. You can manually add an additional disk. Run aos_extend_disk yourself to extend /(root), /var, /var/log, and /var/log/aos/db to the new disk. For more information, see Juniper Support Knowledge Base article KB37699.