search for: apcc

...battery.packs.bad: -1.00 battery.runtime: 5160.00 battery.runtime.low: 120 battery.voltage: 27.00 battery.voltage.nominal: -1.00 device.mfr: APC device.model: SMART-UPS 1400 device.serial: WS9831004667 device.type: ups driver.name: snmp-ups driver.parameter.authProtocol: MD5 driver.parameter.mibs: apcc driver.parameter.pollinterval: 2 driver.parameter.port: 192.5.37.191 driver.parameter.privProtocol: DES driver.parameter.secLevel: authPriv driver.parameter.synchronous: no driver.version: 2.7.4 driver.version.data: apcc MIB 1.2 driver.version.internal: 0.97 input.frequency: 60.00 input.sensitivity...

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 privProtocol=AES desc = "APC SU700 SNMP v3 device, with the highest security level" ...... Now I test /sbin/snmp-ups -DDD -a tfapc01 Ne...

...2/url?u=http-3A__driver.name&d=DwMFaQ&c=f9s1WCuF-N6cmD_YaZ7gBg&r=lhr3k4au5dVQgHY_iS-v_t9g8PHVkn8Px_wyaupZGfQ&m=VdKSS_Vk98WT0ADZ-mQe_3zCfrLacAAuMS7JSj5wn1w&s=hM67G_Mcn7oW5yo4o44Na9wyw26mxM8hKXFExeGyhJQ&e=>: snmp-ups driver.parameter.authProtocol: MD5 driver.parameter.mibs: apcc driver.parameter.pollinterval: 2 driver.parameter.port: 192.5.37.191 driver.parameter.privProtocol: DES driver.parameter.secLevel: authPriv driver.parameter.synchronous: no driver.version: 2.7.4 driver.version.data: apcc MIB 1.2 driver.version.internal: 0.97 input.frequency: 60.00 input.sensitivity...

[please CC the list] On Apr 10, 2015, at 7:55 AM, Ben Kamen <bkamen at benjammin.net> wrote: > On 2015-04-09 9:48 PM, Charles Lepple wrote: >> On Apr 8, 2015, at 11:16 PM, Ben Kamen <bkamen at benjammin.net> wrote: >> >> As a starting point, you might want to search the NUT Device Dump Library (DDL) for 'test.battery' and 'test.interval':

Don't choose mini-box OpenUPS. No instant commands. No reporting of power fail. No replies to emails to support. Otherwise perfect! I have mine working with support from Charles but not ideal. Regards, Philip. Sent from my iPhone > On 9 Apr 2015, at 05:16, Ben Kamen <bkamen at benjammin.net> wrote: > > I'm looking to buy some new UPSs and am thinking of parting ways

...1" produced Network UPS Tools - Generic SNMP UPS driver 0.68 (2.6.5) 0.000000 debug level is '4' 0.000385 SNMP UPS driver : entering upsdrv_initups() 0.000402 SNMP UPS driver : entering nut_snmp_init(snmp-ups) 0.044948 SNMP UPS driver : entering load_mib2nut(apcc) 0.044957 load_mib2nut: trying classic method with 'apcc' mib 0.044961 Entering nut_snmp_get_str() 0.044965 nut_snmp_get(.1.3.6.1.4.1.318.1.1.1.1.1.1.0) 0.051353 Unknown mibs value: apcc Now in the months between the last post and this, I had the opportunity to...

...output for your >device. >> Going back to the classic MIB detection method. >> Detected PR1500LCDRTXL2Ua on host 192.168.125.10 (mib: cyberpower >0.1) >> Network UPS Tools - Generic SNMP UPS driver 0.68 (2.6.5) >> Detected SMART-UPS 3000 RM on host 192.168.125.7 (mib: apcc 1.2) >> [shop] Warning: excessive poll failures, limiting error reporting >> [shop] Warning: excessive poll failures, limiting error reporting > >If I use the mibs = cyberpower > >it works as somewhat expected: > >> >> Network UPS Tools - UPS driver controller...

I'm looking to buy some new UPSs and am thinking of parting ways with APC to explore other brands. Can anyone suggest another brand that handles doing calibration runs (or maybe another brand doesn't need them) that I can automate with NUT? Thanks, -Ben

...I'm confused. When the snmp-ups driver starts, does it immediately see the TRIM state and initiate a shutdown, or does this only happen after going on battery once? Other SNMP sub-drivers map the "TRIM" status to "OL TRIM", so I suspect the same could be done for the 'apcc' MIB setting. > I realize what I am doing is a bit of a kludge, but I can't > get a 208V circuit easily in my house. > > I am also getting these messages whenever NUT starts > > "[CR-UPS] Warning: excessive poll failures, limiting error reporting" From a quic...

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 commands only available using a serial connection driver? I use nut 2.2, but don't see anyt...

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

...4.1.318.1.1.1.9.3.3.1.7.1.1.3" and fails to start. My current [redacted] ups.conf follows. The only differences between the values are on the port and desc lines (ignoring #, of course). [ups1] desc = "APC Smart-UPS 5000 SNMP in rack 1 - AP9617" driver = snmp-ups mibs = apcc port = [ups1...] # snmp_version = v1 # community = [xxx] snmp_version = v3 secLevel = authPriv secName = [xxx] authPassword = [xxx] authProtocol = MD5 privPassword = [xxx] privProtocol = DES [ups2] desc = "APC Smart-UPS 5000 SNMP in rack 2 - AP9619&qu...

