[Nut-upsuser] Any word on when the ietf mib will be fixed for liebert?
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
>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 126.96.36.199.2.1.33) is sufficient.
mib-188.8.131.52.1.0 = STRING: "Liebert Corporation"
mib-184.108.40.206.2.0 = STRING: "GXT2-2000RT120 "
mib-220.127.116.11.3.0 = STRING: "GXT2MR15E-2K3K "
mib-18.104.22.168.4.0 = STRING: "2.200.1"
mib-22.214.171.124.5.0 = STRING: "upswallleft"
mib-126.96.36.199.1.0 = INTEGER: 2
mib-188.8.131.52.2.0 = INTEGER: 0
mib-184.108.40.206.3.0 = INTEGER: 6
mib-220.127.116.11.4.0 = INTEGER: 100
mib-18.104.22.168.5.0 = INTEGER: 553
mib-22.214.171.124.1.0 = Counter32: 0
mib-126.96.36.199.2.0 = INTEGER: 1
mib-188.8.131.52.184.108.40.206 = INTEGER: 600
mib-220.127.116.11.18.104.22.168 = INTEGER: 114
mib-22.214.171.124.1.0 = INTEGER: 3
mib-126.96.36.199.2.0 = INTEGER: 600
mib-188.8.131.52.3.0 = INTEGER: 1
mib-184.108.40.206.220.127.116.11 = INTEGER: 120
mib-18.104.22.168.22.214.171.124 = INTEGER: 112
mib-126.96.36.199.1.0 = INTEGER: 600
mib-188.8.131.52.2.0 = INTEGER: 1
mib-184.108.40.206.220.127.116.11 = INTEGER: 114
mib-18.104.22.168.1.0 = Gauge32: 0
mib-22.214.171.124.1.0 = OID: mib-126.96.36.199.7.1
mib-188.8.131.52.2.0 = INTEGER: 1
mib-184.108.40.206.3.0 = INTEGER: 6
mib-220.127.116.11.4.0 = ""
mib-18.104.22.168.5.0 = Timeticks: (0) 0:00:00.00
mib-22.214.171.124.6.0 = INTEGER: 0
mib-126.96.36.199.1.0 = INTEGER: 1
mib-188.8.131.52.2.0 = INTEGER: 0
mib-184.108.40.206.3.0 = INTEGER: 0
mib-220.127.116.11.4.0 = INTEGER: 0
mib-18.104.22.168.5.0 = INTEGER: 1
mib-22.214.171.124.1.0 = INTEGER: 120
mib-126.96.36.199.2.0 = INTEGER: 600
mib-188.8.131.52.3.0 = INTEGER: 120
mib-184.108.40.206.4.0 = INTEGER: 600
mib-220.127.116.11.5.0 = INTEGER: 2000
mib-18.104.22.168.7.0 = INTEGER: 2
mib-22.214.171.124.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