On Fri, 2005-05-13 at 23:05, Alex Burger wrote: > The first OID passed in an SNMP v2 trap is the uptime and the second is > SNMPv2-MIB::snmpTrapOID.0. In the packet you sent me, it is sending > SNMPv2-MIB::snmpTrapOID (without the trailing .0).
> Net-SNMP could be change to allow either snmpTrapOID or snmpTrapOID.0, > but I'm not sure if that is something that should be done. NO!! It Most Definitely Should Not! It trust that answers the question to your satisfaction, Alex :-) The second varbind in an SNMPv2-format trap *must* be snmpTrapOID.0 - see RFC 1905, section 4.2.6. The notification generator is broken and should be fixed. It would not be appropriate to tweak snmptrapd to accept such broken traps. Dave ------------------------------------------------------- This SF.Net email is sponsored by Oracle Space Sweepstakes Want to be the first software developer in space? Enter now for the Oracle Space Sweepstakes! http://ads.osdn.com/?ad_id=7412&alloc_id=16344&op=click _______________________________________________ Net-snmp-users mailing list Net-snmp-users@lists.sourceforge.net Please see the following page to unsubscribe or change other options: https://lists.sourceforge.net/lists/listinfo/net-snmp-users
