Nut upsuser - Nov 2010 - Problem with Megatec DK520 over SNMP (firmware v2.39)

Hi all,
I think the problem is related with the latest nut update (now I'm using
version 2.4.3)

# snmpwalk -Os -c public -v 1 192.168.20.60
[...]
mib-2.33.1.1.1.0 = ""
mib-2.33.1.1.2.0 = ""
mib-2.33.1.1.3.0 = ""
mib-2.33.1.1.4.0 = STRING: "2.39.DK520"
mib-2.33.1.1.5.0 = ""
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: 0
mib-2.33.1.2.4.0 = INTEGER: 98
mib-2.33.1.2.5.0 = INTEGER: 22
mib-2.33.1.2.6.0 = INTEGER: 0
mib-2.33.1.2.7.0 = INTEGER: 25
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: 499
mib-2.33.1.3.3.1.3.1 = INTEGER: 209
mib-2.33.1.3.3.1.4.1 = INTEGER: 0
mib-2.33.1.3.3.1.5.1 = INTEGER: 0
mib-2.33.1.4.1.0 = INTEGER: 1
mib-2.33.1.4.2.0 = INTEGER: 499
mib-2.33.1.4.3.0 = INTEGER: 1
mib-2.33.1.4.4.1.2.1 = INTEGER: 221
mib-2.33.1.4.4.1.3.1 = INTEGER: 0
mib-2.33.1.4.4.1.4.1 = INTEGER: 0
mib-2.33.1.4.4.1.5.1 = INTEGER: 20
mib-2.33.1.5.1.0 = INTEGER: 0
mib-2.33.1.5.2.0 = INTEGER: 0
mib-2.33.1.5.3.1.2.1 = INTEGER: 0
mib-2.33.1.5.3.1.3.1 = INTEGER: 0
mib-2.33.1.5.3.1.4.1 = INTEGER: 0
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: 1
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: -1
mib-2.33.1.8.3.0 = INTEGER: -1
mib-2.33.1.8.4.0 = INTEGER: -1
mib-2.33.1.8.5.0 = INTEGER: 2
mib-2.33.1.9.1.0 = INTEGER: 2200
mib-2.33.1.9.2.0 = INTEGER: 500
mib-2.33.1.9.3.0 = INTEGER: 2200
mib-2.33.1.9.4.0 = INTEGER: 500
mib-2.33.1.9.5.0 = INTEGER: 2860
mib-2.33.1.9.6.0 = INTEGER: 0
mib-2.33.1.9.7.0 = INTEGER: 2
mib-2.33.1.9.8.0 = INTEGER: 2
mib-2.33.1.9.9.0 = INTEGER: 0
mib-2.33.1.9.10.0 = INTEGER: 0

But...

# upsc myups at localhost

battery.charge: 98.00
battery.current: 0.00
battery.runtime: 0.00
battery.runtime.low: 2
battery.temperature: 25.00
battery.voltage: 2.20
device.mfr:
device.model:
device.serial:
device.type: ups
driver.name: snmp-ups
driver.parameter.mibs: ietf
driver.parameter.pollinterval: 2
driver.parameter.port: 192.168.20.60
driver.parameter.snmp_version: v2c
driver.version: 2.4.3
driver.version.internal: 0.47 (mib: ietf 1.3)
input.current: 0.00
input.frequency: 50.00
input.phases: 1.00
input.quality: 0.00
input.realpower: 0.00
input.voltage: 209.00
output.current: 0.00
output.frequency: 50.00
output.phases: 1.00
output.power: 0.00
output.voltage: 221.00
ups.firmware:
ups.firmware.aux: 2.39.DK520
ups.load: 21.00
ups.mfr:
ups.model:
ups.serial:
ups.status:


So "ups.status" stops to report "OL" and upsmon going crazy
flooding my
mailbox with messages about "UPS unavailable"

Any idea?

Cheers,
Laurento

On Nov 17, 2010, at 6:17 AM, Laurento Frittella wrote:
> Hi all,
> I think the problem is related with the latest nut update (now I'm  
> using
> version 2.4.3)
I'm guessing this worked at one point with an older version of NUT -  
what version was that?