Sorry for the direct email - will keep that in mind!

In response to your questions:

1) Yes - the trap receiver is listening on the specified addressed.  I also 
tried running the snmptrapd command without that address specified with the 
same results.

2) For "host" in the snmptrap command I've tried 10.2.135.137 as well as 
10.2.135.137:162 - same results - nothing happens.

3) With -d on the trap receiver I see packet dumps only when sending from the 
mib browser.  If I send using snmptrap I see nothing.  I'm suspecting that 
there's something wrong with the snmptrap executable at this point.  If I try 
running snmptrap -h I still get absolutely nothing on the console. 


Mike
-----Original Message-----
From: dave.shi...@googlemail.com [mailto:dave.shi...@googlemail.com] On Behalf 
Of Dave Shield
Sent: Wednesday, February 03, 2010 3:43 AM
To: Bowers Mike-cmb004
Cc: net-snmp-users@lists.sourceforge.net
Subject: Re: Problems using snmptrap


    [ First - *please* don't mail me privately, without copying
     any responses to the mailing list.  I don't have the time
     or inclination to offer private, unpaid, SNMP consultancy.
     Keep discussions to the list, where others can both learn
     and offer advice.  Thanks.   ]



On 3 February 2010 03:01, Bowers Mike-cmb004 <michael.bow...@motorola.com> 
wrote:
> My setup is as follows - I have two command prompts open on a windows PC.
> In one I'm running snmptrapd using the command "snmptrapd -Lo -a 
> 10.2.135.137".

So the trap receiver is listening on this address (and this address only).


> I've created the sample MIB referenced in the tutorial docs as follows:

  [snip]


> In a second command prompt I'm trying to send traps using the 
> following command from the tutorial at 
> http://net-snmp.sourceforge.net/wiki/index.php/TUT:snmptrap:
>
> snmptrap -v 1 -c public host UCD-TRAP-TEST-MIB::demotraps "" 6 17 "" 
> SNMPv2-MIB::sysLocation.0 s "Just here"

That looks about right.


> When I do this nothing happens - no errors in the sending window, 
> nothing on the receiving command prompt window.

What are you using for "host" in this command?

>  However, if I load the same MIB contents in to iReasoning, and use it 
> to send the trap, I see the trap received in the command prompt 
> running the snmptrapd command.

Which indicates that the receiver is working fine.
So the problem is most likely at the sending side.



> I'm sure there's a simple setup somewhere that I've overlooked but I 
> haven't found anything yet that has pointed me in the right direction.

The one thing that springs to mind is to make sure that the destination 
specified on the snmptrap command line matches the address that the receiver is 
listening on.

If that doesn't fix it, try running both receiver and sender with the
flag '-d', to dump the raw packets.   What do you see on either side?

Dave

------------------------------------------------------------------------------
The Planet: dedicated and managed hosting, cloud storage, colocation
Stay online with enterprise data centers and the best network in the business
Choose flexible plans and management services without long-term contracts
Personal 24x7 support from experience hosting pros just a phone call away.
http://p.sf.net/sfu/theplanet-com
_______________________________________________
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

Reply via email to