Add a Device Profile

A device profile defines global configuration elements that are added to the device during onboarding. The configuration elements include hostname, IP address of the loopback, router ID, AS number, routing protocols, segment routing, bandwidth, MAC addresses, end points for testing connectivity, traffic engineering, and routing protocol analytics.

We recommend that you create some device profiles with configurations that can be applied to all the devices in a network implementation plan and some profiles with device-specific configurations.

Before you create device profiles, ensure that you have:

Configured the required network resource pools (for example, IP addresses and BGP cluster IDs). If you configure Routing Director to assign values for network resources (loopback addresses, IPv4 addresses, BGP cluster IDs, and so on), Routing Director uses the network resource pools to assign the values automatically. See Prepare for Device Onboarding (Day -2 and Day -1 Activities) for details.
Created the required network implementation plan to associate with the profile. See Add a Network Implementation Plan for creating a network implementation plan.

To add a device profile to Routing Director:

Navigate to Inventory > Devices > Device and Interface Profiles.

The Device and Interface Profiles page appears.
Click Add > Device Profile to create a device profile.

The Create Device Profile page appears.
Enter values by referring to:
- General Tab for configuring fields on the General tab.
- Routing Protocols for configuring fields on the Routing Protocols tab.
- Active Assurance for configuring fields on the Active Assurance tab.
- Placement Resources for configuring fields on the Placement Resources tab.
- Analytics for configuring fields on the Analytics tab.
Fields marked with * are mandatory.

Note:
By default, all the tabs and sections in the Create Device Profile wizard are visible. However, after a network implementation plan Is assigned to the profile, only the tabs and sections that are relevant to the use cases selected in the network implementation plan are visible. For example, if the Infrastructure Configuration is the only use-case selected in the network implementation plan, the General and Routing Protocols tabs would be visible on the Create Device Profile page. Similarly, if Active Assurance is the only use-case selected, the General and Active Assurance tabs would be visible.
Click Save to save the profile.

You can view the profile listed on the Device and Interface Profiles page.

General Tab
Routing Protocols
Active Assurance
Placement Resources
Analytics

General Tab

Table lists the fields on the General tab of the Create Device Profile page.

