Add a Network Implementation Plan

You must be a user with the Network Admin or Super User role to add a network implementation plan.

You can create a network implementation plan in one of the following ways:

Create a network implementation plan by importing an existing configuration into the Network implementation plan wizard in JSON format.

To create a plan from existing configuration, click Browse to upload the JSON file. The values in the JSON file are populated in the Network Implementation Plan wizard.

(Optional) Edit values if needed and save the plan. The plan is saved and listed on the Network Implementation Plan page.
Create a new plan by manually entering values. To create a new plan by entering values, follow the steps in this topic.

Note:

If placement resources are defined in multiple device profiles and associated with a plan, the values from the profile that is applied last to the device will take precedence.
If placement resources are defined in both device profiles associated with the plan and also in the plan, the values defined in the plan are used. The IRBs, RDs, and logical tunnel lists from the device profiles are also replaced by the values in the plan.

To add a network implementation plan by entering values manually:

Navigate to Inventory > Device Onboarding > Network implementation Plan.
The Network Implementation Plan page appears.
On the Network implementation Plan page, click + (Add) to create a network implementation plan.

The Create Network Implementation Plan page appears.
Enter a name for the network implementation plan.

The plan name can contain alphanumeric characters (a-z, A-Z, and 0-9) and some special characters [period (.) and hyphen (-)], and cannot exceed 64 characters. For example, plan-for-pe-device.
In Use Cases, select one or more of the following use cases that you want to configure in the network implementation plan:
- Active Assurance
- Infrastructure Configuration
- Observability
- Optimization
- Service Orchestration
Click Select all to select all the use cases at once. The fields displayed in the tabs of the network implementation plan configuration wizard depends on the use-case that you select. The following tabs are present on the wizard:
- General—Use the General tab to enter general information such as description, and select device profiles, interface profiles, and port profiles from which the devices should derive their configuration. See Table 1 for details.
  
  Click Next to add devices to the plan.
- Devices—Use the Devices tab to associate devices with the plan. You can use the plan to:
  - Configure devices while the device is being onboarded to Routing Director.
  - Manage the configuration of devices after the devices are onboarded.
  - Edit and delete the devices added to the plan from the Devices tab.
  See Devices Tab for details. Click Next to configure links between the devices.
- Links—Use the Links tab to configure links between the devices added to the plan.
  
  For information, see Table 9. You can also edit and delete the links configured between devices from the Links tab.
- Summary—Use the Summary tab to view a summary of the network implementation plan. Click the Edit link to edit the general information or the links added to the devices,
Click Save to save the plan.
The plan is listed on the Network Implementation Plan page.
Click More > Trigger Onboarding to commit the configuration in the network implementation plan on the associated devices. If a device is not yet onboarded, the configurations are committed, when the device is onboarded.

After you create a network implementation plan, the devices included in the plan can be onboarded to and managed by Routing Director.

Table 1: Fields on the General tab of the Network Implementation Plan
Field	Description
General
Upload JSON File	Click Browse to import a pre-created network implementation plan in JSON format. The values in the pre-created plan are automatically populated in the Add Network Implementation Plan page. Click the Download this form into JSON file link to download and save the profile in its current state (for example, when you want to save the current configured values for later reference or for maintaining a record).
Plan Name*	If you are creating a plan, enter a name for the plan. The plan name can contain alphanumeric characters (a-z, A-Z, and 0-9) and some special characters [period (.) and hyphen (-)], and cannot exceed 64 characters. For example: plan-for-pe.
Use Cases	Select the use cases for which you want to configure the network implementation plan. Tabs and fields are displayed for configuration depend on the use case you select. Click Select All to select all the use cases. The selected user cases cannot be cleared after the network implementation plan is published and used by the associated devices.
Description	Enter a description for the plan.
Default Device Profile	Select one or more device profiles to be used in the plan. You can view only those device profiles that you associate with the plan while creating the profile. If you are editing an automatically generated implementation plan, the default interface and device profiles are already populated. Configurations in the default device profile are common to all devices and applied to all the devices included in the plan. Alternatively, click the Add new device profile link to create a device profile to be used as the default device profile. See Add a Device Profile.
Default Interface Profile	Select one or more interface profiles to be used in the plan. You can view only those interface profiles that you associate with the plan while creating the profile. The configurations in the default interface profile are common to all interfaces and applied to all the interfaces configured in the plan. Alternatively, click the Add new interface profile link to create an interface profile to be used as the default interface profile. See Add an Interface Profile.
Default Port Profiles	Select one or more port profiles to be used in the plan. You can view only those port profiles that you associate with the plan while creating the profile. The configurations in the default port profile are committed on aggregated Ethernet interfaces that are included in the plan. Alternatively, click the Add new port profile link to create a port profile that can be used as the default port profile. See Add a Port Profile.

