Nut upsdev - Nov 2006 - apcsmart and ambient data (was: NUT and MonAMI plugin)

Hi Paul,
> I have another NUT client for your client-projects[1] page: MonAMI[2].
> 
> MonAMI aims to be a "universal sensor framework".  The data
gathered
from 
> MonAMI's NUT plugin can be sent to any of the output plugins.
Currently,
> these include Ganglia, Nagios, KSysguard and a file-logger (amongst 
others).

interesting though I've not had time to investigate more.
I've just added a new entry on the client projects page.
Thanks for your work on this point. 
> As an aside, I've configured NUT to talk to our APC-8000[3], which
comes
with 
> an "AP9619" [4] expansion card.  This card has an external
temperature
probe, 
> but it doesn't seem to appear in the variables NUT returns: the
UPS's
> internal temperature is mentioned, but no 
"ambient.temperature.measured". 
> I've copied the output below.
> 
> Should the external probe's temperature be reported or does the 
smart-apc 
> driver and/or the serial interface not support this?
in theory, we have the ambient.* collection (check 
http://eu1.networkupstools.org/doc/2.0.1/new-names.html)
to report such data. And the apcsmart driver seems to support the ambient 
data.
So, so the problem might sit in the sensor data acquisition.
But I'm not the right person to follow up. Maybe some other NUT developers 
will be able to...
> ...
> 
> [1] http://www.networkupstools.org/client-projects/
> [2] http://monami.sourceforge.net/
> [3] 
http://www.apc.com/resource/include/techspec_index.cfm?base_sku=SURT8000RMXLI
> [4] 
http://www.apc.com/resource/include/techspec_index.cfm?base_sku=AP9619
> 
> BEGIN LIST VAR APC-8000RMXLI
> VAR APC-8000RMXLI battery.alarm.threshold "0"
> VAR APC-8000RMXLI battery.charge "100.0"
> VAR APC-8000RMXLI battery.charge.restart "00"
> VAR APC-8000RMXLI battery.date "07/01/06"
> VAR APC-8000RMXLI battery.packs "001"
> VAR APC-8000RMXLI battery.packs.bad "000"
> VAR APC-8000RMXLI battery.runtime "1500"
> VAR APC-8000RMXLI battery.runtime.low "120"
> VAR APC-8000RMXLI battery.voltage "217.0"
> VAR APC-8000RMXLI battery.voltage.nominal "192"
> VAR APC-8000RMXLI driver.name "apcsmart"
> VAR APC-8000RMXLI driver.parameter.port "/dev/ttyS0"
> VAR APC-8000RMXLI driver.version "2.0.3"
> VAR APC-8000RMXLI driver.version.internal "1.99.7"
> VAR APC-8000RMXLI input.frequency "50.05"
> VAR APC-8000RMXLI input.quality "FF"
> VAR APC-8000RMXLI input.sensitivity "A"
> VAR APC-8000RMXLI input.transfer.high "253"
> VAR APC-8000RMXLI input.transfer.low "161"
> VAR APC-8000RMXLI input.transfer.reason "S"
> VAR APC-8000RMXLI input.voltage "244.8"
> VAR APC-8000RMXLI input.voltage.maximum "244.8"
> VAR APC-8000RMXLI input.voltage.minimum "240.4"
> VAR APC-8000RMXLI output.current "12.72"
> VAR APC-8000RMXLI output.voltage "231.6"
> VAR APC-8000RMXLI output.voltage.target.battery "230"
> VAR APC-8000RMXLI ups.delay.shutdown "020"
> VAR APC-8000RMXLI ups.delay.start "000"
> VAR APC-8000RMXLI ups.display.language "E"
> VAR APC-8000RMXLI ups.firmware "477.15.W"
> VAR APC-8000RMXLI ups.id "UPS_IDEN"
> VAR APC-8000RMXLI ups.load "042.0"
> VAR APC-8000RMXLI ups.mfr "APC"
> VAR APC-8000RMXLI ups.mfr.date "07/01/06"
> VAR APC-8000RMXLI ups.model "Smart-UPS RT 8000 XL    "
> VAR APC-8000RMXLI ups.serial "NS0627025684  "
> VAR APC-8000RMXLI ups.status "OL"
> VAR APC-8000RMXLI ups.temperature "027.4"
> VAR APC-8000RMXLI ups.test.interval "1209600"
> VAR APC-8000RMXLI ups.test.result "NO"
> END LIST VAR APC-8000RMXLI
Arnaud Quette
--
Linux / Unix Expert - MGE UPS SYSTEMS - R&D Dpt
Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/
Debian Developer - http://people.debian.org/~aquette/
OpenSource Developer - http://arnaud.quette.free.fr/

On Thursday 23 November 2006 13:38, Arnaud QUETTE wrote:
> > As an aside, I've configured NUT to talk to our APC-8000[3], which
comes
> > with
> > an "AP9619" [4] expansion card.  This card has an external
temperature
> > probe, but it doesn't seem to appear in the variables NUT returns.
[...]
> in theory, we have the ambient.* collection (check
> http://eu1.networkupstools.org/doc/2.0.1/new-names.html)
> to report such data. And the apcsmart driver seems to support the ambient
> data.
> So, so the problem might sit in the sensor data acquisition.
> But I'm not the right person to follow up. Maybe some other NUT
developers
> will be able to...
Here's some further information:  I can see the external sensor when doing a
snmpwalk on the UPS' own external NIC (on the AP9619 card).

The command I use is:

snmpwalk -M /root/MIBs:/usr/share/snmp/mibs -m ALL -v1 -c public <UPS IP 
address> iso.org.dod.internet.private.enterprises.apc

where /root/MIBs contains the powernet MIB (v3.8.5) available from:
  ftp://ftp.apcc.com/apc/public/s477.15.Woftware/pnetmib/mib/385

I've copied part of the snmp tree below:

PowerNet-MIB::iemStatusProbesNumProbes.0 = INTEGER: 1
PowerNet-MIB::iemStatusProbeNumber.1 = INTEGER: 1
PowerNet-MIB::iemStatusProbeName.1 = STRING: "Integrated"
PowerNet-MIB::iemStatusProbeStatus.1 = INTEGER: connected(2)
PowerNet-MIB::iemStatusProbeCurrentTemp.1 = INTEGER: 28
PowerNet-MIB::iemStatusProbeTempUnits.1 = INTEGER: celsius(1)
PowerNet-MIB::iemStatusProbeCurrentHumid.1 = INTEGER: -1
PowerNet-MIB::iemStatusProbeHighTempViolation.1 = INTEGER: disabled(3)
PowerNet-MIB::iemStatusProbeLowTempViolation.1 = INTEGER: disabled(3)
PowerNet-MIB::iemStatusProbeHighHumidViolation.1 = INTEGER: disabled(3)
PowerNet-MIB::iemStatusProbeLowHumidViolation.1 = INTEGER: disabled(3)

If it helps any, the exact UPS model string is "Smart-UPS RT 8000 XL"
and it
has a firmware revision "477.15.W".

Cheers,

Paul.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url :
http://lists.alioth.debian.org/pipermail/nut-upsdev/attachments/20061127/905021c3/attachment.pgp

On Thursday 23 November 2006 13:38, Arnaud QUETTE wrote:
> > I have another NUT client for your client-projects[1] page: MonAMI[2].
[...]
>
> interesting though I've not had time to investigate more.
> I've just added a new entry on the client projects page.
> Thanks for your work on this point.
No problem :-)

BTW, I've had a spring-clean and the code in CVS (to interface with NUT) is 
now much better than in the latest release (v0.6).  We should be releasing a 
new version "soon", but if anyone is interested in trying MonAMI,
I'd
recommend compiling from CVS or waiting for the next release.  If people 
would like, I can announce the new version on this list.

What I hope is a simple question: is it possible to lock-out unauthenticated 
logins from asking monitoring questions (i.e. "LIST VAR xxx")?  It
wasn't
clear to me from the docs whether LIST VAR xxx will always succeed or whether 
one can configure a upsd server so it requires a successful login before 
allowing these queries.

Currently, there is no support within the monami NUT plugin to allow people to 
log in.  It would be (relatively) straight forward to add this; but if the 
information is always available there doesn't seem any point in adding this 
extra functionality.

Cheers,

Paul.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url :
http://lists.alioth.debian.org/pipermail/nut-upsdev/attachments/20061127/c8043859/attachment.pgp