Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

ON THIS PAGE
 

Step 1: Begin

With Juniper Networks Paragon Insights (formerly HealthBot), you can intuitively monitor the performance and health of your network. Paragon Insights gathers and analyzes configuration and telemetry data from your network devices. It can notify you of current issues, warn you about potential issues, and even take corrective action.

What's Next

You can set up additional devices to send OpenConfig data to Paragon Insights. You can configure different devices to send data in different formats for Paragon Insights to collect (ingest). See the Paragon Insights Installation Guide for details.

Get Ready

Here's a high-level view of the workflow for getting Paragon Insights up and running.

Before You Begin

To install a single server instance of Paragon Insights, you'll need a virtual or physical server that meets these specifications:

  • RAM: 32 GB

  • Disk space: 250 GB (SSD recommended)

  • Free disk space must be at least 20% of total disk space

  • Recommended minimum IOPS for the disks: 1000

  • CPU cores: 16

  • 10-Gbps network connections to both the management and production networks

    This is to ensure the required bandwidth for high volume telemetry data transfer between the device and the HealthBot server.

  • Paragon Insights installs on Ubuntu, RedHat Enterprise Linux (RHEL), and CentOS versions of Linux.

    For more information, see Paragon Insights Software Requirements. See Paragon Insights Server Sizing Calculator for more detailed sizing options.

    Whatever operating system you choose, it must use kernel version 4.4.19 or later. The procedure in this document is tested using Ubuntu 16.04 with a 4.15.0-142-generic kernel.

  • Docker version 18.09.3 or later

    Run the following commands to install docker:

    Note:

    If you plan to install Paragon Insights as a non-root user (using sudo), you must include that user in the docker user group. Run these commands to include the non-root-username user in the docker group:

    After making the changes, ensure that you log out and log back in as the desired user to ensure the changes to group membership are activated.

You'll need root user privileges to install Paragon Insights on the server. Make sure that your user account is listed in the /etc/sudoers file on your server. If you choose to install as the root user you must ensure that SSH login for root is enabled.

Install Paragon Insights

You can install Paragon Insights using the Debian (.deb) installation file on Ubuntu, or a Red Hat Package Manager (.rpm) file on CentOS and RedHat Enterprise Linux (RHEL). We show you how to install Paragon Insights using Ubuntu. For information on how to install Paragon Insights on other operating systems, see Using the Interactive Installers in the Paragon Insights Installation Guide.

Note:

When you install Paragon Insights on a Kubernetes cluster, you must enter host IP address or hostnames for the cluster nodes. If you use hostnames, ensure that the hostnames resolve to the IP addresses of the nodes used in the Kubernetes cluster.

  1. Download the Paragon Insights application package from the download site.

    Store the package file on the server in an easily accessible location like /var/tmp.

  2. Run the sudo apt-get install -y /var/tmp/healthbot-<version>.deb command.
  3. When the install is complete, run the healthbot setup command.

    The setup process asks several questions. When a default option is available, the default values for each question are shown in square brackets ([]). If a choice is required, the default option is capitalized (for example, [Y/n]).

    You must have the following information when you run the healthbot setup command.

    • If you choose to install on an existing Kubernetes cluster, you will need information on IP addresses or hostnames of the Kubernetes master node and worker nodes that make up the cluster.

    • If you want the setup to create a new Kubernetes cluster, you must provide the IP addresses or hostnames for the machines that make up the new cluster.

    • A virtual IP (VIP) address to access the Paragon Insights web UI.

      If you have multiple interfaces connected to different networks, you must specify a virtual IP from each network that you need connectivity from.

  4. When the setup process finishes, run the healthbot start command. This initializes Paragon Insights services and starts the Web GUI.

    When the start process finishes, you’ll see the URL for logging in to the Paragon Insights GUI. For example, https://<ip-address-of-paragoninsights-server>:8080 .

  5. Log in to Paragon Insights with the default credentials–username: admin; password: Admin123!. You'll be prompted to change the default password for the admin user at first log in.
    Note:

    Starting from Paragon Insights Release 4.1.0, username is case insensitive.

Set Up Network Devices

Before you begin, ensure the MX240 is running Junos OS 18.3 or later so that the OpenConfig network agent is installed by default.

  1. Enable OpenConfig on the MX240.

    [edit]

    user@router# set system service extension-service request-response grpc clear-text port number

  2. Commit the configuration change.

    [edit]

    user@router# commit

Network devices need some minor configuration before they can send their data to Paragon Insights for monitoring. Here, we provide an example for setting up an MX240 router to send OpenConfig data to Paragon Insights. You can also configure your devices for periodic device polling, telemetry streaming, and sending event data using other options. See Network Device Requirements in the Paragon Insights Installation Guide for details.

Congratulations! Your first device is ready to send telemetry data to Paragon Insights.