CISCO-RTP-METRICS-MIB
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.
- Source file
CISCO-RTP-METRICS-MIB- Last revised
- Identity
ciscoRtpMetricsMIB- Base OID
1.3.6.1.4.1.9.9.703
Imported Objects
| CISCO-FLOW-MONITOR-MIB | cfmFlowId cfmFlowMetricsIntNumber cfmFlowMonitorId |
| CISCO-FLOW-MONITOR-TC-MIB | FlowMetricPrecision FlowMetricScale FlowMetricValue |
| CISCO-REPORT-INTERVAL-TC-MIB | ReportIntervalCount |
| CISCO-SMI | ciscoMgmt |
| SNMPv2-CONF | MODULE-COMPLIANCE (no object page) OBJECT-GROUP (no object page) |
| SNMPv2-SMI | Counter64 Gauge32 MODULE-IDENTITY (no object page) OBJECT-IDENTITY (no object page) OBJECT-TYPE (no object page) |
| SNMPv2-TC | TimeStamp |
Net-SNMP examples using the cisco MIB directory Show commands
These commands use the standard Observium installation path and load the selected MIB variant before the RFC and Net-SNMP directories.
Translate the module identity
/usr/bin/snmptranslate -Pud -Ir -On -m 'CISCO-RTP-METRICS-MIB' -M '/opt/observium/mibs/cisco:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'CISCO-RTP-METRICS-MIB::ciscoRtpMetricsMIB'
Walk the MIB subtree
/usr/bin/snmpbulkwalk -v2c -c '<community>' -Pud -Ir -OQUs -m 'CISCO-RTP-METRICS-MIB' -M '/opt/observium/mibs/cisco:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'CISCO-RTP-METRICS-MIB::ciscoRtpMetricsMIB'
Objects (59)
Showing 59 of 59 objects
Object legend
Object type
Icons distinguish tables, entry rows, columns, scalars, and structural nodes.
SNMPv2-TCTruthValue
Syntax
Blue badges identify the value syntax. Connected badges read as defining module and convention.
IF-MIBifIndex
Table index
Green identifies an index object; yellow names its module when the index is defined elsewhere.
r/w
deprecated
obsolete
Access and status
r/w means read-write. Grey labels mark definitions retained for compatibility.
OBS ✓
Observium use
The indicator appears only when Observium directly references that object.
ifOperStatus
.1.3.6.1.2.1…
Names and OIDs
Object names link to their detail pages. Hover or focus a linked name or badge for available definition details.
.1.3.6.1.4.1.9.9.703 |
||
.1.3.6.1.4.1.9.9.703.0 |
||
.1.3.6.1.4.1.9.9.703.1 |
||
.1.3.6.1.4.1.9.9.703.1.1 |
||
.1.3.6.1.4.1.9.9.703.1.1.1 |
||
.1.3.6.1.4.1.9.9.703.1.1.1.1 |
||
|
Bits
|
.1.3.6.1.4.1.9.9.703.1.1.1.1.1 |
|
.1.3.6.1.4.1.9.9.703.1.1.1.1.10 |
||
.1.3.6.1.4.1.9.9.703.1.1.1.1.11 |
||
.1.3.6.1.4.1.9.9.703.1.1.1.1.12 |
||
.1.3.6.1.4.1.9.9.703.1.1.1.1.13 |
||
.1.3.6.1.4.1.9.9.703.1.1.1.1.14 |
||
|
packetsSNMPv2-SMICounter64
|
.1.3.6.1.4.1.9.9.703.1.1.1.1.2 |
|
|
packetsSNMPv2-SMICounter64
|
.1.3.6.1.4.1.9.9.703.1.1.1.1.3 |
|
.1.3.6.1.4.1.9.9.703.1.1.1.1.4 |
||
.1.3.6.1.4.1.9.9.703.1.1.1.1.5 |
||
.1.3.6.1.4.1.9.9.703.1.1.1.1.6 |
||
.1.3.6.1.4.1.9.9.703.1.1.1.1.7 |
||
.1.3.6.1.4.1.9.9.703.1.1.1.1.8 |
||
.1.3.6.1.4.1.9.9.703.1.1.1.1.9 |
||
.1.3.6.1.4.1.9.9.703.1.1.2 |
||
.1.3.6.1.4.1.9.9.703.1.1.3 |
||
.1.3.6.1.4.1.9.9.703.1.1.3.1 |
||
|
Bits
|
.1.3.6.1.4.1.9.9.703.1.1.3.1.1 |
|
.1.3.6.1.4.1.9.9.703.1.1.3.1.10 |
||
.1.3.6.1.4.1.9.9.703.1.1.3.1.11 |
||
.1.3.6.1.4.1.9.9.703.1.1.3.1.12 |
||
.1.3.6.1.4.1.9.9.703.1.1.3.1.13 |
||
.1.3.6.1.4.1.9.9.703.1.1.3.1.14 |
||
.1.3.6.1.4.1.9.9.703.1.1.3.1.15 |
||
.1.3.6.1.4.1.9.9.703.1.1.3.1.16 |
||
.1.3.6.1.4.1.9.9.703.1.1.3.1.17 |
||
.1.3.6.1.4.1.9.9.703.1.1.3.1.2 |
||
.1.3.6.1.4.1.9.9.703.1.1.3.1.3 |
||
.1.3.6.1.4.1.9.9.703.1.1.3.1.4 |
||
.1.3.6.1.4.1.9.9.703.1.1.3.1.5 |
||
.1.3.6.1.4.1.9.9.703.1.1.3.1.6 |
||
.1.3.6.1.4.1.9.9.703.1.1.3.1.7 |
||
.1.3.6.1.4.1.9.9.703.1.1.3.1.8 |
||
.1.3.6.1.4.1.9.9.703.1.1.3.1.9 |
||
.1.3.6.1.4.1.9.9.703.2 |
||
.1.3.6.1.4.1.9.9.703.2.1 |
||
.1.3.6.1.4.1.9.9.703.2.2 |
||
.1.3.6.1.4.1.9.9.703.3 |
||
.1.3.6.1.4.1.9.9.703.3.1 |
||
.1.3.6.1.4.1.9.9.703.3.1.1 |
||
.1.3.6.1.4.1.9.9.703.3.1.10 |
||
.1.3.6.1.4.1.9.9.703.3.1.11 |
||
.1.3.6.1.4.1.9.9.703.3.1.12 |
||
.1.3.6.1.4.1.9.9.703.3.1.13 |
||
.1.3.6.1.4.1.9.9.703.3.1.14 |
||
.1.3.6.1.4.1.9.9.703.3.1.2 |
||
.1.3.6.1.4.1.9.9.703.3.1.3 |
||
.1.3.6.1.4.1.9.9.703.3.1.4 |
||
.1.3.6.1.4.1.9.9.703.3.1.5 |
||
.1.3.6.1.4.1.9.9.703.3.1.6 |
||
.1.3.6.1.4.1.9.9.703.3.1.7 |
||
.1.3.6.1.4.1.9.9.703.3.1.8 |
||
.1.3.6.1.4.1.9.9.703.3.1.9 |
Dependencies (23) 7 direct · 16 transitive Show tree and compile order Hide dependency details
Each imported module is resolved in the importing module's source directory first, then through the normal default-variant rules.
Dependency tree
Dependency-first compile order
- SNMPv2-SMIrfc
- CISCO-SMIcisco
- SNMPv2-TCrfc
- CISCO-FLOW-MONITOR-TC-MIBcisco
- CISCO-REPORT-INTERVAL-TC-MIBcisco
- CISCO-TCcisco
- INET-ADDRESS-MIBrfc
- IANAifType-MIBrfc
- SNMPv2-CONFrfc
- SNMPv2-MIBrfc
- IF-MIBrfc
- BRIDGE-MIBrfc
- P-BRIDGE-MIBrfc
- RMON-MIBrfc
- RFC-1212rfc
- RFC1155-SMIrfc
- RFC1213-MIBrfc
- RFC1271-MIBrfc
- TOKEN-RING-RMON-MIBrfc
- RMON2-MIBrfc
- SNMP-FRAMEWORK-MIBrfc
- Q-BRIDGE-MIBrfc
- CISCO-FLOW-MONITOR-MIBcisco
- CISCO-RTP-METRICS-MIBciscoselected
Conformance Groups (1)
Compliance Statements (1)
OID
.1.3.6.1.4.1.9.9.703.2.1.1This compliance statement specifies the minimal requirements an
implementation must meet in order to claim full compliance with
the definition of the CISCO-RTP-METRICS-MIB.
implementation must meet in order to claim full compliance with
the definition of the CISCO-RTP-METRICS-MIB.
Required groups
| mandatory | cfmRtpMetricsGroup |