Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
ON THIS PAGE
 

Get Started

Welcome! Juniper Apstra (formerly known as AOS) automates all aspects of the data center network design, build, deploy, and operation phases. It leverages advanced intent-based analytics to continually validate the network, thereby eliminating complexity, vulnerabilities, and outages resulting in a secure and resilient network. To get started with Juniper Apstra, you'll install and configure the software, replace the SSL certificate and default passwords, then start building the elements of your physical network. Depending on the complexity of your design, other tasks may be required in addition to the ones included in this general workflow.

Install Apstra Software

  1. Install and configure the Apstra server.
  2. Replace the SSL certificate and change the default password for the Apstra GUI.

Devices

  1. Device profiles (Devices > Device Profiles) represent the physical devices in your network. Many device profiles are predefined for you. Check the list, and if one that you need is not included, you can create it.
  2. Create and install device agents (Devices > System Agents > Agents) for the devices to be managed in the Apstra environment. If you have many of the same devices using the same configuration you might consider creating agent profiles (Device > Agent Profiles), which can streamline the task of creating many agents.
  3. When agents are created, they appear in the managed devices list in the quarantined state. Acknowledge them (Devices > Managed Devices) to put them in the ready state which allows them to be managed by Apstra software. (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.)

Design

  1. Logical devices (Design > Logical Devices) are abstractions of physical devices. They allow you to specify device capabilities before selecting specific vendor hardware. Check the logical device design (global) catalog for ones that meet your requirements; create them if needed.
  2. Interface maps (Design > Interface Maps) combine device profiles and logical devices. Check the interface map design (global) catalog for ones that meet your requirements; create them if needed.
  3. Rack types (Design > Rack Types) are logical representations of racks. Check the rack type design (global) catalog for ones that meet your requirements; create them if needed.
  4. Templates (Design > Templates) are used to build rack designs (blueprints). Check the template design (global) catalog for one that meets your requirements; create it if needed.

Resources

Create resource pools (ASNs, IPv4 addresses, and IPv6 addresses if needed) for your network. When you're ready to assign resources to your blueprint, you'll specify a resource pool, then the resources will automatically be assigned from that pool.

Blueprints

  1. Create a blueprint from one of the templates in the design section.
  2. Build the network (Blueprints > <your_blueprint_name> > Staged > Physical > Build) by assigning resources, device profiles, and devices (S/Ns).
  3. Review the calculated cabling map (Blueprints > <your_blueprint_name> > Staged > Physical > Links), then 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.
  4. When you're finished with assignments and the blueprint is error-free, commit the blueprint (Blueprints > <your_blueprint_name> > Uncommitted). Committing a blueprint initiates work on the intent and realizes it on the network by pushing configuration changes on assigned devices.
  5. Review the blueprint dashboard (Blueprints > 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.

Next Steps

After your deployment is running, you can proceed to build the virtual environment with virtual networks and routing zones, as needed. You can also refer to the guides in the Reference section to learn about other Apstra capabilities.