similar to: [HCL] <CyberPower> <PR2200LCDRT2U> supported by <snmp-ups>

(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

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

Device manufacturer: GE Digital Energy (http://www.gedigitalenergy.com/powerquality/catalog/rackmountnet.htm) Device name: GE EP6000R (http://www.gedigitalenergy.com/powerquality/catalog/rackmountnet.htm) *upsc:* * battery.voltage: 272.40 * battery.voltage.nominal: 240.0 * beeper.status: disabled * device.type: ups * driver.name: blazer_usb * driver.parameter.bus: 004

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, 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:

I have a data set for different time intervals. The data has three comment lines before data for each time interval. For each time interval there are 500 data points. I want to change the dataset such that I have the following format: t1 t2 t3 ................ 0.00208 0.00417 0.00625 ................. a1 a2 a3 ...................

Hi all, I've been trying to build NUT (latest release source) on a pretty "standard" CentOS (RHEL style) linux box, to monitor an APC Symmetra UPS Unit which powers our server room and broadcasts information via SNMP to appropriate clients. I am having some trouble even encouraging NUT to build with snmp support, which doesn't seem to happen by default. I am curious if anyone

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

Just started using NUT and having a problem. I'm not sure if it is even NUT that is causing the issue. I'm running the latest FreeNAS 9.3 release. Network UPS Tools upsmon 2.7.2. The UPS is a Tripplite SU6000RT4UHVPM with the SNMPwebcard installed. I'm trying to use the SNMPwebcard, not USB or Serial. I've updated the SNMPwebcard to the latest firmware version (see below). In

Dear colleagues, How can I do to "relevel" the intercept? I need that the treatment "Db" be the intercept, and have p-values for the comparisons with the others treatments. I used the function "relevel" but it did not work out to have what I want. Thanks for your help, Xavier T1 <- read.table(file.choose(), h=T) > head(T1) treatment replicate Time

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

G'day I'm currently using NUT on Debian squeeze box in the same subnet with an IBM 3000 HV (branded Eaton 5125 with Web/SNMP card), now I wanted to get our storage appliance running NexentaStor 3.1 set up to be using NUT too. Nexenta- Stor is an OpenSolaris / illumos-based appliance OS currently using NUT packages from ubuntu hardy. My question here is whether I'm running into a -

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:

Hi Charles, Running upsdrvctl -D start on the host with all three configured to SNMPv3 kicks out 56 different "unhandled ASN 0x81 from ..." lines on all three but importantly they all start up and keep running. I'm starting to suspect the startup is taking so long that systemd is timing out and killing it. time -p reports real time of 133.27. I'm not a fan of systemd but

Hi, I have had a long standing problem with NUT talking to 110V MGE UPSs on FreeBSD, I was recently investigating again and noticed that upsd seems overly noisy, eg.. May 5 03:50:36 egbert upsd[96662]: UPS [ups1] data is no longer stale May 5 03:50:36 egbert upsd[96662]: Data for UPS [ups1] is stale - check driver May 5 03:50:36 egbert upsd[96662]: UPS [ups1] data is no longer stale May 5

Hi All, I have an mge pulsar esv 14+ rackmount UPS connected via straight through serial cable to a USB to serial adaptor (My motherboard does not have a native RS232 port). I am running Ubuntu Server 9.04 x64, and nut 2.4.1-2ubuntu4 installed via APT. I am getting the error: Poll UPS [ups1 at localhost] failed - Driver not connected My conf files: (ups.conf) [ups1] driver=mge-utalk

Hello all, Thank you in advance for a great FOSS project. Also, thank you for reading my question. I have a CyberPower OR1500LCDRTXL2U with an RMCARD205. There are a handful of devices plugged into the UPS. I received a message today saying to send upsc output to NUT developers after this message: "No matching MIB found for sysOID '.1.3.6.1.4.1.3808.1.1.1'" root at

Hello, I've got a setup with NUT, where we've got two UPSes, ups1 and ups2. UPS1 supports our servers, while UPS2 supports our desktop boxes. We monitor both of them via USB on a box now called "upsmon". The interesting point comes here. We monitor both UPSes on the upsmon box, but if UPS2 fails, which supports our desktop boxes, NUT shouldn't initiate a shutdown in

Hi, I have the above UPS connected to a FreeBSD 6.2 box and it shows 'data stale' very frequently (every few minutes). I have tried the usual trick of setting maxage, poll interval, etc etc but to no avail. When I wind up logging I see (on mge-shut) entering shut_get_report(id: 0d, len: 1800) shut_wait_ack(): ACK received entering shut_get_report(id: 16, len: 1800) shut_wait_ack():

Hi, I've got two MGE Ellipse 1500 UPS connected via usb to an ubuntu jaunty system with nut and libupsclient1 2.4.1-2ubuntu4. As soon as I start the driver for the second one, they start fighting each other and I get no data. I found an older post to this list that said: If you want to monitor multiple UPSes through usbhid-ups, you *must* make sure that each one can be uniquely identified