draft-ietf-rmonmib-rmon2-v2-03.txt   draft-ietf-rmonmib-rmon2-v2-04.txt 
Remote Network Monitoring Remote Network Monitoring
Management Information Base Management Information Base
Version 2 Version 2
<draft-ietf-rmonmib-rmon2-v2-03.txt> <draft-ietf-rmonmib-rmon2-v2-04.txt>
July 14, 2005 August 21, 2005
Steven Waldbusser Steven Waldbusser
waldbusser@nextbeacon.com waldbusser@nextbeacon.com
Status of this Memo Status of this Memo
This document is an Internet-Draft and is subject to all This document is an Internet-Draft and is subject to all
provisions of Section 3 of RFC 3978. provisions of Section 3 of RFC 3978.
skipping to change at page 2, line ? skipping to change at page 2, line ?
that any applicable patent or other IPR claims of which he that any applicable patent or other IPR claims of which he
or she is aware have been or will be disclosed, and any of or she is aware have been or will be disclosed, and any of
which he or she becomes aware will be disclosed, in which he or she becomes aware will be disclosed, in
accordance with Section 6 of BCP 79. accordance with Section 6 of BCP 79.
Internet-Drafts are working documents of the Internet Internet-Drafts are working documents of the Internet
Engineering Task Force (IETF), its areas, and its working Engineering Task Force (IETF), its areas, and its working
groups. Note that other groups may also distribute working groups. Note that other groups may also distribute working
documents as Internet-Drafts. documents as Internet-Drafts.
This document may not be modified, and derivative works of
it may not be created, except to publish it as an RFC and
to translate it into languages other than English other
than to extract section 6 as-is for separate use.
Internet-Drafts are draft documents valid for a maximum of Internet-Drafts are draft documents valid for a maximum of
six months and may be updated, replaced, or obsoleted by six months and may be updated, replaced, or obsoleted by
other documents at any time. It is inappropriate to use other documents at any time. It is inappropriate to use
Internet-Drafts as reference material or to cite them other Internet-Drafts as reference material or to cite them other
than as "work in progress." than as "work in progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt. http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be The list of Internet-Draft Shadow Directories can be
accessed at http://www.ietf.org/shadow.html. accessed at http://www.ietf.org/shadow.html.
This Internet-Draft will expire on January 14, 2006. This Internet-Draft will expire on February 21, 2006.
Distribution of this document is unlimited. Please send Distribution of this document is unlimited. Please send
comments to the RMON WG mailing list <rmonmib@ietf.org>. comments to the RMON WG mailing list <rmonmib@ietf.org>.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2005). Copyright (C) The Internet Society (2005).
Abstract Abstract
skipping to change at page 2, line ? skipping to change at page 2, line ?
with the RMON2-MIB module in this document with the RMON2-MIB module in this document
XXX XXX
Table of Contents Table of Contents
1 The Internet-Standard Management Framework ............ 4 1 The Internet-Standard Management Framework ............ 4
2 Overview .............................................. 5 2 Overview .............................................. 5
2.1 Remote Network Management Goals ..................... 5 2.1 Remote Network Management Goals ..................... 5
2.2 Structure of MIB .................................... 7 2.2 Structure of MIB .................................... 7
3 Control of Remote Network Monitoring Devices .......... 9 3 Control of Remote Network Monitoring Devices .......... 9
3.1 Resource Sharing Among Multiple Management StaĦ 3.1 Resource Sharing Among Multiple Management Sta-
tions .............................................. 9 tions .............................................. 9
3.2 Row Addition Among Multiple Management Stations ..... 11 3.2 Row Addition Among Multiple Management Stations ..... 11
4 Conventions ........................................... 13 4 Conventions ........................................... 14
5 RMON 2 Conventions .................................... 14 5 RMON 2 Conventions .................................... 15
5.1 Usage of the term Application Level ................. 14 5.1 Usage of the term Application Level ................. 15
5.2 Protocol Directory and Limited Extensibility ........ 14 5.2 Protocol Directory and Limited Extensibility ........ 15
5.3 Errors in packets ................................... 15 5.3 Errors in packets ................................... 16
6 Definitions ........................................... 15 6 Definitions ........................................... 16
7 Security Considerations ............................... 142 7 Security Considerations ............................... 146
8 IANA Considerations ................................... 143 8 IANA Considerations ................................... 147
9 Appendix - TimeFilter Implementation Notes ............ 144 9 Appendix - TimeFilter Implementation Notes ............ 148
10 Changes since RFC 2021 ............................... 150 10 Changes since RFC 2021 ............................... 154
11 Acknowledgments ...................................... 153 11 Acknowledgments ...................................... 157
12 Author's Address ..................................... 153 12 Author's Address ..................................... 157
13 References ........................................... 154 13 References ........................................... 158
13.1 Normative References ............................... 154 13.1 Normative References ............................... 158
13.2 Informative References ............................. 154 13.2 Informative References ............................. 159
14 Full Copyright Statement ............................. 155 14 Full Copyright Statement ............................. 159
1. The Internet-Standard Management Framework 1. The Internet-Standard Management Framework
For a detailed overview of the documents that describe the For a detailed overview of the documents that describe the
current Internet-Standard Management Framework, please current Internet-Standard Management Framework, please
refer to section 7 of RFC 3410 [RFC3410]. refer to section 7 of RFC 3410 [RFC3410].
Managed objects are accessed via a virtual information Managed objects are accessed via a virtual information
store, termed the Management Information Base or MIB. MIB store, termed the Management Information Base or MIB. MIB
objects are generally accessed through the Simple Network objects are generally accessed through the Simple Network
skipping to change at page 14, line 47 skipping to change at page 16, line 4
particular protocol, and can be written in such a way that the particular protocol, and can be written in such a way that the
decoding of the next layer up is table-driven. This works decoding of the next layer up is table-driven. This works
when the code has been written to accomodate it and can be when the code has been written to accomodate it and can be
extended no more than one level higher. This extensibility is extended no more than one level higher. This extensibility is
called "limited extensibility" to highlight these limitations. called "limited extensibility" to highlight these limitations.
However, this can be a very useful tool. However, this can be a very useful tool.
For example, suppose that an implementation has C code that For example, suppose that an implementation has C code that
understands how to decode IP packets on any of several understands how to decode IP packets on any of several
ethernet encapsulations, and also knows how to interpret the ethernet encapsulations, and also knows how to interpret the
IP protocol field to recognize UDP packets and how to decode
IP protocol field to recognize UDP packets and how to decode
the UDP port number fields. That implementation may be table- the UDP port number fields. That implementation may be table-
driven so that among the many different UDP port numbers driven so that among the many different UDP port numbers
possible, it is configured to recognize 161 as SNMP, port 53 possible, it is configured to recognize 161 as SNMP, port 53
as DNS, and port 69 as TFTP. The limited extensibility of the as DNS, and port 69 as TFTP. The limited extensibility of the
protocol directory table would allow an SNMP operation to protocol directory table would allow an SNMP operation to
create an entry that would create an additional table mapping create an entry that would create an additional table mapping
for UDP that would recognize UDP port 123 as NTP and begin for UDP that would recognize UDP port 123 as NTP and begin
counting such packets. counting such packets.
This limited extensibility is an option that an implementation This limited extensibility is an option that an implementation
skipping to change at page 16, line 8 skipping to change at page 17, line 10
OwnerString, statistics, history, hosts, OwnerString, statistics, history, hosts,
matrix, filter, etherStatsEntry, historyControlEntry, matrix, filter, etherStatsEntry, historyControlEntry,
hostControlEntry, matrixControlEntry, filterEntry, hostControlEntry, matrixControlEntry, filterEntry,
channelEntry FROM RMON-MIB channelEntry FROM RMON-MIB
tokenRing, tokenRingMLStatsEntry, tokenRingPStatsEntry, tokenRing, tokenRingMLStatsEntry, tokenRingPStatsEntry,
ringStationControlEntry, sourceRoutingStatsEntry ringStationControlEntry, sourceRoutingStatsEntry
FROM TOKEN-RING-RMON-MIB; FROM TOKEN-RING-RMON-MIB;
-- Remote Network Monitoring MIB -- Remote Network Monitoring MIB
rmon MODULE-IDENTITY rmon MODULE-IDENTITY
LAST-UPDATED "200507141500Z" -- July 14, 2005 LAST-UPDATED "200508211500Z" -- August 21, 2005
ORGANIZATION "IETF RMON MIB Working Group" ORGANIZATION "IETF RMON MIB Working Group"
CONTACT-INFO CONTACT-INFO
"Author: "Author:
Steve Waldbusser Steve Waldbusser
Phone: +1-650-948-6500 Phone: +1-650-948-6500
Fax : +1-650-745-0671 Fax : +1-650-745-0671
Email: waldbusser@nextbeacon.com Email: waldbusser@nextbeacon.com
Working Group Chair: Working Group Chair:
Andy Bierman Andy Bierman
skipping to change at page 16, line 33 skipping to change at page 17, line 35
DESCRIPTION DESCRIPTION
"The MIB module for managing remote monitoring "The MIB module for managing remote monitoring
device implementations. This MIB module device implementations. This MIB module
extends the architecture introduced in the original extends the architecture introduced in the original
RMON MIB as specified in RFC 2819. RMON MIB as specified in RFC 2819.
Copyright (C) The Internet Society (2005). This version of Copyright (C) The Internet Society (2005). This version of
this MIB module is part of RFC yyyy; see the RFC itself for this MIB module is part of RFC yyyy; see the RFC itself for
full legal notices." full legal notices."
REVISION "200507141500Z" -- July 14, 2005 REVISION "200508211500Z" -- August 21, 2005
DESCRIPTION DESCRIPTION
"This version updates the proposed-standard version of the "This version updates the proposed-standard version of the
RMON2 MIB (published as RFC 2021) by adding 2 new enumerations RMON2 MIB (published as RFC 2021) by adding 2 new enumerations
to the nlMatrixTopNControlRateBase object and 4 new to the nlMatrixTopNControlRateBase object and 4 new
enumerations to the alMatrixTopNControlRateBase object. These enumerations to the alMatrixTopNControlRateBase object. These
new enumerations support the creation of high capacity topN new enumerations support the creation of high capacity topN
reports in the High Capacity RMON MIB [RFC3273]. reports in the High Capacity RMON MIB [RFC3273].
Additionally, the following objects have been deprecated as Additionally, the following objects have been deprecated as
they have not had enough independent implementations to they have not had enough independent implementations to
skipping to change at page 18, line 26 skipping to change at page 19, line 29
nlMatrixSDDestAddress nlMatrixSDDestAddress
nlMatrixDSSourceAddress nlMatrixDSSourceAddress
nlMatrixDSDestAddress nlMatrixDSDestAddress
nlMatrixTopNSourceAddress nlMatrixTopNSourceAddress
nlMatrixTopNDestAddress nlMatrixTopNDestAddress
alHostEntry alHostEntry
alMatrixSDEntry alMatrixSDEntry
alMatrixDSEntry alMatrixDSEntry
alMatrixTopNSourceAddress alMatrixTopNSourceAddress
alMatrixTopNDestAddress alMatrixTopNDestAddress
"
Finally, the TimeFilter TC has been updated to encourage agent
implementations that allow a MIB walk to behave well even when
performed by an application that is not aware of the special
TimeFilter semantics."
REVISION "200207080000Z" -- 08 July, 2002 REVISION "200207080000Z" -- 08 July, 2002
DESCRIPTION DESCRIPTION
"Added new enumerations to support the High-Capacity RMON "Added new enumerations to support the High-Capacity RMON
MIB as defined in RFC 3273. Also fixed some typos and add MIB as defined in RFC 3273. Also fixed some typos and add
clarifications." clarifications."
REVISION "199605270000Z" -- 27 May, 1996 REVISION "199605270000Z" -- 27 May, 1996
DESCRIPTION DESCRIPTION
"Original version. Published as RFC 2021." "Original version. Published as RFC 2021."
skipping to change at page 101, line 7 skipping to change at page 103, line 28
sampled. sampled.
Because SNMP access control is articulated entirely in terms Because SNMP access control is articulated entirely in terms
of the contents of MIB views, no access control mechanism of the contents of MIB views, no access control mechanism
exists that can restrict the value of this object to identify exists that can restrict the value of this object to identify
only those objects that exist in a particular MIB view. only those objects that exist in a particular MIB view.
Because there is thus no acceptable means of restricting the Because there is thus no acceptable means of restricting the
read access that could be obtained through the user history read access that could be obtained through the user history
mechanism, the probe must only grant write access to this mechanism, the probe must only grant write access to this
object in those views that have read access to all objects on object in those views that have read access to all objects on
the probe. the probe. See USM [RFC3414] and VACM [RFC3415] for more
information.
During a set operation, if the supplied variable name is not During a set operation, if the supplied variable name is not
available in the selected MIB view, a badValue error must be available in the selected MIB view, a badValue error must be
returned. returned.
This object may not be modified if the associated This object may not be modified if the associated
usrHistoryControlStatus object is equal to active(1)." usrHistoryControlStatus object is equal to active(1)."
::= { usrHistoryObjectEntry 2 } ::= { usrHistoryObjectEntry 2 }
usrHistoryObjectSampleType OBJECT-TYPE usrHistoryObjectSampleType OBJECT-TYPE
skipping to change at page 118, line 21 skipping to change at page 121, line 18
trapDestAddress OBJECT-TYPE trapDestAddress OBJECT-TYPE
SYNTAX OCTET STRING SYNTAX OCTET STRING
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS deprecated STATUS deprecated
DESCRIPTION DESCRIPTION
"The address to send traps on behalf of this entry. "The address to send traps on behalf of this entry.
If the associated trapDestProtocol object is equal to ip(1), If the associated trapDestProtocol object is equal to ip(1),
the encoding of this object is the same as the snmpUDPAddress the encoding of this object is the same as the snmpUDPAddress
textual convention in RFC 3417 "Transport Mappings for the textual convention in RFC 3417 'Transport Mappings for the
Simple Network Management Protocol(SNMP)" [RFC3417]: Simple Network Management Protocol(SNMP)' [RFC3417]:
-- for a SnmpUDPAddress of length 6: -- for a SnmpUDPAddress of length 6:
-- --
-- octets contents encoding -- octets contents encoding
-- 1-4 IP-address network-byte order -- 1-4 IP-address network-byte order
-- 5-6 UDP-port network-byte order -- 5-6 UDP-port network-byte order
If the associated trapDestProtocol object is equal to ipx(2), If the associated trapDestProtocol object is equal to ipx(2),
the encoding of this object is the same as the snmpIPXAddress the encoding of this object is the same as the snmpIPXAddress
textual convention in RFC 3417 "Transport Mappings for the textual convention in RFC 3417 "Transport Mappings for the
Simple Network Management Protocol(SNMP)" [RFC3417]: Simple Network Management Protocol(SNMP)" [RFC3417]:
skipping to change at page 140, line 47 skipping to change at page 144, line 23
trapDestCommunity, trapDestProtocol, trapDestAddress, trapDestCommunity, trapDestProtocol, trapDestAddress,
trapDestOwner, trapDestStatus, trapDestOwner, trapDestStatus,
serialConnectDestIpAddress, serialConnectType, serialConnectDestIpAddress, serialConnectType,
serialConnectDialString, serialConnectSwitchConnectSeq, serialConnectDialString, serialConnectSwitchConnectSeq,
serialConnectSwitchDisconnectSeq, serialConnectSwitchDisconnectSeq,
serialConnectSwitchResetSeq, serialConnectSwitchResetSeq,
serialConnectOwner, serialConnectStatus } serialConnectOwner, serialConnectStatus }
STATUS deprecated STATUS deprecated
DESCRIPTION DESCRIPTION
"This group controls the configuration of various operating "This group controls the configuration of various operating
parameters of the probe." parameters of the probe. This group is not referenced by any
MODULE-COMPLIANCE macro because it is 'grandfathered' from
more recent MIB review rules that would require it."
::= { rmon2MIBGroups 10 } ::= { rmon2MIBGroups 10 }
rmon1EnhancementGroup OBJECT-GROUP rmon1EnhancementGroup OBJECT-GROUP
OBJECTS { historyControlDroppedFrames, hostControlDroppedFrames, OBJECTS { historyControlDroppedFrames, hostControlDroppedFrames,
hostControlCreateTime, matrixControlDroppedFrames, hostControlCreateTime, matrixControlDroppedFrames,
matrixControlCreateTime, channelDroppedFrames, matrixControlCreateTime, channelDroppedFrames,
channelCreateTime, filterProtocolDirDataLocalIndex, channelCreateTime, filterProtocolDirDataLocalIndex,
filterProtocolDirLocalIndex } filterProtocolDirLocalIndex }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
skipping to change at page 141, line 36 skipping to change at page 145, line 16
OBJECTS { tokenRingMLStatsDroppedFrames, OBJECTS { tokenRingMLStatsDroppedFrames,
tokenRingMLStatsCreateTime, tokenRingMLStatsCreateTime,
tokenRingPStatsDroppedFrames, tokenRingPStatsCreateTime, tokenRingPStatsDroppedFrames, tokenRingPStatsCreateTime,
ringStationControlDroppedFrames, ringStationControlDroppedFrames,
ringStationControlCreateTime, ringStationControlCreateTime,
sourceRoutingStatsDroppedFrames, sourceRoutingStatsDroppedFrames,
sourceRoutingStatsCreateTime } sourceRoutingStatsCreateTime }
STATUS deprecated STATUS deprecated
DESCRIPTION DESCRIPTION
"This group adds some enhancements to RMON-1 that help "This group adds some enhancements to RMON-1 that help
management stations." management stations. This group is not referenced by any
MODULE-COMPLIANCE macro because it is 'grandfathered' from
more recent MIB review rules that would require it."
::= { rmon2MIBGroups 13 } ::= { rmon2MIBGroups 13 }
END END
7. Security Considerations 7. Security Considerations
In order to implement this MIB, a probe must capture all In order to implement this MIB, a probe must capture all
packets on the locally-attached network, including packets packets on the locally-attached network, including packets
between third parties. These packets are analyzed to collect between third parties. These packets are analyzed to collect
network addresses, protocol usage information, and network addresses, protocol usage information, and
conversation statistics. Data of this nature may be considered conversation statistics. Data of this nature may be considered
skipping to change at page 145, line 49 skipping to change at page 150, line 4
return FALSE; return FALSE;
else else
return TRUE; return TRUE;
} }
The agent applies this function regardless of the The agent applies this function regardless of the
lastActivationTime of the conceptual row in question. In other lastActivationTime of the conceptual row in question. In other
words, counter discontinuities are ignored (i.e. conceptual words, counter discontinuities are ignored (i.e. conceptual
row deleted and then re-created later). An agent should row deleted and then re-created later). An agent should
consider a object instance 'changed' when it is created consider a object instance 'changed' when it is created
(either at restart time for scalars and static objects, or
(either at restart time for scalars and static objects, or
row-creation-time for dynamic tables). row-creation-time for dynamic tables).
Note that using a timeFilter INDEX value of zero removes the Note that using a timeFilter INDEX value of zero removes the
filtering functionality, as the instance will always be filtering functionality, as the instance will always be
'present' according to the test above.
After some deployment experience, it has been determined that After some deployment experience, it has been determined that
a time-filtered table is more efficient to use if the agent a time-filtered table is more efficient to use if the agent
stops a "MIB walk" operation after one time-filtered entry. stops a "MIB walk" operation after one time-filtered entry.
That is, a GetNext or GetBulk operation will provide one pass That is, a GetNext or GetBulk operation will provide one pass
through a given table, i.e., the agent will continue to the through a given table, i.e., the agent will continue to the
next object or table, instead of incrementing a TimeMark INDEX next object or table, instead of incrementing a TimeMark INDEX
value, even if there exists higher TimeMark values which are value, even if there exists higher TimeMark values which are
valid for the same conceptual row. valid for the same conceptual row.
It is acceptable for an agent to implement a time-filtered It is acceptable for an agent to implement a time-filtered
table in this manner, or in the traditional manner (i.e., table in this manner or in the traditional manner (i.e., every
every conceptual time-filtered instance is returned in GetNext conceptual time-filtered instance is returned in GetNext and
and GetBulk PDU responses). GetBulk PDU responses).
1.2) NMS Implementation of a Time-Filtered Table 1.2) NMS Implementation of a Time-Filtered Table
The particular TimeFilter INDEX values used by an NMS reflect The particular TimeFilter INDEX values used by an NMS reflect
the polling interval of the NMS, relative to the particular the polling interval of the NMS, relative to the particular
agent's notion of sysUpTime. agent's notion of sysUpTime.
An NMS needs to maintain one timestamp variable per agent An NMS needs to maintain one timestamp variable per agent
(initialized to zero) for an arbitrary group of time-filtered (initialized to zero) for an arbitrary group of time-filtered
MIB objects that are gathered together in the same PDU. Each MIB objects that are gathered together in the same PDU. Each
skipping to change at page 153, line 5 skipping to change at page 156, line 35
nlMatrixDSSourceAddress nlMatrixDSSourceAddress
nlMatrixDSDestAddress nlMatrixDSDestAddress
nlMatrixTopNSourceAddress nlMatrixTopNSourceAddress
nlMatrixTopNDestAddress nlMatrixTopNDestAddress
alHostEntry alHostEntry
alMatrixSDEntry alMatrixSDEntry
alMatrixDSEntry alMatrixDSEntry
alMatrixTopNSourceAddress alMatrixTopNSourceAddress
alMatrixTopNDestAddress alMatrixTopNDestAddress
Finally, the TimeFilter TC has been updated to encourage agent
implementations that allow a MIB walk to behave well even when
performed by an application that is not aware of the special
TimeFilter semantics.
11. Acknowledgments 11. Acknowledgments
This document was produced by the IETF Remote Network This document was produced by the IETF Remote Network
Monitoring Working Group. Monitoring Working Group.
The TimeFilter mechanism was invented and documented by Jeanne The TimeFilter mechanism was invented and documented by Jeanne
Haney. Haney.
The User History group was created by Andy Bierman. The User History group was created by Andy Bierman.
skipping to change at page 157, line 4 skipping to change at line 6663
an attempt made to obtain a general license or permission for an attempt made to obtain a general license or permission for
the use of such proprietary rights by implementers or users of the use of such proprietary rights by implementers or users of
this specification can be obtained from the IETF on-line IPR this specification can be obtained from the IETF on-line IPR
repository at http://www.ietf.org/ipr. repository at http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its The IETF invites any interested party to bring to its
attention any copyrights, patents or patent applications, or attention any copyrights, patents or patent applications, or
other proprietary rights that may cover technology that may be other proprietary rights that may cover technology that may be
required to implement this standard. Please address the required to implement this standard. Please address the
information to the IETF at ietf-ipr@ietf.org. information to the IETF at ietf-ipr@ietf.org.
Table of Contents
1 The Internet-Standard Management Framework ............ 4
2 Overview .............................................. 5
2.1 Remote Network Management Goals ..................... 5
2.2 Structure of MIB .................................... 7
3 Control of Remote Network Monitoring Devices .......... 9
3.1 Resource Sharing Among Multiple Management StaĦ
tions .............................................. 9
3.2 Row Addition Among Multiple Management Stations ..... 11
4 Conventions ........................................... 13
5 RMON 2 Conventions .................................... 14
5.1 Usage of the term Application Level ................. 14
5.2 Protocol Directory and Limited Extensibility ........ 14
5.3 Errors in packets ................................... 15
6 Definitions ........................................... 15
7 Security Considerations ............................... 142
8 IANA Considerations ................................... 143
9 Appendix - TimeFilter Implementation Notes ............ 144
10 Changes since RFC 2021 ............................... 150
11 Acknowledgments ...................................... 153
12 Author's Address ..................................... 153
13 References ........................................... 154
13.1 Normative References ............................... 154
13.2 Informative References ............................. 154
14 Full Copyright Statement ............................. 155
 End of changes. 

This html diff was produced by rfcdiff 1.25, available from http://www.levkowetz.com/ietf/tools/rfcdiff/