Current CyberPower profiles
The repository includes the cyberpower profile for carded enterprise OL and PR units using RMCARD205/305 network-management cards. USB-HID direct attach is a separate agent path and does not imply that every consumer model has been verified.
- Profile matching by sysObjectID
- Encrypted reusable SNMP credentials
- Read-only operator-initiated discovery
Signals mapped by the profile
The network profile inherits RFC 1628 and adds CyberPower output states, strong serial identity, battery status and charge, and diagnostic-test results. It distinguishes online, on-battery, boost, bypass, buck, overload, and off states.
- Readable normalized states
- Fleet histories and CSV export
- Battery and fault context where exposed
Verification boundary
The CyberPower profile remains verified:false. A live RMCARD walk and transfer test are pending, and the shutdown path requires special confirmation because its cancel value is -1 rather than zero.
- 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.