draft-ietf-manet-report-mib-03.txt   draft-ietf-manet-report-mib-04.txt 
Internet Engineering Task Force R. Cole Internet Engineering Task Force R. Cole
Internet-Draft US Army CERDEC Internet-Draft US Army CERDEC
Intended status: Experimental J. Macker Intended status: Experimental J. Macker
Expires: May 4, 2013 Naval Research Laboratory Expires: June 10, 2015 Naval Research Laboratory
A. Bierman A. Bierman
YumaWorks, Inc. YumaWorks, Inc.
November 05, 2012 December 7, 2014
Definition of Managed Objects for Performance Reporting Definition of Managed Objects for Performance Reporting
draft-ietf-manet-report-mib-03 draft-ietf-manet-report-mib-04
Abstract Abstract
This memo defines a portion of the Management Information Base (MIB) This memo defines a portion of the Management Information Base (MIB)
for use with network management protocols in the Internet community. for use with network management protocols in the Internet community.
In particular, it describes objects for configuring autonomous report In particular, it describes objects for configuring autonomous report
generation on any device that supports MIBs containing counter and generation on any device that supports MIBs containing objects that
gauge objects for performance monitoring. This allows a management resolve to type Integer32 (i.e., Integer32, Counter, Gauge, or
station to instruct a device to build off-line reports to be TimeTicks). to be used for performance monitoring. This allows a
collected asynchronously by the management station. Further, this management station to instruct a device to build off-line reports to
REPORT-SAMPLED-MIB can be configured in a proxy configuration where be collected either through notifications to the management station
the report generation is performed on a device in close network or queried asynchronously by the management station. Hence, this
proximity to the device containing the referenced counter objects. capability allows network operators to reduce the SNMP polling
Hence, this capability allows network operators to reduce the SNMP traffic burden on Mobile Ad-Hoc and Disruption Tolerant Networks
polling traffic burden on Mobile Ad-Hoc and Disruption Tolerant which is problematic of SNMP performance management applications.
Networks which is typical of SNMP performance management
applications.
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on May 4, 2013. This Internet-Draft will expire on June 10, 2015.
Copyright Notice Copyright Notice
Copyright (c) 2012 IETF Trust and the persons identified as the
Copyright (c) 2014 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. The Internet-Standard Management Framework . . . . . . . . . . 3 2. The Internet-Standard Management Framework . . . . . . . . . . 3
3. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . 4 3. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . 4
4. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 4. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
4.1. REPORT-SAMPLED-MIB Management Model . . . . . . . . . . . 4 4.1. reportSampledMIB Module Management Model . . . . . . . . . 4
4.2. Terms . . . . . . . . . . . . . . . . . . . . . . . . . . 6 4.2. Terms . . . . . . . . . . . . . . . . . . . . . . . . . . 5
5. Structure of the MIB Module . . . . . . . . . . . . . . . . . 6 5. Structure of the MIB Module . . . . . . . . . . . . . . . . . 6
5.1. Textual Conventions . . . . . . . . . . . . . . . . . . . 6 5.1. Textual Conventions . . . . . . . . . . . . . . . . . . . 7
5.2. The Sampled Group . . . . . . . . . . . . . . . . . . . . 7 5.2. Tables and Indexing . . . . . . . . . . . . . . . . . . . 7
5.3. The Notifications Group . . . . . . . . . . . . . . . . . 7
5.4. Tables and Indexing . . . . . . . . . . . . . . . . . . . 7
6. Relationship to Other MIB Modules . . . . . . . . . . . . . . 8 6. Relationship to Other MIB Modules . . . . . . . . . . . . . . 8
6.1. Relationship to the SNMPv2-MIB . . . . . . . . . . . . . . 9 6.1. Relationship to the SNMPv2-MIB . . . . . . . . . . . . . . 8
6.2. Relationship to the RMON2-MIB . . . . . . . . . . . . . . 9 6.2. Relationship to the RMON2-MIB . . . . . . . . . . . . . . 9
6.3. MIB modules required for IMPORTS . . . . . . . . . . . . . 9 6.3. Relationship to the DISMAN-EVENT-MIB . . . . . . . . . . . 9
7. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 9 6.4. Relationship to the DISMAN-EXPRESSION-MIB . . . . . . . . 10
8. Security Considerations . . . . . . . . . . . . . . . . . . . 21 6.5. MIB modules required for IMPORTS . . . . . . . . . . . . . 10
9. Applicability Statement . . . . . . . . . . . . . . . . . . . 24 7. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 11
10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 25 8. Security Considerations . . . . . . . . . . . . . . . . . . . 26
11. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 25 9. Applicability Statement . . . . . . . . . . . . . . . . . . . 29
12. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 25 10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 30
13. References . . . . . . . . . . . . . . . . . . . . . . . . . . 25 11. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 30
13.1. Normative References . . . . . . . . . . . . . . . . . . . 25 12. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 30
13.2. Informative References . . . . . . . . . . . . . . . . . . 26 13. References . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Appendix A. Change Log . . . . . . . . . . . . . . . . . . . . . 26 13.1. Normative References . . . . . . . . . . . . . . . . . . . 30
Appendix B. Open Issues . . . . . . . . . . . . . . . . . . . . . 28 13.2. Informative References . . . . . . . . . . . . . . . . . . 31
Appendix C. . . . . . . . . . . . . . . . . . . . . . . . . . . 28 Appendix A. Change Log . . . . . . . . . . . . . . . . . . . . . 31
Appendix B. Open Issues . . . . . . . . . . . . . . . . . . . . . 33
Appendix C. . . . . . . . . . . . . . . . . . . . . . . . . . . 34
1. Introduction 1. Introduction
This memo defines a portion of the Management Information Base (MIB) This memo defines a portion of the Management Information Base (MIB)
for use with network management protocols in the Internet community. for use with network management protocols in the Internet community.
In particular, it describes objects for configuring autonomous, off- In particular, it describes objects for configuring autonomous, off-
line report generation for performance monitoring on any device line report generation for performance monitoring on any device
supporting MIBs containing variables that resolve to type Integer32 supporting MIBs containing variables that resolve to type Integer32
(i.e., Integer32, Counter, Gauge, or TimeTicks). This REPORT- (i.e., Integer32, Counter, Gauge, or TimeTicks). This
SAMPLED-MIB allows for the report generation to occur on the same reportSampledMIB module allows for the report generation to occur on
device as containing the referenced counter object or on a device in the same device as containing the referenced counter object. This
close network proximity to the device with the referenced counter should be useful to devices or networks where efficient use of
object. This should be useful to devices or networks where efficient bandwidth is of concern or where intermittent connectivity is common.
use of bandwidth is of concern or where intermittent connectivity is Hence, the reportSampledMIB module is useful for devices managed over
common. Hence, the REPORT-SAMPLED-MIB is useful for devices managed some Mobile Ad-Hoc Networks (MANETs) or Disruption Tolerant Networks
over some Mobile Ad-Hoc Networks (MANETs) or Disruption Tolerant (DTNs).
Networks (DTNs).
This version of the REPORT-SAMPLED-MIB offers one type of off-line This version of the reportSampledMIB module offers one type of off-
reporting. The MIB offers a means to collect sampled data related to line reporting. The MIB offers a means to collect sampled
defined MIB objects. This type of reporting is contained in the measurements related to defined MIB objects. This type of reporting
reportSampledGroup. Other types of report data are possible, is contained in the reportSampledMibObjects. Other types of report
including statistical data and historical data. However, it was felt data are possible, including statistical data. However, it was felt
wise to focus on a more limited scope off-line reporting capability wise to focus on a more limited scope off-line reporting capability
and gain experimental use and application prior to expending energy and gain experimental use and application prior to expending energy
developing a more extensive capability. developing a more extensive off line reporting capability.
For the collection of sampled data, the REPORT-SAMPLED-MIB draws The reportSampledMIB module relies upon the dismanEventMIB module RFC
directly from the usrHistoryGroup from RMON 2 [RFC2021] through 2981 [RFC2981] to monitor the progress of reports being developed
application of the 'AUGMENTS' clause. . Here the within the reportSampledMIB module and to trigger an events, i.e.,
reportSampledControlTable allows the user to define aspects of the notifications containing reports, at the appropriate times. This is
report for sampled data, including the number of MIB objects to be discussed below in more detail in the section entitled 'Relationship
sampled and the nature of the sampling frequency and overall report to the DISMAN-EVENT-MIB'. Further, more sophisticated performance
duration. This group uses the notion of buckets, which contain objects for monitoring from the reportSampledMIB module can be
sampled data from a set of identified MIB objects sampled at the same defined through the dismanExpressionMIB module RFC 2982 [RFC2982]
time point. The report consists of the buckets, each containing sets
of sampled data from the selected MIB objects but at the specific
sampling times. The reportSampledObjectTable allows the user to
identify the multiple MIB objects to be sampled. The
reportSampledDataTable contains the storage of the reported sampled
data contained within buckets, one bucket for each time sampling
instance.
2. The Internet-Standard Management Framework 2. The Internet-Standard Management Framework
For a detailed overview of the documents that describe the current For a detailed overview of the documents that describe the current
Internet-Standard Management Framework, please refer to section 7 of Internet-Standard Management Framework, please refer to section 7 of
RFC 3410 [RFC3410]. RFC 3410 [RFC3410].
Managed objects are accessed via a virtual information store, termed Managed objects are accessed via a virtual information store, termed
the Management Information Base or MIB. MIB objects are generally the Management Information Base or MIB. MIB objects are generally
accessed through the Simple Network Management Protocol (SNMP). accessed through the Simple Network Management Protocol (SNMP).
skipping to change at page 4, line 22 skipping to change at page 4, line 13
[RFC2580]. [RFC2580].
3. Conventions 3. Conventions
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119 [RFC2119]. document are to be interpreted as described in RFC 2119 [RFC2119].
4. Overview 4. Overview
The REPORT-SAMPLED-MIB references performance objects in other MIBs The reportSampledMIB module references performance objects in other
(and in other devices) and generates off-line performance reports MIBs and generates off-line performance reports related to those
related to those referenced objects. The REPORT-SAMPLED-MIB can be referenced objects. The reportSampledMIB module can be coincident
coincident with the other MIB or can reside on another device in with the other MIB modules on the same device containing the
close network proximity to the device containing the referenced referenced performance related object.
performance related object.
4.1. REPORT-SAMPLED-MIB Management Model 4.1. reportSampledMIB Module Management Model
This section describes the management model for the REPORT-SAMPLED- This section describes the management model for the reportSampledMIB
MIB process. module process.
Figure 1 illustrates a potential use of the REPORT-SAMPLED-MIB for The reportSampledMIB module objects are primarily contained within
the generation of off-line, remotely generated reports. The four tables. These are:
management station on the left hand side of the illustration
instructs the remote device to create reports through manipulation of
the ReportCntrl Objects in the REPORT-SAMPLED-MIB resident on the
remote device. The reports instruct the device to monitor the status
of specified counters (on other MIBs and potentially on other devices
in close network proximity) periodically. The reports are stored
locally until the management station decides to pull them off the
device. The figure shows a case where the REPORT-SAMPLED-MIB
generates a notification that Report_2 has completed, prompting the
management station to pull Report_2 from the device.
Mgmt Device o reportSampledControlTable - this is the control table within the
Station reportSampledMIB module. This identifies the OIDs to be monitored
REPORT-SAMPLED-MIB MIB_1 which define the core of the Reports. The control table sets the
+---------+ +-----+ sampling frequency for the Measurements and the number of
| | | | Measurements that will define each Report.
Build_Rep_1 |+-------+| +--+ |
+----------------->||cntrl_1||<------>|PC| |
|+-------+|<-+ +--+--+
| | |
| | | MIB_2
| | | +-----+
| | | |
| | | +--+ |
| | +---->|PC| |
Build_Rep_2 |+-------+| +-->+--+--+
+----------------->||cntrl_2||<---+
|+-------+|
| |
| |
Build_Rep_3 |+-------+|
+----------------->||cntrl_3||<---+ MIB_n
|+-------+| | +-----+
| | | | |
|+-----+ | | +--+ |
||Rep_1| | +-->|PC| |
|+-----+ | +--+--+
| |
|+-----+ |
<------------------||Rep_2| |
Notf_Rep_2 |+-----+ |
| |
|+-----+ |
||Rep_3| |
|+-----+ |
Get_Rep_2 | |
+----------------->| |
| |
<-----------------+| |
Send_Rep_2 +---------+
Figure 1: REPORT-SAMPLED-MIB front-end report generation process. o reportSampledCurrentReportsStatusTable - This table tracks the
status, i.e., the current number of collected Measurements per
each Study. This information can be used by the dismanEventMIB
module to determine when to trigger a notification to the Report
owner containing the Measurements and associated data comprising
the just completed Report.
This version of the REPORT-SAMPLED-MIB provides for the collection of o reportSampledCurrentReportsTable - This table holds the
sampled data instead of statistical data. It does this by augmenting Measurements for the Reports which are in current development.
the usrHistory group from RMON2 [RFC2021] which allows for the
generation of reports collecting the sampled object values binned for o reportSampledHistoricalReportsTable - This table holds the
the purpose of aggregation and efficiency of collection. These are completed Reports for each Study for archival purposes, i.e., the
defined within the reportSampledGroup. The model used for this type Study owners can perform table walks to retrieve archived Reports
of report generation is based upon three tables. The or Studies.
reportSampledControlTable defines aspects of the report generation
related to duration of the reporting interval, the bin (or bucket) The below figure illustrates the four main tables within the
sizes for the report, and the number of object values collected for reportSampledMIB module. Further, if the dismanEventMIB module is so
each bucket. The reportUsrHistoryObjectTable identifies the specific configured to generate triggered notifications, the below figure
MIB objects whose values are binned within the report. And the highlights the 'boolean trigger' and the notification generation.
reportSampledDataTable contains the binned data values collected for The figure further illustrates the movement of completed Reports from
the report. the reportSampledCurrentReportsTable to the
reportSampledHistoricalReportsTable upon Report Completion.
+---------------------------------------------------+
| reportSampledControlEntry |
| { reportSampledStudyStudyIndex } |
| |
| |
| reportSampledStudyNumberReportMeasurements------>----+
+---------------------------------------------------+ |
(boolean
+---------------------------------------------------+ trigger)->--+
| reportSampledCurrentReportsStatusEntry | | |
| { reportSampledStudyStudyIndex } | | |
| | | |
| | | |
| reportSampledNumberOfMeasurementsForCurrentReport--->---+ |
+---------------------------------------------------+ |
V
+---------------------------------------------------+ |
| reportSampledCurrentReportsEntry | |
| { reportSampledStudyStudyIndex, |---->--------+
| reportSampledCurrentMeasurementIndex } | |
| |-->---+ |
+---------------------------------------------------+ | |
(move) |
+---------------------------------------------------+ | |
| reportSampledHistoricalReportsEntry | | |
| { reportSampledStudyStudyIndex, | | |
| reportSampledHistoricalReportIndex, |<--+ |
| reportSampledHistoricalMeasurementIndex } | |
| | |
+---------------------------------------------------+ |
V
(notifications)
4.2. Terms 4.2. Terms
The following definitions apply throughout this document: The following definitions apply throughout this document:
o Control - Objects defined within this document which set the o Sampled - periodic measurement of target OIDs.
parameters for specific reports to be generated offline on the the
remote managed device.
o Data - Objects which hold the sampled report data. o Measurement - a single instance of a sampling event.
5. Structure of the MIB Module o Report - a collection of consecutive Measurements on the same
Sampled target OID.
This section presents the structure of the REPORT-SAMPLED-MIB module. o Study - a series of Reports on the same Sampled target OID.
The objects are arranged into the following groups:
o reportSampledMIBNotifications - defines the notifications o Current Report - a Report which is in the process of being
associated with the REPORT-SAMPLED-MIB. developed.
o reportSampledMIBObjects - defines the objects forming the basis o A Completed Report - contains a pre-defined number of Sampled
for the REPORT-SAMPLED-MIB. These objects are divided up by Measurements.
function into the following groups (currently only one group is
defined):
o o Historical Report - a Report which has previously Completed, and
is being stored locally for archival purposes.
* Sampled Group - This group contains the objects which support 5. Structure of the MIB Module
the generation (collection) of reports exposing sampled data
values.
o reportSampledMIBConformance - Defines a variety of conformance of This section presents the structure of the reportSampledMIB module.
implementations of this REPORT-SAMPLED-MIB. The objects are arranged into the following groups:
5.1. Textual Conventions o reportSampledMibNotifications - defines the notifications
associated with the reportSampledMIB module. These objects define
notifications which track the behavior of the reportSampledMib
module. A single notification is defined in the reportSampledMIB
module which reports a series of failed measurement attempts in
the process of building a Report. Associated with this
notification is a control object which defines a threshold of
failures which would initiate the notification. These
notifications do not cover the triggered notifications which carry
the performance Reports generated by the reportSampledMib module.
These triggered notifications are defined through the use of the
dismanEventMIB module.
No textual conventions are used in the REPORT-SAMPLED-MIB. o reportSampledMibObjects - defines the objects forming the basis
for the reportSampledMIB module. These objects are basically
divided up by function into the following four tables:
5.2. The Sampled Group * reportSampledControlTable - This group contains the objects
which support the generation (collection) of Studies comprising
of Reports exposing sampled Measurement values.
The Sampled Group contains tables which allows for the development of * reportSampledCurrentReportsStatusTable - This group contains
reports based upon sampling the referenced counter objects at the objects which track the collection of Measurements for
specified intervals. The development of this group within the current (in-progress) Reports. This table allows the
REPORT-SAMPLED-MIB which augments the User History group from the dismanEventMIB module to set triggers for Completed Reports
RMON 2 MIB [RFC2021]. The Sampled Group is composed of: which it can then send to the report owner through triggered
notifications.
o reportSampledControlTable - allows for the setting of the * reportSampledCurrentReportsTable - This group contains the
parameters of the report. objects which represent the Measurement data associated with
Current (in-progress) Reports. Once the Report completes, it
is moved to the reportSampledHistoricalReportsTable for
archival purposes.
o reportSampledObjectTable - sets the referenced objects to be * reportSampledHistoricalReportsTable - This group contains the
sampled during the test. With this capability, the management objects which represent archived Completed Reports. This
application can reference multiple objects, all of which are allows the report owners to asynchronously retrieve Reports via
sampled during the test and reported out through the table walks if so desired.
reportSampledData Table.
o reportSampledDataTable - contains the reports. o reportSampledMibConformance - Defines a single basic conformance
of implementations of this reportSampledMIB module.
5.3. The Notifications Group 5.1. Textual Conventions
The Notifications Sub-tree contains the list of notifications No textual conventions are defined in the reportSampledMIB module.
supported within the REPORT-SAMPLED-MIB and their intended purpose or
utility. The single notification defined within this MIB module is
the 'reportSampledNewDataReport'. This notification is sent by the
agent upon completion of a given report on the device. The
notification contains the following objects:
'usrHistoryControlOwner', the entity that configured this report
entry, and the 'reportSampledReportIndex', the index of the data
table for this report. Collectively, these objects allow the
management application to pull the completed report from the agent.
5.4. Tables and Indexing 5.2. Tables and Indexing
The REPORT-SAMPLED-MIB module contains a number of tables which The reportSampledMIB module contains four tables which control and
record data related to: record data related to the creation, notification and storage of
Reports. Specifically:
o the control and generation of remote performance reports, o the control and generation of remote performance Reports, i.e.,
reportSampledControlTable
o the storage of remote performance reports, and o the status of the Current Reports' development, i.e.,
reportSampledCurrentReportsStatusTable,
o the notification of remote report completion. o the Current Reports development and interim data, i.e.,
reportSampledCurrentReportsTable, and
The REPORT-SAMPLED-MIB module's tables are indexed via the following o the historical storage of remote performance Reports, i.e.
reportSampledHistoricalReportsTable.
The reportSampledMIB module's tables are indexed via the following
constructs: constructs:
o usrHistoryControlIndex - from the RMON2-MIB [RFC2021], an index o reportSampledStudyIndex - an index that uniquely identifies a
that uniquely identifies an entry in the usrHistoryControlTable. particular Study. The Study is comprised of multiple Reports, the
Each such entry defines a set of samples at a particular interval number of Reports being stored is defined by the
for a specified set of MIB instances available from the managed reportSampledStudyMaximumNumberOfHistoricalReports object.
system.
o usrHistoryObjectIndex - from the RMON2-MIB, an index used to o reportSampledCurrentMeasurementIndex - an index that uniquely
uniquely identify an entry in the usrHistoryObject table from the identifies an atomic Measurement associated with a Report.
RMON2-MIB. Each such entry defines a MIB instance to be collected
periodically.
o reportSampledReportIndex - an index that uniquely identifies the o reportSampledHistoricalReportIndex - an index that uniquely
particular report an entry is associated with among the set of identifies an archived Completed Report resident within the
reports requested through the reportSampledControlNumber in the reportSampledHistoricalReportsTable.
reportSampledControlEntry.
o reportSampledSampleIndex - an index that uniquely identifies the o reportSampledHistoricalMeasurementIndex - an index that uniquely
particular sample this entry represents among all samples identifies an atomic Measurement comprising an archived Completed
associated with the same reportSampledControlEntry. Report.
These tables and their indexing are: These tables and their indexing are:
o reportSampledControlTable - this table contains a list of data- o reportSampledControlTable - this table contains a list of data-
collection configuration entries defining aspects of the reports. collection configuration entries defining aspects of the studies
These include, e.g., number of reports, their start and stop and their reports to be generated. These include, e.g., number of
times, etc. This table 'AUGMENTS { usrHistoryControlEntry }'. reports per study, the number Reports to be archived, etc. This
table has 'INDEX { reportSampledStudyIndex }'.
o reportSampledObjectTable - this table contains a list of data- o reportSampledCurrentReportsStatusTable - this table contains
collection configuration entries which identify specific MIB objects which track the development of current Reports, e.g., the
entries on other devices to monitor. This table 'AUGMENTS { number of current Measurements collected for each Report under
usrHistoryObjectEntry }'. development. This table has 'INDEX { reportSampledStudyIndex }'.
For each (active) Study, there exists only one Current Report
under development.
o reportSampledTable - this table contains a list of historical o reportSampledCurrentReportsTable - this table contains the
samples collected for the report. This table has 'INDEX { Measurements which are developing the Current Reports. This table
usrHistoryControlIndex, reportSampledReportIndex, has 'INDEX { reportSampledStudyIndex,
reportSampledSampleIndex, usrHistoryObjectIndex }'. reportSampledCurrentMeasurementIndex }'.
o reportSampledHistoricalReportsTable - this table contains the
Reports which have completed. This table has 'INDEX {
reportSampledStudyIndex, reportSampledHistoricalReportIndex,
reportSampledHistoricalMeasurementIndex }'.
6. Relationship to Other MIB Modules 6. Relationship to Other MIB Modules
The text of this section specifies the relationship of the MIB The text of this section specifies the relationship of the MIB
modules contained in this document to other standards, particularly modules contained in this document to other standards, particularly
to standards containing other MIB modules. Definitions imported from to standards containing other MIB modules. Definitions imported from
other MIB modules and other MIB modules that SHOULD be implemented in other MIB modules and other MIB modules that SHOULD be implemented in
conjunction with the MIB module contained within this document are conjunction with the MIB module contained within this document are
identified in this section. identified in this section.
6.1. Relationship to the SNMPv2-MIB 6.1. Relationship to the SNMPv2-MIB
The 'system' group in the SNMPv2-MIB [RFC3418] is defined as being The 'system' group in the SNMPv2-MIB [RFC3418] is defined as being
mandatory for all systems, and the objects apply to the entity as a mandatory for all systems, and the objects apply to the entity as a
whole. The 'system' group provides identification of the management whole. The 'system' group provides identification of the management
entity and certain other system-wide data. The REPORT-SAMPLED-MIB entity and certain other system-wide data. The reportSampledMIB
does not duplicate those objects. module does not duplicate those objects.
6.2. Relationship to the RMON2-MIB 6.2. Relationship to the RMON2-MIB
The REPORT-SAMPLED-MIB is closely related to the RMON2-MIB [RFC2021] The reportSampledMIB module is closely related to and was inspired by
usrHistoryGroup. Specifically, the reportSampledGroup is a direct the the RMON2-MIB module [RFC2021] usrHistoryGroup. The use of
copy of the RMON2 User History Group, with the names changed to control tables to establish the periodic collection of measurement
comply with the naming conventions within the REPORT-SAMPLED-MIB. data for creation of performance reports was pulled from earlier work
Further, the design and use of the control tables within the REPORT- on the RMON2-MIB module.
SAMPLED-MIB draw exactly from the definition of these table
structures in the earlier RMON MIBs through the use of the 'AUGMENTS'
clause within the 'reportSampledControlTable' and the
'reportSampledTable' in this MIB module.
6.3. MIB modules required for IMPORTS 6.3. Relationship to the DISMAN-EVENT-MIB
The reportSampledMIB module was developed to fundamentally work with
the dismanEventMIB module RFC 2981 [RFC2981] in order to offer a
complete and efficient off-line reporting capability for bandwidth
challenged networks such as Mobile Ad-Hoc Networks (MANETs). This is
accomplished through defining trigger test and associated
notification actions indexed by mteOwner, mteTriggerName,
mteObjectsName and mteEventName within the dismanEventMIB module.
Specifically (within the dismanEventMIB module):
In the mteTriggerTable and specifically by setting
o 'mteTriggerTest == boolean(1)',
o 'mteTriggerSampleType == absoluteValue(1)',
o 'mteTriggerValueID ==
reportSampledNumberOfMeasurementsForCurrentReport',
o 'mteTriggerValueIDWildcard == false(1)',
o 'mteTriggerFrequency == 0.5*reportSampledStudySamplingInterval',
and
o 'mteTriggerEnabled == true'.
In the mteTriggerBooleanTable and specifically by setting
o 'mteTriggerBooleanComparison == equal(2)',
o 'mteTriggerBooleanValue == value of
reportSampledStudyNumberReportMeasurements', and
o 'mteTriggerBooleanStartup == false'.
In the mteObjectsTable and specifically by setting
o 'mteObjectsID == reportSampledCurrentMeasurementValue' and
reportSampledCurrentMeasurementTime' and
reportSampledCurrentMeasurementStatus' with
o 'mteObjectsIDWildcard == true' // for each.
In the mteEventTable and specifically by setting
o 'mteEventActions == notification(0)' and
o 'mteEventEnabled == true' // for each.
In the mteEventNotificationTable and specifically by setting
o 'mteEventNotification == mteTriggerFired' and the appropriate
names for the
o 'mteEventNotificationObjectOwner == mteOwner' and
o 'mteEventNotificationObjects == mteObjectsName'.
These settings within the dismanEventMIB module will result in
notifications generated by the dismanEventMIB module which will carry
the recently completed reportSampledMIB module reports.
Set up properly, the dismanEventMIB module will trigger a
notification each time the reportSampledCurrentTable contains a
completed Report. This Report will be sent in a notification
containing three columns of the reportSampledCurrentTable, i.e., the
Value, the Time and the Status, due to the use of wildcarding within
the dismanEventMIB module.
Simultaneously, the reportSampledMIB module will move the completed
Current Report into the reportSampledHistoricalReportsTable and
restart collection for the next Report within the
reportSampledCurrentReportsTable.
6.4. Relationship to the DISMAN-EXPRESSION-MIB
In conjunction with the dismanExpressionMIB module RFC 2982
[RFC2982], the reportSampledMIB module can be used to develop reports
on relatively sophisticated object expressions.
6.5. MIB modules required for IMPORTS
Citations are not permitted within a MIB module, but any module Citations are not permitted within a MIB module, but any module
mentioned in an IMPORTS clause or document mentioned in a REFERENCE mentioned in an IMPORTS clause or document mentioned in a REFERENCE
clause is a Normative reference, and must be cited someplace within clause is a Normative reference, and must be cited someplace within
the narrative sections. Therefore, the imported items in this MIB the narrative sections. Therefore, the imported items in this MIB
module, such as Textual Conventions, that are not already cited, are module, such as Textual Conventions, that are not already cited, are
cited in this section. Since relationships to other MIB modules cited in this section. Since relationships to other MIB modules
should be described in the narrative text, this section will cite should be described in the narrative text, this section will cite
modules from which Textual Conventions are imported. modules from which Textual Conventions are imported.
The REPORT-SAMPLED-MIB module IMPORTS objects from SNMPv2-SMI The reportSampledMIB module IMPORTS objects from SNMPv2-SMI
[RFC2578], SNMPv2-TC [RFC2579], SNMPv2-CONF [RFC2580], IF-MIB [RFC2578], SNMPv2-TC [RFC2579], SNMPv2-CONF [RFC2580], SNMP-
[RFC2863], and INET-ADDRESS-MIB [RFC4001]. Significantly, the FRAMEWORK-MIB [RFC3411], and SNMPv2-MIB [RFC3418].
REPORT-SAMPLED-MIB module also IMPORTS objects from the RMON2-MIB
module [RFC2021].
7. Definitions 7. Definitions
REPORT-SAMPLED-MIB DEFINITIONS ::= BEGIN REPORT-SAMPLED-MIB DEFINITIONS ::= BEGIN
IMPORTS
MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE,
Gauge32, Integer32, experimental
FROM SNMPv2-SMI -- [RFC2578]
TimeStamp
FROM SNMPv2-TC -- [RFC2579]
MODULE-COMPLIANCE, OBJECT-GROUP, IMPORTS
NOTIFICATION-GROUP
FROM SNMPv2-CONF -- [RFC2580]
usrHistoryControlEntry, usrHistoryObjectEntry, MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE,
usrHistoryControlIndex, usrHistoryControlOwner, Gauge32, Integer32, experimental
usrHistoryObjectIndex FROM SNMPv2-SMI -- [RFC2578]
-- usrHistoryControlObjects, usrHistoryControlBucketsRequested,
-- usrHistoryControlBucketsGranted, usrHistoryControlInterval,
-- usrHistoryControlStatus,
-- usrHistoryObjectVariable, usrHistoryObjectSampleType
FROM RMON2-MIB -- [RFC2021]
InetAddress, InetAddressType TimeStamp
FROM INET-ADDRESS-MIB -- [RFC4001] FROM SNMPv2-TC -- [RFC2579]
;
reportSampledMIB MODULE-IDENTITY sysUpTime
LAST-UPDATED "201211051300Z" -- November 05, 2012 FROM SNMPv2-MIB -- [RFC3418]
ORGANIZATION "IETF MANET Working Group"
CONTACT-INFO
"WG E-Mail: manet@ietf.org
WG Chairs: sratliff@cisco.com SnmpAdminString
jmacker@nrl.navy.mil FROM SNMP-FRAMEWORK-MIB -- [RFC3411]
Editors: Robert G. Cole MODULE-COMPLIANCE, OBJECT-GROUP,
US Army CERDEC NOTIFICATION-GROUP
6010 Frankford Road FROM SNMPv2-CONF -- [RFC2580]
Aberdeen Proving Ground, MD 21005 ;
USA
+1 443 395-8744
robert.g.cole@us.army.mil
Joseph Macker reportSampledMIB MODULE-IDENTITY
Naval Research Laboratory LAST-UPDATED "201412011300Z" -- December 01, 2014
Washington, D.C. 20375 ORGANIZATION "IETF MANET Working Group"
USA CONTACT-INFO
macker@itd.nrl.navy.mil "WG E-Mail: manet@ietf.org
Andy Bierman WG Chairs: sratliff@cisco.com
YumaWorks, Inc. jmacker@nrl.navy.mil
andy@yumaworks.com"
DESCRIPTION
"This MIB module contains managed object definitions for
the autonmous reporting of performance object counters.
Copyright (C) The IETF Trust (2009). This version
of this MIB module is part of RFC xxxx; see the RFC
itself for full legal notices."
-- Revision History Editors: Robert G. Cole
REVISION "201211051300Z" -- November 05, 2012 US Army CERDEC
DESCRIPTION 6010 Frankford Road
"The seventh draft of this MIB module published as Aberdeen Proving Ground, MD 21005
draft-ietf-manet-report-mib-03.txt. USA
+1 443 395-8744
robert.g.cole@us.army.mil
Revisions to this draft include Joseph Macker
a) Added a 'Tables and Indexing' section to the Naval Research Laboratory
body of this document. Washington, D.C. 20375
b) Added an 'Applicability Statement' section USA
to the body of this document." macker@itd.nrl.navy.mil
REVISION "201201311300Z" -- January 31, 2012
DESCRIPTION
"The sixth draft of this MIB module published as
draft-ietf-manet-report-mib-02.txt.
Revisions to this draft include Andy Bierman
a) Pulled the statistical and historical reporting YumaWorks, Inc.
from the MIB module and left only the sampled andy@yumaworks.com"
reporting, in order to greatly simplify the DESCRIPTION
first instance of this reporting MIB module. "This MIB module contains managed object definitions for
b) Renamed the module, the REPORT-SAMPLED-MIB the autonmous reporting of performance object counters.
module. Copyright (C) The IETF Trust (2009). This version
c) Leveraged the RMON2-MIB module more effectively of this MIB module is part of RFC xxxx; see the RFC
through the use of the AUGMENTS clause. itself for full legal notices."
d) Changed the module to 'experimental'."
REVISION "201102171300Z" -- February 17, 2011
DESCRIPTION
"The fifth draft of this MIB module published as
draft-ietf-manet-report-mib-01.txt. This document
has been promoted to a MANET Working Group
draft.
Revisions to this draft include -- Revision History
a) Proposed changes to the statsReport table to REVISION "201412011300Z" -- December 01, 2014
simplify communications between device and DESCRIPTION
mgmt application, "The ninth draft of this MIB module published as
b) Added Notifications, draft-ietf-manet-report-mib-04.txt.
c) Changed the reporting structure of the
Sampled and the History reporting
to align with the structure of the
Statistics reports for the purpose of
allowing for efficient notification and
collection of data reports.
d) Ran through smilint to clean up all errors
and most warning. A few still remain."
REVISION "201007051300Z" -- July 05, 2010
DESCRIPTION
"The fourth draft of this MIB module published as
draft-ietf-manet-report-mib-00.txt. This document
has been promoted to a MANET Working Group
draft.
Significant revisions to this draft include Revisions to this draft include
a) added support for proxy configurations through a) A major restructuring of the MIB module in order
the addition of address objects associated with to leverage the dismanEventMIB module for the
the referenced counter objects associated with the automatic notification of Completed Reports.
performance reports." b) Efforts to incorporate this MIB module
REVISION "201003021300Z" -- March 02, 2010 into the DISMAN management architecture.
DESCRIPTION "
"The third draft of this MIB module published as REVISION "201211051300Z" -- November 05, 2012
draft-cole-manet-report-mib-02.txt. Significant DESCRIPTION
revisions to this draft include a) changed naming "The seventh draft of this MIB module published as
of usrHistoryGroup to sampledGroup and b) added draft-ietf-manet-report-mib-03.txt.
a historyGroup."
REVISION "200910251300Z" -- October 25, 2009
DESCRIPTION
"The second draft of this MIB module published as
draft-cole-manet-report-mib-01.txt. Significant
revisions to this draft include a) the inclusion of
raw data collection borrow blatently from the
usrHistory Group within RMON2, b) the deletion of
the CurrentHistoryTable from version -00,
c) modifications to the overall structure of the
MIB, and d) the definition of various Compliance
options for implementations related to this MIB."
REVISION "200904281300Z" -- April 28, 2009
DESCRIPTION
"Initial draft of this MIB module published as
draft-cole-manet-report-mib-00.txt."
-- RFC-Editor assigns XXXX
::= { experimental 998 } -- to be assigned by IANA
-- TEXTUAL CONVENTIONs Revisions to this draft include
-- None a) Added a 'Tables and Indexing' section to the
body of this document.
b) Added an 'Applicability Statement' section
to the body of this document."
REVISION "201201311300Z" -- January 31, 2012
DESCRIPTION
"The sixth draft of this MIB module published as
Revisions to this draft include
a) Pulled the statistical and historical reporting
from the MIB module and left only the sampled
reporting, in order to greatly simplify the
first instance of this reporting MIB module.
b) Renamed the module, the reportSampledMIB module.
c) Leveraged the RMON2-MIB module more effectively
through the use of the AUGMENTS clause.
d) Changed the module to 'experimental'."
REVISION "201102171300Z" -- February 17, 2011
DESCRIPTION
"The fifth draft of this MIB module published as
draft-ietf-manet-report-mib-01.txt. This document
has been promoted to a MANET Working Group
draft.
-- Revisions to this draft include
-- Top-Level Object Identifier Assignments a) Proposed changes to the statsReport table to
-- simplify communications between device and
mgmt application,
b) Added Notifications,
c) Changed the reporting structure of the
Sampled and the History reporting
to align with the structure of the
Statistics reports for the purpose of
allowing for efficient notification and
collection of data reports.
d) Ran through smilint to clean up all errors
and most warning. A few still remain."
REVISION "201007051300Z" -- July 05, 2010
DESCRIPTION
"The fourth draft of this MIB module published as
draft-ietf-manet-report-mib-00.txt. This document
has been promoted to a MANET Working Group
draft.
reportSampledMIBNotifications OBJECT IDENTIFIER Significant revisions to this draft include
::= { reportSampledMIB 0 } a) added support for proxy configurations through
reportSampledMIBObjects OBJECT IDENTIFIER the addition of address objects associated with
::= { reportSampledMIB 1 } the referenced counter objects associated with the
reportSampledMIBConformance OBJECT IDENTIFIER performance reports."
::= { reportSampledMIB 2 } REVISION "201003021300Z" -- March 02, 2010
DESCRIPTION
"The third draft of this MIB module published as
draft-cole-manet-report-mib-02.txt. Significant
revisions to this draft include a) changed naming
of usrHistoryGroup to sampledGroup and b) added
a historyGroup."
REVISION "200910251300Z" -- October 25, 2009
DESCRIPTION
"The second draft of this MIB module published as
draft-cole-manet-report-mib-01.txt. Significant
revisions to this draft include a) the inclusion of
raw data collection borrow blatently from the
usrHistory Group within RMON2, b) the deletion of
the CurrentHistoryTable from version -00,
c) modifications to the overall structure of the
MIB, and d) the definition of various Compliance
options for implementations related to this MIB."
REVISION "200904281300Z" -- April 28, 2009
DESCRIPTION
"Initial draft of this MIB module published as
draft-cole-manet-report-mib-00.txt."
-- RFC-Editor assigns XXXX
::= { experimental 998 } -- to be assigned by IANA
reportSampledGroup OBJECT IDENTIFIER -- TEXTUAL CONVENTIONs
::= { reportSampledMIBObjects 1 } -- None
-- Then, the reportSampledGroup assignments are : --
-- reportSampledControlTable - 1 -- Top-Level Object Identifier Assignments
-- reportSampledObjectTable - 2 --
-- reportSampledDataTable - 3 reportSampledMibNotifications OBJECT IDENTIFIER
::= { reportSampledMIB 0 }
reportSampledMibObjects OBJECT IDENTIFIER
::= { reportSampledMIB 1 }
reportSampledMibConformance OBJECT IDENTIFIER
::= { reportSampledMIB 2 }
reportSampledControlTable OBJECT-TYPE -- The reportSampledMibObjects assignments are :
SYNTAX SEQUENCE OF SampledControlEntry -- reportSampledControlTable - 1
MAX-ACCESS not-accessible -- reportSampledCurrentReportsStatusTable - 2
STATUS current -- reportSampledCurrentReportsTable - 3
DESCRIPTION -- reportSampledHistoricalReportsTable - 4
"A list of data-collection configuration entries.
This table augments the 'usrHistoryControlTable'
from RMON2-MIB (RFC 2021)."
REFERENCE
"RFC 2021 - Remote Network Monitoring Management
Information Base Version 2 (RMON2-MIB),
Waldbusser, S., January 1997."
::= { reportSampledGroup 1 }
reportSampledControlEntry OBJECT-TYPE --
SYNTAX SampledControlEntry -- The Control Table
MAX-ACCESS not-accessible --
STATUS current reportSampledControlTable OBJECT-TYPE
DESCRIPTION SYNTAX SEQUENCE OF reportSampledControlEntry
"A list of parameters that set up a group of user-defined MAX-ACCESS not-accessible
MIB objects to be sampled periodically (called a STATUS current
bucket-group). DESCRIPTION
"A table to configure measurement Studies which
are comprised of multiple Reports."
REFERENCE
"tbd."
::= { reportSampledMibObjects 1 }
For example, an instance of reportSampledControlInterval reportSampledControlEntry OBJECT-TYPE
might be named reportSampledControlInterval.1" SYNTAX ReportSampledControlEntry
AUGMENTS { usrHistoryControlEntry } MAX-ACCESS not-accessible
::= { reportSampledControlTable 1 } STATUS current
DESCRIPTION
"A list of parameters that control the creation of
off-line performance Studies.
SampledControlEntry ::= SEQUENCE { The objects in this table are persistent and when
reportSampledControlRequestedNumber Integer32, written the device SHOULD save the change to
reportSampledControlReportNumber Integer32 non-volatile storage. For further information
} on the storage behavior for these objects, refer
to the description for the reportSampledStudyEntryStatus
object."
INDEX { reportSampledStudyIndex }
::= { reportSampledControlTable 1 }
reportSampledControlRequestedNumber OBJECT-TYPE ReportSampledControlEntry ::= SEQUENCE {
SYNTAX Integer32 (1..127) reportSampledStudyIndex Integer32,
MAX-ACCESS read-create reportSampledStudyOwner SnmpAdminString,
STATUS current reportSampledStudyName SnmpAdminString,
DESCRIPTION reportSampledStudyOid Integer32,
"The number of reports to be generated and stored by this reportSampledStudySamplingInterval Integer32,
agent for this report request. reportSampledStudyNumberReportMeasurements Integer32,
reportSampledStudyMaximumNumberOfHistoricalReports Integer32,
reportSampledStudyEntryStatus RowStatus
}
This object may not be modified if the associated reportSampledStudyIndex OBJECT-TYPE
reportSampledControlStatus object is equal to active(1)." SYNTAX Integer32 (1..127)
DEFVAL { 1 } MAX-ACCESS not-accessible
::= { reportSampledControlEntry 1 } STATUS current
DESCRIPTION
"A unique index that identifies a specific performace
Study. Each Study is comprised of multiple
Reports. Each Report is comprised of multiple
atomic Measurements on a specified object."
::= { reportSampledControlEntry 1 }
reportSampledControlReportNumber OBJECT-TYPE reportSampledStudyOwner OBJECT-TYPE
SYNTAX Integer32 (1..127) SYNTAX SnmpAdminString (SIZE (0..32))
MAX-ACCESS read-only MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of the current report in progress. The first "The owner of the Study."
report is assigned a number equal to '1'. Each successive DEFVAL { ''H }
report number is incremented by unity. When the last report ::= { reportSampledControlEntry 2 }
is completed, this value is set to
reportSampledControlRequestedNumber + 1."
::= { reportSampledControlEntry 2 }
-- Object table reportSampledStudyName OBJECT-TYPE
SYNTAX SnmpAdminString (SIZE (0..32))
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The name of the Study."
DEFVAL { ''H }
::= { reportSampledControlEntry 3 }
reportSampledObjectTable OBJECT-TYPE reportSampledStudyOid OBJECT-TYPE
SYNTAX SEQUENCE OF SampledObjectEntry SYNTAX OBJECT IDENTIFIER
MAX-ACCESS not-accessible MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A list of data-collection configuration entries. "The target OID of the Study. Each Study makes
This table augments the 'usrHistoryObjectTable' periodic Measurements on a specified object
from the RMON2-MIB (RFC 2021)." which is local to this device. Currently, the
REFERENCE objects of study are limited to objects that
"RFC 2021 - Remote Network Monitoring Management resolve to Integer32 (i.e., Integer32, Counter,
Information Base Version 2 (RMON2-MIB), Gauge, or TimeTicks)."
Waldbusser, S., January 1997." ::= { reportSampledControlEntry 4 }
::= { reportSampledGroup 2 }
reportSampledObjectEntry OBJECT-TYPE reportSampledStudySamplingInterval OBJECT-TYPE
SYNTAX SampledObjectEntry SYNTAX Integer32 (1..2147483647)
MAX-ACCESS not-accessible UNITS "seconds"
STATUS current MAX-ACCESS read-create
DESCRIPTION STATUS current
"A list of MIB instances to be sampled periodically. DESCRIPTION
"The time (in seconds) between sampled Measurement
instances."
DEFVAL { 10 }
::= { reportSampledControlEntry 5 }
Entries in this table are created when an associated reportSampledStudyNumberReportMeasurements OBJECT-TYPE
reportSampledControlObjects object is created. SYNTAX Integer32 (1..2147483647)
UNITS "count"
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The number of Meaurements per Report for this Study."
The usrHistoryControlIndex value in the index is DEFVAL { 10 }
that of the associated reportSampledControlEntry. ::= { reportSampledControlEntry 6 }
For example, an instance of reportSampledObjectVariable reportSampledStudyMaximumNumberOfHistoricalReports OBJECT-TYPE
might be reportSampledObjectVariable.1.3" SYNTAX Integer32 (1..2147483647)
AUGMENTS { usrHistoryObjectEntry } UNITS "count"
::= { reportSampledObjectTable 1 } MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The number of Historical Reports to archive locally
for this specific Study. The Historical Reports are
archived locally in the
reportSampledHistoricalReportsTable (below)."
DEFVAL { 10 }
::= { reportSampledControlEntry 7 }
SampledObjectEntry ::= SEQUENCE { reportSampledStudyEntryStatus OBJECT-TYPE
reportSampledObjectIpAddrType InetAddressType, SYNTAX RowStatus
reportSampledObjectIPAddress InetAddress MAX-ACCESS read-create
} STATUS current
DESCRIPTION
"This object permits management of this table
by facilitating actions such as row creation,
construction, and destruction. The value of
this object has no effect on whether other
objects in this conceptual row can be
modified.
reportSampledObjectIpAddrType OBJECT-TYPE An entry may not exist in the 'active' state unless all
SYNTAX InetAddressType objects in the entry have a defined appropriate value. For
MAX-ACCESS read-create objects with DEFVAL clauses, the management station
STATUS current does not need to specify the value of these objects in order
DESCRIPTION for the row to transit to the 'active' state; the default
"This identifies the IP address type value for these objects is used. For objects that do not
of the IP address associated with the have DEFVAL clauses, then the network manager MUST
secondary counter object to be specify the value of these objects prior to this row
monitored within this report. transitioning to the 'active' state.
Only the values ipv4(1) and When this object transitions to 'active', all objects
ipv6(2) are supported. in this row SHOULD be written to non-volatile (stable)
storage. Read-create objects in this row MAY be modified.
When an object in a row with smfCfgIfRowStatus of 'active'
is changed, then the updated value MUST be reflected in SMF
and this new object value MUST be written to non-volatile
storage.
This object may not be modified if the associated If this object is not equal to 'active', all associated
reportStatsControlStatus object is equal to active(1)." entries in the reportSampledCurrentReportsStatusTable,
::= { reportSampledObjectEntry 1 } the reportSampledCurrentReportsTable, and the
reportSampledHistoricalReportsTable MUST be deleted."
::= { reportSampledControlEntry 8 }
reportSampledObjectIPAddress OBJECT-TYPE --
SYNTAX InetAddress (SIZE(4|16)) -- the Current Reports Status Table
MAX-ACCESS read-create --
STATUS current reportSampledCurrentReportsStatusTable OBJECT-TYPE
DESCRIPTION SYNTAX SEQUENCE OF reportSampledCurrentReportsStatusEntry
"This identifies the IP addree of the MAX-ACCESS not-accessible
secondary counter object to be STATUS current
monitored within this report. DESCRIPTION
"A table to tracking the progress of measurements of current
reports in development. Of particular note is the object
reportSampledNumberOfMeasurementsForCurrentReport which
can be compared to the value of the object
reportSampledStudyNumberReportMeasurements by the
dismanEventMIB module and generate triggered
notifications to the Study owner containing the
recently Completed Reports."
REFERENCE
"tbd."
::= { reportSampledMibObjects 2 }
This object may not be modified if the associated reportSampledCurrentReportsStatusEntry OBJECT-TYPE
reportStatsControlStatus object is equal to active(1)." SYNTAX ReportSampledCurrentReportsStatusEntry
::= { reportSampledObjectEntry 2 } MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A list of parameters that track the status of
current Reports in development."
INDEX { reportSampledStudyIndex }
::= { reportSampledCurrentReportsStatusTable 1 }
-- data table ReportSampledCurrentReportsStatusEntry ::= SEQUENCE {
reportSampledTable OBJECT-TYPE reportSampledNumberOfCurrentReport Integer32,
SYNTAX SEQUENCE OF SampledEntry reportSampledNumberOfMeasurementsForCurrentReport Integer32
MAX-ACCESS not-accessible }
STATUS current
DESCRIPTION
"A list of user defined history entries."
::= { reportSampledGroup 3 }
reportSampledEntry OBJECT-TYPE reportSampledNumberOfCurrentReport OBJECT-TYPE
SYNTAX SampledEntry SYNTAX Integer32 (1..2147483647)
MAX-ACCESS not-accessible UNITS "count"
STATUS current MAX-ACCESS read-only
DESCRIPTION STATUS current
"A historical sample of user-defined variables. This sample DESCRIPTION
is associated with the reportSampledControlEntry which set "The number within the Study series of this
up the parameters for a regular collection of these samples. current Report. For each new Report within
the Study, this value MIUST increment by
one. For the first Report in this Study,
the initial value of this object MUST be
set to one. The value MUST wrap back to one
when the value has reached the maximum."
::= { reportSampledCurrentReportsStatusEntry 1 }
The usrHistoryControlIndex value, from the RMON2-MIB reportSampledNumberOfMeasurementsForCurrentReport OBJECT-TYPE
(RFC 2021), in the index identifies the SYNTAX Integer32 (1..2147483647)
reportSampledControlEntry on whose behalf this entry UNITS "count"
was created. MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of Measurements collected so far for
for this specific Report. The initial value
of this object MUST be one. The value MUST
increment be one for each attempted Measurement.
The maximum value for this object is
reportSampledStudyNumberReportMeasurements.
Once this value is reached and the next
Measurement is attempted, the Current Report is
considered Completed, the agent MUST copy
the Completed Report's data from the
reportSampledCurrentReportsTable into the
reportSampledHistoricalReportsTable, and the
next Measurement (strating the next Report in the
Study series) MUST be numbered with the value of
this object as one."
::= { reportSampledCurrentReportsStatusEntry 2 }
The usrHistoryObjectIndex value in the index identifies --
the reportSampledObjectEntry on whose behalf this entry -- the Current Reports Table
was created. --
reportSampledCurrentReportsTable OBJECT-TYPE
SYNTAX SEQUENCE OF ReportSampledCurrentReportsEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A list of measurements being collected for active
Reports."
REFERENCE
" TBD."
::= { reportSampledMibObjects 3 }
For example, an instance of reportSampledAbsValue, which reportSampledCurrentReportsEntry OBJECT-TYPE
represents the 14th sample of a variable collected as SYNTAX ReportSampledCurrentReportsEntry
specified by reportSampledControlEntry.1 and MAX-ACCESS not-accessible
reportSampledObjectEntry.1.5, would be named STATUS current
reportSampledAbsValue.1.14.5" DESCRIPTION
REFERENCE "A list of entries storing the measurements from
"RFC 2021 - Remote Network Monitoring Management active Reports. Once an active, current Report
Information Base Version 2 (RMON2-MIB), completes (when the value of the associated
Waldbusser, S., January 1997." reportSampledNumberOfMeasurementsForCurrentReport
INDEX { usrHistoryControlIndex, reportSampledReportIndex, equals the value of the associated
reportSampledSampleIndex, usrHistoryObjectIndex } reportSampledStudyNumberReportMeasurements), the
::= { reportSampledTable 1 } agent MUST move the Report's data from the
reportSampledCurrentReportsTable to the
reportSampledHistoricalReportTable."
INDEX { reportSampledStudyIndex,
reportSampledCurrentMeasurementIndex }
::= { reportSampledCurrentReportsTable 1 }
SampledEntry ::= SEQUENCE { ReportSampledCurrentReportsEntry ::= SEQUENCE {
reportSampledReportIndex Integer32, reportSampledCurrentMeasurementIndex Integer32,
reportSampledReportID Integer32, reportSampledCurrentMeasurementValue Integer32,
reportSampledSampleIndex Integer32, reportSampledCurrentMeasurementTime sysUpTime,
reportSampledIntervalStart TimeStamp, reportSampledCurrentMeasurementStatus INTEGER
reportSampledIntervalEnd TimeStamp, }
reportSampledAbsValue Gauge32,
reportSampledValStatus INTEGER
}
reportSampledReportIndex OBJECT-TYPE reportSampledCurrentMeasurementIndex OBJECT-TYPE
SYNTAX Integer32 (1..127) SYNTAX Integer32 (1..2147483647)
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An index that uniquely identifies the particular report "An index for this table which represents
this entry is associated with among the set of reports the number of Measurements collected so far for
requested through the reportSampledControlNumber in the for this current Report. The initial value
reportSampledControlEntry. This index starts at 1 and of this object MUST be one. The value MUST
increases by one as each new report is generated." increment be one for each attempted Measurement.
::= { reportSampledEntry 1 } The maximum value for this object is
reportSampledStudyNumberReportMeasurements.
Once this value is reached and the next
Measurement is attempted, the Current Report is
considered Completed, the agent MUST copy
the Completed Report's data from the
reportSampledCurrentReportsTable into the
reportSampledHistoricalReportsTable, and the
next Measurement (strating the next Report in the
Study series) MUST be numbered with the value of
this object as one."
::= { reportSampledCurrentReportsEntry 1 }
reportSampledReportID OBJECT-TYPE reportSampledCurrentMeasurementValue OBJECT-TYPE
SYNTAX Integer32 (1..127) SYNTAX Integer32 (1..2147483647)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An ID that uniquely identifies the particular report "A single measurement for this Study for
this entry is associated with among the set of reports this Current Report. The objects identifying
requested through the reportSampledControlNumber in the the measurement MUST resolve to type Integer32
reportSampledControlEntry. This ID is set to equal the (i.e., Integer32, Counter, Gauge, or TimeTicks).
value of the reportSampledReportIndex." to be used for performance monitoring on this device."
::= { reportSampledEntry 2 } ::= { reportSampledCurrentReportsEntry 2 }
reportSampledSampleIndex OBJECT-TYPE reportSampledCurrentMeasurementTime OBJECT-TYPE
SYNTAX Integer32 (1..2147483647) SYNTAX sysUpTime
MAX-ACCESS not-accessible MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An index that uniquely identifies the particular sample this "The systemUpTime of the device on which the
entry represents among all samples associated with the same measurement was made for this Measurement."
reportSampledControlEntry. This index starts at 1 and ::= { reportSampledCurrentReportsEntry 3 }
increases by one as each new sample is taken."
::= { reportSampledEntry 3 }
reportSampledIntervalStart OBJECT-TYPE reportSampledCurrentMeasurementStatus OBJECT-TYPE
SYNTAX TimeStamp SYNTAX INTEGER {
MAX-ACCESS read-only valueNotAvailable(1),
STATUS current valuePositive(2),
DESCRIPTION valueNegative(3)
"The value of sysUpTime at the start of the interval over }
which this sample was measured. If the probe keeps track of MAX-ACCESS read-only
the time of day, it should start the first sample of the STATUS current
history at a time such that when the next hour of the day DESCRIPTION
begins, a sample is started at that instant. "This object indicates the validity and sign of the
data in the associated value recorded by the
reportSampledCurrentMeasurementValue object."
::= { reportSampledCurrentReportsEntry 4 }
Note that following this rule may require the probe to delay --
collecting the first sample of the history, as each sample -- Historical Reports Table
must be of the same interval. Also note that the sample which --
is currently being collected is not accessible in this table reportSampledHistoricalReportsTable OBJECT-TYPE
until the end of its interval." SYNTAX SEQUENCE OF ReportSampledHistoricalReportsEntry
::= { reportSampledEntry 4 } MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A table archiving non-active Reports for each
defined Study up to a maximum number of Reports
per Study."
::= { reportSampledMibObjects 4 }
reportSampledIntervalEnd OBJECT-TYPE reportSampledHistoricalReportsEntry OBJECT-TYPE
SYNTAX TimeStamp SYNTAX ReportSampledHistoricalReportsEntry
MAX-ACCESS read-only MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The value of sysUpTime at the end of the interval over which "A list of entries storing the measurements from
this sample was measured." Completed Reports. Once an active, current Report
::= { reportSampledEntry 5 } completes (when the value of the associated
reportSampledNumberOfMeasurementsForCurrentReport
equals the value of the associated
reportSampledStudyNumberReportMeasurements), the
agent MUST move the Report's data from the
reportSampledCurrentReportsTable to this
reportSampledHistoricalReportTable."
REFERENCE
" TBD. "
INDEX { reportSampledStudyIndex,
reportSampledHistoricalReportIndex,
reportSampledHistoricalMeasurementIndex }
::= { reportSampledHistoricalReportsTable 1 }
reportSampledAbsValue OBJECT-TYPE ReportSampledHistoricalReportsEntry ::= SEQUENCE {
SYNTAX Gauge32 reportSampledHistoricalReportIndex Integer32,
MAX-ACCESS read-only reportSampledHistoricalMeasurementIndex Integer32,
STATUS current reportSampledHistoricalMeasurementValue Integer32,
DESCRIPTION reportSampledHistoricalMeasurementTime sysUpTime,
"The absolute value (i.e. unsigned value) of the reportSampledHistoricalMeasurementStatus INTEGER
user-specified statistic during the last sampling period. The }
value during the current sampling period is not made available
until the period is completed.
To obtain the true value for this sampling interval, the reportSampledHistoricalReportIndex OBJECT-TYPE
associated instance of reportSampledValStatus must SYNTAX Integer32 (1..2147483647)
be checked, and reportSampledAbsValue adjusted as necessary. MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An index that uniquely identifies the particular Report
archived in this table for the specific Study
(identified by the reportSampledStudyIndex)."
::= { reportSampledHistoricalReportsEntry 1 }
If the MIB instance could not be accessed during the sampling reportSampledHistoricalMeasurementIndex OBJECT-TYPE
interval, then this object will have a value of zero and the SYNTAX Integer32 (1..2147483647)
associated instance of reportSampledValStatus will be set to MAX-ACCESS read-only
'valueNotAvailable(1)'." STATUS current
::= { reportSampledEntry 6 } DESCRIPTION
"An index that uniquely identifies a Measurement for
a specific Report achived in this table for a
Specific Study."
::= { reportSampledHistoriclReportsEntry 2 }
reportSampledValStatus OBJECT-TYPE reportSampledHistoricalReportsValue OBJECT-TYPE
SYNTAX INTEGER { SYNTAX Integer32(1..2147483647)
valueNotAvailable(1), MAX-ACCESS read-only
valuePositive(2), STATUS current
valueNegative(3) DESCRIPTION
} "A single measurement for this Study for
MAX-ACCESS read-only this Completed Report. The objects identifying
STATUS current the measurement MUST resolve to type Integer32
DESCRIPTION (i.e., Integer32, Counter, Gauge, or TimeTicks).
"This object indicates the validity and sign of the data in to be used for performance monitoring on this device."
the associated instance of reportSampledAbsValue. ::= { reportSampledHistoriclReportsEntry 3 }
If the MIB instance could not be accessed during the sampling reportSampledHistoricalMeasurementTime OBJECT-TYPE
interval, then 'valueNotAvailable(1)' will be returned. SYNTAX sysUpTime
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The systemUpTime of the device on which the
measurement was made for this Measurement."
::= { reportSampledHistoriclReportsEntry 5 }
If the sample is valid and actual value of the sample is reportSampledHistoricalMeasurementStatus OBJECT-TYPE
greater than or equal to zero then 'valuePositive(2)' is SYNTAX INTEGER {
returned. valueNotAvailable(1),
valuePositive(2),
valueNegative(3)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object indicates the validity and sign of the
data in the associated value recorded by the
reportSampledHistoricalMeasurementValue object."
::= { reportSampledHistoriclReportsEntry 5 }
If the sample is valid and the actual value of the sample is --
less than zero, 'valueNegative(3)' will be returned. The -- Notifications
associated instance of reportSampledAbsValue should be --
multiplied by -1 to obtain the true sample value."
::= { reportSampledEntry 7 }
-- -- The following notification objects to define issues with making
-- Notifications -- and storing measurements.
--
- <span class="insert">and storing measurements.</span> -- Actions which report data, i.e., Reports, are to be handled by
reportSampledNotificationObjects OBJECT IDENTIFIER -- the dismanEventMIB module.
::= {reportSampledMIBNotifications 0}
-- reportSampledNotificationObjects reportSampledNotificationObjects OBJECT IDENTIFIER
::= {reportSampledMibNotifications 0}
reportSampledNotificationControl OBJECT IDENTIFIER
::= {reportSampledMibNotifications 1}
reportSampledNewDataReport NOTIFICATION-TYPE --
OBJECTS { usrHistoryControlOwner, -- The entity that -- reportSampledNotificationObjects
-- configured this entry --
reportSampledReportID -- The ID of the reportSampledDataCollectionFailure NOTIFICATION-TYPE
-- data table for this report OBJECTS { reportSampledStudyOwner, -- The entity that
} -- configured this Study
STATUS current reportSampledStudyName, -- The name of the Study
DESCRIPTION -- that is failing to
"reportSampledNewDataReport is a notification sent -- collect measurement data
when a new report is completed from the reportSampledStudyOid -- The Object ID being
reportSampledControlTable. The notification carries -- monitored in this Study
the index from the control table that established }
this report and the index from the data table that STATUS current
holds this report. Indication of the new report DESCRIPTION
is when the reportSampledControlReportNumber "The reportSampledDataCollectionFailure is a notification
is incremented." sent when the number of consecutive measurement failures
::= { reportSampledNotificationObjects 1 } within a Current Report, as indicated by consecutive values
of the reportSampledCurrentMeasurementStatus being set
to 'valueNotAvailable(1)', exceeds the value of the
threshold value defined in the
reportSampledDataCollectionFailureThreshold object."
::= { reportSampledNotificationObjects 1 }
-- --
-- Compliance Statements -- nhdpNotificationsControl
-- --
reportSampledDataCollectionFailureThreshold OBJECT-TYPE
SYNTAX Integer32 (1..255)
UNITS "count"
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"A threshold value for the number of
consecutive measurement failures within a
Current Report as indicated by consecutive values
of the reportSampledCurrentMeasurementStatus being
being set to 'valueNotAvailable(1)' which
exceed the value of this threshold. A value of
'255' for this threshold indicates that the
reportSampledDataCollectionFailure notification
is never to be sent. "
DEFVAL { 10 }
::= { nhdpNotificationsControl 1 }
-- Mandatory for Sampled will include all. --
-- Compliance Statements
--
reportSampledCompliances OBJECT IDENTIFIER -- Mandatory compliance for the reportSampledMIB module will
::= { reportSampledMIBConformance 1 } -- include all objects defined within the module.
reportSampledMIBGroups OBJECT IDENTIFIER reportSampledCompliances OBJECT IDENTIFIER
::= { reportSampledMIBConformance 2 } ::= { reportSampledMIBConformance 1 }
reportSampledMIBGroups OBJECT IDENTIFIER
::= { reportSampledMIBConformance 2 }
reportSampledCompliance MODULE-COMPLIANCE reportSampledCompliance MODULE-COMPLIANCE
STATUS current STATUS current
DESCRIPTION "The Sampled basic implementation requirements for DESCRIPTION "The reportSampled basic implementation requirements
managed network entities that implement for managed network entities that implement
the REPORT Sampled process." the REPORT Sampled process."
MODULE -- this module MODULE -- this module
MANDATORY-GROUPS { reportSampledLocalGroup } MANDATORY-GROUPS { reportSampledLocalGroup }
::= { reportSampledCompliances 1 } ::= { reportSampledCompliances 1 }
reportSampledNotificationCompliance MODULE-COMPLIANCE --
STATUS current -- Units of Conformance
DESCRIPTION "The Sampled Notification implementation --
requirements for managed network entities reportSampledLocalGroup OBJECT-GROUP
that implement the REPORT process." OBJECTS {
MODULE -- this module reportSampledStudyOwner,
MANDATORY-GROUPS { reportSampledNotificationObjectGroup } reportSampledStudyName,
::= { reportSampledCompliances 2 } reportSampledStudyOid,
reportSampledStudySamplingInterval,
reportSampledStudyNumberReportMeasurements,
reportSampledStudyMaximumNumberOfHistoricalReports,
reportSampledStudyEntryStatus,
-- Units of Conformance reportSampledNumberOfCurrentReport,
reportSampledNumberOfMeasurementsForCurrentReport,
reportSampledLocalGroup OBJECT-GROUP reportSampledCurrentMeasurementValue,
OBJECTS { reportSampledCurrentMeasurementTime,
reportSampledControlRequestedNumber, reportSampledCurrentMeasurementStatus,
reportSampledControlReportNumber,
reportSampledObjectIpAddrType,
reportSampledObjectIPAddress,
reportSampledReportID,
reportSampledIntervalStart,
reportSampledIntervalEnd,
reportSampledAbsValue,
reportSampledValStatus
}
STATUS current
DESCRIPTION
"Set of REPORT state objects implemented
in this module."
::= { reportSampledMIBGroups 1 }
--reportSampledImportedGroup OBJECT-GROUP reportSampledHistoricalMeasurementValue,
-- OBJECTS { reportSampledHistoricalMeasurementTime,
-- usrHistoryControlObjects, reportSampledHistoricalMeasurementStatus,
-- usrHistoryControlBucketsRequested,
-- usrHistoryControlBucketsGranted,
-- usrHistoryControlInterval,
-- usrHistoryControlOwner,
-- usrHistoryControlStatus,
-- usrHistoryObjectVariable,
-- usrHistoryObjectSampleType
-- }
-- STATUS current
-- DESCRIPTION
-- "Set of REPORT state objects implemented
-- in this module."
--::= { reportSampledMIBGroups 2 }
reportSampledNotificationObjectGroup NOTIFICATION-GROUP reportSampledDataCollectionFailure,
NOTIFICATIONS { reportSampledDataCollectionFailureThreshold
reportSampledNewDataReport }
} STATUS current
STATUS current DESCRIPTION
DESCRIPTION "The basic set of objects in thie reportSampledMIB module
"Set of REPORT notifications implemented to be implemented in order to meet the minimal compliance
in this module for the Sampled reports." conditions."
::= { reportSampledMIBGroups 3 } ::= { reportSampledMIBGroups 1 }
END END
8. Security Considerations 8. Security Considerations
This REPORT-SAMPLED-MIB defines a capability where the local device This reportSampledMIB module defines a capability where the local
may poll other remote devices to collect performance data accessible device may poll other MIB modules on the device to collect
through other MIB modules on the remote devices. These capabilities performance data. These capabilities defined within the
defined within the REPORT-SAMPLED-MIB are control-able by a network reportSampledMIB module are control-able by a network management
management application through SNMP. As such, a network management application through SNMP. As such, a network management application
application could potentially use the REPORT-SAMPLED-MIB as a could potentially use the reportSampledMIB module as a mechanism to
mechanism to implement a Distributed Denial-of-Service (DDoS) attack implement a limited Distributed Denial-of-Service (DDoS) attack
against remote devices. Care should be taken to secure access to the against remote devices by overloading their SNMP processing. Care
REPORT-SAMPLED-MIB agent. Specifically, access control mechanisms should be taken to secure access to the reportSampledMIB module
and authentication mechanisms (via SNMPv3) should always be used for agent. Specifically, access control mechanisms and authentication
SNMP SET operations. Further, some objects may contain data deemed mechanisms (via SNMPv3) should always be used for SNMP SET
sensitive and authentication and encryption mechanisms (via SNMPv3) operations. Further, some objects may contain data deemed sensitive
should be used for SNMP GET operations. and authentication and encryption mechanisms (via SNMPv3) should be
used for SNMP GET operations.
There are a number of management objects defined in this MIB module There are a number of management objects defined in this MIB module
with a MAX-ACCESS clause of read-write and/or read-create. Such with a MAX-ACCESS clause of read-write and/or read-create. Such
objects may be considered sensitive or vulnerable in some network objects may be considered sensitive or vulnerable in some network
environments. The support for SET operations in a non-secure environments. The support for SET operations in a non-secure
environment without proper protection can have a negative effect on environment without proper protection can have a negative effect on
network operations. network operations.
These are the tables and objects and their sensitivity/vulnerability: These are the tables and objects and their sensitivity/vulnerability:
o The reportSampledControlTable is a writable table whose columnar o The reportSampledControlTable is a writable table whose columnar
objects are read-create. The following objects with MAX ACCESS of objects are read-create. The following objects with MAX ACCESS of
read-create and their security sensitivities are: read-create and their security sensitivities are:
o o
* usrHistoryControlBucketRequested - this object identifies the * reportSampledStudyOwner - this object is an administrative
requested number of buckets (or intervals) requested for each string which identifies the the owner of the Study.
identified object for each report instance. As such, this
related to the total device memory necessary to hold the
collected data for the identified reports. The device must
determine whether it has the necessary storage. If not, the
device can indicate the available storage through the
usrHistoryControlBucketGranted object within this table. The
device to protect itself against memory overruns.
* usrHistoryControlInterval - this object identifies the time * reportSampledStudyName - this object is an administrative
interval being sampling events. If set too low, the device may string which gives a name to the Study defined by the objects
not be able to sample the object on remote devices fast enough in this table.
to satisfy the requested interval. Further, setting this value
too low could be used to overwhelm the processing capabilities
of the remote agent, resulting in a Denial-of-Service (DoS)
attack.
* reportSampledControlRequestedNumber - this object identifies * reportSampledStudyOid - this object identifies the the Object
the requested number of consecutive reports of this type to be ID from another MIB module resident on this local device which
generated and stored in this device. When, the value of this forms the measurement basis for the Study. Depending upon the
object should be considered in the local device's estimates of object and the associated process responsible for its
memory consumption related to this control table row. maintenance, polling this object too frequently may place an
undo burden on the process resulting in diminishing its overall
ability to perform its operation.
* usrHistoryControlOwner - this objects provides a name * reportSampledStudySamplingInterval - this object identifies the
associated with the presumed identity of the application time interval being sampling events. If set too low, the
configuring this report. If the local device or management device may not be able to sample the object on remote devices
applications attribute any authority to the values contained in fast enough to satisfy the requested interval. Further,
this object, then it is critical to secure access to setting or setting this value too low could be used to overwhelm the
modifying the value of this object. processing capabilities of the remote agent, resulting in a
form of Denial-of-Service (DoS) attack.
* usrHistoryControlStatus - this is the RowStatus object * reportSampledStudyNumberReportsMeasurements - this object
controlling the configuration of this table row. identifies the requested number of measurements (and associated
storage/memory) for each identified object for each Study
instance. As such, this related to the total device memory
necessary to hold the collected data for the identified
reports. The device must determine whether it has the
necessary storage. If not, the device can reject this value
when requested by returning the .... to protect itself against
memory overruns.
o The reportSampledObjectTable is a writable table whose columnar * reportSampledStudyMaximumNumberOfHistoricalReports - this
objects are read-create. The following objects with MAX ACCESS of object identifies the requested number of Reports for each
read-create and their security sensitivities are: identified object for each Study instance. As such, this
related to the total device memory necessary to hold the
collected data for the identified reports. The device must
determine whether it has the necessary storage. If not, the
device can reject this value when requested by returning the
.... to protect itself against memory overruns.
o * reportSampledStudyEntryStatus - this is the RowStatus object
controlling the configuration of this table row.
* usrHistoryObjectVariable - this object identifies the specific o The reportSampledCurrentReportsStatusTable is a read-only table
OID on a (potentially) remote agent whose counter or gauge containing state information. The information in this Table
values are to be collected for the reports. If, for whatever relates to performance measurements on the underlying Mobile Ad-
reason, the values of this OID collected within the report is Hoc Network (MANET). As such, some of this information may be
deemed sensitive, then the SNMP GET operations issued to deemed sensitive to the overall performance of the MANET and to
collect these values should use SNMPv3 authentication and the organization to which the MANET belongs.
encryption mechanisms to protect.
* reportSampledObjectIpAddrType - this object identifies the o The reportSampledCurrentReportsTable is a read-only table
address type associated with the address of the agent whose OID containing state information. The information in this Table
data is being collected for the report. relates to performance measurements on the underlying Mobile Ad-
Hoc Network (MANET). As such, some of this information may be
deemed sensitive to the overall performance of the MANET and to
the organization to which the MANET belongs.
* reportSampledObjectIpAddress - this object identifies the o The reportSampledHistoricalReportsStatusTable is a read-only table
address associated with the address of the agent whose OID data containing state information. The information in this Table
is being collected for the report. If the address of the relates to performance measurements on the underlying Mobile Ad-
remote devices is deemed sensitive, then the SNMP SETs which Hoc Network (MANET). As such, some of this information may be
write or the SNMP GET which collect this information should be deemed sensitive to the overall performance of the MANET and to
protected using SNMPv3 authentication and encryption the organization to which the MANET belongs.
mechanisms.
* usrHistoryObjectSampleType - this object identifies the the way o The reportSampledDataCollectionFailure notification object reports
in which data values are to be stored within the reports. information regarding the inability of the reportSampledMIB module
from completing its configured reporting mission, including the
specific information that the module is failing to collect. To
some organizations this information may be deemed sensitive to its
mission and may want to protect this information through
encryption mechanisms.
o The reportSampledDataCollectionFailureThreshold object controls
the ability of the device to report information regarding the
inability of the reportSampledMIB module from completing its
configured reporting mission. If set to low, notifications may be
produced too frequently causing processor burdens to the agent and
the collecting manager, and generating too much management traffic
for a bandwidth constrained MANET to support. If set too high,
notifications may not be produced frequently enough for the
collecting manager to properly track the MANET system performance.
SNMP versions prior to SNMPv3 did not include adequate security. SNMP versions prior to SNMPv3 did not include adequate security.
Even if the network itself is secure (for example by using IPSec), Even if the network itself is secure (for example by using IPSec),
even then, there is no control as to who on the secure network is even then, there is no control as to who on the secure network is
allowed to access and GET/SET (read/change/create/delete) the objects allowed to access and GET/SET (read/change/create/delete) the objects
in this MIB module. in this MIB module.
It is RECOMMENDED that implementers consider the security features as It is RECOMMENDED that implementers consider the security features as
provided by the SNMPv3 framework (see [RFC3410], section 8), provided by the SNMPv3 framework (see [RFC3410], section 8),
including full support for the SNMPv3 cryptographic mechanisms (for including full support for the SNMPv3 cryptographic mechanisms (for
skipping to change at page 24, line 10 skipping to change at page 29, line 8
RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to
enable cryptographic security. It is then a customer/operator enable cryptographic security. It is then a customer/operator
responsibility to ensure that the SNMP entity giving access to an responsibility to ensure that the SNMP entity giving access to an
instance of this MIB module is properly configured to give access to instance of this MIB module is properly configured to give access to
the objects only to those principals (users) that have legitimate the objects only to those principals (users) that have legitimate
rights to indeed GET or SET (change/create/delete) them. rights to indeed GET or SET (change/create/delete) them.
9. Applicability Statement 9. Applicability Statement
This document describes objects for configuring parameters of the This document describes objects for configuring parameters of the
remote report generation process on a router or close device. This remote report generation process on a router or other device. This
MIB module, denoted REPORT-SAMPLED-MIB, also reports performance MIB module, denoted reportSampledMIB module, also reports performance
information and notifications. The REPORT-SAMPLED-MIB provides for information and notifications. The reportSampledMIB module provides
the remote control, collection and notification of performance for the remote control, collection and notification of performance
reports on devices. As such, it eliminates the need for periodic reports on devices. As such, it eliminates the need for periodic
polling for counters from remote management stations as a means for polling for counters from remote management stations as a means for
generating performance reports. This is hoped to greatly reduce generating performance reports. This is hoped to greatly reduce
management overhead on the MANET. This sections provides some management overhead on the MANET. This sections provides some
examples of how this MIB module can be used in MANET network examples of how this MIB module can be used in MANET network
deployments. A fuller discussion of MANET network management use deployments. A fuller discussion of MANET network management use
cases and challenges will be provided elsewhere. cases and challenges will be provided elsewhere.
In the following, two scenarios are listed where this MIB module is In the following, two scenarios are identified where this MIB module
useful, i.e., is useful. This list is not complete and other scenarios are
possible.
o For Mobile vehicles with Low Bandwidth Satellite Link to a Fixed o For Mobile vehicles with Low Bandwidth Satellite Link to a Fixed
NOC - Here the vehicles carrying the MANET routers carry multiple Network Operations Center (NOC) - Here the vehicles carrying the
wireless interfaces, one of which is a relatively low-bandwidth MANET routers carry multiple wireless interfaces, one of which is
on-the-move satellite connection which interconnects a fix NOC to a relatively low-bandwidth on-the-move satellite connection which
the nodes of the MANET. Standards-based methods for monitoring interconnects a fix NOC to the nodes of the MANET. Standards-
and fault management from the fixed NOC are necessary for this based methods for monitoring and fault management from the fixed
deployment option. However, to reduce polling overhead over the NOC are necessary for this deployment option. However, to reduce
low bandwidth communications links, the REPORT-SAMPLED-MIB can be polling overhead over the low bandwidth communications links, the
deployed the remote MANET nodes for the remote generation of reportSampledMIB module can be deployed the remote MANET nodes for
performance reports. the remote generation of performance reports.
o For Fixed NOC and Mobile Local Manager in Larger Vehicles - for o For Fixed NOC and Mobile Local Manager in Larger Vehicles - for
larger vehicles, a hierarchical network management arrangement is larger vehicles, a hierarchical network management arrangement is
useful. Centralized network management is performed from a fixed useful. Centralized network management is performed from a fixed
NOC while local management is performed locally from within the NOC while local management, as provided by this reportSampledMIB
vehicles. Standards-based methods for configuration, monitoring, module is performed locally from within the vehicles. Standards-
fault and performance management are necessary for this deployment based methods for configuration, monitoring, fault and performance
option. management are necessary for this deployment option.
10. IANA Considerations 10. IANA Considerations
The MIB module in this document uses the following IANA-assigned The MIB module in this document uses the following IANA-assigned
OBJECT IDENTIFIER values recorded in the SMI Numbers registry: OBJECT IDENTIFIER values recorded in the SMI Numbers registry:
Descriptor OBJECT IDENTIFIER value Descriptor OBJECT IDENTIFIER value
---------- ----------------------- ---------- -----------------------
reportSampledMIB { experimental XXX } reportSampledMIB { experimental XXX }
skipping to change at page 25, line 38 skipping to change at page 30, line 38
within the MANET WG, e.g., NHDP and OLSR MIBs. within the MANET WG, e.g., NHDP and OLSR MIBs.
13. References 13. References
13.1. Normative References 13.1. Normative References
[RFC2021] Waldbusser, S., "Remote Network Monitoring Management [RFC2021] Waldbusser, S., "Remote Network Monitoring Management
Information Base Version 2 using SMIv2", RFC 2021, Information Base Version 2 using SMIv2", RFC 2021,
January 1997. January 1997.
[RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group
MIB", RFC 2863, June 2000.
[RFC3418] Presuhn, R., "Management Information Base (MIB) for the
Simple Network Management Protocol (SNMP)", STD 62,
RFC 3418, December 2002.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J. [RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J.
Schoenwaelder, Ed., "Structure of Management Information Schoenwaelder, Ed., "Structure of Management Information
Version 2 (SMIv2)", STD 58, RFC 2578, April 1999. Version 2 (SMIv2)", STD 58, RFC 2578, April 1999.
[RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J. [RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J.
Schoenwaelder, Ed., "Textual Conventions for SMIv2", Schoenwaelder, Ed., "Textual Conventions for SMIv2",
STD 58, RFC 2579, April 1999. STD 58, RFC 2579, April 1999.
[RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder, [RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder,
"Conformance Statements for SMIv2", STD 58, RFC 2580, "Conformance Statements for SMIv2", STD 58, RFC 2580,
April 1999. April 1999.
[RFC4001] Daniele, M., Haberman, B., Routhier, S., and J. [RFC2981] Kavasseri, R., "Event MIB", RFC 2981, October 2000.
Schoenwaelder, "Textual Conventions for Internet Network
Addresses", RFC 4001, February 2005. [RFC2982] Kavasseri, R., "Distributed Management Expression MIB",
RFC 2982, October 2000.
[RFC3411] Harrington, D., Presuhn, R., and B. Wijnen, "An
Architecture for Describing Simple Network Management
Protocol (SNMP) Management Frameworks", STD 62, RFC 3411,
December 2002.
[RFC3418] Presuhn, R., "Management Information Base (MIB) for the
Simple Network Management Protocol (SNMP)", STD 62,
RFC 3418, December 2002.
13.2. Informative References 13.2. Informative References
[RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart, [RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart,
"Introduction and Applicability Statements for Internet- "Introduction and Applicability Statements for Internet-
Standard Management Framework", RFC 3410, December 2002. Standard Management Framework", RFC 3410, December 2002.
Appendix A. Change Log Appendix A. Change Log
Changes from draft-ietf-manet-report-mib-03 to
draft-ietf-manet-report-mib-04 draft.
1. This version 04 of the reportSampledMIB module represents a
fairly significant restructuring of the MIB module. This
restructuring was necessary in order to align the remote
distributed reporting capabilities of this MIB module with the
prior DISMAN Working Group (WG) efforts at the IETF.
2. The reportSampledCurrentReportsStatusTable was added to allow a
network manager to automate notifications of completed reports
from this MIB module using the dismanEventMIB module.
3. The notifications in this reportSampledMIB module were reduced to
only notifications related to the operation of the data
collections and no longer addressing the reporting of the
performance data itself. This later data is now carried in
notifications under the control of the dismanEventMIB module.
Changes from draft-ietf-manet-report-mib-01 to Changes from draft-ietf-manet-report-mib-01 to
draft-ietf-manet-report-mib-02 draft. draft-ietf-manet-report-mib-02 draft.
1. Stripped the Statistical and the Historical Reports from this 1. Stripped the Statistical and the Historical Reports from this
draft in order to greatly simplify the initial development and draft in order to greatly simplify the initial development and
experiments of this MIB module. experiments of this MIB module.
2. Changed the RFC category to Experimental. 2. Changed the RFC category to Experimental.
3. Completed the Security section. 3. Completed the Security section.
skipping to change at page 27, line 18 skipping to change at page 32, line 40
4. Ran MIB through smilint checker and cleaned up all errors and 4. Ran MIB through smilint checker and cleaned up all errors and
most warnings. A few warnings remain to be addressed. most warnings. A few warnings remain to be addressed.
5. Cleaned up textual material. 5. Cleaned up textual material.
Changes from draft-cole-manet-report-mib-02 to Changes from draft-cole-manet-report-mib-02 to
draft-ietf-manet-report-mib-00 draft. draft-ietf-manet-report-mib-00 draft.
1. Major change was the incorporation of the IP address objects 1. Major change was the incorporation of the IP address objects
associated with all objects of type 'OBJECT IDENTIFIER'. This associated with all objects of type 'OBJECT IDENTIFIER'. This
allows the REPORT-SAMPLED-MIB to exist as a proxy report allows the reportSampledMIB module to exist as a proxy report
generation capability on a device separate but in close proximity generation capability on a device separate but in close proximity
to the device monitoring the referenced object. to the device monitoring the referenced object.
2. Cleaned up the up front text, reducing the repetition with the 2. Cleaned up the up front text, reducing the repetition with the
object descriptions in the MIB. object descriptions in the MIB.
3. Worked on and added sections discussing the relationship to other 3. Worked on and added sections discussing the relationship to other
MIBs. MIBs.
Changes from draft-cole-manet-report-mib-01 to Changes from draft-cole-manet-report-mib-01 to
skipping to change at page 27, line 47 skipping to change at page 33, line 21
3. Added a new historyGroup which provides a history of change 3. Added a new historyGroup which provides a history of change
events. events.
4. Updated the4 Conformance section to reflect the above changes and 4. Updated the4 Conformance section to reflect the above changes and
additions. But did not yet run smilint to check MIB syntax. additions. But did not yet run smilint to check MIB syntax.
Changes from draft-cole-manet-report-mib-00 to Changes from draft-cole-manet-report-mib-00 to
draft-cole-manet-report-mib-01 draft. draft-cole-manet-report-mib-01 draft.
1. Added (copied) the usrHistory group from RMON2 into the REPORT- 1. Added (copied) the usrHistory group from RMON2 into the
SAMPLED-MIB. reportSampledMIB module.
2. Restructured the MIB to account for the inclusion of the 2. Restructured the MIB to account for the inclusion of the
reportSampledGroup. reportSampledMibObjects.
3. Dropped the reportCurReportsTable as this did not make sense 3. Dropped the reportCurReportsTable as this did not make sense
within the context of the REPORT-SAMPLED-MIB. within the context of the reportSampledMIB module.
4. Added the Compliance and Conformance material. Defined several 4. Added the Compliance and Conformance material. Defined several
Compliance Groups to all for base implementations of the REPORT- Compliance Groups to all for base implementations of the
SAMPLED-MIB for only statistical reports, for only historical reportSampledMIB module for only statistical reports, for only
reports or for both. Allow for enhanced implementations to historical reports or for both. Allow for enhanced
address higher capacity issues and extension to metric reporting implementations to address higher capacity issues and extension
for statistical reporting. to metric reporting for statistical reporting.
5. Ran the MIB through the smilint checker and in the process 5. Ran the MIB through the smilint checker and in the process
corrected numerous typos, omissions, TEXTUAL CONVENTIONS, corrected numerous typos, omissions, TEXTUAL CONVENTIONS,
IMPORTS, etc. IMPORTS, etc.
6. Updated main text to reflect changes. 6. Updated main text to reflect changes.
Appendix B. Open Issues Appendix B. Open Issues
This section contains the set of open issues related to the This section contains the set of open issues related to the
development and design of the REPORT-SAMPLED-MIB. This section will development and design of the reportSampledMIB module. This section
not be present in the final version of the MIB and will be removed will not be present in the final version of the MIB and will be
once all the open issues have been resolved. removed once all the open issues have been resolved.
1. Identify all objects requiring non-volatile storage in their 1. Provide references within the REFERENCE clauses in the MIB
module.
2. Identify all objects requiring non-volatile storage in their
DESCRIPTION clauses. DESCRIPTION clauses.
3. Request an initial review of this MIB module by a MIB Doctor
familiar with the work of the DISMAN WG, preferably an author of
the dismanEventMIB module.
Appendix C. Appendix C.
*************************************************************** ***************************************************************
* Note to the RFC Editor (to be removed prior to publication) * * Note to the RFC Editor (to be removed prior to publication) *
* * * *
* 1) The reference to RFCXXXX within the DESCRIPTION clauses * * 1) The reference to RFCXXXX within the DESCRIPTION clauses *
* of the MIB module point to this draft and are to be * * of the MIB module point to this draft and are to be *
* assigned by the RFC Editor. * * assigned by the RFC Editor. *
* * * *
* 2) The reference to RFCXXX2 throughout this document point * * 2) The reference to RFCXXX2 throughout this document point *
skipping to change at page 29, line 15 skipping to change at page 34, line 37
Authors' Addresses Authors' Addresses
Robert G. Cole Robert G. Cole
US Army CERDEC US Army CERDEC
6010 Frankford Road 6010 Frankford Road
Aberdeen Proving Ground, Maryland 21005 Aberdeen Proving Ground, Maryland 21005
USA USA
Phone: +1 443 395 8744 Phone: +1 443 395 8744
EMail: robert.g.cole@us.army.mil EMail: robert.g.cole@us.army.mil
URI: http://www.cs.jhu.edu/~rgcole/
Joseph Macker Joseph Macker
Naval Research Laboratory Naval Research Laboratory
Washington, D.C. 20375 Washington, D.C. 20375
USA USA
EMail: macker@itd.nrl.navy.mil EMail: macker@itd.nrl.navy.mil
Andy Bierman Andy Bierman
YumaWorks, Inc. YumaWorks, Inc.
Redwood City, CA 94065 Redwood City, CA 94065
EMail: andy@yumaworks.com EMail: andy@yumaworks.com
 End of changes. 156 change blocks. 
833 lines changed or deleted 1105 lines changed or added

This html diff was produced by rfcdiff 1.41. The latest version is available from http://tools.ietf.org/tools/rfcdiff/