similar to: using nut to monitor SNMP UPS unit

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

Hi, many thanks to those who responded (Charles Lepple and "lonely wolf") In order to build, as directed, I needed to install a few goodies via "yum". Things then built fine and nut seems to detect my UPS perfectly and things are going well. I should mention, maybe, that the following yum installs were done to get this working. --paste-- yum install net-snmp-devel # the

Hi, I''m using yum as our package provider and having an issue. Puppet is complaining of the version, this is the code I''m trying to implement: $snmp_version = "5.3.2.2" package { "net-snmp": ensure => "${snmp_version}"; } On the client I got: debug: //Node[client.example.com]/snmp::base/Package[net-snmp]: Changing ensure debug:

Hello all, There is a new Windows package of NUT. It now contains nut-scanner binary. Note that there is a known issue with libupsclient.dll with nut-scanner. The scan of NUT servers using nut-scanner will not work for now. You can find it at : http://www.networkupstools.org/source/2.6/NUT-Installer-2.6.3-1.msi Please send feedback to the list. Regards, Fred -- Team Open Source Eaton -

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 new to both UPS setup and SNMP on linux - so I'd appreciate any help I can get....I'm stuck! I'm running fedora core 5, and have installed net-snmp and nut. I'm trying to get my network connected UPS to this linux machine. My /etc/ups/ups.conf looks like this: [upsnetwork] driver = snmp-ups port = 172.31.254.7 community = public desc="Network

I have a Symmetra LX 16000 UPS with a Network Management Card (Schneider Electric, I think).?? Can NUT be configured to report from this unit and shutdown hosts based upon messages from this unit?

Hi I set up my ups with driver snmp-ups, and it get recognized as a AEC T2003. In the nut-cgi upstats page input/output/load are displayed corectly, but the Status field is marked as "Not supported". Is "Status" important to initiate shutdown in case of low battery ? Will my server shut down correctly ? thanks Massimo I include "upsc snmp@localhost" output:

(Note that I mentioned this *was* previously working with an older version of Nut). [irs2-ups1] driver = snmp-ups port = irs2-ups1.sum.naoj.org mibs = auto community = private irs2-ups1.sum.naoj.org responds to pings. On Tue, Oct 8, 2013 at 3:55 PM, Tim Rice <tim at multitalents.net> wrote: > On Tue, 8 Oct 2013, Philip Tait wrote: > > > Here is the upsc

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:

Hi, Nut-upsusers, I am having problem configuring NUT to work with Tripplite UPS through SNMP. There is a Tripplite SmartOnline SU10KRT3/1X and attempts to monitor it using NUT though SNMP are failing... OS: Enterprise Linux 6, Nut version: 2.6.5. ups.conf is configured: [trippliteups] driver = snmp-ups port = 10.200.254.39 desc = "ProductionServer"

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

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 >

Hello, I'm wondering if anyone else is seeing the same issues I'm seeing here. I have recently upgraded one of my systems from 4.4 to 4.5 and ever since then I cannot get snmp to work. I am monitoring the interface traffic. Please keep in mind the firewall/router I do the same thing without any issues for 4 interfaces and it is still at 4.4 and doesn't have any issues. If I

I just used Nick Mae's well written HOWTO on setting up Cacti on CentOS 4.xto setup Cacti on my CentOS 5.1 system : http://wiki.centos.org/HowTos/Cacti_on_CentOS_4.x I was hoping to add a page or section for CentOS 5.x with the modifications I'm including below. My wiki.centos.org username is "GeneWood" Changes : # Make sure snmpd accepts 'public' as public

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

Hi ALL, I am trying to use the SNMP extension of michel http://x-ray.prokon.cz/data/snmp/ i pached the snmpd damon as mentioned in the README but when i run "snmpwalk -c community target enterprises.18756" i get this error "snmpwalk: No securityName specified (Sub-id not found: (top) -> enterprises)" any idea ? Thanks , venkat

Hello Pros and users of Puppet. I have two problems with the following modul setup: My first problem that i tried every combination of require,notify,subscribe for the mail sending exec but it runs every single time when i run the module no matter if the files changed or not. Second problem that puppet reports that snmpd was refreshed by two resource and restarted but actually it doesnt happen.

Hi all. I am having an issue and quite frankly would rather not spend the entire next two days learning the entire snmp program. I am hoping someone out there has used MRTG and SNMP to make it work. I have both installed. Single server, polling itself. Question 1- does snmpd have to run as a daemon, or only run once so I can get OID and MIBs from it? Question 2- does anyone know the command

Build from source, and done . . . wasting your time looking for a less out of date RPM is pointless. . . RPM, .deb, etc are almost always downrev. . . - Tim On June 10, 2017 2:06:42 PM CDT, Ben Kamen <ben at benkamen.net> wrote: >Hey all, > > I recently got an RMCARD205 for my Cyber UPS.... > >if I use no MIBS line in the config file, I get this: > > >> Network