Internet Draft C. Kalbfleisch
NTT/VERIO
R.G. Cole
AT&T
D. Romascanu
Avaya Communication
3 June 2002
Definition of Managed Objects for Synthetic Sources for
Performance Monitoring Algorithms.
<draft-ietf-rmonmib-sspm-mib-03.txt>
Status of this Memo
This document is an Internet-Draft and is in full conformance with
all provisions of Section 10 of RFC2026. Internet-Drafts are working
documents of the Internet Engineering Task Force (IETF), its areas,
and its working groups. Note that other groups may also distribute
working documents as Internet-Drafts.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet- Drafts as reference
material or to cite them other than as "work in progress."
To view the list Internet-Draft Shadow Directories, see
http://www.ietf.org/shadow.html.
Copyright Notice
Copyright (C) The Internet Society (2000). All Rights Reserved.
Abstract
This memo defines a portion of the Management Information Base (MIB)
for use with network management protocols in the Internet community.
In particular, it describes objects for configuring Synthetic Sources
for Performance Monitoring algorithms (SSPM).
This memo specifies a MIB module in a manner that is both compliant
to the SMIv2, and semantically identical to the peer SMIv1
definitions.
Distribution of this memo is unlimited.
C. Kalbfleisch Expires Dec 2002 [Page 1]
INTERNET DRAFT SSPM MIB Jun 2002
1. Introduction
This memo defines a portion of the Management Information Base (MIB)
for use with network management protocols in the Internet community.
In particular, it defines a method of describing Synthetic Sources
for Performance Monitoring (SSPM). This is useful within the RMON
framework for performance monitoring in the cases where it is
desireable to inject packets into the network for the purpose of
monitoring their performance with the other MIBs in that framework.
This memo also includes a MIB module. This MIB module extends the
list of managed objects specified in [xx] and [xx].
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in [xx].
2. The SNMP Management Framework
The SNMP Management Framework presently consists of five major
components:
o An overall architecture, described in RFC 2271 [1].
o Mechanisms for describing and naming objects and events for the
purpose of management. The first version of this Structure of
Management Information (SMI) is called SMIv1 and described in RFC
1155 [2], RFC 1212 [3] and RFC 1215 [4]. The second version,
called SMIv2, is described in RFC 1902 [5], RFC 1903 [6] and RFC
1904 [7].
o Message protocols for transferring management information. The
first version of the SNMP message protocol is called SNMPv1 and
described in RFC 1157 [8]. A second version of the SNMP message
protocol, which is not an Internet standards track protocol, is
called SNMPv2c and described in RFC 1901 [9] and RFC 1906 [10].
The third version of the message protocol is called SNMPv3 and
described in RFC 1906 [10], RFC 2272 [11] and RFC 2274 [12].
o Protocol operations for accessing management information. The
first set of protocol operations and associated PDU formats is
described in RFC 1157 [8]. A second set of protocol operations and
associated PDU formats is described in RFC 1905 [13].
o A set of fundamental applications described in RFC 2273 [14] and
the view-based access control mechanism described in RFC 2275
[15].
C. Kalbfleisch Expires Dec 2002 [Page 2]
INTERNET DRAFT SSPM MIB Jun 2002
Managed objects are accessed via a virtual information store, termed
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
MIB conforming to the SMIv1 can be produced through the appropriate
translations. The resulting translated MIB must be semantically
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.
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED","MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC2119 [16].
3. Overview
This document defines a MIB for the purpose of remotely controlling
synthetic sources (or 'active' probes) and sinks for the purpose of
enhancing remote performance monitoring capabilities within IP
networks and services. Much work within the IETF exists related to
performance monitoring. One interesting aspect of this body of work
is that it does not explicitly define an 'active' probe capability.
An active probe capability is complimentary to existing capabilities,
and this MIB is developed to fill this void. The utility of this
function within the Internet and the relationship of this MIB to
other working group activities is discussed in a framework document
[<draft-cole-sspm-03.txt>].
The rperfman BOF in Adelaide in March of 2000 was held to discuss the
possibility of developing a standard set of synthetic probes for
performance management functions. It was agreed at that time to move
forward with the development of this MIB and that this work would be
sponsored within the RMONMIB WG. For more information on the outcome
of this BOF, refer to the meeting minutes [rperfmanBOF minutes by
Bierman].
The following definitions apply throughout this document:
o 'Performance monitoring' is the act of monitoring traffic for
the purpose of evaluating a statistic of a metric related to the
performance of the system. A performance monitoring system is
comprised of a) traffic generators, b) measurement, c) data
reduction, and d) reporting. The traffic generators may be
natural sources, synthetic sources or intrusive sources.
C. Kalbfleisch Expires Dec 2002 [Page 3]
INTERNET DRAFT SSPM MIB Jun 2002
o A 'synthetic source' is a device or an embedded software program
which generates a data packet (or packets) and injects it (them)
onto the path to a corresponding probe or existing server solely
in support of a performance monitoring function. A synthetic
source may talk intrusively to existing application servers.
The design goals for this MIB are:
o Compliment the overall performance management architecture being
defined within the RMONMIB WG - this MIB is defined within the
context of the appmcapsMIB.
o Extensibility - the MIB should be easily extended to include a
greater set of protocols and applications for performance
monitoring purposes.
o Flexible - it should support both round trip and one way
measurements.
o Security - the control of the source and sink of traffic is
handled by a management application and communication is
recommended via SNMPv3.
This document is organized as follows. The next section discusses
the relationship of this MIB to other MIBs from the RMONMIB and
DISMAN working groups. Then the structure of the MIB is discussed.
Finally, the MIB definitions are given.
4. Relationship to other MIBs
This MIB is designed to be used in conjunction with the RMON MIB
Working Groupss two other MIBs for application performance
measurement: Application Performance Measurement MIB and Application
Performance Measurement Framework Transport Performance Metrics MIB.
These MIBs define reporting capabilities for that framework. The
intent of this MIB is to define a method for injecting packets into
the network utilizing probe capabilities defined in the base MIBs and
measured with the reporting MIBs.
Specifically, this MIB uses the AppLocalIndex as defined in the APM-
MIB to map measurement configuration information to defintion and
reporting structures defined in the APM-MIB.
5. Relationship to Other Work
Much work has already occurred within the IETF which has a direct
bearing on the development of active performance probe definitions.
This body of work is addressed in various working groups over the
C. Kalbfleisch Expires Dec 2002 [Page 4]
INTERNET DRAFT SSPM MIB Jun 2002
years. In this section we focus our attention to the work of a) the
IPPM working group, b) the DISMAN working group, c) the RMON working
group, d) the ApplMIB working group, and e) the RTFM working group.
5.1 IPPM
The IPPM working group has defined in detail a set of performance
metrics, sampling techniques and associated statistics for transport-
level, or connectivity-level, measurements. The IPPM framework
document [22] discusses numerous issues around sampling techniques,
clock accuracy, resolution and skew, wire time versus host time,
error analysis, etc. Much of these are considerations for
Configuration and Implementation Issues discussed below. The IPPM
working group has defined several metrics and their associated
statistics, including
+ a connectivity metric [23]
+ one-way delay metric [24]
+ one-way loss metric [25]
+ round trip delay and loss metrics [26]
+ delay variation metric [27]
+ a streaming media metric [28]
+ a throughput metric [29] and [30], and
+ others are under development.
These (or a subset) could form the basis for a set of active,
connectivity-level, probe types designed for the purpose of
monitoring the quality of transport services. A consideration of
some of these metrics may form a set of work activities and a set of
early deliverables out of a group developing an active probe
capability.
During the early development of the sspmmib drafts, it became
apparent that a one-way measurement protocol was required in order
for the ssmpMib to control. This helped led to the current work with
the IPPM WG on the development of the One-Way Measurement Protocol
(OWDP) [31]. This protocol work includes both the measurement
protocol itself, as well as the development of a seperate control
protocol. This later control protocol is rendundant with the current
work on the ssmpMib, so it appears that the IPPM WG will seperate
their protocol into two seperate drafts, one for the measurement
C. Kalbfleisch Expires Dec 2002 [Page 5]
INTERNET DRAFT SSPM MIB Jun 2002
protocol and one for the control protocol. But this remains to be
finally agreed to in the working group.
5.2 DISMAN
The DISMAN working group is defining a set of 'active' tools for
remote management. Of relevance to this draft are:
+ the pingMIB [32],
+ the DNS Lookup MIB [32],
+ the tracerouteMIB [32],
+ the scriptsMIB [33], and
+ the expressionMIB [34].
The pingMIB and tracerouteMIB define an active probe capability,
primarily for the remote determination of path and path connectivity.
There are some performance related metrics collected from the pingMIB
and one could conceivably use these measurements for the evaluation
of a limited set of performance statistics. But there is a
fundamental difference in determining connectivity versus determining
the quality of that connectivity. However, in the context of
performance monitoring, a fault can be viewed as not performing at
all. Therefore, they should both be monitored with the same probes
to reduce network traffic. This was discussed further in the
Architecture section above.
The DNS Lookup MIB also includes some probe-like capabilities and
performance time measurements for the DNS lookup. This could be used
to suggest details of a related session-level, active probe.
Also mentioned in the Architecture section above, the scriptsMIB
allows a network management application to distribute and manage
scripts to remote devices. Conceivably, these scripts could be
designed to run a set of active probe monitors on remote devices.
5.3 RMON
The RMON working group has developed a extensive, passive monitoring
capability defined in [35] and [36] as well as additional MIB
modules. Initially, the monitors collected statistics at the MAC
layer, but has now been extended to high-layer statistics. Higher-
layer statistics are identified through the definition of a Protocol
Directory [36]. The working group is recently re-chartered and is
now concentrating on, among other items, monitoring at the
C. Kalbfleisch Expires Dec 2002 [Page 6]
INTERNET DRAFT SSPM MIB Jun 2002
application level.
The minutes of the Boston interim meeting in January 2000 are a good
source for information about these ongoing activities in the RMON WG
[37]. A number of individual drafts exist which discuss a number of
interesting areas such as:
+ application typing and relevant metrics [38] and [39]
+ transaction level statistics collection and reporting [40] and
[39]
Within this context (and discussed within the Architecture Section
above), the development of an active traffic source for performance
monitoring fits well within the overall performance monitoring
architecture being defined within the RMON WG.
Indeed, based upon the agreements from the rperfman BOF, it appears
that the development of the ssmpMib will occur within the RMONMIB WG
(see the discussion of the rperfman BOF below).
5.4 ApplMIB
The ApplMIB working group defined a series of MIBs which monitor
various aspects of applications, processes and services.
The System Application MIB [41] describes a basic set of managed
objects for fault, configuration and performance management of
applications from a systems perspective. More specifically, the
managed objects it defines are restricted to information that can be
determined from the system itself and which does not require special
instrumentation within the applications to make the information
available.
The Application MIB [42] complements the System Application MIB,
providing for the management of applications' common attributes which
could not typically be observed without the cooperation of the
software being managed. There are attributes which provide
information on application and communication performance.
The WWW MIB [43] describes a set of objects for managing networked
services in the Internet Community, particularly World Wide Web (WWW)
services. Performance attributes are available for the information
about each WWW service, each type of request, each type of response
and top accessed documents.
In the development of synthetic application-level probes,
consideration should be given to the relationship of the application
C. Kalbfleisch Expires Dec 2002 [Page 7]
INTERNET DRAFT SSPM MIB Jun 2002
MIBs to the measurements being performed through a synthetic
application-level probe. Similar, cross-indexing issues arise within
the context of the RMON monitoring and synthetic application-level
active probes.
5.5 SNMPCONF
The snmpconf working group will create a Best Current Practices
document [44] which outlines the most effective methods for using the
SNMP Framework to accomplish configuration management. The scope of
the work will include recommendations for device specific as well as
network-wide (Policy) configuration. The group is also chartered to
write any MIB modules necessary to facilitate configuration
management, specifically they will write a MIB module which describes
a network entities capabilities and capacities which can be used by
management entities making policy decisions at a network level or
device specific level.
Currently the snmpconf working group is focused on the SNMP
Configuration MIB for policy [45]. For synthetic probes there is
need to have configuration of a) a single probe, b) several probes,
c) source and destination probes and d) intermediate probes. In
addition, it may be necessary to configure any or all of these
combinations simultaneously. It is hoped that the work of snmpconf
will suffice. The scripting language defined by the SNMP
Configuration MIB could allow for active monitoring to be activated
and configured from a policy management script. Further, the results
of active monitoring could become arguments in further policy
decisions. This notion is reflected in the decision flow outlined in
Figure 5 below.
5.6 RTFM
The Realtime Traffic Flow Measurement (RTFM) working group is
concerned with issues relating to traffic flow measurements, usage
reporting for network traffic and Internet accounting. Various
documents exist which describe requirements [46], traffic flow
measurement architectures [47], and a traffic flow MIB [48]. The
work in this group is focused on passive measurements of user
traffic. As such, its work is related to the monitoring work within
the RMON WG. Fundamentally, their attention has not been concerned
with methods of active traffic generation.
5.7 Relationship to Other Work: Summary
In summary, the development of an active traffic generation
capability primarily for the purpose of performance monitoring should
draw upon various activities, both past and present within the IETF.
C. Kalbfleisch Expires Dec 2002 [Page 8]
INTERNET DRAFT SSPM MIB Jun 2002
Redrawing Figure 1 in Figure 5, but now with annotations to the
various work activities briefly touched upon in this section, is a
means to position the development of a traffic generation capability
within the larger context of a performance monitoring system.
+-----------------------------------+
| |
V |
+------------------------------------------+ |
+------| Application [script], [expr], [snmpconf],|---+ |
| | [pmcaps] | | |
| +------------------------------------------+ | |
| | | |
+--------------------------------+ | |
| Synchronization Control | | |
+--------------------------------+ | |
| | | |
V V V |
+----------------+ +----------------------+ +-------------------+ |
| Traffic | |Monitoring Metrics | |Data Reduction | |
| Generation | |Control [rmon],[ippm],| |Control [applmib], | |
| Control [sspm]| | [applmib],[sspm], | |[wwwservmib],[expr]| |
+----------------+ +----------------------+ +-------------------+ |
| ^ | ^ | ^ |
| | | | | | |
V | V | V | |
+------------------+ +-------------------+ +----------------+ |
|Traffic Generation| |Monitoring Metrics | |Data Reduction | |
| Instrumentation| | Instrumentation | +-->| Instrumentation| |
+------------------+ +-------------------+ | +----------------+ |
| | |
| | |
Various levels | | |
and span +--------------| |
| |
| |
V |
Reports ---+
Figure 5: Coverage for an overall performance monitoring system
6. MIB Structure
This section presents the structure of the MIB. The objects are
arranged into the following groups:
C. Kalbfleisch Expires Dec 2002 [Page 9]
INTERNET DRAFT SSPM MIB Jun 2002
o general information
o source configuration
o sink configuration
6.1. general information
This section provides general information about the capabilities of
the probe. Currently this information is related to the resolution of
the probe clock and its source.
6.2. source configuration
The source is configured with a pair of tables. The first,
sspmSourceProfileTable, defines a set of profiles for monitoring.
These profiles are then used by the second table,
sspmSourceControlTable, to instantiate a specific measurement. This
MIB takes an IP centric view of the configuration of the measurement.
6.3. sink configuration
Configures the sink for measurements. If the test is round-trip then
this table is on the same probe as the source configuration. If the
test is one-way then the table is on a different probe. The
sspmSinkInstance is a unique identifer for the entry per probe.
Additional attributes are provided for test type and source of the
test to uniquely identifier entries in the table.
7. Definitions
SSPM-MIB DEFINITIONS ::= BEGIN
IMPORTS
MODULE-IDENTITY, OBJECT-TYPE, mib-2,
Counter32, Integer32, Unsigned32
FROM SNMPv2-SMI
TEXTUAL-CONVENTION, DateAndTime,
TruthValue, RowStatus
FROM SNMPv2-TC
MODULE-COMPLIANCE, OBJECT-GROUP
FROM SNMPv2-CONF
OwnerString
FROM RMON-MIB
InetAddressType, InetAddress
FROM INET-ADDRESS-MIB
InterfaceIndex
C. Kalbfleisch Expires Dec 2002 [Page 10]
INTERNET DRAFT SSPM MIB Jun 2002
FROM IF-MIB
AppLocalIndex
FROM APM-MIB
Utf8String
FROM SYSAPPL-MIB;
sspmMIB MODULE-IDENTITY
LAST-UPDATED "200204231500Z" -- April 23, 2002
ORGANIZATION "IETF RMON MIB working group"
CONTACT-INFO
" Carl W. Kalbfleisch
Postal: NTT/VERIO
8700 Stemmons Freeway
Suite 211
Dallas, TX 75247
US
Tel: +1 972 306-2034
E-mail: cwk@verio.net"
DESCRIPTION
"This SSPM MIB module is applicable to probes
implementing Synthetic Source for Perfomance
Monitoring fucntions."
-- revision history
REVISION "200111071500Z" -- November 07, 2001
DESCRIPTION "Initial version."
REVISION "200202271500Z" -- February 27, 2002
DESCRIPTION "Draft 01. Removed History. Added sspmClockMaxSkew."
REVISION "200204231500Z" -- April 23, 2002
DESCRIPTION "Draft 02. Resolved a number of open issues."
REVISION "200206201500Z" -- June 3, 2002
DESCRIPTION "Draft 03. Restructured sspmSource in two tables."
::= { mib-2 777 }
--
-- Object Identifier Assignements
--
sspmMIBObjects OBJECT IDENTIFIER ::= { sspmMIB 1 }
sspmMIBNotifications OBJECT IDENTIFIER ::= { sspmMIB 2 }
sspmMIBConformance OBJECT IDENTIFIER ::= { sspmMIB 3 }
C. Kalbfleisch Expires Dec 2002 [Page 11]
INTERNET DRAFT SSPM MIB Jun 2002
--
-- Textual Conventions
--
MicroSeconds ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"A unit of time with resolution of MicroSeconds."
SYNTAX Unsigned32
ClockSource ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"An indication of the source of the clock as defined by the
NTP [49] definition of stratum:
Stratum (sys.stratum, peer.stratum, pkt.stratum): This is an integer
indicating the stratum of the local clock, with values defined as
follows:
0, unspecified
1, primary reference (e.g.,, calibrated atomic clock,, radio clock)
2-255, secondary reference (via NTP)"
SYNTAX INTEGER (0..255)
--
-- sspmGeneral
--
sspmGeneral OBJECT IDENTIFIER ::= { sspmMIBObjects 1 }
sspmClockResolution OBJECT-TYPE
SYNTAX MicroSeconds
MAX-ACCESS read-only
STATUS current
-- UNITS Microseconds
DESCRIPTION
"A read only variable indicating the resolution
of the measurements possible by this device."
::= { sspmGeneral 1 }
sspmClockMaxSkew OBJECT-TYPE
SYNTAX Integer32 (1..65535)
MAX-ACCESS read-only
STATUS current
-- UNITS Seconds
DESCRIPTION
"A read only variable indicating the maximum offset
C. Kalbfleisch Expires Dec 2002 [Page 12]
INTERNET DRAFT SSPM MIB Jun 2002
error due to skew of the local clock over the
time interval 86400 seconds, in seconds."
::= { sspmGeneral 2 }
sspmClockSource OBJECT-TYPE
SYNTAX ClockSource
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"A read only variable indicating the source of the clock.
This is provided to allow a user to determine how accurate
the timing mechanism is compared with other devices. This
is needed for the co-ordination of time values
between probes for one-way measurements."
::= { sspmGeneral 3 }
sspmMinFrequency OBJECT-TYPE
SYNTAX MicroSeconds
MAX-ACCESS read-only
-- units MicroSeconds
STATUS current
DESCRIPTION
"A read-only variable which indicates the devices
capability for the minimum supported
sspmSourceFrequency. If sspmSourceFrequency is
set to a value lower than the value reported
by this attribute, then the set of sspmSourceFrequency
will fail with an inconsistent value error."
::= { sspmGeneral 4 }
--
-- sspmCapabilities
--
-- Describes the capabilities of the SSPM device.
--
sspmCapabilitiesTable OBJECT-TYPE
SYNTAX SEQUENCE OF SspmCapabilitiesEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The table of SSPM capabilities."
::= { sspmGeneral 3 }
sspmCapabilitiesEntry OBJECT-TYPE
SYNTAX SspmCapabilitiesEntry
MAX-ACCESS not-accessible
STATUS current
C. Kalbfleisch Expires Dec 2002 [Page 13]
INTERNET DRAFT SSPM MIB Jun 2002
DESCRIPTION
"Deatils about a particular SSPM capabilitiy."
INDEX { sspmCapabilitiesInstance }
::= { sspmCapabilitiesTable 1 }
SspmCapabilitiesEntry ::= SEQUENCE {
sspmCapabilitiesInstance AppLocalIndex,
sspmCapabilitiesIsSupported TruthValue
}
sspmCapabilitiesInstance OBJECT-TYPE
SYNTAX AppLocalIndex
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"An arbitrary index."
::= { sspmCapabilitiesEntry 1 }
sspmCapabilitiesIsSupported OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Indicates whether SSPM configuration of the corresponding
AppLocalIndex is supported by this device. Generally entries
in this table are only made by the device when the configuration
of the measurement is available."
::= { sspmCapabilitiesEntry 2 }
--
-- sspmSource
--
-- Contains the details of the source of the
-- Synthetic Sources for Performance Monitoring algorithms.
-- This information is split into two tables. The first defines
-- profiles which can be applied to specific sources in the
-- control table.
--
sspmSource OBJECT IDENTIFIER ::= { sspmMIBObjects 2 }
--
-- sspmSourceProfileTable
-- Define template profiles for measurements.
--
sspmSourceProfileTable OBJECT-TYPE
SYNTAX SEQUENCE OF SspmSourceProfileEntry
MAX-ACCESS not-accessible
STATUS current
C. Kalbfleisch Expires Dec 2002 [Page 14]
INTERNET DRAFT SSPM MIB Jun 2002
DESCRIPTION
"The table of SSPM source profiles configured."
::= { sspmSource 1 }
sspmSourceProfileEntry OBJECT-TYPE
SYNTAX SspmSourceProfileEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Deatils about a particular SSPM Source Profile
configuration. Entries must exist in this table
in order to be referenced by rows in the
sspmSourceControlTable."
INDEX { sspmSourceProfileInstance }
::= { sspmSourceProfileTable 1 }
SspmSourceProfileEntry ::= SEQUENCE {
sspmSourceProfileInstance Integer32,
sspmSourceProfileType AppLocalIndex,
sspmSourceProfilePacketSize Unsigned32,
sspmSourceProfilePacketFillType INTEGER,
sspmSourceProfilePacketFillValue OCTET STRING,
sspmSourceProfileTOS Integer32,
sspmSourceProfileFlowLabel Integer32,
sspmSourceProfileSrcRouteFill OCTET STRING,
sspmSourceProfileSourceSrcRouteLength Integer32,
sspmSourceProfileTTL Integer32,
sspmSourceProfileNoFrag INTEGER,
sspmSourceProfile8021Tagging Integer32,
sspmSourceProfileUsername Utf8String,
sspmSourceProfilePassword Utf8String,
sspmSourceProfileParameter Utf8String,
sspmSourceProfileOwner OwnerString,
sspmSourceProfileStatus RowStatus
}
sspmSourceProfileInstance OBJECT-TYPE
SYNTAX Integer32 (1..65535)
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"An arbitrary index."
::= { sspmSourceProfileEntry 1 }
sspmSourceProfileType OBJECT-TYPE
SYNTAX AppLocalIndex
MAX-ACCESS read-create
STATUS current
C. Kalbfleisch Expires Dec 2002 [Page 15]
INTERNET DRAFT SSPM MIB Jun 2002
DESCRIPTION
"The AppLocalIndex value which uniquely identifies the
measurement per the APM-MIB. In order to create a row
in this table there must be a corresponding
sspmCapabilitiesIsSupported entry set to true."
::= { sspmSourceProfileEntry 2}
sspmSourceProfilePacketSize OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The size of packet to be transmitted in bytes.
If the size is set smaller than the minimum allowed
packet size or greater than the allowed maximum
packet size then the set should fail with
invalid value."
::= { sspmSourceProfileEntry 3 }
sspmSourceProfilePacketFillType OBJECT-TYPE
SYNTAX INTEGER {
random (1),
pattern (2),
url(3)
}
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Indicates how the packet is filled.
'random' indicates that the packet contains random
data patterns. This is probe and implementation
dependent.
'pattern' indicates that the pattern defined in the
sspmSourcePacketFillValue attribute is used to
fill the packet.
'url' indicates that the value of sspmSourcePacketFillValue
should contain a URL. The contents of the document
at that URL are retrieved when sspmSourceStatus becomes
active and utilized in the packet. If the attempt to
access that URL fails then the row status is set to
'notReady' and the set should fail with inconsistentValue. "
::= { sspmSourceProfileEntry 4 }
sspmSourceProfilePacketFillValue OBJECT-TYPE
SYNTAX OCTET STRING (SIZE(0..255))
C. Kalbfleisch Expires Dec 2002 [Page 16]
INTERNET DRAFT SSPM MIB Jun 2002
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The string value to fill the packet with. If
sspmSourcePacketFillType is set to 'pattern' then this
pattern is repeated until the packet is
sspmSourcePacketSize in bytes. Note that if
length of the octet string specified for this
value does not divide evenly into the packet
size then an incomplete last copy of this data
may be copied into the packet. If the value of
sspmSourcePacketFillType is set to 'random' then
this attribute is unused. If the value of the
sspmSourcePacketFillType is set to 'url' then
the URL specified in this attribute is retrieved
and used by the probe."
::= { sspmSourceProfileEntry 5 }
sspmSourceProfileTOS OBJECT-TYPE
SYNTAX Integer32 (0..255)
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"(yes, the whole 8 bit field) Represent the TOS field
in the IP packet header."
::= { sspmSourceProfileEntry 6 }
sspmSourceProfileFlowLabel OBJECT-TYPE
SYNTAX Integer32 (0..1048575) -- 20-bit range (0 to 0xfffff)
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This object is used to specify the Flow Label in a IPv6
packet (RFC 2460) to force special handling by the IPv6 routers for
non-default quality-of-service.
This object is meaningful only when sspmSourceDestAddressType is
ipv6(2). The value of this object defaults to zero if not set."
DEFVAL { 0 }
::= { sspmSourceProfileEntry 7 }
sspmSourceProfileSrcRouteFill OBJECT-TYPE
SYNTAX OCTET STRING (SIZE(7..39))
MAX-ACCESS read-create
STATUS current
DESCRIPTION
C. Kalbfleisch Expires Dec 2002 [Page 17]
INTERNET DRAFT SSPM MIB Jun 2002
"In the event that the test should run over a
specific route. Intent is to force the route.
Series of IP addresses along the path that would be
put into the source route option in the IP header.
Provide reference to IP Header RFC."
::= { sspmSourceProfileEntry 8 }
sspmSourceProfileSourceSrcRouteLength OBJECT-TYPE
SYNTAX Integer32(7..39)
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"In the event that the test should run over a
specific route. Intent is to force the route.
This attribute specifies the length of data
to be copied from the sspmSourceSrcRouteFill."
::= { sspmSourceProfileEntry 9 }
sspmSourceProfileTTL OBJECT-TYPE
SYNTAX Integer32(0..255)
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"If non-zero specifies the value to place into
the TTL field on transmission."
::= { sspmSourceProfileEntry 10 }
sspmSourceProfileNoFrag OBJECT-TYPE
SYNTAX INTEGER {
fragment(1),
noFragment(2)
}
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"'noFragment' indicates that the Don't Fragment Bit should be
set on transmission"
::= { sspmSourceProfileEntry 11 }
sspmSourceProfile8021Tagging OBJECT-TYPE
SYNTAX Integer32 (0..65535)
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"802.1 queue tagging used in bridge environment.
16 bit string. 12 bit vlan, 3 bits priority, 1
C. Kalbfleisch Expires Dec 2002 [Page 18]
INTERNET DRAFT SSPM MIB Jun 2002
bit may be unused."
::= { sspmSourceProfileEntry 12 }
sspmSourceProfileUsername OBJECT-TYPE
SYNTAX Utf8String
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"An optional username used by the application protocol."
::= { sspmSourceProfileEntry 13 }
sspmSourceProfilePassword OBJECT-TYPE
SYNTAX Utf8String
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"An optional password used by the application protocol."
::= { sspmSourceProfileEntry 14 }
sspmSourceProfileParameter OBJECT-TYPE
SYNTAX Utf8String
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"An optional parameter used by the application protocol.
For DNS this would be the hostname or IP. For HTTP,
this would be the URL. For nntp this would be the
news group. For TCP this would be the port number.
For SMTP this would be the recipient (and could
assume the message is predefined)."
::= { sspmSourceProfileEntry 15 }
sspmSourceProfileOwner OBJECT-TYPE
SYNTAX OwnerString
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Name of the mgmt station / application who set up the profile."
::= { sspmSourceProfileEntry 16 }
sspmSourceProfileStatus OBJECT-TYPE
SYNTAX RowStatus
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Status of this profile."
::= { sspmSourceProfileEntry 17 }
C. Kalbfleisch Expires Dec 2002 [Page 19]
INTERNET DRAFT SSPM MIB Jun 2002
--
-- sspmSourceControlTable
-- Defines specific measurement instatnces based on template
-- profiles in the sspmSourceProfileTable which must be
-- pre-configured.
--
sspmSourceControlTable OBJECT-TYPE
SYNTAX SEQUENCE OF SspmSourceControlEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The table of SSPM measurements configured."
::= { sspmSource 2 }
sspmSourceControlEntry OBJECT-TYPE
SYNTAX SspmSourceControlEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Deatils about a particular SSPM configuration."
INDEX { sspmSourceControlInstance }
::= { sspmSourceControlTable 1 }
SspmSourceControlEntry ::= SEQUENCE {
sspmSourceControlInstance Integer32,
sspmSourceControlProfile Integer32,
sspmSourceControlSrc InterfaceIndex,
sspmSourceControlDestAddressType InetAddressType,
sspmSourceControlDestAddress InetAddress,
sspmSourceControlEnabled TruthValue,
sspmSourceControlTimeOut MicroSeconds,
sspmSourceControlSamplingDistribution INTEGER,
sspmSourceControlFrequency MicroSeconds,
sspmSourceControlFirstSequenceNumber Integer32,
sspmSourceControlLastSequenceNumber Integer32,
sspmSourceControlOwner OwnerString,
sspmSourceControlStatus RowStatus
}
sspmSourceControlInstance OBJECT-TYPE
SYNTAX Integer32 (1..65535)
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"An arbitrary index."
::= { sspmSourceControlEntry 1 }
C. Kalbfleisch Expires Dec 2002 [Page 20]
INTERNET DRAFT SSPM MIB Jun 2002
sspmSourceControlProfile OBJECT-TYPE
SYNTAX Integer32 (1..65535)
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"A pointer to the profile (sspmSourceProfileEntry) which this
control entry uses to define the test being performed."
::= { sspmSourceControlEntry 2 }
sspmSourceControlSrc OBJECT-TYPE
SYNTAX InterfaceIndex
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"ifIndex where the packet should originate from the
probe (if it matters). Zero value indicates it does
not matter and the device decides."
::= { sspmSourceControlEntry 3 }
sspmSourceControlDestAddressType OBJECT-TYPE
SYNTAX InetAddressType
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The type of Internet address by which the destination
is accessed."
::= { sspmSourceControlEntry 4 }
sspmSourceControlDestAddress OBJECT-TYPE
SYNTAX InetAddress
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The Internet address for the destination."
::= { sspmSourceControlEntry 5 }
sspmSourceControlEnabled OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"When set to Yes this test is enabled. When set to
No, it is disabled."
::= { sspmSourceControlEntry 6 }
sspmSourceControlTimeOut OBJECT-TYPE
SYNTAX MicroSeconds
MAX-ACCESS read-create
C. Kalbfleisch Expires Dec 2002 [Page 21]
INTERNET DRAFT SSPM MIB Jun 2002
STATUS current
DESCRIPTION
"Timeout value for the measurement response. If no
response is received in the time specified then
the test fails."
::= { sspmSourceControlEntry 7 }
sspmSourceControlSamplingDistribution OBJECT-TYPE
SYNTAX INTEGER {
deterministic(1),
poisson(2)
}
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"When this attbute is set to 'deterministic', then
packets are generated at with a fixed interpacket
injection time specified by sspmSourceFrequency.
When this attribute is set to 'poisson' then packets
are generated with interpacket injection times sampled
from a exponential distribution with the single
distributional parameter determined by the inverse
frequency)."
::= { sspmSourceControlEntry 8 }
sspmSourceControlFrequency OBJECT-TYPE
SYNTAX MicroSeconds
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The inverse of this value is the rate at which packets
are generated. Refer to sspmSourceSamplingDistribution.
If the value set is less than the value of
sspmMinFrequency then the set will fail with invalid
value error."
::= { sspmSourceControlEntry 9 }
sspmSourceControlFirstSequenceNumber OBJECT-TYPE
SYNTAX Integer32
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The first sequence number of packets to be transmitted."
::= { sspmSourceControlEntry 10 }
sspmSourceControlLastSequenceNumber OBJECT-TYPE
SYNTAX Integer32
C. Kalbfleisch Expires Dec 2002 [Page 22]
INTERNET DRAFT SSPM MIB Jun 2002
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The last sequence number transmitted. This value is updated
by the agent after packet generation."
::= { sspmSourceControlEntry 11 }
sspmSourceControlOwner OBJECT-TYPE
SYNTAX OwnerString
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Name of the mgmt station / application who set up the test."
::= { sspmSourceControlEntry 12 }
sspmSourceControlStatus OBJECT-TYPE
SYNTAX RowStatus
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Status of this test."
::= { sspmSourceControlEntry 13 }
--
-- sspmSinkTable
--
-- Contains attributes for configuration of Synthetic
-- Sources for Performance Monitoring sinks. IE
-- sinks for receipt of one-way delay measurements.
--
sspmSink OBJECT IDENTIFIER ::= { sspmMIBObjects 5 }
sspmSinkTable OBJECT-TYPE
SYNTAX SEQUENCE OF SspmSinkEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A table configuring the sink for measurements."
::= { sspmSink 1 }
sspmSinkEntry OBJECT-TYPE
SYNTAX SspmSinkEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The details of a particular sink entry. If the measurement
is a round trip type then the sink entry will be on the same
C. Kalbfleisch Expires Dec 2002 [Page 23]
INTERNET DRAFT SSPM MIB Jun 2002
probe as the corresponding sspmSourceEntry. If the measurement
is a one way type then the sink entry will be on a different
probe."
INDEX { sspmSinkInstance }
::= { sspmSinkTable 1}
SspmSinkEntry ::= SEQUENCE {
sspmSinkInstance Integer32,
sspmSinkType AppLocalIndex,
sspmSinkSourceAddressType InetAddressType,
sspmSinkSourceAddress InetAddress,
sspmSinkExpectationRate MicroSeconds,
sspmSinkEnable TruthValue,
sspmSinkFirstSequenceNumber Integer32,
sspmSinkLastSequenceNumber Integer32,
sspmSinkLastSequenceInvalid Counter32,
sspmSinkStatus RowStatus
}
sspmSinkInstance OBJECT-TYPE
SYNTAX Integer32 (1..65535)
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"An arbitrary index. When the measurement is for a round trip
measurement then this table entry is on the same probe as the
corresponding sspmSourceEntry and the value of this attribute
should correspond to the value of sspmSourceInstance. Management
applications configuring sinks for one way measurements could
define some scheme whereby the sspmSinkInstance is unique
accross all probes. Note that the unique key to this entry is
also constructed with sspmSinkType, sspmSinkSourceAddressType
and sspmSinkSourceAddress. Those other attributes are not included
in the index to make the implementation simpiler. But, uniqueness
is still needed to receive all of the packets."
::= { sspmSinkEntry 1 }
sspmSinkType OBJECT-TYPE
SYNTAX AppLocalIndex
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The AppLocalIndex value which uniquely identifies the
measurement per the APM-MIB. In order to create a row
in this table there must be a corresponding
sspmCapabilitiesIsSupported entry set to true."
::= { sspmSinkEntry 2}
C. Kalbfleisch Expires Dec 2002 [Page 24]
INTERNET DRAFT SSPM MIB Jun 2002
sspmSinkSourceAddressType OBJECT-TYPE
SYNTAX InetAddressType
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The type of Internet address of the source."
::= { sspmSinkEntry 3 }
sspmSinkSourceAddress OBJECT-TYPE
SYNTAX InetAddress
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The Internet address of the source."
::= { sspmSinkEntry 4 }
sspmSinkExpectationRate OBJECT-TYPE
SYNTAX MicroSeconds
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The expected rate of packets to arrive."
::= { sspmSinkEntry 5 }
sspmSinkEnable OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Indicates if the sink is enabled or not."
::= { sspmSinkEntry 6 }
sspmSinkFirstSequenceNumber OBJECT-TYPE
SYNTAX Integer32
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The expected first sequence number of packets."
::= { sspmSinkEntry 7 }
sspmSinkLastSequenceNumber OBJECT-TYPE
SYNTAX Integer32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The last sequence number received."
::= { sspmSinkEntry 8 }
C. Kalbfleisch Expires Dec 2002 [Page 25]
INTERNET DRAFT SSPM MIB Jun 2002
sspmSinkLastSequenceInvalid OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of packets that arrived where their
sequence number was not one plus the value of
sspmSinkLastSequenceNumber."
::= { sspmSinkEntry 9 }
sspmSinkStatus OBJECT-TYPE
SYNTAX RowStatus
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Status of this conceptual row."
::= { sspmSinkEntry 10 }
--
-- Notifications
--
--
-- Conformance information
--
sspmCompliances OBJECT IDENTIFIER ::= { sspmMIBConformance 1 }
sspmGroups OBJECT IDENTIFIER ::= { sspmMIBConformance 2 }
-- Compliance Statements
sspmGeneralCompliance MODULE-COMPLIANCE
STATUS current
DESCRIPTION
"A general compliance which allows all things to be optional."
MODULE -- this module
GROUP sspmGeneralGroup
DESCRIPTION
"The SSPM General Group is mandatory."
GROUP sspmSourceGroup
DESCRIPTION
"The SSPM Source Group is optional. However, if either of
the sspmLinkLayerExtentionGroup or sspmApplLayerExtentionGroup
groups are implemented, then this group becomes mandatory."
GROUP sspmSinkGroup
C. Kalbfleisch Expires Dec 2002 [Page 26]
INTERNET DRAFT SSPM MIB Jun 2002
DESCRIPTION
"The SSPM Sink Group is optional."
GROUP sspmUserPassGroup
DESCRIPTION
"The SSPM User Pass Group is optional."
::= { sspmCompliances 1 }
--
-- SSPM Source Compliance
--
sspmSourceFullCompliance MODULE-COMPLIANCE
STATUS current
DESCRIPTION
"A source compliance. Use this compliance when implementing a
source only device. This is useful for implementing devices which
probe other devices for intrusive application monitoring. It is
also useful for implementing the source of one way tests used with
a sink only devices."
MODULE -- this module
GROUP sspmGeneralGroup
DESCRIPTION
"The SSPM General Group is mandatory."
GROUP sspmSourceGroup
DESCRIPTION
"The SSPM Source Group is mandatory."
GROUP sspmUserPassGroup
DESCRIPTION
"The SSPM User Pass Group is optional."
::= { sspmCompliances 2 }
--
-- SSPM Sink Compliance
--
sspmSinkCompliance MODULE-COMPLIANCE
STATUS current
DESCRIPTION
"A sink-only compliance. Use this compliance when implementing a
sink-only device. This is useful for devices to receive one way
measurements."
MODULE -- this module
GROUP sspmGeneralGroup
DESCRIPTION
C. Kalbfleisch Expires Dec 2002 [Page 27]
INTERNET DRAFT SSPM MIB Jun 2002
"The SSPM General Group is mandatory."
GROUP sspmSinkGroup
DESCRIPTION
"The SSPM Sink Group is mandatory."
::= { sspmCompliances 3 }
--
-- Groups
--
sspmGeneralGroup OBJECT-GROUP
OBJECTS {
sspmClockResolution,
sspmClockMaxSkew,
sspmClockSource,
sspmCapabilitiesInstance,
sspmCapabilitiesIsSupported
}
STATUS current
DESCRIPTION
""
::= { sspmGroups 1 }
sspmSourceGroup OBJECT-GROUP
OBJECTS {
sspmSourceProfileInstance,
sspmSourceProfileType,
sspmSourceProfilePacketSize,
sspmSourceProfilePacketFillType,
sspmSourceProfilePacketFillValue,
sspmSourceProfileTOS,
sspmSourceProfileFlowLabel,
sspmSourceProfileSrcRouteFill,
sspmSourceProfileSourceSrcRouteLength,
sspmSourceProfileTTL,
sspmSourceProfileNoFrag,
sspmSourceProfile8021Tagging,
sspmSourceProfileUsername,
sspmSourceProfilePassword,
sspmSourceProfileParameter,
sspmSourceProfileOwner,
sspmSourceProfileStatus,
sspmSourceControlInstance,
sspmSourceControlProfile,
sspmSourceControlSrc,
sspmSourceControlDestAddressType,
C. Kalbfleisch Expires Dec 2002 [Page 28]
INTERNET DRAFT SSPM MIB Jun 2002
sspmSourceControlDestAddress,
sspmSourceControlEnabled,
sspmSourceControlTimeOut,
sspmSourceControlSamplingDistribution,
sspmSourceControlFrequency,
sspmSourceControlFirstSequenceNumber,
sspmSourceControlLastSequenceNumber,
sspmSourceControlOwner,
sspmSourceControlStatus
}
STATUS current
DESCRIPTION
""
::= { sspmGroups 2 }
sspmUserPassGroup OBJECT-GROUP
OBJECTS {
sspmSourceProfileUsername,
sspmSourceProfilePassword
}
STATUS current
DESCRIPTION
""
::= { sspmGroups 3 }
sspmSinkGroup OBJECT-GROUP
OBJECTS {
sspmSinkInstance,
sspmSinkType,
sspmSinkSourceAddressType,
sspmSinkSourceAddress,
sspmSinkExpectationRate,
sspmSinkEnable,
sspmSinkFirstSequenceNumber,
sspmSinkLastSequenceNumber,
sspmSinkLastSequenceInvalid,
sspmSinkStatus
}
STATUS current
DESCRIPTION
""
::= { sspmGroups 4 }
END
8. References
[1] Harrington, D., Presuhn, R., and B. Wijnen, An Architecture for
C. Kalbfleisch Expires Dec 2002 [Page 29]
INTERNET DRAFT SSPM MIB Jun 2002
Describing SNMP Management Frameworks, RFC 2571, April 1999.
[2] Rose, M., and K. McCloghrie, Structure and Identification of
Management Information for TCP/IP-based Internets, STD 16, RFC 1155,
May 1990.
[3] Rose, M., and K. McCloghrie, Concise MIB Definitions, STD 16, RFC
1212, March 1991.
[4] M. Rose, A Convention for Defining Traps for use with the SNMP,
RFC 1215, March 1991.
[5] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose,
M., and S. Waldbusser, Structure of Management Information Version 2
(SMIv2), STD 58, RFC 2578, April 1999.
[6] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose,
M., and S. Waldbusser, Textual Conventions for SMIv2, STD 58, RFC
2579, April 1999.
[7] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose,
M., and S. Waldbusser, Conformance Statements for SMIv2, STD 58, RFC
2580, April 1999.
[8] Case, J., Fedor, M., Schoffstall, M., and J. Davin, Simple
Network Management Protocol, STD 15, RFC 1157, May 1990.
[9] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser,
Introduction to Community-based SNMPv2, RFC 1901, January 1996.
[10] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, Transport
Mappings for Version 2 of the Simple Network Management Protocol
(SNMPv2), RFC 1906, January 1996.
[11] Case, J., Harrington D., Presuhn R., and B. Wijnen, Message
Processing and Dispatching for the Simple Network Management Protocol
(SNMP), RFC 2572, April 1999.
[12] Blumenthal, U., and B. Wijnen, User-based Security Model (USM)
for version 3 of the Simple Network Management Protocol (SNMPv3), RFC
2574, April 1999.
[13] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, Protocol
Operations for Version 2 of the Simple Network Management Protocol
(SNMPv2), RFC 1905, January 1996.
[14] Levi, D., Meyer, P., and B. Stewart, SNMPv3 Applications, RFC
2573, April 1999.
C. Kalbfleisch Expires Dec 2002 [Page 30]
INTERNET DRAFT SSPM MIB Jun 2002
[15] Wijnen, B., Presuhn, R., and K. McCloghrie, View-based Access
Control Model (VACM) for the Simple Network Management Protocol
(SNMP), RFC 2575, April 1999.
[16] Case, J., Mundy, R., Partain, D., and B. Stewart, Introduction
to Version 3 of the Internet-standard Network Management Framework,
RFC 2570, April 1999.
[17] Daniele, M., Haberman, B., Routhier, S., and J. Schoenwaeler,
Textual Conventions for Internet Network Addresses, RFC 2851, June
2000.
[18] McCloghrie, K. and F. Kastenholz, The Interfaces Group MIB, RFC
2863, June 2000.
[19] R.G. Cole, C. Kalbfleisch, D. Romascanu, A Framework for Active
Probes for Performance Monitoring, <draft-cole-sspm-03.txt>.
[20] S. Waldbusser, Application Performance Measurement MIB, <draft-
ietf-rmonmib-apm-mib-05.txt>.
[21] R. Dietz, R.G.Cole, Application Performance Measurement
Framework Transport Performance Metrics MIB, <draft-ietf-rmonmib-tpm-
mib-00.txt>.
[22] Paxson, V., Almes, G., Mahdavi, J. and M. Mathis, "Framework for
IP Performance Metrics", RFC 2330, May 1998.
[23] Mahdavi, J. and V. Paxson, "IPPM metrics for Measuring
Connectivity", RFC 2678, September 1999.
[24] Almes, G., Kalidindi, S. and M. Zekauskas, "A One-way Delay
Metric for IPPM", RFC 2679, September 1999.
[25] Almes, G., Kalidindi, S. and M. Zekauskas, "A One-Way Packet
Loss Metric for IPPM", Internet Draft, <draft-ietf-ippm-loss-07.txt>,
May 1999.
[26] Almes, G., Kalidindi, S. and M. Zekauskas, "A Round-Trip Delay
Metric for IPPM", RFC 2681, September 1999.
[27] Demichelis, C. and P. Chimento, "IP Packet Delay Variation
Metric for IPPM", Internet Draft, <draft-ietf-ippm-ipdv-06.txt.,
October 1999.
[28] Raisanen, V. and G. Grotefeld, "Network Performance Measurement
for Periodic Streams", Internet Draft, <draft-ietf-ippm-
npmps-00.txt>, March 2000.
C. Kalbfleisch Expires Dec 2002 [Page 31]
INTERNET DRAFT SSPM MIB Jun 2002
[29] Mathis, M. and M. Allman, "Empirical Bulk Transfer Capacity",
Internet Draft, <draft-ietf-ippm-btc-framework-02.txt>, Octobet 1999.
[30] Mathis, M., "TReno Bulk transfer Capacity", Internet Draft,
<draft-ietf-ippm-treno-btc-03.txt>, February 1999.
[31] Shalunov, S., Teitelbaum, B. and M. Zekauskas, "A One-Way Delay
Protocol for IP Performance Measurements", <draft-ietf-ippm-
owdp-02.txt>, December 2000.
[32] White, K., "Definitions of Managed Objects for Remote Ping,
Traceroute, and Lookup Operations", RFC 2925, September 2000.
[33] Levi, D. and J. Schoenwaelder, "Definitions of Managed Objects
for the Delegation of Management Scripts", RFC 2592, May 1999.
[34] Stewart, B. and R. Kavasseri, "Distributed Management Expression
MIB", RFC 2982, October 2000.
[35] Waldbusser, S., "Remote Network Monitoring Management
Information Base", RFC 1757, February 1995.
[36] Waldbusser, S., "Remote Network Monitoring Management
Information Base Version 2 using SMIv2", RFC 2021, January 1997.
[37] Meeting minutes from the interim meeting of the RMON working
group on January 11 and 12, 2000 in Boston, MA.
[38] Waldbusser, S., "Application performance measurement MIB",
<draft-ietf-rmonmib-apm-mib-00.txt>, May 2000.
[39] Warth, A. and J. McQuaid, "Application Response Time (ART) MIB",
Internet Draft, <draft-warth-art-mib-01.txt>, October 1999.
[40] Dietz, R. "Application Performance Measurement Framework
Transport Performance Metrics MIB", Internet Draft, <draft-ietf-
rmonmib-tpm-mib-00.txt>, May 2000.
[41] Krupczak, C. and J. Saperia, "Definitions of System-Level
Managed Objects for Applications", RFC 2287, February 1998.
[42] Kalbfleisch, C., Krupczak, C., Presuhn, R. and J. Saperia,
"Application Management MIB", RFC 2564, May 1999.
[43] Hazewinkel, H., Kalbfleisch, C., and J. Schoenwaelder,
"Definitions of Managed Objects for WWW Services", RFC 2594, May
1999.
C. Kalbfleisch Expires Dec 2002 [Page 32]
INTERNET DRAFT SSPM MIB Jun 2002
[44] MacFadden, M., and J. Saperia, "Configuring Networks and Devices
with SNMP", Internet Draft, ,draft-ietf-snmpconf-bcp-01.txt., May
2000.
[45] Waldbusser, S., Saperia, J., and T. Hongal, "Policy Based
Management MIB", Internet Draft, <draft-ietf-snmpconf-pm-01.txt>, May
2000.
[46] Mills, C., Hirsch, G., and Ruth, G. "Internet Accounting
Background", RFC 1272, November 1991.
[47] Browlee, N., Mills, C. and Ruth, G. "Traffic Flow Measurement:
Architecture", RFC 2063, January 1997.
[48] Brownlee, N. "Traffic Flow Measurement: Meter MIB", RFC 2064,
January 1997.
[49] Mills, D. "Network Time Protocol (Version 3)", RFC-1305, March
1992
9. Intellectual Property
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.
10. Security Considerations
There are a number of management objects defined in this MIB that
have a MAX-ACCESS clause of read-write and/or read-create. Such
objects may be considered sensitive or vulnerable in some network
environments. The support for SET operations in a non-secure
C. Kalbfleisch Expires Dec 2002 [Page 33]
INTERNET DRAFT SSPM MIB Jun 2002
environment without proper protection can have a negative effect on
network operations.
The nature of the MIB is that it defines objects to allow packets to
be injected into the network for the purpose of measuring some
performance characteristics. There are some attributes which allow
specifically configuring various fields in Link and IP layer packets.
There are some attributes which configure username and password
information for some application level protocols. Access to these
attributes may provide unauthorized use of resources.
It is thus important to control even GET access to these objects and
possibly to even encrypt the values of these object when sending them
over the network via SNMP. Not all versions of SNMP provide features
for such a secure environment.
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
control as to who on the secure network is allowed to access and
GET/SET (read/change/create/delete) the objects in this MIB.
It is RECOMMENDED that the implementers consider the security
features as provided by the SNMPv3 framework. Specifically, the use
of the User-based Security Model RFC 2274 [12] and the View-based
Access Control Model RFC 2275 [15] is RECOMMENDED.
It is then a customer/user responsibility to ensure that the SNMP
entity giving access to an instance of this MIB, is properly
configured to give access to the objects only to those principals
(users) that have legitimate rights to indeed GET or SET
(change/create/delete) them.
11. Acknowledgments
This document was produced by the IETF Remote Network Monitoring
Working Group. The editors gratefully acknowledge the comments of the
following individuals:
Andy Bierman, Lester D'Souza, Jim McQuaid, Steven Waldbusser
11. Author's Addresses
Carl W. Kalbfleisch
NTT/VERIO
8700 Stemmons Freeway, Suite 211
Dallas, TX 75247
C. Kalbfleisch Expires Dec 2002 [Page 34]
INTERNET DRAFT SSPM MIB Jun 2002
USA
Tel: +1 972-906-2034
Email: cwk@verio.net
Robert G. Cole
AT&T Labs
Network Design and Performance Analysis Department
330 Saint John Street, 2nd Floor
Havre de Grace, MD 21078
Phone: +1 410-939-8732
Fax: +1 410-939-8732
Email: rgcole@att.com
Dan Romascanu
Avaya Communication
Atidim Technology Park, Bldg. #3
Tel Aviv, 61131
Israel
Tel: +972-3-645-8414
Email: dromasca@avaya.com
A. Full Copyright Statement
This document and translations of it may be copied and furnished to
others, and derivative works that comment on or otherwise explain it
or assist in its implementation may be prepared, copied, published
and distributed, in whole or in part, without restriction of any
kind, provided that the above copyright notice and this paragraph are
included on all such copies and derivative works. However, this
document itself may not be modified in any way, such as by removing
the copyright notice or references to the Internet Society or other
Internet organizations, except as needed for the purpose of
developing Internet standards in which case the procedures for
copyrights defined in the Internet Standards process must be
followed, or as required to translate it into languages other than
English.
The limited permissions granted above are perpetual and will not be
revoked by the Internet Society or its successors or assigns.
This document and the information contained herein is provided on an
"AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING
BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION
HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
C. Kalbfleisch Expires Dec 2002 [Page 35]
INTERNET DRAFT SSPM MIB Jun 2002
12. Issues
This section will ultimately be removed from the document. It
captures a list of open issues that need to be resolved as this
document is discussed. If someone feels strongly about any of the
open issues, please send a proposal to the rmon MIB mailing list.
Open Issues
o Do we need sspmSourceControlEnabled?
Resolved Issues
o Need to restructure tables to allow reuse per Lester. Issue 7.
Resolved in draft 3.
o Should we allow sspmSourceFrequency to be specified in
MicroSeconds? Does this make the system suseptible to DOS
attacks? What is a reasonable bound? - Issue 1. Added
sspmMinFrequency
o What should be the max and min allowed values for
sspmSourcePacketSize? Should the size only be for the application
payload? Maybe not since there are non-application based payloads.
But what if the min size is smaller than the min packet allowed by
the network? Should we handle that case? issue 12 - discuss on
list. Added clarifying text.
o Combined extention tables
o User/Pass are optional in conformance statement
o Should sspmClockSource define various levels of ntp resolution?
issue 8 - no, but apm or tpm need to define TC. Defined TC.
o What should happen if the URL specified in
sspmSourcePacketFillValue can not be retrieved? The agent could
fetch the URL once when the row status is set to active state.
Then the row status could change notReady if the fetch fails.
issue 11 - clarify text as written here.
o Should "random" in the sspmSourceSamplingDistribution be renamed
to "exponential"? Issue 2. REnamed to Poisson. Clarified
description
o Should "linear" be added as a sspmSourceSamplingDistribution
type to incidate the time is incremented by 1? Or can this be done
C. Kalbfleisch Expires Dec 2002 [Page 36]
INTERNET DRAFT SSPM MIB Jun 2002
with "deterministic"? Issue 2. Left as deterministic. Clarified
description.
o Should the packet fill for URL fail if the probe does not
support that ability? - issue 9 - have status change to active
fail with inconsistent value. Added clarifying text to
description.
o There is currently no object to indicate the 16-bit DS' PHB ID.
(Cole) issue 10 - Robert to provide text. Not added.
o Need some text for sspmSourceDestAddressType to restrict
addresses to to IPv4 only. - Issue 5. Proposal - don't restrict.
Lester to define additional attributes.
o Should we more fully specify the quality characteristics of the
clock, e.g., drift, skew ? - Resolved in 01 draft. Added
sspmClockMaxSkew
o Need to flush out conformance and compliance.
o Should we adopt a more flexible scheduling mechanism as found in
[22] or stict with enumeration. [22] E. Stephan, IP measurement
MIB, <draft-stephan-ippm-mib-00.txt>.
o Should Appl Layer Parameter be defined. Could need to set more
attributes for this. One option is a follow on MIB say for HTTP to
set header values, etc.
o sspmApplLayerExtentionParameter - We also discussed deleteing
this attribute and instead describing how one might define such an
attribute in a private extention in the appendix of this ID.
o May need to add application specific configuration tables. At
least need to configure which attributes are part of the protocol
header or body. Defer to protocol specific MIB extentions.
o What are the requirements for indexing on the history table. Do
we want to add an additional index to allow query based on a
subset of something like WEB? Resolved. Deleted history tables.
o Current definition of sspmSourceType and sspmSinkType prevent
configuration of measurements that are not reportable in apm/tpm.
May want to add some OID type to indicate non-apLocalIndex. Then
there is no reporting and breaks indexing. Moved to resolved.
o start time - time to start some test. Controlled by the control
object to enable
C. Kalbfleisch Expires Dec 2002 [Page 37]
INTERNET DRAFT SSPM MIB Jun 2002
o end time - when test ends. Purhaps duration is a better term
o Should start/end times be specified? Or should these be left to
the NMS and or implementation of the schedule/script MIBs to set
the control bit on/off.
o repeat time - for configuing test which run once per hour, day,
week, etc. Perhaps this can/should be done with the DISMAN
shedule MIB.
o This was is a reference to a performance monitoring protocol. (
http://telesto.advanced.org/~kalidindi/STR/owdp.html ). Need to
consider if the constructs described can be implemented with this
MIB.
13. Change Log
Changes from -02 to -03
o Restructured sspmSourceTable into sspmSourceProfileTable and
sspmSourceControlTable.
o Renamed sspmSourceControl to sspmSourceControlEnabled (so that
it was not named sspmSourceControlControl by the split to
two tables).
o Updated conformance statements for new naming scheme
o Updated MIB structure text
Changes from -01 to -02
o added clarifying text for sspmSourcePacketSize
o added clarifying text for sspmSourcePacketFillType when url is
used.
o added sspmMinFrequency and clarifying text in
sspmSourceFrequency.
o added sspmSourceFlowLabel
o Clarified description of sspmSourceSamplingDistribution
C. Kalbfleisch Expires Dec 2002 [Page 38]
INTERNET DRAFT SSPM MIB Jun 2002
Changes from -00 to -01
o Deleted history tables
o Added sspmClockMaxSkew
o Added compliance definitions
o Updated issues list.
o Addd relation to other work (section 5) from draft-cole-sspm-03
Initial version.
C. Kalbfleisch Expires Dec 2002 [Page 39]