Table 1: Fields on the General tab.
Field	Description
Upload JSON File	Click Browse to upload a pre-created device profile in the JSON file format. The values in the pre-created device profile are automatically populated in the Create Device Profile page. Click the Download this form into JSON file link to download and to 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).
Profile Name*	Enter a name for the device profile. The profile name can contain alphanumeric characters and some special characters [hyphen (-), underscore (_), period (.), and colon (:)] For example, PE-Device-Profile.
Plan Name*	Select a network implementation plan you want the device profile to be associated with. This field is hidden when you open the Create Device Profile page from the network implementation plan.
Device Labels	Select one or more device labels from the drop-down list. The labels that you select here are associated with the devices to which you assign this profile. You can use the labels to refer to the device in various contexts. For example, if you assign the label PE for provider edge devices, you can use the label to filter all PE devices present in your network. You can also click the + Add new label link to add a new label to the profile, in the Add New Label page. The name of the label can contain alphanumeric characters and some special characters [hyphen (-) and period (.)] and cannot exceed 64 characters. See Add Labels. For example, PE.
Infrastructure Configuration This section is visible only when the Infrastructure Configuration use case is selected in the network implementation plan associated with the profile.
Configuration Templates	Select one or more configuration templates that you want to include in the profile. Use configuration templates to configure parameters that you cannot define in the profile or plan. All the configuration templates present in the organization are listed here. Note: The configurations in the configuration template can be applied only during onboarding. Any changes to the configurations made after the device is onboarded are not applied to the device.
Software Image	Select the software image to be installed on the device. During device onboarding, Routing Director checks whether the software version installed on the device matches the version you enter here. If the software version does not match, the software version that you specify here is installed on the device. You can view the images that are uploaded to Routing Director here.
Autonomous System	Enter the ID or number of the AS to which you want to assign the device. For example, 64500 Range: 1 through 4,199,999,999
Trust	Click to enable (default) or disable Routing Director to run compliance scans on the device for assessing the integrity and potential vulnerabilities on the device and to calculate compliance score for the device. The compliance score of a device indicates compliance of the device with the rules defined in the Center for Internet Security (CIS) benchmarks.
Router ID	Click to enable or disable (default) automatic router ID configuration on a device during device onboarding. If you enable automatic router ID configuration, the IPv4 loopback address of the device is used as the router ID.
IPv4 Loopback Address	Click to enable or disable (default) automatic IPv4 loopback address configuration on the device. If you enable automatic IPv4 loopback address configuration, Routing Director assigns the IPv4 loopback address automatically to the device's interfaces from the IPv4 address resource pool. For automatic configuration of IPv4 loopback address, you must have IPv4 loopback address resource pools uploaded to Routing Director. Otherwise, the IPv4 loopback address is not assigned to the device's interfaces and device onboarding fails. See Add Network Resource Pools for adding information about resources pools. If you disable this option, you can configure the loopback address when you add devices to a network implementation plan.
IPv6 Loopback Address	Click to enable or disable (default) automatic IPv6 loopback address configuration on the device. If you enable automatic IPv6 loopback address configuration, Routing Director assigns the IPv6 loopback address automatically to the device's interfaces from the IPv6 address resource pool. For automatic configuration of IPv6 loopback address, you must have IPv6 loopback address resource pools uploaded to Routing Director. Otherwise, the IPv6 loopback address is not assigned to the device's interfaces and device onboarding fails. See Add Network Resource Pools for adding information about resources pools. If you disable this option, you can configure the loopback address when you add devices to a network implementation plan.
Per Flow Load Balancing	Click to enable (default) or disable load-balancing traffic over two or more paths when equal-cost multiple paths exist to a destination. For information about configuring per-flow load balancing, see Configuring per-flow load balancing.
IPv6 tunneling	Click to enable or disable (default) MPLS LSPs to be used for IPv6 traffic. When you enable this option, LDP and RSVP routes in inet.3 routing table are converted IPv6 addresses (mapped to IPv4 addresses) and stored in inet6.3 routing table. This option is available only with infrastructure service design version 0.13.20 or later. See Update Service Designs and Instances After Routing Director Upgrade to upgrade your infrastructure service design version.
Observability This section is visible only when the Observability use case is selected in the network implementation plan associated with the profile.
Trust	Click to enable (default) or disable Routing Director to run compliance scans on the device for assessing the integrity and potential vulnerabilities on the device and to calculate compliance score for the device. The compliance score of a device indicates compliance of the device with the rules defined in the Center for Internet Security (CIS) benchmarks.
Infrastructure Configuration This section is visible only when the Infrastructure Configuration use case is selected in the network implementation plan associated with the profile.
ISO Network Address	Click to enable or disable (default) IS-IS protocol configuration on the device. If you enable ISO Network Address, configure the area ID and system ID.
Area ID*	Enter the area ID to be assigned to the device for IS-IS protocol configuration. This field is mandatory if you enable ISO network address. Range: 01 through 99
System ID	Click to enable (default) or disable auto-generation of a system ID for IS-IS protocol configuration. If you choose to auto-generate the system ID, the value assigned is usually the host part of the device’s IP4 or IPv6 loopback address in the binary-coded decimal (BCD) format. For automatic configuration of System ID, you must have IPv4 loopback address resource pools uploaded to Routing Director. Otherwise, the System ID is not assigned to the device and device onboarding fails. See Add Network Resource Pools for information about adding resources pools. If you explicitly specify the system ID, we recommend that you use the IPv4 loopback address represented in the BCD format. For example, if the loopback address is 192.168.1.77, the system ID should be 1921.6800.1077.

Routing Protocols

