Our internal network is finally back up, so I was able to test my theory from yesterday (it stinks coming back from vacation and not being able to get any work done!):
I created an AgentX agent based on the sample 30-second heartbeat code and ran it on a system that did not have snmpd compiled with that support built in (to ensure that the traps are coming from my agent, not snmpd). I am able to receive those heartbeat traps on my trap receiver, but again, my enterprise-defined traps sent out from the same system do NOT get sent to the trap receiver. So does that mean that there's something "wrong" with the way I defined the traps in my MIB??? Or is there something else that needs to be configured for traps from an enterprise OID to be sent out? Can someone please take a look at the MIB snippet from my previous post and see if there's something obvious that I've overlooked? (If you need more detail, just let me know and I'll post it. I'm using the latest version of net-snmp, 5.4.1 on Linux). Thanks!! ~ Wendy -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of McGowen, Wendy Sent: Wednesday, January 02, 2008 9:54 AM To: net-snmp-users@lists.sourceforge.net Subject: AgentX agent not sending traps (was RE: Enterprise trapquestion/send_v2trap API call) Happy New Year, everyone! I didn't see any responses to this issue over the last 2 weeks, and I'm still stuck on this problem. Basically, I am unable to generate any traps from my AgentX agent - I know from my debug output that my code is being triggered, and I'm calling the SNMP API to send the trap accordingly, but nothing happens. The 30-second "built in" heartbeat code (the example) is working just fine, so I know that traps are being sent and received - i.e. the destination is set up correctly in the configuration files. (My earlier response has some of the details.) So is there a known issue with AgentX and traps? Do I need to configure the AgentX agent in some special way to get the traps to work? Or is it more likely something in the way I've defined the trap itself? I used mib2c to create the actual "trap" code, so it should be correct, as far as SNMP is concerned. Here's the trap stuff from my MIB: pivot3 OBJECT IDENTIFIER ::= { enterprises 25148 } pvt3System MODULE-IDENTITY LAST-UPDATED "200712060000Z" DESCRIPTION "MIB for all Pivot3 databank objects" REVISION "200712060000Z" DESCRIPTION "First revision" ::= { pivot3 1 } pvt3SysTraps OBJECT IDENTIFIER ::= { pvt3System 3 } pvt3DatabankDriveStateFailed NOTIFICATION-TYPE OBJECTS { name, slot } STATUS current DESCRIPTION "This trap is sent when the state of a drive in a databank has changed to FAILED." ::= { pvt3SysTraps 7 } Thanks in advance for any advice - I'm really at my wits end here! As an experiment later today, I'm going to try to build the 30-second heartbeat sample trap code as an AgentX agent, and try running that - if I don't see those traps, then I guess it will confirm my suspicion that my problem has to do with the fact that I'm trying to send a trap from an AgentX agent, instead of the main SNMP process. The problem is, I have to compile my stuff separately from SNMP; I can't add the overhead of building the entire SNMP product into our build process. ~ Wendy ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ 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