Devices Tab
Links Tab

Devices Tab

To add a device to the network implementation plan and configure the device:

Click + (Add) icon above the Devices table.

The Add Device page appears.
Enter values in the General tab of the Add Device page by referring to Table 2.

If you have selected Infrastructure Configuration use case, configure additional fields by referring to Table 3

If you have selected Service Orchestration use case, configure additional fields by referring toTable 4
Click Next to view the Physical Ports tab.
In the Physical Ports tab:
- View a graphical representation of the device chassis. Zoom in and zoom out the chassis view.
  Note: The chassis view is supported only for:
  - ACX7024
  - ACX-7024X
  - ACX7100-32C
  - ACX7100-48L
  - ACX7348
  - ACX7509
  - ACX7020
  - MX304
  - MX10004
  - MX204
- View the ports (interfaces) on the device chassis.
- View all the managed interfaces on the device by selecting the Show Managed Interfaces only check box. A managed interface is an interface that is managed by the Service Orchestration component of Routing Director.
- Change managed interfaces to unmanaged interfaces and unmanaged interfaces to managed interfaces.
  - To change managed interfaces to unmanaged, select the managed interfaces and click Set Unmanaged,
  - To change Unmanaged interfaces to managed, select the unmanaged interfaces and click Set Manage.
- Add and configure logical interfaces on the ports. During the migration of existing services to Routing Director, ensure that only CE-facing interfaces are included and configured.
  
  To add a logical port, click the Add (+) icon to specify and configure a port.
  
  See Table 5 for details.
  
  If you have selected Infrastructure Configuration use case, configure additional fields by referring to Table 6
  
  If you have selected Service Orchestration use case, configure additional fields by referring to Table 7
- Add and configure aggregated Ethernet interfaces. During the migration of existing services to Routing Director, ensure that only CE-facing interfaces are included and configured.
  
  To add and define an aggregated Ethernet interface, click the + (Add) icon to specify and configure the port. See Table 8.
  
  Note:
  To migrate a service from an earlier release of Routing Director to a later release, services using ports with aggregated Ethernet interfaces must add the port in the network implementation plan with its access parameters configured. The access parameters must not have VLAN configuration.
