Current APC profiles
The repository includes the apc-powernet UPS profile for PowerNet NMC AP963x/AP964x cards. Separate APC profiles cover ATS, ePDU, environmental-monitor, and rPDU2 device families.
- Profile matching by sysObjectID
- Encrypted reusable SNMP credentials
- Read-only operator-initiated discovery
Signals mapped by the profile
The UPS profile inherits the RFC 1628 battery, runtime, charge, voltage, and temperature baseline. It adds PowerNet output states, strong serial identity, battery self-test results and date, transfer reason, battery-pack counts, last-replacement text, and selected degradation faults.
- Readable normalized states
- Fleet histories and CSV export
- Battery and fault context where exposed
Verification boundary
The PowerNet profile remains verified:false. Firmware-dependent output-state flags, live transfer behaviour, and the vendor shutdown SET path still need a walk and action test on real APC hardware.
- RFC 1628 baseline verified
- Vendor profile hardware proof pending
- No vendor SET claim without bench approval
Shutdown readiness
For controlled shutdown, MayaUPS uses the Observe → Dry-run → Armed safety sequence. Policies can be evaluated before action, dry-run proof is recorded before arming, and live shutdown can use SNMP-SET for UPS shutdown plus an mTLS host agent for ordered host sequences. These live-action paths still require final real-hardware bench approval before general release.
- Observe first
- Dry-run proof before arming
- SNMP-SET and mTLS host-agent path
Operations after polling
MayaUPS brings the available telemetry into one bilingual fleet view with 24 h / 7 d / 30 d histories, CSV export, battery service-life planning, and grouped SMTP email or JSON webhook notifications. That gives mixed sites one operating process while keeping device-specific evidence boundaries visible.