Re: NOC autom problem handling

Daniel MacKay <daniel@nstn.ns.ca> Wed, 30 September 1992 22:40 UTC

Received: from ietf.nri.reston.va.us by IETF.NRI.Reston.VA.US id aa10497; 30 Sep 92 18:40 EDT
Received: from NRI.RESTON.VA.US by IETF.NRI.Reston.VA.US id aa10493; 30 Sep 92 18:40 EDT
Received: from nic.near.net by NRI.Reston.VA.US id aa21905; 30 Sep 92 18:45 EDT
Received: from nic.near.net by nic.near.net id aa27657; 30 Sep 92 18:34 EDT
Received: from owl.nstn.ns.ca by nic.near.net id ab27623; 30 Sep 92 18:32 EDT
Received: by owl.nstn.ns.ca (4.1/SMI-4.1.1) id AA05842; Wed, 30 Sep 92 19:32:31 ADT
Sender: ietf-archive-request@IETF.NRI.Reston.VA.US
From: Daniel MacKay <daniel@nstn.ns.ca>
Message-Id: <9209302232.AA05842@owl.nstn.ns.ca>
Subject: Re: NOC autom problem handling
To: ucp@nic.near.net
Date: Wed, 30 Sep 92 19:32:30 ADT
In-Reply-To: <9209301454.AA01294@mate.inf.ufrgs.br>; from "Ewerton Longoni Madruga" at Sep 30, 92 11:54 am
X-Mailer: ELM [version 2.3 PL0]

Ewerton Longoni Madruga writes:

>         Anyway, I wonder if there is any "specimen" of
> NOC-supporting applications, which reacts automatically to incoming
> traps and events for problem solving.

My feeling is that if you have problems that are so regular that you want a
program to help deal with them, you should be dealing with the source of
the problems instead!

I.e. if a router is breaking down and must be rebooted regularly, then that
router should be replaced.  If a modem must be regularly reset because of a
bad communication line, that line should be cleaned up.

I agree fully that NOC staff shouldn't be doing routine work- but my
standpoint is that there shouldn't *be* any routine work.

(except writing damn monthly progress reports.  OH GOD I hate this time of
the month. :-)
--
	Daniel MacKay				daniel@nstn.ns.ca
	NOC Manager, NSTN Operations Centre	902-494-NSTN
	Dalhousie University, Halifax, Nova Scotia, Canada