Re: [tkined] Using Trap Sink

WILLIAM LEWIS (WLEWIS@erac.com)
Wed, 3 Jun 1998 08:50:39 -0500

Juergen> It is an interesting question whether the current strategie to
drop
Juergen> all traps that do not match the community string of the receiving
SNMP
Juergen> session is reasonable or not. Community string are sometimes used
to
Juergen> indicate the context for a varbind list and there are cases where
you
Juergen> do not know all possible community strings in advance. In these
cases,
Juergen> it would be better to pass all incoming traps to all trap handler
and
Juergen> to let the receiving scripts filter the traps they do not like to
Juergen> process.

Juergen> It is likely that the next major version of the Tnm extension will
Juergen> replace the current strategie with the strategie described above.

louie> Alternatively, have a mechanism whereby you can get all of the
louie> traps regardless of the community; perhaps a distinguished (e.g,
null
louie> string) value for the SNMP session?

Thank you Juergen and Louie.
Armed with Juergen's reply I went to my vender asking them to help me set a
community string in their software. I have yet to receive a response. After
collecting a sum of data I have found that the community string contains
the name of the component that generated the message. In the network I have
over three thousand components that could and do generate messages. Setting
scotty up to receive traps regardless of community is a very attractive
proposition. I am not a programmer but would like to try to set this up. If
you would suggest a starting point and some reference materials, or worst
case let me know if this is beyond the common sysadmin.

Thanks again for all of the help.
Bill

--
!! This message is brought to you via the `tkined & scotty' mailing list.
!! Please do not reply to this message to unsubscribe. To subscribe or
!! unsubscribe, send a mail message to <tkined-request@ibr.cs.tu-bs.de>.
!! See http://wwwsnmp.cs.utwente.nl/~schoenw/scotty/ for more information.