this post was submitted on 24 Apr 2024
104 points (97.3% liked)
graybeard
239 readers
2 users here now
Stories, links, experiences from calculator manipulators with a few grays in their beard
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
It shouldn’t even be a mandatory purchase of a license. There shouldn’t be any license needed around the OOB controller, and in the past there never was. You wanted an OOB controller, you paid for the hardware and that was that.
I don't think that's entirely correct depending on what you call the "past", I have an HP server that is about 10-15 years old that I cant use iLO after post because of the same message. They have charged for OOB management for years, but I think it was rolled into support contracts. This server was from an old job and iLO worked when it was dcommed
It’s correct based on my timeframe in IT 😂. Call me old but just because they’ve been doing as long as you remember doesn’t make it right. I remember a time when that wasn’t the case.
HP has been doing it for at least 20 years, I remember doing HW scans to send for contract renewals and I'm almost positive that included iLO licensing. Back then it was a "luxury" because we still had most of our servers on prem and could walk up to the KVM if needed. But, maybe you're talking about back before that time.
However, I agree, it doesn't make it right, but it also doesn't mean it hasn't been done for a long time.
Before license keys it was physical hardware. It’s the exact same thing, you just don’t have an object you can hold onto any longer.
Yeah iDrac enterprise was a literal module you installed on the motherboard.
Yep. The last server I had that didn't require iLO advanced licence for post boot console was a Pentium 4-class xeon, and the iLO was a PCI card with extra cables to route standby power, keyboard, mouse, and the reset and soft-power switches. If I'm not mistaken, iLO 2.