Debian Codegraph @

rfc2515.html

raw
1 <pre>Network Working Group K. Tesink, Editor
2 Request for Comments: 2515 Bell Communications Research
3 Obsoletes: <a href="./rfc1695">1695</a> February 1999
4 Category: Standards Track
5
6
7 <span class="h1">Definitions of Managed Objects</span>
8 <span class="h1">for ATM Management</span>
9
10 Status of this Memo
11
12 This document specifies an Internet standards track protocol for the
13 Internet community, and requests discussion and suggestions for
14 improvements. Please refer to the current edition of the "Internet
15 Official Protocol Standards" (STD 1) for the standardization state
16 and status of this protocol. Distribution of this memo is unlimited.
17
18 Copyright Notice
19
20 Copyright (C) The Internet Society (1999). All Rights Reserved.
21
22 Table of Contents
23
24 <a href="#section-1">1</a> Abstract ............................................. <a href="#page-2">2</a>
25 <a href="#section-2">2</a> The SNMP Network Management Framework ................. <a href="#page-2">2</a>
26 <a href="#section-3">3</a> ATM Terminology ....................................... <a href="#page-3">3</a>
27 <a href="#section-3.1">3.1</a> VCL/VPL and VCC/VPC ................................. <a href="#page-3">3</a>
28 <a href="#section-3.2">3.2</a> PVC, SVC and Soft PVC ............................... <a href="#page-5">5</a>
29 <a href="#section-3.3">3.3</a> Traffic Management Parameters ....................... <a href="#page-6">6</a>
30 <a href="#section-3.3.1">3.3.1</a> Traffic Policing and Traffic Shaping Parameters
31 .................................................... <a href="#page-6">6</a>
32 <a href="#section-3.3.2">3.3.2</a> Cell Loss Priority ................................ <a href="#page-6">6</a>
33 <a href="#section-3.3.3">3.3.3</a> QoS Class ......................................... <a href="#page-6">6</a>
34 <a href="#section-3.3.4">3.3.4</a> Service Category .................................. <a href="#page-7">7</a>
35 <a href="#section-3.4">3.4</a> Max Active and Max Current VPI and VCI Bits ......... <a href="#page-7">7</a>
36 <a href="#section-4">4</a> Overview .............................................. <a href="#page-8">8</a>
37 <a href="#section-4.1">4.1</a> Background .......................................... <a href="#page-8">8</a>
38 <a href="#section-4.2">4.2</a> Structure of the MIB ................................ <a href="#page-9">9</a>
39 <a href="#section-4.3">4.3</a> ATM Interface Configuration Table ................... <a href="#page-9">9</a>
40 <a href="#section-4.4">4.4</a> ATM Interface DS3 PLCP and TC Layer Tables .......... <a href="#page-9">9</a>
41 <a href="#section-4.5">4.5</a> ATM Virtual Link and Cross-Connect Tables ........... <a href="#page-9">9</a>
42 <a href="#section-5">5</a> Application of MIB II to ATM .......................... <a href="#page-10">10</a>
43 <a href="#section-5.1">5.1</a> The System Group .................................... <a href="#page-10">10</a>
44 <a href="#section-5.2">5.2</a> The Interface Group ................................. <a href="#page-10">10</a>
45 <a href="#section-5.2.1">5.2.1</a> Support of the ATM Cell Layer by ifTable .......... <a href="#page-10">10</a>
46 <a href="#section-6">6</a> Support of the AAL3/4 Based Interfaces ................ <a href="#page-12">12</a>
47 <a href="#section-7">7</a> Support of the AAL5 Managed Objects ................... <a href="#page-12">12</a>
48 <a href="#section-7.1">7.1</a> Managing AAL5 in a Switch ........................... <a href="#page-12">12</a>
49
50
51
52 <span class="grey">Tesink Standards Track [Page 1]</span></pre>
53 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span>
54 <span class="grey"><a href="./rfc2515">RFC 2515</a> ATM Management Objects February 1999</span>
55
56
57 <a href="#section-7.2">7.2</a> Managing AAL5 in a Host ............................. <a href="#page-14">14</a>
58 <a href="#section-7.3">7.3</a> Support of AAL5 by ifTable .......................... <a href="#page-15">15</a>
59 7.4 Support of Proprietary Virtual Interface by ifT-
60 able ............................................... <a href="#page-16">16</a>
61 <a href="#section-7.5">7.5</a> AAL5 Connection Performance Statistics Table ........ <a href="#page-17">17</a>
62 <a href="#section-8">8</a> ILMI MIBs and the ATM Managed Objects ................. <a href="#page-18">18</a>
63 <a href="#section-9">9</a> Definitions ........................................... <a href="#page-20">20</a>
64 <a href="#section-10">10</a> Acknowledgments ...................................... <a href="#page-83">83</a>
65 <a href="#section-11">11</a> References ........................................... <a href="#page-83">83</a>
66 <a href="#section-12">12</a> Security Considerations .............................. <a href="#page-85">85</a>
67 <a href="#section-13">13</a> Author's Address ..................................... <a href="#page-85">85</a>
68 <a href="#section-14">14</a> Intellectual Property ................................ <a href="#page-86">86</a>
69 <a href="#section-15">15</a> Full Copyright Statement ............................. <a href="#page-87">87</a>
70
71 <span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Abstract</span>
72
73 This memo defines a portion of the Management Information Base (MIB)
74 for use with network management protocols in the Internet community.
75 In particular, it describes objects used for managing ATM-based
76 interfaces, devices, networks and services.
77
78 This memo replaces <a href="./rfc1695">RFC 1695</a> [<a href="#ref-24" title="&quot;Definitions of Managed Objects for ATM Management Version 8.0 using SMIv2&quot;">24</a>]. Changes relative to <a href="./rfc1695">RFC 1695</a> are
79 summarized in the MIB module's REVISION clause.
80
81 Textual Conventions used in this MIB are defined in [<a href="#ref-6" title="&quot;Textual Conventions for Version 2 of the Simple Network Management Protocol (SNMPv2)&quot;">6</a>] and [<a href="#ref-19" title="&quot;Definitions of Textual Conventions and OBJECT-IDENTITIES for ATM Management&quot;">19</a>].
82
83 <span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. The SNMP Network Management Framework</span>
84
85 The SNMP Management Framework presently consists of five major
86 components:
87
88 0 An overall architecture, described in <a href="./rfc2271">RFC 2271</a> [<a href="#ref-1" title="&quot;An Architecture for Describing SNMP Management Frameworks&quot;">1</a>].
89
90 0 Mechanisms for describing and naming objects and events
91 for the purpose of management. The first version of this
92 Structure of Management Information (SMI) is called SMIv1 and
93 described in STD 16, <a href="./rfc1155">RFC 1155</a> [<a href="#ref-2" title="&quot;Structure and Identification of Management Information for TCP/IP-based Internets&quot;">2</a>], STD 16, <a href="./rfc1212">RFC 1212</a> [<a href="#ref-3" title="&quot;Concise MIB Definitions&quot;">3</a>] and <a href="./rfc1215">RFC</a>
94 <a href="./rfc1215">1215</a> [<a href="#ref-4" title="&quot;A Convention for Defining Traps for use with the SNMP&quot;">4</a>]. The second version, called SMIv2, is described in <a href="./rfc1902">RFC</a>
95 <a href="./rfc1902">1902</a> [<a href="#ref-5" title="&quot;Structure of Management Information for Version 2 of the Simple Network Management Protocol (SNMPv2)&quot;">5</a>], <a href="./rfc1903">RFC 1903</a> [<a href="#ref-6" title="&quot;Textual Conventions for Version 2 of the Simple Network Management Protocol (SNMPv2)&quot;">6</a>] and <a href="./rfc1904">RFC 1904</a> [<a href="#ref-7" title="&quot;Conformance Statements for Version 2 of the Simple Network Management Protocol (SNMPv2)&quot;">7</a>].
96
97 0 Message protocols for transferring management information. The
98 first version of the SNMP message protocol is called SNMPv1 and
99 described in STD 15, <a href="./rfc1157">RFC 1157</a> [<a href="#ref-8" title="&quot;Simple Network Management Protocol&quot;">8</a>]. A second version of the SNMP
100 message protocol, which is not an Internet standards track
101 protocol, is called SNMPv2c and described in <a href="./rfc1901">RFC 1901</a> [<a href="#ref-9" title="&quot;Introduction to Community-based SNMPv2&quot;">9</a>] and
102 <a href="./rfc1906">RFC 1906</a> [<a href="#ref-10" title="&quot;Transport Mappings for Version 2 of the Simple Network Management Protocol (SNMPv2)&quot;">10</a>].
103
104
105
106
107
108 <span class="grey">Tesink Standards Track [Page 2]</span></pre>
109 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span>
110 <span class="grey"><a href="./rfc2515">RFC 2515</a> ATM Management Objects February 1999</span>
111
112
113 The third version of the message protocol is called SNMPv3 and
114 described in <a href="./rfc1906">RFC 1906</a> [<a href="#ref-10" title="&quot;Transport Mappings for Version 2 of the Simple Network Management Protocol (SNMPv2)&quot;">10</a>], <a href="./rfc2272">RFC 2272</a> [<a href="#ref-11" title="&quot;Message Processing and Dispatching for the Simple Network Management Protocol (SNMP)&quot;">11</a>] and <a href="./rfc2274">RFC 2274</a> [<a href="#ref-12" title="&quot;User-based Security Model (USM) for version 3 of the Simple Network Management Protocol (SNMPv3)&quot;">12</a>].
115
116 0 Protocol operations for accessing management information. The
117 first set of protocol operations and associated PDU formats is
118 described in STD 15, <a href="./rfc1157">RFC 1157</a> [<a href="#ref-8" title="&quot;Simple Network Management Protocol&quot;">8</a>]. A second set of protocol
119 operations and associated PDU formats is described in <a href="./rfc1905">RFC 1905</a>
120 [<a href="#ref-13" title="&quot;Protocol Operations for Version 2 of the Simple Network Management Protocol (SNMPv2)&quot;">13</a>].
121
122 0 A set of fundamental applications described in <a href="./rfc2273">RFC 2273</a> [<a href="#ref-14" title="MPv3 Applications&quot;">14</a>] and
123 the view-based access control mechanism described in <a href="./rfc2275">RFC 2275</a>
124 [<a href="#ref-15" title="&quot;View-based Access Control Model (VACM) for the Simple Network Management Protocol (SNMP)&quot;">15</a>].
125
126 Managed objects are accessed via a virtual information store, termed
127 the Management Information Base or MIB. Objects in the MIB are
128 defined using the mechanisms defined in the SMI.
129
130 This memo specifies a MIB module that is compliant to the SMIv2. A
131 MIB conforming to the SMIv1 can be produced through the appropriate
132 translations. The resulting translated MIB must be semantically
133 equivalent, except where objects or events are omitted because no
134 translation is possible (e.g., use of Counter64). Some machine
135 readable information in SMIv2 will be converted into textual
136 descriptions in SMIv1 during the translation process. However, this
137 loss of machine readable information is not considered to change the
138 semantics of the MIB.
139
140 <span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. ATM Terminology</span>
141
142 Some basic ATM terminologies are described in this section to
143 facilitate defining the ATM managed objects.
144
145 <span class="h3"><a class="selflink" id="section-3.1" href="#section-3.1">3.1</a>. VCL/VPL and VCC/VPC</span>
146
147 There are two distinct types of ATM virtual connections: Virtual
148 Channel Connections (VCCs) and Virtual Path Connection (VPCs). As
149 shown in Figures 1 and 2, ATM virtual connections consist of
150 concatenated series of virtual links which forms a path between two
151 end points, with each concatenation occurring at an ATM switch.
152 Virtual links of VCCs are called Virtual Channel Links (VCLs).
153 Virtual links of VPCs are called Virtual Path Links (VPLs). The VCI
154 and VPI fields in the ATM cell header associate each cell of a VCC
155 with a particular VCL over a given physical link. The VPI field in
156 the ATM cell header associates each cell of a VPC with a particular
157 VPL over a given physical link. Switches route cells between VCLs
158 (or VPLs) via a cross-connect function according to the cells'
159 VCI/VPI (or VPI) values.
160
161
162
163
164 <span class="grey">Tesink Standards Track [Page 3]</span></pre>
165 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span>
166 <span class="grey"><a href="./rfc2515">RFC 2515</a> ATM Management Objects February 1999</span>
167
168
169 &lt;-----------------------VCC--------------------------&gt;
170 ------------ -----------
171 |ATM | |ATM |
172 |X-Connect | |X-Connect |
173 VCL1 |Point | VCL2 |Point | VCL3
174 O---------|----X-----|-------|-----|----X-----|-------O
175 | | | |
176 ------------ ------------
177 ATM Switch ATM Switch
178
179
180 Figure 1: Virtual Channel Links and
181 Virtual Channel Connection
182
183
184
185 &lt;-----------------------VPC--------------------------&gt;
186 ------------ -----------
187 |ATM | |ATM |
188 |X-Connect | |X-Connect |
189 VPL1 |Point | VPL2 |Point | VPL3
190 O---------|----X-----|-------|-----|----X-----|-------O
191 | | | |
192 ------------ ------------
193 ATM Switch ATM Switch
194
195
196 Figure 2: Virtual Path Links and
197 Virtual Path Connection
198
199
200 A single ATM end-system or switch does not support the whole end-to-
201 end span of a VCC (or VPC). Rather, multiple ATM end-systems and/or
202 switches each support one piece of the VCC (or VPC). That is, each
203 ATM end-system (or ATM switch) at one end of the VCC/VPC supports its
204 end of the VCC/VPC plus the VCL or VPL on its external interface, and
205 each switch through which the VCC/VPC passes supports the pair of
206 VCLs/VPLs on its external interfaces as well as the cross-connection
207 of those VCLs/VPLs. Thus, the end-to-end management of a VCC or VPC
208 is achieved only by appropriate management of its individual pieces
209 in combination.
210
211 Note that for management purposes, an ATM network may be viewed as a
212 large distributed switch by hiding all the network's internal
213 connectivity as being internal to the distributed switch (as shown in
214 Figure 2a). This model may for example be used for Customer Network
215 Management (CNM) purposes.
216
217
218
219
220 <span class="grey">Tesink Standards Track [Page 4]</span></pre>
221 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span>
222 <span class="grey"><a href="./rfc2515">RFC 2515</a> ATM Management Objects February 1999</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 Figure 2a: ATM Network modeled as a large distributed
240 switch
241
242 A VCC has a set of traffic characteristics (i.e., bandwidth
243 parameters, service category parameters, etc.). VCLs inherit their
244 traffic characteristics from the VCC of which they are a part. VCCs
245 are bi-directional by definition. However, the traffic parameters in
246 the two directions of a connection can be symmetric or asymmetric,
247 i.e., the two directions can have the same or different traffic
248 flows. A uni-directional traffic flow across a VCC is achieved by
249 assigning a zero bandwidth in one direction. Note that in addition
250 to the bandwidth required by the user traffic flow, bandwidth is also
251 required for OAM cell flows, even for the zero-bandwidth direction of
252 a uni-directional connection. These same principles apply to VPCs.
253
254 <span class="h3"><a class="selflink" id="section-3.2" href="#section-3.2">3.2</a>. PVC, SVC and Soft PVC</span>
255
256 A Permanent Virtual Connection (PVC) is a provisioned VCC or VPC. A
257 Switched Virtual Connection (SVC) is a switched VCC or VPC that is
258 set up in real-time via call set-up signaling procedures. A PVC (or
259 an SVC) can be a point-to-point, point-to-multipoint, or multipoint-
260 to-multipoint VCC or VPC. A Soft PVC is a connection of which
261 portions are switched, while other portions are permanent (see Figure
262 3 and [<a href="#ref-22" title="&quot;ATM Forum Private Network-Network Interface Specification, Version 1.0 (PNNI 1.0)&quot;">22</a>]).
263
264
265 +--------+ +--------+ +--------+
266 pvc| ATM |svc svc | ATM |svc svc | ATM |pvc
267 ----| Switch |-----------| Switch |-----------| Switch |----
268 +--------+ +--------+ +--------+
269
270 Figure 3: An example of a Soft PVC
271
272
273
274
275
276 <span class="grey">Tesink Standards Track [Page 5]</span></pre>
277 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span>
278 <span class="grey"><a href="./rfc2515">RFC 2515</a> ATM Management Objects February 1999</span>
279
280
281 <span class="h3"><a class="selflink" id="section-3.3" href="#section-3.3">3.3</a>. Traffic Management Parameters</span>
282
283 <span class="h4"><a class="selflink" id="section-3.3.1" href="#section-3.3.1">3.3.1</a>. Traffic Policing and Traffic Shaping Parameters</span>
284
285 In order to allocate resources fairly among different users, some
286 networks police traffic at resource access points. The traffic
287 enforcement or policing taken at a UNI is called Usage Parameter
288 Control (UPC) and is conceptually activated on an incoming VCL or VPL
289 as shown in Figure 4. The use of the traffic enforcer at the ingress
290 of the connection is to make sure that the user traffic does not
291 exceed the negotiated traffic parameters such as the peak cell rate
292 associated with a specific traffic descriptor type.
293
294 ---------- ----------
295 UNI | ATM | NNI | ATM | UNI
296 | | switch | | | switch | |
297 O&lt;---|----&gt;X(UPC) |&lt;----|------&gt;| (UPC)X&lt;-----|---&gt;O
298 | VCL | | | VCL | | VCL |
299 ---------- ----------
300
301
302 Figure 4: An Example of a UPC
303
304 In addition, traffic shaping may be performed on an outgoing VPL or
305 VCL at a given ATM interface. The function of the ATM traffic
306 shaper, conceptually either at the source or an egress point of the
307 connection, is to smooth the outgoing cell traffic inter-arrival
308 time. If policing or shaping is not performed then the policing or
309 shaping algorithm is not activated.
310
311 <span class="h4"><a class="selflink" id="section-3.3.2" href="#section-3.3.2">3.3.2</a>. Cell Loss Priority</span>
312
313 To prioritize traffic during resource congestion, ATM cells are
314 assigned one of the two types of Cell Loss Priority (CLP), CLP=0 and
315 CLP=1. ATM cells with CLP=0 have a higher priority in regard to cell
316 loss than ATM cells with CLP=1. Therefore, during resource
317 congestions, CLP=1 cells are dropped before any CLP=0 cell is
318 dropped.
319
320 <span class="h4"><a class="selflink" id="section-3.3.3" href="#section-3.3.3">3.3.3</a>. QoS Class</span>
321
322 <a href="./rfc1695">RFC1695</a> specified that one of a number of Quality of Service (QoS)
323 classes is assigned to a VCC or VPC by associating the object
324 atmTrafficQoSClass with each VCL or VPL. However, new insights in
325 ATM traffic management have caused this object to be deprecated.
326
327
328
329
330
331
332 <span class="grey">Tesink Standards Track [Page 6]</span></pre>
333 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span>
334 <span class="grey"><a href="./rfc2515">RFC 2515</a> ATM Management Objects February 1999</span>
335
336
337 <span class="h4"><a class="selflink" id="section-3.3.4" href="#section-3.3.4">3.3.4</a>. Service Category</span>
338
339 Replacing QoS Class, VPLs and VCLs are qualified in terms of their
340 service category (atmServiceCategory). When properly configured, VCLs
341 (or VPLs) concatenated to form a VCC (or VPC) will all have the same
342 service category class as that of the VCC (or VPC).
343
344 <span class="h3"><a class="selflink" id="section-3.4" href="#section-3.4">3.4</a>. Max Active and Max Current VPI and VCI Bits</span>
345
346 A manager may wish to configure the maximum number of VPI and VCI
347 bits that can be used to identify VPIs and VCIs on a given ATM
348 interface. This value can be less than or equal to the maximum
349 number of bits supported by the interface hardware, and is referred
350 to in the MIB as the Max Active VPI Bits and Max Active VCI Bits.
351
352 However, a manager may not be able to configure the Max Active Bits
353 on both ends of an ATM link. For example, the manager may not be
354 allowed write access to the peer's MIB, or there may be hardware
355 limitations on the peer device. Therefore, the two ATM devices may
356 use ILMI to negotiate "Max Current" VPI and VCI bits, which is the
357 maximum number of bits that both interfaces are willing to support.
358 This is illustrated in Figure 5. The relationship between the
359 different parameters is illustrated in Figure 6. Note that if ILMI
360 negotiation is not supported, then the devices have no choice but to
361 use the configured Max Active bits, and assume that it has been
362 configured to the same value on both ends of the link.
363
364
365 +--------+ +--------+ +--------+
366 | ATM | IF a IF b | ATM | IF c IF d | ATM |
367 | Device |--------------| Device |--------------| Device |
368 +--------+ +--------+ +--------+
369
370 IF a: Max Active VPI Bits = 6 (configured)
371 Max Current VPI Bits = 6 (negotiated)
372
373 IF b: Max Active VPI Bits = 8 (configured)
374 Max Current VPI Bits = 6 (negotiated)
375
376 IF c: Max Active VPI Bits = 8 (configured)
377 Max Current VPI Bits = 8 (negotiated)
378
379 IF d: Max Active VPI Bits = 8 (configured)
380 Max Current VPI Bits = 8 (negotiated)
381
382
383
384
385
386
387
388 <span class="grey">Tesink Standards Track [Page 7]</span></pre>
389 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-8" ></span>
390 <span class="grey"><a href="./rfc2515">RFC 2515</a> ATM Management Objects February 1999</span>
391
392
393 (between IF a and IF b, the minimum of the two configured
394 "Max Active VPI Bits" is 6, so both interfaces set their
395 "Max Current VPI Bits" to 6. Since IF c and IF d both
396 are configured with "Max Active VPI Bits" of 8, they
397 set their "Max Current VPI Bits" to 8.)
398
399 Figure 5
400
401
402 MSB LSB
403 +----------------------------------------------------+
404 | | | | |
405 +----------------------------------------------------+
406 ^ ^ ^ ^
407 | | | |
408 Max bits Max Bits Max Max
409 supported supported Active (config.) current (negotiated)
410 by MIB by h/w Bits Bits
411
412 Figure 6
413
414 <span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Overview</span>
415
416 ATM management objects are used to manage ATM interfaces, ATM virtual
417 links, ATM cross-connects, AAL5 entities and AAL5 connections
418 supported by ATM hosts, ATM switches and ATM networks. This section
419 provides an overview and background of how to use this MIB and other
420 potential MIBs for this purpose.
421
422 The purpose of this memo is primarily to manage ATM PVCs. ATM SVCs
423 are also represented by the management information in this MIB.
424 However, full management of SVCs may require additional capabilities
425 which are beyond the scope of this memo.
426
427 <span class="h3"><a class="selflink" id="section-4.1" href="#section-4.1">4.1</a>. Background</span>
428
429 In addition to the MIB module defined in this memo, other MIB modules
430 are necessary to manage ATM interfaces, links and cross-connects.
431 Examples include MIB II for general system and interface management
432 [<a href="#ref-16" title="&quot;Management Information Base for Network Management of TCP/IP-based internets: MIB-II&quot;">16</a>][17], the DS3 or SONET MIBs for management of physical
433 interfaces, and, as appropriate, MIB modules for applications that
434 make use of ATM, such as SMDS. These MIB modules are outside the
435 scope of this specification.
436
437 The current specification of this ATM MIB is based on SNMPv2-SMI.
438
439
440
441
442
443
444 <span class="grey">Tesink Standards Track [Page 8]</span></pre>
445 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-9" ></span>
446 <span class="grey"><a href="./rfc2515">RFC 2515</a> ATM Management Objects February 1999</span>
447
448
449 <span class="h3"><a class="selflink" id="section-4.2" href="#section-4.2">4.2</a>. Structure of the MIB</span>
450
451 The managed ATM objects are arranged into the following tables:
452
453 (1) ATM interface configuration table
454 (2) ATM interface DS3 PLCP and TC sublayer tables
455 (3) ATM traffic parameter table
456 (4) ATM interface virtual link (VPL/VCL) configuration
457 tables
458 (5) ATM VP/VC cross-connect tables
459 (6) AAL5 connection performance statistics table
460
461 Note that, managed objects for activation/deactivation of OAM cell
462 flows and ATM traps notifying virtual connection or virtual link
463 failures are outside the scope of this memo.
464
465 <span class="h3"><a class="selflink" id="section-4.3" href="#section-4.3">4.3</a>. ATM Interface Configuration Table</span>
466
467 This table contains information on ATM cell layer configuration of
468 local ATM interfaces on an ATM device in addition to the information
469 on such interfaces contained in the ifTable.
470
471 <span class="h3"><a class="selflink" id="section-4.4" href="#section-4.4">4.4</a>. ATM Interface DS3 PLCP and TC Layer Tables</span>
472
473 These tables provide performance statistics of the DS3 PLCP and TC
474 sublayer of local ATM interfaces on a managed ATM device. DS3 PLCP
475 and TC sublayer are currently used to carry ATM cells respectively
476 over DS3 and SONET transmission paths.
477
478 <span class="h3"><a class="selflink" id="section-4.5" href="#section-4.5">4.5</a>. ATM Virtual Link and Cross-Connect Tables</span>
479
480 ATM virtual link and cross-connect tables model bi-directional ATM
481 virtual links and ATM cross-connects. The ATM VP/VC link tables are
482 implemented in an ATM host, ATM switch and ATM network. The ATM
483 switch and ATM network also implement the ATM VP/VC cross-connect
484 tables. Both link and cross-connect tables are implemented in a
485 carrier's network for Customer Network Management (CNM) purposes.
486
487 The ATM virtual link tables are used to create, delete or modify ATM
488 virtual links in an ATM host, ATM switch and ATM network. ATM
489 virtual link tables along with the cross-connect tables are used to
490 create, delete or modify ATM cross-connects in an ATM switch or ATM
491 network (e.g., for CNM purposes).
492
493 For a PVC, the cross-connect between two VPLs is represented in the
494 atmVpCrossConnectTable of the ATM-MIB, indexed by the
495 atmVplCrossConnectIdentifier values for the two VPLs, and the cross-
496
497
498
499
500 <span class="grey">Tesink Standards Track [Page 9]</span></pre>
501 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-10" ></span>
502 <span class="grey"><a href="./rfc2515">RFC 2515</a> ATM Management Objects February 1999</span>
503
504
505 rconnect between two VCLs is represented in the
506 atmVcCrossConnectTable of the ATM-MIB, indexed by the
507 atmVclCrossConnectIdentifier values for the two VCLs.
508
509 For an SVC or Soft PVC the VPL and VCL tables defined in this memo
510 are used. Hoewever, for an SVC or Soft PVC the cross-connect between
511 two VPLs is represented in the atmSvcVpCrossConnectTable of the
512 ATM2-MIB, indexed by the atmVplCrossConnectIdentifier values for the
513 two VPLs, and the cross-connect between two VCLs is represented in
514 the atmSvcVcCrossConnectTable of the ATM2-MIB, indexed by the
515 atmVclCrossConnectIdentifier values for the two VCLs.
516
517 Note: The ATM2-MIB module was being defined in a separate memo at the
518 time of this publication. Please consult the RFC directory for an
519 exact reference.
520
521 <span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. Application of MIB II to ATM</span>
522
523 <span class="h3"><a class="selflink" id="section-5.1" href="#section-5.1">5.1</a>. The System Group</span>
524
525 For the purposes of the sysServices object in the System Group of MIB
526 II [<a href="#ref-16" title="&quot;Management Information Base for Network Management of TCP/IP-based internets: MIB-II&quot;">16</a>], ATM is a data link layer protocol. Thus, for ATM switches
527 and ATM networks, sysServices will have the value "2".
528
529 <span class="h3"><a class="selflink" id="section-5.2" href="#section-5.2">5.2</a>. The Interface Group</span>
530
531 The Interfaces Group of MIB II defines generic managed objects for
532 managing interfaces. This memo contains the media-specific
533 extensions to the Interfaces Group for managing ATM interfaces.
534
535 This memo assumes the interpretation of the Interfaces Group to be in
536 accordance with [<a href="#ref-17" title="&quot;The Interfaces Group MIB&quot;">17</a>] which states that the interfaces table (ifTable)
537 contains information on the managed resource's interfaces and that
538 each sub-layer below the internetwork layer of a network interface is
539 considered an interface. Thus, the ATM cell layer interface is
540 represented as an entry in the ifTable. This entry is concerned with
541 the ATM cell layer as a whole, and not with individual virtual
542 connections which are managed via the ATM-specific managed objects
543 specified in this memo. The inter-relation of entries in the ifTable
544 is defined by Interfaces Stack Group defined in [<a href="#ref-17" title="&quot;The Interfaces Group MIB&quot;">17</a>].
545
546 <span class="h4"><a class="selflink" id="section-5.2.1" href="#section-5.2.1">5.2.1</a>. Support of the ATM Cell Layer by ifTable</span>
547
548 Some specific interpretations of ifTable for the ATM cell layer
549 follow.
550
551
552
553
554
555
556 <span class="grey">Tesink Standards Track [Page 10]</span></pre>
557 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-11" ></span>
558 <span class="grey"><a href="./rfc2515">RFC 2515</a> ATM Management Objects February 1999</span>
559
560
561 Object Use for the generic ATM layer
562 ====== =============================
563
564 ifIndex Each ATM port is represented by an ifEntry.
565
566 ifDescr Description of the ATM interface.
567
568 ifType The value that is allocated for ATM is 37.
569
570 ifSpeed The total bandwidth in bits per second
571 for use by the ATM layer.
572
573 ifPhysAddress The interface's address at the ATM protocol
574 sublayer; the ATM address which would be used as the value
575 of the Called Party Address Information Element (IE) of a
576 signalling message for a connection which either:
577 - would terminate at this interface, or
578 - for which the Called Party Address IE
579 would need to be replaced by the Called Party SubAddress
580 IE before the message was forwarded to any other
581 interface.
582 For an interface on which signalling is not supported,
583 then the interface does not necessarily have an address,
584 but if it does, then ifPhysAddress is the address which
585 would be used as above in the event that signalling were
586 supported. If the interface has multiple such addresses,
587 then ifPhysAddress is its primary address. If the
588 interface has no addresses, then ifPhysAddress is an octet
589 string of zero length. Address encoding is as per [<a href="#ref-20" title="ATM User-Network Interface">20</a>].
590 Note that addresses assigned for purposes other than those
591 listed above (e.g., an address associated with the service
592 provider side of a public network UNI) may be represented
593 through atmInterfaceSubscrAddress.
594
595 ifAdminStatus See [<a href="#ref-17" title="&quot;The Interfaces Group MIB&quot;">17</a>].
596
597 ifOperStatus Assumes the value down(2) if the ATM cell
598 layer is down.
599
600 ifLastChange See [<a href="#ref-17" title="&quot;The Interfaces Group MIB&quot;">17</a>].
601
602 ifInOctets The number of received octets over the
603 interface, i.e., the number of received, assigned cells
604 multiplied by 53.
605
606 ifOutOctets The number of transmitted octets over the interface,
607 i.e., the number of transmitted, assigned cells multiplied
608 by 53.
609
610
611
612 <span class="grey">Tesink Standards Track [Page 11]</span></pre>
613 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-12" ></span>
614 <span class="grey"><a href="./rfc2515">RFC 2515</a> ATM Management Objects February 1999</span>
615
616
617 ifInErrors The number of cells dropped due to uncorrectable HEC
618 errors.
619
620 ifInUnknownProtos The number of received cells discarded during cell
621 header validation, including cells with unrecognized
622 VPI/VCI values, and cells with invalid cell header
623 patterns. If cells with undefined PTI values are
624 discarded, they are also counted here.
625
626 ifOutErrors See [<a href="#ref-17" title="&quot;The Interfaces Group MIB&quot;">17</a>].
627
628 ifName Textual name (unique on this system) of the
629 interface or an octet string of zero length.
630
631 ifLinkUpDownTrapEnable Default is disabled (2).
632
633 ifConnectorPresent Set to false (2).
634
635 ifHighSpeed See [<a href="#ref-17" title="&quot;The Interfaces Group MIB&quot;">17</a>].
636
637 ifHCInOctets The 64-bit version of ifInOctets; supported
638 if required by the compliance statements in [<a href="#ref-17" title="&quot;The Interfaces Group MIB&quot;">17</a>].
639
640 ifHCOutOctets The 64-bit version of ifOutOctets; supported
641 if required by the compliance statements in [<a href="#ref-17" title="&quot;The Interfaces Group MIB&quot;">17</a>].
642
643 ifAlias The non-volatile 'alias' name for the interface
644 as specified by a network manager.
645
646 <span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. Support of the AAL3/4 Based Interfaces</span>
647
648 For the management of AAL3/4 CPCS layer, see [<a href="#ref-18" title="&quot;Definitions of Managed Objects for SMDS Interfaces&quot;">18</a>].
649
650 <span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. Support of the AAL5 Managed Objects</span>
651
652 Support of AAL5 managed objects in an ATM switch and ATM host are
653 described below.
654
655 <span class="h3"><a class="selflink" id="section-7.1" href="#section-7.1">7.1</a>. Managing AAL5 in a Switch</span>
656
657 Managing AAL5 in a switch involves:
658
659 (1) performance management of an AAL5 entity as
660 an internal resource in a switch
661
662 (2) performance management of AAL5 per virtual connection
663
664
665
666
667
668 <span class="grey">Tesink Standards Track [Page 12]</span></pre>
669 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-13" ></span>
670 <span class="grey"><a href="./rfc2515">RFC 2515</a> ATM Management Objects February 1999</span>
671
672
673 AAL5 in a switch is modeled as shown in Figure 7 and 8. AAL5 will be
674 managed in a switch for only those virtual connections that carry
675 AAL5 and are terminated at the AAL5 entity in the switch. Note that,
676 the virtual channels within the ATM UNIs carrying AAL5 will be
677 switched by the ATM switching fabric (termed as ATM Entity in the
678 figure) to the virtual channels on a proprietary internal interface
679 associated with the AAL5 process (termed as AAL5 Entity in the
680 figure). Therefore, performance management of the AAL5 resource in
681 the switch will be modeled using the ifTable through an internal
682 (pseudo-ATM) virtual interface and the AAL5 performance management
683 per virtual connection will be supported using an additional AAL5
684 connection table in the ATM MIB. The association between the AAL5
685 virtual link at the proprietary virtual, internal interface and the
686 ATM virtual link at the ATM interface will be derived from the
687 virtual channel cross-connect table and the virtual channel link
688 table in the ATM MIB. Note that for the proprietary virtual interface
689 the traffic transmit and receive conventions in the virtual channel
690 link table are as follows:
691
692 Transmitting traffic: ATM Entity ---&gt; AAL5 Entity
693 Receiving traffic: ATM Entity &lt;--- AAL5 Entity
694
695 ___________________________
696 | |
697 | ============= |
698 | | AAL5 | |
699 | | Entity | |
700 | ============= |
701 | | |
702 | -----Prop. Virtual Interface
703 | | |
704 | ============= |
705 | | ATM | |
706 | | Entity | |
707 | ============= |
708 |_____|__|__|__|__|_______|
709 | | | | |
710 ---------------- ATM UNIs
711 | | | | |
712 | | | | |
713 v v v v v
714
715 Figure 7: Model of an AAL5 Entity in a Switch
716
717
718
719
720
721
722
723
724 <span class="grey">Tesink Standards Track [Page 13]</span></pre>
725 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-14" ></span>
726 <span class="grey"><a href="./rfc2515">RFC 2515</a> ATM Management Objects February 1999</span>
727
728
729 __________________
730 | |
731 | AAL5 |
732 |________________|
733 | |
734 | Prop. Virtual |
735 | Interface |
736 |________________|
737
738 Figure 8: AAL5 Entity's Interface Stack in a Switch
739
740 <span class="h3"><a class="selflink" id="section-7.2" href="#section-7.2">7.2</a>. Managing AAL5 in a Host</span>
741
742 Managing AAL5 in a host involves managing the AAL5 sublayer interface
743 as shown in Figure 9 and 10. The AAL5 sublayer is stacked directly
744 over the ATM sublayer. The ifTable is applied to the AAL5 sublayer
745 as defined in <a href="#section-10.3">Section 10.3</a>.
746
747 ___________________________
748 | |
749 | ============= |
750 | | AAL5 | |
751 | | Entity | |
752 | ============= |
753 | | ATM | |
754 | | Entity | |
755 | ============= |
756 |___________|_____________|
757 |
758 __|__ ATM UNI
759 |
760 |
761 v
762
763 Figure 9: Model of an AAL5 Entity in a Host
764
765 __________________
766 | |
767 | AAL5 |
768 |________________|
769 | |
770 | ATM Layer |
771 |________________|
772 | |
773 | Physical Layer|
774 |________________|
775
776 Figure 10: AAL5 Entity's Interface Stack in a Host
777
778
779
780 <span class="grey">Tesink Standards Track [Page 14]</span></pre>
781 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-15" ></span>
782 <span class="grey"><a href="./rfc2515">RFC 2515</a> ATM Management Objects February 1999</span>
783
784
785 <span class="h3"><a class="selflink" id="section-7.3" href="#section-7.3">7.3</a>. Support of AAL5 by ifTable</span>
786
787 The AAL5 entity in an ATM device (e.g., switch or host) is managed
788 using the ifTable. There are additional counters specified for AAL5
789 than those specified in the ATM B-ICI document [<a href="#ref-21" title="af-bici-0013.002">21</a>]. Specific
790 interpretations of ifTable for the AAL5 CPCS layer are as follows.
791
792 Object Use for AAL5 CPCS layer entity
793 ====== ==============================
794
795 ifIndex Each AAL5 entity is represented by an ifEntry.
796
797 ifDescr Description of the AAL5 entity.
798
799 ifType The value that is allocated for AAL5 is 49.
800
801 ifMtu Set to the largest PDU size for the
802 AAL5 CPCS layer that can be processed
803 by the AAL5 entity.
804
805 ifSpeed Set to 0.
806
807 ifPhysAddress An octet string of zero length.
808
809 ifAdminStatus See [<a href="#ref-17" title="&quot;The Interfaces Group MIB&quot;">17</a>].
810
811 ifOperStatus Assumes the value down(2) if the AAL5
812 layer is down.
813
814 ifLastChange See [<a href="#ref-17" title="&quot;The Interfaces Group MIB&quot;">17</a>].
815
816 ifInOctets The number of received AAL5 CPCS PDU octets.
817
818 ifOutOctets The number of AAL5 CPCS PDU octets
819 transmitted.
820
821 ifInUcastPkts The number of received AAL5 CPCS PDUs passed
822 to a higher-layer.
823
824 ifOutUcastPkts The number of AAL5 CPCS PDUs received from a
825 higher-layer for transmission.
826 [Note: The number of AAL5 PDUs actually
827 transmitted is the number received from a
828 higher-layer for transmission minus any which
829 are counted by ifOutErrors and ifOutDiscards.]
830
831
832
833
834
835
836 <span class="grey">Tesink Standards Track [Page 15]</span></pre>
837 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-16" ></span>
838 <span class="grey"><a href="./rfc2515">RFC 2515</a> ATM Management Objects February 1999</span>
839
840
841 ifInErrors Number of errored AAL5 CPCS PDUs received.
842 The types of errors counted include CRC-32 errors,
843 SAR time-out errors, and oversized SDU errors.
844
845 ifInUnknownProtos Set to 0.
846
847 ifInDiscards Number of received AAL5 CPCS PDUs discarded.
848 Possible reason may be input buffer overflow.
849
850 ifOutErrors Number of AAL5 CPCS PDUs that could not
851 be transmitted due to errors.
852
853 ifOutDiscards Number of AAL5 CPCS PDUs received for
854 transmission that are discarded.
855 Possible reason may be output buffer
856 overflow.
857
858 ifInMulticastPkts Set to 0.
859
860 ifInBroadcastPkts Set to 0.
861
862 ifOutMulticastPkts Set to 0.
863
864 ifOutBroadcastPkts Set to 0.
865
866 ifName Textual name (unique on this system) of the
867 AAL5 entity or an octet string of zero length.
868
869 ifHighSpeed Set to 0.
870
871 ifConnectorPresent Set to false (2).
872
873 ifPromiscuousMode Set to false(2).
874
875 ifLinkUpDownTrapEnable Default is disabled (2).
876
877 ifAlias The non-volatile 'alias' name for the interface
878 as specified by a network manager.
879
880 <span class="h3"><a class="selflink" id="section-7.4" href="#section-7.4">7.4</a>. Support of Proprietary Virtual Interface by ifTable</span>
881
882 Specific interpretations of ifTable for the proprietary virtual,
883 internal interface associated with an AAL5 entity in an ATM switch
884 are as follows.
885
886
887
888
889
890
891
892 <span class="grey">Tesink Standards Track [Page 16]</span></pre>
893 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-17" ></span>
894 <span class="grey"><a href="./rfc2515">RFC 2515</a> ATM Management Objects February 1999</span>
895
896
897 Object Use for proprietary virtual, internal interface
898 associated with AAL entities
899 ====== ===============================================
900
901 ifIndex Each proprietary virtual, internal interface
902 associated with AAL entities is represented by an
903 ifEntry.
904
905 ifDescr Description of the proprietary virtual, internal
906 interface associated with AAL entities.
907
908 ifType The value that is allocated for proprietary
909 virtual, internal interface is 53.
910
911 ifSpeed See [<a href="#ref-17" title="&quot;The Interfaces Group MIB&quot;">17</a>]. Set to 0 if the speed is not
912 known.
913
914 ifPhysAddress See [<a href="#ref-17" title="&quot;The Interfaces Group MIB&quot;">17</a>]. An octet string of zero length
915 if no address is used for this interface.
916
917 ifAdminStatus See [<a href="#ref-17" title="&quot;The Interfaces Group MIB&quot;">17</a>].
918
919 ifOperStatus See [<a href="#ref-17" title="&quot;The Interfaces Group MIB&quot;">17</a>].
920
921 ifLastChange See [<a href="#ref-17" title="&quot;The Interfaces Group MIB&quot;">17</a>].
922
923 ifName Textual name (unique on this system) of the
924 interface or an octet string of zero length.
925
926 ifHighSpeed See [<a href="#ref-17" title="&quot;The Interfaces Group MIB&quot;">17</a>]. Set to 0 if the speed is not known.
927
928 ifConnectorPresent Set to false (2).
929
930 ifLinkUpDownTrapEnable Default is disabled (2).
931
932 ifAlias The non-volatile 'alias' name for the interface
933 as specified by a network manager.
934
935 <span class="h3"><a class="selflink" id="section-7.5" href="#section-7.5">7.5</a>. AAL5 Connection Performance Statistics Table</span>
936
937 An AAL5 connection table is used to provide AAL5 performance
938 information for each AAL5 virtual connection that is terminated at
939 the AAL5 entity contained within an ATM switch or host.
940
941
942
943
944
945
946
947
948 <span class="grey">Tesink Standards Track [Page 17]</span></pre>
949 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-18" ></span>
950 <span class="grey"><a href="./rfc2515">RFC 2515</a> ATM Management Objects February 1999</span>
951
952
953 <span class="h2"><a class="selflink" id="section-8" href="#section-8">8</a>. ILMI MIBs and the ATM Managed Objects</span>
954
955 The ILMI MIBs are specified by the ATM Forum as a set of several
956 MIBs, all currently defined in the ILMI Specification [<a href="#ref-23" title="&quot;ATM Forum Integrated Local Management Interface (ILMI) Specification&quot;">23</a>]. The ILMI
957 protocols and MIBs allow two connected ATM Interface Management
958 Entities (IMEs) to exchange bi-directional parameters, mainly to
959 facilitate auto-configuration between ATM peer entities. The support
960 of the ATM management functions by the ILMI MIBs and those contained
961 in this memo are compared in Table 1. In this table, "yes" in the
962 "ILMI MIBs" column indicates that the management functions are
963 supported by the ILMI MIBs. The parenthesized numbers in the "This
964 memo" column correspond to the sets of tables enumerated in <a href="#section-6.2">Section</a>
965 <a href="#section-6.2">6.2</a>.
966
967 For that subset of management information which the ILMI MIBs and
968 this memo have in common, every effort has been made to retain
969 identical semantics and syntax, even though the MIB objects are
970 identified using different OBJECT IDENTIFIERs.
971
972 Table 1 - Structuring of ATM Managed Objects
973 ______________________________________________________________
974 | |This |ILMI|
975 ATM Mgmt.Inf. |ATM Managed Objects |memo |MIBs|
976 ______________|_________________________________|_______|____|
977
978 Local Interface Information:
979 _____________________________________________________________
980 ATM interface:| (1) port identifier |ATM MIB| |
981 physical layer| (2) physical transmission types | (1)*|yes |
982 configuration | (3) operational status |MIB II | * |
983 | (4) administrative status | | ** |
984 | (5) last change status | | |
985 _____________________________________________________________
986 ATM interface:| (1) active VPI/VCI fields |ATM MIB| |
987 cell layer | (2) maximum number of VPCs/VCCs | (1) |yes |
988 configuration | (3) configured VPCs/VCCs | | ** |
989 | (4) ILMI VPI/VCI values | | |
990 | (5) Neighbor system info | | |
991 | (6) Max. number of VPI/VCI bits | |yes |
992 | (7) ATM Subscribed Address | | |
993 _____________________________________________________________
994 ATM interface:|(1) received/transmitted cells | | |
995 cell layer |(2) cells with HEC error |MIB II |yes |
996 performance |(3) cell header validation errors| | |
997 _____________________________________________________________
998
999
1000
1001
1002
1003
1004 <span class="grey">Tesink Standards Track [Page 18]</span></pre>
1005 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-19" ></span>
1006 <span class="grey"><a href="./rfc2515">RFC 2515</a> ATM Management Objects February 1999</span>
1007
1008
1009 _____________________________________________________________
1010 ATM interface:|(1)DS3 PLCP severely errored |ATM MIB| |
1011 PLCP &amp; TC | framing seconds | (2)| |
1012 layer |(2)DS3 PLCP unavailable seconds | |no |
1013 performance |(3)DS3 PLCP alarm state | | |
1014 |(4)out of cell delineation events| | |
1015 |(5)TC alarm state | | |
1016 _____________________________________________________________
1017 VP/VC link: |(1)VPI or VPI/VCI value |ATM MIB| |
1018 configuration |(2)VCL or VPL operational status | (3,4)|yes |
1019 |(3)VCL/VPL administrative status | |*** |
1020 |(4)VCL/VPL last change status | | |
1021 |(5)transmit/receive traffic/ | | |
1022 | service category parameters | | |
1023 |(6)AAL type | | |
1024 |(7)transmit/receive AAL5 SDU size| | |
1025 |(8)AAL5 encapsulation type | | |
1026 |(9)connection topology type | | |
1027 |(10)use of call control | | |
1028 _____________________________________________________________
1029 VP/VC |(1)cross-connect identifier | | |
1030 Cross-connect:|(2)port identifier of one | | |
1031 configuration | end | | |
1032 |(3)port identifier of the other |ATM MIB| |
1033 | end | (5)|no |
1034 |(4)VPI or VPI/VCI value | | |
1035 | of one end | | |
1036 |(5)VPI or VPI/VCI value of | | |
1037 | the other end | | |
1038 |(6)VC/VP cross-connect | | |
1039 | operational status | | |
1040 |(7)VC/VP cross-connect | | |
1041 | administrative status | | |
1042 |(8)VC/VP last change status | | |
1043 _____________________________________________________________
1044 VCC AAL5 CPCS |(1)PDUs discarded for CRC errors |ATM MIB| |
1045 layer: |(2)PDUs discarded due to | (6) | |
1046 performance | reassembly time out | |no |
1047 |(3)PDUs discarded due to large | | |
1048 | SDUs | | |
1049 _____________________________________________________________
1050 AAL5 entity: |(1)received/transmitted PDUs | | |
1051 |(2)PDUs discarded due to | | |
1052 | protocol errors |MIB II |no |
1053 |(3)a set of configuration/state | | |
1054 | parameters | | |
1055 _____________________________________________________________
1056
1057
1058
1059
1060 <span class="grey">Tesink Standards Track [Page 19]</span></pre>
1061 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-20" ></span>
1062 <span class="grey"><a href="./rfc2515">RFC 2515</a> ATM Management Objects February 1999</span>
1063
1064
1065 *The operational, administrative, and last change status of the ATM
1066 interface and the physical transmission type shall be supported by
1067 the interface table in MIB II [<a href="#ref-16" title="&quot;Management Information Base for Network Management of TCP/IP-based internets: MIB-II&quot;">16</a>][17]. ILMI does not contain the
1068 administrative and last change status of the ATM interface.
1069
1070 ** The ILMI MIB contains read-only objects for various parameters at
1071 the ATM interface level.
1072
1073 ***The ILMI MIBs contain local and end-to-end operational status of
1074 the VPC/VCC segment. However, it does not contain the VPC/VCC
1075 administrative and last change status and the VCC AAL information.
1076
1077 <span class="h2"><a class="selflink" id="section-9" href="#section-9">9</a>. Definitions</span>
1078
1079 ATM-MIB DEFINITIONS ::= BEGIN
1080
1081 IMPORTS
1082 MODULE-IDENTITY, OBJECT-TYPE,
1083 Counter32, Integer32, IpAddress, mib-2
1084 FROM SNMPv2-SMI
1085 DisplayString, RowStatus, TruthValue
1086 FROM SNMPv2-TC
1087 MODULE-COMPLIANCE, OBJECT-GROUP
1088 FROM SNMPv2-CONF
1089 InterfaceIndex, ifIndex
1090 FROM IF-MIB
1091 AtmAddr, AtmConnKind, AtmConnCastType,
1092 AtmServiceCategory, AtmTrafficDescrParamIndex,
1093 AtmVpIdentifier, AtmVcIdentifier,
1094 AtmVorXAdminStatus, AtmVorXLastChange,
1095 AtmVorXOperStatus, atmNoClpNoScr
1096 FROM ATM-TC-MIB;
1097
1098
1099 atmMIB MODULE-IDENTITY
1100 LAST-UPDATED "9810191200Z"
1101 ORGANIZATION "IETF AToM MIB Working Group"
1102 CONTACT-INFO
1103 " Kaj Tesink
1104 Postal: Bellcore
1105 331 Newman Springs Road
1106 Red Bank, NJ 07701
1107 Tel: 732-758-5254
1108 Fax: 732-758-2269
1109 E-mail: [email protected]"
1110 DESCRIPTION
1111 "This is the MIB Module for ATM and AAL5-related
1112 objects for managing ATM interfaces, ATM virtual
1113
1114
1115
1116 <span class="grey">Tesink Standards Track [Page 20]</span></pre>
1117 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-21" ></span>
1118 <span class="grey"><a href="./rfc2515">RFC 2515</a> ATM Management Objects February 1999</span>
1119
1120
1121 links, ATM cross-connects, AAL5 entities, and
1122 and AAL5 connections."
1123 REVISION "9810191200Z"
1124 DESCRIPTION
1125 "The initial revision of this module was published
1126 as <a href="./rfc1695">RFC 1695</a>. Key revisions include:
1127 o Textual Conventions and OBJECT IDENTITIES have
1128 been moved to a separate MIB module.
1129 o Applicability of objects to PVCs, SVCs and Soft
1130 PVCs has been clarified.
1131 o DEFVAL clauses have been added.
1132 o The relationship of ifIndex values with different
1133 layers and sublayers related to ATM has been
1134 clarified.
1135 o atmTrafficQosClass has been deprecated
1136 and replaced with atmServiceCategory.
1137 o atmInterfaceCurrentMaxVpiBits and
1138 atmInterfaceCurrentMaxVciBits have been added with
1139 a description on their relationship with other
1140 objects.
1141 o atmInterfaceAddressType and atmInterfaceAdminAddress
1142 have been deprecated and replaced by
1143 atmInterfaceSubscrAddress.
1144 o atmInterfaceTCAlarmState has been clarified.
1145 o atmTrafficDescrParamIndexNext has been introduced
1146 in order to provide a manager a free
1147 atmTrafficDescrParamIndex value.
1148 o The atmTrafficFrameDiscard capability has been added.
1149 o A connection topology type (atmVpl/VclCastType) and
1150 a call control type (atmVpl/VclConnKind) have been
1151 added.
1152 o aal2 has been added to atmVccAalType."
1153 REVISION "9406072245Z"
1154 DESCRIPTION
1155 "The <a href="./rfc1695">RFC1695</a> version of this MIB module."
1156 ::= { mib-2 37 }
1157
1158
1159 atmMIBObjects OBJECT IDENTIFIER ::= {atmMIB 1}
1160
1161 -- {atmMIBObjects 1} has been moved to a separate
1162 -- specification [<a href="#ref-19" title="&quot;Definitions of Textual Conventions and OBJECT-IDENTITIES for ATM Management&quot;">19</a>].
1163
1164
1165 -- This ATM MIB Module consists of the following tables:
1166 -- (1) ATM Interface configuration table
1167 -- (2) ATM Interface DS3 PLCP table
1168 -- (3) ATM Interface TC Sublayer table
1169
1170
1171
1172 <span class="grey">Tesink Standards Track [Page 21]</span></pre>
1173 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-22" ></span>
1174 <span class="grey"><a href="./rfc2515">RFC 2515</a> ATM Management Objects February 1999</span>
1175
1176
1177 -- (4) Atm Traffic Descriptor table
1178 -- (5) ATM Interface VPL configuration table
1179 -- (6) ATM Interface VCL configuration table
1180 -- (7) ATM VP Cross Connect table (for PVCs)
1181 -- (8) ATM VC Cross Connect table (for PVCs)
1182 -- (9) ATM Interface AAL5 VCC performance statistics
1183 -- table
1184
1185 -- ATM Interface Configuration Parameters Table
1186
1187 -- This table contains ATM specific
1188 -- configuration information associated with
1189 -- an ATM interface beyond those
1190 -- supported using the ifTable.
1191
1192
1193
1194
1195 atmInterfaceConfTable OBJECT-TYPE
1196 SYNTAX SEQUENCE OF AtmInterfaceConfEntry
1197 MAX-ACCESS not-accessible
1198 STATUS current
1199 DESCRIPTION
1200 "This table contains ATM local interface
1201 configuration parameters, one entry per ATM
1202 interface port."
1203 ::= { atmMIBObjects 2 }
1204
1205 atmInterfaceConfEntry OBJECT-TYPE
1206 SYNTAX AtmInterfaceConfEntry
1207 MAX-ACCESS not-accessible
1208 STATUS current
1209 DESCRIPTION
1210 "This list contains ATM interface configuration
1211 parameters and state variables and is indexed
1212 by ifIndex values of ATM interfaces."
1213 INDEX { ifIndex }
1214 ::= { atmInterfaceConfTable 1}
1215
1216 AtmInterfaceConfEntry ::= SEQUENCE {
1217 atmInterfaceMaxVpcs INTEGER,
1218 atmInterfaceMaxVccs INTEGER,
1219 atmInterfaceConfVpcs INTEGER,
1220 atmInterfaceConfVccs INTEGER,
1221 atmInterfaceMaxActiveVpiBits INTEGER,
1222 atmInterfaceMaxActiveVciBits INTEGER,
1223 atmInterfaceIlmiVpi AtmVpIdentifier,
1224 atmInterfaceIlmiVci AtmVcIdentifier,
1225
1226
1227
1228 <span class="grey">Tesink Standards Track [Page 22]</span></pre>
1229 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-23" ></span>
1230 <span class="grey"><a href="./rfc2515">RFC 2515</a> ATM Management Objects February 1999</span>
1231
1232
1233 atmInterfaceAddressType INTEGER,
1234 atmInterfaceAdminAddress AtmAddr,
1235 atmInterfaceMyNeighborIpAddress IpAddress,
1236 atmInterfaceMyNeighborIfName DisplayString,
1237 atmInterfaceCurrentMaxVpiBits INTEGER,
1238 atmInterfaceCurrentMaxVciBits INTEGER,
1239 atmInterfaceSubscrAddress AtmAddr
1240 }
1241
1242
1243 atmInterfaceMaxVpcs OBJECT-TYPE
1244 SYNTAX INTEGER (0..4096)
1245 MAX-ACCESS read-write
1246 STATUS current
1247 DESCRIPTION
1248 "The maximum number of VPCs (PVPCs and SVPCs)
1249 supported at this ATM interface. At the ATM UNI,
1250 the maximum number of VPCs (PVPCs and SVPCs)
1251 ranges from 0 to 256 only."
1252 ::= { atmInterfaceConfEntry 1}
1253
1254 atmInterfaceMaxVccs OBJECT-TYPE
1255 SYNTAX INTEGER (0..65536)
1256 MAX-ACCESS read-write
1257 STATUS current
1258 DESCRIPTION
1259 "The maximum number of VCCs (PVCCs and SVCCs)
1260 supported at this ATM interface."
1261 ::= { atmInterfaceConfEntry 2}
1262
1263 atmInterfaceConfVpcs OBJECT-TYPE
1264 SYNTAX INTEGER (0..4096)
1265 MAX-ACCESS read-only
1266 STATUS current
1267 DESCRIPTION
1268 "The number of VPCs (PVPC, Soft PVPC and SVPC)
1269 currently in use at this ATM interface. It includes
1270 the number of PVPCs and Soft PVPCs that are configured
1271 at the interface, plus the number of SVPCs
1272 that are currently established at the
1273 interface.
1274
1275 At the ATM UNI, the configured number of
1276 VPCs (PVPCs and SVPCs) can range from
1277 0 to 256 only."
1278 ::= { atmInterfaceConfEntry 3}
1279
1280 atmInterfaceConfVccs OBJECT-TYPE
1281
1282
1283
1284 <span class="grey">Tesink Standards Track [Page 23]</span></pre>
1285 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-24" ></span>
1286 <span class="grey"><a href="./rfc2515">RFC 2515</a> ATM Management Objects February 1999</span>
1287
1288
1289 SYNTAX INTEGER (0..65536)
1290 MAX-ACCESS read-only
1291 STATUS current
1292 DESCRIPTION
1293 "The number of VCCs (PVCC, Soft PVCC and SVCC)
1294 currently in use at this ATM interface. It includes
1295 the number of PVCCs and Soft PVCCs that are configured
1296 at the interface, plus the number of SVCCs
1297 that are currently established at the
1298 interface."
1299 ::= { atmInterfaceConfEntry 4}
1300
1301 atmInterfaceMaxActiveVpiBits OBJECT-TYPE
1302 SYNTAX INTEGER (0..12)
1303 MAX-ACCESS read-write
1304 STATUS current
1305 DESCRIPTION
1306 "The maximum number of active VPI bits
1307 configured for use at the ATM interface.
1308 At the ATM UNI, the maximum number of active
1309 VPI bits configured for use ranges from
1310 0 to 8 only."
1311 ::= { atmInterfaceConfEntry 5}
1312
1313 atmInterfaceMaxActiveVciBits OBJECT-TYPE
1314 SYNTAX INTEGER (0..16)
1315 MAX-ACCESS read-write
1316 STATUS current
1317 DESCRIPTION
1318 "The maximum number of active VCI bits
1319 configured for use at this ATM interface."
1320 ::= { atmInterfaceConfEntry 6}
1321
1322 atmInterfaceIlmiVpi OBJECT-TYPE
1323 SYNTAX AtmVpIdentifier
1324 MAX-ACCESS read-write
1325 STATUS current
1326 DESCRIPTION
1327 "The VPI value of the VCC supporting
1328 the ILMI at this ATM interface. If the values of
1329 atmInterfaceIlmiVpi and atmInterfaceIlmiVci are
1330 both equal to zero then the ILMI is not
1331 supported at this ATM interface."
1332 DEFVAL { 0 }
1333 ::= { atmInterfaceConfEntry 7}
1334
1335 atmInterfaceIlmiVci OBJECT-TYPE
1336 SYNTAX AtmVcIdentifier
1337
1338
1339
1340 <span class="grey">Tesink Standards Track [Page 24]</span></pre>
1341 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-25" ></span>
1342 <span class="grey"><a href="./rfc2515">RFC 2515</a> ATM Management Objects February 1999</span>
1343
1344
1345 MAX-ACCESS read-write
1346 STATUS current
1347 DESCRIPTION
1348 "The VCI value of the VCC supporting
1349 the ILMI at this ATM interface. If the values of
1350 atmInterfaceIlmiVpi and atmInterfaceIlmiVci are
1351 both equal to zero then the ILMI is not
1352 supported at this ATM interface."
1353 DEFVAL { 16 }
1354 ::= { atmInterfaceConfEntry 8}
1355
1356 atmInterfaceAddressType OBJECT-TYPE
1357 SYNTAX INTEGER {
1358 private(1),
1359 nsapE164(2),
1360 nativeE164(3),
1361 other(4)
1362 }
1363 MAX-ACCESS read-only
1364 STATUS deprecated
1365 DESCRIPTION
1366 "The type of primary ATM address configured
1367 for use at this ATM interface."
1368 ::= { atmInterfaceConfEntry 9 }
1369
1370 -- The atmInterfaceAdminAddress object has been replaced by
1371 -- atmInterfaceSubscrAddress.
1372
1373 atmInterfaceAdminAddress OBJECT-TYPE
1374 SYNTAX AtmAddr
1375 MAX-ACCESS read-only
1376 STATUS deprecated
1377 DESCRIPTION
1378 "The primary address assigned for administrative purposes,
1379 for example, an address associated with the
1380 service provider side of a public network UNI
1381 (thus, the value of this address corresponds
1382 with the value of ifPhysAddress at the host side).
1383 If this interface has no assigned administrative
1384 address, or when the address used for
1385 administrative purposes is the same as that used
1386 for ifPhysAddress, then this is an octet string of
1387 zero length."
1388 ::= { atmInterfaceConfEntry 10 }
1389
1390 atmInterfaceMyNeighborIpAddress OBJECT-TYPE
1391 SYNTAX IpAddress
1392 MAX-ACCESS read-write
1393
1394
1395
1396 <span class="grey">Tesink Standards Track [Page 25]</span></pre>
1397 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-26" ></span>
1398 <span class="grey"><a href="./rfc2515">RFC 2515</a> ATM Management Objects February 1999</span>
1399
1400
1401 STATUS current
1402 DESCRIPTION
1403 "The IP address of the neighbor system connected to
1404 the far end of this interface, to which a Network
1405 Management Station can send SNMP messages, as IP
1406 datagrams sent to UDP port 161, in order to access
1407 network management information concerning the
1408 operation of that system. Note that the value
1409 of this object may be obtained in different ways,
1410 e.g., by manual configuration, or through ILMI
1411 interaction with the neighbor system."
1412 ::= { atmInterfaceConfEntry 11 }
1413
1414 atmInterfaceMyNeighborIfName OBJECT-TYPE
1415 SYNTAX DisplayString
1416 MAX-ACCESS read-write
1417 STATUS current
1418 DESCRIPTION
1419 "The textual name of the interface on the neighbor
1420 system on the far end of this interface, and to
1421 which this interface connects. If the neighbor
1422 system is manageable through SNMP and supports
1423 the object ifName, the value of this object must
1424 be identical with that of ifName for the ifEntry
1425 of the lowest level physical interface
1426 for this port. If this interface does not have a
1427 textual name, the value of this object is a zero
1428 length string. Note that the value of this object
1429 may be obtained in different ways, e.g., by manual
1430 configuration, or through ILMI interaction with
1431 the neighbor system."
1432 ::= { atmInterfaceConfEntry 12 }
1433
1434 atmInterfaceCurrentMaxVpiBits OBJECT-TYPE
1435 SYNTAX INTEGER (0..12)
1436 MAX-ACCESS read-only
1437 STATUS current
1438 DESCRIPTION
1439 "The maximum number of VPI Bits that may
1440 currently be used at this ATM interface.
1441 The value is the minimum of
1442 atmInterfaceMaxActiveVpiBits, and the
1443 atmInterfaceMaxActiveVpiBits of the interface's
1444 UNI/NNI peer.
1445
1446 If the interface does not negotiate with
1447 its peer to determine the number of VPI Bits
1448 that can be used on the interface, then the
1449
1450
1451
1452 <span class="grey">Tesink Standards Track [Page 26]</span></pre>
1453 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-27" ></span>
1454 <span class="grey"><a href="./rfc2515">RFC 2515</a> ATM Management Objects February 1999</span>
1455
1456
1457 value of this object must equal
1458 atmInterfaceMaxActiveVpiBits."
1459 ::= { atmInterfaceConfEntry 13 }
1460
1461 atmInterfaceCurrentMaxVciBits OBJECT-TYPE
1462 SYNTAX INTEGER (0..16)
1463 MAX-ACCESS read-only
1464 STATUS current
1465 DESCRIPTION
1466 "The maximum number of VCI Bits that may
1467 currently be used at this ATM interface.
1468 The value is the minimum of
1469 atmInterfaceMaxActiveVciBits, and the
1470 atmInterfaceMaxActiveVciBits of the interface's
1471 UNI/NNI peer.
1472
1473 If the interface does not negotiate with
1474 its peer to determine the number of VCI Bits
1475 that can be used on the interface, then the
1476 value of this object must equal
1477 atmInterfaceMaxActiveVciBits."
1478 ::= { atmInterfaceConfEntry 14 }
1479
1480 atmInterfaceSubscrAddress OBJECT-TYPE
1481 SYNTAX AtmAddr
1482 MAX-ACCESS read-write
1483 STATUS current
1484 DESCRIPTION
1485 "The identifier assigned by a service provider
1486 to the network side of a public network UNI.
1487 If this interface has no assigned service provider
1488 address, or for other interfaces this is an octet string
1489 of zero length."
1490 ::= { atmInterfaceConfEntry 15 }
1491
1492 -- The ATM Interface DS3 PLCP Table
1493
1494 -- This table contains the DS3 PLCP configuration and
1495 -- state parameters of those ATM interfaces
1496 -- which use DS3 PLCP for carrying ATM cells over DS3.
1497
1498 atmInterfaceDs3PlcpTable OBJECT-TYPE
1499 SYNTAX SEQUENCE OF AtmInterfaceDs3PlcpEntry
1500 MAX-ACCESS not-accessible
1501 STATUS current
1502 DESCRIPTION
1503 "This table contains ATM interface DS3 PLCP
1504 parameters and state variables, one entry per
1505
1506
1507
1508 <span class="grey">Tesink Standards Track [Page 27]</span></pre>
1509 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-28" ></span>
1510 <span class="grey"><a href="./rfc2515">RFC 2515</a> ATM Management Objects February 1999</span>
1511
1512
1513 ATM interface port."
1514 ::= { atmMIBObjects 3}
1515
1516 atmInterfaceDs3PlcpEntry OBJECT-TYPE
1517 SYNTAX AtmInterfaceDs3PlcpEntry
1518 MAX-ACCESS not-accessible
1519 STATUS current
1520 DESCRIPTION
1521 "This list contains DS3 PLCP parameters and
1522 state variables at the ATM interface and is
1523 indexed by the ifIndex value of the ATM interface."
1524 INDEX { ifIndex }
1525 ::= { atmInterfaceDs3PlcpTable 1}
1526
1527 AtmInterfaceDs3PlcpEntry ::= SEQUENCE {
1528 atmInterfaceDs3PlcpSEFSs Counter32,
1529 atmInterfaceDs3PlcpAlarmState INTEGER,
1530 atmInterfaceDs3PlcpUASs Counter32
1531 }
1532
1533
1534 atmInterfaceDs3PlcpSEFSs OBJECT-TYPE
1535 SYNTAX Counter32
1536 MAX-ACCESS read-only
1537 STATUS current
1538 DESCRIPTION
1539 "The number of DS3 PLCP Severely Errored Framing
1540 Seconds (SEFS). Each SEFS represents a
1541 one-second interval which contains
1542 one or more SEF events."
1543 ::= { atmInterfaceDs3PlcpEntry 1}
1544
1545 atmInterfaceDs3PlcpAlarmState OBJECT-TYPE
1546 SYNTAX INTEGER {
1547 noAlarm(1),
1548 receivedFarEndAlarm(2),
1549 incomingLOF(3)
1550 }
1551 MAX-ACCESS read-only
1552 STATUS current
1553 DESCRIPTION
1554 "This variable indicates if there is an
1555 alarm present for the DS3 PLCP. The value
1556 receivedFarEndAlarm means that the DS3 PLCP
1557 has received an incoming Yellow
1558 Signal, the value incomingLOF means that
1559 the DS3 PLCP has declared a loss of frame (LOF)
1560 failure condition, and the value noAlarm
1561
1562
1563
1564 <span class="grey">Tesink Standards Track [Page 28]</span></pre>
1565 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-29" ></span>
1566 <span class="grey"><a href="./rfc2515">RFC 2515</a> ATM Management Objects February 1999</span>
1567
1568
1569 means that there are no alarms present.
1570 Transition from the failure to the no alarm state
1571 occurs when no defects (e.g., LOF) are received
1572 for more than 10 seconds."
1573 ::= { atmInterfaceDs3PlcpEntry 2}
1574
1575 atmInterfaceDs3PlcpUASs OBJECT-TYPE
1576 SYNTAX Counter32
1577 MAX-ACCESS read-only
1578 STATUS current
1579 DESCRIPTION
1580 "The counter associated with the number of
1581 Unavailable Seconds encountered by the PLCP."
1582 ::= { atmInterfaceDs3PlcpEntry 3}
1583
1584
1585 -- The ATM Interface TC Sublayer Table
1586
1587 -- This table contains TC sublayer configuration and
1588 -- state parameters of those ATM interfaces
1589 -- which use TC sublayer for carrying ATM cells over
1590 -- SONET/SDH or DS3.
1591
1592
1593 atmInterfaceTCTable OBJECT-TYPE
1594 SYNTAX SEQUENCE OF AtmInterfaceTCEntry
1595 MAX-ACCESS not-accessible
1596 STATUS current
1597 DESCRIPTION
1598 "This table contains ATM interface TC
1599 Sublayer parameters and state variables,
1600 one entry per ATM interface port."
1601 ::= { atmMIBObjects 4}
1602
1603 atmInterfaceTCEntry OBJECT-TYPE
1604 SYNTAX AtmInterfaceTCEntry
1605 MAX-ACCESS not-accessible
1606 STATUS current
1607 DESCRIPTION
1608 "This list contains TC Sublayer parameters
1609 and state variables at the ATM interface and is
1610 indexed by the ifIndex value of the ATM interface."
1611 INDEX {ifIndex }
1612 ::= { atmInterfaceTCTable 1}
1613
1614 AtmInterfaceTCEntry ::= SEQUENCE {
1615 atmInterfaceOCDEvents Counter32,
1616 atmInterfaceTCAlarmState INTEGER
1617
1618
1619
1620 <span class="grey">Tesink Standards Track [Page 29]</span></pre>
1621 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-30" ></span>
1622 <span class="grey"><a href="./rfc2515">RFC 2515</a> ATM Management Objects February 1999</span>
1623
1624
1625 }
1626
1627 atmInterfaceOCDEvents OBJECT-TYPE
1628 SYNTAX Counter32
1629 MAX-ACCESS read-only
1630 STATUS current
1631 DESCRIPTION
1632 "The number of times the Out of Cell
1633 Delineation (OCD) events occur. If seven
1634 consecutive ATM cells have Header Error
1635 Control (HEC) violations, an OCD event occurs.
1636 A high number of OCD events may indicate a
1637 problem with the TC Sublayer."
1638 ::= { atmInterfaceTCEntry 1}
1639
1640
1641 atmInterfaceTCAlarmState OBJECT-TYPE
1642 SYNTAX INTEGER {
1643 noAlarm(1),
1644 lcdFailure(2)
1645 }
1646 MAX-ACCESS read-only
1647 STATUS current
1648 DESCRIPTION
1649 "This variable indicates if there is an
1650 alarm present for the TC Sublayer. The value
1651 lcdFailure(2) indicates that the TC Sublayer
1652 is currently in the Loss of Cell Delineation
1653 (LCD) defect maintenance state. The value
1654 noAlarm(1) indicates that the TC Sublayer
1655 is currently not in the LCD defect
1656 maintenance state."
1657 ::= { atmInterfaceTCEntry 2}
1658
1659 -- ATM Traffic Descriptor Parameter Table
1660
1661 -- This table contains a set of self-consistent
1662 -- ATM traffic parameters including the
1663 -- ATM traffic service category.
1664
1665 -- The ATM virtual link tables (i.e., VPL and VCL tables)
1666 -- will use this ATM Traffic Descriptor table
1667 -- to assign traffic parameters and service category
1668 -- to the receive and transmit directions of
1669 -- the ATM virtual links (i.e., VPLs and VCLs).
1670 -- The ATM VPL or VCL table will indicate a row
1671 -- in the atmTrafficDescrParamTable
1672 -- using its atmTrafficDescrParamIndex value.
1673
1674
1675
1676 <span class="grey">Tesink Standards Track [Page 30]</span></pre>
1677 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-31" ></span>
1678 <span class="grey"><a href="./rfc2515">RFC 2515</a> ATM Management Objects February 1999</span>
1679
1680
1681 -- The management application can then compare a set of
1682 -- ATM traffic parameters with a single value.
1683
1684 -- If no suitable row(s) in the atmTrafficDescrParamTable
1685 -- exists, the manager must create a new row(s) in this
1686 -- table. If such a row is created, agent checks the
1687 -- sanity of that set of ATM traffic parameter values.
1688
1689 -- The manager may use atmTrafficDescrParamIndexNext
1690 -- in order to obtain a free atmTrafficDescrParamIndex
1691 -- value.
1692
1693 -- When creating a new row, the parameter values
1694 -- will be checked for self-consistency.
1695 -- Predefined/template rows may be supported.
1696
1697 -- A row in the atmTrafficDescrParamTable is deleted
1698 -- by setting the atmTrafficDescrRowStatus to destroy(6).
1699 -- The agent will check whether this row is still in use
1700 -- by any entry of the atmVplTable or atmVclTable.
1701 -- The agent denies the request if the row is still in
1702 -- use.
1703
1704 -- The ATM Traffic Descriptor Parameter Table
1705
1706
1707 atmTrafficDescrParamTable OBJECT-TYPE
1708 SYNTAX SEQUENCE OF AtmTrafficDescrParamEntry
1709 MAX-ACCESS not-accessible
1710 STATUS current
1711 DESCRIPTION
1712 "This table contains information on ATM traffic
1713 descriptor type and the associated parameters."
1714 ::= { atmMIBObjects 5}
1715
1716 atmTrafficDescrParamEntry OBJECT-TYPE
1717 SYNTAX AtmTrafficDescrParamEntry
1718 MAX-ACCESS not-accessible
1719 STATUS current
1720 DESCRIPTION
1721 "This list contains ATM traffic descriptor
1722 type and the associated parameters."
1723 INDEX {atmTrafficDescrParamIndex}
1724 ::= { atmTrafficDescrParamTable 1}
1725
1726 AtmTrafficDescrParamEntry ::= SEQUENCE {
1727 atmTrafficDescrParamIndex AtmTrafficDescrParamIndex,
1728 atmTrafficDescrType OBJECT IDENTIFIER,
1729
1730
1731
1732 <span class="grey">Tesink Standards Track [Page 31]</span></pre>
1733 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-32" ></span>
1734 <span class="grey"><a href="./rfc2515">RFC 2515</a> ATM Management Objects February 1999</span>
1735
1736
1737 atmTrafficDescrParam1 Integer32,
1738 atmTrafficDescrParam2 Integer32,
1739 atmTrafficDescrParam3 Integer32,
1740 atmTrafficDescrParam4 Integer32,
1741 atmTrafficDescrParam5 Integer32,
1742 atmTrafficQoSClass INTEGER,
1743 atmTrafficDescrRowStatus RowStatus,
1744 atmServiceCategory AtmServiceCategory,
1745 atmTrafficFrameDiscard TruthValue
1746 }
1747
1748 atmTrafficDescrParamIndex OBJECT-TYPE
1749 SYNTAX AtmTrafficDescrParamIndex (1..2147483647)
1750 MAX-ACCESS not-accessible
1751 STATUS current
1752 DESCRIPTION
1753 "This object is used by the virtual link
1754 table (i.e., VPL or VCL table)
1755 to identify the row of this table.
1756 When creating a new row in the table
1757 the value of this index may be obtained
1758 by retrieving the value of
1759 atmTrafficDescrParamIndexNext."
1760 ::= { atmTrafficDescrParamEntry 1}
1761
1762 atmTrafficDescrType OBJECT-TYPE
1763 SYNTAX OBJECT IDENTIFIER
1764 MAX-ACCESS read-create
1765 STATUS current
1766 DESCRIPTION
1767 "The value of this object identifies the type
1768 of ATM traffic descriptor.
1769 The type may indicate no traffic descriptor or
1770 traffic descriptor with one or more parameters.
1771 These parameters are specified as a parameter
1772 vector, in the corresponding instances of the
1773 objects:
1774 atmTrafficDescrParam1
1775 atmTrafficDescrParam2
1776 atmTrafficDescrParam3
1777 atmTrafficDescrParam4
1778 atmTrafficDescrParam5."
1779 DEFVAL { atmNoClpNoScr }
1780 ::= { atmTrafficDescrParamEntry 2}
1781
1782 atmTrafficDescrParam1 OBJECT-TYPE
1783 SYNTAX Integer32
1784 MAX-ACCESS read-create
1785
1786
1787
1788 <span class="grey">Tesink Standards Track [Page 32]</span></pre>
1789 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-33" ></span>
1790 <span class="grey"><a href="./rfc2515">RFC 2515</a> ATM Management Objects February 1999</span>
1791
1792
1793 STATUS current
1794 DESCRIPTION
1795 "The first parameter of the ATM traffic descriptor
1796 used according to the value of
1797 atmTrafficDescrType."
1798 DEFVAL { 0 }
1799 ::= { atmTrafficDescrParamEntry 3}
1800
1801 atmTrafficDescrParam2 OBJECT-TYPE
1802 SYNTAX Integer32
1803 MAX-ACCESS read-create
1804 STATUS current
1805 DESCRIPTION
1806 "The second parameter of the ATM traffic descriptor
1807 used according to the value of
1808 atmTrafficDescrType."
1809 DEFVAL { 0 }
1810 ::= { atmTrafficDescrParamEntry 4}
1811
1812 atmTrafficDescrParam3 OBJECT-TYPE
1813 SYNTAX Integer32
1814 MAX-ACCESS read-create
1815 STATUS current
1816 DESCRIPTION
1817 "The third parameter of the ATM traffic descriptor
1818 used according to the value of
1819 atmTrafficDescrType."
1820 DEFVAL { 0 }
1821 ::= { atmTrafficDescrParamEntry 5}
1822
1823 atmTrafficDescrParam4 OBJECT-TYPE
1824 SYNTAX Integer32
1825 MAX-ACCESS read-create
1826 STATUS current
1827 DESCRIPTION
1828 "The fourth parameter of the ATM traffic descriptor
1829 used according to the value of
1830 atmTrafficDescrType."
1831 DEFVAL { 0 }
1832 ::= { atmTrafficDescrParamEntry 6}
1833
1834 atmTrafficDescrParam5 OBJECT-TYPE
1835 SYNTAX Integer32
1836 MAX-ACCESS read-create
1837 STATUS current
1838 DESCRIPTION
1839 "The fifth parameter of the ATM traffic descriptor
1840 used according to the value of
1841
1842
1843
1844 <span class="grey">Tesink Standards Track [Page 33]</span></pre>
1845 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-34" ></span>
1846 <span class="grey"><a href="./rfc2515">RFC 2515</a> ATM Management Objects February 1999</span>
1847
1848
1849 atmTrafficDescrType."
1850 DEFVAL { 0 }
1851 ::= { atmTrafficDescrParamEntry 7}
1852
1853 atmTrafficQoSClass OBJECT-TYPE
1854 SYNTAX INTEGER (0..255)
1855 MAX-ACCESS read-create
1856 STATUS deprecated
1857 DESCRIPTION
1858 "The value of this object identifies the QoS Class.
1859 Four Service classes have been
1860 specified in the ATM Forum UNI Specification:
1861 Service Class A: Constant bit rate video and
1862 Circuit emulation
1863 Service Class B: Variable bit rate video/audio
1864 Service Class C: Connection-oriented data
1865 Service Class D: Connectionless data
1866 Four QoS classes numbered 1, 2, 3, and 4 have
1867 been specified with the aim to support service
1868 classes A, B, C, and D respectively.
1869 An unspecified QoS Class numbered `0' is used
1870 for best effort traffic."
1871 DEFVAL { 0 }
1872 ::= { atmTrafficDescrParamEntry 8}
1873
1874 atmTrafficDescrRowStatus OBJECT-TYPE
1875 SYNTAX RowStatus
1876 MAX-ACCESS read-create
1877 STATUS current
1878 DESCRIPTION
1879 "This object is used to create
1880 a new row or modify or delete an
1881 existing row in this table."
1882 DEFVAL { active }
1883 ::= {atmTrafficDescrParamEntry 9}
1884
1885 atmServiceCategory OBJECT-TYPE
1886 SYNTAX AtmServiceCategory
1887 MAX-ACCESS read-create
1888 STATUS current
1889 DESCRIPTION
1890 "The ATM service category."
1891 DEFVAL { ubr }
1892 ::= { atmTrafficDescrParamEntry 10}
1893
1894
1895 atmTrafficFrameDiscard OBJECT-TYPE
1896 SYNTAX TruthValue
1897
1898
1899
1900 <span class="grey">Tesink Standards Track [Page 34]</span></pre>
1901 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-35" ></span>
1902 <span class="grey"><a href="./rfc2515">RFC 2515</a> ATM Management Objects February 1999</span>
1903
1904
1905 MAX-ACCESS read-create
1906 STATUS current
1907 DESCRIPTION
1908 "If set to 'true', this object indicates that the network
1909 is requested to treat data for this connection, in the
1910 given direction, as frames (e.g. AAL5 CPCS_PDU's) rather
1911 than as individual cells. While the precise
1912 implementation is network-specific, this treatment may
1913 for example involve discarding entire frames during
1914 congestion, rather than a few cells from many frames."
1915 DEFVAL { true }
1916 ::= { atmTrafficDescrParamEntry 11 }
1917
1918 -- ATM Interface Virtual Path Link (VPL) Table
1919
1920 -- This table contains configuration and state
1921 -- information of a bi-directional Virtual Path Link
1922 -- (VPL)
1923
1924 -- This table can be used to create, delete or modify
1925 -- a VPL that is terminated in an ATM host or switch.
1926 -- This table can also be used to create, delete or
1927 -- modify a VPL which is cross-connected to another
1928 -- VPL.
1929
1930 -- In the example below, the traffic flows on the receive
1931 -- and transmit directions of the VPLs are characterized
1932 -- by atmVplReceiveTrafficDescrIndex and
1933 -- atmVplTransmitTrafficDescrIndex respectively.
1934 -- The cross-connected VPLs are identified by
1935 -- atmVplCrossConnectIdentifier.
1936
1937
1938
1939 -- ________________________________
1940 -- | |
1941 -- VPL | ATM Host, Switch, or Network | VPL
1942 -- receive | | receive
1943 -- ========&gt; X X &lt;=======
1944 -- &lt;======== X X ========&gt;
1945 -- transmit | | transmit
1946 -- |______________________________|
1947
1948
1949
1950 -- The ATM Interface VPL Table
1951
1952
1953
1954
1955
1956 <span class="grey">Tesink Standards Track [Page 35]</span></pre>
1957 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-36" ></span>
1958 <span class="grey"><a href="./rfc2515">RFC 2515</a> ATM Management Objects February 1999</span>
1959
1960
1961 atmVplTable OBJECT-TYPE
1962 SYNTAX SEQUENCE OF AtmVplEntry
1963 MAX-ACCESS not-accessible
1964 STATUS current
1965 DESCRIPTION
1966 "The Virtual Path Link (VPL) table. A
1967 bi-directional VPL is modeled as one entry
1968 in this table. This table can be used for
1969 PVCs, SVCs and Soft PVCs.
1970 Entries are not present in this table for
1971 the VPIs used by entries in the atmVclTable."
1972 ::= { atmMIBObjects 6}
1973
1974 atmVplEntry OBJECT-TYPE
1975 SYNTAX AtmVplEntry
1976 MAX-ACCESS not-accessible
1977 STATUS current
1978 DESCRIPTION
1979 "An entry in the VPL table. This entry is
1980 used to model a bi-directional VPL.
1981 To create a VPL at an ATM interface,
1982 either of the following procedures are used:
1983
1984 Negotiated VPL establishment
1985
1986 (1) The management application creates
1987 a VPL entry in the atmVplTable
1988 by setting atmVplRowStatus to createAndWait(5).
1989 This may fail for the following reasons:
1990 - The selected VPI value is unavailable,
1991 - The selected VPI value is in use.
1992 Otherwise, the agent creates a row and
1993 reserves the VPI value on that port.
1994
1995 (2) The manager selects an existing row(s) in the
1996 atmTrafficDescrParamTable,
1997 thereby, selecting a set of self-consistent
1998 ATM traffic parameters and the service category
1999 for receive and transmit directions of the VPL.
2000
2001 (2a) If no suitable row(s) in the
2002 atmTrafficDescrParamTable exists,
2003 the manager must create a new row(s)
2004 in that table.
2005
2006 (2b) The manager characterizes the VPL's traffic
2007 parameters through setting the
2008 atmVplReceiveTrafficDescrIndex and the
2009
2010
2011
2012 <span class="grey">Tesink Standards Track [Page 36]</span></pre>
2013 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-37" ></span>
2014 <span class="grey"><a href="./rfc2515">RFC 2515</a> ATM Management Objects February 1999</span>
2015
2016
2017 atmVplTransmitTrafficDescrIndex values
2018 in the VPL table, which point to the rows
2019 containing desired ATM traffic parameter values
2020 in the atmTrafficDescrParamTable. The agent
2021 will check the availability of resources and
2022 may refuse the request.
2023 If the transmit and receive service categories
2024 are inconsistent, the agent should refuse the
2025 request.
2026
2027 (3) The manager activates the VPL by setting the
2028 the atmVplRowStatus to active(1).
2029 If this set is successful, the agent has
2030 reserved the resources to satisfy the requested
2031 traffic parameter values and the service category
2032 for that VPL.
2033
2034 (4) If the VPL terminates a VPC in the ATM host
2035 or switch, the manager turns on the
2036 atmVplAdminStatus to up(1) to turn the VPL
2037 traffic flow on. Otherwise, the
2038 atmVpCrossConnectTable must be used
2039 to cross-connect the VPL to another VPL(s)
2040 in an ATM switch or network.
2041
2042 One-Shot VPL Establishment
2043
2044 A VPL may also be established in one step by a
2045 set-request with all necessary VPL parameter
2046 values and atmVplRowStatus set to createAndGo(4).
2047
2048 In contrast to the negotiated VPL establishment
2049 which allows for detailed error checking
2050 (i.e., set errors are explicitly linked to
2051 particular resource acquisition failures),
2052 the one-shot VPL establishment
2053 performs the setup on one operation but
2054 does not have the advantage of step-wise
2055 error checking.
2056
2057 VPL Retirement
2058
2059 A VPL is released by setting atmVplRowStatus to
2060 destroy(6), and the agent may release all
2061 associated resources."
2062 INDEX {ifIndex, atmVplVpi }
2063 ::= { atmVplTable 1}
2064
2065
2066
2067
2068 <span class="grey">Tesink Standards Track [Page 37]</span></pre>
2069 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-38" ></span>
2070 <span class="grey"><a href="./rfc2515">RFC 2515</a> ATM Management Objects February 1999</span>
2071
2072
2073 AtmVplEntry ::= SEQUENCE {
2074 atmVplVpi AtmVpIdentifier,
2075 atmVplAdminStatus AtmVorXAdminStatus,
2076 atmVplOperStatus AtmVorXOperStatus,
2077 atmVplLastChange AtmVorXLastChange,
2078 atmVplReceiveTrafficDescrIndex
2079 AtmTrafficDescrParamIndex,
2080 atmVplTransmitTrafficDescrIndex
2081 AtmTrafficDescrParamIndex,
2082 atmVplCrossConnectIdentifier INTEGER,
2083 atmVplRowStatus RowStatus,
2084 atmVplCastType AtmConnCastType,
2085 atmVplConnKind AtmConnKind
2086 }
2087
2088
2089 atmVplVpi OBJECT-TYPE
2090 SYNTAX AtmVpIdentifier
2091 MAX-ACCESS not-accessible
2092 STATUS current
2093 DESCRIPTION
2094 "The VPI value of the VPL."
2095 ::= { atmVplEntry 1}
2096
2097 atmVplAdminStatus OBJECT-TYPE
2098 SYNTAX AtmVorXAdminStatus
2099 MAX-ACCESS read-create
2100 STATUS current
2101 DESCRIPTION
2102 "This object is instanciated only for a VPL
2103 which terminates a VPC (i.e., one which is
2104 NOT cross-connected to other VPLs).
2105 Its value specifies the desired
2106 administrative state of the VPL."
2107 DEFVAL { down }
2108 ::= { atmVplEntry 2}
2109
2110 atmVplOperStatus OBJECT-TYPE
2111 SYNTAX AtmVorXOperStatus
2112 MAX-ACCESS read-only
2113 STATUS current
2114 DESCRIPTION
2115 "The current operational status of the VPL."
2116 ::= { atmVplEntry 3}
2117
2118 atmVplLastChange OBJECT-TYPE
2119 SYNTAX AtmVorXLastChange
2120 MAX-ACCESS read-only
2121
2122
2123
2124 <span class="grey">Tesink Standards Track [Page 38]</span></pre>
2125 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-39" ></span>
2126 <span class="grey"><a href="./rfc2515">RFC 2515</a> ATM Management Objects February 1999</span>
2127
2128
2129 STATUS current
2130 DESCRIPTION
2131 "The value of sysUpTime at the time this
2132 VPL entered its current operational state."
2133 ::= { atmVplEntry 4 }
2134
2135 atmVplReceiveTrafficDescrIndex OBJECT-TYPE
2136 SYNTAX AtmTrafficDescrParamIndex
2137 MAX-ACCESS read-create
2138 STATUS current
2139 DESCRIPTION
2140 "The value of this object identifies the row
2141 in the atmTrafficDescrParamTable which
2142 applies to the receive direction of the VPL."
2143 DEFVAL { 0 }
2144 ::= { atmVplEntry 5}
2145
2146 atmVplTransmitTrafficDescrIndex OBJECT-TYPE
2147 SYNTAX AtmTrafficDescrParamIndex
2148 MAX-ACCESS read-create
2149 STATUS current
2150 DESCRIPTION
2151 "The value of this object identifies the row
2152 in the atmTrafficDescrParamTable which
2153 applies to the transmit direction of the VPL."
2154 DEFVAL { 0 }
2155 ::= { atmVplEntry 6}
2156
2157 atmVplCrossConnectIdentifier OBJECT-TYPE
2158 SYNTAX INTEGER (0..2147483647)
2159 MAX-ACCESS read-only
2160 STATUS current
2161 DESCRIPTION
2162 "This object is instantiated only for a VPL
2163 which is cross-connected to other VPLs
2164 that belong to the same VPC. All such
2165 associated VPLs have the same value of this
2166 object, and all their cross-connections are
2167 identified either by entries that are indexed
2168 by the same value of atmVpCrossConnectIndex in
2169 the atmVpCrossConnectTable of this MIB module or by
2170 the same value of the cross-connect index in
2171 the cross-connect table for SVCs and Soft PVCs
2172 (defined in a separate MIB module).
2173 At no time should entries in these respective
2174 cross-connect tables exist simultaneously
2175 with the same cross-connect index value.
2176
2177
2178
2179
2180 <span class="grey">Tesink Standards Track [Page 39]</span></pre>
2181 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-40" ></span>
2182 <span class="grey"><a href="./rfc2515">RFC 2515</a> ATM Management Objects February 1999</span>
2183
2184
2185 The value of this object is initialized by the
2186 agent after the associated entries in the
2187 atmVpCrossConnectTable have been created."
2188 ::= {atmVplEntry 7}
2189
2190 atmVplRowStatus OBJECT-TYPE
2191 SYNTAX RowStatus
2192 MAX-ACCESS read-create
2193 STATUS current
2194 DESCRIPTION
2195 "This object is used to create, delete
2196 or modify a row in this table.
2197 To create a new VCL, this object is
2198 initially set to 'createAndWait' or
2199 'createAndGo'. This object should not be
2200 set to 'active' unless the following columnar
2201 objects have been set to their desired value
2202 in this row:
2203 atmVplReceiveTrafficDescrIndex and
2204 atmVplTransmitTrafficDescrIndex.
2205 The DESCRIPTION of atmVplEntry provides
2206 further guidance to row treatment in this table."
2207 DEFVAL { createAndWait }
2208 ::= {atmVplEntry 8}
2209
2210 atmVplCastType OBJECT-TYPE
2211 SYNTAX AtmConnCastType
2212 MAX-ACCESS read-create
2213 STATUS current
2214 DESCRIPTION
2215 "The connection topology type."
2216 DEFVAL { p2p }
2217 ::= {atmVplEntry 9}
2218
2219 atmVplConnKind OBJECT-TYPE
2220 SYNTAX AtmConnKind
2221 MAX-ACCESS read-create
2222 STATUS current
2223 DESCRIPTION
2224 "The use of call control."
2225 DEFVAL { pvc }
2226 ::= {atmVplEntry 10}
2227
2228 -- ATM Interface Virtual Channel Link (VCL) Table
2229
2230 -- This table contains configuration and state
2231 -- information of a bi-directional Virtual Channel
2232 -- Link (VCL) at an ATM interface.
2233
2234
2235
2236 <span class="grey">Tesink Standards Track [Page 40]</span></pre>
2237 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-41" ></span>
2238 <span class="grey"><a href="./rfc2515">RFC 2515</a> ATM Management Objects February 1999</span>
2239
2240
2241 -- This table can be used to create, delete or modify
2242 -- a VCL that is terminated in an ATM host or switch.
2243 -- This table can also be
2244 -- used to create, delete or modify a VCL that is
2245 -- cross-connected to another VCL.
2246
2247
2248 -- The ATM Interface VCL Table
2249
2250
2251 atmVclTable OBJECT-TYPE
2252 SYNTAX SEQUENCE OF AtmVclEntry
2253 MAX-ACCESS not-accessible
2254 STATUS current
2255 DESCRIPTION
2256 "The Virtual Channel Link (VCL) table. A
2257 bi-directional VCL is modeled as one entry
2258 in this table. This table can be used for
2259 PVCs, SVCs and Soft PVCs."
2260 ::= { atmMIBObjects 7}
2261
2262 atmVclEntry OBJECT-TYPE
2263 SYNTAX AtmVclEntry
2264 MAX-ACCESS not-accessible
2265 STATUS current
2266 DESCRIPTION
2267 "An entry in the VCL table. This entry is
2268 used to model a bi-directional VCL.
2269 To create a VCL at an ATM interface,
2270 either of the following procedures are used:
2271
2272 Negotiated VCL establishment
2273
2274 (1) The management application creates
2275 a VCL entry in the atmVclTable
2276 by setting atmVclRowStatus to createAndWait(5).
2277 This may fail for the following reasons:
2278 - The selected VPI/VCI values are unavailable,
2279 - The selected VPI/VCI values are in use.
2280 Otherwise, the agent creates a row and
2281 reserves the VPI/VCI values on that port.
2282
2283 (2) The manager selects an existing row(s) in the
2284 atmTrafficDescrParamTable,
2285 thereby, selecting a set of self-consistent
2286 ATM traffic parameters and the service category
2287 for receive and transmit directions of the VCL.
2288
2289
2290
2291
2292 <span class="grey">Tesink Standards Track [Page 41]</span></pre>
2293 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-42" ></span>
2294 <span class="grey"><a href="./rfc2515">RFC 2515</a> ATM Management Objects February 1999</span>
2295
2296
2297 (2a) If no suitable row(s) in the
2298 atmTrafficDescrParamTable exists,
2299 the manager must create a new row(s)
2300 in that table.
2301
2302 (2b) The manager characterizes the VCL's traffic
2303 parameters through setting the
2304 atmVclReceiveTrafficDescrIndex and the
2305 atmVclTransmitTrafficDescrIndex values
2306 in the VCL table, which point to the rows
2307 containing desired ATM traffic parameter values
2308 in the atmTrafficDescrParamTable. The agent
2309 will check the availability of resources and
2310 may refuse the request.
2311 If the transmit and receive service categories
2312 are inconsistent, the agent should refuse the
2313 request.
2314
2315 (3) The manager activates the VCL by setting the
2316 the atmVclRowStatus to active(1) (for
2317 requirements on this activation see the
2318 description of atmVclRowStatus).
2319 If this set is successful, the agent has
2320 reserved the resources to satisfy the requested
2321 traffic parameter values and the service category
2322 for that VCL.
2323 (4) If the VCL terminates a VCC in the ATM host
2324 or switch, the manager turns on the
2325 atmVclAdminStatus to up(1) to turn the VCL
2326 traffic flow on. Otherwise, the
2327 atmVcCrossConnectTable must be used
2328 to cross-connect the VCL to another VCL(s)
2329 in an ATM switch or network.
2330
2331 One-Shot VCL Establishment
2332
2333 A VCL may also be established in one step by a
2334 set-request with all necessary VCL parameter
2335 values and atmVclRowStatus set to createAndGo(4).
2336
2337 In contrast to the negotiated VCL establishment
2338 which allows for detailed error checking
2339 (i.e., set errors are explicitly linked to
2340 particular resource acquisition failures),
2341 the one-shot VCL establishment
2342 performs the setup on one operation but
2343 does not have the advantage of step-wise
2344 error checking.
2345
2346
2347
2348 <span class="grey">Tesink Standards Track [Page 42]</span></pre>
2349 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-43" ></span>
2350 <span class="grey"><a href="./rfc2515">RFC 2515</a> ATM Management Objects February 1999</span>
2351
2352
2353 VCL Retirement
2354
2355 A VCL is released by setting atmVclRowStatus to
2356 destroy(6), and the agent may release all
2357 associated resources."
2358 INDEX {ifIndex, atmVclVpi, atmVclVci }
2359 ::= { atmVclTable 1}
2360
2361 AtmVclEntry ::= SEQUENCE {
2362 atmVclVpi AtmVpIdentifier,
2363 atmVclVci AtmVcIdentifier,
2364 atmVclAdminStatus AtmVorXAdminStatus,
2365 atmVclOperStatus AtmVorXOperStatus,
2366 atmVclLastChange AtmVorXLastChange,
2367 atmVclReceiveTrafficDescrIndex
2368 AtmTrafficDescrParamIndex,
2369 atmVclTransmitTrafficDescrIndex
2370 AtmTrafficDescrParamIndex,
2371 atmVccAalType INTEGER,
2372 atmVccAal5CpcsTransmitSduSize INTEGER,
2373 atmVccAal5CpcsReceiveSduSize INTEGER,
2374 atmVccAal5EncapsType INTEGER,
2375 atmVclCrossConnectIdentifier INTEGER,
2376 atmVclRowStatus RowStatus,
2377 atmVclCastType AtmConnCastType,
2378 atmVclConnKind AtmConnKind
2379 }
2380
2381 atmVclVpi OBJECT-TYPE
2382 SYNTAX AtmVpIdentifier
2383 MAX-ACCESS not-accessible
2384 STATUS current
2385 DESCRIPTION
2386 "The VPI value of the VCL."
2387 ::= { atmVclEntry 1}
2388
2389 atmVclVci OBJECT-TYPE
2390 SYNTAX AtmVcIdentifier
2391 MAX-ACCESS not-accessible
2392 STATUS current
2393 DESCRIPTION
2394 "The VCI value of the VCL."
2395 ::= { atmVclEntry 2}
2396
2397 atmVclAdminStatus OBJECT-TYPE
2398 SYNTAX AtmVorXAdminStatus
2399 MAX-ACCESS read-create
2400 STATUS current
2401
2402
2403
2404 <span class="grey">Tesink Standards Track [Page 43]</span></pre>
2405 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-44" ></span>
2406 <span class="grey"><a href="./rfc2515">RFC 2515</a> ATM Management Objects February 1999</span>
2407
2408
2409 DESCRIPTION
2410 "This object is instanciated only for a VCL which
2411 terminates a VCC (i.e., one which is NOT
2412 cross-connected to other VCLs). Its value
2413 specifies the desired administrative state of
2414 the VCL."
2415 DEFVAL { down }
2416 ::= { atmVclEntry 3}
2417
2418 atmVclOperStatus OBJECT-TYPE
2419 SYNTAX AtmVorXOperStatus
2420 MAX-ACCESS read-only
2421 STATUS current
2422 DESCRIPTION
2423 "The current operational status of the VCL."
2424 ::= { atmVclEntry 4}
2425
2426 atmVclLastChange OBJECT-TYPE
2427 SYNTAX AtmVorXLastChange
2428 MAX-ACCESS read-only
2429 STATUS current
2430 DESCRIPTION
2431 "The value of sysUpTime at the time this VCL
2432 entered its current operational state."
2433 ::= { atmVclEntry 5 }
2434
2435 atmVclReceiveTrafficDescrIndex OBJECT-TYPE
2436 SYNTAX AtmTrafficDescrParamIndex
2437 MAX-ACCESS read-create
2438 STATUS current
2439 DESCRIPTION
2440 "The value of this object identifies the row
2441 in the ATM Traffic Descriptor Table which
2442 applies to the receive direction of this VCL."
2443 DEFVAL { 0 }
2444 ::= { atmVclEntry 6}
2445
2446 atmVclTransmitTrafficDescrIndex OBJECT-TYPE
2447 SYNTAX AtmTrafficDescrParamIndex
2448 MAX-ACCESS read-create
2449 STATUS current
2450 DESCRIPTION
2451 "The value of this object identifies the row
2452 of the ATM Traffic Descriptor Table which applies
2453 to the transmit direction of this VCL."
2454 DEFVAL { 0 }
2455 ::= { atmVclEntry 7}
2456
2457
2458
2459
2460 <span class="grey">Tesink Standards Track [Page 44]</span></pre>
2461 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-45" ></span>
2462 <span class="grey"><a href="./rfc2515">RFC 2515</a> ATM Management Objects February 1999</span>
2463
2464
2465 atmVccAalType OBJECT-TYPE
2466 SYNTAX INTEGER {
2467 aal1(1),
2468 aal34(2),
2469 aal5(3),
2470 other(4),
2471 unknown(5),
2472 aal2(6)
2473 }
2474 MAX-ACCESS read-create
2475 STATUS current
2476 DESCRIPTION
2477 "An instance of this object only exists when the
2478 local VCL end-point is also the VCC end-point,
2479 and AAL is in use.
2480 The type of AAL used on this VCC.
2481 The AAL type includes AAL1, AAL2, AAL3/4,
2482 and AAL5. The other(4) may be user-defined
2483 AAL type. The unknown type indicates that
2484 the AAL type cannot be determined."
2485 DEFVAL { aal5 }
2486 ::= { atmVclEntry 8 }
2487
2488 atmVccAal5CpcsTransmitSduSize OBJECT-TYPE
2489 SYNTAX INTEGER (1..65535)
2490 MAX-ACCESS read-create
2491 STATUS current
2492 DESCRIPTION
2493 "An instance of this object only exists when the
2494 local VCL end-point is also the VCC end-point,
2495 and AAL5 is in use.
2496 The maximum AAL5 CPCS SDU size in octets that is
2497 supported on the transmit direction of this VCC."
2498 DEFVAL { 9188 }
2499 ::= { atmVclEntry 9 }
2500
2501 atmVccAal5CpcsReceiveSduSize OBJECT-TYPE
2502 SYNTAX INTEGER (1..65535)
2503 MAX-ACCESS read-create
2504 STATUS current
2505 DESCRIPTION
2506 "An instance of this object only exists when the
2507 local VCL end-point is also the VCC end-point,
2508 and AAL5 is in use.
2509 The maximum AAL5 CPCS SDU size in octets that is
2510 supported on the receive direction of this VCC."
2511 DEFVAL { 9188 }
2512 ::= { atmVclEntry 10 }
2513
2514
2515
2516 <span class="grey">Tesink Standards Track [Page 45]</span></pre>
2517 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-46" ></span>
2518 <span class="grey"><a href="./rfc2515">RFC 2515</a> ATM Management Objects February 1999</span>
2519
2520
2521 atmVccAal5EncapsType OBJECT-TYPE
2522 SYNTAX INTEGER {
2523 vcMultiplexRoutedProtocol(1),
2524 vcMultiplexBridgedProtocol8023(2),
2525 vcMultiplexBridgedProtocol8025(3),
2526 vcMultiplexBridgedProtocol8026(4),
2527 vcMultiplexLANemulation8023(5),
2528 vcMultiplexLANemulation8025(6),
2529 llcEncapsulation(7),
2530 multiprotocolFrameRelaySscs(8),
2531 other(9),
2532 unknown(10)
2533 }
2534 MAX-ACCESS read-create
2535 STATUS current
2536 DESCRIPTION
2537 "An instance of this object only exists when the
2538 local VCL end-point is also the VCC end-point,
2539 and AAL5 is in use.
2540 The type of data encapsulation used over
2541 the AAL5 SSCS layer. The definitions reference
2542 <a href="./rfc1483">RFC 1483</a> Multiprotocol Encapsulation
2543 over ATM AAL5 and to the ATM Forum
2544 LAN Emulation specification."
2545 DEFVAL { llcEncapsulation }
2546 ::= { atmVclEntry 11 }
2547
2548 atmVclCrossConnectIdentifier OBJECT-TYPE
2549 SYNTAX INTEGER (0..2147483647)
2550 MAX-ACCESS read-only
2551 STATUS current
2552 DESCRIPTION
2553 "This object is instantiated only for a VCL
2554 which is cross-connected to other VCLs
2555 that belong to the same VCC. All such
2556 associated VCLs have the same value of this
2557 object, and all their cross-connections are
2558 identified either by entries that are indexed
2559 by the same value of atmVcCrossConnectIndex in
2560 the atmVcCrossConnectTable of this MIB module or by
2561 the same value of the cross-connect index in
2562 the cross-connect table for SVCs and Soft PVCs
2563 (defined in a separate MIB module).
2564
2565 At no time should entries in these respective
2566 cross-connect tables exist simultaneously
2567 with the same cross-connect index value.
2568
2569
2570
2571
2572 <span class="grey">Tesink Standards Track [Page 46]</span></pre>
2573 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-47" ></span>
2574 <span class="grey"><a href="./rfc2515">RFC 2515</a> ATM Management Objects February 1999</span>
2575
2576
2577 The value of this object is initialized by the
2578 agent after the associated entries in the
2579 atmVcCrossConnectTable have been created."
2580 ::= {atmVclEntry 12}
2581
2582 atmVclRowStatus OBJECT-TYPE
2583 SYNTAX RowStatus
2584 MAX-ACCESS read-create
2585 STATUS current
2586 DESCRIPTION
2587 "This object is used to create, delete or
2588 modify a row in this table. To create
2589 a new VCL, this object is initially set
2590 to 'createAndWait' or 'createAndGo'.
2591 This object should not be
2592 set to 'active' unless the following columnar
2593 objects have been set to their desired value
2594 in this row:
2595 atmVclReceiveTrafficDescrIndex,
2596 atmVclTransmitTrafficDescrIndex.
2597 In addition, if the local VCL end-point
2598 is also the VCC end-point:
2599 atmVccAalType.
2600 In addition, for AAL5 connections only:
2601 atmVccAal5CpcsTransmitSduSize,
2602 atmVccAal5CpcsReceiveSduSize, and
2603 atmVccAal5EncapsType. (The existence
2604 of these objects imply the AAL connection type.).
2605 The DESCRIPTION of atmVclEntry provides
2606 further guidance to row treatment in this table."
2607 DEFVAL { createAndWait }
2608 ::= {atmVclEntry 13}
2609
2610 atmVclCastType OBJECT-TYPE
2611 SYNTAX AtmConnCastType
2612 MAX-ACCESS read-create
2613 STATUS current
2614 DESCRIPTION
2615 "The connection topology type."
2616 DEFVAL { p2p }
2617 ::= {atmVclEntry 14}
2618
2619
2620 atmVclConnKind OBJECT-TYPE
2621 SYNTAX AtmConnKind
2622 MAX-ACCESS read-create
2623 STATUS current
2624 DESCRIPTION
2625
2626
2627
2628 <span class="grey">Tesink Standards Track [Page 47]</span></pre>
2629 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-48" ></span>
2630 <span class="grey"><a href="./rfc2515">RFC 2515</a> ATM Management Objects February 1999</span>
2631
2632
2633 "The use of call control."
2634 DEFVAL { pvc }
2635 ::= {atmVclEntry 15}
2636
2637
2638 -- ATM Virtual Path (VP) Cross Connect Table
2639
2640 -- This table contains configuration and state
2641 -- information of point-to-point,
2642 -- point-to-multipoint, or multipoint-to-multipoint
2643 -- VP cross-connects for PVCs.
2644
2645 -- This table has read-create access and can be used
2646 -- to cross-connect the VPLs together in an ATM switch
2647 -- or network. The atmVpCrossConnectIndex
2648 -- is used to associate the related
2649 -- VPLs that are cross-connected together.
2650
2651 -- The ATM VP Cross Connect Table
2652 -- models each bi-directional VPC
2653 -- cross-connect as a set of entries in
2654 -- the atmVpCrossConnectTable. A
2655 -- point-to-point VPC cross-connect is modeled
2656 -- as one entry; a point-to-multipoint (N leafs) VPC
2657 -- cross-connect as N entries in this table; and
2658 -- a multipoint-to-multipoint (N parties) VPC cross-
2659 -- connect as N(N-1)/2 entries in this table.
2660 -- In the latter cases, all the N (or N(N-1)/2) entries
2661 -- are associated with a single VPC cross-connect by
2662 -- having the same value of atmVpCrossConnectIndex.
2663
2664
2665 -- _________________________________________
2666 -- | |
2667 -- Low | ATM Switch or Network | High
2668 -- port| | port
2669 -- _____|&gt;&gt; from low to high VPC traffic flow &gt;&gt;|______
2670 -- |&lt;&lt; from high to low VPC traffic flow &lt;&lt;|
2671 -- | |
2672 -- |_______________________________________|
2673 --
2674
2675 -- The terms low and high are chosen to represent
2676 -- numerical ordering of the two interfaces associated
2677 -- with a VPC cross-connect. That is, the ATM interface
2678 -- with the lower value of ifIndex is termed 'low',
2679 -- while the other ATM interface associated with the
2680 -- VPC cross-connect is termed 'high'. This terminology
2681
2682
2683
2684 <span class="grey">Tesink Standards Track [Page 48]</span></pre>
2685 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-49" ></span>
2686 <span class="grey"><a href="./rfc2515">RFC 2515</a> ATM Management Objects February 1999</span>
2687
2688
2689 -- is used to provide directional information; for
2690 -- example, the atmVpCrossConnectL2HOperStatus applies
2691 -- to the low-&gt;high direction, and
2692 -- atmVpCrossConnectH2LOperStatus applies to the
2693 -- high-&gt;low direction, as illustrated above.
2694
2695
2696
2697
2698 atmVpCrossConnectIndexNext OBJECT-TYPE
2699 SYNTAX INTEGER (0..2147483647)
2700 MAX-ACCESS read-only
2701 STATUS current
2702 DESCRIPTION
2703 "This object contains an appropriate value to
2704 be used for atmVpCrossConnectIndex when creating
2705 entries in the atmVpCrossConnectTable. The value
2706 0 indicates that no unassigned entries are
2707 available. To obtain the atmVpCrossConnectIndex
2708 value for a new entry, the manager issues a
2709 management protocol retrieval operation to obtain
2710 the current value of this object. After each
2711 retrieval, the agent should modify the value to
2712 the next unassigned index.
2713 After a manager retrieves a value the agent will
2714 determine through its local policy when this index
2715 value will be made available for reuse."
2716 ::= { atmMIBObjects 8 }
2717
2718
2719 -- The ATM VP Cross Connect Table
2720
2721
2722 atmVpCrossConnectTable OBJECT-TYPE
2723 SYNTAX SEQUENCE OF AtmVpCrossConnectEntry
2724 MAX-ACCESS not-accessible
2725 STATUS current
2726 DESCRIPTION
2727 "The ATM VP Cross Connect table for PVCs.
2728 An entry in this table models two
2729 cross-connected VPLs.
2730 Each VPL must have its atmConnKind set
2731 to pvc(1)."
2732 ::= { atmMIBObjects 9 }
2733
2734
2735 atmVpCrossConnectEntry OBJECT-TYPE
2736 SYNTAX AtmVpCrossConnectEntry
2737
2738
2739
2740 <span class="grey">Tesink Standards Track [Page 49]</span></pre>
2741 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-50" ></span>
2742 <span class="grey"><a href="./rfc2515">RFC 2515</a> ATM Management Objects February 1999</span>
2743
2744
2745 MAX-ACCESS not-accessible
2746 STATUS current
2747 DESCRIPTION
2748 "An entry in the ATM VP Cross Connect table.
2749 This entry is used to model a bi-directional
2750 ATM VP cross-connect which cross-connects
2751 two VPLs.
2752
2753 Step-wise Procedures to set up a VP Cross-connect
2754
2755 Once the entries in the atmVplTable are created,
2756 the following procedures are used
2757 to cross-connect the VPLs together.
2758
2759 (1) The manager obtains a unique
2760 atmVpCrossConnectIndex by reading the
2761 atmVpCrossConnectIndexNext object.
2762
2763 (2) Next, the manager creates a set of one
2764 or more rows in the ATM VP Cross Connect
2765 Table, one for each cross-connection between
2766 two VPLs. Each row is indexed by the ATM
2767 interface port numbers and VPI values of the
2768 two ends of that cross-connection.
2769 This set of rows specifies the topology of the
2770 VPC cross-connect and is identified by a single
2771 value of atmVpCrossConnectIndex.
2772
2773 Negotiated VP Cross-Connect Establishment
2774
2775 (2a) The manager creates a row in this table by
2776 setting atmVpCrossConnectRowStatus to
2777 createAndWait(5). The agent checks the
2778 requested topology and the mutual sanity of
2779 the ATM traffic parameters and
2780 service categories, i.e., the row creation
2781 fails if:
2782 - the requested topology is incompatible with
2783 associated values of atmVplCastType,
2784 - the requested topology is not supported
2785 by the agent,
2786 - the traffic/service category parameter values
2787 associated with the requested row are
2788 incompatible with those of already existing
2789 rows for this VP cross-connect.
2790 [For example, for setting up
2791 a point-to-point VP cross-connect, the
2792 ATM traffic parameters in the receive direction
2793
2794
2795
2796 <span class="grey">Tesink Standards Track [Page 50]</span></pre>
2797 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-51" ></span>
2798 <span class="grey"><a href="./rfc2515">RFC 2515</a> ATM Management Objects February 1999</span>
2799
2800
2801 of a VPL at the low end of the cross-connect
2802 must equal to the traffic parameters in the
2803 transmit direction of the other VPL at the
2804 high end of the cross-connect,
2805 otherwise, the row creation fails.]
2806 The agent also checks for internal errors
2807 in building the cross-connect.
2808
2809 The atmVpCrossConnectIndex values in the
2810 corresponding atmVplTable rows are filled
2811 in by the agent at this point.
2812
2813 (2b) The manager promotes the row in the
2814 atmVpCrossConnectTable by setting
2815 atmVpCrossConnectRowStatus to active(1). If
2816 this set is successful, the agent has reserved
2817 the resources specified by the ATM traffic
2818 parameter and Service category values
2819 for each direction of the VP cross-connect
2820 in an ATM switch or network.
2821
2822 (3) The manager sets the
2823 atmVpCrossConnectAdminStatus to up(1) in all
2824 rows of this VP cross-connect to turn the
2825 traffic flow on.
2826
2827
2828 One-Shot VP Cross-Connect Establishment
2829
2830 A VP cross-connect may also be established in
2831 one step by a set-request with all necessary
2832 parameter values and atmVpCrossConnectRowStatus
2833 set to createAndGo(4).
2834
2835 In contrast to the negotiated VP cross-connect
2836 establishment which allows for detailed error
2837 checking (i.e., set errors are explicitly linked
2838 to particular resource acquisition failures),
2839 the one-shot VP cross-connect establishment
2840 performs the setup on one operation but does not
2841 have the advantage of step-wise error checking.
2842
2843 VP Cross-Connect Retirement
2844
2845 A VP cross-connect identified by a particular
2846 value of atmVpCrossConnectIndex is released by:
2847
2848 (1) Setting atmVpCrossConnectRowStatus of all
2849
2850
2851
2852 <span class="grey">Tesink Standards Track [Page 51]</span></pre>
2853 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-52" ></span>
2854 <span class="grey"><a href="./rfc2515">RFC 2515</a> ATM Management Objects February 1999</span>
2855
2856
2857 rows identified by this value of
2858 atmVpCrossConnectIndex to destroy(6).
2859 The agent may release all
2860 associated resources, and the
2861 atmVpCrossConnectIndex values in the
2862 corresponding atmVplTable row are removed.
2863 Note that a situation when only a subset of
2864 the associated rows are deleted corresponds
2865 to a VP topology change.
2866
2867 (2) After deletion of the appropriate
2868 atmVpCrossConnectEntries, the manager may
2869 set atmVplRowStatus to destroy(6) the
2870 associated VPLs. The agent releases
2871 the resources and removes the associated
2872 rows in the atmVplTable.
2873
2874 VP Cross-connect Reconfiguration
2875
2876 At the discretion of the agent, a VP
2877 cross-connect may be reconfigured by
2878 adding and/or deleting leafs to/from
2879 the VP topology as per the VP cross-connect
2880 establishment/retirement procedures.
2881 Reconfiguration of traffic/service category parameter
2882 values requires release of the VP cross-connect
2883 before those parameter values may by changed
2884 for individual VPLs."
2885 INDEX { atmVpCrossConnectIndex,
2886 atmVpCrossConnectLowIfIndex,
2887 atmVpCrossConnectLowVpi,
2888 atmVpCrossConnectHighIfIndex,
2889 atmVpCrossConnectHighVpi }
2890 ::= { atmVpCrossConnectTable 1 }
2891
2892 AtmVpCrossConnectEntry ::= SEQUENCE {
2893 atmVpCrossConnectIndex INTEGER,
2894 atmVpCrossConnectLowIfIndex InterfaceIndex,
2895 atmVpCrossConnectLowVpi AtmVpIdentifier,
2896 atmVpCrossConnectHighIfIndex InterfaceIndex,
2897 atmVpCrossConnectHighVpi AtmVpIdentifier,
2898 atmVpCrossConnectAdminStatus AtmVorXAdminStatus,
2899 atmVpCrossConnectL2HOperStatus AtmVorXOperStatus,
2900 atmVpCrossConnectH2LOperStatus AtmVorXOperStatus,
2901 atmVpCrossConnectL2HLastChange AtmVorXLastChange,
2902 atmVpCrossConnectH2LLastChange AtmVorXLastChange,
2903 atmVpCrossConnectRowStatus RowStatus
2904 }
2905
2906
2907
2908 <span class="grey">Tesink Standards Track [Page 52]</span></pre>
2909 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-53" ></span>
2910 <span class="grey"><a href="./rfc2515">RFC 2515</a> ATM Management Objects February 1999</span>
2911
2912
2913 atmVpCrossConnectIndex OBJECT-TYPE
2914 SYNTAX INTEGER (1..2147483647)
2915 MAX-ACCESS not-accessible
2916 STATUS current
2917 DESCRIPTION
2918 "A unique value to identify this VP cross-connect.
2919 For each VPL associated with this cross-connect,
2920 the agent reports this cross-connect index value
2921 in the atmVplCrossConnectIdentifier attribute of
2922 the corresponding atmVplTable entries."
2923 ::= { atmVpCrossConnectEntry 1 }
2924
2925 atmVpCrossConnectLowIfIndex OBJECT-TYPE
2926 SYNTAX InterfaceIndex
2927 MAX-ACCESS not-accessible
2928 STATUS current
2929 DESCRIPTION
2930 "The ifIndex value of the ATM interface for
2931 this VP cross-connect. The term low implies
2932 that this ATM interface has the numerically lower
2933 ifIndex value than the other ATM interface
2934 identified in the same atmVpCrossConnectEntry."
2935 ::= { atmVpCrossConnectEntry 2 }
2936
2937 atmVpCrossConnectLowVpi OBJECT-TYPE
2938 SYNTAX AtmVpIdentifier
2939 MAX-ACCESS not-accessible
2940 STATUS current
2941 DESCRIPTION
2942 "The VPI value at the ATM interface
2943 associated with the VP cross-connect that is
2944 identified by atmVpCrossConnectLowIfIndex."
2945 ::= { atmVpCrossConnectEntry 3 }
2946
2947 atmVpCrossConnectHighIfIndex OBJECT-TYPE
2948 SYNTAX InterfaceIndex
2949 MAX-ACCESS not-accessible
2950 STATUS current
2951 DESCRIPTION
2952 "The ifIndex value of the ATM interface for
2953 this VP cross-connect. The term high implies that
2954 this ATM interface has the numerically higher
2955 ifIndex value than the other ATM interface
2956 identified in the same atmVpCrossConnectEntry."
2957 ::= { atmVpCrossConnectEntry 4 }
2958
2959 atmVpCrossConnectHighVpi OBJECT-TYPE
2960 SYNTAX AtmVpIdentifier
2961
2962
2963
2964 <span class="grey">Tesink Standards Track [Page 53]</span></pre>
2965 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-54" ></span>
2966 <span class="grey"><a href="./rfc2515">RFC 2515</a> ATM Management Objects February 1999</span>
2967
2968
2969 MAX-ACCESS not-accessible
2970 STATUS current
2971 DESCRIPTION
2972 "The VPI value at the ATM interface
2973 associated with the VP cross-connect that is
2974 identified by atmVpCrossConnectHighIfIndex."
2975 ::= { atmVpCrossConnectEntry 5 }
2976
2977 atmVpCrossConnectAdminStatus OBJECT-TYPE
2978 SYNTAX AtmVorXAdminStatus
2979 MAX-ACCESS read-create
2980 STATUS current
2981 DESCRIPTION
2982 "The desired administrative status of this
2983 bi-directional VP cross-connect."
2984 DEFVAL { down }
2985 ::= { atmVpCrossConnectEntry 6 }
2986
2987 atmVpCrossConnectL2HOperStatus OBJECT-TYPE
2988 SYNTAX AtmVorXOperStatus
2989 MAX-ACCESS read-only
2990 STATUS current
2991 DESCRIPTION
2992 "The operational status of the VP cross-connect
2993 in one direction; (i.e., from the low to
2994 high direction)."
2995 ::= { atmVpCrossConnectEntry 7 }
2996
2997 atmVpCrossConnectH2LOperStatus OBJECT-TYPE
2998 SYNTAX AtmVorXOperStatus
2999 MAX-ACCESS read-only
3000 STATUS current
3001 DESCRIPTION
3002 "The operational status of the VP cross-connect
3003 in one direction; (i.e., from the high to
3004 low direction)."
3005 ::= { atmVpCrossConnectEntry 8 }
3006
3007 atmVpCrossConnectL2HLastChange OBJECT-TYPE
3008 SYNTAX AtmVorXLastChange
3009 MAX-ACCESS read-only
3010 STATUS current
3011 DESCRIPTION
3012 "The value of sysUpTime at the time this
3013 VP cross-connect entered its current operational
3014 state in the low to high direction."
3015 ::= { atmVpCrossConnectEntry 9 }
3016
3017
3018
3019
3020 <span class="grey">Tesink Standards Track [Page 54]</span></pre>
3021 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-55" ></span>
3022 <span class="grey"><a href="./rfc2515">RFC 2515</a> ATM Management Objects February 1999</span>
3023
3024
3025 atmVpCrossConnectH2LLastChange OBJECT-TYPE
3026 SYNTAX AtmVorXLastChange
3027 MAX-ACCESS read-only
3028 STATUS current
3029 DESCRIPTION
3030 "The value of sysUpTime at the time this
3031 VP cross-connect entered its current operational
3032 in the high to low direction."
3033 ::= { atmVpCrossConnectEntry 10 }
3034
3035 atmVpCrossConnectRowStatus OBJECT-TYPE
3036 SYNTAX RowStatus
3037 MAX-ACCESS read-create
3038 STATUS current
3039 DESCRIPTION
3040 "The status of this entry in the
3041 atmVpCrossConnectTable. This object is used to
3042 create a cross-connect for cross-connecting
3043 VPLs which are created using the atmVplTable
3044 or to change or delete an existing cross-connect.
3045 This object must be initially set
3046 to `createAndWait' or 'createAndGo'.
3047 To turn on a VP cross-connect,
3048 the atmVpCrossConnectAdminStatus
3049 is set to `up'."
3050 DEFVAL { createAndWait }
3051 ::= { atmVpCrossConnectEntry 11 }
3052
3053
3054 -- ATM Virtual Channel (VC) Cross Connect Table
3055
3056 -- This table contains configuration and state
3057 -- information of point-to-point,
3058 -- point-to-multipoint or multipoint-to-multipoint
3059 -- VC cross-connects for PVCs.
3060
3061 -- This table has read-create access and is used
3062 -- to cross-connect the VCLs together in an ATM switch
3063 -- or network that belong to a VC connection.
3064 -- The atmVcCrossConnectIndex is used to associate
3065 -- the related VCLs that are cross-connected together.
3066
3067
3068
3069 -- The model using step-wise procedures described for setting
3070 -- up a VP cross-connect is also used for setting up
3071 -- a VC cross-connect.
3072
3073
3074
3075
3076 <span class="grey">Tesink Standards Track [Page 55]</span></pre>
3077 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-56" ></span>
3078 <span class="grey"><a href="./rfc2515">RFC 2515</a> ATM Management Objects February 1999</span>
3079
3080
3081 atmVcCrossConnectIndexNext OBJECT-TYPE
3082 SYNTAX INTEGER (0..2147483647)
3083 MAX-ACCESS read-only
3084 STATUS current
3085 DESCRIPTION
3086 "This object contains an appropriate value to
3087 be used for atmVcCrossConnectIndex when creating
3088 entries in the atmVcCrossConnectTable. The value
3089 0 indicates that no unassigned entries are
3090 available. To obtain the atmVcCrossConnectIndex
3091 value for a new entry, the manager issues a
3092 management protocol retrieval operation to obtain
3093 the current value of this object. After each
3094 retrieval, the agent should modify the value to
3095 the next unassigned index.
3096 After a manager retrieves a value the agent will
3097 determine through its local policy when this index
3098 value will be made available for reuse."
3099 ::= { atmMIBObjects 10 }
3100
3101
3102 -- The ATM VC Cross Connect Table
3103
3104
3105 atmVcCrossConnectTable OBJECT-TYPE
3106 SYNTAX SEQUENCE OF AtmVcCrossConnectEntry
3107 MAX-ACCESS not-accessible
3108 STATUS current
3109 DESCRIPTION
3110 "The ATM VC Cross Connect table for PVCs.
3111 An entry in this table models two
3112 cross-connected VCLs.
3113 Each VCL must have its atmConnKind set
3114 to pvc(1)."
3115 ::= { atmMIBObjects 11 }
3116
3117
3118 atmVcCrossConnectEntry OBJECT-TYPE
3119 SYNTAX AtmVcCrossConnectEntry
3120 MAX-ACCESS not-accessible
3121 STATUS current
3122 DESCRIPTION
3123 "An entry in the ATM VC Cross Connect table.
3124 This entry is used to model a bi-directional ATM
3125 VC cross-connect cross-connecting two end points.
3126
3127 Step-wise Procedures to set up a VC Cross-connect
3128
3129
3130
3131
3132 <span class="grey">Tesink Standards Track [Page 56]</span></pre>
3133 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-57" ></span>
3134 <span class="grey"><a href="./rfc2515">RFC 2515</a> ATM Management Objects February 1999</span>
3135
3136
3137 Once the entries in the atmVclTable are created,
3138 the following procedures are used
3139 to cross-connect the VCLs together to
3140 form a VCC segment.
3141
3142 (1) The manager obtains a unique
3143 atmVcCrossConnectIndex by reading the
3144 atmVcCrossConnectIndexNext object.
3145
3146 (2) Next, the manager creates a set of one
3147 or more rows in the ATM VC Cross Connect
3148 Table, one for each cross-connection between
3149 two VCLs. Each row is indexed by the ATM
3150 interface port numbers and VPI/VCI values of
3151 the two ends of that cross-connection.
3152 This set of rows specifies the topology of the
3153 VCC cross-connect and is identified by a single
3154 value of atmVcCrossConnectIndex.
3155
3156 Negotiated VC Cross-Connect Establishment
3157
3158 (2a) The manager creates a row in this table by
3159 setting atmVcCrossConnectRowStatus to
3160 createAndWait(5). The agent checks the
3161 requested topology and the mutual sanity of
3162 the ATM traffic parameters and
3163 service categories, i.e., the row creation
3164 fails if:
3165 - the requested topology is incompatible with
3166 associated values of atmVclCastType,
3167 - the requested topology is not supported
3168 by the agent,
3169 - the traffic/service category parameter values
3170 associated with the requested row are
3171 incompatible with those of already existing
3172 rows for this VC cross-connect.
3173 [For example, for setting up
3174 a point-to-point VC cross-connect, the
3175 ATM traffic parameters in the receive direction
3176 of a VCL at the low end of the cross-connect
3177 must equal to the traffic parameters in the
3178 transmit direction of the other VCL at the
3179 high end of the cross-connect,
3180 otherwise, the row creation fails.]
3181 The agent also checks for internal errors
3182 in building the cross-connect.
3183
3184 The atmVcCrossConnectIndex values in the
3185
3186
3187
3188 <span class="grey">Tesink Standards Track [Page 57]</span></pre>
3189 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-58" ></span>
3190 <span class="grey"><a href="./rfc2515">RFC 2515</a> ATM Management Objects February 1999</span>
3191
3192
3193 corresponding atmVclTable rows are filled
3194 in by the agent at this point.
3195
3196 (2b) The manager promotes the row in the
3197 atmVcCrossConnectTable by setting
3198 atmVcCrossConnectRowStatus to active(1). If
3199 this set is successful, the agent has reserved
3200 the resources specified by the ATM traffic
3201 parameter and Service category values
3202 for each direction of the VC cross-connect
3203 in an ATM switch or network.
3204
3205 (3) The manager sets the
3206 atmVcCrossConnectAdminStatus to up(1)
3207 in all rows of this VC cross-connect to
3208 turn the traffic flow on.
3209
3210
3211 One-Shot VC Cross-Connect Establishment
3212
3213 A VC cross-connect may also be established in
3214 one step by a set-request with all necessary
3215 parameter values and atmVcCrossConnectRowStatus
3216 set to createAndGo(4).
3217
3218 In contrast to the negotiated VC cross-connect
3219 establishment which allows for detailed error
3220 checking i.e., set errors are explicitly linked to
3221 particular resource acquisition failures), the
3222 one-shot VC cross-connect establishment
3223 performs the setup on one operation but does
3224 not have the advantage of step-wise error
3225 checking.
3226
3227 VC Cross-Connect Retirement
3228
3229 A VC cross-connect identified by a particular
3230 value of atmVcCrossConnectIndex is released by:
3231
3232 (1) Setting atmVcCrossConnectRowStatus of all rows
3233 identified by this value of
3234 atmVcCrossConnectIndex to destroy(6).
3235 The agent may release all
3236 associated resources, and the
3237 atmVcCrossConnectIndex values in the
3238 corresponding atmVclTable row are removed.
3239 Note that a situation when only a subset of
3240 the associated rows are deleted corresponds
3241
3242
3243
3244 <span class="grey">Tesink Standards Track [Page 58]</span></pre>
3245 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-59" ></span>
3246 <span class="grey"><a href="./rfc2515">RFC 2515</a> ATM Management Objects February 1999</span>
3247
3248
3249 to a VC topology change.
3250
3251 (2) After deletion of the appropriate
3252 atmVcCrossConnectEntries, the manager may
3253 set atmVclRowStatus to destroy(6) the
3254 associated VCLs. The agent releases
3255 the resources and removes the associated
3256 rows in the atmVclTable.
3257
3258 VC Cross-Connect Reconfiguration
3259
3260 At the discretion of the agent, a VC
3261 cross-connect may be reconfigured by
3262 adding and/or deleting leafs to/from
3263 the VC topology as per the VC cross-connect
3264 establishment/retirement procedures.
3265 Reconfiguration of traffic/service category parameter
3266 values requires release of the VC cross-connect
3267 before those parameter values may by changed
3268 for individual VCLs."
3269 INDEX { atmVcCrossConnectIndex,
3270 atmVcCrossConnectLowIfIndex,
3271 atmVcCrossConnectLowVpi,
3272 atmVcCrossConnectLowVci,
3273 atmVcCrossConnectHighIfIndex,
3274 atmVcCrossConnectHighVpi,
3275 atmVcCrossConnectHighVci }
3276 ::= { atmVcCrossConnectTable 1 }
3277
3278 AtmVcCrossConnectEntry ::= SEQUENCE {
3279 atmVcCrossConnectIndex INTEGER,
3280 atmVcCrossConnectLowIfIndex InterfaceIndex,
3281 atmVcCrossConnectLowVpi AtmVpIdentifier,
3282 atmVcCrossConnectLowVci AtmVcIdentifier,
3283 atmVcCrossConnectHighIfIndex InterfaceIndex,
3284 atmVcCrossConnectHighVpi AtmVpIdentifier,
3285 atmVcCrossConnectHighVci AtmVcIdentifier,
3286 atmVcCrossConnectAdminStatus AtmVorXAdminStatus,
3287 atmVcCrossConnectL2HOperStatus AtmVorXOperStatus,
3288 atmVcCrossConnectH2LOperStatus AtmVorXOperStatus,
3289 atmVcCrossConnectL2HLastChange AtmVorXLastChange,
3290 atmVcCrossConnectH2LLastChange AtmVorXLastChange,
3291 atmVcCrossConnectRowStatus RowStatus
3292 }
3293
3294 atmVcCrossConnectIndex OBJECT-TYPE
3295 SYNTAX INTEGER (1..2147483647)
3296 MAX-ACCESS not-accessible
3297
3298
3299
3300 <span class="grey">Tesink Standards Track [Page 59]</span></pre>
3301 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-60" ></span>
3302 <span class="grey"><a href="./rfc2515">RFC 2515</a> ATM Management Objects February 1999</span>
3303
3304
3305 STATUS current
3306 DESCRIPTION
3307 "A unique value to identify this VC cross-connect.
3308 For each VCL associated with this cross-connect,
3309 the agent reports this cross-connect index value
3310 in the atmVclCrossConnectIdentifier attribute of
3311 the corresponding atmVclTable entries."
3312 ::= { atmVcCrossConnectEntry 1 }
3313
3314 atmVcCrossConnectLowIfIndex OBJECT-TYPE
3315 SYNTAX InterfaceIndex
3316 MAX-ACCESS not-accessible
3317 STATUS current
3318 DESCRIPTION
3319 "The ifIndex value of the ATM interface for this
3320 VC cross-connect. The term low implies
3321 that this ATM interface has the numerically lower
3322 ifIndex value than the other ATM interface
3323 identified in the same atmVcCrossConnectEntry."
3324 ::= { atmVcCrossConnectEntry 2 }
3325
3326 atmVcCrossConnectLowVpi OBJECT-TYPE
3327 SYNTAX AtmVpIdentifier
3328 MAX-ACCESS not-accessible
3329 STATUS current
3330 DESCRIPTION
3331 "The VPI value at the ATM interface
3332 associated with the VC cross-connect that is
3333 identified by atmVcCrossConnectLowIfIndex."
3334 ::= { atmVcCrossConnectEntry 3 }
3335
3336 atmVcCrossConnectLowVci OBJECT-TYPE
3337 SYNTAX AtmVcIdentifier
3338 MAX-ACCESS not-accessible
3339 STATUS current
3340 DESCRIPTION
3341 "The VCI value at the ATM interface
3342 associated with this VC cross-connect that is
3343 identified by atmVcCrossConnectLowIfIndex."
3344 ::= { atmVcCrossConnectEntry 4 }
3345
3346 atmVcCrossConnectHighIfIndex OBJECT-TYPE
3347 SYNTAX InterfaceIndex
3348 MAX-ACCESS not-accessible
3349 STATUS current
3350 DESCRIPTION
3351 "The ifIndex value for the ATM interface for
3352 this VC cross-connect. The term high implies
3353
3354
3355
3356 <span class="grey">Tesink Standards Track [Page 60]</span></pre>
3357 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-61" ></span>
3358 <span class="grey"><a href="./rfc2515">RFC 2515</a> ATM Management Objects February 1999</span>
3359
3360
3361 that this ATM interface has the numerically higher
3362 ifIndex value than the other ATM interface
3363 identified in the same atmVcCrossConnectEntry."
3364 ::= { atmVcCrossConnectEntry 5 }
3365
3366 atmVcCrossConnectHighVpi OBJECT-TYPE
3367 SYNTAX AtmVpIdentifier
3368 MAX-ACCESS not-accessible
3369 STATUS current
3370 DESCRIPTION
3371 "The VPI value at the ATM interface
3372 associated with the VC cross-connect that is
3373 identified by atmVcCrossConnectHighIfIndex."
3374 ::= { atmVcCrossConnectEntry 6 }
3375
3376 atmVcCrossConnectHighVci OBJECT-TYPE
3377 SYNTAX AtmVcIdentifier
3378 MAX-ACCESS not-accessible
3379 STATUS current
3380 DESCRIPTION
3381 "The VCI value at the ATM interface
3382 associated with the VC cross-connect that is
3383 identified by atmVcCrossConnectHighIfIndex."
3384 ::= { atmVcCrossConnectEntry 7 }
3385
3386 atmVcCrossConnectAdminStatus OBJECT-TYPE
3387 SYNTAX AtmVorXAdminStatus
3388 MAX-ACCESS read-create
3389 STATUS current
3390 DESCRIPTION
3391 "The desired administrative status of this
3392 bi-directional VC cross-connect."
3393 DEFVAL { down }
3394 ::= { atmVcCrossConnectEntry 8 }
3395
3396 atmVcCrossConnectL2HOperStatus OBJECT-TYPE
3397 SYNTAX AtmVorXOperStatus
3398 MAX-ACCESS read-only
3399 STATUS current
3400 DESCRIPTION
3401 "The current operational status of the
3402 VC cross-connect in one direction; (i.e.,
3403 from the low to high direction)."
3404 ::= { atmVcCrossConnectEntry 9 }
3405
3406
3407 atmVcCrossConnectH2LOperStatus OBJECT-TYPE
3408 SYNTAX AtmVorXOperStatus
3409
3410
3411
3412 <span class="grey">Tesink Standards Track [Page 61]</span></pre>
3413 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-62" ></span>
3414 <span class="grey"><a href="./rfc2515">RFC 2515</a> ATM Management Objects February 1999</span>
3415
3416
3417 MAX-ACCESS read-only
3418 STATUS current
3419 DESCRIPTION
3420 "The current operational status of the
3421 VC cross-connect in one direction; (i.e.,
3422 from the high to low direction)."
3423 ::= { atmVcCrossConnectEntry 10 }
3424
3425 atmVcCrossConnectL2HLastChange OBJECT-TYPE
3426 SYNTAX AtmVorXLastChange
3427 MAX-ACCESS read-only
3428 STATUS current
3429 DESCRIPTION
3430 "The value of sysUpTime at the time this
3431 VC cross-connect entered its current
3432 operational state in low to high direction."
3433 ::= { atmVcCrossConnectEntry 11 }
3434
3435 atmVcCrossConnectH2LLastChange OBJECT-TYPE
3436 SYNTAX AtmVorXLastChange
3437 MAX-ACCESS read-only
3438 STATUS current
3439 DESCRIPTION
3440 "The value of sysUpTime at the time this
3441 VC cross-connect entered its current
3442 operational state in high to low direction."
3443 ::= { atmVcCrossConnectEntry 12 }
3444
3445 atmVcCrossConnectRowStatus OBJECT-TYPE
3446 SYNTAX RowStatus
3447 MAX-ACCESS read-create
3448 STATUS current
3449 DESCRIPTION
3450 "The status of this entry in the
3451 atmVcCrossConnectTable. This object is used to
3452 create a new cross-connect for cross-connecting
3453 VCLs which are created using the atmVclTable
3454 or to change or delete existing cross-connect.
3455 This object must be initially set to
3456 `createAndWait' or 'createAndGo'.
3457 To turn on a VC cross-connect,
3458 the atmVcCrossConnectAdminStatus
3459 is set to `up'."
3460 DEFVAL { createAndWait }
3461 ::= { atmVcCrossConnectEntry 13 }
3462
3463
3464 -- AAL5 Virtual Channel Connection Performance Statistics
3465
3466
3467
3468 <span class="grey">Tesink Standards Track [Page 62]</span></pre>
3469 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-63" ></span>
3470 <span class="grey"><a href="./rfc2515">RFC 2515</a> ATM Management Objects February 1999</span>
3471
3472
3473 -- Table
3474
3475 -- This table contains the AAL5
3476 -- performance statistics of a VCC at the
3477 -- interface associated with an AAL5 entity in an ATM
3478 -- host or ATM switch.
3479
3480
3481 aal5VccTable OBJECT-TYPE
3482 SYNTAX SEQUENCE OF Aal5VccEntry
3483 MAX-ACCESS not-accessible
3484 STATUS current
3485 DESCRIPTION
3486 "This table contains AAL5 VCC performance
3487 parameters."
3488 ::= { atmMIBObjects 12 }
3489
3490 aal5VccEntry OBJECT-TYPE
3491 SYNTAX Aal5VccEntry
3492 MAX-ACCESS not-accessible
3493 STATUS current
3494 DESCRIPTION
3495 "This list contains the AAL5 VCC
3496 performance parameters and is indexed
3497 by ifIndex values of AAL5 interfaces
3498 and the associated VPI/VCI values."
3499 INDEX { ifIndex, aal5VccVpi, aal5VccVci }
3500 ::= { aal5VccTable 1 }
3501
3502 Aal5VccEntry ::= SEQUENCE {
3503 aal5VccVpi AtmVpIdentifier,
3504 aal5VccVci AtmVcIdentifier,
3505 aal5VccCrcErrors Counter32,
3506 aal5VccSarTimeOuts Counter32,
3507 aal5VccOverSizedSDUs Counter32
3508 }
3509
3510
3511 aal5VccVpi OBJECT-TYPE
3512 SYNTAX AtmVpIdentifier
3513 MAX-ACCESS not-accessible
3514 STATUS current
3515 DESCRIPTION
3516 "The VPI value of the AAL5 VCC at the
3517 interface identified by the ifIndex."
3518 ::= { aal5VccEntry 1 }
3519
3520 aal5VccVci OBJECT-TYPE
3521
3522
3523
3524 <span class="grey">Tesink Standards Track [Page 63]</span></pre>
3525 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-64" ></span>
3526 <span class="grey"><a href="./rfc2515">RFC 2515</a> ATM Management Objects February 1999</span>
3527
3528
3529 SYNTAX AtmVcIdentifier
3530 MAX-ACCESS not-accessible
3531 STATUS current
3532 DESCRIPTION
3533 "The VCI value of the AAL5 VCC at the
3534 interface identified by the ifIndex."
3535 ::= { aal5VccEntry 2 }
3536
3537 aal5VccCrcErrors OBJECT-TYPE
3538 SYNTAX Counter32
3539 MAX-ACCESS read-only
3540 STATUS current
3541 DESCRIPTION
3542 "The number of AAL5 CPCS PDUs received with
3543 CRC-32 errors on this AAL5 VCC at the
3544 interface associated with an AAL5 entity."
3545 ::= { aal5VccEntry 3 }
3546
3547 aal5VccSarTimeOuts OBJECT-TYPE
3548 SYNTAX Counter32
3549 MAX-ACCESS read-only
3550 STATUS current
3551 DESCRIPTION
3552 "The number of partially re-assembled AAL5
3553 CPCS PDUs which were discarded
3554 on this AAL5 VCC at the interface associated
3555 with an AAL5 entity because they
3556 were not fully re-assembled within the
3557 required time period. If the re-assembly
3558 timer is not supported, then this object
3559 contains a zero value."
3560 ::= { aal5VccEntry 4 }
3561
3562 aal5VccOverSizedSDUs OBJECT-TYPE
3563 SYNTAX Counter32
3564 MAX-ACCESS read-only
3565 STATUS current
3566 DESCRIPTION
3567 "The number of AAL5 CPCS PDUs discarded
3568 on this AAL5 VCC at the interface
3569 associated with an AAL5 entity because the
3570 AAL5 SDUs were too large."
3571 ::= { aal5VccEntry 5 }
3572
3573
3574 --
3575 -- The following object may be used in conjunction with
3576 -- the atmTrafficDescrParamTable for the creation of
3577
3578
3579
3580 <span class="grey">Tesink Standards Track [Page 64]</span></pre>
3581 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-65" ></span>
3582 <span class="grey"><a href="./rfc2515">RFC 2515</a> ATM Management Objects February 1999</span>
3583
3584
3585 -- new table entries.
3586 --
3587
3588 atmTrafficDescrParamIndexNext OBJECT-TYPE
3589 SYNTAX INTEGER (0..2147483647)
3590 MAX-ACCESS read-only
3591 STATUS current
3592 DESCRIPTION
3593 "This object contains an appropriate value to
3594 be used for atmTrafficDescrParamIndex when
3595 creating entries in the
3596 atmTrafficDescrParamTable.
3597 The value 0 indicates that no unassigned
3598 entries are available. To obtain the
3599 atmTrafficDescrParamIndex value for a new
3600 entry, the manager issues a management
3601 protocol retrieval operation to obtain the
3602 current value of this object. After each
3603 retrieval, the agent should modify the value
3604 to the next unassigned index.
3605 After a manager retrieves a value the agent will
3606 determine through its local policy when this index
3607 value will be made available for reuse."
3608 ::= { atmMIBObjects 13 }
3609
3610
3611 -- Conformance Information
3612
3613 atmMIBConformance OBJECT IDENTIFIER ::= { atmMIB 2 }
3614
3615 atmMIBGroups OBJECT IDENTIFIER
3616 ::= { atmMIBConformance 1 }
3617 atmMIBCompliances OBJECT IDENTIFIER
3618 ::= { atmMIBConformance 2 }
3619
3620
3621 -- Compliance Statements
3622
3623 atmMIBCompliance2 MODULE-COMPLIANCE
3624 STATUS current
3625 DESCRIPTION
3626 "The compliance statement for SNMP entities
3627 including networks which have ATM and
3628 AAL5 interfaces."
3629
3630 MODULE -- this module
3631 --
3632 -- ****** Interface and Traffic Descriptor Support ***
3633
3634
3635
3636 <span class="grey">Tesink Standards Track [Page 65]</span></pre>
3637 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-66" ></span>
3638 <span class="grey"><a href="./rfc2515">RFC 2515</a> ATM Management Objects February 1999</span>
3639
3640
3641 --
3642 MANDATORY-GROUPS {atmInterfaceConfGroup2,
3643 atmTrafficDescrGroup2 }
3644
3645 OBJECT atmInterfaceMaxVpcs
3646 MIN-ACCESS read-only
3647 DESCRIPTION
3648 "Write access is not required."
3649
3650 OBJECT atmInterfaceMaxVccs
3651 MIN-ACCESS read-only
3652 DESCRIPTION
3653 "Write access is not required."
3654
3655 OBJECT atmInterfaceMaxActiveVpiBits
3656 MIN-ACCESS read-only
3657 DESCRIPTION
3658 "Write access is not required.
3659 At the ATM UNI the maximum number of
3660 active VPI bits configured for use ranges
3661 from 0 to 8 only.
3662 Implementations may support smaller ranges."
3663 OBJECT atmInterfaceMaxActiveVciBits
3664 MIN-ACCESS read-only
3665 DESCRIPTION
3666 "Write access is not required.
3667 Implementations may support smaller ranges."
3668
3669 OBJECT atmInterfaceIlmiVpi
3670 MIN-ACCESS read-only
3671 DESCRIPTION
3672 "Write access is not required."
3673
3674 OBJECT atmInterfaceIlmiVci
3675 MIN-ACCESS read-only
3676 DESCRIPTION
3677 "Write access is not required."
3678
3679 OBJECT atmInterfaceMyNeighborIpAddress
3680 MIN-ACCESS read-only
3681 DESCRIPTION
3682 "Write access is not required."
3683
3684 OBJECT atmInterfaceMyNeighborIfName
3685 MIN-ACCESS read-only
3686 DESCRIPTION
3687 "Write access is not required."
3688
3689
3690
3691
3692 <span class="grey">Tesink Standards Track [Page 66]</span></pre>
3693 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-67" ></span>
3694 <span class="grey"><a href="./rfc2515">RFC 2515</a> ATM Management Objects February 1999</span>
3695
3696
3697 OBJECT atmInterfaceSubscrAddress
3698 MIN-ACCESS read-only
3699 DESCRIPTION
3700 "Write access is not required."
3701
3702 OBJECT atmTrafficDescrParamIndexNext
3703 DESCRIPTION
3704 "This object is only required for systems
3705 that support the creation of entries in
3706 the atmTrafficDescrParamTable."
3707
3708 OBJECT atmTrafficDescrType
3709 MIN-ACCESS read-only
3710 DESCRIPTION
3711 "Write access is not required."
3712
3713 OBJECT atmTrafficDescrParam1
3714 MIN-ACCESS read-only
3715 DESCRIPTION
3716 "Write access is not required."
3717
3718 OBJECT atmTrafficDescrParam2
3719 MIN-ACCESS read-only
3720 DESCRIPTION
3721 "Write access is not required."
3722
3723 OBJECT atmTrafficDescrParam3
3724 MIN-ACCESS read-only
3725 DESCRIPTION
3726 "Write access is not required."
3727
3728 OBJECT atmTrafficDescrParam4
3729 MIN-ACCESS read-only
3730 DESCRIPTION
3731 "Write access is not required."
3732
3733 OBJECT atmTrafficDescrParam5
3734 MIN-ACCESS read-only
3735 DESCRIPTION
3736 "Write access is not required."
3737
3738 OBJECT atmServiceCategory
3739 MIN-ACCESS read-only
3740 DESCRIPTION
3741 "Write access is not required."
3742
3743 OBJECT atmTrafficDescrRowStatus
3744 SYNTAX INTEGER {active(1)}
3745
3746
3747
3748 <span class="grey">Tesink Standards Track [Page 67]</span></pre>
3749 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-68" ></span>
3750 <span class="grey"><a href="./rfc2515">RFC 2515</a> ATM Management Objects February 1999</span>
3751
3752
3753 -- subset of RowStatus
3754 MIN-ACCESS read-only
3755 DESCRIPTION
3756 "Write access is not required, and only one
3757 of the six enumerated values for the
3758 RowStatus textual convention need be
3759 supported, specifically: active(1)."
3760
3761 OBJECT atmTrafficFrameDiscard
3762 MIN-ACCESS read-only
3763 DESCRIPTION
3764 "Write access is not required."
3765
3766 --
3767 -- ****** DS3 PLCP Support **************************
3768 --
3769 GROUP atmInterfaceDs3PlcpGroup
3770 DESCRIPTION
3771 "This group is mandatory only for those
3772 ATM interfaces which implement the
3773 DS3 PLCP layer."
3774 --
3775 -- ****** TC Sublayer Support ********************************
3776 --
3777 GROUP atmInterfaceTCGroup
3778 DESCRIPTION
3779 "This group is mandatory only for those
3780 ATM interfaces which implement the
3781 TC Sublayer."
3782
3783 --
3784 -- ****** VPC Support *******************************
3785 --
3786 GROUP atmVpcTerminationGroup2
3787 DESCRIPTION
3788 "This group is mandatory only for those
3789 ATM interfaces which implement ATM
3790 VPLs that terminate VPCs (i.e., ones which
3791 are NOT cross-connected to other VPLs)."
3792
3793 GROUP atmVplCrossConnectGroup
3794 DESCRIPTION
3795 "This group is mandatory only for those
3796 ATM interfaces which implement ATM
3797 VPLs that are not associated with VCLs
3798 and are cross-connected to other VPLs
3799 for VPCs."
3800
3801
3802
3803
3804 <span class="grey">Tesink Standards Track [Page 68]</span></pre>
3805 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-69" ></span>
3806 <span class="grey"><a href="./rfc2515">RFC 2515</a> ATM Management Objects February 1999</span>
3807
3808
3809 GROUP atmVpPvcCrossConnectGroup
3810 DESCRIPTION
3811 "This group is mandatory only for those
3812 ATM interfaces which implement ATM
3813 VPLs that are not associated with VCLs
3814 and are cross-connected to other VPLs
3815 for permanent VPCs (i.e., PVCs).
3816 This group is not used to crossconnect
3817 a PVC with an SVC to form a Soft PVC."
3818
3819 OBJECT atmVplAdminStatus
3820 MIN-ACCESS read-only
3821 DESCRIPTION
3822 "Write access is not required."
3823
3824 OBJECT atmVplReceiveTrafficDescrIndex
3825 MIN-ACCESS read-only
3826 DESCRIPTION
3827 "Write access is not required."
3828
3829 OBJECT atmVplTransmitTrafficDescrIndex
3830 MIN-ACCESS read-only
3831 DESCRIPTION
3832 "Write access is not required."
3833
3834 OBJECT atmVplRowStatus
3835 SYNTAX INTEGER {active(1)}
3836 -- subset of RowStatus
3837 MIN-ACCESS read-only
3838 DESCRIPTION
3839 "Write access is not required, and only one
3840 of the six enumerated values for the
3841 RowStatus textual convention need be
3842 supported, specifically: active(1)."
3843
3844 OBJECT atmVplCastType
3845 MIN-ACCESS read-only
3846 DESCRIPTION
3847 "Write access is not required."
3848
3849 OBJECT atmVplConnKind
3850 MIN-ACCESS read-only
3851 DESCRIPTION
3852 "Write access is not required."
3853
3854 OBJECT atmVpCrossConnectAdminStatus
3855 MIN-ACCESS read-only
3856 DESCRIPTION
3857
3858
3859
3860 <span class="grey">Tesink Standards Track [Page 69]</span></pre>
3861 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-70" ></span>
3862 <span class="grey"><a href="./rfc2515">RFC 2515</a> ATM Management Objects February 1999</span>
3863
3864
3865 "Write access is not required."
3866
3867 OBJECT atmVpCrossConnectRowStatus
3868 SYNTAX INTEGER {active(1)}
3869 -- subset of RowStatus
3870 MIN-ACCESS read-only
3871 DESCRIPTION
3872 "Write access is not required, and only one
3873 of the six enumerated values for the
3874 RowStatus textual convention need be
3875 supported, specifically: active(1)."
3876
3877 --
3878 -- ****** VCC Support *******************************
3879 --
3880 GROUP atmVccTerminationGroup2
3881 DESCRIPTION
3882 "This group is mandatory only for those
3883 ATM interfaces which implement ATM
3884 VCLs that terminate VCCs (i.e., ones which
3885 are NOT cross-connected to other VCLs)."
3886
3887 GROUP atmVclCrossConnectGroup
3888 DESCRIPTION
3889 "This group is mandatory only for those
3890 ATM interfaces which implement ATM
3891 VCLs that are cross-connected to other VCLs
3892 for VCCs."
3893
3894 GROUP atmVcPvcCrossConnectGroup
3895 DESCRIPTION
3896 "This group is mandatory only for those
3897 ATM interfaces which implement ATM
3898 VCLs that are cross-connected to other
3899 VCLs for permanent VCCs (i.e., PVCs).
3900 This group is not used to crossconnect
3901 a PVC with an SVC to form a Soft PVC."
3902
3903 OBJECT atmVclAdminStatus
3904 MIN-ACCESS read-only
3905 DESCRIPTION
3906 "Write access is not required."
3907
3908 OBJECT atmVclReceiveTrafficDescrIndex
3909 MIN-ACCESS read-only
3910 DESCRIPTION
3911 "Write access is not required."
3912
3913
3914
3915
3916 <span class="grey">Tesink Standards Track [Page 70]</span></pre>
3917 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-71" ></span>
3918 <span class="grey"><a href="./rfc2515">RFC 2515</a> ATM Management Objects February 1999</span>
3919
3920
3921 OBJECT atmVclTransmitTrafficDescrIndex
3922 MIN-ACCESS read-only
3923 DESCRIPTION
3924 "Write access is not required."
3925
3926 OBJECT atmVccAalType
3927 MIN-ACCESS read-only
3928 DESCRIPTION
3929 "Write access is not required."
3930
3931 OBJECT atmVclRowStatus
3932 SYNTAX INTEGER {active(1)}
3933 -- subset of RowStatus
3934 MIN-ACCESS read-only
3935 DESCRIPTION
3936 "Write access is not required, and only one
3937 of the six enumerated values for the
3938 RowStatus textual convention need be
3939 supported, specifically: active(1)."
3940
3941 OBJECT atmVclCastType
3942 MIN-ACCESS read-only
3943 DESCRIPTION
3944 "Write access is not required."
3945
3946 OBJECT atmVclConnKind
3947 MIN-ACCESS read-only
3948 DESCRIPTION
3949 "Write access is not required."
3950
3951 OBJECT atmVcCrossConnectAdminStatus
3952 MIN-ACCESS read-only
3953 DESCRIPTION
3954 "Write access is not required."
3955
3956 OBJECT atmVcCrossConnectRowStatus
3957 SYNTAX INTEGER { active(1)}
3958 -- subset of RowStatus
3959 MIN-ACCESS read-only
3960 DESCRIPTION
3961 "Write access is not required, and only one
3962 of the six enumerated values for the
3963 RowStatus textual convention need be
3964 supported, specifically: active(1)."
3965 --
3966 -- ****** AAL5 Support ******************************
3967 --
3968 GROUP aal5VccGroup
3969
3970
3971
3972 <span class="grey">Tesink Standards Track [Page 71]</span></pre>
3973 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-72" ></span>
3974 <span class="grey"><a href="./rfc2515">RFC 2515</a> ATM Management Objects February 1999</span>
3975
3976
3977 DESCRIPTION
3978 "This group is mandatory for the
3979 AAL5 virtual connections only."
3980 OBJECT atmVccAal5CpcsTransmitSduSize
3981 MIN-ACCESS read-only
3982 DESCRIPTION
3983 "Write access is not required."
3984
3985 OBJECT atmVccAal5CpcsReceiveSduSize
3986 MIN-ACCESS read-only
3987 DESCRIPTION
3988 "Write access is not required."
3989
3990 OBJECT atmVccAal5EncapsType
3991 MIN-ACCESS read-only
3992 DESCRIPTION
3993 "Write access is not required."
3994 ::= { atmMIBCompliances 2 }
3995
3996
3997 -- Units of Conformance
3998
3999 atmInterfaceDs3PlcpGroup OBJECT-GROUP
4000 OBJECTS {atmInterfaceDs3PlcpSEFSs,
4001 atmInterfaceDs3PlcpAlarmState,
4002 atmInterfaceDs3PlcpUASs}
4003 STATUS current
4004 DESCRIPTION
4005 "A collection of objects providing information
4006 about DS3 PLCP layer at an ATM interface."
4007 ::= { atmMIBGroups 3 }
4008
4009 atmInterfaceTCGroup OBJECT-GROUP
4010 OBJECTS { atmInterfaceOCDEvents,
4011 atmInterfaceTCAlarmState }
4012 STATUS current
4013 DESCRIPTION
4014 "A collection of objects providing information
4015 about TC sublayer at an ATM interface."
4016 ::= { atmMIBGroups 4 }
4017
4018 aal5VccGroup OBJECT-GROUP
4019 OBJECTS {atmVccAal5CpcsTransmitSduSize,
4020 atmVccAal5CpcsReceiveSduSize,
4021 atmVccAal5EncapsType,
4022 aal5VccCrcErrors, aal5VccSarTimeOuts,
4023 aal5VccOverSizedSDUs }
4024 STATUS current
4025
4026
4027
4028 <span class="grey">Tesink Standards Track [Page 72]</span></pre>
4029 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-73" ></span>
4030 <span class="grey"><a href="./rfc2515">RFC 2515</a> ATM Management Objects February 1999</span>
4031
4032
4033 DESCRIPTION
4034 "A collection of objects providing
4035 AAL5 configuration and performance statistics
4036 of a VCC."
4037 ::= { atmMIBGroups 9 }
4038
4039 atmInterfaceConfGroup2 OBJECT-GROUP
4040 OBJECTS {
4041 atmInterfaceMaxVpcs, atmInterfaceMaxVccs,
4042 atmInterfaceConfVpcs, atmInterfaceConfVccs,
4043 atmInterfaceMaxActiveVpiBits,
4044 atmInterfaceMaxActiveVciBits,
4045 atmInterfaceIlmiVpi,
4046 atmInterfaceIlmiVci,
4047 atmInterfaceMyNeighborIpAddress,
4048 atmInterfaceMyNeighborIfName,
4049 atmInterfaceCurrentMaxVpiBits,
4050 atmInterfaceCurrentMaxVciBits,
4051 atmInterfaceSubscrAddress }
4052 STATUS current
4053 DESCRIPTION
4054 "A collection of objects providing configuration
4055 information about an ATM interface."
4056 ::= { atmMIBGroups 10 }
4057
4058 atmTrafficDescrGroup2 OBJECT-GROUP
4059 OBJECTS {
4060 atmTrafficDescrType, atmTrafficDescrParam1,
4061 atmTrafficDescrParam2, atmTrafficDescrParam3,
4062 atmTrafficDescrParam4, atmTrafficDescrParam5,
4063 atmTrafficDescrRowStatus, atmServiceCategory,
4064 atmTrafficFrameDiscard,
4065 atmTrafficDescrParamIndexNext }
4066 STATUS current
4067 DESCRIPTION
4068 "A collection of objects providing information
4069 about ATM traffic descriptor type and
4070 the associated parameters."
4071 ::= { atmMIBGroups 11 }
4072
4073 atmVpcTerminationGroup2 OBJECT-GROUP
4074 OBJECTS {atmVplOperStatus, atmVplAdminStatus,
4075 atmVplLastChange,
4076 atmVplReceiveTrafficDescrIndex,
4077 atmVplTransmitTrafficDescrIndex,
4078 atmVplRowStatus, atmVplCastType,
4079 atmVplConnKind }
4080 STATUS current
4081
4082
4083
4084 <span class="grey">Tesink Standards Track [Page 73]</span></pre>
4085 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-74" ></span>
4086 <span class="grey"><a href="./rfc2515">RFC 2515</a> ATM Management Objects February 1999</span>
4087
4088
4089 DESCRIPTION
4090 "A collection of objects providing information
4091 about a VPL at an ATM interface which
4092 terminates a VPC (i.e., one which is NOT
4093 cross-connected to other VPLs)."
4094 ::= { atmMIBGroups 12 }
4095
4096 atmVccTerminationGroup2 OBJECT-GROUP
4097 OBJECTS {atmVclOperStatus, atmVclAdminStatus,
4098 atmVclLastChange,
4099 atmVclReceiveTrafficDescrIndex,
4100 atmVclTransmitTrafficDescrIndex,
4101 atmVccAalType, atmVclRowStatus,
4102 atmVclCastType, atmVclConnKind }
4103 STATUS current
4104 DESCRIPTION
4105 "A collection of objects providing information
4106 about a VCL at an ATM interface
4107 which terminates a VCC (i.e., one which is
4108 NOT cross-connected to other VCLs)."
4109 ::= { atmMIBGroups 13 }
4110
4111 atmVplCrossConnectGroup OBJECT-GROUP
4112 OBJECTS { atmVplReceiveTrafficDescrIndex,
4113 atmVplTransmitTrafficDescrIndex,
4114 atmVplOperStatus, atmVplLastChange,
4115 atmVplRowStatus,
4116 atmVplCastType, atmVplConnKind }
4117 STATUS current
4118 DESCRIPTION
4119 "A collection of objects providing
4120 information about the VPLs that
4121 are cross-connected together."
4122 ::= { atmMIBGroups 14 }
4123
4124 atmVpPvcCrossConnectGroup OBJECT-GROUP
4125 OBJECTS { atmVpCrossConnectAdminStatus,
4126 atmVpCrossConnectL2HOperStatus,
4127 atmVpCrossConnectH2LOperStatus,
4128 atmVpCrossConnectL2HLastChange,
4129 atmVpCrossConnectH2LLastChange,
4130 atmVpCrossConnectRowStatus,
4131 atmVplCrossConnectIdentifier,
4132 atmVpCrossConnectIndexNext }
4133 STATUS current
4134 DESCRIPTION
4135 "A collection of objects providing
4136 information about a VP cross-connect
4137
4138
4139
4140 <span class="grey">Tesink Standards Track [Page 74]</span></pre>
4141 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-75" ></span>
4142 <span class="grey"><a href="./rfc2515">RFC 2515</a> ATM Management Objects February 1999</span>
4143
4144
4145 for PVCs. These objects are not used
4146 for Soft PVCs or SVCs."
4147 ::= { atmMIBGroups 15 }
4148
4149 atmVclCrossConnectGroup OBJECT-GROUP
4150 OBJECTS { atmVclReceiveTrafficDescrIndex,
4151 atmVclTransmitTrafficDescrIndex,
4152 atmVclOperStatus, atmVclLastChange,
4153 atmVclRowStatus,
4154 atmVclCastType, atmVclConnKind }
4155 STATUS current
4156 DESCRIPTION
4157 "A collection of objects providing
4158 information about the VCLs that
4159 are cross-connected together."
4160 ::= { atmMIBGroups 16 }
4161
4162 atmVcPvcCrossConnectGroup OBJECT-GROUP
4163 OBJECTS { atmVcCrossConnectAdminStatus,
4164 atmVcCrossConnectL2HOperStatus,
4165 atmVcCrossConnectH2LOperStatus,
4166 atmVcCrossConnectL2HLastChange,
4167 atmVcCrossConnectH2LLastChange,
4168 atmVcCrossConnectRowStatus,
4169 atmVclCrossConnectIdentifier,
4170 atmVcCrossConnectIndexNext }
4171 STATUS current
4172 DESCRIPTION
4173 "A collection of objects providing
4174 information about a VC cross-connect
4175 for PVCs. These objects are not used
4176 for Soft PVCs or SVCs."
4177 ::= { atmMIBGroups 17 }
4178
4179
4180 -- Deprecated Definitions - Objects
4181
4182 -- atmInterfaceAddressType
4183 -- atmTrafficQoSClass
4184
4185
4186 -- Deprecated Definitions - Compliance
4187
4188 atmMIBCompliance MODULE-COMPLIANCE
4189 STATUS deprecated
4190 DESCRIPTION
4191 "The compliance statement for SNMP entities
4192 including networks which have ATM and
4193
4194
4195
4196 <span class="grey">Tesink Standards Track [Page 75]</span></pre>
4197 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-76" ></span>
4198 <span class="grey"><a href="./rfc2515">RFC 2515</a> ATM Management Objects February 1999</span>
4199
4200
4201 AAL5 interfaces."
4202
4203 MODULE -- this module
4204 MANDATORY-GROUPS {atmInterfaceConfGroup,
4205 atmTrafficDescrGroup}
4206
4207 OBJECT atmInterfaceMaxVpcs
4208 MIN-ACCESS read-only
4209 DESCRIPTION
4210 "Write access is not required."
4211
4212 OBJECT atmInterfaceMaxVccs
4213 MIN-ACCESS read-only
4214 DESCRIPTION
4215 "Write access is not required."
4216
4217 OBJECT atmInterfaceMaxActiveVpiBits
4218 MIN-ACCESS read-only
4219 DESCRIPTION
4220 "Write access is not required."
4221
4222 OBJECT atmInterfaceMaxActiveVciBits
4223 MIN-ACCESS read-only
4224 DESCRIPTION
4225 "Write access is not required."
4226
4227 OBJECT atmInterfaceIlmiVpi
4228 MIN-ACCESS read-only
4229 DESCRIPTION
4230 "Write access is not required."
4231
4232 OBJECT atmInterfaceIlmiVci
4233 MIN-ACCESS read-only
4234 DESCRIPTION
4235 "Write access is not required."
4236
4237 OBJECT atmInterfaceMyNeighborIpAddress
4238 MIN-ACCESS read-only
4239 DESCRIPTION
4240 "Write access is not required."
4241
4242 OBJECT atmInterfaceMyNeighborIfName
4243 MIN-ACCESS read-only
4244 DESCRIPTION
4245 "Write access is not required."
4246
4247 OBJECT atmTrafficDescrType
4248 MIN-ACCESS read-only
4249
4250
4251
4252 <span class="grey">Tesink Standards Track [Page 76]</span></pre>
4253 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-77" ></span>
4254 <span class="grey"><a href="./rfc2515">RFC 2515</a> ATM Management Objects February 1999</span>
4255
4256
4257 DESCRIPTION
4258 "Write access is not required."
4259
4260 OBJECT atmTrafficDescrParam1
4261 MIN-ACCESS read-only
4262 DESCRIPTION
4263 "Write access is not required."
4264
4265 OBJECT atmTrafficDescrParam2
4266 MIN-ACCESS read-only
4267 DESCRIPTION
4268 "Write access is not required."
4269
4270 OBJECT atmTrafficDescrParam3
4271 MIN-ACCESS read-only
4272 DESCRIPTION
4273 "Write access is not required."
4274
4275 OBJECT atmTrafficDescrParam4
4276 MIN-ACCESS read-only
4277 DESCRIPTION
4278 "Write access is not required."
4279
4280 OBJECT atmTrafficDescrParam5
4281 MIN-ACCESS read-only
4282 DESCRIPTION
4283 "Write access is not required."
4284
4285 OBJECT atmTrafficQoSClass
4286 MIN-ACCESS read-only
4287 DESCRIPTION
4288 "Write access is not required."
4289
4290 OBJECT atmTrafficDescrRowStatus
4291 SYNTAX INTEGER {active(1)}
4292 -- subset of RowStatus
4293 MIN-ACCESS read-only
4294 DESCRIPTION
4295 "Write access is not required, and only one
4296 of the six enumerated values for the
4297 RowStatus textual convention need be
4298 supported, specifically: active(1)."
4299
4300 GROUP atmInterfaceDs3PlcpGroup
4301 DESCRIPTION
4302 "This group is mandatory only for those
4303 ATM interfaces which implement the
4304 DS3 PLCP layer."
4305
4306
4307
4308 <span class="grey">Tesink Standards Track [Page 77]</span></pre>
4309 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-78" ></span>
4310 <span class="grey"><a href="./rfc2515">RFC 2515</a> ATM Management Objects February 1999</span>
4311
4312
4313 GROUP atmInterfaceTCGroup
4314 DESCRIPTION
4315 "This group is mandatory only for those
4316 ATM interfaces which implement the
4317 TC Sublayer."
4318
4319 GROUP atmVpcTerminationGroup
4320 DESCRIPTION
4321 "This group is mandatory only for those
4322 ATM interfaces which implement ATM
4323 VPLs that terminate VPCs (i.e., ones which
4324 are NOT cross-connected to other VPLs)."
4325
4326 GROUP atmVpCrossConnectGroup
4327 DESCRIPTION
4328 "This group is mandatory only for those
4329 ATM interfaces which implement ATM
4330 VPLs that are not associated with VCLs
4331 and are cross-connected to other VPLs."
4332
4333 OBJECT atmVplAdminStatus
4334 MIN-ACCESS read-only
4335 DESCRIPTION
4336 "Write access is not required."
4337
4338 OBJECT atmVplReceiveTrafficDescrIndex
4339 MIN-ACCESS read-only
4340 DESCRIPTION
4341 "Write access is not required."
4342
4343 OBJECT atmVplTransmitTrafficDescrIndex
4344 MIN-ACCESS read-only
4345 DESCRIPTION
4346 "Write access is not required."
4347
4348 OBJECT atmVplRowStatus
4349 SYNTAX INTEGER {active(1)}
4350 -- subset of RowStatus
4351 MIN-ACCESS read-only
4352 DESCRIPTION
4353 "Write access is not required, and only one
4354 of the six enumerated values for the
4355 RowStatus textual convention need be
4356 supported, specifically: active(1)."
4357
4358 OBJECT atmVpCrossConnectAdminStatus
4359 MIN-ACCESS read-only
4360 DESCRIPTION
4361
4362
4363
4364 <span class="grey">Tesink Standards Track [Page 78]</span></pre>
4365 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-79" ></span>
4366 <span class="grey"><a href="./rfc2515">RFC 2515</a> ATM Management Objects February 1999</span>
4367
4368
4369 "Write access is not required."
4370
4371 OBJECT atmVpCrossConnectRowStatus
4372 SYNTAX INTEGER {active(1)}
4373 -- subset of RowStatus
4374 MIN-ACCESS read-only
4375 DESCRIPTION
4376 "Write access is not required, and only one
4377 of the six enumerated values for the
4378 RowStatus textual convention need be
4379 supported, specifically: active(1)."
4380
4381 GROUP atmVccTerminationGroup
4382 DESCRIPTION
4383 "This group is mandatory only for those
4384 ATM interfaces which implement ATM
4385 VCLs that terminate VCCs (i.e., ones which
4386 are NOT cross-connected to other VCLs)."
4387
4388 GROUP atmVcCrossConnectGroup
4389 DESCRIPTION
4390 "This group is mandatory only for those
4391 ATM interfaces which implement ATM
4392 VCLs that are cross-connected to
4393 other VCLs."
4394
4395 OBJECT atmVclAdminStatus
4396 MIN-ACCESS read-only
4397 DESCRIPTION
4398 "Write access is not required."
4399
4400 OBJECT atmVclReceiveTrafficDescrIndex
4401 MIN-ACCESS read-only
4402 DESCRIPTION
4403 "Write access is not required."
4404
4405 OBJECT atmVclTransmitTrafficDescrIndex
4406 MIN-ACCESS read-only
4407 DESCRIPTION
4408 "Write access is not required."
4409
4410 OBJECT atmVccAalType
4411 MIN-ACCESS read-only
4412 DESCRIPTION
4413 "Write access is not required."
4414
4415 OBJECT atmVclRowStatus
4416 SYNTAX INTEGER {active(1)}
4417
4418
4419
4420 <span class="grey">Tesink Standards Track [Page 79]</span></pre>
4421 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-80" ></span>
4422 <span class="grey"><a href="./rfc2515">RFC 2515</a> ATM Management Objects February 1999</span>
4423
4424
4425 -- subset of RowStatus
4426 MIN-ACCESS read-only
4427 DESCRIPTION
4428 "Write access is not required, and only one
4429 of the six enumerated values for the
4430 RowStatus textual convention need be
4431 supported, specifically: active(1)."
4432
4433 OBJECT atmVcCrossConnectAdminStatus
4434 MIN-ACCESS read-only
4435 DESCRIPTION
4436 "Write access is not required."
4437
4438 OBJECT atmVcCrossConnectRowStatus
4439 SYNTAX INTEGER { active(1)}
4440 -- subset of RowStatus
4441 MIN-ACCESS read-only
4442 DESCRIPTION
4443 "Write access is not required, and only one
4444 of the six enumerated values for the
4445 RowStatus textual convention need be
4446 supported, specifically: active(1)."
4447
4448 GROUP aal5VccGroup
4449 DESCRIPTION
4450 "This group is mandatory for the
4451 AAL5 virtual connections only."
4452
4453 OBJECT atmVccAal5CpcsTransmitSduSize
4454 MIN-ACCESS read-only
4455 DESCRIPTION
4456 "Write access is not required."
4457
4458 OBJECT atmVccAal5CpcsReceiveSduSize
4459 MIN-ACCESS read-only
4460 DESCRIPTION
4461 "Write access is not required."
4462
4463 OBJECT atmVccAal5EncapsType
4464 MIN-ACCESS read-only
4465 DESCRIPTION
4466 "Write access is not required."
4467 ::= { atmMIBCompliances 1 }
4468
4469
4470 -- Deprecated Definitions - Groups
4471
4472
4473
4474
4475
4476 <span class="grey">Tesink Standards Track [Page 80]</span></pre>
4477 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-81" ></span>
4478 <span class="grey"><a href="./rfc2515">RFC 2515</a> ATM Management Objects February 1999</span>
4479
4480
4481 atmInterfaceConfGroup OBJECT-GROUP
4482 OBJECTS {
4483 atmInterfaceMaxVpcs, atmInterfaceMaxVccs,
4484 atmInterfaceConfVpcs, atmInterfaceConfVccs,
4485 atmInterfaceMaxActiveVpiBits,
4486 atmInterfaceMaxActiveVciBits,
4487 atmInterfaceIlmiVpi,
4488 atmInterfaceIlmiVci,
4489 atmInterfaceAddressType,
4490 atmInterfaceAdminAddress,
4491 atmInterfaceMyNeighborIpAddress,
4492 atmInterfaceMyNeighborIfName }
4493 STATUS deprecated
4494 DESCRIPTION
4495 "A collection of objects providing configuration
4496 information about an ATM interface."
4497 ::= { atmMIBGroups 1 }
4498
4499 atmTrafficDescrGroup OBJECT-GROUP
4500 OBJECTS {
4501 atmTrafficDescrType, atmTrafficDescrParam1,
4502 atmTrafficDescrParam2, atmTrafficDescrParam3,
4503 atmTrafficDescrParam4, atmTrafficDescrParam5,
4504 atmTrafficQoSClass, atmTrafficDescrRowStatus}
4505 STATUS deprecated
4506 DESCRIPTION
4507 "A collection of objects providing information
4508 about ATM traffic descriptor type and
4509 the associated parameters."
4510 ::= { atmMIBGroups 2 }
4511
4512 atmVpcTerminationGroup OBJECT-GROUP
4513 OBJECTS {atmVplOperStatus, atmVplAdminStatus,
4514 atmVplLastChange,
4515 atmVplReceiveTrafficDescrIndex,
4516 atmVplTransmitTrafficDescrIndex,
4517 atmVplRowStatus }
4518 STATUS deprecated
4519 DESCRIPTION
4520 "A collection of objects providing
4521 information about a VPL at an ATM interface
4522 which terminates a VPC
4523 (i.e., one which is NOT cross-connected
4524 to other VPLs)."
4525 ::= { atmMIBGroups 5 }
4526
4527 atmVccTerminationGroup OBJECT-GROUP
4528 OBJECTS {atmVclOperStatus, atmVclAdminStatus,
4529
4530
4531
4532 <span class="grey">Tesink Standards Track [Page 81]</span></pre>
4533 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-82" ></span>
4534 <span class="grey"><a href="./rfc2515">RFC 2515</a> ATM Management Objects February 1999</span>
4535
4536
4537 atmVclLastChange,
4538 atmVclReceiveTrafficDescrIndex,
4539 atmVclTransmitTrafficDescrIndex,
4540 atmVccAalType, atmVclRowStatus }
4541 STATUS deprecated
4542 DESCRIPTION
4543 "A collection of objects providing information
4544 about a VCL at an ATM interface
4545 which terminates a VCC (i.e., one which is
4546 NOT cross-connected to other VCLs)."
4547 ::= { atmMIBGroups 6 }
4548
4549 atmVpCrossConnectGroup OBJECT-GROUP
4550 OBJECTS { atmVplReceiveTrafficDescrIndex,
4551 atmVplTransmitTrafficDescrIndex,
4552 atmVplOperStatus, atmVplRowStatus,
4553 atmVpCrossConnectAdminStatus,
4554 atmVpCrossConnectL2HOperStatus,
4555 atmVpCrossConnectH2LOperStatus,
4556 atmVpCrossConnectL2HLastChange,
4557 atmVpCrossConnectH2LLastChange,
4558 atmVpCrossConnectRowStatus,
4559 atmVplCrossConnectIdentifier,
4560 atmVpCrossConnectIndexNext }
4561 STATUS deprecated
4562 DESCRIPTION
4563 "A collection of objects providing
4564 information about a VP cross-connect
4565 and the associated VPLs that are
4566 cross-connected together."
4567 ::= { atmMIBGroups 7 }
4568
4569 atmVcCrossConnectGroup OBJECT-GROUP
4570 OBJECTS { atmVclReceiveTrafficDescrIndex,
4571 atmVclTransmitTrafficDescrIndex,
4572 atmVclOperStatus, atmVclRowStatus,
4573 atmVcCrossConnectAdminStatus,
4574 atmVcCrossConnectL2HOperStatus,
4575 atmVcCrossConnectH2LOperStatus,
4576 atmVcCrossConnectL2HLastChange,
4577 atmVcCrossConnectH2LLastChange,
4578 atmVcCrossConnectRowStatus,
4579 atmVclCrossConnectIdentifier,
4580 atmVcCrossConnectIndexNext }
4581 STATUS deprecated
4582 DESCRIPTION
4583 "A collection of objects providing
4584 information about a VC cross-connect
4585
4586
4587
4588 <span class="grey">Tesink Standards Track [Page 82]</span></pre>
4589 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-83" ></span>
4590 <span class="grey"><a href="./rfc2515">RFC 2515</a> ATM Management Objects February 1999</span>
4591
4592
4593 and the associated VCLs that are
4594 cross-connected together."
4595 ::= { atmMIBGroups 8 }
4596
4597
4598 -- {atmMIB 3} has been used by [<a href="#ref-19" title="&quot;Definitions of Textual Conventions and OBJECT-IDENTITIES for ATM Management&quot;">19</a>].
4599
4600 END
4601
4602 <span class="h2"><a class="selflink" id="section-10" href="#section-10">10</a>. Acknowledgments</span>
4603
4604 This memo is the result of the work of the AToMMIB Working Group.
4605
4606 <span class="h2"><a class="selflink" id="section-11" href="#section-11">11</a>. References</span>
4607
4608 [<a id="ref-1">1</a>] Harrington, D., Presuhn, R. and B. Wijnen, "An
4609 Architecture for Describing SNMP Management Frameworks", <a href="./rfc2271">RFC</a>
4610 <a href="./rfc2271">2271</a>, January 1998.
4611
4612 [<a id="ref-2">2</a>] Rose, M. and K. McCloghrie, "Structure and Identification of
4613 Management Information for TCP/IP-based Internets", STD 16, <a href="./rfc1155">RFC</a>
4614 <a href="./rfc1155">1155</a>, May 1990.
4615
4616 [<a id="ref-3">3</a>] Rose, M. and K. McCloghrie, "Concise MIB Definitions", STD 16,
4617 <a href="./rfc1212">RFC 1212</a>, March 1991.
4618
4619 [<a id="ref-4">4</a>] Rose, M., "A Convention for Defining Traps for use with the
4620 SNMP", <a href="./rfc1215">RFC 1215</a>, March 1991.
4621
4622 [<a id="ref-5">5</a>] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M. and S.
4623 Waldbusser, "Structure of Management Information for Version 2
4624 of the Simple Network Management Protocol (SNMPv2)", <a href="./rfc1902">RFC 1902</a>,
4625 January 1996.
4626
4627 [<a id="ref-6">6</a>] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M. and S.
4628 Waldbusser, "Textual Conventions for Version 2 of the Simple
4629 Network Management Protocol (SNMPv2)", <a href="./rfc1903">RFC 1903</a>, January 1996.
4630
4631 [<a id="ref-7">7</a>] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M. and S.
4632 Waldbusser, "Conformance Statements for Version 2 of the Simple
4633 Network Management Protocol (SNMPv2)", <a href="./rfc1904">RFC 1904</a>, January 1996.
4634
4635 [<a id="ref-8">8</a>] Case, J., Fedor, M., Schoffstall, M. and J. Davin, "Simple
4636 Network Management Protocol", STD 15, <a href="./rfc1157">RFC 1157</a>, May 1990.
4637
4638 [<a id="ref-9">9</a>] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M. and S.
4639 Waldbusser, "Introduction to Community-based SNMPv2", <a href="./rfc1901">RFC 1901</a>,
4640 January 1996.
4641
4642
4643
4644 <span class="grey">Tesink Standards Track [Page 83]</span></pre>
4645 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-84" ></span>
4646 <span class="grey"><a href="./rfc2515">RFC 2515</a> ATM Management Objects February 1999</span>
4647
4648
4649 [<a id="ref-10">10</a>] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M. and S.
4650 Waldbusser, "Transport Mappings for Version 2 of the Simple
4651 Network Management Protocol (SNMPv2)", <a href="./rfc1906">RFC 1906</a>, January 1996.
4652
4653 [<a id="ref-11">11</a>] Case, J., Harrington D., Presuhn R. and B. Wijnen, "Message
4654 Processing and Dispatching for the Simple Network Management
4655 Protocol (SNMP)", <a href="./rfc2272">RFC 2272</a>, January 1998.
4656
4657 [<a id="ref-12">12</a>] Blumenthal, U. and B. Wijnen, "User-based Security Model (USM)
4658 for version 3 of the Simple Network Management Protocol
4659 (SNMPv3)", <a href="./rfc2274">RFC 2274</a>, January 1998.
4660
4661 [<a id="ref-13">13</a>] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M. and S.
4662 Waldbusser, "Protocol Operations for Version 2 of the Simple
4663 Network Management Protocol (SNMPv2)", <a href="./rfc1905">RFC 1905</a>, January 1996.
4664
4665 [<a id="ref-14">14</a>] Levi, D., Meyer, P. and B. Stewart, MPv3 Applications", <a href="./rfc2273">RFC</a>
4666 <a href="./rfc2273">2273</a>, January 1998.
4667
4668 [<a id="ref-15">15</a>] Wijnen, B., Presuhn, R. and K. McCloghrie, "View-based Access
4669 Control Model (VACM) for the Simple Network Management Protocol
4670 (SNMP)", <a href="./rfc2275">RFC 2275</a>, January 1998.
4671
4672 [<a id="ref-16">16</a>] McCloghrie, K. and M. Rose, Editors, "Management Information
4673 Base for Network Management of TCP/IP-based internets: MIB-II",
4674 STD 17, <a href="./rfc1213">RFC 1213</a>, March 1991.
4675
4676 [<a id="ref-17">17</a>] McCloghrie, K. and F. Kastenholz, "The Interfaces Group MIB",
4677 <a href="./rfc2233">RFC 2233</a>, November 1997.
4678
4679 [<a id="ref-18">18</a>] Brown, T. and K. Tesink, "Definitions of Managed Objects for
4680 SMDS Interfaces", <a href="./rfc1694">RFC 1694</a>, May 1994.
4681
4682 [<a id="ref-19">19</a>] Noto, M., Spiegel, E. and K. Tesink, Editors, "Definitions of
4683 Textual Conventions and OBJECT-IDENTITIES for ATM Management",
4684 <a href="./rfc2514">RFC 2514</a>, February 1999.
4685
4686 [<a id="ref-20">20</a>] ATM Forum, ATM User-Network Interface, Version 3.0 (UNI 3.0)
4687 Specification, 1994.
4688
4689 [<a id="ref-21">21</a>] ATM Forum, B-ICI Specification, Version 2.0, af-bici-0013.002,
4690 November 1995.
4691
4692 [<a id="ref-22">22</a>] "ATM Forum Private Network-Network Interface Specification,
4693 Version 1.0 (PNNI 1.0)", af-sig-0055.000, March 1996.
4694
4695 [<a id="ref-23">23</a>] "ATM Forum Integrated Local Management Interface (ILMI)
4696 Specification", Version 4.0", af-ilmi-0065.000, September 1996.
4697
4698
4699
4700 <span class="grey">Tesink Standards Track [Page 84]</span></pre>
4701 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-85" ></span>
4702 <span class="grey"><a href="./rfc2515">RFC 2515</a> ATM Management Objects February 1999</span>
4703
4704
4705 [<a id="ref-24">24</a>] Ahmed, M. and K. Tesink, "Definitions of Managed Objects for ATM
4706 Management Version 8.0 using SMIv2", <a href="./rfc1695">RFC 1695</a>, August 1994.
4707
4708 <span class="h2"><a class="selflink" id="section-12" href="#section-12">12</a>. Security Considerations</span>
4709
4710 There are a number of management objects defined in this MIB that
4711 have a MAX-ACCESS clause of read-write and/or read-create. Such
4712 objects may be considered sensitive or vulnerable in some network
4713 environments. The support for SET operations in a non-secure
4714 environment without proper protection can have a negative effect on
4715 network operations.
4716
4717 The managed objects in this MIB contain sensitive information since,
4718 collectively, they allow tracing and influencing of virtual
4719 connections in ATM switches or networks and provide information of
4720 their traffic characteristics.
4721
4722 It is thus important to control even GET access to these objects and
4723 possibly to even encrypt the values of these object when sending them
4724 over the network via SNMP. Not all versions of SNMP provide features
4725 for such a secure environment.
4726
4727 SNMPv1 by itself is not a secure environment. Even if the network
4728 itself is secure (for example by using IPSec), even then, there is no
4729 control as to who on the secure network is allowed to access and
4730 GET/SET (read/change/create/delete) the objects in this MIB.
4731
4732 It is recommended that the implementers consider the security
4733 features as provided by the SNMPv3 framework. Specifically, the use
4734 of the User-based Security Model <a href="./rfc2274">RFC 2274</a> [<a href="#ref-12" title="&quot;User-based Security Model (USM) for version 3 of the Simple Network Management Protocol (SNMPv3)&quot;">12</a>] and the View-based
4735 Access Control Model <a href="./rfc2275">RFC 2275</a> [<a href="#ref-15" title="&quot;View-based Access Control Model (VACM) for the Simple Network Management Protocol (SNMP)&quot;">15</a>] is recommended.
4736
4737 It is then a customer/user responsibility to ensure that the SNMP
4738 entity giving access to an instance of this MIB, is properly
4739 configured to give access to the objects only to those principals
4740 (users) that have legitimate rights to indeed GET or SET
4741 (change/create/delete) them.
4742
4743 <span class="h2"><a class="selflink" id="section-13" href="#section-13">13</a>. Author's Address</span>
4744
4745 Kaj Tesink
4746 Bellcore
4747 331 Newman Springs Road
4748 P.O. Box 7020
4749 Red Bank, NJ 07701-7020
4750
4751 Phone: (732) 758-5254
4752 EMail: [email protected]
4753
4754
4755
4756 <span class="grey">Tesink Standards Track [Page 85]</span></pre>
4757 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-86" ></span>
4758 <span class="grey"><a href="./rfc2515">RFC 2515</a> ATM Management Objects February 1999</span>
4759
4760
4761 <span class="h2"><a class="selflink" id="section-14" href="#section-14">14</a>. Intellectual Property</span>
4762
4763 The IETF takes no position regarding the validity or scope of any
4764 intellectual property or other rights that might be claimed to
4765 pertain to the implementation or use of the technology described in
4766 this document or the extent to which any license under such rights
4767 might or might not be available; neither does it represent that it
4768 has made any effort to identify any such rights. Information on the
4769 IETF's procedures with respect to rights in standards-track and
4770 standards-related documentation can be found in <a href="https://www.rfc-editor.org/bcp/bcp11">BCP-11</a>. Copies of
4771 claims of rights made available for publication and any assurances of
4772 licenses to be made available, or the result of an attempt made to
4773 obtain a general license or permission for the use of such
4774 proprietary rights by implementors or users of this specification can
4775 be obtained from the IETF Secretariat.
4776
4777 The IETF invites any interested party to bring to its attention any
4778 copyrights, patents or patent applications, or other proprietary
4779 rights which may cover technology that may be required to practice
4780 this standard. Please address the information to the IETF Executive
4781 Director.
4782
4783
4784
4785
4786
4787
4788
4789
4790
4791
4792
4793
4794
4795
4796
4797
4798
4799
4800
4801
4802
4803
4804
4805
4806
4807
4808
4809
4810
4811
4812 <span class="grey">Tesink Standards Track [Page 86]</span></pre>
4813 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-87" ></span>
4814 <span class="grey"><a href="./rfc2515">RFC 2515</a> ATM Management Objects February 1999</span>
4815
4816
4817 <span class="h2"><a class="selflink" id="section-15" href="#section-15">15</a>. Full Copyright Statement</span>
4818
4819 Copyright (C) The Internet Society (1999). All Rights Reserved.
4820
4821 This document and translations of it may be copied and furnished to
4822 others, and derivative works that comment on or otherwise explain it
4823 or assist in its implementation may be prepared, copied, published
4824 and distributed, in whole or in part, without restriction of any
4825 kind, provided that the above copyright notice and this paragraph are
4826 included on all such copies and derivative works. However, this
4827 document itself may not be modified in any way, such as by removing
4828 the copyright notice or references to the Internet Society or other
4829 Internet organizations, except as needed for the purpose of
4830 developing Internet standards in which case the procedures for
4831 copyrights defined in the Internet Standards process must be
4832 followed, or as required to translate it into languages other than
4833 English.
4834
4835 The limited permissions granted above are perpetual and will not be
4836 revoked by the Internet Society or its successors or assigns.
4837
4838 This document and the information contained herein is provided on an
4839 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
4840 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING
4841 BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION
4842 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
4843 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
4844
4845
4846
4847
4848
4849
4850
4851
4852
4853
4854
4855
4856
4857
4858
4859
4860
4861
4862
4863
4864
4865
4866
4867
4868 Tesink Standards Track [Page 87]
4869 </pre>