draft-ietf-ippm-reporting-mib-05.txt | draft-ietf-ippm-reporting-mib-06.txt | |||
---|---|---|---|---|
Network Working Group E. Stephan | ||||
Internet-Draft J. Jewitt | ||||
Expires: January 14, 2005 France Telecom R&D | ||||
July 16, 2004 | ||||
Network Working Group E. Stephan/J. Jewitt | IP Performance Metrics (IPPM) reporting Information Base (MIB) | |||
Internet Draft France Telecom R&D | draft-ietf-ippm-reporting-mib-06.txt | |||
Document: draft-ietf-ippm-reporting-mib-05.txt February, 2004 | ||||
Category: Standards Track | ||||
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. | |||
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 | |||
groups may also distribute working documents as Internet-Drafts. | other groups may also distribute working documents as | |||
Internet-Drafts. | ||||
Internet-Drafts are draft documents valid for a maximum of six months | Internet-Drafts are draft documents valid for a maximum of six months | |||
and may be updated, replaced, or made obsolete by other documents at | and may be updated, replaced, or obsoleted by other documents at any | |||
any time. It is inappropriate to use Internet- Drafts as reference | time. It is inappropriate to use Internet-Drafts as reference | |||
material or to cite them other than as "work in progress." | material or to cite them other than as "work in progress." | |||
The list of current Internet-Drafts can be accessed at | The list of current Internet-Drafts can be accessed at | |||
http://www.ietf.org/ietf/1id-abstracts.txt. | http://www.ietf.org/ietf/1id-abstracts.txt. | |||
The list of Internet-Draft Shadow Directories can be accessed at | The list of Internet-Draft Shadow Directories can be accessed at | |||
http://www.ietf.org/shadow.html. | http://www.ietf.org/shadow.html. | |||
This Internet-Draft will expire on January 14, 2005. | ||||
Copyright Notice | ||||
Copyright (C) The Internet Society (2004). All Rights Reserved. | ||||
Abstract | Abstract | |||
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 | |||
In particular, this MIB specifies the objects used for managing the | managing the results of the IPPM metrics measures, for pushing | |||
results of the IPPM metrics measures, for pushing alarms, and for | alarms, and for reporting the measures results. | |||
reporting the measures results. | ||||
Table of Contents | Table of Contents | |||
1. Introduction................................................2 | 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4 | |||
2. The IPPM Framework..........................................3 | 2. The IPPM Framework . . . . . . . . . . . . . . . . . . . . . . 4 | |||
3. The SNMP Management Framework...............................3 | 3. The Internet-Standard Management Framework . . . . . . . . . . 4 | |||
4. Overview....................................................5 | 4. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 | |||
4.1. Textual Conventions.........................................5 | 4.1 Textual Conventions . . . . . . . . . . . . . . . . . . . 6 | |||
4.2 Structure of the MIB.........................................8 | 4.1.1 OwnerString . . . . . . . . . . . . . . . . . . . . . 6 | |||
4.3 Row identification in an application namespace..............10 | 4.1.2 IppmOwnerIndex . . . . . . . . . . . . . . . . . . . . 6 | |||
4.4 Relationship of IPPM REPORTING MIB tables...................11 | 4.1.3 TimeUnit . . . . . . . . . . . . . . . . . . . . . . . 6 | |||
5 Measurement architectures...................................12 | 4.1.4 PacketType and PacketTypeAddres . . . . . . . . . . . 6 | |||
5.1 Proxy architecture..........................................12 | 4.1.5 GMTTimeStamp . . . . . . . . . . . . . . . . . . . . . 7 | |||
5.2 Reporting architecture......................................13 | 4.1.6 IppmStandardMetrics . . . . . . . . . . . . . . . . . 7 | |||
5.3 Gateway architecture........................................15 | 4.1.7 Report definition . . . . . . . . . . . . . . . . . . 8 | |||
5.4 Security....................................................15 | 4.2 Structure of the MIB . . . . . . . . . . . . . . . . . . . 9 | |||
6 Reporting mode integration..................................16 | 4.2.1 The ippmSystem Group . . . . . . . . . . . . . . . . . 9 | |||
6.1 Integration.................................................16 | 4.2.2 The ippmHistory Group . . . . . . . . . . . . . . . . 10 | |||
6.2 Setup of the network measure table..........................16 | 4.2.3 The ippmNetMeasure Group . . . . . . . . . . . . . . . 10 | |||
6.3 Setup of the aggregated measure table.......................16 | 4.2.4 The ippmAggrMeasure Group . . . . . . . . . . . . . . 10 | |||
6.4 Updating the history of the MIB.............................17 | 4.2.5 The Notification Group . . . . . . . . . . . . . . . . 11 | |||
6.5 Default value...............................................17 | 4.3 Row identification in an application namespace . . . . . . 11 | |||
7 Definition..................................................17 | 4.4 Relationship of IPPM REPORTING MIB tables . . . . . . . . 11 | |||
8 Security Considerations.....................................57 | 4.4.1 Relationship between the Owners Table and the | |||
8.1 VACM Access control.........................................57 | aggregated measure table . . . . . . . . . . . . . . . 11 | |||
8.2 Privacy.....................................................59 | 4.4.2 Relationship between the Network Measure Table and | |||
8.3 Measurement aspects.........................................59 | the Aggregated Measure Table . . . . . . . . . . . . . 12 | |||
8.4 Management aspects..........................................60 | 5. Measurement architectures . . . . . . . . . . . . . . . . . . 12 | |||
9 Document management.........................................61 | 5.1 Proxy architecture . . . . . . . . . . . . . . . . . . . . 13 | |||
9.1 Open issues.................................................61 | 5.2 Reporting architecture . . . . . . . . . . . . . . . . . . 14 | |||
9.2 Changes done since release 04...............................61 | 5.3 Gateway architecture . . . . . . . . . . . . . . . . . . . 15 | |||
9.3 Changes done since release 03...............................61 | 5.4 Security . . . . . . . . . . . . . . . . . . . . . . . . . 16 | |||
9.4 Changes done since release 02...............................62 | 6. Reporting mode integration . . . . . . . . . . . . . . . . . . 16 | |||
10 References..................................................62 | 6.1 Integration . . . . . . . . . . . . . . . . . . . . . . . 17 | |||
11 Acknowledgments.............................................64 | 6.2 Setup of the network measure table . . . . . . . . . . . . 17 | |||
12 Authors' Addresses..........................................64 | 6.3 Setup of the aggregated measure table . . . . . . . . . . 17 | |||
6.4 Updating the history of the MIB . . . . . . . . . . . . . 17 | ||||
6.5 Default value . . . . . . . . . . . . . . . . . . . . . . 17 | ||||
7. Definition . . . . . . . . . . . . . . . . . . . . . . . . . . 18 | ||||
8. Security Considerations . . . . . . . . . . . . . . . . . . . 70 | ||||
8.1 VACM Access control . . . . . . . . . . . . . . . . . . . 70 | ||||
8.1.1 Example of implementing VACM control for the | ||||
IPPM-REPORTING-MIB . . . . . . . . . . . . . . . . . . 70 | ||||
8.2 Privacy . . . . . . . . . . . . . . . . . . . . . . . . . 73 | ||||
8.3 Measurement aspects . . . . . . . . . . . . . . . . . . . 73 | ||||
8.4 Management aspects . . . . . . . . . . . . . . . . . . . . 74 | ||||
9. Document management . . . . . . . . . . . . . . . . . . . . . 74 | ||||
9.1 Open issues . . . . . . . . . . . . . . . . . . . . . . . 74 | ||||
9.2 Changes done since release 05 . . . . . . . . . . . . . . 75 | ||||
9.3 Changes done since release 04 . . . . . . . . . . . . . . 75 | ||||
9.4 Changes done since release 03 . . . . . . . . . . . . . . 75 | ||||
9.5 Changes done since release 02 . . . . . . . . . . . . . . 76 | ||||
10. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . 77 | ||||
11. References . . . . . . . . . . . . . . . . . . . . . . . . . 77 | ||||
11.1 Normative References . . . . . . . . . . . . . . . . . . . . 77 | ||||
11.2 Informative References . . . . . . . . . . . . . . . . . . . 77 | ||||
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 78 | ||||
Intellectual Property and Copyright Statements . . . . . . . . 79 | ||||
1. Introduction | 1. Introduction | |||
This memo defines a MIB for managing network measurements based upon | This memo defines a MIB for managing network measurements based upon | |||
the IP 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]. | [RFC2330]. | |||
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 | |||
Transport Area (See section 2), and in the Operations and Management | Transport Area (See section 2), and in the Operations and Management | |||
Area (See section 3). The reader should be familiar with these | Area (See section 3). The reader should be familiar with these | |||
documents. | documents. | |||
2. The IPPM Framework | 2. The IPPM Framework | |||
The IPPM Framework consists of 3 major components: | The IPPM Framework consists of 3 major components: | |||
A general framework for defining performance metrics, as described in | o A general framework for defining performance metrics, as described | |||
the Framework for IP Performance Metrics, RFC 2330 [2]; | in the Framework for IP Performance Metrics, RFC 2330 [RFC2330]; | |||
A set of standardized metrics which conform to this framework: The | ||||
IPPM Metrics for Measuring Connectivity, RFC 2678 [iii]; The One-way | ||||
Delay Metric for IPPM, RFC 2679 [iv]; The One-way Packet Loss Metric | ||||
for IPPM, RFC 2680 [v]; The Round-trip Delay Metric for IPPM, RFC | ||||
2681 [vi]; | ||||
Emerging metrics that are being specified in respect of this | o A set of standardized metrics which conform to this framework: | |||
framework. | ||||
3. The SNMP Management Framework | * IPPM Metrics for Measuring Connectivity, RFC 2678 [RFC2678]; | |||
The SNMP Management Framework consists of five major components: | * One-way Delay Metrics, RFC 2679 [RFC2679]; | |||
An overall architecture, described in RFC 2571 [2]. | * One-way Packet Loss Metrics, RFC 2680 [RFC2680]; | |||
Mechanisms for describing and naming objects and events for the | * Round-trip Delay Metrics, RFC 2681 [RFC2681]; | |||
purpose of management. The first version of this Structure of | ||||
Management Information (SMI) is called SMIv1 and described in STD 16, | ||||
RFC 1155 [3], STD 16, RFC 1212 [4] and RFC 1215 [5]. The second | ||||
version, called SMIv2, is described in STD 58, RFC 2578 [6], STD 58, | ||||
RFC 2579 [7] and STD 58, RFC 2580 [8]. | ||||
Message protocols for transferring management information. The | * One-way Loss Pattern Sample Metrics, RFC 3357 [RFC3357]; | |||
first version of the SNMP message protocol is called SNMPv1 and | ||||
described in STD 15, RFC 1157 [9]. A second version of the SNMP | ||||
message protocol, which is not an Internet standards track protocol, | ||||
is called SNMPv2c and described in RFC 1901 [10] and RFC 1906 [11]. | ||||
The third version of the message protocol is called SNMPv3 and | ||||
described in RFC 1906 [11], RFC 2572 [12] and RFC 2574 [13]. | ||||
Protocol operations for accessing management information. The | * IP Packet Delay Variation Metric, RFC 3393 [RFC3393]; | |||
first set of protocol operations and associated PDU formats is | ||||
described in STD 15, RFC 1157 [9]. A second set of protocol | ||||
operations and associated PDU formats is described in RFC 1905 [14]. | ||||
A set of fundamental applications described in RFC 2573 [15] and | * IPPM Metrics for periodic streams, RFC 3432 [RFC3432]; | |||
the view-based access control mechanism described in RFC 2575 [16]. | ||||
A more detailed introduction to the current SNMP Management Framework | o Emerging metrics that are being specified in respect of this | |||
can be found in RFC 2570 [17]. | framework. | |||
Managed objects are accessed via a virtual information store, termed | 3. The Internet-Standard Management Framework | |||
the Management Information Base or MIB. Objects in the MIB are | ||||
defined using the mechanisms defined in the SMI. | ||||
This memo specifies a MIB module that is compliant to the SMIv2. A | For a detailed overview of the documents that describe the current | |||
MIB conforming to the SMIv1 can be produced through the appropriate | Internet-Standard Management Framework, please refer to section 7 of | |||
translations. The resulting translated MIB must be semantically | RFC 3410 [RFC3410];. | |||
equivalent, except where objects or events are omitted because no | ||||
translation is possible (use of Counter64). Some machine readable | ||||
information in SMIv2 will be converted into textual descriptions in | ||||
SMIv1 during the translation process. However, this loss of machine | ||||
readable information is not considered to change the semantics of the | ||||
MIB. | ||||
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. MIB objects are generally | |||
defined using the subset of Abstract Syntax Notation One (ASN.1) | accessed through the Simple Network Management Protocol (SNMP). | |||
defined in the SMI. In particular, each object type is named by an | Objects in the MIB are defined using the mechanisms defined in the | |||
OBJECT IDENTIFIER, an administratively assigned name. | Structure of Management Information (SMI). This memo specifies a MIB | |||
module that is compliant to the SMIv2, which is described in STD 58, | ||||
The object type together with an object instance serves to uniquely | RFC 2578 [RFC2578];, STD 58, RFC 2579 [RFC2579]; and STD 58, RFC 2580 | |||
identify a specific instantiation of the object. For human | [RFC2580];. | |||
convenience, we often use a textual string, termed the descriptor, to | ||||
refer to the object type. | ||||
4. Overview | 4. Overview | |||
Although the number of measurement devices that implement IPPM | Although the number of measurement devices that implement IPPM | |||
metrics is growing, there is not currently any standardized | metrics is growing, there is not currently any standardized | |||
management interface to manage remotely the measurement of these | management interface to manage remotely the measurement of these | |||
metrics. This memo defines a Management Information Base for managing | metrics. This memo defines a Management Information Base for | |||
the measurement of IPPM metrics. | managing 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. | standardized metrics. | |||
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. The administrator may | identifies its measures in an owner namespace. The administrator may | |||
grant access to a measure, or set of measures to another owner via | grant access to a measure, or set of measures to another owner via | |||
view based access control. As a result, one owner may compute | view based access control. As a result, one owner may compute | |||
aggregated metrics on another ownerÆs network measures. | aggregated metrics on another owner's 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 | |||
REPORTING-MIB. This section is for informational purposes only, and | IPPM-REPORTING-MIB. This section is for informational purposes only, | |||
is intended to help specify the relationship among the test protocol, | and is intended to help specify the relationship among the test | |||
the control protocol and the 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. | provide access to results for the applications. | |||
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 | |||
Eight types of data are introduced as textual conventions in this | Eight types of data are introduced as textual conventions in this | |||
document: IppmOwnerString, IppmOwnerIndex, TimeUnit, PacketType, | document: IppmOwnerString, IppmOwnerIndex, TimeUnit, PacketType, | |||
PacketTypeAddress, GMTTimeStamp, IppmStandardMetrics and | PacketTypeAddress, GMTTimeStamp, IppmStandardMetrics and | |||
IppmMetricResultFilter. | IppmMetricResultFilter. | |||
4.1.1 IppmOwnerString | 4.1.1 OwnerString | |||
This octet string is used to represent the owners of the various | This octet string is used to represent the owners of the various | |||
measures and reports in the measurement system. | measures and reports in the measurement system. | |||
4.1.2 IppmOwnerIndex | 4.1.2 IppmOwnerIndex | |||
This integer identifies an instance of an object in an owner | This integer identifies an instance of an object in an owner | |||
namespace. | namespace. | |||
4.1.3 TimeUnit | 4.1.3 TimeUnit | |||
This textual convention is used to indicate a unit of time, ranging | This textual convention is used to indicate a unit of time, ranging | |||
from nanosecond, microsecond, millisecond, second, hour, day, and | from nanosecond, microsecond, millisecond, second, hour, day, and | |||
week. | week. | |||
4.1.4 PacketType and PacketTypeAddress | 4.1.4 PacketType and PacketTypeAddres | |||
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. It is important that one be conscious of the exact type | measurements. It is important that one be conscious of the exact | |||
of traffic being measured. | type of traffic being measured. | |||
The standardization of the management of IPPM measures relies on the | The standardization of the management of IPPM measures relies on the | |||
capability to unambiguously configure the type P of the packets, and | capability to unambiguously configure the type P of the packets, and | |||
the parameters of the protocol suites of the type P. | 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. | |||
skipping to change at page 7, line 8 | skipping to change at page 7, line 25 | |||
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 | |||
encoding rules of the protocol identifier, but without trailing | encoding rules of the protocol identifier, but without trailing | |||
parameters. | parameters. | |||
The packet encapsulation defined in an instance of PacketType embeds | The packet encapsulation defined in an instance of PacketType embeds | |||
the format of "Src" and "Dst" and their values. The type and value of | the format of "Src" and "Dst" and their values. The type and value | |||
these addresses depend on the type P of the packet, IP version 4, | of these addresses depend on the type P of the packet, IP version 4, | |||
IPV6, IP in IP... Both participate in the completion of the packet | IPV6, IP in IP... Both participate in the completion of the packet | |||
encoding. | encoding. | |||
Examples: | Examples: | |||
RFC2896 defines the protocol identifiers ip and ipip4. Should there | RFC2896 defines the protocol identifiers ip and ipip4. Should there | |||
be an Internet tunnel end-point of the IP address 192.168.1.1 in the | be an Internet tunnel end-point of the IP address 192.168.1.1 in the | |||
tunnel 128.2.6.7. the PacketType of the source address of the tunnel, | tunnel 128.2.6.7. the PacketType of the source address of the | |||
Src, is 'ip.ipip4'. The encoding of 'ip.ipip4' using the RFC2895 | tunnel, Src, is 'ip.ipip4'. The encoding of 'ip.ipip4' using the | |||
rules adds a trailer 2.0.0. It means that an instance of this | RFC2895 rules adds a trailer 2.0.0. It means that an instance of | |||
protocol identifier has 2 parameters, which values will be set only | this protocol identifier has 2 parameters, which values will be set | |||
when implemented. In the IPPM PacketType context these 2 parameters | only when implemented. In the IPPM PacketType context these 2 | |||
are provided in Src (or Dst). In the current example the value of Src | parameters are provided in Src (or Dst). In the current example the | |||
is "192.168.1.1 128.2.6.7". | value of Src is "192.168.1.1 128.2.6.7". | |||
4.1.5 GMTTimeStamp | 4.1.5 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.6 IppmStandardMetrics | 4.1.6 IppmStandardMetrics | |||
skipping to change at page 7, line 46 | skipping to change at page 8, line 14 | |||
an octet string to permit several metrics to be performed in a single | an octet string to permit several metrics to be performed in a single | |||
measure. | measure. | |||
4.1.7 Report definition | 4.1.7 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 | |||
defines actions that are taken on the measurement results. An action | defines actions that are taken on the measurement results. An action | |||
is performed either: | is performed either: | |||
+ For each result | For each result; | |||
+ On the results corresponding to a measurement cycle | ||||
+ On the results available at the measurement completion. | On the results corresponding to a measurement cycle; | |||
On the results available at the measurement completion. | ||||
To preserve the scalability of the whole measurement system, it | To preserve the scalability of the whole measurement system, it | |||
limits: | limits: | |||
+ The amount of data sent to the applications | The amount of data sent to the applications; | |||
+ The bandwidth consumption for uploading the result | ||||
+ The number of alarms sent to the applications | The bandwidth consumption for uploading the result; | |||
+ The amount of data saved in the point of measure | ||||
The number of alarms sent to the applications; | ||||
The amount of data saved in the point of measure. | ||||
Metric thresholds (low, high, inband, outband...) may be defined that | Metric thresholds (low, high, inband, outband...) may be defined that | |||
indicate when measure values should be reported. These values and | indicate when measure values should be reported. These values and | |||
their associated time may directly impact service availability. | their associated time may directly impact service availability. | |||
One may also want to report when particular values (i.e. constantly | One may also want to report when particular values (i.e. constantly | |||
over a threshold) repeatedly occur over a period of time. For | over a threshold) repeatedly occur over a period of time. For | |||
example, if one-way-day is constantly over a specified acceptable | example, if one-way-day is constantly over a specified acceptable | |||
threshold value for 10 minutes, then the values should be reported. | threshold value for 10 minutes, then the values should be reported. | |||
The combination of IPPM metric results, threshold events, and event | The combination of IPPM metric results, threshold events, and event | |||
filtering provides a very efficient mechanism to report measurement | filtering provides a very efficient mechanism to report measurement | |||
results, events, and alarms. | results, events, and alarms. | |||
A report is described using the TEXTUAL-CONVENTION | A report is described using the TEXTUAL-CONVENTION | |||
IppmMetricResultFilter. The report setup must not dramatically | IppmMetricResultFilter. The report setup must not dramatically | |||
increase the amount of data needed by the control protocol to setup a | increase the amount of data needed by the control protocol to setup a | |||
measure: | measure: | |||
+ A basic report is defined in the object ippmAggrMeasureFilter; | A basic report is defined in the object ippmAggrMeasureFilter; | |||
+ More elaborate reports are described using a metric threshold to | ||||
generate alarms and events. | More elaborate reports are described using a metric threshold to | |||
+ The generation of alarms and reports requires a management station | generate alarms and events; | |||
address to which the data will be sent. | ||||
+ SLA alarms are described using an events duration threshold. | The generation of alarms and reports requires a management station | |||
address to which the data will be sent; | ||||
SLA alarms are described using an events duration threshold. | ||||
The TEXTUAL-CONVENTION IppmMetricResultFilter specifies the list of | The TEXTUAL-CONVENTION IppmMetricResultFilter 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: | |||
- ippmSystem Group: | ippmSystem Group: | |||
+ ippmPointOfMeasureTable; | ippmPointOfMeasureTable; | |||
+ ippmSynchronizationTable; | ||||
+ ippmMetricsTable. | ||||
- ippmOwners Group: | ippmSynchronizationTable; | |||
- | ||||
+ ippmOwnersTable; | ||||
- ippmHistory Group: | ippmMetricsTable. | |||
- | ||||
+ ippmHistoryTable; | ||||
- ippmNetMeasure Group: | ippmOwners Group: | |||
- | ||||
+ ippmNetMeasureTable; | ||||
- ippmAggrMeasure Group: | ippmOwnersTable; | |||
- | ||||
+ ippmAggrMeasureTable. | ||||
- ippmNotifications | ippmHistory Group: | |||
ippmHistoryTable; | ||||
ippmNetMeasure Group: | ||||
ippmNetMeasureTable; | ||||
ippmAggrMeasure Group: | ||||
ippmAggrMeasureTable. | ||||
ippmNotifications | ||||
4.2.1 The ippmSystem Group | 4.2.1 The ippmSystem Group | |||
The implementation of this group is mandatory. | The implementation of this group is mandatory. | |||
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, as well | synchronization at a particular point of measure over time, as well | |||
as the system clock of the IPPM-REPORTING-MIB agent. | as the system clock of the IPPM-REPORTING-MIB agent. | |||
The table ippmPointOfMeasureTable describes the points of measure. | The table ippmPointOfMeasureTable describes the points of measure. | |||
The table ippmSynchronisationTable is critical to the implementation, | The table ippmSynchronisationTable is critical to the implementation, | |||
especially to be respectful of the Section 6.3. of the IPPM | especially to be respectful of the Section 6.3. of the IPPM | |||
Framework, which states that | Framework, which states that "Those who develop such measurement | |||
"Those who develop such measurement methodologies should strive to: | methodologies should strive to: | |||
+ Minimize their uncertainties/errors, | ||||
+ Understand and document the sources of uncertainty/error, and | Minimize their uncertainties/errors, | |||
+ Quantify the amounts of uncertainty/error." | ||||
Understand and document the sources of uncertainty/error, and | ||||
Quantify the amounts of uncertainty/error." | ||||
Consequently the table ippmSynchronisationTable makes these values | Consequently the table ippmSynchronisationTable makes these values | |||
available to compute reliable statistics. | available to compute reliable statistics. | |||
The table ippmMetricsTable list all the IPPM metrics using the | The table ippmMetricsTable list all the IPPM metrics using the | |||
registry order and describes their implementation (unit...). | registry order and describes their implementation (unit...). | |||
4.2.2 The ippmOwners Group | 4.2.1.1 The ippmOwners Group | |||
This group identifies an owner, or group of owners, that have access | This group identifies an owner, or group of owners, that have access | |||
to measurements on a probe. | to measurements on a probe. | |||
4.2.3 The ippmHistory Group | 4.2.2 The ippmHistory Group | |||
The results of any given measure are stored 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 | The indexing is such that there is an entry in this table for each | |||
result of a given measure for a given metric. | result of a given measure for a given metric. | |||
4.2.4 The ippmNetMeasure Group | 4.2.3 The ippmNetMeasure Group | |||
The control protocol registers a description of the existing network | The control protocol registers a description of the existing network | |||
measures in the ippmNetMeasureTable. | 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. | |||
ippmNetMeasureTable is a reflection of the configuration of the | ippmNetMeasureTable is a reflection of the configuration of the | |||
network measure. | network measure. | |||
4.2.5 The ippmAggrMeasure Group | 4.2.4 The ippmAggrMeasure Group | |||
ippmAggrMeasureTable is responsible for the aggregation of results. | ippmAggrMeasureTable is responsible for the aggregation of results. | |||
The aggregated results are saved in the ippmHistoryTable and may be | The aggregated results are saved in the ippmHistoryTable and may be | |||
used for higher aggregated measures. | used for higher aggregated measures. | |||
4.2.6 The Notification Group | 4.2.5 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 generate alarms, or reports, to management applications. | are used to generate alarms, or reports, to management applications. | |||
4.3 Row identification in an application namespace | 4.3 Row identification in an application namespace | |||
IPPM metrics measurement is a distributed task. An owner namespace is | IPPM metrics measurement is a distributed task. An owner namespace | |||
defined to avoid the need of polling to determine the next free | is defined to avoid the need of polling to determine the next free | |||
index, to avoid index collision when 2 applications are looking for a | index, to avoid index collision when 2 applications are looking for a | |||
new index as the same time; to increase the speed of the management | new index as the same time; to increase the speed of the management | |||
operations; to reduce bandwidth consumption and to reduce CPU load in | operations; to reduce bandwidth consumption and to reduce CPU load in | |||
the agents and applications. | the agents and applications. | |||
In a MIB, an object instance identifier is defined by the clause | In a MIB, an object instance identifier is defined by the clause | |||
INDEX of the table as a list of objects. | INDEX of the table as a list of objects. | |||
The owner namespace is defined in the INDEX as a couple of 2 objects | The owner namespace is defined in the INDEX as a couple of 2 objects | |||
where the type of first one is IppmOwnerString and the type of the | where the type of first one is IppmOwnerString and the type of the | |||
skipping to change at page 10, line 51 | skipping to change at page 11, line 37 | |||
The second term is an private index managed by the owner. This index | The second term is an private index managed by the owner. This index | |||
value is unique in an owner namespace. Before the creation of an | value is unique in an owner namespace. Before the creation of an | |||
instance the creator pick up an IppmOwnerIndex value not in use. | instance the creator pick up an IppmOwnerIndex value not in use. | |||
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. Moreover this allows the owner to | fields exists in the MIB tables. Moreover this allows the owner to | |||
use the same instance identifier over a set of IPPM MIB | use the same instance identifier over a set of IPPM MIB | |||
implementations. | implementations. | |||
Measurements are requested by management applications. An instance of | Measurements are requested by management applications. An instance | |||
an object managed by a management station is identified by the | of 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. | |||
4.4 Relationship of IPPM REPORTING 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 | |||
REPORTING 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 aggregated | 4.4.1 Relationship between the Owners Table and the aggregated measure | |||
measure table | 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 remotely aggregated measures in an IPPM agent, or read the | activate remotely aggregated measures in an IPPM agent, or read the | |||
existing network measures. | existing network measures. | |||
It is recommended to make use of "view based access control" in order | It is recommended to make use of "view based access control" in order | |||
to restrict access to this table. For example, the master user | to restrict access to this table. For example, the master user | |||
"administrator" 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 "administrator" can then setup the list of other users that | The user "administrator" can then setup the list of other users that | |||
skipping to change at page 11, line 38 | skipping to change at page 12, line 25 | |||
above. | above. | |||
An owner may have multiple corresponding entries in the network and | An owner may have multiple corresponding entries in the network and | |||
aggregated measure tables. Each entry in a measure table is | aggregated measure tables. Each entry in a measure table is | |||
associated with one, and only one, entry in the owners' table. That | associated with one, and only one, entry in the owners' table. That | |||
is to say, that a 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 a | 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 | 4.4.2 Relationship between the Network Measure Table and the Aggregated | |||
Aggregated Measure Table | Measure Table | |||
The network measure table is read-only, thus entries in this table | The network measure table is read-only, thus entries in this table | |||
must 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. However, the "owner" | directly interacts with the points of measure. However, the "owner" | |||
of the measure must be defined in the owners table. It may be either | of the measure must be defined in the owners table. It may be either | |||
configured directly, or exported to the agent by the external | configured directly, or exported to the agent by the external | |||
measurement tool. | measurement tool. | |||
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 | aggregated measures (such as average, minimum, maximum...) on | |||
existing measures. An owner may even create aggregated measures on | existing measures. An owner may even create aggregated measures on | |||
skipping to change at page 12, line 7 | skipping to change at page 12, line 45 | |||
configured directly, or exported to the agent by the external | configured directly, or exported to the agent by the external | |||
measurement tool. | measurement tool. | |||
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 | aggregated measures (such as average, minimum, maximum...) on | |||
existing measures. An owner may even create aggregated measures on | existing measures. An owner may even create aggregated measures on | |||
network measures that are owned by other owners. However, it is | network measures that are owned by other owners. However, it is | |||
recommended to use view based access control to grant access of | recommended to use view based access control to grant access of | |||
network measures to other owners in the system. | network measures to other owners in the system. | |||
5 Measurement architectures | 5. Measurement architectures | |||
There are three main measurement architectures. | There are three main measurement architectures. | |||
5.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 NMSÆs query the IPPM-REPORTING- | In this architecture, the different NMS's query the | |||
MIB agent for measurements. The agent controls whether the NMS is | IPPM-REPORTING-MIB agent for measurements. The agent controls | |||
granted access to perform the measure requested. Each NMS may access | whether the NMS is granted access to perform the measure requested. | |||
the results of its measurements in the IPPM-REPORTING-MIB history | Each NMS may access the results of its measurements in the | |||
table. | IPPM-REPORTING-MIB history 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 on the control protocol nor on | In this mode the NMS does not depend on the control protocol nor on | |||
the test protocol. The entities involved in the measurement do not | the test protocol. The entities involved in the measurement do not | |||
need to implement the IPPM-REPORTING-MIB nor SNMP. This mode allows | need to implement the IPPM-REPORTING-MIB nor SNMP. This mode allows | |||
for lightweight implementation in the point of measure, and also for | for lightweight implementation in the point of measure, and also for | |||
heterogeneous control protocols to coexist. | heterogeneous control protocols to coexist. | |||
skipping to change at page 13, line 13 | skipping to change at page 14, line 11 | |||
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. | |||
5.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 Network Measure | protocol creates a measure in the IPPM-REPORTING-MIB Network Measure | |||
table. The table in question may be not accessible by SNMP. In this | table. The table in question may be not accessible by SNMP. In this | |||
case, a list of the measure identifiers (owner, index) is handled by | case, a list of the measure identifiers (owner, index) is handled by | |||
the measurement software. | the measurement software. | |||
Each timestamped result of the measure is logged in the IPPM- | Each timestamped result of the measure is logged in the | |||
REPORTING-MIB History table in order to allow read access to the | IPPM-REPORTING-MIB History table in order to allow read access to the | |||
NMSÆs and event handling. | NMS's and event handling. | |||
On completion, the measurement results are managed according to the | On completion, the measurement results are managed according to the | |||
measure setup: | measure setup: | |||
+ The results may be sent to an NMS; | ||||
+ They may be dropped from the IPPM-REPORTING-MIB History table. | The results may be sent to an NMS; | |||
They may be dropped from the IPPM-REPORTING-MIB History table. | ||||
In this mode, it is recommended to use an SNMPv2 Inform PDU to send | In this mode, it is recommended to use an SNMPv2 Inform PDU to send | |||
reporting events because it ensures that the entire block of the | reporting events because it ensures that the entire block of the | |||
result is received. There is no control using SNMP Trap PDU. | result is received. There is no control using SNMP Trap PDU. | |||
5.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 | | | | |||
. | | | Gateway | | | | | | | 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 | |||
gateway 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 IPPM REPORTING MIB | directly consults the result in the corresponding IPPM REPORTING MIB | |||
agent of the points of measure. | agent of the points of measure. | |||
5.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 setup relies on the control and | The control of the measurement setup relies on the control and the | |||
the test protocol security mechanisms; | test protocol security mechanisms; | |||
+ The control of access to the results depends on the SNMP | ||||
security mechanisms such as community strings, but may also be | The control of access to the results depends on the SNMP security | |||
restricted using VACM for customized access. | 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. | |||
6 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 metric measures; | Define the configuration of the IPPM metric measures; | |||
+ Define the format of the results of the measure; | ||||
+ Define the report of the IPPM metric measure results. | Define the format of the results of the measure; | |||
Define the report of the IPPM metric measure results. | ||||
It introduces the concept of owner namespace to allow for fast | It introduces the concept of owner namespace to allow for fast | |||
configuration and reporting across multiple points of measurement. | configuration and reporting across multiple points of measurement. | |||
A measure is a distributed object describing a task to be performed | A measure is a distributed object describing a task to be performed | |||
by the control and the test protocols. A measure is identified by its | by the control and the test protocols. A measure is identified by | |||
owner and its owner index. This identifier is the same in all the | its owner and its owner index. This identifier is the same in all | |||
points of measure. As the owner chooses the index, there is no need | the points of measure. As the owner chooses the index, there is no | |||
for negotiation between the NMS and the points of measure before | need 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. | |||
6.1 Integration | 6.1 Integration | |||
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 consists in pushing the network measure setup/teardown | protocols consists in pushing the network measure setup/teardown | |||
parameters and the result values from the measurement software to the | parameters and the result values from the measurement software to the | |||
IPPM-REPORTING-MIB agent. | IPPM-REPORTING-MIB agent. | |||
6.2 Setup of the network measure table | 6.2 Setup of the network measure table | |||
The measurement system updates the MIB on creation of a network measure. | The measurement system updates the MIB on creation of a network | |||
measure. | ||||
6.3 Setup of the aggregated measure table | 6.3 Setup of the aggregated measure table | |||
There are 2 ways to setup an aggregated measure: | There are 2 ways to setup an aggregated measure: The measurement | |||
system updates the MIB on creation of an aggregated measure; An SNMP | ||||
The measurement system updates the MIB on creation of an aggregated | application creates an aggregated measure. | |||
measure; | ||||
An SNMP application creates an aggregated measure. | ||||
6.4 Updating the history of the 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 REPORTING 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 SNMP agent. The protocol | result from the measurement software to the SNMP agent. The protocol | |||
that provides the result may be the control protocol, or the test | that provides the result may be the control protocol, or the test | |||
protocol, or another mechanism. | protocol, or another mechanism. | |||
6.5 Default value | 6.5 Default value | |||
The default values correspond to IP version 4. | The default values correspond to IP version 4. | |||
7 Definition | 7. Definition | |||
IPPM-REPORTING-MIB DEFINITIONS ::= BEGIN | IPPM-REPORTING-MIB DEFINITIONS ::= BEGIN | |||
IMPORTS | IMPORTS | |||
mib-2, | ||||
MODULE-IDENTITY, | MODULE-IDENTITY, | |||
NOTIFICATION-TYPE, | NOTIFICATION-TYPE, | |||
OBJECT-TYPE, | OBJECT-TYPE, | |||
experimental ,Integer32, zeroDotZero, Counter64, Unsigned32 | Integer32, zeroDotZero, Counter64, Unsigned32 | |||
FROM SNMPv2-SMI | FROM SNMPv2-SMI | |||
InetAddressType, | InetAddressType, | |||
InetAddress | InetAddress | |||
FROM INET-ADDRESS-MIB | FROM INET-ADDRESS-MIB | |||
SnmpAdminString | SnmpAdminString | |||
FROM SNMP-FRAMEWORK-MIB | FROM SNMP-FRAMEWORK-MIB | |||
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 | ippm MODULE-IDENTITY | |||
LAST-UPDATED "200402121200Z" -- 12 February 2004 | LAST-UPDATED "200407151200Z" -- 15 July 2004 | |||
ORGANIZATION "France Telecom - R&D" | ORGANIZATION "IP Performance Metrics (ippm) Working Group" | |||
CONTACT-INFO | CONTACT-INFO | |||
"Emile Stephan | "Emile Stephan | |||
France Telecom - R&D | France Telecom - R&D | |||
2, Avenue Pierre Marzin | ||||
Technopole Anticipa | ||||
22307 Lannion Cedex | ||||
FRANCE | ||||
Tel: + 33 2 96 05 36 10 | ||||
E-mail: emile.stephan@francetelecom.com | E-mail: emile.stephan@francetelecom.com | |||
Jessie Jewitt | Jessie Jewitt | |||
France Telecom - R&D | France Telecom - R&D | |||
801 Gateway Blvd. Suit 500 | E-mail : jessie.jewitt@rd.francetelecom.com | |||
South San Francisco, CA 94080 | ||||
Tel : 1 650 875-1524 | ||||
E-mail : jessie.jewitt@rd.francetelecom.com" | ||||
Comments about this document should be send to the IPPM | ||||
working group mailing list at ippm@ietf.org. | ||||
" | ||||
DESCRIPTION | DESCRIPTION | |||
" This memo defines a portion of the Management Information Base | "This memo defines a portion of the Management Information | |||
(MIB) for use with network management protocols in TCP/IP-based | Base (MIB) for use with network management protocols in | |||
internets. In particular, it specifies the objects used for | TCP/IP-based internets. In particular, it specifies the | |||
managing the results of the IPPM metrics measurements, alarms and | objects used for managing the results of the IPPM metrics | |||
reporting of measurement results." | measurements, alarms and 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" | |||
skipping to change at page 18, line 46 | skipping to change at page 19, line 29 | |||
DESCRIPTION | DESCRIPTION | |||
"Adaptation to VACM, preparation of the final version" | "Adaptation to VACM, preparation of the final version" | |||
REVISION "200310241200Z" -- 24 October 2003 | REVISION "200310241200Z" -- 24 October 2003 | |||
DESCRIPTION | DESCRIPTION | |||
"Modifications based upon feedback from experimental | "Modifications based upon feedback from experimental | |||
implementation." | implementation." | |||
REVISION "200402121200Z" -- 12 February 2004 | REVISION "200402121200Z" -- 12 February 2004 | |||
DESCRIPTION | DESCRIPTION | |||
"Modifications based upon feedback 58th IETF: The report group | "Modifications based upon feedback 58th IETF: The report | |||
and the corresponding notification are removed." | group and the corresponding notification are removed." | |||
::= { experimental 10001 } -- XXX to be assigned by IANA | ||||
ippm OBJECT IDENTIFIER ::= { experimental 10000 } | REVISION "200407151200Z" -- 15 July 2004 | |||
DESCRIPTION | ||||
"Rewritten in XML and Clean up." | ||||
::= { mib-2 XXX } | ||||
-- RFC Ed.: replace XXX with IANA-assigned number | ||||
-- & remove this note | ||||
-- | -- | |||
-- TEXTUAL-CONVENTION | -- TEXTUAL-CONVENTION | |||
-- | -- | |||
IppmOwnerString ::= TEXTUAL-CONVENTION | IppmOwnerString ::= TEXTUAL-CONVENTION | |||
STATUS current | STATUS current | |||
DESCRIPTION | DESCRIPTION | |||
"The owner namespace is defined in the INDEX of a table as a | "The owner namespace is defined in the INDEX of a table as a | |||
couple of 2 objects where the type of the first one is | couple of 2 objects where the type of the first one is | |||
IppmOwnerString and the type of the second is IppmOwnerIndex. | IppmOwnerString and the type of the second is IppmOwnerIndex. | |||
IppmOwnerString is an OwnerString which length is limited to 32 | IppmOwnerString is an OwnerString which length is limited to | |||
bytes." | 32 bytes." | |||
SYNTAX OCTET STRING (SIZE (0..32)) | SYNTAX OCTET STRING (SIZE (0..32)) | |||
IppmOwnerIndex ::= TEXTUAL-CONVENTION | IppmOwnerIndex ::= TEXTUAL-CONVENTION | |||
STATUS current | STATUS current | |||
DESCRIPTION | DESCRIPTION | |||
"The owner namespace is defined in the INDEX of a table as a | "The owner namespace is defined in the INDEX of a table as a | |||
couple of 2 objects where the type of first one is | couple of 2 objects where the type of first one is | |||
IppmOwnerString and the type of the second is IppmOwnerIndex. | IppmOwnerString and the type of the second is IppmOwnerIndex. | |||
An object of type IppmOwnerIndex uniquely identifies a row of a | An object of type IppmOwnerIndex uniquely identifies a row of | |||
table inside an owner namespace. | a table inside an owner namespace. | |||
Inside one namespace several objects of type IppmOwnerIndex | Inside one namespace several objects of type IppmOwnerIndex | |||
coexist and share the IppmOwnerIndex range of values to provide a | coexist and share the IppmOwnerIndex range of values to | |||
unique instance identifier. | provide an unique instance identifier. | |||
" | " | |||
SYNTAX Unsigned32 (1.. 65535) | SYNTAX Unsigned32 (1.. 65535) | |||
TimeUnit ::= TEXTUAL-CONVENTION | TimeUnit ::= TEXTUAL-CONVENTION | |||
STATUS current | STATUS current | |||
DESCRIPTION | DESCRIPTION | |||
"A enumerated list of time units." | "A enumerated list of time units." | |||
SYNTAX INTEGER { | SYNTAX INTEGER { | |||
week(1), | week(1), | |||
day(2), | day(2), | |||
skipping to change at page 23, line 18 | skipping to change at page 26, line 18 | |||
logBelowValue(4), | logBelowValue(4), | |||
logUpAndDownValue(5) | logUpAndDownValue(5) | |||
} | } | |||
-- | -- | |||
-- IPPM Notifications | -- IPPM Notifications | |||
-- | -- | |||
ippmNotifications OBJECT IDENTIFIER ::= { ippm 0 } | ippmNotifications OBJECT IDENTIFIER ::= { ippm 0 } | |||
-- | -- | |||
-- IPPM MIB Object definitions | ||||
-- | -- | |||
ippmConformance OBJECT IDENTIFIER ::= { ippm 1 } | ippmMibObjects OBJECT IDENTIFIER ::= { ippm 1 } | |||
ippmSystem OBJECT IDENTIFIER ::= { ippmMibObjects 1 } | ||||
ippmOwners OBJECT IDENTIFIER ::= { ippmMibObjects 2 } | ||||
ippmHistory OBJECT IDENTIFIER ::= { ippmMibObjects 3 } | ||||
ippmNetMeasure OBJECT IDENTIFIER ::= { ippmMibObjects 4 } | ||||
ippmAggrMeasure OBJECT IDENTIFIER ::= { ippmMibObjects 5 } | ||||
-- | -- | |||
-- IPPM Conformance | ||||
-- | -- | |||
ippmConformance OBJECT IDENTIFIER ::= { ippm 2 } | ||||
ippmSystem OBJECT IDENTIFIER ::= { ippmReportingMib 1 } | ||||
ippmOwners OBJECT IDENTIFIER ::= { ippmReportingMib 2 } | ||||
ippmHistory OBJECT IDENTIFIER ::= { ippmReportingMib 3 } | ||||
ippmNetMeasure OBJECT IDENTIFIER ::= { ippmReportingMib 4 } | ||||
ippmAggrMeasure OBJECT IDENTIFIER ::= { ippmReportingMib 5 } | ||||
-- | -- | |||
-- 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 system running the IPPM REPORTING MIB | "The current time of the system running the IPPM REPORTING MIB | |||
SNMP agent. When the agent is running in proxy mode, it is the | SNMP agent. When the agent is running in proxy mode, it is the | |||
current time of the proxy agent. | current time of the proxy agent. | |||
When the agent is located in the probe, it is the current time of | When the agent is located in the probe, it is the current time | |||
the probe agent. " | 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 running the IPPM REPORTING MIB | used to synchronize the system running the IPPM REPORTING MIB | |||
SNMP agent. | SNMP agent. | |||
skipping to change at page 24, line 49 | skipping to change at page 28, line 16 | |||
ippmSystemClockResolution OBJECT-TYPE | ippmSystemClockResolution OBJECT-TYPE | |||
SYNTAX Unsigned32 | SYNTAX Unsigned32 | |||
UNITS "Nanoseconds" | UNITS "Nanoseconds" | |||
MAX-ACCESS read-only | MAX-ACCESS read-only | |||
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 nanosecond. For example, | used for the measures . The unit is the nanosecond. 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 10 msec. So its resolution is | msec, and thus have a resolution of 10 msec. So its resolution | |||
10000000 nanoseconds and the value of ippmSystemClockResolution | is 10000000 nanoseconds and the value of | |||
is 10000000." | ippmSystemClockResolution is 10000000." | |||
::= { ippmSystem 4 } | ::= { ippmSystem 4 } | |||
ippmSystemOperationalStatus OBJECT-TYPE | ippmSystemOperationalStatus OBJECT-TYPE | |||
SYNTAX INTEGER { | SYNTAX INTEGER { | |||
unknown(0), | unknown(0), | |||
up(1), | up(1), | |||
down(2) | down(2) | |||
} | } | |||
MAX-ACCESS read-only | MAX-ACCESS read-only | |||
STATUS current | STATUS current | |||
DESCRIPTION | DESCRIPTION | |||
"This object describes the status of the system running the IPPM | "This object describes the status of the system running the IPPM | |||
REPORTING MIB SNMP agent. It does not describe end point measurement | REPORTING MIB SNMP agent. It does not describe end point | |||
status. | measurement status: | |||
unknown(0) means the service is unknown. | unknown(0) means the service is unknown. | |||
up(1) means the service is operational and available for general | up(1) means the service is operational and available for | |||
use. | general use. | |||
down(2) means the agent is not available for use. | down(2) means the agent is not available for use. | |||
" | " | |||
::= { ippmSystem 5 } | ::= { ippmSystem 5 } | |||
ippmSystemAggregatedMetrics OBJECT-TYPE | ippmSystemAggregatedMetrics OBJECT-TYPE | |||
SYNTAX IppmStandardMetrics | SYNTAX IppmStandardMetrics | |||
MAX-ACCESS read-only | MAX-ACCESS read-only | |||
STATUS current | STATUS current | |||
DESCRIPTION | DESCRIPTION | |||
" ippmSystemAggregatedMetrics lists the aggregated metrics that | " ippmSystemAggregatedMetrics lists the aggregated metrics that | |||
skipping to change at page 25, line 31 | skipping to change at page 29, line 4 | |||
ippmSystemAggregatedMetrics OBJECT-TYPE | ippmSystemAggregatedMetrics OBJECT-TYPE | |||
SYNTAX IppmStandardMetrics | SYNTAX IppmStandardMetrics | |||
MAX-ACCESS read-only | MAX-ACCESS read-only | |||
STATUS current | STATUS current | |||
DESCRIPTION | DESCRIPTION | |||
" ippmSystemAggregatedMetrics lists the aggregated metrics that | " ippmSystemAggregatedMetrics lists the aggregated metrics that | |||
are performed in the SNMP agent instead of in the point of | are performed in the SNMP agent instead of in the point of | |||
measure." | measure." | |||
::= { ippmSystem 6 } | ::= { ippmSystem 6 } | |||
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 | |||
the points of measure. Each event is described in an | of 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 7 } | ::= { ippmSystem 7 } | |||
ippmSynchronizationEntry OBJECT-TYPE | ippmSynchronizationEntry OBJECT-TYPE | |||
SYNTAX IppmSynchronizationEntry | SYNTAX IppmSynchronizationEntry | |||
MAX-ACCESS not-accessible | MAX-ACCESS not-accessible | |||
STATUS current | STATUS current | |||
DESCRIPTION | DESCRIPTION | |||
skipping to change at page 26, line 37 | skipping to change at page 30, line 13 | |||
STATUS current | STATUS current | |||
DESCRIPTION | DESCRIPTION | |||
"The time when the synchronization event occurs." | "The time when the synchronization event occurs." | |||
::= { ippmSynchronizationEntry 2 } | ::= { ippmSynchronizationEntry 2 } | |||
ippmSynchronizationStratum OBJECT-TYPE | ippmSynchronizationStratum OBJECT-TYPE | |||
SYNTAX Unsigned32 | SYNTAX Unsigned32 | |||
MAX-ACCESS read-only | MAX-ACCESS read-only | |||
STATUS current | STATUS current | |||
DESCRIPTION | DESCRIPTION | |||
"The stratum level of the clock computed when the synchronization | "The stratum level of the clock computed when the | |||
event occurs." | synchronization event occurs." | |||
::= { ippmSynchronizationEntry 3 } | ::= { ippmSynchronizationEntry 3 } | |||
ippmSynchronizationResolution OBJECT-TYPE | ippmSynchronizationResolution OBJECT-TYPE | |||
SYNTAX Unsigned32 | SYNTAX Unsigned32 | |||
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 | |||
occurred." | event 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 | |||
" This table is the list of measurement end points available in | " This table is the list of measurement end points available | |||
the measurement system. | in the measurement system. | |||
Proxy mode: | Proxy mode: | |||
It is the list of the measurement end points of the set of probes | It is the list of the measurement end points of the set of | |||
for which the IPPM agent provides an SNMP interface. | probes for which the IPPM agent provides an SNMP interface. | |||
IPPM MIB implemented in a probe: | IPPM MIB implemented in a probe: | |||
It is the list of the measurement end points of the probe. | It is the list of the measurement end points of the probe. | |||
The ippmPointOfMeasureTable content is read only. This implies | The ippmPointOfMeasureTable content is read only. This | |||
that the measurement software handles the table internally | implies that the measurement software handles the table | |||
internally ippmPointOfMeasureTable is mandatory." | ||||
ippmPointOfMeasureTable is mandatory." | ||||
::= { ippmSystem 8 } | ::= { ippmSystem 8 } | |||
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 some middleware in | " An entry may be the management address of some 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. | An entry describes the capability of a point of measure. | |||
ippmPointOfMeasureMetrics lists the metrics handles by the point | ippmPointOfMeasureMetrics lists the metrics handles by the | |||
of measure." | point of measure." | |||
INDEX { ippmPointOfMeasureIndex } | INDEX { ippmPointOfMeasureIndex } | |||
::= { ippmPointOfMeasureTable 1 } | ::= { ippmPointOfMeasureTable 1 } | |||
IppmPointOfMeasureEntry ::= SEQUENCE { | IppmPointOfMeasureEntry ::= SEQUENCE { | |||
ippmPointOfMeasureIndex Unsigned32, | ippmPointOfMeasureIndex Unsigned32, | |||
ippmPointOfMeasureMgmtAddrType InetAddressType, | ippmPointOfMeasureMgmtAddrType InetAddressType, | |||
ippmPointOfMeasureMgmtAddress InetAddress, | ippmPointOfMeasureMgmtAddress InetAddress, | |||
ippmPointOfMeasureTestAddrType InetAddressType, | ippmPointOfMeasureTestAddrType InetAddressType, | |||
ippmPointOfMeasureTestAddress InetAddress, | ippmPointOfMeasureTestAddress InetAddress, | |||
ippmPointOfMeasureMetrics IppmStandardMetrics | ippmPointOfMeasureMetrics IppmStandardMetrics | |||
} | } | |||
ippmPointOfMeasureIndex OBJECT-TYPE | ippmPointOfMeasureIndex OBJECT-TYPE | |||
SYNTAX Unsigned32 (1 .. 65535) | SYNTAX Unsigned32 (1 .. 65535) | |||
MAX-ACCESS not-accessible | MAX-ACCESS not-accessible | |||
STATUS current | STATUS current | |||
DESCRIPTION | DESCRIPTION | |||
"A local index that identifies an entry in the point of measure | "A local index that identifies an entry in the point of | |||
table." | measure 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 address type associated with the 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 } | |||
ippmPointOfMeasureTestAddrType OBJECT-TYPE | ippmPointOfMeasureTestAddrType OBJECT-TYPE | |||
SYNTAX InetAddressType | SYNTAX InetAddressType | |||
skipping to change at page 28, line 36 | skipping to change at page 32, line 26 | |||
DESCRIPTION | DESCRIPTION | |||
"Defines the address type of the measurement interface of the | "Defines the address type of the measurement interface of the | |||
point of measure." | point of measure." | |||
::= { ippmPointOfMeasureEntry 4 } | ::= { ippmPointOfMeasureEntry 4 } | |||
ippmPointOfMeasureTestAddress OBJECT-TYPE | ippmPointOfMeasureTestAddress 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 measurement interface for the point | "Specifies the address of the measurement interface for the | |||
of measure." | point of measure." | |||
::= { ippmPointOfMeasureEntry 5} | ::= { ippmPointOfMeasureEntry 5} | |||
ippmPointOfMeasureMetrics OBJECT-TYPE | ippmPointOfMeasureMetrics OBJECT-TYPE | |||
SYNTAX IppmStandardMetrics | SYNTAX IppmStandardMetrics | |||
MAX-ACCESS read-only | MAX-ACCESS read-only | |||
STATUS current | STATUS current | |||
DESCRIPTION | DESCRIPTION | |||
" ippmPointOfMeasureMetrics lists the metrics this point of | " ippmPointOfMeasureMetrics lists the metrics this point of | |||
measure implements." | measure implements." | |||
::= { ippmPointOfMeasureEntry 6 } | ::= { ippmPointOfMeasureEntry 6 } | |||
skipping to change at page 29, line 4 | skipping to change at page 32, line 42 | |||
MAX-ACCESS read-only | MAX-ACCESS read-only | |||
STATUS current | STATUS current | |||
DESCRIPTION | DESCRIPTION | |||
" ippmPointOfMeasureMetrics lists the metrics this point of | " ippmPointOfMeasureMetrics lists the metrics this point of | |||
measure implements." | measure implements." | |||
::= { ippmPointOfMeasureEntry 6 } | ::= { ippmPointOfMeasureEntry 6 } | |||
ippmMetricsTable OBJECT-TYPE | ippmMetricsTable OBJECT-TYPE | |||
SYNTAX SEQUENCE OF IppmMetricsEntry | SYNTAX SEQUENCE OF IppmMetricsEntry | |||
MAX-ACCESS not-accessible | MAX-ACCESS not-accessible | |||
STATUS current | STATUS current | |||
DESCRIPTION | DESCRIPTION | |||
"This table is mandatory. It describes the current | "This table is mandatory. It describes the current | |||
implementation. Each IPPM standardized metric must be described | implementation. Each IPPM standardized metric must be | |||
in the table. | described in the table. | |||
ippmMetricsTable content is read only." | ippmMetricsTable content is read only." | |||
::= { ippmSystem 9 } | ::= { ippmSystem 9 } | |||
ippmMetricsEntry OBJECT-TYPE | ippmMetricsEntry OBJECT-TYPE | |||
SYNTAX IppmMetricsEntry | SYNTAX IppmMetricsEntry | |||
MAX-ACCESS not-accessible | MAX-ACCESS not-accessible | |||
STATUS current | STATUS current | |||
DESCRIPTION | DESCRIPTION | |||
"An entry describes the static capabilities of a metric | "An entry describes the static capabilities of a metric | |||
implementation." | implementation." | |||
skipping to change at page 29, line 44 | skipping to change at page 33, line 41 | |||
DESCRIPTION | DESCRIPTION | |||
"ippmMetricsIndex defines an unambiguous index for each | "ippmMetricsIndex defines an unambiguous index for each | |||
standardized metric. It identifies a metric, and as such its | standardized metric. It identifies a metric, and as such its | |||
value is the value of the node of the metric in the IPPM | value is the value of the node of the metric in the IPPM | |||
registry. This value is the same in any implementation of the | registry. This value is the same in any implementation of the | |||
IPPM REPORTING MIB. | IPPM REPORTING MIB. | |||
Example: | Example: | |||
In the IPPM-METRICS-REGISTRY, onewayPacketLossAverage is | In the IPPM-METRICS-REGISTRY, onewayPacketLossAverage is | |||
registered as the node 14 of ippmMetricsRegistry.metrics.rfc. | registered as the node 14 of ippmMetricsRegistry.metrics.rfc. | |||
Consequently the index of the metric onewayPacketLossAverage in | Consequently the index of the metric onewayPacketLossAverage | |||
the IppmMetricsTable will always be '14'" | in the IppmMetricsTable will always be '14'" | |||
::= { ippmMetricsEntry 1 } | ::= { ippmMetricsEntry 1 } | |||
ippmMetricsType OBJECT-TYPE | ippmMetricsType OBJECT-TYPE | |||
SYNTAX INTEGER { | SYNTAX INTEGER { | |||
network(0), | network(0), | |||
aggregated(1) | aggregated(1) | |||
} | } | |||
MAX-ACCESS read-only | MAX-ACCESS read-only | |||
STATUS current | STATUS current | |||
DESCRIPTION | DESCRIPTION | |||
"Indicates the metric type, whether it is network or aggregated" | "Indicates the metric type, whether it is network or | |||
aggregated." | ||||
::= { ippmMetricsEntry 2 } | ::= { ippmMetricsEntry 2 } | |||
ippmMetricsUnit OBJECT-TYPE | ippmMetricsUnit OBJECT-TYPE | |||
SYNTAX INTEGER { | SYNTAX INTEGER { | |||
noUnit(0), | noUnit(0), | |||
second(1), | second(1), | |||
millisecond(2), | millisecond(2), | |||
microsecond(3), | microsecond(3), | |||
nanosecond(4), | nanosecond(4), | |||
percentage(5), | percentage(5), | |||
skipping to change at page 30, line 34 | skipping to change at page 34, line 35 | |||
DESCRIPTION | DESCRIPTION | |||
"The unit used in the current entity for the results of the | "The unit used in the current entity for the results of the | |||
measurement of this metric." | measurement of this metric." | |||
::= { ippmMetricsEntry 3 } | ::= { ippmMetricsEntry 3 } | |||
ippmMetricsDescription OBJECT-TYPE | ippmMetricsDescription OBJECT-TYPE | |||
SYNTAX SnmpAdminString | SYNTAX SnmpAdminString | |||
MAX-ACCESS read-only | MAX-ACCESS read-only | |||
STATUS current | STATUS current | |||
DESCRIPTION | DESCRIPTION | |||
"A textual description of the metric implementation following the | "A textual description of the metric implementation following | |||
exact name of this metric in the registry. For example: | the exact name of this metric in the registry. For example: | |||
oneWayDelay: OWD Metric ." | oneWayDelay: OWD Metric ." | |||
::= { ippmMetricsEntry 4 } | ::= { ippmMetricsEntry 4 } | |||
-- | -- | |||
-- 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 access or aggregate remote Ippm | "A management entity wishing to access or aggregate remote Ippm | |||
measurements in an agent must previously be registered in the | measurements in an agent must previously be registered in the | |||
ippmOwnersTable. This table is read-create and contains at least the | ippmOwnersTable. This table is read-create and contains at least the | |||
owner 'monitor'." | owner 'monitor'." | |||
::= { 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 | |||
in ippmOwnersTable would be named ippmOwnersEntryOwner.14. | created in ippmOwnersTable would be named | |||
ippmOwnersEntryOwner.14. | ||||
" | " | |||
INDEX { ippmOwnersOwner } | INDEX { ippmOwnersOwner } | |||
::= { ippmOwnersTable 1 } | ::= { ippmOwnersTable 1 } | |||
IppmOwnersEntry ::= SEQUENCE { | IppmOwnersEntry ::= SEQUENCE { | |||
ippmOwnersOwner IppmOwnerString, | ippmOwnersOwner IppmOwnerString, | |||
ippmOwnersGrantedMetrics IppmStandardMetrics, | ippmOwnersGrantedMetrics IppmStandardMetrics, | |||
ippmOwnersQuota Unsigned32, | ippmOwnersQuota Unsigned32, | |||
ippmOwnersIpAddressType InetAddressType, | ippmOwnersIpAddressType InetAddressType, | |||
ippmOwnersIpAddress InetAddress, | ippmOwnersIpAddress InetAddress, | |||
skipping to change at page 31, line 37 | skipping to change at page 36, line 4 | |||
ippmOwnersStatus RowStatus | ippmOwnersStatus RowStatus | |||
} | } | |||
ippmOwnersOwner OBJECT-TYPE | ippmOwnersOwner OBJECT-TYPE | |||
SYNTAX IppmOwnerString | SYNTAX IppmOwnerString | |||
MAX-ACCESS not-accessible | MAX-ACCESS not-accessible | |||
STATUS current | STATUS current | |||
DESCRIPTION | DESCRIPTION | |||
"The owner described by this entry." | "The owner described by this entry." | |||
::= { ippmOwnersEntry 1 } | ::= { ippmOwnersEntry 1 } | |||
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 for which measurements | " Defines the metrics granted to an owner for which | |||
can be performed." | measurements can be performed." | |||
::= { ippmOwnersEntry 2 } | ::= { ippmOwnersEntry 2 } | |||
ippmOwnersQuota OBJECT-TYPE | ippmOwnersQuota OBJECT-TYPE | |||
SYNTAX Unsigned32 | SYNTAX Unsigned32 | |||
MAX-ACCESS read-create | MAX-ACCESS read-create | |||
STATUS current | STATUS current | |||
DESCRIPTION | DESCRIPTION | |||
" The maximum number of records that this owner may have in the | " The maximum number of records that this owner may have in the | |||
history table and in the report table." | history table and in the report table." | |||
::= { ippmOwnersEntry 3 } | ::= { ippmOwnersEntry 3 } | |||
skipping to change at page 32, line 21 | skipping to change at page 36, line 38 | |||
this owner. | this owner. | |||
InetAddressType is restricted to ipv4(1),ipv6(2)and dns(16). " | InetAddressType is restricted to ipv4(1),ipv6(2)and dns(16). " | |||
::= { ippmOwnersEntry 4 } | ::= { ippmOwnersEntry 4 } | |||
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. For example, the IP address of the management console used | owner. For example, the IP address of the management console | |||
to send SNMP requests." | used to send SNMP requests." | |||
::= { ippmOwnersEntry 5 } | ::= { ippmOwnersEntry 5 } | |||
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 | |||
owner." | this owner." | |||
::= { ippmOwnersEntry 6 } | ::= { ippmOwnersEntry 6 } | |||
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. Once this status is set to | "The status of this table entry. Once this status is set to | |||
active, the corresponding entry in the table may not be | active, the corresponding entry in the table may not be | |||
modified." | modified." | |||
::= { ippmOwnersEntry 7 } | ::= { ippmOwnersEntry 7 } | |||
skipping to change at page 33, line 50 | skipping to change at page 38, line 28 | |||
ippmHistorySequence Unsigned32, | ippmHistorySequence Unsigned32, | |||
ippmHistoryTimestamp GMTTimeStamp, | ippmHistoryTimestamp GMTTimeStamp, | |||
ippmHistoryValue Integer32 | ippmHistoryValue Integer32 | |||
} | } | |||
ippmHistoryMeasureOwner OBJECT-TYPE | ippmHistoryMeasureOwner OBJECT-TYPE | |||
SYNTAX IppmOwnerString | SYNTAX IppmOwnerString | |||
MAX-ACCESS not-accessible | MAX-ACCESS not-accessible | |||
STATUS current | STATUS current | |||
DESCRIPTION | DESCRIPTION | |||
"The owner of the measure that produced this result. The measure | "The owner of the measure that produced this result. The | |||
is either an ippmNetMeasure or an ippmAggrMeasure." | measure is either an ippmNetMeasure or an ippmAggrMeasure." | |||
::= { ippmHistoryEntry 1 } | ::= { ippmHistoryEntry 1 } | |||
ippmHistoryMeasureIndex OBJECT-TYPE | ippmHistoryMeasureIndex OBJECT-TYPE | |||
SYNTAX IppmOwnerIndex | SYNTAX IppmOwnerIndex | |||
MAX-ACCESS not-accessible | MAX-ACCESS not-accessible | |||
STATUS current | STATUS current | |||
DESCRIPTION | DESCRIPTION | |||
"The owner index of the measure that produced this result. The | "The owner index of the measure that produced this result. The | |||
measure is either an entry of the ippmNetMeasureTable or of the | measure is either an entry of the ippmNetMeasureTable or of | |||
ippmAggrMeasureTable." | the ippmAggrMeasureTable." | |||
::= { ippmHistoryEntry 2 } | ::= { ippmHistoryEntry 2 } | |||
ippmHistoryMetricIndex OBJECT-TYPE | ippmHistoryMetricIndex OBJECT-TYPE | |||
SYNTAX IppmMetricsRegistryIndex | SYNTAX IppmMetricsRegistryIndex | |||
MAX-ACCESS not-accessible | MAX-ACCESS not-accessible | |||
STATUS current | STATUS current | |||
DESCRIPTION | DESCRIPTION | |||
" ippmHistoryMetricIndex identifies the metric measured by the | " ippmHistoryMetricIndex identifies the metric measured by the | |||
measure. The metric is described in the corresponding entry of | measure. The metric is described in the corresponding entry of | |||
the ippmMetricsTable." | the ippmMetricsTable." | |||
skipping to change at page 34, line 24 | skipping to change at page 39, line 4 | |||
ippmHistoryMetricIndex OBJECT-TYPE | ippmHistoryMetricIndex OBJECT-TYPE | |||
SYNTAX IppmMetricsRegistryIndex | SYNTAX IppmMetricsRegistryIndex | |||
MAX-ACCESS not-accessible | MAX-ACCESS not-accessible | |||
STATUS current | STATUS current | |||
DESCRIPTION | DESCRIPTION | |||
" ippmHistoryMetricIndex identifies the metric measured by the | " ippmHistoryMetricIndex identifies the metric measured by the | |||
measure. The metric is described in the corresponding entry of | measure. The metric is described in the corresponding entry of | |||
the ippmMetricsTable." | the ippmMetricsTable." | |||
::= { ippmHistoryEntry 3 } | ::= { ippmHistoryEntry 3 } | |||
ippmHistorySequence OBJECT-TYPE | ippmHistorySequence OBJECT-TYPE | |||
SYNTAX Unsigned32 (0..4294967295) | SYNTAX Unsigned32 (0..4294967295) | |||
MAX-ACCESS not-accessible | MAX-ACCESS not-accessible | |||
STATUS current | STATUS current | |||
DESCRIPTION | DESCRIPTION | |||
"ippmHistorySequence is the sequence number of the measurement | "ippmHistorySequence is the sequence number of the measurement | |||
results for a metric. | results for a metric. | |||
Network metrics: | Network metrics: | |||
It's the sequence number of a measurement packet. Typically, it | It's the sequence number of a measurement packet. Typically, | |||
identifies the order of the packet in the stream of packets sent | it identifies the order of the packet in the stream of packets | |||
by the source. | sent by the source. | |||
Aggregated metrics: | Aggregated metrics: | |||
It is the sequence order of the aggregation computed." | It is the sequence order of the aggregation computed." | |||
::= { ippmHistoryEntry 4 } | ::= { ippmHistoryEntry 4 } | |||
ippmHistoryTimestamp OBJECT-TYPE | ippmHistoryTimestamp OBJECT-TYPE | |||
SYNTAX GMTTimeStamp | SYNTAX GMTTimeStamp | |||
MAX-ACCESS read-only | MAX-ACCESS read-only | |||
STATUS current | STATUS current | |||
DESCRIPTION | DESCRIPTION | |||
skipping to change at page 35, line 15 | skipping to change at page 39, line 43 | |||
STATUS current | STATUS current | |||
DESCRIPTION | DESCRIPTION | |||
"The observed value of the measurement." | "The observed value of the measurement." | |||
::= { ippmHistoryEntry 6 } | ::= { ippmHistoryEntry 6 } | |||
ippmHistoryPathToResults OBJECT-TYPE | ippmHistoryPathToResults OBJECT-TYPE | |||
SYNTAX SnmpAdminString | SYNTAX SnmpAdminString | |||
MAX-ACCESS read-only | MAX-ACCESS read-only | |||
STATUS current | STATUS current | |||
DESCRIPTION | DESCRIPTION | |||
"It is typically an URL describing the file location where bulk | "It is typically an URL describing the file location where | |||
results are logged." | bulk results are logged." | |||
::= { ippmHistory 2 } | ::= { ippmHistory 2 } | |||
-- | -- | |||
-- ippmNetMeasure Group | -- ippmNetMeasure Group | |||
-- | -- | |||
-- | -- | |||
-- ippmNetMeasureTable | -- ippmNetMeasureTable | |||
-- | -- | |||
-- | -- | |||
ippmNetMeasureTable OBJECT-TYPE | ippmNetMeasureTable OBJECT-TYPE | |||
skipping to change at page 35, line 35 | skipping to change at page 40, line 20 | |||
-- | -- | |||
-- | -- | |||
ippmNetMeasureTable OBJECT-TYPE | ippmNetMeasureTable OBJECT-TYPE | |||
SYNTAX SEQUENCE OF IppmNetMeasureEntry | SYNTAX SEQUENCE OF IppmNetMeasureEntry | |||
MAX-ACCESS not-accessible | MAX-ACCESS not-accessible | |||
STATUS current | STATUS current | |||
DESCRIPTION | DESCRIPTION | |||
"An entry is a measurement that performs network measures and | "An entry is a measurement that performs network measures and | |||
provides results. | provides results. | |||
It performs several metric measurements per packet exchange. Each | It performs several metric measurements per packet exchange. | |||
step of a measure produces a singleton result per metric. The | Each step of a measure produces a singleton result per metric. | |||
time of the measurement and the value of the metric are saved in | The time of the measurement and the value of the metric are | |||
the ippmHistoryTable." | saved in the ippmHistoryTable." | |||
::= { ippmNetMeasure 1 } | ::= { ippmNetMeasure 1 } | |||
ippmNetMeasureEntry OBJECT-TYPE | ippmNetMeasureEntry OBJECT-TYPE | |||
SYNTAX IppmNetMeasureEntry | SYNTAX IppmNetMeasureEntry | |||
MAX-ACCESS not-accessible | MAX-ACCESS not-accessible | |||
STATUS current | STATUS current | |||
DESCRIPTION | DESCRIPTION | |||
" The IppmNetMeasureTable is mandatory, and its content is read | " The IppmNetMeasureTable is mandatory, and its content is read | |||
only. It means that the measurement software handles the table | only. It means that the measurement software handles the table | |||
internally. The setup of the network measure is not permitted | internally. The setup of the network measure is not permitted | |||
skipping to change at page 37, line 9 | skipping to change at page 42, line 4 | |||
"The owner of the network measure." | "The owner of the network measure." | |||
::= { ippmNetMeasureEntry 1 } | ::= { ippmNetMeasureEntry 1 } | |||
ippmNetMeasureIndex OBJECT-TYPE | ippmNetMeasureIndex OBJECT-TYPE | |||
SYNTAX IppmOwnerIndex | SYNTAX IppmOwnerIndex | |||
MAX-ACCESS not-accessible | MAX-ACCESS not-accessible | |||
STATUS current | STATUS current | |||
DESCRIPTION | DESCRIPTION | |||
"The owner index of the network measure." | "The owner index of the network measure." | |||
::= { ippmNetMeasureEntry 2 } | ::= { ippmNetMeasureEntry 2 } | |||
ippmNetMeasureName OBJECT-TYPE | ippmNetMeasureName OBJECT-TYPE | |||
SYNTAX SnmpAdminString | SYNTAX SnmpAdminString | |||
MAX-ACCESS read-only | MAX-ACCESS read-create | |||
STATUS current | STATUS current | |||
DESCRIPTION | DESCRIPTION | |||
"The name of the metric instance(s) as defined in | "The name of the metric instance(s) as defined in | |||
ippmNetMeasureMetrics. It illustrates the specificity of the | ippmNetMeasureMetrics. It illustrates the specificity of the | |||
metric(s) and includes the metric(s) and the PacketType. | metric(s) and includes the metric(s) and the PacketType. | |||
Example: | Example: | |||
IP-TCP-HTTP-One-way-Delay: free text " | IP-TCP-HTTP-One-way-Delay: free text " | |||
::= { ippmNetMeasureEntry 3 } | ::= { ippmNetMeasureEntry 3 } | |||
ippmNetMeasureMetrics OBJECT-TYPE | ippmNetMeasureMetrics OBJECT-TYPE | |||
SYNTAX IppmStandardMetrics | SYNTAX IppmStandardMetrics | |||
MAX-ACCESS read-only | MAX-ACCESS read-create | |||
STATUS current | STATUS current | |||
DESCRIPTION | DESCRIPTION | |||
"ippmNetMeasureMetrics defines the metrics to compute within this | "ippmNetMeasureMetrics defines the metrics to compute within | |||
measure. Only network metrics of the same type are allowed in | this measure. Only network metrics of the same type are | |||
this field (e.g. poisson-based metrics and periodic-based metrics | allowed in this field (e.g. poisson-based metrics and | |||
are incompatibles, while one-way delay and packet loss are | periodic-based metrics are incompatibles, while one-way delay | |||
generally processed simultaneously: a very bad delay is | and packet loss are generally processed simultaneously: a very | |||
potentially a very good packet loss). | bad delay is potentially a very good packet loss). | |||
Results are saved in the ippmHistoryTable. Results of a metric | Results are saved in the ippmHistoryTable. | |||
are identified using an index of type IppmMetricsRegistryIndex. | ||||
Results of a metric are identified using an index of type | ||||
IppmMetricsRegistryIndex. | ||||
Example: | Example: | |||
Given a multi-metrics measure of One-way-Delay(6) and One-way- | Given a multi-metrics measure of One-way-Delay(6) and One-way- | |||
Packet-Loss(12). The value of the field ippmNetMeasureMetrics is | Packet-Loss(12). The value of the field ippmNetMeasureMetrics | |||
'0001000001000000'b, '1040'B. Results are logged in the | is '0001000001000000'b, '1040'B. Results are logged in the | |||
ippmHistoryTable where One-way-Delay singletons have a value of | ippmHistoryTable where One-way-Delay singletons have a value | |||
ippmMetricsIndex of 6 while One-way-Packet-Loss singletons have a | of ippmMetricsIndex of 6 while One-way-Packet-Loss singletons | |||
value of ippmMetricsIndex of 12. | have a value of ippmMetricsIndex of 12. | |||
" | " | |||
::= { ippmNetMeasureEntry 4 } | ::= { ippmNetMeasureEntry 4 } | |||
ippmNetMeasureBeginTime OBJECT-TYPE | ippmNetMeasureBeginTime OBJECT-TYPE | |||
SYNTAX GMTTimeStamp | SYNTAX GMTTimeStamp | |||
MAX-ACCESS read-only | MAX-ACCESS read-create | |||
STATUS current | STATUS current | |||
DESCRIPTION | DESCRIPTION | |||
"Specifies the time at which the measurement begins." | "Specifies the time at which the measurement begins." | |||
::= { ippmNetMeasureEntry 5 } | ::= { ippmNetMeasureEntry 5 } | |||
ippmNetMeasureCollectionRateUnit OBJECT-TYPE | ippmNetMeasureCollectionRateUnit OBJECT-TYPE | |||
SYNTAX TimeUnit | SYNTAX TimeUnit | |||
MAX-ACCESS read-only | MAX-ACCESS read-create | |||
STATUS current | STATUS current | |||
DESCRIPTION | DESCRIPTION | |||
"Specifies the unit of the measurement period." | "Specifies the unit of the measurement period." | |||
::= { ippmNetMeasureEntry 6 } | ::= { ippmNetMeasureEntry 6 } | |||
ippmNetMeasureCollectionRate OBJECT-TYPE | ippmNetMeasureCollectionRate OBJECT-TYPE | |||
SYNTAX Unsigned32 | SYNTAX Unsigned32 | |||
MAX-ACCESS read-only | MAX-ACCESS read-create | |||
STATUS current | STATUS current | |||
DESCRIPTION | DESCRIPTION | |||
"Gives the period used to collect singletons from the point of | "Gives the period used to collect singletons from the point | |||
measures. This value is used as the cycle period in the report." | of measures. This value is used as the cycle period in the | |||
report." | ||||
::= { ippmNetMeasureEntry 7 } | ::= { ippmNetMeasureEntry 7 } | |||
ippmNetMeasureDurationUnit OBJECT-TYPE | ippmNetMeasureDurationUnit OBJECT-TYPE | |||
SYNTAX TimeUnit | SYNTAX TimeUnit | |||
MAX-ACCESS read-only | MAX-ACCESS read-create | |||
STATUS current | STATUS current | |||
DESCRIPTION | DESCRIPTION | |||
"Specifies the measurement duration unit." | "Specifies the measurement duration unit." | |||
::= { ippmNetMeasureEntry 8 } | ::= { ippmNetMeasureEntry 8 } | |||
ippmNetMeasureDuration OBJECT-TYPE | ippmNetMeasureDuration OBJECT-TYPE | |||
SYNTAX Unsigned32 | SYNTAX Unsigned32 | |||
MAX-ACCESS read-only | MAX-ACCESS read-create | |||
STATUS current | STATUS current | |||
DESCRIPTION | DESCRIPTION | |||
"Specifies the measurement duration." | "Specifies the measurement duration." | |||
::= { ippmNetMeasureEntry 9 } | ::= { ippmNetMeasureEntry 9 } | |||
ippmNetMeasureHistorySize OBJECT-TYPE | ippmNetMeasureHistorySize OBJECT-TYPE | |||
SYNTAX Unsigned32 | SYNTAX Unsigned32 | |||
MAX-ACCESS read-only | MAX-ACCESS read-create | |||
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 | |||
this measure. | of this measure. | |||
Overflow condition will be managed by the object | Overflow condition will be managed by the object | |||
ippmNetMeasureResultsMgmt. " | ippmNetMeasureResultsMgmt. " | |||
::= { ippmNetMeasureEntry 10 } | ::= { ippmNetMeasureEntry 10 } | |||
ippmNetMeasureFailureMgmtMode OBJECT-TYPE | ippmNetMeasureFailureMgmtMode OBJECT-TYPE | |||
SYNTAX INTEGER { | SYNTAX INTEGER { | |||
auto(1), | auto(1), | |||
manual(2), | manual(2), | |||
discarded(3) | discarded(3) | |||
} | } | |||
MAX-ACCESS read-only | MAX-ACCESS read-create | |||
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 | |||
by this row) is restarted automatically, manually, or discarded | controlled by this row) is restarted automatically, manually, | |||
upon failure, or reboot of the measurement system. | or discarded upon failure, or reboot of the measurement | |||
system: | ||||
'auto' | 'auto' | |||
The measure is restarted automatically. | The measure is restarted automatically. | |||
'manual' | 'manual' | |||
The measure has to be restarted manually. | The measure has to be restarted manually. | |||
'discarded' | 'discarded' | |||
The measure and it results are discarded. | The measure and it results are discarded. | |||
" | " | |||
::= { ippmNetMeasureEntry 11 } | ::= { ippmNetMeasureEntry 11 } | |||
ippmNetMeasureResultsMgmt OBJECT-TYPE | ippmNetMeasureResultsMgmt OBJECT-TYPE | |||
SYNTAX INTEGER { | SYNTAX INTEGER { | |||
wrap(1), | wrap(1), | |||
suspend(2) | suspend(2) | |||
} | } | |||
MAX-ACCESS read-only | MAX-ACCESS read-create | |||
STATUS current | STATUS current | |||
DESCRIPTION | DESCRIPTION | |||
" | " | |||
Action to take when the log is full. The measurement system owner | Action to take when the log is full. The measurement system | |||
may choose to either wrap, in which case the agent writes over | owner may choose to either wrap, in which case the agent | |||
existing records. The user may choose to suspend writing to the | writes over existing records. The user may choose to suspend | |||
log in the event that he wishes to archive the data. The resume | writing to the log in the event that he wishes to archive the | |||
action causes the agent to begin to write in the log, and assumes | data. The resume action causes the agent to begin to write in | |||
the data has been cleared. | the log, and assumes the data has been cleared. | |||
This object indicates the way the measurement results are managed | This object indicates the way the measurement results are | |||
when the owner quota has been exceeded: | managed when the owner quota has been exceeded: | |||
'wrap' | 'wrap' | |||
continue the measurement and erase the older entries in the | continue the measurement and erase the older entries in | |||
history. | the history. | |||
'suspend' | 'suspend' | |||
stop the measure and keep the results in the history. | stop the measure and keep the results in the history. | |||
" | " | |||
::= { ippmNetMeasureEntry 12 } | ::= { ippmNetMeasureEntry 12 } | |||
ippmNetMeasureSrcPacketType OBJECT-TYPE | ippmNetMeasureSrcPacketType OBJECT-TYPE | |||
SYNTAX PacketType | SYNTAX PacketType | |||
MAX-ACCESS read-only | MAX-ACCESS read-create | |||
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 | |||
the measure." | by the measure." | |||
::= { ippmNetMeasureEntry 13 } | ::= { ippmNetMeasureEntry 13 } | |||
ippmNetMeasureSrc OBJECT-TYPE | ippmNetMeasureSrc OBJECT-TYPE | |||
SYNTAX PacketTypeAddress | SYNTAX PacketTypeAddress | |||
MAX-ACCESS read-only | MAX-ACCESS read-create | |||
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 | |||
of the PROTOCOL IDENTIFIER set in ippmNetMeasureSrcPacketType." | those of the PROTOCOL IDENTIFIER set in | |||
ippmNetMeasureSrcPacketType." | ||||
::= { ippmNetMeasureEntry 14} | ::= { ippmNetMeasureEntry 14} | |||
ippmNetMeasureDstPacketType OBJECT-TYPE | ippmNetMeasureDstPacketType OBJECT-TYPE | |||
SYNTAX PacketType | SYNTAX PacketType | |||
MAX-ACCESS read-only | MAX-ACCESS read-create | |||
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." | |||
::= { ippmNetMeasureEntry 15 } | ::= { ippmNetMeasureEntry 15 } | |||
ippmNetMeasureDst OBJECT-TYPE | ippmNetMeasureDst OBJECT-TYPE | |||
SYNTAX PacketTypeAddress | SYNTAX PacketTypeAddress | |||
MAX-ACCESS read-only | MAX-ACCESS read-create | |||
STATUS current | STATUS current | |||
DESCRIPTION | DESCRIPTION | |||
"Specifies the address of the destination 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 | |||
of the PROTOCOL IDENTIFIER set in ippmNetMeasureDstPacketType." | those of the PROTOCOL IDENTIFIER set in | |||
ippmNetMeasureDstPacketType." | ||||
::= { ippmNetMeasureEntry 16 } | ::= { ippmNetMeasureEntry 16 } | |||
ippmNetMeasureTxMode OBJECT-TYPE | ippmNetMeasureTxMode OBJECT-TYPE | |||
SYNTAX INTEGER { | SYNTAX INTEGER { | |||
other(0), | other(0), | |||
periodic(1), | periodic(1), | |||
poisson(2), | poisson(2), | |||
multiburst(3) | multiburst(3) | |||
} | } | |||
MAX-ACCESS read-only | MAX-ACCESS read-create | |||
STATUS current | STATUS current | |||
DESCRIPTION | DESCRIPTION | |||
"The transmit mode used to send the packets: | "The transmit mode used to send the packets: | |||
'other' | 'other' | |||
The rule used to send the packets is unknown. | The rule used to send the packets is unknown. | |||
'periodic' | 'periodic' | |||
Packets are sent periodically at ippmNetMeasureTxPacketRate | Packets are sent periodically at ippmNetMeasureTxPacketRate | |||
rate. | rate. | |||
'poisson' | 'poisson' | |||
Packets are sent using a Poisson law, the median is the value | Packets are sent using a Poisson law, the median is the | |||
of ippmNetMeasureDevOrIntBurstSize, the deviation is | value of ippmNetMeasureDevOrIntBurstSize, the deviation is | |||
ippmNetMeasureMedOrBurstSize. | ippmNetMeasureMedOrBurstSize. | |||
'multiburst' | 'multiburst' | |||
Packets are sent bursty at ippmNetMeasureTxPacketRate. The | Packets are sent bursty at ippmNetMeasureTxPacketRate. The | |||
size of the burst is made of ippmNetMeasureMedOrBurstSize | size of the burst is made of ippmNetMeasureMedOrBurstSize | |||
packets. | packets. | |||
Between 2 consecutive bursts, transmission stops during the time | Between 2 consecutive bursts, transmission stops during the | |||
needed to send ippmNetMeasureDevOrIntBurstSize. | time needed to send ippmNetMeasureDevOrIntBurstSize. | |||
" | " | |||
::= { ippmNetMeasureEntry 17 } | ::= { ippmNetMeasureEntry 17 } | |||
ippmNetMeasureTxPacketRateUnit OBJECT-TYPE | ippmNetMeasureTxPacketRateUnit OBJECT-TYPE | |||
SYNTAX TimeUnit | SYNTAX TimeUnit | |||
MAX-ACCESS read-only | MAX-ACCESS read-create | |||
STATUS current | STATUS current | |||
DESCRIPTION | DESCRIPTION | |||
"The packet rate unit used to send the packets." | "The packet rate unit used to send the packets." | |||
::= { ippmNetMeasureEntry 18 } | ::= { ippmNetMeasureEntry 18 } | |||
ippmNetMeasureTxPacketRate OBJECT-TYPE | ippmNetMeasureTxPacketRate OBJECT-TYPE | |||
SYNTAX Unsigned32 | SYNTAX Unsigned32 | |||
UNITS "Packets" | UNITS "Packets" | |||
MAX-ACCESS read-only | MAX-ACCESS read-create | |||
STATUS current | STATUS current | |||
DESCRIPTION | DESCRIPTION | |||
"The rate the packets are sent." | "The rate the packets are sent." | |||
::= { ippmNetMeasureEntry 19 } | ::= { ippmNetMeasureEntry 19 } | |||
ippmNetMeasureMedOrBurstSize OBJECT-TYPE | ippmNetMeasureMedOrBurstSize OBJECT-TYPE | |||
SYNTAX Unsigned32 | SYNTAX Unsigned32 | |||
UNITS "Packets" | UNITS "Packets" | |||
MAX-ACCESS read-only | MAX-ACCESS read-create | |||
STATUS current | STATUS current | |||
DESCRIPTION | DESCRIPTION | |||
" | " | |||
Multi-burst mode: This field represents the burst size in number | Multi-burst mode: This field represents the burst size in | |||
of packets. | number of packets. | |||
Poisson mode: This field indicates the number of packets sent, on | Poisson mode: This field indicates the number of packets sent, | |||
average, during each period corresponding to the median. | on average, during each period corresponding to the median. | |||
The median is therefore | The median is therefore | |||
MedOrBurstSize*TxPacketRateUnit/TxPacketRate. | MedOrBurstSize*TxPacketRateUnit/TxPacketRate. | |||
Example: | Example: | |||
If TxPacketRateUnit/TxPacketRate is 100 packets/second, and if | If TxPacketRateUnit/TxPacketRate is 100 packets/second, and | |||
MedOrBurstSize, the number of packets sent during the period | if MedOrBurstSize, the number of packets sent during the | |||
corresponding to the median is 50 packets, then the median equals | period corresponding to the median is 50 packets, then the | |||
50*1/100 = 1/2 seconds. | median equals 50*1/100 = 1/2 seconds. | |||
" | " | |||
::= { ippmNetMeasureEntry 20 } | ::= { ippmNetMeasureEntry 20 } | |||
ippmNetMeasureDevOrIntBurstSize OBJECT-TYPE | ippmNetMeasureDevOrIntBurstSize OBJECT-TYPE | |||
SYNTAX Unsigned32 | SYNTAX Unsigned32 | |||
UNITS "Packets" | UNITS "Packets" | |||
MAX-ACCESS read-only | MAX-ACCESS read-create | |||
STATUS current | STATUS current | |||
DESCRIPTION | DESCRIPTION | |||
" | " | |||
Multi-burst mode: This field indicates the gap between 2 bursts, | Multi-burst mode: This field indicates the gap between 2 | |||
in number of packets. | bursts, in number of packets. | |||
Example: | Example: | |||
If TxPacketRateUnit/TxPacketRate is 100 packets/second, | If TxPacketRateUnit/TxPacketRate is 100 packets/second, | |||
and DevOrIntBurstSize equals 50 packets, then the gap between 2 | and DevOrIntBurstSize equals 50 packets, then the gap between | |||
bursts is | 2 bursts is equal to 50*1/100, or 1/2 second. | |||
equal to 50*1/100, or 1/2 second. | ||||
Poisson mode: | Poisson mode: | |||
This field indicates the typical difference between the packets | This field indicates the typical difference between the | |||
of the period corresponding to the median. | packets of the period corresponding to the median. | |||
" | " | |||
::= { ippmNetMeasureEntry 21 } | ::= { ippmNetMeasureEntry 21 } | |||
ippmNetMeasureLossTimeout OBJECT-TYPE | ippmNetMeasureLossTimeout OBJECT-TYPE | |||
SYNTAX Unsigned32 | SYNTAX Unsigned32 | |||
UNITS "Milliseconds" | UNITS "Milliseconds" | |||
MAX-ACCESS read-only | MAX-ACCESS read-create | |||
STATUS current | STATUS current | |||
DESCRIPTION | DESCRIPTION | |||
"Specifies the delay after which the packet is considered lost | "Specifies the delay after which the packet is considered | |||
by the sink." | lost by the sink." | |||
::= { ippmNetMeasureEntry 22 } | ::= { ippmNetMeasureEntry 22 } | |||
ippmNetMeasureL3PacketSize OBJECT-TYPE | ippmNetMeasureL3PacketSize OBJECT-TYPE | |||
SYNTAX Unsigned32 | SYNTAX Unsigned32 | |||
UNITS "Bytes" | UNITS "Bytes" | |||
MAX-ACCESS read-only | MAX-ACCESS read-create | |||
STATUS current | STATUS current | |||
DESCRIPTION | DESCRIPTION | |||
"Specifies the size of the packets counted at the IP network | "Specifies the size of the packets counted at the IP network | |||
layer in regards to the PacketType definition. | layer in regards to the PacketType definition. | |||
Example: For a PacketType 'ip ipip4' the L3 size will be the size | Example: For a PacketType 'ip ipip4' the L3 size will be the | |||
of the packet at ipip4 level. | size of the packet at ipip4 level. | |||
" | " | |||
::= { ippmNetMeasureEntry 23 } | ::= { ippmNetMeasureEntry 23 } | |||
ippmNetMeasureDataPattern OBJECT-TYPE | ippmNetMeasureDataPattern OBJECT-TYPE | |||
SYNTAX OCTET STRING | SYNTAX OCTET STRING | |||
MAX-ACCESS read-only | MAX-ACCESS read-create | |||
STATUS current | STATUS current | |||
DESCRIPTION | DESCRIPTION | |||
"The pattern used to fill the payload of the packet." | "The pattern used to fill the payload of the packet." | |||
::= { ippmNetMeasureEntry 24 } | ::= { ippmNetMeasureEntry 24 } | |||
ippmNetMeasureTotalPktsRecv OBJECT-TYPE | ippmNetMeasureTotalPktsRecv OBJECT-TYPE | |||
SYNTAX Counter64 | SYNTAX Counter64 | |||
UNITS "Packets" | UNITS "Packets" | |||
MAX-ACCESS read-only | MAX-ACCESS read-only | |||
STATUS current | STATUS current | |||
DESCRIPTION | DESCRIPTION | |||
"Reports the current number of packets received since the | "Reports the current number of packets received since the | |||
beginning of the measure. | beginning of the measure. | |||
This parameters is useful to monitor the measure and it is needed | This parameters is useful to monitor the measure and it is | |||
to compute statistics." | needed to compute statistics." | |||
::= { ippmNetMeasureEntry 25 } | ::= { ippmNetMeasureEntry 25 } | |||
ippmNetMeasureLastUpdate OBJECT-TYPE | ippmNetMeasureLastUpdate OBJECT-TYPE | |||
SYNTAX GMTTimeStamp | SYNTAX GMTTimeStamp | |||
MAX-ACCESS read-only | MAX-ACCESS read-only | |||
STATUS current | STATUS current | |||
DESCRIPTION | DESCRIPTION | |||
"The time when the last aggregation was computed." | "The time when the last aggregation was computed." | |||
::= { ippmNetMeasureEntry 26 } | ::= { ippmNetMeasureEntry 26 } | |||
skipping to change at page 44, line 15 | skipping to change at page 49, line 36 | |||
-- | -- | |||
-- 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 | |||
"An aggregated measure summarizes the results of previous network | "An aggregated measure summarizes the results of previous | |||
or aggregated measures. The results are saved in the | network or aggregated measures. The results are 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 | |||
result per metric." | singleton result per metric." | |||
::= { ippmAggrMeasure 1 } | ::= { ippmAggrMeasure 1 } | |||
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 creates and sets the | "Typically, the configuration operation creates and sets the | |||
value of the fields of a new ippmAggrMeasureEntry. | value of the fields of a new ippmAggrMeasureEntry. | |||
ippmAggrMeasureOwner and ippmAggrMeasureIndex identify the | ippmAggrMeasureOwner and ippmAggrMeasureIndex identify the | |||
instance created. | instance created. | |||
The field ippmAggrMeasureMetrics identifies the metric to | The field ippmAggrMeasureMetrics identifies the metric to | |||
compute. As such its ippmMetricsType should be 'aggregated'. | compute. As such its ippmMetricsType should be 'aggregated'. | |||
The measure aggregates the results of a measure identified by | The measure aggregates the results of a measure identified by | |||
ippmAggrMeasureHistoryOwner, ippmAggrMeasureHistoryIndex and | ippmAggrMeasureHistoryOwner, ippmAggrMeasureHistoryIndex and | |||
ippmAggrMeasureHistoryMetric. The measure to aggregate belongs to | ippmAggrMeasureHistoryMetric. The measure to aggregate belongs | |||
ippmNetMeasureTable or ippmAggrMeasureTable. | to ippmNetMeasureTable or ippmAggrMeasureTable. | |||
The aggregation starts at ippmAggrMeasureBeginTime and ends after | The aggregation starts at ippmAggrMeasureBeginTime and ends | |||
ippmAggrMeasureDuration. | after ippmAggrMeasureDuration. | |||
An aggregated result is computed for each | An aggregated result is computed for each | |||
ippmMeasureCollectionRate tick and saved in the | ippmMeasureCollectionRate tick and saved in the | |||
ippmHistoryTable." | ippmHistoryTable." | |||
INDEX { ippmAggrMeasureOwner, ippmAggrMeasureIndex } | INDEX { ippmAggrMeasureOwner, ippmAggrMeasureIndex } | |||
::= { ippmAggrMeasureTable 1 } | ::= { ippmAggrMeasureTable 1 } | |||
IppmAggrMeasureEntry ::= SEQUENCE { | IppmAggrMeasureEntry ::= SEQUENCE { | |||
ippmAggrMeasureOwner IppmOwnerString, | ippmAggrMeasureOwner IppmOwnerString, | |||
ippmAggrMeasureIndex IppmOwnerIndex, | ippmAggrMeasureIndex IppmOwnerIndex, | |||
skipping to change at page 45, line 37 | skipping to change at page 51, line 22 | |||
STATUS current | STATUS current | |||
DESCRIPTION | DESCRIPTION | |||
"The owner who has configured this entry." | "The owner who has configured this entry." | |||
::= { ippmAggrMeasureEntry 1 } | ::= { ippmAggrMeasureEntry 1 } | |||
ippmAggrMeasureIndex OBJECT-TYPE | ippmAggrMeasureIndex OBJECT-TYPE | |||
SYNTAX IppmOwnerIndex | SYNTAX IppmOwnerIndex | |||
MAX-ACCESS not-accessible | MAX-ACCESS not-accessible | |||
STATUS current | STATUS current | |||
DESCRIPTION | DESCRIPTION | |||
"The index of the aggregated measure. The value is managed by the | "The index of the aggregated measure. The value is managed by | |||
owner." | the owner." | |||
::= { ippmAggrMeasureEntry 2 } | ::= { ippmAggrMeasureEntry 2 } | |||
ippmAggrMeasureName OBJECT-TYPE | ippmAggrMeasureName OBJECT-TYPE | |||
SYNTAX SnmpAdminString | SYNTAX SnmpAdminString | |||
MAX-ACCESS read-create | MAX-ACCESS read-create | |||
STATUS current | STATUS current | |||
DESCRIPTION | DESCRIPTION | |||
"The name of the instance of the metric. It illustrates the | "The name of the instance of the metric. It illustrates the | |||
specificity of the metric and includes the metric and the typeP. | specificity of the metric and includes the metric and the | |||
typeP. | ||||
example: IP-port-HTTP-connectivity: free text." | example: IP-port-HTTP-connectivity: free text." | |||
::= { ippmAggrMeasureEntry 3 } | ::= { ippmAggrMeasureEntry 3 } | |||
ippmAggrMeasureMetrics OBJECT-TYPE | ippmAggrMeasureMetrics OBJECT-TYPE | |||
SYNTAX IppmStandardMetrics | SYNTAX IppmStandardMetrics | |||
MAX-ACCESS read-create | MAX-ACCESS read-create | |||
STATUS current | STATUS current | |||
DESCRIPTION | DESCRIPTION | |||
"ippmAggrMeasureMetrics defines the metrics to compute within | "ippmAggrMeasureMetrics defines the metrics to compute within | |||
this aggregated measure. | this aggregated measure. | |||
Only aggregated metrics of the same type are allowed in this | Only aggregated metrics of the same type are allowed in this | |||
field (e.g. Measurement of minimum, average and maximum metrics | field (e.g. Measurement of minimum, average and maximum | |||
are generally processed simultaneously on the same network | metrics are generally processed simultaneously on the same | |||
measure). | network measure). | |||
Results are saved in the ippmHistoryTable. Results of a metric | Results are saved in the ippmHistoryTable. | |||
are identified using an index of type IppmMetricsRegistryIndex. | ||||
Results of a metric are identified using an index of type | ||||
IppmMetricsRegistryIndex. | ||||
Example: | Example: | |||
Given a multi-aggregation of One-way-Delay-Median(9) and One-way- | Given a multi-aggregation of One-way-Delay-Median(9) and | |||
Delay-Minimum(10). The value of the field ippmAggrMeasureMetrics | One-way-Delay-Minimum(10). The value of the field | |||
is '0000011000000000'b, '0600'B. Results are logged in the | ippmAggrMeasureMetrics is '0000011000000000'b, '0600'B. | |||
ippmHistoryTable where One-way-Delay-Median singletons have a | ||||
value of ippmMetricsIndex of 9 while One-way-Delay-Minimum | Results are logged in the ippmHistoryTable where | |||
singletons have a value of ippmMetricsIndex of 10. | One-way-Delay-Median singletons have a value of | |||
ippmMetricsIndex of 9 while One-way-Delay-Minimum singletons | ||||
have a value of ippmMetricsIndex of 10. | ||||
NOTE WELL: It is not recommended to use the multi aggregation | NOTE WELL: It is not recommended to use the multi aggregation | |||
capability in conjunction with the filter feature. | capability in conjunction with the filter feature. | |||
" | " | |||
::= { ippmAggrMeasureEntry 4 } | ::= { ippmAggrMeasureEntry 4 } | |||
ippmAggrMeasureHistoryOwner OBJECT-TYPE | ippmAggrMeasureHistoryOwner OBJECT-TYPE | |||
SYNTAX IppmOwnerString | SYNTAX IppmOwnerString | |||
MAX-ACCESS read-create | MAX-ACCESS read-create | |||
STATUS current | STATUS current | |||
skipping to change at page 47, line 18 | skipping to change at page 53, line 16 | |||
STATUS current | STATUS current | |||
DESCRIPTION | DESCRIPTION | |||
" | " | |||
ippmAggrMeasureFilter defines the kind of filter to apply on a | ippmAggrMeasureFilter defines the kind of filter to apply on a | |||
result to determine if the result is stored or not. The | result to determine if the result is stored or not. The | |||
parameters of the filter are ippmAggrMeasureLowThreshold and | parameters of the filter are ippmAggrMeasureLowThreshold and | |||
ippmAggrMeasureHighThreshold. | ippmAggrMeasureHighThreshold. | |||
Thresholds have the same unit as the metric value. | Thresholds have the same unit as the metric value. | |||
In the following examples we consider an aggregated measure. Its | In the following examples we consider an aggregated measure. | |||
low threshold is set to 80.its high threshold is set to 100. The | Its low threshold is set to 80.its high threshold is set to | |||
aggregation produced a flow of 12 aggregated results {40 30 60 85 | 100. The aggregation produced a flow of 12 aggregated results | |||
140 130 190 95 50 90 30 20}. | {40 30 60 85 140 130 190 95 50 90 30 20}. | |||
If the filter is set to 'logInBandValue' then the results 85, 95, | If the filter is set to 'logInBandValue' then the results 85, | |||
90 will be stored. | 95, 90 will be stored. | |||
If the filter is set to 'logOutBandValue' then the results 40 30 | If the filter is set to 'logOutBandValue' then the results 40 | |||
60 140 130 190 50 30 20 will be stored. | 30 60 140 130 190 50 30 20 will be stored. | |||
If the filter is set to 'logAboveValue' then the results 140 130 | If the filter is set to 'logAboveValue' then the results 140 | |||
190 will be stored. | 130 190 will be stored. | |||
If the filter is set to 'logBelowValue' then the results 40 30 60 | If the filter is set to 'logBelowValue' then the results 40 30 | |||
50 30 20 will be stored. | 60 50 30 20 will be stored. | |||
If the filter is set to 'logUpAndDownValue' then the results 40, | If the filter is set to 'logUpAndDownValue' then the results | |||
140, 50 will be stored." | 40, 140, 50 will be stored." | |||
::= { ippmAggrMeasureEntry 8 } | ::= { ippmAggrMeasureEntry 8 } | |||
ippmAggrMeasureLowThreshold OBJECT-TYPE | ippmAggrMeasureLowThreshold OBJECT-TYPE | |||
SYNTAX Unsigned32 | SYNTAX Unsigned32 | |||
MAX-ACCESS read-create | MAX-ACCESS read-create | |||
STATUS current | STATUS current | |||
DESCRIPTION | DESCRIPTION | |||
"An event is generated when the result of the measure of the | "An event is generated when the result of the measure of the | |||
metric is lower that the value of ippmAggrMeasureLowThreshold. | metric is lower that the value of ippmAggrMeasureLowThreshold. | |||
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 | |||
recorded in the object ippmMetricsUnit of this metric entry in | is recorded in the object ippmMetricsUnit of this metric entry | |||
the ippmMetricsTable. | in the ippmMetricsTable. | |||
" | " | |||
::= { ippmAggrMeasureEntry 9 } | ::= { ippmAggrMeasureEntry 9 } | |||
ippmAggrMeasureHighThreshold OBJECT-TYPE | ippmAggrMeasureHighThreshold OBJECT-TYPE | |||
SYNTAX Unsigned32 | SYNTAX Unsigned32 | |||
MAX-ACCESS read-create | MAX-ACCESS read-create | |||
STATUS current | STATUS current | |||
DESCRIPTION | DESCRIPTION | |||
"An event is generated when the result of the measure of the | "An event is generated when the result of the measure of the | |||
metric exceeds the value of ippmAggrMeasureHighThreshold. | metric exceeds the value of ippmAggrMeasureHighThreshold. | |||
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 | |||
recorded in the object ippmMetricsUnit of this metric entry in | is recorded in the object ippmMetricsUnit of this metric entry | |||
the ippmMetricsTable. | in the ippmMetricsTable. | |||
" | " | |||
::= { ippmAggrMeasureEntry 10 } | ::= { ippmAggrMeasureEntry 10 } | |||
ippmAggrMeasureBeginTime OBJECT-TYPE | ippmAggrMeasureBeginTime OBJECT-TYPE | |||
SYNTAX GMTTimeStamp | SYNTAX GMTTimeStamp | |||
MAX-ACCESS read-create | MAX-ACCESS read-create | |||
STATUS current | STATUS current | |||
DESCRIPTION | DESCRIPTION | |||
"Specifies the time at which the aggregated measure starts." | "Specifies the time at which the aggregated measure starts." | |||
::= { ippmAggrMeasureEntry 11 } | ::= { ippmAggrMeasureEntry 11 } | |||
skipping to change at page 48, line 39 | skipping to change at page 54, line 39 | |||
"Specifies the unit of the aggregated measure period." | "Specifies the unit of the aggregated measure period." | |||
DEFVAL { second } | DEFVAL { second } | |||
::= { ippmAggrMeasureEntry 12 } | ::= { ippmAggrMeasureEntry 12 } | |||
ippmAggrMeasureAggrPeriod OBJECT-TYPE | ippmAggrMeasureAggrPeriod OBJECT-TYPE | |||
SYNTAX Unsigned32 | SYNTAX Unsigned32 | |||
MAX-ACCESS read-create | MAX-ACCESS read-create | |||
STATUS current | STATUS current | |||
DESCRIPTION | DESCRIPTION | |||
"Specifies the amount of time between 2 measurement action | "Specifies the amount of time between 2 measurement action | |||
intervals. The action is specific to the semantic of the measure. | intervals. The action is specific to the semantic of the | |||
measure. | ||||
Network metrics: | Network metrics: | |||
The ippmNetMeasureClockPattern transforms the flow of periodical | The ippmNetMeasureClockPattern transforms the flow of | |||
instants as a flow of unpredictable instants of measurement | periodical instants as a flow of unpredictable instants of | |||
packet emission. | measurement packet emission. | |||
As the source and the sink share the definition of the clock of | As the source and the sink share the definition of the clock | |||
the measure, and as the sending timestamp is part of the | of the measure, and as the sending timestamp is part of the | |||
measurement packet, the sink has the information to verify that | measurement packet, the sink has the information to verify | |||
the stream of packets generated by the source respects the clock | that the stream of packets generated by the source respects | |||
law. | the clock law. | |||
Aggregated metrics: | Aggregated metrics: | |||
They are performed periodically on a sequence of results of other | They are performed periodically on a sequence of results of | |||
measures. The period corresponds to the interval between two | other measures. The period corresponds to the interval between | |||
successive computations of the metric. The value of | two successive computations of the metric. The value of | |||
ippmHistoryTimestamp result of a aggregated metric computed | ippmHistoryTimestamp result of a aggregated metric computed | |||
corresponds to the value of the ippmHistoryTimestamp of the last | corresponds to the value of the ippmHistoryTimestamp of the | |||
metric result of the sequence used to compute the aggregated | last metric result of the sequence used to compute the | |||
metric." | aggregated metric." | |||
DEFVAL { 60 } | DEFVAL { 60 } | |||
::= { ippmAggrMeasureEntry 13 } | ::= { ippmAggrMeasureEntry 13 } | |||
ippmAggrMeasureDurationUnit OBJECT-TYPE | ippmAggrMeasureDurationUnit OBJECT-TYPE | |||
SYNTAX TimeUnit | SYNTAX TimeUnit | |||
MAX-ACCESS read-create | MAX-ACCESS read-create | |||
STATUS current | STATUS current | |||
DESCRIPTION | DESCRIPTION | |||
"Specifies the unit of the measure duration." | "Specifies the unit of the measure duration." | |||
skipping to change at page 49, line 39 | skipping to change at page 55, line 43 | |||
DESCRIPTION | DESCRIPTION | |||
"Specifies the duration of the measure." | "Specifies the duration of the measure." | |||
DEFVAL { 120 } | DEFVAL { 120 } | |||
::= { ippmAggrMeasureEntry 15 } | ::= { ippmAggrMeasureEntry 15 } | |||
ippmAggrMeasureHistorySize OBJECT-TYPE | ippmAggrMeasureHistorySize OBJECT-TYPE | |||
SYNTAX Unsigned32 | SYNTAX Unsigned32 | |||
MAX-ACCESS read-create | MAX-ACCESS read-create | |||
STATUS current | STATUS current | |||
DESCRIPTION | DESCRIPTION | |||
"Specifies the maximum number of results saved for each metric of | "Specifies the maximum number of results saved for each metric | |||
this measure. Overflow condition will be managed by the object | of this measure. Overflow condition will be managed by the | |||
ippmAggrMeasureResultsMgmt. " | object ippmAggrMeasureResultsMgmt. " | |||
DEFVAL { 2 } | DEFVAL { 2 } | |||
::= { ippmAggrMeasureEntry 16 } | ::= { ippmAggrMeasureEntry 16 } | |||
ippmAggrMeasureStorageType OBJECT-TYPE | ippmAggrMeasureStorageType OBJECT-TYPE | |||
SYNTAX StorageType | SYNTAX StorageType | |||
MAX-ACCESS read-create | MAX-ACCESS read-create | |||
STATUS current | STATUS current | |||
DESCRIPTION | DESCRIPTION | |||
"This object defines whether this row and the measure controlled | "This object defines whether this row and the measure | |||
by this row are kept in volatile storage and lost upon reboot or | controlled by this row are kept in volatile storage and lost | |||
if this row is backed up | upon reboot or 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), | Possible values are: other(1), volatile(2), nonVolatile(3), | |||
permanent(4), readOnly(5)." | permanent(4), readOnly(5)." | |||
DEFVAL { nonVolatile } | DEFVAL { nonVolatile } | |||
::= { ippmAggrMeasureEntry 17 } | ::= { ippmAggrMeasureEntry 17 } | |||
ippmAggrMeasureResultsMgmt OBJECT-TYPE | ippmAggrMeasureResultsMgmt OBJECT-TYPE | |||
SYNTAX INTEGER { | SYNTAX INTEGER { | |||
wrap(1), | wrap(1), | |||
skipping to change at page 50, line 43 | skipping to change at page 57, line 4 | |||
} | } | |||
MAX-ACCESS read-create | MAX-ACCESS read-create | |||
STATUS current | STATUS current | |||
DESCRIPTION | DESCRIPTION | |||
"This object controls the activity of the aggregated measure. | "This object controls the activity of the aggregated measure. | |||
'start' | 'start' | |||
The aggregated measure is started. | The aggregated measure is started. | |||
'stop' | 'stop' | |||
The aggregated measure is stopped." | The aggregated measure is stopped." | |||
DEFVAL { start } | DEFVAL { start } | |||
::= { ippmAggrMeasureEntry 19 } | ::= { ippmAggrMeasureEntry 19 } | |||
ippmAggrMeasureFastReport OBJECT-TYPE | ippmAggrMeasureFastReport OBJECT-TYPE | |||
SYNTAX OBJECT IDENTIFIER | SYNTAX OBJECT IDENTIFIER | |||
MAX-ACCESS read-create | MAX-ACCESS read-create | |||
STATUS current | STATUS current | |||
DESCRIPTION | DESCRIPTION | |||
"A fast report is required in order to verify quickly that a | "A fast report is required in order to verify quickly that a | |||
measure is running well. | measure is running well. | |||
'fast report' feature is active if ippmAggrMeasureFastReport | ||||
The feature 'fast report' is active if ippmAggrMeasureFastReport | ||||
is not null and points to a notification. | is not null and points to a notification. | |||
A fast report consists of sending by email to the owner of the | 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 | measure, a table of the results of all the metrics computed by | |||
this aggregated measure. The owner email address is read from the | this aggregated measure. The owner email address is read from | |||
ippmOwnersTable. | the ippmOwnersTable. | |||
ippmAggrMeasureFastReport identifies the notification which | ippmAggrMeasureFastReport identifies the notification which | |||
defines the header of the report. | defines the header of the report. | |||
The results part of the report is made of a column of results per | The results part of the report is made of a column of results | |||
metrics. Results are separated using commas. | per metrics. Results are separated using commas. | |||
To avoid disaster, an aggregated measure using a fast report must | To avoid disaster, an aggregated measure using a fast report | |||
have a cycle of aggregation greater than or equal to 1 second and | must have a cycle of aggregation greater than or equal to 1 | |||
should not sent more than an email every 5 minutes and should not | second and should not sent more than an email every 5 minutes | |||
sent more than 12 emails." | and should not sent more than 12 emails." | |||
DEFVAL { zeroDotZero } | DEFVAL { zeroDotZero } | |||
::= { ippmAggrMeasureEntry 20 } | ::= { ippmAggrMeasureEntry 20 } | |||
ippmAggrMeasureLastUpdate OBJECT-TYPE | ippmAggrMeasureLastUpdate OBJECT-TYPE | |||
SYNTAX GMTTimeStamp | SYNTAX GMTTimeStamp | |||
MAX-ACCESS read-only | MAX-ACCESS read-only | |||
STATUS current | STATUS current | |||
DESCRIPTION | DESCRIPTION | |||
"The time when the last aggregated measure was computed." | "The time when the last aggregated measure was computed." | |||
::= { ippmAggrMeasureEntry 21 } | ::= { ippmAggrMeasureEntry 21 } | |||
skipping to change at page 52, line 5 | skipping to change at page 58, line 17 | |||
ippmAggrMeasureNbPktsTreated OBJECT-TYPE | ippmAggrMeasureNbPktsTreated OBJECT-TYPE | |||
SYNTAX Counter64 | SYNTAX Counter64 | |||
UNITS "Packets" | UNITS "Packets" | |||
MAX-ACCESS read-only | MAX-ACCESS read-only | |||
STATUS current | STATUS current | |||
DESCRIPTION | DESCRIPTION | |||
"Reports the current number of packets used to calculate the | "Reports the current number of packets used to calculate the | |||
aggregation since the start of the measure. | aggregation since the start of the measure. | |||
This parameters is useful to monitor the measure and it is needed | This parameters is useful to monitor the measure and it is | |||
to compute statistics." | needed to compute statistics." | |||
::= { ippmAggrMeasureEntry 23 } | ::= { ippmAggrMeasureEntry 23 } | |||
ippmAggrMeasureStatus OBJECT-TYPE | ippmAggrMeasureStatus OBJECT-TYPE | |||
SYNTAX RowStatus | SYNTAX RowStatus | |||
MAX-ACCESS read-create | MAX-ACCESS read-create | |||
STATUS current | STATUS current | |||
DESCRIPTION | DESCRIPTION | |||
"The status of this entry. Once the entry status is set to | "The status of this entry. Once the entry status is set to | |||
active, the associate entry cannot be modified. | active, the associate entry cannot be modified. | |||
" | " | |||
skipping to change at page 52, line 40 | skipping to change at page 59, line 12 | |||
ippmMetricsDescription, | ippmMetricsDescription, | |||
ippmHistoryTimestamp, | ippmHistoryTimestamp, | |||
ippmHistoryValue, | ippmHistoryValue, | |||
ippmHistoryPathToResults | ippmHistoryPathToResults | |||
} | } | |||
STATUS current | STATUS current | |||
DESCRIPTION | DESCRIPTION | |||
"A notification sent because the value of the measure is under | "A notification sent because the value of the measure is under | |||
the high threshold value and greater than the low threshold | the high threshold value and greater than the low threshold | |||
value. | value. | |||
The notification contains the instances of the ippmHistoryValue | The notification contains the instances of the | |||
object that exceeded the threshold. | ippmHistoryValue object that exceeded the threshold. | |||
The notification contains the instances of the | The notification contains the instances of the | |||
ippmHistoryTimestamp identifying the time the event occurred. | ippmHistoryTimestamp identifying the time the event occurred. | |||
ippmHistoryPathToResults is a link to the file name, which | ippmHistoryPathToResults is a link to the file name, which | |||
contains detailed results corresponding to this event." | contains detailed results corresponding to this event." | |||
::= { ippmNotifications 1 } | ::= { ippmNotifications 1 } | |||
ippmAggrMeasureHistoryFull NOTIFICATION-TYPE | ippmAggrMeasureHistoryFull NOTIFICATION-TYPE | |||
OBJECTS { | OBJECTS { | |||
ippmAggrMeasureName, | ippmAggrMeasureName, | |||
ippmAggrMeasureHistorySize, | ippmAggrMeasureHistorySize, | |||
ippmMetricsType, | ippmMetricsType, | |||
ippmMetricsUnit, | ippmMetricsUnit, | |||
ippmMetricsDescription, | ippmMetricsDescription, | |||
ippmHistoryTimestamp, | ippmHistoryTimestamp, | |||
ippmHistoryValue | ippmHistoryValue | |||
} | } | |||
STATUS current | STATUS current | |||
DESCRIPTION | DESCRIPTION | |||
skipping to change at page 53, line 14 | skipping to change at page 59, line 34 | |||
ippmAggrMeasureHistorySize, | ippmAggrMeasureHistorySize, | |||
ippmMetricsType, | ippmMetricsType, | |||
ippmMetricsUnit, | ippmMetricsUnit, | |||
ippmMetricsDescription, | ippmMetricsDescription, | |||
ippmHistoryTimestamp, | ippmHistoryTimestamp, | |||
ippmHistoryValue | ippmHistoryValue | |||
} | } | |||
STATUS current | STATUS current | |||
DESCRIPTION | DESCRIPTION | |||
"A notification sent when the size of the history of a metric of | "A notification sent when the size of the history of a metric | |||
a aggregated measure exceeds ippmAggrMeasureHistorySize. The | of a aggregated measure exceeds ippmAggrMeasureHistorySize. | |||
agent will then manage the reports according to the policy | The agent will then manage the reports according to the policy | |||
described in ippmAggrMeasureResultsMgmt." | described in ippmAggrMeasureResultsMgmt." | |||
::= { ippmNotifications 2 } | ::= { ippmNotifications 2 } | |||
ippmNetMeasureHistoryFull NOTIFICATION-TYPE | ippmNetMeasureHistoryFull NOTIFICATION-TYPE | |||
OBJECTS { | OBJECTS { | |||
ippmNetMeasureName, | ippmNetMeasureName, | |||
ippmNetMeasureHistorySize, | ippmNetMeasureHistorySize, | |||
ippmMetricsType, | ippmMetricsType, | |||
ippmMetricsUnit, | ippmMetricsUnit, | |||
ippmMetricsDescription, | ippmMetricsDescription, | |||
ippmHistoryTimestamp, | ippmHistoryTimestamp, | |||
ippmHistoryValue | ippmHistoryValue | |||
} | } | |||
STATUS current | STATUS current | |||
DESCRIPTION | DESCRIPTION | |||
"A notification sent when the size of the history of a metric of | "A notification sent when the size of the history of a metric | |||
a network measure exceeded ippmNetMeasureHistorySize. Then the | of a network measure exceeded ippmNetMeasureHistorySize. Then | |||
agent manages the records according to the policy described in | the agent manages the records according to the policy | |||
ippmNetMeasureResultsMgmt." | described in ippmNetMeasureResultsMgmt." | |||
::= { ippmNotifications 3 } | ::= { ippmNotifications 3 } | |||
-- | -- | |||
-- 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 | |||
IPPM MIB as a proxy in interdomain. The implementation of the | the IPPM MIB as a proxy in interdomain. The implementation of | |||
VACM control is mandatory." | the VACM control is mandatory." | |||
MODULE -- this module | MODULE -- this module | |||
MANDATORY-GROUPS { | MANDATORY-GROUPS { | |||
ippmSystemGroup, ippmHistoryGroup, ippmNetMeasureGroup, | ippmSystemGroup, ippmHistoryGroup, ippmNetMeasureGroup, | |||
ippmAggrMeasureGroup, ippmNotificationGroup | ippmAggrMeasureGroup, ippmNotificationGroup | |||
} | } | |||
OBJECT ippmNetMeasureName | ||||
MIN-ACCESS read-only | ||||
DESCRIPTION | ||||
"In Proxy mode network measures may be managed using another | ||||
interface than SNMP." | ||||
OBJECT ippmNetMeasureMetrics | ||||
MIN-ACCESS read-only | ||||
DESCRIPTION | ||||
"In Proxy mode network measures may be managed using another | ||||
interface than SNMP." | ||||
OBJECT ippmNetMeasureBeginTime | ||||
MIN-ACCESS read-only | ||||
DESCRIPTION | ||||
"In Proxy mode network measures may be managed using another | ||||
interface than SNMP." | ||||
OBJECT ippmNetMeasureCollectionRateUnit | ||||
MIN-ACCESS read-only | ||||
DESCRIPTION | ||||
"In Proxy mode network measures may be managed using another | ||||
interface than SNMP." | ||||
OBJECT ippmNetMeasureCollectionRate | ||||
MIN-ACCESS read-only | ||||
DESCRIPTION | ||||
"In Proxy mode network measures may be managed using another | ||||
interface than SNMP." | ||||
OBJECT ippmNetMeasureDurationUnit | ||||
MIN-ACCESS read-only | ||||
DESCRIPTION | ||||
"In Proxy mode network measures may be managed using another | ||||
interface than SNMP." | ||||
OBJECT ippmNetMeasureDuration | ||||
MIN-ACCESS read-only | ||||
DESCRIPTION | ||||
"In Proxy mode network measures may be managed using another | ||||
interface than SNMP." | ||||
OBJECT ippmNetMeasureHistorySize | ||||
MIN-ACCESS read-only | ||||
DESCRIPTION | ||||
"In Proxy mode network measures may be managed using another | ||||
interface than SNMP." | ||||
OBJECT ippmNetMeasureFailureMgmtMode | ||||
MIN-ACCESS read-only | ||||
DESCRIPTION | ||||
"In Proxy mode network measures may be managed using another | ||||
interface than SNMP." | ||||
OBJECT ippmNetMeasureResultsMgmt | ||||
MIN-ACCESS read-only | ||||
DESCRIPTION | ||||
"In Proxy mode network measures may be managed using another | ||||
interface than SNMP." | ||||
OBJECT ippmNetMeasureSrcPacketType | ||||
MIN-ACCESS read-only | ||||
DESCRIPTION | ||||
"In Proxy mode network measures may be managed using another | ||||
interface than SNMP." | ||||
OBJECT ippmNetMeasureSrc | ||||
MIN-ACCESS read-only | ||||
DESCRIPTION | ||||
"In Proxy mode network measures may be managed using another | ||||
interface than SNMP." | ||||
OBJECT ippmNetMeasureDstPacketType | ||||
MIN-ACCESS read-only | ||||
DESCRIPTION | ||||
"In Proxy mode network measures may be managed using another | ||||
interface than SNMP." | ||||
OBJECT ippmNetMeasureDst | ||||
MIN-ACCESS read-only | ||||
DESCRIPTION | ||||
"In Proxy mode network measures may be managed using another | ||||
interface than SNMP." | ||||
OBJECT ippmNetMeasureTxMode | ||||
MIN-ACCESS read-only | ||||
DESCRIPTION | ||||
"In Proxy mode network measures may be managed using another | ||||
interface than SNMP." | ||||
OBJECT ippmNetMeasureTxPacketRateUnit | ||||
MIN-ACCESS read-only | ||||
DESCRIPTION | ||||
"In Proxy mode network measures may be managed using another | ||||
interface than SNMP." | ||||
OBJECT ippmNetMeasureTxPacketRate | ||||
MIN-ACCESS read-only | ||||
DESCRIPTION | ||||
"In Proxy mode network measures may be managed using another | ||||
interface than SNMP." | ||||
OBJECT ippmNetMeasureMedOrBurstSize | ||||
MIN-ACCESS read-only | ||||
DESCRIPTION | ||||
"In Proxy mode network measures may be managed using another | ||||
interface than SNMP." | ||||
OBJECT ippmNetMeasureDevOrIntBurstSize | ||||
MIN-ACCESS read-only | ||||
DESCRIPTION | ||||
"In Proxy mode network measures may be managed using another | ||||
interface than SNMP." | ||||
OBJECT ippmNetMeasureLossTimeout | ||||
MIN-ACCESS read-only | ||||
DESCRIPTION | ||||
"In Proxy mode network measures may be managed using another | ||||
interface than SNMP." | ||||
OBJECT ippmNetMeasureL3PacketSize | ||||
MIN-ACCESS read-only | ||||
DESCRIPTION | ||||
"In Proxy mode network measures may be managed using another | ||||
interface than SNMP." | ||||
OBJECT ippmNetMeasureDataPattern | ||||
MIN-ACCESS read-only | ||||
DESCRIPTION | ||||
"In Proxy mode network measures may be managed using another | ||||
interface than SNMP." | ||||
::= { ippmCompliances 1 } | ::= { ippmCompliances 1 } | |||
ippmProxyCompliances MODULE-COMPLIANCE | ippmProxyCompliance 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 | |||
IPPM MIB as a proxy." | the IPPM MIB as a proxy." | |||
MODULE -- this module | MODULE -- this module | |||
MANDATORY-GROUPS { | MANDATORY-GROUPS { | |||
ippmSystemGroup, ippmOwnersGroup, ippmHistoryGroup, | ippmSystemGroup, ippmOwnersGroup, ippmHistoryGroup, | |||
ippmNetMeasureGroup, ippmAggrMeasureGroup, ippmNotificationGroup | ippmNetMeasureGroup, ippmAggrMeasureGroup, | |||
ippmNotificationGroup | ||||
} | } | |||
GROUP ippmOwnersGroup | GROUP ippmOwnersGroup | |||
DESCRIPTION | DESCRIPTION | |||
"The ippmOwnersGroup is needed if VACM is not implemented." | "The ippmOwnersGroup is manadatory if VACM is not | |||
::= { ippmCompliances 2 } | implemented." | |||
ippmEmbeddedCompliances MODULE-COMPLIANCE | OBJECT ippmNetMeasureName | |||
MIN-ACCESS read-only | ||||
DESCRIPTION | ||||
"In Proxy mode network measures may be managed using another | ||||
interface than SNMP." | ||||
OBJECT ippmNetMeasureMetrics | ||||
MIN-ACCESS read-only | ||||
DESCRIPTION | ||||
"In Proxy mode network measures may be managed using another | ||||
interface than SNMP." | ||||
OBJECT ippmNetMeasureBeginTime | ||||
MIN-ACCESS read-only | ||||
DESCRIPTION | ||||
"In Proxy mode network measures may be managed using another | ||||
interface than SNMP." | ||||
OBJECT ippmNetMeasureCollectionRateUnit | ||||
MIN-ACCESS read-only | ||||
DESCRIPTION | ||||
"In Proxy mode network measures may be managed using another | ||||
interface than SNMP." | ||||
OBJECT ippmNetMeasureCollectionRate | ||||
MIN-ACCESS read-only | ||||
DESCRIPTION | ||||
"In Proxy mode network measures may be managed using another | ||||
interface than SNMP." | ||||
OBJECT ippmNetMeasureDurationUnit | ||||
MIN-ACCESS read-only | ||||
DESCRIPTION | ||||
"In Proxy mode network measures may be managed using another | ||||
interface than SNMP." | ||||
OBJECT ippmNetMeasureDuration | ||||
MIN-ACCESS read-only | ||||
DESCRIPTION | ||||
"In Proxy mode network measures may be managed using another | ||||
interface than SNMP." | ||||
OBJECT ippmNetMeasureHistorySize | ||||
MIN-ACCESS read-only | ||||
DESCRIPTION | ||||
"In Proxy mode network measures may be managed using another | ||||
interface than SNMP." | ||||
OBJECT ippmNetMeasureFailureMgmtMode | ||||
MIN-ACCESS read-only | ||||
DESCRIPTION | ||||
"In Proxy mode network measures may be managed using another | ||||
interface than SNMP." | ||||
OBJECT ippmNetMeasureResultsMgmt | ||||
MIN-ACCESS read-only | ||||
DESCRIPTION | ||||
"In Proxy mode network measures may be managed using another | ||||
interface than SNMP." | ||||
OBJECT ippmNetMeasureSrcPacketType | ||||
MIN-ACCESS read-only | ||||
DESCRIPTION | ||||
"In Proxy mode network measures may be managed using another | ||||
interface than SNMP." | ||||
OBJECT ippmNetMeasureSrc | ||||
MIN-ACCESS read-only | ||||
DESCRIPTION | ||||
"In Proxy mode network measures may be managed using another | ||||
interface than SNMP." | ||||
OBJECT ippmNetMeasureDstPacketType | ||||
MIN-ACCESS read-only | ||||
DESCRIPTION | ||||
"In Proxy mode network measures may be managed using another | ||||
interface than SNMP." | ||||
OBJECT ippmNetMeasureDst | ||||
MIN-ACCESS read-only | ||||
DESCRIPTION | ||||
"In Proxy mode network measures may be managed using another | ||||
interface than SNMP." | ||||
OBJECT ippmNetMeasureTxMode | ||||
MIN-ACCESS read-only | ||||
DESCRIPTION | ||||
"In Proxy mode network measures may be managed using another | ||||
interface than SNMP." | ||||
OBJECT ippmNetMeasureTxPacketRateUnit | ||||
MIN-ACCESS read-only | ||||
DESCRIPTION | ||||
"In Proxy mode network measures may be managed using another | ||||
interface than SNMP." | ||||
OBJECT ippmNetMeasureTxPacketRate | ||||
MIN-ACCESS read-only | ||||
DESCRIPTION | ||||
"In Proxy mode network measures may be managed using another | ||||
interface than SNMP." | ||||
OBJECT ippmNetMeasureMedOrBurstSize | ||||
MIN-ACCESS read-only | ||||
DESCRIPTION | ||||
"In Proxy mode network measures may be managed using another | ||||
interface than SNMP." | ||||
OBJECT ippmNetMeasureDevOrIntBurstSize | ||||
MIN-ACCESS read-only | ||||
DESCRIPTION | ||||
"In Proxy mode network measures may be managed using another | ||||
interface than SNMP." | ||||
OBJECT ippmNetMeasureLossTimeout | ||||
MIN-ACCESS read-only | ||||
DESCRIPTION | ||||
"In Proxy mode network measures may be managed using another | ||||
interface than SNMP." | ||||
OBJECT ippmNetMeasureL3PacketSize | ||||
MIN-ACCESS read-only | ||||
DESCRIPTION | ||||
"In Proxy mode network measures may be managed using another | ||||
interface than SNMP." | ||||
OBJECT ippmNetMeasureDataPattern | ||||
MIN-ACCESS read-only | ||||
DESCRIPTION | ||||
"In Proxy mode network measures may be managed using another | ||||
interface than SNMP." | ||||
::= { ippmCompliances 2 } | ||||
ippmEmbeddedCompliance 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 | |||
IPPM MIB in a probe." | the IPPM MIB in a probe." | |||
MODULE -- this module | MODULE -- this module | |||
MANDATORY-GROUPS { | MANDATORY-GROUPS { | |||
ippmSystemGroup, ippmHistoryGroup, ippmNetMeasureGroup | ippmSystemGroup, ippmHistoryGroup, ippmNetMeasureGroup | |||
} | } | |||
::= { ippmCompliances 3 } | ::= { ippmCompliances 3 } | |||
ippmSystemGroup OBJECT-GROUP | ippmSystemGroup OBJECT-GROUP | |||
OBJECTS { | OBJECTS { | |||
ippmSystemSynchronizationDesc, | ippmSystemSynchronizationDesc, | |||
ippmSystemTime, | ippmSystemTime, | |||
skipping to change at page 57, line 14 | skipping to change at page 70, line 9 | |||
ippmNetMeasureHistoryFull, | ippmNetMeasureHistoryFull, | |||
ippmAggrMeasureHistoryFull | ippmAggrMeasureHistoryFull | |||
} | } | |||
STATUS current | STATUS current | |||
DESCRIPTION | DESCRIPTION | |||
"The IPPM Notification Group" | "The IPPM Notification Group" | |||
::= { ippmGroups 6} | ::= { ippmGroups 6} | |||
END | END | |||
8 Security Considerations | 8. Security Considerations | |||
8.1 VACM Access control | 8.1 VACM Access control | |||
View Based Access Control, or VACM may be used to restrict access to | View Based Access Control, or VACM may be used to restrict access to | |||
certain objects, or even object instances within tables. For example, | certain objects, or even object instances within tables. For | |||
one may: | example, one may: | |||
+ Give an 'administrator' write access to the ippmOwnersTable, | o Give an 'administrator' write access to the ippmOwnersTable, | |||
whereas all other users may only have read access | whereas all other users may only have read access; | |||
+ Give access to individual rows in the network measure, aggregated | ||||
o Give access to individual rows in the network measure, aggregated | ||||
measure, history, and report table to particular owners based upon | measure, history, and report table to particular owners based upon | |||
indexing on an 'owners name', and even upon a particular measure. | indexing on an 'owners name', and even upon a particular measure. | |||
This will be illustrated below. | This will be illustrated below. | |||
+ Give access of one ownerÆs measure, and associated results, to | ||||
another owner in order to create an aggregated measure based upon the | o Give access of one owner's measure, and associated results, to | |||
results. | 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 | 8.1.1 Example of implementing VACM control for the IPPM-REPORTING-MIB | |||
The following example illustrates how one could use VACM to restrict | The following example illustrates how one could use VACM to restrict | |||
access to particular objects within the MIB. It uses syntax specific | access to particular objects within the MIB. It uses syntax specific | |||
to a particular agent development toolkit, but may be generalized | to a particular agent development toolkit, but may be generalized | |||
using the concepts as defined in the VACM MIB. | using the concepts as defined in the VACM MIB. | |||
In this example, we have two NMS users, namely user1=owner1 and | In this example, we have two NMS users, namely user1=owner1 and | |||
user2=owner2: | user2=owner2: | |||
skipping to change at page 59, line 26 | skipping to change at page 73, line 26 | |||
ippmReportSequence.6.111.119.110.101.114.50 ff.df.c0 | ippmReportSequence.6.111.119.110.101.114.50 ff.df.c0 | |||
3.5) Now we give the two users access to the views defined above. | 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 | Note that owner1 and owner2 have read access to owner1read and | |||
owner2read views respectively. They have write access to owner1write | owner2read views respectively. They have write access to owner1write | |||
and owner2write view respectively. And they both have access to all | and owner2write view respectively. And they both have access to all | |||
the notifications. | the notifications. | |||
access owner1 "" any noauth exact owner1read | access owner1 "" any noauth exact owner1read | |||
owner1write notif | owner1write notif | |||
access owner2 "" any noauth exact owner2read | access owner2 "" any noauth exact owner2read | |||
owner2write notif | owner2write notif | |||
8.2 Privacy | 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 | |||
no release of existing user data. | be no release of existing user data. | |||
8.3 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. | |||
skipping to change at page 60, line 22 | skipping to change at page 74, line 23 | |||
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. | |||
8.4 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 | |||
may be considered sensitive or vulnerable in some network | objects 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 | |||
control as to who on the secure network is allowed to access and | control as to who on the secure network is allowed to access and GET/ | |||
GET/SET (read/change/create/delete) the objects in this MIB. | SET (read/change/create/delete) the objects in this MIB. | |||
It is recommended that the implementors consider the security | It is recommended that the implementors consider the security | |||
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/ | |||
(change/create/delete) them. | create/delete) them. | |||
9 Document management | 9. Document management | |||
9.1 Open issues | 9.1 Open issues | |||
Smilint complains when accessible-for-notify is used for an index. | Do we use accessible-for-notify to report index values in the | |||
notifications ? | ||||
ippmNetMeasure items Read Write ? | ||||
9.2 Changes done since release 04 | Do we need an "IANA Considerations" Section ? | |||
Report Group deleted: | Do we need separate NetMeasure history from aggregateMeasure | |||
reportHistoryTable deleted; | History (may help compliance module spec) ? | |||
reportSetupTable deleted; | ||||
6 related notifications deleted; | ||||
low and high thresholds added in ippmAggrMeasureTable; | 9.2 Changes done since release 05 | |||
TC IppmOwnerIndex added to clearly define the owner namespace. | o Document rewriten in xml; | |||
GMTTimestamp time origine changed to NTP (1900). | o Section 3 updated with the "standard" introductionary text for | |||
MIB; | ||||
9.3 Changes done since release 03 | o nodes cleanup; | |||
+ SMI subtype: INTEGER vs Integer32...; | o ippmNetMeasure max acces set to read-create; | |||
+ SMI UNITS: Clauses added; | ||||
+ cleanup of DEFVAL values; | ||||
+ Counter/index wrapping: | o proxy compliances module reviewed for the usage of the | |||
the index of the table wrap independently of the sequence of the | ippmNetMeasureTable with a min acces of read-only; | |||
results. That makes it very difficult for application to track the | ||||
results. As the sequence id identify the instance of the result of a | ||||
measure the index is removed both from the table and from the index | ||||
clause. | ||||
ippmHistoryIndex removed from ippmHistoryEntry; | ||||
ippmHistoryIndex removed from the INDEX clause of the table | ||||
ippmHistoryTable; | ||||
ippmReportIndex removed from ippmAggrHistoryEntry; | ||||
ippmReportIndex removed from the clause INDEX of | ||||
ippmAggrHistoryEntry INDEX clause of the table ippmAggrHistoryTable; | ||||
9.4 Changes done since release 02 | o A new co-authored: Tom; | |||
+ Security/VACM: | 9.3 Changes done since release 04 | |||
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 | ||||
+ System: | o Report Group deleted: | |||
ippmSystemOperationalStatus added | ||||
ippmSynchronizationTable adapted for proxy mode: | * reportHistoryTable deleted; | |||
ippmPointOfMeasureIndex added to the index of | ||||
ippmSystemCurrentSynchronization removed from system | ||||
capabilities: | * reportSetupTable deleted; | |||
ippmPointOfMeasureMetrics added to | ||||
IppmPointOfMeasureEntry; | ||||
ippmMetricsType added to ippmMetricsTable; | ||||
+ Owners | o 6 related notifications deleted; | |||
ippmMetricMaxHistorySize replaced with quota in ippmOwnersTable; | ||||
+ ippmOnHistoryFullAction replaced with resultsMgmt in aggr and network.; | o low and high thresholds added in ippmAggrMeasureTable; | |||
+ network measure: | o TC IppmOwnerIndex added to clearly define the owner namespace. | |||
ippmNetMeasureOperState added to indicate the state of the network | ||||
measure | ||||
state; | ||||
added burst mode; | ||||
state of the measure: nb of singletons collected and oper status | ||||
added; | ||||
+aggregated metric: | o GMTTimestamp time origine changed to NTP (1900). | |||
fast report added to get raw results by email; | ||||
+ report setup: | 9.4 Changes done since release 03 | |||
onReportDeliveryClearHistory removed from | ||||
IppmMetricResultFilter; | ||||
+ Map field added to network, aggr and report tables to help to map | o SMI subtype: INTEGER vs Integer32...; | |||
on topology map or admin view. | ||||
10 References | o SMI UNITS: Clauses added; | |||
[1] Bradner, S., "The Internet Standards Process -- Revision 3", BCP | o cleanup of DEFVAL values; | |||
9, RFC 2026, October 1996. | ||||
[2] Harrington, D., Presuhn, R., and B. Wijnen, "An Architecture for | o Counter/index wrapping: | |||
Describing SNMP Management Frameworks", RFC 2571, April 1999. | ||||
[3] Rose, M., and K. McCloghrie, "Structure and Identification of | o the index of the table wrap independently of the sequence of the | |||
Management Information for TCP/IP-based Internets", STD 16, RFC | results. That makes it very difficult for application to track | |||
1155, May 1990. | the results. As the sequence id identify the instance of the | |||
result of a measure the index is removed both from the table and | ||||
from the index clause: | ||||
[4] Rose, M., and K. McCloghrie, "Concise MIB Definitions", STD 16, | * ippmHistoryIndex removed from ippmHistoryEntry; | |||
RFC 1212, March 1991. | ||||
[5] M. Rose, "A Convention for Defining Traps for use with the SNMP", | * ippmHistoryIndex removed from the INDEX clause of the table | |||
RFC 1215, March 1991. | ippmHistoryTable; | |||
[6] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, | * ippmReportIndex removed from ippmAggrHistoryEntry; | |||
M., and S. Waldbusser, "Structure of Management Information | ||||
Version 2 (SMIv2)", STD 58, RFC 2578, April 1999. | ||||
[7] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, | * ippmReportIndex removed from the clause INDEX of | |||
M., and S. Waldbusser, "Textual Conventions for SMIv2", STD 58, | ippmAggrHistoryEntry INDEX clause of the table | |||
RFC 2579, April 1999. | ippmAggrHistoryTable; | |||
[8] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, | 9.5 Changes done since release 02 | |||
M., and S. Waldbusser, "Conformance Statements for SMIv2", STD 58, | ||||
RFC 2580, April 1999. | ||||
[9] Case, J., Fedor, M., Schoffstall, M., and J. Davin, "Simple | o Security/VACM: sharing table removed; ippmMeasure merged with | |||
Network Management Protocol", STD 15, RFC 1157, May 1990. | networkMeasure and AggrMeasure to have all networkMeasure objects | |||
in read only. Indexes belong to the table; remove all reference | ||||
to SNMPv1 ...inSNMPTrapPDU | ||||
[10] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, | o System: ippmSystemOperationalStatus added ippmSynchronizationTable | |||
"Introduction to Community-based SNMPv2", RFC 1901, January 1996. | adapted for proxy mode: ippmPointOfMeasureIndex added to the index | |||
of ippmSystemCurrentSynchronization removed from system | ||||
capabilities: ippmPointOfMeasureMetrics added to | ||||
IppmPointOfMeasureEntry; ippmMetricsType added to | ||||
ippmMetricsTable; | ||||
[11] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, | o Owners: ippmMetricMaxHistorySize replaced with quota in | |||
"Transport Mappings for Version 2 of the Simple Network Management | ippmOwnersTable; | |||
Protocol (SNMPv2)", RFC 1906, January 1996. | ||||
[12]Case, J., Harrington D., Presuhn R., and B. Wijnen, "Message | o ippmOnHistoryFullAction replaced with resultsMgmt in aggr and | |||
Processing and Dispatching for the Simple Network Management | network.; | |||
Protocol (SNMP)", RFC 2572, April 1999. | ||||
[13] Blumenthal, U., and B. Wijnen, "User-based Security Model (USM) | o network measure: ippmNetMeasureOperState added to indicate the | |||
for version 3 of the Simple Network Management Protocol (SNMPv3)", | state of the network measure state; added burst mode; state of the | |||
RFC 2574, April 1999. | measure: nb of singletons collected and oper status added; | |||
[14] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Protocol | o aggregated metric: fast report added to get raw results by email; | |||
Operations for Version 2 of the Simple Network Management Protocol | o report setup: onReportDeliveryClearHistory removed from | |||
(SNMPv2)", RFC 1905, January 1996. | IppmMetricResultFilter; | |||
[15] Levi, D., Meyer, P., and B. Stewart, "SNMPv3 Applications", RFC | o Map field added to network, aggr and report tables to help to map | |||
2573, April 1999. | on topology map or admin view. | |||
[16] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-basedAccess | 10. Acknowledgments | |||
Control Model (VACM) for the Simple Network Management Protocol | ||||
(SNMP)", RFC 2575, April 1999. | ||||
[17] Case, J., Mundy, R., Partain, D., and B. Stewart, "Introduction | A Kerbe. | |||
to Version 3 of the Internet-standard Network Management | ||||
Framework", RFC 2570, April 1999. | ||||
11 Acknowledgments | 11. References | |||
A Kerbe. | 11.1 Normative References | |||
12 Authors' Addresses | [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., | |||
McCloghrie, K., Rose, M. and S. Waldbusser, "Structure of | ||||
Management Information Version 2 (SMIv2)", STD 58, RFC | ||||
2578, April 1999. | ||||
Emile STEPHAN | [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., | |||
McCloghrie, K., Rose, M. and S. Waldbusser, "Textual | ||||
Conventions for SMIv2", STD 58, RFC 2579, April 1999. | ||||
[RFC2580] McCloghrie, K., Perkins, D. and J. Schoenwaelder, | ||||
"Conformance Statements for SMIv2", STD 58, RFC 2580, | ||||
April 1999. | ||||
11.2 Informative References | ||||
[RFC2330] Paxson, V., Almes, G., Mahdavi, J. and M. Mathis, | ||||
"Framework for IP Performance Metrics", RFC 2330, May | ||||
1998. | ||||
[RFC2678] Mahdavi, J. and V. Paxson, "IPPM Metrics for Measuring | ||||
Connectivity", RFC 2678, September 1999. | ||||
[RFC2679] Almes, G., Kalidindi, S. and M. Zekauskas, "A One-way | ||||
Delay Metric for IPPM", RFC 2679, September 1999. | ||||
[RFC2680] Almes, G., Kalidindi, S. and M. Zekauskas, "A One-way | ||||
Packet Loss Metric for IPPM", RFC 2680, September 1999. | ||||
[RFC2681] Almes, G., Kalidindi, S. and M. Zekauskas, "A Round-trip | ||||
Delay Metric for IPPM", RFC 2681, September 1999. | ||||
[RFC3357] Koodli, R. and R. Ravikanth, "One-way Loss Pattern Sample | ||||
Metrics", RFC 3357, August 2002. | ||||
[RFC3393] Demichelis, C. and P. Chimento, "IP Packet Delay Variation | ||||
Metric for IP Performance Metrics (IPPM)", RFC 3393, | ||||
November 2002. | ||||
[RFC3410] Case, J., Mundy, R., Partain, D. and B. Stewart, | ||||
"Introduction and Applicability Statements for | ||||
Internet-Standard Management Framework", RFC 3410, | ||||
December 2002. | ||||
[RFC3432] Raisanen, V., Grotefeld, G. and A. Morton, "Network | ||||
performance measurement with periodic streams", RFC 3432, | ||||
November 2002. | ||||
Authors' Addresses | ||||
Stephan Emile | ||||
France Telecom R & D | France Telecom R & D | |||
2 avenue Pierre Marzin | 2 avenue Pierre Marzin | |||
F-22307 Lannion cedex | Lannion, F-22307 | |||
Phone: (+ 33) 2 96 05 11 11 | ||||
Email: emile.stephan@francetelecom.com | ||||
Jessie Jewitt | Phone: +33 2 96 05 11 11 | |||
Fax: +33 2 96 05 18 52 | ||||
EMail: emile.stephan@francetelecom.com | ||||
Jewitt Jessie | ||||
France Telecom R & D | France Telecom R & D | |||
801 Gateway Blvd. Suit 500 | 801 Gateway Blvd. Suit 500 | |||
South San Francisco, CA 94080 | South San Francisco, CA-94080 | |||
Tel: 1 650 875-1524 | ||||
Email: jessie.jewitt@francetelecom.com | EMail: jessie.jewitt@francetelecom.com | |||
Intellectual Property Statement | ||||
The IETF takes no position regarding the validity or scope of any | ||||
intellectual property or other rights that might be claimed to | ||||
pertain to the implementation or use of the technology described in | ||||
this document or the extent to which any license under such rights | ||||
might or might not be available; neither does it represent that it | ||||
has made any effort to identify any such rights. Information on the | ||||
IETF's procedures with respect to rights in standards-track and | ||||
standards-related documentation can be found in BCP-11. Copies of | ||||
claims of rights made available for publication and any assurances of | ||||
licenses to be made available, or the result of an attempt made to | ||||
obtain a general license or permission for the use of such | ||||
proprietary rights by implementors or users of this specification can | ||||
be obtained from the IETF Secretariat. | ||||
The IETF invites any interested party to bring to its attention any | ||||
copyrights, patents or patent applications, or other proprietary | ||||
rights which may cover technology that may be required to practice | ||||
this standard. Please address the information to the IETF Executive | ||||
Director. | ||||
Full Copyright Statement | Full Copyright Statement | |||
"Copyright (C) The Internet Society (2001). All Rights Reserved. | Copyright (C) The Internet Society (2004). All Rights Reserved. | |||
This document and translations of it may be copied and furnished to | This document and translations of it may be copied and furnished to | |||
others, and derivative works that comment on or otherwise explain it | others, and derivative works that comment on or otherwise explain it | |||
or assist its implementation may be prepared, copied, published and | or assist in its implementation may be prepared, copied, published | |||
distributed, in whole or in part, without restriction of any kind, | and distributed, in whole or in part, without restriction of any | |||
provided that the above copyright notice and this paragraph are | kind, provided that the above copyright notice and this paragraph are | |||
included on all such copies and derivative works. However, this | included on all such copies and derivative works. However, this | |||
document itself may not be modified in any way, such as by removing | document itself may not be modified in any way, such as by removing | |||
the copyright notice or references to the Internet Society or other | the copyright notice or references to the Internet Society or other | |||
Internet organizations, except as needed for the purpose of | Internet organizations, except as needed for the purpose of | |||
developing Internet standards in which case the procedures for | developing Internet standards in which case the procedures for | |||
copyrights defined in the Internet Standards process must be | copyrights defined in the Internet Standards process must be | |||
followed, or as required to translate it into languages other than | followed, or as required to translate it into languages other than | |||
English. | English. | |||
The limited permissions granted above are perpetual and will not be | The limited permissions granted above are perpetual and will not be | |||
revoked by the Internet Society or its successors or assigns. | revoked by the Internet Society or its successors or assignees. | |||
This document and the information contained herein is provided on an | This document and the information contained herein is provided on an | |||
"AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING | "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING | |||
TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING | TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING | |||
BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION | BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION | |||
HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF | HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF | |||
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. | MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. | |||
Acknowledgment | ||||
Funding for the RFC Editor function is currently provided by the | ||||
Internet Society. | ||||
End of changes. | ||||
This html diff was produced by rfcdiff 1.23, available from http://www.levkowetz.com/ietf/tools/rfcdiff/ |