TL;DR
| iLO | ProLiant | Latest firmware | Date | Status |
|---|---|---|---|---|
| iLO 1 | G2–G4 (and 100-series up to G6) | 1.96 | 2014-04-30 | Final |
| iLO 2 | G5–G6 (300-series and up) | 2.33 | 2018-03-30 | Final |
| iLO 3 | G7 | 1.94 (1.94.2) | 2020-12-06 | Final; HPE will not publish more |
| iLO 4 | Gen8–Gen9 | 2.82 | 2023-02-06 | Nothing new since 2023 |
| iLO 5 | Gen10 / Gen10 Plus | 3.21 | 2026-07-31 | Active |
| iLO 6 | Gen11 | 1.78 | 2026-07-31 | Active |
| iLO 7 | Gen12 | 1.24.00 | 2026-08-02 | Active |
Data as of 2026-09-25. The first four generations no longer get new releases; iLO 5, 6 and 7 ship firmware every few months, so for those three check HPE’s portal before flashing.
Direct downloads
| iLO | Package | Contains |
|---|---|---|
| iLO 1 | CP023365.scexe | ilo196.bin |
| iLO 2 | CP035238.scexe | ilo2_233.bin |
| iLO 3 | CP046328.scexe | ilo3_194.bin |
| iLO 4 | CP053894.scexe | ilo4_282.bin |
| iLO 5 | ilo5_321.fwpkg | ilo5_321.bin |
| iLO 6 | ilo6_178.fwpkg | ilo6_178.bin |
| iLO 7 | ilo7_1.24.00.fwpkg | ilo7_1.24.00.bin |
At the time of writing all seven links answer 200 with no HPE account. The iLO 5/6/7 ones will go stale: on the support portal search Integrated Lights-Out 5 (or 6, 7) → Drivers & Software → Firmware. A public tracker that keeps up: pingtool.org.
Extracting the .bin from the package
| |
The web UI on iLO 5 and later accepts the .fwpkg as is. The .bin works on every generation and is what load -source over SSH expects.
Checking the installed version
No login, through the iLO’s inventory XML (works at least from iLO 2 to iLO 5):
| |
Over SSH, show /map1/firmware1. On iLO 2/3, when the browser no longer gets in, the XML and SSH still answer.
Intermediate steps
A big jump between versions sometimes fails with an opaque error (flash failed, invalid image). What is documented:
- iLO 3: if you are below 1.20, go to 1.20 first. From 1.55 go to 1.57 and then to 1.94 (guide on GitHub).
- iLO 4/5/6/7: read the release notes of the target version; HPE states there whether a minimum prior version is required.
If a direct flash fails, find the intermediate in the portal’s history and do it in two steps.
How to apply it
| Path | When |
|---|---|
| Web UI → Administration → Firmware | The normal way on iLO 4+; on iLO 2/3 only if the browser gets in (TLS trick) |
SSH: load -source http://…/iloN_xxx.bin | When the UI does not open. Full procedure |
| From the operating system | The same .scexe run as root on Linux (or the .exe on Windows) flashes online; it also ships in the SPP |
Traps
- iLO 3 on 1.94 is still TLS 1.1; the last release does not fix access from Chrome/Edge. Details in ERR_SSL_VERSION_OR_CIPHER_MISMATCH.
- Official firmware only. The
.fwpkgfiles are signed and the iLO refuses images from another generation; there is no risk of pushing anilo4_*.bininto an iLO 5, but there is also no point hunting for it on mirrors. - Gen8/Gen9 are out of support. iLO 4 2.82 has had no successor since 2023; if a security advisory shows up, HPE’s portal is the only source.
- Do not cut the session. The iLO reboots itself when done; the server stays up.
See also
- Upgrade iLO firmware over SSH
- iLO CLI commands
- Read the license key without the UI — the same
xmldataendpoint