EZ5 MIB Catalog

CISCO-RTP-METRICS-MIB

2009-06-17

This MIB module defines objects that describe the quality metrics of RTP streams, similar to those described by an RTCP Receiver Report packet [RFC3550]. GLOSSARY ============ Expected Packets - this value is formally defined as the extended last sequence number received less the initial sequence number received. An extended last sequence number is a 32-bit value, where the most significant 16-bit word indicates the number of sequence number cycles, and the least significant 16-bit word indicates the highest sequence number received. Flow Monitor - a hardware or software entity that classifies traffic flows, collects flow data, and periodically computes flow metrics. Flow Metric - a measurement that reflects the quality of a traffic flow. Inter-Arrival Jitter - an estimate of the statistical variance of the RTP data packet inter-arrival time. The inter-arrival jitter, J, is formally defined to be the mean deviation (smoothed absolute value) of the difference, D, in packet spacing at the flow monitor compared to the sender for a pair of packets. This is equivalent to the difference in the relative transit time for two packets; the relative transit time is the difference between a packet's RTP timestamp and the device's clock at the time of arrival (measured in the same units): D(i,j) = (Rj - Ri) - (Sj - Si) = (Rj - Sj) - (Ri - Si) where Si is the RTP timestamp from packet i, and Ri is the time of arrival in RTP timestamp units for packet i. The inter-arrival jitter SHOULD be calculated continuously for each RTP data packet received from source SSRCn, using this equation to compute difference for each packet and the previous packet (in order of arrival, not necessarily in sequence). |D(i-1,i)| - J(i-1) J(i) = J(i-1) + ------------------- 16 Measurement Interval - the length of time over which a flow monitor collects data related to a traffic flow, after which the flow monitor computes flow metrics using the collected data. Loss Distance - the difference between the sequence numbers delimiting the start of two consecutive loss intervals. Consider the following sequence of RTP data packets: 111111 111222 2233 33333 444 444 5 123456x890123xxxx8901xxx56789x123xx678x0 ^ ^ ^ ^ ^ ^ | | | | | | LI1 LI2 LI3 LI4 LI5 LI6 Loss Interval | Loss Distance ===============+=============== 1 | 2 | 7 3 | 8 4 | 8 5 | 4 6 | 5 Loss Fraction - the fraction of RTP data packets from source SSRCn lost during a measurement interval, expressed as a fixed-point number: Li Fi = ---- Ei where Fi is the loss fraction for measurement interval i, Li is the lost packets during measurement interval i, and Ei is the expected packets during measurement interval i. Observe that the number of packets lost includes packets that are late or duplicates, and hence this number can can have a theoretical theoretical value between negative infinity and one. The cumulative loss fraction is the fraction of RTP data packets from source SSRCn lost over the duration monitoring the flow: n sum [Li] i=1 Fn = ---------- n sum [Ei] i=1 where Fn is the cumulative loss fraction over n measurement intervals. Loss Interval - an interval in which consecutive packet losses were experienced. Consider the following sequence of RTP data packets: 111111 111222 2233 33333 444 444 5 123456x890123xxxx8901xxx56789x123xx678x0 ^ ^ ^ ^ ^ ^ | | | | | | LI1 LI2 LI3 LI4 LI5 LI6 LI1 through LI6 indicate the start of loss intervals observed in this sequence. Loss Interval Duration - the number of packets lost in a loss interval. Consider the following sequence of RTP data packets: 111111 111222 2233 33333 444 444 5 123456x890123xxxx8901xxx56789x123xx678x0 ^ ^ ^ ^ ^ ^ | | | | | | LI1 LI2 LI3 LI4 LI5 LI6 Loss Interval | Duration ===============+========== 1 | 1 2 | 4 3 | 3 4 | 1 5 | 2 6 | 1 Lost Packets - this value is formally defined as the number of packets expected less the number of packets actually received, where the number of packets received includes those which are late or duplicates. SSRCn - the SSRC identifier of the source. Traffic Flow - a unidirectional stream of packets conforming to a classifier. For example, packets having a particular source IP address, destination IP address, protocol type, source port number, and destination port number. Transit Time - the latency from the insertion into the network to the flow monitor. This value can be computed by taking the difference between a packet's RTP timestamp and the device's clock at the time of arrival (measured in the same units). REFERENCES ============== [RFC3550] H. Schlzrinne, S. Casner, R. Frederick, V. Jacobson, 'RTP: A Transport Protocol for Real-Time Applications', RFC-3550, July 2003.

Download CISCO-RTP-METRICS-MIB.txt Open CISCO-RTP-METRICS-MIB.txt in a new tab

SCALARS (1) · TABLES (2)

Scalars (1)

NameOID
cfmRtpMetricsTableChanged1.3.6.1.4.1.9.9.703.1.1.2

Tables (2)

NameOID
cfmRtpMetricsTable1.3.6.1.4.1.9.9.703.1.1.1
cfmRtpMetricsIntTable1.3.6.1.4.1.9.9.703.1.1.3

