idnits 2.17.1 draft-ietf-atommib-atm1ng-05.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Looks like you're using RFC 2026 boilerplate. This must be updated to follow RFC 3978/3979, as updated by RFC 4748. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- ** Missing document type: Expected "INTERNET-DRAFT" in the upper left hand corner of the first page ** Missing expiration date. The document expiration date should appear on the first and last page. ** The document seems to lack a 1id_guidelines paragraph about Internet-Drafts being working documents. ** The document seems to lack a 1id_guidelines paragraph about 6 months document validity -- however, there's a paragraph with a matching beginning. Boilerplate error? ** The document seems to lack a 1id_guidelines paragraph about the list of current Internet-Drafts. ** The document seems to lack a 1id_guidelines paragraph about the list of Shadow Directories. ** Expected the document's filename to be given on the first page, but didn't find any == No 'Intended status' indicated for this document; assuming Proposed Standard == The page length should not exceed 58 lines per page, but there was 102 longer pages, the longest (page 2) being 117 lines == It seems as if not all pages are separated by form feeds - found 0 form feeds but 103 pages Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an Introduction section. (A line matching the expected section header was found, but with an unexpected indentation: ' 2. Introduction' ) ** The document seems to lack a Security Considerations section. (A line matching the expected section header was found, but with an unexpected indentation: ' 14. Security Considerations' ) ** The document seems to lack an IANA Considerations section. (See Section 2.2 of https://www.ietf.org/id-info/checklist for how to handle the case when there are no actions for IANA.) ** The document seems to lack an Authors' Addresses Section. ** There are 25 instances of too long lines in the document, the longest one being 7 characters in excess of 72. ** The abstract seems to contain references ([20], [15], [2], [21], [16], [3], [17], [22], [4], [23], [18], [5], [19], [6], [7], [8], [9], [10], [11], [12], [13], [14], [1]), which it shouldn't. Please replace those with straight textual mentions of the documents in question. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year == Line 248 has weird spacing: '... |svc svc...' == Line 369 has weird spacing: '...pported supp...' == Line 1130 has weird spacing: '...rrently estab...' == Line 1150 has weird spacing: '...rrently estab...' == Line 1159 has weird spacing: '... "The maxim...' == (6 more instances...) == Couldn't figure out when the document was first submitted -- there may comments or warnings related to the use of a disclaimer for pre-RFC5378 work that could not be issued because of this. Please check the Legal Provisions document at https://trustee.ietf.org/license-info to determine if you need the pre-RFC5378 disclaimer. -- The document date (August 15, 1998) is 9386 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) -- Missing reference section? '5' on line 4139 looks like a reference -- Missing reference section? '6' on line 4146 looks like a reference -- Missing reference section? '19' on line 4225 looks like a reference -- Missing reference section? '1' on line 4121 looks like a reference -- Missing reference section? '2' on line 4126 looks like a reference -- Missing reference section? '3' on line 4131 looks like a reference -- Missing reference section? '4' on line 4135 looks like a reference -- Missing reference section? '7' on line 4153 looks like a reference -- Missing reference section? '8' on line 4160 looks like a reference -- Missing reference section? '9' on line 4169 looks like a reference -- Missing reference section? '10' on line 4175 looks like a reference -- Missing reference section? '11' on line 4182 looks like a reference -- Missing reference section? '12' on line 4188 looks like a reference -- Missing reference section? '13' on line 4192 looks like a reference -- Missing reference section? '14' on line 4199 looks like a reference -- Missing reference section? '15' on line 4203 looks like a reference -- Missing reference section? '22' on line 4235 looks like a reference -- Missing reference section? '16' on line 4209 looks like a reference -- Missing reference section? '17' on line 4217 looks like a reference -- Missing reference section? '20' on line 4229 looks like a reference -- Missing reference section? '18' on line 4221 looks like a reference -- Missing reference section? '21' on line 4232 looks like a reference -- Missing reference section? '23' on line 4239 looks like a reference Summary: 14 errors (**), 0 flaws (~~), 11 warnings (==), 24 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Definitions of Managed Objects 3 for ATM Management 5 August 15, 1998 7 Kaj Tesink (editor) 8 Bell Communications Research 9 331 Newman Springs Road 10 Red Bank, NJ 07701 12 kaj@cc.bellcore.com 14 1. Status of this Memo 16 This document is an Internet-Draft. Internet-Drafts are 17 working documents of the Internet Engineering Task Force 18 (IETF), its areas, and its working groups. Note that other 19 groups may also distribute working documents as Internet- 20 Drafts. 22 Internet-Drafts are draft documents valid for a maximum of six 23 months and may be updated, replaced, or obsoleted by other 24 documents at any time. It is inappropriate to use Internet- 25 Drafts as reference material or to cite them other than as 26 ``work in progress.'' 28 To learn the current status of any Internet-Draft, please 29 check the ``1id-abstracts.txt'' listing contained in the 30 Internet- Drafts Shadow Directories on ftp.ietf.org (US East 31 Coast), nic.nordu.net (Europe), ftp.isi.edu (US West Coast), 32 or munnari.oz.au (Pacific Rim). 34 Copyright Notice 36 Copyright (C) The Internet Society (1998). All Rights 37 Reserved. 39 draft ATM Management Objects August 15, 1998 41 Abstract 43 This memo defines an experimental portion of the Management 44 Information Base (MIB) for use with network management 45 protocols in the Internet community. In particular, it 46 describes objects used for managing ATM-based interfaces, 47 devices, networks and services. 49 2. Introduction 51 This memo defines an experimental portion of the Management 52 Information Base (MIB) for use with network management 53 protocols in the Internet community. In particular, it 54 describes objects used for managing ATM-based interfaces, 55 devices, networks and services. 57 This memo specifies a MIB module in a manner that is both 58 compliant to the SNMPv2 SMI[5], and semantically identical to 59 the peer SNMPv1 definitions. 61 Textual Conventions used in this MIB are defined in [6] and 62 [19]. 64 3. The SNMP Network Management Framework 66 The SNMP Management Framework presently consists of five major 67 components: 69 0 An overall architecture, described in RFC 2271 [1]. 71 0 Mechanisms for describing and naming objects and events 72 for the purpose of management. The first version of this 73 Structure of Management Information (SMI) is called SMIv1 74 and described in RFC 1155 [2], RFC 1212 [3] and RFC 1215 75 [4]. The second version, called SMIv2, is described in 76 RFC 1902 [5], RFC 1903 [6] and RFC 1904 [7]. 78 0 Message protocols for transferring management 79 information. The first version of the SNMP message 80 protocol is called SNMPv1 and described in RFC 1157 [8]. 81 A second version of the SNMP message protocol, which is 82 not an Internet standards track protocol, is called 83 SNMPv2c and described in RFC 1901 [9] and RFC 1906 [10]. 84 The third version of the message protocol is called 85 SNMPv3 and described in RFC 1906 [10], RFC 2272 [11] and 87 draft ATM Management Objects August 15, 1998 89 RFC 2274 [12]. 91 0 Protocol operations for accessing management information. 92 The first set of protocol operations and associated PDU 93 formats is described in RFC 1157 [8]. A second set of 94 protocol operations and associated PDU formats is 95 described in RFC 1905 [13]. 97 0 A set of fundamental applications described in RFC 2273 98 [14] and the view-based access control mechanism 99 described in RFC 2275 [15]. 101 Managed objects are accessed via a virtual information store, 102 termed the Management Information Base or MIB. Objects in the 103 MIB are defined using the mechanisms defined in the SMI. 105 This memo specifies a MIB module that is compliant to the 106 SMIv2. A MIB conforming to the SMIv1 can be produced through 107 the appropriate translations. The resulting translated MIB 108 must be semantically equivalent, except where objects or 109 events are omitted because no translation is possible (e.g., 110 use of Counter64). Some machine readable information in SMIv2 111 will be converted into textual descriptions in SMIv1 during 112 the translation process. However, this loss of machine 113 readable information is not considered to change the semantics 114 of the MIB. 116 draft ATM Management Objects August 15, 1998 118 4. Object Definitions 120 Managed objects are accessed via a virtual information store, 121 termed the Management Information Base or MIB. Objects in the 122 MIB are defined using the subset of Abstract Syntax Notation 123 One (ASN.1) defined in the SMI. In particular, each object 124 type is named by an OBJECT IDENTIFIER, an administratively 125 assigned name. The object type together with an object 126 instance serves to uniquely identify a specific instantiation 127 of the object. For human convenience, we often use a textual 128 string, termed the descriptor, to also refer to the object 129 type. 131 draft ATM Management Objects August 15, 1998 133 5. ATM Terminology 135 Some basic ATM terminologies are described in this section to 136 facilitate defining the ATM managed objects. 138 5.1. VCL/VPL and VCC/VPC 140 There are two distinct types of ATM virtual connections: 141 Virtual Channel Connections (VCCs) and Virtual Path Connection 142 (VPCs). As shown in Figures 1 and 2, ATM virtual connections 143 consist of concatenated series of virtual links which forms a 144 path between two end points, with each concatenation occurring 145 at an ATM switch. Virtual links of VCCs are called Virtual 146 Channel Links (VCLs). Virtual links of VPCs are called Virtual 147 Path Links (VPLs). The VCI and VPI fields in the ATM cell 148 header associate each cell of a VCC with a particular VCL over 149 a given physical link. The VPI field in the ATM cell header 150 associates each cell of a VPC with a particular VPL over a 151 given physical link. Switches route cells between VCLs (or 152 VPLs) via a cross-connect function according to the cells' 153 VCI/VPI (or VPI) values. 155 <-----------------------VCC--------------------------> 156 ------------ ----------- 157 |ATM | |ATM | 158 |X-Connect | |X-Connect | 159 VCL1 |Point | VCL2 |Point | VCL3 160 O---------|----X-----|-------|-----|----X-----|-------O 161 | | | | 162 ------------ ------------ 163 ATM Switch ATM Switch 165 Figure 1: Virtual Channel Links and 166 Virtual Channel Connection 168 draft ATM Management Objects August 15, 1998 170 <-----------------------VPC--------------------------> 171 ------------ ----------- 172 |ATM | |ATM | 173 |X-Connect | |X-Connect | 174 VPL1 |Point | VPL2 |Point | VPL3 175 O---------|----X-----|-------|-----|----X-----|-------O 176 | | | | 177 ------------ ------------ 178 ATM Switch ATM Switch 180 Figure 2: Virtual Path Links and 181 Virtual Path Connection 183 A single ATM end-system or switch does not support the whole 184 end-to-end span of a VCC (or VPC). Rather, multiple ATM end- 185 systems and/or switches each support one piece of the VCC (or 186 VPC). That is, each ATM end-system (or ATM switch) at one end 187 of the VCC/VPC supports its end of the VCC/VPC plus the VCL or 188 VPL on its external interface, and each switch through which 189 the VCC/VPC passes supports the pair of VCLs/VPLs on its 190 external interfaces as well as the cross-connection of those 191 VCLs/VPLs. Thus, the end-to-end management of a VCC or VPC is 192 achieved only by appropriate management of its individual 193 pieces in combination. 195 Note that for management purposes, an ATM network may be 196 viewed as a large distributed switch by hiding all the 197 network's internal connectivity as being internal to the 198 distributed switch (as shown in Figure 2a). This model may 199 for example be used for Customer Network Management (CNM) 200 purposes. 202 draft ATM Management Objects August 15, 1998 204 <---------------------VCC---------------------------> 205 -------------------------------------- 206 | | 207 | ---------- ---------- | 208 | | ATM | | ATM | | 209 VCL1 | | Switch | | Switch | | VCL3 210 O-------|-|--------|------/-------|--------|-|------O 211 | | | | | | 212 | ---------- ---------- | 213 | | 214 | ATM Network | 215 -------------------------------------- 217 Figure 2a: ATM Network modeled as a large distributed 218 switch 220 A VCC has a set of traffic characteristics (i.e., bandwidth 221 parameters, service category parameters, etc.). VCLs inherit 222 their traffic characteristics from the VCC of which they are a 223 part. VCCs are bi-directional by definition. However, the 224 traffic parameters in the two directions of a connection can 225 be symmetric or asymmetric, i.e., the two directions can have 226 the same or different traffic flows. A uni-directional 227 traffic flow across a VCC is achieved by assigning a zero 228 bandwidth in one direction. Note that in addition to the 229 bandwidth required by the user traffic flow, bandwidth is also 230 required for OAM cell flows, even for the zero-bandwidth 231 direction of a uni-directional connection. These same 232 principles apply to VPCs. 234 5.2. PVC, SVC and Soft PVC 236 A Permanent Virtual Connection (PVC) is a provisioned VCC or 237 VPC. A Switched Virtual Connection (SVC) is a switched VCC or 238 VPC that is set up in real-time via call set-up signaling 239 procedures. A PVC (or an SVC) can be a point-to-point, 240 point-to-multipoint, or multipoint-to-multipoint VCC or VPC. 241 A Soft PVC is a connection of which portions are switched, 242 while other portions are permanent (see Figure 3 and [22]). 244 +--------+ +--------+ +--------+ 246 draft ATM Management Objects August 15, 1998 248 pvc| ATM |svc svc | ATM |svc svc | ATM |pvc 249 ----| Switch |-----------| Switch |-----------| Switch |---- 250 +--------+ +--------+ +--------+ 252 Figure 3: An example of a Soft PVC 254 5.3. Traffic Management Parameters 256 5.3.1. Traffic Policing and Traffic Shaping Parameters 258 In order to allocate resources fairly among different users, 259 some networks police traffic at resource access points. The 260 traffic enforcement or policing taken at a UNI is called Usage 261 Parameter Control (UPC) and is conceptually activated on an 262 incoming VCL or VPL as shown in Figure 4. The use of the 263 traffic enforcer at the ingress of the connection is to make 264 sure that the user traffic does not exceed the negotiated 265 traffic parameters such as the peak cell rate associated with 266 a specific traffic descriptor type. 268 ---------- ---------- 269 UNI | ATM | NNI | ATM | UNI 270 | | switch | | | switch | | 271 O<---|---->X(UPC) |<----|------>| (UPC)X<-----|--->O 272 | VCL | | | VCL | | VCL | 273 ---------- ---------- 275 Figure 4: An Example of a UPC 277 In addition, traffic shaping may be performed on an outgoing 278 VPL or VCL at a given ATM interface. The function of the ATM 279 traffic shaper, conceptually either at the source or an egress 280 point of the connection, is to smooth the outgoing cell 281 traffic inter-arrival time. If policing or shaping is not 282 performed then the policing or shaping algorithm is not 283 activated. 285 5.3.2. Cell Loss Priority 287 To prioritize traffic during resource congestion, ATM cells 288 are assigned one of the two types of Cell Loss Priority (CLP), 290 draft ATM Management Objects August 15, 1998 292 CLP=0 and CLP=1. ATM cells with CLP=0 have a higher priority 293 in regard to cell loss than ATM cells with CLP=1. Therefore, 294 during resource congestions, CLP=1 cells are dropped before 295 any CLP=0 cell is dropped. 297 5.3.3. QoS Class 299 RFC1695 specified that one of a number of Quality of Service 300 (QoS) classes is assigned to a VCC or VPC by associating the 301 object atmTrafficQoSClass with each VCL or VPL. However, new 302 insights in ATM traffic management have caused this object to 303 be deprecated. 305 5.3.4. Service Category 307 Replacing QoS Class, VPLs and VCLs are qualified in terms of 308 their service category (atmServiceCategory). When properly 309 configured, VCLs (or VPLs) concatenated to form a VCC (or VPC) 310 will all have the same service category class as that of the 311 VCC (or VPC). 313 5.4. Max Active and Max Current VPI and VCI Bits 315 A manager may wish to configure the maximum number of VPI and 316 VCI bits that can be used to identify VPIs and VCIs on a given 317 ATM interface. This value can be less than or equal to the 318 maximum number of bits supported by the interface hardware, 319 and is referred to in the MIB as the Max Active VPI Bits and 320 Max Active VCI Bits. 322 However, a manager may not be able to configure the Max Active 323 Bits on both ends of an ATM link. For example, the manager 324 may not be allowed write access to the peer's MIB, or there 325 may be hardware limitations on the peer device. Therefore, 326 the two ATM devices may use ILMI to negotiate "Max Current" 327 VPI and VCI bits, which is the maximum number of bits that 328 both interfaces are willing to support. This is illustrated 329 in Figure 5. The relationship between the different parameters 330 is illustrated in Figure 6. Note that if ILMI negotiation is 331 not supported, then the devices have no choice but to use the 332 configured Max Active bits, and assume that it has been 333 configured to the same value on both ends of the link. 335 draft ATM Management Objects August 15, 1998 337 +--------+ +--------+ +--------+ 338 | ATM | IF a IF b | ATM | IF c IF d | ATM | 339 | Device |--------------| Device |--------------| Device | 340 +--------+ +--------+ +--------+ 342 IF a: Max Active VPI Bits = 6 (configured) 343 Max Current VPI Bits = 6 (negotiated) 345 IF b: Max Active VPI Bits = 8 (configured) 346 Max Current VPI Bits = 6 (negotiated) 348 IF c: Max Active VPI Bits = 8 (configured) 349 Max Current VPI Bits = 8 (negotiated) 351 IF d: Max Active VPI Bits = 8 (configured) 352 Max Current VPI Bits = 8 (negotiated) 354 (between IF a and IF b, the minimum of the two configured 355 "Max Active VPI Bits" is 6, so both interfaces set their 356 "Max Current VPI Bits" to 6. Since IF c and IF d both 357 are configured with "Max Active VPI Bits" of 8, they 358 set their "Max Current VPI Bits" to 8.) 360 Figure 5 362 MSB LSB 363 +----------------------------------------------------+ 364 | | | | | 365 +----------------------------------------------------+ 366 ^ ^ ^ ^ 367 | | | | 368 Max bits Max Bits Max Max 369 supported supported Active (config.) current (negotiated) 370 by MIB by h/w Bits Bits 372 Figure 6 374 6. Overview 376 ATM management objects are used to manage ATM interfaces, ATM 377 virtual links, ATM cross-connects, AAL5 entities and AAL5 378 connections supported by ATM hosts, ATM switches and ATM 380 draft ATM Management Objects August 15, 1998 382 networks. This section provides an overview and background of 383 how to use this MIB and other potential MIBs for this purpose. 385 The purpose of this memo is primarily to manage ATM PVCs. ATM 386 SVCs are also represented by the management information in 387 this MIB. However, full management of SVCs may require 388 additional capabilities which are beyond the scope of this 389 memo. 391 6.1. Background 393 In addition to the MIB module defined in this memo, other MIB 394 modules are necessary to manage ATM interfaces, links and 395 cross-connects. Examples include MIB II for general system 396 and interface management [16][17], the DS3 or SONET MIBs for 397 management of physical interfaces, and, as appropriate, MIB 398 modules for applications that make use of ATM, such as SMDS. 399 These MIB modules are outside the scope of this specification. 401 The current specification of this ATM MIB is based on SNMPv2- 402 SMI. 404 6.2. Structure of the MIB 406 The managed ATM objects are arranged into the following 407 tables: 408 (1) ATM interface configuration table 409 (2) ATM interface DS3 PLCP and TC sublayer tables 410 (3) ATM traffic parameter table 411 (4) ATM interface virtual link (VPL/VCL) configuration 412 tables 413 (5) ATM VP/VC cross-connect tables 414 (6) AAL5 connection performance statistics table 416 Note that, managed objects for activation/deactivation of OAM 417 cell flows and ATM traps notifying virtual connection or 418 virtual link failures are outside the scope of this memo. 420 6.3. ATM Interface Configuration Table 422 This table contains information on ATM cell layer 423 configuration of local ATM interfaces on an ATM device in 424 addition to the information on such interfaces contained in 426 draft ATM Management Objects August 15, 1998 428 the ifTable. 430 6.4. ATM Interface DS3 PLCP and TC Layer Tables 432 These tables provide performance statistics of the DS3 PLCP 433 and TC sublayer of local ATM interfaces on a managed ATM 434 device. DS3 PLCP and TC sublayer are currently used to carry 435 ATM cells respectively over DS3 and SONET transmission paths. 437 6.5. ATM Virtual Link and Cross-Connect Tables 439 ATM virtual link and cross-connect tables model bi-directional 440 ATM virtual links and ATM cross-connects. The ATM VP/VC link 441 tables are implemented in an ATM host, ATM switch and ATM 442 network. The ATM switch and ATM network also implement the 443 ATM VP/VC cross-connect tables. Both link and cross-connect 444 tables are implemented in a carrier's network for Customer 445 Network Management (CNM) purposes. 447 The ATM virtual link tables are used to create, delete or 448 modify ATM virtual links in an ATM host, ATM switch and ATM 449 network. ATM virtual link tables along with the cross-connect 450 tables are used to create, delete or modify ATM cross-connects 451 in an ATM switch or ATM network (e.g., for CNM purposes). 453 For a PVC, the cross-connect between two VPLs is represented 454 in the atmVpCrossConnectTable of the ATM-MIB, indexed by the 455 atmVplCrossConnectIdentifier values for the two VPLs, and the 456 cross-connect between two VCLs is represented in the 457 atmVcCrossConnectTable of the ATM-MIB, indexed by the 458 atmVclCrossConnectIdentifier values for the two VCLs. 460 For an SVC or Soft PVC the VPL and VCL tables defined in this 461 memo are used. Hoewever, for an SVC or Soft PVC the cross- 462 connect between two VPLs is represented in the 463 atmSvcVpCrossConnectTable of the ATM2-MIB, indexed by the 464 atmVplCrossConnectIdentifier values for the two VPLs, and the 465 cross-connect between two VCLs is represented in the 466 atmSvcVcCrossConnectTable of the ATM2-MIB, indexed by the 467 atmVclCrossConnectIdentifier values for the two VCLs. 469 Note: The ATM2-MIB module was being defined in a separate memo 470 at the time of this publication. Please consult the RFC 472 draft ATM Management Objects August 15, 1998 474 directory for an exact reference. 476 7. Application of MIB II to ATM 478 7.1. The System Group 480 For the purposes of the sysServices object in the System Group 481 of MIB II [16], ATM is a data link layer protocol. Thus, for 482 ATM switches and ATM networks, sysServices will have the value 483 "2". 485 7.2. The Interface Group 487 The Interfaces Group of MIB II defines generic managed objects 488 for managing interfaces. This memo contains the media- 489 specific extensions to the Interfaces Group for managing ATM 490 interfaces. 492 This memo assumes the interpretation of the Interfaces Group 493 to be in accordance with [17] which states that the interfaces 494 table (ifTable) contains information on the managed resource's 495 interfaces and that each sub-layer below the internetwork 496 layer of a network interface is considered an interface. 497 Thus, the ATM cell layer interface is represented as an entry 498 in the ifTable. This entry is concerned with the ATM cell 499 layer as a whole, and not with individual virtual connections 500 which are managed via the ATM-specific managed objects 501 specified in this memo. The inter-relation of entries in the 502 ifTable is defined by Interfaces Stack Group defined in [17]. 504 7.2.1. Support of the ATM Cell Layer by ifTable 506 Some specific interpretations of ifTable for the ATM cell 507 layer follow. 509 draft ATM Management Objects August 15, 1998 511 Object Use for the generic ATM layer 512 ====== ============================= 514 ifIndex Each ATM port is represented by an ifEntry. 516 ifDescr Description of the ATM interface. 518 ifType The value that is allocated for ATM is 37. 520 ifSpeed The total bandwidth in bits per second 521 for use by the ATM layer. 523 ifPhysAddress The interface's address at the ATM protocol 524 sublayer; the ATM address which would be used 525 as the value of the Called Party Address 526 Information Element (IE) of a signalling 527 message for a connection which either: 528 - would terminate at this interface, or 529 - for which the Called Party Address IE 530 would need to be replaced by the Called 531 Party SubAddress IE before the message 532 was forwarded to any other interface. 533 For an interface on which signalling is 534 not supported, then the interface does not 535 necessarily have an address, but if it 536 does, then ifPhysAddress is the address which 537 would be used as above in the event that 538 signalling were supported. If the interface 539 has multiple such addresses, then ifPhysAddress 540 is its primary address. If the interface has 541 no addresses, then ifPhysAddress is an octet 542 string of zero length. Address encoding is as 543 per [20]. Note that addresses assigned for 544 purposes other than those listed above (e.g., 545 an address associated with the service provider 546 side of a public network UNI) may be represented 547 through atmInterfaceSubscrAddress. 549 ifAdminStatus See [17]. 551 ifOperStatus Assumes the value down(2) if the ATM cell 552 layer is down. 554 ifLastChange See [17]. 556 draft ATM Management Objects August 15, 1998 558 ifInOctets The number of received octets over the 559 interface, i.e., the number of received, 560 assigned cells multiplied by 53. 562 ifOutOctets The number of transmitted octets over the 563 interface, i.e., the number of transmitted, 564 assigned cells multiplied by 53. 566 ifInErrors The number of cells dropped due to 567 uncorrectable HEC errors. 569 ifInUnknownProtos The number of received cells discarded 570 during cell header validation, including 571 cells with unrecognized VPI/VCI values, 572 and cells with invalid cell header patterns. 573 If cells with undefined PTI values are discarded, 574 they are also counted here. 576 ifOutErrors See [17]. 578 ifName Textual name (unique on this system) of the 579 interface or an octet string of zero length. 581 ifLinkUpDownTrapEnable Default is disabled (2). 583 ifConnectorPresent Set to false (2). 585 ifHighSpeed See [17]. 587 ifHCInOctets The 64-bit version of ifInOctets; supported 588 if required by the compliance statements in [17]. 590 ifHCOutOctets The 64-bit version of ifOutOctets; supported 591 if required by the compliance statements in [17]. 593 ifAlias The non-volatile 'alias' name for the interface 594 as specified by a network manager. 596 8. Support of the AAL3/4 Based Interfaces 598 For the management of AAL3/4 CPCS layer, see [18]. 600 draft ATM Management Objects August 15, 1998 602 9. Support of the AAL5 Managed Objects 604 Support of AAL5 managed objects in an ATM switch and ATM host 605 are described below. 607 9.1. Managing AAL5 in a Switch 609 Managing AAL5 in a switch involves: 611 (1) performance management of an AAL5 entity as 612 an internal resource in a switch 614 (2) performance management of AAL5 per virtual connection 616 AAL5 in a switch is modeled as shown in Figure 7 and 8. AAL5 617 will be managed in a switch for only those virtual connections 618 that carry AAL5 and are terminated at the AAL5 entity in the 619 switch. Note that, the virtual channels within the ATM UNIs 620 carrying AAL5 will be switched by the ATM switching fabric 621 (termed as ATM Entity in the figure) to the virtual channels 622 on a proprietary internal interface associated with the AAL5 623 process (termed as AAL5 Entity in the figure). Therefore, 624 performance management of the AAL5 resource in the switch will 625 be modeled using the ifTable through an internal (pseudo-ATM) 626 virtual interface and the AAL5 performance management per 627 virtual connection will be supported using an additional AAL5 628 connection table in the ATM MIB. The association between the 629 AAL5 virtual link at the proprietary virtual, internal 630 interface and the ATM virtual link at the ATM interface will 631 be derived from the virtual channel cross-connect table and 632 the virtual channel link table in the ATM MIB. Note that for 633 the proprietary virtual interface the traffic transmit and 634 receive conventions in the virtual channel link table are as 635 follows: 637 Transmitting traffic: ATM Entity ---> AAL5 Entity 638 Receiving traffic: ATM Entity <--- AAL5 Entity 640 draft ATM Management Objects August 15, 1998 642 ___________________________ 643 | | 644 | ============= | 645 | | AAL5 | | 646 | | Entity | | 647 | ============= | 648 | | | 649 | -----Prop. Virtual Interface 650 | | | 651 | ============= | 652 | | ATM | | 653 | | Entity | | 654 | ============= | 655 |_____|__|__|__|__|_______| 656 | | | | | 657 ---------------- ATM UNIs 658 | | | | | 659 | | | | | 660 v v v v v 662 Figure 7: Model of an AAL5 Entity in a Switch 664 __________________ 665 | | 666 | AAL5 | 667 |________________| 668 | | 669 | Prop. Virtual | 670 | Interface | 671 |________________| 673 Figure 8: AAL5 Entity's Interface Stack in a Switch 675 9.2. Managing AAL5 in a Host 677 Managing AAL5 in a host involves managing the AAL5 sublayer 678 interface as shown in Figure 9 and 10. The AAL5 sublayer is 679 stacked directly over the ATM sublayer. The ifTable is 680 applied to the AAL5 sublayer as defined in Section 10.3. 682 draft ATM Management Objects August 15, 1998 684 ___________________________ 685 | | 686 | ============= | 687 | | AAL5 | | 688 | | Entity | | 689 | ============= | 690 | | ATM | | 691 | | Entity | | 692 | ============= | 693 |___________|_____________| 694 | 695 __|__ ATM UNI 696 | 697 | 698 v 700 Figure 9: Model of an AAL5 Entity in a Host 702 __________________ 703 | | 704 | AAL5 | 705 |________________| 706 | | 707 | ATM Layer | 708 |________________| 709 | | 710 | Physical Layer| 711 |________________| 713 Figure 10: AAL5 Entity's Interface Stack in a Host 715 draft ATM Management Objects August 15, 1998 717 9.3. Support of AAL5 by ifTable 719 The AAL5 entity in an ATM device (e.g., switch or host) is 720 managed using the ifTable. There are additional counters 721 specified for AAL5 than those specified in the ATM B-ICI 722 document [21]. Specific interpretations of ifTable for the 723 AAL5 CPCS layer are as follows. 725 Object Use for AAL5 CPCS layer entity 726 ====== ============================== 728 ifIndex Each AAL5 entity is represented by an ifEntry. 730 ifDescr Description of the AAL5 entity. 732 ifType The value that is allocated for AAL5 is 49. 734 ifMtu Set to the largest PDU size for the 735 AAL5 CPCS layer that can be processed 736 by the AAL5 entity. 738 ifSpeed Set to 0. 740 ifPhysAddress An octet string of zero length. 742 ifAdminStatus See [17]. 744 ifOperStatus Assumes the value down(2) if the AAL5 745 layer is down. 747 ifLastChange See [17]. 749 ifInOctets The number of received AAL5 CPCS PDU octets. 751 ifOutOctets The number of AAL5 CPCS PDU octets 752 transmitted. 754 ifInUcastPkts The number of received AAL5 CPCS PDUs passed 755 to a higher-layer. 757 ifOutUcastPkts The number of AAL5 CPCS PDUs received from a 758 higher-layer for transmission. 759 [Note: The number of AAL5 PDUs actually 760 transmitted is the number received from a 761 higher-layer for transmission minus any which 763 draft ATM Management Objects August 15, 1998 765 are counted by ifOutErrors and ifOutDiscards.] 767 ifInErrors Number of errored AAL5 CPCS PDUs received. 768 The types of errors counted include CRC-32 errors, 769 SAR time-out errors, and oversized SDU errors. 771 ifInUnknownProtos Set to 0. 773 ifInDiscards Number of received AAL5 CPCS PDUs discarded. 774 Possible reason may be input buffer overflow. 776 ifOutErrors Number of AAL5 CPCS PDUs that could not 777 be transmitted due to errors. 779 ifOutDiscards Number of AAL5 CPCS PDUs received for 780 transmission that are discarded. 781 Possible reason may be output buffer 782 overflow. 784 ifInMulticastPkts Set to 0. 786 ifInBroadcastPkts Set to 0. 788 ifOutMulticastPkts Set to 0. 790 ifOutBroadcastPkts Set to 0. 792 ifName Textual name (unique on this system) of the 793 AAL5 entity or an octet string of zero length. 795 ifHighSpeed Set to 0. 797 ifConnectorPresent Set to false (2). 799 ifPromiscuousMode Set to false(2). 801 ifLinkUpDownTrapEnable Default is disabled (2). 803 ifAlias The non-volatile 'alias' name for the interface 804 as specified by a network manager. 806 draft ATM Management Objects August 15, 1998 808 9.4. Support of Proprietary Virtual Interface by ifTable 810 Specific interpretations of ifTable for the proprietary 811 virtual, internal interface associated with an AAL5 entity in 812 an ATM switch are as follows. 814 draft ATM Management Objects August 15, 1998 816 Object Use for proprietary virtual, internal interface 817 associated with AAL entities 818 ====== =============================================== 820 ifIndex Each proprietary virtual, internal interface 821 associated with AAL entities is represented by an 822 ifEntry. 824 ifDescr Description of the proprietary virtual, internal 825 interface associated with AAL entities. 827 ifType The value that is allocated for proprietary 828 virtual, internal interface is 53. 830 ifSpeed See [17]. Set to 0 if the speed is not 831 known. 833 ifPhysAddress See [17]. An octet string of zero length 834 if no address is used for this interface. 836 ifAdminStatus See [17]. 838 ifOperStatus See [17]. 840 ifLastChange See [17]. 842 ifName Textual name (unique on this system) of the 843 interface or an octet string of zero length. 845 ifHighSpeed See [17]. Set to 0 if the speed is not known. 847 ifConnectorPresent Set to false (2). 849 ifLinkUpDownTrapEnable Default is disabled (2). 851 ifAlias The non-volatile 'alias' name for the interface 852 as specified by a network manager. 854 9.5. AAL5 Connection Performance Statistics Table 856 An AAL5 connection table is used to provide AAL5 performance 857 information for each AAL5 virtual connection that is 858 terminated at the AAL5 entity contained within an ATM switch 859 or host. 861 draft ATM Management Objects August 15, 1998 863 10. ILMI MIBs and the ATM Managed Objects 865 The ILMI MIBs are specified by the ATM Forum as a set of 866 several MIBs, all currently defined in the ILMI Specification 867 [23]. The ILMI protocols and MIBs allow two connected ATM 868 Interface Management Entities (IMEs) to exchange bi- 869 directional parameters, mainly to facilitate auto- 870 configuration between ATM peer entities. The support of the 871 ATM management functions by the ILMI MIBs and those contained 872 in this memo are compared in Table 1. In this table, "yes" in 873 the "ILMI MIBs" column indicates that the management 874 functions are supported by the ILMI MIBs. The parenthesized 875 numbers in the "This memo" column correspond to the sets of 876 tables enumerated in Section 6.2. 878 For that subset of management information which the ILMI MIBs 879 and this memo have in common, every effort has been made to 880 retain identical semantics and syntax, even though the MIB 881 objects are identified using different OBJECT IDENTIFIERs. 883 draft ATM Management Objects August 15, 1998 885 Table 1 - Structuring of ATM Managed Objects 886 ______________________________________________________________ 887 | |This |ILMI| 888 ATM Mgmt.Inf. |ATM Managed Objects |memo |MIBs| 889 ______________|_________________________________|_______|____| 891 Local Interface Information: 892 _____________________________________________________________ 893 ATM interface:| (1) port identifier |ATM MIB| | 894 physical layer| (2) physical transmission types | (1)*|yes | 895 configuration | (3) operational status |MIB II | * | 896 | (4) administrative status | | ** | 897 | (5) last change status | | | 898 _____________________________________________________________ 899 ATM interface:| (1) active VPI/VCI fields |ATM MIB| | 900 cell layer | (2) maximum number of VPCs/VCCs | (1) |yes | 901 configuration | (3) configured VPCs/VCCs | | ** | 902 | (4) ILMI VPI/VCI values | | | 903 | (5) Neighbor system info | | | 904 | (6) Max. number of VPI/VCI bits | |yes | 905 | (7) ATM Subscribed Address | | | 906 _____________________________________________________________ 907 ATM interface:|(1) received/transmitted cells | | | 908 cell layer |(2) cells with HEC error |MIB II |yes | 909 performance |(3) cell header validation errors| | | 910 _____________________________________________________________ 911 ATM interface:|(1)DS3 PLCP severely errored |ATM MIB| | 912 PLCP & TC | framing seconds | (2)| | 913 layer |(2)DS3 PLCP unavailable seconds | |no | 914 performance |(3)DS3 PLCP alarm state | | | 915 |(4)out of cell delineation events| | | 916 |(5)TC alarm state | | | 917 _____________________________________________________________ 918 VP/VC link: |(1)VPI or VPI/VCI value |ATM MIB| | 919 configuration |(2)VCL or VPL operational status | (3,4)|yes | 920 |(3)VCL/VPL administrative status | |*** | 921 |(4)VCL/VPL last change status | | | 922 |(5)transmit/receive traffic/ | | | 923 | service category parameters | | | 924 |(6)AAL type | | | 925 |(7)transmit/receive AAL5 SDU size| | | 926 |(8)AAL5 encapsulation type | | | 927 |(9)connection topology type | | | 928 |(10)use of call control | | | 929 _____________________________________________________________ 931 draft ATM Management Objects August 15, 1998 933 _____________________________________________________________ 934 VP/VC |(1)cross-connect identifier | | | 935 Cross-connect:|(2)port identifier of one | | | 936 configuration | end | | | 937 |(3)port identifier of the other |ATM MIB| | 938 | end | (5)|no | 939 |(4)VPI or VPI/VCI value | | | 940 | of one end | | | 941 |(5)VPI or VPI/VCI value of | | | 942 | the other end | | | 943 |(6)VC/VP cross-connect | | | 944 | operational status | | | 945 |(7)VC/VP cross-connect | | | 946 | administrative status | | | 947 |(8)VC/VP last change status | | | 948 _____________________________________________________________ 949 VCC AAL5 CPCS |(1)PDUs discarded for CRC errors |ATM MIB| | 950 layer: |(2)PDUs discarded due to | (6) | | 951 performance | reassembly time out | |no | 952 |(3)PDUs discarded due to large | | | 953 | SDUs | | | 954 _____________________________________________________________ 955 AAL5 entity: |(1)received/transmitted PDUs | | | 956 |(2)PDUs discarded due to | | | 957 | protocol errors |MIB II |no | 958 |(3)a set of configuration/state | | | 959 | parameters | | | 960 _____________________________________________________________ 962 *The operational, administrative, and last change status of 963 the ATM interface and the physical transmission type shall be 964 supported by the interface table in MIB II [16][17]. ILMI 965 does not contain the administrative and last change status of 966 the ATM interface. 968 ** The ILMI MIB contains read-only objects for various 969 parameters at the ATM interface level. 971 ***The ILMI MIBs contain local and end-to-end operational 972 status of the VPC/VCC segment. However, it does not contain 973 the VPC/VCC administrative and last change status and the VCC 974 AAL information. 976 draft ATM Management Objects August 15, 1998 978 11. Definitions 980 ATM-MIB DEFINITIONS ::= BEGIN 982 IMPORTS 983 MODULE-IDENTITY, OBJECT-TYPE, 984 experimental, Counter32, Integer32, IpAddress, mib-2 985 FROM SNMPv2-SMI 986 DisplayString, RowStatus, TruthValue 987 FROM SNMPv2-TC 988 MODULE-COMPLIANCE, OBJECT-GROUP 989 FROM SNMPv2-CONF 990 InterfaceIndex, ifIndex 991 FROM IF-MIB 992 AtmAddr, AtmConnKind, AtmConnCastType, 993 AtmServiceCategory, AtmTrafficDescrParamIndex, 994 AtmVpIdentifier, AtmVcIdentifier, 995 AtmVorXAdminStatus, AtmVorXLastChange, 996 AtmVorXOperStatus, atmNoClpNoScr 997 FROM ATM-TC-MIB; 999 atmMIB MODULE-IDENTITY 1000 LAST-UPDATED "9808151200Z" 1001 ORGANIZATION "IETF AToM MIB Working Group" 1002 CONTACT-INFO 1003 " Kaj Tesink 1004 Postal: Bellcore 1005 331 Newman Springs Road 1006 Red Bank, NJ 07701 1007 Tel: 732-758-5254 1008 Fax: 732-758-2269 1009 E-mail: kaj@cc.bellcore.com" 1010 DESCRIPTION 1011 "This is the MIB Module for ATM and AAL5-related 1012 objects for managing ATM interfaces, ATM virtual 1013 links, ATM cross-connects, AAL5 entities, and 1014 and AAL5 connections." 1015 REVISION "9406072245Z" 1016 DESCRIPTION 1017 "The initial revision of this module was published 1018 as RFC 1695." 1019 ::= { experimental 41 } 1021 -- **************************************** 1023 draft ATM Management Objects August 15, 1998 1025 -- * Note to RFC editor * 1026 -- * Replace {experimental 41} with * 1027 -- * { mib-2 37 } when publishing this * 1028 -- * MIB as RFC * 1029 -- **************************************** 1031 atmMIBObjects OBJECT IDENTIFIER ::= {atmMIB 1} 1033 -- {atmMIBObjects 1} has been moved to a separate 1034 -- specification [19]. 1036 draft ATM Management Objects August 15, 1998 1038 -- This ATM MIB Module consists of the following tables: 1039 -- (1) ATM Interface configuration table 1040 -- (2) ATM Interface DS3 PLCP table 1041 -- (3) ATM Interface TC Sublayer table 1042 -- (4) Atm Traffic Descriptor table 1043 -- (5) ATM Interface VPL configuration table 1044 -- (6) ATM Interface VCL configuration table 1045 -- (7) ATM VP Cross Connect table (for PVCs) 1046 -- (8) ATM VC Cross Connect table (for PVCs) 1047 -- (9) ATM Interface AAL5 VCC performance statistics 1048 -- table 1050 draft ATM Management Objects August 15, 1998 1052 -- ATM Interface Configuration Parameters Table 1054 -- This table contains ATM specific 1055 -- configuration information associated with 1056 -- an ATM interface beyond those 1057 -- supported using the ifTable. 1059 atmInterfaceConfTable OBJECT-TYPE 1060 SYNTAX SEQUENCE OF AtmInterfaceConfEntry 1061 MAX-ACCESS not-accessible 1062 STATUS current 1063 DESCRIPTION 1064 "This table contains ATM local interface 1065 configuration parameters, one entry per ATM 1066 interface port." 1067 ::= { atmMIBObjects 2 } 1069 atmInterfaceConfEntry OBJECT-TYPE 1070 SYNTAX AtmInterfaceConfEntry 1071 MAX-ACCESS not-accessible 1072 STATUS current 1073 DESCRIPTION 1074 "This list contains ATM interface configuration 1075 parameters and state variables and is indexed 1076 by ifIndex values of ATM interfaces." 1077 INDEX { ifIndex } 1078 ::= { atmInterfaceConfTable 1} 1080 AtmInterfaceConfEntry ::= SEQUENCE { 1081 atmInterfaceMaxVpcs INTEGER, 1082 atmInterfaceMaxVccs INTEGER, 1083 atmInterfaceConfVpcs INTEGER, 1084 atmInterfaceConfVccs INTEGER, 1085 atmInterfaceMaxActiveVpiBits INTEGER, 1086 atmInterfaceMaxActiveVciBits INTEGER, 1087 atmInterfaceIlmiVpi AtmVpIdentifier, 1088 atmInterfaceIlmiVci AtmVcIdentifier, 1089 atmInterfaceAddressType INTEGER, 1090 atmInterfaceAdminAddress AtmAddr, 1091 atmInterfaceMyNeighborIpAddress IpAddress, 1092 atmInterfaceMyNeighborIfName DisplayString, 1093 atmInterfaceCurrentMaxVpiBits INTEGER, 1095 draft ATM Management Objects August 15, 1998 1097 atmInterfaceCurrentMaxVciBits INTEGER, 1098 atmInterfaceSubscrAddress AtmAddr 1099 } 1101 atmInterfaceMaxVpcs OBJECT-TYPE 1102 SYNTAX INTEGER (0..4096) 1103 MAX-ACCESS read-write 1104 STATUS current 1105 DESCRIPTION 1106 "The maximum number of VPCs (PVPCs and SVPCs) 1107 supported at this ATM interface. At the ATM UNI, 1108 the maximum number of VPCs (PVPCs and SVPCs) 1109 ranges from 0 to 256 only." 1110 ::= { atmInterfaceConfEntry 1} 1112 atmInterfaceMaxVccs OBJECT-TYPE 1113 SYNTAX INTEGER (0..65536) 1114 MAX-ACCESS read-write 1115 STATUS current 1116 DESCRIPTION 1117 "The maximum number of VCCs (PVCCs and SVCCs) 1118 supported at this ATM interface." 1119 ::= { atmInterfaceConfEntry 2} 1121 atmInterfaceConfVpcs OBJECT-TYPE 1122 SYNTAX INTEGER (0..4096) 1123 MAX-ACCESS read-only 1124 STATUS current 1125 DESCRIPTION 1126 "The number of VPCs (PVPC, Soft PVPC and SVPC) 1127 currently in use at this ATM interface. It includes 1128 the number of PVPCs and Soft PVPCs that are configured 1129 at the interface, plus the number of SVPCs 1130 that are currently established at the 1131 interface. 1133 At the ATM UNI, the configured number of 1134 VPCs (PVPCs and SVPCs) can range from 1135 0 to 256 only." 1136 ::= { atmInterfaceConfEntry 3} 1138 atmInterfaceConfVccs OBJECT-TYPE 1139 SYNTAX INTEGER (0..65536) 1140 MAX-ACCESS read-only 1142 draft ATM Management Objects August 15, 1998 1144 STATUS current 1145 DESCRIPTION 1146 "The number of VCCs (PVCC, Soft PVCC and SVCC) 1147 currently in use at this ATM interface. It includes 1148 the number of PVCCs and Soft PVCCs that are configured 1149 at the interface, plus the number of SVCCs 1150 that are currently established at the 1151 interface." 1152 ::= { atmInterfaceConfEntry 4} 1154 atmInterfaceMaxActiveVpiBits OBJECT-TYPE 1155 SYNTAX INTEGER (0..12) 1156 MAX-ACCESS read-write 1157 STATUS current 1158 DESCRIPTION 1159 "The maximum number of active VPI bits 1160 configured for use at the ATM interface. 1161 At the ATM UNI, the maximum number of active 1162 VPI bits configured for use ranges from 1163 0 to 8 only." 1164 ::= { atmInterfaceConfEntry 5} 1166 atmInterfaceMaxActiveVciBits OBJECT-TYPE 1167 SYNTAX INTEGER (0..16) 1168 MAX-ACCESS read-write 1169 STATUS current 1170 DESCRIPTION 1171 "The maximum number of active VCI bits 1172 configured for use at this ATM interface." 1173 ::= { atmInterfaceConfEntry 6} 1175 atmInterfaceIlmiVpi OBJECT-TYPE 1176 SYNTAX AtmVpIdentifier 1177 MAX-ACCESS read-write 1178 STATUS current 1179 DESCRIPTION 1180 "The VPI value of the VCC supporting 1181 the ILMI at this ATM interface. If the values of 1182 atmInterfaceIlmiVpi and atmInterfaceIlmiVci are 1183 both equal to zero then the ILMI is not 1184 supported at this ATM interface." 1185 DEFVAL { 0 } 1186 ::= { atmInterfaceConfEntry 7} 1188 atmInterfaceIlmiVci OBJECT-TYPE 1190 draft ATM Management Objects August 15, 1998 1192 SYNTAX AtmVcIdentifier 1193 MAX-ACCESS read-write 1194 STATUS current 1195 DESCRIPTION 1196 "The VCI value of the VCC supporting 1197 the ILMI at this ATM interface. If the values of 1198 atmInterfaceIlmiVpi and atmInterfaceIlmiVci are 1199 both equal to zero then the ILMI is not 1200 supported at this ATM interface." 1201 DEFVAL { 16 } 1202 ::= { atmInterfaceConfEntry 8} 1204 atmInterfaceAddressType OBJECT-TYPE 1205 SYNTAX INTEGER { 1206 private(1), 1207 nsapE164(2), 1208 nativeE164(3), 1209 other(4) 1210 } 1211 MAX-ACCESS read-only 1212 STATUS deprecated 1213 DESCRIPTION 1214 "The type of primary ATM address configured 1215 for use at this ATM interface." 1216 ::= { atmInterfaceConfEntry 9 } 1218 -- The atmInterfaceAdminAddress object has been replaced by 1219 -- atmInterfaceSubscrAddress. 1221 atmInterfaceAdminAddress OBJECT-TYPE 1222 SYNTAX AtmAddr 1223 MAX-ACCESS read-only 1224 STATUS deprecated 1225 DESCRIPTION 1226 "The primary address assigned for administrative purposes, 1227 for example, an address associated with the 1228 service provider side of a public network UNI 1229 (thus, the value of this address corresponds 1230 with the value of ifPhysAddress at the host side). 1231 If this interface has no assigned administrative 1232 address, or when the address used for 1233 administrative purposes is the same as that used 1234 for ifPhysAddress, then this is an octet string of 1235 zero length." 1236 ::= { atmInterfaceConfEntry 10 } 1238 draft ATM Management Objects August 15, 1998 1240 atmInterfaceMyNeighborIpAddress OBJECT-TYPE 1241 SYNTAX IpAddress 1242 MAX-ACCESS read-write 1243 STATUS current 1244 DESCRIPTION 1245 "The IP address of the neighbor system connected to 1246 the far end of this interface, to which a Network 1247 Management Station can send SNMP messages, as IP 1248 datagrams sent to UDP port 161, in order to access 1249 network management information concerning the 1250 operation of that system. Note that the value 1251 of this object may be obtained in different ways, 1252 e.g., by manual configuration, or through ILMI 1253 interaction with the neighbor system." 1254 ::= { atmInterfaceConfEntry 11 } 1256 atmInterfaceMyNeighborIfName OBJECT-TYPE 1257 SYNTAX DisplayString 1258 MAX-ACCESS read-write 1259 STATUS current 1260 DESCRIPTION 1261 "The textual name of the interface on the neighbor 1262 system on the far end of this interface, and to 1263 which this interface connects. If the neighbor 1264 system is manageable through SNMP and supports 1265 the object ifName, the value of this object must 1266 be identical with that of ifName for the ifEntry 1267 of the lowest level physical interface 1268 for this port. If this interface does not have a 1269 textual name, the value of this object is a zero 1270 length string. Note that the value of this object 1271 may be obtained in different ways, e.g., by manual 1272 configuration, or through ILMI interaction with 1273 the neighbor system." 1274 ::= { atmInterfaceConfEntry 12 } 1276 atmInterfaceCurrentMaxVpiBits OBJECT-TYPE 1277 SYNTAX INTEGER (0..12) 1278 MAX-ACCESS read-only 1279 STATUS current 1280 DESCRIPTION 1281 "The maximum number of VPI Bits that may 1282 currently be used at this ATM interface. 1283 The value is the minimum of 1284 atmInterfaceMaxActiveVpiBits, and the 1286 draft ATM Management Objects August 15, 1998 1288 atmInterfaceMaxActiveVpiBits of the interface's 1289 UNI/NNI peer. 1291 If the interface does not negotiate with 1292 its peer to determine the number of VPI Bits 1293 that can be used on the interface, then the 1294 value of this object must equal 1295 atmInterfaceMaxActiveVpiBits." 1296 ::= { atmInterfaceConfEntry 13 } 1298 atmInterfaceCurrentMaxVciBits OBJECT-TYPE 1299 SYNTAX INTEGER (0..16) 1300 MAX-ACCESS read-only 1301 STATUS current 1302 DESCRIPTION 1303 "The maximum number of VCI Bits that may 1304 currently be used at this ATM interface. 1305 The value is the minimum of 1306 atmInterfaceMaxActiveVciBits, and the 1307 atmInterfaceMaxActiveVciBits of the interface's 1308 UNI/NNI peer. 1310 If the interface does not negotiate with 1311 its peer to determine the number of VCI Bits 1312 that can be used on the interface, then the 1313 value of this object must equal 1314 atmInterfaceMaxActiveVciBits." 1315 ::= { atmInterfaceConfEntry 14 } 1317 atmInterfaceSubscrAddress OBJECT-TYPE 1318 SYNTAX AtmAddr 1319 MAX-ACCESS read-write 1320 STATUS current 1321 DESCRIPTION 1322 "The identifier assigned by a service provider 1323 to the network side of a public network UNI. 1324 If this interface has no assigned service provider 1325 address, or for other interfaces this is an octet string 1326 of zero length." 1327 ::= { atmInterfaceConfEntry 15 } 1329 draft ATM Management Objects August 15, 1998 1331 -- The ATM Interface DS3 PLCP Table 1333 -- This table contains the DS3 PLCP configuration and 1334 -- state parameters of those ATM interfaces 1335 -- which use DS3 PLCP for carrying ATM cells over DS3. 1337 atmInterfaceDs3PlcpTable OBJECT-TYPE 1338 SYNTAX SEQUENCE OF AtmInterfaceDs3PlcpEntry 1339 MAX-ACCESS not-accessible 1340 STATUS current 1341 DESCRIPTION 1342 "This table contains ATM interface DS3 PLCP 1343 parameters and state variables, one entry per 1344 ATM interface port." 1345 ::= { atmMIBObjects 3} 1347 atmInterfaceDs3PlcpEntry OBJECT-TYPE 1348 SYNTAX AtmInterfaceDs3PlcpEntry 1349 MAX-ACCESS not-accessible 1350 STATUS current 1351 DESCRIPTION 1352 "This list contains DS3 PLCP parameters and 1353 state variables at the ATM interface and is 1354 indexed by the ifIndex value of the ATM interface." 1355 INDEX { ifIndex } 1356 ::= { atmInterfaceDs3PlcpTable 1} 1358 AtmInterfaceDs3PlcpEntry ::= SEQUENCE { 1359 atmInterfaceDs3PlcpSEFSs Counter32, 1360 atmInterfaceDs3PlcpAlarmState INTEGER, 1361 atmInterfaceDs3PlcpUASs Counter32 1362 } 1364 atmInterfaceDs3PlcpSEFSs OBJECT-TYPE 1365 SYNTAX Counter32 1366 MAX-ACCESS read-only 1367 STATUS current 1368 DESCRIPTION 1369 "The number of DS3 PLCP Severely Errored Framing 1370 Seconds (SEFS). Each SEFS represents a 1371 one-second interval which contains 1372 one or more SEF events." 1373 ::= { atmInterfaceDs3PlcpEntry 1} 1375 draft ATM Management Objects August 15, 1998 1377 atmInterfaceDs3PlcpAlarmState OBJECT-TYPE 1378 SYNTAX INTEGER { 1379 noAlarm(1), 1380 receivedFarEndAlarm(2), 1381 incomingLOF(3) 1382 } 1383 MAX-ACCESS read-only 1384 STATUS current 1385 DESCRIPTION 1386 "This variable indicates if there is an 1387 alarm present for the DS3 PLCP. The value 1388 receivedFarEndAlarm means that the DS3 PLCP 1389 has received an incoming Yellow 1390 Signal, the value incomingLOF means that 1391 the DS3 PLCP has declared a loss of frame (LOF) 1392 failure condition, and the value noAlarm 1393 means that there are no alarms present. 1394 Transition from the failure to the no alarm state 1395 occurs when no defects (e.g., LOF) are received 1396 for more than 10 seconds." 1397 ::= { atmInterfaceDs3PlcpEntry 2} 1399 atmInterfaceDs3PlcpUASs OBJECT-TYPE 1400 SYNTAX Counter32 1401 MAX-ACCESS read-only 1402 STATUS current 1403 DESCRIPTION 1404 "The counter associated with the number of 1405 Unavailable Seconds encountered by the PLCP." 1406 ::= { atmInterfaceDs3PlcpEntry 3} 1408 draft ATM Management Objects August 15, 1998 1410 -- The ATM Interface TC Sublayer Table 1412 -- This table contains TC sublayer configuration and 1413 -- state parameters of those ATM interfaces 1414 -- which use TC sublayer for carrying ATM cells over 1415 -- SONET/SDH or DS3. 1417 atmInterfaceTCTable OBJECT-TYPE 1418 SYNTAX SEQUENCE OF AtmInterfaceTCEntry 1419 MAX-ACCESS not-accessible 1420 STATUS current 1421 DESCRIPTION 1422 "This table contains ATM interface TC 1423 Sublayer parameters and state variables, 1424 one entry per ATM interface port." 1425 ::= { atmMIBObjects 4} 1427 atmInterfaceTCEntry OBJECT-TYPE 1428 SYNTAX AtmInterfaceTCEntry 1429 MAX-ACCESS not-accessible 1430 STATUS current 1431 DESCRIPTION 1432 "This list contains TC Sublayer parameters 1433 and state variables at the ATM interface and is 1434 indexed by the ifIndex value of the ATM interface." 1435 INDEX {ifIndex } 1436 ::= { atmInterfaceTCTable 1} 1438 AtmInterfaceTCEntry ::= SEQUENCE { 1439 atmInterfaceOCDEvents Counter32, 1440 atmInterfaceTCAlarmState INTEGER 1441 } 1443 atmInterfaceOCDEvents OBJECT-TYPE 1444 SYNTAX Counter32 1445 MAX-ACCESS read-only 1446 STATUS current 1447 DESCRIPTION 1448 "The number of times the Out of Cell 1449 Delineation (OCD) events occur. If seven 1450 consecutive ATM cells have Header Error 1451 Control (HEC) violations, an OCD event occurs. 1452 A high number of OCD events may indicate a 1453 problem with the TC Sublayer." 1455 draft ATM Management Objects August 15, 1998 1457 ::= { atmInterfaceTCEntry 1} 1459 atmInterfaceTCAlarmState OBJECT-TYPE 1460 SYNTAX INTEGER { 1461 noAlarm(1), 1462 lcdFailure(2) 1463 } 1464 MAX-ACCESS read-only 1465 STATUS current 1466 DESCRIPTION 1467 "This variable indicates if there is an 1468 alarm present for the TC Sublayer. The value 1469 lcdFailure(2) indicates that the TC Sublayer 1470 is currently in the Loss of Cell Delineation 1471 (LCD) defect maintenance state. The value 1472 noAlarm(1) indicates that the TC Sublayer 1473 is currently not in the LCD defect 1474 maintenance state." 1475 ::= { atmInterfaceTCEntry 2} 1477 draft ATM Management Objects August 15, 1998 1479 -- ATM Traffic Descriptor Parameter Table 1481 -- This table contains a set of self-consistent 1482 -- ATM traffic parameters including the 1483 -- ATM traffic service category. 1485 -- The ATM virtual link tables (i.e., VPL and VCL tables) 1486 -- will use this ATM Traffic Descriptor table 1487 -- to assign traffic parameters and service category 1488 -- to the receive and transmit directions of 1489 -- the ATM virtual links (i.e., VPLs and VCLs). 1490 -- The ATM VPL or VCL table will indicate a row 1491 -- in the atmTrafficDescrParamTable 1492 -- using its atmTrafficDescrParamIndex value. 1493 -- The management application can then compare a set of 1494 -- ATM traffic parameters with a single value. 1496 -- If no suitable row(s) in the atmTrafficDescrParamTable 1497 -- exists, the manager must create a new row(s) in this 1498 -- table. If such a row is created, agent checks the 1499 -- sanity of that set of ATM traffic parameter values. 1501 -- The manager may use atmTrafficDescrParamIndexNext 1502 -- in order to obtain a free atmTrafficDescrParamIndex 1503 -- value. 1505 -- When creating a new row, the parameter values 1506 -- will be checked for self-consistency. 1507 -- Predefined/template rows may be supported. 1509 -- A row in the atmTrafficDescrParamTable is deleted 1510 -- by setting the atmTrafficDescrRowStatus to destroy(6). 1511 -- The agent will check whether this row is still in use 1512 -- by any entry of the atmVplTable or atmVclTable. 1513 -- The agent denies the request if the row is still in 1514 -- use. 1516 -- The ATM Traffic Descriptor Parameter Table 1518 atmTrafficDescrParamTable OBJECT-TYPE 1519 SYNTAX SEQUENCE OF AtmTrafficDescrParamEntry 1520 MAX-ACCESS not-accessible 1521 STATUS current 1522 DESCRIPTION 1524 draft ATM Management Objects August 15, 1998 1526 "This table contains information on ATM traffic 1527 descriptor type and the associated parameters." 1528 ::= { atmMIBObjects 5} 1530 atmTrafficDescrParamEntry OBJECT-TYPE 1531 SYNTAX AtmTrafficDescrParamEntry 1532 MAX-ACCESS not-accessible 1533 STATUS current 1534 DESCRIPTION 1535 "This list contains ATM traffic descriptor 1536 type and the associated parameters." 1537 INDEX {atmTrafficDescrParamIndex} 1538 ::= { atmTrafficDescrParamTable 1} 1540 AtmTrafficDescrParamEntry ::= SEQUENCE { 1541 atmTrafficDescrParamIndex AtmTrafficDescrParamIndex, 1542 atmTrafficDescrType OBJECT IDENTIFIER, 1543 atmTrafficDescrParam1 Integer32, 1544 atmTrafficDescrParam2 Integer32, 1545 atmTrafficDescrParam3 Integer32, 1546 atmTrafficDescrParam4 Integer32, 1547 atmTrafficDescrParam5 Integer32, 1548 atmTrafficQoSClass INTEGER, 1549 atmTrafficDescrRowStatus RowStatus, 1550 atmServiceCategory AtmServiceCategory, 1551 atmTrafficFrameDiscard TruthValue 1552 } 1554 atmTrafficDescrParamIndex OBJECT-TYPE 1555 SYNTAX AtmTrafficDescrParamIndex 1556 MAX-ACCESS not-accessible 1557 STATUS current 1558 DESCRIPTION 1559 "This object is used by the virtual link 1560 table (i.e., VPL or VCL table) 1561 to identify the row of this table. 1562 When creating a new row in the table 1563 the value of this index may be obtained 1564 by retrieving the value of 1565 atmTrafficDescrParamIndexNext." 1566 ::= { atmTrafficDescrParamEntry 1} 1568 atmTrafficDescrType OBJECT-TYPE 1569 SYNTAX OBJECT IDENTIFIER 1570 MAX-ACCESS read-create 1572 draft ATM Management Objects August 15, 1998 1574 STATUS current 1575 DESCRIPTION 1576 "The value of this object identifies the type 1577 of ATM traffic descriptor. 1578 The type may indicate no traffic descriptor or 1579 traffic descriptor with one or more parameters. 1580 These parameters are specified as a parameter 1581 vector, in the corresponding instances of the 1582 objects: 1583 atmTrafficDescrParam1 1584 atmTrafficDescrParam2 1585 atmTrafficDescrParam3 1586 atmTrafficDescrParam4 1587 atmTrafficDescrParam5." 1588 DEFVAL { atmNoClpNoScr } 1589 ::= { atmTrafficDescrParamEntry 2} 1591 atmTrafficDescrParam1 OBJECT-TYPE 1592 SYNTAX Integer32 1593 MAX-ACCESS read-create 1594 STATUS current 1595 DESCRIPTION 1596 "The first parameter of the ATM traffic descriptor 1597 used according to the value of 1598 atmTrafficDescrType." 1599 DEFVAL { 0 } 1600 ::= { atmTrafficDescrParamEntry 3} 1602 atmTrafficDescrParam2 OBJECT-TYPE 1603 SYNTAX Integer32 1604 MAX-ACCESS read-create 1605 STATUS current 1606 DESCRIPTION 1607 "The second parameter of the ATM traffic descriptor 1608 used according to the value of 1609 atmTrafficDescrType." 1610 DEFVAL { 0 } 1611 ::= { atmTrafficDescrParamEntry 4} 1613 atmTrafficDescrParam3 OBJECT-TYPE 1614 SYNTAX Integer32 1615 MAX-ACCESS read-create 1616 STATUS current 1617 DESCRIPTION 1618 "The third parameter of the ATM traffic descriptor 1620 draft ATM Management Objects August 15, 1998 1622 used according to the value of 1623 atmTrafficDescrType." 1624 DEFVAL { 0 } 1625 ::= { atmTrafficDescrParamEntry 5} 1627 atmTrafficDescrParam4 OBJECT-TYPE 1628 SYNTAX Integer32 1629 MAX-ACCESS read-create 1630 STATUS current 1631 DESCRIPTION 1632 "The fourth parameter of the ATM traffic descriptor 1633 used according to the value of 1634 atmTrafficDescrType." 1635 DEFVAL { 0 } 1636 ::= { atmTrafficDescrParamEntry 6} 1638 atmTrafficDescrParam5 OBJECT-TYPE 1639 SYNTAX Integer32 1640 MAX-ACCESS read-create 1641 STATUS current 1642 DESCRIPTION 1643 "The fifth parameter of the ATM traffic descriptor 1644 used according to the value of 1645 atmTrafficDescrType." 1646 DEFVAL { 0 } 1647 ::= { atmTrafficDescrParamEntry 7} 1649 atmTrafficQoSClass OBJECT-TYPE 1650 SYNTAX INTEGER (0..255) 1651 MAX-ACCESS read-create 1652 STATUS deprecated 1653 DESCRIPTION 1654 "The value of this object identifies the QoS Class. 1655 Four Service classes have been 1656 specified in the ATM Forum UNI Specification: 1657 Service Class A: Constant bit rate video and 1658 Circuit emulation 1659 Service Class B: Variable bit rate video/audio 1660 Service Class C: Connection-oriented data 1661 Service Class D: Connectionless data 1662 Four QoS classes numbered 1, 2, 3, and 4 have 1663 been specified with the aim to support service 1664 classes A, B, C, and D respectively. 1665 An unspecified QoS Class numbered `0' is used 1666 for best effort traffic." 1668 draft ATM Management Objects August 15, 1998 1670 DEFVAL { 0 } 1671 ::= { atmTrafficDescrParamEntry 8} 1673 atmTrafficDescrRowStatus OBJECT-TYPE 1674 SYNTAX RowStatus 1675 MAX-ACCESS read-create 1676 STATUS current 1677 DESCRIPTION 1678 "This object is used to create 1679 a new row or modify or delete an 1680 existing row in this table." 1681 DEFVAL { active } 1682 ::= {atmTrafficDescrParamEntry 9} 1684 atmServiceCategory OBJECT-TYPE 1685 SYNTAX AtmServiceCategory 1686 MAX-ACCESS read-create 1687 STATUS current 1688 DESCRIPTION 1689 "The ATM service category." 1690 DEFVAL { ubr } 1691 ::= { atmTrafficDescrParamEntry 10} 1693 atmTrafficFrameDiscard OBJECT-TYPE 1694 SYNTAX TruthValue 1695 MAX-ACCESS read-create 1696 STATUS current 1697 DESCRIPTION 1698 "If set to 'true', this object indicates that the network 1699 is requested to treat data for this connection, in the 1700 given direction, as frames (e.g. AAL5 CPCS_PDU's) rather 1701 than as individual cells. While the precise 1702 implementation is network-specific, this treatment may 1703 for example involve discarding entire frames during 1704 congestion, rather than a few cells from many frames." 1705 DEFVAL { true } 1706 ::= { atmTrafficDescrParamEntry 11 } 1708 draft ATM Management Objects August 15, 1998 1710 -- ATM Interface Virtual Path Link (VPL) Table 1712 -- This table contains configuration and state 1713 -- information of a bi-directional Virtual Path Link 1714 -- (VPL) 1716 -- This table can be used to create, delete or modify 1717 -- a VPL that is terminated in an ATM host or switch. 1718 -- This table can also be used to create, delete or 1719 -- modify a VPL which is cross-connected to another 1720 -- VPL. 1722 -- In the example below, the traffic flows on the receive 1723 -- and transmit directions of the VPLs are characterized 1724 -- by atmVplReceiveTrafficDescrIndex and 1725 -- atmVplTransmitTrafficDescrIndex respectively. 1726 -- The cross-connected VPLs are identified by 1727 -- atmVplCrossConnectIdentifier. 1729 -- ________________________________ 1730 -- | | 1731 -- VPL | ATM Host, Switch, or Network | VPL 1732 -- receive | | receive 1733 -- ========> X X <======= 1734 -- <======== X X ========> 1735 -- transmit | | transmit 1736 -- |______________________________| 1738 -- The ATM Interface VPL Table 1740 atmVplTable OBJECT-TYPE 1741 SYNTAX SEQUENCE OF AtmVplEntry 1742 MAX-ACCESS not-accessible 1743 STATUS current 1744 DESCRIPTION 1745 "The Virtual Path Link (VPL) table. A 1746 bi-directional VPL is modeled as one entry 1747 in this table. This table can be used for 1748 PVCs, SVCs and Soft PVCs. 1749 Entries are not present in this table for 1751 draft ATM Management Objects August 15, 1998 1753 the VPIs used by entries in the atmVclTable." 1754 ::= { atmMIBObjects 6} 1756 atmVplEntry OBJECT-TYPE 1757 SYNTAX AtmVplEntry 1758 MAX-ACCESS not-accessible 1759 STATUS current 1760 DESCRIPTION 1761 "An entry in the VPL table. This entry is 1762 used to model a bi-directional VPL. 1763 To create a VPL at an ATM interface, 1764 either of the following procedures are used: 1766 Negotiated VPL establishment 1768 (1) The management application creates 1769 a VPL entry in the atmVplTable 1770 by setting atmVplRowStatus to createAndWait(5). 1771 This may fail for the following reasons: 1772 - The selected VPI value is unavailable, 1773 - The selected VPI value is in use. 1774 Otherwise, the agent creates a row and 1775 reserves the VPI value on that port. 1777 (2) The manager selects an existing row(s) in the 1778 atmTrafficDescrParamTable, 1779 thereby, selecting a set of self-consistent 1780 ATM traffic parameters and the service category 1781 for receive and transmit directions of the VPL. 1783 (2a) If no suitable row(s) in the 1784 atmTrafficDescrParamTable exists, 1785 the manager must create a new row(s) 1786 in that table. 1788 (2b) The manager characterizes the VPL's traffic 1789 parameters through setting the 1790 atmVplReceiveTrafficDescrIndex and the 1791 atmVplTransmitTrafficDescrIndex values 1792 in the VPL table, which point to the rows 1793 containing desired ATM traffic parameter values 1794 in the atmTrafficDescrParamTable. The agent 1795 will check the availability of resources and 1796 may refuse the request. 1797 If the transmit and receive service categories 1799 draft ATM Management Objects August 15, 1998 1801 are inconsistent, the agent should refuse the 1802 request. 1804 (3) The manager activates the VPL by setting the 1805 the atmVplRowStatus to active(1). 1806 If this set is successful, the agent has 1807 reserved the resources to satisfy the requested 1808 traffic parameter values and the service category 1809 for that VPL. 1811 (4) If the VPL terminates a VPC in the ATM host 1812 or switch, the manager turns on the 1813 atmVplAdminStatus to up(1) to turn the VPL 1814 traffic flow on. Otherwise, the 1815 atmVpCrossConnectTable must be used 1816 to cross-connect the VPL to another VPL(s) 1817 in an ATM switch or network. 1819 One-Shot VPL Establishment 1821 A VPL may also be established in one step by a 1822 set-request with all necessary VPL parameter 1823 values and atmVplRowStatus set to createAndGo(4). 1825 In contrast to the negotiated VPL establishment 1826 which allows for detailed error checking 1827 (i.e., set errors are explicitly linked to 1828 particular resource acquisition failures), 1829 the one-shot VPL establishment 1830 performs the setup on one operation but 1831 does not have the advantage of step-wise 1832 error checking. 1834 VPL Retirement 1836 A VPL is released by setting atmVplRowStatus to 1837 destroy(6), and the agent may release all 1838 associated resources." 1839 INDEX {ifIndex, atmVplVpi } 1840 ::= { atmVplTable 1} 1842 AtmVplEntry ::= SEQUENCE { 1843 atmVplVpi AtmVpIdentifier, 1844 atmVplAdminStatus AtmVorXAdminStatus, 1845 atmVplOperStatus AtmVorXOperStatus, 1847 draft ATM Management Objects August 15, 1998 1849 atmVplLastChange AtmVorXLastChange, 1850 atmVplReceiveTrafficDescrIndex 1851 AtmTrafficDescrParamIndex, 1852 atmVplTransmitTrafficDescrIndex 1853 AtmTrafficDescrParamIndex, 1854 atmVplCrossConnectIdentifier INTEGER, 1855 atmVplRowStatus RowStatus, 1856 atmVplCastType AtmConnCastType, 1857 atmVplConnKind AtmConnKind 1858 } 1860 atmVplVpi OBJECT-TYPE 1861 SYNTAX AtmVpIdentifier 1862 MAX-ACCESS not-accessible 1863 STATUS current 1864 DESCRIPTION 1865 "The VPI value of the VPL." 1866 ::= { atmVplEntry 1} 1868 atmVplAdminStatus OBJECT-TYPE 1869 SYNTAX AtmVorXAdminStatus 1870 MAX-ACCESS read-create 1871 STATUS current 1872 DESCRIPTION 1873 "This object is instanciated only for a VPL 1874 which terminates a VPC (i.e., one which is 1875 NOT cross-connected to other VPLs). 1876 Its value specifies the desired 1877 administrative state of the VPL." 1878 DEFVAL { down } 1879 ::= { atmVplEntry 2} 1881 atmVplOperStatus OBJECT-TYPE 1882 SYNTAX AtmVorXOperStatus 1883 MAX-ACCESS read-only 1884 STATUS current 1885 DESCRIPTION 1886 "The current operational status of the VPL." 1887 ::= { atmVplEntry 3} 1889 atmVplLastChange OBJECT-TYPE 1890 SYNTAX AtmVorXLastChange 1891 MAX-ACCESS read-only 1892 STATUS current 1894 draft ATM Management Objects August 15, 1998 1896 DESCRIPTION 1897 "The value of sysUpTime at the time this 1898 VPL entered its current operational state." 1899 ::= { atmVplEntry 4 } 1901 atmVplReceiveTrafficDescrIndex OBJECT-TYPE 1902 SYNTAX AtmTrafficDescrParamIndex 1903 MAX-ACCESS read-create 1904 STATUS current 1905 DESCRIPTION 1906 "The value of this object identifies the row 1907 in the atmTrafficDescrParamTable which 1908 applies to the receive direction of the VPL." 1909 DEFVAL { 0 } 1910 ::= { atmVplEntry 5} 1912 atmVplTransmitTrafficDescrIndex OBJECT-TYPE 1913 SYNTAX AtmTrafficDescrParamIndex 1914 MAX-ACCESS read-create 1915 STATUS current 1916 DESCRIPTION 1917 "The value of this object identifies the row 1918 in the atmTrafficDescrParamTable which 1919 applies to the transmit direction of the VPL." 1920 DEFVAL { 0 } 1921 ::= { atmVplEntry 6} 1923 atmVplCrossConnectIdentifier OBJECT-TYPE 1924 SYNTAX INTEGER (0..2147483647) 1925 MAX-ACCESS read-only 1926 STATUS current 1927 DESCRIPTION 1928 "This object is instantiated only for a VPL 1929 which is cross-connected to other VPLs 1930 that belong to the same VPC. All such 1931 associated VPLs have the same value of this 1932 object, and all their cross-connections are 1933 identified either by entries that are indexed 1934 by the same value of atmVpCrossConnectIndex in 1935 the atmVpCrossConnectTable of this MIB module or by 1936 the same value of the cross-connect index in 1937 the cross-connect table for SVCs and Soft PVCs 1938 (defined in a separate MIB module). 1939 At no time should entries in these respective 1940 cross-connect tables exist simultaneously 1942 draft ATM Management Objects August 15, 1998 1944 with the same cross-connect index value. 1946 The value of this object is initialized by the 1947 agent after the associated entries in the 1948 atmVpCrossConnectTable have been created." 1949 ::= {atmVplEntry 7} 1951 atmVplRowStatus OBJECT-TYPE 1952 SYNTAX RowStatus 1953 MAX-ACCESS read-create 1954 STATUS current 1955 DESCRIPTION 1956 "This object is used to create, delete 1957 or modify a row in this table. 1958 To create a new VCL, this object is 1959 initially set to 'createAndWait' or 1960 'createAndGo'. This object should not be 1961 set to 'active' unless the following columnar 1962 objects have been set to their desired value 1963 in this row: 1964 atmVplReceiveTrafficDescrIndex and 1965 atmVplTransmitTrafficDescrIndex." 1966 DEFVAL { active } 1967 ::= {atmVplEntry 8} 1969 atmVplCastType OBJECT-TYPE 1970 SYNTAX AtmConnCastType 1971 MAX-ACCESS read-create 1972 STATUS current 1973 DESCRIPTION 1974 "The connection topology type." 1975 DEFVAL { p2p } 1976 ::= {atmVplEntry 9} 1978 atmVplConnKind OBJECT-TYPE 1979 SYNTAX AtmConnKind 1980 MAX-ACCESS read-create 1981 STATUS current 1982 DESCRIPTION 1983 "The use of call control." 1984 DEFVAL { pvc } 1985 ::= {atmVplEntry 10} 1987 draft ATM Management Objects August 15, 1998 1989 -- ATM Interface Virtual Channel Link (VCL) Table 1991 -- This table contains configuration and state 1992 -- information of a bi-directional Virtual Channel 1993 -- Link (VCL) at an ATM interface. 1995 -- This table can be used to create, delete or modify 1996 -- a VCL that is terminated in an ATM host or switch. 1997 -- This table can also be 1998 -- used to create, delete or modify a VCL that is 1999 -- cross-connected to another VCL. 2001 -- The ATM Interface VCL Table 2003 atmVclTable OBJECT-TYPE 2004 SYNTAX SEQUENCE OF AtmVclEntry 2005 MAX-ACCESS not-accessible 2006 STATUS current 2007 DESCRIPTION 2008 "The Virtual Channel Link (VCL) table. A 2009 bi-directional VCL is modeled as one entry 2010 in this table. This table can be used for 2011 PVCs, SVCs and Soft PVCs." 2012 ::= { atmMIBObjects 7} 2014 atmVclEntry OBJECT-TYPE 2015 SYNTAX AtmVclEntry 2016 MAX-ACCESS not-accessible 2017 STATUS current 2018 DESCRIPTION 2019 "An entry in the VCL table. This entry is 2020 used to model a bi-directional VCL. 2021 To create a VCL at an ATM interface, 2022 either of the following procedures are used: 2024 Negotiated VCL establishment 2026 (1) The management application creates 2027 a VCL entry in the atmVclTable 2028 by setting atmVclRowStatus to createAndWait(5). 2029 This may fail for the following reasons: 2030 - The selected VPI/VCI values are unavailable, 2031 - The selected VPI/VCI values are in use. 2033 draft ATM Management Objects August 15, 1998 2035 Otherwise, the agent creates a row and 2036 reserves the VPI/VCI values on that port. 2038 (2) The manager selects an existing row(s) in the 2039 atmTrafficDescrParamTable, 2040 thereby, selecting a set of self-consistent 2041 ATM traffic parameters and the service category 2042 for receive and transmit directions of the VCL. 2044 (2a) If no suitable row(s) in the 2045 atmTrafficDescrParamTable exists, 2046 the manager must create a new row(s) 2047 in that table. 2049 (2b) The manager characterizes the VCL's traffic 2050 parameters through setting the 2051 atmVclReceiveTrafficDescrIndex and the 2052 atmVclTransmitTrafficDescrIndex values 2053 in the VCL table, which point to the rows 2054 containing desired ATM traffic parameter values 2055 in the atmTrafficDescrParamTable. The agent 2056 will check the availability of resources and 2057 may refuse the request. 2058 If the transmit and receive service categories 2059 are inconsistent, the agent should refuse the 2060 request. 2062 (3) The manager activates the VCL by setting the 2063 the atmVclRowStatus to active(1) (for 2064 requirements on this activation see the 2065 description of atmVclRowStatus). 2066 If this set is successful, the agent has 2067 reserved the resources to satisfy the requested 2068 traffic parameter values and the service category 2069 for that VCL. 2070 (4) If the VCL terminates a VCC in the ATM host 2071 or switch, the manager turns on the 2072 atmVclAdminStatus to up(1) to turn the VCL 2073 traffic flow on. Otherwise, the 2074 atmVcCrossConnectTable must be used 2075 to cross-connect the VCL to another VCL(s) 2076 in an ATM switch or network. 2078 One-Shot VCL Establishment 2080 draft ATM Management Objects August 15, 1998 2082 A VCL may also be established in one step by a 2083 set-request with all necessary VCL parameter 2084 values and atmVclRowStatus set to createAndGo(4). 2086 In contrast to the negotiated VCL establishment 2087 which allows for detailed error checking 2088 (i.e., set errors are explicitly linked to 2089 particular resource acquisition failures), 2090 the one-shot VCL establishment 2091 performs the setup on one operation but 2092 does not have the advantage of step-wise 2093 error checking. 2095 VCL Retirement 2097 A VCL is released by setting atmVclRowStatus to 2098 destroy(6), and the agent may release all 2099 associated resources." 2100 INDEX {ifIndex, atmVclVpi, atmVclVci } 2101 ::= { atmVclTable 1} 2103 AtmVclEntry ::= SEQUENCE { 2104 atmVclVpi AtmVpIdentifier, 2105 atmVclVci AtmVcIdentifier, 2106 atmVclAdminStatus AtmVorXAdminStatus, 2107 atmVclOperStatus AtmVorXOperStatus, 2108 atmVclLastChange AtmVorXLastChange, 2109 atmVclReceiveTrafficDescrIndex 2110 AtmTrafficDescrParamIndex, 2111 atmVclTransmitTrafficDescrIndex 2112 AtmTrafficDescrParamIndex, 2113 atmVccAalType INTEGER, 2114 atmVccAal5CpcsTransmitSduSize INTEGER, 2115 atmVccAal5CpcsReceiveSduSize INTEGER, 2116 atmVccAal5EncapsType INTEGER, 2117 atmVclCrossConnectIdentifier INTEGER, 2118 atmVclRowStatus RowStatus, 2119 atmVclCastType AtmConnCastType, 2120 atmVclConnKind AtmConnKind 2121 } 2123 atmVclVpi OBJECT-TYPE 2124 SYNTAX AtmVpIdentifier 2125 MAX-ACCESS not-accessible 2126 STATUS current 2128 draft ATM Management Objects August 15, 1998 2130 DESCRIPTION 2131 "The VPI value of the VCL." 2132 ::= { atmVclEntry 1} 2134 atmVclVci OBJECT-TYPE 2135 SYNTAX AtmVcIdentifier 2136 MAX-ACCESS not-accessible 2137 STATUS current 2138 DESCRIPTION 2139 "The VCI value of the VCL." 2140 ::= { atmVclEntry 2} 2142 atmVclAdminStatus OBJECT-TYPE 2143 SYNTAX AtmVorXAdminStatus 2144 MAX-ACCESS read-create 2145 STATUS current 2146 DESCRIPTION 2147 "This object is instanciated only for a VCL which 2148 terminates a VCC (i.e., one which is NOT 2149 cross-connected to other VCLs). Its value 2150 specifies the desired administrative state of 2151 the VCL." 2152 DEFVAL { down } 2153 ::= { atmVclEntry 3} 2155 atmVclOperStatus OBJECT-TYPE 2156 SYNTAX AtmVorXOperStatus 2157 MAX-ACCESS read-only 2158 STATUS current 2159 DESCRIPTION 2160 "The current operational status of the VCL." 2161 ::= { atmVclEntry 4} 2163 atmVclLastChange OBJECT-TYPE 2164 SYNTAX AtmVorXLastChange 2165 MAX-ACCESS read-only 2166 STATUS current 2167 DESCRIPTION 2168 "The value of sysUpTime at the time this VCL 2169 entered its current operational state." 2170 ::= { atmVclEntry 5 } 2172 atmVclReceiveTrafficDescrIndex OBJECT-TYPE 2173 SYNTAX AtmTrafficDescrParamIndex 2174 MAX-ACCESS read-create 2176 draft ATM Management Objects August 15, 1998 2178 STATUS current 2179 DESCRIPTION 2180 "The value of this object identifies the row 2181 in the ATM Traffic Descriptor Table which 2182 applies to the receive direction of this VCL." 2183 DEFVAL { 0 } 2184 ::= { atmVclEntry 6} 2186 atmVclTransmitTrafficDescrIndex OBJECT-TYPE 2187 SYNTAX AtmTrafficDescrParamIndex 2188 MAX-ACCESS read-create 2189 STATUS current 2190 DESCRIPTION 2191 "The value of this object identifies the row 2192 of the ATM Traffic Descriptor Table which applies 2193 to the transmit direction of this VCL." 2194 DEFVAL { 0 } 2195 ::= { atmVclEntry 7} 2197 atmVccAalType OBJECT-TYPE 2198 SYNTAX INTEGER { 2199 aal1(1), 2200 aal34(2), 2201 aal5(3), 2202 other(4), 2203 unknown(5), 2204 aal2(6) 2205 } 2206 MAX-ACCESS read-create 2207 STATUS current 2208 DESCRIPTION 2209 "An instance of this object only exists when the 2210 local VCL end-point is also the VCC end-point, 2211 and AAL is in use. 2212 The type of AAL used on this VCC. 2213 The AAL type includes AAL1, AAL2, AAL3/4, 2214 and AAL5. The other(4) may be user-defined 2215 AAL type. The unknown type indicates that 2216 the AAL type cannot be determined." 2217 DEFVAL { aal5 } 2218 ::= { atmVclEntry 8 } 2220 atmVccAal5CpcsTransmitSduSize OBJECT-TYPE 2221 SYNTAX INTEGER (1..65535) 2222 MAX-ACCESS read-create 2224 draft ATM Management Objects August 15, 1998 2226 STATUS current 2227 DESCRIPTION 2228 "An instance of this object only exists when the 2229 local VCL end-point is also the VCC end-point, 2230 and AAL5 is in use. 2231 The maximum AAL5 CPCS SDU size in octets that is 2232 supported on the transmit direction of this VCC." 2233 DEFVAL { 9188 } 2234 ::= { atmVclEntry 9 } 2236 atmVccAal5CpcsReceiveSduSize OBJECT-TYPE 2237 SYNTAX INTEGER (1..65535) 2238 MAX-ACCESS read-create 2239 STATUS current 2240 DESCRIPTION 2241 "An instance of this object only exists when the 2242 local VCL end-point is also the VCC end-point, 2243 and AAL5 is in use. 2244 The maximum AAL5 CPCS SDU size in octets that is 2245 supported on the receive direction of this VCC." 2246 DEFVAL { 9188 } 2247 ::= { atmVclEntry 10 } 2249 atmVccAal5EncapsType OBJECT-TYPE 2250 SYNTAX INTEGER { 2251 vcMultiplexRoutedProtocol(1), 2252 vcMultiplexBridgedProtocol8023(2), 2253 vcMultiplexBridgedProtocol8025(3), 2254 vcMultiplexBridgedProtocol8026(4), 2255 vcMultiplexLANemulation8023(5), 2256 vcMultiplexLANemulation8025(6), 2257 llcEncapsulation(7), 2258 multiprotocolFrameRelaySscs(8), 2259 other(9), 2260 unknown(10) 2261 } 2262 MAX-ACCESS read-create 2263 STATUS current 2264 DESCRIPTION 2265 "An instance of this object only exists when the 2266 local VCL end-point is also the VCC end-point, 2267 and AAL5 is in use. 2268 The type of data encapsulation used over 2269 the AAL5 SSCS layer. The definitions reference 2270 RFC 1483 Multiprotocol Encapsulation 2272 draft ATM Management Objects August 15, 1998 2274 over ATM AAL5 and to the ATM Forum 2275 LAN Emulation specification." 2276 DEFVAL { llcEncapsulation } 2277 ::= { atmVclEntry 11 } 2279 atmVclCrossConnectIdentifier OBJECT-TYPE 2280 SYNTAX INTEGER (0..2147483647) 2281 MAX-ACCESS read-only 2282 STATUS current 2283 DESCRIPTION 2284 "This object is instantiated only for a VCL 2285 which is cross-connected to other VCLs 2286 that belong to the same VCC. All such 2287 associated VCLs have the same value of this 2288 object, and all their cross-connections are 2289 identified either by entries that are indexed 2290 by the same value of atmVcCrossConnectIndex in 2291 the atmVcCrossConnectTable of this MIB module or by 2292 the same value of the cross-connect index in 2293 the cross-connect table for SVCs and Soft PVCs 2294 (defined in a separate MIB module). 2296 At no time should entries in these respective 2297 cross-connect tables exist simultaneously 2298 with the same cross-connect index value. 2300 The value of this object is initialized by the 2301 agent after the associated entries in the 2302 atmVcCrossConnectTable have been created." 2303 ::= {atmVclEntry 12} 2305 atmVclRowStatus OBJECT-TYPE 2306 SYNTAX RowStatus 2307 MAX-ACCESS read-create 2308 STATUS current 2309 DESCRIPTION 2310 "This object is used to create, delete or 2311 modify a row in this table. To create 2312 a new VCL, this object is initially set 2313 to 'createAndWait' or 'createAndGo'. 2314 This object should not be 2315 set to 'active' unless the following columnar 2316 objects have been set to their desired value 2317 in this row: 2318 atmVclReceiveTrafficDescrIndex, 2320 draft ATM Management Objects August 15, 1998 2322 atmVclTransmitTrafficDescrIndex. 2323 In addition, if the local VCL end-point 2324 is also the VCC end-point: 2325 atmVccAalType. 2326 In addition, for AAL5 connections only: 2327 atmVccAal5CpcsTransmitSduSize, 2328 atmVccAal5CpcsReceiveSduSize, and 2329 atmVccAal5EncapsType. (The existence 2330 of these objects imply the AAL connection type.)" 2331 DEFVAL { active } 2332 ::= {atmVclEntry 13} 2334 atmVclCastType OBJECT-TYPE 2335 SYNTAX AtmConnCastType 2336 MAX-ACCESS read-create 2337 STATUS current 2338 DESCRIPTION 2339 "The connection topology type." 2340 DEFVAL { p2p } 2341 ::= {atmVclEntry 14} 2343 atmVclConnKind OBJECT-TYPE 2344 SYNTAX AtmConnKind 2345 MAX-ACCESS read-create 2346 STATUS current 2347 DESCRIPTION 2348 "The use of call control." 2349 DEFVAL { pvc } 2350 ::= {atmVclEntry 15} 2352 draft ATM Management Objects August 15, 1998 2354 -- ATM Virtual Path (VP) Cross Connect Table 2356 -- This table contains configuration and state 2357 -- information of point-to-point, 2358 -- point-to-multipoint, or multipoint-to-multipoint 2359 -- VP cross-connects for PVCs. 2361 -- This table has read-create access and can be used 2362 -- to cross-connect the VPLs together in an ATM switch 2363 -- or network. The atmVpCrossConnectIndex 2364 -- is used to associate the related 2365 -- VPLs that are cross-connected together. 2367 -- The ATM VP Cross Connect Table 2368 -- models each bi-directional VPC 2369 -- cross-connect as a set of entries in 2370 -- the atmVpCrossConnectTable. A 2371 -- point-to-point VPC cross-connect is modeled 2372 -- as one entry; a point-to-multipoint (N leafs) VPC 2373 -- cross-connect as N entries in this table; and 2374 -- a multipoint-to-multipoint (N parties) VPC cross- 2375 -- connect as N(N-1)/2 entries in this table. 2376 -- In the latter cases, all the N (or N(N-1)/2) entries 2377 -- are associated with a single VPC cross-connect by 2378 -- having the same value of atmVpCrossConnectIndex. 2380 -- _________________________________________ 2381 -- | | 2382 -- Low | ATM Switch or Network | High 2383 -- port| | port 2384 -- _____|>> from low to high VPC traffic flow >>|______ 2385 -- |<< from high to low VPC traffic flow <<| 2386 -- | | 2387 -- |_______________________________________| 2388 -- 2390 -- The terms low and high are chosen to represent 2391 -- numerical ordering of the two interfaces associated 2392 -- with a VPC cross-connect. That is, the ATM interface 2393 -- with the lower value of ifIndex is termed 'low', 2394 -- while the other ATM interface associated with the 2395 -- VPC cross-connect is termed 'high'. This terminology 2396 -- is used to provide directional information; for 2397 -- example, the atmVpCrossConnectL2HOperStatus applies 2399 draft ATM Management Objects August 15, 1998 2401 -- to the low->high direction, and 2402 -- atmVpCrossConnectH2LOperStatus applies to the 2403 -- high->low direction, as illustrated above. 2405 atmVpCrossConnectIndexNext OBJECT-TYPE 2406 SYNTAX INTEGER (0..2147483647) 2407 MAX-ACCESS read-only 2408 STATUS current 2409 DESCRIPTION 2410 "This object contains an appropriate value to 2411 be used for atmVpCrossConnectIndex when creating 2412 entries in the atmVpCrossConnectTable. The value 2413 0 indicates that no unassigned entries are 2414 available. To obtain the atmVpCrossConnectIndex 2415 value for a new entry, the manager issues a 2416 management protocol retrieval operation to obtain 2417 the current value of this object. After each 2418 retrieval, the agent should modify the value to 2419 the next unassigned index." 2420 ::= { atmMIBObjects 8 } 2422 -- The ATM VP Cross Connect Table 2424 atmVpCrossConnectTable OBJECT-TYPE 2425 SYNTAX SEQUENCE OF AtmVpCrossConnectEntry 2426 MAX-ACCESS not-accessible 2427 STATUS current 2428 DESCRIPTION 2429 "The ATM VP Cross Connect table for PVCs. 2430 An entry in this table models two 2431 cross-connected VPLs. 2432 Each VPL must have its atmConnKind set 2433 to pvc(1)." 2434 ::= { atmMIBObjects 9 } 2436 atmVpCrossConnectEntry OBJECT-TYPE 2437 SYNTAX AtmVpCrossConnectEntry 2438 MAX-ACCESS not-accessible 2439 STATUS current 2441 draft ATM Management Objects August 15, 1998 2443 DESCRIPTION 2444 "An entry in the ATM VP Cross Connect table. 2445 This entry is used to model a bi-directional 2446 ATM VP cross-connect which cross-connects 2447 two VPLs. 2449 Step-wise Procedures to set up a VP Cross-connect 2451 Once the entries in the atmVplTable are created, 2452 the following procedures are used 2453 to cross-connect the VPLs together. 2455 (1) The manager obtains a unique 2456 atmVpCrossConnectIndex by reading the 2457 atmVpCrossConnectIndexNext object. 2459 (2) Next, the manager creates a set of one 2460 or more rows in the ATM VP Cross Connect 2461 Table, one for each cross-connection between 2462 two VPLs. Each row is indexed by the ATM 2463 interface port numbers and VPI values of the 2464 two ends of that cross-connection. 2465 This set of rows specifies the topology of the 2466 VPC cross-connect and is identified by a single 2467 value of atmVpCrossConnectIndex. 2469 Negotiated VP Cross-Connect Establishment 2471 (2a) The manager creates a row in this table by 2472 setting atmVpCrossConnectRowStatus to 2473 createAndWait(5). The agent checks the 2474 requested topology and the mutual sanity of 2475 the ATM traffic parameters and 2476 service categories, i.e., the row creation 2477 fails if: 2478 - the requested topology is incompatible with 2479 associated values of atmVplCastType, 2480 - the requested topology is not supported 2481 by the agent, 2482 - the traffic/service category parameter values 2483 associated with the requested row are 2484 incompatible with those of already existing 2485 rows for this VP cross-connect. 2486 [For example, for setting up 2487 a point-to-point VP cross-connect, the 2489 draft ATM Management Objects August 15, 1998 2491 ATM traffic parameters in the receive direction 2492 of a VPL at the low end of the cross-connect 2493 must equal to the traffic parameters in the 2494 transmit direction of the other VPL at the 2495 high end of the cross-connect, 2496 otherwise, the row creation fails.] 2497 The agent also checks for internal errors 2498 in building the cross-connect. 2500 The atmVpCrossConnectIndex values in the 2501 corresponding atmVplTable rows are filled 2502 in by the agent at this point. 2504 (2b) The manager promotes the row in the 2505 atmVpCrossConnectTable by setting 2506 atmVpCrossConnectRowStatus to active(1). If 2507 this set is successful, the agent has reserved 2508 the resources specified by the ATM traffic 2509 parameter and Service category values 2510 for each direction of the VP cross-connect 2511 in an ATM switch or network. 2513 (3) The manager sets the 2514 atmVpCrossConnectAdminStatus to up(1) in all 2515 rows of this VP cross-connect to turn the 2516 traffic flow on. 2518 One-Shot VP Cross-Connect Establishment 2520 A VP cross-connect may also be established in 2521 one step by a set-request with all necessary 2522 parameter values and atmVpCrossConnectRowStatus 2523 set to createAndGo(4). 2525 In contrast to the negotiated VP cross-connect 2526 establishment which allows for detailed error 2527 checking (i.e., set errors are explicitly linked 2528 to particular resource acquisition failures), 2529 the one-shot VP cross-connect establishment 2530 performs the setup on one operation but does not 2531 have the advantage of step-wise error checking. 2533 VP Cross-Connect Retirement 2535 draft ATM Management Objects August 15, 1998 2537 A VP cross-connect identified by a particular 2538 value of atmVpCrossConnectIndex is released by: 2540 (1) Setting atmVpCrossConnectRowStatus of all 2541 rows identified by this value of 2542 atmVpCrossConnectIndex to destroy(6). 2543 The agent may release all 2544 associated resources, and the 2545 atmVpCrossConnectIndex values in the 2546 corresponding atmVplTable row are removed. 2547 Note that a situation when only a subset of 2548 the associated rows are deleted corresponds 2549 to a VP topology change. 2551 (2) After deletion of the appropriate 2552 atmVpCrossConnectEntries, the manager may 2553 set atmVplRowStatus to destroy(6) the 2554 associated VPLs. The agent releases 2555 the resources and removes the associated 2556 rows in the atmVplTable. 2558 VP Cross-connect Reconfiguration 2560 At the discretion of the agent, a VP 2561 cross-connect may be reconfigured by 2562 adding and/or deleting leafs to/from 2563 the VP topology as per the VP cross-connect 2564 establishment/retirement procedures. 2565 Reconfiguration of traffic/service category parameter 2566 values requires release of the VP cross-connect 2567 before those parameter values may by changed 2568 for individual VPLs." 2569 INDEX { atmVpCrossConnectIndex, 2570 atmVpCrossConnectLowIfIndex, 2571 atmVpCrossConnectLowVpi, 2572 atmVpCrossConnectHighIfIndex, 2573 atmVpCrossConnectHighVpi } 2574 ::= { atmVpCrossConnectTable 1 } 2576 AtmVpCrossConnectEntry ::= SEQUENCE { 2577 atmVpCrossConnectIndex INTEGER, 2578 atmVpCrossConnectLowIfIndex InterfaceIndex, 2579 atmVpCrossConnectLowVpi AtmVpIdentifier, 2580 atmVpCrossConnectHighIfIndex InterfaceIndex, 2581 atmVpCrossConnectHighVpi AtmVpIdentifier, 2583 draft ATM Management Objects August 15, 1998 2585 atmVpCrossConnectAdminStatus AtmVorXAdminStatus, 2586 atmVpCrossConnectL2HOperStatus AtmVorXOperStatus, 2587 atmVpCrossConnectH2LOperStatus AtmVorXOperStatus, 2588 atmVpCrossConnectL2HLastChange AtmVorXLastChange, 2589 atmVpCrossConnectH2LLastChange AtmVorXLastChange, 2590 atmVpCrossConnectRowStatus RowStatus 2591 } 2593 atmVpCrossConnectIndex OBJECT-TYPE 2594 SYNTAX INTEGER (1..2147483647) 2595 MAX-ACCESS not-accessible 2596 STATUS current 2597 DESCRIPTION 2598 "A unique value to identify this VP cross-connect. 2599 For each VPL associated with this cross-connect, 2600 the agent reports this cross-connect index value 2601 in the atmVplCrossConnectIdentifier attribute of 2602 the corresponding atmVplTable entries." 2603 ::= { atmVpCrossConnectEntry 1 } 2605 atmVpCrossConnectLowIfIndex OBJECT-TYPE 2606 SYNTAX InterfaceIndex 2607 MAX-ACCESS not-accessible 2608 STATUS current 2609 DESCRIPTION 2610 "The ifIndex value of the ATM interface for 2611 this VP cross-connect. The term low implies 2612 that this ATM interface has the numerically lower 2613 ifIndex value than the other ATM interface 2614 identified in the same atmVpCrossConnectEntry." 2615 ::= { atmVpCrossConnectEntry 2 } 2617 atmVpCrossConnectLowVpi OBJECT-TYPE 2618 SYNTAX AtmVpIdentifier 2619 MAX-ACCESS not-accessible 2620 STATUS current 2621 DESCRIPTION 2622 "The VPI value at the ATM interface 2623 associated with the VP cross-connect that is 2624 identified by atmVpCrossConnectLowIfIndex." 2625 ::= { atmVpCrossConnectEntry 3 } 2627 atmVpCrossConnectHighIfIndex OBJECT-TYPE 2628 SYNTAX InterfaceIndex 2629 MAX-ACCESS not-accessible 2631 draft ATM Management Objects August 15, 1998 2633 STATUS current 2634 DESCRIPTION 2635 "The ifIndex value of the ATM interface for 2636 this VP cross-connect. The term high implies that 2637 this ATM interface has the numerically higher 2638 ifIndex value than the other ATM interface 2639 identified in the same atmVpCrossConnectEntry." 2640 ::= { atmVpCrossConnectEntry 4 } 2642 atmVpCrossConnectHighVpi OBJECT-TYPE 2643 SYNTAX AtmVpIdentifier 2644 MAX-ACCESS not-accessible 2645 STATUS current 2646 DESCRIPTION 2647 "The VPI value at the ATM interface 2648 associated with the VP cross-connect that is 2649 identified by atmVpCrossConnectHighIfIndex." 2650 ::= { atmVpCrossConnectEntry 5 } 2652 atmVpCrossConnectAdminStatus OBJECT-TYPE 2653 SYNTAX AtmVorXAdminStatus 2654 MAX-ACCESS read-create 2655 STATUS current 2656 DESCRIPTION 2657 "The desired administrative status of this 2658 bi-directional VP cross-connect." 2659 DEFVAL { down } 2660 ::= { atmVpCrossConnectEntry 6 } 2662 atmVpCrossConnectL2HOperStatus OBJECT-TYPE 2663 SYNTAX AtmVorXOperStatus 2664 MAX-ACCESS read-only 2665 STATUS current 2666 DESCRIPTION 2667 "The operational status of the VP cross-connect 2668 in one direction; (i.e., from the low to 2669 high direction)." 2670 ::= { atmVpCrossConnectEntry 7 } 2672 atmVpCrossConnectH2LOperStatus OBJECT-TYPE 2673 SYNTAX AtmVorXOperStatus 2674 MAX-ACCESS read-only 2675 STATUS current 2676 DESCRIPTION 2677 "The operational status of the VP cross-connect 2679 draft ATM Management Objects August 15, 1998 2681 in one direction; (i.e., from the high to 2682 low direction)." 2683 ::= { atmVpCrossConnectEntry 8 } 2685 atmVpCrossConnectL2HLastChange OBJECT-TYPE 2686 SYNTAX AtmVorXLastChange 2687 MAX-ACCESS read-only 2688 STATUS current 2689 DESCRIPTION 2690 "The value of sysUpTime at the time this 2691 VP cross-connect entered its current operational 2692 state in the low to high direction." 2693 ::= { atmVpCrossConnectEntry 9 } 2695 atmVpCrossConnectH2LLastChange OBJECT-TYPE 2696 SYNTAX AtmVorXLastChange 2697 MAX-ACCESS read-only 2698 STATUS current 2699 DESCRIPTION 2700 "The value of sysUpTime at the time this 2701 VP cross-connect entered its current operational 2702 in the high to low direction." 2703 ::= { atmVpCrossConnectEntry 10 } 2705 atmVpCrossConnectRowStatus OBJECT-TYPE 2706 SYNTAX RowStatus 2707 MAX-ACCESS read-create 2708 STATUS current 2709 DESCRIPTION 2710 "The status of this entry in the 2711 atmVpCrossConnectTable. This object is used to 2712 create a cross-connect for cross-connecting 2713 VPLs which are created using the atmVplTable 2714 or to change or delete an existing cross-connect. 2715 This object must be initially set 2716 to `createAndWait' or 'createAndGo'. 2717 To turn on a VP cross-connect, 2718 the atmVpCrossConnectAdminStatus 2719 is set to `up'." 2720 DEFVAL { active } 2721 ::= { atmVpCrossConnectEntry 11 } 2723 draft ATM Management Objects August 15, 1998 2725 -- ATM Virtual Channel (VC) Cross Connect Table 2727 -- This table contains configuration and state 2728 -- information of point-to-point, 2729 -- point-to-multipoint or multipoint-to-multipoint 2730 -- VC cross-connects for PVCs. 2732 -- This table has read-create access and is used 2733 -- to cross-connect the VCLs together in an ATM switch 2734 -- or network that belong to a VC connection. 2735 -- The atmVcCrossConnectIndex is used to associate 2736 -- the related VCLs that are cross-connected together. 2738 -- The model using step-wise procedures described for setting 2739 -- up a VP cross-connect is also used for setting up 2740 -- a VC cross-connect. 2742 atmVcCrossConnectIndexNext OBJECT-TYPE 2743 SYNTAX INTEGER (0..2147483647) 2744 MAX-ACCESS read-only 2745 STATUS current 2746 DESCRIPTION 2747 "This object contains an appropriate value to 2748 be used for atmVcCrossConnectIndex when creating 2749 entries in the atmVcCrossConnectTable. The value 2750 0 indicates that no unassigned entries are 2751 available. To obtain the atmVcCrossConnectIndex 2752 value for a new entry, the manager issues a 2753 management protocol retrieval operation to obtain 2754 the current value of this object. After each 2755 retrieval, the agent should modify the value to 2756 the next unassigned index." 2757 ::= { atmMIBObjects 10 } 2759 -- The ATM VC Cross Connect Table 2761 atmVcCrossConnectTable OBJECT-TYPE 2762 SYNTAX SEQUENCE OF AtmVcCrossConnectEntry 2763 MAX-ACCESS not-accessible 2764 STATUS current 2766 draft ATM Management Objects August 15, 1998 2768 DESCRIPTION 2769 "The ATM VC Cross Connect table for PVCs. 2770 An entry in this table models two 2771 cross-connected VCLs. 2772 Each VCL must have its atmConnKind set 2773 to pvc(1)." 2774 ::= { atmMIBObjects 11 } 2776 atmVcCrossConnectEntry OBJECT-TYPE 2777 SYNTAX AtmVcCrossConnectEntry 2778 MAX-ACCESS not-accessible 2779 STATUS current 2780 DESCRIPTION 2781 "An entry in the ATM VC Cross Connect table. 2782 This entry is used to model a bi-directional ATM 2783 VC cross-connect cross-connecting two end points. 2785 Step-wise Procedures to set up a VC Cross-connect 2787 Once the entries in the atmVclTable are created, 2788 the following procedures are used 2789 to cross-connect the VCLs together to 2790 form a VCC segment. 2792 (1) The manager obtains a unique 2793 atmVcCrossConnectIndex by reading the 2794 atmVcCrossConnectIndexNext object. 2796 (2) Next, the manager creates a set of one 2797 or more rows in the ATM VC Cross Connect 2798 Table, one for each cross-connection between 2799 two VCLs. Each row is indexed by the ATM 2800 interface port numbers and VPI/VCI values of 2801 the two ends of that cross-connection. 2802 This set of rows specifies the topology of the 2803 VCC cross-connect and is identified by a single 2804 value of atmVcCrossConnectIndex. 2806 Negotiated VC Cross-Connect Establishment 2808 (2a) The manager creates a row in this table by 2809 setting atmVcCrossConnectRowStatus to 2810 createAndWait(5). The agent checks the 2811 requested topology and the mutual sanity of 2813 draft ATM Management Objects August 15, 1998 2815 the ATM traffic parameters and 2816 service categories, i.e., the row creation 2817 fails if: 2818 - the requested topology is incompatible with 2819 associated values of atmVclCastType, 2820 - the requested topology is not supported 2821 by the agent, 2822 - the traffic/service category parameter values 2823 associated with the requested row are 2824 incompatible with those of already existing 2825 rows for this VC cross-connect. 2826 [For example, for setting up 2827 a point-to-point VC cross-connect, the 2828 ATM traffic parameters in the receive direction 2829 of a VCL at the low end of the cross-connect 2830 must equal to the traffic parameters in the 2831 transmit direction of the other VCL at the 2832 high end of the cross-connect, 2833 otherwise, the row creation fails.] 2834 The agent also checks for internal errors 2835 in building the cross-connect. 2837 The atmVcCrossConnectIndex values in the 2838 corresponding atmVclTable rows are filled 2839 in by the agent at this point. 2841 (2b) The manager promotes the row in the 2842 atmVcCrossConnectTable by setting 2843 atmVcCrossConnectRowStatus to active(1). If 2844 this set is successful, the agent has reserved 2845 the resources specified by the ATM traffic 2846 parameter and Service category values 2847 for each direction of the VC cross-connect 2848 in an ATM switch or network. 2850 (3) The manager sets the 2851 atmVcCrossConnectAdminStatus to up(1) 2852 in all rows of this VC cross-connect to 2853 turn the traffic flow on. 2855 One-Shot VC Cross-Connect Establishment 2857 A VC cross-connect may also be established in 2858 one step by a set-request with all necessary 2860 draft ATM Management Objects August 15, 1998 2862 parameter values and atmVcCrossConnectRowStatus 2863 set to createAndGo(4). 2865 In contrast to the negotiated VC cross-connect 2866 establishment which allows for detailed error 2867 checking i.e., set errors are explicitly linked to 2868 particular resource acquisition failures), the 2869 one-shot VC cross-connect establishment 2870 performs the setup on one operation but does 2871 not have the advantage of step-wise error 2872 checking. 2874 VC Cross-Connect Retirement 2876 A VC cross-connect identified by a particular 2877 value of atmVcCrossConnectIndex is released by: 2879 (1) Setting atmVcCrossConnectRowStatus of all rows 2880 identified by this value of 2881 atmVcCrossConnectIndex to destroy(6). 2882 The agent may release all 2883 associated resources, and the 2884 atmVcCrossConnectIndex values in the 2885 corresponding atmVclTable row are removed. 2886 Note that a situation when only a subset of 2887 the associated rows are deleted corresponds 2888 to a VC topology change. 2890 (2) After deletion of the appropriate 2891 atmVcCrossConnectEntries, the manager may 2892 set atmVclRowStatus to destroy(6) the 2893 associated VCLs. The agent releases 2894 the resources and removes the associated 2895 rows in the atmVclTable. 2897 VC Cross-Connect Reconfiguration 2899 At the discretion of the agent, a VC 2900 cross-connect may be reconfigured by 2901 adding and/or deleting leafs to/from 2902 the VC topology as per the VC cross-connect 2903 establishment/retirement procedures. 2904 Reconfiguration of traffic/service category parameter 2905 values requires release of the VC cross-connect 2906 before those parameter values may by changed 2908 draft ATM Management Objects August 15, 1998 2910 for individual VCLs." 2911 INDEX { atmVcCrossConnectIndex, 2912 atmVcCrossConnectLowIfIndex, 2913 atmVcCrossConnectLowVpi, 2914 atmVcCrossConnectLowVci, 2915 atmVcCrossConnectHighIfIndex, 2916 atmVcCrossConnectHighVpi, 2917 atmVcCrossConnectHighVci } 2918 ::= { atmVcCrossConnectTable 1 } 2920 AtmVcCrossConnectEntry ::= SEQUENCE { 2921 atmVcCrossConnectIndex INTEGER, 2922 atmVcCrossConnectLowIfIndex InterfaceIndex, 2923 atmVcCrossConnectLowVpi AtmVpIdentifier, 2924 atmVcCrossConnectLowVci AtmVcIdentifier, 2925 atmVcCrossConnectHighIfIndex InterfaceIndex, 2926 atmVcCrossConnectHighVpi AtmVpIdentifier, 2927 atmVcCrossConnectHighVci AtmVcIdentifier, 2928 atmVcCrossConnectAdminStatus AtmVorXAdminStatus, 2929 atmVcCrossConnectL2HOperStatus AtmVorXOperStatus, 2930 atmVcCrossConnectH2LOperStatus AtmVorXOperStatus, 2931 atmVcCrossConnectL2HLastChange AtmVorXLastChange, 2932 atmVcCrossConnectH2LLastChange AtmVorXLastChange, 2933 atmVcCrossConnectRowStatus RowStatus 2934 } 2936 atmVcCrossConnectIndex OBJECT-TYPE 2937 SYNTAX INTEGER (1..2147483647) 2938 MAX-ACCESS not-accessible 2939 STATUS current 2940 DESCRIPTION 2941 "A unique value to identify this VC cross-connect. 2942 For each VCL associated with this cross-connect, 2943 the agent reports this cross-connect index value 2944 in the atmVclCrossConnectIdentifier attribute of 2945 the corresponding atmVclTable entries." 2946 ::= { atmVcCrossConnectEntry 1 } 2948 atmVcCrossConnectLowIfIndex OBJECT-TYPE 2949 SYNTAX InterfaceIndex 2950 MAX-ACCESS not-accessible 2951 STATUS current 2952 DESCRIPTION 2953 "The ifIndex value of the ATM interface for this 2954 VC cross-connect. The term low implies 2956 draft ATM Management Objects August 15, 1998 2958 that this ATM interface has the numerically lower 2959 ifIndex value than the other ATM interface 2960 identified in the same atmVcCrossConnectEntry." 2961 ::= { atmVcCrossConnectEntry 2 } 2963 atmVcCrossConnectLowVpi OBJECT-TYPE 2964 SYNTAX AtmVpIdentifier 2965 MAX-ACCESS not-accessible 2966 STATUS current 2967 DESCRIPTION 2968 "The VPI value at the ATM interface 2969 associated with the VC cross-connect that is 2970 identified by atmVcCrossConnectLowIfIndex." 2971 ::= { atmVcCrossConnectEntry 3 } 2973 atmVcCrossConnectLowVci OBJECT-TYPE 2974 SYNTAX AtmVcIdentifier 2975 MAX-ACCESS not-accessible 2976 STATUS current 2977 DESCRIPTION 2978 "The VCI value at the ATM interface 2979 associated with this VC cross-connect that is 2980 identified by atmVcCrossConnectLowIfIndex." 2981 ::= { atmVcCrossConnectEntry 4 } 2983 atmVcCrossConnectHighIfIndex OBJECT-TYPE 2984 SYNTAX InterfaceIndex 2985 MAX-ACCESS not-accessible 2986 STATUS current 2987 DESCRIPTION 2988 "The ifIndex value for the ATM interface for 2989 this VC cross-connect. The term high implies 2990 that this ATM interface has the numerically higher 2991 ifIndex value than the other ATM interface 2992 identified in the same atmVcCrossConnectEntry." 2993 ::= { atmVcCrossConnectEntry 5 } 2995 atmVcCrossConnectHighVpi OBJECT-TYPE 2996 SYNTAX AtmVpIdentifier 2997 MAX-ACCESS not-accessible 2998 STATUS current 2999 DESCRIPTION 3000 "The VPI value at the ATM interface 3001 associated with the VC cross-connect that is 3002 identified by atmVcCrossConnectHighIfIndex." 3004 draft ATM Management Objects August 15, 1998 3006 ::= { atmVcCrossConnectEntry 6 } 3008 atmVcCrossConnectHighVci OBJECT-TYPE 3009 SYNTAX AtmVcIdentifier 3010 MAX-ACCESS not-accessible 3011 STATUS current 3012 DESCRIPTION 3013 "The VCI value at the ATM interface 3014 associated with the VC cross-connect that is 3015 identified by atmVcCrossConnectHighIfIndex." 3016 ::= { atmVcCrossConnectEntry 7 } 3018 atmVcCrossConnectAdminStatus OBJECT-TYPE 3019 SYNTAX AtmVorXAdminStatus 3020 MAX-ACCESS read-create 3021 STATUS current 3022 DESCRIPTION 3023 "The desired administrative status of this 3024 bi-directional VC cross-connect." 3025 DEFVAL { down } 3026 ::= { atmVcCrossConnectEntry 8 } 3028 atmVcCrossConnectL2HOperStatus OBJECT-TYPE 3029 SYNTAX AtmVorXOperStatus 3030 MAX-ACCESS read-only 3031 STATUS current 3032 DESCRIPTION 3033 "The current operational status of the 3034 VC cross-connect in one direction; (i.e., 3035 from the low to high direction)." 3036 ::= { atmVcCrossConnectEntry 9 } 3038 atmVcCrossConnectH2LOperStatus OBJECT-TYPE 3039 SYNTAX AtmVorXOperStatus 3040 MAX-ACCESS read-only 3041 STATUS current 3042 DESCRIPTION 3043 "The current operational status of the 3044 VC cross-connect in one direction; (i.e., 3045 from the high to low direction)." 3046 ::= { atmVcCrossConnectEntry 10 } 3048 atmVcCrossConnectL2HLastChange OBJECT-TYPE 3049 SYNTAX AtmVorXLastChange 3051 draft ATM Management Objects August 15, 1998 3053 MAX-ACCESS read-only 3054 STATUS current 3055 DESCRIPTION 3056 "The value of sysUpTime at the time this 3057 VC cross-connect entered its current 3058 operational state in low to high direction." 3059 ::= { atmVcCrossConnectEntry 11 } 3061 atmVcCrossConnectH2LLastChange OBJECT-TYPE 3062 SYNTAX AtmVorXLastChange 3063 MAX-ACCESS read-only 3064 STATUS current 3065 DESCRIPTION 3066 "The value of sysUpTime at the time this 3067 VC cross-connect entered its current 3068 operational state in high to low direction." 3069 ::= { atmVcCrossConnectEntry 12 } 3071 atmVcCrossConnectRowStatus OBJECT-TYPE 3072 SYNTAX RowStatus 3073 MAX-ACCESS read-create 3074 STATUS current 3075 DESCRIPTION 3076 "The status of this entry in the 3077 atmVcCrossConnectTable. This object is used to 3078 create a new cross-connect for cross-connecting 3079 VCLs which are created using the atmVclTable 3080 or to change or delete existing cross-connect. 3081 This object must be initially set to 3082 `createAndWait' or 'createAndGo'. 3083 To turn on a VC cross-connect, 3084 the atmVcCrossConnectAdminStatus 3085 is set to `up'." 3086 DEFVAL { active } 3087 ::= { atmVcCrossConnectEntry 13 } 3089 draft ATM Management Objects August 15, 1998 3091 -- AAL5 Virtual Channel Connection Performance Statistics 3092 -- Table 3094 -- This table contains the AAL5 3095 -- performance statistics of a VCC at the 3096 -- interface associated with an AAL5 entity in an ATM 3097 -- host or ATM switch. 3099 aal5VccTable OBJECT-TYPE 3100 SYNTAX SEQUENCE OF Aal5VccEntry 3101 MAX-ACCESS not-accessible 3102 STATUS current 3103 DESCRIPTION 3104 "This table contains AAL5 VCC performance 3105 parameters." 3106 ::= { atmMIBObjects 12 } 3108 aal5VccEntry OBJECT-TYPE 3109 SYNTAX Aal5VccEntry 3110 MAX-ACCESS not-accessible 3111 STATUS current 3112 DESCRIPTION 3113 "This list contains the AAL5 VCC 3114 performance parameters and is indexed 3115 by ifIndex values of AAL5 interfaces 3116 and the associated VPI/VCI values." 3117 INDEX { ifIndex, aal5VccVpi, aal5VccVci } 3118 ::= { aal5VccTable 1 } 3120 Aal5VccEntry ::= SEQUENCE { 3121 aal5VccVpi AtmVpIdentifier, 3122 aal5VccVci AtmVcIdentifier, 3123 aal5VccCrcErrors Counter32, 3124 aal5VccSarTimeOuts Counter32, 3125 aal5VccOverSizedSDUs Counter32 3126 } 3128 aal5VccVpi OBJECT-TYPE 3129 SYNTAX AtmVpIdentifier 3130 MAX-ACCESS not-accessible 3131 STATUS current 3132 DESCRIPTION 3133 "The VPI value of the AAL5 VCC at the 3135 draft ATM Management Objects August 15, 1998 3137 interface identified by the ifIndex." 3138 ::= { aal5VccEntry 1 } 3140 aal5VccVci OBJECT-TYPE 3141 SYNTAX AtmVcIdentifier 3142 MAX-ACCESS not-accessible 3143 STATUS current 3144 DESCRIPTION 3145 "The VCI value of the AAL5 VCC at the 3146 interface identified by the ifIndex." 3147 ::= { aal5VccEntry 2 } 3149 aal5VccCrcErrors OBJECT-TYPE 3150 SYNTAX Counter32 3151 MAX-ACCESS read-only 3152 STATUS current 3153 DESCRIPTION 3154 "The number of AAL5 CPCS PDUs received with 3155 CRC-32 errors on this AAL5 VCC at the 3156 interface associated with an AAL5 entity." 3157 ::= { aal5VccEntry 3 } 3159 aal5VccSarTimeOuts OBJECT-TYPE 3160 SYNTAX Counter32 3161 MAX-ACCESS read-only 3162 STATUS current 3163 DESCRIPTION 3164 "The number of partially re-assembled AAL5 3165 CPCS PDUs which were discarded 3166 on this AAL5 VCC at the interface associated 3167 with an AAL5 entity because they 3168 were not fully re-assembled within the 3169 required time period. If the re-assembly 3170 timer is not supported, then this object 3171 contains a zero value." 3172 ::= { aal5VccEntry 4 } 3174 aal5VccOverSizedSDUs OBJECT-TYPE 3175 SYNTAX Counter32 3176 MAX-ACCESS read-only 3177 STATUS current 3178 DESCRIPTION 3179 "The number of AAL5 CPCS PDUs discarded 3180 on this AAL5 VCC at the interface 3181 associated with an AAL5 entity because the 3183 draft ATM Management Objects August 15, 1998 3185 AAL5 SDUs were too large." 3186 ::= { aal5VccEntry 5 } 3188 -- 3189 -- The following object may be used in conjunction with 3190 -- the atmTrafficDescrParamTable for the creation of 3191 -- new table entries. 3192 -- 3194 atmTrafficDescrParamIndexNext OBJECT-TYPE 3195 SYNTAX INTEGER (0..2147483647) 3196 MAX-ACCESS read-only 3197 STATUS current 3198 DESCRIPTION 3199 "This object contains an appropriate value to 3200 be used for atmTrafficDescrParamIndex when 3201 creating entries in the 3202 atmTrafficDescrParamTable. 3203 The value 0 indicates that no unassigned 3204 entries are available. To obtain the 3205 atmTrafficDescrParamIndex value for a new 3206 entry, the manager issues a management 3207 protocol retrieval operation to obtain the 3208 current value of this object. After each 3209 retrieval, the agent should modify the value 3210 to the next unassigned index." 3211 ::= { atmMIBObjects 13 } 3213 draft ATM Management Objects August 15, 1998 3215 -- Conformance Information 3217 atmMIBConformance OBJECT IDENTIFIER ::= { atmMIB 2 } 3219 atmMIBGroups OBJECT IDENTIFIER 3220 ::= { atmMIBConformance 1 } 3221 atmMIBCompliances OBJECT IDENTIFIER 3222 ::= { atmMIBConformance 2 } 3224 -- Compliance Statements 3226 atmMIBCompliance2 MODULE-COMPLIANCE 3227 STATUS current 3228 DESCRIPTION 3229 "The compliance statement for SNMP entities 3230 including networks which have ATM and 3231 AAL5 interfaces." 3233 MODULE -- this module 3234 -- 3235 -- ****** Interface and Traffic Descriptor Support *** 3236 -- 3237 MANDATORY-GROUPS {atmInterfaceConfGroup2, 3238 atmTrafficDescrGroup2 } 3240 OBJECT atmInterfaceMaxVpcs 3241 MIN-ACCESS read-only 3242 DESCRIPTION 3243 "Write access is not required." 3245 OBJECT atmInterfaceMaxVccs 3246 MIN-ACCESS read-only 3247 DESCRIPTION 3248 "Write access is not required." 3250 OBJECT atmInterfaceMaxActiveVpiBits 3251 MIN-ACCESS read-only 3252 DESCRIPTION 3253 "Write access is not required. 3254 At the ATM UNI the maximum number of 3255 active VPI bits configured for use ranges 3256 from 0 to 8 only. 3257 Implementations may support smaller ranges." 3259 draft ATM Management Objects August 15, 1998 3261 OBJECT atmInterfaceMaxActiveVciBits 3262 MIN-ACCESS read-only 3263 DESCRIPTION 3264 "Write access is not required. 3265 Implementations may support smaller ranges." 3267 OBJECT atmInterfaceIlmiVpi 3268 MIN-ACCESS read-only 3269 DESCRIPTION 3270 "Write access is not required." 3272 OBJECT atmInterfaceIlmiVci 3273 MIN-ACCESS read-only 3274 DESCRIPTION 3275 "Write access is not required." 3277 OBJECT atmInterfaceMyNeighborIpAddress 3278 MIN-ACCESS read-only 3279 DESCRIPTION 3280 "Write access is not required." 3282 OBJECT atmInterfaceMyNeighborIfName 3283 MIN-ACCESS read-only 3284 DESCRIPTION 3285 "Write access is not required." 3287 OBJECT atmInterfaceSubscrAddress 3288 MIN-ACCESS read-only 3289 DESCRIPTION 3290 "Write access is not required." 3292 OBJECT atmTrafficDescrParamIndexNext 3293 DESCRIPTION 3294 "This object is only required for systems 3295 that support the creation of entries in 3296 the atmTrafficDescrParamTable." 3298 OBJECT atmTrafficDescrType 3299 MIN-ACCESS read-only 3300 DESCRIPTION 3301 "Write access is not required." 3303 OBJECT atmTrafficDescrParam1 3304 MIN-ACCESS read-only 3305 DESCRIPTION 3307 draft ATM Management Objects August 15, 1998 3309 "Write access is not required." 3311 OBJECT atmTrafficDescrParam2 3312 MIN-ACCESS read-only 3313 DESCRIPTION 3314 "Write access is not required." 3316 OBJECT atmTrafficDescrParam3 3317 MIN-ACCESS read-only 3318 DESCRIPTION 3319 "Write access is not required." 3321 OBJECT atmTrafficDescrParam4 3322 MIN-ACCESS read-only 3323 DESCRIPTION 3324 "Write access is not required." 3326 OBJECT atmTrafficDescrParam5 3327 MIN-ACCESS read-only 3328 DESCRIPTION 3329 "Write access is not required." 3331 OBJECT atmServiceCategory 3332 MIN-ACCESS read-only 3333 DESCRIPTION 3334 "Write access is not required." 3336 OBJECT atmTrafficDescrRowStatus 3337 SYNTAX INTEGER {active(1)} 3338 -- subset of RowStatus 3339 MIN-ACCESS read-only 3340 DESCRIPTION 3341 "Write access is not required, and only one 3342 of the six enumerated values for the 3343 RowStatus textual convention need be 3344 supported, specifically: active(1)." 3346 OBJECT atmTrafficFrameDiscard 3347 MIN-ACCESS read-only 3348 DESCRIPTION 3349 "Write access is not required." 3351 -- 3352 -- ****** DS3 PLCP Support ************************** 3353 -- 3355 draft ATM Management Objects August 15, 1998 3357 GROUP atmInterfaceDs3PlcpGroup 3358 DESCRIPTION 3359 "This group is mandatory only for those 3360 ATM interfaces which implement the 3361 DS3 PLCP layer." 3362 -- 3363 -- ****** TC Sublayer Support ******************************** 3364 -- 3365 GROUP atmInterfaceTCGroup 3366 DESCRIPTION 3367 "This group is mandatory only for those 3368 ATM interfaces which implement the 3369 TC Sublayer." 3371 -- 3372 -- ****** VPC Support ******************************* 3373 -- 3374 GROUP atmVpcTerminationGroup2 3375 DESCRIPTION 3376 "This group is mandatory only for those 3377 ATM interfaces which implement ATM 3378 VPLs that terminate VPCs (i.e., ones which 3379 are NOT cross-connected to other VPLs)." 3381 GROUP atmVplCrossConnectGroup 3382 DESCRIPTION 3383 "This group is mandatory only for those 3384 ATM interfaces which implement ATM 3385 VPLs that are not associated with VCLs 3386 and are cross-connected to other VPLs 3387 for VPCs." 3389 GROUP atmVpPvcCrossConnectGroup 3390 DESCRIPTION 3391 "This group is mandatory only for those 3392 ATM interfaces which implement ATM 3393 VPLs that are not associated with VCLs 3394 and are cross-connected to other VPLs 3395 for permanent VPCs (i.e., PVCs). 3396 This group is not used to crossconnect 3397 a PVC with an SVC to form a Soft PVC." 3399 OBJECT atmVplAdminStatus 3400 MIN-ACCESS read-only 3401 DESCRIPTION 3403 draft ATM Management Objects August 15, 1998 3405 "Write access is not required." 3407 OBJECT atmVplReceiveTrafficDescrIndex 3408 MIN-ACCESS read-only 3409 DESCRIPTION 3410 "Write access is not required." 3412 OBJECT atmVplTransmitTrafficDescrIndex 3413 MIN-ACCESS read-only 3414 DESCRIPTION 3415 "Write access is not required." 3417 OBJECT atmVplRowStatus 3418 SYNTAX INTEGER {active(1)} 3419 -- subset of RowStatus 3420 MIN-ACCESS read-only 3421 DESCRIPTION 3422 "Write access is not required, and only one 3423 of the six enumerated values for the 3424 RowStatus textual convention need be 3425 supported, specifically: active(1)." 3427 OBJECT atmVplCastType 3428 MIN-ACCESS read-only 3429 DESCRIPTION 3430 "Write access is not required." 3432 OBJECT atmVplConnKind 3433 MIN-ACCESS read-only 3434 DESCRIPTION 3435 "Write access is not required." 3437 OBJECT atmVpCrossConnectAdminStatus 3438 MIN-ACCESS read-only 3439 DESCRIPTION 3440 "Write access is not required." 3442 OBJECT atmVpCrossConnectRowStatus 3443 SYNTAX INTEGER {active(1)} 3444 -- subset of RowStatus 3445 MIN-ACCESS read-only 3446 DESCRIPTION 3447 "Write access is not required, and only one 3448 of the six enumerated values for the 3449 RowStatus textual convention need be 3451 draft ATM Management Objects August 15, 1998 3453 supported, specifically: active(1)." 3455 -- 3456 -- ****** VCC Support ******************************* 3457 -- 3458 GROUP atmVccTerminationGroup2 3459 DESCRIPTION 3460 "This group is mandatory only for those 3461 ATM interfaces which implement ATM 3462 VCLs that terminate VCCs (i.e., ones which 3463 are NOT cross-connected to other VCLs)." 3465 GROUP atmVclCrossConnectGroup 3466 DESCRIPTION 3467 "This group is mandatory only for those 3468 ATM interfaces which implement ATM 3469 VCLs that are cross-connected to other VCLs 3470 for VCCs." 3472 GROUP atmVcPvcCrossConnectGroup 3473 DESCRIPTION 3474 "This group is mandatory only for those 3475 ATM interfaces which implement ATM 3476 VCLs that are cross-connected to other 3477 VCLs for permanent VCCs (i.e., PVCs). 3478 This group is not used to crossconnect 3479 a PVC with an SVC to form a Soft PVC." 3481 OBJECT atmVclAdminStatus 3482 MIN-ACCESS read-only 3483 DESCRIPTION 3484 "Write access is not required." 3486 OBJECT atmVclReceiveTrafficDescrIndex 3487 MIN-ACCESS read-only 3488 DESCRIPTION 3489 "Write access is not required." 3491 OBJECT atmVclTransmitTrafficDescrIndex 3492 MIN-ACCESS read-only 3493 DESCRIPTION 3494 "Write access is not required." 3496 OBJECT atmVccAalType 3497 MIN-ACCESS read-only 3499 draft ATM Management Objects August 15, 1998 3501 DESCRIPTION 3502 "Write access is not required." 3504 OBJECT atmVclRowStatus 3505 SYNTAX INTEGER {active(1)} 3506 -- subset of RowStatus 3507 MIN-ACCESS read-only 3508 DESCRIPTION 3509 "Write access is not required, and only one 3510 of the six enumerated values for the 3511 RowStatus textual convention need be 3512 supported, specifically: active(1)." 3514 OBJECT atmVclCastType 3515 MIN-ACCESS read-only 3516 DESCRIPTION 3517 "Write access is not required." 3519 OBJECT atmVclConnKind 3520 MIN-ACCESS read-only 3521 DESCRIPTION 3522 "Write access is not required." 3524 OBJECT atmVcCrossConnectAdminStatus 3525 MIN-ACCESS read-only 3526 DESCRIPTION 3527 "Write access is not required." 3529 OBJECT atmVcCrossConnectRowStatus 3530 SYNTAX INTEGER { active(1)} 3531 -- subset of RowStatus 3532 MIN-ACCESS read-only 3533 DESCRIPTION 3534 "Write access is not required, and only one 3535 of the six enumerated values for the 3536 RowStatus textual convention need be 3537 supported, specifically: active(1)." 3538 -- 3539 -- ****** AAL5 Support ****************************** 3540 -- 3541 GROUP aal5VccGroup 3542 DESCRIPTION 3543 "This group is mandatory for the 3544 AAL5 virtual connections only." 3546 draft ATM Management Objects August 15, 1998 3548 OBJECT atmVccAal5CpcsTransmitSduSize 3549 MIN-ACCESS read-only 3550 DESCRIPTION 3551 "Write access is not required." 3553 OBJECT atmVccAal5CpcsReceiveSduSize 3554 MIN-ACCESS read-only 3555 DESCRIPTION 3556 "Write access is not required." 3558 OBJECT atmVccAal5EncapsType 3559 MIN-ACCESS read-only 3560 DESCRIPTION 3561 "Write access is not required." 3562 ::= { atmMIBCompliances 2 } 3564 draft ATM Management Objects August 15, 1998 3566 -- Units of Conformance 3568 atmInterfaceDs3PlcpGroup OBJECT-GROUP 3569 OBJECTS {atmInterfaceDs3PlcpSEFSs, 3570 atmInterfaceDs3PlcpAlarmState, 3571 atmInterfaceDs3PlcpUASs} 3572 STATUS current 3573 DESCRIPTION 3574 "A collection of objects providing information 3575 about DS3 PLCP layer at an ATM interface." 3576 ::= { atmMIBGroups 3 } 3578 atmInterfaceTCGroup OBJECT-GROUP 3579 OBJECTS { atmInterfaceOCDEvents, 3580 atmInterfaceTCAlarmState } 3581 STATUS current 3582 DESCRIPTION 3583 "A collection of objects providing information 3584 about TC sublayer at an ATM interface." 3585 ::= { atmMIBGroups 4 } 3587 aal5VccGroup OBJECT-GROUP 3588 OBJECTS {atmVccAal5CpcsTransmitSduSize, 3589 atmVccAal5CpcsReceiveSduSize, 3590 atmVccAal5EncapsType, 3591 aal5VccCrcErrors, aal5VccSarTimeOuts, 3592 aal5VccOverSizedSDUs } 3593 STATUS current 3594 DESCRIPTION 3595 "A collection of objects providing 3596 AAL5 configuration and performance statistics 3597 of a VCC." 3598 ::= { atmMIBGroups 9 } 3600 atmInterfaceConfGroup2 OBJECT-GROUP 3601 OBJECTS { 3602 atmInterfaceMaxVpcs, atmInterfaceMaxVccs, 3603 atmInterfaceConfVpcs, atmInterfaceConfVccs, 3604 atmInterfaceMaxActiveVpiBits, 3605 atmInterfaceMaxActiveVciBits, 3606 atmInterfaceIlmiVpi, 3607 atmInterfaceIlmiVci, 3608 atmInterfaceMyNeighborIpAddress, 3609 atmInterfaceMyNeighborIfName, 3610 atmInterfaceCurrentMaxVpiBits, 3612 draft ATM Management Objects August 15, 1998 3614 atmInterfaceCurrentMaxVciBits, 3615 atmInterfaceSubscrAddress } 3616 STATUS current 3617 DESCRIPTION 3618 "A collection of objects providing configuration 3619 information about an ATM interface." 3620 ::= { atmMIBGroups 10 } 3622 atmTrafficDescrGroup2 OBJECT-GROUP 3623 OBJECTS { 3624 atmTrafficDescrType, atmTrafficDescrParam1, 3625 atmTrafficDescrParam2, atmTrafficDescrParam3, 3626 atmTrafficDescrParam4, atmTrafficDescrParam5, 3627 atmTrafficDescrRowStatus, atmServiceCategory, 3628 atmTrafficFrameDiscard, 3629 atmTrafficDescrParamIndexNext } 3630 STATUS current 3631 DESCRIPTION 3632 "A collection of objects providing information 3633 about ATM traffic descriptor type and 3634 the associated parameters." 3635 ::= { atmMIBGroups 11 } 3637 atmVpcTerminationGroup2 OBJECT-GROUP 3638 OBJECTS {atmVplOperStatus, atmVplAdminStatus, 3639 atmVplLastChange, 3640 atmVplReceiveTrafficDescrIndex, 3641 atmVplTransmitTrafficDescrIndex, 3642 atmVplRowStatus, atmVplCastType, 3643 atmVplConnKind } 3644 STATUS current 3645 DESCRIPTION 3646 "A collection of objects providing information 3647 about a VPL at an ATM interface which 3648 terminates a VPC (i.e., one which is NOT 3649 cross-connected to other VPLs)." 3650 ::= { atmMIBGroups 12 } 3652 atmVccTerminationGroup2 OBJECT-GROUP 3653 OBJECTS {atmVclOperStatus, atmVclAdminStatus, 3654 atmVclLastChange, 3655 atmVclReceiveTrafficDescrIndex, 3656 atmVclTransmitTrafficDescrIndex, 3657 atmVccAalType, atmVclRowStatus, 3658 atmVclCastType, atmVclConnKind } 3660 draft ATM Management Objects August 15, 1998 3662 STATUS current 3663 DESCRIPTION 3664 "A collection of objects providing information 3665 about a VCL at an ATM interface 3666 which terminates a VCC (i.e., one which is 3667 NOT cross-connected to other VCLs)." 3668 ::= { atmMIBGroups 13 } 3670 atmVplCrossConnectGroup OBJECT-GROUP 3671 OBJECTS { atmVplReceiveTrafficDescrIndex, 3672 atmVplTransmitTrafficDescrIndex, 3673 atmVplOperStatus, atmVplLastChange, 3674 atmVplRowStatus, 3675 atmVplCastType, atmVplConnKind } 3676 STATUS current 3677 DESCRIPTION 3678 "A collection of objects providing 3679 information about the VPLs that 3680 are cross-connected together." 3681 ::= { atmMIBGroups 14 } 3683 atmVpPvcCrossConnectGroup OBJECT-GROUP 3684 OBJECTS { atmVpCrossConnectAdminStatus, 3685 atmVpCrossConnectL2HOperStatus, 3686 atmVpCrossConnectH2LOperStatus, 3687 atmVpCrossConnectL2HLastChange, 3688 atmVpCrossConnectH2LLastChange, 3689 atmVpCrossConnectRowStatus, 3690 atmVplCrossConnectIdentifier, 3691 atmVpCrossConnectIndexNext } 3692 STATUS current 3693 DESCRIPTION 3694 "A collection of objects providing 3695 information about a VP cross-connect 3696 for PVCs. These objects are not used 3697 for Soft PVCs or SVCs." 3698 ::= { atmMIBGroups 15 } 3700 atmVclCrossConnectGroup OBJECT-GROUP 3701 OBJECTS { atmVclReceiveTrafficDescrIndex, 3702 atmVclTransmitTrafficDescrIndex, 3703 atmVclOperStatus, atmVclLastChange, 3704 atmVclRowStatus, 3705 atmVclCastType, atmVclConnKind } 3706 STATUS current 3708 draft ATM Management Objects August 15, 1998 3710 DESCRIPTION 3711 "A collection of objects providing 3712 information about the VCLs that 3713 are cross-connected together." 3714 ::= { atmMIBGroups 16 } 3716 atmVcPvcCrossConnectGroup OBJECT-GROUP 3717 OBJECTS { atmVcCrossConnectAdminStatus, 3718 atmVcCrossConnectL2HOperStatus, 3719 atmVcCrossConnectH2LOperStatus, 3720 atmVcCrossConnectL2HLastChange, 3721 atmVcCrossConnectH2LLastChange, 3722 atmVcCrossConnectRowStatus, 3723 atmVclCrossConnectIdentifier, 3724 atmVcCrossConnectIndexNext } 3725 STATUS current 3726 DESCRIPTION 3727 "A collection of objects providing 3728 information about a VC cross-connect 3729 for PVCs. These objects are not used 3730 for Soft PVCs or SVCs." 3731 ::= { atmMIBGroups 17 } 3733 draft ATM Management Objects August 15, 1998 3735 -- Deprecated Definitions - Objects 3737 -- atmInterfaceAddressType 3738 -- atmTrafficQoSClass 3740 -- Deprecated Definitions - Compliance 3742 atmMIBCompliance MODULE-COMPLIANCE 3743 STATUS deprecated 3744 DESCRIPTION 3745 "The compliance statement for SNMP entities 3746 including networks which have ATM and 3747 AAL5 interfaces." 3749 MODULE -- this module 3750 MANDATORY-GROUPS {atmInterfaceConfGroup, 3751 atmTrafficDescrGroup} 3753 OBJECT atmInterfaceMaxVpcs 3754 MIN-ACCESS read-only 3755 DESCRIPTION 3756 "Write access is not required." 3758 OBJECT atmInterfaceMaxVccs 3759 MIN-ACCESS read-only 3760 DESCRIPTION 3761 "Write access is not required." 3763 OBJECT atmInterfaceMaxActiveVpiBits 3764 MIN-ACCESS read-only 3765 DESCRIPTION 3766 "Write access is not required." 3768 OBJECT atmInterfaceMaxActiveVciBits 3769 MIN-ACCESS read-only 3770 DESCRIPTION 3771 "Write access is not required." 3773 OBJECT atmInterfaceIlmiVpi 3774 MIN-ACCESS read-only 3775 DESCRIPTION 3776 "Write access is not required." 3778 OBJECT atmInterfaceIlmiVci 3780 draft ATM Management Objects August 15, 1998 3782 MIN-ACCESS read-only 3783 DESCRIPTION 3784 "Write access is not required." 3786 OBJECT atmInterfaceMyNeighborIpAddress 3787 MIN-ACCESS read-only 3788 DESCRIPTION 3789 "Write access is not required." 3791 OBJECT atmInterfaceMyNeighborIfName 3792 MIN-ACCESS read-only 3793 DESCRIPTION 3794 "Write access is not required." 3796 OBJECT atmTrafficDescrType 3797 MIN-ACCESS read-only 3798 DESCRIPTION 3799 "Write access is not required." 3801 OBJECT atmTrafficDescrParam1 3802 MIN-ACCESS read-only 3803 DESCRIPTION 3804 "Write access is not required." 3806 OBJECT atmTrafficDescrParam2 3807 MIN-ACCESS read-only 3808 DESCRIPTION 3809 "Write access is not required." 3811 OBJECT atmTrafficDescrParam3 3812 MIN-ACCESS read-only 3813 DESCRIPTION 3814 "Write access is not required." 3816 OBJECT atmTrafficDescrParam4 3817 MIN-ACCESS read-only 3818 DESCRIPTION 3819 "Write access is not required." 3821 OBJECT atmTrafficDescrParam5 3822 MIN-ACCESS read-only 3823 DESCRIPTION 3824 "Write access is not required." 3826 OBJECT atmTrafficQoSClass 3828 draft ATM Management Objects August 15, 1998 3830 MIN-ACCESS read-only 3831 DESCRIPTION 3832 "Write access is not required." 3834 OBJECT atmTrafficDescrRowStatus 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)." 3844 GROUP atmInterfaceDs3PlcpGroup 3845 DESCRIPTION 3846 "This group is mandatory only for those 3847 ATM interfaces which implement the 3848 DS3 PLCP layer." 3850 GROUP atmInterfaceTCGroup 3851 DESCRIPTION 3852 "This group is mandatory only for those 3853 ATM interfaces which implement the 3854 TC Sublayer." 3856 GROUP atmVpcTerminationGroup 3857 DESCRIPTION 3858 "This group is mandatory only for those 3859 ATM interfaces which implement ATM 3860 VPLs that terminate VPCs (i.e., ones which 3861 are NOT cross-connected to other VPLs)." 3863 GROUP atmVpCrossConnectGroup 3864 DESCRIPTION 3865 "This group is mandatory only for those 3866 ATM interfaces which implement ATM 3867 VPLs that are not associated with VCLs 3868 and are cross-connected to other VPLs." 3870 OBJECT atmVplAdminStatus 3871 MIN-ACCESS read-only 3872 DESCRIPTION 3873 "Write access is not required." 3875 draft ATM Management Objects August 15, 1998 3877 OBJECT atmVplReceiveTrafficDescrIndex 3878 MIN-ACCESS read-only 3879 DESCRIPTION 3880 "Write access is not required." 3882 OBJECT atmVplTransmitTrafficDescrIndex 3883 MIN-ACCESS read-only 3884 DESCRIPTION 3885 "Write access is not required." 3887 OBJECT atmVplRowStatus 3888 SYNTAX INTEGER {active(1)} 3889 -- subset of RowStatus 3890 MIN-ACCESS read-only 3891 DESCRIPTION 3892 "Write access is not required, and only one 3893 of the six enumerated values for the 3894 RowStatus textual convention need be 3895 supported, specifically: active(1)." 3897 OBJECT atmVpCrossConnectAdminStatus 3898 MIN-ACCESS read-only 3899 DESCRIPTION 3900 "Write access is not required." 3902 OBJECT atmVpCrossConnectRowStatus 3903 SYNTAX INTEGER {active(1)} 3904 -- subset of RowStatus 3905 MIN-ACCESS read-only 3906 DESCRIPTION 3907 "Write access is not required, and only one 3908 of the six enumerated values for the 3909 RowStatus textual convention need be 3910 supported, specifically: active(1)." 3912 GROUP atmVccTerminationGroup 3913 DESCRIPTION 3914 "This group is mandatory only for those 3915 ATM interfaces which implement ATM 3916 VCLs that terminate VCCs (i.e., ones which 3917 are NOT cross-connected to other VCLs)." 3919 GROUP atmVcCrossConnectGroup 3920 DESCRIPTION 3921 "This group is mandatory only for those 3923 draft ATM Management Objects August 15, 1998 3925 ATM interfaces which implement ATM 3926 VCLs that are cross-connected to 3927 other VCLs." 3929 OBJECT atmVclAdminStatus 3930 MIN-ACCESS read-only 3931 DESCRIPTION 3932 "Write access is not required." 3934 OBJECT atmVclReceiveTrafficDescrIndex 3935 MIN-ACCESS read-only 3936 DESCRIPTION 3937 "Write access is not required." 3939 OBJECT atmVclTransmitTrafficDescrIndex 3940 MIN-ACCESS read-only 3941 DESCRIPTION 3942 "Write access is not required." 3944 OBJECT atmVccAalType 3945 MIN-ACCESS read-only 3946 DESCRIPTION 3947 "Write access is not required." 3949 OBJECT atmVclRowStatus 3950 SYNTAX INTEGER {active(1)} 3951 -- subset of RowStatus 3952 MIN-ACCESS read-only 3953 DESCRIPTION 3954 "Write access is not required, and only one 3955 of the six enumerated values for the 3956 RowStatus textual convention need be 3957 supported, specifically: active(1)." 3959 OBJECT atmVcCrossConnectAdminStatus 3960 MIN-ACCESS read-only 3961 DESCRIPTION 3962 "Write access is not required." 3964 OBJECT atmVcCrossConnectRowStatus 3965 SYNTAX INTEGER { active(1)} 3966 -- subset of RowStatus 3967 MIN-ACCESS read-only 3968 DESCRIPTION 3969 "Write access is not required, and only one 3971 draft ATM Management Objects August 15, 1998 3973 of the six enumerated values for the 3974 RowStatus textual convention need be 3975 supported, specifically: active(1)." 3977 GROUP aal5VccGroup 3978 DESCRIPTION 3979 "This group is mandatory for the 3980 AAL5 virtual connections only." 3982 OBJECT atmVccAal5CpcsTransmitSduSize 3983 MIN-ACCESS read-only 3984 DESCRIPTION 3985 "Write access is not required." 3987 OBJECT atmVccAal5CpcsReceiveSduSize 3988 MIN-ACCESS read-only 3989 DESCRIPTION 3990 "Write access is not required." 3992 OBJECT atmVccAal5EncapsType 3993 MIN-ACCESS read-only 3994 DESCRIPTION 3995 "Write access is not required." 3996 ::= { atmMIBCompliances 1 } 3998 -- Deprecated Definitions - Groups 4000 atmInterfaceConfGroup OBJECT-GROUP 4001 OBJECTS { 4002 atmInterfaceMaxVpcs, atmInterfaceMaxVccs, 4003 atmInterfaceConfVpcs, atmInterfaceConfVccs, 4004 atmInterfaceMaxActiveVpiBits, 4005 atmInterfaceMaxActiveVciBits, 4006 atmInterfaceIlmiVpi, 4007 atmInterfaceIlmiVci, 4008 atmInterfaceAddressType, 4009 atmInterfaceAdminAddress, 4010 atmInterfaceMyNeighborIpAddress, 4011 atmInterfaceMyNeighborIfName } 4012 STATUS deprecated 4013 DESCRIPTION 4014 "A collection of objects providing configuration 4015 information about an ATM interface." 4017 draft ATM Management Objects August 15, 1998 4019 ::= { atmMIBGroups 1 } 4021 atmTrafficDescrGroup OBJECT-GROUP 4022 OBJECTS { 4023 atmTrafficDescrType, atmTrafficDescrParam1, 4024 atmTrafficDescrParam2, atmTrafficDescrParam3, 4025 atmTrafficDescrParam4, atmTrafficDescrParam5, 4026 atmTrafficQoSClass, atmTrafficDescrRowStatus} 4027 STATUS deprecated 4028 DESCRIPTION 4029 "A collection of objects providing information 4030 about ATM traffic descriptor type and 4031 the associated parameters." 4032 ::= { atmMIBGroups 2 } 4034 atmVpcTerminationGroup OBJECT-GROUP 4035 OBJECTS {atmVplOperStatus, atmVplAdminStatus, 4036 atmVplLastChange, 4037 atmVplReceiveTrafficDescrIndex, 4038 atmVplTransmitTrafficDescrIndex, 4039 atmVplRowStatus } 4040 STATUS deprecated 4041 DESCRIPTION 4042 "A collection of objects providing 4043 information about a VPL at an ATM interface 4044 which terminates a VPC 4045 (i.e., one which is NOT cross-connected 4046 to other VPLs)." 4047 ::= { atmMIBGroups 5 } 4049 atmVccTerminationGroup OBJECT-GROUP 4050 OBJECTS {atmVclOperStatus, atmVclAdminStatus, 4051 atmVclLastChange, 4052 atmVclReceiveTrafficDescrIndex, 4053 atmVclTransmitTrafficDescrIndex, 4054 atmVccAalType, atmVclRowStatus } 4055 STATUS deprecated 4056 DESCRIPTION 4057 "A collection of objects providing information 4058 about a VCL at an ATM interface 4059 which terminates a VCC (i.e., one which is 4060 NOT cross-connected to other VCLs)." 4061 ::= { atmMIBGroups 6 } 4063 atmVpCrossConnectGroup OBJECT-GROUP 4065 draft ATM Management Objects August 15, 1998 4067 OBJECTS { atmVplReceiveTrafficDescrIndex, 4068 atmVplTransmitTrafficDescrIndex, 4069 atmVplOperStatus, atmVplRowStatus, 4070 atmVpCrossConnectAdminStatus, 4071 atmVpCrossConnectL2HOperStatus, 4072 atmVpCrossConnectH2LOperStatus, 4073 atmVpCrossConnectL2HLastChange, 4074 atmVpCrossConnectH2LLastChange, 4075 atmVpCrossConnectRowStatus, 4076 atmVplCrossConnectIdentifier, 4077 atmVpCrossConnectIndexNext } 4078 STATUS deprecated 4079 DESCRIPTION 4080 "A collection of objects providing 4081 information about a VP cross-connect 4082 and the associated VPLs that are 4083 cross-connected together." 4084 ::= { atmMIBGroups 7 } 4086 atmVcCrossConnectGroup OBJECT-GROUP 4087 OBJECTS { atmVclReceiveTrafficDescrIndex, 4088 atmVclTransmitTrafficDescrIndex, 4089 atmVclOperStatus, atmVclRowStatus, 4090 atmVcCrossConnectAdminStatus, 4091 atmVcCrossConnectL2HOperStatus, 4092 atmVcCrossConnectH2LOperStatus, 4093 atmVcCrossConnectL2HLastChange, 4094 atmVcCrossConnectH2LLastChange, 4095 atmVcCrossConnectRowStatus, 4096 atmVclCrossConnectIdentifier, 4097 atmVcCrossConnectIndexNext } 4098 STATUS deprecated 4099 DESCRIPTION 4100 "A collection of objects providing 4101 information about a VC cross-connect 4102 and the associated VCLs that are 4103 cross-connected together." 4104 ::= { atmMIBGroups 8 } 4106 -- {atmMIB 3} has been used by [19]. 4108 END 4110 draft ATM Management Objects August 15, 1998 4112 12. Acknowledgments 4114 This memo is the result of the work of the AToMMIB Working 4115 Group. 4117 draft ATM Management Objects August 15, 1998 4119 13. References 4121 [1] Harrington, D., Presuhn, R., and B. Wijnen, "An 4122 Architecture for Describing SNMP Management Frameworks", 4123 RFC 2271, Cabletron Systems, Inc., BMC Software, Inc., 4124 IBM T. J. Watson Research, January 1998 4126 [2] Rose, M., and K. McCloghrie, "Structure and 4127 Identification of Management Information for TCP/IP-based 4128 Internets", RFC 1155, Performance Systems International, 4129 Hughes LAN Systems, May 1990 4131 [3] Rose, M., and K. McCloghrie, "Concise MIB Definitions", 4132 RFC 1212, Performance Systems International, Hughes LAN 4133 Systems, March 1991 4135 [4] M. Rose, "A Convention for Defining Traps for use with 4136 the SNMP", RFC 1215, Performance Systems International, 4137 March 1991 4139 [5] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., 4140 and S. Waldbusser, "Structure of Management Information 4141 for Version 2 of the Simple Network Management Protocol 4142 (SNMPv2)", RFC 1902, SNMP Research,Inc., Cisco Systems, 4143 Inc., Dover Beach Consulting, Inc., International Network 4144 Services, January 1996. 4146 [6] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., 4147 and S. Waldbusser, "Textual Conventions for Version 2 of 4148 the Simple Network Management Protocol (SNMPv2)", RFC 4149 1903, SNMP Research, Inc., Cisco Systems, Inc., Dover 4150 Beach Consulting, Inc., International Network Services, 4151 January 1996. 4153 [7] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., 4154 and S. Waldbusser, "Conformance Statements for Version 2 4155 of the Simple Network Management Protocol (SNMPv2)", RFC 4156 1904, SNMP Research, Inc., Cisco Systems, Inc., Dover 4157 Beach Consulting, Inc., International Network Services, 4158 January 1996. 4160 [8] Case, J., Fedor, M., Schoffstall, M., and J. Davin, 4161 "Simple Network Management Protocol", RFC 1157, SNMP 4162 Research, Performance Systems International, Performance 4163 Systems International, MIT Laboratory for Computer 4165 draft ATM Management Objects August 15, 1998 4167 Science, May 1990. 4169 [9] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., 4170 and S. Waldbusser, "Introduction to Community-based 4171 SNMPv2", RFC 1901, SNMP Research, Inc., Cisco Systems, 4172 Inc., Dover Beach Consulting, Inc., International Network 4173 Services, January 1996. 4175 [10] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., 4176 and S. Waldbusser, "Transport Mappings for Version 2 of 4177 the Simple Network Management Protocol (SNMPv2)", RFC 4178 1906, SNMP Research, Inc., Cisco Systems, Inc., Dover 4179 Beach Consulting, Inc., International Network Services, 4180 January 1996. 4182 [11] Case, J., Harrington D., Presuhn R., and B. Wijnen, 4183 "Message Processing and Dispatching for the Simple 4184 Network Management Protocol (SNMP)", RFC 2272, SNMP 4185 Research, Inc., Cabletron Systems, Inc., BMC Software, 4186 Inc., IBM T. J. Watson Research, January 1998. 4188 [12] version 3 of the Simple Network Management Protocol 4189 (SNMPv3)", RFC 2274, IBM T. J. Watson Research, January 4190 1998. 4192 [13] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., 4193 and S. Waldbusser, "Protocol Operations for Version 2 of 4194 the Simple Network Management Protocol (SNMPv2)", RFC 4195 1905, SNMP Research, Inc., Cisco Systems, Inc., Dover 4196 Beach Consulting, Inc., International Network Services, 4197 January 1996. 4199 [14] Levi, D., Meyer, P., and B. Stewart, MPv3 Applications", 4200 RFC 2273, SNMP Research, Inc., Secure Computing 4201 Corporation, Cisco Systems, January 1998. 4203 [15] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based 4204 Access Control Model (VACM) for the Simple Network 4205 Management Protocol (SNMP)", RFC 2275, IBM T. J. Watson 4206 Research, BMC Software, Inc., Cisco Systems, Inc., 4207 January 1998. 4209 [16] McCloghrie, K., and M. Rose, Editors, "Management 4210 Information Base for Network Management of TCP/IP-based 4211 internets: MIB-II", STD 17, RFC 1213, Hughes LAN Systems, 4213 draft ATM Management Objects August 15, 1998 4215 Performance Systems International, March 1991. 4217 [17] McCloghrie, K. and F. Kastenholz, "The Interfaces Group 4218 MIB", RFC2233, cisco Systems, FTP Software, November 4219 1997. 4221 [18] Brown, T.A. and K. Tesink, "Definitions of Managed 4222 Objects for SMDS Interfaces", RFC 1694, Bellcore, May 4223 1994. 4225 [19] Michael Noto, Kaj Tesink, "ATM Textual Conventions and 4226 OBJECT-IDENTITIES", Internet-Draft, Bellcore, August 15, 4227 1998. 4229 [20] ATM Forum, ATM User-Network Interface, Version 3.0 (UNI 4230 3.0) Specification, 1994. 4232 [21] ATM Forum, B-ICI Specification, Version 2.0, af-bici- 4233 0013.002, November 1995. 4235 [22] "ATM Forum Private Network-Network Interface 4236 Specification, Version 1.0 (PNNI 1.0)", af-sig-0055.000, 4237 March 1996. 4239 [23] "ATM Forum Integrated Local Management Interface (ILMI) 4240 Specification", Version 4.0", af-ilmi-0065.000, September 4241 1996. 4243 draft ATM Management Objects August 15, 1998 4245 14. Security Considerations 4247 This MIB contains both readable objects whose values provide 4248 the number and status of a device's network interfaces, and 4249 write-able objects which allow an administrator to control the 4250 interfaces and to perform tests on the interfaces. 4251 Unauthorized access to the readable objects is relatively 4252 innocuous. Unauthorized access to the write- able objects 4253 could cause a denial of service, or in combination with other 4254 (e.g., physical) security breaches, could cause unauthorized 4255 connectivity to a device. 4257 15. Author's Address 4259 Kaj Tesink 4260 Bellcore 4261 331 Newman Springs Road 4262 P.O. Box 7020 4263 Red Bank, NJ 07701-7020 4264 Phone: (732) 758-5254 4265 EMail: kaj@cc.bellcore.com 4267 draft ATM Management Objects August 15, 1998 4269 16. Full Copyright Statement 4271 Copyright (C) The Internet Society (1998). All Rights 4272 Reserved. 4274 This document and translations of it may be copied and 4275 furnished to others, and derivative works that comment on or 4276 otherwise explain it or assist in its implementation may be 4277 prepared, copied, published and distributed, in whole or in 4278 part, without restriction of any kind, provided that the above 4279 copyright notice and this paragraph are included on all such 4280 copies and derivative works. However, this document itself 4281 may not be modified in any way, such as by removing the 4282 copyright notice or references to the Internet Society or 4283 other Internet organizations, except as needed for the purpose 4284 of developing Internet standards in which case the procedures 4285 for copyrights defined in the Internet Standards process must 4286 be followed, or as required to translate it into languages 4287 other than English. 4289 The limited permissions granted above are perpetual and will 4290 not be revoked by the Internet Society or its successors or 4291 assigns. 4293 This document and the information contained herein is provided 4294 on an "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET 4295 ENGINEERING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR 4296 IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE 4297 USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR 4298 ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A 4299 PARTICULAR PURPOSE." 4301 draft ATM Management Objects August 15, 1998 4303 Table of Contents 4305 1 Status of this Memo ................................... 1 4306 2 Introduction .......................................... 2 4307 3 The SNMP Network Management Framework ................. 2 4308 4 Object Definitions .................................... 4 4309 5 ATM Terminology ....................................... 5 4310 5.1 VCL/VPL and VCC/VPC ................................. 5 4311 5.2 PVC, SVC and Soft PVC ............................... 7 4312 5.3 Traffic Management Parameters ....................... 8 4313 5.3.1 Traffic Policing and Traffic Shaping Parameters 4314 .................................................... 8 4315 5.3.2 Cell Loss Priority ................................ 8 4316 5.3.3 QoS Class ......................................... 9 4317 5.3.4 Service Category .................................. 9 4318 5.4 Max Active and Max Current VPI and VCI Bits ......... 9 4319 6 Overview .............................................. 10 4320 6.1 Background .......................................... 11 4321 6.2 Structure of the MIB ................................ 11 4322 6.3 ATM Interface Configuration Table ................... 11 4323 6.4 ATM Interface DS3 PLCP and TC Layer Tables .......... 12 4324 6.5 ATM Virtual Link and Cross-Connect Tables ........... 12 4325 7 Application of MIB II to ATM .......................... 13 4326 7.1 The System Group .................................... 13 4327 7.2 The Interface Group ................................. 13 4328 7.2.1 Support of the ATM Cell Layer by ifTable .......... 13 4329 8 Support of the AAL3/4 Based Interfaces ................ 15 4330 9 Support of the AAL5 Managed Objects ................... 16 4331 9.1 Managing AAL5 in a Switch ........................... 16 4332 9.2 Managing AAL5 in a Host ............................. 17 4333 9.3 Support of AAL5 by ifTable .......................... 19 4334 9.4 Support of Proprietary Virtual Interface by ifT- 4335 able ............................................... 21 4336 9.5 AAL5 Connection Performance Statistics Table ........ 22 4337 10 ILMI MIBs and the ATM Managed Objects ................ 23 4338 11 Definitions .......................................... 26 4339 12 Acknowledgments ...................................... 97 4340 13 References ........................................... 98 4341 14 Security Considerations .............................. 101 4342 15 Author's Address ..................................... 101 4343 16 Full Copyright Statement ............................. 102