I have added my agent address to the snmpd.conf file. Or else I would
have not received the trap at port no 162.
snmptrap -v 1 -m ALL -c public \
135.36.115.62:5000 .1.3.6.1.6.3169.254.1.1 127.128.129.130 6 1 20071105
>> Yes. The agent is 135.36.115.62. I still didn't receive traps at port no 500.
On Tue, 2011-10-04 at 11:21 +0530, Vivek Nagaraj wrote:
> I just tried it on RHEL 4.6 x86. Here is the more detailed OS info:
> Linux dhcp-135-24-228-150 2.6.9-67.EL #1 Wed Nov 7 13:41:13 EST 2007
> i686 i686 i386 GNU/Linux
> Red Hat Enterprise Linux AS release 4 (Nahant Update 6)
> NET-SNMP versio
I just tried it on RHEL 4.6 x86. Here is the more detailed OS info:
Linux dhcp-135-24-228-150 2.6.9-67.EL #1 Wed Nov 7 13:41:13 EST 2007
i686 i686 i386 GNU/Linux
Red Hat Enterprise Linux AS release 4 (Nahant Update 6)
NET-SNMP version: 5.1.2
When I executed this command on RHEL 4.6 x86
snmptrap -v
On Tue, Oct 04, 2011 at 08:19:57AM +0530, Vivek Nagaraj wrote:
> So, you mean to say any net-SNMP version above and including net-SNMP
> 5.4 supports mentioning ports along with host name?
No, Magnus is telling you about the defTarget directive. I just told
you that using portnumber with hostname
The RHEL 4.6 32-bit I am using has net-SNMP version 5.1.2. So, I hope
this would not support ports mentioned with the snmptrap command.
Please correct me if I am wrong.
The RHEL 6.1 has version 5.5 installed.
So, you mean to say any net-SNMP version above and including net-SNMP
5.4 supports menti
On Mon, 2011-10-03 at 19:50 +0530, Vivek Nagaraj wrote:
> Ok. I am sorry. Not working in the sense, if I provide custom ports
> other than 162, I am not receiving any traps at those custom ports.
>
> I am not seeing any error message after the execution of the command
> mentioned by you.
>
> My s
On Mon, 2011-10-03 at 08:44 +0530, Vivek Nagaraj wrote:
> Response to your previous mail:
>
> 1) Could not find 'snmp.conf'
As Niels said, you have to make it yourself.
>
> 2) And options you have mentioned to be used with 'snmptrap' command
> is not working
--defTarget="udp:169.254.1.1:30617"
Hello coders,
Please, do anyone have a functional source created with *
mib2c.table_data.conf* that makes use of* netsnmp_cache_create()* to cache a
table after reading data from a file?
Here's a code snippet from the source generated by *mib2c*:
int
myTable_load (netsnmp_cache * cache, void *vm
It seems the code automagically generated by *mib2c* was considering those
inexistent functions *netsnmp_cache_free()* and *
netsnmp_table_registration_info_free()*.
I created another file using an updated mib2c conf (see
http://gist.github.com/1259707) and those functions were not present.
Howev
On Mon, Oct 03, 2011 at 07:50:57PM +0530, Vivek Nagaraj wrote:
> My server administrator says that the backward compatibility needs to
> be maintained with older server OS too. I am kind of stuck. I tried
> and tried and tried but could not receive traps at the ports other
> than 162.
With an up2d
Ok. I am sorry. Not working in the sense, if I provide custom ports
other than 162, I am not receiving any traps at those custom ports.
I am not seeing any error message after the execution of the command
mentioned by you.
My server administrator says that the backward compatibility needs to
be m
Hi Wes,
Thanks for the help.
After attaching the strace I could see both snmpd and sub-agent got hung at
a point when sub-agent was sending a trap.
There were no snmpget/walk requests when this situation occurred.
snmpd //
strace -p 7886
Process 7886 attached - interrupt to quit
sen
On Mon, Oct 03, 2011 at 12:11:50PM +0530, Vivek Nagaraj wrote:
> Is there any net-snmp issue (you are aware of) regarding this in older
> net-snmp binaries placed in RHEL 4.7?!
>
> In simple words, its working fine in RHEL 6.1 but not in RHEL 4.7. Any idea
> why?
Define "not working"! Any error
13 matches
Mail list logo
