Power and servers

The Power and servers tab shows what keeps your gear running: UPSes, PDUs and servers read through their management controllers. It appears when at least one UPS, PDU or Redfish source is set up, and carries a count of its current alerts like every tab.

Each UPS, PDU and server gets its own panel, named after it.

UPS

From the UPS's network card, over UPS-MIB. First where its power comes from (mains, battery or bypass) and how long it has been on battery, then the runtime left at this load, the battery's state, charge, voltage and temperature, the load, the input voltage, and any alarms the UPS raises.

See UPS for setting it up and what alerts.

PDUs

New in the next release

This is on the dev and qa builds now, and in the next release.

From the PDU's network card, over its maker's MIB (APC, Raritan or Eaton). Its draw in amps against its rating, the load as a share of that, its power, each bank's current, and every outlet: its name, whether it's on, and what it draws. The count of outlets drawing nothing is what capacity planning treats as free.

See PDUs for setting it up and what alerts.

Servers

From each server's BMC over Redfish (Dell iDRAC, HPE iLO, Lenovo XCC, Supermicro and others). The BMC's own verdict on the server, power state, processors, memory and host name first, then temperatures against the BMC's own lines, fans, power supplies with their redundancy, and drives with their predicted life.

See Servers (Redfish) for setting it up and what alerts.

How capacity planning uses them

When capacity planning checks adding a host like an existing one, it reads that host's peak draw from its BMC, then says what one more does to the UPS that feeds its rack (load and runtime) and to the PDU its supplies are plugged into (free outlets and load).