Do not migrate to Dude 6!!!

After migration from Dude 4 to Dude 6 new dude starts to lose interfaces under DEVICE- SETTINGS - SNMP- INTERFACE.
If device supports RouterOS API - all interfaces presents under DEVICE- SETTINGS - RouterOS- INTERFACE
Link labels sometimes shows RX/TX ?? If i change Link - Mastering Type to RouterOS instead of SNMP - It shows Ether1. It doesn't work with non-mikrotik devices

+1
This is still happening in 6.42.6. Any fix / workaround to force re-discovery of interfaces?

I have the same problem, I lose interfaces and it does not allow me to connect devices, this happens with version 6.42.7. Someone knows how to solve this problem.


In the attached image, example, I try to connect to the Gig 1/0/20 interface and it is not shown, several interfaces are lost, this happens to me at a global level.

On 6.42.7 problem remains. Tested on CHR platform.

It wouldn’t be such an issue if I could get it to rediscover ports when this happens.

Sometimes quitting dude client and reconnecting seems to help rediscover lost ports; but not reliably.

+1
Have this problem on the 6.42.7

Also have another problem with wlan ifaces while monitoring devices running OpenWrt 18.06 (OIDs discovered by SMNPwalk)
While working few days, this interfaces simultaneosly change their indexes and accumulate own non-working copies ("zombies") in the dropdown list of intefaces
this copies have different indexes like
wlan0(19) - zombie (previous working)
wlan0(20) - zombie (previous working)
wlan0(22) - working
wlan0(30) - zombie (previous working)
wlan0(33) - zombie (previous working)

And that's why correct monitoring going to be impossible ..

running

dude -> vacuum-db

solved this a couple of times for me

Thanks, it works.
I think it will be good to schedule this command for every day running

This is just a coincidence of stopping and restarting the server, which is what really fixes it.
Vacuuming the database has no effect in itself.

Just upgraded from v4 to v6.43.2, and many SNMP interfaces are missing too. Has anyone found a resolution or a way to rediscover?

Did you check SNMP V2c instesd of V1?

Did anyone find fix for this problem? i have same problem with interfaces..
snmpawlk finds them but they are not shown in snmp\interface tab. Is there any way to add them manualy? this is driving me crazy ))

Quitting the Dude client then re-opening it and waiting normally works for me.

Hello guys, I am running v6.43.2 and the problem is still there. The interfaces are found in SNMPwalk, but I am not able to find it when adding charts.
I have tried everything, including the command "dude vacuum-db" with no luck.

Any idea?

Experiencing the same problem here, currently on version 6.42.6.

Migrated from an old Version 4.0beta3 to 6.42.9 and no SNMP interfaces anywhere. Tagging this to track for any updates.

Just an update..... Switching to SNMP v2 fixed all my links in the newer Dude.

Please, what in a such case, that no interface is getting recognised via SNMP?

SNMPwalk can fin everything, but when I want to make a link connection, nothing shows up for snmp.

I use the v3 and privace community. Passwords are Ok.

still loosing interfaces.... it is a nightmare this V6...

I'm also struggling with new The Dude loosing interface status and even not listing corectly SNMP interfaces.
What I tried today was to stop The Dude server for a moment and then start it again (dude set enabled=no, and dude set enabled=yes).
It helped.
Maybe you can try it for yourself to check if that helps.

As far as i know, if you are missing some of your interfaces - just close dude and open it again, go to your device and interface list should be full again. It works for me 100%, but so annoying. Hey, MT team, please do something with that issue.

"... just close dude and open it again, ..."

In my case restarting client didn't help at all.
I was testing a bit in the meantime and I think that The Dude has major problem with working with SNMP v3. Tested both with and without encryption.
I guess, even lenght of the encryption key and password may matter because I have experienced some odd behaviour depending on lenghts of the keys/passwords.
I didn't test long enough to find pattern, but maybe I will some day.

I have 30+ devices on my map with no SNMP issues whatsoever on the latest version of The Dude. SNMP is either v2 or v1.

Отправлено с моего Mi A1 через Tapatalk

It’s not like the developers are unaware of these issues, almost certainly there’s a coder at Mikrotik who knows exactly what needs to be done to fix both this and several other stability issues but that it’s just not a priority for them at the moment, however much we would like it to be.

It’s so frustrating because overall the Dude is such a competent tool with loads of potential; it seems weirdly short sighted to just switch off development for your NMS software when the likes of Ubiquity are putting so much effort into theirs.

I guess all we can do is continue to make noise for further development, I just wish it didn’t feel so much like shouting into the wind.

Already since 6.44.1 some weird issues popped up. I was hoping 6.44.2 would fix them but no such luck.
I'll explain: I'm using snmpv3 with about 40 devices. On some of them (5-10 devices), most services are offline, most except routeros management. From the logs I was reading, i can tell that snmpv3 is no longer working : "v3 err : 3 unknown engine id". Due to this fact,i'm guessing, the dude server hosted on a chr, gets to 100% cpu usage (usually at 5-10%), evenly balanced on networking, management and unclassified. I scavenged the internet ever since for fixes or alternatives to Dude. I am still wondering, am I the most stupid Dude user, or is this really a bug?
I just hope that on the next update everything will work from this perspective.

Is there any fix regarding this? we updated to 6.44.3 (its worse then before now).
we have 150+ devices using snmp2. half of them lose their interface after 5m of dude usage. (restarting dude server fixes it for 5 minute than bug comes out again...)
we reseted our database with no luck. problem is still here.

The older Windows server version had a lot of bugs, but it worked after all.

I'm sorry to say that, but using the current version as a monitoring tool is absolutely ridiculous.

Already switched to PRTG, although the Dude has some unique and technically cool features.

Rather than offering a product in such conditions I would not offer it at all.

Time is money. And the one lost to configure such useless software will not return it to you.

Have at least the courage to be ashamed.

I am on 6.47.9 and had this issue with only one of my routers. snmp3 reports everything else except interfaces. snmp walk and routeros management also find the interfaces.
Using snmp2 solved the problem for the moment.