Verifying docker deployment - Adaptive Applications - BlueCat Gateway - 23.2

Network Discovery Administration Guide

Locale
English
Product name
BlueCat Gateway
Version
23.2

After deploying Network Discovery as a discovery probe, you can verify the deployment from the BlueCat Gateway user interface (UI).

To verify the docker deployment status from BlueCat Gateway:

  1. From the BlueCat Gateway UI, click Network Discovery on the left sidebar.

    A list of available pages is displayed on the left sidebar.

  2. From this list, select Settings to view the Settings page.

  3. The Probe table in the Settings page displays the deployment status:
    • If the configuration and creation of the probe were successful, the Status column for the probe displays the status as Active with a green check icon. It is safe to continue with the rest of Network Discovery setup and configuration.
    • If deployment was unsuccessful, the Status column for the probe displays the status as Fail with a red cross icon, along with the specific error. Any errors must be addressed before further Network Discovery setup. See Resolving deployment errors for information about resolving the errors.

Resolving deployment errors

Typically, you can resolve errors by editing settings in Network Discovery's configuration files. For more details, see Edit and adjust configuration files and settings and Update probe settings. The following table lists the solutions to resolve errors in specific areas:

Area Solution
Discovery Probe credentials

Check and correct the API username, API password, probe label, and probe URL settings.

BAM SSH Connection

Check and correct the BAM SSH username and BAM SSH password settings.

Management Connection

Check and correct API username, API password, and Management URL for remote probe fields.

BAM SSH Connection and Management Connection

Check and correct the BAM SSH username, BAM SSH password, API username, API password, and Management URL for remote probe fields.

If probes have stopped

In the Swagger API documentation for the corresponding container, run the following API (discovery_probe section for v1 REST API and Discovery Probe Resource section for v2 REST API):

POST.../ discovery_probe/start

When you've finished resolving the errors, click Submit.