[Date Prev]   [Date Next] [Thread Prev]   [Thread Next] [Date Index]   [Thread Index]


     [nocol-users] Re: SNMPMON

[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.
>        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 []: 
  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 []: 
  sysUpTime.0 = 61d 10:16:35.17 
  snmpTrapOID.0 = 
  enterprises. =
  snmpTrapEnterprise.0 = enterprises. 
 - 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 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.