Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
 

Resource Instance Overview

Before provisioning a network service, a superuser or network administrator must configure and upload the required network resource pools. Routing Director provides the following resource designs to support this process:

  • Routing Resource Designs: Configure routing resource pools such as autonomous systems (AS), route reflectors, and more, for provisioning infrastructure services.

  • Routing and L3 Resource Designs: Configure layer 3 resource pools such as IPv4 addresses, IPv6 addresses, loopback addresses, and more, for provisioning infrastructure services.

  • L2 Resource Design: Configure Layer 2 resource pools such as EVPN Ethernet Segment Identifiers (ESIs), LACP administrative keys, and system identifiers for provisioning EVPN services.

  • Topology Resource Design: Configure topology resource pools for PE device details, PE-to-CE connections, VLANs, and related site-specific information required for provisioning L3VPN, EVPN, and EVPN-VPWS services.

    Because resources can also be managed within network implementation plans, the system automatically creates a blank topology instance on the Resource Instances page (Orchestration > Service > Resource Instances). This instance is read-only and owned by the network operator, serving as a placeholder for topology-related resource configurations.

  • VPN Resource Design: Configure VPN resource pools for route distinguishers, route targets, and virtual circuit IDs to provision L3VPN, EVPN, and Layer 2 circuit services.

These service designs are listed on the Service Catalog page (Orchestration > Service > Service Catalog). You use resource designs to create, modify, or delete resource instances for provisioning services. For example, use the VPN resource design to create a VPN resource instance to define resources such as route distinguishers, route targets, and so on for provisioning L3VPN, EVPN, and L2 circuit services.

Each operation—create, modify, or delete—triggers a corresponding service order, which activates a workflow. This workflow either uploads new resource instances to the Routing Director database, updates existing ones, or removes them, depending on the operation performed.

Upload Resource Pools to Routing Director

You can also upload resource pools to Routing Director by using any of the following options:

  • Upload network resources by using the Resource Instances page (Orchestration > Service > Resource Instances) of the Routing Director GUI. See About the Resource Instances Page.

  • Upload network resources by using REST APIs. See Add Network Resource Pools by Using REST APIs.

  • Upload network resources by using the service orchestration cMGD CLI.

    To add network resources by using the service orchestration cMGD CLI:

    1. Log in to the service orchestration cMGD CLI. See Access the Service Orchestration cMGD CLI.

    2. Execute the request service order load <service-order-name> command to upload a new or modified network resource service order to the service orchestration cMGD environment. See request service order load.

    3. Execute the request network resources load ? command to view all the network resources service orders available in service orchestration cMGD.

    4. Execute the request network resources load <service-order-name> command to upload the network configurations you created or modified in the service order to the Paragon Automation database. See request network resources load.

  • Upload network resources by configuring the resources in a network implementation plan.

    When you use a network implementation plan to onboard a device, the resources defined in the network implementation plan are reserved on the device. You can provision a service by using the reserved resource immediately after the device is onboarded.

    See Configure Topology Resources in Network Implementation Plan.

Related Documentation