diff --git a/mibs/CISCO-BRIDGE-DOMAIN-MIB b/mibs/CISCO-BRIDGE-DOMAIN-MIB new file mode 100644 index 0000000000..68e9ddb9c9 --- /dev/null +++ b/mibs/CISCO-BRIDGE-DOMAIN-MIB @@ -0,0 +1,450 @@ +-- ***************************************************************** +-- CISCO-BRIDGE-DOMAIN-MIB.my : Cisco Bridge Domain MIB +-- +-- Oct 2007, Madhavi Dokku +-- +-- Copyright (c) 2007 by Cisco Systems, Inc. +-- +-- All rights reserved. +-- ***************************************************************** + +CISCO-BRIDGE-DOMAIN-MIB DEFINITIONS ::= BEGIN + +IMPORTS + MODULE-IDENTITY, + OBJECT-TYPE, + Unsigned32 + FROM SNMPv2-SMI + MODULE-COMPLIANCE, + OBJECT-GROUP + FROM SNMPv2-CONF + TEXTUAL-CONVENTION, + TruthValue, + RowStatus, + StorageType + FROM SNMPv2-TC + ifIndex + FROM IF-MIB + ciscoMgmt + FROM CISCO-SMI; + + +ciscoBridgeDomainMIB MODULE-IDENTITY + LAST-UPDATED "200712290000Z" + 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: cs-ethermibs@cisco.com" + DESCRIPTION + "A bridge domain is one of the means by which it is possible + to define a broadcast domain on a bridging device. It is an + alternative to 802.1D bridge-groups and to 802.1Q VLAN + bridging. + + Bridge domain is the service specification, and specifies the + broadcast domain number on which this frame of this particular + service instance must be made available on. The physical and + virtual interfaces that can comprise a bridge domain are + heterogeneous in nature comprising Ethernet service instances, + WAN Virtual Circuit for ATM or Frame Relay and VFIs. However, + the frame encapsulations for all interface types are + essentially Ethernet. + + Without bridge-domains, VLANs would have to be globally unique + per device and one would only be restricted to the theoretical + maximum of 4095 VLANs for single tagged traffic. However + with the introduction of bridge-domains, one can + associate a service instance with a bridge-domain and all + service instances in the same bridge-domain form a + broadcast domain. Bridge-domain ID determines the + broadcast domain and the VLAN id is merely used to match + and map traffic. With bridge domain feature configured + VLAN IDs would be unique per interface only and not globally. + Thus bridge domains make VLAN ids have only local + significance per port + + + Differences between Bridge Domains and 802.1AD Bridges: + ======================================================= + 1. Scope of the VLAN technology which uses 802.1 AD is global to + the box. + But in case of Bridge domain, the scope of vlan is local to + interface + + 2. Switchport 802.1AD restricts the number of broadcast domain + on a box to 4095. + However, with Bridge domains, we can have up to 16k broadcast + domain. + + 3. Under a single Bridge domain service instance, there can be + flexible service mapping criterion.(i.e match based on + outer vlan, outer cos, inner vlan, inner cos and payload + ethertype). + Whereas in case of switch port 802.1AD/dot1q this is not + supported. + + Similarities between Bridge Domains and 802.1AD Bridges: + ======================================================= + + 1. Both use the same MAC address lookup for forwarding. + + 2. Both work with protocols like STP, DTP etc. + + 3. Both of them classify 'ports' in a system into Bridges/Bridge + Domains. + + Ethernet service instance is the instantiation of an Ethernet + virtual circuit on a given port on a given router. In other + words, an Ethernet service instance is an object that holds + information about the layer 2 service that is being offered + on a given port of a given router as part of a given Ethernet + virtual circuit. Bridge domains feature is currently supported + on ethernet service instances only and can be later extented + to other interfaces like ATM and Frame Relay. + + This MIB helps the network management personnel to find out the + details of various broadcast domains configured in the network. + + Definition of terms and acronyms: + + ATM: Asynchronous Transfer mode + + BD: Bridge Domain + + C-mac: Customer MAC + + EVC: Ethernet Virtual Circuit + + FR: Frame Relay + + SH: Split Horizon + + VFI: Virtual Forwarding Instance + + VLAN: Virtual Local Area Network + + WAN: Wide Area Network" + REVISION "200712290000Z" + DESCRIPTION + "Modified the MIB description with details on similarities and + differences between Bridge Domains and 802.1AD Bridges." + REVISION "200712040000Z" + DESCRIPTION + "Initial version of this MIB module." + ::= { ciscoMgmt 642 } + + +ciscoBdMIBNotifications OBJECT IDENTIFIER + ::= { ciscoBridgeDomainMIB 0 } + +ciscoBdMIBObjects OBJECT IDENTIFIER + ::= { ciscoBridgeDomainMIB 1 } + +ciscoBdMIBConformance OBJECT IDENTIFIER + ::= { ciscoBridgeDomainMIB 2 } + +cbdSystemInfo OBJECT IDENTIFIER + ::= { ciscoBdMIBObjects 1 } + +cbdMemberInfo OBJECT IDENTIFIER + ::= { ciscoBdMIBObjects 2 } + + +-- Textual Conventions + +CbdType ::= TEXTUAL-CONVENTION + STATUS current + DESCRIPTION + "Defines the different types of bridge domain members: + + 'other': none of the following + + 'ether': Ethernet Service Instance + + 'atmVc': ATM Virtual connection + + 'frVc': Frame Relay Virtual Connection" + SYNTAX INTEGER { + other(1), + ether(2), + atmVc(3), + frVc(4) + } + +cbdMembersConfigured OBJECT-TYPE + SYNTAX Unsigned32 + MAX-ACCESS read-only + STATUS current + DESCRIPTION + "This object indicates the number of bridge domain + members configured on this bridge domain." + ::= { cbdSystemInfo 1 } +-- Member Info Table + +cbdMemberInfoTable OBJECT-TYPE + SYNTAX SEQUENCE OF CbdMemberInfoEntry + MAX-ACCESS not-accessible + STATUS current + DESCRIPTION + "This table provides the bridge domain member attributes + of the members currently configured for each bridge + domain." + ::= { cbdMemberInfo 1 } + +cbdMemberInfoEntry OBJECT-TYPE + SYNTAX CbdMemberInfoEntry + MAX-ACCESS not-accessible + STATUS current + DESCRIPTION + "A conceptual row in cbdMemberInfoTable. This is indexed + by ifIndex and cbdSIIndex. Each row is created when a bridge + domain member is configured under a service instance." + INDEX { + ifIndex, + cbdSIIndex + } + ::= { cbdMemberInfoTable 1 } + +CbdMemberInfoEntry ::= SEQUENCE { + cbdSIIndex Unsigned32, + cbdMemberType CbdType, + cbdMemberOperState INTEGER , + cbdMemberAdminState INTEGER , + cbdMemberSplitHorizon TruthValue, + cbdMemberSplitHorizonNum Unsigned32, + cbdMemberStorageType StorageType, + cbdMemberStatus RowStatus, + cbdMembercMac TruthValue +} + +cbdSIIndex OBJECT-TYPE + SYNTAX Unsigned32 (1..4294967295 ) + MAX-ACCESS not-accessible + STATUS current + DESCRIPTION + "This object indicates an arbitary index that uniquely + identifies the Service Instance to which this bridge domain + member belongs to." + ::= { cbdMemberInfoEntry 1 } + +cbdMemberType OBJECT-TYPE + SYNTAX CbdType + MAX-ACCESS read-create + STATUS current + DESCRIPTION + "This object identifies the type of the bridge domain member + like ATM VC, Frame Relay VC, or Ethernet service." + DEFVAL { other } + ::= { cbdMemberInfoEntry 2 } + +cbdMemberOperState OBJECT-TYPE + SYNTAX INTEGER { + unknown(1), + up(2), + down(3) + } + MAX-ACCESS read-only + STATUS current + DESCRIPTION + "This object indicates the operational state of the bridge + domain Member. Operational state of the Bridge domain member + is same as the operational state of the underlying service + instance. Bridge domain members are configured under service + instances and multiple service instances can be attached to a + single physical interface defining various kinds of services. + Bridge domain members have many to one relationship with + interface + Indexes. When ifOperStatus of the underlying interface is down, + the state of cbdMemberOperState should be down. When + ifOperStatus + of the underlying interface is up, cbdMemberOperState can be + either up or down based on the state of underlying service + instance. + + 'unknown': the bridge domain member is an unknown state. + + 'up': the bridge domain member is fully operational and + able to bridge the traffic. This means that both the + physical interface and the underlying service instance + are administratively up. + + 'down': the Bridge Domain member is down and not + capable of bridging. This state means either the underlying + service instance is down or the interface is down." + ::= { cbdMemberInfoEntry 3 } + +cbdMemberAdminState OBJECT-TYPE + SYNTAX INTEGER { + unknown(1), + up(2), + down(3) + } + MAX-ACCESS read-create + STATUS current + DESCRIPTION + "This object indicates the administrative state of the + bridge domain Member. Admin state of the Bridge domain member + is same as the admin state of the underlying service instance. + Bridge domain members are configured under service instances + and multiple service instances can be attached to a single + physical interface defining various kinds of services. Bridge + Domain members have many to one relationship with interface + Indexes. When ifAdminStatus of the unerlying interface is down + the state of cbdMemberAdminState should be down. When ifOperStatus + of the underlying interface is up cbdMemberAdminState can be + either up or down based on the state of underlying service + instance. + + 'unknown': the bridge domain member is in unknown + administrative state. + + 'up': the Bridge Domain member is administratively up. This + means that both the physical interface and the underlying service + instance are administratively up. + + 'admindown': the Bridge Domain member is down as it is + administratively configured to be down and is not + capable of bridging. This means that either the underlying + service instance is configured as administratively down or + the physical interface is configured as administratively + down." + ::= { cbdMemberInfoEntry 4 } + +cbdMemberSplitHorizon OBJECT-TYPE + SYNTAX TruthValue + MAX-ACCESS read-create + STATUS current + DESCRIPTION + "This object indicates whether split horizon is + configured on this bridge domain member." + ::= { cbdMemberInfoEntry 5 } + +cbdMemberSplitHorizonNum OBJECT-TYPE + SYNTAX Unsigned32 (0..65535 ) + MAX-ACCESS read-create + STATUS current + DESCRIPTION + "This object indicates the split horizon number if + configured on the bridge domain member. Split horizon + is used to avoid sending traffic between interfaces. + Frames are not forwarded to the members belonging to the + same split horizon group." + DEFVAL { 0 } + ::= { cbdMemberInfoEntry 6 } + +cbdMemberStorageType OBJECT-TYPE + SYNTAX StorageType + MAX-ACCESS read-create + STATUS current + DESCRIPTION + "This object specifies the storage type of this conceptual + row. This object can only have a value 'nonVolatile'. Other + values are not applicable for this conceptual row and are + not supported." + DEFVAL { nonVolatile } + ::= { cbdMemberInfoEntry 7 } + +cbdMemberStatus OBJECT-TYPE + SYNTAX RowStatus + MAX-ACCESS read-create + STATUS current + DESCRIPTION + "This object enables the SNMP agent to create, modify, + and delete rows in the cbdMemberInfoTable." + DEFVAL { active } + ::= { cbdMemberInfoEntry 8 } + +cbdMembercMac OBJECT-TYPE + SYNTAX TruthValue + MAX-ACCESS read-create + STATUS current + DESCRIPTION + "This object indicates if cmac is configured on this + bridge domain member. Cmac denotes if this bridge domain is + configured as a customer domain." + ::= { cbdMemberInfoEntry 9 } + + +-- Notifications + +ciscoBdNotificationPrefix OBJECT IDENTIFIER + ::= { ciscoBdMIBNotifications 0 } + +-- Conformance + +ciscoBdMIBCompliances OBJECT IDENTIFIER + ::= { ciscoBdMIBConformance 1 } + +ciscoBdMIBGroups OBJECT IDENTIFIER + ::= { ciscoBdMIBConformance 2 } + + +ciscoBdMIBComplianceRev1 MODULE-COMPLIANCE + STATUS current + DESCRIPTION + "The compliance statement for entities which implement + the CISCO-BRIDGE-DOMAIN-MIB." + MODULE -- this module + MANDATORY-GROUPS { + cbdSystemInfoGroup, + cbdMemberInfoGroup + } + ::= { ciscoBdMIBCompliances 1 } + +-- Units of Conformance + +cbdSystemInfoGroup OBJECT-GROUP + OBJECTS { cbdMembersConfigured } + STATUS current + DESCRIPTION + "This group contain information about bridge domain." + ::= { ciscoBdMIBGroups 1 } + +cbdMemberInfoGroup OBJECT-GROUP + OBJECTS { + cbdMemberType, + cbdMemberOperState, + cbdMemberAdminState, + cbdMemberSplitHorizon, + cbdMemberSplitHorizonNum, + cbdMemberStorageType, + cbdMemberStatus, + cbdMembercMac + } + STATUS current + DESCRIPTION + "This group contain information related to bridge domain + members." + ::= { ciscoBdMIBGroups 2 } + +END + + + + + + + + + + + + + + + + + + + + + + + diff --git a/mibs/CISCO-CONTEXT-MAPPING-MIB b/mibs/CISCO-CONTEXT-MAPPING-MIB new file mode 100644 index 0000000000..94451564d8 --- /dev/null +++ b/mibs/CISCO-CONTEXT-MAPPING-MIB @@ -0,0 +1,853 @@ +-- ***************************************************************** +-- CISCO-CONTEXT-MAPPING-MIB.my: Cisco Context Mapping MIB +-- +-- January 2005, Chinna Pellacuru. +-- +-- May 2008, Sheethal Gunjal. +-- +-- Copyright (c) 2004-2005, 2008 by cisco Systems Inc. +-- All rights reserved. +-- +-- **************************************************************** + +CISCO-CONTEXT-MAPPING-MIB DEFINITIONS ::= BEGIN + +IMPORTS + MODULE-IDENTITY, + OBJECT-TYPE + FROM SNMPv2-SMI + MODULE-COMPLIANCE, + OBJECT-GROUP + FROM SNMPv2-CONF + SnmpAdminString + FROM SNMP-FRAMEWORK-MIB + RowStatus, + StorageType + FROM SNMPv2-TC + CiscoBridgeDomain + FROM CISCO-TC + ciscoMgmt + FROM CISCO-SMI; + + +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: cs-snmp@cisco.com" + 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 } + + +cContextMappingMIBObjects OBJECT IDENTIFIER + ::= { ciscoContextMappingMIB 1 } + +cContextMappingMIBConformance OBJECT IDENTIFIER + ::= { ciscoContextMappingMIB 2 } + + +cContextMappingTable OBJECT-TYPE + SYNTAX SEQUENCE OF CContextMappingEntry + MAX-ACCESS not-accessible + STATUS current + DESCRIPTION + "This table contains information on which + cContextMappingVacmContextName is mapped to + which VRF, topology, and routing protocol instance. + + This table is indexed by SNMP VACM context. + + Configuring a row in this table for an SNMP context + does not require that the context be already defined, + i.e., a row can be created in this table for a context + before the corresponding row is created in RFC 3415's + vacmContextTable. + + To create a row in this table, a manager must set + cContextMappingRowStatus to either 'createAndGo' or + 'createAndWait'. + + To delete a row in this table, a manager must set + cContextMappingRowStatus to 'destroy'." + ::= { cContextMappingMIBObjects 1 } + +cContextMappingEntry OBJECT-TYPE + SYNTAX CContextMappingEntry + MAX-ACCESS not-accessible + STATUS current + DESCRIPTION + "Information relating to a single mapping of + cContextMappingVacmContextName to the corresponding VRF, + the corresponding topology, and the corresponding routing + protocol instance." + INDEX { cContextMappingVacmContextName } + ::= { cContextMappingTable 1 } + +CContextMappingEntry ::= SEQUENCE { + cContextMappingVacmContextName SnmpAdminString, + cContextMappingVrfName SnmpAdminString, + cContextMappingTopologyName SnmpAdminString, + cContextMappingProtoInstName SnmpAdminString, + cContextMappingStorageType StorageType, + cContextMappingRowStatus RowStatus +} + +cContextMappingVacmContextName OBJECT-TYPE + SYNTAX SnmpAdminString (SIZE (0..32)) + MAX-ACCESS not-accessible + STATUS current + DESCRIPTION + "The vacmContextName given to the SNMP context. + + This is a human readable name identifying a particular + SNMP VACM context at a particular SNMP entity. + The empty contextName (zero length) represents the + default context." + ::= { cContextMappingEntry 1 } + +cContextMappingVrfName OBJECT-TYPE + SYNTAX SnmpAdminString (SIZE (0..32)) + MAX-ACCESS read-create + STATUS current + DESCRIPTION + "The value of an instance of this object identifies + the name given to the VRF to which the SNMP context + is mapped to. + + This is typically a human-readable string. This is + the same ASCII string used in the router's console + interface to refer to this VRF. + + When the value of this object is the zero length + string it indicates that the SNMP context is independent + of any VRF." + DEFVAL { ''H } + ::= { cContextMappingEntry 2 } + +cContextMappingTopologyName OBJECT-TYPE + SYNTAX SnmpAdminString (SIZE (0..32)) + MAX-ACCESS read-create + STATUS current + DESCRIPTION + "The value of an instance of this object identifies + the name given to the topology to which the SNMP + context is mapped to. + + This is typically a human-readable string. This is + the same ASCII string used in the router's console + interface to refer to this topology. + + When the value of this object is the zero length + string it indicates that the SNMP context is independent + of any topology." + DEFVAL { ''H } + ::= { cContextMappingEntry 3 } + +cContextMappingProtoInstName OBJECT-TYPE + SYNTAX SnmpAdminString (SIZE (0..32)) + MAX-ACCESS read-create + STATUS current + DESCRIPTION + "The value of an instance of this object identifies + the name given to the protocol instance to which the + SNMP context is mapped to. + + This is typically a human-readable string. This is + the same ASCII string used in the router's console + interface to refer to this protocol instance. + + When the value of this object is the zero length + string it indicates that the SNMP context is independent + of any protocol instance." + DEFVAL { ''H } + ::= { cContextMappingEntry 4 } + +cContextMappingStorageType OBJECT-TYPE + SYNTAX StorageType + MAX-ACCESS read-create + STATUS current + DESCRIPTION + "The storage type for this conceptual row. + + Conceptual rows having the value 'permanent' need not + allow write-access to any columnar objects in the row." + DEFVAL { nonVolatile } + ::= { cContextMappingEntry 5 } + +cContextMappingRowStatus OBJECT-TYPE + SYNTAX RowStatus + MAX-ACCESS read-create + STATUS current + DESCRIPTION + "This object facilitates the creation, modification, or + deletion of a conceptual row in this table." + ::= { cContextMappingEntry 6 } + + + +cContextMappingBridgeDomainTable OBJECT-TYPE + SYNTAX SEQUENCE OF CContextMappingBridgeDomainEntry + MAX-ACCESS not-accessible + STATUS current + DESCRIPTION + "This table contains information on which + cContextMappingVacmContextName is mapped to + which bridge domain. + + A Bridge Domain is one of the means by which it is possible + to define an Ethernet broadcast domain on a bridging device. + A network can have multiple broadcast domains configured. + This table helps the network management personnel to find + out the details of various broadcast domains configured + in the network. + + An entry need to exist in cContextMappingTable, to create + an entry in this table." + ::= { cContextMappingMIBObjects 2 } + +cContextMappingBridgeDomainEntry OBJECT-TYPE + SYNTAX CContextMappingBridgeDomainEntry + MAX-ACCESS not-accessible + STATUS current + DESCRIPTION + "Information relating to a single mapping of + cContextMappingVacmContextName to the + corresponding bridge domain. + + To create a row in this table, a manager must set + cContextMappingBridgeDomainRowStatus to either + 'createAndGo' or 'createAndWait'. + + To delete a row in this table, a manager must set + cContextMappingBridgeDomainRowStatus to 'destroy'." + INDEX { cContextMappingVacmContextName } + ::= { cContextMappingBridgeDomainTable 1 } + +CContextMappingBridgeDomainEntry ::= SEQUENCE { + cContextMappingBridgeDomainIdentifier CiscoBridgeDomain, + cContextMappingBridgeDomainStorageType StorageType, + cContextMappingBridgeDomainRowStatus RowStatus +} + +cContextMappingBridgeDomainIdentifier OBJECT-TYPE + SYNTAX CiscoBridgeDomain + MAX-ACCESS read-create + STATUS current + DESCRIPTION + "The value of an instance of this object identifies + the bridge domain to which the SNMP context is + mapped to." + REFERENCE "CISCO-BRIDGE-DOMAIN-MIB" + ::= { cContextMappingBridgeDomainEntry 1 } + +cContextMappingBridgeDomainStorageType OBJECT-TYPE + SYNTAX StorageType + MAX-ACCESS read-create + STATUS current + DESCRIPTION + "The storage type for this conceptual row. + + Conceptual rows having the value 'permanent' need not + allow write-access to any columnar objects in the row." + DEFVAL { nonVolatile } + ::= { cContextMappingBridgeDomainEntry 2 } + +cContextMappingBridgeDomainRowStatus OBJECT-TYPE + SYNTAX RowStatus + MAX-ACCESS read-create + STATUS current + DESCRIPTION + "This object facilitates the creation, modification, or + deletion of a conceptual row in this table." + ::= { cContextMappingBridgeDomainEntry 3 } + + + +cContextMappingBridgeInstanceTable OBJECT-TYPE + SYNTAX SEQUENCE OF CContextMappingBridgeInstanceEntry + MAX-ACCESS not-accessible + STATUS current + DESCRIPTION + "This table contains information on mapping between + cContextMappingVacmContextName and bridge instance. + + Bridge instance is an instance of a physical or logical + bridge which has unique bridge-id. + + If an entry is deleted from cContextMappingTable, the + corresponding entry in this table will also get deleted. + + If an entry needs to be created in this table, the + corresponding entry must exist in cContextMappingTable." + REFERENCE "BRIDGE-MIB" + ::= { cContextMappingMIBObjects 3 } + +cContextMappingBridgeInstanceEntry OBJECT-TYPE + SYNTAX CContextMappingBridgeInstanceEntry + MAX-ACCESS not-accessible + STATUS current + DESCRIPTION + "Information relating to a single mapping of + cContextMappingVacmContextName to the + corresponding bridge instance. + + To create a row in this table, a manager must set + cContextMappingBridgeInstRowStatus to either + 'createAndGo' or 'createAndWait'. + + To delete a row in this table, a manager must set + cContextMappingBridgeInstRowStatus to 'destroy'." + INDEX { cContextMappingVacmContextName } + ::= { cContextMappingBridgeInstanceTable 1 } + +CContextMappingBridgeInstanceEntry ::= SEQUENCE { + cContextMappingBridgeInstName SnmpAdminString, + cContextMappingBridgeInstStorageType StorageType, + cContextMappingBridgeInstRowStatus RowStatus +} + +cContextMappingBridgeInstName OBJECT-TYPE + SYNTAX SnmpAdminString + MAX-ACCESS read-create + STATUS current + DESCRIPTION + "The object identifies the name given to bridge + instance to which the SNMP context is mapped to. + + Value of this object cannot be changed when the + RowStatus object in the same row is 'active'. + + This is typically a human-readable string. This is + the same ASCII string used in the router's console + interface to refer to this bridge instance. + + When the value of this object is a zero length + string, it indicates that the SNMP context is + independent of any bridge instances." + ::= { cContextMappingBridgeInstanceEntry 1 } + +cContextMappingBridgeInstStorageType OBJECT-TYPE + SYNTAX StorageType + MAX-ACCESS read-create + STATUS current + DESCRIPTION + "The storage type for this conceptual row. + + Value of this object cannot be changed when the + RowStatus object in the same row is 'active'. + + Conceptual rows having the value 'permanent' need not + allow write-access to any columnar objects in the row." + DEFVAL { nonVolatile } + ::= { cContextMappingBridgeInstanceEntry 2 } + +cContextMappingBridgeInstRowStatus OBJECT-TYPE + SYNTAX RowStatus + MAX-ACCESS read-create + STATUS current + DESCRIPTION + "This object facilitates the creation, modification, or + deletion of a conceptual row in this table." + ::= { cContextMappingBridgeInstanceEntry 3 } + + + +cContextMappingLicenseGroupTable OBJECT-TYPE + SYNTAX SEQUENCE OF CContextMappingLicenseGroupEntry + MAX-ACCESS not-accessible + STATUS current + DESCRIPTION + "This table contains information on which + cContextMappingVacmContextName is mapped to + which License Group. + Group level licensing is used where each + Technology Package is enabled via a License." + ::= { cContextMappingMIBObjects 4 } + +cContextMappingLicenseGroupEntry OBJECT-TYPE + SYNTAX CContextMappingLicenseGroupEntry + MAX-ACCESS not-accessible + STATUS current + DESCRIPTION + "Information relating to a single mapping of + CContextMappingVacmContextName to the + corresponding License Group." + INDEX { cContextMappingVacmContextName } + ::= { cContextMappingLicenseGroupTable 1 } + +CContextMappingLicenseGroupEntry ::= SEQUENCE { + cContextMappingLicenseGroupName SnmpAdminString, + cContextMappingLicenseGroupStorageType StorageType, + cContextMappingLicenseGroupRowStatus RowStatus +} + +cContextMappingLicenseGroupName OBJECT-TYPE + SYNTAX SnmpAdminString (SIZE (0..32)) + MAX-ACCESS read-create + STATUS current + DESCRIPTION + "The value of an instance of this object identifies + the name given to the Group to which the SNMP context + is mapped. + + Feature sets from all groups will be combined to form + universal image. User can configure multiple groups as needed. + + For example: In Next generation ISRs will use + the universal image package level licensing model + for its licensing need. Each group has + the feature set needed for that specific technology. + Feature sets from different groups are combined to + form universal image and each feature set for a group + can be enabled using a valid license key. There will + be a base level ipbase package in which the router + boots with out any license key. + + The following are the different Technology Groups. + 1.crypto + 2.data + 3.ip + 4.legacy + 5.novpn-security + 6.security + 7.uc" + ::= { cContextMappingLicenseGroupEntry 1 } + +cContextMappingLicenseGroupStorageType OBJECT-TYPE + SYNTAX StorageType + MAX-ACCESS read-create + STATUS current + DESCRIPTION + "The storage type for this conceptual row. + + Conceptual rows having the value 'permanent' need not + allow write-access to any columnar objects in the row." + DEFVAL { nonVolatile } + ::= { cContextMappingLicenseGroupEntry 2 } + +cContextMappingLicenseGroupRowStatus OBJECT-TYPE + SYNTAX RowStatus + MAX-ACCESS read-create + STATUS current + DESCRIPTION + "This object facilitates the creation, modification, or + deletion of a conceptual row in this table." + ::= { cContextMappingLicenseGroupEntry 3 } + + +-- Conformance + +cContextMappingMIBCompliances OBJECT IDENTIFIER + ::= { cContextMappingMIBConformance 1 } + +cContextMappingMIBGroups OBJECT IDENTIFIER + ::= { cContextMappingMIBConformance 2 } + + +-- Compliance + +cContextMappingMIBCompliance MODULE-COMPLIANCE + STATUS deprecated + DESCRIPTION + "The compliance statement for entities which implement + the CISCO-CONTEXT-MAPPING-MIB." + MODULE -- this module + MANDATORY-GROUPS { cContextMappingDataGroup } + + OBJECT cContextMappingVrfName + MIN-ACCESS read-only + DESCRIPTION + "Write access is not required." + + OBJECT cContextMappingTopologyName + MIN-ACCESS read-only + DESCRIPTION + "Write access is not required." + + OBJECT cContextMappingProtoInstName + MIN-ACCESS read-only + DESCRIPTION + "Write access is not required." + + OBJECT cContextMappingStorageType + MIN-ACCESS read-only + DESCRIPTION + "Write access is not required." + + OBJECT cContextMappingRowStatus + MIN-ACCESS read-only + DESCRIPTION + "Create/delete/modify access to the + cContextMappingTable is not required." + ::= { cContextMappingMIBCompliances 1 } + +cContextMappingMIBComplianceRev1 MODULE-COMPLIANCE + STATUS deprecated + DESCRIPTION + "The compliance statement for entities which implement + the CISCO-CONTEXT-MAPPING-MIB. This compliance statement + is superceded by cContextMappingMIBComplianceRev2." + MODULE -- this module + MANDATORY-GROUPS { + cContextMappingDataGroup, + cContextMappingBridgeDomainDataGroup + } + + OBJECT cContextMappingVrfName + MIN-ACCESS read-only + DESCRIPTION + "Write access is not required." + + OBJECT cContextMappingTopologyName + MIN-ACCESS read-only + DESCRIPTION + "Write access is not required." + + OBJECT cContextMappingProtoInstName + MIN-ACCESS read-only + DESCRIPTION + "Write access is not required." + + OBJECT cContextMappingStorageType + MIN-ACCESS read-only + DESCRIPTION + "Write access is not required." + + OBJECT cContextMappingRowStatus + MIN-ACCESS read-only + DESCRIPTION + "Create/delete/modify access to the + cContextMappingTable is not required." + + OBJECT cContextMappingBridgeDomainIdentifier + MIN-ACCESS read-only + DESCRIPTION + "Write access is not required." + + OBJECT cContextMappingBridgeDomainStorageType + MIN-ACCESS read-only + DESCRIPTION + "Write access is not required." + + OBJECT cContextMappingBridgeDomainRowStatus + MIN-ACCESS read-only + DESCRIPTION + "Create/delete/modify access to the + cContextMappingTable is not required." + ::= { cContextMappingMIBCompliances 2 } + +cContextMappingMIBComplianceRev2 MODULE-COMPLIANCE + STATUS deprecated + DESCRIPTION + "The compliance statement for entities which implement + the CISCO-CONTEXT-MAPPING-MIB." + MODULE -- this module + MANDATORY-GROUPS { + cContextMappingDataGroup, + cContextMappingBridgeDomainDataGroup, + cContextMappingBridgeInstanceDataGroup + } + + OBJECT cContextMappingVrfName + MIN-ACCESS read-only + DESCRIPTION + "Write access is not required." + + OBJECT cContextMappingTopologyName + MIN-ACCESS read-only + DESCRIPTION + "Write access is not required." + + OBJECT cContextMappingProtoInstName + MIN-ACCESS read-only + DESCRIPTION + "Write access is not required." + + OBJECT cContextMappingStorageType + MIN-ACCESS read-only + DESCRIPTION + "Write access is not required." + + OBJECT cContextMappingRowStatus + MIN-ACCESS read-only + DESCRIPTION + "Create/delete/modify access to the + cContextMappingTable is not required." + + OBJECT cContextMappingBridgeDomainIdentifier + MIN-ACCESS read-only + DESCRIPTION + "Write access is not required." + + OBJECT cContextMappingBridgeDomainStorageType + MIN-ACCESS read-only + DESCRIPTION + "Write access is not required." + + OBJECT cContextMappingBridgeDomainRowStatus + MIN-ACCESS read-only + DESCRIPTION + "Create/delete/modify access to the + cContextMappingBridgeDomainTable is not required." + + OBJECT cContextMappingBridgeInstName + MIN-ACCESS read-only + DESCRIPTION + "Write access is not required." + + OBJECT cContextMappingBridgeInstStorageType + MIN-ACCESS read-only + DESCRIPTION + "Write access is not required." + + OBJECT cContextMappingBridgeInstRowStatus + MIN-ACCESS read-only + DESCRIPTION + "Create/delete/modify access to the + cContextMappingBridgeInstanceTable is not required." + ::= { cContextMappingMIBCompliances 3 } + +cContextMappingMIBComplianceRev3 MODULE-COMPLIANCE + STATUS current + DESCRIPTION + "The compliance statement for entities which implement + the CISCO-CONTEXT-MAPPING-MIB." + MODULE -- this module + MANDATORY-GROUPS { + cContextMappingDataGroup, + cContextMappingBridgeDomainDataGroup, + cContextMappingBridgeInstanceDataGroup, + cContextMappingLicenseGroupDataGroup + } + + OBJECT cContextMappingVrfName + MIN-ACCESS read-only + DESCRIPTION + "Write access is not required." + + OBJECT cContextMappingTopologyName + MIN-ACCESS read-only + DESCRIPTION + "Write access is not required." + + OBJECT cContextMappingProtoInstName + MIN-ACCESS read-only + DESCRIPTION + "Write access is not required." + + OBJECT cContextMappingStorageType + MIN-ACCESS read-only + DESCRIPTION + "Write access is not required." + + OBJECT cContextMappingRowStatus + MIN-ACCESS read-only + DESCRIPTION + "Create/delete/modify access to the + cContextMappingTable is not required." + + OBJECT cContextMappingBridgeDomainIdentifier + MIN-ACCESS read-only + DESCRIPTION + "Write access is not required." + + OBJECT cContextMappingBridgeDomainStorageType + MIN-ACCESS read-only + DESCRIPTION + "Write access is not required." + + OBJECT cContextMappingBridgeDomainRowStatus + MIN-ACCESS read-only + DESCRIPTION + "Create/delete/modify access to the + cContextMappingBridgeDomainTable is not required." + + OBJECT cContextMappingBridgeInstName + MIN-ACCESS read-only + DESCRIPTION + "Write access is not required." + + OBJECT cContextMappingBridgeInstStorageType + MIN-ACCESS read-only + DESCRIPTION + "Write access is not required." + + OBJECT cContextMappingBridgeInstRowStatus + MIN-ACCESS read-only + DESCRIPTION + "Create/delete/modify access to the + cContextMappingBridgeInstanceTable is not required." + + OBJECT cContextMappingLicenseGroupName + MIN-ACCESS read-only + DESCRIPTION + "Write access is not required." + + OBJECT cContextMappingLicenseGroupStorageType + MIN-ACCESS read-only + DESCRIPTION + "Write access is not required." + + OBJECT cContextMappingLicenseGroupRowStatus + MIN-ACCESS read-only + DESCRIPTION + "Create/delete/modify access to the + cContextMappingTable is not required." + ::= { cContextMappingMIBCompliances 4 } + +-- Units of Conformance + +cContextMappingDataGroup OBJECT-GROUP + OBJECTS { + cContextMappingVrfName, + cContextMappingTopologyName, + cContextMappingProtoInstName, + cContextMappingStorageType, + cContextMappingRowStatus + } + STATUS current + DESCRIPTION + "The collection of objects providing the context + mapping data between the SNMP context to the + corresponding VRF, the corresponding topology, + and the corresponding routing protocol instance." + ::= { cContextMappingMIBGroups 1 } + +cContextMappingBridgeDomainDataGroup OBJECT-GROUP + OBJECTS { + cContextMappingBridgeDomainIdentifier, + cContextMappingBridgeDomainStorageType, + cContextMappingBridgeDomainRowStatus + } + STATUS current + DESCRIPTION + "The collection of objects providing the context + mapping data between the SNMP context to the + corresponding bridge domain." + ::= { cContextMappingMIBGroups 2 } + +cContextMappingBridgeInstanceDataGroup OBJECT-GROUP + OBJECTS { + cContextMappingBridgeInstName, + cContextMappingBridgeInstStorageType, + cContextMappingBridgeInstRowStatus + } + STATUS current + DESCRIPTION + "The collection of objects providing the context + mapping data between the SNMP context to the + corresponding bridge instance." + ::= { cContextMappingMIBGroups 3 } + +cContextMappingLicenseGroupDataGroup OBJECT-GROUP + OBJECTS { + cContextMappingLicenseGroupName, + cContextMappingLicenseGroupStorageType, + cContextMappingLicenseGroupStorageType, + cContextMappingLicenseGroupRowStatus + } + STATUS current + DESCRIPTION + "The collection of objects providing the context + mapping data between the SNMP context to the + corresponding LicenseGroupName." + ::= { cContextMappingMIBGroups 4 } + +END + + + + + + + +