idnits 2.17.1 draft-ietf-atommib-atm2-19.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Looks like you're using RFC 2026 boilerplate. This must be updated to follow RFC 3978/3979, as updated by RFC 4748. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- ** The document seems to lack a 1id_guidelines paragraph about 6 months document validity -- however, there's a paragraph with a matching beginning. Boilerplate error? ** The document seems to lack a 1id_guidelines paragraph about the list of current Internet-Drafts. ** The document seems to lack a 1id_guidelines paragraph about the list of Shadow Directories. == 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 Introduction section. (A line matching the expected section header was found, but with an unexpected indentation: ' 2.1 Background' ) ** The document seems to lack a Security Considerations section. (A line matching the expected section header was found, but with an unexpected indentation: ' 8. 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.) ** There are 292 instances of too long lines in the document, the longest one being 8 characters in excess of 72. ** The abstract seems to contain references ([RFC1155], [RFC2573], [RFC1906], [RFC2574], [RFC1157], [RFC2575], [4], [RFC2580], [RFC2026], [5], [24], [RFC1212], [RFC2863], [RFC2028], [25], [30], [RFC2578], [26], [31], [RFC2579], [RFC1694], [27], [RFC1901], [RFC1215], [RFC2493], [RFC2558], [28], [29], [34], [RFC2570], [RFC3410], [RFC2571], [RFC2496], [RFC2515], [RFC2572], [RFC1905]), which it shouldn't. Please replace those with straight textual mentions of the documents in question. ** The document seems to lack a both a reference to RFC 2119 and the recommended RFC 2119 boilerplate, even if it appears to use RFC 2119 keywords. RFC 2119 keyword, line 4292: '... It is RECOMMENDED that implement...' RFC 2119 keyword, line 4298: '... RECOMMENDED. Instead, it is REC...' Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year == Line 2698 has weird spacing: '...smitted by th...' == Line 2849 has weird spacing: '...smitted by th...' -- 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 (January 3, 2003) is 7756 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? '24' on line 822 looks like a reference -- Missing reference section? 'RFC3410' on line 4293 looks like a reference -- Missing reference section? 'RFC2578' on line 4200 looks like a reference -- Missing reference section? 'RFC2579' on line 4205 looks like a reference -- Missing reference section? 'RFC2580' on line 4209 looks like a reference -- Missing reference section? '5' on line 80 looks like a reference -- Missing reference section? '4' on line 813 looks like a reference -- Missing reference section? '31' on line 80 looks like a reference -- Missing reference section? '30' on line 81 looks like a reference -- Missing reference section? '28' on line 83 looks like a reference -- Missing reference section? '27' on line 83 looks like a reference -- Missing reference section? '34' on line 87 looks like a reference -- Missing reference section? '25' on line 574 looks like a reference -- Missing reference section? '26' on line 574 looks like a reference -- Missing reference section? '29' on line 659 looks like a reference -- Missing reference section? 'RFC2515' on line 4134 looks like a reference -- Missing reference section? 'RFC1694' on line 4150 looks like a reference -- Missing reference section? 'RFC2558' on line 4157 looks like a reference -- Missing reference section? 'RFC2496' on line 4160 looks like a reference -- Missing reference section? 'RFC1905' on line 4163 looks like a reference -- Missing reference section? 'RFC1906' on line 4167 looks like a reference -- Missing reference section? 'RFC2026' on line 4171 looks like a reference -- Missing reference section? 'RFC2028' on line 4174 looks like a reference -- Missing reference section? 'RFC2493' on line 4177 looks like a reference -- Missing reference section? 'RFC2571' on line 4181 looks like a reference -- Missing reference section? 'RFC2572' on line 4185 looks like a reference -- Missing reference section? 'RFC2573' on line 4189 looks like a reference -- Missing reference section? 'RFC2574' on line 4192 looks like a reference -- Missing reference section? 'RFC2575' on line 4196 looks like a reference -- Missing reference section? 'RFC2863' on line 4213 looks like a reference -- Missing reference section? 'RFC1157' on line 4218 looks like a reference -- Missing reference section? 'RFC2570' on line 4222 looks like a reference -- Missing reference section? 'RFC1155' on line 4226 looks like a reference -- Missing reference section? 'RFC1212' on line 4230 looks like a reference -- Missing reference section? 'RFC1215' on line 4233 looks like a reference -- Missing reference section? 'RFC1901' on line 4236 looks like a reference Summary: 10 errors (**), 0 flaws (~~), 4 warnings (==), 38 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 INTERNET-DRAFT Supplemental ATM Managed Objects Faye Ly 3 Pedestal Networks 4 Michael Noto 5 Cisco Systems 6 Andrew Smith 7 Allegro Networks 8 Ethan Mickey Spiegel 9 Cisco Systems 10 Kaj Tesink 11 Telcordia Technologies 12 January 3, 2003 14 Definitions of Supplemental Managed Objects 15 for ATM Interface 17 January 3, 2003 19 draft-ietf-atommib-atm2-19.txt 21 Status of this Memo 23 This document is an Internet-Draft and is in full conformance with all 24 provisions of Section 10 of RFC2026. 26 Internet-Drafts are working documents of the Internet Engineering Task 27 Force (IETF), its areas, and its working groups. Note that other 28 groups may also distribute working documents as Internet-Drafts. 30 Internet-Drafts are draft documents valid for a maximum of six months 31 and may be updated, replaced, or obsoleted by other documents at any 32 time. It is inappropriate to use Internet-Drafts as reference 33 material or to cite them other than as ``work in progress.'' 35 Copyright Notice 37 Copyright (C) The Internet Society (2003). All Rights Reserved. 39 Abstract 41 This memo defines objects used for managing ATM-based interfaces, devices, 42 and services in addition to those defined in the ATM-MIB [24], to 43 provide additional support for the management of: 45 - ATM Switched Virtual Connections (SVCs) 46 - ATM Permanent Virtual Connections (PVCs) 48 1. The Internet-Standard Management Framework 50 For a detailed overview of the documents that describe the current 51 Internet-Standard Management Framework, please refer to section 7 of 52 RFC 3410 [RFC3410]. 54 Managed objects are accessed via a virtual information store, termed 55 the Management Information Base or MIB. MIB objects are generally 56 accessed through the Simple Network Management Protocol (SNMP). 57 Objects in the MIB are defined using the mechanisms defined in the 58 Structure of Management Information (SMI). This memo specifies a MIB 59 module that is compliant to the SMIv2, which is described in STD 58, 60 RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 61 [RFC2580]. 63 2. Overview 65 The purpose of this memo is to provide additional capabilities, not found 66 in the ATM-MIB [24], which are needed to manage ATM interfaces. This memo 67 addresses the following areas: 69 - ATM Switch Support 70 - ATM Service Support 71 - ATM Host Support 73 In addition, this memo also provides ATM trap support. 75 2.1 Background 77 In addition to the MIB module defined in this memo, other MIB modules 78 are necessary to manage ATM interfaces, links and cross-connects. 79 Examples include MIB II for general system and interface 80 management (RFC 1907 [5] and RFC 2863 [4]), the DS3 (RFC 2496 [31]) 81 or SONET MIBs (RFC 2558 [30]) for management of SONET and DS3 physical 82 interfaces, and, as appropriate, MIB modules for applications that make 83 use of ATM, such as SMDS [28] and LAN Emulation [27]. These MIB modules 84 are outside the scope of this specification. 86 This MIB module also requires the use of the ATM-MIB module defined in 87 [24] and ATM-specific textual conventions defined in [34]. 89 ATM Endpoint applications such as ATM LAN Emulation or Classical 90 IP-over-ATM Clients and Servers use ATM to establish 91 SVC/PVC connections for exchanging control and data information. 92 The agents of these ATM applications must provide the network 93 manager with information on the SVC/PVCs in use and which 94 applications are using them. The information can be made 95 generic so as to apply to all ATM applications. This memo defines 96 extensions to the ATM-MIB [24] in order to support this. 98 The current specification of this supplemental ATM2-MIB is based on 99 SNMPv2 SMI. 101 2.2 Important Definitions 103 The following terms are defined here and used throughout this MIB: 104 - Virtual Path Link (VPL) 105 - Virtual Path Connection (VPC) 106 - Virtual Path Segment (VP Segment) 107 - Virtual Channel Link (VCL) 108 - Virtual Channel Connection (VCC) 109 - Virtual Channel Segment (VC Segment). 111 The figures on the next page show how these terms apply in typical ATM 112 network topologies. Additional terms relevant to this MIB are defined 113 and illustrated in the ATM Terminology section 3 of [24]. 115 _____ _______ _______ _______ _____ 116 | |____| |____| |____| |____| | 117 |Host1| |SwitchA| |SwitchB| |SwitchC| |Host2| 118 | |____| |____| |____| |____| | 119 |_____| |_______| |_______| |_______| |_____| 121 |<-->| |<-->| 122 Virtual Path Link Virtual Path Link 124 |<----------------------------------------->| 125 Virtual Path Connection 126 (between Host1 and Host2) 128 |<--------------->| 129 Virtual Path Segment 130 (between SwitchA and SwitchC) 132 Figure 1: Examples of Virtual Path Links, Virtual Path 133 Connection, and Virtual Path Segment 135 _____ _______ _______ _______ _____ 136 | |____| |____| |____| |____| | 137 |Host1|----|SwitchA|----|SwitchB|----|SwitchC|----|Host2| 138 | |____| |____| |____| |____| | 139 |_____| |_______| |_______| |_______| |_____| 141 |<-->| |<-->| 142 Virtual Channel Link Virtual Channel Link 144 |<----------------------------------------->| 145 Virtual Channel Connection 146 (between Host1 and Host2) 148 |<--------------->| 149 Virtual Channel Segment 150 (between SwitchA and SwitchC) 152 Figure 2: Examples of Virtual Channel Links, Virtual 153 Channel Connection, and Virtual Channel Segment 155 3. Conventions used in the MIB 157 3.1 Structure 159 The managed ATM objects are arranged as follows: 161 Table Host Switch Service 162 _____________________________________________________ 163 atmSvcVcCrossConnectTable | | Y | Y | 164 atmSvcVpCrossConnectTable | | Y | Y | 166 atmSigStatTable | Y | Y | Y | 167 atmSigSupportTable | | Y | Y | 168 atmSigDescrParamTable | Y | | | 170 atmIfRegisteredAddrTable | | Y | Y | 171 atmVclAddrTable | Y | | | 172 atmAddrVclTable | Y | | | 174 atmVplStatTable | Y | Y | Y | 175 atmVplLogicalPortTable | Y | Y | Y | 177 atmVclStatTable | Y | Y | Y | 178 atmAal5VclStatTable | Y | | | 179 atmVclGenTable | Y | | | 180 atmInterfaceExtTable | Y | Y | Y | 182 atmIlmiSrvcRegTable | | Y | Y | 183 atmIlmiNetworkPrefixTable | | Y | Y | 184 atmSwitchAddressTable | | Y | | 186 atmVpCrossConnectXTable | | | Y | 187 atmVcCrossConnectXTable | | | Y | 189 atmCurrentlyFailingPVplTable | Y | Y | Y | 190 atmCurrentlyFailingPVclTable | Y | Y | Y | 192 Table 1: MIB structure 194 3.1.1 ATM SVC VP Cross-Connect Table 196 This table provides the SVC VP Cross-Connect (SVPC) information. The 197 equivalent PVC VP Cross-Connect table is defined in [24]. This table 198 also includes cross-connect information for Soft PVPs. 200 This table contains configuration and state information of all SVC VP 201 point-to-point, point-to-multipoint, or multipoint-to-multipoint VP 202 cross-connects. 204 This table has read-only access and can be used to monitor the 205 cross-connects which connect the VPLs together in an ATM switch or 206 network. The atmSvcVpCrossConnectIndex is used to associate the 207 related SVC VPLs that are cross-connected together. The 208 atmSvcVpCrossConnectRowStatus object has read-write access to allow 209 for tear-down. 211 The ATM SVC VP Cross-Connect Table models each bi-directional Switched 212 Virtual Circuit (SVC) VP cross-connect as a set of entries in the 213 atmSvcVpCrossConnectTable. A point-to-point VPC cross-connect is 214 modeled as one entry; a point-to-multipoint (N leafs) VPC cross-connect 215 as N entries in this table; and a multipoint-to-multipoint (N parties) 216 VPC cross-connect as N(N-1)/2 entries in this table. In the latter 217 cases, all the N (or N(N-1)/2) entries are associated with a single VPC 218 cross-connect by having the same value of atmSvcVpCrossConnectIndex. 220 _________________________________________ 221 | | 222 Low | ATM Switch or Network | High 223 port| | port 224 _____|>> from low to high VPC traffic flow >>|______ 225 |<< from high to low VPC traffic flow <<| 226 |_______________________________________| 228 Figure 3: VPC Cross-Connect Model 230 The terms low and high are chosen to represent numerical ordering of 231 the two interfaces associated with a VPC cross-connect. That is, the 232 ATM interface with the lower value of ifIndex is termed 'low', while 233 the other ATM interface associated with the VPC cross-connect is 234 termed 'high'. 236 3.1.2 ATM SVC VC Cross-Connect Table 238 This table provides the SVC Cross-Connect (SVCC) information. The 239 equivalent PVC VC Cross-Connect table is defined in [24]. This table 240 also includes cross-connect information for Soft PVCs. 242 This table is used to model a bi-directional 243 point-to-point, point-to-multipoint or 244 multipoint-to-multipoint SVC VC cross-connect. 246 This table has read-only access and is used 247 to monitor the cross-connects which connect 248 the VCLs together in an ATM switch 249 or network that belong to a VC connection. The 250 atmSvcVcCrossConnectIndex is used to associate 251 the related SVC VCLs that are cross-connected together. 252 The atmSvcVcCrossConnectRowStatus object 253 has read-write access to allow for tear-down. 255 The ATM SVC VC Cross-Connect Table models each bi-directional 256 Switched Virtual Circuit (SVC) VC cross-connect as a set of entries 257 in the atmSvcVcCrossConnectTable. A point-to-point VC cross-connect 258 is modeled as one entry; a point-to-multipoint (N leafs) VC 259 cross-connect as N entries in this table; and a multipoint-to-multipoint 260 (N parties) VPC cross-connect as N(N-1)/2 entries in this table. 261 In the latter cases, all the N (or N(N-1)/2) entries are associated 262 with a single VPC cross-connect by having the same value of 263 atmSvcVcCrossConnectIndex. 265 ______________________________________ 266 | | 267 Low | ATM Switch or Network | High 268 port| | port 269 _____|>> from low to high VC traffic flow >>|______ 270 |<< from high to low VC traffic flow <<| 271 |______________________________________| 273 Figure 4: VC Cross-Connect Model 275 The terms low and high are chosen to represent numerical ordering of 276 the two interfaces associated with a VPC cross-connect. That is, the 277 ATM interface with the lower value of ifIndex is termed 'low', while 278 the other ATM interface associated with the VPC cross-connect is 279 termed 'high'. 281 5.1.3 ATM Interface Signalling Statistics Table 283 This table provides statistical information of the signalling entity. 284 A signalling entity can be deployed over an ATM interface as defined 285 in the atmInterfaceConfTable [24], a logical ATM interface defined in 286 section 5.1.10.1 in this document, or a proprietary virtual interface 287 as described in the atmInterfaceExtTable. To monitor the signalling 288 entity, a few counters are provided. They are defined as: 290 atmSigSSCOPConEvents 291 atmSigSSCOPErrdPdus 292 atmSigDetectSetupAttempts 293 atmSigEmitSetupAttempts 294 atmSigDetectUnavailRoutes 295 atmSigEmitUnavailRoutes 296 atmSigDetectUnavailResrcs 297 atmSigEmitUnavailResrcs 298 atmSigDetectCldPtyEvents 299 atmSigEmitCldPtyEvents 300 atmSigDetectMsgErrors 301 atmSigEmitMsgErrors 302 atmSigDetectClgPtyEvents 303 atmSigEmitClgPtyEvents 304 atmSigDetectTimerExpireds 305 atmSigEmitTimerExpireds 306 atmSigDetectRestarts 307 atmSigEmitRestarts 308 atmSigInEstabls 309 atmSigOutEstabls 311 3.1.4 ATM Signalling Capability Support 312 A number of Information Elements may or may not be supported by ATM 313 switches or ATM Services. Hence, for trouble isolation it is important 314 to keep track which particular Information Elements are supported. The 315 corresponding group of objects must be supported by switches or services 316 supporting SVCs, and indicate whether the following Information Elements 317 are enabled/disabled: 319 1) Calling party number 321 2) Calling party subaddress 323 3) Called party subaddress 325 4) Broadband high layer information 327 5) Broadband low layer information 329 5) Broadband Repeat Indicator 331 7) AAL parameters 333 The last parameter, Preferred Carrier Pre-Subscription, identifies the 334 carrier to which intercarrier calls originated from this interface are 335 routed when transit network selection information is not provided by 336 the calling party. 338 5.1.5 Signalling Descriptor Parameter Table 340 This table extends the ATM VCL table of the 341 ATM-MIB [24] to include all other necessary signalling information as 342 specified in the ATM Forum UNI Specifications [25] and [26]. 343 A user can create an entry with all signalling parameters 344 and later use that entry to specify the signalling 345 characteristics of SVCs. 347 Some of the signalling parameters, such as the AAL5 parameters information 348 element, are reflected in the VCL and VPL tables, and this table only 349 contains the remaining AAL5 parameters. 351 Signalling attributes can be grouped into following categories: 353 1) ATM Adaptation Layer Parameters 355 Information in this group is captured in the 356 ATM Signalling Descriptor Parameter Table defined 357 in this memo. Please refer to section 5.4.5.5 of 358 [25] and [26]. 360 2) Broadband High Layer Information 362 Information in this group is captured by the 363 ATM Signalling Descriptor Parameter Table defined 364 in this memo. Please refer to section 5.4.5.8 of 365 [25] and [26]. 367 3) Broadband Low Layer Information 369 Information in this group is captured by the 370 ATM Signalling Descriptor Parameter Table defined 371 in this memo. Please refer to section 5.4.5.9 of 372 [25] and [26]. 374 3.1.6 ATM Interface Registered Address Table 376 This table contains a list of ATM addresses that can be used for calls 377 to and from a given interface by a switch or service. The ATM addresses 378 are either registered by the endsystem via ILMI or statically configured. 379 This table does not expose PNNI reachability information. This table 380 only applies to switches and network services. See also Section 5.2. 382 3.1.7 ATM VPI/VCI to Address Mapping Table 384 In the atmVclAddrTable, the object atmVclAddrAddr can 385 either be an ATM Local Address or an ATM Remote Address which represent 386 the two endpoint addresses of a VCL. ATM Local Address 387 identifies the local endpoint of the VCL represented by this 388 agent. The ATM Remote address represents the address of 389 the ATM application at the other end of the VCL. 391 5.1.8 ATM Address to VPI/VCI Mapping Table 393 This table provides an alternative way to retrieve 394 the atmVclTable. This table can be used to retrieve the 395 indexing to the atmVclTable by an ATM address. 397 3.1.9 ATM VPL Statistics Table 399 The atmVplStatTable includes per-VPL cell counters. The VPL cell counters 400 count the valid ATM cells. The valid ATM cells include the user and OAM 401 cells but exclude the physical layer (e.g., idle cells) and unassigned cells. 402 Cells coming into an ATM managed system are counted differently with the 403 high Cell Loss Priority (CLP=0) or low Cell Loss Priority (CLP=1). 404 The cells are tagged, passed or discarded 405 depending on the incoming CLP value and the policed cell rate by the 406 "traffic policing" entity in the ATM managed system. Refer to 407 [25] and [26] for a description of the traffic policing. 409 In the switch where the traffic policing is not supported, cells are 410 passed or discarded depending on the bandwidth and buffering capacity 411 of the switching fabric. 412 The Output Tagged Cells counter, in this case, is always zero. 414 _______________ 415 | ATM Managed | 416 Input | System | Output 417 CLP=0 cells| | CLP=0 cells 418 ---------->| |-----------> 419 CLP=1 cells| (traffic | CLP=1 cells 420 ---------->| policing |-----------> 421 | entity) | Tagged cells (CLP=1) 422 |_____________|-----------> 423 |Discard | Discard 424 |CLP=0 | CLP=1 425 |cells | cells 426 | | 427 V V 429 Figure 5: ATM Cell Counters per VPL 431 In this table, cells coming into and out of the managed ATM system are 432 counted as the total number of cells and the cells with the CLP=0. The 433 CLP=1 counter is derived by subtracting CLP=0 cells from the total cells. 434 In addition, cells that are tagged on the output are also counted. The 435 output CLP=1 cells equals the total cells out count minus both the 436 CLP=0 cells and the tagged cells. 438 3.1.10 ATM VPL Logical Port Table 440 The ATM VPL Logical Port Table includes all ATM logical port interface 441 configuration information. 443 3.1.10.1 ATM Logical Port Interface 445 The interface type "ATM Logical Port" (ifType=80) is defined to allow 446 the representation of a VP Tunnel, which is a VPL used as a trunk 447 connection (most likely between devices that are not physically 448 adjacent), providing for multiplexing and demultiplexing of VCs on 449 the VP. Figure 6 illustrates such a VP Tunnel. 451 Note: the "ATM Logical Port" interface is more of a logical port, 452 compared with an interface of type "ATM" which is more of a physical 453 port that provides for the transport of many VP and VC connections 454 between adjacent devices. 456 <------VP Tunnel------> 457 ATM Switch A ATM Switch B 458 ------------ ----------- 459 |ATM |_____________|ATM | 460 |X-Connect | . |X-Connect | 461 VCL1 |Point | VPL1 . VPL2 |Point | VCL4 462 O---------|----X-----|----- . -----|----X-----|-----O 463 | X-----|----- . -----|----X | 464 | | |_____________| | | 465 ------------ ------------ 466 | VCL2 | VCL3 467 O O 469 Figure 6: Virtual Path Tunnel 471 In Figure 6, a VP tunnel (denoted as VPL1 by Switch A, and as VPL2 by 472 Switch B) is used to connect VCL1 with VCL4 and VCL2 with VCL3. 473 Figure 6 shows only one VP tunnel, but there can be multiple VP tunnels 474 over the same physical interface. 476 A particularly useful VP tunnel scenario is tunneling across a public 477 network that does not support signalling. In Figure 6 above, assume 478 Switches A and B are private switches that signal over the VP to set 479 up connections transparently through the public network. The public 480 network would just transport a PVC VP between the two switches. 482 Because the VP Tunnel constitutes an interface between two ATM devices 483 that are not necessarily physically adjacent, most of the management 484 information pertaining to the interface may differ for the tunnel, 485 including: 487 - active VPI/VCI fields (the tunnel may be a subset 488 of the parent interface). 489 - maximum number of VCCs 490 - configured VCCs 491 - ILMI VPI/VCI values 492 - ATM address type 493 - ATM administrative address 494 - received/transmitted cells. 496 3.1.10.2 How to create an ATM Logical Port interface 498 On ATM devices supporting VP tunnels, the ATM Logical Port Interface Table 499 can be used to create VP tunnels. To create an ATM Logical Port interface 500 via SNMP: 502 - Create a VPL (e.g., VPI=a on an existing ATM interface 503 which has ifIndex=x) in the atmVplTable. 505 - Set the object atmVplLogicalPortDef to isLogicalIf. 506 A new row in the ifTable is then created by the agent, 507 with ifIndex=y, to represent the ATM Logical Port 508 interface. The object atmVplLogicalPortIndex is also 509 set to y by the agent to represent the ifIndex value of 510 the ATM Logical Port interface. 512 - The ifEntry values are set for the ATM Logical 513 Port interface (ifIndex=y) as discussed in RFC 514 2515, with the following exceptions: 515 * ifType - a new enumerated value of atmLogical(80) 516 was added to IANAifType, specifying an "ATM 517 Logical Port" interface. 518 * ifSpeed - The total bandwidth in bits per 519 second for use by the ATM layer. Computed 520 from the traffic descriptor for the VPL. 521 * ifOperStatus - determined hierarchically, 522 depending on the state of the physical 523 atm-cell layer interface beneath it, 524 and the ILMI on the VP. 525 * ifInOctets, ifOutOctets - support of 526 these objects is not mandatory for ATM 527 Logical Port interfaces. 528 * ifInErrors - always zero, HEC errors are 529 specified for the atm cell-layer interface 530 beneath it. 531 * ifInUnknownProtos - always zero, errors 532 are specified for the atm cell-layer 533 interface beneath it. 535 - The atmInterfaceConfEntry values are set and reported 536 as discussed in [24], with the following exceptions: 537 * atmInterfaceMaxVpcs - 0. 538 * atmInterfaceConfVpcs - 0. 539 * atmInterfaceIlmiVpi - VPI of the VP tunnel. 541 - The atmInterfaceExtEntry values are set and reported 542 as follows: 543 * atmInterfaceConfMaxSvpcVpi - VPI of the VP tunnel, 544 although VPCs cannot be setup on a VP tunnel. 545 * atmInterfaceCurrentMaxSvpcVpi - VPI of VP tunnel, 546 although VPCs cannot be setup on a VP tunnel. 547 * atmInterfaceConfMaxSvccVpi - VPI of the VP tunnel. 548 * atmInterfaceCurrentMaxSvccVpi - VPI of VP tunnel. 549 * atmIntfPvcFailures - Includes failures of PVCLs 550 within the VP tunnel, but not of the PVPL itself, 551 since those are reported on the atm(37) interface. 552 * atmIntfCurrentlyFailingPVpls - 0. 553 * atmIntfPvcFailuresTrapEnable - Enables traps for 554 PVCL failures within the VP tunnel, but not for 555 the PVPL itself, since the latter are generated on 556 behalf of the atm(37) interface. 558 - An entry is created in the ifStackTable, with 559 values: ifStackHigherLayer=y, ifStackLowerLayer=x. 561 - VCLs defined on the VP tunnel are indexed by 562 ifIndex=y, VPI=a, VCI. 564 3.1.11 ATM VCL Statistics Table 566 The atmVclStatTable includes per-VCL cell counters. The VCL cell counters 567 count the valid ATM cells. The valid ATM cells include the user and OAM 568 cells but exclude the physical layer (e.g., idle cells) and unassigned cells. 569 Cells coming into an ATM managed system are counted differently with the 570 high Cell Loss Priority (CLP=0) or low Cell Loss Priority (CLP=1). 571 The cells are tagged, passed or discarded 572 depending on the incoming CLP value and the policed cell rate by the 573 "traffic policing" entity in the ATM managed system. Refer to 574 [25] and [26] for the description of the traffic policing. 576 In a switch where the traffic policing is not supported, cells are 577 passed or discarded depending on the bandwidth and buffering capacity 578 of the switching fabric. 579 The Output Tagged Cells counter, in this case, is always zero. 581 _______________ 582 | ATM Managed | 583 Input | System | Output 584 CLP=0 cells| | CLP=0 cells 585 ---------->| |-----------> 586 CLP=1 cells| (traffic | CLP=1 cells 587 ---------->| policing |-----------> 588 | entity) | Tagged cells (CLP=1) 589 |_____________|-----------> 590 |Discard | Discard 591 |CLP=0 | CLP=1 592 |cells | cells 593 | | 594 V V 596 Figure 7: ATM Cell Counters per VCL 598 In this table, cells coming into and out of the managed ATM system 599 are counted as the total number of cells and the cells with the CLP=0. 600 The CLP=1 counter is derived by subtracting CLP=0 cells from the 601 total cells. In addition, cells that are tagged on the output are 602 also counted. The output CLP=1 cells equals the total cells out 603 count minus both the CLP=0 cells and the tagged cells. 605 3.1.12 ATM VC General Information Table 607 This table contains the general information for each VC. It provides 608 an index to the atmSigDescrParamTable defined in this MIB. This table 609 is an extension to the atmVclTable defined in the ATM-MIB [24]. 611 3.1.13 ATM Interface Configuration Extension Table 613 The ATM Interface Configuration Extension Table contains ATM interface 614 information that supplements the atmInterfaceConfTable defined in [24]. 615 It includes the configuration information of the interface type (i.e., 616 connection setup procedures) and ILMI. 618 A network manager can configure the interface to run a specific type of 619 connection setup procedures (i.e., protocol and version) such as ITU-T 620 DSS2, ATM Forum UNI 3.1, PNNI 1.0 or BICI 2.0. It can also dictate the 621 role of the managed entity as one side of the interface. For example, 622 if an interface is configured to run ATM Forum UNI 3.1, the managed 623 entity has to be told to run as either the network side or the user 624 side of the UNI. 626 The objects atmIntfConfigType and atmIntfConfigSide are used for 627 configuration and the objects atmIntfActualType and atmIntfActualSide 628 are used for reading back the actual interface protocol and version. 630 The following table describes all the valid combinations of 631 configuration of the interface type and side. Note that the value 632 N/A meaning not applicable, should be set to the value other(1) when 633 used. 635 atmIntfConfigType atmIntfConfigSide 636 ----------------- ----------------- 637 autoConfig N/A 638 ituDss2 user/network 639 atmfUni3Dot0 user/network 640 atmfUni3Dot1 user/network 641 atmfUni4Dot0 user/network 642 atmfIispUni3Dot0 user/network 643 atmfIispUni3Dot1 user/network 644 atmfIispUni4Dot0 user/network 645 atmfPnni1Dot0 N/A 646 atmfBici2Dot0 N/A 647 atmfUniPvcOnly user/network 648 atmfNniPvcOnly N/A 650 When the value of the object atmIntfConfigType is configured to 651 autoConfig(2), the interface type is determined via the ATM Forum 652 ILMI auto-configuration procedures [29]. There is no need to set 653 the interface side since it should be a derived value. The PNNI 654 and BICI interfaces are always symmetric so setting the interface 655 side is also not necessary. 657 This table also includes the configured and negotiated maximum VPI 658 value per ATM interface, and the configured and negotiated minimum VCI 659 value per ATM interface. Refer to [29] Sections 8.2.3.8 through 660 8.2.3.10 for a detailed description. 662 The following figure provides an example how the current minimum VCI 663 values are derived from the configured minimum VCI values and the 664 neighboring minimum VCI values: 666 +--------+ +--------+ +--------+ 667 | ATM | ifA ifB | ATM | ifC ifD | ATM | 668 | Device |--------------| Device |--------------| Device | 669 +--------+ +--------+ +--------+ 671 ifA: Configured Min SVCC VCI = 32 (configured) 672 Current Min SVCC VCI = 40 (negotiated) 674 ifB: Configured Min SVCC VCI = 40 (configured) 675 Current Min SVCC VCI = 40 (negotiated) 677 ifC: Configured Min SVCC VCI = 32 (configured) 678 Current Min SVCC VCI = 32 (negotiated) 680 ifD: Configured Min SVCC VCI = 32 (configured) 681 Current Min SVCC VCI = 32 (negotiated) 683 Between ifA and ifB, the maximum of the two vales for 684 atmInterfaceConfMinSvccVci is 40, so both interfaces set 685 their atmInterfaceCurrentMinSvccVci values to 40. On 686 the other hand, since ifC and ifD both are configured 687 with atmInterfaceConfMinSvccVci values of 32, they set 688 their atmInterfaceCurrentMinSvccVci values to 32. 690 Figure 8: Examples of configured vs. negotiated ILMI values 692 3.1.14 ATM ILMI Service Registry Table 694 This table contains information used by the switch/service to inform ATM 695 hosts of the location of ATM network services such as the LAN Emulation 696 Configuration Server (LECS), the ATM Name Server (ANS), the ATMARP 697 Server, the Multicast Address Resolution Server (MARS), and the NHRP 698 Server (NHS). 699 Entries in this table are exported to adjacent devices via ILMI over either 700 all or a few user selected ATM interfaces. 702 As an example, let's assume that: 703 - An ATM switch X has three interfaces if1, if2 and if3. 704 - There are two ATM network services offered, a1.a2...aN and 705 b1.b2...bN, where a1.a2...aN is an object identifier used to 706 identify the first service, and b1.b2...bN is the object 707 identifier for the other service. 708 - The first service is available at the ATM address 'a'. 709 - The second service is available at the ATM address 'b'. 710 - The first service can be used by any device connecting to 711 the switch X. 712 - The second service can be used only by devices that connect 713 to interfaces if1 and if3 on switch X. 715 +------------------+ +------------------+ 716 |service a1.a2...aN| |service b1.b2...bN| 717 | | | | 718 | ATM address = a | | ATM address = b | 719 +--------+---------+ +--------+---------+ 720 | | 721 | | 722 +--------+-----------------------+---------+ 723 | ATM NETWORK | 724 +-----------------+------------------------+ 725 | 726 | 727 +-------------+ 728 | switch X | 729 +-+----+----+-+ 730 | | | 731 | | | 732 if1 if2 if3 (interfaces) 734 Figure 9: ATM topology with registered services 736 The table for switch X will contain three entries: 737 - one entry for the "a1.a2...aN", implicitly available to any 738 devices on switch X. 739 - two entries for the "b1.b2...bN" (one for each interface 740 where this service can be explicitly used). 742 The content of the table is: 743 - Service Identifier: a1.a2...aN b1.b2...bN b1.b2...bN 744 - ATM address: a b b 745 - Arbitrary index: m n p 746 - Available interface: 0 1 3 748 where the Service Identifier values a1.a2...aN and b1.b2...bN 749 are represented by atmIlmiSrvcRegServiceID, the ATM addresses 750 a and b are represented by atmIlmiSrvcRegATMAddress, the values 751 m, n, and p are arbitrary non-zero integer parameters (necessary 752 in this example to differentiate the two entries for b1.b2...bN 753 that are both available at the ATM address 'b') represented by 754 atmIlmiSrvcRegAddressIndex, and the available interfaces are 755 represented by atmIlmiSrvcRegIndex, where the special value 0 756 indicates any ATM interface. 758 When querying the ILMI service registry table, through the 759 ILMI protocol: 760 - the device attached to interface if1 will obtain the 761 address a and b. 763 - the device attached to interface if2 will obtain the 764 address a only. 765 - the device attached to interface if3 will obtain the 766 address a and b. 768 3.1.15 ILMI Network Prefix Table 770 A table specifying per-interface network prefix(es) supplied by the 771 network side of the UNI during ILMI address registration. When no 772 network prefixes are specified for a particular interface, one or 773 more network prefixes based on the switch address(es) may be used 774 for ILMI address registration. 776 3.1.16 ATM Switch Address Table 778 This table contains one or more ATM endsystem addresses on a per-switch 779 basis. These addresses are used to identify the switch. When no ILMI 780 network prefixes are configured for certain interfaces, network prefixes 781 based on the switch address(es) may be used for ILMI address registration. 783 3.1.17 AAL5 per-VCC Statistics Table 785 This table contains the AAL5 statistics for the VCCs. 787 3.1.18 ATM VP Cross-Connect Extension Table 789 This table extends the atmVpCrossConnectTable defined in ATM-MIB [24]. 791 3.1.19 ATM VC Cross-Connect Extension Table 793 This table extends the atmVcCrossConnectTable defined in ATM-MIB [24]. 795 3.1.20 Currently Failing PVPL Table 797 This table contains all the PVPLs that are in trouble. 799 3.1.21 Currently Failing PVCL Table 801 This table contains all the PVCLs that are in trouble. 803 3.1.22 Leaf Initiated Join Counter support 805 Two counter objects are added to count the number of leaf intiated 806 setup requests and setup failures. 808 3.2 Network and User Addresses 809 At the user side of a given ATM UNI interface there may be an address, 810 "ifPhysAddress", to identify the interface. In addition, there may be 811 several other addresses which can be used to originate and receive calls. 812 These other addresses that are used to receive calls are listed in the 813 "ifRcvAddrTable" defined in RFC 2863 [4]. The registered addresses on 814 the network side are listed in the ATM Registered Address Table. The 815 ATM Registered Address Table is supported by switches and network 816 services. It is not supported by hosts. 818 3.3 Configuration of VPLs, VCLs, and Cross-Connects 820 The ATM Managed Objects needed to support the configuration of VPLs, 821 VCLs, and Cross-Connects of the Permanent VPLs and VCLs are defined in 822 the ATM-MIB [24]. Cross-Connects of the Switched VPLs and VCLs are 823 defined in this memo. 825 3.4 ATM-related Trap Support 827 Traps are defined to detect changes in the status of permanent VPLs 828 and VCLs. The current up/down status of each permanent VPL or VCL 829 is indicated by the atmVplOperStatus or atmVclOperStatus object, 830 respectively. Several tables and objects and one trap are defined 831 in order to help network managers quickly and efficiently detect 832 changes in the status of permanent virtual links. Through use of 833 these tables, objects, and traps, the time consuming and resource 834 intensive task of continuously polling each row in the entire 835 atmVplTable and atmVclTable can be avoided. 837 The atmIntfPvcFailures counter and the atmIntfCurrentlyFailingPVpls 838 and atmIntfCurrentlyFailingPVcls gauges provide a quick means of 839 determining the status of all PVPLs and PVCLs on an interface. The 840 atmCurrentlyFailingPVplTable and the atmCurrentlyFailingPVclTable 841 list all of the problematic PVPLs and PVCLs, respectively, allowing 842 them to be quickly identified. 844 The atmIntfPvcFailuresTrap is generated just after a PVPL or PVCL on 845 a particular interface leaves the `up' operational state. Managers can 846 then determine which PVPLs and/or PVCLs are failing by reading the 847 atmCurrentlyFailingPVplTable and the atmCurrentlyFailingPVclTable. 848 Generation of the atmIntfPvcFailuresTrap is rate limited by suppressing 849 all traps that would occur within atmIntfPvcNotificationInterval of a 850 previous trap for the same interface. Managers should continuously poll 851 the tables and objects mentioned above for at least this amount of time 852 in order to keep up with the state of the network. 854 4. Conformance and Compliance 856 See the conformance and compliance statements within the information module. 858 5. Definitions 860 ATM2-MIB DEFINITIONS ::= BEGIN 862 IMPORTS 863 MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, 864 Gauge32, Counter32, Integer32 865 FROM SNMPv2-SMI 866 TruthValue, RowStatus, TimeStamp 867 FROM SNMPv2-TC 868 MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP 869 FROM SNMPv2-CONF 870 SnmpAdminString 871 FROM SNMP-FRAMEWORK-MIB 872 InterfaceIndex, InterfaceIndexOrZero, ifIndex 873 FROM IF-MIB 874 atmMIBObjects, atmInterfaceConfEntry, 875 atmVplEntry, atmVplVpi, 876 atmVclEntry, atmVclVpi, atmVclVci, 877 atmVpCrossConnectEntry, atmVcCrossConnectEntry 878 FROM ATM-MIB 879 AtmAddr, AtmSigDescrParamIndex, 880 AtmInterfaceType, AtmIlmiNetworkPrefix, 881 AtmVcIdentifier, AtmVpIdentifier, 882 AtmTrafficDescrParamIndex 883 FROM ATM-TC-MIB; 885 atm2MIB MODULE-IDENTITY 886 LAST-UPDATED "200304131200Z" 887 ORGANIZATION "IETF AToMMIB Working Group" 888 CONTACT-INFO 889 "AToMMIB WG 890 http://www.ietf.org/html.charters/atommib-charter.html 891 Editors: 892 Faye Ly 893 Postal: Pedestal Networks 894 6503 Dumbarton Circle 895 Fremont, CA 94555 896 USA 897 Tel: +1 510 896 2908 898 E-Mail: faye@pedestalnetworks.com 900 Michael Noto 901 Postal: Cisco Systems 902 170 W. Tasman Drive 903 San Jose, CA 95134-1706 904 USA 906 E-mail: mnoto@cisco.com 908 Andrew Smith 909 Postal: Allegro Networks 910 6399 San Ignacio Ave. 911 San Jose, CA 95119 912 USA 913 Fax: +1 415 345 1827 914 E-Mail: andrew@allegronetworks.com 916 Ethan Mickey Spiegel 917 Postal: Cisco Systems 918 170 W. Tasman Drive 919 San Jose, CA 95134-1706 920 USA 921 Tel: +1 408 526 6408 922 Fax: +1 408 526 6488 923 E-Mail: mspiegel@cisco.com 925 Kaj Tesink 926 Postal: Telcordia Technologies 927 331 Newman Springs Road 928 Red Bank, NJ 07701 929 USA 930 Tel: +1 732 758 5254 931 Fax: +1 732 758 2269 932 E-mail: kaj@research.telcordia.com" 933 DESCRIPTION 934 "Copyright (C) The Internet Society (2003). This version of 935 this MIB module is part of RFC xxxx; see the RFC itself for 936 full legal notices. 938 This MIB Module is a supplement to the ATM-MIB 939 defined in RFC 2515." 940 REVISION "200304131200Z" 941 DESCRIPTION 942 "Initial version of this MIB, published as RFC xxxx." 943 -- xxxx to be assigned by RFC-Editor 944 ::= { atmMIBObjects 14 } 946 -- ******** NOTE TO THE RFC EDITOR **************** 947 -- Please fill out xxxx above with the RFC number of 948 -- this RFC and remove this note 950 atm2MIBObjects OBJECT IDENTIFIER ::= {atm2MIB 1} 952 atm2MIBTraps OBJECT IDENTIFIER ::= {atm2MIB 2} 953 -- This ATM2-MIB Module consists of the following tables, 954 -- plus ATM trap support: 955 -- 1. atmSvcVpCrossConnectTable 956 -- 2. atmSvcVcCrossConnectTable 957 -- 3. atmSigStatTable 958 -- 4. atmSigSupportTable 959 -- 5. atmSigDescrParamTable 960 -- 6. atmIfRegisteredAddrTable 961 -- 7. atmVclAddrTable 962 -- 8. atmAddrVclTable 963 -- 9. atmVplStatTable 964 -- 10. atmVplLogicalPortTable 965 -- 11. atmVclStatTable 966 -- 12. atmAal5VclStatTable 967 -- 13. atmVclGenTable 968 -- 14. atmInterfaceExtTable 969 -- 15. atmIlmiSrvcRegTable 970 -- 16. atmIlmiNetworkPrefixTable 971 -- 17. atmSwitchAddressTable 972 -- 18. atmVpCrossConnectXTable 973 -- 19. atmVcCrossConnectXTable 974 -- 20. atmCurrentlyFailingPVplTable 975 -- 21. atmCurrentlyFailingPVclTable 977 -- 1. ATM VPL SVC Cross-Connect Table 979 atmSvcVpCrossConnectTable OBJECT-TYPE 980 SYNTAX SEQUENCE OF 981 AtmSvcVpCrossConnectEntry 982 MAX-ACCESS not-accessible 984 STATUS current 985 DESCRIPTION 986 "The ATM SVPC Cross-Connect table. A 987 bi-directional VP cross-connect between two 988 switched VPLs is modeled as one entry in this 989 table. A Soft PVPC cross-connect, between a 990 soft permanent VPL and a switched VPL, is 991 also modeled as one entry in this table." 992 ::= { atm2MIBObjects 1 } 994 atmSvcVpCrossConnectEntry OBJECT-TYPE 995 SYNTAX AtmSvcVpCrossConnectEntry 996 MAX-ACCESS not-accessible 997 STATUS current 998 DESCRIPTION 999 "An entry in the ATM SVPC Cross-Connect table. 1001 This entry is used to model a bi-directional 1002 ATM VP cross-connect between two VPLs." 1003 INDEX { atmSvcVpCrossConnectIndex, 1004 atmSvcVpCrossConnectLowIfIndex, 1005 atmSvcVpCrossConnectLowVpi, 1006 atmSvcVpCrossConnectHighIfIndex, 1007 atmSvcVpCrossConnectHighVpi } 1008 ::= { atmSvcVpCrossConnectTable 1 } 1010 AtmSvcVpCrossConnectEntry ::= SEQUENCE { 1011 atmSvcVpCrossConnectIndex INTEGER, 1012 atmSvcVpCrossConnectLowIfIndex InterfaceIndex, 1013 atmSvcVpCrossConnectLowVpi AtmVpIdentifier, 1014 atmSvcVpCrossConnectHighIfIndex InterfaceIndex, 1015 atmSvcVpCrossConnectHighVpi AtmVpIdentifier, 1016 atmSvcVpCrossConnectCreationTime TimeStamp, 1017 atmSvcVpCrossConnectRowStatus RowStatus 1018 } 1020 atmSvcVpCrossConnectIndex OBJECT-TYPE 1021 SYNTAX INTEGER (1..2147483647) 1022 MAX-ACCESS not-accessible 1023 STATUS current 1024 DESCRIPTION 1025 "A unique value to identify this SVPC 1026 cross-connect. For each VP associated 1027 with this cross-connect, the agent reports 1028 this cross-connect index value in the 1029 atmVplCrossConnectIdentifer attribute of the 1030 corresponding atmVplTable entries." 1031 ::= { atmSvcVpCrossConnectEntry 1 } 1033 atmSvcVpCrossConnectLowIfIndex OBJECT-TYPE 1034 SYNTAX InterfaceIndex 1035 MAX-ACCESS not-accessible 1036 STATUS current 1037 DESCRIPTION 1038 "The value of this object is equal to the 1039 ifIndex value of the ATM interface port for this 1040 SVPC cross-connect. The term low implies 1041 that this ATM interface has the numerically lower 1042 ifIndex value than the other ATM interface 1043 identified in the same atmSvcVpCrossConnectEntry." 1044 ::= { atmSvcVpCrossConnectEntry 2 } 1046 atmSvcVpCrossConnectLowVpi OBJECT-TYPE 1047 SYNTAX AtmVpIdentifier 1048 MAX-ACCESS not-accessible 1049 STATUS current 1050 DESCRIPTION 1051 "The value of this object is equal to the VPI 1052 value associated with the SVPC cross-connect 1053 at the ATM interface that is identified by 1054 atmSvcVpCrossConnectLowIfIndex. The VPI value 1055 cannot exceed the number supported by the 1056 atmInterfaceCurrentMaxSvpcVpi at the low ATM interface 1057 port." 1058 ::= { atmSvcVpCrossConnectEntry 3 } 1060 atmSvcVpCrossConnectHighIfIndex OBJECT-TYPE 1061 SYNTAX InterfaceIndex 1062 MAX-ACCESS not-accessible 1063 STATUS current 1064 DESCRIPTION 1065 "The value of this object is equal to the 1066 ifIndex value of the ATM interface port for 1067 this SVC VP cross-connect. The term high 1068 implies that this ATM interface has the 1069 numerically higher ifIndex value than the 1070 other ATM interface identified in the same 1071 atmSvcVpCrossConnectEntry." 1072 ::= { atmSvcVpCrossConnectEntry 4 } 1074 atmSvcVpCrossConnectHighVpi OBJECT-TYPE 1075 SYNTAX AtmVpIdentifier 1076 MAX-ACCESS not-accessible 1077 STATUS current 1078 DESCRIPTION 1079 "The value of this object is equal to the VPI 1080 value associated with the SVPC cross-connect 1082 at the ATM interface that is identified by 1083 atmSvcVpCrossConnectHighIfIndex. The VPI value 1084 cannot exceed the number supported by the 1085 atmInterfaceCurrentMaxSvpcVpi at the high ATM interface 1086 port." 1087 ::= { atmSvcVpCrossConnectEntry 5 } 1089 atmSvcVpCrossConnectCreationTime OBJECT-TYPE 1090 SYNTAX TimeStamp 1091 MAX-ACCESS read-only 1092 STATUS current 1093 DESCRIPTION 1094 "The value of the sysUpTime object 1095 at the time this bi-directional SVPC 1096 cross-connect was created. If the current 1097 state was entered prior to the last 1098 re-initialization of the agent, then this 1099 object contains a zero value." 1100 ::= { atmSvcVpCrossConnectEntry 6 } 1102 atmSvcVpCrossConnectRowStatus OBJECT-TYPE 1103 SYNTAX RowStatus 1104 MAX-ACCESS read-write 1105 STATUS current 1106 DESCRIPTION 1107 "This object is used to delete rows in the 1108 atmSvcVpCrossConnectTable." 1109 ::= { atmSvcVpCrossConnectEntry 7 } 1111 -- 2. ATM VCL SVC Cross-Connect Table 1113 atmSvcVcCrossConnectTable OBJECT-TYPE 1114 SYNTAX SEQUENCE OF AtmSvcVcCrossConnectEntry 1115 MAX-ACCESS not-accessible 1116 STATUS current 1117 DESCRIPTION 1118 "The ATM SVCC Cross-Connect table. A 1119 bi-directional VC cross-connect between two 1120 switched VCLs is modeled as one entry in 1121 this table. A Soft PVCC cross-connect, 1122 between a soft permanent VCL and a switched 1123 VCL, is also modeled as one entry in this 1124 table." 1125 ::= { atm2MIBObjects 2 } 1127 atmSvcVcCrossConnectEntry OBJECT-TYPE 1128 SYNTAX AtmSvcVcCrossConnectEntry 1129 MAX-ACCESS not-accessible 1130 STATUS current 1131 DESCRIPTION 1132 "An entry in the ATM SVCC Cross-Connect table. 1133 This entry is used to model a bi-directional ATM 1134 VC cross-connect between two VCLs." 1135 INDEX { atmSvcVcCrossConnectIndex, 1136 atmSvcVcCrossConnectLowIfIndex, 1137 atmSvcVcCrossConnectLowVpi, 1138 atmSvcVcCrossConnectLowVci, 1139 atmSvcVcCrossConnectHighIfIndex, 1140 atmSvcVcCrossConnectHighVpi, 1141 atmSvcVcCrossConnectHighVci } 1142 ::= { atmSvcVcCrossConnectTable 1 } 1144 AtmSvcVcCrossConnectEntry ::= SEQUENCE { 1145 atmSvcVcCrossConnectIndex INTEGER, 1146 atmSvcVcCrossConnectLowIfIndex InterfaceIndex, 1147 atmSvcVcCrossConnectLowVpi AtmVpIdentifier, 1148 atmSvcVcCrossConnectLowVci AtmVcIdentifier, 1149 atmSvcVcCrossConnectHighIfIndex InterfaceIndex, 1150 atmSvcVcCrossConnectHighVpi AtmVpIdentifier, 1151 atmSvcVcCrossConnectHighVci AtmVcIdentifier, 1152 atmSvcVcCrossConnectCreationTime TimeStamp, 1153 atmSvcVcCrossConnectRowStatus RowStatus 1154 } 1156 atmSvcVcCrossConnectIndex OBJECT-TYPE 1157 SYNTAX INTEGER (1..2147483647) 1158 MAX-ACCESS not-accessible 1159 STATUS current 1160 DESCRIPTION 1161 "A unique value to identify this SVCC cross-connect. 1162 For each VP associated with this cross-connect, the 1163 agent reports this cross-connect index value in the 1164 atmVclCrossConnectIdentifier attribute of the 1165 corresponding atmVplTable entries." 1166 ::= { atmSvcVcCrossConnectEntry 1 } 1168 atmSvcVcCrossConnectLowIfIndex OBJECT-TYPE 1169 SYNTAX InterfaceIndex 1170 MAX-ACCESS not-accessible 1171 STATUS current 1172 DESCRIPTION 1173 "The value of this object is equal to the 1174 ifIndex value of the ATM interface port for this 1175 SVCC cross-connect. The term low implies that 1177 this ATM interface has the numerically lower 1178 ifIndex value than the other ATM interface 1179 identified in the same atmSvcVcCrossConnectEntry." 1180 ::= { atmSvcVcCrossConnectEntry 2 } 1182 atmSvcVcCrossConnectLowVpi OBJECT-TYPE 1183 SYNTAX AtmVpIdentifier 1184 MAX-ACCESS not-accessible 1185 STATUS current 1186 DESCRIPTION 1187 "The value of this object is equal to the VPI 1188 value associated with the SVCC cross-connect 1189 at the ATM interface that is identified by 1190 atmSvcVcCrossConnectLowIfIndex. The VPI value 1191 cannot exceed the number supported by the 1192 atmInterfaceCurrentMaxSvccVpi at the low ATM interface 1193 port." 1194 ::= { atmSvcVcCrossConnectEntry 3 } 1196 atmSvcVcCrossConnectLowVci OBJECT-TYPE 1197 SYNTAX AtmVcIdentifier 1198 MAX-ACCESS not-accessible 1199 STATUS current 1200 DESCRIPTION 1201 "The value of this object is equal to the VCI 1202 value associated with the SVCC cross-connect 1203 at the ATM interface that is identified by 1204 atmSvcVcCrossConnectLowIfIndex. The VCI value 1205 cannot exceed the number supported by the 1206 atmInterfaceCurrentMaxSvccVci at the low ATM interface 1207 port." 1208 ::= { atmSvcVcCrossConnectEntry 4 } 1210 atmSvcVcCrossConnectHighIfIndex OBJECT-TYPE 1211 SYNTAX InterfaceIndex 1212 MAX-ACCESS not-accessible 1213 STATUS current 1214 DESCRIPTION 1215 "The value of this object is equal to the 1216 ifIndex value for the ATM interface port for 1217 this SVCC cross-connect. The term high implies 1218 that this ATM interface has the numerically 1219 higher ifIndex value than the other ATM interface 1220 identified in the same atmSvcVcCrossConnectEntry." 1221 ::= { atmSvcVcCrossConnectEntry 5 } 1223 atmSvcVcCrossConnectHighVpi OBJECT-TYPE 1224 SYNTAX AtmVpIdentifier 1226 MAX-ACCESS not-accessible 1227 STATUS current 1228 DESCRIPTION 1229 "The value of this object is equal to the VPI 1230 value associated with the SVCC cross-connect 1231 at the ATM interface that is identified by 1232 atmSvcVcCrossConnectHighIfIndex. The VPI value 1233 cannot exceed the number supported by the 1234 atmInterfaceCurrentMaxSvccVpi at the high ATM interface 1235 port." 1236 ::= { atmSvcVcCrossConnectEntry 6 } 1238 atmSvcVcCrossConnectHighVci OBJECT-TYPE 1239 SYNTAX AtmVcIdentifier 1240 MAX-ACCESS not-accessible 1241 STATUS current 1242 DESCRIPTION 1243 "The value of this object is equal to the VCI 1244 value associated with the SVCC cross-connect 1245 at the ATM interface that is identified by 1246 atmSvcVcCrossConnectHighIfIndex. The VCI value 1247 cannot exceed the number supported by the 1248 atmInterfaceMaxVciBits at the high ATM interface 1249 port." 1250 ::= { atmSvcVcCrossConnectEntry 7 } 1252 atmSvcVcCrossConnectCreationTime OBJECT-TYPE 1253 SYNTAX TimeStamp 1254 MAX-ACCESS read-only 1255 STATUS current 1256 DESCRIPTION 1257 "The value of the sysUpTime object 1258 at the time this bi-directional SVCC 1259 cross-connect was created. If the current 1260 state was entered prior to the last 1261 re-initialization of the agent, then this 1262 object contains a zero value." 1263 ::= { atmSvcVcCrossConnectEntry 8 } 1265 atmSvcVcCrossConnectRowStatus OBJECT-TYPE 1266 SYNTAX RowStatus 1267 MAX-ACCESS read-write 1268 STATUS current 1269 DESCRIPTION 1270 "This object is used to delete rows in the 1271 atmSvcVcCrossConnectTable." 1272 ::= { atmSvcVcCrossConnectEntry 9 } 1274 -- 3. ATM Interface Signalling Statistics Table -- 1276 atmSigStatTable OBJECT-TYPE 1277 SYNTAX SEQUENCE OF AtmSigStatEntry 1278 MAX-ACCESS not-accessible 1279 STATUS current 1280 DESCRIPTION 1281 "This table contains ATM interface signalling 1282 statistics, one entry per ATM signalling 1283 interface." 1284 ::= { atm2MIBObjects 3 } 1286 atmSigStatEntry OBJECT-TYPE 1287 SYNTAX AtmSigStatEntry 1288 MAX-ACCESS not-accessible 1289 STATUS current 1290 DESCRIPTION 1291 "This list contains signalling statistics variables." 1292 INDEX { ifIndex } 1293 ::= { atmSigStatTable 1} 1295 AtmSigStatEntry ::= SEQUENCE { 1296 atmSigSSCOPConEvents Counter32, 1297 atmSigSSCOPErrdPdus Counter32, 1298 atmSigDetectSetupAttempts Counter32, 1299 atmSigEmitSetupAttempts Counter32, 1300 atmSigDetectUnavailRoutes Counter32, 1301 atmSigEmitUnavailRoutes Counter32, 1302 atmSigDetectUnavailResrcs Counter32, 1303 atmSigEmitUnavailResrcs Counter32, 1304 atmSigDetectCldPtyEvents Counter32, 1305 atmSigEmitCldPtyEvents Counter32, 1306 atmSigDetectMsgErrors Counter32, 1307 atmSigEmitMsgErrors Counter32, 1308 atmSigDetectClgPtyEvents Counter32, 1309 atmSigEmitClgPtyEvents Counter32, 1310 atmSigDetectTimerExpireds Counter32, 1311 atmSigEmitTimerExpireds Counter32, 1312 atmSigDetectRestarts Counter32, 1313 atmSigEmitRestarts Counter32, 1314 atmSigInEstabls Counter32, 1315 atmSigOutEstabls Counter32 1316 } 1318 atmSigSSCOPConEvents OBJECT-TYPE 1319 SYNTAX Counter32 1320 MAX-ACCESS read-only 1321 STATUS current 1323 DESCRIPTION 1324 "SSCOP Connection Events Counter. This counter counts 1325 the sum of the following errors: 1327 1) SSCOP Connection Disconnect Counter 1329 The abnormal occurrence of this event is 1330 characterized by the expiry of Timer_NO_RESPONSE. 1331 (This event is communicated to the layer management 1332 with MAA-ERROR code P. See ITU-T Q.2110.) 1334 2) SSCOP Connection Initiation Failure 1336 This condition indicates the inability to establish 1337 an SSCOP connection. This event occurs whenever the 1338 number of expiries of the connection control timer 1339 (Timer_CC) equals or exceeds the MaxCC, or upon 1340 receipt of a connection reject message BGREJ PDU. 1341 (This event is communicated to layer management with 1342 MAA-ERROR code O. See ITU-T Q.2110.) 1344 3) SSCOP Connection Re-Establ/Resynch 1346 This event occurs upon receipt of a BGN PDU or 1347 RS PDU." 1348 REFERENCE 1349 "ITU-T Recommendation Q.2110, Broadband 1350 Integrated Services Digital Network 1351 (B-ISDN) - ATM Adaptation Layer - Service 1352 Specific Connection Oriented Protocol (SSCOP) 1353 Specification, July 1994." 1354 ::= { atmSigStatEntry 1} 1356 atmSigSSCOPErrdPdus OBJECT-TYPE 1357 SYNTAX Counter32 1358 MAX-ACCESS read-only 1359 STATUS current 1360 DESCRIPTION 1361 "SSCOP Errored PDUs Counter. This counter counts the 1362 sum of the following errors: 1364 1) Invalid PDUs. 1365 These are defined in SSCOP and consist of PDUs 1366 with an incorrect length (MAA-ERROR code U), an 1367 undefined PDU type code, or that are not 32-bit 1368 aligned. 1370 2) PDUs that result in MAA-ERROR codes and are 1372 discarded. 1374 See MAA-ERROR codes A-D, F-M, and Q-T defined in 1375 ITU-T Q.2110." 1376 REFERENCE 1377 "ITU-T Recommendation Q.2110, Broadband 1378 Integrated Services Digital Network 1379 (B-ISDN) - ATM Adaptation Layer - Service 1380 Specific Connection Oriented Protocol (SSCOP) 1381 Specification, July 1994." 1382 ::= { atmSigStatEntry 2 } 1384 atmSigDetectSetupAttempts OBJECT-TYPE 1385 SYNTAX Counter32 1386 MAX-ACCESS read-only 1387 STATUS current 1388 DESCRIPTION 1389 "Call Setup Attempts Counter. This counter counts 1390 the number of call setup attempts (both successful 1391 and unsuccessful) detected on this interface." 1392 ::= { atmSigStatEntry 3 } 1394 atmSigEmitSetupAttempts OBJECT-TYPE 1395 SYNTAX Counter32 1396 MAX-ACCESS read-only 1397 STATUS current 1398 DESCRIPTION 1399 "Call Setup Attempts Counter. This counter counts 1400 the number of call setup attempts (both successful 1401 and unsuccessful) transmitted on this interface." 1402 ::= { atmSigStatEntry 4 } 1404 atmSigDetectUnavailRoutes OBJECT-TYPE 1405 SYNTAX Counter32 1406 MAX-ACCESS read-only 1407 STATUS current 1408 DESCRIPTION 1409 "Number of Route Unavailability detected on this interface. 1410 This counter is incremented when a RELEASE, RELEASE COMPLETE 1411 (only when not preceded by a RELEASE message for the same 1412 call), ADD PARTY REJECT, or STATUS message that 1413 contains one of the following cause code values is 1414 received (Note: These cause values 1415 apply to both UNI3.0 and UNI3.1): 1417 Cause Value Meaning 1419 1 unallocated (unassigned) number 1420 2 no route to specified transit network 1421 3 no route to destination 1423 NOTE: For this counter, RELEASE COMPLETE 1424 messages that are a reply to a previous RELEASE 1425 message and contain the same cause value, are 1426 redundant (for counting purposes) and should not 1427 be counted." 1429 ::= { atmSigStatEntry 5 } 1431 atmSigEmitUnavailRoutes OBJECT-TYPE 1432 SYNTAX Counter32 1433 MAX-ACCESS read-only 1434 STATUS current 1435 DESCRIPTION 1436 "Number of Route Unavailability transmitted from this 1437 interface. This counter is incremented when a RELEASE, 1438 RELEASE COMPLETE (only when not preceded by a RELEASE 1439 message for the same call), ADD PARTY REJECT, or 1440 STATUS message that contains one of the following cause 1441 code values is transmitted (Note: These cause values apply 1442 to both UNI3.0 and UNI3.1): 1444 Cause Value Meaning 1446 1 unallocated (unassigned) number 1447 2 no route to specified transit network 1448 3 no route to destination 1450 NOTE: For this counter, RELEASE COMPLETE 1451 messages that are a reply to a previous RELEASE 1452 message and contain the same cause value, are 1453 redundant (for counting purposes) and should not 1454 be counted." 1455 ::= { atmSigStatEntry 6 } 1457 atmSigDetectUnavailResrcs OBJECT-TYPE 1458 SYNTAX Counter32 1459 MAX-ACCESS read-only 1460 STATUS current 1461 DESCRIPTION 1462 "Number of Resource Unavailability detected on this 1463 interface. This counter is incremented when a RELEASE, 1464 RELEASE COMPLETE (only when not preceded by a RELEASE 1465 message for the same call), ADD PARTY REJECT, or 1466 STATUS message that contains one of the following 1468 cause code values is received (Note: These cause 1469 values apply to both UNI3.0 and UNI3.1 unless 1470 otherwise stated): 1472 Cause Value Meaning 1474 35 requested VPCI/VCI not available 1475 37 user cell rate not available (UNI3.1 1476 only) 1477 38 network out of order 1478 41 temporary failure 1479 45 no VPCI/VCI available 1480 47 resource unavailable, unspecified 1481 49 Quality of Service unavailable 1482 51 user cell rate not available (UNI3.0 1483 only) 1484 58 bearer capability not presently 1485 available 1486 63 Service or option not available, 1487 unspecified 1488 92 too many pending add party requests 1490 NOTE: For this counter, RELEASE COMPLETE 1491 messages that are a reply to a previous RELEASE 1492 message and contain the same cause value, are 1493 redundant (for counting purposes) and should not 1494 be counted." 1495 ::= { atmSigStatEntry 7 } 1497 atmSigEmitUnavailResrcs OBJECT-TYPE 1498 SYNTAX Counter32 1499 MAX-ACCESS read-only 1500 STATUS current 1501 DESCRIPTION 1502 "Number of Resource Unavailability transmitted from this 1503 interface. This counter is incremented when a RELEASE, 1504 RELEASE COMPLETE (only when not preceded by a RELEASE message 1505 for the same call), ADD PARTY REJECT, or STATUS message that 1506 contains one of the following cause code values is transmitted 1507 (Note: These cause values apply to both UNI3.0 and UNI3.1 1508 unless otherwise stated): 1510 Cause Value Meaning 1512 35 requested VPCI/VCI not available 1513 37 user cell rate not available (UNI3.1 1515 only) 1516 38 network out of order 1517 41 temporary failure 1518 45 no VPCI/VCI available 1519 47 resource unavailable, unspecified 1520 49 Quality of Service unavailable 1521 51 user cell rate not available (UNI3.0 1522 only) 1524 58 bearer capability not presently 1525 available 1526 63 Service or option not available, 1527 unspecified 1528 92 too many pending add party requests 1530 NOTE: For this counter, RELEASE COMPLETE messages that are a 1531 reply to a previous RELEASE message and contain the same cause 1532 value, are redundant (for counting purposes) and should not be 1533 counted." 1535 ::= { atmSigStatEntry 8 } 1537 atmSigDetectCldPtyEvents OBJECT-TYPE 1538 SYNTAX Counter32 1539 MAX-ACCESS read-only 1540 STATUS current 1541 DESCRIPTION 1542 "Number of Called Party Responsible For Unsuccessful Call 1543 detected on this interface. This counter is incremented when a 1544 RELEASE, RELEASE COMPLETE (only when not preceded by a RELEASE 1545 message for the same call), ADD PARTY REJECT, or STATUS message 1546 that contains one of the following cause code values is 1547 received (Note: These cause values apply to both UNI3.0 and 1548 UNI3.1): 1550 Cause Value Meaning 1552 17 user busy 1553 18 no user responding 1554 21 call rejected 1555 22 number changed 1556 23 user rejects all calls with calling 1557 line identification restriction (CLIR) 1558 27 destination out of order 1559 31 normal, unspecified 1560 88 incompatible destination 1562 NOTE: For this counter, RELEASE COMPLETE messages that are a 1563 reply to a previous RELEASE message and contain the same cause 1564 value, are redundant (for counting purposes) and should not be 1565 counted. 1567 Note: Cause Value #30 'response to STATUS ENQUIRY' was not 1568 included in this memo since it did not apply to a hard 1569 failure." 1571 ::= { atmSigStatEntry 9 } 1573 atmSigEmitCldPtyEvents OBJECT-TYPE 1574 SYNTAX Counter32 1575 MAX-ACCESS read-only 1576 STATUS current 1577 DESCRIPTION 1579 "Number of Called Party Responsible For Unsuccessful Call 1580 transmitted from this interface. This counter is incremented 1581 when a RELEASE, RELEASE COMPLETE (only when not preceded by a 1582 RELEASE message for the same call), ADD PARTY REJECT, or STATUS 1583 message that contains one of the following cause code values is 1584 transmitted (Note: These cause values apply to both UNI3.0 and 1585 UNI3.1): 1587 Cause Value Meaning 1589 17 user busy 1590 18 no user responding 1591 21 call rejected 1592 22 number changed 1593 23 user rejects all calls with calling 1594 line identification restriction (CLIR) 1595 27 destination out of order 1596 31 normal, unspecified 1597 88 incompatible destination 1599 NOTE: For this counter, RELEASE COMPLETE messages that are a 1600 reply to a previous RELEASE message and contain the same cause 1601 value, are redundant (for counting purposes) and should not be 1602 counted. 1604 Note: Cause Value #30 'response to STATUS ENQUIRY' was not 1605 included in this memo since it did not apply to a hard failure." 1607 ::= { atmSigStatEntry 10 } 1609 atmSigDetectMsgErrors OBJECT-TYPE 1611 SYNTAX Counter32 1612 MAX-ACCESS read-only 1613 STATUS current 1614 DESCRIPTION 1615 "Number of Incorrect Messages detected on this interface. The 1616 Incorrect Messages Counter reflects any sort of incorrect 1617 information in a message. This includes: 1619 - RELEASE, RELEASE COMPLETE, ADD PARTY REJECT, 1620 and STATUS messages transmitted, that contain any of 1621 the Cause values listed below. 1623 - Ignored messages. These messages are dropped 1624 because the message was so damaged that it could 1625 not be further processed. A list of dropped 1626 messages is compiled below: 1628 1. Message with invalid protocol discriminator 1630 2. Message with errors in the call reference I.E. 1631 - Bits 5-8 of the first octet not equal to 1632 '0000' 1633 - Bits 1-4 of the first octet indicating a 1634 length other than 3 octets 1635 - RELEASE COMPLETE message received with a 1636 call reference that does not relate to a 1637 call active or in progress 1638 - SETUP message received with call reference 1639 flag incorrectly set to 1 1640 - SETUP message received with a call 1641 reference for a call that is already 1642 active or in progress. 1644 3. Message too short 1646 The following cause values are monitored by this counter (Note: 1647 These cause values apply to both UNI3.0 and UNI3.1 unless 1648 otherwise stated): 1650 Cause Value Meaning 1652 10 VPCI/VCI unacceptable (UNI3.0 only) 1653 36 VPCI/VCI assignment failure (UNI3.1 only) 1655 81 invalid call reference value 1656 82 identified channel does not exist 1657 89 invalid endpoint reference 1658 96 mandatory information element is missing 1659 97 message type non-existent or not 1660 implemented 1661 99 information element non-existent or not 1662 implemented 1663 100 invalid information element contents 1664 101 message not compatible with call state 1665 104 incorrect message length 1666 111 protocol error, unspecified 1668 NOTE: For this counter, RELEASE COMPLETE messages that are 1669 a reply to a previous RELEASE message and contain the same 1670 cause value, are redundant (for counting purposes) and 1671 should not be counted." 1673 ::= { atmSigStatEntry 11 } 1675 atmSigEmitMsgErrors OBJECT-TYPE 1676 SYNTAX Counter32 1677 MAX-ACCESS read-only 1678 STATUS current 1679 DESCRIPTION 1680 "Number of Incorrect Messages transmitted on this interface. 1681 The Incorrect Messages Counter reflects any sort of incorrect 1682 information in a message. This includes: 1684 - RELEASE, RELEASE COMPLETE, ADD PARTY REJECT, 1685 and STATUS messages transmitted or 1686 received, that contain any of the Cause values 1687 listed below. 1689 - Ignored messages. These messages are dropped 1690 because the message was so damaged that it could 1691 not be further processed. A list of dropped 1692 messages is compiled below: 1694 1. Message with invalid protocol discriminator 1696 2. Message with errors in the call reference I.E. 1697 - Bits 5-8 of the first octet not equal to 1698 '0000' 1699 - Bits 1-4 of the first octet indicating a 1700 length other than 3 octets 1701 - RELEASE COMPLETE message received with a 1702 call reference that does not relate to a 1703 call active or in progress 1704 - SETUP message received with call reference 1705 flag incorrectly set to 1 1706 - SETUP message received with a call 1707 reference for a call that is already 1708 active or in progress. 1710 3. Message too short 1712 The following cause values are monitored by this counter 1713 (Note: These cause values apply to both UNI3.0 and UNI3.1 1714 unless otherwise stated): 1716 Cause Value Meaning 1718 10 VPCI/VCI unacceptable (UNI3.0 only) 1719 36 VPCI/VCI assignment failure (UNI3.1 only) 1720 81 invalid call reference value 1721 82 identified channel does not exist 1722 89 invalid endpoint reference 1723 96 mandatory information element is missing 1724 97 message type non-existent or not 1725 implemented 1726 99 information element non-existent or not 1727 implemented 1728 100 invalid information element contents 1729 101 message not compatible with call state 1730 104 incorrect message length 1731 111 protocol error, unspecified 1733 NOTE: For this counter, RELEASE COMPLETE messages that are 1734 a reply to a previous RELEASE message and contain the same 1735 cause value, are redundant (for counting purposes) and 1736 should not be counted." 1738 ::= { atmSigStatEntry 12 } 1740 atmSigDetectClgPtyEvents OBJECT-TYPE 1741 SYNTAX Counter32 1742 MAX-ACCESS read-only 1743 STATUS current 1744 DESCRIPTION 1745 "Number of Calling Party Events detected on this interface. 1746 This counter monitors error events that occur due to the 1747 originating user doing something wrong. This counter is 1748 incremented when a RELEASE, RELEASE COMPLETE (only when not 1749 preceded by a RELEASE message for the same call), ADD PARTY 1750 REJECT, or STATUS message that contains one of the following 1751 cause code values is received (Note: These cause values 1752 apply to both UNI3.0 and UNI3.1): 1754 Cause Value Meaning 1756 28 invalid number format (address incomplete) 1757 43 access information discarded 1758 57 bearer capability not authorized 1759 65 bearer capability not implemented 1760 73 unsupported combination of traffic 1761 parameters 1763 78 AAL parameters cannot be supported (UNI3.1 1764 only) 1765 91 invalid transit network selection 1766 93 AAL parameters cannot be supported (UNI3.0 1767 only) 1769 NOTE: For this counter, RELEASE COMPLETE messages that 1770 are a reply to a previous RELEASE message and contain 1771 the same cause value, are redundant (for counting purposes) 1772 and should not be counted." 1774 ::= { atmSigStatEntry 13 } 1776 atmSigEmitClgPtyEvents OBJECT-TYPE 1777 SYNTAX Counter32 1778 MAX-ACCESS read-only 1779 STATUS current 1780 DESCRIPTION 1781 "Number of Calling Party Events transmitted from this interface. 1782 This counter monitors error events that occur due to the 1783 originating user doing something wrong. This counter is 1784 incremented when a RELEASE, RELEASE COMPLETE (only when not 1785 preceded by a RELEASE message for the same call), ADD PARTY 1786 REJECT, or STATUS message that contains one of the following 1787 cause code values is transmitted (Note: These cause values 1788 apply to both UNI3.0 and UNI3.1): 1790 Cause Value Meaning 1792 28 invalid number format (address incomplete) 1793 43 access information discarded 1794 57 bearer capability not authorized 1795 65 bearer capability not implemented 1796 73 unsupported combination of traffic 1797 parameters 1798 78 AAL parameters cannot be supported (UNI3.1 1799 only) 1800 91 invalid transit network selection 1801 93 AAL parameters cannot be supported (UNI3.0 1802 only) 1804 NOTE: For this counter, RELEASE COMPLETE messages that are 1805 a reply to a previous RELEASE message and contain the same 1806 cause value, are redundant (for counting purposes) and 1807 should not be counted." 1809 ::= { atmSigStatEntry 14 } 1811 atmSigDetectTimerExpireds OBJECT-TYPE 1812 SYNTAX Counter32 1813 MAX-ACCESS read-only 1814 STATUS current 1815 DESCRIPTION 1816 "Number of Timer Expiries detected on this interface. The Timer 1817 Expiries Counter provides a count of network timer expiries, and 1818 to some extent, host or switch timer expiries. The conditions 1819 for incrementing this counter are: 1821 - Expiry of any network timer 1823 - Receipt of a RELEASE or RELEASE COMPLETE 1824 message with Cause #102, 'recovery on 1825 timer expiry'. 1827 NOTE: For this counter, RELEASE COMPLETE messages that are 1828 a reply to a previous RELEASE message and contain the same 1829 cause value, are redundant (for counting purposes) and 1830 should not be counted." 1832 ::= { atmSigStatEntry 15 } 1834 atmSigEmitTimerExpireds OBJECT-TYPE 1836 SYNTAX Counter32 1837 MAX-ACCESS read-only 1838 STATUS current 1839 DESCRIPTION 1840 "Number of Timer Expiries transmitted from this interface. 1841 The Timer Expiries Counter provides a count of network timer 1842 expiries, and to some extent, host or switch timer expiries. 1843 The conditions for incrementing this counter are: 1845 - Expiry of any network timer 1847 - Receipt of a RELEASE or RELEASE COMPLETE 1848 message with Cause #102, 'recovery on 1849 timer expiry'. 1851 NOTE: For this counter, RELEASE COMPLETE messages that are a 1852 reply to a previous RELEASE message and contain the same cause 1853 value, are redundant (for counting purposes) and should not be 1854 counted." 1856 ::= { atmSigStatEntry 16 } 1858 atmSigDetectRestarts OBJECT-TYPE 1859 SYNTAX Counter32 1860 MAX-ACCESS read-only 1861 STATUS current 1862 DESCRIPTION 1863 "Number of Restart Activity errors detected on this interface. 1864 The Restart Activity Counter provides a count of host, switch, 1865 or network restart activity. This counter is incremented when 1866 receiving a RESTART message." 1868 ::= { atmSigStatEntry 17 } 1870 atmSigEmitRestarts OBJECT-TYPE 1871 SYNTAX Counter32 1872 MAX-ACCESS read-only 1873 STATUS current 1874 DESCRIPTION 1875 "Number of Restart Activity errors transmitted from this 1876 interface. The Restart Activity Counter provides a count of 1877 host, switch, or network restart activity. This counter is 1878 incremented when transmitting a RESTART message." 1880 ::= { atmSigStatEntry 18 } 1882 atmSigInEstabls OBJECT-TYPE 1883 SYNTAX Counter32 1884 MAX-ACCESS read-only 1885 STATUS current 1886 DESCRIPTION 1887 "Number of SVCs established at this signalling entity for 1888 incoming connections." 1889 ::= { atmSigStatEntry 19 } 1891 atmSigOutEstabls OBJECT-TYPE 1892 SYNTAX Counter32 1893 MAX-ACCESS read-only 1894 STATUS current 1895 DESCRIPTION 1896 "Number of SVCs established at this signalling entity for 1897 outgoing connections." 1898 ::= { atmSigStatEntry 20 } 1900 -- 4. ATM Interface Signalling Support Table 1901 -- 1902 -- This table provides information to support 1903 -- the signalling process which is used to establish 1904 -- ATM Switched Virtual Connections (SVCs). 1906 atmSigSupportTable OBJECT-TYPE 1907 SYNTAX SEQUENCE OF AtmSigSupportEntry 1908 MAX-ACCESS not-accessible 1909 STATUS current 1910 DESCRIPTION 1911 "This table contains ATM local interface configuration 1912 parameters, one entry per ATM signalling interface." 1913 ::= { atm2MIBObjects 4 } 1915 atmSigSupportEntry OBJECT-TYPE 1916 SYNTAX AtmSigSupportEntry 1917 MAX-ACCESS not-accessible 1918 STATUS current 1919 DESCRIPTION 1920 "This list contains signalling configuration parameters 1921 and state variables." 1922 INDEX { ifIndex } 1923 ::= { atmSigSupportTable 1} 1925 AtmSigSupportEntry ::= SEQUENCE { 1926 atmSigSupportClgPtyNumDel INTEGER, 1927 atmSigSupportClgPtySubAddr INTEGER, 1928 atmSigSupportCldPtySubAddr INTEGER, 1929 atmSigSupportHiLyrInfo INTEGER, 1930 atmSigSupportLoLyrInfo INTEGER, 1931 atmSigSupportBlliRepeatInd INTEGER, 1932 atmSigSupportAALInfo INTEGER, 1933 atmSigSupportPrefCarrier OCTET STRING 1934 } 1936 atmSigSupportClgPtyNumDel OBJECT-TYPE 1937 SYNTAX INTEGER { enabled(1), disabled(2) } 1938 MAX-ACCESS read-write 1939 STATUS current 1940 DESCRIPTION 1941 "This object indicates whether the Calling Party Number 1942 Information Element is transferred to the called party 1943 address. The value of this object can be: 1945 - enabled(1) This Information Element is transferred 1946 to the called party 1948 - disabled(2) This Information Element is NOT 1949 transferred to the called party." 1951 ::= { atmSigSupportEntry 1 } 1953 atmSigSupportClgPtySubAddr OBJECT-TYPE 1954 SYNTAX INTEGER { enabled(1), disabled(2) } 1955 MAX-ACCESS read-write 1956 STATUS current 1957 DESCRIPTION 1958 "This object indicates whether to accept and transfer the Calling 1959 Party Subaddress Information Element from the calling party to 1960 the called party. Calling party subaddress information shall 1961 only be transferred to the called party if calling party number 1962 delivery is enabled (i.e., atmSigSupportClgPtyNumDel = 1963 'enabled(1)'. The value of this object can be: 1965 - enabled(1) This Information Element is transferred 1966 to the called party 1968 - disabled(2) This Information Element is NOT 1969 transferred to the called party." 1971 ::= { atmSigSupportEntry 2 } 1973 atmSigSupportCldPtySubAddr OBJECT-TYPE 1974 SYNTAX INTEGER { enabled(1), disabled(2) } 1975 MAX-ACCESS read-write 1976 STATUS current 1977 DESCRIPTION 1978 "This object indicates whether to accept, transfer, and deliver 1979 the Called Party Subaddress Information Element from the calling 1980 party to the called party. The value of this object can be: 1982 - enabled(1) This Information Element is transferred 1983 to the called party 1985 - disabled(2) This Information Element is NOT 1986 transferred to the called party." 1988 ::= { atmSigSupportEntry 3 } 1990 atmSigSupportHiLyrInfo OBJECT-TYPE 1991 SYNTAX INTEGER { enabled(1), disabled(2) } 1992 MAX-ACCESS read-write 1993 STATUS current 1994 DESCRIPTION 1995 "This object indicates whether to accept, transfer, and deliver 1996 the Broadband High Layer Information Element from the calling 1997 party to the called party. The value of this object can be: 1999 - enabled(1) This Information Element is transferred 2000 to the called party 2002 - disabled(2) This Information Element is NOT 2003 transferred to the called party." 2005 ::= { atmSigSupportEntry 4 } 2007 atmSigSupportLoLyrInfo OBJECT-TYPE 2008 SYNTAX INTEGER { enabled(1), disabled(2) } 2009 MAX-ACCESS read-write 2010 STATUS current 2011 DESCRIPTION 2012 "This object indicates whether to accept, transfer, and deliver 2013 the Broadband Low Layer Information Element from the calling 2014 party to the called party. The value of this object can be: 2016 - enabled(1) This Information Element is transferred 2017 to the called party 2019 - disabled(2) This Information Element is NOT 2020 transferred to the called party." 2022 ::= { atmSigSupportEntry 5 } 2024 atmSigSupportBlliRepeatInd OBJECT-TYPE 2025 SYNTAX INTEGER { enabled(1), disabled(2) } 2026 MAX-ACCESS read-write 2027 STATUS current 2028 DESCRIPTION 2029 "This object indicates whether to accept, transfer, and deliver 2030 the Broadband Repeat Indicator with two or three instances of 2031 the Broadband Low Layer Information Element for low layer 2032 information selection from the calling party to the called 2033 party. This object's value should always be disabled(2) if 2034 the value of atmSigSupportLolyrInfo is disabled(2). 2036 The value of this object can be: 2038 - enabled(1) This Information Element is transferred 2039 to the called party 2041 - disabled(2) This Information Element is NOT 2042 transferred to the called party." 2043 ::= { atmSigSupportEntry 6 } 2045 atmSigSupportAALInfo OBJECT-TYPE 2046 SYNTAX INTEGER { enabled(1), disabled(2) } 2047 MAX-ACCESS read-write 2048 STATUS current 2049 DESCRIPTION 2050 "This object indicates whether to accept, transfer, and deliver 2051 the ATM Adaptation Layer Parameters Information Element from the 2052 calling party to the called party. The value of this object can 2053 be: 2055 - enabled(1) This Information Element is transferred 2056 to the called party 2058 - disabled(2) This Information Element is NOT 2059 transferred to the called party." 2061 ::= { atmSigSupportEntry 7 } 2063 atmSigSupportPrefCarrier OBJECT-TYPE 2064 SYNTAX OCTET STRING (SIZE(0|4)) 2065 MAX-ACCESS read-write 2066 STATUS current 2067 DESCRIPTION 2068 "This parameter identifies the carrier to which intercarrier 2069 calls originated from this interface are routed when transit 2071 network selection information is not provided by the calling 2072 party. If a Carrier Identification Code (CIC) is used the 2073 parameter shall contain the CIC. For three-digit CICs, the first 2074 octet shall be '0' and the CIC is contained in the three 2075 following octets. If the preferred carrier feature is not 2076 supported the value is a zero-length string." 2078 ::= { atmSigSupportEntry 8 } 2080 -- 5. ATM Signalling Descriptor Parameter Table 2082 atmSigDescrParamTable OBJECT-TYPE 2083 SYNTAX SEQUENCE OF AtmSigDescrParamEntry 2084 MAX-ACCESS not-accessible 2085 STATUS current 2086 DESCRIPTION 2087 "A table contains signalling capabilities of VCLs except the 2088 Traffic Descriptor. Traffic descriptors are described in 2089 the atmTrafficDescrParamTable." 2091 REFERENCE 2092 "ATM User-Network Interface Specification, Version 3.1 (UNI 2093 3.1), September 1994, Section 5.4.5 Variable Length 2094 Information Elements." 2096 ::= { atm2MIBObjects 5 } 2098 atmSigDescrParamEntry OBJECT-TYPE 2099 SYNTAX AtmSigDescrParamEntry 2100 MAX-ACCESS not-accessible 2101 STATUS current 2102 DESCRIPTION 2103 "Each entry in this table represents a 2104 set of signalling capabilities that can 2105 be applied to a VCL. There is no requirement 2106 for unique entries, except that the index must 2107 be unique." 2108 INDEX { atmSigDescrParamIndex } 2109 ::= { atmSigDescrParamTable 1 } 2111 AtmSigDescrParamEntry ::= 2112 SEQUENCE { 2113 atmSigDescrParamIndex 2114 AtmSigDescrParamIndex, 2115 atmSigDescrParamAalType INTEGER, 2116 atmSigDescrParamAalSscsType INTEGER, 2117 atmSigDescrParamBhliType INTEGER, 2119 atmSigDescrParamBhliInfo OCTET STRING, 2120 atmSigDescrParamBbcConnConf INTEGER, 2121 atmSigDescrParamBlliLayer2 INTEGER, 2122 atmSigDescrParamBlliLayer3 INTEGER, 2123 atmSigDescrParamBlliPktSize INTEGER, 2124 atmSigDescrParamBlliSnapId INTEGER, 2125 atmSigDescrParamBlliOuiPid OCTET STRING, 2126 atmSigDescrParamRowStatus RowStatus 2127 } 2129 atmSigDescrParamIndex OBJECT-TYPE 2130 SYNTAX AtmSigDescrParamIndex 2131 MAX-ACCESS not-accessible 2132 STATUS current 2133 DESCRIPTION 2134 "The value of this object is used by the 2135 atmVclGenSigDescrIndex object in the atmVclGenTable to 2136 identify a row in this table." 2138 ::= { atmSigDescrParamEntry 1 } 2140 atmSigDescrParamAalType OBJECT-TYPE 2141 SYNTAX INTEGER { 2142 other(1), -- not defined 2143 aal1(2), -- AAL type 1 2144 aal34(3), -- AAL type 3/4 2145 aal5(4), -- AAL type 5 2146 userDefined(5), -- User-Defined AAL 2147 aal2(6) -- AAL type 2 2148 } 2149 MAX-ACCESS read-create 2150 STATUS current 2151 DESCRIPTION 2152 "The AAL type. The value of this object is set to other(1) 2153 when not defined." 2155 DEFVAL { other } 2156 ::= { atmSigDescrParamEntry 2 } 2158 atmSigDescrParamAalSscsType OBJECT-TYPE 2159 SYNTAX INTEGER { 2160 other(1), -- other, or not used 2161 assured(2), -- Data SSCS based on SSCOP 2162 -- assured operation 2163 nonassured(3), -- Data SSCS based on SSCOP 2164 -- non-assured operation 2165 frameRelay(4), -- frame relay SSCS 2166 null(5) -- null 2168 } 2169 MAX-ACCESS read-create 2170 STATUS current 2171 DESCRIPTION 2172 "The SSCS type used by this entry." 2174 DEFVAL { other } 2175 ::= { atmSigDescrParamEntry 3 } 2177 atmSigDescrParamBhliType OBJECT-TYPE 2178 SYNTAX INTEGER { 2179 other(1), -- not defined 2180 iso(2), -- ISO 2181 user(3), -- User specific 2182 hiProfile(4), -- Higher layer profile 2183 -- this enum applicable to 2184 -- UNI 3.0 only 2185 vendorSpecific(5) -- Vender specific 2186 -- application identifier 2187 } 2188 MAX-ACCESS read-create 2189 STATUS current 2190 DESCRIPTION 2191 "The Broadband high layer type." 2193 DEFVAL { other } 2194 ::= { atmSigDescrParamEntry 4 } 2196 atmSigDescrParamBhliInfo OBJECT-TYPE 2197 SYNTAX OCTET STRING (SIZE(0..8)) 2198 MAX-ACCESS read-create 2199 STATUS current 2200 DESCRIPTION 2201 "The Broadband high layer information. When 2202 atmSigDescrParamBhliType is set to iso(2), the value of this 2203 object is a zero length string. When 2204 atmSigDescrParamBhliType is set to user(3), the value of 2205 this object is an octet string with length ranging from 0 to 2206 8. When atmSigDescrParamBhliType is set to hiProfile(4), 2207 the value of this object is a length of 4 octet string 2208 containing user to user profile identifier. When 2209 atmSigDescrParamBhliType is set to vendorSpecific(5), the 2210 value of this object is a length of 7 octet string, where 2211 the most significant 3 octets consist of a globally- 2212 administered OUI, and the least significant 4 octets are the 2213 vender administered application OUI." 2215 DEFVAL { ''H } 2217 ::= { atmSigDescrParamEntry 5 } 2219 atmSigDescrParamBbcConnConf OBJECT-TYPE 2220 SYNTAX INTEGER { 2221 ptp(1), -- point-to-point 2222 ptmp(2) -- point-to-multipoint 2223 } 2224 MAX-ACCESS read-create 2225 STATUS current 2226 DESCRIPTION 2227 "The Broadband bearer capability user plane connection 2228 configuration parameter." 2229 DEFVAL { ptp } 2230 ::= { atmSigDescrParamEntry 6 } 2232 atmSigDescrParamBlliLayer2 OBJECT-TYPE 2233 SYNTAX INTEGER { 2234 other(1), -- not specified 2235 iso1745(2), -- Basic mode ISO 1745 2236 q921(3), -- CCITT Recommendation Q.921 2237 x25linklayer(4), -- CCITT Recommendation X.25 2238 -- Link Layer 2239 x25multilink(5), -- CCITT Recommendation X.25 2240 -- Multilink 2241 lapb(6), -- Extended LAPB; for half 2242 -- duplex operation 2243 hdlcArm(7), -- HDLC ARM (ISO 4335) 2244 hdlcNrm(8), -- HDLC NRM (ISO 4335) 2245 hdlcAbm(9), -- HDLC ABM (ISO 4335) 2246 iso88022(10), -- LAN logical link control 2247 -- (ISO 8802/2) 2248 x75slp(11), -- CCITT Recommendation X.75, 2249 -- single link 2250 -- procedure (SLP) 2251 q922(12), -- CCITT Recommendation Q.922 2252 userDef(13), -- User specified 2253 iso7776(14) -- ISO 7776 DTE-DTE operation 2254 } 2255 MAX-ACCESS read-create 2256 STATUS current 2257 DESCRIPTION 2258 "The Broadband low layer information, protocol type of layer 2259 2. The value of this object is other(1) if layer 2 protocol 2260 is not used." 2262 DEFVAL { other } 2263 ::= { atmSigDescrParamEntry 7 } 2265 atmSigDescrParamBlliLayer3 OBJECT-TYPE 2266 SYNTAX INTEGER { 2267 other(1), -- not specified 2268 x25pkt(2), -- CCITT Recommendation X.25 2269 -- packet layer 2270 isoiec8208(3), -- ISO/IEC 8208 (X.25 packet 2271 -- level protocol for data 2272 -- terminal equipment) 2273 x223iso8878(4), -- X.223/ISO 8878 2274 isoiec8473(5), -- ISO/IEC 8473 OSI 2275 -- connectionless 2276 -- mode protocol 2277 t70(6), -- CCITT Recommendation T.70 2278 -- minimum 2279 -- network layer 2280 tr9577(7), -- ISO/IEC TR 9577 Protocol 2281 -- Identification in the 2282 -- network layer 2283 userDef(8) -- user specified 2284 } 2285 MAX-ACCESS read-create 2286 STATUS current 2287 DESCRIPTION 2288 "The Broadband low layer information, protocol type of layer 2289 3. The value of this object is other(1) if layer 3 protocol 2290 is not used." 2292 DEFVAL { other } 2293 ::= { atmSigDescrParamEntry 8 } 2295 atmSigDescrParamBlliPktSize OBJECT-TYPE 2296 SYNTAX INTEGER { 2297 other(1), -- not used 2298 s16(2), -- 16 octets 2299 s32(3), -- 32 octets 2300 s64(4), -- 64 octets 2301 s128(5), -- 128 octets 2302 s256(6), -- 256 octets 2303 s512(7), -- 512 octets 2304 s1024(8), -- 1028 octets 2305 s2048(9), -- 2048 octets 2306 s4096(10) -- 4096 octets 2307 } 2308 MAX-ACCESS read-create 2309 STATUS current 2310 DESCRIPTION 2311 "The default packet size defined in B-LLI." 2313 DEFVAL { other } 2314 ::= { atmSigDescrParamEntry 9 } 2316 atmSigDescrParamBlliSnapId OBJECT-TYPE 2317 SYNTAX INTEGER { 2318 other(1), -- not used 2319 true(2), -- SNAP ID is 1 2320 false(3) -- SNAP ID is 0 2321 } 2322 MAX-ACCESS read-create 2323 STATUS current 2324 DESCRIPTION 2325 "The SNAP ID used for Broadband low layer protocol layer 3. 2326 The value of this object is other(1) if 2327 atmSigDescrParamBlliLayer3 is set to other(1)." 2329 DEFVAL { other } 2330 ::= { atmSigDescrParamEntry 10 } 2332 atmSigDescrParamBlliOuiPid OBJECT-TYPE 2333 SYNTAX OCTET STRING (SIZE(0|5)) 2334 MAX-ACCESS read-create 2335 STATUS current 2336 DESCRIPTION 2337 "The OUI/PID encoding for Broadband low layer protocol layer 2338 3. The value of this object is a zero length string if 2339 atmSigDescrParamBlliLayer3 is set to other(1). When used, 2340 it is always 5 octets with the most significant octet as the 2341 OUI Octet 1 and the least significant octet as the PID Octet 2342 2." 2344 DEFVAL { ''H } 2345 ::= { atmSigDescrParamEntry 11 } 2347 atmSigDescrParamRowStatus OBJECT-TYPE 2348 SYNTAX RowStatus 2349 MAX-ACCESS read-create 2350 STATUS current 2351 DESCRIPTION 2352 "This object is used to create and delete rows in the 2353 atmSigDescrParamTable." 2355 ::= { atmSigDescrParamEntry 12 } 2357 -- 6. ATM Interface Registered Address Table -- 2359 atmIfRegisteredAddrTable OBJECT-TYPE 2361 SYNTAX SEQUENCE OF AtmIfRegisteredAddrEntry 2362 MAX-ACCESS not-accessible 2363 STATUS current 2364 DESCRIPTION 2365 "This table contains a list of ATM addresses that can be used for 2366 calls to and from a given interface by a switch or service. The 2367 ATM addresses are either registered by the endsystem via ILMI or 2368 statically configured. This table does not expose PNNI 2369 reachability information. ILMI registered addresses cannot be 2370 deleted using this table. This table only applies to switches 2371 and network services." 2372 ::= { atm2MIBObjects 6 } 2374 atmIfRegisteredAddrEntry OBJECT-TYPE 2375 SYNTAX AtmIfRegisteredAddrEntry 2376 MAX-ACCESS not-accessible 2377 STATUS current 2378 DESCRIPTION 2379 "An entry in the ATM Interface Registered Address table." 2381 INDEX { ifIndex, atmIfRegAddrAddress } 2382 ::= { atmIfRegisteredAddrTable 1} 2384 AtmIfRegisteredAddrEntry ::= SEQUENCE { 2385 atmIfRegAddrAddress AtmAddr, 2386 atmIfRegAddrAddressSource INTEGER, 2387 atmIfRegAddrOrgScope INTEGER, 2388 atmIfRegAddrRowStatus RowStatus 2389 } 2391 atmIfRegAddrAddress OBJECT-TYPE 2392 SYNTAX AtmAddr 2393 MAX-ACCESS not-accessible 2394 STATUS current 2395 DESCRIPTION 2396 "An address registered for a given switch or service interface." 2398 ::= { atmIfRegisteredAddrEntry 1} 2400 atmIfRegAddrAddressSource OBJECT-TYPE 2401 SYNTAX INTEGER { 2402 other(1), 2403 static(2), 2404 dynamic(3) 2405 } 2406 MAX-ACCESS read-only 2407 STATUS current 2408 DESCRIPTION 2409 "The type of address source for a given ATM Address. The value 2410 dynamic(3) is indicated when ILMI is used." 2411 ::= { atmIfRegisteredAddrEntry 2} 2413 atmIfRegAddrOrgScope OBJECT-TYPE 2414 SYNTAX INTEGER { 2415 localNetwork(1), 2416 localNetworkPlusOne(2), 2417 localNetworkPlusTwo(3), 2418 siteMinusOne(4), 2419 intraSite(5), 2420 sitePlusOne(6), 2421 organizationMinusOne(7), 2422 intraOrganization(8), 2423 organizationPlusOne(9), 2424 communityMinusOne(10), 2425 intraCommunity(11), 2426 communityPlusOne(12), 2427 regional(13), 2428 interRegional(14), 2429 global(15) 2430 } 2431 MAX-ACCESS read-create 2432 STATUS current 2433 DESCRIPTION 2434 "This object indicates the organizational scope for 2435 the referenced address. The information of the 2436 referenced address shall not be distributed outside 2437 the indicated scope. Refer to Annex 5.3 of ATM 2438 Forum UNI Signalling 4.0 for guidelines regarding 2439 the use of organizational scopes. 2441 This value cannot be configured for ILMI-registered 2442 addresses. 2444 The default values for organizational scope are 2445 localNetwork(1) for ATM group addresses, and 2446 global(15) for individual addresses." 2447 ::= { atmIfRegisteredAddrEntry 3} 2449 atmIfRegAddrRowStatus OBJECT-TYPE 2450 SYNTAX RowStatus 2451 MAX-ACCESS read-create 2452 STATUS current 2453 DESCRIPTION 2454 "This object is used to create and delete rows in the 2455 atmIfRegisteredAddrTable. Rows created dynamically (e.g., ILMI- 2456 registered addresses) cannot be deleted using this object." 2458 ::= { atmIfRegisteredAddrEntry 4} 2460 -- 7. ATM VPI/VCI to Address Mapping Table 2462 atmVclAddrTable OBJECT-TYPE 2463 SYNTAX SEQUENCE OF AtmVclAddrEntry 2464 MAX-ACCESS not-accessible 2465 STATUS current 2466 DESCRIPTION 2467 "This table provides a mapping between the atmVclTable and 2468 the ATM called party/calling party address. This table can 2469 be used to retrieve the calling party and called party ATM 2470 address pair for a given VCL. Note that there can be more 2471 than one pair of calling party and called party ATM 2472 addresses for a VCL in a point to multi-point call." 2473 ::= { atm2MIBObjects 7 } 2475 atmVclAddrEntry OBJECT-TYPE 2476 SYNTAX AtmVclAddrEntry 2477 MAX-ACCESS not-accessible 2478 STATUS current 2479 DESCRIPTION 2480 "Each entry in this table represents a binding between a VCL 2481 and an ATM address associated with this call. This ATM 2482 address can be either the called party address or the 2483 calling party address. There can be more than one pair of 2484 calling/called party ATM addresses associated with the VCL 2485 entry for point to multi-point calls. Objects 2486 atmVclAddrType, and atmVclAddrRowStatus are 2487 required during row creation." 2488 INDEX { ifIndex, atmVclVpi, atmVclVci, 2489 atmVclAddrAddr } 2490 ::= { atmVclAddrTable 1 } 2492 AtmVclAddrEntry ::= 2493 SEQUENCE { 2494 atmVclAddrAddr AtmAddr, 2495 atmVclAddrType INTEGER, 2496 atmVclAddrRowStatus RowStatus 2497 } 2499 atmVclAddrAddr OBJECT-TYPE 2500 SYNTAX AtmAddr 2501 MAX-ACCESS not-accessible 2502 STATUS current 2503 DESCRIPTION 2504 "An ATM address on one end of the VCL. For SVCs, the agent 2505 supplies the value of this object at creation time. For PVC 2506 VCL, the manager can supply the value of this object during 2507 or after the PVC VCL creation." 2508 ::= { atmVclAddrEntry 1 } 2510 atmVclAddrType OBJECT-TYPE 2511 SYNTAX INTEGER { 2512 callingParty(1), 2513 calledParty(2) 2514 } 2515 MAX-ACCESS read-create 2516 STATUS current 2517 DESCRIPTION 2518 "The type of ATM Address represented by the object 2519 atmVclAddrAddr. Choices are either the calling party ATM 2520 address or the called party ATM address." 2522 ::= { atmVclAddrEntry 2 } 2524 atmVclAddrRowStatus OBJECT-TYPE 2525 SYNTAX RowStatus 2526 MAX-ACCESS read-create 2527 STATUS current 2528 DESCRIPTION 2529 "This object is used to create or destroy an 2530 entry from this table. Note that the manager entity 2531 can only destroy the PVC VCLs." 2532 ::= { atmVclAddrEntry 3 } 2534 -- 8. ATM Address to VPI/VCI Mapping Table 2535 -- 2536 -- This table provides an alternative way to access 2537 -- a row in the atmVclAddrTable by using 2538 -- an ATM address as an index, instead of 2539 -- the ifIndex 2541 atmAddrVclTable OBJECT-TYPE 2542 SYNTAX SEQUENCE OF AtmAddrVclEntry 2543 MAX-ACCESS not-accessible 2544 STATUS current 2545 DESCRIPTION 2546 "This table provides an alternative way to retrieve the 2547 atmVclTable. This table can be used to retrieve the 2548 indexing to the atmVclTable by an ATM address." 2550 ::= { atm2MIBObjects 8 } 2552 atmAddrVclEntry OBJECT-TYPE 2553 SYNTAX AtmAddrVclEntry 2554 MAX-ACCESS not-accessible 2555 STATUS current 2556 DESCRIPTION 2557 "Each entry in this table represents an entry in the 2558 atmVclTable of the ATM-MIB by its ATM address. The ATM 2559 address is either the calling or called party ATM address 2560 of the call. Entries in this table are read only. 2561 They show up when entries are created in the 2562 atmVclAddrTable." 2563 REFERENCE 2564 "Tesink, K., Editor, Definitions of Managed Objects 2565 for ATM Management, RFC 2515, Bell Communications 2566 Research, February, 1999." 2567 INDEX { atmVclAddrAddr, atmAddrVclAtmIfIndex, 2568 atmAddrVclVpi, atmAddrVclVci } 2569 ::= { atmAddrVclTable 1 } 2571 AtmAddrVclEntry ::= 2572 SEQUENCE { 2573 atmAddrVclAtmIfIndex InterfaceIndex, 2574 atmAddrVclVpi AtmVpIdentifier, 2575 atmAddrVclVci AtmVcIdentifier, 2576 atmAddrVclAddrType INTEGER 2577 } 2579 atmAddrVclAtmIfIndex OBJECT-TYPE 2580 SYNTAX InterfaceIndex 2581 MAX-ACCESS not-accessible 2582 STATUS current 2583 DESCRIPTION 2584 "The interface index of the ATM interface to which this 2585 VCL pertains. This object combined with the 2586 atmAddrVclVpi and atmAddrVclVci objects serves as an 2587 index to the atmVclTable." 2588 ::= { atmAddrVclEntry 1 } 2590 atmAddrVclVpi OBJECT-TYPE 2591 SYNTAX AtmVpIdentifier 2592 MAX-ACCESS not-accessible 2593 STATUS current 2594 DESCRIPTION 2595 "The VPI value of the VCL. This object combined with the 2596 atmAddrVclAtmIfIndex and atmAddrVclVci objects serves as 2597 an index to the atmVclTable." 2598 ::= { atmAddrVclEntry 2 } 2600 atmAddrVclVci OBJECT-TYPE 2601 SYNTAX AtmVcIdentifier 2602 MAX-ACCESS not-accessible 2603 STATUS current 2604 DESCRIPTION 2605 "The VCI value of the VCL. This object combined with the 2606 atmAddrVclAtmIfIndex and atmAddrVclVpi objects serves as 2607 an index to the atmVclTable." 2608 ::= { atmAddrVclEntry 3 } 2610 atmAddrVclAddrType OBJECT-TYPE 2611 SYNTAX INTEGER { 2612 callingParty(1), 2613 calledParty(2) } 2614 MAX-ACCESS read-only 2615 STATUS current 2616 DESCRIPTION 2617 "The type of ATM Address represented by the object 2618 atmVclAddrAddr. Choices are either calling party address 2619 or called party address." 2620 ::= { atmAddrVclEntry 4 } 2622 -- 9. ATM VPL Statistics Table 2624 atmVplStatTable OBJECT-TYPE 2625 SYNTAX SEQUENCE OF AtmVplStatEntry 2626 MAX-ACCESS not-accessible 2627 STATUS current 2628 DESCRIPTION 2629 "This table contains all statistics counters per VPL. It is 2630 used to monitor the usage of the VPL in terms of incoming 2631 cells and outgoing cells." 2632 ::= { atm2MIBObjects 9 } 2634 atmVplStatEntry OBJECT-TYPE 2635 SYNTAX AtmVplStatEntry 2636 MAX-ACCESS not-accessible 2637 STATUS current 2638 DESCRIPTION 2639 "Each entry in this table represents a VPL." 2640 INDEX { ifIndex, atmVplVpi } 2641 ::= { atmVplStatTable 1 } 2643 AtmVplStatEntry ::= 2644 SEQUENCE { 2645 atmVplStatTotalCellIns Counter32, 2646 atmVplStatClp0CellIns Counter32, 2647 atmVplStatTotalDiscards Counter32, 2648 atmVplStatClp0Discards Counter32, 2649 atmVplStatTotalCellOuts Counter32, 2650 atmVplStatClp0CellOuts Counter32, 2651 atmVplStatClp0Tagged Counter32 2652 } 2654 atmVplStatTotalCellIns OBJECT-TYPE 2655 SYNTAX Counter32 2656 MAX-ACCESS read-only 2657 STATUS current 2658 DESCRIPTION 2659 "The total number of valid ATM cells received by this VPL 2660 including both CLP=0 and CLP=1 cells. The cells are 2661 counted prior to the application of the traffic policing." 2662 ::= { atmVplStatEntry 1 } 2664 atmVplStatClp0CellIns OBJECT-TYPE 2665 SYNTAX Counter32 2666 MAX-ACCESS read-only 2667 STATUS current 2668 DESCRIPTION 2669 "The number of valid ATM cells received by this VPL with 2670 CLP=0. The cells are counted prior to the application of 2671 the traffic policing." 2672 ::= { atmVplStatEntry 2 } 2674 atmVplStatTotalDiscards OBJECT-TYPE 2675 SYNTAX Counter32 2676 MAX-ACCESS read-only 2677 STATUS current 2678 DESCRIPTION 2679 "The total number of valid ATM cells discarded by the 2680 traffic policing entity. This includes cells originally 2681 received with CLP=0 and CLP=1." 2682 ::= { atmVplStatEntry 3 } 2684 atmVplStatClp0Discards OBJECT-TYPE 2685 SYNTAX Counter32 2686 MAX-ACCESS read-only 2687 STATUS current 2688 DESCRIPTION 2689 "The total number of valid ATM cells received with CLP=0 and 2690 discarded by the traffic policing entity." 2691 ::= { atmVplStatEntry 4 } 2693 atmVplStatTotalCellOuts OBJECT-TYPE 2694 SYNTAX Counter32 2695 MAX-ACCESS read-only 2696 STATUS current 2697 DESCRIPTION 2698 "The total number of valid ATM cells transmitted by this 2699 VPL. This includes both CLP=0 and CLP=1 cells." 2700 ::= { atmVplStatEntry 5 } 2702 atmVplStatClp0CellOuts OBJECT-TYPE 2703 SYNTAX Counter32 2704 MAX-ACCESS read-only 2705 STATUS current 2706 DESCRIPTION 2707 "The total number of valid ATM cells transmitted with CLP=0 2708 by this VPL." 2709 ::= { atmVplStatEntry 6 } 2711 atmVplStatClp0Tagged OBJECT-TYPE 2712 SYNTAX Counter32 2713 MAX-ACCESS read-only 2714 STATUS current 2715 DESCRIPTION 2716 "The total number of valid ATM cells tagged by the traffic 2717 policing entity from CLP=0 to CLP=1." 2718 ::= { atmVplStatEntry 7 } 2720 -- 10. ATM Logical Port Configuration Table 2722 atmVplLogicalPortTable OBJECT-TYPE 2723 SYNTAX SEQUENCE OF AtmVplLogicalPortEntry 2724 MAX-ACCESS not-accessible 2725 STATUS current 2726 DESCRIPTION 2727 "Indicates whether the VPL is an ATM Logical Port interface 2728 (ifType=80)." 2729 ::= { atm2MIBObjects 10 } 2731 atmVplLogicalPortEntry OBJECT-TYPE 2732 SYNTAX AtmVplLogicalPortEntry 2733 MAX-ACCESS not-accessible 2734 STATUS current 2735 DESCRIPTION 2736 "An entry with information about the ATM Logical Port 2737 interface." 2738 AUGMENTS { atmVplEntry } 2739 ::= { atmVplLogicalPortTable 1 } 2741 AtmVplLogicalPortEntry ::= 2742 SEQUENCE { 2743 atmVplLogicalPortDef INTEGER, 2744 atmVplLogicalPortIndex InterfaceIndexOrZero 2745 } 2747 atmVplLogicalPortDef OBJECT-TYPE 2748 SYNTAX INTEGER { 2749 notLogicalIf(1), 2750 isLogicalIf(2) 2751 } 2752 MAX-ACCESS read-create 2753 STATUS current 2754 DESCRIPTION 2755 "Indicates whether the VPC at this VPL interface is an ATM 2756 Logical Port interface." 2757 DEFVAL { notLogicalIf } 2758 ::= { atmVplLogicalPortEntry 1 } 2760 atmVplLogicalPortIndex OBJECT-TYPE 2761 SYNTAX InterfaceIndexOrZero 2762 MAX-ACCESS read-only 2763 STATUS current 2764 DESCRIPTION 2765 "The ifTable index of the ATM logical port interface 2766 associated with this VPL. The distinguished value of zero 2767 indicates that the agent has not (yet) assigned such an 2768 ifTable Index. The zero value must be assigned by the agent 2769 if the value of atmVplLogicalPortDef is set to notLogicalIf, 2770 or if the VPL row is not active." 2771 ::= { atmVplLogicalPortEntry 2 } 2773 -- 11. ATM VCL Statistics Table 2775 atmVclStatTable OBJECT-TYPE 2776 SYNTAX SEQUENCE OF AtmVclStatEntry 2777 MAX-ACCESS not-accessible 2778 STATUS current 2779 DESCRIPTION 2780 "This table contains all statistics counters per VCL. It is 2781 used to monitor the usage of the VCL in terms of incoming 2782 cells and outgoing cells." 2783 ::= { atm2MIBObjects 11 } 2785 atmVclStatEntry OBJECT-TYPE 2786 SYNTAX AtmVclStatEntry 2787 MAX-ACCESS not-accessible 2788 STATUS current 2789 DESCRIPTION 2790 "Each entry in this table represents a VCL." 2791 INDEX { ifIndex, atmVclVpi, atmVclVci } 2792 ::= { atmVclStatTable 1 } 2794 AtmVclStatEntry ::= 2795 SEQUENCE { 2796 atmVclStatTotalCellIns Counter32, 2797 atmVclStatClp0CellIns Counter32, 2798 atmVclStatTotalDiscards Counter32, 2799 atmVclStatClp0Discards Counter32, 2800 atmVclStatTotalCellOuts Counter32, 2801 atmVclStatClp0CellOuts Counter32, 2802 atmVclStatClp0Tagged Counter32 2803 } 2805 atmVclStatTotalCellIns OBJECT-TYPE 2806 SYNTAX Counter32 2807 MAX-ACCESS read-only 2808 STATUS current 2809 DESCRIPTION 2810 "The total number of valid ATM cells received by this VCL 2811 including both CLP=0 and CLP=1 cells. The cells are counted 2812 prior to the application of the traffic policing." 2813 ::= { atmVclStatEntry 1 } 2815 atmVclStatClp0CellIns OBJECT-TYPE 2816 SYNTAX Counter32 2817 MAX-ACCESS read-only 2818 STATUS current 2819 DESCRIPTION 2820 "The number of valid ATM cells received by this VCL with 2821 CLP=0. The cells are counted prior to the application of 2822 the traffic policing." 2823 ::= { atmVclStatEntry 2 } 2825 atmVclStatTotalDiscards OBJECT-TYPE 2826 SYNTAX Counter32 2827 MAX-ACCESS read-only 2828 STATUS current 2829 DESCRIPTION 2830 "The total number of valid ATM cells discarded by the 2831 traffic policing entity. This includes cells originally 2832 received with CLP=0 and CLP=1." 2833 ::= { atmVclStatEntry 3 } 2835 atmVclStatClp0Discards OBJECT-TYPE 2836 SYNTAX Counter32 2837 MAX-ACCESS read-only 2838 STATUS current 2839 DESCRIPTION 2840 "The total number of valid ATM cells received with CLP=0 2841 and discarded by the traffic policing entity." 2842 ::= { atmVclStatEntry 4 } 2844 atmVclStatTotalCellOuts OBJECT-TYPE 2845 SYNTAX Counter32 2846 MAX-ACCESS read-only 2847 STATUS current 2848 DESCRIPTION 2849 "The total number of valid ATM cells transmitted by this 2850 VCL. This includes both CLP=0 and CLP=1 cells." 2851 ::= { atmVclStatEntry 5 } 2853 atmVclStatClp0CellOuts OBJECT-TYPE 2854 SYNTAX Counter32 2855 MAX-ACCESS read-only 2856 STATUS current 2857 DESCRIPTION 2858 "The total number of valid ATM cells transmitted with CLP=0 2859 by this VCL." 2860 ::= { atmVclStatEntry 6 } 2862 atmVclStatClp0Tagged OBJECT-TYPE 2863 SYNTAX Counter32 2864 MAX-ACCESS read-only 2865 STATUS current 2866 DESCRIPTION 2867 "The total number of valid ATM cells tagged by the traffic 2868 policing entity from CLP=0 to CLP=1." 2869 ::= { atmVclStatEntry 7 } 2871 -- 12. ATM AAL5 per-VCC Statistics Table 2873 atmAal5VclStatTable OBJECT-TYPE 2874 SYNTAX SEQUENCE OF AtmAal5VclStatEntry 2875 MAX-ACCESS not-accessible 2876 STATUS current 2877 DESCRIPTION 2878 "This table provides a collection of objects providing AAL5 2879 configuration and performance statistics of a VCL." 2880 ::= { atm2MIBObjects 12 } 2882 atmAal5VclStatEntry OBJECT-TYPE 2883 SYNTAX AtmAal5VclStatEntry 2884 MAX-ACCESS not-accessible 2885 STATUS current 2886 DESCRIPTION 2887 "Each entry in this table represents an AAL5 VCL, and 2888 is indexed by ifIndex values of AAL5 interfaces and 2889 the associated VPI/VCI values." 2890 INDEX { ifIndex, atmVclVpi, atmVclVci } 2891 ::= { atmAal5VclStatTable 1 } 2893 AtmAal5VclStatEntry ::= 2894 SEQUENCE { 2895 atmAal5VclInPkts Counter32, 2896 atmAal5VclOutPkts Counter32, 2897 atmAal5VclInOctets Counter32, 2898 atmAal5VclOutOctets Counter32 2899 } 2901 atmAal5VclInPkts OBJECT-TYPE 2902 SYNTAX Counter32 2903 MAX-ACCESS read-only 2904 STATUS current 2905 DESCRIPTION 2906 "The number of AAL5 CPCS PDUs received on the AAL5 VCC at 2907 the interface identified by the ifIndex." 2908 ::= { atmAal5VclStatEntry 1 } 2910 atmAal5VclOutPkts OBJECT-TYPE 2911 SYNTAX Counter32 2912 MAX-ACCESS read-only 2913 STATUS current 2914 DESCRIPTION 2915 "The number of AAL5 CPCS PDUs transmitted on the AAL5 VCC 2916 at the interface identified by the ifIndex." 2917 ::= { atmAal5VclStatEntry 2 } 2919 atmAal5VclInOctets OBJECT-TYPE 2920 SYNTAX Counter32 2921 MAX-ACCESS read-only 2922 STATUS current 2923 DESCRIPTION 2924 "The number of octets contained in AAL5 CPCS PDUs received 2925 on the AAL5 VCC at the interface identified by the ifIndex." 2926 ::= { atmAal5VclStatEntry 3 } 2928 atmAal5VclOutOctets OBJECT-TYPE 2929 SYNTAX Counter32 2930 MAX-ACCESS read-only 2931 STATUS current 2932 DESCRIPTION 2933 "The number of octets contained in AAL5 CPCS PDUs 2934 transmitted on the AAL5 VCC at the interface identified by 2935 the ifIndex." 2936 ::= { atmAal5VclStatEntry 4 } 2938 -- 13. ATM VC General Information Table 2940 atmVclGenTable OBJECT-TYPE 2941 SYNTAX SEQUENCE OF AtmVclGenEntry 2942 MAX-ACCESS not-accessible 2943 STATUS current 2944 DESCRIPTION 2945 "General Information for each VC." 2946 ::= { atm2MIBObjects 13 } 2948 atmVclGenEntry OBJECT-TYPE 2949 SYNTAX AtmVclGenEntry 2950 MAX-ACCESS not-accessible 2951 STATUS current 2952 DESCRIPTION 2953 "An entry with general information about the ATM VC." 2955 AUGMENTS { atmVclEntry } 2956 ::= { atmVclGenTable 1 } 2958 AtmVclGenEntry ::= 2959 SEQUENCE { 2960 atmVclGenSigDescrIndex AtmSigDescrParamIndex 2961 } 2963 atmVclGenSigDescrIndex OBJECT-TYPE 2964 SYNTAX AtmSigDescrParamIndex 2965 MAX-ACCESS read-create 2966 STATUS current 2967 DESCRIPTION 2968 "The value of this object identifies the row in the ATM 2969 Signalling Descriptor Parameter Table which applies to this 2970 VCL." 2971 ::= { atmVclGenEntry 1 } 2973 -- 14. ATM Interface Configuration Extension Table 2975 atmInterfaceExtTable OBJECT-TYPE 2976 SYNTAX SEQUENCE OF AtmInterfaceExtEntry 2977 MAX-ACCESS not-accessible 2978 STATUS current 2979 DESCRIPTION 2980 "This table contains ATM interface configuration and monitoring 2981 information not defined in the atmInterfaceConfTable from the 2982 ATM-MIB. This includes the type of connection setup procedures, 2983 ILMI information, and information on the VPI/VCI range." 2984 REFERENCE 2985 "Tesink, K., Editor, Definitions of Managed Objects 2986 for ATM Management, RFC 2515, Bell Communications 2987 Research, February, 1999." 2988 ::= { atm2MIBObjects 14 } 2990 atmInterfaceExtEntry OBJECT-TYPE 2991 SYNTAX AtmInterfaceExtEntry 2992 MAX-ACCESS not-accessible 2993 STATUS current 2994 DESCRIPTION 2995 "An entry extends the atmInterfaceConfEntry defined in the ATM- 2996 MIB. Each entry corresponds to an ATM interface." 2997 REFERENCE 2998 "Tesink, K., Editor, Definitions of Managed Objects 2999 for ATM Management, RFC 2515, Bell Communications 3000 Research, February, 1999." 3001 AUGMENTS { atmInterfaceConfEntry } 3002 ::= { atmInterfaceExtTable 1 } 3004 AtmInterfaceExtEntry ::= SEQUENCE { 3005 atmIntfConfigType AtmInterfaceType, 3006 atmIntfActualType AtmInterfaceType, 3007 atmIntfConfigSide INTEGER, 3008 atmIntfActualSide INTEGER, 3009 atmIntfIlmiAdminStatus BITS, 3010 atmIntfIlmiOperStatus BITS, 3011 atmIntfIlmiFsmState INTEGER, 3012 atmIntfIlmiEstablishConPollIntvl Integer32, 3013 atmIntfIlmiCheckConPollIntvl Integer32, 3014 atmIntfIlmiConPollInactFactor Integer32, 3015 atmIntfIlmiPublicPrivateIndctr INTEGER, 3016 atmInterfaceConfMaxSvpcVpi INTEGER, 3017 atmInterfaceCurrentMaxSvpcVpi INTEGER, 3018 atmInterfaceConfMaxSvccVpi INTEGER, 3019 atmInterfaceCurrentMaxSvccVpi INTEGER, 3020 atmInterfaceConfMinSvccVci INTEGER, 3021 atmInterfaceCurrentMinSvccVci INTEGER, 3022 atmIntfSigVccRxTrafficDescrIndex 3023 AtmTrafficDescrParamIndex, 3024 atmIntfSigVccTxTrafficDescrIndex 3025 AtmTrafficDescrParamIndex, 3026 atmIntfPvcFailures Counter32, 3027 atmIntfCurrentlyFailingPVpls Gauge32, 3028 atmIntfCurrentlyFailingPVcls Gauge32, 3029 atmIntfPvcFailuresTrapEnable TruthValue, 3030 atmIntfPvcNotificationInterval INTEGER, 3031 atmIntfLeafSetupFailures Counter32, 3032 atmIntfLeafSetupRequests Counter32 } 3034 atmIntfConfigType OBJECT-TYPE 3035 SYNTAX AtmInterfaceType 3036 MAX-ACCESS read-write 3037 STATUS current 3038 DESCRIPTION 3039 "The type of connection setup procedures configured for the ATM 3040 interface. Setting this variable to a value of 'other' is not 3041 allowed." 3042 DEFVAL { autoConfig } 3043 ::= { atmInterfaceExtEntry 1 } 3045 atmIntfActualType OBJECT-TYPE 3046 SYNTAX AtmInterfaceType 3047 MAX-ACCESS read-only 3048 STATUS current 3049 DESCRIPTION 3050 "The type of connection setup procedures currently being used on 3051 the interface. This may reflect a manually configured value for 3052 the interface type, or may be determined by other means such as 3053 auto-configuration. A value of `autoConfig' indicates that 3054 auto-configuration was requested but has not yet been completed." 3055 ::= { atmInterfaceExtEntry 2 } 3057 atmIntfConfigSide OBJECT-TYPE 3058 SYNTAX INTEGER { 3059 other(1), 3060 user(2), 3061 network(3) } 3062 MAX-ACCESS read-write 3063 STATUS current 3064 DESCRIPTION 3065 "The configured role of the managed entity as one side of the ATM 3066 interface. This value does not apply when the object 3067 atmIntfConfigType is set to `autoConfig', `atmfPnni1Dot0', or 3068 `atmfBici2Dot0'." 3069 ::= { atmInterfaceExtEntry 3 } 3071 atmIntfActualSide OBJECT-TYPE 3072 SYNTAX INTEGER { 3073 other(1), 3074 user(2), 3075 network(3), 3076 symmetric(4) } 3077 MAX-ACCESS read-only 3078 STATUS current 3079 DESCRIPTION 3080 "The current role used by the managed entity to represent one 3081 side of the ATM interface." 3082 ::= { atmInterfaceExtEntry 4 } 3084 atmIntfIlmiAdminStatus OBJECT-TYPE 3085 SYNTAX BITS { ilmi(0), 3086 ilmiAddressRegistration(1), 3087 ilmiConnectivity(2), 3088 ilmiPvcPvpMgmt(3), 3089 ilmiSigVccParamNegotiation(4) } 3090 MAX-ACCESS read-write 3091 STATUS current 3092 DESCRIPTION 3093 "Indicates which components of ILMI are administratively enabled 3094 on this interface. If the 'ilmi' bit is not set, then no ILMI 3095 components are operational. ILMI components other than auto- 3096 configuration that are not represented in the value have their 3097 administrative status determined according to the 'ilmi' bit. 3098 The ILMI auto-configuration component is enabled/disabled by the 3099 atmIntfConfigType object." 3100 ::= { atmInterfaceExtEntry 5 } 3102 atmIntfIlmiOperStatus OBJECT-TYPE 3103 SYNTAX BITS { ilmi(0), 3104 ilmiAddressRegistration(1), 3105 ilmiConnectivity(2), 3106 ilmiPvcPvpMgmt(3), 3107 ilmiSigVccParamNegotiation(4) } 3108 MAX-ACCESS read-only 3109 STATUS current 3110 DESCRIPTION 3111 "Indicates which components of ILMI are operational on this 3112 interface." 3113 ::= { atmInterfaceExtEntry 6 } 3115 atmIntfIlmiFsmState OBJECT-TYPE 3116 SYNTAX INTEGER { stopped(1), 3117 linkFailing(2), 3118 establishing(3), 3119 configuring(4), 3120 retrievingNetworkPrefixes(5), 3121 registeringNetworkPrefixes(6), 3122 retrievingAddresses(7), 3123 registeringAddresses(8), 3124 verifying(9) } 3125 MAX-ACCESS read-only 3126 STATUS current 3127 DESCRIPTION 3128 "Indicates the state of the ILMI Finite State Machine associated 3129 with this interface." 3131 REFERENCE 3132 "ATM Forum, Integrated Local Management Interface 3133 (ILMI) Specification, Version 4.0, af-ilmi-0065.000, 3134 September 1996, Appendix 1" 3135 ::= { atmInterfaceExtEntry 7 } 3137 atmIntfIlmiEstablishConPollIntvl OBJECT-TYPE 3138 SYNTAX Integer32 (1..65535) 3139 UNITS "seconds" 3140 MAX-ACCESS read-write 3141 STATUS current 3142 DESCRIPTION 3143 "The amount of time S between successive transmissions of ILMI 3144 messages on this interface for the purpose of detecting 3145 establishment of ILMI connectivity." 3146 REFERENCE 3147 "ATM Forum, Integrated Local Management Interface 3148 (ILMI) Specification, Version 4.0, af-ilmi-0065.000, 3149 September 1996, Section 8.3.1" 3150 DEFVAL { 1 } 3151 ::= { atmInterfaceExtEntry 8 } 3153 atmIntfIlmiCheckConPollIntvl OBJECT-TYPE 3154 SYNTAX Integer32 (0..65535) 3155 UNITS "seconds" 3156 MAX-ACCESS read-write 3157 STATUS current 3158 DESCRIPTION 3159 "The amount of time T between successive transmissions of ILMI 3160 messages on this interface for the purpose of detecting loss of 3161 ILMI connectivity. The distinguished value zero disables ILMI 3162 connectivity procedures on this interface." 3163 REFERENCE 3164 "ATM Forum, Integrated Local Management Interface 3165 (ILMI) Specification, Version 4.0, af-ilmi-0065.000, 3166 September 1996, Section 8.3.1" 3167 DEFVAL { 5 } 3168 ::= { atmInterfaceExtEntry 9 } 3170 atmIntfIlmiConPollInactFactor OBJECT-TYPE 3171 SYNTAX Integer32 (0..65535) 3172 MAX-ACCESS read-write 3173 STATUS current 3174 DESCRIPTION 3175 "The number K of consecutive polls on this interface for which no 3176 ILMI response message is received before ILMI connectivity is 3177 declared lost." 3178 REFERENCE 3179 "ATM Forum, Integrated Local Management Interface 3180 (ILMI) Specification, Version 4.0, af-ilmi-0065.000, 3181 September 1996, Section 8.3.1" 3182 DEFVAL { 4 } 3183 ::= { atmInterfaceExtEntry 10 } 3185 atmIntfIlmiPublicPrivateIndctr OBJECT-TYPE 3186 SYNTAX INTEGER { 3187 other(1), 3188 public(2), 3189 private(3) 3190 } 3191 MAX-ACCESS read-write 3192 STATUS current 3193 DESCRIPTION 3194 "Specifies whether this end of the interface is advertised in 3195 ILMI as a device of the `public' or `private' type." 3196 DEFVAL { private } 3197 ::= { atmInterfaceExtEntry 11 } 3199 atmInterfaceConfMaxSvpcVpi OBJECT-TYPE 3200 SYNTAX INTEGER (0..4095) 3201 MAX-ACCESS read-write 3202 STATUS current 3203 DESCRIPTION 3204 "The maximum VPI that the signalling stack on the ATM interface 3205 is configured to support for allocation to switched virtual path 3206 connections." 3207 ::= { atmInterfaceExtEntry 12 } 3209 atmInterfaceCurrentMaxSvpcVpi OBJECT-TYPE 3210 SYNTAX INTEGER (0..4095) 3211 MAX-ACCESS read-only 3212 STATUS current 3213 DESCRIPTION 3214 "The maximum VPI that the signalling stack on the ATM interface 3215 may currently allocate to switched virtual path connections. 3216 This value is the minimum of atmInterfaceConfMaxSvpcVpi, and the 3217 atmInterfaceMaxSvpcVpi of the interface's UNI/NNI peer. 3219 If the interface does not negotiate with its peer to determine 3220 the maximum VPI that can be allocated to SVPCs on the interface, 3221 then the value of this object must equal 3222 atmInterfaceConfMaxSvpcVpi. " 3223 ::= { atmInterfaceExtEntry 13 } 3225 atmInterfaceConfMaxSvccVpi OBJECT-TYPE 3226 SYNTAX INTEGER (0..4095) 3227 MAX-ACCESS read-write 3228 STATUS current 3229 DESCRIPTION 3230 "The maximum VPI that the signalling stack on the ATM interface 3231 is configured to support for allocation to switched virtual 3232 channel connections." 3233 ::= { atmInterfaceExtEntry 14 } 3235 atmInterfaceCurrentMaxSvccVpi OBJECT-TYPE 3236 SYNTAX INTEGER (0..4095) 3237 MAX-ACCESS read-only 3238 STATUS current 3239 DESCRIPTION 3240 "The maximum VPI that the signalling stack on the ATM interface 3241 may currently allocate to switched virtual channel connections. 3243 This value is the minimum of atmInterfaceConfMaxSvccVpi, and the 3244 atmInterfaceConfMaxSvccVpi of the interface's UNI/NNI peer. 3246 If the interface does not negotiate with its peer to determine 3247 the maximum VPI that can be allocated to SVCCs on the interface, 3248 then the value of this object must equal 3249 atmInterfaceConfMaxSvccVpi." 3250 ::= { atmInterfaceExtEntry 15 } 3252 atmInterfaceConfMinSvccVci OBJECT-TYPE 3253 SYNTAX INTEGER (0..65535) 3254 MAX-ACCESS read-write 3255 STATUS current 3256 DESCRIPTION 3257 "The minimum VCI that the signalling stack on the ATM interface 3258 is configured to support for allocation to switched virtual 3259 channel connections." 3260 ::= { atmInterfaceExtEntry 16 } 3262 atmInterfaceCurrentMinSvccVci OBJECT-TYPE 3263 SYNTAX INTEGER (0..65535) 3264 MAX-ACCESS read-only 3265 STATUS current 3266 DESCRIPTION 3267 "The minimum VCI that the signalling stack on the ATM interface 3268 may currently allocate to switched virtual channel connections. 3269 This value is the maximum of atmInterfaceConfMinSvccVci, and the 3270 atmInterfaceConfMinSvccVci of the interface's UNI/NNI peer. 3271 If the interface does not negotiate with its peer to determine 3272 the minimum VCI that can be allocated to SVCCs on the interface, 3273 then the value of this object must equal 3274 atmInterfaceConfMinSvccVci." 3275 ::= { atmInterfaceExtEntry 17 } 3277 atmIntfSigVccRxTrafficDescrIndex OBJECT-TYPE 3278 SYNTAX AtmTrafficDescrParamIndex 3279 MAX-ACCESS read-write 3280 STATUS current 3281 DESCRIPTION 3282 "This object identifies the row in the atmTrafficDescrParamTable 3283 used during ILMI auto-configuration to specify the advertised 3284 signalling VCC traffic parameters for the receive direction. 3285 The traffic descriptor resulting from ILMI auto-configuration of 3286 the signalling VCC is indicated in the atmVclTable." 3287 ::= { atmInterfaceExtEntry 18 } 3289 atmIntfSigVccTxTrafficDescrIndex OBJECT-TYPE 3290 SYNTAX AtmTrafficDescrParamIndex 3291 MAX-ACCESS read-write 3292 STATUS current 3293 DESCRIPTION 3294 "This object identifies the row in the atmTrafficDescrParamTable 3295 used during ILMI auto-configuration to specify the advertised 3296 signalling VCC traffic parameters for the transmit direction. 3297 The traffic descriptor resulting from ILMI auto-configuration of 3298 the signalling VCC is indicated in the atmVclTable." 3299 ::= { atmInterfaceExtEntry 19 } 3301 atmIntfPvcFailures OBJECT-TYPE 3302 SYNTAX Counter32 3303 MAX-ACCESS read-only 3304 STATUS current 3305 DESCRIPTION 3306 "The number of times the operational status of a PVPL or PVCL on 3307 this interface has gone down." 3308 ::= { atmInterfaceExtEntry 20 } 3310 atmIntfCurrentlyFailingPVpls OBJECT-TYPE 3311 SYNTAX Gauge32 3312 MAX-ACCESS read-only 3313 STATUS current 3314 DESCRIPTION 3315 "The current number of VPLs on this interface for which there is 3316 an active row in the atmVplTable having an atmVplConnKind value 3317 of `pvc' and an atmVplOperStatus with a value other than `up'." 3318 ::= { atmInterfaceExtEntry 21 } 3320 atmIntfCurrentlyFailingPVcls OBJECT-TYPE 3321 SYNTAX Gauge32 3322 MAX-ACCESS read-only 3323 STATUS current 3324 DESCRIPTION 3325 "The current number of VCLs on this interface for which there is 3326 an active row in the atmVclTable having an atmVclConnKind value 3327 of `pvc' and an atmVclOperStatus with a value other than `up'." 3328 ::= { atmInterfaceExtEntry 22 } 3330 atmIntfPvcFailuresTrapEnable OBJECT-TYPE 3331 SYNTAX TruthValue 3332 MAX-ACCESS read-write 3333 STATUS current 3334 DESCRIPTION 3335 "Allows the generation of traps in response to PVCL or PVPL 3336 failures on this interface." 3337 DEFVAL { false } 3338 ::= { atmInterfaceExtEntry 23 } 3340 atmIntfPvcNotificationInterval OBJECT-TYPE 3341 SYNTAX INTEGER (1..3600) 3342 UNITS "seconds" 3343 MAX-ACCESS read-write 3344 STATUS current 3345 DESCRIPTION 3346 "The minimum interval between the sending of 3347 atmIntfPvcFailuresTrap notifications for this interface." 3348 DEFVAL { 30 } 3349 ::= { atmInterfaceExtEntry 24 } 3351 atmIntfLeafSetupFailures OBJECT-TYPE 3352 SYNTAX Counter32 3353 MAX-ACCESS read-only 3354 STATUS current 3355 DESCRIPTION 3356 "Number of setup failures. For root, this is the number of 3357 rejected setup requests and for leaf, this is the number of setup 3358 failure received." 3359 ::= { atmInterfaceExtEntry 25 } 3361 atmIntfLeafSetupRequests OBJECT-TYPE 3362 SYNTAX Counter32 3363 MAX-ACCESS read-only 3364 STATUS current 3365 DESCRIPTION 3366 "Number of setup requests. For root, this includes both incoming 3367 setup request and root intiated setup requests." 3368 ::= { atmInterfaceExtEntry 26 } 3370 -- 15. ATM ILMI Service Registry Table 3372 atmIlmiSrvcRegTable OBJECT-TYPE 3373 SYNTAX SEQUENCE OF AtmIlmiSrvcRegEntry 3374 MAX-ACCESS not-accessible 3375 STATUS current 3376 DESCRIPTION 3377 "This table contains a list of all the ATM network services known 3378 by this device. 3380 The characteristics of these services are made available through 3381 the ILMI, using the ILMI general-purpose service registry MIB. 3382 These services may be made available to all ATM interfaces 3383 (atmIlmiSrvcRegIndex = 0) or to some specific ATM interfaces only 3384 (atmIlmiSrvcRegIndex = ATM interface index)." 3385 ::= { atm2MIBObjects 15 } 3387 atmIlmiSrvcRegEntry OBJECT-TYPE 3388 SYNTAX AtmIlmiSrvcRegEntry 3389 MAX-ACCESS not-accessible 3390 STATUS current 3391 DESCRIPTION 3392 "Information about a single service provider that is available to 3393 the user-side of an adjacent device through the ILMI." 3394 INDEX { atmIlmiSrvcRegIndex, 3395 atmIlmiSrvcRegServiceID, 3396 atmIlmiSrvcRegAddressIndex } 3397 ::= { atmIlmiSrvcRegTable 1 } 3399 AtmIlmiSrvcRegEntry ::= SEQUENCE { 3400 atmIlmiSrvcRegIndex InterfaceIndexOrZero, 3401 atmIlmiSrvcRegServiceID OBJECT IDENTIFIER, 3402 atmIlmiSrvcRegAddressIndex INTEGER, 3403 atmIlmiSrvcRegATMAddress AtmAddr, 3404 atmIlmiSrvcRegParm1 OCTET STRING, 3405 atmIlmiSrvcRegRowStatus RowStatus 3406 } 3408 atmIlmiSrvcRegIndex OBJECT-TYPE 3409 SYNTAX InterfaceIndexOrZero 3410 MAX-ACCESS not-accessible 3411 STATUS current 3412 DESCRIPTION 3413 "The ATM interface where the service defined in this entry can be 3414 made available to an ATM device attached to this interface. 3416 The value of 0 has a special meaning: when an ATM service is 3417 defined in an entry whose atmIlmiSrvcRegIndex is zero, the ATM 3418 service is available to ATM devices connected to any ATM 3419 interface. (default value(s)). 3421 When the user-side of an adjacent device queries the content of 3422 the ILMI service registry MIB (using the ILMI protocol), the 3423 local network-side responds with the ATM services defined in 3424 atmIlmiSrvcRegTable entries, provided that these entries are 3425 indexed by: 3427 - the corresponding ifIndex value (atmIlmiSrvcRegIndex 3428 equal to the ifIndex of the interface to which the 3429 adjacent device is connected) - zero (atmIlmiSrvcRegIndex=0)." 3430 ::= { atmIlmiSrvcRegEntry 1 } 3432 atmIlmiSrvcRegServiceID OBJECT-TYPE 3433 SYNTAX OBJECT IDENTIFIER 3434 MAX-ACCESS not-accessible 3435 STATUS current 3436 DESCRIPTION 3437 "This is the service identifier which uniquely identifies the 3438 type of service at the address provided in the table. The object 3439 identifiers for the LAN Emulation Configuration Server (LECS) and 3440 the ATM Name Server (ANS) are defined in the ATM Forum ILMI 3441 Service Registry MIB. The object identifiers for the ATMARP 3442 Server, the Multicast Address Resolution Server (MARS), and the 3443 NHRP Server (NHS) are defined in RFC 2601, RFC 2602, and RFC 3444 2603, respectively." 3445 ::= { atmIlmiSrvcRegEntry 2 } 3447 atmIlmiSrvcRegAddressIndex OBJECT-TYPE 3448 SYNTAX INTEGER (1..2147483647) 3449 MAX-ACCESS not-accessible 3450 STATUS current 3451 DESCRIPTION 3452 "An arbitrary integer to differentiate multiple rows containing 3453 different ATM addresses for the same service on the same 3454 interface. This number need NOT be the same as the corresponding 3455 ILMI atmfSrvcRegAddressIndex MIB object." 3456 ::= { atmIlmiSrvcRegEntry 3 } 3458 atmIlmiSrvcRegATMAddress OBJECT-TYPE 3459 SYNTAX AtmAddr 3460 MAX-ACCESS read-create 3461 STATUS current 3462 DESCRIPTION 3463 "This is the full address of the service. The user-side of the 3464 adjacent device may use this address to establish a connection 3465 with the service." 3466 ::= { atmIlmiSrvcRegEntry 4 } 3468 atmIlmiSrvcRegParm1 OBJECT-TYPE 3469 SYNTAX OCTET STRING (SIZE(1..255)) 3470 MAX-ACCESS read-create 3471 STATUS current 3472 DESCRIPTION 3473 "An octet string used according to the value of 3474 atmIlmiSrvcRegServiceID." 3475 ::= { atmIlmiSrvcRegEntry 5 } 3477 atmIlmiSrvcRegRowStatus OBJECT-TYPE 3478 SYNTAX RowStatus 3479 MAX-ACCESS read-create 3480 STATUS current 3481 DESCRIPTION 3482 "This object is used to create or destroy an entry from this 3483 table." 3485 ::= { atmIlmiSrvcRegEntry 6 } 3487 -- 16. ILMI Network Prefix Table 3489 atmIlmiNetworkPrefixTable OBJECT-TYPE 3490 SYNTAX SEQUENCE OF AtmIlmiNetworkPrefixEntry 3491 MAX-ACCESS not-accessible 3492 STATUS current 3493 DESCRIPTION 3494 "A table specifying per-interface network prefix(es) supplied by 3495 the network side of the UNI during ILMI address registration. 3496 When no network prefixes are specified for a particular 3497 interface, one or more network prefixes based on the switch 3498 address(es) may be used for ILMI address registration." 3499 ::= { atm2MIBObjects 16 } 3501 atmIlmiNetworkPrefixEntry OBJECT-TYPE 3502 SYNTAX AtmIlmiNetworkPrefixEntry 3503 MAX-ACCESS not-accessible 3504 STATUS current 3505 DESCRIPTION 3506 "Information about a single network prefix supplied by the 3507 network side of the UNI during ILMI address registration. Note 3508 that the index variable atmIlmiNetPrefixPrefix is a variable- 3509 length string, and as such the rule for variable-length strings 3510 in section 7.7 of RFC 2578 applies." 3511 INDEX { ifIndex, 3512 atmIlmiNetPrefixPrefix } 3513 ::= { atmIlmiNetworkPrefixTable 1 } 3515 AtmIlmiNetworkPrefixEntry ::= 3516 SEQUENCE { 3517 atmIlmiNetPrefixPrefix AtmIlmiNetworkPrefix, 3518 atmIlmiNetPrefixRowStatus RowStatus 3519 } 3521 atmIlmiNetPrefixPrefix OBJECT-TYPE 3522 SYNTAX AtmIlmiNetworkPrefix 3523 MAX-ACCESS not-accessible 3524 STATUS current 3525 DESCRIPTION 3526 "The network prefix specified for use in ILMI address 3527 registration." 3528 ::= { atmIlmiNetworkPrefixEntry 1 } 3530 atmIlmiNetPrefixRowStatus OBJECT-TYPE 3531 SYNTAX RowStatus 3532 MAX-ACCESS read-create 3533 STATUS current 3534 DESCRIPTION 3535 "Used to create, delete, activate and de-activate network 3536 prefixes used in ILMI address registration." 3538 ::= { atmIlmiNetworkPrefixEntry 2 } 3540 -- 17. ATM Switch Address Table 3542 atmSwitchAddressTable OBJECT-TYPE 3543 SYNTAX SEQUENCE OF AtmSwitchAddressEntry 3544 MAX-ACCESS not-accessible 3545 STATUS current 3546 DESCRIPTION 3547 "This table contains one or more ATM endsystem addresses on a 3548 per-switch basis. These addresses are used to identify the 3549 switch. When no ILMI network prefixes are configured for certain 3550 interfaces, network prefixes based on the switch address(es) may 3551 be used for ILMI address registration." 3552 ::= { atm2MIBObjects 17 } 3554 atmSwitchAddressEntry OBJECT-TYPE 3555 SYNTAX AtmSwitchAddressEntry 3556 MAX-ACCESS not-accessible 3557 STATUS current 3558 DESCRIPTION 3559 "An entry in the ATM Switch Address table." 3560 INDEX { atmSwitchAddressIndex } 3561 ::= { atmSwitchAddressTable 1 } 3563 AtmSwitchAddressEntry ::= 3564 SEQUENCE { 3565 atmSwitchAddressIndex Integer32, 3566 atmSwitchAddressAddress OCTET STRING, 3567 atmSwitchAddressRowStatus RowStatus 3568 } 3570 atmSwitchAddressIndex OBJECT-TYPE 3571 SYNTAX Integer32 (1..65535) 3572 MAX-ACCESS not-accessible 3573 STATUS current 3574 DESCRIPTION 3575 "An arbitrary index used to enumerate the ATM endsystem addresses 3576 for this switch." 3577 ::= { atmSwitchAddressEntry 1 } 3579 atmSwitchAddressAddress OBJECT-TYPE 3580 SYNTAX OCTET STRING (SIZE(13|20)) 3581 MAX-ACCESS read-create 3582 STATUS current 3583 DESCRIPTION 3584 "An ATM endsystem address or address prefix used to identify this 3585 switch. When no ESI or SEL field is specified, the switch may 3586 generate the ESI and SEL fields automatically to obtain a 3587 complete 20-byte ATM endsystem address." 3588 ::= { atmSwitchAddressEntry 2 } 3590 atmSwitchAddressRowStatus OBJECT-TYPE 3591 SYNTAX RowStatus 3592 MAX-ACCESS read-create 3593 STATUS current 3594 DESCRIPTION 3595 "Used to create, delete, activate, and de-activate addresses used 3596 to identify this switch." 3597 ::= { atmSwitchAddressEntry 3 } 3599 -- 18. ATM VP Cross-Connect Extension Table 3601 atmVpCrossConnectXTable OBJECT-TYPE 3602 SYNTAX SEQUENCE OF AtmVpCrossConnectXEntry 3603 MAX-ACCESS not-accessible 3604 STATUS current 3605 DESCRIPTION 3606 "This table contains one row per VP Cross-Connect represented in 3607 the atmVpCrossConnectTable." 3608 ::= { atm2MIBObjects 18 } 3610 atmVpCrossConnectXEntry OBJECT-TYPE 3611 SYNTAX AtmVpCrossConnectXEntry 3612 MAX-ACCESS not-accessible 3613 STATUS current 3614 DESCRIPTION 3615 "Information about a particular ATM VP Cross-Connect. 3616 Each entry provides an two objects that name the Cross-Connect. 3617 One is assigned by the Service User and the other by the Service 3618 Provider." 3619 AUGMENTS { atmVpCrossConnectEntry } 3620 ::= { atmVpCrossConnectXTable 1 } 3622 AtmVpCrossConnectXEntry ::= SEQUENCE { 3623 atmVpCrossConnectUserName SnmpAdminString, 3624 atmVpCrossConnectProviderName SnmpAdminString 3625 } 3627 atmVpCrossConnectUserName OBJECT-TYPE 3628 SYNTAX SnmpAdminString (SIZE(0..255)) 3629 MAX-ACCESS read-create 3630 STATUS current 3631 DESCRIPTION 3632 "This is a service user assigned textual representation of a VPC 3633 PVC." 3634 ::= { atmVpCrossConnectXEntry 1 } 3636 atmVpCrossConnectProviderName OBJECT-TYPE 3637 SYNTAX SnmpAdminString (SIZE(0..255)) 3638 MAX-ACCESS read-only 3639 STATUS current 3640 DESCRIPTION 3641 "This is a system supplied textual representation of VPC PVC. It 3642 is assigned by the service provider." 3643 ::= { atmVpCrossConnectXEntry 2 } 3645 -- 19. ATM VC Cross-Connect Extension Table 3647 atmVcCrossConnectXTable OBJECT-TYPE 3648 SYNTAX SEQUENCE OF AtmVcCrossConnectXEntry 3649 MAX-ACCESS not-accessible 3650 STATUS current 3651 DESCRIPTION 3652 "This table contains one row per VC Cross-Connect represented in 3653 the atmVcCrossConnectTable." 3654 ::= { atm2MIBObjects 19 } 3656 atmVcCrossConnectXEntry OBJECT-TYPE 3657 SYNTAX AtmVcCrossConnectXEntry 3658 MAX-ACCESS not-accessible 3659 STATUS current 3660 DESCRIPTION 3661 "Information about a particular ATM VC Cross-Connect. 3662 Each entry provides an two objects that name the Cross-Connect. 3663 One is assigned by the Service User and the other by the Service 3664 Provider." 3665 AUGMENTS { atmVcCrossConnectEntry } 3666 ::= { atmVcCrossConnectXTable 1 } 3668 AtmVcCrossConnectXEntry ::= SEQUENCE { 3669 atmVcCrossConnectUserName SnmpAdminString, 3670 atmVcCrossConnectProviderName SnmpAdminString 3671 } 3673 atmVcCrossConnectUserName OBJECT-TYPE 3674 SYNTAX SnmpAdminString (SIZE(0..255)) 3675 MAX-ACCESS read-create 3676 STATUS current 3677 DESCRIPTION 3678 "This is a service user assigned textual representation of a VCC 3679 PVC." 3680 ::= { atmVcCrossConnectXEntry 1 } 3682 atmVcCrossConnectProviderName OBJECT-TYPE 3683 SYNTAX SnmpAdminString (SIZE(0..255)) 3684 MAX-ACCESS read-only 3685 STATUS current 3686 DESCRIPTION 3687 "This is a system supplied textual representation of VCC PVC. It 3688 is assigned by the service provider." 3689 ::= { atmVcCrossConnectXEntry 2 } 3691 -- 20. Currently Failing PVPL Table 3693 atmCurrentlyFailingPVplTable OBJECT-TYPE 3694 SYNTAX SEQUENCE OF AtmCurrentlyFailingPVplEntry 3695 MAX-ACCESS not-accessible 3696 STATUS current 3697 DESCRIPTION 3698 "A table indicating all VPLs for which there is an active row in 3699 the atmVplTable having an atmVplConnKind value of `pvc' and an 3700 atmVplOperStatus with a value other than `up'." 3701 ::= { atm2MIBObjects 20 } 3703 atmCurrentlyFailingPVplEntry OBJECT-TYPE 3704 SYNTAX AtmCurrentlyFailingPVplEntry 3705 MAX-ACCESS not-accessible 3706 STATUS current 3707 DESCRIPTION 3708 "Each entry in this table represents a VPL for which the 3709 atmVplRowStatus is `active', the atmVplConnKind is `pvc', and the 3710 atmVplOperStatus is other than `up'." 3711 INDEX { ifIndex, atmVplVpi } 3712 ::= { atmCurrentlyFailingPVplTable 1 } 3714 AtmCurrentlyFailingPVplEntry ::= 3715 SEQUENCE { 3716 atmCurrentlyFailingPVplTimeStamp TimeStamp 3717 } 3719 atmCurrentlyFailingPVplTimeStamp OBJECT-TYPE 3720 SYNTAX TimeStamp 3721 MAX-ACCESS read-only 3722 STATUS current 3723 DESCRIPTION 3724 "The time at which this PVPL began to fail." 3725 ::= { atmCurrentlyFailingPVplEntry 1 } 3727 -- 21. Currently Failing PVCL Table 3729 atmCurrentlyFailingPVclTable OBJECT-TYPE 3730 SYNTAX SEQUENCE OF AtmCurrentlyFailingPVclEntry 3731 MAX-ACCESS not-accessible 3732 STATUS current 3733 DESCRIPTION 3734 "A table indicating all VCLs for which there is an active row in 3735 the atmVclTable having an atmVclConnKind value of `pvc' and an 3736 atmVclOperStatus with a value other than `up'." 3737 ::= { atm2MIBObjects 21 } 3739 atmCurrentlyFailingPVclEntry OBJECT-TYPE 3740 SYNTAX AtmCurrentlyFailingPVclEntry 3741 MAX-ACCESS not-accessible 3742 STATUS current 3743 DESCRIPTION 3744 "Each entry in this table represents a VCL for which the 3745 atmVclRowStatus is `active', the atmVclConnKind is `pvc', and the 3746 atmVclOperStatus is other than `up'." 3747 INDEX { ifIndex, atmVclVpi, atmVclVci } 3748 ::= { atmCurrentlyFailingPVclTable 1 } 3750 AtmCurrentlyFailingPVclEntry ::= 3751 SEQUENCE { 3752 atmCurrentlyFailingPVclTimeStamp TimeStamp 3753 } 3755 atmCurrentlyFailingPVclTimeStamp OBJECT-TYPE 3756 SYNTAX TimeStamp 3757 MAX-ACCESS read-only 3758 STATUS current 3759 DESCRIPTION 3760 "The time at which this PVCL began to fail." 3761 ::= { atmCurrentlyFailingPVclEntry 1 } 3763 -- ATM PVC Traps 3765 atmPvcTraps OBJECT IDENTIFIER ::= { atm2MIBTraps 1 } 3767 atmPvcTrapsPrefix OBJECT IDENTIFIER ::= { atmPvcTraps 0 } 3769 atmIntfPvcFailuresTrap NOTIFICATION-TYPE 3770 OBJECTS { ifIndex, atmIntfPvcFailures, 3771 atmIntfCurrentlyFailingPVpls, 3772 atmIntfCurrentlyFailingPVcls } 3773 STATUS current 3774 DESCRIPTION 3775 "A notification indicating that one or more PVPLs or PVCLs on 3776 this interface has failed since the last atmPvcFailuresTrap was 3777 sent. If this trap has not been sent for the last 3778 atmIntfPvcNotificationInterval, then it will be sent on the next 3779 increment of atmIntfPvcFailures." 3780 ::= { atmPvcTrapsPrefix 1 } 3782 -- Conformance Information 3784 atm2MIBConformance OBJECT IDENTIFIER ::= {atm2MIB 3} 3786 atm2MIBGroups OBJECT IDENTIFIER ::= {atm2MIBConformance 1} 3788 atm2MIBCompliances OBJECT IDENTIFIER ::= {atm2MIBConformance 2} 3790 -- Compliance Statements 3792 atm2MIBCompliance MODULE-COMPLIANCE 3793 STATUS current 3794 DESCRIPTION 3795 "The compliance statement for SNMP entities which represent ATM 3796 interfaces. The compliance statements are used to determine if a 3797 particular group or object applies to hosts, networks/switches, 3798 or both. The Common group is defined as applicable to all three." 3800 MODULE -- this module 3801 MANDATORY-GROUPS { atmCommonGroup } 3803 -- Objects in the ATM Switch/Service/Host Group 3805 GROUP atmCommonStatsGroup 3806 DESCRIPTION 3807 "This group is mandatory for systems that are supporting 3808 per-VPC or per-VCC counters." 3810 OBJECT atmVplLogicalPortDef 3811 MIN-ACCESS read-only 3812 DESCRIPTION 3813 "This object is mandatory for systems support ATM Logical 3814 Port interfaces." 3816 OBJECT atmIntfSigVccRxTrafficDescrIndex 3817 DESCRIPTION 3818 "This object is mandatory for systems that support negotiation of 3819 signalling VCC traffic parameters through ILMI." 3821 OBJECT atmIntfSigVccTxTrafficDescrIndex 3822 DESCRIPTION 3823 "This object is mandatory for systems that support negotiation of 3824 signalling VCC traffic parameters through ILMI." 3826 OBJECT atmCurrentlyFailingPVplTimeStamp 3827 DESCRIPTION 3828 "This object is optional." 3830 OBJECT atmCurrentlyFailingPVclTimeStamp 3831 DESCRIPTION 3832 "This object is optional." 3834 OBJECT atmIntfLeafSetupFailures 3835 DESCRIPTION 3836 "This object is optional." 3838 OBJECT atmIntfLeafSetupRequests 3839 DESCRIPTION 3840 "This object is optional." 3842 -- Objects in the ATM Switch/Service Group 3844 GROUP atmSwitchServcGroup 3845 DESCRIPTION 3846 "This group is mandatory for a Switch/Service that implements 3847 ATM interfaces." 3849 OBJECT atmIfRegAddrRowStatus 3850 MIN-ACCESS read-only 3851 DESCRIPTION 3852 "Write access is not required, and only one of the six enumerated 3853 values for the RowStatus textual convention need be supported, 3854 specifically: active(1)." 3856 OBJECT atmSvcVpCrossConnectRowStatus 3857 MIN-ACCESS read-only 3858 DESCRIPTION 3859 "Write access is not required, and only one of the six enumerated 3860 values for the RowStatus textual convention need be supported, 3861 specifically: active(1)" 3863 OBJECT atmSvcVcCrossConnectRowStatus 3864 MIN-ACCESS read-only 3865 DESCRIPTION 3866 "Write access is not required, and only one of the six enumerated 3867 values for the RowStatus textual convention need be supported, 3868 specifically: active(1)" 3870 -- Objects in the ATM Switch/Service Signalling Group 3872 GROUP atmSwitchServcSigGroup 3873 DESCRIPTION 3874 "This group's write access is not required." 3876 -- Objects in the ATM Switch/Service Notifications Group 3878 GROUP atmSwitchServcNotifGroup 3879 DESCRIPTION 3880 "This group is optional for systems implementing support for an ATM 3881 Switch or an ATM Network Service." 3883 -- Objects in the ATM Switch Group 3885 GROUP atmSwitchGroup 3886 DESCRIPTION 3887 "This group is optional for a switch that implements ATM interfaces." 3889 -- Objects in the ATM Service Group 3891 GROUP atmServcGroup 3892 DESCRIPTION 3893 "This group is mandatory for systems implementing support for an ATM 3894 Network Service." 3896 -- Objects in the ATM Host Group 3898 GROUP atmHostGroup 3899 DESCRIPTION 3900 "This group is mandatory for a Host that implements ATM interfaces." 3902 OBJECT atmVclAddrType 3903 MIN-ACCESS read-only 3904 DESCRIPTION 3905 "Write access is not required." 3907 OBJECT atmVclAddrRowStatus 3908 MIN-ACCESS read-only 3909 DESCRIPTION 3910 "Write access is not required, and only one of the six enumerated 3911 values for the RowStatus textual convention need be supported, 3912 specifically: active(1)." 3914 -- ATM Host Sig Descriptor Parameter Group 3916 GROUP atmHostSigDescrGroup 3917 DESCRIPTION 3918 "This group is mandatory for a Host that implements ATM interfaces. 3919 Write access is not required for this group." 3921 ::= { atm2MIBCompliances 1 } 3923 -- ********************************************** 3925 -- Units of Conformance 3926 -- Mandatory for ATM hosts and switch/service providers 3928 atmCommonGroup OBJECT-GROUP 3930 OBJECTS { 3931 atmSigSSCOPConEvents, 3932 atmSigSSCOPErrdPdus, 3933 atmSigDetectSetupAttempts, 3934 atmSigEmitSetupAttempts, 3935 atmSigDetectUnavailRoutes, 3936 atmSigEmitUnavailRoutes, 3937 atmSigDetectUnavailResrcs, 3938 atmSigEmitUnavailResrcs, 3939 atmSigDetectCldPtyEvents, 3940 atmSigEmitCldPtyEvents, 3941 atmSigDetectMsgErrors, 3942 atmSigEmitMsgErrors, 3943 atmSigDetectClgPtyEvents, 3944 atmSigEmitClgPtyEvents, 3945 atmSigDetectTimerExpireds, 3946 atmSigEmitTimerExpireds, 3947 atmSigDetectRestarts, 3948 atmSigEmitRestarts, 3949 atmSigInEstabls, 3950 atmSigOutEstabls, 3951 atmVplLogicalPortDef, 3952 atmVplLogicalPortIndex, 3953 atmInterfaceConfMaxSvpcVpi, 3954 atmInterfaceCurrentMaxSvpcVpi, 3955 atmInterfaceConfMaxSvccVpi, 3956 atmInterfaceCurrentMaxSvccVpi, 3957 atmInterfaceConfMinSvccVci, 3958 atmInterfaceCurrentMinSvccVci, 3959 atmIntfSigVccRxTrafficDescrIndex, 3960 atmIntfSigVccTxTrafficDescrIndex, 3961 atmIntfPvcFailures, 3962 atmIntfCurrentlyFailingPVpls, 3963 atmIntfCurrentlyFailingPVcls, 3964 atmIntfPvcNotificationInterval, 3965 atmIntfPvcFailuresTrapEnable, 3966 atmIntfLeafSetupFailures, 3967 atmIntfLeafSetupRequests, 3968 atmIntfConfigType, 3969 atmIntfActualType, 3970 atmIntfConfigSide, 3971 atmIntfActualSide, 3972 atmIntfIlmiAdminStatus, 3973 atmIntfIlmiOperStatus, 3974 atmIntfIlmiFsmState, 3975 atmIntfIlmiEstablishConPollIntvl, 3976 atmIntfIlmiCheckConPollIntvl, 3977 atmIntfIlmiConPollInactFactor, 3978 atmIntfIlmiPublicPrivateIndctr, 3979 atmCurrentlyFailingPVplTimeStamp, 3980 atmCurrentlyFailingPVclTimeStamp 3981 } 3983 STATUS current 3984 DESCRIPTION 3985 "A collection of objects providing information 3986 for a Switch/Service/Host that implements 3987 ATM interfaces." 3988 ::= { atm2MIBGroups 1 } 3990 atmCommonStatsGroup OBJECT-GROUP 3992 OBJECTS { 3993 atmVclStatTotalCellIns, 3994 atmVclStatClp0CellIns, 3995 atmVclStatTotalDiscards, 3996 atmVclStatClp0Discards, 3997 atmVclStatTotalCellOuts, 3998 atmVclStatClp0CellOuts, 3999 atmVclStatClp0Tagged, 4000 atmVplStatTotalCellIns, 4001 atmVplStatClp0CellIns, 4002 atmVplStatTotalDiscards, 4003 atmVplStatClp0Discards, 4004 atmVplStatTotalCellOuts, 4005 atmVplStatClp0CellOuts, 4006 atmVplStatClp0Tagged 4007 } 4009 STATUS current 4010 DESCRIPTION 4011 "A collection of objects providing information 4012 for a Switch/Service/Host that implements 4013 ATM VCL and VPL Statistics" 4014 ::= { atm2MIBGroups 2 } 4016 atmSwitchServcGroup OBJECT-GROUP 4018 OBJECTS { 4019 atmIlmiSrvcRegATMAddress, 4020 atmIlmiSrvcRegParm1, 4021 atmIlmiSrvcRegRowStatus, 4022 atmIlmiNetPrefixRowStatus, 4023 atmSvcVpCrossConnectCreationTime, 4024 atmSvcVpCrossConnectRowStatus, 4025 atmSvcVcCrossConnectCreationTime, 4026 atmSvcVcCrossConnectRowStatus, 4027 atmIfRegAddrAddressSource, 4028 atmIfRegAddrOrgScope, 4029 atmIfRegAddrRowStatus} 4030 STATUS current 4031 DESCRIPTION 4032 "A collection of objects providing information 4033 for a Switch/Service that implements ATM interfaces." 4034 ::= { atm2MIBGroups 3 } 4036 atmSwitchServcSigGroup OBJECT-GROUP 4038 OBJECTS { 4039 atmSigSupportClgPtyNumDel, 4040 atmSigSupportClgPtySubAddr, 4041 atmSigSupportCldPtySubAddr, 4042 atmSigSupportHiLyrInfo, 4043 atmSigSupportLoLyrInfo, 4044 atmSigSupportBlliRepeatInd, 4045 atmSigSupportAALInfo, 4046 atmSigSupportPrefCarrier} 4047 STATUS current 4048 DESCRIPTION 4049 "A collection of objects providing information 4050 for a Switch/Service that implements ATM signalling." 4051 ::= { atm2MIBGroups 4 } 4053 atmSwitchServcNotifGroup NOTIFICATION-GROUP 4055 NOTIFICATIONS { atmIntfPvcFailuresTrap } 4056 STATUS current 4057 DESCRIPTION 4058 "A collection of notifications providing information 4059 for a Switch/Service that implements ATM interfaces." 4060 ::= { atm2MIBGroups 5 } 4062 atmSwitchGroup OBJECT-GROUP 4063 OBJECTS { 4064 atmSwitchAddressAddress, 4065 atmSwitchAddressRowStatus } 4066 STATUS current 4067 DESCRIPTION 4068 "A collection of objects providing information 4069 for an ATM switch." 4070 ::= { atm2MIBGroups 6 } 4072 atmServcGroup OBJECT-GROUP 4074 OBJECTS { 4075 atmVpCrossConnectUserName, 4076 atmVpCrossConnectProviderName, 4077 atmVcCrossConnectUserName, 4078 atmVcCrossConnectProviderName } 4079 STATUS current 4080 DESCRIPTION 4081 "A collection of objects providing information 4082 for an ATM Network Service." 4083 ::= { atm2MIBGroups 7 } 4085 atmHostGroup OBJECT-GROUP 4087 OBJECTS { 4088 atmAal5VclInPkts, 4089 atmAal5VclOutPkts, 4090 atmAal5VclInOctets, 4091 atmAal5VclOutOctets, 4092 atmVclAddrType, 4093 atmVclAddrRowStatus, 4094 atmAddrVclAddrType, 4095 atmVclGenSigDescrIndex} 4096 STATUS current 4097 DESCRIPTION 4098 "A collection of objects providing information 4099 for a Host that implements ATM interfaces." 4100 ::= { atm2MIBGroups 8 } 4102 atmHostSigDescrGroup OBJECT-GROUP 4104 OBJECTS { 4105 atmSigDescrParamAalType, 4106 atmSigDescrParamAalSscsType, 4107 atmSigDescrParamBhliType, 4108 atmSigDescrParamBhliInfo, 4109 atmSigDescrParamBbcConnConf, 4110 atmSigDescrParamBlliLayer2, 4111 atmSigDescrParamBlliLayer3, 4112 atmSigDescrParamBlliPktSize, 4113 atmSigDescrParamBlliSnapId, 4114 atmSigDescrParamBlliOuiPid, 4115 atmSigDescrParamRowStatus} 4116 STATUS current 4117 DESCRIPTION 4118 "A collection of objects providing information 4119 for a Host that implements ATM interfaces." 4120 ::= { atm2MIBGroups 9 } 4122 END 4124 6. Acknowledgments 4126 This document is a product of the AToMMIB Working Group. Special thanks 4127 go to Gary Hanson of ADC Telecommunications for his quality contributions 4128 to this specification. 4130 7. References 4132 7.1 Normative References 4134 [RFC2515] Tesink, K., "Definitions of Managed Objects for ATM 4135 Management", RFC 2515, Bell Communications Research, 4136 February, 1999. 4138 [ATM Forum 3.0] ATM Forum, "ATM User-Network Interface 4139 Specification, Version 3.0 (UNI 3.0)", 4140 September 1993. 4142 [ATM Forum UNI 3.1] ATM Forum, "ATM User-Network Interface 4143 Specification, Version 3.1 (UNI 3.1)", 4144 September 1994. 4146 [ATM Forum LANE] ATM Forum, "LAN Emulation Client Management 4147 Specification, Version 1.0", af-lane-0038.000, 4148 September 1995. 4150 [RFC1694] Brown, T., Tesink, K., "Definitions of Managed Objects 4151 for SMDS Interfaces using SMIv2", RFC 1694, August 1994. 4153 [ATM Forum ILMI] ATM Forum, "Integrated Local Management Interface 4154 (ILMI) Specification, Version 4.0", 4155 af-ilmi-0065.000, September 1996. 4157 [RFC2558] Tesink, K., "Definitions of Managed Objects for the 4158 SONET/SDH Interface Type", RFC 2558, March 1999. 4160 [RFC2496] Fowler, D., "Definitions of Managed Objects for the DS3/E3 4161 Interface Type", RFC 2496, January 1999. 4163 [RFC1905] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 4164 "Protocol Operations for Version 2 of the Simple Network 4165 Management Protocol (SNMPv2)", RFC 1905, January 1996. 4167 [RFC1906] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 4168 "Transport Mappings for Version 2 of the Simple Network 4169 Management Protocol (SNMPv2)", RFC 1906, January 1996. 4171 [RFC2026] Bradner S., "The Internet Standards Process - 4172 Revision 3", October 1996. 4174 [RFC2028] Hovey R., S. Bradner, "The Organizations Involved in 4175 the IETF Standards Process", October 1996. 4177 [RFC2493] K. Tesink "Textual Conventions for MIB Modules Using 4178 Performance History Based on 15 Minute Intervals" 4179 RFC 2493, January 1999. 4181 [RFC2571] Harrington, D., Presuhn, R., and B. Wijnen, "An 4182 Architecture for Describing SNMP Management Frameworks", 4183 RFC 2571, April 1999. 4185 [RFC2572] Case, J., Harrington D., Presuhn R., and B. Wijnen, 4186 "Message Processing and Dispatching for the Simple 4187 Network Management Protocol (SNMP)", RFC 2572, April 1999. 4189 [RFC2573] Levi, D., Meyer, P., and B. Stewart, "SNMPv3 4190 Applications", RFC 2573, April 1999. 4192 [RFC2574] Blumenthal, U., and B. Wijnen, "User-based Security Model 4193 (USM) for version 3 of the Simple Network Management 4194 Protocol (SNMPv3)", RFC 2574, April 1999. 4196 [RFC2575] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based 4197 Access Control Model (VACM) for the Simple Network 4198 Management Protocol (SNMP)", RFC 2575, April 1999. 4200 [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 4201 Rose, M., and S. Waldbusser, "Structure of Management 4202 Information Version 2 (SMIv2)", STD 58, RFC 2578, April 4203 1999. 4205 [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 4206 Rose, M., and S. Waldbusser, "Textual Conventions for 4207 SMIv2", STD 58, RFC 2579, April 1999. 4209 [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 4210 Rose, M., and S. Waldbusser, "Conformance Statements for 4211 SMIv2", STD 58, RFC 2580, April 1999. 4213 [RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group 4214 MIB", RFC 2863, June 2000. 4216 7.2 Informative References 4218 [RFC1157] Case, J., Fedor, M., Schoffstall, M., and J. Davin, 4219 "Simple Network Management Protocol", STD 15, RFC 1157, 4220 May 1990. 4222 [RFC2570] Case, J., Mundy, R., Partain, D., and B. Stewart, 4223 "Introduction to Version 3 of the Internet-standard 4224 Network Management Framework", RFC 2570, April 1999. 4226 [RFC1155] Rose, M., and K. McCloghrie, "Structure and 4227 Identification of Management Information for 4228 TCP/IP-based Internets", STD 16, RFC 1155, May 1990. 4230 [RFC1212] Rose, M. and K. McCloghrie, "Concise MIB Definitions", 4231 STD 16, RFC 1212, March 1991. 4233 [RFC1215] M. Rose, "A Convention for Defining Traps for use with 4234 the SNMP", RFC 1215, March 1991. 4236 [RFC1901] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 4237 "Introduction to Community-based SNMPv2", RFC 1901, 4238 January 1996. 4240 [RFC3410] Case, J., Mundy, R., Partain, D. and B. Stewart, 4241 "Introduction and Applicability Statements for Internet- 4242 Standard Management Framework", RFC 3410, December 2002. 4244 8. Security Considerations 4246 There are a number of management objects defined in this MIB module 4247 with a MAX-ACCESS clause of read-write and/or read-create. Such 4248 objects may be considered sensitive or vulnerable in some network 4249 environments. The support for SET operations in a non-secure 4250 environment without proper protection can have a negative effect on 4251 network operations. These are the tables and objects and their 4252 sensitivity/vulnerability: 4254 Table Sensitivity/vulnerability 4256 1. atmSvcVpCrossConnectTable Deletion of VP cross-connects 4257 2. atmSvcVcCrossConnectTable Deletion of VC cross-connects 4258 3. atmSigStatTable Signalling read-only statistics 4259 4. atmSigSupportTable Signalling configuration params 4260 5. atmSigDescrParamTable Signalling configuration params 4261 6. atmIfRegisteredAddrTable Interface address table 4262 7. atmVclAddrTable VCL/Address mapping table 4263 8. atmAddrVclTable VCL/Address mapping table 4264 (read-only) 4265 9. atmVplStatTable VPL statistics (read-only) 4266 10. atmVplLogicalPortTable VPL logical port configuration 4267 11. atmVclStatTable VCL statistics (read-only) 4268 12. atmAal5VclStatTable AAL5 statistics (read-only) 4269 13. atmVclGenTable Signalling configuration 4270 14. atmInterfaceExtTable Interface configuration 4271 15. atmIlmiSrvcRegTable ILMI config params 4272 16. atmIlmiNetworkPrefixTable ILMI config params 4273 17. atmSwitchAddressTable Switch address info 4274 18. atmVpCrossConnectXTable VP cross-connect params 4275 19. atmVcCrossConnectXTable VC cross-connect params 4276 20. atmCurrentlyFailingPVplTable PVPL status info (read-only) 4277 21. atmCurrentlyFailingPVclTable PVCL status info (read-only) 4279 Some of the readable objects in this MIB module (i.e., objects with a 4280 MAX-ACCESS other than not-accessible) may be considered sensitive or 4281 vulnerable in some network environments. It is thus important to 4282 control even GET and/or NOTIFY access to these objects and possibly 4283 to even encrypt the values of these objects when sending them over 4284 the network via SNMP. 4286 SNMP versions prior to SNMPv3 did not include adequate security. 4287 Even if the network itself is secure (for example by using IPSec), 4288 even then, there is no control as to who on the secure network is 4289 allowed to access and GET/SET (read/change/create/delete) the objects 4290 in this MIB module. 4292 It is RECOMMENDED that implementers consider the security features as 4293 provided by the SNMPv3 framework (see [RFC3410], section 8), 4294 including full support for the SNMPv3 cryptographic mechanisms (for 4295 authentication and privacy). 4297 Further, deployment of SNMP versions prior to SNMPv3 is NOT 4298 RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to 4299 enable cryptographic security. It is then a customer/operator 4300 responsibility to ensure that the SNMP entity giving access to an 4301 instance of this MIB module is properly configured to give access to 4302 the objects only to those principals (users) that have legitimate 4303 rights to indeed GET or SET (change/create/delete) them. 4305 9. Intellectual Property Notice 4307 The IETF takes no position regarding the validity or scope of any 4308 intellectual property or other rights that might be claimed to 4309 pertain to the implementation or use of the technology described in 4310 this document or the extent to which any license under such rights 4311 might or might not be available; neither does it represent that it 4312 has made any effort to identify any such rights. Information on the 4313 IETF's procedures with respect to rights in standards-track and 4314 standards-related documentation can be found in BCP-11. Copies of 4315 claims of rights made available for publication and any assurances of 4316 licenses to be made available, or the result of an attempt made to 4317 obtain a general license or permission for the use of such 4318 proprietary rights by implementers or users of this specification can 4319 be obtained from the IETF Secretariat." 4320 The IETF invites any interested party to bring to its attention any 4321 copyrights, patents or patent applications, or other proprietary 4322 rights which may cover technology that may be required to practice 4323 this standard. Please address the information to the IETF Executive 4324 Director. 4326 10. Authors' Addresses 4328 Faye Ly 4329 Pedestal Networks 4330 6503 Dumbarton Circle 4331 Fremont, CA 94555 4332 USA 4333 Phone (510) 896-2908 4334 EMail: faye@pedestalnetworks.com 4336 Michael Noto 4337 Cisco Systems 4338 170 W. Tasman Drive 4339 San Jose, CA 95134-1706 4340 USA 4341 EMail: mnoto@cisco.com 4343 Andrew Smith 4344 Allegro Networks 4345 6399 San Ignacio 4346 San Jose, CA 95119-1206 4347 USA 4348 EMail: andrew@allegronetworks.com 4350 Ethan Mickey Spiegel 4351 Cisco Systems 4352 170 W. Tasman Drive 4353 San Jose, CA 95134-1706 4354 Phone: (408) 526-6408 4355 EMail: mspiegel@cisco.com 4357 Kaj Tesink 4358 Telcordia Technologies 4359 331 Newman Springs Road 4360 Red Bank, NJ 07701-7020 4361 Phone: (732) 758-5254 4362 EMail: kaj@research.telcordia.com 4364 11. Full Copyright Statement 4366 Copyright (C) The Internet Society (2003). All Rights Reserved. 4368 This document and translations of it may be copied and furnished to 4369 others, and derivative works that comment on or otherwise explain it or 4370 assist in its implementation may be prepared, copied, published and 4371 distributed, in whole or in part, without restriction of any kind, 4372 provided that the above copyright notice and this paragraph are included 4373 on all such copies and derivative works. However, this document itself 4374 may not be modified in any way, such as by removing the copyright notice 4375 or references to the Internet Society or other Internet organizations, 4376 except as needed for the purpose of developing Internet standards in 4377 which case the procedures for copyrights defined in the Internet 4378 Standards process must be followed, or as required to translate it into 4379 languages other than English. 4381 The limited permissions granted above are perpetual and will not be 4382 revoked by the Internet Society or its successors or assigns. 4384 This document and the information contained herein is provided on an "AS 4385 IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK 4386 FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT 4387 LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT 4388 INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR 4389 FITNESS FOR A PARTICULAR PURPOSE." 4390 Table of Contents 4392 Status of this Memo ...................................... 1 4393 Abstract .................................................. 2 4394 1. The Internet-Standard Management Framework ............. 2 4395 2. Overview ............................................... 11 4396 3. Conventions used in the MIB ............................ 13 4397 4. Conformance and Compliance ............................. 28 4398 5. Definitions ............................................ 28 4399 6. Acknowledgments ........................................ 95 4400 7. References ............................................. 95 4401 8. Security Considerations ................................ 97 4402 9. Intellectual Property Notice ........................... 98 4403 10. Authors' Addresses .................................... 98 4404 11. Full Copyright Statement .............................. 99