This MIB module defines objects that manages flow cloning
feature. A flow cloning can be described as a hardware or
software entity, that is responsible to clone (or duplicate)
flows to the specified destination port in the device. These
cloned packets will be sent to an external device for a more
fine-grained analysis of the flows. A typical application of
this MIB module will facilitate cloning media flows. However,
by no means does the definition of this MIB module prevents
other applications from using it.
CLONE PROFILE:
==============
At the top level, this MIB module describes the notion of flow
cloning. Further descriptive texts in this MIB will use clone
profile to describe flow cloning. We can think of clone profile
as a container for the traffic flows for which it will clone
packets and send out on the specified egress interface. Because
a device can support more than one clone profile, this MIB
defines cfcCloneProfileTable.
TRAFFIC FLOW:
=============
At the next level, this MIB module describes the notion of a
traffic flow associated with the clone profile. A traffic flow
is 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.
CLONE TARGET:
=============
A clone target may represent an entity that the system
provisions with a clone profile.
Clone targets include, but are not necessarily limited to, the
system, nodes (i.e., an instance of an operating system),
interfaces, VRF instances, and bridge domains.
IMPLEMENTATION GUIDANCE
=======================
It might seem that the concepts presented by this MIB module
lend themselves to a profile-based approach. However, this
approach provides the most general abstraction and lends itself
to implementations that can fall under two categories: global
and per-interface.
A global level clone profile will clone the specified flows
that are monitored in the whole device. Per interface clone
profile will clone the specified flows that are monitored on
the specified interface.
This MIB module can represent the global level clone profile
using the following procedure:
o Create a row in the cfcCloneProfileTable having the following
attributes. Allocate a value for cfcCloneProfileId and a name
for cfcCloneProfileName. For sake of discussion, let's say
the value is
cfcCloneProfileId =
cfcCloneProfileName =
.
.
cfcCloneTargetType = 'system'
o Similarly per interface level clone profile implementation
can be represented as follows.
Create a row in the cfcCloneProfileTable having the following
attributes. Allocate a value for cfcCloneProfileId and a name
for cfcCloneProfileName. For sake of discussion, let's say
the value is
cfcCloneProfileId =
cfcCloneProfileName =
.
.
cfcCloneTargetType = 'interface'
cfcCloneTargetIfIndex =
While this example illustrates how an implementation may
represent global and per-interface configuration data, it is
understood that an implementation may have other requirements.
In these cases, use this example as a guide in satisfying these
requirements.
Parsed from file CISCO-FLOW-CLONE-MIB.mib
Module: CISCO-FLOW-CLONE-MIB
This MIB module defines objects that manages flow cloning
feature. A flow cloning can be described as a hardware or
software entity, that is responsible to clone (or duplicate)
flows to the specified destination port in the device. These
cloned packets will be sent to an external device for a more
fine-grained analysis of the flows. A typical application of
this MIB module will facilitate cloning media flows. However,
by no means does the definition of this MIB module prevents
other applications from using it.
CLONE PROFILE:
==============
At the top level, this MIB module describes the notion of flow
cloning. Further descriptive texts in this MIB will use clone
profile to describe flow cloning. We can think of clone profile
as a container for the traffic flows for which it will clone
packets and send out on the specified egress interface. Because
a device can support more than one clone profile, this MIB
defines cfcCloneProfileTable.
TRAFFIC FLOW:
=============
At the next level, this MIB module describes the notion of a
traffic flow associated with the clone profile. A traffic flow
is 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.
CLONE TARGET:
=============
A clone target may represent an entity that the system
provisions with a clone profile.
Clone targets include, but are not necessarily limited to, the
system, nodes (i.e., an instance of an operating system),
interfaces, VRF instances, and bridge domains.
IMPLEMENTATION GUIDANCE
=======================
It might seem that the concepts presented by this MIB module
lend themselves to a profile-based approach. However, this
approach provides the most general abstraction and lends itself
to implementations that can fall under two categories: global
and per-interface.
A global level clone profile will clone the specified flows
that are monitored in the whole device. Per interface clone
profile will clone the specified flows that are monitored on
the specified interface.
This MIB module can represent the global level clone profile
using the following procedure:
o Create a row in the cfcCloneProfileTable having the following
attributes. Allocate a value for cfcCloneProfileId and a name
for cfcCloneProfileName. For sake of discussion, let's say
the value is
cfcCloneProfileId =
cfcCloneProfileName =
.
.
cfcCloneTargetType = 'system'
o Similarly per interface level clone profile implementation
can be represented as follows.
Create a row in the cfcCloneProfileTable having the following
attributes. Allocate a value for cfcCloneProfileId and a name
for cfcCloneProfileName. For sake of discussion, let's say
the value is
cfcCloneProfileId =
cfcCloneProfileName =
.
.
cfcCloneTargetType = 'interface'
cfcCloneTargetIfIndex =
While this example illustrates how an implementation may
represent global and per-interface configuration data, it is
understood that an implementation may have other requirements.
In these cases, use this example as a guide in satisfying these
requirements.
Parsed from file CISCO-FLOW-CLONE-MIB.my.txt
Company: None
Module: CISCO-FLOW-CLONE-MIB
This MIB module defines objects that manages flow cloning
feature. A flow cloning can be described as a hardware or
software entity, that is responsible to clone (or duplicate)
flows to the specified destination port in the device. These
cloned packets will be sent to an external device for a more
fine-grained analysis of the flows. A typical application of
this MIB module will facilitate cloning media flows. However,
by no means does the definition of this MIB module prevents
other applications from using it.
CLONE PROFILE:
==============
At the top level, this MIB module describes the notion of flow
cloning. Further descriptive texts in this MIB will use clone
profile to describe flow cloning. We can think of clone profile
as a container for the traffic flows for which it will clone
packets and send out on the specified egress interface. Because
a device can support more than one clone profile, this MIB
defines cfcCloneProfileTable.
TRAFFIC FLOW:
=============
At the next level, this MIB module describes the notion of a
traffic flow associated with the clone profile. A traffic flow
is 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.
CLONE TARGET:
=============
A clone target may represent an entity that the system
provisions with a clone profile.
Clone targets include, but are not necessarily limited to, the
system, nodes (i.e., an instance of an operating system),
interfaces, VRF instances, and bridge domains.
IMPLEMENTATION GUIDANCE
=======================
It might seem that the concepts presented by this MIB module
lend themselves to a profile-based approach. However, this
approach provides the most general abstraction and lends itself
to implementations that can fall under two categories: global
and per-interface.
A global level clone profile will clone the specified flows
that are monitored in the whole device. Per interface clone
profile will clone the specified flows that are monitored on
the specified interface.
This MIB module can represent the global level clone profile
using the following procedure:
o Create a row in the cfcCloneProfileTable having the following
attributes. Allocate a value for cfcCloneProfileId and a name
for cfcCloneProfileName. For sake of discussion, let's say
the value is
cfcCloneProfileId =
cfcCloneProfileName =
.
.
cfcCloneTargetType = 'system'
o Similarly per interface level clone profile implementation
can be represented as follows.
Create a row in the cfcCloneProfileTable having the following
attributes. Allocate a value for cfcCloneProfileId and a name
for cfcCloneProfileName. For sake of discussion, let's say
the value is
cfcCloneProfileId =
cfcCloneProfileName =
.
.
cfcCloneTargetType = 'interface'
cfcCloneTargetIfIndex =
While this example illustrates how an implementation may
represent global and per-interface configuration data, it is
understood that an implementation may have other requirements.
In these cases, use this example as a guide in satisfying these
requirements.
ciscoFlowCloneMIB MODULE-IDENTITY LAST-UPDATED "201010190000Z" ORGANIZATION "Cisco Systems, Inc." CONTACT-INFO "Cisco Systems Customer Service Postal: 170 West Tasman Drive San Jose, CA 95134 USA Tel: +1 800 553-NETS E-mail: [email protected]" DESCRIPTION "This MIB module defines objects that manages flow cloning feature. A flow cloning can be described as a hardware or software entity, that is responsible to clone (or duplicate) flows to the specified destination port in the device. These cloned packets will be sent to an external device for a more fine-grained analysis of the flows. A typical application of this MIB module will facilitate cloning media flows. However, by no means does the definition of this MIB module prevents other applications from using it. CLONE PROFILE: ============== At the top level, this MIB module describes the notion of flow cloning. Further descriptive texts in this MIB will use clone profile to describe flow cloning. We can think of clone profile as a container for the traffic flows for which it will clone packets and send out on the specified egress interface. Because a device can support more than one clone profile, this MIB defines cfcCloneProfileTable. TRAFFIC FLOW: ============= At the next level, this MIB module describes the notion of a traffic flow associated with the clone profile. A traffic flow is 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. CLONE TARGET: ============= A clone target may represent an entity that the system provisions with a clone profile. Clone targets include, but are not necessarily limited to, the system, nodes (i.e., an instance of an operating system), interfaces, VRF instances, and bridge domains. IMPLEMENTATION GUIDANCE ======================= It might seem that the concepts presented by this MIB module lend themselves to a profile-based approach. However, this approach provides the most general abstraction and lends itself to implementations that can fall under two categories: global and per-interface. A global level clone profile will clone the specified flows that are monitored in the whole device. Per interface clone profile will clone the specified flows that are monitored on the specified interface. This MIB module can represent the global level clone profile using the following procedure: o Create a row in the cfcCloneProfileTable having the following attributes. Allocate a value for cfcCloneProfileId and a name for cfcCloneProfileName. For sake of discussion, let's say the value is
and the name is 'XYZ'. cfcCloneProfileId = cfcCloneProfileName = . . cfcCloneTargetType = 'system' o Similarly per interface level clone profile implementation can be represented as follows. Create a row in the cfcCloneProfileTable having the following attributes. Allocate a value for cfcCloneProfileId and a name for cfcCloneProfileName. For sake of discussion, let's say the value is and the name is 'ABC'. cfcCloneProfileId = cfcCloneProfileName = . . cfcCloneTargetType = 'interface' cfcCloneTargetIfIndex = While this example illustrates how an implementation may represent global and per-interface configuration data, it is understood that an implementation may have other requirements. In these cases, use this example as a guide in satisfying these requirements." REVISION "201007080000Z" DESCRIPTION "Added: The initial version of the MIB module" ::= { ciscoMgmt 765 }
ciscoFlowCloneMIB OBJECT IDENTIFIER ::= { ciscoMgmt 765 }
Vendor: Cisco
Module: CISCO-FLOW-CLONE-MIB
[Automatically extracted from oidview.com]
ciscoFlowCloneMIB MODULE-IDENTITY LAST-UPDATED "201010190000Z" ORGANIZATION "Cisco Systems, Inc." CONTACT-INFO "Cisco Systems Customer Service Postal: 170 West Tasman Drive San Jose, CA 95134 USA Tel: +1 800 553-NETS E-mail: [email protected]" DESCRIPTION "This MIB module defines objects that manages flow cloning feature. A flow cloning can be described as a hardware or software entity, that is responsible to clone (or duplicate) flows to the specified destination port in the device. These cloned packets will be sent to an external device for a more fine-grained analysis of the flows. A typical application of this MIB module will facilitate cloning media flows. However, by no means does the definition of this MIB module prevents other applications from using it. CLONE PROFILE: ============== At the top level, this MIB module describes the notion of flow cloning. Further descriptive texts in this MIB will use clone profile to describe flow cloning. We can think of clone profile as a container for the traffic flows for which it will clone packets and send out on the specified egress interface. Because a device can support more than one clone profile, this MIB defines cfcCloneProfileTable. TRAFFIC FLOW: ============= At the next level, this MIB module describes the notion of a traffic flow associated with the clone profile. A traffic flow is 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. CLONE TARGET: ============= A clone target may represent an entity that the system provisions with a clone profile. Clone targets include, but are not necessarily limited to, the system, nodes (i.e., an instance of an operating system), interfaces, VRF instances, and bridge domains. IMPLEMENTATION GUIDANCE ======================= It might seem that the concepts presented by this MIB module lend themselves to a profile-based approach. However, this approach provides the most general abstraction and lends itself to implementations that can fall under two categories: global and per-interface. A global level clone profile will clone the specified flows that are monitored in the whole device. Per interface clone profile will clone the specified flows that are monitored on the specified interface. This MIB module can represent the global level clone profile using the following procedure: o Create a row in the cfcCloneProfileTable having the following attributes. Allocate a value for cfcCloneProfileId and a name for cfcCloneProfileName. For sake of discussion, let's say the value is
and the name is 'XYZ'. cfcCloneProfileId = cfcCloneProfileName = . . cfcCloneTargetType = 'system' o Similarly per interface level clone profile implementation can be represented as follows. Create a row in the cfcCloneProfileTable having the following attributes. Allocate a value for cfcCloneProfileId and a name for cfcCloneProfileName. For sake of discussion, let's say the value is and the name is 'ABC'. cfcCloneProfileId = cfcCloneProfileName = . . cfcCloneTargetType = 'interface' cfcCloneTargetIfIndex = While this example illustrates how an implementation may represent global and per-interface configuration data, it is understood that an implementation may have other requirements. In these cases, use this example as a guide in satisfying these requirements." REVISION "201007080000Z" DESCRIPTION "Added: The initial version of the MIB module" ::= { ciscoMgmt 765 }
ciscoFlowCloneMIB MODULE-IDENTITY LAST-UPDATED "201010190000Z" ORGANIZATION "Cisco Systems, Inc." CONTACT-INFO "Cisco Systems Customer Service Postal: 170 West Tasman Drive San Jose, CA 95134 USA Tel: +1 800 553-NETS E-mail: [email protected]" DESCRIPTION "This MIB module defines objects that manages flow cloning feature. A flow cloning can be described as a hardware or software entity, that is responsible to clone (or duplicate) flows to the specified destination port in the device. These cloned packets will be sent to an external device for a more fine-grained analysis of the flows. A typical application of this MIB module will facilitate cloning media flows. However, by no means does the definition of this MIB module prevents other applications from using it. CLONE PROFILE: ============== At the top level, this MIB module describes the notion of flow cloning. Further descriptive texts in this MIB will use clone profile to describe flow cloning. We can think of clone profile as a container for the traffic flows for which it will clone packets and send out on the specified egress interface. Because a device can support more than one clone profile, this MIB defines cfcCloneProfileTable. TRAFFIC FLOW: ============= At the next level, this MIB module describes the notion of a traffic flow associated with the clone profile. A traffic flow is 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. CLONE TARGET: ============= A clone target may represent an entity that the system provisions with a clone profile. Clone targets include, but are not necessarily limited to, the system, nodes (i.e., an instance of an operating system), interfaces, VRF instances, and bridge domains. IMPLEMENTATION GUIDANCE ======================= It might seem that the concepts presented by this MIB module lend themselves to a profile-based approach. However, this approach provides the most general abstraction and lends itself to implementations that can fall under two categories: global and per-interface. A global level clone profile will clone the specified flows that are monitored in the whole device. Per interface clone profile will clone the specified flows that are monitored on the specified interface. This MIB module can represent the global level clone profile using the following procedure: o Create a row in the cfcCloneProfileTable having the following attributes. Allocate a value for cfcCloneProfileId and a name for cfcCloneProfileName. For sake of discussion, let's say the value is
and the name is 'XYZ'. cfcCloneProfileId = cfcCloneProfileName = . . cfcCloneTargetType = 'system' o Similarly per interface level clone profile implementation can be represented as follows. Create a row in the cfcCloneProfileTable having the following attributes. Allocate a value for cfcCloneProfileId and a name for cfcCloneProfileName. For sake of discussion, let's say the value is and the name is 'ABC'. cfcCloneProfileId = cfcCloneProfileName = . . cfcCloneTargetType = 'interface' cfcCloneTargetIfIndex = While this example illustrates how an implementation may represent global and per-interface configuration data, it is understood that an implementation may have other requirements. In these cases, use this example as a guide in satisfying these requirements." REVISION "201007080000Z" DESCRIPTION "Added: The initial version of the MIB module" ::= { ciscoMgmt 765 }
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.9.9.765.0 | ciscoFlowCloneMIBNotifications | 0 | 0 | None |
| 1.3.6.1.4.1.9.9.765.1 | ciscoFlowCloneMIBObjects | 3 | 35 | None |
| 1.3.6.1.4.1.9.9.765.2 | ciscoFlowCloneMIBConformance | 2 | 6 | 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.715 | ciscoEntityQfpMIB | 3 | 82 | This MIB module defines managed objects that facilitate the management of Quantum Flow Processors (QFP), which are listed in the … |
| 1.3.6.1.4.1.9.9.716 | ciscoVoIpTapMIB | 3 | 18 | This module manages Cisco's intercept feature for Voice over IP (VoIP). This MIB is used along with CISCO-TAP2-MIB to intercept V… |
| 1.3.6.1.4.1.9.9.718 | ciscoCuicappsMIB | 3 | 130 | The Cisco Unified Intelligence Center (CUIC) is a scalable robust and secure reporting solution for contact center applications. T… |
| 1.3.6.1.4.1.9.9.719 | ciscoUnifiedComputingMIB | 5 | 13463 | This MIB module defines the managed objects for Unified Computing System (UCS) Manager. Cisco UCS Manager provides centralized m… |
| 1.3.6.1.4.1.9.9.720 | ciscoTrustSecSxpMIB | 3 | 140 | This MIB module is for the configuration and status query of SGT Exchange Protocol over TCP (SXPoTCP) feature of the device on th… |
| 1.3.6.1.4.1.9.9.721 | ciscoMldSnoopingMIB | 3 | 215 | This MIB module defines objects that describe IGMP/MLD snooping. It provides remote network management system the ability to manag… |
| 1.3.6.1.4.1.9.9.724 | cggsnGeoMIB | 2 | 12 | This MIB provide additional information for passive interface configured for each OSPF process, independent of object creation in… |
| 1.3.6.1.4.1.9.9.725 | ciscoSmartInstallMIB | 3 | 101 | This MIB module defines managed objects that facilitate the management of Smart Install feature. Smart Install is a plug-and-pla… |
| 1.3.6.1.4.1.9.9.729 | ciscoCdstvServicesMIB | 3 | 21 | This MIB module defines service monitoring objects that faciliate the management of the Cisco Content Delivery System for TV (CDS… |
| 1.3.6.1.4.1.9.9.730 | ciscoTrustSecMIB | 3 | 128 | This MIB module is for the configuration of a network device on the Cisco Trusted Security (TrustSec) system. TrustSec secures a … |
| 1.3.6.1.4.1.9.9.731 | ciscoEpcGatewayMIB | 3 | 130 | This MIB module manages the features and configuration for PDN Gateway(PGW) and Serving Gateway(SGW) in Evolved Packet Core(EPC) … |
| 1.3.6.1.4.1.9.9.732 | ciscoDeviceLocationMIB | 3 | 49 | This MIB is used for managing location information of end point devices(Telepresence, IP Camera, Digital media player etc) connec… |
| 1.3.6.1.4.1.9.9.733 | ciscoMeetingPlaceMIB | 3 | 70 | This MIB allows management of Cisco Unified MeetingPlace (CUMP) features, CUMP is the key conferencing solution component for Cis… |
| 1.3.6.1.4.1.9.9.734 | ciscoGtpv2MIB | 2 | 160 | This MIB module manages the GPRS Tunneling Protocol version 2(GTPv2) statistics for the Evolved Packet Core(EPC) architecture. SGW… |
| 1.3.6.1.4.1.9.9.735 | ciscoCdstvFsiMIB | 3 | 25 | This MIB module defines FSI configurartion objects that faciliate the management of the Cisco Content Delivery System for TV (CDS… |
| 1.3.6.1.4.1.9.9.736 | ciscoRadiusExtMIB | 2 | 51 | This MIB module defines objects describing RADIUS (Remote Access Dialin User Service), serving as an extension of the following M… |
| 1.3.6.1.4.1.9.9.737 | ciscoSwitchNetflowMIB | 3 | 40 | This MIB module defines management objects for the Netflow features on Cisco Layer 2 and Layer 3 devices. |
| 1.3.6.1.4.1.9.9.738 | cmplsTeStdExtMIB | 3 | 72 | This MIB module contains Cisco specific managed object definitions for MPLS Traffic Engineering (TE), not contained in MPLS-TE-ST… |
| 1.3.6.1.4.1.9.9.739 | ciscoCdstvIngestmgrMIB | 3 | 69 | This MIB module defines ingest manager configuration objects that faciliate the management of the Cisco Content Delivery System f… |
| 1.3.6.1.4.1.9.9.740 | ciscoTrustSecIfMIB | 3 | 143 | This MIB module defines management objects for configuration and monitoring of the interfaces in Cisco Trusted Security environme… |
| 1.3.6.1.4.1.9.9.741 | ciscoTrustSecServerMIB | 3 | 85 | This MIB module defines management objects for configuration and monitoring of the AAA servers in Cisco Trusted Security environm… |
| 1.3.6.1.4.1.9.9.742 | ciscoIpAddressPoolTcMIB | 0 | 0 | This MIB module defines textual conventions used by MIB modules defining objects describing IP address pools. |
| 1.3.6.1.4.1.9.9.743 | ciscoCdstvCsStatsMIB | 3 | 83 | This MIB module defines objects describing the caching and streaming statistics objects that facilitate the management of the Cis… |
| 1.3.6.1.4.1.9.9.744 | ciscoIpslaVideoMIB | 3 | 73 | 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.745 | ciscoEntitySensorExtMIB | 3 | 21 | This MIB is extension to ENTITY-SENSOR-MIB(RFC 3433). This MIB also defines the notifications applicable for sensors reported in … |
| 1.3.6.1.4.1.9.9.748 | ciscoIpAddressPoolMIB | 3 | 96 | This MIB modules defines objects that describe common aspects of IP address pools. IP Address Pool Manager =======================… |
| 1.3.6.1.4.1.9.9.749 | ciscoCdstvBwmgrMIB | 3 | 21 | This MIB module defines Bandwidth Manager configuration objects that facilitate the management of the Cisco Content Delivery Syst… |
| 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.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.800 | ciscoMediatraceMIB | 3 | 191 | Mediatrace helps to isolate and troubleshoot network degradation problems by enabling a network administrator to discover an Inte… |
| 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… |
| ... | ||||