[Nut-upsdev] lcomtois at ebarrette.com - Bayesian Filter detected spam - Re: Nut-snmp 0.42 vs 0.41
Comtois, Luc
lcomtois at ebarrette.com
Mon Jun 16 12:39:39 UTC 2008
Bonjour Arnaud,
Both servers are using ietf, here is what I am getting form the 2 versions:
***** OLD 0.41*****
battery.runtime: 1080.0
battery.runtime.low: 3
battery.voltage: 154.0
driver.name: snmp-ups
driver.parameter.mibs: ietf
driver.parameter.port: 172.30.1.48
driver.version: 2.0.5
driver.version.internal: 0.41
*Lost* input.frequency: 60.0
*Lost* input.voltage: 115.0
*Lost* output.voltage: 120.0
ups.firmware: ConnectUPS Web/SNMP Card V4.20
ups.firmware.aux: FP: 1.70
*Lost* ups.load: 81.0
ups.mfr: Powerware Corporation
ups.model: Powerware Profile
ups.power: 2290.0
ups.status: OL
***** NEW 0.42 ******
battery.runtime: 1080.0
battery.runtime.low: 3
battery.voltage: 154.0
driver.name: snmp-ups
driver.parameter.mibs: ietf
*new* driver.parameter.pollinterval: 2
driver.parameter.port: 172.30.1.48
driver.version: 2.2.1-
driver.version.internal: 0.42 (mib: ietf 1.2)
*new* input.phases: 2.0
*new* output.frequency: 59.9
*new* output.phases: 2.0
ups.firmware: FP: 1.70
ups.firmware.aux: ConnectUPS Web/SNMP Card V4.20
ups.mfr: Powerware Corporation
ups.model: Powerware Profile
ups.power: 2344.0
*new* ups.serial: ID: TV115W0011, Msg: PF0821114UE0000
ups.status: OL
Luc Comtois
From: Arnaud Quette [mailto:aquette.dev at gmail.com]
Sent: June-13-08 9:29 AM
To: Comtois, Luc
Cc: nut-upsdev at lists.alioth.debian.org
Subject: lcomtois at ebarrette.com - Bayesian Filter detected spam - Re: [Nut-upsdev] Nut-snmp 0.42 vs 0.41
Bonjour Luc,
2008/6/12 Comtois, Luc <lcomtois at ebarrette.com>:
I am using nut-snmp driver on ubuntu 8.04 to query a Powerware ConnectUPS Web/SNMP Card V4.20.
With 0.41 I used to be able to query these field that are now gone with 0.42:
input.frequency
input.voltage
output.voltage
ups.load
Any idea how I can get ups.load back ?
without having dug (I've not taken care of this driver for an eternity), you're possibly using the Powerware mib (at least implicitly by not specifying otherwise), while the ietf one mgith be more suitable to get the needed data...
you should see which mib is used from the upsc output.
and you can override this by adding "mibs=ietf" in your ups.conf.
I'm currently firing up a pw with such a card to check and continue my training on these products. The above assertion seems confirmed...
Arnaud
--
Linux / Unix Expert R&D - MGE Office Protection Systems - http://www.mgeops.com
Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/
Debian Developer - http://people.debian.org/~aquette/
Free Software Developer - http://arnaud.quette.free.fr/
--
Conseiller Municipal - Saint Bernard du Touvet -
http://www.SaintBernardDuTouvet.fr/
en charge de la Communication, de l'Informatique et des Technologies
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.alioth.debian.org/pipermail/nut-upsdev/attachments/20080616/f59a144d/attachment.htm
More information about the Nut-upsdev
mailing list