Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
 

Add Network Resource Pools

A network resource pool defines values for the network resources, such as IPv4 loopback addresses, interface IP addresses, segment identifiers (SIDs), BGP cluster IDs, and so on, that are assigned to devices in your network.

Paragon Automation assigns values to the network resources in a device profile and an interface profile when automatic configuration is enabled for the network resources.

You can create a resource pool by using:

Add Network Resource Pools for Device Onboarding by Using the GUI

To add network resource pools for device onboarding by using Paragon Automation UI:

  1. Navigate to Inventory > Device Onboarding > Network Implementation Plan.
    The Network Implementation Plan page appears.
  2. Click More > Download Sample Network Resources to download sample files that define the resource pools.

    Sample network resource files l3-addr.json and routing.json files are downloaded to your local system.

    The l3-addr.json file defines the resource pools for loopback address and IPv4 addresses. The routing.json file defines the resource pools for autonomous system (AS) number, SIDs, and BGP cluster IDs.

  3. Define your network resource files by editing the values for network resources in the sample files.
  4. Save your network resource files.
  5. Click More > Upload Network Resources to upload the files and create the resource pools.
  6. In the browser dialog box, browse for the network resource files and click Upload to upload the files.
  7. (Optional) Click More > View Network Resources to view the resource pools that you uploaded and that are available in Paragon Automation. See View Network Resources.

After you define the resource pools, you can add device profiles and interface profiles to Paragon Automation. See Add a Device Profile and Add an Interface Profile for details.

Add Network Resource Pools for VPN Services by Using the Service Instances GUI

To add network resources for L3VPN, L2VPN, and L2 circuit services from the Service Instances page in the Paragon Automation GUI:

  1. Click Orchestration > Instances.
    The Service Instances page appears.
  2. Click More > Download Sample Network Resources to download sample files for topology and VPN resource pools.
    The vpn_resources_sample.json and topo_sample.json.txt files are downloaded to your local computer. The vpn_resources_sample.json file defines route distinguisher, route target, and virtual circuit resource pools. The topo_sample.json.txt file defines sample topology resources such as site names, PE device and interface names, PE to CE connection parameters, and so on.
  3. Define your network resource files by editing the values for network resources in the sample files.
  4. Save your network resource files.
  5. Click Orchestration > Instances.
  6. Click More > Upload Sample Network Resources to upload a file.
  7. Browse and select the preconfigured network resource JSON file on your computer.
  8. Click Open to upload the file.
    Paragon Automation generates a service order for the network resource file that you uploaded and executes the order to upload the resource pool to the database.
  9. (Optional) Click More > View Network Resources to view the resource pools that you uploaded and other available resource pools in Paragon Automation.

You can view the order execution status and detailed task logs by navigating to Orchestration > Monitoring > Workflows. See About the Workflows Page.

Add Network Resource Pools by Using REST APIs

To create network resource pools by using REST APIs, you should be familiar working with the tools such as Postman to make API requests to Paragon Automation.

You will need values for the following parameters to create resource pools for the network resources:

  • The URL to the environment where Paragon Automation is running.

  • ID of the organization where you want to add the resource pools.

  • Username for accessing the organization.

  • Password for accessing the organization.

To create a resource pool:

Note:

This procedure details how to use Postman to execute the REST APIs. You can use other tools as well to execute the REST APIs.

  1. Download the Postman application from https://www.postman.com/downloads/.
  2. Install and configure Postman on your system.

    For information about working with Postman application, see Postman documentation.

  3. Create a Postman environment file.
    For information about creating an environment file, see https://learning.postman.com/docs/sending-requests/managing-environments/. See Sample Postman Environment File for a sample of the Postman environment file.
  4. Create a Postman collection file.
    • For device onboarding, see Sample Postman Collection File for Device Onboarding for a sample of the Postman collection file and Table 1 for the REST APIs included in the sample Postman collection file. The sample collection file includes APIs for creating resource pools for IPv4 addresses and BGP cluster IDs.

    • For service orchestration, see Sample Postman Collection Files for Service Orchestration for a sample of the Postman collection file and Table 2 for the REST APIs included in the sample Postman collection file. The sample collection file includes APIs for creating the VPN and topology resource pools for the L3VPN service.

  5. Execute the REST API for getting credentials to access Paragon Automation and get organization ID. You need the organization ID to update the organization_id parameter in the environment file (ORG in the Sample Postman Environment File).

    In the Sample Postman Collection File for Device Onboarding and Sample Postman Collection Files for Service Orchestration, the REST API to be executed for getting the organization ID is 01-who am i and get orgs. A snippet of the sample response for the 01-who am i and get orgs API request is as follows:

    Alternatively, access the Organization Settings page (Settings menu > System Settings on the banner) on the Paragon Automation GUI to get the organization ID from the Organization ID field.
  6. In the environment file, ensure that:
    • Variables User and Password are set to your username and password used for logging in to the Paragon Automation GUI.

    • Verify that the server is set to the Paragon Automation VIP address.web-ui-vip-address

  7. Import the environment file into Postman.
  8. Import the collection file into Postman.
  9. Execute the REST APIs in the collection file to create resource pools.
  10. After the APIs complete execution and return a response indicating that the resource pools are created, view the network resources added to Paragon Automation.
    • For device onboarding, see View Network Resources.

    • For service orchestration:

      1. Click Orchestration > Instances.

        The Service Instances page appears.

      2. Click More > View Network Resources on the Service Instances page to view the resource pools that you uploaded and that are available in Paragon Automation.

Sample Files

This section provides a sample of the environment file, collection file, and the list of REST APIs that you can use to define network resources pools.

Sample Postman Environment File

The following is a sample Postman environment file.

Sample Postman Collection File for Device Onboarding

The following is a sample Postman collection file to define values for IPv4 addresses and BGP cluster IDs.

Table 1 lists the APIs in the sample Postman collection file for onboarding devices.

Table 1: REST APIs in the Sample Postman Collection File for Onboarding Devices.
REST API Description Reference in Collection File

Get Organization Details

Get credentials for accessing an organization and the organization details.

01-Who am I and get orgs

Get Site

Get the site where the device is to be installed and onboarded.

02-pick-site

Add L3 Address; see Sample REST API to Create an IPv4 Address Pool

Create layer 3 (L3) address groups.

03-Create L3 Addr

Post L3 Address

Save the L3 address groups in the database.

04-Exec L3 Addr

Add Routing Resources; see Sample REST API to Create BGP Cluster ID Pool

Create BGP cluster groups.

05-Create Routing Resources

Post Routing Resources

Save the BGP cluster groups in the database.

06-Exec Routing Resources

Get Resources

Get the L3 address groups and BGP clusters that were created for verification.

07-Verify Resources

Sample REST API to Create an IPv4 Address Pool

Note:

The operation field in the JSON file can take up the following values:

  • create—Creates new network resources if none exist. However, if resources already exist, new network resources specified in the JSON file are added to the existing ones.

  • modify—Overrides the existing network resources with the values passed through the JSON file.

  • delete—Removes the network resources specified in the JSON file.

The following is a sample of the REST API to create an IPv4 address resource pool:

Sample REST API to Create BGP Cluster ID Pool

Note:

The operation field in the JSON file can take up the following values:

  • create—Creates new network resources if none exist. However, if resources already exist, new network resources specified in the JSON file are added to the existing ones.

  • modify—Overrides the existing network resources with the values passed through the JSON file.

  • delete—Removes the network resources specified in the JSON file.

The following is a sample of the REST API to the create BGP cluster ID resource pool:

Sample Postman Collection Files for Service Orchestration

The following is a sample of the Postman collection file to provision an L3VPN service in your network.

Table 2 lists the APIs in the sample collection file.

Table 2: REST APIs in the Sample Postman Collection File for L3VPN Provisioning

REST API

Description

Reference in the Collection File