END OF TOC

Scalar details

cfmRtpMetricsTableChanged

1.3.6.1.4.1.9.9.703.1.1.2

TimeStampThe value of the sysUpTime object at which a specific occurrence happened. The specific occurrence must be defined in the description of any object defined using this type. If sysUpTime is reset to zero as a result of a re- initialization of the network management (sub)system, then the values of all TimeStamp objects are also reset. However, after approximately 497 days without a re- initialization, the sysUpTime object will reach 2^^32-1 and then increment around to zero; in this case, existing values of TimeStamp objects do not change. This can lead to ambiguities in the value of TimeStamp objects. · TimeTicks

This object indicates the value of sysUpTime the last time the device created/destroyed a row in the cfmRtpMetricsTable.

Table details

cfmRtpMetricsTable

1.3.6.1.4.1.9.9.703.1.1.1

Index: cfmFlowMonitorId · cfmFlowId

This table contains aggregate data maintained by a flow monitor for traffic flows for which it is computing RTP metrics. This table has an sparse dependent relationship on the cfmFlowMetricsTable (defined by the CISCO-FLOW-MONITOR-MIB), containing a row for each row in the cfmFlowMetricsTable having a corresponding instance of cfmFlowMetricsCollected with the 'rtp' bit set to one.

from CISCO-FLOW-MONITOR-MIB

cfmFlowMonitorId

FlowMonitorIdentifierThis textual convention denotes an arbitrary integer-value that uniquely identifies a flow monitor. (1..4294967295) · Unsigned32 · hint d

This object indicates an arbitrary integer-value that uniquely identifies the flow monitor. Observe that the value assigned to a flow monitor does not necessarily persist across restarts or the removal-insertion of a physical entity supporting flow monitor(s).

cfmFlowId

FlowIdentifierThis textual convention denotes an arbitrary integer-value that uniquely identifies a traffic flow within the scope of the flow monitor that collects data and periodically computes metrics for the traffic flow. (1..4294967295) · Unsigned32 · hint d

This object indicates an arbitrary integer-value that uniquely identifies a traffic flow in the scope of the flow monitor that learned it. Observe that the value assigned to a flow does not necessarily persist across restarts or the removal-insertion of a physical entity supporting flow monitor(s).

cfmRtpMetricsValid

1.3.6.1.4.1.9.9.703.1.1.1.1.1

BITS

This object indicates which metrics are valid for the traffic flow: 'expectedPkts' If this bit is set to '1', then the corresponding instance of cfmRtpMetricsExpectedPkts is valid. 'lostPkts' If this bit is set to '1', then the corresponding instance of cfmRtpMetricsLostPkts is valid. 'lossFraction' If this bit is set to '1', then the corresponding instances of cfmRtpMetricsFracScale, cfmRtpMetricsFracPrecision, and cfmRtpMetricsFrac are valid. 'lossIntervals' If this bit is set to '1', then the corresponding instance of cfmRtpMetricsLIs is valid. 'avgLossIntervalDuration' If this bit is set to '1', then the corresponding instances of cfmRtpMetricsAvgLDScale, cfmRtpMetricsAvgLDPrecision, and cfmRtpMetricsAvgLD are valid. 'avgLossDistance' If this bit is set to '1', then the corresponding instance of cfmRtpMetricsAvgLossDistance is valid. 'jitter' If this bit is set to '1', then the corresponding instances of cfmRtpMetricsJitterScale, cfmRtpMetricsJitterPrecision, and cfmRtpMetricsJitter are valid.

cfmRtpMetricsExpectedPkts

1.3.6.1.4.1.9.9.703.1.1.1.1.2

Counter64 (0..18446744073709551615) · packets

This object indicates the number of RTP packets expected for the traffic flow.

cfmRtpMetricsLostPkts

1.3.6.1.4.1.9.9.703.1.1.1.1.3

Counter64 (0..18446744073709551615) · packets

This object indicates the number of RTP packets lost for the traffic flow.

cfmRtpMetricsFracScale

1.3.6.1.4.1.9.9.703.1.1.1.1.4

FlowMetricScale1 = yocto2 = zepto3 = atto4 = femto5 = pico6 = nano7 = micro8 = milli9 = units10 = kilo11 = mega12 = giga13 = tera14 = exa15 = peta16 = zetta17 = yottaThis textual convention denotes an enumerated integer-value that represents an International System of Units (SI) prefix used as a scaling factor for fixed-point values: Prefix Scale Factor ========================= 'yocto' 10E-24 'zepto' 10E-21 'atto' 10E-18 'femto' 10E-15 'pico' 10E-12 'nano' 10E-9 'micro' 10E-6 'milli' 10E-3 'units' 10E0 'kilo' 10E3 'mega' 10E6 'giga' 10E9 'tera' 10E12 'exa' 10E15 'peta' 10E18 'zetta' 10E21 'yotta' 10E24 A MIB module may abstract a fixed-point value by defining three objects together: 1) A FlowMetricScale object, which indicates the scale of the value. 2) A FlowMetricPrecision object, which indicates the precision of the value. In the case that the value has a fractional portion, this object indicates the number of digits comprising the fractional portion. 3) A FlowMetricValue object, which indicates the value before scaling. · Integer32

