Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?




In this use case, you used the Apstra Fabric Conductor to design, build, and deploy a fabric of QFX Series switches, including the overlay networks that run on top of the fabric.

The procedures you used to create the network in this use case apply equally well to cloud-scale data centers. The notion of configuring the fabric as a whole while leaving individual device configuration details to AOS allows these procedures to scale gracefully. Being able to create multiple blueprints from a single design template enables you to take a cookie cutter approach when deploying multiple sites.

Since your design is based on physical building blocks such as ports, devices, and racks, the AOS design process is highly intuitive. By creating these building blocks and specifying what ports are used, you’ve given AOS all the information necessary to come up with a reference design for your fabric.

The reference design that AOS builds contains not only configuration information, but also the roles and responsibilities of various components, enforcement mechanisms, and the expectations that need to be met. This allows AOS to use the reference design not only to configure the fabric but to validate the fabric once the configuration is deployed, and on an ongoing basis thereafter.

We’ve shown how this works by creating cabling and configuration issues for AOS to detect as well as performing a device software upgrade. This ability to reliably handle controlled changes and unexpected network events is what separates AOS from other fabric management tools.


To reinforce your learning, try the Apstra Fabric Conductor lab at Juniper Networks Virtual Labs. You can find the Apstra Fabric Conductor lab by scrolling down to the Switching category.