Help Center User GuideGetting StartedFAQRelease Notes
 
X
User Guide
Getting Started
FAQ
Release Notes
Contents  

Troubleshooting

Starting with Release 2.1.0, HealthBot supports four verification and troubleshooting features:

You can access these features by navigating to Administration > Debug from the left-nav panel.

HealthBot Self Test

Overview

When setting up basic functionality in HealthBot, it can be challenging to diagnose problems. From installation, to device configuration, to adding devices and applying playbooks, when an issue occurs there are many possible areas to investigate.

Starting with HealthBot 2.1.0, the self-test tool validates the core functionality of HealthBot. To perform the self test, the tool performs a typical set of tasks:

The self-test instance essentially acts as a fully working setup, running entirely within the HealthBot system. When testing is complete, the tool provides a report.

Other Uses for the Self Test Tool

In addition to validating the HealthBot installation, the self-test feature also provides:

Usage Notes

How to Use the Self Test Tool

Procedure

  1. Navigate to the Administration > Debug page from the left-nav panel, and select the APPLICATION tab.
  2. Select the desired sensor type(s) from drop-down menu.
  3. Click the Test button.
  4. After a few moments, the test results appear.

    The example above shows that both sensors are working as expected.

Device Reachability Test

Overview

In early versions of HealthBot, there was no way to easily determine whether the devices you added were up and reachable; you would need to get through the entire setup procedure - add the device, setup a device group, apply playbooks, monitor devices - at which point the health pages would indicate “no data” indicating that the setup did not work correctly. Furthermore, “no data” does not indicate whether the problem is a reachability issue or data streaming issue.

Starting with HealthBot 2.1.0, the device reachability tool can verify connectivity to a device. The tool performs tests using ping and SSH. HealthBot uses the device’s IP address or host name, based on what was configured when adding the device.

Usage Notes

How to Use the Device Reachability Tool

Procedure

  1. To access the tool:
    • Navigate to the Administration > Debug page from the left-nav panel, and select the REACHABILITY tab.

    • Or, on the Dashboard page click the desired device in the device list widget, and in the pop-up window click the REACHABILITY TEST button.

    Note The REACHABILITY TEST button does not appear when first adding the device.

  2. In the Device Reachability tool, select the desired device from drop-down menu.
  3. Click the Test button.
  4. After a few moments, the test results appear.

    The example above shows that the ping test was successful, but the SSH test failed.

Ingest Connectivity Test

Overview

In early versions of HealthBot, there was no way to easily determine which ingest methods were supported for a given device; you also had no way to know whether the configured ingest method successfully established a connection with the network device.

Starting with HealthBot 2.1.0, the ingest connectivity tool can verify ingest methods where HealthBot initiates the connection, such as OpenConfig, iAgent, and SNMP. HealthBot does not test UDP-based ingest methods, such as syslog and Native GPB, as the UDP parameters are common to a device group and not specific to a device.

HealthBot validates each supported ingest method in its own way:

This tool provides multiple benefits:

Usage Notes

How to Use the Ingest Connectivity Tool

Procedure

  1. To access the tool:
    • Navigate to the Administration > Debug page from the left-nav panel, and click the INGEST tab.

    • Or, on the Dashboard page click the desired device in the device list widget, and in the pop-up window click the INGEST TEST button.

    Note The Ingest Test button does not appear when first adding the device.

  2. In the Ingest Connectivity tool, select the desired device from drop-down menu
  3. Click the Test button.
  4. After a few moments, the test results appear.

    The example above shows that iAgent is supported, OpenConfig is not supported, and SNMP encountered an error.

Debug No-Data

Overview

One of the most common problems that a HealthBot users face is “How to debug no-data?”. Determining the root cause is challenging as the issue can occur for a variety of reasons, including:

In early versions of HealthBot, you needed to manually look for the problem, checking add-device parameters, reviewing logs, checking the device configuration, and so on.

Starting with HealthBot 2.1.0, the debug no-data tool helps to determine why a device or rule is showing a status of “no-data”. The tool takes a sequential, step-by-step approach to determine at which stage incoming data is getting dropped or blocked, as follows:

Usage Notes

How to Use the Debug No-Data Tool

Procedure

  1. To access the tool:
    • On any device health page, click a “no data” tile.

    • Or, navigate to the Administration > Debug page from the left-nav panel, and select the NO DATA tab.

  2. In the Debug No-Data tool, select the desired device group, device, and one or more rules from the drop-down menu
  3. Click the Debug button.
  4. After a few moments, the test results appear.

    The example above shows that one common services is not working properly.

Help us to improve. Rate this article.
Feedback Received. Thank You!

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