The agent(node2) is also net-snmp
The node1 (master) also has its agent of its own right?


Nishant

On Sun, 26 Sep 2021, 06:53 Bill Fenner, <fen...@gmail.com> wrote:

> On Thu, Sep 23, 2021 at 6:43 AM Nishant Nayan <nayan.nishant2...@gmail.com>
> wrote:
>
>> Thanks for the suggestions, I have tried that and I could see the data
>> sent and data received, however I am interested in the receiver part, as to
>> how the date is prepared by the receiver(node 2) based on sender's request
>> and then sent back to sender(node1),
>>
>
> The terms that we use in the SNMP world to describe these entities are
> that the manager sends a request to the agent, who then sends a response
> back to the manager.  You are asking how the agent builds its response.
> What kind of agent is it?  Is it also net-snmp, or is it something else?
>
>
>> specifically how the error index and error status is getting
>> prepared/calculated from receiver side, is there a way to debug this?
>>
>
> RFC3416 talks about the rules for setting them - e.g., general definitions
> in section 4.1
> https://datatracker.ietf.org/doc/html/rfc3416#section-4.1
> and specifics about how they are set when handling a GetRequest in section
> 4.2.1
> https://datatracker.ietf.org/doc/html/rfc3416#section-4.2.1
>
>   Bill
>
>
>
>>
>>
>> Thanks
>> Nishant
>>
>> On Mon, 6 Sept 2021 at 19:34, Bill Fenner <fen...@gmail.com> wrote:
>>
>>> By the way, I wanted to mention - I noticed your example was using
>>> SNMPv1.  SNMPv1 has been obsolete since 2002 (when the RFC was moved to
>>> historic status).  You should ideally be using SNMPv3, with its
>>> authorization and privacy improvements, and if not, at least use SNMPv2
>>> which is not obsolete.
>>>
>>>   Bill
>>>
>>>
_______________________________________________
Net-snmp-coders mailing list
Net-snmp-coders@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/net-snmp-coders

Reply via email to