Solutions · Out-of-Band Hardware Monitoring

    Lenovo XCC Monitoring, Agentless Health for ThinkSystem Servers

    Lenovo's XClarity Controller (XCC) exposes detailed hardware health for ThinkSystem servers, but XClarity Administrator is another management plane to operate on its own. XCC monitoring with Sensaka reads that telemetry agentlessly and unifies Lenovo hardware with the rest of the fleet.

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

    Coverage

    What Sensaka Monitors on Lenovo XCC

    XCC (XClarity Controller) is the Lenovo baseboard management controller. Sensaka DCOS connects to it agentlessly over Redfish and IPMI 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
    DIMM memory errors and status
    RAID controller and physical disk health
    CPU and system board status
    XCC event log entries
    XCC reachability and overall 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.

    Lenovo Specifics

    Notes for Monitoring Lenovo XCC at Scale

    Uses the Redfish API on the XClarity Controller across current ThinkSystem generations.
    Avoids standing up XClarity Administrator agents on every host by reading directly from XCC.
    Fits estates where Lenovo runs alongside other vendors and one operational view is required.
    Normalizes Lenovo sensors into the same model as Dell, HPE, Huawei, and Supermicro hardware.

    Lenovo XCC 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.

    FAQ

    Lenovo XCC Monitoring, Answered

    Get started

    Monitor Lenovo Hardware Without an Agent

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