This object indicates the scaling factor for the corresponding instance of cfmRtpMetricsFrac.

cfmRtpMetricsFracPrecision

1.3.6.1.4.1.9.9.703.1.1.1.1.5

FlowMetricPrecisionThis textual convention denotes the precision or accuracy of a fixed-point value. A MIB module may abstract a fixed-point value by defining three objects together: 1) A FlowMetricScale object, which indicates the scale of the value. 2) A FlowMetricPrecision object, which indicates the precision of the value. In the case that the value has a fractional portion, this object indicates the number of digits comprising the fractional portion. 3) A FlowMetricValue object, which indicates the value before scaling. If an instance of an object of this type has a value in the range of 1 to 9, then it represents the precision of the associated value; that is, the number of decimal places in the fractional part of the associated value. For example, if the Media Loss Rate (MLR) computed for a traffic flow is 350.9E-6, then the FlowMetricScale object is 'micro', the FlowMetricPrecision object is 1, and the object indicating the value is 3509. If an instance of an object of this type has a value in the range of -8 to -1, then it represents the number of accurate digits in the associated value. For example, if the jitter measured for a traffic flow can range between -100,000 and 100,000 microseconds in 10 microsecond increments, with an accuracy of +/- 5 microseconds, the FlowMetricScale object is 'micro', the FlowMetricPrecision object is -2, and the object indicating the value has range of -100,000 to 100,000. (-8..-1 | 1..9) · Integer32 · hint d

This object indicates the precision for the corresponding instance of cfmRtpmetricsFrac.

cfmRtpMetricsFrac

1.3.6.1.4.1.9.9.703.1.1.1.1.6

FlowMetricValueThis textual convention denotes the value of a fixed-point value. A MIB module may abstract a fixed-point value by defining three objects together: 1) A FlowMetricScale object, which indicates the scale of the value. 2) A FlowMetricPrecision object, which indicates the precision of the value. In the case that the value has a fractional portion, this object indicates the number of digits comprising the fractional portion. 3) A FlowMetricValue object, which indicates the value before scaling. (-1000000000..1000000000) · Integer32 · hint d

This object indicates the loss fraction for traffic flow.

cfmRtpMetricsLIs

1.3.6.1.4.1.9.9.703.1.1.1.1.7

Counter64 (0..18446744073709551615)

This object indicates the number of loss intervals for the traffic flow.

cfmRtpMetricsAvgLDScale

1.3.6.1.4.1.9.9.703.1.1.1.1.8

FlowMetricScale1 = yocto2 = zepto3 = atto4 = femto5 = pico6 = nano7 = micro8 = milli9 = units10 = kilo11 = mega12 = giga13 = tera14 = exa15 = peta16 = zetta17 = yottaThis textual convention denotes an enumerated integer-value that represents an International System of Units (SI) prefix used as a scaling factor for fixed-point values: Prefix Scale Factor ========================= 'yocto' 10E-24 'zepto' 10E-21 'atto' 10E-18 'femto' 10E-15 'pico' 10E-12 'nano' 10E-9 'micro' 10E-6 'milli' 10E-3 'units' 10E0 'kilo' 10E3 'mega' 10E6 'giga' 10E9 'tera' 10E12 'exa' 10E15 'peta' 10E18 'zetta' 10E21 'yotta' 10E24 A MIB module may abstract a fixed-point value by defining three objects together: 1) A FlowMetricScale object, which indicates the scale of the value. 2) A FlowMetricPrecision object, which indicates the precision of the value. In the case that the value has a fractional portion, this object indicates the number of digits comprising the fractional portion. 3) A FlowMetricValue object, which indicates the value before scaling. · Integer32

This object indicates the scaling factor for the corresponding instance of cfmRtpMetricsAvgLD.

cfmRtpMetricsAvgLDPrecision

1.3.6.1.4.1.9.9.703.1.1.1.1.9

FlowMetricPrecisionThis textual convention denotes the precision or accuracy of a fixed-point value. A MIB module may abstract a fixed-point value by defining three objects together: 1) A FlowMetricScale object, which indicates the scale of the value. 2) A FlowMetricPrecision object, which indicates the precision of the value. In the case that the value has a fractional portion, this object indicates the number of digits comprising the fractional portion. 3) A FlowMetricValue object, which indicates the value before scaling. If an instance of an object of this type has a value in the range of 1 to 9, then it represents the precision of the associated value; that is, the number of decimal places in the fractional part of the associated value. For example, if the Media Loss Rate (MLR) computed for a traffic flow is 350.9E-6, then the FlowMetricScale object is 'micro', the FlowMetricPrecision object is 1, and the object indicating the value is 3509. If an instance of an object of this type has a value in the range of -8 to -1, then it represents the number of accurate digits in the associated value. For example, if the jitter measured for a traffic flow can range between -100,000 and 100,000 microseconds in 10 microsecond increments, with an accuracy of +/- 5 microseconds, the FlowMetricScale object is 'micro', the FlowMetricPrecision object is -2, and the object indicating the value has range of -100,000 to 100,000. (-8..-1 | 1..9) · Integer32 · hint d

