Home/Catalog/CISCO-MEDIATRACE-MIB

CISCO-MEDIATRACE-MIB

AI MIB Summary

The CISCO-MEDIATRACE-MIB manages the configuration and retrieval of hop-by-hop performance data for IP flows on Cisco devices acting as Mediatrace initiators or responders. It enables the collection of specific metrics including interface utilization, CPU and memory usage, packet loss, jitter, and route changes along a dynamically discovered path through configurable periodic monitoring sessions.

Mediatrace helps to isolate and troubleshoot network degradation problems by enabling a network administrator to discover an Internet Protocol (IP) flow's path, dynamically enable monitoring capabilities on the nodes along the path, and collect information on a hop-by-hop basis. This information includes, among other things, flow statistics, and utilization information for incoming and outgoing interfaces, CPUs, and memory, as well as any changes to IP routes. This information can be retrieved by configuring Cisco Mediatrace to start a recurring monitoring session at a specific time and on specific days. The session can be configured to specify which metrics to collect, and how frequently they are collected. The hops along the path are automatically discovered as part of the operation. This module defines a MIB for the features of configuring Mediatrace sessions and obtain statistics data for a particular hop at a specific time. INITIATOR/RESPONDER ==================== At the top level, this MIB module describes the initiator and responder roles for the device. The scalar objects corresponding to each role are used to enable and set parameters like maximum sessions supported, IP address used for enabling the initiator,etc. Some of the scalar objects are used to obtain information about a particular role for the device. At a time the device supports a single initiator and/or single responder. The following scalar objects are used for enabling the initiator, +-> cMTInitiatorEnable +-> cMTInitiatorSourceInterface +-> cMTInitiatorSourceAddressType +-> cMTInitiatorSourceAddress +-> cMTInitiatorMaxSessions In addition to the above objects, the following objects are used for obtaining information about the initiator role on the device, +-> cMTInitiatorSoftwareVersionMajor +-> cMTInitiatorSoftwareVersionMinor +-> cMTInitiatorProtocolVersionMajor +-> cMTInitiatorProtocolVersionMinor +-> cMTInitiatorConfiguredSessions +-> cMTInitiatorPendingSessions +-> cMTInitiatorInactiveSessions +-> cMTInitiatorActiveSessions The following scalar objects are used for enabling the responder, +-> cMTResponderEnable +-> cMTResponderMaxSessions In addition to the above objects, the following object is used for obtaining information about the responder role on the device, +-> cMTResponderActiveSessions CONTROL TABLES =============== At the next level, this MIB module describes the entities - path specifier, flow specifier, session params and profile. This section also includes the session and scheduling entities. Each row in the cMTSessionTable corresponds to a single session. The session is a container and hence the path specifier, flow specifier, session params and profile objects for each session point to the corresponding entities in the cMTPathSpecifierTable, cMTFlowSpecifierTable, cMTSessionParamsTable, cMTMediaMonitorProfileTable and cMTSystemProfileTable tables. o cMTPathSpecifierTable - describes path specifiers. o cMTFlowSpecifierTable - describes flow specifiers. o cMTSessionParamsTable - describes session params entities. o cMTMediaMonitorProfileTable - describes media monitor profile. o cMTSystemProfileTable - describes system profiles. The cMTSessionTable has a sparse dependent relationship with each of these tables, as there exist situations when data from those tables may not be used for a particular session, including : 1) The session using system profile does not need flow specifier. 2) The session using media monitor profile may not need optional flow specifier. 3) The session may only use one of the two profiles, system or media monitor. o cMTSessionTable - describes sessions. o cMTScheduleTable - describes scheduling entities for the sessions. The cMTScheduleTable has sparse dependent relationship on the cMTSessionTable, as there exist situations when the a session is not available for scheduling, including - a session is created but is not yet scheduled. + | cMTPathSpecifierTable| | | +-+ | cMTPathSpecifierName = ps1 | +-+ | | +-+ | cMTPathSpecifierName = ps2 | +-+ : : : : +-+ | cMTPathSpecifierName = ps6 | +-+ | | + + | cMTFlowSpecifierTable| | | +-+ | cMTFlowSpecifierName = fs1 | +-+ | | +-+ | cMTFlowSpecifierName = fs2 | +-+ : : : : +-+ | cMTFlowSpecifierName = fs6 | +-+ | | + +-+ + | cMTSessionTable | | cMTSessionParamsTable| | | | | +-+ + | cMTSessionNumber = 1 | |cMTSessionParamsName = sp1| | +-+ | + | |cMTSessionPathSpecifierName = ps1| | | | | +-+ | + | | |cMTSessionParamsName = sp2| | +-+ | + | |cMTSessionParamName = sp1 | | : : | +-+ | : : | | + | +-+ | |cMTSessionParamsName = sp5| | |cMTSessionProfileName = rtp1 | | + | +-+ | | | | | + | +-+ | | |cMTSessionFlowSpecifierName = fs1| | | +-+ | | | | +-+ | | |cMTSessionTraceRouteEnabled = T | | | +-+ | | | +-+ | | | | +-+ | cMTSessionNumber = 2 | | +-+ | + | |cMTSessionPathSpecifierName = ps2| | |cMTMediaMonitorProfileTable| | +-+ | | | | | +-+ | +-+ | |cMTMediaMonitorProfileName | | |cMTSessionParamName = sp5 | | | =rtp1 | | +-+ | +-+ | | | | | +-+ | +-+ | |cMTSessionProfileName = intf1 | | |cMTMediaMonitorProfileName | | +-+ | | =rtp1 | | | +-+ | +-+ | : : | |cMTSessionTraceRouteEnabled = T | | : : | +-+ | +-+ | | |cMTMediaMonitorProfileName | +-+ | =tcp1 | : : +-+ : : | | +-+ + | cMTSessionNumber = 10 | | +-+ | | |cMTSessionPathSpecifierName = ps1| | | +-+ | | | | +-+ | | |cMTSessionParamName = sp1 | | | +-+ | | | | +-+ | | |cMTSessionProfileName = tcp1 | | | +-+ | | | | +-+ | | |cMTSessionTraceRouteEnabled = T | | | +-+ | | | +-+ | | | | +-+ + | cMTSystemProfileTable| | | +-+ | cMTSystemProfileName = intf1| +-+ | | +-+ | cMTSystemProfileName = cpu1 | +-+ : : : : +-+ | cMTSystemProfileName = intf2| +-+ | | + DEFINITIONS =============== Mediatrace Initiator - This is the entity that supports creation of periodic sessions using global session id. Initiator can send request, collects the responses to those request and processes them for reporting. Henceforth, it will be referred as initiator. Mediatrace Responder - This is the entity that queries local database and features to obtain information based on the request sent by the Initiator as part of a session. The collected information is sent as response to the initiator to match the session. Henceforth, it will be referred as responder. Meta-data - Meta information about the flow not contained in the data packet. Examples of such information are global session id, multi party session id, type of application that is generating this flow e.g., telepresence. Meta-data global session identifier - it is one of the meta-data attributes which uniquely identifies a flow globally and is used to query the meta-data database for obtaining the corresponding 5-tuple (destination address, destination port, source address, source port and IP protocol) for path specifier or flow specifier. Path - This specifies the route taken by the Mediatrace request for a particular session. This can be specified in terms of single or multiple 5-tuple parameters - destination address, destination port, source address, source port and IP protocol. Gateway address and VLAN are required in cases where the path starts from network element without IP address. This is specified using path specifier entity. Path Specifier - The path specifier is generally specified using complete or partial 5-tuple (destination address, destination port, source address, source port and IP protocol) for Layer 3 initiator. Gateway and VLAN ID are required for a Layer 2 initiator. It can also use the meta-data Global session Id to specify the 5-tuple. A single row corresponds to a path specifier which is created or destroyed when a path specifier is added or removed. Each path specifier entry is uniquely identified by cMTPathSpecifierName. Examples of a path specifier are as follows, path-specifier (ps1)+ + + + + + + path-specifier (ps2)+ (345123456) 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. This is specified using a flow specifier entity. Flow Specifier - The flow specifier is generally specified using complete or partial 5-tuple (destination address, destination port, source address, source port and IP protocol). It can also use the meta-data Global session Id to specify the 5-tuple. A single row corresponds to a flow specifier which is created or destroyed when a flow specifier is added or removed. Each flow specifier entry is uniquely identified by cMTFlowSpecifierName. Examples of a flow specifier is as follows, flow-specifier (fs1)+ + + + + flow-specifier (fs2)+ (345123456) Metric - It defines a measurement that reflects the quality of a traffic flow or a resource on a hop or along the path e.g. number of packets for a flow, memory utilization on a hop, number of dropped packets on an interface, etc. Metric-list - It defines logical grouping of related metrics e.g. Metric-list CPU has 1% and 2% CPU utilization metric, Metric-list interface has ingress interface speed, egress interface speed, etc. Profile - It defines the set of metric-lists to be collected from the devices along the path. It can also include additional parameters which are required for collecting the metric e.g., sampling interval (also referred as monitor interval), etc. A Profile can include a set of related metric-lists along with related configuration parameters. The metrics could be the media monitoring (also referred as performance monitoring) metrics such as jitter, packet loss, bit rate etc., or system resource utilization metrics or interface counters. Two profiles, System profile and Media Monitoring (Performance Monitoring) Profile are supported. The different profiles, metric-lists and metrics are listed below, +-> Profile + | System | CPU | | | +> five min CPU utilization | | | + | | | +> octets input at ingress | Interface | | + | | | | at ingress | + | + | + | + | + | +> Metric-list +> loss of Media Monitor | TCP | IP | measurement confidence | | metrics | | | + | | + | | + | | + | | + | | + | | + | | + | | count | | | +> TCP connect round trip | specific | delay | metrics | | + | +> Common + RTP | IP | confidence | metrics | | + | + | + | + | + | + | + | + | +> RTP inter arrival jitter specific | delay metrics | + + + | count + Examples of the profiles are as follows, profile system - metric-list interface (sys1) profile media-monitor - metric-list rtp (rtp1) + (60 seconds) Session parameter Profile - These correspond to the various parameters related to session such as frequency of data collection, timeout for request, etc. These are specified using the session params entity. This is the entity that executes via a conceptual session/schedule control row and populates a conceptual statistics row. Example session parameter profile is as follows, Session-params (sp1)+ + + + + Session - The session is a grouping of various configurable entities such as profiles, session parameters and path specifiers. Flow specifier is optional and required for media monitor profile only. Once these parameters for a mediatrace session are defined through these entities, they are combined into a mediatrace session. Example of sessions are as follows, session (1) +> path-specifier (ps1) +> session-params (sp1) +> profile system (sys1) metric-list interface session (2) +> path-specifier (ps1) +> session-params (sp2) +> profile media-monitor (rtp1) | metric-list rtp +> flow-specifier (fs1) A session cycles through various states in its lifetime. The different states are, Active state : A session is said to be in active state when it is requesting and collecting data from the responders. Inactive state : A session becomes inactive when it is either stopped by unscheduling or life expires. In this state it will no longer collect or request data. Pending state: A session is in pending state when the session is created but not yet scheduled to be active. Based on the state and history of a session it can be classified as configured or scheduled session. Configured session : A session which is created and is in pending or inactive state is called a configured session. It can also be a newly created session which has not been scheduled (made active) yet. Scheduled session : A session which is in active state or pending state which is already requesting and collecting data or has set a time in future to start requesting or collecting data. Responder: The responder is in active state when it is able to process the requests from the initiator, collect the data locally and send the Response back to the initiator. Reachability Address: It is the address of the interface on a responder which is used to send the response to the initiator. Statistics row - This conceptual row is indexed based on the session index, session life index, bucket number and hop information (Hop address type and Hop address). This identifies the statistics for a particular session with specific life, at a particular time and for a specific hop.
Main OID:
ciscoMediatraceMIB.1.3.6.1.4.1.9.9.800
190
Objects
Active
Status
9
Dependencies

