Prerequisites

There are many ways to set up a topology to work with Apstra ConnectorOps. For a step-by-step guide on how to set up the exact topology used in this guide, see Set Up the Example ConnectorOps Topology.

If you are using your own topology, the following prerequisites are required for Apstra ConnectorOps to identify SRX attached blueprints in Apstra and generate configurations.

Note: Currently, for MNHA topologies, ConnectorOps supports up to two SRXs. The SRXs can be physical SRXs, or vSRXs.

Blueprint prerequisites:

DC fabric with border leaf connected to SRX in Multinode High Availability (MNHA) mode is onboarded to Apstra as Blueprint.
Loopback IP and ASN’s assigned to both the SRX devices
Verify that the SRX Interface names are correct in your Blueprint. For more information, see Verify SRX Interface Names.
Connectivity Template created between SRX and borderleaf with appropriate IPLink, BGP Peer, and Routing Policy details. For more information, see To Create and Assign a Connectivity Template Between the SRXs and Border Leaves.
Create DCI/Over the Top or External Gateway between SRX and border leaf. For more information, see To Create External (Over the Top) Gateways in Apstra, and Designate them as Firewalls for Each SRX.
User-created Routing Zones, assigned to appropriate nodes
Virtual Networks created with associated routing zones, and assigned to hosts. For more information, see To Create VNs and Assign Routing Zones to Nodes.

Apstra ConnectorOps prerequisites:

Both SRX’s onboarded to Apstra Blueprint as Generic Systems with tag “srx”
Import Global Property Set with the following information: SRX details (management IP, device name, and username), VRF details, commitConfig onto Blueprint. This will be used as input by ConnectorOps
The VM/host/server where ConnectorOps is installed has access to both Apstra and the SRXs
Netconf over SSH is enabled on SRXs
SSH public key authentication is configured on the SRXs, and the corresponding private key is mounted as a read-only volume in the ConnectorOps container. For more information, see Configure SSH Public Key Authentication on the SRXs.