This object indicates the precision for the corresponding instance of cfmRtpMetricsAvgLD.

cfmRtpMetricsAvgLD

1.3.6.1.4.1.9.9.703.1.1.1.1.10

FlowMetricValueThis textual convention denotes the value of a fixed-point value. A MIB module may abstract a fixed-point value by defining three objects together: 1) A FlowMetricScale object, which indicates the scale of the value. 2) A FlowMetricPrecision object, which indicates the precision of the value. In the case that the value has a fractional portion, this object indicates the number of digits comprising the fractional portion. 3) A FlowMetricValue object, which indicates the value before scaling. (-1000000000..1000000000) · Integer32 · hint d

This object indicates the average loss duration for the traffic flow.

cfmRtpMetricsAvgLossDistance

1.3.6.1.4.1.9.9.703.1.1.1.1.11

Gauge32

This object indicates the average loss distance for the traffic flow.

cfmRtpMetricsJitterScale

1.3.6.1.4.1.9.9.703.1.1.1.1.12

FlowMetricScale1 = yocto2 = zepto3 = atto4 = femto5 = pico6 = nano7 = micro8 = milli9 = units10 = kilo11 = mega12 = giga13 = tera14 = exa15 = peta16 = zetta17 = yottaThis textual convention denotes an enumerated integer-value that represents an International System of Units (SI) prefix used as a scaling factor for fixed-point values: Prefix Scale Factor ========================= 'yocto' 10E-24 'zepto' 10E-21 'atto' 10E-18 'femto' 10E-15 'pico' 10E-12 'nano' 10E-9 'micro' 10E-6 'milli' 10E-3 'units' 10E0 'kilo' 10E3 'mega' 10E6 'giga' 10E9 'tera' 10E12 'exa' 10E15 'peta' 10E18 'zetta' 10E21 'yotta' 10E24 A MIB module may abstract a fixed-point value by defining three objects together: 1) A FlowMetricScale object, which indicates the scale of the value. 2) A FlowMetricPrecision object, which indicates the precision of the value. In the case that the value has a fractional portion, this object indicates the number of digits comprising the fractional portion. 3) A FlowMetricValue object, which indicates the value before scaling. · Integer32

This object indicates the scaling factor for the corresponding instance of cfmRtpMetricsJitter.

cfmRtpMetricsJitterPrecision

1.3.6.1.4.1.9.9.703.1.1.1.1.13

FlowMetricPrecisionThis textual convention denotes the precision or accuracy of a fixed-point value. A MIB module may abstract a fixed-point value by defining three objects together: 1) A FlowMetricScale object, which indicates the scale of the value. 2) A FlowMetricPrecision object, which indicates the precision of the value. In the case that the value has a fractional portion, this object indicates the number of digits comprising the fractional portion. 3) A FlowMetricValue object, which indicates the value before scaling. If an instance of an object of this type has a value in the range of 1 to 9, then it represents the precision of the associated value; that is, the number of decimal places in the fractional part of the associated value. For example, if the Media Loss Rate (MLR) computed for a traffic flow is 350.9E-6, then the FlowMetricScale object is 'micro', the FlowMetricPrecision object is 1, and the object indicating the value is 3509. If an instance of an object of this type has a value in the range of -8 to -1, then it represents the number of accurate digits in the associated value. For example, if the jitter measured for a traffic flow can range between -100,000 and 100,000 microseconds in 10 microsecond increments, with an accuracy of +/- 5 microseconds, the FlowMetricScale object is 'micro', the FlowMetricPrecision object is -2, and the object indicating the value has range of -100,000 to 100,000. (-8..-1 | 1..9) · Integer32 · hint d

This object indicates the precision for the corresponding instance of cfmRtpMetricsJitter.

cfmRtpMetricsJitter

1.3.6.1.4.1.9.9.703.1.1.1.1.14

FlowMetricValueThis textual convention denotes the value of a fixed-point value. A MIB module may abstract a fixed-point value by defining three objects together: 1) A FlowMetricScale object, which indicates the scale of the value. 2) A FlowMetricPrecision object, which indicates the precision of the value. In the case that the value has a fractional portion, this object indicates the number of digits comprising the fractional portion. 3) A FlowMetricValue object, which indicates the value before scaling. (-1000000000..1000000000) · Integer32 · hint d · seconds

This object indicates the inter-arrival jitter for the traffic flow.

cfmRtpMetricsIntTable

1.3.6.1.4.1.9.9.703.1.1.3

Index: cfmFlowMonitorId · cfmFlowId · cfmFlowMetricsIntNumber

