idnits 2.17.1 draft-ietf-atommib-atm2-12.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Cannot find the required boilerplate sections (Copyright, IPR, etc.) in this document. Expected boilerplate is as follows today (2024-04-26) according to https://trustee.ietf.org/license-info : IETF Trust Legal Provisions of 28-dec-2009, Section 6.a: This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79. IETF Trust Legal Provisions of 28-dec-2009, Section 6.b(i), paragraph 2: Copyright (c) 2024 IETF Trust and the persons identified as the document authors. All rights reserved. IETF Trust Legal Provisions of 28-dec-2009, Section 6.b(i), paragraph 3: This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- ** Missing 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 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: ' 13. 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. Miscellaneous warnings: ---------------------------------------------------------------------------- == Line 2392 has weird spacing: '... to ven...' == Line 2907 has weird spacing: '...LP=0 an disca...' == Line 3073 has weird spacing: '...LP=0 an disca...' == Line 4767 has weird spacing: '...l Port inter...' -- 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 (March 13, 1998) is 9541 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 4598 looks like a reference -- Missing reference section? '2' on line 4603 looks like a reference -- Missing reference section? '3' on line 4610 looks like a reference -- Missing reference section? '5' on line 4615 looks like a reference -- Missing reference section? '6' on line 4621 looks like a reference -- Missing reference section? '15' on line 4664 looks like a reference -- Missing reference section? '14' on line 4660 looks like a reference -- Missing reference section? '9' on line 4637 looks like a reference -- Missing reference section? '10' on line 4642 looks like a reference -- Missing reference section? '21' on line 4692 looks like a reference -- Missing reference section? '13' on line 4655 looks like a reference -- Missing reference section? '7' on line 4625 looks like a reference -- Missing reference section? '8' on line 4631 looks like a reference -- Missing reference section? '11' on line 4645 looks like a reference -- Missing reference section? '12' on line 4651 looks like a reference -- Missing reference section? '16' on line 4668 looks like a reference -- Missing reference section? '17' on line 4673 looks like a reference -- Missing reference section? '18' on line 4679 looks like a reference -- Missing reference section? '19' on line 4683 looks like a reference -- Missing reference section? '20' on line 4689 looks like a reference -- Missing reference section? '22' on line 4696 looks like a reference Summary: 11 errors (**), 0 flaws (~~), 5 warnings (==), 23 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 INTERNET-DRAFT 2 4 Definitions of Supplemental Managed Objects 5 for ATM Management 7 March 13, 1998 9 Faye Ly (editor) 10 3Com Corporation 11 fayely@3com.com 13 Michael Noto (editor) 14 Network Equipment Technologies 15 mike_noto@net.com 17 Andrew Smith (editor) 18 Extreme Networks 19 ansmith@extremenetworks.com 21 Ethan Mickey Spiegel (editor) 22 Cisco Systems 23 mspiegel@cisco.com 25 Kaj Tesink (editor) 26 Bell Communications Research 27 kaj@cc.bellcore.com 29 1. Status of this Memo 31 This document is an Internet Draft. Internet Drafts are 32 working documents of the Internet Engineering Task Force 33 (IETF), its Areas, and its Working Groups. Note that other 34 groups may also distribute working documents as Internet 35 Drafts. 37 draft Supplemental ATM Management Objects Mar 13, 1998 39 Internet Drafts are valid for a maximum of six months and may 40 be updated, replaced, or obsoleted by other documents at any 41 time. It is inappropriate to use Internet Drafts as reference 42 material or to cite them other than as a "work in progress". 44 draft Supplemental ATM Management Objects Mar 13, 1998 46 2. Introduction 48 This memo defines an experimental portion of the Management 49 Information Base (MIB) for use with network management 50 protocols in the Internet community. In particular, it 51 describes objects used for managing ATM-based interfaces, 52 devices, and services in addition to those defined in the 53 ATM-MIB [1], to provide additional support for the management 54 of: 55 - ATM Switched Virtual Connections (SVCs) 56 - ATM Permanent Virtual Connections (PVCs) 58 This memo specifies a MIB module in a manner that is both 59 compliant to the SNMPv2 SMI, and semantically identical to the 60 peer SNMPv1 definitions. 62 This memo does not specify a standard for the Internet 63 community. 65 3. Change Log 67 This section tracks changes made to the revisions of the 68 Internet Drafts of this document. It will be deleted when the 69 document is published as an RFC. 71 The following changes were made for the version of the 72 document dated March 13, 1998. 74 - Changed atmSwitchAddressTable entry in Table 1 of section 75 6.3, to indicate that it only applies to switches. 76 - Added missing figure headings, fixed figure numbers, and 77 changed pagination to prevent page breaks within figures. 78 - Clarified usage of ATM Logical Port Interface Table, and 79 of atmInterfaceExtEntry attributes for atmLogical(80) 80 interfaces. 81 - Removed IMPORTS for TEXTUAL-CONVENTION, atmVplOperStatus, 82 and atmVclOperStatus. 83 - Added IMPORTS for InterfaceIndexOrZero. 84 - Changed SYNTAX of the atmVplLogicalPortIndex object from 85 InterfaceIndex to InterfaceIndexOrZero, and updated its 86 DESCRIPTION. 87 - Swapped INTEGER and BITS types for atmIntfIlmiOperStatus 89 draft Supplemental ATM Management Objects Mar 13, 1998 91 and atmIntfIlmiFsmState in AtmInterfaceExtEntry SEQUENCE. 92 - Changed atmSwitchAddressAddress from AtmAddr to OCTET 93 STRING in AtmSwitchAddressEntry SEQUENCE. 94 - Replaced "OBJECT-IDENTIFIER" with the correct keywords 95 "OBJECT IDENTIFIER" for atmPvcTraps and atmPvcTrapsPrefix. 96 - Changed DESCRIPTION of atmSigDescrParamIndex to refer to 97 the atmVclGenSigDescrIndex object in the atmVclGenTable. 98 - Removed spurious commas after several OBJECT compliance 99 clauses. 100 - Added OBJECT clauses for atmCurrentlyFailingPV.lTimeStamp 101 objects, to note that they are optional. 102 - Changed the atmSwitchServcHostGroup OBJECTS list to remove 103 old objects (atmPv.lTrapControl and atmTrapThreshold) and 104 to add new objects (atmCurrentlyFailingPV.lTimeStamp). 105 - Changed atmSwitchServcNotifGroup to a NOTIFICATION-GROUP. 106 - Added an atmSwitchGroup for the atmSwitchAddressAddress 107 and the atmSwitchAddressRowStatus objects. 108 - Updated references from RFC 1573 to RFC 2233. Tweaked 109 some other references. 110 - Made other minor editorial changes, including a number 111 that affected the indentation of object DESCRIPTIONs. 113 The following changes were made for the version of the 114 document dated July 30, 1997. 116 - Changed the name of the objects atmInterfaceConfigSigType, 117 atmInterfaceActualSigType, atmInterfaceConfigSigSide, and 118 atmInterfaceActualSigSide to atmIntfConfigType, 119 atmIntfActualType, atmIntfConfigSide and atmIntfActualSide 120 - Changed the name of the atmIfAdminAddrTable to 121 atmIfRegisteredAddrTable, as agreed in the December 122 meeting, and rewrote DESCRIPTION 123 - Changed atmInterfaceExtEntry to augment 124 atmInterfaceConfEntry from RFC 1695/atm1ng 125 - Reordered atmInterfaceExtEntry 126 - Changed names of objects for ILMI-related initial timer 127 values and public/private indicator so that length is less 128 than 32 characters 129 - Changed range of max VPI values from (0..4096) to 130 (0..4095) 131 - Restored missing atmInterfaceConfMinSvccVci and 132 atmInterfaceCurrentMinSvccVci objects 133 - Made atmInterfaceCurrentM..Sv.cV.i objects read-only. 134 - Deleted atmIlmiSrvcRegSource 136 draft Supplemental ATM Management Objects Mar 13, 1998 138 - Added atmVpCrossConnextXTable and atmVcCrossConnectXTable 139 with service user and service provider assigned names 140 - Deleted atmPvplChange and atmPvclChange traps 142 The following changes were made for the version of the 143 document dated July 6, 1997. 145 - Replaced current ATM trap support with new trap proposal 146 - Added ATM switch address table 147 - Deleted atmAal5VclTotalErrors 148 - Replaced atmIntfIlmiAddressRegistration with 149 atmIntfIlmiAdminStatus 150 - Added atmIntfIlmiOperStatus and atmIntfIlmiFsmState to 151 atmInterfaceExtEntry 152 - Added atmIfAdminAddrOrgScope to atmIfAdminAddrTable 153 - Added atmIntfSigVccRcvTrafficDescrIndex and 154 atmIntfSigVccTrxTrafficDescrIndex to atmInterfaceExtTable 156 draft Supplemental ATM Management Objects Mar 13, 1998 158 4. The SNMPv2 Network Management Framework 160 The SNMPv2 Network Management Framework consists of three 161 major components. They are: 163 0 RFC 1902 [2] which defines the SMI, the mechanisms used 164 for describing and naming objects for the purpose of 165 management. 167 0 STD 17, RFC 1213 [3] defines MIB-II, the core set of 168 managed objects for the Internet suite of protocols. 170 0 RFC 1905 [5] which defines the protocol used for network 171 access to managed objects. 173 The Framework permits new objects to be defined for the 174 purpose of experimentation and evaluation. 176 5. Object Definitions 178 Managed objects are accessed via a virtual information store, 179 termed the Management Information Base or MIB. Objects in the 180 MIB are defined using the subset of Abstract Syntax Notation 181 One (ASN.1) defined in the SMI. In particular, each object 182 type is named by an OBJECT IDENTIFIER, an administratively 183 assigned name. The object type together with an object 184 instance serves to uniquely identify a specific instantiation 185 of the object. For human convenience, we often use a textual 186 string, termed the descriptor, to also refer to the object 187 type. 189 6. Overview 191 The purpose of this memo is to provide additional 192 capabilities, not found in the ATM-MIB [1], which are needed 193 to manage ATM interfaces. This memo addresses the following 194 areas: 195 - ATM Switch Support 196 - ATM Service Support 197 - ATM Host Support 199 In addition, this memo also provides ATM trap support. 201 draft Supplemental ATM Management Objects Mar 13, 1998 203 6.1. Background 205 In addition to the MIB module defined in this memo, other MIB 206 modules are necessary to manage ATM interfaces, links and 207 cross-connects. Examples include MIB II for general system 208 and interface management (RFC 1213 [3] and RFC 2233 [6]), the 209 DS3 or SONET MIBs for management of SONET and DS3 physical 210 interfaces, and, as appropriate, MIB modules for applications 211 that make use of ATM, such as SMDS [15] and LAN Emulation 212 [14]. These MIB modules are outside the scope of this 213 specification. 215 This MIB module also requires the use of the ATM-MIB module 216 defined in [1]. 218 ATM Endpoint applications such as ATM LAN Emulation or 219 Classical IP-over-ATM Clients and Servers use ATM to establish 220 SVC/PVC connections for exchanging control and data 221 information. The agents of these ATM applications must provide 222 the network manager with information on the SVC/PVCs in use 223 and which applications are using them. The information can be 224 made generic so as to apply to all ATM applications. This 225 memo proposes extensions to the ATM-MIB [1] in order to 226 support this. 228 The current specification of this supplemental ATM-MIB is 229 based on SNMPv2 SMI. 231 6.2. Important Definitions 233 The following terms are defined here and used throughout this 234 MIB: 235 - Virtual Path Link (VPL) 236 - Virtual Path Connection (VPC) 237 - Virtual Path Segment (VP Segment) 238 - Virtual Channel Link (VCL) 239 - Virtual Channel Connection (VCC) 240 - Virtual Channel Segment (VC Segment). 242 The figures on the next page show how these terms apply in 243 typical ATM network topologies. 245 draft Supplemental ATM Management Objects Mar 13, 1998 247 _____ _______ _______ _______ _____ 248 | |____| |____| |____| |____| | 249 |Host1| |SwitchA| |SwitchB| |SwitchC| |Host2| 250 | |____| |____| |____| |____| | 251 |_____| |_______| |_______| |_______| |_____| 253 |<----->| Virtual |<----->| Virtual 254 Path Link Path Link 256 |<------------Virtual Path Connection---------->| 257 (between Host1 and Host2) 259 |<--------------->| Virtual Path 260 Segment (between 261 SwitchA and SwitchC) 263 Figure 1: Examples of Virtual Path Links, Virtual Path 264 Connection, and Virtual Path Segment 266 _____ _______ _______ _______ _____ 267 | |____| |____| |____| |____| | 268 |Host1|----|SwitchA|----|SwitchB|----|SwitchC|----|Host2| 269 | |____| |____| |____| |____| | 270 |_____| |_______| |_______| |_______| |_____| 272 |<----->| Virtual |<----->| Virtual 273 Channel Link Channel Link 275 |<----------Virtual Channel Connection--------->| 276 (between Host1 and Host2) 278 |<--------------->| Virtual Channel 279 Segment (between 280 SwitchA and SwitchC) 282 Figure 2: Examples of Virtual Channel Links, Virtual 283 Channel Connection, and Virtual Channel Segment 285 draft Supplemental ATM Management Objects Mar 13, 1998 287 6.3. Supported Functions 289 The managed ATM objects are arranged as follows: 291 Table Host Switch Service 292 _____________________________________________________ 293 atmSvcVcCrossConnectTable | | Y | Y | 294 atmSvcVpCrossConnectTable | | Y | Y | 296 atmSigStatTable | Y | Y | Y | 297 atmSigSupportTable | | Y | Y | 298 atmSigDescrParamTable | Y | | | 300 atmIfRegisteredAddrTable | | Y | Y | 301 atmVclAddrTable | Y | | | 302 atmAddrVclTable | Y | | | 304 atmVplStatTable | Y | Y | Y | 305 atmVplLogicalPortTable | Y | Y | Y | 307 atmVclStatTable | Y | Y | Y | 308 atmAal5VclStatTable | Y | | | 309 atmVclGenTable | Y | | | 311 atmInterfaceExtTable | Y | Y | Y | 313 atmIlmiSrvcRegTable | | Y | Y | 314 atmIlmiNetworkPrefixTable | | Y | Y | 315 atmSwitchAddressTable | | Y | | 317 atmVpCrossConnectXTable | | | Y | 318 atmVcCrossConnectXTable | | | Y | 320 atmCurrentlyFailingPVplTable | Y | Y | Y | 321 atmCurrentlyFailingPVclTable | Y | Y | Y | 323 Table 1: MIB structure 325 draft Supplemental ATM Management Objects Mar 13, 1998 327 6.3.1. ATM SVC VC Cross-Connect Table 329 This table provides the SVC Cross-Connect information. The 330 equivalent PVC VC Cross-Connect table is defined in [1]. This 331 table also includes cross-connect information for Soft PVCs. 333 This group is used to model a bi-directional point-to-point, 334 point-to-multipoint or multipoint-to-multipoint SVC VC cross- 335 connect. 337 This table has read-only access and is used to monitor the 338 cross-connects which connect the VCLs together in an ATM 339 switch or network that belong to a VC connection. The 340 atmSvcVcCrossConnectIndex is used to associate the related SVC 341 VCLs that are cross-connected together. The 342 atmSvcVcCrossConnectRowStatus object has read-write access to 343 allow for tear-down. 345 The ATM SVC VC Cross-Connect Table models each bi-directional 346 Switched Virtual Circuit (SVC) VC cross-connect as a set of 347 entries in the atmSvcVcCrossConnectTable. A point-to-point VC 348 cross-connect is modeled as one entry; a point-to-multipoint 349 (N leafs) VC cross-connect as N entries in this table; and a 350 multipoint-to-multipoint (N parties) VPC cross-connect as 351 N(N-1)/2 entries in this table. In the latter cases, all the 352 N (or N(N-1)/2) entries are associated with a single VPC 353 cross-connect by having the same value of 354 atmSvcVcCrossConnectIndex. 355 ______________________________________ 356 | | 357 Low | ATM Switch or Network | High 358 port| | port 359 _____|>> from low to high VC traffic flow >>|______ 360 |<< from high to low VC traffic flow <<| 361 | | 362 |______________________________________| 364 Figure 3: VC Cross-Connect Model 366 The terms low and high are chosen to represent numerical 367 ordering of the two interfaces associated with a VPC cross- 368 connect. That is, the ATM interface with the lower value of 369 ifIndex is termed 'low', while the other ATM interface 370 draft Supplemental ATM Management Objects Mar 13, 1998 372 associated with the VPC cross-connect is termed 'high'. This 373 terminology is used to provide directional information; for 374 example, the atmSvcVcCrossConnectL2HOperStatus applies to the 375 low->high direction, and atmSvcVcCrossConnectH2LOperStatus 376 applies to the high->low direction. 378 6.3.2. ATM SVC VP Cross-Connect Table 380 This table provides the SVC VP Cross-Connect information. The 381 equivalent PVC VP Cross-Connect table is defined in [1]. This 382 table also includes cross-connect information for Soft PVPs. 384 This group contains configuration and state information of all 385 SVC VP point-to-point, point-to-multipoint, or multipoint-to- 386 multipoint VP cross-connects. 388 This table has read-only access and can be used to monitor the 389 cross-connects which connect the VPLs together in an ATM 390 switch or network. The atmSvcVpCrossConnectIndex is used to 391 associate the related SVC VPLs that are cross-connected 392 together. The atmSvcVpCrossConnectRowStatus object has read- 393 write access to allow for tear-down. 395 The ATM SVC VP Cross-Connect Table models each bi-directional 396 Switched Virtual Circuit (SVC) VP cross-connect as a set of 397 entries in the atmSvcVpCrossConnectTable. A point-to-point 398 VPC cross-connect is modeled as one entry; a point-to- 399 multipoint (N leafs) VPC cross-connect as N entries in this 400 table; and a multipoint-to-multipoint (N parties) VPC cross- 401 connect as N(N-1)/2 entries in this table. In the latter 402 cases, all the N (or N(N-1)/2) entries are associated with a 403 single VPC cross-connect by having the same value of 404 atmSvcVpCrossConnectIndex. 406 _________________________________________ 407 | | 408 Low | ATM Switch or Network | High 409 port| | port 410 _____|>> from low to high VPC traffic flow >>|______ 411 |<< from high to low VPC traffic flow <<| 412 | | 413 |_______________________________________| 415 Figure 4: VPC Cross-Connect Model 417 draft Supplemental ATM Management Objects Mar 13, 1998 419 The terms low and high are chosen to represent numerical 420 ordering of the two interfaces associated with a VPC cross- 421 connect. That is, the ATM interface with the lower value of 422 ifIndex is termed 'low', while the other ATM interface 423 associated with the VPC cross-connect is termed 'high'. This 424 terminology is used to provide directional information; for 425 example, the atmSvcVpCrossConnectL2HOperStatus applies to the 426 low->high direction, and atmSvcVpCrossConnectH2LOperStatus 427 applies to the high->low direction. 429 6.3.3. ATM Interface Signalling Statistics Table 431 This table provides statistical information of the signalling 432 entity. A signalling entity can be deployed over an ATM 433 interface as defined in the atmInterfaceConfTable [1], a 434 logical ATM interface defined in section 6.3.10.1 in this 435 document or a proprietary virtual interface as described 436 atmInterfaceExtTable. To monitor the signalling entity, a few 437 counters are provided. They are defined as: 438 atmSigSSCOPConEvents 439 atmSigSSCOPErrdPdus 440 atmSigDetectSetupAttempts 441 atmSigEmitSetupAttempts 442 atmSigDetectUnavailRoutes 443 atmSigEmitUnavailRoutes 444 atmSigDetectUnavailResrcs 445 atmSigEmitUnavailResrcs 446 atmSigDetectCldPtyEvents 447 atmSigEmitCldPtyEvents 448 atmSigDetectMsgErrors 449 atmSigEmitMsgErrors 450 atmSigDetectClgPtyEvents 451 atmSigEmitClgPtyEvents 452 atmSigDetectTimerExpireds 453 atmSigEmitTimerExpireds 454 atmSigDetectRestarts 455 atmSigEmitRestarts 456 atmSigInEstabls 457 atmSigOutEstabls 459 6.3.4. ATM Signalling Capability Support 461 A number of Information Elements may or may not be supported 462 by ATM switches or ATM Service. Hence, for trouble isolation 463 draft Supplemental ATM Management Objects Mar 13, 1998 465 it is important to keep track which particular Information 466 Elements are supported. The corresponding group of objects 467 must be supported by switches or services supporting SVCs, and 468 indicate whether the following Information Elements are 469 enabled/disabled: 471 1) Calling party number 473 2) Calling party subaddress 475 3) Called party subaddress 477 4) Broadband high layer information 479 5) Broadband low layer information 481 6) Broadband Repeat Indicator 483 7) AAL parameters 485 The last parameter, Preferred Carrier Pre-Subscription, 486 identifies the carrier to which intercarrier calls originated 487 from this interface are routed when transit network selection 488 information is not provided by the calling party. 490 6.3.5. Signalling Descriptor Parameter Table 492 This table extends the ATM VCL table of the ATM-MIB [1] to 493 include all other necessary signalling information as 494 specified in the ATM Forum UNI Specifications [9] and [10]. A 495 user can create an entry with all signalling parameters and 496 later use that entry to specify the signalling characteristics 497 of SVCs. 499 Some of the signalling parameters such as the AAL5 parameters 500 information element is reflected in the VCL and VPL tables, 501 and this table only contains the remaining AAL5 parameters 502 information. 504 Signalling attributes can be grouped into following 505 categories: 507 draft Supplemental ATM Management Objects Mar 13, 1998 509 1) ATM Adaptation Layer Parameters 511 Information in this group are captured in the ATM Signalling 512 Descriptor Parameter Table defined in this memo. Please refer 513 to section 5.4.5.5 of [9] and [10]. 515 2) Broadband High Layer Information 517 Information in this group are captured by the ATM Signalling 518 Descriptor Parameter Table defined in this memo. Please refer 519 to section 5.4.5.8 of [9] and [10]. 521 3) Broadband Low Layer Information 523 Information in this group are captured by the ATM Signalling 524 Descriptor Parameter Table defined in this memo. Please refer 525 to section 5.4.5.9 of [9] and [10]. 527 6.3.6. ATM Interface Registered Address Table 529 This table contains a list of ATM addresses that can be used 530 for calls to and from a given interface by a switch or 531 service. The ATM addresses are either registered by the 532 endsystem via ILMI or statically configured. This table does 533 not expose PNNI reachability information. This table only 534 applies to switches and network services. See also Section 7. 536 6.3.7. ATM VPI/VCI to Address Mapping Table 538 In the atmVclAddrTable, the object atmVclAddrAddr can either 539 be an ATM Local Address or an ATM Remote Address which 540 represent the two endpoint addresses of a VCL. ATM Local 541 Address identifies the local endpoint of the VCL represented 542 by this agent. While, the ATM Remote address represents the 543 address of the ATM application at the other end of the VCL. 545 6.3.8. ATM Address to VPI/VCI Mapping Table 547 This table provides an alternative way to retrieve the 548 atmVclTable. This table can be used to retrieve the indexing 549 to the atmVclTable by an ATM address. 551 draft Supplemental ATM Management Objects Mar 13, 1998 553 6.3.9. ATM VPL Statistics Table 555 The atmVplStatTable includes per VPL cell counters. The VPL 556 cell counters count the valid ATM cells. The valid ATM cells 557 include the user and OAM cells but exclude the physical layer 558 (e.g., idle cells) and unassigned cells. Cells coming into an 559 ATM managed system are counted differently with the high Cell 560 Loss Priority (CLP=0) or low Cell Loss Priority (CLP=1). The 561 cells are tagged, passed or discarded depending on the 562 incoming CLP value and the policed cell rate by the "traffic 563 policing" entity in the ATM managed system. Refer to [9] and 564 [10] for the description of the traffic policing. 566 In the switch where the traffic policing is not supported, 567 cells are passed or discarded depending on the bandwidth of 568 the switching fabric. The Output Tagged Cells counter, in 569 this case, is always zero. 571 _______________ 572 | ATM Managed | 573 Input | System | Output 574 CLP=0 cells| | CLP=0 cells 575 ---------->| |-----------> 576 CLP=1 cells| (traffic | CLP=1 cells 577 ---------->| policing |-----------> 578 | entity) | Tagged cells (CLP=1) 579 |_____________|-----------> 580 |Discard | Discard 581 |CLP=0 | CLP=1 582 |cells | cells 583 | | 584 V V 586 Figure 5: ATM Cell Counters per VPL 588 In this table, cells coming into and out of the managed ATM 589 system are counted as the total number of cells and the cells 590 with the CLP=0. The CLP=1 counter is derived by subtracting 591 CLP=0 cells from the total cells. In addition, cells that are 592 tagged on the output are also counted. The output CLP=1 cells 593 equals to the total cells out count minus both the CLP=0 cells 594 and the tagged cells. 596 draft Supplemental ATM Management Objects Mar 13, 1998 598 6.3.10. ATM VPL Logical Port Table 600 The ATM VPL Logical Port Table includes all ATM logical port 601 interface configuration information. 603 6.3.10.1. ATM Logical Port Interface 605 The interface type "ATM Logical Port" (ifType=80) is defined 606 to allow the representation of a VP Tunnel, which is a VPL 607 used as a trunk connection (most likely between devices that 608 are not physically adjacent), providing for multiplexing and 609 demultiplexing of VCs on the VP. Figure 6 illustrates such a 610 VP Tunnel. 612 Note: the "ATM Logical Port" interface is more of a logical 613 port, compared with an interface of type "ATM" which is more 614 of a physical port that provides for the transport of many VP 615 and VC connections between adjacent devices. 617 <------VP Tunnel------> 618 ATM Switch A ATM Switch B 619 ------------ ----------- 620 |ATM |_____________|ATM | 621 |X-Connect | . |X-Connect | 622 VCL1 |Point | VPL1 . VPL2 |Point | VCL4 623 O---------|----X-----|----- . -----|----X-----|-----O 624 | X-----|----- . -----|----X | 625 | | |_____________| | | 626 ------------ ------------ 627 | VCL2 | VCL3 628 O O 630 Figure 6: Virtual Path Tunnel 632 In Figure 6, a VP tunnel (denoted as VPL1 by Switch A, and as 633 VPL2 by Switch B) is used to connect VCL1 with VCL4 and VCL2 634 with VCL3. Figure 6 shows only one VP tunnel, but there can 635 be multiple VP tunnels over the same physical interface. 637 A particularly useful VP tunnel scenario is tunneling across a 638 public network that does not support signalling. In Figure 6 639 above, assume Switches A and B are private switches that 640 signal over the VP to set up connections transparently through 641 draft Supplemental ATM Management Objects Mar 13, 1998 643 the public network. The public network would just transport a 644 PVC VP between the two switches. 646 Because the VP Tunnel constitutes an interface between two ATM 647 devices that are not necessarily physically adjacent, most of 648 the management information pertaining to the interface may 649 differ for the tunnel, including: 650 - active VPI/VCI fields (the tunnel may be a subset 651 of the parent interface). 652 - maximum number of VCCs 653 - configured VCCs 654 - ILMI VPI/VCI values 655 - ATM address type 656 - ATM administrative address 657 - received/transmitted cells. 659 6.3.10.2. How to create an ATM Logical Port interface 661 On ATM devices supporting VP tunnels, the ATM Logical Port 662 Interface Table can be used to create VP tunnels. To create 663 an ATM Logical Port interface via SNMP: 664 - Create a VPL (e.g., VPI=a on an existing ATM interface 665 which has ifIndex=x) in the atmVplTable. 667 - Set the object atmVplLogicalPortDef to isLogicalIf. 668 A new row in the ifTable is then created by the agent, 669 with ifIndex=y, to represent the ATM Logical Port 670 interface. The object atmVplLogicalPortIndex is also 671 set to y by the agent to represent the ifIndex value of 672 the ATM Logical Port interface. 674 - The ifEntry values are set for the ATM Logical 675 Port interface (ifIndex=y) as discussed in RFC 676 1695, with the following exceptions: 677 * ifType - a new enumerated value of atmLogical(80) 678 was added to IANAifType, specifying an "ATM 679 Logical Port" interface. 680 * ifSpeed - The total bandwidth in bits per 681 second for use by the ATM layer. Computed 682 from the traffic descriptor for the VPL. 683 * ifOperStatus - determined hierarchically, 684 depending on the state of the physical 685 atm-cell layer interface beneath it, 687 draft Supplemental ATM Management Objects Mar 13, 1998 689 and the ILMI on the VP. 690 * ifInOctets, ifOutOctets - support of 691 these objects is not mandatory for ATM 692 Logical Port interfaces. 693 * ifInErrors - always zero, HEC errors are 694 specified for the atm cell-layer interface 695 beneath it. 696 * ifInUnknownProtos - always zero, errors 697 are specified for the atm cell-layer 698 interface beneath it. 700 - The atmInterfaceConfEntry values are set and reported 701 as discussed in [1], with the following exceptions: 702 * atmInterfaceMaxVpcs - 0. 703 * atmInterfaceConfVpcs - 0. 704 * atmInterfaceIlmiVpi - VPI of the VP tunnel. 706 - The atmInterfaceExtEntry values are set and reported 707 as follows: 708 * atmInterfaceConfMaxSvpcVpi - VPI of the VP tunnel, 709 although VPCs cannot be setup on a VP tunnel. 710 * atmInterfaceCurrentMaxSvpcVpi - VPI of VP tunnel, 711 although VPCs cannot be setup on a VP tunnel. 712 * atmInterfaceConfMaxSvccVpi - VPI of the VP tunnel. 713 * atmInterfaceCurrentMaxSvccVpi - VPI of VP tunnel. 714 * atmIntfPvcFailures - Includes failures of PVCLs 715 within the VP tunnel, but not of the PVPL itself, 716 since those are reported on the atm(37) interface. 717 * atmIntfCurrentlyFailingPVpls - 0. 718 * atmIntfPvcFailuresTrapEnable - Enables traps for 719 PVCL failures within the VP tunnel, but not for 720 the PVPL itself, since the latter are generated on 721 behalf of the atm(37) interface. 723 - An entry is created in the ifStackTable, with 724 values: ifStackHigherLayer=y, ifStackLowerLayer=x. 726 - VCLs defined on the VP tunnel are indexed by 727 ifIndex=y, VPI=a, VCI. 729 draft Supplemental ATM Management Objects Mar 13, 1998 731 6.3.11. ATM VCL Statistics Table 733 The atmVclStatTable includes per VCL cell counters. The VCL 734 cell counters count the valid ATM cells. The valid ATM cells 735 include the user and OAM cells but exclude the physical layer 736 (e.g., idle cells) and unassigned cells. Cells coming into an 737 ATM managed system are counted differently with the high Cell 738 Loss Priority (CLP=0) or low Cell Loss Priority (CLP=1). The 739 cells are tagged, passed or discarded depending on the 740 incoming CLP value and the policed cell rate by the "traffic 741 policing" entity in the ATM managed system. Refer to [9] and 742 [10] for the description of the traffic policing. 744 In the switch where the traffic policing is not supported, 745 cells are passed or discarded depending on the bandwidth of 746 the switching fabric. The Output Tagged Cells counter, in 747 this case, is always zero. 749 _______________ 750 | ATM Managed | 751 Input | System | Output 752 CLP=0 cells| | CLP=0 cells 753 ---------->| |-----------> 754 CLP=1 cells| (traffic | CLP=1 cells 755 ---------->| policing |-----------> 756 | entity) | Tagged cells (CLP=1) 757 |_____________|-----------> 758 |Discard | Discard 759 |CLP=0 | CLP=1 760 |cells | cells 761 | | 762 V V 764 Figure 7: ATM Cell Counters per VCL 766 In this table, cells coming into and out of the managed ATM 767 system are counted as the total number of cells and the cells 768 with the CLP=0. The CLP=1 counter is derived by subtracting 769 CLP=0 cells from the total cells. In addition, cells that are 770 tagged on the output are also counted. The output CLP=1 cells 771 equals to the total cells out count minus both the CLP=0 cells 772 and the tagged cells. 774 draft Supplemental ATM Management Objects Mar 13, 1998 776 6.3.12. ATM VC General Information Table 778 This table contains the general information for each VC. It 779 provides an index to the atmSigDescrParamTable defined in this 780 MIB. This table is an extension to the atmVclTable defined in 781 the ATM-MIB [1]. 783 6.3.13. ATM Interface Configuration Extension Table 785 The ATM Interface Configuration Extension Table contains ATM 786 interface information that supplements the 787 atmInterfaceConfTable defined in [1]. It includes the 788 configuration information of the interface type (i.e., 789 connection setup procedures) and ILMI. 791 A network manager can configure the interface to run a 792 specific type of connection setup procedures (i.e., protocol 793 and version) such as ITU-T DSS2, ATM Forum UNI 3.1, PNNI 1.0 794 or BICI 2.0. It can also dictate the role of the managed 795 entity as one side of the interface. For example, if an 796 interface is configured to run ATM Forum UNI 3.1, the managed 797 entity has to be told to run as either the network side or the 798 user side of the UNI. 800 The objects atmIntfConfigType and atmIntfConfigSide are used 801 for configuration and the objects atmIntfActualType and 802 atmIntfActualSide are used for reading back the actual 803 interface protocol and version. 805 The following table describes all the valid combinations of 806 configuration of the interface type and side: 808 atmIntfConfigType atmIntfConfigSide 809 ----------------- ----------------- 810 autoConfig N/A 811 ituDss2 user/network 812 atmfUni3Dot0 user/network 813 atmfUni3Dot1 user/network 814 atmfUni4Dot0 user/network 815 atmfIispUni3Dot0 user/network 816 atmfIispUni3Dot1 user/network 817 atmfIispUni4Dot0 user/network 818 atmfPnni1Dot0 N/A 819 atmfBici2Dot0 N/A 821 draft Supplemental ATM Management Objects Mar 13, 1998 823 When the value of the object atmIntfConfigType is configured 824 to autoConfig(2), the interface type is determined via the ATM 825 Forum ILMI auto-configuration procedures [21]. There is no 826 need to set the interface side since it should be a derived 827 value. The PNNI and BICI interfaces are always symmetric so 828 setting the interface side is also not necessary. 830 This table also includes the configured and negotiated maximum 831 VPI value per ATM interface, and the configured and negotiated 832 minimum VCI value per ATM interface. Refer to [21] Sections 833 8.2.3.8 through 8.2.3.10 for a detailed description. 835 The following figure provides an example how the current 836 minimum VCI values are derived from the configured minimum VCI 837 values and the neighboring minimum VCI values: 839 +--------+ +--------+ +--------+ 840 | ATM | IF a IF b | ATM | IF c IF d | ATM | 841 | Device |--------------| Device |--------------| Device | 842 +--------+ +--------+ +--------+ 844 IF a: Configured Min SVCC VCI = 32 (configured) 845 Current Min SVCC VCI = 40 (negotiated) 847 IF b: Configured Min SVCC VCI = 40 (configured) 848 Current Min SVCC VCI = 40 (negotiated) 850 IF c: Configured Min SVCC VCI = 32 (configured) 851 Current Min SVCC VCI = 32 (negotiated) 853 IF d: Configured Min SVCC VCI = 32 (configured) 854 Current Min SVCC VCI = 32 (negotiated) 856 (between IF a and IF b, the maximum of the two 857 atmInterfaceConfMinSvccVci is 40, so both interfaces set 858 their atmInterfaceCurrentMinSvccVci to 40. Since IF c 859 and IF d both are configured with 860 atmInterfaceConfMinSvccVci of 32, they set their 861 atmInterfaceCurrentMinSvccVci to 32.) 863 Figure 8: Examples of configured vs. negotiated ILMI values 865 draft Supplemental ATM Management Objects Mar 13, 1998 867 6.3.14. ATM ILMI Service Registry Table 869 This table contains information used by the switch/service to 870 inform ATM hosts of the location of ATM network services such 871 as the LAN Emulation Configuration Server (LECS) and the ATM 872 Name Server (ANS). Entries in this table are exported to 873 adjacent devices via ILMI over either all or a few user 874 selected ATM interfaces. 876 As an example, let's assume that: 878 - an ATM switch X has three interfaces if1, if2 and if3. 879 - there are two ATM network services offered: a1.a2...aN and 880 b1.b2...bN, 881 (where a1.a2...aN is an object identifier used to identify 882 the first service, and b1.b2...bN is the object identifier 883 for the other service. These services may be ATMARP 884 servers, LECS server, ...) 885 - The first service is available at the ATM address 'a'. 886 - The second service is available at the ATM address 'b'. 887 - The first service can be used by any device connecting to 888 the switch X. 889 - The second service can be used only by devices that connect 890 to interfaces if1 and if3 on switch X. 892 +------------------+ +------------------+ 893 |service a1.a2...aN| |service b1.b2...bN| 894 | | | | 895 | ATM address = a | | ATM address = b | 896 +--------+---------+ +--------+---------+ 897 I I 898 +--------+-----------------------+---------+ 899 | ATM NETWORK | 900 +-----------------+------------------------+ 901 I 902 +-------------+ 903 | switch X | 904 +-+----+----+-+ 905 I I I 907 if1 if2 if3 (interfaces) 909 Figure 9: ATM topology with registered services 911 draft Supplemental ATM Management Objects Mar 13, 1998 913 The table for switch X will contain three entries: 915 - one entry for the "a1.a2...aN", implicitly available to any 916 devices on switch X. 917 - two entries for the "b1.b2...bN" (one for each interface 918 where this service can be explicitly used). 920 The content of the table is: 922 - Service Identifier: a1.a2...aN b1.b2...bN b1.b2...bN 923 - ATM address: a b b 924 - Arbitrary index: m n p 925 - Interface: 0 1 3 927 where m, n and p are arbitrary parameters. 929 When querying the ILMI service registry table, through the 930 ILMI protocol: 932 - the device attached to interface if1 will obtain the 933 address a and b 934 - the device attached to interface if2 will obtain the 935 address a only 936 - the device attached to interface if3 will obtain the 937 address a and b 939 6.3.15. ILMI Network Prefix Table 941 A table specifying per interface network prefix(es) supplied 942 by the network side of the UNI during ILMI address 943 registration. When no network prefixes are specified for a 944 particular interface, one or more network prefixes based on 945 the switch address(es) may be used for ILMI address 946 registration. 948 6.3.16. ATM Switch Address Table 950 This table contains one or more ATM endsystem addresses on a 951 per switch basis. These addresses are used to identify the 952 switch. When no ILMI network prefixes are configured for 953 certain interfaces, network prefixes based on the switch 954 address(es) may be used for ILMI address registration. 956 draft Supplemental ATM Management Objects Mar 13, 1998 958 7. Network and User Addresses 960 At the user side of a given ATM UNI interface there may be an 961 address, "ifPhysAddress", to identify the interface. In 962 addition, there may be several other addresses which can be 963 used to originate and receive calls. These other addresses 964 that are used to receive calls are listed in the 965 "ifRcvAddrTable" defined in RFC 2233 [6]. The registered 966 addresses on the network side are listed in the ATM Registered 967 Address Table. The ATM Registered Address Table is supported 968 by switches and network services. It is not supported by 969 hosts. 971 8. Configuration of VPLs, VCLs, and Cross-Connects 973 The ATM Managed Objects needed to support the configuration of 974 VPLs, VCLs, and Cross-Connects of the Permanent VPLs and VCLs 975 are defined in the ATM-MIB [1]. Cross-Connects of the 976 Switched VPLs and VCLs are defined in this memo. 978 9. ATM Related Trap Support 980 Traps are defined to detect changes in the status of permanent 981 VPLs and VCLs. The current up/down status of each permanent 982 VPL or VCL is indicated by the atmVplOperStatus or 983 atmVclOperStatus object, respectively. Several tables and 984 objects and one trap are defined in order to help network 985 managers quickly and efficiently detect changes in the status 986 of permanent virtual links. Through use of these tables, 987 objects, and traps, the time consuming and resource intensive 988 task of continuously polling each row in the entire 989 atmVplTable and atmVclTable can be avoided. 991 The atmIntfPvcFailures counter and the 992 atmIntfCurrentlyFailingPVpls and atmIntfCurrentlyFailingPVcls 993 gauges provide a quick means of determining the status of all 994 PVPLs and PVCLs on an interface. The 995 atmCurrentlyFailingPVplTable and the 996 atmCurrentlyFailingPVclTable list all of the problematic PVPLs 997 and PVCLs, respectively, allowing them to be quickly 998 identified. 1000 draft Supplemental ATM Management Objects Mar 13, 1998 1002 The atmIntfPvcFailuresTrap is generated just after a PVPL or 1003 PVCL on a particular interface leaves the `up' operational 1004 state. Managers can then determine which PVPLs and/or PVCLs 1005 are failing by reading the atmCurrentlyFailingPVplTable and 1006 the atmCurrentlyFailingPVclTable. Generation of the 1007 atmIntfPvcFailuresTrap is rate limited by suppressing all 1008 traps that would occur within atmIntfPvcNotificationInterval 1009 of a previous trap for the same interface. Managers should 1010 continuously poll the tables and objects mentioned above for 1011 at least this amount of time in order to keep up with the 1012 state of the network. 1014 draft Supplemental ATM Management Objects Mar 13, 1998 1016 10. Definitions 1018 ATM2-MIB DEFINITIONS ::= BEGIN 1020 IMPORTS 1021 MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, 1022 BITS, Gauge32, experimental, Counter32, Integer32 1023 FROM SNMPv2-SMI 1024 TruthValue, RowStatus, TimeStamp, DisplayString 1025 FROM SNMPv2-TC 1026 MODULE-COMPLIANCE, OBJECT-GROUP 1027 FROM SNMPv2-CONF 1028 InterfaceIndex, InterfaceIndexOrZero, ifIndex 1029 FROM IF-MIB 1030 atmMIBObjects, atmInterfaceConfEntry, 1031 atmVplEntry, atmVplVpi, 1032 atmVclEntry, atmVclVpi, atmVclVci, 1033 atmVpCrossConnectEntry, atmVcCrossConnectEntry 1034 FROM ATM-MIB 1035 AtmAddr, AtmSigDescrParamIndex, 1036 AtmInterfaceType, AtmIlmiNetworkPrefix, 1037 AtmVcIdentifier, AtmVpIdentifier, 1038 AtmTrafficDescrParamIndex 1039 FROM ATM-TC-MIB; 1041 atm2MIB MODULE-IDENTITY 1042 LAST-UPDATED "9803131200Z" 1043 ORGANIZATION "IETF AToMMIB Working Group" 1044 CONTACT-INFO 1045 " Faye Ly 1046 Postal: 3Com Networks Inc. 1047 Santa Clara, CA 95052 1048 US 1049 Tel: +1 408 764 6576 1050 Fax: +1 408 495 2599 1051 E-Mail: faye@3com.com 1053 Michael Noto 1054 Postal: Network Equipment Technologies 1055 800 Saginaw Drive RM 21.1.111 1056 Redwood City, CA 94063 1057 US 1058 Tel: +1 415 569 7143 1060 draft Supplemental ATM Management Objects Mar 13, 1998 1062 Fax: +1 732 758 4177 1063 E-mail: mike_noto@net.com 1065 Andrew Smith 1066 Postal: Extreme Networks 1067 1601 S. De Anza Blvd, #220 1068 Cupertino, CA 95014 1069 US 1070 Tel: +1 408 342 0985 1071 Fax: +1 408 342 0989 1072 E-Mail: ansmith@ix.netcom.com 1074 Ethan Mickey Spiegel 1075 Postal: Cisco Systems 1076 170 W. Tasman Drive 1077 San Jose, CA 95134-1706 1078 Tel: +1 408 526 6408 1079 Fax: +1 408 526 6488 1080 E-Mail: mspiegel@cisco.com 1082 Kaj Tesink 1083 Postal: Bell Communications Research 1084 331 Newman Springs Road 1085 Red Bank, NJ 07701 1086 US 1087 Tel: +1 732 758 5254 1088 Fax: +1 732 758 4177 1089 E-mail: kaj@cc.bellcore.com" 1090 DESCRIPTION 1091 "This MIB Module is a supplement to the 1092 ATM-MIB [1]." 1093 ::= { experimental XX } 1095 atm2MIBObjects OBJECT IDENTIFIER ::= {atm2MIB 1} 1096 atm2MIBTraps OBJECT IDENTIFIER ::= {atm2MIB 2} 1098 -- ******** NOTE TO THE RFC EDITOR ************** 1099 -- In case this module is put on the standards track 1100 -- replace the following: 1101 -- "atm2MIB MODULE-IDENTITY ::= {experimental XX}" with 1102 -- "atm2MIB MODULE-IDENTITY ::= {atmMIBObjects 14}" 1103 -- and include atmMIBObjects in the IMPORT clause. 1105 draft Supplemental ATM Management Objects Mar 13, 1998 1107 -- This ATM2-MIB Module consists of the following tables, 1108 -- plus ATM trap support: 1109 -- 1. atmSvcVpCrossConnectTable 1110 -- 2. atmSvcVcCrossConnectTable 1111 -- 3. atmSigStatTable 1112 -- 4. atmSigSupportTable 1113 -- 5. atmSigDescrParamTable 1114 -- 6. atmIfRegisteredAddrTable 1115 -- 7. atmVclAddrTable 1116 -- 8. atmAddrVclTable 1117 -- 9. atmVplStatTable 1118 -- 10. atmVplLogicalPortTable 1119 -- 11. atmVclStatTable 1120 -- 12. atmAal5VclStatTable 1121 -- 13. atmVclGenTable 1122 -- 14. atmInterfaceExtTable 1123 -- 15. atmIlmiSrvcRegTable 1124 -- 16. atmIlmiNetworkPrefixTable 1125 -- 17. atmSwitchAddressTable 1126 -- 18. atmVpCrossConnectXTable 1127 -- 19. atmVcCrossConnectXTable 1128 -- 20. atmCurrentlyFailingPVplTable 1129 -- 21. atmCurrentlyFailingPVclTable 1131 draft Supplemental ATM Management Objects Mar 13, 1998 1133 -- 1. ATM VPL SVC Cross-Connect Table 1135 atmSvcVpCrossConnectTable OBJECT-TYPE 1136 SYNTAX SEQUENCE OF 1137 AtmSvcVpCrossConnectEntry 1138 MAX-ACCESS not-accessible 1139 STATUS current 1140 DESCRIPTION 1141 "The ATM SVPC Cross-Connect table. A 1142 bi-directional VP cross-connect between two 1143 switched VPLs is modeled as one entry in this 1144 table. A Soft PVPC cross-connect, between a 1145 soft permanent VPL and a switched VPL, is 1146 also modeled as one entry in this table." 1147 ::= { atm2MIBObjects 1 } 1149 atmSvcVpCrossConnectEntry OBJECT-TYPE 1150 SYNTAX AtmSvcVpCrossConnectEntry 1151 MAX-ACCESS not-accessible 1152 STATUS current 1153 DESCRIPTION 1154 "An entry in the ATM SVPC Cross-Connect table. 1155 This entry is used to model a bi-directional 1156 ATM VP cross-connect between two VPLs." 1157 INDEX { atmSvcVpCrossConnectIndex, 1158 atmSvcVpCrossConnectLowIfIndex, 1159 atmSvcVpCrossConnectLowVpi, 1160 atmSvcVpCrossConnectHighIfIndex, 1161 atmSvcVpCrossConnectHighVpi } 1162 ::= { atmSvcVpCrossConnectTable 1 } 1164 AtmSvcVpCrossConnectEntry ::= SEQUENCE { 1165 atmSvcVpCrossConnectIndex INTEGER, 1166 atmSvcVpCrossConnectLowIfIndex InterfaceIndex, 1167 atmSvcVpCrossConnectLowVpi AtmVpIdentifier, 1168 atmSvcVpCrossConnectHighIfIndex InterfaceIndex, 1169 atmSvcVpCrossConnectHighVpi AtmVpIdentifier, 1170 atmSvcVpCrossConnectCreationTime TimeStamp, 1171 atmSvcVpCrossConnectRowStatus RowStatus 1172 } 1174 atmSvcVpCrossConnectIndex OBJECT-TYPE 1176 draft Supplemental ATM Management Objects Mar 13, 1998 1178 SYNTAX INTEGER (1..2147483647) 1179 MAX-ACCESS not-accessible 1180 STATUS current 1181 DESCRIPTION 1182 "A unique value to identify this SVPC 1183 cross-connect." 1184 ::= { atmSvcVpCrossConnectEntry 1 } 1186 atmSvcVpCrossConnectLowIfIndex OBJECT-TYPE 1187 SYNTAX InterfaceIndex 1188 MAX-ACCESS not-accessible 1189 STATUS current 1190 DESCRIPTION 1191 "The value of this object is equal to MIB II's 1192 ifIndex value of the ATM interface port for this 1193 SVPC cross-connect. The term low implies 1194 that this ATM interface has the numerically lower 1195 ifIndex value than the other ATM interface 1196 identified in the same atmSvcVpCrossConnectEntry." 1197 ::= { atmSvcVpCrossConnectEntry 2 } 1199 atmSvcVpCrossConnectLowVpi OBJECT-TYPE 1200 SYNTAX AtmVpIdentifier 1201 MAX-ACCESS not-accessible 1202 STATUS current 1203 DESCRIPTION 1204 "The value of this object is equal to the VPI 1205 value associated with the SVPC cross-connect 1206 at the ATM interface that is identified by 1207 atmSvcVpCrossConnectLowIfIndex. The VPI value 1208 cannot exceed the number supported by the 1209 atmInterfaceMaxVpiBits at the low ATM interface 1210 port." 1211 ::= { atmSvcVpCrossConnectEntry 3 } 1213 atmSvcVpCrossConnectHighIfIndex OBJECT-TYPE 1214 SYNTAX InterfaceIndex 1215 MAX-ACCESS not-accessible 1216 STATUS current 1217 DESCRIPTION 1218 "The value of this object is equal to MIB II's 1219 ifIndex value of the ATM interface port for 1220 this SVC VP cross-connect. The term high 1221 implies that this ATM interface has the 1223 draft Supplemental ATM Management Objects Mar 13, 1998 1225 numerically higher ifIndex value than the 1226 other ATM interface identified in the same 1227 atmSvcVpCrossConnectEntry." 1228 ::= { atmSvcVpCrossConnectEntry 4 } 1230 atmSvcVpCrossConnectHighVpi OBJECT-TYPE 1231 SYNTAX AtmVpIdentifier 1232 MAX-ACCESS not-accessible 1233 STATUS current 1234 DESCRIPTION 1235 "The value of this object is equal to the VPI 1236 value associated with the SVPC cross-connect 1237 at the ATM interface that is identified by 1238 atmSvcVpCrossConnectHighIfIndex. The VPI value 1239 cannot exceed the number supported by the 1240 atmInterfaceMaxVpiBits at the high ATM interface 1241 port." 1242 ::= { atmSvcVpCrossConnectEntry 5 } 1244 atmSvcVpCrossConnectCreationTime OBJECT-TYPE 1245 SYNTAX TimeStamp 1246 MAX-ACCESS read-only 1247 STATUS current 1248 DESCRIPTION 1249 "The value of MIB II's sysUpTime object 1250 at the time this bi-directional SVPC 1251 cross-connect was created. If the current 1252 state was entered prior to the last 1253 re-initialization of the agent, then this 1254 object contains a zero value." 1255 ::= { atmSvcVpCrossConnectEntry 6 } 1257 atmSvcVpCrossConnectRowStatus OBJECT-TYPE 1258 SYNTAX RowStatus 1259 MAX-ACCESS read-write 1260 STATUS current 1261 DESCRIPTION 1262 "This object is used to delete rows in the 1263 atmSvcVpCrossConnectTable." 1264 ::= { atmSvcVpCrossConnectEntry 7 } 1266 -- 2. ATM VCL SVC Cross-Connect Table 1268 draft Supplemental ATM Management Objects Mar 13, 1998 1270 atmSvcVcCrossConnectTable OBJECT-TYPE 1271 SYNTAX SEQUENCE OF AtmSvcVcCrossConnectEntry 1272 MAX-ACCESS not-accessible 1273 STATUS current 1274 DESCRIPTION 1275 "The ATM SVCC Cross-Connect table. A 1276 bi-directional VC cross-connect between two 1277 switched VCLs is modeled as one entry in 1278 this table. A Soft PVCC cross-connect, 1279 between a soft permanent VCL and a switched 1280 VCL, is also modeled as one entry in this 1281 table." 1282 ::= { atm2MIBObjects 2 } 1284 atmSvcVcCrossConnectEntry OBJECT-TYPE 1285 SYNTAX AtmSvcVcCrossConnectEntry 1286 MAX-ACCESS not-accessible 1287 STATUS current 1288 DESCRIPTION 1289 "An entry in the ATM SVCC Cross-Connect table. 1290 This entry is used to model a bi-directional ATM 1291 VC cross-connect between two VCLs." 1292 INDEX { atmSvcVcCrossConnectIndex, 1293 atmSvcVcCrossConnectLowIfIndex, 1294 atmSvcVcCrossConnectLowVpi, 1295 atmSvcVcCrossConnectLowVci, 1296 atmSvcVcCrossConnectHighIfIndex, 1297 atmSvcVcCrossConnectHighVpi, 1298 atmSvcVcCrossConnectHighVci } 1299 ::= { atmSvcVcCrossConnectTable 1 } 1301 AtmSvcVcCrossConnectEntry ::= SEQUENCE { 1302 atmSvcVcCrossConnectIndex INTEGER, 1303 atmSvcVcCrossConnectLowIfIndex InterfaceIndex, 1304 atmSvcVcCrossConnectLowVpi AtmVpIdentifier, 1305 atmSvcVcCrossConnectLowVci AtmVcIdentifier, 1306 atmSvcVcCrossConnectHighIfIndex InterfaceIndex, 1307 atmSvcVcCrossConnectHighVpi AtmVpIdentifier, 1308 atmSvcVcCrossConnectHighVci AtmVcIdentifier, 1309 atmSvcVcCrossConnectCreationTime TimeStamp, 1310 atmSvcVcCrossConnectRowStatus RowStatus 1311 } 1313 draft Supplemental ATM Management Objects Mar 13, 1998 1315 atmSvcVcCrossConnectIndex OBJECT-TYPE 1316 SYNTAX INTEGER (1..2147483647) 1317 MAX-ACCESS not-accessible 1318 STATUS current 1319 DESCRIPTION 1320 "A unique value to identify this SVCC cross-connect." 1321 ::= { atmSvcVcCrossConnectEntry 1 } 1323 atmSvcVcCrossConnectLowIfIndex OBJECT-TYPE 1324 SYNTAX InterfaceIndex 1325 MAX-ACCESS not-accessible 1326 STATUS current 1327 DESCRIPTION 1328 "The value of this object is equal to MIB II's 1329 ifIndex value of the ATM interface port for this 1330 SVCC cross-connect. The term low implies that 1331 this ATM interface has the numerically lower 1332 ifIndex value than the other ATM interface 1333 identified in the same atmSvcVcCrossConnectEntry." 1334 ::= { atmSvcVcCrossConnectEntry 2 } 1336 atmSvcVcCrossConnectLowVpi OBJECT-TYPE 1337 SYNTAX AtmVpIdentifier 1338 MAX-ACCESS not-accessible 1339 STATUS current 1340 DESCRIPTION 1341 "The value of this object is equal to the VPI 1342 value associated with the SVCC cross-connect 1343 at the ATM interface that is identified by 1344 atmSvcVcCrossConnectLowIfIndex. The VPI value 1345 cannot exceed the number supported by the 1346 atmInterfaceMaxVpiBits at the low ATM interface 1347 port." 1348 ::= { atmSvcVcCrossConnectEntry 3 } 1350 atmSvcVcCrossConnectLowVci OBJECT-TYPE 1351 SYNTAX AtmVcIdentifier 1352 MAX-ACCESS not-accessible 1353 STATUS current 1354 DESCRIPTION 1355 "The value of this object is equal to the VCI 1356 value associated with the SVCC cross-connect 1357 at the ATM interface that is identified by 1358 atmSvcVcCrossConnectLowIfIndex. The VCI value 1360 draft Supplemental ATM Management Objects Mar 13, 1998 1362 cannot exceed the number supported by the 1363 atmInterfaceMaxVciBits at the low ATM interface 1364 port." 1365 ::= { atmSvcVcCrossConnectEntry 4 } 1367 atmSvcVcCrossConnectHighIfIndex OBJECT-TYPE 1368 SYNTAX InterfaceIndex 1369 MAX-ACCESS not-accessible 1370 STATUS current 1371 DESCRIPTION 1372 "The value of this object is equal to MIB II's 1373 ifIndex value for the ATM interface port for 1374 this SVCC cross-connect. The term high implies 1375 that this ATM interface has the numerically 1376 higher ifIndex value than the other ATM interface 1377 identified in the same atmSvcVcCrossConnectEntry." 1378 ::= { atmSvcVcCrossConnectEntry 5 } 1380 atmSvcVcCrossConnectHighVpi OBJECT-TYPE 1381 SYNTAX AtmVpIdentifier 1382 MAX-ACCESS not-accessible 1383 STATUS current 1384 DESCRIPTION 1385 "The value of this object is equal to the VPI 1386 value associated with the SVCC cross-connect 1387 at the ATM interface that is identified by 1388 atmSvcVcCrossConnectHighIfIndex. The VPI value 1389 cannot exceed the number supported by the 1390 atmInterfaceMaxVpiBits at the high ATM interface 1391 port." 1392 ::= { atmSvcVcCrossConnectEntry 6 } 1394 atmSvcVcCrossConnectHighVci OBJECT-TYPE 1395 SYNTAX AtmVcIdentifier 1396 MAX-ACCESS not-accessible 1397 STATUS current 1398 DESCRIPTION 1399 "The value of this object is equal to the VCI 1400 value associated with the SVCC cross-connect 1401 at the ATM interface that is identified by 1402 atmSvcVcCrossConnectHighIfIndex. The VCI value 1403 cannot exceed the number supported by the 1404 atmInterfaceMaxVciBits at the high ATM interface 1405 port." 1407 draft Supplemental ATM Management Objects Mar 13, 1998 1409 ::= { atmSvcVcCrossConnectEntry 7 } 1411 atmSvcVcCrossConnectCreationTime OBJECT-TYPE 1412 SYNTAX TimeStamp 1413 MAX-ACCESS read-only 1414 STATUS current 1415 DESCRIPTION 1416 "The value of MIB II's sysUpTime object 1417 at the time this bi-directional SVCC 1418 cross-connect was created. If the current 1419 state was entered prior to the last 1420 re-initialization of the agent, then this 1421 object contains a zero value." 1422 ::= { atmSvcVcCrossConnectEntry 8 } 1424 atmSvcVcCrossConnectRowStatus OBJECT-TYPE 1425 SYNTAX RowStatus 1426 MAX-ACCESS read-write 1427 STATUS current 1428 DESCRIPTION 1429 "This object is used to delete rows in the 1430 atmSvcVcCrossConnectTable." 1431 ::= { atmSvcVcCrossConnectEntry 9 } 1433 -- 1434 -- 3. ATM Interface Signalling Statistics Table 1435 -- 1437 atmSigStatTable OBJECT-TYPE 1438 SYNTAX SEQUENCE OF AtmSigStatEntry 1439 MAX-ACCESS not-accessible 1440 STATUS current 1441 DESCRIPTION 1442 "This table contains ATM interface signalling 1443 statistics, one entry per ATM signalling 1444 interface." 1445 ::= { atm2MIBObjects 3 } 1447 atmSigStatEntry OBJECT-TYPE 1448 SYNTAX AtmSigStatEntry 1449 MAX-ACCESS not-accessible 1450 STATUS current 1451 DESCRIPTION 1452 "This list contains signalling statistics variables." 1454 draft Supplemental ATM Management Objects Mar 13, 1998 1456 INDEX { ifIndex } 1457 ::= { atmSigStatTable 1} 1459 AtmSigStatEntry ::= SEQUENCE { 1460 atmSigSSCOPConEvents Counter32, 1461 atmSigSSCOPErrdPdus Counter32, 1462 atmSigDetectSetupAttempts Counter32, 1463 atmSigEmitSetupAttempts Counter32, 1464 atmSigDetectUnavailRoutes Counter32, 1465 atmSigEmitUnavailRoutes Counter32, 1466 atmSigDetectUnavailResrcs Counter32, 1467 atmSigEmitUnavailResrcs Counter32, 1468 atmSigDetectCldPtyEvents Counter32, 1469 atmSigEmitCldPtyEvents Counter32, 1470 atmSigDetectMsgErrors Counter32, 1471 atmSigEmitMsgErrors Counter32, 1472 atmSigDetectClgPtyEvents Counter32, 1473 atmSigEmitClgPtyEvents Counter32, 1474 atmSigDetectTimerExpireds Counter32, 1475 atmSigEmitTimerExpireds Counter32, 1476 atmSigDetectRestarts Counter32, 1477 atmSigEmitRestarts Counter32, 1478 atmSigInEstabls Counter32, 1479 atmSigOutEstabls Counter32 1480 } 1482 atmSigSSCOPConEvents OBJECT-TYPE 1483 SYNTAX Counter32 1484 MAX-ACCESS read-only 1485 STATUS current 1486 DESCRIPTION 1487 "SSCOP Connection Events Counter. This 1488 counter counts the sum of the following errors: 1490 1) SSCOP Connection Disconnect Counter 1492 The abnormal occurrence of this event is 1493 characterized by the expiry of Timer_NO_RESPONSE. 1494 (This event is communicated to the layer management 1495 with MAA-ERROR code P. See ITU-T Q.2110 [13].) 1497 2) SSCOP Connection Initiation Failure 1499 This condition indicates the inability to establish 1501 draft Supplemental ATM Management Objects Mar 13, 1998 1503 an SSCOP connection. This event occurs whenever the 1504 number of expiries of the connection control timer 1505 (Timer_CC) exceeds the MaxCC or upon receipt of a 1506 connection reject message BGREJ PDU. (This event is 1507 communicated to layer management with MAA-ERROR 1508 code O. See ITU-T Q.2110.) 1510 3) SSCOP Connection Re-Establ/Resynch 1512 This event occurs upon receipt of a BGN PDU or 1513 RESYNC PDU." 1514 ::= { atmSigStatEntry 1} 1516 atmSigSSCOPErrdPdus OBJECT-TYPE 1517 SYNTAX Counter32 1518 MAX-ACCESS read-only 1519 STATUS current 1520 DESCRIPTION 1521 "SSCOP Errored PDUs Counter. This counter counts the 1522 sum of the following errors: 1524 1) Invalid PDUs. 1525 These are defined in SSCOP and consist of PDUs 1526 with incorrect length (MAA-ERROR code U), 1527 undefined PDU type code or not 32-bit aligned. 1529 2) PDUs that result in MAA error codes and are 1530 discarded. 1532 See Errors A-M and Q-T defined in ITU-T Q.2110 [13]." 1533 ::= { atmSigStatEntry 2 } 1535 atmSigDetectSetupAttempts OBJECT-TYPE 1536 SYNTAX Counter32 1537 MAX-ACCESS read-only 1538 STATUS current 1539 DESCRIPTION 1540 "Call Setup Attempts Counter. This counter counts 1541 the number of call setup attempts (both successful 1542 and unsuccessful) detected on this interface." 1543 ::= { atmSigStatEntry 3 } 1545 atmSigEmitSetupAttempts OBJECT-TYPE 1546 SYNTAX Counter32 1548 draft Supplemental ATM Management Objects Mar 13, 1998 1550 MAX-ACCESS read-only 1551 STATUS current 1552 DESCRIPTION 1553 "Call Setup Attempts Counter. This counter counts the 1554 number of call setup attempts (both successful and 1555 unsuccessful) transmitted on this interface." 1556 ::= { atmSigStatEntry 4 } 1558 atmSigDetectUnavailRoutes OBJECT-TYPE 1559 SYNTAX Counter32 1560 MAX-ACCESS read-only 1561 STATUS current 1562 DESCRIPTION 1563 "Number of Route Unavailability detected on this 1564 interface. This counter is incremented when a RELEASE, 1565 RELEASE COMPLETE (only when not preceded by a RELEASE 1566 mesg for the same call), ADD PARTY REJECT, or STATUS 1567 message that contains one of the following cause code 1568 values is received (Note: These cause values apply to 1569 both UNI3.0 and UNI3.1): 1571 draft Supplemental ATM Management Objects Mar 13, 1998 1573 Cause Value Meaning 1575 1 unallocated (unassigned) number 1576 2 no route to specified transit network 1577 3 no route to destination 1579 NOTE: For this counter, RELEASE COMPLETE 1580 messages that are a reply to a previous RELEASE 1581 message and contain the same cause value, are 1582 redundant (for counting purposes) and should not 1583 be counted." 1584 ::= { atmSigStatEntry 5 } 1586 atmSigEmitUnavailRoutes OBJECT-TYPE 1587 SYNTAX Counter32 1588 MAX-ACCESS read-only 1589 STATUS current 1590 DESCRIPTION 1591 "Number of Route Unavailability transmitted from this 1592 interface. This counter is incremented when a RELEASE, 1593 RELEASE COMPLETE (only when not preceded by a RELEASE 1594 mesg for the same call), ADD PARTY REJECT, or STATUS 1595 message that contains one of the following cause code 1596 values is transmitted (Note: These cause values apply 1597 to both UNI3.0 and UNI3.1): 1599 draft Supplemental ATM Management Objects Mar 13, 1998 1601 Cause Value Meaning 1603 1 unallocated (unassigned) number 1604 2 no route to specified transit network 1605 3 no route to destination 1607 NOTE: For this counter, RELEASE COMPLETE 1608 messages that are a reply to a previous RELEASE 1609 message and contain the same cause value, are 1610 redundant (for counting purposes) and should not 1611 be counted." 1612 ::= { atmSigStatEntry 6 } 1614 atmSigDetectUnavailResrcs OBJECT-TYPE 1615 SYNTAX Counter32 1616 MAX-ACCESS read-only 1617 STATUS current 1618 DESCRIPTION 1619 "Number of Resource Unavailability detected on this 1620 interface. This counter is incremented when a RELEASE, 1621 RELEASE COMPLETE (only when not preceded by a RELEASE 1622 mesg for the same call), ADD PARTY REJECT, or STATUS 1623 message that contains one of the following cause code 1624 values is received (Note: These cause values apply to 1625 both UNI3.0 and UNI3.1 unless otherwise stated): 1627 Cause Value Meaning 1629 35 requested VPCI/VCI not available 1630 37 user cell rate not available (UNI3.1 1631 only) 1632 38 network out of order 1633 41 temporary failure 1634 45 no VPCI/VCI available 1635 47 resource unavailable, unspecified 1636 49 Quality of Service unavailable 1637 51 user cell rate not available (UNI3.0 1638 only) 1639 58 bearer capability not presently 1640 available 1641 63 Service or option not available, 1642 unspecified 1643 92 too many pending add party requests 1645 draft Supplemental ATM Management Objects Mar 13, 1998 1647 NOTE: For this counter, RELEASE COMPLETE 1648 messages that are a reply to a previous RELEASE 1649 message and contain the same cause value, are 1650 redundant (for counting purposes) and should not 1651 be counted." 1653 ::= { atmSigStatEntry 7 } 1655 atmSigEmitUnavailResrcs OBJECT-TYPE 1656 SYNTAX Counter32 1657 MAX-ACCESS read-only 1658 STATUS current 1659 DESCRIPTION 1660 "Number of Resource Unavailability transmitted from 1661 this interface. This counter is incremented when a 1662 RELEASE, RELEASE COMPLETE (only when not preceded by a 1663 RELEASE mesg for the same call), ADD PARTY REJECT, or 1664 STATUS message that contains one of the following cause 1665 code values is transmitted (Note: These cause values 1666 apply to both UNI3.0 and UNI3.1 unless otherwise 1667 stated): 1669 Cause Value Meaning 1671 35 requested VPCI/VCI not available 1672 37 user cell rate not available (UNI3.1 1673 only) 1674 38 network out of order 1675 41 temporary failure 1676 45 no VPCI/VCI available 1677 47 resource unavailable, unspecified 1678 49 Quality of Service unavailable 1679 51 user cell rate not available (UNI3.0 1680 only) 1681 58 bearer capability not presently 1682 available 1683 63 Service or option not available, 1684 unspecified 1685 92 too many pending add party requests 1687 NOTE: For this counter, RELEASE COMPLETE 1688 messages that are a reply to a previous RELEASE 1689 message and contain the same cause value, are 1690 redundant (for counting purposes) and should not 1692 draft Supplemental ATM Management Objects Mar 13, 1998 1694 be counted." 1696 ::= { atmSigStatEntry 8 } 1698 atmSigDetectCldPtyEvents OBJECT-TYPE 1699 SYNTAX Counter32 1700 MAX-ACCESS read-only 1701 STATUS current 1702 DESCRIPTION 1703 "Number of Called Party Responsible For Unsuccessful 1704 Call detected on this interface. This counter is 1705 incremented when a RELEASE, RELEASE COMPLETE (only when 1706 not preceded by a RELEASE mesg for the same call), ADD 1707 PARTY REJECT, or STATUS message that contains one of 1708 the following cause code values is received (Note: 1709 These cause values apply to both UNI3.0 and UNI3.1): 1711 Cause Value Meaning 1713 17 user busy 1714 18 no user responding 1715 21 call rejected 1716 22 number changed 1717 23 user rejects all calls with calling 1718 line id restriction (CLIR) 1719 27 destination out of order 1720 31 normal, unspecified 1721 88 incompatible destination 1723 NOTE: For this counter, RELEASE COMPLETE 1724 messages that are a reply to a previous RELEASE 1725 message and contain the same cause value, are 1726 redundant (for counting purposes) and should not 1727 be counted. 1729 Note: Cause Value #30 'response to STATUS ENQUIRY' 1730 was not included in this memo since it did not apply 1731 to a hard failure." 1732 ::= { atmSigStatEntry 9 } 1734 atmSigEmitCldPtyEvents OBJECT-TYPE 1735 SYNTAX Counter32 1736 MAX-ACCESS read-only 1737 STATUS current 1739 draft Supplemental ATM Management Objects Mar 13, 1998 1741 DESCRIPTION 1742 "Number of Called Party Responsible For Unsuccessful 1743 Call transmitted from this interface. This counter is 1744 incremented when a RELEASE, RELEASE COMPLETE (only 1745 when not preceded by a RELEASE mesg for the same call), 1746 ADD PARTY REJECT, or STATUS message that contains one 1747 of the following cause code values is 1748 transmitted (Note: These cause values apply to both 1749 UNI3.0 and UNI3.1): 1751 Cause Value Meaning 1753 17 user busy 1754 18 no user responding 1755 21 call rejected 1756 22 number changed 1757 23 user rejects all calls with calling 1758 line id restriction (CLIR) 1759 27 destination out of order 1760 31 normal, unspecified 1761 88 incompatible destination 1763 NOTE: For this counter, RELEASE COMPLETE 1764 messages that are a reply to a previous RELEASE 1765 message and contain the same cause value, are 1766 redundant (for counting purposes) and should not 1767 be counted. 1769 Note: Cause Value #30 'response to STATUS ENQUIRY' 1770 was not included in this memo since it did not apply 1771 to a hard failure." 1772 ::= { atmSigStatEntry 10 } 1774 atmSigDetectMsgErrors OBJECT-TYPE 1775 SYNTAX Counter32 1776 MAX-ACCESS read-only 1777 STATUS current 1778 DESCRIPTION 1779 "Number of Incorrect Messages detected on this 1780 interface. The Incorrect Messages Counter reflects any 1781 sort of incorrect information in a message. This 1782 includes: 1784 - RELEASE, RELEASE COMPLETE, ADD PARTY REJECT, 1786 draft Supplemental ATM Management Objects Mar 13, 1998 1788 and STATUS messages transmitted, that contain any of 1789 the Cause values listed below. 1791 - Ignored messages. These messages are dropped 1792 because the message was so damaged that it could 1793 not be further processed. A list of dropped 1794 messages is compiled below: 1796 1. Message with invalid protocol discriminator 1798 2. Message with errors in the call reference I.E. 1799 - Bits 5-8 of the first octet not equal to 1800 '0000' 1801 - Bits 1-4 of the first octet indicating a 1802 length other than 3 octets 1803 - RELEASE COMPLETE message received with a 1804 call reference that does not relate to a 1805 call active or in progress 1806 - SETUP message received with call reference 1807 flag incorrectly set to 1 1808 - SETUP message received with a call 1809 reference for a call that is already 1810 active or in progress. 1812 3. Message too short 1814 The following cause values are monitored by this 1815 counter (Note: These cause values apply to both UNI3.0 1816 and UNI3.1 unless otherwise stated): 1818 Cause Value Meaning 1820 10 VPCI/VCI unacceptable (UNI3.0 only) 1821 36 VPCI/VCI assignment failure (UNI3.1 only) 1822 81 invalid call reference value 1823 82 identified channel does not exist 1824 89 invalid endpoint reference 1825 96 mandatory information element is missing 1826 97 message type non-existent or not 1827 implemented 1828 99 information element non-existent or not 1829 implemented 1830 100 invalid information element contents 1832 draft Supplemental ATM Management Objects Mar 13, 1998 1834 101 message not compatible with call state 1835 104 incorrect message length 1836 111 protocol error, unspecified 1838 NOTE: For this counter, RELEASE COMPLETE 1839 messages that are a reply to a previous RELEASE 1840 message and contain the same cause value, are 1841 redundant (for counting purposes) and should not 1842 be counted." 1843 ::= { atmSigStatEntry 11 } 1845 atmSigEmitMsgErrors OBJECT-TYPE 1846 SYNTAX Counter32 1847 MAX-ACCESS read-only 1848 STATUS current 1849 DESCRIPTION 1850 "Number of Incorrect Messages transmitted on this 1851 interface. The Incorrect Messages Counter reflects any 1852 sort of incorrect information in a message. This 1853 includes: 1855 - RELEASE, RELEASE COMPLETE, ADD PARTY REJECT, 1856 and STATUS messages transmitted or 1857 received, that contain any of the Cause values 1858 listed below. 1860 - Ignored messages. These messages are dropped 1861 because the message was so damaged that it could 1862 not be further processed. A list of dropped 1863 messages is compiled below: 1865 1. Message with invalid protocol discriminator 1867 2. Message with errors in the call reference I.E. 1868 - Bits 5-8 of the first octet not equal to 1869 '0000' 1870 - Bits 1-4 of the first octet indicating a 1871 length other than 3 octets 1872 - RELEASE COMPLETE message received with a 1873 call reference that does not relate to a 1874 call active or in progress 1875 - SETUP message received with call reference 1876 flag incorrectly set to 1 1878 draft Supplemental ATM Management Objects Mar 13, 1998 1880 - SETUP message received with a call 1881 reference for a call that is already 1882 active or in progress. 1884 3. Message too short 1886 The following cause values are monitored by this 1887 counter (Note: These cause values apply to both UNI3.0 1888 and UNI3.1 unless otherwise stated): 1890 Cause Value Meaning 1892 10 VPCI/VCI unacceptable (UNI3.0 only) 1893 36 VPCI/VCI assignment failure (UNI3.1 only) 1894 81 invalid call reference value 1895 82 identified channel does not exist 1896 89 invalid endpoint reference 1897 96 mandatory information element is missing 1898 97 message type non-existent or not 1899 implemented 1900 99 information element non-existent or not 1901 implemented 1902 100 invalid information element contents 1903 101 message not compatible with call state 1904 104 incorrect message length 1905 111 protocol error, unspecified 1907 NOTE: For this counter, RELEASE COMPLETE 1908 messages that are a reply to a previous RELEASE 1909 message and contain the same cause value, are 1910 redundant (for counting purposes) and should not 1911 be counted." 1912 ::= { atmSigStatEntry 12 } 1914 atmSigDetectClgPtyEvents OBJECT-TYPE 1915 SYNTAX Counter32 1916 MAX-ACCESS read-only 1917 STATUS current 1918 DESCRIPTION 1919 "Number of Calling Party Events detected on this 1920 interface. This counter monitors error events that 1921 occur due to the originating user doing something 1922 wrong. This counter is incremented when a RELEASE, 1924 draft Supplemental ATM Management Objects Mar 13, 1998 1926 RELEASE COMPLETE (only when not preceded by a RELEASE 1927 mesg for the same call), ADD PARTY REJECT, or STATUS 1928 message that contains one of the following cause code 1929 values is received (Note: These cause values apply to 1930 both UNI3.0 and UNI3.1): 1932 Cause Value Meaning 1934 28 invalid number format (address incomplete) 1935 43 access information discarded 1936 57 bearer capability not authorized 1937 65 bearer capability not implemented 1938 73 unsupported combination of traffic 1939 parameters 1940 78 AAL parameters cannot be supported (UNI3.1 1941 only) 1942 91 invalid transit network selection 1943 93 AAL parameters cannot be supported (UNI3.0 1944 only) 1946 NOTE: For this counter, RELEASE COMPLETE 1947 messages that are a reply to a previous RELEASE 1948 message and contain the same cause value, are 1949 redundant (for counting purposes) and should not 1950 be counted." 1951 ::= { atmSigStatEntry 13 } 1953 atmSigEmitClgPtyEvents OBJECT-TYPE 1954 SYNTAX Counter32 1955 MAX-ACCESS read-only 1956 STATUS current 1957 DESCRIPTION 1958 "Number of Calling Party Events transmitted from this 1959 interface. This counter monitors error events that 1960 occur due to the originating user doing something 1961 wrong. This counter is incremented when a RELEASE, 1962 RELEASE COMPLETE (only when not preceded by a RELEASE 1963 mesg for the same call), ADD PARTY REJECT, or STATUS 1964 message that contains one of the following cause code 1965 values is transmitted (Note: These cause values apply 1966 to both UNI3.0 and UNI3.1): 1968 Cause Value Meaning 1970 draft Supplemental ATM Management Objects Mar 13, 1998 1972 28 invalid number format (address incomplete) 1973 43 access information discarded 1974 57 bearer capability not authorized 1975 65 bearer capability not implemented 1976 73 unsupported combination of traffic 1977 parameters 1978 78 AAL parameters cannot be supported (UNI3.1 1979 only) 1980 91 invalid transit network selection 1981 93 AAL parameters cannot be supported (UNI3.0 1982 only) 1984 NOTE: For this counter, RELEASE COMPLETE 1985 messages that are a reply to a previous RELEASE 1986 message and contain the same cause value, are 1987 redundant (for counting purposes) and should not 1988 be counted." 1989 ::= { atmSigStatEntry 14 } 1991 atmSigDetectTimerExpireds OBJECT-TYPE 1992 SYNTAX Counter32 1993 MAX-ACCESS read-only 1994 STATUS current 1995 DESCRIPTION 1996 "Number of Timer Expiries detected on this interface. 1997 The Timer Expiries Counter provides a count of network 1998 timer expiries, and to some extent, host or switch 1999 timer expiries. The conditions for incrementing this 2000 counter are: 2001 - Expiry of any network timer 2003 - Receipt of a RELEASE or RELEASE COMPLETE 2004 message with Cause #102, 'recovery on 2005 timer expiry'. 2007 NOTE: For this counter, RELEASE COMPLETE messages 2008 that are a reply to a previous RELEASE message and 2009 contain the same cause value, are redundant (for 2010 counting purposes) and should not be counted." 2012 ::= { atmSigStatEntry 15 } 2014 atmSigEmitTimerExpireds OBJECT-TYPE 2015 SYNTAX Counter32 2017 draft Supplemental ATM Management Objects Mar 13, 1998 2019 MAX-ACCESS read-only 2020 STATUS current 2021 DESCRIPTION 2022 "Number of Timer Expiries transmitted from this 2023 interface. The Timer Expiries Counter provides a count 2024 of network timer expiries, and to some extent, host or 2025 switch timer expiries. The conditions for incrementing 2026 this counter are: 2027 - Expiry of any network timer 2029 - Receipt of a RELEASE or RELEASE COMPLETE 2030 message with Cause #102, 'recovery on 2031 timer expiry'. 2033 NOTE: For this counter, RELEASE COMPLETE messages 2034 that are a reply to a previous RELEASE message and 2035 contain the same cause value, are redundant (for 2036 counting purposes) and should not be counted." 2037 ::= { atmSigStatEntry 16 } 2039 atmSigDetectRestarts OBJECT-TYPE 2040 SYNTAX Counter32 2041 MAX-ACCESS read-only 2042 STATUS current 2043 DESCRIPTION 2044 "Number of Restart Activity errors detected on this 2045 interface. The Restart Activity Counter provides a 2046 count of host, switch, or network restart activity. 2047 This counter is incremented when receiving a RESTART 2048 message." 2049 ::= { atmSigStatEntry 17 } 2051 atmSigEmitRestarts OBJECT-TYPE 2052 SYNTAX Counter32 2053 MAX-ACCESS read-only 2054 STATUS current 2055 DESCRIPTION 2056 "Number of Restart Activity errors transmitted from 2057 this interface. The Restart Activity Counter provides 2058 a count of host, switch, or network restart activity. 2059 This counter is incremented when transmitting a RESTART 2060 message." 2061 ::= { atmSigStatEntry 18 } 2063 draft Supplemental ATM Management Objects Mar 13, 1998 2065 atmSigInEstabls OBJECT-TYPE 2066 SYNTAX Counter32 2067 MAX-ACCESS read-only 2068 STATUS current 2069 DESCRIPTION 2070 "Number of SVC VCCs established at this signalling 2071 entity for incoming connections." 2072 ::= { atmSigStatEntry 19 } 2074 atmSigOutEstabls OBJECT-TYPE 2075 SYNTAX Counter32 2076 MAX-ACCESS read-only 2077 STATUS current 2078 DESCRIPTION 2079 "Number of SVC VCCs established at this signalling 2080 entity for outgoing connections." 2081 ::= { atmSigStatEntry 20 } 2083 draft Supplemental ATM Management Objects Mar 13, 1998 2085 -- 4. ATM Interface Signalling Support Table 2086 -- 2087 -- This table provides information to support 2088 -- the signalling process which is used to establish 2089 -- ATM Switched Virtual Connections (SVCs). 2091 atmSigSupportTable OBJECT-TYPE 2092 SYNTAX SEQUENCE OF AtmSigSupportEntry 2093 MAX-ACCESS not-accessible 2094 STATUS current 2095 DESCRIPTION 2096 "This table contains ATM local interface configuration 2097 parameters, one entry per ATM signalling interface." 2098 ::= { atm2MIBObjects 4 } 2100 atmSigSupportEntry OBJECT-TYPE 2101 SYNTAX AtmSigSupportEntry 2102 MAX-ACCESS not-accessible 2103 STATUS current 2104 DESCRIPTION 2105 "This list contains signalling configuration parameters 2106 and state variables." 2107 INDEX { ifIndex } 2108 ::= { atmSigSupportTable 1} 2110 AtmSigSupportEntry ::= SEQUENCE { 2111 atmSigSupportClgPtyNumDel INTEGER, 2112 atmSigSupportClgPtySubAddr INTEGER, 2113 atmSigSupportCldPtySubAddr INTEGER, 2114 atmSigSupportHiLyrInfo INTEGER, 2115 atmSigSupportLoLyrInfo INTEGER, 2116 atmSigSupportBlliRepeatInd INTEGER, 2117 atmSigSupportAALInfo INTEGER, 2118 atmSigSupportPrefCarrier OCTET STRING 2119 } 2121 atmSigSupportClgPtyNumDel OBJECT-TYPE 2122 SYNTAX INTEGER { enabled(1), disabled(2) } 2123 MAX-ACCESS read-write 2124 STATUS current 2125 DESCRIPTION 2126 "This object indicates whether the Calling Party Number 2127 Information Element is transferred to the called party 2128 address. The value of this object can be: 2130 draft Supplemental ATM Management Objects Mar 13, 1998 2132 - enabled(1) This Information Element is transferred 2133 to the called party 2135 - disabled(2) This Information Element is NOT 2136 transferred to the called party." 2137 ::= { atmSigSupportEntry 1 } 2139 atmSigSupportClgPtySubAddr OBJECT-TYPE 2140 SYNTAX INTEGER { enabled(1), disabled(2) } 2141 MAX-ACCESS read-write 2142 STATUS current 2143 DESCRIPTION 2144 "This object indicates whether to accept and transfer 2145 the Calling Party Subaddress Information Element from 2146 the calling party to the called party. Calling party 2147 subaddress information shall only be transferred to the 2148 called party if calling party number delivery is 2149 enabled (i.e., atmSigSupportClgPtyNumDel = 2150 'enabled(1)'. The value of this object can be: 2151 - enabled(1) This Information Element is transferred 2152 to the called party 2154 - disabled(2) This Information Element is NOT 2155 transferred to the called party." 2156 ::= { atmSigSupportEntry 2 } 2158 atmSigSupportCldPtySubAddr OBJECT-TYPE 2159 SYNTAX INTEGER { enabled(1), disabled(2) } 2160 MAX-ACCESS read-write 2161 STATUS current 2162 DESCRIPTION 2163 "This object indicates whether to accept, transfer, and 2164 deliver the Called Party Subaddress Information Element 2165 from the calling party to the called party. The value 2166 of this object can be: 2167 - enabled(1) This Information Element is transferred 2168 to the called party 2170 - disabled(2) This Information Element is NOT 2171 transferred to the called party." 2172 ::= { atmSigSupportEntry 3 } 2174 atmSigSupportHiLyrInfo OBJECT-TYPE 2175 SYNTAX INTEGER { enabled(1), disabled(2) } 2177 draft Supplemental ATM Management Objects Mar 13, 1998 2179 MAX-ACCESS read-write 2180 STATUS current 2181 DESCRIPTION 2182 "This object indicates whether to accept, transfer, and 2183 deliver the Broadband High Layer Information Element 2184 from the calling party to the called party. The value 2185 of this object can be: 2186 - enabled(1) This Information Element is transferred 2187 to the called party 2189 - disabled(2) This Information Element is NOT 2190 transferred to the called party." 2191 ::= { atmSigSupportEntry 4 } 2193 atmSigSupportLoLyrInfo OBJECT-TYPE 2194 SYNTAX INTEGER { enabled(1), disabled(2) } 2195 MAX-ACCESS read-write 2196 STATUS current 2197 DESCRIPTION 2198 "This object indicates whether to accept, transfer, and 2199 deliver the Broadband Low Layer Information Element 2200 from the calling party to the called party. The value 2201 of this object can be: 2202 - enabled(1) This Information Element is transferred 2203 to the called party 2205 - disabled(2) This Information Element is NOT 2206 transferred to the called party." 2207 ::= { atmSigSupportEntry 5 } 2209 atmSigSupportBlliRepeatInd OBJECT-TYPE 2210 SYNTAX INTEGER { enabled(1), disabled(2) } 2211 MAX-ACCESS read-write 2212 STATUS current 2213 DESCRIPTION 2214 "This object indicates whether to accept, transfer, and 2215 deliver the Broadband Repeat Indicator with two or 2216 three instances of the Broadband Low Layer Information 2217 Element for low layer information selection from the 2218 calling party to the called party. This object shall 2219 only be transferred if atmSigSupportLoLyrInfo = 2220 'enabled(1)'. The value of this object can be: 2221 - enabled(1) This Information Element is transferred 2222 to the called party 2224 draft Supplemental ATM Management Objects Mar 13, 1998 2226 - disabled(2) This Information Element is NOT 2227 transferred to the called party." 2228 ::= { atmSigSupportEntry 6 } 2230 atmSigSupportAALInfo OBJECT-TYPE 2231 SYNTAX INTEGER { enabled(1), disabled(2) } 2232 MAX-ACCESS read-write 2233 STATUS current 2234 DESCRIPTION 2235 "This object indicates whether to accept, transfer, and 2236 deliver the ATM Adaptation Layer Parameters Information 2237 Element from the calling party to the called party. 2238 The value of this object can be: 2239 - enabled(1) This Information Element is transferred 2240 to the called party 2242 - disabled(2) This Information Element is NOT 2243 transferred to the called party." 2244 ::= { atmSigSupportEntry 7 } 2246 atmSigSupportPrefCarrier OBJECT-TYPE 2247 SYNTAX OCTET STRING 2248 MAX-ACCESS read-write 2249 STATUS current 2250 DESCRIPTION 2251 "This parameter identifies the carrier to which 2252 intercarrier calls originated from this interface are 2253 routed when transit network selection information is 2254 not provided by the calling party. If a Carrier 2255 Identification Code (CIC) is used the parameter shall 2256 contain the CIC. For three-digit CICs, the first octet 2257 shall be '0' and the CIC is contained in the three 2258 following octets. If the preferred carrier feature is 2259 not supported the value is a zero-length string." 2260 ::= { atmSigSupportEntry 8 } 2262 -- 5. ATM Signalling Descriptor Parameter Table 2264 atmSigDescrParamTable OBJECT-TYPE 2265 SYNTAX SEQUENCE OF AtmSigDescrParamEntry 2266 MAX-ACCESS not-accessible 2267 STATUS current 2268 DESCRIPTION 2270 draft Supplemental ATM Management Objects Mar 13, 1998 2272 "A table contains signalling capabilities of VCLs 2273 except the Traffic Descriptor. Traffic 2274 descriptors are described in the 2275 atmTrafficDescrParamTable." 2276 REFERENCE 2277 "ATM Forum User-Network Interface Specification, 2278 Version 3.1, Section 5.4.5 Variable Length 2279 Information Elements." 2280 ::= { atm2MIBObjects 5 } 2282 atmSigDescrParamEntry OBJECT-TYPE 2283 SYNTAX AtmSigDescrParamEntry 2284 MAX-ACCESS not-accessible 2285 STATUS current 2286 DESCRIPTION 2287 "Each entry in this table represents a set of 2288 signalling capabilities that can be applied to a 2289 VCL. There is no requirement for unique entries, 2290 except that the index must be unique. Objects 2291 atmSigDescrParamRowStatus is required during 2292 creation." 2293 INDEX { atmSigDescrParamIndex } 2294 ::= { atmSigDescrParamTable 1 } 2296 AtmSigDescrParamEntry ::= 2297 SEQUENCE { 2298 atmSigDescrParamIndex 2299 AtmSigDescrParamIndex, 2300 atmSigDescrParamAalType INTEGER, 2301 atmSigDescrParamAalSscsType INTEGER, 2302 atmSigDescrParamBhliType INTEGER, 2303 atmSigDescrParamBhliInfo OCTET STRING, 2304 atmSigDescrParamBbcConnConf INTEGER, 2305 atmSigDescrParamBlliLayer2 INTEGER, 2306 atmSigDescrParamBlliLayer3 INTEGER, 2307 atmSigDescrParamBlliPktSize INTEGER, 2308 atmSigDescrParamBlliSnapId INTEGER, 2309 atmSigDescrParamBlliOuiPid OCTET STRING, 2310 atmSigDescrParamRowStatus RowStatus 2311 } 2313 atmSigDescrParamIndex OBJECT-TYPE 2314 SYNTAX AtmSigDescrParamIndex 2315 MAX-ACCESS not-accessible 2317 draft Supplemental ATM Management Objects Mar 13, 1998 2319 STATUS current 2320 DESCRIPTION 2321 "The value of this object is used by the 2322 atmVclGenSigDescrIndex object in the 2323 atmVclGenTable to identify a row in this table." 2324 ::= { atmSigDescrParamEntry 1 } 2326 atmSigDescrParamAalType OBJECT-TYPE 2327 SYNTAX INTEGER { 2328 other(1), -- not defined 2329 aal1(2), -- AAL type 1 2330 aal34(3), -- AAL type 3/4 2331 aal5(4), -- AAL type 5 2332 userDefined(5) -- User-Defined AAL 2333 } 2334 MAX-ACCESS read-create 2335 STATUS current 2336 DESCRIPTION 2337 "The AAL type. The value of this object is set to 2338 other(1) when not defined." 2339 DEFVAL { other } 2340 ::= { atmSigDescrParamEntry 2 } 2342 atmSigDescrParamAalSscsType OBJECT-TYPE 2343 SYNTAX INTEGER { 2344 other(1), -- other, or not used 2345 assured(2), -- Data SSCS based on SSCOP 2346 -- assured operation 2347 nonassured(3), -- Data SSCS based on SSCOP 2348 -- non-assured operation 2349 frameRelay(4), -- frame relay SSCS 2350 null(5) -- null 2351 } 2352 MAX-ACCESS read-create 2353 STATUS current 2354 DESCRIPTION 2355 "The SSCS type used by this entry." 2356 DEFVAL { other } 2357 ::= { atmSigDescrParamEntry 3 } 2359 atmSigDescrParamBhliType OBJECT-TYPE 2360 SYNTAX INTEGER { 2361 other(1), -- not defined 2362 iso(2), -- ISO 2364 draft Supplemental ATM Management Objects Mar 13, 1998 2366 user(3), -- User specific 2367 hiProfile(4), -- Higher layer profile 2368 -- this enum applicable to 2369 -- UNI 3.0 only 2370 vendorSpecific(5) -- Vender specific 2371 -- application identifier 2372 } 2373 MAX-ACCESS read-create 2374 STATUS current 2375 DESCRIPTION 2376 "The Broadband high layer type." 2377 DEFVAL { other } 2378 ::= { atmSigDescrParamEntry 4 } 2380 atmSigDescrParamBhliInfo OBJECT-TYPE 2381 SYNTAX OCTET STRING (SIZE(0..7)) 2382 MAX-ACCESS read-create 2383 STATUS current 2384 DESCRIPTION 2385 "The Broadband high layer information. When 2386 atmSigDescrParamBhliType is set to iso(2), the 2387 value of this object is a zero length string. 2388 When atmSigDescrParamBhliType is set to 2389 hiProfile(4), the value of this object is a length 2390 of 4 octet string containing user to user profile 2391 identifier. When atmSigDescrParamBhliType is set 2392 to vendorSpecific(4), the value of this object 2393 is a length of 7 octet string. The most 2394 significant 3 octets consist of a globally- 2395 administered OUI, the least significant 4 octets 2396 are the vender administered application OUI." 2397 DEFVAL { ''H } 2398 ::= { atmSigDescrParamEntry 5 } 2400 atmSigDescrParamBbcConnConf OBJECT-TYPE 2401 SYNTAX INTEGER { 2402 ptp(1), -- point-to-point 2403 ptmp(2) -- point-to-multipoint 2404 } 2405 MAX-ACCESS read-create 2406 STATUS current 2407 DESCRIPTION 2408 "The Broadband bearer capability user plane 2409 connection configuration parameter." 2411 draft Supplemental ATM Management Objects Mar 13, 1998 2413 ::= { atmSigDescrParamEntry 6 } 2415 atmSigDescrParamBlliLayer2 OBJECT-TYPE 2416 SYNTAX INTEGER { 2417 other(1), -- not specified 2418 iso1745(2), -- Basic mode ISO 1745 2419 q921(3), -- CCITT Recommendation Q.921 2420 x25linklayer(4), -- CCITT Recommendation X.25 2421 -- Link Layer 2422 x25multilink(5), -- CCITT Recommendation X.25 2423 -- Multilink 2424 lapb(6), -- Extended LAPB; for half 2425 -- duplex operation 2426 hdlcArm(7), -- HDLC ARM (ISO 4335) 2427 hdlcNrm(8), -- HDLC NRM (ISO 4335) 2428 hdlcAbm(9), -- HDLC ABM (ISO 4335) 2429 iso88022(10), -- LAN logical link control 2430 -- (ISO 8802/2) 2431 x75slp(11), -- CCITT Recommendation X.75, 2432 -- single link 2433 -- procedure (SLP) 2434 q922(12), -- CCITT Recommendation Q.922 2435 userDef(13), -- User specified 2436 iso7776(14) -- ISO 7776 DTE-DTE operation 2437 } 2438 MAX-ACCESS read-create 2439 STATUS current 2440 DESCRIPTION 2441 "The Broadband low layer information, protocol 2442 type of layer 2. The value of this object is 2443 other(1) if layer 2 protocol is not used." 2444 DEFVAL { other } 2445 ::= { atmSigDescrParamEntry 7 } 2447 atmSigDescrParamBlliLayer3 OBJECT-TYPE 2448 SYNTAX INTEGER { 2449 other(1), -- not specified 2450 x25pkt(2), -- CCITT Recommendation X.25 2451 -- packet layer 2452 isoiec8208(3), -- ISO/IEC 8208 (X.25 packet 2453 -- level protocol for data 2454 -- terminal equipment) 2455 x223iso8878(4), -- X.223/ISO 8878 2456 isoiec8473(5), -- ISO/IEC 8473 OSI 2458 draft Supplemental ATM Management Objects Mar 13, 1998 2460 -- connectionless 2461 -- mode protocol 2462 t70(6), -- CCITT Recommendation T.70 2463 -- minimum 2464 -- network layer 2465 tr9577(7), -- ISO/IEC TR 9577 Protocol 2466 -- Identification in the 2467 -- network layer 2468 userDef(8) -- user specified 2469 } 2470 MAX-ACCESS read-create 2471 STATUS current 2472 DESCRIPTION 2473 "The Broadband low layer information, protocol 2474 type of layer 3. The value of this object is 2475 other(1) if layer 3 protocol is not used." 2476 DEFVAL { other } 2477 ::= { atmSigDescrParamEntry 8 } 2479 atmSigDescrParamBlliPktSize OBJECT-TYPE 2480 SYNTAX INTEGER { 2481 other(1), -- not used 2482 s16(2), -- 16 octets 2483 s32(3), -- 32 octets 2484 s64(4), -- 64 octets 2485 s128(5), -- 128 octets 2486 s256(6), -- 256 octets 2487 s512(7), -- 512 octets 2488 s1024(8), -- 1028 octets 2489 s2048(9), -- 2048 octets 2490 s4096(10) -- 4096 octets 2491 } 2492 MAX-ACCESS read-create 2493 STATUS current 2494 DESCRIPTION 2495 "The default packet size defined in B-LLI." 2496 DEFVAL { other } 2497 ::= { atmSigDescrParamEntry 9 } 2499 atmSigDescrParamBlliSnapId OBJECT-TYPE 2500 SYNTAX INTEGER { 2501 other(1), -- not used 2502 true(2), -- SNAP ID is 1 2503 false(3) -- SNAP ID is 0 2505 draft Supplemental ATM Management Objects Mar 13, 1998 2507 } 2508 MAX-ACCESS read-create 2509 STATUS current 2510 DESCRIPTION 2511 "The SNAP ID used for Broadband low layer protocol 2512 layer 3. The value of this object is other(1) if 2513 atmSigDescrParamBlliLayer3 is set to other(1)." 2514 DEFVAL { other } 2515 ::= { atmSigDescrParamEntry 10 } 2517 atmSigDescrParamBlliOuiPid OBJECT-TYPE 2518 SYNTAX OCTET STRING (SIZE(0..5)) 2519 MAX-ACCESS read-create 2520 STATUS current 2521 DESCRIPTION 2522 "The OUI/PID encoding for Broadband low layer 2523 protocol layer 3. The value of this object is a 2524 zero length string if atmSigDescrParamBlliLayer3 2525 is set to none(1). When used, it is always 5 2526 octets with the most significant octet as the OUI 2527 Octet 1 and the least significant octet as the PID 2528 Octet 2." 2529 DEFVAL { ''H } 2530 ::= { atmSigDescrParamEntry 11 } 2532 atmSigDescrParamRowStatus OBJECT-TYPE 2533 SYNTAX RowStatus 2534 MAX-ACCESS read-create 2535 STATUS current 2536 DESCRIPTION 2537 "This object is used to create and delete rows in 2538 the atmSigDescrParamTable. Writable values are: 2539 -'createAndWait' which allows manager to create an 2540 entry first and fill in the parameters later. 2541 -'active' which allows manager to set the entry to 2542 be available to users. -'destroy' which allows 2543 manager to delete an entry from this table. 2544 Readable values are: -'createAndWait' which means 2545 the entry is created but not available to be used. 2546 -'active' means it is active and ready to be used 2547 by agent or manager." 2548 ::= { atmSigDescrParamEntry 12 } 2550 draft Supplemental ATM Management Objects Mar 13, 1998 2552 -- 2553 -- 6. ATM Interface Registered Address Table 2554 -- 2556 atmIfRegisteredAddrTable OBJECT-TYPE 2557 SYNTAX SEQUENCE OF AtmIfRegisteredAddrEntry 2558 MAX-ACCESS not-accessible 2559 STATUS current 2560 DESCRIPTION 2561 "This table contains a list of ATM addresses that can 2562 be used for calls to and from a given interface by a 2563 switch or service. The ATM addresses are either 2564 registered by the endsystem via ILMI or statically 2565 configured. This table does not expose PNNI 2566 reachability information. ILMI registered addresses 2567 cannot be deleted using this table. This table only 2568 applies to switches and network services." 2569 ::= { atm2MIBObjects 6 } 2571 atmIfRegisteredAddrEntry OBJECT-TYPE 2572 SYNTAX AtmIfRegisteredAddrEntry 2573 MAX-ACCESS not-accessible 2574 STATUS current 2575 DESCRIPTION 2576 "An entry in the ATM Interface Registered Address 2577 table." 2578 INDEX { ifIndex, atmIfRegAddrAddress } 2579 ::= { atmIfRegisteredAddrTable 1} 2581 AtmIfRegisteredAddrEntry ::= SEQUENCE { 2582 atmIfRegAddrAddress AtmAddr, 2583 atmIfRegAddrAddressSource INTEGER, 2584 atmIfRegAddrOrgScope INTEGER, 2585 atmIfRegAddrRowStatus RowStatus 2586 } 2588 atmIfRegAddrAddress OBJECT-TYPE 2589 SYNTAX AtmAddr 2590 MAX-ACCESS not-accessible 2591 STATUS current 2592 DESCRIPTION 2593 "An address registered for a given switch or service 2594 interface." 2595 ::= { atmIfRegisteredAddrEntry 1} 2597 draft Supplemental ATM Management Objects Mar 13, 1998 2599 atmIfRegAddrAddressSource OBJECT-TYPE 2600 SYNTAX INTEGER { 2601 other(1), 2602 static(2), 2603 dynamic(3) 2604 } 2605 MAX-ACCESS read-only 2606 STATUS current 2607 DESCRIPTION 2608 "The type of address source for a given ATM Address. 2609 The value dynamic(3) is indicated when ILMI is used." 2610 ::= { atmIfRegisteredAddrEntry 2} 2612 atmIfRegAddrOrgScope OBJECT-TYPE 2613 SYNTAX INTEGER { 2614 localNetwork(1), 2615 localNetworkPlusOne(2), 2616 localNetworkPlusTwo(3), 2617 siteMinusOne(4), 2618 intraSite(5), 2619 sitePlusOne(6), 2620 organizationMinusOne(7), 2621 intraOrganization(8), 2622 organizationPlusOne(9), 2623 communityMinusOne(10), 2624 intraCommunity(11), 2625 communityPlusOne(12), 2626 regional(13), 2627 interRegional(14), 2628 global(15) 2629 } 2630 MAX-ACCESS read-create 2631 STATUS current 2632 DESCRIPTION 2633 "This object indicates the organizational scope for 2634 the referenced address. The information of the 2635 referenced address shall not be distributed outside 2636 the indicated scope. Refer to Annex 5.3 of ATM 2637 Forum UNI Signalling 4.0 for guidelines regarding 2638 the use of organizational scopes. 2640 This value cannot be configured for ILMI-registered 2641 addresses. 2643 draft Supplemental ATM Management Objects Mar 13, 1998 2645 The default values for organizational scope are 2646 localNetwork(1) for ATM group addresses, and 2647 global(15) for individual addresses." 2648 ::= { atmIfRegisteredAddrEntry 3} 2650 atmIfRegAddrRowStatus OBJECT-TYPE 2651 SYNTAX RowStatus 2652 MAX-ACCESS read-create 2653 STATUS current 2654 DESCRIPTION 2655 "This object is used to create and delete rows in the 2656 atmIfRegisteredAddrTable. Rows created dynamically 2657 (e.g., ILMI-registered addresses) cannot be deleted 2658 using this object." 2659 ::= { atmIfRegisteredAddrEntry 4} 2661 -- 7. ATM VPI/VCI to Address Mapping Table 2663 atmVclAddrTable OBJECT-TYPE 2664 SYNTAX SEQUENCE OF AtmVclAddrEntry 2665 MAX-ACCESS not-accessible 2666 STATUS current 2667 DESCRIPTION 2668 "This table provides a mapping between the 2669 atmVclTable and the ATM called party/calling party 2670 address. This table can be used to retrieve the 2671 calling party and called party ATM address pair 2672 for a given Vcl. Note that there can be more than 2673 one pair of calling party and called party ATM 2674 addresses for a VCL in a point to multi-point 2675 call." 2676 ::= { atm2MIBObjects 7 } 2678 atmVclAddrEntry OBJECT-TYPE 2679 SYNTAX AtmVclAddrEntry 2680 MAX-ACCESS not-accessible 2681 STATUS current 2682 DESCRIPTION 2683 "Each entry in this table represents a binding 2684 between a VCL and an ATM address associated with 2685 this call. This ATM address can be either the 2686 called party address or the calling party address. 2687 There can be more than one pair of calling/called 2689 draft Supplemental ATM Management Objects Mar 13, 1998 2691 party ATM addresses associated with the VCL entry 2692 for point to multi-point calls. Objects 2693 atmVclAddrAddr, atmVclAddrType, and 2694 atmVclAddrRowStatus are required during row 2695 creation." 2696 INDEX { ifIndex, atmVclVpi, atmVclVci, 2697 atmVclAddrAddr } 2698 ::= { atmVclAddrTable 1 } 2700 AtmVclAddrEntry ::= 2701 SEQUENCE { 2702 atmVclAddrAddr AtmAddr, 2703 atmVclAddrType INTEGER, 2704 atmVclAddrRowStatus RowStatus 2705 } 2707 atmVclAddrAddr OBJECT-TYPE 2708 SYNTAX AtmAddr 2709 MAX-ACCESS not-accessible 2710 STATUS current 2711 DESCRIPTION 2712 "An ATM address on one end of the VCL. For SVCs, 2713 the agent supplies the value of this object at 2714 creation time. For PVCs, manager can supply the 2715 value of this object during or after the PVC 2716 creation." 2717 ::= { atmVclAddrEntry 1 } 2719 atmVclAddrType OBJECT-TYPE 2720 SYNTAX INTEGER { 2721 callingParty(1), 2722 calledParty(2) 2723 } 2724 MAX-ACCESS read-create 2725 STATUS current 2726 DESCRIPTION 2727 "The type of ATM Address represented by the object 2728 atmVclAddrAddr. Choices are either the calling 2729 party ATM address or the called party ATM 2730 address." 2731 ::= { atmVclAddrEntry 2 } 2733 atmVclAddrRowStatus OBJECT-TYPE 2735 draft Supplemental ATM Management Objects Mar 13, 1998 2737 SYNTAX RowStatus 2738 MAX-ACCESS read-create 2739 STATUS current 2740 DESCRIPTION 2741 "This object is used to create or destroy an entry 2742 from this table." 2743 ::= { atmVclAddrEntry 3 } 2745 -- 8. ATM Address to VPI/VCI Mapping Table 2746 -- 2747 -- This table provides an alternative way to access 2748 -- a row in the atmVclAddrTable by using 2749 -- an ATM address as an index, instead of 2750 -- the ifIndex 2752 atmAddrVclTable OBJECT-TYPE 2753 SYNTAX SEQUENCE OF AtmAddrVclEntry 2754 MAX-ACCESS not-accessible 2755 STATUS current 2756 DESCRIPTION 2757 "This table provides an alternative way to 2758 retrieve the atmVclTable. This table can be used 2759 to retrieve the indexing to the atmVclTable by an 2760 ATM address." 2761 ::= { atm2MIBObjects 8 } 2763 atmAddrVclEntry OBJECT-TYPE 2764 SYNTAX AtmAddrVclEntry 2765 MAX-ACCESS not-accessible 2766 STATUS current 2767 DESCRIPTION 2768 "Each entry in this table represents an entry in 2769 the atmVclTable of the ATM-MIB [1] by its ATM 2770 address. The ATM address is either the calling or 2771 called party ATM address of the call. Entries in 2772 this table are read only. They show up when 2773 entries are created in the atmVclAddrTable." 2774 INDEX { atmVclAddrAddr, atmAddrVclAtmIfIndex, 2775 atmAddrVclVpi, atmAddrVclVci } 2776 ::= { atmAddrVclTable 1 } 2778 AtmAddrVclEntry ::= 2779 SEQUENCE { 2781 draft Supplemental ATM Management Objects Mar 13, 1998 2783 atmAddrVclAtmIfIndex InterfaceIndex, 2784 atmAddrVclVpi AtmVpIdentifier, 2785 atmAddrVclVci AtmVcIdentifier, 2786 atmAddrVclAddrType INTEGER 2787 } 2789 atmAddrVclAtmIfIndex OBJECT-TYPE 2790 SYNTAX InterfaceIndex 2791 MAX-ACCESS not-accessible 2792 STATUS current 2793 DESCRIPTION 2794 "The interface index of the ATM interface to which 2795 this VCL pertains. This object combined with the 2796 atmAddrVclVpi and atmAddrVclVci objects serves as 2797 an index to the atmVclTable." 2798 ::= { atmAddrVclEntry 1 } 2800 atmAddrVclVpi OBJECT-TYPE 2801 SYNTAX AtmVpIdentifier 2802 MAX-ACCESS not-accessible 2803 STATUS current 2804 DESCRIPTION 2805 "The VPI value of the VCL. This object combined 2806 with the atmAddrVclAtmIfIndex and atmAddrVclVci 2807 objects serves as an index to the atmVclTable." 2808 ::= { atmAddrVclEntry 2 } 2810 atmAddrVclVci OBJECT-TYPE 2811 SYNTAX AtmVcIdentifier 2812 MAX-ACCESS not-accessible 2813 STATUS current 2814 DESCRIPTION 2815 "The VCI value of the VCL. This object combined 2816 with the atmAddrVclAtmIfIndex and atmAddrVclVpi 2817 objects serves as an index to the atmVclTable." 2818 ::= { atmAddrVclEntry 3 } 2820 atmAddrVclAddrType OBJECT-TYPE 2821 SYNTAX INTEGER { 2822 callingParty(1), 2823 calledParty(2) } 2824 MAX-ACCESS read-only 2825 STATUS current 2826 DESCRIPTION 2828 draft Supplemental ATM Management Objects Mar 13, 1998 2830 "The type of ATM Address represented by the object 2831 atmVclAddrAddr. Choices are either calling party 2832 address or called party address." 2833 ::= { atmAddrVclEntry 4 } 2835 -- 9. ATM VPL Statistics Table 2837 atmVplStatTable OBJECT-TYPE 2838 SYNTAX SEQUENCE OF AtmVplStatEntry 2839 MAX-ACCESS not-accessible 2840 STATUS current 2841 DESCRIPTION 2842 "This table contains all statistic counters per 2843 VPL. It is used to monitor the usage of the VPL 2844 in terms of incoming cells and outgoing cells." 2845 ::= { atm2MIBObjects 9 } 2847 atmVplStatEntry OBJECT-TYPE 2848 SYNTAX AtmVplStatEntry 2849 MAX-ACCESS not-accessible 2850 STATUS current 2851 DESCRIPTION 2852 "Each entry in this table represents a VPL." 2853 INDEX { ifIndex, atmVplVpi } 2854 ::= { atmVplStatTable 1 } 2856 AtmVplStatEntry ::= 2857 SEQUENCE { 2858 atmVplStatTotalCellIns Counter32, 2859 atmVplStatClp0CellIns Counter32, 2860 atmVplStatTotalDiscards Counter32, 2861 atmVplStatClp0Discards Counter32, 2862 atmVplStatTotalCellOuts Counter32, 2863 atmVplStatClp0CellOuts Counter32, 2864 atmVplStatTaggedOuts Counter32 2865 } 2867 atmVplStatTotalCellIns OBJECT-TYPE 2868 SYNTAX Counter32 2869 MAX-ACCESS read-only 2870 STATUS current 2871 DESCRIPTION 2872 "The total number of valid ATM cells received by 2874 draft Supplemental ATM Management Objects Mar 13, 1998 2876 this VPL including both CLP=0 and CLP=1 cells. 2877 The cells are counted prior to the application of 2878 the traffic policing." 2879 ::= { atmVplStatEntry 1 } 2881 atmVplStatClp0CellIns OBJECT-TYPE 2882 SYNTAX Counter32 2883 MAX-ACCESS read-only 2884 STATUS current 2885 DESCRIPTION 2886 "The number of valid ATM cells received by this 2887 VPL with CLP=0. The cells are counted prior to 2888 the application of the traffic policing." 2889 ::= { atmVplStatEntry 2 } 2891 atmVplStatTotalDiscards OBJECT-TYPE 2892 SYNTAX Counter32 2893 MAX-ACCESS read-only 2894 STATUS current 2895 DESCRIPTION 2896 "The total number of valid ATM cells discarded by 2897 the traffic policing entity. This includes cells 2898 originally received with CLP=0 and CLP=1." 2899 ::= { atmVplStatEntry 3 } 2901 atmVplStatClp0Discards OBJECT-TYPE 2902 SYNTAX Counter32 2903 MAX-ACCESS read-only 2904 STATUS current 2905 DESCRIPTION 2906 "The total number of valid ATM cells received with 2907 CLP=0 an discarded by the traffic policing 2908 entity." 2909 ::= { atmVplStatEntry 4 } 2911 atmVplStatTotalCellOuts OBJECT-TYPE 2912 SYNTAX Counter32 2913 MAX-ACCESS read-only 2914 STATUS current 2915 DESCRIPTION 2916 "The total number of valid ATM cells transmitted 2917 by this VPL. This includes both CLP=0 and CLP=1 2918 cells." 2919 ::= { atmVplStatEntry 5 } 2921 draft Supplemental ATM Management Objects Mar 13, 1998 2923 atmVplStatClp0CellOuts OBJECT-TYPE 2924 SYNTAX Counter32 2925 MAX-ACCESS read-only 2926 STATUS current 2927 DESCRIPTION 2928 "The total number of valid ATM cells transmitted 2929 with CLP=0 by this VPL." 2930 ::= { atmVplStatEntry 6 } 2932 atmVplStatTaggedOuts OBJECT-TYPE 2933 SYNTAX Counter32 2934 MAX-ACCESS read-only 2935 STATUS current 2936 DESCRIPTION 2937 "The total number of valid ATM cells tagged by the 2938 traffic policing entity from CLP=0 to CLP=1 and 2939 transmitted by this VPL." 2940 ::= { atmVplStatEntry 7 } 2942 -- 10. ATM Logical Port Configuration Table 2944 atmVplLogicalPortTable OBJECT-TYPE 2945 SYNTAX SEQUENCE OF AtmVplLogicalPortEntry 2946 MAX-ACCESS not-accessible 2947 STATUS current 2948 DESCRIPTION 2949 "Indicates whether the VPL is an ATM Logical Port 2950 interface (ifType=80)." 2951 ::= { atm2MIBObjects 10 } 2953 atmVplLogicalPortEntry OBJECT-TYPE 2954 SYNTAX AtmVplLogicalPortEntry 2955 MAX-ACCESS not-accessible 2956 STATUS current 2957 DESCRIPTION 2958 "An entry with information about the ATM Logical 2959 Port interface." 2960 AUGMENTS { atmVplEntry } 2961 ::= { atmVplLogicalPortTable 1 } 2963 AtmVplLogicalPortEntry ::= 2964 SEQUENCE { 2966 draft Supplemental ATM Management Objects Mar 13, 1998 2968 atmVplLogicalPortDef INTEGER, 2969 atmVplLogicalPortIndex InterfaceIndexOrZero 2970 } 2972 atmVplLogicalPortDef OBJECT-TYPE 2973 SYNTAX INTEGER { 2974 notLogicalIf(1), 2975 isLogicalIf(2) 2976 } 2977 MAX-ACCESS read-create 2978 STATUS current 2979 DESCRIPTION 2980 "Indicates whether the VPC at this VPL interface 2981 is an ATM Logical Port interface." 2982 DEFVAL { notLogicalIf } 2983 ::= { atmVplLogicalPortEntry 1 } 2985 atmVplLogicalPortIndex OBJECT-TYPE 2986 SYNTAX InterfaceIndexOrZero 2987 MAX-ACCESS read-only 2988 STATUS current 2989 DESCRIPTION 2990 "The ifTable index of the ATM logical port 2991 interface associated with this VPL. The 2992 distinguished value of zero indicates that the 2993 agent has not (yet) assigned such an ifTable 2994 Index. The zero value must be assigned by the 2995 agent if the value of atmVplLogicalPortDef is set 2996 to notLogicalIf, or if the VPL row is not active." 2997 ::= { atmVplLogicalPortEntry 2 } 2999 draft Supplemental ATM Management Objects Mar 13, 1998 3001 -- 11. ATM VCL Statistics Table 3003 atmVclStatTable OBJECT-TYPE 3004 SYNTAX SEQUENCE OF AtmVclStatEntry 3005 MAX-ACCESS not-accessible 3006 STATUS current 3007 DESCRIPTION 3008 "This table contains all statistic counters per 3009 VCL. It is used to monitor the usage of the VCL 3010 in terms of incoming cells and outgoing cells." 3011 ::= { atm2MIBObjects 11 } 3013 atmVclStatEntry OBJECT-TYPE 3014 SYNTAX AtmVclStatEntry 3015 MAX-ACCESS not-accessible 3016 STATUS current 3017 DESCRIPTION 3018 "Each entry in this table represents a VCL." 3019 INDEX { ifIndex, atmVclVpi, atmVclVci } 3020 ::= { atmVclStatTable 1 } 3022 AtmVclStatEntry ::= 3023 SEQUENCE { 3024 atmVclStatTotalCellIns Counter32, 3025 atmVclStatClp0CellIns Counter32, 3026 atmVclStatTotalDiscards Counter32, 3027 atmVclStatClp0Discards Counter32, 3028 atmVclStatTotalCellOuts Counter32, 3029 atmVclStatClp0CellOuts Counter32, 3030 atmVclStatTaggedOuts Counter32 3031 } 3033 atmVclStatTotalCellIns OBJECT-TYPE 3034 SYNTAX Counter32 3035 MAX-ACCESS read-only 3036 STATUS current 3037 DESCRIPTION 3038 "The total number of valid ATM cells received by 3039 this VCL including both CLP=0 and CLP=1 cells. 3040 The cells are counted prior to the application of 3041 the traffic policing." 3042 ::= { atmVclStatEntry 1 } 3044 atmVclStatClp0CellIns OBJECT-TYPE 3046 draft Supplemental ATM Management Objects Mar 13, 1998 3048 SYNTAX Counter32 3049 MAX-ACCESS read-only 3050 STATUS current 3051 DESCRIPTION 3052 "The number of valid ATM cells received by this 3053 VCL with CLP=0. The cells are counted prior to 3054 the application of the traffic policing." 3055 ::= { atmVclStatEntry 2 } 3057 atmVclStatTotalDiscards OBJECT-TYPE 3058 SYNTAX Counter32 3059 MAX-ACCESS read-only 3060 STATUS current 3061 DESCRIPTION 3062 "The total number of valid ATM cells discarded by 3063 the traffic policing entity. This includes cells 3064 originally received with CLP=0 and CLP=1." 3065 ::= { atmVclStatEntry 3 } 3067 atmVclStatClp0Discards OBJECT-TYPE 3068 SYNTAX Counter32 3069 MAX-ACCESS read-only 3070 STATUS current 3071 DESCRIPTION 3072 "The total number of valid ATM cells received with 3073 CLP=0 an discarded by the traffic policing 3074 entity." 3075 ::= { atmVclStatEntry 4 } 3077 atmVclStatTotalCellOuts OBJECT-TYPE 3078 SYNTAX Counter32 3079 MAX-ACCESS read-only 3080 STATUS current 3081 DESCRIPTION 3082 "The total number of valid ATM cells transmitted 3083 by this VCL. This includes both CLP=0 and CLP=1 3084 cells." 3085 ::= { atmVclStatEntry 5 } 3087 atmVclStatClp0CellOuts OBJECT-TYPE 3088 SYNTAX Counter32 3089 MAX-ACCESS read-only 3090 STATUS current 3091 DESCRIPTION 3093 draft Supplemental ATM Management Objects Mar 13, 1998 3095 "The total number of valid ATM cells transmitted 3096 with CLP=0 by this VCL." 3097 ::= { atmVclStatEntry 6 } 3099 atmVclStatTaggedOuts OBJECT-TYPE 3100 SYNTAX Counter32 3101 MAX-ACCESS read-only 3102 STATUS current 3103 DESCRIPTION 3104 "The total number of valid ATM cells tagged by the 3105 traffic policing entity from CLP=0 to CLP=1 and 3106 transmitted by this VCL." 3107 ::= { atmVclStatEntry 7 } 3109 -- 12. ATM AAL5 per VCC Statistics Table 3111 atmAal5VclStatTable OBJECT-TYPE 3112 SYNTAX SEQUENCE OF AtmAal5VclStatEntry 3113 MAX-ACCESS not-accessible 3114 STATUS current 3115 DESCRIPTION 3116 "This table provides a collection of objects 3117 providing AAL5 configuration and performance 3118 statistics of a VCL." 3119 ::= { atm2MIBObjects 12 } 3121 atmAal5VclStatEntry OBJECT-TYPE 3122 SYNTAX AtmAal5VclStatEntry 3123 MAX-ACCESS not-accessible 3124 STATUS current 3125 DESCRIPTION 3126 "Each entry in this table represents a VCL." 3127 INDEX { ifIndex, atmVclVpi, atmVclVci } 3128 ::= { atmAal5VclStatTable 1 } 3130 AtmAal5VclStatEntry ::= 3131 SEQUENCE { 3132 atmAal5VclInPkts Counter32, 3133 atmAal5VclOutPkts Counter32, 3134 atmAal5VclInOctets Counter32, 3135 atmAal5VclOutOctets Counter32 3136 } 3138 draft Supplemental ATM Management Objects Mar 13, 1998 3140 atmAal5VclInPkts OBJECT-TYPE 3141 SYNTAX Counter32 3142 MAX-ACCESS read-only 3143 STATUS current 3144 DESCRIPTION 3145 "The number of AAL5 CPCS PDUs received on the AAL5 3146 VCC at the interface identified by the ifIndex." 3147 ::= { atmAal5VclStatEntry 1 } 3149 atmAal5VclOutPkts OBJECT-TYPE 3150 SYNTAX Counter32 3151 MAX-ACCESS read-only 3152 STATUS current 3153 DESCRIPTION 3154 "The number of AAL5 CPCS PDUs transmitted on the 3155 AAL5 VCC at the interface identified by the 3156 ifIndex." 3157 ::= { atmAal5VclStatEntry 2 } 3159 atmAal5VclInOctets OBJECT-TYPE 3160 SYNTAX Counter32 3161 MAX-ACCESS read-only 3162 STATUS current 3163 DESCRIPTION 3164 "The number of octets contained in AAL5 CPCS PDUs 3165 received on the AAL5 VCC at the interface 3166 identified by the ifIndex." 3167 ::= { atmAal5VclStatEntry 3 } 3169 atmAal5VclOutOctets OBJECT-TYPE 3170 SYNTAX Counter32 3171 MAX-ACCESS read-only 3172 STATUS current 3173 DESCRIPTION 3174 "The number of octets contained in AAL5 CPCS PDUs 3175 transmitted on the AAL5 VCC at the interface 3176 identified by the ifIndex." 3177 ::= { atmAal5VclStatEntry 4 } 3179 -- 13. ATM VC General Information Table 3181 atmVclGenTable OBJECT-TYPE 3183 draft Supplemental ATM Management Objects Mar 13, 1998 3185 SYNTAX SEQUENCE OF AtmVclGenEntry 3186 MAX-ACCESS not-accessible 3187 STATUS current 3188 DESCRIPTION 3189 "General Information for each VC." 3190 ::= { atm2MIBObjects 13 } 3192 atmVclGenEntry OBJECT-TYPE 3193 SYNTAX AtmVclGenEntry 3194 MAX-ACCESS not-accessible 3195 STATUS current 3196 DESCRIPTION 3197 "An entry with general information about the ATM 3198 VC." 3199 AUGMENTS { atmVclEntry } 3200 ::= { atmVclGenTable 1 } 3202 AtmVclGenEntry ::= 3203 SEQUENCE { 3204 atmVclGenSigDescrIndex AtmSigDescrParamIndex 3205 } 3207 atmVclGenSigDescrIndex OBJECT-TYPE 3208 SYNTAX AtmSigDescrParamIndex 3209 MAX-ACCESS read-create 3210 STATUS current 3211 DESCRIPTION 3212 "The value of this object identifies the row in 3213 the ATM Signalling Descriptor Parameter Table 3214 which applies to this VCL." 3215 ::= { atmVclGenEntry 1 } 3217 -- 14. ATM Interface Configuration Extension Table 3219 atmInterfaceExtTable OBJECT-TYPE 3220 SYNTAX SEQUENCE OF AtmInterfaceExtEntry 3221 MAX-ACCESS not-accessible 3222 STATUS current 3223 DESCRIPTION 3224 "This table contains ATM interface configuration and 3226 draft Supplemental ATM Management Objects Mar 13, 1998 3228 monitoring information not defined in the 3229 atmInterfaceConfTable from the ATM-MIB [1]. This 3230 includes the type of connection setup procedures, ILMI 3231 information, and information on the VPI/VCI range." 3232 ::= { atm2MIBObjects 14 } 3234 atmInterfaceExtEntry OBJECT-TYPE 3235 SYNTAX AtmInterfaceExtEntry 3236 MAX-ACCESS not-accessible 3237 STATUS current 3238 DESCRIPTION 3239 "An entry extends the atmInterfaceConfEntry defined in 3240 [1]. Each entry corresponds to an ATM interface." 3241 AUGMENTS { atmInterfaceConfEntry } 3242 ::= { atmInterfaceExtTable 1 } 3244 AtmInterfaceExtEntry ::= SEQUENCE { 3245 atmIntfConfigType AtmInterfaceType, 3246 atmIntfActualType AtmInterfaceType, 3247 atmIntfConfigSide INTEGER, 3248 atmIntfActualSide INTEGER, 3249 atmIntfIlmiAdminStatus BITS, 3250 atmIntfIlmiOperStatus BITS, 3251 atmIntfIlmiFsmState INTEGER, 3252 atmIntfIlmiEstablishConPollIntvl Integer32, 3253 atmIntfIlmiCheckConPollIntvl Integer32, 3254 atmIntfIlmiConPollInactFactor Integer32, 3255 atmIntfIlmiPublicPrivateIndctr INTEGER, 3256 atmInterfaceConfMaxSvpcVpi INTEGER, 3257 atmInterfaceCurrentMaxSvpcVpi INTEGER, 3258 atmInterfaceConfMaxSvccVpi INTEGER, 3259 atmInterfaceCurrentMaxSvccVpi INTEGER, 3260 atmInterfaceConfMinSvccVci INTEGER, 3261 atmInterfaceCurrentMinSvccVci INTEGER, 3262 atmIntfSigVccRxTrafficDescrIndex 3263 AtmTrafficDescrParamIndex, 3264 atmIntfSigVccTxTrafficDescrIndex 3265 AtmTrafficDescrParamIndex, 3266 atmIntfPvcFailures Counter32, 3267 atmIntfCurrentlyFailingPVpls Gauge32, 3268 atmIntfCurrentlyFailingPVcls Gauge32, 3269 atmIntfPvcFailuresTrapEnable TruthValue, 3270 atmIntfPvcNotificationInterval INTEGER 3271 } 3272 draft Supplemental ATM Management Objects Mar 13, 1998 3274 atmIntfConfigType OBJECT-TYPE 3275 SYNTAX AtmInterfaceType 3276 MAX-ACCESS read-write 3277 STATUS current 3278 DESCRIPTION 3279 "The type of connection setup procedures configured for 3280 the ATM interface. Setting this variable to a value of 3281 'other' is not allowed." 3282 DEFVAL { autoConfig } 3283 ::= { atmInterfaceExtEntry 1 } 3285 atmIntfActualType OBJECT-TYPE 3286 SYNTAX AtmInterfaceType 3287 MAX-ACCESS read-only 3288 STATUS current 3289 DESCRIPTION 3290 "The type of connection setup procedures currently 3291 being used on the interface. This may reflect a 3292 manually configured value for the interface type, or 3293 may be determined by other means such as auto- 3294 configuration. A value of `autoConfig' indicates that 3295 auto-configuration was requested but has not yet been 3296 completed." 3297 ::= { atmInterfaceExtEntry 2 } 3299 atmIntfConfigSide OBJECT-TYPE 3300 SYNTAX INTEGER { 3301 other(1), 3302 user(2), 3303 network(3) } 3304 MAX-ACCESS read-write 3305 STATUS current 3306 DESCRIPTION 3307 "The configured role of the managed entity as one side 3308 of the ATM interface. This value does not apply when 3309 the object atmIntfConfigType is set to `autoConfig', 3310 `atmfPnni1Dot0', or `atmfBici2Dot0'." 3311 ::= { atmInterfaceExtEntry 3 } 3313 atmIntfActualSide OBJECT-TYPE 3314 SYNTAX INTEGER { 3315 other(1), 3316 user(2), 3317 network(3), 3319 draft Supplemental ATM Management Objects Mar 13, 1998 3321 symmetric(4) } 3322 MAX-ACCESS read-only 3323 STATUS current 3324 DESCRIPTION 3325 "The current role used by the managed entity to 3326 represent one side of the ATM interface." 3327 ::= { atmInterfaceExtEntry 4 } 3329 atmIntfIlmiAdminStatus OBJECT-TYPE 3330 SYNTAX BITS { ilmi(0), 3331 ilmiAddressRegistration(1), 3332 ilmiConnectivity(2), 3333 ilmiPvcPvpMgmt(3), 3334 ilmiSigVccParamNegotiation(4) } 3335 MAX-ACCESS read-write 3336 STATUS current 3337 DESCRIPTION 3338 "Indicates which components of ILMI are 3339 administratively enabled on this interface. If the 3340 'ilmi' bit is not set, then no ILMI components are 3341 operational. ILMI components other than auto- 3342 configuration that are not represented in the value 3343 have their administrative status determined according 3344 to the 'ilmi' bit. The ILMI auto-configuration 3345 component is enabled/disabled by the atmIntfConfigType 3346 object." 3347 ::= { atmInterfaceExtEntry 5 } 3349 atmIntfIlmiOperStatus OBJECT-TYPE 3350 SYNTAX BITS { ilmi(0), 3351 ilmiAddressRegistration(1), 3352 ilmiConnectivity(2), 3353 ilmiPvcPvpMgmt(3), 3354 ilmiSigVccParamNegotiation(4) } 3355 MAX-ACCESS read-only 3356 STATUS current 3357 DESCRIPTION 3358 "Indicates which components of ILMI are operational on 3359 this interface." 3360 ::= { atmInterfaceExtEntry 6 } 3362 atmIntfIlmiFsmState OBJECT-TYPE 3363 SYNTAX INTEGER { stopped(1), 3364 linkFailing(2), 3366 draft Supplemental ATM Management Objects Mar 13, 1998 3368 establishing(3), 3369 configuring(4), 3370 retrievingNetworkPrefixes(5), 3371 registeringNetworkPrefixes(6), 3372 retrievingAddresses(7), 3373 registeringAddresses(8), 3374 verifying(9) } 3375 MAX-ACCESS read-only 3376 STATUS current 3377 DESCRIPTION 3378 "Indicates the state of the ILMI Finite State Machine 3379 associated with this interface." 3380 REFERENCE 3381 "ATM Forum ILMI 4.0 Specification, Appendix 1" 3382 ::= { atmInterfaceExtEntry 7 } 3384 atmIntfIlmiEstablishConPollIntvl OBJECT-TYPE 3385 SYNTAX Integer32 (1..65535) 3386 UNITS "seconds" 3387 MAX-ACCESS read-write 3388 STATUS current 3389 DESCRIPTION 3390 "The amount of time S between successive transmissions 3391 of ILMI messages on this interface for the purpose of 3392 detecting establishment of ILMI connectivity." 3393 REFERENCE 3394 "ATM Forum ILMI 4.0 Section 8.3.1" 3395 DEFVAL { 1 } 3396 ::= { atmInterfaceExtEntry 8 } 3398 atmIntfIlmiCheckConPollIntvl OBJECT-TYPE 3399 SYNTAX Integer32 (0..65535) 3400 UNITS "seconds" 3401 MAX-ACCESS read-write 3402 STATUS current 3403 DESCRIPTION 3404 "The amount of time T between successive transmissions 3405 of ILMI messages on this interface for the purpose of 3406 detecting loss of ILMI connectivity. The distinguished 3407 value zero disables ILMI connectivity procedures on 3408 this interface." 3409 REFERENCE 3410 "ATM Forum ILMI 4.0 Section 8.3.1" 3411 DEFVAL { 5 } 3413 draft Supplemental ATM Management Objects Mar 13, 1998 3415 ::= { atmInterfaceExtEntry 9 } 3417 atmIntfIlmiConPollInactFactor OBJECT-TYPE 3418 SYNTAX Integer32 (0..65535) 3419 MAX-ACCESS read-write 3420 STATUS current 3421 DESCRIPTION 3422 "The number K of consecutive polls on this interface 3423 for which no ILMI response message is received before 3424 ILMI connectivity is declared lost." 3425 REFERENCE 3426 "ATM Forum ILMI 4.0 Section 8.3.1" 3427 DEFVAL { 4 } 3428 ::= { atmInterfaceExtEntry 10 } 3430 atmIntfIlmiPublicPrivateIndctr OBJECT-TYPE 3431 SYNTAX INTEGER { 3432 other(1), 3433 public(2), 3434 private(3) 3435 } 3436 MAX-ACCESS read-write 3437 STATUS current 3438 DESCRIPTION 3439 "Specifies whether this end of the interface is 3440 advertised in ILMI as a device of the `public' or 3441 `private' type." 3442 DEFVAL { private } 3443 ::= { atmInterfaceExtEntry 11 } 3445 atmInterfaceConfMaxSvpcVpi OBJECT-TYPE 3446 SYNTAX INTEGER (0..4095) 3447 MAX-ACCESS read-write 3448 STATUS current 3449 DESCRIPTION 3450 "The maximum VPI that the signalling stack on the ATM 3451 interface is configured to support for allocation to 3452 switched virtual path connections." 3453 ::= { atmInterfaceExtEntry 12 } 3455 atmInterfaceCurrentMaxSvpcVpi OBJECT-TYPE 3456 SYNTAX INTEGER (0..4095) 3457 MAX-ACCESS read-only 3458 STATUS current 3460 draft Supplemental ATM Management Objects Mar 13, 1998 3462 DESCRIPTION 3463 "The maximum VPI that the signalling stack on the ATM 3464 interface may currently allocate to switched virtual 3465 path connections. This value is the minimum of 3466 atmInterfaceConfMaxSvpcVpi, and the 3467 atmInterfaceMaxSvpcVpi of the interface's UNI/NNI peer. 3469 If the interface does not negotiate with its peer to 3470 determine the maximum VPI that can be allocated to 3471 SVPCs on the interface, then the value of this object 3472 must equal atmInterfaceConfMaxSvpcVpi. " 3473 ::= { atmInterfaceExtEntry 13 } 3475 atmInterfaceConfMaxSvccVpi OBJECT-TYPE 3476 SYNTAX INTEGER (0..4095) 3477 MAX-ACCESS read-write 3478 STATUS current 3479 DESCRIPTION 3480 "The maximum VPI that the signalling stack on the ATM 3481 interface is configured to support for allocation to 3482 switched virtual channel connections." 3483 ::= { atmInterfaceExtEntry 14 } 3485 atmInterfaceCurrentMaxSvccVpi OBJECT-TYPE 3486 SYNTAX INTEGER (0..4095) 3487 MAX-ACCESS read-only 3488 STATUS current 3489 DESCRIPTION 3490 "The maximum VPI that the signalling stack on the ATM 3491 interface may currently allocate to switched virtual 3492 channel connections. This value is the minimum of 3493 atmInterfaceConfMaxSvccVpi, and the 3494 atmInterfaceConfMaxSvccVpi of the interface's UNI/NNI 3495 peer. 3497 If the interface does not negotiate with its peer to 3498 determine the maximum VPI that can be allocated to 3499 SVCCs on the interface, then the value of this object 3500 must equal atmInterfaceConfMaxSvccVpi." 3501 ::= { atmInterfaceExtEntry 15 } 3503 atmInterfaceConfMinSvccVci OBJECT-TYPE 3504 SYNTAX INTEGER (0..65535) 3505 MAX-ACCESS read-write 3507 draft Supplemental ATM Management Objects Mar 13, 1998 3509 STATUS current 3510 DESCRIPTION 3511 "The minimum VCI that the signalling stack on the ATM 3512 interface is configured to support for allocation to 3513 switched virtual channel connections." 3514 ::= { atmInterfaceExtEntry 16 } 3516 atmInterfaceCurrentMinSvccVci OBJECT-TYPE 3517 SYNTAX INTEGER (0..65535) 3518 MAX-ACCESS read-only 3519 STATUS current 3520 DESCRIPTION 3521 "The minimum VCI that the signalling stack on the ATM 3522 interface may currently allocate to switched virtual 3523 channel connections. This value is the maximum of 3524 atmInterfaceConfMinSvccVci, and the 3525 atmInterfaceConfMinSvccVci of the interface's UNI/NNI 3526 peer. 3528 If the interface does not negotiate with its peer to 3529 determine the minimum VCI that can be allocated to 3530 SVCCs on the interface, then the value of this object 3531 must equal atmInterfaceConfMinSvccVci." 3532 ::= { atmInterfaceExtEntry 17 } 3534 atmIntfSigVccRxTrafficDescrIndex OBJECT-TYPE 3535 SYNTAX AtmTrafficDescrParamIndex 3536 MAX-ACCESS read-write 3537 STATUS current 3538 DESCRIPTION 3539 "This object identifies the row in the 3540 atmTrafficDescrParamTable used during ILMI auto- 3541 configuration to specify the advertised signalling VCC 3542 traffic parameters for the receive direction. 3544 The traffic descriptor resulting from ILMI auto- 3545 configuration of the signalling VCC is indicated in the 3546 atmVclTable." 3547 ::= { atmInterfaceExtEntry 18 } 3549 atmIntfSigVccTxTrafficDescrIndex OBJECT-TYPE 3550 SYNTAX AtmTrafficDescrParamIndex 3551 MAX-ACCESS read-write 3552 STATUS current 3554 draft Supplemental ATM Management Objects Mar 13, 1998 3556 DESCRIPTION 3557 "This object identifies the row in the 3558 atmTrafficDescrParamTable used during ILMI auto- 3559 configuration to specify the advertised signalling VCC 3560 traffic parameters for the transmit direction. 3562 The traffic descriptor resulting from ILMI auto- 3563 configuration of the signalling VCC is indicated in the 3564 atmVclTable." 3565 ::= { atmInterfaceExtEntry 19 } 3567 atmIntfPvcFailures OBJECT-TYPE 3568 SYNTAX Counter32 3569 MAX-ACCESS read-only 3570 STATUS current 3571 DESCRIPTION 3572 "The number of times the operational status of a PVPL 3573 or PVCL on this interface has gone down." 3574 ::= { atmInterfaceExtEntry 20 } 3576 atmIntfCurrentlyFailingPVpls OBJECT-TYPE 3577 SYNTAX Gauge32 3578 MAX-ACCESS read-only 3579 STATUS current 3580 DESCRIPTION 3581 "The current number of VPLs on this interface for which 3582 there is an active row in the atmVplTable having an 3583 atmVplConnKind value of `pvc' and an atmVplOperStatus 3584 with a value other than `up'." 3585 ::= { atmInterfaceExtEntry 21 } 3587 atmIntfCurrentlyFailingPVcls OBJECT-TYPE 3588 SYNTAX Gauge32 3589 MAX-ACCESS read-only 3590 STATUS current 3591 DESCRIPTION 3592 "The current number of VCLs on this interface for which 3593 there is an active row in the atmVclTable having an 3594 atmVclConnKind value of `pvc' and an atmVclOperStatus 3595 with a value other than `up'." 3596 ::= { atmInterfaceExtEntry 22 } 3598 atmIntfPvcFailuresTrapEnable OBJECT-TYPE 3599 SYNTAX TruthValue 3601 draft Supplemental ATM Management Objects Mar 13, 1998 3603 MAX-ACCESS read-write 3604 STATUS current 3605 DESCRIPTION 3606 "Allows the generation of traps in response to PVCL or 3607 PVPL failures on this interface." 3608 DEFVAL { false } 3609 ::= { atmInterfaceExtEntry 23 } 3611 atmIntfPvcNotificationInterval OBJECT-TYPE 3612 SYNTAX INTEGER (1..3600) 3613 UNITS "seconds" 3614 MAX-ACCESS read-write 3615 STATUS current 3616 DESCRIPTION 3617 "The minimum interval between the sending of 3618 atmIntfPvcFailuresTrap notifications for this 3619 interface." 3620 DEFVAL { 30 } 3621 ::= { atmInterfaceExtEntry 24 } 3623 -- 15. ATM ILMI Service Registry Table 3625 atmIlmiSrvcRegTable OBJECT-TYPE 3626 SYNTAX SEQUENCE OF AtmIlmiSrvcRegEntry 3627 MAX-ACCESS not-accessible 3628 STATUS current 3629 DESCRIPTION 3630 "This table contains a list of all the ATM network 3631 services known by this device. 3633 The characteristics of these services are made 3634 available through the ILMI, using the ILMI general- 3635 purpose service registry MIB. 3637 These services may be made available to all ATM 3638 interfaces (atmIlmiSrvcRegIndex = 0) or to some 3639 specific ATM interfaces only (atmIlmiSrvcRegIndex = ATM 3640 interface index)." 3641 ::= { atm2MIBObjects 15 } 3643 atmIlmiSrvcRegEntry OBJECT-TYPE 3644 SYNTAX AtmIlmiSrvcRegEntry 3645 MAX-ACCESS not-accessible 3647 draft Supplemental ATM Management Objects Mar 13, 1998 3649 STATUS current 3650 DESCRIPTION 3651 "Information about a single service provider that is 3652 available to the user-side of an adjacent device 3653 through the ILMI." 3654 INDEX { atmIlmiSrvcRegIndex, 3655 atmIlmiSrvcRegServiceID, 3656 atmIlmiSrvcRegAddressIndex } 3657 ::= { atmIlmiSrvcRegTable 1 } 3659 AtmIlmiSrvcRegEntry ::= SEQUENCE { 3660 atmIlmiSrvcRegIndex InterfaceIndex, 3661 atmIlmiSrvcRegServiceID OBJECT IDENTIFIER, 3662 atmIlmiSrvcRegAddressIndex INTEGER, 3663 atmIlmiSrvcRegATMAddress AtmAddr, 3664 atmIlmiSrvcRegParm1 OCTET STRING, 3665 atmIlmiSrvcRegRowStatus RowStatus 3666 } 3668 atmIlmiSrvcRegIndex OBJECT-TYPE 3669 SYNTAX InterfaceIndex 3670 MAX-ACCESS not-accessible 3671 STATUS current 3672 DESCRIPTION 3673 "The ATM interface where the service defined in this 3674 entry can be made available to an ATM device attached 3675 to this interface. 3677 The value of 0 has a special meaning: when an ATM 3678 service is defined in an entry whose 3679 atmIlmiSrvcRegIndex is zero, the ATM service is 3680 available to ATM devices connected to any ATM 3681 interface. (default value(s)). 3683 When the user-side of an adjacent device queries the 3684 content of the ILMI service registry MIB (using the 3685 ILMI protocol), the local network-side responds with 3686 the ATM services defined in atmIlmiSrvcRegTable 3687 entries, provided that these entries are indexed by: 3688 - the corresponding ifIndex value (atmIlmiSrvcRegIndex 3689 equal to the ifIndex of the interface to which the 3690 adjacent device is connected) 3691 - zero (atmIlmiSrvcRegIndex=0)." 3692 ::= { atmIlmiSrvcRegEntry 1 } 3694 draft Supplemental ATM Management Objects Mar 13, 1998 3696 atmIlmiSrvcRegServiceID OBJECT-TYPE 3697 SYNTAX OBJECT IDENTIFIER 3698 MAX-ACCESS not-accessible 3699 STATUS current 3700 DESCRIPTION 3701 "This is the service identifier which uniquely 3702 identifies the type of service at the address provided 3703 in the table. The object identifiers for the LAN 3704 Emulation Configuration Server (LECS) and the ATM Name 3705 Server (ANS) are defined in the ATM Forum ILMI Service 3706 Registry MIB." 3707 ::= { atmIlmiSrvcRegEntry 2 } 3709 atmIlmiSrvcRegAddressIndex OBJECT-TYPE 3710 SYNTAX INTEGER (1..2147483647) 3711 MAX-ACCESS not-accessible 3712 STATUS current 3713 DESCRIPTION 3714 "An arbitrary integer to differentiate multiple rows 3715 containing different ATM addresses for the same service 3716 on the same interface. This number need NOT be the 3717 same as the corresponding ILMI atmfSrvcRegAddressIndex 3718 MIB object." 3719 ::= { atmIlmiSrvcRegEntry 3 } 3721 atmIlmiSrvcRegATMAddress OBJECT-TYPE 3722 SYNTAX AtmAddr 3723 MAX-ACCESS read-create 3724 STATUS current 3725 DESCRIPTION 3726 "This is the full address of the service. The user- 3727 side of the adjacent device may use this address to 3728 establish a connection with the service." 3729 ::= { atmIlmiSrvcRegEntry 4 } 3731 atmIlmiSrvcRegParm1 OBJECT-TYPE 3732 SYNTAX OCTET STRING (SIZE(1..255)) 3733 MAX-ACCESS read-create 3734 STATUS current 3735 DESCRIPTION 3736 "An octet string used according to the value of 3737 atmIlmiSrvcRegServiceID." 3738 ::= { atmIlmiSrvcRegEntry 5 } 3740 draft Supplemental ATM Management Objects Mar 13, 1998 3742 atmIlmiSrvcRegRowStatus OBJECT-TYPE 3743 SYNTAX RowStatus 3744 MAX-ACCESS read-create 3745 STATUS current 3746 DESCRIPTION 3747 "This object is used to create or destroy an entry from 3748 this table." 3749 ::= { atmIlmiSrvcRegEntry 6 } 3751 -- 16. ILMI Network Prefix Table 3753 atmIlmiNetworkPrefixTable OBJECT-TYPE 3754 SYNTAX SEQUENCE OF AtmIlmiNetworkPrefixEntry 3755 MAX-ACCESS not-accessible 3756 STATUS current 3757 DESCRIPTION 3758 "A table specifying per interface network prefix(es) 3759 supplied by the network side of the UNI during ILMI 3760 address registration. When no network prefixes are 3761 specified for a particular interface, one or more 3762 network prefixes based on the switch address(es) may be 3763 used for ILMI address registration." 3764 ::= { atm2MIBObjects 16 } 3766 atmIlmiNetworkPrefixEntry OBJECT-TYPE 3767 SYNTAX AtmIlmiNetworkPrefixEntry 3768 MAX-ACCESS not-accessible 3769 STATUS current 3770 DESCRIPTION 3771 "Information about a single network prefix supplied by 3772 the network side of the UNI during ILMI address 3773 registration. Note that the index variable 3774 atmIlmiNetPrefixPrefix is a variable-length string, and 3775 as such the rule for variable-length strings in section 3776 7.7 of RFC 1902 applies." 3777 INDEX { ifIndex, 3778 atmIlmiNetPrefixPrefix } 3779 ::= { atmIlmiNetworkPrefixTable 1 } 3781 AtmIlmiNetworkPrefixEntry ::= 3782 SEQUENCE { 3783 atmIlmiNetPrefixPrefix AtmIlmiNetworkPrefix, 3784 atmIlmiNetPrefixRowStatus RowStatus 3785 } 3787 draft Supplemental ATM Management Objects Mar 13, 1998 3789 atmIlmiNetPrefixPrefix OBJECT-TYPE 3790 SYNTAX AtmIlmiNetworkPrefix 3791 MAX-ACCESS not-accessible 3792 STATUS current 3793 DESCRIPTION 3794 "The network prefix specified for use in ILMI address 3795 registration." 3796 ::= { atmIlmiNetworkPrefixEntry 1 } 3798 atmIlmiNetPrefixRowStatus OBJECT-TYPE 3799 SYNTAX RowStatus 3800 MAX-ACCESS read-create 3801 STATUS current 3802 DESCRIPTION 3803 "Used to create, delete, activate and de-activate 3804 network prefixes used in ILMI address registration." 3805 ::= { atmIlmiNetworkPrefixEntry 2 } 3807 -- 17. ATM Switch Address Table 3809 atmSwitchAddressTable OBJECT-TYPE 3810 SYNTAX SEQUENCE OF AtmSwitchAddressEntry 3811 MAX-ACCESS not-accessible 3812 STATUS current 3813 DESCRIPTION 3814 "This table contains one or more ATM endsystem 3815 addresses on a per switch basis. These addresses are 3816 used to identify the switch. When no ILMI network 3817 prefixes are configured for certain interfaces, network 3818 prefixes based on the switch address(es) may be used 3819 for ILMI address registration." 3820 ::= { atm2MIBObjects 17 } 3822 atmSwitchAddressEntry OBJECT-TYPE 3823 SYNTAX AtmSwitchAddressEntry 3824 MAX-ACCESS not-accessible 3825 STATUS current 3826 DESCRIPTION 3827 "An entry in the ATM Switch Address table." 3828 INDEX { atmSwitchAddressIndex } 3829 ::= { atmSwitchAddressTable 1 } 3831 AtmSwitchAddressEntry ::= 3832 draft Supplemental ATM Management Objects Mar 13, 1998 3834 SEQUENCE { 3835 atmSwitchAddressIndex Integer32, 3836 atmSwitchAddressAddress OCTET STRING, 3837 atmSwitchAddressRowStatus RowStatus 3838 } 3840 atmSwitchAddressIndex OBJECT-TYPE 3841 SYNTAX Integer32 (1..65535) 3842 MAX-ACCESS not-accessible 3843 STATUS current 3844 DESCRIPTION 3845 "An arbitrary index used to enumerate the ATM endsystem 3846 addresses for this switch." 3847 ::= { atmSwitchAddressEntry 1 } 3849 atmSwitchAddressAddress OBJECT-TYPE 3850 SYNTAX OCTET STRING (SIZE(13|20)) 3851 MAX-ACCESS read-create 3852 STATUS current 3853 DESCRIPTION 3854 "An ATM endsystem address or address prefix used to 3855 identify this switch. When no ESI or SEL field is 3856 specified, the switch may generate the ESI and SEL 3857 fields automatically to obtain a complete 20-byte ATM 3858 endsystem address." 3859 ::= { atmSwitchAddressEntry 2 } 3861 atmSwitchAddressRowStatus OBJECT-TYPE 3862 SYNTAX RowStatus 3863 MAX-ACCESS read-create 3864 STATUS current 3865 DESCRIPTION 3866 "Used to create, delete, activate, and de-activate 3867 addresses used to identify this switch." 3868 ::= { atmSwitchAddressEntry 3 } 3870 -- 18. ATM VP Cross-Connect Extension Table 3872 atmVpCrossConnectXTable OBJECT-TYPE 3873 SYNTAX SEQUENCE OF AtmVpCrossConnectXEntry 3874 MAX-ACCESS not-accessible 3875 STATUS current 3876 DESCRIPTION 3878 draft Supplemental ATM Management Objects Mar 13, 1998 3880 "This table contains one row per VP Cross-Connect 3881 represented in the atmVpCrossConnectTable." 3882 ::= { atm2MIBObjects 18 } 3884 atmVpCrossConnectXEntry OBJECT-TYPE 3885 SYNTAX AtmVpCrossConnectXEntry 3886 MAX-ACCESS not-accessible 3887 STATUS current 3888 DESCRIPTION 3889 "Information about a particular ATM VP Cross-Connect. 3891 Each entry provides an two objects that name the 3892 Cross-Connect. One is assigned by the Service User and 3893 the other by the Service Provider." 3894 AUGMENTS { atmVpCrossConnectEntry } 3895 ::= { atmVpCrossConnectXTable 1 } 3897 AtmVpCrossConnectXEntry ::= SEQUENCE { 3898 atmVpCrossConnectUserName DisplayString, 3899 atmVpCrossConnectProviderName DisplayString 3900 } 3902 atmVpCrossConnectUserName OBJECT-TYPE 3903 SYNTAX DisplayString (0..255) 3904 MAX-ACCESS read-create 3905 STATUS current 3906 DESCRIPTION 3907 "This is a service user assigned textual representation 3908 of a VPC PVC." 3909 ::= { atmVpCrossConnectXEntry 1 } 3911 atmVpCrossConnectProviderName OBJECT-TYPE 3912 SYNTAX DisplayString (0..255) 3913 MAX-ACCESS read-only 3914 STATUS current 3915 DESCRIPTION 3916 "This is a system supplied textual representation of 3917 VPC PVC. It is assigned by the service provider." 3918 ::= { atmVpCrossConnectXEntry 2 } 3920 -- 19. ATM VC Cross-Connect Extension Table 3922 atmVcCrossConnectXTable OBJECT-TYPE 3923 draft Supplemental ATM Management Objects Mar 13, 1998 3925 SYNTAX SEQUENCE OF AtmVcCrossConnectXEntry 3926 MAX-ACCESS not-accessible 3927 STATUS current 3928 DESCRIPTION 3929 "This table contains one row per VC Cross-Connect 3930 represented in the atmVcCrossConnectTable." 3931 ::= { atm2MIBObjects 19 } 3933 atmVcCrossConnectXEntry OBJECT-TYPE 3934 SYNTAX AtmVcCrossConnectXEntry 3935 MAX-ACCESS not-accessible 3936 STATUS current 3937 DESCRIPTION 3938 "Information about a particular ATM VC Cross-Connect. 3940 Each entry provides an two objects that name the 3941 Cross-Connect. One is assigned by the Service User and 3942 the other by the Service Provider." 3943 AUGMENTS { atmVcCrossConnectEntry } 3944 ::= { atmVcCrossConnectXTable 1 } 3946 AtmVcCrossConnectXEntry ::= SEQUENCE { 3947 atmVcCrossConnectUserName DisplayString, 3948 atmVcCrossConnectProviderName DisplayString 3949 } 3951 atmVcCrossConnectUserName OBJECT-TYPE 3952 SYNTAX DisplayString (0..255) 3953 MAX-ACCESS read-create 3954 STATUS current 3955 DESCRIPTION 3956 "This is a service user assigned textual representation 3957 of a VCC PVC." 3958 ::= { atmVcCrossConnectXEntry 1 } 3960 atmVcCrossConnectProviderName OBJECT-TYPE 3961 SYNTAX DisplayString (0..255) 3962 MAX-ACCESS read-only 3963 STATUS current 3964 DESCRIPTION 3965 "This is a system supplied textual representation of 3966 VCC PVC. It is assigned by the service provider." 3967 ::= { atmVcCrossConnectXEntry 2 } 3969 draft Supplemental ATM Management Objects Mar 13, 1998 3971 -- 20. Currently Failing PVPL Table 3973 atmCurrentlyFailingPVplTable OBJECT-TYPE 3974 SYNTAX SEQUENCE OF AtmCurrentlyFailingPVplEntry 3975 MAX-ACCESS not-accessible 3976 STATUS current 3977 DESCRIPTION 3978 "A table indicating all VPLs for which there is an 3979 active row in the atmVplTable having an atmVplConnKind 3980 value of `pvc' and an atmVplOperStatus with a value 3981 other than `up'." 3982 ::= { atm2MIBObjects 20 } 3984 atmCurrentlyFailingPVplEntry OBJECT-TYPE 3985 SYNTAX AtmCurrentlyFailingPVplEntry 3986 MAX-ACCESS not-accessible 3987 STATUS current 3988 DESCRIPTION 3989 "Each entry in this table represents a VPL for which 3990 the atmVplRowStatus is `active', the atmVplConnKind is 3991 `pvc', and the atmVplOperStatus is other than `up'." 3992 INDEX { ifIndex, atmVplVpi } 3993 ::= { atmCurrentlyFailingPVplTable 1 } 3995 AtmCurrentlyFailingPVplEntry ::= 3996 SEQUENCE { 3997 atmCurrentlyFailingPVplTimeStamp TimeStamp 3998 } 4000 atmCurrentlyFailingPVplTimeStamp OBJECT-TYPE 4001 SYNTAX TimeStamp 4002 MAX-ACCESS read-only 4003 STATUS current 4004 DESCRIPTION 4005 "The time at which this PVPL began to fail." 4006 ::= { atmCurrentlyFailingPVplEntry 1 } 4008 -- 21. Currently Failing PVCL Table 4010 atmCurrentlyFailingPVclTable OBJECT-TYPE 4011 SYNTAX SEQUENCE OF AtmCurrentlyFailingPVclEntry 4012 MAX-ACCESS not-accessible 4013 STATUS current 4015 draft Supplemental ATM Management Objects Mar 13, 1998 4017 DESCRIPTION 4018 "A table indicating all VCLs for which there is an 4019 active row in the atmVclTable having an atmVclConnKind 4020 value of `pvc' and an atmVclOperStatus with a value 4021 other than `up'." 4022 ::= { atm2MIBObjects 21 } 4024 atmCurrentlyFailingPVclEntry OBJECT-TYPE 4025 SYNTAX AtmCurrentlyFailingPVclEntry 4026 MAX-ACCESS not-accessible 4027 STATUS current 4028 DESCRIPTION 4029 "Each entry in this table represents a VCL for which 4030 the atmVclRowStatus is `active', the atmVclConnKind is 4031 `pvc', and the atmVclOperStatus is other than `up'." 4032 INDEX { ifIndex, atmVclVpi, atmVclVci } 4033 ::= { atmCurrentlyFailingPVclTable 1 } 4035 AtmCurrentlyFailingPVclEntry ::= 4036 SEQUENCE { 4037 atmCurrentlyFailingPVclTimeStamp TimeStamp 4038 } 4040 atmCurrentlyFailingPVclTimeStamp OBJECT-TYPE 4041 SYNTAX TimeStamp 4042 MAX-ACCESS read-only 4043 STATUS current 4044 DESCRIPTION 4045 "The time at which this PVCL began to fail." 4046 ::= { atmCurrentlyFailingPVclEntry 1 } 4048 -- ATM PVC Traps 4050 atmPvcTraps OBJECT IDENTIFIER ::= { atm2MIBTraps 1 } 4052 atmPvcTrapsPrefix OBJECT IDENTIFIER ::= { atmPvcTraps 0 } 4054 atmIntfPvcFailuresTrap NOTIFICATION-TYPE 4055 OBJECTS { ifIndex, atmIntfPvcFailures, 4056 atmIntfCurrentlyFailingPVpls, 4057 atmIntfCurrentlyFailingPVcls } 4058 STATUS current 4059 DESCRIPTION 4061 draft Supplemental ATM Management Objects Mar 13, 1998 4063 "A notification indicating that one or more PVPLs or 4064 PVCLs on this interface has failed since the last 4065 atmPvcFailuresTrap was sent. If this trap has not been 4066 sent for the last atmIntfPvcNotificationInterval, then 4067 it will be sent on the next increment of 4068 atmIntfPvcFailures." 4069 ::= { atmPvcTrapsPrefix 1 } 4071 draft Supplemental ATM Management Objects Mar 13, 1998 4073 -- ************************************************ 4075 -- Conformance Information 4077 atm2MIBConformance OBJECT IDENTIFIER ::= {atm2MIB 2} 4079 atm2MIBGroups OBJECT IDENTIFIER 4080 ::= {atm2MIBConformance 1} 4082 atm2MIBCompliances OBJECT IDENTIFIER 4083 ::= {atm2MIBConformance 2} 4085 -- Compliance Statements 4087 atm2MIBCompliance MODULE-COMPLIANCE 4088 STATUS current 4089 DESCRIPTION 4090 "The compliance statement for SNMP entities which 4091 represent ATM interfaces. The compliance statements 4092 are used to determine if a particular group or object 4093 applies to hosts, networks/switches, or both." 4095 MODULE -- this module 4097 MANDATORY-GROUPS { atmSwitchServcHostGroup } 4099 -- Objects in the ATM Switch/Service/Host Group 4101 OBJECT atmVclStatTotalCellIns 4102 DESCRIPTION 4103 "This object is mandatory for systems that are 4104 supporting per VCC counters." 4106 OBJECT atmVclStatClp0CellIns 4107 DESCRIPTION 4108 "This object is mandatory for systems that are 4109 supporting per VCC counters." 4111 OBJECT atmVclStatTotalDiscards 4112 DESCRIPTION 4113 "This object is mandatory for systems that are 4114 supporting per VCC counters." 4116 draft Supplemental ATM Management Objects Mar 13, 1998 4118 OBJECT atmVclStatClp0Discards 4119 DESCRIPTION 4120 "This object is mandatory for systems that are 4121 supporting per VCC counters." 4123 OBJECT atmVclStatTotalCellOuts 4124 DESCRIPTION 4125 "This object is mandatory for systems that are 4126 supporting per VCC counters." 4128 OBJECT atmVclStatClp0CellOuts 4129 DESCRIPTION 4130 "This object is mandatory for systems that are 4131 supporting per VCC counters." 4133 OBJECT atmVclStatTaggedOuts 4134 DESCRIPTION 4135 "This object is mandatory for systems that are 4136 supporting per VCC counters." 4138 OBJECT atmVplStatTotalCellIns 4139 DESCRIPTION 4140 "This object is mandatory for systems that are 4141 supporting per VPC counters." 4143 OBJECT atmVplStatClp0CellIns 4144 DESCRIPTION 4145 "This object is mandatory for systems that are 4146 supporting per VPC counters." 4148 OBJECT atmVplStatTotalDiscards 4149 DESCRIPTION 4150 "This object is mandatory for systems that are 4151 supporting per VPC counters." 4153 OBJECT atmVplStatClp0Discards 4154 DESCRIPTION 4155 "This object is mandatory for systems that are 4156 supporting per VPC counters." 4158 OBJECT atmVplStatTotalCellOuts 4159 DESCRIPTION 4160 "This object is mandatory for systems that are 4162 draft Supplemental ATM Management Objects Mar 13, 1998 4164 supporting per VPC counters." 4166 OBJECT atmVplStatClp0CellOuts 4167 DESCRIPTION 4168 "This object is mandatory for systems that are 4169 supporting per VPC counters." 4171 OBJECT atmVplStatTaggedOuts 4172 DESCRIPTION 4173 "This object is mandatory for systems that are 4174 supporting per VPC counters." 4176 OBJECT atmVplLogicalPortDef 4177 MIN-ACCESS read-only 4178 DESCRIPTION 4179 "This object is mandatory for systems support ATM 4180 Logical Port interfaces." 4182 OBJECT atmIntfSigVccRxTrafficDescrIndex 4183 DESCRIPTION 4184 "This object is mandatory for systems that support 4185 negotiation of signalling VCC traffic parameters 4186 through ILMI." 4188 OBJECT atmIntfSigVccTxTrafficDescrIndex 4189 DESCRIPTION 4190 "This object is mandatory for systems that support 4191 negotiation of signalling VCC traffic parameters 4192 through ILMI." 4194 OBJECT atmCurrentlyFailingPVplTimeStamp 4195 DESCRIPTION 4196 "This object is optional." 4198 OBJECT atmCurrentlyFailingPVclTimeStamp 4199 DESCRIPTION 4200 "This object is optional." 4202 -- Objects in the ATM Switch/Service Group 4204 GROUP atmSwitchServcGroup 4205 DESCRIPTION 4206 "This group is mandatory for a Switch/Service that 4208 draft Supplemental ATM Management Objects Mar 13, 1998 4210 implements ATM interfaces." 4212 OBJECT atmIfRegAddrRowStatus 4213 MIN-ACCESS read-only 4214 DESCRIPTION 4215 "Write access is not required, and only one of the six 4216 enumerated values for the RowStatus textual convention 4217 need be supported, specifically: active(1)." 4219 OBJECT atmSigSupportClgPtyNumDel 4220 MIN-ACCESS read-only 4221 DESCRIPTION 4222 "Write access is not required. This parameter is 4223 required for ATM systems that support only a value of 4224 'disabled(2)' (i.e., the ATM systems does not support 4225 the feature associated with the parameter)." 4227 OBJECT atmSigSupportClgPtySubAddr 4228 MIN-ACCESS read-only 4229 DESCRIPTION 4230 "Write access is not required. This parameter is 4231 required for ATM systems that support only a value of 4232 'disabled(2)' (i.e., the ATM systems does not support 4233 the feature associated with the parameter)." 4235 OBJECT atmSigSupportCldPtySubAddr 4236 MIN-ACCESS read-only 4237 DESCRIPTION 4238 "Write access is not required. This parameter is 4239 required for ATM systems that support only a value of 4240 'disabled(2)' (i.e., the ATM systems does not support 4241 the feature associated with the parameter)." 4243 OBJECT atmSigSupportHiLyrInfo 4244 MIN-ACCESS read-only 4245 DESCRIPTION 4246 "Write access is not required. This parameter is 4247 required for ATM systems that support only a value of 4248 'disabled(2)' (i.e., the ATM systems does not support 4249 the feature associated with the parameter)." 4251 OBJECT atmSigSupportLoLyrInfo 4252 MIN-ACCESS read-only 4253 DESCRIPTION 4254 draft Supplemental ATM Management Objects Mar 13, 1998 4256 "Write access is not required. This parameter is 4257 required for ATM systems that support only a value of 4258 'disabled(2)' (i.e., the ATM systems does not support 4259 the feature associated with the parameter)." 4261 OBJECT atmSigSupportBlliRepeatInd 4262 MIN-ACCESS read-only 4263 DESCRIPTION 4264 "Write access is not required. This parameter is 4265 required for ATM systems that support only a value of 4266 'disabled(2)' (i.e., the ATM systems does not support 4267 the feature associated with the parameter)." 4269 OBJECT atmSigSupportAALInfo 4270 MIN-ACCESS read-only 4271 DESCRIPTION 4272 "Write access is not required. This parameter is 4273 required for ATM systems that support only a value of 4274 'disabled(2)' (i.e., the ATM systems does not support 4275 the feature associated with the parameter)." 4277 OBJECT atmSigSupportPrefCarrier 4278 MIN-ACCESS read-only 4279 DESCRIPTION 4280 "Write access is not required." 4282 OBJECT atmSvcVpCrossConnectRowStatus 4283 MIN-ACCESS read-only 4284 DESCRIPTION 4285 "Write access is not required, and only one of the six 4286 enumerated values for the RowStatus textual convention 4287 need be supported, specifically: active(1)" 4289 OBJECT atmSvcVcCrossConnectRowStatus 4290 MIN-ACCESS read-only 4291 DESCRIPTION 4292 "Write access is not required, and only two of the six 4293 enumerated values for the RowStatus textual convention 4294 need be supported, specifically: active(1)." 4296 -- Objects in the ATM Switch/Service Notifications Group 4298 GROUP atmSwitchServcNotifGroup 4299 draft Supplemental ATM Management Objects Mar 13, 1998 4301 DESCRIPTION 4302 "This group is optional for systems implementing 4303 support for an ATM Switch or an ATM Network Service." 4305 -- Objects in the ATM Switch Group 4307 GROUP atmSwitchGroup 4308 DESCRIPTION 4309 "This group is optional for a switch that implements 4310 ATM interfaces." 4312 -- Objects in the ATM Service Group 4314 GROUP atmServcGroup 4315 DESCRIPTION 4316 "This group is mandatory for systems implementing 4317 support for an ATM Network Service." 4319 -- Objects in the ATM Host Group 4321 GROUP atmHostGroup 4322 DESCRIPTION 4323 "This group is mandatory for a Host that implements ATM 4324 interfaces." 4326 OBJECT atmVclAddrType 4327 MIN-ACCESS read-only 4328 DESCRIPTION 4329 "Write access is not required." 4331 OBJECT atmVclAddrRowStatus 4332 MIN-ACCESS read-only 4333 DESCRIPTION 4334 "Write access is not required, and only one of the six 4335 enumerated values for the RowStatus textual convention 4336 need be supported, specifically: active(1)." 4338 OBJECT atmVclGenSigDescrIndex 4339 MIN-ACCESS read-only 4340 DESCRIPTION 4341 "Write access is not required." 4343 draft Supplemental ATM Management Objects Mar 13, 1998 4345 OBJECT atmSigDescrParamAalType 4346 MIN-ACCESS read-only 4347 DESCRIPTION 4348 "Write access is not required." 4350 OBJECT atmSigDescrParamAalSscsType 4351 MIN-ACCESS read-only 4352 DESCRIPTION 4353 "Write access is not required." 4355 OBJECT atmSigDescrParamBhliType 4356 MIN-ACCESS read-only 4357 DESCRIPTION 4358 "Write access is not required." 4360 OBJECT atmSigDescrParamBhliInfo 4361 MIN-ACCESS read-only 4362 DESCRIPTION 4363 "Write access is not required." 4365 OBJECT atmSigDescrParamBbcConnConf 4366 MIN-ACCESS read-only 4367 DESCRIPTION 4368 "Write access is not required." 4370 OBJECT atmSigDescrParamBlliLayer2 4371 MIN-ACCESS read-only 4372 DESCRIPTION 4373 "Write access is not required." 4375 OBJECT atmSigDescrParamBlliLayer3 4376 MIN-ACCESS read-only 4377 DESCRIPTION 4378 "Write access is not required." 4380 OBJECT atmSigDescrParamBlliPktSize 4381 MIN-ACCESS read-only 4382 DESCRIPTION 4383 "Write access is not required." 4385 OBJECT atmSigDescrParamBlliSnapId 4386 MIN-ACCESS read-only 4387 DESCRIPTION 4388 "Write access is not required." 4390 draft Supplemental ATM Management Objects Mar 13, 1998 4392 OBJECT atmSigDescrParamBlliOuiPid 4393 MIN-ACCESS read-only 4394 DESCRIPTION 4395 "Write access is not required." 4397 OBJECT atmSigDescrParamRowStatus 4398 MIN-ACCESS read-only 4399 DESCRIPTION 4400 "Write access is not required, and only one of the six 4401 enumerated values for the RowStatus textual convention 4402 need be supported, specifically: active(1)." 4404 ::= { atm2MIBCompliances 1 } 4406 -- ********************************************** 4408 -- Units of Conformance 4410 -- Mandatory for ATM hosts and switch/service providers 4412 atmSwitchServcHostGroup OBJECT-GROUP 4414 OBJECTS { 4415 atmSigSSCOPConEvents, 4416 atmSigSSCOPErrdPdus, 4417 atmSigDetectSetupAttempts, 4418 atmSigEmitSetupAttempts, 4419 atmSigDetectUnavailRoutes, 4420 atmSigEmitUnavailRoutes, 4421 atmSigDetectUnavailResrcs, 4422 atmSigEmitUnavailResrcs, 4423 atmSigDetectCldPtyEvents, 4424 atmSigEmitCldPtyEvents, 4425 atmSigDetectMsgErrors, 4426 atmSigEmitMsgErrors, 4427 atmSigDetectClgPtyEvents, 4428 atmSigEmitClgPtyEvents, 4429 atmSigDetectTimerExpireds, 4430 atmSigEmitTimerExpireds, 4431 atmSigDetectRestarts, 4432 atmSigEmitRestarts, 4433 atmSigInEstabls, 4434 atmSigOutEstabls, 4436 draft Supplemental ATM Management Objects Mar 13, 1998 4438 atmVclStatTotalCellIns, 4439 atmVclStatClp0CellIns, 4440 atmVclStatTotalDiscards, 4441 atmVclStatClp0Discards, 4442 atmVclStatTotalCellOuts, 4443 atmVclStatClp0CellOuts, 4444 atmVclStatTaggedOuts, 4445 atmVplStatTotalCellIns, 4446 atmVplStatClp0CellIns, 4447 atmVplStatTotalDiscards, 4448 atmVplStatClp0Discards, 4449 atmVplStatTotalCellOuts, 4450 atmVplStatClp0CellOuts, 4451 atmVplStatTaggedOuts, 4452 atmVplLogicalPortDef, 4453 atmVplLogicalPortIndex, 4454 atmInterfaceConfMaxSvpcVpi, 4455 atmInterfaceCurrentMaxSvpcVpi, 4456 atmInterfaceConfMaxSvccVpi, 4457 atmInterfaceCurrentMaxSvccVpi, 4458 atmInterfaceConfMinSvccVci, 4459 atmInterfaceCurrentMinSvccVci, 4460 atmIntfSigVccRxTrafficDescrIndex, 4461 atmIntfSigVccTxTrafficDescrIndex, 4462 atmIntfPvcFailures, 4463 atmIntfCurrentlyFailingPVpls, 4464 atmIntfCurrentlyFailingPVcls, 4465 atmIntfPvcNotificationInterval, 4466 atmIntfPvcFailuresTrapEnable, 4467 atmIntfConfigType, 4468 atmIntfActualType, 4469 atmIntfConfigSide, 4470 atmIntfActualSide, 4471 atmIntfIlmiAdminStatus, 4472 atmIntfIlmiOperStatus, 4473 atmIntfIlmiFsmState, 4474 atmIntfIlmiEstablishConPollIntvl, 4475 atmIntfIlmiCheckConPollIntvl, 4476 atmIntfIlmiConPollInactFactor, 4477 atmIntfIlmiPublicPrivateIndctr, 4478 atmCurrentlyFailingPVplTimeStamp, 4479 atmCurrentlyFailingPVclTimeStamp 4480 } 4481 STATUS current 4483 draft Supplemental ATM Management Objects Mar 13, 1998 4485 DESCRIPTION 4486 "A collection of objects providing information 4487 for a Switch/Service/Host that implements 4488 ATM interfaces." 4489 ::= { atm2MIBGroups 1 } 4491 atmSwitchServcGroup OBJECT-GROUP 4493 OBJECTS { 4494 atmIlmiSrvcRegATMAddress, 4495 atmIlmiSrvcRegParm1, 4496 atmIlmiSrvcRegRowStatus, 4497 atmIlmiNetPrefixRowStatus, 4498 atmSigSupportClgPtyNumDel, 4499 atmSigSupportClgPtySubAddr, 4500 atmSigSupportCldPtySubAddr, 4501 atmSigSupportHiLyrInfo, 4502 atmSigSupportLoLyrInfo, 4503 atmSigSupportBlliRepeatInd, 4504 atmSigSupportAALInfo, 4505 atmSigSupportPrefCarrier, 4506 atmSvcVpCrossConnectCreationTime, 4507 atmSvcVpCrossConnectRowStatus, 4508 atmSvcVcCrossConnectCreationTime, 4509 atmSvcVcCrossConnectRowStatus, 4510 atmIfRegAddrAddressSource, 4511 atmIfRegAddrOrgScope, 4512 atmIfRegAddrRowStatus} 4513 STATUS current 4514 DESCRIPTION 4515 "A collection of objects providing information 4516 for a Switch/Service that implements ATM interfaces." 4517 ::= { atm2MIBGroups 2 } 4519 atmSwitchServcNotifGroup NOTIFICATION-GROUP 4521 NOTIFICATIONS { 4522 atmIntfPvcFailuresTrap } 4523 STATUS current 4524 DESCRIPTION 4525 "A collection of notifications providing information 4526 for a Switch/Service that implements ATM interfaces." 4528 draft Supplemental ATM Management Objects Mar 13, 1998 4530 ::= { atm2MIBGroups 3 } 4532 atmSwitchGroup OBJECT-GROUP 4534 OBJECTS { 4535 atmSwitchAddressAddress, 4536 atmSwitchAddressRowStatus } 4537 STATUS current 4538 DESCRIPTION 4539 "A collection of objects providing information 4540 for an ATM switch." 4541 ::= { atm2MIBGroups 4 } 4543 atmServcGroup OBJECT-GROUP 4545 OBJECTS { 4546 atmVpCrossConnectUserName, 4547 atmVpCrossConnectProviderName, 4548 atmVcCrossConnectUserName, 4549 atmVcCrossConnectProviderName } 4550 STATUS current 4551 DESCRIPTION 4552 "A collection of objects providing information 4553 for an ATM Network Service." 4554 ::= { atm2MIBGroups 5 } 4556 atmHostGroup OBJECT-GROUP 4558 OBJECTS { 4559 atmAal5VclInPkts, 4560 atmAal5VclOutPkts, 4561 atmAal5VclInOctets, 4562 atmAal5VclOutOctets, 4563 atmVclAddrType, 4564 atmVclAddrRowStatus, 4565 atmAddrVclAddrType, 4566 atmVclGenSigDescrIndex, 4567 atmSigDescrParamAalType, 4568 atmSigDescrParamAalSscsType, 4569 atmSigDescrParamBhliType, 4570 atmSigDescrParamBhliInfo, 4572 draft Supplemental ATM Management Objects Mar 13, 1998 4574 atmSigDescrParamBbcConnConf, 4575 atmSigDescrParamBlliLayer2, 4576 atmSigDescrParamBlliLayer3, 4577 atmSigDescrParamBlliPktSize, 4578 atmSigDescrParamBlliSnapId, 4579 atmSigDescrParamBlliOuiPid, 4580 atmSigDescrParamRowStatus} 4581 STATUS current 4582 DESCRIPTION 4583 "A collection of objects providing information 4584 for a Host that implements ATM interfaces." 4585 ::= { atm2MIBGroups 6 } 4587 END 4588 draft Supplemental ATM Management Objects Mar 13, 1998 4590 11. Acknowledgments 4592 This document is a product of the AToMMIB Working Group. 4594 draft Supplemental ATM Management Objects Mar 13, 1998 4596 12. References 4598 [1] Tesink, K., "Definitions of Managed Objects for ATM 4599 Management", RFC ???? (Internet-Draft , Bell Communications Research, 4601 January 8, 1997. 4603 [2] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 4604 "Structure of Management Information for Version 2 of the 4605 Simple Network Management Protocol (SNMPv2)", RFC 1902, 4606 SNMP Research, Inc., Cisco Systems, Inc., Dover Beach 4607 Consulting, Inc., International Network Services, January 4608 1996. 4610 [3] McCloghrie, K., and M. Rose, Editors, "Management 4611 Information Base for Network Management of TCP/IP-based 4612 internets: MIB-II", STD 17, RFC 1213, Hughes LAN Systems, 4613 Performance Systems International, March 1991. 4615 [5] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 4616 "Protocol Operations for Version 2 of the Simple Network 4617 Management Protocol (SNMPv2)", RFC 1905, SNMP Research, 4618 Inc., Cisco Systems, Inc., Dover Beach Consulting, Inc., 4619 International Network Services, January 1996. 4621 [6] McCloghrie, K. and F. Kastenholz, "The Interfaces Group 4622 MIB using SMIv2", RFC 2233, Cisco Systems, FTP Software, 4623 November 1997. 4625 [7] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 4626 "Textual Conventions for Version 2 of the Simple Network 4627 Management Protocol (SNMPv2)", RFC 1903, SNMP Research, 4628 Inc., Cisco Systems, Inc., Dover Beach Consulting, Inc., 4629 International Network Services, January 1996. 4631 [8] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 4632 "Conformance Statements for SNMPv2", RFC 1904, SNMP 4633 Research, Inc., Cisco Systems, Inc., Dover Beach 4634 Consulting, Inc., International Network Services, January 4635 1996. 4637 [9] ATM Forum, "ATM User-Network Interface Specification, 4638 Version 3.0 (UNI 3.0)", September 1993. 4640 draft Supplemental ATM Management Objects Mar 13, 1998 4642 [10] ATM Forum, "ATM User-Network Interface Specification, 4643 Version 3.1 (UNI 3.1)", September 1994. 4645 [11] ITU-T Recommendation Q.2931, "Broadband Integrated 4646 Services Digital Network (B-ISDN) - Digital Subscriber 4647 Signalling System No. 2 (DSS2) - User-Network Interface 4648 (UNI) Layer 3 Specification for Basic Call/Connection 4649 Control", February 1995. 4651 [12] ATM Forum, "Private Network-Network Interface 4652 Specification, Version 1.0 (PNNI 1.0)", af-pnni-0055.000, 4653 March 1996. 4655 [13] ITU-T Recommendation Q.2110, "Broadband Integrated 4656 Services Digital Network (B-ISDN) - ATM Adaptation Layer 4657 - Service Specific Connection Oriented Protocol (SSCOP) 4658 Specification", July 1994. 4660 [14] ATM Forum, "LAN Emulation Client Management 4661 Specification, Version 1.0", af-lane-0038.000, September 4662 1995. 4664 [15] Brown, T., Tesink, K., "Definitions of Managed Objects 4665 for SMDS Interfaces using SMIv2", RFC 1694, Bell 4666 Communications Research, August 1994. 4668 [16] ITU-T Recommendation Q.2961, "Broadband Integrated 4669 Services Digital Network (B-ISDN) - Digital Subscriber 4670 Signalling System No. 2 (DSS2) - Additional Traffic 4671 Parameters", October 1995. 4673 [17] ITU-T Recommendation Q.2971, "Broadband Integrated 4674 Services Digital Network (B-ISDN) - Digital Subscriber 4675 Signalling System No. 2 (DSS2) - User-Network Interface 4676 Layer 3 Specification for Point-to-Multipoint 4677 Call/Connection Control", October 1995. 4679 [18] ATM Forum, "Interim Inter-Switch Signaling Protocol 4680 (IISP) Specification, Version 1.0", af-pnni-0026.000, 4681 December 1994. 4683 [19] ATM Forum, "BISDN Inter Carrier Interface (B-ICI) 4684 Specification, Version 2.0 (Integrated)", af-bici- 4685 0013.003, December 1995. 4687 draft Supplemental ATM Management Objects Mar 13, 1998 4689 [20] ITU-T Recommendation I.610, "B-ISDN Operation and 4690 Maintenance Principles and Functions", November 1995. 4692 [21] ATM Forum, "Integrated Local Management Interface (ILMI) 4693 Specification, Version 4.0", af-ilmi-0065.000, September 4694 1996. 4696 [22] ATM Forum, "ATM User-Network Interface (UNI) Signalling 4697 Specification, Version 4.0", af-sig-0061.000, July 1996. 4699 draft Supplemental ATM Management Objects Mar 13, 1998 4701 13. Security Considerations 4703 Security issues are not discussed in this memo. 4705 14. Authors' Addresses 4707 Faye Ly 4708 3Com Networks Inc. 4709 Santa Clara, CA 95052 4710 Phone: (408) 764-6576 4711 EMail: fayely@3com.com 4713 Michael Noto 4714 Network Equipment Technologies 4715 800 Saginaw Drive RM 21.1.111 4716 Redwood City, CA 94063 4717 Phone: (415) 569-7134 4718 EMail: mike_noto@net.com 4720 Andrew Smith 4721 Extreme Networks 4722 1601 S. De Anza Blvd, #220 4723 Cupertino, CA 95014 4724 Phone: (408) 342-0985 4725 EMail: ansmith@extremenetworks.com 4727 Ethan Mickey Spiegel 4728 Cisco Systems 4729 170 W. Tasman Drive 4730 San Jose, CA 95134-1706 4731 Phone: (408) 526-6408 4732 EMail: mspiegel@cisco.com 4734 Kaj Tesink 4735 Bell Communications Research 4736 Room 1A-427 4737 331 Newman Springs Road 4738 P.O. Box 7020 4739 Red Bank, NJ 07701-7020 4740 Phone: (908) 758-5254 4741 EMail: kaj@cc.bellcore.com 4743 draft Supplemental ATM Management Objects Mar 13, 1998 4745 Table of Contents 4747 1 Status of this Memo ................................... 1 4748 2 Introduction .......................................... 3 4749 3 Change Log ............................................ 3 4750 4 The SNMPv2 Network Management Framework ............... 6 4751 5 Object Definitions .................................... 6 4752 6 Overview .............................................. 6 4753 6.1 Background .......................................... 7 4754 6.2 Important Definitions ............................... 7 4755 6.3 Supported Functions ................................. 9 4756 6.3.1 ATM SVC VC Cross-Connect Table .................... 10 4757 6.3.2 ATM SVC VP Cross-Connect Table .................... 11 4758 6.3.3 ATM Interface Signalling Statistics Table ......... 12 4759 6.3.4 ATM Signalling Capability Support ................. 12 4760 6.3.5 Signalling Descriptor Parameter Table ............. 13 4761 6.3.6 ATM Interface Registered Address Table ............ 14 4762 6.3.7 ATM VPI/VCI to Address Mapping Table .............. 14 4763 6.3.8 ATM Address to VPI/VCI Mapping Table .............. 14 4764 6.3.9 ATM VPL Statistics Table .......................... 15 4765 6.3.10 ATM VPL Logical Port Table ....................... 16 4766 6.3.10.1 ATM Logical Port Interface ..................... 16 4767 6.3.10.2 How to create an ATM Logical Port interface 4768 .................................................... 17 4769 6.3.11 ATM VCL Statistics Table ......................... 19 4770 6.3.12 ATM VC General Information Table ................. 20 4771 6.3.13 ATM Interface Configuration Extension Table ...... 20 4772 6.3.14 ATM ILMI Service Registry Table .................. 22 4773 6.3.15 ILMI Network Prefix Table ........................ 23 4774 6.3.16 ATM Switch Address Table ......................... 23 4775 7 Network and User Addresses ............................ 24 4776 8 Configuration of VPLs, VCLs, and Cross-Connects ....... 24 4777 9 ATM Related Trap Support .............................. 24 4778 10 Definitions .......................................... 26 4779 11 Acknowledgments ...................................... 107 4780 12 References ........................................... 108 4781 13 Security Considerations .............................. 111 4782 14 Authors' Addresses ................................... 111