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 Service
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.
Route Distinguisher Type	Select the route distinguisher (RD) type. The default RD type is Type 0. If Type 0 is selected, after the service instance is configured and the placements are updated, the Type 0 values are populated from the VPN resource pool in the Route Distinguishers table at the bottom of the page. If Type 1 is selected, the Type 1 values are populated from the NIP or topo resource pool in the Route Distinguishers table at the bottom of the page.
EVPN Service Type	Select the type of EVPN service: vlan-aware—VLAN-aware supports multiple broadcast domains to map to a single bridge domain. Multiple VLANs are mapped to a single EVPN instance and share the same bridge table in the MAC-VRF table. Note: This is a Beta feature this release. The VLAN-aware EVPN service type is not supported for untagged interfaces and Q-in-Q tagged interfaces. vlan-based—VLAN-based supports a one-to-one mapping of a single broadcast domain to a single bridge domain. Each VLAN is mapped to a single EVPN instance, resulting in a separate bridge table for each VLAN. The default EVPN service type is vlan-based.
Multiplatform	Switch the Multiplatform toggle to True to enable the VPN service to span multiple device platforms. The default setting is False. Note: When Routing Director is upgraded from release 2.5.0 to release 2.6.0, the toggle button is automatically set to true.
Route Target
Number	Enter the number of route targets. The block size entered when configuring a VPN resource pool is the upper limit for the route target number. The entered block size is displayed to the right of the text box.
Pool	Select a pool value. The ASN values specified when configuring a VPN resource pool are available as options in the drop-down list.
Pinned Reservation Configure the service to use reserved resources (pinned resources).
Brownfield	Enable this flag if this is a brownfield service. When enabled, this service would be provisioned by using resources reserved for migrating brownfield services to Routing Director.
Customer	Enable this flag to allow the service to be provisioned by using resources that are exclusively reserved for the customer associated with this service.
Instance	Enable this flag to allow the service to be provisioned by using resources exclusively reserved for this service.
Placement IRB Select the PE node and click the edit icon. The Placement IRB page appears. The Placement IRB section appears only when you use the update placements option. If you selected vlan-based as the EVPN service type on the General page, configure the placement parameters by referring to the following table:
PE Node	Displays the PE device assigned to the IRB instance.
IRB	Enter the IRB interface ID for the PE device from the available range of interface IDs. The available range of IRB interface IDs is specified when you configure the topology resource instance and is displayed next to the IRB text box.
If you selected vlan-aware as the EVPN service type, configure the placement parameters by referring to the following table:
PE Node	Displays the PE device assigned to the IRB instance.
VLAN	Displays the VLAN ID assigned to the PE device.
IRB	Enter the IRB interface ID for the PE device from the available range of interface IDs. The available range of IRB interface IDs is specified when you configure the topology resource instance and is displayed next to the IRB text box.
Service Settings Enter common settings applicable for the service.
Use instance name instead of UUID in device configuration.	Toggle to True to use the service instance name, instead of UUID, in the device configurations. The specified name is used in configuration such as routing instance name, filter name, policer name, community name, policy statement name, and so on. The instance name must be unique across customers and can be a maximum of 32 characters long. Disable it to set it to False, so that the service instance name is auto-converted to a UUID and used in the device configuration. The UUID is a system generated alphanumeric value. This option is disabled, by default.
Route Distinguishers Update placements and configure the service instance to see the assigned RDs.
For Type 0 Route Distinguishers
PE Node	The name of the PE node device.
Pool	The unique RD identifier configured as the ASN in the VPN resource pool. When the service is configured, the combination of the pool ID a Routing Director assigned number is visible in the device CLI in the format `pool:number`. For example, 60000:9.
Number	A unique number assigned to the RD by Routing Director. In the previous example, the number is 9.
For Type 1 Route Distinguishers
PE Node	Name of the PE node device.
IP Address	Loopback address of the device. If you want to change the loopback address for the device, you can edit the entry from the available preconfigured loopback addresses. To edit, select the RD, click the pencil icon, and select another loopback address from the drop-down list.
Name	Unique RD identifier populated from the configured names in the topo resource instance.
Assigned Number	A unique number assigned to the RD by Routing Director from the block size configured in the topo resource instance. To change the assigned number, select the RD, click the pencil icon, and edit the number from the preconfigured range visible next to the textbox. When the service is configured, the combination of the loopback address and the assigned number is visible in the device CLI in the format `loopback_IP:number`. For example, 192.168.1.1:30.

Note:

Configuring IRB interfaces for an E-LAN EVPN CSM service is qualified only for the following scenarios:
- EVPN with Ethernet interface port mode.
- EVPN with Ethernet interface VLAN mode.
- EVPN with Aggregate Ethernet interface port mode.
- EVPN with Aggregate Ethernet interface VLAN mode.

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.
Pinned Reservation Configure the service to use reserved resources (pinned resources).
Brownfield	Enable this flag if this is a brownfield service. When enabled, this service would be provisioned by using resources reserved for migrating brownfield services to Routing Director.
Customer	Enable this flag to allow the service to be provisioned by using resources that are exclusively reserved for the customer associated with this service.
Instance	Enable this flag to allow the service to be provisioned by using resources exclusively reserved for this service.
Service Settings Enter common settings applicable for the service.
Use instance name instead of UUID in device configuration.	Toggle to True to use the service instance name, instead of UUID, in the device configurations. The specified name is used in configuration such as routing instance name, filter name, policer name, community name, policy statement name, and so on. The instance name must be unique across customers and can be a maximum of 32 characters long. Disable it to set it to False, so that the service instance name is auto-converted to a UUID and used in the device configuration. The UUID is a system generated alphanumeric value. This option is disabled, by default.

Add an EVPN or EVPN-VPWS Service Instance

Related Documentation