search for: secnames

This adds [f]getc() and fgets() for parsing config files. Probably hard to avoid. Still trying to decide if I actually want to add system() or not. -hpa

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

nut-2.6.5 Scientific Linux 6.3 APC AP9630 management card My basic question is, does nut's SNMPv3 implementation work? I have this in /etc/ups/ups.conf ...... [tfapc01] driver = snmp-ups port = tfapc01.testfest.ixorg.org mibs = apcc snmp_version = v3 secLevel = authPriv secName = tfsnmpprof1 authPassword = ralow6moHet7zoboP8 privPassword = tuseL8Pakaz9degim7 authProtocol=MD5

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:

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

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

OS: CentOS 7 NUT Version: 2.7 Installed NUT through: yum install nut UPS: APC smart UPS srt3000 with NMC I am trying to set up NUT with snmp for my apc ups. Heres the config; [ups6]                 Driver = snmp-ups                 Port: ups6.domain.name (also tried 192.168.24.9)                 Snmp_version = v3                 secLevel = authPriv                 secName = ups6

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

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

Hi, Every time that I have to restart the nut-server it's a nightmare. For example, after editing ups.conf In many cases the only "solution" is to reboot the system. These are the errors: systemctl -l status nut-driver ? nut-driver.service - Network UPS Tools - power device driver controller Loaded: loaded (/usr/lib/systemd/system/nut-driver.service; static; vendor preset:

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

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