NMPv3 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 Mo
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
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 a
kjonze wrote:
> I am using net-snmp 5.4 to send v3 informs to a utility using the -C i
> parameter but they are being transmitted on port 161. How do I adjust
> it so
> that it gets sent on port 162?
The upcoming 5.4.1 release (currently at pre3) will fix this.
In the meantime, you may want to
All,
I am using net-snmp 5.4 to send v3 informs to a utility using the -C i
parameter but they are being transmitted on port 161. How do I adjust it so
that it gets sent on port 162?
-
This SF.net email is sponsored by DB2 E
