[Nut-upsdev] Re old message CPQPOWER-MIB - nearly there (using snmp-ups with HP AH401A management card)

Fri Jan 6 13:53:14 UTC 2012

Hi Jack,

2012/1/5 Jack Challen <jack.challen at ocsl.co.uk>

> Hi,
>
> This appears to be related to a thread from January 2010:
> http://lists.alioth.debian.**org/pipermail/nut-upsdev/2010-**
> January/004470.html<http://lists.alioth.debian.org/pipermail/nut-upsdev/2010-January/004470.html>
>
> NB: This is on an HP-UX 11.31 box, using a self compiled and packaged
> version of NUT 2.6.3, and net-snmp v5.7.1. Therefore some of the search
> paths and things like that may well be wrong because I've done something
> dumb. I'm also only just getting started with NUT on account of finding the
> HP tools don't appear to do the right thing. Therefore, my post may in fact
> be unwanted gibberish.
>
> I've got an HP "R5500 XR" UPS with an additional network-capable
> management card (AH401A). On using the client to talk to it I get the
> following output:
>
> # /usr/local/ups/bin/upsdrvctl start
> Network UPS Tools - UPS driver controller 2.6.3
> Network UPS Tools - Generic SNMP UPS driver 0.58 (2.6.3)
> MIB search path: //.snmp/mibs:/usr/local/share/**snmp/mibs
> Cannot find module (SNMPv2-MIB): At line 0 in (none)
> Cannot find module (IF-MIB): At line 0 in (none)
> Cannot find module (IP-MIB): At line 0 in (none)
> Cannot find module (TCP-MIB): At line 0 in (none)
> Cannot find module (UDP-MIB): At line 0 in (none)
> Cannot find module (HOST-RESOURCES-MIB): At line 0 in (none)
> Cannot find module (NOTIFICATION-LOG-MIB): At line 0 in (none)
> Cannot find module (DISMAN-EVENT-MIB): At line 0 in (none)
> Cannot find module (DISMAN-SCHEDULE-MIB): At line 0 in (none)
> Cannot find module (UCD-SNMP-MIB): At line 0 in (none)
> Cannot find module (UCD-DEMO-MIB): At line 0 in (none)
> Cannot find module (SNMP-TARGET-MIB): At line 0 in (none)
> Cannot find module (NET-SNMP-AGENT-MIB): At line 0 in (none)
> Cannot find module (HOST-RESOURCES-TYPES): At line 0 in (none)
> Cannot find module (SNMP-MPD-MIB): At line 0 in (none)
> Cannot find module (SNMP-USER-BASED-SM-MIB): At line 0 in (none)
> Cannot find module (SNMP-FRAMEWORK-MIB): At line 0 in (none)
> Cannot find module (SNMP-VIEW-BASED-ACM-MIB): At line 0 in (none)
> Cannot find module (SNMP-COMMUNITY-MIB): At line 0 in (none)
> Cannot find module (NET-SNMP-PASS-MIB): At line 0 in (none)
> Cannot find module (NET-SNMP-EXTEND-MIB): At line 0 in (none)
> Cannot find module (UCD-DLMOD-MIB): At line 0 in (none)
> Cannot find module (SNMP-NOTIFICATION-MIB): At line 0 in (none)
> Cannot find module (SNMPv2-TM): At line 0 in (none)
> Cannot find module (NET-SNMP-VACM-MIB): At line 0 in (none)
>

these are messages from Net-SNMP itself.

> No matching MIB found for sysOID '.1.3.6.1.4.1.232.165.3'! Please report
> it to NUT developers, with the 'mib' paramater for your devices
>

the "No matching MIB..." msg is misleading.
But I had to make it bold enough in order to improve quickly the situation.
It seems to work.
In fact, the new "sysOID" method to match MIB is not working for you, since
the sysOID value for this MIB was not known... until now ;-)
I've just fixed it in the trunk (r3378) with your reported sysOID value.
And also adjusted the message (r3379).

> Detected R5500 XR on host 192.168.24.101 (mib: cpqpower 1.0)
> [r5500] snmp_ups_walk: data stale for ups.realpower
> [r5500] snmp_ups_walk: data stale for input.voltage
> [r5500] snmp_ups_walk: data stale for input.current
> [r5500] snmp_ups_walk: data stale for input.realpower
>

nothing really harming there, only few data that can be refreshed.

> That output suggests to me that the MIB for this UPS is missing or
> incomplete. I tried copying in the file:
> ftp://ftp.hp.com/pub/softlib2/**software1/pubsw-windows/**
> p104049210/v69218/CPQPOWER1.**64.MIB<ftp://ftp.hp.com/pub/softlib2/software1/pubsw-windows/p104049210/v69218/CPQPOWER1.64.MIB>
> to /usr/local/share/snmp/mibs in an attempt to fix it, but that doesn't
> seem to change anything.
>
>
> Happily, upsc seems to communicate successfully:
> # ./upsc r5500
> ambient.temperature: 22.0
> battery.charge: 97.00
> battery.current: 0.00
> battery.runtime: 46800.00
> battery.voltage: 24.60
> device.mfr: Hewlett-Packard
> device.model: R5500 XR
> device.type: ups
> driver.name: snmp-ups
> driver.parameter.pollinterval: 2
> driver.parameter.port: 192.168.24.101
> driver.version: 2.6.3
> driver.version.internal: 0.58 (mib: cpqpower 1.0)
> input.frequency: 50.00
> input.phases: 1.00
> input.quality: 0.00
> output.frequency: 50.00
> output.phases: 1.00
> ups.firmware:  2.08
> ups.load: 49.00
> ups.mfr: Hewlett-Packard
> ups.model: R5500 XR
> ups.model.aux: 12
> ups.status: OL DISCHRG
> ups.test.result: Done and error
> ups.type: normal
> #
>
> This UPS actually has dud batteries, which should explain the "error"
> result.
>
> So, my questions:
>
> Should the snmp-ups driver report this error?
> Is it fixable with that MIB file?
> Does that MIB file need to be included in a different way, or is it any
> use to you guys?
>

As per my above comment, everything is fine.
An improvement is even on the way, to speed up init time.
I would be pleased if you could give a test to the trunk, to fully validate
the fix for you.

cheers,
Arnaud
-- 
Linux / Unix Expert R&D - Eaton - http://powerquality.eaton.com
Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/
Debian Developer - http://www.debian.org
Free Software Developer - http://arnaud.quette.free.fr/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.alioth.debian.org/pipermail/nut-upsdev/attachments/20120106/e69548c5/attachment.html>