Add an Interface Profile

An interface profile defines interface-specific configuration elements that are added to the device during onboarding, including the interface’s IP address, whether the interface will be used for management or Internet connectivity, or whether the interface will be running OSPF, IS-IS, LDP, or RSVP protocols.

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

Before you create interface profiles, ensure that you have configured the required network implementation plan to associate with the profile and the required IPv4 address resource pools. See Add a Network Implementation Plan for configuring a network implementation plan. Routing Director uses the resource pools to assign IP addresses and BGP cluster IDs to the devices.

To add an interface profile:

Navigate to Inventory > Devices > Device and Interface Profiles.
The Device and Interface Profiles page appears.
Click Add > Interface Profile to create an interface profile.
The Create Interface Profile page appears.
Enter values by referring to:
- Fields on General Tab
- Fields on the Routing Protocols Tab
  Note:
  By default, all the tabs and sections in the Create Interface Profile page 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. The Routing Protocols tab is visible only when the Infrastructure Configuration use case is selected in the network implementation plan associated with the interface profile.
Click Save to save the profile.
You can view the profile listed on the Device and Interface Profiles page.

Table 1: Fields on the General Tab of the Create Interface Profile Page
Field	Description
Upload JSON File	Click Browse to upload a pre-created interface profile in the JSON file format. The values in the pre-created interface profile are automatically populated in the Create Interface Profile page. Click the Download this form into JSON file link to download and save the profile in its current state (for example, to save the current configured values for later reference or for maintaining a record).
Profile Name*	Enter a name for the interface profile. The name can contain alphanumeric characters and some special characters [hyphen (-), underscore (_), period (.), and colon (:)] and cannot exceed 64 characters. For example, interface-profile-for-PE
Plan Name*	Select a network implementation plan you want the interface profile to be associated with. This field is hidden when you open the Create Interface Profile page from the network implementation plan.
Management	Click to enable or disable (default) the use of an interface as a management interface. If you enable this option, the interface to which you assign this profile is configured as a management interface.
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. When you use a configuration template to configure an interface using NETCONF, you can parametrize only the Interface name in the configuration template. The interface name should be parametrized as `{{ interface.name.split(".")[0] }}`. For example, the below configuration enables VLAN tagging on a physical port, assigns VLAN IDs to the subinterfaces on the physical port and configures IP addresses on the sub-interfaces on a device. {% for interface in interfaces %} set interfaces {{ interface.name.split(".")[0] }} vlan-tagging set interfaces {{ interface.name.split(".")[0] }} unit {{ interface.name.split(".")[1] }} vlan-id {{ interface.vlan_id }} set interfaces {{ interface.name.split(".")[0] }} unit {{ interface.name.split(".")[1] }} family inet address {{ interface.ipv4_address }} {% endfor %} See Add a Configuration Template for more details.
IPv4 Address	Click to enable or disable (default) the automatic assignment of the IPv4 address for an interface. If you enable this option, Routing Director assigns an IPv4 address to an interface from the resource pool configured in it. For automatic configuration of an IPv4 address, you must have uploaded IPv4 address resource pools to Routing Director. Otherwise, the IP address is not assigned to the device and the device onboarding fails. See Add Network Resource Pools. If you disable this option, you must assign an IPv4 address for the interface in the network implementation plan. See Add a Network Implementation Plan.
IPv6 Address	Click to enable or disable (default) the automatic assignment of the IPv6 address for an interface. If you enable this option, Routing Director assigns an IPv6 address to an interface from the resource pool configured in it. For automatic configuration of an IPv6 address, you must have uploaded IPv6 address resource pools to Routing Director. Otherwise, the IP address is not assigned to the device and the device onboarding fails. See Add Network Resource Pools. If you disable this option, you must assign an IPv6 address for the interface in the network implementation plan. See Add a Network Implementation Plan.
Active Assurance This section is visible only when the Active Assurance use case is selected in the network implementation plan associated with the profile.
Internet Connected	Click to enable or disable (default) connectivity tests (by Active Assurance) on an interface. If you enable the Internet Connected option and add the profile as the default interface profile in the network implementation plan, Routing Director initiates connectivity tests from all the ports you configure for all the devices in the network implementation plan. See Device Connectivity Data and Tests Results for more information. In the network implementation plan, you can also assign the interface profile to specific interfaces (ports).

Table 2: Fields on the Routing Protocols tab of the Create Interface Profile Page
Field	Description
OSPFv2 Click to enable or disable (default) OSPF configuration on an IPv4 interface. If you enable OSPF configuration, you configure the Area Address, Interface Type, Metric, and MTU for the interface.
Area Address*	Enter the OSPFv2 area address of the interface. For example, 0.0.0.1.
Interface Type	Select the interface type—auto, nbma, p2mp, and p2p.
Metric	Enter the OSPFv2 metric for the interface. The OSPFv2 protocol uses the cost metric to determine the best path to a destination. Range: 1 through 65,535 For example, 10
MTU	Enter the maximum transmission unit (MTU) over the OSPFv2 link configured on the interface. Range: 128 through 65,535 bytes For example 1514 bytes.
OSPFv3 Click to enable or disable (default) OSPF configuration on an IPv6 interface. If you enable OSPF configuration, you can configure the Area Address, Interface Type, Metric, and MTU for the interface.
Area Address*	Enter the OSPFv3 area address of the interface. For example, 0.0.0.1.
Interface Type	Select the interface type—auto, nbma, p2mp, and p2p.
Metric	Enter the OSPFv3 metric for the interface. The OSPFv3 protocol uses the cost metric to determine the best path to a destination. Range: 1 through 65,535 For example: 11.
MTU	Enter the MTU over the OSPFv3 link configured on the interface. Range: 128 through 65,535 bytes For example, 1514 bytes.
ISIS Click to enable or disable (default) IS-IS configuration on an interface. If you enable IS-IS, you can configure the IS-IS level, and metric for the interface.
Level	Select the IS-IS level: IS-IS Level 1—Routers exchange routing information within the same area IS-IS Level 2—Routers exchange routing information between different areas IS-IS Levels 1 and 2—Routers participate in both Level 1 and Level 2 routing
Metric	Enter the IS-IS metric for the interface. The IS-IS protocol uses the cost metric to determine the best path to a destination. Range: 1 through 16,777,215
LDP Click to enable or disable (default) LDP configuration on an interface. If you enable LDP, you can enable or disable LDP synchronization for an interface.
LDP Synchronization	Click to enable or disable (default) synchronizing LDP with the underlying IS-IS or OSPF protocol to ensure that LSPs are fully established on an IGP path before forwarding traffic through the LSPs. If LDP is not synchronized with the underlying IS-IS or OSPF protocol, packets might be dropped.
RSVP Click to enable or disable (default) RSVP configuration on an interface. If you enable RSVP, you can configure link protection for the interface. You must configure this option if you enable traffic engineering (TE) in the device profile that you applied to a device and apply this profile on an interface on the same device.
Link Protection	Click to enable or disable (default) link protection for a tunnel. You must enable link protection if you configure tunnels in the device profile.

Add an Interface Profile

Related Documentation