On 14 July 2010 04:35, Grumm, Scott <[email protected]> wrote: > Some clients are having problems with the OID for SNMP v1 Traps
There's no such thing as a (single) OID for SNMPv1 traps. SNMPv1 enterprise-specific traps are identified using an (OID, integer) pair. > The iReasoning MIB Browser shows the v1 trap as: > > Specific: 1; .1.3.6.1.4.1.9804.3.1.1 Which is trap#1, using the enterprise OID lhnNsmDevices Given the Notification definition, this is the correct mapping. See RFC 3584, section 3.2, steps (1) and (4) > Wireshark shows: > > version: version-1 > enterprise: 1.3.6.1.4.1.9804.3.1.1 (SNMPv2-SMI::enterprises.9804.3.1.1) > generic-trap: enterpriseSpecific (6) > specific-trap: 1 Which is exactly what you would expect to see for this particular trap. Dave ------------------------------------------------------------------------------ This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first _______________________________________________ Net-snmp-coders mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
