draft-ietf-ippm-reporting-mib-02.txt   draft-ietf-ippm-reporting-mib-03.txt 
Network Working Group E. Stephan/J. Jewitt Network Working Group E. Stephan/J. Jewitt
Internet Draft France Telecom R&D Internet Draft France Telecom R&D
Document: draft-ietf-ippm-reporting-mib-02.txt March 1st, 2003 Document: draft-ietf-ippm-reporting-mib-03.txt June, 2003
IPPM reporting MIB IPPM reporting MIB
Status of this Memo Status of this Memo
This document is an Internet-Draft and is in full conformance with This document is an Internet-Draft and is in full conformance with
all provisions of Section 10 of RFC2026 [1]. all provisions of Section 10 of RFC2026 [1].
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that other Task Force (IETF), its areas, and its working groups. Note that other
skipping to change at page 2, line 7 skipping to change at page 2, line 7
This memo defines a portion of the Management Information Base (MIB) This memo defines a portion of the Management Information Base (MIB)
designed for use with network management protocols in TCP/IP-based designed for use with network management protocols in TCP/IP-based
internets. internets.
In particular, this MIB specifies the objects used for managing the In particular, this MIB specifies the objects used for managing the
results of the IPPM metrics measures, for pushing alarms, and for results of the IPPM metrics measures, for pushing alarms, and for
reporting the measures results. reporting the measures results.
Table of Contents Table of Contents
1. Introduction................................................3 1. Introduction................................................2
2. The IPPM Framework..........................................3 2. The IPPM Framework..........................................3
3. The SNMP Management Framework...............................3 3. The SNMP Management Framework...............................3
4. Overview....................................................5 4. Overview....................................................5
4.1. Textual Conventions.........................................6 4.1. Textual Conventions.........................................6
4.2. Structure of the MIB........................................8 4.2 Structure of the MIB.........................................8
4.3. Row identification in an application namespace.............10 4.3 Row identification in an application namespace..............10
4.4. Relationship of IPPM MIB tables............................11 4.4 Relationship of IPPM REPORTING MIB tables...................11
5. IPPM-REPORTING-MIB conceptual presentation.................15 5 Measurement architectures...................................12
5.1. IPPM-REPORTING-MIB diagram.................................15 5.1 Proxy architecture..........................................12
5.2. Conceptual programming interface...........................16 5.2 Reporting architecture......................................13
5.3. SNMP mapping...............................................16 5.3 Gateway architecture........................................15
6. Measurement architectures..................................17 5.4 Security....................................................15
6.1. Proxy architecture.........................................17 6 Reporting mode integration..................................16
6.2. Reporting architecture.....................................18 6.1 Integration.................................................16
6.3. Gateway architecture.......................................20 6.2 Setup of the measure network................................16
6.4. Security...................................................20 6.3 Setup of a measurement report...............................16
7. Reporting mode integration.................................21 6.4 Updating the history of the MIB.............................17
7.1. Integration................................................21 6.5 Report download and upload..................................17
7.2. Setup of the measure.......................................21 6.6 Default value...............................................17
7.3. Setup of the measurement report............................22 7 Definition..................................................17
7.4. Writing the results in the IPPM-REPORTING-MIB..............22 8 Security Considerations.....................................71
7.5. Report download and upload.................................23 8.1 VACM Access control.........................................71
7.6. Default value..............................................23 8.2 Privacy.....................................................74
8. Definition.................................................24 8.3 Measurement aspects.........................................74
9. Security Considerations....................................67 8.4 Management aspects..........................................75
9.1. Privacy....................................................67 9 Document management.........................................75
9.2. Measurement aspects........................................67 9.1 Open issues.................................................76
9.3. Management aspects.........................................68 9.2 Changes done since release 02...............................76
10. Document management........................................69 10 References..................................................77
10.1. Open issues.................................................69 11 Acknowledgments.............................................78
10.2. changes since release 00....................................69 12 Authors Addresses...........................................78
10.3. Changes since release 01....................................70
11. References.................................................72
12. Acknowledgments............................................73
13. Authors Addresses..........................................73
1. Introduction 1. Introduction
This memo defines a MIB for managing measures based upon the IP This memo defines a MIB for managing network measurements based upon
performance metrics specified by the IPPM Working Group. the IP performance metrics specified by the IPPM Working Group.
The definition of objects in the IPPM MIB are built on notions The definition of objects in the IPPM MIB are built on notions
introduced and discussed in the IPPM Framework document, RFC 2330 introduced and discussed in the IPPM Framework document, RFC 2330
[ii]. [ii].
This memo defines a Management Information Base (MIB), and as such it This memo defines a Management Information Base (MIB), and as such it
is intended to be respectful of the "Boilerplate for IETF MIBs" is intended to be respectful of the "Boilerplate for IETF MIBs"
defined in http://www.ops.ietf.org/mib-boilerplate.html. defined in http://www.ops.ietf.org/mib-boilerplate.html.
There are companion documents to the IPPM-REPORTING-MIB both in the There are companion documents to the IPPM-REPORTING-MIB both in the
skipping to change at page 3, line 41 skipping to change at page 3, line 25
for IPPM, RFC 2680 [v]; The Round-trip Delay Metric for IPPM, RFC for IPPM, RFC 2680 [v]; The Round-trip Delay Metric for IPPM, RFC
2681 [vi]. 2681 [vi].
Emerging metrics that are being specified in respect of this Emerging metrics that are being specified in respect of this
framework. framework.
3. The SNMP Management Framework 3. The SNMP Management Framework
The SNMP Management Framework consists of five major components: The SNMP Management Framework consists of five major components:
An overall architecture, described in RFC 2571 [6]. An overall architecture, described in RFC 2571 [2].
Mechanisms for describing and naming objects and events for the Mechanisms for describing and naming objects and events for the
purpose of management. The first version of this Structure of purpose of management. The first version of this Structure of
Management Information (SMI) is called SMIv1 and described in STD 16, Management Information (SMI) is called SMIv1 and described in STD 16,
RFC 1155 [7], STD 16, RFC 1212 [8] and RFC 1215 [9]. The second RFC 1155 [3], STD 16, RFC 1212 [4] and RFC 1215 [5]. The second
version, called SMIv2, is described in STD 58, RFC 2578 [10], STD 58, version, called SMIv2, is described in STD 58, RFC 2578 [6], STD 58,
RFC 2579 [11] and STD 58, RFC 2580 [12]. RFC 2579 [7] and STD 58, RFC 2580 [8].
Message protocols for transferring management information. The Message protocols for transferring management information. The
first version of the SNMP message protocol is called SNMPv1 and first version of the SNMP message protocol is called SNMPv1 and
described in STD 15, RFC 1157 [13]. A second version of the SNMP described in STD 15, RFC 1157 [9]. A second version of the SNMP
message protocol, which is not an Internet standards track protocol, message protocol, which is not an Internet standards track protocol,
is called SNMPv2c and described in RFC 1901 [14] and RFC 1906 [15]. is called SNMPv2c and described in RFC 1901 [10] and RFC 1906 [11].
The third version of the message protocol is called SNMPv3 and The third version of the message protocol is called SNMPv3 and
described in RFC 1906 [15], RFC 2572 [16] and RFC 2574 [17]. described in RFC 1906 [11], RFC 2572 [12] and RFC 2574 [13].
Protocol operations for accessing management information. The Protocol operations for accessing management information. The
first set of protocol operations and associated PDU formats is first set of protocol operations and associated PDU formats is
described in STD 15, RFC 1157 [13]. A second set of protocol described in STD 15, RFC 1157 [9]. A second set of protocol
operations and associated PDU formats is described in RFC 1905 [18]. operations and associated PDU formats is described in RFC 1905 [14].
A set of fundamental applications described in RFC 2573 [19] and A set of fundamental applications described in RFC 2573 [15] and
the view-based access control mechanism described in RFC 2575 [20]. the view-based access control mechanism described in RFC 2575 [16].
A more detailed introduction to the current SNMP Management Framework A more detailed introduction to the current SNMP Management Framework
can be found in RFC 2570 [21]. can be found in RFC 2570 [17].
Managed objects are accessed via a virtual information store, termed Managed objects are accessed via a virtual information store, termed
the Management Information Base or MIB. Objects in the MIB are the Management Information Base or MIB. Objects in the MIB are
defined using the mechanisms defined in the SMI. defined using the mechanisms defined in the SMI.
This memo specifies a MIB module that is compliant to the SMIv2. A This memo specifies a MIB module that is compliant to the SMIv2. A
MIB conforming to the SMIv1 can be produced through the appropriate MIB conforming to the SMIv1 can be produced through the appropriate
translations. The resulting translated MIB must be semantically translations. The resulting translated MIB must be semantically
equivalent, except where objects or events are omitted because no equivalent, except where objects or events are omitted because no
translation is possible (use of Counter64). Some machine readable translation is possible (use of Counter64). Some machine readable
skipping to change at page 5, line 20 skipping to change at page 5, line 20
metrics. This memo defines a Management Information Base for managing metrics. This memo defines a Management Information Base for managing
the measurement of IPPM metrics. the measurement of IPPM metrics.
To permit metrics to be referenced by other MIBs and other protocols, To permit metrics to be referenced by other MIBs and other protocols,
the IPPM WG has defined a registry of the current metrics and a the IPPM WG has defined a registry of the current metrics and a
framework for the integration of future metrics in the [IPPM metrics framework for the integration of future metrics in the [IPPM metrics
registry]. registry].
As the specification of new metrics is a continuous process, this As the specification of new metrics is a continuous process, this
memo defines a framework for the integration of the future memo defines a framework for the integration of the future
standardized metrics. To address future needs specialized tables may standardized metrics.
be created, while augmenting the definition of the ippmMeasureTable.
The MIB architecture is inspired by the RMON model [xxiii],[xxiv] The MIB architecture is inspired by the RMON model [xxiii],[xxiv]
which specifies the MIB for the monitoring of a single point of which specifies the MIB for the monitoring of a single point of
measure. The IPPM-REPORTING-MIB differs from this model in that IPPM measure. The IPPM-REPORTING-MIB differs from this model in that IPPM
metrics measurement involves several points of measure and requires metrics measurement involves several points of measure and requires
common references for time and for measure identification. common references for time and for measure identification.
The IPPM-REPORTING-MIB introduces a framework where each application The IPPM-REPORTING-MIB introduces a framework where each application
identifies its measures in an owner namespace. Using the namespace identifies its measures in an owner namespace. The administrator may
framework, an application may grant other owners access to its grant access to a measure, or set of measures to another owner via
measurement results for aggregated metrics computation, reporting, or view based access control. As a result, one owner may compute
alarming. aggregated metrics on another owners network measures.
Different architectures may be used to perform metric measurements, Different architectures may be used to perform metric measurements,
using a control protocol and a test protocol. Different control using a control protocol and a test protocol. Different control
frameworks are suitable for performing measurements. The memo lists frameworks are suitable for performing measurements. The memo lists
them, while also looking for a way to integrate them with the IPPM- them, while also looking for a way to integrate them with the IPPM-
REPORTING-MIB. This section is for informational purposes only, and REPORTING-MIB. This section is for informational purposes only, and
is intended to help to specify the relationship among the test is intended to help to specify the relationship among the test
protocol, the control protocol and IPPM-REPORTING-MIB. protocol, the control protocol and the IPPM-REPORTING-MIB.
Special care has been taken to provide a reporting mode suitable for Special care has been taken to provide a reporting mode suitable for
control protocols and test protocols. It addresses the need to control protocols and test protocols. It addresses the need to
provide access to results for the applications. Moreover, it may be provide access to results for the applications. Moreover, it may be
used to reduce the number of control frameworks. used to reduce the number of control frameworks.
This MIB is intended to handle multiple concurrent sessions by SNMP This MIB is intended to handle multiple concurrent sessions by SNMP
applications. However, the SNMP requests are not necessarily to be applications. However, the SNMP requests are not necessarily to be
handled explicitly by the measurement devices, but can be sent to handled explicitly by the measurement devices, but can be sent to
middleware performing an aggregation function. This allows for middleware performing an aggregation function. This allows for
continuous collection of measurements and statistics computation. continuous collection of measurements and statistics computation.
4.1. Textual Conventions 4.1. Textual Conventions
Five types of data are introduced as a textual convention in this Seven types of data are introduced as textual conventions in this
document: TypeP, TypePaddress, GMTTimeStamp, IppmStandardMetrics and document: IppmOwnerString, TimeUnit,TypeP, TypePaddress,
IppmReportDefinition. GMTTimeStamp, IppmStandardMetrics and IppmReportDefinition.
4.1.1. TypeP and TypePaddress 4.1.1 IppmOwnerString
This octet string is used to represent the owners of the various
measures and reports in the measurement system.
4.1.2 TimeUnit
This textual convention is used to indicate a unit of time, ranging
from nanosecond, microsecond, millisecond, second, hour, day, week,
month, and year.
4.1.3 TypeP and TypePaddress
Section 13 of the IPPM framework [2] introduces the generic notion of Section 13 of the IPPM framework [2] introduces the generic notion of
a "packet of type P" because in some contexts the metric's value a "packet of type P" because in some contexts the metric's value
depends on the type of the packets involved in the metric. In the depends on the type of the packets involved in the metric. In the
definition of a metric, the type P will be explicitly defined, definition of a metric, the type P will be explicitly defined,
partially defined, or left generic. Measurement of metrics defined partially defined, or left generic. Measurement of metrics defined
with generic type P are made specific when performing actual with generic type P are made specific when performing actual
measurements. This naming convention serves as an important reminder measurements. It is important that one be conscious of the exact type
that one must be conscious of the exact type of traffic being of traffic being measured.
measured.
The standardization of the management of the IPPM measures relies on The standardization of the management of the IPPM measures relies on
the capability to finely and unambiguously configure the type P of the capability to finely and unambiguously configure the type P of
the packets, and the parameters of the protocol suites of the type P. the packets, and the parameters of the protocol suites of the type P.
RMON2 introduced the concept of protocol identifiers. RFC2895 [xxv] RMON2 introduced the concept of protocol identifiers. RFC2895 [xxv]
specifies a macro for the definition of protocol identifier. The specifies a macro for the definition of protocol identifier. The
RFC2896 [xxvi] defines the protocol identifiers for different RFC2896 [xxvi] defines the protocol identifiers for different
protocol encapsulation trees. protocol encapsulation trees.
The type P implementation relies on the MACRO PROTOCOL-IDENTIFIER The type P implementation relies on the MACRO PROTOCOL-IDENTIFIER
defined for identifying protocol suites in RMON2. It is achieved by defined for identifying protocol suites in RMON2. It is achieved by
defining the TypeP and the TypePaddress as new syntax in SMIv2 defining the TypeP and the TypePaddress as new syntax in SMIv2
TEXTUAL-CONVENTION. TEXTUAL-CONVENTION.
4.1.1.1. Internet addresses 4.1.3.1 Internet addresses
The section 14 of the IPPM framework defines (for the usual case of a The section 14 of the IPPM framework defines (for the usual case of a
unidirectional path through the Internet) the term "Src" and "Dst". unidirectional path through the Internet) the term "Src" and "Dst".
"Src" denotes the IP address of the beginning of the path, and "Dst" "Src" denotes the IP address of the beginning of the path, and "Dst"
denotes the IP address of the end. denotes the IP address of the end.
The section 3 of the RMON PI Reference specifies the Protocol The section 3 of the RMON PI Reference specifies the Protocol
Identifier Encoding rules, which consists briefly in a recursive Identifier Encoding rules, which consists briefly in a recursive
length value format. "Src" and "Dst" are protocol identifier length value format. "Src" and "Dst" are protocol identifier
parameters. Their values are encoded in separated fields using the parameters. Their values are encoded in separated fields using the
skipping to change at page 7, line 17 skipping to change at page 7, line 27
RFC2896 defines the protocol identifiers ip and ipip4. Should there RFC2896 defines the protocol identifiers ip and ipip4. Should there
be an Internet tunnel end-point of the IP address 192.168.1.1 in the be an Internet tunnel end-point of the IP address 192.168.1.1 in the
tunnel 128.2.6.7. the TypeP of the source address of the tunnel, Src, tunnel 128.2.6.7. the TypeP of the source address of the tunnel, Src,
is 'ip.ipip4'. The encoding of 'ip.ipip4' using the RFC2895 rules 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 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 identifier has 2 parameters, which values will be set only when
implemented. In the IPPM TypeP context these 2 parameters are implemented. In the IPPM TypeP context these 2 parameters are
provided in Src (or Dst). In the current example the value of Src is provided in Src (or Dst). In the current example the value of Src is
"192.168.1.1 128.2.6.7". "192.168.1.1 128.2.6.7".
4.1.2. GMTTimeStamp 4.1.4 GMTTimeStamp
This textual convention defines the time at which an event occurred. This textual convention defines the time at which an event occurred.
It is very similar to the NTP timestamp format except that it It is very similar to the NTP timestamp format except that it
represents the time elapsed since January 1st, 2000 instead of represents the time elapsed since January 1st, 2000 instead of
January 1st, 1900. January 1st, 1900.
4.1.3. IppmStandardMetrics 4.1.5 IppmStandardMetrics
Each standard metric is identified in the IPPM-METRICS-REGISTRY under Each standard metric is identified in the IPPM-METRICS-REGISTRY under
the node rfc in a chronological order. This textual convention the node rfc in a chronological order. This textual convention
defines an octet string to permit several metrics to be performed in defines an octet string to permit several metrics to be performed in
a single measure. a single measure.
4.1.4. Report definition 4.1.6 Report definition
A report consists of sending, or logging, a subset of results of A report consists of sending, or logging, a subset of results of
measurements that have been taken over a period of time. The report measurements that have been taken over a period of time. The report
consists of actions that are taken on the measurement results. An consists of actions that are taken on the measurement results. An
action is performed either: action is performed either:
+ For each result + For each result
+ On the results corresponding to a measurement cycle + On the results corresponding to a measurement cycle
+ On the results available at the measurement completion. + On the results available at the measurement completion.
skipping to change at page 8, line 30 skipping to change at page 8, line 36
+ A basic report is defined in the object ippmReportSetupDefinition; + A basic report is defined in the object ippmReportSetupDefinition;
+ More elaborate reports are described using a metric threshold to + More elaborate reports are described using a metric threshold to
generate alarms and events. generate alarms and events.
+ Pushing of alarms and reports requires a management station + Pushing of alarms and reports requires a management station
address to which the data will be sent. address to which the data will be sent.
+ SLA alarms are described using an events duration threshold. + SLA alarms are described using an events duration threshold.
The TEXTUAL-CONVENTION IppmReportDefinition specifies the list of The TEXTUAL-CONVENTION IppmReportDefinition specifies the list of
events and actions that are used to create a report. events and actions that are used to create a report.
4.2. Structure of the MIB 4.2 Structure of the MIB
The MIB is arranged as follow: The MIB is arranged as follow:
- ippmNotifications - ippmSystem
- ippmOwnersGroup
- ippmSystemGroup
- ippmMeasureGroup - ippmOwners
- ippmHistoryGroup - ippmHistory
- ippmNetworkMeasureGroup - ippmNetMeasure
- ippmAggrMeasureGroup - ippmAggrMeasure
- ippmReportGroup - ippmReport
4.2.1. The ippmOwners Group
This group identifies an owner, or group of owners that have access - ippmNotifications
to measurements on a probe.
4.2.2. The ippmSystem Group 4.2.1 The ippmSystem Group
This group consists of a set of parameters describing the clock This group consists of a set of parameters describing the clock
synchronization at a particular point of measure over time. synchronization at a particular point of measure over time, as well
as the system clock where the IPPM-REPORTING-MIB agent resides.
This group is critical to the implementation of the IPPM MIB. This group is critical to the implementation of the IPPM MIB.
Section 6.3. of the IPPM Framework states that Section 6.3. of the IPPM Framework states that
"Those who develop such measurement methodologies should strive to: "Those who develop such measurement methodologies should strive to:
+ Minimize their uncertainties/errors, + Minimize their uncertainties/errors,
+ Understand and document the sources of uncertainty/error, and + Understand and document the sources of uncertainty/error, and
+ Quantify the amounts of uncertainty/error." + Quantify the amounts of uncertainty/error."
The aim of this group is to have these values available to compute The aim of this group is to have these values available to compute
reliable statistics. The implementation of this group is mandatory, reliable statistics. The implementation of this group is mandatory,
whether the time synchronization is automatic or not. whether the time synchronization is automatic or not.
4.2.3. The ippmMeasureGroup 4.2.2 The ippmOwners Group
This group displays all the measures configured on the measurement This group identifies an owner, or group of owners that have access
entity. It consists of the ippmMetricsTable and ippmMeasureTable. The to measurements on a probe.
ippmMeasureTable holds the common part of a measure, while the
specific parameters are handled in the corresponding auxiliary table 4.2.3 The ippmMeasure Group
(ippmNetworkMeasure, ippmAggrMeasureTable...) .
This group contains all the IPPM metrics that are registered and
available for use by the agent.
The measurement entity describes in the ippmMetricsTable of the SNMP The measurement entity describes in the ippmMetricsTable of the SNMP
agent the local implementation of the standardized metrics. All agent the local implementation of the standardized metrics. All
standardized metrics should be displayed in this table, with the standardized metrics should be displayed in this table, with the
capability object defining whether the metric is implemented or not. ippmMetricCapabilities object defining whether the metric is
implemented or not.
The control protocol registers a description of the existing measures 4.2.4 The ippmHistory Group
in the ippmMeasureTable and in the auxiliary measure tables. The
ippmMeasureTable table is read-create, but only allows for the
creation of "aggregated" measures when defined in conjunction with
the ippmAggrMeasureTable. Network measures are not allowed to be
created directly by the management entity, and as such the measure
table values for these measures should be display only.
The results of the measurements are logged in the ippmHistoryTable. 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.5 The ippmNetMeasure Group
4.2.4. The ippmNetworkMeasure Group
The control protocol registers a description of the existing network The control protocol registers a description of the existing network
measures in the ippmNetworkMeasureTable and in the ippmMeasureTable. measures in the ippmNetMeasureTable.
This group displays the network measures defined by the control This group displays the network measures defined by the control
protocol. The results are saved in the ippmHistoryTable. protocol. The results are saved in the ippmHistoryTable.
ippmNetworkMeasureTable is an auxiliary table of ippmMeasureTable, ippmNetMeasureTable is a reflection of the configuration of the
and is responsible for the configuration of the network measure. network measure.
4.2.5. The ippmAggrMeasure Group 4.2.6 The ippmAggrMeasure Group
ippmAggrMeasureTable is an auxiliary table of ippmMeasureTable, and ippmAggrMeasureTable is responsible for the consolidation, or
is responsible for the consolidation of the results previously aggregation, of results previously measured and saved in the
measured and saved in the ippmHistoryTable. The aggregated results ippmHistoryTable. The aggregated results are saved in the
are saved in the ippmHistoryTable and may be used for higher ippmHistoryTable and may be used for higher aggregated measures.
aggregated measures.
4.2.6. The Report Group 4.2.7 The Report Group
This group displays the existing reports of the measures collected. This group displays the existing reports of the measures collected.
ippmReportSetupTable is an auxiliary table of ippmMeasureTable, and The ippmReportSetupTable is responsible for the configuration of the
is responsible for the configuration of the reports. reports.
The reports are saved in the ippmReportTable, or sent directly to the The reports are saved in the ippmReportTable, or sent directly to the
applications. applications.
4.2.7. The Notification Group 4.2.8 The Notification Group
The Notification group specifies a list of valid notifications. They The Notification group specifies a list of valid notifications. They
are used to push alarms or reports to the applications. are used to generate alarms,or reports, to the applications.
4.3. Row identification in an application namespace 4.3 Row identification in an application namespace
The control protocol or the test protocol adds rows in the namespace The control protocol, or the test protocol, adds rows in the
of the corresponding measure. namespace of the corresponding measure.
An identifier of an instance of an object is defined as a list of An object instance identifier in an owner namespace is defined as a
objects in the clause INDEX. An object instance identifier in an list of objects in the clause INDEX where the first object type is
owner namespace is defined as a list of objects in the clause INDEX IppmOwnerString.
where the first object type is IppmOwnerString.
As the OBJECT IDENTIFIER, which identifies the instance, begins with As the OBJECT IDENTIFIER, which identifies the instance, begins with
the owner value, the remaining values of the index fields may be the owner value, the remaining values of the index fields may be
chosen independently from one namespace to another. chosen independently from one namespace to another.
This allows the user to choose arbitrary values for the remaining This allows the user to choose arbitrary values for the remaining
fields of the INDEX clause without checking that the values of these fields of the INDEX clause without checking that the values of these
fields exists in the MIB tables. This allows the owner to use the fields exists in the MIB tables. This allows the owner to use the
same values across MIB implementations. same values across MIB implementations.
skipping to change at page 11, line 24 skipping to change at page 11, line 16
an object managed by a management station is identified by the an object managed by a management station is identified by the
management station IppmOwnerString and the private index provided by management station IppmOwnerString and the private index provided by
the MS. the MS.
As the MS manages its private range of indices, it simply chooses one As the MS manages its private range of indices, it simply chooses one
when it wishes to create a new control entry. For the same reason, when it wishes to create a new control entry. For the same reason,
the setup of a measure on several points of measures consists of the setup of a measure on several points of measures consists of
simply sending the same copy of the measure setup to the different simply sending the same copy of the measure setup to the different
points of measures involved. points of measures involved.
4.4. Relationship of IPPM MIB tables 4.4 Relationship of IPPM REPORTING MIB tables
There is inherently a relationship between various tables in the IPPM There is inherently a relationship between various tables in the IPPM
Mib, and as such, the data integrity must be assured. This REPORTING MIB, and as such, the data integrity must be assured. This
relationship is depicted in the following examples. relationship is depicted in the following examples.
4.4.1. Relationship between the Owners Table and the Measure Table 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 The owners table contains the list of "owners" that can create and
activate remote IPPM measurements in an agent. As the table is activate remotely aggregated measures in an IPPM agent or read the
"Read/Create", these users and their associated existing network measures.
"access" rights on metric measurements can be directly configured. It
is recommended to make use of "view based access control" in order to It is recommended to make use of "view based access control" in order
restrict access to this table. For example, the to restrict access to this table. For example, the master user
master user "acme" may be given "write" privileges on the "administrator" may be given "write" privileges on the
ippmOwnersTable, whereas all others are restricted to "read" access. ippmOwnersTable, whereas all others are restricted to "read" access.
The user "acme" can then setup the list of other users that have The user "administrator" can then setup the list of other users that
access to measures. have access to measures.
There must be at least 1 owner in the owners table. This owner may be There must be at least 1 owner in the owners' table. This owner may
either setup by default by the IPPM agent, or configured as stated be either setup by default by the IPPM agent, or configured as stated
above. above.
An owner may have multiple corresponding entries in the measure An owner may have multiple corresponding entries in the network and
table. Each entry in the measure table must be associated with one, aggregated measure tables. Each entry in the measure table is
and only one, entry in the owners table. That is to say, that a associated with one, and only one, entry in the owners' table. That
defined measure may NOT have multiple owners. is to say, that a defined measure may NOT have multiple owners.
Thus, we have a 1:N relationship between the owners table and the Thus, we have a 1:N relationship between the owners' table and a
measure table. measure table.
+---------------------+ +---------------------------+ 4.4.2 Relationship between the Network Measure Table and the
| ippmOwnersTable | | ippmMeasureTable | Aggregated Measure Table
+---------------------+ 1:N +---------------------------+
| OwnersOwner: "Acme" |--------------| Measure Owner: "Acme" |
| "Foo" | | Measure Name:"OneWayDelay"|
| . | |...... |
| . | | Measure Owner: "Foo" |
| . | | Measure Name: "PacketLoss"|
| | | Measure Owner: "Foo" |
+---------------------+ +---------------------------+
4.4.2. Relationship between the Measure Table and the Network Measure
Table/Aggregated Measure Table
The network measure table and the aggregated measure table can be
seen as logical "extensions" to the measure table.
The measure table contains information that is common to both types
of measurements. The information found in the Network Measure Table
and the Aggregated Measure Table is specific to each type of measure.
As the network measure table is read-only, entries in this table must The network measure table is read-only, thus entries in this table
be populated by the agent upon startup. must be populated by the agent upon startup.
The agent could potentially read a database that contains network The agent could potentially read a database that contains network
measures configured by a 3rd party proprietary management system that measures configured by a 3rd party proprietary management system that
directly interacts with the points of measure. An entry can not be directly interacts with the points of measure. However, the "owner"
created in the network measure table without creating the of the measure be defined in the owners table.
corresponding entry in the measure table associated to the measure.
This also implies that the "owner" of the measure be defined in the
owners table.
The aggregated measure table allows for an "owner" to create The aggregated measure table allows for an "owner" to create
aggregated measures (such as average, minimum, maximum) on existing aggregated measures (such as average, minimum, maximum) on existing
measures that are in the measure table. If an "owner" (A) wishes to measures. An owner may even create aggregated measures on network
create an aggregated measure on a measure "owned" by another measures that are owned by other owners. However, it is recommended
"owner" (B), then "owner" (B) must grant "owner" (A) access to his to use view based access control to grant access of network measures
measures. This can be done in the resultsharing table. to owners in the system.
Even though the Measure Table is read-create, an "owner" should only
be able to create, or modify entries in the measure table that
correspond to aggregated measure types. Should an "owner" attempt to
update an entry in the measure table that corresponds to an entry
in the network measure table, than access should be denied.
+---------------------------+ +----------------------------------+
| ippmMeasureTable | | ippmNetworkMeasureTable |
+---------------------------+ +----------------------------------+
| Measure Owner: "Acme" | | MeasureSrc: "Src1" |
| Measure Name:"OneWayDelay | ---| MeasureDst: "Dst1" |
| ....... | | ........ |
| Measure Owner: "Foo" | | MeasureSrc: "Src2" |
| Measure Name: "PacketLoss"| | MeasureDst: "Dst2" |
| | +----------------------------------+
| |
| | +----------------------------------+
| | | ippmAggrMeasureTable |
| | +----------------------------------+
| Measure Owner: "Acme" | | AMHistoryOwner: "Foo" |
| Measure Name: "AvgPLoss" | ---| AMHistoryMetric: "PacketLoss" |
+---------------------------+ +----------------------------------+
+---------------------------+ +----------------------------------+
| ippmHistoryTable | | ippmResultSharingTable |
| (ex: with OWPL values) | | |
+---------------------------+ +----------------------------------+
| Idx: Meas. Owner"Foo " | | SharingOwner: "Foo" |
| Measure Index: 1 | | SharingMeasureOwner:"PacketLoss"|
| Metrix Indx: 12 | | |
| | | SharingGrantedOwner: "Acme" |
| HistorySqceNdx: 1 | +----------------------------------+
| GMTTimeStampValue |
| Value: 5 |
+---------------------------+
| Idx: Meas. Owner "Foo" |
| Mesure Index: 1 |
| Metric Index: 12 |
| HistorySqceNdx: 2 |
| GMTTimeStampValue |
| Value: 15 |
| Idx: Meas. "Acme" |
| Measure Index: 3 |
| Metric Index: 14 |
| HistorySqceNdx: 1 |
| GMTTimeStampValue |
| Value: 10 |
+---------------------------+
As the aggregated measure table essentially "inherits" from the
measure table, one can not create an entry is this table without
first creating an entry in the measure table. Likewise, one can not
delete an entry in the measure table without first deleting the
corresponding row in the aggregated measure table. This logic ensures
that there are no "orphaned" table entries in the aggregated measure
table.
5. IPPM-REPORTING-MIB conceptual presentation
5.1. IPPM-REPORTING-MIB diagram
Conceptual view of objects configured using the IPPM-REPORTING-MIB
+--------------------------------------------------------+
| IPPM-REPORTING-MIB entity |
| |
| +---------------------+ +-------------------+ |
| | | | | |
| | Measure scheduler | | Result storage | |
| | | | | |
| | ^ | | ^ ^^^ | |
| | | | | | ||| | |
| +----------|----------+ +-|---|||-----------+ |
| | | ||| |
| +----------|--------------|---|||-----------+ |
| | | owner | ||| | |
| | | Acces | ||| | |
| | | Control | ||| | |
| +----------|--------------|---|||-----------+ |
| | | ||| |
+------------------|--------------|---|||----------------+
| | |||
| | |||
+----------------+ | +----------+-+ ||| +-------------+
| ControlMeasure | | | GetResult | ||| | CreateResult|
|----------------+-+ |------------| ||+--+-------------|
| | | | || | |
| owner | | owner | || | owner |
| privateNdx | | privateNdx | || | privateNdx |
| metrics | | metric | || | metrics |
| scheduler | | timestamp | || | timestamp |
| addresses | +------------+ || | value |
| status | || +-------------+
+----------------+ ||
||
+---------------------------+|
| |
+---------+---------+ +------+-----------------+
|GetMeasureResults | |GetMeasureMetricResults |
|-------------------| |------------------------|
| | | owner |
| owner | | privateNdx |
| privateNdx | | metric |
+-------------------+ +------------------------+
The managed objects of the IPPM-REPORTING-MIB are the measures and
the results.
5.2. Conceptual programming interface
This section describes a conceptual programming interface for the
integration of the IPPM-REPORTING-MIB in a point of measure.
5.2.1. Measure control
A measure is created/deleted/suspended through the ControlMeasure()
call.
5.2.2. Result log
A result of a measure is created in the IPPM-REPORTING-MIB History
table using a CreateResult() call. Results belonging to a measure are
managed according to the setup of the measure.
5.2.3. Reporting
Results are reported using the method GetResult(),
GetMeasureMetricResults() and GetMeasureResults() respectively to get
a singleton result, the singleton result of a metric measure, and
finally to get the singleton result of a measure.
5.2.4. Logical calls
Objects are managed using 5 main primitives:
controlMeasure();
CreateResult();
GetResult();
GetMeasureMetricResults();
GetMeasureResults().
5.3. SNMP mapping
ControlMeasure() corresponds to a SNMP set-request on a conceptual
row of ippmMeasureEntry and on a conceptual row of
ippmNetworkMeasureEntry.
CreateResult() is a internal interface for adding measure results in
the ippmHistoryTable.
GetResult() corresponds to an SNMP get-request on a result.
GetMeasureMetricResults() corresponds to a SNMP walk on the results
of a metric measure subtree.
GetMeasureResults() corresponds to a SNMP walk on the results of a
measure subtree.
6. Measurement architectures 5 Measurement architectures
There are four main measurement architectures. There are three main measurement architectures.
6.1. Proxy architecture 5.1 Proxy architecture
+----+ +----+ . +----+ +----+
|NMS1| |NMS2| . |NMS1| |NMS2|
+----+ +----+ . +----+ +----+
^ ^ . ^ ^
| | . | |
+----------+ +----------+ . +----------+ +----------+
| | . | |
SNMP or Sibling . SNMP or Sibling
| | . | |
v v . v v
+--------------------------+ . +--------------------------+
| IPPM-REPORTING-MIB agent | . | IPPM-REPORTING-MIB agent |
+--------------------------+ . +--------------------------+
^ ^ . ^ ^
| | . | |
OWDP-Control . OWDP-Control
| | . | |
+----------+ +----------+ . +----------+ +----------+
| | . | |
v v . v v
+----------------+ +------------------+ .+----------------+ +------------------+
| Packets-Sender |--OWDP-Test-->| Packets-Receiver | .| Packets-Sender |--OWDP-Test-->| Packets-Receiver |
+----------------+ +------------------+ .+----------------+ +------------------+
In this architecture, the different NMSs query the IPPM-REPORTING- In this architecture, the different NMSs query the IPPM-REPORTING-
MIB agent for measurements. The agent controls whether the NMS is MIB agent for measurements. The agent controls whether the NMS is
granted access to perform the measure requested. Each NMS accesses granted access to perform the measure requested. Each NMS accesses
the results of its measurements in the IPPM-REPORTING-MIB statistics the results of its measurements in the IPPM-REPORTING-MIB statistics
table. table.
The measurement setup/teardown and the data collection are done using The measurement setup/teardown and the data collection are done using
the control protocol and the test protocol. the control protocol and the test protocol.
In this mode the NMS does not depend either on the control protocol In this mode the NMS does not depend on the control protocol nor on
nor on the test protocol. The entities involved in the measurement do the test protocol. The entities involved in the measurement do not
not need to implement the IPPM-REPORTING-MIB nor SNMP. This mode need to implement the IPPM-REPORTING-MIB nor SNMP. This mode allows
allows for lightweight implementation in the point of measure, and for lightweight implementation in the point of measure, and also for
also for heterogeneous control protocols to coexist. heterogeneous control protocols to coexist.
Finally, the proxy is a checkpoint where measurement activity may be Finally, the proxy is a checkpoint where measurement activity may be
logged, and where access to measurement setups may be tightly logged, and where access to measurement setups may be tightly
controlled. Thus, it provides a reliable architecture to manage the controlled. Thus, it provides a reliable architecture to manage the
security of a measurement system. security of a measurement system.
6.2. Reporting architecture 5.2 Reporting architecture
In this architecture the SNMP protocol is only used to read the In this architecture the SNMP protocol is only used to read the
results of the measurements in the IPPM-REPORTING-MIB History Table, results of the measurements in the IPPM-REPORTING-MIB History Table,
and also to inform the NMS that an event has occurred. and also to inform the NMS that an event has occurred.
+----+ +----+ . +----+ +----+
|NMS1| |NMS2| . |NMS1| |NMS2|
+----+ +----+ . +----+ +----+
^ ^ ^ ^ . ^ ^ ^ ^
| | | | . | | | |
SNMP| SNMP| . SNMP| SNMP|
| | | | . | | | |
| | | | . | | | |
| OWDP | OWDP . | OWDP | OWDP
|Control |Control . |Control |Control
| | | | . | | | |
| | +------------------------------+ . | | +------------------------------+
| | | | | . | | | | |
| | +--|---------------------------+ | . | | +--|---------------------------+ |
| | | | | | . | | | | | |
| +--|--|------------------------+ | | . | +--|--|------------------------+ | |
| | | | | | | . | | | | | | |
+--------+---------------------+ | | . +--------+---------------------+ | |
| | | | | | | | . | | | | | | | |
| | | | | | | | . | | | | | | | |
v v v v v v v v . v v v v v v v v
+------------------+ +------------------+ . +------------------+ +------------------+
|IPPM-REPORTING-MIB| |IPPM-REPORTING-MIB| . |IPPM-REPORTING-MIB| |IPPM-REPORTING-MIB|
| agent | | agent | . | agent | | agent |
+------------------+ +------------------+ . +------------------+ +------------------+
| Packets-Sender |--OWDP-Test-->| Packets-Receiver | . | Packets-Sender |--OWDP-Test-->| Packets-Receiver |
+------------------+ +------------------+ . +------------------+ +------------------+
The activation of a measure by the control protocol or the test The activation of a measure by the control protocol or the test
protocol creates a measure in the IPPM-REPORTING-MIB Measure table. protocol creates a measure in the IPPM-REPORTING-MIB Network Measure
The table in question may be not accessible by SNMP. In this case, a table. The table in question may be not accessible by SNMP. In this
list of the measure identifiers (owner, index) is handled by the case, a list of the measure identifiers (owner, index) is handled by
measurement software. the measurement software.
Each timestamped result of the measure is logged on the fly in the Each timestamped result of the measure is logged in the IPPM-
IPPM-REPORTING-MIB History table in order to allow read access to the REPORTING-MIB History table in order to allow read access to the
NMSs and event handling. NMSs and event handling.
On completion, the measurement results are managed according to the On completion, the measurement results are managed according to the
measure setup: measure setup:
+ The results may be sent to an NMS using a SNMP Trap PDU or a + The results may be sent to an NMS;
SNMP Inform PDU. The NMS may be the sender entity or the control
entity;
+ They may be dropped from the IPPM-REPORTING-MIB History table. + 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 In this mode, it is recommended to use an SNMPv2 Inform PDU to send
the result because it ensures that the entire block of the result is reporting events because it ensures that the entire block of the
received. There is no control using SNMP Trap PDU. result is received. There is no control using SNMP Trap PDU.
6.3. Gateway architecture 5.3 Gateway architecture
The gateway architecture combines the proxy mode and the reporting The gateway architecture combines the proxy mode and the reporting
mode. mode.
+-------+ +------+ . +-------+ +------+
| NMS1 | | NMS2 | . | NMS1 | | NMS2 |
+-------+ +------+ . +-------+ +------+
^ ^ . ^ ^
| | . | |
SNMP SNMP . SNMP SNMP
| | . | |
| +----------------------------------------+ . | +----------------------------------------+
| | | . | | |
+-------------+ +------------------+ . +-------------+ +------------------+
| | | | | . | | | | |
+----------------------------------------+ | . +----------------------------------------+ |
| | | | | | . | | | | | |
| | v v | | . | | v v | |
| | +------------------------+ | | . | | +------------------------+ | |
| | | IPPM-REPORTING-MIB | | | . | | | IPPM-REPORTING-MIB | | |
| | | scheduler | | | . | | | Gateway | | |
| | +------------------------+ | | . | | +------------------------+ | |
| | | control server | | | . | | | control server | | |
| | +------------------------+ | | . | | +------------------------+ | |
| | ^ ^ | | . | | ^ ^ | |
| | | | | | . | | | | | |
| | OWDP-Control protocol | | . | | OWDP-Control protocol | |
| | | | | | . | | | | | |
| | +-----+ +-------+ | | . | | +-----+ +-------+ | |
| | | | | | . | | | | | |
v v v v v v . v v v v v v
+-------------+---------+ +--------+-------------+ . +-------------+---------+ +--------+-------------+
| IPPM- | Packets | |Packets | IPPM | . | IPPM- | Packets | |Packets | IPPM |
|REPORTING-MIB| Sender | |Receiver|REPORTING-MIB| . |REPORTING-MIB| Sender | |Receiver|REPORTING-MIB|
| agent | |-OWDP-Test->| | agent | . | agent | |-OWDP-Test->| | agent |
+-------------+---------+ +--------+-------------+ . +-------------+---------+ +--------+-------------+
The NMS measurement queries are registered in the IPPM-REPORTING-MIB The NMS measurement queries are registered in the IPPM-REPORTING-MIB
scheduler and performed by the control and the test protocol. The NMS gateway and performed by the control and the test protocol. The NMS
directly consults the result in the corresponding points of measure. directly consults the result in the corresponding IPPM REPORTING MIB
agent of the points of measure.
6.4. Security 5.4 Security
The proxy mode provides flexibility and control of the access to the The proxy mode provides flexibility and control of the access to the
points of measure, while allowing lightweight control protocol and points of measure, while allowing lightweight control protocol and
test protocol implementations in the points of measure. Different test protocol implementations in the points of measure. Different
security rules may be applied to the NMS domain and to measurement security rules may be applied to the NMS domain and to measurement
system domains. system domains.
The reporting mode has 2 security domains: The reporting mode has 2 security domains:
+The control of the measurement setups relies on the control and
the test protocol security mechanisms. + The control of the measurement setups relies on the control
and the test protocol security mechanisms;
+ The control of access to the results depends on the SNMP + The control of access to the results depends on the SNMP
security mechanisms. 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 The gateway mode security relies on the security of the proxy mode
and of the reporting mode. and of the reporting mode.
7. Reporting mode integration 6 Reporting mode integration
The IPPM-REPORTING-MIB standardizes the parameters that: The IPPM-REPORTING-MIB standardizes the parameters that:
+ Define the configuration of the IPPM metrics measures; + Define the configuration of the IPPM metrics measures;
+ Define the format of the results of the measure; + Define the format of the results of the measure;
+ Define the report of the IPPM metric measures results. + Define the report of the IPPM metric measures results.
It introduces the concept of owner namespace to allow for fast It introduces the concept of owner namespace to allow for fast
configuration and reporting across multiple points of measurement. configuration and reporting across multiple points of measurement.
skipping to change at page 21, line 39 skipping to change at page 16, line 41
for negotiation between the NMS and the points of measure before for negotiation between the NMS and the points of measure before
activating the measure. activating the measure.
A measure is primarily defined by its identifier, the metrics to A measure is primarily defined by its identifier, the metrics to
measure, the description of the end point addresses and the measure, the description of the end point addresses and the
description of the scheduling of the measure. description of the scheduling of the measure.
The description of the measure is distributed to the points of The description of the measure is distributed to the points of
measure involved. The distribution may not be synchronized. measure involved. The distribution may not be synchronized.
7.1. Integration 6.1 Integration
The control protocol, test protocol and the IPPM-REPORTING-MIB share
the same semantic.
The integration of the IPPM-REPORTING-MIB, and the test and control The integration of the IPPM-REPORTING-MIB, and the test and control
protocols, relies on the use of the conceptual programming interface protocols consists in pushing the network measure setup/teardown
described in section 6. It consists in pushing the measure parameters and the result values from the measurement software to the
setup/teardown parameters and the result values from the measurement IPPM-REPORTING-MIB agent.
software to the IPPM-REPORTING-MIB agent.
7.2. Setup of the measure
The creation of the measure consists only in transferring the measure
description from the measurement software to the MIB. The management
of the measure is done using the ControlMeasure().
The protocol, which provides the parameters of the measure to manage,
may be the control protocol of the test protocol.
Different frameworks may be used to setup a measure.
7.2.1. Synchronous setup
The control protocol sets up the measure both in the sender and the
receiver before the measurement.
7.2.2. Asynchronous setup
The control protocol sets up the measure only in the sender. In this
case, the receiver has a service already activated (or pending )for
the typeP of the measurement.
As the first test packet includes the description of the measure, it
may differ from regular test packets. If the first test packet is not
consistent with the regular test packets, it must not be used for
performing metrics measurement.
7.3. Setup of the measurement report 6.2 Setup of the measure network
The report description is an extension to the definition of a The measurement system updates the MIB on creation of a network
measure. It describes the event and the data to include in the measure.
report. A report is read by an NMS in the ippmReportTable, or pushed
to a NMS using a SNMP Trap PDU, a SNMP Inform PDU, an email, or a
SMS.
The control protocol, or the test protocol, includes the description 6.3 Setup of a measurement report
of the report in the setup of the measure. A measurement report setup describes events and data to include in
the report. A report is read by an NMS in the ippmReportTable, or
pushed to a NMS using a SNMP Inform PDU, an email, or a SMS.
Different types of reports may be combined: Different types of reports may be combined:
+ A trivial report defines the results to be saved in the + A trivial report defines the results to be saved in the
ippmReportTable; ippmReportTable;
+ A basic report defines the host to which the results are pushed + A basic report defines the host to which the results are pushed
on completion of the measure; on completion of the measure;
+ An alarm report defines a threshold on the results of the + An alarm report defines a threshold on the results of the
measure. A message is sent to a host when the result raises or measure. A message is sent to a host when the result rises above,
fall the threshold; or falls below the threshold;
+ An SLA report defines a threshold on the results of the + An SLA report defines a threshold on the results of the
measure. The events are filtered using a staircase method. The measure. The report consists of the results of the measure (time
report consists in the results of the measure (time and value) of and value) of the filtered events. The reports are sent at each
the filtered events. The reports are sent at each measure cycle measurement cycle, or when the measure completes.
or when the measure completes.
7.4. Writing the results in the IPPM-REPORTING-MIB 6.4 Updating the history of the MIB
Results have to be written by the measurement task in the agent Results have to be written by the measurement task in the agent
implementing the IPPM MIB. implementing the IPPM REPORTING MIB.
Adding the results of a measurement consists in the transfer of the Adding the results of a measurement consists in the transfer of the
result from the measurement software to the agent. The protocol that result from the measurement software to the SNMP agent. The protocol
provides the result may be the control protocol, or the test that provides the result may be the control protocol, or the test
protocol. protocol.
Writing a result is done using the CreateResult(). 6.5 Report download and upload
7.5. Report download and upload
A report is read in the ippmReportTable using SNMP, or pushed by the A report is read in the ippmReportTable using SNMP, or pushed by the
IPPM_MIB agent using a SNMP Trap PDU, a SNMP Inform PDU, an email or IPPM_MIB agent using a SNMP Inform PDU, an email or a SMS.
a SMS.
7.6. Default value 6.6 Default value
The default values correspond to IP version 4. The default values correspond to IP version 4.
8. Definition 7 Definition
IPPM-REPORTING-MIB DEFINITIONS ::= BEGIN IPPM-REPORTING-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
MODULE-IDENTITY, MODULE-IDENTITY,
NOTIFICATION-TYPE, NOTIFICATION-TYPE,
OBJECT-TYPE, OBJECT-TYPE,
experimental ,Integer32 experimental ,Integer32
FROM SNMPv2-SMI FROM SNMPv2-SMI
-- --
skipping to change at page 24, line 34 skipping to change at page 18, line 21
RowStatus, RowStatus,
StorageType, StorageType,
TEXTUAL-CONVENTION TEXTUAL-CONVENTION
FROM SNMPv2-TC FROM SNMPv2-TC
MODULE-COMPLIANCE, MODULE-COMPLIANCE,
OBJECT-GROUP, OBJECT-GROUP,
NOTIFICATION-GROUP NOTIFICATION-GROUP
FROM SNMPv2-CONF; FROM SNMPv2-CONF;
ippmReportingMib MODULE-IDENTITY ippmReportingMib MODULE-IDENTITY
LAST-UPDATED "200203171200Z" -- March 17, 2002 LAST-UPDATED "200306291200Z" -- June, 2003
ORGANIZATION "France Telecom - R&D" ORGANIZATION "France Telecom - R&D"
CONTACT-INFO CONTACT-INFO
"Emile Stephan "Emile Stephan
France Telecom - R&D France Telecom - R&D
2, Avenue Pierre Marzin 2, Avenue Pierre Marzin
Technopole Anticipa Technopole Anticipa
22307 Lannion Cedex 22307 Lannion Cedex
FRANCE FRANCE
Tel: + 33 2 96 05 36 10 Tel: + 33 2 96 05 36 10
E-mail: emile.stephan@francetelecom.com E-mail: emile.stephan@francetelecom.com
skipping to change at page 25, line 8 skipping to change at page 18, line 45
801 Gateway Blvd. Suit 500 801 Gateway Blvd. Suit 500
South San Francisco, CA 94080 South San Francisco, CA 94080
Tel : 1 650 875-1524 Tel : 1 650 875-1524
E-mail : jessie.jewitt@rd.francetelecom.com" E-mail : jessie.jewitt@rd.francetelecom.com"
DESCRIPTION DESCRIPTION
" This memo defines a portion of the Management Information Base " This memo defines a portion of the Management Information Base
(MIB) for use with network management protocols in TCP/IP-based (MIB) for use with network management protocols in TCP/IP-based
internets. In particular, it specifies the objects used for internets. In particular, it specifies the objects used for
managing the results of the IPPM metrics measurements, alarms and managing the results of the IPPM metrics measurements, alarms and
reporting the measures results." reporting of measurement results."
REVISION "200210181200Z" -- 18 October 2002 REVISION "200210181200Z" -- 18 October 2002
DESCRIPTION DESCRIPTION
"General cleanup "General cleanup
Change 5 tables to read write" Change 5 tables to read write"
REVISION "200302141200Z" -- 14 February 2003 REVISION "200302141200Z" -- 14 February 2003
DESCRIPTION DESCRIPTION
"Modifications based upon feedback from IETF-55" "Modifications based upon feedback from IETF-55"
REVISION "200306291200Z" -- 29 June 2003
DESCRIPTION
"Adaptation to VACM, preparation of the final version"
::= { experimental 10001 } ::= { experimental 10001 }
ippm OBJECT IDENTIFIER ::= { experimental 10000 } ippm OBJECT IDENTIFIER ::= { experimental 10000 }
-- --
-- TEXTUAL-CONVENTION -- TEXTUAL-CONVENTION
-- --
IppmOwnerString ::= TEXTUAL-CONVENTION IppmOwnerString ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An OwnerString, which length is limited to 32." "An OwnerString, which length is limited to 32."
SYNTAX OCTET STRING (SIZE (0..32)) SYNTAX OCTET STRING (SIZE (0..32))
TimeUnit ::= TEXTUAL-CONVENTION TimeUnit ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A list of time units." "A enumerated list of time units."
SYNTAX INTEGER { SYNTAX INTEGER {
year(1), year(1),
month(2), month(2),
week(3), week(3),
day(4), day(4),
hour(5), hour(5),
second(6), second(6),
millisecond(7), millisecond(7),
microsecond(8), microsecond(8),
nanosecond(9) nanosecond(9)
} }
-- --
-- --
IppmStandardMetrics ::= TEXTUAL-CONVENTION IppmStandardMetrics ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
" Each standard metric is identified in the IPPM-METRICS- " Each standard metric is identified in the IPPM-METRICS-
REGISTRY under the node rfc in a chronological order. To permit REGISTRY under the node rfc in chronological order. In order to
several metrics to be performed in a single measure there is an allow for
several metrics to be calculated in a single measure, there is an
need need
to describe in a bit string the metrics to be performed, to describe in a bit string the metrics to be measured.
granted... This textual convention defines an octet string that gathers in a
This textual convention defines an octet string that gathered in
a
bit string a sequence of bits. The bit order corresponds to the bit string a sequence of bits. The bit order corresponds to the
order order
of the metrics identifiers in the registry. of the metric identifiers in the registry.
The first bit of the string has the index 0. The index 1 The first bit of the string has the index 0. The index 1
corresponds to the first metric of the registry corresponds to the first metric of the registry
(instantaneousUnidirectionalConnectivity ). (instantaneousUnidirectionalConnectivity ).
Example: Example:
One-way-Delay(6) is identified as the leaf number 6 of the node One-way-Delay(6) is identified as the leaf number 6 of the node
rfc of the rfc of the
registry. One-way-Packet-Loss(12) is identified as the leaf registry. One-way-Packet-Loss(12) is identified as the leaf
number 12 of the node number 12 of the node
rfc of the registry. A network measure performing both One-way- rfc of the registry. A network measure performing both One-way-
Delay(6) and One- Delay(6) and One-
way-Packet-Loss(12) will be described as '0001000001000000'b, way-Packet-Loss(12) will be described as '0001000001000000'b,
'1040'B. '1040'B.
" "
SYNTAX OCTET STRING SYNTAX OCTET STRING
GMTTimeStamp ::= TEXTUAL-CONVENTION GMTTimeStamp ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The value of the ippmSystemTime object at which a specific "The value at which a specific occurrence happened. The specific
occurrence happened. The specific occurrence must be defined in occurrence must be defined in the description of any object
the description of any object defined using this type. defined using this type.
field octets contents range field octets contents range
----- ------ -------- ----- ----- ------ -------- -----
1 1-4 second since 1 Jan 2000 0H00* 0..2^31 - 1 1 1-4 second since 1 Jan 2000 0H00* 0..2^31 - 1
2 5-8 fractional part of the second* 0..2^32 - 1 2 5-8 fractional part of the second* 0..2^32 - 1
* the value is in network-byte order * the value is in network-byte order
The timestamp format is directly inspired from the NTP timestamp The timestamp format is directly inspired from the NTP timestamp
format. format.
It differs because it counts the second since 1 Jan 2000 0H00 It differs because it counts the second since 1 Jan 2000 0H00
skipping to change at page 27, line 24 skipping to change at page 21, line 12
" "
SYNTAX OCTET STRING (SIZE (8)) SYNTAX OCTET STRING (SIZE (8))
TypeP ::= TEXTUAL-CONVENTION TypeP ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This textual convention is a display string used to describe the "This textual convention is a display string used to describe the
protocol encapsulation list of a packet, and is used as the value protocol encapsulation list of a packet, and is used as the value
of the SYNTAX clause for the type of the Src and Dst of an IPPM of the SYNTAX clause for the type of the Src and Dst of an IPPM
measure. The RFC2895 specifies a macro named PROTOCOL-IDENTIFIER measure. The RFC2895 specifies a macro named PROTOCOL-IDENTIFIER
for the definition of protocol identifiers while its companion for the definition of protocol identifiers, while its companion
document, the RFC2896 defines a set of protocol identifiers. document, the RFC2896 defines a set of protocol identifiers.
TypeP is defined as a display string. It consists in a list of TypeP is defined as a display string. It consists of a list of
dot separated protocol names. Each protocol name has been dot separated protocol names. Each protocol name has been
previously defined using the macro PROTOCOL-IDENTIFIER of the RFC previously defined using the macro PROTOCOL-IDENTIFIER of the RFC
2895. 2895.
Examples: Examples:
The RFC2896 defines the protocol identifiers 'ether2', 'ip', The RFC2896 defines the protocol identifiers 'ether2', 'ip',
'ipip4', 'udp', 'tcp', 'telnet'... 'ipip4', 'udp', 'tcp', 'telnet'...
The TypeP of the source address corresponding to telnet is the The TypeP of the source address corresponding to telnet is the
string 'ip.tcp.telnet'. string 'ip.tcp.telnet'.
The TypeP of the source address corresponding to UDP packets sent The TypeP of the source address corresponding to UDP packets sent
in an IP tunnel is the string 'ip.ipip4.udp'. in an IP tunnel is the string 'ip.ipip4.udp'.
Notes: Note:
An IPPM measure is active, so generally a TypeP value does not An IPPM measure is active, so generally a TypeP value does not
describe the link layer (i.e. ether2...). Valid Internet packets describe the link layer (i.e. ether2...). Valid Internet packets
are sent from Src to Dst. Then the choice of the link layer are sent from Src to Dst. Then the choice of the link layer
relies on the Internet stack." relies on the Internet stack."
SYNTAX OCTET STRING (SIZE (0..255)) SYNTAX OCTET STRING (SIZE (0..512))
TypePaddress ::= TEXTUAL-CONVENTION TypePaddress ::= TEXTUAL-CONVENTION
DISPLAY-HINT "255a" DISPLAY-HINT "255a"
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This textual convention is a Display string used to describe the "This textual convention is a Display string used to describe the
parameters of the protocol encapsulation list of a packet, parameters of the protocol encapsulation list of a packet,
basically the address. basically the address.
TypePaddress is defined as a display string. It consists in a TypePaddress is defined as a display string. It consists in a
list of space separated parameter list. Each parameter in the list of space separated parameter list. Each parameter in the
list corresponds a parameter of a PROTOCOL-IDENTIFIER of the list corresponds to a parameter of a PROTOCOL-IDENTIFIER of the
TypeP. TypeP.
Example: Example:
The TypeP 'ip.ipip4' has 2 parameters. A valid TypePaddress value The TypeP 'ip.ipip4' has 2 parameters. A valid TypePaddress value
is '192.168.1.1 128.2.6.7'." is '192.168.1.1 128.2.6.7'."
SYNTAX OCTET STRING (SIZE (0..255)) SYNTAX OCTET STRING (SIZE (0..512))
IppmReportDefinition ::= TEXTUAL-CONVENTION IppmReportDefinition ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"IppmReportDefinition is intended to be used for describing the " A report definition is a list of statements describing a report. A
report resulting from a measurement. By default, all the results of a statement is part of this process if its bit in the definition is set
measure belong to the report of this measure. to '1'. For all bit values that are set to one, a report will be
generated.
The first step of the report definition sets up triggers on the value The report process uses results saved in the history table. Threshold
of the measure, and on the distribution over time of the events values are provided by the report setup.
generated by these triggers.
The resulting measures corresponding to an event are reported Given that not all results from a metric measurement are
periodically, or sent in alarms as soon as the event occurs. pertinent to a particular report, and that the size of the report
must be limited whenever possible, the guidelines for the definition
of a report are as follows:
The end of the description describes housekeeping tasks. + Select the events for consideration (1);
+ Configure filters to select pertinent values (2);
+ Describe the way the report is delivered (3);
+ Describe clean up actions to perform on report completion (4);
An action is performed if the corresponding bit is set to 1. -1- events
onSingleton(1): Events determine when a report is processed. Events are
The actions are performed each time a new result of the measure exclusive. The possible values are:
onSingleton:
The report is processed each time a new result of the measurement
occurs. occurs.
onMeasureCycle(2): onMeasureCycle:
The actions are performed on the results of the measure at the end of The report is processed each time a cycle of measure is
each cycle of measure. completed.
onMeasureCompletion(3): onMeasureCompletion:
The actions are performed on the results of the measure at the end of The report is processed at the end of the measurement.
the measure.
reportOnlyUptoDownMetricResults(4): -2- filters
Report the contiguous results that are on opposite sides of the Filters determine if a result belongs to a report.
metric threshold. ReportInBandResults and ReportOutBandResults are exclusive. The
usage of ReportInBandResults and ReportOutBandResults exclude the
usage of ReportAboveResults and ReportBelowResults.
Possible values are:
reportOnlyExceededEventsDuration(5): reportUpAndDownResults:
Report the current result of a series of contiguous results that Report contiguous results that are on opposite sides of
exceed the metric threshold when the duration of the series is over the up and down metric threshold.
the events duration threshold seconds.
inIppmReportTable(6): ReportInBandResults:
Store the report in the local ippmReportTable.
inSNMPTrapPDU(7): Report results lower than the high metric threshold
Send the report using a SNMP-Trap-PDU. field of the report setup and greater than the low
metric threshold field of the report setup.
inSNMPv2TrapPDU(8): ReportOutBandResults:
Report results greater than the high metric threshold
field of the report setup and lower than the low metric
threshold field of the report setup.
ReportAboveResults:
Report results greater than the high metric threshold
field of the report setup.
ReportBelowResults:
Report results lower than the low metric threshold field
of the report setup.
reportExceededEventsDuration:
Save the results of the metric only if the current
filter triggers repeatedly for a series of contiguous
results during more than
ippmReportSetupDurationThreshold seconds.
-3- deliver
Even though report delivery statements are not exclusive, care
should be taken to limit the number of report methods to 2. The
delivery methods are:
inIppmReportTable:
Store the report in the local ippmReportTable.
NOTE WELL: Results are not stored in the report table if
this flag is not set.
inSNMPv2TrapPDU:
Send the report using a SNMPv2-Trap-PDU. Send the report using a SNMPv2-Trap-PDU.
inInformRequestPDU(9): inInformRequestPDU:
Send the report using a SNMP InformRequest-PDU. Send the report using a SNMP InformRequest-PDU.
inEmail(10): inEmail:
Send the report using an email. Send the report using an email.
inSMS(11): inSMS:
Send the report using a SMS. Send the report using a SMS.
onReportDeliveryClearHistory(12): -4- Cleanup
Remove all the results corresponding to this measure from the onReportDeliveryClearReport(12):
ippmHistoryTable when the report has been delivered.
Remove all the results corresponding to this measure
from the ippmReportTable when the report has been
delivered.
onReportDeliveryClearReport(13):
Remove all the results corresponding to this measure from the
ippmReportTable when the report has been delivered.
" "
SYNTAX BITS { SYNTAX BITS {
none(0), -- reserved none(0), -- reserved
onSingleton(1), onSingleton(1),
onMeasureCycle(2), onMeasureCycle(2),
onMeasureCompletion(3), onMeasureCompletion(3),
reportOnlyUptoDownMetricResults(4), reportUpAndDownResults(4),
reportOnlyExceededEventsDuration(5), reportInBandResults(5),
inIppmReportTable(6), reportOutBandResults(6),
inSNMPTrapPDU(7), reportAboveResults(7),
inSNMPv2TrapPDU(8), reportBelowResults(8),
inInformRequestPDU(9), reportExceededEventsDuration(9),
inEmail(10), inIppmReportTable(10),
inSMS(11), inSNMPv2TrapPDU(11),
onReportDeliveryClearHistory (12), inInformRequestPDU(12),
onReportDeliveryClearReport (13) inEmail(13),
inSMS(14),
onReportDeliveryClearReport(15)
} }
-- --
-- IPPM Notifications -- IPPM Notifications
-- --
ippmNotifications OBJECT IDENTIFIER ::= { ippm 0 } ippmNotifications OBJECT IDENTIFIER ::= { ippm 0 }
-- --
-- IPPM Conformance -- IPPM Conformance
-- --
ippmConformance OBJECT IDENTIFIER ::= { ippm 1 } ippmConformance OBJECT IDENTIFIER ::= { ippm 1 }
-- --
-- IPPM Mib objects definitions -- IPPM Mib objects definitions
-- --
ippmSystem OBJECT IDENTIFIER ::= { ippmReportingMib 1 } ippmSystem OBJECT IDENTIFIER ::= { ippmReportingMib 1 }
ippmOwners OBJECT IDENTIFIER ::= { ippmReportingMib 2 } ippmOwners OBJECT IDENTIFIER ::= { ippmReportingMib 2 }
ippmMeasure OBJECT IDENTIFIER ::= { ippmReportingMib 3 } ippmHistory OBJECT IDENTIFIER ::= { ippmReportingMib 3 }
ippmHistory OBJECT IDENTIFIER ::= { ippmReportingMib 4 } ippmMeasure OBJECT IDENTIFIER ::= { ippmReportingMib 4 }
ippmNetworkMeasure OBJECT IDENTIFIER ::= { ippmReportingMib 5 } ippmReport OBJECT IDENTIFIER ::= { ippmReportingMib 5 }
ippmAggrMeasure OBJECT IDENTIFIER ::= { ippmReportingMib 6 }
ippmReport OBJECT IDENTIFIER ::= { ippmReportingMib 7 }
-- --
-- ippmSystem Group -- ippmSystem Group
-- --
-- --
ippmSystemTime OBJECT-TYPE ippmSystemTime OBJECT-TYPE
SYNTAX GMTTimeStamp SYNTAX GMTTimeStamp
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The current time of the measurement system." "The current time of the system running the IPPM REPORTING MIB
SNMP agent.
When the agent is running in proxy mode is it the current time of the
proxy agent.
When the agent is located in the probe, it is the current time
of the probe agent. "
::= { ippmSystem 1 } ::= { ippmSystem 1 }
ippmSystemSynchronizationType OBJECT-TYPE ippmSystemSynchronizationType OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
other(0), other(0),
ntp(1), ntp(1),
gps(2), gps(2),
cdma(3) cdma(3)
} }
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"ippmSystemSynchronizationType describes the mechanism "ippmSystemSynchronizationType describes the mechanism
used to synchronize the system. used to synchronize the system running the IPPM REPORTING MIB
SNMP agent.
Other(0) Other(0)
The synchronization process must be defined The synchronization process must be defined
in the ippmSystemSynchonizationDescription. in the ippmSystemSynchonizationDescription.
Ntp(1) Ntp(1)
The system is synchronized using the network The system is synchronized using the network
time protocol. The NTP synchronization must be described time protocol. The NTP synchronization must be described
in the ippmSystemSynchonizationDescription. in the ippmSystemSynchonizationDescription.
skipping to change at page 31, line 17 skipping to change at page 25, line 53
Cdma(3) Cdma(3)
The system is synchronized using the CDMA clocks." The system is synchronized using the CDMA clocks."
::= { ippmSystem 2 } ::= { ippmSystem 2 }
ippmSystemSynchronizationDesc OBJECT-TYPE ippmSystemSynchronizationDesc OBJECT-TYPE
SYNTAX SnmpAdminString SYNTAX SnmpAdminString
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The description of the synchronization process." "The description of the synchronization process of the system
running the IPPM REPORTING MIB SNMP agent."
::= { ippmSystem 3 } ::= { ippmSystem 3 }
ippmSystemClockResolution OBJECT-TYPE ippmSystemClockResolution OBJECT-TYPE
SYNTAX Integer32 SYNTAX Integer32
MAX-ACCESS read-only MAX-ACCESS read-only
-- UNITS "picoseconds"
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"ippmSystemClockResolution provides the precision of the clock "ippmSystemClockResolution provides the precision of the clock
used for the measures. The unit is the picosecond. For example, used for the measures. The unit is the picosecond. For example,
the clock on an old Unix host might advance only once every 10 the clock on an old Unix host might advance only once every 10
msec, and thus have a resolution of only 10 msec. So its msec, and thus have a resolution of 10 msec. So its resolution is
resolution is 100000 picosecond and the value of 100000 picosecond and the value of ippmSystemClockResolution is
ippmSystemClockResolution is 100000." 100000."
::= { ippmSystem 4 } ::= { ippmSystem 4 }
ippmSystemCurrentSynchronization OBJECT-TYPE ippmSystemOperationalStatus OBJECT-TYPE
SYNTAX Integer32 SYNTAX INTEGER {
unknown(0),
up(1),
down(2)
}
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The index on the last synchronization event in the "This object describes the status of the system running the IPPM
ippmSynchronizationTable." REPORTING MIB SNMP agent. It does not describe end points measurement
status.
unknown(0)
up(1) means service is operational and available for general use.
down(2) means the proxy is not available for use.
"
::= { ippmSystem 5 } ::= { ippmSystem 5 }
ippmSynchronizationTable OBJECT-TYPE ippmSynchronizationTable OBJECT-TYPE
SYNTAX SEQUENCE OF IppmSynchronizationEntry SYNTAX SEQUENCE OF IppmSynchronizationEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table registers the event related to the synchronization of "This table registers the event related to the synchronization of
the point of measure. Each event is described in an the points of measure. Each event is described in an
ippmSynchronizationEntry. ippmSynchronizationEntry.
ippmSynchronizationTable is mandatory. ippmSynchronizationTable is mandatory.
ippmSynchronizationTable content is read only." ippmSynchronizationTable content is read only."
::= { ippmSystem 6 } ::= { ippmSystem 6 }
ippmSynchronizationEntry OBJECT-TYPE ippmSynchronizationEntry OBJECT-TYPE
SYNTAX IppmSynchronizationEntry SYNTAX IppmSynchronizationEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry describes a modification of the synchronization status. "An entry describes a modification of the synchronization status.
" "
INDEX { ippmSynchronizationIndex } INDEX { ippmPointOfMeasureIndex, ippmSynchronizationIndex }
::= { ippmSynchronizationTable 1 } ::= { ippmSynchronizationTable 1 }
IppmSynchronizationEntry ::= IppmSynchronizationEntry ::=
SEQUENCE { SEQUENCE {
ippmSynchronizationIndex Integer32, ippmSynchronizationIndex Integer32,
ippmSynchronizationTime GMTTimeStamp, ippmSynchronizationTime GMTTimeStamp,
ippmSynchronizationStratum Integer32, ippmSynchronizationStratum Integer32,
ippmSynchronizationResolution Integer32 ippmSynchronizationResolution Integer32
} }
skipping to change at page 33, line 5 skipping to change at page 28, line 5
event occurs." event occurs."
::= { ippmSynchronizationEntry 3 } ::= { ippmSynchronizationEntry 3 }
ippmSynchronizationResolution OBJECT-TYPE ippmSynchronizationResolution OBJECT-TYPE
SYNTAX Integer32 SYNTAX Integer32
UNITS "NanoSeconds" UNITS "NanoSeconds"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The new time resolution computed after the synchronization event "The new time resolution computed after the synchronization event
occured." occurred."
::= { ippmSynchronizationEntry 4 } ::= { ippmSynchronizationEntry 4 }
ippmPointOfMeasureTable OBJECT-TYPE ippmPointOfMeasureTable OBJECT-TYPE
SYNTAX SEQUENCE OF IppmPointOfMeasureEntry SYNTAX SEQUENCE OF IppmPointOfMeasureEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
" A lookup table that identifies the management software in " This table is the list of measurement end points available in
charge of the point of measures. the measurement system.
ippmPointOfMeasureTable content is read only. It means that the Proxy mode:
measurement software handles the table internally It is the list of the measurement end points of the set of probes
for which the IPPM proxy provides an SNMP interface.
IPPM MIB implemented 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." ippmPointOfMeasureTable is mandatory."
::= { ippmSystem 7 } ::= { ippmSystem 7 }
ippmPointOfMeasureEntry OBJECT-TYPE ippmPointOfMeasureEntry OBJECT-TYPE
SYNTAX IppmPointOfMeasureEntry SYNTAX IppmPointOfMeasureEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
" An entry may be the management address of a middleware in " An entry may be the management address of a middleware in
charge of the management of a set of probes. It may the charge of the management of a set of probes. It may the
management address of a probe that contains several line cards. management address of a probe that contains several line cards.
An entry describes the capability of a point of measure. The An entry describes the capability of a point of measure. The
description may make the use of wildcards to define multiple description may make the use of wildcards to define multiple
capabilities." capabilities."
INDEX { ippmPointOfMeasureIndex } INDEX { ippmPointOfMeasureIndex }
::= { ippmPointOfMeasureTable 1 } ::= { ippmPointOfMeasureTable 1 }
IppmPointOfMeasureEntry ::= IppmPointOfMeasureEntry ::= SEQUENCE {
SEQUENCE {
ippmPointOfMeasureIndex Integer32, ippmPointOfMeasureIndex Integer32,
ippmPointOfMeasureMgmtAddrType InetAddressType, ippmPointOfMeasureMgmtAddrType InetAddressType,
ippmPointOfMeasureMgmtAddress InetAddress, ippmPointOfMeasureMgmtAddress InetAddress,
ippmPointOfMeasureTypePAddress TypeP, ippmPointOfMeasureTypePAddress TypeP,
ippmPointOfMeasureAddress InetAddress ippmPointOfMeasureAddress InetAddress,
ippmPointOfMeasureMetrics IppmStandardMetrics
} }
ippmPointOfMeasureIndex OBJECT-TYPE ippmPointOfMeasureIndex OBJECT-TYPE
SYNTAX Integer32 (1 .. 65535) SYNTAX Integer32 (1 .. 65535)
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The index of the entry." "A local index that identifies an entry of the points of measures
table."
::= { ippmPointOfMeasureEntry 1 } ::= { ippmPointOfMeasureEntry 1 }
ippmPointOfMeasureMgmtAddrType OBJECT-TYPE ippmPointOfMeasureMgmtAddrType OBJECT-TYPE
SYNTAX InetAddressType SYNTAX InetAddressType
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The type of address associated with management address" "The address type associated with the management address."
::= { ippmPointOfMeasureEntry 2 } ::= { ippmPointOfMeasureEntry 2 }
ippmPointOfMeasureMgmtAddress OBJECT-TYPE ippmPointOfMeasureMgmtAddress OBJECT-TYPE
SYNTAX InetAddress (SIZE (1..128)) SYNTAX InetAddress (SIZE (1..128))
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The management address on the point of measure" "The management address on the point of measure"
::= { ippmPointOfMeasureEntry 3 } ::= { ippmPointOfMeasureEntry 3 }
ippmPointOfMeasureTypePAddress OBJECT-TYPE ippmPointOfMeasureTypePAddress OBJECT-TYPE
SYNTAX TypeP SYNTAX TypeP
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Defines the type P of the address of the point of measure." "Defines the type P address of the point of measure."
DEFVAL { "ip" } DEFVAL { "ip" }
::= { ippmPointOfMeasureEntry 4 } ::= { ippmPointOfMeasureEntry 4 }
ippmPointOfMeasureAddress OBJECT-TYPE ippmPointOfMeasureAddress OBJECT-TYPE
SYNTAX InetAddress SYNTAX InetAddress
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Specifies the address of the point of measure. "Specifies the address of the point of measure.
It is represented as an octet string with specific semantics and It is represented as an octet string with specific semantics and
length as identified by the ippmPointOfMeasureTypePAddress. length as identified by the ippmPointOfMeasureTypePAddress.
For example, if the ippmPointOfMeasureTypePAddress indicates an For example, if the ippmPointOfMeasureTypePAddress indicates an
encapsulation of 'ip', this object length is 4, followed by the 4 encapsulation of 'ip', this object length is 4, followed by the 4
octets of the IP address, in network byte order." octets of the IP address, in network byte order."
::= { ippmPointOfMeasureEntry 5} ::= { ippmPointOfMeasureEntry 5}
ippmPointOfMeasureMetrics OBJECT-TYPE
SYNTAX IppmStandardMetrics
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Metrics supported by this point of measure."
::= { ippmPointOfMeasureEntry 6 }
ippmMetricTable OBJECT-TYPE
SYNTAX SEQUENCE OF IppmMetricEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This table is mandatory. It describes the current
implementation. Each IPPM standardized metric must be described
in the table.
ippmMetricTable content is read only."
::= { ippmSystem 8 }
ippmMetricEntry OBJECT-TYPE
SYNTAX IppmMetricEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry describes the static capabilities of a metric
implementation."
INDEX { ippmMetricIndex }
::= { ippmMetricTable 1 }
IppmMetricEntry ::=
SEQUENCE {
ippmMetricIndex Integer32,
ippmMetricCapabilities INTEGER,
ippmMetricType INTEGER,
ippmMetricUnit INTEGER,
ippmMetricDescription SnmpAdminString
}
ippmMetricIndex OBJECT-TYPE
SYNTAX Integer32 (1.. 65535)
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"ippmMetricIndex defines an unambiguous index for each
standardized metric. It identifies a metric. Its value is the
value of the node of the metric in an IPPM registry. This value
is the same in any implementation of the IPPM REPORTING 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 IppmMetricTable will always be '14'"
::= { ippmMetricEntry 1 }
ippmMetricCapabilities OBJECT-TYPE
SYNTAX INTEGER {
notImplemented(0),
implemented(1)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"A value of notImplemented implies the metric is not implemented.
A value of implemented implies the metric is implemented either
in the proxy or the point of measure itself.
Example: if the aggregated metric is not implemented in the point
of measure it may be implemented in the proxy."
DEFVAL { implemented }
::= { ippmMetricEntry 2 }
ippmMetricType OBJECT-TYPE
SYNTAX INTEGER {
network(0),
aggregated(1)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Indicates the metric type, whether it is network or aggregated"
DEFVAL { aggregated }
::= { ippmMetricEntry 3 }
ippmMetricUnit OBJECT-TYPE
SYNTAX INTEGER {
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
"The unit used in the current entity for the results of the
measurement of this metric."
::= { ippmMetricEntry 4 }
ippmMetricDescription 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 the registry. For example:
oneWayDelay: text ."
::= { ippmMetricEntry 5 }
-- --
-- ippmOwners Group -- ippmOwners Group
-- --
-- The ippmOwners objects are responsible for managing -- The ippmOwners objects are responsible for managing
-- the owners access to the measurements. -- the owners access to the measurements.
-- --
-- --
ippmOwnersTable OBJECT-TYPE ippmOwnersTable OBJECT-TYPE
SYNTAX SEQUENCE OF IppmOwnersEntry SYNTAX SEQUENCE OF IppmOwnersEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A management entity wishing to create and activate remote Ippm "A management entity wishing to create and activate remote Ippm
measurements in an agent must previously be registered in the measurements in an agent must previously be registered in the
ippmOwnersTable. ippmOwnersTable.
ippmOwnersTable content is read-create. It contains at least the ippmOwnersTable content is read-create. It contains at least the
owner 'monitor'. It is mandatory, except if the VACM framework is owner 'monitor'.
used."
::= { ippmOwners 1 } ::= { ippmOwners 1 }
ippmOwnersEntry OBJECT-TYPE ippmOwnersEntry OBJECT-TYPE
SYNTAX IppmOwnersEntry SYNTAX IppmOwnersEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The description of the resources granted to an SNMP application. "The description of the resources granted to an SNMP application.
For example, an instance of ippmOwnersOwner with an For example, an instance of ippmOwnersOwner with an
IppmOwnerString 'acme', which represents the 14th owner created IppmOwnerString 'acme', which represents the 14th owner created
in ippmOwnersTable would be named ippmOwnersEntryOwner.14. in ippmOwnersTable would be named ippmOwnersEntryOwner.14.
Notes: Notes:
The ippmOwnersIndex value is a local index managed directly by The ippmOwnersIndex value is a local index managed directly by
the agent. The management application must poll to get the next the agent. The management application must poll to get the next
available index value. available index value.
It is not used in anyway in the other IPPM tables." It is not used in anyway in other IPPM tables."
INDEX { ippmOwnersIndex } INDEX { ippmOwnersIndex }
::= { ippmOwnersTable 1 } ::= { ippmOwnersTable 1 }
IppmOwnersEntry ::= SEQUENCE { IppmOwnersEntry ::= SEQUENCE {
ippmOwnersIndex Integer32, ippmOwnersIndex Integer32,
ippmOwnersOwner SnmpAdminString, ippmOwnersOwner IppmOwnerString,
ippmOwnersGrantedMetrics IppmStandardMetrics, ippmOwnersGrantedMetrics IppmStandardMetrics,
ippmOwnersGrantedRules BITS, ippmOwnersQuota Integer32,
ippmOwnersIpAddressType InetAddressType, ippmOwnersIpAddressType InetAddressType,
ippmOwnersIpAddress InetAddress, ippmOwnersIpAddress InetAddress,
ippmOwnersEmail SnmpAdminString, ippmOwnersEmail SnmpAdminString,
ippmOwnersSMS SnmpAdminString, ippmOwnersSMS SnmpAdminString,
ippmOwnersStatus RowStatus ippmOwnersStatus RowStatus
} }
ippmOwnersIndex OBJECT-TYPE ippmOwnersIndex OBJECT-TYPE
SYNTAX Integer32 (1.. 65535) SYNTAX Integer32 (1.. 65535)
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An arbitrary index that identifies an entry in this table" "An arbitrary index that identifies an entry in the owners
table."
::= { ippmOwnersEntry 1 } ::= { ippmOwnersEntry 1 }
ippmOwnersOwner OBJECT-TYPE ippmOwnersOwner OBJECT-TYPE
SYNTAX SnmpAdminString SYNTAX IppmOwnerString
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The owner described by this entry." "The owner described by this entry."
::= { ippmOwnersEntry 2 } ::= { ippmOwnersEntry 2 }
ippmOwnersGrantedMetrics OBJECT-TYPE ippmOwnersGrantedMetrics OBJECT-TYPE
SYNTAX IppmStandardMetrics SYNTAX IppmStandardMetrics
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
" Defines the metrics granted to an owner." " Defines the metrics granted to an owner for which measurements
can be performed."
::= { ippmOwnersEntry 3 } ::= { ippmOwnersEntry 3 }
ippmOwnersGrantedRules OBJECT-TYPE ippmOwnersQuota OBJECT-TYPE
SYNTAX BITS { SYNTAX Integer32
all(0),
readonly(1),
permanent(2),
sender(3),
receiver(4),
report(5),
alarm(6)
}
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Defines the rules this owner may act on in the current IPPM MIB " The maximum number of records that this owner may have in the history
instance. table and/or in the report table.
all(0):
The owner is granted all the rules.
readonly(1):
The measures (not only the metrics) that this owner may access
are setup by the manager of the point of measure. The owner can
not add new measures for these metrics. The creation and the
configuration of the measures corresponding to these metrics are
managed by the manager of the point of measure.
permanent(2):
The measures (not only the metrics) that this owner may access
are determined by the manager of the point of measure. The owner
can not add new measures for these metrics. The creation and the
first configuration of the measures corresponding to these
metrics are managed by the manager of the point of measure. The
owner may modify the measures parameters of the entries of the
corresponding ippmMeasureEntry whose access is read-write.
Typically this allows the owner to suspend the measures, to
change the beginning and end of the measures.
sender(3):
The owner may only activate measures for those metrics that send
packets from the current point of measure. This flag is only
suitable for network measures. It shall be ignored for derived
metrics.
receiver(4):
The owner may only activate measures for those metrics that
receive packets on the current point of measure. This flag is
only suitable for network measures. It shall be ignored for
derived metrics. Such control increases the security. The owner
may not generate packets from the probe.
report(5):
The owner may setup aggregated metrics on the measures
corresponding to these metrics.
alarm(6):
The owner may setup alarms on the results of the measures
metrics.
e.g.:
if the owner Acme is granted with the metric Instantaneous-
Unidirectional-Connectivity as a Receiver in the current point of
measure, then Acme can not setup a Instantaneous-Unidirectional-
Connectivity to another point of measure."
DEFVAL { 1 }
::= { ippmOwnersEntry 4 } ::= { ippmOwnersEntry 4 }
ippmOwnersIpAddressType OBJECT-TYPE ippmOwnersIpAddressType OBJECT-TYPE
SYNTAX InetAddressType SYNTAX InetAddressType {
ipv4(1) ,
ipv6(2),
dns(16)
}
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The IP address type of the management entity corresponding to "The IP address type of the management entity corresponding to
this owner." this owner.
InetAddressType is restricted to ipv4(1),ipv6(2)and dns(16). "
::= { ippmOwnersEntry 5 } ::= { ippmOwnersEntry 5 }
ippmOwnersIpAddress OBJECT-TYPE ippmOwnersIpAddress OBJECT-TYPE
SYNTAX InetAddress (SIZE (1..128)) SYNTAX InetAddress (SIZE (1..128))
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The IP address of the management entity corresponding to this "The IP address of the management entity corresponding to this
owner. The address is human readable and is represented using the owner."
dot format."
::= { ippmOwnersEntry 6 } ::= { ippmOwnersEntry 6 }
ippmOwnersEmail OBJECT-TYPE ippmOwnersEmail OBJECT-TYPE
SYNTAX SnmpAdminString SYNTAX SnmpAdminString
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The email address of the management entity corresponding to this "The email address of the management entity corresponding to this
owner." owner."
::= { ippmOwnersEntry 7 } ::= { ippmOwnersEntry 7 }
skipping to change at page 38, line 25 skipping to change at page 35, line 13
::= { ippmOwnersEntry 8 } ::= { ippmOwnersEntry 8 }
ippmOwnersStatus OBJECT-TYPE ippmOwnersStatus OBJECT-TYPE
SYNTAX RowStatus SYNTAX RowStatus
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The status of this table entry." "The status of this table entry."
::= { ippmOwnersEntry 9 } ::= { ippmOwnersEntry 9 }
-- ippmHistory Group
-- --
-- ippmResultSharingTable
-- --
ippmResultSharingTable OBJECT-TYPE --
SYNTAX SEQUENCE OF IppmResultSharingEntry -- ippmHistoryTable
MAX-ACCESS not-accessible --
STATUS current
DESCRIPTION
" The ippmResultSharingTable controls the access of an owner to
the measure results of other owners. An owner may grant another
access to read the result of its measure.
Entries may exist in ippmResultSharingTable even if the measures
to be shared are not yet defined. Deleting a measure entry in the
ippmMeasureTable does not delete the entries corresponding to
this measure in the ippmResultSharingTable. This table is
optional.
ippmResultSharingTable content is read-create.
If this table is not implemented then the owner has only access
to its own measurement results."
::= { ippmOwners 2 }
ippmResultSharingEntry OBJECT-TYPE
SYNTAX IppmResultSharingEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry allows an owner to read the results of a measure owned
by another owner.
It permits 2 typical usages:
1) Creating derived measurements on these results
2) Reading the results from a remote management station.
Example: if acme.12 is a One-way-Delay(6) measure, Acme may allow
Peter to make derived metrics on the results of this measure."
INDEX { ippmResultSharingOwner, ippmResultSharingIndex}
::= { ippmResultSharingTable 1 }
IppmResultSharingEntry ::= SEQUENCE { ippmHistoryTable OBJECT-TYPE
ippmResultSharingOwner IppmOwnerString, SYNTAX SEQUENCE OF IppmHistoryEntry
ippmResultSharingIndex Integer32,
ippmResultSharingMeasureOwner IppmOwnerString,
ippmResultSharingMeasureIndex Integer32,
ippmResultSharingGrantedOwner IppmOwnerString,
ippmResultSharingStatus RowStatus
}
ippmResultSharingOwner OBJECT-TYPE
SYNTAX IppmOwnerString
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
" The owner of this result control entry. Typically the owner who "The table containing the measurement results."
created this conceptual row." ::= { ippmHistory 1 }
::= { ippmResultSharingEntry 1 }
ippmResultSharingIndex OBJECT-TYPE ippmHistoryEntry OBJECT-TYPE
SYNTAX Integer32 (1.. 65535) SYNTAX IppmHistoryEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
" The index of this result control entry. The value is managed by "An ippmHistoryEntry entry is one of the results of a measure
the owner. On creation a SNMP error 'inconsistentValue' is identified by ippmHistoryMeasureOwner, ippmHistoryMeasureIndex,
returned if this value is already in use by this owner." ippmHistoryMetricIndex and ippmHistoryIndex.
::= { ippmResultSharingEntry 2 }
ippmResultSharingMeasureOwner OBJECT-TYPE
SYNTAX IppmOwnerString
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The owner of the measure to be shared. The couple
ippmResultSharingMeasureOwner, ippmResultSharingMeasureIndex
identifies absolutely a measure"
::= { ippmResultSharingEntry 3 }
ippmResultSharingMeasureIndex OBJECT-TYPE In the index :
SYNTAX Integer32 (1.. 65535)
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The index of the measure to be shared."
::= { ippmResultSharingEntry 4 }
ippmResultSharingGrantedOwner OBJECT-TYPE + ippmHistoryMeasureOwner identifies the owner of the measure;
SYNTAX IppmOwnerString
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The owner who is granted access to the result of the measure + ippmHistoryMeasureIndex identifies the measure in the owner
described by the couple ippmResultSharingMeasureOwner, namespace;
ippmResultSharingMeasureIndex."
::= { ippmResultSharingEntry 5 }
ippmResultSharingStatus OBJECT-TYPE + ippmHistoryMetricIndex identifies the metric measured by the
SYNTAX RowStatus measure. The metric is described in the corresponding entry of
MAX-ACCESS read-create the n ippmMetricTable;
STATUS current
DESCRIPTION
" The status of this table entry. Once the entry status is set to
active."
::= { ippmResultSharingEntry 6 }
-- + ippmHistoryIndex is the local index of the result on the
history table."
INDEX { ippmHistoryMeasureOwner, ippmHistoryMeasureIndex,
ippmHistoryMetricIndex, ippmHistoryIndex }
::= { ippmHistoryTable 1 }
-- IppmHistoryEntry ::=
-- SEQUENCE {
-- ippmMeasure Group ippmHistoryMeasureOwner IppmOwnerString,
-- ippmHistoryMeasureIndex Integer32,
-- ippmHistoryMetricIndex Integer32,
-- ippmHistoryIndex Integer32,
ippmHistorySequence Integer32,
ippmHistoryTimestamp GMTTimeStamp,
ippmHistoryValue Integer32
}
ippmMetricTable OBJECT-TYPE ippmHistoryMeasureOwner OBJECT-TYPE
SYNTAX SEQUENCE OF IppmMetricEntry SYNTAX IppmOwnerString
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table describes the current implementation and is "The owner of the measure that produced this result."
mandatory. Each IPPM standardized metric must be described in the ::= { ippmHistoryEntry 1 }
table.
In reporting mode, the entries of this table may be not
accessible. It means that the measurement software handles the
table internally.
ippmMetricTable is mandatory.
ippmMetricTable content is read only."
::= { ippmMeasure 1 }
ippmMetricEntry OBJECT-TYPE ippmHistoryMeasureIndex OBJECT-TYPE
SYNTAX IppmMetricEntry SYNTAX Integer32 (1.. 65535)
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry describes the static capabilities of a metric " The owner index of the measure that produced this result."
implementation." ::= { ippmHistoryEntry 2 }
INDEX { ippmMetricIndex }
::= { ippmMetricTable 1 }
IppmMetricEntry ::=
SEQUENCE {
ippmMetricIndex Integer32,
ippmMetricCapabilities INTEGER,
ippmMetricUnit INTEGER,
ippmMetricDescription SnmpAdminString,
ippmMetricMaxHistorySize Integer32
}
ippmMetricIndex OBJECT-TYPE ippmHistoryMetricIndex OBJECT-TYPE
SYNTAX Integer32 (1.. 65535) SYNTAX Integer32 (1.. 65535)
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"ippmMetricIndex defines an unambiguous index for each " ippmHistoryMetricIndex identifies the metric measured by the
standardized metric. Its value is the value of the node of the measure. The metric is described in the corresponding entry of
metric in the IPPM-REPORTING-MIB metrics registry the ippmMetricTable."
ippmMib.metrics.rfc. ::= { ippmHistoryEntry 3 }
Each metric registered in the standard registry must be present
in this table.
This index is used to identify the metric calculated between the
IPPM-REPORTING-MIB entities involved in the measure.
Example:
The index of the metric onewayPacketLossAverage which is
registered as ippmMib.metrics.rfc.onewayPacketLossAverage will
always have the value 14."
::= { ippmMetricEntry 1 }
ippmMetricCapabilities OBJECT-TYPE ippmHistoryIndex OBJECT-TYPE
SYNTAX INTEGER { SYNTAX Integer32 (1.. 65535)
notImplemented(0), MAX-ACCESS not-accessible
implemented(1)
}
MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A value of notImplemented implies the metric is not implemented. " A local index that identifies a result in the history table."
A value of implemented implies the metric is implemented." ::= { ippmHistoryEntry 4 }
DEFVAL { implemented }
::= { ippmMetricEntry 2 }
ippmMetricUnit OBJECT-TYPE ippmHistorySequence OBJECT-TYPE
SYNTAX INTEGER { SYNTAX Integer32 (0.. 65535)
noUnit(0),
second(1),
ms(2),
us(3),
ns(4),
percentage(5),
packets(6),
byte(7),
kbyte(8),
megabyte(9)
}
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The unit used in the current entity for the results of the "ippmHistorySequence is the sequence index of the measurement
measurement of this metric." results for a metric.
::= { ippmMetricEntry 3 }
ippmMetricDescription OBJECT-TYPE Network metrics:
SYNTAX SnmpAdminString It's the sequence index of a measurement packet. Typically, it
identifies the order of the packet in the stream of packets sends
by the source.
Aggregated metrics:
It is the sequence index of the computed aggregated metric
result."
::= { ippmHistoryEntry 5 }
ippmHistoryTimestamp OBJECT-TYPE
SYNTAX GMTTimeStamp
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A textual description of the metric implementation." "The timestamp when the measurement occured."
::= { ippmMetricEntry 4 } ::= { ippmHistoryEntry 6 }
ippmMetricMaxHistorySize OBJECT-TYPE ippmHistoryValue OBJECT-TYPE
SYNTAX Integer32 SYNTAX Integer32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Specifies the maximum number of results that a metric measure "The observed value of the measurement."
can save in the ippmHistoryTable." ::= { ippmHistoryEntry 7 }
DEFVAL { 200 }
::= { ippmMetricEntry 5 }
-- --
-- ippmMeasureTable -- ippmMeasure Group
--
--
--
-- ippmNetMeasureTable
-- --
-- --
ippmMeasureTable OBJECT-TYPE ippmNetMeasureTable OBJECT-TYPE
SYNTAX SEQUENCE OF IppmMeasureEntry SYNTAX SEQUENCE OF IppmNetMeasureEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The table of all the IPPM measures which are running in the "A entry is a measurement that performs network measures and
device. They may not all be active. provides results.
It performs several metric measurements per packet exchange. Each
A measure consists of a subset of metrics to compute. The results step of a measure produces a singleton result per metric. The
of the measure may be saved in the ippmHistoryTable. The time of the measurement and the value of the metric are saved in
configuration of the measure sets the size of the history the ippmHistoryTable."
requested in ippmMeasureHistorySize. ::= { ippmMeasure 1 }
The maximum number of MIB objects to be collected in the portion
of ippmHistoryTable associated with this metric depends on the
value of the ippmMetricMaxHistorySize.
The value of each metric ippmMeasureHistorySize must not be over ippmNetMeasureEntry OBJECT-TYPE
the value of ippmMetricMaxHistorySize corresponding to this SYNTAX IppmNetMeasureEntry
metric in the ippmMetricTable. MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
" Typically the configuration operation sets both the values of
the new IppmNetMeasureEntry.
The IppmNetMeasureTable is mandatory.
The ippmMeasureTable is mandatory. The IppmNetMeasureTable content is read only. It means that the
measurement software handles the table internally. The setup of
the network measure is not permitted through the IPPM REPORTING
MIB. OWAP provides a setup protocol to enable and teardown
networks measures.
ippmMeasureTable content is read-create. The table is handled The ippmNetMeasureMetrics is set to a list of metrics to be
internally by the measurement software for network measures. computed from the same raw packet exchange. Each step of
measurement delivers a singleton per chosen metric. Results are
timestamped and saved in the ippmHistoryTable.
The setup of network is not permitted through the IPPM REPORTING The ippmNetMeasureTable typical usage consists in providing
MIB. OWAP provides a setup protocol to enable and teardown network measure indices in order to allow aggregated measures to
networks measures." perform aggregation on the results of network measures.
::= { ippmMeasure 2 }
ippmMeasureEntry OBJECT-TYPE INDEX { ippmNetMeasureOwner, ippmNetMeasureIndex }
SYNTAX IppmMeasureEntry ::= { ippmNetMeasureTable 1 }
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The measure entries are created/deleted internally by the
measurement software."
INDEX { ippmMeasureOwner, ippmMeasureIndex }
::= { ippmMeasureTable 1 }
IppmMeasureEntry ::= IppmNetMeasureEntry ::= SEQUENCE {
SEQUENCE { ippmNetMeasureOwner IppmOwnerString,
ippmMeasureOwner IppmOwnerString, ippmNetMeasureIndex Integer32,
ippmMeasureIndex Integer32, ippmNetMeasureName SnmpAdminString,
ippmMeasureName SnmpAdminString, ippmNetMeasureMetrics IppmStandardMetrics,
ippmMeasureMetrics IppmStandardMetrics, ippmNetMeasureBeginTime GMTTimeStamp,
ippmMeasureBeginTime GMTTimeStamp, ippmNetMeasureCollectionRateUnit TimeUnit,
ippmMeasureClockPeriodUnit TimeUnit, ippmNetMeasureCollectionRate Integer32,
ippmMeasureClockPeriod Integer32, ippmNetMeasureDurationUnit TimeUnit,
ippmMeasureDurationUnit TimeUnit, ippmNetMeasureDuration Integer32,
ippmMeasureDuration Integer32, ippmNetMeasureHistorySize Integer32,
ippmMeasureHistorySize Integer32, ippmNetMeasureFailureMgmtMode INTEGER,
ippmMeasureStorageType StorageType, ippmNetMeasureResultsMgmt Integer32,
ippmMeasureStatus RowStatus ippmNetMeasureSrcTypeP TypeP,
ippmNetMeasureSrc TypePaddress,
ippmNetMeasureDstTypeP TypeP,
ippmNetMeasureDst TypePaddress,
ippmNetMeasureTxMode Integer32,
ippmNetMeasureTxPacketRateUnit Integer32,
ippmNetMeasureTxPacketRate INTEGER,
ippmNetMeasureDevtnOrBurstSize Integer32,
ippmNetMeasureMedOrIntBurstSize Integer32,
ippmNetMeasureLossTimeout Integer32,
ippmNetMeasureL3PacketSize Integer32,
ippmNetMeasureDataPattern OCTET STRING,
ippmNetMeasureMap SnmpAdminString,
ippmNetMeasureSingletons INTEGER,
ippmNetMeasureOperState INTEGER
} }
ippmMeasureOwner OBJECT-TYPE ippmNetMeasureOwner OBJECT-TYPE
SYNTAX IppmOwnerString SYNTAX IppmOwnerString
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The owner who has configured this entry." "The owner of the network measurement."
::= { ippmMeasureEntry 1 } ::= { ippmNetMeasureEntry 1 }
ippmMeasureIndex OBJECT-TYPE ippmNetMeasureIndex OBJECT-TYPE
SYNTAX Integer32 (1.. 65535) SYNTAX Integer32 (1.. 65535)
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The owner index of the measure. The value is managed by the "The owner index of the network measure. "
owner." ::= { ippmNetMeasureEntry 2 }
::= { ippmMeasureEntry 2 }
ippmMeasureName OBJECT-TYPE ippmNetMeasureName OBJECT-TYPE
SYNTAX SnmpAdminString SYNTAX SnmpAdminString
MAX-ACCESS read-create MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The name of the instance of the metric. It illustrates the "The name of the metric instance. It illustrates the specificity
specificity of the metric and includes the metric and the typeP. of the metric and includes the metric and the TypeP.
example: IP-port-HTTP-connectivity" Example:
::= { ippmMeasureEntry 3 } IP-TCP-HTTP-One-way-Delay: free text "
::= { ippmNetMeasureEntry 3 }
ippmMeasureMetrics OBJECT-TYPE ippmNetMeasureMetrics OBJECT-TYPE
SYNTAX IppmStandardMetrics SYNTAX IppmStandardMetrics
MAX-ACCESS read-create MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Defines the metrics to compute within this measure. A measure "Defines the metrics to compute within this measure. ONLY network
may be configured for the result of different metric singletons metrics of the same type are allowed in this field.
to be archived in the ippmHistoryTable. The ippmMetricIndex of A measure may be configured for the result of different metric
the created result has the value of the bit index of the singletons to be archived in the ippmHistoryTable. The
corresponding ippmMeasureMetrics as explained above in the ippmMetricIndex of the created result has the value of the bit
ippmMetricIndex definition. index of the corresponding ippmMeasureMetrics as explained above
in the ippmMetricIndex definition.
Example: Example:
A measure asking for One-way-Delay(6) and One-way-Packet-Loss(12) A measure asking for One-way-Delay(6) and One-way-Packet-Loss(12)
generated a flow of singletons which are logged in the generated a flow of singletons which are logged in the
ippmHistoryTable. The singletons created for the One-way-Delay ippmHistoryTable. The singletons created for the One-way-Delay
measure have a value of ippmMetricIndex of 6 while the created measure have a value of ippmMetricIndex of 6 while the created
singletons for the One-way-Packet-Loss measure have a value of singletons for the One-way-Packet-Loss measure have a value of
ippmMetricIndex of 12." ippmMetricIndex of 12.
One measure may perform simultaneously
either several network metrics
either several aggregated metrics
"
-- { one-way-Delay, one-way-Packet-Loss } -- { one-way-Delay, one-way-Packet-Loss }
DEFVAL { '0001000001000000'b } DEFVAL { 0000001000001 }
::= { ippmMeasureEntry 4 } ::= { ippmNetMeasureEntry 4 }
ippmMeasureBeginTime OBJECT-TYPE ippmNetMeasureBeginTime OBJECT-TYPE
SYNTAX GMTTimeStamp SYNTAX GMTTimeStamp
MAX-ACCESS read-create MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Specifies the time at which the measure starts." "Specifies the time at which the measurement begins."
::= { ippmMeasureEntry 5 } ::= { ippmNetMeasureEntry 5 }
ippmMeasureClockPeriodUnit OBJECT-TYPE ippmNetMeasureCollectionRateUnit OBJECT-TYPE
SYNTAX TimeUnit SYNTAX TimeUnit
MAX-ACCESS read-create MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Specifies the unit of the measure period." "Specifies the unit of the measurement period."
DEFVAL { second } DEFVAL { second }
::= { ippmMeasureEntry 6 } ::= { ippmNetMeasureEntry 6 }
ippmMeasureClockPeriod OBJECT-TYPE ippmNetMeasureCollectionRate OBJECT-TYPE
SYNTAX Integer32 SYNTAX Integer32
MAX-ACCESS read-create MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Specifies the amount of time between 2 measurement action "Gives the period used to collect singletons from the point of
intervals. The action is specific to the semantic of the measure. measures.
This value is used as the cycle period in the report."
Network metrics:
The ippmNetworkMeasureClockPattern transforms the flow of
periodical instants as a flow of unpredictable instants of
measurement packet emission.
As the source and the sink share the definition of the clock of
the measure, as the sending timestamp is part of the measurement
packet, the sink have the information to verify that the stream
of packets generated by the source respects the clock law.
Aggregated metrics:
They are performed periodically on a sequence of results of other
measures. The period corresponds to the interval between two
successive computations of the metric. The value of
ippmHistoryTimestamp result of a aggregated metric computed
corresponds to the value of the ippmHistoryTimestamp of the last
metric result of the sequence used in to compute the aggregated
metric."
DEFVAL { 60 } DEFVAL { 60 }
::= { ippmMeasureEntry 7 } ::= { ippmNetMeasureEntry 7 }
ippmMeasureDurationUnit OBJECT-TYPE ippmNetMeasureDurationUnit OBJECT-TYPE
SYNTAX TimeUnit SYNTAX TimeUnit
MAX-ACCESS read-create MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Specifies the unit of the measure duration." "Specifies the measurement duration unit."
DEFVAL { second } DEFVAL { second }
::= { ippmMeasureEntry 8 } ::= { ippmNetMeasureEntry 8 }
ippmMeasureDuration OBJECT-TYPE ippmNetMeasureDuration OBJECT-TYPE
SYNTAX Integer32 SYNTAX Integer32
MAX-ACCESS read-create MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Specifies the duration of the measure." "Specifies the measurement duration."
DEFVAL { 120 } DEFVAL { 120 }
::= { ippmMeasureEntry 9 } ::= { ippmNetMeasureEntry 9 }
ippmMeasureHistorySize OBJECT-TYPE ippmNetMeasureHistorySize OBJECT-TYPE
SYNTAX Integer32 SYNTAX Integer32
MAX-ACCESS read-create MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Specifies the maximum number of results saved for each metric of "Specifies the maximum number of results saved for each metric of
this measure. The history of each metric is managed as a circular this measure.
table. The newest result overwrites the oldest one when the Overflow condition will be managed by the object
history granted to this metric measure is full. ippmNetMeasureResultsMgmt. "
The management of the results may be optimized if synchronized ::= { ippmNetMeasureEntry 10 }
with the reports steps of this measure. "
DEFVAL { 120 }
::= { ippmMeasureEntry 10 }
ippmMeasureStorageType OBJECT-TYPE ippmNetMeasureFailureMgmtMode OBJECT-TYPE
SYNTAX StorageType SYNTAX INTEGER {
MAX-ACCESS read-create auto(1),
manual(2),
discarded(3)
}
MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object defines whether this row and the measure controlled "This object defines whether this row and the measure controlled
by this row are kept in volatile storage and lost upon reboot or by this row are kept in volatile storage and lost upon reboot or
if this row is backed up if this row is backed up
by non-volatile or permanent storage. by non-volatile or permanent storage.
Possible values are: other(1), volatile(2), nonVolatile(3), 'auto'
permanent(4), readOnly(5)" continue the measurement and erase the older entries in the
DEFVAL { nonVolatile } history.
::= { ippmMeasureEntry 11 } 'manual'
continue the measurement and erase the older entries in the
ippmMeasureStatus OBJECT-TYPE history.
SYNTAX RowStatus 'discarded'
MAX-ACCESS read-create continue the measurement and erase the older entries in the
STATUS current history.
DESCRIPTION
"The status of this table entry. Once the entry status is set to
active, the associate entry cannot be modified."
::= { ippmMeasureEntry 12 }
--
-- ippmHistory Group
--
--
--
-- ippmHistoryTable
--
ippmHistoryTable OBJECT-TYPE
SYNTAX SEQUENCE OF IppmHistoryEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The table of the results of the measures."
::= { ippmHistory 1 }
ippmHistoryEntry OBJECT-TYPE
SYNTAX IppmHistoryEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An ippmHistoryEntry entry is one of the results of a measure
identified by ippmMeasureOwner, ippmMeasureIndex, ippmMetricIndex
and ippmHistoryIndex.
In the index :
+ ippmMeasureOwner identifies the owner of the measure;
+ ippmMeasureIndex identifies the measure in the owner namespace;
+ ippmMetricIndex identifies the metric measured in
ippmMetricTable;
+ ippmHistoryIndex is the local index of the result on the
history table."
INDEX { ippmMeasureOwner, ippmMeasureIndex, ippmMetricIndex,
ippmHistoryIndex }
::= { ippmHistoryTable 1 }
IppmHistoryEntry ::=
SEQUENCE {
ippmHistoryIndex Integer32,
ippmHistorySequence Integer32,
ippmHistoryTimestamp GMTTimeStamp,
ippmHistoryValue Integer32
}
ippmHistoryIndex OBJECT-TYPE
SYNTAX Integer32 (1.. 65535)
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
" A local index that only identifies a result in the history
table."
::= { ippmHistoryEntry 1 }
ippmHistorySequence OBJECT-TYPE
SYNTAX Integer32 (1.. 65535)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"ippmHistorySequence is the sequence index of the measurement
results of the measure of a metric.
Network metrics:
It's the sequence index of a measurement packet. Typically, it
identifies the order of the packet in the stream of packets sends
by the source.
Aggregated metrics: Possible values are: other(1), volatile(2), nonVolatile(3),
It is the sequence index of the aggregated metric results permanent(4)
computed."
::= { ippmHistoryEntry 2 }
ippmHistoryTimestamp OBJECT-TYPE
SYNTAX GMTTimeStamp
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The instant of the measure of the result."
::= { ippmHistoryEntry 3 }
ippmHistoryValue OBJECT-TYPE Network: "
SYNTAX Integer32 DEFVAL { auto }
MAX-ACCESS read-only ::= { ippmNetMeasureEntry 11 }
STATUS current
DESCRIPTION
"The value of the measure."
::= { ippmHistoryEntry 4 }
ippmOnHistoryFullAction OBJECT-TYPE ippmNetMeasureResultsMgmt OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
wrap(1), wrap(1),
suspend(2), suspend(2),
resume(3) delete(3)
} }
MAX-ACCESS read-write MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Action to take when the history log is full. The user may choose "
Action to take when the log is full. The user may choose
to either wrap, in which case the agent writes over existing to either wrap, in which case the agent writes over existing
records. The user may choose to suspend writing to the log in the records. The user may choose to suspend writing to the log in the
event that he wishes to archive the data. The resume action event that he wishes to archive the data. The resume action
causes the agent to begin to write in the history log, and causes the agent to begin to write in thelog, and assumes the
assumes the data has been cleared." data has been cleared.
::= { ippmHistory 2 } This object indicates the way the measurement results are managed
when the owner quota has been exceeded:
-- 'wrap'
-- ippmNetworkMeasure Group continue the measurement and erase the older entries in the
-- history.
'suspend'
-- stop the measure and keep the results in the history.
-- 'delete'
-- ippmNetworkMeasureTable remove the results from the history.
-- "
-- ::= { ippmNetMeasureEntry 12 }
ippmNetworkMeasureTable OBJECT-TYPE
SYNTAX SEQUENCE OF IppmNetworkMeasureEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A entry is a measure which performs network measures and
provides a flow of results.
This table extends the ippmMeasureTable.
It performs several metric measurements per packet exchange. Each
step of a measure produces a singleton result per metric. The
time of the measure and the value of the metric are saved in the
ippmHistoryTable."
::= { ippmNetworkMeasure 1 }
ippmNetworkMeasureEntry OBJECT-TYPE
SYNTAX IppmNetworkMeasureEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
" Typically the configuration operation sets both the values of
the new ippmMeasureEntry and of the new IppmNetworkMeasureEntry.
IppmNetworkMeasureTable is mandatory.
IppmNetworkMeasureTable content is read only. It means that the
measurement software handles the table internally. The setup of
network is not permitted through the IPPM REPORTING MIB. OWAP
provides a setup protocol to enable and teardown networks
measures.
The ippmMeasureMetrics is set to a list of metrics to be computed
from the same raw packet exchange. Each step of measurement
delivers a singleton per chosen metric. Results are timestamped
and saved in the ippmHistoryTable.
The ippmNetworkMeasureTable typical usage consists is providing
network measure indexes to permits aggregated measure to perform
aggregation on the results of network measures.
An obvious usage of the ippmNetworkMeasureTable consists in the
verification of the network measures states."
INDEX { ippmMeasureOwner, ippmMeasureIndex }
::= { ippmNetworkMeasureTable 1 }
IppmNetworkMeasureEntry ::=
SEQUENCE {
ippmNetworkMeasureSrcTypeP TypeP,
ippmNetworkMeasureSrc TypePaddress,
ippmNetworkMeasureDstTypeP TypeP,
ippmNetworkMeasureDst TypePaddress,
ippmNetworkMeasureClockPattern OCTET STRING,
ippmNetworkMeasurePoissonRate Integer32,
ippmNetworkMeasureTimeoutDelay Integer32,
ippmNetworkMeasureL3PacketSize Integer32,
ippmNetworkMeasureDataPattern OCTET STRING
}
ippmNetworkMeasureSrcTypeP OBJECT-TYPE ippmNetMeasureSrcTypeP OBJECT-TYPE
SYNTAX TypeP SYNTAX TypeP
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Defines the type P of the source address of the packets sent by "Defines the type P of the source address of the packets sent by
the measure." the measure."
DEFVAL { '04000080001000'H } -- ->ip: 4.0.0.8.0.1.0 DEFVAL { "ip" }
::= { ippmNetworkMeasureEntry 1 } ::= { ippmNetMeasureEntry 13 }
ippmNetworkMeasureSrc OBJECT-TYPE ippmNetMeasureSrc OBJECT-TYPE
SYNTAX TypePaddress SYNTAX TypePaddress
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Specifies the address of the source of the measure. "Specifies the address of the source of the measure.
It is represented as a list of parameters corresponding to those It is represented as a list of parameters corresponding to those
of the PROTOCOL IDENTIFIER sets in ippmNetworkMeasureSrcTypeP." of the PROTOCOL IDENTIFIER sets in ippmNetMeasureSrcTypeP."
::= { ippmNetworkMeasureEntry 2} ::= { ippmNetMeasureEntry 14}
ippmNetworkMeasureDstTypeP OBJECT-TYPE ippmNetMeasureDstTypeP OBJECT-TYPE
SYNTAX TypeP SYNTAX TypeP
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Defines the type P of the destination address of the packets "Defines the type P of the destination address of the packets
sent by the measure." sent by the measure."
::= { ippmNetworkMeasureEntry 3 } DEFVAL { "ip" }
::= { ippmNetMeasureEntry 15 }
ippmNetworkMeasureDst OBJECT-TYPE ippmNetMeasureDst OBJECT-TYPE
SYNTAX TypePaddress SYNTAX TypePaddress
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Specifies the address of the source of the measure. "Specifies the address of the destination of the measure.
It is represented as a list of parameters corresponding to those It is represented as a list of parameters corresponding to those
of the PROTOCOL IDENTIFIER sets in ippmNetworkMeasureSrcTypeP." of the PROTOCOL IDENTIFIER set in ippmNetMeasureDstTypeP."
::= { ippmNetworkMeasureEntry 4 } ::= { ippmNetMeasureEntry 16 }
ippmNetworkMeasureClockPattern OBJECT-TYPE ippmNetMeasureTxMode OBJECT-TYPE
SYNTAX OCTET STRING SYNTAX INTEGER {
other(0),
periodic(1),
poisson(2),
multiburst(3)
}
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This cyclic clock shapes the profile of the instants of "The transmit mode used to send the packets:
measurement action provided by ippmMeasureClockPeriod according 'other'
to an arbitrary distribution law. The clock resolution is The rule used to send the packets is unknown.
ippmMeasureClockPeriod. The bits of the clock pattern set to the 'periodic'
value 1 determine the valid instants of measurement action. A Packets are sent periodically at ippmNetMeasureTxPacketRate
measure is to be processed if and only if the current bit value rate.
is 1. 'poisson'
This pseudo-random clock pattern allows the configuration by the Packets are sent using a Poisson law, the median is the value
NMS of numerous kind of time sampling law such as periodic, of ippmNetMeasureMedOrIntBurstSize, the deviation is
pseudo random or Poisson. ippmNetMeasureDevtnOrBurstSize.
'multiburst'
Packets are sent bursty at ippmNetMeasureTxPacketRate. The
size of the burst is made of ippmNetMeasureDevtnOrBurstSize
packets.
Between 2 consecutive bursts, transmission stops during the time
needed to send ippmNetMeasureInterBurstPacketsNb.
The source of the measure sends the stream of measurement packets "
synchronously with the stream of instants selected by the clock ::= { ippmNetMeasureEntry 17 }
pattern sampling.
ippmNetworkMeasureClockPattern can not be used conjointly with ippmNetMeasureTxPacketRateUnit OBJECT-TYPE
ippmNetworkMeasurePoissonRate." SYNTAX TimeUnit
DEFVAL { "11111111" } MAX-ACCESS read-only
-- 100% periodic STATUS current
::= { ippmNetworkMeasureEntry 5 } DESCRIPTION
"The packet rate unit used to send the packets."
::= { ippmNetMeasureEntry 18 }
ippmNetworkMeasurePoissonRate OBJECT-TYPE ippmNetMeasureTxPacketRate OBJECT-TYPE
SYNTAX Integer32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The rate the packets are sent."
::= { ippmNetMeasureEntry 19 }
ippmNetMeasureDevtnOrBurstSize OBJECT-TYPE
SYNTAX Integer32 SYNTAX Integer32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Indicates the average number of packets per seconds sent using a "Indicates the average number of packets per seconds sent using a
poisson law. poisson law.
ippmNetworkMeasurePoissonRate can not be used conjointly with ippmNetMeasurePoissonRate can not be used conjointly with
ippmNetworkMeasureClockPattern." ippmNetMeasureClockPattern."
DEFVAL { 30 } DEFVAL { 30 }
::= { ippmNetworkMeasureEntry 6 } ::= { ippmNetMeasureEntry 20 }
ippmNetworkMeasureTimeoutDelay OBJECT-TYPE ippmNetMeasureMedOrIntBurstSize OBJECT-TYPE
SYNTAX Integer32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"According to the transmit mode, this value indicates the average
number of packets per seconds sent using a poisson law, or the
number of packets to wait between consecutive bursts."
DEFVAL { 30 }
::= { ippmNetMeasureEntry 21 }
ippmNetMeasureLossTimeout OBJECT-TYPE
SYNTAX Integer32 SYNTAX Integer32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
-- UNITS "Milliseconds" -- UNITS "Milliseconds"
DESCRIPTION DESCRIPTION
"Specifies the delay after which the packet is considered lost by the "Specifies the delay after which the packet is considered lost by the
sink." sink."
DEFVAL { 1 } DEFVAL { 10 }
::= { ippmNetworkMeasureEntry 7 } ::= { ippmNetMeasureEntry 22 }
ippmNetworkMeasureL3PacketSize OBJECT-TYPE ippmNetMeasureL3PacketSize OBJECT-TYPE
SYNTAX Integer32 SYNTAX Integer32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Specifies the size of the packets sent at the last network layer "Specifies the size of the packets counted at the IP network
in regards to the TypeP definition." layer in regards to the TypeP definition.
Example: For a TypeP 'ip ipip4' the L3 size will be the size of
the packet at ipip4 level.
"
DEFVAL { 64 } DEFVAL { 64 }
::= { ippmNetworkMeasureEntry 8 } ::= { ippmNetMeasureEntry 23 }
ippmNetworkMeasureDataPattern OBJECT-TYPE ippmNetMeasureDataPattern OBJECT-TYPE
SYNTAX OCTET STRING SYNTAX OCTET STRING
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The current field defines the round robin pattern used to fill "The pattern used to fill the payload of the packet."
the packet."
DEFVAL { 'FF'H } DEFVAL { 'FF'H }
::= { ippmNetworkMeasureEntry 9 } ::= { ippmNetMeasureEntry 24 }
ippmNetMeasureMap OBJECT-TYPE
SYNTAX SnmpAdminString
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"A administrative name of a network management map to which the measure
belongs."
DEFVAL { "" }
::= { ippmNetMeasureEntry 25 }
ippmNetMeasureSingletons OBJECT-TYPE
SYNTAX Integer32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Reports the number of singletons performed per metric by the
measure since the beginning of the measure. This parameters is
required for aggregation."
::= { ippmNetMeasureEntry 26 }
ippmNetMeasureOperState OBJECT-TYPE
SYNTAX INTEGER {
unknown(0),
running(1),
stopped(2)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Reports the operational status of the network measure.
::= { ippmNetMeasureEntry 27 }
--
--
-- ippmAggrMeasure Group
--
--
-- --
-- --
-- ippmAggrMeasureTable -- ippmAggrMeasureTable
-- --
-- --
ippmAggrMeasureTable OBJECT-TYPE ippmAggrMeasureTable OBJECT-TYPE
SYNTAX SEQUENCE OF IppmAggrMeasureEntry SYNTAX SEQUENCE OF IppmAggrMeasureEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
" This table extends the ippmMeasureTable. " An aggregated measure summarizes the results of previous
An aggregated measure summarizes the results of previous network network or aggregated measures. The results may be saved in the
or aggregated measures. The results may be saved in the
ippmHistoryTable. ippmHistoryTable.
Each step of the calculation for the measure produces a singleton Each step of the calculation for the measure produces a singleton
result per metric." result per metric."
::= { ippmAggrMeasure 1 } ::= { ippmMeasure 2 }
ippmAggrMeasureEntry OBJECT-TYPE ippmAggrMeasureEntry OBJECT-TYPE
SYNTAX IppmAggrMeasureEntry SYNTAX IppmAggrMeasureEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Typically the configuration operation sets both the values of "Typically the configuration operation sets the value of
the new ippmMeasureEntry and of the new IppmAggrMeasureEntry. theIppmAggrMeasureEntry.
ippmAggrMeasureTable is mandatory. ippmAggrMeasureTable is mandatory.
ippmAggrMeasureTable content is read only. It means that the The ippmAggrMeasureMetrics defines the metric to compute.
measure software handles the table internally.
The ippmMeasureMetrics defines the metric to compute.
The results of the measure to summarize are identified by: The results of the measure to summarize are identified by:
+ ippmAggrMeasureHistoryOwner, + ippmAggrMeasureHistoryOwner,
+ ippmAggrMeasureHistoryOwnerIndex and + ippmAggrMeasureHistoryOwnerIndex and
+ ippmAggrMeasureHistoryMetric + ippmAggrMeasureHistoryMetric
The aggregated task starts at ippmMeasureBeginTime and ends after The aggregated task starts at ippmMeasureBeginTime and ends after
ippmMeasureDuration. An aggregated result is performed and saved ippmMeasureDuration. An aggregated result is performed and saved
in the ippmHistoryTable for each ippmMeasureClockPeriod tick. " in the ippmHistoryTable for each ippmMeasureCollectionRate tick.
INDEX { ippmMeasureOwner, ippmMeasureIndex } "
INDEX { ippmAggrMeasureOwner, ippmAggrMeasureIndex }
::= { ippmAggrMeasureTable 1 } ::= { ippmAggrMeasureTable 1 }
IppmAggrMeasureEntry ::= IppmAggrMeasureEntry ::= SEQUENCE {
SEQUENCE { ippmAggrMeasureOwner IppmOwnerString,
ippmAggrMeasureIndex Integer32,
ippmAggrMeasureName SnmpAdminString,
ippmAggrMeasureMetrics IppmStandardMetrics,
ippmAggrMeasureBeginTime GMTTimeStamp,
ippmAggrMeasureAggrPeriodUnit TimeUnit,
ippmAggrMeasureAggrPeriod Integer32,
ippmAggrMeasureDurationUnit TimeUnit,
ippmAggrMeasureDuration Integer32,
ippmAggrMeasureHistorySize Integer32,
ippmAggrMeasureStorageType StorageType,
ippmAggrMeasureHistoryOwner IppmOwnerString, ippmAggrMeasureHistoryOwner IppmOwnerString,
ippmAggrMeasureHistoryOwnerIndex Integer32, ippmAggrMeasureHistoryOwnerIndex Integer32,
ippmAggrMeasureHistoryMetric Integer32 ippmAggrMeasureHistoryMetric Integer32,
ippmAggrMeasureAdminState Integer32,
ippmAggrMeasureFastReport OBJECT IDENTIFIER,
ippmAggrMeasureMap SnmpAdminString,
ippmAggrMeasureResultsMgmt Integer32,
ippmAggrMeasureStatus RowStatus
} }
ippmAggrMeasureOwner OBJECT-TYPE
SYNTAX IppmOwnerString
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The owner who has configured this entry."
::= { ippmAggrMeasureEntry 1 }
ippmAggrMeasureIndex OBJECT-TYPE
SYNTAX Integer32 (1.. 65535)
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The owner index of the measure. The value is managed by the
owner."
::= { ippmAggrMeasureEntry 2 }
ippmAggrMeasureName OBJECT-TYPE
SYNTAX SnmpAdminString
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The name of the instance of the metric. It illustrates the
specificity of the metric and includes the metric and the typeP.
example: IP-port-HTTP-connectivity"
::= { ippmAggrMeasureEntry 3 }
ippmAggrMeasureMetrics OBJECT-TYPE
SYNTAX IppmStandardMetrics
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Defines the metrics to compute within this aggregated measure.
ONLY aggregated metrics of the same type are allowed in this
field.
A measure may be configured for the result of different metric
singletons to be archived in the ippmHistoryTable. The
ippmMetricIndex of the created result has the value of the bit
index of the corresponding ippmAggrMeasureMetrics as explained
above in the ippmMetricIndex definition.
Example:
A measure asking for One-way-Delay(6) and One-way-Packet-Loss(12)
generated a flow of singletons which are logged in the
ippmHistoryTable. The singletons created for the One-way-Delay
measure have a value of ippmMetricIndex of 6 while the created
singletons for the One-way-Packet-Loss measure have a value of
ippmMetricIndex of 12.
"
::= { ippmAggrMeasureEntry 4 }
ippmAggrMeasureBeginTime OBJECT-TYPE
SYNTAX GMTTimeStamp
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Specifies the time at which the aggregated measure starts."
::= { ippmAggrMeasureEntry 5 }
ippmAggrMeasureAggrPeriodUnit OBJECT-TYPE
SYNTAX TimeUnit
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Specifies the unit of the aggregated measure period."
DEFVAL { second }
::= { ippmAggrMeasureEntry 6 }
ippmAggrMeasureAggrPeriod OBJECT-TYPE
SYNTAX Integer32
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Specifies the amount of time between 2 measurement action
intervals. The action is specific to the semantic of the measure.
Network metrics:
The ippmNetMeasureClockPattern transforms the flow of periodical
instants as a flow of unpredictable instants of measurement
packet emission.
As the source and the sink share the definition of the clock of
the measure, as the sending timestamp is part of the measurement
packet, the sink have the information to verify that the stream
of packets generated by the source respects the clock law.
Aggregated metrics:
They are performed periodically on a sequence of results of other
measures. The period corresponds to the interval between two
successive computations of the metric. The value of
ippmHistoryTimestamp result of a aggregated metric computed
corresponds to the value of the ippmHistoryTimestamp of the last
metric result of the sequence used in to compute the aggregated
metric."
DEFVAL { 60 }
::= { ippmAggrMeasureEntry 7 }
ippmAggrMeasureDurationUnit OBJECT-TYPE
SYNTAX TimeUnit
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Specifies the unit of the measure duration."
DEFVAL { second }
::= { ippmAggrMeasureEntry 8 }
ippmAggrMeasureDuration OBJECT-TYPE
SYNTAX Integer32
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Specifies the duration of the measure."
DEFVAL { 120 }
::= { ippmAggrMeasureEntry 9 }
ippmAggrMeasureHistorySize OBJECT-TYPE
SYNTAX Integer32
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Specifies the maximum number of results saved for each metric of
this measure. Overflow condition will be managed by the object
ippmAggrMeasureResultsMgmt. "
::= { ippmAggrMeasureEntry 10 }
ippmAggrMeasureStorageType OBJECT-TYPE
SYNTAX StorageType
MAX-ACCESS read-create
STATUS current
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 11 }
ippmAggrMeasureResultsMgmt OBJECT-TYPE
SYNTAX INTEGER {
wrap(1),
suspend(2)
}
MAX-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 12 }
ippmAggrMeasureHistoryOwner OBJECT-TYPE ippmAggrMeasureHistoryOwner OBJECT-TYPE
SYNTAX IppmOwnerString SYNTAX IppmOwnerString
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The owner of the measure to summarize. " "The owner of the measure to summarize. "
::= { ippmAggrMeasureEntry 1 } ::= { ippmAggrMeasureEntry 13 }
ippmAggrMeasureHistoryOwnerIndex OBJECT-TYPE ippmAggrMeasureHistoryOwnerIndex OBJECT-TYPE
SYNTAX Integer32 (1.. 65535) SYNTAX Integer32 (1.. 65535)
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The owner index of the measure to summarize. " "The owner index of the measure to summarize. "
::= { ippmAggrMeasureEntry 2 } ::= { ippmAggrMeasureEntry 14 }
ippmAggrMeasureHistoryMetric OBJECT-TYPE ippmAggrMeasureHistoryMetric OBJECT-TYPE
SYNTAX Integer32 SYNTAX Integer32
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The metric of the measure to summarize. " "The metric of the measure to summarize. "
::= { ippmAggrMeasureEntry 3 } ::= { ippmAggrMeasureEntry 15 }
ippmAggrMeasureAdminState OBJECT-TYPE
SYNTAX INTEGER {
start(0),
stop(1)
}
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This object controls the activity of the aggregated measure.
'start'
The aggregated measure is started.
'stop'
The aggregated measure is stopped.
"
::= { ippmAggrMeasureEntry 16 }
ippmAggrMeasureFastReport OBJECT-TYPE
SYNTAX OBJECT IDENTIFIER
MAX-ACCESS read-create
STATUS current
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 the a column of results
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 { 0.0 }
::= { ippmAggrMeasureEntry 17 }
ippmAggrMeasureMap OBJECT-TYPE
SYNTAX SnmpAdminString
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This object allows for classification of the measure. It is
typically the name of an administrative map.
"
DEFVAL { "" }
::= { ippmAggrMeasureEntry 18 }
ippmAggrMeasureStatus OBJECT-TYPE
SYNTAX RowStatus
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The status of this table entry. Once the entry status is set to
active, the associate entry cannot be modified.
The creation of an aggregated measure forced the creation of the
corresponding entry in ippmMeasureTable."
::= { ippmAggrMeasureEntry 19 }
-- --
-- ippmReport Group -- ippmReport Group
-- --
ippmReportPathToResults OBJECT-TYPE
SYNTAX SnmpAdminString
MAX-ACCESS read-only
STATUS current
DESCRIPTION
" It is typically an URL describing the file location where the
results are logged. "
::= { ippmReport 1 }
-- --
-- --
-- ippmReportSetupTable -- ippmReportSetupTable
-- --
-- --
ippmReportSetupTable OBJECT-TYPE ippmReportSetupTable OBJECT-TYPE
SYNTAX SEQUENCE OF IppmReportSetupEntry SYNTAX SEQUENCE OF IppmReportSetupEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The ippmReportSetupTable is a list of definition of reports. It "The ippmReportSetupTable is a list of definition of reports. It
defines the results of a network or aggregated measures that are defines the results of network or aggregated measures that are to
to be reported. A report is saved in the ippmReportTable, or sent be reported. A report is saved in the ippmReportTable, or sent to
to an application using a SNMP Trap, a SNMP inform PDU, an email an application using a SNMP Trap, a SNMP inform PDU, an email, or
or a SMS. The reporting task is not intended to be a batch action a SMS. The reporting task is not intended to be a batch action
processed at the end of the measure. It is coupled with threshold processed at the end of the measure. It is coupled with threshold
detections and event filtering to deliver application level detections and event filtering to deliver application level
events and data, while preserving scalability. events and data, while preserving scalability.
It extends the definition of a measure: the definition of a "
measure may include the definition of a report." ::= { ippmReport 2 }
::= { ippmReport 1 }
ippmReportSetupEntry OBJECT-TYPE ippmReportSetupEntry OBJECT-TYPE
SYNTAX IppmReportSetupEntry SYNTAX IppmReportSetupEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The report applies to the results of the measure which is "The report applies to the results of a measure as defined in
extended by the current report definition. either the network measure table, or the aggregated measure
table.
Typically the creation of a report sets both the values of the
new measure and those of the new IppmReportSetupEntry.
The ippmReportSetupDefinition describes the data and the events The ippmReportSetupDefinition describes the data and the events
to include in the report. The definition consists in a list of to include in the report. The definition consists of a list of
tasks to perform on the results of the measure. tasks to perform on the results of the measure.
A report is associated to a network measure or to an aggregated A report is associated to a network measure or to an aggregated
measure. measure.
Note 1 : To associate a report to an existing measure the manager Note 1 : To associate a report to an existing measure the manager
suspends the measure while setting the ippmMeasureStatus to suspends the measure by setting either the ippmNetMeasureStatus
'notInService'. Then he setups the report fields and activates or the ippmAggrMeasureStatus to 'notInService'. Then one sets the
the measure while setting the ippmMeasureStatus to 'active'. report fields and activates the measure by setting the
corresponding MeasureStatus to 'active'.
Note 2 : A report is tied to a measure. The period of the measure Note 2: A report is tied to a measure. The period of the measure"
" INDEX { ippmReportSetupOwner, ippmReportSetupIndex }
INDEX { ippmMeasureOwner, ippmMeasureIndex }
::= { ippmReportSetupTable 1 } ::= { ippmReportSetupTable 1 }
IppmReportSetupEntry ::= IppmReportSetupEntry ::=
SEQUENCE { SEQUENCE {
ippmReportSetupOwner IppmOwnerString,
ippmReportSetupIndex Integer32,
ippmReportSetupMeasureOwner IppmOwnerString,
ippmReportSetupMeasureIndex Integer32,
ippmReportSetupMeasureMetric Integer32,
ippmReportSetupDefinition IppmReportDefinition, ippmReportSetupDefinition IppmReportDefinition,
ippmReportSetupMetricThreshold Integer32, ippmReportSetupUpDownThreshold Integer32,
ippmReportSetupLowThreshold Integer32,
ippmReportSetupHighThreshold Integer32,
ippmReportSetupDurationThresUnit TimeUnit,
ippmReportSetupDurationThreshold Integer32, ippmReportSetupDurationThreshold Integer32,
ippmReportSetupReportSize Integer32,
ippmReportSetupResultsMgmt Integer32,
ippmReportSetupNMS SnmpAdminString, ippmReportSetupNMS SnmpAdminString,
ippmReportSetupNotification OBJECT IDENTIFIER, ippmReportSetupNotification OBJECT IDENTIFIER,
ippmReportSetupMap SnmpAdminString,
ippmReportSetupStatus RowStatus ippmReportSetupStatus RowStatus
} }
ippmReportSetupOwner OBJECT-TYPE
SYNTAX IppmOwnerString
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The owner who has configured this report entry."
::= { ippmReportSetupEntry 1 }
ippmReportSetupIndex OBJECT-TYPE
SYNTAX Integer32 (1.. 65535)
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The owner index of the report entry. The value is managed by the
owner."
::= { ippmReportSetupEntry 2 }
ippmReportSetupMeasureOwner OBJECT-TYPE
SYNTAX IppmOwnerString
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The owner of the measure to report."
::= { ippmReportSetupEntry 3 }
ippmReportSetupMeasureIndex OBJECT-TYPE
SYNTAX Integer32 (1.. 65535)
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The index of the measure to report."
::= { ippmReportSetupEntry 4 }
ippmReportSetupMeasureMetric OBJECT-TYPE
SYNTAX Integer32 (1.. 65535)
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The metric of the measure to report."
::= { ippmReportSetupEntry 5 }
ippmReportSetupDefinition OBJECT-TYPE ippmReportSetupDefinition OBJECT-TYPE
SYNTAX IppmReportDefinition SYNTAX IppmReportDefinition
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The description of the events and actions that are used in the "In order to properly define a report, one must provide
definition of the report. information to:
Send the report using the type of message selected by the bits 8 + Select the events to consider for reporting;
to 12. The report consists of the results of the measure which + Configure filters to select pertinent values;
have been saved in the ippmReportTable. If the + Describe the way the report is delivered;
onEventSendReport(7) bit is unset, the report is not saved. + Describe clean up actions to perform on report completion;
The format of a report sent to a NMS is described in a
notification defined in the ippmNotifications node.
The message sent is a notification defined in the The event and the filter selected in the report definition
ippmNotifications node. The notification sent depends on the step determines the notification to refer:
of the measure: + Up and Down filter report format is ippmUpAndDownReport;
+ Singleton events are sent using the notification + Inband filter report format is ippmInBandReport;
ippmSingletonAlarm + Outband filter report format is ippmOutBandReport;
+ Exceeded events durations are sent using the notification + Above filter report format is ippmAboveReport;
ippmEventsDurationExceededAlarm + Below filter report format is ippmBelowReport;
+ A report of a cycle of measure is sent using the notification + Any filter and reportExceededEventsDuration report format is
ippmCycleOfMeasureReport ippmEventsDurationExceededReport;
+ A report of a complete measure is sent using the notification + Any filter and the event onMeasureCompletion report format is
ippmCompletedMeasureReport ippmCompletedMeasureReport;
Example 1: Example 1:
The report setup of an alarm to be sent to the owner in a SNMP Consider a report definition, which reports on the fly, up and
Trap each time the two results are found on each side of the down result events of a metric measure:
metric threshold value of 5:
ippmReportSetupMetricThreshold 5
ippmReportSetupDefinition { ippmReportSetupDefinition {
onSingleton(1), onSingleton,
reportOnlyUptoDownMetricResults(4), reportUpAndDownMetricResults,
inSNMPTrapPDU(8) inSNMPv2TrapPDU
} }
Example 2: The value of the threshold is given by
ippmReportSetupUpDownThreshold. It has the value '5' in this
example.
The setup of a report to be sent to the owner in a SNMP Being a flow of results { 3.3 3.2 3.2 5.1 5.3 5.6 6.3 5.2 4.0 3.8
informRequestPDU per measure cycle. It reports the two results ...}, the report process will send 2 traps:
found on each side of the metric threshold of 5: + The first one carries the results 3.2 and 5.1
corresponding to a down to up event;
+ The second one carries the results 5.2 and 4.0 of the
up to down event
UpAndDown
ippmReportSetupMetricThreshold 5 Example 2:
ippmReportSetupDefinition { Consider the report definition, which reports per measure cycle
onMeasureCycle(2), in a SNMP informRequestPDU, up and down results events of a
reportOnlyUptoDownMetricResults(4), metric measure:
inInformRequestPDU(10), :
onReportDeliveryClearHistory(13)
}
Default report:
The default report provides the control protocol with an implicit
mechanism to forward the result of a cycle of measure to the
owner of the measure while deleting the results corresponding to
this cycle of measure from the ippmHistoryTable on reception of
the response to the InformRequestPDU :
ippmReportSetupDefinition { ippmReportSetupDefinition {
onMeasureCycle(2), onMeasureCycle,
inInformRequestPDU(10), reportUpAndDownMetricResults,
onReportDeliveryClearHistory(13) inInformRequestPDU,
onReportDeliveryClearReport
} }
The value of the threshold is given by
ippmReportSetupUpDownThreshold. It has the value '5' in this
example.
The cycle of measure of the measure setup is set to 10 results.
Being a flow of 10 results { 3.3 3.2 3.2 5.1 5.3 5.6 6.3 5.2 4.0
3.8 ... }, the report process will send one InformRequestPDU that
carries the couples (3.2, 5.1) and (5.2 ,4.0) corresponding to
the first down to up event and to the second up to down event,
respectively.
" "
DEFVAL { { onMeasureCycle, inInformRequestPDU, ::= { ippmReportSetupEntry 6 }
onReportDeliveryClearHistory} }
::= { ippmReportSetupEntry 1 }
ippmReportSetupMetricThreshold OBJECT-TYPE ippmReportSetupUpDownThreshold OBJECT-TYPE
SYNTAX Integer32 SYNTAX Integer32
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An event is generated when the result of the measure exceeds the "An event is generated when the result of the measure exceeds the
value of ippmReportSetupMetricThreshold. value of ippmReportSetupMetricThreshold.
The threshold has the same unit as the metric. The metric unit is The threshold has the same unit as the metric. The metric unit is
recorded in the object ippmMetricsUnit of this metric entry in recorded in the object ippmMetricsUnit of this metric entry in
the ippmMetricTable. the ippmMetricTable.
" "
::= { ippmReportSetupEntry 2 } ::= { ippmReportSetupEntry 7 }
ippmReportSetupLowThreshold OBJECT-TYPE
SYNTAX Integer32
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"An event is generated when the result of the measure of the
metric is lower that the value of ippmReportSetupLowThreshold.
The threshold has the same unit as the metric. The metric unit is
recorded in the object ippmMetricsUnit of this metric entry in
the ippmMetricTable.
"
::= { ippmReportSetupEntry 8 }
ippmReportSetupHighThreshold OBJECT-TYPE
SYNTAX Integer32
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"An event is generated when the result of the measure of the
metric exceeds the value of ippmReportSetupHighThreshold.
The threshold has the same unit as the metric. The metric unit is
recorded in the object ippmMetricsUnit of this metric entry in
the ippmMetricTable.
"
::= { ippmReportSetupEntry 9 }
ippmReportSetupDurationThresUnit OBJECT-TYPE
SYNTAX TimeUnit
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The unit of the duration threshold."
::= { ippmReportSetupEntry 10 }
ippmReportSetupDurationThreshold OBJECT-TYPE ippmReportSetupDurationThreshold OBJECT-TYPE
SYNTAX Integer32 SYNTAX Integer32
UNITS "Seconds"
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An event is generated when contiguous results of the measure are "An event is generated when contiguous results of the measure are
over the ippmReportSetupMetricThreshold, during over the ippmReportSetupUpDownThreshold, during
ippmReportSetupDurationThreshold seconds. ippmReportSetupDurationThreshold seconds.
Performance: Performance:
To improve the performance the ippmReportSetupDurationThreshold To improve the performance of the system, the report process may
may have the same value as the ippmMeasurePeriod. be synchronized with the cycle of collection of network measure
The default value of ippmReportSetupDurationThreshold is or with the period of aggregation of an aggregate measure."
ippmMeasurePeriod. That improves the performance because the
threshold comparison is synchronized with the ippmMeasurePeriod
aggregation cycle. That improves the performance because it
synchronized the report exportation with the management of the
history and report records of a measure."
DEFVAL { 15 } DEFVAL { 15 }
::= { ippmReportSetupEntry 3 } ::= { ippmReportSetupEntry 11 }
ippmReportSetupReportSize OBJECT-TYPE
SYNTAX Integer32
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Specifies the maximum number of results saved for each metric of
this measure. The history of each metric is managed as a circular
table. The newest result overwrites the oldest one when the
history granted to this metric measure is full.
The management of the results may be optimized if synchronized
with the reports steps of this measure. "
::= { ippmReportSetupEntry 12 }
ippmReportSetupResultsMgmt OBJECT-TYPE
SYNTAX INTEGER {
wrap(1),
suspend(2),
delete(3)
}
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"
Action to take when the report log is full. The user may choose
to either wrap, in which case the agent writes over existing
records. The user may choose to suspend writing to the log in the
event that he wishes to archive the data. The resume action
causes the agent to begin to write in the report log, and assumes
the data has been cleared
This object indicates the way the measure results are managed
when the owner quota is over:
'wrap'
continue the measure and erase the older entries in the
history.
'suspend'
stop the measure and keep the results in the history.
'delete'
remove the results from the history.
"
::= { ippmReportSetupEntry 13 }
ippmReportSetupNMS OBJECT-TYPE ippmReportSetupNMS OBJECT-TYPE
SYNTAX SnmpAdminString SYNTAX SnmpAdminString
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The recipient of the report may be provided in the setup. By "The recipient of the report may be provided in the setup. By
default the recipient of the report is the owner of the measure. default the recipient of the report is the owner of the measure.
Its addresses are recorded in the ippmOwnersTable. Its addresses are recorded in the ippmOwnersTable.
The type of ippmReportSetupNMS is not InetAddress because the The type of ippmReportSetupNMS is not InetAddress because the
report may be sent using SMS or fax. report may be sent using SMS or fax.
" "
::= { ippmReportSetupEntry 4 } ::= { ippmReportSetupEntry 14 }
ippmReportSetupNotification OBJECT-TYPE ippmReportSetupNotification OBJECT-TYPE
SYNTAX OBJECT IDENTIFIER SYNTAX OBJECT IDENTIFIER
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
" ippmReportSetupNotification identifies the notification used to "Even though the notification to use is defined in the report
send the report. The definition of the notification defines the definition, the object ippmReportSetupNotification provides
content and the format of the report. " flexibility to select another notification. "
::= { ippmReportSetupEntry 5 } -- DEFVAL { 0.0 }
::= { ippmReportSetupEntry 15 }
ippmReportSetupMap OBJECT-TYPE
SYNTAX SnmpAdminString
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"An administrative name of a map to which the report belongs."
DEFVAL { "" }
::= { ippmReportSetupEntry 16 }
ippmReportSetupStatus OBJECT-TYPE ippmReportSetupStatus OBJECT-TYPE
SYNTAX RowStatus SYNTAX RowStatus
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The status of this table entry. " "The status of this table entry. "
::= { ippmReportSetupEntry 6 } ::= { ippmReportSetupEntry 17 }
-- --
-- ippmReportTable -- ippmReportTable
-- --
ippmReportTable OBJECT-TYPE ippmReportTable OBJECT-TYPE
SYNTAX SEQUENCE OF IppmReportEntry SYNTAX SEQUENCE OF IppmReportEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The ippmReportTable logs the results of the reports. The results "The ippmReportTable logs the results of the reports. The results
consist of a subset of the results of a measure as described in consist of a subset of the results of a measure as described in
the report definition. The activation of an up and down filtering the report definition. The activation of an up and down filtering
in the report definition limits the results logged to those in the report definition limits the results logged to those
corresponding to major events. Otherwise, the ippmReportTable is corresponding to major events. Otherwise, the ippmReportTable is
skipping to change at page 59, line 16 skipping to change at page 60, line 39
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The ippmReportTable logs the results of the reports. The results "The ippmReportTable logs the results of the reports. The results
consist of a subset of the results of a measure as described in consist of a subset of the results of a measure as described in
the report definition. The activation of an up and down filtering the report definition. The activation of an up and down filtering
in the report definition limits the results logged to those in the report definition limits the results logged to those
corresponding to major events. Otherwise, the ippmReportTable is corresponding to major events. Otherwise, the ippmReportTable is
identical to the ippmHistoryTable." identical to the ippmHistoryTable."
::= { ippmReport 2 } ::= { ippmReport 3 }
ippmReportEntry OBJECT-TYPE ippmReportEntry OBJECT-TYPE
SYNTAX IppmReportEntry SYNTAX IppmReportEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A report is a list of results of a measure. This sample is "A report is a list of results of a measure. This sample is
associated with the ippmReportSetupEntry which has set up the associated with the ippmReportSetupEntry which has set up the
report. An ippmReportEntry entry is one of the results of a report. An ippmReportEntry entry is one of the results of a
measure to report. measure to report.
An ippmReportEntry entry is one of the results of a measure An ippmReportEntry entry is one of the results of a measure
identified by ippmReportOwner, ippmReportIndex, ippmReportIndex identified by ippmReportMeasureOwner, ippmReportMeasureIndex,
and ippmHistoryIndex. ippmReportMetricIndex and ippmReportIndex.
In the index: In the index:
+ ippmMeasureOwner identifies the owner of the measure; + ippmReportMeasureOwner identifies the owner of the measure;
+ ippmMeasureIndex identifies the measure in the owner namespace; + ippmReportMeasureIndex identifies the measure in the owner
namespace;
+ ippmMetricIndex identifies the metric measured in + ippmReportMetricIndex identifies the metric measured in
ippmMetricTable; ippmMetricTable;
+ ippmReportIndex is the local index of the result on the report + ippmReportIndex is the local index of the result on the report
table." table."
INDEX { ippmMeasureOwner, ippmMeasureIndex, ippmMetricIndex, INDEX { ippmReportMeasureOwner, ippmReportMeasureIndex,
ippmReportIndex } ippmReportMetricIndex, ippmReportIndex }
::= { ippmReportTable 1 } ::= { ippmReportTable 1 }
IppmReportEntry ::= IppmReportEntry ::=
SEQUENCE { SEQUENCE {
ippmReportMeasureOwner IppmOwnerString,
ippmReportMeasureIndex Integer32,
ippmReportMetricIndex Integer32,
ippmReportIndex Integer32, ippmReportIndex Integer32,
ippmReportSequence Integer32, ippmReportSequence Integer32,
ippmReportTimestamp GMTTimeStamp, ippmReportTimestamp GMTTimeStamp,
ippmReportValue Integer32 ippmReportValue Integer32
} }
ippmReportMeasureOwner OBJECT-TYPE
SYNTAX IppmOwnerString
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The owner of the measure that produced this result."
::= { ippmReportEntry 1 }
ippmReportMeasureIndex OBJECT-TYPE
SYNTAX Integer32 (1.. 65535)
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
" The owner index of the measure that produced this result."
::= { ippmReportEntry 2 }
ippmReportMetricIndex OBJECT-TYPE
SYNTAX Integer32 (1.. 65535)
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
" ippmReportMetricIndex identifies the metric measured by the
measure. The metric is described in the corresponding entry of
the ippmMetricTable."
::= { ippmReportEntry 3 }
ippmReportIndex OBJECT-TYPE ippmReportIndex OBJECT-TYPE
SYNTAX Integer32 (1.. 65535) SYNTAX Integer32 (1.. 65535)
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The local index of the result of a metric measure" "The local index of the result of a metric measure"
::= { ippmReportEntry 1 } ::= { ippmReportEntry 4 }
ippmReportSequence OBJECT-TYPE ippmReportSequence OBJECT-TYPE
SYNTAX Integer32 (1.. 65535) SYNTAX Integer32 (0.. 65535)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
" ippmReportSequence is the sequence index of the measurement " ippmReportSequence is the sequence index of the measurement
results of the measure of a metric. results of the measure of a metric.
Network metrics: Network metrics:
It's the sequence index of a measurement packet. Typically, it It's the sequence index of a measurement packet. Typically, it
identifies the order of the packet in the stream of packets sends identifies the order of the packet in the stream of packets sends
by the source. by the source.
Aggregated metrics: Aggregated metrics:
It is the sequence index of the aggregated metric results It is the sequence index of the aggregated metric results
computed." computed."
::= { ippmReportEntry 2 } ::= { ippmReportEntry 5 }
ippmReportTimestamp OBJECT-TYPE ippmReportTimestamp OBJECT-TYPE
SYNTAX GMTTimeStamp SYNTAX GMTTimeStamp
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The instant of the measure of the result." "The instant of the measure of the result."
::= { ippmReportEntry 3 } ::= { ippmReportEntry 6 }
ippmReportValue OBJECT-TYPE ippmReportValue OBJECT-TYPE
SYNTAX Integer32 SYNTAX Integer32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The value." "The value."
::= { ippmReportEntry 4 } ::= { ippmReportEntry 7 }
ippmOnReportFullAction OBJECT-TYPE
SYNTAX INTEGER {
wrap(1),
suspend(2),
resume(3)
}
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"Action to take when the report log is full. The user may choose
to either wrap, in which case the agent writes over existing
records. The user may choose to suspend writing to the log in the
event that he wishes to archive the data. The resume action
causes the agent to begin to write in the report log, and assumes
the data has been cleared."
::= { ippmReport 3 }
-- --
-- IPPM Notifications -- IPPM Notifications
-- --
ippmSingletonAlarm NOTIFICATION-TYPE ippmUpAndDownReport NOTIFICATION-TYPE
OBJECTS { OBJECTS {
ippmReportSetupDefinition,
ippmMetricType,
ippmMetricUnit, ippmMetricUnit,
ippmReportTimestamp, ippmMetricDescription,
ippmReportValue ippmHistoryTimestamp,
ippmHistorySequence,
ippmHistoryValue,
ippmReportPathToResults
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A notification sent because 2 contiguous results are on opposite "A notification sent because 2 contiguous results are on opposite
sides of the metric threshold value. sides of the metric threshold value.
The notification contains the instances of the ippmReportValue The notification contains the instances of the ippmHistoryValue
object that exceeded the threshold. object that exceeded the threshold.
The notification contains the instances of the The notification contains the instances of the
ippmReportTimestamp identifying the time the event occurred." ippmHistoryTimestamp identifying the time the event occurred.
ippmReportPathToResults is a link to the file name, which
contains detailled results corresponding to this event."
::= { ippmNotifications 1 } ::= { ippmNotifications 1 }
ippmEventsDurationExceededAlarm NOTIFICATION-TYPE ippmInBandReport NOTIFICATION-TYPE
OBJECTS { OBJECTS {
ippmReportSetupDefinition,
ippmMetricType,
ippmMetricUnit, ippmMetricUnit,
ippmReportTimestamp, ippmMetricDescription,
ippmReportValue ippmHistoryTimestamp,
ippmHistorySequence,
ippmHistoryValue,
ippmReportPathToResults
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A notification sent when the duration of contiguous raising "A notification sent because the value of the measure is under
ippmReportSetupMetricThreshold exceeds the the high threshold value and greater than the low threshold
ippmReportSetupDurationThreshold value. value.
The notification contains the instances of the ippmHistoryValue
object that exceeded the threshold.
The notification contains the instances of the
ippmHistoryTimestamp identifying the time the event occurred.
ippmReportPathToResults is a link to the file name, which
contains detailled results corresponding to this event."
::= { ippmNotifications 2 }
The notification contains the instances of the ippmReportValue ippmOutBandReport NOTIFICATION-TYPE
OBJECTS {
ippmReportSetupDefinition,
ippmMetricType,
ippmMetricUnit,
ippmMetricDescription,
ippmHistoryTimestamp,
ippmHistorySequence,
ippmHistoryValue,
ippmReportPathToResults
}
STATUS current
DESCRIPTION
"A notification sent because the result of the measure is either
greater than the high threshold or lower than the low threshold.
The notification contains the instances of the ippmHistoryValue
object that exceeded the threshold.
The notification contains the instances of the
ippmHistoryTimestamp identifying the time the event occurred.
ippmReportPathToResults is a link to the file name, which
contains detailled results corresponding to this event."
::= { ippmNotifications 3 }
ippmAboveReport NOTIFICATION-TYPE
OBJECTS {
ippmReportSetupDefinition,
ippmMetricType,
ippmMetricUnit,
ippmMetricDescription,
ippmHistoryTimestamp,
ippmHistorySequence,
ippmHistoryValue,
ippmReportPathToResults
}
STATUS current
DESCRIPTION
" The notification contains the instances of the ippmHistoryValue
object that exceeded the threshold. object that exceeded the threshold.
The notification contains the instances of the The notification contains the instances of the
ippmReportTimestamp identifying the time the event occurred." ippmHistoryTimestamp identifying the time the event occurred.
::= { ippmNotifications 2 } ippmReportPathToResults is a link to the file name, which
contains detailled results corresponding to this event."
::= { ippmNotifications 4 }
ippmCycleOfMeasureReport NOTIFICATION-TYPE ippmBelowReport NOTIFICATION-TYPE
OBJECTS { OBJECTS {
ippmReportSetupDefinition,
ippmMetricType,
ippmMetricUnit,
ippmMetricDescription,
ippmHistoryTimestamp,
ippmHistorySequence,
ippmHistoryValue,
ippmReportPathToResults
}
STATUS current
DESCRIPTION
"
The notification contains the instances of the ippmHistoryValue
object that exceeded the threshold.
The notification contains the instances of the
ippmHistoryTimestamp identifying the time the event occurred.
ippmReportPathToResults is a link to the file name, which
contains detailled results corresponding to this event."
::= { ippmNotifications 5 }
ippmEventsDurationExceededReport NOTIFICATION-TYPE
OBJECTS {
ippmReportSetupDefinition,
ippmMetricType,
ippmMetricUnit, ippmMetricUnit,
ippmMetricDescription,
ippmHistoryTimestamp, ippmHistoryTimestamp,
ippmHistorySequence,
ippmHistoryValue ippmHistoryValue
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A notification sent when a measure cycle completes. "A notification sent when the duration of continuously rising
metric threshold exceeds the ippmReportSetupDurationThreshold
value.
The notification contains the instances of the ippmReportValue The notification contains the instances of the ippmReportValue
objects saved in the ippmReportTable for this measure cycle. The object that exceeded the threshold.
ippmHistoryTimestamp of the index identifies the time the
measures where performed." The notification contains the instances of the
::= { ippmNotifications 3 } ippmReportTimestamp identifying the time the event occurred.
ippmReportPathToResults is a link to the file name, which
contains detailled results corresponding to this event.
"
::= { ippmNotifications 6 }
ippmCompletedMeasureReport NOTIFICATION-TYPE ippmCompletedMeasureReport NOTIFICATION-TYPE
OBJECTS { OBJECTS {
ippmReportSetupDefinition,
ippmMetricType,
ippmMetricUnit, ippmMetricUnit,
ippmMetricDescription,
ippmHistoryTimestamp, ippmHistoryTimestamp,
ippmHistoryValue ippmHistorySequence,
ippmHistoryValue,
ippmReportPathToResults
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A notification sent when a measure completes. "A notification sent when a measure completes.
The index of the included ippmReportSetupDefinition object The index of the included ippmReportSetupDefinition object
identifies the ippmMeasureEntry and the ippmResultSetupEntry that identifies the ippmMeasureEntry and the ippmResultSetupEntry that
specified the report. specified the report.
The notification contains the instances of the ippmReportValue ippmReportPathToResults is a link to the file name, which
objects saved in the ippmReportTable for this measure cycle. The contains the results of this measure cycle."
ippmHistoryTimestamp of the index identifies the time the ::= { ippmNotifications 7 }
measures where performed."
::= { ippmNotifications 4 }
ippmHistoryLogFull NOTIFICATION-TYPE ippmAggrMeasureHistoryFull NOTIFICATION-TYPE
OBJECTS { OBJECTS {
ippmOnHistoryFullAction ippmAggrMeasureName,
ippmMetricType,
ippmMetricUnit,
ippmMetricDescription,
ippmHistoryTimestamp,
ippmHistorySequence,
ippmHistoryValue
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A notification sent when the history log is full. It indicates " A notification sent when the size of the history of a metric of
what action is to be taken. If the action is wrap the agent will a aggregated measure exceeds ippmAggrMeasureHistorySize. The
write over existing records in the beginning of the log file. If agent will then manage the reports according to the policy
the action is suspend, the agent halts all recording of measures described in ippmAggrMeasureResultsMgmt."
in the history table. If the action is resume, the agent begins ::= { ippmNotifications 8 }
writing measures again in the history log"
::= { ippmNotifications 5 } ippmNetMeasureHistoryFull NOTIFICATION-TYPE
OBJECTS {
ippmNetMeasureName,
ippmMetricType,
ippmMetricUnit,
ippmMetricDescription,
ippmHistoryTimestamp,
ippmHistorySequence,
ippmHistoryValue
}
STATUS current
DESCRIPTION
" A notification sent when the size of the history of a metric of
a network measure exceeded ippmNetMeasureHistorySize. Then the
agent manages the records according to the policy described in
ippmNetMeasureResultsMgmt."
::= { ippmNotifications 9 }
ippmReportLogFull NOTIFICATION-TYPE ippmReportLogFull NOTIFICATION-TYPE
OBJECTS { OBJECTS {
ippmOnReportFullAction -- iIppmReportMetricIndex,
ippmReportSetupResultsMgmt,
ippmReportTimestamp,
ippmReportSequence,
ippmReportValue
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A notification sent when the report log is full. It indicates "A notification sent when the size of the report of a metric of a
what action is to be taken. If the action is wrap the agent will measure exceeded ippmReportSetupReportSize. Then the agent
write over existing records in the beginning of the log file. If manages the reports according to the policy described in
the action is suspend, the agent halts all recording of measures ippmReportSetupResultsMgmt."
in the report table. If the action is resume, the agent begins ::= { ippmNotifications 10 }
writing measures again in the report log"
::= { ippmNotifications 6 }
-- --
-- IPPM MIB Conformance statements -- IPPM MIB Conformance statements
-- --
ippmCompliances OBJECT IDENTIFIER ::={ ippmConformance 1 } ippmCompliances OBJECT IDENTIFIER ::={ ippmConformance 1 }
ippmGroups OBJECT IDENTIFIER ::={ ippmConformance 2 } ippmGroups OBJECT IDENTIFIER ::={ ippmConformance 2 }
ippmProxyInterDomainCompliances MODULE-COMPLIANCE ippmProxyInterDomainCompliances MODULE-COMPLIANCE
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The compliance statement for SNMP entities which implement the "The compliance statement for SNMP entities which implement the
IPPM MIB as a proxy in interdomain. The implementation of the IPPM MIB as a proxy in interdomain. The implementation of the
VACM control is mandatory." VACM control is mandatory."
MODULE -- this module MODULE -- this module
MANDATORY-GROUPS { MANDATORY-GROUPS {
ippmSystemGroup, ippmMeasureGroup, ippmNetworkMeasureGroup, ippmSystemGroup, ippmNetMeasureGroup, ippmHistoryGroup,
ippmHistoryGroup, ippmAggrMeasureGroup, ippmReportGroup, ippmAggrMeasureGroup, ippmReportGroup, ippmNotificationGroup
ippmNotificationGroup
} }
::= { ippmCompliances 1 } ::= { ippmCompliances 1 }
ippmProxyCompliances MODULE-COMPLIANCE ippmProxyCompliances MODULE-COMPLIANCE
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The compliance statement for SNMP entities which implement the "The compliance statement for SNMP entities which implement the
IPPM MIB as a proxy." IPPM MIB as a proxy."
MODULE -- this module MODULE -- this module
MANDATORY-GROUPS { MANDATORY-GROUPS {
ippmSystemGroup, ippmMeasureGroup, ippmNetworkMeasureGroup, ippmSystemGroup, ippmNetMeasureGroup, ippmHistoryGroup,
ippmHistoryGroup, ippmAggrMeasureGroup, ippmReportGroup, ippmAggrMeasureGroup, ippmReportGroup, ippmNotificationGroup
ippmNotificationGroup
} }
GROUP ippmOwnersGroup GROUP ippmOwnersGroup
DESCRIPTION DESCRIPTION
"The ippmOwnersGroup is needed if VACM is not implemented." "The ippmOwnersGroup is needed if VACM is not implemented."
::= { ippmCompliances 2 } ::= { ippmCompliances 2 }
ippmProbeCompliances MODULE-COMPLIANCE ippmProbeCompliances MODULE-COMPLIANCE
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The compliance statement for SNMP entities which implement the "The compliance statement for SNMP entities which implement the
IPPM MIB in a probe." IPPM MIB in a probe."
MODULE -- this module MODULE -- this module
MANDATORY-GROUPS { MANDATORY-GROUPS {
ippmSystemGroup, ippmMeasureGroup, ippmNetworkMeasureGroup, ippmSystemGroup, ippmNetMeasureGroup, ippmHistoryGroup
ippmHistoryGroup
} }
::= { ippmCompliances 3 } ::= { ippmCompliances 3 }
ippmSystemGroup OBJECT-GROUP ippmSystemGroup OBJECT-GROUP
OBJECTS { OBJECTS {
ippmSystemSynchronizationDesc, ippmSystemSynchronizationDesc,
ippmSystemTime, ippmSystemTime,
ippmSystemSynchronizationType, ippmSystemSynchronizationType,
ippmSystemClockResolution, ippmSystemClockResolution,
ippmSystemCurrentSynchronization,
ippmSynchronizationTime, ippmSynchronizationTime,
ippmSynchronizationStratum, ippmSynchronizationStratum,
ippmSynchronizationResolution, ippmSynchronizationResolution,
ippmPointOfMeasureMgmtAddrType, ippmPointOfMeasureMgmtAddrType,
ippmPointOfMeasureMgmtAddress, ippmPointOfMeasureMgmtAddress,
ippmPointOfMeasureTypePAddress, ippmPointOfMeasureTypePAddress,
ippmPointOfMeasureAddress ippmPointOfMeasureAddress,
} ippmSystemOperationalStatus,
STATUS current ippmPointOfMeasureMetrics,
DESCRIPTION
"The IPPM System Group"
::= { ippmGroups 1}
ippmMeasureGroup OBJECT-GROUP
OBJECTS {
ippmMetricCapabilities, ippmMetricCapabilities,
ippmMetricType,
ippmMetricUnit, ippmMetricUnit,
ippmMetricDescription, ippmMetricDescription
ippmMetricMaxHistorySize,
ippmMeasureName,
ippmMeasureMetrics,
ippmMeasureBeginTime,
ippmMeasureClockPeriodUnit,
ippmMeasureClockPeriod,
ippmMeasureDurationUnit,
ippmMeasureDuration,
ippmMeasureHistorySize,
ippmMeasureStorageType,
ippmMeasureStatus
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The IPPM Measure Group" "The IPPM System Group"
::= { ippmGroups 2} ::= { ippmGroups 1}
ippmNetworkMeasureGroup OBJECT-GROUP ippmNetMeasureGroup OBJECT-GROUP
OBJECTS { OBJECTS {
ippmNetworkMeasureSrcTypeP, ippmNetMeasureName,
ippmNetworkMeasureSrc, ippmNetMeasureMetrics,
ippmNetworkMeasureDstTypeP, ippmNetMeasureBeginTime,
ippmNetworkMeasureDst, ippmNetMeasureCollectionRateUnit,
ippmNetworkMeasureClockPattern, ippmNetMeasureCollectionRate,
ippmNetworkMeasurePoissonRate, ippmNetMeasureDurationUnit,
ippmNetworkMeasureTimeoutDelay, ippmNetMeasureDuration,
ippmNetworkMeasureL3PacketSize, ippmNetMeasureHistorySize,
ippmNetworkMeasureDataPattern ippmNetMeasureFailureMgmtMode,
ippmNetMeasureResultsMgmt,
ippmNetMeasureSrcTypeP,
ippmNetMeasureSrc,
ippmNetMeasureDstTypeP,
ippmNetMeasureDst,
ippmNetMeasureTxMode,
ippmNetMeasureTxPacketRateUnit,
ippmNetMeasureTxPacketRate,
ippmNetMeasureDevtnOrBurstSize,
ippmNetMeasureMedOrIntBurstSize,
ippmNetMeasureLossTimeout,
ippmNetMeasureL3PacketSize,
ippmNetMeasureDataPattern,
ippmNetMeasureMap,
ippmNetMeasureSingletons,
ippmNetMeasureOperState
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The IPPM Network Measure Group" "The IPPM Network Measure Group"
::= { ippmGroups 3} ::= { ippmGroups 3}
ippmHistoryGroup OBJECT-GROUP ippmHistoryGroup OBJECT-GROUP
OBJECTS { OBJECTS {
ippmHistorySequence, ippmHistorySequence,
ippmHistoryTimestamp, ippmHistoryTimestamp,
ippmOnHistoryFullAction,
ippmHistoryValue ippmHistoryValue
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The IPPM History Group" "The IPPM History Group"
::= { ippmGroups 4} ::= { ippmGroups 4}
ippmAggrMeasureGroup OBJECT-GROUP ippmAggrMeasureGroup OBJECT-GROUP
OBJECTS { OBJECTS {
ippmAggrMeasureName,
ippmAggrMeasureMetrics,
ippmAggrMeasureBeginTime,
ippmAggrMeasureAggrPeriodUnit,
ippmAggrMeasureAggrPeriod,
ippmAggrMeasureDurationUnit,
ippmAggrMeasureDuration,
ippmAggrMeasureHistorySize,
ippmAggrMeasureStorageType,
ippmAggrMeasureHistoryOwner, ippmAggrMeasureHistoryOwner,
ippmAggrMeasureHistoryOwnerIndex, ippmAggrMeasureHistoryOwnerIndex,
ippmAggrMeasureHistoryMetric ippmAggrMeasureHistoryMetric,
ippmAggrMeasureAdminState,
ippmAggrMeasureFastReport,
ippmAggrMeasureMap,
ippmAggrMeasureResultsMgmt,
ippmAggrMeasureStatus
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The IPPM AggregatedMeasure Group" "The IPPM AggregatedMeasure Group"
::= { ippmGroups 5} ::= { ippmGroups 5}
ippmReportGroup OBJECT-GROUP ippmReportGroup OBJECT-GROUP
OBJECTS { OBJECTS {
ippmReportSetupMeasureOwner,
ippmReportSetupMeasureIndex,
ippmReportSetupMeasureMetric,
ippmReportSetupDefinition, ippmReportSetupDefinition,
ippmReportSetupMetricThreshold, ippmReportSetupUpDownThreshold,
ippmReportSetupLowThreshold,
ippmReportSetupHighThreshold,
ippmReportSetupDurationThresUnit,
ippmReportSetupDurationThreshold, ippmReportSetupDurationThreshold,
ippmReportSetupReportSize,
ippmReportSetupResultsMgmt,
ippmReportSetupNMS, ippmReportSetupNMS,
ippmReportSetupNotification, ippmReportSetupNotification,
ippmReportSetupMap,
ippmReportSetupStatus, ippmReportSetupStatus,
ippmReportPathToResults,
ippmReportSequence, ippmReportSequence,
ippmReportTimestamp, ippmReportTimestamp,
ippmReportValue, ippmReportValue
ippmOnReportFullAction
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The IPPM Report Group" "The IPPM Report Group"
::= { ippmGroups 6} ::= { ippmGroups 6}
ippmOwnersGroup OBJECT-GROUP ippmOwnersGroup OBJECT-GROUP
OBJECTS { OBJECTS {
ippmOwnersOwner, ippmOwnersOwner,
ippmOwnersGrantedMetrics, ippmOwnersGrantedMetrics,
ippmOwnersGrantedRules, ippmOwnersQuota,
ippmOwnersIpAddressType,
ippmOwnersIpAddress, ippmOwnersIpAddress,
ippmOwnersEmail, ippmOwnersEmail,
ippmOwnersSMS, ippmOwnersSMS,
ippmOwnersStatus, ippmOwnersStatus
ippmOwnersIpAddressType,
ippmResultSharingMeasureOwner,
ippmResultSharingMeasureIndex,
ippmResultSharingGrantedOwner,
ippmResultSharingStatus
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The IPPM Owners Group" "The IPPM Owners Group"
::= { ippmGroups 7} ::= { ippmGroups 7}
ippmNotificationGroup NOTIFICATION-GROUP ippmNotificationGroup NOTIFICATION-GROUP
NOTIFICATIONS { NOTIFICATIONS {
ippmSingletonAlarm, ippmUpAndDownReport,
ippmCycleOfMeasureReport, ippmInBandReport,
ippmOutBandReport,
ippmAboveReport,
ippmBelowReport,
ippmEventsDurationExceededReport,
ippmCompletedMeasureReport, ippmCompletedMeasureReport,
ippmEventsDurationExceededAlarm, ippmAggrMeasureHistoryFull,
ippmHistoryLogFull, ippmNetMeasureHistoryFull,
ippmReportLogFull ippmReportLogFull
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The IPPM Notification Group" "The IPPM Notification Group"
::= { ippmGroups 8} ::= { ippmGroups 8}
END END
9. Security Considerations 8 Security Considerations
9.1. Privacy 8.1 VACM Access control
View Based Access Control, or VACM may be used to restrict access to
certain objects, or even object instances within tables. For example,
one may:
+ Give an 'administrator' write access to the ippmOwnersTable,
whereas all other users may only have read access
+ Give access to individual rows in the network measure, aggregated
measure, history, and report table to particular owners based upon
indexing on an 'owners name', and even upon a particular measure.
This will be illustrated below.
+ Give access of one owners measure, and associated results, to
another owner in order to create an aggregated measure based upon the
results.
8.1.1 Example of implementing VACM control for the IPPM-REPORTING-MIB
The following example illustrates how one could use VACM to restrict
access to particular objects within the MIB. It uses syntax specific
to a particular agent development toolkit, but may be generalized
using the concepts as defined in the VACM MIB.
In this example, we have two NMS users, namely user1=owner1 and
user2=owner2:
1) First we define the two users and their host addresses:
com2sec owner1 owner1computer@ private
com2sec owner2 owner2computer@ private
2) We then define SNMPv2c groups
group owner1 v2c owner1
group owner2 v2c owner2
view notif included ippmNotifications ff
3.1) For the user owner1, we now define the views for which he will
have read access
# covers PointOfMeasureTable SynchronizationTable and all scalars
view owner1read included ippmSystem ff
# covers OwnersTable
view owner1read included ippmOwners ff
# covers MetricsTable
view owner1read included ippmMeasure ff
# covers NetworkMeasureTable
view owner1read included
ippmNetMeasureOwner.6.111.119.110.101.114.49 ff.df.c0
# covers AggrMeasureTable
view owner1read included
ippmAggrMeasureOwner.6.111.119.110.101.114.49 ff.df.c0
3.2) We will now define the views for which owner1 will have write
access
view owner1write included
ippmAggrMeasureOwner.6.111.119.110.101.114.49 ff.df.c0
# covers ReportSetupTable
view owner1read included
ippmReportSetupOwner.6.111.119.110.101.114.49 ff.df.c0
view owner1write included
ippmReportSetupOwner.6.111.119.110.101.114.49 ff.df.c0
# covers HistoryTable
view owner1read included
ippmHistoryMeasureOwner.6.111.119.110.101.114.49 ff.df.c0
# covers ReportTable
view owner1read included
ippmReportOwner.6.111.119.110.101.114.49 ff.df.c0
3.3) For owner2, we will define the views for which he has read
access
view owner2read included ippmSystem ff
view owner2read included ippmOwners ff
view owner2read included ippmMeasure ff
# covers NetworkMeasureTable plus let's say the owner1 network
measure of index X
view owner2read included
ippmNetMeasureOwner.6.111.119.110.101.114.50 ff.df.c0
view owner2read included
ippmNetMeasureOwner.6.111.119.110.101.114.49.X ff.df.e0
# covers AggrMeasureTable plus let's say the OWNER1 aggregated
measure of index Y
view owner2read included
ippmAggrMeasureOwner.6.111.119.110.101.114.50 ff.df.c0
view owner2read included
ippmAggrMeasureOwner.6.111.119.110.101.114.49.Y ff.df.e0
3.4) For owner2, we will define the views for which he has write
access
view owner2write included
ippmAggrMeasureOwner.6.111.119.110.101.114.50 ff.df.c0
# covers ReportSetupTable
view owner2read included
ippmReportSetupOwner.6.111.119.110.101.114.50 ff.df.c0
view owner2write included
ippmReportSetupOwner.6.111.119.110.101.114.50 ff.df.c0
# covers HistoryTable plus OWNER1 related X network measure results
and OWNER1 related Y aggregated measure results
view owner2read included
ippmHistoryMeasureOwner.6.111.119.110.101.114.50 ff.df.c0
view owner2read included
ippmHistoryMeasureOwner.6.111.119.110.101.114.49.X ff.df.e0
view owner2read included
ippmHistoryMeasureOwner.6.111.119.110.101.114.49.Y ff.df.e0
# covers ReportTable
view owner2read included
ippmReportOwner.6.111.119.110.101.114.50 ff.df.c0
3.5) Now we give the two users access to the views defined above.
Note that owner1 and owner2 have read access to owner1read and
owner2read views respectively. They have write access to owner1write
and owner2write view respectively. And they both have access to all
the notifications.
access owner1 "" any noauth exact owner1read
owner1write notif
access owner2 "" any noauth exact owner2read
owner2write notif
8.2 Privacy
The privacy concerns of network measurement are intrinsically limited The privacy concerns of network measurement are intrinsically limited
by the active measurements. Unlike passive measurements, there can be by the active measurements. Unlike passive measurements, there can be
no release of existing user data. no release of existing user data.
9.2. Measurement aspects 8.3 Measurement aspects
Conducting Internet measurements raises both security and privacy Conducting Internet measurements raises both security and privacy
concerns. This memo does not specify an implementation of the concerns. This memo does not specify an implementation of the
metrics, so it does not directly affect the security of the Internet metrics, so it does not directly affect the security of the Internet
nor of applications that run on the Internet. However, nor of applications that run on the Internet. However,
implementations of these metrics must be mindful of security and implementations of these metrics must be mindful of security and
privacy concerns. privacy concerns.
There are two types of security concerns: potential harm caused by There are two types of security concerns: potential harm caused by
the measurements, and potential harm to the measurements. The the measurements, and potential harm to the measurements. The
skipping to change at page 68, line 10 skipping to change at page 75, line 5
measurements will not reflect actual user traffic. If an attacker measurements will not reflect actual user traffic. If an attacker
injects artificial traffic that is accepted as legitimate, the loss injects artificial traffic that is accepted as legitimate, the loss
rate will be artificially lowered. Therefore, the measurement rate will be artificially lowered. Therefore, the measurement
methodologies SHOULD include appropriate techniques to reduce the methodologies SHOULD include appropriate techniques to reduce the
probability measurement traffic can be distinguished from "normal" probability measurement traffic can be distinguished from "normal"
traffic. traffic.
Authentication techniques, such as digital signatures, may be used Authentication techniques, such as digital signatures, may be used
where appropriate to guard against injected traffic attacks. where appropriate to guard against injected traffic attacks.
9.3. Management aspects 8.4 Management aspects
There are a number of management objects defined in this MIB that There are a number of management objects defined in this MIB that
have a MAX-ACCESS clause of read-write and/or read-only. Such objects have a MAX-ACCESS clause of read-write and/or read-only. Such objects
may be considered sensitive or vulnerable in some network may be considered sensitive or vulnerable in some network
environments. The support for SET operations in a non-secure environments. The support for SET operations in a non-secure
environment without proper protection can have a negative effect on environment without proper protection can have a negative effect on
network operations. network operations.
SNMPv1 by itself is not a secure environment. Even if the network SNMPv1 by itself is not a secure environment. Even if the network
itself is secure (for example by using IPSec), even then, there is no itself is secure (for example by using IPSec), even then, there is no
skipping to change at page 69, line 5 skipping to change at page 75, line 30
features as provided by the SNMPv3 framework. Specifically, the use features as provided by the SNMPv3 framework. Specifically, the use
of the User-based Security Model RFC 2574 [18] and the View-based of the User-based Security Model RFC 2574 [18] and the View-based
Access Control Model RFC 2575 [21] is recommended. Access Control Model RFC 2575 [21] is recommended.
It is then a customer/user responsibility to ensure that the SNMP It is then a customer/user responsibility to ensure that the SNMP
entity giving access to an instance of this MIB, is properly entity giving access to an instance of this MIB, is properly
configured to give access to the objects only to those principals configured to give access to the objects only to those principals
(users) that have legitimate rights to indeed GET or SET (users) that have legitimate rights to indeed GET or SET
(change/create/delete) them. (change/create/delete) them.
10. Document management 9 Document management
10.1. Open issues
Describe incompatible bit combinations in IPPMreport and granted
metric
Run SMIlint.
Discussion on the management of the history size.
10.2. changes since release 00
+ Put in a description of the relationship of certain tables,
particularly the measure/network measure/aggregated measure table.
+ The TC GMTTimeStamp is the common type to define timestamp objects.
+ ippmHisoryTable index simplified: ippmHistoryTimestamp replaced
with ippmHistorySqceNdx in the index.
+ The MIB has been compiled using net-snmp.
+ Snmpadminstring replaces Displaystring.
+ IP addresses defined using INETaddresstype.
+ Sharing table is optional to permit the VACM framework to be used.
+ The description of the network measure table emphases that the set
up of network measure is not permitted using SNMP.
+ The TC StandardMetrics is removed and replaced with the table
ippmMetricsTable.
+ The table pointOfMeasureTable is added to describe multiples
interfaces devices
+ 5 tables have been changed to read/create: ippmOwnersTable,
ippmMeasureTable, ippmAggrMeasureTable, ippmResultSharingTable, and
ippmReportSetupTable.
+ IppmHistoryTable and ippmReportTable index reviews:
IppmHistorySqceNdx field added in the ippmHistoryTable.
INDEX modified. IppmHistorySqceNdx replaces IppmHistoryTimemark.
+ IppmSystem group refurbished:
IppmSystemTimer renamed ippmSystemTime.
Current and last synch event concept generalized in the
ippmSynchronizationTable.
10.3. Changes since release 01
+ Document Format:
Make use of the regular MIB object indentation.
+ Typos correction: ippmMeasureHystorySize and so on.
+ Time unit textual convention:
Enumerations listed in description clauses (e.g. ms, us, ns may
not be universally understood so explicitly named as millisecond,
microsecond, nanosecond)
+ Clarify ClearHistory and ClearReport definition:
OnReportDeliveryClearHistory and OnReportDeliveryClearReport
options
+ Added scalars ippmOnReportFullAction and ippmOnHistoryFullAction:
To take action when the tables are full. A scalar, which is read-
write and indicates the action to be taken when the log is full.
Options are: wrap, suspend, resume. Same was done for report
group.
+ Conformance section:
Added the MODULE-COMPLIANCE macro and the corresponding OBJECT-
GROUPS instances.
Added a compliance instances for proxy mode, proxy inter-domain
mode and probe mode.
+ PointOfMeasure:
Put in ippmPointOfMeasureMgmtAddrType-> InetAddressType with
ippmPointOfMeasureMgmtAddress-> InetAddress.
Changed point of measure address to be INET also.
+ Took out default point of measure address:
Added OwnersIpAddressType to be in pair with OwnersIpAddress
+ Added ippmSynchronizationResolution in the ppmSynchronizationTable:
It indicates the new time resolution (Henk request).
+ Added an object ippmReportSetupNotification in the report setup.
+ IppmHistoryIndex added in the history table:
To differentiate the result index from the test packet order. 9.1 Open issues
+ IppmReportIndex added in the report table: Defval 0 for an OID ?
To differentiate the result index from the test packet order. Usage of accessible-for-notify for an index ?
Subtype of InetAddress ?
+ Smilint: with the option -s -l6: 9.2 Changes done since release 02
Name length exceeded 32 chars:
Prefix:
+ ippmAggregatedMeasure -> ippmAggrMeasure;
+ IppmSystemSynchronizationDescription
-> ippmSystemSynchronizationDescr;
+ IppmReportSetupEventsDurationThreshold
-> ippmReportSetupDurationThreshold.
+ ippmNotifications identified under ippm + Security/VACM:
sharing table removed;
ippmMeasure merged with networkMeasure and AggrMeasure to have
all networkMeasure objects in read only.
Indexes belong to the table;
remove all reference to SNMPv1 ...inSNMPTrapPDU
+ TC OwnerString replaced with IppmOwnerString to fix a warning + System:
of the key length; ippmSystemOperationalStatus added
+ Gain 0 error and warning ! ippmSynchronizationTable adapted for proxy mode:
ippmPointOfMeasureIndex added to the index of
ippmSystemCurrentSynchronization removed from system
+ ippmAggrMeasureStatus removed: capabilities:
The status of the row is managed in the ippmMeasureTable ippmPointOfMeasureMetrics added to
IppmPointOfMeasureEntry;
ippmMetricType added to ippmMetricsTable;
+ Notifications: + Owners
definition clarified; ippmMetricMaxHistorySize replaced with quota in ippmOwnersTable;
ippmReportTimestamp added to notification
ippmEventsDurationExceededAlarm, ippmSingletonAlarm,
ippmCycleOfMeasureReport, ippmCompletedMeasureReport.
+ IppmNetworkMeasureEntry : + ippmOnHistoryFullAction replaced with resultsMgmt in aggr and network.;
ippmNetworkMeasurePoissonRate added as the average rates.
+ TypeP redefined as a SnmpAdminString instead of a raw OCTET STRING + network measure:
e.g: '080000080000000011020000'H -> "ip.ipip4". ippmNetMeasureOperState added to indicate the state of the network
open issue: measure
is there a need to indicate the number of parameters of the state;
protocol identifier ? "ip.ipip4.2" or "ip.ipip4" ? added burst mode;
state of the measure: nb of singletons collected and oper status
added;
+ TypePaddress Textual convention created: +aggregated metric:
Dst and Src value is a display string instead of a raw OCTET fast report added to get raw results by email;
STRING. It is the list of parameters of a TypeP.
e.g:
Src address TypeP is "ip.ipip4": 128.2.6.7 in 192.168.1.1.
Src value was '0A04C0A801010480020607'H.
Src is now "192.168.1.1 128.2.6.7".
open issue: + report setup:
onReportDeliveryClearHistory removed from IppmReportDefinition;
is there any potential parameter with one or more space + Map field added to network, aggr and report tables to help to map
inside ? on topology map or admin view.
11. References 10 References
[1] Bradner, S., "The Internet Standards Process -- Revision 3", BCP [1] Bradner, S., "The Internet Standards Process -- Revision 3", BCP
9, RFC 2026, October 1996. 9, RFC 2026, October 1996.
[2] Mahdavi J. and V. Paxson, "IPPM Metrics for Measuring [2] Harrington, D., Presuhn, R., and B. Wijnen, "An Architecture for
Connectivity", RFC 2678, September 1999.
[3] Almes, G., Kalidindi, S. and M. Zekauskas, "A One-way Delay
Metric for IPPM", RFC 2679, September 1999.
[4] Almes, G., Kalidindi, S. and M. Zekauskas, "A One-way Packet
Loss Metric for IPPM", RFC 2680, September 1999.
[5]Almes, G., Kalidindi, S. and M. Zekauskas, "A Round-trip Delay
Metric for IPPM.", RFC 2681, September 1999.
[6] Harrington, D., Presuhn, R., and B. Wijnen, "An Architecture for
Describing SNMP Management Frameworks", RFC 2571, April 1999. Describing SNMP Management Frameworks", RFC 2571, April 1999.
[7] Rose, M., and K. McCloghrie, "Structure and Identification of [3] Rose, M., and K. McCloghrie, "Structure and Identification of
Management Information for TCP/IP-based Internets", STD 16, RFC Management Information for TCP/IP-based Internets", STD 16, RFC
1155, May 1990. 1155, May 1990.
[8] Rose, M., and K. McCloghrie, "Concise MIB Definitions", STD 16, [4] Rose, M., and K. McCloghrie, "Concise MIB Definitions", STD 16,
RFC 1212, March 1991. RFC 1212, March 1991.
[9] M. Rose, "A Convention for Defining Traps for use with the SNMP", [5] M. Rose, "A Convention for Defining Traps for use with the SNMP",
RFC 1215, March 1991. RFC 1215, March 1991.
[10] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, [6] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose,
M., and S. Waldbusser, "Structure of Management Information M., and S. Waldbusser, "Structure of Management Information
Version 2 (SMIv2)", STD 58, RFC 2578, April 1999. Version 2 (SMIv2)", STD 58, RFC 2578, April 1999.
[11] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, [7] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose,
M., and S. Waldbusser, "Textual Conventions for SMIv2", STD 58, M., and S. Waldbusser, "Textual Conventions for SMIv2", STD 58,
RFC 2579, April 1999. RFC 2579, April 1999.
[12] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, [8] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose,
M., and S. Waldbusser, "Conformance Statements for SMIv2", STD 58, M., and S. Waldbusser, "Conformance Statements for SMIv2", STD 58,
RFC 2580, April 1999. RFC 2580, April 1999.
[13] Case, J., Fedor, M., Schoffstall, M., and J. Davin, "Simple [9] Case, J., Fedor, M., Schoffstall, M., and J. Davin, "Simple
Network Management Protocol", STD 15, RFC 1157, May 1990. Network Management Protocol", STD 15, RFC 1157, May 1990.
[14] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, [10] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser,
"Introduction to Community-based SNMPv2", RFC 1901, January 1996. "Introduction to Community-based SNMPv2", RFC 1901, January 1996.
[15] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, [11] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser,
"Transport Mappings for Version 2 of the Simple Network Management "Transport Mappings for Version 2 of the Simple Network Management
Protocol (SNMPv2)", RFC 1906, January 1996. Protocol (SNMPv2)", RFC 1906, January 1996.
[16]Case, J., Harrington D., Presuhn R., and B. Wijnen, "Message [12]Case, J., Harrington D., Presuhn R., and B. Wijnen, "Message
Processing and Dispatching for the Simple Network Management Processing and Dispatching for the Simple Network Management
Protocol (SNMP)", RFC 2572, April 1999. Protocol (SNMP)", RFC 2572, April 1999.
[17] Blumenthal, U., and B. Wijnen, "User-based Security Model (USM) [13] Blumenthal, U., and B. Wijnen, "User-based Security Model (USM)
for version 3 of the Simple Network Management Protocol (SNMPv3)", for version 3 of the Simple Network Management Protocol (SNMPv3)",
RFC 2574, April 1999. RFC 2574, April 1999.
[18] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Protocol [14] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Protocol
Operations for Version 2 of the Simple Network Management Protocol Operations for Version 2 of the Simple Network Management Protocol
(SNMPv2)", RFC 1905, January 1996. (SNMPv2)", RFC 1905, January 1996.
[19] Levi, D., Meyer, P., and B. Stewart, "SNMPv3 Applications", RFC [15] Levi, D., Meyer, P., and B. Stewart, "SNMPv3 Applications", RFC
2573, April 1999. 2573, April 1999.
[20] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-basedAccess [16] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-basedAccess
Control Model (VACM) for the Simple Network Management Protocol Control Model (VACM) for the Simple Network Management Protocol
(SNMP)", RFC 2575, April 1999. (SNMP)", RFC 2575, April 1999.
[21] Case, J., Mundy, R., Partain, D., and B. Stewart, "Introduction [17] Case, J., Mundy, R., Partain, D., and B. Stewart, "Introduction
to Version 3 of the Internet-standard Network Management to Version 3 of the Internet-standard Network Management
Framework", RFC 2570, April 1999. Framework", RFC 2570, April 1999.
12. Acknowledgments 11 Acknowledgments
A Kerbe. A Kerbe.
13. Authors Addresses 12 Authors Addresses
Emile STEPHAN Emile STEPHAN
France Telecom R & D France Telecom R & D
2 avenue Pierre Marzin 2 avenue Pierre Marzin
F-22307 Lannion cedex F-22307 Lannion cedex
Phone: (+ 33) 2 96 05 11 11 Phone: (+ 33) 2 96 05 11 11
Email: emile.stephan@francetelecom.com Email: emile.stephan@francetelecom.com
Jessie Jewitt Jessie Jewitt
France Telecom R & D France Telecom R & D
 End of changes. 

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