What is NodeCare?
NodeCare is the hardware early warning in PeakNode. 22 rules evaluate vendor values and the history of every component and report, for example, a drive that will soon be full if the trend continues, a GPU that runs hotter at the same power, or rising memory errors.
Does NodeCare cost extra?
No. NodeCare is included in every PeakNode plan, including the free Proof of Concept. There, because of the 14-day data retention, the temperature comparison with its own history is not available; the other rules apply.
Does NodeCare detect when a GPU will fail?
No. NodeCare gives no failure probability and no remaining lifetime. It reports what the driver and the kernel log say about the card and how its values change compared with its own history. Only the fill level of drives is projected, with the calculation shown.
How does NodeCare calculate when a drive will be full?
With a linear projection over the daily means of usage for the last 30 days, once 7 days of data are available and only with an increase of 0.02 percentage points per day or more. Full within 30 days at most means “Plan maintenance”, within up to 12 months “Watch”. The thresholds of 85% and 95% apply immediately, without a learning phase.
When does NodeCare notify, and when not?
“Act now” goes immediately to the server monitor’s channels, “Plan maintenance” once a day at 08:00 and only for new items. “Watch” does not create a message. GPU items are only sent if “Alert on hardware events” is switched on for the server monitor. If hardware health reports the same event, only its message is sent.
What is in the warranty claim (RMA) record?
Server monitor, GPU, model, UUID, PCI address and driver version, the ECC counters since the driver was loaded and over the lifetime, the state of remapped rows, the Xid events of the last 30 days and the corrected ECC errors per day. You enter the serial number by hand; the agent does not provide it.
Which hardware does NodeCare not cover?
NodeCare evaluates memory errors (EDAC), drive health and wear (SMART), power supplies and fans (BMC) and the CPU temperature as soon as the Linux agent version 11 or later provides them. If a system has no such source, the rule remains without data. On Windows the agent provides neither ECC nor PCIe nor Xid, so the related rules remain without data there. The temperature comparison needs 14 days of history and a data retention of at least 21 days. NodeCare does not replace a diagnosis by the vendor.
How do I read SMART values on a server?
On Linux with smartctl -a from the smartmontools package, for NVMe drives also with nvme smart-log. The PeakNode agent version 11 or later reads the values every 30 minutes through smartctl, or nvme-cli as a fallback, without waking sleeping drives. NodeCare evaluates health, wear, spare and media errors from them. If these tools or python3 are missing, the drive rules stay without data; the agent installs nothing.
Does NodeCare read IPMI or BMC sensors?
Yes, if ipmitool is installed and the server’s BMC is reachable over IPMI. The Linux agent version 11 or later reads power supplies, fans, inlet temperature and power every 3 minutes, and NodeCare reports a failed power supply or fan as “Act now”. Without a BMC, fan speeds come from hwmon. The HGX server page shows how this looks on an 8-GPU system.