[Nut-upsdev] CPQPOWER-MIB contribution
Philip Ward
p.g.ward at stir.ac.uk
Mon Feb 1 12:36:43 UTC 2010
On Mon, 2010-02-01 at 12:15 +0000, Arjen de Korte wrote:
> Why did you remove the three phase support? The unit seems to
> correctly report the number of input- and output phases, so leaving
> that in wouldn't hurt. Even though it's not tested, you already know
> it works for single phase units.
I removed it because requesting a specific 3-phase variable does not
work (at least on the units I have to hand).
Compare the following:
hostadm:/etc/nut# snmpget -v 1 -c public \
ups-pf34-2 .1.3.6.1.4.1.232.165.3.3.4.1.2.1
Error in packet
Reason: (noSuchName) There is no such variable name in this MIB.
Failed object: CPQPOWER-MIB::upsInputVoltage.1
hostadm:/etc/nut# snmpget -v 1 -c public \
ups-pf34-2 .1.3.6.1.4.1.232.165.3.3.4.1.2
CPQPOWER-MIB::upsInputVoltage.1 = INTEGER: 245
This suggests to me that requesting the 3-phase values will cause an
error. Unless I have misunderstood how the driver grabs the values. Does
the SU_INPUT_3 flag tell the driver to ask for (for
example) .1.3.6.1.4.1.232.165.3.3.4.1.2, and then only grab the one that
it asked for?
I'll stick the 3-phase stuff back in if this is the case.
-
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.
More information about the Nut-upsdev
mailing list