Remote Network Monitoring Management Information Base
RFC 1757
Document | Type |
RFC - Draft Standard
(February 1995; No errata)
Obsoleted by RFC 2819
Obsoletes RFC 1271
|
|
---|---|---|---|
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 1757 (Draft Standard) | |
Consensus Boilerplate | Unknown | ||
Telechat date | |||
Responsible AD | (None) | ||
Send notices to | (None) |
Network Working Group S. Waldbusser Request for Comments: 1757 Carnegie Mellon University Obsoletes: 1271 February 1995 Category: Standards Track Remote Network Monitoring Management Information Base 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 .............................................. 3 2.1 Remote Network Management Goals ...................... 3 2.2 Textual Conventions .................................. 5 2.3 Structure of MIB ..................................... 5 2.3.1 The Ethernet Statistics Group ...................... 6 2.3.2 The History Control Group .......................... 6 2.3.3 The Ethernet History Group ......................... 6 2.3.4 The Alarm Group .................................... 6 2.3.5 The Host Group ..................................... 6 2.3.6 The HostTopN Group ................................. 7 2.3.7 The Matrix Group ................................... 7 2.3.8 The Filter Group ................................... 7 2.3.9 The Packet Capture Group ........................... 7 2.3.10 The Event Group ................................... 7 3. Control of Remote Network Monitoring Devices .......... 7 3.1 Resource Sharing Among Multiple Management Stations .. 8 3.2 Row Addition Among Multiple Management Stations ...... 10 4. Conventions ........................................... 11 5. Definitions ........................................... 11 6. Acknowledgments ....................................... 89 7. References ............................................ 89 8. Security Considerations ............................... 90 Waldbusser [Page 1] RFC 1757 Remote Network Monitoring MIB February 1995 9. Author's Address ...................................... 90 10. Appendix: Changes from RFC 1271 ...................... 91 1. The Network Management Framework The Internet-standard Network Management Framework consists of three components. They are: STD 16, RFC 1155 [1] which defines the SMI, the mechanisms used for describing and naming objects for the purpose of management. STD 16, RFC 1212 [2] defines a more concise description mechanism, which is wholly consistent with the SMI. STD 17, RFC 1213 [3] which defines MIB-II, the core set of managed objects for the Internet suite of protocols. STD 15, RFC 1157 [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 RFC 1212'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[5] language is used for this purpose. However, RFC 1155 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. Waldbusser [Page 2] RFC 1757 Remote Network Monitoring MIB February 1995Show full document text