similar to: SNMP connection problem

Hi, ? have a necron snmp ups. nut-scanner cant find it. i tried to add with these definition but it fails.. [test5-ups] driver = snmp-ups port = 10.9.40.19 community = asdf12 desc ="test" i run driver with debugging , result is , root at upsviewer-debian:/usr/local/ups/bin# ./snmp-ups -DDDDDDD -a test5-upsNetwork UPS Tools - Generic SNMP UPS driver 0.68 (2.6.5) 0.000000

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

On 2/24/2014 11:10 PM, Charles Lepple wrote: > On Feb 24, 2014, at 10:29 PM, Jason R Begley wrote: > >> Thanks for the quick response Charles! I may not have gotten the correct output from the snmpwalk, let me know if the attachment is usable. Thanks! > Sorry, it's basically all comments. Do you have the stdout from the subdriver script? Also, how is the MIB file installed?

On Feb 24, 2014, at 11:48 PM, Jason R Begley wrote: > 0.073855 load_mib2nut: trying classic method with 'delta_ups' mib > 0.073878 Entering nut_snmp_get_str() > 0.073899 nut_snmp_get((null)) > 0.073918 nut_snmp_walk((null)) Arnaud, The gen-snmp-subdriver.sh script is setting mib2nut[i]->oid_auto_check to NULL for new drivers (with no instructions

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

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

2014-02-25 12:58 GMT+01:00 Charles Lepple <clepple at gmail.com>: > On Feb 24, 2014, at 11:48 PM, Jason R Begley wrote: > > > 0.073855 load_mib2nut: trying classic method with 'delta_ups' mib > > 0.073878 Entering nut_snmp_get_str() > > 0.073899 nut_snmp_get((null)) > > 0.073918 nut_snmp_walk((null)) > > Arnaud, > >

OpenBSD 5.6 nut-2.7.2 (bin package) Liebert IntelliSlot Unity Card IS-UNITY-DP ups.conf: ...... ? mibs = ietf ? snmp_version = v1 ...... The problem is that the card responds to other snmp (v1,2c,3) requests normally but not to the 1.3.6.1.2.1.33.1.1.1.0 (UPS-MIB.upsIdentManufacturer). # snmp-ups -a laes2ups -DDDDDDD Network UPS Tools - Generic SNMP UPS driver 0.72 (2.7.2) ?? 0.000000???? debug

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 >

Thanks for the quick response Charles! I may not have gotten the correct output from the snmpwalk, let me know if the attachment is usable. Thanks! New data added, here is the gdb output: Reading symbols from /usr/bin/snmp-ups...(no debugging symbols found)...done. (gdb) run -a tripplite -DD Starting program: /usr/bin/snmp-ups -a tripplite -DD warning: Could not load shared library symbols for

Hello All ! Recently I have upgraded NUT to 2.4.1, and now I can't monitor old IMV LanPro S3 UPS with old SNMP board. Previously it is monitored OK, but now snmp-ups refuses to start: [root at perforce /usr/local/etc/nut]# /usr/local/libexec/nut/snmp-ups -a lanproups -DDDDDDD Network UPS Tools - Generic SNMP UPS driver 0.44 (2.4.1) debug level is '7' SNMP UPS driver : entering

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

On Feb 24, 2014, at 10:29 PM, Jason R Begley wrote: > Thanks for the quick response Charles! I may not have gotten the correct output from the snmpwalk, let me know if the attachment is usable. Thanks! Sorry, it's basically all comments. Do you have the stdout from the subdriver script? Also, how is the MIB file installed? > New data added, here is the gdb output: > Reading

[I had a look through the mail archives before sending this, but I didn't find anyone else having this issue.] Has anyone seen this before? I'm almost 100% certain I tested this nut correctly detected OB LB in the past, but when I happened to look at it today, I see it refusing to work -- apparently because the NUT client knows how to ask for RFC1628 OIDs, but not what to do with the

Hello list, I've installed NUT on an HP blade server, and I try to get it communicating via SNMP with 2 HP R3000 UPSes, each fitted with a AF465A management card. To do this, I used the snmp-ups driver, and configured it for the "cpqpower" MIB. Communication with the UPSes is established. My problem is that both UPSes constantly return the "OL OB" status which, in

Hi, I'm trying connect a device: * OS name and version: root at nut:/etc/nut# hostnamectl Static hostname: nut Icon name: computer-vm Chassis: vm Machine ID: d7a3b7fc724f4fe1a79a3d0eeff08f72 Boot ID: 40a561c464064b5184150f5909af0aa7 Virtualization: vmware Operating System: Debian GNU/Linux 9 (stretch) Kernel: Linux 4.9.0-9-amd64 Architecture: x86-64 * NUT version

Hi, I have two UPS SMART-UPS 2200 RM both of them have the same configuration.One of them works fine, but the other one it doesn't, it output as follows: snmp-ups -D -a nutdev10 Network UPS Tools - Generic SNMP UPS driver 0.72 (2.7.2) 0.000000 debug level is '1' 0.001013 SNMP UPS driver : entering upsdrv_initups() 0.048606 trying the new match_sysoid() method

Hi, I just installed NUT to monitor 4 UPS, all APC, all with Network card APC 9617. NUT have problem to access the following SNMP OID on all the UPSes: Detected Smart-UPS 3000 XL on host apc4.cs.ait.ac.th (mib: apcc 1.1) [apc4] nut_snmp_get: .1.3.6.1.4.1.318.1.1.1.9.2.2.1.2.1: Error in packet: (noSuchName) There is no such variable name in this MIB. [apc4] nut_snmp_get:

Here is the upsc output: # /usr/local/ups/bin/snmp-ups -DD -a irs2-ups1 Network UPS Tools - Generic SNMP UPS driver 0.68 (2.6.5) 0.000000 debug level is '2' 0.000327 SNMP UPS driver : entering upsdrv_initups() 0.000341 SNMP UPS driver : entering nut_snmp_init(snmp-ups) 0.056112 SNMP UPS driver : entering load_mib2nut(auto) 0.056126 trying the new