Debian Codegraph @

rfc1695.html

raw
1 <pre>Network Working Group M. Ahmed
2 Request for Comments: 1695 K. Tesink
3 Category: Standards Track Editors
4 Bell Communications Research
5 August 1994
6
7
8 <span class="h1">Definitions of Managed Objects</span>
9 <span class="h1">for ATM Management Version 8.0</span>
10 <span class="h1">using SMIv2</span>
11
12 Status of this Memo
13
14 This document specifies an Internet standards track protocol for the
15 Internet community, and requests discussion and suggestions for
16 improvements. Please refer to the current edition of the "Internet
17 Official Protocol Standards" (STD 1) for the standardization state
18 and status of this protocol. Distribution of this memo is unlimited.
19
20 Table of Contents
21
22 <a href="#section-1">1</a>. Introduction ............................................. <a href="#page-2">2</a>
23 <a href="#section-2">2</a>. The SNMPv2 Network Management Framework .................. <a href="#page-2">2</a>
24 <a href="#section-3">3</a>. Object Definitions ....................................... <a href="#page-2">2</a>
25 <a href="#section-4">4</a>. ATM Terminology .......................................... <a href="#page-3">3</a>
26 <a href="#section-4.1">4.1</a> VCL/VPL and VCC/VPC ..................................... <a href="#page-3">3</a>
27 <a href="#section-4.2">4.2</a> PVC and SVC ............................................. <a href="#page-5">5</a>
28 <a href="#section-4.3">4.3</a> Traffic Management Parameters ........................... <a href="#page-5">5</a>
29 <a href="#section-4.3.1">4.3.1</a> Traffic Policing and Traffic Shaping Parameters ...... <a href="#page-5">5</a>
30 <a href="#section-4.3.2">4.3.2</a> Cell Loss Priority .................................... <a href="#page-6">6</a>
31 <a href="#section-4.3.3">4.3.3</a> QoS Class ............................................. <a href="#page-6">6</a>
32 <a href="#section-5">5</a>. Overview ................................................. <a href="#page-7">7</a>
33 <a href="#section-5.1">5.1</a> Background .............................................. <a href="#page-7">7</a>
34 <a href="#section-5.2">5.2</a> Structure of the MIB .................................... <a href="#page-7">7</a>
35 <a href="#section-5.3">5.3</a> ATM Interface Configuration Group ....................... <a href="#page-7">7</a>
36 <a href="#section-5.4">5.4</a> ATM Interface DS3 PLCP and TC Layer Groups .............. <a href="#page-8">8</a>
37 <a href="#section-5.5">5.5</a> ATM Virtual Link and Cross-Connect Groups ............... <a href="#page-8">8</a>
38 <a href="#section-6">6</a>. Application of MIB II to ATM ............................. <a href="#page-8">8</a>
39 <a href="#section-6.1">6.1</a> The System Group ........................................ <a href="#page-8">8</a>
40 <a href="#section-6.2">6.2</a> The Interface Group ..................................... <a href="#page-8">8</a>
41 <a href="#section-6.2.1">6.2.1</a> Support of the ATM Cell Layer by ifTable .............. <a href="#page-9">9</a>
42 <a href="#section-7">7</a>. Support of the AAL3/4 Based Interfaces ................... <a href="#page-10">10</a>
43 <a href="#section-8">8</a>. Support of the AAL5 Managed Objects ...................... <a href="#page-10">10</a>
44 <a href="#section-8.1">8.1</a> Managing AAL5 in a Switch ............................... <a href="#page-11">11</a>
45 <a href="#section-8.2">8.2</a> Managing AAL5 in a Host ................................. <a href="#page-12">12</a>
46 <a href="#section-8.3">8.3</a> Support of AAL5 by ifTable .............................. <a href="#page-13">13</a>
47 <a href="#section-8.4">8.4</a> Support of Proprietary Virtual Interface by ifT-able .. <a href="#page-14">14</a>
48 <a href="#section-8.5">8.5</a> AAL5 Connection Performance Statistics Group ............ <a href="#page-15">15</a>
49
50
51
52 <span class="grey">Ahmed &amp; Tesink [Page 1]</span></pre>
53 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span>
54 <span class="grey"><a href="./rfc1695">RFC 1695</a> ATM Management Objects August 1994</span>
55
56
57 <a href="#section-9">9</a>. ILMI MIB and the ATM Managed Objects ..................... <a href="#page-15">15</a>
58 <a href="#section-10">10</a>. Definitions ............................................. <a href="#page-18">18</a>
59 <a href="#section-11">11</a>. Acknowledgments ......................................... <a href="#page-72">72</a>
60 <a href="#section-12">12</a>. References .............................................. <a href="#page-72">72</a>
61 <a href="#section-13">13</a>. Security Considerations ................................. <a href="#page-73">73</a>
62 <a href="#section-14">14</a>. Authors' Addresses ...................................... <a href="#page-73">73</a>
63
64 <span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span>
65
66 This memo defines a portion of the Management Information Base (MIB)
67 for use with network management protocols in the Internet community.
68 In particular, it describes objects used for managing ATM-based
69 interfaces, devices, networks and services.
70
71 This memo specifies a MIB module in a manner that is both compliant
72 to the SNMPv2 SMI, and semantically identical to the peer SNMPv1
73 definitions.
74
75 <span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. The SNMPv2 Network Management Framework</span>
76
77 The SNMPv2 Network Management Framework consists of four major
78 components. They are:
79
80 0 <a href="./rfc1442">RFC 1442</a> [<a href="#ref-1" title="&quot;Structure of Management Information for version 2 of the Simple Network Management Protocol (SNMPv2)&quot;">1</a>] which defines the SMI, the mechanisms used
81 for describing and naming objects for the purpose of
82 management.
83
84 0 STD 17, <a href="./rfc1213">RFC 1213</a> [<a href="#ref-2" title="&quot;Management Information Base for Network Management of TCP/IP-based internets: MIB-II&quot;">2</a>] defines MIB-II, the core set of
85 managed objects for the Internet suite of protocols.
86
87 0 <a href="./rfc1445">RFC 1445</a> [<a href="#ref-3" title="&quot;Administrative Model for version 2 of the Simple Network Management Protocol (SNMPv2)&quot;">3</a>] which defines the administrative and other
88 architectural aspects of the framework.
89
90 0 <a href="./rfc1448">RFC 1448</a> [<a href="#ref-4" title="&quot;Protocol Operations for version 2 of the Simple Network Management Protocol (SNMPv2)&quot;">4</a>] which defines the protocol used for network
91 access to managed objects.
92
93 The Framework permits new objects to be defined for the purpose of
94 experimentation and evaluation.
95
96 <span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. Object Definitions</span>
97
98 Managed objects are accessed via a virtual information store, termed
99 the Management Information Base or MIB. Objects in the MIB are
100 defined using the subset of Abstract Syntax Notation One (ASN.1)
101 defined in the SMI. In particular, each object type is named by an
102 OBJECT IDENTIFIER, an administratively assigned name. The object
103 type together with an object instance serves to uniquely identify a
104 specific instantiation of the object. For human convenience, we
105
106
107
108 <span class="grey">Ahmed &amp; Tesink [Page 2]</span></pre>
109 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span>
110 <span class="grey"><a href="./rfc1695">RFC 1695</a> ATM Management Objects August 1994</span>
111
112
113 often use a textual string, termed the descriptor, to also refer to
114 the object type.
115
116 <span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. ATM Terminology</span>
117
118 Some basic ATM terminologies are described in this section to
119 facilitate defining the ATM managed objects.
120
121 <span class="h3"><a class="selflink" id="section-4.1" href="#section-4.1">4.1</a>. VCL/VPL and VCC/VPC</span>
122
123 There are two distinct types of ATM virtual connections: Virtual
124 Channel Connections (VCCs) and Virtual Path Connection (VPCs). As
125 shown in Figures 1 and 2, ATM virtual connections consist of
126 concatenated series of virtual links which forms a path between two
127 end points, with each concatenation occurring at an ATM switch.
128 Virtual links of VCCs are called Virtual Channel Links (VCLs).
129 Virtual links of VPCs are called Virtual Path Links (VPLs). The VCI
130 and VPI fields in the ATM cell header associate each cell of a VCC
131 with a particular VCL over a given physical link. The VPI field in
132 the ATM cell header associates each cell of a VPC with a particular
133 VPL over a given physical link. Switches route cells between VCLs
134 (or VPLs) via a cross-connect function according to the cells'
135 VCI/VPI (or VPI) values.
136
137 &lt;-----------------------VCC--------------------------&gt;
138 ------------ -----------
139 |ATM | |ATM |
140 |X-Connect | |X-Connect |
141 VCL1 |Point | VCL2 |Point | VCL3
142 O---------|----X-----|-------|-----|----X-----|-------O
143 | | | |
144 ------------ ------------
145 ATM Switch ATM Switch
146
147
148 Figure 1: Virtual Channel Links and
149 Virtual Channel Connection
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164 <span class="grey">Ahmed &amp; Tesink [Page 3]</span></pre>
165 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span>
166 <span class="grey"><a href="./rfc1695">RFC 1695</a> ATM Management Objects August 1994</span>
167
168
169 &lt;-----------------------VPC--------------------------&gt;
170 ------------ -----------
171 |ATM | |ATM |
172 |X-Connect | |X-Connect |
173 VPL1 |Point | VPL2 |Point | VPL3
174 O---------|----X-----|-------|-----|----X-----|-------O
175 | | | |
176 ------------ ------------
177 ATM Switch ATM Switch
178
179
180 Figure 2: Virtual Path Links and
181 Virtual Path Connection
182
183 A single ATM end-system or switch does not support the whole end-to-
184 end span of a VCC (or VPC). Rather, multiple ATM end- systems and/or
185 switches each support one piece of the VCC (or VPC). That is, each
186 ATM end-system at one end of the VCC/VPC supports its end of the
187 VCC/VPC plus the VCLs or VPLs on its external interfaces, and each
188 switch through which the VCC/VPC passes, supports the multiple
189 VCLs/VPLs on that switch's external interfaces and the cross-
190 connection of those VCLs/VPLs through that switch. Thus, the end-
191 to-end management of a VCC or VPC is achieved only by appropriate
192 management of its individual pieces in combination.
193
194 Note that for management purposes, an ATM network may be viewed as a
195 large distributed switch by hiding all the network's internal
196 connectivity as being internal to the distributed switch (as shown in
197 Figure 2a). This model may for example be used for Customer Network
198 Management (CNM) purposes.
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220 <span class="grey">Ahmed &amp; Tesink [Page 4]</span></pre>
221 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span>
222 <span class="grey"><a href="./rfc1695">RFC 1695</a> ATM Management Objects August 1994</span>
223
224
225 &lt;---------------------VCC---------------------------&gt;
226 --------------------------------------
227 | |
228 | ---------- ---------- |
229 | | ATM | | ATM | |
230 VCL1 | | Switch | | Switch | | VCL3
231 O-------|-|--------|------/-------|--------|-|------O
232 | | | | | |
233 | ---------- ---------- |
234 | |
235 | ATM Network |
236 --------------------------------------
237
238
239
240 Figure 2a: ATM Network modeled as a large distributed
241 switch
242
243 A VCC has a set of traffic characteristics (i.e., bandwidth
244 parameters, QoS Class parameters, etc.). VCLs inherit their traffic
245 characteristics from the VCC of which they are a part. VCCs are bi-
246 directional by definition. However, the traffic parameters in the
247 two directions of a connection can be symmetric or asymmetric, i.e.,
248 the two directions can have the same or different traffic flows. A
249 uni-directional traffic flow across a VCC is achieved by assigning a
250 zero bandwidth in one direction. Note that in addition to the
251 bandwidth required by the user traffic flow, bandwidth is also
252 required for OAM cell flows, even for the zero-bandwidth direction of
253 a uni-directional connection. These same principles apply to VPCs.
254
255 <span class="h3"><a class="selflink" id="section-4.2" href="#section-4.2">4.2</a>. PVC and SVC</span>
256
257 A Permanent Virtual Connection (PVC) is a provisioned VCC or VPC. A
258 Switched Virtual Connection (SVC) is a switched VCC or VPC that is
259 set up in real-time via call set-up signaling procedures. A PVC (or
260 an SVC) can be a point-to-point, point-to-multipoint, or multipoint-
261 to-multipoint VCC or VPC.
262
263 <span class="h3"><a class="selflink" id="section-4.3" href="#section-4.3">4.3</a>. Traffic Management Parameters</span>
264
265 <span class="h4"><a class="selflink" id="section-4.3.1" href="#section-4.3.1">4.3.1</a>. Traffic Policing and Traffic Shaping Parameters</span>
266
267 In order to allocate resources fairly among different users, some
268 networks police traffic at resource access points. The traffic
269 enforcement or policing taken at a UNI is called Usage Parameter
270 Control (UPC) and is activated on an incoming VCL or VPL as shown in
271 Figure 3. The use of the traffic enforcer at the ingress of the
272 connection is to make sure that the user traffic does not exceed the
273
274
275
276 <span class="grey">Ahmed &amp; Tesink [Page 5]</span></pre>
277 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span>
278 <span class="grey"><a href="./rfc1695">RFC 1695</a> ATM Management Objects August 1994</span>
279
280
281 negotiated traffic parameters such as the peak cell rate associated
282 with a specific traffic descriptor type.
283
284
285 ---------- ----------
286 UNI | ATM | NNI | ATM | UNI
287 | | switch | | | switch | |
288 O&lt;---|----&gt;X(UPC) |&lt;----|------&gt;| (UPC)X&lt;-----|---&gt;O
289 | VCL | | | VCL | | VCL |
290 ---------- ----------
291
292
293 Figure 3: An Example of a UPC
294
295 In addition, traffic shaping may be performed on an outgoing VPL or
296 VCL at a given ATM interface. The function of the ATM traffic shaper
297 either at the source or an egress point of the connection is to
298 smooth the outgoing cell traffic inter-arrival time. If policing or
299 shaping is not performed then the policing or shaping algorithm is
300 not activated. ATM Forum has specified seven traffic descriptor
301 types including one for the best effort traffic [<a href="#ref-9" title="&quot;ATM Forum UNI Specification, Version 3.0&quot;">9</a>].
302
303 <span class="h4"><a class="selflink" id="section-4.3.2" href="#section-4.3.2">4.3.2</a>. Cell Loss Priority</span>
304
305 To prioritize traffic during resource congestion, ATM cells are
306 assigned one of the two types of Cell Loss Priority (CLP), CLP=0 and
307 CLP=1. ATM cells with CLP=0 have a higher priority in regard to cell
308 loss than ATM cells with CLP=1. Therefore, during resource
309 congestions, CLP=1 cells are dropped before any CLP=0 cell is
310 dropped.
311
312 <span class="h4"><a class="selflink" id="section-4.3.3" href="#section-4.3.3">4.3.3</a>. QoS Class</span>
313
314 A VCC or VPC is associated with one of a number of Quality of Service
315 (QoS) classes. The following service classes have been specified:
316
317 Service Class A: Constant bit rate video and Circuit
318 emulation
319 Service Class B: Variable bit rate video/audio
320 Service Class C: Connection-oriented data
321 Service Class D: Connectionless data
322
323 Four QoS classes numbered 1, 2, 3, and 4 have been specified with the
324 aim of supporting service classes A, B, C, and D respectively. The
325 VCLs (or VPLs) concatenated to form a VCC (or VPC) will all have the
326 same QoS class as that of the VCC (or VPC). The Cell Loss Ratio
327 (CLR), Cell Delay Variation (CDV), and end-to-end Cell Delay (CD)
328 parameters are defined as part of QoS Class definition. In addition,
329
330
331
332 <span class="grey">Ahmed &amp; Tesink [Page 6]</span></pre>
333 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span>
334 <span class="grey"><a href="./rfc1695">RFC 1695</a> ATM Management Objects August 1994</span>
335
336
337 an unspecified QoS Class numbered 0 is specified for best effort
338 traffic.
339
340 <span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. Overview</span>
341
342 ATM management objects are used to manage ATM interfaces, ATM virtual
343 links, ATM cross-connects, AAL5 entities and AAL5 connections
344 supported by ATM hosts, ATM switches and ATM networks. This section
345 provides an overview and background of how to use this MIB and other
346 potential MIBs for this purpose.
347
348 The purpose of this memo is primarily to manage ATM PVCs. ATM SVCs
349 are also represented by the management information in this MIB.
350 However, full management of SVCs may require additional capabilities
351 which are beyond the scope of this memo.
352
353 <span class="h3"><a class="selflink" id="section-5.1" href="#section-5.1">5.1</a>. Background</span>
354
355 In addition to the MIB module defined in this memo, other MIB modules
356 are necessary to manage ATM interfaces, links and cross-connects.
357 Examples include MIB II for general system and interface management
358 (<a href="./rfc1213">RFC 1213</a> and <a href="./rfc1573">RFC 1573</a>), the DS3 or SONET MIBs for management of
359 physical interfaces, and, as appropriate, MIB modules for
360 applications that make use of ATM, such as SMDS. These MIB modules
361 are outside the scope of this specification.
362
363 The current specification of this ATM MIB is based on SNMPv2.
364
365 <span class="h3"><a class="selflink" id="section-5.2" href="#section-5.2">5.2</a>. Structure of the MIB</span>
366
367 The managed ATM objects are arranged into the following groups:
368
369 (1) ATM interface configuration group
370 (2) ATM interface DS3 PLCP group
371 (3) ATM interface TC Sublayer group
372 (4) ATM interface virtual link (VPL/VCL) configuration
373 groups
374 (5) ATM VP/VC cross-connect groups
375 (6) AAL5 connection performance statistics group
376
377 Note that, managed objects for activation/deactivation of OAM cell
378 flows and ATM traps notifying virtual connection or virtual link
379 failures are outside the scope of this memo.
380
381 <span class="h3"><a class="selflink" id="section-5.3" href="#section-5.3">5.3</a>. ATM Interface Configuration Group</span>
382
383 This group contains information on ATM cell layer configuration of
384 local ATM interfaces on an ATM device in addition to the information
385
386
387
388 <span class="grey">Ahmed &amp; Tesink [Page 7]</span></pre>
389 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-8" ></span>
390 <span class="grey"><a href="./rfc1695">RFC 1695</a> ATM Management Objects August 1994</span>
391
392
393 on such interfaces contained in the ifTable.
394
395 <span class="h3"><a class="selflink" id="section-5.4" href="#section-5.4">5.4</a>. ATM Interface DS3 PLCP and TC Layer Groups</span>
396
397 These groups provide performance statistics of the DS3 PLCP and TC
398 sublayer of local ATM interfaces on a managed ATM device. DS3 PLCP
399 and TC sublayer are currently used to carry ATM cells respectively
400 over DS3 and SONET transmission paths.
401
402 <span class="h3"><a class="selflink" id="section-5.5" href="#section-5.5">5.5</a>. ATM Virtual Link and Cross-Connect Groups</span>
403
404 ATM virtual link and cross-connect groups model bi-directional ATM
405 virtual links and ATM cross-connects. The ATM VP/VC link groups are
406 implemented in an ATM host, ATM switch and ATM network. The ATM
407 switch and ATM network also implement the ATM VP/VC cross-connect
408 groups. Both link and cross-connect groups are implemented in a
409 carrier's network for Customer Network Management (CNM) purposes.
410
411 The ATM virtual link groups are used to create, delete or modify ATM
412 virtual links in an ATM host, ATM switch and ATM network. ATM
413 virtual link groups along with the cross-connect groups are used to
414 create, delete or modify ATM cross-connects in an ATM switch or ATM
415 network (e.g., for CNM purposes).
416
417 <span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. Application of MIB II to ATM</span>
418
419 <span class="h3"><a class="selflink" id="section-6.1" href="#section-6.1">6.1</a>. The System Group</span>
420
421 For the purposes of the sysServices object in the System Group of MIB
422 II [<a href="#ref-2" title="&quot;Management Information Base for Network Management of TCP/IP-based internets: MIB-II&quot;">2</a>], ATM is a data link layer protocol. Thus, for ATM switches
423 and ATM networks, sysServices will have the value "2".
424
425 <span class="h3"><a class="selflink" id="section-6.2" href="#section-6.2">6.2</a>. The Interface Group</span>
426
427 The Interfaces Group of MIB II defines generic managed objects for
428 managing interfaces. This memo contains the media-specific
429 extensions to the Interfaces Group for managing ATM interfaces.
430
431 This memo assumes the interpretation of the Interfaces Group to be in
432 accordance with [<a href="#ref-5" title="&quot;Evolution of the Interfaces Group of MIB-II&quot;">5</a>] which states that the interfaces table (ifTable)
433 contains information on the managed resource's interfaces and that
434 each sub-layer below the internetwork layer of a network interface is
435 considered an interface. Thus, the ATM cell layer interface is
436 represented as an entry in the ifTable. This entry is concerned with
437 the ATM cell layer as a whole, and not with individual virtual
438 connections which are managed via the ATM-specific managed objects
439 specified in this memo. The inter-relation of entries in the ifTable
440 is defined by Interfaces Stack Group defined in [<a href="#ref-5" title="&quot;Evolution of the Interfaces Group of MIB-II&quot;">5</a>].
441
442
443
444 <span class="grey">Ahmed &amp; Tesink [Page 8]</span></pre>
445 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-9" ></span>
446 <span class="grey"><a href="./rfc1695">RFC 1695</a> ATM Management Objects August 1994</span>
447
448
449 <span class="h4"><a class="selflink" id="section-6.2.1" href="#section-6.2.1">6.2.1</a>. Support of the ATM Cell Layer by ifTable</span>
450
451 Some specific interpretations of ifTable for the ATM cell layer
452 follow.
453
454 Object Use for the generic ATM layer
455 ====== =============================
456
457 ifIndex Each ATM port is represented by an ifEntry.
458
459 ifDescr Description of the ATM interface.
460
461 ifType The value that is allocated for ATM is 37.
462
463 ifSpeed The total bandwidth in bits per second
464 for use by the ATM layer.
465
466 ifPhysAddress The interface's address at the ATM protocol
467 sublayer; the ATM address which would be used
468 as the value of the Called Party Address
469 Information Element (IE) of a signalling
470 message for a connection which either:
471 - would terminate at this interface, or
472 - for which the Called Party Address IE
473 would need to be replaced by the Called
474 Party SubAddress IE before the message
475 was forwarded to any other interface.
476 For an interface on which signalling is
477 not supported, then the interface does not
478 necessarily have an address, but if it
479 does, then ifPhysAddress is the address which
480 would be used as above in the event that
481 signalling were supported. If the interface
482 has multiple such addresses, then ifPhysAddress
483 is its primary address. If the interface has
484 no addresses, then ifPhysAddress is an octet
485 string of zero length. Address encoding is as
486 per [<a href="#ref-9" title="&quot;ATM Forum UNI Specification, Version 3.0&quot;">9</a>]. Note that addresses assigned for
487 purposes other than those listed above (e.g.,
488 an address associated with the service provider
489 side of a public network UNI) may be represented
490 through atmInterfaceAdminAddress.
491
492 ifAdminStatus See [<a href="#ref-5" title="&quot;Evolution of the Interfaces Group of MIB-II&quot;">5</a>].
493
494 ifOperStatus Assumes the value down(2) if the ATM cell
495 layer or any layer below that layer is down.
496
497
498
499
500 <span class="grey">Ahmed &amp; Tesink [Page 9]</span></pre>
501 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-10" ></span>
502 <span class="grey"><a href="./rfc1695">RFC 1695</a> ATM Management Objects August 1994</span>
503
504
505 ifLastChange See [<a href="#ref-5" title="&quot;Evolution of the Interfaces Group of MIB-II&quot;">5</a>].
506
507 ifInOctets The number of received octets over the
508 interface, i.e., the number of received,
509 assigned cells multiplied by 53.
510
511 ifOutOctets The number of transmitted octets over the
512 interface, i.e., the number of transmitted,
513 assigned cells multiplied by 53.
514
515 ifInErrors The number of cells dropped due to
516 uncorrectable HEC errors.
517
518 ifInUnknownProtos The number of received cells discarded
519 during cell header validation, including
520 cells with unrecognized VPI/VCI values,
521 and cells with invalid cell header patterns.
522 If cells with undefined PTI values are discarded,
523 they are also counted here.
524
525 ifOutErrors See [<a href="#ref-5" title="&quot;Evolution of the Interfaces Group of MIB-II&quot;">5</a>].
526
527 ifName Textual name (unique on this system) of the
528 interface or an octet string of zero length.
529
530 ifLinkUpDownTrapEnable Default is disabled (2).
531
532 ifConnectorPresent Set to false (2).
533
534 ifPromiscuousMode Set to false(2).
535
536 ifHighSpeed See [<a href="#ref-5" title="&quot;Evolution of the Interfaces Group of MIB-II&quot;">5</a>].
537
538 ifHCInOctets The 64-bit version of ifInOctets; supported
539 if required by the compliance statements in [<a href="#ref-5" title="&quot;Evolution of the Interfaces Group of MIB-II&quot;">5</a>].
540
541 ifHCOutOctets The 64-bit version of ifOutOctets; supported
542 if required by the compliance statements in [<a href="#ref-5" title="&quot;Evolution of the Interfaces Group of MIB-II&quot;">5</a>].
543
544 <span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. Support of the AAL3/4 Based Interfaces</span>
545
546 For the management of AAL3/4 CPCS layer, see [<a href="#ref-6" title="&quot;Definitions of Managed Objects for SMDS Interfaces&quot;">6</a>].
547
548 <span class="h2"><a class="selflink" id="section-8" href="#section-8">8</a>. Support of the AAL5 Managed Objects</span>
549
550 Support of AAL5 managed objects in an ATM switch and ATM host are
551 described below.
552
553
554
555
556 <span class="grey">Ahmed &amp; Tesink [Page 10]</span></pre>
557 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-11" ></span>
558 <span class="grey"><a href="./rfc1695">RFC 1695</a> ATM Management Objects August 1994</span>
559
560
561 <span class="h3"><a class="selflink" id="section-8.1" href="#section-8.1">8.1</a>. Managing AAL5 in a Switch</span>
562
563 Managing AAL5 in a switch involves:
564
565 (1) performance management of an AAL5 entity as
566 an internal resource in a switch
567
568 (2) performance management of AAL5 per virtual connection
569
570 AAL5 in a switch is modeled as shown in Figures 4 and 5. AAL5 will
571 be managed in a switch for only those virtual connections that carry
572 AAL5 and are terminated at the AAL5 entity in the switch. Note that,
573 the virtual channels within the ATM UNIs carrying AAL5 will be
574 switched by the ATM switching fabric (termed as ATM Entity in the
575 figure) to the virtual channels on a proprietary internal interface
576 associated with the AAL5 process (termed as AAL5 Entity in the
577 figure). Therefore, performance management of the AAL5 resource in
578 the switch will be modeled using the ifTable through an internal
579 (pseudo-ATM) virtual interface and the AAL5 performance management
580 per virtual connection will be supported using an additional AAL5
581 connection table in the ATM MIB. The association between the AAL5
582 virtual link at the proprietary virtual, internal interface and the
583 ATM virtual link at the ATM interface will be derived from the
584 virtual channel cross-connect table and the virtual channel link
585 table in the ATM MIB.
586
587 ___________________________
588 | |
589 | ============= |
590 | | AAL5 | |
591 | | Entity | |
592 | ============= |
593 | | |
594 | -----Prop. Virtual Interface
595 | | |
596 | ============= |
597 | | ATM | |
598 | | Entity | |
599 | ============= |
600 |_____|__|__|__|__|_______|
601 | | | | |
602 ---------------- ATM UNIs
603 | | | | |
604 | | | | |
605 v v v v v
606
607 Figure 4 : Model of an AAL5 Entity in a Switch
608
609
610
611
612 <span class="grey">Ahmed &amp; Tesink [Page 11]</span></pre>
613 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-12" ></span>
614 <span class="grey"><a href="./rfc1695">RFC 1695</a> ATM Management Objects August 1994</span>
615
616
617 __________________
618 | |
619 | AAL5 |
620 |________________|
621 | |
622 | Prop. Virtual |
623 | Interface |
624 |________________|
625
626 Figure 5 : AAL5 Entity's Interface Stack in a Switch
627
628 <span class="h3"><a class="selflink" id="section-8.2" href="#section-8.2">8.2</a>. Managing AAL5 in a Host</span>
629
630 Managing AAL5 in a host involves managing the AAL5 sublayer interface
631 as shown in Figures 6 and 7. The AAL5 sublayer is stacked directly
632 over the ATM sublayer. The ifTable is applied to the AAL5 sublayer
633 as defined in <a href="#section-8.3">Section 8.3</a>.
634
635 ___________________________
636 | |
637 | ============= |
638 | | AAL5 | |
639 | | Entity | |
640 | ============= |
641 | | ATM | |
642 | | Entity | |
643 | ============= |
644 |___________|_____________|
645 |
646 __|__ ATM UNI
647 |
648 |
649 v
650
651 Figure 6 : Model of an AAL5 Entity in a Host
652
653
654 __________________
655 | |
656 | AAL5 |
657 |________________|
658 | |
659 | ATM Layer |
660 |________________|
661 | |
662 | Physical Layer|
663 |________________|
664
665
666
667
668 <span class="grey">Ahmed &amp; Tesink [Page 12]</span></pre>
669 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-13" ></span>
670 <span class="grey"><a href="./rfc1695">RFC 1695</a> ATM Management Objects August 1994</span>
671
672
673 Figure 7 : AAL5 Entity's Interface Stack in a Host
674
675 <span class="h3"><a class="selflink" id="section-8.3" href="#section-8.3">8.3</a>. Support of AAL5 by ifTable</span>
676
677 The AAL5 entity in an ATM device (e.g., switch or host) is managed
678 using the ifTable. There are additional counters specified for AAL5
679 than those specified in the ATM B-ICI document [<a href="#ref-10" title="&quot;ATM Forum B-ICI Specification, Version 1.0&quot;">10</a>]. Specific
680 interpretations of ifTable for the AAL5 CPCS layer are as follows.
681
682 Object Use for AAL5 CPCS layer entity
683 ====== ==============================
684
685 ifIndex Each AAL5 entity is represented by an ifEntry.
686
687 ifDescr Description of the AAL5 entity.
688
689 ifType The value that is allocated for AAL5 is 49.
690
691 ifMtu Set to the largest PDU size for the
692 AAL5 CPCS layer that can be processed
693 by the AAL5 entity.
694
695 ifSpeed Set to 0.
696
697 ifPhysAddress An octet string of zero length.
698
699 ifAdminStatus See [<a href="#ref-5" title="&quot;Evolution of the Interfaces Group of MIB-II&quot;">5</a>].
700
701 ifOperStatus Assumes the value down(2) if the AAL5 or
702 any layer below that layer is down.
703
704 ifLastChange See [<a href="#ref-5" title="&quot;Evolution of the Interfaces Group of MIB-II&quot;">5</a>].
705
706 ifInOctets The number of received AAL5 CPCS PDU octets.
707
708 ifOutOctets The number of AAL5 CPCS PDU octets
709 transmitted.
710
711 ifInUcastPkts The number of received AAL5 CPCS PDUs passed
712 to a higher-layer.
713
714 ifOutUcastPkts The number of AAL5 CPCS PDUs received from a
715 higher-layer for transmission.
716 [Note: The number of AAL5 PDUs actually
717 transmitted is the number received from a
718 higher-layer for transmission minus any which
719 are counted by ifOutErrors and ifOutDiscards.]
720
721
722
723
724 <span class="grey">Ahmed &amp; Tesink [Page 13]</span></pre>
725 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-14" ></span>
726 <span class="grey"><a href="./rfc1695">RFC 1695</a> ATM Management Objects August 1994</span>
727
728
729 ifInErrors Number of errored AAL5 CPCS PDUs received.
730 The types of errors counted include CRC-32 errors,
731 SAR time-out errors, and oversized SDU errors.
732
733 ifInUnknownProtos Set to 0.
734
735 ifInDiscards Number of received AAL5 CPCS PDUs discarded.
736 Possible reason may be input buffer overflow.
737
738 ifOutErrors Number of AAL5 CPCS PDUs that could not
739 be transmitted due to errors.
740
741 ifOutDiscards Number of AAL5 CPCS PDUs received for
742 transmission that are discarded.
743 Possible reason may be output buffer
744 overflow.
745
746 ifInMulticastPkts Set to 0.
747
748 ifInBroadcastPkts Set to 0.
749
750 ifOutMulticastPkts Set to 0.
751
752 ifOutBroadcastPkts Set to 0.
753
754 ifName Textual name (unique on this system) of the
755 AAL5 entity or an octet string of zero length.
756
757 ifHighSpeed Set to 0.
758
759 ifConnectorPresent Set to false (2).
760
761 ifPromiscuousMode Set to false(2).
762
763 ifLinkUpDownTrapEnable Default is disabled (2).
764
765 <span class="h3"><a class="selflink" id="section-8.4" href="#section-8.4">8.4</a>. Support of Proprietary Virtual Interface by ifTable</span>
766
767 Specific interpretations of ifTable for the proprietary virtual,
768 internal interface associated with an AAL5 entity in an ATM switch
769 are as follows.
770
771 Object Use for proprietary virtual, internal interface
772 associated with AAL entities
773 ====== ===============================================
774
775 ifIndex Each proprietary virtual, internal interface
776 associated with AAL entities is represented by an
777
778
779
780 <span class="grey">Ahmed &amp; Tesink [Page 14]</span></pre>
781 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-15" ></span>
782 <span class="grey"><a href="./rfc1695">RFC 1695</a> ATM Management Objects August 1994</span>
783
784
785 ifEntry.
786
787 ifDescr Description of the proprietary virtual, internal
788 interface associated with AAL entities.
789
790 ifType The value that is allocated for proprietary
791 virtual, internal interface is 53.
792
793 ifSpeed See [<a href="#ref-5" title="&quot;Evolution of the Interfaces Group of MIB-II&quot;">5</a>]. Set to 0 if the speed is not
794 known.
795
796 ifPhysAddress See [<a href="#ref-5" title="&quot;Evolution of the Interfaces Group of MIB-II&quot;">5</a>]. An octet string of zero length
797 if no address is used for this interface.
798
799 ifAdminStatus See [<a href="#ref-5" title="&quot;Evolution of the Interfaces Group of MIB-II&quot;">5</a>].
800
801 ifOperStatus See [<a href="#ref-5" title="&quot;Evolution of the Interfaces Group of MIB-II&quot;">5</a>].
802
803 ifLastChange See [<a href="#ref-5" title="&quot;Evolution of the Interfaces Group of MIB-II&quot;">5</a>].
804
805 ifName Textual name (unique on this system) of the
806 interface or an octet string of zero length.
807
808 ifHighSpeed See [<a href="#ref-5" title="&quot;Evolution of the Interfaces Group of MIB-II&quot;">5</a>]. Set to 0 if the speed is not known.
809
810 ifConnectorPresent Set to false (2).
811
812 ifLinkUpDownTrapEnable Default is disabled (2).
813
814 <span class="h3"><a class="selflink" id="section-8.5" href="#section-8.5">8.5</a>. AAL5 Connection Performance Statistics Group</span>
815
816 An AAL5 connection table is used to provide AAL5 performance
817 information for each AAL5 virtual connection that is terminated at
818 the AAL5 entity contained within an ATM switch or host.
819
820 <span class="h2"><a class="selflink" id="section-9" href="#section-9">9</a>. ILMI MIB and the ATM Managed Objects</span>
821
822 The ILMI MIB is specified by the ATM Forum in UNI specification [<a href="#ref-9" title="&quot;ATM Forum UNI Specification, Version 3.0&quot;">9</a>],
823 to manage local ATM UNIs. The support of the ATM management
824 functions by the ILMI MIB and those contained in this memo are
825 compared in Table 1. In this table, "yes" in the "ILMI MIB" column
826 indicates that the management functions are supported by the ILMI
827 MIB. The MIB groups in the "This memo" column are the groups listed
828 in <a href="#section-5.2">Section 5.2</a>.
829
830 For that subset of management information which the ILMI MIB and this
831 memo have in common, every effort has been made to retain identical
832 semantics and syntax, even though the MIB objects are identified
833
834
835
836 <span class="grey">Ahmed &amp; Tesink [Page 15]</span></pre>
837 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-16" ></span>
838 <span class="grey"><a href="./rfc1695">RFC 1695</a> ATM Management Objects August 1994</span>
839
840
841 using different OBJECT IDENTIFIERs.
842
843 Table 1 - Structuring of ATM Managed Objects
844
845 ______________________________________________________________
846 | |This |ILMI|
847 ATM Mgmt.Inf. |ATM Managed Objects |memo |MIB |
848 ______________|_________________________________|_______|____|
849
850 Local Interface Information:
851 _____________________________________________________________
852 ATM interface:| (1) port identifier |ATM MIB| |
853 physical layer| (2) physical transmission types | gr.1*|yes*|
854 configuration | (3) operational status |MIB II | |
855 | (4) administrative status | | |
856 | (5) last change status | | |
857 _____________________________________________________________
858 ATM interface:| (1) active VPI/VCI fields |ATM MIB| |
859 cell layer | (2) maximum number of VPCs/VCCs | gr.1 |yes |
860 configuration | (3) configured VPCs/VCCs | | ** |
861 | (4) ILMI VPI/VCI values | | |
862 | (5) ATM address type | | |
863 | (6) ATM administrative address | | |
864 _____________________________________________________________
865 ATM interface:|(1) received/transmitted cells | | |
866 cell layer |(2) cells with HEC error |MIB II |yes |
867 performance |(3) cell header validation errors| | |
868 _____________________________________________________________
869 ATM interface:|(1)DS3 PLCP severely errored |ATM MIB| |
870 PLCP &amp; TC | framing seconds | gr.2,3| |
871 layer |(2)DS3 PLCP unavailable seconds | |no |
872 performance |(3)DS3 PLCP alarm state | | |
873 |(4)out of cell delineation events| | |
874 |(5)TC alarm state | | |
875 _____________________________________________________________
876 VP/VC link: |(1)VPI or VPI/VCI value |ATM MIB| |
877 configuration |(2)VCL or VPL operational status | gr. 4|yes |
878 |(3)VCL/VPL administrative status | |*** |
879 |(4)VCL/VPL last change status | | |
880 |(5)transmit/receive traffic/QoS | | |
881 | parameters | | |
882 |(6)AAL type | | |
883 |(7)transmit/receive AAL5 SDU size| | |
884 |(8)AAL5 encapsulation type | | |
885 _____________________________________________________________
886
887
888
889
890
891
892 <span class="grey">Ahmed &amp; Tesink [Page 16]</span></pre>
893 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-17" ></span>
894 <span class="grey"><a href="./rfc1695">RFC 1695</a> ATM Management Objects August 1994</span>
895
896
897 _____________________________________________________________
898 VP/VC |(1)cross-connect identifier | | |
899 Cross-connect:|(2)port identifier of one | | |
900 configuration | end | | |
901 |(3)port identifier of the other |ATM MIB| |
902 | end | gr. 5|no |
903 |(4)VPI or VPI/VCI value | | |
904 | of one end | | |
905 |(5)VPI or VPI/VCI value of | | |
906 | the other end | | |
907 |(6)VC/VP cross-connect | | |
908 | operational status | | |
909 |(7)VC/VP cross-connect | | |
910 | administrative status | | |
911 |(8)VC/VP last change status | | |
912 _____________________________________________________________
913 VCC AAL5 CPCS |(1)PDUs discarded for CRC errors |ATM MIB| |
914 layer: |(2)PDUs discarded due to | gr.6 | |
915 performance | reassembly time out | |no |
916 |(3)PDUs discarded due to large | | |
917 | SDUs | | |
918 _____________________________________________________________
919 AAL5 entity: |(1)received/transmitted PDUs | | |
920 |(2)PDUs discarded due to | | |
921 | protocol errors |MIB II |no |
922 |(3)a set of configuration/state | | |
923 | parameters | | |
924 _____________________________________________________________
925
926 *The operational, administrative, and last change status of
927 the ATM interface and the physical transmission type shall be
928 supported by the interface table in MIB II (<a href="./rfc1213">RFC 1213</a>, <a href="./rfc1573">RFC</a>
929 <a href="./rfc1573">1573</a>). ILMI does not contain the administrative and last
930 change status of the ATM interface.
931
932 ** The ILMI MIB does not contain information on the ATM
933 address type and the ATM administrative address assigned at
934 the ATM interface.
935
936 ***The ILMI MIB contains local and end-to-end operational
937 status of the VPC/VCC segment. However, it does not contain
938 the VPC/VCC administrative and last change status and the VCC
939 AAL information.
940
941
942
943
944
945
946
947
948 <span class="grey">Ahmed &amp; Tesink [Page 17]</span></pre>
949 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-18" ></span>
950 <span class="grey"><a href="./rfc1695">RFC 1695</a> ATM Management Objects August 1994</span>
951
952
953 <span class="h2"><a class="selflink" id="section-10" href="#section-10">10</a>. Definitions</span>
954
955 ATM-MIB DEFINITIONS ::= BEGIN
956
957 IMPORTS
958 MODULE-IDENTITY, OBJECT-TYPE, OBJECT-IDENTITY,
959 Counter32, Integer32, IpAddress
960 FROM SNMPv2-SMI
961 TEXTUAL-CONVENTION, DisplayString,
962 TimeStamp, RowStatus
963 FROM SNMPv2-TC
964 MODULE-COMPLIANCE, OBJECT-GROUP
965 FROM SNMPv2-CONF
966 ifIndex, mib-2
967 FROM <a href="./rfc1213">RFC1213</a>-MIB;
968
969
970 atmMIB MODULE-IDENTITY
971 LAST-UPDATED "9406072245Z"
972 ORGANIZATION "IETF AToM MIB Working Group"
973 CONTACT-INFO
974 " Masuma Ahmed
975 Postal: Bellcore
976 331 Newman Springs Road
977 Red Bank, NJ 07701
978 US
979 Tel: +1 908 758 2515
980 Fax: +1 908 758 4131
981 E-mail: [email protected]
982
983 Kaj Tesink
984 Postal: Bellcore
985 331 Newman Springs Road
986 Red Bank, NJ 07701
987 US
988 Tel: +1 908 758 5254
989 Fax: +1 908 758 4196
990 E-mail: [email protected]"
991 DESCRIPTION
992 "This is the MIB Module for ATM and AAL5-related
993 objects for managing ATM interfaces, ATM virtual
994 links, ATM cross-connects, AAL5 entities, and
995 and AAL5 connections."
996 ::= { mib-2 37 }
997
998 atmMIBObjects OBJECT IDENTIFIER ::= {atmMIB 1}
999
1000 -- This ATM MIB Module consists of the following groups:
1001
1002
1003
1004 <span class="grey">Ahmed &amp; Tesink [Page 18]</span></pre>
1005 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-19" ></span>
1006 <span class="grey"><a href="./rfc1695">RFC 1695</a> ATM Management Objects August 1994</span>
1007
1008
1009 -- (1) ATM Interface configuration group
1010 -- (2) ATM Interface DS3 PLCP group
1011 -- (3) ATM Interface TC Sublayer group
1012 -- (4) ATM Interface VPL configuration group
1013 -- (5) ATM Interface VCL configuration group
1014 -- (6) ATM VP Cross Connect group
1015 -- (7) ATM VC Cross Connect group
1016 -- (8) ATM Interface AAL5 VCC performance statistics
1017 -- group
1018
1019
1020 IfIndex ::= TEXTUAL-CONVENTION
1021 STATUS current
1022 DESCRIPTION
1023 "The value of this object identifies the interface
1024 for which the entry contains management
1025 information. The value of this object for a
1026 particular interface has the same value as the
1027 ifIndex object, defined in <a href="./rfc1213">RFC 1213</a>, for the same
1028 interface."
1029 SYNTAX Integer32
1030
1031
1032 AtmTrafficDescrParamIndex ::= TEXTUAL-CONVENTION
1033 STATUS current
1034 DESCRIPTION
1035 "The value of this object identifies the row
1036 in the atmTrafficDescrParamTable."
1037 SYNTAX Integer32
1038
1039 atmTrafficDescriptorTypes OBJECT IDENTIFIER ::=
1040 {atmMIBObjects 1}
1041
1042 -- The following values are defined for use as
1043 -- possible values of the ATM traffic descriptor type.
1044 -- ATM Forum specified seven types of ATM traffic
1045 -- descriptors.
1046
1047 atmNoTrafficDescriptor OBJECT-IDENTITY
1048 STATUS current
1049 DESCRIPTION
1050 "This identifies the no ATM traffic descriptor
1051 type. Parameters 1, 2, 3, 4, and 5 are not used.
1052 This traffic descriptor type can be used for
1053 best effort traffic."
1054 ::= { atmTrafficDescriptorTypes 1}
1055
1056 atmNoClpNoScr OBJECT-IDENTITY
1057
1058
1059
1060 <span class="grey">Ahmed &amp; Tesink [Page 19]</span></pre>
1061 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-20" ></span>
1062 <span class="grey"><a href="./rfc1695">RFC 1695</a> ATM Management Objects August 1994</span>
1063
1064
1065 STATUS current
1066 DESCRIPTION
1067 "This traffic descriptor is for no CLP and
1068 no Sustained Cell Rate. The use of the
1069 parameter vector for this type:
1070 Parameter 1: CLP=0+1 peak cell rate in
1071 cells per second
1072 Parameter 2: not used
1073 Parameter 3: not used
1074 Parameter 4: not used
1075 Parameter 5: not used.
1076 This traffic descriptor type can be used
1077 for best effort traffic."
1078 ::= { atmTrafficDescriptorTypes 2}
1079
1080 atmClpNoTaggingNoScr OBJECT-IDENTITY
1081 STATUS current
1082 DESCRIPTION
1083 "This traffic descriptor is for no CLP without
1084 tagging and no Sustained Cell Rate. The use
1085 of the parameter vector for this type:
1086 Parameter 1: CLP=0+1 peak cell rate in
1087 cells per second
1088 Parameter 2: CLP=0 peak cell rate in
1089 cells per second
1090 Parameter 3: not used
1091 Parameter 4: not used
1092 Parameter 5: not used."
1093 ::= { atmTrafficDescriptorTypes 3}
1094
1095 atmClpTaggingNoScr OBJECT-IDENTITY
1096 STATUS current
1097 DESCRIPTION
1098 "This traffic descriptor is for CLP with
1099 tagging and no Sustained Cell Rate. The
1100 use of the parameter vector for this type:
1101 Parameter 1: CLP=0+1 peak cell rate in
1102 cells per second
1103 Parameter 2: CLP=0 peak cell rate in
1104 cells per second with excess
1105 traffic tagged as CLP=1
1106 Parameter 3: not used
1107 Parameter 4: not used
1108 Parameter 5: not used."
1109 ::= { atmTrafficDescriptorTypes 4}
1110
1111 atmNoClpScr OBJECT-IDENTITY
1112 STATUS current
1113
1114
1115
1116 <span class="grey">Ahmed &amp; Tesink [Page 20]</span></pre>
1117 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-21" ></span>
1118 <span class="grey"><a href="./rfc1695">RFC 1695</a> ATM Management Objects August 1994</span>
1119
1120
1121 DESCRIPTION
1122 "This traffic descriptor is for no CLP
1123 with Sustained Cell Rate. The
1124 use of the parameter vector for this type:
1125 Parameter 1: CLP=0+1 peak cell rate in
1126 cells per second
1127 Parameter 2: CLP=0+1 sustained cell rate in
1128 cells per second
1129 Parameter 3: CLP=0+1 maximum burst size
1130 in cells
1131 Parameter 4: not used
1132 Parameter 5: not used."
1133 ::= { atmTrafficDescriptorTypes 5}
1134
1135 atmClpNoTaggingScr OBJECT-IDENTITY
1136 STATUS current
1137 DESCRIPTION
1138 "This traffic descriptor is for CLP
1139 with Sustained Cell Rate and no tagging.
1140 The use of the parameter vector for this type:
1141 Parameter 1: CLP=0+1 peak cell rate in
1142 cells per second
1143 Parameter 2: CLP=0 sustained cell rate in
1144 cells per second
1145 Parameter 3: CLP=0 maximum burst size in cells
1146 Parameter 4: not used
1147 Parameter 5: not used."
1148 ::= { atmTrafficDescriptorTypes 6}
1149
1150 atmClpTaggingScr OBJECT-IDENTITY
1151 STATUS current
1152 DESCRIPTION
1153 "This traffic descriptor is for CLP
1154 with tagging and Sustained Cell Rate.
1155 The use of the parameter vector for this type:
1156 Parameter 1: CLP=0+1 peak cell rate in
1157 cells per second
1158 Parameter 2: CLP=0 sustained cell rate in
1159 cells per second with excess
1160 traffic tagged as CLP=1
1161 Parameter 3: CLP=0 maximum burst size in cells
1162 Parameter 4: not used
1163 Parameter 5: not used."
1164 ::= { atmTrafficDescriptorTypes 7}
1165
1166
1167 -- ATM Interface Configuration Parameters Group
1168
1169
1170
1171
1172 <span class="grey">Ahmed &amp; Tesink [Page 21]</span></pre>
1173 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-22" ></span>
1174 <span class="grey"><a href="./rfc1695">RFC 1695</a> ATM Management Objects August 1994</span>
1175
1176
1177 -- This group contains ATM specific
1178 -- configuration information associated with
1179 -- an ATM interface beyond those
1180 -- supported using the ifTable.
1181
1182
1183 atmInterfaceConfTable OBJECT-TYPE
1184 SYNTAX SEQUENCE OF AtmInterfaceConfEntry
1185 MAX-ACCESS not-accessible
1186 STATUS current
1187 DESCRIPTION
1188 "This table contains ATM local interface
1189 configuration parameters, one entry per ATM
1190 interface port."
1191 ::= { atmMIBObjects 2 }
1192
1193 atmInterfaceConfEntry OBJECT-TYPE
1194 SYNTAX AtmInterfaceConfEntry
1195 MAX-ACCESS not-accessible
1196 STATUS current
1197 DESCRIPTION
1198 "This list contains ATM interface configuration
1199 parameters and state variables."
1200 INDEX { ifIndex }
1201 ::= { atmInterfaceConfTable 1}
1202
1203 AtmInterfaceConfEntry ::= SEQUENCE {
1204 atmInterfaceMaxVpcs INTEGER,
1205 atmInterfaceMaxVccs INTEGER,
1206 atmInterfaceConfVpcs INTEGER,
1207 atmInterfaceConfVccs INTEGER,
1208 atmInterfaceMaxActiveVpiBits INTEGER,
1209 atmInterfaceMaxActiveVciBits INTEGER,
1210 atmInterfaceIlmiVpi INTEGER,
1211 atmInterfaceIlmiVci INTEGER,
1212 atmInterfaceAddressType INTEGER,
1213 atmInterfaceAdminAddress OCTET STRING,
1214 atmInterfaceMyNeighborIpAddress IpAddress,
1215 atmInterfaceMyNeighborIfName DisplayString
1216 }
1217
1218 atmInterfaceMaxVpcs OBJECT-TYPE
1219 SYNTAX INTEGER (0..4096)
1220 MAX-ACCESS read-write
1221 STATUS current
1222 DESCRIPTION
1223 "The maximum number of VPCs (PVCs and SVCs)
1224 supported at this ATM interface. At the ATM UNI,
1225
1226
1227
1228 <span class="grey">Ahmed &amp; Tesink [Page 22]</span></pre>
1229 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-23" ></span>
1230 <span class="grey"><a href="./rfc1695">RFC 1695</a> ATM Management Objects August 1994</span>
1231
1232
1233 the maximum number of VPCs (PVCs and SVCs)
1234 ranges from 0 to 256 only."
1235 ::= { atmInterfaceConfEntry 1}
1236
1237 atmInterfaceMaxVccs OBJECT-TYPE
1238 SYNTAX INTEGER (0..65536)
1239 MAX-ACCESS read-write
1240 STATUS current
1241 DESCRIPTION
1242 "The maximum number of VCCs (PVCs and SVCs)
1243 supported at this ATM interface."
1244 ::= { atmInterfaceConfEntry 2}
1245
1246 atmInterfaceConfVpcs OBJECT-TYPE
1247 SYNTAX INTEGER (0..4096)
1248 MAX-ACCESS read-only
1249 STATUS current
1250 DESCRIPTION
1251 "The number of VPCs (PVCs and SVCs)
1252 configured for use at this ATM interface.
1253 At the ATM UNI, the configured number of
1254 VPCs (PVCs and SVCs) can range from
1255 0 to 256 only."
1256 ::= { atmInterfaceConfEntry 3}
1257
1258 atmInterfaceConfVccs OBJECT-TYPE
1259 SYNTAX INTEGER (0..65536)
1260 MAX-ACCESS read-only
1261 STATUS current
1262 DESCRIPTION
1263 "The number of VCCs (PVCs and SVCs)
1264 configured for use at the ATM interface."
1265 ::= { atmInterfaceConfEntry 4}
1266
1267 atmInterfaceMaxActiveVpiBits OBJECT-TYPE
1268 SYNTAX INTEGER (0..12)
1269 MAX-ACCESS read-write
1270 STATUS current
1271 DESCRIPTION
1272 "The maximum number of active VPI bits
1273 configured for use at the ATM interface.
1274 At the ATM UNI, the maximum number of active
1275 VPI bits configured for use ranges from
1276 0 to 8 only."
1277 ::= { atmInterfaceConfEntry 5}
1278
1279 atmInterfaceMaxActiveVciBits OBJECT-TYPE
1280 SYNTAX INTEGER (0..16)
1281
1282
1283
1284 <span class="grey">Ahmed &amp; Tesink [Page 23]</span></pre>
1285 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-24" ></span>
1286 <span class="grey"><a href="./rfc1695">RFC 1695</a> ATM Management Objects August 1994</span>
1287
1288
1289 MAX-ACCESS read-write
1290 STATUS current
1291 DESCRIPTION
1292 "The maximum number of active VCI bits
1293 configured for use at this ATM interface."
1294 ::= { atmInterfaceConfEntry 6}
1295
1296 atmInterfaceIlmiVpi OBJECT-TYPE
1297 SYNTAX INTEGER (0..255)
1298 MAX-ACCESS read-write
1299 STATUS current
1300 DESCRIPTION
1301 "The VPI value of the VCC supporting
1302 the ILMI at this ATM interface. If the values of
1303 atmInterfaceIlmiVpi and atmInterfaceIlmiVci are
1304 both equal to zero then the ILMI is not
1305 supported at this ATM interface."
1306 DEFVAL { 0 }
1307 ::= { atmInterfaceConfEntry 7}
1308
1309 atmInterfaceIlmiVci OBJECT-TYPE
1310 SYNTAX INTEGER (0..65535)
1311 MAX-ACCESS read-write
1312 STATUS current
1313 DESCRIPTION
1314 "The VCI value of the VCC supporting
1315 the ILMI at this ATM interface. If the values of
1316 atmInterfaceIlmiVpi and atmInterfaceIlmiVci are
1317 both equal to zero then the ILMI is not
1318 supported at this ATM interface."
1319 DEFVAL { 16 }
1320 ::= { atmInterfaceConfEntry 8}
1321
1322 atmInterfaceAddressType OBJECT-TYPE
1323 SYNTAX INTEGER {
1324 private(1),
1325 nsapE164(2),
1326 nativeE164(3),
1327 other(4)
1328 }
1329 MAX-ACCESS read-only
1330 STATUS current
1331 DESCRIPTION
1332 "The type of primary ATM address configured
1333 for use at this ATM interface."
1334 ::= { atmInterfaceConfEntry 9 }
1335
1336 atmInterfaceAdminAddress OBJECT-TYPE
1337
1338
1339
1340 <span class="grey">Ahmed &amp; Tesink [Page 24]</span></pre>
1341 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-25" ></span>
1342 <span class="grey"><a href="./rfc1695">RFC 1695</a> ATM Management Objects August 1994</span>
1343
1344
1345 SYNTAX OCTET STRING (SIZE(0..255))
1346 MAX-ACCESS read-only
1347 STATUS current
1348 DESCRIPTION
1349 "An address assigned for administrative purposes,
1350 for example, an address associated with the
1351 service provider side of a public network UNI.
1352 If this interface has no assigned administrative
1353 address, or when the address used for
1354 administrative purposes is the same as that used
1355 for ifPhysAddress, then this is an octet string of
1356 zero length."
1357 ::= { atmInterfaceConfEntry 10 }
1358
1359 atmInterfaceMyNeighborIpAddress OBJECT-TYPE
1360 SYNTAX IpAddress
1361 MAX-ACCESS read-write
1362 STATUS current
1363 DESCRIPTION
1364 "The IP address of the neighbor system connected to
1365 the far end of this interface, to which a Network
1366 Management Station can send SNMP messages, as IP
1367 datagrams sent to UDP port 161, in order to access
1368 network management information concerning the
1369 operation of that system. Note that the value
1370 of this object may be obtained in different ways,
1371 e.g., by manual configuration, or through ILMI
1372 interaction with the neighbor system."
1373 ::= { atmInterfaceConfEntry 11 }
1374
1375 atmInterfaceMyNeighborIfName OBJECT-TYPE
1376 SYNTAX DisplayString
1377 MAX-ACCESS read-write
1378 STATUS current
1379 DESCRIPTION
1380 "The textual name of the interface on the neighbor
1381 system on the far end of this interface, and to
1382 which this interface connects. If the neighbor
1383 system is manageable through SNMP and supports
1384 the object ifName, the value of this object must
1385 be identical with that of ifName for the ifEntry
1386 of the lowest level physical interface
1387 for this port. If this interface does not have a
1388 textual name, the value of this object is a zero
1389 length string. Note that the value of this object
1390 may be obtained in different ways, e.g., by manual
1391 configuration, or through ILMI interaction with
1392 the neighbor system."
1393
1394
1395
1396 <span class="grey">Ahmed &amp; Tesink [Page 25]</span></pre>
1397 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-26" ></span>
1398 <span class="grey"><a href="./rfc1695">RFC 1695</a> ATM Management Objects August 1994</span>
1399
1400
1401 ::= { atmInterfaceConfEntry 12 }
1402
1403
1404 -- The ATM Interface DS3 PLCP Group
1405
1406 -- This group contains the DS3 PLCP configuration and
1407 -- state parameters of those ATM interfaces
1408 -- which use DS3 PLCP for carrying ATM cells over DS3.
1409
1410 atmInterfaceDs3PlcpTable OBJECT-TYPE
1411 SYNTAX SEQUENCE OF AtmInterfaceDs3PlcpEntry
1412 MAX-ACCESS not-accessible
1413 STATUS current
1414 DESCRIPTION
1415 "This table contains ATM interface DS3 PLCP
1416 parameters and state variables, one entry per
1417 ATM interface port."
1418 ::= { atmMIBObjects 3}
1419
1420 atmInterfaceDs3PlcpEntry OBJECT-TYPE
1421 SYNTAX AtmInterfaceDs3PlcpEntry
1422 MAX-ACCESS not-accessible
1423 STATUS current
1424 DESCRIPTION
1425 "This list contains DS3 PLCP parameters and
1426 state variables at the ATM interface."
1427 INDEX {ifIndex }
1428 ::= { atmInterfaceDs3PlcpTable 1}
1429
1430 AtmInterfaceDs3PlcpEntry ::= SEQUENCE {
1431 atmInterfaceDs3PlcpSEFSs Counter32,
1432 atmInterfaceDs3PlcpAlarmState INTEGER,
1433 atmInterfaceDs3PlcpUASs Counter32
1434 }
1435
1436
1437 atmInterfaceDs3PlcpSEFSs OBJECT-TYPE
1438 SYNTAX Counter32
1439 MAX-ACCESS read-only
1440 STATUS current
1441 DESCRIPTION
1442 "The number of DS3 PLCP Severely Errored Framing
1443 Second (SEFS). Each SEFS represents a
1444 one-second interval which contains
1445 one or more SEF event."
1446 ::= { atmInterfaceDs3PlcpEntry 1}
1447
1448 atmInterfaceDs3PlcpAlarmState OBJECT-TYPE
1449
1450
1451
1452 <span class="grey">Ahmed &amp; Tesink [Page 26]</span></pre>
1453 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-27" ></span>
1454 <span class="grey"><a href="./rfc1695">RFC 1695</a> ATM Management Objects August 1994</span>
1455
1456
1457 SYNTAX INTEGER {
1458 noAlarm(1),
1459 receivedFarEndAlarm(2),
1460 incomingLOF(3)
1461 }
1462 MAX-ACCESS read-only
1463 STATUS current
1464 DESCRIPTION
1465 "This variable indicates if there is an
1466 alarm present for the DS3 PLCP. The value
1467 receivedFarEndAlarm means that the DS3 PLCP
1468 has received an incoming Yellow
1469 Signal, the value incomingLOF means that
1470 the DS3 PLCP has declared a loss of frame (LOF)
1471 failure condition, and the value noAlarm
1472 means that there are no alarms present.
1473 Transition from the failure to the no alarm state
1474 occurs when no defects (e.g., LOF) are received
1475 for more than 10 seconds."
1476 ::= { atmInterfaceDs3PlcpEntry 2}
1477
1478 atmInterfaceDs3PlcpUASs OBJECT-TYPE
1479 SYNTAX Counter32
1480 MAX-ACCESS read-only
1481 STATUS current
1482 DESCRIPTION
1483 "The counter associated with the number of
1484 Unavailable Seconds encountered by the PLCP."
1485 ::= { atmInterfaceDs3PlcpEntry 3}
1486
1487
1488 -- The ATM Interface TC Sublayer Group
1489
1490 -- This group contains TC sublayer configuration and
1491 -- state parameters of those ATM interfaces
1492 -- which use TC sublayer for carrying ATM cells over
1493 -- SONET or DS3.
1494
1495
1496 atmInterfaceTCTable OBJECT-TYPE
1497 SYNTAX SEQUENCE OF AtmInterfaceTCEntry
1498 MAX-ACCESS not-accessible
1499 STATUS current
1500 DESCRIPTION
1501 "This table contains ATM interface TC
1502 Sublayer parameters and state variables,
1503 one entry per ATM interface port."
1504 ::= { atmMIBObjects 4}
1505
1506
1507
1508 <span class="grey">Ahmed &amp; Tesink [Page 27]</span></pre>
1509 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-28" ></span>
1510 <span class="grey"><a href="./rfc1695">RFC 1695</a> ATM Management Objects August 1994</span>
1511
1512
1513 atmInterfaceTCEntry OBJECT-TYPE
1514 SYNTAX AtmInterfaceTCEntry
1515 MAX-ACCESS not-accessible
1516 STATUS current
1517 DESCRIPTION
1518 "This list contains TC Sublayer parameters
1519 and state variables at the ATM interface."
1520 INDEX {ifIndex }
1521 ::= { atmInterfaceTCTable 1}
1522
1523 AtmInterfaceTCEntry ::= SEQUENCE {
1524 atmInterfaceOCDEvents Counter32,
1525 atmInterfaceTCAlarmState INTEGER
1526 }
1527
1528 atmInterfaceOCDEvents OBJECT-TYPE
1529 SYNTAX Counter32
1530 MAX-ACCESS read-only
1531 STATUS current
1532 DESCRIPTION
1533 "The number of times the Out of Cell
1534 Delineation (OCD) events occur. If seven
1535 consecutive ATM cells have Header Error
1536 Control (HEC) violations, an OCD event occurs.
1537 A high number of OCD events may indicate a
1538 problem with the TC Sublayer."
1539 ::= { atmInterfaceTCEntry 1}
1540
1541 atmInterfaceTCAlarmState OBJECT-TYPE
1542 SYNTAX INTEGER {
1543 noAlarm(1),
1544 lcdFailure(2)
1545 }
1546 MAX-ACCESS read-only
1547 STATUS current
1548 DESCRIPTION
1549 "This variable indicates if there is an
1550 alarm present for the TC Sublayer. The value
1551 lcdFailure indicates that a Loss of
1552 Cell Delineation (LCD) failure state has been
1553 declared for the TC Sublayer. Transition from
1554 failure to the no alarm state occurs
1555 when 6 consecutive ATM cells
1556 are received with valid HEC, followed by
1557 about 10 seconds of acceptable working signal."
1558 ::= { atmInterfaceTCEntry 2}
1559
1560
1561
1562
1563
1564 <span class="grey">Ahmed &amp; Tesink [Page 28]</span></pre>
1565 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-29" ></span>
1566 <span class="grey"><a href="./rfc1695">RFC 1695</a> ATM Management Objects August 1994</span>
1567
1568
1569 -- ATM Traffic Descriptor Parameter Group
1570
1571 -- This group contains a set of self-consistent
1572 -- ATM traffic parameters including the
1573 -- ATM traffic QoS Class.
1574
1575 -- The ATM virtual link tables (i.e., VPL and VCL tables)
1576 -- will use this ATM Traffic Descriptor table
1577 -- to assign traffic parameters and QoS Class
1578 -- to the receive and transmit directions of
1579 -- the ATM virtual links (i.e., VPLs and VCLs).
1580 -- The ATM VPL or VCL table will indicate a row
1581 -- in the atmTrafficDescrParamTable
1582 -- using its atmTrafficDescrParamIndex value.
1583 -- The management application can then compare a set of
1584 -- ATM traffic parameters with a single value.
1585
1586 -- If no suitable row(s) in the atmTrafficDescrParamTable
1587 -- exists, the manager must create a new row(s) in this
1588 -- table. If such a row is created, agent checks the
1589 -- sanity of that set of ATM traffic parameter values.
1590
1591 -- When creating a new row, the parameter values
1592 -- will be checked for self-consistency.
1593 -- Predefined/template rows may be supported.
1594
1595 -- A row in the atmTrafficDescrParamTable is deleted
1596 -- by setting the atmTrafficDescrRowStatus to destroy(6).
1597 -- The agent will check whether this row is still in use
1598 -- by any entry of the atmVplTable or atmVclTable.
1599 -- The agent denies the request if the row is still in
1600 -- use.
1601
1602 -- The ATM Traffic Descriptor Parameter Table
1603
1604
1605 atmTrafficDescrParamTable OBJECT-TYPE
1606 SYNTAX SEQUENCE OF AtmTrafficDescrParamEntry
1607 MAX-ACCESS not-accessible
1608 STATUS current
1609 DESCRIPTION
1610 "This table contains information on ATM traffic
1611 descriptor type and the associated parameters."
1612 ::= { atmMIBObjects 5}
1613
1614 atmTrafficDescrParamEntry OBJECT-TYPE
1615 SYNTAX AtmTrafficDescrParamEntry
1616 MAX-ACCESS not-accessible
1617
1618
1619
1620 <span class="grey">Ahmed &amp; Tesink [Page 29]</span></pre>
1621 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-30" ></span>
1622 <span class="grey"><a href="./rfc1695">RFC 1695</a> ATM Management Objects August 1994</span>
1623
1624
1625 STATUS current
1626 DESCRIPTION
1627 "This list contains ATM traffic descriptor
1628 type and the associated parameters."
1629 INDEX {atmTrafficDescrParamIndex}
1630 ::= { atmTrafficDescrParamTable 1}
1631
1632 AtmTrafficDescrParamEntry ::= SEQUENCE {
1633 atmTrafficDescrParamIndex AtmTrafficDescrParamIndex,
1634 atmTrafficDescrType OBJECT IDENTIFIER,
1635 atmTrafficDescrParam1 Integer32,
1636 atmTrafficDescrParam2 Integer32,
1637 atmTrafficDescrParam3 Integer32,
1638 atmTrafficDescrParam4 Integer32,
1639 atmTrafficDescrParam5 Integer32,
1640 atmTrafficQoSClass INTEGER,
1641 atmTrafficDescrRowStatus RowStatus
1642 }
1643
1644 atmTrafficDescrParamIndex OBJECT-TYPE
1645 SYNTAX AtmTrafficDescrParamIndex
1646 MAX-ACCESS not-accessible
1647 STATUS current
1648 DESCRIPTION
1649 "This object is used by the virtual link
1650 table (i.e., VPL or VCL table)
1651 to identify the row of this table."
1652 ::= { atmTrafficDescrParamEntry 1}
1653
1654 atmTrafficDescrType OBJECT-TYPE
1655 SYNTAX OBJECT IDENTIFIER
1656 MAX-ACCESS read-create
1657 STATUS current
1658 DESCRIPTION
1659 "The value of this object identifies the type
1660 of ATM traffic descriptor.
1661 The type may indicate no traffic descriptor or
1662 traffic descriptor with one or more parameters.
1663 These parameters are specified as a parameter
1664 vector, in the corresponding instances of the
1665 objects:
1666 atmTrafficDescrParam1
1667 atmTrafficDescrParam2
1668 atmTrafficDescrParam3
1669 atmTrafficDescrParam4
1670 atmTrafficDescrParam5."
1671 DEFVAL { atmNoTrafficDescriptor }
1672 ::= { atmTrafficDescrParamEntry 2}
1673
1674
1675
1676 <span class="grey">Ahmed &amp; Tesink [Page 30]</span></pre>
1677 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-31" ></span>
1678 <span class="grey"><a href="./rfc1695">RFC 1695</a> ATM Management Objects August 1994</span>
1679
1680
1681 atmTrafficDescrParam1 OBJECT-TYPE
1682 SYNTAX Integer32
1683 MAX-ACCESS read-create
1684 STATUS current
1685 DESCRIPTION
1686 "The first parameter of the ATM traffic descriptor
1687 used according to the value of
1688 atmTrafficDescrType."
1689 DEFVAL { 0 }
1690 ::= { atmTrafficDescrParamEntry 3}
1691
1692 atmTrafficDescrParam2 OBJECT-TYPE
1693 SYNTAX Integer32
1694 MAX-ACCESS read-create
1695 STATUS current
1696 DESCRIPTION
1697 "The second parameter of the ATM traffic descriptor
1698 used according to the value of
1699 atmTrafficDescrType."
1700 DEFVAL { 0 }
1701 ::= { atmTrafficDescrParamEntry 4}
1702
1703 atmTrafficDescrParam3 OBJECT-TYPE
1704 SYNTAX Integer32
1705 MAX-ACCESS read-create
1706 STATUS current
1707 DESCRIPTION
1708 "The third parameter of the ATM traffic descriptor
1709 used according to the value of
1710 atmTrafficDescrType."
1711 DEFVAL { 0 }
1712 ::= { atmTrafficDescrParamEntry 5}
1713
1714 atmTrafficDescrParam4 OBJECT-TYPE
1715 SYNTAX Integer32
1716 MAX-ACCESS read-create
1717 STATUS current
1718 DESCRIPTION
1719 "The fourth parameter of the ATM traffic descriptor
1720 used according to the value of
1721 atmTrafficDescrType."
1722 DEFVAL { 0 }
1723 ::= { atmTrafficDescrParamEntry 6}
1724
1725 atmTrafficDescrParam5 OBJECT-TYPE
1726 SYNTAX Integer32
1727 MAX-ACCESS read-create
1728 STATUS current
1729
1730
1731
1732 <span class="grey">Ahmed &amp; Tesink [Page 31]</span></pre>
1733 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-32" ></span>
1734 <span class="grey"><a href="./rfc1695">RFC 1695</a> ATM Management Objects August 1994</span>
1735
1736
1737 DESCRIPTION
1738 "The fifth parameter of the ATM traffic descriptor
1739 used according to the value of
1740 atmTrafficDescrType."
1741 DEFVAL { 0 }
1742 ::= { atmTrafficDescrParamEntry 7}
1743
1744 atmTrafficQoSClass OBJECT-TYPE
1745 SYNTAX INTEGER (0..255)
1746 MAX-ACCESS read-create
1747 STATUS current
1748 DESCRIPTION
1749 "The value of this object identifies the QoS Class.
1750 Four Service classes have been
1751 specified in the ATM Forum UNI Specification:
1752 Service Class A: Constant bit rate video and
1753 Circuit emulation
1754 Service Class B: Variable bit rate video/audio
1755 Service Class C: Connection-oriented data
1756 Service Class D: Connectionless data
1757 Four QoS classes numbered 1, 2, 3, and 4 have
1758 been specified with the aim to support service
1759 classes A, B, C, and D respectively.
1760 An unspecified QoS Class numbered `0' is used
1761 for best effort traffic."
1762 DEFVAL { 0 }
1763 ::= { atmTrafficDescrParamEntry 8}
1764
1765
1766 atmTrafficDescrRowStatus OBJECT-TYPE
1767 SYNTAX RowStatus
1768 MAX-ACCESS read-create
1769 STATUS current
1770 DESCRIPTION
1771 "This object is used to create
1772 a new row or modify or delete an
1773 existing row in this table."
1774 DEFVAL { active }
1775 ::= {atmTrafficDescrParamEntry 9}
1776
1777
1778 -- ATM Interface Virtual Path Link (VPL) Group
1779
1780 -- This group contains configuration and state
1781 -- information of a bi-directional Virtual Path Link
1782 -- (VPL)
1783
1784 -- This table can be used to create, delete or modify
1785
1786
1787
1788 <span class="grey">Ahmed &amp; Tesink [Page 32]</span></pre>
1789 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-33" ></span>
1790 <span class="grey"><a href="./rfc1695">RFC 1695</a> ATM Management Objects August 1994</span>
1791
1792
1793 -- a VPL that is terminated in an ATM host or switch.
1794 -- This table can also be used to create, delete or
1795 -- modify a VPL which is cross-connected to another
1796 -- VPL.
1797
1798 -- In the example below, the traffic flows on the receive
1799 -- and transmit directions of the VPLs are characterized
1800 -- by atmVplReceiveTrafficDescrIndex and
1801 -- atmVplTransmitTrafficDescrIndex respectively.
1802 -- The cross-connected VPLs are identified by
1803 -- atmVplCrossConnectIdentifier.
1804
1805
1806
1807 -- ________________________________
1808 -- | |
1809 -- VPL | ATM Host, Switch, or Network | VPL
1810 -- receive | | receive
1811 -- ========&gt; X X &lt;=======
1812 -- &lt;======== X X ========&gt;
1813 -- transmit | | transmit
1814 -- |______________________________|
1815
1816
1817
1818 -- The ATM Interface VPL Table
1819
1820
1821 atmVplTable OBJECT-TYPE
1822 SYNTAX SEQUENCE OF AtmVplEntry
1823 MAX-ACCESS not-accessible
1824 STATUS current
1825 DESCRIPTION
1826 "The Virtual Path Link (VPL) table. A
1827 bi-directional VPL is modeled as one entry
1828 in this table."
1829 ::= { atmMIBObjects 6}
1830
1831 atmVplEntry OBJECT-TYPE
1832 SYNTAX AtmVplEntry
1833 MAX-ACCESS not-accessible
1834 STATUS current
1835 DESCRIPTION
1836 "An entry in the VPL table. This entry is
1837 used to model a bi-directional VPL.
1838 To create a VPL at an ATM interface,
1839 either of the following procedures are used:
1840
1841
1842
1843
1844 <span class="grey">Ahmed &amp; Tesink [Page 33]</span></pre>
1845 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-34" ></span>
1846 <span class="grey"><a href="./rfc1695">RFC 1695</a> ATM Management Objects August 1994</span>
1847
1848
1849 Negotiated VPL establishment
1850
1851 (1) The management application creates
1852 a VPL entry in the atmVplTable
1853 by setting atmVplRowStatus to createAndWait(5).
1854 This may fail for the following reasons:
1855 - The selected VPI value is unavailable,
1856 - The selected VPI value is in use.
1857 Otherwise, the agent creates a row and
1858 reserves the VPI value on that port.
1859
1860 (2) The manager selects an existing row(s) in the
1861 atmTrafficDescrParamTable,
1862 thereby, selecting a set of self-consistent
1863 ATM traffic parameters and the QoS Class
1864 for receive and transmit directions of the VPL.
1865
1866 (2a) If no suitable row(s) in the
1867 atmTrafficDescrParamTable exists,
1868 the manager must create a new row(s)
1869 in that table.
1870
1871 (2b) The manager characterizes the VPL's traffic
1872 parameters through setting the
1873 atmVplReceiveTrafficDescrIndex and the
1874 atmVplTransmitTrafficDescrIndex values
1875 in the VPL table, which point to the rows
1876 containing desired ATM traffic parameter values
1877 in the atmTrafficDescrParamTable. The agent
1878 will check the availability of resources and
1879 may refuse the request.
1880
1881 (3) The manager activates the VPL by setting the
1882 the atmVplRowStatus to active(1).
1883 If this set is successful, the agent has
1884 reserved the resources to satisfy the requested
1885 traffic parameter values and the QoS Class
1886 for that VPL.
1887 (4) If the VPL terminates a VPC in the ATM host
1888 or switch, the manager turns on the
1889 atmVplAdminStatus to up(1) to turn the VPL
1890 traffic flow on. Otherwise, the
1891 atmVpCrossConnectTable must be used
1892 to cross-connect the VPL to another VPL(s)
1893 in an ATM switch or network.
1894
1895 One-Shot VPL Establishment
1896
1897
1898
1899
1900 <span class="grey">Ahmed &amp; Tesink [Page 34]</span></pre>
1901 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-35" ></span>
1902 <span class="grey"><a href="./rfc1695">RFC 1695</a> ATM Management Objects August 1994</span>
1903
1904
1905 A VPL may also be established in one step by a
1906 set-request with all necessary VPL parameter
1907 values and atmVplRowStatus set to createAndGo(4).
1908
1909 In contrast to the negotiated VPL establishment
1910 which allows for detailed error checking
1911 (i.e., set errors are explicitly linked to
1912 particular resource acquisition failures),
1913 the one-shot VPL establishment
1914 performs the setup on one operation but
1915 does not have the advantage of step-wise
1916 error checking.
1917
1918 VPL Retirement
1919
1920 A VPL is released by setting atmVplRowStatus to
1921 destroy(6), and the agent may release all
1922 associated resources."
1923 INDEX {ifIndex, atmVplVpi }
1924 ::= { atmVplTable 1}
1925
1926 AtmVplEntry ::= SEQUENCE {
1927 atmVplVpi INTEGER,
1928 atmVplAdminStatus INTEGER,
1929 atmVplOperStatus INTEGER,
1930 atmVplLastChange TimeStamp,
1931 atmVplReceiveTrafficDescrIndex
1932 AtmTrafficDescrParamIndex,
1933 atmVplTransmitTrafficDescrIndex
1934 AtmTrafficDescrParamIndex,
1935 atmVplCrossConnectIdentifier INTEGER,
1936 atmVplRowStatus RowStatus
1937 }
1938
1939
1940 atmVplVpi OBJECT-TYPE
1941 SYNTAX INTEGER (1..4095)
1942 MAX-ACCESS not-accessible
1943 STATUS current
1944 DESCRIPTION
1945 "The VPI value of the VPL.
1946 Note that the VPI=0 is not used
1947 for a VPL not associated with a VCL.
1948 The maximum VPI value cannot
1949 exceed the value allowable by the
1950 atmInterfaceMaxVpiBits."
1951 ::= { atmVplEntry 1}
1952
1953
1954
1955
1956 <span class="grey">Ahmed &amp; Tesink [Page 35]</span></pre>
1957 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-36" ></span>
1958 <span class="grey"><a href="./rfc1695">RFC 1695</a> ATM Management Objects August 1994</span>
1959
1960
1961 atmVplAdminStatus OBJECT-TYPE
1962 SYNTAX INTEGER {
1963 up(1),
1964 down(2)
1965 }
1966 MAX-ACCESS read-create
1967 STATUS current
1968 DESCRIPTION
1969 "This object is implemented only for a VPL which
1970 terminates a VPC (i.e.,
1971 one which is NOT cross-connected to other VPLs).
1972 Its value specifies the desired administrative
1973 state of the VPL. The up and down states indicate
1974 that the traffic flow is enabled and disabled
1975 respectively for this VPL."
1976 DEFVAL { down }
1977 ::= { atmVplEntry 2}
1978
1979
1980 atmVplOperStatus OBJECT-TYPE
1981 SYNTAX INTEGER {
1982 up(1),
1983 down(2),
1984 unknown(3)
1985 }
1986 MAX-ACCESS read-only
1987 STATUS current
1988 DESCRIPTION
1989 "This object indicates the current operational
1990 status of the VPL. The up and down states
1991 indicate that the VPL is currently
1992 operational, or not operational, respectively.
1993 The unknown state indicates that the status of
1994 this VPL cannot be determined."
1995 ::= { atmVplEntry 3}
1996
1997 atmVplLastChange OBJECT-TYPE
1998 SYNTAX TimeStamp
1999 MAX-ACCESS read-only
2000 STATUS current
2001 DESCRIPTION
2002 "The value of MIB II's sysUpTime object
2003 at the time this VPL entered its current
2004 operational state. If the current state was
2005 entered prior to the last re-initialization of the
2006 agent, then this object contains a zero value."
2007 ::= { atmVplEntry 4 }
2008
2009
2010
2011
2012 <span class="grey">Ahmed &amp; Tesink [Page 36]</span></pre>
2013 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-37" ></span>
2014 <span class="grey"><a href="./rfc1695">RFC 1695</a> ATM Management Objects August 1994</span>
2015
2016
2017 atmVplReceiveTrafficDescrIndex OBJECT-TYPE
2018 SYNTAX AtmTrafficDescrParamIndex
2019 MAX-ACCESS read-create
2020 STATUS current
2021 DESCRIPTION
2022 "The value of this object identifies the row
2023 in the atmTrafficDescrParamTable which
2024 applies to the receive direction of the VPL."
2025 ::= { atmVplEntry 5}
2026
2027 atmVplTransmitTrafficDescrIndex OBJECT-TYPE
2028 SYNTAX AtmTrafficDescrParamIndex
2029 MAX-ACCESS read-create
2030 STATUS current
2031 DESCRIPTION
2032 "The value of this object identifies the row
2033 in the atmTrafficDescrParamTable which
2034 applies to the transmit direction of the VPL."
2035 ::= { atmVplEntry 6}
2036
2037 atmVplCrossConnectIdentifier OBJECT-TYPE
2038 SYNTAX INTEGER (0..2147483647)
2039 MAX-ACCESS read-only
2040 STATUS current
2041 DESCRIPTION
2042 "This object is implemented only for a VPL
2043 which is cross-connected to other VPLs
2044 that belong to the same VPC. All such
2045 associated VPLs have the same value of this
2046 object, and all their cross-connections are
2047 identified by entries in the
2048 atmVpCrossConnectTable for which
2049 atmVpCrossConnectIndex has the same value.
2050 The value of this object is initialized by the
2051 agent after the associated entries in the
2052 atmVpCrossConnectTable have been created."
2053 ::= {atmVplEntry 7}
2054
2055 atmVplRowStatus OBJECT-TYPE
2056 SYNTAX RowStatus
2057 MAX-ACCESS read-create
2058 STATUS current
2059 DESCRIPTION
2060 "This object is used to create, delete
2061 or modify a row in this table.
2062 To create a new VCL, this object is
2063 initially set to 'createAndWait' or
2064 'createAndGo'. This object must not be
2065
2066
2067
2068 <span class="grey">Ahmed &amp; Tesink [Page 37]</span></pre>
2069 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-38" ></span>
2070 <span class="grey"><a href="./rfc1695">RFC 1695</a> ATM Management Objects August 1994</span>
2071
2072
2073 set to 'active' unless the following columnar
2074 objects exist in this row:
2075 atmVplReceiveTrafficDescrIndex and
2076 atmVplTransmitTrafficDescrIndex."
2077 DEFVAL { active }
2078 ::= {atmVplEntry 8}
2079
2080
2081 -- ATM Interface Virtual Channel Link (VCL) Group
2082
2083 -- This group contains configuration and state
2084 -- information of a bi-directional Virtual Channel
2085 -- Link (VCL) at an ATM interface.
2086
2087 -- This table can be used to create, delete or modify
2088 -- a VCL that is terminated in an ATM host or switch.
2089 -- This table can also be
2090 -- used to create, delete or modify a VCL that is
2091 -- cross-connected to another VCL.
2092
2093
2094 -- The ATM Interface VCL Table
2095
2096
2097 atmVclTable OBJECT-TYPE
2098 SYNTAX SEQUENCE OF AtmVclEntry
2099 MAX-ACCESS not-accessible
2100 STATUS current
2101 DESCRIPTION
2102 "The Virtual Channel Link (VCL) table. A
2103 bi-directional VCL is modeled as one entry
2104 in this table."
2105 ::= { atmMIBObjects 7}
2106
2107 atmVclEntry OBJECT-TYPE
2108 SYNTAX AtmVclEntry
2109 MAX-ACCESS not-accessible
2110 STATUS current
2111 DESCRIPTION
2112 "An entry in the VCL table. This entry is
2113 used to model a bi-directional VCL.
2114 To create a VCL at an ATM interface,
2115 either of the following procedures are used:
2116
2117 Negotiated VCL establishment
2118
2119 (1) The management application creates
2120 a VCL entry in the atmVclTable
2121
2122
2123
2124 <span class="grey">Ahmed &amp; Tesink [Page 38]</span></pre>
2125 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-39" ></span>
2126 <span class="grey"><a href="./rfc1695">RFC 1695</a> ATM Management Objects August 1994</span>
2127
2128
2129 by setting atmVclRowStatus to createAndWait(5).
2130 This may fail for the following reasons:
2131 - The selected VPI/VCI values are unavailable,
2132 - The selected VPI/VCI values are in use.
2133 Otherwise, the agent creates a row and
2134 reserves the VPI/VCI values on that port.
2135
2136 (2) The manager selects an existing row(s) in the
2137 atmTrafficDescrParamTable,
2138 thereby, selecting a set of self-consistent
2139 ATM traffic parameters and the QoS Class
2140 for receive and transmit directions of the VCL.
2141
2142 (2a) If no suitable row(s) in the
2143 atmTrafficDescrParamTable exists,
2144 the manager must create a new row(s)
2145 in that table.
2146
2147 (2b) The manager characterizes the VCL's traffic
2148 parameters through setting the
2149 atmVclReceiveTrafficDescrIndex and the
2150 atmVclTransmitTrafficDescrIndex values
2151 in the VCL table, which point to the rows
2152 containing desired ATM traffic parameter values
2153 in the atmTrafficDescrParamTable. The agent
2154 will check the availability of resources and
2155 may refuse the request.
2156
2157 (3) The manager activates the VCL by setting the
2158 the atmVclRowStatus to active(1).
2159 If this set is successful, the agent has
2160 reserved the resources to satisfy the requested
2161 traffic parameter values and the QoS Class
2162 for that VCL.
2163 (4) If the VCL terminates a VCC in the ATM host
2164 or switch, the manager turns on the
2165 atmVclAdminStatus to up(1) to turn the VCL
2166 traffic flow on. Otherwise, the
2167 atmVcCrossConnectTable must be used
2168 to cross-connect the VCL to another VCL(s)
2169 in an ATM switch or network.
2170
2171 One-Shot VCL Establishment
2172
2173 A VCL may also be established in one step by a
2174 set-request with all necessary VCL parameter
2175 values and atmVclRowStatus set to createAndGo(4).
2176
2177
2178
2179
2180 <span class="grey">Ahmed &amp; Tesink [Page 39]</span></pre>
2181 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-40" ></span>
2182 <span class="grey"><a href="./rfc1695">RFC 1695</a> ATM Management Objects August 1994</span>
2183
2184
2185 In contrast to the negotiated VCL establishment
2186 which allows for detailed error checking
2187 (i.e., set errors are explicitly linked to
2188 particular resource acquisition failures),
2189 the one-shot VCL establishment
2190 performs the setup on one operation but
2191 does not have the advantage of step-wise
2192 error checking.
2193
2194 VCL Retirement
2195
2196 A VCL is released by setting atmVclRowStatus to
2197 destroy(6), and the agent may release all
2198 associated resources."
2199 INDEX {ifIndex, atmVclVpi, atmVclVci }
2200 ::= { atmVclTable 1}
2201
2202 AtmVclEntry ::= SEQUENCE {
2203 atmVclVpi INTEGER,
2204 atmVclVci INTEGER,
2205 atmVclAdminStatus INTEGER,
2206 atmVclOperStatus INTEGER,
2207 atmVclLastChange TimeStamp,
2208 atmVclReceiveTrafficDescrIndex
2209 AtmTrafficDescrParamIndex,
2210 atmVclTransmitTrafficDescrIndex
2211 AtmTrafficDescrParamIndex,
2212 atmVccAalType INTEGER,
2213 atmVccAal5CpcsTransmitSduSize INTEGER,
2214 atmVccAal5CpcsReceiveSduSize INTEGER,
2215 atmVccAal5EncapsType INTEGER,
2216 atmVclCrossConnectIdentifier INTEGER,
2217 atmVclRowStatus RowStatus
2218 }
2219
2220 atmVclVpi OBJECT-TYPE
2221 SYNTAX INTEGER (0..4095)
2222 MAX-ACCESS not-accessible
2223 STATUS current
2224 DESCRIPTION
2225 "The VPI value of the VCL.
2226 The maximum VPI value cannot
2227 exceed the value allowable by the
2228 atmInterfaceMaxVpiBits."
2229 ::= { atmVclEntry 1}
2230
2231 atmVclVci OBJECT-TYPE
2232 SYNTAX INTEGER (0..65535)
2233
2234
2235
2236 <span class="grey">Ahmed &amp; Tesink [Page 40]</span></pre>
2237 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-41" ></span>
2238 <span class="grey"><a href="./rfc1695">RFC 1695</a> ATM Management Objects August 1994</span>
2239
2240
2241 MAX-ACCESS not-accessible
2242 STATUS current
2243 DESCRIPTION
2244 "The VCI value of the VCL.
2245 The maximum VCI value cannot
2246 exceed the value allowable by the
2247 atmInterfaceMaxVciBits."
2248 ::= { atmVclEntry 2}
2249
2250 atmVclAdminStatus OBJECT-TYPE
2251 SYNTAX INTEGER {
2252 up(1),
2253 down(2)
2254 }
2255 MAX-ACCESS read-create
2256 STATUS current
2257 DESCRIPTION
2258 "This object is implemented only for a VCL which
2259 terminates a VCC (i.e.,
2260 one which is NOT cross-connected to other VCLs).
2261 Its value specifies the desired administrative
2262 state of the VCL. The up and down states indicate
2263 that the traffic flow is enabled and disabled
2264 respectively for this VCL."
2265 ::= { atmVclEntry 3}
2266
2267 atmVclOperStatus OBJECT-TYPE
2268 SYNTAX INTEGER {
2269 up(1),
2270 down(2),
2271 unknown(3)
2272 }
2273 MAX-ACCESS read-only
2274 STATUS current
2275 DESCRIPTION
2276 "This object indicates the current operational
2277 status of the VCL. The up and down states
2278 indicate that the VCL is currently
2279 operational, or not operational, respectively.
2280 The unknown state indicates that the status of
2281 this VCL cannot be determined."
2282 ::= { atmVclEntry 4}
2283
2284 atmVclLastChange OBJECT-TYPE
2285 SYNTAX TimeStamp
2286 MAX-ACCESS read-only
2287 STATUS current
2288 DESCRIPTION
2289
2290
2291
2292 <span class="grey">Ahmed &amp; Tesink [Page 41]</span></pre>
2293 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-42" ></span>
2294 <span class="grey"><a href="./rfc1695">RFC 1695</a> ATM Management Objects August 1994</span>
2295
2296
2297 "The value of MIB II's sysUpTime object
2298 at the time this VCL entered its current
2299 operational state. If the current state was
2300 entered prior to the last re-initialization of the
2301 agent, then this object contains a zero value."
2302 ::= { atmVclEntry 5 }
2303
2304 atmVclReceiveTrafficDescrIndex OBJECT-TYPE
2305 SYNTAX AtmTrafficDescrParamIndex
2306 MAX-ACCESS read-create
2307 STATUS current
2308 DESCRIPTION
2309 "The value of this object identifies the row
2310 in the ATM Traffic Descriptor Table which
2311 applies to the receive direction of this VCL."
2312 ::= { atmVclEntry 6}
2313
2314 atmVclTransmitTrafficDescrIndex OBJECT-TYPE
2315 SYNTAX AtmTrafficDescrParamIndex
2316 MAX-ACCESS read-create
2317 STATUS current
2318 DESCRIPTION
2319 "The value of this object identifies the row
2320 of the ATM Traffic Descriptor Table which applies
2321 to the transmit direction of this VCL."
2322 ::= { atmVclEntry 7}
2323
2324 atmVccAalType OBJECT-TYPE
2325 SYNTAX INTEGER {
2326 aal1(1),
2327 aal34(2),
2328 aal5(3),
2329 other(4),
2330 unknown(5)
2331 }
2332 MAX-ACCESS read-create
2333 STATUS current
2334 DESCRIPTION
2335 "An instance of this object only exists when the
2336 local VCL end-point is also the VCC end-point,
2337 and AAL is in use.
2338 The type of AAL used on this VCC.
2339 The AAL type includes AAL1, AAL3/4,
2340 and AAL5. The other(4) may be user-defined
2341 AAL type. The unknown type indicates that
2342 the AAL type cannot be determined."
2343 ::= { atmVclEntry 8 }
2344
2345
2346
2347
2348 <span class="grey">Ahmed &amp; Tesink [Page 42]</span></pre>
2349 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-43" ></span>
2350 <span class="grey"><a href="./rfc1695">RFC 1695</a> ATM Management Objects August 1994</span>
2351
2352
2353 atmVccAal5CpcsTransmitSduSize OBJECT-TYPE
2354 SYNTAX INTEGER (1..65535)
2355 MAX-ACCESS read-create
2356 STATUS current
2357 DESCRIPTION
2358 "An instance of this object only exists when the
2359 local VCL end-point is also the VCC end-point,
2360 and AAL5 is in use.
2361 The maximum AAL5 CPCS SDU size in octets that is
2362 supported on the transmit direction of this VCC."
2363 DEFVAL { 9188 }
2364 ::= { atmVclEntry 9 }
2365
2366 atmVccAal5CpcsReceiveSduSize OBJECT-TYPE
2367 SYNTAX INTEGER (1..65535)
2368 MAX-ACCESS read-create
2369 STATUS current
2370 DESCRIPTION
2371 "An instance of this object only exists when the
2372 local VCL end-point is also the VCC end-point,
2373 and AAL5 is in use.
2374 The maximum AAL5 CPCS SDU size in octets that is
2375 supported on the receive direction of this VCC."
2376 DEFVAL { 9188 }
2377 ::= { atmVclEntry 10 }
2378
2379 atmVccAal5EncapsType OBJECT-TYPE
2380 SYNTAX INTEGER {
2381 vcMultiplexRoutedProtocol(1),
2382 vcMultiplexBridgedProtocol8023(2),
2383 vcMultiplexBridgedProtocol8025(3),
2384 vcMultiplexBridgedProtocol8026(4),
2385 vcMultiplexLANemulation8023(5),
2386 vcMultiplexLANemulation8025(6),
2387 llcEncapsulation(7),
2388 multiprotocolFrameRelaySscs(8),
2389 other(9),
2390 unknown(10)
2391 }
2392 MAX-ACCESS read-create
2393 STATUS current
2394 DESCRIPTION
2395 "An instance of this object only exists when the
2396 local VCL end-point is also the VCC end-point,
2397 and AAL5 is in use.
2398 The type of data encapsulation used over
2399 the AAL5 SSCS layer. The definitions reference
2400 <a href="./rfc1483">RFC 1483</a> Multiprotocol Encapsulation
2401
2402
2403
2404 <span class="grey">Ahmed &amp; Tesink [Page 43]</span></pre>
2405 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-44" ></span>
2406 <span class="grey"><a href="./rfc1695">RFC 1695</a> ATM Management Objects August 1994</span>
2407
2408
2409 over ATM AAL5 and to the ATM Forum
2410 LAN Emulation specification."
2411 DEFVAL { llcEncapsulation }
2412 ::= { atmVclEntry 11 }
2413
2414 atmVclCrossConnectIdentifier OBJECT-TYPE
2415 SYNTAX INTEGER (0..2147483647)
2416 MAX-ACCESS read-only
2417 STATUS current
2418 DESCRIPTION
2419 "This object is implemented only for a VCL
2420 which is cross-connected to other VCLs
2421 that belong to the same VCC. All such
2422 associated VCLs have the same value of this
2423 object, and all their cross-connections are
2424 identified by entries in the
2425 atmVcCrossConnectTable for which
2426 atmVcCrossConnectIndex has the same value.
2427 The value of this object is initialized by the
2428 agent after the associated entries in the
2429 atmVcCrossConnectTable have been created."
2430 ::= {atmVclEntry 12}
2431
2432 atmVclRowStatus OBJECT-TYPE
2433 SYNTAX RowStatus
2434 MAX-ACCESS read-create
2435 STATUS current
2436 DESCRIPTION
2437 "This object is used to create, delete or
2438 modify a row in this table. To create
2439 a new VCL, this object is initially set
2440 to 'createAndWait' or 'createAndGo'.
2441 This object must not be set to 'active'
2442 unless the following columnar objects exist
2443 in this row:
2444 atmVclReceiveTrafficDescrIndex,
2445 atmVclTransmitTrafficDescrIndex.
2446 In addition, if the local VCL end-point
2447 is also the VCC end-point:
2448 atmVccAalType.
2449 In addition, for AAL5 connections only:
2450 atmVccAal5CpcsTransmitSduSize,
2451 atmVccAal5CpcsReceiveSduSize, and
2452 atmVccAal5EncapsType."
2453 DEFVAL { active }
2454 ::= {atmVclEntry 13}
2455
2456
2457
2458
2459
2460 <span class="grey">Ahmed &amp; Tesink [Page 44]</span></pre>
2461 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-45" ></span>
2462 <span class="grey"><a href="./rfc1695">RFC 1695</a> ATM Management Objects August 1994</span>
2463
2464
2465 -- ATM Virtual Path (VP) Cross Connect Group
2466
2467 -- This group contains configuration and state
2468 -- information of all point-to-point,
2469 -- point-to-multipoint, or multipoint-to-multipoint
2470 -- VP cross-connects.
2471
2472 -- This table has read-create access and can be used
2473 -- to cross-connect the VPLs together in an ATM switch
2474 -- or network. The atmVpCrossConnectIndex
2475 -- is used to associate the related
2476 -- VPLs that are cross-connected together.
2477
2478 -- The ATM VP Cross Connect Group
2479 -- models each bi-directional VPC
2480 -- cross-connect as a set of entries in
2481 -- the atmVpCrossConnectTable. A
2482 -- point-to-point VPC cross-connect is modeled
2483 -- as one entry; a point-to-multipoint (N leafs) VPC
2484 -- cross-connect as N entries in this table; and
2485 -- a multipoint-to-multipoint (N parties) VPC cross-
2486 -- connect as N(N-1)/2 entries in this table.
2487 -- In the latter cases, all the N (or N(N-1)/2) entries
2488 -- are associated with a single VPC cross-connect by
2489 -- having the same value of atmVpCrossConnectIndex.
2490
2491
2492 -- _________________________________________
2493 -- | |
2494 -- Low | ATM Switch or Network | High
2495 -- port| | port
2496 -- _____|&gt;&gt; from low to high VPC traffic flow &gt;&gt;|______
2497 -- |&lt;&lt; from high to low VPC traffic flow &lt;&lt;|
2498 -- | |
2499 -- |_______________________________________|
2500 --
2501
2502 -- The terms low and high are chosen to represent
2503 -- numerical ordering of the two interfaces associated
2504 -- with a VPC cross-connect. That is, the ATM interface
2505 -- with the lower value of ifIndex is termed 'low',
2506 -- while the other ATM interface associated with the
2507 -- VPC cross-connect is termed 'high'. This terminology
2508 -- is used to provide directional information; for
2509 -- example, the atmVpCrossConnectL2HOperStatus applies
2510 -- to the low-&gt;high direction, and
2511 -- atmVpCrossConnectH2LOperStatus applies to the
2512 -- high-&gt;low direction, as illustrated above.
2513
2514
2515
2516 <span class="grey">Ahmed &amp; Tesink [Page 45]</span></pre>
2517 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-46" ></span>
2518 <span class="grey"><a href="./rfc1695">RFC 1695</a> ATM Management Objects August 1994</span>
2519
2520
2521 atmVpCrossConnectIndexNext OBJECT-TYPE
2522 SYNTAX INTEGER (0..2147483647)
2523 MAX-ACCESS read-only
2524 STATUS current
2525 DESCRIPTION
2526 "This object contains an appropriate value to
2527 be used for atmVpCrossConnectIndex when creating
2528 entries in the atmVpCrossConnectTable. The value
2529 0 indicates that no unassigned entries are
2530 available. To obtain the atmVpCrossConnectIndex
2531 value for a new entry, the manager issues a
2532 management protocol retrieval operation to obtain
2533 the current value of this object. After each
2534 retrieval, the agent should modify the value to
2535 the next unassigned index."
2536 ::= { atmMIBObjects 8 }
2537
2538
2539 -- The ATM VP Cross Connect Table
2540
2541
2542 atmVpCrossConnectTable OBJECT-TYPE
2543 SYNTAX SEQUENCE OF AtmVpCrossConnectEntry
2544 MAX-ACCESS not-accessible
2545 STATUS current
2546 DESCRIPTION
2547 "The ATM VP Cross Connect table. A bi-
2548 directional VP cross-connect which
2549 cross-connects two VPLs is modeled
2550 as one entry in this table."
2551 ::= { atmMIBObjects 9 }
2552
2553
2554 atmVpCrossConnectEntry OBJECT-TYPE
2555 SYNTAX AtmVpCrossConnectEntry
2556 MAX-ACCESS not-accessible
2557 STATUS current
2558 DESCRIPTION
2559 "An entry in the ATM VP Cross Connect table.
2560 This entry is used to model a bi-directional
2561 ATM VP cross-connect which cross-connects
2562 two VPLs.
2563
2564 Step-wise Procedures to set up a VP Cross-connect
2565
2566 Once the entries in the atmVplTable are created,
2567 the following procedures are used
2568 to cross-connect the VPLs together.
2569
2570
2571
2572 <span class="grey">Ahmed &amp; Tesink [Page 46]</span></pre>
2573 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-47" ></span>
2574 <span class="grey"><a href="./rfc1695">RFC 1695</a> ATM Management Objects August 1994</span>
2575
2576
2577 (1) The manager obtains a unique
2578 atmVpCrossConnectIndex by reading the
2579 atmVpCrossConnectIndexNext object.
2580
2581 (2) Next, the manager creates a set of one
2582 or more rows in the ATM VP Cross Connect
2583 Table, one for each cross-connection between
2584 two VPLs. Each row is indexed by the ATM
2585 interface port numbers and VPI values of the
2586 two ends of that cross-connection.
2587 This set of rows specifies the topology of the
2588 VPC cross-connect and is identified by a single
2589 value of atmVpCrossConnectIndex.
2590
2591 Negotiated VP Cross-Connect Establishment
2592
2593 (2a) The manager creates a row in this table by
2594 setting atmVpCrossConnectRowStatus to
2595 createAndWait(5). The agent checks the
2596 requested topology and the mutual sanity of
2597 the ATM traffic parameters and
2598 QoS Classes, i.e., the row creation fails if:
2599 - the requested topology is not supported
2600 by the agent,
2601 - the traffic/QoS parameter values
2602 associated with the requested row are
2603 incompatible with those of already existing
2604 rows for this VP cross-connect.
2605 [For example, for setting up
2606 a point-to-point VP cross-connect, the
2607 ATM traffic parameters in the receive direction
2608 of a VPL at the low end of the cross-connect
2609 must equal to the traffic parameters in the
2610 transmit direction of the other VPL at the
2611 high end of the cross-connect,
2612 otherwise, the row creation fails.]
2613 The agent also checks for internal errors
2614 in building the cross-connect.
2615
2616 The atmVpCrossConnectIndex values in the
2617 corresponding atmVplTable rows are filled
2618 in by the agent at this point.
2619
2620 (2b) The manager promotes the row in the
2621 atmVpCrossConnectTable by setting
2622 atmVpCrossConnectRowStatus to active(1). If
2623 this set is successful, the agent has reserved
2624 the resources specified by the ATM traffic
2625
2626
2627
2628 <span class="grey">Ahmed &amp; Tesink [Page 47]</span></pre>
2629 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-48" ></span>
2630 <span class="grey"><a href="./rfc1695">RFC 1695</a> ATM Management Objects August 1994</span>
2631
2632
2633 parameter and QoS Class values
2634 for each direction of the VP cross-connect
2635 in an ATM switch or network.
2636
2637 (3) The manager sets the
2638 atmVpCrossConnectAdminStatus to up(1) in all
2639 rows of this VP cross-connect to turn the
2640 traffic flow on.
2641
2642
2643 One-Shot VP Cross-Connect Establishment
2644
2645 A VP cross-connect may also be established in
2646 one step by a set-request with all necessary
2647 parameter values and atmVpCrossConnectRowStatus
2648 set to createAndGo(4).
2649
2650 In contrast to the negotiated VP cross-connect
2651 establishment which allows for detailed error
2652 checking (i.e., set errors are explicitly linked
2653 to particular resource acquisition failures),
2654 the one-shot VP cross-connect establishment
2655 performs the setup on one operation but does not
2656 have the advantage of step-wise error checking.
2657
2658 VP Cross-Connect Retirement
2659
2660 A VP cross-connect identified by a particular
2661 value of atmVpCrossConnectIndex is released by:
2662
2663 (1) Setting atmVpCrossConnectRowStatus of all
2664 rows identified by this value of
2665 atmVpCrossConnectIndex to destroy(6).
2666 The agent may release all
2667 associated resources, and the
2668 atmVpCrossConnectIndex values in the
2669 corresponding atmVplTable row are removed.
2670 Note that a situation when only a subset of
2671 the associated rows are deleted corresponds
2672 to a VP topology change.
2673
2674 (2) After deletion of the appropriate
2675 atmVpCrossConnectEntries, the manager may
2676 set atmVplRowStatus to destroy(6) the
2677 associated VPLs. The agent releases
2678 the resources and removes the associated
2679 rows in the atmVplTable.
2680
2681
2682
2683
2684 <span class="grey">Ahmed &amp; Tesink [Page 48]</span></pre>
2685 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-49" ></span>
2686 <span class="grey"><a href="./rfc1695">RFC 1695</a> ATM Management Objects August 1994</span>
2687
2688
2689 VP Cross-connect Reconfiguration
2690
2691 At the discretion of the agent, a VP
2692 cross-connect may be reconfigured by
2693 adding and/or deleting leafs to/from
2694 the VP topology as per the VP cross-connect
2695 establishment/retirement procedures.
2696 Reconfiguration of traffic/QoS parameter
2697 values requires release of the VP cross-connect
2698 before those parameter values may by changed
2699 for individual VPLs."
2700 INDEX { atmVpCrossConnectIndex,
2701 atmVpCrossConnectLowIfIndex,
2702 atmVpCrossConnectLowVpi,
2703 atmVpCrossConnectHighIfIndex,
2704 atmVpCrossConnectHighVpi }
2705 ::= { atmVpCrossConnectTable 1 }
2706
2707 AtmVpCrossConnectEntry ::= SEQUENCE {
2708 atmVpCrossConnectIndex INTEGER,
2709 atmVpCrossConnectLowIfIndex IfIndex,
2710 atmVpCrossConnectLowVpi INTEGER,
2711 atmVpCrossConnectHighIfIndex IfIndex,
2712 atmVpCrossConnectHighVpi INTEGER,
2713 atmVpCrossConnectAdminStatus INTEGER,
2714 atmVpCrossConnectL2HOperStatus INTEGER,
2715 atmVpCrossConnectH2LOperStatus INTEGER,
2716 atmVpCrossConnectL2HLastChange TimeStamp,
2717 atmVpCrossConnectH2LLastChange TimeStamp,
2718 atmVpCrossConnectRowStatus RowStatus
2719 }
2720
2721 atmVpCrossConnectIndex OBJECT-TYPE
2722 SYNTAX INTEGER (1..2147483647)
2723 MAX-ACCESS not-accessible
2724 STATUS current
2725 DESCRIPTION
2726 "A unique value to identify this VP cross-connect."
2727 ::= { atmVpCrossConnectEntry 1 }
2728
2729 atmVpCrossConnectLowIfIndex OBJECT-TYPE
2730 SYNTAX IfIndex
2731 MAX-ACCESS not-accessible
2732 STATUS current
2733 DESCRIPTION
2734 "The value of this object is equal to MIB II's
2735 ifIndex value of the ATM interface port for this
2736 VP cross-connect. The term low implies
2737
2738
2739
2740 <span class="grey">Ahmed &amp; Tesink [Page 49]</span></pre>
2741 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-50" ></span>
2742 <span class="grey"><a href="./rfc1695">RFC 1695</a> ATM Management Objects August 1994</span>
2743
2744
2745 that this ATM interface has the numerically lower
2746 ifIndex value than the other ATM interface
2747 identified in the same atmVpCrossConnectEntry."
2748 ::= { atmVpCrossConnectEntry 2 }
2749
2750 atmVpCrossConnectLowVpi OBJECT-TYPE
2751 SYNTAX INTEGER (1..4095)
2752 MAX-ACCESS not-accessible
2753 STATUS current
2754 DESCRIPTION
2755 "The value of this object is equal to the VPI
2756 value at the ATM interface
2757 associated with the VP cross-connect that is
2758 identified by atmVpCrossConnectLowIfIndex.
2759 The VPI value cannot exceed the number
2760 supported by the atmInterfaceMaxVpiBits
2761 at the low ATM interface port."
2762 ::= { atmVpCrossConnectEntry 3 }
2763
2764 atmVpCrossConnectHighIfIndex OBJECT-TYPE
2765 SYNTAX IfIndex
2766 MAX-ACCESS not-accessible
2767 STATUS current
2768 DESCRIPTION
2769 "The value of this object is equal to MIB II's
2770 ifIndex value of the ATM interface port for
2771 this VP cross-connect. The term high
2772 implies that this ATM interface has the
2773 numerically higher ifIndex value than the
2774 other ATM interface identified in the same
2775 atmVpCrossConnectEntry."
2776 ::= { atmVpCrossConnectEntry 4 }
2777
2778 atmVpCrossConnectHighVpi OBJECT-TYPE
2779 SYNTAX INTEGER (1..4095)
2780 MAX-ACCESS not-accessible
2781 STATUS current
2782 DESCRIPTION
2783 "The value of this object is equal to the VPI
2784 value at the ATM interface associated with
2785 the VP cross-connect that is identified
2786 by atmVpCrossConnectHighIfIndex.
2787 The VPI value cannot exceed the number
2788 supported by the atmInterfaceMaxVpiBits
2789 at the high ATM interface port."
2790 ::= { atmVpCrossConnectEntry 5 }
2791
2792 atmVpCrossConnectAdminStatus OBJECT-TYPE
2793
2794
2795
2796 <span class="grey">Ahmed &amp; Tesink [Page 50]</span></pre>
2797 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-51" ></span>
2798 <span class="grey"><a href="./rfc1695">RFC 1695</a> ATM Management Objects August 1994</span>
2799
2800
2801 SYNTAX INTEGER {
2802 up(1),
2803 down(2)
2804 }
2805 MAX-ACCESS read-create
2806 STATUS current
2807 DESCRIPTION
2808 "The value of this object identifies the desired
2809 administrative status of this bi-directional
2810 VP cross-connect. The up and down states
2811 indicate that the traffic flow is enabled
2812 and disabled respectively on this VP
2813 cross-connect."
2814 DEFVAL { down }
2815 ::= { atmVpCrossConnectEntry 6 }
2816
2817 atmVpCrossConnectL2HOperStatus OBJECT-TYPE
2818 SYNTAX INTEGER {
2819 up(1),
2820 down(2),
2821 unknown(3)
2822 }
2823 MAX-ACCESS read-only
2824 STATUS current
2825 DESCRIPTION
2826 "The value of this object identifies the current
2827 operational status of the VP cross-connect
2828 in one direction; (i.e., from the low to
2829 high direction). The up and down states indicate
2830 that this ATM VP cross-connect from low
2831 to high direction is operational or not
2832 operational respectively.
2833 The unknown state indicates that
2834 the state of it cannot be determined."
2835 ::= { atmVpCrossConnectEntry 7 }
2836
2837 atmVpCrossConnectH2LOperStatus OBJECT-TYPE
2838 SYNTAX INTEGER {
2839 up(1),
2840 down(2),
2841 unknown(3)
2842 }
2843 MAX-ACCESS read-only
2844 STATUS current
2845 DESCRIPTION
2846 "The value of this object identifies the current
2847 operational status of the VP cross-connect
2848 in one direction; (i.e., from the high to
2849
2850
2851
2852 <span class="grey">Ahmed &amp; Tesink [Page 51]</span></pre>
2853 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-52" ></span>
2854 <span class="grey"><a href="./rfc1695">RFC 1695</a> ATM Management Objects August 1994</span>
2855
2856
2857 low direction). The up and down states indicate
2858 that this ATM VP cross-connect from high
2859 to low direction is operational or not
2860 operational respectively. The
2861 unknown state indicates that the state
2862 of it cannot be determined."
2863 ::= { atmVpCrossConnectEntry 8 }
2864
2865 atmVpCrossConnectL2HLastChange OBJECT-TYPE
2866 SYNTAX TimeStamp
2867 MAX-ACCESS read-only
2868 STATUS current
2869 DESCRIPTION
2870 "The value of MIB II's sysUpTime object
2871 at the time this VP cross-connect entered
2872 its current operational state in the low to
2873 high direction. If the current state was
2874 entered prior to the last re-initialization of the
2875 agent, then this object contains a zero value."
2876 ::= { atmVpCrossConnectEntry 9 }
2877
2878 atmVpCrossConnectH2LLastChange OBJECT-TYPE
2879 SYNTAX TimeStamp
2880 MAX-ACCESS read-only
2881 STATUS current
2882 DESCRIPTION
2883 "The value of MIB II's sysUpTime object at the
2884 time this VP cross-connect entered its current
2885 operational state in the high to low direction.
2886 If the current state was entered prior to the
2887 last re-initialization of the agent,
2888 then this object contains a zero value."
2889 ::= { atmVpCrossConnectEntry 10 }
2890
2891 atmVpCrossConnectRowStatus OBJECT-TYPE
2892 SYNTAX RowStatus
2893 MAX-ACCESS read-create
2894 STATUS current
2895 DESCRIPTION
2896 "The status of this entry in the
2897 atmVpCrossConnectTable. This object is used to
2898 create a cross-connect for cross-connecting
2899 VPLs which are created using the atmVplTable
2900 or to change or delete an existing cross-connect.
2901 This object must be initially set
2902 to `createAndWait' or 'createAndGo'.
2903 This object cannot be set to `active'
2904 unless the following columnar object exists
2905
2906
2907
2908 <span class="grey">Ahmed &amp; Tesink [Page 52]</span></pre>
2909 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-53" ></span>
2910 <span class="grey"><a href="./rfc1695">RFC 1695</a> ATM Management Objects August 1994</span>
2911
2912
2913 in this row: atmVpCrossConnectAdminStatus.
2914 To turn on a VP cross-connect,
2915 the atmVpCrossConnectAdminStatus
2916 is set to `up'."
2917 DEFVAL { active }
2918 ::= { atmVpCrossConnectEntry 11 }
2919
2920
2921 -- ATM Virtual Channel (VC) Cross Connect Group
2922
2923 -- This group contains configuration and state
2924 -- information of a bi-directional VC cross-connect.
2925
2926 -- This group is used to model a bi-directional
2927 -- point-to-point, point-to-multipoint or
2928 -- multipoint-to-multipoint VC cross-connects.
2929
2930 -- This table has read-create access and is used
2931 -- to cross-connect the VCLs together in an ATM switch
2932 -- or network that belong to a VC connection.
2933 -- The atmVcCrossConnectIndex is used to associate
2934 -- the related VCLs that are cross-connected together.
2935
2936
2937 -- The step-wise procedures described for setting
2938 -- up a VP cross-connect are also used for setting up
2939 -- a VC cross-connect.
2940
2941
2942 atmVcCrossConnectIndexNext OBJECT-TYPE
2943 SYNTAX INTEGER (0..2147483647)
2944 MAX-ACCESS read-only
2945 STATUS current
2946 DESCRIPTION
2947 "This object contains an appropriate value to
2948 be used for atmVcCrossConnectIndex when creating
2949 entries in the atmVcCrossConnectTable. The value
2950 0 indicates that no unassigned entries are
2951 available. To obtain the atmVpCrossConnectIndex
2952 value for a new entry, the manager issues a
2953 management protocol retrieval operation to obtain
2954 the current value of this object. After each
2955 retrieval, the agent should modify the value to
2956 the next unassigned index."
2957 ::= { atmMIBObjects 10 }
2958
2959
2960 -- The ATM VC Cross Connect Table
2961
2962
2963
2964 <span class="grey">Ahmed &amp; Tesink [Page 53]</span></pre>
2965 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-54" ></span>
2966 <span class="grey"><a href="./rfc1695">RFC 1695</a> ATM Management Objects August 1994</span>
2967
2968
2969 atmVcCrossConnectTable OBJECT-TYPE
2970 SYNTAX SEQUENCE OF AtmVcCrossConnectEntry
2971 MAX-ACCESS not-accessible
2972 STATUS current
2973 DESCRIPTION
2974 "The ATM VC Cross Connect table. A bi-
2975 directional VC cross-connect which
2976 cross-connects two end points (i.e., VCLs)
2977 is modeled as one entry in this table."
2978 ::= { atmMIBObjects 11 }
2979
2980
2981 atmVcCrossConnectEntry OBJECT-TYPE
2982 SYNTAX AtmVcCrossConnectEntry
2983 MAX-ACCESS not-accessible
2984 STATUS current
2985 DESCRIPTION
2986 "An entry in the ATM VC Cross Connect table.
2987 This entry is used to model a bi-directional ATM
2988 VC cross-connect cross-connecting two end points.
2989
2990 Step-wise Procedures to set up a VC Cross-connect
2991
2992 Once the entries in the atmVclTable are created,
2993 the following procedures are used
2994 to cross-connect the VCLs together to
2995 form a VCC segment.
2996
2997 (1) The manager obtains a unique
2998 atmVcCrossConnectIndex by reading the
2999 atmVcCrossConnectIndexNext object.
3000
3001 (2) Next, the manager creates a set of one
3002 or more rows in the ATM VC Cross Connect
3003 Table, one for each cross-connection between
3004 two VCLs. Each row is indexed by the ATM
3005 interface port numbers and VPI/VCI values of
3006 the two ends of that cross-connection.
3007 This set of rows specifies the topology of the
3008 VCC cross-connect and is identified by a single
3009 value of atmVcCrossConnectIndex.
3010
3011 Negotiated VC Cross-Connect Establishment
3012
3013 (2a) The manager creates a row in this table by
3014 setting atmVcCrossConnectRowStatus to
3015 createAndWait(5). The agent checks the
3016 requested topology and the mutual sanity of
3017
3018
3019
3020 <span class="grey">Ahmed &amp; Tesink [Page 54]</span></pre>
3021 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-55" ></span>
3022 <span class="grey"><a href="./rfc1695">RFC 1695</a> ATM Management Objects August 1994</span>
3023
3024
3025 the ATM traffic parameters and
3026 QoS Classes, i.e., the row creation fails if:
3027 - the requested topology is not supported
3028 by the agent,
3029 - the traffic/QoS parameter values
3030 associated with the requested row are
3031 incompatible with those of already existing
3032 rows for this VC cross-connect.
3033 [For example, for setting up
3034 a point-to-point VC cross-connect, the
3035 ATM traffic parameters in the receive direction
3036 of a VCL at the low end of the cross-connect
3037 must equal to the traffic parameters in the
3038 transmit direction of the other VCL at the
3039 high end of the cross-connect,
3040 otherwise, the row creation fails.]
3041 The agent also checks for internal errors
3042 in building the cross-connect.
3043
3044 The atmVcCrossConnectIndex values in the
3045 corresponding atmVclTable rows are filled
3046 in by the agent at this point.
3047
3048 (2b) The manager promotes the row in the
3049 atmVcCrossConnectTable by setting
3050 atmVcCrossConnectRowStatus to active(1). If
3051 this set is successful, the agent has reserved
3052 the resources specified by the ATM traffic
3053 parameter and QoS Class values
3054 for each direction of the VC cross-connect
3055 in an ATM switch or network.
3056
3057 (3) The manager sets the
3058 atmVcCrossConnectAdminStatus to up(1)
3059 in all rows of this VC cross-connect to
3060 turn the traffic flow on.
3061
3062
3063 One-Shot VC Cross-Connect Establishment
3064
3065 A VC cross-connect may also be established in
3066 one step by a set-request with all necessary
3067 parameter values and atmVcCrossConnectRowStatus
3068 set to createAndGo(4).
3069
3070 In contrast to the negotiated VC cross-connect
3071 establishment which allows for detailed error
3072 checking i.e., set errors are explicitly linked to
3073
3074
3075
3076 <span class="grey">Ahmed &amp; Tesink [Page 55]</span></pre>
3077 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-56" ></span>
3078 <span class="grey"><a href="./rfc1695">RFC 1695</a> ATM Management Objects August 1994</span>
3079
3080
3081 particular resource acquisition failures), the
3082 one-shot VC cross-connect establishment
3083 performs the setup on one operation but does
3084 not have the advantage of step-wise error
3085 checking.
3086
3087 VC Cross-Connect Retirement
3088
3089 A VC cross-connect identified by a particular
3090 value of atmVcCrossConnectIndex is released by:
3091
3092 (1) Setting atmVcCrossConnectRowStatus of all rows
3093 identified by this value of
3094 atmVcCrossConnectIndex to destroy(6).
3095 The agent may release all
3096 associated resources, and the
3097 atmVcCrossConnectIndex values in the
3098 corresponding atmVclTable row are removed.
3099 Note that a situation when only a subset of
3100 the associated rows are deleted corresponds
3101 to a VC topology change.
3102
3103 (2) After deletion of the appropriate
3104 atmVcCrossConnectEntries, the manager may
3105 set atmVclRowStatus to destroy(6) the
3106 associated VCLs. The agent releases
3107 the resources and removes the associated
3108 rows in the atmVclTable.
3109
3110 VC Cross-Connect Reconfiguration
3111
3112 At the discretion of the agent, a VC
3113 cross-connect may be reconfigured by
3114 adding and/or deleting leafs to/from
3115 the VC topology as per the VC cross-connect
3116 establishment/retirement procedures.
3117 Reconfiguration of traffic/QoS parameter
3118 values requires release of the VC cross-connect
3119 before those parameter values may by changed
3120 for individual VCLs."
3121 INDEX { atmVcCrossConnectIndex,
3122 atmVcCrossConnectLowIfIndex,
3123 atmVcCrossConnectLowVpi,
3124 atmVcCrossConnectLowVci,
3125 atmVcCrossConnectHighIfIndex,
3126 atmVcCrossConnectHighVpi,
3127 atmVcCrossConnectHighVci }
3128 ::= { atmVcCrossConnectTable 1 }
3129
3130
3131
3132 <span class="grey">Ahmed &amp; Tesink [Page 56]</span></pre>
3133 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-57" ></span>
3134 <span class="grey"><a href="./rfc1695">RFC 1695</a> ATM Management Objects August 1994</span>
3135
3136
3137 AtmVcCrossConnectEntry ::= SEQUENCE {
3138 atmVcCrossConnectIndex INTEGER,
3139 atmVcCrossConnectLowIfIndex IfIndex,
3140 atmVcCrossConnectLowVpi INTEGER,
3141 atmVcCrossConnectLowVci INTEGER,
3142 atmVcCrossConnectHighIfIndex IfIndex,
3143 atmVcCrossConnectHighVpi INTEGER,
3144 atmVcCrossConnectHighVci INTEGER,
3145 atmVcCrossConnectAdminStatus INTEGER,
3146 atmVcCrossConnectL2HOperStatus INTEGER,
3147 atmVcCrossConnectH2LOperStatus INTEGER,
3148 atmVcCrossConnectL2HLastChange TimeStamp,
3149 atmVcCrossConnectH2LLastChange TimeStamp,
3150 atmVcCrossConnectRowStatus RowStatus
3151 }
3152
3153 atmVcCrossConnectIndex OBJECT-TYPE
3154 SYNTAX INTEGER (1..2147483647)
3155 MAX-ACCESS not-accessible
3156 STATUS current
3157 DESCRIPTION
3158 "A unique value to identify this VC cross-connect."
3159 ::= { atmVcCrossConnectEntry 1 }
3160
3161 atmVcCrossConnectLowIfIndex OBJECT-TYPE
3162 SYNTAX IfIndex
3163 MAX-ACCESS not-accessible
3164 STATUS current
3165 DESCRIPTION
3166 "The value of this object is equal to MIB II's
3167 ifIndex value of the ATM interface port for this
3168 VC cross-connect. The term low implies
3169 that this ATM interface has the numerically lower
3170 ifIndex value than the other ATM interface
3171 identified in the same atmVcCrossConnectEntry."
3172 ::= { atmVcCrossConnectEntry 2 }
3173
3174 atmVcCrossConnectLowVpi OBJECT-TYPE
3175 SYNTAX INTEGER (0..4095)
3176 MAX-ACCESS not-accessible
3177 STATUS current
3178 DESCRIPTION
3179 "The value of this object is equal to the VPI
3180 value at the ATM interface
3181 associated with the VC cross-connect that is
3182 identified by atmVcCrossConnectLowIfIndex.
3183 The VPI value cannot exceed the number
3184 supported by the atmInterfaceMaxVpiBits
3185
3186
3187
3188 <span class="grey">Ahmed &amp; Tesink [Page 57]</span></pre>
3189 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-58" ></span>
3190 <span class="grey"><a href="./rfc1695">RFC 1695</a> ATM Management Objects August 1994</span>
3191
3192
3193 at the low ATM interface port."
3194 ::= { atmVcCrossConnectEntry 3 }
3195
3196 atmVcCrossConnectLowVci OBJECT-TYPE
3197 SYNTAX INTEGER (0..65535)
3198 MAX-ACCESS not-accessible
3199 STATUS current
3200 DESCRIPTION
3201 "The value of this object is equal to the VCI
3202 value at the ATM interface
3203 associated with this VC cross-connect that is
3204 identified by atmVcCrossConnectLowIfIndex.
3205 The VCI value cannot exceed the number
3206 supported by the atmInterfaceMaxVciBits
3207 at the low ATM interface port."
3208 ::= { atmVcCrossConnectEntry 4 }
3209
3210 atmVcCrossConnectHighIfIndex OBJECT-TYPE
3211 SYNTAX IfIndex
3212 MAX-ACCESS not-accessible
3213 STATUS current
3214 DESCRIPTION
3215 "The value of this object is equal to MIB II's
3216 ifIndex value for the ATM interface port for
3217 this VC cross-connect. The term high
3218 implies that this VC cross-connect
3219 that this ATM interface has the numerically higher
3220 ifIndex value than the other ATM interface
3221 identified in the same atmVcCrossConnectEntry."
3222 ::= { atmVcCrossConnectEntry 5 }
3223
3224 atmVcCrossConnectHighVpi OBJECT-TYPE
3225 SYNTAX INTEGER (0..4095)
3226 MAX-ACCESS not-accessible
3227 STATUS current
3228 DESCRIPTION
3229 "The value of this object is equal to the VPI
3230 value at the ATM interface
3231 associated with the VC cross-connect that is
3232 identified by atmVcCrossConnectHighIfIndex.
3233 The VPI value cannot exceed
3234 the number supported by the atmInterfaceMaxVpiBits
3235 at the high ATM interface port."
3236 ::= { atmVcCrossConnectEntry 6 }
3237
3238 atmVcCrossConnectHighVci OBJECT-TYPE
3239 SYNTAX INTEGER (0..65535)
3240 MAX-ACCESS not-accessible
3241
3242
3243
3244 <span class="grey">Ahmed &amp; Tesink [Page 58]</span></pre>
3245 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-59" ></span>
3246 <span class="grey"><a href="./rfc1695">RFC 1695</a> ATM Management Objects August 1994</span>
3247
3248
3249 STATUS current
3250 DESCRIPTION
3251 "The value of this object is equal to the VCI
3252 value at the ATM interface
3253 associated with the VC cross-connect that is
3254 identified by atmVcCrossConnectHighIfIndex.
3255 The VCI value cannot exceed
3256 the number supported by the atmInterfaceMaxVciBits
3257 at the high ATM interface port."
3258 ::= { atmVcCrossConnectEntry 7 }
3259
3260 atmVcCrossConnectAdminStatus OBJECT-TYPE
3261 SYNTAX INTEGER {
3262 up(1),
3263 down(2)
3264 }
3265 MAX-ACCESS read-create
3266 STATUS current
3267 DESCRIPTION
3268 "The value of this object identifies the desired
3269 administrative status of this bi-directional
3270 VC cross-connect. The up and down states
3271 indicate that the traffic flow is enabled or
3272 disabled respectively on this VC cross-connect."
3273 DEFVAL { down }
3274 ::= { atmVcCrossConnectEntry 8 }
3275
3276 atmVcCrossConnectL2HOperStatus OBJECT-TYPE
3277 SYNTAX INTEGER {
3278 up(1),
3279 down(2),
3280 unknown(3)
3281 }
3282 MAX-ACCESS read-only
3283 STATUS current
3284 DESCRIPTION
3285 "The value of this object identifies the current
3286 operational status of the VC cross-connect
3287 in one direction; (i.e., from the low to
3288 high direction). The up and down states indicate
3289 that this ATM VC cross-connect from low
3290 to high direction is operational or not
3291 operational respectively. The unknown state
3292 indicates that the state of it cannot be
3293 determined."
3294 ::= { atmVcCrossConnectEntry 9 }
3295
3296
3297
3298
3299
3300 <span class="grey">Ahmed &amp; Tesink [Page 59]</span></pre>
3301 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-60" ></span>
3302 <span class="grey"><a href="./rfc1695">RFC 1695</a> ATM Management Objects August 1994</span>
3303
3304
3305 atmVcCrossConnectH2LOperStatus OBJECT-TYPE
3306 SYNTAX INTEGER {
3307 up(1),
3308 down(2),
3309 unknown(3)
3310 }
3311 MAX-ACCESS read-only
3312 STATUS current
3313 DESCRIPTION
3314 "The value of this object identifies the current
3315 operational status of the VC cross-connect
3316 in one direction; (i.e., from the high to
3317 low direction). The up and down states indicate
3318 that this ATM VC cross-connect from high
3319 to low direction is operational or not
3320 operational respectively. The unknown state
3321 indicates that the state of it cannot be
3322 determined."
3323 ::= { atmVcCrossConnectEntry 10 }
3324
3325 atmVcCrossConnectL2HLastChange OBJECT-TYPE
3326 SYNTAX TimeStamp
3327 MAX-ACCESS read-only
3328 STATUS current
3329 DESCRIPTION
3330 "The value of MIB II's sysUpTime object
3331 at the time this VC cross-connect entered
3332 its current operational state in low to high
3333 direction. If the current state was
3334 entered prior to the last re-initialization of the
3335 agent, then this object contains a zero value."
3336 ::= { atmVcCrossConnectEntry 11 }
3337
3338 atmVcCrossConnectH2LLastChange OBJECT-TYPE
3339 SYNTAX TimeStamp
3340 MAX-ACCESS read-only
3341 STATUS current
3342 DESCRIPTION
3343 "The value of MIB II's sysUpTime object
3344 at the time this VC cross-connect entered
3345 its current operational state in high to low
3346 direction. If the current state was
3347 entered prior to the last re-initialization of the
3348 agent, then this object contains a zero value."
3349 ::= { atmVcCrossConnectEntry 12 }
3350
3351 atmVcCrossConnectRowStatus OBJECT-TYPE
3352 SYNTAX RowStatus
3353
3354
3355
3356 <span class="grey">Ahmed &amp; Tesink [Page 60]</span></pre>
3357 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-61" ></span>
3358 <span class="grey"><a href="./rfc1695">RFC 1695</a> ATM Management Objects August 1994</span>
3359
3360
3361 MAX-ACCESS read-create
3362 STATUS current
3363 DESCRIPTION
3364 "The status of this entry in the
3365 atmVcCrossConnectTable. This object is used to
3366 create a new cross-connect for cross-connecting
3367 VCLs which are created using the atmVclTable
3368 or to change or delete existing cross-connect.
3369 This object must be initially set to
3370 `createAndWait' or 'createAndGo'. This object
3371 cannot be set to `active' unless the following
3372 columnar object exists in this row:
3373 atmVcCrossConnectAdminStatus.
3374 To turn on a VC cross-connect,
3375 the atmVcCrossConnectAdminStatus
3376 is set to `up'."
3377 ::= { atmVcCrossConnectEntry 13 }
3378
3379
3380 -- AAL5 Virtual Channel Connection Performance Statistics
3381 -- Group
3382
3383 -- This group contains the AAL5
3384 -- performance statistics of a VCC at the
3385 -- interface associated with an AAL5 entity in an ATM
3386 -- host or ATM switch.
3387
3388
3389 aal5VccTable OBJECT-TYPE
3390 SYNTAX SEQUENCE OF Aal5VccEntry
3391 MAX-ACCESS not-accessible
3392 STATUS current
3393 DESCRIPTION
3394 "This table contains AAL5 VCC performance
3395 parameters."
3396 ::= { atmMIBObjects 12 }
3397
3398 aal5VccEntry OBJECT-TYPE
3399 SYNTAX Aal5VccEntry
3400 MAX-ACCESS not-accessible
3401 STATUS current
3402 DESCRIPTION
3403 "This list contains the AAL5 VCC
3404 performance parameters."
3405 INDEX { ifIndex, aal5VccVpi, aal5VccVci }
3406 ::= { aal5VccTable 1 }
3407
3408 Aal5VccEntry ::= SEQUENCE {
3409
3410
3411
3412 <span class="grey">Ahmed &amp; Tesink [Page 61]</span></pre>
3413 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-62" ></span>
3414 <span class="grey"><a href="./rfc1695">RFC 1695</a> ATM Management Objects August 1994</span>
3415
3416
3417 aal5VccVpi INTEGER,
3418 aal5VccVci INTEGER,
3419 aal5VccCrcErrors Counter32,
3420 aal5VccSarTimeOuts Counter32,
3421 aal5VccOverSizedSDUs Counter32
3422 }
3423
3424
3425 aal5VccVpi OBJECT-TYPE
3426 SYNTAX INTEGER (0..4095)
3427 MAX-ACCESS not-accessible
3428 STATUS current
3429 DESCRIPTION
3430 "The VPI value of the AAL5 VCC at the
3431 interface identified by the ifIndex."
3432 ::= { aal5VccEntry 1 }
3433
3434 aal5VccVci OBJECT-TYPE
3435 SYNTAX INTEGER (0..65535)
3436 MAX-ACCESS not-accessible
3437 STATUS current
3438 DESCRIPTION
3439 "The VCI value of the AAL5 VCC at the
3440 interface identified by the ifIndex."
3441 ::= { aal5VccEntry 2 }
3442
3443 aal5VccCrcErrors OBJECT-TYPE
3444 SYNTAX Counter32
3445 MAX-ACCESS read-only
3446 STATUS current
3447 DESCRIPTION
3448 "The number of AAL5 CPCS PDUs received with
3449 CRC-32 errors on this AAL5 VCC at the
3450 interface associated with an AAL5 entity."
3451 ::= { aal5VccEntry 3 }
3452
3453 aal5VccSarTimeOuts OBJECT-TYPE
3454 SYNTAX Counter32
3455 MAX-ACCESS read-only
3456 STATUS current
3457 DESCRIPTION
3458 "The number of partially re-assembled AAL5
3459 CPCS PDUs which were discarded
3460 on this AAL5 VCC at the interface associated
3461 with an AAL5 entity because they
3462 were not fully re-assembled within the
3463 required time period. If the re-assembly
3464 timer is not supported, then this object
3465
3466
3467
3468 <span class="grey">Ahmed &amp; Tesink [Page 62]</span></pre>
3469 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-63" ></span>
3470 <span class="grey"><a href="./rfc1695">RFC 1695</a> ATM Management Objects August 1994</span>
3471
3472
3473 contains a zero value."
3474 ::= { aal5VccEntry 4 }
3475
3476 aal5VccOverSizedSDUs OBJECT-TYPE
3477 SYNTAX Counter32
3478 MAX-ACCESS read-only
3479 STATUS current
3480 DESCRIPTION
3481 "The number of AAL5 CPCS PDUs discarded
3482 on this AAL5 VCC at the interface
3483 associated with an AAL5 entity because the
3484 AAL5 SDUs were too large."
3485 ::= { aal5VccEntry 5 }
3486
3487
3488 -- Conformance Information
3489
3490 atmMIBConformance OBJECT IDENTIFIER ::= { atmMIB 2 }
3491
3492 atmMIBGroups OBJECT IDENTIFIER
3493 ::= { atmMIBConformance 1 }
3494 atmMIBCompliances OBJECT IDENTIFIER
3495 ::= { atmMIBConformance 2 }
3496
3497
3498 -- Compliance Statements
3499
3500 atmMIBCompliance MODULE-COMPLIANCE
3501 STATUS current
3502 DESCRIPTION
3503 "The compliance statement for SNMP entities
3504 including networks which have ATM and
3505 AAL5 interfaces."
3506
3507 MODULE -- this module
3508 MANDATORY-GROUPS {atmInterfaceConfGroup,
3509 atmTrafficDescrGroup}
3510
3511 OBJECT atmInterfaceMaxVpcs
3512 MIN-ACCESS read-only
3513 DESCRIPTION
3514 "Write access is not required."
3515
3516 OBJECT atmInterfaceMaxVccs
3517 MIN-ACCESS read-only
3518 DESCRIPTION
3519 "Write access is not required."
3520
3521
3522
3523
3524 <span class="grey">Ahmed &amp; Tesink [Page 63]</span></pre>
3525 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-64" ></span>
3526 <span class="grey"><a href="./rfc1695">RFC 1695</a> ATM Management Objects August 1994</span>
3527
3528
3529 OBJECT atmInterfaceMaxActiveVpiBits
3530 MIN-ACCESS read-only
3531 DESCRIPTION
3532 "Write access is not required."
3533
3534 OBJECT atmInterfaceMaxActiveVciBits
3535 MIN-ACCESS read-only
3536 DESCRIPTION
3537 "Write access is not required."
3538
3539 OBJECT atmInterfaceIlmiVpi
3540 MIN-ACCESS read-only
3541 DESCRIPTION
3542 "Write access is not required."
3543
3544 OBJECT atmInterfaceIlmiVci
3545 MIN-ACCESS read-only
3546 DESCRIPTION
3547 "Write access is not required."
3548
3549 OBJECT atmInterfaceMyNeighborIpAddress
3550 MIN-ACCESS read-only
3551 DESCRIPTION
3552 "Write access is not required."
3553
3554 OBJECT atmInterfaceMyNeighborIfName
3555 MIN-ACCESS read-only
3556 DESCRIPTION
3557 "Write access is not required."
3558
3559 OBJECT atmTrafficDescrType
3560 MIN-ACCESS read-only
3561 DESCRIPTION
3562 "Write access is not required."
3563
3564 OBJECT atmTrafficDescrParam1
3565 MIN-ACCESS read-only
3566 DESCRIPTION
3567 "Write access is not required."
3568
3569 OBJECT atmTrafficDescrParam2
3570 MIN-ACCESS read-only
3571 DESCRIPTION
3572 "Write access is not required."
3573
3574 OBJECT atmTrafficDescrParam3
3575 MIN-ACCESS read-only
3576 DESCRIPTION
3577
3578
3579
3580 <span class="grey">Ahmed &amp; Tesink [Page 64]</span></pre>
3581 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-65" ></span>
3582 <span class="grey"><a href="./rfc1695">RFC 1695</a> ATM Management Objects August 1994</span>
3583
3584
3585 "Write access is not required."
3586
3587 OBJECT atmTrafficDescrParam4
3588 MIN-ACCESS read-only
3589 DESCRIPTION
3590 "Write access is not required."
3591
3592 OBJECT atmTrafficDescrParam5
3593 MIN-ACCESS read-only
3594 DESCRIPTION
3595 "Write access is not required."
3596
3597 OBJECT atmTrafficQoSClass
3598 MIN-ACCESS read-only
3599 DESCRIPTION
3600 "Write access is not required."
3601
3602 OBJECT atmTrafficDescrRowStatus
3603 SYNTAX INTEGER {active(1)}
3604 -- subset of RowStatus
3605 MIN-ACCESS read-only
3606 DESCRIPTION
3607 "Write access is not required, and only one
3608 of the six enumerated values for the
3609 RowStatus textual convention need be
3610 supported, specifically: active(1)."
3611
3612 GROUP atmInterfaceDs3PlcpGroup
3613 DESCRIPTION
3614 "This group is mandatory only for those
3615 ATM interfaces which implement the
3616 DS3 PLCP layer."
3617
3618 GROUP atmInterfaceTCGroup
3619 DESCRIPTION
3620 "This group is mandatory only for those
3621 ATM interfaces which implement the
3622 TC Sublayer."
3623
3624 GROUP atmVpcTerminationGroup
3625 DESCRIPTION
3626 "This group is mandatory only for those
3627 ATM interfaces which implement ATM
3628 VPLs that terminate VPCs (i.e., ones which
3629 are NOT cross-connected to other VPLs)."
3630
3631 GROUP atmVpCrossConnectGroup
3632 DESCRIPTION
3633
3634
3635
3636 <span class="grey">Ahmed &amp; Tesink [Page 65]</span></pre>
3637 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-66" ></span>
3638 <span class="grey"><a href="./rfc1695">RFC 1695</a> ATM Management Objects August 1994</span>
3639
3640
3641 "This group is mandatory only for those
3642 ATM interfaces which implement ATM
3643 VPLs that are not associated with VCLs
3644 and are cross-connected to other VPLs."
3645
3646 OBJECT atmVplVpi
3647 SYNTAX INTEGER (1..255)
3648 DESCRIPTION
3649 "For ATM UNIs supporting VPCs, the VPI value
3650 ranges from 1 to 255."
3651
3652 OBJECT atmVplAdminStatus
3653 MIN-ACCESS read-only
3654 DESCRIPTION
3655 "Write access is not required."
3656
3657 OBJECT atmVplReceiveTrafficDescrIndex
3658 MIN-ACCESS read-only
3659 DESCRIPTION
3660 "Write access is not required."
3661
3662 OBJECT atmVplTransmitTrafficDescrIndex
3663 MIN-ACCESS read-only
3664 DESCRIPTION
3665 "Write access is not required."
3666
3667 OBJECT atmVplRowStatus
3668 SYNTAX INTEGER {active(1)}
3669 -- subset of RowStatus
3670 MIN-ACCESS read-only
3671 DESCRIPTION
3672 "Write access is not required, and only one
3673 of the six enumerated values for the
3674 RowStatus textual convention need be
3675 supported, specifically: active(1)."
3676
3677 OBJECT atmVpCrossConnectLowVpi
3678 SYNTAX INTEGER (1..255)
3679 DESCRIPTION
3680 "For ATM UNIs supporting VPCs, the VPI value
3681 at the numerically lower ATM interface port
3682 index number ranges from 1 to 255."
3683
3684 OBJECT atmVpCrossConnectHighVpi
3685 SYNTAX INTEGER (1..255)
3686 DESCRIPTION
3687 "For ATM UNIs supporting VPCs, the VPI value
3688 at the numerically higher ATM interface port
3689
3690
3691
3692 <span class="grey">Ahmed &amp; Tesink [Page 66]</span></pre>
3693 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-67" ></span>
3694 <span class="grey"><a href="./rfc1695">RFC 1695</a> ATM Management Objects August 1994</span>
3695
3696
3697 index number ranges from 1 to 255."
3698
3699 OBJECT atmVpCrossConnectAdminStatus
3700 MIN-ACCESS read-only
3701 DESCRIPTION
3702 "Write access is not required."
3703
3704 OBJECT atmVpCrossConnectRowStatus
3705 SYNTAX INTEGER {active(1)}
3706 -- subset of RowStatus
3707 MIN-ACCESS read-only
3708 DESCRIPTION
3709 "Write access is not required, and only one
3710 of the six enumerated values for the
3711 RowStatus textual convention need be
3712 supported, specifically: active(1)."
3713
3714 GROUP atmVccTerminationGroup
3715 DESCRIPTION
3716 "This group is mandatory only for those
3717 ATM interfaces which implement ATM
3718 VCLs that terminate VCCs (i.e., ones which
3719 are NOT cross-connected to other VCLs)."
3720
3721 GROUP atmVcCrossConnectGroup
3722 DESCRIPTION
3723 "This group is mandatory only for those
3724 ATM interfaces which implement ATM
3725 VCLs that are cross-connected to
3726 other VCLs."
3727
3728 OBJECT atmVclVpi
3729 SYNTAX INTEGER (0..255)
3730 DESCRIPTION
3731 "For ATM UNIs supporting VCCs, the VPI value
3732 ranges from 0 to 255."
3733
3734 OBJECT atmVclAdminStatus
3735 MIN-ACCESS read-only
3736 DESCRIPTION
3737 "Write access is not required."
3738
3739 OBJECT atmVclReceiveTrafficDescrIndex
3740 MIN-ACCESS read-only
3741 DESCRIPTION
3742 "Write access is not required."
3743
3744 OBJECT atmVclTransmitTrafficDescrIndex
3745
3746
3747
3748 <span class="grey">Ahmed &amp; Tesink [Page 67]</span></pre>
3749 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-68" ></span>
3750 <span class="grey"><a href="./rfc1695">RFC 1695</a> ATM Management Objects August 1994</span>
3751
3752
3753 MIN-ACCESS read-only
3754 DESCRIPTION
3755 "Write access is not required."
3756
3757 OBJECT atmVccAalType
3758 MIN-ACCESS read-only
3759 DESCRIPTION
3760 "Write access is not required."
3761
3762 OBJECT atmVclRowStatus
3763 SYNTAX INTEGER {active(1)}
3764 -- subset of RowStatus
3765 MIN-ACCESS read-only
3766 DESCRIPTION
3767 "Write access is not required, and only one
3768 of the six enumerated values for the
3769 RowStatus textual convention need be
3770 supported, specifically: active(1)."
3771
3772 OBJECT atmVcCrossConnectLowVpi
3773 SYNTAX INTEGER (0..255)
3774 DESCRIPTION
3775 "For ATM UNIs supporting VCCs, the VPI value
3776 at the numerically lower ATM interface port
3777 index number ranges from 0 to 255."
3778
3779 OBJECT atmVcCrossConnectHighVpi
3780 SYNTAX INTEGER (0..255)
3781 DESCRIPTION
3782 "For ATM UNIs supporting VCCs, the VPI value
3783 at the numerically higher ATM interface port
3784 index number ranges from 0 to 255."
3785
3786 OBJECT atmVcCrossConnectAdminStatus
3787 MIN-ACCESS read-only
3788 DESCRIPTION
3789 "Write access is not required."
3790
3791 OBJECT atmVcCrossConnectRowStatus
3792 SYNTAX INTEGER { active(1)}
3793 -- subset of RowStatus
3794 MIN-ACCESS read-only
3795 DESCRIPTION
3796 "Write access is not required, and only one
3797 of the six enumerated values for the
3798 RowStatus textual convention need be
3799 supported, specifically: active(1)."
3800
3801
3802
3803
3804 <span class="grey">Ahmed &amp; Tesink [Page 68]</span></pre>
3805 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-69" ></span>
3806 <span class="grey"><a href="./rfc1695">RFC 1695</a> ATM Management Objects August 1994</span>
3807
3808
3809 GROUP aal5VccGroup
3810 DESCRIPTION
3811 "This group is mandatory for the
3812 AAL5 virtual connections only."
3813
3814 OBJECT aal5VccVpi
3815 SYNTAX INTEGER (0..255)
3816 DESCRIPTION
3817 "For ATM UNIs supporting AAL5 VCCs,
3818 the VPI value ranges from 0 to 255."
3819
3820 OBJECT atmVccAal5CpcsTransmitSduSize
3821 MIN-ACCESS read-only
3822 DESCRIPTION
3823 "Write access is not required."
3824
3825 OBJECT atmVccAal5CpcsReceiveSduSize
3826 MIN-ACCESS read-only
3827 DESCRIPTION
3828 "Write access is not required."
3829
3830 OBJECT atmVccAal5EncapsType
3831 MIN-ACCESS read-only
3832 DESCRIPTION
3833 "Write access is not required."
3834 ::= { atmMIBCompliances 1 }
3835
3836
3837 -- Units of Conformance
3838
3839 atmInterfaceConfGroup OBJECT-GROUP
3840 OBJECTS {
3841 atmInterfaceMaxVpcs, atmInterfaceMaxVccs,
3842 atmInterfaceConfVpcs, atmInterfaceConfVccs,
3843 atmInterfaceMaxActiveVpiBits,
3844 atmInterfaceMaxActiveVciBits,
3845 atmInterfaceIlmiVpi,
3846 atmInterfaceIlmiVci,
3847 atmInterfaceAddressType,
3848 atmInterfaceAdminAddress,
3849 atmInterfaceMyNeighborIpAddress,
3850 atmInterfaceMyNeighborIfName}
3851 STATUS current
3852 DESCRIPTION
3853 "A collection of objects providing configuration
3854 information about an ATM interface."
3855 ::= { atmMIBGroups 1 }
3856
3857
3858
3859
3860 <span class="grey">Ahmed &amp; Tesink [Page 69]</span></pre>
3861 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-70" ></span>
3862 <span class="grey"><a href="./rfc1695">RFC 1695</a> ATM Management Objects August 1994</span>
3863
3864
3865 atmTrafficDescrGroup OBJECT-GROUP
3866 OBJECTS {
3867 atmTrafficDescrType, atmTrafficDescrParam1,
3868 atmTrafficDescrParam2, atmTrafficDescrParam3,
3869 atmTrafficDescrParam4, atmTrafficDescrParam5,
3870 atmTrafficQoSClass, atmTrafficDescrRowStatus}
3871 STATUS current
3872 DESCRIPTION
3873 "A collection of objects providing information
3874 about ATM traffic descriptor type and
3875 the associated parameters."
3876 ::= { atmMIBGroups 2 }
3877
3878 atmInterfaceDs3PlcpGroup OBJECT-GROUP
3879 OBJECTS {atmInterfaceDs3PlcpSEFSs,
3880 atmInterfaceDs3PlcpAlarmState,
3881 atmInterfaceDs3PlcpUASs}
3882 STATUS current
3883 DESCRIPTION
3884 "A collection of objects providing information
3885 about DS3 PLCP layer at an ATM interface."
3886 ::= { atmMIBGroups 3 }
3887
3888 atmInterfaceTCGroup OBJECT-GROUP
3889 OBJECTS { atmInterfaceOCDEvents,
3890 atmInterfaceTCAlarmState }
3891 STATUS current
3892 DESCRIPTION
3893 "A collection of objects providing information
3894 about TC sublayer at an ATM interface."
3895 ::= { atmMIBGroups 4 }
3896
3897 atmVpcTerminationGroup OBJECT-GROUP
3898 OBJECTS {atmVplOperStatus, atmVplAdminStatus,
3899 atmVplLastChange,
3900 atmVplReceiveTrafficDescrIndex,
3901 atmVplTransmitTrafficDescrIndex,
3902 atmVplRowStatus }
3903 STATUS current
3904 DESCRIPTION
3905 "A collection of objects providing
3906 information about a VPL at an ATM interface
3907 which terminates a VPC
3908 (i.e., one which is NOT cross-connected
3909 to other VPLs)."
3910 ::= { atmMIBGroups 5 }
3911
3912 atmVccTerminationGroup OBJECT-GROUP
3913
3914
3915
3916 <span class="grey">Ahmed &amp; Tesink [Page 70]</span></pre>
3917 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-71" ></span>
3918 <span class="grey"><a href="./rfc1695">RFC 1695</a> ATM Management Objects August 1994</span>
3919
3920
3921 OBJECTS {atmVclOperStatus, atmVclAdminStatus,
3922 atmVclLastChange,
3923 atmVclReceiveTrafficDescrIndex,
3924 atmVclTransmitTrafficDescrIndex,
3925 atmVccAalType, atmVclRowStatus }
3926 STATUS current
3927 DESCRIPTION
3928 "A collection of objects providing information
3929 about a VCL at an ATM interface
3930 which terminates a VCC (i.e., one which is
3931 NOT cross-connected to other VCLs)."
3932 ::= { atmMIBGroups 6 }
3933
3934 atmVpCrossConnectGroup OBJECT-GROUP
3935 OBJECTS { atmVplReceiveTrafficDescrIndex,
3936 atmVplTransmitTrafficDescrIndex,
3937 atmVplOperStatus, atmVplRowStatus,
3938 atmVpCrossConnectAdminStatus,
3939 atmVpCrossConnectL2HOperStatus,
3940 atmVpCrossConnectH2LOperStatus,
3941 atmVpCrossConnectL2HLastChange,
3942 atmVpCrossConnectH2LLastChange,
3943 atmVpCrossConnectRowStatus,
3944 atmVplCrossConnectIdentifier,
3945 atmVpCrossConnectIndexNext }
3946 STATUS current
3947 DESCRIPTION
3948 "A collection of objects providing
3949 information about a VP cross-connect
3950 and the associated VPLs that are
3951 cross-connected together."
3952 ::= { atmMIBGroups 7 }
3953
3954 atmVcCrossConnectGroup OBJECT-GROUP
3955 OBJECTS { atmVclReceiveTrafficDescrIndex,
3956 atmVclTransmitTrafficDescrIndex,
3957 atmVclOperStatus, atmVclRowStatus,
3958 atmVcCrossConnectAdminStatus,
3959 atmVcCrossConnectL2HOperStatus,
3960 atmVcCrossConnectH2LOperStatus,
3961 atmVcCrossConnectL2HLastChange,
3962 atmVcCrossConnectH2LLastChange,
3963 atmVcCrossConnectRowStatus,
3964 atmVclCrossConnectIdentifier,
3965 atmVcCrossConnectIndexNext }
3966 STATUS current
3967 DESCRIPTION
3968 "A collection of objects providing
3969
3970
3971
3972 <span class="grey">Ahmed &amp; Tesink [Page 71]</span></pre>
3973 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-72" ></span>
3974 <span class="grey"><a href="./rfc1695">RFC 1695</a> ATM Management Objects August 1994</span>
3975
3976
3977 information about a VC cross-connect
3978 and the associated VCLs that are
3979 cross-connected together."
3980 ::= { atmMIBGroups 8 }
3981
3982 aal5VccGroup OBJECT-GROUP
3983 OBJECTS {atmVccAal5CpcsTransmitSduSize,
3984 atmVccAal5CpcsReceiveSduSize,
3985 atmVccAal5EncapsType,
3986 aal5VccCrcErrors, aal5VccSarTimeOuts,
3987 aal5VccOverSizedSDUs }
3988 STATUS current
3989 DESCRIPTION
3990 "A collection of objects providing
3991 AAL5 configuration and performance statistics
3992 of a VCC."
3993 ::= { atmMIBGroups 9 }
3994
3995 END
3996
3997 <span class="h2"><a class="selflink" id="section-11" href="#section-11">11</a>. Acknowledgments</span>
3998
3999 This memo is the result of the work of the AToMMIB Working Group. In
4000 particular, the contributions of Keith McCloghrie and Ted Brunner
4001 were critical to the formulation of this specification.
4002
4003 <span class="h2"><a class="selflink" id="section-12" href="#section-12">12</a>. References</span>
4004
4005 [<a id="ref-1">1</a>] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Structure
4006 of Management Information for version 2 of the Simple Network
4007 Management Protocol (SNMPv2)", <a href="./rfc1442">RFC 1442</a>, SNMP Research,Inc.,
4008 Hughes LAN Systems, Dover Beach Consulting, Inc., Carnegie Mellon
4009 University, April 1993.
4010
4011 [<a id="ref-2">2</a>] McCloghrie, K., and M. Rose, Editors, "Management Information
4012 Base for Network Management of TCP/IP-based internets: MIB-II",
4013 STD 17, <a href="./rfc1213">RFC 1213</a>, Hughes LAN Systems, Performance Systems
4014 International, March 1991.
4015
4016 [<a id="ref-3">3</a>] Galvin, J., and K. McCloghrie, "Administrative Model for version
4017 2 of the Simple Network Management Protocol (SNMPv2)", <a href="./rfc1445">RFC 1445</a>,
4018 Trusted Information Systems, Hughes LAN Systems, April 1993.
4019
4020 [<a id="ref-4">4</a>] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Protocol
4021 Operations for version 2 of the Simple Network Management
4022 Protocol (SNMPv2)", <a href="./rfc1448">RFC 1448</a>, SNMP Research, Inc., Hughes LAN
4023 Systems, Dover Beach Consulting, Inc., Carnegie Mellon
4024 University, April 1993.
4025
4026
4027
4028 <span class="grey">Ahmed &amp; Tesink [Page 72]</span></pre>
4029 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-73" ></span>
4030 <span class="grey"><a href="./rfc1695">RFC 1695</a> ATM Management Objects August 1994</span>
4031
4032
4033 [<a id="ref-5">5</a>] McCloghrie, K. and F. Kastenholz, "Evolution of the Interfaces
4034 Group of MIB-II", <a href="./rfc1573">RFC 1573</a>, Hughes LAN Systems, FTP Software,
4035 January 1994.
4036
4037 [<a id="ref-6">6</a>] Brown, T., and K. Tesink, "Definitions of Managed Objects for
4038 SMDS Interfaces", <a href="./rfc1694">RFC 1694</a>, Bellcore, August 1994.
4039
4040 [<a id="ref-7">7</a>] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Textual
4041 Conventions for SNMPv2", <a href="./rfc1443">RFC 1443</a>, SNMP Research,Inc., Hughes LAN
4042 Systems, Dover Beach Consulting, Inc., Carnegie Mellon
4043 University, April 1993.
4044
4045 [<a id="ref-8">8</a>] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser,
4046 "Conformance Statements for SNMPv2", <a href="./rfc1444">RFC 1444</a>, SNMP
4047 Research,Inc., Hughes LAN Systems, Dover Beach Consulting, Inc.,
4048 Carnegie Mellon University, April 1993.
4049
4050 [<a id="ref-9">9</a>] "ATM Forum UNI Specification, Version 3.0", September 1993.
4051
4052 [<a id="ref-10">10</a>] "ATM Forum B-ICI Specification, Version 1.0", September 1993.
4053
4054 <span class="h2"><a class="selflink" id="section-13" href="#section-13">13</a>. Security Considerations</span>
4055
4056 Security issues are not discussed in this memo.
4057
4058 <span class="h2"><a class="selflink" id="section-14" href="#section-14">14</a>. Authors' Addresses</span>
4059
4060 Masuma Ahmed
4061 Bell Communications Research
4062 Room 1F-217
4063 331 Newman Springs Road
4064 P.O. Box 7020
4065 Red Bank, NJ 07701-7020
4066
4067 Phone: (908) 758-2515
4068 EMail: [email protected]
4069
4070
4071 Kaj Tesink
4072 Bell Communications Research
4073 Room 1A-427
4074 331 Newman Springs Road
4075 P.O. Box 7020
4076 Red Bank, NJ 07701-7020
4077
4078 Phone: (908) 758-5254
4079 EMail: [email protected]
4080
4081
4082
4083
4084 Ahmed &amp; Tesink [Page 73]
4085 </pre>