Nut upsdev - Jan 2010 - CPQPOWER-MIB - nearly there

I have attempted to create cpqpowermib.h for the snmp-ups driver. We use
HP UPSs and version 2 of the firmware for their AF401A management cards
use the CPQPOWER-MIB.

I have attached my current attempt (which builds and almost works
against nut 2.4.1). Once all is working I'll send in the finished
article for consideration. This file is based on ietfmib.h.

There are a couple of issues I'd like input on. Firstly I can't seem to
get input and output voltage to work. The code looks right to me
(compared with the corresponding code in ietfmib.h) but the values are
not showing when running upsc. Perhaps a fresh pair of eyes will spot
what I have missed.

Secondly CPQPOWER-MIB does not have a "Battery Status" field in the
same
sense that IETF does. In order to get around this I have used Battery
Capacity instead. This is a percentage, so I've made values above 20 as
normal, and values of 20 and below as LB. If anyone has strong feelings
regarding this, or a better idea then please reply.

Finally, there is a temperature field (upsEnvAmbientTemp) which shows
the environmental temperature. There is no field for internal
temperature. I have used this value for ups.temperature. Is this what it
is for, or should ups.temperature be left blank?

You can find a description of CPQPOWER-MIB at
http://www.oidview.com/mibs/232/CPQPOWER-MIB.html

Regards,
-  
Philip Ward
Unix Systems Administrator
Ext 7274


-- 
The Sunday Times Scottish University of the Year 2009/2010
The University of Stirling is a charity registered in Scotland, 
 number SC 011159.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: cpqpowermib.h
Type: text/x-chdr
Size: 13157 bytes
Desc: not available
URL:
<http://lists.alioth.debian.org/pipermail/nut-upsdev/attachments/20100127/bd820a7a/attachment.h>

On Wed, Jan 27, 2010 at 9:13 AM, Philip Ward <p.g.ward at stir.ac.uk>
wrote:
> There are a couple of issues I'd like input on. Firstly I can't
seem to
> get input and output voltage to work. The code looks right to me
> (compared with the corresponding code in ietfmib.h) but the values are
> not showing when running upsc. Perhaps a fresh pair of eyes will spot
> what I have missed.
Hi Philip,

In the cpqpower_mib array, the #define'd names for the voltage and
current OIDs are listed with a ".1", ".2" and ".3"
suffix for each of
the three phases. Is your UPS a 3-phase unit? The URL for the MIB
shows CPQPOWER_OID_IN_VOLTAGE as a leaf.
> Secondly CPQPOWER-MIB does not have a "Battery Status" field in
the same
> sense that IETF does. In order to get around this I have used Battery
> Capacity instead. This is a percentage, so I've made values above 20 as
> normal, and values of 20 and below as LB. If anyone has strong feelings
> regarding this, or a better idea then please reply.
Not sure if snmp-ups has this as well, but the usbhid-ups code allows
you to specify mapping functions. Maybe one of the other developers
has worked with this on and can comment further.
> Finally, there is a temperature field (upsEnvAmbientTemp) which shows
> the environmental temperature. There is no field for internal
> temperature. I have used this value for ups.temperature. Is this what it
> is for, or should ups.temperature be left blank?
We do have a separate ambient.temperature variable. That said, what is
your best guess as to the origin of that temperature value? If it is
mislabeled as an internal temperature (that is, somewhat hotter than
ambient), then "ups.temperature" might be a better name (probably with
a comment in the code in case someone runs across a different version
of the firmware). If it does look like ambient temperature,
ambient.temperature is the better variable name.

-- 
- Charles Lepple