snmp-ups: map more xppc readings for Phoenixtec UPS cards by vowstar · Pull Request #3492 · networkupstools/nut

vowstar · 2026-06-21T09:25:05Z

What this does

The xppc subdriver (XPPC-MIB, enterprise 935) currently maps only a handful of data points. This adds five readings that the cards already answer in the same subtree but that NUT was throwing away:

battery.runtime from .1.3.6.1.4.1.935.1.1.1.2.2.4.0
battery.voltage from .1.3.6.1.4.1.935.1.1.1.2.2.2.0
input.frequency from .1.3.6.1.4.1.935.1.1.1.3.2.4.0
output.voltage.nominal from .1.3.6.1.4.1.935.1.1.1.5.2.1.0
ups.firmware.aux from .1.3.6.1.4.1.935.1.1.1.1.2.4.0

XPPC_MIB_VERSION is bumped to 0.41 and a NEWS.adoc entry is added.

Why

battery.runtime is the big one. Before this change upsc reported no remaining runtime for these cards even though the value is right there in the MIB. The other four round out battery voltage, line frequency, rated output voltage and the agent firmware string.

Device and evidence

The card identifies as device.description "UPS Agent", device.mfr "Tripp Lite / Phoenixtec", sysObjectID .1.3.6.1.4.1.935.1.1.1. This is the Phoenixtec XPPC-MIB that the xppc subdriver already targets. The runtime OID maps to the same structural slot (.2.2.4.0) that cyberpower-mib.c reads as battery.runtime with scale 1.0 in seconds, which matched the observed value of about 83 minutes at light load.

This is the same family of card discussed in issue #2608, where the reporter had to give up because the hardware was no longer available to test against.

Verified on real hardware

$ upsc myups
battery.charge: 100
battery.runtime: 5760
battery.voltage: 81.10
device.mfr: Tripp Lite / Phoenixtec
device.type: ups
driver.name: snmp-ups
driver.parameter.mibs: xppc
driver.parameter.snmp_version: v2c
driver.version: 2.8.4
input.frequency: 49.90
input.voltage: 217.50
output.frequency: 49.90
output.voltage: 219.70
output.voltage.nominal: 220
ups.firmware.aux: 11105200-1.44.00
ups.load: 9
ups.status: OL
ups.temperature: 32.80

The five readings this change adds are battery.runtime, battery.voltage, input.frequency, output.voltage.nominal and ups.firmware.aux. All five show up above on a live card.

How to reproduce the dump

snmpwalk -v2c -c <community> <ups-ip> .1.3.6.1.4.1.935 > xppc-snmpwalk.log

I can attach the full walk if you want it for the DDL.

Closes part of #2608.

- add battery.runtime, battery.voltage and input.frequency readings - add output.voltage.nominal and ups.firmware.aux readings - bump XPPC_MIB_VERSION to 0.41 Signed-off-by: Huang Rui <vowstar@gmail.com>

github-actions · 2026-06-21T09:25:14Z

A ZIP file with standard source tarball and another tarball with pre-built docs for commit 20c732d is temporarily available: NUT-tarballs-PR-3492.zip.

vowstar · 2026-06-21T09:29:44Z

Full snmpwalk of the enterprise 935 tree from the same card, in case it is useful for the DDL. No system group is included, so there is no host name, location or contact. The community is shown as a placeholder.

sysObjectID .1.3.6.1.2.1.1.2.0 resolves to .1.3.6.1.4.1.935.1.1.1.

