draft-ietf-ippm-reporting-mib-00.txt   draft-ietf-ippm-reporting-mib-01.txt 
Network Working Group E. Stephan/J. Jewitt Network Working Group E. Stephan/J. Jewitt
Internet Draft France Telecom R&D Internet Draft France Telecom R&D
Document: draft-ietf-ippm-reporting-mib-01.txt November 2002
Document: draft-ietf-ippm-reporting-mib-00.txt June 20, 2002
IPPM reporting MIB IPPM reporting MIB
Status of this Memo Status of this Memo
This document is an Internet-Draft and is in full conformance with This document is an Internet-Draft and is in full conformance with
all provisions of Section 10 of RFC2026 [1]. all provisions of Section 10 of RFC2026 [1].
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that other Task Force (IETF), its areas, and its working groups. Note that other
skipping to change at page 2, line 9 skipping to change at page 2, line 9
designed for use with network management protocols in TCP/IP-based designed for use with network management protocols in TCP/IP-based
internets. internets.
In particular, this MIB specifies the objects used for managing the In particular, this MIB specifies the objects used for managing the
results of the IPPM metrics measures, for pushing alarms, and for results of the IPPM metrics measures, for pushing alarms, and for
reporting the measures results. reporting the measures results.
Table of Contents Table of Contents
1. Introduction................................................3 1. Introduction................................................3
2. The IPPM Framework..........................................3 2. The IPPM Framework..........................................3
3. The SNMP Management Framework...............................3 3. The IPPM Framework..........................................3
4. Overview....................................................5 4. The SNMP Management Framework...............................4
4.1. Textual Conventions.........................................6 5. Overview....................................................6
4.2. Structure of the MIB.......................................10 5.1. Textual Conventions.........................................7
4.3. Row identification in an application namespace.............12 5.2. Structure of the MIB........................................9
5. IPPM-REPORTING-MIB conceptual presentation.................14 5.3. Row identification in an application namespace.............11
5.1. IPPM-REPORTING-MIB diagram.................................14 5.4. Relationship of IPPM MIB tables............................12
5.2. Conceptual programming interface...........................15 6. IPPM-REPORTING-MIB conceptual presentation.................16
5.3. SNMP mapping...............................................15 6.1. IPPM-REPORTING-MIB diagram.................................16
6. Measurement architectures..................................16 6.2. Conceptual programming interface...........................17
6.1. Proxy architecture.........................................16 6.3. SNMP mapping...............................................17
6.2. Reporting architecture.....................................17 7. Measurement architectures..................................18
6.3. Gateway architecture.......................................19 7.1. Proxy architecture.........................................18
6.4. Security...................................................19 7.2. Reporting architecture.....................................19
7. Reporting mode integration with the control and test 7.3. Gateway architecture.......................................21
protocols................................................20 7.4. Security...................................................21
7.1. Integration................................................20 8. Reporting mode integration with the control and test
7.2. Setup of the measure.......................................20 protocols................................................22
7.3. Setup of the measurement report............................21 8.1. Integration................................................22
7.4. Writing the measurement results in the IPPM-REPORTING 8.2. Setup of the measure.......................................22
MIB......................................................21 8.3. Setup of the measurement report............................23
7.5. Report download and upload.................................22 8.4. Writing the measurement results in the IPPM-REPORTING
7.6. Default value..............................................22 MIB......................................................23
8. Definition.................................................22 8.5. Report download and upload.................................24
9. Security Considerations....................................58 8.6. Default value..............................................24
9.1. Privacy....................................................58 9. Definition.................................................25
9.2. Measurement aspects........................................58 10. Security Considerations....................................58
9.3. Management aspects.........................................58 10.1. Privacy.....................................................58
10. References.................................................59 10.2. Measurement aspects.........................................58
11. Acknowledgments............................................61 10.3. Management aspects..........................................59
12. Author's Addresses.........................................61 11. Document management........................................60
11.1. Open issues.................................................60
11.2. changes since release 00....................................60
12. References.................................................61
13. Acknowledgments............................................63
14. Authors Addresses..........................................63
1. Introduction 1. Introduction
This memo defines a MIB for managing measures based upon the IP
This memo defines a MIB for managing the measures using the IP
performance metrics specified by the IPPM Working Group. performance metrics specified by the IPPM Working Group.
It specifies the objects to manage the results of the measure of The definition of objects in the IPPM MIB are built on notions
metrics standardized by IPPM Working Group. They are built on notions
introduced and discussed in the IPPM Framework document, RFC 2330 introduced and discussed in the IPPM Framework document, RFC 2330
[2]. [ii].
This memo defines a Management Information Base (MIB), and as such This memo defines a Management Information Base (MIB), and as such it
it is intended to be respectful of the "Boilerplate for IETF MIBs" is intended to be respectful of the "Boilerplate for IETF MIBs"
defined in http://www.ops.ietf.org/mib-boilerplate.html. defined in http://www.ops.ietf.org/mib-boilerplate.html.
There are companion documents to the IPPM-REPORTING-MIB both in the There are companion documents to the IPPM-REPORTING-MIB both in the
Transport Area (See section 2), and in the Operations and Management Transport Area (See section 2), and in the Operations and Management
Area (See section 3). The reader should be familiar with these Area (See section 3). The reader should be familiar with these
documents. documents.
2. The IPPM Framework 2. The IPPM Framework
The IPPM Framework consists of 3 major components:
A general framework for defining performance metrics, as described in
the Framework for IP Performance Metrics, RFC 2330 [2];
A set of standardized metrics which conform to this framework: The
IPPM Metrics for Measuring Connectivity, RFC 2678 [iii]; The One-way
Delay Metric for IPPM, RFC 2679 [iv]; The One-way Packet Loss Metric
for IPPM, RFC 2680 [v]; The Round-trip Delay Metric for IPPM, RFC
2681 [vi].
Emerging metrics that are being specified in respect of this
framework.
3. The IPPM Framework
The IPPM Framework consists in 3 major components: The IPPM Framework consists in 3 major components:
A general framework for defining performance metrics, described A general framework for defining performance metrics, described
in the Framework for IP Performance Metrics, RFC 2330 [2]; in the Framework for IP Performance Metrics, RFC 2330 [2];
A set of standardized metrics which conform to this framework: A set of standardized metrics which conform to this framework:
The IPPM Metrics for Measuring Connectivity, RFC 2678 [3]; The One- The IPPM Metrics for Measuring Connectivity, RFC 2678 [3]; The One-
way Delay Metric for IPPM, RFC 2679 [4]; The One-way Packet Loss way Delay Metric for IPPM, RFC 2679 [4]; The One-way Packet Loss
Metric for IPPM, RFC 2680 [5]; The Round-trip Delay Metric for IPPM, Metric for IPPM, RFC 2680 [5]; The Round-trip Delay Metric for IPPM,
RFC 2681 [6]. RFC 2681 [6].
Emerging metrics that are being specified in respect of this Emerging metrics that are being specified in respect of this
framework. framework.
3. The SNMP Management Framework 4. The SNMP Management Framework
The SNMP Management Framework consists of five major components: The SNMP Management Framework consists of five major components:
An overall architecture, described in RFC 2571 [7]. An overall architecture, described in RFC 2571 [7].
Mechanisms for describing and naming objects and events for the Mechanisms for describing and naming objects and events for the
purpose of management. The first version of this Structure of purpose of management. The first version of this Structure of
Management Information (SMI) is called SMIv1 and described in STD 16, Management Information (SMI) is called SMIv1 and described in STD 16,
RFC 1155 [8], STD 16, RFC 1212 [9] and RFC 1215 [10]. The second RFC 1155 [8], STD 16, RFC 1212 [9] and RFC 1215 [10]. The second
version, called SMIv2, is described in STD 58, RFC 2578 [11], STD 58, version, called SMIv2, is described in STD 58, RFC 2578 [11], STD 58,
skipping to change at page 5, line 5 skipping to change at page 6, line 5
the Management Information Base or MIB. Objects in the MIB are the Management Information Base or MIB. Objects in the MIB are
defined using the subset of Abstract Syntax Notation One (ASN.1) defined using the subset of Abstract Syntax Notation One (ASN.1)
defined in the SMI. In particular, each object type is named by an defined in the SMI. In particular, each object type is named by an
OBJECT IDENTIFIER, an administratively assigned name. OBJECT IDENTIFIER, an administratively assigned name.
The object type together with an object instance serves to uniquely The object type together with an object instance serves to uniquely
identify a specific instantiation of the object. For human identify a specific instantiation of the object. For human
convenience, we often use a textual string, termed the descriptor, to convenience, we often use a textual string, termed the descriptor, to
refer to the object type. refer to the object type.
4. Overview 5. Overview
Although the number of measurement devices that implement IPPM Although the number of measurement devices that implement IPPM
metrics is growing, there is not currently any standardized metrics is growing, there is not currently any standardized
management interface to manage remotely the results of these metrics. management interface to manage remotely the measurement of these
This memo defines a Management Information Base for managing the metrics. This memo defines a Management Information Base for managing
results of the measures of IPPM metrics. the measurement of IPPM metrics.
To permit metrics to be referenced by other MIBs and other protocols, To permit metrics to be referenced by other MIBs and other protocols,
the IPPM WG has defined a registry of the current metrics and a the IPPM WG has defined a registry of the current metrics and a
framework for the integration of future metrics in [IPPM metrics framework for the integration of future metrics in the [IPPM metrics
registry]. registry].
As the specification of new metrics is a continuous process, this As the specification of new metrics is a continuous process, this
memo defines a framework for the integration of the future memo defines a framework for the integration of the future
standardized metrics. To address future needs Specialized tables may standardized metrics. To address future needs specialized tables may
be created, while augmenting the definition of the ippmMeasureTable. be created, while augmenting the definition of the ippmMeasureTable.
The MIB architecture is inspired by the RMON model [23],[24] which The MIB architecture is inspired by the RMON model [xxiii],[xxiv]
specifies the MIB for the monitoring of a single point of measure. which specifies the MIB for the monitoring of a single point of
The IPPM-REPORTING-MIB differs from this model in that IPPM metrics measure. The IPPM-REPORTING-MIB differs from this model in that IPPM
measurement involves several points of measures and requires common metrics measurement involves several points of measure and requires
references for time and for measure identification. The IPPM- common references for time and for measure identification. The IPPM-
REPORTING-MIB defines an absolute timeFilter. REPORTING-MIB defines an absolute timeFilter.
The IPPM-REPORTING-MIB introduces a framework where each application The IPPM-REPORTING-MIB introduces a framework where each application
identifies its measures in an owner namespace. Using the namespace identifies its measures in an owner namespace. Using the namespace
framework, an application may grant other owners access to its framework, an application may grant other owners access to its
measure results for aggregated metrics computation, reporting, or measurement results for aggregated metrics computation, reporting, or
alarming. alarming.
Different architectures may be used to perform metric measurements, Different architectures may be used to perform metric measurements,
using a control protocol and a test protocol. Different control using a control protocol and a test protocol. Different control
frameworks are suitable for performing a measure. The memo lists frameworks are suitable for performing measurements. The memo lists
them, while also looking for a way to integrate them with the IPPM- them, while also looking for a way to integrate them with the IPPM-
REPORTING-MIB . This section is informational, but helps to specify REPORTING-MIB. This section is for informational purposes only, and
the relationship among the test protocol, the control protocol and is intended to help to specify the relationship among the test
IPPM-REPORTING-MIB. protocol, the control protocol and IPPM-REPORTING-MIB.
Special care has been taken to provide a reporting mode suitable for Special care has been taken to provide a reporting mode suitable for
control protocol and test protocol. It addresses the need to provide control protocols and test protocols. It addresses the need to
access to results for the applications. Moreover, it may be used to provide access to results for the applications. Moreover, it may be
reduce the number of control frameworks. used to reduce the number of control frameworks.
This MIB is intended to handle multiple concurrent access by SNMP
applications. They are not in constant contact with the measurement
devices. For this reason, this MIB allows continuous measures
collection and statistics computation.
The objects defined in this document are not intended for direct This MIB is intended to handle multiple concurrent sessions by SNMP
manipulation.. applications. However, the SNMP requests are not necessarily to be
handled explicitly by the measurement devices, but can be sent to
middleware performing an aggregation function. This allows for
continuous collection of measurements and statistics computation.
4.1. Textual Conventions 5.1. Textual Conventions
Five types of data are introduced as a textual convention in this Four types of data are introduced as a textual convention in this
MIB document: TypeP,GMTDateAndTime, GmtTimeFilter, document: TypeP, GMTTimeStamp, IppmStandardMetrics and
IppmReportDefinition and IppmStandardMetrics. IppmReportDefinition.
4.1.1. Packet of type P 5.1.1. Packet of type P
Section 13 of the IPPM framework [2] introduces the generic notion of Section 13 of the IPPM framework [2] introduces the generic notion of
a "packet of type P" because in some contexts the metric's value a "packet of type P" because in some contexts the metric's value
depends on the type of the packets involved in the metric. In the depends on the type of the packets involved in the metric. In the
definition of a metric, the type P will be explicitly defined, definition of a metric, the type P will be explicitly defined,
partially defined, or left generic. Measurement of metrics defined partially defined, or left generic. Measurement of metrics defined
with generic type P are made specific when performing actual with generic type P are made specific when performing actual
measurements. This naming convention serves as an important reminder measurements. This naming convention serves as an important reminder
that one must be conscious of the exact type of traffic being that one must be conscious of the exact type of traffic being
measured. measured.
The standardization of the management of the IPPM measures relies on The standardization of the management of the IPPM measures relies on
the capability to configure finely and unambiguously the type P of the capability to finely and unambiguously configure the type P of
the packets, and the parameters of the protocol suites of the type P. the packets, and the parameters of the protocol suites of the type P.
RMON2 introduced the concept of protocol identifiers. The RFC2895 RMON2 introduced the concept of protocol identifiers. RFC2895 [xxv]
[25] specifies a macro for the definition of protocol identifier. The specifies a macro for the definition of protocol identifier. The
RFC2896 [26] defines the protocol identifiers for different protocol RFC2896 [xxvi] defines the protocol identifiers for different
encapsulation trees. protocol encapsulation trees.
The type P implementation relies on the MACRO PROTOCOL-IDENTIFIER The type P implementation relies on the MACRO PROTOCOL-IDENTIFIER
defined for identifying protocol suites in RMON2. It is achieved by defined for identifying protocol suites in RMON2. It is achieved by
defining the TypeP as a new syntax in SMIv2 TEXTUAL-CONVENTION. defining the TypeP as a new syntax in SMIv2 TEXTUAL-CONVENTION.
4.1.1.1. Internet addresses 5.1.1.1. Internet addresses
The section 14 of the IPPM framework defines (for the usual case of a The section 14 of the IPPM framework defines (for the usual case of a
unidirectional path through the Internet) the term "Src" and "Dst". unidirectional path through the Internet) the term "Src" and "Dst".
"Src" denotes the IP address of the beginning of the path, and "Dst" "Src" denotes the IP address of the beginning of the path, and "Dst"
denotes the IP address of the end. denotes the IP address of the end.
The section 3 of the RMON PI Reference specifies the Protocol The section 3 of the RMON PI Reference specifies the Protocol
Identifier Encoding rules which consists briefly in a recursive Identifier Encoding rules which consists briefly in a recursive
length value format. "Src" and "Dst" are protocol identifier length value format. "Src" and "Dst" are protocol identifier
parameters. Their values are encoded in separated fields using the parameters. Their values are encoded in separated fields using the
protocol identifier encoding rule, but without trailing parameters. protocol identifier encoding rule, but without trailing parameters.
The packet encapsulation defined in an instance of TypeP embeds the The packet encapsulation defined in an instance of TypeP embeds the
format of "Src" and "Dst" and their values. These addresses type and format of "Src" and "Dst" and their values. The type and value of
value depend on the type P of the packet, IP version 4, V6, IP in these addresses depend on the type P of the packet, IP version 4, V6,
IP... Both participate to the completion of the packet encoding. IP in IP... Both participate in the completion of the packet
encoding.
Examples: Examples:
RFC2896 defines the protocol identifiers ip and ipip4. Should there RFC2896 defines the protocol identifiers ip and ipip4. Should there
be an Internet tunnel end-point of the IP address 192.168.1.1 in the be an Internet tunnel end-point of the IP address 192.168.1.1 in the
tunnel 128.2.6.7. The TypeP of the source address of the tunnel, Src, tunnel 128.2.6.7. the TypeP of the source address of the tunnel, Src,
is 8.0.0.8.0.0.0.0.17.2.0.0 (ip.ipip4). The trailer 2.0.0 in the is 8.0.0.8.0.0.0.0.17.2.0.0 (ip.ipip4). The trailer 2.0.0 in the
TypeP indicates that there are 2 parameters. In the IPPM context TypeP indicates that there are 2 parameters. In the IPPM context
these 2 parameters are provided in Src, which has the value these 2 parameters are provided in Src, which has the value
10.4.192.168.1.1.4.128.2.6.7. 10.4.192.168.1.1.4.128.2.6.7.
4.1.2. GMTDateAndTime 5.1.2. GMTTimeStamp
This textual convention defines the date and time, and is represented
by the following format: year, month, day, hour, minutes, seconds,
fractions of second.
The first part is human readable. The fields year, month, day, hour,
minutes are seconds are printable characters.
The last field is the fraction of second. The fraction step is 250
picoseconds.
or example, 50 ms is 200000000 times 250 picosecond which correspond to
0BEBC200'H. 0001000201090200010501000BEBC200 represent 8:15pm, 10
econds and 50 ms GMT on 19 February 2001 and is displayed as 01-02-
9,20:15:10, 200000000.
4.1.3. GmtTimeFilter
GmtTimeFilter uses an absolute reference of time, and is intended to be
used for the index of a table. It allows an application to download only
those rows changed since a particular time. A row is considered changed
if the value of any object in the row changes, or if the row is created
or deleted.
Each new conceptual row will be associated with the timeMark instance
that was created at the value of ippmTimeSysTimer.
It is intended to provide an absolute timestamp index for the results of
measures. Typically for each singleton produced by an IPPM measure is
associated the timemark corresponding to the moment of the measure.
Illustrations:
Consider the 2 tables measureTable and resultTable
measureTable OBJECT-TYPE
SYNTAX SEQUENCE OF MeasureEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION ''
::= { fooMib 1 }
INDEX { measureIndex }
resultTable OBJECT-TYPE
SYNTAX SEQUENCE OF ResultEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION ''
::= { fooMib 2 }
INDEX { measureIndex, resultTimeMark }
ResultEntry {
resultTimeMark TimeFilter,
resultCounts Counter
}
LetÆs assume there are two measure rows in the measure table
(measureIndex == 1, measureIndex == 2) which produced results
asynchronously (e.g. made at Poisson intervals or sibling) and logged
them in the result table.
LetÆs also assume that Measure 1 produced the result 34 at time
0001000201090200010501000BEBC200 GMT, while Measure 2 produced the value
54 10ms later at time 0001000201090200010501000E4E1C00 GMT, and that
both rows are updated on several later occasions such that the current
values are 37 and 53 respectively.
Then the following resultCounts instances would exist:
resultCounts.1.0001000201090200010501000BEBC200 34
resultCounts.2.0001000201090200010501000E4E1C00 54
resultCounts.1.00010002010902000105010016A65700 65
resultCounts.1.0001000201090200010501000E4E1C00 57
resultCounts.2.0001000201090200010501001312D000 48
resultCounts.2.0001000201090200010501001443FD00 53
resultCounts.1.00010002010902000105010101312D00 49
resultCounts.1.00010002010902000105010104C4B400 37
The following get-bulk explains how an NMS retrieves the results of the
measures.
get-bulk(nonRptrs=1, maxReps=10, resultCounts.1); This textual convention defines the time at which an event occurred.
returns: It is very similar to the NTP timestamp format except that it
resultCounts.1. 0001000201090200010501000BEBC200 == 34 represents the time elapsed since January 1st, 2000 instead of
resultCounts.1.00010002010902000105010016A65700 == 65 January 1st, 1900.
resultCounts.1.0001000201090200010501000E4E1C00 == 57
resultCounts.1.00010002010902000105010101312D00 == 49
resultCounts.1.00010002010902000105010104C4B400 == 37
# return lexigraphically-next two MIB instances
get-bulk(nonRptrs=0, maxReps=2, 5.1.3. IppmStandardMetrics
resultCounts.1.0001000201090200010501000E4E1C00 ,
resultCounts.2.0001000201090200010501000E4E1C00 );
returns:
resultCounts.1.00010002010902000105010016A65700 == 65
resultCounts.2.0001000201090200010501001312D000 == 48
resultCounts.1.0001000201090200010501000E4E1C00 == 57
resultCounts.2.0001000201090200010501001443FD00 == 53
get-bulk(nonRptrs=0, maxReps=2, Each standard metric is identified in the IPPM-METRICS-REGISTRY under
resultCounts.1.00010002010902000105010104C4B400 , the node rfc in a chronological order. To permit several metrics to
resultCounts.2.00010002010902000105010104C4B400 ); be performed in a single measure there is an need to describe in a
returns: bit string the metrics to be performed, granted... This textual
return lexigraphically-next two MIB instances convention defines an octet string that gathered in a bit string a
no 'resultTable' counter values at all are returned because sequence of bits. The bit order corresponds to the order of the
neither counter has been updated since the time metrics identifiers in the registry.
00010002010902000105010104C4B400
4.1.4. Report definition 5.1.4. Report definition
A report consists of sending or logging a subset of results of A report consists of sending, or logging, a subset of results of
measure. The elaboration of the report consists of actions to perform measurements that have been taken over a period of time. The report
on the measurement results. An action is performed either: consists of actions that are taken on the measurement results. An
action is performed either:
+ For each result + For each result
+ On the results corresponding to a measurement cycle + On the results corresponding to a measurement cycle
+ On the results available at the measurement completion. + On the results available at the measurement completion.
To preserve the scalability of the whole measurement system, it To preserve the scalability of the whole measurement system, it
limits: limits:
+ The amount of data sent to the applications + The amount of data sent to the applications
+ The bandwidth consumption for uploading the result + The bandwidth consumption for uploading the result
+ The number of alarms sent to the applications + The number of alarms sent to the applications
+ The amount of data saved in the point of measure + The amount of data saved in the point of measure
The comparison of the measures results in a metric threshold that
The comparison of the measure results in a metric threshold that
identifies particular measure values and times that directly impact identifies particular measure values and times that directly impact
service availability. service availability.
The comparison of the duration of repeated events with a duration The comparison of the duration of repeated events with a duration
threshold identifies particular measure values and times that threshold identifies particular measure values and times that
directly affect an SLA. directly affect an SLA.
The combination of IPPM metric results, threshold events, and event The combination of IPPM metric results, threshold events, and event
filtering provides a very efficient mechanism to report results, filtering provides a very efficient mechanism to report results,
events, and alarms. events, and alarms.
A report is described using the TEXTUAL-CONVENTION A report is described using the TEXTUAL-CONVENTION
IppmReportDefinition. The report setup must not dramatically increase IppmReportDefinition. The report setup must not dramatically increase
the amount of data needed by the control protocol to setup a measure: the amount of data needed by the control protocol to setup a measure:
+ A basic report is defined in the object + A basic report is defined in the object ippmReportSetupDefinition;
ippmReportSetupDefinition; + More elaborate reports are described using a metric threshold to
+ More elaborate reports are described using a metric generate alarms and events.
threshold to generate alarms and events. + Pushing of alarms and reports requires a management station
+ Pushing of alarms and reports requires an NMS address. address to which the data will be sent.
+ SLA alarms are described using an events duration + SLA alarms are described using an events duration threshold.
threshold.
The TEXTUAL-CONVENTION IppmReportDefinition specifies the list of The TEXTUAL-CONVENTION IppmReportDefinition specifies the list of
events and actions that are used to create a report. events and actions that are used to create a report.
4.1.5. IppmStandardMetrics 5.2. Structure of the MIB
The TEXTUAL-CONVENTION IppmStandardMetrics defines the standardized
IPPM metrics.
4.2. Structure of the MIB
The MIB is arranged as follow: The MIB is arranged as follow:
- ippmOwnersGroup - ippmOwnersGroup
- ippmSystemGroup - ippmSystemGroup
- ippmMeasureGroup - ippmMeasureGroup
- ippmHistoryGroup - ippmHistoryGroup
- ippmNetworkMeasureGroup - ippmNetworkMeasureGroup
skipping to change at page 10, line 49 skipping to change at page 9, line 49
- ippmHistoryGroup - ippmHistoryGroup
- ippmNetworkMeasureGroup - ippmNetworkMeasureGroup
- ippmAggregatedMeasureGroup - ippmAggregatedMeasureGroup
- ippmReportGroup - ippmReportGroup
- ippmNotifications - ippmNotifications
4.2.1. The ippmOwners Group 5.2.1. The ippmOwners Group
This group identifies an owner, or group of owners that have access
This group controls access to the probe. to measurements on a probe.
4.2.2. The ippmSystem Group 5.2.2. The ippmSystem Group
This group consists of a set of parameters describing the clock This group consists of a set of parameters describing the clock
synchronization over the time. synchronization at a particular point of measure over time.
This group is Critical to the implementation of the IPPM MIB. This group is critical to the implementation of the IPPM MIB.
Section 6.3. of the IPPM Framework states that Section 6.3. of the IPPM Framework states that
"Those who develop such measurement methodologies should strive to: "Those who develop such measurement methodologies should strive to:
+ Minimize their uncertainties/errors, + Minimize their uncertainties/errors,
+ Understand and document the sources of uncertainty/error, and + Understand and document the sources of uncertainty/error, and
+ Quantify the amounts of uncertainty/error." + Quantify the amounts of uncertainty/error."
The aim of this group is to have these values available to compute The aim of this group is to have these values available to compute
reliable statistics. The implementation of this group is mandatory reliable statistics. The implementation of this group is mandatory,
whether the time synchronization is automatic or not. whether the time synchronization is automatic or not.
4.2.3. The ippmMeasureGroup 5.2.3. The ippmMeasureGroup
This group displays all the measures configured on the measurement This group displays all the measures configured on the measurement
entity. It consists of the ippmMetricsTable, ippmMeasureTable. entity. It consists of the ippmMetricsTable and ippmMeasureTable. The
ippmMeasureTable holds the common part of a measure, while the
specific parameters are handled in the corresponding auxiliary table
(ippmNetworkMeasure, ippmAggregatedMeasureTable...) .
The measurement entity describes in the ippmMetricsTable of the SNMP The measurement entity describes in the ippmMetricsTable of the SNMP
agent the local implementation of the standardized metrics. agent the local implementation of the standardized metrics. All
standardized metrics should be displayed in this table, with the
capability object defining whether the metric is implemented or not.
The control protocol registers a description of the existing measures The control protocol registers a description of the existing measures
in the ippmMeasureTable and in the auxiliary measure tables. in the ippmMeasureTable and in the auxiliary measure tables. The
ippmMeasureTable table is read-create, but only allows for the
ippmMeasureTable holds the common part of a measure, while the creation of "aggregated" measures when defined in conjunction with
specific parameters are handled in the corresponding auxiliary table the ippmAggregatedMeasureTable. Network measures are not allowed to
(ippmNetworkMeasure, ippmAggregatedMeasureTableà) . be created directly by the management entity, and as such the measure
table values for these measures should be display only.
The results of the measures are logged in the ippmHistoryTable. The results of the measurements are logged in the ippmHistoryTable.
4.2.4. The ippmNetworkMeasure Group 5.2.4. The ippmNetworkMeasure Group
The control protocol registers a description of the existing network The control protocol registers a description of the existing network
measures in the ippmNetworkMeasureTable and in the ippmMeasureTable. measures in the ippmNetworkMeasureTable and in the ippmMeasureTable.
This group displays the network measures defined by the control This group displays the network measures defined by the control
protocol. The results are saved in the ippmHistoryTable. protocol. The results are saved in the ippmHistoryTable.
ippmNetworkMeasureTable is an auxiliary table of ippmMeasureTable, ippmNetworkMeasureTable is an auxiliary table of ippmMeasureTable,
and is responsible for the configuration of the network measure. and is responsible for the configuration of the network measure.
4.2.5. The ippmAggregatedMeasure Group 5.2.5. The ippmAggregatedMeasure Group
ippmAggregatedMeasureTable is an auxiliary table of ippmMeasureTable, ippmAggregatedMeasureTable is an auxiliary table of ippmMeasureTable,
and is responsible for the consolidation of the results previously and is responsible for the consolidation of the results previously
measured and saved in the ippmHistoryTable. The aggregated results measured and saved in the ippmHistoryTable. The aggregated results
are saved in the ippmHistoryTable and may be used for higher are saved in the ippmHistoryTable and may be used for higher
aggregated measures. aggregated measures.
4.2.6. The report Group 5.2.6. The Report Group
This group displays the existing reports of the measures. This group displays the existing reports of the measures collected.
ippmReportSetupTable is an auxiliary table of ippmMeasureTable, and ippmReportSetupTable is an auxiliary table of ippmMeasureTable, and
is responsible for the configuration of the reports. is responsible for the configuration of the reports.
The reports are saved in the ippmReportTable, or sent directly to the The reports are saved in the ippmReportTable, or sent directly to the
applications. applications.
4.2.7. The notification Group 5.2.7. The Notification Group
The Notification group specifies a list of valid notifications. They The Notification group specifies a list of valid notifications. They
are used to push alarms or reports to the applications. are used to push alarms or reports to the applications.
4.3. Row identification in an application namespace 5.3. Row identification in an application namespace
The control protocol or the test protocol adds rows in the namespace The control protocol or the test protocol adds rows in the namespace
of the corresponding measure. of the corresponding measure.
An identifier of an instance of an object is defined as a list of An identifier of an instance of an object is defined as a list of
objects in the clause INDEX. An identifier of an instance of an objects in the clause INDEX. An object instance identifier in an
object in an owner namespace is defined as a list of objects in the owner namespace is defined as a list of objects in the clause INDEX
clause INDEX where the first object type is OwnerString. where the first object type is OwnerString.
As the OBJECT IDENTIFIER, which identifies the instance, begins with As the OBJECT IDENTIFIER, which identifies the instance, begins with
the owner value, the remaining value of the index fields may be the owner value, the remaining values of the index fields may be
chosen independently from one namespace to another. chosen independently from one namespace to another.
This allows the user to choose arbitrary values for the remaining This allows the user to choose arbitrary values for the remaining
fields of the INDEX clause without checking that the values of these fields of the INDEX clause without checking that the values of these
fields exist in the MIB tables. This allows the owner to use the same fields exists in the MIB tables. This allows the owner to use the
values across MIB implementations. same values across MIB implementations.
Thus, it avoids polling to determine the next free index. Also, as a Thus, it avoids polling to determine the next free index. Also, as a
consequence, s 2 applications will never find the same free index consequence, two applications will never find the same free index
value. value.
The usage of owner namespace increases the speed of the management The usage of owner namespace increases the speed of the management
operations while reducing bandwidth consumption and CPU load in the operations while reducing bandwidth consumption and CPU load in the
agents and applications. agents and applications.
Measurements are requested by NMS applications. An instance of an Measurements are requested by management applications. An instance of
object managed by an NMS is identified by the NMS OwnerString and the an object managed by a management station is identified by the
private index provided by the NMS. management station OwnerString and the private index provided by the
MS.
As the NMS manages its private range of indices, it simply chooses As the MS manages its private range of indices, it simply chooses one
one when it wishes to create a new control entry. For the same when it wishes to create a new control entry. For the same reason,
reason, the setup of a measure on several points of measures consists the setup of a measure on several points of measures consists of
of simply sending the same copy of the measure setup to the different simply sending the same copy of the measure setup to the different
points of measures involved. points of measures involved.
5. IPPM-REPORTING-MIB conceptual presentation 5.4. Relationship of IPPM MIB tables
5.1. IPPM-REPORTING-MIB diagram There is inherently a relationship between various tables in the IPPM
Mib, and as such, the data integrity must be assured. This
relationship is depicted in the following examples.
5.4.1. Relationship between the Owners Table and the Measure Table
The owners table contains the list of "owners" that can create and
activate remote IPPM measurements in an agent. As the table is
"Read/Create", these users and their associated
"access" rights on metric measurements can be directly configured. It
is recommended to make use of "view based access control" in order to
restrict access to this table. For example, the
master user "acme" may be given "write" privileges on the
ippmOwnersTable, whereas all others are restricted to "read" access.
The user "acme" can then setup the list of other users that have
access to measures.
There must be at least 1 owner in the owners table. This owner may be
either setup by default by the IPPM agent, or configured as stated
above.
An owner may have multiple corresponding entries in the measure
table. Each entry in the measure table must be associated with one,
and only one, entry in the owners table. That is to say, that a
defined measure may NOT have multiple owners.
Thus, we have a 1:N relationship between the owners table and the
measure table.
+---------------------+ +---------------------------+
+ ippmOwnersTable + + ippmMeasureTable +
+---------------------+ 1:N +---------------------------+
+ OwnersOwner: "Acme" +--------------+ Measure Owner: "Acme" +
+ ..... + + Measure Name:"OneWayDelay"+
+ "Foo" + +...... +
+ + + Measure Owner: "Foo" +
+---------------------+ + Measure Name: "PacketLoss"+
+---------------------------+
5.4.2. Relationship between the Measure Table and the Network Measure
Table/Aggregated Measure Table
The network measure table and the aggregated measure table can be
seen as logical "extensions" to the measure table.
The measure table contains information that is common to both types
of measurements. The information found in the Network Measure Table
and the Aggregated Measure Table is specific to each type of measure.
As the network measure table is read-only, entries in this table must
be populated by the agent upon startup.
The agent could potentially read a database that contains network
measures configured by a 3rd party proprietary management system that
directly interacts with the points of measure. An entry can not be
created in the network measure table without creating the
corresponding entry in the measure table associated to the measure.
This also implies that the "owner" of the measure be defined in the
owners table.
The aggregated measure table allows for an "owner" to create
aggregated measures (such as average, minimum, maximum) on existing
measures that are in the measure table. If an "owner" (A) wishes to
create an aggregated measure on a measure "owned" by another
"owner" (B), then "owner" (B) must grant "owner" (A) access to his
measures. This can be done in the resultsharing table.
Even though the Measure Table is read-create, an "owner" should only
be able to create, or modify entries in the measure table that
correspond to aggregated measure types. Should an "owner" attempt to
update an entry in the measure table that corresponds to an entry
in the network measure table, than access should be denied.
+---------------------------+ +----------------------------------+
+ ippmMeasureTable + + ippmNetworkMeasureTable +
+---------------------------+ +----------------------------------+
+ Measure Owner: "Acme" + + MeasureSrc: "Src1" +
+ Measure Name:"OneWayDelay + ---+ MeasureDst: "Dst1" +
+ ....... + + ........ +
+ Measure Owner: "Foo" + + MeasureSrc: "Src2" +
+ Measure Name: "PacketLoss"+ + MeasureDst: "Dst2" +
+ + +----------------------------------+
+ +
+ + +----------------------------------+
+ + + ippmAggregatedMeasureTable +
+ + +----------------------------------+
+ Measure Owner: "Acme" + + AMHistoryOwner: "Foo" +
+ Measure Name: "AvgPLoss" + ---+ AMHistoryMetric: "PacketLoss" +
+---------------------------+ +----------------------------------+
+---------------------------------+ +--------------------------+
+ ippmResultSharingTable + + ippmHistoryTable +
+ + + (ex: with OWPL values) +
+---------------------------------+ +--------------------------+
+ SharingOwner: "Foo" + + Idx: Meas. Owner"Foo " +
+ SharingMeasureOwner:"PacketLoss"+ + Measure Index: 1 +
+ + + Metrix Indx: 12 +
+ SharingGrantedOwner: "Acme" + + +
+---------------------------------+ + HistorySqceNdx: 1 +
+ GMTTimeStampValue +
+ Value: 5 +
+------------------------- +
+ Idx: Meas. Owner "Foo" +
+ Mesure Index: 1 +
+ Metric Index: 12 +
+ HistorySqceNdx: 2 +
+ GMTTimeStampValue +
+ Value: 15 +
+ Idx: Meas. "Acme" +
+ Measure Index: 3 +
+ Metric Index: 14 +
+ HistorySqceNdx: 1 +
+ GMTTimeStampValue +
+ Value: 10 +
+--------------------------+
As the aggregated measure table essentially "inherits" from the
measure table, one can not create an entry is this table without
first creating an entry in the measure table. Likewise, one can not
delete an entry in the measure table without first deleting the
corresponding row in the aggregated measure table. This logic ensures
that there are no "orphaned" table entries in the aggregated measure
table.
6. IPPM-REPORTING-MIB conceptual presentation
6.1. IPPM-REPORTING-MIB diagram
Conceptual view of objects configured using the IPPM-REPORTING-MIB Conceptual view of objects configured using the IPPM-REPORTING-MIB
+--------------------------------------------------------+ +--------------------------------------------------------+
| IPPM-REPORTING-MIB entity | | IPPM-REPORTING-MIB entity |
| | | |
| +---------------------+ +-------------------+ | | +---------------------+ +-------------------+ |
| | | | | | | | | | | |
| | Measure scheduler | | Result storage | | | | Measure scheduler | | Result storage | |
| | | | | | | | | | | |
skipping to change at page 15, line 5 skipping to change at page 17, line 5
|GetMeasureResults | |GetMeasureMetricResults | |GetMeasureResults | |GetMeasureMetricResults |
|-------------------| |------------------------| |-------------------| |------------------------|
| | | owner | | | | owner |
| owner | | privateNdx | | owner | | privateNdx |
| privateNdx | | metric | | privateNdx | | metric |
+-------------------+ +------------------------+ +-------------------+ +------------------------+
The managed objects of the IPPM-REPORTING-MIB are the measures and The managed objects of the IPPM-REPORTING-MIB are the measures and
the results. the results.
5.2. Conceptual programming interface 6.2. Conceptual programming interface
This section describes a conceptual programming interface for the This section describes a conceptual programming interface for the
integration of the IPPM-REPORTING-MIB in a point of measure. integration of the IPPM-REPORTING-MIB in a point of measure.
5.2.1. Measure control 6.2.1. Measure control
A measure is created/deleted/suspended through the ControlMeasure() A measure is created/deleted/suspended through the ControlMeasure()
call. call.
5.2.2. Result log 6.2.2. Result log
A result of a measure is created in the IPPM-REPORTING-MIB History A result of a measure is created in the IPPM-REPORTING-MIB History
table using a CreateResult() call. Results belonging to a measure are table using a CreateResult() call. Results belonging to a measure are
managed according to the setup of the measure. managed according to the setup of the measure.
5.2.3. Reporting 6.2.3. Reporting
Results are reported using the method GetResult(), Results are reported using the method GetResult(),
GetMeasureMetricResults() and GetMeasureResults() respectively to get GetMeasureMetricResults() and GetMeasureResults() respectively to get
a singleton result, the singleton result of a metric measure, and a singleton result, the singleton result of a metric measure, and
finally to get the singleton result of a measure. finally to get the singleton result of a measure.
5.2.4. Logical calls 6.2.4. Logical calls
Objects are managed using 5 main primitives: Objects are managed using 5 main primitives:
controlMeasure(); controlMeasure();
CreateResult(); CreateResult();
GetResult(); GetResult();
GetMeasureMetricResults(); GetMeasureMetricResults();
GetMeasureResults(). GetMeasureResults().
5.3. SNMP mapping 6.3. SNMP mapping
ControlMeasure() corresponds to a SNMP set-request on a conceptual ControlMeasure() corresponds to a SNMP set-request on a conceptual
row of ippmMeasureEntry and on a conceptual row of row of ippmMeasureEntry and on a conceptual row of
ippmNetworkMeasureEntry. ippmNetworkMeasureEntry.
CreateResult() is a internal interface for adding measure results in CreateResult() is a internal interface for adding measure results in
the ippmHistoryTable. the ippmHistoryTable.
GetResult() corresponds to an SNMP get-request on a result. GetResult() corresponds to an SNMP get-request on a result.
GetMeasureMetricResults() corresponds to a SNMP walk on the results GetMeasureMetricResults() corresponds to a SNMP walk on the results
of a metric measure subtree. of a metric measure subtree.
GetMeasureResults() corresponds to a SNMP walk on the results of a GetMeasureResults() corresponds to a SNMP walk on the results of a
measure subtree. measure subtree.
6. Measurement architectures 7. Measurement architectures
There are four main measurement architectures. There are four main measurement architectures.
6.1. Proxy architecture 7.1. Proxy architecture
+----+ +----+ +----+ +----+
|NMS1| |NMS2| |NMS1| |NMS2|
+----+ +----+ +----+ +----+
^ ^ ^ ^
| | | |
+----------+ +----------+ +----------+ +----------+
| | | |
SNMP or Sibling SNMP or Sibling
| | | |
skipping to change at page 17, line 7 skipping to change at page 19, line 7
nor on the test protocol. The entities involved in the measurement do nor on the test protocol. The entities involved in the measurement do
not need to implement the IPPM-REPORTING-MIB nor SNMP. This mode not need to implement the IPPM-REPORTING-MIB nor SNMP. This mode
allows for lightweight implementation in the point of measure, and allows for lightweight implementation in the point of measure, and
also for heterogeneous control protocols to coexist. also for heterogeneous control protocols to coexist.
Finally, the proxy is a checkpoint where measurement activity may be Finally, the proxy is a checkpoint where measurement activity may be
logged, and where access to measurement setups may be tightly logged, and where access to measurement setups may be tightly
controlled. Thus, it provides a reliable architecture to manage the controlled. Thus, it provides a reliable architecture to manage the
security of a measurement system. security of a measurement system.
6.2. Reporting architecture 7.2. Reporting architecture
In this architecture the SNMP protocol is only used to read the In this architecture the SNMP protocol is only used to read the results
results of the measurements in the IPPM-REPORTING-MIB History Table, of the measurements in the IPPM-REPORTING-MIB History Table, and also to
and also to inform the NMS that an event has occurred. inform the NMS that an event has occurred.
+----+ +----+ +----+ +----+
|NMS1| |NMS2| |NMS1| |NMS2|
+----+ +----+ +----+ +----+
^ ^ ^ ^ ^ ^ ^ ^
| | | | | | | |
SNMP| SNMP| SNMP| SNMP|
| | | | | | | |
| | | | | | | |
| OWDP | OWDP | OWDP | OWDP
skipping to change at page 19, line 5 skipping to change at page 21, line 5
table. table.
In this mode, it is recommended to use an SNMPv2 Inform PDU to send the In this mode, it is recommended to use an SNMPv2 Inform PDU to send the
result because it ensures that the entire block of the result is result because it ensures that the entire block of the result is
received. There is no control using SNMP Trap PDU. received. There is no control using SNMP Trap PDU.
Also, in this mode, it is recommended to implement the IPPM-REPORTING- Also, in this mode, it is recommended to implement the IPPM-REPORTING-
MIB Measure table in read only in order to allow an NMS to read the MIB Measure table in read only in order to allow an NMS to read the
status of their measures. status of their measures.
6.3. Gateway architecture 7.3. Gateway architecture
The gateway architecture combines the proxy mode and the reporting mode. The gateway architecture combines the proxy mode and the reporting mode.
+-------+ +------+ +-------+ +------+
| NMS1 | | NMS2 | | NMS1 | | NMS2 |
+-------+ +------+ +-------+ +------+
^ ^ ^ ^
| | | |
SNMP SNMP SNMP SNMP
| | | |
skipping to change at page 19, line 46 skipping to change at page 21, line 46
+-------------+---------+ +--------+-------------+ +-------------+---------+ +--------+-------------+
| IPPM- | Packets | |Packets | IPPM | | IPPM- | Packets | |Packets | IPPM |
|REPORTING-MIB| Sender | |Receiver|REPORTING-MIB| |REPORTING-MIB| Sender | |Receiver|REPORTING-MIB|
| agent | |-OWDP-Test->| | agent | | agent | |-OWDP-Test->| | agent |
+-------------+---------+ +--------+-------------+ +-------------+---------+ +--------+-------------+
The NMS measurement queries are registered in the IPPM-REPORTING-MIB The NMS measurement queries are registered in the IPPM-REPORTING-MIB
scheduler and performed by the control and the test protocol. The NMS scheduler and performed by the control and the test protocol. The NMS
directly consults the result in the corresponding points of measure. directly consults the result in the corresponding points of measure.
6.4. Security 7.4. Security
The proxy mode provides flexibility and control of the access to the The proxy mode provides flexibility and control of the access to the
points of measure, while allowing lightweight control protocol and test points of measure, while allowing lightweight control protocol and test
protocol implementations in the points of measure. Different security protocol implementations in the points of measure. Different security
rules may be applied to the NMS domain and to measurement system rules may be applied to the NMS domain and to measurement system
domains. domains.
The reporting mode has 2 security domains: The reporting mode has 2 security domains:
+The control of the measurement setups relies on the control and the +The control of the measurement setups relies on the control and the
test protocol security mechanisms. test protocol security mechanisms.
+ The control of access to the results depends on the SNMP security + The control of access to the results depends on the SNMP security
mechanisms. mechanisms.
The gateway mode security relies on the security of the proxy mode and The gateway mode security relies on the security of the proxy mode and
of the reporting mode. of the reporting mode.
7. Reporting mode integration with the control and test protocols 8. Reporting mode integration with the control and test protocols
The IPPM-REPORTING-MIB standardizes the parameters that: The IPPM-REPORTING-MIB standardizes the parameters that:
+ Define the configuration of the IPPM metrics measures; + Define the configuration of the IPPM metrics measures;
+ Define the format of the results of the measure; + Define the format of the results of the measure;
+ Define the report of the IPPM metric measures results. + Define the report of the IPPM metric measures results.
It introduces the concept of owner namespace to allow for fast It introduces the concept of owner namespace to allow for fast
configuration and reporting across multiple points of measurement. configuration and reporting across multiple points of measurement.
skipping to change at page 20, line 38 skipping to change at page 22, line 38
negotiation between the NMS and the points of measure before activating negotiation between the NMS and the points of measure before activating
the measure. the measure.
A measure is primarily defined by its identifier, the metrics to A measure is primarily defined by its identifier, the metrics to
measure, the description of the end point addresses and the description measure, the description of the end point addresses and the description
of the scheduling of the measure. of the scheduling of the measure.
The description of the measure is distributed to the points of measure The description of the measure is distributed to the points of measure
involved. The distribution may not be synchronized. involved. The distribution may not be synchronized.
7.1. Integration 8.1. Integration
The control protocol, test protocol and the IPPM-REPORTING-MIB share the The control protocol, test protocol and the IPPM-REPORTING-MIB share the
same semantic. same semantic.
The integration of the IPPM-REPORTING-MIB, and the test and control The integration of the IPPM-REPORTING-MIB, and the test and control
protocols, relies on the use of the conceptual programming interface protocols, relies on the use of the conceptual programming interface
described in section 6. It consists in pushing the measure described in section 6. It consists in pushing the measure
setup/teardown parameters and the result values from the measurement setup/teardown parameters and the result values from the measurement
software to the IPPM-REPORTING-MIB agent. software to the IPPM-REPORTING-MIB agent.
7.2. Setup of the measure 8.2. Setup of the measure
The creation of the measure consists only in transferring the measure The creation of the measure consists only in transferring the measure
description from the measurement software to the MIB. The management of description from the measurement software to the MIB. The management of
the measure is done using the ControlMeasure(). the measure is done using the ControlMeasure().
The protocol, which provides the parameters of the measure to manage, The protocol, which provides the parameters of the measure to manage,
may be the control protocol of the test protocol. may be the control protocol of the test protocol.
Different frameworks may be used to setup a measure. Different frameworks may be used to setup a measure.
7.2.1. Synchronous setup 8.2.1. Synchronous setup
The control protocol sets up the measure both in the sender and the The control protocol sets up the measure both in the sender and the
receiver before the measurement. receiver before the measurement.
7.2.2. Asynchronous setup 8.2.2. Asynchronous setup
The control protocol sets up the measure only in the sender. In this The control protocol sets up the measure only in the sender. In this
case, the receiver has a service already activated (or pending )for the case, the receiver has a service already activated (or pending )for the
typeP of the measurement. typeP of the measurement.
As the first test packet includes the description of the measure, it may As the first test packet includes the description of the measure, it may
differ from regular test packets. If the first test packet is not differ from regular test packets. If the first test packet is not
consistent with the regular test packets, it must not be used for consistent with the regular test packets, it must not be used for
performing metrics measurement. performing metrics measurement.
7.3. Setup of the measurement report 8.3. Setup of the measurement report
The report description is an extension to the definition of a measure. The report description is an extension to the definition of a measure.
It describes the event and the data to include in the report. A report It describes the event and the data to include in the report. A report
is read by an NMS in the ippmReportTable, or pushed to a NMS using a is read by an NMS in the ippmReportTable, or pushed to a NMS using a
SNMP Trap PDU, a SNMP Inform PDU, an email, or a SMS. SNMP Trap PDU, a SNMP Inform PDU, an email, or a SMS.
The control protocol, or the test protocol, includes the description of The control protocol, or the test protocol, includes the description of
the report in the setup of the measure. the report in the setup of the measure.
Different types of reports may be combined: Different types of reports may be combined:
skipping to change at page 21, line 51 skipping to change at page 23, line 51
pushed on completion of the measure; pushed on completion of the measure;
+ An alarm report defines a threshold on the results of the + An alarm report defines a threshold on the results of the
measure. A message is sent to a host when the result raises measure. A message is sent to a host when the result raises
or fall the threshold; or fall the threshold;
+ An SLA report defines a threshold on the results of the + An SLA report defines a threshold on the results of the
measure. The events are filtered using a staircase method. measure. The events are filtered using a staircase method.
The report consists in the results of the measure (time and The report consists in the results of the measure (time and
value) of the filtered events. The reports are sent at each value) of the filtered events. The reports are sent at each
measure cycle or when the measure completes. measure cycle or when the measure completes.
7.4. Writing the measurement results in the IPPM-REPORTING-MIB 8.4. Writing the measurement results in the IPPM-REPORTING-MIB
Results have to be written by the measurement task in the agent Results have to be written by the measurement task in the agent
implementing the IPPM MIB. implementing the IPPM MIB.
Adding the results of a measurement consists in the transfer of the Adding the results of a measurement consists in the transfer of the
result from the measurement software to the agent. The protocol that result from the measurement software to the agent. The protocol that
provides the result may be the control protocol, or the test protocol. provides the result may be the control protocol, or the test protocol.
Writing a result is done using the CreateResult(). Writing a result is done using the CreateResult().
7.5. Report download and upload 8.5. Report download and upload
A report is read in the ippmReportTable using SNMP, or pushed by the A report is read in the ippmReportTable using SNMP, or pushed by the
IPPM_MIB agent using a SNMP Trap PDU, a SNMP Inform PDU, an email or a IPPM_MIB agent using a SNMP Trap PDU, a SNMP Inform PDU, an email or a
SMS. SMS.
7.6. Default value 8.6. Default value
The default values correspond to Ipv4 best effort. The default values correspond to Ipv4 best effort.
8. Definition 9. Definition
IPPM-REPORTING-MIB DEFINITIONS ::= BEGIN IPPM-REPORTING-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
MODULE-IDENTITY, MODULE-IDENTITY,
NOTIFICATION-TYPE, NOTIFICATION-TYPE,
OBJECT-TYPE, OBJECT-TYPE,
Integer32, Integer32,
Counter32, Counter32
experimental
FROM SNMPv2-SMI FROM SNMPv2-SMI
ippm
FROM IPPM-REGISTRY
OwnerString OwnerString
FROM RMON-MIB FROM RMON-MIB
protocolDir InetAddressType,
FROM RMON2-MIB InetAddress
DisplayString, FROM INET-ADDRESS-MIB
SnmpAdminString
FROM SNMP-FRAMEWORK-MIB
TimeStamp, TimeStamp,
DateAndTime,
TruthValue, TruthValue,
RowStatus, RowStatus,
StorageType, StorageType,
TEXTUAL-CONVENTION TEXTUAL-CONVENTION
FROM SNMPv2-TC FROM SNMPv2-TC
MODULE-COMPLIANCE, MODULE-COMPLIANCE,
OBJECT-GROUP, OBJECT-GROUP,
NOTIFICATION-GROUP NOTIFICATION-GROUP
FROM SNMPv2-CONF; FROM SNMPv2-CONF;
ippmReportingMib MODULE-IDENTITY ippmReportingMib MODULE-IDENTITY
LAST-UPDATED "200202011200Z" -- March 17, 2002 LAST-UPDATED "200203171200Z" -- March 17, 2002
ORGANIZATION "France Telecom - R&D" ORGANIZATION "France Telecom - R&D"
CONTACT-INFO CONTACT-INFO
"Mail : Emile Stephan "Mail : Emile Stephan
France Telecom - R&D, Dpt. CPN France Telecom - R&D, Dpt. CPN
2, Avenue Pierre Marzin 2, Avenue Pierre Marzin
Technopole Anticipa Technopole Anticipa
22307 Lannion Cedex 22307 Lannion Cedex
FRANCE FRANCE
Tel: + 33 2 96 05 36 10 Tel: + 33 2 96 05 36 10
E-mail: emile.stephan@francetelecom.com E-mail: emile.stephan@francetelecom.com
Jessie Jewitt Jessie Jewitt
France Telecom - - R&D France Telecom - R&D
801 Gateway Blvd. Suit 500 801 Gateway Blvd. Suit 500
South San Francisco, CA 94080 South San Francisco, CA 94080
Tel : 1 650 875-1524 Tel : 1 650 875-1524
E-mail : jessie.jewitt@rd.francetelecom.com" E-mail : jessie.jewitt@rd.francetelecom.com"
DESCRIPTION DESCRIPTION
" This memo defines a portion of the Management Information Base " This memo defines a portion of the Management Information Base (MIB) for use with
(MIB) for use with network management protocols in TCP/IP-based network management protocols in TCP/IP-based internets. In particular, it specifies
internets. In particular, it specifies the objects used for managing the objects used for managing the results of the IPPM metrics measurements, alarms and
the results of the IPPM metrics measurements, alarms and reporting reporting the measures results.
the measures results.
" "
REVISION "200210181200Z" -- 18 October 2002
DESCRIPTION
"General cleanup
Change 5 tables to read write"
::= { ippm 2 } ::= { ippm 2 }
-- --
-- TEXTUAL-CONVENTION -- TEXTUAL-CONVENTION
-- --
TimeUnit ::= TEXTUAL-CONVENTION TimeUnit ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A list of time units." "A list of time units."
SYNTAX INTEGER { SYNTAX INTEGER {
skipping to change at page 23, line 49 skipping to change at page 26, line 38
week(3), week(3),
day(4), day(4),
hour(5), hour(5),
second(6), second(6),
ms(7), ms(7),
us(8), us(8),
ns(9) ns(9)
} }
-- --
-- --
-- A absolute, GMT timer using UTC like convention.
--
--
GMTDateAndTime ::= TEXTUAL-CONVENTION IppmStandardMetrics ::= TEXTUAL-CONVENTION
DISPLAY-HINT "d-d-d,d:d:d,4d"
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A date-time specification. " Each standard metric is identified in the IPPM-METRICS-
REGISTRY under the node rfc in a chronological order. To permit
several metrics to be performed in a single measure there is an need
to describe in a bit string the metrics to be performed, granted...
This textual convention defines an octet string that gathered in a
bit string a sequence of bits. The bit order corresponds to the order
of the metrics identifiers in the registry.
The first bit of the string is not used.
Example:
One-way-Delay(6) is identified as the leaf number 6 of the node rfc of the
registry. One-way-Packet-Loss(12) is identified as the leaf number 12 of the node
rfc of the registry. A network measure performing both One-way-Delay(6) and One-
way-Packet-Loss(12) will be described as '0000001000001000'b, '0208'B.
field octets contents range
----- ------ -------- -----
1 1-2 year* 0..99
2 3-4 month 1..12
3 5-6 day 1..31
4 7-8 hour 0..23
5 9-10 minutes 0..59
6 11-12 seconds 0..59
7 13-16 250 picoseconds 0..2^32-1
" "
SYNTAX OCTET STRING (SIZE (16)) SYNTAX OCTET STRING
GmtTimeFilter ::= TEXTUAL-CONVENTION GMTTimeStamp ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"GmtTimeFilter TC is inspired by the TimeFilter defined "The value of the ippmSystemTime object at which a specific occurrence
in RMON2. The reference for the time of TimeFilter is happened. The specific occurrence must be defined in the description of any object
the local value of sysUptime, while GmtTimeFilter uses defined using this type.
an absolute reference of time.Æ Æ
SYNTAX GMTDateAndTime field octets contents range
----- ------ -------- -----
1 1-4 second since 1 Jan 2000 0H00* 0..2^31 - 1
2 5-8 fractional part of the second* 0..2^32 - 1
* the value is in network-byte order
The timestamp format is directly inspired from the NTP timestamp format.
It differs because it counts the second since 1 Jan 2000 0H00 instead of 1 Jan 1900
0H00. The most significant bit of the part that represents the second is reserved. It
will wrap in year 2068 (The NTP timestamp will wrap in year 2036).
This bit is set to indicate if the fractional part of the second contains a precision
field and a synchronization field as initially proposed in the OWAMP draft.
When this bit is not set the resolution is maximal.
The maximal resolution is close to 250 picoseconds.
The precision of the timestamp must be provided in another field.
"
SYNTAX OCTET STRING (SIZE (8))
TypeP ::= TEXTUAL-CONVENTION TypeP ::= TEXTUAL-CONVENTION
DISPLAY-HINT "1d." DISPLAY-HINT "1d."
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This textual convention is used to describe the "This textual convention is used to describe the protocol encapsulation list of a
protocol encapsulation list of a packet, and is used as packet, and is used as the value of the SYNTAX clause for the type of the Src and Dst
the value of the SYNTAX clause for the type of the Src of an IPPM measure. The RFC2895 specifies a macro for the definition of protocol
and Dst of an IPPM measure. The RFC2895 specifies a identifiers while its companion document, the RFC2896 defines a set of protocol
macro for the definition of protocol identifiers while identifiers.
its companion document, the RFC2896 defines a set of
protocol identifiers.
Notes: An IPPM TypeP does not differ from RMON2 Protocol Notes: An IPPM TypeP does not differ from RMON2 Protocol identifiers, but TypeP usage
identifiers, but TypeP usage in IPPM MIB differs from in IPPM MIB differs from Protocol identifier usage in RMON2. A IPPM measure is active,
Protocol identifier usage in RMON2. A IPPM measure is so generally TypeP does not describe the link layer (i.e. ether2...). Valid Internet
active, so generally TypeP does not describe the link packets are sent from Src to Dst. Then the choice of the link layer relies on the
layer (i.e. ether2...). Valid Internet packets are sent Internet stack.
from Src to Dst. Then the choice of the link layer
relies on the Internet stack.
For example, the RFC2896 defines the protocol identifier For example, the RFC2896 defines the protocol identifier
'16.0.0.0.1.0.0.8.0.0.0.0.6.0.0.0.23.3.0.0.0' which '16.0.0.0.1.0.0.8.0.0.0.0.6.0.0.0.23.3.0.0.0' which represents ether2.ip.tcp.telnet
represents ether2.ip.tcp.telnet and the protocol and the protocol identifier 16.0.0.0.1.0.0.8.0.0.0.0.4.0.0.0.17.3.0.0.0 which stands
identifier 16.0.0.0.1.0.0.8.0.0.0.0.4.0.0.0.17.3.0.0.0 for ether2.ip.ipip4.udp. The corresponding TypeP are
which stands for ether2.ip.ipip4.udp. The corresponding '12.0.0.8.0.0.0.0.6.0.0.0.23.3.0.0.0' (ip.tcp.telnet) and
TypeP are '12.0.0.8.0.0.0.0.6.0.0.0.23.3.0.0.0' 12.0.0.8.0.0.0.0.4.0.0.0.17.3.0.0.0 (ip.ipip4.udp)."
(ip.tcp.telnet) and 12.0.0.8.0.0.0.0.4.0.0.0.17.3.0.0.0
(ip.ipip4.udp)."
SYNTAX OCTET STRING SYNTAX OCTET STRING
IppmReportDefinition ::= TEXTUAL-CONVENTION IppmReportDefinition ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"IppmReportDefinition is intended to be used for describing the "IppmReportDefinition is intended to be used for describing the report
report resulting from a measurement. By default, all the results of a resulting from a measurement. By default, all the results of a measure belong to the
measure belong to the report of this measure. report of this measure.
The first step of the report definition sets up triggers on the The first step of the report definition sets up triggers on the value of the
value of the measure, and on the distribution over time of the events measure, and on the distribution over time of the events generated by these triggers.
generated by these triggers.
The resulting measures corresponding to an event are reported The resulting measures corresponding to an event are reported periodically,
periodically, or sent in alarms as soon as the event occurs. or sent in alarms as soon as the event occurs.
The end of the description describes housekeeping tasks. The end of the description describes housekeeping tasks.
An action if performed if the corresponding bit is set to 1. An action is performed if the corresponding bit is set to 1.
onSingleton(1): onSingleton(1):
The actions are performed each time a new result of the The actions are performed each time a new result of the measure occurs.
measure occurs.
onMeasureCycle(2): onMeasureCycle(2):
The actions are performed on the results of the measure The actions are performed on the results of the measure at the end of each cycle of
at the end of each cycle of measure. measure.
onMeasureCompletion(3): onMeasureCompletion(3):
The actions are performed on the results of the measure The actions are performed on the results of the measure at the end of the measure.
at the end of the measure.
reportOnlyUptoDownMetricResults(4): reportOnlyUptoDownMetricResults(4):
Report the contiguous results that are on opposite sides Report the contiguous results that are on opposite sides of the metric threshold.
of the metric threshold.
reportOnlyExceededEventsDuration(5): reportOnlyExceededEventsDuration(5):
Report the current result of a series of contiguous Report the current result of a series of contiguous results that exceed the metric
results that exceed the metric threshold when the threshold when the duration of the series is over the events duration threshold
duration of the series is over the events duration seconds.
threshold seconds.
inIppmReportTable(6): inIppmReportTable(6):
Store the report in the local ippmReportTable. Store the report in the local ippmReportTable.
inSNMPTrapPDU(7): inSNMPTrapPDU(7):
Send the report using a SNMP-Trap-PDU. Send the report using a SNMP-Trap-PDU.
inSNMPv2TrapPDU(8): inSNMPv2TrapPDU(8):
Send the report using a SNMPv2-Trap-PDU. Send the report using a SNMPv2-Trap-PDU.
inInformRequestPDU(9): inInformRequestPDU(9):
Send the report using a SNMP InformRequest-PDU. Send the report using a SNMP InformRequest-PDU.
inEmail(10): inEmail(10):
Send the report using an email. Send the report using an email.
inSMS(11): inSMS(11):
Send the report using a SMS. Send the report using a SMS.
clearHistory(12): clearHistory(12):
Remove all the results corresponding to this measure Remove all the results corresponding to this measure from the ippmHistoryTable.
from the ippmHistoryTable.
clearReport(13): clearReport(13):
Remove all the results corresponding to this measure Remove all the results corresponding to this measure from the ippmReportTable.
from the ippmReportTable.
" "
SYNTAX BITS { SYNTAX BITS {
none(0), -- reserved none(0), -- reserved
onSingleton(1), onSingleton(1),
onMeasureCycle(2), onMeasureCycle(2),
onMeasureCompletion(3), onMeasureCompletion(3),
reportOnlyUptoDownMetricResults(4), reportOnlyUptoDownMetricResults(4),
reportOnlyExceededEventsDuration(5), reportOnlyExceededEventsDuration(5),
inIppmReportTable(6), inIppmReportTable(6),
inSNMPTrapPDU(7), inSNMPTrapPDU(7),
inSNMPv2TrapPDU(8), inSNMPv2TrapPDU(8),
inInformRequestPDU(9), inInformRequestPDU(9),
inEmail(10), inEmail(10),
inSMS(11), inSMS(11),
clearHistory(12), clearHistory(12),
clearReport(13) clearReport(13)
} }
IppmStandardMetrics ::= TEXTUAL-CONVENTION -- IPPM Mib objects definitions
ippmCompliances OBJECT IDENTIFIER ::= { ippmReportingMib 2 }
ippmSystemGroup OBJECT IDENTIFIER ::= { ippmReportingMib 3 }
ippmOwnersGroup OBJECT IDENTIFIER ::= { ippmReportingMib 4 }
ippmMeasureGroup OBJECT IDENTIFIER ::= { ippmReportingMib 5 }
ippmHistoryGroup OBJECT IDENTIFIER ::= { ippmReportingMib 6 }
ippmNetworkMeasureGroup OBJECT IDENTIFIER ::= { ippmReportingMib 7 }
ippmAggregatedMeasureGroup OBJECT IDENTIFIER ::= { ippmReportingMib 8 }
ippmReportGroup OBJECT IDENTIFIER ::= { ippmReportingMib 9 }
ippmNotifications OBJECT IDENTIFIER ::= { ippmReportingMib 10 }
--
-- ippmSystemGroup
--
--
ippmSystemTime OBJECT-TYPE
SYNTAX GMTTimeStamp
MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The definition of the standardized IPPM metrics. "The current time of the measurement system."
If the draftMetrics bit is set then the other bits describe a WG ::= { ippmSystemGroup 1 }
draft metric identifier.
ippmSystemSynchronizationType OBJECT-TYPE
SYNTAX INTEGER {
other(0),
ntp(1),
gps(2),
cdma(4)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"ippmSystemSynchronizationType describes the mechanism
used to synchronize the system.
Other(0)
The synchronization process must be defined
in the ippmSystemSynchonizationDescription.
Ntp(1)
The system is synchronized using the network
time protocol. The NTP synchronization must be described
in the ippmSystemSynchonizationDescription.
Gps (2)
The system is synchronized using the GPS clocks.
Cdma(4)
The system is synchronized using the CDMA clocks.
" "
SYNTAX BITS { ::= { ippmSystemGroup 2 }
draftMetrics(0),
instantaneousUnidirectionalConnectivity(1), ippmSystemSynchronizationDescription OBJECT-TYPE
instantaneousBidirectionalConnectivity(2), SYNTAX SnmpAdminString
intervalUnidirectionalConnectivity(3), MAX-ACCESS read-only
intervalBidirectionalConnectivity(4), STATUS current
intervalTemporalConnectivity(5), DESCRIPTION
onewayDelay(6), "The description of the synchronization process."
onewayDelayPoissonStream(7), ::= { ippmSystemGroup 3 }
onewayDelayPercentile(8),
onewayDelayMedian(9), ippmSystemClockResolution OBJECT-TYPE
onewayDelayMinimum(10), SYNTAX Integer32
onewayDelayInversePercentile(11), MAX-ACCESS read-only
onewayPacketLoss(12), STATUS current
onewayPacketLossPoissonStream(13), DESCRIPTION
onewayPacketLossAverage(14), "ippmSystemClockResolution provides the precision of the clock used for the measures.
roundtripDelay(15), The unit is the picosecond. For example, the clock on an old Unix host might advance
roundtripDelayPoissonStream(16), only once every 10 msec, and thus have a resolution of only 10 msec. So its resolution
roundtripDelayPercentile(17), is 100000 picosecond and the value of ippmSystemClockResolution is 100000."
roundtripDelayMedian(18), ::= { ippmSystemGroup 4 }
roundtripDelayMinimum(19),
roundtripDelayInversePercentile(20) ippmSystemCurrentSynchronization OBJECT-TYPE
SYNTAX Integer32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The index on the last synchronization event in the ippmSynchronizationTable."
::= { ippmSystemGroup 5 }
ippmSynchronizationTable OBJECT-TYPE
SYNTAX SEQUENCE OF IppmSynchronizationEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This table registers the event related to the synchronization of the point of
measure. Each event is described in an ippmSynchronizationEntry.
ippmSynchronizationTable is mandatory.
ippmSynchronizationTable content is read only.
"
::= { ippmMeasureGroup 6 }
ippmSynchronizationEntry OBJECT-TYPE
SYNTAX IppmSynchronizationEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry describes a modification of the synchronization status. "
INDEX { ippmSynchronizationIndex }
::= { ippmSynchronizationTable 1 }
IppmSynchronizationEntry ::=
SEQUENCE {
ippmSynchronizationIndex Integer32,
ippmSynchronizationTime GMTTimeStamp,
ippmSynchronizationStratum Integer32
} }
-- IPPM Mib objects definitions
ippmCompliances OBJECT IDENTIFIER ::= { ippmMib 2 } ippmSynchronizationIndex OBJECT-TYPE
ippmOwnersGroup OBJECT IDENTIFIER ::= { ippmMib 3 } SYNTAX Integer32 (1..1000)
ippmSystemGroup OBJECT IDENTIFIER ::= { ippmMib 4 } MAX-ACCESS not-accessible
ippmMeasureGroup OBJECT IDENTIFIER ::= { ippmMib 5 } STATUS current
ippmHistoryGroup OBJECT IDENTIFIER ::= { ippmMib 6 } DESCRIPTION
ippmNetworkMeasureGroup OBJECT IDENTIFIER ::= { ippmMib 7 } "An index that identifies the synchronization events in chronological order."
ippmAggregatedMeasureGroup OBJECT IDENTIFIER ::= { ippmMib 8 } ::= { ippmSynchronizationEntry 1 }
ippmReportGroup OBJECT IDENTIFIER ::= { ippmMib 9 }
ippmNotifications OBJECT IDENTIFIER ::= { ippmMib 10 } ippmSynchronizationTime OBJECT-TYPE
SYNTAX GMTTimeStamp
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The time when the synchronization event occurs."
::= { ippmSynchronizationEntry 2 }
ippmSynchronizationStratum OBJECT-TYPE
SYNTAX Integer32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The stratum level of the clock computed when the synchronization event occurs."
::= { ippmSynchronizationEntry 3 }
ippmPointOfMeasureTable OBJECT-TYPE
SYNTAX SEQUENCE OF IppmPointOfMeasureEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
" A lookup table that identifies the management software in charge of the point of
measures.
ippmPointOfMeasureTable content is read only. It means that the measurement software
handles the table internally
ippmPointOfMeasureTable is mandatory.
"
::= { ippmSystemGroup 6 }
ippmPointOfMeasureEntry OBJECT-TYPE
SYNTAX IppmPointOfMeasureEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
" An entry may be the management address of a middleware in charge of the management
of a set of probes. It may the management address of a probe that contains several
line cards.
An entry describes the capability of a point of measure. The description may make the
use of wildcards to define multiple capabilities.
"
INDEX { ippmPointOfMeasureIndex }
::= { ippmPointOfMeasureTable 1 }
IppmPointOfMeasureEntry ::=
SEQUENCE {
ippmPointOfMeasureIndex Integer32,
ippmPointOfMeasureMgmtAddress SnmpAdminString,
ippmPointOfMeasureTypePAddress TypeP,
ippmPointOfMeasureAddress OCTET STRING
}
ippmPointOfMeasureIndex OBJECT-TYPE
SYNTAX Integer32 (1.. 65535)
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The index of the entry."
::= { ippmPointOfMeasureEntry 1 }
ippmPointOfMeasureMgmtAddress OBJECT-TYPE
SYNTAX SnmpAdminString
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"
The management software in charge of this point of measure."
::= { ippmPointOfMeasureEntry 2 }
ippmPointOfMeasureTypePAddress OBJECT-TYPE
SYNTAX TypeP
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Defines the type P of the address of the point of measure."
DEFVAL { '04000080001000'H } -- ->ip: 4.0.0.8.0.1.0
::= { ippmPointOfMeasureEntry 3 }
ippmPointOfMeasureAddress OBJECT-TYPE
SYNTAX OCTET STRING
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Specifies the address of the point of measure.
It is represented as an octet string with specific semantics and length as identified
by the ippmPointOfMeasureTypePAddress.
For example, if the ippmPointOfMeasureTypePAddress indicates an encapsulation of 'ip',
this object length is 4, followed by the 4 octets of the IP address, in network byte
order."
DEFVAL { '04C0210415'H } -- -> ip: 192.33.4.21
::= { ippmPointOfMeasureEntry 4}
-- --
-- ippmOwnersGroup -- ippmOwnersGroup
-- --
-- The ippmOwnersGroup objects are responsible for managing -- The ippmOwnersGroup objects are responsible for managing
-- the owners access to the measurements. -- the owners access to the measurements.
-- --
-- --
ippmOwnersTable OBJECT-TYPE ippmOwnersTable OBJECT-TYPE
SYNTAX SEQUENCE OF IppmOwnersEntry SYNTAX SEQUENCE OF IppmOwnersEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A NMS entity wishing to create and activate remote Ippm "A management entity wishing to create and activate remote Ippm measurements in an
measurements in an agent must previously be registered agent must previously be registered in the ippmOwnersTable.
in the ippmOwnersTable.
ippmOwnersTable content is read only. ippmOwnersTable content is read-create.
ippmOwnersTable is mandatory. It contains at least the ippmOwnersTable contains at least the owner 'monitor'.
owner 'monitor'.
ippmOwnersTable is mandatory, excepted if the VACM framework is used.
" "
::= { ippmOwnersGroup 1 } ::= { ippmOwnersGroup 1 }
ippmOwnersEntry OBJECT-TYPE ippmOwnersEntry OBJECT-TYPE
SYNTAX IppmOwnersEntry SYNTAX IppmOwnersEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The description of the resources the agent granted to a "The description of the resources granted to an SNMP application.
SNMP application.
For example, an instance of ippmOwnersOwner with an For example, an instance of ippmOwnersOwner with an OwnerString 'acme', which
OwnerString 'acme', which represents the 14th owner represents the 14th owner created in ippmOwnersTable would be named
created in ippmOwnersTable would be named
ippmOwnersEntryOwner.14. ippmOwnersEntryOwner.14.
Notes: Notes:
The ippmOwnersIndex value is a local index managed The ippmOwnersIndex value is a local index managed directly by the agent. The
directly by the agent. It is not used in anyway in the management application must poll to get the next available index value.
other IPPM tables." It is not used in anyway in the other IPPM tables."
INDEX { ippmOwnersIndex } INDEX { ippmOwnersIndex }
::= { ippmOwnersTable 1 } ::= { ippmOwnersTable 1 }
IppmOwnersEntry ::= SEQUENCE { IppmOwnersEntry ::= SEQUENCE {
ippmOwnersOwner OwnerString, ippmOwnersOwner SnmpAdminString,
ippmOwnersIndex Integer32, ippmOwnersIndex Integer32,
ippmOwnersGrantedMetrics IppmStandardMetrics, ippmOwnersGrantedMetrics IppmStandardMetrics,
ippmOwnersGrantedRules BITS, ippmOwnersGrantedRules BITS,
ippmOwnersIpAddress DisplayString, ippmOwnersIpAddress InetAddressType,
ippmOwnersEmail DisplayString, ippmOwnersEmail SnmpAdminString,
ippmOwnersSMS DisplayString, ippmOwnersSMS SnmpAdminString,
ippmOwnersStatus OwnerString ippmOwnersStatus OwnerString
} }
ippmOwnersIndex OBJECT-TYPE ippmOwnersIndex OBJECT-TYPE
SYNTAX Integer32 (1.. 65535) SYNTAX Integer32 (1.. 65535)
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An arbitrary index that identifies an entry in this "An arbitrary index that identifies an entry in this table"
table"
::= { ippmOwnersEntry 1 } ::= { ippmOwnersEntry 1 }
ippmOwnersOwner OBJECT-TYPE ippmOwnersOwner OBJECT-TYPE
SYNTAX OwnerString SYNTAX SnmpAdminString
MAX-ACCESS read-only MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The owner described by this entry." "The owner described by this entry."
::= { ippmOwnersEntry 2 } ::= { ippmOwnersEntry 2 }
ippmOwnersGrantedMetrics OBJECT-TYPE ippmOwnersGrantedMetrics OBJECT-TYPE
SYNTAX IppmStandardMetrics SYNTAX IppmStandardMetrics
MAX-ACCESS read-only MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
" Defines the metrics granted to an owner." " Defines the metrics granted to an owner."
::= { ippmOwnersEntry 3 } ::= { ippmOwnersEntry 3 }
ippmOwnersGrantedRules OBJECT-TYPE ippmOwnersGrantedRules OBJECT-TYPE
SYNTAX BITS { SYNTAX BITS {
all(0), all(0),
readonly(1), readonly(1),
permanent(2), permanent(2),
sender(2), sender(3),
receive(3), receive(4),
report(4), report(5),
alarm(5) alarm(6)
} }
MAX-ACCESS read-only MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Defines the rules this owner may act on in the current IPPM MIB "Defines the rules this owner may act on in the current IPPM MIB instance.
instance.
all(0): all(0):
The owner is granted all the rules. The owner is granted all the rules.
readonly(1): readonly(1):
The measures (not only the metrics) that this owner may The measures (not only the metrics) that this owner may access are
access are setup by the manager of the point of measure. The owner setup by the manager of the point of measure. The owner can not add new measures for
can not add new measures for these metrics. The creation and the these metrics. The creation and the configuration of the measures corresponding to
configuration of the measures corresponding to these metrics are these metrics are managed by the manager of the point of measure.
managed by the manager of the point of measure.
permanent(2): permanent(2):
The measures (not only the metrics) that this owner may The measures (not only the metrics) that this owner may access are
access are determined by the manager of the point of measure. The determined by the manager of the point of measure. The owner can not add new measures
owner can not add new measures for these metrics. The creation and for these metrics. The creation and the first configuration of the measures
the first configuration of the measures corresponding to these corresponding to these metrics are managed by the manager of the point of measure. The
metrics are managed by the manager of the point of measure. The owner owner may modify the measures parameters of the entries of the corresponding
may modify the measures parameters of the entries of the ippmMeasureEntry whose access is read-write.
corresponding ippmMeasureEntry whose access is read-write. Typically this allows the owner to suspend the measures, to change the beginning and
Typically this allows the owner to suspend the measures, end of the measures.
to change the beginning and end of the measures.
sender(3): sender(3):
The owner may only activate measures for those metrics The owner may only activate measures for those metrics that send
that send packets from the current point of measure. This flag is packets from the current point of measure. This flag is only suitable for network
only suitable for network measures. It shall be ignored for derived measures. It shall be ignored for derived metrics.
metrics.
receiver(2): receiver(2):
The owner may only activate measures for those metrics
that receive packets on the current point of measure. This flag is The owner may only activate measures for those metrics that receive
only suitable for network measures. It shall be ignored for derived packets on the current point of measure. This flag is only suitable for network
metrics. Such control increases the security. The owner may not measures. It shall be ignored for derived metrics. Such control increases the
generate packets from the probe. security. The owner may not generate packets from the probe.
report(4): report(4):
The owner may setup aggregated metrics on the measures The owner may setup aggregated metrics on the measures
corresponding to these metrics. corresponding to these metrics.
alarm(5): alarm(5):
The owner may setup alarms on the results of the The owner may setup alarms on the results of the measures metrics.
measures metrics.
e.g.: e.g.:
if the owner Acme is granted with the metric Instantaneous- if the owner Acme is granted with the metric Instantaneous-Unidirectional-Connectivity
Unidirectional-Connectivity as a Receiver in the current point of as a Receiver in the current point of measure, then Acme can not setup a
measure, then Acme can not setup a Instantaneous-Unidirectional- Instantaneous-Unidirectional-Connectivity to another point of measure.
Connectivity to another point of measure.
" "
DEFVAL { 1 } DEFVAL { 1 }
::= { ippmOwnersEntry 4 } ::= { ippmOwnersEntry 4 }
ippmOwnersIpAddress OBJECT-TYPE ippmOwnersIpAddress OBJECT-TYPE
SYNTAX DisplayString SYNTAX InetAddressType
MAX-ACCESS read-only MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The IP address of the NMS corresponding to this owner. "The IP address of the management entity corresponding to this
The address is human readable and is represented using the dot owner. The address is human readable and is represented using the dot format."
format."
::= { ippmOwnersEntry 5 } ::= { ippmOwnersEntry 5 }
ippmOwnersEmail OBJECT-TYPE ippmOwnersEmail OBJECT-TYPE
SYNTAX DisplayString SYNTAX SnmpAdminString
MAX-ACCESS read-only MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The email address of the NMS corresponding to this "The email address of the management entity corresponding to this
owner." owner."
::= { ippmOwnersEntry 6 } ::= { ippmOwnersEntry 6 }
ippmOwnersSMS OBJECT-TYPE ippmOwnersSMS OBJECT-TYPE
SYNTAX DisplayString SYNTAX SnmpAdminString
MAX-ACCESS read-only MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The SMS phone number of the NMS corresponding to this "The SMS phone number of the management entity corresponding to
owner." this owner."
::= { ippmOwnersEntry 7 } ::= { ippmOwnersEntry 7 }
ippmOwnersStatus OBJECT-TYPE ippmOwnersStatus OBJECT-TYPE
SYNTAX RowStatus SYNTAX RowStatus
MAX-ACCESS read-only MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The status of this table entry." "The status of this table entry."
::= { ippmOwnersEntry 8 } ::= { ippmOwnersEntry 8 }
-- --
-- ippmResultSharingTable -- ippmResultSharingTable
-- --
ippmResultSharingTable OBJECT-TYPE ippmResultSharingTable OBJECT-TYPE
SYNTAX SEQUENCE OF IppmResultSharingEntry SYNTAX SEQUENCE OF IppmResultSharingEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
" The ippmResultSharingTable controls the access of an " The ippmResultSharingTable controls the access of an owner to the measure results of
owner to the measure results of other owners. An owner other owners. An owner may grant another access to read the result of its measure.
may grant another access to read the result of its
measure.
Entries may exist in ippmResultSharingTable even if the Entries may exist in ippmResultSharingTable even if the measures to be shared are not
measures to be shared are not yet defined. Deleting a yet defined. Deleting a measure entry in the ippmMeasureTable does not delete the
measure entry in the ippmMeasureTable does not delete entries corresponding to this measure in the ippmResultSharingTable.
the entries corresponding to this measure in the
ippmResultSharingTable.
IppmResultSharingTable is optional. IppmResultSharingTable is optional.
IppmResultSharingTable content is read only. IppmResultSharingTable content is read-create.
If this table is not implemented then the owner has only If this table is not implemented then the owner has only access to its own measurement
access to its measure results." results."
::= { ippmOwnersGroup 2 } ::= { ippmOwnersGroup 2 }
ippmResultSharingEntry OBJECT-TYPE ippmResultSharingEntry OBJECT-TYPE
SYNTAX IppmResultSharingEntry SYNTAX IppmResultSharingEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry allows an owner to read the results of a "An entry allows an owner to read the results of a measure owned by another owner.
measure owned by another owner.
It permits 2 typical usages: It permits 2 typical usages:
1) Creating derived measurements on these results 1) Creating derived measurements on these results
2) Reading the results from a remote NMS. 2) Reading the results from a remote management station.
Example: if acme.12 is a One-way-Delay(6) measure Example: if acme.12 is a One-way-Delay(6) measure, Acme may allow Peter to make
Acme may allow Peter to make derived metrics derived metrics on the results of this measure.
on the results of this measure.
" "
INDEX { ippmResultSharingOwner, ippmResultSharingIndex} INDEX { ippmResultSharingOwner, ippmResultSharingIndex}
::= { ippmResultSharingTable 1 } ::= { ippmResultSharingTable 1 }
IppmResultSharingEntry ::= SEQUENCE { IppmResultSharingEntry ::= SEQUENCE {
ippmResultSharingOwner OwnerString, ippmResultSharingOwner OwnerString,
ippmResultSharingIndex Integer32, ippmResultSharingIndex Integer32,
ippmResultSharingMeasureOwner OwnerString, ippmResultSharingMeasureOwner OwnerString,
ippmResultSharingMeasureIndex Integer32, ippmResultSharingMeasureIndex Integer32,
ippmResultSharingGrantedOwner OwnerString, ippmResultSharingGrantedOwner OwnerString,
ippmResultSharingStatus RowStatus ippmResultSharingStatus RowStatus
} }
ippmResultSharingOwner OBJECT-TYPE ippmResultSharingOwner OBJECT-TYPE
SYNTAX OwnerString SYNTAX OwnerString
MAX-ACCESS read-only MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
" The owner of this result control entry. Typically the " The owner of this result control entry. Typically the owner who
owner who created this conceptual row." created this conceptual row."
::= { ippmResultSharingEntry 1 } ::= { ippmResultSharingEntry 1 }
ippmResultSharingIndex OBJECT-TYPE ippmResultSharingIndex OBJECT-TYPE
SYNTAX Integer32 (1.. 65535) SYNTAX Integer32 (1.. 65535)
MAX-ACCESS read-only MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
" The index of this result control entry. The value is " The index of this result control entry. The value is managed by
managed by the owner. On creation a SNMP error 'inconsistentValue' is the owner. On creation a SNMP error 'inconsistentValue' is returned if this value is
returned if this value is already in use by this owner." already in use by this owner."
::= { ippmResultSharingEntry 2 } ::= { ippmResultSharingEntry 2 }
ippmResultSharingMeasureOwner OBJECT-TYPE ippmResultSharingMeasureOwner OBJECT-TYPE
SYNTAX OwnerString SYNTAX OwnerString
MAX-ACCESS read-only MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The owner of the measure to be shared. The couple "The owner of the measure to be shared. The couple
ippmResultSharingMeasureOwner, ippmResultSharingMeasureIndex ippmResultSharingMeasureOwner, ippmResultSharingMeasureIndex identifies absolutely a
identifies absolutely a measure" measure"
::= { ippmResultSharingEntry 3 } ::= { ippmResultSharingEntry 3 }
ippmResultSharingMeasureIndex OBJECT-TYPE ippmResultSharingMeasureIndex OBJECT-TYPE
SYNTAX Integer32 (1.. 65535) SYNTAX Integer32 (1.. 65535)
MAX-ACCESS read-only MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The index of the measure to be shared." "The index of the measure to be shared."
::= { ippmResultSharingEntry 4 } ::= { ippmResultSharingEntry 4 }
ippmResultSharingGrantedOwner OBJECT-TYPE ippmResultSharingGrantedOwner OBJECT-TYPE
SYNTAX OwnerString SYNTAX OwnerString
MAX-ACCESS read-only MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The owner who is granted access to the result of the "The owner who is granted access to the result of the measure
measure described by the couple ippmResultSharingMeasureOwner, described by the couple ippmResultSharingMeasureOwner, ippmResultSharingMeasureIndex."
ippmResultSharingMeasureIndex."
::= { ippmResultSharingEntry 5 } ::= { ippmResultSharingEntry 5 }
ippmResultSharingStatus OBJECT-TYPE ippmResultSharingStatus OBJECT-TYPE
SYNTAX RowStatus SYNTAX RowStatus
MAX-ACCESS read-only MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
" The status of this table entry. Once the entry status " The status of this table entry. Once the entry status is set to
is set to active." active."
::= { ippmResultSharingEntry 6 } ::= { ippmResultSharingEntry 6 }
-- --
-- ippmSystemGroup
--
--
ippmSystemTimer OBJECT-TYPE
SYNTAX GMTDateAndTime
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The current time of the system."
::= { ippmSystemGroup 1 }
ippmSystemSynchonizationType OBJECT-TYPE
SYNTAX INTEGER {
other(0),
ntp(1),
gps(2),
cdma(4)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"ippmSystemSynchonizationType describes the mechanism
used to synchronize the system.
Other(0)
The synchronization process must be defined
in the ippmSystemSynchonizationDescription.
Ntp(1)
The system is synchronized using the network
time protocol. The NTP synchronization must be described
in the ippmSystemSynchonizationDescription.
Gps (2)
The system is synchronized using the GPS clocks.
Cdma(4)
The system is synchronized using the CDMA
clocks.
"
::= { ippmSystemGroup 2 }
ippmSystemSynchonizationDescription OBJECT-TYPE
SYNTAX DisplayString
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The description of the synchronization process."
::= { ippmSystemGroup 3 }
ippmSystemClockResolution OBJECT-TYPE
SYNTAX Integer32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"ippmSystemClockResolution provides the precision of the
clock used for the measures. The unit is 1/10 of
millisecond. For example, the clock on an old Unix host
might advance only once every 10 msec, and thus have a
resolution of only 10 msec."
::= { ippmSystemGroup 4 }
ippmSystemSynchronisationTime OBJECT-TYPE
SYNTAX DateAndTime
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The time when the last synchronization of the clock
occured. The last synchronization must be set even if
the synchronization is not automatic."
::= { ippmSystemGroup 5 }
ippmSystemClockAccuracy OBJECT-TYPE
SYNTAX Integer32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The most recent accuracy of the clock computed. The
accuracy must be computed even if the synchronization is
not automatic."
::= { ippmSystemGroup 6 }
ippmSystemClockSkew OBJECT-TYPE
SYNTAX Integer32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The most recent skew of the clock computed. The
ippmSystemSkew must be computed even if the
synchronization is not automatic."
::= { ippmSystemGroup 7 }
ippmSystemPrevClockAccuracy OBJECT-TYPE
SYNTAX Integer32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The previous accuracy of the clock measured. The
ippmSystemPrevClockAccuracy must be computed even if the
synchronization is not automatic."
::= { ippmSystemGroup 8 }
ippmSystemPrevClockSkew OBJECT-TYPE
SYNTAX Integer32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The previous skew of the clock measured. The
ippmSystemPrevClockSkew must be computed even if the
synchronisation is not automatic."
::= { ippmSystemGroup 9 }
ippmSystemSynchonizationOperStatus OBJECT-TYPE
SYNTAX INTEGER {
other(0),
unsynchronized(1),
initializing(2),
synchronized(4)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
" ippmSystemSynchonizationOperStatus describes the
operational status of the clock synchronization.
Other(0)
The status of the synchronization is unknown.
unsynchronized(1)
The system is not synchronized.
initializing(2)
The system is receiving synchronization
information but is not yet synchronized.
synchronized(4)
The system is synchronized.
"
::= { ippmSystemGroup 10 }
--
-- --
-- --
-- ippmMeasureGroup -- ippmMeasureGroup
-- --
-- --
-- --
ippmMetricTable OBJECT-TYPE ippmMetricsTable OBJECT-TYPE
SYNTAX SEQUENCE OF IppmMetricEntry SYNTAX SEQUENCE OF IppmMetricsEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table describes the current implementation and is "This table describes the current implementation and is mandatory. Each IPPM
mandatory. Each IPPM standardized metric must be standardized metric identified in the IPPM-METRICS-REGISTRY must be described in the
described in the table. table. The index of the metric corresponds to the node number of the metric in the rfc
In reporting mode, the entries of this table may be not subtree of the IPPM-METRICS-REGISTRY. That provides a metric with the same index value
accessible. It means that the measure software handles in any IPPM REPORTING MIB implementations.
the table internally.
ippmMetricTable is mandatory.
ippmMetricTable content is read only.
ippmMetricsTable is mandatory.
ippmMetricsTable content is read only.
" "
::= { ippmMeasureGroup 1 } ::= { ippmMeasureGroup 1 }
ippmMetricEntry OBJECT-TYPE ippmMetricsEntry OBJECT-TYPE
SYNTAX IppmMetricEntry SYNTAX IppmMetricsEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry describes the static capabilities of a metric "An entry describes the static capabilities of a metric implementation."
implementation." INDEX { ippmMetricsIndex }
INDEX { ippmMetricIndex } ::= { ippmMetricsTable 1 }
::= { ippmMetricTable 1 }
IppmMetricEntry ::= IppmMetricsEntry ::=
SEQUENCE { SEQUENCE {
ippmMetricIndex Integer32, ippmMetricsIndex Integer32,
ippmMetricCapabilities INTEGER, ippmMetricsCapabilities INTEGER,
ippmMetricUnit INTEGER, ippmMetricUnit INTEGER,
ippmMetricDescription DisplayString, ippmMetricsDescription SnmpAdminString,
ippmMetricMaxHistorySize Integer32 ippmMetricsMaxHistorySize Integer32
} }
ippmMetricIndex OBJECT-TYPE ippmMetricsIndex OBJECT-TYPE
SYNTAX Integer32 (1.. 65535) SYNTAX Integer32 (1.. 65535)
MAX-ACCESS read-only MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"ippmMetricIndex defines an unambiguous index for each "ippmMetricsIndex defines an unambiguous index for each standardized metric. Its value
standardized metric. Its value is the value of the node of the is the value of the node of the metric in the IPPM-REPORTING-MIB metrics registry
metric in the IPPM-REPORTING-MIB metrics registry
ippmMib.metrics.rfc. ippmMib.metrics.rfc.
Each metric registered in the standard registry must be present Each metric registered in the standard registry must be present in this table.
in this table. This index is used to identify the metric calculated between the IPPM-REPORTING-MIB
This index is used to identify the metric calculated between the entities involved in the measure.
IPPM-REPORTING-MIB entities involved in the measure.
Example: Example:
The index of the metric onewayPacketLossAverage which is The index of the metric onewayPacketLossAverage which is registered as
registered as ippmMib.metrics.rfc.onewayPacketLossAverage will ippmMib.metrics.rfc.onewayPacketLossAverage will always have the value 14."
always have the value 14." ::= { ippmMetricsEntry 1 }
::= { ippmMetricEntry 1 }
ippmMetricCapabilities OBJECT-TYPE ippmMetricsCapabilities OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
notImplemented(0), notImplemented(0),
implemented(1) implemented(1)
} }
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"notImplemented "notImplemented
the metric is not implemented. the metric is not implemented.
implemented implemented
the metric is implemented." the metric is implemented."
DEFVAL { implemented } DEFVAL { implemented }
::= { ippmMetricEntry 2 } ::= { ippmMetricsEntry 2 }
ippmMetricUnit OBJECT-TYPE ippmMetricUnit OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
noUnit(0), noUnit(0),
second(1), second(1),
ms(2), ms(2),
us(3), us(3),
ns(4), ns(4),
percentage(5), percentage(5),
packets(6), packets(6),
byte(6), byte(7),
kbyte(7), kbyte(8),
megabyte(8) megabyte(9)
} }
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The unit used in the current entity for the results of "The unit used in the current entity for the results of the measurement of this
the measurement of this metric." metric."
::= { ippmMetricEntry 3 } ::= { ippmMetricsEntry 3 }
ippmMetricDescription OBJECT-TYPE ippmMetricsDescription OBJECT-TYPE
SYNTAX DisplayString SYNTAX SnmpAdminString
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A textual description of the metric implementation." "A textual description of the metric implementation."
::= { ippmMetricEntry 4 } ::= { ippmMetricsEntry 4 }
ippmMetricMaxHistorySize OBJECT-TYPE ippmMetricsMaxHistorySize OBJECT-TYPE
SYNTAX Integer32 SYNTAX Integer32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Specifies the maximum number of results that a metric "Specifies the maximum number of results that a metric measure can
measure can save in the ippmHistoryTable." save in the ippmHistoryTable."
::= { ippmMetricEntry 5 } DEFVAL { 200 }
::= { ippmMetricsEntry 5 }
-- --
-- ippmMeasureTable -- ippmMeasureTable
-- --
-- --
ippmMeasureTable OBJECT-TYPE ippmMeasureTable OBJECT-TYPE
SYNTAX SEQUENCE OF IppmMeasureEntry SYNTAX SEQUENCE OF IppmMeasureEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The table of all the IPPM measures which are running in "The table of all the IPPM measures which are running in the device. They may not all
the device. They may not all be active. be active.
A measure consists of a subset of metrics to compute. A measure consists of a subset of metrics to compute. The results of the measure may
The results of the measure may be saved in the be saved in the ippmHistoryTable. The configuration of the measure sets the size of
ippmHistoryTable. The configuration of the measure sets the history requested in ippmMeasureHystorySize.
the size of the history requested in
ippmMeasureHystorySize.
The maximum number of MIB objects to be collected in the The maximum number of MIB objects to be collected in the portion of ippmHistoryTable
portion of ippmHistoryTable associated with this metric associated with this metric depends on the value of the ippmMetricMaxHistorySize.
depends on the value of the ippmMetricMaxHistorySize.
The value of each metric ippmMeasureHystorySize must not The value of each metric ippmMeasureHystorySize must not be over the value of
be over the value of ippmMetricMaxHistorySize ippmMetricMaxHistorySize corresponding to this metric in the ippmMetricTable.
corresponding to this metric in the ippmMetricTable.
The ippmMeasureTable is mandatory. The ippmMeasureTable is mandatory.
ippmMeasureTable content is read only. It means that the ippmMeasureTable content is read-create. The table is handled internally by the
table is handled internally by the measurement measurement software for network measures.
software.
The setup of network is not permitted through the IPPM REPORTING MIB. OWAP provides a
setup protocol to enable and teardown networks measures.
" "
::= { ippmMeasureGroup 2 } ::= { ippmMeasureGroup 2 }
ippmMeasureEntry OBJECT-TYPE ippmMeasureEntry OBJECT-TYPE
SYNTAX IppmMeasureEntry SYNTAX IppmMeasureEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The measure entries are created/deleted internally by "The measure entries are created/deleted internally by the measurement software.
the measurement software.
" "
INDEX { ippmMeasureOwner, ippmMeasureIndex } INDEX { ippmMeasureOwner, ippmMeasureIndex }
::= { ippmMeasureTable 1 } ::= { ippmMeasureTable 1 }
IppmMeasureEntry ::= IppmMeasureEntry ::=
SEQUENCE { SEQUENCE {
ippmMeasureOwner OwnerString, ippmMeasureOwner OwnerString,
ippmMeasureIndex Integer32, ippmMeasureIndex Integer32,
ippmMeasureName DisplayString, ippmMeasureName SnmpAdminString,
ippmMeasureMetrics IppmStandardMetrics, ippmMeasureMetrics IppmStandardMetrics,
ippmMeasureBeginTime GMTDateAndTime, ippmMeasureBeginTime GMTTimeStamp,
ippmMeasureClockPeriodUnit TimeUnit, ippmMeasureClockPeriodUnit TimeUnit,
ippmMeasureClockPeriod Integer32, ippmMeasureClockPeriod Integer32,
ippmMeasureDurationUnit TimeUnit, ippmMeasureDurationUnit TimeUnit,
ippmMeasureDuration Integer32, ippmMeasureDuration Integer32,
ippmMeasureHystorySize Integer32, ippmMeasureHystorySize Integer32,
ippmMeasureStorageType StorageType, ippmMeasureStorageType StorageType,
ippmMeasureStatus RowStatus ippmMeasureStatus RowStatus
} }
ippmMeasureOwner OBJECT-TYPE ippmMeasureOwner OBJECT-TYPE
SYNTAX OwnerString SYNTAX OwnerString
MAX-ACCESS read-only MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The owner who has configured this entry." "The owner who has configured this entry."
DEFVAL { "acme" } DEFVAL { "acme" }
::= { ippmMeasureEntry 1 } ::= { ippmMeasureEntry 1 }
ippmMeasureIndex OBJECT-TYPE ippmMeasureIndex OBJECT-TYPE
SYNTAX Integer32 (1.. 65535) SYNTAX Integer32 (1.. 65535)
MAX-ACCESS read-only MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The owner index of the measure. The value is managed by "The owner index of the measure. The value is managed by the owner."
the owner."
::= { ippmMeasureEntry 2 } ::= { ippmMeasureEntry 2 }
ippmMeasureName OBJECT-TYPE ippmMeasureName OBJECT-TYPE
SYNTAX DisplayString SYNTAX SnmpAdminString
MAX-ACCESS read-only MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The name of the instance of the metric. It illustrates "The name of the instance of the metric. It illustrates the specificity of the metric
the specificity of the metric and includes the metric and includes the metric and the typeP.
and the typeP.
example: IP-port-HTTP-connectivity" example: IP-port-HTTP-connectivity"
::= { ippmMeasureEntry 3 } ::= { ippmMeasureEntry 3 }
ippmMeasureMetrics OBJECT-TYPE ippmMeasureMetrics OBJECT-TYPE
SYNTAX IppmStandardMetrics SYNTAX IppmStandardMetrics
MAX-ACCESS read-only MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Defines the metrics to compute within this measure. A "Defines the metrics to compute within this measure. A measure may be configured for
measure may be configured for the result of different the result of different metric singletons to be archived in the ippmHistoryTable. The
metric singletons to be archived in the ippmMetricsIndex of the created result has the value of the bit index of the
ippmHistoryTable. The ippmMetricIndex of the created corresponding ippmMeasureMetrics as explained above in the IppmMetricsEntry
result has the value of the bit index of the definition.
corresponding ippmMeasureMetrics as explained above in
the ippmMetricIndex definition.
Example: Example:
A measure asking for One-way-Delay(6) and One-way- A measure asking for One-way-Delay(6) and One-way-Packet-Loss(12) generated a flow of
Packet-Loss(12) generated a flow of singletons which are singletons which are logged in the ippmHistoryTable. The singletons created for the
logged in the ippmHistoryTable. The singletons created One-way-Delay measure have a value of IppmMetricsIndex of 6 while the created
for the One-way-Delay measure have a value of singletons for the One-way-Packet-Loss measure have a value of IppmMetricsIndex of
ippmMetricIndex of 6 while the created singletons for 12."
the One-way-Packet-Loss measure have a value of
ippmMetricIndex of 12."
DEFVAL { { one-way-Delay, one-way-Packet-Loss } } DEFVAL { { one-way-Delay, one-way-Packet-Loss } }
::= { ippmMeasureEntry 4 } ::= { ippmMeasureEntry 4 }
ippmMeasureBeginTime OBJECT-TYPE ippmMeasureBeginTime OBJECT-TYPE
SYNTAX GMTDateAndTime SYNTAX GMTTimeStamp
MAX-ACCESS read-only MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Specifies the time at which the measure starts." "Specifies the time at which the measure starts."
::= { ippmMeasureEntry 5 } ::= { ippmMeasureEntry 5 }
ippmMeasureClockPeriodUnit OBJECT-TYPE ippmMeasureClockPeriodUnit OBJECT-TYPE
SYNTAX TimeUnit SYNTAX TimeUnit
MAX-ACCESS read-only MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Specifies the unit of the measure period." "Specifies the unit of the measure period."
DEFVAL { second } DEFVAL { second }
::= { ippmMeasureEntry 6 } ::= { ippmMeasureEntry 6 }
ippmMeasureClockPeriod OBJECT-TYPE ippmMeasureClockPeriod OBJECT-TYPE
SYNTAX Integer32 SYNTAX Integer32
MAX-ACCESS read-only MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Specifies the amount of time between 2 measurement "Specifies the amount of time between 2 measurement action intervals. The action is
action intervals. The action is specific to the semantic specific to the semantic of the measure.
of the measure.
Network metrics: Network metrics:
The ippmNetworkMeasureClockPattern transforms the flow The ippmNetworkMeasureClockPattern transforms the flow of periodical instants as a
of periodical instants as a flow of unpredictable flow of unpredictable instants of measurement packet emission.
instants of measurement packet emission.
As the source and the sink share the definition of the As the source and the sink share the definition of the clock of the measure, as the
clock of the measure, as the sending timestamp is part sending timestamp is part of the measurement packet, the sink have the information to
of the measurement packet, the sink have the information verify that the stream of packets generated by the source respects the clock law.
to verify that the stream of packets generated by the
source respects the clock law.
Aggregated metrics: Aggregated metrics:
They are performed periodically on a sequence of results They are performed periodically on a sequence of results of other measures. The period
of other measures. The period corresponds to the corresponds to the interval between two successive computations of the metric. The
interval between two successive computations of the value of ippmHistoryTimestamp result of a aggregated metric computed corresponds to
metric. The ippmHistoryTimeMark result value of the the value of the ippmHistoryTimestamp of the last metric result of the sequence used
metric computed corresponds to the ippmHistoryTimeMark in to compute the aggregated metric."
value of the last metric result of the sequence used in
the computation."
DEFVAL { 60 } DEFVAL { 60 }
::= { ippmMeasureEntry 7 } ::= { ippmMeasureEntry 7 }
ippmMeasureDurationUnit OBJECT-TYPE ippmMeasureDurationUnit OBJECT-TYPE
SYNTAX TimeUnit SYNTAX TimeUnit
MAX-ACCESS read-only MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Specifies the unit of the measure duration." "Specifies the unit of the measure duration."
DEFVAL { second } DEFVAL { second }
::= { ippmMeasureEntry 8 } ::= { ippmMeasureEntry 8 }
ippmMeasureDuration OBJECT-TYPE ippmMeasureDuration OBJECT-TYPE
SYNTAX Integer32 SYNTAX Integer32
MAX-ACCESS read-only MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Specifies the duration of the measure." "Specifies the duration of the measure."
DEFVAL { 120 } DEFVAL { 120 }
::= { ippmMeasureEntry 9 } ::= { ippmMeasureEntry 9 }
ippmMeasureHystorySize OBJECT-TYPE ippmMeasureHystorySize OBJECT-TYPE
SYNTAX Integer32 SYNTAX Integer32
MAX-ACCESS read-only MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Specifies the maximum number of results saved for each "Specifies the maximum number of results saved for each metric of this measure. The
metric of this measure. The history of each metric is history of each metric is managed as a circular table. The newest result overwrites
managed as a circular table. The newest result the oldest one when the history granted to this metric measure is full.
overwrites the oldest one when the history granted to
this metric measure is full.
The management of the results may be optimized if The management of the results may be optimized if synchronized with the reports steps
synchronized with the reports steps of this measure. of this measure.
" "
DEFVAL { 120 } DEFVAL { 120 }
::= { ippmMeasureEntry 10 } ::= { ippmMeasureEntry 10 }
ippmMeasureStorageType OBJECT-TYPE ippmMeasureStorageType OBJECT-TYPE
SYNTAX StorageType SYNTAX StorageType
MAX-ACCESS read-only MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object defines whether this row and the measure "This object defines whether this row and the measure
controlled by this row are kept in volatile storage and controlled by this row are kept in volatile storage and
lost upon reboot or if this row is backed up by lost upon reboot or if this row is backed up by
non-volatile or permanent storage. non-volatile or permanent storage.
Possible values are: other(1), volatile(2), nonVolatile(3), Possible values are: other(1), volatile(2), nonVolatile(3), permanent(4), readOnly(5)"
permanent(4), readOnly(5)"
DEFVAL { nonVolatile } DEFVAL { nonVolatile }
::= { ippmMeasureEntry 11 } ::= { ippmMeasureEntry 11 }
ippmMeasureStatus OBJECT-TYPE ippmMeasureStatus OBJECT-TYPE
SYNTAX RowStatus SYNTAX RowStatus
MAX-ACCESS read-only MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The status of this table entry. Once the entry status "The status of this table entry. Once the entry status is set to active, the associate
is set to active, the associate entry cannot be entry cannot be modified."
modified."
DEFVAL { createAndGo }
::= { ippmMeasureEntry 12 } ::= { ippmMeasureEntry 12 }
-- --
-- ippmHistoryGroup -- ippmHistoryGroup
-- --
-- --
-- --
-- ippmHistoryTable -- ippmHistoryTable
-- --
skipping to change at page 44, line 8 skipping to change at page 45, line 40
"The table of the results of the measures." "The table of the results of the measures."
::= { ippmHistoryGroup 1 } ::= { ippmHistoryGroup 1 }
ippmHistoryEntry OBJECT-TYPE ippmHistoryEntry OBJECT-TYPE
SYNTAX IppmHistoryEntry SYNTAX IppmHistoryEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An ippmHistoryEntry entry is one of the results of a "An ippmHistoryEntry entry is one of the results of a measure identified by the index
measure identified by the index members ippmMeasureOwner members ippmMeasureOwner and ippmMeasureIndex.
and ippmMeasureIndex.
In the index : In the index :
+ ippmMeasureOwner and ippmMeasureIndex identify + ippmMeasureOwner and ippmMeasureIndex identify the ippmMeasureEntry on
the ippmMeasureEntry on whose behalf this entry was whose behalf this entry was created
created + IppmMetricsIndex identifies the ippmMetricsEntry of the metric to measure
+ ippmMetricIndex identifies the ippmMetricEntry + ippmHistorySqceNdx value is the absolute time when the result of the metric
of the metric to measure was measured.
+ ippmLogTimeMark value is the absolute time
when the result of the metric was measured.
The ippmHistoryTimeMark value is the absolute time when The ippmHistoryTimestamp value is the absolute time when the ippmHistoryValue was
the ippmHistoryValue was performed. performed.
IppmHistoryValue is the value of the metric measured at IppmHistoryValue is the value of the metric measured at the time ippmHistoryTimestamp.
the time ippmHistoryTimeMark.
Example: Example: <TODO provide an example with a stream of one way result for the same
A one way delay measure is created by the entity 'acme' measure>
using the owner index 1 and setting the 6th bit A one way delay measure is created by the entity 'acme' using the owner index 1 and
(corresponding to One-way-Delay) of ippmMeasureMetrics setting the 6th bit (corresponding to One-way-Delay) of ippmMeasureMetrics to 1.
to 1. Consider that the first result of the one way delay measured for acme on the day 15 of
Consider that the result of the one way delay measured June at 8h20mn 10s 50ms is 23. The result is identified as the singleton
for acme on the day 15 of June at 8h20mn 10s 50ms is 23. ippmHistoryValue.acme.1.6.1 and stored with value 23.
The result is identified as the singleton
ippmHistoryValue.acme.1.6.0001000201090200010501000BEBC2
00 and stored with value 23.
Its value may be retrieved using a get- Its value may be retrieved using a get-next(ippmHistoryValue.acme.1.6) which returns
next(ippmHistoryValue.acme.1.6.0001000201090200010501000 (ippmHistoryValue.acme.1.6.1 == 23). The IppmMetricsIndex value of '6' corresponds to
0000000) which returns the 6th metric of ippmMetricsTable which is Type-P-One-way-Delay.
(ippmHistoryValue.acme.1.6.0001000201090200010501000BEBC
200 == 23). The ippmMetricIndex value of '6' corresponds
to the 6th metric of ippmMetricTable which is Type-P-
One-way-Delay.
" "
INDEX { ippmMeasureOwner, ippmMeasureIndex, ippmMetricIndex, INDEX { ippmMeasureOwner, ippmMeasureIndex, ippmMetricsIndex,
ippmHistoryTimeMark } ippmHistorySqceNdx }
::= { ippmHistoryTable 1 } ::= { ippmHistoryTable 1 }
IppmHistoryEntry ::= IppmHistoryEntry ::=
SEQUENCE { SEQUENCE {
ippmHistoryTimeMark GMTDateAndTime,
ippmHistorySqceNdx Integer32, ippmHistorySqceNdx Integer32,
ippmHistoryTimestamp GMTTimeStamp,
ippmHistoryValue Integer32 ippmHistoryValue Integer32
} }
ippmHistoryTimeMark OBJECT-TYPE
SYNTAX GMTDateAndTime
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The instant of the measure of the result."
::= { ippmHistoryEntry 1 }
ippmHistorySqceNdx OBJECT-TYPE ippmHistorySqceNdx OBJECT-TYPE
SYNTAX Integer32 SYNTAX Integer32 (0..65536)
MAX-ACCESS read-only MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
" ippmHistorySqceNdx is the sequence index of the " ippmHistorySqceNdx is the sequence index of the measurement
measurement results of the measure of a metric. results of the measure of a metric.
Network metrics: Network metrics:
It's the sequence index of a measurement packet. Typically, it It's the sequence index of a measurement packet. Typically, it identifies the order of
identifies the order of the packet in the stream of packets sends by the packet in the stream of packets sends by the source.
the source.
Aggregated metrics: Aggregated metrics:
It is the sequence index of the aggregated metric results It is the sequence index of the aggregated metric results computed.
computed.
" "
::= { ippmHistoryEntry 1 }
ippmHistoryTimestamp OBJECT-TYPE
SYNTAX GMTTimeStamp
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The instant of the measure of the result."
::= { ippmHistoryEntry 2 } ::= { ippmHistoryEntry 2 }
ippmHistoryValue OBJECT-TYPE ippmHistoryValue OBJECT-TYPE
SYNTAX Integer32 SYNTAX Integer32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The value of the measure." "The value of the measure."
::= { ippmHistoryEntry 3 } ::= { ippmHistoryEntry 3 }
skipping to change at page 46, line 11 skipping to change at page 47, line 26
-- --
-- ippmNetworkMeasureTable -- ippmNetworkMeasureTable
-- --
-- --
ippmNetworkMeasureTable OBJECT-TYPE ippmNetworkMeasureTable OBJECT-TYPE
SYNTAX SEQUENCE OF IppmNetworkMeasureEntry SYNTAX SEQUENCE OF IppmNetworkMeasureEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A entry is a measure which performs network measures "A entry is a measure which performs network measures and provides a flow of results.
and provides a flow of results.
This table extends the ippmMeasureTable. A network This table extends the ippmMeasureTable. A network measure is a specific measure.
measure is a specific measure.
It performs several metric measurements per packet It performs several metric measurements per packet exchange. Each step of a measure
exchange. Each step of a measure produces a singleton produces a singleton result per metric. The time of the measure and the value of the
result per metric. The time of the measure and the value metric are saved in the ippmHistoryTable."
of the metric are saved in the ippmHistoryTable."
::= { ippmNetworkMeasureGroup 1 } ::= { ippmNetworkMeasureGroup 1 }
ippmNetworkMeasureEntry OBJECT-TYPE ippmNetworkMeasureEntry OBJECT-TYPE
SYNTAX IppmNetworkMeasureEntry SYNTAX IppmNetworkMeasureEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
" Typically the configuration operation sets both the " Typically the configuration operation sets both the values of the new
values of the new ippmMeasureEntry and of the new ippmMeasureEntry and of the new IppmNetworkMeasureEntry.
IppmNetworkMeasureEntry.
IppmNetworkMeasureTable is mandatory. IppmNetworkMeasureTable is mandatory.
IppmNetworkMeasureTable content is read only. It means IppmNetworkMeasureTable content is read only. It means that the measurement software
that the measurement software handles the table handles the table internally. The setup of network is not permitted through the IPPM
internally. REPORTING MIB. OWAP provides a setup protocol to enable and teardown networks
measures.
The ippmMeasureMetrics is set to a list of metrics to be The ippmMeasureMetrics is set to a list of metrics to be computed from the same raw
computed from the same raw packet exchange. Each step of packet exchange. Each step of measurement delivers a singleton per chosen metric.
measurement delivers a singleton per chosen metric. Results are timestamped and saved in the ippmHistoryTable.
Results are timestamped and saved in the
ippmHistoryTable." The ippmNetworkMeasureTable typical usage consists is providing network measure
indexes to permits aggregated measure to perform aggregation on the results of network
measures.
An obvious usage of the ippmNetworkMeasureTable consists in the verification of the
network measures states."
INDEX { ippmMeasureOwner, ippmMeasureIndex } INDEX { ippmMeasureOwner, ippmMeasureIndex }
::= { ippmNetworkMeasureTable 1 } ::= { ippmNetworkMeasureTable 1 }
IppmNetworkMeasureEntry ::= IppmNetworkMeasureEntry ::=
SEQUENCE { SEQUENCE {
ippmNetworkMeasureSrcTypeP TypeP, ippmNetworkMeasureSrcTypeP TypeP,
ippmNetworkMeasureSrc OCTET STRING, ippmNetworkMeasureSrc OCTET STRING,
ippmNetworkMeasureDstTypeP TypeP, ippmNetworkMeasureDstTypeP TypeP,
ippmNetworkMeasureDst OCTET STRING, ippmNetworkMeasureDst OCTET STRING,
ippmNetworkMeasureClockPattern OCTET STRING, ippmNetworkMeasureClockPattern OCTET STRING,
ippmNetworkMeasureTimeoutDelay Integer32, ippmNetworkMeasureTimeoutDelay Integer32,
ippmNetworkMeasureL3PacketSize Integer32, ippmNetworkMeasureL3PacketSize Integer32,
ippmNetworkMeasureDataPattern OCTET STRING ippmNetworkMeasureDataPattern OCTET STRING
} }
ippmNetworkMeasureSrcTypeP OBJECT-TYPE ippmNetworkMeasureSrcTypeP OBJECT-TYPE
SYNTAX TypeP SYNTAX TypeP
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Defines the type P of the source address of the packets "Defines the type P of the source address of the packets sent by the measure."
sent by the measure."
DEFVAL { '04000080001000'H } -- ->ip: 4.0.0.8.0.1.0 DEFVAL { '04000080001000'H } -- ->ip: 4.0.0.8.0.1.0
::= { ippmNetworkMeasureEntry 1 } ::= { ippmNetworkMeasureEntry 1 }
ippmNetworkMeasureSrc OBJECT-TYPE ippmNetworkMeasureSrc OBJECT-TYPE
SYNTAX OCTET STRING SYNTAX OCTET STRING
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Specifies the address of the source of the measure. "Specifies the address of the source of the measure.
It is represented as an octet string with specific It is represented as an octet string with specific semantics and length as identified
semantics and length as identified by the by the ippmNetworkMeasureSrcTypeP.
ippmNetworkMeasureSrcTypeP.
For example, if the ippmNetworkMeasureSrcTypeP indicates For example, if the ippmNetworkMeasureSrcTypeP indicates an encapsulation of 'ip',
an encapsulation of 'ip', this object length is 4, this object length is 4, followed by the 4 octets of the IP address, in network byte
followed by the 4 octets of the IP address, in network order."
byte order."
DEFVAL { '04C0210415'H } -- -> ip: 192.33.4.21 DEFVAL { '04C0210415'H } -- -> ip: 192.33.4.21
::= { ippmNetworkMeasureEntry 2} ::= { ippmNetworkMeasureEntry 2}
ippmNetworkMeasureDstTypeP OBJECT-TYPE ippmNetworkMeasureDstTypeP OBJECT-TYPE
SYNTAX TypeP SYNTAX TypeP
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Defines the type P of the destination address of the "Defines the type P of the destination address of the packets sent
packets sent by the measure." by the measure."
DEFVAL { '04000080001000'H } -- ->ip: 4.0.0.8.0.1.0 DEFVAL { '04000080001000'H } -- ->ip: 4.0.0.8.0.1.0
::= { ippmNetworkMeasureEntry 3 } ::= { ippmNetworkMeasureEntry 3 }
ippmNetworkMeasureDst OBJECT-TYPE ippmNetworkMeasureDst OBJECT-TYPE
SYNTAX OCTET STRING SYNTAX OCTET STRING
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Specifies the address of the destination of the "Specifies the address of the destination of the measure.
measure.
It is represented as an octet string with specific It is represented as an octet string with specific semantics and length as identified
semantics and length as identified by the by the ippmNetworkMeasureDstTypeP.
ippmNetworkMeasureDstTypeP.
For example, if the ippmNetworkMeasureDstTypeP indicates For example, if the ippmNetworkMeasureDstTypeP indicates an encapsulation of 'ip',
an encapsulation of 'ip', this object length is 4, this object length is 4, followed by the 4 octets of the IP address, in network byte
followed by the 4 octets of the IP address, in network order."
byte order."
DEFVAL { '04C0220414'H } -- -> ip: 192.34.4.20 DEFVAL { '04C0220414'H } -- -> ip: 192.34.4.20
::= { ippmNetworkMeasureEntry 4 } ::= { ippmNetworkMeasureEntry 4 }
ippmNetworkMeasureClockPattern OBJECT-TYPE ippmNetworkMeasureClockPattern OBJECT-TYPE
SYNTAX OCTET STRING SYNTAX OCTET STRING
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This cyclic clock shapes the profile of the instants of "This cyclic clock shapes the profile of the instants of measurement action provided
measurement action provided by ippmMeasureClockPeriod by ippmMeasureClockPeriod according to an arbitrary distribution law. The clock
according to an arbitrary distribution law. The clock resolution is ippmMeasureClockPeriod. The bits of the clock pattern set to the value 1
resolution is ippmMeasureClockPeriod. The bits of the determine the valid instants of measurement action. A measure is to be processed if
clock pattern set to the value 1 determine the valid and only if the current bit value is 1.
instants of measurement action. A measure is to be This pseudo-random clock pattern allows the configuration by the NMS of numerous kind
processed if and only if the current bit value is 1. of time sampling law such as periodic, pseudo random or Poisson.
This pseudo-random clock pattern allows the
configuration by the NMS of numerous kind of time
sampling law such as periodic, pseudo random or Poisson.
The source of the measure sends the stream of The source of the measure sends the stream of measurement packets synchronously with
measurement packets synchronously with the stream of the stream of instants selected by the clock pattern sampling.
instants selected by the clock pattern sampling.
" "
DEFVAL { 11111111} -- 100% periodic DEFVAL { 11111111} -- 100% periodic
::= { ippmNetworkMeasureEntry 5 } ::= { ippmNetworkMeasureEntry 5 }
ippmNetworkMeasureTimeoutDelay OBJECT-TYPE ippmNetworkMeasureTimeoutDelay OBJECT-TYPE
SYNTAX Integer32 SYNTAX Integer32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
-- UNITS "Milliseconds" -- UNITS "Milliseconds"
DESCRIPTION DESCRIPTION
"Specifies the delay after which the packet is "Specifies the delay after which the packet is considered lost by
considered lost by the sink." the sink."
DEFVAL { 1 } DEFVAL { 1 }
::= { ippmNetworkMeasureEntry 6 } ::= { ippmNetworkMeasureEntry 6 }
ippmNetworkMeasureL3PacketSize OBJECT-TYPE ippmNetworkMeasureL3PacketSize OBJECT-TYPE
SYNTAX Integer32 SYNTAX Integer32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Specifies the size of the packets sent at the last "Specifies the size of the packets sent at the last network layer in regards to the
network layer in regards to the TypeP definition." TypeP definition."
DEFVAL { 64 } DEFVAL { 64 }
::= { ippmNetworkMeasureEntry 7 } ::= { ippmNetworkMeasureEntry 7 }
ippmNetworkMeasureDataPattern OBJECT-TYPE ippmNetworkMeasureDataPattern OBJECT-TYPE
SYNTAX OCTET STRING SYNTAX OCTET STRING
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The current field defines the round robin pattern used "The current field defines the round robin pattern used to fill the packet."
to fill the packet."
DEFVAL { 'FF'H } DEFVAL { 'FF'H }
::= { ippmNetworkMeasureEntry 8 } ::= { ippmNetworkMeasureEntry 8 }
-- --
-- --
-- ippmAggregatedMeasureGroup -- ippmAggregatedMeasureGroup
-- --
-- --
-- --
-- --
-- ippmAggregatedMeasureTable -- ippmAggregatedMeasureTable
-- --
-- --
ippmAggregatedMeasureTable OBJECT-TYPE ippmAggregatedMeasureTable OBJECT-TYPE
SYNTAX SEQUENCE OF IppmAggregatedMeasureEntry SYNTAX SEQUENCE OF IppmAggregatedMeasureEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
" This table extends the ippmMeasureTable. " This table extends the ippmMeasureTable.
An aggregated measure summarizes the results of previous An aggregated measure summarizes the results of previous network or aggregated
network or aggregated measures. The results may be saved measures. The results may be saved in the ippmHistoryTable.
in the ippmHistoryTable.
Each step of the calculation for the measure produces a Each step of the calculation for the measure produces a singleton result per metric."
singleton result per metric."
::= { ippmAggregatedMeasureGroup 1 } ::= { ippmAggregatedMeasureGroup 1 }
ippmAggregatedMeasureEntry OBJECT-TYPE ippmAggregatedMeasureEntry OBJECT-TYPE
SYNTAX IppmAggregatedMeasureEntry SYNTAX IppmAggregatedMeasureEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Typically the configuration operation sets both the values of "Typically the configuration operation sets both the values of the new
the new ippmMeasureEntry and of the new ippmMeasureEntry and of the new IppmAggregatedMeasureEntry.
IppmAggregatedMeasureEntry.
ippmAggregatedMeasureTable is mandatory. ippmAggregatedMeasureTable is mandatory.
ippmAggregatedMeasureTable content is read only. It means that ippmAggregatedMeasureTable content is read only. It means that the measure software
the measure software handles the table internally. handles the table internally.
The ippmMeasureMetrics defines the metric to compute. The ippmMeasureMetrics defines the metric to compute.
The results of the measure to summarize are identified The results of the measure to summarize are identified by:
by:
+ ippmAggregatedMeasureHistoryOwner, + ippmAggregatedMeasureHistoryOwner,
+ ippmAggregatedMeasureHistoryOwnerIndex and + ippmAggregatedMeasureHistoryOwnerIndex and
+ ippmAggregatedMeasureHistoryMetric + ippmAggregatedMeasureHistoryMetric
The aggregated task starts at ippmMeasureBeginTime and ends The aggregated task starts at ippmMeasureBeginTime and ends after ippmMeasureDuration.
after ippmMeasureDuration. An aggregated result is performed and An aggregated result is performed and saved in the ippmHistoryTable for each
saved in the ippmHistoryTable for each ippmMeasureClockPeriod ippmMeasureClockPeriod tick.
tick.
" "
INDEX { ippmMeasureOwner, ippmMeasureIndex } INDEX { ippmMeasureOwner, ippmMeasureIndex }
::= { ippmAggregatedMeasureTable 1 } ::= { ippmAggregatedMeasureTable 1 }
IppmAggregatedMeasureEntry ::= IppmAggregatedMeasureEntry ::=
SEQUENCE { SEQUENCE {
ippmAggregatedMeasureHistoryOwner OwnerString, ippmAggregatedMeasureHistoryOwner OwnerString,
ippmAggregatedMeasureHistoryOwnerIndex Integer32, ippmAggregatedMeasureHistoryOwnerIndex Integer32,
ippmAggregatedMeasureHistoryMetric Integer32 ippmAggregatedMeasureHistoryMetric Integer32,
ippmAggregatedMeasureStatus RowStatus
} }
ippmAggregatedMeasureHistoryOwner OBJECT-TYPE ippmAggregatedMeasureHistoryOwner OBJECT-TYPE
SYNTAX OwnerString SYNTAX OwnerString
MAX-ACCESS read-only MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The owner of the measure to summarize. " "The owner of the measure to summarize. "
::= { ippmAggregatedMeasureEntry 1 } ::= { ippmAggregatedMeasureEntry 1 }
ippmAggregatedMeasureHistoryOwnerIndex OBJECT-TYPE ippmAggregatedMeasureHistoryOwnerIndex OBJECT-TYPE
SYNTAX Integer32 (1.. 65535) SYNTAX Integer32 (1.. 65535)
MAX-ACCESS read-only MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The owner index of the measure to summarize. " "The owner index of the measure to summarize. "
::= { ippmAggregatedMeasureEntry 2 } ::= { ippmAggregatedMeasureEntry 2 }
ippmAggregatedMeasureHistoryMetric OBJECT-TYPE ippmAggregatedMeasureHistoryMetric OBJECT-TYPE
SYNTAX Integer32 SYNTAX Integer32
MAX-ACCESS read-only MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The metric of the measure to summarize. " "The metric of the measure to summarize. "
::= { ippmAggregatedMeasureEntry 3 } ::= { ippmAggregatedMeasureEntry 3 }
ippmAggregatedMeasureStatus OBJECT-TYPE
SYNTAX RowStatus
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The status of this table entry. Once the entry status is set to active, the associate
entry cannot be modified."
::= { ippmAggregatedMeasureEntry 4 }
-- --
-- ippmReportGroup -- ippmReportGroup
-- --
-- --
-- --
-- ippmReportSetupTable -- ippmReportSetupTable
-- --
-- --
ippmReportSetupTable OBJECT-TYPE ippmReportSetupTable OBJECT-TYPE
SYNTAX SEQUENCE OF IppmReportSetupEntry SYNTAX SEQUENCE OF IppmReportSetupEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The ippmReportSetupTable is a list of definition of reports. It "The ippmReportSetupTable is a list of definition of reports. It defines the results
defines the results of a network or aggregated measures that are to of a network or aggregated measures that are to be reported. A report is saved in the
be reported. A report is saved in the ippmReportTable, or sent to an ippmReportTable, or sent to an application using a SNMP Trap, a SNMP inform PDU, an
application using a SNMP Trap, a SNMP inform PDU, an email or a SMS. email or a SMS. The reporting task is not intended to be a batch action processed at
The reporting task is not intended to be a batch action processed at the end of the measure. It is coupled with threshold detections and event filtering to
the end of the measure. It is coupled with threshold detections and deliver application level events and data, while preserving scalability.
event filtering to deliver application level events and data, while
preserving scalability.
It extends the definition of a measure: the definition of a measure It extends the definition of a measure: the definition of a measure may include the
may include the definition of a report." definition of a report."
::= { ippmReportGroup 1 } ::= { ippmReportGroup 1 }
ippmReportSetupEntry OBJECT-TYPE ippmReportSetupEntry OBJECT-TYPE
SYNTAX IppmReportSetupEntry SYNTAX IppmReportSetupEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The report applies to the results of the measure which is extended "The report applies to the results of the measure which is extended by the current
by the current report definition. report definition.
Typically the creation of a report sets both the values of the new Typically the creation of a report sets both the values of the new measure and those
measure and those of the new IppmReportSetupEntry. of the new IppmReportSetupEntry.
The ippmReportSetupDefinition describes the data and the events to The ippmReportSetupDefinition describes the data and the events to include in the
include in the report. The definition consists in a list of tasks to report. The definition consists in a list of tasks to perform on the results of the
perform on the results of the measure." measure."
INDEX { ippmMeasureOwner, ippmMeasureIndex } INDEX { ippmMeasureOwner, ippmMeasureIndex }
::= { ippmReportSetupTable 1 } ::= { ippmReportSetupTable 1 }
IppmReportSetupEntry ::= IppmReportSetupEntry ::=
SEQUENCE { SEQUENCE {
ippmReportSetupDefinition IppmReportDefinition, ippmReportSetupDefinition IppmReportDefinition,
ippmReportSetupMetricThreshold Integer32, ippmReportSetupMetricThreshold Integer32,
ippmReportSetupEventsDurationThreshold Integer32, ippmReportSetupEventsDurationThreshold Integer32,
ippmReportSetupNMS SnmpAdminString,
ippmReportSetupNMS DisplayString ippmReportSetupStatus RowStatus
} }
ippmReportSetupDefinition OBJECT-TYPE ippmReportSetupDefinition OBJECT-TYPE
SYNTAX IppmReportDefinition SYNTAX IppmReportDefinition
MAX-ACCESS read-only MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The description of the events and actions that are used in the "The description of the events and actions that are used in the definition of
definition of the report. the report.
Send the report using the type of message selected by the bits 8 Send the report using the type of message selected by the bits 8 to 12. The
to 12. The report consists of the results of the measure which have report consists of the results of the measure which have been saved in the
been saved in the ippmReportTable. If the onEventSendReport(7) bit is ippmReportTable. If the onEventSendReport(7) bit is unset, the report is not saved.
unset, the report is not saved.
The message sent is a notification defined in the The message sent is a notification defined in the ippmNotifications node. The
ippmNotifications node. The notification sent depends on the step of notification sent depends on the step of the measure:
the measure:
+ Singleton events are sent using the notification + Singleton events are sent using the notification ippmSingletonAlarm
ippmSingletonAlarm + Exceeded events durations are sent using the notification
+ Exceeded events durations are sent using the ippmEventsDurationExceededAlarm
notification ippmEventsDurationExceededAlarm + A report of a cycle of measure is sent using the notification
+ A report of a cycle of measure is sent using the ippmCycleOfMeasureReport
notification ippmCycleOfMeasureReport + A report of a complete measure is sent using the notification
+ A report of a complete measure is sent using the ippmCompletedMeasureReport
notification ippmCompletedMeasureReport
Example 1: Example 1:
The setup of an alarm to be sent to the owner in a SNMP Trap The setup of an alarm to be sent to the owner in a SNMP Trap each time the
each time the staircase crosses the metric threshold value of 5: staircase crosses the metric threshold value of 5:
ippmReportSetupMetricThreshold 5 ippmReportSetupMetricThreshold 5
ippmReportSetupDefinition { ippmReportSetupDefinition {
onSingleton(1), onSingleton(1),
reportOnlyUptoDownMetricResults(4), reportOnlyUptoDownMetricResults(4),
inSNMPTrapPDU(8) inSNMPTrapPDU(8)
} }
Example 2: Example 2:
The setup of a report to be sent to the owner in a SNMP The setup of a report to be sent to the owner in a SNMP informRequestPDU per
informRequestPDU per measure cycle. It reports the staircase values measure cycle. It reports the staircase values corresponding to a metric threshold of
corresponding to a metric threshold of 5: 5:
ippmReportSetupMetricThreshold 5 ippmReportSetupMetricThreshold 5
ippmReportSetupDefinition { ippmReportSetupDefinition {
onMeasureCycle(2), onMeasureCycle(2),
reportOnlyUptoDownMetricResults(4), reportOnlyUptoDownMetricResults(4),
inInformRequestPDU(10), inInformRequestPDU(10),
clearHistory(13) clearHistory(13)
} }
Default report: Default report:
The default report provides the control protocol with an The default report provides the control protocol with an implicit mechanism
implicit mechanism to forward the result of a cycle of measure to the to forward the result of a cycle of measure to the owner of the measure while deleting
owner of the measure while deleting the results from the the results from the ippmHistoryTable on reception of the response to the
ippmHistoryTable on reception of the response to the InformRequestPDU InformRequestPDU :
:
ippmReportSetupDefinition { ippmReportSetupDefinition {
onMeasureCycle(2), onMeasureCycle(2),
inInformRequestPDU(10), inInformRequestPDU(10),
clearHistory(13) clearHistory(13)
} }
" "
DEFVAL { { onMeasureCycle, inInformRequestPDU, clearHistory } } DEFVAL { { onMeasureCycle, inInformRequestPDU, clearHistory } } ::= {
::= { ippmReportSetupEntry 1 } ippmReportSetupEntry 1 }
ippmReportSetupMetricThreshold OBJECT-TYPE ippmReportSetupMetricThreshold OBJECT-TYPE
SYNTAX Integer32 SYNTAX Integer32
MAX-ACCESS read-only MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An event is generated when the result of the measure exceeds "An event is generated when the result of the measure exceeds the value of
the value of ippmReportSetupMetricThreshold. ippmReportSetupMetricThreshold.
The threshold has the same unit as the metric. The metric unit The threshold has the same unit as the metric. The metric unit is recorded in
is recorded in the object ippmMetricsUnit of this metric entry in the the object ippmMetricUnit of this metric entry in the ippmMetricTable.
ippmMetricTable.
" "
::= { ippmReportSetupEntry 2 } ::= { ippmReportSetupEntry 2 }
ippmReportSetupEventsDurationThreshold OBJECT-TYPE ippmReportSetupEventsDurationThreshold OBJECT-TYPE
SYNTAX Integer32 SYNTAX Integer32
UNITS "Seconds" UNITS "Seconds"
MAX-ACCESS read-only MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An event is generated when the duration of a series of results, "An event is generated when the duration of a series of results, which are
which are continuously over the metric threshold, cross over the continuously over the metric threshold, cross over the duration of the
duration of the ippmReportSetupEventsDurationThreshold. ippmReportSetupEventsDurationThreshold.
" "
DEFVAL { 15 } DEFVAL { 15 }
::= { ippmReportSetupEntry 3 } ::= { ippmReportSetupEntry 3 }
ippmReportSetupNMS OBJECT-TYPE ippmReportSetupNMS OBJECT-TYPE
SYNTAX DisplayString SYNTAX SnmpAdminString
MAX-ACCESS read-only MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The recipient of the report may be provided in the setup. By "The recipient of the report may be provided in the setup. By default the
default the recipient of the report is the owner of the measure. Its recipient of the report is the owner of the measure. Its addresses are recorded in the
addresses are recorded in the ippmOwnersTable. ippmOwnersTable.
The type of ippmReportSetupNMS is not InetAddress because the report may be sent using
SMS or fax.
" "
::= { ippmReportSetupEntry 4 } ::= { ippmReportSetupEntry 4 }
ippmReportSetupStatus OBJECT-TYPE
SYNTAX RowStatus
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The status of this table entry. "
::= { ippmReportSetupEntry 5 }
-- --
-- ippmReportTable -- ippmReportTable
-- --
ippmReportTable OBJECT-TYPE ippmReportTable OBJECT-TYPE
SYNTAX SEQUENCE OF IppmReportEntry SYNTAX SEQUENCE OF IppmReportEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The ippmReportTable logs the results of the reports. "The ippmReportTable logs the results of the reports. The results
The results consist of a subset of the results of a measure as consist of a subset of the results of a measure as described in the report definition.
described in the report definition. The activation of an up and down The activation of an up and down filtering in the report definition limits the results
filtering in the report definition limits the results logged to those logged to those corresponding to major events. Otherwise, the ippmReportTable is
corresponding to major events. Otherwise, the ippmReportTable is
identical to the ippmHistoryTable. identical to the ippmHistoryTable.
" "
::= { ippmReportGroup 2 } ::= { ippmReportGroup 2 }
ippmReportEntry OBJECT-TYPE ippmReportEntry OBJECT-TYPE
SYNTAX IppmReportEntry SYNTAX IppmReportEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A report is a list of results of a measure. This sample is "A report is a list of results of a measure. This sample is associated with the
associated with the ippmReportSetupEntry which has set up the report. ippmReportSetupEntry which has set up the report. An ippmReportEntry entry is one of
An ippmReportEntry entry is one of the results of a measure to the results of a measure to report. The measure and the report definition are
report. The measure and the report definition are identified by the identified by the index members ippmMeasureOwner and ippmMeasureIndex.
index members ippmMeasureOwner and ippmMeasureIndex.
In the index : In the index :
+ ippmMeasureOwner and ippmMeasureIndex identify the + ippmMeasureOwner and ippmMeasureIndex identify the ippmMeasureEntry and the
ippmMeasureEntry and the ippmReportSetupEntry on whose behalf ippmReportSetupEntry on whose behalf this report was created
this report was created
+ ippmMetricIndex identifies the ippmMetricEntry of the metric + IppmMetricsIndex identifies the ippmMetricsEntry of the metric measured
measured + ippmHistorySqceNdx value is the absolute time when the result of the metric was
+ ippmReportTimeMark value is the absolute time when the value computed.
of the metric was measured.
The ippmReportTimeMark value is the absolute time when the The ippmReportTimestamp value is the absolute time when the ippmHistoryValue
ippmHistoryValue was performed. was performed.
IppmHistoryValue is the value of the metric measured at the time IppmHistoryValue is the value of the metric measured at the timef
ippmReportTimeMark. ippmReportTimestamp.
" "
INDEX { ippmMeasureOwner, ippmMeasureIndex, ippmMetricIndex, INDEX { ippmMeasureOwner, ippmMeasureIndex, ippmMetricsIndex,
ippmReportTimeMark } ippmReportSqceNdx}
::= { ippmReportTable 1 } ::= { ippmReportTable 1 }
IppmReportEntry ::= IppmReportEntry ::=
SEQUENCE { SEQUENCE {
ippmReportTimeMark GMTDateAndTime, ippmReportSqceNdx Integer32,
ippmReportTimestamp GMTTimeStamp,
ippmReportValue Integer32 ippmReportValue Integer32
} }
ippmReportTimeMark OBJECT-TYPE ippmReportSqceNdx OBJECT-TYPE
SYNTAX GMTDateAndTime SYNTAX Integer32 (1..65536)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The instant of the measure of the result."
" ippmReportSqceNdx is the sequence index of the measurement
results of the measure of a metric.
Network metrics:
It's the sequence index of a measurement packet. Typically, it identifies the order of
the packet in the stream of packets sends by the source.
Aggregated metrics:
It is the sequence index of the aggregated metric results computed.
"
::= { ippmReportEntry 1 } ::= { ippmReportEntry 1 }
ippmReportTimestamp OBJECT-TYPE
SYNTAX GMTTimeStamp
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The instant of the measure of the result."
::= { ippmReportEntry 2 }
ippmReportValue OBJECT-TYPE ippmReportValue OBJECT-TYPE
SYNTAX Integer32 SYNTAX Integer32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The value." "The value."
::= { ippmReportEntry 2 } ::= { ippmReportEntry 3 }
-- --
-- ippmNotifications -- ippmNotifications
-- --
ippmSingletonAlarm NOTIFICATION-TYPE ippmSingletonAlarm NOTIFICATION-TYPE
OBJECTS { OBJECTS {
ippmReportSetupDefinition, ippmReportSetupDefinition,
ippmReportSetupMetricThreshold, ippmReportSetupMetricThreshold,
ippmMetricUnit, ippmMetricUnit,
ippmHistoryValue ippmHistoryValue
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A notification sent because 2 contiguous results are on "A notification sent because 2 contiguous results are on opposite sides of the metric
opposite sides of the metric threshold value. threshold value.
The index of the included ippmReportSetupMetricThreshold object identifies the
The index of the included ippmReportSetupMetricThreshold ippmMeasureEntry and the ippmResultSetupEntry that specified the threshold.
object identifies the ippmMeasureEntry and the
ippmResultSetupEntry that specified the threshold.
The notification contains the instances of the The notification contains the instances of the ippmReportValue object that exceeded
ippmReportValue object that exceeded the threshold. The the threshold. The ippmHistoryTimestamp of the index identifies the time the event
ippmHistoryTimeMark of the index identifies the time the occurred.
event occurred.
" "
::= { ippmNotifications 1 } ::= { ippmNotifications 1 }
ippmEventsDurationExceededAlarm NOTIFICATION-TYPE ippmEventsDurationExceededAlarm NOTIFICATION-TYPE
OBJECTS { OBJECTS {
ippmReportSetupDefinition, ippmReportSetupDefinition,
ippmReportSetupEventsDurationThreshold, ippmReportSetupEventsDurationThreshold,
ippmMetricUnit, ippmMetricUnit,
ippmHistoryValue ippmHistoryValue
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A notification sent when the duration of contiguous "A notification sent when the duration of contiguous raising
raising ippmReportSetupMetricThreshold exceeds the ippmReportSetupMetricThreshold exceeds the ippmReportSetupEventsDurationThreshold
ippmReportSetupEventsDurationThreshold value. The index value. The index of the included ippmReportSetupDefinition object identifies the
of the included ippmReportSetupDefinition object ippmMeasureEntry and the ippmResultSetupEntry that specified the report.
identifies the ippmMeasureEntry and the
ippmResultSetupEntry that specified the report.
The notification contains the instances of the The notification contains the instances of the ippmReportValue objects saved in the
ippmReportValue objects saved in the ippmReportTable for ippmReportTable for this report. The ippmHistoryTimestamp of the index identifies the
this report. The ippmHistoryTimeMark of the index time theses measures results where performed.
identifies the time theses measures results where
performed.
" "
::= { ippmNotifications 2 } ::= { ippmNotifications 2 }
ippmCycleOfMeasureReport NOTIFICATION-TYPE ippmCycleOfMeasureReport NOTIFICATION-TYPE
OBJECTS { OBJECTS {
ippmReportSetupDefinition, ippmReportSetupDefinition,
ippmMetricUnit, ippmMetricUnit,
ippmHistoryValue ippmHistoryValue
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A notification sent when a measure cycle completes. "A notification sent when a measure cycle completes.
The index of the included ippmReportSetupDefinition The index of the included ippmReportSetupDefinition object identifies the
object identifies the ippmMeasureEntry and the ippmMeasureEntry and the ippmResultSetupEntry that specified the report.
ippmResultSetupEntry that specified the report.
The notification contains the instances of the The notification contains the instances of the ippmReportValue objects saved in the
ippmReportValue objects saved in the ippmReportTable for ippmReportTable for this measure cycle. The ippmHistoryTimestamp of the index
this measure cycle. The ippmHistoryTimeMark of the index
identifies the time the measures where performed. identifies the time the measures where performed.
" "
::= { ippmNotifications 3 } ::= { ippmNotifications 3 }
ippmCompletedMeasureReport NOTIFICATION-TYPE ippmCompletedMeasureReport NOTIFICATION-TYPE
OBJECTS { OBJECTS {
ippmReportSetupDefinition, ippmReportSetupDefinition,
ippmMetricUnit, ippmMetricUnit,
ippmHistoryValue ippmHistoryValue
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A notification sent when a measure completes. "A notification sent when a measure completes.
The index of the included ippmReportSetupDefinition The index of the included ippmReportSetupDefinition object identifies the
object identifies the ippmMeasureEntry and the ippmMeasureEntry and the ippmResultSetupEntry that specified the report.
ippmResultSetupEntry that specified the report.
The notification contains the instances of the The notification contains the instances of the ippmReportValue objects saved in the
ippmReportValue objects saved in the ippmReportTable for ippmReportTable for this measure cycle. The ippmHistoryTimestamp of the index
this measure cycle. The ippmHistoryTimeMark of the index
identifies the time the measures where performed. identifies the time the measures where performed.
" "
::= { ippmNotifications 4 } ::= { ippmNotifications 4 }
-- --
-- Compliance statements -- Compliance statements
-- --
ippmCompliance MODULE-COMPLIANCE ippmCompliance MODULE-COMPLIANCE
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The compliance statement for SNMP entities which "The compliance statement for SNMP entities which implement the IPPM MIB"
implement the IPPM MIB"
MODULE -- this module MODULE -- this module
MANDATORY-GROUPS { ippmSystemGroup, ippmMeasureGroup, MANDATORY-GROUPS { ippmSystemGroup, ippmMeasureGroup,
ippmNetworkMeasureGroup, ippmHistoryGroup } ippmNetworkMeasureGroup, ippmHistoryGroup }
::= { ippmCompliances 1 } ::= { ippmCompliances 1 }
END END
9. Security Considerations 10. Security Considerations
9.1. Privacy 10.1. Privacy
The privacy concerns of network measurement are intrinsically limited The privacy concerns of network measurement are intrinsically limited
by the active measurements. Unlike passive measurements, there can be by the active measurements. Unlike passive measurements, there can be
no release of existing user data. no release of existing user data.
9.2. Measurement aspects 10.2. Measurement aspects
Conducting Internet measurements raises both security and privacy Conducting Internet measurements raises both security and privacy
concerns. This memo does not specify an implementation of the concerns. This memo does not specify an implementation of the
metrics, so it does not directly affect the security of the Internet metrics, so it does not directly affect the security of the Internet
nor of applications that run on the Internet. However, nor of applications that run on the Internet. However,
implementations of these metrics must be mindful of security and implementations of these metrics must be mindful of security and
privacy concerns. privacy concerns.
There are two types of security concerns: potential harm caused by There are two types of security concerns: potential harm caused by
the measurements, and potential harm to the measurements. The the measurements, and potential harm to the measurements. The
skipping to change at page 58, line 45 skipping to change at page 59, line 31
measurements will not reflect actual user traffic. If an attacker measurements will not reflect actual user traffic. If an attacker
injects artificial traffic that is accepted as legitimate, the loss injects artificial traffic that is accepted as legitimate, the loss
rate will be artificially lowered. Therefore, the measurement rate will be artificially lowered. Therefore, the measurement
methodologies SHOULD include appropriate techniques to reduce the methodologies SHOULD include appropriate techniques to reduce the
probability measurement traffic can be distinguished from "normal" probability measurement traffic can be distinguished from "normal"
traffic. traffic.
Authentication techniques, such as digital signatures, may be used Authentication techniques, such as digital signatures, may be used
where appropriate to guard against injected traffic attacks. where appropriate to guard against injected traffic attacks.
9.3. Management aspects 10.3. Management aspects
There are a number of management objects defined in this MIB that There are a number of management objects defined in this MIB that
have a MAX-ACCESS clause of read-write and/or read-only. Such objects have a MAX-ACCESS clause of read-write and/or read-only. Such objects
may be considered sensitive or vulnerable in some network 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.
SNMPv1 by itself is not a secure environment. Even if the network SNMPv1 by itself is not a secure environment. Even if the network
itself is secure (for example by using IPSec), even then, there is no itself is secure (for example by using IPSec), even then, there is no
skipping to change at page 59, line 21 skipping to change at page 60, line 7
features as provided by the SNMPv3 framework. Specifically, the use features as provided by the SNMPv3 framework. Specifically, the use
of the User-based Security Model RFC 2574 [18] and the View-based of the User-based Security Model RFC 2574 [18] and the View-based
Access Control Model RFC 2575 [21] is recommended. Access Control Model RFC 2575 [21] is recommended.
It is then a customer/user responsibility to ensure that the SNMP It is then a customer/user responsibility to ensure that the SNMP
entity giving access to an instance of this MIB, is properly entity giving access to an instance of this MIB, is properly
configured to give access to the objects only to those principals configured to give access to the objects only to those principals
(users) that have legitimate rights to indeed GET or SET (users) that have legitimate rights to indeed GET or SET
(change/create/delete) them. (change/create/delete) them.
10. References 11. Document management
11.1. Open issues
Describe incompatible bit combinations in IPPMreport and granted
metric
Run SMIlint.
Discussion on the management of the history size.
11.2. changes since release 00
Put in a description of the relationship of certain tables,
particularly the measure/network measure/aggregated measure table.
The TC GMTTimeStamp is the common type to define timestamp objects.
ippmHisoryTable index simplified: ippmHistoryTimestamp replaced with
ippmHistorySqceNdx in the index.
The MIB has been compiled using net-snmp.
Snmpadminstring replaces Displaystring.
IP addresses defined using INETaddresstype.
Sharing table is optional to permit the VACM framework to be used.
The description of the network measure table emphases that the set up
of network measure is not permitted using SNMP.
The TC StandardMetrics is removed and replaced with the table
ippmMetricsTable.
The table pointOfMeasureTable is added to describe multiples
interfaces devices
5 tables have been changed to read/create: ippmOwnersTable,
ippmMeasureTable, ippmAggregatedMeasureTable, ippmResultSharingTable,
and ippmReportSetupTable.
IppmHistoryTable and ippmReportTable index reviews:
IppmHistorySqceNdx field added in the ippmHistoryTable.
INDEX modified. IppmHistorySqceNdx replaces IppmHistoryTimemark.
IppmSystem group refurbished:
IppmSystemTimer renamed ippmSystemTime.
Current and last synch event concept generalized in the
ippmSynchronizationTable.
12. References
[1] Bradner, S., "The Internet Standards Process -- Revision 3", BCP [1] Bradner, S., "The Internet Standards Process -- Revision 3", BCP
9, RFC 2026, October 1996. 9, RFC 2026, October 1996.
[2]Paxson, V., Almes, G., Mahdavi, J. and M. Mathis, "Framework for [2]Paxson, V., Almes, G., Mahdavi, J. and M. Mathis, "Framework for
IP Performance Metrics", RFC 2330, May 1998. IP Performance Metrics", RFC 2330, May 1998.
[3] Mahdavi J. and V. Paxson, "IPPM Metrics for Measuring [3] Mahdavi J. and V. Paxson, "IPPM Metrics for Measuring
Connectivity", RFC 2678, September 1999. Connectivity", RFC 2678, September 1999.
skipping to change at page 61, line 9 skipping to change at page 63, line 20
2573, April 1999. 2573, April 1999.
[21] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-basedAccess [21] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-basedAccess
Control Model (VACM) for the Simple Network Management Protocol Control Model (VACM) for the Simple Network Management Protocol
(SNMP)", RFC 2575, April 1999. (SNMP)", RFC 2575, April 1999.
[22] Case, J., Mundy, R., Partain, D., and B. Stewart, "Introduction [22] Case, J., Mundy, R., Partain, D., and B. Stewart, "Introduction
to Version 3 of the Internet-standard Network Management to Version 3 of the Internet-standard Network Management
Framework", RFC 2570, April 1999. Framework", RFC 2570, April 1999.
[23] Waldbusser, S., "Remote Network Monitoring MIB", STD 59, RFC 13. Acknowledgments
2819, Lucent Technologies, May 2000
[24] Waldbusser, S., "Remote Network Monitoring Management
Information Base Version 2 using SMIv2", RFC 2021, International
Network Services, January 1997.
[25] Remote Network Monitoring MIB Protocol Identifier Reference. A.
Bierman, C. Bucci, R. Iddon. RFC RFC2895 ,August 2000.
[26] Remote Network Monitoring MIB Protocol Identifier Macros. A.
Bierman, C. Bucci, R. Iddon. RFC RFC2896, August 2000.
11. Acknowledgments
A Kerbe. A Kerbe.
12. Author's Addresses 14. Authors Addresses
Emile STEPHAN Emile STEPHAN
France Telecom R & D France Telecom R & D
2 avenue Pierre Marzin 2 avenue Pierre Marzin
F-22307 Lannion cedex F-22307 Lannion cedex
Phone: (+ 33) 2 96 05 11 11 Phone: (+ 33) 2 96 05 11 11
Email: emile.stephan@francetelecom.com Email: emile.stephan@francetelecom.com
Jessie Jewitt Jessie Jewitt
France Telecom R & D France Telecom R & D
 End of changes. 

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