Add an EVPN or EVPN-VPWS Service Instance
A superuser or network administrator can use Paragon Automation to provision an L2VPN service in their network. Paragon Automation 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, Paragon Automation generates a create service order. After you provision the service instance, Paragon Automation 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:
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:
The customer name must be unique within an organization. |
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. 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. Note that, Paragon Automation supports only the EVPN-MPLS service
type, though the selection option is displayed as
|
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:
The customer name must be unique within an organization. |
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. |