...0.009138 nut_snmp_get(.1.3.6.1.2.1.1.2.0) 0.009156 nut_snmp_walk(.1.3.6.1.2.1.1.2.0) 0.009158 nut_snmp_walk: max. iteration = 1 0.030970 OID value: .1.3.6.1.4.1.318.1.3.2.10 0.030992 match_sysoid: device sysOID value = .1.3.6.1.4.1.318.1.3.2.10 0.030995 match_sysoid: checking MIB apcc 0.030997 match_sysoid: checking MIB mge 0.030999 match_sysoid: comparing .1.3.6.1.4.1.318.1.3.2.10 with .1.3.6.1.4.1.705.1 0.031016 match_sysoid: checking MIB netvision 0.031018 match_sysoid: comparing .1.3.6.1.4.1.318.1.3.2.10 with .1.3.6.1.4.1.4555.1.1.1 0.031021 match_sysoid: chec...

...to 1 second(s) 0.015344 SNMP UPS driver: entering load_mib2nut(auto) 0.015355 trying the new match_sysoid() method 0.018505 OID value: .1.3.6.1.4.1.476.1.42 0.018522 match_sysoid: device sysOID value = .1.3.6.1.4.1.476.1.42 0.018529 match_sysoid: checking MIB apcc 0.018533 match_sysoid: checking MIB mge 0.018540 match_sysoid: comparing .1.3.6.1.4.1.476.1.42 with .1.3.6.1.4.1.705.1 0.018549 match_sysoid: checking MIB netvision 0.018560 match_sysoid: comparing .1.3.6.1.4.1.476.1.42 with .1.3.6.1.4.1.4555.1.1.1 0.018570 m...

Hi all, I have an APCC Back-UPS XS 1000 (it's a USB device) that I'm using with nut 2.0.2 that came with Fedora Core 4. It reports itself like this: Back-UPS RS 1000 FW:7.g8 .D USB FW:g8 in the nut web status page, which seems a tad messy. It otherwise works fine, except I don't get any information on...

...esn't interpret TRIM and power on line, so it thinks line power was never restored. It initiates a shutdown after the configured time (300 seconds) expires. > Other SNMP sub-drivers map the "TRIM" status to "OL TRIM", so I suspect > the same could be done for the 'apcc' MIB setting. > >> I realize what I am doing is a bit of a kludge, but I can't >> get a 208V circuit easily in my house. >> >> I am also getting these messages whenever NUT starts >> >> "[CR-UPS] Warning: excessive poll failures, limiting error re...

...r 0.70 (2.7.1) kill: No such process No matching MIB found for sysOID '.1.3.6.1.4.1.318.1.3.2.11'! Please report it to NUT developers, with an 'upsc' output for your device. Going back to the classic MIB detection method. Detected SMART-UPS 2200 RM XL on host guyups2.gy.ls.cbn (mib: apcc 1.2) [guyups2] Warning: excessive poll failures, limiting error reporting [guyups2] Warning: excessive poll failures, limiting error reporting [LIVE] guybackup:~ # upsc guyups2 ambient.1.humidity.alarm.high: 60.00 ambient.1.humidity.alarm.low: 30.00 ambient.1.temperature.alarm.high: 40.00 ambient....

..., with an 'upsc' output for your device. > Going back to the classic MIB detection method. > Detected PR1500LCDRTXL2Ua on host 192.168.125.10 (mib: cyberpower 0.1) > Network UPS Tools - Generic SNMP UPS driver 0.68 (2.6.5) > Detected SMART-UPS 3000 RM on host 192.168.125.7 (mib: apcc 1.2) > [shop] Warning: excessive poll failures, limiting error reporting > [shop] Warning: excessive poll failures, limiting error reporting If I use the mibs = cyberpower it works as somewhat expected: > > Network UPS Tools - UPS driver controller 2.6.5 > Network UPS Tools - Gene...

...nt driver... *monk:/etc/nut# upsdrvctl shutdown rm700 Network UPS Tools - UPS driver controller 2.2.2 Network UPS Tools - Multi-MIBS SNMP UPS driver 0.421 (2.2.2) Warning: This is an experimental driver. Some features may not function correctly. Detected Smart-UPS 700 RM on host 192.168.3.8 (mib: apcc 1.1) Initiating UPS shutdown shutdown not supported Driver failed to start (exit status=1)* regards Michael -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.alioth.debian.org/pipermail/nut-upsdev/attachments/20090609/dad9d3d0/attachment-0001.htm&gt...

...quired. The details of my ups.conf file are as follows: [apc] driver = usbhid-ups port = auto pollonly = 1 Thanks, -Chris Collins Chris Collins | APC by Schneider Electric | Senior Software Engineer Phone: +353-91-702000 x2661 | Mobile: +353-87-4189477 Email: chris.collins at apcc.com | Address: City East Business Park, Ballybrit, Galway, IRELAND *** Please consider the environment before printing this e-mail -------------- next part -------------- A non-text attachment was scrubbed... Name: apc-hid.patch Type: application/octet-stream Size: 606 bytes Desc: not available...