idnits 2.17.1 draft-ietf-ion-mib-06.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: ---------------------------------------------------------------------------- ** Missing expiration date. The document expiration date should appear on the first and last page. ** The document seems to lack a 1id_guidelines paragraph about Internet-Drafts being working documents. ** The document seems to lack a 1id_guidelines paragraph about 6 months document validity. ** The document seems to lack a 1id_guidelines paragraph about the list of current Internet-Drafts. ** The document seems to lack a 1id_guidelines paragraph about the list of Shadow Directories. == No 'Intended status' indicated for this document; assuming Proposed Standard == The page length should not exceed 58 lines per page, but there was 51 longer pages, the longest (page 2) being 60 lines == It seems as if not all pages are separated by form feeds - found 0 form feeds but 52 pages Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an IANA Considerations section. (See Section 2.2 of https://www.ietf.org/id-info/checklist for how to handle the case when there are no actions for IANA.) ** The document seems to lack separate sections for Informative/Normative References. All references will be assumed normative when checking for downward references. ** There is 1 instance of too long lines in the document, the longest one being 3 characters in excess of 72. ** The abstract seems to contain references ([3], [1]), which it shouldn't. Please replace those with straight textual mentions of the documents in question. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year == Line 135 has weird spacing: '...defines trans...' -- 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 1998) is 9595 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) ** Obsolete normative reference: RFC 1902 (ref. '1') (Obsoleted by RFC 2578) ** Obsolete normative reference: RFC 2233 (ref. '2') (Obsoleted by RFC 2863) -- Possible downref: Non-RFC (?) normative reference: ref. '3' ** Obsolete normative reference: RFC 1695 (ref. '4') (Obsoleted by RFC 2515) ** Obsolete normative reference: RFC 1903 (ref. '6') (Obsoleted by RFC 2579) ** Obsolete normative reference: RFC 1905 (ref. '7') (Obsoleted by RFC 3416) ** Obsolete normative reference: RFC 1904 (ref. '8') (Obsoleted by RFC 2580) ** Obsolete normative reference: RFC 2011 (ref. '9') (Obsoleted by RFC 4293) ** Obsolete normative reference: RFC 1906 (ref. '12') (Obsoleted by RFC 3417) ** Obsolete normative reference: RFC 1907 (ref. '13') (Obsoleted by RFC 3418) ** Obsolete normative reference: RFC 1908 (ref. '14') (Obsoleted by RFC 2576) Summary: 20 errors (**), 0 flaws (~~), 5 warnings (==), 3 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 Internetworking Over NBMA (ion) Working Group Maria Greene 2 INTERNET DRAFT Xedia Corp. 3 Expires July, 1998 James Luciani 4 Bay Networks, Inc. 5 Kenneth White 6 IBM Corp. 7 Ted T.I. Kuo 8 Bay Networks, Inc. 10 January 1998 12 Definitions of Managed Objects for 13 Classical IP and ARP Over ATM Using SMIv2 14 (IPOA-MIB) 16 Status of this Memo 18 This document is an Internet Draft. Internet Drafts are working 19 documents of the Internet Engineering Task Force (IETF), its Areas, 20 and its Working Groups. Note that other groups may also distribute 21 working documents as Internet Drafts. 23 Internet Drafts are draft documents valid for a maximum of six 24 months. Internet Drafts may be updated, replaced, or obsoleted by 25 other documents at any time. It is not appropriate to use Internet 26 Drafts as reference material or to cite them other than as a "working 27 draft" or "work in progress." 29 Please check the I-D abstract listing contained in each Internet 30 Draft directory to learn the current status of this or any Internet 31 Draft. Distribution of this document is unlimited. 33 Copyright Notice 35 Copyright (C) The Internet Society (1998). All Rights Reserved. 37 Abstract 39 The purpose of this memo is to define the Management Information 40 Base (MIB) for supporting Classical IP and ARP over ATM as specified 41 in Classical IP and ARP over ATM, refer to reference [3]. Support of 42 an ATM interface by an IP layer will require implementation of objects 43 from several Management Information Bases (MIBs) as well as their 44 enhancement in order to enable usage of ATM transports. It is the 45 intent of this MIB to fully adhere to all prerequisite MIBs unless 46 explicitly stated. Deviations will be documented in corresponding 47 conformance statements. The specification of this MIB will utilize 48 the Structure of Management Information (SMI) for Version 2 of the 49 Simple Network Management Protocol Version (refer to RFC 1902, 50 reference [1]). 52 Table of Contents 54 1. Introduction.............................................. 2 55 2. The SNMPv2 Network Management Framework................... 3 56 2.1 Object Definitions....................................... 4 57 3. Structure of the MIB...................................... 4 58 3.1 Basic Support MIB Definitions............................ 5 59 3.1.1 ATM Logical IP Subnet (LIS) Table...................... 5 60 3.1.2 ATM Logical IP Subnet Interface Mapping Table.......... 7 61 3.1.3 ATMARP Remote Server Table............................. 7 62 3.1.4 ATM VC Table........................................... 8 63 3.1.5 ATM Config PVC Table................................... 9 64 3.1.6 Notifications.......................................... 10 . 65 3.2 Client Supported MIB Definitions......................... 10 66 3.2.1 ATMARP Client Table.................................... 11 67 3.3 Server Supported MIB Definitions......................... 12 68 3.3.1 ATMARP Server Table.................................... 12 69 3.3.2 Notifications.......................................... 13 70 4. Definitions............................................... 14 71 5. Security Considerations................................... 48 72 6. Intellectual Property..................................... 49 73 7. Acknowledgments........................................... 50 74 8. References................................................ 50 75 9. Authors' Addresses........................................ 51 76 10. Full Copyright Statement................................. 52 78 1. Introduction 80 This document is a product of the Internetworking Over NBMA Working 81 Group. Its purpose is to define a MIB module for extending the 82 traditional MIBs supported by a TCP/IP implementation to support 83 Classical IP and ARP over ATM. 85 Many MIB related RFCs and Internet Drafts have been considered in the 86 development of this document. The ones that are considered central to 87 the extensions defined by this document are: 89 o RFC 2011 - SNMPv2 Management Information Base for the 90 Internet Protocol using SMIv2 [9]. The IP over ATM 91 (IPOA) MIB provides extensions to the IP Group for 92 handling IP over ATM flows. A basic understanding of 93 the IP Group is essential for understanding this 94 document. 96 o RFC 2233 - The Interfaces Group MIB (IF-MIB) using SMIv2, 97 reference [2]. This document is important since it 98 provides several very useful enhancements over the 99 interface group defined in RFC 1213 (reference [5]) 100 that aid in handling ATM related interfaces. 102 o RFC 1695 - Definitions of Managed Objects for ATM Management 103 [4] (ATM-MIB). Support of this MIB is REQUIRED for 104 implementing the layers between AAL5 and ATM. The 105 contents of this MIB will not explicitly be addressed 106 here. The ATM-MIB provides a basis for managing ATM 107 interface layering and management of: 109 - ATM Switched Virtual Connections (SVCs) 110 - ATM Permanent Virtual Connections (PVCs) 112 The ATM Forum UNI ILMI MIB is specified by the ATM Forum in various 113 versions of the UNI specification. The ILMI MIBs being defined are 114 not supported via SNMP agents but via SNMP requests sent over an ATM 115 network to an ATM entity encapsulated in an AAL5 header. Support of 116 the ILMI MIB(s) is considered out of the scope of this document. 118 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 119 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 120 document are to be interpreted as described in RFC 2119, reference 121 [10]. 123 2. The SNMPv2 Network Management Framework 125 The SNMPv2 Network Management Framework consists of seven major 126 components. They are: 128 o RFC 1902 [1] which defines the SMI, the mechanisms used for 129 describing and naming objects for the purpose of management. 131 o RFC 1903 [6] defines textual conventions for SNMPv2. 133 o RFC 1904 [8] defines conformance statements for SNMPv2. 135 o RFC 1905 [7] defines transport mappings for SNMPv2. 137 o RFC 1906 [12] defines the protocol operations used for network 138 access to managed objects. 140 o RFC 1907 [13] defines the Management Information Base for SNMPv2. 142 o RFC 1908 [14] specifies coexistence between SNMPv1 and SNMPv2. 144 The Framework permits new objects to be defined for the purpose of 145 experimentation and evaluation. 147 This memo specifies a MIB module that is compliant to the SNMPv2 SMI. 148 A semantically identical MIB conforming to the SNMPv1 SMI can be 149 produced through the appropriate translation. 151 2.1. Object Definitions 153 Managed objects are accessed via a virtual information store, termed 154 the Management Information Base or MIB. Objects in the MIB are 155 defined using the subset of Abstract Syntax Notation One (ASN.1) 156 defined in the SMI. In particular, each object type is named by an 157 OBJECT IDENTIFIER, an administratively assigned name. The object type 158 together with an object instance serves to uniquely identify a 159 specific instantiation of the object. For human convenience, we often 160 use a textual string, termed the descriptor, to refer to the object 161 type. 163 3. Structure of the MIB 165 The Classical ARP and IP over ATM (IPOA) MIB structure is split into 166 three components: 168 o Basic Support MIB Definitions 169 o Client Supported MIB Definitions 170 o Server Supported MIB Definitions 172 All IP and ARP over ATM entities, both clients and ATMARP Servers, are 173 REQUIRED to support the MIB definitions in the Basic Support MIB 174 Definitions section. Clients need to additionally support the MIB 175 definitions outlined in the Client specific section and ATMARP Servers 176 MUST additionally support the ATMARP Server specific MIB definitions. 178 Implementation of the Definitions of Managed Objects for ATM 179 Management [4] defines the modeling of the various layers within an 180 ATM Interface. This modeling is assumed as a prerequisite for the 181 IPOA-MIB. The IPOA-MIB makes no assumptions on how this layering is 182 actually implemented within a system. Several of the MIB tables 183 defined by the IPOA-MIB, like the base TCP/IP MIBs, require that an 184 ifIndex exist that points to an ATM Interface. Refer to the ATM-MIB 185 [4] for the definition of ATM Interface layering. 187 The use of an IP over ATM Virtual Interface layer is NOT explicitly 188 REQUIRED by the IPOA-MIB. The use of virtual layers above an ATM-MIB 189 defined interface layer is not absolutely necessary for modeling the 190 attachment of IP to an ATM network. The IPOA-MIB refers to use of a 191 generic ifIndex object, whose value SHOULD reflect that of some 192 specific ATM related interface as determined by an implementation. It 193 is up to the implementers of this MIB to determine their own ATM 194 interface layering (assuming compliance with the IF-MIB and the ATM- 195 MIB). 197 The Internet Assigned Numbers Authority (IANA) ifType ipOverAtm(114) 198 was created for use by systems that require a virtual IP over ATM 199 interface layer. The IF-MIB's ifStackTable SHOULD be used to show the 200 relationship between virtual IP over ATM interfaces and the actual ATM 201 physical interface layers. The current set of ifType values can be 202 accessed via the IANA homepage at: "http://www.iana.org/iana/". 204 3.1. Basic Support MIB Definitions 206 Basic support that MUST be implemented by both Clients and ATMARP 207 Servers consists of: 209 o ATM Logical IP Subnet (LIS) Table 210 o ATM Logical IP Subnet Interface Mapping Table 211 o ATMARP Remote Server Table 212 o ATM VC Table 213 o ATM Config PVC Table 214 o Notifications 216 3.1.1. ATM Logical IP Subnet (LIS) Table 218 The ATM Logical IP Subnet (LIS) Table defines the subnets that this 219 system is a member of for purposes of reaching destinations over an 220 ATM transport. The LIS table is indexed by the subnet address 221 (ipoaLisSubnetAddr) and not ifIndex. The ipoaLisIfMappingTable 222 described in the next section provides the mapping between Logical IP 223 Subnets and the interface layer. It is possible that the same LIS can 224 be reached via different ATM interfaces. 226 The ipAddrTable and the ipoaClientTable provides the mapping from a 227 local IP address to an ATM interface. One or more ipAddrTable entries 228 can point to the same ipoaLisEntry. An ipAddrEntry's ipAdEntAddr 229 ANDed with its ipAdEntNetMask SHOULD equal an ipoaLisEntry's 230 ipoaLisSubnetAddr. Given that an interface can be multi-homed, each 231 local IP address associated with an interface requires an entry in the 232 ipAddrTable. Each ipAddrTable entry for a local IP address associated 233 with an ATM interface SHOULD map to an entry in the ipoaLisTable. 235 The bulk of the objects in an ipoaLisEntry exists to control ATMARP 236 for a particular LIS. In a PVC only environment it is implementation 237 dependent as to whether this table should be supported: 239 ipoaLisInactivityTimer 240 ipoaLisMinHoldingTime 241 ipoaLisQDepth 242 ipoaLisMaxCalls 243 ipoaLisCacheEntryAge 244 ipoaLisRetries 245 ipoaLisTimeout 247 The value of an ipoaLisMaxCalls object defines the maximum number of 248 VCs that can be established simultaneously per LIS. The value of an 249 ipoaLisDefaultPeakCellRate object defines the best effort default peak 250 cell rate in both the forward and backward directions when 251 establishing VCCs (Virtual Channel Connections). Refer to RFC 1755, 252 ATM Signaling Support for IP over ATM (reference [11]), for a 253 definition of the use of this object's value. 255 The ipAddrTable's ipAdEntReasmMaxSize is the "The size of the largest 256 IP datagram which this entity can re-assemble from incoming IP 257 fragmented datagrams received on this interface" and is different from 258 the ipoaLisTable's ipoaLisDefaultMtu with is the default MTU used 259 within an LIS. Note that this is the default MTU, not the actual MTU 260 (which is represented as ipoaVcNegotiatedMtu in the ipoaVcTable). 262 The ipoaLisRowStatus object enables entries in the ipoaLisTable to be 263 created or deleted via SNMP. Creation of an ipoaLisTable entry 264 results in the addition of a corresponding ipAddrTable entry and an 265 ipoaLisIfMappingTable entry. Creation of multiple ipAddrTable entries 266 and ipoaLisIfMappingTable entries for the same LIS is not addressed by 267 this document. When ipoaLisRowStatus is changed from active(1) to 268 notInService(2) or from active(1) to destroy(6), this has the side- 269 effect of removing all entries from the ipNetToMediaTable that are 270 associated with this LIS (in other words, it flushes the entity's 271 ATMARP cache). It also removes the ipoaVcTable entries that were 272 associated with those ipNetToMediaTable entries. Destroying the row 273 removes the corresponding entries in the ipoaArpSrvrTable, 274 ipoaArpClientTable, ipoaLisIfMappingTable, and the 275 ipoaArpRemoteSrvrTable. 277 Entries in both the ipNetToMediaTable and the ipoaVcTable that are 278 associated with an ipoaConfigPvcEntry are not affected by changes to 279 ipoaLisRowStatus. 281 3.1.2. ATM Logical IP Subnet Interface Mapping Table 283 The ipoaLisIfMappingTable maps a LIS to all ATM interfaces from which 284 it is configured to be supported. Each entry in the 285 ipoaLisIfMappingTable SHOULD map to an ipAddrTable entry. It is also 286 possible for a system, most commonly a switch, to have multiple LISs 287 associated with the same ATM interface. 289 3.1.3. ATMARP Remote Server Table 291 Entries in the ipoaArpRemoteSrvrTable exists to locally configure the 292 remote ATMARP Servers that exist on a per LIS and interface basis. 293 Classical IP and ARP over ATM [3] requires that at least one ATMARP 294 Server be configured per LIS where SVC traffic is intended. PVC usage 295 doesn't require use of ATMARP. No ipoaArpRemoteSrvrTable entries 296 SHOULD be configured for a LIS where only PVCs will be used. An entry 297 in the ipoaArpRemoteSrvrTable is indexed by the subnet address of the 298 LIS (ipoaLisSubnetAddr), the ATM address of the remote ATMARP Server 299 (ipoaArpRemoteSrvrAtmAddr) and an interface ifIndex 300 (ipoaArpRemoteSrvrIfIndex) value. 302 The object ipoaArpRemoteSrvrIpAddr in an ipoaArpRemoteSrvrEntry is set 303 with the IP Address of the Remote ATMARP Server when a VC to the 304 Remote ATMARP Server is established. A value of 0.0.0.0 SHOULD be 305 used when the IP address of the Remote ATMARP Server is not known. 306 Once ipoaArpRemoteSrvrIpAddr is set then the ipoaVcTable can be 307 searched using ipoaArpRemoteSrvrIfIndex and ipoaArpRemoteSrvrIpAddr to 308 find the VC in use to the Remote ATMARP Server. 310 ipoaArpRemoteSrvrIfIndex is defined to have the textual convention of 311 InterfaceIndexOrZero. Adding ipoaArpRemoteSrvrIfIndex to the index 312 clause allows a system to have a VC to a ATMARP Remote Server on a per 313 LIS and interface basis. An entry in this table SHOULD exist for each 314 interface on a per LIS basis. Each interface would then have a 315 separate VC to the Remote ATMARP Server for ATMARP purposes. 317 An implementation that wants to use a single VC MAY use an 318 ipoaArpRemoteSrvrIfIndex value of 0 when configuring an 319 ipoaArpRemoteSrvrEntry for the associating LIS. If 320 ipoaArpRemoteSrvrIfIndex is 0 then an implementation dependent method 321 MAY be used for finding the VPI and VCI of the VC in use to the Remote 322 ATMARP Server. For example, search the ipoaVcTable for a match 323 between ipNetToMediaNetAddress and ipoaArpRemoteSrvrIpAddr from an 324 ipoaArpRemoteSrvrEntry, ignoring ipNetToMediaIfIndex. Since a single 325 VC is being used the first match SHOULD correspond to the correct VC. 327 If a PVC is intended to be used to communicate with a remote ATMARP 328 Server then the ipoaConfigPvcTable MUST be used to create and activate 329 the PVC prior to activating a ipoaArpRemoteSrvrEntry. 331 The object ipoaArpRemoteSrvrRowStatus allows for row creation and 332 deletion of entries in the ipoaArpRemoteSrvrTable. The objects 333 ipoaArpRemoteSrvrAdminStatus and ipoaArpRemoteSrvrOperStatus exists to 334 control and relect the operational use of a Remote ATMARP Server 335 defined by an ipoaArpRemoteSrvrEntry. The object 336 ipoaArpRemoteSrvrOperStatus SHOULD have a value of up(1) when an SVC 337 has been established to the Remote ATMARP Server or if using a PVC 338 when the InATMARP reply with the IP Address of the Remote ATMARP 339 Server has been received. The value of down(2) SHOULD be used to 340 indicate that a VC to the Remote ATMARP Server doesn't exist. 342 3.1.4. ATM VC Table 344 An entry in the ipoaVcTable SHOULD have at least one corresponding 345 ipNetToMediaTable entry. Both tables use the ipNetToMediaTable's 346 indexes ipNetToMediaIfIndex and ipNetToMediaNetAddress. The 347 ipoaVcTable has the additional indexes ipoaVcVpi and ipoaVcVci. An 348 ipoaVcEntry exists for every VC per ATM interface per destination IP 349 address. Refer to the following diagram that illustrates the 350 relationship between ipoaVcTable and the ipNetToMediaTable: 352 ipoaVcTable ipNetToMediatable 353 ------------------------------ ---------------------------- 354 | ipNetToMediaIfIndex | | ipNetToMediaIfIndex | 355 | ipNetToMediaNetAddress | | ipNetToMediaNetAddress | 356 | ipoaVcVpi | | | 357 | ipoaVcVci | | | 358 | ipoaVcType | | | 359 | ---> use IpoaAtmAddr TC | | ipNetToMediaPhysAddress | 360 | ipoaVcNegotiatedEncapsType | | | 361 | ipoaVcNegotiatedMtu | | | 362 | | | ipNetToMediaType | 363 ------------------------------ ---------------------------- 365 ipoaVcType indicates if the entry is for an SVC or an PVC. An 366 ipoaVcEntry, corresponding to an PVC, is created automatically when an 367 ipoaConfigPvcEntry is created and the IP Address at the end of the PVC 368 is discovered. The associating ipNetToMediaTable entry would have its 369 ipNetToMediaType set to static(4). ipNetToMediaTable entries created 370 during ATMARP processing have a ipNetToMediaType of dynamic(3). The 371 process to locally configuring an ipNetToMediaTable entry and an 372 ipoaVcTable entry for an SVC without using ATMARP is not within the 373 scope of this document. 375 The objects ipoaVcVpi and ipoaVcVci are defined to have a MAX-ACCESS 376 of not-accessible since they are only used for purposes of indexing an 377 entry in the ipoaVcTable. 379 3.1.5. ATM Config PVC Table 381 An entry in the ipoaVcTable is created after the InATMARP reply is 382 successfully received for an ipoaConfigPvcEntry during its activation. 383 InATMARP should return the IP Address of the other end of the PVC in 384 order to have the needed indexes to create an ipNetToMediaEntry and an 385 ipoaVcEntry. ipoaConfigPvcRowStatus would then be set to active(1). 387 The object ipoaConfigPvcRowStatus doesn't get a value of active(1) 388 until the InATMARP reply is received. If the row was complete it 389 would have a value of notInService(2) as defined by RFC 1903 as 390 opposed to notReady(3). The value of a ipoaConfigPvcRowStatus object 391 can be used to determine if the PVC is available for use or not. The 392 value of an ipoaConfigPvcRowStatus object SHOULD be set to 393 notInService(2) and the corresponding ARP Cache entry deleted whenever 394 a PVC becomes unusable. 396 A Network Management Station wanting to create a PVC at a particular 397 system for use as an IP transport would: 399 o use the ATM-MIB, reference [4], to create the PVC 400 o use the ipoaConfigPvcTable in the IPOA-MIB to configure 401 the PVC for use by IP 403 Refer to the following diagram that illustrates the relationship 404 between the ipoaVcTable and the ipoaConfigPvcTable: 406 ipoaVcTable ipoaConfigPvcTable 407 ------------------------------ ---------------------------- 408 | ipNetToMediaIfIndex | | ipNetToMediaIfIndex | 409 | ipNetToMediaNetAddress | | | 410 | ipoaVcVpi | | ipoaConfigPvcVpi | 411 | ipoaVcVci | | ipoaConfigPvcVci | 412 | ipoaVcType | | | 413 | | | ipoaConfigPvcDefaultMtu | 414 | ipoaVcNegotiatedEncapsType | | | 415 | ipoaVcNegotiatedMtu | | | 416 | | | ipoaConfigPvcRowStatus | 417 ------------------------------ ---------------------------- 419 When the ipoaVcEntry is created its ipoaVcType will be set to pvc(1), 420 its ipoaVcNegotiatedEncapsType set to llcSnap(1), and its 421 ipoaVcNegotiatedMtu set to 9180 octets by default. Classical IP and 422 ARP over ATM [3] allows use of other MTU values for PVCs but considers 423 the selection of a value other than 9180 to be out of scope. 424 ipoaConfigPvcDefaultMtu can be used to configure the MTU to be used 425 for the PVC. Both ends MUST have the same value configured. The 426 associating ipNetToMediaTable entry would have its ipNetToMediaType 427 set to static(4). 429 Changing ipoaConfigPvcRowStatus from active(1) to notInService(2) or 430 from active(1) to destroy(6) has the side-effect of removing the 431 corresponding ipNetToMediaTable, ipoaVcTable, and ipoaConfigPvcTable 432 entries. 434 3.1.6. Notifications 436 Both ATM clients and ATMARP Servers MUST support generation of an 437 ipoaMtuExceeded notification. 439 3.2. Client Supported MIB Definitions 441 The ATMARP Client Table is the only additional MIB table that a client 442 MUST implement. 444 3.2.1. ATMARP Client Table 446 An entry in the ipoaArpClientTable SHOULD have a corresponding 447 ipAddrTable entry where both are indexed by the same ipAdEntAddr 448 value. Refer to the following diagram that illustrates the 449 relationship between ipoaArpClientTable and ipAddrTable entries: 451 ipoaArpClientTable ipAddrTable 452 ----------------------------------- ------------------------ 453 | ipAdEntAddr | | ipAdEntAddr | 454 | | | ipAdEntNetMask | 455 | | | ipAdEntIfIndex | 456 | ipoaArpClientAtmAddr | | | 457 | ipoaArpClientSrvrInUse | | | 458 | ipoaArpClientInArpInReqs | | | 459 | ipoaArpClientInArpOutReqs | | | 460 | ipoaArpClientInArpInReplies | | | 461 | ipoaArpClientInArpOutReplies | | | 462 | ipoaArpClientInArpInvalidInReqs | | | 463 | ipoaArpClientInArpInvalidOutReqs| | | 464 | ipoaArpClientArpInReqs | | | 465 | ipoaArpClientArpOutReqs | | | 466 | ipoaArpClientArpInReplies | | | 467 | ipoaArpClientArpOutReplies | | | 468 | ipoaArpClientArpInNaks | | | 469 | ipoaArpClientArpOutNaks | | | 470 | ipoaArpClientArpUnknownOps | | | 471 | ipoaArpClientArpNoSrvrResps | | | 472 | ipoaArpClientRowStatus | | | 473 | | | ipAdEntBcastAddr | 474 | | | ipAdEntReasmMaxSize | 475 ----------------------------------- ------------------------ 477 Both tables have the same index, ipAdEntAddr. The ipAddrTable's 478 ipAdEntNetMask when ANDed with its corresponding ipAdEntAddr yield the 479 subnet of the LIS which can be used as an index into the ipoaLisTable 480 (ipoaLisSubnetAddr). The ipAddrTable's ipAdEntIfIndex points to an 481 interface ifTable entry via an ifIndex value. The attachment point 482 for IP into an ATM network is via an ATM interface's ifIndex. Each 483 ipoaArpClientEntry MUST point to an ATM interface via its 484 corresponding ipAddrEntry. 486 ipoaArpClientAtmAddr is the local ATM address associated with the 487 corresponding ATM ifTable entry. ipoaArpClientSrvrInUse is the ATM 488 address of the ATMARP Server being used for a particular client. If 489 SVCs are not being used then the value of this object is a zero-length 490 OCTET STRING. 492 It is sometimes possible for a system to have multiple IP addresses 493 configured within the same IP subnet. The indexing of this table 494 would seem to preclude that. However, it is possible to have 495 additional entries in the ipAddrTable with the same ifIndex and with 496 the same subnet address. The mechanism for adding these multiple 497 entries to the ipAddrTable (which is read-only) is beyond the scope of 498 this document. 500 The counter object ipoaArpClientInArpInvalidInReqs is "The number of 501 times that this client detects an invalid InATMARP request." This 502 object SHOULD be incremented when processing fails for an InATMARP 503 request (e.g., for incorrect InATMARP request structure fields). The 504 object ipoaArpClientInArpInvalidOutReqs is defined as "The number of 505 times that this client did not receive an InATMARP reply." This is 506 different from ipoaArpClientArpNoSrvrResps which counts the number of 507 times no response was received from an ATMARP request. 509 InATMARP retransmission processing is not controlled by objects in the 510 ipoaLisTable. In general, the ipoaLisTable objects relate to ATMARP 511 Server processing. Configuration of InATMARP retransmission 512 processing is considered to be implementation dependent and not 513 defined by the IPOA-MIB. 515 Implementations SHOULD use local policy for defining both InATMARP 516 timeout and retry count values. This policy would be expected to 517 differ for sending an InATMARP Request over an PVC as opposed to an 518 SVC. For transmission of an InATMARP Request over an SVC a timeout of 519 60 seconds with a retry count of 3 is suggested. InATMARP 520 transmission over a PVC should differ since its retry limit may need 521 to be infinite in order to ensure that InATMARP Request processing 522 eventually occurs. 524 3.3. Server Supported MIB Definitions 526 ATMARP Servers MUST support: 528 o ATMARP Server Table 529 o Notifications 531 as defined in the following sections. This table exists only on a 532 system where at least one ATMARP Server is present. 534 3.3.1. ATMARP Server Table 536 This table defines the list of ATMARP Servers within a LIS. Each 537 entry of the table defines each ATMARP Server's ATM address, the LIS 538 it is a member of, and various InATMARP and ATMARP statistics. 540 An entry in this table provides information about an ATMARP Server 541 within a LIS and is indexed by ipAdEntAddr (a local IP Address from an 542 IP Address Table entry) and ipoaArpSrvrAddr (an ATM Address associated 543 with the ATMARP Server). 545 Entries MAY be created by a management application using the 546 ipoaArpSrvrRowStatus object. Entries in this table MAY also be 547 created by the system and not by a management application, for example 548 via ILMI. 550 Entries in this table MAY be deleted by setting the 551 ipoaArpSrvrRowStatus object to destroy(6). This includes entries that 552 were added by the system and not by a management application. 554 On a host that supports multiple ATMARP Servers where the local IP 555 address being associated with each ATMARP Server is the same (for 556 example a non-multihomed host), the ATM Address (ipoaArpSrvrAddr) 557 uniquely identifies a particular ATMARP Server. On a host supporting 558 multiple ATMARP Servers having a single ATM Interface with a single 559 ATM Address, the ipAdEntAddr MUST be used to uniquely identify an 560 entry in the ipoaArpSrvrTable. 562 The indexing of the ipoaArpSrvrTable does not allow entries with the 563 same or no local IP Address (ipAdEntAddr) and the same ATM Address 564 (ipoaArpSrvrAddr) to exist. The values of the index elements when 565 combined to index a row must be unique. 567 3.3.2. Notifications 569 An ATMARP Server MUST support the following notifications: 571 o ipoaDuplicateIpAddress 572 o ipoaLisCreate 573 o ipoaLisDelete 575 Generation of ipoaLisCreate and ipoaLisDelete notifications is 576 controlled by the ipoaLisTrapEnable object. These notifications 577 indicate when an ipoaLisEntry is either created or deleted. The 578 purpose of these notifications is to enable Network Management 579 Applications to dynamically discover the existence of ATMARP Server 580 LIS participation in order to eventually determine LIS composition via 581 subsequent SNMP queries. It is permissible for a ATM client-only 582 system to support the ipoaLisTrapEnable object and generate 583 ipoaLisCreate and ipoaLisDelete notifications. 585 4. Definitions 587 IPOA-MIB DEFINITIONS ::= BEGIN 589 IMPORTS 590 MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, 591 experimental, Integer32, IpAddress, Counter32, 592 Gauge32 593 FROM SNMPv2-SMI 594 TEXTUAL-CONVENTION, RowStatus 595 FROM SNMPv2-TC 596 MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP 597 FROM SNMPv2-CONF 598 ipNetToMediaNetAddress, ipNetToMediaIfIndex, 599 ipNetToMediaPhysAddress, ipAdEntAddr 600 FROM IP-MIB 602 -- The following textual conventions are defined locally within 603 -- this MIB module. They have been prefixed with 'Ipoa' to 604 -- distinguish them from their counterparts in the ATM-TC-MIB. 605 -- This was done so that the IPOA-MIB could be advanced as 606 -- a standards-based MIB without waiting for the ATM-TC-MIB. 607 -- AtmConnKind, AtmAddr 608 -- FROM ATM-TC-MIB 610 InterfaceIndex, InterfaceIndexOrZero 611 FROM IF-MIB 612 ; 614 ipoaMIB MODULE-IDENTITY 615 LAST-UPDATED "9801220000Z" -- January 22, 1998 616 ORGANIZATION "IETF Internetworking Over NBMA Working 617 Group (ion)" 618 CONTACT-INFO 619 "Maria Greene (greene@xedia.com) 620 Xedia Corp. 622 Jim Luciani (jluciani@BayNetworks.com) 623 Bay Networks 625 Kenneth White (kennethw@vnet.ibm.com) 626 IBM Corp. 628 Ted Kuo (tkuo@eos.ncsu.edu) 629 Bay Networks" 630 DESCRIPTION 631 "This module defines a portion of the management 632 information base (MIB) for managing Classical IP and 633 ARP over ATM entities." 634 ::= { experimental 78 } 636 -- Textual Conventions 638 IpoaEncapsType ::= TEXTUAL-CONVENTION 639 STATUS current 640 DESCRIPTION 641 "The encapsulation type used on a VC." 642 SYNTAX INTEGER { 643 llcSnap(1), 644 vcMuxed(2), 645 other(3) 646 } 648 IpoaVpiInteger ::= TEXTUAL-CONVENTION 649 STATUS current 650 DESCRIPTION 651 "An integer large enough to contain the value of a VPI." 652 SYNTAX Integer32 (0..255) 654 IpoaVciInteger ::= TEXTUAL-CONVENTION 655 STATUS current 656 DESCRIPTION 657 "An integer large enough to contain the value of a VCI." 658 SYNTAX Integer32 (0..65535) 660 IpoaAtmAddr ::= TEXTUAL-CONVENTION 661 DISPLAY-HINT "1x" 662 STATUS current 663 DESCRIPTION 664 "The ATM address used by the network entity. 665 The semantics are implied by the length. 666 The address types are: 668 - no address (0 octets) 669 - E.164 (8 octets) 670 - NSAP (20 octets) 672 In addition, when subaddresses are used IpoaAtmAddr 673 may represent the concatenation of address and 674 subaddress. The associated address types are: 676 - E.164, E.164 (16 octets) 677 - E.164, NSAP (28 octets) 678 - NSAP, NSAP (40 octets) 680 Address lengths other than defined in this definition 681 imply address types defined elsewhere. 682 Note: The E.164 address is encoded in BCD format." 683 SYNTAX OCTET STRING (SIZE(0..40)) 685 IpoaAtmConnKind ::= TEXTUAL-CONVENTION 686 STATUS current 687 DESCRIPTION 688 "The use of call control. The use is as follows: 689 pvc(1) 690 Virtual link of a PVC. Should not be 691 used in a PVC/SVC (i.e., SPVC) 692 crossconnect. 693 svcIncoming(2) 694 Virtual link established after a 695 received signaling request to setup 696 an SVC. 697 svcOutgoing(3) 698 Virtual link established after a 699 transmitted or forwarded signaling 700 request to setup an SVC. 701 spvcInitiator(4) 702 Virtual link at the PVC side of an 703 SVC/PVC crossconnect, where the 704 switch is the initiator of the SPVC 705 setup. 706 spvcTarget(5) 707 Virtual link at the PVC side of an 708 SVC/PVC crossconnect, where the 709 switch is the target of the SPVC 710 setup. 712 An spvcInitiator is always cross-connected to 713 an svcOutgoing, and an spvcTarget is always 714 cross-connected to an svcIncoming." 715 SYNTAX INTEGER { 716 pvc(1), 717 svcIncoming(2), 718 svcOutgoing(3), 719 spvcInitiator(4), 720 spvcTarget(5) 721 } 723 -- Top-level structure of the MIB 725 ipoaObjects OBJECT IDENTIFIER ::= { ipoaMIB 1 } 726 ipoaNotifications OBJECT IDENTIFIER ::= { ipoaMIB 2 } 727 ipoaConformance OBJECT IDENTIFIER ::= { ipoaMIB 3 } 728 -- MIB Objects 730 ipoaLisTrapEnable OBJECT-TYPE 731 SYNTAX INTEGER { enabled(1), disabled(2) } 732 MAX-ACCESS read-write 733 STATUS current 734 DESCRIPTION 735 "Indicates whether ipoaLisCreate and ipoaLisDelete 736 traps should be generated by this system. 738 By default, this object should have the value 739 enabled(1) for systems where ATMARP Servers are 740 present and disabled(2) on systems where only 741 clients reside." 742 ::= { ipoaObjects 1 } 744 -- The ATM Logical IP Subnet (LIS) Table 746 ipoaLisTable OBJECT-TYPE 747 SYNTAX SEQUENCE OF IpoaLisEntry 748 MAX-ACCESS not-accessible 749 STATUS current 750 DESCRIPTION 751 "There is one entry in this table for every Logical IP 752 Subnet (LIS) of which this system is a member. 754 The bulk of the objects in an ipoaLisEntry exists 755 to control ATMARP for a particular LIS. In a PVC only 756 environment it is implementation dependent as to 757 whether this table should be supported." 758 ::= { ipoaObjects 2 } 760 ipoaLisEntry OBJECT-TYPE 761 SYNTAX IpoaLisEntry 762 MAX-ACCESS not-accessible 763 STATUS current 764 DESCRIPTION 765 "Information about a single LIS of which this system 766 is a member. 768 Membership in a LIS is independent of the actual ATM 769 interfaces being used. The ipoaLisTable defines 770 all LISs that a system is a member of. The ipAddrTable 771 and the ipoaClientTable provides the mapping from local 772 IP address to ATM interface. The ipoaLisIfMappingTable 773 provides the mappings between Logical IP Subnets and 774 interfaces. 776 The ipoaLisTable is indexed by ipoaLisSubnetAddr (IP 777 subnet address). An entry in the ipoaLisTable should 778 exist for each ipAddrEntry that is associated with an 779 ATM related interface used for Classical IP and ARP 780 over ATM traffic. 782 Its ipAdEntAddr and ipAdEntNetMask when ANDed together 783 should equal the ipoaLisSubnetAddr of the corresponding 784 ipoaLisEntry." 785 INDEX { ipoaLisSubnetAddr } 786 ::= { ipoaLisTable 1 } 788 IpoaLisEntry ::= SEQUENCE { 789 ipoaLisSubnetAddr IpAddress, 790 ipoaLisDefaultMtu Integer32, 791 ipoaLisDefaultEncapsType IpoaEncapsType, 792 ipoaLisInactivityTimer Integer32, 793 ipoaLisMinHoldingTime Integer32, 794 ipoaLisQDepth Integer32, 795 ipoaLisMaxCalls Integer32, 796 ipoaLisCacheEntryAge Integer32, 797 ipoaLisRetries Integer32, 798 ipoaLisTimeout Integer32, 799 ipoaLisDefaultPeakCellRate Integer32, 800 ipoaLisActiveVcs Gauge32, 801 ipoaLisRowStatus RowStatus } 803 ipoaLisSubnetAddr OBJECT-TYPE 804 SYNTAX IpAddress 805 MAX-ACCESS read-only 806 STATUS current 807 DESCRIPTION 808 "The IP subnet address associated with this LIS." 809 ::= { ipoaLisEntry 1 } 811 ipoaLisDefaultMtu OBJECT-TYPE 812 SYNTAX Integer32 (0..65535) 813 MAX-ACCESS read-create 814 STATUS current 815 DESCRIPTION 816 "The default MTU used within this LIS. Note that the 817 actual MTU used for a VC between two members of the 818 LIS may be negotiated during connection setup and may 819 be different than this value. The ipoaVcNegotiatedMtu 820 object indicates the actual MTU in use for a 821 particular VC." 822 DEFVAL { 9180 } 823 ::= { ipoaLisEntry 2 } 825 ipoaLisDefaultEncapsType OBJECT-TYPE 826 SYNTAX IpoaEncapsType 827 MAX-ACCESS read-create 828 STATUS current 829 DESCRIPTION 830 "The default encapsulation to use on VCs created for 831 this LIS. Note that the actual encapsulation type may 832 be negotiated during connection setup and may be 833 different than this value. The 834 ipoaVcNegotiatedEncapsType object indicates the actual 835 encapsulation in use for a particular VC." 836 DEFVAL { llcSnap } 837 ::= { ipoaLisEntry 3 } 839 ipoaLisInactivityTimer OBJECT-TYPE 840 SYNTAX Integer32 841 UNITS "seconds" 842 MAX-ACCESS read-create 843 STATUS current 844 DESCRIPTION 845 "The time, in seconds, before a call established for an 846 ipNetToMediaEntry on a client will timeout due to no 847 traffic being passed on the VC. A value of 0 implies 848 no time out." 849 REFERENCE 850 "RFC 1755, Sec. 3.4 VC Teardown" 851 DEFVAL { 1200 } 852 ::= { ipoaLisEntry 4 } 854 ipoaLisMinHoldingTime OBJECT-TYPE 855 SYNTAX Integer32 (0..65535) 856 UNITS "seconds" 857 MAX-ACCESS read-create 858 STATUS current 859 DESCRIPTION 860 "The minimum amount of time, in seconds, that a call 861 will remain open. If 0 then ipoaInactivityTimer will 862 completely determine when a call is terminated." 863 REFERENCE 864 "RFC 1755, Sec. 3.4 VC Teardown" 865 DEFVAL { 60 } 866 ::= { ipoaLisEntry 5 } 868 ipoaLisQDepth OBJECT-TYPE 869 SYNTAX Integer32 (1..65535) 870 UNITS "packets" 871 MAX-ACCESS read-create 872 STATUS current 873 DESCRIPTION 874 "The maximum number of outstanding requests that are 875 allowed while waiting for ATMARP replies and 876 InATMARP replies for this LIS." 877 DEFVAL { 1 } 878 ::= { ipoaLisEntry 6 } 880 ipoaLisMaxCalls OBJECT-TYPE 881 SYNTAX Integer32 (1..65535) 882 MAX-ACCESS read-create 883 STATUS current 884 DESCRIPTION 885 "The maximum number of SVCs that can be established 886 simultaneously for this LIS." 887 DEFVAL { 500 } 888 ::= { ipoaLisEntry 7 } 890 ipoaLisCacheEntryAge OBJECT-TYPE 891 SYNTAX Integer32 (60..1200) 892 UNITS "seconds" 893 MAX-ACCESS read-create 894 STATUS current 895 DESCRIPTION 896 "The time, in seconds, before an ipNetToMediaEntry will 897 age out of the table. Note that the default value will 898 be different for a client and a server. An ATMARP 899 Server should use a default of 1200 and a client should 900 use 900." 901 DEFVAL { 900 } 902 ::= { ipoaLisEntry 8 } 904 ipoaLisRetries OBJECT-TYPE 905 SYNTAX Integer32 (0..10) 906 MAX-ACCESS read-create 907 STATUS current 908 DESCRIPTION 909 "The number of times the ATMARP request will be retried 910 when no response is received in the timeout interval 911 indicated by ipoaLisTimeout." 912 DEFVAL { 2 } 913 ::= { ipoaLisEntry 9 } 915 ipoaLisTimeout OBJECT-TYPE 916 SYNTAX Integer32 (1..60) 917 UNITS "seconds" 918 MAX-ACCESS read-create 919 STATUS current 920 DESCRIPTION 921 "The time to wait, in seconds, before retransmission 922 of an ARP PDU." 923 DEFVAL { 10 } 924 ::= { ipoaLisEntry 10 } 926 ipoaLisDefaultPeakCellRate OBJECT-TYPE 927 SYNTAX Integer32 928 MAX-ACCESS read-create 929 STATUS current 930 DESCRIPTION 931 "This object is the signalling parameter that 932 should be used when setting up all best effort 933 VCCs (Virtual Channel Connections). 934 This parameter applies to the forward and 935 backward direction on a per best effort VCC basis. 936 A value of zero implies that no configured default 937 exists and that local policy should be used to 938 determine the actual default to used during 939 call setup. ATM Signaling Support for IP over ATM 940 (RFC 1755) recommends 1/10th of the ATM interface's 941 speed." 942 ::= { ipoaLisEntry 11 } 944 ipoaLisActiveVcs OBJECT-TYPE 945 SYNTAX Gauge32 946 MAX-ACCESS read-only 947 STATUS current 948 DESCRIPTION 949 "Number of active SVCs for this LIS." 950 ::= { ipoaLisEntry 12 } 952 ipoaLisRowStatus OBJECT-TYPE 953 SYNTAX RowStatus 954 MAX-ACCESS read-create 955 STATUS current 956 DESCRIPTION 957 "This object allows entries to be created and deleted 958 in the ipoaLisTable. 960 When the ipoaLisRowStatus deleted (by setting this 961 object to destroy(6)), this has the side-effect of 962 removing all entries from the ipNetToMediaTable that 963 are associated with this LIS (in other words, it 964 flushes the entity's ATMARP cache). It also removes 965 the ipoaVcTable entries that were associated with those 966 ipNetToMediaTable entries. Destroying the row also 967 removes the corresponding entries in the 968 ipoaArpSrvrTable, ipoaArpClientTable, 969 ipoaLisIfMappingTable, and ipoaArpRemoteSrvrTable. 971 Entries in both the ipNetToMediaTable and the 972 ipoaVcTable that are associated with a 973 ipoaConfigPvcEntry are not affected by changes to 974 ipoaLisRowStatus." 975 REFERENCE 976 "RFC 1903, 'Textual Conventions for Version 2 of the 977 Simple Network Management Protocol (SNMPv2).'" 978 ::= { ipoaLisEntry 13 } 980 -- The ATM Logical IP Subnet Interface Mapping Table 982 ipoaLisIfMappingTable OBJECT-TYPE 983 SYNTAX SEQUENCE OF IpoaLisIfMappingEntry 984 MAX-ACCESS not-accessible 985 STATUS current 986 DESCRIPTION 987 "There is one entry in this table for every combination 988 of ipoaLisEntry and IP over ATM interface." 989 ::= { ipoaObjects 3 } 991 ipoaLisIfMappingEntry OBJECT-TYPE 992 SYNTAX IpoaLisIfMappingEntry 993 MAX-ACCESS not-accessible 994 STATUS current 995 DESCRIPTION 996 "Defines an entry in the ipoaLisIfMappingTable." 997 INDEX { ipoaLisSubnetAddr, ipoaLisIfMappingIfIndex } 998 ::= { ipoaLisIfMappingTable 1 } 1000 IpoaLisIfMappingEntry ::= SEQUENCE { 1001 ipoaLisIfMappingIfIndex InterfaceIndex, 1002 ipoaLisIfMappingRowStatus RowStatus } 1004 ipoaLisIfMappingIfIndex OBJECT-TYPE 1005 SYNTAX InterfaceIndex 1006 MAX-ACCESS not-accessible 1007 STATUS current 1008 DESCRIPTION 1009 "The ipAdEntIfIndex object from an ipAddrEntry 1010 is used as an index to this table when its 1011 ipAdEntAddr is in the subnet implied by 1012 ipoaLisSubnetAddr." 1013 ::= { ipoaLisIfMappingEntry 1 } 1015 ipoaLisIfMappingRowStatus OBJECT-TYPE 1016 SYNTAX RowStatus 1017 MAX-ACCESS read-create 1018 STATUS current 1019 DESCRIPTION 1020 "This object allows entries to be created and deleted 1021 in the ipoaLisIfMappingTable." 1022 REFERENCE 1023 "RFC 1903, 'Textual Conventions for Version 2 of the 1024 Simple Network Management Protocol (SNMPv2).'" 1025 ::= { ipoaLisIfMappingEntry 2 } 1027 -- The ATMARP Client Table 1029 ipoaArpClientTable OBJECT-TYPE 1030 SYNTAX SEQUENCE OF IpoaArpClientEntry 1031 MAX-ACCESS not-accessible 1032 STATUS current 1033 DESCRIPTION 1034 "The ATMARP clients running on this system." 1035 ::= { ipoaObjects 4 } 1037 ipoaArpClientEntry OBJECT-TYPE 1038 SYNTAX IpoaArpClientEntry 1039 MAX-ACCESS not-accessible 1040 STATUS current 1041 DESCRIPTION 1042 "Information about a single ATMARP Client. Clients 1043 can be started and stopped by adding and removing 1044 entries from this table. An entry in the 1045 ipoaArpClientTable has a corresponding entry in the 1046 ipAddrTable. Both are indexed by ipAdEntAddr. 1047 The ifIndex and subnet mask of a client entry are the 1048 ipAddrEntry's ipAdEntIfIndex and ipAdEntNetMask, 1049 respectively. 1051 Note that adding and removing entries from this table 1052 may have the same effect on the corresponding 1053 ipAddrTable entry. Row creation of an entry in this 1054 table requires that either the corresponding ipAddrTable 1055 entry exists or that ipAdEntIfIndex and ipAdEntNetMask 1056 be specified in the creation of an ipoaArpClientEntry 1057 at a minimum in order to create the corresponding 1058 ipAddrEntry. Specification of ipAdEntBcastAddr and 1059 ipAdEntReasmMaxSize to complete an ipAddrEntry is 1060 implementation dependent. 1062 Whether a corresponding ipAddrEntry is deleted during 1063 the deletion of an ipoaArpClientEntry is considered 1064 implementation dependent." 1065 INDEX { ipAdEntAddr } 1066 ::= { ipoaArpClientTable 1 } 1068 IpoaArpClientEntry ::= SEQUENCE { 1069 ipoaArpClientAtmAddr IpoaAtmAddr, 1070 ipoaArpClientSrvrInUse IpoaAtmAddr, 1071 ipoaArpClientInArpInReqs Counter32, 1072 ipoaArpClientInArpOutReqs Counter32, 1073 ipoaArpClientInArpInReplies Counter32, 1074 ipoaArpClientInArpOutReplies Counter32, 1075 ipoaArpClientInArpInvalidInReqs Counter32, 1076 ipoaArpClientInArpInvalidOutReqs Counter32, 1077 ipoaArpClientArpInReqs Counter32, 1078 ipoaArpClientArpOutReqs Counter32, 1079 ipoaArpClientArpInReplies Counter32, 1080 ipoaArpClientArpOutReplies Counter32, 1081 ipoaArpClientArpInNaks Counter32, 1082 ipoaArpClientArpOutNaks Counter32, 1083 ipoaArpClientArpUnknownOps Counter32, 1084 ipoaArpClientArpNoSrvrResps Counter32, 1085 ipoaArpClientRowStatus RowStatus } 1087 ipoaArpClientAtmAddr OBJECT-TYPE 1088 SYNTAX IpoaAtmAddr 1089 MAX-ACCESS read-create 1090 STATUS current 1091 DESCRIPTION 1092 "The ATM address of the client." 1093 ::= { ipoaArpClientEntry 1 } 1095 ipoaArpClientSrvrInUse OBJECT-TYPE 1096 SYNTAX IpoaAtmAddr 1097 MAX-ACCESS read-only 1098 STATUS current 1099 DESCRIPTION 1100 "The ATM address of the ATMARP Server, 1101 ipoaArpRemoteSrvrAtmAddr, in use by this client. A 1102 zero length octet string implies that communication 1103 with a Remote ATMARP Server is not in effect." 1104 DEFVAL { ''H } 1105 ::= { ipoaArpClientEntry 2 } 1107 ipoaArpClientInArpInReqs OBJECT-TYPE 1108 SYNTAX Counter32 1109 MAX-ACCESS read-only 1110 STATUS current 1111 DESCRIPTION 1112 "The number of InATMARP requests received by this 1113 client." 1114 ::= { ipoaArpClientEntry 3 } 1116 ipoaArpClientInArpOutReqs OBJECT-TYPE 1117 SYNTAX Counter32 1118 MAX-ACCESS read-only 1119 STATUS current 1120 DESCRIPTION 1121 "The number of InATMARP requests sent by this client." 1122 ::= { ipoaArpClientEntry 4 } 1124 ipoaArpClientInArpInReplies OBJECT-TYPE 1125 SYNTAX Counter32 1126 MAX-ACCESS read-only 1127 STATUS current 1128 DESCRIPTION 1129 "The number of InATMARP replies received by this 1130 client." 1131 ::= { ipoaArpClientEntry 5 } 1133 ipoaArpClientInArpOutReplies OBJECT-TYPE 1134 SYNTAX Counter32 1135 MAX-ACCESS read-only 1136 STATUS current 1137 DESCRIPTION 1138 "Total number of InATMARP replies sent by this client." 1139 ::= { ipoaArpClientEntry 6 } 1141 ipoaArpClientInArpInvalidInReqs OBJECT-TYPE 1142 SYNTAX Counter32 1143 MAX-ACCESS read-only 1144 STATUS current 1145 DESCRIPTION 1146 "The number of times that this client detected an 1147 invalid InATMARP request." 1148 ::= { ipoaArpClientEntry 7 } 1150 ipoaArpClientInArpInvalidOutReqs OBJECT-TYPE 1151 SYNTAX Counter32 1152 MAX-ACCESS read-only 1153 STATUS current 1154 DESCRIPTION 1155 "The number of times that this client did not 1156 receive an InATMARP reply." 1157 ::= { ipoaArpClientEntry 8 } 1159 ipoaArpClientArpInReqs OBJECT-TYPE 1160 SYNTAX Counter32 1161 MAX-ACCESS read-only 1162 STATUS current 1163 DESCRIPTION 1164 "Total number of ATMARP requests received by this 1165 client." 1166 ::= { ipoaArpClientEntry 9 } 1168 ipoaArpClientArpOutReqs OBJECT-TYPE 1169 SYNTAX Counter32 1170 MAX-ACCESS read-only 1171 STATUS current 1172 DESCRIPTION 1173 "Total number of ATMARP requests sent by this client." 1174 ::= { ipoaArpClientEntry 10 } 1176 ipoaArpClientArpInReplies OBJECT-TYPE 1177 SYNTAX Counter32 1178 MAX-ACCESS read-only 1179 STATUS current 1180 DESCRIPTION 1181 "Total number of ATMARP replies received by this 1182 client." 1183 ::= { ipoaArpClientEntry 11 } 1185 ipoaArpClientArpOutReplies OBJECT-TYPE 1186 SYNTAX Counter32 1187 MAX-ACCESS read-only 1188 STATUS current 1189 DESCRIPTION 1190 "Total number of ATMARP replies sent by this client." 1191 ::= { ipoaArpClientEntry 12 } 1193 ipoaArpClientArpInNaks OBJECT-TYPE 1194 SYNTAX Counter32 1195 MAX-ACCESS read-only 1196 STATUS current 1197 DESCRIPTION 1198 "Total number of negative ATMARP replies 1199 received by this client." 1200 ::= { ipoaArpClientEntry 13 } 1202 ipoaArpClientArpOutNaks OBJECT-TYPE 1203 SYNTAX Counter32 1204 MAX-ACCESS read-only 1205 STATUS current 1206 DESCRIPTION 1207 "Total number of negative ATMARP replies sent by 1208 this client. 1210 Classic IP and ARP over ATM does not require an 1211 ATMARP client to transmit an ATMARP_NAK upon 1212 receipt of an ATMARP request from another ATMARP 1213 client. However, implementation experience has 1214 shown that this error condition is somewhat easy 1215 to create inadvertently by configuring one ATMARP 1216 client with an ipoaArpRemoteSrvrTable entry 1217 containing an ipoaArpRemoteSrvrAtmAddr value which 1218 is the ATM address of another ATMARP client-only 1219 system. 1221 If an ATMARP client supports the transmission of 1222 ATMARP_NAKs, then it should increment 1223 ipoaArpClientArpOutNaks each time it transmits 1224 an ATMARP_NAK. Otherwise, support of this 1225 object is considered optional." 1226 ::= { ipoaArpClientEntry 14 } 1228 ipoaArpClientArpUnknownOps OBJECT-TYPE 1229 SYNTAX Counter32 1230 MAX-ACCESS read-only 1231 STATUS current 1232 DESCRIPTION 1233 "The number of times that this client received 1234 an ATMARP message with an operation code for which 1235 it is not coded to support." 1236 ::= { ipoaArpClientEntry 15 } 1238 ipoaArpClientArpNoSrvrResps OBJECT-TYPE 1239 SYNTAX Counter32 1240 MAX-ACCESS read-only 1241 STATUS current 1242 DESCRIPTION 1243 "The number of times this client failed to receive 1244 a response from a ATMARP Server within the 1245 ipoaLisTimeout value for ipoaLisRetries times. 1246 This may imply that the client will re-elect a 1247 new primary ATMARP Server for this LIS from the 1248 ipoaArpRemoteSrvrTable." 1249 ::= { ipoaArpClientEntry 16 } 1251 ipoaArpClientRowStatus OBJECT-TYPE 1252 SYNTAX RowStatus 1253 MAX-ACCESS read-create 1254 STATUS current 1255 DESCRIPTION 1256 "This object allows entries to be created and 1257 deleted from the ipoaArpClientTable." 1258 REFERENCE 1259 "RFC 1903, 'Textual Conventions for Version 2 of the 1260 Simple Network Management Protocol (SNMPv2).'" 1261 ::= { ipoaArpClientEntry 17 } 1263 -- The ATMARP Server Table 1265 ipoaArpSrvrTable OBJECT-TYPE 1266 SYNTAX SEQUENCE OF IpoaArpSrvrEntry 1267 MAX-ACCESS not-accessible 1268 STATUS current 1269 DESCRIPTION 1270 "The ATMARP Servers running on this system." 1271 ::= { ipoaObjects 5 } 1273 ipoaArpSrvrEntry OBJECT-TYPE 1274 SYNTAX IpoaArpSrvrEntry 1275 MAX-ACCESS not-accessible 1276 STATUS current 1277 DESCRIPTION 1278 "Information about an ATMARP Server within a LIS. An 1279 entry in this table has two indexes: first ipAdEntAddr, 1280 which is the IP address that this system uses as a 1281 member of the LIS, and then ipoaArpSrvrAddr, which is 1282 the ATM address of the ATMARP Server. 1284 Entries may be created by a management application 1285 using the ipoaArpSrvrRowStatus object. Entries in this 1286 table may also be created by the system and not by a 1287 management application, for example via ILMI. 1289 Entries in this table may be deleted by setting the 1290 ipoaArpSrvrRowStatus object to 'destroy(6)'. This 1291 includes entries that were added by the system and not 1292 by a management application." 1293 INDEX { ipAdEntAddr, ipoaArpSrvrAddr } 1294 ::= { ipoaArpSrvrTable 1 } 1296 IpoaArpSrvrEntry ::= SEQUENCE { 1297 ipoaArpSrvrAddr IpoaAtmAddr, 1298 ipoaArpSrvrLis IpAddress, 1299 ipoaArpSrvrInArpInReqs Counter32, 1300 ipoaArpSrvrInArpOutReqs Counter32, 1301 ipoaArpSrvrInArpInReplies Counter32, 1302 ipoaArpSrvrInArpOutReplies Counter32, 1303 ipoaArpSrvrInArpInvalidInReqs Counter32, 1304 ipoaArpSrvrInArpInvalidOutReqs Counter32, 1305 ipoaArpSrvrArpInReqs Counter32, 1306 ipoaArpSrvrArpOutReplies Counter32, 1307 ipoaArpSrvrArpOutNaks Counter32, 1308 ipoaArpSrvrArpDupIpAddrs Counter32, 1309 ipoaArpSrvrArpUnknownOps Counter32, 1310 ipoaArpSrvrRowStatus RowStatus } 1312 ipoaArpSrvrAddr OBJECT-TYPE 1313 SYNTAX IpoaAtmAddr 1314 MAX-ACCESS not-accessible 1315 STATUS current 1316 DESCRIPTION 1317 "The ATM address of the ATMARP Server." 1318 ::= { ipoaArpSrvrEntry 1 } 1320 ipoaArpSrvrLis OBJECT-TYPE 1321 SYNTAX IpAddress 1322 MAX-ACCESS read-create 1323 STATUS current 1324 DESCRIPTION 1325 "The subnet address that identifies the LIS with 1326 which this server is associated." 1327 ::= { ipoaArpSrvrEntry 2 } 1329 ipoaArpSrvrInArpInReqs OBJECT-TYPE 1330 SYNTAX Counter32 1331 MAX-ACCESS read-only 1332 STATUS current 1333 DESCRIPTION 1334 "The number of InATMARP requests received by this 1335 ATMARP Server." 1336 ::= { ipoaArpSrvrEntry 3 } 1338 ipoaArpSrvrInArpOutReqs OBJECT-TYPE 1339 SYNTAX Counter32 1340 MAX-ACCESS read-only 1341 STATUS current 1342 DESCRIPTION 1343 "The number of InATMARP requests sent by this ATMARP 1344 Server." 1345 ::= { ipoaArpSrvrEntry 4 } 1347 ipoaArpSrvrInArpInReplies OBJECT-TYPE 1348 SYNTAX Counter32 1349 MAX-ACCESS read-only 1350 STATUS current 1351 DESCRIPTION 1352 "The number of InATMARP replies received by this 1353 ATMARP Server." 1354 ::= { ipoaArpSrvrEntry 5 } 1356 ipoaArpSrvrInArpOutReplies OBJECT-TYPE 1357 SYNTAX Counter32 1358 MAX-ACCESS read-only 1359 STATUS current 1360 DESCRIPTION 1361 "The number of InATMARP replies sent by this ATMARP 1362 Server." 1363 ::= { ipoaArpSrvrEntry 6 } 1365 ipoaArpSrvrInArpInvalidInReqs OBJECT-TYPE 1366 SYNTAX Counter32 1367 MAX-ACCESS read-only 1368 STATUS current 1369 DESCRIPTION 1370 "The number of invalid InATMARP requests received by 1371 this ATMARP Server." 1372 ::= { ipoaArpSrvrEntry 7 } 1374 ipoaArpSrvrInArpInvalidOutReqs OBJECT-TYPE 1375 SYNTAX Counter32 1376 MAX-ACCESS read-only 1377 STATUS current 1378 DESCRIPTION 1379 "The number of times that this server did not receive 1380 an InATMARP reply." 1381 ::= { ipoaArpSrvrEntry 8 } 1383 ipoaArpSrvrArpInReqs OBJECT-TYPE 1384 SYNTAX Counter32 1385 MAX-ACCESS read-only 1386 STATUS current 1387 DESCRIPTION 1388 "Total number of ATMARP requests received by this 1389 ATMARP Server." 1390 ::= { ipoaArpSrvrEntry 9 } 1392 ipoaArpSrvrArpOutReplies OBJECT-TYPE 1393 SYNTAX Counter32 1394 MAX-ACCESS read-only 1395 STATUS current 1396 DESCRIPTION 1397 "Total number of ATMARP replies sent by this ATMARP 1398 Server." 1399 ::= { ipoaArpSrvrEntry 10 } 1401 ipoaArpSrvrArpOutNaks OBJECT-TYPE 1402 SYNTAX Counter32 1403 MAX-ACCESS read-only 1404 STATUS current 1405 DESCRIPTION 1406 "Total number of negative ATMARP replies sent by this 1407 ATMARP Server." 1408 ::= { ipoaArpSrvrEntry 11 } 1410 ipoaArpSrvrArpDupIpAddrs OBJECT-TYPE 1411 SYNTAX Counter32 1412 MAX-ACCESS read-only 1413 STATUS current 1414 DESCRIPTION 1415 "The number of times that a duplicate IP address was 1416 detected by this ATMARP Server." 1417 ::= { ipoaArpSrvrEntry 12 } 1419 ipoaArpSrvrArpUnknownOps OBJECT-TYPE 1420 SYNTAX Counter32 1421 MAX-ACCESS read-only 1422 STATUS current 1423 DESCRIPTION 1424 "The number of times that this ATMARP Server received 1425 an ATMARP message with an operation code for which it 1426 is not coded to support." 1427 ::= { ipoaArpSrvrEntry 13 } 1429 ipoaArpSrvrRowStatus OBJECT-TYPE 1430 SYNTAX RowStatus 1431 MAX-ACCESS read-create 1432 STATUS current 1433 DESCRIPTION 1434 "This object allows entries to be created and deleted 1435 from the ipoaArpSrvrTable." 1436 REFERENCE 1437 "RFC 1903, 'Textual Conventions for Version 2 of the 1438 Simple Network Management Protocol (SNMPv2).'" 1439 ::= { ipoaArpSrvrEntry 14 } 1441 -- The Remote ATMARP Server Table 1443 ipoaArpRemoteSrvrTable OBJECT-TYPE 1444 SYNTAX SEQUENCE OF IpoaArpRemoteSrvrEntry 1445 MAX-ACCESS not-accessible 1446 STATUS current 1447 DESCRIPTION 1448 "A table of non-local ATMARP Servers associated with a 1449 LIS. An entry in this table has three indexes: first 1450 the ipoaLisSubnetAddr of the LIS for which the 1451 corresponding ATMARP Server provides ATMARP services, 1452 then the ipoaArpRemoteSrvrAtmAddr, which is the ATM 1453 address of the remote ATMARP Server, and finally the 1454 ifIndex of the interface on which the VC to the ATMARP 1455 Remote Server will be opened. An ifIndex value of 0 1456 should be used when a single VC is to be shared for 1457 ATMARP purposes by multiple interfaces." 1458 ::= { ipoaObjects 6 } 1460 ipoaArpRemoteSrvrEntry OBJECT-TYPE 1461 SYNTAX IpoaArpRemoteSrvrEntry 1462 MAX-ACCESS not-accessible 1463 STATUS current 1464 DESCRIPTION 1465 "Information about one non-local ATMARP Server." 1466 INDEX { ipoaLisSubnetAddr, ipoaArpRemoteSrvrAtmAddr, 1467 ipoaArpRemoteSrvrIfIndex } 1468 ::= { ipoaArpRemoteSrvrTable 1 } 1470 IpoaArpRemoteSrvrEntry ::= SEQUENCE { 1471 ipoaArpRemoteSrvrAtmAddr IpoaAtmAddr, 1472 ipoaArpRemoteSrvrRowStatus RowStatus, 1473 ipoaArpRemoteSrvrIfIndex InterfaceIndexOrZero, 1474 ipoaArpRemoteSrvrIpAddr IpAddress, 1475 ipoaArpRemoteSrvrAdminStatus INTEGER, 1476 ipoaArpRemoteSrvrOperStatus INTEGER } 1478 ipoaArpRemoteSrvrAtmAddr OBJECT-TYPE 1479 SYNTAX IpoaAtmAddr 1480 MAX-ACCESS not-accessible 1481 STATUS current 1482 DESCRIPTION 1483 "The ATM address of the remote ATMARP Server." 1484 ::= { ipoaArpRemoteSrvrEntry 1 } 1486 ipoaArpRemoteSrvrRowStatus OBJECT-TYPE 1487 SYNTAX RowStatus 1488 MAX-ACCESS read-create 1489 STATUS current 1490 DESCRIPTION 1491 "This object allows entries to be created and deleted 1492 from the ipoaArpRemoteSrvrTable. 1494 Deleting an ipoaArpRemoteSrvrEntry (by setting this 1495 object to destroy(6)) may affect ipoaArpClientTable 1496 entries. The object ipoaArpClientSrvrInUse in an 1497 ipoaArpClientSrvrEntry may contain the ATM address 1498 of an ATMARP Remote Server whose entry in the 1499 ipoaArpRemoteSrvrTable is being removed. In this 1500 case, any corresponding ipoaArpClientSrvrInUse 1501 objects should be at a minimum invalidated by 1502 setting their values to that of a zero length 1503 OCTET STRING. 1505 The value of ipoaArpRemoteSrvrOperStatus should be 1506 consistent with that of ipoaArpRemoteSrvrRowStatus. 1507 For example, successfully setting the value of 1508 this object to notInService(2) after its being in 1509 the up(1) state should result in 1510 ipoaArpRemoteSrvrOperStatus being set to down(2) 1511 if currently up(1)." 1512 REFERENCE 1513 "RFC 1903, 'Textual Conventions for Version 2 of the 1514 Simple Network Management Protocol (SNMPv2).'" 1515 ::= { ipoaArpRemoteSrvrEntry 2 } 1517 ipoaArpRemoteSrvrIfIndex OBJECT-TYPE 1518 SYNTAX InterfaceIndexOrZero 1519 MAX-ACCESS not-accessible 1520 STATUS current 1521 DESCRIPTION 1522 "The ifIndex of the interface that the VC to the 1523 Remote ATMARP Server is associated with." 1524 ::= { ipoaArpRemoteSrvrEntry 3 } 1526 ipoaArpRemoteSrvrIpAddr OBJECT-TYPE 1527 SYNTAX IpAddress 1528 MAX-ACCESS read-only 1529 STATUS current 1530 DESCRIPTION 1531 "The IP Address of the Remote ATMARP Server. A 1532 value of 0.0.0.0 implies that this address isn't 1533 known." 1534 DEFVAL { '00000000'H } 1535 ::= { ipoaArpRemoteSrvrEntry 4 } 1537 ipoaArpRemoteSrvrAdminStatus OBJECT-TYPE 1538 SYNTAX INTEGER { 1539 up(1), -- use this ATMARP Server 1540 down(2) -- stop using this ATMARP Server 1541 } 1542 MAX-ACCESS read-create 1543 STATUS current 1544 DESCRIPTION 1545 "The desired state for use of the ATMARP Server 1546 represented by an entry in this table. 1547 ipoaArpRemoteSrvrAdminStatus values: 1549 up(1) - Attempt to activate use of the 1550 ATMARP Server represented by this 1551 entry in the ipoaArpRemoteSrvrTable. 1552 down(2) - Deactivate use of this ATMARP 1553 Server. 1555 When a managed system creates an entry in this 1556 table ipoaArpRemoteSrvrAdminStatus and 1557 ipoaArpRemoteSrvrOperStatus are initialized as 1558 down(2) by default." 1559 DEFVAL { down } 1560 ::= { ipoaArpRemoteSrvrEntry 5 } 1562 ipoaArpRemoteSrvrOperStatus OBJECT-TYPE 1563 SYNTAX INTEGER { 1564 up(1), -- eligible for use 1565 down(2) -- not eligible for use 1566 } 1567 MAX-ACCESS read-only 1568 STATUS current 1569 DESCRIPTION 1570 "The current operational state for use of a Remote 1571 ATMARP Server. An up(1) entry has a VC 1572 established to the respective Remote ATMARP 1573 Server: 1575 up(1) - A VC exists to Remote ATMARP Server 1576 whose IP Address is stored in 1577 ipoaArpRemoteSrvrIpAddr. This VC can 1578 be determined by searching the 1579 ipoaVcTable using 1580 ipoaArpRemoteSrvrIfIndex (if not 0, 1581 otherwise ignore ipNetToMediaIfIndex 1582 index) and ipoaArpRemoteSrvrIpAddr. 1583 An ipoaArpClientEntry should exist 1584 with its ipoaArpClientSrvrInUse 1585 object having the same value as 1586 ipoaArpRemoteSrvrAtmAddr. 1587 down(2) - Entry exists without an active VC to 1588 the Remote ATMARP Server. 1590 Transition from up(1) to down(2) 1591 status may affect ipoaArpClientTable entries. 1592 The object ipoaArpClientSrvrInUse in an 1593 ipoaArpClientSrvrEntry may contain the ATM address 1594 of an ATMARP Remote Server whose entry in the 1595 ipoaArpRemoteSrvrTable is being deactivated. In 1596 this case, any corresponding ipoaArpClientSrvrInUse 1597 objects should be at a minimum invalidated by 1598 setting their values to that of a zero length 1599 OCTET STRING. 1601 If ipoaArpRemoteSrvrAdminStatus is down(2) then 1602 ipoaArpRemoteSrvrOperStatus should be down(2). 1603 If ipoaArpRemoteSrvrAdminStatus is changed to 1604 up(1) then ipoaArpRemoteSrvrOperStatus should 1605 change to up(1) if the Remote ATMARP Server 1606 entry can be activated." 1607 DEFVAL { down } 1608 ::= { ipoaArpRemoteSrvrEntry 6 } 1610 -- The ATM VC Table 1612 ipoaVcTable OBJECT-TYPE 1613 SYNTAX SEQUENCE OF IpoaVcEntry 1614 MAX-ACCESS not-accessible 1615 STATUS current 1616 DESCRIPTION 1617 "A system that supports IP over ATM is an IP system and 1618 therefore MUST support all of the appropriate tables in 1619 the SNMPv2-MIB (RFC 1907), the IF-MIB (RFC 2233), 1620 the IP-MIB (RFC 2011), the TCP-MIB (RFC 2012), and 1621 the UDP-MIB (RFC 2013). This includes the 1622 ipNetToMediaTable (the ARP cache) that is defined 1623 within the IP-MIB (RFC 2011). The ipoaVcTable 1624 keeps a set of VCs for each entry in the ARP cache 1625 that was put there by an IP over ATM system acting 1626 as either a host or server. The ipoaVcTable doesn't 1627 augment the ipNetToMediaTable (ARP Cache) since the 1628 the correspondence between tables is not necessarily 1629 one-to-one. 1631 An ipNetToMediaPhysAddress object should contain the 1632 content as defined by the IpoaAtmAddr textual 1633 convention when used to hold an IPOA-MIB ATM Address." 1634 ::= { ipoaObjects 7 } 1636 ipoaVcEntry OBJECT-TYPE 1637 SYNTAX IpoaVcEntry 1638 MAX-ACCESS not-accessible 1639 STATUS current 1640 DESCRIPTION 1641 "A VC (permanent or switched) that this host or server 1642 has opened with another member of a LIS. Additional 1643 information can be determined about the VC from the 1644 ATM-MIB. 1646 Entries in this table cannot be created by management 1647 applications. 1649 In an SVC environment, an entry is automatically added 1650 by the system as the result of ATMARP processing. 1652 In a PVC environment, an entry is automatically added 1653 to this table when an entry is created in the 1654 ipoaConfigPvcTable and the IP Address at the remote 1655 end of the PVC is discovered using InATMARP. An 1656 entry also is added to the ipNetToMediaTable." 1657 INDEX { ipNetToMediaIfIndex, 1658 ipNetToMediaNetAddress, 1659 ipoaVcVpi, 1660 ipoaVcVci 1661 } 1662 ::= { ipoaVcTable 1 } 1664 IpoaVcEntry ::= SEQUENCE { 1665 ipoaVcVpi IpoaVpiInteger, 1666 ipoaVcVci IpoaVciInteger, 1667 ipoaVcType IpoaAtmConnKind, 1668 ipoaVcNegotiatedEncapsType IpoaEncapsType, 1669 ipoaVcNegotiatedMtu Integer32 } 1671 ipoaVcVpi OBJECT-TYPE 1672 SYNTAX IpoaVpiInteger 1673 MAX-ACCESS not-accessible 1674 STATUS current 1675 DESCRIPTION 1676 "The VPI value for the Virtual Circuit." 1677 ::= { ipoaVcEntry 1 } 1679 ipoaVcVci OBJECT-TYPE 1680 SYNTAX IpoaVciInteger 1681 MAX-ACCESS not-accessible 1682 STATUS current 1683 DESCRIPTION 1684 "The VCI value for the Virtual Circuit." 1685 ::= { ipoaVcEntry 2 } 1687 ipoaVcType OBJECT-TYPE 1688 SYNTAX IpoaAtmConnKind 1689 MAX-ACCESS read-only 1690 STATUS current 1691 DESCRIPTION 1692 "The type of the Virtual Circuit." 1693 ::= { ipoaVcEntry 3 } 1695 ipoaVcNegotiatedEncapsType OBJECT-TYPE 1696 SYNTAX IpoaEncapsType 1697 MAX-ACCESS read-only 1698 STATUS current 1699 DESCRIPTION 1700 "The encapsulation type used when communicating over 1701 this circuit." 1702 ::= { ipoaVcEntry 4 } 1704 ipoaVcNegotiatedMtu OBJECT-TYPE 1705 SYNTAX Integer32 (0..65535) 1706 MAX-ACCESS read-only 1707 STATUS current 1708 DESCRIPTION 1709 "The MTU used when communicating over this circuit." 1710 ::= { ipoaVcEntry 5 } 1712 -- The ATM Config PVC Table 1714 ipoaConfigPvcTable OBJECT-TYPE 1715 SYNTAX SEQUENCE OF IpoaConfigPvcEntry 1716 MAX-ACCESS not-accessible 1717 STATUS current 1718 DESCRIPTION 1719 "This table MUST be supported when PVCs are intended to 1720 be supported in order to enable the setup of PVCs for 1721 use by IP." 1722 ::= { ipoaObjects 8 } 1724 ipoaConfigPvcEntry OBJECT-TYPE 1725 SYNTAX IpoaConfigPvcEntry 1726 MAX-ACCESS not-accessible 1727 STATUS current 1728 DESCRIPTION 1729 "Defines a single PVC that exists at this host for 1730 use by IP." 1731 INDEX { ipoaConfigPvcIfIndex, 1732 ipoaConfigPvcVpi, 1733 ipoaConfigPvcVci 1734 } 1735 ::= { ipoaConfigPvcTable 1 } 1737 IpoaConfigPvcEntry ::= SEQUENCE { 1738 ipoaConfigPvcIfIndex InterfaceIndex, 1739 ipoaConfigPvcVpi IpoaVpiInteger, 1740 ipoaConfigPvcVci IpoaVciInteger, 1741 ipoaConfigPvcDefaultMtu Integer32, 1742 ipoaConfigPvcRowStatus RowStatus } 1744 ipoaConfigPvcIfIndex OBJECT-TYPE 1745 SYNTAX InterfaceIndex 1746 MAX-ACCESS not-accessible 1747 STATUS current 1748 DESCRIPTION 1749 "The ifIndex of the ATM Interface that this PVC 1750 is associated with." 1751 ::= { ipoaConfigPvcEntry 1 } 1753 ipoaConfigPvcVpi OBJECT-TYPE 1754 SYNTAX IpoaVpiInteger 1755 MAX-ACCESS not-accessible 1756 STATUS current 1757 DESCRIPTION 1758 "The VPI value for the Virtual Circuit." 1759 ::= { ipoaConfigPvcEntry 2 } 1761 ipoaConfigPvcVci OBJECT-TYPE 1762 SYNTAX IpoaVciInteger 1763 MAX-ACCESS not-accessible 1764 STATUS current 1765 DESCRIPTION 1766 "The VCI value for the Virtual Circuit." 1767 ::= { ipoaConfigPvcEntry 3 } 1769 ipoaConfigPvcDefaultMtu OBJECT-TYPE 1770 SYNTAX Integer32 (0..65535) 1771 MAX-ACCESS read-create 1772 STATUS current 1773 DESCRIPTION 1774 "Classical IP and ARP over ATM allows use of 1775 other MTU values for PVCs but considers how a 1776 value other than 9180 could be selected to be out 1777 of scope. ipoaConfigPvcDefaultMtu can be used to 1778 configure the MTU to be used for the PVC. 1779 Both ends MUST have the same value configured." 1780 DEFVAL { 9180 } 1781 ::= { ipoaConfigPvcEntry 4 } 1783 ipoaConfigPvcRowStatus OBJECT-TYPE 1784 SYNTAX RowStatus 1785 MAX-ACCESS read-create 1786 STATUS current 1787 DESCRIPTION 1788 "This object allows rows to be created and deleted in 1789 the ipoaConfigPvcTable. Creation of an entry in this 1790 table should eventually result in the creation of an 1791 ipNetToMediaEntry and a corresponding ipoaVcEntry 1792 after InATMARP has determined the destination address 1793 of the remote system that the PVC is connected to. 1794 Setting this object to destroy(6) should remove the 1795 corresponding ipNetToMediaTable and ipoaVcTable 1796 entries." 1797 REFERENCE 1798 "RFC 1903, 'Textual Conventions for Version 2 of the 1799 Simple Network Management Protocol (SNMPv2).'" 1800 ::= { ipoaConfigPvcEntry 5 } 1802 -- Notifications 1804 ipoaTrapPrefix OBJECT IDENTIFIER ::= { ipoaNotifications 0 } 1806 ipoaMtuExceeded NOTIFICATION-TYPE 1807 OBJECTS { 1808 ipoaVcNegotiatedMtu 1809 } 1810 STATUS current 1811 DESCRIPTION 1812 "A frame was received that exceeds the negotiated 1813 MTU size. The VPI and VCI of the VC for which this 1814 condition was detected can be determined from the 1815 index values for ipoaVcNegotiatedMtu. In addition, 1816 the ifIndex and IP Address can be determined as 1817 well (refer to the ipoaVcTable)." 1818 ::= { ipoaTrapPrefix 1 } 1820 ipoaDuplicateIpAddress NOTIFICATION-TYPE 1821 OBJECTS { 1822 ipNetToMediaIfIndex, 1823 ipNetToMediaNetAddress, 1824 ipNetToMediaPhysAddress, 1825 ipNetToMediaPhysAddress 1826 } 1827 STATUS current 1828 DESCRIPTION 1829 "The ATMARP Server has detected more than one ATM end 1830 point attempting to associate the same IP address with 1831 different ATM addresses." 1833 ::= { ipoaTrapPrefix 2 } 1835 ipoaLisCreate NOTIFICATION-TYPE 1836 OBJECTS { 1837 ipoaLisSubnetAddr 1838 } 1839 STATUS current 1840 DESCRIPTION 1841 "Generation of this trap occurs when an ipoaLisEntry is 1842 created while the ipoaLisTrapEnable.0 object has the 1843 value enabled(1)." 1844 ::= { ipoaTrapPrefix 3 } 1846 ipoaLisDelete NOTIFICATION-TYPE 1847 OBJECTS { 1848 ipoaLisSubnetAddr 1849 } 1850 STATUS current 1851 DESCRIPTION 1852 "Generation of this trap occurs when an ipoaLisEntry is 1853 deleted while the ipoaLisTrapEnable.0 object has the 1854 value enabled(1)." 1855 ::= { ipoaTrapPrefix 4 } 1857 -- Conformance Definitions 1859 ipoaGroups OBJECT IDENTIFIER ::= { ipoaConformance 1 } 1861 ipoaCompliances OBJECT IDENTIFIER ::= { ipoaConformance 2 } 1863 -- compliance statements 1865 ipoaCompliance MODULE-COMPLIANCE 1866 STATUS current 1867 DESCRIPTION 1868 "The compliance statement for agents that support the 1869 IPOA-MIB." 1870 MODULE -- this module 1871 MANDATORY-GROUPS { ipoaGeneralGroup, 1872 ipoaBasicNotificationsGroup 1873 } 1874 GROUP ipoaClientGroup 1875 DESCRIPTION 1876 "This group is mandatory for all hosts where IP 1877 over ATM client support is present." 1878 GROUP ipoaSrvrGroup 1879 DESCRIPTION 1880 "This group is mandatory for all hosts where ATMARP 1881 Servers are present." 1882 GROUP ipoaSrvrNotificationsGroup 1883 DESCRIPTION 1884 "This group is mandatory for all hosts where ATMARP 1885 Servers are present." 1886 GROUP ipoaLisNotificationsGroup 1887 DESCRIPTION 1888 "This group is mandatory for all hosts where 1889 ATMARP client only support is present and 1890 ipoaLisTrapEnable is allowed to be set to 1891 enabled(1)." 1892 GROUP ipoaLisTableGroup 1893 DESCRIPTION 1894 "This group is mandatory for all entities which 1895 support IP over ATM SVCs. Support of objects in 1896 this group by IP over ATM clients which only 1897 support IP over ATM PVCs is optional." 1899 OBJECT ipoaLisDefaultMtu 1900 MIN-ACCESS read-only 1901 DESCRIPTION 1902 "The agent is not required to allow the user 1903 to change the default MTU from the value 9180. 1905 The agent is not required to support a SET 1906 operation to this object in the absence of 1907 adequate security." 1909 OBJECT ipoaLisDefaultEncapsType 1910 MIN-ACCESS read-only 1911 DESCRIPTION 1912 "The agent is not required to allow the user to 1913 specify the default encapsulation type for the 1914 LIS. 1916 The agent is not required to support a SET 1917 operation to this object in the absence of 1918 adequate security." 1920 OBJECT ipoaLisInactivityTimer 1921 MIN-ACCESS read-only 1922 DESCRIPTION 1923 "The agent is not required to support a SET 1924 operation to this object in the absence of 1925 adequate security." 1927 OBJECT ipoaLisMinHoldingTime 1928 MIN-ACCESS read-only 1929 DESCRIPTION 1930 "The agent is not required to support a SET 1931 operation to this object in the absence of 1932 adequate security." 1934 OBJECT ipoaLisQDepth 1935 MIN-ACCESS read-only 1936 DESCRIPTION 1937 "The agent is not required to support a SET 1938 operation to this object in the absence of 1939 adequate security." 1941 OBJECT ipoaLisMaxCalls 1942 MIN-ACCESS read-only 1943 DESCRIPTION 1944 "The agent is not required to support a SET 1945 operation to this object in the absence of 1946 adequate security." 1948 OBJECT ipoaLisCacheEntryAge 1949 MIN-ACCESS read-only 1950 DESCRIPTION 1951 "The agent is not required to support a SET 1952 operation to this object in the absence of 1953 adequate security." 1955 OBJECT ipoaLisRetries 1956 MIN-ACCESS read-only 1957 DESCRIPTION 1958 "The agent is not required to allow the user 1959 to change the default number of times an ATMARP 1960 request will be retried when no response is 1961 received from the default of 2. 1963 The agent is not required to support a SET 1964 operation to this object in the absence of 1965 adequate security." 1967 OBJECT ipoaLisTimeout 1968 MIN-ACCESS read-only 1969 DESCRIPTION 1970 "The agent is not required to allow the user 1971 to change the default retransmission time from 1972 the default of 10 seconds. 1974 The agent is not required to support a SET 1975 operation to this object in the absence of 1976 adequate security." 1978 OBJECT ipoaLisDefaultPeakCellRate 1979 MIN-ACCESS read-only 1980 DESCRIPTION 1981 "Implementations that do not support IP over 1982 ATM SVC usage are not required to allow the 1983 user to specify a best effort default peak cell 1984 rate since typically the ipoaLisTable won't 1985 exist. 1987 The agent is not required to support a SET 1988 operation to this object in the absence of 1989 adequate security." 1991 OBJECT ipoaLisIfMappingRowStatus 1992 SYNTAX INTEGER { 1993 active(1) -- subset of RowStatus 1994 } 1995 MIN-ACCESS read-only 1996 DESCRIPTION 1997 "The agent is not required to support a SET 1998 operation to this object, and only one 1999 of the six enumerated values for the 2000 RowStatus textual convention need be 2001 supported, specifically: active(1)." 2003 OBJECT ipoaArpClientAtmAddr 2004 MIN-ACCESS read-only 2005 DESCRIPTION 2006 "The agent is not required to support a SET 2007 operation to this object in the absence of 2008 adequate security." 2010 OBJECT ipoaArpSrvrLis 2011 MIN-ACCESS read-only 2012 DESCRIPTION 2013 "The agent is not required to support a SET 2014 operation to this object in the absence of 2015 adequate security." 2017 OBJECT ipoaArpRemoteSrvrAdminStatus 2018 MIN-ACCESS read-only 2019 DESCRIPTION 2020 "The agent is not required to support a SET 2021 operation to this object in the absence of 2022 adequate security. In this case the value of 2023 this object should be up(1) when a VC 2024 exists to the Remote ATMARP Server or 2025 otherwise down(2), and the agent should not 2026 allow a SET operation to this object." 2028 OBJECT ipoaConfigPvcDefaultMtu 2029 MIN-ACCESS read-only 2030 DESCRIPTION 2031 "The agent is not required to support a SET 2032 operation to this object in the absence of 2033 adequate security." 2035 OBJECT ipoaLisRowStatus 2036 SYNTAX INTEGER { 2037 active(1) -- subset of RowStatus 2038 } 2039 MIN-ACCESS read-only 2040 DESCRIPTION 2041 "Write access is not required, and only one 2042 of the six enumerated values for the 2043 RowStatus textual convention need be 2044 supported, specifically: active(1)." 2046 OBJECT ipoaArpClientRowStatus 2047 SYNTAX INTEGER { 2048 active(1) -- subset of RowStatus 2049 } 2050 MIN-ACCESS read-only 2051 DESCRIPTION 2052 "Write access is not required, and only one 2053 of the six enumerated values for the 2054 RowStatus textual convention need be 2055 supported, specifically: active(1)." 2057 OBJECT ipoaArpRemoteSrvrRowStatus 2058 SYNTAX INTEGER { 2059 active(1) -- subset of RowStatus 2060 } 2061 MIN-ACCESS read-only 2062 DESCRIPTION 2063 "Write access is not required, and only one 2064 of the six enumerated values for the 2065 RowStatus textual convention need be 2066 supported, specifically: active(1)." 2068 OBJECT ipoaArpSrvrRowStatus 2069 SYNTAX INTEGER { 2070 active(1) -- subset of RowStatus 2071 } 2072 MIN-ACCESS read-only 2073 DESCRIPTION 2074 "Write access is not required, and only one 2075 of the six enumerated values for the 2076 RowStatus textual convention need be 2077 supported, specifically: active(1)." 2079 OBJECT ipoaConfigPvcRowStatus 2080 SYNTAX INTEGER { 2081 active(1) -- subset of RowStatus 2082 } 2083 MIN-ACCESS read-only 2084 DESCRIPTION 2085 "Write access is not required, and only one 2086 of the six enumerated values for the 2087 RowStatus textual convention need be 2088 supported, specifically: active(1)." 2090 OBJECT ipoaArpClientArpOutNaks 2091 MIN-ACCESS not-accessible 2092 DESCRIPTION 2093 "Classic IP and ARP over ATM does not require 2094 an ATMARP client to transmit an ATMARP_NAK 2095 upon receipt of an ATMARP request from another 2096 ATMARP client. This object should be 2097 implemented when an ATMARP client supports the 2098 transmission of ATMARP_NAKs." 2100 ::= { ipoaCompliances 1 } 2102 -- units of conformance 2104 ipoaGeneralGroup OBJECT-GROUP 2105 OBJECTS { 2106 ipoaLisTrapEnable, 2107 ipoaLisSubnetAddr, 2108 ipoaLisDefaultMtu, 2109 ipoaLisDefaultEncapsType, 2110 ipoaLisInactivityTimer, 2111 ipoaLisMinHoldingTime, 2112 ipoaLisQDepth, 2113 ipoaLisMaxCalls, 2114 ipoaLisCacheEntryAge, 2115 ipoaLisRetries, 2116 ipoaLisTimeout, 2117 ipoaLisDefaultPeakCellRate, 2118 ipoaLisActiveVcs, 2119 ipoaLisRowStatus, 2120 ipoaLisIfMappingRowStatus, 2121 ipoaArpRemoteSrvrRowStatus, 2122 ipoaArpRemoteSrvrIpAddr, 2123 ipoaArpRemoteSrvrAdminStatus, 2124 ipoaArpRemoteSrvrOperStatus, 2125 ipoaVcType, 2126 ipoaVcNegotiatedEncapsType, 2127 ipoaVcNegotiatedMtu, 2128 ipoaConfigPvcDefaultMtu, 2129 ipoaConfigPvcRowStatus 2130 } 2131 STATUS current 2132 DESCRIPTION 2133 "This group is mandatory for all IP over ATM entities." 2134 ::= { ipoaGroups 1 } 2136 ipoaClientGroup OBJECT-GROUP 2137 OBJECTS { 2138 ipoaArpClientAtmAddr, 2139 ipoaArpClientSrvrInUse, 2140 ipoaArpClientInArpInReqs, 2141 ipoaArpClientInArpOutReqs, 2142 ipoaArpClientInArpInReplies, 2143 ipoaArpClientInArpOutReplies, 2144 ipoaArpClientInArpInvalidInReqs, 2145 ipoaArpClientInArpInvalidOutReqs, 2146 ipoaArpClientArpInReqs, 2147 ipoaArpClientArpOutReqs, 2148 ipoaArpClientArpInReplies, 2149 ipoaArpClientArpOutReplies, 2150 ipoaArpClientArpInNaks, 2151 ipoaArpClientArpOutNaks, 2152 ipoaArpClientArpUnknownOps, 2153 ipoaArpClientArpNoSrvrResps, 2154 ipoaArpClientRowStatus 2155 } 2156 STATUS current 2157 DESCRIPTION 2158 "This group is mandatory for all hosts where an IP 2159 over ATM client is present." 2160 ::= { ipoaGroups 2 } 2162 ipoaSrvrGroup OBJECT-GROUP 2163 OBJECTS { 2164 ipoaArpSrvrLis, 2165 ipoaArpSrvrInArpInReqs, 2166 ipoaArpSrvrInArpOutReqs, 2167 ipoaArpSrvrInArpInReplies, 2168 ipoaArpSrvrInArpOutReplies, 2169 ipoaArpSrvrInArpInvalidInReqs, 2170 ipoaArpSrvrInArpInvalidOutReqs, 2171 ipoaArpSrvrArpInReqs, 2172 ipoaArpSrvrArpOutReplies, 2173 ipoaArpSrvrArpOutNaks, 2174 ipoaArpSrvrArpDupIpAddrs, 2175 ipoaArpSrvrArpUnknownOps, 2176 ipoaArpSrvrRowStatus 2177 } 2178 STATUS current 2179 DESCRIPTION 2180 "This group is mandatory for all hosts where ATMARP 2181 Servers are present." 2182 ::= { ipoaGroups 3 } 2184 ipoaBasicNotificationsGroup NOTIFICATION-GROUP 2185 NOTIFICATIONS { 2186 ipoaMtuExceeded 2187 } 2188 STATUS current 2189 DESCRIPTION 2190 "The notification which an IP over ATM entity 2191 is required to implement." 2192 ::= { ipoaGroups 4 } 2194 ipoaSrvrNotificationsGroup NOTIFICATION-GROUP 2195 NOTIFICATIONS { 2196 ipoaDuplicateIpAddress 2197 } 2198 STATUS current 2199 DESCRIPTION 2200 "The notification which an IP over ATM ATMARP 2201 Server is required to implement." 2202 ::= { ipoaGroups 5 } 2204 ipoaLisNotificationsGroup NOTIFICATION-GROUP 2205 NOTIFICATIONS { 2206 ipoaLisCreate, 2207 ipoaLisDelete 2208 } 2209 STATUS current 2210 DESCRIPTION 2211 "The LIS-related notifications which are required 2212 to be implemented by an IP over ATM ATMARP server, 2213 as well as by any IP over ATM client which allows 2214 ipoaLisTrapEnable to be set to enabled(1)." 2215 ::= { ipoaGroups 6 } 2217 ipoaLisTableGroup OBJECT-GROUP 2218 OBJECTS { 2219 ipoaLisTrapEnable, 2220 ipoaLisSubnetAddr, 2221 ipoaLisDefaultMtu, 2222 ipoaLisDefaultEncapsType, 2223 ipoaLisInactivityTimer, 2224 ipoaLisMinHoldingTime, 2225 ipoaLisQDepth, 2226 ipoaLisMaxCalls, 2227 ipoaLisCacheEntryAge, 2228 ipoaLisRetries, 2229 ipoaLisTimeout, 2230 ipoaLisDefaultPeakCellRate, 2231 ipoaLisActiveVcs, 2232 ipoaLisRowStatus, 2233 ipoaLisIfMappingRowStatus, 2234 ipoaArpRemoteSrvrRowStatus, 2235 ipoaArpRemoteSrvrIpAddr, 2236 ipoaArpRemoteSrvrAdminStatus, 2237 ipoaArpRemoteSrvrOperStatus 2238 } 2239 STATUS current 2240 DESCRIPTION 2241 "This group is mandatory for all entities which 2242 support IP over ATM SVCs. Support of objects in 2243 this group by IP over ATM clients which only 2244 support IP over ATM PVCs is optional." 2245 ::= { ipoaGroups 7 } 2247 END 2249 5. Security Considerations 2251 Certain management information defined in this MIB MAY be considered 2252 sensitive in some network environments. Therefore, authentication of 2253 received SNMP requests and controlled access to management information 2254 SHOULD be employed in such environments. The method for this 2255 authentication is a function of the SNMP Administrative Framework, and 2256 has not been expanded by this MIB. 2258 Several objects in this MIB allow write access or provide for row 2259 creation. Allowing this support in a non-secure environment can have 2260 a negative effect on network operations. It is RECOMMENDED that 2261 implementers seriously consider whether set operations or row creation 2262 be allowed without providing, at a minimum, authentication of request 2263 origin. It is RECOMMENDED that without such support that the 2264 following objects be implemented as read-only: 2266 o ipoaLisDefaultMtu 2267 o ipoaLisDefaultEncapsType 2268 o ipoaLisInactivityTimer 2269 o ipoaLisMinHoldingTime 2270 o ipoaLisQDepth 2271 o ipoaLisMaxCalls 2272 o ipoaLisCacheEntryAge 2273 o ipoaLisRetries 2274 o ipoaLisTimeout 2275 o ipoaLisDefaultPeakCellRate 2276 o ipoaArpClientAtmAddr 2277 o ipoaArpSrvrLis 2278 o ipoaArpRemoteSrvrAdminStatus, show status as being either 2279 up(1) when a VC exists to the Remote ATMARP Server or 2280 otherwise down(2). Don't allow set support. 2281 ipoaArpRemoteSrvrOperStatus would have the same value as 2282 ipoaArpRemoteSrvrAdminStatus. 2283 o ipoaConfigPvcDefaultMtu 2284 o ipoaLisRowStatus 2285 o ipoaArpClientRowStatus 2286 o ipoaArpRemoteSrvrRowStatus 2287 o ipoaArpSrvrRowStatus 2288 o ipoaConfigPvcRowStatus 2289 o ipoaLisIfMappingRowStatus 2291 6. Intellectual Property 2293 The IETF takes no position regarding the validity or scope of any 2294 intellectual property or other rights that might be claimed to pertain 2295 to the implementation or use of the technology described in this 2296 document or the extent to which any license under such rights might or 2297 might not be available; neither does it represent that it has made any 2298 effort to identify any such rights. Information on the IETF's 2299 procedures with respect to rights in standards-track and standards- 2300 related documentation can be found in BCP-11. Copies of claims of 2301 rights made available for publication and any assurances of licenses 2302 to be made available, or the result of an attempt made to obtain a 2303 general license or permission for the use of such proprietary rights 2304 by implementors or users of this specification can be obtained from 2305 the IETF Secretariat. 2307 The IETF invites any interested party to bring to its attention any 2308 copyrights, patents or patent applications, or other proprietary 2309 rights which may cover technology that may be required to practice 2310 this standard. Please address the information to the IETF Executive 2311 Director. 2313 7. Acknowledgments 2315 This document is a product of the Internetworking Over NBMA Working 2316 Group. The authors of this document would like to recognize Keith 2317 McCloghrie from Cisco Systems for his support as our mentor from the 2318 Network Management Area. 2320 8. References 2322 [1] Case, J., McCloghrie, K., Rose, M., and Waldbusser S., "Structure 2323 of Management Information for Version 2 of the Simple Network 2324 Management Protocol (SNMPv2)", RFC 1902, January 1996. 2326 [2] McCloghrie, K., and Kastenholtz, F., "The Interfaces Group MIB 2327 using SMIv2", RFC 2233, November 1997. 2329 [3] Laubach M., and Halpern J., "Classical IP and ARP over ATM", 2330 Internet Draft, March 26, 1997. 2332 [4] Ahmed, M., and Tesink, K., "Definitions of Managed Objects for ATM 2333 Management Version 8.0 using SMIv2", RFC 1695, August 1994. 2335 [5] McCloghrie, K., and M. Rose, Editors, "Management Information Base 2336 for Network Management of TCP/IP-based internets: MIB-II", STD 17, 2337 RFC 1213, March 1991. 2339 [6] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Textual 2340 Conventions for Version 2 of the Simple Network Management Protocol 2341 (SNMPv2)", RFC 1903, January 1996. 2343 [7] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Protocol 2344 Operations for Version 2 of the Simple Network Management Protocol 2345 (SNMPv2)", RFC 1905, January 1996. 2347 [8] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Conformance 2348 Statements for Version 2 of the Simple Network Management Protocol 2349 (SNMPv2)", RFC 1904, January 1996. 2351 [9] McCloghrie K., "Management Information Base for the Internet 2352 Protocol using SMIv2", RFC 2011, November 1996. 2354 [10] Bradner, S., "Key words for use in RFCs to Indicate Requirement 2355 Levels", BCP 14, RFC 2119, March 1997. 2357 [11] Perez, M., Liaw, F., Mankin, A., Hoffman, E., Grossman, D., Malis, 2358 A., "ATM Signaling Support for IP over ATM", RFC 1755, February 2359 1995. 2361 [12] Case, J., McCloghrie, K., Rose, M., and Waldbusser, S., "Transport 2362 Mappings for Version 2 of the Simple Network Management Protocol 2363 (SNMPv2)", RFC 1906, January 1996. 2365 [13] Case, J., McCloghrie, K., Rose, M., and Waldbusser, S., "Management 2366 Information Base for Version 2 of the Simple Network Management 2367 Protocol (SNMPv2)", RFC 1907, January 1996. 2369 [14] Case, J., McCloghrie, K., Rose, M., and Waldbusser, S., 2370 "Coexistence between Version 1 and Version 2 of the Internet- 2371 standard Network Management Framework", RFC 1908, January 1996. 2373 9. Authors' Addresses 2375 Maria N. Greene 2376 Xedia Corp. 2377 119 Russell Dr. 2378 Littleton, MA 01460 2379 E-mail: maria@xedia.com 2381 James Luciani 2382 Bay Networks, Inc. 2383 3 Federal St., BL3-04 2384 Billerica, MA 01821, USA 2385 Phone: +1-508-439-4734 2386 E-mail: luciani@baynetworks.com 2388 Kenneth D. White 2389 Dept. G80/Bldg 503 2390 IBM Corporation 2391 Research Triangle Park, NC 27709, USA 2392 E-mail: kennethw@vnet.ibm.com 2394 Ted T.I. Kuo 2395 Bay Networks, Inc. 2396 4401 Great America Parkway 2397 Santa Clara, CA 95052-8185 2398 Phone: +1-408-495-7319 2399 fax: +1-408-495-1905 2400 E-mail: ted_kuo@Baynetworks.com 2402 10. Full Copyright Statement 2404 Copyright (C) The Internet Society (1998). All Rights Reserved. 2406 This document and translations of it may be copied and furnished to 2407 others, and derivative works that comment on or otherwise explain it 2408 or assist in its implementation may be prepared, copied, published and 2409 distributed, in whole or in part, without restriction of any kind, 2410 provided that the above copyright notice and this paragraph are 2411 included on all such copies and derivative works. However, this 2412 document itself may not be modified in any way, such as by removing 2413 the copyright notice or references to the Internet Society or other 2414 Internet organizations, except as needed for the purpose of developing 2415 Internet standards in which case the procedures for copyrights defined 2416 in the Internet Standards process must be followed, or as required to 2417 translate it into languages other than English. 2419 The limited permissions granted above are perpetual and will not be 2420 revoked by the Internet Society or its successors or assigns. 2422 This document and the information contained herein is provided on an 2423 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING 2424 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT 2425 NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN 2426 WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF 2427 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.