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,
+
+
+
+
+
In addition to the above objects, the following objects are
used for obtaining information about the initiator role on
the device,
+
+
+
+
+
+
+
+
The following scalar objects are used for enabling the
responder,
+
+
In addition to the above objects, the following object is used
for obtaining information about the responder role on the
device,
+
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 | | : :
| +
| | +
| +
| |cMTSessionProfileName = rtp1 | | +
| +
| | +
| +
| |cMTSessionFlowSpecifierName = fs1| |
| +
| |
| +
| |cMTSessionTraceRouteEnabled = T | |
| +
| |
+
| |
| |
+
| cMTSessionNumber = 2 |
| +
| |cMTSessionPathSpecifierName = ps2| | |cMTMediaMonitorProfileTable|
| +
| | +
| +
| |cMTSessionParamName = sp5 | | | =rtp1 |
| +
| | | |
| +
| |cMTSessionProfileName = intf1 | | |cMTMediaMonitorProfileName |
| +
| | +
| +
| |cMTSessionTraceRouteEnabled = T | | : :
| +
| | |cMTMediaMonitorProfileName |
+
: : +
: : | |
+
| 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,
+
| System | CPU |
| | +
| |
| +
| |
| +
| Interface |
| +
| |
| | at ingress
| +
| +
| +
| +
| +
|
+
Media Monitor | TCP | IP | measurement confidence
| | metrics |
| | +
| | +
| | +
| | +
| | +
| | +
| | +
| | +
| | count
| |
| +
| specific | delay
| metrics |
| +
|
+
RTP | IP | confidence
| metrics |
| +
| +
| +
| +
| +
| +
| +
| +
|
+
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) +
+
+
session (2) +
+
+
| metric-list rtp
+
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.
ciscoMediatraceMIB OBJECT IDENTIFIER ::= { ciscoMgmt 800 }
ciscoMediatraceMIB MODULE-IDENTITY LAST-UPDATED "201208230000Z" ORGANIZATION "Cisco Systems, Inc." CONTACT-INFO "Cisco Systems Customer Service Postal: 170 W Tasman Drive San Jose, CA 95134 USA Tel: +1 800 553-NETS E-mail: [email protected]" DESCRIPTION "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, + + + + + In addition to the above objects, the following objects are used for obtaining information about the initiator role on the device, + + + + + + + + The following scalar objects are used for enabling the responder, + + In addition to the above objects, the following object is used for obtaining information about the responder role on the device, + 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 | | : : | + | | + | + | |cMTSessionProfileName = rtp1 | | + | + | | + | + | |cMTSessionFlowSpecifierName = fs1| | | + | | | + | |cMTSessionTraceRouteEnabled = T | | | + | | + | | | | + | cMTSessionNumber = 2 | | + | |cMTSessionPathSpecifierName = ps2| | |cMTMediaMonitorProfileTable| | + | | + | + | |cMTSessionParamName = sp5 | | | =rtp1 | | + | | | | | + | |cMTSessionProfileName = intf1 | | |cMTMediaMonitorProfileName | | + | | + | + | |cMTSessionTraceRouteEnabled = T | | : : | + | | |cMTMediaMonitorProfileName | + : : + : : | | + | 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, + | System | CPU | | | + | | | + | | | + | Interface | | + | | | | at ingress | + | + | + | + | + | + Media Monitor | TCP | IP | measurement confidence | | metrics | | | + | | + | | + | | + | | + | | + | | + | | + | | count | | | + | specific | delay | metrics | | + | + RTP | IP | confidence | metrics | | + | + | + | + | + | + | + | + | + 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) + + + session (2) + + + | metric-list rtp + 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." REVISION "201208230000Z" DESCRIPTION "Initial version of this MIB module." ::= { ciscoMgmt 800 }
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.9.9.800.0 | ciscoMediatraceMIBNotifs | 0 | 0 | None |
| 1.3.6.1.4.1.9.9.800.1 | ciscoMediatraceMIBObjects | 2 | 184 | None |
| 1.3.6.1.4.1.9.9.800.2 | ciscoMediatraceMIBConform | 2 | 4 | None |
To many brothers! Only 100 nearest brothers are shown.
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| ... | ||||
| 1.3.6.1.4.1.9.9.750 | ciscoCdstvIngestTuningMIB | 3 | 18 | This MIB module defines ingest tuning configuration objects that facilitate the management of the Cisco Content Delivery System f… |
| 1.3.6.1.4.1.9.9.751 | ciscoCdstvAuthmgrMIB | 3 | 25 | This MIB module defines objects that describe the configuration of the authentication manager for the Cisco Content Delivery Syst… |
| 1.3.6.1.4.1.9.9.753 | ciscoVideoSessionMIB | 3 | 145 | This MIB module complements the CISCO-VOICE-DIAL-CONTROL-MIB, which provides voice telephony peer information, by providing manag… |
| 1.3.6.1.4.1.9.9.754 | ciscoCdstvServerMIB | 3 | 82 | This MIB module defines server configuration that faciliate the management of the Cisco Content Delivery System for TV (CDS-TV) … |
| 1.3.6.1.4.1.9.9.755 | ciscoCdstvIsaMIB | 3 | 145 | This MIB module defines ISA configuration objects that faciliate the management of the Cisco Content Delivery System for TV (CDS-… |
| 1.3.6.1.4.1.9.9.756 | ciscoEntityPerformanceMIB | 3 | 56 | This MIB module defines managed objects that facilitate to monitor performance of any physical entity, which are listed in the EN… |
| 1.3.6.1.4.1.9.9.757 | ciscoSbcStatsMIB | 3 | 106 | The main purpose of this MIB is to define the statistics information for Session Border Controller application. This MIB categori… |
| 1.3.6.1.4.1.9.9.758 | ciscoTelepresenceExchangeSystemMIB | 3 | 173 | The main purpose of this MIB is to provide product component level configuration, status, statistics, events, and alarm notificat… |
| 1.3.6.1.4.1.9.9.759 | ciscoGdoiMIB | 3 | 213 | This MIB module defines objects for managing the GDOI protocol. Copyright (c) The IETF Trust (2010). This version of this MIB mo… |
| 1.3.6.1.4.1.9.9.760 | ciscoPtpMIB | 3 | 182 | The MIB module for PTPv2 (IEEE1588 - 2008) Overview of PTPv2 (IEEE 1588-2008) This IEEE standard defines a protocol enabling prec… |
| 1.3.6.1.4.1.9.9.761 | ciscoNetsyncMIB | 3 | 104 | The Synchronous Ethernet (SyncE) MIB is defined for monitoring network synchronization based on ITU-T G.781 clock selection. Sync… |
| 1.3.6.1.4.1.9.9.762 | ciscoWanOptimizationMIB | 3 | 302 | This MIB is for managing Wide Area Network (WAN) Optimization systems. The objective of WAN optimization system is to reduce as m… |
| 1.3.6.1.4.1.9.9.763 | ciscoVideoTc | 0 | 0 | This MIB module defines a collection of common video-related textual conventions to be used in Cisco MIBS for video-capable produ… |
| 1.3.6.1.4.1.9.9.764 | ciscoUbeMIB | 2 | 12 | This MIB describes objects used for managing Cisco Unified Border Element (CUBE). The Cisco Unified Border Element (CUBE) is a Ci… |
| 1.3.6.1.4.1.9.9.765 | ciscoFlowCloneMIB | 3 | 44 | This MIB module defines objects that manages flow cloning feature. A flow cloning can be described as a hardware or software enti… |
| 1.3.6.1.4.1.9.9.766 | ciscoIpslaVideoProfileMIB | 3 | 29 | IP SLA is a capability which utilizes active monitoring for network performance. It can be used for network troubleshooting, net… |
| 1.3.6.1.4.1.9.9.767 | ciscoLwappDot11ClientRmMIB | 3 | 64 | This MIB is intended to be implemented on all those devices operating as Central controllers, that terminate the Light Weight Acc… |
| 1.3.6.1.4.1.9.9.768 | ciscoEntitySensorHistoryMIB | 2 | 20 | This MIB module defines objects that describe collections and measurement information for each sensor supporting historical data … |
| 1.3.6.1.4.1.9.9.769 | ciscoMediaQualityMIB | 3 | 214 | This MIB module enhances the DIAL-CONTROL-MIB (RFC2128) by providing call information and voice and video quality statistics of c… |
| 1.3.6.1.4.1.9.9.770 | ciscoTcpMetricsMIB | 4 | 22 | This MIB module defines objects that describe the quality metrics of TCP streams. GLOSSARY ============ Flow Monitor - a hardware o… |
| 1.3.6.1.4.1.9.9.771 | ciscoMediaMetricsMIB | 4 | 38 | This MIB module defines objects that describe the quality metrics of Media streams. GLOSSARY ============ Flow Monitor - a hardware… |
| 1.3.6.1.4.1.9.9.772 | ciscoPfrMIB | 3 | 303 | This MIB module defines objects that describe Performance Routing (PfR). Standard routing protocols base routing decisions on re… |
| 1.3.6.1.4.1.9.9.773 | ciscoSwitchRateLimiterMIB | 3 | 28 | This MIB module defines management objects for the Switch Rate Limiter features on Cisco Layer 2 and Layer 3 devices. Rate limits … |
| 1.3.6.1.4.1.9.9.774 | ciscoVdcMIB | 3 | 90 | CISCO-VDC-MIB |
| 1.3.6.1.4.1.9.9.775 | ciscoSelectiveVrfDownloadMIB | 3 | 41 | This MIB module defines objects describing selective VRF download. The selective VRF download feature makes a best effort to dow… |
| 1.3.6.1.4.1.9.9.776 | ciscoNetflowLiteMIB | 3 | 56 | This MIB provides a method to configure Netflow-lite feature and get information in these areas: 1. Exporter config information a… |
| 1.3.6.1.4.1.9.9.777 | ciscoDsgIfExtMIB | 3 | 15 | A MIB module for extending the DSG-IF-MIB (ITU-T J.128 10/2008) to add objects which provide additional management information ab… |
| 1.3.6.1.4.1.9.9.779 | ciscoPmonMIB | 3 | 14 | This MIB module is for providing the port monitoring information. |
| 1.3.6.1.4.1.9.9.782 | ciscoSubscriberIdentityTcMIB | 0 | 0 | This MIB module defines textual conventions describing subscriber session identities. A subscriber session identity consists of … |
| 1.3.6.1.4.1.9.9.783 | ciscoDynamicTemplateTcMIB | 0 | 0 | This MIB module defines textual conventions used by the CISCO-DYNAMIC-TEMPLATE-MIB and MIB modules that use and expand on dynamic… |
| 1.3.6.1.4.1.9.9.784 | ciscoDynamicTemplateMIB | 3 | 152 | This MIB defines objects that describe dynamic templates. A dynamic template is a set of configuration attributes that a system … |
| 1.3.6.1.4.1.9.9.785 | ciscoSubscriberSessionTcMIB | 0 | 0 | This MIB module defines textual conventions describing subscriber sessions. |
| 1.3.6.1.4.1.9.9.786 | ciscoSubscriberSessionMIB | 3 | 187 | This MIB defines objects describing subscriber sessions, or more specifically, subscriber sessions terminated by a RAS. A subscr… |
| 1.3.6.1.4.1.9.9.789 | ciscoFlowMetadataMIB | 3 | 30 | The MIB module for managing Cisco medianet flow metadata. Metadata, in the simplest form, is data that qualifies other data. Flow… |
| 1.3.6.1.4.1.9.9.790 | ciscoSwitchCefMIB | 3 | 33 | This MIB module defines management objects for the CEF features on Cisco Layer 2 and Layer 3 devices. Definition of some of the t… |
| 1.3.6.1.4.1.9.9.791 | ciscoAppNavMIB | 2 | 51 | This MIB module defines SNMP management objects describing the AppNav technology. A device, which implements the AppNav technolog… |
| 1.3.6.1.4.1.9.9.793 | ciscoMspMIB | 3 | 54 | Objective of media services proxy is to provide media services to end-points and its flows identified by a set of protocols. Medi… |
| 1.3.6.1.4.1.9.9.798 | ciscoLocalAuthUserMIB | 3 | 40 | This MIB module defines objects describing users authenticated locally by a Network Access Server (NAS). + | | | … |
| 1.3.6.1.4.1.9.9.801 | ciscoFabricPathTopologyMIB | 3 | 40 | This MIB module defines managed objects that facilitate the management of Cisco's FabricPath Topology technology. |
| 1.3.6.1.4.1.9.9.803 | ciscoSwitchFabricMIB | 3 | 30 | This MIB module defined managed objects that facilitates the management of switching fabric information in a Cisco switch. |
| 1.3.6.1.4.1.9.9.804 | ciscoHardwareIpVerifyMIB | 3 | 13 | This MIB module defines management objects for configuration and monitoring of the Intrusion Detection System (IDS) that checks f… |
| 1.3.6.1.4.1.9.9.806 | ciscoL2natMIB | 2 | 80 | Network Address Translation (NAT) involves translating the source and or destination IP addresses of packets as they traverse fro… |
| 1.3.6.1.4.1.9.9.807 | ciscoVpcMIB | 3 | 73 | This MIB module defines MIB objects which provide management information for configuring and monitoring of Virtual Port Channel(V… |
| 1.3.6.1.4.1.9.9.808 | ciscoACLMIB | 2 | 87 | This MIB module defines objects that describe Cisco Access Control Lists (ACL). This MIB describes different objects that enable … |
| 1.3.6.1.4.1.9.9.809 | ciscoWebExMeetingMIB | 3 | 58 | Cisco WebEx Collaboration Host is a software-only system, with hardware independence a key goal. To that end, it will be designed… |
| 1.3.6.1.4.1.9.9.810 | ciscoOtvMIB | 3 | 129 | This MIB module is for configuration & statistic query of Overlay Transport Virtualization (OTV) functionality on Cisco routers a… |
| 1.3.6.1.4.1.9.9.811 | ciscoVlanIfTableRelationshipMIB | 1 | 12 | None |
| 1.3.6.1.4.1.9.9.812 | ciscoLptsMIB | 3 | 22 | The MIB module for Local Packet Transport Services(LPTS) related information like the flows and the policer values related to var… |
| 1.3.6.1.4.1.9.9.813 | ciscoPfcExtMIB | 3 | 27 | This MIB module defines management objects for monitoring information of Priority-based Flow Control. The following terms are used… |
| 1.3.6.1.4.1.9.9.814 | ciscoLivedataMIB | 3 | 57 | Cisco LiveData is the next generation reporting product for Cisco Unified Contact Center Enterprise (CCE). Cisco LiveData provid… |
| 1.3.6.1.4.1.9.9.816 | ciscoVpnLicUsageMonitorMIB | 2 | 60 | Acronyms and Definitions The following acronyms and terms are used in this document: IPSec: Secure IP Protocol VPN: Virtual Priva… |
| 1.3.6.1.4.1.9.9.817 | ciscoWanCellExtMIB | 3 | 81 | This MIB module is an extension of CISCO-WAN-3G-MIB.my, and it provides network management support for Cisco cellular WAN 4G/LTE p… |
| 1.3.6.1.4.1.9.9.818 | ciscoNatCgnExtMIB | 3 | 69 | This MIB module extends the IETF draft NAT MIB available at http://tools.ietf.org/html/draft-ietf-behave-nat-mib-11 The extension… |
| 1.3.6.1.4.1.9.9.819 | ciscoWpanMIB | 3 | 25 | This MIB module defines management objects for configuration and monitoring of Wireless Personal Area Network (WPAN). Personal Are… |
| 1.3.6.1.4.1.9.9.820 | ciscoNetworkVirtualizationOverlayMIB | 3 | 61 | This MIB module is for managing Network Virtualization Overlay functionality on Cisco devices. The following terms are used throu… |
| 1.3.6.1.4.1.9.9.821 | ciscoCableIronBusStatMIB | 3 | 22 | This is the MIB module for Cable Iron Bus Statistics for DOCSIS-compliant Cable Modem Termination Systems (CMTS). The Statistics … |
| 1.3.6.1.4.1.9.9.822 | ciscoDtiExtMIB | 3 | 12 | This MIB module provides the trap objects necessary to monitor the DOCSIS Timing Interface devices. |
| 1.3.6.1.4.1.9.9.824 | ciscoQpLbgMIB | 3 | 74 | This MIB module represents the Qam-Partition (QP) and Load Balance Group (LBG) parameters in the headend and it is supported by … |
| 1.3.6.1.4.1.9.9.825 | ciscoLispExtMIB | 3 | 77 | This MIB is an extension to the IETF LISP-MIB module defined in RFC 7052. It contains Cisco defined managed objects and traps to … |
| 1.3.6.1.4.1.9.9.827 | ciscoUspMIB | 3 | 80 | The MIB Module for the management of the Cisco Unified SIP Proxy (CUSP) service. CUSP is a Session Initiation Protocol (SIP) prox… |
| 1.3.6.1.4.1.9.9.828 | ciscoOpticalMIB | 3 | 176 | This MIB module defines the managed objects for physical layer characteristics of optical interfaces and performance statistics o… |
| 1.3.6.1.4.1.9.9.829 | ciscoSslvpnMIB | 3 | 53 | This MIB module defines management objects for configuration and monitoring of the Cisco secure gateway that implements SSLVPN. Gl… |
| 1.3.6.1.4.1.9.9.831 | ciscoSmartLicMIB | 3 | 78 | The MIB module for managing licenses on the system. The licensing mechanism provides flexibility to enforce licensing for various… |
| ... | ||||