1-- *****************************************************************
2-- CISCO-WAN-SCT-MGMT-MIB.my
3--
4-- Cisco SCT Management MIB
5--
6-- Sept 2001, Muthumayan
7--
8-- Copyright (c) 2001 by Cisco Systems, Inc.
9-- All rights reserved.
10-- *****************************************************************
11--
12-- SCT, Service Class Template
13--
14--
15
16CISCO-WAN-SCT-MGMT-MIB DEFINITIONS ::= BEGIN
17
18IMPORTS
19        MODULE-IDENTITY,
20        OBJECT-TYPE,
21        Unsigned32
22                FROM SNMPv2-SMI
23        RowStatus
24                FROM SNMPv2-TC
25        MODULE-COMPLIANCE, OBJECT-GROUP
26                FROM SNMPv2-CONF
27        SnmpAdminString
28                FROM SNMP-FRAMEWORK-MIB
29        ciscoMgmt
30                FROM CISCO-SMI;
31
32ciscoWanSctMgmtMIB MODULE-IDENTITY
33	LAST-UPDATED    "200205210000Z"
34	ORGANIZATION    "Cisco Systems, Inc."
35	CONTACT-INFO
36	        "       Cisco Systems
37	                Customer Service
38
39	        Postal: 170 W Tasman Drive
40	                San Jose, CA  95134
41	                USA
42
43	                Tel: +1 800 553-NETS
44
45	        E-mail: cs-wanatm@cisco.com"
46
47        DESCRIPTION
48                "MIB module to manage SCT files in a node.
49
50                 SCTs (Service Class Templates) are nodal configuration files,
51                 which define the traffic characteristics of a switch based on
52                 class of service queues.
53
54                 There is a unique SCT file for every combination of card type,
55                 SCT type, SCT Id and major SCT version. For instance, the file
56                 AXSM_PORT_SCT.4.V2 refers to a SCT for the card type AXSM, port
57                 type SCT, SCT id 4 and a major version of 2.
58
59                 SCTs are transfered to a node using FTP by NMS.
60
61                 The NMS adds, deletes, discovers and monitors SCT files in a
62                 node using this MIB."
63
64        REVISION "200205210000Z"
65        DESCRIPTION
66                "1. Added ATM Service Module(axsmxg) to cwSctCardType.
67                 2. Imported Unsigned32 from SNMPv2-SMI instead
68                    of CISCO-TC."
69
70        REVISION "200111180000Z"
71        DESCRIPTION
72                 "Changed SYNTAX clause of cwSctFileMinorVersion from
73                  (1..65535) to (0..65535)."
74
75        REVISION "200109170000Z"
76        DESCRIPTION
77                 "Initial version of the MIB."
78        ::= { ciscoMgmt 236 }
79
80ciscoWanSctMgmtMIBObjects OBJECT IDENTIFIER ::=  { ciscoWanSctMgmtMIB 1 }
81
82
83--------------------------------------------------------------------
84--
85--         SCT File Management Table
86--
87-- -----------------------------------------------------------------
88
89cwSctFileMgmtTable OBJECT-TYPE
90        SYNTAX     SEQUENCE OF CwSctFileMgmtEntry
91        MAX-ACCESS not-accessible
92        STATUS     current
93        DESCRIPTION
94               "This MIB defines a SCT file management table in which each row
95                corresponds to a unique SCT file.
96
97                When the NMS needs to add a SCT to a node, it transfers the SCT
98                file to a transient storage area on the node. The NMS then
99                performs a SET operation requesting the agent to accept the
100                transferred file. The agent validates the integrity of the
101                file and if valid, transfers the file to a secure area. It
102                would then create a new row in the SCT file management table. This
103                newly added row is then advertised to all NMS in the network using
104                appropriate traps (refer CISCO-WAN-SCT-MGMT-TRAPS-MIB).
105
106                Once a row is created, the agent keeps track of the operational
107                status of the corresponding SCT file. The NMS can query the status
108                of a SCT file by performing a GET operation on the row.
109
110                The NMS can delete a SCT file and its corresponding row in the SCT
111                file management table by performing a SET operation with the
112                appropriate RowStatus. The agent, upon successful deletion
113                of the row would advertise this configuration change to all the
114                NMS using appropriate traps.
115
116                The NMS could also perform a GETNEXT operation to discover all the
117                configured SCTs on a node."
118        ::= { ciscoWanSctMgmtMIBObjects 1 }
119
120cwSctFileMgmtEntry OBJECT-TYPE
121        SYNTAX     CwSctFileMgmtEntry
122        MAX-ACCESS not-accessible
123        STATUS     current
124        DESCRIPTION
125               "An entry in the SCT file Management Table. This represents a
126                unique SCT file in the node. Each entry contains the configuration
127                and status information of a specific SCT in the node."
128        INDEX  { cwSctCardType, cwSctType, cwSctId, cwSctMajorVersion }
129        ::= { cwSctFileMgmtTable 1 }
130
131CwSctFileMgmtEntry ::= SEQUENCE  {
132        cwSctCardType                    INTEGER,
133        cwSctType                        INTEGER,
134        cwSctId                          Unsigned32,
135        cwSctMajorVersion                Unsigned32,
136        cwSctFileName                    SnmpAdminString,
137        cwSctFileMinorVersion            Unsigned32,
138        cwSctFileChecksum                Unsigned32,
139        cwSctFileDescription             SnmpAdminString,
140        cwSctFileOperStatus              INTEGER,
141        cwSctFileRowStatus               RowStatus
142        }
143
144cwSctCardType      OBJECT-TYPE
145        SYNTAX     INTEGER {
146                   axsm   (1),
147                   axsme  (2),
148                   pxm1e  (3),
149                   hsfr   (4),
150                   axsmxg (5)
151                  }
152        MAX-ACCESS not-accessible
153        STATUS     current
154        DESCRIPTION
155                "This represents service modules in a node that require the
156                 use of a SCT. The content of the SCT varies depending on the
157                 specific hardware used. Hence there is a different SCT for
158                 every type of card. The card types that support SCTs are
159                 listed in the SYNTAX clause"
160        ::= { cwSctFileMgmtEntry 1 }
161
162cwSctType          OBJECT-TYPE
163        SYNTAX     INTEGER {
164                   portSct  (1),
165                   cardSct  (2)
166                   }
167        MAX-ACCESS not-accessible
168        STATUS     current
169        DESCRIPTION
170                "There are several types of SCTs. The portSct (1) specifies
171                 traffic parameters that are applicable to a logical port
172                 within a card. The cardSct (2) specifies traffic parameters
173                 that are applicable to the whole card."
174        ::= { cwSctFileMgmtEntry 2 }
175
176cwSctId            OBJECT-TYPE
177        SYNTAX     Unsigned32 (1..65535)
178        MAX-ACCESS not-accessible
179        STATUS     current
180        DESCRIPTION
181                "Each logical port on a service module could need different
182                 'class of service' characteristics. This can be achieved by
183                 applying different SCTs on different ports. Thus for a given
184                 card type, there could be multiple SCTs of different IDs."
185        ::= { cwSctFileMgmtEntry 3 }
186
187cwSctMajorVersion  OBJECT-TYPE
188        SYNTAX     Unsigned32 (1..65535)
189        MAX-ACCESS not-accessible
190        STATUS     current
191        DESCRIPTION
192                "The SCT file consists of several tables. The number of
193                 tables depend on the service module card type. Both the
194                 contents and the row/column size of a table are subject
195                 to change. The major version is incremented by the manager
196                 whenever there is a change in the row/column size of the
197                 table."
198        ::= { cwSctFileMgmtEntry 4 }
199
200cwSctFileName OBJECT-TYPE
201        SYNTAX     SnmpAdminString (SIZE (0..132))
202        MAX-ACCESS read-only
203        STATUS     current
204        DESCRIPTION
205                "This object specifies the absolute path name of the file
206                 corresponding to the SCT indices.
207
208                 After the agent accepts a SET operation and creates a new
209                 row in the SCT file management table, it transfers the file
210                 from the transient storage area to a secure location on the
211                 disk. This object identifies the absolute path name of the
212                 secure location on disk.
213
214                 The file name would be in the format:
215                 <CardType>_SCT.<SCTType>.<SCTId>.V<Major version>
216                "
217        ::= { cwSctFileMgmtEntry 5 }
218
219cwSctFileMinorVersion OBJECT-TYPE
220        SYNTAX     Unsigned32 (0..65535)
221        MAX-ACCESS read-only
222        STATUS     current
223        DESCRIPTION
224                "The SCT file consists of several tables. The number of
225                 tables depend on the service module card type. Both the
226                 contents and the row/column size of a table are subject
227                 to change. The minor version is incremented by the manager
228                 whenever there is a change in contents of the table."
229        ::= { cwSctFileMgmtEntry 6 }
230
231cwSctFileChecksum  OBJECT-TYPE
232        SYNTAX     Unsigned32
233        MAX-ACCESS read-create
234        STATUS     current
235        DESCRIPTION
236                "The manager specifies this checksum when trying to add
237                 a SCT on the node. The agent while acting on the SET
238                 operation would perform a checksum computation on the
239                 FTPed file and compare against this object. If they differ,
240                 the SET operation would be negated. If same, the file is
241                 considered valid and this value is stored in a persistent
242                 database. SCT files across the network with the same
243                 combination of card type, sct type, major and minor versions
244                 would have the same checksum."
245        ::= { cwSctFileMgmtEntry 7 }
246
247cwSctFileDescription OBJECT-TYPE
248        SYNTAX     SnmpAdminString (SIZE (0..132))
249        MAX-ACCESS read-create
250        STATUS     current
251        DESCRIPTION
252	       "A description string can be associated with a specific SCT
253                index and in turn the SCT file. This may be used for
254                associating customized filenames."
255        ::= { cwSctFileMgmtEntry 8 }
256
257cwSctFileOperStatus OBJECT-TYPE
258        SYNTAX     INTEGER {
259                       valid   (1),
260                       invalid (2),
261                       absent  (3)
262                   }
263        MAX-ACCESS read-only
264        STATUS     current
265        DESCRIPTION
266                "Reflects the operational status of the SCT file.
267
268                 The agent sets the value to valid(1) if the computed checksum
269                 of the SCT file matches the provisioned checksum.
270
271                 The agent sets the value to invalid(2) if the computed checksum
272                 of the SCT file mismatches with the provisioned checksum. This
273                 usually suggests a corrupted SCT file.
274
275                 The agent sets the value to absent(3) if the file is missing in
276                 the secure area of the disk, while a row exists in the SCT file
277                 management table."
278        ::= { cwSctFileMgmtEntry 9 }
279
280cwSctFileRowStatus OBJECT-TYPE
281        SYNTAX     RowStatus
282        MAX-ACCESS read-create
283        STATUS     current
284        DESCRIPTION
285                  "
286                   * To create a row, the manager needs to perform a SET
287                     operations with a 'CreateAndGo' option. The agent would
288                     validate the file specified by the indices if found valid
289                     would create a new row.
290
291                   * SET operation with 'CreateAndWait' option will be
292                     rejected by the agent.
293
294                   * SET operations with 'active' option would be treated as
295                     a modify operation. The only objects that can be modified
296                     in a row are the cwSctFileDescription and the
297                     cwSctFileMinorVersion.
298
299                   * SET operation with a 'Destroy' option would be used for
300                     deleting a row in the cwSctFileMgmtTable and its
301                     associated SCT file in the switch.
302
303                   * The GET status of this object would always return 'active'.
304                  "
305        ::= { cwSctFileMgmtEntry 10 }
306
307
308-- conformance information
309
310ciscoWanSctMgmtMIBConformance OBJECT IDENTIFIER ::= { ciscoWanSctMgmtMIB 3 }
311ciscoWanSctMgmtMIBCompliances OBJECT IDENTIFIER ::=
312                                    { ciscoWanSctMgmtMIBConformance 1 }
313ciscoWanSctMgmtMIBGroups            OBJECT IDENTIFIER ::=
314                                    { ciscoWanSctMgmtMIBConformance 2 }
315
316cwSctFileMgmtMIBCompliance MODULE-COMPLIANCE
317        STATUS current
318        DESCRIPTION
319            "The compliance statement for Cisco SCT file management group."
320        MODULE -- this module
321        MANDATORY-GROUPS { cwSctFileMgmtObjectGroup }
322        ::= { ciscoWanSctMgmtMIBCompliances 1 }
323
324-- units of conformance
325
326cwSctFileMgmtObjectGroup  OBJECT-GROUP
327        OBJECTS {
328            cwSctFileName,
329            cwSctFileMinorVersion,
330            cwSctFileChecksum,
331            cwSctFileDescription,
332            cwSctFileOperStatus,
333            cwSctFileRowStatus
334       }
335       STATUS current
336       DESCRIPTION
337         "Objects used for SCT file management."
338       ::= { ciscoWanSctMgmtMIBGroups 1 }
339
340END
341
342
343
344