trap error message

2008-03-17 Thread Siva Prakash Reddy G
Hi! I have written trap code, after compiling I'm getting error messages like as shown below. Trap.o: In function `send_ampMemUtilization_trap': Trap.c:(.text+0x80): undefined reference to `snmp_varlist_add_variable' Trap.c:(.text+0xa4): undefined reference to

Re: How to override the result of an GET request?

2008-03-17 Thread Nguyen Dinh Nam
On Fri, Mar 14, 2008 at 9:47 AM, Nguyen Dinh Nam [EMAIL PROTECTED] wrote: I want to write an embedded Perl extension to replace the built in value of .iso.org.dod.internet.mgmt.mib-2.interfaces.ifTable.ifEntry.ifDescr.* == .1.3.6.1.2.1.2.2.1.2 with my own values, such as the long description

extending 'pass' to do a fair number of the other types too.

2008-03-17 Thread Dirk-Willem van Gulik
Is there any reason as to why 'pass' and 'pass_persistant' are currently not supporting all the data types; in particular the COUNTER64 and unsigned types ? Or is there some fundamental reason why this is a bad idea ? Thanks, Dw diff -c -r

RE: trap error message

2008-03-17 Thread Siva Prakash Reddy G
Hi! I'm using make file to compile. Please go thru the make file as shown below. CC : = ${TOOLPATH} $(CROSS_COMPILE) gcc NET_SNMP_VERSION = 5.1.2 PRESENT_PATH = $(shell pwd) SNMP_PATH:= -I$(TOP_DIR)/../../../buildroot/build_armeb/net-snmp- $(NET_SNMP_VERSION)/include

Re: trap error message

2008-03-17 Thread Dave Shield
On 17/03/2008, Siva Prakash Reddy G [EMAIL PROTECTED] wrote: I'm using make file to compile. Please go thru the make file as shown below. Two comments. a) You don't appear to be linking your application with the Net-SNMP library, This would explain why it's not

Re: extending 'pass' to do a fair number of the other types too.

2008-03-17 Thread Thomas Anders
Dirk-Willem van Gulik wrote: Is there any reason as to why 'pass' and 'pass_persistant' are currently not supporting all the data types; in particular the COUNTER64 and unsigned types ? Or is there some fundamental reason why this is a bad idea ? No, and patch 1657741 (applied in

RE: trap error message

2008-03-17 Thread Siva Prakash Reddy G
Hi! Dave thanks for your reply. I don't understand first point that is. a) you don't appear to be linking your application with the Net-SNMP library, this would explain why it's not picking up the Net-SNMP library routines. Let me

Re: trap error message

2008-03-17 Thread Dave Shield
On 17/03/2008, Siva Prakash Reddy G [EMAIL PROTECTED] wrote: I don't understand first point that is. a) you don't appear to be linking your application with the Net-SNMP library The Net-SNMP API routines are collected together into the library 'libnetsnmp'. So if you are writing

Re: extending 'pass' to do a fair number of the other types too.

2008-03-17 Thread Dirk-Willem van Gulik
On Mar 17, 2008, at 12:31 PM, Thomas Anders wrote: Dirk-Willem van Gulik wrote: Is there any reason as to why 'pass' and 'pass_persistant' are currently not supporting all the data types; in particular the COUNTER64 and unsigned types ? Or is there some fundamental reason why this is a

Re: Notify/Target Address/Target Paramenters/NotifyFilterTable Table

2008-03-17 Thread Daniel Chuang
Hello, I dig a little bit further. If you configure/compile snmd with snmp v3 target address/target parameters/notifyFilter,the simple command such as ./snmpget -v2c -c public device-name snmpNotifyFilterRowStatus.1.65.1.3.6.1.2.1 will kill your snmpd. The following patch

A fix of DisMan monitoring of AgentX subagents problem

2008-03-17 Thread Athena G
Hello, I have a fix to bug 1689163 and would like to contribute it to the mailing list. I believe 1058412 is of the same problem but I haven't tested the fix on that scenario. Should I just submit it to http://www.net-snmp.org/patches/? Do we need some code review? I think the problem is due to

Re: A fix of DisMan monitoring of AgentX subagents problem

2008-03-17 Thread Thomas Anders
Athena G wrote: I have a fix to bug 1689163 and would like to contribute it to the mailing list. I believe 1058412 is of the same problem but I haven't tested the fix on that scenario. Should I just submit it to http://www.net-snmp.org/patches/? Do we need some code review? Please submit the