Re: snmpinform and not in time window

Pushpa Thimmaiah <[email protected]>
Newsgroups gmane.network.net-snmp.user
Message-ID <CAASqVJW1NX2PhTaHYNoqr89WHeoz2w=N1dwJ-pOrGN_QVJeNcA@mail.gmail.com>
Hi Folks,

I did enable debug while sending inform

command : snmptrap -Dall -t 6 -v 3 -Ci -n "" -a MD5 -A 123password  -l
authNoPriv -u testinform 172.16.1.10 69 .1.3.6.1.4.1.8072.2.3.1
.1.3.6.1.4.1.8072.2.1.1 i 44

Last log is "sess_select: blocking:no session requests or alarms." and
'snmptrap' get stuck , has to kill the process manually.
I need some clue regarding above log.

Thanks,
Pushpa.T


On Mon, Nov 9, 2015 at 3:25 PM, Pushpa Thimmaiah <[email protected]
> wrote:

> Hi Folks,
>
> I did debug using wireshark and following is my observation
>
> 1. there are totally four messages . This is correct behaviour
>     get-request (agent to trapreceiver)
>     report (trapreceiver to agent)
>     informRequest (agent to trapreceiver)
>     get-response (trapreceiver to agent)
>
> 2. In 'report' message pdu, msgAuthoritiveEngineID,
> msgAuthoritiveEngineBoots and msgAuthoritiveEngineTime contains values of
> engineid, engineboots, enginetime of 'trapreceiver'  . This is correct
> behavior
>
> But, In 'informRequest' PDU both boot and time ( msgAuthoritiveEngineBoots
> and msgAuthoritiveEngineTime )contains values of the snmp-agent's boot and
> time.  I have doubt here.
> According to my knowledge snmp-agent should use 'trapreceiver's" boot and
> time which got in message 'report' .
>
> Kindly let me know why snmpagent using its boot and time in outgoing
> 'informRequest' message?
>
> Thank you,
> Pushpa. T
>
> On Sat, Nov 7, 2015 at 12:20 AM, Pushpa Thimmaiah <
> [email protected]> wrote:
>
>> Hi Folks,
>>
>> Adding to previous mail.
>> trap receiver shows no error for  traps received from the agent.
>>
>> On Sat, Nov 7, 2015 at 12:00 AM, Pushpa Thimmaiah <
>> [email protected]> wrote:
>>
>>> Hi Folks,
>>>
>>>  When SNMP agent sends snmpinform, trapreceiver (snmptrapd)  displays
>>> 'not in time window' error
>>>
>>>
>>>
>>> command : snmptrap -t 6 -v 3 -Ci -n "" -a MD5 -A 123password  -l
>>> authNoPriv -u testinform 172.16.1.10 69 .1.3.6.1.4.1.8072.2.3.1
>>> .1.3.6.1.4.1.8072.2.1.1 i 44
>>>
>>> I am facing two issues
>>> 1. snmptrapd (trapreceiver) shows 'not in time window'
>>>
>>> Snmpagent running on ubuntu . Its time setting is IST
>>> snmptrapd runnning on ubuntu . Its time setting is UST
>>>
>>> Does this causing 'not in time window' ? how it can be resolved
>>>
>>>
>>> 2. It looks like agent keep retrying to send inform, hence command(above
>>> mentioned) 'snmptrap' got struck and I had to kill the process
>>> I did tried option '-r' but still it will get struck
>>>
>>> snmptrap -r 0 -v 3 -Ci -n "" -a MD5 -A password123  -l authNoPriv -u
>>> testinform 172.16.1.10 69 .1.3.6.1.4.1.8072.2.3.1 .1.3.6.1.4.1.8072.2.1.1 i
>>> 44
>>>
>>> Thank you,
>>> Pushpa.T
>>>
>>
>>
>

------------------------------------------------------------------------------

_______________________________________________
Net-snmp-users mailing list
[email protected]
Please see the following page to unsubscribe or change other options:
https://lists.sourceforge.net/lists/listinfo/net-snmp-users
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.