Add an EVPN Service Instance
A superuser or network administrator can use Paragon Automation to provision an L2VPN service in their network.
Ethernet VPN (EVPN) is the only L2VPN service supported in this release. EVPN-VPWS is not supported.
When you create and save an EVPN service instance, Paragon Automation generates a create service order. After you publish the service instance, Paragon Automation activates the automated workflow for fulfilling the service order and provisions the service in the network.
You can create an EVPN service instance by uploading a preconfigured JSON file or by entering the details in the fields on the Add L2 VPN Service page.
To create an EVPN 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 publish 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. Only the Provider Backbone Bridging with Ethernet VPN (PBB-EVPN) service type is supported in this release. PBB-EVPN allows aggregation of large numbers of customer MAC (C-MAC) addresses into smaller number of backbone MAC (B-MAC) addresses, and exchange of MAC address information in the MPLS network using the BGP routing protocol. |