search for: nutdev1

On 4/28/20 1:58 PM, David Zomaya wrote: > snmpwalk -l authpriv -v 3 -u user -a MD5 -x DES -A authpassphrase -X > privpassphrase Evidently, even with argument identifiers order matters. That worked just fine and dandy. Now I guess I need to play with the order of the nut-scanner arguments to see if I get a similar result. thanks, nomad

Network UPS Tools version 2.6.3 has been released: http://www.networkupstools.org/ Direct access: - Download: http://www.networkupstools.org/source/2.6/nut-2.6.3.tar.gz - News: http://www.networkupstools.org/source/2.6/new-2.6.3.txt - ChangeLog: http://www.networkupstools.org/source/2.6/ChangeLog Arnaud and the NUT team -------------- next part -------------- An HTML attachment was scrubbed...

...t Synch Type None Usage Type Data wMaxPacketSize 0x0008 1x 8 bytes bInterval 10Device Status: 0x0000 (Bus Powered) Which doesnt give much useful information. I managed to get nut-scanner to work and got this output: [nutdev1] driver = "blazer_usb" port = "auto" vendorid = "0001" productid = "0000" product = "ATCL FOR UPS" serial = "ATCL FOR UPS" vendor = "ATCL FOR UPS" bus = "001" I am...

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 battery.date: 03/14/20 bat...

...the ZIP file and ran the x86/install-filter and re-ran the installation. Running nut-scanner finds the UPS but ------------- Cannot load NUT library (libupsclient) : The specified module could not be found .. NUT search disabled. Scanning USB bus. No start IP, skipping SNMP Scanning XML/HTTP bus. [nutdev1] driver = "bcmxcp_usb" port = "auto" vendorid = "0592" productid = "0002" product = "Powerware UPS" bus = "bus-0" This application has requested the Runtime to terminate it in an unusual way...

...think before clicking any links or opening any attachments from this email. If suspicious, please forward to ishelpdesk at tripplite.com for review. ________________________________ 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 battery.date: 03/14/20 bat...

...rivProtocol DES --authPassword NutScan at P Password43LongerWord --privPassword NutScan at Password43LongerWord -s apcups Scanning SNMP bus. Error: unknown authtypeError generating Ku from authentication pass phrase ]0;lvd at chscc-pc-052:~: || lvd at chscc-pc-052 ~ [937] ; please snmp-ups -DDDD -a nutdev1 -x secLevel=authPriv -x secName=nut -x authProtocol=MD5 -x privProtocol=DES -x x authPassword=NutScan at Password43LongerWord -x privPassword=NutScan at Password43LongerWord -k [sudo] password for lvd: Network UPS Tools - Generic SNMP UPS driver 0.97 (2.7.4) 0.000000 debug level is '4'...

...on the Windows port, but you also need upsd running. This diagram shows how the pieces go together: http://www.networkupstools.org/docs/developer-guide.chunked/ar01s02.html#_the_layering > But many other commands complain... > > ------------- > C:\Program Files (x86)\NUT\bin>upsc nutdev1 > Error: Connection failure: Unknown error > ------------- upsdrvctl seems to have successfully started the bcmxcp_usb driver, but for upsc to get data from the driver, it needs to go through upsd. If you have a TCP port listening on 3493, then upsd is running. > For what it's worth,...

...rent one? > > If it is a different one (e.g. an SNMP v1 or v2c string) does that user > / community string have read/write access? I tried setting them all with -x thing= arguments as well as letting it pull from ups.conf, same result. It's all SNMPv3 settings. sudo snmp-ups -DDDD -a nutdev1 -x secLevel=authPriv -x secName=nut -x authProtocol=MD5 -x privProtocol=DES -x authPassword=NutScan at Password43LongerWord -x privPassword=NutScan at Password43LongerWord -k The output with -DDDD is the same either way. > tcpdump to listen for packets across UDP 161 is one way to check what i...

Hello! I have tested APC Back UPS ES 700 and NUT 2.6.5-3 a few days ago and I have got some news. This device is detected by nut-scanner as: [nutdev1] driver = "usbhid-ups" port = "auto" vendorid = "051D" productid = "0002" product = "Back-UPS ES 700 FW:829.D2 .I USB FW:D2 " serial = "5B0811T33088 " vendor = "APC"...

...tting ups.delay.start in upsrw does not change UPS behavior - it still powers on all power plugs instantly as power to UPS is restored. Also I have noticed that during testing (shutdown of UPS on power loss) upsrw variables reset to default values. Here is output of upsc/upsrw: > host ~ # upsc nutdev1 > battery.charge: 23 > battery.charge.low: 20 > battery.runtime: 208 > battery.type: PbAc > device.mfr: EATON > device.model: Protection Station 650 > device.serial: AN2E49008 > device.type: ups > driver.name: usbhid-ups > driver.parameter.bus: 002 > driver.paramete...

