Thanks a lot Niels!
snmptrap -v 1 -m ALL -c public 135.36.115.62:30617 .1.3.6.1.6.3
169.254.1.1 6 1 20071105
>> Worked like magic on custom ports on RHEL 6.1!
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 workin
On Mon, Oct 03, 2011 at 08:44:50AM +0530, Vivek Nagaraj wrote:
> Response to your previous mail:
>
> 1) Could not find 'snmp.conf'
You have to create it yourself.
> 2) And options you have mentioned to be used with 'snmptrap' command
> is not working
> [root@localhost snmp]# snmptrap -v 1 -m AL
Response to your previous mail:
1) Could not find 'snmp.conf'
2) And options you have mentioned to be used with 'snmptrap' command
is not working
Please refer the attachments for more details.
Thanks a lot for your time and response.
[root@localhost snmp]# snmptrap -v 1 -m ALL -c public 135.36.
I think I have found some dead code lying around.
There are three C test cases under testing, etimetest.c, scapitest.c and
keymanagetest.c. All three of them contains calls to the function
sc_shutdown that used to be in scapi.c prior to commit
3eaa9878d4f196d1104f01a22f17fcef904f94c2.
That one ha
When you starts talking about execl snmptrap I also have to say that I
wouldn't have done it that way...
I would probably either embed the library to send the traps directly or
let the program act as an AgentX subagent and use that to make the agent
send the traps to the places that are specified i
On Sun, 2011-10-02 at 10:37 +0530, Vivek Nagaraj wrote:
> Ok. That sounds reasonable. Thanks a lot! Hope you can can answer my
> following questions:
>
> 1) What is the difference between snmp.conf and snmpd.conf files in
> '/etc/snmp/' directory?
snmp.conf is used by all snmp*-programs
snmpd.con