Table lists the fields on the Routing Protocols tab.

This tab is visible only when the Infrastructure Configuration use case is selected in the network implementation plan associated with the profile. Use this tab to configure routing protocols on a device when the device is onboarded to Routing Director.

Table 2: Fields on the Routing Protocols tab of the Create Device Profile page.
Field	Description
BGP	Click to enable or disable (default) BGP configuration on the device. If you enable BGP configuration, add an internal or external BGP peer group for the device. For information about the configurable fields to add a BGP group, See Table 3. You can also edit and delete BGP peer groups of a device from here.
PCEP	Click to enable or disable (default) path computation element protocol (PCEP) configuration on a device. If you enable PCEP, configure the IPv4 path computation element (PCE) address in your network.
PCE Address	IPv4 or IPv6 address of the PCE in your network.
Traffic Engineering	Click to enable or disable (default) traffic engineering (TE) configuration on your device. If you enable TE, add tunnels [label-switched paths (LSPs)] for TE. See Table 4. You can also edit and delete tunnels from here. Note: If you configure tunnels, you must configure RSVP in an interface profile and apply the interface profile to a device to which you apply this device profile.
Segment Routing	Click to enable or disable (default) segment routing configuration on a device. If you enable segment routing, configure start label and index range for the OSPF and IS-IS protocols, and the node segment identifier (SID) (referred to as IPv4 index) for a device.
OSPF > Start Label*	Click to enable or disable (default) OSPF for segment routing. If you enable OSPF, configure the start label and index range of OSPF, Start Label—Enter a start label for the segment routing label block. This label is advertised using the OSPF protocol. Range: 16 through 1,048,575 Index Range—Enter the range of label values that you want to use as the SID for a device. For example, 40. Range: 32 through 1,048,559
ISIS > Start Label*	Click to enable or disable (default) OSPF for segment routing. If you enable OSPF, configure the start label and index range of OSPF, Start Label—Enter a start label for the segment routing label block. This label is advertised using the IS-IS protocol. For example 40. Range: 16 through 1,048,575 Index Range—Enter the range of label values that you want to use as SID for a device. For example, 50. Range: 32 through 1,048,559
IPv4 Index	Click to enable or disable (default) the automatic configuration of the IPv4 node SID for segment routing. For automatic configuration of IPv4 index, you must have the segment identifier resource pools uploaded to Routing Director. Otherwise, the IPv4 index is not assigned to the device and the device onboarding process fails. See Add Network Resource Pools for information about adding resources pools.
IPv6 Index	Click to enable or disable (default) the automatic configuration of the IPv6 node SID for segment routing. For automatic configuration of IPv6 index, you must have the segment identifier resource pools uploaded to Routing Director. Otherwise, the IPv6 index is not assigned to the device and the device onboarding process fails. See Add Network Resource Pools for information about adding resources pools.
ISIS
IPv4	Click to enable (default) or disable IPv4 routing by using IS-IS protocol.
IPv6	Click to enable (default) or disable IPv6 routing by using IS-IS protocol.
LDP
IPv4	Click to enable (default) or disable IPv4 routing by using LDP protocol.
IPv6	Click to enable (default) or disable IPv6 routing by using LDP protocol.

