Thanks for the reply. I actually found what is going on. First of all,
I did not specify the snmp session as version 2 session. Then scotty
discard the version 2 trap for non version 2 session. I just figure out
how to specify the version 2 session. And the version 2 trap is now properly
parsed. It works really well.
With best regards,
--James
> Hi!
>
> jsong@nlc.com (James Song) said:
>
> James> I don't know if the scotty can parse the SNMPv2 trap. I am using
> James> the snmpperl to send the trap. Scotty parses the trap all right
> James> and I am thinking that snmpperl is sending SNMPv2 trap. Now I
> James> have an agent that is developed with using the development
> James> toolkit from SNMP Research. Scotty seems to fail to parse the
> James> SNMPv2 trap from that agent since the trap handler does not
> James> pass the trap to the trap handler proc. I don't see any failure
> James> message from scotty, either. I wonder what the scotty does when
> James> it fails to parse a trap. Any help is greatly appreciated.
>
> Scotty discards packets that seem to be broken or not authentic.
> However, there might be bugs in the trap handling code that did not
> show up yet. You should turn on the debugging mode using the
> `snmp watch on' command. Scotty should print the hex dump of the SNMP
> trap packet. If Scotty does not print the hex dump, it is very likely
> that you have problems running the straps daemon or something like this.
> If you are able to get the hex dump of the packet (and it is ok for you
> to give it away), just send it to me and I will take a look at it.
>
> Juergen
>