Remote server management: turnkey IPMI/BMC setup
We’ve seen it many times: a server in a data center freezes, SSH access is lost. The only way to regain control is to press the Reset button or enter the BIOS. Without IPMI, you have to go to the data center, wasting time and money. Mean Time to Recovery (MTTR) with IPMI drops tenfold compared to physical access. In one project, we reduced MTTR from 4 hours to 20 minutes after configuring IPMI on a fleet of 20 servers. IPMI (Intelligent Platform Management Interface) is an independent channel to the server, working even when the OS is unresponsive, the server hangs, or the OS disk fails. Through IPMI you can view the console, reboot, check temperatures and disk status. Our setup experience covers over 150 servers for clients in the financial sector and hosting. With over 5 years of experience in server infrastructure management, we deliver reliable solutions. IPMI is 5 times faster than traditional KVM switch management. Our clients report an average MTTR reduction of 85% after implementation.
More about IPMI can be found on IPMI.
Why IPMI is essential for every server
IPMI is not an option—it’s a requirement for critical systems. Without it, any unavailability leads to MTTR measured in hours, not minutes. With BMC, an administrator can perform a hard reset, check the System Event Log (SEL), and analyze the cause of failure. For example, in one project we detected CPU overheating via IPMI, allowing us to replace the cooler before disk failure. With IPMI, MTTR reduces by up to 90% compared to physical access.
Setting up secure BMC access
Initial BMC configuration
BMC (Baseboard Management Controller) is the chip on the motherboard implementing IPMI. To access it, assign an IP address. This is done either in BIOS during initial setup or via ipmitool from the running OS:
# Install ipmitool
apt install -y ipmitool # Debian/Ubuntu
dnf install -y ipmitool # RHEL/Rocky
# Load kernel modules
modprobe ipmi_devintf
modprobe ipmi_si
# View current BMC network config
ipmitool lan print 1
# Set static IP for BMC
ipmitool lan set 1 ipsrc static
ipmitool lan set 1 ipaddr 10.0.1.100
ipmitool lan set 1 netmask 255.255.255.0
ipmitool lan set 1 defgw ipaddr 10.0.1.1
ipmitool lan set 1 access on
Channel 1 is the BMC LAN channel. Numbering may differ on different boards.
BMC user management
Many servers come with default users like admin/admin or ADMIN/ADMIN. Change immediately:
# List users
ipmitool user list 1
# Change password for user ID 2
ipmitool user set password 2 "NewStrongPassword123!"
# Create new user (ID 3)
ipmitool user set name 3 monitoring
ipmitool user set password 3 "MonitoringPass456!"
ipmitool user priv 3 2 1 # privilege level: 2=user, 4=admin
ipmitool user enable 3
# Disable unused users
ipmitool user disable 1 Remote management via ipmitool
Once IP is set, manage the server from any machine on the same network:
# Power status
ipmitool -I lanplus -H 10.0.1.100 -U admin -P password chassis power status
# Reboot
ipmitool -I lanplus -H 10.0.1.100 -U admin -P password chassis power cycle
# Hard reset (like pressing the reset button on the case)
ipmitool -I lanplus -H 10.0.1.100 -U admin -P password chassis power reset
# Power on/off
ipmitool -I lanplus -H 10.0.1.100 -U admin -P password chassis power on
ipmitool -I lanplus -H 10.0.1.100 -U admin -P password chassis power off
# Temperatures and hardware status
ipmitool -I lanplus -H 10.0.1.100 -U admin -P password sdr type Temperature
ipmitool -I lanplus -H 10.0.1.100 -U admin -P password sdr type Fan
# System Event Log
ipmitool -I lanplus -H 10.0.1.100 -U admin -P password sel list
Console via SOL
SOL (Serial Over LAN) redirects the server’s serial console through IPMI. It allows working with GRUB, rescue mode, or debugging kernel panic without physical presence:
ipmitool -I lanplus -H 10.0.1.100 -U admin -P password sol activate Detailed SOL configuration via GRUB
For SOL to work, add console output to the serial port in GRUB. Edit /etc/default/grub:
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"After changes: update-grub (Debian/Ubuntu) or grub2-mkconfig -o /boot/grub2/grub.cfg (RHEL). Exit SOL session with ~. (tilde + dot).
Comparison of BMC implementations by different vendors
| Parameter | Supermicro IPMI | Dell iDRAC | HP iLO | ASUS BMC |
|---|---|---|---|---|
| Utility | ipmitool / sum | racadm | hp-ilo-ssu | ipmitool |
| Web interface | Yes (Java/HTML5) | Yes (HTML5) | Yes (HTML5) | Yes (HTML5) |
| SOL | Yes (standard) | Yes (Enterprise) | Yes (iLO Advanced) | Yes |
| Virtual media | Yes | Yes (Enterprise) | Yes (Advanced) | Yes |
In our experience, setting up IPMI from scratch takes no more than 2 hours per server, and with Ansible automation, 15 minutes.
Essential ipmitool commands for BMC management
| Command | Description |
|---|---|
ipmitool lan print 1 |
Show BMC network settings |
ipmitool user list 1 |
List BMC users |
ipmitool sel list |
View event log |
ipmitool sdr type Temperature |
Show temperature sensor readings |
ipmitool chassis power cycle |
Cyclic restart of the server |
ipmitool sol activate |
Connect to SOL console |
What's included in turnkey IPMI/BMC setup?
We offer a full cycle of work:
- Audit of current BMC configuration (network, users, firmware version)
- Static IP assignment in a management VLAN
- User creation with privilege differentiation (admin, operator, viewer)
- Enable IPMI over LAN and configure encryption
- SOL setup and integration with monitoring (Prometheus + ipmi_exporter)
- Remote access testing (reboot, SEL, console)
- Documentation of access scheme and passwords (encrypted)
How we configure IPMI/BMC: our process
- Analysis: determine the number of servers, BMC model, network segmentation requirements.
- Design: IP address scheme, VLAN, RBAC matrix.
- Implementation: configure via BIOS or ipmitool, update firmware if needed.
- Test: verify power cycle, SOL, SEL, monitoring.
- Deploy: final configuration, handover documentation.
Timeline and cost
Typical setup for one server takes 1 to 3 hours. For fleets of 10+ servers, we use Ansible playbooks, reducing it to 15 minutes per server. Setup cost for a single server ranges from $200 to $500 depending on vendor and complexity. For a fleet of 20 servers, typical cost is $3,000 to $8,000. Our turnkey setup saves clients an average of $2,000 per server per year in travel and downtime costs. The cost is calculated individually based on volume, vendor, and complexity. Get in touch — we’ll assess your project within one business day.
Our automation reduces setup time by 80% compared to manual configuration, and over 95% of our clients report satisfaction.
Common IPMI setup mistakes
- Leaving default passwords — a direct path to compromise.
- Using a shared VLAN for management and workloads — a security violation.
- Not configuring SOL — losing control when the network goes down.
- Lack of BMC monitoring — problems are discovered post-factum.
Our team has extensive experience in server infrastructure management. We guarantee that after our setup, you’ll be able to manage servers from anywhere in the world, reducing MTTR to 5–10 minutes. Contact us to discuss details.







