79
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 06 Aug 2026
79 points (100.0% liked)
Technology
86962 readers
3031 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related news or articles.
- Be excellent to each other!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, this includes using AI responses and summaries. To ask if your bot can be added please contact a mod.
- Check for duplicates before posting, duplicates may be removed
- Accounts 7 days and younger will have their posts automatically removed.
Approved Bots
founded 3 years ago
MODERATORS
Hmm. I don't really understand what the major benefit is to having an integrated management system over just providing a BIOS that can expose its interface on a serial port and having a serial device server attached to the thing, which then means that you aren't tied to a particular management system. I'd also kinda think that it'd be cheaper to use a serial device server if you have a ton of servers in a rack that need to be managed, since one serial port server can handle all of them. Use a smart PMU for power control.
Maybe interfaces are more standardized or something, for automated tasks?
You can mount an ISO image through the BMC and boot the server from there. A serial port would be too slow. The management ethernet is supposed to be on a separate network not exposed on the same network as the rest.
I mean, you can typically do a TFTP boot on the systems that I've seen that have serial-capable BIOS setups.
considers
Heck, I think that all of my modern personal non-serial-port-BIOS systems can do that, even.
If the power is off, the BMC is still active. That's the advantage.
When you're dealing with a large fleet of servers you need a system that you can automate. IPMI is (sort of) standardised, so you can use the same tooling to monitor and manage all of your servers, regardless of model or manufacturer. A serial based interface would put a lot more friction in the way of that, and mean you have to manage and maintain even more devices.
The benefit is when you have a huge number of servers arround the world you can manage them from a few locations without having to have someone go physically touch them. Bonus points they often allow for remote wiping and provisioning, it makes it possible for a few peoole to manage the entier life of a server without ever touching it. This is a lot cheaper than flying people out to each site whenever something goes wrong.
Right
that's why I'm talking about a PMU and serial device server linked to a serial console and BIOS as an alternative. That's another way to accomplish that.
My guess was that IPMI might provide a more-standardized interface, and notabot said that this was the case.