search for: ups2

...x81 received from .1.3.6.1.4.1.318.1.1.2.1.1.0 [ups1-1] unhandled ASN 0x81 received from .1.3.6.1.4.1.318.1.1.2.1.2.0 [ups1-1] unhandled ASN 0x81 received from .1.3.6.1.4.1.318.1.1.10.2.3.2.1.4.1 [ups1-1] unhandled ASN 0x81 received from .1.3.6.1.4.1.318.1.1.10.2.3.2.1.6.1 42.773758 Starting UPS: ups2-1 Network UPS Tools - Generic SNMP UPS driver 0.72 (2.7.2) Detected Smart-UPS 5000 on host ups2-1.[redacted] (mib: apcc 1.2) [ups2-1] unhandled ASN 0x81 received from .1.3.6.1.4.1.318.1.1.1.9.2.3.1.3.1.1.1 [ups2-1] unhandled ASN 0x81 received from .1.3.6.1.4.1.318.1.1.1.9.2.3.1.3.1.1.2 [ups2-1] unh...

...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" driver = snmp-ups mibs = apcc port = [ups2...] snmp_version = v1 community = [xxx] # snmp_version = v3 # secLevel = authPriv # secName = [xxx] # authPassword = [xxx] # authProtocol = MD5 # privP...

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

...e UPS is doing an integer divide by 60 on the number of seconds given by the command. That is why the request for a 59 second delay resulted in no delay at all. === I see the same behavior with this model. The following command excerpts from the upssched.conf file work as expected: AT LOWBATT ups2 at 127.0.0.1 START-TIMER ups2-lowbattwarn 1 AT ONBATT ups2 at 127.0.0.1 START-TIMER ups2-onbatt-early 60 AT ONBATT ups2 at 127.0.0.1 START-TIMER ups2-onbatt-final 180 AT ONBATT ups2 at 127.0.0.1 EXECUTE ups2-start-batt AT ONLINE ups2 at 127.0.0.1 CANCEL-TIMER ups2-onbatt-ea...

...irection of the `clone` drivers, although using the modern `upsdrvquery.c` API. Essentially I am parsing the protocol lines directly reading from the driver sockets, as the clone drivers do. As for ups.conf, I start up as follows without problems: [ups] driver = dummy-ups port = /etc/nut/5E.dev [ups2] driver = dummy-ups port = /etc/nut/APC.dev [failover] driver = failover port = dummy-ups-ups,dummy-ups-ups2 Is this what you had in mind? Appreciate any pointers regarding the `upsdrvctl` and `nutshutdown` specifics. Sebastian Am Mo., 12. Mai 2025 um 15:53 Uhr schrieb Jim Klimov < jimklimov...

...> modern `upsdrvquery.c` API. > Essentially I am parsing the protocol lines directly reading from the > driver sockets, as the clone drivers do. > > As for ups.conf, I start up as follows without problems: > > [ups] > driver = dummy-ups > port = /etc/nut/5E.dev > > [ups2] > driver = dummy-ups > port = /etc/nut/APC.dev > > [failover] > driver = failover > port = dummy-ups-ups,dummy-ups-ups2 > > Is this what you had in mind? > Appreciate any pointers regarding the `upsdrvctl` and `nutshutdown` > specifics. > > Sebastian > > A...

...PC Smartups 1500 and two 1000. Because of the number of ups, i connected them using usb cables. I'm using Debian Etch AMD64 and nut 2.2.0 from testing (already tried 2.0 from stable, but had problems reading the ups serials and all the following problems of 2.2). This is my ups.conf: [ups2] driver = usbhid-ups port = auto vendorid = 051d serial = AS0413113031 offdelay=5 ondelay=30 sdorder = 4 The output of "upsrw ups2 at localhost": [battery.charge.low] Remaining battery level when UPS switches to LB (percent) Type: STRING Value: 10 [ba...

