# Use IPMI on a dedicated server: virtual console, ISO mounting and power > Manage a dedicated server out of band with IPMI: open the remote console, boot from an ISO through virtual media, control power and read sensors with ipmitool. Difficulty: Intermediate Dedicated servers with **IPMI** have a small management computer of their own, the **BMC** (baseboard management controller). It works even when the server is switched off or the operating system hangs, and gives you three things over the network: the **screen and keyboard** (remote console, also called KVM over IP), a **virtual DVD or USB drive** for ISO images, and the **power button**. This guide shows how to use them safely. For the overview of dedicated servers, see [dedicated servers](/guides/dedicated-servers). ## Before you start - A dedicated server that includes IPMI, and its access details: the BMC address, user name and password, which come with your service. - A current browser for the web interface and remote console. - For command-line control: a Linux computer or server with `ipmitool` (`sudo apt install ipmitool`). ## Step 1: Sign in and change the password 1. Open `https://` followed by the BMC address in your browser. The certificate is usually self-signed; check the address and continue. 2. Sign in with the details you received. 3. Change the password straight away in the user settings, to a long, unique one. **Verify:** sign out and in again with the new password. > **Warning** > > Never leave a management controller open to the whole internet. Allow access only from your own IP addresses or through a VPN, and do not reuse its password anywhere else. ## Step 2: Open the remote console In the web interface, open the **remote console** (the name depends on the maker, for example iKVM, Virtual Console or Remote Console). Current controllers open it in the browser (HTML5); older ones may need a Java-based viewer. You now see the server's screen exactly as on a monitor, including the firmware setup and the boot loader. Use it to fix a server that does not boot ([Linux server does not boot](/guides/linux-server-boot-problems)) or to watch an installation. ## Step 3: Boot from an ISO with virtual media 1. In the remote console or the web interface, open **Virtual Media** and attach an installation ISO from your computer (or from a network share, if the controller offers it). 2. Restart the server from the console's power menu. 3. Open the one-time boot menu during start-up, or set the next boot device to the virtual CD/DVD in the controller, and choose the virtual drive. 4. Install the operating system as on a local machine. Upload speed decides how fast the ISO is read, so a small network installer ISO saves time. **Verify:** the installer starts from the virtual drive. After the installation, detach the ISO so the server boots from its disk. ## Step 4: Control power and read the logs with ipmitool `ipmitool` talks to the BMC over the network (RMCP+, interface `lanplus`). Put the password in an environment variable instead of the command line, so it does not show up in your shell history and process list: ```bash export IPMI_PASSWORD='your-bmc-password' ipmitool -I lanplus -H 198.51.100.50 -U admin -E chassis power status ``` The most useful commands: | Command | What it does | |---|---| | `chassis power status` | Shows whether the server is on | | `chassis power soft` | Asks the operating system to shut down cleanly (ACPI) | | `chassis power on` | Switches the server on | | `chassis power cycle` | Power off for at least a second, then on again | | `chassis power reset` | Hard reset, like the reset button | | `sel elist` | The hardware event log, with the sensor of each event | | `sensor list` | Temperatures, fans and voltages with their thresholds | | `sol activate` | The serial console (Serial over LAN); type `~.` on a new line to leave | `chassis power off`, `cycle` and `reset` do not shut down the operating system first; use them only when it no longer responds. ## Troubleshooting **The web interface does not load.** Check that you use `https` and the exact BMC address from your service details, and that your network or VPN may reach it. If it still fails, open a ticket. **The remote console stays black.** The server is switched off, the display is in power saving, or the operating system has no screen output. Press a key in the console, check `chassis power status` and switch it on if needed. **`ipmitool` reports that it cannot establish an IPMI v2 / RMCP+ session.** The credentials are wrong, or IPMI's network port (UDP 623) is blocked between you and the BMC. Check the details and use the web interface to confirm that the account works. **The ISO is detached during installation.** The browser session ended or the network dropped. Keep the console window open until the installer has copied what it needs, or use a network installer. ## Next steps - Disks and RAID: [replace a failed RAID disk](/guides/replace-failed-raid-disk). - Boot problems on Linux: [Linux server does not boot](/guides/linux-server-boot-problems). ## Frequently asked questions ### Does every dedicated server include IPMI? No. IPMI access comes with selected servers; the server's details say whether yours includes it, and the access details arrive with your service. ### Is IPMI the same as iDRAC, iLO or iKVM? They are the server makers' names for their management controllers (BMC). All of them offer a remote console, virtual media and power control; menus and labels differ by maker. ### Can I install any operating system through IPMI? Yes, any system the hardware supports: mount its installation ISO as virtual media and boot from it. Our order form also offers ready images for most systems. ### Is it safe to leave IPMI reachable from the internet? No. Management controllers are a frequent target. Change the default password, allow access only from your own addresses or a VPN, and use it for installation and emergencies. --- Source: \ Updated: 2026-10-15