Hi Mostafa, Thank you for response. I have given information that SNMPv3 inform should be sent out until it will get response from NMS. I didnot not get much information about SNMPv3 Informs in RFC3414. Could you please share RFC that has information about SNMPv3 inform.
Thanks, Pushpa.T On Tue, Aug 6, 2024 at 5:41 PM Mostafa Kassem <mosta...@danlawinc.com> wrote: > Until it exhausts the number of retries and then it gives up (that is why > there is timeout period and retry value), but not until it gets a reply. > > Mostafa > ------------------------------ > *From:* Pushpa Thimmaiah <pushpa.thimma...@gmail.com> > *Sent:* Tuesday, August 6, 2024 12:41 AM > *To:* Net-SNMP Coders <net-snmp-coders@lists.sourceforge.net> > *Subject:* [*Newsletter*] SNMPv3 informs behavior when destination is > unreachable > > CAUTION: This email originated from outside of the organization. Do not > click links or open attachments unless you recognize the sender and know > the content is safe. > > Hi All, > > As per my knowledge, Whenever trap-destination is unreachable snmpv3 > informs retries upto default retry i.e 5 (if not defined) and in default > timeout. > Kindly let me know if this is correct. > Eg: > snmptrap -Ci -v 3 -r 4 -t 1 -n "" -a SHA -A test12345 -x AES -X test123456 > -l authPriv -u traptest 172.16.1.131 69 .1.3.6.1.4.1.8072.2.3.1 > .1.3.6.1.4.1.8072.2.1.1 i 11 > Here, timeout=1sec retry=4 , NMS=172.16.1.131(down) > Does it send snmpv3 informs until it gets response from > NMS/trap-destination > > > Thanks, > Pushpa.T >
_______________________________________________ Net-snmp-coders mailing list Net-snmp-coders@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
