[Nut-upsuser] Powerware 9155 with SNMP card

Bernd Markgraf Bernd.Markgraf at med.ovgu.de
Fri Aug 10 08:37:57 UTC 2007


Morning,

after my questions yesterday I did a little detective work... First of
all it's thanks to the nice and clean style of NUT that i found what
I've been looking for!
So here's what's going wrong:

snmp-ups -DDDDDDDDD -a ups2 gives me this:

Network UPS Tools - Multi-MIBS SNMP UPS driver 0.42 ()
debug level is '9'
SNMP UPS driver : entering upsdrv_initups()
SNMP UPS driver : entering nut_snmp_init(snmp-ups, 149.203.91.170, v1,
power)
SNMP UPS driver : entering load_mib2nut(pw)
load_mib2nut: using pw mib
Detected 9155-12-NHS-8        on host 149.203.91.170 (mib: pw 0.5)
SNMP UPS driver : entering upsdrv_initinfo()
su_ups_get: ups.mfr 1.3.6.1.4.1.534.1.1.1.0
SNMP UPS driver : entering su_setinfo(ups.mfr)
=> value: Powerware Corporation
su_ups_get: ups.model 1.3.6.1.4.1.534.1.1.2.0
SNMP UPS driver : entering su_setinfo(ups.model)
=> value: 9155-12-NHS-8       
su_ups_get: ups.firmware 1.3.6.1.4.1.534.1.1.3.0
SNMP UPS driver : entering su_setinfo(ups.firmware)
=> value:   INV: 2.28  IFC: 1.10
su_ups_get: ups.firmware.aux 1.3.6.1.2.1.33.1.1.4.0
SNMP UPS driver : entering su_setinfo(ups.firmware.aux)
=> value: ConnectUPS Web/SNMP Card V4.22
su_ups_get: ups.serial 1.3.6.1.2.1.33.1.1.5.0
SNMP UPS driver : entering su_setinfo(ups.serial)
=> value: ID: 351526          , Msg: 1024225         
su_ups_get: ups.power 1.3.6.1.4.1.534.1.4.4.1.4.0
SNMP UPS driver : entering su_setinfo(ups.power)
=> value: 1428.0
su_ups_get: ups.status 1.3.6.1.4.1.534.1.4.5.0
SNMP UPS driver : entering su_status_set()
su_find_infoval: no matching INFO_* value for this OID value (9)
=> value: 9
su_ups_get: ups.status 1.3.6.1.2.1.33.1.2.1.0
SNMP UPS driver : entering su_status_set()
su_find_infoval: found  (value: 2)
=> value: 2

So NUT doesn't know what '9' is supposed to be of a status.
Looking into ietfmib.h ietf_pwr_info[] indeed stops at 7.
The missing values from XUPS.mib (provided on the cds that came with the
ups) are:

parallelCapacity(8),    -- normal enhanced by Parallel for Capacity	
			   operation   
parallelRedundant(9),   -- normal enhanced by Redundant Parallel 
			   operation
highEfficiencyMode(10)  -- normal enhanced by High Efficiency mode

So would one go ahead and add these values to ietf_pwr_info[] ?
Or would one rather extend that inside pwmib.h? The latter seems more
obvious to me, since XUPS.mib states that it extends upsOutputSource
from the rfc1628 MIB.

For being the easier way to check for me right now I extend
ietf_pwr_info like this:
        { 8, "PCAP"   /* parallel capacity */ },
        { 9, "PRED"   /* parallel redundancy */ },
        {10, "HEFF"   /* high efficiancy */ },

So I get a status of "PRED" right now, which is indeed what I'm running.
Though I cannot answer the question who NUT behaves with it being not
OL. Some hints here would be appreciated.

As for the missing variables in the MIB these are

su_ups_get: output.current 1.3.6.1.4.1.534.1.4.4.1.3
[ups2] nut_snmp_get: 1.3.6.1.4.1.534.1.4.4.1.3: Error in packet:
(noSuchName) There is no such variable name in this MIB.
=> Failed

Check inphases
inphases is set
su_ups_get: input.L1.realpower 1.3.6.1.4.1.534.1.3.4.1.4.1
[ups2] nut_snmp_get: 1.3.6.1.4.1.534.1.3.4.1.4.1: Error in packet:
(noSuchName) 
There is no such variable name in this MIB.
=> Failed
Check inphases
inphases is set
su_ups_get: input.L2.realpower 1.3.6.1.4.1.534.1.3.4.1.4.2
[ups2] nut_snmp_get: 1.3.6.1.4.1.534.1.3.4.1.4.2: Error in packet:
(noSuchName) 
There is no such variable name in this MIB.
=> Failed
Check inphases
inphases is set
su_ups_get: input.L3.realpower 1.3.6.1.4.1.534.1.3.4.1.4.3
[ups2] nut_snmp_get: 1.3.6.1.4.1.534.1.3.4.1.4.3: Error in packet:
(noSuchName) 
There is no such variable name in this MIB.
=> Failed


I haven't figured them out yet...

 Bernd




More information about the Nut-upsuser mailing list