Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?


About the Service Instances Page

The Service Instances page lists the services that you (service provider) have created in an organization and intend to provision for your customers. This includes service instances for L3VPN service provisioning. The service instances are listed by name, customer name, the associated service design, devices on which the service is provisioned, and so on.

To access the Service Instances page, click Orchestration > Instances on the navigation menu.

Tasks You Can Perform

You can perform the following tasks on the Service Instances page:

  • View details of service instances.

    Use one of the following options to view details about a service instance:

    • To view service details on the right pane:

      • Hover over the service instance and click the Details icon that appears next to the service instance name.

      • Select the service instance and click More > Detail.

      The service-instance-name pane appears on the right side of the GUI. For information about the details of the fields, see Table 1.

    • Click the service-instance-name hyperlink and view details on the service-instance-name Details page. See View Service Instance Details.

  • Create L3VPN service instances. See Add an L3VPN Service Instance.

  • Modify L3VPN service instances. See Modify an L3VPN Service Instance.

  • Provision a service instance

    To provision a service instance, select the service instance and click Publish. After you publish, a service order is generated. You can view the service order in the Service Orders page (Orchestration > Monitoring > Service Orders) and the execution of the corresponding workflow on the Workflows (Orchestration > Monitoring > Workflows) page.


    You can only provision L3VPN service in this release.

  • Deprovision a service—To delete or deprovision a service from your network, select the service instance and click More > Deprovision. Click Yes when prompted for confirmation.

  • Download sample network resource pools—To download sample resource pools, click More > Download Sample Network Resources. The following files are downloaded to your local system:

    • topo_sample.json.txt—contains samples for L3VPN service topology parameters such as point-of-presence (PoP).

    • vpn_resources_sample.json—contains samples for route distinguisher and route targets for the L3VPN service.

  • Upload and view network resource pools—As a prerequisite to creating L3VPN service instances, you must upload topology and VPN network resources to the Paragon Automation database. Paragon Automation uses these network resources for automatic configuration of service parameters.

    To upload network service resources as JSON files, click More > Upload Network Resources. See Add Network Resources for L3VPN Service.

    To view the network resources, click More > View Network Resources. The Network Resources page displays all network resource pools available in the Paragon Automation database.

  • Export details of a service instance in the JSON format—To export a service instance in the JSON format and save it on your local system, select the service instance and click More > Export. The plan.service-instance-name.json file is downloaded to your local system.

  • Filter the data displayed in the table—Click the filter icon (funnel) and select whether you want to show or hide advanced filters. You can then add or remove filter criteria, save criteria as a filter, apply or clear filters, and so on. The filtered results are displayed on the same page.

  • Search by using keywords—Click the search icon (magnifying glass), enter the search term in the text box, and press Enter. The search results are displayed on the same page.

  • Show or hide columns in the table or reset page preferences, using the vertical ellipsis menu.

Field Descriptions

Table 1 lists the fields on the Service Instances page.

Table 1: Fields on the Service Instances Page




Name of a service instance.


Name of the customer for whom you are provisioning a service.

Service Design

Name of the service design associated with the service instance.

Design version

Service design version associated with the service instance.


Hostnames of the devices on which you are provisioning the service.

Device Count

Number of devices on which you are provisioning the service.


Sites that connect to the service.


The execution state of the service order generated for the service instance. A service order can have the following execution states:

  • Success—The service order is successfully executed.

  • Success with warnings—The service order is successfully executed but certain tasks in the workflow have failed. You can view the tasks that have failed and take appropriate action if required. To view detailed task logs, navigate to the Orchestration > Workflows > run details page. See View Workflow Run Details.

  • Processing—The service order is in the process of being executed.

  • Failed—The service order has failed to execute.

Status Message

Additional information about the status of the service order initiated for the service instance. The status is Uploaded after the service instance is saved (either after creating or modifying).

Last Modified

The date and time when the service instance was last modified.

Last Modified By

Name of the user who last modified the service instance.