1-- *****************************************************************
2-- CISCO-CONTEXT-MAPPING-MIB.my:  Cisco Context Mapping MIB
3--
4-- January 2005, Chinna Pellacuru.
5--
6-- May 2008, Sheethal Gunjal.
7--
8-- Copyright (c) 2004-2005, 2008 by cisco Systems Inc.
9-- All rights reserved.
10--
11-- ****************************************************************
12
13CISCO-CONTEXT-MAPPING-MIB DEFINITIONS ::= BEGIN
14
15IMPORTS
16    MODULE-IDENTITY,
17    OBJECT-TYPE
18        FROM SNMPv2-SMI
19    MODULE-COMPLIANCE,
20    OBJECT-GROUP
21        FROM SNMPv2-CONF
22    SnmpAdminString
23        FROM SNMP-FRAMEWORK-MIB
24    RowStatus,
25    StorageType
26        FROM SNMPv2-TC
27    CiscoBridgeDomain
28        FROM CISCO-TC
29    ciscoMgmt
30        FROM CISCO-SMI;
31
32
33ciscoContextMappingMIB MODULE-IDENTITY
34    LAST-UPDATED    "200811220000Z"
35    ORGANIZATION    "Cisco Systems, Inc."
36    CONTACT-INFO
37            "Cisco Systems
38            Customer Service
39
40            Postal: 170 W Tasman Drive
41            San Jose, CA  95134
42            USA
43
44            Tel: +1 800 553-NETS
45
46            E-mail: cs-snmp@cisco.com"
47    DESCRIPTION
48        "A single SNMP agent sometimes needs to support multiple
49        instances of the same MIB module, and does so through the
50        use of multiple SNMP contexts.  This typically occurs because
51        the technology has evolved to have extra dimension(s), i.e.,
52        one or more extra data and/or identifier values which are
53        different in the different contexts, but were not defined in
54        INDEX clause(s) of the original MIB module.  In such cases,
55        network management applications need to know the specific
56        data/identifier values in each context, and this MIB module
57        provides mapping tables which contain that information.
58
59        Within a network there can be multiple Virtual Private
60        Networks (VPNs) configured using Virtual Routing and
61        Forwarding Instances (VRFs). Within a VPN there can be
62        multiple topologies when Multi-topology Routing (MTR) is
63        used. Also, Interior Gateway Protocols (IGPs) can have
64        multiple protocol instances running on the device.
65        A network can have multiple broadcast domains configured
66        using Bridge Domain Identifiers.
67
68        With MTR routing, VRFs, and Bridge domains, a router now
69        needs to support multiple instances of several existing
70        MIB modules, and this can be achieved if the router's SNMP
71        agent provides access to each instance of the same MIB module
72        via a different SNMP context (see Section 3.1.1 of RFC 3411).
73        For MTR routing, VRFs, and Bridge domains, a different SNMP
74        context is needed depending on one or more of the following:
75        the VRF, the topology-identifier, the routing protocol instance,
76        and the bridge domain identifier.
77        In other words, the router's management information can be
78        accessed through multiple SNMP contexts where each such
79        context represents a specific VRF, a specific
80        topology-identifier, a specific routing protocol instance
81        and/or a bridge domain identifier. This MIB module provides
82        a mapping of each such SNMP context to the corresponding VRF,
83        the corresponding topology, the corresponding routing protocol
84        instance, and the corresponding bridge domain identifier.
85        Some SNMP contexts are independent of VRFs, independent of
86        a topology, independent of a routing protocol instance, or
87        independent of a bridge domain and in such a case, the mapping
88        is to the zero length string.
89
90        With the Cisco package licensing strategy, the features
91        available in the image are grouped into multiple packages
92        and each packages can be managed to operate at different
93        feature levels based on the available license. This MIB
94        module provides option to associate an SNMP context to a
95        feature package group. This will allow manageability of
96        license MIB objects specific to a feature package group.
97
98        As technology evolves more we may need additional
99        identifiers to identify the context. Then we would need
100        to add those additional identifiers into the mapping."
101    REVISION        "200811220000Z"
102    DESCRIPTION
103        "Added New Table cContextMappingLicenseGroupTable
104        to provide SNMP Context support for license package groups.
105
106        Added cContextMappingLicenseGroupDataGroup in OBJECT-GROUP
107        Added cContextMappingMIBComplianceRev2 in MODULE-COMPLIANCE
108
109        Updated the MIB description to indicate the use of
110        the above additions"
111    REVISION        "200805300000Z"
112    DESCRIPTION
113        "Add cContextMappingBridgeInstanceTable.
114
115        Added cContextMappingBridgeInstanceDataGroup.
116        Deprecated cContextMappingMIBComplianceRev1 and added
117        cContextMappingMIBComplianceRev2 compliance statement."
118    REVISION        "200802010000Z"
119    DESCRIPTION
120        "Added New Table cContextMappingBridgeDomainTable
121        to provide SNMP context support to the Bridge Domain.
122
123        Added cContextMappingBridgeDomainDataGroup in OBJECT-GROUP
124        Added cContextMappingMIBComplianceRev1 in MODULE-COMPLIANCE"
125    REVISION        "200503170000Z"
126    DESCRIPTION
127        "Initial version of the MIB module."
128    ::= { ciscoMgmt 468 }
129
130
131cContextMappingMIBObjects  OBJECT IDENTIFIER
132    ::= { ciscoContextMappingMIB 1 }
133
134cContextMappingMIBConformance  OBJECT IDENTIFIER
135    ::= { ciscoContextMappingMIB 2 }
136
137
138cContextMappingTable OBJECT-TYPE
139    SYNTAX          SEQUENCE OF CContextMappingEntry
140    MAX-ACCESS      not-accessible
141    STATUS          current
142    DESCRIPTION
143        "This table contains information on which
144        cContextMappingVacmContextName is mapped to
145        which VRF, topology, and routing protocol instance.
146
147        This table is indexed by SNMP VACM context.
148
149        Configuring a row in this table for an SNMP context
150        does not require that the context be already defined,
151        i.e., a row can be created in this table for a context
152        before the corresponding row is created in RFC 3415's
153        vacmContextTable.
154
155        To create a row in this table, a manager must set
156        cContextMappingRowStatus to either 'createAndGo' or
157        'createAndWait'.
158
159        To delete a row in this table, a manager must set
160        cContextMappingRowStatus to 'destroy'."
161    ::= { cContextMappingMIBObjects 1 }
162
163cContextMappingEntry OBJECT-TYPE
164    SYNTAX          CContextMappingEntry
165    MAX-ACCESS      not-accessible
166    STATUS          current
167    DESCRIPTION
168        "Information relating to a single mapping of
169        cContextMappingVacmContextName to the corresponding VRF,
170        the corresponding topology, and the corresponding routing
171        protocol instance."
172    INDEX           { cContextMappingVacmContextName }
173    ::= { cContextMappingTable 1 }
174
175CContextMappingEntry ::= SEQUENCE {
176        cContextMappingVacmContextName SnmpAdminString,
177        cContextMappingVrfName         SnmpAdminString,
178        cContextMappingTopologyName    SnmpAdminString,
179        cContextMappingProtoInstName   SnmpAdminString,
180        cContextMappingStorageType     StorageType,
181        cContextMappingRowStatus       RowStatus
182}
183
184cContextMappingVacmContextName OBJECT-TYPE
185    SYNTAX          SnmpAdminString (SIZE  (0..32))
186    MAX-ACCESS      not-accessible
187    STATUS          current
188    DESCRIPTION
189        "The vacmContextName given to the SNMP context.
190
191        This is a human readable name identifying a particular
192        SNMP VACM context at a particular SNMP entity.
193        The empty contextName (zero length) represents the
194        default context."
195    ::= { cContextMappingEntry 1 }
196
197cContextMappingVrfName OBJECT-TYPE
198    SYNTAX          SnmpAdminString (SIZE  (0..32))
199    MAX-ACCESS      read-create
200    STATUS          current
201    DESCRIPTION
202        "The value of an instance of this object identifies
203        the name given to the VRF to which the SNMP context
204        is mapped to.
205
206        This is typically a human-readable string. This is
207        the same ASCII string used in the router's console
208        interface to refer to this VRF.
209
210        When the value of this object is the zero length
211        string it indicates that the SNMP context is independent
212        of any VRF."
213    DEFVAL          { ''H }
214    ::= { cContextMappingEntry 2 }
215
216cContextMappingTopologyName OBJECT-TYPE
217    SYNTAX          SnmpAdminString (SIZE  (0..32))
218    MAX-ACCESS      read-create
219    STATUS          current
220    DESCRIPTION
221        "The value of an instance of this object identifies
222        the name given to the topology to which the SNMP
223        context is mapped to.
224
225        This is typically a human-readable string. This is
226        the same ASCII string used in the router's console
227        interface to refer to this topology.
228
229        When the value of this object is the zero length
230        string it indicates that the SNMP context is independent
231        of any topology."
232    DEFVAL          { ''H }
233    ::= { cContextMappingEntry 3 }
234
235cContextMappingProtoInstName OBJECT-TYPE
236    SYNTAX          SnmpAdminString (SIZE  (0..32))
237    MAX-ACCESS      read-create
238    STATUS          current
239    DESCRIPTION
240        "The value of an instance of this object identifies
241        the name given to the protocol instance to which the
242        SNMP context is mapped to.
243
244        This is typically a human-readable string. This is
245        the same ASCII string used in the router's console
246        interface to refer to this protocol instance.
247
248        When the value of this object is the zero length
249        string it indicates that the SNMP context is independent
250        of any protocol instance."
251    DEFVAL          { ''H }
252    ::= { cContextMappingEntry 4 }
253
254cContextMappingStorageType OBJECT-TYPE
255    SYNTAX          StorageType
256    MAX-ACCESS      read-create
257    STATUS          current
258    DESCRIPTION
259        "The storage type for this conceptual row.
260
261        Conceptual rows having the value 'permanent' need not
262        allow write-access to any columnar objects in the row."
263    DEFVAL          { nonVolatile }
264    ::= { cContextMappingEntry 5 }
265
266cContextMappingRowStatus OBJECT-TYPE
267    SYNTAX          RowStatus
268    MAX-ACCESS      read-create
269    STATUS          current
270    DESCRIPTION
271        "This object facilitates the creation, modification, or
272        deletion of a conceptual row in this table."
273    ::= { cContextMappingEntry 6 }
274
275
276
277cContextMappingBridgeDomainTable OBJECT-TYPE
278    SYNTAX          SEQUENCE OF CContextMappingBridgeDomainEntry
279    MAX-ACCESS      not-accessible
280    STATUS          current
281    DESCRIPTION
282        "This table contains information on which
283        cContextMappingVacmContextName is mapped to
284        which bridge domain.
285
286        A Bridge Domain is one of the means by which it is possible
287        to define an Ethernet broadcast domain on a bridging device.
288        A network can have multiple broadcast domains configured.
289        This table helps the network management personnel to find
290        out the  details of various broadcast domains configured
291        in the network.
292
293        An entry need to exist in cContextMappingTable, to create
294        an entry in this table."
295    ::= { cContextMappingMIBObjects 2 }
296
297cContextMappingBridgeDomainEntry OBJECT-TYPE
298    SYNTAX          CContextMappingBridgeDomainEntry
299    MAX-ACCESS      not-accessible
300    STATUS          current
301    DESCRIPTION
302        "Information relating to a single mapping of
303        cContextMappingVacmContextName to the
304        corresponding bridge domain.
305
306        To create a row in this table, a manager must set
307        cContextMappingBridgeDomainRowStatus to either
308        'createAndGo' or 'createAndWait'.
309
310        To delete a row in this table, a manager must set
311        cContextMappingBridgeDomainRowStatus to 'destroy'."
312    INDEX           { cContextMappingVacmContextName }
313    ::= { cContextMappingBridgeDomainTable 1 }
314
315CContextMappingBridgeDomainEntry ::= SEQUENCE {
316        cContextMappingBridgeDomainIdentifier  CiscoBridgeDomain,
317        cContextMappingBridgeDomainStorageType StorageType,
318        cContextMappingBridgeDomainRowStatus   RowStatus
319}
320
321cContextMappingBridgeDomainIdentifier OBJECT-TYPE
322    SYNTAX          CiscoBridgeDomain
323    MAX-ACCESS      read-create
324    STATUS          current
325    DESCRIPTION
326        "The value of an instance of this object identifies
327        the bridge domain to which the SNMP context is
328        mapped to."
329    REFERENCE       "CISCO-BRIDGE-DOMAIN-MIB"
330    ::= { cContextMappingBridgeDomainEntry 1 }
331
332cContextMappingBridgeDomainStorageType OBJECT-TYPE
333    SYNTAX          StorageType
334    MAX-ACCESS      read-create
335    STATUS          current
336    DESCRIPTION
337        "The storage type for this conceptual row.
338
339        Conceptual rows having the value 'permanent' need not
340        allow write-access to any columnar objects in the row."
341    DEFVAL          { nonVolatile }
342    ::= { cContextMappingBridgeDomainEntry 2 }
343
344cContextMappingBridgeDomainRowStatus OBJECT-TYPE
345    SYNTAX          RowStatus
346    MAX-ACCESS      read-create
347    STATUS          current
348    DESCRIPTION
349        "This object facilitates the creation, modification, or
350        deletion of a conceptual row in this table."
351    ::= { cContextMappingBridgeDomainEntry 3 }
352
353
354
355cContextMappingBridgeInstanceTable OBJECT-TYPE
356    SYNTAX          SEQUENCE OF CContextMappingBridgeInstanceEntry
357    MAX-ACCESS      not-accessible
358    STATUS          current
359    DESCRIPTION
360        "This table contains information on mapping between
361        cContextMappingVacmContextName and bridge instance.
362
363        Bridge instance is an instance of a physical or logical
364        bridge which has unique bridge-id.
365
366        If an entry is deleted from cContextMappingTable, the
367        corresponding entry in this table will also get deleted.
368
369        If an entry needs to be created in this table, the
370        corresponding entry must exist in cContextMappingTable."
371    REFERENCE       "BRIDGE-MIB"
372    ::= { cContextMappingMIBObjects 3 }
373
374cContextMappingBridgeInstanceEntry OBJECT-TYPE
375    SYNTAX          CContextMappingBridgeInstanceEntry
376    MAX-ACCESS      not-accessible
377    STATUS          current
378    DESCRIPTION
379        "Information relating to a single mapping of
380        cContextMappingVacmContextName to the
381        corresponding bridge instance.
382
383        To create a row in this table, a manager must set
384        cContextMappingBridgeInstRowStatus to either
385        'createAndGo' or 'createAndWait'.
386
387        To delete a row in this table, a manager must set
388        cContextMappingBridgeInstRowStatus to 'destroy'."
389    INDEX           { cContextMappingVacmContextName }
390    ::= { cContextMappingBridgeInstanceTable 1 }
391
392CContextMappingBridgeInstanceEntry ::= SEQUENCE {
393        cContextMappingBridgeInstName        SnmpAdminString,
394        cContextMappingBridgeInstStorageType StorageType,
395        cContextMappingBridgeInstRowStatus   RowStatus
396}
397
398cContextMappingBridgeInstName OBJECT-TYPE
399    SYNTAX          SnmpAdminString
400    MAX-ACCESS      read-create
401    STATUS          current
402    DESCRIPTION
403        "The object identifies the name given to bridge
404        instance to which the SNMP context is mapped to.
405
406        Value of this object cannot be changed when the
407        RowStatus object in the same row is 'active'.
408
409        This is typically a human-readable string. This is
410        the same ASCII string used in the router's console
411        interface to refer to this bridge instance.
412
413        When the value of this object is a zero length
414        string, it indicates that the SNMP context is
415        independent of any bridge instances."
416    ::= { cContextMappingBridgeInstanceEntry 1 }
417
418cContextMappingBridgeInstStorageType OBJECT-TYPE
419    SYNTAX          StorageType
420    MAX-ACCESS      read-create
421    STATUS          current
422    DESCRIPTION
423        "The storage type for this conceptual row.
424
425        Value of this object cannot be changed when the
426        RowStatus object in the same row is 'active'.
427
428        Conceptual rows having the value 'permanent' need not
429        allow write-access to any columnar objects in the row."
430    DEFVAL          { nonVolatile }
431    ::= { cContextMappingBridgeInstanceEntry 2 }
432
433cContextMappingBridgeInstRowStatus OBJECT-TYPE
434    SYNTAX          RowStatus
435    MAX-ACCESS      read-create
436    STATUS          current
437    DESCRIPTION
438        "This object facilitates the creation, modification, or
439        deletion of a conceptual row in this table."
440    ::= { cContextMappingBridgeInstanceEntry 3 }
441
442
443
444cContextMappingLicenseGroupTable OBJECT-TYPE
445    SYNTAX          SEQUENCE OF CContextMappingLicenseGroupEntry
446    MAX-ACCESS      not-accessible
447    STATUS          current
448    DESCRIPTION
449        "This table contains information on which
450        cContextMappingVacmContextName is mapped to
451        which License Group.
452        Group level licensing is used where each
453        Technology Package is enabled via a License."
454    ::= { cContextMappingMIBObjects 4 }
455
456cContextMappingLicenseGroupEntry OBJECT-TYPE
457    SYNTAX          CContextMappingLicenseGroupEntry
458    MAX-ACCESS      not-accessible
459    STATUS          current
460    DESCRIPTION
461        "Information relating to a single mapping of
462        CContextMappingVacmContextName to the
463        corresponding License Group."
464    INDEX           { cContextMappingVacmContextName }
465    ::= { cContextMappingLicenseGroupTable 1 }
466
467CContextMappingLicenseGroupEntry ::= SEQUENCE {
468        cContextMappingLicenseGroupName        SnmpAdminString,
469        cContextMappingLicenseGroupStorageType StorageType,
470        cContextMappingLicenseGroupRowStatus   RowStatus
471}
472
473cContextMappingLicenseGroupName OBJECT-TYPE
474    SYNTAX          SnmpAdminString (SIZE  (0..32))
475    MAX-ACCESS      read-create
476    STATUS          current
477    DESCRIPTION
478        "The value of an instance of this object identifies
479        the name given to the Group to which the SNMP context
480        is mapped.
481
482        Feature sets from all groups will be combined to form
483        universal image. User can configure multiple groups as needed.
484
485        For example: In Next generation ISRs will use
486        the universal image package level licensing model
487        for its licensing need. Each group has
488        the feature set needed for that specific technology.
489        Feature sets from different groups are combined to
490        form universal image and each feature set for a group
491        can be enabled using a valid license key. There will
492        be a base level ipbase package in which the router
493        boots with out any license key.
494
495        The following are the different Technology Groups.
496        1.crypto
497        2.data
498        3.ip
499        4.legacy
500        5.novpn-security
501        6.security
502        7.uc"
503    ::= { cContextMappingLicenseGroupEntry 1 }
504
505cContextMappingLicenseGroupStorageType OBJECT-TYPE
506    SYNTAX          StorageType
507    MAX-ACCESS      read-create
508    STATUS          current
509    DESCRIPTION
510        "The storage type for this conceptual row.
511
512        Conceptual rows having the value 'permanent' need not
513        allow write-access to any columnar objects in the row."
514    DEFVAL          { nonVolatile }
515    ::= { cContextMappingLicenseGroupEntry 2 }
516
517cContextMappingLicenseGroupRowStatus OBJECT-TYPE
518    SYNTAX          RowStatus
519    MAX-ACCESS      read-create
520    STATUS          current
521    DESCRIPTION
522        "This object facilitates the creation, modification, or
523        deletion of a conceptual row in this table."
524    ::= { cContextMappingLicenseGroupEntry 3 }
525
526
527-- Conformance
528
529cContextMappingMIBCompliances  OBJECT IDENTIFIER
530    ::= { cContextMappingMIBConformance 1 }
531
532cContextMappingMIBGroups  OBJECT IDENTIFIER
533    ::= { cContextMappingMIBConformance 2 }
534
535
536-- Compliance
537
538cContextMappingMIBCompliance MODULE-COMPLIANCE
539    STATUS          deprecated
540    DESCRIPTION
541        "The compliance statement for entities which implement
542        the CISCO-CONTEXT-MAPPING-MIB."
543    MODULE          -- this module
544    MANDATORY-GROUPS { cContextMappingDataGroup }
545
546    OBJECT          cContextMappingVrfName
547    MIN-ACCESS      read-only
548    DESCRIPTION
549        "Write access is not required."
550
551    OBJECT          cContextMappingTopologyName
552    MIN-ACCESS      read-only
553    DESCRIPTION
554        "Write access is not required."
555
556    OBJECT          cContextMappingProtoInstName
557    MIN-ACCESS      read-only
558    DESCRIPTION
559        "Write access is not required."
560
561    OBJECT          cContextMappingStorageType
562    MIN-ACCESS      read-only
563    DESCRIPTION
564        "Write access is not required."
565
566    OBJECT          cContextMappingRowStatus
567    MIN-ACCESS      read-only
568    DESCRIPTION
569        "Create/delete/modify access to the
570        cContextMappingTable is not required."
571    ::= { cContextMappingMIBCompliances 1 }
572
573cContextMappingMIBComplianceRev1 MODULE-COMPLIANCE
574    STATUS          deprecated
575    DESCRIPTION
576        "The compliance statement for entities which implement
577        the CISCO-CONTEXT-MAPPING-MIB. This compliance statement
578        is superceded by cContextMappingMIBComplianceRev2."
579    MODULE          -- this module
580    MANDATORY-GROUPS {
581                        cContextMappingDataGroup,
582                        cContextMappingBridgeDomainDataGroup
583                    }
584
585    OBJECT          cContextMappingVrfName
586    MIN-ACCESS      read-only
587    DESCRIPTION
588        "Write access is not required."
589
590    OBJECT          cContextMappingTopologyName
591    MIN-ACCESS      read-only
592    DESCRIPTION
593        "Write access is not required."
594
595    OBJECT          cContextMappingProtoInstName
596    MIN-ACCESS      read-only
597    DESCRIPTION
598        "Write access is not required."
599
600    OBJECT          cContextMappingStorageType
601    MIN-ACCESS      read-only
602    DESCRIPTION
603        "Write access is not required."
604
605    OBJECT          cContextMappingRowStatus
606    MIN-ACCESS      read-only
607    DESCRIPTION
608        "Create/delete/modify access to the
609        cContextMappingTable is not required."
610
611    OBJECT          cContextMappingBridgeDomainIdentifier
612    MIN-ACCESS      read-only
613    DESCRIPTION
614        "Write access is not required."
615
616    OBJECT          cContextMappingBridgeDomainStorageType
617    MIN-ACCESS      read-only
618    DESCRIPTION
619        "Write access is not required."
620
621    OBJECT          cContextMappingBridgeDomainRowStatus
622    MIN-ACCESS      read-only
623    DESCRIPTION
624        "Create/delete/modify access to the
625        cContextMappingTable is not required."
626    ::= { cContextMappingMIBCompliances 2 }
627
628cContextMappingMIBComplianceRev2 MODULE-COMPLIANCE
629    STATUS          deprecated
630    DESCRIPTION
631        "The compliance statement for entities which implement
632        the CISCO-CONTEXT-MAPPING-MIB."
633    MODULE          -- this module
634    MANDATORY-GROUPS {
635                        cContextMappingDataGroup,
636                        cContextMappingBridgeDomainDataGroup,
637                        cContextMappingBridgeInstanceDataGroup
638                    }
639
640    OBJECT          cContextMappingVrfName
641    MIN-ACCESS      read-only
642    DESCRIPTION
643        "Write access is not required."
644
645    OBJECT          cContextMappingTopologyName
646    MIN-ACCESS      read-only
647    DESCRIPTION
648        "Write access is not required."
649
650    OBJECT          cContextMappingProtoInstName
651    MIN-ACCESS      read-only
652    DESCRIPTION
653        "Write access is not required."
654
655    OBJECT          cContextMappingStorageType
656    MIN-ACCESS      read-only
657    DESCRIPTION
658        "Write access is not required."
659
660    OBJECT          cContextMappingRowStatus
661    MIN-ACCESS      read-only
662    DESCRIPTION
663        "Create/delete/modify access to the
664        cContextMappingTable is not required."
665
666    OBJECT          cContextMappingBridgeDomainIdentifier
667    MIN-ACCESS      read-only
668    DESCRIPTION
669        "Write access is not required."
670
671    OBJECT          cContextMappingBridgeDomainStorageType
672    MIN-ACCESS      read-only
673    DESCRIPTION
674        "Write access is not required."
675
676    OBJECT          cContextMappingBridgeDomainRowStatus
677    MIN-ACCESS      read-only
678    DESCRIPTION
679        "Create/delete/modify access to the
680        cContextMappingBridgeDomainTable is not required."
681
682    OBJECT          cContextMappingBridgeInstName
683    MIN-ACCESS      read-only
684    DESCRIPTION
685        "Write access is not required."
686
687    OBJECT          cContextMappingBridgeInstStorageType
688    MIN-ACCESS      read-only
689    DESCRIPTION
690        "Write access is not required."
691
692    OBJECT          cContextMappingBridgeInstRowStatus
693    MIN-ACCESS      read-only
694    DESCRIPTION
695        "Create/delete/modify access to the
696        cContextMappingBridgeInstanceTable is not required."
697    ::= { cContextMappingMIBCompliances 3 }
698
699cContextMappingMIBComplianceRev3 MODULE-COMPLIANCE
700    STATUS          current
701    DESCRIPTION
702        "The compliance statement for entities which implement
703        the CISCO-CONTEXT-MAPPING-MIB."
704    MODULE          -- this module
705    MANDATORY-GROUPS {
706                        cContextMappingDataGroup,
707                        cContextMappingBridgeDomainDataGroup,
708                        cContextMappingBridgeInstanceDataGroup,
709                        cContextMappingLicenseGroupDataGroup
710                    }
711
712    OBJECT          cContextMappingVrfName
713    MIN-ACCESS      read-only
714    DESCRIPTION
715        "Write access is not required."
716
717    OBJECT          cContextMappingTopologyName
718    MIN-ACCESS      read-only
719    DESCRIPTION
720        "Write access is not required."
721
722    OBJECT          cContextMappingProtoInstName
723    MIN-ACCESS      read-only
724    DESCRIPTION
725        "Write access is not required."
726
727    OBJECT          cContextMappingStorageType
728    MIN-ACCESS      read-only
729    DESCRIPTION
730        "Write access is not required."
731
732    OBJECT          cContextMappingRowStatus
733    MIN-ACCESS      read-only
734    DESCRIPTION
735        "Create/delete/modify access to the
736        cContextMappingTable is not required."
737
738    OBJECT          cContextMappingBridgeDomainIdentifier
739    MIN-ACCESS      read-only
740    DESCRIPTION
741        "Write access is not required."
742
743    OBJECT          cContextMappingBridgeDomainStorageType
744    MIN-ACCESS      read-only
745    DESCRIPTION
746        "Write access is not required."
747
748    OBJECT          cContextMappingBridgeDomainRowStatus
749    MIN-ACCESS      read-only
750    DESCRIPTION
751        "Create/delete/modify access to the
752        cContextMappingBridgeDomainTable is not required."
753
754    OBJECT          cContextMappingBridgeInstName
755    MIN-ACCESS      read-only
756    DESCRIPTION
757        "Write access is not required."
758
759    OBJECT          cContextMappingBridgeInstStorageType
760    MIN-ACCESS      read-only
761    DESCRIPTION
762        "Write access is not required."
763
764    OBJECT          cContextMappingBridgeInstRowStatus
765    MIN-ACCESS      read-only
766    DESCRIPTION
767        "Create/delete/modify access to the
768        cContextMappingBridgeInstanceTable is not required."
769
770    OBJECT          cContextMappingLicenseGroupName
771    MIN-ACCESS      read-only
772    DESCRIPTION
773        "Write access is not required."
774
775    OBJECT          cContextMappingLicenseGroupStorageType
776    MIN-ACCESS      read-only
777    DESCRIPTION
778        "Write access is not required."
779
780    OBJECT          cContextMappingLicenseGroupRowStatus
781    MIN-ACCESS      read-only
782    DESCRIPTION
783        "Create/delete/modify access to the
784        cContextMappingTable is not required."
785    ::= { cContextMappingMIBCompliances 4 }
786
787-- Units of Conformance
788
789cContextMappingDataGroup OBJECT-GROUP
790    OBJECTS         {
791                        cContextMappingVrfName,
792                        cContextMappingTopologyName,
793                        cContextMappingProtoInstName,
794                        cContextMappingStorageType,
795                        cContextMappingRowStatus
796                    }
797    STATUS          current
798    DESCRIPTION
799        "The collection of objects providing the context
800        mapping data between the SNMP context to the
801        corresponding VRF, the corresponding topology,
802        and the corresponding routing protocol instance."
803    ::= { cContextMappingMIBGroups 1 }
804
805cContextMappingBridgeDomainDataGroup OBJECT-GROUP
806    OBJECTS         {
807                        cContextMappingBridgeDomainIdentifier,
808                        cContextMappingBridgeDomainStorageType,
809                        cContextMappingBridgeDomainRowStatus
810                    }
811    STATUS          current
812    DESCRIPTION
813        "The collection of objects providing the context
814        mapping data between the SNMP context to the
815        corresponding bridge domain."
816    ::= { cContextMappingMIBGroups 2 }
817
818cContextMappingBridgeInstanceDataGroup OBJECT-GROUP
819    OBJECTS         {
820                        cContextMappingBridgeInstName,
821                        cContextMappingBridgeInstStorageType,
822                        cContextMappingBridgeInstRowStatus
823                    }
824    STATUS          current
825    DESCRIPTION
826        "The collection of objects providing the context
827        mapping data between the SNMP context to the
828        corresponding bridge instance."
829    ::= { cContextMappingMIBGroups 3 }
830
831cContextMappingLicenseGroupDataGroup OBJECT-GROUP
832    OBJECTS         {
833                        cContextMappingLicenseGroupName,
834                        cContextMappingLicenseGroupStorageType,
835                        cContextMappingLicenseGroupStorageType,
836                        cContextMappingLicenseGroupRowStatus
837                    }
838    STATUS          current
839    DESCRIPTION
840        "The collection of objects providing the context
841        mapping data between the SNMP context to the
842        corresponding LicenseGroupName."
843    ::= { cContextMappingMIBGroups 4 }
844
845END
846
847
848
849
850
851
852
853
854