Click here to see reports of other supported models from APC.
|
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):
|
ambient.1.humidity.alarm.high
|
|
|
ambient.1.humidity.alarm.low
|
|
|
ambient.1.temperature.alarm.high
|
|
|
ambient.1.temperature.alarm.low
|
|
|
battery.charge
|
|
|
battery.charge.restart
|
|
|
battery.current
|
|
|
battery.date
|
|
|
battery.packs
|
|
|
battery.packs.bad
|
|
|
battery.runtime
|
|
|
battery.runtime.low
|
|
|
battery.voltage
|
|
|
battery.voltage.nominal
|
|
|
device.mfr
|
|
|
device.model
|
|
|
device.serial
|
|
|
device.type
|
|
|
driver.name
|
|
|
driver.parameter.pollfreq
|
|
|
driver.parameter.pollinterval
|
|
|
driver.parameter.port
|
|
|
driver.parameter.snmp_retries
|
|
|
driver.parameter.snmp_timeout
|
|
|
driver.parameter.snmp_version
|
|
|
driver.parameter.synchronous
|
|
|
driver.version
|
|
|
driver.version.data
|
|
|
driver.version.internal
|
|
|
input.frequency
|
|
|
input.sensitivity
|
|
|
input.transfer.high
|
|
|
input.transfer.low
|
|
|
input.transfer.reason
|
|
|
input.voltage
|
|
|
input.voltage.maximum
|
|
|
input.voltage.minimum
|
|
|
output.current
|
|
|
output.frequency
|
|
|
output.voltage
|
|
|
output.voltage.nominal
|
|
|
ups.delay.shutdown
|
|
|
ups.delay.start
|
|
|
ups.firmware
|
|
|
ups.id
|
|
|
ups.load
|
|
|
ups.mfr
|
|
|
ups.mfr.date
|
|
|
ups.model
|
|
|
ups.serial
|
|
|
ups.status
|
|
|
ups.temperature
|
|
|
ups.test.date
|
|
|
ups.test.result
|
|
About this device
Reported at:
Further system data or configuration example:
An APC SUA1000 UPS (reports itself as Smart-UPS 1000) connected via SNMPv1
does not have the problem described in this ticket: Battery Runtime matches
on UPS and NUT monitoring, and equals `70680.00` here.Report #2 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):
|
ambient.1.humidity.alarm.high
|
|
|
ambient.1.humidity.alarm.low
|
|
|
ambient.1.temperature.alarm.high
|
|
|
ambient.1.temperature.alarm.low
|
|
|
battery.charge
|
|
|
battery.charge.restart
|
|
|
battery.current
|
|
|
battery.date
|
|
|
battery.packs
|
|
|
battery.packs.bad
|
|
|
battery.runtime
|
|
|
battery.runtime.low
|
|
|
battery.voltage
|
|
|
battery.voltage.nominal
|
|
|
device.mfr
|
|
|
device.model
|
|
|
device.serial
|
|
|
device.type
|
|
|
driver.name
|
|
|
driver.parameter.pollfreq
|
|
|
driver.parameter.pollinterval
|
|
|
driver.parameter.port
|
|
|
driver.parameter.snmp_version
|
|
|
driver.parameter.synchronous
|
|
|
driver.version
|
|
|
driver.version.data
|
|
|
driver.version.internal
|
|
|
input.frequency
|
|
|
input.sensitivity
|
|
|
input.transfer.high
|
|
|
input.transfer.low
|
|
|
input.transfer.reason
|
|
|
input.voltage
|
|
|
input.voltage.maximum
|
|
|
input.voltage.minimum
|
|
|
output.current
|
|
|
output.frequency
|
|
|
output.voltage
|
|
|
output.voltage.nominal
|
|
|
ups.delay.shutdown
|
|
|
ups.delay.start
|
|
|
ups.firmware
|
|
|
ups.id
|
|
|
ups.load
|
|
|
ups.mfr
|
|
|
ups.mfr.date
|
|
|
ups.model
|
|
|
ups.serial
|
|
|
ups.status
|
|
|
ups.temperature
|
|
|
ups.test.date
|
|
|
ups.test.result
|
|
About this device
Reported at:
Further system data or configuration example:
An APC SU-1000 UPS with AP9617 card (reports itself as Smart-UPS 1000)
connected via SNMPv3, tested with a NUT v2.8.0 candidate code base.
A number of shutdown attempt tests were done, returning SNMP errors like:[su1000] nut_snmp_set: can’t set .1.3.6.1.4.1.318.1.1.1.6.1.1.0: Error in packet: wrongType (The set datatype does not match the data type the agent expects)
...or (using NUT v2.7.4 from Fedora 33):[su1000] nut_snmp_set: can’t set .1.3.6.1.4.1.318.1.1.1.6.1.1.0: Error in packet: (genError) A general failure occured
...and those problems can be reproduced with `snmpset` program, as detailed
in the https://github.com/networkupstools/nut/issues/953 NUT ticket.
Similar problems were reported with an APC SmartUPS 750 and an AP9631 card.2.6.0
Report #1 with driver usbhid-ups (detailed comments available)
This device is known to work with driver usbhid-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
|
|
|
battery.charge.low
|
|
|
battery.charge.warning
|
|
|
battery.mfr.date
|
|
|
battery.runtime
|
|
|
battery.runtime.low
|
|
|
battery.temperature
|
|
|
battery.type
|
|
|
battery.voltage
|
|
|
battery.voltage.nominal
|
|
|
device.mfr
|
|
|
device.model
|
|
|
device.serial
|
|
|
device.type
|
|
|
driver.name
|
|
|
driver.parameter.pollfreq
|
|
|
driver.parameter.pollinterval
|
|
|
driver.parameter.port
|
|
|
driver.version
|
|
|
driver.version.data
|
|
|
driver.version.internal
|
|
|
input.sensitivity
|
|
|
input.voltage
|
|
|
output.voltage
|
|
|
output.voltage.nominal
|
|
|
ups.beeper.status
|
|
|
ups.delay.shutdown
|
|
|
ups.delay.start
|
|
|
ups.firmware
|
|
|
ups.firmware.aux
|
|
|
ups.load
|
|
|
ups.mfr
|
|
|
ups.mfr.date
|
|
|
ups.model
|
|
|
ups.productid
|
|
|
ups.serial
|
|
|
ups.status
|
|
|
ups.test.result
|
|
|
ups.timer.reboot
|
|
|
ups.timer.shutdown
|
|
|
ups.timer.start
|
|
|
ups.vendorid
|
|
Known supported commands
This device is known to support the following NUT’s instant commands:
-
beeper.disable
-
beeper.enable
-
beeper.mute
-
beeper.off
-
beeper.on
-
load.off
-
load.off.delay
-
load.on
-
load.on.delay
-
shutdown.reboot
-
shutdown.return
-
shutdown.stayoff
-
shutdown.stop
-
test.battery.start.deep
-
test.battery.start.quick
-
test.battery.stop
-
test.panel.start
-
test.panel.stop
About this device
Reported at:
2.4.1
Report #1 with driver usbhid-ups (detailed comments available)
This device is known to work with driver usbhid-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
|
|
|
battery.charge.low
|
|
|
battery.charge.warning
|
|
|
battery.mfr.date
|
|
|
battery.runtime
|
|
|
battery.runtime.low
|
|
|
battery.temperature
|
|
|
battery.type
|
|
|
battery.voltage
|
|
|
battery.voltage.nominal
|
|
|
driver.name
|
|
|
driver.parameter.pollfreq
|
|
|
driver.parameter.pollinterval
|
|
|
driver.parameter.port
|
|
|
driver.version
|
|
|
driver.version.data
|
|
|
driver.version.internal
|
|
|
input.voltage
|
|
|
output.voltage
|
|
|
output.voltage.nominal
|
|
|
ups.beeper.status
|
|
|
ups.delay.shutdown
|
|
|
ups.firmware
|
|
|
ups.firmware.aux
|
|
|
ups.load
|
|
|
ups.mfr
|
|
|
ups.mfr.date
|
|
|
ups.model
|
|
|
ups.productid
|
|
|
ups.serial
|
|
|
ups.status
|
|
|
ups.test.result
|
|
|
ups.timer.reboot
|
|
|
ups.timer.shutdown
|
|
|
ups.vendorid
|
|
Known supported commands
This device is known to support the following NUT’s instant commands:
-
beeper.disable
-
beeper.enable
-
beeper.mute
-
beeper.off
-
beeper.on
-
load.off
-
load.off.delay
-
load.on
-
load.on.delay
-
shutdown.reboot
-
shutdown.return
-
shutdown.stayoff
-
shutdown.stop
-
test.battery.start.deep
-
test.battery.start.quick
-
test.battery.stop
-
test.panel.start
-
test.panel.stop
About this device
Reported at:
Report #2 with driver usbhid-ups (detailed comments available)
This device is known to work with driver usbhid-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
|
|
|
battery.charge.low
|
|
|
battery.charge.warning
|
|
|
battery.mfr.date
|
|
|
battery.runtime
|
|
|
battery.runtime.low
|
|
|
battery.temperature
|
|
|
battery.type
|
|
|
battery.voltage
|
|
|
battery.voltage.nominal
|
|
|
driver.name
|
|
|
driver.parameter.pollfreq
|
|
|
driver.parameter.pollinterval
|
|
|
driver.parameter.port
|
|
|
driver.version
|
|
|
driver.version.data
|
|
|
driver.version.internal
|
|
|
input.voltage
|
|
|
output.voltage
|
|
|
output.voltage.nominal
|
|
|
ups.beeper.status
|
|
|
ups.delay.shutdown
|
|
|
ups.firmware
|
|
|
ups.firmware.aux
|
|
|
ups.load
|
|
|
ups.mfr
|
|
|
ups.mfr.date
|
|
|
ups.model
|
|
|
ups.productid
|
|
|
ups.serial
|
|
|
ups.status
|
|
|
ups.test.result
|
|
|
ups.timer.reboot
|
|
|
ups.timer.shutdown
|
|
|
ups.vendorid
|
|
About this device
Reported at:
