Additional question: I noticed on the HP Website that the latest version of "CPQPOWER.MIB" (1.76, dated Sept. 19, 2013) was more recent than the related file (./drivers/compaq-mib.c) in the NUT driver.
Is the MIB structure as implemented on the management card perhaps no longer in line with the NUT driver ? The latest MIB file can be downloaded from the following URL: <https://h20565.www2.hp.com/portal/site/hpsc/template.PAGE/public/psi/swdDetails/?javax.portlet.begCacheTok=com.vignette.cachetoken&javax.portlet.endCacheTok=com.vignette.cachetoken&javax.portlet.prp_bd9b6997fbc7fc515f4cf4626f5c8d01=wsrp-navigationalState%3Didx%3D|swItem%3DMTX_d32e012fd5f14f1fb3e3859897|itemLocale%3D|mode%3D|action%3DdriverDocument&javax.portlet.tpst=bd9b6997fbc7fc515f4cf4626f5c8d01&ac.admitted=1393496865122.876444892.492883150> TIA Cheers. Bye. Ph. A. On 27/02/14 11:06, Philippe Andersson wrote: > Hello list, > > I've installed NUT on an HP blade server, and I try to get it > communicating via SNMP with 2 HP R3000 UPSes, each fitted with a AF465A > management card. To do this, I used the snmp-ups driver, and configured > it for the "cpqpower" MIB. Communication with the UPSes is established. > > My problem is that both UPSes constantly return the "OL OB" status > which, in addition to being nonsensical, drives upsmon crazy (it flips > between the two states every second). > > Here is the upsc output (from one of the UPSes -- they're both similar): > > -----------------------------<cut>-------------------------------- > mcbackup:/etc/ups # upsc R3000-B@localhost > ambient.temperature: 28.0 > ambient.temperature.high: 40.00 > ambient.temperature.low: 0.00 > battery.charge: 99.00 > battery.current: 0.00 > battery.runtime: 7440.00 > battery.voltage: 13.10 > device.mfr: HP > device.model: HP RT3000 G2 UPS > device.serial: 3C83435450 > device.type: ups > driver.name: snmp-ups > driver.parameter.mibs: auto > driver.parameter.pollfreq: 15 > driver.parameter.pollinterval: 2 > driver.parameter.port: mcups1.cal.org > driver.parameter.snmp_version: v1 > driver.version: 2.6.5 > driver.version.data: cpqpower MIB 1.5 > driver.version.internal: 0.68 > input.current: 0.40 > input.frequency: 50.00 > input.phases: 1.00 > input.quality: 2.00 > input.voltage: 209.00 > input.voltage.nominal: 230 > outlet.1.id: 1.00 > outlet.1.status: on > outlet.1.switchable: yes > outlet.2.id: 2.00 > outlet.2.status: on > outlet.2.switchable: yes > outlet.count: 2.00 > outlet.desc: All outlets > outlet.id: 0 > output.current: 0.20 > output.frequency: 50.00 > output.frequency.nominal: 500 > output.phases: 1.00 > output.voltage: 223.00 > output.voltage.nominal: 230 > ups.delay.shutdown: 20 > ups.delay.start: 30 > ups.firmware: 01.06.0026;01.02.0004 > ups.load: 19.00 > ups.mfr: HP > ups.model: HP RT3000 G2 UPS > ups.realpower: 3000.00 > ups.serial: 3C83435450 > ups.status: OL OB <================ !!! > ups.test.result: Unknown > ups.timer.shutdown: 0.00 > ups.timer.start: 0.00 > ups.type: normal > -----------------------------<cut>-------------------------------- > > If I use a MIB browser to inspect the .1.3.6.1.4.1.232.165.3.4.5.0 OID > (defined in ./drivers/compaq-mib.c as "CPQPOWER_OID_POWER_STATUS"), the > value returned by both UPSes is 3, meaning "OL" as defined in > "cpqpower_pwr_info[]" (which is indeed the expected state for the UPS at > present. > > But if I inspect OID .1.3.6.1.4.1.232.165.3.7.3.0 > ("CPQPOWER_OID_ALARM_OB") as suggested by Arnaud, this one returns "1" > on both UPSes (i.e. "OB", as defined in "cpqpower_alarm_ob[]") -- an > information which is clearly inaccurate. Both UPSes are currently on > grid power, as reported by their Web management interface. > > Both UPS management cards (HP P/N AF465A) are on the latest firmware > version (v. 1.01.013). > > My system: > OpenSUSE 13.1 64bit on HP BL460c in a C7000 enclosure > nut-2.6.5-6.1.5.x86_64 > nut-drivers-net-2.6.5-6.1.5.x86_64 > net-snmp-5.7.2-9.1.2.x86_64 > (NUT installed from official OpenSUSE repository) > > UPSes: > UPS Name : HP RT3000 G2 UPS > UPS Part Number : AF468A > UPS Firmware Revision : 01.02.0004 > Communication Board Firmware Revision : 01.06.0026 > Card Firmware revision : 1.01.013 > Card Part Number : AF465A > Card Technical Level : 05 > Card Hardware Revision : BB > > Attached is the captured trace of running the driver in debug mode. > > To me, this look more and more like a bug in the Management card > firmware. Has any one of you already experienced this? Is there a > workaround? > > TIA > > Cheers. Bye. > > Ph. A. > -- *Philippe Andersson* Unix System Administrator IBA Particle Therapy | Tel: +32-10-475.983 Fax: +32-10-487.707 eMail: [email protected] <http://www.iba-worldwide.com>
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Nut-upsuser mailing list [email protected] http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
