similar to: validating ambient.temperature from APC IEM (AP9618, AP9619) patch

Perhaps someone else could confirm this, I have an APC UPS with a built-in network management card with environmental sensor for temp/humidity. The OID index for the sensors appears to be .1 (the last component for each of the OIDs listed below). The original source code has them at .0 drivers/apccmib.h #define APCC_OID_IEM_TEMP ".1.3.6.1.4.1.318.1.1.10.2.3.2.1.4.1" #define

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 Paul, > I have another NUT client for your client-projects[1] page: MonAMI[2]. > > MonAMI aims to be a "universal sensor framework". The data gathered from > MonAMI's NUT plugin can be sent to any of the output plugins. Currently, > these include Ganglia, Nagios, KSysguard and a file-logger (amongst others). interesting though I've not had time to

Hi Paul, Aha - we have both found the same. I am referring to your post from: http://lists.alioth.debian.org/pipermail/nut-upsdev/2006-November/001344.html Looking at the source code the temp value is obtained by querying the following OID: #define APCC_OID_IEM_TEMP ".1.3.6.1.4.1.318.1.1.10.2.3.2.1.4.0" notice that the OID ends with .0 (index zero). Well, looking at the

Hi all, Not sure if this is on topic or not. I'm trying to query an SNMP value from centos 6 and I get a bad response if I don't specify the MIB to use: 0 digimer at pulsar:~/anvil/striker$ snmpget -v2c -c public -m /home/digimer/Downloads/APC/AP7900/MIB/powernet421.mib 10.255.2.1 .1.3.6.1.2.1.2.2.1.6.2 RFC1213-MIB::ifPhysAddress.2 = Hex-STRING: 00 C0 B7 5F 8A 85 0 digimer at

Hi, I'm new to nut. I have some 100 APC Smart-UPS 2200 & 3000's and I'm trying to do some calibration test on them. I've installed nut, with driver = snmp-ups mibs = apcc in ups.conf. I can read the variables using upsc. However it seems, I can't actually execute commands on the UPSses this way. ( upscmd some-ups calibrate.start ) Do I miss something, or are those

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

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 \

Hi All! Just an update! The snmp driver seems quite happy with an APC AP9618 managment card in an APC Smart-UPS RT 5000 XL UPS. I have an APC AP9630 to test in the near future so will give and update on that one too! Cheers Ang -- Angela Williams angierfw at gmail dot com Linux/Networking Hacker Blog http://angierfw.wordpress.com Smile! Jesus Loves You!

I have a SmartUPS 750 (SUA750) which has the temperature and humidity SmartSlot card installed. When NUT 2.2 communicates with this UPS over /dev/ttyS0 using apcsmart, using the APC Smart cable connected to the SUA750 serial port, and this ups.conf: [su700] driver=apcsmart port = /dev/ttyS0 I can see the ambient temperature and humidity data with "upsc su700 at

Has anyone had any success with this card? Thank you. Sandy.

Dear all, I'm studing how to include .c code in my .r functions . In the R-exts.pdf manual I have found the following code. At one point the author write "called from R by"... How can I load a .c file on R? ( I am using a xp windows as so.) Thank you ale void convolve(double *a, int *na, double *b, int *nb, double *ab) { int i, j, nab = *na + *nb - 1; for(i = 0; i < nab; i++)

I am using NUT 2.6.5 as part of FreeNAS 9.2.0. I am using an APC Smart-UPS 5000 RM DL4 with a AP9619 network management card. NUT properly detects when the UPS goes on battery and initiates a shutdown after the configured time. The problem I have is that I am using a 208V unit on a 240V circuit. That means the normal state for the UPS is "TRIM". NUT doesn't treat that as an on line

I'm running nut-2.8.0-3.el8.x86_64 on CentOS Stream 8 talking with an APC Smart-UPS RT 5000 RM XL via a Network Management Card AP9619 (version A10). Up to today I would receive occasional COMMBAD messages, then 5 minutes later I'd see a COMMOK.Maybe 1 or two a day. Today I updated the firmware on the AP9619 from 3.7.2 to SUMX 3.9.3 and AOX 3.9.4, the most recent releases available for

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

On Jan 10, 2014, at 12:58 PM, Elliot Dierksen wrote: > I am using NUT 2.6.5 as part of FreeNAS 9.2.0. I am using an APC Smart-UPS > 5000 RM DL4 with a AP9619 network management card. NUT properly detects > when the UPS goes on battery and initiates a shutdown after the configured > time. The problem I have is that I am using a 208V unit on a 240V circuit. > That means the normal

Hi, we do have APC Smart-UPS each with AP9617 and latest FW. As we found out we are not able to shutdown the UPS via SNMP - neither immediately nor delayed. And we cannot set values, but we can read them correctly. So it seems as we are not able to write to the UPS and get back strange errors. root at abex:/etc/nut# upsdrvctl -DDDD shutdown apc10001 Network UPS Tools - UPS driver controller

> On Jan 10, 2014, at 12:58 PM, Elliot Dierksen wrote: >> I am using NUT 2.6.5 as part of FreeNAS 9.2.0. I am using an APC >> Smart-UPS >> 5000 RM DL4 with a AP9619 network management card. NUT properly detects >> when the UPS goes on battery and initiates a shutdown after the >> configured >> time. The problem I have is that I am using a 208V unit on a 240V

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

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