> For the complete documentation index, see [llms.txt](https://doc.engenius.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.engenius.ai/bmc-user-guide/monitoring/host-system-diagnostics.md).

# Host System Diagnostics

Beyond routine monitoring and log review, the BMC provides advanced diagnostic tools designed to capture deep system-level data during and after a failure. These features are typically used when working with support engineers to diagnose complex hardware or firmware issues.

This chapter introduces the autonomous tools available for collecting debug data, generating crash dumps, and enabling large-scale diagnostics.

## **Configuring autonomous data collection (ADDC)**

**Autonomous Debug Data Collection (ADDC)** allows you to configure how the system collects detailed debug information during an error recovery event, such as a warm or cold reset.

To configure ADDC:

1. In the sidebar menu, navigate to **Host System Diagnostics** > **ADDC**.
2. Configure the available options:
   * **Error Recovery Mode**: Select the system's response after an error: `None`, `Warm Reset`, or `Cold Reset`.
   * **Data Harvesting Options**:
     * **Harvest uCode**: Collects microcode debug data from the processor.
     * **Harvest PPIN**: Collects the Platform Processor Identification Number, a unique identifier for the CPU.
   * **Polling Configuration**: Proactively check for hardware errors at a defined interval.
     * **MCA Polling**: For Machine Check Architecture events.
     * **DramCecc Polling**: For DRAM Correctable ECC memory errors.
     * **PCIeAer Polling**: For PCIe Advanced Error Reporting.
   * **Retry**: Defines how many times the system should attempt to collect data if the first attempt fails.
3. Click **Save**.

<figure><img src="https://lh7-rt.googleusercontent.com/docsz/AD_4nXdiDlox62JzBEae17S3SguRsz6iaRCwtcohK0D7S7r5hhq8GYP18WMhkwFuKP7VfUTnhJGw9acAnVZexL7Nr7R45Xqth9u3zxWO-mtMTSsQsxwMKHgXsz3YlXBWdcNimSvdpNeJ?key=UlDoHTEZLTRXe-KURf91Rw" alt=""><figcaption></figcaption></figure>

## **Configuring autonomous crash dumps (ACD)**

**Autonomous Crash Dump (ACD)** automatically generates and stores a crash dump file when the system detects a critical failure. This provides a snapshot of the system's state at the time of the crash, which is invaluable for root cause analysis.

To manage ACD:

1. Navigate to **Host System Diagnostics** > **ACD**.
2. Use the **ACD Server** toggle to enable or disable the automatic dump service.
3. To manually trigger a dump, click the **Generate** button.
4. Generated logs will appear in the table, where you can download them.

<figure><img src="https://lh7-rt.googleusercontent.com/docsz/AD_4nXdf9mvIJ3SEjEgu34Kk8AY8LlUGNsCs6UyBQfWxj7C1rYOXHtQmTZDyjQL7HOtcsimfXWEMBclmir3SqAuH1Idqn_StbLdBA1EbOY45Rseo7d2OJgjb7DJy3dazawAtCYmhqgUCdQ?key=UlDoHTEZLTRXe-KURf91Rw" alt=""><figcaption></figcaption></figure>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://doc.engenius.ai/bmc-user-guide/monitoring/host-system-diagnostics.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.