search for: ap9619

Hi Dmitry and the list, would you (or anyone owning such a device) be able to validate the below patch: https://alioth.debian.org/tracker/index.php?func=detail&aid=310613&group_id=30602&atid=411542 Most notably, it's about the paths changes: -#define APCC_OID_IEM_TEMP ".1.3.6.1.4.1.318.1.1.10.2.3.2.1.4.0" -#define APCC_OID_IEM_TEMP_UNIT

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 c...

...d a file-logger (amongst others). interesting though I've not had time to investigate more. I've just added a new entry on the client projects page. Thanks for your work on this point. > As an aside, I've configured NUT to talk to our APC-8000[3], which comes with > an "AP9619" [4] expansion card. This card has an external temperature probe, > but it doesn't seem to appear in the variables NUT returns: the UPS's > internal temperature is mentioned, but no "ambient.temperature.measured". > I've copied the output below. > >...

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 the card. Now I am seeing COMMBAD, then...

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 mana...

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 state for the UPS is "TRIM". NUT doesn't treat that...

> 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 state for the UPS is "TRIM&quot...

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 UPSs wi...

...y. Incidentally, the remarks in the snmp-ups driver man page that say "APC AP9606 APC Web/SNMP management card, perhaps others" could definitely use updating, since the driver categorically works with the AP9617 card. Since the AP9617 card is programmatically identical to the AP9618 and AP9619 cards, I'd say that it's safe to claim that the driver works with all three. One more note. I flashed the AP9617 firmware to the latest "apc_hw02_aos373_sumx372" version. I'm using V1.0 SNMP. No idea whether V3.0 SNMP works. Eric Wilde