I am using net-snmp to send v3 traps from the command line. I
understand that the manager must know the engine id of the trap sender
prior to receiving the trap.
Is there an accepted way of setting the engineID in this situation? The
random generation of engineID at startup will not work very well in
this case. The way I see it, I have two viable options, either set the
engineID manually to what ever I feel like, or having it create the ID
from the ip address. Is one way preferred by the community over the
other? Are there any rules or guidelines for choosing an engineID?
Secondly, how do I determine what engine ID snmptrap is using? I'd like
to display the current engineID through a CLI command.
Also, does the trapsess directive apply to the snmptrap command? I'd
like to have it so that I don't have to specify the destination on the
commandline.
Thanks in advance,
Mike
-------------------------------------------------------------------------
SF.Net email is sponsored by: The Future of Linux Business White Paper
from Novell. From the desktop to the data center, Linux is going
mainstream. Let it simplify your IT future.
http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4
_______________________________________________
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