Imported Objects

Objects

190 total
Object Name
ciscoMediatraceMIB
MODULE-IDENTITY
.1.3.6.1.4.1.9.9.800
ciscoMediatraceMIBNotifs
OBJECT IDENTIFIER
.1.3.6.1.4.1.9.9.800.0
ciscoMediatraceMIBObjects
OBJECT IDENTIFIER
.1.3.6.1.4.1.9.9.800.1
cMTCtrl
OBJECT IDENTIFIER
.1.3.6.1.4.1.9.9.800.1.1
cMTInitiatorEnablerw
TruthValue (SNMPv2-TC)
.1.3.6.1.4.1.9.9.800.1.1.2
cMTInitiatorSourceInterfacerw
InterfaceIndexOrZero (IF-MIB)
.1.3.6.1.4.1.9.9.800.1.1.3
cMTInitiatorSourceAddressTyperw
InetAddressType (INET-ADDRESS-MIB)
.1.3.6.1.4.1.9.9.800.1.1.4
cMTInitiatorSourceAddressrw
InetAddress (INET-ADDRESS-MIB)
.1.3.6.1.4.1.9.9.800.1.1.5
cMTInitiatorMaxSessionsrw
Unsigned32
.1.3.6.1.4.1.9.9.800.1.1.6
cMTInitiatorSoftwareVersionMajorro
Unsigned32
.1.3.6.1.4.1.9.9.800.1.1.7
cMTInitiatorSoftwareVersionMinorro
Unsigned32
.1.3.6.1.4.1.9.9.800.1.1.8
cMTInitiatorProtocolVersionMajorro
Unsigned32
.1.3.6.1.4.1.9.9.800.1.1.9
cMTInitiatorProtocolVersionMinorro
Unsigned32
.1.3.6.1.4.1.9.9.800.1.1.10
cMTInitiatorConfiguredSessionsro
Gauge32
.1.3.6.1.4.1.9.9.800.1.1.11
cMTInitiatorPendingSessionsro
Gauge32
.1.3.6.1.4.1.9.9.800.1.1.12
cMTInitiatorInactiveSessionsro
Gauge32
.1.3.6.1.4.1.9.9.800.1.1.13
cMTInitiatorActiveSessionsro
Gauge32
.1.3.6.1.4.1.9.9.800.1.1.14
cMTResponderEnablerw
TruthValue (SNMPv2-TC)
.1.3.6.1.4.1.9.9.800.1.1.15
cMTResponderMaxSessionsrw
Unsigned32
.1.3.6.1.4.1.9.9.800.1.1.16
cMTResponderActiveSessionsro
Gauge32 UNITS "sessions"
.1.3.6.1.4.1.9.9.800.1.1.17
cMTFlowSpecifierTable
SEQUENCE OF CMTFlowSpecifierEntry
.1.3.6.1.4.1.9.9.800.1.1.18
cMTFlowSpecifierEntry
CMTFlowSpecifierEntry
.1.3.6.1.4.1.9.9.800.1.1.18.1
cMTFlowSpecifierName
SnmpAdminString (SNMP-FRAMEWORK-MIB)
.1.3.6.1.4.1.9.9.800.1.1.18.1.1
cMTFlowSpecifierRowStatusrw
RowStatus (SNMPv2-TC)
.1.3.6.1.4.1.9.9.800.1.1.18.1.2
cMTFlowSpecifierMetadataGlobalIdrw
SnmpAdminString (SNMP-FRAMEWORK-MIB)
.1.3.6.1.4.1.9.9.800.1.1.18.1.3
cMTFlowSpecifierDestAddrTyperw
InetAddressType (INET-ADDRESS-MIB)
.1.3.6.1.4.1.9.9.800.1.1.18.1.4
cMTFlowSpecifierDestAddrrw
InetAddress (INET-ADDRESS-MIB)
.1.3.6.1.4.1.9.9.800.1.1.18.1.5
cMTFlowSpecifierDestPortrw
InetPortNumber (INET-ADDRESS-MIB)
.1.3.6.1.4.1.9.9.800.1.1.18.1.6
cMTFlowSpecifierSourceAddrTyperw
InetAddressType (INET-ADDRESS-MIB)
.1.3.6.1.4.1.9.9.800.1.1.18.1.7
cMTFlowSpecifierSourceAddrrw
InetAddress (INET-ADDRESS-MIB)
.1.3.6.1.4.1.9.9.800.1.1.18.1.8
cMTFlowSpecifierSourcePortrw
InetPortNumber (INET-ADDRESS-MIB)
.1.3.6.1.4.1.9.9.800.1.1.18.1.9
cMTFlowSpecifierIpProtocolrw
CiscoMediatraceSupportProtocol
.1.3.6.1.4.1.9.9.800.1.1.18.1.10
cMTPathSpecifierTable
SEQUENCE OF CMTPathSpecifierEntry
.1.3.6.1.4.1.9.9.800.1.1.19
cMTPathSpecifierEntry
CMTPathSpecifierEntry
.1.3.6.1.4.1.9.9.800.1.1.19.1
cMTPathSpecifierName
SnmpAdminString (SNMP-FRAMEWORK-MIB)
.1.3.6.1.4.1.9.9.800.1.1.19.1.1
cMTPathSpecifierRowStatusrw
RowStatus (SNMPv2-TC)
.1.3.6.1.4.1.9.9.800.1.1.19.1.2
cMTPathSpecifierMetadataGlobalIdrw
SnmpAdminString (SNMP-FRAMEWORK-MIB)
.1.3.6.1.4.1.9.9.800.1.1.19.1.3
cMTPathSpecifierDestAddrTyperw
InetAddressType (INET-ADDRESS-MIB)
.1.3.6.1.4.1.9.9.800.1.1.19.1.4
cMTPathSpecifierDestAddrrw
InetAddress (INET-ADDRESS-MIB)
.1.3.6.1.4.1.9.9.800.1.1.19.1.5
cMTPathSpecifierDestPortrw
InetPortNumber (INET-ADDRESS-MIB)
.1.3.6.1.4.1.9.9.800.1.1.19.1.6
cMTPathSpecifierSourceAddrTyperw
InetAddressType (INET-ADDRESS-MIB)
.1.3.6.1.4.1.9.9.800.1.1.19.1.7
cMTPathSpecifierSourceAddrrw
InetAddress (INET-ADDRESS-MIB)
.1.3.6.1.4.1.9.9.800.1.1.19.1.8
cMTPathSpecifierSourcePortrw
InetPortNumber (INET-ADDRESS-MIB)
.1.3.6.1.4.1.9.9.800.1.1.19.1.9
cMTPathSpecifierProtocolForDiscoveryrw
CiscoMediatraceDiscoveryProtocol
.1.3.6.1.4.1.9.9.800.1.1.19.1.10
cMTPathSpecifierGatewayAddrTyperw
InetAddressType (INET-ADDRESS-MIB)
.1.3.6.1.4.1.9.9.800.1.1.19.1.11
cMTPathSpecifierGatewayAddrrw
InetAddress (INET-ADDRESS-MIB)
.1.3.6.1.4.1.9.9.800.1.1.19.1.12
cMTPathSpecifierGatewayVlanIdrw
VlanId
.1.3.6.1.4.1.9.9.800.1.1.19.1.13
cMTPathSpecifierIpProtocolrw
CiscoMediatraceSupportProtocol
.1.3.6.1.4.1.9.9.800.1.1.19.1.14
cMTSessionParamsTable
SEQUENCE OF CMTSessionParamsEntry
.1.3.6.1.4.1.9.9.800.1.1.20
cMTSessionParamsEntry
CMTSessionParamsEntry
.1.3.6.1.4.1.9.9.800.1.1.20.1
cMTSessionParamsName
SnmpAdminString (SNMP-FRAMEWORK-MIB)
.1.3.6.1.4.1.9.9.800.1.1.20.1.1
cMTSessionParamsRowStatusrw
RowStatus (SNMPv2-TC)
.1.3.6.1.4.1.9.9.800.1.1.20.1.2
cMTSessionParamsResponseTimeoutrw
Unsigned32
.1.3.6.1.4.1.9.9.800.1.1.20.1.3
cMTSessionParamsFrequencyrw
Unsigned32
.1.3.6.1.4.1.9.9.800.1.1.20.1.4
cMTSessionParamsInactivityTimeoutrw
Unsigned32
.1.3.6.1.4.1.9.9.800.1.1.20.1.5
cMTSessionParamsHistoryBucketsrw
Unsigned32
.1.3.6.1.4.1.9.9.800.1.1.20.1.6
cMTSessionParamsRouteChangeReactiontimerw
Unsigned32
.1.3.6.1.4.1.9.9.800.1.1.20.1.7
cMTMediaMonitorProfileTable
SEQUENCE OF CMTMediaMonitorProfileEntry
.1.3.6.1.4.1.9.9.800.1.1.21
cMTMediaMonitorProfileEntry
CMTMediaMonitorProfileEntry
.1.3.6.1.4.1.9.9.800.1.1.21.1
cMTMediaMonitorProfileName
SnmpAdminString (SNMP-FRAMEWORK-MIB)
.1.3.6.1.4.1.9.9.800.1.1.21.1.1
cMTMediaMonitorProfileRowStatusrw
RowStatus (SNMPv2-TC)
.1.3.6.1.4.1.9.9.800.1.1.21.1.2
cMTMediaMonitorProfileMetricrw
Enumeration
.1.3.6.1.4.1.9.9.800.1.1.21.1.3
cMTMediaMonitorProfileIntervalrw
Unsigned32
.1.3.6.1.4.1.9.9.800.1.1.21.1.4
cMTMediaMonitorProfileRtpMaxDropoutrw
Unsigned32
.1.3.6.1.4.1.9.9.800.1.1.21.1.5
cMTMediaMonitorProfileRtpMaxReorderrw
Unsigned32
.1.3.6.1.4.1.9.9.800.1.1.21.1.6
cMTMediaMonitorProfileRtpMinimalSequentialrw
Unsigned32
.1.3.6.1.4.1.9.9.800.1.1.21.1.7
cMTSystemProfileTable
SEQUENCE OF CMTSystemProfileEntry
.1.3.6.1.4.1.9.9.800.1.1.22
cMTSystemProfileEntry
CMTSystemProfileEntry
.1.3.6.1.4.1.9.9.800.1.1.22.1
cMTSystemProfileName
SnmpAdminString (SNMP-FRAMEWORK-MIB)
.1.3.6.1.4.1.9.9.800.1.1.22.1.1
cMTSystemProfileRowStatusrw
RowStatus (SNMPv2-TC)
.1.3.6.1.4.1.9.9.800.1.1.22.1.2
cMTSystemProfileMetricrw
Enumeration
.1.3.6.1.4.1.9.9.800.1.1.22.1.3
cMTSessionTable
SEQUENCE OF CMTSessionEntry
.1.3.6.1.4.1.9.9.800.1.1.23
cMTSessionEntry
CMTSessionEntry
.1.3.6.1.4.1.9.9.800.1.1.23.1
cMTSessionNumber
Unsigned32
.1.3.6.1.4.1.9.9.800.1.1.23.1.2
cMTSessionRowStatusrw
RowStatus (SNMPv2-TC)
.1.3.6.1.4.1.9.9.800.1.1.23.1.3
cMTSessionPathSpecifierNamerw
SnmpAdminString (SNMP-FRAMEWORK-MIB)
.1.3.6.1.4.1.9.9.800.1.1.23.1.4
cMTSessionParamNamerw
SnmpAdminString (SNMP-FRAMEWORK-MIB)
.1.3.6.1.4.1.9.9.800.1.1.23.1.5
cMTSessionProfileNamerw
SnmpAdminString (SNMP-FRAMEWORK-MIB)
.1.3.6.1.4.1.9.9.800.1.1.23.1.6
cMTSessionFlowSpecifierNamerw
SnmpAdminString (SNMP-FRAMEWORK-MIB)
.1.3.6.1.4.1.9.9.800.1.1.23.1.7
cMTSessionTraceRouteEnabledrw
TruthValue (SNMPv2-TC)
.1.3.6.1.4.1.9.9.800.1.1.23.1.8
cMTScheduleTable
SEQUENCE OF CMTScheduleEntry
.1.3.6.1.4.1.9.9.800.1.1.24
cMTScheduleEntry
CMTScheduleEntry
.1.3.6.1.4.1.9.9.800.1.1.24.1
cMTScheduleRowStatusrw
RowStatus (SNMPv2-TC)
.1.3.6.1.4.1.9.9.800.1.1.24.1.1
cMTScheduleStartTimerw
TimeStamp (SNMPv2-TC)
.1.3.6.1.4.1.9.9.800.1.1.24.1.2
cMTScheduleLiferw
Unsigned32
.1.3.6.1.4.1.9.9.800.1.1.24.1.3
cMTScheduleEntryAgeoutrw
Unsigned32
.1.3.6.1.4.1.9.9.800.1.1.24.1.4
cMTScheduleRecurringrw
TruthValue (SNMPv2-TC)
.1.3.6.1.4.1.9.9.800.1.1.24.1.5
cMTStats
OBJECT IDENTIFIER
.1.3.6.1.4.1.9.9.800.1.2
cMTPathTable
SEQUENCE OF CMTPathEntry
.1.3.6.1.4.1.9.9.800.1.2.1
cMTPathEntry
CMTPathEntry
.1.3.6.1.4.1.9.9.800.1.2.1.1
cMTSessionLifeNumber
Unsigned32
.1.3.6.1.4.1.9.9.800.1.2.1.1.1
cMTBucketNumber
Unsigned32
.1.3.6.1.4.1.9.9.800.1.2.1.1.2
cMTPathHopNumber
Unsigned32
.1.3.6.1.4.1.9.9.800.1.2.1.1.3
cMTPathHopAddrTypero
InetAddressType (INET-ADDRESS-MIB)
.1.3.6.1.4.1.9.9.800.1.2.1.1.4
cMTPathHopAddrro
InetAddress (INET-ADDRESS-MIB)
.1.3.6.1.4.1.9.9.800.1.2.1.1.5
cMTPathHopTypero
Enumeration
.1.3.6.1.4.1.9.9.800.1.2.1.1.6
cMTPathHopAlternate1AddrTypero
InetAddressType (INET-ADDRESS-MIB)
.1.3.6.1.4.1.9.9.800.1.2.1.1.7
cMTPathHopAlternate1Addrro
InetAddress (INET-ADDRESS-MIB)
.1.3.6.1.4.1.9.9.800.1.2.1.1.8
cMTPathHopAlternate2AddrTypero
InetAddressType (INET-ADDRESS-MIB)
.1.3.6.1.4.1.9.9.800.1.2.1.1.9
cMTPathHopAlternate2Addrro
InetAddress (INET-ADDRESS-MIB)
.1.3.6.1.4.1.9.9.800.1.2.1.1.10
Showing 100 of 190 OID objects

CISCO-MEDIATRACE-MIB Technical Reference Overview

The CISCO-MEDIATRACE-MIB SNMP MIB module published by Cisco defines 190 managed OID objects, including 150 scalar/column metrics, 17 SNMP tables, and 0 trap/notification events anchored at base OID .1.3.6.1.4.1.9.9.800. Key tabular structures include cMTFlowSpecifierTable, cMTPathSpecifierTable, cMTSessionParamsTable, cMTMediaMonitorProfileTable, cMTSystemProfileTable, cMTSessionTable.

Key OID Definitions in CISCO-MEDIATRACE-MIB

ciscoMediatraceMIBMODULE-IDENTITYnot-accessible
.1.3.6.1.4.1.9.9.800

Mediatrace helps to isolate and troubleshoot network degradation problems by enabling a network administrator to discover an Internet Protocol (IP) flow's path, dynamically enable monitoring capabilities on the nodes along the path, and collect information on a hop-by-hop basis. This information includes, among other things, flow statistics, and utilization information for incoming and outgoing interfaces, CPUs, and memory, as well as any changes to IP routes. This information can be retrieved by configuring Cisco Mediatrace to start a recurring monitoring session at a specific time and on specific days. The session can be configured to specify which metrics to collect, and how frequently they are collected. The hops along the path are automatically discovered as part of the operation. This module defines a MIB for the features of configuring Mediatrace sessions and obtain statistics data for a particular hop at a specific time. INITIATOR/RESPONDER ==================== At the top level, this MIB module describes the initiator and responder roles for the device. The scalar objects corresponding to each role are used to enable and set parameters like maximum sessions supported, IP address used for enabling the initiator,etc. Some of the scalar objects are used to obtain information about a particular role for the device. At a time the device supports a single initiator and/or single responder. The following scalar objects are used for enabling the initiator, +-> cMTInitiatorEnable +-> cMTInitiatorSourceInterface +-> cMTInitiatorSourceAddressType +-> cMTInitiatorSourceAddress +-> cMTInitiatorMaxSessions In addition to the above objects, the following objects are used for obtaining information about the initiator role on the device, +-> cMTInitiatorSoftwareVersionMajor +-> cMTInitiatorSoftwareVersionMinor +-> cMTInitiatorProtocolVersionMajor +-> cMTInitiatorProtocolVersionMinor +-> cMTInitiatorConfiguredSessions +-> cMTInitiatorPendingSessions +-> cMTInitiatorInactiveSessions +-> cMTInitiatorActiveSessions The following scalar objects are used for enabling the responder, +-> cMTResponderEnable +-> cMTResponderMaxSessions In addition to the above objects, the following object is used for obtaining information about the responder role on the device, +-> cMTResponderActiveSessions CONTROL TABLES =============== At the next level, this MIB module describes the entities - path specifier, flow specifier, session params and profile. This section also includes the session and scheduling entities. Each row in the cMTSessionTable corresponds to a single session. The session is a container and hence the path specifier, flow specifier, session params and profile objects for each session point to the corresponding entities in the cMTPathSpecifierTable, cMTFlowSpecifierTable, cMTSessionParamsTable, cMTMediaMonitorProfileTable and cMTSystemProfileTable tables. o cMTPathSpecifierTable - describes path specifiers. o cMTFlowSpecifierTable - describes flow specifiers. o cMTSessionParamsTable - describes session params entities. o cMTMediaMonitorProfileTable - describes media monitor profile. o cMTSystemProfileTable - describes system profiles. The cMTSessionTable has a sparse dependent relationship with each of these tables, as there exist situations when data from those tables may not be used for a particular session, including : 1) The session using system profile does not need flow specifier. 2) The session using media monitor profile may not need optional flow specifier. 3) The session may only use one of the two profiles, system or media monitor. o cMTSessionTable - describes sessions. o cMTScheduleTable - describes scheduling entities for the sessions. The cMTScheduleTable has sparse dependent relationship on the cMTSessionTable, as there exist situations when the a session is not available for scheduling, including - a session is created but is not yet scheduled. + | cMTPathSpecifierTable| | | +-+ | cMTPathSpecifierName = ps1 | +-+ | | +-+ | cMTPathSpecifierName = ps2 | +-+ : : : : +-+ | cMTPathSpecifierName = ps6 | +-+ | | + + | cMTFlowSpecifierTable| | | +-+ | cMTFlowSpecifierName = fs1 | +-+ | | +-+ | cMTFlowSpecifierName = fs2 | +-+ : : : : +-+ | cMTFlowSpecifierName = fs6 | +-+ | | + +-+ + | cMTSessionTable | | cMTSessionParamsTable| | | | | +-+ + | cMTSessionNumber = 1 | |cMTSessionParamsName = sp1| | +-+ | + | |cMTSessionPathSpecifierName = ps1| | | | | +-+ | + | | |cMTSessionParamsName = sp2| | +-+ | + | |cMTSessionParamName = sp1 | | : : | +-+ | : : | | + | +-+ | |cMTSessionParamsName = sp5| | |cMTSessionProfileName = rtp1 | | + | +-+ | | | | | + | +-+ | | |cMTSessionFlowSpecifierName = fs1| | | +-+ | | | | +-+ | | |cMTSessionTraceRouteEnabled = T | | | +-+ | | | +-+ | | | | +-+ | cMTSessionNumber = 2 | | +-+ | + | |cMTSessionPathSpecifierName = ps2| | |cMTMediaMonitorProfileTable| | +-+ | | | | | +-+ | +-+ | |cMTMediaMonitorProfileName | | |cMTSessionParamName = sp5 | | | =rtp1 | | +-+ | +-+ | | | | | +-+ | +-+ | |cMTSessionProfileName = intf1 | | |cMTMediaMonitorProfileName | | +-+ | | =rtp1 | | | +-+ | +-+ | : : | |cMTSessionTraceRouteEnabled = T | | : : | +-+ | +-+ | | |cMTMediaMonitorProfileName | +-+ | =tcp1 | : : +-+ : : | | +-+ + | cMTSessionNumber = 10 | | +-+ | | |cMTSessionPathSpecifierName = ps1| | | +-+ | | | | +-+ | | |cMTSessionParamName = sp1 | | | +-+ | | | | +-+ | | |cMTSessionProfileName = tcp1 | | | +-+ | | | | +-+ | | |cMTSessionTraceRouteEnabled = T | | | +-+ | | | +-+ | | | | +-+ + | cMTSystemProfileTable| | | +-+ | cMTSystemProfileName = intf1| +-+ | | +-+ | cMTSystemProfileName = cpu1 | +-+ : : : : +-+ | cMTSystemProfileName = intf2| +-+ | | + DEFINITIONS =============== Mediatrace Initiator - This is the entity that supports creation of periodic sessions using global session id. Initiator can send request, collects the responses to those request and processes them for reporting. Henceforth, it will be referred as initiator. Mediatrace Responder - This is the entity that queries local database and features to obtain information based on the request sent by the Initiator as part of a session. The collected information is sent as response to the initiator to match the session. Henceforth, it will be referred as responder. Meta-data - Meta information about the flow not contained in the data packet. Examples of such information are global session id, multi party session id, type of application that is generating this flow e.g., telepresence. Meta-data global session identifier - it is one of the meta-data attributes which uniquely identifies a flow globally and is used to query the meta-data database for obtaining the corresponding 5-tuple (destination address, destination port, source address, source port and IP protocol) for path specifier or flow specifier. Path - This specifies the route taken by the Mediatrace request for a particular session. This can be specified in terms of single or multiple 5-tuple parameters - destination address, destination port, source address, source port and IP protocol. Gateway address and VLAN are required in cases where the path starts from network element without IP address. This is specified using path specifier entity. Path Specifier - The path specifier is generally specified using complete or partial 5-tuple (destination address, destination port, source address, source port and IP protocol) for Layer 3 initiator. Gateway and VLAN ID are required for a Layer 2 initiator. It can also use the meta-data Global session Id to specify the 5-tuple. A single row corresponds to a path specifier which is created or destroyed when a path specifier is added or removed. Each path specifier entry is uniquely identified by cMTPathSpecifierName. Examples of a path specifier are as follows, path-specifier (ps1)+ + + + + + + path-specifier (ps2)+ (345123456) 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. This is specified using a flow specifier entity. Flow Specifier - The flow specifier is generally specified using complete or partial 5-tuple (destination address, destination port, source address, source port and IP protocol). It can also use the meta-data Global session Id to specify the 5-tuple. A single row corresponds to a flow specifier which is created or destroyed when a flow specifier is added or removed. Each flow specifier entry is uniquely identified by cMTFlowSpecifierName. Examples of a flow specifier is as follows, flow-specifier (fs1)+ + + + + flow-specifier (fs2)+ (345123456) Metric - It defines a measurement that reflects the quality of a traffic flow or a resource on a hop or along the path e.g. number of packets for a flow, memory utilization on a hop, number of dropped packets on an interface, etc. Metric-list - It defines logical grouping of related metrics e.g. Metric-list CPU has 1% and 2% CPU utilization metric, Metric-list interface has ingress interface speed, egress interface speed, etc. Profile - It defines the set of metric-lists to be collected from the devices along the path. It can also include additional parameters which are required for collecting the metric e.g., sampling interval (also referred as monitor interval), etc. A Profile can include a set of related metric-lists along with related configuration parameters. The metrics could be the media monitoring (also referred as performance monitoring) metrics such as jitter, packet loss, bit rate etc., or system resource utilization metrics or interface counters. Two profiles, System profile and Media Monitoring (Performance Monitoring) Profile are supported. The different profiles, metric-lists and metrics are listed below, +-> Profile + | System | CPU | | | +> five min CPU utilization | | | + | | | +> octets input at ingress | Interface | | + | | | | at ingress | + | + | + | + | + | +> Metric-list +> loss of Media Monitor | TCP | IP | measurement confidence | | metrics | | | + | | + | | + | | + | | + | | + | | + | | + | | count | | | +> TCP connect round trip | specific | delay | metrics | | + | +> Common + RTP | IP | confidence | metrics | | + | + | + | + | + | + | + | + | +> RTP inter arrival jitter specific | delay metrics | + + + | count + Examples of the profiles are as follows, profile system - metric-list interface (sys1) profile media-monitor - metric-list rtp (rtp1) + (60 seconds) Session parameter Profile - These correspond to the various parameters related to session such as frequency of data collection, timeout for request, etc. These are specified using the session params entity. This is the entity that executes via a conceptual session/schedule control row and populates a conceptual statistics row. Example session parameter profile is as follows, Session-params (sp1)+ + + + + Session - The session is a grouping of various configurable entities such as profiles, session parameters and path specifiers. Flow specifier is optional and required for media monitor profile only. Once these parameters for a mediatrace session are defined through these entities, they are combined into a mediatrace session. Example of sessions are as follows, session (1) +> path-specifier (ps1) +> session-params (sp1) +> profile system (sys1) metric-list interface session (2) +> path-specifier (ps1) +> session-params (sp2) +> profile media-monitor (rtp1) | metric-list rtp +> flow-specifier (fs1) A session cycles through various states in its lifetime. The different states are, Active state : A session is said to be in active state when it is requesting and collecting data from the responders. Inactive state : A session becomes inactive when it is either stopped by unscheduling or life expires. In this state it will no longer collect or request data. Pending state: A session is in pending state when the session is created but not yet scheduled to be active. Based on the state and history of a session it can be classified as configured or scheduled session. Configured session : A session which is created and is in pending or inactive state is called a configured session. It can also be a newly created session which has not been scheduled (made active) yet. Scheduled session : A session which is in active state or pending state which is already requesting and collecting data or has set a time in future to start requesting or collecting data. Responder: The responder is in active state when it is able to process the requests from the initiator, collect the data locally and send the Response back to the initiator. Reachability Address: It is the address of the interface on a responder which is used to send the response to the initiator. Statistics row - This conceptual row is indexed based on the session index, session life index, bucket number and hop information (Hop address type and Hop address). This identifies the statistics for a particular session with specific life, at a particular time and for a specific hop.

cMTFlowSpecifierTableSEQUENCEnot-accessible
.1.3.6.1.4.1.9.9.800.1.1.18

This table lists the flow specifiers contained by the device.

cMTPathSpecifierTableSEQUENCEnot-accessible
.1.3.6.1.4.1.9.9.800.1.1.19

This table lists the path specifiers contained by the device.

cMTSessionParamsTableSEQUENCEnot-accessible
.1.3.6.1.4.1.9.9.800.1.1.20

This table is collection of session parameter profiles.

cMTMediaMonitorProfileTableSEQUENCEnot-accessible
.1.3.6.1.4.1.9.9.800.1.1.21

This table lists the media monitor profiles configured on the device.

cMTSystemProfileTableSEQUENCEnot-accessible
.1.3.6.1.4.1.9.9.800.1.1.22

This table lists the system profiles configured on the device.

cMTSessionTableSEQUENCEnot-accessible
.1.3.6.1.4.1.9.9.800.1.1.23

This table lists the Mediatrace sessions configured on the device.

cMTScheduleTableSEQUENCEnot-accessible
.1.3.6.1.4.1.9.9.800.1.1.24

A table of Mediatrace scheduling specific definitions. Each entry in this table schedules a cMTSessionEntry created via the cMTSessionTable object.

cMTPathTableSEQUENCEnot-accessible
.1.3.6.1.4.1.9.9.800.1.2.1

List of paths discovered by a mediatrace session.

cMTHopStatsTableSEQUENCEnot-accessible
.1.3.6.1.4.1.9.9.800.1.2.2

An entry in cMTHopStatsTable represents a hop on the path associated to a Mediatrace session. This table contains information about particular hop (Mediatrace or non-Mediatrace) such as the address, type of hop, etc. A single row corresponds to a hop on the Mediatrace path discovered for a session and is uniquely identified by cMTSessionNumber, cMTSessionLifeNumber, cMTBucketNumber,cMTHopStatsAddrType and cMTHopStatsAddr. The created rows are destroyed when the device undergoes a restart.

cMTTraceRouteTableSEQUENCEnot-accessible
.1.3.6.1.4.1.9.9.800.1.2.3

This table lists the hops discovered by traceroute executed from the initiator. These are the hops which are on media flow path but on which mediatrace is not enabled or is not supported.

cMTSessionStatusTableSEQUENCEnot-accessible
.1.3.6.1.4.1.9.9.800.1.2.4

This table contains aggregate data maintained by Mediatrace for session status.

cMTSessionRequestStatsTableSEQUENCEnot-accessible
.1.3.6.1.4.1.9.9.800.1.2.5

This table contains aggregate data maintained by Mediatrace for session request status.

cMTCommonMetricStatsTableSEQUENCEnot-accessible
.1.3.6.1.4.1.9.9.800.1.2.6

This table contains the list of entries representing common IP metrics values for a particular mediatrace session on particular hop.

cMTRtpMetricStatsTableSEQUENCEnot-accessible
.1.3.6.1.4.1.9.9.800.1.2.7

This table contains aggregate data maintained by Mediatrace for traffic flows for which it is computing RTP metrics.

cMTTcpMetricStatsTableSEQUENCEnot-accessible
.1.3.6.1.4.1.9.9.800.1.2.8

This table contains aggregate data maintained by Mediatrace for traffic flows for which it is computing TCP metrics.

cMTSystemMetricStatsTableSEQUENCEnot-accessible
.1.3.6.1.4.1.9.9.800.1.2.9

A list of objects which accumulate the system metrics results of a particular node for that path.

cMTInterfaceMetricStatsTableSEQUENCEnot-accessible
.1.3.6.1.4.1.9.9.800.1.2.10

This table contains aggregate data of interface information for the network nodes.

cMTInitiatorEnableTruthValueread-write
.1.3.6.1.4.1.9.9.800.1.1.2

This object specifies the whether the Mediatrace initiator is enabled on the network element.

cMTInitiatorSourceInterfaceInterfaceIndexOrZeroread-write
.1.3.6.1.4.1.9.9.800.1.1.3

This object specifies the interface whose IP or IPv6 address will be used as initiator address. The Initiator address is used by layer 2 mediatrace responder to unicast the response message to initiator. This address is also reachability address for mediatrace hop 0. The value of this object should be set to ifIndex value of the desired interface from the ifTable.

cMTInitiatorSourceAddressTypeInetAddressTyperead-write
.1.3.6.1.4.1.9.9.800.1.1.4

Address type (IP or IPv6) of the initiator address specified in cMTInitiatorSourceAddress object. The value should be set to unknown (0) if source interface object is non zero.

cMTInitiatorSourceAddressInetAddressread-write
.1.3.6.1.4.1.9.9.800.1.1.5

This object specifies the IP address used by the initiator when obtaining the reachability address from a downstream responder.

cMTInitiatorMaxSessionsUnsigned32read-write
.1.3.6.1.4.1.9.9.800.1.1.6

This object specifies the maximum number of mediatrace sessions that can be active simultaneously on the initiator.

cMTInitiatorSoftwareVersionMajorUnsigned32read-only
.1.3.6.1.4.1.9.9.800.1.1.7

This object indicates the major version number of Mediatrace application.

More MIBs from Cisco

Browse all CiscoMIBs →
CISCO-UNIFIED-COMPUTING-COMPUTE-MIB

The CISCO-UNIFIED-COMPUTING-COMPUTE-MIB provides SNMP-based monitoring and management of Cisco UCS compute blades, servers, and chassis components, exposing critical metrics such as CPU utilization, memory usage, thermal sensor readings, power supply status, and interface operational states. This module enables granular visibility into the health and performance of the Cisco Unified Computing System's compute subsystems for capacity planning and fault isolation.