This table contains historic RTP metrics for the traffic flows monitored by each of the flow monitors supported by the device. This table has an sparse dependent relationship on the cfmFlowMetricsIntTable (defined by the CISCO-FLOW-MONITOR-MIB), containing a row for each row in the cfmFlowMetricsIntTable having a corresponding instance of cfmFlowMetricsCollected with the 'rtp' bit set to one.

from CISCO-FLOW-MONITOR-MIB

cfmFlowMonitorId

FlowMonitorIdentifierThis textual convention denotes an arbitrary integer-value that uniquely identifies a flow monitor. (1..4294967295) · Unsigned32 · hint d

This object indicates an arbitrary integer-value that uniquely identifies the flow monitor. Observe that the value assigned to a flow monitor does not necessarily persist across restarts or the removal-insertion of a physical entity supporting flow monitor(s).

cfmFlowId

FlowIdentifierThis textual convention denotes an arbitrary integer-value that uniquely identifies a traffic flow within the scope of the flow monitor that collects data and periodically computes metrics for the traffic flow. (1..4294967295) · Unsigned32 · hint d

This object indicates an arbitrary integer-value that uniquely identifies a traffic flow in the scope of the flow monitor that learned it. Observe that the value assigned to a flow does not necessarily persist across restarts or the removal-insertion of a physical entity supporting flow monitor(s).

cfmFlowMetricsIntNumber

Unsigned32 (1..4294967295)

This object indicates the interval number identifying the measurement interval. The measurement interval identified by the value '1' represents the most recent measurement interval, and the interval identified by the value (n) represents the interval immediately preceding the interval identified by the value (n-1).

cfmRtpMetricsIntValid

1.3.6.1.4.1.9.9.703.1.1.3.1.1

BITS

This object indicates which metrics are valid for the measurement interval: 'expectedPkts' If this bit is set to '1', then the corresponding instance of cfmRtpMetricsIntExpectedPkts is valid. 'lostPkts' If this bit is set to '1', then the corresponding instance of cfmRtpMetricsIntLostPkts is valid. 'lossFraction' If this bit is set to '1', then the corresponding instances of cfmRtpMetricsIntFracScale, cfmRtpMetricsIntFracPrecision, and cfmRtpMetricsIntFrac are valid. 'lossIntervals' If this bit is set to '1', then the corresponding instance of cfmRtpMetricsIntLIs is valid. 'avgLossDuration' If this bit is set to '1', then the corresponding instances of cfmRtpMetricsIntAvgLDScale, cfmRtpMetricsIntAvgLDPrecision, and cfmRtpMetricsIntAvgLD are valid. 'avgLossDistance' If this bit is set to '1', then the corresponding instance of cfmRtpMetricsIntAvgLossDistance is valid. 'maxJitter' If this bit is set to '1', then the corresponding instances of cfmRtpMetricsIntJitterScale, cfmRtpMetricsIntJitterPrecision, and cfmRtpMetricsIntJitter are valid. 'maxMinTransit' If this bit is set to '1', then the corresponding instances of cfmRtpMetricsIntTransitScale, cfmRtpMetricsIntTransitPrecision, and cfmRtpMetricsIntTransit are valid.

cfmRtpMetricsIntExpectedPkts

1.3.6.1.4.1.9.9.703.1.1.3.1.2

ReportIntervalCountAn integer-value representing the value of a counter associated with the measurement taken during a previous report interval. An implementation supporting a history of N report intervals with IntervalCount(1) and IntervalCount(N) representing the most and least recent intervals, respectively, the following applies at the end of each report interval: - Discards the value of IntervalCount(N). - The value of IntervalCount(i) becomes that of IntervalCount(i-1) for N >= i > 1. - The value of IntervalCount(1) becomes that of CurrentCount. · Gauge32 · hint d · packets

This object indicates the number of RTP packets expected for the traffic flow during the measurement interval.

cfmRtpMetricsIntLostPkts

1.3.6.1.4.1.9.9.703.1.1.3.1.3

ReportIntervalCountAn integer-value representing the value of a counter associated with the measurement taken during a previous report interval. An implementation supporting a history of N report intervals with IntervalCount(1) and IntervalCount(N) representing the most and least recent intervals, respectively, the following applies at the end of each report interval: - Discards the value of IntervalCount(N). - The value of IntervalCount(i) becomes that of IntervalCount(i-1) for N >= i > 1. - The value of IntervalCount(1) becomes that of CurrentCount. · Gauge32 · hint d · packets

This object indicates the number of RTP packets lost for the traffic flow during the measurement interval.

cfmRtpMetricsIntFracScale

1.3.6.1.4.1.9.9.703.1.1.3.1.4

