in reply to SNMP Trap not working with Perl 5.8.3

you could always use something like snoop, tcpdump, etc to see if the trap is sending out of the socket.

eliminate one failure possibility at a time.

  1. make sure it's a legit trap (as another poster noted)
  2. make sure the trap is sending (via network sniffers)
  3. make sure the OpenView box is accepting traps for that host
just an off-the-top list.

i don't immediately remember the ports that traps use, and i don't have access to the code i maintained for a trap collector at a previous company, so i'm relying on memory.

Replies are listed 'Best First'.
Re^2: SNMP Trap not working with Perl 5.8.3
by w3ntp (Beadle) on Jun 09, 2004 at 18:33 UTC
    Hi Yes it is a legal trap. Problem is that the trap is not being generated by originating node. used snoop and sniffer to verify. Even if is not a legal trap, something should be sent. thanks Neil
      the last part of the dumb questions -- you *do* have all the required SNMP libs on the machine you're trying to send traps from ....
      [meo@host dir]$ ps ax | grep sn 617 ? S 0:34 /usr/sbin/snmpd -s -l /dev/null -P /var/run +/snmpd -a
      i'd hate for it to be something like that. IIRC, Net::SNMP is an *interface* to SNMP, not a replacement *for* SNMP
        Net::SNMP doesn't depend on any SNMP libraries other than itself; it's a full implementation of SNMP. Clearly it can't be a replacement for SNMP, because SNMP is a protocol, while Net::SNMP is a Perl module. Whether or not there is an snmpd process running doesn't have anything to do with either the presence of SNMP libraries or Net::SNMP. Finally, if Net::SNMP (or nearly any Perl module) is missing one of its dependencies, it won't fail silently; it will raise an exception.