OK, so there were two things going on here: 1) When intermapperd started last time, snmptrapd was still running. So apparently intermapperd won't listen on port 162 due to the collision even after snmptrapd was shut down. I had to restart intermapperd after shutting down snmptrapd.
2) The Trap Viewer probe defaults to port 161. Should this be 162 by default to avoid confusion? Viola! Now I'm receiving traps and can begin writing probes accordingly. Thanks to those that replied. -- Dave Stempien University of Rochester Medical Center Information Systems Division (585) 784-2427 On May 4, 2011, at 3:33 PM, Stempien, Dave wrote: > Out of curiosity, how are other InterMapper admins handling SNMP traps (if at > all)? I can't even get the built-in trap viewer probe to display them. I am > seeing them arrive via tcpdump on our InterMapper server, but InterMapper > seems to be ignoring them. If I enable the Net-SNMP snmptrapd, they get > logged just fine. > > Also, does InterMapper log received traps anywhere? The InterMapper > documentation for traps seems to be pretty sparse, and a grep of the > InterMapper forums shows only 18 past discussions involving traps. Am I > being obtuse? > > Thanks, > -- > Dave Stempien > University of Rochester Medical Center > Information Systems Division > (585) 784-2427 > > ____________________________________________________________________ > List archives: > http://www.mail-archive.com/intermapper-talk%40list.dartware.com/ > To unsubscribe: send email to: [email protected] > ____________________________________________________________________ List archives: http://www.mail-archive.com/intermapper-talk%40list.dartware.com/ To unsubscribe: send email to: [email protected]
