On Fri, 23 Jan 2009 20:19:44 -0500, lanas <[email protected]> wrote :
> I'm using the send_linkUpDownNotifications() to generate a trap when > I got some information from the netlink system. When pulling an > eth cable I thus get the following trap (note that the Admin and Oper > values ares test values) : > 9:41:10 TRAP:Cold Start from UDP: [10.159.9.37]:41278 TRAP2, SNMP > v2c, community public DISMAN-EVENT-MIB::sysUpTimeInstance = > Timeticks: (255210) 0:42:32.10 SNMPv2-MIB::snmpTrapOID.0 = OID: > IF-MIB::linkUp > IF-MIB::ifIndex.5 = INTEGER: 5 > IF-MIB::ifAdminStatus.5 = INTEGER: 30 > IF-MIB::ifOperStatus.5 = INTEGER: 50 > SNMPv2-MIB::snmpTrapEnterprise.0 = OID: > NET-SNMP-MIB::netSnmpAgentOIDs.10 What seems to happen is that the %W format option of snmptrapd will always return 'Cold Start'. In the example above it is clearly a linkUp trap: SNMPv2-MIB::snmpTrapOID.0 = OID: IF-MIB::linkUp But &W is neverthless 'Cold Start'. So, should one do without using this %W format option and parse the actual trap ? ------------------------------------------------------------------------------ This SF.net email is sponsored by: SourcForge Community SourceForge wants to tell your story. http://p.sf.net/sfu/sf-spreadtheword _______________________________________________ Net-snmp-coders mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
