Skip to content

VPS & dedicated

IPMI and iKVM on dedicated

Use IPMI and iKVM to recover, reinstall, and power-cycle a dedicated server when the operating system is unreachable.

Updated Aug 29, 20263 min read20 reads

Tags

IPMI and iKVM on dedicated
IPMI and iKVM on a dedicated server

IPMI is a small management computer on the dedicated server motherboard that stays available when the operating system will not boot. iKVM is the remote keyboard, video, and mouse session that rides on that same controller, so you can see the screen, mount an ISO, and work as if you were standing at the rack. On a LogicWeb dedicated server you get a physical chassis with IPMI for power control, BIOS access, and reinstalls without a datacenter visit.

When IPMI and iKVM help you

Use IPMI when the kernel panics, the filesystem will not boot, or networking never starts and SSH is gone. iKVM lets you watch GRUB, press a key at the right moment, and click through an installer after you mount a vendor ISO on the BMC. You can also confirm the chassis is powered on, or finish a Windows update that sits on “getting ready” with no network path left. Treat IPMI as the wrench for those moments, not as your daily admin session. Keep routine package work and site management on the public NIC over SSH once the OS is healthy again.

How dedicated IPMI differs from a VPS console

A VPS console and an IPMI session can look similar in a screenshot, but they are not the same path. On dedicated hardware you mount the ISO on the BMC, boot it, install the OS, then restore keys and DNS records as needed. On a KVM VPS you rebuild from the panel, which wipes the guest disk and has no BMC to log into. Shared hosting has neither option; you open a ticket instead of booting the node. Document the IPMI address separately from the server’s public IP so a browser timeout on the site address does not look like a dead chassis at 2 a.m.

Keep IPMI reachable by you, not by everyone

IPMI must be reachable when you need it, but it should not sit open on the public internet with factory defaults. Change the BMC password in the first hour, and restrict access with a VPN, an allow list, or a jump host. Do not run the website on the BMC address, and do not leave the console bookmarked as a substitute for SSH. Test iKVM on a calm day so you are not learning a new Java or HTML5 prompt during an outage.

When the OS is down, IPMI and iKVM are the reliable way back onto a dedicated box. When the OS is up, use the public network for normal work and keep the BMC locked down for the next real emergency.

Share

Send this article

Need someone else to do this? Send them the link — the commands are in the article.

Tagged

Was this article helpful?

Be the first to rate this article.