Questions[apc](server)

I have an APC Backup UPS ES 850G2, connected via USB to a RaspberryPi acting as NUT master. The Pi uses the usbhid-ups driver. Several other devices are NUT slaves and poll the Pi for UPS info.

Here's a list of some particular things about the APC:

pi@nut-server:~ $ upsc apc@localhost
Init SSL without certificate database
battery.charge: 92
battery.charge.low: 10
battery.charge.warning: 50
...
battery.runtime: 884
battery.runtime.low: 350
...
driver.name: usbhid-ups
driver.parameter.ondelay: 60
driver.parameter.pollfreq: 30
driver.parameter.pollinterval: 1
driver.parameter.port: auto
driver.parameter.productid: 0002
...
driver.version: 2.7.4
driver.version.data: APC HID 0.96
driver.version.internal: 0.41
...
ups.delay.shutdown: 20
ups.firmware: 938.a2 .I
ups.firmware.aux: a2
ups.load: 31
ups.mfr: American Power Conversion
ups.mfr.date: 2021/05/02
ups.model: Back-UPS ES 850G2
ups.productid: 0002
...
ups.timer.reboot: 0
ups.timer.shutdown: -1
ups.vendorid: 051d

ups.conf

[apc]
    driver = usbhid-ups
    port = auto
    desc = "APC 850VA UPS"
    vendorid = 051d
    productid = 0002
    serial = "xxxxxx"

A few issues I have with it:

• I can't set the battery.charge.low parameter, although, I can set the battery.runtime.low using upsrw
• when the UPS is online (i.e. getting power from the mains), as soon as the runtime drops below battery.runtime.low due to a high load, the UPS starts beeping and FSD is triggered

Apr 18 16:26:34 nut-server upsmon[477]: UPS apc@localhost battery is low
Apr 18 16:26:34 nut-server upssched[2840]: Executing command: triggerfsd
Apr 18 16:26:34 nut-server upsmon[477]: Signal 10: User requested FSD
Apr 18 16:26:34 nut-server upsd[472]: Client [email protected] set FSD on UPS [apc]
Apr 18 16:26:34 nut-server upsmon[477]: Executing automatic power-fail shutdown
Apr 18 16:26:34 nut-server upsmon[477]: Auto logout and shutdown proceeding
Apr 18 16:26:34 nut-server upssched[2850]: Executing command: turnoffups

• when the UPS powers back on having a low battery (i.e. runtime < battery.runtime.low) and turns on the load, it immediately triggers a FSD and none of the devices have time to properly shut down, as the Pi master shuts everything down again.

I have set the battery.runtime.low value to something reasonable, so that the UPS load has time to shut down (especially my QNAP NAS, which shuts down in ~3-4 minutes).

Shouldn't the "Low Battery" flag be triggered only of the UPS is offline? Is what I'm describing normal behavior? Is there anything I set up badly? Do I need to provide any extra config for some help?

From the NUT documentation on upsmon.conf:

LOWBATT UPS is on battery and has a low battery (is critical)

I have an APC Rack PDU (AP7920) and a Lantronix ETS16P RS232 terminal server. I would like to connect the RackPDU directly to the Lantronix. The RackPDU has a serial RJ12 connector and the Lantronix a serial RJ45 connector. I found pinouts for RackPDU and Lantronix.

This is the connection I came up with:

However, after crimping the cable, the connection did not work (regardless how much I was typing in the Lantronix, there was no response from the APC).

Is this the right connection? Do I miss anything?

Are the TX- and RX- indeed GND?

I have an APC Rack PDU (AP7920) and have configured:

• [x] Enable SNMPv3 access
• Username: switch
• Authentication Passphrase: test
• Privacy Passphrase: test
• Authentication Protocol: (o) MD5
• Privacy Protocol: (o) DES
• Access Control: [x] Enable, Username: switch, NMS IP/Host Name: 0.0.0.0

Now when I execute snmpwalk I get:

# snmpwalk -v3 -a MD5 -A test -u switch -x DES -X test 192.168.1.1
snmpwalk: Decryption error

What am I doing wrong?

My goal is to switch outlets via SNMP

I have an APC Rack PDU AP7920 (hardware revision B2, manufactured 07/21/2012). When I log in via telnet I get:

American Power Conversion               Network Management Card AOS      v3.3.4                                          
(c) Copyright 2005 All Rights Reserved  Rack PDU APP                     v3.3.3     

I would like to upgrade the firmware. On the APC website, I found two options (they are very hidden for some reason): apc_hw02_aos390_rpdu374.exe and apc_hw02_aos392_rpdu392.exe (i.e., v3.9.0/3.7.4 and 3.9.2/3.9.2).

After executing go.bat and entering correct IP address, username and password, I get for both:

Checking network connection ...  ERROR!!! Login unsuccessful.

That's definitely not true: IP and login details are 100% correct. How can I upgrade this?

I'm configuring a UPS to be controllable via SNMP and have come across to options:

• Write mode
• Write+ mode

I've tested both settings and only Write+ works for me so it's what I'll have to use. I'm interested to know what exactly Write+ enables as opposed to just the regular Write mode though.