CISCO-MDI-METRICS-MIB

        This MIB module defines objects that describe the Media
Delivery Index (MDI).  The MDI [RFC4445] measurement describes
the quality indicator of a network intended to delivery
applications such as streaming media, MPEG video, VoIP, or other
information sensitive to arrival time and packet loss.
        
GLOSSARY
============
        
Delay Factor - the maximum observed value of the flow rate
    imbalance over a measurement interval.
        
DF - Delay Factor.
        
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.
        
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.
        
Media Loss Rate - the number of lost or out-of-order packets
    over a measurement interval.
        
Media Rate - the effective bit rate of the media content carried
by a traffic flow.
        
MLR - Media Loss Rate.
        
MR - Media Rate.
        
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.
        
VB - Virtual Buffer.
        
Virtual Buffer - a virtual buffer is a construct used to
    simulate a real buffer used by a media application for the
    purpose of storing media packets until the application can
    render their content.
        
REFERENCES
==============
        
[RFC4445]   J. Welch and J. Clark, 'A Proposed Media Delivery
            Index (MDI)', RFC-4445, April 2006.
    
Source file
CISCO-MDI-METRICS-MIB
Last revised
Identity
ciscoMdiMetricsMIB
Base OID
1.3.6.1.4.1.9.9.699
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-MDI-METRICS-MIB' -M '/opt/observium/mibs/cisco:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'CISCO-MDI-METRICS-MIB::ciscoMdiMetricsMIB'
Walk the MIB subtree
/usr/bin/snmpbulkwalk -v2c -c '<community>' -Pud -Ir -OQUs -m 'CISCO-MDI-METRICS-MIB' -M '/opt/observium/mibs/cisco:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'CISCO-MDI-METRICS-MIB::ciscoMdiMetricsMIB'
How SNMP, Net-SNMP, MIB paths, and variants work
Objects (44)
.1.3.6.1.4.1.9.9.699
.1.3.6.1.4.1.9.9.699.0
.1.3.6.1.4.1.9.9.699.1
.1.3.6.1.4.1.9.9.699.1.1
.1.3.6.1.4.1.9.9.699.1.1.1
.1.3.6.1.4.1.9.9.699.1.1.1.1
.1.3.6.1.4.1.9.9.699.1.1.1.1.1
.1.3.6.1.4.1.9.9.699.1.1.1.1.10
.1.3.6.1.4.1.9.9.699.1.1.1.1.2
Unsigned32
.1.3.6.1.4.1.9.9.699.1.1.1.1.3
octetsUnsigned32
.1.3.6.1.4.1.9.9.699.1.1.1.1.4
Bits
.1.3.6.1.4.1.9.9.699.1.1.1.1.5
.1.3.6.1.4.1.9.9.699.1.1.1.1.6
.1.3.6.1.4.1.9.9.699.1.1.1.1.7
.1.3.6.1.4.1.9.9.699.1.1.1.1.8
.1.3.6.1.4.1.9.9.699.1.1.1.1.9
.1.3.6.1.4.1.9.9.699.1.1.2
.1.3.6.1.4.1.9.9.699.1.1.3
.1.3.6.1.4.1.9.9.699.1.1.3.1
Bits
.1.3.6.1.4.1.9.9.699.1.1.3.1.1
.1.3.6.1.4.1.9.9.699.1.1.3.1.10
.1.3.6.1.4.1.9.9.699.1.1.3.1.11
.1.3.6.1.4.1.9.9.699.1.1.3.1.12
.1.3.6.1.4.1.9.9.699.1.1.3.1.13
.1.3.6.1.4.1.9.9.699.1.1.3.1.2
.1.3.6.1.4.1.9.9.699.1.1.3.1.3
.1.3.6.1.4.1.9.9.699.1.1.3.1.4
.1.3.6.1.4.1.9.9.699.1.1.3.1.5
.1.3.6.1.4.1.9.9.699.1.1.3.1.6
.1.3.6.1.4.1.9.9.699.1.1.3.1.7
.1.3.6.1.4.1.9.9.699.1.1.3.1.8
.1.3.6.1.4.1.9.9.699.1.1.3.1.9
.1.3.6.1.4.1.9.9.699.2
.1.3.6.1.4.1.9.9.699.2.1
.1.3.6.1.4.1.9.9.699.2.2
.1.3.6.1.4.1.9.9.699.3
.1.3.6.1.4.1.9.9.699.3.1
.1.3.6.1.4.1.9.9.699.3.1.1
.1.3.6.1.4.1.9.9.699.3.1.2
.1.3.6.1.4.1.9.9.699.3.1.3
.1.3.6.1.4.1.9.9.699.3.1.4
.1.3.6.1.4.1.9.9.699.3.1.5
.1.3.6.1.4.1.9.9.699.3.1.6
.1.3.6.1.4.1.9.9.699.3.1.7
Dependencies (23) 8 direct · 15 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
Compliance Statements (1)

OID .1.3.6.1.4.1.9.9.699.2.1.1
This compliance statement specifies the minimal requirements an
implementation must meet in order to claim full compliance with
the definition of the CISCO-MDI-METRICS-MIB.
Required groups