Getting Started

Up and Running with Juniper Apstra Software

Welcome! To get started, you’ll install and configure the Apstra server. Then for security purposes, we recommend that you replace the SSL certificate and change default passwords. Follow the links below for details.

  1. Ensure that the server you’re going to use for the Apstra server meets requirements.
  2. Install and configure the Apstra server.
  3. Replace the SSL certificate and change the default password for the web interface (UI).

Now you’re ready to design, build, deploy, operate and validate networks.

Design / Build Physical Network

Depending on the complexity of your design, other tasks may be required in addition to the ones included in this general workflow. You can work with devices, design, resources and external systems in any order before proceeding to the blueprint section.


  1. Device profiles represent physical devices. Many device profiles are predefined for you. Check the list, and if one that you need is not included, you can create it.

    Devices > Device Profiles
  2. Create and install agents for the devices in your network. If you have many of the same devices using the same configuration you might consider creating agent profiles, which can streamline the task of creating agents.

    Devices > System Agents > Agents
  3. When agents are created, they appear in the managed devices list in the quarantined state. Acknowledge them to put them in the ready state which allows them to be managed. (If you have a modular device in your network, you may need to change the associated device profile. It’s best to do this before acknowledging.)

    Devices > Managed Devices


  1. Logical devices are abstractions of physical devices. Check existing logical devices for ones that meet your requirements and create them as needed for your design.

    Design > Logical devices
  2. Interface maps are used to create links between physical devices (device profiles) and logical devices. Check existing interface maps, and if they don’t meet your needs, you can create them.

    Design > Interface maps
  3. Rack types are logical representations of racks. If a rack type that you need for your design is not included with the predefined ones, you can create one.

    Design > Rack Types
  4. Templates are used to build rack designs. Check the predefined templates and if one doesn’t meet the needs of your design, you can create one.

    Design > Templates


Create pools for resources (ASNs, IPv4 addresses, IPv6 addresses) that will be used in the network.


External Systems

Create external routers to represent switches that the network uses for traffic exiting the fabric.

External Systems > External Routers


  1. Create a blueprint based on a predefined template or one that you created in the design section.

  2. Build the network by assigning resources, device profiles, device system IDs, and external routers.

    Blueprints > <your_blueprint_name> > Staged > Physical > Build
  3. Review the calculated cabling map and cable up the physical devices according to the map. If you have a set of pre-cabled switches, ensure that you have configured interface maps according to the actual cabling so that calculated cabling matches actual cabling. You can also use AOS CLI to discover existing cabling and override the blueprint with that cabling.

    Blueprints > <your_blueprint_name> > Staged > Physical > Links
  4. When all assignments have been made and the blueprint is error-free, commit the blueprint. Committing a blueprint initiates work on the intent and realizes it on the network by pushing configuration changes on assigned devices.

    Blueprints > <your_blueprint_name> > Uncommitted
  5. Review the blueprint dashboard for anomalies. If you have cabling anomalies, the likely reason is a mismatch in calculated cabling and actual cabling. Either re-cable the switches, recreate the blueprint with appropriate interface maps or use AOS CLI to override the cabling in the blueprint with discovered cabling.

    Blueprints > Dashboard

Next Steps

After your deployment is running, you can proceed to build the virtual environment with virtual networks and security zones, as needed. You can also refer to the guides to learn about intent-based analytics and other capabilities.