[Nut-upsuser] Any word on when the ietf mib will be fixed for liebert?

Maurice Volaski mvolaski at aecom.yu.edu
Mon Jul 27 20:18:23 UTC 2009


At 9:11 AM +0200 7/27/09, Arnaud Quette wrote:
>2009/7/27 Maurice Volaski 
><<mailto:mvolaski at aecom.yu.edu>mvolaski at aecom.yu.edu>
>
>This mib used to work, so is there a way to go back to the version 
>prior to this one without downgrading the whole package?
>
>
>yes, only take the snmp-ups driver from the previous working release.

2.2.2 and 2.0.5 also complain but with fewer errors. 1.5.15 does not 
complain, so it's the one I added. Oddly, this old version doesn't 
seem to like that /var/state/ups directory is owned by user nut. I 
had to manually pass "-u nut" to upsdrvctl to get it to work.

Anyway, now that the script is starting, I'm seeing "failed - got 
[ERR ACCESS-DENIED]" errors  from upsmon, and I don't know why. I 
noted that the configuration has changed. It seems ACLs and ACCEPT 
are no longer used and have been replaced with LISTEN, but I have set 
that.

>provide us back with an SNMP walk so that we can check the exact 
>issue and find a suitable solution.
>this might have something to do with the ".0" suffix...
>starting with the RFC1628 MIB entry point (ie 1.3.6.1.2.1.33) is sufficient.

mib-2.33.1.1.1.0 = STRING: "Liebert Corporation"
mib-2.33.1.1.2.0 = STRING: "GXT2-2000RT120                "
mib-2.33.1.1.3.0 = STRING: "GXT2MR15E-2K3K                "
mib-2.33.1.1.4.0 = STRING: "2.200.1"
mib-2.33.1.1.5.0 = STRING: "upswallleft"
mib-2.33.1.2.1.0 = INTEGER: 2
mib-2.33.1.2.2.0 = INTEGER: 0
mib-2.33.1.2.3.0 = INTEGER: 6
mib-2.33.1.2.4.0 = INTEGER: 100
mib-2.33.1.2.5.0 = INTEGER: 553
mib-2.33.1.3.1.0 = Counter32: 0
mib-2.33.1.3.2.0 = INTEGER: 1
mib-2.33.1.3.3.1.2.1 = INTEGER: 600
mib-2.33.1.3.3.1.3.1 = INTEGER: 114
mib-2.33.1.4.1.0 = INTEGER: 3
mib-2.33.1.4.2.0 = INTEGER: 600
mib-2.33.1.4.3.0 = INTEGER: 1
mib-2.33.1.4.4.1.2.1 = INTEGER: 120
mib-2.33.1.4.4.1.3.1 = INTEGER: 112
mib-2.33.1.5.1.0 = INTEGER: 600
mib-2.33.1.5.2.0 = INTEGER: 1
mib-2.33.1.5.3.1.2.1 = INTEGER: 114
mib-2.33.1.6.1.0 = Gauge32: 0
mib-2.33.1.7.1.0 = OID: mib-2.33.1.7.7.1
mib-2.33.1.7.2.0 = INTEGER: 1
mib-2.33.1.7.3.0 = INTEGER: 6
mib-2.33.1.7.4.0 = ""
mib-2.33.1.7.5.0 = Timeticks: (0) 0:00:00.00
mib-2.33.1.7.6.0 = INTEGER: 0
mib-2.33.1.8.1.0 = INTEGER: 1
mib-2.33.1.8.2.0 = INTEGER: 0
mib-2.33.1.8.3.0 = INTEGER: 0
mib-2.33.1.8.4.0 = INTEGER: 0
mib-2.33.1.8.5.0 = INTEGER: 1
mib-2.33.1.9.1.0 = INTEGER: 120
mib-2.33.1.9.2.0 = INTEGER: 600
mib-2.33.1.9.3.0 = INTEGER: 120
mib-2.33.1.9.4.0 = INTEGER: 600
mib-2.33.1.9.5.0 = INTEGER: 2000
mib-2.33.1.9.7.0 = INTEGER: 2
mib-2.33.1.9.8.0 = INTEGER: 2
-- 

Maurice Volaski, mvolaski at aecom.yu.edu
Computing Support, Rose F. Kennedy Center
Albert Einstein College of Medicine of Yeshiva University



More information about the Nut-upsuser mailing list