On Tue, 2011-10-04 at 12:45 +0530, Vivek Nagaraj wrote:
> I shall provide you some of my findings now. Please correct me if I am wrong.
> 
> 1) I 'DID' receive the trap message on my trap receiver (another
> server in the network) on port no 162 if mentioned hostname:portno

What command, exactly, did you issue to send this message?

> 2) I 'DID NOT' receive the trap message on my trap receiver (another
> server in the network) on port no other than 162 if mentioned
> hostname:portno in the following cmd:
> >> snmptrap -v 1 -m ALL -c public \
> 135.36.115.62:<port no> .1.3.6.1.6.3169.254.1.1 127.128.129.130 6 1 20071105

Ok. I am assuming that you ran this from the command line. Did it say
anything on standard output/standard error?

What happened if you did use port number 162?

If you adds the flag -d, does it say anything then?

> 3) Since you say that the 'defTarget' was introduced in netSNMP v5.4
> (I have netSNMP v5.1 pre-installed with the RHEL 4.6 OS) or later, I
> shall not touch configuration files. Lets leave that for the moment.

Agreed.

> 4) I am not seeing any snmp errors in '/var/log/message' either. If
> you know a place where the SNMP logs are generated, can you please let
> me know the same?

Since you are running a user tool it defaults to logging on standard
error. You can redirect the logs to a file with -Lf <filename> or to
syslog with -Ls. From the man page snmpcmd(1):

LOGGING OPTIONS
       The  mechanism and destination to use for logging of warning and
       error messages can be controlled by passing  various  parameters
       to the -L flag.

       -Le    Log messages to the standard error stream.

       -Lf FILE
              Log messages to the specified file.

       -Lo    Log messages to the standard output stream.

       -Ls FACILITY
              Log  messages  via  syslog,  using the specified facility
              ('d' for LOG_DAEMON, 'u' for  LOG_USER,  or  '0'-'7'  for
              LOG_LOCAL0 through LOG_LOCAL7).

/MF


------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense.
http://p.sf.net/sfu/splunk-d2dcopy1
_______________________________________________
Net-snmp-coders mailing list
Net-snmp-coders@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/net-snmp-coders

Reply via email to