Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
ON THIS PAGE
 

Adopt a Device

You must be a user with Super User or Network Admin privileges to adopt or onboard a device (router, switch, or firewall).

Note:

You can only adopt routers in this release.

A Super User or Network Admin can adopt a device both new devices (greenfield) and devices that are already a part of the network (brownfield device), and manage the device by using Paragon Automation. When you adopt a device that is not associated with a network implementation plan, you (Super User or Network Admin) must manually update configurations by using configuration templates, apply licenses, and upgrade software. However, if you use a network implementation plan to onboard devices, you can make the changes to the network implementation plan and publish the changes for the changes to take effect on the devices included in the plan. You also obtain the granular metrics about the device’s health and performance by using the network implementation plan to onboard a device.

The status of a device that is already installed and connected to the network, but is not managed by the Paragon Automation appears as Disconnected on the Inventory page (Inventory > Devices > Network Inventory). When you adopt a device, the device connects with Paragon Automation and the status of the device changes to Connected, indicating that the device is managed by Paragon Automation.

You can adopt a device to Paragon Automation by using any of the following methods:

Before you adopt a device, ensure that:

  • The device can reach the gateway.

    Note:

    If a firewall exists between Paragon Automation and the device, configure the firewall to allow outbound access on TCP ports 443, 2200, 6800, and 32,767 from the management port of the device.

  • The device can connect to Paragon Automation.

Adopt a Device by using ZTP

Prerequisites:

  • A network implementation plan should be configured for the device.

  • The device should be zeroized or in its factory-default settings.

  • A TFTP server reachable from the device

  • A DHCP server reachable from the device, with the ability to respond to the device with the TFTP server and configuration file (script) name

Figure shows the workflow for adopting device by using ZTP.

Figure 1: Workflow for adopting a Device by using ZTP Workflow for adopting a Device by using ZTP

The steps for the workflow are as follows:

  1. Create an onboarding script (Python or SLAX) with the required SSH configuration by:

    • Connecting to Paragon Automation GUI and copying the onboarding configuration statements. To copy the onboarding configuration from the Paragon Automation GUI:

      1. Navigate to Inventory > Network Inventory.

      2. On the Routers tab, click Adopt Router.

      3. On the Router Adoption page, click Select Site to select the site where the device is installed.

        The outbound SSH configuration that is required for the device to establish a connection with Paragon Automation is displayed.

      4. Click the Copy to Clipboard link to copy the CLI commands under the Apply the following CLI commands to adopt a Juniper Device if meets the requirements section to clipboard.

    • Adding the SSH configuration statements to the onboarding script.

    See Sample Onboarding Script for Committing SSH Configuration on a Device for a sample of the onboarding script.

  2. Upload the onboarding script to the TFTP server.
  3. Configure the DHCP server with the onboarding script filename and path to the onboarding script in the TFTP server.
  4. Install the device, connect it to the network, and power on the device.

    For information about installing the device, see the respective installation guide on the Product Documentation website.

  5. After the device is powered on, the factory default settings in the device trigger a built-in script (ztp.py). The script obtains the IP addresses for the management interface, default gateway, DNS server, TFTP server and the path of the onboarding script on the TFTP server, from the DHCP server.
  6. The device configures its management IP address, static default route, and the DNS server address, based on the values from the DHCP network.
  7. The device downloads the onboarding script, based on the values from the DHCP network, and executes it, resulting in the onboarding configuration statements to be committed.
  8. The device opens an outbound SSH session with Paragon Automation based on the committed onboarding configuration.
  9. Paragon Automation configures management and telemetry parameters including gNMI by using NETCONF. Paragon Automation also configures the interfaces and protocols based on the configurations defined in the network implementation plan associated with the device, using NETCONF.

Sample Onboarding Script for Committing SSH Configuration on a Device

The following is a sample of the onboarding script that is downloaded from the TFTP server to the device:

What's Next

Connect to the Paragon Automation GUI and view the status of device onboarding. After the device status changes to Connected on the Inventory page (Inventory > Devices > Network Inventory), you can start managing the device. See Device Management Workflow.

Adopt a Device without ZTP

To adopt a device without ZTP:
  1. Navigate to Inventory > Devices > Network Inventory.

    The Inventory page appears.

  2. On the respective tab of the device type (for example, Router) the device is listed, click Adopt Device-Type. For example, if the device is a router, on the Router tab, click Adopt Router.

    The Device Adoption page appears.

  3. Click Select Site to select the site where the device is installed or to be installed.
    The outbound SSH configuration that is required for the device to establish a connection with Paragon Automation appears.
  4. Click Copy to copy the CLI commands under Apply the following CLI commands to adopt a Juniper Device if meets the requirements. section.
  5. Access the device by using Telnet or SSH and log in to the device in configuration mode.
  6. Paste the contents of the clipboard and commit the configuration on the device.
    The device connects to and is managed by Paragon Automation.
  7. After you adopt a device, you can verify the connectivity status by running the following command on the device:

    An output similar to the following indicates that the device is connected to Paragon Automation:

What's Next

Connect to the Paragon Automation GUI and view the status of device onboarding. After the device status changes to Connected on the Inventory page (Inventory > Devices > Network Inventory), you can start managing the device. See Device Management Workflow.