Request IPMI or KVM console access

Use the console for out-of-band diagnosis

IPMI/KVM is useful when the operating system is not reachable over SSH: for example, while observing firmware startup, selecting a boot device, reading an early kernel error, or repairing a network configuration. It is not the normal administration channel and should not be left open for routine shell work.

The KVM request is associated with a server owned by the signed-in account. The service accepts the request, creates an action reference, and reports QUEUED. That response confirms storage of the request only; it does not prove that a management controller was contacted or that a session exists.

Queue the request

Do not expect a browser window to open. There is no GET action route in the API, so refreshing the dashboard cannot show progress or completion. Preserve the visible action suffix in case the operator needs to correlate the request with the queue.

1. Open Account > Servers and locate the correct server by name and region.
2. Confirm that the state and timing match the incident you are investigating.
3. Select Open KVM once. The button changes to show a shortened queued action reference.
4. Copy the full context you have: server name, region, order reference if available, time, and the shortened action reference.
5. Contact the operator through the documented support channel and request fulfilment of that queued action.

Handle delivered console access safely

• Verify that the operator’s message identifies the expected server and that the console endpoint uses HTTPS.
• Treat a console link or credential as a secret. Do not paste it into chat, logs, screenshots, or shared issue trackers.
• Observe first. Avoid changing boot order, firmware, storage controllers, or RAID settings unless the recovery plan requires it.
• Never initialize, format, or rebuild a disk before verifying backups and the exact target device.
• Close the browser session and ask for revocation when the work is complete.

Expected result and escalation

The immediate expected result in the account is a queued action reference. The operational result, available only after operator fulfilment, is a temporary remote-console session connected to the intended server. Use it to determine whether the failure occurs before boot, during boot, or after the operating system starts.

If the request is queued but no access arrives, do not generate many duplicate KVM requests. Send the operator one concise report containing the server, region, action suffix, request time, and business impact. If a console opens on an unexpected machine, disconnect without interacting and report it as a security issue.