On Sat, 2006-01-28 at 16:14 -0600, Sonia Garcia wrote:
> #Link Up Trap (0)
> traphandle SNMPv2-SMI::enterprises.311.1.1.3.1.1 ....
But that is not the OID of the "Link Up" notification.
$ snmptranslate -On -IR linkUp
.1.3.6.1.6.3.1.1.5.4
> When I defined the traphandlers, I used the snmptrapd
> log information.
You would have done better by looking at the results
of receiving SNMPv2 traps. The "traphandle" directive
works with SMIv2-style notification OIDs, not SNMPv1-style
(enterprise, generic trap, specific trap) triplets.
> 148.204.218.236) TRAP, SNMP v1,
> community public
> SNMPv2-SMI::enterprises.311.1.1.3.1.1 Link Up Trap (0)
That would be processed by a directive of the form:
traphandle IF-MIB::linkUp ....
or
traphandle .1.3.6.1.6.3.1.1.5.4 ....
> community public
> SNMPv2-SMI::enterprises.52 Enterprise Specific Trap (419)
Try
traphandle SNMPv2-SMI::enterprises.52.0.419 ....
> Another question that I have is what kind of
> information can I obtain from the traps that the
> daemon receives
$ man snmptrapd.conf
The program is fed details about the trap to its standard
input, in the following format, one entry per line:
HOSTNAME
The name of the host in question that sent the trap,
as determined by gethostbyaddr(3).
IPADDRESS
The IP address of the host that sent the trap.
VARBINDS
A list of variable bindings that describe the
trap and the variables enclosed in it.
Dave
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
_______________________________________________
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
