wdiff draft-ietf-ippm-reporting-mib-05.txt draft-ietf-ippm-reporting-mib-06.txt

Network Working Group E. Stephan/J. Stephan
Internet-Draft J. Jewitt
Internet Draft
Expires: January 14, 2005 France Telecom R&D
Document: draft-ietf-ippm-reporting-mib-05.txt February,
July 16, 2004
Category: Standards Track

IPPM

IP Performance Metrics (IPPM) reporting MIB Information Base (MIB)
draft-ietf-ippm-reporting-mib-06.txt

Status of this Memo

This document is an Internet-Draft and is in full conformance with
all provisions of Section 10 of RFC2026 [1]. RFC2026.

Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as
Internet-Drafts.

Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or made obsolete obsoleted by other documents at any
time. It is inappropriate to use Internet- Drafts Internet-Drafts as reference
material or to cite them other than as "work in progress."

The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt.

The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html.

This Internet-Draft will expire on January 14, 2005.

Abstract

This memo defines a portion of the Management Information Base (MIB)
designed for use with network management protocols in TCP/IP-based
internets. In particular, this MIB specifies the objects used for
managing the results of the IPPM metrics measures, for pushing
alarms, and for reporting the measures results.

Table of Contents

1. Introduction................................................2 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4
2. The IPPM Framework..........................................3 Framework . . . . . . . . . . . . . . . . . . . . . . 4
3. The SNMP Internet-Standard Management Framework...............................3 Framework . . . . . . . . . . 4
4. Overview....................................................5
4.1. Textual Conventions.........................................5
4.2 Structure of the MIB.........................................8
4.3 Row identification in an application namespace..............10
4.4 Relationship of IPPM REPORTING MIB tables...................11 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 Measurement architectures...................................12
5.1 Proxy architecture..........................................12
5.2 Reporting architecture......................................13
5.3 Gateway architecture........................................15
5.4 Security....................................................15
4.1 Textual Conventions . . . . . . . . . . . . . . . . . . . 6 Reporting mode integration..................................16
6.1 Integration.................................................16
6.2 Setup of the network measure table..........................16
6.3 Setup of the aggregated measure table.......................16
6.4 Updating the history of the MIB.............................17
6.5 Default value...............................................17
7 Definition..................................................17
8 Security Considerations.....................................57
8.1 VACM Access control.........................................57
8.2 Privacy.....................................................59
8.3 Measurement aspects.........................................59
8.4 Management aspects..........................................60
9 Document management.........................................61
9.1 Open issues.................................................61
9.2 Changes done since release 04...............................61
9.3 Changes done since release 03...............................61
9.4 Changes done since release 02...............................62
10 References..................................................62
11 Acknowledgments.............................................64
12 Authors' Addresses..........................................64

1. Introduction
This memo defines a MIB for managing network measurements based upon
the IP performance metrics specified by the IPPM Working Group.

The definition of objects in the IPPM MIB are built on notions
introduced and discussed in the IPPM Framework document, RFC 2330
[ii].

This memo defines a Management Information Base (MIB),
4.1.1 OwnerString . . . . . . . . . . . . . . . . . . . . . 6
4.1.2 IppmOwnerIndex . . . . . . . . . . . . . . . . . . . . 6
4.1.3 TimeUnit . . . . . . . . . . . . . . . . . . . . . . . 6
4.1.4 PacketType and as such it
is intended to be respectful PacketTypeAddres . . . . . . . . . . . 6
4.1.5 GMTTimeStamp . . . . . . . . . . . . . . . . . . . . . 7
4.1.6 IppmStandardMetrics . . . . . . . . . . . . . . . . . 7
4.1.7 Report definition . . . . . . . . . . . . . . . . . . 8
4.2 Structure of the "Boilerplate for IETF MIBs"
defined in http://www.ops.ietf.org/mib-boilerplate.html.

There are companion documents to the IPPM-REPORTING-MIB both in the
Transport Area (See section 2), and in the Operations and Management
Area (See section 3). The reader should be familiar with these
documents.

2. The IPPM Framework MIB . . . . . . . . . . . . . . . . . . . 9
4.2.1 The IPPM Framework consists of 3 major components:

A general framework for defining performance metrics, as described in
the Framework for IP Performance Metrics, RFC 2330 [2];

A set of standardized metrics which conform to this framework: ippmSystem Group . . . . . . . . . . . . . . . . . 9
4.2.2 The
IPPM Metrics for Measuring Connectivity, RFC 2678 [iii]; ippmHistory Group . . . . . . . . . . . . . . . . 10
4.2.3 The One-way
Delay Metric for IPPM, RFC 2679 [iv]; ippmNetMeasure Group . . . . . . . . . . . . . . . 10
4.2.4 The One-way Packet Loss Metric
for IPPM, RFC 2680 [v]; ippmAggrMeasure Group . . . . . . . . . . . . . . 10
4.2.5 The Round-trip Delay Metric for IPPM, RFC
2681 [vi];

Emerging metrics that are being specified Notification Group . . . . . . . . . . . . . . . . 11
4.3 Row identification in respect of this
framework.

3. The SNMP Management Framework

The SNMP Management Framework consists an application namespace . . . . . . 11
4.4 Relationship of five major components:

An overall architecture, described in RFC 2571 [2].

Mechanisms for describing IPPM REPORTING MIB tables . . . . . . . . 11
4.4.1 Relationship between the Owners Table and naming objects the
aggregated measure table . . . . . . . . . . . . . . . 11
4.4.2 Relationship between the Network Measure Table and events for
the
purpose of management. The first version of this Structure of
Management Information (SMI) is called SMIv1 and described in STD 16,
RFC 1155 [3], STD 16, RFC 1212 [4] and RFC 1215 [5]. The second
version, called SMIv2, is described in STD 58, RFC 2578 [6], STD 58,
RFC 2579 [7] and STD 58, RFC 2580 [8].

Message protocols for transferring management information. The
first version Aggregated Measure Table . . . . . . . . . . . . . 12
5. Measurement architectures . . . . . . . . . . . . . . . . . . 12
5.1 Proxy architecture . . . . . . . . . . . . . . . . . . . . 13
5.2 Reporting architecture . . . . . . . . . . . . . . . . . . 14
5.3 Gateway architecture . . . . . . . . . . . . . . . . . . . 15
5.4 Security . . . . . . . . . . . . . . . . . . . . . . . . . 16
6. Reporting mode integration . . . . . . . . . . . . . . . . . . 16
6.1 Integration . . . . . . . . . . . . . . . . . . . . . . . 17
6.2 Setup of the SNMP message protocol is called SNMPv1 and
described in STD 15, RFC 1157 [9]. A second version network measure table . . . . . . . . . . . . 17
6.3 Setup of the SNMP
message protocol, which is not an Internet standards track protocol,
is called SNMPv2c and described in RFC 1901 [10] and RFC 1906 [11].
The third version aggregated measure table . . . . . . . . . . 17
6.4 Updating the history of the message protocol is called SNMPv3 and
described in RFC 1906 [11], RFC 2572 [12] and RFC 2574 [13].

Protocol operations MIB . . . . . . . . . . . . . 17
6.5 Default value . . . . . . . . . . . . . . . . . . . . . . 17
7. Definition . . . . . . . . . . . . . . . . . . . . . . . . . . 18
8. Security Considerations . . . . . . . . . . . . . . . . . . . 70
8.1 VACM Access control . . . . . . . . . . . . . . . . . . . 70
8.1.1 Example of implementing VACM control for the
IPPM-REPORTING-MIB . . . . . . . . . . . . . . . . . . 70
8.2 Privacy . . . . . . . . . . . . . . . . . . . . . . . . . 73
8.3 Measurement aspects . . . . . . . . . . . . . . . . . . . 73
8.4 Management aspects . . . . . . . . . . . . . . . . . . . . 74
9. Document management . . . . . . . . . . . . . . . . . . . . . 74
9.1 Open issues . . . . . . . . . . . . . . . . . . . . . . . 74
9.2 Changes done since release 05 . . . . . . . . . . . . . . 75
9.3 Changes done since release 04 . . . . . . . . . . . . . . 75
9.4 Changes done since release 03 . . . . . . . . . . . . . . 75
9.5 Changes done since release 02 . . . . . . . . . . . . . . 76
10. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . 77
11. References . . . . . . . . . . . . . . . . . . . . . . . . . 77
11.1 Normative References . . . . . . . . . . . . . . . . . . . . 77
11.2 Informative References . . . . . . . . . . . . . . . . . . . 77
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 78
Intellectual Property and Copyright Statements . . . . . . . . 79

1. Introduction

This memo defines a MIB for accessing management information. managing network measurements based upon
the IP performance metrics specified by the IPPM Working Group.

The
first set of protocol operations and associated PDU formats is
described in STD 15, RFC 1157 [9]. A second set of protocol
operations and associated PDU formats is described in RFC 1905 [14].

A set definition of fundamental applications described objects in RFC 2573 [15] and the view-based access control mechanism described IPPM MIB are built on notions
introduced and discussed in RFC 2575 [16].

A more detailed introduction to the current SNMP Management IPPM Framework
can be found in document, RFC 2570 [17].

Managed objects are accessed via 2330
[RFC2330].

This memo defines a virtual information store, termed
the Management Information Base or MIB. Objects in the MIB are
defined using (MIB), and as such it
is intended to be respectful of the mechanisms "Boilerplate for IETF MIBs"
defined in the SMI.

This memo specifies a MIB module that is compliant http://www.ops.ietf.org/mib-boilerplate.html.

There are companion documents to the SMIv2. A
MIB conforming to IPPM-REPORTING-MIB both in the SMIv1 can be produced through
Transport Area (See section 2), and in the appropriate
translations. Operations and Management
Area (See section 3). The resulting translated MIB must reader should be semantically
equivalent, except where objects or events familiar with these
documents.

2. The IPPM Framework

The IPPM Framework consists of 3 major components:

o A general framework for defining performance metrics, as described
in the Framework for IP Performance Metrics, RFC 2330 [RFC2330];

o A set of standardized metrics which conform to this framework:

* IPPM Metrics for Measuring Connectivity, RFC 2678 [RFC2678];

* One-way Delay Metrics, RFC 2679 [RFC2679];

* One-way Packet Loss Metrics, RFC 2680 [RFC2680];

* Round-trip Delay Metrics, RFC 2681 [RFC2681];

* One-way Loss Pattern Sample Metrics, RFC 3357 [RFC3357];

* IP Packet Delay Variation Metric, RFC 3393 [RFC3393];

* IPPM Metrics for periodic streams, RFC 3432 [RFC3432];

o Emerging metrics that are omitted because no
translation is possible (use of Counter64). Some machine readable
information in SMIv2 will be converted into textual descriptions being specified in
SMIv1 during the translation process. However, respect of this loss
framework.

3. The Internet-Standard Management Framework

For a detailed overview of machine
readable information is not considered to change the semantics of documents that describe the
MIB. current
Internet-Standard Management Framework, please refer to section 7 of
RFC 3410 [RFC3410];.

Managed objects are accessed via a virtual information store, termed
the Management Information Base or MIB. MIB objects are generally
accessed through the Simple Network Management Protocol (SNMP).
Objects in the MIB are defined using the subset of Abstract Syntax Notation One (ASN.1) mechanisms defined in the SMI. In particular, each object type is named by an
OBJECT IDENTIFIER, an administratively assigned name.

The object type together with an object instance serves to uniquely
identify a specific instantiation
Structure of the object. For human
convenience, we often use Management Information (SMI). This memo specifies a textual string, termed the descriptor, to
refer MIB
module that is compliant to the object type. SMIv2, which is described in STD 58,
RFC 2578 [RFC2578];, STD 58, RFC 2579 [RFC2579]; and STD 58, RFC 2580
[RFC2580];.

4. Overview

Although the number of measurement devices that implement IPPM
metrics is growing, there is not currently any standardized
management interface to manage remotely the measurement of these
metrics. This memo defines a Management Information Base for
managing the measurement of IPPM metrics.

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
framework for the integration of future metrics in the [IPPM metrics
registry].

As the specification of new metrics is a continuous process, this
memo defines a framework for the integration of the future
standardized metrics.

The IPPM-REPORTING-MIB introduces a framework where each application
identifies its measures in an owner namespace. The administrator may
grant access to a measure, or set of measures to another owner via
view based access control. As a result, one owner may compute
aggregated metrics on another owner�s owner's network measures.

Different architectures may be used to perform metric measurements,
using a control protocol and a test protocol. Different control
frameworks are suitable for performing measurements. The memo lists
them, while also looking for a way to integrate them with the IPPM-
REPORTING-MIB.
IPPM-REPORTING-MIB. This section is for informational purposes only,
and is intended to help specify the relationship among the test
protocol, the control protocol and the IPPM-REPORTING-MIB.

Special care has been taken to provide a reporting mode suitable for
control protocols and test protocols. It addresses the need to
provide access to results for the applications.

This MIB is intended to handle multiple concurrent sessions by SNMP
applications. However, the SNMP requests are not necessarily to be
handled explicitly by the measurement devices, but can be sent to
middleware performing an aggregation function. This allows for
continuous collection of measurements and statistics computation.

4.1.

4.1 Textual Conventions

Eight types of data are introduced as textual conventions in this
document: IppmOwnerString, IppmOwnerIndex, TimeUnit, PacketType,
PacketTypeAddress, GMTTimeStamp, IppmStandardMetrics and
IppmMetricResultFilter.

4.1.1 IppmOwnerString OwnerString

This octet string is used to represent the owners of the various
measures and reports in the measurement system.

4.1.2 IppmOwnerIndex

This integer identifies an instance of an object in an owner
namespace.

4.1.3 TimeUnit

This textual convention is used to indicate a unit of time, ranging
from nanosecond, microsecond, millisecond, second, hour, day, and
week.

4.1.4 PacketType and PacketTypeAddress PacketTypeAddres

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
depends on the type of the packets involved in the metric. In the
definition of a metric, the type P will be explicitly defined,
partially defined, or left generic. Measurement of metrics defined
with generic type P are made specific when performing actual
measurements. It is important that one be conscious of the exact
type of traffic being measured.

The standardization of the management of IPPM measures relies on the
capability to unambiguously configure the type P of the packets, and
the parameters of the protocol suites of the type P.

RMON2 introduced the concept of protocol identifiers. RFC2895 [xxv]
specifies a macro for the definition of protocol identifier. The
RFC2896 [xxvi] defines the protocol identifiers for different
protocol encapsulation trees.

The type P implementation relies on the MACRO PROTOCOL-IDENTIFIER
defined for identifying protocol suites in RMON2. It is achieved by
defining the PacketType and the PacketTypeAddress as new syntax in
SMIv2 TEXTUAL-CONVENTION.

4.1.4.1 Internet addresses

The section 14 of the IPPM framework defines (for the usual case of a
unidirectional path through the Internet) the term "Src" and "Dst".
"Src" denotes the IP address of the beginning of the path, and "Dst"
denotes the IP address of the end.

The section 3 of the RMON PI Reference specifies the Protocol
Identifier Encoding rules, which consists briefly in a recursive
length value format. "Src" and "Dst" are protocol identifier
parameters. Their values are encoded in separated fields using the
encoding rules of the protocol identifier, but without trailing
parameters.

The packet encapsulation defined in an instance of PacketType embeds
the 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,
IPV6, IP in IP... Both participate in the completion of the packet
encoding.

Examples:

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
tunnel 128.2.6.7. the PacketType of the source address of the
tunnel, Src, is 'ip.ipip4'. The encoding of 'ip.ipip4' using the
RFC2895 rules adds a trailer 2.0.0. It means that an instance of
this protocol identifier has 2 parameters, which values will be set
only when implemented. In the IPPM PacketType 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".

4.1.5 GMTTimeStamp

This textual convention defines the time at which an event occurred.
It is very similar to the NTP timestamp format except that it
represents the time elapsed since January 1st, 2000 instead of
January 1st, 1900.

4.1.6 IppmStandardMetrics

Each standard metric is identified in the IPPM-METRICS-REGISTRY under
the node rfc in chronological order. This textual convention defines
an octet string to permit several metrics to be performed in a single
measure.

4.1.7 Report definition

A report consists of sending, or logging, a subset of results of
measurements that have been taken over a period of time. The report
defines actions that are taken on the measurement results. An action
is performed either:

For each result
+ result;

On the results corresponding to a measurement cycle
+ cycle;

