On Tue, 2005-09-06 at 12:04 +0530, Poojan Tanna wrote: > On Mon, 2005-09-05 at 15:38 +0100, Dave Shield wrote:
> > Assuming that these traps used the enterprise OID .1.2.3.4.5, > > then you'd need snmptrapd.conf settings along the lines of: > > > > > > forward .1.2.3.4.5.0.1 10.10.10.1 > > forward .1.2.3.4.5.0.2 10.10.10.1 > > : > > forward .1.2.3.4.5.0.20 10.10.10.1 > > forward .1.2.3.4.5.0.45 10.10.10.2 > Any special reason why you are insisting on forwarding based on > combination of OID and TrapType. Because that's how SNMP traps work. The (specific) trap number alone is *not* sufficient to identify a particular trap. Trap #4 sent by a Cisco box (with enterprise 1.3.6.1.4.1.437.1.1.3) is different from trap #4 sent by a Sun box (with enterprise 1.3.6.1.4.1.34). One indicates a broadcast storm, the other an overheating circuit board. But you can't tell which is which by just looking at the trap number, you need the enterprise OID as well. > I suppose forwarding on Trap Type alone is sufficient. You supposes erroneously :-) > For enterprise > traps, we have provision in the forwarding logic to act accordingly. No - the enterprise OID is a fundamental part of identifying a particular trap. It needs to be taken into account right from the start. > Also, pl. note that in the example that you have given above, forwarding > action is done solely on the basis on OID. Talking about "trap numbers" and "enterprise OIDs" is only relevant to SNMPv1 traps. SNMPv2 uses a different approach, based on a single "trap OID". There is a standard mechanism for mapping between SNMPv1 (trap #, enterprise OID) pairs, and SNMPv2 trap OIDs. The Net-SNMP snmptrapd configuration uses SNMPv2 trap OIDs, regardless of the version of the incoming trap. The OIDs listed above are the SNMPv2 equivalents of the trap numbers you were asking about (with a dummy enterprise OID, since you didn't specify this). Dave ------------------------------------------------------- SF.Net email is Sponsored by the Better Software Conference & EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf _______________________________________________ Net-snmp-coders mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
