Diagnosing a probe using the HDEBUG shell

Ops Center Analyzer Detail View User Guide
Version
11.0.x
Audience
anonymous
Part Number
MK-99ANA007-06
ft:lastEdition
2026-03-16

If a problem occurs when adding or using a probe in the Analyzer probe server, you can diagnose the problem using the interactive HDEBUG shell. The following probes are supported:
  • Hitachi Enterprise Storage
  • VMware
  • VMAX

Diagnosing a problem when adding a probe

If a failure occurs while attempting to add a probe, follow these steps.

  1. Connect to the HDEBUG shell as the megha or root user.
  2. Run the following command:
    diagnoseProbe --i
  3. Choose the probe type and enter the required details. For example, if you choose 2 (HitachiEnterpriseStorage probe), provide the connection type, RAID agent IP address, host name, port, and so on.
  4. HDEBUG validates your entries and displays the diagnosis. In the following example, the diagnosis suggests that the probe is unable to collect data because the latest data is unavailable from the RAID Agent (possibly because the RAID Agent instance service is not running). You can try to resolve this issue by starting the RAID Agent instance service.

Diagnosing a problem after adding a probe

If a failure occurs after you have successfully added a probe, follow these steps.

  1. Connect to the HDEBUG shell as the megha or root user.
  2. Run the diagnoseProbe command and specify the probe instance (number).
    For example: diagnoseProbe --probeName "421358"
  3. HDEBUG displays the diagnosis on the CLI. The following example shows that data collection has stopped because the Analyzer probe server is unable to connect to the RAID Agent server on port 24221, possibly because the RAID Agent services (REST Application Service and REST Web Service) are not running. You can try to resolve this issue by starting these services.