EVPN Eline - demo service

The demo version of Prelude come with a simple EVPN Eline demo service to showcase the Prelude service capabilities.

What we want to highlight with this service is level of abstraction we are bringing in Prelude. In the demo service as in all the tailored services we are shipping to our customers, we are trying to offer the highest level of abstraction of the underlying technology and configuration.

For exemple in the EVPN Eline demo service, you will be asked to choose between CPE endpoint or MMR (Meet Me Room) endpoint and this simple choice will lead to different configuration underneath.

EVPN Eline provisioning graph

Provisioning of an L2VPN EVPN ELine service could be sum up as follows:

Step-by-step procedure to build an Eline service

Choose a customer and Select a service type

To create a new customer in Prelude OneBoard:

1 - Navigate to Services > Dashboard and then click on New Service.

2 - Select a customer

3 - Select a service type

Create the new service

Create both sites

Then, you need to create two sites (extremity).

1 - Service overview

2 - Create a site

3 - Service overview after sites creation

Create attachment circuits on both sites

Create an attachment circuit on each site.

During the AC creation, the interface selection dropdown help you to select a usable interface.

The interface dropdown shows you all the device interface but prevents you from choosing an interface that won't work.

The excluded interfaces are:

• Infra interfaces Interfaces that are supposed to be used for infrastructure purpose not customer services.
• Incompatible interfaces Interfaces that are already supporting services which are not compatible with the service you want to configure.

Once the interface is selected, you can change the speed to make the configuration on this interface pushed with preconfigure (Only for Cisco IOS-XR).

Now, the service is fully configured in Prelude OneBoard.

Deploy the service

In Prelude OneBoard, all the services configuration is only done locally and only when explicitly requested, the configuration is pushed to the devices.

Everything that have been done until now, is only impacted OneBoard database.

To deploy the configuration to the network, you need to follow these steps:

1. Dry run the service's configuration to validate everything is ok

Navigate to the Deploy dry-run button.

Before doing anything, the system is checking that the service configuration is correct.

Then, OneBoard is asking Cisco NSO to generate the configuration dry-run for the service.

1. If you are happy with the target configurations you can click on "deploy" to try service deployment:

Prelude will ensure that we can connect to all devices before starting the configuration.

Fix deployment errors

If the service failed to deploy, it will go in state failed and you can get the deployment error from NSO by clicking on the state badge.

You can then fix the problem and simply re-try the service deployment.

One the of the usual deployment error is device out-of-sync, to fix this issue, simply go in Application Settings > Devices > Out-of-Sync device and click Sync-From in the NSO actions dropdown.