FlowMetricScale1 = yocto2 = zepto3 = atto4 = femto5 = pico6 = nano7 = micro8 = milli9 = units10 = kilo11 = mega12 = giga13 = tera14 = exa15 = peta16 = zetta17 = yottaThis textual convention denotes an enumerated integer-value that represents an International System of Units (SI) prefix used as a scaling factor for fixed-point values: Prefix Scale Factor ========================= 'yocto' 10E-24 'zepto' 10E-21 'atto' 10E-18 'femto' 10E-15 'pico' 10E-12 'nano' 10E-9 'micro' 10E-6 'milli' 10E-3 'units' 10E0 'kilo' 10E3 'mega' 10E6 'giga' 10E9 'tera' 10E12 'exa' 10E15 'peta' 10E18 'zetta' 10E21 'yotta' 10E24 A MIB module may abstract a fixed-point value by defining three objects together: 1) A FlowMetricScale object, which indicates the scale of the value. 2) A FlowMetricPrecision object, which indicates the precision of the value. In the case that the value has a fractional portion, this object indicates the number of digits comprising the fractional portion. 3) A FlowMetricValue object, which indicates the value before scaling. · Integer32

This object indicates the scaling factor for the corresponding instance of cfmRtpMetricsIntFrac.

cfmRtpMetricsIntFracPrecision

1.3.6.1.4.1.9.9.703.1.1.3.1.5

FlowMetricPrecisionThis textual convention denotes the precision or accuracy of a fixed-point value. A MIB module may abstract a fixed-point value by defining three objects together: 1) A FlowMetricScale object, which indicates the scale of the value. 2) A FlowMetricPrecision object, which indicates the precision of the value. In the case that the value has a fractional portion, this object indicates the number of digits comprising the fractional portion. 3) A FlowMetricValue object, which indicates the value before scaling. If an instance of an object of this type has a value in the range of 1 to 9, then it represents the precision of the associated value; that is, the number of decimal places in the fractional part of the associated value. For example, if the Media Loss Rate (MLR) computed for a traffic flow is 350.9E-6, then the FlowMetricScale object is 'micro', the FlowMetricPrecision object is 1, and the object indicating the value is 3509. If an instance of an object of this type has a value in the range of -8 to -1, then it represents the number of accurate digits in the associated value. For example, if the jitter measured for a traffic flow can range between -100,000 and 100,000 microseconds in 10 microsecond increments, with an accuracy of +/- 5 microseconds, the FlowMetricScale object is 'micro', the FlowMetricPrecision object is -2, and the object indicating the value has range of -100,000 to 100,000. (-8..-1 | 1..9) · Integer32 · hint d

This object indicates the precision for the corresponding instance of cfmRtpmetricsIntFrac.

cfmRtpMetricsIntFrac

1.3.6.1.4.1.9.9.703.1.1.3.1.6

FlowMetricValueThis textual convention denotes the value of a fixed-point value. A MIB module may abstract a fixed-point value by defining three objects together: 1) A FlowMetricScale object, which indicates the scale of the value. 2) A FlowMetricPrecision object, which indicates the precision of the value. In the case that the value has a fractional portion, this object indicates the number of digits comprising the fractional portion. 3) A FlowMetricValue object, which indicates the value before scaling. (-1000000000..1000000000) · Integer32 · hint d

This object indicates the loss fraction for traffic flow during the measurement interval.

cfmRtpMetricsIntLIs

1.3.6.1.4.1.9.9.703.1.1.3.1.7

ReportIntervalCountAn integer-value representing the value of a counter associated with the measurement taken during a previous report interval. An implementation supporting a history of N report intervals with IntervalCount(1) and IntervalCount(N) representing the most and least recent intervals, respectively, the following applies at the end of each report interval: - Discards the value of IntervalCount(N). - The value of IntervalCount(i) becomes that of IntervalCount(i-1) for N >= i > 1. - The value of IntervalCount(1) becomes that of CurrentCount. · Gauge32 · hint d

This object indicates the number of loss intervals for the traffic flow during the measurement interval.

cfmRtpMetricsIntAvgLDScale

1.3.6.1.4.1.9.9.703.1.1.3.1.8

FlowMetricScale1 = yocto2 = zepto3 = atto4 = femto5 = pico6 = nano7 = micro8 = milli9 = units10 = kilo11 = mega12 = giga13 = tera14 = exa15 = peta16 = zetta17 = yottaThis textual convention denotes an enumerated integer-value that represents an International System of Units (SI) prefix used as a scaling factor for fixed-point values: Prefix Scale Factor ========================= 'yocto' 10E-24 'zepto' 10E-21 'atto' 10E-18 'femto' 10E-15 'pico' 10E-12 'nano' 10E-9 'micro' 10E-6 'milli' 10E-3 'units' 10E0 'kilo' 10E3 'mega' 10E6 'giga' 10E9 'tera' 10E12 'exa' 10E15 'peta' 10E18 'zetta' 10E21 'yotta' 10E24 A MIB module may abstract a fixed-point value by defining three objects together: 1) A FlowMetricScale object, which indicates the scale of the value. 2) A FlowMetricPrecision object, which indicates the precision of the value. In the case that the value has a fractional portion, this object indicates the number of digits comprising the fractional portion. 3) A FlowMetricValue object, which indicates the value before scaling. · Integer32

