Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
 

Create and Import a Global Property Set

Follow these steps to create and import a Global Property Set. Apstra ConnectorOps uses this Property Set as input to render SRX configurations.

You must define a Property Set with input information for ConnectorOps to automate configuration generation to the SRXs. ConnectorOps uses this Property Set as the data source for configuration rendering and to establish connectivity between devices.

You must configure a Property Set with the "connector_ops_config" prefix. Create the Property Set at the global scope, then import it into the revelant Blueprint.

The Property Set contains an "SRXSetGroups" field. This field contains one or more SRX configuration groups. Each group represents a logical grouping of SRX devices with similar configuration settings. Each group must include the following:

  • "SRX_details": A list of the SRX devices in the group. Each entry must define:

    • "managementIP": The management IP address of the SRX.
    • "name": The device identifier. This must match the system name defined in the Blueprint.
    • "username": The username ConnectorOps uses to connect to the SRX.

  • "commitConfig": A Boolean flag (true, false). If set to “true”, ConnectorOps pushes the configuration and commits it on the SRX. If set to “false”, ConnectorOps saves the config file on the SRX but doesn’t commit, so that you can review the file before committing. The config file is saved with the following file name: co-<blueprint_name>-<device_name>_config_<timestamp>.txt.

    The config files are located in /var/tmp.


    Shell command output showing `ls -lrt` in the /var/tmp directory on a Unix-like system. Displays file permissions, owners, groups, sizes, timestamps, and names of directories, files, named pipes, and temporary configuration files.

  • "sharedLoopbackIP": Shared loopback IP address between peer SRX.

  • "vrf": VRF assignment details for route leaking and policy configuration. Contains one or more VRF group definitions. Each VRF group must contain a "name" and an optional "advertise_routes" list of routes to advertise.

Note:

For successful authentication, the username in the Property Set must match the username associated with the SSH public key on the SRX. SRX passwords are no longer included in the Property Set.

The following is an example Property Set:

Note: You can add multiple SRX peer groups under "SRXSetGroups".

For managementIP, specify the SRX management address as either an IP or hostname. If SSH access uses a non-default port, specify it as host:port (for example, 192.0.2.1:2222). ConnectorOps uses port 22 by default if no port is provided.

  1. Navigate to Design > Property Sets > Create Property Set.
    The Create Property Set window displays.
  2. Enter a Name and define a Property Set configuration in Values.
    Make sure to follow the proper naming convention.
  3. From within your Blueprint, navigate to Staged > Catalog > Property Sets > Import Property Set.
    The Import Property Set from Global Catalog window displays.
  4. Select the Property Set you created from the dropdown, and click Import Property Set.

    User interface for selecting and importing a property set from a dropdown list, with an Import Property Set button.
    This triggers an event, and ConnectorOps uses the Property Set as input to generate the configuration.
  5. Verify that ConnectorOps has generated a Global Configlet by navigating to Design > Configlets.

    Configlets beginning with the "co" prefix are automatically generated by ConnectorOps during its operational workflow. These configlets follow the naming convention co-<BlueprintName>-<SRX-Name>, and show the device-specific SRX configuration rendered by ConnectorOps.

  6. (Optional) Log into your SRX and verify that the custom configs showing Group names that match the generated configs are present.
    The group names should match the name of the Global Configlet.

    Configuration output from a Juniper device in set format showing high-availability settings, including redundancy groups, peer IPs, activeness probes, and routing priorities.
  7. If commitConfig="true", ConnectorOps pushes the configurations to the SRX and you must manually reboot the SRX for the HA configs to take effect.