Table 3: Fields on the Add BGP Group Page
Field	Description
Name*	Enter a name for the BGP peer group of the device. The name can contain alphanumeric characters and some special characters [hyphen (-), underscore (_), period (.), and colon (:)] and cannot exceed 64 characters. For example, iBGP-Mesh.
Type	Select a type of BGP peer group for the device: Internal (IBGP) Peer External (EBGP) Peer
Peer AS	Enter the AS number of the device's BGP peer groups. The value can range from 1 to 4,199,999,999. For example, 64510.
BGP Link State
Originator	Click to enable or disable (default) the BGP peer group as the source for BGP-LS information. If you enable this option, the devices in this group provide the BGP link state information to Routing Director.
Neighbors > IPv4
Device Labels	Select one or more labels of devices that belong to the BGP peer group. All devices that share the label you enter here become part of the peer group. Note: For specifying a single device as a BGP neighbor, provide either the device label or IPv4 address. For specifying multiple devices as a BGP neighbor, use a combination of both device labels and IPv4 and IPv6 addresses. We recommend that you use labels for specifying BGP neighbors as one label can represent multiple devices.
Addresses	Enter the IPv4 addresses (in dotted decimal notation) of the devices that you want to add in the BGP peer group. Press Enter to add another IP address. For example, 10.2.3.4. 10.2.5.10. Note: For specifying a single device as a BGP neighbor, you can provide either the device label or IPv4 address. For specifying multiple devices as a BGP neighbor, you can use a combination of both device labels and IPv4 addresses.
Address Family	Select one or more IP address families from the drop-down list that a device can support for BGP sessions with peers.
Neighbors > IPv6
Device Labels	Select one or more labels of devices that belong to the BGP peer group. All devices that share the label you enter here become part of the peer group. Note: For specifying a single device as a BGP neighbor, provide either the device label or IPv4 address. For specifying multiple devices as a BGP neighbor, use a combination of both device labels and IPv6 addresses. We recommend that you use labels for specifying BGP neighbors as one label can represent multiple devices.
Addresses	Enter the IPv6 addresses (in dotted decimal notation) of the devices that you want to add in the BGP peer group. Press enter to add another IP address. For example, 2001:db8::ff00:42:8329 Note: For specifying a single device as a BGP neighbor, you can provide either the device label or IPv6 address. For specifying multiple devices as a BGP neighbor, you can use a combination of both device labels and IPv6 addresses.
Address Family	Select one or more IP address families from the drop-down list that a device can support for BGP sessions with peers.
Route Reflector
Cluster Name	Select one or more BGP cluster IDs to which you want to assign the devices from the BGP peer group. Click the Manage Clusters link to add, modify, or delete BGP clusters. To add a BGP cluster: Click Manage Clusters. The BGP Route Reflector Clusters page appears. Click the add (+) icon. The Name and Cluster Identifier fields are enabled. Enter a name for the BGP cluster in the Name field. The name can contain alphanumeric characters and some special characters [hyphen (-), underscore (_), period (.), and colon (:)] and cannot exceed 64 characters. Enter an IP address for the BGP cluster in the Cluster Identifier field. Do not enter a value for the cluster ID if you want Routing Director to automatically assign the cluster ID. For example, 10.2.0.0. For automatic configuration of cluster IDs, you must have BGP cluster ID resource pools uploaded to Routing Director. Otherwise, the cluster IDs are not assigned to the BGP clusters, and the device onboarding fails.

Table 4: Fields on the Add Tunnel Page
Field	Description
Name*	Enter a name for the tunnel. The name can contain alphanumeric characters and some special characters [hyphen (-), underscore (_), period (.), and colon (:)] and cannot exceed 64 characters. For example, mpls-full-mesh.
Protection	Select the type of protection you want to configure for the tunnel: none: The tunnel does not have any protection. link: The links in the tunnel are protected. node-link: Both the devices and the links in the tunnel are protected. detour: The tunnel is protected by a secondary tunnel.
Destination
Device Labels	Select the labels of the devices where you want the tunnel to end. Note: You need to provide either the device label or IPv4 address for the tunnel destination. We recommend that you use labels to specify devices for tunnel destination.
Addresses	Enter the IPv4 addresses or IPv6 addresses of the devices where you want the tunnel to end. Press Enter to add another IP address. Note: You need to provide either the device label or IPv4 or IPv6 address for the tunnel destination. For example, 10.2.3.40. 10.2.5.10
Bandwidth
Bandwidth	Click to enable (default) or disable the automatic configuration (static configuration) of the tunnel bandwidth. If you disable auto configuration (static), specify the tunnel bandwidth in Kbps, Mbps, or Gbps. For example, 5 Mbps.