...starting to look like a bug somewhere in nut, not a config problem. I've just tried the same command from a FBSD box with the same unfortunate result. Mind you, it could be the UPS card, I'm using the same one for both tests. : || nomad at castle nut-2.7.4 [93] ; please drivers/snmp-ups -a nutdev1 -x secLevel=authPriv -x secName=nut -x authProtocol=MD5 -x privProtocol=DES -x authPassword=NutScan at Password43LongerWord -x privPassword=NutScan at Password43LongerWord -k Network UPS Tools - Generic SNMP UPS driver 0.97 (2.7.4) No matching MIB found for sysOID '.1.3.6.1.4.1.318.1.3.2.10'...

Having trouble configuring nut 2.7.4 on Fedora 25, with a new Tripp Lite UPS. I'm running XFCE, and XFCE's Power Manager sees the UPS just fine. lsusb gives: Bus 006 Device 002: ID 09ae:3016 Tripp Lite nut-scanner -U has no issues either: # nut-scanner -U Scanning USB bus. [nutdev1] driver = "usbhid-ups" port = "auto" vendorid = "09AE" productid = "3016" product = "TRIPP LITE UPS" serial = "2643FVLSM871900817" vendor = "Tripp Lite" bus = "006" I took this and placed it in ups.conf, but up...

Hello! I tried NUT 2.6.5-1 (Windows port) with my APC Back UPS ES. It seems I have configured NUT properly, nut-scanner found my UPS: [nutdev1] driver = "usbhid-ups" port = "auto" vendorid = "051D" productid = "0002" product = "Back-UPS ES 525 FW:851.t3.I USB FW:t3" serial = "8B0745R23575 " vendor = "American Power Con...

...I have tried with my printer's USB cable and seen the same thing. I then tried it on my laptop (also on Fedora 32) with the same result. To me this eliminates my PC and the cabling. 2. The device is detected by "nut-scanner -U" as:root at fedora ~]# nut- scanner -UScanning USB bus.[nutdev1] driver = "usbhid-ups" port = "auto" vendorid = "0463" productid = "FFFF" product = "5E" bus = "002"I have put that exact info into /etc/ups/ups.conf - it's the only info not commented with a # in the file. I changed the name to eato...

...Mon Feb 16 13:46:11 MSK 2015 x86_64 Intel(R) Celeron(R) CPU 1037U @ 1.80GHz GenuineIntel GNU/Linux Network UPS Tools 2.7.2 1) USB connection partially works using usbhid-ups driver, the problem is that I can't issue any command to the UPS. Any command returns ERR CMD-NOT-SUPPORTED error. [nutdev1] driver = "usbhid-ups" port = "auto" vendorid = "06DA" productid = "FFFF" product = "HID UPS" serial = "S42140930054" vendor = "PPC" bus = "002" #...

..., 2015, at 1:16 PM, James Hammond <james_r_hammond at hotmail.com> wrote: > I am running Ubuntu 14.04 and using NUT version 2.73 installed from apt-get package. Hmm, the version below says 2.7.1, not 2.7.3. > Driver debug output: > > root at unifi:/lib/nut# ./blazer_usb -DD -a nutdev1 > Network UPS Tools - Megatec/Q1 protocol USB driver 0.10 (2.7.1) > To get the drivers hyouko mentioned on Ubuntu, the easiest way might be to use a PPA: https://launchpad.net/~clepple/+archive/ubuntu/nut (the strange version number in the PPA is because the packages were built from Git j...

...ere any way I could use that value to differentiate between them? > > I cannot change bus, this is on a raspberry pi have you tried to run 'nut-scanner -U' to find out the serial number of the UPS, so that you can use it to identify each device: # nut-scanner -U Scanning USB bus. [nutdev1] driver = "usbhid-ups" port = "auto" vendorid = "051D" productid = "0002" product = "Back-UPS BR 800 FW:9.o4 .I USB FW:o4" serial = "3B763X76344" # <<<...

> >> # nut-scanner >> Cannot load USB library (/usr/lib64/libusb-1.0.so.0.1.0) : /usr/lib64/libusb-1.0.so.0.1.0: undefined symbol: usb_get_string_simple. USB search disabled. > > Although I suspect that the USB portion of nut-scanner could probably be replaced with a small shell script that parses the output of lsusb, this shouldn't be too hard to fix. Logged, in case it

.../usr/sbin/upsdrvctl start Network UPS Tools – UPS driver controller 2.7.2 Network UPS Tools – Generic SNMP UPS driver 0.72 (2.7.2) No support device detected Driver failed to start (exit status=1) But nut-scanner finds the UPS # nut-scanner -S -s 192.168.24.9 Scanning SNMP bus. [nutdev1]                 driver = “snmp-ups”                 port = “192.168.24.9”                 desc = “Smart-UPS SRT                   3000”                 mibs = “ictf”                 community = “public” [nutdev2]                 driver = “snmp-ups”                 port = “192.168.24.9”   ...