I have an existing link that has been monitored in The Dude using SNMPv1. It has not been installed long, and we are now trying to implement some security. Most of the network is only SNMPv2 capable.
I am able to walk the device and setup probes. The Dude configuration for SNMPv3 is working.
My issue is with a map link. I select mastering type of “SNMP” but the interface does not show up. If I walk the device, I see the interfaces. See the attached.
I did. It looked to me a bit lazy but it worked as expected. But then I deleted dude from RB2011 as it was making terrible things - freezing, leaking memory, loosing data.
Were you able to access interface data (e.g. create link and see interfaces and bitrates per interface) or did you just walk the device and create custom probes? I can do the latter, not the former
Yes, I saw interface data but was very slowly updated - approximatelly 5-10x per minute. Using “winbox type communication” was much more faster (1-2x per second). Unfortunatelly I fully uninstalled Dude so I cannot show you how it worked. But the setting was quite intuititve, I did not need to consult any manual for SNMPv3 settings. - You need to create special profile for this in Dude and switch it within all devices or make your profile to be default for used types of devices, as I remember. I used both authentication and encryption. Also the special community has to be set and enabled in each device.
Thanks. Or throw it on Windows (or a virtual session) and hit a device or two. I really do not understand why V3 is not working. This is not a Mikrotik device. But I have The Dude watching Ubiquity, Cambium, Memorylink, plus four other brands. This is the only SNMPV3 I have going, and I am having problems. Not sure where to look, for the config is correct.
Thank you for taking the time to do this and to post images.
So maybe this is a problem with v4.0b3. I compared settings in The Dude and they are valid. I think I will need to test on 3.6 and also test monitoring a Tik device with v3. That will suggest where the bug is.