I compiled the 5.3 release with the notification-log-mib in snmpd (as opposed to running it in snmptrapd).
When I start and turn on debugging I can see that notification_log is initialized and that events are going into it. However, if I walk the log using snmpwalk, the walk will terminate at the first hole in the various tables. When walking nlmLogTable it usually terminates when the walk tries to get nlmLogEngineID. When walking the nlmLogVariableTable I get a noSuchVariable error. This happens independent of using V1, 2c, or 3. If I try to get specific objects (as opposed to getnext) using the correct index I do indeed retrieve the variable. This seems to indicate to me that there is a problem walking the mib.
I did search the archives and FAQs and noticed that Wes shows a successful walk of the notification log but I think this was using pre-5.3 software in and that the notification log mib was in snmptrapd.
Has anybody been able to walk the notification-log-mib in 5.3? If so, did you succeed by using the notification log mib in snmpd or was it in snmptrapd? Any other ideas as to what might be happening?
Jeff
------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________ Net-snmp-users mailing list [email protected] Please see the following page to unsubscribe or change other options: https://lists.sourceforge.net/lists/listinfo/net-snmp-users
