// Benutzung · Steuerung
Power-cycling a server via iDRAC
Power a physical server on or off, or reset it, from the admin UI — through its
iDRAC/Redfish BMC. Like all control actions it runs on the location's agent and
is written to the hub-wide audit log (control.*
rows: a proposed row before it runs, and how it ended).
These are hardware power actions on a real server. Force Off and Power Cycle cut power immediately (no graceful OS shutdown). Requires the
control.executepermission (admin).
Doing it
Open the location → Resources tab.
On the registered iDRAC host card, use the Power buttons:
Button What it does Redfish ResetTypePower On Turn the server on OnGraceful Shutdown Ask the OS to shut down cleanly GracefulShutdownForce Off Cut power immediately ForceOffReset Hard reset ForceRestartPower Cycle Off, then on PowerCycleConfirm in the dialog (it names the host). Everything but Power On is treated as destructive and gets the red confirm.
Buttons are disabled while the agent is unreachable. The action targets the iDRAC host resource, whose stored credential (username/password) the agent reveals to authenticate to the BMC.
Verifying
The result appears in the Agents tab → Control path audit log (the
control rows of the audit log; all of it on the
Audit page with audit.view), and the
server's power draw / state updates on the next agent report (nudged
automatically after the action). If a BMC uses a self-signed certificate, the
resource must have Allow invalid/self-signed TLS certificates ticked (see
Adding a resource to a location), or the action fails on cert
verification.