Remote Network Monitoring Management Information Base Version 2 using SMIv2
RFC 2021
Document | Type |
RFC - Proposed Standard
(January 1997; Errata)
Obsoleted by RFC 4502
|
|
---|---|---|---|
Author | Steven Waldbusser | ||
Last updated | 2020-01-21 | ||
Stream | Internent Engineering Task Force (IETF) | ||
Formats | plain text html pdf htmlized (tools) htmlized with errata bibtex | ||
Stream | WG state | (None) | |
Document shepherd | No shepherd assigned | ||
IESG | IESG state | RFC 2021 (Proposed Standard) | |
Consensus Boilerplate | Unknown | ||
Telechat date | |||
Responsible AD | (None) | ||
Send notices to | (None) |
Network Working Group S. Waldbusser Request for Comments: 2021 INS Category: Standards Track January 1997 Remote Network Monitoring Management Information Base Version 2 using SMIv2 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. Abstract This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets. In particular, it defines objects for managing remote network monitoring devices. Table of Contents 1 The Network Management Framework ...................... 2 2 Overview .............................................. 2 2.1 Remote Network Management Goals ..................... 3 2.2 Structure of MIB .................................... 5 3 Control of Remote Network Monitoring Devices .......... 6 3.1 Resource Sharing Among Multiple Management Sta- tions .............................................. 7 3.2 Row Addition Among Multiple Management Stations ..... 9 4 Conventions ........................................... 10 5 RMON 2 Conventions .................................... 10 5.1 Usage of the term Application Level ................. 10 5.2 Protocol Directory and Limited Extensibility ........ 11 5.3 Errors in packets ................................... 11 6 Definitions ........................................... 12 7 Security Considerations ............................... 122 8 Appendix - TimeFilter Implementation Notes ........... 123 9 Acknowledgments ...................................... 129 10 References ........................................... 129 11 Author's Address...................................... 130 Waldbusser Standards Track [Page 1] RFC 2021 Remote Network Monitoring MIB January 1997 1. The Network Management Framework The Internet-standard Network Management Framework consists of three components. They are: RFC 1902 [1] which defines the SMI, the mechanisms used for describing and naming objects for the purpose of management. RFC 1213, STD 17, [3] which defines MIB-II, the core set of managed objects for the Internet suite of protocols. RFC 1905 [4] which defines the SNMP, the protocol used for network access to managed objects. The Framework permits new objects to be defined for the purpose of experimentation and evaluation. Managed objects are accessed via a virtual information store, termed the Management Information Base or MIB. Within a given MIB module, objects are defined using the SMI's OBJECT-TYPE macro. At a minimum, each object has a name, a syntax, an access-level, and an implementation-status. The name is an object identifier, an administratively assigned name, which specifies an object type. 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 object descriptor, to also refer to the object type. The syntax of an object type defines the abstract data structure corresponding to that object type. The ASN.1 [6] language is used for this purpose. However, RFC 1902 purposely restricts the ASN.1 constructs which may be used. These restrictions are explicitly made for simplicity. The access-level of an object type defines whether it makes "protocol sense" to read and/or write the value of an instance of the object type. (This access-level is independent of any administrative authorization policy.) The implementation-status of an object type indicates whether the object is mandatory, optional, obsolete, or deprecated. 2. Overview This document continues the architecture created in the RMON MIB [RFC 1757] by providing a major feature upgrade, primarily by providing RMON analysis up to the application layer. Waldbusser Standards Track [Page 2] RFC 2021 Remote Network Monitoring MIB January 1997 Remote network monitoring devices, often called monitors or probes, are instruments that exist for the purpose of managing a network. Often these remote probes are stand-alone devices and devote significant internal resources for the sole purpose of managing a network. An organization may employ many of these devices, one per network segment, to manage its internet. In addition, these devicesShow full document text