Please try to use the Reply feature of your mail app, instead of creating a new message. The keeps the chain of messages together, making it easier for readers to refer back to past messages.
On Tue, 28 Feb 2012 09:45:57 +0100 Zeljko wrote: ZM> I'd like to use the command snmptrap to reach following scenarios ZM> ZM> Agent Client ZM> (10.140.20.71) (10.140.20.69) ZM> | | ZM> snmptrap * | | ZM> =========> | | ZM> | Notification (SNMP v2) | ZM> | ============================> | ZM> | source ** | ZM> | destination (10.140.20.69) | ZM> | and so on... | - snmptrap does not communicate with the agent, it sends traps directly to the specified host. - are you always sending traps to a single client? Or does "and so on..." mean that you need to send the same trap to multiple clients? ZM> * snmptrap -v 2c [COMMON OPTIONS] [-Ci] uptime trap-oid [OID TYPE ZM> VALUE]... Note: there is no possibility to generate wanted source with ZM> this command, i.e. Agent address (10.140.20.71) will be always in source This is true for all v2/v3 traps. We don't support spoofing the source address in the udp packet. Why not use v1 traps, which contain the 'agent' in the PDU itself (which can easily be set via snmptrap)? ------------------------------------------------------------------------------ Keep Your Developer Skills Current with LearnDevNow! The most comprehensive online learning library for Microsoft developers is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, Metro Style Apps, more. Free future releases when you subscribe now! http://p.sf.net/sfu/learndevnow-d2d _______________________________________________ Net-snmp-coders mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
