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.

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 8. 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.
Note:
- If placement resources (IP addresses, autonomous system numbers, and so on) 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.
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.
Click Publish to push network wide configurations based on labels (for example, for devices with same labels to form BGP peers).

When multiple devices are added to a plan, one device may fail onboarding due to a commit error caused by conflicting configurations. Republishing the plan can help prevent these subsequent onboarding failures.

After you create a network implementation plan, the devices included in the plan can be onboarded 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

On the Devices tab, you can add devices to the network implementation plan and configure the general and port properties. Under Devices tab > General, configure the general device properties. Under the Physical Port section, you can:

View the list of all the devices in the plan.
Add devices to the network implementation plan and configure the general and port properties.

To add a device:
1. You can add a device in one of the following two ways:
  - If you have devices in inventory that are not added to a network implementation plan, click the Import Devices button.
    
    On the Import Devices page that appears, select the devices that you want to add to the plan and click Import.
    
    The devices are added to the plan.
    
    To configure the general and physical port properties, select the device and click the Pen (Edit) icon.
    
    The Edit Device page appears.
  - Click the + (Add) icon above the device list.
    
    The Add Devices page appears.
2. On the General section:
  - Configure the general properties 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 to Table 4
3. Click Next to view the Physical Ports tab.
4. In the Physical Ports tab, add and configure physical and logical interfaces on the device.
  
  Some devices such as ACX7024 have their physical interfaces listed by default. For devices that do not have the physical interfaces listed, add physical interfaces manually and configure the physical and logical interfaces.
  
  To add and configure physical interfaces:
  1. 1. Select Add > Physical Interfaces.
      
      The Configure Port page appears.
    2. Configure the ports by referring to Table 5.
    3. Repeat steps a and b to add as many ports as you want to configure.
      
      The ports you configure are listed in the Interfaces table.
      
      To view all configured port parameters, such as LAG Parameters and MTU, click show or hide columns in the table using the vertical ellipsis menu.
    To add logical interfaces within a physical interface:
    1. Select the physical port and click Add > Logical Interfaces.
      
      The Configure Port page appears.
    2. Configure the logical interface by referring to Table 6.
      
      If Infrastructure is selected as a use case in the plan, configure infrastructure parameters by referring to Table 7.
    3. Repeat steps a and b to add as many logical interfaces as you want to configure.
      
      The interfaces you configure are listed under the Interfaces table. The list of logical interfaces within a physical interface can be collapsed and expanded in the table.
  2. 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.
5. Repeat steps 1 through 4 to add as many devices as you want.
6. Click Next to go to the Links tab.

You can 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.

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. 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

Note: The infrastructure attributes create a new configuration on the device.

Table 4: Additional fields on the General tab for Service Orchestration use case
Field	Description
Discovered Parameters Displays service orchestration-related parameters such as loopback addresses configured on devices that are automatically discovered. You can modify the parameter values.
IPv4 Loopback	The IPv4 loopback address configured on the device that is discovered by Routing Director. You can modify the loopback address. This loopback address is used to generate the Type 1 route distinguisher needed by a service configured on the device.
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.
Logical Tunnel Configure logical tunnel interfaces for service stitching.
Logical Tunnel	Click + (Add) icon above the table to configure the logical tunnel interfaces and subinterface units.
Name	Enter a name for the logical tunnel interface. For example, lt-0/0/0 or lt-0/0/0:12.
Ranges Click + (Add) icon to add subinterface units for the LT interface.
Name	Enter a unique name for the range of LT subinterfaces. For example, Range-1.
Size	Enter the number of consecutive subinterfaces allocated in this range. For example, a size of 10 will configure 10 distinct subinterfaces (for example, 200 through 219) on the interface. Range: 1 through 16,385
Start	Enter the starting subinterface number of the defined range. For example, if you specify 200 as the starting value for subinterfaces on lt-0/0/1, the first logical subinterface created will be lt-0/0/1.200. Range: 0 through 16,385.
Pinned Reservation Reserve the defined logical tunnel subinterfaces for sepecific services.
Brownfield	Enable this flag to reserve the defined LT interface units for migrating brownfield services. The LT 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 the customer whose service would use the LT interface units in the defined range. The LT 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 LT interface units. Note: 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 LT 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 physical interface)
Field	Description
Name	Enter a name for the physical interface: Use the type-fpc/pic/port format to enter the name. For example, et-0/0/0, ge-0/0/1. Use fpc/pic/port[:channel].logical format to enter the name for a channelized interface. For example, t3-0/0/0:1, t1-0/1/0:1. Use the management interface name of the device for management interfaces. For example, re0:mgmt-0, re1:mgmt-0. Use the aggregated Ethernet interface name for aggregated interfaces. For example, ae0, ae1, and ae2. If you enter an aggregated Ethernet interface name, the Lag Parameters section becomes available.
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.
Port Profiles	Select one or more port profiles for aggregation. If you do not have a port profile, click Add Port Profile to create a new port profile.
Infrastructure Configuration
Description	Enter a description for the port.
MTU	Enter the maximum transmission unit (MTU) for the port in bytes. For example, 1514 bytes. The MTU range depends on the device model. Refer to the respective device documentation for the exact range. Range: 128 through 65,535
Tagging	Select a tagging option for the Ethernet interface: Tagged—You can configure VLANs on the interface. If you select Tagged, you must define the type of tagging for the port under Access Parameters or specify the VLAN ID for the core interface in the physical port's logical interface. Untagged—You cannot configure VLAN on the interface.
Lag Parameters This section appears when you enter an aggregated Ethernet interface in the physical interface Name field on the Configure Port page.
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 Links Click + icon in the Member Link table to open the Member Link page and select a physical interface.
Name	Select a physical interface. All the physical interfaces of the device are listed here.
Service Orchestration
Access Parameters	Click to enable or disable configuring access parameters on the physical interface. By default, this option is disabled. Enable this option to configure the access parameters on the port.
Access Interface (or CE Reference) Click the add (+) icon above the Access Interface (or CE reference) table. The Access Interface (or CE reference) page appears.
Access Interface (or CE reference)*	Enter the CE reference connecting to the customer edge (CE) device. For example, CE1, CE2
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. Note: You must ensure that the VLAN IDs and sizes you set for Dot1q and Q-in-Q fall within the range supported by the defined access interface units.
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 access interface for specific services.
Brownfield	Enable this flag to reserve the access interface for migrating brownfield services. The reserved access interface will be used by services that are configured to use pinned resources and have the Brownfield flag enabled. Disabling this flag while the reserved access interface is 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 access interface The access interface will be used exclusively by services provisioned for the customer that you select here.
Service	Enter the name of the service instance that can use the defined access interface. 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.
Units Configure units that a service can allocate to the interface during resource allocation when provisioning a service. Click the Add icon above the Units table to add a range of 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 interface units. 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. 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.
Pinned Reservation Reserve the physical interface for specific services.
Brownfield	Enable this flag to reserve the physical interface for migrating brownfield services. The reserved physical interface 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 physical interface. The physical interface 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 physical interface. 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 6: Fields on the Configure Port page (for configuring logical interfaces)
Field	Description
Unit	Enter the logical unit number of the interface. For example ge-0/0/0.100, where the logical unit number is 100.
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 7: 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.
VLAN ID	Enter the VLAN ID of the logical interface. Range: 1 through 4094.

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 8.

Table 8: 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