Add a Network Implementation Plan
You must be a user with the Network Admin or Super User role to add a network implementation plan.
After you create a network implementation plan, the devices included in the plan can be installed and onboarded to Routing Director.
| 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. If you are editing a plan, the name is already populated and cannot be edited. For example: plan-for-pe. |
| 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 |
Add all devices that you want to configure while the device is onboarded to Routing Director. The plan can also be used to manage the configuration of the devices after the devices are onboarded. You can also edit and delete the devices added to the plan from here. To add devices:
Note:
You can add a device to only one network implementation plan. |
| Links |
Add links between the devices added to the plan. Click the Add (+) to add links to other devices. The Add Link page appears from where you can configure the links. You can also edit and delete the links configured between devices included in the plan from here. See Table 4. |
| Summary |
Displays a summary of the onboarding plan. Click the Edit link to edit the general information or the links added to the plan. |
| Field | Description |
|---|---|
| General | |
| 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.
|
| 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. |
| 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. |
| 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 |
| 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. |
| Installation Duration |
Enter the time duration in minutes that the field technician can take to install the device, add pluggables, and connect cables. Routing Director checks the health of the device as soon as it pushes the configurations on the device. However, If the device installation is not complete by then, Routing Director notifies the device as unhealthy and executes the next task. For example, 30 minutes. To prevent reporting the device as unhealthy before installation is complete, Routing Director retries the device health checks every minute. The device health is checked until the device is detected as healthy or for the duration that you enter here, whichever is earlier. Default: 20 minutes Range: 0 through 20 |
| Instructions |
Enter instructions or any additional information that you want to provide to a field technician who is onboarding the device. The field technician can view the instructions that you enter here. |
|
Placement Resources Enable or disable (default) allocating resources for provisioning services on the device. |
|
|
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. |
|
IRBs Enable or disable (default) integrated routing and bridging (IRB) interfaces on a PE device. |
|
|
Start* |
Enter the starting IRB for the range of IRB IDs to which the PE interface connects. Enter a value in the range 1 through 65535. For example, if 200 is the starting VLAN ID, the first VLAN supported by the PE interface has a VLAN ID of 200. |
|
Size* |
Enter the number or range of IRB IDs available for a PE device. You can define a range using a starting ID and the number of IRBs required. Enter a value in the range 1 through 65535. |
| Physical Ports |
Displays the device's chassis view. You can perform the following tasks from here:
|
|
Configure Port |
|
| Interface Name* |
Enter a name for the interface as follows:
Note: Unit 0 is the only logical unit
supported for an interface.
For ports in the ACX7204 devices, this field is auto-populated if you select a port to be configured in the Physical Ports tab. |
| 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. |
| 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. |
| Pluggable |
Enter the type of pluggable to use in the port; for example, QOD-400G-FR4. A field technician can view the information that you enter here during device onboarding. |
| Cabling Instructions |
Enter instructions to connect cables to the interfaces. A field technician can view and use this information that you enter here to connect cables to interfaces during device onboarding. We recommend that you use specific instructions that are known to the field technician, such as a reference number of the cable. |
|
Access Parameters Click the add (+) icon above the Access Parameters table. The Add Access Parameter page appears. |
|
|
Name* |
Enter a reference name for the CE facing interface. |
|
Tag Type |
Select dot1q, qinq, or untagged as the VLAN tag from the Tag Type drop-down list. The default tag type is untagged. |
|
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:
|
|
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:
Enter Outer VLANs details:
|
|
untagged Tag Type |
Select untagged tag type to assign no VLANs to the interface. An untagged interface receives and sends Ethernet frames without VLAN tags. |
|
Chassis |
|
| PSMs |
Enter the number of power supply modules (PSMs) in the device. This information is used for collecting analytics and health data from the PSMs. For example, 2. |
| Fans |
Enter the number of fans in the device. This information is used for collecting analytics and health data from the fans. For example, 6 |
| Linecards |
Enter the number of line cards in the device. This information is used for collecting analytics and health data from the line cards. |
| Pluggables |
Enter the number of pluggables in the device. This information is used for collecting analytics and health data from the pluggables. |
| 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 |
|
Tagging |
Select a tagging option for the aggregated Ethernet 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 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. |
|
|
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:
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 |
| 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. |