Upload topology resources service order

Create topology network resource pools for provisioning L3VPN service.

Create Topology - Step 1.1

Execute topology resources service order

Upload topology resource pools to the Paragon Automation database.

EXEC Topology Step 1.2

Upload VPN resources service order

Create VPN resource pools for provisioning L3VPN service.

Create vpn resources Step 2.1

Execute VPN resources service order

Upload VPN resource pools to the Paragon Automation database.

EXEC vpn resources Step 2.2

View network resources for placement

View available network resources to assign placement configurations for L3VPN service.

Check Placement Resources 3 Copy

The following is a sample of the Postman collection file to provision an L2VPN service in your network.

Table 3 lists the APIs in the sample collection file.

Table 3: REST APIs in the Sample Postman Collection File for L2VPN Provisioning

REST API

Description

Reference in the Collection File

Upload L2VPN service order

Upload or save the L2VPN service order to the Paragon Automation database.

L2VPN SO Upload

Execute the L2VPN service order

Activate the provisioning workflow for the L2VPN service order.

L2VPN SO Exec

Upload VPN resources service order

Create VPN resource pools for provisioning an L2VPN service.

VPN SO Upload

Execute VPN resources service order

Upload VPN resource pools to the Paragon Automation database. These resources are allocated when provisioning an L2VPN service.

VPN SO Exec

Upload L2 address resources service order

Create L2 address resource pools for provisioning an L2VPN service.

L2 Resource Upload

Execute L2 address resources service order

Upload L2 address resource pools to the Paragon Automation database. These resources are allocated when provisioning an L2VPN service.

L2 Resource Exec

Upload topology resources service order

Create topology resource pools for provisioning an L2VPN service.

Topology SO Upload

Execute topology resources service order

Upload topology resource pools to the Paragon Automation database. These resources are allocated when provisioning an L2VPN service.

Topology SO Exec

The following is a sample of the Postman collection file to provision an L2 circuit service in your network.

Table 4 lists the APIs in the sample collection file.

Table 4: REST APIs in the Sample Postman Collection File for L2 Circuit Provisioning

REST API

Description

Reference in Collection File

Create L2 circuit service instance

Create an L2 circuit service instance.

Create L2VPN Instance

Execute L2 circuit service instance

Activate the provisioning workflow for the L2 circuit service instance.

Exec L2VPN Instance

View L2 circuit provisioning status

View the status of provisioning of the L2 circuit service instance.

Get L2VPN Instance

Delete L2 circuit service instance

Activate the delete workflow for the L2 circuit service instance.

Delete L2VPN Instance

Create VPN resource pool

Create VPN resource pool for provisioning an L2 circuit service.

Create VPN Resources

Execute VPN resource instance

Upload VPN resource pool to the Paragon Automation database. These resources are allocated when provisioning an L2 circuit service.

Exec VPN Resources

Get VPN resources for L2 circuit service provisioning

View resources available in the VPN resource pool for provisioning an L2 circuit service.

Get VPN Resources

Sample REST API to Create Topology Resources for L3VPN and L2VPN Services

Note:

The operation field in the JSON file can take up the following values:

  • create—Creates new network resources if none exist. However, if resources already exist, new network resources specified in the JSON file are added to the existing ones.

  • modify—Overrides the existing network resources with the values passed through the JSON file.

  • delete—Removes the network resources specified in the JSON file.

The following is a sample of the REST API to create topology resource pool for L3VPN and L2VPN services:

Sample REST API to Create VPN Resources for L3VPN, L2VPN, and L2 Circuit Services

Note:

The operation field in the JSON file can take up the following values:

  • create—Creates new network resources if none exist. However, if resources already exist, new network resources specified in the JSON file are added to the existing ones.

  • modify—Overrides the existing network resources with the values passed through the JSON file.

  • delete—Removes the network resources specified in the JSON file.

The following is a sample of the REST API to create a VPN resource pool for L3VPN, L2VPN, and L2 circuit services: