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