$ snmpwalk -v2c -c <community> -On <ups-ip> .1.3.6.1.4.1.935
.1.3.6.1.4.1.935.1.1.1.1.1.1.0 = ""
.1.3.6.1.4.1.935.1.1.1.1.1.2.0 = ""
.1.3.6.1.4.1.935.1.1.1.1.2.1.0 = ""
.1.3.6.1.4.1.935.1.1.1.1.2.2.0 = STRING: "0"
.1.3.6.1.4.1.935.1.1.1.1.2.3.0 = STRING: "0"
.1.3.6.1.4.1.935.1.1.1.1.2.4.0 = STRING: "11105200-1.44.00"
.1.3.6.1.4.1.935.1.1.1.2.1.1.0 = INTEGER: 2
.1.3.6.1.4.1.935.1.1.1.2.1.2.0 = INTEGER: 0
.1.3.6.1.4.1.935.1.1.1.2.1.3.0 = STRING: "2000/01/01"
.1.3.6.1.4.1.935.1.1.1.2.1.4.0 = STRING: "1000"
.1.3.6.1.4.1.935.1.1.1.2.2.1.0 = INTEGER: 100
.1.3.6.1.4.1.935.1.1.1.2.2.2.0 = INTEGER: 811
.1.3.6.1.4.1.935.1.1.1.2.2.3.0 = INTEGER: 328
.1.3.6.1.4.1.935.1.1.1.2.2.4.0 = INTEGER: 4980
.1.3.6.1.4.1.935.1.1.1.2.2.5.0 = INTEGER: 0
.1.3.6.1.4.1.935.1.1.1.2.2.6.0 = INTEGER: 138
.1.3.6.1.4.1.935.1.1.1.2.2.7.0 = INTEGER: 0
.1.3.6.1.4.1.935.1.1.1.2.2.8.0 = INTEGER: 4980
.1.3.6.1.4.1.935.1.1.1.3.1.1.0 = INTEGER: 1
.1.3.6.1.4.1.935.1.1.1.3.2.1.0 = INTEGER: 2190
.1.3.6.1.4.1.935.1.1.1.3.2.2.0 = INTEGER: 2190
.1.3.6.1.4.1.935.1.1.1.3.2.3.0 = INTEGER: 2190
.1.3.6.1.4.1.935.1.1.1.3.2.4.0 = INTEGER: 500
.1.3.6.1.4.1.935.1.1.1.3.2.5.0 = INTEGER: 1
.1.3.6.1.4.1.935.1.1.1.3.2.6.0 = INTEGER: 0
.1.3.6.1.4.1.935.1.1.1.4.1.1.0 = INTEGER: 2
.1.3.6.1.4.1.935.1.1.1.4.1.2.0 = INTEGER: 1
.1.3.6.1.4.1.935.1.1.1.4.2.1.0 = INTEGER: 2198
.1.3.6.1.4.1.935.1.1.1.4.2.2.0 = INTEGER: 499
.1.3.6.1.4.1.935.1.1.1.4.2.3.0 = INTEGER: 10
.1.3.6.1.4.1.935.1.1.1.4.2.4.0 = INTEGER: 30
.1.3.6.1.4.1.935.1.1.1.4.2.5.0 = INTEGER: 20
.1.3.6.1.4.1.935.1.1.1.4.2.6.0 = INTEGER: 15
.1.3.6.1.4.1.935.1.1.1.5.1.1.0 = INTEGER: 4
.1.3.6.1.4.1.935.1.1.1.5.2.1.0 = INTEGER: 2200
.1.3.6.1.4.1.935.1.1.1.5.2.2.0 = INTEGER: 0
.1.3.6.1.4.1.935.1.1.1.5.2.3.0 = INTEGER: 0
.1.3.6.1.4.1.935.1.1.1.5.2.4.0 = INTEGER: 3
.1.3.6.1.4.1.935.1.1.1.5.2.5.0 = INTEGER: 2147483647
.1.3.6.1.4.1.935.1.1.1.5.2.6.0 = INTEGER: 0
.1.3.6.1.4.1.935.1.1.1.5.2.7.0 = INTEGER: 1
.1.3.6.1.4.1.935.1.1.1.5.2.8.0 = INTEGER: 120
.1.3.6.1.4.1.935.1.1.1.5.2.9.0 = INTEGER: 60
.1.3.6.1.4.1.935.1.1.1.5.2.10.0 = INTEGER: 120
.1.3.6.1.4.1.935.1.1.1.5.2.11.0 = INTEGER: 2
.1.3.6.1.4.1.935.1.1.1.5.2.12.0 = INTEGER: 1
.1.3.6.1.4.1.935.1.1.1.6.1.1.0 = INTEGER: 1
.1.3.6.1.4.1.935.1.1.1.6.2.1.0 = INTEGER: 1
.1.3.6.1.4.1.935.1.1.1.6.2.2.0 = INTEGER: 1
.1.3.6.1.4.1.935.1.1.1.6.2.3.0 = INTEGER: 1
.1.3.6.1.4.1.935.1.1.1.6.2.4.0 = INTEGER: 1
.1.3.6.1.4.1.935.1.1.1.6.2.5.0 = INTEGER: 1
.1.3.6.1.4.1.935.1.1.1.6.2.6.0 = INTEGER: 1
.1.3.6.1.4.1.935.1.1.1.7.2.1.0 = INTEGER: 4
.1.3.6.1.4.1.935.1.1.1.7.2.2.0 = INTEGER: 1
.1.3.6.1.4.1.935.1.1.1.7.2.3.0 = INTEGER: 1
.1.3.6.1.4.1.935.1.1.1.7.2.4.0 = STRING: "2019/5/5"
.1.3.6.1.4.1.935.1.1.1.7.2.5.0 = INTEGER: 1
.1.3.6.1.4.1.935.1.1.1.7.2.6.0 = INTEGER: 1
.1.3.6.1.4.1.935.1.1.1.7.2.7.0 = INTEGER: 1
.1.3.6.1.4.1.935.1.1.1.7.2.8.0 = STRING: "2019/5/5"
.1.3.6.1.4.1.935.1.1.1.8.1.1.0 = INTEGER: 81
.1.3.6.1.4.1.935.1.1.1.8.1.2.0 = INTEGER: 100
.1.3.6.1.4.1.935.1.1.1.8.1.3.0 = INTEGER: 4980
.1.3.6.1.4.1.935.1.1.1.8.1.4.0 = INTEGER: 0
.1.3.6.1.4.1.935.1.1.1.8.1.5.0 = INTEGER: 328
.1.3.6.1.4.1.935.1.1.1.8.2.1.0 = INTEGER: 500
.1.3.6.1.4.1.935.1.1.1.8.2.2.0 = INTEGER: 2190
.1.3.6.1.4.1.935.1.1.1.8.2.3.0 = INTEGER: 0
.1.3.6.1.4.1.935.1.1.1.8.2.4.0 = INTEGER: 0
.1.3.6.1.4.1.935.1.1.1.8.2.5.0 = INTEGER: 0
.1.3.6.1.4.1.935.1.1.1.8.2.6.0 = INTEGER: 0
.1.3.6.1.4.1.935.1.1.1.8.2.7.0 = INTEGER: 0
.1.3.6.1.4.1.935.1.1.1.8.3.1.0 = INTEGER: 499
.1.3.6.1.4.1.935.1.1.1.8.3.2.0 = INTEGER: 2196
.1.3.6.1.4.1.935.1.1.1.8.3.3.0 = INTEGER: 0
.1.3.6.1.4.1.935.1.1.1.8.3.4.0 = INTEGER: 0
.1.3.6.1.4.1.935.1.1.1.8.3.5.0 = INTEGER: 80
.1.3.6.1.4.1.935.1.1.1.8.3.6.0 = INTEGER: 0
.1.3.6.1.4.1.935.1.1.1.8.3.7.0 = INTEGER: 0
.1.3.6.1.4.1.935.1.1.1.8.3.8.0 = INTEGER: 10
.1.3.6.1.4.1.935.1.1.1.8.3.9.0 = INTEGER: 0
.1.3.6.1.4.1.935.1.1.1.8.3.10.0 = INTEGER: 0
.1.3.6.1.4.1.935.1.1.1.8.3.11.0 = INTEGER: 20
.1.3.6.1.4.1.935.1.1.1.8.3.12.0 = INTEGER: 0
.1.3.6.1.4.1.935.1.1.1.8.3.13.0 = INTEGER: 0
.1.3.6.1.4.1.935.1.1.1.8.3.14.0 = INTEGER: 20
.1.3.6.1.4.1.935.1.1.1.8.3.15.0 = INTEGER: 0
.1.3.6.1.4.1.935.1.1.1.8.3.16.0 = INTEGER: 0
.1.3.6.1.4.1.935.1.1.1.8.4.1.0 = INTEGER: 500
.1.3.6.1.4.1.935.1.1.1.8.4.2.0 = INTEGER: 2181
.1.3.6.1.4.1.935.1.1.1.8.4.3.0 = INTEGER: 0
.1.3.6.1.4.1.935.1.1.1.8.4.4.0 = INTEGER: 0
.1.3.6.1.4.1.935.1.1.1.8.4.5.0 = INTEGER: 0
.1.3.6.1.4.1.935.1.1.1.8.4.6.0 = INTEGER: 0
.1.3.6.1.4.1.935.1.1.1.8.4.7.0 = INTEGER: 0
.1.3.6.1.4.1.935.1.1.1.8.5.1.0 = INTEGER: 16
.1.3.6.1.4.1.935.1.1.1.8.5.2.0 = INTEGER: 16
.1.3.6.1.4.1.935.1.1.1.8.5.3.0 = INTEGER: 16
.1.3.6.1.4.1.935.1.1.1.8.5.4.0 = INTEGER: 2
.1.3.6.1.4.1.935.1.1.1.8.5.5.0 = INTEGER: 5
.1.3.6.1.4.1.935.1.1.1.8.5.6.0 = INTEGER: 7
.1.3.6.1.4.1.935.1.1.1.8.5.7.0 = INTEGER: 16
.1.3.6.1.4.1.935.1.1.1.8.6.1.0 = INTEGER: 16
.1.3.6.1.4.1.935.1.1.1.8.6.2.0 = INTEGER: 9
.1.3.6.1.4.1.935.1.1.1.8.6.3.0 = INTEGER: 10
.1.3.6.1.4.1.935.1.1.1.8.6.4.0 = INTEGER: 12
.1.3.6.1.4.1.935.1.1.1.8.6.5.0 = INTEGER: 14
.1.3.6.1.4.1.935.1.1.1.8.7.1.0 = INTEGER: 16
.1.3.6.1.4.1.935.1.1.1.8.7.2.0 = INTEGER: 16
.1.3.6.1.4.1.935.1.1.1.8.7.3.0 = INTEGER: 16
.1.3.6.1.4.1.935.1.1.1.8.7.4.0 = INTEGER: 16
.1.3.6.1.4.1.935.1.1.1.8.7.5.0 = INTEGER: 16
.1.3.6.1.4.1.935.1.1.1.8.7.6.0 = INTEGER: 16
.1.3.6.1.4.1.935.1.1.1.8.7.7.0 = INTEGER: 16
.1.3.6.1.4.1.935.1.1.1.8.8.1.0 = STRING: "220"
.1.3.6.1.4.1.935.1.1.1.8.8.2.0 = INTEGER: 50
.1.3.6.1.4.1.935.1.1.1.8.8.3.0 = STRING: "220"
.1.3.6.1.4.1.935.1.1.1.8.8.4.0 = INTEGER: 50
.1.3.6.1.4.1.935.1.1.1.8.8.5.0 = STRING: "220"
.1.3.6.1.4.1.935.1.1.1.8.8.6.0 = INTEGER: 50
.1.3.6.1.4.1.935.1.1.1.8.8.7.0 = INTEGER: 0
.1.3.6.1.4.1.935.1.1.1.8.8.8.0 = STRING: "0"
.1.3.6.1.4.1.935.1.1.1.9.1.1.0 = INTEGER: 0
.1.3.6.1.4.1.935.1.1.1.9.1.2.0 = INTEGER: 0
.1.3.6.1.4.1.935.1.1.1.9.1.3.0 = INTEGER: 1
.1.3.6.1.4.1.935.1.1.1.9.1.4.0 = INTEGER: 1
.1.3.6.1.4.1.935.1.1.1.9.1.5.0 = INTEGER: 1
.1.3.6.1.4.1.935.1.1.1.9.1.6.0 = INTEGER: 1
.1.3.6.1.4.1.935.1.1.1.9.1.7.0 = INTEGER: 1
.1.3.6.1.4.1.935.1.1.1.9.1.8.0 = INTEGER: 1
.1.3.6.1.4.1.935.1.1.1.9.1.9.0 = INTEGER: 1
.1.3.6.1.4.1.935.1.1.1.9.1.10.0 = INTEGER: 1
.1.3.6.1.4.1.935.1.1.1.9.1.11.0 = INTEGER: 1
.1.3.6.1.4.1.935.1.1.1.9.2.1.0 = INTEGER: 500
.1.3.6.1.4.1.935.1.1.1.9.2.2.0 = INTEGER: 200
.1.3.6.1.4.1.935.1.1.1.9.2.3.0 = INTEGER: 900
.1.3.6.1.4.1.935.1.1.1.9.2.4.0 = INTEGER: 200
.1.3.6.1.4.1.935.2.1.1.0 = INTEGER: 0

