idnits 2.17.1 draft-ietf-atommib-atm1ng-04.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Cannot find the required boilerplate sections (Copyright, IPR, etc.) in this document. Expected boilerplate is as follows today (2024-04-19) according to https://trustee.ietf.org/license-info : IETF Trust Legal Provisions of 28-dec-2009, Section 6.a: This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79. IETF Trust Legal Provisions of 28-dec-2009, Section 6.b(i), paragraph 2: Copyright (c) 2024 IETF Trust and the persons identified as the document authors. All rights reserved. IETF Trust Legal Provisions of 28-dec-2009, Section 6.b(i), paragraph 3: This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. 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. ** 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 100 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 101 pages Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an Abstract section. ** 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 26 instances of too long lines in the document, the longest one being 13 characters in excess of 72. Miscellaneous warnings: ---------------------------------------------------------------------------- == Line 197 has weird spacing: '... |svc svc...' == Line 318 has weird spacing: '...pported supp...' == Line 1082 has weird spacing: '...rrently estab...' == Line 1102 has weird spacing: '...rrently estab...' == Line 1111 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 (April 4, 1998) is 9512 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? '1' on line 4068 looks like a reference -- Missing reference section? '2' on line 4073 looks like a reference -- Missing reference section? '3' on line 4078 looks like a reference -- Missing reference section? '4' on line 4084 looks like a reference -- Missing reference section? '7' on line 4097 looks like a reference -- Missing reference section? '8' on line 4103 looks like a reference -- Missing reference section? '11' on line 4114 looks like a reference -- Missing reference section? '5' on line 4089 looks like a reference -- Missing reference section? '9' on line 4106 looks like a reference -- Missing reference section? '6' on line 4093 looks like a reference -- Missing reference section? '10' on line 4109 looks like a reference -- Missing reference section? '12' on line 4118 looks like a reference Summary: 14 errors (**), 0 flaws (~~), 10 warnings (==), 13 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 April 4, 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 valid for a maximum of six months and may 23 be updated, replaced, or obsoleted by other documents at any 24 time. It is inappropriate to use Internet Drafts as reference 25 material or to cite them other than as a "work in progress". 27 draft ATM Management Objects April 4, 1998 29 2. Introduction 31 This memo defines an experimental portion of the Management 32 Information Base (MIB) for use with network management 33 protocols in the Internet community. In particular, it 34 describes objects used for managing ATM-based interfaces, 35 devices, networks and services. 37 This memo specifies a MIB module in a manner that is both 38 compliant to the SNMPv2 SMI, and semantically identical to the 39 peer SNMPv1 definitions. 41 This memo does not specify a standard for the Internet 42 community. 44 3. The SNMP Network Management Framework 46 The SNMP Network Management Framework consists of three major 47 components. They are: 49 0 RFC 1902 [1] which defines the SMI, the mechanisms used 50 for describing and naming objects for the purpose of 51 management. 53 0 STD 17, RFC 1213 [2] defines MIB-II, the core set of 54 managed objects for the Internet suite of protocols. 56 0 RFC 1157 [3] and RFC1905 [4] which define two versions of 57 the protocol used for network access to managed objects. 59 The Framework permits new objects to be defined for the 60 purpose of experimentation and evaluation. 62 Textual Conventions used in this MIB are defined in [7] and 63 [8]. 65 draft ATM Management Objects April 4, 1998 67 4. Object Definitions 69 Managed objects are accessed via a virtual information store, 70 termed the Management Information Base or MIB. Objects in the 71 MIB are defined using the subset of Abstract Syntax Notation 72 One (ASN.1) defined in the SMI. In particular, each object 73 type is named by an OBJECT IDENTIFIER, an administratively 74 assigned name. The object type together with an object 75 instance serves to uniquely identify a specific instantiation 76 of the object. For human convenience, we often use a textual 77 string, termed the descriptor, to also refer to the object 78 type. 80 draft ATM Management Objects April 4, 1998 82 5. ATM Terminology 84 Some basic ATM terminologies are described in this section to 85 facilitate defining the ATM managed objects. 87 5.1. VCL/VPL and VCC/VPC 89 There are two distinct types of ATM virtual connections: 90 Virtual Channel Connections (VCCs) and Virtual Path Connection 91 (VPCs). As shown in Figures 1 and 2, ATM virtual connections 92 consist of concatenated series of virtual links which forms a 93 path between two end points, with each concatenation occurring 94 at an ATM switch. Virtual links of VCCs are called Virtual 95 Channel Links (VCLs). Virtual links of VPCs are called Virtual 96 Path Links (VPLs). The VCI and VPI fields in the ATM cell 97 header associate each cell of a VCC with a particular VCL over 98 a given physical link. The VPI field in the ATM cell header 99 associates each cell of a VPC with a particular VPL over a 100 given physical link. Switches route cells between VCLs (or 101 VPLs) via a cross-connect function according to the cells' 102 VCI/VPI (or VPI) values. 104 <-----------------------VCC--------------------------> 105 ------------ ----------- 106 |ATM | |ATM | 107 |X-Connect | |X-Connect | 108 VCL1 |Point | VCL2 |Point | VCL3 109 O---------|----X-----|-------|-----|----X-----|-------O 110 | | | | 111 ------------ ------------ 112 ATM Switch ATM Switch 114 Figure 1: Virtual Channel Links and 115 Virtual Channel Connection 117 draft ATM Management Objects April 4, 1998 119 <-----------------------VPC--------------------------> 120 ------------ ----------- 121 |ATM | |ATM | 122 |X-Connect | |X-Connect | 123 VPL1 |Point | VPL2 |Point | VPL3 124 O---------|----X-----|-------|-----|----X-----|-------O 125 | | | | 126 ------------ ------------ 127 ATM Switch ATM Switch 129 Figure 2: Virtual Path Links and 130 Virtual Path Connection 132 A single ATM end-system or switch does not support the whole 133 end-to-end span of a VCC (or VPC). Rather, multiple ATM end- 134 systems and/or switches each support one piece of the VCC (or 135 VPC). That is, each ATM end-system (or ATM switch) at one end 136 of the VCC/VPC supports its end of the VCC/VPC plus the VCL or 137 VPL on its external interface, and each switch through which 138 the VCC/VPC passes supports the pair of VCLs/VPLs on its 139 external interfaces as well as the cross-connection of those 140 VCLs/VPLs. Thus, the end-to-end management of a VCC or VPC is 141 achieved only by appropriate management of its individual 142 pieces in combination. 144 Note that for management purposes, an ATM network may be 145 viewed as a large distributed switch by hiding all the 146 network's internal connectivity as being internal to the 147 distributed switch (as shown in Figure 2a). This model may 148 for example be used for Customer Network Management (CNM) 149 purposes. 151 draft ATM Management Objects April 4, 1998 153 <---------------------VCC---------------------------> 154 -------------------------------------- 155 | | 156 | ---------- ---------- | 157 | | ATM | | ATM | | 158 VCL1 | | Switch | | Switch | | VCL3 159 O-------|-|--------|------/-------|--------|-|------O 160 | | | | | | 161 | ---------- ---------- | 162 | | 163 | ATM Network | 164 -------------------------------------- 166 Figure 2a: ATM Network modeled as a large distributed 167 switch 169 A VCC has a set of traffic characteristics (i.e., bandwidth 170 parameters, service category parameters, etc.). VCLs inherit 171 their traffic characteristics from the VCC of which they are a 172 part. VCCs are bi-directional by definition. However, the 173 traffic parameters in the two directions of a connection can 174 be symmetric or asymmetric, i.e., the two directions can have 175 the same or different traffic flows. A uni-directional 176 traffic flow across a VCC is achieved by assigning a zero 177 bandwidth in one direction. Note that in addition to the 178 bandwidth required by the user traffic flow, bandwidth is also 179 required for OAM cell flows, even for the zero-bandwidth 180 direction of a uni-directional connection. These same 181 principles apply to VPCs. 183 5.2. PVC, SVC and Soft PVC 185 A Permanent Virtual Connection (PVC) is a provisioned VCC or 186 VPC. A Switched Virtual Connection (SVC) is a switched VCC or 187 VPC that is set up in real-time via call set-up signaling 188 procedures. A PVC (or an SVC) can be a point-to-point, 189 point-to-multipoint, or multipoint-to-multipoint VCC or VPC. 190 A Soft PVC is a connection of which portions are switched, 191 while other portions are permanent (see Figure 3 and [11]). 193 +--------+ +--------+ +--------+ 195 draft ATM Management Objects April 4, 1998 197 pvc| ATM |svc svc | ATM |svc svc | ATM |pvc 198 ----| Switch |-----------| Switch |-----------| Switch |---- 199 +--------+ +--------+ +--------+ 201 Figure 3: An example of a Soft PVC 203 5.3. Traffic Management Parameters 205 5.3.1. Traffic Policing and Traffic Shaping Parameters 207 In order to allocate resources fairly among different users, 208 some networks police traffic at resource access points. The 209 traffic enforcement or policing taken at a UNI is called Usage 210 Parameter Control (UPC) and is conceptually activated on an 211 incoming VCL or VPL as shown in Figure 4. The use of the 212 traffic enforcer at the ingress of the connection is to make 213 sure that the user traffic does not exceed the negotiated 214 traffic parameters such as the peak cell rate associated with 215 a specific traffic descriptor type. 217 ---------- ---------- 218 UNI | ATM | NNI | ATM | UNI 219 | | switch | | | switch | | 220 O<---|---->X(UPC) |<----|------>| (UPC)X<-----|--->O 221 | VCL | | | VCL | | VCL | 222 ---------- ---------- 224 Figure 4: An Example of a UPC 226 In addition, traffic shaping may be performed on an outgoing 227 VPL or VCL at a given ATM interface. The function of the ATM 228 traffic shaper, conceptually either at the source or an egress 229 point of the connection, is to smooth the outgoing cell 230 traffic inter-arrival time. If policing or shaping is not 231 performed then the policing or shaping algorithm is not 232 activated. 234 5.3.2. Cell Loss Priority 236 To prioritize traffic during resource congestion, ATM cells 237 are assigned one of the two types of Cell Loss Priority (CLP), 239 draft ATM Management Objects April 4, 1998 241 CLP=0 and CLP=1. ATM cells with CLP=0 have a higher priority 242 in regard to cell loss than ATM cells with CLP=1. Therefore, 243 during resource congestions, CLP=1 cells are dropped before 244 any CLP=0 cell is dropped. 246 5.3.3. QoS Class 248 RFC1695 specified that one of a number of Quality of Service 249 (QoS) classes is assigned to a VCC or VPC by associating the 250 object atmTrafficQoSClass with each VCL or VPL. However, new 251 insights in ATM traffic management have caused this object to 252 be deprecated. 254 5.3.4. Service Category 256 Replacing QoS Class, VPLs and VCLs are qualified in terms of 257 their service category (atmServiceCategory). When properly 258 configured, VCLs (or VPLs) concatenated to form a VCC (or VPC) 259 will all have the same service category class as that of the 260 VCC (or VPC). 262 5.4. Max Active and Max Current VPI and VCI Bits 264 A manager may wish to configure the maximum number of VPI and 265 VCI bits that can be used to identify VPIs and VCIs on a given 266 ATM interface. This value can be less than or equal to the 267 maximum number of bits supported by the interface hardware, 268 and is referred to in the MIB as the Max Active VPI Bits and 269 Max Active VCI Bits. 271 However, a manager may not be able to configure the Max Active 272 Bits on both ends of an ATM link. For example, the manager 273 may not be allowed write access to the peer's MIB, or there 274 may be hardware limitations on the peer device. Therefore, 275 the two ATM devices may use ILMI to negotiate "Max Current" 276 VPI and VCI bits, which is the maximum number of bits that 277 both interfaces are willing to support. This is illustrated 278 in Figure 5. The relationship between the different parameters 279 is illustrated in Figure 6. Note that if ILMI negotiation is 280 not supported, then the devices have no choice but to use the 281 configured Max Active bits, and assume that it has been 282 configured to the same value on both ends of the link. 284 draft ATM Management Objects April 4, 1998 286 +--------+ +--------+ +--------+ 287 | ATM | IF a IF b | ATM | IF c IF d | ATM | 288 | Device |--------------| Device |--------------| Device | 289 +--------+ +--------+ +--------+ 291 IF a: Max Active VPI Bits = 6 (configured) 292 Max Current VPI Bits = 6 (negotiated) 294 IF b: Max Active VPI Bits = 8 (configured) 295 Max Current VPI Bits = 6 (negotiated) 297 IF c: Max Active VPI Bits = 8 (configured) 298 Max Current VPI Bits = 8 (negotiated) 300 IF d: Max Active VPI Bits = 8 (configured) 301 Max Current VPI Bits = 8 (negotiated) 303 (between IF a and IF b, the minimum of the two configured 304 "Max Active VPI Bits" is 6, so both interfaces set their 305 "Max Current VPI Bits" to 6. Since IF c and IF d both 306 are configured with "Max Active VPI Bits" of 8, they 307 set their "Max Current VPI Bits" to 8.) 309 Figure 5 311 MSB LSB 312 +----------------------------------------------------+ 313 | | | | | 314 +----------------------------------------------------+ 315 ^ ^ ^ ^ 316 | | | | 317 Max bits Max Bits Max Max 318 supported supported Active (config.) current (negotiated) 319 by MIB by h/w Bits Bits 321 Figure 6 323 6. Overview 325 ATM management objects are used to manage ATM interfaces, ATM 326 virtual links, ATM cross-connects, AAL5 entities and AAL5 327 connections supported by ATM hosts, ATM switches and ATM 329 draft ATM Management Objects April 4, 1998 331 networks. This section provides an overview and background of 332 how to use this MIB and other potential MIBs for this purpose. 334 The purpose of this memo is primarily to manage ATM PVCs. ATM 335 SVCs are also represented by the management information in 336 this MIB. However, full management of SVCs may require 337 additional capabilities which are beyond the scope of this 338 memo. 340 6.1. Background 342 In addition to the MIB module defined in this memo, other MIB 343 modules are necessary to manage ATM interfaces, links and 344 cross-connects. Examples include MIB II for general system 345 and interface management [2][5], the DS3 or SONET MIBs for 346 management of physical interfaces, and, as appropriate, MIB 347 modules for applications that make use of ATM, such as SMDS. 348 These MIB modules are outside the scope of this specification. 350 The current specification of this ATM MIB is based on SNMPv2- 351 SMI. 353 6.2. Structure of the MIB 355 The managed ATM objects are arranged into the following 356 tables: 357 (1) ATM interface configuration table 358 (2) ATM interface DS3 PLCP and TC sublayer tables 359 (3) ATM traffic parameter table 360 (4) ATM interface virtual link (VPL/VCL) configuration 361 tables 362 (5) ATM VP/VC cross-connect tables 363 (6) AAL5 connection performance statistics table 365 Note that, managed objects for activation/deactivation of OAM 366 cell flows and ATM traps notifying virtual connection or 367 virtual link failures are outside the scope of this memo. 369 6.3. ATM Interface Configuration Table 371 This table contains information on ATM cell layer 372 configuration of local ATM interfaces on an ATM device in 373 addition to the information on such interfaces contained in 375 draft ATM Management Objects April 4, 1998 377 the ifTable. 379 6.4. ATM Interface DS3 PLCP and TC Layer Tables 381 These tables provide performance statistics of the DS3 PLCP 382 and TC sublayer of local ATM interfaces on a managed ATM 383 device. DS3 PLCP and TC sublayer are currently used to carry 384 ATM cells respectively over DS3 and SONET transmission paths. 386 6.5. ATM Virtual Link and Cross-Connect Tables 388 ATM virtual link and cross-connect tables model bi-directional 389 ATM virtual links and ATM cross-connects. The ATM VP/VC link 390 tables are implemented in an ATM host, ATM switch and ATM 391 network. The ATM switch and ATM network also implement the 392 ATM VP/VC cross-connect tables. Both link and cross-connect 393 tables are implemented in a carrier's network for Customer 394 Network Management (CNM) purposes. 396 The ATM virtual link tables are used to create, delete or 397 modify ATM virtual links in an ATM host, ATM switch and ATM 398 network. ATM virtual link tables along with the cross-connect 399 tables are used to create, delete or modify ATM cross-connects 400 in an ATM switch or ATM network (e.g., for CNM purposes). 402 For a PVC, the cross-connect between two VPLs is represented 403 in the atmVpCrossConnectTable of the ATM-MIB, indexed by the 404 atmVplCrossConnectIdentifier values for the two VPLs, and the 405 cross-connect between two VCLs is represented in the 406 atmVcCrossConnectTable of the ATM-MIB, indexed by the 407 atmVclCrossConnectIdentifier values for the two VCLs. 409 For an SVC or Soft PVC the VPL and VCL tables defined in this 410 memo are used. Hoewever, for an SVC or Soft PVC the cross- 411 connect between two VPLs is represented in the 412 atmSvcVpCrossConnectTable of the ATM2-MIB, indexed by the 413 atmVplCrossConnectIdentifier values for the two VPLs, and the 414 cross-connect between two VCLs is represented in the 415 atmSvcVcCrossConnectTable of the ATM2-MIB, indexed by the 416 atmVclCrossConnectIdentifier values for the two VCLs. 418 Note: The ATM2-MIB module was being defined in a separate memo 419 at the time of this publication. Please consult the RFC 421 draft ATM Management Objects April 4, 1998 423 directory for an exact reference. 425 7. Application of MIB II to ATM 427 7.1. The System Group 429 For the purposes of the sysServices object in the System Group 430 of MIB II [2], ATM is a data link layer protocol. Thus, for 431 ATM switches and ATM networks, sysServices will have the value 432 "2". 434 7.2. The Interface Group 436 The Interfaces Group of MIB II defines generic managed objects 437 for managing interfaces. This memo contains the media- 438 specific extensions to the Interfaces Group for managing ATM 439 interfaces. 441 This memo assumes the interpretation of the Interfaces Group 442 to be in accordance with [5] which states that the interfaces 443 table (ifTable) contains information on the managed resource's 444 interfaces and that each sub-layer below the internetwork 445 layer of a network interface is considered an interface. 446 Thus, the ATM cell layer interface is represented as an entry 447 in the ifTable. This entry is concerned with the ATM cell 448 layer as a whole, and not with individual virtual connections 449 which are managed via the ATM-specific managed objects 450 specified in this memo. The inter-relation of entries in the 451 ifTable is defined by Interfaces Stack Group defined in [5]. 453 7.2.1. Support of the ATM Cell Layer by ifTable 455 Some specific interpretations of ifTable for the ATM cell 456 layer follow. 458 draft ATM Management Objects April 4, 1998 460 Object Use for the generic ATM layer 461 ====== ============================= 463 ifIndex Each ATM port is represented by an ifEntry. 465 ifDescr Description of the ATM interface. 467 ifType The value that is allocated for ATM is 37. 469 ifSpeed The total bandwidth in bits per second 470 for use by the ATM layer. 472 ifPhysAddress The interface's address at the ATM protocol 473 sublayer; the ATM address which would be used 474 as the value of the Called Party Address 475 Information Element (IE) of a signalling 476 message for a connection which either: 477 - would terminate at this interface, or 478 - for which the Called Party Address IE 479 would need to be replaced by the Called 480 Party SubAddress IE before the message 481 was forwarded to any other interface. 482 For an interface on which signalling is 483 not supported, then the interface does not 484 necessarily have an address, but if it 485 does, then ifPhysAddress is the address which 486 would be used as above in the event that 487 signalling were supported. If the interface 488 has multiple such addresses, then ifPhysAddress 489 is its primary address. If the interface has 490 no addresses, then ifPhysAddress is an octet 491 string of zero length. Address encoding is as 492 per [9]. Note that addresses assigned for 493 purposes other than those listed above (e.g., 494 an address associated with the service provider 495 side of a public network UNI) may be represented 496 through atmInterfaceSubscrAddress. 498 ifAdminStatus See [5]. 500 ifOperStatus Assumes the value down(2) if the ATM cell 501 layer is down. 503 ifLastChange See [5]. 505 draft ATM Management Objects April 4, 1998 507 ifInOctets The number of received octets over the 508 interface, i.e., the number of received, 509 assigned cells multiplied by 53. 511 ifOutOctets The number of transmitted octets over the 512 interface, i.e., the number of transmitted, 513 assigned cells multiplied by 53. 515 ifInErrors The number of cells dropped due to 516 uncorrectable HEC errors. 518 ifInUnknownProtos The number of received cells discarded 519 during cell header validation, including 520 cells with unrecognized VPI/VCI values, 521 and cells with invalid cell header patterns. 522 If cells with undefined PTI values are discarded, 523 they are also counted here. 525 ifOutErrors See [5]. 527 ifName Textual name (unique on this system) of the 528 interface or an octet string of zero length. 530 ifLinkUpDownTrapEnable Default is disabled (2). 532 ifConnectorPresent Set to false (2). 534 ifHighSpeed See [5]. 536 ifHCInOctets The 64-bit version of ifInOctets; supported 537 if required by the compliance statements in [5]. 539 ifHCOutOctets The 64-bit version of ifOutOctets; supported 540 if required by the compliance statements in [5]. 542 ifAlias The non-volatile 'alias' name for the interface 543 as specified by a network manager. 545 8. Support of the AAL3/4 Based Interfaces 547 For the management of AAL3/4 CPCS layer, see [6]. 549 draft ATM Management Objects April 4, 1998 551 9. Support of the AAL5 Managed Objects 553 Support of AAL5 managed objects in an ATM switch and ATM host 554 are described below. 556 9.1. Managing AAL5 in a Switch 558 Managing AAL5 in a switch involves: 560 (1) performance management of an AAL5 entity as 561 an internal resource in a switch 563 (2) performance management of AAL5 per virtual connection 565 AAL5 in a switch is modeled as shown in Figure 7 and 8. AAL5 566 will be managed in a switch for only those virtual connections 567 that carry AAL5 and are terminated at the AAL5 entity in the 568 switch. Note that, the virtual channels within the ATM UNIs 569 carrying AAL5 will be switched by the ATM switching fabric 570 (termed as ATM Entity in the figure) to the virtual channels 571 on a proprietary internal interface associated with the AAL5 572 process (termed as AAL5 Entity in the figure). Therefore, 573 performance management of the AAL5 resource in the switch will 574 be modeled using the ifTable through an internal (pseudo-ATM) 575 virtual interface and the AAL5 performance management per 576 virtual connection will be supported using an additional AAL5 577 connection table in the ATM MIB. The association between the 578 AAL5 virtual link at the proprietary virtual, internal 579 interface and the ATM virtual link at the ATM interface will 580 be derived from the virtual channel cross-connect table and 581 the virtual channel link table in the ATM MIB. Note that for 582 the proprietary virtual interface the traffic transmit and 583 receive conventions in the virtual channel link table are as 584 follows: 586 Transmitting traffic: ATM Entity ---> AAL5 Entity 587 Receiving traffic: ATM Entity <--- AAL5 Entity 589 draft ATM Management Objects April 4, 1998 591 ___________________________ 592 | | 593 | ============= | 594 | | AAL5 | | 595 | | Entity | | 596 | ============= | 597 | | | 598 | -----Prop. Virtual Interface 599 | | | 600 | ============= | 601 | | ATM | | 602 | | Entity | | 603 | ============= | 604 |_____|__|__|__|__|_______| 605 | | | | | 606 ---------------- ATM UNIs 607 | | | | | 608 | | | | | 609 v v v v v 611 Figure 7: Model of an AAL5 Entity in a Switch 613 __________________ 614 | | 615 | AAL5 | 616 |________________| 617 | | 618 | Prop. Virtual | 619 | Interface | 620 |________________| 622 Figure 8: AAL5 Entity's Interface Stack in a Switch 624 9.2. Managing AAL5 in a Host 626 Managing AAL5 in a host involves managing the AAL5 sublayer 627 interface as shown in Figure 9 and 10. The AAL5 sublayer is 628 stacked directly over the ATM sublayer. The ifTable is 629 applied to the AAL5 sublayer as defined in Section 10.3. 631 draft ATM Management Objects April 4, 1998 633 ___________________________ 634 | | 635 | ============= | 636 | | AAL5 | | 637 | | Entity | | 638 | ============= | 639 | | ATM | | 640 | | Entity | | 641 | ============= | 642 |___________|_____________| 643 | 644 __|__ ATM UNI 645 | 646 | 647 v 649 Figure 9: Model of an AAL5 Entity in a Host 651 __________________ 652 | | 653 | AAL5 | 654 |________________| 655 | | 656 | ATM Layer | 657 |________________| 658 | | 659 | Physical Layer| 660 |________________| 662 Figure 10: AAL5 Entity's Interface Stack in a Host 664 draft ATM Management Objects April 4, 1998 666 9.3. Support of AAL5 by ifTable 668 The AAL5 entity in an ATM device (e.g., switch or host) is 669 managed using the ifTable. There are additional counters 670 specified for AAL5 than those specified in the ATM B-ICI 671 document [10]. Specific interpretations of ifTable for the 672 AAL5 CPCS layer are as follows. 674 Object Use for AAL5 CPCS layer entity 675 ====== ============================== 677 ifIndex Each AAL5 entity is represented by an ifEntry. 679 ifDescr Description of the AAL5 entity. 681 ifType The value that is allocated for AAL5 is 49. 683 ifMtu Set to the largest PDU size for the 684 AAL5 CPCS layer that can be processed 685 by the AAL5 entity. 687 ifSpeed Set to 0. 689 ifPhysAddress An octet string of zero length. 691 ifAdminStatus See [5]. 693 ifOperStatus Assumes the value down(2) if the AAL5 694 layer is down. 696 ifLastChange See [5]. 698 ifInOctets The number of received AAL5 CPCS PDU octets. 700 ifOutOctets The number of AAL5 CPCS PDU octets 701 transmitted. 703 ifInUcastPkts The number of received AAL5 CPCS PDUs passed 704 to a higher-layer. 706 ifOutUcastPkts The number of AAL5 CPCS PDUs received from a 707 higher-layer for transmission. 708 [Note: The number of AAL5 PDUs actually 709 transmitted is the number received from a 710 higher-layer for transmission minus any which 712 draft ATM Management Objects April 4, 1998 714 are counted by ifOutErrors and ifOutDiscards.] 716 ifInErrors Number of errored AAL5 CPCS PDUs received. 717 The types of errors counted include CRC-32 errors, 718 SAR time-out errors, and oversized SDU errors. 720 ifInUnknownProtos Set to 0. 722 ifInDiscards Number of received AAL5 CPCS PDUs discarded. 723 Possible reason may be input buffer overflow. 725 ifOutErrors Number of AAL5 CPCS PDUs that could not 726 be transmitted due to errors. 728 ifOutDiscards Number of AAL5 CPCS PDUs received for 729 transmission that are discarded. 730 Possible reason may be output buffer 731 overflow. 733 ifInMulticastPkts Set to 0. 735 ifInBroadcastPkts Set to 0. 737 ifOutMulticastPkts Set to 0. 739 ifOutBroadcastPkts Set to 0. 741 ifName Textual name (unique on this system) of the 742 AAL5 entity or an octet string of zero length. 744 ifHighSpeed Set to 0. 746 ifConnectorPresent Set to false (2). 748 ifPromiscuousMode Set to false(2). 750 ifLinkUpDownTrapEnable Default is disabled (2). 752 ifAlias The non-volatile 'alias' name for the interface 753 as specified by a network manager. 755 draft ATM Management Objects April 4, 1998 757 9.4. Support of Proprietary Virtual Interface by ifTable 759 Specific interpretations of ifTable for the proprietary 760 virtual, internal interface associated with an AAL5 entity in 761 an ATM switch are as follows. 763 draft ATM Management Objects April 4, 1998 765 Object Use for proprietary virtual, internal interface 766 associated with AAL entities 767 ====== =============================================== 769 ifIndex Each proprietary virtual, internal interface 770 associated with AAL entities is represented by an 771 ifEntry. 773 ifDescr Description of the proprietary virtual, internal 774 interface associated with AAL entities. 776 ifType The value that is allocated for proprietary 777 virtual, internal interface is 53. 779 ifSpeed See [5]. Set to 0 if the speed is not 780 known. 782 ifPhysAddress See [5]. An octet string of zero length 783 if no address is used for this interface. 785 ifAdminStatus See [5]. 787 ifOperStatus See [5]. 789 ifLastChange See [5]. 791 ifName Textual name (unique on this system) of the 792 interface or an octet string of zero length. 794 ifHighSpeed See [5]. Set to 0 if the speed is not known. 796 ifConnectorPresent Set to false (2). 798 ifLinkUpDownTrapEnable Default is disabled (2). 800 ifAlias The non-volatile 'alias' name for the interface 801 as specified by a network manager. 803 9.5. AAL5 Connection Performance Statistics Table 805 An AAL5 connection table is used to provide AAL5 performance 806 information for each AAL5 virtual connection that is 807 terminated at the AAL5 entity contained within an ATM switch 808 or host. 810 draft ATM Management Objects April 4, 1998 812 10. ILMI MIBs and the ATM Managed Objects 814 The ILMI MIBs are specified by the ATM Forum as a set of 815 several MIBs, all currently defined in the ILMI Specification 816 [12]. The ILMI protocols and MIBs allow two connected ATM 817 Interface Management Entities (IMEs) to exchange bi- 818 directional parameters, mainly to facilitate auto- 819 configuration between ATM peer entities. The support of the 820 ATM management functions by the ILMI MIBs and those contained 821 in this memo are compared in Table 1. In this table, "yes" in 822 the "ILMI MIBs" column indicates that the management 823 functions are supported by the ILMI MIBs. The parenticed 824 numberss in the "This memo" column correspond to the sets of 825 tables enumeratedg in Section 7.2. 827 For that subset of management information which the ILMI MIBs 828 and this memo have in common, every effort has been made to 829 retain identical semantics and syntax, even though the MIB 830 objects are identified using different OBJECT IDENTIFIERs. 832 draft ATM Management Objects April 4, 1998 834 Table 1 - Structuring of ATM Managed Objects 836 ______________________________________________________________ 837 | |This |ILMI| 838 ATM Mgmt.Inf. |ATM Managed Objects |memo |MIBs| 839 ______________|_________________________________|_______|____| 841 Local Interface Information: 842 _____________________________________________________________ 843 ATM interface:| (1) port identifier |ATM MIB| | 844 physical layer| (2) physical transmission types | (1)*|yes | 845 configuration | (3) operational status |MIB II | * | 846 | (4) administrative status | | ** | 847 | (5) last change status | | | 848 _____________________________________________________________ 849 ATM interface:| (1) active VPI/VCI fields |ATM MIB| | 850 cell layer | (2) maximum number of VPCs/VCCs | (1) |yes | 851 configuration | (3) configured VPCs/VCCs | | ** | 852 | (4) ILMI VPI/VCI values | | | 853 | (5) Neighbor system info | | | 854 | (6) Max. number of VPI/VCI bits | |yes | 855 | (7) ATM Subscribed Address | | | 856 _____________________________________________________________ 857 ATM interface:|(1) received/transmitted cells | | | 858 cell layer |(2) cells with HEC error |MIB II |yes | 859 performance |(3) cell header validation errors| | | 860 _____________________________________________________________ 861 ATM interface:|(1)DS3 PLCP severely errored |ATM MIB| | 862 PLCP & TC | framing seconds | (2)| | 863 layer |(2)DS3 PLCP unavailable seconds | |no | 864 performance |(3)DS3 PLCP alarm state | | | 865 |(4)out of cell delineation events| | | 866 |(5)TC alarm state | | | 867 _____________________________________________________________ 868 VP/VC link: |(1)VPI or VPI/VCI value |ATM MIB| | 869 configuration |(2)VCL or VPL operational status | (3,4)|yes | 870 |(3)VCL/VPL administrative status | |*** | 871 |(4)VCL/VPL last change status | | | 872 |(5)transmit/receive traffic/ | | | 873 | service category parameters | | | 874 |(6)AAL type | | | 875 |(7)transmit/receive AAL5 SDU size| | | 876 |(8)AAL5 encapsulation type | | | 877 |(9)connection topology type | | | 878 |(10)use of call control | | | 880 draft ATM Management Objects April 4, 1998 882 _____________________________________________________________ 884 draft ATM Management Objects April 4, 1998 886 _____________________________________________________________ 887 VP/VC |(1)cross-connect identifier | | | 888 Cross-connect:|(2)port identifier of one | | | 889 configuration | end | | | 890 |(3)port identifier of the other |ATM MIB| | 891 | end | (5)|no | 892 |(4)VPI or VPI/VCI value | | | 893 | of one end | | | 894 |(5)VPI or VPI/VCI value of | | | 895 | the other end | | | 896 |(6)VC/VP cross-connect | | | 897 | operational status | | | 898 |(7)VC/VP cross-connect | | | 899 | administrative status | | | 900 |(8)VC/VP last change status | | | 901 _____________________________________________________________ 902 VCC AAL5 CPCS |(1)PDUs discarded for CRC errors |ATM MIB| | 903 layer: |(2)PDUs discarded due to | (6) | | 904 performance | reassembly time out | |no | 905 |(3)PDUs discarded due to large | | | 906 | SDUs | | | 907 _____________________________________________________________ 908 AAL5 entity: |(1)received/transmitted PDUs | | | 909 |(2)PDUs discarded due to | | | 910 | protocol errors |MIB II |no | 911 |(3)a set of configuration/state | | | 912 | parameters | | | 913 _____________________________________________________________ 915 *The operational, administrative, and last change status of 916 the ATM interface and the physical transmission type shall be 917 supported by the interface table in MIB II [2][5]. ILMI does 918 not contain the administrative and last change status of the 919 ATM interface. 921 ** The ILMI MIB contains read-only objects for various 922 parameters at the ATM interface level. 924 ***The ILMI MIBs contain local and end-to-end operational 925 status of the VPC/VCC segment. However, it does not contain 926 the VPC/VCC administrative and last change status and the VCC 927 AAL information. 929 draft ATM Management Objects April 4, 1998 931 11. Definitions 933 ATM-MIB DEFINITIONS ::= BEGIN 935 IMPORTS 936 MODULE-IDENTITY, OBJECT-TYPE, 937 experimental, Counter32, Integer32, IpAddress, mib-2 938 FROM SNMPv2-SMI 939 DisplayString, RowStatus, TruthValue 940 FROM SNMPv2-TC 941 MODULE-COMPLIANCE, OBJECT-GROUP 942 FROM SNMPv2-CONF 943 InterfaceIndex, ifIndex 944 FROM IF-MIB 945 AtmAddr, AtmConnKind, AtmConnCastType, 946 AtmServiceCategory, AtmTrafficDescrParamIndex, 947 AtmVpIdentifier, AtmVcIdentifier, 948 AtmVorXAdminStatus, AtmVorXLastChange, 949 AtmVorXOperStatus, atmNoClpNoScr 950 FROM ATM-TC-MIB; 952 atmMIB MODULE-IDENTITY 953 LAST-UPDATED "9804041200Z" 954 ORGANIZATION "IETF AToM MIB Working Group" 955 CONTACT-INFO 956 " Kaj Tesink 957 Postal: Bellcore 958 331 Newman Springs Road 959 Red Bank, NJ 07701 960 Tel: 908-758-5254 961 Fax: 908-758-2269 962 E-mail: kaj@cc.bellcore.com" 963 DESCRIPTION 964 "This is the MIB Module for ATM and AAL5-related 965 objects for managing ATM interfaces, ATM virtual 966 links, ATM cross-connects, AAL5 entities, and 967 and AAL5 connections." 968 REVISION "9406072245Z" 969 DESCRIPTION 970 "The initial revision of this module was published as RFC 1695." 971 ::= { experimental 41 } 973 -- **************************************** 974 -- * Note to RFC editor * 976 draft ATM Management Objects April 4, 1998 978 -- * Replace {experimental 41} with * 979 -- * { mib-2 37 } when publishing this * 980 -- * MIB as RFC * 981 -- **************************************** 983 atmMIBObjects OBJECT IDENTIFIER ::= {atmMIB 1} 985 -- {atmMIBObjects 1} has been moved to a separate 986 -- specification [8]. 988 draft ATM Management Objects April 4, 1998 990 -- This ATM MIB Module consists of the following tables: 991 -- (1) ATM Interface configuration table 992 -- (2) ATM Interface DS3 PLCP table 993 -- (3) ATM Interface TC Sublayer table 994 -- (4) Atm Traffic Descriptor table 995 -- (5) ATM Interface VPL configuration table 996 -- (6) ATM Interface VCL configuration table 997 -- (7) ATM VP Cross Connect table (for PVCs) 998 -- (8) ATM VC Cross Connect table (for PVCs) 999 -- (9) ATM Interface AAL5 VCC performance statistics 1000 -- table 1002 draft ATM Management Objects April 4, 1998 1004 -- ATM Interface Configuration Parameters Table 1006 -- This table contains ATM specific 1007 -- configuration information associated with 1008 -- an ATM interface beyond those 1009 -- supported using the ifTable. 1011 atmInterfaceConfTable OBJECT-TYPE 1012 SYNTAX SEQUENCE OF AtmInterfaceConfEntry 1013 MAX-ACCESS not-accessible 1014 STATUS current 1015 DESCRIPTION 1016 "This table contains ATM local interface 1017 configuration parameters, one entry per ATM 1018 interface port." 1019 ::= { atmMIBObjects 2 } 1021 atmInterfaceConfEntry OBJECT-TYPE 1022 SYNTAX AtmInterfaceConfEntry 1023 MAX-ACCESS not-accessible 1024 STATUS current 1025 DESCRIPTION 1026 "This list contains ATM interface configuration 1027 parameters and state variables and is indexed 1028 by ifIndex values of ATM interfaces." 1029 INDEX { ifIndex } 1030 ::= { atmInterfaceConfTable 1} 1032 AtmInterfaceConfEntry ::= SEQUENCE { 1033 atmInterfaceMaxVpcs INTEGER, 1034 atmInterfaceMaxVccs INTEGER, 1035 atmInterfaceConfVpcs INTEGER, 1036 atmInterfaceConfVccs INTEGER, 1037 atmInterfaceMaxActiveVpiBits INTEGER, 1038 atmInterfaceMaxActiveVciBits INTEGER, 1039 atmInterfaceIlmiVpi AtmVpIdentifier, 1040 atmInterfaceIlmiVci AtmVcIdentifier, 1041 atmInterfaceAddressType INTEGER, 1042 atmInterfaceAdminAddress AtmAddr, 1043 atmInterfaceMyNeighborIpAddress IpAddress, 1044 atmInterfaceMyNeighborIfName DisplayString, 1045 atmInterfaceCurrentMaxVpiBits INTEGER, 1047 draft ATM Management Objects April 4, 1998 1049 atmInterfaceCurrentMaxVciBits INTEGER, 1050 atmInterfaceSubscrAddress AtmAddr 1051 } 1053 atmInterfaceMaxVpcs OBJECT-TYPE 1054 SYNTAX INTEGER (0..4096) 1055 MAX-ACCESS read-write 1056 STATUS current 1057 DESCRIPTION 1058 "The maximum number of VPCs (PVPCs and SVPCs) 1059 supported at this ATM interface. At the ATM UNI, 1060 the maximum number of VPCs (PVPCs and SVPCs) 1061 ranges from 0 to 256 only." 1062 ::= { atmInterfaceConfEntry 1} 1064 atmInterfaceMaxVccs OBJECT-TYPE 1065 SYNTAX INTEGER (0..65536) 1066 MAX-ACCESS read-write 1067 STATUS current 1068 DESCRIPTION 1069 "The maximum number of VCCs (PVCCs and SVCCs) 1070 supported at this ATM interface." 1071 ::= { atmInterfaceConfEntry 2} 1073 atmInterfaceConfVpcs OBJECT-TYPE 1074 SYNTAX INTEGER (0..4096) 1075 MAX-ACCESS read-only 1076 STATUS current 1077 DESCRIPTION 1078 "The number of VPCs (PVPC, Soft PVPC and SVPC) 1079 currently in use at this ATM interface. It includes 1080 the number of PVPCs and Soft PVPCs that are configured 1081 at the interface, plus the number of SVPCs 1082 that are currently established at the 1083 interface. 1085 At the ATM UNI, the configured number of 1086 VPCs (PVPCs and SVPCs) can range from 1087 0 to 256 only." 1088 ::= { atmInterfaceConfEntry 3} 1090 atmInterfaceConfVccs OBJECT-TYPE 1091 SYNTAX INTEGER (0..65536) 1092 MAX-ACCESS read-only 1094 draft ATM Management Objects April 4, 1998 1096 STATUS current 1097 DESCRIPTION 1098 "The number of VCCs (PVCC, Soft PVCC and SVCC) 1099 currently in use at this ATM interface. It includes 1100 the number of PVCCs and Soft PVCCs that are configured 1101 at the interface, plus the number of SVCCs 1102 that are currently established at the 1103 interface." 1104 ::= { atmInterfaceConfEntry 4} 1106 atmInterfaceMaxActiveVpiBits OBJECT-TYPE 1107 SYNTAX INTEGER (0..12) 1108 MAX-ACCESS read-write 1109 STATUS current 1110 DESCRIPTION 1111 "The maximum number of active VPI bits 1112 configured for use at the ATM interface. 1113 At the ATM UNI, the maximum number of active 1114 VPI bits configured for use ranges from 1115 0 to 8 only." 1116 ::= { atmInterfaceConfEntry 5} 1118 atmInterfaceMaxActiveVciBits OBJECT-TYPE 1119 SYNTAX INTEGER (0..16) 1120 MAX-ACCESS read-write 1121 STATUS current 1122 DESCRIPTION 1123 "The maximum number of active VCI bits 1124 configured for use at this ATM interface." 1125 ::= { atmInterfaceConfEntry 6} 1127 atmInterfaceIlmiVpi OBJECT-TYPE 1128 SYNTAX AtmVpIdentifier 1129 MAX-ACCESS read-write 1130 STATUS current 1131 DESCRIPTION 1132 "The VPI value of the VCC supporting 1133 the ILMI at this ATM interface. If the values of 1134 atmInterfaceIlmiVpi and atmInterfaceIlmiVci are 1135 both equal to zero then the ILMI is not 1136 supported at this ATM interface." 1137 DEFVAL { 0 } 1138 ::= { atmInterfaceConfEntry 7} 1140 atmInterfaceIlmiVci OBJECT-TYPE 1142 draft ATM Management Objects April 4, 1998 1144 SYNTAX AtmVcIdentifier 1145 MAX-ACCESS read-write 1146 STATUS current 1147 DESCRIPTION 1148 "The VCI value of the VCC supporting 1149 the ILMI at this ATM interface. If the values of 1150 atmInterfaceIlmiVpi and atmInterfaceIlmiVci are 1151 both equal to zero then the ILMI is not 1152 supported at this ATM interface." 1153 DEFVAL { 16 } 1154 ::= { atmInterfaceConfEntry 8} 1156 atmInterfaceAddressType OBJECT-TYPE 1157 SYNTAX INTEGER { 1158 private(1), 1159 nsapE164(2), 1160 nativeE164(3), 1161 other(4) 1162 } 1163 MAX-ACCESS read-only 1164 STATUS deprecated 1165 DESCRIPTION 1166 "The type of primary ATM address configured 1167 for use at this ATM interface." 1168 ::= { atmInterfaceConfEntry 9 } 1170 -- The atmInterfaceAdminAddress object has been replaced by 1171 -- atmInterfaceSubscrAddress. 1173 atmInterfaceAdminAddress OBJECT-TYPE 1174 SYNTAX AtmAddr 1175 MAX-ACCESS read-only 1176 STATUS deprecated 1177 DESCRIPTION 1178 "The primary address assigned for administrative purposes, 1179 for example, an address associated with the 1180 service provider side of a public network UNI 1181 (thus, the value of this address corresponds 1182 with the value of ifPhysAddress at the host side). 1183 If this interface has no assigned administrative 1184 address, or when the address used for 1185 administrative purposes is the same as that used 1186 for ifPhysAddress, then this is an octet string of 1187 zero length." 1188 ::= { atmInterfaceConfEntry 10 } 1190 draft ATM Management Objects April 4, 1998 1192 atmInterfaceMyNeighborIpAddress OBJECT-TYPE 1193 SYNTAX IpAddress 1194 MAX-ACCESS read-write 1195 STATUS current 1196 DESCRIPTION 1197 "The IP address of the neighbor system connected to 1198 the far end of this interface, to which a Network 1199 Management Station can send SNMP messages, as IP 1200 datagrams sent to UDP port 161, in order to access 1201 network management information concerning the 1202 operation of that system. Note that the value 1203 of this object may be obtained in different ways, 1204 e.g., by manual configuration, or through ILMI 1205 interaction with the neighbor system." 1206 ::= { atmInterfaceConfEntry 11 } 1208 atmInterfaceMyNeighborIfName OBJECT-TYPE 1209 SYNTAX DisplayString 1210 MAX-ACCESS read-write 1211 STATUS current 1212 DESCRIPTION 1213 "The textual name of the interface on the neighbor 1214 system on the far end of this interface, and to 1215 which this interface connects. If the neighbor 1216 system is manageable through SNMP and supports 1217 the object ifName, the value of this object must 1218 be identical with that of ifName for the ifEntry 1219 of the lowest level physical interface 1220 for this port. If this interface does not have a 1221 textual name, the value of this object is a zero 1222 length string. Note that the value of this object 1223 may be obtained in different ways, e.g., by manual 1224 configuration, or through ILMI interaction with 1225 the neighbor system." 1226 ::= { atmInterfaceConfEntry 12 } 1228 atmInterfaceCurrentMaxVpiBits OBJECT-TYPE 1229 SYNTAX INTEGER (0..12) 1230 MAX-ACCESS read-only 1231 STATUS current 1232 DESCRIPTION 1233 "The maximum number of VPI Bits that may 1234 currently be used at this ATM interface. 1235 The value is the minimum of 1236 atmInterfaceMaxActiveVpiBits, and the 1238 draft ATM Management Objects April 4, 1998 1240 atmInterfaceMaxActiveVpiBits of the interface's 1241 UNI/NNI peer. 1243 If the interface does not negotiate with 1244 its peer to determine the number of VPI Bits 1245 that can be used on the interface, then the 1246 value of this object must equal 1247 atmInterfaceMaxActiveVpiBits." 1248 ::= { atmInterfaceConfEntry 13 } 1250 atmInterfaceCurrentMaxVciBits OBJECT-TYPE 1251 SYNTAX INTEGER (0..16) 1252 MAX-ACCESS read-only 1253 STATUS current 1254 DESCRIPTION 1255 "The maximum number of VCI Bits that may 1256 currently be used at this ATM interface. 1257 The value is the minimum of 1258 atmInterfaceMaxActiveVciBits, and the 1259 atmInterfaceMaxActiveVciBits of the interface's 1260 UNI/NNI peer. 1262 If the interface does not negotiate with 1263 its peer to determine the number of VCI Bits 1264 that can be used on the interface, then the 1265 value of this object must equal 1266 atmInterfaceMaxActiveVciBits." 1267 ::= { atmInterfaceConfEntry 14 } 1269 atmInterfaceSubscrAddress OBJECT-TYPE 1270 SYNTAX AtmAddr 1271 MAX-ACCESS read-write 1272 STATUS current 1273 DESCRIPTION 1274 "The identifier assigned by a service provider 1275 to the network side of a public network UNI. 1276 If this interface has no assigned service provider 1277 address, or for other interfaces this is an octet string 1278 of zero length." 1279 ::= { atmInterfaceConfEntry 15 } 1281 draft ATM Management Objects April 4, 1998 1283 -- The ATM Interface DS3 PLCP Table 1285 -- This table contains the DS3 PLCP configuration and 1286 -- state parameters of those ATM interfaces 1287 -- which use DS3 PLCP for carrying ATM cells over DS3. 1289 atmInterfaceDs3PlcpTable OBJECT-TYPE 1290 SYNTAX SEQUENCE OF AtmInterfaceDs3PlcpEntry 1291 MAX-ACCESS not-accessible 1292 STATUS current 1293 DESCRIPTION 1294 "This table contains ATM interface DS3 PLCP 1295 parameters and state variables, one entry per 1296 ATM interface port." 1297 ::= { atmMIBObjects 3} 1299 atmInterfaceDs3PlcpEntry OBJECT-TYPE 1300 SYNTAX AtmInterfaceDs3PlcpEntry 1301 MAX-ACCESS not-accessible 1302 STATUS current 1303 DESCRIPTION 1304 "This list contains DS3 PLCP parameters and 1305 state variables at the ATM interface and is 1306 indexed by the ifIndex value of the ATM interface." 1307 INDEX { ifIndex } 1308 ::= { atmInterfaceDs3PlcpTable 1} 1310 AtmInterfaceDs3PlcpEntry ::= SEQUENCE { 1311 atmInterfaceDs3PlcpSEFSs Counter32, 1312 atmInterfaceDs3PlcpAlarmState INTEGER, 1313 atmInterfaceDs3PlcpUASs Counter32 1314 } 1316 atmInterfaceDs3PlcpSEFSs OBJECT-TYPE 1317 SYNTAX Counter32 1318 MAX-ACCESS read-only 1319 STATUS current 1320 DESCRIPTION 1321 "The number of DS3 PLCP Severely Errored Framing 1322 Seconds (SEFS). Each SEFS represents a 1323 one-second interval which contains 1324 one or more SEF events." 1325 ::= { atmInterfaceDs3PlcpEntry 1} 1327 draft ATM Management Objects April 4, 1998 1329 atmInterfaceDs3PlcpAlarmState OBJECT-TYPE 1330 SYNTAX INTEGER { 1331 noAlarm(1), 1332 receivedFarEndAlarm(2), 1333 incomingLOF(3) 1334 } 1335 MAX-ACCESS read-only 1336 STATUS current 1337 DESCRIPTION 1338 "This variable indicates if there is an 1339 alarm present for the DS3 PLCP. The value 1340 receivedFarEndAlarm means that the DS3 PLCP 1341 has received an incoming Yellow 1342 Signal, the value incomingLOF means that 1343 the DS3 PLCP has declared a loss of frame (LOF) 1344 failure condition, and the value noAlarm 1345 means that there are no alarms present. 1346 Transition from the failure to the no alarm state 1347 occurs when no defects (e.g., LOF) are received 1348 for more than 10 seconds." 1349 ::= { atmInterfaceDs3PlcpEntry 2} 1351 atmInterfaceDs3PlcpUASs OBJECT-TYPE 1352 SYNTAX Counter32 1353 MAX-ACCESS read-only 1354 STATUS current 1355 DESCRIPTION 1356 "The counter associated with the number of 1357 Unavailable Seconds encountered by the PLCP." 1358 ::= { atmInterfaceDs3PlcpEntry 3} 1360 draft ATM Management Objects April 4, 1998 1362 -- The ATM Interface TC Sublayer Table 1364 -- This table contains TC sublayer configuration and 1365 -- state parameters of those ATM interfaces 1366 -- which use TC sublayer for carrying ATM cells over 1367 -- SONET/SDH or DS3. 1369 atmInterfaceTCTable OBJECT-TYPE 1370 SYNTAX SEQUENCE OF AtmInterfaceTCEntry 1371 MAX-ACCESS not-accessible 1372 STATUS current 1373 DESCRIPTION 1374 "This table contains ATM interface TC 1375 Sublayer parameters and state variables, 1376 one entry per ATM interface port." 1377 ::= { atmMIBObjects 4} 1379 atmInterfaceTCEntry OBJECT-TYPE 1380 SYNTAX AtmInterfaceTCEntry 1381 MAX-ACCESS not-accessible 1382 STATUS current 1383 DESCRIPTION 1384 "This list contains TC Sublayer parameters 1385 and state variables at the ATM interface and is 1386 indexed by the ifIndex value of the ATM interface." 1387 INDEX {ifIndex } 1388 ::= { atmInterfaceTCTable 1} 1390 AtmInterfaceTCEntry ::= SEQUENCE { 1391 atmInterfaceOCDEvents Counter32, 1392 atmInterfaceTCAlarmState INTEGER 1393 } 1395 atmInterfaceOCDEvents OBJECT-TYPE 1396 SYNTAX Counter32 1397 MAX-ACCESS read-only 1398 STATUS current 1399 DESCRIPTION 1400 "The number of times the Out of Cell 1401 Delineation (OCD) events occur. If seven 1402 consecutive ATM cells have Header Error 1403 Control (HEC) violations, an OCD event occurs. 1404 A high number of OCD events may indicate a 1405 problem with the TC Sublayer." 1407 draft ATM Management Objects April 4, 1998 1409 ::= { atmInterfaceTCEntry 1} 1411 atmInterfaceTCAlarmState OBJECT-TYPE 1412 SYNTAX INTEGER { 1413 noAlarm(1), 1414 lcdFailure(2) 1415 } 1416 MAX-ACCESS read-only 1417 STATUS current 1418 DESCRIPTION 1419 "This variable indicates if there is an 1420 alarm present for the TC Sublayer. The value 1421 lcdFailure(2) indicates that the TC Sublayer 1422 is currently in the Loss of Cell Delineation 1423 (LCD) defect maintenance state. The value 1424 noAlarm(1) indicates that the TC Sublayer 1425 is currently not in the LCD defect 1426 maintenance state." 1427 ::= { atmInterfaceTCEntry 2} 1429 draft ATM Management Objects April 4, 1998 1431 -- ATM Traffic Descriptor Parameter Table 1433 -- This table contains a set of self-consistent 1434 -- ATM traffic parameters including the 1435 -- ATM traffic service category. 1437 -- The ATM virtual link tables (i.e., VPL and VCL tables) 1438 -- will use this ATM Traffic Descriptor table 1439 -- to assign traffic parameters and service category 1440 -- to the receive and transmit directions of 1441 -- the ATM virtual links (i.e., VPLs and VCLs). 1442 -- The ATM VPL or VCL table will indicate a row 1443 -- in the atmTrafficDescrParamTable 1444 -- using its atmTrafficDescrParamIndex value. 1445 -- The management application can then compare a set of 1446 -- ATM traffic parameters with a single value. 1448 -- If no suitable row(s) in the atmTrafficDescrParamTable 1449 -- exists, the manager must create a new row(s) in this 1450 -- table. If such a row is created, agent checks the 1451 -- sanity of that set of ATM traffic parameter values. 1453 -- The manager may use atmTrafficDescrParamIndexNext 1454 -- in order to obtain a free atmTrafficDescrParamIndex 1455 -- value. 1457 -- When creating a new row, the parameter values 1458 -- will be checked for self-consistency. 1459 -- Predefined/template rows may be supported. 1461 -- A row in the atmTrafficDescrParamTable is deleted 1462 -- by setting the atmTrafficDescrRowStatus to destroy(6). 1463 -- The agent will check whether this row is still in use 1464 -- by any entry of the atmVplTable or atmVclTable. 1465 -- The agent denies the request if the row is still in 1466 -- use. 1468 -- The ATM Traffic Descriptor Parameter Table 1470 atmTrafficDescrParamTable OBJECT-TYPE 1471 SYNTAX SEQUENCE OF AtmTrafficDescrParamEntry 1472 MAX-ACCESS not-accessible 1473 STATUS current 1474 DESCRIPTION 1476 draft ATM Management Objects April 4, 1998 1478 "This table contains information on ATM traffic 1479 descriptor type and the associated parameters." 1480 ::= { atmMIBObjects 5} 1482 atmTrafficDescrParamEntry OBJECT-TYPE 1483 SYNTAX AtmTrafficDescrParamEntry 1484 MAX-ACCESS not-accessible 1485 STATUS current 1486 DESCRIPTION 1487 "This list contains ATM traffic descriptor 1488 type and the associated parameters." 1489 INDEX {atmTrafficDescrParamIndex} 1490 ::= { atmTrafficDescrParamTable 1} 1492 AtmTrafficDescrParamEntry ::= SEQUENCE { 1493 atmTrafficDescrParamIndex AtmTrafficDescrParamIndex, 1494 atmTrafficDescrType OBJECT IDENTIFIER, 1495 atmTrafficDescrParam1 Integer32, 1496 atmTrafficDescrParam2 Integer32, 1497 atmTrafficDescrParam3 Integer32, 1498 atmTrafficDescrParam4 Integer32, 1499 atmTrafficDescrParam5 Integer32, 1500 atmTrafficQoSClass INTEGER, 1501 atmTrafficDescrRowStatus RowStatus, 1502 atmServiceCategory AtmServiceCategory, 1503 atmTrafficFrameDiscard TruthValue 1504 } 1506 atmTrafficDescrParamIndex OBJECT-TYPE 1507 SYNTAX AtmTrafficDescrParamIndex 1508 MAX-ACCESS not-accessible 1509 STATUS current 1510 DESCRIPTION 1511 "This object is used by the virtual link 1512 table (i.e., VPL or VCL table) 1513 to identify the row of this table. 1514 When creating a new row in the table 1515 the value of this index may be obtained 1516 by retrieving the value of 1517 atmTrafficDescrParamIndexNext." 1518 ::= { atmTrafficDescrParamEntry 1} 1520 atmTrafficDescrType OBJECT-TYPE 1521 SYNTAX OBJECT IDENTIFIER 1522 MAX-ACCESS read-create 1524 draft ATM Management Objects April 4, 1998 1526 STATUS current 1527 DESCRIPTION 1528 "The value of this object identifies the type 1529 of ATM traffic descriptor. 1530 The type may indicate no traffic descriptor or 1531 traffic descriptor with one or more parameters. 1532 These parameters are specified as a parameter 1533 vector, in the corresponding instances of the 1534 objects: 1535 atmTrafficDescrParam1 1536 atmTrafficDescrParam2 1537 atmTrafficDescrParam3 1538 atmTrafficDescrParam4 1539 atmTrafficDescrParam5." 1540 DEFVAL { atmNoClpNoScr } 1541 ::= { atmTrafficDescrParamEntry 2} 1543 atmTrafficDescrParam1 OBJECT-TYPE 1544 SYNTAX Integer32 1545 MAX-ACCESS read-create 1546 STATUS current 1547 DESCRIPTION 1548 "The first parameter of the ATM traffic descriptor 1549 used according to the value of 1550 atmTrafficDescrType." 1551 DEFVAL { 0 } 1552 ::= { atmTrafficDescrParamEntry 3} 1554 atmTrafficDescrParam2 OBJECT-TYPE 1555 SYNTAX Integer32 1556 MAX-ACCESS read-create 1557 STATUS current 1558 DESCRIPTION 1559 "The second parameter of the ATM traffic descriptor 1560 used according to the value of 1561 atmTrafficDescrType." 1562 DEFVAL { 0 } 1563 ::= { atmTrafficDescrParamEntry 4} 1565 atmTrafficDescrParam3 OBJECT-TYPE 1566 SYNTAX Integer32 1567 MAX-ACCESS read-create 1568 STATUS current 1569 DESCRIPTION 1570 "The third parameter of the ATM traffic descriptor 1572 draft ATM Management Objects April 4, 1998 1574 used according to the value of 1575 atmTrafficDescrType." 1576 DEFVAL { 0 } 1577 ::= { atmTrafficDescrParamEntry 5} 1579 atmTrafficDescrParam4 OBJECT-TYPE 1580 SYNTAX Integer32 1581 MAX-ACCESS read-create 1582 STATUS current 1583 DESCRIPTION 1584 "The fourth parameter of the ATM traffic descriptor 1585 used according to the value of 1586 atmTrafficDescrType." 1587 DEFVAL { 0 } 1588 ::= { atmTrafficDescrParamEntry 6} 1590 atmTrafficDescrParam5 OBJECT-TYPE 1591 SYNTAX Integer32 1592 MAX-ACCESS read-create 1593 STATUS current 1594 DESCRIPTION 1595 "The fifth parameter of the ATM traffic descriptor 1596 used according to the value of 1597 atmTrafficDescrType." 1598 DEFVAL { 0 } 1599 ::= { atmTrafficDescrParamEntry 7} 1601 atmTrafficQoSClass OBJECT-TYPE 1602 SYNTAX INTEGER (0..255) 1603 MAX-ACCESS read-create 1604 STATUS deprecated 1605 DESCRIPTION 1606 "The value of this object identifies the QoS Class. 1607 Four Service classes have been 1608 specified in the ATM Forum UNI Specification: 1609 Service Class A: Constant bit rate video and 1610 Circuit emulation 1611 Service Class B: Variable bit rate video/audio 1612 Service Class C: Connection-oriented data 1613 Service Class D: Connectionless data 1614 Four QoS classes numbered 1, 2, 3, and 4 have 1615 been specified with the aim to support service 1616 classes A, B, C, and D respectively. 1617 An unspecified QoS Class numbered `0' is used 1618 for best effort traffic." 1620 draft ATM Management Objects April 4, 1998 1622 DEFVAL { 0 } 1623 ::= { atmTrafficDescrParamEntry 8} 1625 atmTrafficDescrRowStatus OBJECT-TYPE 1626 SYNTAX RowStatus 1627 MAX-ACCESS read-create 1628 STATUS current 1629 DESCRIPTION 1630 "This object is used to create 1631 a new row or modify or delete an 1632 existing row in this table." 1633 DEFVAL { active } 1634 ::= {atmTrafficDescrParamEntry 9} 1636 atmServiceCategory OBJECT-TYPE 1637 SYNTAX AtmServiceCategory 1638 MAX-ACCESS read-create 1639 STATUS current 1640 DESCRIPTION 1641 "The ATM service category." 1642 DEFVAL { ubr } 1643 ::= { atmTrafficDescrParamEntry 10} 1645 atmTrafficFrameDiscard OBJECT-TYPE 1646 SYNTAX TruthValue 1647 MAX-ACCESS read-create 1648 STATUS current 1649 DESCRIPTION 1650 "If set to 'true', this object indicates that the network 1651 is requested to treat data for this connection, in the 1652 given direction, as frames (e.g. AAL5 CPCS_PDU's) rather 1653 than as individual cells. While the precise 1654 implementation is network-specific, this treatment may 1655 for example involve discarding entire frames during 1656 congestion, rather than a few cells from many frames." 1657 DEFVAL { true } 1658 ::= { atmTrafficDescrParamEntry 11 } 1660 draft ATM Management Objects April 4, 1998 1662 -- ATM Interface Virtual Path Link (VPL) Table 1664 -- This table contains configuration and state 1665 -- information of a bi-directional Virtual Path Link 1666 -- (VPL) 1668 -- This table can be used to create, delete or modify 1669 -- a VPL that is terminated in an ATM host or switch. 1670 -- This table can also be used to create, delete or 1671 -- modify a VPL which is cross-connected to another 1672 -- VPL. 1674 -- In the example below, the traffic flows on the receive 1675 -- and transmit directions of the VPLs are characterized 1676 -- by atmVplReceiveTrafficDescrIndex and 1677 -- atmVplTransmitTrafficDescrIndex respectively. 1678 -- The cross-connected VPLs are identified by 1679 -- atmVplCrossConnectIdentifier. 1681 -- ________________________________ 1682 -- | | 1683 -- VPL | ATM Host, Switch, or Network | VPL 1684 -- receive | | receive 1685 -- ========> X X <======= 1686 -- <======== X X ========> 1687 -- transmit | | transmit 1688 -- |______________________________| 1690 -- The ATM Interface VPL Table 1692 atmVplTable OBJECT-TYPE 1693 SYNTAX SEQUENCE OF AtmVplEntry 1694 MAX-ACCESS not-accessible 1695 STATUS current 1696 DESCRIPTION 1697 "The Virtual Path Link (VPL) table. A 1698 bi-directional VPL is modeled as one entry 1699 in this table. This table can be used for 1700 PVCs, SVCs and Soft PVCs. 1701 Entries are not present in this table for 1703 draft ATM Management Objects April 4, 1998 1705 the VPIs used by entries in the atmVclTable." 1706 ::= { atmMIBObjects 6} 1708 atmVplEntry OBJECT-TYPE 1709 SYNTAX AtmVplEntry 1710 MAX-ACCESS not-accessible 1711 STATUS current 1712 DESCRIPTION 1713 "An entry in the VPL table. This entry is 1714 used to model a bi-directional VPL. 1715 To create a VPL at an ATM interface, 1716 either of the following procedures are used: 1718 Negotiated VPL establishment 1720 (1) The management application creates 1721 a VPL entry in the atmVplTable 1722 by setting atmVplRowStatus to createAndWait(5). 1723 This may fail for the following reasons: 1724 - The selected VPI value is unavailable, 1725 - The selected VPI value is in use. 1726 Otherwise, the agent creates a row and 1727 reserves the VPI value on that port. 1729 (2) The manager selects an existing row(s) in the 1730 atmTrafficDescrParamTable, 1731 thereby, selecting a set of self-consistent 1732 ATM traffic parameters and the service category 1733 for receive and transmit directions of the VPL. 1735 (2a) If no suitable row(s) in the 1736 atmTrafficDescrParamTable exists, 1737 the manager must create a new row(s) 1738 in that table. 1740 (2b) The manager characterizes the VPL's traffic 1741 parameters through setting the 1742 atmVplReceiveTrafficDescrIndex and the 1743 atmVplTransmitTrafficDescrIndex values 1744 in the VPL table, which point to the rows 1745 containing desired ATM traffic parameter values 1746 in the atmTrafficDescrParamTable. The agent 1747 will check the availability of resources and 1748 may refuse the request. 1749 If the transmit and receive service categories 1751 draft ATM Management Objects April 4, 1998 1753 are inconsistent, the agent should refuse the 1754 request. 1756 (3) The manager activates the VPL by setting the 1757 the atmVplRowStatus to active(1). 1758 If this set is successful, the agent has 1759 reserved the resources to satisfy the requested 1760 traffic parameter values and the service category 1761 for that VPL. 1763 (4) If the VPL terminates a VPC in the ATM host 1764 or switch, the manager turns on the 1765 atmVplAdminStatus to up(1) to turn the VPL 1766 traffic flow on. Otherwise, the 1767 atmVpCrossConnectTable must be used 1768 to cross-connect the VPL to another VPL(s) 1769 in an ATM switch or network. 1771 One-Shot VPL Establishment 1773 A VPL may also be established in one step by a 1774 set-request with all necessary VPL parameter 1775 values and atmVplRowStatus set to createAndGo(4). 1777 In contrast to the negotiated VPL establishment 1778 which allows for detailed error checking 1779 (i.e., set errors are explicitly linked to 1780 particular resource acquisition failures), 1781 the one-shot VPL establishment 1782 performs the setup on one operation but 1783 does not have the advantage of step-wise 1784 error checking. 1786 VPL Retirement 1788 A VPL is released by setting atmVplRowStatus to 1789 destroy(6), and the agent may release all 1790 associated resources." 1791 INDEX {ifIndex, atmVplVpi } 1792 ::= { atmVplTable 1} 1794 AtmVplEntry ::= SEQUENCE { 1795 atmVplVpi AtmVpIdentifier, 1796 atmVplAdminStatus AtmVorXAdminStatus, 1797 atmVplOperStatus AtmVorXOperStatus, 1799 draft ATM Management Objects April 4, 1998 1801 atmVplLastChange AtmVorXLastChange, 1802 atmVplReceiveTrafficDescrIndex 1803 AtmTrafficDescrParamIndex, 1804 atmVplTransmitTrafficDescrIndex 1805 AtmTrafficDescrParamIndex, 1806 atmVplCrossConnectIdentifier INTEGER, 1807 atmVplRowStatus RowStatus, 1808 atmVplCastType AtmConnCastType, 1809 atmVplConnKind AtmConnKind 1810 } 1812 atmVplVpi OBJECT-TYPE 1813 SYNTAX AtmVpIdentifier 1814 MAX-ACCESS not-accessible 1815 STATUS current 1816 DESCRIPTION 1817 "The VPI value of the VPL." 1818 ::= { atmVplEntry 1} 1820 atmVplAdminStatus OBJECT-TYPE 1821 SYNTAX AtmVorXAdminStatus 1822 MAX-ACCESS read-create 1823 STATUS current 1824 DESCRIPTION 1825 "This object is instanciated only for a VPL 1826 which terminates a VPC (i.e., one which is 1827 NOT cross-connected to other VPLs). 1828 Its value specifies the desired 1829 administrative state of the VPL." 1830 DEFVAL { down } 1831 ::= { atmVplEntry 2} 1833 atmVplOperStatus OBJECT-TYPE 1834 SYNTAX AtmVorXOperStatus 1835 MAX-ACCESS read-only 1836 STATUS current 1837 DESCRIPTION 1838 "The current operational status of the VPL." 1839 ::= { atmVplEntry 3} 1841 atmVplLastChange OBJECT-TYPE 1842 SYNTAX AtmVorXLastChange 1843 MAX-ACCESS read-only 1844 STATUS current 1846 draft ATM Management Objects April 4, 1998 1848 DESCRIPTION 1849 "The value of sysUpTime at the time this 1850 VPL entered its current operational state." 1851 ::= { atmVplEntry 4 } 1853 atmVplReceiveTrafficDescrIndex OBJECT-TYPE 1854 SYNTAX AtmTrafficDescrParamIndex 1855 MAX-ACCESS read-create 1856 STATUS current 1857 DESCRIPTION 1858 "The value of this object identifies the row 1859 in the atmTrafficDescrParamTable which 1860 applies to the receive direction of the VPL." 1861 DEFVAL { 0 } 1862 ::= { atmVplEntry 5} 1864 atmVplTransmitTrafficDescrIndex OBJECT-TYPE 1865 SYNTAX AtmTrafficDescrParamIndex 1866 MAX-ACCESS read-create 1867 STATUS current 1868 DESCRIPTION 1869 "The value of this object identifies the row 1870 in the atmTrafficDescrParamTable which 1871 applies to the transmit direction of the VPL." 1872 DEFVAL { 0 } 1873 ::= { atmVplEntry 6} 1875 atmVplCrossConnectIdentifier OBJECT-TYPE 1876 SYNTAX INTEGER (0..2147483647) 1877 MAX-ACCESS read-only 1878 STATUS current 1879 DESCRIPTION 1880 "This object is instantiated only for a VPL 1881 which is cross-connected to other VPLs 1882 that belong to the same VPC. All such 1883 associated VPLs have the same value of this 1884 object, and all their cross-connections are 1885 identified either by entries that are indexed 1886 by the same value of atmVpCrossConnectIndex in 1887 the atmVpCrossConnectTable of this MIB module or by 1888 the same value of the cross-connect index in 1889 the cross-connect table for SVCs and Soft PVCs 1890 (defined in a separate MIB module). 1891 At no time should entries in these respective 1892 cross-connect tables exist simultaneously 1894 draft ATM Management Objects April 4, 1998 1896 with the same cross-connect index value. 1898 The value of this object is initialized by the 1899 agent after the associated entries in the 1900 atmVpCrossConnectTable have been created." 1901 ::= {atmVplEntry 7} 1903 atmVplRowStatus OBJECT-TYPE 1904 SYNTAX RowStatus 1905 MAX-ACCESS read-create 1906 STATUS current 1907 DESCRIPTION 1908 "This object is used to create, delete 1909 or modify a row in this table. 1910 To create a new VCL, this object is 1911 initially set to 'createAndWait' or 1912 'createAndGo'. This object should not be 1913 set to 'active' unless the following columnar 1914 objects have been set to their desired value 1915 in this row: 1916 atmVplReceiveTrafficDescrIndex and 1917 atmVplTransmitTrafficDescrIndex." 1918 DEFVAL { active } 1919 ::= {atmVplEntry 8} 1921 atmVplCastType OBJECT-TYPE 1922 SYNTAX AtmConnCastType 1923 MAX-ACCESS read-create 1924 STATUS current 1925 DESCRIPTION 1926 "The connection topology type." 1927 DEFVAL { p2p } 1928 ::= {atmVplEntry 9} 1930 atmVplConnKind OBJECT-TYPE 1931 SYNTAX AtmConnKind 1932 MAX-ACCESS read-create 1933 STATUS current 1934 DESCRIPTION 1935 "The use of call control." 1936 DEFVAL { pvc } 1937 ::= {atmVplEntry 10} 1939 draft ATM Management Objects April 4, 1998 1941 -- ATM Interface Virtual Channel Link (VCL) Table 1943 -- This table contains configuration and state 1944 -- information of a bi-directional Virtual Channel 1945 -- Link (VCL) at an ATM interface. 1947 -- This table can be used to create, delete or modify 1948 -- a VCL that is terminated in an ATM host or switch. 1949 -- This table can also be 1950 -- used to create, delete or modify a VCL that is 1951 -- cross-connected to another VCL. 1953 -- The ATM Interface VCL Table 1955 atmVclTable OBJECT-TYPE 1956 SYNTAX SEQUENCE OF AtmVclEntry 1957 MAX-ACCESS not-accessible 1958 STATUS current 1959 DESCRIPTION 1960 "The Virtual Channel Link (VCL) table. A 1961 bi-directional VCL is modeled as one entry 1962 in this table. This table can be used for 1963 PVCs, SVCs and Soft PVCs." 1964 ::= { atmMIBObjects 7} 1966 atmVclEntry OBJECT-TYPE 1967 SYNTAX AtmVclEntry 1968 MAX-ACCESS not-accessible 1969 STATUS current 1970 DESCRIPTION 1971 "An entry in the VCL table. This entry is 1972 used to model a bi-directional VCL. 1973 To create a VCL at an ATM interface, 1974 either of the following procedures are used: 1976 Negotiated VCL establishment 1978 (1) The management application creates 1979 a VCL entry in the atmVclTable 1980 by setting atmVclRowStatus to createAndWait(5). 1981 This may fail for the following reasons: 1982 - The selected VPI/VCI values are unavailable, 1983 - The selected VPI/VCI values are in use. 1985 draft ATM Management Objects April 4, 1998 1987 Otherwise, the agent creates a row and 1988 reserves the VPI/VCI values on that port. 1990 (2) The manager selects an existing row(s) in the 1991 atmTrafficDescrParamTable, 1992 thereby, selecting a set of self-consistent 1993 ATM traffic parameters and the service category 1994 for receive and transmit directions of the VCL. 1996 (2a) If no suitable row(s) in the 1997 atmTrafficDescrParamTable exists, 1998 the manager must create a new row(s) 1999 in that table. 2001 (2b) The manager characterizes the VCL's traffic 2002 parameters through setting the 2003 atmVclReceiveTrafficDescrIndex and the 2004 atmVclTransmitTrafficDescrIndex values 2005 in the VCL table, which point to the rows 2006 containing desired ATM traffic parameter values 2007 in the atmTrafficDescrParamTable. The agent 2008 will check the availability of resources and 2009 may refuse the request. 2010 If the transmit and receive service categories 2011 are inconsistent, the agent should refuse the 2012 request. 2014 (3) The manager activates the VCL by setting the 2015 the atmVclRowStatus to active(1) (for 2016 requirements on this activation see the 2017 description of atmVclRowStatus). 2018 If this set is successful, the agent has 2019 reserved the resources to satisfy the requested 2020 traffic parameter values and the service category 2021 for that VCL. 2022 (4) If the VCL terminates a VCC in the ATM host 2023 or switch, the manager turns on the 2024 atmVclAdminStatus to up(1) to turn the VCL 2025 traffic flow on. Otherwise, the 2026 atmVcCrossConnectTable must be used 2027 to cross-connect the VCL to another VCL(s) 2028 in an ATM switch or network. 2030 One-Shot VCL Establishment 2032 draft ATM Management Objects April 4, 1998 2034 A VCL may also be established in one step by a 2035 set-request with all necessary VCL parameter 2036 values and atmVclRowStatus set to createAndGo(4). 2038 In contrast to the negotiated VCL establishment 2039 which allows for detailed error checking 2040 (i.e., set errors are explicitly linked to 2041 particular resource acquisition failures), 2042 the one-shot VCL establishment 2043 performs the setup on one operation but 2044 does not have the advantage of step-wise 2045 error checking. 2047 VCL Retirement 2049 A VCL is released by setting atmVclRowStatus to 2050 destroy(6), and the agent may release all 2051 associated resources." 2052 INDEX {ifIndex, atmVclVpi, atmVclVci } 2053 ::= { atmVclTable 1} 2055 AtmVclEntry ::= SEQUENCE { 2056 atmVclVpi AtmVpIdentifier, 2057 atmVclVci AtmVcIdentifier, 2058 atmVclAdminStatus AtmVorXAdminStatus, 2059 atmVclOperStatus AtmVorXOperStatus, 2060 atmVclLastChange AtmVorXLastChange, 2061 atmVclReceiveTrafficDescrIndex 2062 AtmTrafficDescrParamIndex, 2063 atmVclTransmitTrafficDescrIndex 2064 AtmTrafficDescrParamIndex, 2065 atmVccAalType INTEGER, 2066 atmVccAal5CpcsTransmitSduSize INTEGER, 2067 atmVccAal5CpcsReceiveSduSize INTEGER, 2068 atmVccAal5EncapsType INTEGER, 2069 atmVclCrossConnectIdentifier INTEGER, 2070 atmVclRowStatus RowStatus, 2071 atmVclCastType AtmConnCastType, 2072 atmVclConnKind AtmConnKind 2073 } 2075 atmVclVpi OBJECT-TYPE 2076 SYNTAX AtmVpIdentifier 2077 MAX-ACCESS not-accessible 2078 STATUS current 2080 draft ATM Management Objects April 4, 1998 2082 DESCRIPTION 2083 "The VPI value of the VCL." 2084 ::= { atmVclEntry 1} 2086 atmVclVci OBJECT-TYPE 2087 SYNTAX AtmVcIdentifier 2088 MAX-ACCESS not-accessible 2089 STATUS current 2090 DESCRIPTION 2091 "The VCI value of the VCL." 2092 ::= { atmVclEntry 2} 2094 atmVclAdminStatus OBJECT-TYPE 2095 SYNTAX AtmVorXAdminStatus 2096 MAX-ACCESS read-create 2097 STATUS current 2098 DESCRIPTION 2099 "This object is instanciated only for a VCL which 2100 terminates a VCC (i.e., one which is NOT 2101 cross-connected to other VCLs). Its value 2102 specifies the desired administrative state of 2103 the VCL." 2104 DEFVAL { down } 2105 ::= { atmVclEntry 3} 2107 atmVclOperStatus OBJECT-TYPE 2108 SYNTAX AtmVorXOperStatus 2109 MAX-ACCESS read-only 2110 STATUS current 2111 DESCRIPTION 2112 "The current operational status of the VCL." 2113 ::= { atmVclEntry 4} 2115 atmVclLastChange OBJECT-TYPE 2116 SYNTAX AtmVorXLastChange 2117 MAX-ACCESS read-only 2118 STATUS current 2119 DESCRIPTION 2120 "The value of sysUpTime at the time this VCL 2121 entered its current operational state." 2122 ::= { atmVclEntry 5 } 2124 atmVclReceiveTrafficDescrIndex OBJECT-TYPE 2125 SYNTAX AtmTrafficDescrParamIndex 2126 MAX-ACCESS read-create 2128 draft ATM Management Objects April 4, 1998 2130 STATUS current 2131 DESCRIPTION 2132 "The value of this object identifies the row 2133 in the ATM Traffic Descriptor Table which 2134 applies to the receive direction of this VCL." 2135 DEFVAL { 0 } 2136 ::= { atmVclEntry 6} 2138 atmVclTransmitTrafficDescrIndex OBJECT-TYPE 2139 SYNTAX AtmTrafficDescrParamIndex 2140 MAX-ACCESS read-create 2141 STATUS current 2142 DESCRIPTION 2143 "The value of this object identifies the row 2144 of the ATM Traffic Descriptor Table which applies 2145 to the transmit direction of this VCL." 2146 DEFVAL { 0 } 2147 ::= { atmVclEntry 7} 2149 atmVccAalType OBJECT-TYPE 2150 SYNTAX INTEGER { 2151 aal1(1), 2152 aal34(2), 2153 aal5(3), 2154 other(4), 2155 unknown(5), 2156 aal2(6) 2157 } 2158 MAX-ACCESS read-create 2159 STATUS current 2160 DESCRIPTION 2161 "An instance of this object only exists when the 2162 local VCL end-point is also the VCC end-point, 2163 and AAL is in use. 2164 The type of AAL used on this VCC. 2165 The AAL type includes AAL1, AAL2, AAL3/4, 2166 and AAL5. The other(4) may be user-defined 2167 AAL type. The unknown type indicates that 2168 the AAL type cannot be determined." 2169 DEFVAL { aal5 } 2170 ::= { atmVclEntry 8 } 2172 atmVccAal5CpcsTransmitSduSize OBJECT-TYPE 2173 SYNTAX INTEGER (1..65535) 2174 MAX-ACCESS read-create 2176 draft ATM Management Objects April 4, 1998 2178 STATUS current 2179 DESCRIPTION 2180 "An instance of this object only exists when the 2181 local VCL end-point is also the VCC end-point, 2182 and AAL5 is in use. 2183 The maximum AAL5 CPCS SDU size in octets that is 2184 supported on the transmit direction of this VCC." 2185 DEFVAL { 9188 } 2186 ::= { atmVclEntry 9 } 2188 atmVccAal5CpcsReceiveSduSize OBJECT-TYPE 2189 SYNTAX INTEGER (1..65535) 2190 MAX-ACCESS read-create 2191 STATUS current 2192 DESCRIPTION 2193 "An instance of this object only exists when the 2194 local VCL end-point is also the VCC end-point, 2195 and AAL5 is in use. 2196 The maximum AAL5 CPCS SDU size in octets that is 2197 supported on the receive direction of this VCC." 2198 DEFVAL { 9188 } 2199 ::= { atmVclEntry 10 } 2201 atmVccAal5EncapsType OBJECT-TYPE 2202 SYNTAX INTEGER { 2203 vcMultiplexRoutedProtocol(1), 2204 vcMultiplexBridgedProtocol8023(2), 2205 vcMultiplexBridgedProtocol8025(3), 2206 vcMultiplexBridgedProtocol8026(4), 2207 vcMultiplexLANemulation8023(5), 2208 vcMultiplexLANemulation8025(6), 2209 llcEncapsulation(7), 2210 multiprotocolFrameRelaySscs(8), 2211 other(9), 2212 unknown(10) 2213 } 2214 MAX-ACCESS read-create 2215 STATUS current 2216 DESCRIPTION 2217 "An instance of this object only exists when the 2218 local VCL end-point is also the VCC end-point, 2219 and AAL5 is in use. 2220 The type of data encapsulation used over 2221 the AAL5 SSCS layer. The definitions reference 2222 RFC 1483 Multiprotocol Encapsulation 2224 draft ATM Management Objects April 4, 1998 2226 over ATM AAL5 and to the ATM Forum 2227 LAN Emulation specification." 2228 DEFVAL { llcEncapsulation } 2229 ::= { atmVclEntry 11 } 2231 atmVclCrossConnectIdentifier OBJECT-TYPE 2232 SYNTAX INTEGER (0..2147483647) 2233 MAX-ACCESS read-only 2234 STATUS current 2235 DESCRIPTION 2236 "This object is instantiated only for a VCL 2237 which is cross-connected to other VCLs 2238 that belong to the same VCC. All such 2239 associated VCLs have the same value of this 2240 object, and all their cross-connections are 2241 identified either by entries that are indexed 2242 by the same value of atmVcCrossConnectIndex in 2243 the atmVcCrossConnectTable of this MIB module or by 2244 the same value of the cross-connect index in 2245 the cross-connect table for SVCs and Soft PVCs 2246 (defined in a separate MIB module). 2248 At no time should entries in these respective 2249 cross-connect tables exist simultaneously 2250 with the same cross-connect index value. 2252 The value of this object is initialized by the 2253 agent after the associated entries in the 2254 atmVcCrossConnectTable have been created." 2255 ::= {atmVclEntry 12} 2257 atmVclRowStatus OBJECT-TYPE 2258 SYNTAX RowStatus 2259 MAX-ACCESS read-create 2260 STATUS current 2261 DESCRIPTION 2262 "This object is used to create, delete or 2263 modify a row in this table. To create 2264 a new VCL, this object is initially set 2265 to 'createAndWait' or 'createAndGo'. 2266 This object should not be 2267 set to 'active' unless the following columnar 2268 objects have been set to their desired value 2269 in this row: 2270 atmVclReceiveTrafficDescrIndex, 2272 draft ATM Management Objects April 4, 1998 2274 atmVclTransmitTrafficDescrIndex. 2275 In addition, if the local VCL end-point 2276 is also the VCC end-point: 2277 atmVccAalType. 2278 In addition, for AAL5 connections only: 2279 atmVccAal5CpcsTransmitSduSize, 2280 atmVccAal5CpcsReceiveSduSize, and 2281 atmVccAal5EncapsType. (The existence 2282 of these objects imply the AAL connection type.)" 2283 DEFVAL { active } 2284 ::= {atmVclEntry 13} 2286 atmVclCastType OBJECT-TYPE 2287 SYNTAX AtmConnCastType 2288 MAX-ACCESS read-create 2289 STATUS current 2290 DESCRIPTION 2291 "The connection topology type." 2292 DEFVAL { p2p } 2293 ::= {atmVclEntry 14} 2295 atmVclConnKind OBJECT-TYPE 2296 SYNTAX AtmConnKind 2297 MAX-ACCESS read-create 2298 STATUS current 2299 DESCRIPTION 2300 "The use of call control." 2301 DEFVAL { pvc } 2302 ::= {atmVclEntry 15} 2304 draft ATM Management Objects April 4, 1998 2306 -- ATM Virtual Path (VP) Cross Connect Table 2308 -- This table contains configuration and state 2309 -- information of point-to-point, 2310 -- point-to-multipoint, or multipoint-to-multipoint 2311 -- VP cross-connects for PVCs. 2313 -- This table has read-create access and can be used 2314 -- to cross-connect the VPLs together in an ATM switch 2315 -- or network. The atmVpCrossConnectIndex 2316 -- is used to associate the related 2317 -- VPLs that are cross-connected together. 2319 -- The ATM VP Cross Connect Table 2320 -- models each bi-directional VPC 2321 -- cross-connect as a set of entries in 2322 -- the atmVpCrossConnectTable. A 2323 -- point-to-point VPC cross-connect is modeled 2324 -- as one entry; a point-to-multipoint (N leafs) VPC 2325 -- cross-connect as N entries in this table; and 2326 -- a multipoint-to-multipoint (N parties) VPC cross- 2327 -- connect as N(N-1)/2 entries in this table. 2328 -- In the latter cases, all the N (or N(N-1)/2) entries 2329 -- are associated with a single VPC cross-connect by 2330 -- having the same value of atmVpCrossConnectIndex. 2332 -- _________________________________________ 2333 -- | | 2334 -- Low | ATM Switch or Network | High 2335 -- port| | port 2336 -- _____|>> from low to high VPC traffic flow >>|______ 2337 -- |<< from high to low VPC traffic flow <<| 2338 -- | | 2339 -- |_______________________________________| 2340 -- 2342 -- The terms low and high are chosen to represent 2343 -- numerical ordering of the two interfaces associated 2344 -- with a VPC cross-connect. That is, the ATM interface 2345 -- with the lower value of ifIndex is termed 'low', 2346 -- while the other ATM interface associated with the 2347 -- VPC cross-connect is termed 'high'. This terminology 2348 -- is used to provide directional information; for 2349 -- example, the atmVpCrossConnectL2HOperStatus applies 2351 draft ATM Management Objects April 4, 1998 2353 -- to the low->high direction, and 2354 -- atmVpCrossConnectH2LOperStatus applies to the 2355 -- high->low direction, as illustrated above. 2357 atmVpCrossConnectIndexNext OBJECT-TYPE 2358 SYNTAX INTEGER (0..2147483647) 2359 MAX-ACCESS read-only 2360 STATUS current 2361 DESCRIPTION 2362 "This object contains an appropriate value to 2363 be used for atmVpCrossConnectIndex when creating 2364 entries in the atmVpCrossConnectTable. The value 2365 0 indicates that no unassigned entries are 2366 available. To obtain the atmVpCrossConnectIndex 2367 value for a new entry, the manager issues a 2368 management protocol retrieval operation to obtain 2369 the current value of this object. After each 2370 retrieval, the agent should modify the value to 2371 the next unassigned index." 2372 ::= { atmMIBObjects 8 } 2374 -- The ATM VP Cross Connect Table 2376 atmVpCrossConnectTable OBJECT-TYPE 2377 SYNTAX SEQUENCE OF AtmVpCrossConnectEntry 2378 MAX-ACCESS not-accessible 2379 STATUS current 2380 DESCRIPTION 2381 "The ATM VP Cross Connect table for PVCs. 2382 An entry in this table models two 2383 cross-connected VPLs. 2384 Each VPL must have its atmConnKind set 2385 to pvc(1)" 2386 ::= { atmMIBObjects 9 } 2388 atmVpCrossConnectEntry OBJECT-TYPE 2389 SYNTAX AtmVpCrossConnectEntry 2390 MAX-ACCESS not-accessible 2391 STATUS current 2393 draft ATM Management Objects April 4, 1998 2395 DESCRIPTION 2396 "An entry in the ATM VP Cross Connect table. 2397 This entry is used to model a bi-directional 2398 ATM VP cross-connect which cross-connects 2399 two VPLs. 2401 Step-wise Procedures to set up a VP Cross-connect 2403 Once the entries in the atmVplTable are created, 2404 the following procedures are used 2405 to cross-connect the VPLs together. 2407 (1) The manager obtains a unique 2408 atmVpCrossConnectIndex by reading the 2409 atmVpCrossConnectIndexNext object. 2411 (2) Next, the manager creates a set of one 2412 or more rows in the ATM VP Cross Connect 2413 Table, one for each cross-connection between 2414 two VPLs. Each row is indexed by the ATM 2415 interface port numbers and VPI values of the 2416 two ends of that cross-connection. 2417 This set of rows specifies the topology of the 2418 VPC cross-connect and is identified by a single 2419 value of atmVpCrossConnectIndex. 2421 Negotiated VP Cross-Connect Establishment 2423 (2a) The manager creates a row in this table by 2424 setting atmVpCrossConnectRowStatus to 2425 createAndWait(5). The agent checks the 2426 requested topology and the mutual sanity of 2427 the ATM traffic parameters and 2428 service categories, i.e., the row creation 2429 fails if: 2430 - the requested topology is incompatible with 2431 associated values of atmVplCastType, 2432 - the requested topology is not supported 2433 by the agent, 2434 - the traffic/service category parameter values 2435 associated with the requested row are 2436 incompatible with those of already existing 2437 rows for this VP cross-connect. 2438 [For example, for setting up 2439 a point-to-point VP cross-connect, the 2441 draft ATM Management Objects April 4, 1998 2443 ATM traffic parameters in the receive direction 2444 of a VPL at the low end of the cross-connect 2445 must equal to the traffic parameters in the 2446 transmit direction of the other VPL at the 2447 high end of the cross-connect, 2448 otherwise, the row creation fails.] 2449 The agent also checks for internal errors 2450 in building the cross-connect. 2452 The atmVpCrossConnectIndex values in the 2453 corresponding atmVplTable rows are filled 2454 in by the agent at this point. 2456 (2b) The manager promotes the row in the 2457 atmVpCrossConnectTable by setting 2458 atmVpCrossConnectRowStatus to active(1). If 2459 this set is successful, the agent has reserved 2460 the resources specified by the ATM traffic 2461 parameter and Service category values 2462 for each direction of the VP cross-connect 2463 in an ATM switch or network. 2465 (3) The manager sets the 2466 atmVpCrossConnectAdminStatus to up(1) in all 2467 rows of this VP cross-connect to turn the 2468 traffic flow on. 2470 One-Shot VP Cross-Connect Establishment 2472 A VP cross-connect may also be established in 2473 one step by a set-request with all necessary 2474 parameter values and atmVpCrossConnectRowStatus 2475 set to createAndGo(4). 2477 In contrast to the negotiated VP cross-connect 2478 establishment which allows for detailed error 2479 checking (i.e., set errors are explicitly linked 2480 to particular resource acquisition failures), 2481 the one-shot VP cross-connect establishment 2482 performs the setup on one operation but does not 2483 have the advantage of step-wise error checking. 2485 VP Cross-Connect Retirement 2487 draft ATM Management Objects April 4, 1998 2489 A VP cross-connect identified by a particular 2490 value of atmVpCrossConnectIndex is released by: 2492 (1) Setting atmVpCrossConnectRowStatus of all 2493 rows identified by this value of 2494 atmVpCrossConnectIndex to destroy(6). 2495 The agent may release all 2496 associated resources, and the 2497 atmVpCrossConnectIndex values in the 2498 corresponding atmVplTable row are removed. 2499 Note that a situation when only a subset of 2500 the associated rows are deleted corresponds 2501 to a VP topology change. 2503 (2) After deletion of the appropriate 2504 atmVpCrossConnectEntries, the manager may 2505 set atmVplRowStatus to destroy(6) the 2506 associated VPLs. The agent releases 2507 the resources and removes the associated 2508 rows in the atmVplTable. 2510 VP Cross-connect Reconfiguration 2512 At the discretion of the agent, a VP 2513 cross-connect may be reconfigured by 2514 adding and/or deleting leafs to/from 2515 the VP topology as per the VP cross-connect 2516 establishment/retirement procedures. 2517 Reconfiguration of traffic/service category parameter 2518 values requires release of the VP cross-connect 2519 before those parameter values may by changed 2520 for individual VPLs." 2521 INDEX { atmVpCrossConnectIndex, 2522 atmVpCrossConnectLowIfIndex, 2523 atmVpCrossConnectLowVpi, 2524 atmVpCrossConnectHighIfIndex, 2525 atmVpCrossConnectHighVpi } 2526 ::= { atmVpCrossConnectTable 1 } 2528 AtmVpCrossConnectEntry ::= SEQUENCE { 2529 atmVpCrossConnectIndex INTEGER, 2530 atmVpCrossConnectLowIfIndex InterfaceIndex, 2531 atmVpCrossConnectLowVpi AtmVpIdentifier, 2532 atmVpCrossConnectHighIfIndex InterfaceIndex, 2533 atmVpCrossConnectHighVpi AtmVpIdentifier, 2535 draft ATM Management Objects April 4, 1998 2537 atmVpCrossConnectAdminStatus AtmVorXAdminStatus, 2538 atmVpCrossConnectL2HOperStatus AtmVorXOperStatus, 2539 atmVpCrossConnectH2LOperStatus AtmVorXOperStatus, 2540 atmVpCrossConnectL2HLastChange AtmVorXLastChange, 2541 atmVpCrossConnectH2LLastChange AtmVorXLastChange, 2542 atmVpCrossConnectRowStatus RowStatus 2543 } 2545 atmVpCrossConnectIndex OBJECT-TYPE 2546 SYNTAX INTEGER (1..2147483647) 2547 MAX-ACCESS not-accessible 2548 STATUS current 2549 DESCRIPTION 2550 "A unique value to identify this VP cross-connect. 2551 For each VPL associated with this cross-connect, 2552 the agent reports this cross-connect index value 2553 in the atmVplCrossConnectIdentifier attribute of 2554 the corresponding atmVplTable entries." 2555 ::= { atmVpCrossConnectEntry 1 } 2557 atmVpCrossConnectLowIfIndex OBJECT-TYPE 2558 SYNTAX InterfaceIndex 2559 MAX-ACCESS not-accessible 2560 STATUS current 2561 DESCRIPTION 2562 "The ifIndex value of the ATM interface for 2563 this VP cross-connect. The term low implies 2564 that this ATM interface has the numerically lower 2565 ifIndex value than the other ATM interface 2566 identified in the same atmVpCrossConnectEntry." 2567 ::= { atmVpCrossConnectEntry 2 } 2569 atmVpCrossConnectLowVpi OBJECT-TYPE 2570 SYNTAX AtmVpIdentifier 2571 MAX-ACCESS not-accessible 2572 STATUS current 2573 DESCRIPTION 2574 "The VPI value at the ATM interface 2575 associated with the VP cross-connect that is 2576 identified by atmVpCrossConnectLowIfIndex." 2577 ::= { atmVpCrossConnectEntry 3 } 2579 atmVpCrossConnectHighIfIndex OBJECT-TYPE 2580 SYNTAX InterfaceIndex 2581 MAX-ACCESS not-accessible 2583 draft ATM Management Objects April 4, 1998 2585 STATUS current 2586 DESCRIPTION 2587 "The ifIndex value of the ATM interface for 2588 this VP cross-connect. The term high implies that 2589 this ATM interface has the numerically higher 2590 ifIndex value than the other ATM interface 2591 identified in the same atmVpCrossConnectEntry." 2592 ::= { atmVpCrossConnectEntry 4 } 2594 atmVpCrossConnectHighVpi OBJECT-TYPE 2595 SYNTAX AtmVpIdentifier 2596 MAX-ACCESS not-accessible 2597 STATUS current 2598 DESCRIPTION 2599 "The VPI value at the ATM interface 2600 associated with the VP cross-connect that is 2601 identified by atmVpCrossConnectHighIfIndex." 2602 ::= { atmVpCrossConnectEntry 5 } 2604 atmVpCrossConnectAdminStatus OBJECT-TYPE 2605 SYNTAX AtmVorXAdminStatus 2606 MAX-ACCESS read-create 2607 STATUS current 2608 DESCRIPTION 2609 "The desired administrative status of this 2610 bi-directional VP cross-connect." 2611 DEFVAL { down } 2612 ::= { atmVpCrossConnectEntry 6 } 2614 atmVpCrossConnectL2HOperStatus OBJECT-TYPE 2615 SYNTAX AtmVorXOperStatus 2616 MAX-ACCESS read-only 2617 STATUS current 2618 DESCRIPTION 2619 "The operational status of the VP cross-connect 2620 in one direction; (i.e., from the low to 2621 high direction)." 2622 ::= { atmVpCrossConnectEntry 7 } 2624 atmVpCrossConnectH2LOperStatus OBJECT-TYPE 2625 SYNTAX AtmVorXOperStatus 2626 MAX-ACCESS read-only 2627 STATUS current 2628 DESCRIPTION 2629 "The operational status of the VP cross-connect 2631 draft ATM Management Objects April 4, 1998 2633 in one direction; (i.e., from the high to 2634 low direction)." 2635 ::= { atmVpCrossConnectEntry 8 } 2637 atmVpCrossConnectL2HLastChange OBJECT-TYPE 2638 SYNTAX AtmVorXLastChange 2639 MAX-ACCESS read-only 2640 STATUS current 2641 DESCRIPTION 2642 "The value of sysUpTime at the time this 2643 VP cross-connect entered its current operational 2644 state in the low to high direction." 2645 ::= { atmVpCrossConnectEntry 9 } 2647 atmVpCrossConnectH2LLastChange OBJECT-TYPE 2648 SYNTAX AtmVorXLastChange 2649 MAX-ACCESS read-only 2650 STATUS current 2651 DESCRIPTION 2652 "The value of sysUpTime at the time this 2653 VP cross-connect entered its current operational 2654 in the high to low direction." 2655 ::= { atmVpCrossConnectEntry 10 } 2657 atmVpCrossConnectRowStatus OBJECT-TYPE 2658 SYNTAX RowStatus 2659 MAX-ACCESS read-create 2660 STATUS current 2661 DESCRIPTION 2662 "The status of this entry in the 2663 atmVpCrossConnectTable. This object is used to 2664 create a cross-connect for cross-connecting 2665 VPLs which are created using the atmVplTable 2666 or to change or delete an existing cross-connect. 2667 This object must be initially set 2668 to `createAndWait' or 'createAndGo'. 2669 To turn on a VP cross-connect, 2670 the atmVpCrossConnectAdminStatus 2671 is set to `up'." 2672 DEFVAL { active } 2673 ::= { atmVpCrossConnectEntry 11 } 2675 draft ATM Management Objects April 4, 1998 2677 -- ATM Virtual Channel (VC) Cross Connect Table 2679 -- This table contains configuration and state 2680 -- information of point-to-point, 2681 -- point-to-multipoint or multipoint-to-multipoint 2682 -- VC cross-connects for PVCs. 2684 -- This table has read-create access and is used 2685 -- to cross-connect the VCLs together in an ATM switch 2686 -- or network that belong to a VC connection. 2687 -- The atmVcCrossConnectIndex is used to associate 2688 -- the related VCLs that are cross-connected together. 2690 -- The model using step-wise procedures described for setting 2691 -- up a VP cross-connect is also used for setting up 2692 -- a VC cross-connect. 2694 atmVcCrossConnectIndexNext OBJECT-TYPE 2695 SYNTAX INTEGER (0..2147483647) 2696 MAX-ACCESS read-only 2697 STATUS current 2698 DESCRIPTION 2699 "This object contains an appropriate value to 2700 be used for atmVcCrossConnectIndex when creating 2701 entries in the atmVcCrossConnectTable. The value 2702 0 indicates that no unassigned entries are 2703 available. To obtain the atmVcCrossConnectIndex 2704 value for a new entry, the manager issues a 2705 management protocol retrieval operation to obtain 2706 the current value of this object. After each 2707 retrieval, the agent should modify the value to 2708 the next unassigned index." 2709 ::= { atmMIBObjects 10 } 2711 -- The ATM VC Cross Connect Table 2713 atmVcCrossConnectTable OBJECT-TYPE 2714 SYNTAX SEQUENCE OF AtmVcCrossConnectEntry 2715 MAX-ACCESS not-accessible 2716 STATUS current 2718 draft ATM Management Objects April 4, 1998 2720 DESCRIPTION 2721 "The ATM VC Cross Connect table for PVCs. 2722 An entry in this table models two 2723 cross-connected VCLs. 2724 Each VCL must have its atmConnKind set 2725 to pvc(1)." 2726 ::= { atmMIBObjects 11 } 2728 atmVcCrossConnectEntry OBJECT-TYPE 2729 SYNTAX AtmVcCrossConnectEntry 2730 MAX-ACCESS not-accessible 2731 STATUS current 2732 DESCRIPTION 2733 "An entry in the ATM VC Cross Connect table. 2734 This entry is used to model a bi-directional ATM 2735 VC cross-connect cross-connecting two end points. 2737 Step-wise Procedures to set up a VC Cross-connect 2739 Once the entries in the atmVclTable are created, 2740 the following procedures are used 2741 to cross-connect the VCLs together to 2742 form a VCC segment. 2744 (1) The manager obtains a unique 2745 atmVcCrossConnectIndex by reading the 2746 atmVcCrossConnectIndexNext object. 2748 (2) Next, the manager creates a set of one 2749 or more rows in the ATM VC Cross Connect 2750 Table, one for each cross-connection between 2751 two VCLs. Each row is indexed by the ATM 2752 interface port numbers and VPI/VCI values of 2753 the two ends of that cross-connection. 2754 This set of rows specifies the topology of the 2755 VCC cross-connect and is identified by a single 2756 value of atmVcCrossConnectIndex. 2758 Negotiated VC Cross-Connect Establishment 2760 (2a) The manager creates a row in this table by 2761 setting atmVcCrossConnectRowStatus to 2762 createAndWait(5). The agent checks the 2763 requested topology and the mutual sanity of 2764 the ATM traffic parameters and 2766 draft ATM Management Objects April 4, 1998 2768 service categories, i.e., the row creation 2769 fails if: 2770 - the requested topology is incompatible with 2771 associated values of atmVclCastType, 2772 - the requested topology is not supported 2773 by the agent, 2774 - the traffic/service category parameter values 2775 associated with the requested row are 2776 incompatible with those of already existing 2777 rows for this VC cross-connect. 2778 [For example, for setting up 2779 a point-to-point VC cross-connect, the 2780 ATM traffic parameters in the receive direction 2781 of a VCL at the low end of the cross-connect 2782 must equal to the traffic parameters in the 2783 transmit direction of the other VCL at the 2784 high end of the cross-connect, 2785 otherwise, the row creation fails.] 2786 The agent also checks for internal errors 2787 in building the cross-connect. 2789 The atmVcCrossConnectIndex values in the 2790 corresponding atmVclTable rows are filled 2791 in by the agent at this point. 2793 (2b) The manager promotes the row in the 2794 atmVcCrossConnectTable by setting 2795 atmVcCrossConnectRowStatus to active(1). If 2796 this set is successful, the agent has reserved 2797 the resources specified by the ATM traffic 2798 parameter and Service category values 2799 for each direction of the VC cross-connect 2800 in an ATM switch or network. 2802 (3) The manager sets the 2803 atmVcCrossConnectAdminStatus to up(1) 2804 in all rows of this VC cross-connect to 2805 turn the traffic flow on. 2807 One-Shot VC Cross-Connect Establishment 2809 A VC cross-connect may also be established in 2810 one step by a set-request with all necessary 2811 parameter values and atmVcCrossConnectRowStatus 2813 draft ATM Management Objects April 4, 1998 2815 set to createAndGo(4). 2817 In contrast to the negotiated VC cross-connect 2818 establishment which allows for detailed error 2819 checking i.e., set errors are explicitly linked to 2820 particular resource acquisition failures), the 2821 one-shot VC cross-connect establishment 2822 performs the setup on one operation but does 2823 not have the advantage of step-wise error 2824 checking. 2826 VC Cross-Connect Retirement 2828 A VC cross-connect identified by a particular 2829 value of atmVcCrossConnectIndex is released by: 2831 (1) Setting atmVcCrossConnectRowStatus of all rows 2832 identified by this value of 2833 atmVcCrossConnectIndex to destroy(6). 2834 The agent may release all 2835 associated resources, and the 2836 atmVcCrossConnectIndex values in the 2837 corresponding atmVclTable row are removed. 2838 Note that a situation when only a subset of 2839 the associated rows are deleted corresponds 2840 to a VC topology change. 2842 (2) After deletion of the appropriate 2843 atmVcCrossConnectEntries, the manager may 2844 set atmVclRowStatus to destroy(6) the 2845 associated VCLs. The agent releases 2846 the resources and removes the associated 2847 rows in the atmVclTable. 2849 VC Cross-Connect Reconfiguration 2851 At the discretion of the agent, a VC 2852 cross-connect may be reconfigured by 2853 adding and/or deleting leafs to/from 2854 the VC topology as per the VC cross-connect 2855 establishment/retirement procedures. 2856 Reconfiguration of traffic/service category parameter 2857 values requires release of the VC cross-connect 2858 before those parameter values may by changed 2859 for individual VCLs." 2861 draft ATM Management Objects April 4, 1998 2863 INDEX { atmVcCrossConnectIndex, 2864 atmVcCrossConnectLowIfIndex, 2865 atmVcCrossConnectLowVpi, 2866 atmVcCrossConnectLowVci, 2867 atmVcCrossConnectHighIfIndex, 2868 atmVcCrossConnectHighVpi, 2869 atmVcCrossConnectHighVci } 2870 ::= { atmVcCrossConnectTable 1 } 2872 AtmVcCrossConnectEntry ::= SEQUENCE { 2873 atmVcCrossConnectIndex INTEGER, 2874 atmVcCrossConnectLowIfIndex InterfaceIndex, 2875 atmVcCrossConnectLowVpi AtmVpIdentifier, 2876 atmVcCrossConnectLowVci AtmVcIdentifier, 2877 atmVcCrossConnectHighIfIndex InterfaceIndex, 2878 atmVcCrossConnectHighVpi AtmVpIdentifier, 2879 atmVcCrossConnectHighVci AtmVcIdentifier, 2880 atmVcCrossConnectAdminStatus AtmVorXAdminStatus, 2881 atmVcCrossConnectL2HOperStatus AtmVorXOperStatus, 2882 atmVcCrossConnectH2LOperStatus AtmVorXOperStatus, 2883 atmVcCrossConnectL2HLastChange AtmVorXLastChange, 2884 atmVcCrossConnectH2LLastChange AtmVorXLastChange, 2885 atmVcCrossConnectRowStatus RowStatus 2886 } 2888 atmVcCrossConnectIndex OBJECT-TYPE 2889 SYNTAX INTEGER (1..2147483647) 2890 MAX-ACCESS not-accessible 2891 STATUS current 2892 DESCRIPTION 2893 "A unique value to identify this VC cross-connect. 2894 For each VCL associated with this cross-connect, 2895 the agent reports this cross-connect index value 2896 in the atmVclCrossConnectIdentifier attribute of 2897 the corresponding atmVclTable entries." 2898 ::= { atmVcCrossConnectEntry 1 } 2900 atmVcCrossConnectLowIfIndex OBJECT-TYPE 2901 SYNTAX InterfaceIndex 2902 MAX-ACCESS not-accessible 2903 STATUS current 2904 DESCRIPTION 2905 "The ifIndex value of the ATM interface for this 2906 VC cross-connect. The term low implies 2907 that this ATM interface has the numerically lower 2909 draft ATM Management Objects April 4, 1998 2911 ifIndex value than the other ATM interface 2912 identified in the same atmVcCrossConnectEntry." 2913 ::= { atmVcCrossConnectEntry 2 } 2915 atmVcCrossConnectLowVpi OBJECT-TYPE 2916 SYNTAX AtmVpIdentifier 2917 MAX-ACCESS not-accessible 2918 STATUS current 2919 DESCRIPTION 2920 "The VPI value at the ATM interface 2921 associated with the VC cross-connect that is 2922 identified by atmVcCrossConnectLowIfIndex." 2923 ::= { atmVcCrossConnectEntry 3 } 2925 atmVcCrossConnectLowVci OBJECT-TYPE 2926 SYNTAX AtmVcIdentifier 2927 MAX-ACCESS not-accessible 2928 STATUS current 2929 DESCRIPTION 2930 "The VCI value at the ATM interface 2931 associated with this VC cross-connect that is 2932 identified by atmVcCrossConnectLowIfIndex." 2933 ::= { atmVcCrossConnectEntry 4 } 2935 atmVcCrossConnectHighIfIndex OBJECT-TYPE 2936 SYNTAX InterfaceIndex 2937 MAX-ACCESS not-accessible 2938 STATUS current 2939 DESCRIPTION 2940 "The ifIndex value for the ATM interface for 2941 this VC cross-connect. The term high implies 2942 that this ATM interface has the numerically higher 2943 ifIndex value than the other ATM interface 2944 identified in the same atmVcCrossConnectEntry." 2945 ::= { atmVcCrossConnectEntry 5 } 2947 atmVcCrossConnectHighVpi OBJECT-TYPE 2948 SYNTAX AtmVpIdentifier 2949 MAX-ACCESS not-accessible 2950 STATUS current 2951 DESCRIPTION 2952 "The VPI value at the ATM interface 2953 associated with the VC cross-connect that is 2954 identified by atmVcCrossConnectHighIfIndex." 2955 ::= { atmVcCrossConnectEntry 6 } 2957 draft ATM Management Objects April 4, 1998 2959 atmVcCrossConnectHighVci OBJECT-TYPE 2960 SYNTAX AtmVcIdentifier 2961 MAX-ACCESS not-accessible 2962 STATUS current 2963 DESCRIPTION 2964 "The VCI value at the ATM interface 2965 associated with the VC cross-connect that is 2966 identified by atmVcCrossConnectHighIfIndex." 2967 ::= { atmVcCrossConnectEntry 7 } 2969 atmVcCrossConnectAdminStatus OBJECT-TYPE 2970 SYNTAX AtmVorXAdminStatus 2971 MAX-ACCESS read-create 2972 STATUS current 2973 DESCRIPTION 2974 "The desired administrative status of this 2975 bi-directional VC cross-connect." 2976 DEFVAL { down } 2977 ::= { atmVcCrossConnectEntry 8 } 2979 atmVcCrossConnectL2HOperStatus OBJECT-TYPE 2980 SYNTAX AtmVorXOperStatus 2981 MAX-ACCESS read-only 2982 STATUS current 2983 DESCRIPTION 2984 "The current operational status of the 2985 VC cross-connect in one direction; (i.e., 2986 from the low to high direction)." 2987 ::= { atmVcCrossConnectEntry 9 } 2989 atmVcCrossConnectH2LOperStatus OBJECT-TYPE 2990 SYNTAX AtmVorXOperStatus 2991 MAX-ACCESS read-only 2992 STATUS current 2993 DESCRIPTION 2994 "The current operational status of the 2995 VC cross-connect in one direction; (i.e., 2996 from the high to low direction)." 2997 ::= { atmVcCrossConnectEntry 10 } 2999 atmVcCrossConnectL2HLastChange OBJECT-TYPE 3000 SYNTAX AtmVorXLastChange 3001 MAX-ACCESS read-only 3002 STATUS current 3004 draft ATM Management Objects April 4, 1998 3006 DESCRIPTION 3007 "The value of sysUpTime at the time this 3008 VC cross-connect entered its current 3009 operational state in low to high direction." 3010 ::= { atmVcCrossConnectEntry 11 } 3012 atmVcCrossConnectH2LLastChange OBJECT-TYPE 3013 SYNTAX AtmVorXLastChange 3014 MAX-ACCESS read-only 3015 STATUS current 3016 DESCRIPTION 3017 "The value of sysUpTime at the time this 3018 VC cross-connect entered its current 3019 operational state in high to low direction." 3020 ::= { atmVcCrossConnectEntry 12 } 3022 atmVcCrossConnectRowStatus OBJECT-TYPE 3023 SYNTAX RowStatus 3024 MAX-ACCESS read-create 3025 STATUS current 3026 DESCRIPTION 3027 "The status of this entry in the 3028 atmVcCrossConnectTable. This object is used to 3029 create a new cross-connect for cross-connecting 3030 VCLs which are created using the atmVclTable 3031 or to change or delete existing cross-connect. 3032 This object must be initially set to 3033 `createAndWait' or 'createAndGo'. 3034 To turn on a VC cross-connect, 3035 the atmVcCrossConnectAdminStatus 3036 is set to `up'." 3037 DEFVAL { active } 3038 ::= { atmVcCrossConnectEntry 13 } 3040 draft ATM Management Objects April 4, 1998 3042 -- AAL5 Virtual Channel Connection Performance Statistics 3043 -- Table 3045 -- This table contains the AAL5 3046 -- performance statistics of a VCC at the 3047 -- interface associated with an AAL5 entity in an ATM 3048 -- host or ATM switch. 3050 aal5VccTable OBJECT-TYPE 3051 SYNTAX SEQUENCE OF Aal5VccEntry 3052 MAX-ACCESS not-accessible 3053 STATUS current 3054 DESCRIPTION 3055 "This table contains AAL5 VCC performance 3056 parameters." 3057 ::= { atmMIBObjects 12 } 3059 aal5VccEntry OBJECT-TYPE 3060 SYNTAX Aal5VccEntry 3061 MAX-ACCESS not-accessible 3062 STATUS current 3063 DESCRIPTION 3064 "This list contains the AAL5 VCC 3065 performance parameters." 3066 INDEX { ifIndex, aal5VccVpi, aal5VccVci } 3067 ::= { aal5VccTable 1 } 3069 Aal5VccEntry ::= SEQUENCE { 3070 aal5VccVpi AtmVpIdentifier, 3071 aal5VccVci AtmVcIdentifier, 3072 aal5VccCrcErrors Counter32, 3073 aal5VccSarTimeOuts Counter32, 3074 aal5VccOverSizedSDUs Counter32 3075 } 3077 aal5VccVpi OBJECT-TYPE 3078 SYNTAX AtmVpIdentifier 3079 MAX-ACCESS not-accessible 3080 STATUS current 3081 DESCRIPTION 3082 "The VPI value of the AAL5 VCC at the 3083 interface identified by the ifIndex." 3084 ::= { aal5VccEntry 1 } 3086 draft ATM Management Objects April 4, 1998 3088 aal5VccVci OBJECT-TYPE 3089 SYNTAX AtmVcIdentifier 3090 MAX-ACCESS not-accessible 3091 STATUS current 3092 DESCRIPTION 3093 "The VCI value of the AAL5 VCC at the 3094 interface identified by the ifIndex." 3095 ::= { aal5VccEntry 2 } 3097 aal5VccCrcErrors OBJECT-TYPE 3098 SYNTAX Counter32 3099 MAX-ACCESS read-only 3100 STATUS current 3101 DESCRIPTION 3102 "The number of AAL5 CPCS PDUs received with 3103 CRC-32 errors on this AAL5 VCC at the 3104 interface associated with an AAL5 entity." 3105 ::= { aal5VccEntry 3 } 3107 aal5VccSarTimeOuts OBJECT-TYPE 3108 SYNTAX Counter32 3109 MAX-ACCESS read-only 3110 STATUS current 3111 DESCRIPTION 3112 "The number of partially re-assembled AAL5 3113 CPCS PDUs which were discarded 3114 on this AAL5 VCC at the interface associated 3115 with an AAL5 entity because they 3116 were not fully re-assembled within the 3117 required time period. If the re-assembly 3118 timer is not supported, then this object 3119 contains a zero value." 3120 ::= { aal5VccEntry 4 } 3122 aal5VccOverSizedSDUs OBJECT-TYPE 3123 SYNTAX Counter32 3124 MAX-ACCESS read-only 3125 STATUS current 3126 DESCRIPTION 3127 "The number of AAL5 CPCS PDUs discarded 3128 on this AAL5 VCC at the interface 3129 associated with an AAL5 entity because the 3130 AAL5 SDUs were too large." 3131 ::= { aal5VccEntry 5 } 3133 draft ATM Management Objects April 4, 1998 3135 -- 3136 -- The following object may be used in conjunction with 3137 -- the atmTrafficDescrParamTable for the creation of 3138 -- new table entries. 3139 -- 3141 atmTrafficDescrParamIndexNext OBJECT-TYPE 3142 SYNTAX INTEGER (0..2147483647) 3143 MAX-ACCESS read-only 3144 STATUS current 3145 DESCRIPTION 3146 "This object contains an appropriate value to 3147 be used for atmTrafficDescrParamIndex when 3148 creating entries in the 3149 atmTrafficDescrParamTable. 3150 The value 0 indicates that no unassigned 3151 entries are available. To obtain the 3152 atmTrafficDescrParamIndex value for a new 3153 entry, the manager issues a management 3154 protocol retrieval operation to obtain the 3155 current value of this object. After each 3156 retrieval, the agent should modify the value 3157 to the next unassigned index." 3158 ::= { atmMIBObjects 13 } 3160 draft ATM Management Objects April 4, 1998 3162 -- Conformance Information 3164 atmMIBConformance OBJECT IDENTIFIER ::= { atmMIB 2 } 3166 atmMIBGroups OBJECT IDENTIFIER 3167 ::= { atmMIBConformance 1 } 3168 atmMIBCompliances OBJECT IDENTIFIER 3169 ::= { atmMIBConformance 2 } 3171 -- Compliance Statements 3173 atmMIBCompliance2 MODULE-COMPLIANCE 3174 STATUS current 3175 DESCRIPTION 3176 "The compliance statement for SNMP entities 3177 including networks which have ATM and 3178 AAL5 interfaces." 3180 MODULE -- this module 3181 -- 3182 -- ****** Interface and Traffic Descriptor Support *** 3183 -- 3184 MANDATORY-GROUPS {atmInterfaceConfGroup2, 3185 atmTrafficDescrGroup2 } 3187 OBJECT atmInterfaceMaxVpcs 3188 MIN-ACCESS read-only 3189 DESCRIPTION 3190 "Write access is not required." 3192 OBJECT atmInterfaceMaxVccs 3193 MIN-ACCESS read-only 3194 DESCRIPTION 3195 "Write access is not required." 3197 OBJECT atmInterfaceMaxActiveVpiBits 3198 MIN-ACCESS read-only 3199 DESCRIPTION 3200 "Write access is not required. 3201 At the ATM UNI the maximum number of 3202 active VPI bits configured for use ranges 3203 from 0 to 8 only. 3204 Implementations may support smaller ranges." 3206 draft ATM Management Objects April 4, 1998 3208 OBJECT atmInterfaceMaxActiveVciBits 3209 MIN-ACCESS read-only 3210 DESCRIPTION 3211 "Write access is not required. 3212 Implementations may support smaller ranges." 3214 OBJECT atmInterfaceIlmiVpi 3215 MIN-ACCESS read-only 3216 DESCRIPTION 3217 "Write access is not required." 3219 OBJECT atmInterfaceIlmiVci 3220 MIN-ACCESS read-only 3221 DESCRIPTION 3222 "Write access is not required." 3224 OBJECT atmInterfaceMyNeighborIpAddress 3225 MIN-ACCESS read-only 3226 DESCRIPTION 3227 "Write access is not required." 3229 OBJECT atmInterfaceMyNeighborIfName 3230 MIN-ACCESS read-only 3231 DESCRIPTION 3232 "Write access is not required." 3234 OBJECT atmInterfaceSubscrAddress 3235 MIN-ACCESS read-only 3236 DESCRIPTION 3237 "Write access is not required." 3239 OBJECT atmTrafficDescrParamIndexNext 3240 DESCRIPTION 3241 "This object is only required for systems 3242 that support the creation of entries in 3243 the atmTrafficDescrParamTable." 3245 OBJECT atmTrafficDescrType 3246 MIN-ACCESS read-only 3247 DESCRIPTION 3248 "Write access is not required." 3250 OBJECT atmTrafficDescrParam1 3251 MIN-ACCESS read-only 3252 DESCRIPTION 3254 draft ATM Management Objects April 4, 1998 3256 "Write access is not required." 3258 OBJECT atmTrafficDescrParam2 3259 MIN-ACCESS read-only 3260 DESCRIPTION 3261 "Write access is not required." 3263 OBJECT atmTrafficDescrParam3 3264 MIN-ACCESS read-only 3265 DESCRIPTION 3266 "Write access is not required." 3268 OBJECT atmTrafficDescrParam4 3269 MIN-ACCESS read-only 3270 DESCRIPTION 3271 "Write access is not required." 3273 OBJECT atmTrafficDescrParam5 3274 MIN-ACCESS read-only 3275 DESCRIPTION 3276 "Write access is not required." 3278 OBJECT atmServiceCategory 3279 MIN-ACCESS read-only 3280 DESCRIPTION 3281 "Write access is not required." 3283 OBJECT atmTrafficDescrRowStatus 3284 SYNTAX INTEGER {active(1)} 3285 -- subset of RowStatus 3286 MIN-ACCESS read-only 3287 DESCRIPTION 3288 "Write access is not required, and only one 3289 of the six enumerated values for the 3290 RowStatus textual convention need be 3291 supported, specifically: active(1)." 3293 OBJECT atmTrafficFrameDiscard 3294 MIN-ACCESS read-only 3295 DESCRIPTION 3296 "Write access is not required." 3298 -- 3299 -- ****** DS3 PLCP Support ************************** 3300 -- 3302 draft ATM Management Objects April 4, 1998 3304 GROUP atmInterfaceDs3PlcpGroup 3305 DESCRIPTION 3306 "This group is mandatory only for those 3307 ATM interfaces which implement the 3308 DS3 PLCP layer." 3309 -- 3310 -- ****** TC Sublayer Support ******************************** 3311 -- 3312 GROUP atmInterfaceTCGroup 3313 DESCRIPTION 3314 "This group is mandatory only for those 3315 ATM interfaces which implement the 3316 TC Sublayer." 3318 -- 3319 -- ****** VPC Support ******************************* 3320 -- 3321 GROUP atmVpcTerminationGroup2 3322 DESCRIPTION 3323 "This group is mandatory only for those 3324 ATM interfaces which implement ATM 3325 VPLs that terminate VPCs (i.e., ones which 3326 are NOT cross-connected to other VPLs)." 3328 GROUP atmVplCrossConnectGroup 3329 DESCRIPTION 3330 "This group is mandatory only for those 3331 ATM interfaces which implement ATM 3332 VPLs that are not associated with VCLs 3333 and are cross-connected to other VPLs 3334 for VPCs." 3336 GROUP atmVpPvcCrossConnectGroup 3337 DESCRIPTION 3338 "This group is mandatory only for those 3339 ATM interfaces which implement ATM 3340 VPLs that are not associated with VCLs 3341 and are cross-connected to other VPLs 3342 for permanent VPCs (i.e., PVCs). 3343 This group is not used to crossconnect 3344 a PVC with an SVC to form a Soft PVC." 3346 OBJECT atmVplAdminStatus 3347 MIN-ACCESS read-only 3348 DESCRIPTION 3350 draft ATM Management Objects April 4, 1998 3352 "Write access is not required." 3354 OBJECT atmVplReceiveTrafficDescrIndex 3355 MIN-ACCESS read-only 3356 DESCRIPTION 3357 "Write access is not required." 3359 OBJECT atmVplTransmitTrafficDescrIndex 3360 MIN-ACCESS read-only 3361 DESCRIPTION 3362 "Write access is not required." 3364 OBJECT atmVplRowStatus 3365 SYNTAX INTEGER {active(1)} 3366 -- subset of RowStatus 3367 MIN-ACCESS read-only 3368 DESCRIPTION 3369 "Write access is not required, and only one 3370 of the six enumerated values for the 3371 RowStatus textual convention need be 3372 supported, specifically: active(1)." 3374 OBJECT atmVplCastType 3375 MIN-ACCESS read-only 3376 DESCRIPTION 3377 "Write access is not required." 3379 OBJECT atmVplConnKind 3380 MIN-ACCESS read-only 3381 DESCRIPTION 3382 "Write access is not required." 3384 OBJECT atmVpCrossConnectAdminStatus 3385 MIN-ACCESS read-only 3386 DESCRIPTION 3387 "Write access is not required." 3389 OBJECT atmVpCrossConnectRowStatus 3390 SYNTAX INTEGER {active(1)} 3391 -- subset of RowStatus 3392 MIN-ACCESS read-only 3393 DESCRIPTION 3394 "Write access is not required, and only one 3395 of the six enumerated values for the 3396 RowStatus textual convention need be 3398 draft ATM Management Objects April 4, 1998 3400 supported, specifically: active(1)." 3402 -- 3403 -- ****** VCC Support ******************************* 3404 -- 3405 GROUP atmVccTerminationGroup2 3406 DESCRIPTION 3407 "This group is mandatory only for those 3408 ATM interfaces which implement ATM 3409 VCLs that terminate VCCs (i.e., ones which 3410 are NOT cross-connected to other VCLs)." 3412 GROUP atmVclCrossConnectGroup 3413 DESCRIPTION 3414 "This group is mandatory only for those 3415 ATM interfaces which implement ATM 3416 VCLs that are cross-connected to other VCLs 3417 for VCCs." 3419 GROUP atmVcPvcCrossConnectGroup 3420 DESCRIPTION 3421 "This group is mandatory only for those 3422 ATM interfaces which implement ATM 3423 VCLs that are cross-connected to other 3424 VCLs for permanent VCCs (i.e., PVCs). 3425 This group is not used to crossconnect 3426 a PVC with an SVC to form a Soft PVC." 3428 OBJECT atmVclAdminStatus 3429 MIN-ACCESS read-only 3430 DESCRIPTION 3431 "Write access is not required." 3433 OBJECT atmVclReceiveTrafficDescrIndex 3434 MIN-ACCESS read-only 3435 DESCRIPTION 3436 "Write access is not required." 3438 OBJECT atmVclTransmitTrafficDescrIndex 3439 MIN-ACCESS read-only 3440 DESCRIPTION 3441 "Write access is not required." 3443 OBJECT atmVccAalType 3444 MIN-ACCESS read-only 3446 draft ATM Management Objects April 4, 1998 3448 DESCRIPTION 3449 "Write access is not required." 3451 OBJECT atmVclRowStatus 3452 SYNTAX INTEGER {active(1)} 3453 -- subset of RowStatus 3454 MIN-ACCESS read-only 3455 DESCRIPTION 3456 "Write access is not required, and only one 3457 of the six enumerated values for the 3458 RowStatus textual convention need be 3459 supported, specifically: active(1)." 3461 OBJECT atmVclCastType 3462 MIN-ACCESS read-only 3463 DESCRIPTION 3464 "Write access is not required." 3466 OBJECT atmVclConnKind 3467 MIN-ACCESS read-only 3468 DESCRIPTION 3469 "Write access is not required." 3471 OBJECT atmVcCrossConnectAdminStatus 3472 MIN-ACCESS read-only 3473 DESCRIPTION 3474 "Write access is not required." 3476 OBJECT atmVcCrossConnectRowStatus 3477 SYNTAX INTEGER { active(1)} 3478 -- subset of RowStatus 3479 MIN-ACCESS read-only 3480 DESCRIPTION 3481 "Write access is not required, and only one 3482 of the six enumerated values for the 3483 RowStatus textual convention need be 3484 supported, specifically: active(1)." 3485 -- 3486 -- ****** AAL5 Support ****************************** 3487 -- 3488 GROUP aal5VccGroup 3489 DESCRIPTION 3490 "This group is mandatory for the 3491 AAL5 virtual connections only." 3493 draft ATM Management Objects April 4, 1998 3495 OBJECT atmVccAal5CpcsTransmitSduSize 3496 MIN-ACCESS read-only 3497 DESCRIPTION 3498 "Write access is not required." 3500 OBJECT atmVccAal5CpcsReceiveSduSize 3501 MIN-ACCESS read-only 3502 DESCRIPTION 3503 "Write access is not required." 3505 OBJECT atmVccAal5EncapsType 3506 MIN-ACCESS read-only 3507 DESCRIPTION 3508 "Write access is not required." 3509 ::= { atmMIBCompliances 2 } 3511 draft ATM Management Objects April 4, 1998 3513 -- Units of Conformance 3515 atmInterfaceDs3PlcpGroup OBJECT-GROUP 3516 OBJECTS {atmInterfaceDs3PlcpSEFSs, 3517 atmInterfaceDs3PlcpAlarmState, 3518 atmInterfaceDs3PlcpUASs} 3519 STATUS current 3520 DESCRIPTION 3521 "A collection of objects providing information 3522 about DS3 PLCP layer at an ATM interface." 3523 ::= { atmMIBGroups 3 } 3525 atmInterfaceTCGroup OBJECT-GROUP 3526 OBJECTS { atmInterfaceOCDEvents, 3527 atmInterfaceTCAlarmState } 3528 STATUS current 3529 DESCRIPTION 3530 "A collection of objects providing information 3531 about TC sublayer at an ATM interface." 3532 ::= { atmMIBGroups 4 } 3534 aal5VccGroup OBJECT-GROUP 3535 OBJECTS {atmVccAal5CpcsTransmitSduSize, 3536 atmVccAal5CpcsReceiveSduSize, 3537 atmVccAal5EncapsType, 3538 aal5VccCrcErrors, aal5VccSarTimeOuts, 3539 aal5VccOverSizedSDUs } 3540 STATUS current 3541 DESCRIPTION 3542 "A collection of objects providing 3543 AAL5 configuration and performance statistics 3544 of a VCC." 3545 ::= { atmMIBGroups 9 } 3547 atmInterfaceConfGroup2 OBJECT-GROUP 3548 OBJECTS { 3549 atmInterfaceMaxVpcs, atmInterfaceMaxVccs, 3550 atmInterfaceConfVpcs, atmInterfaceConfVccs, 3551 atmInterfaceMaxActiveVpiBits, 3552 atmInterfaceMaxActiveVciBits, 3553 atmInterfaceIlmiVpi, 3554 atmInterfaceIlmiVci, 3555 atmInterfaceMyNeighborIpAddress, 3556 atmInterfaceMyNeighborIfName, 3557 atmInterfaceCurrentMaxVpiBits, 3559 draft ATM Management Objects April 4, 1998 3561 atmInterfaceCurrentMaxVciBits, 3562 atmInterfaceSubscrAddress } 3563 STATUS current 3564 DESCRIPTION 3565 "A collection of objects providing configuration 3566 information about an ATM interface." 3567 ::= { atmMIBGroups 10 } 3569 atmTrafficDescrGroup2 OBJECT-GROUP 3570 OBJECTS { 3571 atmTrafficDescrType, atmTrafficDescrParam1, 3572 atmTrafficDescrParam2, atmTrafficDescrParam3, 3573 atmTrafficDescrParam4, atmTrafficDescrParam5, 3574 atmTrafficDescrRowStatus, atmServiceCategory, 3575 atmTrafficFrameDiscard, 3576 atmTrafficDescrParamIndexNext } 3577 STATUS current 3578 DESCRIPTION 3579 "A collection of objects providing information 3580 about ATM traffic descriptor type and 3581 the associated parameters." 3582 ::= { atmMIBGroups 11 } 3584 atmVpcTerminationGroup2 OBJECT-GROUP 3585 OBJECTS {atmVplOperStatus, atmVplAdminStatus, 3586 atmVplLastChange, 3587 atmVplReceiveTrafficDescrIndex, 3588 atmVplTransmitTrafficDescrIndex, 3589 atmVplRowStatus, atmVplCastType, 3590 atmVplConnKind } 3591 STATUS current 3592 DESCRIPTION 3593 "A collection of objects providing information 3594 about a VPL at an ATM interface which 3595 terminates a VPC (i.e., one which is NOT 3596 cross-connected to other VPLs)." 3597 ::= { atmMIBGroups 12 } 3599 atmVccTerminationGroup2 OBJECT-GROUP 3600 OBJECTS {atmVclOperStatus, atmVclAdminStatus, 3601 atmVclLastChange, 3602 atmVclReceiveTrafficDescrIndex, 3603 atmVclTransmitTrafficDescrIndex, 3604 atmVccAalType, atmVclRowStatus, 3605 atmVclCastType, atmVclConnKind } 3607 draft ATM Management Objects April 4, 1998 3609 STATUS current 3610 DESCRIPTION 3611 "A collection of objects providing information 3612 about a VCL at an ATM interface 3613 which terminates a VCC (i.e., one which is 3614 NOT cross-connected to other VCLs)." 3615 ::= { atmMIBGroups 13 } 3617 atmVplCrossConnectGroup OBJECT-GROUP 3618 OBJECTS { atmVplReceiveTrafficDescrIndex, 3619 atmVplTransmitTrafficDescrIndex, 3620 atmVplOperStatus, atmVplLastChange, 3621 atmVplRowStatus, 3622 atmVplCastType, atmVplConnKind } 3623 STATUS current 3624 DESCRIPTION 3625 "A collection of objects providing 3626 information about the VPLs that 3627 are cross-connected together." 3628 ::= { atmMIBGroups 14 } 3630 atmVpPvcCrossConnectGroup OBJECT-GROUP 3631 OBJECTS { atmVpCrossConnectAdminStatus, 3632 atmVpCrossConnectL2HOperStatus, 3633 atmVpCrossConnectH2LOperStatus, 3634 atmVpCrossConnectL2HLastChange, 3635 atmVpCrossConnectH2LLastChange, 3636 atmVpCrossConnectRowStatus, 3637 atmVplCrossConnectIdentifier, 3638 atmVpCrossConnectIndexNext } 3639 STATUS current 3640 DESCRIPTION 3641 "A collection of objects providing 3642 information about a VP cross-connect 3643 for PVCs. These objects are not used 3644 for Soft PVCs or SVCs." 3645 ::= { atmMIBGroups 15 } 3647 atmVclCrossConnectGroup OBJECT-GROUP 3648 OBJECTS { atmVclReceiveTrafficDescrIndex, 3649 atmVclTransmitTrafficDescrIndex, 3650 atmVclOperStatus, atmVclLastChange, 3651 atmVclRowStatus, 3652 atmVclCastType, atmVclConnKind } 3653 STATUS current 3655 draft ATM Management Objects April 4, 1998 3657 DESCRIPTION 3658 "A collection of objects providing 3659 information about the VCLs that 3660 are cross-connected together." 3661 ::= { atmMIBGroups 16 } 3663 atmVcPvcCrossConnectGroup OBJECT-GROUP 3664 OBJECTS { atmVcCrossConnectAdminStatus, 3665 atmVcCrossConnectL2HOperStatus, 3666 atmVcCrossConnectH2LOperStatus, 3667 atmVcCrossConnectL2HLastChange, 3668 atmVcCrossConnectH2LLastChange, 3669 atmVcCrossConnectRowStatus, 3670 atmVclCrossConnectIdentifier, 3671 atmVcCrossConnectIndexNext } 3672 STATUS current 3673 DESCRIPTION 3674 "A collection of objects providing 3675 information about a VC cross-connect 3676 for PVCs. These objects are not used 3677 for Soft PVCs or SVCs." 3678 ::= { atmMIBGroups 17 } 3680 draft ATM Management Objects April 4, 1998 3682 -- Deprecated Definitions - Objects 3684 -- atmInterfaceAddressType 3685 -- atmTrafficQoSClass 3687 -- Deprecated Definitions - Compliance 3689 atmMIBCompliance MODULE-COMPLIANCE 3690 STATUS deprecated 3691 DESCRIPTION 3692 "The compliance statement for SNMP entities 3693 including networks which have ATM and 3694 AAL5 interfaces." 3696 MODULE -- this module 3697 MANDATORY-GROUPS {atmInterfaceConfGroup, 3698 atmTrafficDescrGroup} 3700 OBJECT atmInterfaceMaxVpcs 3701 MIN-ACCESS read-only 3702 DESCRIPTION 3703 "Write access is not required." 3705 OBJECT atmInterfaceMaxVccs 3706 MIN-ACCESS read-only 3707 DESCRIPTION 3708 "Write access is not required." 3710 OBJECT atmInterfaceMaxActiveVpiBits 3711 MIN-ACCESS read-only 3712 DESCRIPTION 3713 "Write access is not required." 3715 OBJECT atmInterfaceMaxActiveVciBits 3716 MIN-ACCESS read-only 3717 DESCRIPTION 3718 "Write access is not required." 3720 OBJECT atmInterfaceIlmiVpi 3721 MIN-ACCESS read-only 3722 DESCRIPTION 3723 "Write access is not required." 3725 OBJECT atmInterfaceIlmiVci 3727 draft ATM Management Objects April 4, 1998 3729 MIN-ACCESS read-only 3730 DESCRIPTION 3731 "Write access is not required." 3733 OBJECT atmInterfaceMyNeighborIpAddress 3734 MIN-ACCESS read-only 3735 DESCRIPTION 3736 "Write access is not required." 3738 OBJECT atmInterfaceMyNeighborIfName 3739 MIN-ACCESS read-only 3740 DESCRIPTION 3741 "Write access is not required." 3743 OBJECT atmTrafficDescrType 3744 MIN-ACCESS read-only 3745 DESCRIPTION 3746 "Write access is not required." 3748 OBJECT atmTrafficDescrParam1 3749 MIN-ACCESS read-only 3750 DESCRIPTION 3751 "Write access is not required." 3753 OBJECT atmTrafficDescrParam2 3754 MIN-ACCESS read-only 3755 DESCRIPTION 3756 "Write access is not required." 3758 OBJECT atmTrafficDescrParam3 3759 MIN-ACCESS read-only 3760 DESCRIPTION 3761 "Write access is not required." 3763 OBJECT atmTrafficDescrParam4 3764 MIN-ACCESS read-only 3765 DESCRIPTION 3766 "Write access is not required." 3768 OBJECT atmTrafficDescrParam5 3769 MIN-ACCESS read-only 3770 DESCRIPTION 3771 "Write access is not required." 3773 OBJECT atmTrafficQoSClass 3775 draft ATM Management Objects April 4, 1998 3777 MIN-ACCESS read-only 3778 DESCRIPTION 3779 "Write access is not required." 3781 OBJECT atmTrafficDescrRowStatus 3782 SYNTAX INTEGER {active(1)} 3783 -- subset of RowStatus 3784 MIN-ACCESS read-only 3785 DESCRIPTION 3786 "Write access is not required, and only one 3787 of the six enumerated values for the 3788 RowStatus textual convention need be 3789 supported, specifically: active(1)." 3791 GROUP atmInterfaceDs3PlcpGroup 3792 DESCRIPTION 3793 "This group is mandatory only for those 3794 ATM interfaces which implement the 3795 DS3 PLCP layer." 3797 GROUP atmInterfaceTCGroup 3798 DESCRIPTION 3799 "This group is mandatory only for those 3800 ATM interfaces which implement the 3801 TC Sublayer." 3803 GROUP atmVpcTerminationGroup 3804 DESCRIPTION 3805 "This group is mandatory only for those 3806 ATM interfaces which implement ATM 3807 VPLs that terminate VPCs (i.e., ones which 3808 are NOT cross-connected to other VPLs)." 3810 GROUP atmVpCrossConnectGroup 3811 DESCRIPTION 3812 "This group is mandatory only for those 3813 ATM interfaces which implement ATM 3814 VPLs that are not associated with VCLs 3815 and are cross-connected to other VPLs." 3817 OBJECT atmVplAdminStatus 3818 MIN-ACCESS read-only 3819 DESCRIPTION 3820 "Write access is not required." 3822 draft ATM Management Objects April 4, 1998 3824 OBJECT atmVplReceiveTrafficDescrIndex 3825 MIN-ACCESS read-only 3826 DESCRIPTION 3827 "Write access is not required." 3829 OBJECT atmVplTransmitTrafficDescrIndex 3830 MIN-ACCESS read-only 3831 DESCRIPTION 3832 "Write access is not required." 3834 OBJECT atmVplRowStatus 3835 SYNTAX INTEGER {active(1)} 3836 -- subset of RowStatus 3837 MIN-ACCESS read-only 3838 DESCRIPTION 3839 "Write access is not required, and only one 3840 of the six enumerated values for the 3841 RowStatus textual convention need be 3842 supported, specifically: active(1)." 3844 OBJECT atmVpCrossConnectAdminStatus 3845 MIN-ACCESS read-only 3846 DESCRIPTION 3847 "Write access is not required." 3849 OBJECT atmVpCrossConnectRowStatus 3850 SYNTAX INTEGER {active(1)} 3851 -- subset of RowStatus 3852 MIN-ACCESS read-only 3853 DESCRIPTION 3854 "Write access is not required, and only one 3855 of the six enumerated values for the 3856 RowStatus textual convention need be 3857 supported, specifically: active(1)." 3859 GROUP atmVccTerminationGroup 3860 DESCRIPTION 3861 "This group is mandatory only for those 3862 ATM interfaces which implement ATM 3863 VCLs that terminate VCCs (i.e., ones which 3864 are NOT cross-connected to other VCLs)." 3866 GROUP atmVcCrossConnectGroup 3867 DESCRIPTION 3868 "This group is mandatory only for those 3870 draft ATM Management Objects April 4, 1998 3872 ATM interfaces which implement ATM 3873 VCLs that are cross-connected to 3874 other VCLs." 3876 OBJECT atmVclAdminStatus 3877 MIN-ACCESS read-only 3878 DESCRIPTION 3879 "Write access is not required." 3881 OBJECT atmVclReceiveTrafficDescrIndex 3882 MIN-ACCESS read-only 3883 DESCRIPTION 3884 "Write access is not required." 3886 OBJECT atmVclTransmitTrafficDescrIndex 3887 MIN-ACCESS read-only 3888 DESCRIPTION 3889 "Write access is not required." 3891 OBJECT atmVccAalType 3892 MIN-ACCESS read-only 3893 DESCRIPTION 3894 "Write access is not required." 3896 OBJECT atmVclRowStatus 3897 SYNTAX INTEGER {active(1)} 3898 -- subset of RowStatus 3899 MIN-ACCESS read-only 3900 DESCRIPTION 3901 "Write access is not required, and only one 3902 of the six enumerated values for the 3903 RowStatus textual convention need be 3904 supported, specifically: active(1)." 3906 OBJECT atmVcCrossConnectAdminStatus 3907 MIN-ACCESS read-only 3908 DESCRIPTION 3909 "Write access is not required." 3911 OBJECT atmVcCrossConnectRowStatus 3912 SYNTAX INTEGER { active(1)} 3913 -- subset of RowStatus 3914 MIN-ACCESS read-only 3915 DESCRIPTION 3916 "Write access is not required, and only one 3918 draft ATM Management Objects April 4, 1998 3920 of the six enumerated values for the 3921 RowStatus textual convention need be 3922 supported, specifically: active(1)." 3924 GROUP aal5VccGroup 3925 DESCRIPTION 3926 "This group is mandatory for the 3927 AAL5 virtual connections only." 3929 OBJECT atmVccAal5CpcsTransmitSduSize 3930 MIN-ACCESS read-only 3931 DESCRIPTION 3932 "Write access is not required." 3934 OBJECT atmVccAal5CpcsReceiveSduSize 3935 MIN-ACCESS read-only 3936 DESCRIPTION 3937 "Write access is not required." 3939 OBJECT atmVccAal5EncapsType 3940 MIN-ACCESS read-only 3941 DESCRIPTION 3942 "Write access is not required." 3943 ::= { atmMIBCompliances 1 } 3945 -- Deprecated Definitions - Groups 3947 atmInterfaceConfGroup OBJECT-GROUP 3948 OBJECTS { 3949 atmInterfaceMaxVpcs, atmInterfaceMaxVccs, 3950 atmInterfaceConfVpcs, atmInterfaceConfVccs, 3951 atmInterfaceMaxActiveVpiBits, 3952 atmInterfaceMaxActiveVciBits, 3953 atmInterfaceIlmiVpi, 3954 atmInterfaceIlmiVci, 3955 atmInterfaceAddressType, 3956 atmInterfaceAdminAddress, 3957 atmInterfaceMyNeighborIpAddress, 3958 atmInterfaceMyNeighborIfName } 3959 STATUS deprecated 3960 DESCRIPTION 3961 "A collection of objects providing configuration 3962 information about an ATM interface." 3964 draft ATM Management Objects April 4, 1998 3966 ::= { atmMIBGroups 1 } 3968 atmTrafficDescrGroup OBJECT-GROUP 3969 OBJECTS { 3970 atmTrafficDescrType, atmTrafficDescrParam1, 3971 atmTrafficDescrParam2, atmTrafficDescrParam3, 3972 atmTrafficDescrParam4, atmTrafficDescrParam5, 3973 atmTrafficQoSClass, atmTrafficDescrRowStatus} 3974 STATUS deprecated 3975 DESCRIPTION 3976 "A collection of objects providing information 3977 about ATM traffic descriptor type and 3978 the associated parameters." 3979 ::= { atmMIBGroups 2 } 3981 atmVpcTerminationGroup OBJECT-GROUP 3982 OBJECTS {atmVplOperStatus, atmVplAdminStatus, 3983 atmVplLastChange, 3984 atmVplReceiveTrafficDescrIndex, 3985 atmVplTransmitTrafficDescrIndex, 3986 atmVplRowStatus } 3987 STATUS deprecated 3988 DESCRIPTION 3989 "A collection of objects providing 3990 information about a VPL at an ATM interface 3991 which terminates a VPC 3992 (i.e., one which is NOT cross-connected 3993 to other VPLs)." 3994 ::= { atmMIBGroups 5 } 3996 atmVccTerminationGroup OBJECT-GROUP 3997 OBJECTS {atmVclOperStatus, atmVclAdminStatus, 3998 atmVclLastChange, 3999 atmVclReceiveTrafficDescrIndex, 4000 atmVclTransmitTrafficDescrIndex, 4001 atmVccAalType, atmVclRowStatus } 4002 STATUS deprecated 4003 DESCRIPTION 4004 "A collection of objects providing information 4005 about a VCL at an ATM interface 4006 which terminates a VCC (i.e., one which is 4007 NOT cross-connected to other VCLs)." 4008 ::= { atmMIBGroups 6 } 4010 atmVpCrossConnectGroup OBJECT-GROUP 4012 draft ATM Management Objects April 4, 1998 4014 OBJECTS { atmVplReceiveTrafficDescrIndex, 4015 atmVplTransmitTrafficDescrIndex, 4016 atmVplOperStatus, atmVplRowStatus, 4017 atmVpCrossConnectAdminStatus, 4018 atmVpCrossConnectL2HOperStatus, 4019 atmVpCrossConnectH2LOperStatus, 4020 atmVpCrossConnectL2HLastChange, 4021 atmVpCrossConnectH2LLastChange, 4022 atmVpCrossConnectRowStatus, 4023 atmVplCrossConnectIdentifier, 4024 atmVpCrossConnectIndexNext } 4025 STATUS deprecated 4026 DESCRIPTION 4027 "A collection of objects providing 4028 information about a VP cross-connect 4029 and the associated VPLs that are 4030 cross-connected together." 4031 ::= { atmMIBGroups 7 } 4033 atmVcCrossConnectGroup OBJECT-GROUP 4034 OBJECTS { atmVclReceiveTrafficDescrIndex, 4035 atmVclTransmitTrafficDescrIndex, 4036 atmVclOperStatus, atmVclRowStatus, 4037 atmVcCrossConnectAdminStatus, 4038 atmVcCrossConnectL2HOperStatus, 4039 atmVcCrossConnectH2LOperStatus, 4040 atmVcCrossConnectL2HLastChange, 4041 atmVcCrossConnectH2LLastChange, 4042 atmVcCrossConnectRowStatus, 4043 atmVclCrossConnectIdentifier, 4044 atmVcCrossConnectIndexNext } 4045 STATUS deprecated 4046 DESCRIPTION 4047 "A collection of objects providing 4048 information about a VC cross-connect 4049 and the associated VCLs that are 4050 cross-connected together." 4051 ::= { atmMIBGroups 8 } 4053 -- {atmMIB 3} has been used by [8]. 4055 END 4057 draft ATM Management Objects April 4, 1998 4059 12. Acknowledgments 4061 This memo is the result of the work of the AToMMIB Working 4062 Group. 4064 draft ATM Management Objects April 4, 1998 4066 13. References 4068 [1] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., 4069 and S. Waldbusser, "Structure of Management Information 4070 for version 2 of the Simple Network Management Protocol 4071 (SNMPv2)", RFC 1902, January 1996. 4073 [2] McCloghrie, K., and M. Rose, Editors, "Management 4074 Information Base for Network Management of TCP/IP-based 4075 internets: MIB-II", STD 17, RFC 1213, Hughes LAN Systems, 4076 Performance Systems International, March 1991. 4078 [3] Case, J., Fedor, M., Schoffstall, M., and J. Davin, 4079 "Simple Network Management Protocol", RFC 1157, SNMP 4080 Research, Performance Systems International, Performance 4081 Systems International, MIT Laboratory for Computer 4082 Science, May 1990. 4084 [4] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., 4085 and S. Waldbusser, "Protocol Operations for version 2 of 4086 the Simple Network Management Protocol (SNMPv2)", RFC 4087 1905, January 1996. 4089 [5] McCloghrie, K. and F. Kastenholz, "The Interfaces Group 4090 MIB", RFC2233, cisco Systems, FTP Software, November 4091 1997. 4093 [6] Brown, T.A. and K. Tesink, "Definitions of Managed 4094 Objects for SMDS Interfaces", RFC 1694, Bellcore, May 4095 1994. 4097 [7] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 4098 "Textual Conventions for version 2 of the Simple Network 4099 Management Protocol (SNMPv2)", RFC1903, SNMP 4100 Research,Inc., Hughes LAN Systems, Dover Beach 4101 Consulting, Inc., Carnegie Mellon University, April 1993. 4103 [8] Michael Noto, Kaj Tesink, "ATM Textual Conventions and 4104 OBJECT-IDENTITIES", Internet-Draft, Bellcore, April 1998. 4106 [9] "ATM Forum UNI Specification, Version 3.0", September 4107 1993. 4109 [10] "ATM Forum B-ICI Specification, Version 1.0", September 4110 1993. 4112 draft ATM Management Objects April 4, 1998 4114 [11] "ATM Forum Private Network-Network Interface 4115 Specification, Version 1.0 (PNNI 1.0)", af-sig-0055.000, 4116 March 1996. 4118 [12] "ATM Forum Integrated Local Management Interface (ILMI) 4119 Specification", Version 4.0", af-ilmi-0065.000, September 4120 1996. 4122 draft ATM Management Objects April 4, 1998 4124 14. Security Considerations 4126 This MIB contains both readable objects whose values provide 4127 the number and status of a device's network interfaces, and 4128 write-able objects which allow an administrator to control the 4129 interfaces and to perform tests on the interfaces. 4130 Unauthorized access to the readable objects is relatively 4131 innocuous. Unauthorized access to the write- able objects 4132 could cause a denial of service, or in combination with other 4133 (e.g., physical) security breaches, could cause unauthorized 4134 connectivity to a device. 4136 15. Author's Address 4138 Kaj Tesink 4139 Bell Communications Research 4140 331 Newman Springs Road 4141 P.O. Box 7020 4142 Red Bank, NJ 07701-7020 4143 Phone: (908) 758-5254 4144 EMail: kaj@cc.bellcore.com 4146 draft ATM Management Objects April 4, 1998 4148 Table of Contents 4150 1 Status of this Memo ................................... 1 4151 2 Introduction .......................................... 2 4152 3 The SNMP Network Management Framework ................. 2 4153 4 Object Definitions .................................... 3 4154 5 ATM Terminology ....................................... 4 4155 5.1 VCL/VPL and VCC/VPC ................................. 4 4156 5.2 PVC, SVC and Soft PVC ............................... 6 4157 5.3 Traffic Management Parameters ....................... 7 4158 5.3.1 Traffic Policing and Traffic Shaping Parameters 4159 .................................................... 7 4160 5.3.2 Cell Loss Priority ................................ 7 4161 5.3.3 QoS Class ......................................... 8 4162 5.3.4 Service Category .................................. 8 4163 5.4 Max Active and Max Current VPI and VCI Bits ......... 8 4164 6 Overview .............................................. 9 4165 6.1 Background .......................................... 10 4166 6.2 Structure of the MIB ................................ 10 4167 6.3 ATM Interface Configuration Table ................... 10 4168 6.4 ATM Interface DS3 PLCP and TC Layer Tables .......... 11 4169 6.5 ATM Virtual Link and Cross-Connect Tables ........... 11 4170 7 Application of MIB II to ATM .......................... 12 4171 7.1 The System Group .................................... 12 4172 7.2 The Interface Group ................................. 12 4173 7.2.1 Support of the ATM Cell Layer by ifTable .......... 12 4174 8 Support of the AAL3/4 Based Interfaces ................ 14 4175 9 Support of the AAL5 Managed Objects ................... 15 4176 9.1 Managing AAL5 in a Switch ........................... 15 4177 9.2 Managing AAL5 in a Host ............................. 16 4178 9.3 Support of AAL5 by ifTable .......................... 18 4179 9.4 Support of Proprietary Virtual Interface by ifT- 4180 able ............................................... 20 4181 9.5 AAL5 Connection Performance Statistics Table ........ 21 4182 10 ILMI MIBs and the ATM Managed Objects ................ 22 4183 11 Definitions .......................................... 26 4184 12 Acknowledgments ...................................... 97 4185 13 References ........................................... 98 4186 14 Security Considerations .............................. 100 4187 15 Author's Address ..................................... 100