Migrate a Brownfield Service to Routing Director

Pre-requisites to Migrating Brownfield Services

As a Pre-requisites to importing the services from brownfield devices, perform the following steps:

1. Make a list of all the services to be imported.

2. Make a note of the resources used by the services, including:

   • Interfaces and VLANs
   • interface units
   • Integrated Routing and Bridging (IRB) interfaces
   • Link Aggregation Control Protocol (LACP) system IDs
   • LACP admin keys
   • Ethernet Segment Identifiers (ESI)
   • Route Distinguishers
   • Route Targets
   • Virtual circuit identifiers (VCID) for Layer 2 circuit services
   • VPN communities
   Note: For migrating the Q-in-Q interface configuration in a brownfield service to Routing Director, you must configure a range of Ethernet interface units that would be associated with the service. For information, see Units.

Migration Workflow

To migrate or import a brownfield service to Routing Director that is configured on a single device:

1. In Routing Director, configure a network implementation plan to onboard the brownfield devices. Ensure that the Pinned Reservation under access parameters (for both logical ports and aggregated Ethernet interface ports) have Brownfield set to true.

   Optionally, include the name of the customer and the service instance for which you want the access parameters to be used as resources.

   Note:

   If you do not plan to use a network implementation plan, ensure that you:

   • Create a topo resource instance with required nodes, access parameters, aggregated Ethernet interfaces, route distinguishers, and so on.

   • Configure the pinned reservation for those resources. In the pinned reservation, enter the same instance name as the brownfield service that you want to migrate.

   For information about creating a topo resource, see Create a Topology Resource Pool.

   For detailed information about creating a network implementation plan, see Add a Network Implementation Plan.

2. Identify the services on the devices that you want to migrate to Routing Director.

3. Create the required VPN resources and l2-address for the identified services:

   • VPN resources—VPN community, route distinguisher, route target, and virtual circuit ID.

   • L2 address—EVPN ESIs, LACP admin keys, and LACP System IDs.

   For information about creating VPN resources and L2 address resources, see Create a VPN Resource Pool and Create a Layer 2 Resource Pool respectively. Ensure to configure pinned reservation for the resources.

4. Create a service instance for the service you want to migrate. See the Provision VPN Services chapter in this guide for details.

   In the service instance:

   • Under General > Service Settings, ensure to enable Use instance name instead of UUID in device configuration to use the instance name instead of UUID.

   • Under General > Pinned Reservation, ensure to enable Brownfield and Instance fields. Optionally, enable Customer. When you enable Brownfield in a service instance, the service instance uses reserved resources (pinned resources). Enabling the Customer and the service instance ensures that the service uses resources exclusively reserved for the specific service and the specific customer.

5. Save the service instance.

6. Execute dry run with validation to validate the configured service instance.

   To execute dry run on a service, on the Service Instance page, select the service and click More > Dry run with Validation.

   When you execute dry run on a service instance, the configuration generated for the service instance is validated on the devices without changing the current configuration on the devices. You can view the generated dry-run configuration on the Service Configuration tab of the Service Instance Details page (More > Details).

7. Verify the dry-run configuration generated for each device against the existing configuration on the devices.

8. Do one of the following:

   • Provision the service if the generated dry-run configuration matches with the configuration on the devices.

     To provision the service on the Service Instances page (Orchestration > Service > Instances), select the service and click Provision.

   • If the generated dry-run configuration does not match with the device configuration, edit the service instance to correct the generated dry-run configuration. Alternatively, update the placement resources by using the Update Placement button and then cancel the changes made to the placement SNAs by clicking the Cancel button.

9. After the service is successfully provisioned by Routing Director, delete the brownfield service configuration provisioned before migration from the devices and commit the configuration on the device.

Migration of brownfield services is complete and you can use Routing Director to orchestrate and manage the brownfield services. After all the services are migrated, you can release the pinned reservation by disabling the Brownfield, Customer, and Instance flags configured in the service instance and resources. so that the released resources can be used by any other service that needs them.

If a service spans a large number of devices, the service must be migrated to Routing Director in several steps. The brownfield service must be initially created in Routing Director with a small subset of Site Network Access (SNA) and only those SNAs must be migrated. After the service is migrated with the subset of SNAs to Routing Director, update the service with the remaining SNAs. The workflow for updating the service with the remaining SNAs is the same as the procedure outlined for migrating a service on a single device, namely:

1. Define pinned resources to be used.

2. Update the service.

3. Execute dry run to verify that the new configuration match for the updated SNAs. Executing dry run keeps the existing configuration for that service on a device untouched.

4. Provision the service after verification by clicking the on the Provision button on the Service Instances page (Orchestration > Service > Instances),

After the service is provisioned on all the devices, remove the pinned reservation on the resources and service using any of the options listed in table. Always disable or set the resource flag and fields first before disabling or setting the service flags.