Remote Network Monitoring Management Information Base for High Capacity Networks
RFC 3273
| Document | Type |
RFC - Proposed Standard
(July 2002; No errata)
Updated by RFC 4502
|
|
|---|---|---|---|
| Last updated | 2015-10-14 | ||
| Stream | IETF | ||
| Formats | plain text pdf html bibtex | ||
| Stream | WG state | (None) | |
| Document shepherd | No shepherd assigned | ||
| IESG | IESG state | RFC 3273 (Proposed Standard) | |
| Consensus Boilerplate | Unknown | ||
| Telechat date | |||
| Responsible AD | Bert Wijnen | ||
| IESG note | Responsible: Finished | ||
| Send notices to | (None) | ||
Network Working Group S. Waldbusser
Request for Comments: 3273 July 2002
Category: Standards Track
Remote Network Monitoring Management Information Base for High
Capacity Networks
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.
Copyright Notice
Copyright (C) The Internet Society (2002). All Rights Reserved.
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 (RMON) devices for use on high speed networks. This
document contains a MIB Module that defines these new objects and
also contains definitions of some updated objects from the RMON-MIB
in RFC 2819 and the RMON2-MIB in RFC 2021.
Table of Contents
1 The SNMP Management Framework ............................... 2
2 Overview .................................................... 3
2.1 Structure of MIB .......................................... 3
3 Updates to RMON MIB and RMON2 MIB objects ................... 4
4 Conventions ................................................. 6
5 Definitions ................................................. 7
6 Security Considerations .....................................73
7 Acknowledgments .............................................73
8 References ..................................................73
9 Notices .....................................................75
10 Author's Address.............................................76
11 Full Copyright Statement.....................................77
Waldbusser Standards Track [Page 1]
RFC 3273 Remote Network Monitoring Management July 2002
1. The SNMP Management Framework
The SNMP Management Framework presently consists of five major
components:
o An overall architecture, described in RFC 2571 [1].
o Mechanisms for describing and naming objects and events for the
purpose of management. The first version of this Structure of
Management Information (SMI) is called SMIv1 and described in
STD 16, RFC 1155 [2], STD 16, RFC 1212 [3], and RFC 1215 [4].
The second version, called SMIv2, is described in STD 58, RFC
2578 [5], RFC 2579 [6], and RFC 2580 [7].
o Message protocols for transferring management information. The
first version of the SNMP message protocol is called SNMPv1 and
is described in STD 15, RFC 1157 [8]. A second version of the
SNMP message protocol, which is not an Internet standards track
protocol, is called SNMPv2c and is described in RFC 1901 [9],
and RFC 1906 [10]. The third version of the message protocol
is called SNMPv3 and is described in RFC 1906 [10], RFC 2572
[11], and RFC 2574 [12].
o Protocol operations for accessing management information. The
first set of protocol operations and associated PDU formats is
described in STD 15, RFC 1157 [8]. A second set of protocol
operations and associated PDU formats is described in RFC 1905
[13].
o A set of fundamental applications described in RFC 2573 [14]
and the view-based access control mechanism described in RFC
2575 [15].
A more detailed introduction to the current SNMP Management Framework
can be found in RFC 2570 [22].
Managed objects are accessed via a virtual information store, termed
the Management Information Base or MIB. Objects in the MIB are
defined using the mechanisms defined in the SMI.
This memo specifies a MIB module that is compliant to the SMIv2. A
MIB conforming to the SMIv1 can be produced through the appropriate
translations. The resulting translated MIB must be semantically
equivalent, except where objects or events are omitted because no
translation is possible (use of Counter64). Some machine readable
information in SMIv2 will be converted into textual descriptions in
Waldbusser Standards Track [Page 2]
RFC 3273 Remote Network Monitoring Management July 2002
SMIv1 during the translation process. However, this loss of machine
Show full document text