idnits 2.17.1 draft-ietf-atommib-atm1ng-01.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-26) 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 101 longer pages, the longest (page 2) being 112 lines == It seems as if not all pages are separated by form feeds - found 0 form feeds but 102 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: ' 15. 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 9 instances of too long lines in the document, the longest one being 7 characters in excess of 72. Miscellaneous warnings: ---------------------------------------------------------------------------- == Line 294 has weird spacing: '... |svc svc...' == Line 414 has weird spacing: '...pported supp...' == Line 1136 has weird spacing: '...rrently estab...' == Line 1156 has weird spacing: '...rrently estab...' == Line 1165 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 (June 26, 1996) is 10166 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 4013 looks like a reference -- Missing reference section? '2' on line 4018 looks like a reference -- Missing reference section? '3' on line 4023 looks like a reference -- Missing reference section? '4' on line 4029 looks like a reference -- Missing reference section? '7' on line 4042 looks like a reference -- Missing reference section? '8' on line 4048 looks like a reference -- Missing reference section? '11' on line 4059 looks like a reference -- Missing reference section? '9' on line 4051 looks like a reference -- Missing reference section? '5' on line 4034 looks like a reference -- Missing reference section? '6' on line 4038 looks like a reference -- Missing reference section? '10' on line 4054 looks like a reference Summary: 14 errors (**), 0 flaws (~~), 10 warnings (==), 12 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 June 26, 1996 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 June 26, 1996 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. Change Log 46 This section tracks changes made to the revisions of this 47 document. It will be deleted when the document is published as 48 an RFC. The following changes were made for the version of 49 the document dated June 26, 1996. These changes were made as a 50 result of the comments provided by the AToM MIB Working Group 51 on RFC1695. 53 0 atmConnKind inserted 55 0 Soft PVC text /P-NNI reference fixed. 57 0 Sect. 6.3.1 sentence "including one for best effort" 58 removed (misleading and in error). 60 0 Sect. 6.3.4 - Fixed issue that Vls may not have the same 61 service category. 63 0 atmInterfaceAddressType is deprecated - rationale: 64 redundant. 66 0 atmInterfaceAdminAddress DESCRIPTION fixed. 68 0 atmVpl/VclRowStatus modified for consistency with DEFVALs 69 of the TrafficDescrIndices. 71 0 atmVccAalType has DEFVAL {aal5} 73 draft ATM Management Objects June 26, 1996 75 0 Editorials, references, etc. fixed. 77 Still to be done: 79 0 Conformance statement updates & PVC/SVC conformance 80 requirements. 82 The following changes were made for the version of the 83 document dated April 6, 1996. These changes were made as a 84 result of the comments provided by the AToM MIB Working Group 85 on RFC1695. 87 0 Remove IfIndex TC. Move AtmTrafficDescrParamIndex and all 88 OBJECT IDENTITIES to a separate document. Import 89 InterfaceIndex, AtmVpIdentifier, AtmVcIdentifier, 90 AtmTrafficDescrParamIndex, AtmConnCastType, 91 AtmVorXAdminStatus, AtmVorXOperStatus, AtmVorXLastChange 92 FROM ATM-TC-MIB and simplify DESCRIPTION clauses 93 accordingly. 95 0 Fix AtmTrafficDescrParamIndex=0 case (in ATM-TC-MIB) - 96 i.e., no row is identified. 98 0 Clarify that the ifIndex value in the 99 atmInterfaceConfTable as well as in the DS3PLCP and TC 100 Tables refers to the ATM interface. 102 0 Clarify that Vxl/XConnectOperStatus goes down/unknown if 103 underlying ATM goes down/unknown. 105 0 Replace atmTrafficQosClass with atmServiceCategory. 106 Leading text regarding QoS is fixed. 108 0 Introduce new objects for atmInterfaceMaxBits/Vxcs etc. 109 and introduce a leading text section on this include 110 figure. 112 0 Fix Conformance statement according with additions. 114 0 Extended 4.2 with a descriptive line on SPVCs since we 115 use that in the interface table. 117 0 DEFVAL atmVpl/VclTransmit/ReceiveDescrIndex, 118 atmVclAdminStatus, atmVcCrossConnectRowStatus. 120 draft ATM Management Objects June 26, 1996 122 0 Clarify the implication of the existence of the 123 atmVccAal5 objects (see atmVclRowStatus). 125 0 Introduce atmVplCastType and atmVclCastType. Fix 126 procedure description regarding use of atmVxlCastType 128 0 Email 1/10/95 on chicken&egg problem - included a 129 qualification in item (3) of atmVclEntry 131 0 Some editorials. 133 Still to be done: 135 0 Is there an issue on what atmInterfaceAddressType refers 136 to (refers to ifPhysAddr or atmInterfaceAdminAddr - what 137 to do if there is no address, etc.). 139 0 Fix references 141 4. The SNMPv2 Network Management Framework 143 The SNMPv2 Network Management Framework consists of four major 144 components. They are: 146 0 RFC 1902 [1] which defines the SMI, the mechanisms used 147 for describing and naming objects for the purpose of 148 management. 150 0 STD 17, RFC 1213 [2] defines MIB-II, the core set of 151 managed objects for the Internet suite of protocols. 153 0 RFC 1157 [3] and RFC1905 [4] which define two versions of 154 the protocol used for network access to managed objects. 156 The Framework permits new objects to be defined for the 157 purpose of experimentation and evaluation. 159 Textual Conventions used in this MIB are defined in [7] and 160 [8]. 162 draft ATM Management Objects June 26, 1996 164 5. Object Definitions 166 Managed objects are accessed via a virtual information store, 167 termed the Management Information Base or MIB. Objects in the 168 MIB are defined using the subset of Abstract Syntax Notation 169 One (ASN.1) defined in the SMI. In particular, each object 170 type is named by an OBJECT IDENTIFIER, an administratively 171 assigned name. The object type together with an object 172 instance serves to uniquely identify a specific instantiation 173 of the object. For human convenience, we often use a textual 174 string, termed the descriptor, to also refer to the object 175 type. 177 draft ATM Management Objects June 26, 1996 179 6. ATM Terminology 181 Some basic ATM terminologies are described in this section to 182 facilitate defining the ATM managed objects. 184 6.1. VCL/VPL and VCC/VPC 186 There are two distinct types of ATM virtual connections: 187 Virtual Channel Connections (VCCs) and Virtual Path Connection 188 (VPCs). As shown in Figures 1 and 2, ATM virtual connections 189 consist of concatenated series of virtual links which forms a 190 path between two end points, with each concatenation occurring 191 at an ATM switch. Virtual links of VCCs are called Virtual 192 Channel Links (VCLs). Virtual links of VPCs are called Virtual 193 Path Links (VPLs). The VCI and VPI fields in the ATM cell 194 header associate each cell of a VCC with a particular VCL over 195 a given physical link. The VPI field in the ATM cell header 196 associates each cell of a VPC with a particular VPL over a 197 given physical link. Switches route cells between VCLs (or 198 VPLs) via a cross-connect function according to the cells' 199 VCI/VPI (or VPI) values. 201 <-----------------------VCC--------------------------> 202 ------------ ----------- 203 |ATM | |ATM | 204 |X-Connect | |X-Connect | 205 VCL1 |Point | VCL2 |Point | VCL3 206 O---------|----X-----|-------|-----|----X-----|-------O 207 | | | | 208 ------------ ------------ 209 ATM Switch ATM Switch 211 Figure 1: Virtual Channel Links and 212 Virtual Channel Connection 214 draft ATM Management Objects June 26, 1996 216 <-----------------------VPC--------------------------> 217 ------------ ----------- 218 |ATM | |ATM | 219 |X-Connect | |X-Connect | 220 VPL1 |Point | VPL2 |Point | VPL3 221 O---------|----X-----|-------|-----|----X-----|-------O 222 | | | | 223 ------------ ------------ 224 ATM Switch ATM Switch 226 Figure 2: Virtual Path Links and 227 Virtual Path Connection 229 A single ATM end-system or switch does not support the whole 230 end-to-end span of a VCC (or VPC). Rather, multiple ATM end- 231 systems and/or switches each support one piece of the VCC (or 232 VPC). That is, each ATM end-system at one end of the VCC/VPC 233 supports its end of the VCC/VPC plus the VCLs or VPLs on its 234 external interfaces, and each switch through which the VCC/VPC 235 passes, supports the multiple VCLs/VPLs on that switch's 236 external interfaces and the cross-connection of those 237 VCLs/VPLs through that switch. Thus, the end-to-end 238 management of a VCC or VPC is achieved only by appropriate 239 management of its individual pieces in combination. 241 Note that for management purposes, an ATM network may be 242 viewed as a large distributed switch by hiding all the 243 network's internal connectivity as being internal to the 244 distributed switch (as shown in Figure 2a). This model may 245 for example be used for Customer Network Management (CNM) 246 purposes. 248 draft ATM Management Objects June 26, 1996 250 <---------------------VCC---------------------------> 251 -------------------------------------- 252 | | 253 | ---------- ---------- | 254 | | ATM | | ATM | | 255 VCL1 | | Switch | | Switch | | VCL3 256 O-------|-|--------|------/-------|--------|-|------O 257 | | | | | | 258 | ---------- ---------- | 259 | | 260 | ATM Network | 261 -------------------------------------- 263 Figure 2a: ATM Network modeled as a large distributed 264 switch 266 A VCC has a set of traffic characteristics (i.e., bandwidth 267 parameters, service category parameters, etc.). VCLs inherit 268 their traffic characteristics from the VCC of which they are a 269 part. VCCs are bi-directional by definition. However, the 270 traffic parameters in the two directions of a connection can 271 be symmetric or asymmetric, i.e., the two directions can have 272 the same or different traffic flows. A uni-directional 273 traffic flow across a VCC is achieved by assigning a zero 274 bandwidth in one direction. Note that in addition to the 275 bandwidth required by the user traffic flow, bandwidth is also 276 required for OAM cell flows, even for the zero-bandwidth 277 direction of a uni-directional connection. These same 278 principles apply to VPCs. 280 6.2. PVC, SVC and Soft PVC 282 A Permanent Virtual Connection (PVC) is a provisioned VCC or 283 VPC. A Switched Virtual Connection (SVC) is a switched VCC or 284 VPC that is set up in real-time via call set-up signaling 285 procedures. A PVC (or an SVC) can be a point-to-point, 286 point-to-multipoint, or multipoint-to-multipoint VCC or VPC. 287 A Soft PVC is a connection of which portions are switched, 288 while other portions are permanent (see Figure 3 and [11]). 290 +--------+ +--------+ +--------+ 292 draft ATM Management Objects June 26, 1996 294 pvc| ATM |svc svc | ATM |svc svc | ATM |pvc 295 ----| Switch |-----------| Switch |-----------| Switch |---- 296 +--------+ +--------+ +--------+ 298 Figure 3: An example of a Soft PVC 300 6.3. Traffic Management Parameters 302 6.3.1. Traffic Policing and Traffic Shaping Parameters 304 In order to allocate resources fairly among different users, 305 some networks police traffic at resource access points. The 306 traffic enforcement or policing taken at a UNI is called Usage 307 Parameter Control (UPC) and is activated on an incoming VCL or 308 VPL as shown in Figure 4. The use of the traffic enforcer at 309 the ingress of the connection is to make sure that the user 310 traffic does not exceed the negotiated traffic parameters such 311 as the peak cell rate associated with a specific traffic 312 descriptor type. 314 ---------- ---------- 315 UNI | ATM | NNI | ATM | UNI 316 | | switch | | | switch | | 317 O<---|---->X(UPC) |<----|------>| (UPC)X<-----|--->O 318 | VCL | | | VCL | | VCL | 319 ---------- ---------- 321 Figure 4: An Example of a UPC 323 In addition, traffic shaping may be performed on an outgoing 324 VPL or VCL at a given ATM interface. The function of the ATM 325 traffic shaper either at the source or an egress point of the 326 connection is to smooth the outgoing cell traffic inter- 327 arrival time. If policing or shaping is not performed then 328 the policing or shaping algorithm is not activated. ATM Forum 329 has specified seven traffic descriptor types [9]. 331 6.3.2. Cell Loss Priority 333 To prioritize traffic during resource congestion, ATM cells 334 are assigned one of the two types of Cell Loss Priority (CLP), 336 draft ATM Management Objects June 26, 1996 338 CLP=0 and CLP=1. ATM cells with CLP=0 have a higher priority 339 in regard to cell loss than ATM cells with CLP=1. Therefore, 340 during resource congestions, CLP=1 cells are dropped before 341 any CLP=0 cell is dropped. 343 6.3.3. QoS Class 345 RFC1695 specified that one of a number of Quality of Service 346 (QoS) classes is assigned to a VCC or VPC by associating the 347 object atmTrafficQoSClass with each VCL or VPL. However, new 348 insights in ATM traffic management have caused this object to 349 be deprecated. 351 6.3.4. Service Category 353 Replacing QoS Class, VPLs and VCLs are qualified in terms of 354 their service category (atmServiceCategory). VCLs (or VPLs) 355 concatenated to form a VCC (or VPC) will all have the same 356 service category class as that of the VCC (or VPC). 358 6.4. Max Active and Max Current VPI and VCI Bits 360 A manager may wish to configure the maximum number of VPI and 361 VCI bits that can be used to identify VPIs and VCIs on a given 362 ATM interface. This value can be less than or equal to the 363 maximum number of bits supported by the interface hardware, 364 and is referred to in the MIB as the Max Active VPI Bits and 365 Max Active VCI Bits. 367 However, a manager may not be able to configure the Max Active 368 Bits on both ends of an ATM link. For example, the manager 369 may not be allowed write access to the peer's MIB, or there 370 may be hardware limitations on the peer device. Therefore, 371 the two ATM devices may use ILMI to negotiate "Max Current" 372 VPI and VCI bits, which is the maximum number of bits that 373 both interfaces are willing to support. This is illustrated 374 in Figure 5. The relationship between the different parameters 375 is illustrated in Figure 6. Note that if ILMI negotiation is 376 not supported, then the devices have no choice but to use the 377 configured MaxActive bits, and assume that it has been 378 configured to the same value on both ends of the link. 380 draft ATM Management Objects June 26, 1996 382 +--------+ +--------+ +--------+ 383 | ATM | IF a IF b | ATM | IF c IF d | ATM | 384 | Device |--------------| Device |--------------| Device | 385 +--------+ +--------+ +--------+ 387 IF a: Max Active VPI Bits = 6 (configured) 388 Max Current VPI Bits = 6 (negotiated) 390 IF b: Max Active VPI Bits = 8 (configured) 391 Max Current VPI Bits = 6 (negotiated) 393 IF c: Max Active VPI Bits = 8 (configured) 394 Max Current VPI Bits = 8 (negotiated) 396 IF d: Max Active VPI Bits = 8 (configured) 397 Max Current VPI Bits = 8 (negotiated) 399 (between IF a and IF b, the minimum of the two configured 400 "Max Active VPI Bits" is 6, so both interfaces set their 401 "Max Current VPI Bits" to 6. Since IF c and IF d both 402 are configured with "Max Active VPI Bits" of 8, they 403 set their "Max Current VPI Bits" to 8.) 405 Figure 5 407 MSB LSB 408 +----------------------------------------------------+ 409 | | | | | 410 +----------------------------------------------------+ 411 ^ ^ ^ ^ 412 | | | | 413 Max bits Max Bits Max Max 414 supported supported Active (config.) current (negotiated) 415 by MIB by h/w Bits Bits 417 Figure 6 419 7. Overview 421 ATM management objects are used to manage ATM interfaces, ATM 422 virtual links, ATM cross-connects, AAL5 entities and AAL5 423 connections supported by ATM hosts, ATM switches and ATM 425 draft ATM Management Objects June 26, 1996 427 networks. This section provides an overview and background of 428 how to use this MIB and other potential MIBs for this purpose. 430 The purpose of this memo is primarily to manage ATM PVCs. ATM 431 SVCs are also represented by the management information in 432 this MIB. However, full management of SVCs may require 433 additional capabilities which are beyond the scope of this 434 memo. 436 7.1. Background 438 In addition to the MIB module defined in this memo, other MIB 439 modules are necessary to manage ATM interfaces, links and 440 cross-connects. Examples include MIB II for general system 441 and interface management [2][5], the DS3 or SONET MIBs for 442 management of physical interfaces, and, as appropriate, MIB 443 modules for applications that make use of ATM, such as SMDS. 444 These MIB modules are outside the scope of this specification. 446 The current specification of this ATM MIB is based on SNMPv2. 448 7.2. Structure of the MIB 450 The managed ATM objects are arranged into the following 451 groups: 452 (1) ATM interface configuration group 453 (2) ATM interface DS3 PLCP group 454 (3) ATM interface TC Sublayer group 455 (4) ATM interface virtual link (VPL/VCL) configuration 456 groups 457 (5) ATM VP/VC cross-connect groups 458 (6) AAL5 connection performance statistics group 460 Note that, managed objects for activation/deactivation of OAM 461 cell flows and ATM traps notifying virtual connection or 462 virtual link failures are outside the scope of this memo. 464 7.3. ATM Interface Configuration Group 466 This group contains information on ATM cell layer 467 configuration of local ATM interfaces on an ATM device in 468 addition to the information on such interfaces contained in 469 the ifTable. 471 draft ATM Management Objects June 26, 1996 473 7.4. ATM Interface DS3 PLCP and TC Layer Groups 475 These groups provide performance statistics of the DS3 PLCP 476 and TC sublayer of local ATM interfaces on a managed ATM 477 device. DS3 PLCP and TC sublayer are currently used to carry 478 ATM cells respectively over DS3 and SONET transmission paths. 480 7.5. ATM Virtual Link and Cross-Connect Groups 482 ATM virtual link and cross-connect groups model bi-directional 483 ATM virtual links and ATM cross-connects. The ATM VP/VC link 484 groups are implemented in an ATM host, ATM switch and ATM 485 network. The ATM switch and ATM network also implement the 486 ATM VP/VC cross-connect groups. Both link and cross-connect 487 groups are implemented in a carrier's network for Customer 488 Network Management (CNM) purposes. 490 The ATM virtual link groups are used to create, delete or 491 modify ATM virtual links in an ATM host, ATM switch and ATM 492 network. ATM virtual link groups along with the cross-connect 493 groups are used to create, delete or modify ATM cross-connects 494 in an ATM switch or ATM network (e.g., for CNM purposes). 496 8. Application of MIB II to ATM 498 8.1. The System Group 500 For the purposes of the sysServices object in the System Group 501 of MIB II [2], ATM is a data link layer protocol. Thus, for 502 ATM switches and ATM networks, sysServices will have the value 503 "2". 505 8.2. The Interface Group 507 The Interfaces Group of MIB II defines generic managed objects 508 for managing interfaces. This memo contains the media- 509 specific extensions to the Interfaces Group for managing ATM 510 interfaces. 512 This memo assumes the interpretation of the Interfaces Group 513 to be in accordance with [5] which states that the interfaces 514 table (ifTable) contains information on the managed resource's 515 interfaces and that each sub-layer below the internetwork 516 layer of a network interface is considered an interface. 518 draft ATM Management Objects June 26, 1996 520 Thus, the ATM cell layer interface is represented as an entry 521 in the ifTable. This entry is concerned with the ATM cell 522 layer as a whole, and not with individual virtual connections 523 which are managed via the ATM-specific managed objects 524 specified in this memo. The inter-relation of entries in the 525 ifTable is defined by Interfaces Stack Group defined in [5]. 527 8.2.1. Support of the ATM Cell Layer by ifTable 529 Some specific interpretations of ifTable for the ATM cell 530 layer follow. 532 draft ATM Management Objects June 26, 1996 534 Object Use for the generic ATM layer 535 ====== ============================= 537 ifIndex Each ATM port is represented by an ifEntry. 539 ifDescr Description of the ATM interface. 541 ifType The value that is allocated for ATM is 37. 543 ifSpeed The total bandwidth in bits per second 544 for use by the ATM layer. 546 ifPhysAddress The interface's address at the ATM protocol 547 sublayer; the ATM address which would be used 548 as the value of the Called Party Address 549 Information Element (IE) of a signalling 550 message for a connection which either: 551 - would terminate at this interface, or 552 - for which the Called Party Address IE 553 would need to be replaced by the Called 554 Party SubAddress IE before the message 555 was forwarded to any other interface. 556 For an interface on which signalling is 557 not supported, then the interface does not 558 necessarily have an address, but if it 559 does, then ifPhysAddress is the address which 560 would be used as above in the event that 561 signalling were supported. If the interface 562 has multiple such addresses, then ifPhysAddress 563 is its primary address. If the interface has 564 no addresses, then ifPhysAddress is an octet 565 string of zero length. Address encoding is as 566 per [9]. Note that addresses assigned for 567 purposes other than those listed above (e.g., 568 an address associated with the service provider 569 side of a public network UNI) may be represented 570 through atmInterfaceAdminAddress. 572 ifAdminStatus See [5]. 574 ifOperStatus Assumes the value down(2) if the ATM cell 575 layer or any layer below that layer is down. 577 ifLastChange See [5]. 579 draft ATM Management Objects June 26, 1996 581 ifInOctets The number of received octets over the 582 interface, i.e., the number of received, 583 assigned cells multiplied by 53. 585 ifOutOctets The number of transmitted octets over the 586 interface, i.e., the number of transmitted, 587 assigned cells multiplied by 53. 589 ifInErrors The number of cells dropped due to 590 uncorrectable HEC errors. 592 ifInUnknownProtos The number of received cells discarded 593 during cell header validation, including 594 cells with unrecognized VPI/VCI values, 595 and cells with invalid cell header patterns. 596 If cells with undefined PTI values are discarded, 597 they are also counted here. 599 ifOutErrors See [5]. 601 ifName Textual name (unique on this system) of the 602 interface or an octet string of zero length. 604 ifLinkUpDownTrapEnable Default is disabled (2). 606 ifConnectorPresent Set to false (2). 608 ifHighSpeed See [5]. 610 ifHCInOctets The 64-bit version of ifInOctets; supported 611 if required by the compliance statements in [5]. 613 ifHCOutOctets The 64-bit version of ifOutOctets; supported 614 if required by the compliance statements in [5]. 616 ifAlias The non-volatile 'alias' name for the interface 617 as specified by a network manager. 619 9. Support of the AAL3/4 Based Interfaces 621 For the management of AAL3/4 CPCS layer, see [6]. 623 draft ATM Management Objects June 26, 1996 625 10. Support of the AAL5 Managed Objects 627 Support of AAL5 managed objects in an ATM switch and ATM host 628 are described below. 630 10.1. Managing AAL5 in a Switch 632 Managing AAL5 in a switch involves: 634 (1) performance management of an AAL5 entity as 635 an internal resource in a switch 637 (2) performance management of AAL5 per virtual connection 639 AAL5 in a switch is modeled as shown in Figure 7 and 8. AAL5 640 will be managed in a switch for only those virtual connections 641 that carry AAL5 and are terminated at the AAL5 entity in the 642 switch. Note that, the virtual channels within the ATM UNIs 643 carrying AAL5 will be switched by the ATM switching fabric 644 (termed as ATM Entity in the figure) to the virtual channels 645 on a proprietary internal interface associated with the AAL5 646 process (termed as AAL5 Entity in the figure). Therefore, 647 performance management of the AAL5 resource in the switch will 648 be modeled using the ifTable through an internal (pseudo-ATM) 649 virtual interface and the AAL5 performance management per 650 virtual connection will be supported using an additional AAL5 651 connection table in the ATM MIB. The association between the 652 AAL5 virtual link at the proprietary virtual, internal 653 interface and the ATM virtual link at the ATM interface will 654 be derived from the virtual channel cross-connect table and 655 the virtual channel link table in the ATM MIB. 657 draft ATM Management Objects June 26, 1996 659 ___________________________ 660 | | 661 | ============= | 662 | | AAL5 | | 663 | | Entity | | 664 | ============= | 665 | | | 666 | -----Prop. Virtual Interface 667 | | | 668 | ============= | 669 | | ATM | | 670 | | Entity | | 671 | ============= | 672 |_____|__|__|__|__|_______| 673 | | | | | 674 ---------------- ATM UNIs 675 | | | | | 676 | | | | | 677 v v v v v 679 Figure 7: Model of an AAL5 Entity in a Switch 681 __________________ 682 | | 683 | AAL5 | 684 |________________| 685 | | 686 | Prop. Virtual | 687 | Interface | 688 |________________| 690 Figure 8: AAL5 Entity's Interface Stack in a Switch 692 10.2. Managing AAL5 in a Host 694 Managing AAL5 in a host involves managing the AAL5 sublayer 695 interface as shown in Figure 9 and 10. The AAL5 sublayer is 696 stacked directly over the ATM sublayer. The ifTable is 697 applied to the AAL5 sublayer as defined in Section 10.3. 699 draft ATM Management Objects June 26, 1996 701 ___________________________ 702 | | 703 | ============= | 704 | | AAL5 | | 705 | | Entity | | 706 | ============= | 707 | | ATM | | 708 | | Entity | | 709 | ============= | 710 |___________|_____________| 711 | 712 __|__ ATM UNI 713 | 714 | 715 v 717 Figure 9: Model of an AAL5 Entity in a Host 719 __________________ 720 | | 721 | AAL5 | 722 |________________| 723 | | 724 | ATM Layer | 725 |________________| 726 | | 727 | Physical Layer| 728 |________________| 730 Figure 10: AAL5 Entity's Interface Stack in a Host 732 draft ATM Management Objects June 26, 1996 734 10.3. Support of AAL5 by ifTable 736 The AAL5 entity in an ATM device (e.g., switch or host) is 737 managed using the ifTable. There are additional counters 738 specified for AAL5 than those specified in the ATM B-ICI 739 document [10]. Specific interpretations of ifTable for the 740 AAL5 CPCS layer are as follows. 742 Object Use for AAL5 CPCS layer entity 743 ====== ============================== 745 ifIndex Each AAL5 entity is represented by an ifEntry. 747 ifDescr Description of the AAL5 entity. 749 ifType The value that is allocated for AAL5 is 49. 751 ifMtu Set to the largest PDU size for the 752 AAL5 CPCS layer that can be processed 753 by the AAL5 entity. 755 ifSpeed Set to 0. 757 ifPhysAddress An octet string of zero length. 759 ifAdminStatus See [5]. 761 ifOperStatus Assumes the value down(2) if the AAL5 or 762 any layer below that layer is down. 764 ifLastChange See [5]. 766 ifInOctets The number of received AAL5 CPCS PDU octets. 768 ifOutOctets The number of AAL5 CPCS PDU octets 769 transmitted. 771 ifInUcastPkts The number of received AAL5 CPCS PDUs passed 772 to a higher-layer. 774 ifOutUcastPkts The number of AAL5 CPCS PDUs received from a 775 higher-layer for transmission. 776 [Note: The number of AAL5 PDUs actually 777 transmitted is the number received from a 778 higher-layer for transmission minus any which 780 draft ATM Management Objects June 26, 1996 782 are counted by ifOutErrors and ifOutDiscards.] 784 ifInErrors Number of errored AAL5 CPCS PDUs received. 785 The types of errors counted include CRC-32 errors, 786 SAR time-out errors, and oversized SDU errors. 788 ifInUnknownProtos Set to 0. 790 ifInDiscards Number of received AAL5 CPCS PDUs discarded. 791 Possible reason may be input buffer overflow. 793 ifOutErrors Number of AAL5 CPCS PDUs that could not 794 be transmitted due to errors. 796 ifOutDiscards Number of AAL5 CPCS PDUs received for 797 transmission that are discarded. 798 Possible reason may be output buffer 799 overflow. 801 ifInMulticastPkts Set to 0. 803 ifInBroadcastPkts Set to 0. 805 ifOutMulticastPkts Set to 0. 807 ifOutBroadcastPkts Set to 0. 809 ifName Textual name (unique on this system) of the 810 AAL5 entity or an octet string of zero length. 812 ifHighSpeed Set to 0. 814 ifConnectorPresent Set to false (2). 816 ifPromiscuousMode Set to false(2). 818 ifLinkUpDownTrapEnable Default is disabled (2). 820 ifAlias The non-volatile 'alias' name for the interface 821 as specified by a network manager. 823 draft ATM Management Objects June 26, 1996 825 10.4. Support of Proprietary Virtual Interface by ifTable 827 Specific interpretations of ifTable for the proprietary 828 virtual, internal interface associated with an AAL5 entity in 829 an ATM switch are as follows. 831 draft ATM Management Objects June 26, 1996 833 Object Use for proprietary virtual, internal interface 834 associated with AAL entities 835 ====== =============================================== 837 ifIndex Each proprietary virtual, internal interface 838 associated with AAL entities is represented by an 839 ifEntry. 841 ifDescr Description of the proprietary virtual, internal 842 interface associated with AAL entities. 844 ifType The value that is allocated for proprietary 845 virtual, internal interface is 53. 847 ifSpeed See [5]. Set to 0 if the speed is not 848 known. 850 ifPhysAddress See [5]. An octet string of zero length 851 if no address is used for this interface. 853 ifAdminStatus See [5]. 855 ifOperStatus See [5]. 857 ifLastChange See [5]. 859 ifName Textual name (unique on this system) of the 860 interface or an octet string of zero length. 862 ifHighSpeed See [5]. Set to 0 if the speed is not known. 864 ifConnectorPresent Set to false (2). 866 ifLinkUpDownTrapEnable Default is disabled (2). 868 ifAlias The non-volatile 'alias' name for the interface 869 as specified by a network manager. 871 10.5. AAL5 Connection Performance Statistics Group 873 An AAL5 connection table is used to provide AAL5 performance 874 information for each AAL5 virtual connection that is 875 terminated at the AAL5 entity contained within an ATM switch 876 or host. 878 draft ATM Management Objects June 26, 1996 880 11. ILMI MIB and the ATM Managed Objects 882 The ILMI MIB is specified by the ATM Forum in UNI 883 specification [9], to manage local ATM UNIs. The support of 884 the ATM management functions by the ILMI MIB and those 885 contained in this memo are compared in Table 1. In this 886 table, "yes" in the "ILMI MIB" column indicates that the 887 management functions are supported by the ILMI MIB. The MIB 888 groups in the "This memo" column are the groups listed in 889 Section 7.2. 891 For that subset of management information which the ILMI MIB 892 and this memo have in common, every effort has been made to 893 retain identical semantics and syntax, even though the MIB 894 objects are identified using different OBJECT IDENTIFIERs. 896 draft ATM Management Objects June 26, 1996 898 Table 1 - Structuring of ATM Managed Objects 900 ______________________________________________________________ 901 | |This |ILMI| 902 ATM Mgmt.Inf. |ATM Managed Objects |memo |MIB | 903 ______________|_________________________________|_______|____| 905 Local Interface Information: 906 _____________________________________________________________ 907 ATM interface:| (1) port identifier |ATM MIB| | 908 physical layer| (2) physical transmission types | gr.1*|yes*| 909 configuration | (3) operational status |MIB II | | 910 | (4) administrative status | | | 911 | (5) last change status | | | 912 _____________________________________________________________ 913 ATM interface:| (1) active VPI/VCI fields |ATM MIB| | 914 cell layer | (2) maximum number of VPCs/VCCs | gr.1 |yes | 915 configuration | (3) configured VPCs/VCCs | | ** | 916 | (4) ILMI VPI/VCI values | | | 917 | (5) ATM address type | | | 918 | (6) ATM administrative address | | | 919 _____________________________________________________________ 920 ATM interface:|(1) received/transmitted cells | | | 921 cell layer |(2) cells with HEC error |MIB II |yes | 922 performance |(3) cell header validation errors| | | 923 _____________________________________________________________ 924 ATM interface:|(1)DS3 PLCP severely errored |ATM MIB| | 925 PLCP & TC | framing seconds | gr.2,3| | 926 layer |(2)DS3 PLCP unavailable seconds | |no | 927 performance |(3)DS3 PLCP alarm state | | | 928 |(4)out of cell delineation events| | | 929 |(5)TC alarm state | | | 930 _____________________________________________________________ 931 VP/VC link: |(1)VPI or VPI/VCI value |ATM MIB| | 932 configuration |(2)VCL or VPL operational status | gr. 4|yes | 933 |(3)VCL/VPL administrative status | |*** | 934 |(4)VCL/VPL last change status | | | 935 |(5)transmit/receive traffic/ | | | 936 | service category parameters | | | 937 |(6)AAL type | | | 938 |(7)transmit/receive AAL5 SDU size| | | 939 |(8)AAL5 encapsulation type | | | 940 _____________________________________________________________ 942 draft ATM Management Objects June 26, 1996 944 _____________________________________________________________ 945 VP/VC |(1)cross-connect identifier | | | 946 Cross-connect:|(2)port identifier of one | | | 947 configuration | end | | | 948 |(3)port identifier of the other |ATM MIB| | 949 | end | gr. 5|no | 950 |(4)VPI or VPI/VCI value | | | 951 | of one end | | | 952 |(5)VPI or VPI/VCI value of | | | 953 | the other end | | | 954 |(6)VC/VP cross-connect | | | 955 | operational status | | | 956 |(7)VC/VP cross-connect | | | 957 | administrative status | | | 958 |(8)VC/VP last change status | | | 959 _____________________________________________________________ 960 VCC AAL5 CPCS |(1)PDUs discarded for CRC errors |ATM MIB| | 961 layer: |(2)PDUs discarded due to | gr.6 | | 962 performance | reassembly time out | |no | 963 |(3)PDUs discarded due to large | | | 964 | SDUs | | | 965 _____________________________________________________________ 966 AAL5 entity: |(1)received/transmitted PDUs | | | 967 |(2)PDUs discarded due to | | | 968 | protocol errors |MIB II |no | 969 |(3)a set of configuration/state | | | 970 | parameters | | | 971 _____________________________________________________________ 973 *The operational, administrative, and last change status of 974 the ATM interface and the physical transmission type shall be 975 supported by the interface table in MIB II [2][5]. ILMI does 976 not contain the administrative and last change status of the 977 ATM interface. 979 ** The ILMI MIB does not contain information on the ATM 980 address type and the ATM administrative address assigned at 981 the ATM interface. 983 ***The ILMI MIB contains local and end-to-end operational 984 status of the VPC/VCC segment. However, it does not contain 985 the VPC/VCC administrative and last change status and the VCC 986 AAL information. 988 draft ATM Management Objects June 26, 1996 990 12. Definitions 992 ATM-MIB DEFINITIONS ::= BEGIN 994 IMPORTS 995 MODULE-IDENTITY, OBJECT-TYPE, OBJECT-IDENTITY, 996 experimental, Counter32, Integer32, IpAddress 997 FROM SNMPv2-SMI 998 TEXTUAL-CONVENTION, DisplayString, 999 TimeStamp, RowStatus 1000 FROM SNMPv2-TC 1001 MODULE-COMPLIANCE, OBJECT-GROUP 1002 FROM SNMPv2-CONF 1003 InterfaceIndex, ifIndex 1004 FROM IF-MIB 1005 mib-2 1006 FROM RFC1213-MIB 1007 AtmConnKind, AtmConnCastType, 1008 AtmServiceCategory, AtmTrafficDescrParamIndex, 1009 AtmVpIdentifier, AtmVcIdentifier, 1010 AtmVorXAdminStatus, AtmVorXLastChange, 1011 AtmVorXOperStatus 1012 FROM ATM-TC-MIB; 1014 atmMIB MODULE-IDENTITY 1015 LAST-UPDATED "9606262245Z" 1016 ORGANIZATION "IETF AToM MIB Working Group" 1017 CONTACT-INFO 1018 " Kaj Tesink 1019 Postal: Bellcore 1020 331 Newman Springs Road 1021 Red Bank, NJ 07701 1022 Tel: 908-758-5254 1023 Fax: 908-758-4177 1024 E-mail: kaj@cc.bellcore.com" 1025 DESCRIPTION 1026 "This is the MIB Module for ATM and AAL5-related 1027 objects for managing ATM interfaces, ATM virtual 1028 links, ATM cross-connects, AAL5 entities, and 1029 and AAL5 connections." 1030 ::= { experimental 41 } 1032 -- **************************************** 1033 -- * Note to RFC editor * 1035 draft ATM Management Objects June 26, 1996 1037 -- * Replace {experimental 41} with * 1038 -- * { mib-2 37 } when publishing this * 1039 -- * MIB as RFC * 1040 -- **************************************** 1042 atmMIBObjects OBJECT IDENTIFIER ::= {atmMIB 1} 1044 draft ATM Management Objects June 26, 1996 1046 -- This ATM MIB Module consists of the following groups: 1047 -- (1) ATM Interface configuration group 1048 -- (2) ATM Interface DS3 PLCP group 1049 -- (3) ATM Interface TC Sublayer group 1050 -- (4) ATM Interface VPL configuration group 1051 -- (5) ATM Interface VCL configuration group 1052 -- (6) ATM VP Cross Connect group (for PVCs) 1053 -- (7) ATM VC Cross Connect group (for PVCs) 1054 -- (8) ATM Interface AAL5 VCC performance statistics 1055 -- group 1057 draft ATM Management Objects June 26, 1996 1059 -- ATM Interface Configuration Parameters Group 1061 -- This group contains ATM specific 1062 -- configuration information associated with 1063 -- an ATM interface beyond those 1064 -- supported using the ifTable. 1066 atmInterfaceConfTable OBJECT-TYPE 1067 SYNTAX SEQUENCE OF AtmInterfaceConfEntry 1068 MAX-ACCESS not-accessible 1069 STATUS current 1070 DESCRIPTION 1071 "This table contains ATM local interface 1072 configuration parameters, one entry per ATM 1073 interface port." 1074 ::= { atmMIBObjects 2 } 1076 atmInterfaceConfEntry OBJECT-TYPE 1077 SYNTAX AtmInterfaceConfEntry 1078 MAX-ACCESS not-accessible 1079 STATUS current 1080 DESCRIPTION 1081 "This list contains ATM interface configuration 1082 parameters and state variables and is indexed 1083 by ifIndex values of ATM interfaces." 1084 INDEX { ifIndex } 1085 ::= { atmInterfaceConfTable 1} 1087 AtmInterfaceConfEntry ::= SEQUENCE { 1088 atmInterfaceMaxVpcs INTEGER, 1089 atmInterfaceMaxVccs INTEGER, 1090 atmInterfaceConfVpcs INTEGER, 1091 atmInterfaceConfVccs INTEGER, 1092 atmInterfaceMaxActiveVpiBits INTEGER, 1093 atmInterfaceMaxActiveVciBits INTEGER, 1094 atmInterfaceIlmiVpi VpIdentifier, 1095 atmInterfaceIlmiVci VcIdentifier, 1096 atmInterfaceAddressType INTEGER, 1097 atmInterfaceAdminAddress AtmAddr, 1098 atmInterfaceMyNeighborIpAddress IpAddress, 1099 atmInterfaceMyNeighborIfName DisplayString, 1100 atmInterfaceCurrentMaxVpiBits INTEGER, 1102 draft ATM Management Objects June 26, 1996 1104 atmInterfaceCurrentMaxVciBits INTEGER 1105 } 1107 atmInterfaceMaxVpcs OBJECT-TYPE 1108 SYNTAX INTEGER (0..4096) 1109 MAX-ACCESS read-write 1110 STATUS current 1111 DESCRIPTION 1112 "The maximum number of VPCs (PVCs and SVCs) 1113 supported at this ATM interface. At the ATM UNI, 1114 the maximum number of VPCs (PVCs and SVCs) 1115 ranges from 0 to 256 only." 1116 ::= { atmInterfaceConfEntry 1} 1118 atmInterfaceMaxVccs OBJECT-TYPE 1119 SYNTAX INTEGER (0..65536) 1120 MAX-ACCESS read-write 1121 STATUS current 1122 DESCRIPTION 1123 "The maximum number of VCCs (PVCs and SVCs) 1124 supported at this ATM interface." 1125 ::= { atmInterfaceConfEntry 2} 1127 atmInterfaceConfVpcs OBJECT-TYPE 1128 SYNTAX INTEGER (0..4096) 1129 MAX-ACCESS read-only 1130 STATUS current 1131 DESCRIPTION 1132 "The number of VPCs (PVC, SPVC and SVC) currently 1133 in use at this ATM interface. It includes 1134 the number of PVCs and SPVCs that are configured 1135 at the interface, plus the number of SVCs 1136 that are currently established at the 1137 interface. 1139 At the ATM UNI, the configured number of 1140 VPCs (PVCs and SVCs) can range from 1141 0 to 256 only." 1142 ::= { atmInterfaceConfEntry 3} 1144 atmInterfaceConfVccs OBJECT-TYPE 1145 SYNTAX INTEGER (0..65536) 1146 MAX-ACCESS read-only 1147 STATUS current 1149 draft ATM Management Objects June 26, 1996 1151 DESCRIPTION 1152 "The number of VCCs (PVC, SPVC and SVC) currently 1153 in use at this ATM interface. It includes 1154 the number of PVCs and SPVCs that are configured 1155 at the interface, plus the number of SVCs 1156 that are currently established at the 1157 interface." 1158 ::= { atmInterfaceConfEntry 4} 1160 atmInterfaceMaxActiveVpiBits OBJECT-TYPE 1161 SYNTAX INTEGER (0..12) 1162 MAX-ACCESS read-write 1163 STATUS current 1164 DESCRIPTION 1165 "The maximum number of active VPI bits 1166 configured for use at the ATM interface. 1167 At the ATM UNI, the maximum number of active 1168 VPI bits configured for use ranges from 1169 0 to 8 only." 1170 ::= { atmInterfaceConfEntry 5} 1172 atmInterfaceMaxActiveVciBits OBJECT-TYPE 1173 SYNTAX INTEGER (0..16) 1174 MAX-ACCESS read-write 1175 STATUS current 1176 DESCRIPTION 1177 "The maximum number of active VCI bits 1178 configured for use at this ATM interface." 1179 ::= { atmInterfaceConfEntry 6} 1181 atmInterfaceIlmiVpi OBJECT-TYPE 1182 SYNTAX VpIdentifier 1183 MAX-ACCESS read-write 1184 STATUS current 1185 DESCRIPTION 1186 "The VPI value of the VCC supporting 1187 the ILMI at this ATM interface. If the values of 1188 atmInterfaceIlmiVpi and atmInterfaceIlmiVci are 1189 both equal to zero then the ILMI is not 1190 supported at this ATM interface." 1191 DEFVAL { 0 } 1192 ::= { atmInterfaceConfEntry 7} 1194 atmInterfaceIlmiVci OBJECT-TYPE 1195 SYNTAX VcIdentifier 1197 draft ATM Management Objects June 26, 1996 1199 MAX-ACCESS read-write 1200 STATUS current 1201 DESCRIPTION 1202 "The VCI value of the VCC supporting 1203 the ILMI at this ATM interface. If the values of 1204 atmInterfaceIlmiVpi and atmInterfaceIlmiVci are 1205 both equal to zero then the ILMI is not 1206 supported at this ATM interface." 1207 DEFVAL { 16 } 1208 ::= { atmInterfaceConfEntry 8} 1210 atmInterfaceAddressType OBJECT-TYPE 1211 SYNTAX INTEGER { 1212 private(1), 1213 nsapE164(2), 1214 nativeE164(3), 1215 other(4) 1216 } 1217 MAX-ACCESS read-only 1218 STATUS deprecated 1219 DESCRIPTION 1220 "The type of primary ATM address configured 1221 for use at this ATM interface." 1222 ::= { atmInterfaceConfEntry 9 } 1224 atmInterfaceAdminAddress OBJECT-TYPE 1225 SYNTAX AtmAddr 1226 MAX-ACCESS read-write 1227 STATUS current 1228 DESCRIPTION 1229 "The primary address assigned for administrative purposes, 1230 for example, an address associated with the 1231 service provider side of a public network UNI 1232 (thus, the value of this address corresponds 1233 with the value of ifPhysAddress at the host side). 1234 If this interface has no assigned administrative 1235 address, or when the address used for 1236 administrative purposes is the same as that used 1237 for ifPhysAddress, then this is an octet string of 1238 zero length." 1239 ::= { atmInterfaceConfEntry 10 } 1241 atmInterfaceMyNeighborIpAddress OBJECT-TYPE 1242 SYNTAX IpAddress 1243 MAX-ACCESS read-write 1245 draft ATM Management Objects June 26, 1996 1247 STATUS current 1248 DESCRIPTION 1249 "The IP address of the neighbor system connected to 1250 the far end of this interface, to which a Network 1251 Management Station can send SNMP messages, as IP 1252 datagrams sent to UDP port 161, in order to access 1253 network management information concerning the 1254 operation of that system. Note that the value 1255 of this object may be obtained in different ways, 1256 e.g., by manual configuration, or through ILMI 1257 interaction with the neighbor system." 1258 ::= { atmInterfaceConfEntry 11 } 1260 atmInterfaceMyNeighborIfName OBJECT-TYPE 1261 SYNTAX DisplayString 1262 MAX-ACCESS read-write 1263 STATUS current 1264 DESCRIPTION 1265 "The textual name of the interface on the neighbor 1266 system on the far end of this interface, and to 1267 which this interface connects. If the neighbor 1268 system is manageable through SNMP and supports 1269 the object ifName, the value of this object must 1270 be identical with that of ifName for the ifEntry 1271 of the lowest level physical interface 1272 for this port. If this interface does not have a 1273 textual name, the value of this object is a zero 1274 length string. Note that the value of this object 1275 may be obtained in different ways, e.g., by manual 1276 configuration, or through ILMI interaction with 1277 the neighbor system." 1278 ::= { atmInterfaceConfEntry 12 } 1280 atmInterfaceCurrentMaxVpiBits OBJECT-TYPE 1281 SYNTAX INTEGER (0..12) 1282 MAX-ACCESS read-only 1283 STATUS current 1284 DESCRIPTION 1285 "The maximum number of VPI Bits that may 1286 currently be used at this ATM interface. 1287 The value is the minimum of 1288 atmInterfaceMaxActiveVpiBits, and the 1289 atmInterfaceMaxActiveVpiBits of the interface's 1290 UNI/NNI peer. 1292 draft ATM Management Objects June 26, 1996 1294 If the interface does not negotiate with 1295 its peer to determine the number of VPI Bits 1296 that can be used on the interface, then the 1297 value of this object must equal 1298 atmInterfaceMaxActiveVpiBits." 1299 ::= { atmInterfaceConfEntry 13 } 1301 atmInterfaceCurrentMaxVciBits OBJECT-TYPE 1302 SYNTAX INTEGER (0..16) 1303 MAX-ACCESS read-only 1304 STATUS current 1305 DESCRIPTION 1306 "The maximum number of VCI Bits that may 1307 currently be used at this ATM interface. 1308 The value is the minimum of 1309 atmInterfaceMaxActiveVciBits, and the 1310 atmInterfaceMaxActiveVpiBits of the interface's 1311 UNI/NNI peer. 1313 If the interface does not negotiate with 1314 its peer to determine the number of VCI Bits 1315 that can be used on the interface, then the 1316 value of this object must equal 1317 atmInterfaceMaxActiveVciBits." 1318 ::= { atmInterfaceConfEntry 14 } 1320 draft ATM Management Objects June 26, 1996 1322 -- The ATM Interface DS3 PLCP Group 1324 -- This group contains the DS3 PLCP configuration and 1325 -- state parameters of those ATM interfaces 1326 -- which use DS3 PLCP for carrying ATM cells over DS3. 1328 atmInterfaceDs3PlcpTable OBJECT-TYPE 1329 SYNTAX SEQUENCE OF AtmInterfaceDs3PlcpEntry 1330 MAX-ACCESS not-accessible 1331 STATUS current 1332 DESCRIPTION 1333 "This table contains ATM interface DS3 PLCP 1334 parameters and state variables, one entry per 1335 ATM interface port." 1336 ::= { atmMIBObjects 3} 1338 atmInterfaceDs3PlcpEntry OBJECT-TYPE 1339 SYNTAX AtmInterfaceDs3PlcpEntry 1340 MAX-ACCESS not-accessible 1341 STATUS current 1342 DESCRIPTION 1343 "This list contains DS3 PLCP parameters and 1344 state variables at the ATM interface and is 1345 indexed by the ifIndex value of the ATM interface." 1346 INDEX { ifIndex } 1347 ::= { atmInterfaceDs3PlcpTable 1} 1349 AtmInterfaceDs3PlcpEntry ::= SEQUENCE { 1350 atmInterfaceDs3PlcpSEFSs Counter32, 1351 atmInterfaceDs3PlcpAlarmState INTEGER, 1352 atmInterfaceDs3PlcpUASs Counter32 1353 } 1355 atmInterfaceDs3PlcpSEFSs OBJECT-TYPE 1356 SYNTAX Counter32 1357 MAX-ACCESS read-only 1358 STATUS current 1359 DESCRIPTION 1360 "The number of DS3 PLCP Severely Errored Framing 1361 Second (SEFS). Each SEFS represents a 1362 one-second interval which contains 1363 one or more SEF event." 1364 ::= { atmInterfaceDs3PlcpEntry 1} 1366 draft ATM Management Objects June 26, 1996 1368 atmInterfaceDs3PlcpAlarmState OBJECT-TYPE 1369 SYNTAX INTEGER { 1370 noAlarm(1), 1371 receivedFarEndAlarm(2), 1372 incomingLOF(3) 1373 } 1374 MAX-ACCESS read-only 1375 STATUS current 1376 DESCRIPTION 1377 "This variable indicates if there is an 1378 alarm present for the DS3 PLCP. The value 1379 receivedFarEndAlarm means that the DS3 PLCP 1380 has received an incoming Yellow 1381 Signal, the value incomingLOF means that 1382 the DS3 PLCP has declared a loss of frame (LOF) 1383 failure condition, and the value noAlarm 1384 means that there are no alarms present. 1385 Transition from the failure to the no alarm state 1386 occurs when no defects (e.g., LOF) are received 1387 for more than 10 seconds." 1388 ::= { atmInterfaceDs3PlcpEntry 2} 1390 atmInterfaceDs3PlcpUASs OBJECT-TYPE 1391 SYNTAX Counter32 1392 MAX-ACCESS read-only 1393 STATUS current 1394 DESCRIPTION 1395 "The counter associated with the number of 1396 Unavailable Seconds encountered by the PLCP." 1397 ::= { atmInterfaceDs3PlcpEntry 3} 1399 draft ATM Management Objects June 26, 1996 1401 -- The ATM Interface TC Sublayer Group 1403 -- This group contains TC sublayer configuration and 1404 -- state parameters of those ATM interfaces 1405 -- which use TC sublayer for carrying ATM cells over 1406 -- SONET/SDH or DS3. 1408 atmInterfaceTCTable OBJECT-TYPE 1409 SYNTAX SEQUENCE OF AtmInterfaceTCEntry 1410 MAX-ACCESS not-accessible 1411 STATUS current 1412 DESCRIPTION 1413 "This table contains ATM interface TC 1414 Sublayer parameters and state variables, 1415 one entry per ATM interface port." 1416 ::= { atmMIBObjects 4} 1418 atmInterfaceTCEntry OBJECT-TYPE 1419 SYNTAX AtmInterfaceTCEntry 1420 MAX-ACCESS not-accessible 1421 STATUS current 1422 DESCRIPTION 1423 "This list contains TC Sublayer parameters 1424 and state variables at the ATM interface and is 1425 indexed by the ifIndex value of the ATM interface." 1426 INDEX {ifIndex } 1427 ::= { atmInterfaceTCTable 1} 1429 AtmInterfaceTCEntry ::= SEQUENCE { 1430 atmInterfaceOCDEvents Counter32, 1431 atmInterfaceTCAlarmState INTEGER 1432 } 1434 atmInterfaceOCDEvents OBJECT-TYPE 1435 SYNTAX Counter32 1436 MAX-ACCESS read-only 1437 STATUS current 1438 DESCRIPTION 1439 "The number of times the Out of Cell 1440 Delineation (OCD) events occur. If seven 1441 consecutive ATM cells have Header Error 1442 Control (HEC) violations, an OCD event occurs. 1443 A high number of OCD events may indicate a 1444 problem with the TC Sublayer." 1446 draft ATM Management Objects June 26, 1996 1448 ::= { atmInterfaceTCEntry 1} 1450 atmInterfaceTCAlarmState OBJECT-TYPE 1451 SYNTAX INTEGER { 1452 noAlarm(1), 1453 lcdFailure(2) 1454 } 1455 MAX-ACCESS read-only 1456 STATUS current 1457 DESCRIPTION 1458 "This variable indicates if there is an 1459 alarm present for the TC Sublayer. The value 1460 lcdFailure(2) indicates that the TC Sublayer 1461 is currently in the Loss of Cell Delineation 1462 (LCD) defect maintenance state. The value 1463 noAlarm(1) indicates that the TC Sublayer 1464 is currently not in the LCD defect 1465 maintenance state." 1466 ::= { atmInterfaceTCEntry 2} 1468 draft ATM Management Objects June 26, 1996 1470 -- ATM Traffic Descriptor Parameter Group 1472 -- This group contains a set of self-consistent 1473 -- ATM traffic parameters including the 1474 -- ATM traffic service category. 1476 -- The ATM virtual link tables (i.e., VPL and VCL tables) 1477 -- will use this ATM Traffic Descriptor table 1478 -- to assign traffic parameters and service category 1479 -- to the receive and transmit directions of 1480 -- the ATM virtual links (i.e., VPLs and VCLs). 1481 -- The ATM VPL or VCL table will indicate a row 1482 -- in the atmTrafficDescrParamTable 1483 -- using its atmTrafficDescrParamIndex value. 1484 -- The management application can then compare a set of 1485 -- ATM traffic parameters with a single value. 1487 -- If no suitable row(s) in the atmTrafficDescrParamTable 1488 -- exists, the manager must create a new row(s) in this 1489 -- table. If such a row is created, agent checks the 1490 -- sanity of that set of ATM traffic parameter values. 1492 -- When creating a new row, the parameter values 1493 -- will be checked for self-consistency. 1494 -- Predefined/template rows may be supported. 1496 -- A row in the atmTrafficDescrParamTable is deleted 1497 -- by setting the atmTrafficDescrRowStatus to destroy(6). 1498 -- The agent will check whether this row is still in use 1499 -- by any entry of the atmVplTable or atmVclTable. 1500 -- The agent denies the request if the row is still in 1501 -- use. 1503 -- The ATM Traffic Descriptor Parameter Table 1505 atmTrafficDescrParamTable OBJECT-TYPE 1506 SYNTAX SEQUENCE OF AtmTrafficDescrParamEntry 1507 MAX-ACCESS not-accessible 1508 STATUS current 1509 DESCRIPTION 1510 "This table contains information on ATM traffic 1511 descriptor type and the associated parameters." 1512 ::= { atmMIBObjects 5} 1514 draft ATM Management Objects June 26, 1996 1516 atmTrafficDescrParamEntry OBJECT-TYPE 1517 SYNTAX AtmTrafficDescrParamEntry 1518 MAX-ACCESS not-accessible 1519 STATUS current 1520 DESCRIPTION 1521 "This list contains ATM traffic descriptor 1522 type and the associated parameters." 1523 INDEX {atmTrafficDescrParamIndex} 1524 ::= { atmTrafficDescrParamTable 1} 1526 AtmTrafficDescrParamEntry ::= SEQUENCE { 1527 atmTrafficDescrParamIndex AtmTrafficDescrParamIndex, 1528 atmTrafficDescrType OBJECT IDENTIFIER, 1529 atmTrafficDescrParam1 Integer32, 1530 atmTrafficDescrParam2 Integer32, 1531 atmTrafficDescrParam3 Integer32, 1532 atmTrafficDescrParam4 Integer32, 1533 atmTrafficDescrParam5 Integer32, 1534 atmTrafficQoSClass INTEGER, 1535 atmTrafficDescrRowStatus RowStatus, 1536 atmServiceCategory AtmServiceCategory 1537 } 1539 atmTrafficDescrParamIndex OBJECT-TYPE 1540 SYNTAX AtmTrafficDescrParamIndex 1541 MAX-ACCESS not-accessible 1542 STATUS current 1543 DESCRIPTION 1544 "This object is used by the virtual link 1545 table (i.e., VPL or VCL table) 1546 to identify the row of this table." 1547 ::= { atmTrafficDescrParamEntry 1} 1549 atmTrafficDescrType OBJECT-TYPE 1550 SYNTAX OBJECT IDENTIFIER 1551 MAX-ACCESS read-create 1552 STATUS current 1553 DESCRIPTION 1554 "The value of this object identifies the type 1555 of ATM traffic descriptor. 1556 The type may indicate no traffic descriptor or 1557 traffic descriptor with one or more parameters. 1558 These parameters are specified as a parameter 1559 vector, in the corresponding instances of the 1560 objects: 1562 draft ATM Management Objects June 26, 1996 1564 atmTrafficDescrParam1 1565 atmTrafficDescrParam2 1566 atmTrafficDescrParam3 1567 atmTrafficDescrParam4 1568 atmTrafficDescrParam5." 1569 DEFVAL { atmNoTrafficDescriptor } 1570 ::= { atmTrafficDescrParamEntry 2} 1572 atmTrafficDescrParam1 OBJECT-TYPE 1573 SYNTAX Integer32 1574 MAX-ACCESS read-create 1575 STATUS current 1576 DESCRIPTION 1577 "The first parameter of the ATM traffic descriptor 1578 used according to the value of 1579 atmTrafficDescrType." 1580 DEFVAL { 0 } 1581 ::= { atmTrafficDescrParamEntry 3} 1583 atmTrafficDescrParam2 OBJECT-TYPE 1584 SYNTAX Integer32 1585 MAX-ACCESS read-create 1586 STATUS current 1587 DESCRIPTION 1588 "The second parameter of the ATM traffic descriptor 1589 used according to the value of 1590 atmTrafficDescrType." 1591 DEFVAL { 0 } 1592 ::= { atmTrafficDescrParamEntry 4} 1594 atmTrafficDescrParam3 OBJECT-TYPE 1595 SYNTAX Integer32 1596 MAX-ACCESS read-create 1597 STATUS current 1598 DESCRIPTION 1599 "The third parameter of the ATM traffic descriptor 1600 used according to the value of 1601 atmTrafficDescrType." 1602 DEFVAL { 0 } 1603 ::= { atmTrafficDescrParamEntry 5} 1605 atmTrafficDescrParam4 OBJECT-TYPE 1606 SYNTAX Integer32 1607 MAX-ACCESS read-create 1608 STATUS current 1610 draft ATM Management Objects June 26, 1996 1612 DESCRIPTION 1613 "The fourth parameter of the ATM traffic descriptor 1614 used according to the value of 1615 atmTrafficDescrType." 1616 DEFVAL { 0 } 1617 ::= { atmTrafficDescrParamEntry 6} 1619 atmTrafficDescrParam5 OBJECT-TYPE 1620 SYNTAX Integer32 1621 MAX-ACCESS read-create 1622 STATUS current 1623 DESCRIPTION 1624 "The fifth parameter of the ATM traffic descriptor 1625 used according to the value of 1626 atmTrafficDescrType." 1627 DEFVAL { 0 } 1628 ::= { atmTrafficDescrParamEntry 7} 1630 atmTrafficQoSClass OBJECT-TYPE 1631 SYNTAX INTEGER (0..255) 1632 MAX-ACCESS read-create 1633 STATUS deprecated 1634 DESCRIPTION 1635 "The value of this object identifies the QoS Class. 1636 Four Service classes have been 1637 specified in the ATM Forum UNI Specification: 1638 Service Class A: Constant bit rate video and 1639 Circuit emulation 1640 Service Class B: Variable bit rate video/audio 1641 Service Class C: Connection-oriented data 1642 Service Class D: Connectionless data 1643 Four QoS classes numbered 1, 2, 3, and 4 have 1644 been specified with the aim to support service 1645 classes A, B, C, and D respectively. 1646 An unspecified QoS Class numbered `0' is used 1647 for best effort traffic." 1648 DEFVAL { 0 } 1649 ::= { atmTrafficDescrParamEntry 8} 1651 atmTrafficDescrRowStatus OBJECT-TYPE 1652 SYNTAX RowStatus 1653 MAX-ACCESS read-create 1654 STATUS current 1655 DESCRIPTION 1656 "This object is used to create 1658 draft ATM Management Objects June 26, 1996 1660 a new row or modify or delete an 1661 existing row in this table." 1662 DEFVAL { active } 1663 ::= {atmTrafficDescrParamEntry 9} 1665 atmServiceCategory OBJECT-TYPE 1666 SYNTAX AtmServiceCategory 1667 MAX-ACCESS read-create 1668 STATUS current 1669 DESCRIPTION 1670 " The ATM service category." 1671 DEFVAL { ubr } 1672 ::= { atmTrafficDescrParamEntry 10} 1674 draft ATM Management Objects June 26, 1996 1676 -- ATM Interface Virtual Path Link (VPL) Group 1678 -- This group contains configuration and state 1679 -- information of a bi-directional Virtual Path Link 1680 -- (VPL) 1682 -- This table can be used to create, delete or modify 1683 -- a VPL that is terminated in an ATM host or switch. 1684 -- This table can also be used to create, delete or 1685 -- modify a VPL which is cross-connected to another 1686 -- VPL. 1688 -- In the example below, the traffic flows on the receive 1689 -- and transmit directions of the VPLs are characterized 1690 -- by atmVplReceiveTrafficDescrIndex and 1691 -- atmVplTransmitTrafficDescrIndex respectively. 1692 -- The cross-connected VPLs are identified by 1693 -- atmVplCrossConnectIdentifier. 1695 -- ________________________________ 1696 -- | | 1697 -- VPL | ATM Host, Switch, or Network | VPL 1698 -- receive | | receive 1699 -- ========> X X <======= 1700 -- <======== X X ========> 1701 -- transmit | | transmit 1702 -- |______________________________| 1704 -- The ATM Interface VPL Table 1706 atmVplTable OBJECT-TYPE 1707 SYNTAX SEQUENCE OF AtmVplEntry 1708 MAX-ACCESS not-accessible 1709 STATUS current 1710 DESCRIPTION 1711 "The Virtual Path Link (VPL) table. A 1712 bi-directional VPL is modeled as one entry 1713 in this table." 1714 ::= { atmMIBObjects 6} 1716 draft ATM Management Objects June 26, 1996 1718 atmVplEntry OBJECT-TYPE 1719 SYNTAX AtmVplEntry 1720 MAX-ACCESS not-accessible 1721 STATUS current 1722 DESCRIPTION 1723 "An entry in the VPL table. This entry is 1724 used to model a bi-directional VPL. 1725 To create a VPL at an ATM interface, 1726 either of the following procedures are used: 1728 Negotiated VPL establishment 1730 (1) The management application creates 1731 a VPL entry in the atmVplTable 1732 by setting atmVplRowStatus to createAndWait(5). 1733 This may fail for the following reasons: 1734 - The selected VPI value is unavailable, 1735 - The selected VPI value is in use. 1736 Otherwise, the agent creates a row and 1737 reserves the VPI value on that port. 1739 (2) The manager selects an existing row(s) in the 1740 atmTrafficDescrParamTable, 1741 thereby, selecting a set of self-consistent 1742 ATM traffic parameters and the service category 1743 for receive and transmit directions of the VPL. 1745 (2a) If no suitable row(s) in the 1746 atmTrafficDescrParamTable exists, 1747 the manager must create a new row(s) 1748 in that table. 1750 (2b) The manager characterizes the VPL's traffic 1751 parameters through setting the 1752 atmVplReceiveTrafficDescrIndex and the 1753 atmVplTransmitTrafficDescrIndex values 1754 in the VPL table, which point to the rows 1755 containing desired ATM traffic parameter values 1756 in the atmTrafficDescrParamTable. The agent 1757 will check the availability of resources and 1758 may refuse the request. 1760 (3) The manager activates the VPL by setting the 1761 the atmVplRowStatus to active(1). 1762 If this set is successful, the agent has 1764 draft ATM Management Objects June 26, 1996 1766 reserved the resources to satisfy the requested 1767 traffic parameter values and the service category 1768 for that VPL. 1770 (4) If the VPL terminates a VPC in the ATM host 1771 or switch, the manager turns on the 1772 atmVplAdminStatus to up(1) to turn the VPL 1773 traffic flow on. Otherwise, the 1774 atmVpCrossConnectTable must be used 1775 to cross-connect the VPL to another VPL(s) 1776 in an ATM switch or network. 1778 One-Shot VPL Establishment 1780 A VPL may also be established in one step by a 1781 set-request with all necessary VPL parameter 1782 values and atmVplRowStatus set to createAndGo(4). 1784 In contrast to the negotiated VPL establishment 1785 which allows for detailed error checking 1786 (i.e., set errors are explicitly linked to 1787 particular resource acquisition failures), 1788 the one-shot VPL establishment 1789 performs the setup on one operation but 1790 does not have the advantage of step-wise 1791 error checking. 1793 VPL Retirement 1795 A VPL is released by setting atmVplRowStatus to 1796 destroy(6), and the agent may release all 1797 associated resources." 1798 INDEX {ifIndex, atmVplVpi } 1799 ::= { atmVplTable 1} 1801 AtmVplEntry ::= SEQUENCE { 1802 atmVplVpi AtmVpIdentifier, 1803 atmVplAdminStatus AtmVorXAdminStatus, 1804 atmVplOperStatus AtmVorXOperStatus, 1805 atmVplLastChange AtmVorXLastChange, 1806 atmVplReceiveTrafficDescrIndex 1807 AtmTrafficDescrParamIndex, 1808 atmVplTransmitTrafficDescrIndex 1809 AtmTrafficDescrParamIndex, 1810 atmVplCrossConnectIdentifier INTEGER, 1812 draft ATM Management Objects June 26, 1996 1814 atmVplRowStatus RowStatus, 1815 atmVplCastType AtmConnCastType, 1816 atmVplConnKind AtmConnKind 1817 } 1819 atmVplVpi OBJECT-TYPE 1820 SYNTAX AtmVpIdentifier 1821 MAX-ACCESS not-accessible 1822 STATUS current 1823 DESCRIPTION 1824 "The VPI value of the VPL." 1825 ::= { atmVplEntry 1} 1827 atmVplAdminStatus OBJECT-TYPE 1828 SYNTAX AtmVorXAdminStatus 1829 MAX-ACCESS read-create 1830 STATUS current 1831 DESCRIPTION 1832 "This object is implemented only for a VPL 1833 which terminates a VPC (i.e., one which is 1834 NOT cross-connected to other VPLs). 1835 Its value specifies the desired 1836 administrative state of the VPL." 1837 DEFVAL { down } 1838 ::= { atmVplEntry 2} 1840 atmVplOperStatus OBJECT-TYPE 1841 SYNTAX AtmVorXOperStatus 1842 MAX-ACCESS read-only 1843 STATUS current 1844 DESCRIPTION 1845 "The current operational status of the VPL." 1846 ::= { atmVplEntry 3} 1848 atmVplLastChange OBJECT-TYPE 1849 SYNTAX AtmVorXLastChange 1850 MAX-ACCESS read-only 1851 STATUS current 1852 DESCRIPTION 1853 "The value of sysUpTime at the time this 1854 VPL entered its current operational state." 1855 ::= { atmVplEntry 4 } 1857 atmVplReceiveTrafficDescrIndex OBJECT-TYPE 1859 draft ATM Management Objects June 26, 1996 1861 SYNTAX AtmTrafficDescrParamIndex 1862 MAX-ACCESS read-create 1863 STATUS current 1864 DESCRIPTION 1865 "The value of this object identifies the row 1866 in the atmTrafficDescrParamTable which 1867 applies to the receive direction of the VPL." 1868 DEFVAL { 0 } 1869 ::= { atmVplEntry 5} 1871 atmVplTransmitTrafficDescrIndex OBJECT-TYPE 1872 SYNTAX AtmTrafficDescrParamIndex 1873 MAX-ACCESS read-create 1874 STATUS current 1875 DESCRIPTION 1876 "The value of this object identifies the row 1877 in the atmTrafficDescrParamTable which 1878 applies to the transmit direction of the VPL." 1879 DEFVAL { 0 } 1880 ::= { atmVplEntry 6} 1882 atmVplCrossConnectIdentifier OBJECT-TYPE 1883 SYNTAX INTEGER (0..2147483647) 1884 MAX-ACCESS read-only 1885 STATUS current 1886 DESCRIPTION 1887 "This object is implemented only for a VPL 1888 which is cross-connected to other VPLs 1889 that belong to the same VPC. All such 1890 associated VPLs have the same value of this 1891 object, and all their cross-connections are 1892 identified by entries in the 1893 atmVpCrossConnectTable for which 1894 atmVpCrossConnectIndex has the same value. 1895 The value of this object is initialized by the 1896 agent after the associated entries in the 1897 atmVpCrossConnectTable have been created." 1898 ::= {atmVplEntry 7} 1900 atmVplRowStatus OBJECT-TYPE 1901 SYNTAX RowStatus 1902 MAX-ACCESS read-create 1903 STATUS current 1904 DESCRIPTION 1905 "This object is used to create, delete 1907 draft ATM Management Objects June 26, 1996 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 June 26, 1996 1941 -- ATM Interface Virtual Channel Link (VCL) Group 1943 -- This group 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." 1963 ::= { atmMIBObjects 7} 1965 atmVclEntry OBJECT-TYPE 1966 SYNTAX AtmVclEntry 1967 MAX-ACCESS not-accessible 1968 STATUS current 1969 DESCRIPTION 1970 "An entry in the VCL table. This entry is 1971 used to model a bi-directional VCL. 1972 To create a VCL at an ATM interface, 1973 either of the following procedures are used: 1975 Negotiated VCL establishment 1977 (1) The management application creates 1978 a VCL entry in the atmVclTable 1979 by setting atmVclRowStatus to createAndWait(5). 1980 This may fail for the following reasons: 1981 - The selected VPI/VCI values are unavailable, 1982 - The selected VPI/VCI values are in use. 1983 Otherwise, the agent creates a row and 1985 draft ATM Management Objects June 26, 1996 1987 reserves the VPI/VCI values on that port. 1989 (2) The manager selects an existing row(s) in the 1990 atmTrafficDescrParamTable, 1991 thereby, selecting a set of self-consistent 1992 ATM traffic parameters and the service category 1993 for receive and transmit directions of the VCL. 1995 (2a) If no suitable row(s) in the 1996 atmTrafficDescrParamTable exists, 1997 the manager must create a new row(s) 1998 in that table. 2000 (2b) The manager characterizes the VCL's traffic 2001 parameters through setting the 2002 atmVclReceiveTrafficDescrIndex and the 2003 atmVclTransmitTrafficDescrIndex values 2004 in the VCL table, which point to the rows 2005 containing desired ATM traffic parameter values 2006 in the atmTrafficDescrParamTable. The agent 2007 will check the availability of resources and 2008 may refuse the request. 2010 (3) The manager activates the VCL by setting the 2011 the atmVclRowStatus to active(1) (for 2012 requirements on this activation see the 2013 description of atmVclRowStatus). 2014 If this set is successful, the agent has 2015 reserved the resources to satisfy the requested 2016 traffic parameter values and the service category 2017 for that VCL. 2018 (4) If the VCL terminates a VCC in the ATM host 2019 or switch, the manager turns on the 2020 atmVclAdminStatus to up(1) to turn the VCL 2021 traffic flow on. Otherwise, the 2022 atmVcCrossConnectTable must be used 2023 to cross-connect the VCL to another VCL(s) 2024 in an ATM switch or network. 2026 One-Shot VCL Establishment 2028 A VCL may also be established in one step by a 2029 set-request with all necessary VCL parameter 2030 values and atmVclRowStatus set to createAndGo(4). 2032 draft ATM Management Objects June 26, 1996 2034 In contrast to the negotiated VCL establishment 2035 which allows for detailed error checking 2036 (i.e., set errors are explicitly linked to 2037 particular resource acquisition failures), 2038 the one-shot VCL establishment 2039 performs the setup on one operation but 2040 does not have the advantage of step-wise 2041 error checking. 2043 VCL Retirement 2045 A VCL is released by setting atmVclRowStatus to 2046 destroy(6), and the agent may release all 2047 associated resources." 2048 INDEX {ifIndex, atmVclVpi, atmVclVci } 2049 ::= { atmVclTable 1} 2051 AtmVclEntry ::= SEQUENCE { 2052 atmVclVpi AtmVpIdentifier, 2053 atmVclVci AtmVcIdentifier, 2054 atmVclAdminStatus AtmVorXAdminStatus, 2055 atmVclOperStatus AtmVorXOperStatus, 2056 atmVclLastChange AtmVorXLastChange, 2057 atmVclReceiveTrafficDescrIndex 2058 AtmTrafficDescrParamIndex, 2059 atmVclTransmitTrafficDescrIndex 2060 AtmTrafficDescrParamIndex, 2061 atmVccAalType INTEGER, 2062 atmVccAal5CpcsTransmitSduSize INTEGER, 2063 atmVccAal5CpcsReceiveSduSize INTEGER, 2064 atmVccAal5EncapsType INTEGER, 2065 atmVclCrossConnectIdentifier INTEGER, 2066 atmVclRowStatus RowStatus, 2067 atmVclCastType AtmConnCastType, 2068 atmVclConnKind AtmConnKind 2069 } 2071 atmVclVpi OBJECT-TYPE 2072 SYNTAX AtmVpIdentifier 2073 MAX-ACCESS not-accessible 2074 STATUS current 2075 DESCRIPTION 2076 "The VPI value of the VCL." 2077 ::= { atmVclEntry 1} 2079 draft ATM Management Objects June 26, 1996 2081 atmVclVci OBJECT-TYPE 2082 SYNTAX AtmVcIdentifier 2083 MAX-ACCESS not-accessible 2084 STATUS current 2085 DESCRIPTION 2086 "The VCI value of the VCL." 2087 ::= { atmVclEntry 2} 2089 atmVclAdminStatus OBJECT-TYPE 2090 SYNTAX AtmVorXAdminStatus 2091 MAX-ACCESS read-create 2092 STATUS current 2093 DESCRIPTION 2094 "This object is implemented only for a VCL which 2095 terminates a VCC (i.e., one which is NOT 2096 cross-connected to other VCLs). Its value 2097 specifies the desired administrative state of 2098 the VCL." 2099 DEFVAL { down } 2100 ::= { atmVclEntry 3} 2102 atmVclOperStatus OBJECT-TYPE 2103 SYNTAX AtmVorXOperStatus 2104 MAX-ACCESS read-only 2105 STATUS current 2106 DESCRIPTION 2107 "The current operational status of the VCL." 2108 ::= { atmVclEntry 4} 2110 atmVclLastChange OBJECT-TYPE 2111 SYNTAX AtmVorXLastChange 2112 MAX-ACCESS read-only 2113 STATUS current 2114 DESCRIPTION 2115 "The value of sysUpTime at the time this VCL 2116 entered its current operational state." 2117 ::= { atmVclEntry 5 } 2119 atmVclReceiveTrafficDescrIndex OBJECT-TYPE 2120 SYNTAX AtmTrafficDescrParamIndex 2121 MAX-ACCESS read-create 2122 STATUS current 2123 DESCRIPTION 2124 "The value of this object identifies the row 2125 in the ATM Traffic Descriptor Table which 2127 draft ATM Management Objects June 26, 1996 2129 applies to the receive direction of this VCL." 2130 DEFVAL { 0 } 2131 ::= { atmVclEntry 6} 2133 atmVclTransmitTrafficDescrIndex OBJECT-TYPE 2134 SYNTAX AtmTrafficDescrParamIndex 2135 MAX-ACCESS read-create 2136 STATUS current 2137 DESCRIPTION 2138 "The value of this object identifies the row 2139 of the ATM Traffic Descriptor Table which applies 2140 to the transmit direction of this VCL." 2141 DEFVAL { 0 } 2142 ::= { atmVclEntry 7} 2144 atmVccAalType OBJECT-TYPE 2145 SYNTAX INTEGER { 2146 aal1(1), 2147 aal34(2), 2148 aal5(3), 2149 other(4), 2150 unknown(5) 2151 } 2152 MAX-ACCESS read-create 2153 STATUS current 2154 DESCRIPTION 2155 "An instance of this object only exists when the 2156 local VCL end-point is also the VCC end-point, 2157 and AAL is in use. 2158 The type of AAL used on this VCC. 2159 The AAL type includes AAL1, AAL3/4, 2160 and AAL5. The other(4) may be user-defined 2161 AAL type. The unknown type indicates that 2162 the AAL type cannot be determined." 2163 DEFVAL { aal5 } 2164 ::= { atmVclEntry 8 } 2166 atmVccAal5CpcsTransmitSduSize OBJECT-TYPE 2167 SYNTAX INTEGER (1..65535) 2168 MAX-ACCESS read-create 2169 STATUS current 2170 DESCRIPTION 2171 "An instance of this object only exists when the 2172 local VCL end-point is also the VCC end-point, 2173 and AAL5 is in use. 2175 draft ATM Management Objects June 26, 1996 2177 The maximum AAL5 CPCS SDU size in octets that is 2178 supported on the transmit direction of this VCC." 2179 DEFVAL { 9188 } 2180 ::= { atmVclEntry 9 } 2182 atmVccAal5CpcsReceiveSduSize OBJECT-TYPE 2183 SYNTAX INTEGER (1..65535) 2184 MAX-ACCESS read-create 2185 STATUS current 2186 DESCRIPTION 2187 "An instance of this object only exists when the 2188 local VCL end-point is also the VCC end-point, 2189 and AAL5 is in use. 2190 The maximum AAL5 CPCS SDU size in octets that is 2191 supported on the receive direction of this VCC." 2192 DEFVAL { 9188 } 2193 ::= { atmVclEntry 10 } 2195 atmVccAal5EncapsType OBJECT-TYPE 2196 SYNTAX INTEGER { 2197 vcMultiplexRoutedProtocol(1), 2198 vcMultiplexBridgedProtocol8023(2), 2199 vcMultiplexBridgedProtocol8025(3), 2200 vcMultiplexBridgedProtocol8026(4), 2201 vcMultiplexLANemulation8023(5), 2202 vcMultiplexLANemulation8025(6), 2203 llcEncapsulation(7), 2204 multiprotocolFrameRelaySscs(8), 2205 other(9), 2206 unknown(10) 2207 } 2208 MAX-ACCESS read-create 2209 STATUS current 2210 DESCRIPTION 2211 "An instance of this object only exists when the 2212 local VCL end-point is also the VCC end-point, 2213 and AAL5 is in use. 2214 The type of data encapsulation used over 2215 the AAL5 SSCS layer. The definitions reference 2216 RFC 1483 Multiprotocol Encapsulation 2217 over ATM AAL5 and to the ATM Forum 2218 LAN Emulation specification." 2219 DEFVAL { llcEncapsulation } 2220 ::= { atmVclEntry 11 } 2222 draft ATM Management Objects June 26, 1996 2224 atmVclCrossConnectIdentifier OBJECT-TYPE 2225 SYNTAX INTEGER (0..2147483647) 2226 MAX-ACCESS read-only 2227 STATUS current 2228 DESCRIPTION 2229 "This object is implemented only for a VCL 2230 which is cross-connected to other VCLs 2231 that belong to the same VCC. All such 2232 associated VCLs have the same value of this 2233 object, and all their cross-connections are 2234 identified by entries in the 2235 atmVcCrossConnectTable for which 2236 atmVcCrossConnectIndex has the same value. 2237 The value of this object is initialized by the 2238 agent after the associated entries in the 2239 atmVcCrossConnectTable have been created." 2240 ::= {atmVclEntry 12} 2242 atmVclRowStatus OBJECT-TYPE 2243 SYNTAX RowStatus 2244 MAX-ACCESS read-create 2245 STATUS current 2246 DESCRIPTION 2247 "This object is used to create, delete or 2248 modify a row in this table. To create 2249 a new VCL, this object is initially set 2250 to 'createAndWait' or 'createAndGo'. 2251 This object should not be 2252 set to 'active' unless the following columnar 2253 objects have been set to their desired value 2254 in this row: 2255 atmVclReceiveTrafficDescrIndex, 2256 atmVclTransmitTrafficDescrIndex. 2257 In addition, if the local VCL end-point 2258 is also the VCC end-point: 2259 atmVccAalType. 2260 In addition, for AAL5 connections only: 2261 atmVccAal5CpcsTransmitSduSize, 2262 atmVccAal5CpcsReceiveSduSize, and 2263 atmVccAal5EncapsType. (The existence 2264 of these objects imply the AAL connection type.)" 2265 DEFVAL { active } 2266 ::= {atmVclEntry 13} 2268 atmVclCastType OBJECT-TYPE 2270 draft ATM Management Objects June 26, 1996 2272 SYNTAX AtmConnCastType 2273 MAX-ACCESS read-create 2274 STATUS current 2275 DESCRIPTION 2276 "The connection topology type." 2277 DEFVAL { p2p } 2278 ::= {atmVclEntry 14} 2280 atmVclConnKind OBJECT-TYPE 2281 SYNTAX AtmConnKind 2282 MAX-ACCESS read-create 2283 STATUS current 2284 DESCRIPTION 2285 "The use of call control." 2286 DEFVAL { pvc } 2287 ::= {atmVclEntry 15} 2289 draft ATM Management Objects June 26, 1996 2291 -- ATM Virtual Path (VP) Cross Connect Group 2293 -- This group contains configuration and state 2294 -- information of point-to-point, 2295 -- point-to-multipoint, or multipoint-to-multipoint 2296 -- VP cross-connects for PVCs. 2298 -- This table has read-create access and can be used 2299 -- to cross-connect the VPLs together in an ATM switch 2300 -- or network. The atmVpCrossConnectIndex 2301 -- is used to associate the related 2302 -- VPLs that are cross-connected together. 2304 -- The ATM VP Cross Connect Group 2305 -- models each bi-directional VPC 2306 -- cross-connect as a set of entries in 2307 -- the atmVpCrossConnectTable. A 2308 -- point-to-point VPC cross-connect is modeled 2309 -- as one entry; a point-to-multipoint (N leafs) VPC 2310 -- cross-connect as N entries in this table; and 2311 -- a multipoint-to-multipoint (N parties) VPC cross- 2312 -- connect as N(N-1)/2 entries in this table. 2313 -- In the latter cases, all the N (or N(N-1)/2) entries 2314 -- are associated with a single VPC cross-connect by 2315 -- having the same value of atmVpCrossConnectIndex. 2317 -- _________________________________________ 2318 -- | | 2319 -- Low | ATM Switch or Network | High 2320 -- port| | port 2321 -- _____|>> from low to high VPC traffic flow >>|______ 2322 -- |<< from high to low VPC traffic flow <<| 2323 -- | | 2324 -- |_______________________________________| 2325 -- 2327 -- The terms low and high are chosen to represent 2328 -- numerical ordering of the two interfaces associated 2329 -- with a VPC cross-connect. That is, the ATM interface 2330 -- with the lower value of ifIndex is termed 'low', 2331 -- while the other ATM interface associated with the 2332 -- VPC cross-connect is termed 'high'. This terminology 2333 -- is used to provide directional information; for 2334 -- example, the atmVpCrossConnectL2HOperStatus applies 2336 draft ATM Management Objects June 26, 1996 2338 -- to the low->high direction, and 2339 -- atmVpCrossConnectH2LOperStatus applies to the 2340 -- high->low direction, as illustrated above. 2342 atmVpCrossConnectIndexNext OBJECT-TYPE 2343 SYNTAX INTEGER (0..2147483647) 2344 MAX-ACCESS read-only 2345 STATUS current 2346 DESCRIPTION 2347 "This object contains an appropriate value to 2348 be used for atmVpCrossConnectIndex when creating 2349 entries in the atmVpCrossConnectTable. The value 2350 0 indicates that no unassigned entries are 2351 available. To obtain the atmVpCrossConnectIndex 2352 value for a new entry, the manager issues a 2353 management protocol retrieval operation to obtain 2354 the current value of this object. After each 2355 retrieval, the agent should modify the value to 2356 the next unassigned index." 2357 ::= { atmMIBObjects 8 } 2359 -- The ATM VP Cross Connect Table 2361 atmVpCrossConnectTable OBJECT-TYPE 2362 SYNTAX SEQUENCE OF AtmVpCrossConnectEntry 2363 MAX-ACCESS not-accessible 2364 STATUS current 2365 DESCRIPTION 2366 "The ATM VP Cross Connect table. A bi- 2367 directional VP cross-connect which 2368 cross-connects two VPLs is modeled 2369 as one entry in this table." 2370 ::= { atmMIBObjects 9 } 2372 atmVpCrossConnectEntry OBJECT-TYPE 2373 SYNTAX AtmVpCrossConnectEntry 2374 MAX-ACCESS not-accessible 2375 STATUS current 2376 DESCRIPTION 2378 draft ATM Management Objects June 26, 1996 2380 "An entry in the ATM VP Cross Connect table. 2381 This entry is used to model a bi-directional 2382 ATM VP cross-connect which cross-connects 2383 two VPLs. 2385 Step-wise Procedures to set up a VP Cross-connect 2387 Once the entries in the atmVplTable are created, 2388 the following procedures are used 2389 to cross-connect the VPLs together. 2391 (1) The manager obtains a unique 2392 atmVpCrossConnectIndex by reading the 2393 atmVpCrossConnectIndexNext object. 2395 (2) Next, the manager creates a set of one 2396 or more rows in the ATM VP Cross Connect 2397 Table, one for each cross-connection between 2398 two VPLs. Each row is indexed by the ATM 2399 interface port numbers and VPI values of the 2400 two ends of that cross-connection. 2401 This set of rows specifies the topology of the 2402 VPC cross-connect and is identified by a single 2403 value of atmVpCrossConnectIndex. 2405 Negotiated VP Cross-Connect Establishment 2407 (2a) The manager creates a row in this table by 2408 setting atmVpCrossConnectRowStatus to 2409 createAndWait(5). The agent checks the 2410 requested topology and the mutual sanity of 2411 the ATM traffic parameters and 2412 service categories, i.e., the row creation 2413 fails if: 2414 - the requested topology is incompatible with 2415 associated values of atmVplCastType, 2416 - the requested topology is not supported 2417 by the agent, 2418 - the traffic/service category parameter values 2419 associated with the requested row are 2420 incompatible with those of already existing 2421 rows for this VP cross-connect. 2422 [For example, for setting up 2423 a point-to-point VP cross-connect, the 2424 ATM traffic parameters in the receive direction 2426 draft ATM Management Objects June 26, 1996 2428 of a VPL at the low end of the cross-connect 2429 must equal to the traffic parameters in the 2430 transmit direction of the other VPL at the 2431 high end of the cross-connect, 2432 otherwise, the row creation fails.] 2433 The agent also checks for internal errors 2434 in building the cross-connect. 2436 The atmVpCrossConnectIndex values in the 2437 corresponding atmVplTable rows are filled 2438 in by the agent at this point. 2440 (2b) The manager promotes the row in the 2441 atmVpCrossConnectTable by setting 2442 atmVpCrossConnectRowStatus to active(1). If 2443 this set is successful, the agent has reserved 2444 the resources specified by the ATM traffic 2445 parameter and Service category values 2446 for each direction of the VP cross-connect 2447 in an ATM switch or network. 2449 (3) The manager sets the 2450 atmVpCrossConnectAdminStatus to up(1) in all 2451 rows of this VP cross-connect to turn the 2452 traffic flow on. 2454 One-Shot VP Cross-Connect Establishment 2456 A VP cross-connect may also be established in 2457 one step by a set-request with all necessary 2458 parameter values and atmVpCrossConnectRowStatus 2459 set to createAndGo(4). 2461 In contrast to the negotiated VP cross-connect 2462 establishment which allows for detailed error 2463 checking (i.e., set errors are explicitly linked 2464 to particular resource acquisition failures), 2465 the one-shot VP cross-connect establishment 2466 performs the setup on one operation but does not 2467 have the advantage of step-wise error checking. 2469 VP Cross-Connect Retirement 2471 A VP cross-connect identified by a particular 2473 draft ATM Management Objects June 26, 1996 2475 value of atmVpCrossConnectIndex is released by: 2477 (1) Setting atmVpCrossConnectRowStatus of all 2478 rows identified by this value of 2479 atmVpCrossConnectIndex to destroy(6). 2480 The agent may release all 2481 associated resources, and the 2482 atmVpCrossConnectIndex values in the 2483 corresponding atmVplTable row are removed. 2484 Note that a situation when only a subset of 2485 the associated rows are deleted corresponds 2486 to a VP topology change. 2488 (2) After deletion of the appropriate 2489 atmVpCrossConnectEntries, the manager may 2490 set atmVplRowStatus to destroy(6) the 2491 associated VPLs. The agent releases 2492 the resources and removes the associated 2493 rows in the atmVplTable. 2495 VP Cross-connect Reconfiguration 2497 At the discretion of the agent, a VP 2498 cross-connect may be reconfigured by 2499 adding and/or deleting leafs to/from 2500 the VP topology as per the VP cross-connect 2501 establishment/retirement procedures. 2502 Reconfiguration of traffic/service category parameter 2503 values requires release of the VP cross-connect 2504 before those parameter values may by changed 2505 for individual VPLs." 2506 INDEX { atmVpCrossConnectIndex, 2507 atmVpCrossConnectLowIfIndex, 2508 atmVpCrossConnectLowVpi, 2509 atmVpCrossConnectHighIfIndex, 2510 atmVpCrossConnectHighVpi } 2511 ::= { atmVpCrossConnectTable 1 } 2513 AtmVpCrossConnectEntry ::= SEQUENCE { 2514 atmVpCrossConnectIndex INTEGER, 2515 atmVpCrossConnectLowIfIndex InterfaceIndex, 2516 atmVpCrossConnectLowVpi AtmVpIdentifier, 2517 atmVpCrossConnectHighIfIndex InterfaceIndex, 2518 atmVpCrossConnectHighVpi AtmVpIdentifier, 2519 atmVpCrossConnectAdminStatus AtmVorXAdminStatus, 2521 draft ATM Management Objects June 26, 1996 2523 atmVpCrossConnectL2HOperStatus AtmVorXOperStatus, 2524 atmVpCrossConnectH2LOperStatus AtmVorXOperStatus, 2525 atmVpCrossConnectL2HLastChange AtmVorXLastChange, 2526 atmVpCrossConnectH2LLastChange AtmVorXLastChange, 2527 atmVpCrossConnectRowStatus RowStatus 2528 } 2530 atmVpCrossConnectIndex OBJECT-TYPE 2531 SYNTAX INTEGER (1..2147483647) 2532 MAX-ACCESS not-accessible 2533 STATUS current 2534 DESCRIPTION 2535 "A unique value to identify this VP cross-connect." 2536 ::= { atmVpCrossConnectEntry 1 } 2538 atmVpCrossConnectLowIfIndex OBJECT-TYPE 2539 SYNTAX InterfaceIndex 2540 MAX-ACCESS not-accessible 2541 STATUS current 2542 DESCRIPTION 2543 "The ifIndex value of the ATM interface for 2544 this VP cross-connect. The term low implies 2545 that this ATM interface has the numerically lower 2546 ifIndex value than the other ATM interface 2547 identified in the same atmVpCrossConnectEntry." 2548 ::= { atmVpCrossConnectEntry 2 } 2550 atmVpCrossConnectLowVpi OBJECT-TYPE 2551 SYNTAX AtmVpIdentifier 2552 MAX-ACCESS not-accessible 2553 STATUS current 2554 DESCRIPTION 2555 "The VPI value at the ATM interface 2556 associated with the VP cross-connect that is 2557 identified by atmVpCrossConnectLowIfIndex." 2558 ::= { atmVpCrossConnectEntry 3 } 2560 atmVpCrossConnectHighIfIndex OBJECT-TYPE 2561 SYNTAX InterfaceIndex 2562 MAX-ACCESS not-accessible 2563 STATUS current 2564 DESCRIPTION 2565 "The ifIndex value of the ATM interface for 2566 this VP cross-connect. The term high implies that 2567 this ATM interface has the numerically higher 2569 draft ATM Management Objects June 26, 1996 2571 ifIndex value than the other ATM interface 2572 identified in the same atmVpCrossConnectEntry." 2573 ::= { atmVpCrossConnectEntry 4 } 2575 atmVpCrossConnectHighVpi OBJECT-TYPE 2576 SYNTAX AtmVpIdentifier 2577 MAX-ACCESS not-accessible 2578 STATUS current 2579 DESCRIPTION 2580 "The VPI value at the ATM interface 2581 associated with the VP cross-connect that is 2582 identified by atmVpCrossConnectHighIfIndex." 2583 ::= { atmVpCrossConnectEntry 5 } 2585 atmVpCrossConnectAdminStatus OBJECT-TYPE 2586 SYNTAX AtmVorXAdminStatus 2587 MAX-ACCESS read-create 2588 STATUS current 2589 DESCRIPTION 2590 "The desired administrative status of this 2591 bi-directional VP cross-connect." 2592 DEFVAL { down } 2593 ::= { atmVpCrossConnectEntry 6 } 2595 atmVpCrossConnectL2HOperStatus OBJECT-TYPE 2596 SYNTAX AtmVorXOperStatus 2597 MAX-ACCESS read-only 2598 STATUS current 2599 DESCRIPTION 2600 "The operational status of the VP cross-connect 2601 in one direction; (i.e., from the low to 2602 high direction)." 2603 ::= { atmVpCrossConnectEntry 7 } 2605 atmVpCrossConnectH2LOperStatus OBJECT-TYPE 2606 SYNTAX AtmVorXOperStatus 2607 MAX-ACCESS read-only 2608 STATUS current 2609 DESCRIPTION 2610 "The operational status of the VP cross-connect 2611 in one direction; (i.e., from the high to 2612 low direction)." 2613 ::= { atmVpCrossConnectEntry 8 } 2615 atmVpCrossConnectL2HLastChange OBJECT-TYPE 2617 draft ATM Management Objects June 26, 1996 2619 SYNTAX AtmVorXLastChange 2620 MAX-ACCESS read-only 2621 STATUS current 2622 DESCRIPTION 2623 "The value of sysUpTime at the time this 2624 VP cross-connect entered its current operational 2625 state in the low to high direction." 2626 ::= { atmVpCrossConnectEntry 9 } 2628 atmVpCrossConnectH2LLastChange OBJECT-TYPE 2629 SYNTAX AtmVorXLastChange 2630 MAX-ACCESS read-only 2631 STATUS current 2632 DESCRIPTION 2633 "The value of sysUpTime at the time this 2634 VP cross-connect entered its current operational 2635 in the high to low direction." 2636 ::= { atmVpCrossConnectEntry 10 } 2638 atmVpCrossConnectRowStatus OBJECT-TYPE 2639 SYNTAX RowStatus 2640 MAX-ACCESS read-create 2641 STATUS current 2642 DESCRIPTION 2643 "The status of this entry in the 2644 atmVpCrossConnectTable. This object is used to 2645 create a cross-connect for cross-connecting 2646 VPLs which are created using the atmVplTable 2647 or to change or delete an existing cross-connect. 2648 This object must be initially set 2649 to `createAndWait' or 'createAndGo'. 2650 This object cannot be set to `active' 2651 unless the following columnar object exists 2652 in this row: atmVpCrossConnectAdminStatus. 2653 To turn on a VP cross-connect, 2654 the atmVpCrossConnectAdminStatus 2655 is set to `up'." 2656 DEFVAL { active } 2657 ::= { atmVpCrossConnectEntry 11 } 2659 draft ATM Management Objects June 26, 1996 2661 -- ATM Virtual Channel (VC) Cross Connect Group 2663 -- This group contains configuration and state 2664 -- information of point-to-point, 2665 -- point-to-multipoint or multipoint-to-multipoint 2666 -- VC cross-connects for PVCs. 2668 -- This table has read-create access and is used 2669 -- to cross-connect the VCLs together in an ATM switch 2670 -- or network that belong to a VC connection. 2671 -- The atmVcCrossConnectIndex is used to associate 2672 -- the related VCLs that are cross-connected together. 2674 -- The step-wise procedures described for setting 2675 -- up a VP cross-connect are also used for setting up 2676 -- a VC cross-connect. 2678 atmVcCrossConnectIndexNext OBJECT-TYPE 2679 SYNTAX INTEGER (0..2147483647) 2680 MAX-ACCESS read-only 2681 STATUS current 2682 DESCRIPTION 2683 "This object contains an appropriate value to 2684 be used for atmVcCrossConnectIndex when creating 2685 entries in the atmVcCrossConnectTable. The value 2686 0 indicates that no unassigned entries are 2687 available. To obtain the atmVpCrossConnectIndex 2688 value for a new entry, the manager issues a 2689 management protocol retrieval operation to obtain 2690 the current value of this object. After each 2691 retrieval, the agent should modify the value to 2692 the next unassigned index." 2693 ::= { atmMIBObjects 10 } 2695 -- The ATM VC Cross Connect Table 2697 atmVcCrossConnectTable OBJECT-TYPE 2698 SYNTAX SEQUENCE OF AtmVcCrossConnectEntry 2699 MAX-ACCESS not-accessible 2700 STATUS current 2702 draft ATM Management Objects June 26, 1996 2704 DESCRIPTION 2705 "The ATM VC Cross Connect table. A bi- 2706 directional VC cross-connect which 2707 cross-connects two end points (i.e., VCLs) 2708 is modeled as one entry in this table." 2709 ::= { atmMIBObjects 11 } 2711 atmVcCrossConnectEntry OBJECT-TYPE 2712 SYNTAX AtmVcCrossConnectEntry 2713 MAX-ACCESS not-accessible 2714 STATUS current 2715 DESCRIPTION 2716 "An entry in the ATM VC Cross Connect table. 2717 This entry is used to model a bi-directional ATM 2718 VC cross-connect cross-connecting two end points. 2720 Step-wise Procedures to set up a VC Cross-connect 2722 Once the entries in the atmVclTable are created, 2723 the following procedures are used 2724 to cross-connect the VCLs together to 2725 form a VCC segment. 2727 (1) The manager obtains a unique 2728 atmVcCrossConnectIndex by reading the 2729 atmVcCrossConnectIndexNext object. 2731 (2) Next, the manager creates a set of one 2732 or more rows in the ATM VC Cross Connect 2733 Table, one for each cross-connection between 2734 two VCLs. Each row is indexed by the ATM 2735 interface port numbers and VPI/VCI values of 2736 the two ends of that cross-connection. 2737 This set of rows specifies the topology of the 2738 VCC cross-connect and is identified by a single 2739 value of atmVcCrossConnectIndex. 2741 Negotiated VC Cross-Connect Establishment 2743 (2a) The manager creates a row in this table by 2744 setting atmVcCrossConnectRowStatus to 2745 createAndWait(5). The agent checks the 2746 requested topology and the mutual sanity of 2747 the ATM traffic parameters and 2749 draft ATM Management Objects June 26, 1996 2751 service categories, i.e., the row creation 2752 fails if: 2753 - the requested topology is incompatible with 2754 associated values of atmVclCastType, 2755 - the requested topology is not supported 2756 by the agent, 2757 - the traffic/service category parameter values 2758 associated with the requested row are 2759 incompatible with those of already existing 2760 rows for this VC cross-connect. 2761 [For example, for setting up 2762 a point-to-point VC cross-connect, the 2763 ATM traffic parameters in the receive direction 2764 of a VCL at the low end of the cross-connect 2765 must equal to the traffic parameters in the 2766 transmit direction of the other VCL at the 2767 high end of the cross-connect, 2768 otherwise, the row creation fails.] 2769 The agent also checks for internal errors 2770 in building the cross-connect. 2772 The atmVcCrossConnectIndex values in the 2773 corresponding atmVclTable rows are filled 2774 in by the agent at this point. 2776 (2b) The manager promotes the row in the 2777 atmVcCrossConnectTable by setting 2778 atmVcCrossConnectRowStatus to active(1). If 2779 this set is successful, the agent has reserved 2780 the resources specified by the ATM traffic 2781 parameter and Service category values 2782 for each direction of the VC cross-connect 2783 in an ATM switch or network. 2785 (3) The manager sets the 2786 atmVcCrossConnectAdminStatus to up(1) 2787 in all rows of this VC cross-connect to 2788 turn the traffic flow on. 2790 One-Shot VC Cross-Connect Establishment 2792 A VC cross-connect may also be established in 2793 one step by a set-request with all necessary 2794 parameter values and atmVcCrossConnectRowStatus 2796 draft ATM Management Objects June 26, 1996 2798 set to createAndGo(4). 2800 In contrast to the negotiated VC cross-connect 2801 establishment which allows for detailed error 2802 checking i.e., set errors are explicitly linked to 2803 particular resource acquisition failures), the 2804 one-shot VC cross-connect establishment 2805 performs the setup on one operation but does 2806 not have the advantage of step-wise error 2807 checking. 2809 VC Cross-Connect Retirement 2811 A VC cross-connect identified by a particular 2812 value of atmVcCrossConnectIndex is released by: 2814 (1) Setting atmVcCrossConnectRowStatus of all rows 2815 identified by this value of 2816 atmVcCrossConnectIndex to destroy(6). 2817 The agent may release all 2818 associated resources, and the 2819 atmVcCrossConnectIndex values in the 2820 corresponding atmVclTable row are removed. 2821 Note that a situation when only a subset of 2822 the associated rows are deleted corresponds 2823 to a VC topology change. 2825 (2) After deletion of the appropriate 2826 atmVcCrossConnectEntries, the manager may 2827 set atmVclRowStatus to destroy(6) the 2828 associated VCLs. The agent releases 2829 the resources and removes the associated 2830 rows in the atmVclTable. 2832 VC Cross-Connect Reconfiguration 2834 At the discretion of the agent, a VC 2835 cross-connect may be reconfigured by 2836 adding and/or deleting leafs to/from 2837 the VC topology as per the VC cross-connect 2838 establishment/retirement procedures. 2839 Reconfiguration of traffic/service category parameter 2840 values requires release of the VC cross-connect 2841 before those parameter values may by changed 2842 for individual VCLs." 2844 draft ATM Management Objects June 26, 1996 2846 INDEX { atmVcCrossConnectIndex, 2847 atmVcCrossConnectLowIfIndex, 2848 atmVcCrossConnectLowVpi, 2849 atmVcCrossConnectLowVci, 2850 atmVcCrossConnectHighIfIndex, 2851 atmVcCrossConnectHighVpi, 2852 atmVcCrossConnectHighVci } 2853 ::= { atmVcCrossConnectTable 1 } 2855 AtmVcCrossConnectEntry ::= SEQUENCE { 2856 atmVcCrossConnectIndex INTEGER, 2857 atmVcCrossConnectLowIfIndex InterfaceIndex, 2858 atmVcCrossConnectLowVpi AtmVpIdentifier, 2859 atmVcCrossConnectLowVci AtmVcIdentifier, 2860 atmVcCrossConnectHighIfIndex InterfaceIndex, 2861 atmVcCrossConnectHighVpi AtmVpIdentifier, 2862 atmVcCrossConnectHighVci AtmVcIdentifier, 2863 atmVcCrossConnectAdminStatus AtmVorXAdminStatus, 2864 atmVcCrossConnectL2HOperStatus AtmVorXOperStatus, 2865 atmVcCrossConnectH2LOperStatus AtmVorXOperStatus, 2866 atmVcCrossConnectL2HLastChange AtmVorXLastChange, 2867 atmVcCrossConnectH2LLastChange AtmVorXLastChange, 2868 atmVcCrossConnectRowStatus RowStatus 2869 } 2871 atmVcCrossConnectIndex OBJECT-TYPE 2872 SYNTAX INTEGER (1..2147483647) 2873 MAX-ACCESS not-accessible 2874 STATUS current 2875 DESCRIPTION 2876 "A unique value to identify this VC cross-connect." 2877 ::= { atmVcCrossConnectEntry 1 } 2879 atmVcCrossConnectLowIfIndex OBJECT-TYPE 2880 SYNTAX InterfaceIndex 2881 MAX-ACCESS not-accessible 2882 STATUS current 2883 DESCRIPTION 2884 "The ifIndex value of the ATM interface for this 2885 VC cross-connect. The term low implies 2886 that this ATM interface has the numerically lower 2887 ifIndex value than the other ATM interface 2888 identified in the same atmVcCrossConnectEntry." 2889 ::= { atmVcCrossConnectEntry 2 } 2891 draft ATM Management Objects June 26, 1996 2893 atmVcCrossConnectLowVpi OBJECT-TYPE 2894 SYNTAX AtmVpIdentifier 2895 MAX-ACCESS not-accessible 2896 STATUS current 2897 DESCRIPTION 2898 "The VPI value at the ATM interface 2899 associated with the VC cross-connect that is 2900 identified by atmVcCrossConnectLowIfIndex." 2901 ::= { atmVcCrossConnectEntry 3 } 2903 atmVcCrossConnectLowVci OBJECT-TYPE 2904 SYNTAX AtmVcIdentifier 2905 MAX-ACCESS not-accessible 2906 STATUS current 2907 DESCRIPTION 2908 "The VCI value at the ATM interface 2909 associated with this VC cross-connect that is 2910 identified by atmVcCrossConnectLowIfIndex." 2911 ::= { atmVcCrossConnectEntry 4 } 2913 atmVcCrossConnectHighIfIndex OBJECT-TYPE 2914 SYNTAX InterfaceIndex 2915 MAX-ACCESS not-accessible 2916 STATUS current 2917 DESCRIPTION 2918 "The ifIndex value for the ATM interface for 2919 this VC cross-connect. The term high implies 2920 that this ATM interface has the numerically higher 2921 ifIndex value than the other ATM interface 2922 identified in the same atmVcCrossConnectEntry." 2923 ::= { atmVcCrossConnectEntry 5 } 2925 atmVcCrossConnectHighVpi OBJECT-TYPE 2926 SYNTAX AtmVpIdentifier 2927 MAX-ACCESS not-accessible 2928 STATUS current 2929 DESCRIPTION 2930 "The VPI value at the ATM interface 2931 associated with the VC cross-connect that is 2932 identified by atmVcCrossConnectHighIfIndex." 2933 ::= { atmVcCrossConnectEntry 6 } 2935 atmVcCrossConnectHighVci OBJECT-TYPE 2936 SYNTAX AtmVcIdentifier 2937 MAX-ACCESS not-accessible 2939 draft ATM Management Objects June 26, 1996 2941 STATUS current 2942 DESCRIPTION 2943 "The VCI value at the ATM interface 2944 associated with the VC cross-connect that is 2945 identified by atmVcCrossConnectHighIfIndex." 2946 ::= { atmVcCrossConnectEntry 7 } 2948 atmVcCrossConnectAdminStatus OBJECT-TYPE 2949 SYNTAX AtmVorXAdminStatus 2950 MAX-ACCESS read-create 2951 STATUS current 2952 DESCRIPTION 2953 "The desired administrative status of this 2954 bi-directional VC cross-connect." 2955 DEFVAL { down } 2956 ::= { atmVcCrossConnectEntry 8 } 2958 atmVcCrossConnectL2HOperStatus OBJECT-TYPE 2959 SYNTAX AtmVorXOperStatus 2960 MAX-ACCESS read-only 2961 STATUS current 2962 DESCRIPTION 2963 "The current operational status of the 2964 VC cross-connect in one direction; (i.e., 2965 from the low to high direction)." 2966 ::= { atmVcCrossConnectEntry 9 } 2968 atmVcCrossConnectH2LOperStatus OBJECT-TYPE 2969 SYNTAX AtmVorXOperStatus 2970 MAX-ACCESS read-only 2971 STATUS current 2972 DESCRIPTION 2973 "The current operational status of the 2974 VC cross-connect in one direction; (i.e., 2975 from the high to low direction)." 2976 ::= { atmVcCrossConnectEntry 10 } 2978 atmVcCrossConnectL2HLastChange OBJECT-TYPE 2979 SYNTAX AtmVorXLastChange 2980 MAX-ACCESS read-only 2981 STATUS current 2982 DESCRIPTION 2983 "The value of sysUpTime at the time this 2984 VC cross-connect entered its current 2986 draft ATM Management Objects June 26, 1996 2988 operational state in low to high direction." 2989 ::= { atmVcCrossConnectEntry 11 } 2991 atmVcCrossConnectH2LLastChange OBJECT-TYPE 2992 SYNTAX AtmVorXLastChange 2993 MAX-ACCESS read-only 2994 STATUS current 2995 DESCRIPTION 2996 "The value of sysUpTime at the time this 2997 VC cross-connect entered its current 2998 operational state in high to low direction." 2999 ::= { atmVcCrossConnectEntry 12 } 3001 atmVcCrossConnectRowStatus OBJECT-TYPE 3002 SYNTAX RowStatus 3003 MAX-ACCESS read-create 3004 STATUS current 3005 DESCRIPTION 3006 "The status of this entry in the 3007 atmVcCrossConnectTable. This object is used to 3008 create a new cross-connect for cross-connecting 3009 VCLs which are created using the atmVclTable 3010 or to change or delete existing cross-connect. 3011 This object must be initially set to 3012 `createAndWait' or 'createAndGo'. This object 3013 cannot be set to `active' unless the following 3014 columnar object exists in this row: 3015 atmVcCrossConnectAdminStatus. 3016 To turn on a VC cross-connect, 3017 the atmVcCrossConnectAdminStatus 3018 is set to `up'." 3019 DEFVAL { active } 3020 ::= { atmVcCrossConnectEntry 13 } 3022 draft ATM Management Objects June 26, 1996 3024 -- AAL5 Virtual Channel Connection Performance Statistics 3025 -- Group 3027 -- This group contains the AAL5 3028 -- performance statistics of a VCC at the 3029 -- interface associated with an AAL5 entity in an ATM 3030 -- host or ATM switch. 3032 aal5VccTable OBJECT-TYPE 3033 SYNTAX SEQUENCE OF Aal5VccEntry 3034 MAX-ACCESS not-accessible 3035 STATUS current 3036 DESCRIPTION 3037 "This table contains AAL5 VCC performance 3038 parameters." 3039 ::= { atmMIBObjects 12 } 3041 aal5VccEntry OBJECT-TYPE 3042 SYNTAX Aal5VccEntry 3043 MAX-ACCESS not-accessible 3044 STATUS current 3045 DESCRIPTION 3046 "This list contains the AAL5 VCC 3047 performance parameters." 3048 INDEX { ifIndex, aal5VccVpi, aal5VccVci } 3049 ::= { aal5VccTable 1 } 3051 Aal5VccEntry ::= SEQUENCE { 3052 aal5VccVpi AtmVpIdentifier, 3053 aal5VccVci AtmVcIdentifier, 3054 aal5VccCrcErrors Counter32, 3055 aal5VccSarTimeOuts Counter32, 3056 aal5VccOverSizedSDUs Counter32 3057 } 3059 aal5VccVpi OBJECT-TYPE 3060 SYNTAX AtmVpIdentifier 3061 MAX-ACCESS not-accessible 3062 STATUS current 3063 DESCRIPTION 3064 "The VPI value of the AAL5 VCC at the 3065 interface identified by the ifIndex." 3066 ::= { aal5VccEntry 1 } 3068 draft ATM Management Objects June 26, 1996 3070 aal5VccVci OBJECT-TYPE 3071 SYNTAX AtmVcIdentifier 3072 MAX-ACCESS not-accessible 3073 STATUS current 3074 DESCRIPTION 3075 "The VCI value of the AAL5 VCC at the 3076 interface identified by the ifIndex." 3077 ::= { aal5VccEntry 2 } 3079 aal5VccCrcErrors OBJECT-TYPE 3080 SYNTAX Counter32 3081 MAX-ACCESS read-only 3082 STATUS current 3083 DESCRIPTION 3084 "The number of AAL5 CPCS PDUs received with 3085 CRC-32 errors on this AAL5 VCC at the 3086 interface associated with an AAL5 entity." 3087 ::= { aal5VccEntry 3 } 3089 aal5VccSarTimeOuts OBJECT-TYPE 3090 SYNTAX Counter32 3091 MAX-ACCESS read-only 3092 STATUS current 3093 DESCRIPTION 3094 "The number of partially re-assembled AAL5 3095 CPCS PDUs which were discarded 3096 on this AAL5 VCC at the interface associated 3097 with an AAL5 entity because they 3098 were not fully re-assembled within the 3099 required time period. If the re-assembly 3100 timer is not supported, then this object 3101 contains a zero value." 3102 ::= { aal5VccEntry 4 } 3104 aal5VccOverSizedSDUs OBJECT-TYPE 3105 SYNTAX Counter32 3106 MAX-ACCESS read-only 3107 STATUS current 3108 DESCRIPTION 3109 "The number of AAL5 CPCS PDUs discarded 3110 on this AAL5 VCC at the interface 3111 associated with an AAL5 entity because the 3112 AAL5 SDUs were too large." 3113 ::= { aal5VccEntry 5 } 3115 draft ATM Management Objects June 26, 1996 3117 -- Conformance Information 3119 atmMIBConformance OBJECT IDENTIFIER ::= { atmMIB 2 } 3121 atmMIBGroups OBJECT IDENTIFIER 3122 ::= { atmMIBConformance 1 } 3123 atmMIBCompliances OBJECT IDENTIFIER 3124 ::= { atmMIBConformance 2 } 3126 -- Compliance Statements 3128 atmMIBCompliance2 MODULE-COMPLIANCE 3129 STATUS current 3130 DESCRIPTION 3131 "The compliance statement for SNMP entities 3132 including networks which have ATM and 3133 AAL5 interfaces." 3135 MODULE -- this module 3136 MANDATORY-GROUPS {atmInterfaceConfGroup2, 3137 atmTrafficDescrGroup2 } 3139 OBJECT atmInterfaceMaxVpcs 3140 MIN-ACCESS read-only 3141 DESCRIPTION 3142 "Write access is not required." 3144 OBJECT atmInterfaceMaxVccs 3145 MIN-ACCESS read-only 3146 DESCRIPTION 3147 "Write access is not required." 3149 OBJECT atmInterfaceMaxActiveVpiBits 3150 MIN-ACCESS read-only 3151 DESCRIPTION 3152 "Write access is not required. 3153 At the ATM UNI the maximum number of 3154 active VPI bits configured for use ranges 3155 from 0 to 8 only. 3156 Implementations may support smaller ranges." 3158 OBJECT atmInterfaceMaxActiveVciBits 3159 MIN-ACCESS read-only 3160 DESCRIPTION 3162 draft ATM Management Objects June 26, 1996 3164 "Write access is not required. 3165 Implementations may support smaller ranges." 3167 OBJECT atmInterfaceIlmiVpi 3168 MIN-ACCESS read-only 3169 DESCRIPTION 3170 "Write access is not required." 3172 OBJECT atmInterfaceIlmiVci 3173 MIN-ACCESS read-only 3174 DESCRIPTION 3175 "Write access is not required." 3177 OBJECT atmInterfaceAdminAddress 3178 MIN-ACCESS read-only 3179 DESCRIPTION 3180 "Write access is not required." 3182 OBJECT atmInterfaceMyNeighborIpAddress 3183 MIN-ACCESS read-only 3184 DESCRIPTION 3185 "Write access is not required." 3187 OBJECT atmInterfaceMyNeighborIfName 3188 MIN-ACCESS read-only 3189 DESCRIPTION 3190 "Write access is not required." 3192 OBJECT atmTrafficDescrType 3193 MIN-ACCESS read-only 3194 DESCRIPTION 3195 "Write access is not required." 3197 OBJECT atmTrafficDescrParam1 3198 MIN-ACCESS read-only 3199 DESCRIPTION 3200 "Write access is not required." 3202 OBJECT atmTrafficDescrParam2 3203 MIN-ACCESS read-only 3204 DESCRIPTION 3205 "Write access is not required." 3207 OBJECT atmTrafficDescrParam3 3208 MIN-ACCESS read-only 3210 draft ATM Management Objects June 26, 1996 3212 DESCRIPTION 3213 "Write access is not required." 3215 OBJECT atmTrafficDescrParam4 3216 MIN-ACCESS read-only 3217 DESCRIPTION 3218 "Write access is not required." 3220 OBJECT atmTrafficDescrParam5 3221 MIN-ACCESS read-only 3222 DESCRIPTION 3223 "Write access is not required." 3225 OBJECT atmServiceCategory 3226 MIN-ACCESS read-only 3227 DESCRIPTION 3228 "Write access is not required." 3230 OBJECT atmTrafficDescrRowStatus 3231 SYNTAX INTEGER {active(1)} 3232 -- subset of RowStatus 3233 MIN-ACCESS read-only 3234 DESCRIPTION 3235 "Write access is not required, and only one 3236 of the six enumerated values for the 3237 RowStatus textual convention need be 3238 supported, specifically: active(1)." 3240 GROUP atmInterfaceDs3PlcpGroup 3241 DESCRIPTION 3242 "This group is mandatory only for those 3243 ATM interfaces which implement the 3244 DS3 PLCP layer." 3246 GROUP atmInterfaceTCGroup 3247 DESCRIPTION 3248 "This group is mandatory only for those 3249 ATM interfaces which implement the 3250 TC Sublayer." 3252 GROUP atmVpcTerminationGroup2 3253 DESCRIPTION 3254 "This group is mandatory only for those 3255 ATM interfaces which implement ATM 3256 VPLs that terminate VPCs (i.e., ones which 3258 draft ATM Management Objects June 26, 1996 3260 are NOT cross-connected to other VPLs)." 3262 GROUP atmVpCrossConnectGroup 3263 DESCRIPTION 3264 "This group is mandatory only for those 3265 ATM interfaces which implement ATM 3266 VPLs that are not associated with VCLs 3267 and are cross-connected to other VPLs 3268 for permanent VPCs (i.e., PVCs). 3269 This group is not used to crossconnect 3270 a PVC with an SVC to form a Soft PVC." 3272 OBJECT atmVplAdminStatus 3273 MIN-ACCESS read-only 3274 DESCRIPTION 3275 "Write access is not required." 3277 OBJECT atmVplReceiveTrafficDescrIndex 3278 MIN-ACCESS read-only 3279 DESCRIPTION 3280 "Write access is not required." 3282 OBJECT atmVplTransmitTrafficDescrIndex 3283 MIN-ACCESS read-only 3284 DESCRIPTION 3285 "Write access is not required." 3287 OBJECT atmVplRowStatus 3288 SYNTAX INTEGER {active(1)} 3289 -- subset of RowStatus 3290 MIN-ACCESS read-only 3291 DESCRIPTION 3292 "Write access is not required, and only one 3293 of the six enumerated values for the 3294 RowStatus textual convention need be 3295 supported, specifically: active(1)." 3297 OBJECT atmVplCastType 3298 MIN-ACCESS read-only 3299 DESCRIPTION 3300 "Write access is not required." 3302 OBJECT atmVplConnKind 3303 MIN-ACCESS read-only 3304 DESCRIPTION 3306 draft ATM Management Objects June 26, 1996 3308 "Write access is not required." 3310 OBJECT atmVpCrossConnectAdminStatus 3311 MIN-ACCESS read-only 3312 DESCRIPTION 3313 "Write access is not required." 3315 OBJECT atmVpCrossConnectRowStatus 3316 SYNTAX INTEGER {active(1)} 3317 -- subset of RowStatus 3318 MIN-ACCESS read-only 3319 DESCRIPTION 3320 "Write access is not required, and only one 3321 of the six enumerated values for the 3322 RowStatus textual convention need be 3323 supported, specifically: active(1)." 3325 GROUP atmVccTerminationGroup2 3326 DESCRIPTION 3327 "This group is mandatory only for those 3328 ATM interfaces which implement ATM 3329 VCLs that terminate VCCs (i.e., ones which 3330 are NOT cross-connected to other VCLs)." 3332 GROUP atmVcCrossConnectGroup 3333 DESCRIPTION 3334 "This group is mandatory only for those 3335 ATM interfaces which implement ATM 3336 VCLs that are cross-connected to 3337 other VCLs for permanent VCCs (i.e., PVCs). 3338 This group is not used to crossconnect 3339 a PVC with an SVC to form a Soft PVC." 3341 OBJECT atmVclAdminStatus 3342 MIN-ACCESS read-only 3343 DESCRIPTION 3344 "Write access is not required." 3346 OBJECT atmVclReceiveTrafficDescrIndex 3347 MIN-ACCESS read-only 3348 DESCRIPTION 3349 "Write access is not required." 3351 OBJECT atmVclTransmitTrafficDescrIndex 3352 MIN-ACCESS read-only 3354 draft ATM Management Objects June 26, 1996 3356 DESCRIPTION 3357 "Write access is not required." 3359 OBJECT atmVccAalType 3360 MIN-ACCESS read-only 3361 DESCRIPTION 3362 "Write access is not required." 3364 OBJECT atmVclRowStatus 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 atmVclCastType 3375 MIN-ACCESS read-only 3376 DESCRIPTION 3377 "Write access is not required." 3379 OBJECT atmVclConnKind 3380 MIN-ACCESS read-only 3381 DESCRIPTION 3382 "Write access is not required." 3384 OBJECT atmVcCrossConnectAdminStatus 3385 MIN-ACCESS read-only 3386 DESCRIPTION 3387 "Write access is not required." 3389 OBJECT atmVcCrossConnectRowStatus 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 3397 supported, specifically: active(1)." 3399 GROUP aal5VccGroup 3400 DESCRIPTION 3402 draft ATM Management Objects June 26, 1996 3404 "This group is mandatory for the 3405 AAL5 virtual connections only." 3407 OBJECT aal5VccVpi 3408 SYNTAX INTEGER (0..255) 3409 DESCRIPTION 3410 "For ATM UNIs supporting AAL5 VCCs, 3411 the VPI value ranges from 0 to 255." 3413 OBJECT atmVccAal5CpcsTransmitSduSize 3414 MIN-ACCESS read-only 3415 DESCRIPTION 3416 "Write access is not required." 3418 OBJECT atmVccAal5CpcsReceiveSduSize 3419 MIN-ACCESS read-only 3420 DESCRIPTION 3421 "Write access is not required." 3423 OBJECT atmVccAal5EncapsType 3424 MIN-ACCESS read-only 3425 DESCRIPTION 3426 "Write access is not required." 3427 ::= { atmMIBCompliances 2 } 3429 draft ATM Management Objects June 26, 1996 3431 -- Units of Conformance 3433 atmInterfaceDs3PlcpGroup OBJECT-GROUP 3434 OBJECTS {atmInterfaceDs3PlcpSEFSs, 3435 atmInterfaceDs3PlcpAlarmState, 3436 atmInterfaceDs3PlcpUASs} 3437 STATUS current 3438 DESCRIPTION 3439 "A collection of objects providing information 3440 about DS3 PLCP layer at an ATM interface." 3441 ::= { atmMIBGroups 3 } 3443 atmInterfaceTCGroup OBJECT-GROUP 3444 OBJECTS { atmInterfaceOCDEvents, 3445 atmInterfaceTCAlarmState } 3446 STATUS current 3447 DESCRIPTION 3448 "A collection of objects providing information 3449 about TC sublayer at an ATM interface." 3450 ::= { atmMIBGroups 4 } 3452 aal5VccGroup OBJECT-GROUP 3453 OBJECTS {atmVccAal5CpcsTransmitSduSize, 3454 atmVccAal5CpcsReceiveSduSize, 3455 atmVccAal5EncapsType, 3456 aal5VccCrcErrors, aal5VccSarTimeOuts, 3457 aal5VccOverSizedSDUs } 3458 STATUS current 3459 DESCRIPTION 3460 "A collection of objects providing 3461 AAL5 configuration and performance statistics 3462 of a VCC." 3463 ::= { atmMIBGroups 9 } 3465 atmInterfaceConfGroup2 OBJECT-GROUP 3466 OBJECTS { 3467 atmInterfaceMaxVpcs, atmInterfaceMaxVccs, 3468 atmInterfaceConfVpcs, atmInterfaceConfVccs, 3469 atmInterfaceMaxActiveVpiBits, 3470 atmInterfaceMaxActiveVciBits, 3471 atmInterfaceIlmiVpi, 3472 atmInterfaceIlmiVci, 3473 atmInterfaceAddressType, 3474 atmInterfaceAdminAddress, 3475 atmInterfaceMyNeighborIpAddress, 3477 draft ATM Management Objects June 26, 1996 3479 atmInterfaceMyNeighborIfName, 3480 atmInterfaceCurrentMaxVpiBits, 3481 atmInterfaceCurrentMaxVciBits } 3482 STATUS current 3483 DESCRIPTION 3484 "A collection of objects providing configuration 3485 information about an ATM interface." 3486 ::= { atmMIBGroups 10 } 3488 atmTrafficDescrGroup2 OBJECT-GROUP 3489 OBJECTS { 3490 atmTrafficDescrType, atmTrafficDescrParam1, 3491 atmTrafficDescrParam2, atmTrafficDescrParam3, 3492 atmTrafficDescrParam4, atmTrafficDescrParam5, 3493 atmTrafficDescrRowStatus, atmServiceCategory } 3494 STATUS current 3495 DESCRIPTION 3496 "A collection of objects providing information 3497 about ATM traffic descriptor type and 3498 the associated parameters." 3499 ::= { atmMIBGroups 11 } 3501 atmVpcTerminationGroup2 OBJECT-GROUP 3502 OBJECTS {atmVplOperStatus, atmVplAdminStatus, 3503 atmVplLastChange, 3504 atmVplReceiveTrafficDescrIndex, 3505 atmVplTransmitTrafficDescrIndex, 3506 atmVplRowStatus, atmVplCastType, 3507 atmVplConnKind } 3508 STATUS current 3509 DESCRIPTION 3510 "A collection of objects providing information 3511 about a VPL at an ATM interface which 3512 terminates a VPC (i.e., one which is NOT 3513 cross-connected to other VPLs)." 3514 ::= { atmMIBGroups 12 } 3516 atmVccTerminationGroup2 OBJECT-GROUP 3517 OBJECTS {atmVclOperStatus, atmVclAdminStatus, 3518 atmVclLastChange, 3519 atmVclReceiveTrafficDescrIndex, 3520 atmVclTransmitTrafficDescrIndex, 3521 atmVccAalType, atmVclRowStatus, 3522 atmVclCastType, atmVclConnKind } 3523 STATUS current 3525 draft ATM Management Objects June 26, 1996 3527 DESCRIPTION 3528 "A collection of objects providing information 3529 about a VCL at an ATM interface 3530 which terminates a VCC (i.e., one which is 3531 NOT cross-connected to other VCLs)." 3532 ::= { atmMIBGroups 13 } 3534 atmVpCrossConnectGroup2 OBJECT-GROUP 3535 OBJECTS { atmVplReceiveTrafficDescrIndex, 3536 atmVplTransmitTrafficDescrIndex, 3537 atmVplOperStatus, atmVplRowStatus, 3538 atmVplCastType, atmVplConnKind, 3539 atmVpCrossConnectAdminStatus, 3540 atmVpCrossConnectL2HOperStatus, 3541 atmVpCrossConnectH2LOperStatus, 3542 atmVpCrossConnectL2HLastChange, 3543 atmVpCrossConnectH2LLastChange, 3544 atmVpCrossConnectRowStatus, 3545 atmVplCrossConnectIdentifier, 3546 atmVpCrossConnectIndexNext } 3547 STATUS current 3548 DESCRIPTION 3549 "A collection of objects providing 3550 information about a VP cross-connect 3551 and the associated VPLs that are 3552 cross-connected together." 3553 ::= { atmMIBGroups 14 } 3555 atmVcCrossConnectGroup2 OBJECT-GROUP 3556 OBJECTS { atmVclReceiveTrafficDescrIndex, 3557 atmVclTransmitTrafficDescrIndex, 3558 atmVclOperStatus, atmVclRowStatus, 3559 atmVclCastType, atmVclConnKind, 3560 atmVcCrossConnectAdminStatus, 3561 atmVcCrossConnectL2HOperStatus, 3562 atmVcCrossConnectH2LOperStatus, 3563 atmVcCrossConnectL2HLastChange, 3564 atmVcCrossConnectH2LLastChange, 3565 atmVcCrossConnectRowStatus, 3566 atmVclCrossConnectIdentifier, 3567 atmVcCrossConnectIndexNext } 3568 STATUS current 3569 DESCRIPTION 3570 "A collection of objects providing 3571 information about a VC cross-connect 3573 draft ATM Management Objects June 26, 1996 3575 and the associated VCLs that are 3576 cross-connected together." 3577 ::= { atmMIBGroups 15 } 3579 draft ATM Management Objects June 26, 1996 3581 -- Deprecated Definitions - Objects 3583 -- atmTrafficQoSClass 3585 -- Deprecated Definitions - Compliance 3587 atmMIBCompliance MODULE-COMPLIANCE 3588 STATUS deprecated 3589 DESCRIPTION 3590 "The compliance statement for SNMP entities 3591 including networks which have ATM and 3592 AAL5 interfaces." 3594 MODULE -- this module 3595 MANDATORY-GROUPS {atmInterfaceConfGroup, 3596 atmTrafficDescrGroup} 3598 OBJECT atmInterfaceMaxVpcs 3599 MIN-ACCESS read-only 3600 DESCRIPTION 3601 "Write access is not required." 3603 OBJECT atmInterfaceMaxVccs 3604 MIN-ACCESS read-only 3605 DESCRIPTION 3606 "Write access is not required." 3608 OBJECT atmInterfaceMaxActiveVpiBits 3609 MIN-ACCESS read-only 3610 DESCRIPTION 3611 "Write access is not required." 3613 OBJECT atmInterfaceMaxActiveVciBits 3614 MIN-ACCESS read-only 3615 DESCRIPTION 3616 "Write access is not required." 3618 OBJECT atmInterfaceIlmiVpi 3619 MIN-ACCESS read-only 3620 DESCRIPTION 3621 "Write access is not required." 3623 OBJECT atmInterfaceIlmiVci 3624 MIN-ACCESS read-only 3626 draft ATM Management Objects June 26, 1996 3628 DESCRIPTION 3629 "Write access is not required." 3631 OBJECT atmInterfaceMyNeighborIpAddress 3632 MIN-ACCESS read-only 3633 DESCRIPTION 3634 "Write access is not required." 3636 OBJECT atmInterfaceMyNeighborIfName 3637 MIN-ACCESS read-only 3638 DESCRIPTION 3639 "Write access is not required." 3641 OBJECT atmTrafficDescrType 3642 MIN-ACCESS read-only 3643 DESCRIPTION 3644 "Write access is not required." 3646 OBJECT atmTrafficDescrParam1 3647 MIN-ACCESS read-only 3648 DESCRIPTION 3649 "Write access is not required." 3651 OBJECT atmTrafficDescrParam2 3652 MIN-ACCESS read-only 3653 DESCRIPTION 3654 "Write access is not required." 3656 OBJECT atmTrafficDescrParam3 3657 MIN-ACCESS read-only 3658 DESCRIPTION 3659 "Write access is not required." 3661 OBJECT atmTrafficDescrParam4 3662 MIN-ACCESS read-only 3663 DESCRIPTION 3664 "Write access is not required." 3666 OBJECT atmTrafficDescrParam5 3667 MIN-ACCESS read-only 3668 DESCRIPTION 3669 "Write access is not required." 3671 OBJECT atmTrafficQoSClass 3672 MIN-ACCESS read-only 3674 draft ATM Management Objects June 26, 1996 3676 DESCRIPTION 3677 "Write access is not required." 3679 OBJECT atmTrafficDescrRowStatus 3680 SYNTAX INTEGER {active(1)} 3681 -- subset of RowStatus 3682 MIN-ACCESS read-only 3683 DESCRIPTION 3684 "Write access is not required, and only one 3685 of the six enumerated values for the 3686 RowStatus textual convention need be 3687 supported, specifically: active(1)." 3689 GROUP atmInterfaceDs3PlcpGroup 3690 DESCRIPTION 3691 "This group is mandatory only for those 3692 ATM interfaces which implement the 3693 DS3 PLCP layer." 3695 GROUP atmInterfaceTCGroup 3696 DESCRIPTION 3697 "This group is mandatory only for those 3698 ATM interfaces which implement the 3699 TC Sublayer." 3701 GROUP atmVpcTerminationGroup 3702 DESCRIPTION 3703 "This group is mandatory only for those 3704 ATM interfaces which implement ATM 3705 VPLs that terminate VPCs (i.e., ones which 3706 are NOT cross-connected to other VPLs)." 3708 GROUP atmVpCrossConnectGroup 3709 DESCRIPTION 3710 "This group is mandatory only for those 3711 ATM interfaces which implement ATM 3712 VPLs that are not associated with VCLs 3713 and are cross-connected to other VPLs." 3715 OBJECT atmVplVpi 3716 SYNTAX INTEGER (1..255) 3717 DESCRIPTION 3718 "For ATM UNIs supporting VPCs, the VPI value 3719 ranges from 1 to 255." 3721 draft ATM Management Objects June 26, 1996 3723 OBJECT atmVplAdminStatus 3724 MIN-ACCESS read-only 3725 DESCRIPTION 3726 "Write access is not required." 3728 OBJECT atmVplReceiveTrafficDescrIndex 3729 MIN-ACCESS read-only 3730 DESCRIPTION 3731 "Write access is not required." 3733 OBJECT atmVplTransmitTrafficDescrIndex 3734 MIN-ACCESS read-only 3735 DESCRIPTION 3736 "Write access is not required." 3738 OBJECT atmVplRowStatus 3739 SYNTAX INTEGER {active(1)} 3740 -- subset of RowStatus 3741 MIN-ACCESS read-only 3742 DESCRIPTION 3743 "Write access is not required, and only one 3744 of the six enumerated values for the 3745 RowStatus textual convention need be 3746 supported, specifically: active(1)." 3748 OBJECT atmVpCrossConnectLowVpi 3749 SYNTAX INTEGER (1..255) 3750 DESCRIPTION 3751 "For ATM UNIs supporting VPCs, the VPI value 3752 at the numerically lower ATM interface port 3753 index number ranges from 1 to 255." 3755 OBJECT atmVpCrossConnectHighVpi 3756 SYNTAX INTEGER (1..255) 3757 DESCRIPTION 3758 "For ATM UNIs supporting VPCs, the VPI value 3759 at the numerically higher ATM interface port 3760 index number ranges from 1 to 255." 3762 OBJECT atmVpCrossConnectAdminStatus 3763 MIN-ACCESS read-only 3764 DESCRIPTION 3765 "Write access is not required." 3767 OBJECT atmVpCrossConnectRowStatus 3769 draft ATM Management Objects June 26, 1996 3771 SYNTAX INTEGER {active(1)} 3772 -- subset of RowStatus 3773 MIN-ACCESS read-only 3774 DESCRIPTION 3775 "Write access is not required, and only one 3776 of the six enumerated values for the 3777 RowStatus textual convention need be 3778 supported, specifically: active(1)." 3780 GROUP atmVccTerminationGroup 3781 DESCRIPTION 3782 "This group is mandatory only for those 3783 ATM interfaces which implement ATM 3784 VCLs that terminate VCCs (i.e., ones which 3785 are NOT cross-connected to other VCLs)." 3787 GROUP atmVcCrossConnectGroup 3788 DESCRIPTION 3789 "This group is mandatory only for those 3790 ATM interfaces which implement ATM 3791 VCLs that are cross-connected to 3792 other VCLs." 3794 OBJECT atmVclVpi 3795 SYNTAX INTEGER (0..255) 3796 DESCRIPTION 3797 "For ATM UNIs supporting VCCs, the VPI value 3798 ranges from 0 to 255." 3800 OBJECT atmVclAdminStatus 3801 MIN-ACCESS read-only 3802 DESCRIPTION 3803 "Write access is not required." 3805 OBJECT atmVclReceiveTrafficDescrIndex 3806 MIN-ACCESS read-only 3807 DESCRIPTION 3808 "Write access is not required." 3810 OBJECT atmVclTransmitTrafficDescrIndex 3811 MIN-ACCESS read-only 3812 DESCRIPTION 3813 "Write access is not required." 3815 OBJECT atmVccAalType 3817 draft ATM Management Objects June 26, 1996 3819 MIN-ACCESS read-only 3820 DESCRIPTION 3821 "Write access is not required." 3823 OBJECT atmVclRowStatus 3824 SYNTAX INTEGER {active(1)} 3825 -- subset of RowStatus 3826 MIN-ACCESS read-only 3827 DESCRIPTION 3828 "Write access is not required, and only one 3829 of the six enumerated values for the 3830 RowStatus textual convention need be 3831 supported, specifically: active(1)." 3833 OBJECT atmVcCrossConnectLowVpi 3834 SYNTAX INTEGER (0..255) 3835 DESCRIPTION 3836 "For ATM UNIs supporting VCCs, the VPI value 3837 at the numerically lower ATM interface port 3838 index number ranges from 0 to 255." 3840 OBJECT atmVcCrossConnectHighVpi 3841 SYNTAX INTEGER (0..255) 3842 DESCRIPTION 3843 "For ATM UNIs supporting VCCs, the VPI value 3844 at the numerically higher ATM interface port 3845 index number ranges from 0 to 255." 3847 OBJECT atmVcCrossConnectAdminStatus 3848 MIN-ACCESS read-only 3849 DESCRIPTION 3850 "Write access is not required." 3852 OBJECT atmVcCrossConnectRowStatus 3853 SYNTAX INTEGER { active(1)} 3854 -- subset of RowStatus 3855 MIN-ACCESS read-only 3856 DESCRIPTION 3857 "Write access is not required, and only one 3858 of the six enumerated values for the 3859 RowStatus textual convention need be 3860 supported, specifically: active(1)." 3862 GROUP aal5VccGroup 3863 DESCRIPTION 3865 draft ATM Management Objects June 26, 1996 3867 "This group is mandatory for the 3868 AAL5 virtual connections only." 3870 OBJECT aal5VccVpi 3871 SYNTAX INTEGER (0..255) 3872 DESCRIPTION 3873 "For ATM UNIs supporting AAL5 VCCs, 3874 the VPI value ranges from 0 to 255." 3876 OBJECT atmVccAal5CpcsTransmitSduSize 3877 MIN-ACCESS read-only 3878 DESCRIPTION 3879 "Write access is not required." 3881 OBJECT atmVccAal5CpcsReceiveSduSize 3882 MIN-ACCESS read-only 3883 DESCRIPTION 3884 "Write access is not required." 3886 OBJECT atmVccAal5EncapsType 3887 MIN-ACCESS read-only 3888 DESCRIPTION 3889 "Write access is not required." 3890 ::= { atmMIBCompliances 1 } 3892 -- Deprecated Definitions - Groups 3894 atmInterfaceConfGroup OBJECT-GROUP 3895 OBJECTS { 3896 atmInterfaceMaxVpcs, atmInterfaceMaxVccs, 3897 atmInterfaceConfVpcs, atmInterfaceConfVccs, 3898 atmInterfaceMaxActiveVpiBits, 3899 atmInterfaceMaxActiveVciBits, 3900 atmInterfaceIlmiVpi, 3901 atmInterfaceIlmiVci, 3902 atmInterfaceAddressType, 3903 atmInterfaceAdminAddress, 3904 atmInterfaceMyNeighborIpAddress, 3905 atmInterfaceMyNeighborIfName} 3906 STATUS deprecated 3907 DESCRIPTION 3908 "A collection of objects providing configuration 3909 information about an ATM interface." 3911 draft ATM Management Objects June 26, 1996 3913 ::= { atmMIBGroups 1 } 3915 atmTrafficDescrGroup OBJECT-GROUP 3916 OBJECTS { 3917 atmTrafficDescrType, atmTrafficDescrParam1, 3918 atmTrafficDescrParam2, atmTrafficDescrParam3, 3919 atmTrafficDescrParam4, atmTrafficDescrParam5, 3920 atmTrafficQoSClass, atmTrafficDescrRowStatus} 3921 STATUS deprecated 3922 DESCRIPTION 3923 "A collection of objects providing information 3924 about ATM traffic descriptor type and 3925 the associated parameters." 3926 ::= { atmMIBGroups 2 } 3928 atmVpcTerminationGroup OBJECT-GROUP 3929 OBJECTS {atmVplOperStatus, atmVplAdminStatus, 3930 atmVplLastChange, 3931 atmVplReceiveTrafficDescrIndex, 3932 atmVplTransmitTrafficDescrIndex, 3933 atmVplRowStatus } 3934 STATUS deprecated 3935 DESCRIPTION 3936 "A collection of objects providing 3937 information about a VPL at an ATM interface 3938 which terminates a VPC 3939 (i.e., one which is NOT cross-connected 3940 to other VPLs)." 3941 ::= { atmMIBGroups 5 } 3943 atmVccTerminationGroup OBJECT-GROUP 3944 OBJECTS {atmVclOperStatus, atmVclAdminStatus, 3945 atmVclLastChange, 3946 atmVclReceiveTrafficDescrIndex, 3947 atmVclTransmitTrafficDescrIndex, 3948 atmVccAalType, atmVclRowStatus } 3949 STATUS deprecated 3950 DESCRIPTION 3951 "A collection of objects providing information 3952 about a VCL at an ATM interface 3953 which terminates a VCC (i.e., one which is 3954 NOT cross-connected to other VCLs)." 3955 ::= { atmMIBGroups 6 } 3957 atmVpCrossConnectGroup OBJECT-GROUP 3959 draft ATM Management Objects June 26, 1996 3961 OBJECTS { atmVplReceiveTrafficDescrIndex, 3962 atmVplTransmitTrafficDescrIndex, 3963 atmVplOperStatus, atmVplRowStatus, 3964 atmVpCrossConnectAdminStatus, 3965 atmVpCrossConnectL2HOperStatus, 3966 atmVpCrossConnectH2LOperStatus, 3967 atmVpCrossConnectL2HLastChange, 3968 atmVpCrossConnectH2LLastChange, 3969 atmVpCrossConnectRowStatus, 3970 atmVplCrossConnectIdentifier, 3971 atmVpCrossConnectIndexNext } 3972 STATUS deprecated 3973 DESCRIPTION 3974 "A collection of objects providing 3975 information about a VP cross-connect 3976 and the associated VPLs that are 3977 cross-connected together." 3978 ::= { atmMIBGroups 7 } 3980 atmVcCrossConnectGroup OBJECT-GROUP 3981 OBJECTS { atmVclReceiveTrafficDescrIndex, 3982 atmVclTransmitTrafficDescrIndex, 3983 atmVclOperStatus, atmVclRowStatus, 3984 atmVcCrossConnectAdminStatus, 3985 atmVcCrossConnectL2HOperStatus, 3986 atmVcCrossConnectH2LOperStatus, 3987 atmVcCrossConnectL2HLastChange, 3988 atmVcCrossConnectH2LLastChange, 3989 atmVcCrossConnectRowStatus, 3990 atmVclCrossConnectIdentifier, 3991 atmVcCrossConnectIndexNext } 3992 STATUS deprecated 3993 DESCRIPTION 3994 "A collection of objects providing 3995 information about a VC cross-connect 3996 and the associated VCLs that are 3997 cross-connected together." 3998 ::= { atmMIBGroups 8 } 4000 END 4002 draft ATM Management Objects June 26, 1996 4004 13. Acknowledgments 4006 This memo is the result of the work of the AToMMIB Working 4007 Group. 4009 draft ATM Management Objects June 26, 1996 4011 14. References 4013 [1] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., 4014 and S. Waldbusser, "Structure of Management Information 4015 for version 2 of the Simple Network Management Protocol 4016 (SNMPv2)", RFC 1902, January 1996. 4018 [2] McCloghrie, K., and M. Rose, Editors, "Management 4019 Information Base for Network Management of TCP/IP-based 4020 internets: MIB-II", STD 17, RFC 1213, Hughes LAN Systems, 4021 Performance Systems International, March 1991. 4023 [3] Case, J., Fedor, M., Schoffstall, M., and J. Davin, 4024 "Simple Network Management Protocol", RFC 1157, SNMP 4025 Research, Performance Systems International, Performance 4026 Systems International, MIT Laboratory for Computer 4027 Science, May 1990. 4029 [4] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., 4030 and S. Waldbusser, "Protocol Operations for version 2 of 4031 the Simple Network Management Protocol (SNMPv2)", RFC 4032 1905, January 1996. 4034 [5] McCloghrie, K. and F. Kastenholz, "The Interfaces Group 4035 MIB", Internet-Draft, cisco Systems, FTP Software, 4036 February 1996. 4038 [6] Brown, T.A. and K. Tesink, "Definitions of Managed 4039 Objects for SMDS Interfaces", RFC 1694, Bellcore, May 4040 1994. 4042 [7] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 4043 "Textual Conventions for version 2 of the Simple Network 4044 Management Protocol (SNMPv2)", RFC1903, SNMP 4045 Research,Inc., Hughes LAN Systems, Dover Beach 4046 Consulting, Inc., Carnegie Mellon University, April 1993. 4048 [8] Michael Noto, Kaj Tesink, "ATM Textual Conventions and 4049 OBJECT-IDENTITIES", Internet-Draft, Bellcore, June 1996. 4051 [9] "ATM Forum UNI Specification, Version 3.0", September 4052 1993. 4054 [10] "ATM Forum B-ICI Specification, Version 1.0", September 4055 1993. 4057 draft ATM Management Objects June 26, 1996 4059 [11] "ATM Forum Private Network-Network Interface 4060 Specification, Version 1.0 (P-NNI 1.0)", af-sig- 4061 0061.0000, June 1996. 4063 draft ATM Management Objects June 26, 1996 4065 15. Security Considerations 4067 Security issues are not discussed in this memo. 4069 16. Author's Address 4071 Kaj Tesink 4072 Bell Communications Research 4073 331 Newman Springs Road 4074 P.O. Box 7020 4075 Red Bank, NJ 07701-7020 4076 Phone: (908) 758-5254 4077 EMail: kaj@cc.bellcore.com 4079 draft ATM Management Objects June 26, 1996 4081 Table of Contents 4083 1 Status of this Memo ................................... 1 4084 2 Introduction .......................................... 2 4085 3 Change Log ............................................ 2 4086 4 The SNMPv2 Network Management Framework ............... 4 4087 5 Object Definitions .................................... 5 4088 6 ATM Terminology ....................................... 6 4089 6.1 VCL/VPL and VCC/VPC ................................. 6 4090 6.2 PVC, SVC and Soft PVC ............................... 8 4091 6.3 Traffic Management Parameters ....................... 9 4092 6.3.1 Traffic Policing and Traffic Shaping Parameters 4093 .................................................... 9 4094 6.3.2 Cell Loss Priority ................................ 9 4095 6.3.3 QoS Class ......................................... 10 4096 6.3.4 Service Category .................................. 10 4097 6.4 Max Active and Max Current VPI and VCI Bits ......... 10 4098 7 Overview .............................................. 11 4099 7.1 Background .......................................... 12 4100 7.2 Structure of the MIB ................................ 12 4101 7.3 ATM Interface Configuration Group ................... 12 4102 7.4 ATM Interface DS3 PLCP and TC Layer Groups .......... 13 4103 7.5 ATM Virtual Link and Cross-Connect Groups ........... 13 4104 8 Application of MIB II to ATM .......................... 13 4105 8.1 The System Group .................................... 13 4106 8.2 The Interface Group ................................. 13 4107 8.2.1 Support of the ATM Cell Layer by ifTable .......... 14 4108 9 Support of the AAL3/4 Based Interfaces ................ 16 4109 10 Support of the AAL5 Managed Objects .................. 17 4110 10.1 Managing AAL5 in a Switch .......................... 17 4111 10.2 Managing AAL5 in a Host ............................ 18 4112 10.3 Support of AAL5 by ifTable ......................... 20 4113 10.4 Support of Proprietary Virtual Interface by ifT- 4114 able ............................................... 22 4115 10.5 AAL5 Connection Performance Statistics Group ....... 23 4116 11 ILMI MIB and the ATM Managed Objects ................. 24 4117 12 Definitions .......................................... 27 4118 13 Acknowledgments ...................................... 97 4119 14 References ........................................... 98 4120 15 Security Considerations .............................. 100 4121 16 Author's Address ..................................... 100 4123 draft ATM Management Objects June 26, 1996