search for: su_status_set

Here's the first update of ups.status: 0.102449 getting data: ups.status (.1.3.6.1.4.1.232.165.3.4.5.0) 0.102546 su_ups_get: ups.status .1.3.6.1.4.1.232.165.3.4.5.0 0.102646 nut_snmp_get(.1.3.6.1.4.1.232.165.3.4.5.0) 0.104539 SNMP UPS driver : entering su_status_set() 0.104641 su_find_infoval: found OL (value: 3) 0.104730 => value: 3 0.104823 getting data: ups.status (.1.3.6.1.4.1.232.165.3.2.5.0) 0.104919 su_ups_get: ups.status .1.3.6.1.4.1.232.165.3.2.5.0 0.105028 nut_snmp_get(.1.3.6.1.4.1.232.165.3.2.5.0) 0.107134 SNMP UPS driver : ent...

Sorry about that! Chris. Chris Pratt Development Infrastructure Manager T: +44 118 929 4176 | M: +44 7979 854 307 | F: +44 118 929 4001 -----Original Message----- From: Charles Lepple [mailto:clepple at gmail.com] Sent: 16 July 2013 00:32 To: Pratt Chris Subject: Re: [Nut-upsuser] HP R12000/3 UPS reports status as OL DISCHRG OB On Jul 15, 2013, at 9:35 AM, Pratt Chris wrote: > Debug output

Hi all, I recently upgraded an ubuntu jaunty machine with nut 2.4.1 to lucid LTS. The previously working nut configuration is a no-go, but I got it up and running using the snmp-ups executable from the previous install. What it happens (from what I can see at least) is that the status has been changed and it's not read as before. In the 2.4.1 release I had an "OL" string (online, I

...t_phases 0.096130 Check output_phases 0.096136 Check output_phases 0.096142 Check output_phases 0.096149 getting data: ups.status (.1.3.6.1.4.1.232.165.3.4.5.0) 0.096156 su_ups_get: ups.status .1.3.6.1.4.1.232.165.3.4.5.0 0.100990 SNMP UPS driver : entering su_status_set() 0.101016 su_find_infoval: found OL (value: 3) 0.101024 => value: 3 0.101032 getting data: ups.status (.1.3.6.1.4.1.232.165.3.2.5.0) 0.101039 su_ups_get: ups.status .1.3.6.1.4.1.232.165.3.2.5.0 0.107038 SNMP UPS driver : entering su_status_set() 0.107063...

Hi. Back before Christmas Arnaud sent me a patch for the snmp-ups driver for my HP R12000/3 UPS. Unfortunately shortly after I had to take quite a lot of sick leave so wasn't able to progress it, but I'm working on it again now. I'm at the point where I can start the driver with upsdrvctl and start the daemon with upsd. When I check the UPS status though it shows as OL DISCHRG OB,

...for my problem was kinda easy (still need some testing though): found out my ups status is a string, so then I changed the way snmp-ups.c gets the status. Had to change *nut_snmp_get_int *to *nut_snmp_get_str *at around line 3470, then grab fourth char out, use *strtol *function to then send it to *su_status_set *function. I created my copy of *apc-mib.c *with my OID at place, then did cases for 0/1 values and Voil?! (I know I probably need some if's there so other non-string-status UPS's would work with my config but I'm happy nonetheless :)) Matthew ?r., 29 mar 2023 o 13:31 Jim Klimov <...

One good intro to this is https://github.com/networkupstools/nut/blob/master/docs/snmp-subdrivers.txt although it focuses on adding new subdrivers - but more or less the same workflow applies to extending existing ones. Sometimes it helps to generate a new one for a currently-partially-supported device, and then compare with existing subdriver (using meld or similar GUI helps a lot) to port the