[reply to NOCOL list, cross-posted to Scotty/tkined list - anyone else on
both lists/interested in cross-pollination?]
On Wed, 21 Oct 1998, TTSG wrote:
> > Also, can NOCOL watch for SNMP traps? If not, would anyone else be =
> > interested in a monitor to do so if I were to write one?
> >
> > Scott M. Grim
> > Calltech Communications, Inc.
>
> NAME
> trapmon - inform nocol(1) of outstanding SNMP trap mes-
> sages
>
> Tuc/TTSG
OK but what then? Scotty's SNMP trap receiver (part of tkined) gives me
more-or-less useful trap info such as
Mon Nov 09 16:06:23 GMT 1998 SNMPv1 trap from [134.225.144.254]:
sysUpTime.0 = 0d 2:37:44.02
snmpTrapOID.0 = IF-MIB!linkUp
ifIndex.0 = 96
ifAdminStatus.0 = up
ifOperStatus.0 = up
snmpTrapEnterprise.0 = rcTraps
or (where it hasn't got the appropriate MIB loaded, I guess):
Tue Nov 10 02:13:36 GMT 1998 SNMPv1 trap from [134.225.228.253]:
sysUpTime.0 = 61d 10:16:35.17
snmpTrapOID.0 = 1.3.6.1.4.1.11.2.3.7.11.3.0.2
enterprises.18.1.1.26.7.0 =
49:20:31:31:2F:31:30:2F:39:38:20:30:32:3A:31:33:3A:33:36:20:74:69:6D:65
:70:3A:20:63:6C:69:65:6E:74:20:70:6F:6C:6C:69:6E:67:20:73:65:72:76:65:72:20:61:74:20:31:33:34:2E:32:3
2:35:2E:33:32:2E:31:31
snmpTrapEnterprise.0 = enterprises.11.2.3.7.11.3
- but I have to be running Tkined to catch the traps (I think)
All NOCOL's trapmon gives me is reports like:
Wed Nov 18 13:23:00 1998 [trapmon]: SITE Unknown 134.225.226.249 VAR
Enterprise/5 0 0 T
I'm not sure how much use most SNMP traps (e.g. system restart, link
up/down) are to NOCOL: only systems sending repeated traps for e.g.
excessive errors/utilisation on a link fit in with NOCOL's
escalating-severity reporting stategy. Or am I missing something?
--
John Stumbles j.d.stumbles@reading.ac.uk
I.T. Services (Centre), University of Reading http://www.rdg.ac.uk/~suqstmbl
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
If a job's worth doing, it'll still be worth doing tomorrow.
|