Network Services Monitoring MIB
RFC 1565
Document | Type |
RFC - Proposed Standard
(January 1994; No errata)
Obsoleted by RFC 2248
|
|
---|---|---|---|
Authors | Ned Freed , Steve Kille | ||
Last updated | 2013-03-02 | ||
Stream | IETF | ||
Formats | plain text html pdf htmlized bibtex | ||
Stream | WG state | (None) | |
Document shepherd | No shepherd assigned | ||
IESG | IESG state | RFC 1565 (Proposed Standard) | |
Consensus Boilerplate | Unknown | ||
Telechat date | |||
Responsible AD | (None) | ||
Send notices to | (None) |
Network Working Group S. Kille, WG Chair Request for Comments: 1565 ISODE Consortium Category: Standards Track N. Freed, Editor Innosoft January 1994 Network Services Monitoring MIB Status of this Memo This document specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "Internet Official Protocol Standards" (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited. Table of Contents 1. Introduction ................................................. 2 2. The SNMPv2 Network Management Framework ...................... 2 2.1 Object Definitions .......................................... 3 3. Rationale for having a Network Services Monitoring MIB ....... 3 3.1 General Relationship to Other MIBs .......................... 4 3.2 Restriction of Scope ........................................ 4 3.3 Relationship to Directory Services .......................... 4 4. Application Objects .......................................... 5 5. Definitions .................................................. 6 6. Acknowledgements .............................................16 7. References ...................................................16 8. Security Considerations ......................................16 9. Authors' Addresses ...........................................17 Kille & Freed [Page 1] RFC 1565 Network Services Monitoring MIB January 1994 1. Introduction There are a wide range of networked applications for which it is appropriate to provide SNMP Monitoring. This includes both TCP/IP and OSI applications. This document defines a MIB which contains the elements common to the monitoring of any network service application. This information includes a table of all monitorable network service applications, a count of the associations (connections) to each application, and basic information about the parameters and status of each application-related association. This MIB may be used on its own for any application, and for most simple applications this will suffice. This MIB is also designed to serve as a building block which can be used in conjunction with application-specific monitoring and management. Two examples of this are MIBs defining additional variables for monitoring a Message Transfer Agent (MTA) service or a Directory Service Agent (DSA) service. It is expected that further MIBs of this nature will be specified. This MIB does not attempt to provide facilities for management of the host or hosts the network service application runs on, nor does it provide facilities for monitoring applications that provide something other than a network service. Host resource and general application monitoring is handled by the Host Resources MIB. 2. The SNMPv2 Network Management Framework The SNMPv2 Network Management Framework consists of four major components. They are: o RFC 1442 [1] which defines the SMI, the mechanisms used for describing and naming objects for the purpose of management. o STD 17, RFC 1213 [2] defines MIB-II, the core set of managed objects for the Internet suite of protocols. o RFC 1445 [3] which defines the administrative and other architectural aspects of the framework. o RFC 1448 [4] which defines the protocol used for network access to managed objects. The Framework permits new objects to be defined for the purpose of experimentation and evaluation. Kille & Freed [Page 2] RFC 1565 Network Services Monitoring MIB January 1994 2.1 Object Definitions Managed objects are accessed via a virtual information store, termed the Management Information Base or MIB. Objects in the MIB are defined using the subset of Abstract Syntax Notation One (ASN.1) defined in the SMI. In particular, each object type is named by an OBJECT IDENTIFIER, an administratively assigned name. The object type together with an object instance serves to uniquely identify a specific instantiation of the object. For human convenience, we often use a textual string, termed the descriptor, to refer to the object type. 3. Rationale for having a Network Services Monitoring MIB Much effort has been expended in developing tools to manage lower layer network facilities. However, relatively little work has been done on managing application layer entities. It is neither efficientShow full document text