How to Configure IPMI/BMC for Remote Server Management on a Dedicated Server

Your dedicated server freezes. SSH fails, the website is down, and the operating system won't respond. On a VPS you would click "reboot" in a panel. On a physical machine in a data centre, you need something that works even when the OS doesn't.

That something is IPMI, and it is one of the most useful features of bare-metal hosting.

Quick answer: IPMI is a standard for managing a server through its BMC, a small controller on the motherboard that runs independently of the operating system. With it, you can power the server on or off, view its screen, mount an ISO, and read hardware sensors remotely. You set it up by securing an admin account, testing with ipmitool, and keeping it off the public internet.

What Are IPMI and BMC?

BMC (Baseboard Management Controller) is the hardware: a tiny separate computer on the motherboard with its own processor, memory, and network connection. It stays alive as long as the server has standby power, even when the server is switched off.

IPMI (Intelligent Platform Management Interface) is the standard that defines how you talk to the BMC: power commands, sensor readings, event logs, and so on.

Each hardware brand has its own name for its version. Supermicro uses IPMI, Dell uses iDRAC, and HPE uses iLO. They all do the same core job, with different web interfaces and extra features.

eServers UK lists remote management through IPMI, iDRAC, or on-demand KVM over IP on its bare-metal servers, and its Linux range runs on enterprise-grade Supermicro hardware. The examples below use ipmitool, a standard utility that works with most vendors.

What Can You Do With It?

• Power control: power on, shut down, reset, or power cycle the server.

• Remote KVM: a live remote screen, keyboard, and mouse. You can see the BIOS, the boot process, and a frozen OS.

• Virtual media: attach an ISO from your own computer to reinstall an OS or boot a rescue disk.

• Hardware monitoring: temperatures, fan speeds, voltages, and power supply status.

• System Event Log (SEL): a hardware log that records overheating, fan failures, and memory errors, even if the OS never noticed them.

• Serial over LAN (SOL): a text console over the network, useful for boot failures and kernel messages.

Which of these you get depends on your server model, firmware, licence, and your provider's access policy.

Before You Start

Important for hosted servers: in a data centre, your provider often sets up the BMC's network (IP address, VLAN) and gives you access through a VPN, an IP allowlist, or a web portal. In that case you may only need to secure your account and test access, so skip Step 3. Ask your provider first, because a wrong network setting can cut you off from the BMC until their support team fixes it.

You will need:

Step 1: Install ipmitool and Check the Local BMC

Ubuntu or Debian:

sudo apt update
sudo apt install -y ipmitool
                            

AlmaLinux or Rocky Linux:

sudo dnf install -y ipmitool
                            

Load the kernel modules that let Linux talk to the BMC (they often load automatically):

sudo modprobe ipmi_msghandler
sudo modprobe ipmi_devintf
sudo modprobe ipmi_si
                            

Test it:

sudo ipmitool mc info
                            

If you see the BMC's manufacturer and firmware version, local access works. If you get an error, check that the modules loaded. Virtual machines have no BMC, so this only works on physical servers.

Step 2: Find the BMC's Network Channel

The BMC's LAN port is usually channel 1, but some boards use 2 or 8.

sudo ipmitool lan print 1
                            

Look for the IP address source (DHCP or static), IP address, subnet mask, and default gateway. If channel 1 gives an error, try lan print 2 or lan print 8, or check which channels exist with sudo ipmitool channel info 2.

Step 3: Set a Static IP for the BMC (Optional)

A fixed address makes the BMC easy to find when something breaks. The values below are examples, so use your own:

sudo ipmitool lan set 1 ipsrc static
sudo ipmitool lan set 1 ipaddr 10.0.0.50
sudo ipmitool lan set 1 netmask 255.255.255.0
sudo ipmitool lan set 1 defgw ipaddr 10.0.0.1
                            

Check the result:

sudo ipmitool lan print 1
                            

Run these from SSH on the server itself, not from the BMC web page. Changing the BMC's address while you are connected through it will drop your session.

Step 4: Create a Secure Admin User

Some boards ship with a default account such as ADMIN. Older units used a well-known default password, and newer ones usually print a unique password on a label. Either way, create your own account.

See which user slots are used:

sudo ipmitool user list 1
                            

Pick a free slot (this example uses ID 3):

sudo ipmitool user set name 3 sysadmin
sudo ipmitool user set password 3
sudo ipmitool user enable 3
sudo ipmitool channel setaccess 1 3 callin=on ipmi=on link=on privilege=4
                            

The password command asks you to type the password, so it never lands in your shell history. privilege=4 means Administrator.

Test the new account (Step 5) before you change or disable any old one. Never remove your only working admin account.

Step 5: Test Remote Access

From your own machine, use the lanplus interface, which supports IPMI 2.0:

ipmitool -I lanplus -H 10.0.0.50 -U sysadmin -a chassis power status
                            