Active Assurance

Table 5 lists the fields on the Active Assurance tab of the Create Device Profile page. Use this tab to configure Active Assurance tests on a device when the device is onboarded to Routing Director.

Table 5: Fields on the Active Assurance tab.
Field	Description
Enable Active Assurance	Click to enable or disable (default) active assurance-related test configurations. If you enable this option, Active Assurance-related test configurations are generated and tests are executed based on the details present in the network implementation plan associated with this profile.
Wait for Test Results	Click to enable or disable (default) the onboarding workflow to wait for Active Assurance test results before proceeding with the steps in the onboarding workflow. Enable—The onboarding workflow pauses for Active Assurance test results to be available and records them in the service order before proceeding. If the Active Assurance test does not create any monitors, it records zero monitors as the result. Similarly, if the test generates no results, Active Assurance marks the test as failed. Disable—The onboarding workflow configures Active Assurance tests, but skips the tasks that wait, fetch, and record the test results.
Neighbour Ping Test Parameters	Click to enable or disable (default) the test agents installed on the device from performing connectivity tests to the device's neighbors.
Neighbour Ping Duration	Enter the number of seconds for which the device can ping its neighbors. Range: 30 through 3600 seconds
Edge Devices	Click to enable or disable (default) the test agents installed on the device to run connectivity tests to the edge devices in the network. If you enable running connectivity tests to the edge devices, configure the labels and IPv4 addresses of the edge devices.
Device Labels	Select the device labels for edge devices. Test agents run connectivity tests to all devices that share the device label. For example, PE.
Addresses	Enter one or more IPv4 addresses of edge devices to which test agents on the device run connectivity tests. For example 192.0.2.10 and 203.0.113.100.
Internet Endpoints	Click to enable or disable (default) the test agents that are installed on devices to run connectivity tests to the Internet endpoints such as Web servers and DNS servers in the network. If you enable running connectivity tests to the Internet endpoints, you must configure the endpoints for the connectivity test.
DNS Server	Enter the IPv4 address of the internal or external DNS server to which the test agent runs a ping connectivity test. For example, 8.8.8.8.
Internet Endpoints	Click + to add Internet Endpoints for connectivity checks. Configure the following: Name—Enter the name of the Internet endpoint server. For example, Apache. URL—Enter the URL of the Internet endpoint server in host[:port]/[path] format. For example, `https://httpd.apache.org`. Click the check mark to save the endpoints.
Cloud Providers	Click to enable or disable (default) the test agents installed on devices from running connectivity tests to hosts in the Cloud Provider's network. If you enable running connectivity tests to the cloud provider endpoints, you must configure the cloud provider endpoints.
Select cloud providers	Configure the parameters to check connectivity from a device to the cloud provider network. To configure connectivity tests to cloud provider endpoints: Select a cloud provider (Amazon Web Services [AWS], Microsoft Azure, or Google Cloud Platform) in the Cloud Providers list to which connectivity is to be tested. (Optional) Click Edit to change the default delay and delay variance threshold values for the selected cloud provider. You can edit the values as per your preference and click the check mark to save the edited values. Click Save. Routing Director runs connectivity checks to the configured cloud provider endpoints during device onboarding.

Placement Resources

This tab is visible when the service orchestration use case is enabled in the plan associated with the device profile.

Table shows the fields on the Placement Resources tab of the Create Device Profiles page. This tab is visible only when the Service Orchestration use case is selected in the Network Implementation plan associated with the profile. Use this tab to configure resources such as bandwidth, MAC addresses, route distinguishers, IRB interfaces and so on, during device onboarding so that the device is ready for service provisioning soon after onboarding.

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.

