Dude label stop to show/refresh data from SNMP or Script

I have a issue with Dude 4.0 b3 on Windows Server 2003 x64.
It stop to show/refresh data in device label, it show only text:

[Device.Name]
CPU Load:          [oid("1.3.6.1.2.1.25.3.3.1.2.1")]%
MU Connected:      [ros_wireless_clients_count()]
[Device.ServicesDown]

I start to work again only when I added something in the label(as example CPU Load: [oid(“1.3.6.1.2.1.25.3.3.1.2.1”)]%) and then press Apply.

Does anyone have any similar problems ?

Thanks.

Hi,

What network card do you use? I have similar observation on Atheros lan card, but works fine on Realtek card in another workstation, so I am wondering if this is lan card related.

I noticed a strange pattern of tx/rx data, which may give a clue as to why snmp data apears and disappears frequently.
chart.jpeg

Have two integrated Broadcom BCM5708C NetXtreme II GigE

I have ordered an Intel card but it can take up to 3 or 4 weeks until I replace the Atheros card and report back if there is any change, as I have no direct access to the workstation in question and it’s not on top of my priority list. If you find a workaround until that time please let me know. Maybe others have experienced disappearing snmp data and have a solution to this. Thanks.

Wow 20Mbps outbound and very little inbound from your server at regular intervals? That is very strange.

Changed mode Run mode from all time to as service.
Will see changes.

Without effect. Some labels don’t show any counts.

It’s a streaming server - maybe that’s why.

I have replaced the network card today, but I can still see the same weird tx pattern as before. The pattern differs when compared to the wireless link and the SNMP information still disappears once in a while.

Maybe it is due to the network card configuration, maybe due to the router in that site. Cat 5e cable was checked and is all fine. I can’t troubleshoot any further because I am not the siteowner, therefore any suggestions would be much appreciated.
Untitled-1.png

just a bug in dude … it cant always keep up with how many probes its doing, so the snmp will timeout and not show labels properly.

it could also be multihomed machine returning snmp packets via a different source ip, which wont make it back to dude. Please MT - allow SNMP to be bound to a specific interface on the box, preferrably lo interface : )