Skip to content

Reading IPMI sensor thresholds correctly

Dedicated Servers by kat_fold 3 replies 400 views
8 #1

Hey folks

Pinning this briefly since IPMI misreads cause unnecessary panic and unneeded datacenter trips. Good reference thread.

~be kind or be gone~
#2

The thresholds they hide in plain sight—critical is not the end—non-recoverable is the true death—sensor reading is it

Your grafana alerts cry wolf for critical—visit only for non-recoverable—this the poets of infrastructure know ji

#3

Actually, the IPMI spec (v2.0 rev1.1 section 36.2) defines this precisely: critical means (operation outside limits (possible damage (but recoverable if condition returns to normal))) whereas non-recoverable means (hardware damage (likely permanent (requires physical intervention)))

I have (like (many others)) automated this with ipmitool sensor list parsed through awk into node_exporter textfile collector

  • Critical = page only
  • Non-recoverable = datacenter visit trigger
  • Upper non-recoverable > upper critical > upper non-critical

The common mistake is (reading threshold tables backwards (or ignoring the bitmask for threshold type))

#4

Non-recoverable is the one that actually matters.

Post a reply

You need an account to reply. Log in or register to join the conversation.

Post reply Preview Save draft