2009/7/27 Maurice Volaski <[email protected]> > 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. Note that Liebert is not registered with SNMP support in our compat list! so we even don't know about that. > * Starting UPS drivers... > Network UPS Tools - UPS driver controller 2.4.1 > Network UPS Tools - Generic SNMP UPS driver 0.44 (2.4.1) > Detected GXT2-2000RT120 on host upswallleft (mib: ietf 1.3) > [upswallleft] nut_snmp_get: 1.3.6.1.2.1.33.1.4.4.1.4.0: Error in packet: > (noSuchName) There is no such variable name in this MIB. > [upswallleft] nut_snmp_get: 1.3.6.1.2.1.33.1.7.4: Error in packet: > (noSuchName) There is no such variable name in this MIB. > [upswallleft] nut_snmp_get: 1.3.6.1.2.1.33.1.2.6.0: Error in packet: > (noSuchName) There is no such variable name in this MIB. > [upswallleft] nut_snmp_get: 1.3.6.1.2.1.33.1.2.7.0: Error in packet: > (noSuchName) There is no such variable name in this MIB. > [upswallleft] nut_snmp_get: 1.3.6.1.2.1.33.1.4.4.1.2.0: Error in packet: > (noSuchName) There is no such variable name in this MIB. > [upswallleft] nut_snmp_get: 1.3.6.1.2.1.33.1.4.4.1.3.0: Error in packet: > (noSuchName) There is no such variable name in this MIB. > [upswallleft] nut_snmp_get: 1.3.6.1.2.1.33.1.4.4.1.4.0: Error in packet: > (noSuchName) There is no such variable name in this MIB. > [upswallleft] nut_snmp_get: 1.3.6.1.2.1.33.1.3.3.1.2.0: Error in packet: > (noSuchName) There is no such variable name in this MIB. > [upswallleft] nut_snmp_get: 1.3.6.1.2.1.33.1.3.3.1.3.0: Error in packet: > (noSuchName) There is no such variable name in this MIB. > [upswallleft] nut_snmp_get: 1.3.6.1.2.1.33.1.3.3.1.4.0: Error in packet: > (noSuchName) There is no such variable name in this MIB. > [upswallleft] nut_snmp_get: 1.3.6.1.2.1.33.1.4.4.1.5.0: Error in packet: > (noSuchName) There is no such variable name in this MIB. > [upswallleft] snmp_ups_walk: data stale for ups.load > 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. cheers, Arnaud -- Linux / Unix Expert R&D - Eaton - http://www.eaton.com/mgeops Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/ Debian Developer - http://www.debian.org Free Software Developer - http://arnaud.quette.free.fr/
_______________________________________________ Nut-upsuser mailing list [email protected] http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
