Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
 

Resource Instance Overview

To provision a service in the network, you (superuser or network administrator) must configure the network resource pools for the service. A resource instance defines the elements of a network resource pool. For example, a VPN resource instance defines resources such as route distinguishers, route targets, and so on for provisioning L3VPN, EVPN, and L2 circuit services. You can create the following types of resource instances based on the guidelines and templates defined by the corresponding resource designs that Paragon Automation provides:

  • Routing resource instance based on the routing resource design—Defines the routing resource pool (AS, route reflector, and so on) required to provision the infrastructure service.

  • Layer 3 resource instance based on the Layer 3 (L3-Addr) resource design—Defines the Layer 3 resource pool (IPv4 and loopback addresses) to provision infrastructure services.

  • Layer 2 resource instance based on the Layer 2 (L2-Addr) resource design—Defines the Layer 2 resource pool (EVPN ESIs, LACP administrative keys and system IDs) to provision EVPN services.

  • Topology resource instance based on the topology (Topo) resource design—Defines the topology resource pool (PE details, PE to CE connection details, VLANs, and so on) to provision L3VPN and EVPN services.

  • VPN resource instance based on the VPN Resources resource design—Defines the VPN resource pool (route distinguishers, route targets, and so on) to provision L3VPN, EVPN, and L2 circuit services.

You can also modify and delete a resource instance. When you create, modify, or delete a resource instance, and then save and commit it, you generate a corresponding service order (create, modify, or delete) that activates the automated workflows associated with the service order. You can monitor the execution status of a service order. After a create or modify workflow is successfully executed, the resource pool is uploaded to the Paragon Automation database. When you provision a service, you use the uploaded network resource configurations to assign and allocate network resources for the service. The delete workflow deletes or removes the resource pools from the database.

The Resource Instances page (Orchestration > Service > Resource Instances) lists all the resource instances created in an organization.

Related Documentation