ADMINISTRATION PORTAL
Help Center User GuideGetting StartedFAQsRelease Notes
 
X
User Guide
Getting Started
FAQs
Release Notes

HealthBot Installation Requirements

For HealthBot to install successfully, the following hardware and software components are required on the host machine.

HealthBot Hardware Requirements

You can install HealthBot on either a physical or a virtual machine.

Proof-of-concept (POC) system—supports up to two device groups and three devices per device group:

Production system:

See the scaling tool at https://apps.juniper.net/hb-sizing/ for more information on server configurations for a given use case.

HealthBot Software Requirements

HealthBot installs on Ubuntu, RedHat Enterprise Linux (RHEL), and CentOS versions of Linux.

For Ubuntu:

For RHEL:

For CentOS:

Network Requirements

Network Device Requirements

Junos Devices

HealthBot collects data from devices running Junos OS using multiple data collection methods, called sensors. Each sensor type requires a certain Junos OS version, and configuration added to the devices, to enable a connection to the HealthBot server.

Native GPB

NetFlow (IPFIX)

The following samples are for an IPFIX configuration. Lines that start with “##” are comments and are used to point out details in the configuration.

IPFIX Template Configuration

set services flow-monitoring version-ipfix template IPv4-TEMPLATE ipv4-template

Apply IPFIX Template to Enable Traffic Sampling

set forwarding-options sampling instance IPFIX-IPv4-INSTANCE input rate 10 set forwarding-options sampling instance IPFIX-IPv4-INSTANCE family inet output flow-server 10.102.70.200 port 2055
set forwarding-options sampling instance IPFIX-IPv4-INSTANCE family inet output flow-server 10.102.70.200 version-ipfix template IPv4-TEMPLATE
set forwarding-options sampling instance IPFIX-IPv4-INSTANCE family inet output inline-jflow source-address 198.51.100.1

## 10.102.70.200 = HealthBot server

## port 2055; use this value in HealthBot GUI (device group config)

## inline-jflow = Enable inline flow monitoring for traffic from the designated address

## 198.51.100.1 = traffic interface that does the exporting; use this value in HealthBot GUI (device config)

Associate Sampling Instance with the FPC

set chassis fpc 0 sampling-instance IPFIX-IPv4-INSTANCE

Specify the Traffic Interface to Sample and Direction of Sampled Traffic

set interfaces ge-0/0/0 unit 0 family inet sampling input
set interfaces ge-0/0/0 unit 0 family inet sampling output

OpenConfig

iAgent (NETCONF)

SNMP

Syslog

Best Practice Structured syslog is highly recommended because it avoids text parsing by the HealthBot server.

Cisco Device Support

HealthBot can collect telemetry data from Cisco IOS XR devices. To use these devices with HealthBot, you must configure the grpc server and the openconfig-interfaces sensors. HealthBot does not automatically configure these for you.

The following example shows a sensor group sg1 created for gRPC dial-in configuration with the YANG model for interfaces. An hbot_interfaces subscription associates the sg1 sensor group with an interval of 10 seconds to stream data.

Note The following reference configuration is loaded on a device running Cisco IOS XR software version 6.3.2.

!
grpc
port 32767
!
telemetry model-driven
sensor-group sg1
 sensor-path openconfig-interfaces:interfaces/interface
!
subscription hbot_interfaces_
 sensor-group-id sg1 sample-interval 10000
!
!
ssh server v2
end

Multi-Node Installation

Starting with release 3.0.0 HealthBot uses Kubernetes for all HA/multi-node installations. In order to install HealthBot on more than one server, you must install using Kubernetes. All of the needed configuration for the clusters is performed by Kubernetes. During the setup phase of the installation process, you must identify the Kubernetes master node and worker node(s). The following example shows the installation command for an Ubuntu server.

$ sudo apt-get install -y /<path-to-deb-file>/healthbot-<version>.deb
$ sudo apt-get install -y /var/tmp/healthbot-3.0.0.deb
[sudo] password for user: 
Reading package lists... Done
Building dependency tree       
Reading state information... Done
Note, selecting 'healthbot' instead of '/var/tmp/healthbot-3.0.0.deb'
The following NEW packages will be installed:
  healthbot
…
Unpacking healthbot (3.0.0) ...
…
Setting up healthbot (3.0.0) ...
…

Related Documentation

Help us to improve. Rate this article.
Feedback Received. Thank You!
  • Using the Interactive Installers

  • Using the Silent Installer

Ask questions in TechWiki

Check documentation in TechLibrary

Rating by you:      
X

Additional Comments

800 characters remaining

May we contact you if necessary?

Name:
Email:

Need product assistance? Contact Juniper Support

Submit