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 |
|---|
ciscoMediatraceMIBMediatrace 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. 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 |
cMTInitiatorEnableThis object specifies the whether the Mediatrace initiator
is enabled on the network element.rw TruthValue (SNMPv2-TC) .1.3.6.1.4.1.9.9.800.1.1.2 |
cMTInitiatorSourceInterfaceThis 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.rw InterfaceIndexOrZero (IF-MIB) .1.3.6.1.4.1.9.9.800.1.1.3 |
cMTInitiatorSourceAddressTypeAddress 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.rw InetAddressType (INET-ADDRESS-MIB) .1.3.6.1.4.1.9.9.800.1.1.4 |
cMTInitiatorSourceAddressThis object specifies the IP address used by the initiator
when obtaining the reachability address from a downstream
responder.rw InetAddress (INET-ADDRESS-MIB) .1.3.6.1.4.1.9.9.800.1.1.5 |
cMTInitiatorMaxSessionsThis object specifies the maximum number of mediatrace
sessions that can be active simultaneously on the initiator.rw Unsigned32 .1.3.6.1.4.1.9.9.800.1.1.6 |
cMTInitiatorSoftwareVersionMajorThis object indicates the major version number of Mediatrace
application.ro Unsigned32 .1.3.6.1.4.1.9.9.800.1.1.7 |
cMTInitiatorSoftwareVersionMinorThis object indicates the minor version number of Mediatrace
application.ro Unsigned32 .1.3.6.1.4.1.9.9.800.1.1.8 |
cMTInitiatorProtocolVersionMajorThis object indicates the major version number of Mediatrace
protocol.ro Unsigned32 .1.3.6.1.4.1.9.9.800.1.1.9 |
cMTInitiatorProtocolVersionMinorThis object indicates the minor version number of Mediatrace
protocol.ro Unsigned32 .1.3.6.1.4.1.9.9.800.1.1.10 |
cMTInitiatorConfiguredSessionsThis object indicates number of mediatrace sessions configured.
The session may or may not be active.ro Gauge32 .1.3.6.1.4.1.9.9.800.1.1.11 |
cMTInitiatorPendingSessionsThis object indicates the current number of sessions in pending
state on the initiator.ro Gauge32 .1.3.6.1.4.1.9.9.800.1.1.12 |
cMTInitiatorInactiveSessionsThis object indicates the current number of sessions in
inactive state on the initiator.ro Gauge32 .1.3.6.1.4.1.9.9.800.1.1.13 |
cMTInitiatorActiveSessionsThis object indicates the current number of sessions in
active state on the initiator.ro Gauge32 .1.3.6.1.4.1.9.9.800.1.1.14 |
cMTResponderEnableThis object specifies the whether the Mediatrace responder
is enabled.
If set to 'true' the responder will be enabled. If set to
false then mediatrace responder process will be stopped and
the device will no longer be discovered as mediatrace capable
hop along the flow path.rw TruthValue (SNMPv2-TC) .1.3.6.1.4.1.9.9.800.1.1.15 |
cMTResponderMaxSessionsThis object specifies the maximum number of sessions that
a responder can accept from initiator.rw Unsigned32 .1.3.6.1.4.1.9.9.800.1.1.16 |
cMTResponderActiveSessionsThis object indicates the current number of sessions that are
in active state on the responder.ro Gauge32 UNITS "sessions" .1.3.6.1.4.1.9.9.800.1.1.17 |
cMTFlowSpecifierTableThis table lists the flow specifiers contained by the device. SEQUENCE OF CMTFlowSpecifierEntry .1.3.6.1.4.1.9.9.800.1.1.18 |
cMTFlowSpecifierEntryAn entry represents a flow specifier which can be
associated with a Mediatrace session contained by the
cMTSessionTable.
Each entry is uniquely identified by name specified
by cMTFlowSpecifierName object. A row created in this
table will be shown in 'show running' command and it
will not be saved into non-volatile memory. CMTFlowSpecifierEntry .1.3.6.1.4.1.9.9.800.1.1.18.1 |
cMTFlowSpecifierNameA unique identifier for the flow specifier. SnmpAdminString (SNMP-FRAMEWORK-MIB) .1.3.6.1.4.1.9.9.800.1.1.18.1.1 |
cMTFlowSpecifierRowStatusThis object specifies the status of the flow specifier.
Only CreateAndGo and active status is supported. The
following columns must be valid before activating the
flow specifier:
- cMTFlowSpecifierDestAddrType and cMTFlowSpecifierDestAddr OR
- cMTFlowSpecifierMetadataGlobalId
All other objects can assume default values.
Once the flow specifier is activated no column can be modified.
Setting this object to 'delete' will destroy the flow specifier.
The flow specifier can be deleted only if it is not attached to
any session.rw RowStatus (SNMPv2-TC) .1.3.6.1.4.1.9.9.800.1.1.18.1.2 |
cMTFlowSpecifierMetadataGlobalIdThis object specifies the meta-data Global ID of the
flow specifier. Maximum of 24 characters can be
specified for this field.rw SnmpAdminString (SNMP-FRAMEWORK-MIB) .1.3.6.1.4.1.9.9.800.1.1.18.1.3 |
cMTFlowSpecifierDestAddrTypeThis object specifies the type of IP address specified by
the corresponding instance of cMTFlowSpecifierDestAddr.rw InetAddressType (INET-ADDRESS-MIB) .1.3.6.1.4.1.9.9.800.1.1.18.1.4 |
cMTFlowSpecifierDestAddrAddress of the destination of the flow to be monitored.rw InetAddress (INET-ADDRESS-MIB) .1.3.6.1.4.1.9.9.800.1.1.18.1.5 |
cMTFlowSpecifierDestPortThis object specifies the destination port for the flow.rw InetPortNumber (INET-ADDRESS-MIB) .1.3.6.1.4.1.9.9.800.1.1.18.1.6 |
cMTFlowSpecifierSourceAddrTypeThis object specifies the type of IP address specified by
the corresponding instance of cMTFlowSpecifierSourceAddr.rw InetAddressType (INET-ADDRESS-MIB) .1.3.6.1.4.1.9.9.800.1.1.18.1.7 |
cMTFlowSpecifierSourceAddrThis object specifies the source address for the
flow to be monitored.rw InetAddress (INET-ADDRESS-MIB) .1.3.6.1.4.1.9.9.800.1.1.18.1.8 |
cMTFlowSpecifierSourcePortThis object specifies the source port for the flow.rw InetPortNumber (INET-ADDRESS-MIB) .1.3.6.1.4.1.9.9.800.1.1.18.1.9 |
cMTFlowSpecifierIpProtocolThis is transport protocol type for the flow. Flow of this
type between specified source and and destination will be
monitored.rw CiscoMediatraceSupportProtocol .1.3.6.1.4.1.9.9.800.1.1.18.1.10 |
cMTPathSpecifierTableThis table lists the path specifiers contained by the device. SEQUENCE OF CMTPathSpecifierEntry .1.3.6.1.4.1.9.9.800.1.1.19 |
cMTPathSpecifierEntryThis entry defines path specifier that can be used in
mediatrace session.
Each entry is uniquely identified by name specified
by cMTPathSpecifierName object. A row created in this
table will be shown in 'show running' command and it will
not be saved into non-volatile memory. CMTPathSpecifierEntry .1.3.6.1.4.1.9.9.800.1.1.19.1 |
cMTPathSpecifierNameA unique identifier for the path specifier. SnmpAdminString (SNMP-FRAMEWORK-MIB) .1.3.6.1.4.1.9.9.800.1.1.19.1.1 |
cMTPathSpecifierRowStatusThis object specifies the status of the path specifier.
Only CreateAndGo and active status is supported. The
following columns must be valid before activating the
path specifier:
- cMTPathSpecifierDestAddrType and cMTPathSpecifierDestAddr OR
- cMTPathSpecifierMetadataGlobalId
All other objects can assume default values.
Once the path specifier is activated no column can be modified.
Setting this object to 'delete' will destroy the path specifier.
The path specifier can be deleted only if it is not attached to
any session.rw RowStatus (SNMPv2-TC) .1.3.6.1.4.1.9.9.800.1.1.19.1.2 |
cMTPathSpecifierMetadataGlobalIdMetadata global session id can be used as path specifier.
This object should be populated when this is desired.
Mediatrace software will query the Metadata database for
five tuple to be used for establishing the path.rw SnmpAdminString (SNMP-FRAMEWORK-MIB) .1.3.6.1.4.1.9.9.800.1.1.19.1.3 |
cMTPathSpecifierDestAddrTypeThis object specifies the type of IP address specified by
the corresponding instance of cMTPathSpecifierDestAddr.rw InetAddressType (INET-ADDRESS-MIB) .1.3.6.1.4.1.9.9.800.1.1.19.1.4 |
cMTPathSpecifierDestAddrThis object specifies the destination address for
the path specifier.rw InetAddress (INET-ADDRESS-MIB) .1.3.6.1.4.1.9.9.800.1.1.19.1.5 |
cMTPathSpecifierDestPortThis object specifies the destination port for the
path specifier.rw InetPortNumber (INET-ADDRESS-MIB) .1.3.6.1.4.1.9.9.800.1.1.19.1.6 |
cMTPathSpecifierSourceAddrTypeThis object specifies the type of IP address specified by
the corresponding instance of cMTFlowSpecifierSourceAddr.rw InetAddressType (INET-ADDRESS-MIB) .1.3.6.1.4.1.9.9.800.1.1.19.1.7 |
cMTPathSpecifierSourceAddrThis object specifies the source address for the
path specifier.rw InetAddress (INET-ADDRESS-MIB) .1.3.6.1.4.1.9.9.800.1.1.19.1.8 |
cMTPathSpecifierSourcePortThis object specifies the source port for the path
specifier.rw InetPortNumber (INET-ADDRESS-MIB) .1.3.6.1.4.1.9.9.800.1.1.19.1.9 |
cMTPathSpecifierProtocolForDiscoveryThis object specifies the protocol used for path discovery
on Mediatrace. Currently, only RSVP is used by default.rw CiscoMediatraceDiscoveryProtocol .1.3.6.1.4.1.9.9.800.1.1.19.1.10 |
cMTPathSpecifierGatewayAddrTypeThis object specifies the type of IP address specified by
the corresponding instance of cMTPathSpecifierGatewayAddr.rw InetAddressType (INET-ADDRESS-MIB) .1.3.6.1.4.1.9.9.800.1.1.19.1.11 |
cMTPathSpecifierGatewayAddrWhen the mediatrace session is originated on layer-2 switch
the address of gateway is required to establish the session.
This object specifies address of this gateway.rw InetAddress (INET-ADDRESS-MIB) .1.3.6.1.4.1.9.9.800.1.1.19.1.12 |
cMTPathSpecifierGatewayVlanIdThis object specifies the Vlan ID associated with the gateway
for path specifier.rw VlanId .1.3.6.1.4.1.9.9.800.1.1.19.1.13 |
cMTPathSpecifierIpProtocolThis object specifies which metrics are monitored for a
path specifier. Currently, only TCP and UDP are
supported.rw CiscoMediatraceSupportProtocol .1.3.6.1.4.1.9.9.800.1.1.19.1.14 |
cMTSessionParamsTableThis table is collection of session parameter profiles. SEQUENCE OF CMTSessionParamsEntry .1.3.6.1.4.1.9.9.800.1.1.20 |
cMTSessionParamsEntryAn entry represents session parameters that can be associated
with a Mediatrace session contained by the cMTSessionTable.
Each entry is uniquely identified by name specified
by cMTSessionParamsName object. A row created in this
table will be shown in 'show running' command and it will
not be saved into non-volatile memory. CMTSessionParamsEntry .1.3.6.1.4.1.9.9.800.1.1.20.1 |
cMTSessionParamsNameThis object specifies the name of this set of session
parameters. SnmpAdminString (SNMP-FRAMEWORK-MIB) .1.3.6.1.4.1.9.9.800.1.1.20.1.1 |
cMTSessionParamsRowStatusThis object specifies the status of the session parameters.
Only CreateAndGo and active status is supported.
In order for this object to become active cMTSessionParamsName
must be defined. The value of cMTSessionParamsInactivityTimeout
needs to be at least 3 times of the value of
cMTSessionParamsFrequency. All other objects assume the default
value.
Once the session parameters is activated no column can be
modified.
Setting this object to 'delete' will destroy the session
parameters. The session parameters can be deleted only if
it is not attached to any session.rw RowStatus (SNMPv2-TC) .1.3.6.1.4.1.9.9.800.1.1.20.1.2 |
cMTSessionParamsResponseTimeoutThis object specifies the amount of time a session
should wait for the responses after sending out a
Mediatrace request. The initiator will discard any
responses to a particular request after this timeout.rw Unsigned32 .1.3.6.1.4.1.9.9.800.1.1.20.1.3 |
cMTSessionParamsFrequencyDuration between two successive data fetch requests.rw Unsigned32 .1.3.6.1.4.1.9.9.800.1.1.20.1.4 |
cMTSessionParamsInactivityTimeoutThis object specifies the interval that the responder
wait without any requests from the initiator before
removing a particular session.
The inactivity timeout needs to be at least 3 times of
the session frequency.rw Unsigned32 .1.3.6.1.4.1.9.9.800.1.1.20.1.5 |
cMTSessionParamsHistoryBucketsThis object specifies the number of buckets of statistics
retained. Each bucket will contain complete set of metrics
collected for all hops in one iteration.rw Unsigned32 .1.3.6.1.4.1.9.9.800.1.1.20.1.6 |
cMTSessionParamsRouteChangeReactiontimeThis object specifies the amount of time the initiator should
wait after receiving the first route change, before reacting to
further route change notifications. Range is from 0 to 60.rw Unsigned32 .1.3.6.1.4.1.9.9.800.1.1.20.1.7 |
cMTMediaMonitorProfileTableThis table lists the media monitor profiles configured on the
device. SEQUENCE OF CMTMediaMonitorProfileEntry .1.3.6.1.4.1.9.9.800.1.1.21 |
cMTMediaMonitorProfileEntryAn entry represents a media monitor profile that can be
associated with a Mediatrace session contained by the
cMTSessionTable.
The entry is uniquely identified by cMTMediaMonitorProfileName.
A row created in this table will be shown in 'show running'
command and it will not be saved into non-volatile memory. CMTMediaMonitorProfileEntry .1.3.6.1.4.1.9.9.800.1.1.21.1 |
cMTMediaMonitorProfileNameThis object specifies the name of the Mediatrace media monitor
profile. SnmpAdminString (SNMP-FRAMEWORK-MIB) .1.3.6.1.4.1.9.9.800.1.1.21.1.1 |
cMTMediaMonitorProfileRowStatusThis object specifies the status of the media monitor profile.
Only CreateAndGo and active status is supported.
In order for this object to become active cMTMediaMonitorProfileName
must be defined. All other objects assume the default value.
Once the media monitor profile is activated no column can be
modified.
Setting this object to 'delete' will destroy the media monitor.
The media monitor profile can be deleted only if it is not
attached to any session.rw RowStatus (SNMPv2-TC) .1.3.6.1.4.1.9.9.800.1.1.21.1.2 |
cMTMediaMonitorProfileMetricThis object specifies the type of metrics group to be
collected in addition to basic IP metrics. Specify value
as RTP if metrics from 'Metric-List RTP' are desired
and 'TCP' if metrics in 'Metric-List TCP' is desired.rw Enumeration .1.3.6.1.4.1.9.9.800.1.1.21.1.3 |
cMTMediaMonitorProfileIntervalThis object specifies the sampling interval for the media
monitor profile.rw Unsigned32 .1.3.6.1.4.1.9.9.800.1.1.21.1.4 |
cMTMediaMonitorProfileRtpMaxDropoutThis object specifies the maximum number of dropouts allowed
when sampling RTP monitoring metrics.rw Unsigned32 .1.3.6.1.4.1.9.9.800.1.1.21.1.5 |
cMTMediaMonitorProfileRtpMaxReorderThis object specifies the maximum number of reorders allowed
when sampling RTP monitoring metrics.rw Unsigned32 .1.3.6.1.4.1.9.9.800.1.1.21.1.6 |
cMTMediaMonitorProfileRtpMinimalSequentialThis object specifies the minimum number of sequental packets
required to identify a stream as being an RTP flow.rw Unsigned32 .1.3.6.1.4.1.9.9.800.1.1.21.1.7 |
cMTSystemProfileTableThis table lists the system profiles configured on the
device. SEQUENCE OF CMTSystemProfileEntry .1.3.6.1.4.1.9.9.800.1.1.22 |
cMTSystemProfileEntryAn entry represents a system profile that can be associated
with a Mediatrace session contained by the cMTSessionTable.
Each entry is uniquely identified by name specified
by cMTSystemProfileName object. A row created in this
table will be shown in 'show running' command and it will
not be saved into non-volatile memory. CMTSystemProfileEntry .1.3.6.1.4.1.9.9.800.1.1.22.1 |
cMTSystemProfileNameThis object specifies the name of the Mediatrace system
profile. SnmpAdminString (SNMP-FRAMEWORK-MIB) .1.3.6.1.4.1.9.9.800.1.1.22.1.1 |
cMTSystemProfileRowStatusThis object specifies the status of the system profile.
Only CreateAndGo and active status is supported.
In order for this object to become active cMTSystemProfileName
must be defined. All other objects assume the default value.
Once the system profile is activated no column can be
modified.
Setting this object to 'delete' will destroy the system
profile. The system prifile can be deleted only if
it is not attached to any session.rw RowStatus (SNMPv2-TC) .1.3.6.1.4.1.9.9.800.1.1.22.1.2 |
cMTSystemProfileMetricThis object specifies the type of metrics group to be
collected in addition to basic IP metrics. Specify
'interface' if metrics from 'Metric-List-Interface'
are desired. Specify 'cpu' if metrics in 'Metric-List-CPU'
is desired. Specify 'memory' if metrics in
'Metric-List-Memory' is desired.rw Enumeration .1.3.6.1.4.1.9.9.800.1.1.22.1.3 |
cMTSessionTableThis table lists the Mediatrace sessions configured on the
device. SEQUENCE OF CMTSessionEntry .1.3.6.1.4.1.9.9.800.1.1.23 |
cMTSessionEntryA list of objects that define specific configuration for
the session of Mediatrace.
The entry is uniquely identified by cMTSessionNumber.
A row created in this table will be shown in 'show running'
command and it will not be saved into non-volatile memory. CMTSessionEntry .1.3.6.1.4.1.9.9.800.1.1.23.1 |
cMTSessionNumberThis object specifies an arbitrary integer-value that uniquely
identifies a Mediatrace session. Unsigned32 .1.3.6.1.4.1.9.9.800.1.1.23.1.2 |
cMTSessionRowStatusThis object indicates the status of Mediatrace session. Only
CreateAndGo and active status is supported. Following columns
must be specified in order to activate the session:
- cMTSessionPathSpecifierName
- cMTSessionProfileName
All other objects can assume default values.
None of the properties of session can be modified once it is in
'active' state.
Setting the value of 'destroy' for this object will delete the
session. The session can be deleted only if the corresponding
schedule (row in cMTScheduleTable ) not exist.rw RowStatus (SNMPv2-TC) .1.3.6.1.4.1.9.9.800.1.1.23.1.3 |
cMTSessionPathSpecifierNameThis object specifies the name of the Mediatrace path
specifier profile associated with the session.rw SnmpAdminString (SNMP-FRAMEWORK-MIB) .1.3.6.1.4.1.9.9.800.1.1.23.1.4 |
cMTSessionParamNameThis object specifies the name of Mediatrace session
parameter associated with the session.rw SnmpAdminString (SNMP-FRAMEWORK-MIB) .1.3.6.1.4.1.9.9.800.1.1.23.1.5 |
cMTSessionProfileNameThis object specifies the name of the Mediatrace metric
profile associated with the session.rw SnmpAdminString (SNMP-FRAMEWORK-MIB) .1.3.6.1.4.1.9.9.800.1.1.23.1.6 |
cMTSessionFlowSpecifierNameThis object specifies the name of the Mediatrace flow
specifier profile associated with the session. Flow
specifier is not required if system profile is attached
to the session. In this case, media monitor
profile is attached to the session. Flow specifier is
optional and the 5-tuple from the path-specifier is used
instead.rw SnmpAdminString (SNMP-FRAMEWORK-MIB) .1.3.6.1.4.1.9.9.800.1.1.23.1.7 |
cMTSessionTraceRouteEnabledThis object specifies if traceroute is enabled for this
session.rw TruthValue (SNMPv2-TC) .1.3.6.1.4.1.9.9.800.1.1.23.1.8 |
cMTScheduleTableA table of Mediatrace scheduling specific definitions.
Each entry in this table schedules a cMTSessionEntry
created via the cMTSessionTable object. SEQUENCE OF CMTScheduleEntry .1.3.6.1.4.1.9.9.800.1.1.24 |
cMTScheduleEntryA list of objects that define specific configuration for
the scheduling of Mediatrace operations.
A row is created when a session is scheduled to make it active.
Likewise, a row is destroyed when the session is unscheduled.
A row created in this table will be shown in 'show running'
command and it will not be saved into non-volatile memory. CMTScheduleEntry .1.3.6.1.4.1.9.9.800.1.1.24.1 |
cMTScheduleRowStatusThis objects specifies the status of Mediatrace session
schedule. Only CreateAndGo and destroy operations are
permitted on the row.
All objects can assume default values.
The schedule start time (column cMTScheduleStartTime) must
be specified in order to activate the schedule. Once
activated none of the properties of the schedule can be
changed.
The schedule can be destroyed any time by setting the value
of this object to 'destroy'. Destroying the schedule will
stop the Mediatrace session but the session will not be
destroyed.rw RowStatus (SNMPv2-TC) .1.3.6.1.4.1.9.9.800.1.1.24.1.1 |
cMTScheduleStartTimeThis object specifies the start time of the scheduled
session.rw TimeStamp (SNMPv2-TC) .1.3.6.1.4.1.9.9.800.1.1.24.1.2 |
cMTScheduleLifeThis object specifies the duration of the session in seconds.rw Unsigned32 .1.3.6.1.4.1.9.9.800.1.1.24.1.3 |
cMTScheduleEntryAgeoutThis object specifies the amount of time after which
mediatrace session entry will be removed once the life
of session is over and session is inactive.rw Unsigned32 .1.3.6.1.4.1.9.9.800.1.1.24.1.4 |
cMTScheduleRecurringThis object specifies whether the schedule is recurring
schedule. This object can be used when a periodic session
is to be executed everyday at certain time and for certain
life.rw 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 |
cMTPathTableList of paths discovered by a mediatrace session. SEQUENCE OF CMTPathEntry .1.3.6.1.4.1.9.9.800.1.2.1 |
cMTPathEntryAn entry in cMTPathTable represents a Mediatrace path
discovered by a session.
This table contains information about the hops (Mediatrace or
non-Mediatrace) discovered during a specific request.
The Path table is used to find the hop address (Address type
- IPv4 or IPv6 and Address) and hop type (currently Mediatrace
or Traceroute) to use as index for other statistics tables.
A row is created when a Mediatrace scheduled session discovers
a path to the specified destination during a request.
Likewise, a row is destroyed when the path is no longer avilable.
A single row corresponds to a Mediatrace path discovered for
a session and is uniquely identified by cMTSessionNumber,
cMTSessionLifeNumber, cMTBucketNumber and cMTPathHopNumber.
The created rows are destroyed when the device undergoes a
restart. CMTPathEntry .1.3.6.1.4.1.9.9.800.1.2.1.1 |
cMTSessionLifeNumberThis object specifies a life for a conceptual statistics
row.
For a particular value of cMTSessionLifeNumber, the agent
assigns the first value of 0 to the current (latest) life,
with 1 being the next latest and so on. The sequence
keeps incrementing, despite older (lower) values being removed
from the table. Unsigned32 .1.3.6.1.4.1.9.9.800.1.2.1.1.1 |
cMTBucketNumberThis object is index of the list of statistics buckets
stored. A statistics bucket corresponds to data collected
from each hop in one run of the periodic mediatrace
session. Bucket with Index value of 0 is the bucket for
latest completed run. Index 1 is one run prior to latest
completed run, index 2 is two runs prior to latest
completed run, and so on. Unsigned32 .1.3.6.1.4.1.9.9.800.1.2.1.1.2 |
cMTPathHopNumberThis object specifies the hop number for a Mediatrace Path.
This hop can be either Mediatrace or Non-Mediatrace node.
The hop number is relative to the initiator with 0 being
used to identify initiator itself, 1 for next farther node,
etc. This hop number is always unique i.e., two hops cannot
have same hop number. Unsigned32 .1.3.6.1.4.1.9.9.800.1.2.1.1.3 |
cMTPathHopAddrTypeThis object specifies the type of IP address specified by
the corresponding instance of cMTPathHopAddrType.ro InetAddressType (INET-ADDRESS-MIB) .1.3.6.1.4.1.9.9.800.1.2.1.1.4 |
cMTPathHopAddrThis object indicates IP Address type of the hop on a
Mediatrace Path.ro InetAddress (INET-ADDRESS-MIB) .1.3.6.1.4.1.9.9.800.1.2.1.1.5 |
cMTPathHopTypeThis object indicates the type of the hop on a Mediatrace
path. Currently, only two types are present - mediatrace(1)
and traceroute(2).
A hop is of type 'mediatrace' if it is discovered by only
mediatrace or by both mediatrace and trace-route. The hop
is 'trace route' if it is discovered by trace route only.ro Enumeration .1.3.6.1.4.1.9.9.800.1.2.1.1.6 |
cMTPathHopAlternate1AddrTypeThis object specifies the type of IP address specified by
the corresponding instance of cMTPathHopAlternate1AddrType.ro InetAddressType (INET-ADDRESS-MIB) .1.3.6.1.4.1.9.9.800.1.2.1.1.7 |
cMTPathHopAlternate1AddrThis object indicates the IP Address of the first alternate hop
on a traceroute path.ro InetAddress (INET-ADDRESS-MIB) .1.3.6.1.4.1.9.9.800.1.2.1.1.8 |
cMTPathHopAlternate2AddrTypeThis object specifies the type of IP address specified by
the corresponding instance of cMTPathHopAlternate2AddrType.ro InetAddressType (INET-ADDRESS-MIB) .1.3.6.1.4.1.9.9.800.1.2.1.1.9 |
cMTPathHopAlternate2AddrThis object indicates the IP Address of the second alternate
hop on a traceroute path.ro InetAddress (INET-ADDRESS-MIB) .1.3.6.1.4.1.9.9.800.1.2.1.1.10 |
cMTPathHopAlternate3AddrTypeThis object specifies the type of IP address specified by
the corresponding instance of cMTPathHopAlternate3AddrType.ro InetAddressType (INET-ADDRESS-MIB) .1.3.6.1.4.1.9.9.800.1.2.1.1.11 |
cMTPathHopAlternate3AddrThis object indicates the IP Address of the third alternate hop
on a traceroute path.ro InetAddress (INET-ADDRESS-MIB) .1.3.6.1.4.1.9.9.800.1.2.1.1.12 |
cMTHopStatsTableAn 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. SEQUENCE OF CMTHopStatsEntry .1.3.6.1.4.1.9.9.800.1.2.2 |
cMTHopStatsEntryAn entry in cMTHopStatsTable CMTHopStatsEntry .1.3.6.1.4.1.9.9.800.1.2.2.1 |
cMTHopStatsMaskBitmapsThis object indicates whether the corresponding instances of
these statistics fields in the table are supported. It also
indicates if the statistics data are collected. There are 2
bits for each corresponding field.ro Bits .1.3.6.1.4.1.9.9.800.1.2.2.1.1 |
cMTHopStatsAddrTypeThis object specifies the type of IP address specified by
the corresponding instance of cMTHopStatsAddr. InetAddressType (INET-ADDRESS-MIB) .1.3.6.1.4.1.9.9.800.1.2.2.1.2 |
cMTHopStatsAddrThis object specifies the IP Address of the hop on a
Mediatrace Path. This value is obtained from
CMTPathHopAddr in cMTPathTable. InetAddress (INET-ADDRESS-MIB) .1.3.6.1.4.1.9.9.800.1.2.2.1.3 |
cMTHopStatsNameThis object indicates the name for this hop. This can
be either the hostname or the IP address for the hop.ro SnmpAdminString (SNMP-FRAMEWORK-MIB) .1.3.6.1.4.1.9.9.800.1.2.2.1.4 |
cMTHopStatsMediatraceTtlThis object indicates the hop limit of the corresponding
traffic flow.
If version 4 of the IP carries the traffic flow, then the value
of this column corresponds to the 'Time to Live' field of the
IP header contained by packets in the Mediatrace request.
If version 6 of the IP carries the traffic flow, then the value
of this column corresponds to the 'Hop Limit' field of the IP
header contained by packets in the Mediatrace request.ro Unsigned32 .1.3.6.1.4.1.9.9.800.1.2.2.1.5 |
cMTHopStatsCollectionStatusThis object indicates the operational status of data being
collected on the hop for a specific session:
'success'
The hop is actively collecting and responding with
data.
'notsuccess'
The hop is not collecting or responding with data.ro Enumeration .1.3.6.1.4.1.9.9.800.1.2.2.1.6 |
cMTHopStatsIngressInterfaceThis object indicates the interface on the responder that
receives the Mediatrace request from the initiator.ro SnmpAdminString (SNMP-FRAMEWORK-MIB) .1.3.6.1.4.1.9.9.800.1.2.2.1.7 |
cMTHopStatsEgressInterfaceThis object indicates the interface on the responder which
is used to forward the Mediatrace request from the initiator
towards destination in the path specifier.
Value of 'None' will be shown if the destination address in
path specifier terminates on this hop.ro SnmpAdminString (SNMP-FRAMEWORK-MIB) .1.3.6.1.4.1.9.9.800.1.2.2.1.8 |
cMTTraceRouteTableThis 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. SEQUENCE OF CMTTraceRouteEntry .1.3.6.1.4.1.9.9.800.1.2.3 |
cMTTraceRouteEntryAn entry in cMTTraceRouteTable represents a Traceroute
hop on the path associated to a Mediatrace session.
The created rows are destroyed when the device undergoes
a restart. CMTTraceRouteEntry .1.3.6.1.4.1.9.9.800.1.2.3.1 |
cMTTraceRouteHopNumberThis object indicates the hop number of Traceroute host
relative to the Initiator. It start with 1 and increments
as we go farther from the Initiator.ro Gauge32 .1.3.6.1.4.1.9.9.800.1.2.3.1.1 |
cMTTraceRouteHopRttThis object indicates RTT. The time it takes for a packet
to get to a hop and back, displayed in milliseconds. (ms).ro Counter64 .1.3.6.1.4.1.9.9.800.1.2.3.1.2 |
cMTSessionStatusTableThis table contains aggregate data maintained by Mediatrace
for session status. SEQUENCE OF CMTSessionStatusEntry .1.3.6.1.4.1.9.9.800.1.2.4 |
cMTSessionStatusEntryAn entry in cMTSessionStatusTable represents information
about a Mediatrace session.
This table contains information about particular session
such as global session identifier, operation state and
time to live.
A single row corresponds to status of a Mediatrace
session and is uniquely identified by cMTSessionNumber.
The created rows are destroyed when the device undergoes
a restart. CMTSessionStatusEntry .1.3.6.1.4.1.9.9.800.1.2.4.1 |
cMTSessionStatusBitmapsThis object indicates whether the corresponding instances of
these statistics fields in the table are supported. It also
indicates if the statistics are collected. There are 2 bits for
each field.ro Bits .1.3.6.1.4.1.9.9.800.1.2.4.1.1 |
cMTSessionStatusGlobalSessionIdThis object indicates a globally unique Id to identify a
session throughout the network.ro Unsigned32 .1.3.6.1.4.1.9.9.800.1.2.4.1.2 |
cMTSessionStatusOperationStateThis object indicates the operation status of the session.
pending - Session is not currently active.
active - Session is in active state.
inactive - Session is not active but it has not aged out.
sleep - Session is in sleep state.ro Enumeration .1.3.6.1.4.1.9.9.800.1.2.4.1.3 |
cMTSessionStatusOperationTimeToLiveThis object indicates how long the session operation will
last.ro Counter64 .1.3.6.1.4.1.9.9.800.1.2.4.1.4 |
cMTSessionRequestStatsTableThis table contains aggregate data maintained by Mediatrace
for session request status. SEQUENCE OF CMTSessionRequestStatsEntry .1.3.6.1.4.1.9.9.800.1.2.5 |
cMTSessionRequestStatsEntryAn entry in cMTSessionRequestStatsTable represents status
for each request for a particular session.
A single row corresponds to a request sent by a
particular Mediatrace session and is uniquely
identified by cMTSessionNumber, cMTSessionLifeNumber and
cMTBucketNumber.
The created rows are destroyed when the device undergoes
a restart. CMTSessionRequestStatsEntry .1.3.6.1.4.1.9.9.800.1.2.5.1 |
cMTSessionRequestStatsBitmapsThis object indicates whether the corresponding instances of
these stats fields in the table are supported. It also
indicates if the stats data are collected. There are 2 bits
for each corresponding field.ro Bits .1.3.6.1.4.1.9.9.800.1.2.5.1.1 |
cMTSessionRequestStatsRequestTimestampThis object indicates the value of request time when the
request was sent our by the initiator for this particular
session.ro TimeStamp (SNMPv2-TC) .1.3.6.1.4.1.9.9.800.1.2.5.1.2 |
cMTSessionRequestStatsRequestStatusThis object indicates the status of request for the session.ro Enumeration .1.3.6.1.4.1.9.9.800.1.2.5.1.3 |
cMTSessionRequestStatsTracerouteStatusThis object indicates the status of traceroute for the
session.ro Enumeration .1.3.6.1.4.1.9.9.800.1.2.5.1.4 |
cMTSessionRequestStatsRouteIndexThis object indicates the route index for the session
request. It signifies the number of times a route
has changed for a particular session. 0 signifies
no route change.ro Gauge32 .1.3.6.1.4.1.9.9.800.1.2.5.1.5 |
cMTSessionRequestStatsNumberOfMediatraceHopsThis object indicates the number of Mediatrace hops in
the path.ro Counter32 .1.3.6.1.4.1.9.9.800.1.2.5.1.6 |
cMTSessionRequestStatsNumberOfNonMediatraceHopsThis object indicates the number of non-Mediatrace hops in the
path.ro Counter32 .1.3.6.1.4.1.9.9.800.1.2.5.1.7 |
cMTSessionRequestStatsNumberOfValidHopsThis object indicates the number of hops with valid data
report.ro Counter32 .1.3.6.1.4.1.9.9.800.1.2.5.1.8 |
cMTSessionRequestStatsNumberOfErrorHopsThis object indicates the number of hops with error report.
These hops are not able to return the statistics due to
some issue.ro Counter32 .1.3.6.1.4.1.9.9.800.1.2.5.1.9 |
cMTSessionRequestStatsNumberOfNoDataRecordHopsThis object indicates the number of hops with no data record.ro Counter32 .1.3.6.1.4.1.9.9.800.1.2.5.1.10 |
cMTSessionRequestStatsMDGlobalIdThis object indicates the meta-data global Id for this
session.ro OCTET STRING .1.3.6.1.4.1.9.9.800.1.2.5.1.11 |
cMTSessionRequestStatsMDMultiPartySessionIdThis object indicates the meta-data Multi Party Session Id for
this session.ro OCTET STRING .1.3.6.1.4.1.9.9.800.1.2.5.1.12 |
cMTSessionRequestStatsMDAppNameThis object indicates the meta-data AppName for this session.ro OCTET STRING .1.3.6.1.4.1.9.9.800.1.2.5.1.13 |
cMTCommonMetricStatsTableThis table contains the list of entries representing
common IP metrics values for a particular mediatrace
session on particular hop. SEQUENCE OF CMTCommonMetricStatsEntry .1.3.6.1.4.1.9.9.800.1.2.6 |
cMTCommonMetricStatsEntryAn entry in cMTCommonMetricStatsTable represents
common media monitor profile information of a hop on the
path associated to a Mediatrace session such as flow sampling
time stamp, packets dropped, IP TTL, etc.
The devices creates a row in the cMTCommonMetricStatsTable
when a Mediatrace session starts collecting a traffic metrics
data and has been configured to compute common IP metrics.
Likewise, the device destroys a row in the
cMTCommonMetricStatsTable when the corresponding
Mediatrace session has ceased collecting the traffic metrics
data (e.g., when a scheduled session has timed out).
A single row corresponds to a common media monitor profile
information of a hop on the 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. CMTCommonMetricStatsEntry .1.3.6.1.4.1.9.9.800.1.2.6.1 |
cMTCommonMetricsBitmapsThis object indicates whether the corresponding instances of
these stats fields in the table are supported. It also
indicates if the stats data are collected. There are 2 bits
for each field.ro Bits .1.3.6.1.4.1.9.9.800.1.2.6.1.2 |
cMTCommonMetricsFlowSamplingStartTimeThis object defines the the timestamp when the statistics
were collected on the responder.ro CiscoNTPTimeStamp .1.3.6.1.4.1.9.9.800.1.2.6.1.3 |
cMTCommonMetricsIpPktDroppedThis object indicates number of packet drops observed
on the flow being monitored on this hop from flow sampling
start time in window of 'sample interval' length.ro Counter64 UNITS "packets" .1.3.6.1.4.1.9.9.800.1.2.6.1.4 |
cMTCommonMetricsIpOctetsThis object indicates the total number of octets contained by
the packets processed by the Mediatrace request for the
corresponding traffic flow.ro Counter64 UNITS "octets" .1.3.6.1.4.1.9.9.800.1.2.6.1.5 |
cMTCommonMetricsIpPktCountThis object indicates the total number of packets processed by
the Mediatrace request for the corresponding traffic flow.ro Counter64 UNITS "packets" .1.3.6.1.4.1.9.9.800.1.2.6.1.6 |
cMTCommonMetricsIpByteRateThis object indicates the average packet rate at which the
Mediatrace request is processing data for the corresponding
traffic flow. This value is cumulative over the lifetime of
the traffic flow.ro Gauge32 UNITS "packets per second" .1.3.6.1.4.1.9.9.800.1.2.6.1.7 |
cMTCommonMetricsIpDscpThis object indicates the DSCP value of the corresponding
traffic flow.
If version 4 of the IP carries the traffic flow, then the value
of this column corresponds to the DSCP part of 'Type of
Service' field of the IP header contained by packets in the
traffic flow.
If version 6 of the IP carries the traffic flow, then the value
of this column corresponds to DSCP part of the 'Traffic Class'
field of the IP header contained by packets in the traffic
flow.ro Unsigned32 .1.3.6.1.4.1.9.9.800.1.2.6.1.8 |
cMTCommonMetricsIpTtlThis object indicates the hop limit of the corresponding
traffic flow.
If version 4 of the IP carries the traffic flow, then the value
of this column corresponds to the 'Time to Live' field of the
IP header contained by packets in the Mediatrace request.
If version 6 of the IP carries the traffic flow, then the value
of this column corresponds to the 'Hop Limit' field of the IP
header contained by packets in the Mediatrace request.ro Unsigned32 .1.3.6.1.4.1.9.9.800.1.2.6.1.9 |
cMTCommonMetricsFlowCounterThis object indicates the number of traffic flows currently
monitored by the Mediatrace request.ro Gauge32 .1.3.6.1.4.1.9.9.800.1.2.6.1.10 |
cMTCommonMetricsFlowDirectionThis object indicates the direction of the traffic flow where
the data is monitored :
'unknown'
The SNMP entity does not know the direction of the
traffic flow at the point data is collected.
'ingress'
Data is collected at the point where the
traffic flow enters the devices
'egress'
Data is colected at the point where the
traffic flow leaves the device.ro Enumeration .1.3.6.1.4.1.9.9.800.1.2.6.1.11 |
cMTCommonMetricsLossMeasurementThis object indicates the loss measurement.ro Enumeration .1.3.6.1.4.1.9.9.800.1.2.6.1.12 |
cMTCommonMetricsMediaStopOccurredThis object indicates the media stop occurred.ro Enumeration .1.3.6.1.4.1.9.9.800.1.2.6.1.13 |
cMTCommonMetricsRouteForwardThis object indicates routing or forwarding status i.e.
whether the packet is forwarded or dropped for the flow.ro SnmpAdminString (SNMP-FRAMEWORK-MIB) .1.3.6.1.4.1.9.9.800.1.2.6.1.14 |
cMTCommonMetricsIpProtocolThis table contains entry to specify the media
Metric-list for the particular Mmediatrace session on
the hop.ro CiscoMediatraceSupportProtocol .1.3.6.1.4.1.9.9.800.1.2.6.1.15 |
cMTRtpMetricStatsTableThis table contains aggregate data maintained by Mediatrace
for traffic flows for which it is computing RTP metrics. SEQUENCE OF CMTRtpMetricStatsEntry .1.3.6.1.4.1.9.9.800.1.2.7 |
cMTRtpMetricStatsEntryAn entry in cMTRtpMetricStatsTable represents RTP related
information of a hop on the path associated to a Mediatrace
session such as bit rate, octets, etc.
The devices creates a row in the cMTRtpMetricStatsTable when
a Mediatrace session starts collecting a traffic metrics data
and has been configured to compute RTP metrics for the same
traffic metrics data. Likewise, the device destroys a row in
the cMTRtpMetricStatsTable when the corresponding Mediatrace
session has ceased collecting the traffic metrics data (e.g.,
when a scheduled session has timed out).
A single row corresponds to a RTP information of a hop on the
path discovered for a Mediatrace session and is uniquely
identified by cMTSessionNumber, cMTSessionLifeNumber,
cMTBucketNumber,cMTHopStatsAddrType and cMTHopStatsAddr.
The created rows are destroyed when the device undergoes
a restart. CMTRtpMetricStatsEntry .1.3.6.1.4.1.9.9.800.1.2.7.1 |
cMTRtpMetricsBitmapsThis object indicates whether the corresponding instances of
these statistics fields in the table are supported. It also
indicates if the stats data are collected. There are 2 bits
for each field.ro Bits .1.3.6.1.4.1.9.9.800.1.2.7.1.2 |
cMTRtpMetricsBitRateThis object indicates the average bit rate at which the
corresponding Mediatrace request is processing data for
the corresponding traffic flow. This value is
cumulative over the lifetime of the traffic flow.ro Gauge32 .1.3.6.1.4.1.9.9.800.1.2.7.1.3 |
cMTRtpMetricsOctetsThis object indicates the total number of octets contained
by the packets processed by the Mediatrace request for the
corresponding traffic flow.ro Counter64 .1.3.6.1.4.1.9.9.800.1.2.7.1.4 |
cMTRtpMetricsPktsThis object indicates the total number of packets processed by
the corresponding Mediatrace request for the corresponding
traffic flow.ro Counter64 UNITS "packets" .1.3.6.1.4.1.9.9.800.1.2.7.1.5 |
cMTRtpMetricsJitterThis object indicates the inter-arrival jitter for the traffic
flow.ro FlowMetricValue UNITS "seconds" .1.3.6.1.4.1.9.9.800.1.2.7.1.6 |
cMTRtpMetricsLostPktsThis object indicates the number of RTP packets lost for the
traffic flow.ro Counter64 UNITS "packets" .1.3.6.1.4.1.9.9.800.1.2.7.1.7 |
cMTRtpMetricsExpectedPktsThis object indicates the number of RTP packets expected for
the traffic flow.ro Counter64 UNITS "packets" .1.3.6.1.4.1.9.9.800.1.2.7.1.8 |
cMTRtpMetricsLostPktEventsThis object indicates the number of packet loss events observed
by the Mediatrace request for the corresponding traffic flow.ro Counter64 UNITS "packets" .1.3.6.1.4.1.9.9.800.1.2.7.1.9 |
cMTRtpMetricsLossPercentThis object indicates the percentage of packages are lost per
ten thousand packets in a traffic flow.ro Gauge32 .1.3.6.1.4.1.9.9.800.1.2.7.1.10 |
cMTTcpMetricStatsTableThis table contains aggregate data maintained by Mediatrace
for traffic flows for which it is computing TCP
metrics. SEQUENCE OF CMTTcpMetricStatsEntry .1.3.6.1.4.1.9.9.800.1.2.8 |
cMTTcpMetricStatsEntryAn entry in cMTTcpMetricStatsTable represents TCP information
of a hop on the path associated to a Mediatrace session such
as byte count, round trip delay, etc.
The devices creates a row in the cMTTcpMetricStatsTable when
a Mediatrace session starts collecting a traffic metrics data
and has been configured to compute TCP metrics for the same
traffic metrics data. Likewise, the device destroys a row in
the cMTTcpMetricStatsTable when the corresponding Mediatrace
session has ceased collecting the traffic metrics data (e.g.,
when a scheduled session has timed out).
A single row corresponds to TCP information of
a hop on the path discovered for a Mediatrace session
and is uniquely identified by cMTSessionNumber,
cMTSessionLifeNumber, cMTBucketNumber,cMTHopStatsAddrType
and cMTHopStatsAddr.
The created rows are destroyed when the device undergoes
a restart. CMTTcpMetricStatsEntry .1.3.6.1.4.1.9.9.800.1.2.8.1 |
cMTTcpMetricBitmapsThis object indicates whether the corresponding instances of
these stats fields in the table are supported. It also
indicates if the stats data are collected. There are 2 bits
for each field.ro Bits .1.3.6.1.4.1.9.9.800.1.2.8.1.2 |
cMTTcpMetricMediaByteCountThis object indicates the number of bytes for the packets
observed by the Mediatrace session for the corresponding
flow.ro FlowMetricValue (CISCO-FLOW-MONITOR-TC-MIB) .1.3.6.1.4.1.9.9.800.1.2.8.1.3 |
cMTTcpMetricConnectRoundTripDelayThis object indicates the round trip time for the packets
observed by the Mediatrace session for the corresponding
flow. The round trip time is defined as the length of time
it takes for a TCP segment transmission and receipt of
acknowledgement. This object indicates the connect round
trip delay.ro Counter64 .1.3.6.1.4.1.9.9.800.1.2.8.1.4 |
cMTTcpMetricLostEventCountThis object indicates the number of packets lost for the
traffic flow.ro Counter64 .1.3.6.1.4.1.9.9.800.1.2.8.1.5 |
cMTSystemMetricStatsTableA list of objects which accumulate the system metrics results
of a particular node for that path. SEQUENCE OF CMTSystemMetricStatsEntry .1.3.6.1.4.1.9.9.800.1.2.9 |
cMTSystemMetricStatsEntryAn entry in cMTSystemMetricStatsTable represents
CPU or memory utilization information of a hop on the
path associated to a Mediatrace session such as five
minutes CPU utilization, memory utilization, etc.
The devices creates a row in the cMTSystemMetricStatsTable when
a Mediatrace session starts collecting a system metrics data
and has been configured to compute system metrics. Likewise,
the device destroys a row in the cMTSystemMetricStatsTable when
the corresponding Mediatrace session has ceased collecting
the system metrics data (e.g., when a scheduled session has
timed out).
A single row corresponds to a CPU or memory utilization
information of a hop on the path discovered for a Mediatrace
session and is uniquely identified by cMTSessionNumber,
cMTSessionLifeNumber, cMTBucketNumber,cMTHopStatsAddrType
and cMTHopStatsAddr.
The created rows are destroyed when the device undergoes
a restart. CMTSystemMetricStatsEntry .1.3.6.1.4.1.9.9.800.1.2.9.1 |
cMTSystemMetricBitmapsThis object indicates whether the corresponding instances of
these stats fields in the table are supported. It also
indicates if the stats data are collected. There are 2 bits
for each field.ro Bits .1.3.6.1.4.1.9.9.800.1.2.9.1.1 |
cMTSystemMetricCpuOneMinuteUtilizationThis object indicates the overall CPU busy percentage in the
last 1 minute period for the network elementro Gauge32 .1.3.6.1.4.1.9.9.800.1.2.9.1.2 |
cMTSystemMetricCpuFiveMinutesUtilizationThis object indicates the overall CPU busy percentage in
the last 5 minute period for the network elementro Gauge32 .1.3.6.1.4.1.9.9.800.1.2.9.1.3 |
cMTSystemMetricMemoryUtilizationThis object indicates the overall memory usage percentage for
the node.ro Gauge32 .1.3.6.1.4.1.9.9.800.1.2.9.1.4 |
cMTInterfaceMetricStatsTableThis table contains aggregate data of interface information for
the network nodes. SEQUENCE OF CMTInterfaceMetricStatsEntry .1.3.6.1.4.1.9.9.800.1.2.10 |
cMTInterfaceMetricStatsEntryAn entry in cMTInterfaceMetricStatsTable represents
interface information of a hop on the path associated
to a Mediatrace session such as ingress interface speed,
egress interface speed, etc.
The devices creates a row in the cMTInterfaceMetricStatsTable
when a Mediatrace session starts collecting an interface
metrics data and has been configured to compute interface
metrics. Likewise, the device destroys a row in the
cMTInterfaceMetricStatsTable when the corresponding Mediatrace
session has ceased collecting the interface metrics data
(e.g., when a scheduled session has timed out).
A single row corresponds to a interface information of a hop
on the 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. CMTInterfaceMetricStatsEntry .1.3.6.1.4.1.9.9.800.1.2.10.1 |
cMTInterfaceBitmapsThis object indicates whether the corresponding instances of
these stats fields in the table are supported. It also
indicates if the stats data are collected. There are 2 bits
for each field.ro Bits .1.3.6.1.4.1.9.9.800.1.2.10.1.2 |
cMTInterfaceOutSpeedThis object indicates the egress interface's current bandwidth
in bits per second. For interfaces which do not vary in
bandwidth or for those where no accurate estimation can be
made, this object should contain the nominal bandwidth.
Currently bandwidth above the maximum value 4,294,967,295
is not supported and it will show the maximum for this
condition.ro Gauge32 .1.3.6.1.4.1.9.9.800.1.2.10.1.3 |
cMTInterfaceInSpeedThis object indicates an estimate of the ingress interface's
current bandwidth in bits per second. Currently bandwidth
above the maximum value 4,294,967,295 is not supported and it
will show the maximum for this condition.ro Gauge32 .1.3.6.1.4.1.9.9.800.1.2.10.1.4 |
cMTInterfaceOutDiscardsThis object indicates the number of outbound packets which were
chosen to be discarded even though no errors had been detected
to prevent their being transmitted. One possible reason for
discarding such a packet could be to free up buffer space.ro Counter32 .1.3.6.1.4.1.9.9.800.1.2.10.1.5 |
cMTInterfaceInDiscardsThis object indicates the number of inbound packets which were
chosen to be discarded even though no errors had been detected
to prevent their being deliverable to a higher-layer protocol.
One possible reason for discarding such a packet could be to
free up buffer space.
Discontinuities in the value of this counter can occur at
re-initialization of the management system, and at other
times as indicated by the value of
ifCounterDiscontinuityTime.ro Counter32 .1.3.6.1.4.1.9.9.800.1.2.10.1.6 |
cMTInterfaceOutErrorsThis object indicates the error packet number. For
packet-oriented interfaces, the number of outbound packets that
could not be transmitted because of errors. For
character-oriented or fixed-length interfaces, the number of
outbound transmission units that could not be transmitted
because of errors.
Discontinuities in the value of this counter can occur at
re-initialization of the management system, and at other
times as indicated by the value of
ifCounterDiscontinuityTime.ro Counter32 .1.3.6.1.4.1.9.9.800.1.2.10.1.7 |
cMTInterfaceInErrorsThis object indicates the error packet number. For
packet-oriented interfaces, the number of inbound packets that
contained errors preventing them from being deliverable to a
higher-layer protocol. For character-oriented or fixed-length
interfaces, the number of inbound transmission units that
contained errors preventing them from being deliverable to
a higher-layer protocol.
Discontinuities in the value of this counter can occur at
re-initialization of the management system, and at other
times as indicated by the value of
ifCounterDiscontinuityTime.ro Counter32 .1.3.6.1.4.1.9.9.800.1.2.10.1.8 |
cMTInterfaceOutOctetsThis object indicates the total number of octets transmitted
out of the interface, including framing characters.
Discontinuities in the value of this counter can occur at
re-initialization of the management system, and at other
times as indicated by the value of
ifCounterDiscontinuityTime.ro Counter32 .1.3.6.1.4.1.9.9.800.1.2.10.1.9 |
cMTInterfaceInOctetsThis object indicates the total number of octets received on
the interface, including framing characters.
Discontinuities in the value of this counter can occur at
re-initialization of the management system, and at other
times as indicated by the value of
ifCounterDiscontinuityTime.ro Counter32 .1.3.6.1.4.1.9.9.800.1.2.10.1.10 |
ciscoMediatraceMIBConform OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.800.2 |
ciscoMediatraceMIBCompliances OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.800.2.1 |
ciscoMediatraceMIBGroups OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.800.2.2 |