1-- *****************************************************************
2-- CISCO-DYNTAMIC-TEMPLATE-TC-MIB
3-- Definitions of textual conventions used by MIB modules describing
4-- and using dynamic templates.
5--
6-- September 2007, Patrick R. Gili
7--
8-- Copyright (c) 2007, 2011-2012 by Cisco Systems Inc.
9-- All rights reserved.
10-- *****************************************************************
11
12CISCO-DYNAMIC-TEMPLATE-TC-MIB DEFINITIONS ::= BEGIN
13
14IMPORTS
15    MODULE-IDENTITY
16        FROM SNMPv2-SMI
17    TEXTUAL-CONVENTION
18        FROM SNMPv2-TC
19    ciscoMgmt
20        FROM CISCO-SMI;
21
22
23ciscoDynamicTemplateTcMIB MODULE-IDENTITY
24    LAST-UPDATED    "201201270000Z"
25    ORGANIZATION    "Cisco Systems, Inc."
26    CONTACT-INFO
27            "Cisco Systems
28            Customer Service
29
30            Postal: 170 W Tasman Drive
31            San Jose, CA 95134
32
33            Tel: +1 800 553-NETS
34
35            E-mail: cs-snmp@cisco.com"
36    DESCRIPTION
37        "This MIB module defines textual conventions used by the
38        CISCO-DYNAMIC-TEMPLATE-MIB and MIB modules that use and expand
39        on dynamic templates."
40    REVISION        "200709060000Z"
41    DESCRIPTION
42        "The initial version of the MIB module."
43    ::= { ciscoMgmt 783 }
44
45
46
47DynamicTemplateName ::= TEXTUAL-CONVENTION
48    STATUS          current
49    DESCRIPTION
50        "A string-value that identifies a dynamic template.  The
51        semantics of the string-value are the same as those specified
52        by the SnmpAdminString textual convention defined by the
53        SNMP-FRAMEWORK-MIB [RFC3411]."
54
55    REFERENCE
56        "D. Harrington, R. Resuhn, B. Wijnen, 'An Architecture for
57        Describing Simple Network Management Protocol (SNMP)
58        Management
59        Frameworks', RFC-3411, December 2002."
60    SYNTAX          OCTET STRING (SIZE (1..64))
61
62DynamicTemplateType ::= TEXTUAL-CONVENTION
63    STATUS          current
64    DESCRIPTION
65        "An enumerated integer-value describing the type of dynamic
66        template:
67
68        'other'
69            The implementation of the MIB module using this textual
70            convention does not recognize the type of dynamic template.
71
72        'derived'
73            A configuration resulting from the union of the attributes
74            contained by all the dynamic templates associated with a
75            target.  The system generates a derived configuration, and
76            an EMS/NMS cannot directly modify it.  An EMS/NMS can only
77            affect a derived configuration by modifying one or more of
78            the dynamic templates associated with the target.
79
80        'ppp'
81            A PPP template is a set of locally-configured attributes
82            relating to the configuration of a PPP interface.
83
84        'ethernet'
85            An Ethernet template is a set of locally-configured
86            attributes used by the system to configure dynamic
87            interfaces initiated on Ethernet virtual interfaces (e.g.,
88            EoMPLS) or automatically created VLANs.
89
90        'ipSubscriber'
91            An IP subscriber template is a set of locally-configured
92            attributes used by the system to configure certain types of
93            IP and L2 subscriber sessions.
94
95        'service'
96            A service template is a set of locally-configured attributes
97            used by the system to configure subscriber sessions.  These
98            attributes specifically relate to services, and the system
99            applies these attributes in response to subscriber session
100            life-cycle events."
101    SYNTAX          INTEGER  {
102                        other(1),
103                        derived(2),
104                        ppp(3),
105                        ethernet(4),
106                        ipSubscriber(5),
107                        service(6)
108                    }
109
110DynamicTemplateTargetType ::= TEXTUAL-CONVENTION
111    STATUS          current
112    DESCRIPTION
113        "An enumerated integer-value describing the type of target
114        associated with one or more dynamic templates:
115
116            'other'
117                The implementation of the MIB module using this textual
118                convention does not recognize the type of target.
119
120            'interface'
121                The target is a physical, logical, or virtual interface
122                represented by an ifEntry (defined by the IF-MIB).
123
124        An implementation must ensure that DynamicTemplateTargetType
125        object and any associated DynamicTemplateTargetId objects are
126        consistent.  An attempt to set a DynamicTemplateTargetType
127        object to a value inconsistent with the associated
128        DynamicTemplateTargetId object must result in a response with
129        an
130        error-status of 'inconsistentValue'."
131
132    REFERENCE
133        "K. McCloghrie and F. Kastenholtz, 'The Interfaces Group
134        MIB',
135        RFC-2863, June 2000."
136    SYNTAX          INTEGER  {
137                        other(1),
138                        interface(2)
139                    }
140
141DynamicTemplateTargetId ::= TEXTUAL-CONVENTION
142    STATUS          current
143    DESCRIPTION
144        "An binary string-value in network byte order identifying a
145        target associated with one or more dynamic templates.
146
147        An implementation must interpret a DynamicTemplateTargetId
148        value
149        within the context of a DynamicTemplateTargetType.  Every usage
150        of the DynamicTemplateTargetId textual convention must have a
151        corresponding object specifying the DynamicTemplateType that
152        provides this context.  It is most appropriate that a MIB
153        module
154        logical registers the DynamicTemplateType object before the use
155        of the DynamicTemplateTargetId textual convention within the
156        same logical row.
157
158        The value of a DynamicTemplateTargetId object must always be
159        consistent with the value of the associated
160        DynamicTemplateTargetType object.  An attempt to set a
161        DynamicTemplateTargetId object to a value inconsistent with the
162        with the associated DynamicTemplateTargetType object must
163        result
164        in a response with an error-status of 'inconsistentValue'.
165
166        If the DynamicTemplateTargetType is 'interface', then the representation
167        of DynamicTemplateTargetId is as below
168
169        octets   contents              encoding
170         1-4     ifIndex               network-byte order"
171
172    REFERENCE
173        "K. McCloghrie and F. Kastenholtz, 'The Interfaces Group
174        MIB',
175        RFC-2863, June 2000."
176    SYNTAX          OCTET STRING (SIZE (1..20))
177
178END
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195