...(sockets) in > comma-separated > form from the `port` variable and keeps track of these drivers, monitoring > their information and failing over where necessary. Basic configuration > looks > like: > > [failover] > driver = failover > port = dummy-ups-ups,dummy-ups-ups2 > > I could well picture a multiplexing driver accepting a similar format, > merging > variables of both drivers and resolving conflicts by port argument order > (`dummy-ups-ups`, then `dummy-ups-ups2`) in its most basic form. > > Additionally, this could be extended with prefe...

...out managing two UPSes under NUT. I have two similar model APC usb-connected UPSes to work with, but don't know how to manage them simultaneously from under Windows. Long story short, my ups.conf looks like this: --- ups.conf --- [ups1] driver= usbhid-ups port= auto serial=AS1054340323 [ups2] driver= usbhid-ups port= auto serial=AS1026662626 --- ups.conf --- I tried all the combinations with vendorid, productid, vendor, product as in the manual for usbhid-ups and libusb's test --- TestLibUsb --- - Manufacturer : American Power Conversion - Product : Smart-UPS X 1500 FW...

Hi, I didn't found an answer for my question in NUT documentation/FAQ or this mailing list archive so I?m posting it here. I want to start a timer only if both of my UPSes remain on battery. Not just one, both. My UPSes are: - ups1@host-a - ups2@host-b Is it possible to use something like this in upssched.conf? AT ONBATT ups1.* && ups2.* START-TIMER onbattwarn 180 Thanks, Dumitru

...ically, my failover logic takes driver names (sockets) in comma-separated form from the `port` variable and keeps track of these drivers, monitoring their information and failing over where necessary. Basic configuration looks like: [failover] driver = failover port = dummy-ups-ups,dummy-ups-ups2 I could well picture a multiplexing driver accepting a similar format, merging variables of both drivers and resolving conflicts by port argument order (`dummy-ups-ups`, then `dummy-ups-ups2`) in its most basic form. Additionally, this could be extended with preference arguments, such as: pref...

...; Essentially I am parsing the protocol lines directly reading from the >> driver sockets, as the clone drivers do. >> >> As for ups.conf, I start up as follows without problems: >> >> [ups] >> driver = dummy-ups >> port = /etc/nut/5E.dev >> >> [ups2] >> driver = dummy-ups >> port = /etc/nut/APC.dev >> >> [failover] >> driver = failover >> port = dummy-ups-ups,dummy-ups-ups2 >> >> Is this what you had in mind? >> Appreciate any pointers regarding the `upsdrvctl` and `nutshutdown` >> sp...