The -a flag asks for the password instead of putting it in the command. A working connection returns:

Chassis Power is on
                            

Other power commands use the same pattern:

ipmitool -I lanplus -H 10.0.0.50 -U sysadmin -a chassis power soft    # clean shutdown
ipmitool -I lanplus -H 10.0.0.50 -U sysadmin -a chassis power on
ipmitool -I lanplus -H 10.0.0.50 -U sysadmin -a chassis power off     # hard power off
ipmitool -I lanplus -H 10.0.0.50 -U sysadmin -a chassis power reset   # hard reboot
ipmitool -I lanplus -H 10.0.0.50 -U sysadmin -a chassis power cycle   # off, then on
                            

Try soft first. It asks the OS to shut down cleanly, but it only works if the OS is still responding. Hard off, reset, and cycle cut power without warning and can corrupt files or lose unsaved data, so use them when nothing else works.

Step 6: Use the Web Interface and Remote KVM

Open the BMC's address in a browser, for example https://10.0.0.50. This is a private example address, so you may need your provider's VPN to reach the real one.

The web interface usually includes:

• Remote console (KVM): see the BIOS, boot messages, and installers. Newer boards use an HTML5 viewer in the browser.

• Virtual media: mount an ISO file from your computer.

• Sensor readings: temperatures, fans, and voltages.

• Maintenance: firmware and BMC settings.

To reinstall an OS remotely:

1. Back up your data. A reinstall erases the disks you select.

2. Open the remote console and mount the OS installer ISO as virtual media.

3. Reboot the server and open the boot menu. On many Supermicro boards this is F11, but check your board's manual.

4. Choose the virtual CD/DVD and run the installer in the console window.

5. Unmount the ISO when the installation finishes and confirm the server boots from its own disk.

Step 7: Read Sensors and Hardware Logs

sudo ipmitool sdr elist      # all sensors with readings
sudo ipmitool sensor list    # sensors with warning thresholds
sudo ipmitool sel list       # System Event Log
                            

Watch for temperatures above their limits, failed fans, power supply faults, voltage warnings, and memory errors. These show up in the SEL even when the OS reported nothing, so review it regularly instead of only after a crash.

Save the log before you ever clear it, because it is useful evidence for support tickets:

sudo ipmitool sel save /root/ipmi-sel-backup.txt
sudo ipmitool sel clear
                            

Step 8: Set Up Serial Over LAN (Optional)

SOL gives you a text console that works when SSH doesn't. It needs three things to line up: the BIOS, the OS, and the BMC.

• BIOS: turn on serial console redirection (usually under Advanced settings).

• OS: add the serial console to your GRUB settings in /etc/default/grub. Add to your existing lines instead of replacing them:

GRUB_CMDLINE_LINUX="console=tty0 console=ttyS1,115200n8"
GRUB_TERMINAL="console serial"
GRUB_SERIAL_COMMAND="serial --speed=115200 --unit=1 --word=8 --parity=no --stop=1"
                            

The port can be ttyS0 or ttyS1 depending on the motherboard. Then rebuild the GRUB config:

sudo update-grub                                  # Debian / Ubuntu
sudo grub2-mkconfig -o /boot/grub2/grub.cfg       # AlmaLinux / Rocky (BIOS boot)
                            

UEFI systems use a different output path, so check yours before running the second command.

Connect from your machine:

ipmitool -I lanplus -H 10.0.0.50 -U sysadmin -a sol activate
                            

Press ~. at the start of a line to exit. If the session sticks, run sol deactivate from another terminal. A wrong console setting can affect boot output, so apply it when you have KVM access as a fallback.

Step 9: Lock It Down

The BMC controls your server's power and console, so anyone who gets in has the same power as someone standing at the machine. Treat these as required:

• Keep the BMC off the public internet. IPMI uses UDP port 623 plus a web interface. Put both behind a VPN, a private network, or a strict IP allowlist.

• Replace default credentials with long, unique passwords and remove accounts you don't use.

• Know the protocol's weakness. IPMI 2.0 authentication (RAKP) lets anyone who can reach the BMC request a password hash and crack it offline. A strong password helps, but only network isolation fixes the root problem.

• Disable cipher suite 0 if your firmware allows it. It means "no authentication."

• Update the BMC firmware. Vendors regularly patch BMC vulnerabilities. Read the release notes first, because a failed flash can leave the BMC unusable.

• Review logs for failed logins, new users, and unexpected power actions.

Common Problems and Fixes

Conclusion

IPMI makes a physical server in a distant data centre feel like it's next to you. The key habits are simple: secure the account, keep the BMC private, and test your recovery steps before an emergency.

To get hardware with remote management built in, explore eServers UK's bare-metal dedicated servers or their Linux dedicated servers, or browse the full server range. Check which management tool (IPMI, iDRAC, or KVM over IP) comes with the configuration you choose.