Add an EVPN or EVPN-VPWS Service Instance

A superuser or network administrator can use Routing Director to provision an L2VPN service in their network. Routing Director supports provisioning of Ethernet VPN (EVPN) and EVPN Virtual Private Wire Service (VPWS) services.

An EVPN service provides multipoint Layer 2 connectivity and enables you to connect dispersed customer sites or devices, while an EVPN-VPWS service provides point-to-point connection between two customer sites or devices over an MPLS network.

When you create and save an EVPN or EVPN-VPWS service instance, Routing Director generates a create service order. After you provision the service instance, Routing Director activates the automated workflow for fulfilling the service order and provisions the service in the network.

You can create EVPN and EVPN-VPWS service instances by uploading preconfigured JSON files or by entering the details in the fields on the Add E-LAN EVPN CSM and Add E-Line EVPN VPWS CSM service pages respectively.

To create an EVPN or an EVPN-VPWS service instance:

Click Orchestration > Instances.

The Service Instances page appears.
To add an EVPN service instance, click Add > E-LAN EVPN CSM. The Add E-LAN EVPN CSM service page appears.

To add an EVPN-VPWS service instance, click Add > E-Line EVPN VPWS CSM. The Add E-Line EVPN VPWS CSM service page appears.
In the General section of the Add E-LAN EVPN CSM page, enter the values by referring to Table 1.

In the General section of the Add E-Line EVPN VPWS CSM page, enter the values by referring to Table 2.
Click Next to proceed to the Site Settings section.
Enter site-specific details in the Site Settings section. See Add EVPN or EVPN-VPWS Service Site Details.
Click Next to proceed to the Summary section.

You see a graphical map of your service topology and a summary of the instance details in the Summary section. You can zoom in and zoom out using the zoom options on the map.
(Optional) Click Export to export and save the service details in JSON format on your local system.
(Optional) Click Reset Placements to remove existing placement configurations for the service instance.

Provisioning of a service instance might fail when existing placement configurations for the service instance are no longer available or applicable. When you reset placement parameters, service orchestration automatically assigns placement options for the instance before provisioning the service.
Click Next to proceed to the Schedule section.
(Optional) Switch the Schedule toggle on if you want to schedule when to provision the service. The Schedule option is disabled by default. When you schedule provisioning, the Save & Provision button on top of the page is disabled and grayed out.

The Schedule field appears. Perform the following steps to schedule the date and time to provision the service:
1. Click the calendar icon in the Schedule field.
2. Select the date and time for provisioning the service, and click OK.
  The scheduled date and time are displayed in the MM/DD/YYYY HH:MM AM/PM format.
  Note:
  
  You must set a present or future date and time to schedule provisioning of a service. If you select a past time and save the service order, the service is provisioned immediately.
  
  To delete a provisioning schedule, select the Service-Instance-Name on the Service Instances page and click the edit icon. On the Modify Service-Instance-Name page, proceed to the Schedule section. In the Schedule section, switch the Schedule toggle off and click Save. The provisioning schedule is deleted and the service instance is provisioned immediately.
  
  Scheduling of service provisioning is a Beta feature in this release.
To save and provision the service instance, click one of the following buttons:
- Save & Provision—Click this button and confirm when prompted, to save the service instance to the Routing Director database and provision the instance immediately. This option is disabled if you have scheduled the provisioning of a service instance.
- Save—Click this button to save the service instance to the Routing Director database.
  
  The Service Instances page appears and the new service instance is listed in the Service Instances table. To provision the service instance, select the service instance and click Provision. Alternatively, you can schedule provisioning of the service instance as defined in step 10.
  Note:
  
  The Provision button is disabled if you schedule the provisioning of a service instance. The service is provisioned automatically at the scheduled date and time.

Note: Fields marked with an asterisk (*) are mandatory.

Table 1: Fields in the Add E-LAN EVPN CSM Service Page General Section
Field	Description
Upload JSON File	Click Browse to upload a preconfigured JSON file. You see a message that the file is successfully imported. The values specified in the file are automatically populated in the corresponding UI fields. Note: If you are uploading a preconfigured JSON file to create an EVPN service instance, you must clear the placement section in the file before you provision the service order.
Customer*	Enter the name of the customer for whom you are provisioning the service: If you already added the customer name by using the Customer Inventory page (Orchestration > Service > Customers), click the Customer field to see a drop-down with the customer names that you added. Select the customer name from the drop-down list. Alternatively, click the Add Customer link to create a new customer. See Add a Customer. The customer name must be unique within an organization. For example, network-operator.
Instance name*	Enter a name for the service instance. For example, evpn1. The instance name can be a set of alphanumeric characters and the special character hyphen (-). The maximum number of characters allowed is 64.
VPN Id*	Enter the ID you want to assign to the VPN. For example, vpn10. The VPN ID must not exceed 64 characters.
VPN Service Topology	The topology for the VPN service. Only the any-to-any topology is supported in this release. In this service topology, all VPN sites can exchange network traffic with each other without any restrictions.
VPN Service Type	The service type for EVPN service provisioned by the service provider. Routing Director supports only the EVPN-MPLS service type.

Table 2: Fields in the Add E-LINE EVPN VPWS CSM Service Page General Section
Field	Description
Upload JSON File	Click Browse to upload a preconfigured JSON file. You see a message that the file is successfully imported. The values specified in the file are automatically populated in the corresponding UI fields. Note: If you are uploading a preconfigured JSON file to create an EVPN-VPWS service instance, you must clear the placement section in the file before you provision the service order.
Customer*	Enter the name of the customer for whom you are provisioning the service: If you already added the customer name by using the Customer Inventory page (Orchestration > Service > Customers), click the Customer field to see a drop-down with the customer names that you added. Select the customer name from the drop-down list. Alternatively, click the Add Customer link to create a new customer. See Add a Customer. The customer name must be unique within an organization. For example, network-operator.
Instance name*	Enter a name for the service instance. For example, evpn-vpws1. The instance name can be a set of alphanumeric characters and the special character hyphen (-). The maximum number of characters allowed is 64.

Add an EVPN or EVPN-VPWS Service Instance

Related Documentation