Re: Regarding snmpv3 inform packet

Pushpa Thimmaiah <[email protected]>
Newsgroups gmane.network.net-snmp.devel
Message-ID <CAASqVJVYmB-MeLT-HwsXtj1KV+KaA0XDd3L8gCP5ChmBGkn2WA@mail.gmail.com>
Hi Bill Fenner,

Thanks a lot. I am very grateful to the portal for keeping us more
knowledgeable and interest on snmp alive.

Regards,
Pushpa.T

On Tue, Aug 27, 2019 at 7:20 PM Bill Fenner <[email protected]> wrote:

> On Fri, Aug 23, 2019 at 12:19 PM Pushpa Thimmaiah <
> [email protected]> wrote:
>
>> Hi All,
>>
>> I would like to understand messages exchanged between manager and agent
>> during snmpv3-inform.
>> Following is my understanding
>> Msg1. Agent to manager : Request for engineID
>> Msg2. Manager to Agent : Response with engineID
>> Msg3. Agent to Manager :  Send snmpv3 trap to manager
>> Msg4. Manager to Agent :  Send ACK to agent on authenticating and
>> receiving snmpv3 trap
>>
>> *Query:*
>> Varbinds in Message #3 and #4  are same. Varbinds of
>> Message#3(informRequest) is trap, but why manager sends same varbinds back
>> to Agent in Message#4 (get-response)
>>
>
> See section 4.2.7 of RFC3416:
> https://tools.ietf.org/html/rfc3416#section-4.2.7
>
>    Upon receipt of an InformRequest-PDU, the receiving SNMP entity
>    determines the size of a message encapsulating a Response-PDU with
>    the same values in its request-id, error-status, error-index and
>    variable-bindings fields as the received InformRequest-PDU.
>
>
> Presumably the intent of including the varbinds in the response is to
> allow the originator of the inform to ensure that the complete message was
> received, if it cares to do that much validation.
>
>   Bill
>
>

_______________________________________________
Net-snmp-coders mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
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.