Title: Re: snmpTargetAddrTable inconsistent values
Hi,
 
The following directive (in snmpd.conf) populates values in to snmpTargetAddrTable.
 
trapsess -e 0x900003ddf15414344452 -v 3 -u admin -a SHA -x AES -l noAuthNoPriv 10.201.114.135 -Ci -r 3 -t 15
 
options:

 r: retry count
 t: timeout
 
If I don't include these values then it will take timeout as 1000 and retry count as 5. As per the MIB defintion the default values are 1500 and 3. But these values are not observed in the snmpTargetAddrTable when querying through snmptable query.
 
But when I give 15 as timeout value in trapsess then it shows 15000 value in timeout in snmpTargetAddrTable entries. How to to intialize this value as 1500 in this table for timeout.
 
Thanks in advance,
Mahesh


From: Wes Hardaker [mailto:[EMAIL PROTECTED]
Sent: Wed 4/5/2006 11:48 PM
To: Mahesh Anasuri (WT01 - Broadband Networks)
Cc: net-snmp-coders@lists.sourceforge.net
Subject: Re: snmpTargetAddrTable inconsistent values

>>>>> On Fri, 24 Mar 2006 16:02:00 +0530, <[EMAIL PROTECTED]> said:

kanakamahesh> But I suddenly noticed with out any changes it is giving
kanakamahesh> 1000, 5 as values for snmpTargetAddrTimeout,
kanakamahesh> snmpTargetAddrRetryCount attributes for corresponding of
kanakamahesh> same trapsess entries in snmpd.conf.

the trapsess line actually pulls defaults from the standard snmp
command line utilities.  You can override them with the -t and -r flags.

kanakamahesh> I did not do any modify the hardcoded values in the
kanakamahesh> mibgroup/source files. Also I see that values 0 for
kanakamahesh> tra2sink entries? Are they expected default values for
kanakamahesh> these entries?

trap2sink entries don't do retries and timeouts because they're not
acknowledge messages.  It doesn't make sense for them.
--
Wes Hardaker
Sparta, Inc.

Reply via email to