SNMP issues with Observium/Dude

[bmv]

I am having trouble using SNMP with either the AC or DC Netonix WISP switches.
The symptoms are that I can monitor the WISP switches from Mikrotik DUDE and Observium, but the information resets/reloads, so I can't log/report on anything.

Can't see what is going wrong. I can use SNMP on other devices at the similar subnet ranges.
The other devices we are monitoring are Mikrotik routers, toughswitches, HP Procurve switches, APC UPSs, Site Monitors. They all work fine.

In the WISP switches I have set the following in the Device -> Configuration -> SNMP Server settings:
- Enabled: checked
- Contact: [name here]
- Location: [location here]
- Community: [community here]

On Observium or Mikrotik Dude I configure the device's SNMP details to match, and using SNMP version 2.

Dude probing switch causes errors on the Netonix

Sep 6 14:49:10 mini_snmpd[2903]: could not handle packet from UDP client x.x.x.x:26072: Bad address
Sep 6 14:49:10 mini_snmpd[2903]: could not handle packet from UDP client x.x.x.x:26072: Bad address
Sep 6 14:49:10 mini_snmpd[2903]: could not handle packet from UDP client x.x.x.x:26072: Bad address
Sep 6 14:49:34 mini_snmpd[2903]: could not handle packet from UDP client x.x.x.x:26072: Bad address
Sep 6 14:49:34 mini_snmpd[2903]: could not handle packet from UDP client x.x.x.x:26072: Bad address
Sep 6 14:49:34 mini_snmpd[2903]: could not handle packet from UDP client x.x.x.x:26072: Bad address

Where x.x.x.x is the IP address of our DUDE server.
Interesting, although Observium is set to probe the switch, there are no similar alerts against it's IP address - although in Observium, I still don't get stable results.

I have checked firewall, routing - this is all okay.
Like I say, I can probe and monitor other devices from DUDE/Observium at similar subnets, and there are no firewall rules to block this.

I have tried 1.2.4 and 1.3.2. Same problems.

Any ideas?
This is probably a really obvious failure on my behalf, but expended my energy checking anything else!

[sirhc]

I asked eric to help you but he appears to want a personal day. ....pfft i'm on first weekend off in 2 years in Miami on south beach half lit sitting next to the pool guaking at girls and yet here I am answering posts. ...shame on him and me

[lligetfa]

...shame on him and me

Chris, put down your phone and enjoy the time off.
I'm sure this issue will keep.

[Eric Stern]

Dude probing switch causes errors on the Netonix

Sep 6 14:49:10 mini_snmpd[2903]: could not handle packet from UDP client x.x.x.x:26072: Bad address
Sep 6 14:49:10 mini_snmpd[2903]: could not handle packet from UDP client x.x.x.x:26072: Bad address
Sep 6 14:49:10 mini_snmpd[2903]: could not handle packet from UDP client x.x.x.x:26072: Bad address
Sep 6 14:49:34 mini_snmpd[2903]: could not handle packet from UDP client x.x.x.x:26072: Bad address
Sep 6 14:49:34 mini_snmpd[2903]: could not handle packet from UDP client x.x.x.x:26072: Bad address
Sep 6 14:49:34 mini_snmpd[2903]: could not handle packet from UDP client x.x.x.x:26072: Bad address

[/quote]

The only time I've seen this error is when The Dude is sending v1 packets and our switch is configured for v2c. Try installing 1.3.2 and change the SNMP version to v1 and see if that helps.

[Gerard]

I'm seeing the same bad address errors in my log on 1.3.2. I've tried both v1/v2c in The Dude and the Netonix. Dude v3 if it matters.

Gerard

[sirhc]

I am NOT a DUDE expert but I set it up and played a little but with it and it appears to work fine?

You need to make sure The Dude is using the same version of SNMP and ONLY THAT VERSION.

I asked my CTO at http://www.netlinx.net (My WISP) to set up The Dude and make sure he can also pole our switches.

I will ask Tom report back here once he has completed that task and is able to use it proficiently.

Entering an NMS IP address under the Syslog area of the Device/Configuration Tab will prevent all those Drop bear connections in the Log every time the NMS server talks to the switch.

CLICK IMAGE BELOW TO VIEW FULL SIZE

the_dude.jpg (354.78 KiB) Viewed 28460 times

[sbyrd]

I can poll the switch and read SNMP in the Dude. However, when I add a Link between the switch and AP to show an interface usaged on the Dude Map it pulls the data correctly but the interface keeps disappearing and reappearing for long periods of time. Not sure if I described it correctly or not. This happens on V1 or V2c SNMP. I also get the "could not handle packet.....Bad Address error"

As you can see below it is missing ports 3 and 4 (6 port switch)

Netonix link.PNG (59.14 KiB) Viewed 28458 times

[mhoppes]

Was a solution for this ever discovered? I'm having the exact same issue, but using Cacti. It just started with some recent firmware update (but I don't know which one).

[mhoppes]

I just realized, this morning, all of my Cacti graphs are broken, and I can't get new graphs to setup and work properly on new switches I've installed.

[mhoppes]

Hmmmm.. Upgrading to 1.3.7 seems to have fixed this issue.