This object indicates the scaling factor for the corresponding instance of cfmRtpMetricsIntAvgLD.

cfmRtpMetricsIntAvgLDPrecision

1.3.6.1.4.1.9.9.703.1.1.3.1.9

FlowMetricPrecisionThis textual convention denotes the precision or accuracy of a fixed-point value. A MIB module may abstract a fixed-point value by defining three objects together: 1) A FlowMetricScale object, which indicates the scale of the value. 2) A FlowMetricPrecision object, which indicates the precision of the value. In the case that the value has a fractional portion, this object indicates the number of digits comprising the fractional portion. 3) A FlowMetricValue object, which indicates the value before scaling. If an instance of an object of this type has a value in the range of 1 to 9, then it represents the precision of the associated value; that is, the number of decimal places in the fractional part of the associated value. For example, if the Media Loss Rate (MLR) computed for a traffic flow is 350.9E-6, then the FlowMetricScale object is 'micro', the FlowMetricPrecision object is 1, and the object indicating the value is 3509. If an instance of an object of this type has a value in the range of -8 to -1, then it represents the number of accurate digits in the associated value. For example, if the jitter measured for a traffic flow can range between -100,000 and 100,000 microseconds in 10 microsecond increments, with an accuracy of +/- 5 microseconds, the FlowMetricScale object is 'micro', the FlowMetricPrecision object is -2, and the object indicating the value has range of -100,000 to 100,000. (-8..-1 | 1..9) · Integer32 · hint d

This object indicates the precision for the corresponding instance of cfmRtpMetricsIntAvgLD.

cfmRtpMetricsIntAvgLD

1.3.6.1.4.1.9.9.703.1.1.3.1.10

FlowMetricValueThis textual convention denotes the value of a fixed-point value. A MIB module may abstract a fixed-point value by defining three objects together: 1) A FlowMetricScale object, which indicates the scale of the value. 2) A FlowMetricPrecision object, which indicates the precision of the value. In the case that the value has a fractional portion, this object indicates the number of digits comprising the fractional portion. 3) A FlowMetricValue object, which indicates the value before scaling. (-1000000000..1000000000) · Integer32 · hint d

This object indicates the average loss duration for the traffic flow during the measurement interval.

cfmRtpMetricsIntAvgLossDistance

1.3.6.1.4.1.9.9.703.1.1.3.1.11

ReportIntervalCountAn integer-value representing the value of a counter associated with the measurement taken during a previous report interval. An implementation supporting a history of N report intervals with IntervalCount(1) and IntervalCount(N) representing the most and least recent intervals, respectively, the following applies at the end of each report interval: - Discards the value of IntervalCount(N). - The value of IntervalCount(i) becomes that of IntervalCount(i-1) for N >= i > 1. - The value of IntervalCount(1) becomes that of CurrentCount. · Gauge32 · hint d

This object indicates the average loss distance for the traffic flow during the measurement interval.

cfmRtpMetricsIntJitterScale

1.3.6.1.4.1.9.9.703.1.1.3.1.12

FlowMetricScale1 = yocto2 = zepto3 = atto4 = femto5 = pico6 = nano7 = micro8 = milli9 = units10 = kilo11 = mega12 = giga13 = tera14 = exa15 = peta16 = zetta17 = yottaThis textual convention denotes an enumerated integer-value that represents an International System of Units (SI) prefix used as a scaling factor for fixed-point values: Prefix Scale Factor ========================= 'yocto' 10E-24 'zepto' 10E-21 'atto' 10E-18 'femto' 10E-15 'pico' 10E-12 'nano' 10E-9 'micro' 10E-6 'milli' 10E-3 'units' 10E0 'kilo' 10E3 'mega' 10E6 'giga' 10E9 'tera' 10E12 'exa' 10E15 'peta' 10E18 'zetta' 10E21 'yotta' 10E24 A MIB module may abstract a fixed-point value by defining three objects together: 1) A FlowMetricScale object, which indicates the scale of the value. 2) A FlowMetricPrecision object, which indicates the precision of the value. In the case that the value has a fractional portion, this object indicates the number of digits comprising the fractional portion. 3) A FlowMetricValue object, which indicates the value before scaling. · Integer32

This object indicates the scaling factor for the corresponding instance of cfmRtpMetricsIntJitter.

cfmRtpMetricsIntJitterPrecision

1.3.6.1.4.1.9.9.703.1.1.3.1.13