Table 6: Fields on the Placement Resources tab
Field	Description
Bandwidth*	Enter the bandwidth (in Mbps) to be used for service provisioning on the device. For example, 1000 Mbps.
MAC Address	Enter the maximum number of MAC addresses to be assigned to the device for service provisioning. For example, 10.
Routes	Enter the maximum number of routes to be assigned to the device for service provisioning. For example, 50.
Route Distinguisher Type 1 Click the Add (+) icon above the Route Distinguisher (RD) table to configure a range of Type 1 RDs during device onboarding. If you do not configure the range, Routing Director automatically configures the range.
Name*	Enter a name for the range of RDs being configured. For example, RD-CORP-BLR-VPN.
Size*	Enter the number of RDs to be defined within the range. For example, a size of 10 will configure 10 distinct RDs 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.1.1.1:20 up to 10.1.1.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 route targets. 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 route targets will be used exclusively by the service that you enter here for the customer specified in Customer.
IRBs > Migration Click Add to configure a range of IRB interfaces during device onboarding, for migrating brownfield services.
Name*	Enter a name for the range of IRB interface units to be 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 five distinct IRB interfaces on the device. Range: 0 through 65,535
Start*	Enter the starting number of the IRB interface unit in the defined range. For example, assigning 10 as the Start value configures IRB interfaces from irb.10 to irb.14, for a size of 5. 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 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 IRB interface units in the defined range. 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 the defined route targets. 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 route targets will be used exclusively by the service that you enter here for the customer specified in Customer.
Size*	Enter the number or range of IRB interface units to be configured on a device. For example, a size of 5 will configure 5 distinct IRB interfaces on the device. Range: 0 through 65,535
Start*	Enter the number of IRB interface units to be defined within the range. For example, assigning 10 as the Start value configures IRB interfaces from irb.10 to irb.14. Range: 0 through 65,535

Analytics

Table shows the fields on the Analytics tab of the Create Device Profile page to be configured. This tab is visible only when the Observability use case is selected in the network implementation plan associated with the profile. Use this tab to enable Routing Director to:

Collect telemetry data from data sources such as interfaces, tunnels, and so on,
Enable display of BGP and IGP-related metrics on Route Topology page (Observability > Routing > Route Topology), and
Collect routing, OS, and forwarding exceptions.

Table 7: Fields on the Analytics tab
Field	Description
Observability and Optimization This section is visible only when both Observability and Optimization use cases are selected in the network implementation plan associated with the profile.
Traffic-Engineering	Click to enable or disable (default) the collection of historical telemetry data for the elements (tunnels, interfaces, delay, and so on) that are configured for traffic data collection.
Observability This section is visible only when the Observability use case is selected in the network implementation plan associated with the profile.
Routing Observability > Junos Resiliency Interface	Enable or disable (default) Juniper Resiliency Interface to allow Routing Director to collect routing, OS, and forwarding exceptions from devices. Routing Director analyzes the collected exceptions to predict potential traffic blackholes and identify correlated events that may have caused the exceptions.
Routing Observability > Routing Protocol Analytics	Click to enable or disable (default) routing protocol analytics and data collection that you can apply to devices in the network implementation plan. Routing protocol analytics are disabled by default. You can use the Route Explorer dashboard and its features only after you have enabled Routing Protocol Analytics.
BGP State	Select the check box to enable the data collection and monitoring of all BGP peers. You can view BGP state and analytics on the Route Explorer dashboard. See About the Route Explorer Page.
BGP Ribs	Select the check box to enable the data collection and monitoring of all BGP-related routing information bases (RIBs). You can view a record of all BGP RIBs on the Route Explorer dashboard. See About the Route Explorer Page.
IGP State	Select the check box to enable the data collection and monitoring of all IGP peers. You can view IGP state and analytics on the Route Topology page (Observability > Routing > Route Topology). See About the Route Topology Page.
Link State Database	Select the check box to enable the data collection and monitoring of all IGP-related RIBs. You can view a record of all IGP RIBs on the Route Topology page (Observability > Routing > Route Topology). See About the Route Topology Page.