AppVeyorBot · 2026-06-21T09:49:59Z

❌ Build nut 2.8.5.4847-master failed (commit 36ab3eb74c by @vowstar)

artifacts (if any)

AppVeyorBot · 2026-06-21T09:49:59Z

❌ Build nut 2.8.5.4847-master failed (commit 36ab3eb74c by @vowstar)

jimklimov · 2026-06-21T10:31:50Z

Thanks! The DDL-ready upsc et al data dump (or PR there https://github.com/networkupstools/nut-ddl/) would be most welcome too.

PR looks good, waiting for CI to not complain about anything :)

AppVeyorBot · 2026-06-21T10:33:52Z

✅ Build nut 2.8.5.4848-master completed (commit c6b0c6847f by @vowstar)

artifacts
A 7-zip archive with built NUT for Windows debug binaries is temporarily available: NUT-for-Windows-x86_64-SNAPSHOT-2.8.5.4848-master.7z

AppVeyorBot · 2026-06-21T10:33:53Z

✅ Build nut 2.8.5.4848-master completed (commit c6b0c6847f by @vowstar)

vowstar · 2026-06-21T15:56:49Z

Thanks for the pointer. Posted it as networkupstools/nut-ddl#62, with IP, community, host name and location stripped. Can add the full enterprise-935 snmpwalk there too if it is useful.

