On 07/11/2007, Войнович Андрей Александрович <[EMAIL PROTECTED]> wrote:
> I wrote in the snmptrapd.conf:
>         traphandle .1.3.6.1.4.1.171.10.61.2.1.3.1.6.*   /etc/snmp/down

That script should be triggered when a notification is received with
a snmpTrapOID value starting:

     .1.3.6.1.4.1.171.10.61.2.1.3.1.6....

i.e. some form of private enterprise-specific trap.



> when i remove and insert cabel from port on my device i see in TRAP log the
> following:

> 2007-11-07 11:43:44 10.9.3.251(via UDP: [10.9.3.251]:1024) TRAP, SNMP v1,
> community public
>         SNMPv2-SMI::enterprises.171.10.61.2 Link Down Trap (0) ....

which is the standard linkDown trap - OID .1.3.6.1.6.3.1.1.5.3


> 2007-11-07 11:43:48 10.9.3.251(via UDP: [10.9.3.251]:1024) TRAP, SNMP v1,
> community public
>         SNMPv2-SMI::enterprises.171.10.61.2 Link Up Trap (0)....

which is the standard linkUp trap - OID .1.3.6.1.6.3.1.1.5.4


Neither of these match the OID that you have configured in
the traphandle directive.   So it's reasonable that the script isn't
triggered by a non-matching trap.


Dave
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.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
  • problem with snmp... Войнович Андрей Александрович
    • Re: problem ... Dave Shield

Reply via email to