similar to: SNMPv3

Updating an old thread. History here. http://lists.alioth.debian.org/pipermail/nut-upsdev/2013-January/006391.html http://lists.alioth.debian.org/pipermail/nut-upsdev/2013-February/006394.html http://lists.alioth.debian.org/pipermail/nut-upsdev/2013-February/006398.html On Fri, 1 Feb 2013, Tim Rice wrote: [snip] > > In all my testing I discovered the APC AP9630 is kind of flaky when >

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

On Nov 30, 2017, at 6:31 PM, Lee Damon <nomad at ee.washington.edu> wrote: > > SNMPv3 works fine when I have any one of the three configured in > ups.conf while the other two are configured with SNMPv1. It doesn't > matter which _one_ UPS is configured for SNMPv3 in ups.conf, they all > work individually (see below example). > > However, if I configure any two or

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

Dear all, I have installed mrtg via yum on centos 7, and using cron job to load mrtg every 5 mins. Everything work fine but just snmp v3 graph no show up. I try to load the command LAND=C /usr/bin/mrtg /etc/mrtg/metg.cfg it will show an error "SNMP V3 libraries not found, SNMPV3 disabled.". so, i installed all the net-snmp but still showing the error. I can't find any suggestion on

I've told systemd to wait up to 10 minutes for startup but it's still failing. Sometimes it fails with "timeout exceeded" and sometimes with the ASN error previously reported. I went back to running upsdrvctl -D to see if I could see anything. On the third run I saw messages about "startup timer elapsed" for ups2-1 and then it tried again to launch that one (killing

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:

One thing I just noticed, all of the COMBAD and COMOK messages are about the same UPS, the other two seem to be fine. nomad On 12/5/17 08:24 , Lee Damon wrote: ... > I suspect there's a deeper problem here. This morning I came in to 22 > emails about COMBAD and 22 emails about COMOK from upsmon on the master > host and a bunch more such messages from upsmon on my test clients. The

On Dec 4, 2017, at 2:43 PM, Lee Damon <nomad at ee.washington.edu> wrote: > > I have it "working" with the following settings changes from the default > in the RPM. By "working" I mean it starts after reboot and after issuing > 'sudo systemctl restart nut-driver' but, as expected, it takes quite a > while to finish startup. Yeah, this doesn't

On 4/28/20 1:58 PM, David Zomaya wrote: > snmpwalk -l authpriv -v 3 -u user -a MD5 -x DES -A authpassphrase -X > privpassphrase Evidently, even with argument identifiers order matters. That worked just fine and dandy. Now I guess I need to play with the order of the nut-scanner arguments to see if I get a similar result. thanks, nomad

>How close do the EPEL RPM's systemd configuration files look to the ones in the NUT tree? The only difference between?/lib/systemd/system/nut-driver.service and the one at?https://github.com/networkupstools/nut/blob/v2.7.2/scripts/systemd/nut-driver.service.in (not counting variable substitution for paths) is an additional line in the [Service] section provided by EPEL:

I have it "working" with the following settings changes from the default in the RPM. By "working" I mean it starts after reboot and after issuing 'sudo systemctl restart nut-driver' but, as expected, it takes quite a while to finish startup. /etc/systemd/system/nut-driver.service.d/nut-driver.conf [Unit] StopWhenUnneeded=no [Service] TimeoutSec=600

Hi Charles, Running upsdrvctl -D start on the host with all three configured to SNMPv3 kicks out 56 different "unhandled ASN 0x81 from ..." lines on all three but importantly they all start up and keep running. I'm starting to suspect the startup is taking so long that systemd is timing out and killing it. time -p reports real time of 133.27. I'm not a fan of systemd but

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'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

Hello, i'm trying to monitor a APC Smart-UPS 1000 behind a APC AP9630 Network Management Card via SNMPv3 using the AES Privacy Protocol. * OS name and version: Debian 10.1 * exact NUT version: 2.7.4 * NUT installation method: from debian package 2.7.4-8 * exact device name and related information * Model Number AP9630 * Hardware Revision 08 * Manufacture Date

Hi David On 4/29/20 3:28 PM, David Zomaya wrote: > 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? I tried setting them all with -x thing= arguments as well as letting it pull from ups.conf, same result. It's all SNMPv3 settings. sudo

Hi Jim, On Tue, 18 Feb 2014, Jim Klimov wrote: > Hello all, > > I was asked about a proper way to ensure powerfail shutdown of a blade > server fed off an APC SmartUPS, which is monitored by all hosts over > SNMP. In particular, they'd like to avoid the "untimely" return of > utility power - when the OSes are already shutting down, and would > stay down

SO, my full load on my core UPS is two Dell R610s, one Sun X4540, one HP DL360p gen8, two six-core Thuban-II workstations plua their monitors, and the network stack and KVM. The APC SU3000RM (3KVA) that blew up last week considered this to be just short of 60% load. The new Cyberpower PR3000 (also 3KVA), wqhich operates at a 90% power factor, considers this same load to be 43% load. I wasn't