- In the Count field under Link Aggregation Group (LAG) Settings, enter the number of LAGs that can be configured on the device (The maximum number of LAGs supported on a device depends on the device type.
  
  The LAG settings section is visible only when Interface Configuration or Service Orchestration use cases are selected in the plan.
- Edit or delete the ports that you added.

Table 2: Fields on the General tab of the Add Device Page
Field	Description
Name*	Enter a name for the device. Routing Director uses this name internally. The name can contain alphanumeric characters and some special characters [hyphen (-) and underscore (_)]. The name cannot exceed 64 characters. Alternatively, enter the hostname of the device and click the Search icon to populate the device values from the network inventory on this page. For example, Singapore-ACX-05.
Site*	Select the site where you want to install the device. Alternatively, if you have permissions to add a site, you can view the Add new site link next to the Site drop-down list. Click the link and add a new site on the Create Site page. See Add Sites.
Serial Number	Enter the serial number of the device that you want to associate with the plan. The serial number will be used to map the device to this profile when it is added to the inventory (during adoption which is described later), and the onboarding process is started. For example, XXXXXXXXXXXX.
Vendor	Select the vendor of the device. For example, Juniper Networks
Model*	Select the model of the device from the drop-down list. For a list of supported devices, see Supported Junos OS Releases, Devices, and Browsers. For example, ACX7024.
Device Profiles	Select one or more device profiles to be applied to the device from the drop-down list. The configurations in the device profiles are committed on the device in the order in which the profiles are added to the plan. Configurations present in both the default device profile and the specific profiles that you enter here are committed on the device. However, for configurations that are present in both the specific device profiles and the default device profile, the values in the specific device profiles override the configuration in the default device profile.

Table 3: Additional fields on the General tab for Infrastructure Configuration use case
Field	Description
Hostname	Enter a hostname for the device. The name can contain alphanumeric characters and some special characters [hyphen (-) and underscore (_)]. The hostname cannot exceed 64 characters. If you do not enter a hostname, Name is used as the hostname. For example, Singapore-ACX-05.
IPv4 Loopback	Enter an IPv4 loopback address for the device in the dotted decimal notation format. For example, 10.10.10.1. The value that you enter here overrides the value that is configured in a device profile. For example, 127.0.0.1.
IPv6 Loopback	Enter an IPv6 loopback address for the device. For example, 2001:db8:4136:e378:8000:63bf:3fff:fdd2. The value that you enter here overrides the value that is configured in a device profile. For example, 2001:db8::1.
Software Image	Select the software image to be installed on the device during onboarding from the drop-down list. All software images that are uploaded to Routing Director are listed here. For example, junos-evo-install-media-usb-acx-f-x86-64-25.2R1.8-EVO.img

Table 4: Additional fields on the General tab for Service Orchestration use case
Field	Description
Placement Resources Enable or disable (default) allocating resources for provisioning services on the device. Note: If placement resources are defined in both device profiles associated with the plan and also in the plan, the values defined in the plan are used. The IRBs, RDs, and logical tunnels lists from the profiles are also replaced by corresponding values configured in the plan.
Bandwidth*	Enter the bandwidth (in Mbps) to be reserved on the device for service provisioning. Note: If you are configuring a PE node, you must configure bandwidth for the PE node to appear as a resource for a service. For example, 100Mbps.
MAC Address	Enter the maximum number of MAC addresses to be assigned to the device for service provisioning. For example, 20.
Routes	Enter the maximum number of routes addresses to be assigned to the device for service provisioning. For example, 50.
Units Click Add above the Units table to add a range of Ethernet interface units. You must configure units if you want to migrate L3VPN Q-in-Q configuration to Routing Director.
Name*	Enter a name for the range of Ethernet interface unit. For example, eth-vpn-100 to eth-vpn-105.
Size*	Enter the number of interface units in the range. For example, a size of five will configure five distinct interface units on the Ethernet interface. Range: 0 through 4095.
Start*	Enter the first interface unit in the range. For example, assigning 100 as the Start value configures interface units from 100 up to 104 for a range size of five. Range: 0 through 4095.
Pinned Reservation Reserve the interface units for specific services.
Brownfield	Enable this flag to reserve the interface units in the defined range on the PE access interface for migrating brownfield services. The reserved interface units would be used by services that are configured to use pinned resources and have the Brownfield flag enabled. Disabling this flag while the reserved interface units are in use by a service will release the reservation. If the service is reprovisioned without disabling the Brownfield flag, the service will be disrupted due to missing resource allocation.
Customer	Select a customer whose services would use the defined interface units. The interface units will be used exclusively by services provisioned for the customer that you select here.
Instance	Enter the name of the service instance that can use the defined interface units. Note: For migrating a brownfield service, the service instance name that you enter here must match with the service that you want to migrate. The interface units will be used exclusively by the service that you enter here for the customer specified in Customer.
Route Distinguisher Type 1 Click the + (Add) icon to configure a range of Type 1 route distinguishers (RDs) during device onboarding. If you do not configure, Routing Director automatically configures the range.
Name*	Enter a name for the range of route distinguishers being configured. For example, RD-CORP-BLR-VPN
Size*	Enter the number of route distinguishers to be defined within the range. For example, a size of 10 will configure 10 distinct route distinguishers on the device.
Start*	Enter the starting number of the route distinguisher range. For example, assigning 20 as the Start value configures route distinguishers starting from 10.10.10.1:20 up to 10.10.10.1:29, assuming a range size of 10.
Pinned Reservation Reserve the RDs for specific services.
Brownfield	Enable this flag to reserve the defined RDs for migrating brownfield services. The reserved RDs would be used by services that are configured to use pinned resources and have the Brownfield flag enabled. Disabling this flag while the reserved RDs are in use by a service will release the reservation. If the service is reprovisioned without disabling the Brownfield flag, the service will be disrupted due to missing resource allocation.
Customer	Select a customer whose service would use the defined RDs. The RDs will be used exclusively by services created for the customer that you select here.
Instance	Enter the name of the service instance that can use the defined RDs. Note: For migrating a brownfield service, the service instance name that you enter here must match with the service that you want to migrate. The RDs will be used exclusively by the service that you enter here for the customer specified in Customer.
IRBs Enable or disable (default) integrated routing and bridging (IRB) interfaces on a PE device.
Start*	Enter the starting IRB interface unit available on the PE device. For example, assigning 10 as the Start value configures IRB interfaces from irb.10 to irb.14, assuming a size of 5. Enter a value in the range 0 through 65,535.
Size*	Enter the number or range of IRB interface units available for a PE device. For example, a size of 5 will configure five distinct IRB interface units on the device. Enter a value in the range 0 through 65,535.
IRBs > Migration Click the + (Add) to configure a range of IRB interface units to be used for migrating brownfield services to Routing Director.
Name*	Enter a name for the range of IRB interface units being configured. For example, IRB-HQ-Access.
Size*	Enter the number of IRB interface units to be defined within the range. For example, a size of 5 will configure 5 distinct IRB interface units on the device. Range: 0 through 65,535
Start*	Enter the starting number of the IRB interface units in the defined range. For example, assigning 10 as the Start value configures IRB interfaces from irb.10 to irb.14. Range: 0 through 65,535
Pinned Reservation Reserve the defined IRB interface units for specific services.
Brownfield	Enable this flag to reserve the defined IRB interface units for migrating brownfield services. The IRB interfaces would be used by services that are configured to use pinned resources and have the Brownfield flag enabled. Disabling this flag while the reserved interface units are in use by a service will release the reservation. If the service is reprovisioned without disabling the Brownfield flag, the service will be disrupted due to missing resource allocation.
Customer	Select the customer whose service would use the defined IRB interface units. The IRB interface units will be used exclusively by services provisioned for the customer that you select here.
Instance	Enter the name of the service instance that can use defined IRB interface units. Note: For migrating a brownfield service, the service instance name that you enter here must match with the service that you want to migrate. The IRB interface units will be used exclusively by the service that you enter here for the customer specified in Customer.

Table 5: Fields on the Configure Port page (for configuring logical ports)
Field	Description
Interface Name*	Enter a name for the CE-facing interface as follows: Use the type-fpc/pic/port.logical format to enter the name with a logical unit. For example, et-0/0/0.0, ge-0/0/1.1. Use fpc/pic/port[:channel].logical format to enter the name for a channelized interface. For example, t3-0/0/0:1.0, t1-0/1/0:1.2. Use the management interface name of the device for management interfaces. For example, re0:mgmt-0.0, re1:mgmt-0.1. Use the aggregated Ethernet interface name for aggregated interfaces. For example, ae0.1, ae1.1, and ae2.3. Note: Starting from Routing Director Release 2.6.0, all logical units are supported. For ports in the ACX7204 devices, this field is auto-populated if you select a port to be configured in the Physical Ports tab.
Interface Profiles	Select one or more interface profiles to be applied to the interface from the drop-down list. The configurations in the device profiles are committed on the device in the order in which the profiles are added to the plan. Configurations present in both the default interface profile and the specific profiles that you enter here are committed on the device. However, for configurations that are present in both the specific interface profiles and the default interface profile, the values in the specific interface profiles override the configuration in the default interface profile. Alternatively, click the Add new interface profile to create a new interface profile and assign it to the port.

Table 6: Additional fields on the Configure Port page for Infrastructure Configuration use case (for configuring logical ports)
Field	Description
Description	Enter a description for the interface.
IPv4 Address/Subnet Mask	Enter the IPv4 address (in dotted decimal notation) with the subnet mask for the interface. For example, 10.10.10.10/24. If you have disabled automatic IP address assignment in the interface profiles assigned to the interface, you can assign the IPv4 address for the interface here.
IPv6 Address/Subnet Mask	Enter the IPv6 address with the subnet mask for the interface. For example, 2001:db8:4136:e378:8000:63bf:3fff:fdd2/48 If you have disabled automatic IP address assignment in the interface profiles assigned to the interface, you can assign the IPv6 address for the interface here.

Table 7: Additional fields on the Configure Port page for Service Orchestration use case (for configuring logical ports)
Field	Description
Access Parameters > CEs Click the add (+) icon above the CEs table. The CEs page appears.
Name*	Enter a reference name for the customer edge (CE)-facing interface.
Tag Type	Select one of the following VLAN tag types: dot1q If you select the dot1q tag type, enter the VLAN starting ID and VLAN size. qinq If you select qinq tag type, enter the VLAN starting ID and VLAN size for outer (service) VLAN and inner (customer) VLAN. untagged (default) An untagged interface receives and sends Ethernet frames without VLAN tags.
dot1q Tag Type	A Dot1q interface transmits and receives Ethernet frames with a single VLAN tag. When you select dot1q from the Tag Type drop-down, the VLANs section appears. Enter VLAN details by referring to the following list: Start—Enter the starting VLAN ID for the range of VLANs from the CE device that the PE interface supports. Enter a value in the range 1 through 4094. For example, if you enter 200 as the starting VLAN ID, the first VLAN supported by the PE interface has a VLAN ID of 200. Size—Enter the range of VLANs from the CE device that the PE interface supports. A size of 10 will configure 10 distinct VLAN IDs (200 through 2on the interface. Enter a value in the range 1 through 4094.
qinq Tag Type	A Q-in-Q interface transmits and receives frames with double VLAN tags. When you select qinq from the Tag Type drop-down, the Inner VLANs and Outer VLANs sections appear. Enter Inner VLANs and Outer VLANs details by referring to the following list: Enter Inner VLANs details: Start—Enter the starting VLAN ID for the range of inner VLANs. Enter a value in the range 1 through 4094. For example, if 200 is the starting inner VLAN ID, the first inner VLAN supported by PE device has a VLAN ID of 200. Size—Enter the range for inner VLANs. Enter a value in the range 1 through 4094. Enter Outer VLANs details: Start—Enter the starting VLAN ID for the range of outer VLANs. Enter a value in the range 1 through 4094. For example, if 200 is the starting outer VLAN ID, the first outer VLAN supported by PE device has a VLAN ID of 200. Size—Enter the range for outer VLANs. Enter a value in the range 1 through 4094.
Pinned Reservation Reserve the logical interfaces for specific services.
Brownfield	Enable this flag to reserve VLAN ID ranges for migrating brownfield services. The reserved VLAN ID ranges would be used by services that are configured to use pinned resources and have the Brownfield flag enabled. Disabling this flag while the reserved VLAN ID ranges are in use by a service will release the reservation. If the service is reprovisioned without disabling the Brownfield flag, the service will be disrupted due to missing resource allocation.
Customer	Select the customer whose service would use the defined VLAN ID ranges. The VLAN ID ranges will be used exclusively by services provisioned for the customer that you select here.
Instance	Enter the name of the service instance that can use the defined VLAN ID ranges. Note: For migrating a brownfield service, the service instance name that you enter here must match with the service that you want to migrate. The VLAN ID ranges will be used exclusively by the service that you enter here for the customer specified in Customer.
Access Parameters > Units Click Add above the Units table to add a range of Ethernet interface units. You must configure units if you want to migrate L3VPN Q-in-Q configuration to Routing Director.
Name*	Enter a name for the range of Ethernet interface unit. For example, eth-vpn-100 to eth-vpn-105.
Size*	Enter the number of interface units in the range. For example, a size of five will configure five distinct interface units on the Ethernet interface. Range: 0 through 4095.
Start*	Enter the first interface unit in the range. For example, assigning 100 as the Start value configures interface units from 100 up to 104 for a range size of five. Range: 0 through 4095.
Pinned Reservation Reserve the interface units for specific services.
Brownfield	Enable this flag to reserve the interface units in the defined range on the PE access interface for migrating brownfield services. The reserved interface units would be used by services that are configured to use pinned resources and have the Brownfield flag enabled. Disabling this flag while the reserved interface units are in use by a service will release the reservation. If the service is reprovisioned without disabling the Brownfield flag, the service will be disrupted due to missing resource allocation.
Customer	Select a customer whose services would use the defined interface units. The interface units will be used exclusively by services provisioned for the customer that you select here.
Instance	Enter the name of the service instance that can use the defined interface units. Note: For migrating a brownfield service, the service instance name that you enter here must match with the service that you want to migrate. The interface units will be used exclusively by the service that you enter here for the customer specified in Customer.

Table 8: Fields on the Configure Port page (for configuring aggregated Ethernet interfaces)
Field	Description
Name	Enter a name for the aggregated Ethernet interface. For example, ae1, ae3.
Description	Enter a description of the interface. For example, Link to PE router.
MTU	Enter the maximum transmission unit (MTU) for the aggregated Ethernet interface in bytes. For example, 1514 bytes. The MTU range depends on the device. Refer to the device documentation for the exact range. Range: 128 through 65,535
Profiles	Select one or more profiles to inherit configuration for the port.
Tagging	Select a tagging option for the aggregated Ethernet interface: Tagged – You can configure VLANs on the interface. Define the type of tagging for the port under Access Parameters. Untagged – You cannot configure VLAN on the interface.
Port Profiles	Select one or more port profiles to be assigned to the aggregated Ethernet interface. Click Add new port profile to configure a new port profile and assign it to the interface. For the same values defined in the port profile and the network implementation plan, the values defined in the plan take precedence over the values in the profile.
LAG Parameters Note: Link Aggregation Control Protocol (LACP) is not supported in this release.
Minimum Links	Enter the minimum number of links that can be configured on the aggregated Ethernet interface. For example, 10. Range: 1 through 64
Member Link
Name	Enter a name for the physical interfaces (Ethernet interfaces and channelized interfaces) that are a part of the aggregated Ethernet interface, For example, ge-1/0/0, ge-1/0/1. t3-0/0/0:1.2
Access Parameters > CEs Add the range of VLANs and the number of VLANs for service provisioning on the aggregated Ethernet interface. If you assign multiple VLANs, you can configure multiple services on the LAG. If you do not configure a VLAN, you can configure a single service on the LAG. To use an existing manually configured aggregated Ethernet interface on a device as an access interface for a service, define the interface in the network implementation plan by including VLAN in the interface's access parameters. Click the + (Add) icon above the CEs table.
Name*	Enter a reference name for the CE facing interface.
Tag Type	Select the type of VLAN tagging to be used on the aggregated Ethernet interface: Untagged dot1q qinq If you select dot1q tag type, enter the VLAN starting ID and VLAN size. If you select qinq tag type, enter the VLAN starting ID and VLAN size for outer (service) VLAN and inner (customer) VLAN.
VLANs
Start*	Enter the starting VLAN ID for the range of VLAN IDs that will be assigned to the interface. For example, a value of 10 indicates that the range of VLAN IDs assigned to the interface starts from 10. Range – 1 through 4094
Size*	Enter the size of the VLAN range that will be assigned to the interface. For example, a size of five with starting VLAN ID as 10 indicates that the VLAN IDs 10 through 14 are assigned to the interface. Range: 1 through 4094
q-in-q
Inner VLANs
Start*	Enter the range of inner VLAN IDs (customer VLAN IDs) that will be assigned to the interface. For example, a size of five with starting inner VLAN ID as 15, indicates that the inner VLAN IDs 15 through 19 are assigned to the interface. Range: 1 through 4094
Size*	Enter the starting outer VLAN ID (service VLAN ID) for the range of outer VLAN IDs that will be assigned to the interface. For example, a value of 25 indicates that the range of outer VLAN IDs assigned to this interface starts from 25. Range: 1 through 4094
Outer VLANs
Start*	Enter the starting outer VLAN ID (service VLAN ID) for the range of outer VLAN IDs that will be assigned to the interface. For example, a value of 25 indicates that the range of outer VLAN IDs assigned to this interface starts from 25. Range: 1 through 4094
Size*	Enter the range of outer VLAN IDs (service VLAN IDs) that will be assigned to the interface. For example, a size of five with starting outer VLAN ID as 25, indicates that the outer VLAN IDs 25 through 29 are assigned to the interface. Range: 1 through 4094
Pinned Reservation Reserve the VLAN IDs for specific services.
Brownfield	Enable this flag to reserve VLAN ID ranges for migrating brownfield services. The reserved VLAN ID ranges would be used by services that are configured to use pinned resources and have the Brownfield flag enabled. Disabling this flag while the reserved VLAN ID ranges are in use by a service will release the reservation. If the service is reprovisioned without disabling the Brownfield flag, the service will be disrupted due to missing resource allocation.
Customer	Select the customer whose service would use the defined VLAN ID ranges. The VLAN ID ranges will be used exclusively by services provisioned for the customer that you select here.
Instance	Enter the name of the service instance that can use the defined interface units. Note: For migrating a brownfield service, the service instance name that you enter here must match with the service that you want to migrate. The interface units will be used exclusively by the service that you enter here for the customer specified in Customer.
Access Parameters > Units Click Add above the Units table to add a range of Ethernet interface units. You must configure units if you want to migrate L3VPN Q-in-Q configuration to Routing Director.
Name*	Enter a name for the range of Ethernet interface unit. For example, eth-vpn-100 to eth-vpn-105.
Size*	Enter the number of interface units in the range. For example, a size of five will configure five distinct interface units on the Ethernet interface. Range: 0 through 4095.
Start*	Enter the first interface unit in the range. For example, assigning 100 as the Start value configures interface units from 100 up to 104 for a range size of five. Range: 0 through 4095.
Pinned Reservation Reserve the interface units for specific services.
Brownfield	Enable this flag to reserve the interface units in the defined range on the PE access interface for migrating brownfield services. The reserved interface units would be used by services that are configured to use pinned resources and have the Brownfield flag enabled. Disabling this flag while the reserved interface units are in use by a service will release the reservation. If the service is reprovisioned without disabling the Brownfield flag, the service will be disrupted due to missing resource allocation.
Customer	Select a customer whose services would use the defined interface units. The interface units will be used exclusively by services provisioned for the customer that you select here.
Instance	Enter the name of the service instance that can use the defined interface units. Note: For migrating a brownfield service, the service instance name that you enter here must match with the service that you want to migrate. The interface units will be used exclusively by the service that you enter here for the customer specified in Customer.
Access Parameters > Pinned Reservation Reserve the configured aggregated Ethernet interfaces for specific services.
Brownfield	Enable this flag to reserve the interface units in the defined range on the PE access interface for migrating brownfield services. The reserved interface units would be used by services that are configured to use pinned resources and have the Brownfield flag enabled. Disabling this flag while the reserved interface units are in use by a service will release the reservation. If the service is reprovisioned without disabling the Brownfield flag, the service will be disrupted due to missing resource allocation.
Customer	Select a customer whose services would use the defined interface units. The interface units will be used exclusively by services provisioned for the customer that you select here.
Instance	Enter the name of the service instance that can use the defined interface units. Note: For migrating a brownfield service, the service instance name that you enter here must match with the service that you want to migrate. The interface units will be used exclusively by the service that you enter here for the customer specified in Customer.

Links Tab

Use the Links tab to configure links between the devices. You can view a graphical representation of the links that you configure on the left-side of the tab.

To add a link between the devices included in the plan, click the + (Add) icon. Enter values by referring to Table 9.

Table 9: Fields on the Add Link Page
Field	Description
Link Name	Enter a name for the link. The name can contain alphanumeric characters and some special characters [hyphen (-), underscore (_), period (.), and colon (:)] and cannot exceed 64 characters. You must enter the link name if you want to configure links between multiple devices in the same subnet. For example, singapore-bogota-link1
Device A
Device*	Select a source device to originate the link. For example, Singapore-ACX-05.
Site	Displays the site where the device that originates the link is installed. For example, Singapore
Interface*	Select the interface on the source device from which the link originates. For example, et-0/0/12.0.
Connection Instructions	Enter instructions for the link. For example, the cables to be used to connect the device to the network or another device.
Device Z
Device	Select the destination device to terminate the link. You need not select a destination device if you want to connect to multiple devices from the same source device and interface. For example, Bogota-MX-204.
Site	Displays the site where the destination device that terminates the link is installed. For example, Bogota.
Interface	Select an interface on the destination device at which the link terminates. You need not select a destination interface if you want to connect to multiple devices from the same source device and interface. For example, xe-0/1/1.0
Connection Instructions	Enter instructions for the link. For example, the cables to be used to connect the device to the network or another device.

Add a Network Implementation Plan

Devices Tab

Links Tab

Related Documentation