Service Provisioning Workflow

Service orchestration automates provisioning of Layer 3 VPN (L3VPN), Layer 2 Ethernet VPN (EVPN), Layer 2 EVPN Virtual Private Wire Service (VPWS), and Layer 2 circuit (L2 circuit) services and monitoring of the health and quality of a service after it is provisioned. Routing Director provides predefined service designs that codify the guidelines for executing the service provisioning and monitoring workflows for the services.

Note:

LDP signaling without BGP autodiscovery is the only variant of L2 circuit that is supported.

The service provisioning sequence of activities 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 Routing Director 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 and manage the installed service designs.

   View the installed service designs their 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.

   You can configure network resources by using the Routing Director 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 service instances to provision VPN services.

   Create service instances by entering data in the corresponding fields in the Routing Director GUI or by uploading preconfigured JSON files:

   • To create an L3VPN service instance, see Add an L3VPN Service Instance.

   • To create an EVPN service instance, see Add an EVPN Service Instance.

   • To create an EVPN-VPWS service instance, see Add an EVPN-VPWS Service Instance.

   • To create an L2 Circuit service instance, see Add an L2 Circuit Service Instance.

   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.

   You can provision a service instance when you create the service instance or when you select the service instance and click the Provision button on the Service Instances page. Provisioning a service instance generates a service order to activate the create or modify workflows.

   Before provisioning a service in the network, Routing Director validates the service configuration on all the devices on which the service is provisioned.

   See About the Service Instances Page.

6. View the service order generated for the service.

   A service instance is implemented through a service order. View details of the service order and the execution status of the service instance on the Service Orders page.

   See About the Service Orders Page

7. View the workflows that are executed as part of the service order.

   Monitor the workflow run details for each service order from the Workflows page.

   By viewing detailed task logs, you can troubleshoot issues when a workflow run fails. See About the Workflows Page.

8. View post provisioning monitoring data data.

   Routing Director automatically configures passive device monitoring rules for all services and active data plane tests for L3VPN services to monitor the health and quality of the service after provisioning. To view the monitoring data generated for each service instance, see View Service Instance Details.

   To view active assurance Tests and Monitors data to monitor the quality of L3VPN services after provisioning, under the Active Assurance tab, see View Service Instance Details.

   To view passive assurance monitoring data to monitor the health of a VPN service and its components after provisioning, see View Passive Assurance Monitoring Data.

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.