Re: Cannot Process SNMP Traps

Russ Woodman Thu, 16 Dec 2004 21:25:25 -0800

Gary,

Forgive me if anything I say after this sentence is naive or misinformed.

Gary Clark wrote:

Hi,
Ok three months....Good one.

That's probably an understatement. So much for trying to figure it out on my own.

1) When running your agent have you configured your snmpd.conf to send
traps?

As stated below, I'm trying to receive traps from external devices (Cisco routers, etc.) so I'm not sure why this is relevant.

2) When running the snmptrapd it also has an associated configuration file
this
     should contain an oid value and a perl script which is called when the
trap is received.

My snmptrapd.conf is shown below in the original message. It contains a traphandle line with a default entry for processing any trap (I would think).

3) Examine the FAQ. This has more information.


I've read the man pages and FAQs a hundred times if I've read them once.

4)  The most obvious trap to look for is the coldStart trap which is sent
when your agent
      has completed initialisation.

I'll attempt to get my local agent to send a trap to the local host. This is something I hadn't tried previously because I'm not interested in Linux server snmp traps on the local host.

5) If you get stuck I will help you more so dont panic ok.


I appreciate that.

Cheers,
Garyc

----- Original Message -----
From: "Russ Woodman" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, December 14, 2004 9:48 AM
Subject: Cannot Process SNMP Traps

Hi,

I am attempting to receive traps from various devices on my network
(Copper Mountain DSLAMs, Cisco routers, etc.) so that I can then funnel
the traps into Nagios for network monitoring.  However, nothing I have
tried for the last three or more months has allowed me to receive/handle
any traps sent by any devices.  Below are some relevant files and
configuration.

10782 ?        S      0:00 /usr/sbin/snmpd -Lsd -Lf /dev/null -p
/var/run/snmpd.pid
10784 ?        Ss     0:00 /usr/sbin/snmptrapd -Lsd -p
/var/run/snmptrapd.pid

snmptrapd.conf:
traphandle default /usr/local/bin/traphandle.sh default

traphandle.sh:
#!/bin/bash

LOGFILE="/tmp/snmptrapd.log"

case ${1} in
  default)
    echo -e "Found default trap:" >> ${LOGFILE}
    echo -e "${*}\n" >> ${LOGFILE}
    ;;
  *)
    echo -e "Found unhandled trap:" >> ${LOGFILE}
    echo -e "${*}\n" >> ${LOGFILE}
    ;;
esac

exit 0

snmp.conf
mibs ALL

I have the Copper Mountain MIB located in /usr/share/snmp/mibs, where
all of the other default MIBs are located.  When run in debug mode, the
snmptrapd output shows the Copper Mountain MIB is processed.  When I
bring up and drop an interfaces on a Copper Mountain DSLAM, tcpdump on
the receiving host running snmptrapd shows:

09:36:35.926828 IP 172.20.7.2.1966 >
ldhl-sentry.natcotech.com.snmp-trap:  C=Natco Trap(36)  E:1996
172.20.7.2 enterpriseSpecific s=12 132246500 .iso.org=[|snmp]
09:37:14.772609 IP 172.20.7.2.1967 >
ldhl-sentry.natcotech.com.snmp-trap:  C=Natco Trap(36)  E:1996
172.20.7.2 enterpriseSpecific s=12 132246890 .iso.org=[|snmp]

So I know the trap packet is being received.  But the file
/tmp/snmptrapd.log referenced in the traphandle.sh script never has
anything in it.

Can someone please help me figure out why I have never been able to
receive or process SNMP traps using net-snmp--before I go stark raving
mad?  If someone is able to work with me via phone or IM in an
interactive way, that would be greatly appreciated.

Regards,
Russ

------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ _______________________________________________ Net-snmp-users mailing list [EMAIL PROTECTED] Please see the following page to unsubscribe or change other options: https://lists.sourceforge.net/lists/listinfo/net-snmp-users

Re: Cannot Process SNMP Traps

Reply via email to