How does Sensaka monitor HPE iLO without an agent?

Sensaka DCOS connects to each ProLiant server's iLO over the management network using the Redfish API. It reads sensors, the Integrated Management Log, and component health directly from iLO, so no OneView or OS agent is required on the host.

Does it work with iLO 5 and iLO 6?

Yes. Sensaka uses Redfish on iLO 5 and iLO 6, covering ProLiant Gen10, Gen10 Plus, and Gen11 servers, with consistent coverage across mixed HPE fleets.

Do I need an iLO Advanced license?

Core hardware health and Redfish telemetry are available without advanced features; certain capabilities such as remote console depend on iLO licensing. Sensaka reads the health, sensor, and event data the controller exposes and surfaces it in one view.

What HPE hardware faults can it detect?

Power supply degradation and redundancy loss, fan failure and thermal issues, DIMM memory errors, Smart Array controller and disk faults, and CPU or system board events, along with iLO IML entries.

Which Sensaka product covers HPE iLO monitoring?

DCOS provides agentless out-of-band monitoring for HPE hardware. It feeds the iDCOS unified platform, and SmartBSM adds AIOps and business service mapping so iLO faults connect to service impact.

Solutions · Out-of-Band Hardware Monitoring

HPE iLO Monitoring, Agentless Health for ProLiant Servers

HPE iLO is one of the most capable server management controllers, but iLO Advanced licensing and the OneView console keep that visibility inside the HPE ecosystem. iLO monitoring with Sensaka reads hardware health agentlessly and unifies it with the rest of a mixed fleet.

Collection runs over the management network through the Redfish API, so power, thermal, and memory faults surface early and ProLiant nodes stay visible during a crash, hang, or power event, with no OS agent required.

Coverage

What Sensaka Monitors on HPE iLO

iLO (Integrated Lights-Out) is the HPE baseboard management controller. Sensaka DCOS connects to it agentlessly over Redfish (and IPMI where applicable) and reads hardware health directly from the controller.

Power supply health, redundancy, and power readings

Fan speed, fan failure, and thermal status

Inlet and component temperatures

Memory (DIMM) errors and status

Smart Array controller and physical disk health

CPU and system board status

iLO Integrated Management Log (IML) events

iLO reachability and overall server health summary

Why Out-of-Band

Hardware Visibility That Survives an OS Failure

OS-independent visibility

The controller runs on dedicated management hardware, so health data keeps flowing when the OS crashes, hangs, or loses its production network.

Component-level faults

CPU, DIMM correctable and uncorrectable errors, PSU state, fan speed and failure, RAID and disk health, and inlet temperature.

One view across vendors

Normalized into the same model as the rest of your fleet, so this hardware does not need its own separate console.

Remote operations

Power cycle, remote console, and batch actions over the management network for lights-out sites and remote troubleshooting.

Firmware & change context

Firmware levels and configuration baselines tracked alongside alerts, connecting hardware change to incidents and audit needs.

Service impact mapping

Faults related to the business services that depend on the node, so critical hardware is prioritized accordingly.

HPE Specifics

Notes for Monitoring HPE iLO at Scale

Uses the Redfish API on iLO 5 and iLO 6 for current ProLiant Gen10, Gen10 Plus, and Gen11 servers.

Reads the iLO Integrated Management Log (IML) so historical hardware events stay attached to each node.

Avoids per-host OneView or Insight agents by collecting directly from the controller.

Normalizes HPE Smart Array and sensor data into the same model as Dell, Lenovo, Huawei, and Supermicro hardware.

HPE iLO is one layer of a mixed estate. The same approach powers multi-vendor BMC monitoring across your whole fleet, feeding the unified iDCOS platform and SmartBSM for business service impact.

Protocol references: Redfish (DMTF) and the IPMI specification.

Other vendor controllers: Dell iDRAC, Huawei iBMC, Lenovo XCC, Supermicro IPMI. See also out-of-band monitoring and multi-vendor hardware monitoring.

FAQ

HPE iLO Monitoring, Answered

Get started

Monitor HPE Hardware Without an Agent

See how DCOS reads iLO health agentlessly and folds it into one view across your whole multi-vendor fleet.