similar to: How to treat UPS status of TRIM as on line

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

> 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 am running NUT as part of FreeNAS 9.2.0. I have looked through the manuals, but I don't see how to address my issue. The box has 4 NIC's in a LACP LAGG group. It takes a while for LACP to finish, and NUT tries to start before packets are flowing. NUT will complain endlessly about communication errors and never establish SNMP communication with my APC UPS. If I stop NUT and restart

On Feb 4, 2014, at 10:48 PM, Elliot Dierksen wrote: > NUT will complain endlessly about communication errors and never establish SNMP communication with my APC UPS Hmm, at first glance, I read the "complain endlessly" part as a figure of speech, and figured SNMP would get there eventually since it's UDP. But if you have to stop and restart NUT, that is a different story. What

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

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

On 2/5/2014 8:24 AM, Charles Lepple wrote: > On Feb 4, 2014, at 10:48 PM, Elliot Dierksen wrote: > >> NUT will complain endlessly about communication errors and never establish SNMP communication with my APC UPS > Hmm, at first glance, I read the "complain endlessly" part as a figure of speech, and figured SNMP would get there eventually since it's UDP. But if you have

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

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

Hello, I'm having a problem renaming and sorting the underlying factor of a ggplot2 based plot. Here's my code: ---8<---------- > delta <- ggplot(subset(data, Model==c("dyn", "dl4", "dl3")), aes(x=Problemsize, y=Fitness)) + geom_smooth(size=1, color="black", fill=alpha("blue", 0.2))+ geom_point(size=0.5,

Hello, I'm currently using a boxplot to visualize data for three different models. As I have three models, I'm plotting three parallel boxplots for each factor. This works fine - what I need now is a line connecting the medians of each boxplot of each model. I want to do this in order to visualize the trend that one of the models exhibit. Basically, I want to plot a curve for each model

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

Hello, I have the following hardware configuration. Tyan 2466N motherboard, 1.03 BIOS, 2 Athlon-MP 1800+ CPUs, 512MB registered ECC DRAM, Onboard 3Com NIC (xl type) Radeon 8500 AGP video card Adaptec 3210S SCSI RAID controller Comtrol RocketPort 8 port PCI serial card I have started to experience some odd system lockups in the past couple months, and it seems to be getting worse. I particular,

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

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 >

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

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

Hi, I am trying to configure my Tripp Lite SU5000RT3U on Ubuntu 18.04 as I am not able to completely get all the data from the UPS. After installing all required packages from the Ubuntu repos (had to run sudo apt-get install dkms, I had to install the displaylink drivers from displaylink.org by doing sudo ./displaylink-driver-4.2.29.run, and I created a sim link by doing the following: sudo ln

Hey there, I got a new UPS (CyberPower PR1500LCDRTXL2Ua) and found the serial drivers don't quite work... So I decided to jump in and make changes to the driver that would hopefully make it happier. I have it working (I really only changed powerp-txt.c) but still have a couple questions... Charles said I should mention them here to talk to anyone interest but specifically Arjen (one of