By the SNMP Monitoring team · Reviewed July 2026
The server can be perfect and still die because the room turned on it. Cooling fails and inlet temps climb; a pipe above the rack lets go; a UPS cooks and smoke drifts through the cold aisle. None of that shows up in CPU or interface counters — it comes from environmental sensors, and SNMP is how those probes report it. Drop a gateway in the room, hang temperature, humidity, leak, and smoke sensors off it, and the whole physical envelope becomes something you can poll and alert on. This page covers what environmental SNMP watches, how gateways expose it, and how to prioritise the alerts so a leak wakes someone up and a door-open doesn't.
Parent: monitoring.
What environmental SNMP can monitor
An environmental gateway turns physical conditions into SNMP objects. The common signals:
- Temperature & humidity — inlet/ambient °C and %RH, the daily bread of a server room
- Water / leak — rope or spot detectors under raised floors and near CRAC units
- Smoke / fire — early-warning smoke and heat sensors
- Door / motion — cabinet and room access, physical-security overlap
Each gets a dedicated page: temperature & humidity, water leak, smoke & fire, and door contact. Analogue signals (temp, humidity) give you a number; discrete signals (leak, smoke, door) give you a state.
How environmental gateways work
You don't usually poll a probe directly. The pattern is a chain: physical probes plug into an SNMP gateway (an appliance from vendors like APC NetBotz, HWg, or Sensaphone), and that gateway is what your manager polls. The gateway aggregates every attached sensor into a table and publishes it through the vendor's enterprise MIB under 1.3.6.1.4.1.
- Probes measure; the gateway digitises and hosts the SNMP agent.
- The gateway can also emit traps the instant a threshold trips — useful when a leak can't wait for the next poll.
- Some quantities (temperature in celsius, humidity as percentRH) follow the generic ENTITY-SENSOR-MIB pattern; most vendors also expose their own richer tree.
Because the layout is vendor-specific, the exact OID for "rack inlet temp" on an APC box isn't the same leaf as on an HWg unit. Learn the shape, then read the vendor MIB — see devices.
Sensor types & units
| Sensor | Reported as | Typical alert |
|---|---|---|
| Temperature | °C (often integer tenths) | High-temp threshold breached |
| Humidity | %RH | Too high (condensation) or too low (static) |
| Water / leak | Dry-contact state (integer) | Any leak = critical |
| Smoke / fire | Dry-contact state (integer) | Any trip = critical |
| Door / motion | Dry-contact state (integer) | Unexpected open / after-hours motion |
Note the split: analogue sensors need a threshold; discrete dry-contact sensors are booleans reported as integer states — one value means normal, the other means alarm. There's no averaging a leak.
Reading a probe with snmpwalk
Walk the gateway's enterprise subtree to see what's wired in. The arc is vendor-specific, so treat the objects below as illustrative of the pattern, not fixed OIDs:
snmpwalk -v2c -c <RO_string> <gateway> 1.3.6.1.4.1.<vendor>
enterprises.<vendor>.sensors.temp.1 = INTEGER: 226
enterprises.<vendor>.sensors.humidity.1 = INTEGER: 47
enterprises.<vendor>.sensors.leak.1 = INTEGER: 1
Read it against the vendor MIB: a temperature of 226 is almost certainly 22.6 °C (many probes report tenths), humidity 47 is 47 %RH, and a leak value of 1 is a discrete state — check the MIB to learn whether 1 is "normal/dry" or "alarm." That last point matters: never guess the polarity of a dry contact, or you'll invert your most important alert. Load the vendor MIB so names and states resolve instead of raw integers.
Building environmental alerts
Not every environmental event is equal. Rank them by how fast they destroy hardware:
- Smoke / fire — critical, page immediately, no delay window.
- Water / leak — critical, page immediately; water and power don't mix.
- High temperature — high priority; escalate if it climbs past a hard ceiling or keeps rising.
- Humidity out of band — medium; condensation and static are slow burns.
- Door / after-hours motion — informational to medium, depending on your security posture.
For the discrete criticals, prefer traps or a fast poll — a leak detected on a 15-minute cycle is a leak you found late. Route and de-duplicate these the same way as any other signal; see alerts for thresholds, hysteresis, and escalation.
Two more things worth wiring up. First, alert on the health of the probe itself — a gateway that stops answering is indistinguishable from a room that's fine, and that's the dangerous case. A simple reachability check on the gateway (poll its sysUpTime) catches a probe that's died or been unplugged. Second, give the analogue sensors a little hysteresis so a temperature hovering on the threshold doesn't flap the channel; a leak contact needs none, but an inlet temp wobbling by half a degree around a hard number will page you all night if you let a single sample decide. Set the temperature ceiling with headroom below the point where the hardware actually throttles, so the alert is a warning and not an obituary.
Sensor catalog
Go deeper on each:
Reference twins: humidity & airflow sensors, temperature sensors. Terms: glossary; full index: all sensors.
Frequently asked questions
Can SNMP monitor room temperature?
Yes — through an environmental probe wired to an SNMP gateway. The gateway reports temperature (usually in °C, often as integer tenths) and humidity (%RH) as pollable objects, either under its vendor enterprise MIB or via ENTITY-SENSOR-MIB patterns. Your manager polls the gateway, not the raw probe.
What is an SNMP environmental gateway?
An appliance that attached physical probes plug into, which digitises their readings and hosts the SNMP agent. Vendors include APC NetBotz, HWg, and Sensaphone. It aggregates every sensor into a table and publishes it under 1.3.6.1.4.1, and can also fire traps the moment a threshold trips.
Can SNMP detect water leaks?
Yes. Leak detectors are typically dry-contact sensors reported as an integer state — one value normal, the other alarm. Check the vendor MIB for the polarity, then alert on the alarm state as critical. Pair a fast poll or a trap so a leak isn't found on the next slow cycle.
Which vendors make SNMP probes?
Common environmental-gateway vendors include APC (NetBotz), HWg, and Sensaphone, among others. Each exposes its sensors through its own enterprise MIB under 1.3.6.1.4.1, so load the matching MIB rather than assuming OIDs carry across brands.
Key takeaways
- The room can kill the hardware; environmental probes make that risk pollable over SNMP.
- Probes feed a gateway (APC NetBotz, HWg, Sensaphone) that hosts the agent under
1.3.6.1.4.1. - Analogue sensors (temp °C, humidity %RH) need thresholds; dry-contact leak/smoke/door sensors are integer states.
- Exact probe OIDs are vendor-specific — read the vendor MIB; don't guess leaves or contact polarity.
- Prioritise alerts: smoke and leak are critical and can't wait for a slow poll — see alerts.
- Back the on-site poller with an external check so a room-wide incident still reaches you.