jimklimov · 2026-06-21T18:41:02Z

Maybe that would make sense. I don't think there's precedent about publishing SNMP walks though, so they probably can go as a structured DDL file comment block for now.

vowstar · 2026-06-21T23:48:13Z

Makes sense. Folded the enterprise-935 walk into the .dev as a DEVICE:COMMENT-BLOCK rather than a separate file, so nut-ddl#62 now carries both the upsc data and the raw OIDs in one place for cross-checking the mappings.

feat(snmp-ups): map more xppc readings for Phoenixtec UPS cards

20c732d

- add battery.runtime, battery.voltage and input.frequency readings - add output.voltage.nominal and ups.firmware.aux readings - bump XPPC_MIB_VERSION to 0.41 Signed-off-by: Huang Rui <vowstar@gmail.com>

vowstar force-pushed the xppc-mib-runtime-readings branch from 9d1b9a9 to 20c732d Compare June 21, 2026 09:38

jimklimov added this to the 2.8.6 milestone Jun 21, 2026

jimklimov added the ready / gonna merge The PR is in final cycles leading to merge unless someone logs an objection before we hit the button label Jun 21, 2026

vowstar mentioned this pull request Jun 21, 2026

Add Tripp Lite / Phoenixtec xppc SNMP card dump (snmp-ups, NUT 2.8.4) networkupstools/nut-ddl#62

