Network UPS Tools
Power Devices support
Table of Contents

Click here to see reports of other supported models from Tripp Lite.

Note

When a user reports that a variable/command is not right then it will be highlighted by a red underline.

Bad values/ranges/etc… will get a red dashed outline or red solid left border.

The accompanying explaining comment - if provided - will be emphasized through a red dotted border on the left.

2.7.4

Report #1 with driver snmp-ups (detailed comments available)

This device is known to work with driver snmp-ups.

You can grab a dummy-ups compliant .dev file to simulate this device clicking here.

Some more detailed comments are available after the "Known supported…" sections.

Known supported variables

This device is known to support the following variables (values are just examples):

battery.charge

100.00

battery.runtime

3300.00

battery.temperature

32.00

battery.voltage

56.00

device.mfr

Tripp Lite

device.model

SU2200RTXL2Ua

device.type

ups

driver.name

snmp-ups

driver.parameter.mibs

ietf

driver.parameter.pollfreq

15

driver.parameter.pollinterval

2

driver.parameter.port

x.x.x.x

driver.parameter.snmp_version

v2c

driver.parameter.synchronous

no

driver.version

2.7.4

driver.version.data

ietf MIB 1.5

driver.version.internal

0.97

input.bypass.frequency

59.90

input.bypass.phases

1.00

input.bypass.voltage

124.00

input.frequency

59.90

input.phases

1.00

input.transfer.high

150.00

input.transfer.low

65.00

input.voltage

124.00

input.voltage.nominal

120.00

output.current

0.20

output.frequency

59.90

output.phases

1.00

output.realpower

253.00

output.voltage

124.00

ups.beeper.status

muted

ups.firmware

19

ups.firmware.aux

12.06.0064

ups.load

150.00

this value should show as 15% load

ups.mfr

Tripp Lite

ups.model

SU2200RTXL2Ua

ups.status

OL

About this device

Tripp-Lite SNMPWEBCARD running version 12.06.0064.2791.2532

Device is a Tripp-Lite SU2200RTXL2Ua UPS.

At that version, it reports "ups.load" 10 times higher than real value, seems a mismatch of factors between firmware reading vs. IETF MIB RFC

Reported at: