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.

Imported Objects

ciscoMgmtCISCO-SMI
CiscoBridgeDomainCISCO-TC
SnmpAdminStringSNMP-FRAMEWORK-MIB
MODULE-COMPLIANCE, OBJECT-GROUPSNMPv2-CONF
MODULE-IDENTITY, OBJECT-TYPESNMPv2-SMI
RowStatus, StorageTypeSNMPv2-TC
ciscoContextMappingMIB .1.3.6.1.4.1.9.9.468
cContextMappingMIBObjects .1.3.6.1.4.1.9.9.468.1
cContextMappingTable .1.3.6.1.4.1.9.9.468.1.1
cContextMappingEntry .1.3.6.1.4.1.9.9.468.1.1.1
cContextMappingVacmContextName .1.3.6.1.4.1.9.9.468.1.1.1.1
cContextMappingVrfName .1.3.6.1.4.1.9.9.468.1.1.1.2
cContextMappingTopologyName .1.3.6.1.4.1.9.9.468.1.1.1.3
cContextMappingProtoInstName .1.3.6.1.4.1.9.9.468.1.1.1.4
cContextMappingStorageType .1.3.6.1.4.1.9.9.468.1.1.1.5
cContextMappingRowStatus .1.3.6.1.4.1.9.9.468.1.1.1.6
cContextMappingBridgeDomainTable .1.3.6.1.4.1.9.9.468.1.2
cContextMappingBridgeDomainEntry .1.3.6.1.4.1.9.9.468.1.2.1
cContextMappingBridgeDomainIdentifier .1.3.6.1.4.1.9.9.468.1.2.1.1
cContextMappingBridgeDomainStorageType .1.3.6.1.4.1.9.9.468.1.2.1.2
cContextMappingBridgeDomainRowStatus .1.3.6.1.4.1.9.9.468.1.2.1.3
cContextMappingBridgeInstanceTable .1.3.6.1.4.1.9.9.468.1.3
cContextMappingBridgeInstanceEntry .1.3.6.1.4.1.9.9.468.1.3.1
cContextMappingBridgeInstName .1.3.6.1.4.1.9.9.468.1.3.1.1
cContextMappingBridgeInstStorageType .1.3.6.1.4.1.9.9.468.1.3.1.2
cContextMappingBridgeInstRowStatus .1.3.6.1.4.1.9.9.468.1.3.1.3
cContextMappingLicenseGroupTable .1.3.6.1.4.1.9.9.468.1.4
cContextMappingLicenseGroupEntry .1.3.6.1.4.1.9.9.468.1.4.1
cContextMappingLicenseGroupName .1.3.6.1.4.1.9.9.468.1.4.1.1
cContextMappingLicenseGroupStorageType .1.3.6.1.4.1.9.9.468.1.4.1.2
cContextMappingLicenseGroupRowStatus .1.3.6.1.4.1.9.9.468.1.4.1.3
cContextMappingMIBConformance .1.3.6.1.4.1.9.9.468.2
cContextMappingMIBCompliances .1.3.6.1.4.1.9.9.468.2.1
cContextMappingMIBGroups .1.3.6.1.4.1.9.9.468.2.2