Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 

Step 1: Begin

This guide walks you through the steps to onboard a Juniper Networks® device to Paragon Automation, so that the device can be managed, provisioned, and monitored through automated workflows. Use this guide if you are a user with the Super User or Network Admin role in Paragon Automation.

Meet Juniper Networks Devices

You can onboard ACX, MX, and PTX devices listed in Supported Hardware to Paragon Automation and manage them.

Install the Device

Follow the instructions in the hardware documentation to unbox the device, mount it on a rack, and power on the device. For details about installing a device, see the device's Hardware Guide at https://www.juniper.net/documentation/.

Prerequisites

Ensure that the following prerequisites are fulfilled before you onboard a device to Paragon Automation:
  1. Paragon Automation is installed. See Paragon Automation Installation Guide.
  2. You must have the Super User or Network Admin role in Paragon Automation to onboard devices to Paragon Automation. Before you can onboard a device to Paragon Automation, ensure that:
    A Super User in Paragon Automation has:
    1. Created an organization and a site to which the device can be onboarded.
    2. Added one or more users with the Network Admin role.
    For more information, see Paragon Automation Quick Start Guide.
  3. A Super User or a Network Admin has:
    1. Created network resource pools, device and interface profiles, and a network implementation plan; see Paragon Automation Quick Start Guide.
    2. Checked if a firewall exists between Paragon Automation and the device. If a firewall exists, the firewall is configured to allow outbound access on TCP ports 443, 2200, 6800, and 32,767.
    3. Configured static routes on the device to reach Paragon Automation by executing the following command:
      user@device# set routing-options static route 0.0.0.0/0 next-hop Gateway-IP-address
    4. Configured a DNS server on the device to resolve domain names or allow the device to access an external DNS server (for example, 8.8.8.8).
    5. Configured NTP server on the device.