EXPLAINER
UPS SNMP monitoring reads a network-management card on the LAN. The card exposes status, metrics, and alarms through standard and vendor MIBs, and the monitoring software turns that raw telemetry into states an operator can use.
MayaUPS supports SNMP v1, v2c, and v3 USM. SNMPv3 adds authentication and privacy, and fails closed without credentials. That matters for operators who need stronger credential handling than a shared community string while still supporting older devices on the same site.
Community strings and SNMPv3 USM credentials are stored as sealed encrypted profiles and reused across devices by name. That lets a site avoid repeatedly typing secrets into individual device records while still testing each device connection before relying on the telemetry.
Discovery is gentle, read-only, bounded to a /24, and initiated by the operator. It is never automatic. MayaUPS can use sysObjectID to match a vendor profile when one is available, while RFC-1628 provides the standards-based baseline for UPS devices that expose the standard MIB.
A poll can return status, charge, runtime remaining, load, input and output voltage, temperature, and alarm data. MayaUPS normalizes those signals into readable fleet states and histories so an operator sees On battery, Replace battery, Overtemperature, runtime trends, and site-level summaries instead of raw object identifiers.
The standard MIB is not the whole story. Where manufacturers expose extra bitmasks or flags, vendor profiles can add more detailed fault decoding. The current vendor-specific profiles are not yet marked as hardware verified, so the site does not imply that every brand-specific code has been bench confirmed.
SNMP monitoring feeds the rest of the workflow: grouped SMTP alerts, battery service-life forecasting, CSV export, and shutdown readiness. The operator can watch the site in Observe mode, prove policies in Dry-run, and only then move toward Armed shutdown when the evidence supports it.