Open

11 tasks

jimklimov merged commit 138c70c into networkupstools:master Jun 28, 2026
107 of 114 checks passed

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Uh oh!

snmp-ups: map more xppc readings for Phoenixtec UPS cards#3492

snmp-ups: map more xppc readings for Phoenixtec UPS cards#3492
jimklimov merged 1 commit into
networkupstools:masterfrom
vowstar:xppc-mib-runtime-readings

vowstar commented Jun 21, 2026 •

edited

Loading

Uh oh!

github-actions Bot commented Jun 21, 2026 •

edited

Loading

Uh oh!

vowstar commented Jun 21, 2026

Uh oh!

AppVeyorBot commented Jun 21, 2026

Uh oh!

AppVeyorBot commented Jun 21, 2026

Uh oh!

jimklimov commented Jun 21, 2026 •

edited

Loading

Uh oh!

AppVeyorBot commented Jun 21, 2026

Uh oh!

AppVeyorBot commented Jun 21, 2026

Uh oh!

vowstar commented Jun 21, 2026

Uh oh!

jimklimov commented Jun 21, 2026

Uh oh!

vowstar commented Jun 21, 2026

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

Uh oh!

Uh oh!

Conversation

vowstar commented Jun 21, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

What this does

Why

Device and evidence

Verified on real hardware

How to reproduce the dump

Uh oh!

github-actions Bot commented Jun 21, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

vowstar commented Jun 21, 2026

Uh oh!

AppVeyorBot commented Jun 21, 2026

Uh oh!

AppVeyorBot commented Jun 21, 2026

Uh oh!

jimklimov commented Jun 21, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

AppVeyorBot commented Jun 21, 2026

Uh oh!

AppVeyorBot commented Jun 21, 2026

Uh oh!

vowstar commented Jun 21, 2026

Uh oh!

jimklimov commented Jun 21, 2026

Uh oh!

vowstar commented Jun 21, 2026

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

vowstar commented Jun 21, 2026 •

edited

Loading

github-actions Bot commented Jun 21, 2026 •

edited

Loading

jimklimov commented Jun 21, 2026 •

edited

Loading