...col lines directly reading from the >>> driver sockets, as the clone drivers do. >>> >>> As for ups.conf, I start up as follows without problems: >>> >>> [ups] >>> driver = dummy-ups >>> port = /etc/nut/5E.dev >>> >>> [ups2] >>> driver = dummy-ups >>> port = /etc/nut/APC.dev >>> >>> [failover] >>> driver = failover >>> port = dummy-ups-ups,dummy-ups-ups2 >>> >>> Is this what you had in mind? >>> Appreciate any pointers regarding the `upsd...

...erWare 9155 UPS (3 input phaes, one output phase), running parallel. Since I didn't want to install a Windows box to run Powerwares software I now went nut(s) ;-) So far things look pretty good, snmp-ups talks to both ups using the pw mib. Though I get these messages, when I start the driver: [ups2] nut_snmp_get: 1.3.6.1.4.1.534.1.4.4.1.3: Error in packet: (noSuchName) There is no such variable name in this MIB. [ups2] nut_snmp_get: 1.3.6.1.4.1.534.1.3.4.1.4.1: Error in packet: (noSuchName) There is no such variable name in this MIB. [ups2] nut_snmp_get: 1.3.6.1.4.1.534.1.3.4.1.4.2: Error in...

...erWare 9155 UPS (3 input phaes, one output phase), running parallel. Since I didn't want to install a Windows box to run Powerwares software I now went nut(s) ;-) So far things look pretty good, snmp-ups talks to both ups using the pw mib. Though I get these messages, when I start the driver: [ups2] nut_snmp_get: 1.3.6.1.4.1.534.1.4.4.1.3: Error in packet: (noSuchName) There is no such variable name in this MIB. [ups2] nut_snmp_get: 1.3.6.1.4.1.534.1.3.4.1.4.1: Error in packet: (noSuchName) There is no such variable name in this MIB. [ups2] nut_snmp_get: 1.3.6.1.4.1.534.1.3.4.1.4.2: Error in...

Hello, We have two APC Back-UPS RS 1500 USB stuff, and i've got a bit of a problem with it and NUT. The usbdevs output: addr 2: Back-UPS RS 1500 FW:8.g8 .I USB FW:g8, American Power Conversion addr 3: Back-UPS RS 1500 FW:8.g8 .I USB FW:g8, American Power Conversion (UPS1 and UPS2) I've configured our NUT system to monitor the UPSes, and it went very fine till the time had arrived for a test. UPS unpower (-> ONBAT), and test what NUT does to the boxes connected to it. After I've unplugged the power cable of UPS1, nut started not to notice that on its cgi interfa...

Wow, that's quite the tale! I take away from this: There is a real example of wanting to merge two information sources. It's very complicated. Anybody wishing to succeed in a very complicated situation needs to really pay attention, to twice as many things as they thought when they started. It's unclear how to generalize from this to a solution that will work for the

...get from a snmpwalk is like this (for 6 devices): NUT-MIB::deviceIndex.1 = INTEGER: 1 NUT-MIB::deviceIndex.2 = INTEGER: 2 NUT-MIB::deviceIndex.3 = INTEGER: 3 NUT-MIB::deviceIndex.4 = INTEGER: 4 NUT-MIB::deviceIndex.5 = INTEGER: 5 NUT-MIB::deviceIndex.6 = INTEGER: 6 NUT-MIB::deviceName.1 = STRING: ups2 NUT-MIB::deviceName.2 = STRING: xxx NUT-MIB::deviceName.3 = STRING: upsoutlet NUT-MIB::deviceName.4 = STRING: ups3p1 NUT-MIB::deviceName.5 = STRING: ups3p2 NUT-MIB::deviceName.6 = STRING: ups3 NUT-MIB::deviceDesc.1 = STRING: UPS2 10 KVA Lacerda Titan Black tri-mono 10KVA (220v) Serial A08823221 NUT...

...get from a snmpwalk is like this (for 6 devices): NUT-MIB::deviceIndex.1 = INTEGER: 1 NUT-MIB::deviceIndex.2 = INTEGER: 2 NUT-MIB::deviceIndex.3 = INTEGER: 3 NUT-MIB::deviceIndex.4 = INTEGER: 4 NUT-MIB::deviceIndex.5 = INTEGER: 5 NUT-MIB::deviceIndex.6 = INTEGER: 6 NUT-MIB::deviceName.1 = STRING: ups2 NUT-MIB::deviceName.2 = STRING: xxx NUT-MIB::deviceName.3 = STRING: upsoutlet NUT-MIB::deviceName.4 = STRING: ups3p1 NUT-MIB::deviceName.5 = STRING: ups3p2 NUT-MIB::deviceName.6 = STRING: ups3 NUT-MIB::deviceDesc.1 = STRING: UPS2 10 KVA Lacerda Titan Black tri-mono 10KVA (220v) Serial A08823221 NUT...

...ystems' for both. They're also on the same bus ('Bus 003 Device 063' and 'Bus 003 Device 064') Since there is no flag for manufacturer, I had to go with serial. This is my new ups.conf: [ups1] driver = usbhid-ups port = /dev/usb/hiddev0 serial=000000000 [ups2] driver = usbhid-ups port = /dev/usb/hiddev1 serial=1HCG4700J When I run upsdrvctl start ups1, it starts /lib/nut/usbhid-ups -a ups1 but no -x flag. Starting usbhid-ups manually with the -x serial=000000000 and -DD flag shows: Checking device (0463/FFFF) (003/064) - VendorID:...