similar to: APC AP9617 SNMP returns strange errors

I have a couple of Slackware servers which I have plugged into some APC UPS's. Each UPS has a network management card in it - one is the AP9617 and the other is the AP9606. I want the servers to shut themselves down when the UPS's go into "low battery" mode. What do I need to install? I've read this thread

Is NUT using the same SNMP v3 user as your SNMP Set or a different one? If it is a different one (e.g. an SNMP v1 or v2c string) does that user / community string have read/write access? tcpdump to listen for packets across UDP 161 is one way to check what is actually being sent. Thank you, David Zomaya Tripp Lite ________________________________ From: Nut-upsuser

I'm in the process of trying to get NUT to manage an APC SmartUPS. Monitoring of the UPS is working fine: $ upsc nutdev1 at localhost Init SSL without certificate database ambient.1.humidity.alarm.high: 60.00 ambient.1.humidity.alarm.low: 30.00 ambient.1.temperature.alarm.high: 40.00 ambient.1.temperature.alarm.low: 10.00 battery.charge: 94.00 battery.charge.restart: 0 battery.current: 0.00

I meant to send this to the list but evidently only sent it to David. Since sending it I've done a second test which shows what a successful snmpset looks like. First attachment, from the forwarded email, is nutout.txt. Second attachment is snmpout.txt. nomad -------- Forwarded Message -------- Subject: Re: [Nut-upsuser] [EXTERNAL] SNMP shutdown timing out Date: Mon, 4 May 2020 09:28:57

Is anyone using snmp-ups with the -k option successfully? This is really starting to look like a bug somewhere in nut, not a config problem. I've just tried the same command from a FBSD box with the same unfortunate result. Mind you, it could be the UPS card, I'm using the same one for both tests. : || nomad at castle nut-2.7.4 [93] ; please drivers/snmp-ups -a nutdev1 -x

I have three APC SmartUPS 5000s. Two of them are AP9617 and one is AP9619. I have a RS-232 connections from my monitor host to all three. All three report status and give information. One of the two AP9617 - ups3-1 - does not shut down when FSD is sent. It did when I first set this system up a year or two ago but it's stopped doing so since then. Resetting the management interface does not

I know this isn't exactly the right place to ask, but I figure at least *someone* on this list has done it once. I recently acquired an AP9617 web/snmp management board for my UPS. The web and telnet part of it work great. However, I can't get *anything* from the snmp interface. I've triple-checked the community name and access settings (currently are wide open). I've ensured

Attempting to install the SNMP driver on Enterprise SuSE 10.0. The version of NUT is 2.6.0. To begin with, I installed the net-snmp and net-snmp-devel packages, using YAST. If I do this command: net-snmp-config --version --base-cflags --libs The result is: 5.3.0.1 -DINET6 -O2 -fmessage-length=0 -Wall -D_FORTIFY_SOURCE=2 -g \ -fno-strict-aliasing -fstack-protector-all -Dlinux \

I'm trying to get SNMPv3 management working for an APC AP9617 card. It is newly refurbed, running sumx v3.7.2 and aos v3.7.3. In the SNMPv3 user profiles section I have (I don't care about the password leaking, it's temporary): User Name: nut Authentication Passphrase: NutScan at Password43LongerWord Privacy Passphrase: NutScan at Password43LongerWord Authentication protocol:

New NUT install dealing with three APC Smart-UPS 5000s, two of which have AP9617 and the third has a AP9619 card. The SNMPv3 configurations on all three are exactly the same. This is confirmed by snmpget calls that work just fine: snmpget -Cf -v3 -u [...] -l authPriv -A '[...]' -X '[...]' -a MD5 -x DES [upsname] .1.3.6.1.4.1.318.1.1.1.1.1.1.0 snmp-ups can query all three

Hi all! I'm wondering if there's anyone doing any hacking on the snmp-ups driver at the moment. I've started looking at implementing 3phase-support, and this uncovered some rather unpleasant stuff in the snmp-ups driver that I really need to fix in order to get things sane. Those of you that's allergic to SNMP might want to stop reading now, this is rather icky ;)

Hi Dmitry and the list, would you (or anyone owning such a device) be able to validate the below patch: https://alioth.debian.org/tracker/index.php?func=detail&aid=310613&group_id=30602&atid=411542 Most notably, it's about the paths changes: -#define APCC_OID_IEM_TEMP ".1.3.6.1.4.1.318.1.1.10.2.3.2.1.4.0" -#define APCC_OID_IEM_TEMP_UNIT

Just a hunch about your snmpwalk, what happens if you format like this? snmpwalk -l authpriv -v 3 -u user -a MD5 -x DES -A authpassphrase -X privpassphrase {host address} so snmpwalk -l authpriv -v 3 -u nut -a MD5 -x DES -A NutScan at Password43LongerWord -X NutScan at Password43LongerWord apcups Thank you, David Zomaya Tripp Lite ________________________________ From: Nut-upsuser

I need a little help on this problem, please? I include my /etc/apcupsd/apcupsd.conf file is attached. port 3551 udp/tcp has been added to the (running) firewall. My APC is recognized as: APC Back-UPS 450 FW:844.Kld.D USB FW:Kld This from the hardware browser. PS says: root 2419 0.0 0.0 4196 584 ? Ss Mar23 0:09 /sbin/apcupsd -f /etc/apcupsd/apcupsd.conf Is group 2419 the

This is the third attempt to make the stats filter better. This time I kept the changes minimal to make it eaier to make progress. I tried the idea of showing global stats in separate "total" section, but it became messy and hard to implemnt, so I tried the simpler solution of showing both operation rate and total rate in the operation line. Nir Soffer (5): filters: stats: Add

Change the first line to show total ops, time, total size, and rate. The totals are useful for understanding the total throughput of the application. --- filters/stats/nbdkit-stats-filter.pod | 8 ++++---- filters/stats/stats.c | 19 ++++++++++++++++++- 2 files changed, 22 insertions(+), 5 deletions(-) diff --git a/filters/stats/nbdkit-stats-filter.pod

Here are a series of my recent changes to NUT. The first few in the set are primarily little fixes and improvements. In among those are a few for .gitignore files which of course you can ignore for SVN, and there's one for a commit to a generated file which of course should not be tracked in any VCS. Then there are a couple or three to do with generating the header files used by