On the results available at the measurement completion.

To preserve the scalability of the whole measurement system, it
limits:

The amount of data sent to the applications
+ applications;

The bandwidth consumption for uploading the result
+ result;

The number of alarms sent to the applications
+ applications;

The amount of data saved in the point of measure measure.

Metric thresholds (low, high, inband, outband...) may be defined that
indicate when measure values should be reported. These values and
their associated time may directly impact service availability.

One may also want to report when particular values (i.e. constantly
over a threshold) repeatedly occur over a period of time. For
example, if one-way-day is constantly over a specified acceptable
threshold value for 10 minutes, then the values should be reported.

The combination of IPPM metric results, threshold events, and event
filtering provides a very efficient mechanism to report measurement
results, events, and alarms.

A report is described using the TEXTUAL-CONVENTION
IppmMetricResultFilter. The report setup must not dramatically
increase the amount of data needed by the control protocol to setup a
measure:

A basic report is defined in the object ippmAggrMeasureFilter;
+

More elaborate reports are described using a metric threshold to
generate alarms and events.
+ events;

The generation of alarms and reports requires a management station
address to which the data will be sent.
+ sent;

SLA alarms are described using an events duration threshold.

The TEXTUAL-CONVENTION IppmMetricResultFilter specifies the list of
events and actions that are used to create a report.

4.2 Structure of the MIB

The MIB is arranged as follow:

ippmSystem Group:

ippmPointOfMeasureTable;
+

ippmSynchronizationTable;
+

ippmMetricsTable.

ippmOwners Group:
-
+

ippmOwnersTable;

ippmHistory Group:
-
+

ippmHistoryTable;

ippmNetMeasure Group:
-
+

ippmNetMeasureTable;

ippmAggrMeasure Group:
-
+

ippmAggrMeasureTable.

ippmNotifications

4.2.1 The ippmSystem Group

The implementation of this group is mandatory.

This group consists of a set of parameters describing the clock
synchronization at a particular point of measure over time, as well
as the system clock of the IPPM-REPORTING-MIB agent.

The table ippmPointOfMeasureTable describes the points of measure.

The table ippmSynchronisationTable is critical to the implementation,
especially to be respectful of the Section 6.3. of the IPPM
Framework, which states that "Those who develop such measurement
methodologies should strive to:
+

Minimize their uncertainties/errors,
+

Understand and document the sources of uncertainty/error, and
+

Quantify the amounts of uncertainty/error."

Consequently the table ippmSynchronisationTable makes these values
available to compute reliable statistics.

The table ippmMetricsTable list all the IPPM metrics using the
registry order and describes their implementation (unit...).

4.2.2

4.2.1.1 The ippmOwners Group

This group identifies an owner, or group of owners, that have access
to measurements on a probe.

4.2.3

4.2.2 The ippmHistory Group

The results of any given measure are stored in the ippmHistoryTable.
The indexing is such that there is an entry in this table for each
result of a given measure for a given metric.

4.2.4

4.2.3 The ippmNetMeasure Group

The control protocol registers a description of the existing network
measures in the ippmNetMeasureTable.

This group displays the network measures defined by the control
protocol. The results are saved in the ippmHistoryTable.

ippmNetMeasureTable is a reflection of the configuration of the
network measure.

4.2.5

4.2.4 The ippmAggrMeasure Group

ippmAggrMeasureTable is responsible for the aggregation of results.
The aggregated results are saved in the ippmHistoryTable and may be
used for higher aggregated measures.

4.2.6

4.2.5 The Notification Group

The Notification group specifies a list of valid notifications. They
are used to generate alarms, or reports, to management applications.

4.3 Row identification in an application namespace

IPPM metrics measurement is a distributed task. An owner namespace
is defined to avoid the need of polling to determine the next free
index, to avoid index collision when 2 applications are looking for a
new index as the same time; to increase the speed of the management
operations; to reduce bandwidth consumption and to reduce CPU load in
the agents and applications.

In a MIB, an object instance identifier is defined by the clause
INDEX of the table as a list of objects.

The owner namespace is defined in the INDEX as a couple of 2 objects
where the type of first one is IppmOwnerString and the type of the
second is IppmOwnerIndex.

The first term of the instance identifier is the name of the owner.
The second term is an private index managed by the owner. This index
value is unique in an owner namespace. Before the creation of an
instance the creator pick up an IppmOwnerIndex value not in use.

This allows the user to choose arbitrary values for the remaining
fields of the INDEX clause without checking that the values of these
fields exists in the MIB tables. Moreover this allows the owner to
use the same instance identifier over a set of IPPM MIB
implementations.

Measurements are requested by management applications. An instance
of an object managed by a management station is identified by the
management station IppmOwnerString and the private index provided by
the MS.

4.4 Relationship of IPPM REPORTING MIB tables

There is inherently a relationship between various tables in the IPPM
REPORTING MIB, and as such, the data integrity must be assured. This
relationship is depicted in the following examples.

4.4.1 Relationship between the Owners Table and the aggregated measure
table

The owners table contains the list of "owners" that can create and
activate remotely aggregated measures in an IPPM agent, or read the
existing network measures.

It is recommended to make use of "view based access control" in order
to restrict access to this table. For example, the master user
"administrator" may be given "write" privileges on the
ippmOwnersTable, whereas all others are restricted to "read" access.
The user "administrator" can then setup the list of other users that
have access to measures.

There must be at least 1 owner in the owners' table. This owner may
be either setup by default by the IPPM agent, or configured as stated
above.

An owner may have multiple corresponding entries in the network and
aggregated measure tables. Each entry in a measure table is
associated with one, and only one, entry in the owners' table. That
is to say, that a defined measure may NOT have multiple owners.

Thus, we have a 1:N relationship between the owners' table and a
measure table.

4.4.2 Relationship between the Network Measure Table and the Aggregated
Measure Table

The network measure table is read-only, thus entries in this table
must be populated by the agent upon startup.

The agent could potentially read a database that contains network
measures configured by a 3rd party proprietary management system that
directly interacts with the points of measure. However, the "owner"
of the measure must be defined in the owners table. It may be either
configured directly, or exported to the agent by the external
measurement tool.

The aggregated measure table allows for an "owner" to create
aggregated measures (such as average, minimum, maximum...) on
existing measures. An owner may even create aggregated measures on
network measures that are owned by other owners. However, it is
recommended to use view based access control to grant access of
network measures to other owners in the system.

5. Measurement architectures

There are three main measurement architectures.

5.1 Proxy architecture

+----+ +----+
.
|NMS1| |NMS2|
.
+----+ +----+
.
^ ^
.
| |
.
+----------+ +----------+
.
| |
.
SNMP or Sibling
.
| |
.
v v
.
+--------------------------+
.
| IPPM-REPORTING-MIB agent |
.
+--------------------------+
.
^ ^
.
| |
.
OWDP-Control
.
| |
.
+----------+ +----------+
.
| |
.
v v
.+----------------+
+----------------+ +------------------+
.|
| Packets-Sender |--OWDP-Test-->| Packets-Receiver |
.+----------------+
+----------------+ +------------------+

In this architecture, the different NMS�s NMS's query the IPPM-REPORTING-
MIB
IPPM-REPORTING-MIB agent for measurements. The agent controls
whether the NMS is granted access to perform the measure requested.
Each NMS may access the results of its measurements in the
IPPM-REPORTING-MIB history table.

The measurement setup/teardown and the data collection are done using
the control protocol and the test protocol.

In this mode the NMS does not depend on the control protocol nor on
the test protocol. The entities involved in the measurement do not
need to implement the IPPM-REPORTING-MIB nor SNMP. This mode allows
for lightweight implementation in the point of measure, and also for
heterogeneous control protocols to coexist.

Finally, the proxy is a checkpoint where measurement activity may be
logged, and where access to measurement setups may be tightly
controlled. Thus, it provides a reliable architecture to manage the
security of a measurement system.

5.2 Reporting architecture

In this architecture the SNMP protocol is only used to read the
results of the measurements in the IPPM-REPORTING-MIB History Table,
and also to inform the NMS that an event has occurred.

+----+ +----+
.
|NMS1| |NMS2|
.
+----+ +----+
.
^ ^ ^ ^
.
| | | |
.
SNMP| SNMP|
.
| | | |
.
| | | |
.
| OWDP | OWDP
.
|Control |Control
.
| | | |
.
| | +------------------------------+
.
| | | | |
.
| | +--|---------------------------+ |
.
| | | | | |
.
| +--|--|------------------------+ | |
.
| | | | | | |
.
+--------+---------------------+ | |
.
| | | | | | | |
.
| | | | | | | |
.
v v v v v v v v
.
+------------------+ +------------------+
.
|IPPM-REPORTING-MIB| |IPPM-REPORTING-MIB|
.
| agent | | agent |
.
+------------------+ +------------------+
.
| Packets-Sender |--OWDP-Test-->| Packets-Receiver |
.
+------------------+ +------------------+

The activation of a measure by the control protocol or the test
protocol creates a measure in the IPPM-REPORTING-MIB Network Measure
table. The table in question may be not accessible by SNMP. In this
case, a list of the measure identifiers (owner, index) is handled by
the measurement software.

Each timestamped result of the measure is logged in the IPPM-
REPORTING-MIB
IPPM-REPORTING-MIB History table in order to allow read access to the
NMS�s
NMS's and event handling.

On completion, the measurement results are managed according to the
measure setup:
+

The results may be sent to an NMS;
+

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
reporting events because it ensures that the entire block of the
result is received. There is no control using SNMP Trap PDU.

5.3 Gateway architecture

The gateway architecture combines the proxy mode and the reporting
mode.

+-------+ +------+
.
| NMS1 | | NMS2 |
.
+-------+ +------+
.
^ ^
.
| |
.
SNMP SNMP
.
| |
.
| +----------------------------------------+
.
| | |
.
+-------------+ +------------------+
.
| | | | |
.
+----------------------------------------+ |
.
| | | | | |
.
| | v v | |
.
| | +------------------------+ | |
.
| | | IPPM-REPORTING-MIB | | |
.
| | | Gateway | | |
.
| | +------------------------+ | |
.
| | | control server | | |
.
| | +------------------------+ | |
.
| | ^ ^ | |
.
| | | | | |
.
| | OWDP-Control protocol | |
.
| | | | | |
.
| | +-----+ +-------+ | |
.
| | | | | |
.
v v v v v v
.
+-------------+---------+ +--------+-------------+
.
| IPPM- | Packets | |Packets | IPPM |
.
|REPORTING-MIB| Sender | |Receiver|REPORTING-MIB|
.
| agent | |-OWDP-Test->| | agent |
.
+-------------+---------+ +--------+-------------+
The NMS measurement queries are registered in the IPPM-REPORTING-MIB
gateway and performed by the control and the test protocol. The NMS
directly consults the result in the corresponding IPPM REPORTING MIB
agent of the points of measure.

5.4 Security

The proxy mode provides flexibility and control of the access to the
points of measure, while allowing lightweight control protocol and
test protocol implementations in the points of measure. Different
security rules may be applied to the NMS domain and to measurement
system domains.

The reporting mode has 2 security domains:

The control of the measurement setup relies on setup relies on the control and the
test protocol security mechanisms;

The control of access to the results depends on the SNMP security
mechanisms such as community strings, but may also be restricted
using VACM for customized access.

The gateway mode security relies on the security of the proxy mode
and of the reporting mode.

6. Reporting mode integration

The IPPM-REPORTING-MIB standardizes the parameters that:

Define the configuration of the IPPM metric measures;

Define the format of the results of the measure;

Define the report of the IPPM metric measure results.

It introduces the concept of owner namespace to allow for fast
configuration and reporting across multiple points of measurement.

A measure is a distributed object describing a task to be performed
by the control and the test protocols. A measure is identified by
its owner and its owner index. This identifier is the same in all
the points of measure. As the owner chooses the index, there is no
need for negotiation between the NMS and the points of measure before
activating the measure.

A measure is primarily defined by its identifier, the metrics to
measure, the description of the end point addresses and the
description of the scheduling of the measure.

The description of the measure is distributed to the points of
measure involved. The distribution may not be synchronized.

6.1 Integration

The integration of the IPPM-REPORTING-MIB, and the test and control
protocols consists in pushing the network measure setup/teardown
parameters and the result values from the measurement software to the control and
IPPM-REPORTING-MIB agent.

6.2 Setup of the test protocol security mechanisms;
+ network measure table

The control of access to measurement system updates the results depends MIB on creation of a network
measure.

6.3 Setup of the SNMP
security mechanisms such as community strings, but may also be
restricted using VACM for customized access. aggregated measure table

There are 2 ways to setup an aggregated measure: The gateway mode security relies on measurement
system updates the security MIB on creation of an aggregated measure; An SNMP
application creates an aggregated measure.

6.4 Updating the proxy mode
and history of the reporting mode.

6 Reporting mode integration

The IPPM-REPORTING-MIB standardizes MIB

Results have to be written by the parameters that:

+ Define measurement task in the configuration of agent
implementing the IPPM metric measures;
+ Define the format of REPORTING MIB.

Adding the results of a measurement consists in the measure;
+ Define the report transfer of the IPPM metric measure results.

It introduces
result from the concept of owner namespace measurement software to allow for fast
configuration and reporting across multiple points of measurement.

A measure is a distributed object describing a task the SNMP agent. The protocol
that provides the result may be the control protocol, or the test
protocol, or another mechanism.

6.5 Default value

The default values correspond to IP version 4.

7. Definition

IPPM-REPORTING-MIB DEFINITIONS ::= BEGIN

IMPORTS
mib-2,
MODULE-IDENTITY,
NOTIFICATION-TYPE,
OBJECT-TYPE,
Integer32, zeroDotZero, Counter64, Unsigned32
FROM SNMPv2-SMI
InetAddressType,
InetAddress
FROM INET-ADDRESS-MIB
SnmpAdminString
FROM SNMP-FRAMEWORK-MIB
RowStatus,
StorageType,
TEXTUAL-CONVENTION
FROM SNMPv2-TC
MODULE-COMPLIANCE,
OBJECT-GROUP,
NOTIFICATION-GROUP
FROM SNMPv2-CONF;

ippm MODULE-IDENTITY
LAST-UPDATED "200407151200Z" -- 15 July 2004
ORGANIZATION "IP Performance Metrics (ippm) Working Group"
CONTACT-INFO
"Emile Stephan
France Telecom - R&D
E-mail: emile.stephan@francetelecom.com

Jessie Jewitt
France Telecom - R&D
E-mail : jessie.jewitt@rd.francetelecom.com

Comments about this document should be performed
by the control and the test protocols. A measure is identified by its
owner and its owner index. This identifier is the same in all send to the
points IPPM
working group mailing list at ippm@ietf.org.
"
DESCRIPTION
"This memo defines a portion of measure. As the owner chooses the index, there is no need Management Information
Base (MIB) for negotiation between use with network management protocols in
TCP/IP-based internets. In particular, it specifies the NMS and
objects used for managing the points results of measure before
activating the measure.

A measure is primarily defined by its identifier, the IPPM metrics to
measure, the description of the end point addresses
measurements, alarms and the
description of the scheduling of the measure.

The description reporting of the measure is distributed measurement results."

REVISION "200210181200Z" -- 18 October 2002
DESCRIPTION
"General cleanup
Change 5 tables to the points of
measure involved. The distribution may not be synchronized.

6.1 Integration

The integration read write"

REVISION "200302141200Z" -- 14 February 2003
DESCRIPTION
"Modifications based upon feedback from IETF-55"

REVISION "200306291200Z" -- 29 June 2003
DESCRIPTION
"Adaptation to VACM, preparation of the IPPM-REPORTING-MIB, final version"

REVISION "200310241200Z" -- 24 October 2003
DESCRIPTION
"Modifications based upon feedback from experimental
implementation."

REVISION "200402121200Z" -- 12 February 2004
DESCRIPTION
"Modifications based upon feedback 58th IETF: The report
group and the test corresponding notification are removed."

REVISION "200407151200Z" -- 15 July 2004
DESCRIPTION
"Rewritten in XML and control
protocols consists Clean up."

::= { mib-2 XXX }
-- RFC Ed.: replace XXX with IANA-assigned number
-- & remove this note
--
-- TEXTUAL-CONVENTION

IppmOwnerString ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"The owner namespace is defined in pushing the network measure setup/teardown
parameters and the result values from the measurement software to the
IPPM-REPORTING-MIB agent.

