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. 
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.