> For the complete documentation index, see [llms.txt](https://www.opal-rt.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.opal-rt.com/docs/op4610xg/supplementary-operations/access-the-simulator-remotely-via-ipmi.md).

# Access the Simulator Remotely via IPMI

IPMI remote access is **optional**. It is mainly intended for advanced configuration, troubleshooting, or hardware monitoring. **Most users will never need to use IPMI** in their daily work.

**What is IPMI?**\
The ***Intelligent Platform Management Interface (IPMI)*** allows administrators to manage a system remotely, even when it is powered off or unresponsive.

**Key capabilities include:**

* **Remote hardware access:** Monitor and control hardware without being physically present.
* **System health monitoring:** View temperatures, voltages, and hardware status.
* **Power management:** Power on, reset, or reboot the simulator remotely.
* **Console access:** Troubleshoot, install an OS, or configure the simulator regardless of its state.

**Why use it?**\
IPMI improves efficiency by enabling remote troubleshooting and maintenance, reducing the need for on-site interventions.


---

# 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://www.opal-rt.com/docs/op4610xg/supplementary-operations/access-the-simulator-remotely-via-ipmi.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.