6.2 Setup INDEX of the network measure a table

The measurement system updates the MIB on creation of as a network measure.

6.3 Setup
couple of the aggregated measure table

There are 2 ways to setup an aggregated measure:

The measurement system updates objects where the MIB on creation type of an aggregated
measure;
An SNMP application creates an aggregated measure.

6.4 Updating the history first one is
IppmOwnerString and the type of the MIB

Results have second is IppmOwnerIndex.
IppmOwnerString is an OwnerString which length is limited to be written by the measurement task
32 bytes."
SYNTAX OCTET STRING (SIZE (0..32))

IppmOwnerIndex ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"The owner namespace is defined in the agent
implementing the IPPM REPORTING MIB.

Adding the results INDEX of a measurement consists in the transfer table as a
couple of 2 objects where the
result from the measurement software to the SNMP agent. The protocol
that provides type of first one is
IppmOwnerString and the result may be type of the control protocol, or second is IppmOwnerIndex.
An object of type IppmOwnerIndex uniquely identifies a row of
a table inside an owner namespace.
Inside one namespace several objects of type IppmOwnerIndex
coexist and share the test
protocol, or another mechanism.

6.5 Default value

The default IppmOwnerIndex range of values correspond to IP version 4.

7 Definition

IPPM-REPORTING-MIB DEFINITIONS ::= BEGIN

IMPORTS
MODULE-IDENTITY,
NOTIFICATION-TYPE,
OBJECT-TYPE,
experimental ,Integer32, zeroDotZero, Counter64,
provide an unique instance identifier.
"
SYNTAX Unsigned32
FROM SNMPv2-SMI
--
-- ippm (1.. 65535)

TimeUnit ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"A enumerated list of time units."
SYNTAX INTEGER {
week(1),
day(2),
hour(3),
minute(4),
second(5),
millisecond(6),
microsecond(7),
nanosecond(8)
}

-- FROM IPPM-REGISTRY
--
InetAddressType,
InetAddress
FROM INET-ADDRESS-MIB
SnmpAdminString
FROM SNMP-FRAMEWORK-MIB
RowStatus,
StorageType,

IppmStandardMetrics ::= TEXTUAL-CONVENTION
FROM SNMPv2-TC
MODULE-COMPLIANCE,
OBJECT-GROUP,
NOTIFICATION-GROUP
FROM SNMPv2-CONF;

ippmReportingMib MODULE-IDENTITY
LAST-UPDATED "200402121200Z" -- 12 February 2004
ORGANIZATION "France Telecom - R&D"
CONTACT-INFO
"Emile Stephan
France Telecom - R&D
2, Avenue Pierre Marzin
Technopole Anticipa
22307 Lannion Cedex
FRANCE
Tel: + 33 2 96 05 36 10
E-mail: emile.stephan@francetelecom.com

Jessie Jewitt
France Telecom - R&D
801 Gateway Blvd. Suit 500
South San Francisco, CA 94080
Tel : 1 650 875-1524
E-mail : jessie.jewitt@rd.francetelecom.com"
STATUS current
DESCRIPTION
" Each standard metric is identified in the IPPM-METRICS-
REGISTRY under the node rfc in chronological order. In order to
allow for several metrics to be calculated in a single measure,
there is a need to describe in a bit string the metrics to be
measured.

This memo textual convention defines an octet string that gathers in a portion
bit string a sequence of bits. The bit order corresponds to the Management Information Base
(MIB) for use with network management protocols
order of the metric identifiers in TCP/IP-based
internets. In particular, it specifies the objects used for
managing registry.
The first bit of the results string has the index 0. The index 1
corresponds to the first metric of the IPPM metrics measurements, alarms and
reporting registry
(instantaneousUnidirectionalConnectivity ).

Example:
One-way-Delay(6) is identified as the leaf number 6 of measurement results."

REVISION "200210181200Z" -- 18 October 2002
DESCRIPTION
"General cleanup
Change 5 tables to read write"

REVISION "200302141200Z" -- 14 February 2003
DESCRIPTION
"Modifications based upon feedback from IETF-55"

REVISION "200306291200Z" -- 29 June 2003
DESCRIPTION
"Adaptation to VACM, preparation the node
rfc of the final version"

REVISION "200310241200Z" -- 24 October 2003
DESCRIPTION
"Modifications based upon feedback from experimental
implementation."

REVISION "200402121200Z" -- registry. One-way-Packet-Loss(12) is identified as the
leaf number 12 February 2004
DESCRIPTION
"Modifications based upon feedback 58th IETF: The report group
and of the corresponding notification are removed."

::= { experimental 10001 } -- XXX to node
rfc of the registry. A network measure performing both One-way-
Delay(6) and One-way-Packet-Loss(12) will be assigned by IANA

ippm OBJECT IDENTIFIER ::= { experimental 10000 }

--
-- TEXTUAL-CONVENTION

IppmOwnerString described as
'0001000001000000'b, '1040'B.
"
SYNTAX OCTET STRING (SIZE (1..64))
IppmMetricsRegistryIndex ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"The owner namespace
"IppmMetricsRegistryIndex defines an unambiguous index for each
standardized metric. It identifies a metric, and as such its
value is defined the value of the node of the metric in the INDEX IPPM
registry. This value is the same in any implementation of a table the
IPPM REPORTING MIB.

Example:
In the IPPM-METRICS-REGISTRY, onewayPacketLossAverage is
registered as a
couple the node 14 of 2 objects where ippmMetricsRegistry.metrics.rfc.
Consequently the type index of the first one metric onewayPacketLossAverage in
the IppmMetricsTable will always be '14'. At large an instance,
which type is
IppmOwnerString IppmMetricsRegistryIndex and which value is '14',
points to the type metric onewayPacketLossAverage."
SYNTAX Unsigned32 (1.. 65535)

GMTTimeStamp ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"The time value at which a measure or an event took place.

field octets contents range
----- ------ -------- -----
1 1-4 second since 1 Jan 1900 0H00* 0..2^31 - 1
2 5-8 fractional part of the second second* 0..2^32 - 1
* the value is IppmOwnerIndex.
IppmOwnerString in network-byte order

The timestamp format is an OwnerString which length the NTP timestamp format [RFC 1305].
The reference of time is limited to 32
bytes." GMT.

"
SYNTAX OCTET STRING (SIZE (0..32))

IppmOwnerIndex (8))
PacketType ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"The owner namespace
"This textual convention is defined in a display string used to describe the INDEX
protocol encapsulation list of a table packet, and is used as a
couple the value
of 2 objects where the SYNTAX clause for the type of first one is
IppmOwnerString the Src and Dst of an IPPM
measure. The RFC2895 specifies a macro named PROTOCOL-IDENTIFIER
for the type definition of protocol identifiers, while its companion
document, the second is IppmOwnerIndex.
An object RFC2896 defines a set of type IppmOwnerIndex uniquely identifies protocol identifiers.

PacketType is defined as a row display string. It consists of a
table inside an owner namespace.
Inside one namespace several objects list
of type IppmOwnerIndex
coexist and share dot separated protocol names. Each protocol name has been
previously defined using the IppmOwnerIndex range macro PROTOCOL-IDENTIFIER of values the RFC
2895.

Examples:
The RFC2896 defines the protocol identifiers 'ether2', 'ip',
'ipip4', 'udp', 'tcp', 'telnet'...

The PacketType of the source address corresponding to provide telnet is
the string 'ip.tcp.telnet'.

The PacketType of the source address corresponding to UDP packets
sent in an IP tunnel is the string 'ip.ipip4.udp'.

Note:
An IPPM measure is active, so generally a
unique instance identifier.
"
SYNTAX Unsigned32 (1.. 65535)

TimeUnit ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"A enumerated list PacketType value does
not describe the link layer (i.e. ether2...). Valid Internet
packets are sent from Src to Dst. Then the choice of time units." the link
layer relies on the Internet stack."
SYNTAX INTEGER {
week(1),
day(2),
hour(3),
minute(4),
second(5),
millisecond(6),
microsecond(7),
nanosecond(8)
}
--
--

IppmStandardMetrics OCTET STRING (SIZE (0..512))
PacketTypeAddress ::= TEXTUAL-CONVENTION
DISPLAY-HINT "255a"
STATUS current
DESCRIPTION
" Each standard metric
"This textual convention is identified in a Display string used to describe the IPPM-METRICS-
REGISTRY under
parameters of the node rfc in chronological order. In order to
allow for several metrics to be calculated in protocol encapsulation list of a single measure,
there packet,
basically the address.

PacketTypeAddress is defined as a need to describe display string. It consists in
a bit string the metrics to be
measured.

This textual convention defines an octet string list of blank separated addresses that gathers reflect the
encapsulation of the PacketType. Each parameter in the list
corresponds to a
bit string parameter of a sequence PROTOCOL-IDENTIFIER of bits. the
PacketType.
Example:
The bit order corresponds PacketType 'ip.ipip4' has 2 parameters. A valid
PacketTypeAddress value is '192.168.1.1 128.2.6.7'."
SYNTAX OCTET STRING (SIZE (0..512))

IppmMetricResultFilter ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"Given that not all results from a metric measurement are
pertinent, and that the size of the history must be limited whenever
possible, the TC IppmMetricResultFilter defines basic filters to
limit the
order among of data collected:

Filter's parameters are the 2 fields ippmAggrMeasureLowThreshold and
ippmAggrMeasureLowThreshold of the metric identifiers in aggregated measure setup.

A filter determines if the registry.
The first bit result of the string current aggregation has the index 0. The index 1
corresponds to
be stored:

LogInBandValue:
The value is stored if it is lower than the first metric high threshold of
the registry
(instantaneousUnidirectionalConnectivity ).

Example:
One-way-Delay(6) aggregated measure setup and greater than the low
threshold of of the aggregated measure setup.

LogOutBandValue:
The value is identified as stored if it is greater than the leaf number 6 high threshold
of the node
rfc aggregated measure setup or lower than the low
threshold of the registry. One-way-Packet-Loss(12) aggregated measure setup.

LogAboveValue:
The value is identified as the
leaf number 12 of stored if it is greater than the node
rfc high threshold
of the registry. A network aggregated measure performing both One-way-
Delay(6) and One-way-Packet-Loss(12) will be described as
'0001000001000000'b, '1040'B.
"
SYNTAX OCTET STRING (SIZE (1..64))

IppmMetricsRegistryIndex ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"IppmMetricsRegistryIndex defines an unambiguous index for each
standardized metric. It identifies a metric, and as such its setup.

LogBelowValue:
The value is stored if it is lower than the value low metric
threshold field of the node aggregated measure setup.

logUpAndDownValue:
This filter stores contiguous results that are on opposite
sides of the up and down metric in thresholds:
A result is stored if it is the IPPM
registry. This first result aggregated:
If it is greater than the high threshold and lower than the
low threshold then its value is set to the same in any implementation value of the
IPPM REPORTING MIB.

Example:
In low
threshold;

A result greater than the IPPM-METRICS-REGISTRY, onewayPacketLossAverage high threshold is
registered as the node 14 of ippmMetricsRegistry.metrics.rfc.
Consequently stored if the index of
previous result is lower than the metric onewayPacketLossAverage in low threshold;

A result lower than the IppmMetricsTable will always be '14'. At large an instance,
which type low threshold is IppmMetricsRegistryIndex and which value stored if the
previous result is '14',
points to greater than the metric onewayPacketLossAverage." high threshold;

"
SYNTAX INTEGER {
logInBandValue(1),
logOutBandValue(2),
logAboveValue(3),
logBelowValue(4),
logUpAndDownValue(5)
}

--
-- IPPM Notifications
--
ippmNotifications OBJECT IDENTIFIER ::= { ippm 0 }

--
-- IPPM MIB Object definitions
--
ippmMibObjects OBJECT IDENTIFIER ::= { ippm 1 }

ippmSystem OBJECT IDENTIFIER ::= { ippmMibObjects 1 }
ippmOwners OBJECT IDENTIFIER ::= { ippmMibObjects 2 }
ippmHistory OBJECT IDENTIFIER ::= { ippmMibObjects 3 }
ippmNetMeasure OBJECT IDENTIFIER ::= { ippmMibObjects 4 }
ippmAggrMeasure OBJECT IDENTIFIER ::= { ippmMibObjects 5 }

--
-- IPPM Conformance
--
ippmConformance OBJECT IDENTIFIER ::= { ippm 2 }

--
-- ippmSystem Group
--
--

ippmSystemTime OBJECT-TYPE
SYNTAX Unsigned32 (1.. 65535) GMTTimeStamp ::= TEXTUAL-CONVENTION
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The current time value at which a measure or an event took place.

field octets contents range
----- ------ -------- -----
1 1-4 second since 1 Jan 1900 0H00* 0..2^31 - 1
2 5-8 fractional part of the second* 0..2^32 - 1
* system running the value IPPM REPORTING MIB
SNMP agent. When the agent is running in network-byte order

The timestamp format proxy mode, it is the NTP timestamp format [RFC 1305].
The reference of time is GMT.

"
SYNTAX OCTET STRING (SIZE (8))

PacketType ::= TEXTUAL-CONVENTION
STATUS
current
DESCRIPTION
"This textual convention is a display string used to describe the
protocol encapsulation list of a packet, and is used as the value time of the SYNTAX clause for proxy agent.
When the type of agent is located in the Src and Dst of an IPPM
measure. The RFC2895 specifies a macro named PROTOCOL-IDENTIFIER
for probe, it is the definition current time
of protocol identifiers, while its companion
document, the RFC2896 defines a set of protocol identifiers.

PacketType is defined as a display string. It consists of a list
of dot separated protocol names. Each protocol name has been
previously defined using probe agent. "
::= { ippmSystem 1 }

