practical network management
"25833-Wendell Lansford(F039" <wendell@outland.cc.bellcore.com> Tue, 12 October 1993 19:10 UTC
Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa17826;
12 Oct 93 15:10 EDT
Received: from CNRI.RESTON.VA.US by IETF.CNRI.Reston.VA.US id aa17821;
12 Oct 93 15:10 EDT
Received: from JArthur.CS.HMC.Edu by CNRI.Reston.VA.US id aa17043;
12 Oct 93 15:10 EDT
Received: from jarthur by jarthur.Claremont.EDU id ac12255; 12 Oct 93 9:45 PDT
Received: from lists.psi.com by jarthur.Claremont.EDU id aa11364;
12 Oct 93 9:25 PDT
Received: by lists.psi.com (4.1/SMI-4.1.2-PSI)
id AA24843; Tue, 12 Oct 93 12:06:50 EDT
Return-Path: <wendell@outland.cc.bellcore.com>
Received: from psi.com by lists.psi.com (4.1/SMI-4.1.2-PSI)
id AA24807; Tue, 12 Oct 93 12:06:38 EDT
Received: from outland.cc.bellcore.com by psi.com (4.1/2.1-PSI/PSINet)
id AA05630; Tue, 12 Oct 93 12:07:18 EDT
Received: by outland.cc.bellcore.com id AA25526
(5.65c/IDA-1.4.4 for snmp@psi.com); Tue, 12 Oct 1993 11:32:50 -0400
Date: Tue, 12 Oct 1993 11:32:50 -0400
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: "25833-Wendell Lansford(F039" <wendell@outland.cc.bellcore.com>
MMDF-Warning: Parse error in original version of preceding line at
jarthur.Claremont.EDU
Message-Id: <199310121532.AA25526@outland.cc.bellcore.com>
To: snmp@psi.com
Subject: practical network management
I am in the process of defining and implementing a new corporate-wide network management paradigm. We use an SNMP-based management station and other third-party applicaitons. We are also trailing third-party relational database backend. Such a system, if properly administered, can be a powerful analytical and diagnostic tool. However, A difficult problem seems to be determining what management data is useful. There is an over-abundance of data accessible in the various proprietary and standard MIBs. While we can pontificate about the details of standards and consortiums, a thread delving into network managment strategies, experiences, and practicalities may also prove beneficial to a number of us. Does anyone care to share experiences regarding data collection, aggregation, trending, and analysis? How are people accomplishing fault, configuration, security, performance, and accounting management? What data is important/valuable, either in an abstract sense (such as utilization of WAN links or CPU utilization on a router) or on a specfic level (such as SNMP-MIBII-ifInput)? While such questions are obviously subjective, I believe that one can learn from another's experiences nonetheless. It often seems that functions of mib variables (such as the link utilization as a function of ifInOctets, ifOutOctets, and ifSpeed) are of great interest, as Allan Leinwand pointed out in his article in Vol. 1 No. 5 of _The_Simple_Times_. The ability to aggregate such data and monitor its trends has further value. Our environment is made of up diverse network architectures (ethernet, FDDI, token ring, SNA) and protocols (TCP/IP, AppleTalk, IPX, etc) and spans several locations in the wide area. We have a primarily routed internetwork, but still maintain a number of bridges. Network management is a complex task. I could stand to learn something from other's perspectives. Any info would be appreciated. This may be more appropriate for the netmgrs mailing list, but I lost the address. -- Wendell Lansford Bell Communications Research wendell@cc.bellcore.com 3 Corporate Place, PYA-2E212 (908) 699-6450 Piscataway, New Jersey 08854 --
- practical network management 25833-Wendell Lansford(F039