A single SNMP agent sometimes needs to support multiple
instances of the same MIB module, and does so through the
use of multiple SNMP contexts. This typically occurs because
the technology has evolved to have extra dimension(s), i.e.,
one or more extra data and/or identifier values which are
different in the different contexts, but were not defined in
INDEX clause(s) of the original MIB module. In such cases,
network management applications need to know the specific
data/identifier values in each context, and this MIB module
provides mapping tables which contain that information.
Within a network there can be multiple Virtual Private
Networks (VPNs) configured using Virtual Routing and
Forwarding Instances (VRFs). Within a VPN there can be
multiple topologies when Multi-topology Routing (MTR) is
used. Also, Interior Gateway Protocols (IGPs) can have
multiple protocol instances running on the device.
A network can have multiple broadcast domains configured
using Bridge Domain Identifiers.
With MTR routing, VRFs, and Bridge domains, a router now
needs to support multiple instances of several existing
MIB modules, and this can be achieved if the router's SNMP
agent provides access to each instance of the same MIB module
via a different SNMP context (see Section 3.1.1 of RFC 3411).
For MTR routing, VRFs, and Bridge domains, a different SNMP
context is needed depending on one or more of the following:
the VRF, the topology-identifier, the routing protocol instance,
and the bridge domain identifier.
In other words, the router's management information can be
accessed through multiple SNMP contexts where each such
context represents a specific VRF, a specific
topology-identifier, a specific routing protocol instance
and/or a bridge domain identifier. This MIB module provides
a mapping of each such SNMP context to the corresponding VRF,
the corresponding topology, the corresponding routing protocol
instance, and the corresponding bridge domain identifier.
Some SNMP contexts are independent of VRFs, independent of
a topology, independent of a routing protocol instance, or
independent of a bridge domain and in such a case, the mapping
is to the zero length string.
With the Cisco package licensing strategy, the features
available in the image are grouped into multiple packages
and each packages can be managed to operate at different
feature levels based on the available license. This MIB
module provides option to associate an SNMP context to a
feature package group. This will allow manageability of
license MIB objects specific to a feature package group.
As technology evolves more we may need additional
identifiers to identify the context. Then we would need
to add those additional identifiers into the mapping.
Parsed from file CISCO-CONTEXT-MAPPING-MIB.mib
Module: CISCO-CONTEXT-MAPPING-MIB
A single SNMP agent sometimes needs to support multiple
instances of the same MIB module, and does so through the
use of multiple SNMP contexts. This typically occurs because
the technology has evolved to have extra dimension(s), i.e.,
one or more extra data and/or identifier values which are
different in the different contexts, but were not defined in
INDEX clause(s) of the original MIB module. In such cases,
network management applications need to know the specific
data/identifier values in each context, and this MIB module
provides mapping tables which contain that information.
Within a network there can be multiple Virtual Private
Networks (VPNs) configured using Virtual Routing and
Forwarding Instances (VRFs). Within a VPN there can be
multiple topologies when Multi-topology Routing (MTR) is
used. Also, Interior Gateway Protocols (IGPs) can have
multiple protocol instances running on the device.
A network can have multiple broadcast domains configured
using Bridge Domain Identifiers.
With MTR routing, VRFs, and Bridge domains, a router now
needs to support multiple instances of several existing
MIB modules, and this can be achieved if the router's SNMP
agent provides access to each instance of the same MIB module
via a different SNMP context (see Section 3.1.1 of RFC 3411).
For MTR routing, VRFs, and Bridge domains, a different SNMP
context is needed depending on one or more of the following:
the VRF, the topology-identifier, the routing protocol instance,
and the bridge domain identifier.
In other words, the router's management information can be
accessed through multiple SNMP contexts where each such
context represents a specific VRF, a specific
topology-identifier, a specific routing protocol instance
and/or a bridge domain identifier. This MIB module provides
a mapping of each such SNMP context to the corresponding VRF,
the corresponding topology, the corresponding routing protocol
instance, and the corresponding bridge domain identifier.
Some SNMP contexts are independent of VRFs, independent of
a topology, independent of a routing protocol instance, or
independent of a bridge domain and in such a case, the mapping
is to the zero length string.
With the Cisco package licensing strategy, the features
available in the image are grouped into multiple packages
and each packages can be managed to operate at different
feature levels based on the available license. This MIB
module provides option to associate an SNMP context to a
feature package group. This will allow manageability of
license MIB objects specific to a feature package group.
As technology evolves more we may need additional
identifiers to identify the context. Then we would need
to add those additional identifiers into the mapping.
Parsed from file CISCO-CONTEXT-MAPPING-MIB.my.txt
Company: None
Module: CISCO-CONTEXT-MAPPING-MIB
A single SNMP agent sometimes needs to support multiple
instances of the same MIB module, and does so through the
use of multiple SNMP contexts. This typically occurs because
the technology has evolved to have extra dimension(s), i.e.,
one or more extra data and/or identifier values which are
different in the different contexts, but were not defined in
INDEX clause(s) of the original MIB module. In such cases,
network management applications need to know the specific
data/identifier values in each context, and this MIB module
provides mapping tables which contain that information.
Within a network there can be multiple Virtual Private
Networks (VPNs) configured using Virtual Routing and
Forwarding Instances (VRFs). Within a VPN there can be
multiple topologies when Multi-topology Routing (MTR) is
used. Also, Interior Gateway Protocols (IGPs) can have
multiple protocol instances running on the device.
A network can have multiple broadcast domains configured
using Bridge Domain Identifiers.
With MTR routing, VRFs, and Bridge domains, a router now
needs to support multiple instances of several existing
MIB modules, and this can be achieved if the router's SNMP
agent provides access to each instance of the same MIB module
via a different SNMP context (see Section 3.1.1 of RFC 3411).
For MTR routing, VRFs, and Bridge domains, a different SNMP
context is needed depending on one or more of the following:
the VRF, the topology-identifier, the routing protocol instance,
and the bridge domain identifier.
In other words, the router's management information can be
accessed through multiple SNMP contexts where each such
context represents a specific VRF, a specific
topology-identifier, a specific routing protocol instance
and/or a bridge domain identifier. This MIB module provides
a mapping of each such SNMP context to the corresponding VRF,
the corresponding topology, the corresponding routing protocol
instance, and the corresponding bridge domain identifier.
Some SNMP contexts are independent of VRFs, independent of
a topology, independent of a routing protocol instance, or
independent of a bridge domain and in such a case, the mapping
is to the zero length string.
With the Cisco package licensing strategy, the features
available in the image are grouped into multiple packages
and each packages can be managed to operate at different
feature levels based on the available license. This MIB
module provides option to associate an SNMP context to a
feature package group. This will allow manageability of
license MIB objects specific to a feature package group.
As technology evolves more we may need additional
identifiers to identify the context. Then we would need
to add those additional identifiers into the mapping.
ciscoContextMappingMIB MODULE-IDENTITY LAST-UPDATED "200811220000Z" 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 "A single SNMP agent sometimes needs to support multiple instances of the same MIB module, and does so through the use of multiple SNMP contexts. This typically occurs because the technology has evolved to have extra dimension(s), i.e., one or more extra data and/or identifier values which are different in the different contexts, but were not defined in INDEX clause(s) of the original MIB module. In such cases, network management applications need to know the specific data/identifier values in each context, and this MIB module provides mapping tables which contain that information. Within a network there can be multiple Virtual Private Networks (VPNs) configured using Virtual Routing and Forwarding Instances (VRFs). Within a VPN there can be multiple topologies when Multi-topology Routing (MTR) is used. Also, Interior Gateway Protocols (IGPs) can have multiple protocol instances running on the device. A network can have multiple broadcast domains configured using Bridge Domain Identifiers. With MTR routing, VRFs, and Bridge domains, a router now needs to support multiple instances of several existing MIB modules, and this can be achieved if the router's SNMP agent provides access to each instance of the same MIB module via a different SNMP context (see Section 3.1.1 of RFC 3411). For MTR routing, VRFs, and Bridge domains, a different SNMP context is needed depending on one or more of the following: the VRF, the topology-identifier, the routing protocol instance, and the bridge domain identifier. In other words, the router's management information can be accessed through multiple SNMP contexts where each such context represents a specific VRF, a specific topology-identifier, a specific routing protocol instance and/or a bridge domain identifier. This MIB module provides a mapping of each such SNMP context to the corresponding VRF, the corresponding topology, the corresponding routing protocol instance, and the corresponding bridge domain identifier. Some SNMP contexts are independent of VRFs, independent of a topology, independent of a routing protocol instance, or independent of a bridge domain and in such a case, the mapping is to the zero length string. With the Cisco package licensing strategy, the features available in the image are grouped into multiple packages and each packages can be managed to operate at different feature levels based on the available license. This MIB module provides option to associate an SNMP context to a feature package group. This will allow manageability of license MIB objects specific to a feature package group. As technology evolves more we may need additional identifiers to identify the context. Then we would need to add those additional identifiers into the mapping." REVISION "200811220000Z" DESCRIPTION "Added New Table cContextMappingLicenseGroupTable to provide SNMP Context support for license package groups. Added cContextMappingLicenseGroupDataGroup in OBJECT-GROUP Added cContextMappingMIBComplianceRev2 in MODULE-COMPLIANCE Updated the MIB description to indicate the use of the above additions" REVISION "200805300000Z" DESCRIPTION "Add cContextMappingBridgeInstanceTable. Added cContextMappingBridgeInstanceDataGroup. Deprecated cContextMappingMIBComplianceRev1 and added cContextMappingMIBComplianceRev2 compliance statement." REVISION "200802010000Z" DESCRIPTION "Added New Table cContextMappingBridgeDomainTable to provide SNMP context support to the Bridge Domain. Added cContextMappingBridgeDomainDataGroup in OBJECT-GROUP Added cContextMappingMIBComplianceRev1 in MODULE-COMPLIANCE" REVISION "200503170000Z" DESCRIPTION "Initial version of the MIB module." ::= { ciscoMgmt 468 }
ciscoContextMappingMIB OBJECT IDENTIFIER ::= { ciscoMgmt 468 }
Vendor: Cisco
Module: CISCO-CONTEXT-MAPPING-MIB
[Automatically extracted from oidview.com]
ciscoContextMappingMIB MODULE-IDENTITY LAST-UPDATED "200811220000Z" 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 "A single SNMP agent sometimes needs to support multiple instances of the same MIB module, and does so through the use of multiple SNMP contexts. This typically occurs because the technology has evolved to have extra dimension(s), i.e., one or more extra data and/or identifier values which are different in the different contexts, but were not defined in INDEX clause(s) of the original MIB module. In such cases, network management applications need to know the specific data/identifier values in each context, and this MIB module provides mapping tables which contain that information. Within a network there can be multiple Virtual Private Networks (VPNs) configured using Virtual Routing and Forwarding Instances (VRFs). Within a VPN there can be multiple topologies when Multi-topology Routing (MTR) is used. Also, Interior Gateway Protocols (IGPs) can have multiple protocol instances running on the device. A network can have multiple broadcast domains configured using Bridge Domain Identifiers. With MTR routing, VRFs, and Bridge domains, a router now needs to support multiple instances of several existing MIB modules, and this can be achieved if the router's SNMP agent provides access to each instance of the same MIB module via a different SNMP context (see Section 3.1.1 of RFC 3411). For MTR routing, VRFs, and Bridge domains, a different SNMP context is needed depending on one or more of the following: the VRF, the topology-identifier, the routing protocol instance, and the bridge domain identifier. In other words, the router's management information can be accessed through multiple SNMP contexts where each such context represents a specific VRF, a specific topology-identifier, a specific routing protocol instance and/or a bridge domain identifier. This MIB module provides a mapping of each such SNMP context to the corresponding VRF, the corresponding topology, the corresponding routing protocol instance, and the corresponding bridge domain identifier. Some SNMP contexts are independent of VRFs, independent of a topology, independent of a routing protocol instance, or independent of a bridge domain and in such a case, the mapping is to the zero length string. With the Cisco package licensing strategy, the features available in the image are grouped into multiple packages and each packages can be managed to operate at different feature levels based on the available license. This MIB module provides option to associate an SNMP context to a feature package group. This will allow manageability of license MIB objects specific to a feature package group. As technology evolves more we may need additional identifiers to identify the context. Then we would need to add those additional identifiers into the mapping." REVISION "200811220000Z" DESCRIPTION "Added New Table cContextMappingLicenseGroupTable to provide SNMP Context support for license package groups. Added cContextMappingLicenseGroupDataGroup in OBJECT-GROUP Added cContextMappingMIBComplianceRev2 in MODULE-COMPLIANCE Updated the MIB description to indicate the use of the above additions" REVISION "200805300000Z" DESCRIPTION "Add cContextMappingBridgeInstanceTable. Added cContextMappingBridgeInstanceDataGroup. Deprecated cContextMappingMIBComplianceRev1 and added cContextMappingMIBComplianceRev2 compliance statement." REVISION "200802010000Z" DESCRIPTION "Added New Table cContextMappingBridgeDomainTable to provide SNMP context support to the Bridge Domain. Added cContextMappingBridgeDomainDataGroup in OBJECT-GROUP Added cContextMappingMIBComplianceRev1 in MODULE-COMPLIANCE" REVISION "200503170000Z" DESCRIPTION "Initial version of the MIB module." ::= { ciscoMgmt 468 }
ciscoContextMappingMIB MODULE-IDENTITY LAST-UPDATED "200811220000Z" 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 "A single SNMP agent sometimes needs to support multiple instances of the same MIB module, and does so through the use of multiple SNMP contexts. This typically occurs because the technology has evolved to have extra dimension(s), i.e., one or more extra data and/or identifier values which are different in the different contexts, but were not defined in INDEX clause(s) of the original MIB module. In such cases, network management applications need to know the specific data/identifier values in each context, and this MIB module provides mapping tables which contain that information. Within a network there can be multiple Virtual Private Networks (VPNs) configured using Virtual Routing and Forwarding Instances (VRFs). Within a VPN there can be multiple topologies when Multi-topology Routing (MTR) is used. Also, Interior Gateway Protocols (IGPs) can have multiple protocol instances running on the device. A network can have multiple broadcast domains configured using Bridge Domain Identifiers. With MTR routing, VRFs, and Bridge domains, a router now needs to support multiple instances of several existing MIB modules, and this can be achieved if the router's SNMP agent provides access to each instance of the same MIB module via a different SNMP context (see Section 3.1.1 of RFC 3411). For MTR routing, VRFs, and Bridge domains, a different SNMP context is needed depending on one or more of the following: the VRF, the topology-identifier, the routing protocol instance, and the bridge domain identifier. In other words, the router's management information can be accessed through multiple SNMP contexts where each such context represents a specific VRF, a specific topology-identifier, a specific routing protocol instance and/or a bridge domain identifier. This MIB module provides a mapping of each such SNMP context to the corresponding VRF, the corresponding topology, the corresponding routing protocol instance, and the corresponding bridge domain identifier. Some SNMP contexts are independent of VRFs, independent of a topology, independent of a routing protocol instance, or independent of a bridge domain and in such a case, the mapping is to the zero length string. With the Cisco package licensing strategy, the features available in the image are grouped into multiple packages and each packages can be managed to operate at different feature levels based on the available license. This MIB module provides option to associate an SNMP context to a feature package group. This will allow manageability of license MIB objects specific to a feature package group. As technology evolves more we may need additional identifiers to identify the context. Then we would need to add those additional identifiers into the mapping." REVISION "200811220000Z" DESCRIPTION "Added New Table cContextMappingLicenseGroupTable to provide SNMP Context support for license package groups. Added cContextMappingLicenseGroupDataGroup in OBJECT-GROUP Added cContextMappingMIBComplianceRev2 in MODULE-COMPLIANCE Updated the MIB description to indicate the use of the above additions" REVISION "200805300000Z" DESCRIPTION "Add cContextMappingBridgeInstanceTable. Added cContextMappingBridgeInstanceDataGroup. Deprecated cContextMappingMIBComplianceRev1 and added cContextMappingMIBComplianceRev2 compliance statement." REVISION "200802010000Z" DESCRIPTION "Added New Table cContextMappingBridgeDomainTable to provide SNMP context support to the Bridge Domain. Added cContextMappingBridgeDomainDataGroup in OBJECT-GROUP Added cContextMappingMIBComplianceRev1 in MODULE-COMPLIANCE" REVISION "200503170000Z" DESCRIPTION "Initial version of the MIB module." ::= { ciscoMgmt 468 }
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.9.9.468.1 | cContextMappingMIBObjects | 4 | 23 | None |
| 1.3.6.1.4.1.9.9.468.2 | cContextMappingMIBConformance | 2 | 10 | 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.420 | ciscoUnityExpressMIB | 3 | 179 | The MIB Module for the management of the Cisco Unity Express (CUE) service. CUE is a voicemail service that runs in a Cisco rout… |
| 1.3.6.1.4.1.9.9.421 | ciscoDpvmMIB | 3 | 55 | The MIB module for the management of the Dynamic Port Vsan Membership (DPVM) module. DPVM provides the ability to assign (virtual… |
| 1.3.6.1.4.1.9.9.422 | ciscoIPsecTc | 0 | 0 | This MIB module defines the textual conventions used in the IPsec suite of MIBs. This includes Internet DOI numbers defined in RF… |
| 1.3.6.1.4.1.9.9.423 | ciscoIkeConfigMIB | 3 | 93 | This is a MIB Module for configuring and viewing IKE parameters and policies. Acronyms The following acronyms are used in this do… |
| 1.3.6.1.4.1.9.9.424 | ciscoCableMeteringMIB | 3 | 53 | This is the MIB module for Usage Based Metering for the DOCSIS-compliant Cable Modem Termination Systems (CMTS). Usage Based Mete… |
| 1.3.6.1.4.1.9.9.426 | ciscoLinkErrorMonitorMIB | 3 | 34 | The MIB module for managing Link Error Monitoring Feature on devices. Link Error Monitoring Feature provides a mechanism to monito… |
| 1.3.6.1.4.1.9.9.427 | ciscoZsExtMIB | 3 | 33 | The MIB module for the management of zoning within the framework of Cisco's Zoning Server (ZS) Archi- tecture which realizes the … |
| 1.3.6.1.4.1.9.9.428 | ciscoIkeFlowExtMIB | 3 | 18 | This MIB module is an extension to CISCO-IKE-FLOW-MIB and contains Cisco Specific extensions for monitoring IKE. It is for monito… |
| 1.3.6.1.4.1.9.9.429 | ciscoIkeFlowMIB | 3 | 80 | This is a MIB module for monitoring the structures and status of IPsec control flows based on Internet Key Exchange protocol. The… |
| 1.3.6.1.4.1.9.9.430 | ciscoFcDeviceAliasMIB | 3 | 14 | The MIB module for the management of Device Aliases in a Fibre Channel Fabric. A Fibre Channel fabric consists of devices such as… |
| 1.3.6.1.4.1.9.9.431 | ciscoIPsecProvisioningMIB | 3 | 98 | IPSec is the next-generation network layer crypto framework described in RFC2401-2411. This MIB defines the IPsec configurations.… |
| 1.3.6.1.4.1.9.9.432 | ciscoEnhancedIpsecFlowMIB | 3 | 330 | This is a MIB Module for monitoring the structures and status of IPSec-based networks. The MIB has been designed to be adopted as… |
| 1.3.6.1.4.1.9.9.433 | ciscoCFSMIB | 3 | 102 | This MIB applies to one or more of a set of devices which have connectivity through some kind of 'fabric'. Many features which ru… |
| 1.3.6.1.4.1.9.9.434 | ciscoIpNetworkDiscoveryMIB, ciscoIsnsIpNetDiscoveryMIB | 3 | 58 | MIB to provide the information about the disjoint IP networks connected to the various gigabit ethernet interfaces in the 'Fabric… |
| 1.3.6.1.4.1.9.9.435 | ciscoFcMulticastMIB | 3 | 14 | MIB module for monitoring and configuring Fibre Channel Multicast feature. |
| 1.3.6.1.4.1.9.9.436 | ciscoDNSClientMIB | 3 | 28 | The MIB module for entities implementing the client side of the Domain Name System (DNS) protocol. |
| 1.3.6.1.4.1.9.9.437 | ciscoPortTrackMIB | 2 | 18 | A MIB to configure the Port-Track feature. When a link goes down, all the services which depend on the link are notified of the o… |
| 1.3.6.1.4.1.9.9.438 | ciscoIPsecSignalingMIB | 3 | 140 | This MIB Module models status, performance and failures of a protocol with the generic characteristics of signalling protocols us… |
| 1.3.6.1.4.1.9.9.439 | ciscoCcmeMIB | 3 | 338 | This MIB allows management of Cisco CallManager Express (CCME) feature in Cisco IOS. CCME is optional software feature that enabl… |
| 1.3.6.1.4.1.9.9.441 | ciscoSrstMIB | 3 | 149 | This MIB allows management of Cisco Survivable Remote Site Telephony (SRST) feature in Cisco IOS. SRST is an optional software fe… |
| 1.3.6.1.4.1.9.9.443 | ciscoCommonMgmtMIB | 3 | 37 | MIB module for integrating different elements of managing a device. For example, different device access methods like SNMP, CLI, … |
| 1.3.6.1.4.1.9.9.445 | ciscoQinqVlanMIB | 3 | 25 | This MIB defines configuration and monitoring capabilities relating to 802.1QinQ interfaces. QinQ interfaces are capable of term… |
| 1.3.6.1.4.1.9.9.447 | ciscoScsiFlowMIB | 3 | 99 | A SCSI Flow is described as a SCSI Initiator SCSI Target combination. This MIB is used to configure and monitor SCSI Flows. Gloss… |
| 1.3.6.1.4.1.9.9.448 | ciscoSsmProvMIB | 2 | 26 | This MIB is used to provision features on a Data Path Processor (DPP) of a Storage Service Module (SSM). A DPP is assigned to a c… |
| 1.3.6.1.4.1.9.9.449 | ciscoEigrpMIB | 3 | 103 | Enhanced Interior Gateway Protocol (EIGRP) is a Cisco proprietary distance vector routing protocol. It is based on the Diffusin… |
| 1.3.6.1.4.1.9.9.450 | ciscoCableAdmCtrlMIB | 3 | 123 | This MIB module defines the managed objects enabling the management of Cable Modem Termination System (CMTS) admission control. CM… |
| 1.3.6.1.4.1.9.9.451 | ciscoIpUrpfMIB | 3 | 47 | Unicast Reverse Path Forwarding (URPF) is a function that checks the validity of the source address of IP packets received on an … |
| 1.3.6.1.4.1.9.9.454 | ciscoDot11LbsMIB | 3 | 23 | This MIB module supports network management for Location Based Services on IEEE 802.11 wireless LAN devices. Location Based Serv… |
| 1.3.6.1.4.1.9.9.455 | ciscoImageTc | 0 | 0 | This MIB module defines the textual conventions used in the enhanced image MIB. Glossary: Base Image Essential part of the operatin… |
| 1.3.6.1.4.1.9.9.456 | ciscoDot11WidsMIB | 3 | 50 | This MIB is intended to be implemented on the following IOS based network entities for the purpose of providing network managemen… |
| 1.3.6.1.4.1.9.9.457 | ciscoWdsIdsMIB | 2 | 18 | This MIB is intended to be implemented on all IOS based network entities that provide Wireless Domain Services, for the purpose o… |
| 1.3.6.1.4.1.9.9.458 | ciscoApplianceRedundancyMIB | 3 | 47 | This mib defines the SNMP objects to report the status of High Availability (HA) functionality in Cisco network management applia… |
| 1.3.6.1.4.1.9.9.459 | ciscoBitsClockMIB | 3 | 21 | This MIB provides information on Building Integrated Timing Supply(BITS) clocking sources and modes of operations. It is used to… |
| 1.3.6.1.4.1.9.9.460 | ciscoTpcMIB | 3 | 24 | The MIB module for Third Party Copy(TPC): Third Party Copy derives its name from the fact that there are three entities involved … |
| 1.3.6.1.4.1.9.9.461 | ciscoEtherCfmMIB | 3 | 39 | This MIB module defines the managed objects and notifications for Ethernet Connectivity Fault Management (CFM). CFM is an end-to-e… |
| 1.3.6.1.4.1.9.9.463 | ciscoSanTapMIB | 3 | 30 | MIB module to provide information about the SanTap service configuration. SanTap is a fibre channel switch based capability that p… |
| 1.3.6.1.4.1.9.9.466 | ciscoEthernetAccessMIB | 2 | 20 | The tables defined by this MIB module contain a collection of managed objects that are general in nature and apply to an edge dev… |
| 1.3.6.1.4.1.9.9.467 | ciscoCryptoAcceleratorMIB | 3 | 107 | The MIB module for monitoring the identity, status, activity and faults of crypto accelerator (CA) modules used in devices implem… |
| 1.3.6.1.4.1.9.9.470 | ciscoEnhancedSlbMIB | 3 | 106 | The MIB for managing Server Load Balancing Manager(s), and products supporting Server Load Balancing(SLB) features. This MIB exten… |
| 1.3.6.1.4.1.9.9.471 | ciscoFlexLinksMIB | 3 | 36 | This MIB module is for configuration and status query of Flex Links feature on the Cisco device. Flex Links are a pair of Layer 2… |
| 1.3.6.1.4.1.9.9.472 | ciscoModuleVirtualizationMIB | 3 | 35 | This MIB provides a way to create virtual contexts, and managing them. A virtual context is logical partition of a physical devi… |
| 1.3.6.1.4.1.9.9.473 | ciscoCcaMIB | 3 | 200 | The Cisco Contact Center Applications (CCCA) Management Information Base (MIB) module defines management instrumentation for appl… |
| 1.3.6.1.4.1.9.9.474 | ciscoFilterGroupMIB | 3 | 55 | The MIB module is for creating and configuring object groups to support packet filtering and access control on IP and other proto… |
| 1.3.6.1.4.1.9.9.479 | ciscoCableWidebandMIB | 3 | 77 | This is the MIB module for the support of Channel Bonding Protocol for the Cable Modem Termination System (CMTS). Wideband DOCSIS… |
| 1.3.6.1.4.1.9.9.480 | ciscoL4L7moduleResourceLimitMIB | 4 | 100 | The MIB module for managing resource classes and configuring limits(max/min) to different resources. The resource referenced in … |
| 1.3.6.1.4.1.9.9.482 | ciscoInterfaceTopNExtMIB | 3 | 16 | This MIB module is an extension to INTERFACETOPN-MIB. It provides additional management information for sorting device interfaces. |
| 1.3.6.1.4.1.9.9.483 | ciscoIpRanBackHaulMIB | 3 | 248 | This MIB provides information on the IP-RAN traffic from cell site to aggregation site in the following situations. In an GSM en… |
| 1.3.6.1.4.1.9.9.484 | ciscoNacNadMIB | 3 | 157 | This MIB module is for the configuration of a Network Access Device (NAD) on the Cisco Network Admission Control (NAC) system. End… |
| 1.3.6.1.4.1.9.9.485 | ciscoRttMonTCMIB | 0 | 0 | This MIB contains textual conventions used by CISCO-RTTMON-MIB, CISCO-RTTMON-RTP-MIB and CISCO-RTTMON-ICMP-MIB, but they are not … |
| 1.3.6.1.4.1.9.9.486 | ciscoRttMonIcmpMIB | 3 | 7 | An extension to the CISCO-RTTMON-MIB for ICMP operations. The ICMP Jitter operation provides capability to measure metrics such a… |
| 1.3.6.1.4.1.9.9.487 | ciscoRttMonRtpMIB | 3 | 8 | An extension to the CISCO-RTTMON-MIB for Cisco IP SLA RTP operation, Real-Time Transport Protocol(RFC 1889). This operation provi… |
| 1.3.6.1.4.1.9.9.488 | ciscoFirewallTc | 0 | 0 | This MIB module defines textual conventions that are commonly used in modeling management information pertaining to configuration… |
| 1.3.6.1.4.1.9.9.490 | ciscoNetintMIB | 3 | 11 | This MIB module is for Network Interrupt information on Cisco device. |
| 1.3.6.1.4.1.9.9.491 | ciscoUnifiedFirewallMIB | 3 | 235 | Overview of Cisco Firewall MIB ============================== This MIB Module models status and performance statistics pertaining … |
| 1.3.6.1.4.1.9.9.492 | ciscoCefMIB | 3 | 192 | Cisco Express Forwarding (CEF) describes a high speed switching mechanism that a router uses to forward packets from the inbound … |
| 1.3.6.1.4.1.9.9.493 | ciscoCefTextualConventions | 0 | 0 | ciscoCeftextualConventions |
| 1.3.6.1.4.1.9.9.494 | ciscoEntityRedunTcMIB | 0 | 0 | This module defines the textual conventions used within Cisco Entity Redundancy MIBs. |
| 1.3.6.1.4.1.9.9.495 | ciscoPsdClientMIB | 3 | 44 | This MIB module manages the client side functionality of the Persistent Storage Device(PSD). This MIB instrumentation is for conf… |
| 1.3.6.1.4.1.9.9.497 | cGgsnSAMIB | 3 | 247 | This MIB module manages the service-aware feature of Gateway GPRS Support Node (GGSN). This MIB is an enhancement of the CISCO-GG… |
| 1.3.6.1.4.1.9.9.498 | ciscoEntityRedunMIB | 3 | 93 | This management information module supports configuration, control and monitoring of redundancy protection for various kinds of c… |
| 1.3.6.1.4.1.9.9.500 | ciscoStackWiseMIB | 3 | 111 | This MIB module contain a collection of managed objects that apply to network devices supporting the Cisco StackWise(TM) technolo… |
| 1.3.6.1.4.1.9.9.504 | ciscoSwitchMulticastMIB | 3 | 108 | This MIB module defines management objects for the Multicast Switching features on Cisco Layer 2/3 devices. Definition of some of … |
| 1.3.6.1.4.1.9.9.505 | cpkiMIB | 3 | 44 | A networking device may provide several security services and protocols like SSL, SSH, IPSec/IKE etc. which need identities … |
| 1.3.6.1.4.1.9.9.507 | ciscoPolicyGroupMIB | 3 | 35 | The MIB module is for configuration of policy and policy group. A policy group can be described as a set of entities identified b… |
| 1.3.6.1.4.1.9.9.508 | ciscoSlbHealthMonMIB | 3 | 62 | An extension to the CISCO-SLB-EXT-MIB for SLB health monitoring probes. SLB: Server Load Balancing. Server load balancing provides… |
| 1.3.6.1.4.1.9.9.509 | ciscoWdsInfoMIB | 3 | 141 | This MIB is intended to be implemented on all Cisco network entities that provide Wireless Domain Services (WDS). The WDS provide… |
| 1.3.6.1.4.1.9.9.510 | ciscoErmMIB, ciscoVoiceLmrMIB | 3 | 176 | This MIB module provides management of voice tone signal as static injected tone for Land Mobile Radio The tone signal includes … |
| 1.3.6.1.4.1.9.9.511 | ciscoCbpTargetTCMIB | 0 | 0 | This MIB module defines Textual Conventions for representing targets which have class based policy mappings. A target can be any … |
| 1.3.6.1.4.1.9.9.512 | ciscoLwappWlanMIB | 3 | 249 | This MIB is intended to be implemented on all those devices operating as Central Controllers (CC) that terminate the Light Weigh… |
| 1.3.6.1.4.1.9.9.513 | ciscoLwappApMIB | 4 | 386 | This MIB is intended to be implemented on all those devices operating as Central Controllers (CC) that terminate the Light Weight… |
| 1.3.6.1.4.1.9.9.514 | ciscoLwappTextualConventions | 0 | 0 | This module defines textual conventions used throughout the Cisco enterprise MIBs designed for implementation on Central Controlle… |
| 1.3.6.1.4.1.9.9.515 | ciscoLwappWebAuthMIB | 4 | 43 | 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.516 | ciscoLwappLinkTestMIB | 3 | 57 | 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.517 | ciscoLwappReapMIB | 3 | 63 | This MIB is intended to be implemented on all those devices operating as Central Controllers (CC) that terminate the Light Weight… |
| 1.3.6.1.4.1.9.9.518 | ciscoLwappMfpMIB | 4 | 64 | This MIB is intended to be implemented on all those devices operating as Central Controllers (CC) that terminate the Light Weight… |
| ... | ||||