The Integrated Management Log (IML) is the first place to look when a ProLiant server reports a hardware problem. It records events generated by the system ROM and by services such as the iLO drivers: health and status changes, firmware updates, OS information and ROM-based POST codes. iLO manages the IML, so you can read it from a browser even when the server is powered off. This guide covers ProLiant Gen10/Gen10 Plus (iLO 5) and Gen11 (iLO 6); the IML pages are the same in both user guides.
Before you start
- An iLO login. Viewing and exporting need no special privilege in the procedures; marking entries repaired, adding notes and clearing need Configure iLO Settings.
- Correct iLO date and time, so event timestamps line up with your other logs.
- The approximate time the problem started.
IML or iLO Event Log?
| Integrated Management Log (IML) | iLO Event Log | |
|---|---|---|
| What it records | Server hardware and firmware events: fans, power supplies, temperature and thermal shutdown, drive failures, firmware flashes, Smart Storage Energy Pack status, network status | Events recorded by iLO firmware: logins and login failures, virtual power events, server power outages and resets, log clearing, some configuration changes |
| Where | Information > Integrated Management Log | Information > iLO Event Log |
| Typical use | Diagnosing hardware faults | Auditing who did what in iLO |
Both logs overwrite their oldest entries when full. Both can be forwarded with remote syslog.
Step 1 — Open the IML
- Log in to iLO and click Information in the navigation tree.
- Click the Integrated Management Log tab. The newest event is at the top (sorted by ID).
Step 2 — Read the columns and severities
| Column | Meaning |
|---|---|
| Check box | Shown only for Critical or Caution events; used to mark them repaired. |
| ID | Event number in order of creation. A factory reset resets the counter. |
| Severity | Critical, Caution, Informational or Repaired (see below). |
| Class | Event type, for example UEFI, environment or system revision. |
| Description | What happened. |
| Last Update | When the latest event of this type occurred. [NOT SET] means iLO did not recognise the date and time. |
| Count | How many times it occurred. Less important repeated events are consolidated; important events get a new entry each time. |
| Category | For example Hardware, Firmware or Administration. |
- Critical — service loss or imminent service loss; immediate attention needed.
- Caution — significant, but not a performance degradation.
- Informational — background information.
- Repaired — corrective action has been taken.
Note: If iLO firmware has been rolled back, events written by the newer firmware may show UNKNOWN EVENT TYPE. HPE's fix is to update iLO to the latest supported version (or clear the log).
Step 3 — Filter and search
- Click the filter icon and choose a Severity, Class or Category, or a Last Update range. The count of matching events appears under the filter icon.
- Use the Time menu to show Show Default (UTC), Show Local Time (your browser's time) or Show ISO Time (UTC in ISO 8601).
- Click the search icon to search by date, event ID or description text.
- Reset filters returns to the default view.
Step 4 — Open an event and find the fix
Click an event to open its details pane:
- Initial Update — when the first event of this type occurred.
- Event Class and Event Code — unique identifiers, shown in hexadecimal.
- Learn More — a link to troubleshooting information for supported events.
- Recommended Action — a short fix. This text is static and does not change when the event is repaired.
Look up the class and code in HPE's Integrated Management Log messages guide, which has one page per message with Symptom, Cause and Action. For example, Gen11 DIMM Initialization Error is Error Class 0x0032, Error Code 0x0223; the action is to reseat the DIMMs in the identified channel during a maintenance window, update the System ROM, and contact support if it persists. SNMP traps carry the same class and code, so you can match a trap to its IML entry. If you open an HPE case, also download the Active Health System log for the same period.
Step 5 — Record the repair
Mark an entry as repaired
- Investigate and fix the problem first.
- On the Integrated Management Log tab, tick the check box next to the entry. Entries without a check box cannot be marked.
- Click the mark-as-repaired icon. The status changes to Repaired.
Add a maintenance note
Click the maintenance note icon, type the text (up to 227 bytes) and click OK. iLO adds an Informational entry with the class Maintenance, useful for recording upgrades, backups, part replacements or software installs.
Export to CSV
Click the CSV icon; the CSV Output window opens. Click Save. Export before you clear the log or hand a case to another engineer.
Clearing the IML
Warning: Clearing removes all previously logged IML events, including evidence HPE support may need. Save the IML to CSV and download the AHS log first. Clear only after the fault is resolved, or when HPE asks you to.
- Open Information > Integrated Management Log.
- Click the clear icon and confirm with Yes, clear. The clear action itself is recorded in the IML.
Frequently asked questions
Can I read the IML when the server is off?
Yes. iLO manages the IML, so it is available in the iLO web interface while the server is powered off.
Why do I see one entry with a high count instead of many entries?
iLO consolidates repeated less important events into one entry and updates Count and Last Update. Important events get a separate entry each time.
Checklist
- IML opened from Information > Integrated Management Log and filtered to Critical and Caution.
- Event class and code looked up in the IML messages guide; recommended action followed.
- Entry marked Repaired and a maintenance note added after the fix.
- IML exported to CSV and AHS log downloaded for any HPE case.
- Log cleared only after export, if at all.
Skyline can supply, configure and maintain Dell, HPE and Huawei servers under an annual maintenance contract (AMC). Contact us.
Comments
0 total · 0 threads