On 8 February 2011 22:42, Al Gambardella <agam.em...@gmail.com> wrote: > The problem is that the net-snmp > snmptrapd code keeps looking for the snmpTrapOID. This OID isn't present in > the traps I am receiving.
Then these traps are broken. > I see the SysUpTime OID then a number of > enterprise specific OIDs in each trap I receive. The first two varbinds in an SNMPv2 trap *must* be sysUpTime.0 followed by snmpTrapOID.0 See RFC 1905 section 4.2.7 > Is this OID supposed to be part of a V2C trap? Yes. > Does this mean the device I am monitoring have a problem. Whatever is generating these traps has a problem, yes. Dave ------------------------------------------------------------------------------ The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb _______________________________________________ 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