1401 objects→
CISCO-UNIFIED-COMPUTING-STORAGE-MIB

The CISCO-UNIFIED-COMPUTING-STORAGE-MIB facilitates SNMP-based monitoring and management of storage subsystems, including Fibre Channel and iSCSI interfaces, within the Cisco Unified Computing System (UCS) fabric interconnects and blade servers. It exposes critical operational metrics such as port status, error counters, throughput statistics, and storage controller health states to enable granular visibility into the storage infrastructure.

1295 objects→
CISCO-UNIFIED-COMPUTING-VNIC-MIB

The CISCO-UNIFIED-COMPUTING-VNIC-MIB enables SNMP-based monitoring and management of Virtual Network Interface Card (vNIC) attributes, including operational status, traffic counters, and binding configurations, within the Cisco Unified Computing System (UCS) fabric interconnects and server blades.

1161 objects→
CERENT-GENERIC-MIB

SNMP MIB module

984 objects→
CISCO-UNIFIED-COMPUTING-BIOS-MIB

The CISCO-UNIFIED-COMPUTING-BIOS-MIB enables SNMP-based monitoring and configuration of BIOS-level parameters, firmware versions, and hardware initialization states within Cisco Unified Computing System (UCS) servers. It provides visibility into critical server boot diagnostics, BIOS settings, and hardware readiness indicators to facilitate low-level infrastructure management and troubleshooting.

937 objects→
CISCO-UNIFIED-COMPUTING-ETHER-MIB

The CISCO-UNIFIED-COMPUTING-ETHER-MIB provides SNMP management interfaces for monitoring Ethernet interface statistics, link states, and error counters on Cisco Unified Computing System (UCS) fabric interconnects and blade server line cards. This module enables the tracking of physical layer connectivity, port throughput, and packet error rates within the UCS Ethernet switching infrastructure.

920 objects→