-- extracted from draft-dietz-tpm-mib-00.txt -- at Fri Mar 17 12:29:46 2000 TPM-MIB DEFINITIONS ::= BEGIN IMPORTS MODULE-IDENTITY, OBJECT-TYPE, Integer32, Counter32 FROM SNMPv2-SMI MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF RowStatus, TEXTUAL-CONVENTION, TimeStamp FROM SNMPv2-TC rmon, OwnerString FROM RMON-MIB protocolDirLocalIndex, LastCreateTime, DataSource, TimeFilter FROM RMON2-MIB; tpmMIB MODULE-IDENTITY LAST-UPDATED "200003101500Z" -- 10-Mar-2000 ORGANIZATION "Apptitude, Inc." CONTACT-INFO " Russell Dietz Apptitude, Inc. Postal: 6330 San Ignacio Avenue San Jose, CA 95119-1209 USA Tel: +1 408 574-2256 Fax: +1 408 224-1038 E-mail: rsdietz@apptitude.com" DESCRIPTION "This module defines Remote Monitoring MIB extensions for measuring traffic related transport performance metrics in networks." ::= { rmon 24 } tpmObjects OBJECT IDENTIFIER ::= { tpmMIB 1 } tpmNotifications OBJECT IDENTIFIER ::= { tpmMIB 2 } tpmConformance OBJECT IDENTIFIER ::= { tpmMIB 3 } tpmDirObjects OBJECT IDENTIFIER ::= { tpmObjects 1 } tpmConfigObjects OBJECT IDENTIFIER ::= { tpmObjects 2 } tpmMetricObjects OBJECT IDENTIFIER ::= { tpmObjects 3 } perfMetricDir OBJECT IDENTIFIER ::= { tpmDirObjects 1 } perfMetricProtocolDir OBJECT IDENTIFIER ::= { tpmDirObjects 2 } perfMetric OBJECT IDENTIFIER ::= { tpmMetricObjects 1 } -- -- Extensions to the RMON-2 MIB for the collection of Performance -- Metrics related to application traffic in a network -- -- In order to maintain the RMON 'look-and-feel', some of -- the text from the RMON-2 and HC-RMON MIBs by -- Steve Waldbusser have been used in this MIB. -- -- -- Performance Metric Directory Group -- -- Lists the inventory of performance metrics the probe has the -- capability of collecting and allows the configuration of -- entries in this list. -- perfMetricDirLastChange OBJECT-TYPE SYNTAX TimeStamp MAX-ACCESS read-only STATUS current DESCRIPTION "The value of sysUpTime at the time the performance metric directory was last modified, through modifications of the perfMetricDirConfig object." ::= { perfMetricDir 1 } perfMetricDirTable OBJECT-TYPE SYNTAX SEQUENCE OF PerfMetricDirEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This table lists the performance metrics that this agent has the capability to track and generate. There is one entry in this table for each such metric. These metrics represent different statistical analyses which may be performed on any or all protocols in the agent. The agent should boot up with this table preconfigured with those metrics that it has the ability to generate." ::= { perfMetricDir 2 } perfMetricDirEntry OBJECT-TYPE SYNTAX PerfMetricDirEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "A conceptual row in the perfMetricDirTable. An example of the indexing of this entry is perfMetricDirLocalIndex.2.1.2048.1.0, which is the encoding of a length of 2, followed by 2 subids encoding the perfMetricDirID of 1.2048, followed by a length of 1 and the 1 subids encoding zero-valued parameters. If the same perfMetricDirID has several different implementations within the agent that vary the parameters, each of those will appear in this table with the appropriate parameter values." INDEX { perfMetricDirID, -- Metric OID perfMetricDirParameters -- Metric parameter values } ::= { perfMetricDirTable 1 } PerfMetricDirEntry ::= SEQUENCE { perfMetricDirID OCTET STRING, perfMetricDirParameters OCTET STRING, perfMetricDirLocalIndex Integer32, perfMetricDirDescr DisplayString, perfMetricDirConfig INTEGER } perfMetricDirID OBJECT-TYPE SYNTAX OCTET STRING MAX-ACCESS not-accessible STATUS current DESCRIPTION "A unique identifier for a particular performance metric. Standard identifiers will be defined in a manner such as defined by other standard documents. See [20] for more details. Despite the broad set of standard metrics, the probe will only place entries in here for those performance metrics it chooses to collect. In other words, it need not populate this table with all of the possible variations of a 'response time related' metric. Whether or not it does these things is a matter of product definition (cost/benefit, usability), and is up to the designer of the product. If an entry is written to this table with a perfMetricDirID that the agent doesn't understand, either directly or algorithmically, the SET request will be rejected with an inconsistentName or badValue (for SNMPv1) error." ::= { perfMetricDirEntry 1 } perfMetricDirParameters OBJECT-TYPE SYNTAX OCTET STRING MAX-ACCESS not-accessible STATUS current DESCRIPTION "A set of parameters for the associated perfMetricDirID. See the associated RMON2 Performance Metric Identifiers document for a description of the possible parameters. There will be one octet in this string for each sub-identifier in the perfMetricDirID, and the parameters will appear here in the same order as the associated sub-identifiers appear in the perfMetricDirID. Every node in the perfMetricDirID tree has a different, optional set of parameters defined (that is, the definition of parameters for a node is optional). The proper parameter value for each node is included in this string. Note that the inclusion of a parameter value in this string for each node is not optional - what is optional is that a node may have no parameters defined, in which case the parameter field for that node will be zero." ::= { perfMetricDirEntry 2 } perfMetricDirLocalIndex OBJECT-TYPE SYNTAX Integer32 (1..2147483647) MAX-ACCESS read-only STATUS current DESCRIPTION "The locally arbitrary, but unique identifier associated with this perfMetricDir entry. The value for each supported metric must remain constant at least from one re-initialization of the entity's network management system to the next re-initialization. The specific value is meaningful only within a given SNMP entity. A perfMetricDirLocalIndex must not be reused until the next agent-restart." ::= { perfMetricDirEntry 3 } perfMetricDirDescr OBJECT-TYPE SYNTAX DisplayString (SIZE (1..64)) MAX-ACCESS read-only STATUS current DESCRIPTION "A textual description of the performance metric computation. A probe may choose to describe only a subset of the entire statistical operation (e.g. only a simple understanding as in 'response time in milliseconds'). This object is intended for human consumption only." ::= { perfMetricDirEntry 4 } perfMetricDirConfig OBJECT-TYPE SYNTAX INTEGER { notSupported(1), supportedOff(2), supportedOn(3) } MAX-ACCESS read-write STATUS current DESCRIPTION "This object describes and configures the probe's support for this performance metric. When the agent begins processing it creates entries in this table for all metrics that it can generate. Because the probe will only populate this table with supported entries, and the table cannot have entries added, the notSupport(1) setting is only used to signify that other configuration parameters are causing the agent to currently not support the generation and collection of this metric. If the value of this object is notSupported(1), the probe will not perform computations for this performance metric and shall not allow this object to be changed to any other value. If the value of this object is supportedOn(3), the probe supports computations for this performance metric and is configured to perform the computations for this performance metric for all perfMetricProtocolDirTable entries and all interfaces. If the value of this object is supportedOff(2), the probe supports computations for this performance metric but is configured to not perform the computations for this performance metric for any perfMetricProtocolDirEntries and all interfaces. Whenever this value changes from supportedOn(3) to supportedOff(2), the probe shall leave the current value of perfMetricProtocolDirConfig and perfMetricProtocolDirServerDynamic as it was prior to the change of perfMetricDirConfig. In addition, this change will cause the deletion of all entries in the perfTable, perfServerSummayTable and perfClientSummaryTable, for all appropriate studies configured in the perfControl table. It is important for the management application to understand the relationship between these configuration values. This table acts as a filter for features selected in the perfMetricProtocolDir Table. In other words, if support is enabled in the perfMetricProtocolDirTable, but disabled here, the metric will not be computed." ::= { perfMetricDirEntry 5 } -- -- Performance Metric Protocol Directory -- -- This table is used to describe and link a set of performance -- metrics to an entry in the protocol directory. The table is also -- used to detail and configure the collection of each metric, as -- well as the dynamic creation of Server Addresses in the -- perfServerConfig table. -- perfMetricProtocolDirLastChange OBJECT-TYPE SYNTAX TimeStamp MAX-ACCESS read-only STATUS current DESCRIPTION "The value of sysUpTime at the time the performance metric protocol directory was last modified, through modifications of the perfMetricProtocolDirConfig or perfMetricProtocolDirServerDynamicConfig objects." ::= { perfMetricProtocolDir 1 } perfMetricProtocolDirTable OBJECT-TYPE SYNTAX SEQUENCE OF PerfMetricProtocolDirEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This table lists the performance metrics that this agent has the capability to compute and collect, for the specified protocol. There is one entry in this table for each such combination of metric and protocol. The entries in this table represent the metrics that are collected for each protocol. The agent should boot up with this table preconfigured with those combinations of metrics and protocols that it knows about and wishes to monitor. Implementations must populate the table with all possible metric and protocol combinations and have the default configuration objects set to supportedOff(2). This table does not support the creation of new metric and protocol combinations by the management application. The deletion of an entry in the protocolDirTable will cause the removal of entries from this table. These entries must be removed because the protocolDirLocalIndex value will no longer be visible in the protocolDirTable. When an entry is created in the protocolDirTable and the agent has the ability to support metrics for that protocol. The appropriate entries must be made in the perfMetricProtocol table." ::= { perfMetricProtocolDir 2 } perfMetricProtocolDirEntry OBJECT-TYPE SYNTAX PerfMetricProtocolDirEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "A conceptual row in the perfMetricProtocolDirTable. An example of the indexing of this entry is perfMetricProtocolDirConfig.1.2. Where 1 is the value of a valid and visible protocolDirLocalIndex object in the protocolDir table and 2 is the value of a valid perfMetricDirLocalIndex in the perfMetricDir table." INDEX { protocolDirLocalIndex, -- Protocol Index perfMetricDirLocalIndex -- Metric Index } ::= { perfMetricProtocolDirTable 1 } PerfMetricProtocolDirEntry ::= SEQUENCE { perfMetricProtocolDirConfig INTEGER, perfMetricProtocolDirServerDynamic INTEGER } perfMetricProtocolDirConfig OBJECT-TYPE SYNTAX INTEGER { notSupported(1), supportedOff(2), supportedOn(3) } MAX-ACCESS read-write STATUS current DESCRIPTION "This object describes and configures the probe's support for this performance metric in relationship to the specified protocol. The agent creates entries in this table for all metrics and protocol combinations that it can generate. Because the probe will only populate this table with supported entries, and the table cannot have entries added, the notSupported(1) setting is only used to signify that other configuration parameters are causing the agent to currently not support the generation and collection of this metric for the specified protocol. Also, the status of this object will not change to notSupported(1) due to a change to supportedOff(2) in the perfMetricDir table. If the value of this object is notSupported(1), the probe will not perform computations for this performance metric and protocol combination and shall not allow this object to be changed to any other value. If the value of this object is supportedOn(3), the probe supports computations for this performance metric and protocol and is configured to perform the computations for this performance metric and protocol combination for all interfaces. If the value of this object is supportedOff(2), the probe supports computations for this performance metric for the specified protocol, but is configured to not perform the computations for this performance metric and protocol for any interfaces. Whenever this value changes from supportedOn(3) to supportedOff(2), the probe shall cause the deletion of all entries in the perfTable, perfServerSummayTable and perfClientSummaryTable, for all appropriate studies configured in the perfControl table." ::= { perfMetricProtocolDirEntry 1 } perfMetricProtocolDirServerDynamic OBJECT-TYPE SYNTAX INTEGER { notSupported(1), supportedOff(2), supportedOn(3) } MAX-ACCESS read-write STATUS current DESCRIPTION "This object describes and configures the probe's support for the discovery of servers for this performance metric in relationship the the specified protocol. If an agent has the ability to dynamically determine the server for a protocol while collecting a specific metric, then the agent should set this object to supportedOff(2), by default. If the agent has no way to determine the server for this metric and protocol, the agent must set this object to notSupported(1). When the agent creates entries in this table for all metrics and protocol combinations that it can generate. If the value of this object is notSupported(1), the probe will not populate the perfServerConfig table with entries for the metric and protocol combination and shall not allow this object to be changed to any other value. If the value of this object is supportedOn(3), the probe supports the creation of entries for this performance metric and protocol and is configured to populate the perfServerConfig table for this performance metric and protocol combination for all interfaces. If the value of this object is supportedOff(2), the probe supports the creation of dynamic entries in the perfServerConfig table for this performance metric for the specified protocol, but is configured to not insert entries into the perfServerConfig table for this performance metric and protocol for any interfaces. Whenever this value changes from supportedOn(3) to supportedOff(2), the probe shall cause the deletion of all entries in the perfServerConfig table with the perfServerConfigEntryType object set to dynamic(1) as well as causing the removal of any entries from the perfTable, perfServerSummayTable and perfClientSummaryTable, where the perfServerConfigServerAddress object was used to populate those tables for all appropriate studies configured in the perfControl table." ::= { perfMetricProtocolDirEntry 2 } -- -- -- Performance Metric Group -- -- The perfControlTable is the controlling entry to manage -- the population of studies in the Performance Group -- perfControlTable OBJECT-TYPE SYNTAX SEQUENCE OF PerfControlEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "A table to control the collection of performance metric studies for selected interfaces, metrics and protocols. Note that this is not like the typical RMON controlTable and dataTable in which each entry creates its own data table. Each entry in this table enables the creation of up to 3 data tables on a study basis. For each interval, the study is updated in place and the current data content of the table becomes invalid." ::= { perfMetric 1 } perfControlEntry OBJECT-TYPE SYNTAX PerfControlEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "A conceptual row in the perfControlTable. An example of the indexing of this entry is perfControlDataSource.1" INDEX { perfControlIndex } ::= { perfControlTable 1 } perfControlEntry ::= SEQUENCE { perfControlIndex Integer32, perfControlDataSource DataSource, perfControlMetrics Integer32, perfControlAggregationType INTEGER, perfControlTimeRemaining Integer32, perfControlGeneratedReports Counter32, perfControlDuration Integer32, perfControlRequestedSize Integer32, perfControlGrantedSize Integer32, perfControlStartTime TimeStamp, perfControlOwner OwnerString, perfControlStatus RowStatus } perfControlIndex OBJECT-TYPE SYNTAX Integer32 (1..65535) MAX-ACCESS not-accessible STATUS current DESCRIPTION "A unique index for this entry in the perfControlTable." ::= { perfControlEntry 1 } perfControlDataSource OBJECT-TYPE SYNTAX DataSource MAX-ACCESS read-create STATUS current DESCRIPTION "The source of data for this perfControlEntry." ::= { perfControlEntry 2 } perfControlMetrics OBJECT-TYPE SYNTAX Integer32 (1..65535) MAX-ACCESS read-create STATUS current DESCRIPTION "The number of performance metric and protocol combinations to be collected in the portion of perfTable associated with this perfControlEntry. This object may not be modified if the associated instance of perfControlStatus is equal to active(1)." ::= { perfControlEntry 3 } perfControlAggregationType OBJECT-TYPE SYNTAX INTEGER { flows(1), -- Least Aggregation clients(2), servers(3), protocols(4) -- Most Aggregation } MAX-ACCESS read-create STATUS current DESCRIPTION "The type of aggregation being performed for this set of reports. The metrics for a single traffic flow are selected in the perfTable by the perfControlMetrics object. When such metrics are aggregated in this MIB, these metrics are replaced by statistical representation of each metric. The metrics describing aggregates are constant no matter which type of aggregation is being performed. These metrics may be found in the perfTable. The flows(1) aggregation is the simplest. All traffic flows that share common protocol/server/client 3-tuples are aggregated together, resulting in a set of metrics for all such unique 3-tuples. The clients(2) aggregation results in somewhat more aggregation (i.e. fewer resulting records). All traffic flows that share common protocol/client tuples are aggregated together, resulting in a set of metrics for all such unique tuples. The clients(3) aggregation usually results in still more aggregation (i.e. fewer resulting records). All traffic flows that share common protocol/server tuples are aggregated together, resulting in a set of metrics for all such unique tuples. The protocols(4) aggregation results in the most aggregation (i.e. the fewest resulting records). All traffic flows that share a common protocol are aggregated together, resulting in a set of metrics for all such unique protocols. Note that it is not meaningful to aggregate protocols, as different protocols have widely varying characteristics. As a result, this set of aggregations is complete. This object may not be modified if the associated perfControlStatus object is equal to active(1)." ::= { perfControlEntry 4 } perfControlTimeRemaining OBJECT-TYPE SYNTAX Integer32 (0..2147483647) MAX-ACCESS read-create STATUS current DESCRIPTION "The number of seconds left in the report currently being collected. When this object is modified by the management station, a new collection is started, possibly aborting a currently running report. The new value is used as the requested duration of this report, and is immediately loaded into the associated perfControlDuration object. When the report finishes, the probe will automatically start another collection with the same initial value of perfControlTimeRemaining. Thus the management station may simply read the resulting reports repeatedly, checking the startTime and duration each time to ensure that a report was not missed or that the report parameters were not changed. While the value of this object is nonzero, it decrements by one per second until it reaches zero. At the time that this object decrements to zero, the reports are made accessible in any or all of the perfTable, perfServerSummaryTable and perfClientSummaryTable overwriting any reports that may be there. When this object is modified by the management station, any associated entries in the perfTable, perfServerSummaryTable and perfClientSummaryTable will be deleted." DEFVAL { 1800 } ::= { perfControlEntry 5 } perfControlGeneratedReports OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "The number of reports that have been generated by this entry." ::= { perfControlEntry 6 } perfControlDuration OBJECT-TYPE SYNTAX Integer32 MAX-ACCESS read-only STATUS current DESCRIPTION "The number of seconds that this report has collected during the last analysis interval. When the associated perfControlTimeRemaining object is set, this object shall be set by the probe to the same value and shall not be modified until the next time the perfControlTimeRemaining is set. This value shall be zero if no reports have been requested for this perfControlEntry." ::= { perfControlEntry 7 } perfControlRequestedSize OBJECT-TYPE SYNTAX Integer32 (0..2147483647) MAX-ACCESS read-create STATUS current DESCRIPTION "The maximum number of Client and Server combination entries requested for this report. When this object is created or modified, the probe should set perfControlGrantedSize as closely to this object as is possible for the particular probe implementation and available resources. It is important to note that this value is the number of requested entries in the perfTable only. Since the probe can derive the perfServerSummaryTable and perfClientSummaryTable from this table, the probe must make sure that sufficient resources exist to support the creation of the perfTable plus any additional resources required to convert or support the two summary tables." DEFVAL { 1024 } ::= { perfControlEntry 8 } perfControlGrantedSize OBJECT-TYPE SYNTAX Integer32 (0..2147483647) MAX-ACCESS read-only STATUS current DESCRIPTION "The maximum number of performance entries in this report. When the associated perfControlRequestedSize object is created or modified, the probe should set this object as closely to the requested value as is possible for the particular implementation and available resources. The probe must not lower this value except as a result of a set to the associated perfControlRequestedSize object. Since the probe must support only the granted size, the probe should attempt to maintain the most recently active entries in the perfMetric table if there is no more room or until there are no more performance metric entries. It is an implementation-specific matter as to whether or not zero-valued entries are available." ::= { perfControlEntry 9 } perfControlStartTime OBJECT-TYPE SYNTAX TimeStamp MAX-ACCESS read-only STATUS current DESCRIPTION "The value of sysUpTime when this performance metric report was last started. In other words, this is the time that the associated perfControlTimeRemaining object was modified to start the requested report or the time the report was last automatically (re)started. This object may be used by the management station to determine if a report was missed or not." ::= { perfControlEntry 10 } perfControlOwner OBJECT-TYPE SYNTAX OwnerString MAX-ACCESS read-create STATUS current DESCRIPTION "The entity that configured this entry and is therefore using the resources assigned to it." ::= { perfControlEntry 11 } perfControlStatus OBJECT-TYPE SYNTAX RowStatus MAX-ACCESS read-create STATUS current DESCRIPTION "The status of this performance control entry. An entry may not exist in the active state unless all objects in the entry have an appropriate value. If this object is not equal to active(1), all associated entries in the perfTable shall be deleted." ::= { perfControlEntry 12 } -- -- Metric tables -- -- The following tables are all part of the Metric Study Group. -- These tables contain the results of the collected metrics. -- perfMetricTable OBJECT-TYPE SYNTAX SEQUENCE OF PerfMetricEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "A list of performance metric and protocol collection entries." ::= { perfMetric 2 } perfMetricEntry OBJECT-TYPE SYNTAX PerfMetricEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "A list of metric and protocol index values for the statistics to be generated for a specific report in the perfControl table." Entries in this table are created when an associated perfControlMetrics object is created. The perfControlIndex value in the index is that of the associated perforamnceControlEntry. For example, an instance of perfMetricDirLocalIndex might be perfMetricDirLocalIndex.1.3" INDEX { perfControlIndex, perfMetricIndex } ::= { perfMetricTable 1 } PerfMetricEntry ::= SEQUENCE { perfMetricIndex Integer32, perfMetricMetricDirLocalIndex Integer32, perfMetricProtocolDirLocalIndex Integer32 } perfMetricIndex OBJECT-TYPE SYNTAX Integer32 (1..65535) MAX-ACCESS not-accessible STATUS current DESCRIPTION "An index used to uniquely identify an entry in the perforamnceMetric table. Each such entry defines a metric instance to be generated for a specific protocol periodically." ::= { perfMetricEntry 1 } perfMetricMetricDirLocalIndex OBJECT-TYPE SYNTAX Integer32 (1..2147483647) MAX-ACCESS read-create STATUS current DESCRIPTION "The perfMetricDirLocalIndex of the particular metric to be generated. This object may not be modified if the associated perfControlStatus object is equal to active(1)." ::= { perfMetricEntry 2 } perfMetricProtocolDirLocalIndex OBJECT-TYPE SYNTAX Integer32 (1..2147483647) MAX-ACCESS read-create STATUS current DESCRIPTION "The protocolDirLocalIndex of the particular protocol to be analyzed when computing and generating the selected metric. This object may not be modified if the associated perfControlStatus object is equal to active(1)." ::= { perfMetricEntry 3 } -- -- Performance Table -- -- This table contains performance metric studies for each of the -- control table entries in performanceControl table. These studies -- are provided based on the selections and parameters found for the -- entry in the perfControl table. -- perfTable OBJECT-TYPE SYNTAX SEQUENCE OF PerfEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "A study of performance metrics for those perfMetric table entries specified in the perfMetric table as indexed by perfControlIndex and perfMetricIndex." ::= { perfMetric 3 } perfEntry OBJECT-TYPE SYNTAX PerfEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "A conceptual row in the perfTable. The perControlIndex value in the index identifies the perfControlEntry on whose behalf this entry was created. The perfControIndex value in the index identifies which report (in the series of reports) this entry is a part of. The perfMetricIndex value in the index identifies the transported application protocol of the traffic flows aggregated in this entry. The protocolDirLocalIndex value in the index identifies the network layer protocol of the perfServerAddress and perfClientAddress. When the associated perfControlAggregationType value is equal to protocol(4), this value will equal 0. The perfServerAddress value in the index identifies the network layer address of the server in traffic flows aggregated in this entry. The perfClientAddress value in the index identifies the network layer address of the client in traffic flows aggregated in this entry. Note that the order of protocolDirLocalIndex variables is the opposite of that in the RMON2 MIB (application.network instead of network.application) so that the report entries are sorted by application first, server second and client third. The perfControlIndex value in the index identifies the perfControlEntry on whose behalf this entry was created. The perfMetricIndex value in the index identifies the metric and protocol of the perfServerAddress and perfClientAddress, via the perfMetric table. An example of the indexing of this table is perfStatisticN.1.2.17.4.128.2.6.7.4.128.2.6.6" INDEX { perfControlIndex, perfMetricIndex, -- Metric and Protocol protocolLocalDirIndex, -- Network Layer perfServerAddress, perfClientAddress } ::= { perfTable 1 } PerfEntry ::= SEQUENCE { perfServerAddress OCTET STRING, perfClientAddress OCTET STRING, perfStatisticN Counter32, perfOverflowStatisticN Counter32, perfHCStatisticN Counter64, perfStatisticSumX Counter32, perfOverflowStatisticSumX Counter32, perfHCStatisticSumX Counter64, perfStatisticMaximum Gauge32, perfStatisticMinimum Gauge32, perfStatisticSumSquared Counter32, perfOverflowStatisticSumSquared Counter32, perfHCStatisticSumSquared Counter64, perfStatisticSumIX Counter32, perfOverflowStatisticSumIX Counter32, perfHCStatisticSumIX Counter64 } perfServerAddress OBJECT-TYPE SYNTAX OCTET STRING MAX-ACCESS not-accessible STATUS current DESCRIPTION "The network layer address of the server host in this conversation. This is represented as an octet string with specific semantics and length as identified by the associated perfMetricProtocolDirLocalIndex from the perfMetricIndex for this conversation. For example, if the protocolDirLocalIndex indicates an encapsulation of IP, this object is encoded as a length octet of 4, followed by the 4 octets of the IP address, in network byte order." ::= { perfEntry 1 } perfClientAddress OBJECT-TYPE SYNTAX OCTET STRING MAX-ACCESS not-accessible STATUS current DESCRIPTION "The network layer address of the client host in this conversation. This is represented as an octet string with specific semantics and length as identified by the associated perfMetricProtocolDirLocalIndex from the perfMetricIndex for this conversation. For example, if the protocolDirLocalIndex indicates an encapsulation of IP, this object is encoded as a length octet of 4, followed by the 4 octets of the IP address, in network byte order." ::= { perfEntry 2 } perfStatisticN OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "The count of the total number of data points for the specified metric. This number always represents the total size of the statistical datum analyzed. Each metric specifies the exact meaning of this object. This value represents the results of one metric and is related directly to the specific parameters of the metric and the Server and Client addresses involved." ::= { perfEntry 3 } perfOverflowStatisticN OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "The number of times the associated perfStatisticN counter has overflowed." ::= { perfEntry 4 } perfHCStatisticN OBJECT-TYPE SYNTAX Counter64 MAX-ACCESS read-only STATUS current DESCRIPTION "The high-capacity version of perfStatisticN." ::= { perfEntry 5 } perfStatisticSumX OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "The sum of all the data point values for the specified metric. This number always represents the total values of the statistical datum analyzed. Each metric specifies the exact meaning of this object. This value represents the results of one metric and is related directly to the specific parameters of the metric and the Server and Client addresses involved." ::= { perfEntry 6 } perfOverflowStatisticSumX OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "The number of times the associated perfStatisticSumX counter has overflowed." ::= { perfEntry 7 } perfHCStatisticSumX OBJECT-TYPE SYNTAX Counter64 MAX-ACCESS read-only STATUS current DESCRIPTION "The high-capacity version of perfStatisticSumX." ::= { perfEntry 8 } perfStatisticMaximum OBJECT-TYPE SYNTAX Gauge32 MAX-ACCESS read-only STATUS current DESCRIPTION "The single maximum data point value observed during the study period for the specified metric. This number always represents the maximum value of any single statistical datum analyzed. Each metric specifies the exact meaning of this object. This value represents the results of one metric and is related directly to the specific parameters of the metric and the Server and Client addresses involved." ::= { perfEntry 9 } perfStatisticMinimum OBJECT-TYPE SYNTAX Gauge32 MAX-ACCESS read-only STATUS current DESCRIPTION "The single minimum data point value observed during the study period for the specified metric. This number always represents the minimum value of any single statistical datum analyzed. Each metric specifies the exact meaning of this object. This value represents the results of one metric and is related directly to the specific parameters of the metric and the Server and Client addresses involved." ::= { perfEntry 10 } perfStatisticSumSquared OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "The sum of all the squared data point values for the specified metric. This number always represents the total of the squared values of the statistical datum analyzed. Each metric specifies the exact meaning of this object. This value represents the results of one metric and is related directly to the specific parameters of the metric and the Server and Client addresses involved." ::= { perfEntry 11 } perfOverflowStatisticSumSquared OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "The number of times the associated perfStatisticSumSquared counter has overflowed." ::= { perfEntry 12 } perfHCStatisticSumSquared OBJECT-TYPE SYNTAX Counter64 MAX-ACCESS read-only STATUS current DESCRIPTION "The high-capacity version of perfStatisticSumSquared." ::= { perfEntry 13 } perfStatisticSumIX OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "For each interval, each data point is associated with a value I, I = 1..N where N is the number of data points, perfStatisticN. IX is the multiplication of the data point value with the current I. This value along with the other statistics values allow the calculation of the slope of the least-squares line through the data points." ::= { perfEntry 14 } perfOverflowStatisticSumIX OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "The number of times the associated perfStatisticSumIX counter has overflowed." ::= { perfEntry 15 } perfHCStatisticSumIX OBJECT-TYPE SYNTAX Counter64 MAX-ACCESS read-only STATUS current DESCRIPTION "The high-capacity version of perfStatisticSumIX." ::= { perfEntry 16 } END -- -- Copyright (C) The Internet Society (2000). All Rights Reserved. -- -- 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 doc- -- ument 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 develop- -- ing 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 MER- -- CHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE."