draft-ietf-manet-report-mib-02.txt   draft-ietf-manet-report-mib-03.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: August 3, 2012 Naval Research Laboratory Expires: May 4, 2013 Naval Research Laboratory
A. Bierman A. Bierman
Brocade YumaWorks, Inc.
January 31, 2012 November 05, 2012
Definition of Managed Objects for Performance Reporting Definition of Managed Objects for Performance Reporting
draft-ietf-manet-report-mib-02 draft-ietf-manet-report-mib-03
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 counter and
gauge objects for performance monitoring. This allows a management gauge objects for performance monitoring. This allows a management
station to instruct a device to build off-line reports to be station to instruct a device to build off-line reports to be
collected asynchronously by the management station. Further, this collected asynchronously by the management station. Further, this
skipping to change at page 1, line 46 skipping to change at page 1, line 46
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 August 3, 2012. This Internet-Draft will expire on May 4, 2013.
Copyright Notice Copyright Notice
Copyright (c) 2012 IETF Trust and the persons identified as the Copyright (c) 2012 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
skipping to change at page 2, line 29 skipping to change at page 2, line 29
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. REPORT-SAMPLED-MIB Management Model . . . . . . . . . . . 4
4.2. Terms . . . . . . . . . . . . . . . . . . . . . . . . . . 6 4.2. Terms . . . . . . . . . . . . . . . . . . . . . . . . . . 6
5. Structure of the MIB Module . . . . . . . . . . . . . . . . . 6 5. Structure of the MIB Module . . . . . . . . . . . . . . . . . 6
5.1. Textual Conventions . . . . . . . . . . . . . . . . . . . 6 5.1. Textual Conventions . . . . . . . . . . . . . . . . . . . 6
5.2. The Sampled Group . . . . . . . . . . . . . . . . . . . . 7 5.2. The Sampled Group . . . . . . . . . . . . . . . . . . . . 7
5.3. The Notifications Group . . . . . . . . . . . . . . . . . 7 5.3. The Notifications Group . . . . . . . . . . . . . . . . . 7
6. Relationship to Other MIB Modules . . . . . . . . . . . . . . 7 5.4. Tables and Indexing . . . . . . . . . . . . . . . . . . . 7
6.1. Relationship to the SNMPv2-MIB . . . . . . . . . . . . . . 7 6. Relationship to Other MIB Modules . . . . . . . . . . . . . . 8
6.2. Relationship to the RMON2-MIB . . . . . . . . . . . . . . 8 6.1. Relationship to the SNMPv2-MIB . . . . . . . . . . . . . . 9
6.3. MIB modules required for IMPORTS . . . . . . . . . . . . . 8 6.2. Relationship to the RMON2-MIB . . . . . . . . . . . . . . 9
7. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 8 6.3. MIB modules required for IMPORTS . . . . . . . . . . . . . 9
8. Security Considerations . . . . . . . . . . . . . . . . . . . 19 7. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 9
9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 22 8. Security Considerations . . . . . . . . . . . . . . . . . . . 21
10. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 22 9. Applicability Statement . . . . . . . . . . . . . . . . . . . 24
11. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 22 10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 25
12. References . . . . . . . . . . . . . . . . . . . . . . . . . . 22 11. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 25
12.1. Normative References . . . . . . . . . . . . . . . . . . . 22 12. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 25
12.2. Informative References . . . . . . . . . . . . . . . . . . 23 13. References . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Appendix A. Change Log . . . . . . . . . . . . . . . . . . . . . 23 13.1. Normative References . . . . . . . . . . . . . . . . . . . 25
Appendix B. Open Issues . . . . . . . . . . . . . . . . . . . . . 25 13.2. Informative References . . . . . . . . . . . . . . . . . . 26
Appendix C. . . . . . . . . . . . . . . . . . . . . . . . . . . 26 Appendix A. Change Log . . . . . . . . . . . . . . . . . . . . . 26
Appendix B. Open Issues . . . . . . . . . . . . . . . . . . . . . 28
Appendix C. . . . . . . . . . . . . . . . . . . . . . . . . . . 28
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 REPORT-
SAMPLED-MIB allows for the report generation to occur on the same SAMPLED-MIB allows for the report generation to occur on the same
skipping to change at page 7, line 37 skipping to change at page 7, line 37
supported within the REPORT-SAMPLED-MIB and their intended purpose or supported within the REPORT-SAMPLED-MIB and their intended purpose or
utility. The single notification defined within this MIB module is utility. The single notification defined within this MIB module is
the 'reportSampledNewDataReport'. This notification is sent by the the 'reportSampledNewDataReport'. This notification is sent by the
agent upon completion of a given report on the device. The agent upon completion of a given report on the device. The
notification contains the following objects: notification contains the following objects:
'usrHistoryControlOwner', the entity that configured this report 'usrHistoryControlOwner', the entity that configured this report
entry, and the 'reportSampledReportIndex', the index of the data entry, and the 'reportSampledReportIndex', the index of the data
table for this report. Collectively, these objects allow the table for this report. Collectively, these objects allow the
management application to pull the completed report from the agent. management application to pull the completed report from the agent.
5.4. Tables and Indexing
The REPORT-SAMPLED-MIB module contains a number of tables which
record data related to:
o the control and generation of remote performance reports,
o the storage of remote performance reports, and
o the notification of remote report completion.
The REPORT-SAMPLED-MIB module's tables are indexed via the following
constructs:
o usrHistoryControlIndex - from the RMON2-MIB [RFC2021], an index
that uniquely identifies an entry in the usrHistoryControlTable.
Each such entry defines a set of samples at a particular interval
for a specified set of MIB instances available from the managed
system.
o usrHistoryObjectIndex - from the RMON2-MIB, an index used to
uniquely identify an entry in the usrHistoryObject table from the
RMON2-MIB. Each such entry defines a MIB instance to be collected
periodically.
o reportSampledReportIndex - an index that uniquely identifies the
particular report an entry is associated with among the set of
reports requested through the reportSampledControlNumber in the
reportSampledControlEntry.
o reportSampledSampleIndex - an index that uniquely identifies the
particular sample this entry represents among all samples
associated with the same reportSampledControlEntry.
These tables and their indexing are:
o reportSampledControlTable - this table contains a list of data-
collection configuration entries defining aspects of the reports.
These include, e.g., number of reports, their start and stop
times, etc. This table 'AUGMENTS { usrHistoryControlEntry }'.
o reportSampledObjectTable - this table contains a list of data-
collection configuration entries which identify specific MIB
entries on other devices to monitor. This table 'AUGMENTS {
usrHistoryObjectEntry }'.
o reportSampledTable - this table contains a list of historical
samples collected for the report. This table has 'INDEX {
usrHistoryControlIndex, reportSampledReportIndex,
reportSampledSampleIndex, usrHistoryObjectIndex }'.
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
skipping to change at page 9, line 19 skipping to change at page 10, line 26
-- usrHistoryControlBucketsGranted, usrHistoryControlInterval, -- usrHistoryControlBucketsGranted, usrHistoryControlInterval,
-- usrHistoryControlStatus, -- usrHistoryControlStatus,
-- usrHistoryObjectVariable, usrHistoryObjectSampleType -- usrHistoryObjectVariable, usrHistoryObjectSampleType
FROM RMON2-MIB -- [RFC2021] FROM RMON2-MIB -- [RFC2021]
InetAddress, InetAddressType InetAddress, InetAddressType
FROM INET-ADDRESS-MIB -- [RFC4001] FROM INET-ADDRESS-MIB -- [RFC4001]
; ;
reportSampledMIB MODULE-IDENTITY reportSampledMIB MODULE-IDENTITY
LAST-UPDATED "201201311300Z" -- January 31, 2012 LAST-UPDATED "201211051300Z" -- November 05, 2012
ORGANIZATION "IETF MANET Working Group" ORGANIZATION "IETF MANET Working Group"
CONTACT-INFO CONTACT-INFO
"WG E-Mail: manet@ietf.org "WG E-Mail: manet@ietf.org
WG Chairs: ian.chakeres@gmail.com WG Chairs: sratliff@cisco.com
jmacker@nrl.navy.mil jmacker@nrl.navy.mil
Editors: Robert G. Cole Editors: Robert G. Cole
US Army CERDEC US Army CERDEC
6010 Frankford Road 6010 Frankford Road
Aberdeen Proving Ground, MD 21005 Aberdeen Proving Ground, MD 21005
USA USA
+1 443 395-8744 +1 443 395-8744
robert.g.cole@us.army.mil robert.g.cole@us.army.mil
Joseph Macker Joseph Macker
Naval Research Laboratory Naval Research Laboratory
Washington, D.C. 20375 Washington, D.C. 20375
USA USA
macker@itd.nrl.navy.mil macker@itd.nrl.navy.mil
Andy Bierman Andy Bierman
Brocade YumaWorks, Inc.
andy.bierman@brocade.com" andy@yumaworks.com"
DESCRIPTION DESCRIPTION
"This MIB module contains managed object definitions for "This MIB module contains managed object definitions for
the autonmous reporting of performance object counters. the autonmous reporting of performance object counters.
Copyright (C) The IETF Trust (2009). This version Copyright (C) The IETF Trust (2009). This version
of this MIB module is part of RFC xxxx; see the RFC of this MIB module is part of RFC xxxx; see the RFC
itself for full legal notices." itself for full legal notices."
-- Revision History -- Revision History
REVISION "201211051300Z" -- November 05, 2012
DESCRIPTION
"The seventh draft of this MIB module published as
draft-ietf-manet-report-mib-03.txt.
Revisions to this draft include
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 REVISION "201201311300Z" -- January 31, 2012
DESCRIPTION DESCRIPTION
"The sixth draft of this MIB module published as "The sixth draft of this MIB module published as
draft-ietf-manet-report-mib-02.txt. draft-ietf-manet-report-mib-02.txt.
Revisions to this draft include Revisions to this draft include
a) Pulled the statistical and historical reporting a) Pulled the statistical and historical reporting
from the MIB module and left only the sampled from the MIB module and left only the sampled
reporting, in order to greatly simplify the reporting, in order to greatly simplify the
first instance of this reporting MIB module. first instance of this reporting MIB module.
b) Renamed the module, the REPORT-SAMPLED-MIB b) Renamed the module, the REPORT-SAMPLED-MIB
module. module.
c) Leveraged the RMON2-MIB module more effectively c) Leveraged the RMON2-MIB module more effectively
through the use of the AUGMENTS clause. through the use of the AUGMENTS clause.
d) Changed the module to 'experimental'. d) Changed the module to 'experimental'."
"
REVISION "201102171300Z" -- February 17, 2011 REVISION "201102171300Z" -- February 17, 2011
DESCRIPTION DESCRIPTION
"The fifth draft of this MIB module published as "The fifth draft of this MIB module published as
draft-ietf-manet-report-mib-01.txt. This document draft-ietf-manet-report-mib-01.txt. This document
has been promoted to a MANET Working Group has been promoted to a MANET Working Group
draft. draft.
Revisions to this draft include Revisions to this draft include
a) Proposed changes to the statsReport table to a) Proposed changes to the statsReport table to
simplify communications between device and simplify communications between device and
mgmt application, mgmt application,
b) Added Notifications, b) Added Notifications,
c) Changed the reporting structure of the c) Changed the reporting structure of the
Sampled and the History reporting Sampled and the History reporting
to align with the structure of the to align with the structure of the
Statistics reports for the purpose of Statistics reports for the purpose of
allowing for efficient notification and allowing for efficient notification and
collection of data reports. collection of data reports.
d) Ran through smilint to clean up all errors d) Ran through smilint to clean up all errors
and most warning. A few still remain. and most warning. A few still remain."
"
REVISION "201007051300Z" -- July 05, 2010 REVISION "201007051300Z" -- July 05, 2010
DESCRIPTION DESCRIPTION
"The fourth draft of this MIB module published as "The fourth draft of this MIB module published as
draft-ietf-manet-report-mib-00.txt. This document draft-ietf-manet-report-mib-00.txt. This document
has been promoted to a MANET Working Group has been promoted to a MANET Working Group
draft. draft.
Significant revisions to this draft include Significant revisions to this draft include
a) added support for proxy configurations through a) added support for proxy configurations through
the addition of address objects associated with the addition of address objects associated with
skipping to change at page 12, line 4 skipping to change at page 13, line 18
::= { reportSampledMIB 0 } ::= { reportSampledMIB 0 }
reportSampledMIBObjects OBJECT IDENTIFIER reportSampledMIBObjects OBJECT IDENTIFIER
::= { reportSampledMIB 1 } ::= { reportSampledMIB 1 }
reportSampledMIBConformance OBJECT IDENTIFIER reportSampledMIBConformance OBJECT IDENTIFIER
::= { reportSampledMIB 2 } ::= { reportSampledMIB 2 }
reportSampledGroup OBJECT IDENTIFIER reportSampledGroup OBJECT IDENTIFIER
::= { reportSampledMIBObjects 1 } ::= { reportSampledMIBObjects 1 }
-- Then, the reportSampledGroup assignments are : -- Then, the reportSampledGroup assignments are :
-- reportSampledControlTable - 1 -- reportSampledControlTable - 1
-- reportSampledObjectTable - 2 -- reportSampledObjectTable - 2
-- reportSampledDataTable - 3 -- reportSampledDataTable - 3
reportSampledControlTable OBJECT-TYPE reportSampledControlTable OBJECT-TYPE
SYNTAX SEQUENCE OF SampledControlEntry SYNTAX SEQUENCE OF SampledControlEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A list of data-collection configuration entries." "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 } ::= { reportSampledGroup 1 }
reportSampledControlEntry OBJECT-TYPE reportSampledControlEntry OBJECT-TYPE
SYNTAX SampledControlEntry SYNTAX SampledControlEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A list of parameters that set up a group of user-defined "A list of parameters that set up a group of user-defined
MIB objects to be sampled periodically (called a MIB objects to be sampled periodically (called a
bucket-group). bucket-group).
skipping to change at page 13, line 22 skipping to change at page 14, line 43
reportSampledControlRequestedNumber + 1." reportSampledControlRequestedNumber + 1."
::= { reportSampledControlEntry 2 } ::= { reportSampledControlEntry 2 }
-- Object table -- Object table
reportSampledObjectTable OBJECT-TYPE reportSampledObjectTable OBJECT-TYPE
SYNTAX SEQUENCE OF SampledObjectEntry SYNTAX SEQUENCE OF SampledObjectEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A list of data-collection configuration entries." "A list of data-collection configuration entries.
This table augments the 'usrHistoryObjectTable'
from the RMON2-MIB (RFC 2021)."
REFERENCE
"RFC 2021 - Remote Network Monitoring Management
Information Base Version 2 (RMON2-MIB),
Waldbusser, S., January 1997."
::= { reportSampledGroup 2 } ::= { reportSampledGroup 2 }
reportSampledObjectEntry OBJECT-TYPE reportSampledObjectEntry OBJECT-TYPE
SYNTAX SampledObjectEntry SYNTAX SampledObjectEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A list of MIB instances to be sampled periodically. "A list of MIB instances to be sampled periodically.
Entries in this table are created when an associated Entries in this table are created when an associated
skipping to change at page 14, line 11 skipping to change at page 15, line 38
reportSampledObjectIpAddrType OBJECT-TYPE reportSampledObjectIpAddrType OBJECT-TYPE
SYNTAX InetAddressType SYNTAX InetAddressType
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This identifies the IP address type "This identifies the IP address type
of the IP address associated with the of the IP address associated with the
secondary counter object to be secondary counter object to be
monitored within this report. monitored within this report.
Only the values ipv4(1) and
ipv6(2) are supported.
This object may not be modified if the associated This object may not be modified if the associated
reportStatsControlStatus object is equal to active(1)." reportStatsControlStatus object is equal to active(1)."
::= { reportSampledObjectEntry 1 } ::= { reportSampledObjectEntry 1 }
reportSampledObjectIPAddress OBJECT-TYPE reportSampledObjectIPAddress OBJECT-TYPE
SYNTAX InetAddress SYNTAX InetAddress (SIZE(4|16))
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This identifies the IP addree of the "This identifies the IP addree of the
secondary counter object to be secondary counter object to be
monitored within this report. monitored within this report.
This object may not be modified if the associated This object may not be modified if the associated
reportStatsControlStatus object is equal to active(1)." reportStatsControlStatus object is equal to active(1)."
::= { reportSampledObjectEntry 2 } ::= { reportSampledObjectEntry 2 }
skipping to change at page 14, line 46 skipping to change at page 16, line 27
reportSampledEntry OBJECT-TYPE reportSampledEntry OBJECT-TYPE
SYNTAX SampledEntry SYNTAX SampledEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A historical sample of user-defined variables. This sample "A historical sample of user-defined variables. This sample
is associated with the reportSampledControlEntry which set is associated with the reportSampledControlEntry which set
up the parameters for a regular collection of these samples. up the parameters for a regular collection of these samples.
The usrHistoryControlIndex value in the index identifies The usrHistoryControlIndex value, from the RMON2-MIB
the reportSampledControlEntry on whose behalf this entry (RFC 2021), in the index identifies the
reportSampledControlEntry on whose behalf this entry
was created. was created.
The usrHistoryObjectIndex value in the index identifies The usrHistoryObjectIndex value in the index identifies
the reportSampledObjectEntry on whose behalf this entry the reportSampledObjectEntry on whose behalf this entry
was created. was created.
For example, an instance of reportSampledAbsValue, which For example, an instance of reportSampledAbsValue, which
represents the 14th sample of a variable collected as represents the 14th sample of a variable collected as
specified by reportSampledControlEntry.1 and specified by reportSampledControlEntry.1 and
reportSampledObjectEntry.1.5, would be named reportSampledObjectEntry.1.5, would be named
reportSampledAbsValue.1.14.5" reportSampledAbsValue.1.14.5"
REFERENCE
"RFC 2021 - Remote Network Monitoring Management
Information Base Version 2 (RMON2-MIB),
Waldbusser, S., January 1997."
INDEX { usrHistoryControlIndex, reportSampledReportIndex, INDEX { usrHistoryControlIndex, reportSampledReportIndex,
reportSampledSampleIndex, usrHistoryObjectIndex } reportSampledSampleIndex, usrHistoryObjectIndex }
::= { reportSampledTable 1 } ::= { reportSampledTable 1 }
SampledEntry ::= SEQUENCE { SampledEntry ::= SEQUENCE {
reportSampledReportIndex Integer32, reportSampledReportIndex Integer32,
reportSampledReportID Integer32,
reportSampledSampleIndex Integer32, reportSampledSampleIndex Integer32,
reportSampledIntervalStart TimeStamp, reportSampledIntervalStart TimeStamp,
reportSampledIntervalEnd TimeStamp, reportSampledIntervalEnd TimeStamp,
reportSampledAbsValue Gauge32, reportSampledAbsValue Gauge32,
reportSampledValStatus INTEGER reportSampledValStatus INTEGER
} }
reportSampledReportIndex OBJECT-TYPE reportSampledReportIndex OBJECT-TYPE
SYNTAX Integer32 (1..127) SYNTAX Integer32 (1..127)
MAX-ACCESS read-only MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An index that uniquely identifies the particular report "An index that uniquely identifies the particular report
this entry is associated with among the set of reports this entry is associated with among the set of reports
requested through the reportSampledControlNumber in the requested through the reportSampledControlNumber in the
reportSampledControlEntry. This index starts at 1 and reportSampledControlEntry. This index starts at 1 and
increases by one as each new report is generated." increases by one as each new report is generated."
::= { reportSampledEntry 1 } ::= { reportSampledEntry 1 }
reportSampledReportID OBJECT-TYPE
SYNTAX Integer32 (1..127)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"An ID that uniquely identifies the particular report
this entry is associated with among the set of reports
requested through the reportSampledControlNumber in the
reportSampledControlEntry. This ID is set to equal the
value of the reportSampledReportIndex."
::= { reportSampledEntry 2 }
reportSampledSampleIndex OBJECT-TYPE reportSampledSampleIndex OBJECT-TYPE
SYNTAX Integer32 (1..2147483647) 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 sample this "An index that uniquely identifies the particular sample this
entry represents among all samples associated with the same entry represents among all samples associated with the same
reportSampledControlEntry. This index starts at 1 and reportSampledControlEntry. This index starts at 1 and
increases by one as each new sample is taken." increases by one as each new sample is taken."
::= { reportSampledEntry 2 } ::= { reportSampledEntry 3 }
reportSampledIntervalStart OBJECT-TYPE reportSampledIntervalStart OBJECT-TYPE
SYNTAX TimeStamp SYNTAX TimeStamp
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The value of sysUpTime at the start of the interval over "The value of sysUpTime at the start of the interval over
which this sample was measured. If the probe keeps track of which this sample was measured. If the probe keeps track of
the time of day, it should start the first sample of the the time of day, it should start the first sample of the
history at a time such that when the next hour of the day history at a time such that when the next hour of the day
begins, a sample is started at that instant. begins, a sample is started at that instant.
Note that following this rule may require the probe to delay Note that following this rule may require the probe to delay
collecting the first sample of the history, as each sample collecting the first sample of the history, as each sample
must be of the same interval. Also note that the sample which must be of the same interval. Also note that the sample which
is currently being collected is not accessible in this table is currently being collected is not accessible in this table
until the end of its interval." until the end of its interval."
::= { reportSampledEntry 3 } ::= { reportSampledEntry 4 }
reportSampledIntervalEnd OBJECT-TYPE reportSampledIntervalEnd OBJECT-TYPE
SYNTAX TimeStamp SYNTAX TimeStamp
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The value of sysUpTime at the end of the interval over which "The value of sysUpTime at the end of the interval over which
this sample was measured." this sample was measured."
::= { reportSampledEntry 4 } ::= { reportSampledEntry 5 }
reportSampledAbsValue OBJECT-TYPE reportSampledAbsValue OBJECT-TYPE
SYNTAX Gauge32 SYNTAX Gauge32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The absolute value (i.e. unsigned value) of the "The absolute value (i.e. unsigned value) of the
user-specified statistic during the last sampling period. The user-specified statistic during the last sampling period. The
value during the current sampling period is not made available value during the current sampling period is not made available
until the period is completed. until the period is completed.
To obtain the true value for this sampling interval, the To obtain the true value for this sampling interval, the
associated instance of reportSampledValStatus must associated instance of reportSampledValStatus must
be checked, and reportSampledAbsValue adjusted as necessary. be checked, and reportSampledAbsValue adjusted as necessary.
If the MIB instance could not be accessed during the sampling If the MIB instance could not be accessed during the sampling
interval, then this object will have a value of zero and the interval, then this object will have a value of zero and the
associated instance of reportSampledValStatus will be set to associated instance of reportSampledValStatus will be set to
'valueNotAvailable(1)'." 'valueNotAvailable(1)'."
::= { reportSampledEntry 5 } ::= { reportSampledEntry 6 }
reportSampledValStatus OBJECT-TYPE reportSampledValStatus OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
valueNotAvailable(1), valueNotAvailable(1),
valuePositive(2), valuePositive(2),
valueNegative(3) valueNegative(3)
} }
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
skipping to change at page 17, line 23 skipping to change at page 19, line 21
interval, then 'valueNotAvailable(1)' will be returned. interval, then 'valueNotAvailable(1)' will be returned.
If the sample is valid and actual value of the sample is If the sample is valid and actual value of the sample is
greater than or equal to zero then 'valuePositive(2)' is greater than or equal to zero then 'valuePositive(2)' is
returned. returned.
If the sample is valid and the actual value of the sample is If the sample is valid and the actual value of the sample is
less than zero, 'valueNegative(3)' will be returned. The less than zero, 'valueNegative(3)' will be returned. The
associated instance of reportSampledAbsValue should be associated instance of reportSampledAbsValue should be
multiplied by -1 to obtain the true sample value." multiplied by -1 to obtain the true sample value."
::= { reportSampledEntry 6 } ::= { reportSampledEntry 7 }
-- --
-- Notifications -- Notifications
-- --
reportSampledNotificationObjects OBJECT IDENTIFIER reportSampledNotificationObjects OBJECT IDENTIFIER
::= {reportSampledMIBNotifications 1} ::= {reportSampledMIBNotifications 0}
-- reportSampledNotificationObjects -- reportSampledNotificationObjects
reportSampledNewDataReport NOTIFICATION-TYPE reportSampledNewDataReport NOTIFICATION-TYPE
OBJECTS { usrHistoryControlOwner, -- The entity that OBJECTS { usrHistoryControlOwner, -- The entity that
-- configured this entry -- configured this entry
reportSampledReportIndex -- The index of the reportSampledReportID -- The ID of the
-- data table for this report -- data table for this report
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"reportSampledNewDataReport is a notification sent "reportSampledNewDataReport is a notification sent
when a new report is completed from the when a new report is completed from the
reportSampledControlTable. The notification carries reportSampledControlTable. The notification carries
the index from the control table that established the index from the control table that established
this report and the index from the data table that this report and the index from the data table that
holds this report. Indication of the new report holds this report. Indication of the new report
skipping to change at page 18, line 44 skipping to change at page 20, line 42
::= { reportSampledCompliances 2 } ::= { reportSampledCompliances 2 }
-- Units of Conformance -- Units of Conformance
reportSampledLocalGroup OBJECT-GROUP reportSampledLocalGroup OBJECT-GROUP
OBJECTS { OBJECTS {
reportSampledControlRequestedNumber, reportSampledControlRequestedNumber,
reportSampledControlReportNumber, reportSampledControlReportNumber,
reportSampledObjectIpAddrType, reportSampledObjectIpAddrType,
reportSampledObjectIPAddress, reportSampledObjectIPAddress,
reportSampledReportIndex, reportSampledReportID,
reportSampledIntervalStart, reportSampledIntervalStart,
reportSampledIntervalEnd, reportSampledIntervalEnd,
reportSampledAbsValue, reportSampledAbsValue,
reportSampledValStatus reportSampledValStatus
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Set of REPORT state objects implemented "Set of REPORT state objects implemented
in this module." in this module."
::= { reportSampledMIBGroups 1 } ::= { reportSampledMIBGroups 1 }
skipping to change at page 22, line 13 skipping to change at page 24, line 7
authentication and privacy). authentication and privacy).
Further, deployment of SNMP versions prior to SNMPv3 is NOT Further, deployment of SNMP versions prior to SNMPv3 is NOT
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. IANA Considerations 9. Applicability Statement
This document describes objects for configuring parameters of the
remote report generation process on a router or close device. This
MIB module, denoted REPORT-SAMPLED-MIB, also reports performance
information and notifications. The REPORT-SAMPLED-MIB provides for
the remote control, collection and notification of performance
reports on devices. As such, it eliminates the need for periodic
polling for counters from remote management stations as a means for
generating performance reports. This is hoped to greatly reduce
management overhead on the MANET. This sections provides some
examples of how this MIB module can be used in MANET network
deployments. A fuller discussion of MANET network management use
cases and challenges will be provided elsewhere.
In the following, two scenarios are listed where this MIB module is
useful, i.e.,
o For Mobile vehicles with Low Bandwidth Satellite Link to a Fixed
NOC - Here the vehicles carrying the MANET routers carry multiple
wireless interfaces, one of which is a relatively low-bandwidth
on-the-move satellite connection which interconnects a fix NOC to
the nodes of the MANET. Standards-based methods for monitoring
and fault management from the fixed NOC are necessary for this
deployment option. However, to reduce polling overhead over the
low bandwidth communications links, the REPORT-SAMPLED-MIB can be
deployed the remote MANET nodes for the remote generation of
performance reports.
o For Fixed NOC and Mobile Local Manager in Larger Vehicles - for
larger vehicles, a hierarchical network management arrangement is
useful. Centralized network management is performed from a fixed
NOC while local management is performed locally from within the
vehicles. Standards-based methods for configuration, monitoring,
fault and performance management are necessary for this deployment
option.
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 }
10. Contributors 11. Contributors
This MIB document uses the template authored by D. Harrington which This MIB document uses the template authored by D. Harrington which
is based on contributions from the MIB Doctors, especially Juergen is based on contributions from the MIB Doctors, especially Juergen
Schoenwaelder, Dave Perkins, C.M.Heard and Randy Presuhn. Schoenwaelder, Dave Perkins, C.M.Heard and Randy Presuhn.
11. Acknowledgements 12. Acknowledgements
We would like to thank Bert Wijnen for pointing out the existence of We would like to thank Bert Wijnen for pointing out the existence of
the usrHistory group within RMON2 and in answering our numerous the usrHistory group within RMON2 and in answering our numerous
questions on the usrHistory group. Further, we wish to thank U. questions on the usrHistory group. Further, we wish to thank U.
Herberg for promoting additions to this MIB through his thoughtful Herberg for promoting additions to this MIB through his thoughtful
consideration of performance monitoring requirements for other MIBs consideration of performance monitoring requirements for other MIBs
within the MANET WG, e.g., NHDP and OLSR MIBs. within the MANET WG, e.g., NHDP and OLSR MIBs.
12. References 13. References
12.1. Normative References 13.1. Normative References
[RFC2021] Waldbusser, S., "Remote Network Monitoring Management
Information Base Version 2 using SMIv2", RFC 2021,
January 1997.
[RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group [RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group
MIB", RFC 2863, June 2000. MIB", RFC 2863, June 2000.
[RFC3418] Presuhn, R., "Management Information Base (MIB) for the [RFC3418] Presuhn, R., "Management Information Base (MIB) for the
Simple Network Management Protocol (SNMP)", STD 62, Simple Network Management Protocol (SNMP)", STD 62,
RFC 3418, December 2002. 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.
skipping to change at page 23, line 21 skipping to change at page 26, line 17
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. [RFC4001] Daniele, M., Haberman, B., Routhier, S., and J.
Schoenwaelder, "Textual Conventions for Internet Network Schoenwaelder, "Textual Conventions for Internet Network
Addresses", RFC 4001, February 2005. Addresses", RFC 4001, February 2005.
12.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.
[RFC2021] Waldbusser, S., "Remote Network Monitoring Management
Information Base Version 2 using SMIv2", RFC 2021,
January 1997.
Appendix A. Change Log Appendix A. Change Log
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.
skipping to change at page 26, line 40 skipping to change at page 29, line 25
URI: http://www.cs.jhu.edu/~rgcole/ 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
Brocade YumaWorks, Inc.
Redwood City, CA 94065
EMail: andy.bierman@brocade.com EMail: andy@yumaworks.com
 End of changes. 39 change blocks. 
54 lines changed or deleted 185 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/