How to send V3 traps from enterprise MIB modules?

"Ron Rader" <[email protected]>
Newsgroups gmane.network.net-snmp.user
Message-ID <6BA04340F278EB47AB42AAF2EED9CBBA03BC116C@dellserver.cipheroptics.local>
  Apologies if this is better suited to the coders list, I'm hoping I
can accomplish my task with some clever manipulation of snmpd.conf.

  I maintain an embedded v5.4.1 installation that includes a number of
enterprise-specific traps.  These are generated using send_v2trap().

  V2C traps work just fine.  Now I need to know how to send V3 traps.

  I know I'll have to add appropriate auth user support to snmpd.conf.
My experiments thus far have not been fruitful.  My agent generates V2C
traps but does not appear to attempt any V3 traps.

  The guides and tutorials I've found suggest generating traps with the
"snmptrap" system command and the -v3 option.  This isn't useful for my
enterprise traps.

  I feel like I'm missing something obvious.  How can I configure my
agent to enforce the V3 authentication (and maybe encryption)
capabilities on the V2C traps that it currently generates?

  Thanks,

  Ron



The information contained in this message may be privileged and confidential and protected from disclosure. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by replying to the message and deleting all copies. Thank you.

------------------------------------------------------------------------------

_______________________________________________
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
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.