draft-ietf-ippm-reporting-mib-01.txt   draft-ietf-ippm-reporting-mib-02.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-02.txt March 1st, 2003
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 IPPM Framework..........................................3 3. The SNMP Management Framework...............................3
4. The SNMP Management Framework...............................4 4. Overview....................................................5
5. Overview....................................................6 4.1. Textual Conventions.........................................6
5.1. Textual Conventions.........................................7 4.2. Structure of the MIB........................................8
5.2. Structure of the MIB........................................9 4.3. Row identification in an application namespace.............10
5.3. Row identification in an application namespace.............11 4.4. Relationship of IPPM MIB tables............................11
5.4. Relationship of IPPM MIB tables............................12 5. IPPM-REPORTING-MIB conceptual presentation.................15
6. IPPM-REPORTING-MIB conceptual presentation.................16 5.1. IPPM-REPORTING-MIB diagram.................................15
6.1. IPPM-REPORTING-MIB diagram.................................16 5.2. Conceptual programming interface...........................16
6.2. Conceptual programming interface...........................17 5.3. SNMP mapping...............................................16
6.3. SNMP mapping...............................................17 6. Measurement architectures..................................17
7. Measurement architectures..................................18 6.1. Proxy architecture.........................................17
7.1. Proxy architecture.........................................18 6.2. Reporting architecture.....................................18
7.2. Reporting architecture.....................................19 6.3. Gateway architecture.......................................20
7.3. Gateway architecture.......................................21 6.4. Security...................................................20
7.4. Security...................................................21 7. Reporting mode integration.................................21
8. Reporting mode integration with the control and test 7.1. Integration................................................21
protocols................................................22 7.2. Setup of the measure.......................................21
8.1. Integration................................................22 7.3. Setup of the measurement report............................22
8.2. Setup of the measure.......................................22 7.4. Writing the results in the IPPM-REPORTING-MIB..............22
8.3. Setup of the measurement report............................23 7.5. Report download and upload.................................23
8.4. Writing the measurement results in the IPPM-REPORTING 7.6. Default value..............................................23
MIB......................................................23 8. Definition.................................................24
8.5. Report download and upload.................................24 9. Security Considerations....................................67
8.6. Default value..............................................24 9.1. Privacy....................................................67
9. Definition.................................................25 9.2. Measurement aspects........................................67
10. Security Considerations....................................58 9.3. Management aspects.........................................68
10.1. Privacy.....................................................58 10. Document management........................................69
10.2. Measurement aspects.........................................58 10.1. Open issues.................................................69
10.3. Management aspects..........................................59 10.2. changes since release 00....................................69
11. Document management........................................60 10.3. Changes since release 01....................................70
11.1. Open issues.................................................60 11. References.................................................72
11.2. changes since release 00....................................60 12. Acknowledgments............................................73
12. References.................................................61 13. Authors Addresses..........................................73
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 measures based upon the IP
performance metrics specified by the IPPM Working Group. performance metrics specified by the IPPM Working Group.
The definition of objects in the IPPM MIB are built on notions The definition of objects in the IPPM MIB are built on notions
introduced and discussed in the IPPM Framework document, RFC 2330 introduced and discussed in the IPPM Framework document, RFC 2330
[ii]. [ii].
This memo defines a Management Information Base (MIB), and as such it This memo defines a Management Information Base (MIB), and as such it
is intended to be respectful of the "Boilerplate for IETF MIBs" is intended to be respectful of the "Boilerplate for IETF MIBs"
skipping to change at page 3, line 37 skipping to change at page 3, line 37
A set of standardized metrics which conform to this framework: The A set of standardized metrics which conform to this framework: The
IPPM Metrics for Measuring Connectivity, RFC 2678 [iii]; The One-way IPPM Metrics for Measuring Connectivity, RFC 2678 [iii]; The One-way
Delay Metric for IPPM, RFC 2679 [iv]; The One-way Packet Loss Metric 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 for IPPM, RFC 2680 [v]; The Round-trip Delay Metric for IPPM, RFC
2681 [vi]. 2681 [vi].
Emerging metrics that are being specified in respect of this Emerging metrics that are being specified in respect of this
framework. framework.
3. The IPPM Framework 3. The SNMP Management Framework
The IPPM Framework consists in 3 major components:
A general framework for defining performance metrics, 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 [3]; The One-
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,
RFC 2681 [6].
Emerging metrics that are being specified in respect of this
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 [6].
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 [7], STD 16, RFC 1212 [8] and RFC 1215 [9]. 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 [10], STD 58,
RFC 2579 [12] and STD 58, RFC 2580 [13]. RFC 2579 [11] and STD 58, RFC 2580 [12].
Message protocols for transferring management information. The Message protocols for transferring management information. The
first version of the SNMP message protocol is called SNMPv1 and first version of the SNMP message protocol is called SNMPv1 and
described in STD 15, RFC 1157 [14]. A second version of the SNMP described in STD 15, RFC 1157 [13]. A second version of the SNMP
message protocol, which is not an Internet standards track protocol, message protocol, which is not an Internet standards track protocol,
is called SNMPv2c and described in RFC 1901 [15] and RFC 1906 [16]. is called SNMPv2c and described in RFC 1901 [14] and RFC 1906 [15].
The third version of the message protocol is called SNMPv3 and The third version of the message protocol is called SNMPv3 and
described in RFC 1906 [16], RFC 2572 [17] and RFC 2574 [18]. described in RFC 1906 [15], RFC 2572 [16] and RFC 2574 [17].
Protocol operations for accessing management information. The Protocol operations for accessing management information. The
first set of protocol operations and associated PDU formats is first set of protocol operations and associated PDU formats is
described in STD 15, RFC 1157 [14]. A second set of protocol described in STD 15, RFC 1157 [13]. A second set of protocol
operations and associated PDU formats is described in RFC 1905 [19]. operations and associated PDU formats is described in RFC 1905 [18].
A set of fundamental applications described in RFC 2573 [20] and A set of fundamental applications described in RFC 2573 [19] and
the view-based access control mechanism described in RFC 2575 [21]. the view-based access control mechanism described in RFC 2575 [20].
A more detailed introduction to the current SNMP Management Framework A more detailed introduction to the current SNMP Management Framework
can be found in RFC 2570 [22]. can be found in RFC 2570 [21].
Managed objects are accessed via a virtual information store, termed Managed objects are accessed via a virtual information store, termed
the Management Information Base or MIB. Objects in the MIB are the Management Information Base or MIB. Objects in the MIB are
defined using the mechanisms defined in the SMI. defined using the mechanisms defined in the SMI.
This memo specifies a MIB module that is compliant to the SMIv2. A This memo specifies a MIB module that is compliant to the SMIv2. A
MIB conforming to the SMIv1 can be produced through the appropriate MIB conforming to the SMIv1 can be produced through the appropriate
translations. The resulting translated MIB must be semantically translations. The resulting translated MIB must be semantically
equivalent, except where objects or events are omitted because no equivalent, except where objects or events are omitted because no
translation is possible (use of Counter64). Some machine readable translation is possible (use of Counter64). Some machine readable
skipping to change at page 6, line 5 skipping to change at page 5, 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.
5. Overview 4. 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 measurement of these management interface to manage remotely the measurement of these
metrics. This memo defines a Management Information Base for managing metrics. This memo defines a Management Information Base for managing
the measurement 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 the [IPPM metrics framework for the integration of future metrics in the [IPPM metrics
skipping to change at page 6, line 27 skipping to change at page 5, line 27
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 [xxiii],[xxiv] The MIB architecture is inspired by the RMON model [xxiii],[xxiv]
which specifies the MIB for the monitoring of a single point of which specifies the MIB for the monitoring of a single point of
measure. The IPPM-REPORTING-MIB differs from this model in that IPPM measure. The IPPM-REPORTING-MIB differs from this model in that IPPM
metrics measurement involves several points of measure and requires metrics measurement involves several points of measure and requires
common references for time and for measure identification. The IPPM- common references for time and for measure identification.
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
measurement 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 measurements. The memo lists frameworks are suitable for performing measurements. The memo lists
skipping to change at page 7, line 5 skipping to change at page 6, line 5
control protocols and test protocols. It addresses the need to control protocols and test protocols. It addresses the need to
provide access to results for the applications. Moreover, it may be provide access to results for the applications. Moreover, it may be
used to reduce the number of control frameworks. used to reduce the number of control frameworks.
This MIB is intended to handle multiple concurrent sessions by SNMP This MIB is intended to handle multiple concurrent sessions by SNMP
applications. However, the SNMP requests are not necessarily to be applications. However, the SNMP requests are not necessarily to be
handled explicitly by the measurement devices, but can be sent to handled explicitly by the measurement devices, but can be sent to
middleware performing an aggregation function. This allows for middleware performing an aggregation function. This allows for
continuous collection of measurements and statistics computation. continuous collection of measurements and statistics computation.
5.1. Textual Conventions 4.1. Textual Conventions
Four types of data are introduced as a textual convention in this Five types of data are introduced as a textual convention in this
document: TypeP, GMTTimeStamp, IppmStandardMetrics and document: TypeP, TypePaddress, GMTTimeStamp, IppmStandardMetrics and
IppmReportDefinition. IppmReportDefinition.
5.1.1. Packet of type P 4.1.1. TypeP and TypePaddress
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.
skipping to change at page 7, line 34 skipping to change at page 6, line 34
the capability to finely and unambiguously configure 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. RFC2895 [xxv] RMON2 introduced the concept of protocol identifiers. RFC2895 [xxv]
specifies a macro for the definition of protocol identifier. The specifies a macro for the definition of protocol identifier. The
RFC2896 [xxvi] defines the protocol identifiers for different RFC2896 [xxvi] defines the protocol identifiers for different
protocol 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 and the TypePaddress as new syntax in SMIv2
TEXTUAL-CONVENTION.
5.1.1.1. Internet addresses 4.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. encoding rules of the protocol identifier, 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. The type and value of format of "Src" and "Dst" and their values. The type and value of
these addresses depend on the type P of the packet, IP version 4, V6, these addresses depend on the type P of the packet, IP version 4,
IP in IP... Both participate in the completion of the packet IPV6, IP in IP... Both participate in the completion of the packet
encoding. 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 'ip.ipip4'. The encoding of 'ip.ipip4' using the RFC2895 rules
TypeP indicates that there are 2 parameters. In the IPPM context adds a trailer 2.0.0. It means that an instance of this protocol
these 2 parameters are provided in Src, which has the value identifier has 2 parameters, which values will be set only when
10.4.192.168.1.1.4.128.2.6.7. implemented. In the IPPM TypeP context these 2 parameters are
provided in Src (or Dst). In the current example the value of Src is
"192.168.1.1 128.2.6.7".
5.1.2. GMTTimeStamp 4.1.2. GMTTimeStamp
This textual convention defines the time at which an event occurred. This textual convention defines the time at which an event occurred.
It is very similar to the NTP timestamp format except that it It is very similar to the NTP timestamp format except that it
represents the time elapsed since January 1st, 2000 instead of represents the time elapsed since January 1st, 2000 instead of
January 1st, 1900. January 1st, 1900.
5.1.3. IppmStandardMetrics 4.1.3. IppmStandardMetrics
Each standard metric is identified in the IPPM-METRICS-REGISTRY under Each standard metric is identified in the IPPM-METRICS-REGISTRY under
the node rfc in a chronological order. To permit several metrics to the node rfc in a chronological order. This textual convention
be performed in a single measure there is an need to describe in a defines an octet string to permit several metrics to be performed in
bit string the metrics to be performed, granted... This textual a single measure.
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.
5.1.4. Report definition 4.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
measurements that have been taken over a period of time. The report measurements that have been taken over a period of time. The report
consists of actions that are taken on the measurement results. An consists of actions that are taken on the measurement results. An
action is performed either: 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.
skipping to change at page 9, line 30 skipping to change at page 8, line 30
+ A basic report is defined in the object ippmReportSetupDefinition; + A basic report is defined in the object ippmReportSetupDefinition;
+ More elaborate reports are described using a metric threshold to + More elaborate reports are described using a metric threshold to
generate alarms and events. generate alarms and events.
+ Pushing of alarms and reports requires a management station + Pushing of alarms and reports requires a management station
address to which the data will be sent. address to which the data will be sent.
+ SLA alarms are described using an events duration threshold. + SLA alarms are described using an events duration 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.
5.2. Structure of the MIB 4.2. Structure of the MIB
The MIB is arranged as follow: The MIB is arranged as follow:
- ippmNotifications
- ippmOwnersGroup - ippmOwnersGroup
- ippmSystemGroup - ippmSystemGroup
- ippmMeasureGroup - ippmMeasureGroup
- ippmHistoryGroup - ippmHistoryGroup
- ippmNetworkMeasureGroup - ippmNetworkMeasureGroup
- ippmAggregatedMeasureGroup - ippmAggrMeasureGroup
- ippmReportGroup - ippmReportGroup
4.2.1. The ippmOwners Group
- ippmNotifications
5.2.1. The ippmOwners Group
This group identifies an owner, or group of owners that have access This group identifies an owner, or group of owners that have access
to measurements on a probe. to measurements on a probe.
5.2.2. The ippmSystem Group 4.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 at a particular point of measure over 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.
5.2.3. The ippmMeasureGroup 4.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 and ippmMeasureTable. The entity. It consists of the ippmMetricsTable and ippmMeasureTable. The
ippmMeasureTable holds the common part of a measure, while the ippmMeasureTable holds the common part of a measure, while the
specific parameters are handled in the corresponding auxiliary table specific parameters are handled in the corresponding auxiliary table
(ippmNetworkMeasure, ippmAggregatedMeasureTable...) . (ippmNetworkMeasure, ippmAggrMeasureTable...) .
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. All agent the local implementation of the standardized metrics. All
standardized metrics should be displayed in this table, with the standardized metrics should be displayed in this table, with the
capability object defining whether the metric is implemented or not. 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. The in the ippmMeasureTable and in the auxiliary measure tables. The
ippmMeasureTable table is read-create, but only allows for the ippmMeasureTable table is read-create, but only allows for the
creation of "aggregated" measures when defined in conjunction with creation of "aggregated" measures when defined in conjunction with
the ippmAggregatedMeasureTable. Network measures are not allowed to the ippmAggrMeasureTable. Network measures are not allowed to be
be created directly by the management entity, and as such the measure created directly by the management entity, and as such the measure
table values for these measures should be display only. table values for these measures should be display only.
The results of the measurements are logged in the ippmHistoryTable. The results of the measurements are logged in the ippmHistoryTable.
5.2.4. The ippmNetworkMeasure Group 4.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.
5.2.5. The ippmAggregatedMeasure Group 4.2.5. The ippmAggrMeasure Group
ippmAggregatedMeasureTable is an auxiliary table of ippmMeasureTable, ippmAggrMeasureTable is an auxiliary table of ippmMeasureTable, and
and is responsible for the consolidation of the results previously 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.
5.2.6. The Report Group 4.2.6. The Report Group
This group displays the existing reports of the measures collected. 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.
5.2.7. The Notification Group 4.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.
5.3. Row identification in an application namespace 4.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 object instance identifier in an objects in the clause INDEX. An object instance identifier in an
owner namespace is defined as a list of objects in the clause INDEX owner namespace is defined as a list of objects in the clause INDEX
where the first object type is OwnerString. where the first object type is IppmOwnerString.
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 values 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 exists in the MIB tables. This allows the owner to use the fields exists in the MIB tables. This allows the owner to use the
same 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, two 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 management applications. An instance of Measurements are requested by management applications. An instance of
an object managed by a management station is identified by the an object managed by a management station is identified by the
management station OwnerString and the private index provided by the management station IppmOwnerString and the private index provided by
MS. the MS.
As the MS manages its private range of indices, it simply chooses one As the MS manages its private range of indices, it simply chooses one
when it wishes to create a new control entry. For the same reason, when it wishes to create a new control entry. For the same reason,
the setup of a measure on several points of measures consists of the setup of a measure on several points of measures consists 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.4. Relationship of IPPM MIB tables 4.4. Relationship of IPPM MIB tables
There is inherently a relationship between various tables in the IPPM There is inherently a relationship between various tables in the IPPM
Mib, and as such, the data integrity must be assured. This Mib, and as such, the data integrity must be assured. This
relationship is depicted in the following examples. relationship is depicted in the following examples.
5.4.1. Relationship between the Owners Table and the Measure Table 4.4.1. Relationship between the Owners Table and the Measure Table
The owners table contains the list of "owners" that can create and The owners table contains the list of "owners" that can create and
activate remote IPPM measurements in an agent. As the table is activate remote IPPM measurements in an agent. As the table is
"Read/Create", these users and their associated "Read/Create", these users and their associated
"access" rights on metric measurements can be directly configured. It "access" rights on metric measurements can be directly configured. It
is recommended to make use of "view based access control" in order to is recommended to make use of "view based access control" in order to
restrict access to this table. For example, the restrict access to this table. For example, the
master user "acme" may be given "write" privileges on the master user "acme" may be given "write" privileges on the
ippmOwnersTable, whereas all others are restricted to "read" access. ippmOwnersTable, whereas all others are restricted to "read" access.
The user "acme" can then setup the list of other users that have The user "acme" can then setup the list of other users that have
skipping to change at page 12, line 42 skipping to change at page 11, line 46
is recommended to make use of "view based access control" in order to is recommended to make use of "view based access control" in order to
restrict access to this table. For example, the restrict access to this table. For example, the
master user "acme" may be given "write" privileges on the master user "acme" may be given "write" privileges on the
ippmOwnersTable, whereas all others are restricted to "read" access. ippmOwnersTable, whereas all others are restricted to "read" access.
The user "acme" can then setup the list of other users that have The user "acme" can then setup the list of other users that have
access to measures. access to measures.
There must be at least 1 owner in the owners table. This owner may be 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 either setup by default by the IPPM agent, or configured as stated
above. above.
An owner may have multiple corresponding entries in the measure An owner may have multiple corresponding entries in the measure
table. Each entry in the measure table must be associated with one, 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 and only one, entry in the owners table. That is to say, that a
defined measure may NOT have multiple owners. defined measure may NOT have multiple owners.
Thus, we have a 1:N relationship between the owners table and the Thus, we have a 1:N relationship between the owners table and the
measure table. measure table.
+---------------------+ +---------------------------+ +---------------------+ +---------------------------+
+ ippmOwnersTable + + ippmMeasureTable + | ippmOwnersTable | | ippmMeasureTable |
+---------------------+ 1:N +---------------------------+ +---------------------+ 1:N +---------------------------+
+ OwnersOwner: "Acme" +--------------+ Measure Owner: "Acme" + | OwnersOwner: "Acme" |--------------| Measure Owner: "Acme" |
+ ..... + + Measure Name:"OneWayDelay"+ | "Foo" | | Measure Name:"OneWayDelay"|
+ "Foo" + +...... + | . | |...... |
+ + + Measure Owner: "Foo" + | . | | Measure Owner: "Foo" |
+---------------------+ + Measure Name: "PacketLoss"+ | . | | Measure Name: "PacketLoss"|
+---------------------------+ | | | Measure Owner: "Foo" |
+---------------------+ +---------------------------+
5.4.2. Relationship between the Measure Table and the Network Measure 4.4.2. Relationship between the Measure Table and the Network Measure
Table/Aggregated Measure Table Table/Aggregated Measure Table
The network measure table and the aggregated measure table can be The network measure table and the aggregated measure table can be
seen as logical "extensions" to the measure table. seen as logical "extensions" to the measure table.
The measure table contains information that is common to both types The measure table contains information that is common to both types
of measurements. The information found in the Network Measure Table of measurements. The information found in the Network Measure Table
and the Aggregated Measure Table is specific to each type of measure. 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 As the network measure table is read-only, entries in this table must
be populated by the agent upon startup. be populated by the agent upon startup.
skipping to change at page 14, line 6 skipping to change at page 13, line 6
"owner" (B), then "owner" (B) must grant "owner" (A) access to his "owner" (B), then "owner" (B) must grant "owner" (A) access to his
measures. This can be done in the resultsharing table. measures. This can be done in the resultsharing table.
Even though the Measure Table is read-create, an "owner" should only Even though the Measure Table is read-create, an "owner" should only
be able to create, or modify entries in the measure table that be able to create, or modify entries in the measure table that
correspond to aggregated measure types. Should an "owner" attempt to correspond to aggregated measure types. Should an "owner" attempt to
update an entry in the measure table that corresponds to an entry update an entry in the measure table that corresponds to an entry
in the network measure table, than access should be denied. in the network measure table, than access should be denied.
+---------------------------+ +----------------------------------+ +---------------------------+ +----------------------------------+
+ ippmMeasureTable + + ippmNetworkMeasureTable + | ippmMeasureTable | | ippmNetworkMeasureTable |
+---------------------------+ +----------------------------------+ +---------------------------+ +----------------------------------+
+ Measure Owner: "Acme" + + MeasureSrc: "Src1" + | Measure Owner: "Acme" | | MeasureSrc: "Src1" |
+ Measure Name:"OneWayDelay + ---+ MeasureDst: "Dst1" + | Measure Name:"OneWayDelay | ---| MeasureDst: "Dst1" |
+ ....... + + ........ + | ....... | | ........ |
+ Measure Owner: "Foo" + + MeasureSrc: "Src2" + | Measure Owner: "Foo" | | MeasureSrc: "Src2" |
+ Measure Name: "PacketLoss"+ + MeasureDst: "Dst2" + | Measure Name: "PacketLoss"| | MeasureDst: "Dst2" |
+ + +----------------------------------+ | | +----------------------------------+
+ + | |
+ + +----------------------------------+ | | +----------------------------------+
+ + + ippmAggregatedMeasureTable + | | | ippmAggrMeasureTable |
+ + +----------------------------------+ | | +----------------------------------+
+ Measure Owner: "Acme" + + AMHistoryOwner: "Foo" + | Measure Owner: "Acme" | | AMHistoryOwner: "Foo" |
+ Measure Name: "AvgPLoss" + ---+ AMHistoryMetric: "PacketLoss" + | Measure Name: "AvgPLoss" | ---| AMHistoryMetric: "PacketLoss" |
+---------------------------+ +----------------------------------+ +---------------------------+ +----------------------------------+
+---------------------------------+ +--------------------------+ +---------------------------+ +----------------------------------+
+ ippmResultSharingTable + + ippmHistoryTable + | ippmHistoryTable | | ippmResultSharingTable |
+ + + (ex: with OWPL values) + | (ex: with OWPL values) | | |
+---------------------------------+ +--------------------------+ +---------------------------+ +----------------------------------+
+ SharingOwner: "Foo" + + Idx: Meas. Owner"Foo " + | Idx: Meas. Owner"Foo " | | SharingOwner: "Foo" |
+ SharingMeasureOwner:"PacketLoss"+ + Measure Index: 1 + | Measure Index: 1 | | SharingMeasureOwner:"PacketLoss"|
+ + + Metrix Indx: 12 + | Metrix Indx: 12 | | |
+ SharingGrantedOwner: "Acme" + + + | | | SharingGrantedOwner: "Acme" |
+---------------------------------+ + HistorySqceNdx: 1 + | HistorySqceNdx: 1 | +----------------------------------+
+ GMTTimeStampValue + | GMTTimeStampValue |
+ Value: 5 + | Value: 5 |
+------------------------- + +---------------------------+
+ Idx: Meas. Owner "Foo" + | Idx: Meas. Owner "Foo" |
+ Mesure Index: 1 + | Mesure Index: 1 |
+ Metric Index: 12 + | Metric Index: 12 |
+ HistorySqceNdx: 2 + | HistorySqceNdx: 2 |
+ GMTTimeStampValue + | GMTTimeStampValue |
+ Value: 15 + | Value: 15 |
+ Idx: Meas. "Acme" + | Idx: Meas. "Acme" |
+ Measure Index: 3 + | Measure Index: 3 |
+ Metric Index: 14 + | Metric Index: 14 |
+ HistorySqceNdx: 1 + | HistorySqceNdx: 1 |
+ GMTTimeStampValue + | GMTTimeStampValue |
+ Value: 10 + | Value: 10 |
+--------------------------+ +---------------------------+
As the aggregated measure table essentially "inherits" from the As the aggregated measure table essentially "inherits" from the
measure table, one can not create an entry is this table without measure table, one can not create an entry is this table without
first creating an entry in the measure table. Likewise, one can not first creating an entry in the measure table. Likewise, one can not
delete an entry in the measure table without first deleting the delete an entry in the measure table without first deleting the
corresponding row in the aggregated measure table. This logic ensures corresponding row in the aggregated measure table. This logic ensures
that there are no "orphaned" table entries in the aggregated measure that there are no "orphaned" table entries in the aggregated measure
table. table.
6. IPPM-REPORTING-MIB conceptual presentation 5. IPPM-REPORTING-MIB conceptual presentation
6.1. IPPM-REPORTING-MIB diagram 5.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 17, line 5 skipping to change at page 16, 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.
6.2. Conceptual programming interface 5.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.
6.2.1. Measure control 5.2.1. Measure control
A measure is created/deleted/suspended through the ControlMeasure() A measure is created/deleted/suspended through the ControlMeasure()
call. call.
6.2.2. Result log 5.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.
6.2.3. Reporting 5.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.
6.2.4. Logical calls 5.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().
6.3. SNMP mapping 5.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.
7. Measurement architectures 6. Measurement architectures
There are four main measurement architectures. There are four main measurement architectures.
7.1. Proxy architecture 6.1. Proxy architecture
+----+ +----+ +----+ +----+
|NMS1| |NMS2| |NMS1| |NMS2|
+----+ +----+ +----+ +----+
^ ^ ^ ^
| | | |
+----------+ +----------+ +----------+ +----------+
| | | |
SNMP or Sibling SNMP or Sibling
| | | |
skipping to change at page 19, line 7 skipping to change at page 18, line 5
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.
7.2. Reporting architecture 6.2. Reporting architecture
In this architecture the SNMP protocol is only used to read the results In this architecture the SNMP protocol is only used to read the
of the measurements in the IPPM-REPORTING-MIB History Table, and also to results of the measurements in the IPPM-REPORTING-MIB History Table,
inform the NMS that an event has occurred. and also to 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 41 skipping to change at page 18, line 39
| | | | | | | | | | | | | | | |
| | | | | | | | | | | | | | | |
v v v v v v v v v v v v v v v v
+------------------+ +------------------+ +------------------+ +------------------+
|IPPM-REPORTING-MIB| |IPPM-REPORTING-MIB| |IPPM-REPORTING-MIB| |IPPM-REPORTING-MIB|
| agent | | agent | | agent | | agent |
+------------------+ +------------------+ +------------------+ +------------------+
| Packets-Sender |--OWDP-Test-->| Packets-Receiver | | Packets-Sender |--OWDP-Test-->| Packets-Receiver |
+------------------+ +------------------+ +------------------+ +------------------+
The activation of a measure by the control protocol or the test protocol The activation of a measure by the control protocol or the test
creates a measure in the IPPM-REPORTING-MIB Measure table. The table in protocol creates a measure in the IPPM-REPORTING-MIB Measure table.
question may be not accessible by SNMP. In this case, a list of the The table in question may be not accessible by SNMP. In this case, a
measure identifiers (owner, index) is handled by the measurement list of the measure identifiers (owner, index) is handled by the
software. measurement software.
Each timestamped result of the measure is logged on the fly in the IPPM- Each timestamped result of the measure is logged on the fly in the
REPORTING-MIB History table in order to allow read access to the NMSÆs IPPM-REPORTING-MIB History table in order to allow read access to the
and event handling. NMSÆs and event handling.
On completion, the measurement results are managed according to the On completion, the measurement results are managed according to the
measure setup: measure setup:
+ The results may be sent to an NMS using a SNMP Trap PDU or a
SNMP Inform PDU. The NMS may be the sender entity or the control
entity;
+ They may be dropped from the IPPM-REPORTING-MIB History table.
+ The results may be sent to an NMS using a SNMP Trap PDU or In this mode, it is recommended to use an SNMPv2 Inform PDU to send
a SNMP Inform PDU. The NMS may be the sender entity or the the result because it ensures that the entire block of the result is
control entity;
+ They may be dropped from the IPPM-REPORTING-MIB History
table.
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
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- 6.3. Gateway architecture
MIB Measure table in read only in order to allow an NMS to read the
status of their measures.
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 21, line 46 skipping to change at page 20, line 47
+-------------+---------+ +--------+-------------+ +-------------+---------+ +--------+-------------+
| 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.
7.4. Security 6.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
protocol implementations in the points of measure. Different security test protocol implementations in the points of measure. Different
rules may be applied to the NMS domain and to measurement system security rules may be applied to the NMS domain and to measurement
domains. system 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 test protocol security mechanisms.
+ The control of access to the results depends on the SNMP
security mechanisms.
+The control of the measurement setups relies on the control and the The gateway mode security relies on the security of the proxy mode
test protocol security mechanisms. and of the reporting mode.
+ The control of access to the results depends on the SNMP security
mechanisms.
The gateway mode security relies on the security of the proxy mode and
of the reporting mode.
8. Reporting mode integration with the control and test protocols 7. Reporting mode integration
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.
A measure is a distributed object describing a task to be performed by A measure is a distributed object describing a task to be performed
the control and the test protocols. A measure is identified by its owner by the control and the test protocols. A measure is identified by its
and its owner index. This identifier is the same in all the points of owner and its owner index. This identifier is the same in all the
measure. As the owner chooses the index, there is no need for points of measure. As the owner chooses the index, there is no need
negotiation between the NMS and the points of measure before activating for negotiation between the NMS and the points of measure before
the measure. activating 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
of the scheduling of the measure. description 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
involved. The distribution may not be synchronized. measure involved. The distribution may not be synchronized.
8.1. Integration 7.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
same semantic. the 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.
8.2. Setup of the measure 7.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
the measure is done using the ControlMeasure(). of 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.
8.2.1. Synchronous setup 7.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.
8.2.2. Asynchronous setup 7.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
typeP of the measurement. the 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
differ from regular test packets. If the first test packet is not may 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.
8.3. Setup of the measurement report 7.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
It describes the event and the data to include in the report. A report measure. It describes the event and the data to include in the
is read by an NMS in the ippmReportTable, or pushed to a NMS using a report. A report is read by an NMS in the ippmReportTable, or pushed
SNMP Trap PDU, a SNMP Inform PDU, an email, or a SMS. to a NMS using a 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
the report in the setup of the measure. of the report in the setup of the measure.
Different types of reports may be combined: Different types of reports may be combined:
+ A trivial report defines the results to be saved in the + A trivial report defines the results to be saved in the
ippmReportTable; ippmReportTable;
+ A basic report defines the host to which the results are + A basic report defines the host to which the results are pushed
pushed on completion of the measure; 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
or fall the threshold; 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
The report consists in the results of the measure (time and report consists in the results of the measure (time and value) of
value) of the filtered events. The reports are sent at each the filtered events. The reports are sent at each measure cycle
measure cycle or when the measure completes. or when the measure completes.
8.4. Writing the measurement results in the IPPM-REPORTING-MIB 7.4. Writing the 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().
8.5. Report download and upload 7.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
SMS. a SMS.
8.6. Default value 7.6. Default value
The default values correspond to Ipv4 best effort. The default values correspond to IP version 4.
9. Definition 8. 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, experimental ,Integer32
Counter32
FROM SNMPv2-SMI FROM SNMPv2-SMI
ippm --
FROM IPPM-REGISTRY -- ippm
OwnerString -- FROM IPPM-REGISTRY
FROM RMON-MIB --
InetAddressType, InetAddressType,
InetAddress InetAddress
FROM INET-ADDRESS-MIB FROM INET-ADDRESS-MIB
SnmpAdminString SnmpAdminString
FROM SNMP-FRAMEWORK-MIB FROM SNMP-FRAMEWORK-MIB
TimeStamp,
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 "200203171200Z" -- 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 "Emile Stephan
France Telecom - R&D, Dpt. CPN France Telecom - R&D
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
skipping to change at page 26, line 4 skipping to change at page 24, line 52
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 (MIB) for use with " This memo defines a portion of the Management Information Base
network management protocols in TCP/IP-based internets. In particular, it specifies (MIB) for use with network management protocols in TCP/IP-based
the objects used for managing the results of the IPPM metrics measurements, alarms and internets. In particular, it specifies the objects used for
reporting the measures results. managing the results of the IPPM metrics measurements, alarms and
" reporting the measures results."
REVISION "200210181200Z" -- 18 October 2002 REVISION "200210181200Z" -- 18 October 2002
DESCRIPTION DESCRIPTION
"General cleanup "General cleanup
Change 5 tables to read write" Change 5 tables to read write"
::= { ippm 2 } REVISION "200302141200Z" -- 14 February 2003
DESCRIPTION
"Modifications based upon feedback from IETF-55"
::= { experimental 10001 }
ippm OBJECT IDENTIFIER ::= { experimental 10000 }
-- --
-- TEXTUAL-CONVENTION -- TEXTUAL-CONVENTION
-- --
IppmOwnerString ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"An OwnerString, which length is limited to 32."
SYNTAX OCTET STRING (SIZE (0..32))
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 {
year(1), year(1),
month(2), month(2),
week(3), week(3),
day(4), day(4),
hour(5), hour(5),
second(6), second(6),
ms(7), millisecond(7),
us(8), microsecond(8),
ns(9) nanosecond(9)
} }
-- --
-- --
IppmStandardMetrics ::= TEXTUAL-CONVENTION IppmStandardMetrics ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
" Each standard metric is identified in the IPPM-METRICS- " Each standard metric is identified in the IPPM-METRICS-
REGISTRY under the node rfc in a chronological order. To permit REGISTRY under the node rfc in a chronological order. To permit
several metrics to be performed in a single measure there is an need several metrics to be performed in a single measure there is an
to describe in a bit string the metrics to be performed, granted... need
This textual convention defines an octet string that gathered in a to describe in a bit string the metrics to be performed,
bit string a sequence of bits. The bit order corresponds to the order 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. of the metrics identifiers in the registry.
The first bit of the string is not used. The first bit of the string has the index 0. The index 1
corresponds to the first metric of the registry
(instantaneousUnidirectionalConnectivity ).
Example: Example:
One-way-Delay(6) is identified as the leaf number 6 of the node rfc of the One-way-Delay(6) is identified as the leaf number 6 of the node
registry. One-way-Packet-Loss(12) is identified as the leaf number 12 of the node rfc of the
rfc of the registry. A network measure performing both One-way-Delay(6) and One- registry. One-way-Packet-Loss(12) is identified as the leaf
way-Packet-Loss(12) will be described as '0000001000001000'b, '0208'B. 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 '0001000001000000'b,
'1040'B.
" "
SYNTAX OCTET STRING SYNTAX OCTET STRING
GMTTimeStamp ::= TEXTUAL-CONVENTION GMTTimeStamp ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The value of the ippmSystemTime object at which a specific occurrence "The value of the ippmSystemTime object at which a specific
happened. The specific occurrence must be defined in the description of any object occurrence happened. The specific occurrence must be defined in
defined using this type. the description of any object defined using this type.
field octets contents range field octets contents range
----- ------ -------- ----- ----- ------ -------- -----
1 1-4 second since 1 Jan 2000 0H00* 0..2^31 - 1 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 2 5-8 fractional part of the second* 0..2^32 - 1
* the value is in network-byte order * the value is in network-byte order
The timestamp format is directly inspired from the NTP timestamp format. The timestamp format is directly inspired from the NTP timestamp
It differs because it counts the second since 1 Jan 2000 0H00 instead of 1 Jan 1900 format.
0H00. The most significant bit of the part that represents the second is reserved. It It differs because it counts the second since 1 Jan 2000 0H00
will wrap in year 2068 (The NTP timestamp will wrap in year 2036). 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 This bit is set to indicate if the fractional part of the second
field and a synchronization field as initially proposed in the OWAMP draft. 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. When this bit is not set the resolution is maximal.
The maximal resolution is close to 250 picoseconds. The maximal resolution is close to 250 picoseconds.
The precision of the timestamp must be provided in another field. The precision of the timestamp must be provided in another field.
" "
SYNTAX OCTET STRING (SIZE (8)) SYNTAX OCTET STRING (SIZE (8))
TypeP ::= TEXTUAL-CONVENTION TypeP ::= TEXTUAL-CONVENTION
DISPLAY-HINT "1d."
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This textual convention is used to describe the protocol encapsulation list of a "This textual convention is a display string used to describe the
packet, and is used as the value of the SYNTAX clause for the type of the Src and Dst protocol encapsulation list of a packet, and is used as the value
of an IPPM measure. The RFC2895 specifies a macro for the definition of protocol of the SYNTAX clause for the type of the Src and Dst of an IPPM
identifiers while its companion document, the RFC2896 defines a set of protocol measure. The RFC2895 specifies a macro named PROTOCOL-IDENTIFIER
identifiers. for the definition of protocol identifiers while its companion
document, the RFC2896 defines a set of protocol identifiers.
Notes: An IPPM TypeP does not differ from RMON2 Protocol identifiers, but TypeP usage TypeP is defined as a display string. It consists in a list of
in IPPM MIB differs from Protocol identifier usage in RMON2. A IPPM measure is active, dot separated protocol names. Each protocol name has been
so generally TypeP does not describe the link layer (i.e. ether2...). Valid Internet previously defined using the macro PROTOCOL-IDENTIFIER of the RFC
packets are sent from Src to Dst. Then the choice of the link layer relies on the 2895.
Internet stack.
For example, the RFC2896 defines the protocol identifier Examples:
'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 The RFC2896 defines the protocol identifiers 'ether2', 'ip',
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 'ipip4', 'udp', 'tcp', 'telnet'...
for ether2.ip.ipip4.udp. The corresponding TypeP are
'12.0.0.8.0.0.0.0.6.0.0.0.23.3.0.0.0' (ip.tcp.telnet) and The TypeP of the source address corresponding to telnet is the
12.0.0.8.0.0.0.0.4.0.0.0.17.3.0.0.0 (ip.ipip4.udp)." string 'ip.tcp.telnet'.
SYNTAX OCTET STRING
The TypeP of the source address corresponding to UDP packets sent
in an IP tunnel is the string 'ip.ipip4.udp'.
Notes:
An IPPM measure is active, so generally a TypeP value does not
describe the link layer (i.e. ether2...). Valid Internet packets
are sent from Src to Dst. Then the choice of the link layer
relies on the Internet stack."
SYNTAX OCTET STRING (SIZE (0..255))
TypePaddress ::= TEXTUAL-CONVENTION
DISPLAY-HINT "255a"
STATUS current
DESCRIPTION
"This textual convention is a Display string used to describe the
parameters of the protocol encapsulation list of a packet,
basically the address.
TypePaddress is defined as a display string. It consists in a
list of space separated parameter list. Each parameter in the
list corresponds a parameter of a PROTOCOL-IDENTIFIER of the
TypeP.
Example:
The TypeP 'ip.ipip4' has 2 parameters. A valid TypePaddress value
is '192.168.1.1 128.2.6.7'."
SYNTAX OCTET STRING (SIZE (0..255))
IppmReportDefinition ::= TEXTUAL-CONVENTION IppmReportDefinition ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"IppmReportDefinition is intended to be used for describing the report "IppmReportDefinition is intended to be used for describing the
resulting from a measurement. By default, all the results of a measure belong to the report resulting from a measurement. By default, all the results of a
report of this measure. measure belong to the report of this measure.
The first step of the report definition sets up triggers on the value of the The first step of the report definition sets up triggers on the value
measure, and on the distribution over time of the events generated by these triggers. of the measure, and on the distribution over time of the events
generated by these triggers.
The resulting measures corresponding to an event are reported periodically, The resulting measures corresponding to an event are reported
or sent in alarms as soon as the event occurs. periodically, 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 is 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 measure occurs. The actions are performed each time a new result of the measure
occurs.
onMeasureCycle(2): onMeasureCycle(2):
The actions are performed on the results of the measure at the end of each cycle of The actions are performed on the results of the measure at the end of
measure. each cycle of measure.
onMeasureCompletion(3): onMeasureCompletion(3):
The actions are performed on the results of the measure at the end of the measure. The actions are performed on the results of the measure at the end of
the measure.
reportOnlyUptoDownMetricResults(4): reportOnlyUptoDownMetricResults(4):
Report the contiguous results that are on opposite sides of the metric threshold. Report the contiguous results that are on opposite sides of the
metric threshold.
reportOnlyExceededEventsDuration(5): reportOnlyExceededEventsDuration(5):
Report the current result of a series of contiguous results that exceed the metric Report the current result of a series of contiguous results that
threshold when the duration of the series is over the events duration threshold exceed the metric threshold when the duration of the series is over
seconds. the events duration 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): onReportDeliveryClearHistory(12):
Remove all the results corresponding to this measure from the ippmHistoryTable. Remove all the results corresponding to this measure from the
ippmHistoryTable when the report has been delivered.
clearReport(13): onReportDeliveryClearReport(13):
Remove all the results corresponding to this measure from the ippmReportTable. Remove all the results corresponding to this measure from the
ippmReportTable when the report has been delivered.
" "
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),
skipping to change at page 29, line 28 skipping to change at page 29, line 44
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), onReportDeliveryClearHistory (12),
clearReport(13) onReportDeliveryClearReport (13)
} }
--
-- IPPM Notifications
--
ippmNotifications OBJECT IDENTIFIER ::= { ippm 0 }
--
-- IPPM Conformance
--
ippmConformance OBJECT IDENTIFIER ::= { ippm 1 }
--
-- IPPM Mib objects definitions -- IPPM Mib objects definitions
--
ippmCompliances OBJECT IDENTIFIER ::= { ippmReportingMib 2 } ippmSystem OBJECT IDENTIFIER ::= { ippmReportingMib 1 }
ippmSystemGroup OBJECT IDENTIFIER ::= { ippmReportingMib 3 } ippmOwners OBJECT IDENTIFIER ::= { ippmReportingMib 2 }
ippmOwnersGroup OBJECT IDENTIFIER ::= { ippmReportingMib 4 } ippmMeasure OBJECT IDENTIFIER ::= { ippmReportingMib 3 }
ippmMeasureGroup OBJECT IDENTIFIER ::= { ippmReportingMib 5 } ippmHistory OBJECT IDENTIFIER ::= { ippmReportingMib 4 }
ippmHistoryGroup OBJECT IDENTIFIER ::= { ippmReportingMib 6 } ippmNetworkMeasure OBJECT IDENTIFIER ::= { ippmReportingMib 5 }
ippmNetworkMeasureGroup OBJECT IDENTIFIER ::= { ippmReportingMib 7 } ippmAggrMeasure OBJECT IDENTIFIER ::= { ippmReportingMib 6 }
ippmAggregatedMeasureGroup OBJECT IDENTIFIER ::= { ippmReportingMib 8 } ippmReport OBJECT IDENTIFIER ::= { ippmReportingMib 7 }
ippmReportGroup OBJECT IDENTIFIER ::= { ippmReportingMib 9 }
ippmNotifications OBJECT IDENTIFIER ::= { ippmReportingMib 10 }
-- --
-- ippmSystemGroup -- ippmSystemGroup
-- --
-- --
ippmSystemTime OBJECT-TYPE ippmSystemTime OBJECT-TYPE
SYNTAX GMTTimeStamp SYNTAX GMTTimeStamp
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The current time of the measurement system." "The current time of the measurement system."
::= { ippmSystemGroup 1 } ::= { ippmSystem 1 }
ippmSystemSynchronizationType OBJECT-TYPE ippmSystemSynchronizationType OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
other(0), other(0),
ntp(1), ntp(1),
gps(2), gps(2),
cdma(4) cdma(3)
} }
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"ippmSystemSynchronizationType describes the mechanism "ippmSystemSynchronizationType describes the mechanism
used to synchronize the system. used to synchronize the system.
Other(0) Other(0)
The synchronization process must be defined The synchronization process must be defined
in the ippmSystemSynchonizationDescription. in the ippmSystemSynchonizationDescription.
Ntp(1) Ntp(1)
The system is synchronized using the network The system is synchronized using the network
time protocol. The NTP synchronization must be described time protocol. The NTP synchronization must be described
in the ippmSystemSynchonizationDescription. in the ippmSystemSynchonizationDescription.
Gps (2) Gps (2)
The system is synchronized using the GPS clocks. The system is synchronized using the GPS clocks.
Cdma(4) Cdma(3)
The system is synchronized using the CDMA clocks. The system is synchronized using the CDMA clocks."
" ::= { ippmSystem 2 }
::= { ippmSystemGroup 2 }
ippmSystemSynchronizationDescription OBJECT-TYPE ippmSystemSynchronizationDesc OBJECT-TYPE
SYNTAX SnmpAdminString SYNTAX SnmpAdminString
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The description of the synchronization process." "The description of the synchronization process."
::= { ippmSystemGroup 3 } ::= { ippmSystem 3 }
ippmSystemClockResolution OBJECT-TYPE ippmSystemClockResolution OBJECT-TYPE
SYNTAX Integer32 SYNTAX Integer32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"ippmSystemClockResolution provides the precision of the clock used for the measures. "ippmSystemClockResolution provides the precision of the clock
The unit is the picosecond. For example, the clock on an old Unix host might advance used for the measures. The unit is the picosecond. For example,
only once every 10 msec, and thus have a resolution of only 10 msec. So its resolution the clock on an old Unix host might advance only once every 10
is 100000 picosecond and the value of ippmSystemClockResolution is 100000." msec, and thus have a resolution of only 10 msec. So its
::= { ippmSystemGroup 4 } resolution is 100000 picosecond and the value of
ippmSystemClockResolution is 100000."
::= { ippmSystem 4 }
ippmSystemCurrentSynchronization OBJECT-TYPE ippmSystemCurrentSynchronization OBJECT-TYPE
SYNTAX Integer32 SYNTAX Integer32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The index on the last synchronization event in the ippmSynchronizationTable." "The index on the last synchronization event in the
ippmSynchronizationTable."
::= { ippmSystemGroup 5 } ::= { ippmSystem 5 }
ippmSynchronizationTable OBJECT-TYPE ippmSynchronizationTable OBJECT-TYPE
SYNTAX SEQUENCE OF IppmSynchronizationEntry SYNTAX SEQUENCE OF IppmSynchronizationEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table registers the event related to the synchronization of the point of "This table registers the event related to the synchronization of
measure. Each event is described in an ippmSynchronizationEntry. the point of measure. Each event is described in an
ippmSynchronizationEntry.
ippmSynchronizationTable is mandatory. ippmSynchronizationTable is mandatory.
ippmSynchronizationTable content is read only. ippmSynchronizationTable content is read only."
" ::= { ippmSystem 6 }
::= { ippmMeasureGroup 6 }
ippmSynchronizationEntry OBJECT-TYPE ippmSynchronizationEntry OBJECT-TYPE
SYNTAX IppmSynchronizationEntry SYNTAX IppmSynchronizationEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry describes a modification of the synchronization status. " "An entry describes a modification of the synchronization status.
"
INDEX { ippmSynchronizationIndex } INDEX { ippmSynchronizationIndex }
::= { ippmSynchronizationTable 1 } ::= { ippmSynchronizationTable 1 }
IppmSynchronizationEntry ::= IppmSynchronizationEntry ::=
SEQUENCE { SEQUENCE {
ippmSynchronizationIndex Integer32, ippmSynchronizationIndex Integer32,
ippmSynchronizationTime GMTTimeStamp, ippmSynchronizationTime GMTTimeStamp,
ippmSynchronizationStratum Integer32 ippmSynchronizationStratum Integer32,
ippmSynchronizationResolution Integer32
} }
ippmSynchronizationIndex OBJECT-TYPE ippmSynchronizationIndex OBJECT-TYPE
SYNTAX Integer32 (1..1000) SYNTAX Integer32 (1 .. 65535)
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An index that identifies the synchronization events in chronological order." "An index that identifies the synchronization events in
chronological order."
::= { ippmSynchronizationEntry 1 } ::= { ippmSynchronizationEntry 1 }
ippmSynchronizationTime OBJECT-TYPE ippmSynchronizationTime OBJECT-TYPE
SYNTAX GMTTimeStamp SYNTAX GMTTimeStamp
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The time when the synchronization event occurs." "The time when the synchronization event occurs."
::= { ippmSynchronizationEntry 2 } ::= { ippmSynchronizationEntry 2 }
ippmSynchronizationStratum OBJECT-TYPE ippmSynchronizationStratum OBJECT-TYPE
SYNTAX Integer32 SYNTAX Integer32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The stratum level of the clock computed when the synchronization event occurs." "The stratum level of the clock computed when the synchronization
event occurs."
::= { ippmSynchronizationEntry 3 } ::= { ippmSynchronizationEntry 3 }
ippmSynchronizationResolution OBJECT-TYPE
SYNTAX Integer32
UNITS "NanoSeconds"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The new time resolution computed after the synchronization event
occured."
::= { ippmSynchronizationEntry 4 }
ippmPointOfMeasureTable OBJECT-TYPE ippmPointOfMeasureTable OBJECT-TYPE
SYNTAX SEQUENCE OF IppmPointOfMeasureEntry SYNTAX SEQUENCE OF IppmPointOfMeasureEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
" A lookup table that identifies the management software in charge of the point of " A lookup table that identifies the management software in
measures. charge of the point of measures.
ippmPointOfMeasureTable content is read only. It means that the measurement software
handles the table internally
ippmPointOfMeasureTable is mandatory. ippmPointOfMeasureTable content is read only. It means that the
" measurement software handles the table internally
::= { ippmSystemGroup 6 } ippmPointOfMeasureTable is mandatory."
::= { ippmSystem 7 }
ippmPointOfMeasureEntry OBJECT-TYPE ippmPointOfMeasureEntry OBJECT-TYPE
SYNTAX IppmPointOfMeasureEntry SYNTAX IppmPointOfMeasureEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
" An entry may be the management address of a middleware in charge of the management " An entry may be the management address of a middleware in
of a set of probes. It may the management address of a probe that contains several charge of the management of a set of probes. It may the
line cards. 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 An entry describes the capability of a point of measure. The
use of wildcards to define multiple capabilities. description may make the use of wildcards to define multiple
" capabilities."
INDEX { ippmPointOfMeasureIndex } INDEX { ippmPointOfMeasureIndex }
::= { ippmPointOfMeasureTable 1 } ::= { ippmPointOfMeasureTable 1 }
IppmPointOfMeasureEntry ::= IppmPointOfMeasureEntry ::=
SEQUENCE { SEQUENCE {
ippmPointOfMeasureIndex Integer32, ippmPointOfMeasureIndex Integer32,
ippmPointOfMeasureMgmtAddress SnmpAdminString, ippmPointOfMeasureMgmtAddrType InetAddressType,
ippmPointOfMeasureMgmtAddress InetAddress,
ippmPointOfMeasureTypePAddress TypeP, ippmPointOfMeasureTypePAddress TypeP,
ippmPointOfMeasureAddress OCTET STRING ippmPointOfMeasureAddress InetAddress
} }
ippmPointOfMeasureIndex OBJECT-TYPE ippmPointOfMeasureIndex OBJECT-TYPE
SYNTAX Integer32 (1.. 65535) SYNTAX Integer32 (1.. 65535)
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The index of the entry." "The index of the entry."
::= { ippmPointOfMeasureEntry 1 } ::= { ippmPointOfMeasureEntry 1 }
ippmPointOfMeasureMgmtAddrType OBJECT-TYPE
SYNTAX InetAddressType
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The type of address associated with management address"
::= { ippmPointOfMeasureEntry 2 }
ippmPointOfMeasureMgmtAddress OBJECT-TYPE ippmPointOfMeasureMgmtAddress OBJECT-TYPE
SYNTAX SnmpAdminString SYNTAX InetAddress (SIZE (1..128))
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
" "The management address on the point of measure"
The management software in charge of this point of measure." ::= { ippmPointOfMeasureEntry 3 }
::= { ippmPointOfMeasureEntry 2 }
ippmPointOfMeasureTypePAddress OBJECT-TYPE ippmPointOfMeasureTypePAddress 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 address of the point of measure." "Defines the type P of the address of the point of measure."
DEFVAL { '04000080001000'H } -- ->ip: 4.0.0.8.0.1.0 DEFVAL { "ip" }
::= { ippmPointOfMeasureEntry 3 } ::= { ippmPointOfMeasureEntry 4 }
ippmPointOfMeasureAddress OBJECT-TYPE ippmPointOfMeasureAddress OBJECT-TYPE
SYNTAX OCTET STRING SYNTAX InetAddress
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Specifies the address of the point of measure. "Specifies the address of the point of measure.
It is represented as an octet string with specific semantics and length as identified It is represented as an octet string with specific semantics and
by the ippmPointOfMeasureTypePAddress. length as identified by the ippmPointOfMeasureTypePAddress.
For example, if the ippmPointOfMeasureTypePAddress indicates an encapsulation of 'ip', For example, if the ippmPointOfMeasureTypePAddress indicates an
this object length is 4, followed by the 4 octets of the IP address, in network byte encapsulation of 'ip', this object length is 4, followed by the 4
order." octets of the IP address, in network byte order."
DEFVAL { '04C0210415'H } -- -> ip: 192.33.4.21 ::= { ippmPointOfMeasureEntry 5}
::= { ippmPointOfMeasureEntry 4}
-- --
-- ippmOwnersGroup -- ippmOwnersGroup
-- --
-- The ippmOwnersGroup objects are responsible for managing -- The ippmOwners 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 management entity wishing to create and activate remote Ippm measurements in an "A management entity wishing to create and activate remote Ippm
agent must previously be registered in the ippmOwnersTable. measurements in an agent must previously be registered in the
ippmOwnersTable.
ippmOwnersTable content is read-create. ippmOwnersTable content is read-create. It contains at least the
owner 'monitor'. It is mandatory, except if the VACM framework is
ippmOwnersTable contains at least the owner 'monitor'. used."
::= { ippmOwners 1 }
ippmOwnersTable is mandatory, excepted if the VACM framework is used.
"
::= { 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 granted to an SNMP application. "The description of the resources granted to an SNMP application.
For example, an instance of ippmOwnersOwner with an OwnerString 'acme', which For example, an instance of ippmOwnersOwner with an
represents the 14th owner created in ippmOwnersTable would be named IppmOwnerString 'acme', which represents the 14th owner created
ippmOwnersEntryOwner.14. in ippmOwnersTable would be named ippmOwnersEntryOwner.14.
Notes: Notes:
The ippmOwnersIndex value is a local index managed directly by the agent. The The ippmOwnersIndex value is a local index managed directly by
management application must poll to get the next available index value. the agent. The management application must poll to get the next
available index value.
It is not used in anyway in the 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 SnmpAdminString,
ippmOwnersIndex Integer32, ippmOwnersIndex Integer32,
ippmOwnersOwner SnmpAdminString,
ippmOwnersGrantedMetrics IppmStandardMetrics, ippmOwnersGrantedMetrics IppmStandardMetrics,
ippmOwnersGrantedRules BITS, ippmOwnersGrantedRules BITS,
ippmOwnersIpAddress InetAddressType, ippmOwnersIpAddressType InetAddressType,
ippmOwnersIpAddress InetAddress,
ippmOwnersEmail SnmpAdminString, ippmOwnersEmail SnmpAdminString,
ippmOwnersSMS SnmpAdminString, ippmOwnersSMS SnmpAdminString,
ippmOwnersStatus OwnerString ippmOwnersStatus RowStatus
} }
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 table" "An arbitrary index that identifies an entry in this table"
::= { ippmOwnersEntry 1 } ::= { ippmOwnersEntry 1 }
ippmOwnersOwner OBJECT-TYPE ippmOwnersOwner OBJECT-TYPE
SYNTAX SnmpAdminString SYNTAX SnmpAdminString
MAX-ACCESS read-create 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
skipping to change at page 35, line 26 skipping to change at page 36, line 25
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(3), sender(3),
receive(4), receiver(4),
report(5), report(5),
alarm(6) alarm(6)
} }
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Defines the rules this owner may act on in the current IPPM MIB instance. "Defines the rules this owner may act on in the current IPPM MIB
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 access are The measures (not only the metrics) that this owner may access
setup by the manager of the point of measure. The owner can not add new measures for are setup by the manager of the point of measure. The owner can
these metrics. The creation and the configuration of the measures corresponding to not add new measures for these metrics. The creation and the
these metrics are managed by the manager of the point of measure. configuration of the measures corresponding to these metrics are
managed by the manager of the point of measure.
permanent(2): permanent(2):
The measures (not only the metrics) that this owner may access are The measures (not only the metrics) that this owner may access
determined by the manager of the point of measure. The owner can not add new measures are determined by the manager of the point of measure. The owner
for these metrics. The creation and the first configuration of the measures can not add new measures for these metrics. The creation and the
corresponding to these metrics are managed by the manager of the point of measure. The first configuration of the measures corresponding to these
owner may modify the measures parameters of the entries of the corresponding metrics are managed by the manager of the point of measure. The
ippmMeasureEntry whose access is read-write. owner may modify the measures parameters of the entries of the
Typically this allows the owner to suspend the measures, to change the beginning and corresponding ippmMeasureEntry whose access is read-write.
end of the measures. Typically this allows the owner to suspend the measures, to
change the beginning and end of the measures.
sender(3): sender(3):
The owner may only activate measures for those metrics that send
packets from the current point of measure. This flag is only suitable for network
measures. It shall be ignored for derived metrics.
receiver(2):
The owner may only activate measures for those metrics that receive The owner may only activate measures for those metrics that send
packets on the current point of measure. This flag is only suitable for network packets from the current point of measure. This flag is only
measures. It shall be ignored for derived metrics. Such control increases the suitable for network measures. It shall be ignored for derived
security. The owner may not generate packets from the probe. metrics.
receiver(4):
The owner may only activate measures for those metrics that
receive packets on the current point of measure. This flag is
only suitable for network measures. It shall be ignored for
derived metrics. Such control increases the security. The owner
may not generate packets from the probe.
report(4): report(5):
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(6):
The owner may setup alarms on the results of the measures metrics. The owner may setup alarms on the results of the measures
metrics.
e.g.: e.g.:
if the owner Acme is granted with the metric Instantaneous-Unidirectional-Connectivity if the owner Acme is granted with the metric Instantaneous-
as a Receiver in the current point of measure, then Acme can not setup a Unidirectional-Connectivity as a Receiver in the current point of
Instantaneous-Unidirectional-Connectivity to another point of measure. measure, then Acme can not setup a Instantaneous-Unidirectional-
" Connectivity to another point of measure."
DEFVAL { 1 } DEFVAL { 1 }
::= { ippmOwnersEntry 4 } ::= { ippmOwnersEntry 4 }
ippmOwnersIpAddress OBJECT-TYPE ippmOwnersIpAddressType OBJECT-TYPE
SYNTAX InetAddressType SYNTAX InetAddressType
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The IP address of the management entity corresponding to this "The IP address type of the management entity corresponding to
owner. The address is human readable and is represented using the dot format." this owner."
::= { ippmOwnersEntry 5 } ::= { ippmOwnersEntry 5 }
ippmOwnersIpAddress OBJECT-TYPE
SYNTAX InetAddress (SIZE (1..128))
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The IP address of the management entity corresponding to this
owner. The address is human readable and is represented using the
dot format."
::= { ippmOwnersEntry 6 }
ippmOwnersEmail OBJECT-TYPE ippmOwnersEmail OBJECT-TYPE
SYNTAX SnmpAdminString SYNTAX SnmpAdminString
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The email address of the management entity corresponding to this "The email address of the management entity corresponding to this
owner." owner."
::= { ippmOwnersEntry 6 } ::= { ippmOwnersEntry 7 }
ippmOwnersSMS OBJECT-TYPE ippmOwnersSMS OBJECT-TYPE
SYNTAX SnmpAdminString SYNTAX SnmpAdminString
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The SMS phone number of the management entity corresponding to "The SMS phone number of the management entity corresponding to
this owner." this owner."
::= { ippmOwnersEntry 7 } ::= { ippmOwnersEntry 8 }
ippmOwnersStatus OBJECT-TYPE ippmOwnersStatus OBJECT-TYPE
SYNTAX RowStatus SYNTAX RowStatus
MAX-ACCESS read-create 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 9 }
-- --
-- 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 owner to the measure results of " The ippmResultSharingTable controls the access of an owner to
other owners. An owner may grant another access to read the result of its measure. the measure results of other owners. An owner may grant another
access to read the result of its measure.
Entries may exist in ippmResultSharingTable even if the measures to be shared are not
yet defined. Deleting a measure entry in the ippmMeasureTable does not delete the
entries corresponding to this measure in the ippmResultSharingTable.
IppmResultSharingTable is optional. Entries may exist in ippmResultSharingTable even if the measures
IppmResultSharingTable content is read-create. to be shared are not yet defined. Deleting a measure entry in the
ippmMeasureTable does not delete the entries corresponding to
this measure in the ippmResultSharingTable. This table is
optional.
If this table is not implemented then the owner has only access to its own measurement ippmResultSharingTable content is read-create.
results."
::= { ippmOwnersGroup 2 } If this table is not implemented then the owner has only access
to its own measurement results."
::= { ippmOwners 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 measure owned by another owner. "An entry allows an owner to read the results of a 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 management station. 2) Reading the results from a remote management station.
Example: if acme.12 is a One-way-Delay(6) measure, Acme may allow Peter to make Example: if acme.12 is a One-way-Delay(6) measure, Acme may allow
derived metrics on the results of this measure. Peter to make derived metrics on the results of this measure."
"
INDEX { ippmResultSharingOwner, ippmResultSharingIndex} INDEX { ippmResultSharingOwner, ippmResultSharingIndex}
::= { ippmResultSharingTable 1 } ::= { ippmResultSharingTable 1 }
IppmResultSharingEntry ::= SEQUENCE { IppmResultSharingEntry ::= SEQUENCE {
ippmResultSharingOwner OwnerString, ippmResultSharingOwner IppmOwnerString,
ippmResultSharingIndex Integer32, ippmResultSharingIndex Integer32,
ippmResultSharingMeasureOwner OwnerString, ippmResultSharingMeasureOwner IppmOwnerString,
ippmResultSharingMeasureIndex Integer32, ippmResultSharingMeasureIndex Integer32,
ippmResultSharingGrantedOwner OwnerString, ippmResultSharingGrantedOwner IppmOwnerString,
ippmResultSharingStatus RowStatus ippmResultSharingStatus RowStatus
} }
ippmResultSharingOwner OBJECT-TYPE ippmResultSharingOwner OBJECT-TYPE
SYNTAX OwnerString SYNTAX IppmOwnerString
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
" The owner of this result control entry. Typically the owner who " The owner of this result control entry. Typically the 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 not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
" The index of this result control entry. The value is managed by " The index of this result control entry. The value is managed by
the owner. On creation a SNMP error 'inconsistentValue' is returned if this value is the owner. On creation a SNMP error 'inconsistentValue' is
already in use by this owner." returned if this value is already in use by this owner."
::= { ippmResultSharingEntry 2 } ::= { ippmResultSharingEntry 2 }
ippmResultSharingMeasureOwner OBJECT-TYPE ippmResultSharingMeasureOwner OBJECT-TYPE
SYNTAX OwnerString SYNTAX IppmOwnerString
MAX-ACCESS read-create 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 identifies absolutely a ippmResultSharingMeasureOwner, ippmResultSharingMeasureIndex
measure" identifies absolutely a measure"
::= { ippmResultSharingEntry 3 } ::= { ippmResultSharingEntry 3 }
ippmResultSharingMeasureIndex OBJECT-TYPE ippmResultSharingMeasureIndex OBJECT-TYPE
SYNTAX Integer32 (1.. 65535) SYNTAX Integer32 (1.. 65535)
MAX-ACCESS read-create 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 IppmOwnerString
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The owner who is granted access to the result of the measure "The owner who is granted access to the result of the measure
described by the couple ippmResultSharingMeasureOwner, ippmResultSharingMeasureIndex." described by the couple ippmResultSharingMeasureOwner,
ippmResultSharingMeasureIndex."
::= { ippmResultSharingEntry 5 } ::= { ippmResultSharingEntry 5 }
ippmResultSharingStatus OBJECT-TYPE ippmResultSharingStatus OBJECT-TYPE
SYNTAX RowStatus SYNTAX RowStatus
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
" The status of this table entry. Once the entry status is set to " The status of this table entry. Once the entry status is set to
active." active."
::= { ippmResultSharingEntry 6 } ::= { ippmResultSharingEntry 6 }
-- --
-- --
-- --
-- ippmMeasureGroup -- ippmMeasureGroup
-- --
-- --
-- --
ippmMetricsTable OBJECT-TYPE ippmMetricTable OBJECT-TYPE
SYNTAX SEQUENCE OF IppmMetricsEntry SYNTAX SEQUENCE OF IppmMetricEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table describes the current implementation and is mandatory. Each IPPM "This table describes the current implementation and is
standardized metric identified in the IPPM-METRICS-REGISTRY must be described in the mandatory. Each IPPM standardized metric must be described in the
table. The index of the metric corresponds to the node number of the metric in the rfc table.
subtree of the IPPM-METRICS-REGISTRY. That provides a metric with the same index value
in any IPPM REPORTING MIB implementations.
ippmMetricsTable is mandatory. In reporting mode, the entries of this table may be not
ippmMetricsTable content is read only. accessible. It means that the measurement software handles the
" table internally.
::= { ippmMeasureGroup 1 }
ippmMetricsEntry OBJECT-TYPE ippmMetricTable is mandatory.
SYNTAX IppmMetricsEntry ippmMetricTable content is read only."
::= { ippmMeasure 1 }
ippmMetricEntry OBJECT-TYPE
SYNTAX IppmMetricEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry describes the static capabilities of a metric implementation." "An entry describes the static capabilities of a metric
INDEX { ippmMetricsIndex } implementation."
::= { ippmMetricsTable 1 } INDEX { ippmMetricIndex }
::= { ippmMetricTable 1 }
IppmMetricsEntry ::= IppmMetricEntry ::=
SEQUENCE { SEQUENCE {
ippmMetricsIndex Integer32, ippmMetricIndex Integer32,
ippmMetricsCapabilities INTEGER, ippmMetricCapabilities INTEGER,
ippmMetricUnit INTEGER, ippmMetricUnit INTEGER,
ippmMetricsDescription SnmpAdminString, ippmMetricDescription SnmpAdminString,
ippmMetricsMaxHistorySize Integer32 ippmMetricMaxHistorySize Integer32
} }
ippmMetricsIndex OBJECT-TYPE ippmMetricIndex OBJECT-TYPE
SYNTAX Integer32 (1.. 65535) SYNTAX Integer32 (1.. 65535)
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"ippmMetricsIndex defines an unambiguous index for each standardized metric. Its value "ippmMetricIndex defines an unambiguous index for each
is the value of the node of the metric in the IPPM-REPORTING-MIB metrics registry standardized metric. Its value is the value of the node of the
metric in the IPPM-REPORTING-MIB metrics registry
ippmMib.metrics.rfc. ippmMib.metrics.rfc.
Each metric registered in the standard registry must be present in this table. Each metric registered in the standard registry must be present
This index is used to identify the metric calculated between the IPPM-REPORTING-MIB in this table.
entities involved in the measure. This index is used to identify the metric calculated between the
IPPM-REPORTING-MIB entities involved in the measure.
Example: Example:
The index of the metric onewayPacketLossAverage which is registered as The index of the metric onewayPacketLossAverage which is
ippmMib.metrics.rfc.onewayPacketLossAverage will always have the value 14." registered as ippmMib.metrics.rfc.onewayPacketLossAverage will
::= { ippmMetricsEntry 1 } always have the value 14."
::= { ippmMetricEntry 1 }
ippmMetricsCapabilities OBJECT-TYPE ippmMetricCapabilities 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 "A value of notImplemented implies the metric is not implemented.
the metric is not implemented. A value of implemented implies the metric is implemented."
implemented
the metric is implemented."
DEFVAL { implemented } DEFVAL { implemented }
::= { ippmMetricsEntry 2 } ::= { ippmMetricEntry 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(7), byte(7),
kbyte(8), kbyte(8),
megabyte(9) 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 measurement of this "The unit used in the current entity for the results of the
metric." measurement of this metric."
::= { ippmMetricsEntry 3 } ::= { ippmMetricEntry 3 }
ippmMetricsDescription OBJECT-TYPE ippmMetricDescription OBJECT-TYPE
SYNTAX SnmpAdminString 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."
::= { ippmMetricsEntry 4 } ::= { ippmMetricEntry 4 }
ippmMetricsMaxHistorySize OBJECT-TYPE ippmMetricMaxHistorySize 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 measure can "Specifies the maximum number of results that a metric measure
save in the ippmHistoryTable." can save in the ippmHistoryTable."
DEFVAL { 200 } DEFVAL { 200 }
::= { ippmMetricsEntry 5 } ::= { ippmMetricEntry 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 device. They may not all "The table of all the IPPM measures which are running in the
be active. device. They may not all be active.
A measure consists of a subset of metrics to compute. The results of the measure may A measure consists of a subset of metrics to compute. The results
be saved in the ippmHistoryTable. The configuration of the measure sets the size of of the measure may be saved in the ippmHistoryTable. The
the history requested in ippmMeasureHystorySize. configuration of the measure sets the size of the history
requested in ippmMeasureHistorySize.
The maximum number of MIB objects to be collected in the portion of ippmHistoryTable The maximum number of MIB objects to be collected in the portion
associated with this metric depends on the value of the ippmMetricMaxHistorySize. of ippmHistoryTable associated with this metric depends on the
value of the ippmMetricMaxHistorySize.
The value of each metric ippmMeasureHystorySize must not be over the value of The value of each metric ippmMeasureHistorySize must not be over
ippmMetricMaxHistorySize corresponding to this metric in the ippmMetricTable. the value of ippmMetricMaxHistorySize corresponding to this
metric in the ippmMetricTable.
The ippmMeasureTable is mandatory. The ippmMeasureTable is mandatory.
ippmMeasureTable content is read-create. The table is handled internally by the ippmMeasureTable content is read-create. The table is handled
measurement software for network measures. internally by the measurement software for network measures.
The setup of network is not permitted through the IPPM REPORTING MIB. OWAP provides a The setup of network is not permitted through the IPPM REPORTING
setup protocol to enable and teardown networks measures. MIB. OWAP provides a setup protocol to enable and teardown
" networks measures."
::= { ippmMeasureGroup 2 } ::= { ippmMeasure 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 measurement software. "The measure entries are created/deleted internally by the
measurement software."
"
INDEX { ippmMeasureOwner, ippmMeasureIndex } INDEX { ippmMeasureOwner, ippmMeasureIndex }
::= { ippmMeasureTable 1 } ::= { ippmMeasureTable 1 }
IppmMeasureEntry ::= IppmMeasureEntry ::=
SEQUENCE { SEQUENCE {
ippmMeasureOwner OwnerString, ippmMeasureOwner IppmOwnerString,
ippmMeasureIndex Integer32, ippmMeasureIndex Integer32,
ippmMeasureName SnmpAdminString, ippmMeasureName SnmpAdminString,
ippmMeasureMetrics IppmStandardMetrics, ippmMeasureMetrics IppmStandardMetrics,
ippmMeasureBeginTime GMTTimeStamp, ippmMeasureBeginTime GMTTimeStamp,
ippmMeasureClockPeriodUnit TimeUnit, ippmMeasureClockPeriodUnit TimeUnit,
ippmMeasureClockPeriod Integer32, ippmMeasureClockPeriod Integer32,
ippmMeasureDurationUnit TimeUnit, ippmMeasureDurationUnit TimeUnit,
ippmMeasureDuration Integer32, ippmMeasureDuration Integer32,
ippmMeasureHystorySize Integer32, ippmMeasureHistorySize Integer32,
ippmMeasureStorageType StorageType, ippmMeasureStorageType StorageType,
ippmMeasureStatus RowStatus ippmMeasureStatus RowStatus
} }
ippmMeasureOwner OBJECT-TYPE ippmMeasureOwner OBJECT-TYPE
SYNTAX OwnerString SYNTAX IppmOwnerString
MAX-ACCESS not-accessible 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" }
::= { ippmMeasureEntry 1 } ::= { ippmMeasureEntry 1 }
ippmMeasureIndex OBJECT-TYPE ippmMeasureIndex OBJECT-TYPE
SYNTAX Integer32 (1.. 65535) SYNTAX Integer32 (1.. 65535)
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The owner index of the measure. The value is managed by the owner." "The owner index of the measure. The value is managed by the
owner."
::= { ippmMeasureEntry 2 } ::= { ippmMeasureEntry 2 }
ippmMeasureName OBJECT-TYPE ippmMeasureName OBJECT-TYPE
SYNTAX SnmpAdminString SYNTAX SnmpAdminString
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The name of the instance of the metric. It illustrates the specificity of the metric "The name of the instance of the metric. It illustrates the
and includes the metric and the typeP. specificity of the metric and includes the metric 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-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Defines the metrics to compute within this measure. A measure may be configured for "Defines the metrics to compute within this measure. A measure
the result of different metric singletons to be archived in the ippmHistoryTable. The may be configured for the result of different metric singletons
ippmMetricsIndex of the created result has the value of the bit index of the to be archived in the ippmHistoryTable. The ippmMetricIndex of
corresponding ippmMeasureMetrics as explained above in the IppmMetricsEntry the created 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-Packet-Loss(12) generated a flow of A measure asking for One-way-Delay(6) and One-way-Packet-Loss(12)
singletons which are logged in the ippmHistoryTable. The singletons created for the generated a flow of singletons which are logged in the
One-way-Delay measure have a value of IppmMetricsIndex of 6 while the created ippmHistoryTable. The singletons created for the One-way-Delay
singletons for the One-way-Packet-Loss measure have a value of IppmMetricsIndex of measure have a value of ippmMetricIndex of 6 while the created
12." singletons for the One-way-Packet-Loss measure have a value of
DEFVAL { { one-way-Delay, one-way-Packet-Loss } } ippmMetricIndex of 12."
-- { one-way-Delay, one-way-Packet-Loss }
DEFVAL { '0001000001000000'b }
::= { ippmMeasureEntry 4 } ::= { ippmMeasureEntry 4 }
ippmMeasureBeginTime OBJECT-TYPE ippmMeasureBeginTime OBJECT-TYPE
SYNTAX GMTTimeStamp SYNTAX GMTTimeStamp
MAX-ACCESS read-create 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 }
skipping to change at page 43, line 43 skipping to change at page 45, line 40
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-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Specifies the amount of time between 2 measurement action intervals. The action is "Specifies the amount of time between 2 measurement action
specific to the semantic of the measure. intervals. The action is specific to the semantic of the measure.
Network metrics: Network metrics:
The ippmNetworkMeasureClockPattern transforms the flow of periodical instants as a The ippmNetworkMeasureClockPattern transforms the flow of
flow of unpredictable instants of measurement packet emission. periodical instants as a flow of unpredictable instants of
measurement packet emission.
As the source and the sink share the definition of the clock of the measure, as the As the source and the sink share the definition of the clock of
sending timestamp is part of the measurement packet, the sink have the information to the measure, as the sending timestamp is part of the measurement
verify that the stream of packets generated by the source respects the clock law. packet, the sink have the information 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 of other measures. The period They are performed periodically on a sequence of results of other
corresponds to the interval between two successive computations of the metric. The measures. The period corresponds to the interval between two
value of ippmHistoryTimestamp result of a aggregated metric computed corresponds to successive computations of the metric. The value of
the value of the ippmHistoryTimestamp of the last metric result of the sequence used ippmHistoryTimestamp result of a aggregated metric computed
in to compute the aggregated metric." corresponds to the value of the ippmHistoryTimestamp of the last
metric result of the sequence used in to compute the aggregated
metric."
DEFVAL { 60 } DEFVAL { 60 }
::= { ippmMeasureEntry 7 } ::= { ippmMeasureEntry 7 }
ippmMeasureDurationUnit OBJECT-TYPE ippmMeasureDurationUnit OBJECT-TYPE
SYNTAX TimeUnit SYNTAX TimeUnit
MAX-ACCESS read-create 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-create MAX-ACCESS read-create
skipping to change at page 44, line 32 skipping to change at page 46, line 35
ippmMeasureDuration OBJECT-TYPE ippmMeasureDuration OBJECT-TYPE
SYNTAX Integer32 SYNTAX Integer32
MAX-ACCESS read-create 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 ippmMeasureHistorySize OBJECT-TYPE
SYNTAX Integer32 SYNTAX Integer32
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Specifies the maximum number of results saved for each metric of this measure. The "Specifies the maximum number of results saved for each metric of
history of each metric is managed as a circular table. The newest result overwrites this measure. The history of each metric is managed as a circular
the oldest one when the history granted to this metric measure is full. table. The newest result overwrites the oldest one when the
history granted to this metric measure is full.
The management of the results may be optimized if synchronized with the reports steps The management of the results may be optimized if synchronized
of this measure. with the reports steps of this measure. "
"
DEFVAL { 120 } DEFVAL { 120 }
::= { ippmMeasureEntry 10 } ::= { ippmMeasureEntry 10 }
ippmMeasureStorageType OBJECT-TYPE ippmMeasureStorageType OBJECT-TYPE
SYNTAX StorageType SYNTAX StorageType
MAX-ACCESS read-create 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
controlled by this row are kept in volatile storage and by this row are kept in volatile storage and lost upon reboot or
lost upon reboot or if this row is backed up by if this row is backed up
non-volatile or permanent storage. by non-volatile or permanent storage.
Possible values are: other(1), volatile(2), nonVolatile(3), permanent(4), readOnly(5)" Possible values are: other(1), volatile(2), nonVolatile(3),
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-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The status of this table entry. Once the entry status is set to active, the associate "The status of this table entry. Once the entry status is set to
entry cannot be modified." active, the associate entry cannot be modified."
::= { ippmMeasureEntry 12 } ::= { ippmMeasureEntry 12 }
-- --
-- ippmHistoryGroup -- ippmHistoryGroup
-- --
-- --
-- --
-- ippmHistoryTable -- ippmHistoryTable
-- --
ippmHistoryTable OBJECT-TYPE ippmHistoryTable OBJECT-TYPE
SYNTAX SEQUENCE OF IppmHistoryEntry SYNTAX SEQUENCE OF IppmHistoryEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The table of the results of the measures." "The table of the results of the measures."
::= { ippmHistory 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 measure
"An ippmHistoryEntry entry is one of the results of a measure identified by the index identified by ippmMeasureOwner, ippmMeasureIndex, ippmMetricIndex
members ippmMeasureOwner and ippmMeasureIndex. and ippmHistoryIndex.
In the index : In the index :
+ ippmMeasureOwner and ippmMeasureIndex identify the ippmMeasureEntry on + ippmMeasureOwner identifies the owner of the measure;
whose behalf this entry was created
+ IppmMetricsIndex identifies the ippmMetricsEntry of the metric to measure
+ ippmHistorySqceNdx value is the absolute time when the result of the metric
was measured.
The ippmHistoryTimestamp value is the absolute time when the ippmHistoryValue was
performed.
IppmHistoryValue is the value of the metric measured at the time ippmHistoryTimestamp. + ippmMeasureIndex identifies the measure in the owner namespace;
Example: <TODO provide an example with a stream of one way result for the same + ippmMetricIndex identifies the metric measured in
measure> ippmMetricTable;
A one way delay measure is created by the entity 'acme' using the owner index 1 and
setting the 6th bit (corresponding to One-way-Delay) of ippmMeasureMetrics to 1.
Consider that the first result of the one way delay measured for acme on the day 15 of
June at 8h20mn 10s 50ms is 23. The result is identified as the singleton
ippmHistoryValue.acme.1.6.1 and stored with value 23.
Its value may be retrieved using a get-next(ippmHistoryValue.acme.1.6) which returns + ippmHistoryIndex is the local index of the result on the
(ippmHistoryValue.acme.1.6.1 == 23). The IppmMetricsIndex value of '6' corresponds to history table."
the 6th metric of ippmMetricsTable which is Type-P-One-way-Delay. INDEX { ippmMeasureOwner, ippmMeasureIndex, ippmMetricIndex,
" ippmHistoryIndex }
INDEX { ippmMeasureOwner, ippmMeasureIndex, ippmMetricsIndex,
ippmHistorySqceNdx }
::= { ippmHistoryTable 1 } ::= { ippmHistoryTable 1 }
IppmHistoryEntry ::= IppmHistoryEntry ::=
SEQUENCE { SEQUENCE {
ippmHistorySqceNdx Integer32, ippmHistoryIndex Integer32,
ippmHistorySequence Integer32,
ippmHistoryTimestamp GMTTimeStamp, ippmHistoryTimestamp GMTTimeStamp,
ippmHistoryValue Integer32 ippmHistoryValue Integer32
} }
ippmHistorySqceNdx OBJECT-TYPE
SYNTAX Integer32 (0..65536) ippmHistoryIndex OBJECT-TYPE
SYNTAX Integer32 (1.. 65535)
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
" A local index that only identifies a result in the history
table."
::= { ippmHistoryEntry 1 }
" ippmHistorySqceNdx is the sequence index of the measurement ippmHistorySequence OBJECT-TYPE
SYNTAX Integer32 (1.. 65535)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"ippmHistorySequence is the sequence index of the 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
the packet in the stream of packets sends by the source. by 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 2 }
::= { ippmHistoryEntry 1 }
ippmHistoryTimestamp OBJECT-TYPE ippmHistoryTimestamp OBJECT-TYPE
SYNTAX GMTTimeStamp SYNTAX GMTTimeStamp
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The instant of the measure of the result." "The instant of the measure of the result."
::= { ippmHistoryEntry 2 } ::= { ippmHistoryEntry 3 }
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 4 }
ippmOnHistoryFullAction OBJECT-TYPE
SYNTAX INTEGER {
wrap(1),
suspend(2),
resume(3)
}
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"Action to take when the history log is full. The user may choose
to either wrap, in which case the agent writes over existing
records. The user may choose to suspend writing to the log in the
event that he wishes to archive the data. The resume action
causes the agent to begin to write in the history log, and
assumes the data has been cleared."
::= { ippmHistory 2 }
-- --
-- ippmNetworkMeasureGroup -- ippmNetworkMeasureGroup
-- --
-- --
-- --
-- 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 and provides a flow of results. "A entry is a measure which performs network measures and
provides a flow of results.
This table extends the ippmMeasureTable. A network measure is a specific measure. This table extends the ippmMeasureTable.
It performs several metric measurements per packet exchange. Each step of a measure It performs several metric measurements per packet exchange. Each
produces a singleton result per metric. The time of the measure and the value of the step of a measure produces a singleton result per metric. The
metric are saved in the ippmHistoryTable." time of the measure and the value of the metric are saved in the
::= { ippmNetworkMeasureGroup 1 } ippmHistoryTable."
::= { ippmNetworkMeasure 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 values of the new " Typically the configuration operation sets both the values of
ippmMeasureEntry and of the new IppmNetworkMeasureEntry. the new ippmMeasureEntry and of the new IppmNetworkMeasureEntry.
IppmNetworkMeasureTable is mandatory. IppmNetworkMeasureTable is mandatory.
IppmNetworkMeasureTable content is read only. It means that the measurement software IppmNetworkMeasureTable content is read only. It means that the
handles the table internally. The setup of network is not permitted through the IPPM measurement software handles the table internally. The setup of
REPORTING MIB. OWAP provides a setup protocol to enable and teardown networks network is not permitted through the IPPM REPORTING MIB. OWAP
provides a setup protocol to enable and teardown networks
measures. measures.
The ippmMeasureMetrics is set to a list of metrics to be computed from the same raw The ippmMeasureMetrics is set to a list of metrics to be computed
packet exchange. Each step of measurement delivers a singleton per chosen metric. from the same raw packet exchange. Each step of measurement
Results are timestamped and saved in the ippmHistoryTable. delivers a singleton per chosen metric. Results are timestamped
and saved in the ippmHistoryTable.
The ippmNetworkMeasureTable typical usage consists is providing network measure The ippmNetworkMeasureTable typical usage consists is providing
indexes to permits aggregated measure to perform aggregation on the results of network network measure indexes to permits aggregated measure to perform
measures. aggregation on the results of network measures.
An obvious usage of the ippmNetworkMeasureTable consists in the verification of the An obvious usage of the ippmNetworkMeasureTable consists in the
network measures states." 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 TypePaddress,
ippmNetworkMeasureDstTypeP TypeP, ippmNetworkMeasureDstTypeP TypeP,
ippmNetworkMeasureDst OCTET STRING, ippmNetworkMeasureDst TypePaddress,
ippmNetworkMeasureClockPattern OCTET STRING, ippmNetworkMeasureClockPattern OCTET STRING,
ippmNetworkMeasurePoissonRate Integer32,
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 sent by the measure." "Defines the type P of the source address of the packets 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 TypePaddress
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 a list of parameters corresponding to those
It is represented as an octet string with specific semantics and length as identified of the PROTOCOL IDENTIFIER sets in ippmNetworkMeasureSrcTypeP."
by the ippmNetworkMeasureSrcTypeP.
For example, if the ippmNetworkMeasureSrcTypeP 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
::= { 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 packets sent "Defines the type P of the destination address of the packets
by the measure." sent by the measure."
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 TypePaddress
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Specifies the address of the destination of the measure. "Specifies the address of the source of the measure.
It is represented as a list of parameters corresponding to those
It is represented as an octet string with specific semantics and length as identified of the PROTOCOL IDENTIFIER sets in ippmNetworkMeasureSrcTypeP."
by the ippmNetworkMeasureDstTypeP.
For example, if the ippmNetworkMeasureDstTypeP indicates an encapsulation of 'ip',
this object length is 4, followed by the 4 octets of the IP address, in network byte
order."
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 measurement action provided "This cyclic clock shapes the profile of the instants of
by ippmMeasureClockPeriod according to an arbitrary distribution law. The clock measurement action provided by ippmMeasureClockPeriod according
resolution is ippmMeasureClockPeriod. The bits of the clock pattern set to the value 1 to an arbitrary distribution law. The clock resolution is
determine the valid instants of measurement action. A measure is to be processed if ippmMeasureClockPeriod. The bits of the clock pattern set to the
and only if the current bit value is 1. value 1 determine the valid instants of measurement action. A
This pseudo-random clock pattern allows the configuration by the NMS of numerous kind measure is to be processed if and only if the current bit value
of time sampling law such as periodic, pseudo random or Poisson. is 1.
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 measurement packets synchronously with The source of the measure sends the stream of measurement packets
the stream of instants selected by the clock pattern sampling. synchronously with the stream of instants selected by the clock
" pattern sampling.
DEFVAL { 11111111} -- 100% periodic
ippmNetworkMeasureClockPattern can not be used conjointly with
ippmNetworkMeasurePoissonRate."
DEFVAL { "11111111" }
-- 100% periodic
::= { ippmNetworkMeasureEntry 5 } ::= { ippmNetworkMeasureEntry 5 }
ippmNetworkMeasurePoissonRate OBJECT-TYPE
SYNTAX Integer32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Indicates the average number of packets per seconds sent using a
poisson law.
ippmNetworkMeasurePoissonRate can not be used conjointly with
ippmNetworkMeasureClockPattern."
DEFVAL { 30 }
::= { ippmNetworkMeasureEntry 6 }
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 considered lost by "Specifies the delay after which the packet is considered lost by the
the sink." sink."
DEFVAL { 1 } DEFVAL { 1 }
::= { ippmNetworkMeasureEntry 6 } ::= { ippmNetworkMeasureEntry 7 }
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 network layer in regards to the "Specifies the size of the packets sent at the last network layer
TypeP definition." in regards to the TypeP definition."
DEFVAL { 64 } DEFVAL { 64 }
::= { ippmNetworkMeasureEntry 7 } ::= { ippmNetworkMeasureEntry 8 }
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 to fill the packet." "The current field defines the round robin pattern used to fill
the packet."
DEFVAL { 'FF'H } DEFVAL { 'FF'H }
::= { ippmNetworkMeasureEntry 8 } ::= { ippmNetworkMeasureEntry 9 }
-- --
-- --
-- ippmAggregatedMeasureGroup -- ippmAggrMeasure Group
-- --
-- --
-- --
-- --
-- ippmAggregatedMeasureTable -- ippmAggrMeasureTable
-- --
-- --
ippmAggregatedMeasureTable OBJECT-TYPE ippmAggrMeasureTable OBJECT-TYPE
SYNTAX SEQUENCE OF IppmAggregatedMeasureEntry SYNTAX SEQUENCE OF IppmAggrMeasureEntry
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 network or aggregated An aggregated measure summarizes the results of previous network
measures. The results may be saved in the ippmHistoryTable. or aggregated measures. The results may be saved in the
ippmHistoryTable.
Each step of the calculation for the measure produces a singleton result per metric." Each step of the calculation for the measure produces a singleton
::= { ippmAggregatedMeasureGroup 1 } result per metric."
::= { ippmAggrMeasure 1 }
ippmAggregatedMeasureEntry OBJECT-TYPE ippmAggrMeasureEntry OBJECT-TYPE
SYNTAX IppmAggregatedMeasureEntry SYNTAX IppmAggrMeasureEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Typically the configuration operation sets both the values of the new "Typically the configuration operation sets both the values of
ippmMeasureEntry and of the new IppmAggregatedMeasureEntry. the new ippmMeasureEntry and of the new IppmAggrMeasureEntry.
ippmAggregatedMeasureTable is mandatory. ippmAggrMeasureTable is mandatory.
ippmAggregatedMeasureTable content is read only. It means that the measure software ippmAggrMeasureTable content is read only. It means that the
handles the table internally. measure software 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 by: The results of the measure to summarize are identified by:
+ ippmAggregatedMeasureHistoryOwner, + ippmAggrMeasureHistoryOwner,
+ ippmAggregatedMeasureHistoryOwnerIndex and + ippmAggrMeasureHistoryOwnerIndex and
+ ippmAggregatedMeasureHistoryMetric + ippmAggrMeasureHistoryMetric
The aggregated task starts at ippmMeasureBeginTime and ends after ippmMeasureDuration. The aggregated task starts at ippmMeasureBeginTime and ends after
An aggregated result is performed and saved in the ippmHistoryTable for each ippmMeasureDuration. An aggregated result is performed and saved
ippmMeasureClockPeriod tick. in the ippmHistoryTable for each ippmMeasureClockPeriod tick. "
"
INDEX { ippmMeasureOwner, ippmMeasureIndex } INDEX { ippmMeasureOwner, ippmMeasureIndex }
::= { ippmAggregatedMeasureTable 1 } ::= { ippmAggrMeasureTable 1 }
IppmAggregatedMeasureEntry ::= IppmAggrMeasureEntry ::=
SEQUENCE { SEQUENCE {
ippmAggregatedMeasureHistoryOwner OwnerString, ippmAggrMeasureHistoryOwner IppmOwnerString,
ippmAggregatedMeasureHistoryOwnerIndex Integer32, ippmAggrMeasureHistoryOwnerIndex Integer32,
ippmAggregatedMeasureHistoryMetric Integer32, ippmAggrMeasureHistoryMetric Integer32
ippmAggregatedMeasureStatus RowStatus
} }
ippmAggregatedMeasureHistoryOwner OBJECT-TYPE ippmAggrMeasureHistoryOwner OBJECT-TYPE
SYNTAX OwnerString SYNTAX IppmOwnerString
MAX-ACCESS read-create 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 } ::= { ippmAggrMeasureEntry 1 }
ippmAggregatedMeasureHistoryOwnerIndex OBJECT-TYPE ippmAggrMeasureHistoryOwnerIndex OBJECT-TYPE
SYNTAX Integer32 (1.. 65535) SYNTAX Integer32 (1.. 65535)
MAX-ACCESS read-create 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 } ::= { ippmAggrMeasureEntry 2 }
ippmAggregatedMeasureHistoryMetric OBJECT-TYPE ippmAggrMeasureHistoryMetric OBJECT-TYPE
SYNTAX Integer32 SYNTAX Integer32
MAX-ACCESS read-create 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 } ::= { ippmAggrMeasureEntry 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 defines the results "The ippmReportSetupTable is a list of definition of reports. It
of a network or aggregated measures that are to be reported. A report is saved in the defines the results of a network or aggregated measures that are
ippmReportTable, or sent to an application using a SNMP Trap, a SNMP inform PDU, an to be reported. A report is saved in the ippmReportTable, or sent
email or a SMS. The reporting task is not intended to be a batch action processed at to an application using a SNMP Trap, a SNMP inform PDU, an email
the end of the measure. It is coupled with threshold detections and event filtering to or a SMS. The reporting task is not intended to be a batch action
deliver application level events and data, while preserving scalability. processed at the end of the measure. It is coupled with threshold
detections and event filtering to deliver application level
events and data, while preserving scalability.
It extends the definition of a measure: the definition of a measure may include the It extends the definition of a measure: the definition of a
definition of a report." measure may include the definition of a report."
::= { ippmReportGroup 1 } ::= { ippmReport 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 by the current "The report applies to the results of the measure which is
report definition. extended by the current report definition.
Typically the creation of a report sets both the values of the new measure and those Typically the creation of a report sets both the values of the
of the new IppmReportSetupEntry. new measure and those of the new IppmReportSetupEntry.
The ippmReportSetupDefinition describes the data and the events to include in the The ippmReportSetupDefinition describes the data and the events
report. The definition consists in a list of tasks to perform on the results of the to include in the report. The definition consists in a list of
measure." tasks to perform on the results of the measure.
A report is associated to a network measure or to an aggregated
measure.
Note 1 : To associate a report to an existing measure the manager
suspends the measure while setting the ippmMeasureStatus to
'notInService'. Then he setups the report fields and activates
the measure while setting the ippmMeasureStatus to 'active'.
Note 2 : A report is tied to a measure. The period of the 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, ippmReportSetupDurationThreshold Integer32,
ippmReportSetupNMS SnmpAdminString, ippmReportSetupNMS SnmpAdminString,
ippmReportSetupNotification OBJECT IDENTIFIER,
ippmReportSetupStatus RowStatus ippmReportSetupStatus RowStatus
} }
ippmReportSetupDefinition OBJECT-TYPE ippmReportSetupDefinition OBJECT-TYPE
SYNTAX IppmReportDefinition SYNTAX IppmReportDefinition
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The description of the events and actions that are used in the definition of "The description of the events and actions that are used in the
the report. definition of the report.
Send the report using the type of message selected by the bits 8 to 12. The Send the report using the type of message selected by the bits 8
report consists of the results of the measure which have been saved in the to 12. The report consists of the results of the measure which
ippmReportTable. If the onEventSendReport(7) bit is unset, the report is not saved. have been saved in the ippmReportTable. If the
onEventSendReport(7) bit is unset, the report is not saved.
The message sent is a notification defined in the ippmNotifications node. The
notification sent depends on the step of the measure:
+ Singleton events are sent using the notification ippmSingletonAlarm The message sent is a notification defined in the
ippmNotifications node. The notification sent depends on the step
of the measure:
+ Singleton events are sent using the notification
ippmSingletonAlarm
+ Exceeded events durations are sent using the notification + Exceeded events durations are sent using the notification
ippmEventsDurationExceededAlarm ippmEventsDurationExceededAlarm
+ A report of a cycle of measure is sent using the notification + A report of a cycle of measure is sent using the notification
ippmCycleOfMeasureReport ippmCycleOfMeasureReport
+ A report of a complete measure is sent using the notification + A report of a complete measure is sent using the notification
ippmCompletedMeasureReport ippmCompletedMeasureReport
Example 1: Example 1:
The setup of an alarm to be sent to the owner in a SNMP Trap each time the The report setup of an alarm to be sent to the owner in a SNMP
staircase crosses the metric threshold value of 5: Trap each time the two results are found on each side of 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 informRequestPDU per
measure cycle. It reports the staircase values corresponding to a metric threshold of The setup of a report to be sent to the owner in a SNMP
5: informRequestPDU per measure cycle. It reports the two results
found on each side of the metric threshold of 5:
ippmReportSetupMetricThreshold 5 ippmReportSetupMetricThreshold 5
ippmReportSetupDefinition { ippmReportSetupDefinition {
onMeasureCycle(2), onMeasureCycle(2),
reportOnlyUptoDownMetricResults(4), reportOnlyUptoDownMetricResults(4),
inInformRequestPDU(10), inInformRequestPDU(10),
clearHistory(13) onReportDeliveryClearHistory(13)
} }
Default report: Default report:
The default report provides the control protocol with an implicit mechanism The default report provides the control protocol with an implicit
to forward the result of a cycle of measure to the owner of the measure while deleting mechanism to forward the result of a cycle of measure to the
the results from the ippmHistoryTable on reception of the response to the owner of the measure while deleting the results corresponding to
InformRequestPDU : this cycle of measure from the ippmHistoryTable on reception of
the response to the InformRequestPDU :
ippmReportSetupDefinition { ippmReportSetupDefinition {
onMeasureCycle(2), onMeasureCycle(2),
inInformRequestPDU(10), inInformRequestPDU(10),
clearHistory(13) onReportDeliveryClearHistory(13)
} }
" "
DEFVAL { { onMeasureCycle, inInformRequestPDU, clearHistory } } ::= { DEFVAL { { onMeasureCycle, inInformRequestPDU,
ippmReportSetupEntry 1 } onReportDeliveryClearHistory} }
::= { ippmReportSetupEntry 1 }
ippmReportSetupMetricThreshold OBJECT-TYPE ippmReportSetupMetricThreshold OBJECT-TYPE
SYNTAX Integer32 SYNTAX Integer32
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An event is generated when the result of the measure exceeds the value of "An event is generated when the result of the measure exceeds the
ippmReportSetupMetricThreshold. value of ippmReportSetupMetricThreshold.
The threshold has the same unit as the metric. The metric unit is recorded in The threshold has the same unit as the metric. The metric unit is
the object ippmMetricUnit of this metric entry in the ippmMetricTable. recorded in the object ippmMetricsUnit of this metric entry in
the ippmMetricTable.
" "
::= { ippmReportSetupEntry 2 } ::= { ippmReportSetupEntry 2 }
ippmReportSetupEventsDurationThreshold OBJECT-TYPE ippmReportSetupDurationThreshold OBJECT-TYPE
SYNTAX Integer32 SYNTAX Integer32
UNITS "Seconds" UNITS "Seconds"
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An event is generated when the duration of a series of results, which are "An event is generated when contiguous results of the measure are
continuously over the metric threshold, cross over the duration of the over the ippmReportSetupMetricThreshold, during
ippmReportSetupEventsDurationThreshold. ippmReportSetupDurationThreshold seconds.
"
Performance:
To improve the performance the ippmReportSetupDurationThreshold
may have the same value as the ippmMeasurePeriod.
The default value of ippmReportSetupDurationThreshold is
ippmMeasurePeriod. That improves the performance because the
threshold comparison is synchronized with the ippmMeasurePeriod
aggregation cycle. That improves the performance because it
synchronized the report exportation with the management of the
history and report records of a measure."
DEFVAL { 15 } DEFVAL { 15 }
::= { ippmReportSetupEntry 3 } ::= { ippmReportSetupEntry 3 }
ippmReportSetupNMS OBJECT-TYPE ippmReportSetupNMS OBJECT-TYPE
SYNTAX SnmpAdminString SYNTAX SnmpAdminString
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The recipient of the report may be provided in the setup. By default the "The recipient of the report may be provided in the setup. By
recipient of the report is the owner of the measure. Its addresses are recorded in the default the recipient of the report is the owner of the measure.
ippmOwnersTable. Its addresses are recorded in the ippmOwnersTable.
The type of ippmReportSetupNMS is not InetAddress because the report may be sent using The type of ippmReportSetupNMS is not InetAddress because the
SMS or fax. report may be sent using SMS or fax.
" "
::= { ippmReportSetupEntry 4 } ::= { ippmReportSetupEntry 4 }
ippmReportSetupNotification OBJECT-TYPE
SYNTAX OBJECT IDENTIFIER
MAX-ACCESS read-create
STATUS current
DESCRIPTION
" ippmReportSetupNotification identifies the notification used to
send the report. The definition of the notification defines the
content and the format of the report. "
::= { ippmReportSetupEntry 5 }
ippmReportSetupStatus OBJECT-TYPE ippmReportSetupStatus OBJECT-TYPE
SYNTAX RowStatus SYNTAX RowStatus
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The status of this table entry. " "The status of this table entry. "
::= { ippmReportSetupEntry 5 } ::= { ippmReportSetupEntry 6 }
-- --
-- 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 results "The ippmReportTable logs the results of the reports. The results
consist of a subset of the results of a measure as described in the report definition. consist of a subset of the results of a measure as described in
The activation of an up and down filtering in the report definition limits the results the report definition. The activation of an up and down filtering
logged to those corresponding to major events. Otherwise, the ippmReportTable is in the report definition limits the results logged to those
identical to the ippmHistoryTable. corresponding to major events. Otherwise, the ippmReportTable is
" identical to the ippmHistoryTable."
::= { ippmReportGroup 2 } ::= { ippmReport 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 associated with the "A report is a list of results of a measure. This sample is
ippmReportSetupEntry which has set up the report. An ippmReportEntry entry is one of associated with the ippmReportSetupEntry which has set up the
the results of a measure to report. The measure and the report definition are report. An ippmReportEntry entry is one of the results of a
identified by the index members ippmMeasureOwner and ippmMeasureIndex. measure to report.
An ippmReportEntry entry is one of the results of a measure
identified by ippmReportOwner, ippmReportIndex, ippmReportIndex
and ippmHistoryIndex.
In the index : In the index :
+ ippmMeasureOwner and ippmMeasureIndex identify the ippmMeasureEntry and the + ippmMeasureOwner identifies the owner of the measure;
ippmReportSetupEntry on whose behalf this report was created
+ IppmMetricsIndex identifies the ippmMetricsEntry of the metric measured + ippmMeasureIndex identifies the measure in the owner namespace;
+ ippmHistorySqceNdx value is the absolute time when the result of the metric was
computed.
The ippmReportTimestamp value is the absolute time when the ippmHistoryValue + ippmMetricIndex identifies the metric measured in
was performed. ippmMetricTable;
IppmHistoryValue is the value of the metric measured at the timef
ippmReportTimestamp. + ippmReportIndex is the local index of the result on the report
" table."
INDEX { ippmMeasureOwner, ippmMeasureIndex, ippmMetricsIndex,
ippmReportSqceNdx} INDEX { ippmMeasureOwner, ippmMeasureIndex, ippmMetricIndex,
ippmReportIndex }
::= { ippmReportTable 1 } ::= { ippmReportTable 1 }
IppmReportEntry ::= IppmReportEntry ::=
SEQUENCE { SEQUENCE {
ippmReportSqceNdx Integer32, ippmReportIndex Integer32,
ippmReportSequence Integer32,
ippmReportTimestamp GMTTimeStamp, ippmReportTimestamp GMTTimeStamp,
ippmReportValue Integer32 ippmReportValue Integer32
} }
ippmReportSqceNdx OBJECT-TYPE
SYNTAX Integer32 (1..65536) ippmReportIndex OBJECT-TYPE
SYNTAX Integer32 (1.. 65535)
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The local index of the result of a metric measure"
::= { ippmReportEntry 1 }
ippmReportSequence OBJECT-TYPE
SYNTAX Integer32 (1.. 65535)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
" ippmReportSqceNdx is the sequence index of the measurement " ippmReportSequence is the sequence index of the 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 identifies the order of It's the sequence index of a measurement packet. Typically, it
the packet in the stream of packets sends by the source. identifies the order of the packet in the stream of packets sends
by the source.
Aggregated metrics: Aggregated metrics:
It is the sequence index of the aggregated metric results computed. It is the sequence index of the aggregated metric results
" computed."
::= { ippmReportEntry 1 } ::= { ippmReportEntry 2 }
ippmReportTimestamp OBJECT-TYPE ippmReportTimestamp OBJECT-TYPE
SYNTAX GMTTimeStamp SYNTAX GMTTimeStamp
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The instant of the measure of the result." "The instant of the measure of the result."
::= { ippmReportEntry 2 } ::= { ippmReportEntry 3 }
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 3 } ::= { ippmReportEntry 4 }
ippmOnReportFullAction OBJECT-TYPE
SYNTAX INTEGER {
wrap(1),
suspend(2),
resume(3)
}
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"Action to take when the report log is full. The user may choose
to either wrap, in which case the agent writes over existing
records. The user may choose to suspend writing to the log in the
event that he wishes to archive the data. The resume action
causes the agent to begin to write in the report log, and assumes
the data has been cleared."
::= { ippmReport 3 }
-- --
-- ippmNotifications -- IPPM Notifications
-- --
ippmSingletonAlarm NOTIFICATION-TYPE ippmSingletonAlarm NOTIFICATION-TYPE
OBJECTS { OBJECTS {
ippmReportSetupDefinition,
ippmReportSetupMetricThreshold,
ippmMetricUnit, ippmMetricUnit,
ippmHistoryValue ippmReportTimestamp,
ippmReportValue
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A notification sent because 2 contiguous results are on opposite sides of the metric "A notification sent because 2 contiguous results are on opposite
threshold value. sides of the metric threshold value.
The index of the included ippmReportSetupMetricThreshold object identifies the
ippmMeasureEntry and the ippmResultSetupEntry that specified the threshold.
The notification contains the instances of the ippmReportValue object that exceeded The notification contains the instances of the ippmReportValue
the threshold. The ippmHistoryTimestamp of the index identifies the time the event object that exceeded the threshold.
occurred. The notification contains the instances of the
" ippmReportTimestamp identifying the time the event occurred."
::= { ippmNotifications 1 } ::= { ippmNotifications 1 }
ippmEventsDurationExceededAlarm NOTIFICATION-TYPE ippmEventsDurationExceededAlarm NOTIFICATION-TYPE
OBJECTS { OBJECTS {
ippmReportSetupDefinition,
ippmReportSetupEventsDurationThreshold,
ippmMetricUnit, ippmMetricUnit,
ippmHistoryValue ippmReportTimestamp,
ippmReportValue
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A notification sent when the duration of contiguous raising "A notification sent when the duration of contiguous raising
ippmReportSetupMetricThreshold exceeds the ippmReportSetupEventsDurationThreshold ippmReportSetupMetricThreshold exceeds the
value. The index of the included ippmReportSetupDefinition object identifies the ippmReportSetupDurationThreshold value.
ippmMeasureEntry and the ippmResultSetupEntry that specified the report.
The notification contains the instances of the ippmReportValue objects saved in the The notification contains the instances of the ippmReportValue
ippmReportTable for this report. The ippmHistoryTimestamp of the index identifies the object that exceeded the threshold.
time theses measures results where performed.
" The notification contains the instances of the
ippmReportTimestamp identifying the time the event occurred."
::= { ippmNotifications 2 } ::= { ippmNotifications 2 }
ippmCycleOfMeasureReport NOTIFICATION-TYPE ippmCycleOfMeasureReport NOTIFICATION-TYPE
OBJECTS { OBJECTS {
ippmReportSetupDefinition,
ippmMetricUnit, ippmMetricUnit,
ippmHistoryTimestamp,
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 object identifies the
ippmMeasureEntry and the ippmResultSetupEntry that specified the report.
The notification contains the instances of the ippmReportValue objects saved in the The notification contains the instances of the ippmReportValue
ippmReportTable for this measure cycle. The ippmHistoryTimestamp of the index objects saved in the ippmReportTable for this measure cycle. The
identifies the time the measures where performed. ippmHistoryTimestamp of the index identifies the time the
" measures where performed."
::= { ippmNotifications 3 } ::= { ippmNotifications 3 }
ippmCompletedMeasureReport NOTIFICATION-TYPE ippmCompletedMeasureReport NOTIFICATION-TYPE
OBJECTS { OBJECTS {
ippmReportSetupDefinition,
ippmMetricUnit, ippmMetricUnit,
ippmHistoryTimestamp,
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 object identifies the The index 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 ippmReportValue objects saved in the The notification contains the instances of the ippmReportValue
ippmReportTable for this measure cycle. The ippmHistoryTimestamp of the index objects saved in the ippmReportTable for this measure cycle. The
identifies the time the measures where performed. ippmHistoryTimestamp of the index identifies the time the
" measures where performed."
::= { ippmNotifications 4 } ::= { ippmNotifications 4 }
ippmHistoryLogFull NOTIFICATION-TYPE
OBJECTS {
ippmOnHistoryFullAction
}
STATUS current
DESCRIPTION
"A notification sent when the history log is full. It indicates
what action is to be taken. If the action is wrap the agent will
write over existing records in the beginning of the log file. If
the action is suspend, the agent halts all recording of measures
in the history table. If the action is resume, the agent begins
writing measures again in the history log"
::= { ippmNotifications 5 }
ippmReportLogFull NOTIFICATION-TYPE
OBJECTS {
ippmOnReportFullAction
}
STATUS current
DESCRIPTION
"A notification sent when the report log is full. It indicates
what action is to be taken. If the action is wrap the agent will
write over existing records in the beginning of the log file. If
the action is suspend, the agent halts all recording of measures
in the report table. If the action is resume, the agent begins
writing measures again in the report log"
::= { ippmNotifications 6 }
-- --
-- Compliance statements -- IPPM MIB Conformance statements
-- --
ippmCompliance MODULE-COMPLIANCE ippmCompliances OBJECT IDENTIFIER ::={ ippmConformance 1 }
ippmGroups OBJECT IDENTIFIER ::={ ippmConformance 2 }
ippmProxyInterDomainCompliances MODULE-COMPLIANCE
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The compliance statement for SNMP entities which implement the IPPM MIB" "The compliance statement for SNMP entities which implement the
IPPM MIB as a proxy in interdomain. The implementation of the
VACM control is mandatory."
MODULE -- this module MODULE -- this module
MANDATORY-GROUPS { ippmSystemGroup, ippmMeasureGroup, MANDATORY-GROUPS {
ippmNetworkMeasureGroup, ippmHistoryGroup } ippmSystemGroup, ippmMeasureGroup, ippmNetworkMeasureGroup,
ippmHistoryGroup, ippmAggrMeasureGroup, ippmReportGroup,
ippmNotificationGroup
}
::= { ippmCompliances 1 } ::= { ippmCompliances 1 }
ippmProxyCompliances MODULE-COMPLIANCE
STATUS current
DESCRIPTION
"The compliance statement for SNMP entities which implement the
IPPM MIB as a proxy."
MODULE -- this module
MANDATORY-GROUPS {
ippmSystemGroup, ippmMeasureGroup, ippmNetworkMeasureGroup,
ippmHistoryGroup, ippmAggrMeasureGroup, ippmReportGroup,
ippmNotificationGroup
}
GROUP ippmOwnersGroup
DESCRIPTION
"The ippmOwnersGroup is needed if VACM is not implemented."
::= { ippmCompliances 2 }
ippmProbeCompliances MODULE-COMPLIANCE
STATUS current
DESCRIPTION
"The compliance statement for SNMP entities which implement the
IPPM MIB in a probe."
MODULE -- this module
MANDATORY-GROUPS {
ippmSystemGroup, ippmMeasureGroup, ippmNetworkMeasureGroup,
ippmHistoryGroup
}
::= { ippmCompliances 3 }
ippmSystemGroup OBJECT-GROUP
OBJECTS {
ippmSystemSynchronizationDesc,
ippmSystemTime,
ippmSystemSynchronizationType,
ippmSystemClockResolution,
ippmSystemCurrentSynchronization,
ippmSynchronizationTime,
ippmSynchronizationStratum,
ippmSynchronizationResolution,
ippmPointOfMeasureMgmtAddrType,
ippmPointOfMeasureMgmtAddress,
ippmPointOfMeasureTypePAddress,
ippmPointOfMeasureAddress
}
STATUS current
DESCRIPTION
"The IPPM System Group"
::= { ippmGroups 1}
ippmMeasureGroup OBJECT-GROUP
OBJECTS {
ippmMetricCapabilities,
ippmMetricUnit,
ippmMetricDescription,
ippmMetricMaxHistorySize,
ippmMeasureName,
ippmMeasureMetrics,
ippmMeasureBeginTime,
ippmMeasureClockPeriodUnit,
ippmMeasureClockPeriod,
ippmMeasureDurationUnit,
ippmMeasureDuration,
ippmMeasureHistorySize,
ippmMeasureStorageType,
ippmMeasureStatus
}
STATUS current
DESCRIPTION
"The IPPM Measure Group"
::= { ippmGroups 2}
ippmNetworkMeasureGroup OBJECT-GROUP
OBJECTS {
ippmNetworkMeasureSrcTypeP,
ippmNetworkMeasureSrc,
ippmNetworkMeasureDstTypeP,
ippmNetworkMeasureDst,
ippmNetworkMeasureClockPattern,
ippmNetworkMeasurePoissonRate,
ippmNetworkMeasureTimeoutDelay,
ippmNetworkMeasureL3PacketSize,
ippmNetworkMeasureDataPattern
}
STATUS current
DESCRIPTION
"The IPPM Network Measure Group"
::= { ippmGroups 3}
ippmHistoryGroup OBJECT-GROUP
OBJECTS {
ippmHistorySequence,
ippmHistoryTimestamp,
ippmOnHistoryFullAction,
ippmHistoryValue
}
STATUS current
DESCRIPTION
"The IPPM History Group"
::= { ippmGroups 4}
ippmAggrMeasureGroup OBJECT-GROUP
OBJECTS {
ippmAggrMeasureHistoryOwner,
ippmAggrMeasureHistoryOwnerIndex,
ippmAggrMeasureHistoryMetric
}
STATUS current
DESCRIPTION
"The IPPM AggregatedMeasure Group"
::= { ippmGroups 5}
ippmReportGroup OBJECT-GROUP
OBJECTS {
ippmReportSetupDefinition,
ippmReportSetupMetricThreshold,
ippmReportSetupDurationThreshold,
ippmReportSetupNMS,
ippmReportSetupNotification,
ippmReportSetupStatus,
ippmReportSequence,
ippmReportTimestamp,
ippmReportValue,
ippmOnReportFullAction
}
STATUS current
DESCRIPTION
"The IPPM Report Group"
::= { ippmGroups 6}
ippmOwnersGroup OBJECT-GROUP
OBJECTS {
ippmOwnersOwner,
ippmOwnersGrantedMetrics,
ippmOwnersGrantedRules,
ippmOwnersIpAddress,
ippmOwnersEmail,
ippmOwnersSMS,
ippmOwnersStatus,
ippmOwnersIpAddressType,
ippmResultSharingMeasureOwner,
ippmResultSharingMeasureIndex,
ippmResultSharingGrantedOwner,
ippmResultSharingStatus
}
STATUS current
DESCRIPTION
"The IPPM Owners Group"
::= { ippmGroups 7}
ippmNotificationGroup NOTIFICATION-GROUP
NOTIFICATIONS {
ippmSingletonAlarm,
ippmCycleOfMeasureReport,
ippmCompletedMeasureReport,
ippmEventsDurationExceededAlarm,
ippmHistoryLogFull,
ippmReportLogFull
}
STATUS current
DESCRIPTION
"The IPPM Notification Group"
::= { ippmGroups 8}
END END
10. Security Considerations 9. Security Considerations
10.1. Privacy 9.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.
10.2. Measurement aspects 9.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 59, line 31 skipping to change at page 68, line 10
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.
10.3. Management aspects 9.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 60, line 7 skipping to change at page 69, line 5
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.
11. Document management 10. Document management
11.1. Open issues 10.1. Open issues
Describe incompatible bit combinations in IPPMreport and granted Describe incompatible bit combinations in IPPMreport and granted
metric metric
Run SMIlint. Run SMIlint.
Discussion on the management of the history size. Discussion on the management of the history size.
11.2. changes since release 00 10.2. changes since release 00
Put in a description of the relationship of certain tables, + Put in a description of the relationship of certain tables,
particularly the measure/network measure/aggregated measure table. particularly the measure/network measure/aggregated measure table.
The TC GMTTimeStamp is the common type to define timestamp objects. + The TC GMTTimeStamp is the common type to define timestamp objects.
ippmHisoryTable index simplified: ippmHistoryTimestamp replaced with + ippmHisoryTable index simplified: ippmHistoryTimestamp replaced
ippmHistorySqceNdx in the index. with ippmHistorySqceNdx in the index.
The MIB has been compiled using net-snmp. + The MIB has been compiled using net-snmp.
Snmpadminstring replaces Displaystring. + Snmpadminstring replaces Displaystring.
IP addresses defined using INETaddresstype. + IP addresses defined using INETaddresstype.
Sharing table is optional to permit the VACM framework to be used. + Sharing table is optional to permit the VACM framework to be used.
The description of the network measure table emphases that the set up + The description of the network measure table emphases that the set
of network measure is not permitted using SNMP. up of network measure is not permitted using SNMP.
The TC StandardMetrics is removed and replaced with the table + The TC StandardMetrics is removed and replaced with the table
ippmMetricsTable. ippmMetricsTable.
The table pointOfMeasureTable is added to describe multiples + The table pointOfMeasureTable is added to describe multiples
interfaces devices interfaces devices
5 tables have been changed to read/create: ippmOwnersTable, + 5 tables have been changed to read/create: ippmOwnersTable,
ippmMeasureTable, ippmAggregatedMeasureTable, ippmResultSharingTable, ippmMeasureTable, ippmAggrMeasureTable, ippmResultSharingTable, and
and ippmReportSetupTable. ippmReportSetupTable.
+ IppmHistoryTable and ippmReportTable index reviews:
IppmHistoryTable and ippmReportTable index reviews:
IppmHistorySqceNdx field added in the ippmHistoryTable. IppmHistorySqceNdx field added in the ippmHistoryTable.
INDEX modified. IppmHistorySqceNdx replaces IppmHistoryTimemark. INDEX modified. IppmHistorySqceNdx replaces IppmHistoryTimemark.
IppmSystem group refurbished: + IppmSystem group refurbished:
IppmSystemTimer renamed ippmSystemTime. IppmSystemTimer renamed ippmSystemTime.
Current and last synch event concept generalized in the Current and last synch event concept generalized in the
ippmSynchronizationTable. ippmSynchronizationTable.
12. References 10.3. Changes since release 01
+ Document Format:
Make use of the regular MIB object indentation.
+ Typos correction: ippmMeasureHystorySize and so on.
+ Time unit textual convention:
Enumerations listed in description clauses (e.g. ms, us, ns may
not be universally understood so explicitly named as millisecond,
microsecond, nanosecond)
+ Clarify ClearHistory and ClearReport definition:
OnReportDeliveryClearHistory and OnReportDeliveryClearReport
options
+ Added scalars ippmOnReportFullAction and ippmOnHistoryFullAction:
To take action when the tables are full. A scalar, which is read-
write and indicates the action to be taken when the log is full.
Options are: wrap, suspend, resume. Same was done for report
group.
+ Conformance section:
Added the MODULE-COMPLIANCE macro and the corresponding OBJECT-
GROUPS instances.
Added a compliance instances for proxy mode, proxy inter-domain
mode and probe mode.
+ PointOfMeasure:
Put in ippmPointOfMeasureMgmtAddrType-> InetAddressType with
ippmPointOfMeasureMgmtAddress-> InetAddress.
Changed point of measure address to be INET also.
+ Took out default point of measure address:
Added OwnersIpAddressType to be in pair with OwnersIpAddress
+ Added ippmSynchronizationResolution in the ppmSynchronizationTable:
It indicates the new time resolution (Henk request).
+ Added an object ippmReportSetupNotification in the report setup.
+ IppmHistoryIndex added in the history table:
To differentiate the result index from the test packet order.
+ IppmReportIndex added in the report table:
To differentiate the result index from the test packet order.
+ Smilint: with the option -s -l6:
Name length exceeded 32 chars:
Prefix:
+ ippmAggregatedMeasure -> ippmAggrMeasure;
+ IppmSystemSynchronizationDescription
-> ippmSystemSynchronizationDescr;
+ IppmReportSetupEventsDurationThreshold
-> ippmReportSetupDurationThreshold.
+ ippmNotifications identified under ippm
+ TC OwnerString replaced with IppmOwnerString to fix a warning
of the key length;
+ Gain 0 error and warning !
+ ippmAggrMeasureStatus removed:
The status of the row is managed in the ippmMeasureTable
+ Notifications:
definition clarified;
ippmReportTimestamp added to notification
ippmEventsDurationExceededAlarm, ippmSingletonAlarm,
ippmCycleOfMeasureReport, ippmCompletedMeasureReport.
+ IppmNetworkMeasureEntry :
ippmNetworkMeasurePoissonRate added as the average rates.
+ TypeP redefined as a SnmpAdminString instead of a raw OCTET STRING
e.g: '080000080000000011020000'H -> "ip.ipip4".
open issue:
is there a need to indicate the number of parameters of the
protocol identifier ? "ip.ipip4.2" or "ip.ipip4" ?
+ TypePaddress Textual convention created:
Dst and Src value is a display string instead of a raw OCTET
STRING. It is the list of parameters of a TypeP.
e.g:
Src address TypeP is "ip.ipip4": 128.2.6.7 in 192.168.1.1.
Src value was '0A04C0A801010480020607'H.
Src is now "192.168.1.1 128.2.6.7".
open issue:
is there any potential parameter with one or more space
inside ?
11. 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] Mahdavi J. and V. Paxson, "IPPM Metrics for Measuring
IP Performance Metrics", RFC 2330, May 1998.
[3] Mahdavi J. and V. Paxson, "IPPM Metrics for Measuring
Connectivity", RFC 2678, September 1999. Connectivity", RFC 2678, September 1999.
[4] Almes, G., Kalidindi, S. and M. Zekauskas, "A One-way Delay [3] Almes, G., Kalidindi, S. and M. Zekauskas, "A One-way Delay
Metric for IPPM", RFC 2679, September 1999. Metric for IPPM", RFC 2679, September 1999.
[5] Almes, G., Kalidindi, S. and M. Zekauskas, "A One-way Packet [4] Almes, G., Kalidindi, S. and M. Zekauskas, "A One-way Packet
Loss Metric for IPPM", RFC 2680, September 1999. Loss Metric for IPPM", RFC 2680, September 1999.
[6]Almes, G., Kalidindi, S. and M. Zekauskas, "A Round-trip Delay [5]Almes, G., Kalidindi, S. and M. Zekauskas, "A Round-trip Delay
Metric for IPPM.", RFC 2681, September 1999. Metric for IPPM.", RFC 2681, September 1999.
[7] Harrington, D., Presuhn, R., and B. Wijnen, "An Architecture for [6] Harrington, D., Presuhn, R., and B. Wijnen, "An Architecture for
Describing SNMP Management Frameworks", RFC 2571, April 1999. Describing SNMP Management Frameworks", RFC 2571, April 1999.
[8] Rose, M., and K. McCloghrie, "Structure and Identification of [7] Rose, M., and K. McCloghrie, "Structure and Identification of
Management Information for TCP/IP-based Internets", STD 16, RFC Management Information for TCP/IP-based Internets", STD 16, RFC
1155, May 1990. 1155, May 1990.
[9] Rose, M., and K. McCloghrie, "Concise MIB Definitions", STD 16, [8] Rose, M., and K. McCloghrie, "Concise MIB Definitions", STD 16,
RFC 1212, March 1991. RFC 1212, March 1991.
[10] M. Rose, "A Convention for Defining Traps for use with the [9] M. Rose, "A Convention for Defining Traps for use with the SNMP",
SNMP", RFC 1215, March 1991. RFC 1215, March 1991.
[11] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, [10] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose,
M., and S. Waldbusser, "Structure of Management Information M., and S. Waldbusser, "Structure of Management Information
Version 2 (SMIv2)", STD 58, RFC 2578, April 1999. Version 2 (SMIv2)", STD 58, RFC 2578, April 1999.
[12] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, [11] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose,
M., and S. Waldbusser, "Textual Conventions for SMIv2", STD 58, M., and S. Waldbusser, "Textual Conventions for SMIv2", STD 58,
RFC 2579, April 1999. RFC 2579, April 1999.
[13] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, [12] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose,
M., and S. Waldbusser, "Conformance Statements for SMIv2", STD 58, M., and S. Waldbusser, "Conformance Statements for SMIv2", STD 58,
RFC 2580, April 1999. RFC 2580, April 1999.
[14] Case, J., Fedor, M., Schoffstall, M., and J. Davin, "Simple [13] Case, J., Fedor, M., Schoffstall, M., and J. Davin, "Simple
Network Management Protocol", STD 15, RFC 1157, May 1990. Network Management Protocol", STD 15, RFC 1157, May 1990.
[15] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, [14] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser,
"Introduction to Community-based SNMPv2", RFC 1901, January 1996. "Introduction to Community-based SNMPv2", RFC 1901, January 1996.
[16] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, [15] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser,
"Transport Mappings for Version 2 of the Simple Network Management "Transport Mappings for Version 2 of the Simple Network Management
Protocol (SNMPv2)", RFC 1906, January 1996. Protocol (SNMPv2)", RFC 1906, January 1996.
[17]Case, J., Harrington D., Presuhn R., and B. Wijnen, "Message [16]Case, J., Harrington D., Presuhn R., and B. Wijnen, "Message
Processing and Dispatching for the Simple Network Management Processing and Dispatching for the Simple Network Management
Protocol (SNMP)", RFC 2572, April 1999. Protocol (SNMP)", RFC 2572, April 1999.
[18] Blumenthal, U., and B. Wijnen, "User-based Security Model (USM) [17] Blumenthal, U., and B. Wijnen, "User-based Security Model (USM)
for version 3 of the Simple Network Management Protocol (SNMPv3)", for version 3 of the Simple Network Management Protocol (SNMPv3)",
RFC 2574, April 1999. RFC 2574, April 1999.
[19] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Protocol [18] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Protocol
Operations for Version 2 of the Simple Network Management Protocol Operations for Version 2 of the Simple Network Management Protocol
(SNMPv2)", RFC 1905, January 1996. (SNMPv2)", RFC 1905, January 1996.
[20] Levi, D., Meyer, P., and B. Stewart, "SNMPv3 Applications", RFC [19] Levi, D., Meyer, P., and B. Stewart, "SNMPv3 Applications", RFC
2573, April 1999. 2573, April 1999.
[21] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-basedAccess [20] 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 [21] 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.
13. Acknowledgments 12. Acknowledgments
A Kerbe. A Kerbe.
14. Authors Addresses 13. 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/