Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
 

Device and Interface Profiles Overview

Onboarding profiles comprise device and interface profiles. A device onboarding profile defines the following parameters associated with a device:

  • IP address

  • Protocols—BGP, IS-IS, and OSPF

  • Traffic engineering (TE)

  • Segment routing (SR)

  • Neighboring devices, DNS servers, Internet endpoints, and cloud provider endpoints for checking connectivity.

A network architect creates a device profile based on the role of the device in the network. For example, a device might be a provider edge (PE) device or a metro router. For the PE router, you can configure BGP, IS-IS, and add tunnels in your device profile, whereas for a metro router, you can configure only the BGP and IS-IS protocols. See Add a Device Profile for information about adding a device profile.

An interface profile defines the configuration for OSPF, IS-IS, LDP, and RSVP protocols for an interface. You create an interface profile based on the role of an interface. For example, core-facing or customer-facing. See Add an Interface Profile for information about adding an interface profile.

You assign the profiles to a network implementation plan. In the network implementation plan, you can specify the profile that must be applied to all the devices or ports or specific devices or ports. Paragon Automation commits the configurations defined in the profiles and in the plan during device onboarding so that the device is ready for service soon after you onboard the device. You can also use the profiles to modify the configurations after a device is onboarded and in service. See Network Implementation Plan Overview for details about the network implementation plan.