ippmSystemSynchronizationType OBJECT-TYPE
SYNTAX INTEGER {
other(0),

ntp(1),
gps(2),
cdma(3)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"ippmSystemSynchronizationType describes the macro PROTOCOL-IDENTIFIER of mechanism
used to synchronize the RFC
2895.

Examples:
The RFC2896 defines system running the protocol identifiers 'ether2', 'ip',
'ipip4', 'udp', 'tcp', 'telnet'... IPPM REPORTING MIB
SNMP agent.

Other(0)
The PacketType of synchronization process must be defined
in the source address corresponding to telnet ippmSystemSynchonizationDescription.

Ntp(1)
The system is synchronized using the string 'ip.tcp.telnet'. network
time protocol. The PacketType of the source address corresponding to UDP packets
sent NTP synchronization must be described
in an IP tunnel the ippmSystemSynchonizationDescription.

Gps(2)
The system is synchronized using the string 'ip.ipip4.udp'.

Note:
An IPPM measure GPS clocks.

Cdma(3)
The system is active, so generally a PacketType value does
not describe synchronized using the link layer (i.e. ether2...). Valid Internet
packets are sent from Src to Dst. Then CDMA clocks."
::= { ippmSystem 2 }

ippmSystemSynchronizationDesc OBJECT-TYPE
SYNTAX SnmpAdminString
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The description of the choice synchronization process of the link
layer relies on system
running the Internet stack."
SYNTAX OCTET STRING (SIZE (0..512))

PacketTypeAddress IPPM REPORTING MIB SNMP agent."
::= TEXTUAL-CONVENTION
DISPLAY-HINT "255a" { ippmSystem 3 }

ippmSystemClockResolution OBJECT-TYPE
SYNTAX Unsigned32
UNITS "Nanoseconds"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This textual convention is a Display string used to describe
"ippmSystemClockResolution provides the
parameters precision of the protocol encapsulation list of a packet,
basically clock
used for the address.

PacketTypeAddress measures . The unit is defined as a display string. It consists in
a list of blank separated addresses that reflect the
encapsulation of the PacketType. Each parameter in nanosecond. For example,
the list
corresponds to a parameter of clock on an old Unix host might advance only once every 10
msec, and thus have a PROTOCOL-IDENTIFIER resolution of 10 msec. So its resolution
is 10000000 nanoseconds and the
PacketType.
Example:

The PacketType 'ip.ipip4' has 2 parameters. A valid
PacketTypeAddress value of
ippmSystemClockResolution is '192.168.1.1 128.2.6.7'."
SYNTAX OCTET STRING (SIZE (0..512))

IppmMetricResultFilter 10000000."
::= TEXTUAL-CONVENTION { ippmSystem 4 }

ippmSystemOperationalStatus OBJECT-TYPE

SYNTAX INTEGER {
unknown(0),
up(1),
down(2)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
" Given that not all results from a metric measurement are
pertinent, and that
"This object describes the size status of the history must be limited whenever
possible, system running the TC IppmMetricResultFilter defines basic filters to
limit IPPM
REPORTING MIB SNMP agent. It does not describe end point
measurement status:

unknown(0) means the among of data collected:

Filter's parameters are service is unknown.
up(1) means the 2 fields ippmAggrMeasureLowThreshold service is operational and
ippmAggrMeasureLowThreshold of available for
general use.
down(2) means the agent is not available for use.
"
::= { ippmSystem 5 }

ippmSystemAggregatedMetrics OBJECT-TYPE
SYNTAX IppmStandardMetrics
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"ippmSystemAggregatedMetrics lists the aggregated measure setup.

A filter determines if metrics that
are performed in the result SNMP agent instead of in the point of
measure."
::= { ippmSystem 6 }
ippmSynchronizationTable OBJECT-TYPE
SYNTAX SEQUENCE OF IppmSynchronizationEntry
MAX-ACCESS not-accessible
STATUS current aggregation has
DESCRIPTION
"This table registers the event related to
be stored:

LogInBandValue:
The value is stored if it is lower than the high threshold synchronization
of the aggregated measure setup and greater than the low
threshold points of measure. Each event is described in an
ippmSynchronizationEntry.
ippmSynchronizationTable is mandatory.
ippmSynchronizationTable content is read only."
::= { ippmSystem 7 }

ippmSynchronizationEntry OBJECT-TYPE
SYNTAX IppmSynchronizationEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry describes a modification of the aggregated measure setup.

LogOutBandValue:
The value synchronization
status."
INDEX { ippmPointOfMeasureIndex, ippmSynchronizationIndex }
::= { ippmSynchronizationTable 1 }

IppmSynchronizationEntry ::=
SEQUENCE {
ippmSynchronizationIndex Unsigned32,
ippmSynchronizationTime GMTTimeStamp,
ippmSynchronizationStratum Unsigned32,
ippmSynchronizationResolution Unsigned32
}

ippmSynchronizationIndex OBJECT-TYPE
SYNTAX Unsigned32 (1 .. 65535)
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An index that identifies the synchronization events in
chronological order.
65535 is stored if it an arbitrary size. It is greater than not recommended to keep
permanently a history of 65535 events."
::= { ippmSynchronizationEntry 1 }

ippmSynchronizationTime OBJECT-TYPE
SYNTAX GMTTimeStamp
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The time when the high threshold synchronization event occurs."
::= { ippmSynchronizationEntry 2 }

ippmSynchronizationStratum OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The stratum level of the aggregated measure setup or lower than clock computed when the low
threshold of
synchronization event occurs."
::= { ippmSynchronizationEntry 3 }

ippmSynchronizationResolution OBJECT-TYPE
SYNTAX Unsigned32
UNITS "Nanoseconds"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The new time resolution computed after the aggregated measure setup.

LogAboveValue:
The value is stored if it synchronization
event occurred."
::= { ippmSynchronizationEntry 4 }

ippmPointOfMeasureTable OBJECT-TYPE
SYNTAX SEQUENCE OF IppmPointOfMeasureEntry
MAX-ACCESS not-accessible
STATUS current

DESCRIPTION
" This table is greater than the high threshold list of measurement end points available
in the aggregated measure setup.

LogBelowValue:
The value is stored if it measurement system.

Proxy mode:
It is lower than the low metric
threshold field list of the aggregated measure setup.

logUpAndDownValue:
This filter stores contiguous results that are on opposite
sides measurement end points of the up and down metric thresholds:
A result is stored if it is the first result aggregated:
If it is greater than the high threshold and lower than set of
probes for which the
low threshold then its value IPPM agent provides an SNMP interface.

IPPM MIB implemented in a probe:
It is set to the value list of the low
threshold;

A result greater than the high threshold is stored if measurement end points of the
previous result probe.

The ippmPointOfMeasureTable content is lower than the low threshold;

A result lower than read only. This
implies that the low threshold is stored if measurement software handles the
previous result table
internally ippmPointOfMeasureTable is greater than the high threshold;

"
SYNTAX INTEGER {
logInBandValue(1),
logOutBandValue(2),
logAboveValue(3),
logBelowValue(4),
logUpAndDownValue(5)
}

--
-- IPPM Notifications
--
ippmNotifications OBJECT IDENTIFIER mandatory."
::= { ippm 0 ippmSystem 8 }

--
-- IPPM Conformance
--
ippmConformance OBJECT IDENTIFIER ::=

ippmPointOfMeasureEntry OBJECT-TYPE
SYNTAX IppmPointOfMeasureEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
" An entry may be the management address of some middleware in
charge of the management of a set of probes. It may the
management address of a probe that contains several line
cards.

An entry describes the capability of a point of measure.

ippmPointOfMeasureMetrics lists the metrics handles by the
point of measure."
INDEX { ippm 1 ippmPointOfMeasureIndex }

--
-- IPPM MIB Object definitions
--

ippmSystem OBJECT IDENTIFIER
::= { ippmReportingMib ippmPointOfMeasureTable 1 }
ippmOwners OBJECT IDENTIFIER ::= { ippmReportingMib 2 }
ippmHistory OBJECT IDENTIFIER

IppmPointOfMeasureEntry ::= SEQUENCE { ippmReportingMib 3
ippmPointOfMeasureIndex Unsigned32,
ippmPointOfMeasureMgmtAddrType InetAddressType,
ippmPointOfMeasureMgmtAddress InetAddress,
ippmPointOfMeasureTestAddrType InetAddressType,
ippmPointOfMeasureTestAddress InetAddress,
ippmPointOfMeasureMetrics IppmStandardMetrics
}
ippmNetMeasure OBJECT IDENTIFIER

ippmPointOfMeasureIndex OBJECT-TYPE
SYNTAX Unsigned32 (1 .. 65535)
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A local index that identifies an entry in the point of
measure table."

::= { ippmReportingMib 4 ippmPointOfMeasureEntry 1 }
ippmAggrMeasure OBJECT IDENTIFIER

ippmPointOfMeasureMgmtAddrType OBJECT-TYPE
SYNTAX InetAddressType
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The address type associated with the management address."
::= { ippmReportingMib 5 ippmPointOfMeasureEntry 2 }

--
-- ippmSystem Group
--
--

ippmSystemTime
ippmPointOfMeasureMgmtAddress OBJECT-TYPE
SYNTAX GMTTimeStamp InetAddress (SIZE (1..128))
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The current time of the system running the IPPM REPORTING MIB
SNMP agent. When the agent is running in proxy mode, it is management address on the
current time point of measure"
::= { ippmPointOfMeasureEntry 3 }

ippmPointOfMeasureTestAddrType OBJECT-TYPE
SYNTAX InetAddressType
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Defines the proxy agent.
When the agent is located in the probe, it is address type of the current time measurement interface of the probe agent. "
point of measure."
::= { ippmSystem 1 ippmPointOfMeasureEntry 4 }

ippmSystemSynchronizationType

ippmPointOfMeasureTestAddress OBJECT-TYPE
SYNTAX INTEGER {
other(0),
ntp(1),
gps(2),
cdma(3)
} InetAddress
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"ippmSystemSynchronizationType describes
"Specifies the mechanism
used to synchronize address of the system running measurement interface for the IPPM REPORTING MIB
SNMP agent.

Other(0)
The synchronization process must be defined
in
point of measure."
::= { ippmPointOfMeasureEntry 5}

ippmPointOfMeasureMetrics OBJECT-TYPE
SYNTAX IppmStandardMetrics
MAX-ACCESS read-only
STATUS current
DESCRIPTION
" ippmPointOfMeasureMetrics lists the ippmSystemSynchonizationDescription.

Ntp(1)
The system metrics this point of
measure implements."
::= { ippmPointOfMeasureEntry 6 }

ippmMetricsTable OBJECT-TYPE
SYNTAX SEQUENCE OF IppmMetricsEntry
MAX-ACCESS not-accessible

STATUS current
DESCRIPTION
"This table is synchronized using mandatory. It describes the network
time protocol. The NTP synchronization current
implementation. Each IPPM standardized metric must be
described in the ippmSystemSynchonizationDescription.

Gps(2)
The system is synchronized using the GPS clocks.

Cdma(3)
The system table.
ippmMetricsTable content is synchronized using the CDMA clocks." read only."
::= { ippmSystem 2 9 }

ippmSystemSynchronizationDesc

ippmMetricsEntry OBJECT-TYPE
SYNTAX IppmMetricsEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry describes the static capabilities of a metric
implementation."
INDEX { ippmMetricsIndex }
::= { ippmMetricsTable 1 }

IppmMetricsEntry ::=
SEQUENCE {
ippmMetricsIndex IppmMetricsRegistryIndex,
ippmMetricsType INTEGER,
ippmMetricsUnit INTEGER,
ippmMetricsDescription SnmpAdminString
}

ippmMetricsIndex OBJECT-TYPE
SYNTAX IppmMetricsRegistryIndex
MAX-ACCESS read-only not-accessible
STATUS current
DESCRIPTION
"The description
"ippmMetricsIndex defines an unambiguous index for each
standardized metric. It identifies a metric, and as such its
value is the value of the synchronization process node of the system
running metric in the IPPM
registry. This value is the same in any implementation of the
IPPM REPORTING MIB SNMP agent." MIB.

Example:
In the IPPM-METRICS-REGISTRY, onewayPacketLossAverage is
registered as the node 14 of ippmMetricsRegistry.metrics.rfc.
Consequently the index of the metric onewayPacketLossAverage
in the IppmMetricsTable will always be '14'"
::= { ippmSystem 3 ippmMetricsEntry 1 }

ippmSystemClockResolution

ippmMetricsType OBJECT-TYPE
SYNTAX Unsigned32
UNITS "Nanoseconds" INTEGER {
network(0),
aggregated(1)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"ippmSystemClockResolution provides the precision of the clock
used for the measures . The unit is the nanosecond. For example,
the clock on an old Unix host might advance only once every 10
msec, and thus have a resolution of 10 msec. So its resolution is
10000000 nanoseconds and
"Indicates the value of ippmSystemClockResolution metric type, whether it is 10000000." network or
aggregated."
::= { ippmSystem 4 ippmMetricsEntry 2 }

ippmSystemOperationalStatus

ippmMetricsUnit OBJECT-TYPE
SYNTAX INTEGER {
unknown(0),
up(1),
down(2)
noUnit(0),
second(1),
millisecond(2),
microsecond(3),
nanosecond(4),
percentage(5),
packet(6),
byte(7),
kilobyte(8),
megabyte(9)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object describes
"The unit used in the status of current entity for the system running results of the IPPM
REPORTING MIB SNMP agent. It does not describe end point
measurement
status.
unknown(0) means the service is unknown.
up(1) means the service is operational and available for general
use.
down(2) means the agent is not available for use.
" of this metric."
::= { ippmSystem 5 ippmMetricsEntry 3 }

ippmSystemAggregatedMetrics

ippmMetricsDescription OBJECT-TYPE
SYNTAX IppmStandardMetrics SnmpAdminString
MAX-ACCESS read-only
STATUS current
DESCRIPTION
" ippmSystemAggregatedMetrics lists
"A textual description of the aggregated metrics that
are performed in metric implementation following
the SNMP agent instead exact name of this metric in the point of
measure." registry. For example:
oneWayDelay: OWD Metric ."
::= { ippmSystem 6 ippmMetricsEntry 4 }

ippmSynchronizationTable

--
-- ippmOwners Group
--
-- The ippmOwners objects are responsible for managing
-- the owners access to the measurements.

--
--

ippmOwnersTable OBJECT-TYPE
SYNTAX SEQUENCE OF IppmSynchronizationEntry IppmOwnersEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This table registers the event related
"A management entity wishing to the synchronization of
the points of measure. Each event is described access or aggregate remote Ippm
measurements in an
ippmSynchronizationEntry.
ippmSynchronizationTable is mandatory.
ippmSynchronizationTable content agent must previously be registered in the
ippmOwnersTable. This table is read only." read-create and contains at least the
owner 'monitor'."

::= { ippmSystem 7 ippmOwners 1 }

ippmSynchronizationEntry

ippmOwnersEntry OBJECT-TYPE
SYNTAX IppmSynchronizationEntry IppmOwnersEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry describes a modification
"The description of the synchronization
status." resources granted to an SNMP
application.

For example, an instance of ippmOwnersOwner with an
IppmOwnerString 'acme', which represents the 14th owner
created in ippmOwnersTable would be named
ippmOwnersEntryOwner.14.
"
INDEX { ippmPointOfMeasureIndex, ippmSynchronizationIndex ippmOwnersOwner }
::= { ippmSynchronizationTable ippmOwnersTable 1 }

IppmSynchronizationEntry

IppmOwnersEntry ::= SEQUENCE {
ippmSynchronizationIndex Unsigned32,
ippmSynchronizationTime GMTTimeStamp,
ippmSynchronizationStratum
ippmOwnersOwner IppmOwnerString,
ippmOwnersGrantedMetrics IppmStandardMetrics,
ippmOwnersQuota Unsigned32,
ippmSynchronizationResolution Unsigned32
ippmOwnersIpAddressType InetAddressType,
ippmOwnersIpAddress InetAddress,
ippmOwnersEmail SnmpAdminString,
ippmOwnersStatus RowStatus
}

ippmSynchronizationIndex

ippmOwnersOwner OBJECT-TYPE
SYNTAX Unsigned32 (1 .. 65535) IppmOwnerString
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An index that identifies the synchronization events in
chronological order.
65535 is an arbitrary size. It is not recommended to keep
permanently a history of 65535 events."
::= { ippmSynchronizationEntry 1 }

ippmSynchronizationTime OBJECT-TYPE
SYNTAX GMTTimeStamp
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The time when the synchronization event occurs."
::= { ippmSynchronizationEntry 2 }

ippmSynchronizationStratum OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The stratum level of the clock computed when the synchronization
event occurs." owner described by this entry."
::= { ippmSynchronizationEntry 3 ippmOwnersEntry 1 }

ippmSynchronizationResolution
ippmOwnersGrantedMetrics OBJECT-TYPE
SYNTAX Unsigned32
UNITS "Nanoseconds" IppmStandardMetrics
MAX-ACCESS read-only read-create
STATUS current
DESCRIPTION
"The new time resolution computed after
" Defines the synchronization event
occurred." metrics granted to an owner for which
measurements can be performed."
::= { ippmSynchronizationEntry 4 ippmOwnersEntry 2 }

ippmPointOfMeasureTable

ippmOwnersQuota OBJECT-TYPE
SYNTAX SEQUENCE OF IppmPointOfMeasureEntry Unsigned32
MAX-ACCESS not-accessible read-create
STATUS current
DESCRIPTION
" This table is the list
"The maximum number of measurement end points available records that this owner may have in the measurement system.

Proxy mode:
It is the list of the measurement end points of the set of probes
for which the IPPM agent provides an SNMP interface.

IPPM MIB implemented
history table and in a probe:
It is the list of the measurement end points of the probe.

The ippmPointOfMeasureTable content is read only. This implies
that the measurement software handles the table internally

ippmPointOfMeasureTable is mandatory." report table."
::= { ippmSystem 8 ippmOwnersEntry 3 }

ippmPointOfMeasureEntry

ippmOwnersIpAddressType OBJECT-TYPE
SYNTAX IppmPointOfMeasureEntry InetAddressType
MAX-ACCESS not-accessible read-create
STATUS current
DESCRIPTION
" An entry may be the management
"The IP address type of some middleware in
charge of the management of a set of probes. It may the management address of a probe that contains several line cards.

An entry describes the capability of a point of measure.

ippmPointOfMeasureMetrics lists the metrics handles by the point
of measure."
INDEX { ippmPointOfMeasureIndex }
::= { ippmPointOfMeasureTable 1 }

IppmPointOfMeasureEntry entity corresponding to
this owner.
InetAddressType is restricted to ipv4(1),ipv6(2)and dns(16)."
::= SEQUENCE {
ippmPointOfMeasureIndex Unsigned32,
ippmPointOfMeasureMgmtAddrType InetAddressType,
ippmPointOfMeasureMgmtAddress InetAddress,
ippmPointOfMeasureTestAddrType InetAddressType,
ippmPointOfMeasureTestAddress InetAddress,
ippmPointOfMeasureMetrics IppmStandardMetrics ippmOwnersEntry 4 }

ippmPointOfMeasureIndex

ippmOwnersIpAddress OBJECT-TYPE
SYNTAX Unsigned32 (1 .. 65535) InetAddress (SIZE (1..128))
MAX-ACCESS not-accessible read-create
STATUS current
DESCRIPTION
"A local index that identifies an entry in
"The IP address of the management entity corresponding to this
owner. For example, the point IP address of measure
table." the management console
used to send SNMP requests."
::= { ippmPointOfMeasureEntry 1 ippmOwnersEntry 5 }

ippmPointOfMeasureMgmtAddrType

ippmOwnersEmail OBJECT-TYPE
SYNTAX InetAddressType SnmpAdminString
MAX-ACCESS read-only read-create
STATUS current
DESCRIPTION
"The email address type associated with of the management address." entity corresponding to
this owner."
::= { ippmPointOfMeasureEntry 2 ippmOwnersEntry 6 }

ippmPointOfMeasureMgmtAddress
ippmOwnersStatus OBJECT-TYPE
SYNTAX InetAddress (SIZE (1..128)) RowStatus
MAX-ACCESS read-only read-create
STATUS current
DESCRIPTION
"The management address on the point status of measure" this table entry. Once this status is set to
active, the corresponding entry in the table may not be
modified."
::= { ippmPointOfMeasureEntry 3 ippmOwnersEntry 7 }

ippmPointOfMeasureTestAddrType

--
-- ippmHistory Group
--
--
-- ippmHistoryTable
--

ippmHistoryTable OBJECT-TYPE
SYNTAX InetAddressType SEQUENCE OF IppmHistoryEntry
MAX-ACCESS read-only not-accessible

STATUS current
DESCRIPTION
"Defines the address type of
"The table containing the measurement interface of the
point of measure." results."
::= { ippmPointOfMeasureEntry 4 ippmHistory 1 }

ippmPointOfMeasureTestAddress

ippmHistoryEntry OBJECT-TYPE
SYNTAX InetAddress IppmHistoryEntry
MAX-ACCESS read-only not-accessible
STATUS current
DESCRIPTION
"Specifies
"An ippmHistoryEntry entry is one of the address results of a measure
identified by ippmHistoryMeasureOwner, ippmHistoryMeasureIndex,
ippmHistoryMetricIndex and ippmHistorySequence.

In the index :

+ ippmHistoryMeasureOwner identifies the owner of the measure;

+ ippmHistoryMeasureIndex identifies the measure in the owner
namespace;

+ ippmHistoryMetricIndex identifies the metric measured by the
measure. The metric is described in the corresponding entry of
the ippmMetricsTable;

+ ippmHistorySequence is the sequence number of the measurement interface
result for an entry in the point
of measure." history table."
INDEX { ippmHistoryMeasureOwner, ippmHistoryMeasureIndex,
ippmHistoryMetricIndex, ippmHistorySequence }
::= { ippmPointOfMeasureEntry 5}

ippmPointOfMeasureMetrics ippmHistoryTable 1 }

IppmHistoryEntry ::=
SEQUENCE {
ippmHistoryMeasureOwner IppmOwnerString,
ippmHistoryMeasureIndex IppmOwnerIndex,
ippmHistoryMetricIndex IppmMetricsRegistryIndex,
ippmHistorySequence Unsigned32,
ippmHistoryTimestamp GMTTimeStamp,
ippmHistoryValue Integer32
}

ippmHistoryMeasureOwner OBJECT-TYPE
SYNTAX IppmStandardMetrics IppmOwnerString
MAX-ACCESS read-only not-accessible
STATUS current
DESCRIPTION
" ippmPointOfMeasureMetrics lists
"The owner of the metrics measure that produced this point of result. The
measure implements." is either an ippmNetMeasure or an ippmAggrMeasure."
::= { ippmPointOfMeasureEntry 6 { ippmHistoryEntry 1 }

ippmMetricsTable

ippmHistoryMeasureIndex OBJECT-TYPE
SYNTAX SEQUENCE OF IppmMetricsEntry IppmOwnerIndex
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This table
"The owner index of the measure that produced this result. The
measure is mandatory. It describes either an entry of the current
implementation. Each IPPM standardized metric must be described
in ippmNetMeasureTable or of
the table.
ippmMetricsTable content is read only." ippmAggrMeasureTable."
::= { ippmSystem 9 ippmHistoryEntry 2 }

ippmMetricsEntry

ippmHistoryMetricIndex OBJECT-TYPE
SYNTAX IppmMetricsEntry IppmMetricsRegistryIndex
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry describes
" ippmHistoryMetricIndex identifies the static capabilities of a metric
implementation."
INDEX { ippmMetricsIndex }
::= { ippmMetricsTable 1 }

IppmMetricsEntry measured by the
measure. The metric is described in the corresponding entry of
the ippmMetricsTable."
::=
SEQUENCE {
ippmMetricsIndex IppmMetricsRegistryIndex,
ippmMetricsType INTEGER,
ippmMetricsUnit INTEGER,
ippmMetricsDescription SnmpAdminString ippmHistoryEntry 3 }

ippmMetricsIndex
ippmHistorySequence OBJECT-TYPE
SYNTAX IppmMetricsRegistryIndex Unsigned32 (0..4294967295)
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"ippmMetricsIndex defines an unambiguous index
"ippmHistorySequence is the sequence number of the measurement
results for each
standardized metric. It identifies a metric, and as such its
value is metric.

Network metrics:
It's the value sequence number of a measurement packet. Typically,
it identifies the node order of the metric packet in the IPPM
registry. This value is the same in any implementation stream of packets
sent by the
IPPM REPORTING MIB.

Example:
In the IPPM-METRICS-REGISTRY, onewayPacketLossAverage source.

Aggregated metrics:
It is
registered as the node 14 of ippmMetricsRegistry.metrics.rfc.
Consequently the index sequence order of the metric onewayPacketLossAverage in
the IppmMetricsTable will always be '14'" aggregation computed."
::= { ippmMetricsEntry 1 ippmHistoryEntry 4 }

ippmMetricsType

ippmHistoryTimestamp OBJECT-TYPE
SYNTAX INTEGER {
network(0),
aggregated(1)
} GMTTimeStamp
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Indicates
"The timestamp when the metric type, whether it is network or aggregated" measurement occurred."
::= { ippmMetricsEntry 2 ippmHistoryEntry 5 }

ippmMetricsUnit

ippmHistoryValue OBJECT-TYPE
SYNTAX INTEGER {
noUnit(0),
second(1),
millisecond(2),
microsecond(3),
nanosecond(4),
percentage(5),
packet(6),
byte(7),
kilobyte(8),
megabyte(9)
} Integer32

MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The unit used in the current entity for the results observed value of the
measurement of this metric." measurement."
::= { ippmMetricsEntry 3 ippmHistoryEntry 6 }

ippmMetricsDescription

ippmHistoryPathToResults OBJECT-TYPE
SYNTAX SnmpAdminString
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"A textual description of the metric implementation following the
exact name of this metric in
"It is typically an URL describing the registry. For example:
oneWayDelay: OWD Metric ." file location where
bulk results are logged."
::= { ippmMetricsEntry 4 ippmHistory 2 }
--
-- ippmOwners ippmNetMeasure Group
--

-- The ippmOwners objects are responsible for managing
-- the owners access to the measurements. ippmNetMeasureTable
--
--
ippmOwnersTable

ippmNetMeasureTable OBJECT-TYPE
SYNTAX SEQUENCE OF IppmOwnersEntry IppmNetMeasureEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A management entity wishing to access or aggregate remote Ippm
"An entry is a measurement that performs network measures and
provides results.
It performs several metric measurements in an agent must previously be registered in per packet exchange.
Each step of a measure produces a singleton result per metric.
The time of the
ippmOwnersTable. This table is read-create measurement and contains at least the
owner 'monitor'." value of the metric are
saved in the ippmHistoryTable."
::= { ippmOwners ippmNetMeasure 1 }

ippmOwnersEntry

ippmNetMeasureEntry OBJECT-TYPE
SYNTAX IppmOwnersEntry IppmNetMeasureEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The description
" The IppmNetMeasureTable is mandatory, and its content is read
only. It means that the measurement software handles the table
internally. The setup of the resources granted to network measure is not permitted
through the IPPM REPORTING MIB. As an SNMP application.

For example, an instance OWAP provides a
setup protocol to setup and tear down networks measures.

The ippmNetMeasureMetrics is set to a list of ippmOwnersOwner with an
IppmOwnerString 'acme', which represents metrics to be
computed from the 14th owner created same raw packet exchange. Each step of
measurement delivers a singleton per metric. Results are
timestamped and saved in ippmOwnersTable would be named ippmOwnersEntryOwner.14.
" the ippmHistoryTable.

One may create aggregated measures by using the results of
network measures."

INDEX { ippmOwnersOwner ippmNetMeasureOwner, ippmNetMeasureIndex }
::= { ippmOwnersTable ippmNetMeasureTable 1 }

IppmOwnersEntry

IppmNetMeasureEntry ::= SEQUENCE {
ippmOwnersOwner
ippmNetMeasureOwner IppmOwnerString,
ippmOwnersGrantedMetrics
ippmNetMeasureIndex IppmOwnerIndex,
ippmNetMeasureName SnmpAdminString,
ippmNetMeasureMetrics IppmStandardMetrics,
ippmOwnersQuota
ippmNetMeasureBeginTime GMTTimeStamp,
ippmNetMeasureCollectionRateUnit TimeUnit,
ippmNetMeasureCollectionRate Unsigned32,
ippmOwnersIpAddressType InetAddressType,
ippmOwnersIpAddress InetAddress,
ippmOwnersEmail SnmpAdminString,
ippmOwnersStatus RowStatus
ippmNetMeasureDurationUnit TimeUnit,
ippmNetMeasureDuration Unsigned32,
ippmNetMeasureHistorySize Unsigned32,
ippmNetMeasureFailureMgmtMode INTEGER,
ippmNetMeasureResultsMgmt INTEGER,
ippmNetMeasureSrcPacketType PacketType,
ippmNetMeasureSrc PacketTypeAddress,
ippmNetMeasureDstPacketType PacketType,
ippmNetMeasureDst PacketTypeAddress,
ippmNetMeasureTxMode INTEGER,
ippmNetMeasureTxPacketRateUnit TimeUnit,
ippmNetMeasureTxPacketRate Unsigned32,
ippmNetMeasureMedOrBurstSize Unsigned32,
ippmNetMeasureDevOrIntBurstSize Unsigned32,
ippmNetMeasureLossTimeout Unsigned32,
ippmNetMeasureL3PacketSize Unsigned32,
ippmNetMeasureDataPattern OCTET STRING,
ippmNetMeasureTotalPktsRecv Counter64,
ippmNetMeasureLastUpdate GMTTimeStamp,
ippmNetMeasureOperState INTEGER
}

ippmOwnersOwner

ippmNetMeasureOwner OBJECT-TYPE
SYNTAX IppmOwnerString
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The owner described by this entry." of the network measure."
::= { ippmOwnersEntry ippmNetMeasureEntry 1 }

ippmOwnersGrantedMetrics

ippmNetMeasureIndex OBJECT-TYPE
SYNTAX IppmStandardMetrics IppmOwnerIndex
MAX-ACCESS read-create not-accessible
STATUS current
DESCRIPTION
" Defines the metrics granted to an
"The owner for which measurements
can be performed." index of the network measure."
::= { ippmOwnersEntry ippmNetMeasureEntry 2 }

ippmOwnersQuota
ippmNetMeasureName OBJECT-TYPE
SYNTAX Unsigned32 SnmpAdminString
MAX-ACCESS read-create
STATUS current
DESCRIPTION
" The maximum number
"The name of records that this owner may have the metric instance(s) as defined in
ippmNetMeasureMetrics. It illustrates the
history table specificity of the
metric(s) and in includes the report table." metric(s) and the PacketType.

Example:
IP-TCP-HTTP-One-way-Delay: free text "
::= { ippmOwnersEntry ippmNetMeasureEntry 3 }

ippmOwnersIpAddressType

ippmNetMeasureMetrics OBJECT-TYPE
SYNTAX InetAddressType IppmStandardMetrics
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The IP address type of
"ippmNetMeasureMetrics defines the management entity corresponding metrics to compute within
this owner.
InetAddressType measure. Only network metrics of the same type are
allowed in this field (e.g. poisson-based metrics and
periodic-based metrics are incompatibles, while one-way delay
and packet loss are generally processed simultaneously: a very
bad delay is potentially a very good packet loss).

Results are saved in the ippmHistoryTable.

Results of a metric are identified using an index of type
IppmMetricsRegistryIndex.

Example:
Given a multi-metrics measure of One-way-Delay(6) and One-way-
Packet-Loss(12). The value of the field ippmNetMeasureMetrics
is restricted to ipv4(1),ipv6(2)and dns(16). '0001000001000000'b, '1040'B. Results are logged in the
ippmHistoryTable where One-way-Delay singletons have a value
of ippmMetricsIndex of 6 while One-way-Packet-Loss singletons
have a value of ippmMetricsIndex of 12.

"
::= { ippmOwnersEntry ippmNetMeasureEntry 4 }

ippmOwnersIpAddress

ippmNetMeasureBeginTime OBJECT-TYPE
SYNTAX InetAddress (SIZE (1..128)) GMTTimeStamp
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The IP address of the management entity corresponding to this
owner. For example,
"Specifies the IP address of time at which the management console used
to send SNMP requests." measurement begins."
::= { ippmOwnersEntry ippmNetMeasureEntry 5 }

ippmOwnersEmail

ippmNetMeasureCollectionRateUnit OBJECT-TYPE
SYNTAX SnmpAdminString TimeUnit
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The email address
"Specifies the unit of the management entity corresponding to this
owner." measurement period."
::= { ippmOwnersEntry ippmNetMeasureEntry 6 }

ippmOwnersStatus

ippmNetMeasureCollectionRate OBJECT-TYPE
SYNTAX RowStatus Unsigned32
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The status
"Gives the period used to collect singletons from the point
of this table entry. Once this status measures. This value is set to
active, used as the corresponding entry cycle period in the table may not be
modified."
report."
::= { ippmOwnersEntry ippmNetMeasureEntry 7 }

--
-- ippmHistory Group
--
--
-- ippmHistoryTable
--

ippmHistoryTable

ippmNetMeasureDurationUnit OBJECT-TYPE
SYNTAX SEQUENCE OF IppmHistoryEntry TimeUnit
MAX-ACCESS not-accessible read-create
STATUS current
DESCRIPTION
"The table containing
"Specifies the measurement results." duration unit."
::= { ippmHistory 1 ippmNetMeasureEntry 8 }

ippmHistoryEntry

ippmNetMeasureDuration OBJECT-TYPE
SYNTAX IppmHistoryEntry Unsigned32
MAX-ACCESS not-accessible read-create
STATUS current
DESCRIPTION
"An ippmHistoryEntry entry is one of the results of a measure
identified by ippmHistoryMeasureOwner, ippmHistoryMeasureIndex,
ippmHistoryMetricIndex and ippmHistorySequence.

In the index :

+ ippmHistoryMeasureOwner identifies the owner of the measure;

+ ippmHistoryMeasureIndex identifies the measure in the owner
namespace;

+ ippmHistoryMetricIndex identifies the metric measured by the
measure. The metric is described in the corresponding entry of
the ippmMetricsTable;

+ ippmHistorySequence is the sequence number of the measurement
result for an entry in
"Specifies the history table."
INDEX { ippmHistoryMeasureOwner, ippmHistoryMeasureIndex,
ippmHistoryMetricIndex, ippmHistorySequence }
::= { ippmHistoryTable 1 }

IppmHistoryEntry measurement duration."
::=
SEQUENCE {
ippmHistoryMeasureOwner IppmOwnerString,
ippmHistoryMeasureIndex IppmOwnerIndex,
ippmHistoryMetricIndex IppmMetricsRegistryIndex,
ippmHistorySequence Unsigned32,
ippmHistoryTimestamp GMTTimeStamp,
ippmHistoryValue Integer32 ippmNetMeasureEntry 9 }

ippmHistoryMeasureOwner

ippmNetMeasureHistorySize OBJECT-TYPE
SYNTAX IppmOwnerString Unsigned32
MAX-ACCESS not-accessible read-create
STATUS current
DESCRIPTION
"The owner of
"Specifies the measure that produced maximum number of results saved for each metric
of this result. The measure
is either an ippmNetMeasure or an ippmAggrMeasure." measure.
Overflow condition will be managed by the object
ippmNetMeasureResultsMgmt. "

::= { ippmHistoryEntry 1 ippmNetMeasureEntry 10 }

ippmHistoryMeasureIndex

ippmNetMeasureFailureMgmtMode OBJECT-TYPE
SYNTAX IppmOwnerIndex INTEGER {
auto(1),
manual(2),
discarded(3)
}
MAX-ACCESS not-accessible read-create
STATUS current
DESCRIPTION
"The owner index of
"This object defines whether this row (and the measure that produced
controlled by this result. The
measure row) is either an entry of the ippmNetMeasureTable restarted automatically, manually,
or discarded upon failure, or reboot of the
ippmAggrMeasureTable." measurement
system:
'auto'
The measure is restarted automatically.
'manual'
The measure has to be restarted manually.
'discarded'
The measure and it results are discarded.
"
::= { ippmHistoryEntry 2 ippmNetMeasureEntry 11 }

ippmHistoryMetricIndex

ippmNetMeasureResultsMgmt OBJECT-TYPE
SYNTAX IppmMetricsRegistryIndex INTEGER {
wrap(1),
suspend(2)
}
MAX-ACCESS not-accessible read-create
STATUS current
DESCRIPTION
" ippmHistoryMetricIndex identifies
Action to take when the metric measured by log is full. The measurement system
owner may choose to either wrap, in which case the
measure. agent
writes over existing records. The metric is described 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 log, and assumes the data has been cleared.
This object indicates the way the measurement results are
managed when the owner quota has been exceeded:
'wrap'
continue the measurement and erase the older entries in
the history.
'suspend'
stop the measure and keep the results in the corresponding entry of
the ippmMetricsTable." history.
"
::= { ippmHistoryEntry 3 ippmNetMeasureEntry 12 }

ippmHistorySequence

ippmNetMeasureSrcPacketType OBJECT-TYPE
SYNTAX Unsigned32 (0..4294967295) PacketType
MAX-ACCESS not-accessible read-create
STATUS current
DESCRIPTION
"ippmHistorySequence is the sequence number of the measurement
results for a metric.

Network metrics:
It's
"Defines the sequence number type P of a measurement packet. Typically, it
identifies the order source address of the packet in the stream of packets sent
by the source.

Aggregated metrics:
It is the sequence order of the aggregation computed." measure."
::= { ippmHistoryEntry 4 ippmNetMeasureEntry 13 }

ippmHistoryTimestamp

ippmNetMeasureSrc OBJECT-TYPE
SYNTAX GMTTimeStamp PacketTypeAddress
MAX-ACCESS read-only read-create
STATUS current
DESCRIPTION
"The timestamp when
"Specifies the measurement occurred."
::= { ippmHistoryEntry 5 }

ippmHistoryValue OBJECT-TYPE
SYNTAX Integer32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The observed value address of the measurement." source of the measure.
It is represented as a list of parameters corresponding to
those of the PROTOCOL IDENTIFIER set in
ippmNetMeasureSrcPacketType."
::= { ippmHistoryEntry 6 }

ippmHistoryPathToResults ippmNetMeasureEntry 14}

ippmNetMeasureDstPacketType OBJECT-TYPE
SYNTAX SnmpAdminString PacketType
MAX-ACCESS read-only read-create
STATUS current
DESCRIPTION
"It is typically an URL describing
"Defines the file location where bulk
results are logged." type P of the destination address of the packets
sent by the measure."
::= { ippmHistory 2 ippmNetMeasureEntry 15 }

--
-- ippmNetMeasure Group
--

--
-- ippmNetMeasureTable
--
--

ippmNetMeasureTable

ippmNetMeasureDst OBJECT-TYPE
SYNTAX SEQUENCE OF IppmNetMeasureEntry PacketTypeAddress
MAX-ACCESS not-accessible read-create
STATUS current
DESCRIPTION
"An entry is a measurement that performs network measures and
provides results.
It performs several metric measurements per packet exchange. Each
step of a measure produces a singleton result per metric. The
time
"Specifies the address of the measurement and destination of the value measure.
It is represented as a list of parameters corresponding to
those of the metric are saved PROTOCOL IDENTIFIER set in
the ippmHistoryTable."
ippmNetMeasureDstPacketType."
::= { ippmNetMeasure 1 ippmNetMeasureEntry 16 }

ippmNetMeasureTxMode OBJECT-TYPE
SYNTAX INTEGER {
other(0),
periodic(1),
poisson(2),
multiburst(3)
}

ippmNetMeasureEntry OBJECT-TYPE
SYNTAX IppmNetMeasureEntry
MAX-ACCESS not-accessible read-create
STATUS current
DESCRIPTION
"
"The transmit mode used to send the packets:

'other'
The IppmNetMeasureTable is mandatory, and its content rule used to send the packets is read
only. It means that unknown.
'periodic'
Packets are sent periodically at ippmNetMeasureTxPacketRate
rate.
'poisson'
Packets are sent using a Poisson law, the measurement software handles median is the table
internally. The setup
value of ippmNetMeasureDevOrIntBurstSize, the network measure deviation is not permitted
through the IPPM REPORTING MIB. As an example, OWAP provides a
setup protocol to setup and tear down networks measures.
ippmNetMeasureMedOrBurstSize.
'multiburst'
Packets are sent bursty at ippmNetMeasureTxPacketRate. The ippmNetMeasureMetrics is set to a list
size of metrics to be
computed from the same raw packet exchange. Each step burst is made of
measurement delivers a singleton per metric. Results are
timestamped and saved in the ippmHistoryTable.

One may create aggregated measures by using ippmNetMeasureMedOrBurstSize
packets.
Between 2 consecutive bursts, transmission stops during the results of
network measures."

INDEX { ippmNetMeasureOwner, ippmNetMeasureIndex }
time needed to send ippmNetMeasureDevOrIntBurstSize.

"
::= { ippmNetMeasureTable 1 ippmNetMeasureEntry 17 }

IppmNetMeasureEntry ::= SEQUENCE {
ippmNetMeasureOwner IppmOwnerString,
ippmNetMeasureIndex IppmOwnerIndex,
ippmNetMeasureName SnmpAdminString,
ippmNetMeasureMetrics IppmStandardMetrics,
ippmNetMeasureBeginTime GMTTimeStamp,
ippmNetMeasureCollectionRateUnit TimeUnit,
ippmNetMeasureCollectionRate Unsigned32,
ippmNetMeasureDurationUnit TimeUnit,
ippmNetMeasureDuration Unsigned32,
ippmNetMeasureHistorySize Unsigned32,
ippmNetMeasureFailureMgmtMode INTEGER,
ippmNetMeasureResultsMgmt INTEGER,
ippmNetMeasureSrcPacketType PacketType,
ippmNetMeasureSrc PacketTypeAddress,
ippmNetMeasureDstPacketType PacketType,
ippmNetMeasureDst PacketTypeAddress,
ippmNetMeasureTxMode INTEGER,

ippmNetMeasureTxPacketRateUnit TimeUnit,
ippmNetMeasureTxPacketRate Unsigned32,
ippmNetMeasureMedOrBurstSize Unsigned32,
ippmNetMeasureDevOrIntBurstSize Unsigned32,
ippmNetMeasureLossTimeout Unsigned32,
ippmNetMeasureL3PacketSize Unsigned32,
ippmNetMeasureDataPattern OCTET STRING,
ippmNetMeasureTotalPktsRecv Counter64,
ippmNetMeasureLastUpdate GMTTimeStamp,
ippmNetMeasureOperState INTEGER
}

ippmNetMeasureOwner OBJECT-TYPE
SYNTAX IppmOwnerString TimeUnit
MAX-ACCESS not-accessible read-create
STATUS current
DESCRIPTION
"The owner of packet rate unit used to send the network measure." packets."
::= { ippmNetMeasureEntry 1 18 }

ippmNetMeasureIndex

ippmNetMeasureTxPacketRate OBJECT-TYPE
SYNTAX IppmOwnerIndex Unsigned32
UNITS "Packets"
MAX-ACCESS not-accessible read-create
STATUS current
DESCRIPTION
"The owner index of
DESCRIPTION
"The rate the network measure." packets are sent."
::= { ippmNetMeasureEntry 2 19 }

ippmNetMeasureName

ippmNetMeasureMedOrBurstSize OBJECT-TYPE
SYNTAX SnmpAdminString Unsigned32
UNITS "Packets"
MAX-ACCESS read-only read-create
STATUS current
DESCRIPTION
"The name of
"
Multi-burst mode: This field represents the metric instance(s) as defined burst size in
ippmNetMeasureMetrics. It illustrates
number of packets.
Poisson mode: This field indicates the specificity number of packets sent,
on average, during each period corresponding to the
metric(s) median.
The median is therefore
MedOrBurstSize*TxPacketRateUnit/TxPacketRate.

Example:
If TxPacketRateUnit/TxPacketRate is 100 packets/second, and includes
if MedOrBurstSize, the metric(s) and number of packets sent during the PacketType.

Example:
IP-TCP-HTTP-One-way-Delay: free text
period corresponding to the median is 50 packets, then the
median equals 50*1/100 = 1/2 seconds.
"
::= { ippmNetMeasureEntry 3 20 }

ippmNetMeasureMetrics

ippmNetMeasureDevOrIntBurstSize OBJECT-TYPE
SYNTAX IppmStandardMetrics Unsigned32
UNITS "Packets"
MAX-ACCESS read-only read-create
STATUS current
DESCRIPTION
"ippmNetMeasureMetrics defines the metrics to compute within this
measure. Only network metrics of the same type are allowed in
this
"
Multi-burst mode: This field (e.g. poisson-based metrics and periodic-based metrics
are incompatibles, while one-way delay and packet loss are
generally processed simultaneously: a very bad delay is
potentially a very good packet loss).

Results are saved in indicates the ippmHistoryTable. Results of a metric
are identified using an index gap between 2
bursts, in number of type IppmMetricsRegistryIndex. packets.
Example:
Given a multi-metrics measure of One-way-Delay(6)
If TxPacketRateUnit/TxPacketRate is 100 packets/second,
and One-way-
Packet-Loss(12). The value of DevOrIntBurstSize equals 50 packets, then the field ippmNetMeasureMetrics gap between
2 bursts is
'0001000001000000'b, '1040'B. Results are logged in equal to 50*1/100, or 1/2 second.

Poisson mode:
This field indicates the
ippmHistoryTable where One-way-Delay singletons have a value of
ippmMetricsIndex of 6 while One-way-Packet-Loss singletons have a
value of ippmMetricsIndex typical difference between the
packets of 12. the period corresponding to the median.

"
::= { ippmNetMeasureEntry 4 21 }

ippmNetMeasureBeginTime

ippmNetMeasureLossTimeout OBJECT-TYPE
SYNTAX GMTTimeStamp Unsigned32
UNITS "Milliseconds"
MAX-ACCESS read-only read-create
STATUS current
DESCRIPTION
"Specifies the time at delay after which the measurement begins." packet is considered
lost by the sink."
::= { ippmNetMeasureEntry 5 22 }

ippmNetMeasureCollectionRateUnit

ippmNetMeasureL3PacketSize OBJECT-TYPE
SYNTAX TimeUnit Unsigned32
UNITS "Bytes"
MAX-ACCESS read-only read-create
STATUS current
DESCRIPTION
"Specifies the unit size of the measurement period." packets counted at the IP network
layer in regards to the PacketType definition.
Example: For a PacketType 'ip ipip4' the L3 size will be the
size of the packet at ipip4 level.
"
::= { ippmNetMeasureEntry 6 23 }

ippmNetMeasureCollectionRate

ippmNetMeasureDataPattern OBJECT-TYPE

SYNTAX Unsigned32 OCTET STRING
MAX-ACCESS read-only read-create
STATUS current
DESCRIPTION
"Gives the period
"The pattern used to collect singletons from fill the point payload of
measures. This value is used as the cycle period in the report." packet."

::= { ippmNetMeasureEntry 7 24 }

ippmNetMeasureDurationUnit

ippmNetMeasureTotalPktsRecv OBJECT-TYPE
SYNTAX TimeUnit Counter64
UNITS "Packets"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Specifies
"Reports the measurement duration unit."
::= { ippmNetMeasureEntry 8 }

ippmNetMeasureDuration OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Specifies number of packets received since the measurement duration."
beginning of the measure.
This parameters is useful to monitor the measure and it is
needed to compute statistics."
::= { ippmNetMeasureEntry 9 25 }

ippmNetMeasureHistorySize

ippmNetMeasureLastUpdate OBJECT-TYPE
SYNTAX Unsigned32 GMTTimeStamp
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Specifies the maximum number of results saved for each metric of
this measure.
Overflow condition will be managed by
"The time when the object
ippmNetMeasureResultsMgmt. " last aggregation was computed."
::= { ippmNetMeasureEntry 10 26 }

ippmNetMeasureFailureMgmtMode

ippmNetMeasureOperState OBJECT-TYPE
SYNTAX INTEGER {
auto(1),
manual(2),
discarded(3)
unknown(0),
running(1),
stopped(2)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object defines whether this row (and the measure controlled
by this row) is restarted automatically, manually, or discarded
upon failure, or reboot of the measurement system.
'auto'
The measure is restarted automatically.
'manual'
The measure has to be restarted manually.
'discarded'
The measure and it results are discarded.
"
"Reports the operational status of the network measure."
::= { ippmNetMeasureEntry 11 27 }

ippmNetMeasureResultsMgmt

--
--
-- ippmAggrMeasure Group
--
--

--
-- ippmAggrMeasureTable
--
--

ippmAggrMeasureTable OBJECT-TYPE
SYNTAX INTEGER {
wrap(1),
suspend(2)
} SEQUENCE OF IppmAggrMeasureEntry
MAX-ACCESS read-only not-accessible
STATUS current
DESCRIPTION
"
Action to take when
"An aggregated measure summarizes the log is full. results of previous
network or aggregated measures. The measurement system owner
may choose to either wrap, results are saved in which case the agent writes over
existing records. The user may choose to suspend writing to
ippmHistoryTable.
Each step of the
log in calculation for the event that he wishes to archive measure produces a
singleton result per metric."
::= { ippmAggrMeasure 1 }

ippmAggrMeasureEntry OBJECT-TYPE
SYNTAX IppmAggrMeasureEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Typically, the data. The resume
action causes configuration operation creates and sets the agent to begin to write in
value of the log, fields of a new ippmAggrMeasureEntry.
ippmAggrMeasureOwner and assumes ippmAggrMeasureIndex identify the data has been cleared.
This object indicates
instance created.
The field ippmAggrMeasureMetrics identifies the way metric to
compute. As such its ippmMetricsType should be 'aggregated'.

The measure aggregates the measurement results are managed
when the owner quota has been exceeded:
'wrap'
continue the measurement of a measure identified by
ippmAggrMeasureHistoryOwner, ippmAggrMeasureHistoryIndex and erase the older entries in the
history.
'suspend'
stop the
ippmAggrMeasureHistoryMetric. The measure to aggregate belongs
to ippmNetMeasureTable or ippmAggrMeasureTable.

The aggregation starts at ippmAggrMeasureBeginTime and keep the results ends
after ippmAggrMeasureDuration.

An aggregated result is computed for each
ippmMeasureCollectionRate tick and saved in the history.
"
ippmHistoryTable."
INDEX { ippmAggrMeasureOwner, ippmAggrMeasureIndex }
::= { ippmNetMeasureEntry 12 ippmAggrMeasureTable 1 }

IppmAggrMeasureEntry ::= SEQUENCE {
ippmAggrMeasureOwner IppmOwnerString,
ippmAggrMeasureIndex IppmOwnerIndex,
ippmAggrMeasureName SnmpAdminString,
ippmAggrMeasureMetrics IppmStandardMetrics,
ippmAggrMeasureHistoryOwner IppmOwnerString,
ippmAggrMeasureHistoryIndex IppmOwnerIndex,
ippmAggrMeasureHistoryMetric IppmMetricsRegistryIndex,
ippmAggrMeasureFilter IppmMetricResultFilter,
ippmAggrMeasureLowThreshold Unsigned32,
ippmAggrMeasureHighThreshold Unsigned32,
ippmAggrMeasureBeginTime GMTTimeStamp,
ippmAggrMeasureAggrPeriodUnit TimeUnit,
ippmAggrMeasureAggrPeriod Unsigned32,
ippmAggrMeasureDurationUnit TimeUnit,
ippmAggrMeasureDuration Unsigned32,
ippmAggrMeasureHistorySize Unsigned32,
ippmAggrMeasureStorageType StorageType,
ippmAggrMeasureAdminState INTEGER,
ippmAggrMeasureFastReport OBJECT IDENTIFIER,
ippmAggrMeasureResultsMgmt INTEGER,
ippmAggrMeasureLastUpdate GMTTimeStamp,
ippmAggrMeasureOperState INTEGER,
ippmAggrMeasureNbPktsTreated Counter64,
ippmAggrMeasureStatus RowStatus
}

ippmNetMeasureSrcPacketType

ippmAggrMeasureOwner OBJECT-TYPE
SYNTAX PacketType IppmOwnerString
MAX-ACCESS read-only not-accessible
STATUS current
DESCRIPTION
"Defines the type P of the source address of the packets sent by
the measure."
"The owner who has configured this entry."
::= { ippmNetMeasureEntry 13 ippmAggrMeasureEntry 1 }

ippmNetMeasureSrc

ippmAggrMeasureIndex OBJECT-TYPE
SYNTAX PacketTypeAddress IppmOwnerIndex
MAX-ACCESS read-only not-accessible
STATUS current
DESCRIPTION
"Specifies the address of the source
"The index of the aggregated measure.
It The value is represented as a list of parameters corresponding to those
of managed by
the PROTOCOL IDENTIFIER set in ippmNetMeasureSrcPacketType." owner."
::= { ippmNetMeasureEntry 14}

ippmNetMeasureDstPacketType ippmAggrMeasureEntry 2 }

ippmAggrMeasureName OBJECT-TYPE
SYNTAX PacketType SnmpAdminString
MAX-ACCESS read-only read-create
STATUS current
DESCRIPTION
"Defines
"The name of the type P instance of the destination address metric. It illustrates the
specificity of the packets
sent by metric and includes the measure." metric and the
typeP.

example: IP-port-HTTP-connectivity: free text."
::= { ippmNetMeasureEntry 15 ippmAggrMeasureEntry 3 }

ippmNetMeasureDst

ippmAggrMeasureMetrics OBJECT-TYPE
SYNTAX PacketTypeAddress IppmStandardMetrics

MAX-ACCESS read-only read-create
STATUS current
DESCRIPTION
"Specifies
"ippmAggrMeasureMetrics defines the address metrics to compute within
this aggregated measure.

Only aggregated metrics of the destination same type are allowed in this
field (e.g. Measurement of minimum, average and maximum
metrics are generally processed simultaneously on the same
network measure).

Results are saved in the ippmHistoryTable.

Results of a metric are identified using an index of type
IppmMetricsRegistryIndex.

Example:
Given a multi-aggregation of One-way-Delay-Median(9) and
One-way-Delay-Minimum(10). The value of the field
ippmAggrMeasureMetrics is '0000011000000000'b, '0600'B.

Results are logged in the ippmHistoryTable where
One-way-Delay-Median singletons have a value of
ippmMetricsIndex of 9 while One-way-Delay-Minimum singletons
have a value of ippmMetricsIndex of the measure. 10.

NOTE WELL: It is represented as a list of parameters corresponding not recommended to those
of use the PROTOCOL IDENTIFIER set multi aggregation
capability in ippmNetMeasureDstPacketType." conjunction with the filter feature.
"
::= { ippmNetMeasureEntry 16 ippmAggrMeasureEntry 4 }

ippmNetMeasureTxMode

ippmAggrMeasureHistoryOwner OBJECT-TYPE
SYNTAX INTEGER {
other(0),
periodic(1),
poisson(2),
multiburst(3)
} IppmOwnerString
MAX-ACCESS read-only read-create
STATUS current
DESCRIPTION
"The transmit mode used to send the packets:
'other'
The rule used to send the packets is unknown.
'periodic'
Packets are sent periodically at ippmNetMeasureTxPacketRate
rate.
'poisson'
Packets are sent using a Poisson law, the median is the value
of ippmNetMeasureDevOrIntBurstSize, the deviation is
ippmNetMeasureMedOrBurstSize.
'multiburst'
Packets are sent bursty at ippmNetMeasureTxPacketRate. The
size of the burst is made owner of ippmNetMeasureMedOrBurstSize
packets.
Between 2 consecutive bursts, transmission stops during the time
needed measure to send ippmNetMeasureDevOrIntBurstSize. summarize. "
::= { ippmNetMeasureEntry 17 ippmAggrMeasureEntry 5 }

ippmNetMeasureTxPacketRateUnit

ippmAggrMeasureHistoryIndex OBJECT-TYPE
SYNTAX TimeUnit IppmOwnerIndex
MAX-ACCESS read-only read-create
STATUS current
DESCRIPTION
"The packet rate unit used to send owner index of the packets." measure to summarize. "
::= { ippmNetMeasureEntry 18 ippmAggrMeasureEntry 6 }

ippmNetMeasureTxPacketRate

ippmAggrMeasureHistoryMetric OBJECT-TYPE
SYNTAX Unsigned32
UNITS "Packets" IppmMetricsRegistryIndex
MAX-ACCESS read-only read-create
STATUS current
DESCRIPTION
"The rate metric of the packets are sent." measure to summarize. "
::= { ippmNetMeasureEntry 19 ippmAggrMeasureEntry 7 }

ippmNetMeasureMedOrBurstSize

ippmAggrMeasureFilter OBJECT-TYPE
SYNTAX Unsigned32
UNITS "Packets" IppmMetricResultFilter
MAX-ACCESS read-only read-create
STATUS current
DESCRIPTION
"
Multi-burst mode: This field represents the burst size in number
of packets.
Poisson mode: This field indicates
ippmAggrMeasureFilter defines the number kind of packets sent, filter to apply on
average, during each period corresponding a
result to determine if the median. result is stored or not. The median
parameters of the filter are ippmAggrMeasureLowThreshold and
ippmAggrMeasureHighThreshold.

Thresholds have the same unit as the metric value.

In the following examples we consider an aggregated measure.
Its low threshold is therefore
MedOrBurstSize*TxPacketRateUnit/TxPacketRate.

Example:
If TxPacketRateUnit/TxPacketRate set to 80.its high threshold is 100 packets/second, and if
MedOrBurstSize, the number set to
100. The aggregation produced a flow of packets sent during 12 aggregated results
{40 30 60 85 140 130 190 95 50 90 30 20}.

If the period
corresponding filter is set to 'logInBandValue' then the median results 85,
95, 90 will be stored.

If the filter is 50 packets, set to 'logOutBandValue' then the median equals
50*1/100 = 1/2 seconds.
"
::= { ippmNetMeasureEntry results 40
30 60 140 130 190 50 30 20 }

ippmNetMeasureDevOrIntBurstSize OBJECT-TYPE
SYNTAX Unsigned32
UNITS "Packets"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"
Multi-burst mode: This field indicates the gap between 2 bursts,
in number of packets.
Example: will be stored.

If TxPacketRateUnit/TxPacketRate is 100 packets/second,
and DevOrIntBurstSize equals 50 packets, then the gap between 2
bursts filter is
equal set to 50*1/100, or 1/2 second.

Poisson mode:
This field indicates the typical difference between 'logAboveValue' then the packets
of results 140
130 190 will be stored.

If the period corresponding filter is set to 'logBelowValue' then the median.

"
::= { ippmNetMeasureEntry 21 }

ippmNetMeasureLossTimeout OBJECT-TYPE
SYNTAX Unsigned32
UNITS "Milliseconds"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Specifies the delay after which results 40 30
60 50 30 20 will be stored.

If the packet filter is considered lost
by set to 'logUpAndDownValue' then the sink." results
40, 140, 50 will be stored."
::= { ippmNetMeasureEntry 22 ippmAggrMeasureEntry 8 }

ippmNetMeasureL3PacketSize

ippmAggrMeasureLowThreshold OBJECT-TYPE
SYNTAX Unsigned32
UNITS "Bytes"
MAX-ACCESS read-only read-create
STATUS current
DESCRIPTION
"Specifies
"An event is generated when the size result of the packets counted at measure of the IP network
layer in regards to
metric is lower that the PacketType definition.
Example: For a PacketType 'ip ipip4' value of ippmAggrMeasureLowThreshold.
The threshold has the L3 size will be same unit as the size metric. The metric unit
is recorded in the object ippmMetricsUnit of this metric entry
in the packet at ipip4 level. ippmMetricsTable.
"
::= { ippmNetMeasureEntry 23 ippmAggrMeasureEntry 9 }

ippmNetMeasureDataPattern

ippmAggrMeasureHighThreshold OBJECT-TYPE
SYNTAX OCTET STRING Unsigned32
MAX-ACCESS read-only read-create
STATUS current
DESCRIPTION
"The pattern used to fill
"An event is generated when the payload result of the packet."

::= { ippmNetMeasureEntry 24 }

ippmNetMeasureTotalPktsRecv OBJECT-TYPE
SYNTAX Counter64
UNITS "Packets"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Reports the current number measure of packets received since the
beginning
metric exceeds the value of ippmAggrMeasureHighThreshold.
The threshold has the measure.
This parameters is useful to monitor same unit as the measure and it metric. The metric unit
is needed
to compute statistics." recorded in the object ippmMetricsUnit of this metric entry
in the ippmMetricsTable.
"
::= { ippmNetMeasureEntry 25 ippmAggrMeasureEntry 10 }

ippmNetMeasureLastUpdate

ippmAggrMeasureBeginTime OBJECT-TYPE
SYNTAX GMTTimeStamp
MAX-ACCESS read-only read-create
STATUS current
DESCRIPTION
"The
"Specifies the time when at which the last aggregation was computed." aggregated measure starts."
::= { ippmNetMeasureEntry 26 ippmAggrMeasureEntry 11 }

ippmNetMeasureOperState

ippmAggrMeasureAggrPeriodUnit OBJECT-TYPE
SYNTAX INTEGER {
unknown(0),
running(1),
stopped(2)
} TimeUnit
MAX-ACCESS read-only read-create
STATUS current
DESCRIPTION
"Reports
"Specifies the operational status unit of the network measure." aggregated measure period."
DEFVAL { second }
::= { ippmNetMeasureEntry 27 ippmAggrMeasureEntry 12 }

--
--
-- ippmAggrMeasure Group
--
--

--
-- ippmAggrMeasureTable
--
--

ippmAggrMeasureTable

ippmAggrMeasureAggrPeriod OBJECT-TYPE
SYNTAX SEQUENCE OF IppmAggrMeasureEntry Unsigned32
MAX-ACCESS not-accessible read-create
STATUS current
DESCRIPTION
"An aggregated measure summarizes
"Specifies the results amount of previous network
or aggregated measures. time between 2 measurement action
intervals. The results are saved in action is specific to the
ippmHistoryTable.
Each step semantic of the calculation for the measure produces a singleton
result per metric."
::= { ippmAggrMeasure 1 }

ippmAggrMeasureEntry OBJECT-TYPE
SYNTAX IppmAggrMeasureEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Typically,
measure.

Network metrics:

The ippmNetMeasureClockPattern transforms the configuration operation creates flow of
periodical instants as a flow of unpredictable instants of
measurement packet emission.

As the source and sets the
value sink share the definition of the fields clock
of a new ippmAggrMeasureEntry.
ippmAggrMeasureOwner the measure, and ippmAggrMeasureIndex identify as the
instance created.
The field ippmAggrMeasureMetrics identifies sending timestamp is part of the metric
measurement packet, the sink has the information to
compute. As such its ippmMetricsType should be 'aggregated'.

The measure aggregates verify
that the results stream of a measure identified packets generated by
ippmAggrMeasureHistoryOwner, ippmAggrMeasureHistoryIndex and
ippmAggrMeasureHistoryMetric. the source respects
the clock law.

Aggregated metrics:

They are performed periodically on a sequence of results of
other measures. The measure to aggregate belongs period corresponds to
ippmNetMeasureTable or ippmAggrMeasureTable. the interval between
two successive computations of the metric. The aggregation starts at ippmAggrMeasureBeginTime and ends after
ippmAggrMeasureDuration.

An aggregated value of
ippmHistoryTimestamp result is of a aggregated metric computed for each
ippmMeasureCollectionRate tick and saved in
corresponds to the
ippmHistoryTable."
INDEX { ippmAggrMeasureOwner, ippmAggrMeasureIndex }
::= { ippmAggrMeasureTable 1 }

IppmAggrMeasureEntry ::= SEQUENCE value of the ippmHistoryTimestamp of the
last metric result of the sequence used to compute the
aggregated metric."
DEFVAL {
ippmAggrMeasureOwner IppmOwnerString,
ippmAggrMeasureIndex IppmOwnerIndex,
ippmAggrMeasureName SnmpAdminString,
ippmAggrMeasureMetrics IppmStandardMetrics,
ippmAggrMeasureHistoryOwner IppmOwnerString,
ippmAggrMeasureHistoryIndex IppmOwnerIndex,
ippmAggrMeasureHistoryMetric IppmMetricsRegistryIndex,
ippmAggrMeasureFilter IppmMetricResultFilter,
ippmAggrMeasureLowThreshold Unsigned32,
ippmAggrMeasureHighThreshold Unsigned32,
ippmAggrMeasureBeginTime GMTTimeStamp,
ippmAggrMeasureAggrPeriodUnit TimeUnit,
ippmAggrMeasureAggrPeriod Unsigned32,
ippmAggrMeasureDurationUnit TimeUnit,
ippmAggrMeasureDuration Unsigned32,
ippmAggrMeasureHistorySize Unsigned32,
ippmAggrMeasureStorageType StorageType,
ippmAggrMeasureAdminState INTEGER,
ippmAggrMeasureFastReport OBJECT IDENTIFIER,
ippmAggrMeasureResultsMgmt INTEGER,
ippmAggrMeasureLastUpdate GMTTimeStamp,
ippmAggrMeasureOperState INTEGER,
ippmAggrMeasureNbPktsTreated Counter64,
ippmAggrMeasureStatus RowStatus 60 }

ippmAggrMeasureOwner OBJECT-TYPE
SYNTAX IppmOwnerString
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The owner who has configured this entry."

::= { ippmAggrMeasureEntry 1 13 }

ippmAggrMeasureIndex

ippmAggrMeasureDurationUnit OBJECT-TYPE
SYNTAX IppmOwnerIndex TimeUnit
MAX-ACCESS not-accessible read-create
STATUS current
DESCRIPTION
"The index of
"Specifies the aggregated measure. The value is managed by unit of the
owner." measure duration."
DEFVAL { second }
::= { ippmAggrMeasureEntry 2 14 }

ippmAggrMeasureName

ippmAggrMeasureDuration OBJECT-TYPE
SYNTAX SnmpAdminString Unsigned32
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The name of the instance of the metric. It illustrates
"Specifies the
specificity duration of the metric and includes the metric and the typeP.

example: IP-port-HTTP-connectivity: free text." measure."
DEFVAL { 120 }
::= { ippmAggrMeasureEntry 3 15 }

ippmAggrMeasureMetrics

ippmAggrMeasureHistorySize OBJECT-TYPE
SYNTAX IppmStandardMetrics Unsigned32
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"ippmAggrMeasureMetrics defines the metrics to compute within
this aggregated measure.

Only aggregated metrics of
"Specifies the same type are allowed in this
field (e.g. Measurement of minimum, average and maximum metrics
are generally processed simultaneously on the same network
measure).

Results are saved in the ippmHistoryTable. Results number of a results saved for each metric
are identified using an index of type IppmMetricsRegistryIndex.

Example:
Given a multi-aggregation of One-way-Delay-Median(9) and One-way-
Delay-Minimum(10). The value of the field ippmAggrMeasureMetrics
is '0000011000000000'b, '0600'B. Results are logged in the
ippmHistoryTable where One-way-Delay-Median singletons have a
value of ippmMetricsIndex of 9 while One-way-Delay-Minimum
singletons have a value
of ippmMetricsIndex of 10.

NOTE WELL: It is not recommended to use the multi aggregation
capability in conjunction with this measure. Overflow condition will be managed by the filter feature.
object ippmAggrMeasureResultsMgmt. "
DEFVAL { 2 }
::= { ippmAggrMeasureEntry 4 16 }

ippmAggrMeasureHistoryOwner

ippmAggrMeasureStorageType OBJECT-TYPE
SYNTAX IppmOwnerString StorageType
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The owner of
"This object defines whether this row and the measure to summarize. "
controlled by this row are kept in volatile storage and lost
upon reboot or if this row is backed up
by non-volatile or permanent storage.

Possible values are: other(1), volatile(2), nonVolatile(3),
permanent(4), readOnly(5)."
DEFVAL { nonVolatile }
::= { ippmAggrMeasureEntry 5 17 }

ippmAggrMeasureHistoryIndex

ippmAggrMeasureResultsMgmt OBJECT-TYPE
SYNTAX IppmOwnerIndex INTEGER {
wrap(1),
suspend(2)
}
MAX-ACCESS read-create read-only
STATUS current
DESCRIPTION
"The owner index
"This object displays the way the history of the aggregated
measure to summarize. is managed.
'wrap'
continue the measure and erase the older entries in the
history.
'suspend'
stop the measure and keep the results in the history.
"
DEFVAL { wrap }
::= { ippmAggrMeasureEntry 6 18 }

ippmAggrMeasureHistoryMetric

ippmAggrMeasureAdminState OBJECT-TYPE
SYNTAX IppmMetricsRegistryIndex INTEGER {
start(0),
stop(1)
}
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The metric
"This object controls the activity of the aggregated measure.
'start'
The aggregated measure to summarize. " is started.
'stop'
The aggregated measure is stopped."
DEFVAL { start }
::= { ippmAggrMeasureEntry 7 19 }

ippmAggrMeasureFilter

ippmAggrMeasureFastReport OBJECT-TYPE
SYNTAX IppmMetricResultFilter OBJECT IDENTIFIER
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"
ippmAggrMeasureFilter defines the kind of filter
"A fast report is required in order to apply on verify quickly that a
result to determine if the result
measure is stored or not. The
parameters of the filter are ippmAggrMeasureLowThreshold and
ippmAggrMeasureHighThreshold.

Thresholds have the same unit as the metric value.

In the following examples we consider an aggregated measure. Its
low threshold running well.
'fast report' feature is set to 80.its high threshold active if ippmAggrMeasureFastReport
is set not null and points to 100. The
aggregation produced a flow notification.
A fast report consists of 12 aggregated results {40 30 60 85
140 130 190 95 50 90 30 20}.

If the filter is set sending by email to 'logInBandValue' then the results 85, 95,
90 will be stored.

If owner of the filter is set to 'logOutBandValue' then
measure, a table of the results 40 30
60 140 130 190 50 30 20 will be stored.

If of all the filter metrics computed by
this aggregated measure. The owner email address is set to 'logAboveValue' then read from
the ippmOwnersTable.

ippmAggrMeasureFastReport identifies the results 140 130
190 will be stored.

If notification which
defines the filter is set to 'logBelowValue' then header of the report.

The results 40 30 60
50 30 20 will be stored.

If part of the filter report is set to 'logUpAndDownValue' then the made of a column of results 40,
140, 50 will be stored."
per metrics. Results are separated using commas.

To avoid disaster, an aggregated measure using a fast report
must have a cycle of aggregation greater than or equal to 1
second and should not sent more than an email every 5 minutes
and should not sent more than 12 emails."
DEFVAL { zeroDotZero }
::= { ippmAggrMeasureEntry 8 20 }

ippmAggrMeasureLowThreshold

ippmAggrMeasureLastUpdate OBJECT-TYPE
SYNTAX Unsigned32 GMTTimeStamp
MAX-ACCESS read-create read-only
STATUS current
DESCRIPTION
"An event is generated
"The time when the result of the last aggregated measure of the
metric is lower that the value of ippmAggrMeasureLowThreshold.
The threshold has the same unit as the metric. The metric unit is
recorded in the object ippmMetricsUnit of this metric entry in
the ippmMetricsTable.
" was computed."
::= { ippmAggrMeasureEntry 9 21 }

ippmAggrMeasureHighThreshold

ippmAggrMeasureOperState OBJECT-TYPE
SYNTAX Unsigned32 INTEGER {
unknown(0),
running(1),
stopped(2)
}
MAX-ACCESS read-create read-only
STATUS current
DESCRIPTION
"An event is generated when the result of the measure of the
metric exceeds the value of ippmAggrMeasureHighThreshold.
The threshold has the same unit as the metric. The metric unit is
recorded in
"Reports the object ippmMetricsUnit operational status of this metric entry in the ippmMetricsTable.
" aggregated measure."
::= { ippmAggrMeasureEntry 10 22 }

ippmAggrMeasureBeginTime

ippmAggrMeasureNbPktsTreated OBJECT-TYPE
SYNTAX GMTTimeStamp Counter64
UNITS "Packets"
MAX-ACCESS read-create read-only
STATUS current
DESCRIPTION
"Specifies
"Reports the time at which current number of packets used to calculate the
aggregation since the start of the measure.

This parameters is useful to monitor the aggregated measure starts." and it is
needed to compute statistics."
::= { ippmAggrMeasureEntry 11 23 }

ippmAggrMeasureAggrPeriodUnit

ippmAggrMeasureStatus OBJECT-TYPE
SYNTAX TimeUnit RowStatus
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Specifies the unit
"The status of this entry. Once the aggregated measure period."
DEFVAL { second } entry status is set to
active, the associate entry cannot be modified.
"
::= { ippmAggrMeasureEntry 12 24 }

--
-- IPPM Notifications
--

ippmAggrMeasureReport NOTIFICATION-TYPE
OBJECTS {
ippmAggrMeasureFilter,
ippmAggrMeasureLowThreshold,
ippmAggrMeasureHighThreshold,
ippmMetricsType,
ippmMetricsUnit,
ippmMetricsDescription,
ippmHistoryTimestamp,
ippmHistoryValue,
ippmHistoryPathToResults
}

ippmAggrMeasureAggrPeriod OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Specifies
"A notification sent because the amount value of time between 2 measurement action
intervals. The action the measure is specific to under
the semantic of high threshold value and greater than the measure.

Network metrics: low threshold
value.
The ippmNetMeasureClockPattern transforms notification contains the flow of periodical
instants as a flow of unpredictable instants instances of measurement
packet emission.

As the source and
ippmHistoryValue object that exceeded the sink share threshold.
The notification contains the definition instances of the clock of
ippmHistoryTimestamp identifying the measure, and as time the sending timestamp event occurred.
ippmHistoryPathToResults is part of the
measurement packet, the sink has a link to the information file name, which
contains detailed results corresponding to verify that this event."
::= { ippmNotifications 1 }

ippmAggrMeasureHistoryFull NOTIFICATION-TYPE
OBJECTS {
ippmAggrMeasureName,

ippmAggrMeasureHistorySize,
ippmMetricsType,
ippmMetricsUnit,
ippmMetricsDescription,
ippmHistoryTimestamp,
ippmHistoryValue

}
STATUS current
DESCRIPTION
"A notification sent when the stream size of packets generated by the source respects the clock
law.

Aggregated metrics:

They are performed periodically on a sequence history of results a metric
of other
measures. a aggregated measure exceeds ippmAggrMeasureHistorySize.
The period corresponds agent will then manage the reports according to the interval between two
successive computations policy
described in ippmAggrMeasureResultsMgmt."
::= { ippmNotifications 2 }

ippmNetMeasureHistoryFull NOTIFICATION-TYPE
OBJECTS {
ippmNetMeasureName,
ippmNetMeasureHistorySize,
ippmMetricsType,
ippmMetricsUnit,
ippmMetricsDescription,
ippmHistoryTimestamp,
ippmHistoryValue
}
STATUS current
DESCRIPTION
"A notification sent when the size of the metric. The value of
ippmHistoryTimestamp result history of a aggregated metric computed
corresponds to the value of the ippmHistoryTimestamp
of a network measure exceeded ippmNetMeasureHistorySize. Then
the last
metric result of agent manages the sequence used records according to compute the aggregated
metric."
DEFVAL { 60 } policy
described in ippmNetMeasureResultsMgmt."
::= { ippmAggrMeasureEntry 13 ippmNotifications 3 }

ippmAggrMeasureDurationUnit OBJECT-TYPE
SYNTAX TimeUnit
MAX-ACCESS read-create

--
-- IPPM MIB Conformance statements
--

ippmCompliances OBJECT IDENTIFIER ::={ ippmConformance 1 }

ippmGroups OBJECT IDENTIFIER ::={ ippmConformance 2 }

ippmProxyInterDomainCompliances MODULE-COMPLIANCE
STATUS current
DESCRIPTION
"Specifies
"The compliance statement for SNMP entities which implement
the unit IPPM MIB as a proxy in interdomain. The implementation of
the measure duration."
DEFVAL { second }
::= VACM control is mandatory."
MODULE -- this module
MANDATORY-GROUPS { ippmAggrMeasureEntry 14

ippmSystemGroup, ippmHistoryGroup, ippmNetMeasureGroup,
ippmAggrMeasureGroup, ippmNotificationGroup
}

ippmAggrMeasureDuration OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS read-create
STATUS current

OBJECT ippmNetMeasureName
MIN-ACCESS read-only
DESCRIPTION
"In Proxy mode network measures may be managed using another
interface than SNMP."

OBJECT ippmNetMeasureMetrics
MIN-ACCESS read-only
DESCRIPTION
"In Proxy mode network measures may be managed using another
interface than SNMP."

OBJECT ippmNetMeasureBeginTime
MIN-ACCESS read-only
DESCRIPTION
"In Proxy mode network measures may be managed using another
interface than SNMP."

OBJECT ippmNetMeasureCollectionRateUnit
MIN-ACCESS read-only
DESCRIPTION
"In Proxy mode network measures may be managed using another
interface than SNMP."

OBJECT ippmNetMeasureCollectionRate
MIN-ACCESS read-only
DESCRIPTION
"In Proxy mode network measures may be managed using another
interface than SNMP."

OBJECT ippmNetMeasureDurationUnit
MIN-ACCESS read-only
DESCRIPTION
"In Proxy mode network measures may be managed using another
interface than SNMP."

OBJECT ippmNetMeasureDuration
MIN-ACCESS read-only
DESCRIPTION
"In Proxy mode network measures may be managed using another
interface than SNMP."

OBJECT ippmNetMeasureHistorySize
MIN-ACCESS read-only
DESCRIPTION
"In Proxy mode network measures may be managed using another
interface than SNMP."

OBJECT ippmNetMeasureFailureMgmtMode
MIN-ACCESS read-only
DESCRIPTION
"Specifies the duration of the measure."
DEFVAL { 120 }
::= { ippmAggrMeasureEntry 15 }

ippmAggrMeasureHistorySize OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS read-create
STATUS current
"In Proxy mode network measures may be managed using another
interface than SNMP."

OBJECT ippmNetMeasureResultsMgmt
MIN-ACCESS read-only
DESCRIPTION
"Specifies the maximum number of results saved for each metric of
this measure. Overflow condition will
"In Proxy mode network measures may be managed by the object
ippmAggrMeasureResultsMgmt. "
DEFVAL { 2 }
::= { ippmAggrMeasureEntry 16 }

ippmAggrMeasureStorageType OBJECT-TYPE
SYNTAX StorageType
MAX-ACCESS read-create
STATUS current using another
interface than SNMP."

OBJECT ippmNetMeasureSrcPacketType
MIN-ACCESS read-only
DESCRIPTION
"This object defines whether this row and the measure controlled
by this row are kept in volatile storage and lost upon reboot or
if this row is backed up
by non-volatile or permanent storage.

Possible values are: other(1), volatile(2), nonVolatile(3),
permanent(4), readOnly(5)."
DEFVAL { nonVolatile }
::= { ippmAggrMeasureEntry 17 }

ippmAggrMeasureResultsMgmt OBJECT-TYPE
SYNTAX INTEGER {
wrap(1),
suspend(2)
}
MAX-ACCESS
"In Proxy mode network measures may be managed using another
interface than SNMP."

OBJECT ippmNetMeasureSrc
MIN-ACCESS read-only
STATUS current
DESCRIPTION
"This object displays the way the history of the aggregated
measure is managed.
'wrap'
continue the measure and erase the older entries in the
history.
'suspend'
stop the measure and keep the results in the history.
"
DEFVAL { wrap }
::= { ippmAggrMeasureEntry 18 }

ippmAggrMeasureAdminState OBJECT-TYPE
SYNTAX INTEGER {
start(0),
stop(1)
}
MAX-ACCESS read-create
STATUS current
"In Proxy mode network measures may be managed using another
interface than SNMP."

OBJECT ippmNetMeasureDstPacketType
MIN-ACCESS read-only
DESCRIPTION
"In Proxy mode network measures may be managed using another
interface than SNMP."

OBJECT ippmNetMeasureDst
MIN-ACCESS read-only
DESCRIPTION
"This object controls the activity of the aggregated measure.
'start'
The aggregated measure is started.
'stop'
The aggregated measure is stopped."
DEFVAL { start }

::= { ippmAggrMeasureEntry 19 }

ippmAggrMeasureFastReport OBJECT-TYPE
SYNTAX
"In Proxy mode network measures may be managed using another
interface than SNMP."

OBJECT IDENTIFIER
MAX-ACCESS read-create
STATUS current ippmNetMeasureTxMode
MIN-ACCESS read-only
DESCRIPTION
"A fast report is required in order to verify quickly that a
measure is running well.

The feature 'fast report' is active if ippmAggrMeasureFastReport
is not null and points to a notification.
A fast report consists of sending by email to the owner of the
measure, a table of the results of all the metrics computed by
this aggregated measure. The owner email address is read from the
ippmOwnersTable.

ippmAggrMeasureFastReport identifies the notification which
defines the header of the report.

The results part of the report is made of a column of results per
metrics. Results are separated
"In Proxy mode network measures may be managed using commas.

To avoid disaster, an aggregated measure another
interface than SNMP."

OBJECT ippmNetMeasureTxPacketRateUnit
MIN-ACCESS read-only
DESCRIPTION
"In Proxy mode network measures may be managed using a fast report must
have a cycle of aggregation greater another
interface than or equal to 1 second and
should not sent more SNMP."

OBJECT ippmNetMeasureTxPacketRate
MIN-ACCESS read-only
DESCRIPTION
"In Proxy mode network measures may be managed using another
interface than SNMP."

OBJECT ippmNetMeasureMedOrBurstSize
MIN-ACCESS read-only
DESCRIPTION
"In Proxy mode network measures may be managed using another
interface than SNMP."

OBJECT ippmNetMeasureDevOrIntBurstSize
MIN-ACCESS read-only
DESCRIPTION
"In Proxy mode network measures may be managed using another
interface than SNMP."

OBJECT ippmNetMeasureLossTimeout
MIN-ACCESS read-only
DESCRIPTION
"In Proxy mode network measures may be managed using another
interface than an email every 5 minutes and should not
sent more SNMP."

OBJECT ippmNetMeasureL3PacketSize
MIN-ACCESS read-only
DESCRIPTION
"In Proxy mode network measures may be managed using another
interface than 12 emails."
DEFVAL { zeroDotZero } SNMP."

OBJECT ippmNetMeasureDataPattern
MIN-ACCESS read-only
DESCRIPTION
"In Proxy mode network measures may be managed using another
interface than SNMP."

::= { ippmAggrMeasureEntry 20 ippmCompliances 1 }

ippmAggrMeasureLastUpdate OBJECT-TYPE
SYNTAX GMTTimeStamp
MAX-ACCESS read-only

ippmProxyCompliance MODULE-COMPLIANCE
STATUS current
DESCRIPTION
"The time when compliance statement for SNMP entities which implement
the last aggregated measure was computed."
::= { ippmAggrMeasureEntry 21 }

ippmAggrMeasureOperState OBJECT-TYPE
SYNTAX INTEGER IPPM MIB as a proxy."
MODULE -- this module
MANDATORY-GROUPS {
unknown(0),
running(1),
stopped(2)
ippmSystemGroup, ippmOwnersGroup, ippmHistoryGroup,
ippmNetMeasureGroup, ippmAggrMeasureGroup,
ippmNotificationGroup
}
MAX-ACCESS
GROUP ippmOwnersGroup
DESCRIPTION
"The ippmOwnersGroup is manadatory if VACM is not
implemented."