Step 1: Begin
With Juniper Networks HealthBot, you can intuitively monitor the performance and health of your network. HealthBot 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.
Getting Started Workflow
Here's a high-level view of the workflow for getting HealthBot up and running.
Before You Begin
To install a single server instance of HealthBot, you'll need a virtual or physical server that meets these specifications:
RAM: 512 GB
Disk space: 2 TB (SSD recommended)
Free disk space must be at least 20% of total disk space
Recommended minimum IOPS for the disks: 1000
CPU cores: 64
10-Gbps network connections to both the management and production networks
Ubuntu 16.04; CentOS version 7, Release 7.3 or later; RHEL version 7, Release 7.5 or later
Whatever operating system you choose, it must use kernel version 4.4.19 or later.
If your network is smaller, you can install HealthBot on smaller servers. See HealthBot Server Sizing Calculator for more detailed sizing options.
You'll need root user privileges to install HealthBot on the
server. Make sure that your user account is listed in the
/etc/sudoers file on your server.
You can install HealthBot using the Debian (.deb) installation file on Ubuntu, or a Red Hat Package Manager (.rpm) file on CentOS and RedHat Enterprise Linux (RHEL). We’ll show you how to install HealthBot using Ubuntu. For information on how to install HealthBot on other operating systems, see Using the Interactive Installers in the HealthBot Installation Guide.
- Download the HealthBot application package from the download site.
Store the package file on the server in an easily accessible location like
- Run the sudo apt-get install -y /var/tmp/healthbot-<version>.deb command.
- After the packages are installed, run the healthbot
The setup process asks several questions. 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]).
- When the setup process finishes, run the healthbot start command. This initializes HealthBot services and starts the Web GUI.
- When the start process finishes, the URL for logging in to the HealthBot GUI is displayed. The URL is formatted like this: https://<ip-address-of-healthbot-server>:8080 or https://<hostname-of-healthbot-server>:8080.
- Log in to HealthBot with the default credentials–username: admin; password: healthbot. You'll be prompted to change the default password for the admin user when you first log in.
Set Up Network Devices
Network devices need some minor configuration before they can send their data to HealthBot for monitoring. We provide an example for setting up an MX240 router to send OpenConfig data to HealthBot. 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 HealthBot Installation Guide for details.
Before you begin, ensure the MX240 is running Junos OS 18.3 or later so that the OpenConfig network agent is installed by default.
- Enable OpenConfig on the MX240.
user@router# set system service extension-service request-response grpc clear-text
- Commit the configuration change.
Congratulations! Your first device is ready to send telemetry data to HealthBot.