FlowMetricPrecisionThis textual convention denotes the precision or accuracy of a fixed-point value. A MIB module may abstract a fixed-point value by defining three objects together: 1) A FlowMetricScale object, which indicates the scale of the value. 2) A FlowMetricPrecision object, which indicates the precision of the value. In the case that the value has a fractional portion, this object indicates the number of digits comprising the fractional portion. 3) A FlowMetricValue object, which indicates the value before scaling. If an instance of an object of this type has a value in the range of 1 to 9, then it represents the precision of the associated value; that is, the number of decimal places in the fractional part of the associated value. For example, if the Media Loss Rate (MLR) computed for a traffic flow is 350.9E-6, then the FlowMetricScale object is 'micro', the FlowMetricPrecision object is 1, and the object indicating the value is 3509. If an instance of an object of this type has a value in the range of -8 to -1, then it represents the number of accurate digits in the associated value. For example, if the jitter measured for a traffic flow can range between -100,000 and 100,000 microseconds in 10 microsecond increments, with an accuracy of +/- 5 microseconds, the FlowMetricScale object is 'micro', the FlowMetricPrecision object is -2, and the object indicating the value has range of -100,000 to 100,000. (-8..-1 | 1..9) · Integer32 · hint d

This object indicates the precision for the corresponding instance of cfmRtpMetricsIntJitter.

cfmRtpMetricsIntJitter

1.3.6.1.4.1.9.9.703.1.1.3.1.14

FlowMetricValueThis textual convention denotes the value of a fixed-point value. A MIB module may abstract a fixed-point value by defining three objects together: 1) A FlowMetricScale object, which indicates the scale of the value. 2) A FlowMetricPrecision object, which indicates the precision of the value. In the case that the value has a fractional portion, this object indicates the number of digits comprising the fractional portion. 3) A FlowMetricValue object, which indicates the value before scaling. (-1000000000..1000000000) · Integer32 · hint d

This object indicates the maximum inter-arrival jitter for the traffic flow during the measurement interval.

cfmRtpMetricsIntTransitScale

1.3.6.1.4.1.9.9.703.1.1.3.1.15

FlowMetricScale1 = yocto2 = zepto3 = atto4 = femto5 = pico6 = nano7 = micro8 = milli9 = units10 = kilo11 = mega12 = giga13 = tera14 = exa15 = peta16 = zetta17 = yottaThis textual convention denotes an enumerated integer-value that represents an International System of Units (SI) prefix used as a scaling factor for fixed-point values: Prefix Scale Factor ========================= 'yocto' 10E-24 'zepto' 10E-21 'atto' 10E-18 'femto' 10E-15 'pico' 10E-12 'nano' 10E-9 'micro' 10E-6 'milli' 10E-3 'units' 10E0 'kilo' 10E3 'mega' 10E6 'giga' 10E9 'tera' 10E12 'exa' 10E15 'peta' 10E18 'zetta' 10E21 'yotta' 10E24 A MIB module may abstract a fixed-point value by defining three objects together: 1) A FlowMetricScale object, which indicates the scale of the value. 2) A FlowMetricPrecision object, which indicates the precision of the value. In the case that the value has a fractional portion, this object indicates the number of digits comprising the fractional portion. 3) A FlowMetricValue object, which indicates the value before scaling. · Integer32

This object indicates the scaling factor for the corresponding instance of cfmRtpMetricsIntTransit.

cfmRtpMetricsIntTransitPrecision

1.3.6.1.4.1.9.9.703.1.1.3.1.16

FlowMetricPrecisionThis textual convention denotes the precision or accuracy of a fixed-point value. A MIB module may abstract a fixed-point value by defining three objects together: 1) A FlowMetricScale object, which indicates the scale of the value. 2) A FlowMetricPrecision object, which indicates the precision of the value. In the case that the value has a fractional portion, this object indicates the number of digits comprising the fractional portion. 3) A FlowMetricValue object, which indicates the value before scaling. If an instance of an object of this type has a value in the range of 1 to 9, then it represents the precision of the associated value; that is, the number of decimal places in the fractional part of the associated value. For example, if the Media Loss Rate (MLR) computed for a traffic flow is 350.9E-6, then the FlowMetricScale object is 'micro', the FlowMetricPrecision object is 1, and the object indicating the value is 3509. If an instance of an object of this type has a value in the range of -8 to -1, then it represents the number of accurate digits in the associated value. For example, if the jitter measured for a traffic flow can range between -100,000 and 100,000 microseconds in 10 microsecond increments, with an accuracy of +/- 5 microseconds, the FlowMetricScale object is 'micro', the FlowMetricPrecision object is -2, and the object indicating the value has range of -100,000 to 100,000. (-8..-1 | 1..9) · Integer32 · hint d

This object indicates the precision for the corresponding instance of cfmRtpMetricsIntTransit.

cfmRtpMetricsIntTransit

1.3.6.1.4.1.9.9.703.1.1.3.1.17

FlowMetricValueThis textual convention denotes the value of a fixed-point value. A MIB module may abstract a fixed-point value by defining three objects together: 1) A FlowMetricScale object, which indicates the scale of the value. 2) A FlowMetricPrecision object, which indicates the precision of the value. In the case that the value has a fractional portion, this object indicates the number of digits comprising the fractional portion. 3) A FlowMetricValue object, which indicates the value before scaling. (-1000000000..1000000000) · Integer32 · hint d

This object indicates the max-min transit time for the traffic flow during the measurement interval. The max-min transit is the difference between the maximum and minimum transit times observed for RTP data packets during the measurement interval.

↑ To TOC