Path: utzoo!mnetor!tmsoft!torsqnt!news-server.csri.toronto.edu!cs.utexas.edu!usc!sdd.hp.com!hplabs!pyramid!lstowell From: lstowell@pyrnova.pyramid.com (Lon Stowell) Newsgroups: comp.protocols.misc Subject: Re: What is Network Management? Message-ID: <139665@pyramid.pyramid.com> Date: 2 Jan 91 23:39:36 GMT Sender: daemon@pyramid.pyramid.com Reply-To: lstowell@pyrnova.pyramid.com (Lon Stowell) Distribution: comp Organization: Pyramid Technology Corp., Mountain View, CA Lines: 143 NONE of the following is to be construed as an official position or opinion of my current employer... Short answer....based loosely on OSI/Network Management forum... Fault Management Configuration Management Performance Management Accounting Management Security Management First a word about providers... There are several Network Management providers....each has differing views of what Network Management is...and is not. This takes the broader view...of a more complete package..this view eliminates Netmaster, etc, as it lacks the broad spectrum of capabilities of a real network manager... IBM's Netview (tm) is the granddaddy. Release 3 and later versions are quite formidable in their capabilities( earlier versions, IMHO, were glorified VTAM operator facilities.. Netview allows true two-way control and communications...network elements with electronic identifiers may use Netview's facilities to provide a full network configuration database of ALL elements, links, hardware components, software components, etc. A facility to automate microcode and code updates is included. A graphic user interface is available.... the full capabilities of Netview and it's "Common Repository" concept are too great to detail here... IBM has excellent documentation, including PC-based self study tutorials on Netview....see any sales office. AT&T has the UNMA, the implementing product is Accumaster Integrator. This product makes somewhat (IMHO) better use of the graphic user interface than does Netview, and has somewhat better facilities and flexibility for connection of "foreign" networks, managers, and facilities. (As opposed to Netview/PC) Both Netview and Accumaster address OSI, although in somewhat differing views. The major difference between Netview and Accumaster is that Netview (personal opinion here) views a network as a bunch of applications mysteriously glued together with data links and hardware. Netviews tools tend to reflect this somewhat--they are formidable at resolving application and session layer difficulties--not too great at resolving (accurately) telecom facility problems. Accumaster tends to view a network as a bunch of telecom facilities with the hosts just another chunk of hardware interfacing to the telecom facilities....and the (current) tools provide formidable facility management and not as elegant applications or session tools... (views are mine--as a user of both) Netview has one formidable advantage over competitors, particularly UNIX based systems... Netview actually emerged from earlier problem reporting tools which are actually implemented in the Operating System's kernel. Unix has no inherent kernel-implemented error logging and reporting facility which compares with EREP...although it would not be rocket science to modify the Unix kernel to include same A dream Net Management package would include a combination of Accumaster and Netview. o There is the forthcoming OSI Network Management architecture which is intended to replace the (largely 1-way) alert and reporting mechanisms of SNMP based on TCP/IP. This OSI NM architecture is intended to provide the five basics of network management: - Fault Management. This will range from detecting, reporting, up through help desk, trouble ticket management, even including fault isolation and recovery. Transient and persistent faults are addressed. The ability to filter, enable, and inhibit alarms is included. Also included is the ability to request self-testing or QOS testing upon schedule or command. - Configuration Management. This includes ALL components of the network... hardware, links, as well as software. Configuration includes all components AND their status. There are 4 subcategories.. Network State Information. This includes the network element connectivity (topology), element operational status, distribution AND configuration of equipment, and availability (operational status) of network resources...applications, ports, links, etc. Also included would be performance measurements and accounting info. Modification of Network Attributes. This allows addition of new features to an existing network or tuning of network operations. Configuration Modification. This allows new network resources and capabilities to be added, allocation of resources to network elements and/or users, as well as dynamic reconfiguration for outages or performance. Inventory Management. This allows control and management of the physical pieces of the network (including software). Facilities are provided to include such information as type, vendor, location, revision levels, and functional criticality. This should include Detailed history such as Type, Serial Number, License Number, Location, Vendor, etc. Financial Information on ownership, warranty, contract status, cross-billing charges, etc. Historical Information on revision changes, prior fault reports, location changes, previous recovery action etc. Directory Maintenance. This would include all hosts, applications, network addresses, access priveleges, security access privileges, service levels, etc. - Performance Management. Provides tools and functions to measure and report on the behavior of network elements,,,hardware, links, software, etc.. This includes the 3 basic features of response time, rejection rates, and availability per cent. Also included are aggregate throughput accounting, user useage accounting, etc. - Accounting Management. Provides user-oriented tools to measure and provide accounting information based on individual users or groups. This includes the ability to set and alter accounting limits associated with the use of network resources. - Security Management. Provides for the addition, deletion, and modification of security services mechanisms and tools. Also provides for the distribution and management of security related information as well as the reporting of all security related events.