Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
ON THIS PAGE
 

Using the Interactive Installers to Install or Upgrade to Paragon Insights Release 4.X

This topic provides information on how to:

  • Perform a fresh installation of Paragon Insights releases 4.0.0, 4.1.0, 4.2.0, or 4.3.0.

  • Seamlessly upgrade Paragon Insights from an earlier 4.X release to a later release.

    Note:

    If you are currently using Paragon Insights with Docker Compose-based installation, then you must perform a fresh installation of Release 4.X. If you are using Paragon Insights with Kubernetes-based installation, follow the instructions provided in the Upgrading Paragon Insights Release 3.X with Kubernetes-based Installation to Release 4.X topic.

You can perform an online or offline installation of Paragon Insights.

  • Online Installation—You need an active internet connection to run an online installation of Paragon Insights. You must download the necessary online package (.deb for Ubuntu or .rpm for CentOS/RedHat) from the Juniper Networks Software Downloads page and install them. You can then proceed to run the sudo healthbot setup and healthbot start commands.

  • Offline Installation—You do not need an active internet connection during offline installation. However, you need an active internet connection to download and install the necessary Paragon Insights package (.deb for Ubuntu or .rpm for CentOS/RedHat) from the Juniper Networks Software Downloads page and install them. After you install the package (.deb or .rpm), you must download the offline install package to the /var/local/healthbot directory and rename the file to healthbot-offline.tgz. You can then run the sudo healthbot setup and healthbot start commands without an active internet connection.

The Paragon Insights (formerly HealthBot) software package is available for download as a Debian (.deb) file for installation on Ubuntu, or a Red Hat Package Manager (.rpm) file for installation on CentOS and Red Hat Enterprise Linux (RHEL).

Before You Begin

You will need the following details for the installation:

  • Deployment type—Single node or multinode installation. Multinode installations are useful for load distribution and scaling.

  • SSL certificate and private key—Supply your own key, or have Paragon Insights create one for you.

  • Host IP address—The server IP address, for SSH and Web UI access.

  • If you are using Paragon Insights to install a new Kubernetes cluster, ensure that the hostnames of the nodes resolve to the IP addresses of the nodes used in the Kubernetes cluster. You can use DNS to map the hostname to the IP address or add the entries to the local /etc/hosts file.

  • If you are installing Paragon Insights into an existing Kubernetes cluster, you need information about the existing Kubernetes cluster:

    • Docker registry name

    • The path to a kubeconfig file configured with the existing cluster details

    • A user account with administrator privileges for the Kubernetes cluster

Note:

The following points regarding installation on an existing Kubernetes cluster must be considered:

  • Paragon Insights has only been qualified with the Calico container network interface (CNI). It should work with other CNI plugins, but has not been tested.

  • If your Kubernetes cluster uses other CNI plugins, such as Flannel, you might notice long playbook deployment times on some Kubernetes versions. One potential workaround, is to disable transmit (tx) and receive (rx) checksum offloading on VXLAN interfaces. An example of this, using Flannel: ethtool --offload flannel.1 tx off rx off.

    For discussions regarding the latency issue, see:

  • If there are a large number of device groups in Paragon Insights, there is the possibility that some of the Kubernetes pods might not get scheduled if the nodes are saturated by the maximum pods per node limit. By default, this limit is 110 pods per node in most Kubernetes distributions.

    As a workaround, you can increase the maximum pods per node setting. Refer to the documentation from your Kubernetes distribution for details on how to modify this setting.

  • If your CNI plugin is configured with a static IP CIDR block for each node, make sure the number of IP addresses in the block allocated to the node is at least double the size of the maximum pods per node setting.

Additional requirements:

  • You must have a Juniper.net user account with permissions to download the Paragon Insights software package.

  • The Paragon Insights server must have access to the Internet during the software extraction process of installation (.deb for Ubuntu or .rpm for CentOS/Red Hat).

Paragon Insights creates a /var/local/healthbot/ directory as part of the installation process. This directory contains all the Paragon Insights-related files.

Installing Paragon Insights On Ubuntu

The general workflow for installing Paragon Insights on Ubuntu is shown in Figure 1.

Figure 1: Installation Workflow - Paragon Insights on UbuntuInstallation Workflow - Paragon Insights on Ubuntu
Note:

For multinode installations, perform the following tasks only on the primary node.

If you are logged in as root or using root privileges, remove the sudo portion of each command below.

Part 1 - PREPARE

  1. Ensure that you have at least 60GB of free disk space. We recommend 100GB of free disk space.
  2. Set the environment variable, HB_EXTRA_MOUNT1, to allow Paragon Insights to access directories outside of the /var/local/healthbot directory.

    To set the environment variable:

  3. Set the environment variables— HB_IAM_SKIP_MAIL_VERIFICATION and HB_IAM_DISABLE_SMTP_SETTINGS— as false to enable e-mail verification of users.

    To set the environment variable:

  4. Ensure that the Ubuntu package lists on your host system are latest.
  5. (Optional) Install the wget package. This tool will be used later to download the Paragon Insights software package. On some installations, wget is installed by default.
  6. Install Docker CE.

    The following commands install the latest stable version on x86 machines:

    To verify that Docker is installed and running:

    To verify the Docker version installed:

    or

    For more information, see Get Docker CE for Ubuntu and Manage Docker as a Non-root User.

  7. (Optional) Add your user account to the Docker group. This is required for a later installation step.

    If installing and running with root privileges, this step is not required.

    Log out of the current session, and log back in.

