Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
 

Service Provisioning Workflow

Service orchestration automates provisioning of Layer 3 VPN (L3VPN), Layer 2 Ethernet VPN (EVPN), and Layer 2 circuit (L2 circuit) services and monitoring of the health and quality of a service after it is provisioned. Paragon Automation provides predefined service designs that contain the guidelines and templates for executing the service provisioning and monitoring workflows for the services.

Note:

  • Ethernet VPN (EVPN) is the only L2VPN service that is supported in this release. EVPN-VPWS is not supported.

  • LDP signaling without BGP autodiscovery is the only variant of L2 circuit that is supported in this release.

  • Redundant pseudowires for L2 circuit are not supported in this release.

The service provisioning workflow includes tasks such as configuring network resources, defining service elements and initiating service orders for service provisioning, monitoring service order execution states, and troubleshooting issues by monitoring task logs. A network administrator or a superuser provisions a service by using the Paragon Automation GUI, REST API, or the service orchestration cMGD CLI.

To provision a service:

  1. Add customer names in the Customer Inventory page. See About the Customer Inventory Page.

  2. View the installed service designs with version numbers on the Service Designs page. Network administrators and observers have read-only access to this page. Superusers can manage the service design catalog and perform tasks like installing the latest available version of a service design and setting the default service design version. See About the Service Designs Page and Manage Service Design Versions.

    Superusers with root user privileges can manage service designs by using the service orchestration cMGD CLI. See About the Service Orchestration cMGD CLI.

  3. Configure and upload network resources for the services by using the Paragon Automation GUI, REST API, or the service orchestration cMGD CLI. See Add Network Resources for Provisioning Services, About the Resource Instances Page, and request network resources load.

  4. Create or modify service instances by entering data in the corresponding fields in the Paragon Automation GUI or by uploading preconfigured JSON files:

    To modify a service instance, see Modify a Service Instance.

    When you create or modify a service instance, a create or modify service order is generated for these operations.

  5. Provision the service instance by clicking the Provision button on the Service Instances page. Provisioning a service instance generates a service order to activate the create or modify workflows.

    You can also delete a service instance by clicking More > Deprovision on this page to generate a delete service order to activate the delete workflow. See About the Service Instances Page.

  6. View details of the service order and the execution status of the service order on the Service Orders page. See About the Service Orders Page.

  7. Monitor the workflow run details for each service order from the Workflows page (Orchestration > Monitoring > Workflows). By viewing detailed task logs, you can troubleshoot issues when a workflow run fails. See About the Workflows Page.

As a superuser with root user privileges, you can perform service provisioning tasks by using the service orchestration cMGD CLI. For more information, see About the Service Orchestration cMGD CLI.

Before provisioning a service in the network, Paragon Automation validates the service configuration on all the devices on which the service is provisioned. Paragon Automation automatically configures passive device monitoring rules (for L2 circuit services) and active data plane tests (for L3VPN and EVPN services) to monitor the health and quality of the service after provisioning. You can view the monitoring data generated for each service instance. See View Service Instance Details.

Related Documentation