Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

header-navigation
keyboard_arrow_up
close
keyboard_arrow_left
Juniper Paragon Automation User Guide
Table of Contents Expand all
list Table of Contents
file_download PDF
{ "lLangCode": "en", "lName": "English", "lCountryCode": "us", "transcode": "en_US" }
English
keyboard_arrow_right

Add Network Resource Pools and Profiles (Day -2 Activities)

date_range 18-Jun-24

Before a network architect plans to add devices, they must add the following to Paragon Automation.

  1. Network resource pools to automatically assign IPv4 addresses, loopback addresses, and BGP cluster IDs. See Add Network Resource Pools.

  2. Device profiles to define device-level configurations such as loopback addresses, BGP groups, PCEP configuration, and so on.

    A device profile is created based on the role of a device in the network. For example, a device might be a provider edge (PE) device or a metro router. For the PE device, you can configure BGP, IS-IS, and add tunnels in your device profile, whereas for the metro router, you can configure only BGP and IS-IS protocols.

    See Add a Device Profile.

  3. Interface profiles to define the routing protocol configurations (OSPF, IS-IS, RSVP, and LDP) on the device. See Add an Interface Profile.

    An interface profile is created based on the role of the interface, for example core-facing or customer-facing.

What's Next

A network planner uses the device and interface profiles in a network implementation plan to define the device configurations. The network planner can use the profiles in the plan as per their specific needs, that is, apply the profiles to all the devices and ports or to specific devices and ports.

To add the network implementation plan. See Add a Network Implementation Plan.

footer-navigation