Part 2 - DOWNLOAD

  1. Download the Paragon Insights package from the Juniper Networks Software Download page to a temporary directory (like /var/tmp/) on the server. Note that downloading software requires a Juniper.net account.

    Note:

    You can also download the Paragon Insights package locally and push it to the server.

Part 3 - INSTALL

  1. Install the .deb package using the following format:

    Paragon Insights checks that prerequisite software is installed on your host device during this step. If any required software is not found, Paragon Insights will prompt you before installing those missing software packages.

    For example:

    root@ubuntu:/var/tmp#

    Note:

    If you see the following error when running the sudo apt-get command, you can ignore it:

    “Can't drop privileges for downloading as file '/home/user/healthbot-3.0.0-1.deb' couldn't be accessed by user '_apt'. - pkgAcquire::Run (13: Permission denied)”

    For more information, see Bug 1543280.

  2. Download the offline install package that is required for offline installation from the Juniper Networks Software Downloads page. Once downloaded, change the name of the file to healthbot-offline.tgz and place it in the /var/local/healthbot directory.

  3. Enter sudo healthbot setup to configure your installation. You can also use sudo healthbot -v setup to display more detailed information.

    While running the sudo healthbot setup command, you are prompted to answer several questions as part of the setup process. For more information, see Paragon Insights Interactive Installation Prompts.

    An example of the setup command from a multinode installation:

    An example of the setup command from a single-node installation:

    Paragon Insights installation is now complete. If any errors occurred, they will be listed in the outputs above.

  4. Enter healthbot start to start Paragon Insights services including the Web UI.

    For example:

  5. Enter healthbot status to verify that the Paragon Insights services are up and running.

    For example:

Part 4 - LOG IN

  1. Open a browser and enter the https://server-IP:8080 URL to access the Paragon Insights UI, where server-IP is the virtual IP address you entered, to connect to Paragon Insights services, during installation. Log in to the Paragon Insights Web UI using the credentials: Username: admin, Password: Admin123!. These are one-time credentials. When you enter them, Paragon Insights prompts you to change the password and gives instructions about the recommended length, case changes, and so on.

    Note:

    Starting from Paragon Insights Release 4.1.0, username is not case sensitive.

Installing Paragon Insights On CentOS

The general workflow for installing Paragon Insights on CentOS is shown in Figure 2.

Figure 2: Installation Workflow - Paragon Insights on CentOSInstallation Workflow - Paragon Insights on CentOS
Note:

For multinode installations, perform the following tasks only on the primary node. If you are logged in as root or using root privileges, remove the sudo portion of each command below.

Part 1 - PREPARE

  1. This procedure assumes you are installing Paragon Insights using a non-root user. If this user does not already have sudo privileges, set them now.
  2. While logged in as root, set secure_path in the /etc/sudoers file to include /usr/local/bin/ so that sudo will be able to locate the Paragon Insights script during the healthbot setup step, later in this procedure.
  3. Install the epel-release repository. This is required for installing Python3 and other packages.
  4. Install the yum-utils package used for handling repositories and extending package management.
  5. Install the wget package. This tool will be used later to download the Paragon Insights software package.
  6. Install Docker CE.

    To verify that Docker is installed and running:

    For full instructions, see Get Docker CE for CentOS and Manage Docker as a Non-root User.

Part 2 - DOWNLOAD

  1. Download the Paragon Insights package from the Juniper Networks Software Download page to a temporary directory (like /var/tmp) on the server. Note that downloading software requires a Juniper.net account.

    Note:

    You can also download the Paragon Insights package locally and push it to the server.

Part 3 - INSTALL

  1. Install the .rpm package using the following format:

    Paragon Insights checks that prerequisite software is installed on your host device during this step. If any required software is not found, Paragon Insights will prompt you before installing those missing software packages. Paragon Insights uses an Internet connection to download any missing packages.

    An example, from CentOS:

  2. Paragon Insights supports offline installation for Kubernetes-based installations.

    Download the offline install package that is required for offline installation from the Juniper Networks Software Downloads page. Once downloaded, change the name of the file to healthbot-offline.tgz and place it in the /var/local/healthbot directory.

  3. Enter sudo healthbot setup to configure your installation. You can also use sudo healthbot -v setup to display more detailed information.

    While running the sudo healthbot setup command, you are prompted to answer several questions as part of the setup process. For more information, see Paragon Insights Interactive Installation Prompts.

    An example of the setup command from a multinode installation:

    An example of the setup command from a single-node installation:

    Paragon Insights installation is now complete. If any errors occurred, they will be listed in the outputs above.

  4. Enter healthbot start to start Paragon Insights services including the Web UI.

  5. Enter healthbot status to verify that the Paragon Insights services are up and running.

    For example:

  6. Verify that SELinux is set to Enforcing. If not, change it to Enforcing..

Part 4 - LOG IN

  1. Open a browser and enter the https://server-IP:8080 URL to access the Paragon Insights UI, where server-IP is the virtual IP address you entered, to connect to Paragon Insights services, during installation. Log in to the Paragon Insights Web UI using the credentials: Username: admin, Password: Admin123!. These are one-time credentials. When you enter them, Paragon Insights prompts you to change the password and gives instructions about the recommended length, case changes, and so on.

    Note:

    Starting from Paragon Insights Release 4.1.0, username is not case sensitive.