Is this correct place to put discovered problems with "the dude" ?
There is a problem with the dude if you add a Linux (here Centos) or cisco device (here asa5510).
I am having a parallel run with older dude (3.x, 4.x) and the new generation 6.x, where snmp has some issues.
Dude 3.x, 4.x is running in Server 2008r2 on a physical hpdl120G8 box with 8GB RAM and 2CPU and 2 * 250GB mirrored SSD disks.
Dude 6.x running on CHR with 4CPU and 4GB ram with 1GB disk, in a hpdl380g8p with also SSD disks in a raid10 system
CHR is licensed and registered (but not yet payed), to overcome the bandwidth limitations.
SNMP walking them works and show all values, also older versions of the dude (3.x, 4.x) and also other monitoring like mrtg and nagios.
On Cisco ASA devices you are not able to see any of those SNMP values
SNMP -> INTERFACES
On Linux devices you are not able to see any of those SNMP values
SNMP -> ROUTING
SNMP -> STORAGE
It seems like the new dude v6.x map devices does not recognize the oid:s related to them.
It results in you can not have speed on links, neither you can set interfaces to links and so on.
Unfortunately we discovered now more problems with dude and snmp...
Our AIX servers which was perfectly dealt with by dude snmp, now it turned out they lost the ability to see interfaces by snmp, they same way as cisco devices.
Yesterday they all had lo0, en0 and en1, now they have only lo0 left, they have lost en0 and en1 by some reason.
Another oddity is that snmpwalking is very very slow, in the historic 3.x and 4.x it is blistering fast, could it be that snmp simply times out before the interfaces is found (long down in the list so to say) ?
In dude map devices beneath SERVICES, it recognize for linux cpu, disk, memory, ping, ssh, virtual memory.
Anyone who faced this as well, how did you solve it, or is it a bug ?