From: SourceForge.net <no...@so...> - 2009-06-11 23:09:25
|
Patches item #2693746, was opened at 2009-03-19 00:48 Message generated for change (Comment added) made by hardaker You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=312694&aid=2693746&group_id=12694 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: backport-needed >Status: Closed >Resolution: Accepted Priority: 5 Private: No Submitted By: Bart Van Assche (bvassche) >Assigned to: Wes Hardaker (hardaker) Summary: 5.4.2.1: fix for NOTIFICATION-LOG-MIB related bugs Initial Comment: There are several problems in the Net-SNMP 5.4.2.1 source code related to the implementation of the NOTIFICATION-LOG-MIB: * SOCK_STARTUP is called too late, which triggers a WSANOTINITIALISED in source file winpipe.c. * A template for the macro USING_NOTIFICATION_MODULE is missing in win32/net-snmp/agent/mib_module_config.h. * When the macro USING_NOTIFICATION_MODULE is defined, the source code does no longer compile on a Win32 platform. I have fixed this by moving the notification_log.c source file from the snmptrapd project to the netsnmpmibssdk project. This patch has been tested on Windows XP with the Visual Studio 2005 compiler. I have verified that after these changes snmptrapd is now able to register via the AgentX protocol with the Net-SNMP SNMP agent. The output of an SNMP walk on the OID notificationLogMIB (1.3.6.1.2.1.92) is still empty however. It's not clear to me why. ---------------------------------------------------------------------- >Comment By: Wes Hardaker (hardaker) Date: 2009-06-11 16:09 Message: Applied in r17653 ---------------------------------------------------------------------- Comment By: Wes Hardaker (hardaker) Date: 2009-06-11 16:09 Message: Thanks for the patch! It has been applied to the 5.3.x and 5.4.x code branches and the main development tree, and will appear in future releases of the Net-SNMP package. ---------------------------------------------------------------------- Comment By: Dave Shield (dts12) Date: 2009-04-09 00:36 Message: > $ snmpwalk -v1 -cpublic 192.168.1.225 .1.3.6.1.2.1.92 > > $ snmpwalk -v1 -cpublic 192.168.1.225 .1.3.6.1.2.1.1.3 > DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (7576911) 21:02:49.11 The "snmptrapd" notification receiver registers as an AgentX subagent using the context "snmptrapd". So in order to see content provided by snmptrapd, you must specify the same context in your SNMP requests. That effectively means using SNMPv3, with the option "-n snmptrapd". ---------------------------------------------------------------------- Comment By: Dave Shield (dts12) Date: 2009-04-08 07:21 Message: How were you querying the notificationLogMIB? In particular, what context were you using? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=312694&aid=2693746&group_id=12694 |