iLO, iDRAC and IMM: What They Do and What the Licence Adds
Remote management is the difference between a fault that takes twenty minutes and one that takes a day and a site visit. This covers what these controllers do, what the licences change, and what to configure before you need them.
What a management controller actually is
A small computer inside the server, with its own processor, its own network connection and its own power, running independently of the operating system.
That independence is the point. It works when the machine is powered off, when the operating system has crashed, and when the machine will not boot at all. Those are exactly the situations where you need information and cannot get it any other way.
HPE calls it iLO, Dell calls it iDRAC, Lenovo and IBM call it IMM or XCC. The names differ; the capability is the same.
What you get without a licence
More than people assume.
Power control — on, off, reset, remotely.
Hardware health — memory by slot, drives by bay, power supplies, fans, temperatures, with faults identified.
Event log, which frequently records what stopped a boot.
Serial, model and configuration without touching the machine. Our serial lookup guide covers using this.
For inventory, health monitoring and remote power cycling, the base capability is enough.
What the licence adds, and why it matters
Two features, and they are the ones you need in an emergency.
Remote console. Seeing and controlling the screen and keyboard as though you were in front of the machine — through boot, firmware setup, and operating system install. Without it, anything that needs to be seen during boot needs someone on site.
Virtual media. Mounting an ISO or image from your machine as though it were in the server’s drive. This is how you install or repair an operating system remotely.
Together these mean a machine that will not boot can be diagnosed and rebuilt without anyone travelling. For a remote site, that single capability frequently justifies the licence on its own.
The catch on used equipment: licences do not always transfer. Check before buying. Our used server guide covers this among the eight questions worth asking.
Configure it before you need it
Five things, and each one is discovered missing at the worst time.
A network address you can reach when the production network is affected. A management controller on the same network as everything else is unreachable in exactly the situations it exists for.
Credentials that work, recorded somewhere accessible when systems are down. Not on a wiki hosted on the failed server.
Tested access. Log in from where you would actually be, on a device you would actually have.
Alerts configured and routed to a person. The controller sees hardware faults the operating system does not. Our monitoring guide covers what to alert on.
Firmware updated. Management controller firmware carries security fixes, and a controller with a network connection and old firmware is a real exposure.
Security: it is a computer on your network
Three things that follow.
Never leave default credentials. Management controllers with default passwords are found and used, and they give complete control of the machine.
Put them on a separate management network, not reachable from the general network or the internet. This is the single most important control. Our segmentation guide covers arranging it.
Keep firmware current, unlike the general rule for production hardware where updating without reason is unnecessary. Management controllers are the exception because they are network-exposed.
What it cannot do
Being clear about the limits.
It cannot fix hardware. It tells you which part failed, which is most of the diagnosis, but someone still has to replace it.
It cannot help if the network to it is down, which is why a separate management network and, at larger sites, a separate path matter.
And it cannot replace a console for the times everything is down. Our KVM guide covers the local option.
Frequently asked questions
What is iLO, iDRAC or IMM?
A small computer inside the server with its own processor, network connection and power, running independently of the operating system. It works when the machine is off, crashed, or will not boot.
What do I get without a licence?
Power control, hardware health by component, the event log, and serial and configuration information. Enough for inventory, health monitoring and remote power cycling.
Is the management licence worth buying?
For remote sites, frequently yes on its own. It adds remote console and virtual media, which together mean a machine that will not boot can be diagnosed and rebuilt without anyone travelling.
Does the licence transfer with a used server?
Not always. Check before buying, because it is the feature you need when the machine will not boot and nobody is on site.
Should management controllers be on the main network?
No. Put them on a separate management network, not reachable from the general network or the internet. A controller on the same network as everything else is unreachable in exactly the situations it exists for, and it is a security exposure.
Should I update management controller firmware?
Yes, unlike the general rule for production hardware. Management controllers are network-exposed and their firmware carries security fixes, so they are the exception to updating only for a specific reason.
Tell us the platform and we will confirm which management features are licensed and what a licence covers on that generation.
