idnits 2.17.1 draft-ietf-appleip-mib2-01.txt: ** The Abstract section seems to be numbered Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Cannot find the required boilerplate sections (Copyright, IPR, etc.) in this document. Expected boilerplate is as follows today (2024-04-26) according to https://trustee.ietf.org/license-info : IETF Trust Legal Provisions of 28-dec-2009, Section 6.a: This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79. IETF Trust Legal Provisions of 28-dec-2009, Section 6.b(i), paragraph 2: Copyright (c) 2024 IETF Trust and the persons identified as the document authors. All rights reserved. IETF Trust Legal Provisions of 28-dec-2009, Section 6.b(i), paragraph 3: This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- ** Missing document type: Expected "INTERNET-DRAFT" in the upper left hand corner of the first page ** Missing expiration date. The document expiration date should appear on the first and last page. ** The document seems to lack a 1id_guidelines paragraph about Internet-Drafts being working documents. ** The document seems to lack a 1id_guidelines paragraph about 6 months document validity. ** The document seems to lack a 1id_guidelines paragraph about the list of current Internet-Drafts. ** The document seems to lack a 1id_guidelines paragraph about the list of Shadow Directories. ** Expected the document's filename to be given on the first page, but didn't find any == No 'Intended status' indicated for this document; assuming Proposed Standard Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an Abstract section. (A line matching the expected section header was found, but with an unexpected indentation: ' 2. Abstract' ) ** The document seems to lack an Introduction section. ** The document seems to lack a Security Considerations section. ** The document seems to lack an IANA Considerations section. (See Section 2.2 of https://www.ietf.org/id-info/checklist for how to handle the case when there are no actions for IANA.) ** The document seems to lack an Authors' Addresses Section. ** There are 195 instances of too long lines in the document, the longest one being 8 characters in excess of 72. ** The abstract seems to contain references ([2], [3], [4], [5], [6], [7], [8], [9], [10], [1]), which it shouldn't. Please replace those with straight textual mentions of the documents in question. Miscellaneous warnings: ---------------------------------------------------------------------------- == Line 1876 has weird spacing: '... is, it effec...' == Line 2117 has weird spacing: '... is, it effec...' == Line 2252 has weird spacing: '... is, it effec...' == Line 2587 has weird spacing: '... is, it effec...' == Line 3033 has weird spacing: '... is, it effec...' == (3 more instances...) == Couldn't figure out when the document was first submitted -- there may comments or warnings related to the use of a disclaimer for pre-RFC5378 work that could not be issued because of this. Please check the Legal Provisions document at https://trustee.ietf.org/license-info to determine if you need the pre-RFC5378 disclaimer. -- The document date (April 30, 1993) is 11319 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) -- Missing reference section? '1' on line 3907 looks like a reference -- Missing reference section? '2' on line 3913 looks like a reference -- Missing reference section? '3' on line 3918 looks like a reference -- Missing reference section? '4' on line 3924 looks like a reference -- Missing reference section? '5' on line 3930 looks like a reference -- Missing reference section? '7' on line 3942 looks like a reference -- Missing reference section? '8' on line 3948 looks like a reference -- Missing reference section? '9' on line 3954 looks like a reference -- Missing reference section? '10' on line 3959 looks like a reference -- Missing reference section? '6' on line 3936 looks like a reference Summary: 16 errors (**), 0 flaws (~~), 8 warnings (==), 11 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Internet Draft AppleTalk MIB II April 1993 4 Expiration Date: November 5, 1993 6 AppleTalk Management Information Base II 8 April 30, 1993 10 Steven Waldbusser 11 Karen Frisa 13 Carnegie Mellon University 14 4910 Forbes Ave. 15 Pittsburgh, PA 15213 17 waldbusser@andrew.cmu.edu 18 frisa@andrew.cmu.edu 20 1. Status of this Memo 22 This draft document will be submitted to the RFC editor as an 23 experimental extension to the SNMP MIB. Distribution of this 24 memo is unlimited. Please send comments to the authors. 26 This document is an Internet Draft. Internet Drafts are 27 working documents of the Internet Engineering Task Force 28 (IETF), its Areas, and its Working Groups. Note that other 29 groups may also distribute working documents as Internet 30 Drafts. Internet Drafts are draft documents valid for a 31 maximum of six months. Internet Drafts may be updated, 32 replaced, or obsoleted by other documents at any time. It is 33 not appropriate to use Internet Drafts as reference material 34 or to cite them other than as a "working draft" or "work in 35 progress." Please check the 1id-abstracts.txt listing 36 contained in the internet-drafts Shadow Directories on 37 nic.ddn.mil, nnsc.nsf.net, nic.nordu.net, ftp.nisc.sri.com, or 38 munnari.oz.au to learn the current status of any Internet 39 Draft. 41 Table of Contents 43 1 Status of this Memo ................................... 1 44 2 Abstract .............................................. 2 45 3 Historical Perspective ................................ 3 46 4 Additions and Changes ................................. 5 47 4.1 New Groups .......................................... 5 48 4.2 Additional Variables ................................ 5 49 4.2.1 AARP Additions .................................... 5 50 4.2.2 ATPort Additions .................................. 5 51 4.2.3 DDP Addition ...................................... 6 52 4.2.4 RTMP Additions .................................... 6 53 4.2.5 KIP Addition ...................................... 6 54 4.2.6 ZIP Additions ..................................... 6 55 4.2.7 NBP Additions ..................................... 6 56 4.2.8 ATEcho Additions .................................. 6 57 4.3 Deprecations ........................................ 6 58 4.4 Changes ............................................. 7 59 5 Objects ............................................... 9 60 5.1 Format of Definitions ............................... 9 61 6 Overview .............................................. 10 62 6.1 Structure of MIB .................................... 10 63 6.2 The LocalTalk Link Access Protocol Group ............ 11 64 6.3 The AppleTalk Address Resolution Protocol Group ..... 11 65 6.4 The AppleTalk Port Group ............................ 11 66 6.5 The Datagram Delivery Protocol Group ................ 11 67 6.6 The Datagram Delivery Protocol Router Group ......... 11 68 6.7 The Routing Table Maintenance Protocol Group ........ 11 69 6.8 The Routing Table Maintenance Protocol Stub Group 70 .................................................... 12 71 6.9 The Kinetics Internet Protocol Group ................ 12 72 6.10 The Zone Information Protocol Router Group ......... 12 73 6.11 The Zone Information Protocol End Node Group ....... 12 74 6.12 The Name Binding Protocol Group .................... 12 75 6.13 The AppleTalk Echo Protocol Group .................. 13 76 6.14 The AppleTalk Transaction Protocol Group ........... 13 77 6.15 The Printer Access Protocol Group .................. 13 78 6.16 The AppleTalk Session Protocol Group ............... 13 79 6.17 The AppleTalk Data Stream Protocol Group ........... 13 80 6.18 The AppleTalk Port Point to Point Group ............ 13 81 6.19 The Per Port Counters Group ........................ 13 82 6.20 Textual Conventions ................................ 14 83 7 Definitions ........................................... 15 84 8 Acknowledgments ....................................... 97 85 9 References ............................................ 99 86 2. Abstract 88 This memo defines an experimental portion of the Management 89 Information Base (MIB) for use with network management 90 protocols in TCP/IP-based internets. In particular, it 91 defines objects for managing AppleTalk networks. 93 RFC1243 defines a set of MIB objects for managing the lower 94 layers of the AppleTalk protocol stack, up to the Network 95 layer. This memo defines additional objects that exist in the 96 AppleTalk portion of the MIB. These objects provide for the 97 management of the transport and session layers of the 98 AppleTalk protocol stack, as well as extensions to the lower 99 layers. This is achieved in an upwardly-compatable fashion. 101 This memo does not specify a standard for the Internet 102 community. 104 3. Historical Perspective 106 As reported in RFC 1052, IAB Recommendations for the 107 Development of Internet Network Management Standards [1], a 108 two-prong strategy for network management of TCP/IP-based 109 internets was undertaken. In the short-term, the Simple 110 Network Management Protocol (SNMP), defined in RFC 1067, was 111 to be used to manage nodes in the Internet community. In the 112 long-term, the use of the OSI network management framework was 113 to be examined. Two documents were produced to define the 114 management information: RFC 1065, which defined the Structure 115 of Management Information (SMI), and RFC 1066, which defined 116 the Management Information Base (MIB). Both of these 117 documents were designed so as to be compatible with both the 118 SNMP and the OSI network management framework. 120 This strategy was quite successful in the short-term: 121 Internet-based network management technology was fielded, by 122 both the research and commercial communities, within a few 123 months. As a result of this, portions of the Internet 124 community became network manageable in a timely fashion. 126 As reported in RFC 1109, Report of the Second Ad Hoc Network 127 Management Review Group [2], the requirements of the SNMP and 128 the OSI network management frameworks were more different than 129 anticipated. As such, the requirement for compatibility 130 between the SMI/MIB and both frameworks was suspended. This 131 action permitted the operational network management framework, 132 based on the SNMP, to respond to new operational needs in the 133 Internet community by producing MIB-II. 135 In May of 1990, the core documents were elevated to "Standard 136 Protocols" with "Recommended" status. As such, the Internet- 137 standard network management framework consists of: Structure 138 and Identification of Management Information for TCP/IP-based 139 internets, RFC 1155 [3], which describes how managed objects 140 contained in the MIB are defined; Management Information Base 141 for Network Management of TCP/IP-based internets, which 142 describes the managed objects contained in the MIB, RFC 1156 143 [4]; and, the Simple Network Management Protocol, RFC 1157 144 [5], which defines the protocol used to manage these objects. 146 Consistent with the IAB directive to produce simple, workable 147 systems in the short-term, the list of managed objects defined 148 in the Internet-standard MIB was derived by taking only those 149 elements which are considered essential. However, the SMI 150 defined three extensibility mechanisms: one, the addition of 151 new standard objects through the definitions of new versions 152 of the MIB; two, the addition of widely-available but non- 153 standard objects through the experimental subtree; and three, 154 the addition of private objects through the enterprises 155 subtree. Such additional objects can not only be used for 156 vendor-specific elements, but also for experimentation as 157 required to further the knowledge of which other objects are 158 essential. 160 This memo defines extensions to the MIB using the second 161 method. It contains definitions of managed objects used for 162 experimentation. 164 4. Additions and Changes 166 This MIB includes additions and changes to RFC 1243. These 167 changes are outlined in the following sections. 169 4.1. New Groups 171 The following groups are introduced in this MIB: 173 - DDP Router 174 - RTMP Stub 175 - ZIP Router 176 - ATP 177 - PAP 178 - ASP 179 - ADSP 180 - ATPortPtoP 181 - Per Port Counters 183 4.2. Additional Variables 185 Many variables, mostly counters, were added to groups that 186 existed in RFC 1243. These variables are listed in the 187 following sections. 189 4.2.1. AARP Additions 191 aarpStatus 192 aarpLookups 193 aarpHits 195 4.2.2. ATPort Additions 197 atportNetFrom 198 atportZoneFrom 199 atportInPkts 200 atportOutPkts 201 atportHome 202 atportCurrentZone 203 atportConflictPhysAddr 204 atportZoneTable 206 4.2.3. DDP Addition 208 ddpListenerTable 210 4.2.4. RTMP Additions 212 rtmpInDataPkts 213 rtmpOutDataPkts 214 rtmpInRequestPkts 215 rtmpNextIREqualChanges 216 rtmpNextIRLessChanges 217 rtmpRouteDeletes 218 rtmpRoutingTableOverflows 220 4.2.5. KIP Addition 222 kipFrom 224 4.2.6. ZIP Additions 226 zipNetInfoTable 227 zipInErrors 229 4.2.7. NBP Additions 231 nbpAddress 232 nbpSocket 233 nbpEnumerator 234 nbpInLookUpRequests 235 nbpInLookUpReplies 236 nbpInBroadcastRequests 237 nbpInForwardRequests 238 nbpOutLookUpReplies 239 nbpRegistrationFailures 240 nbpInErrors 242 4.2.8. ATEcho Additions 244 atechoOutRequests 245 atechoInReplies 247 4.3. Deprecations 249 The following variables have been deprecated in this version 250 of the MIB: 252 llapInPkts 253 llapOutPkts 254 llapInNoHandlers 255 llapInErrors 257 These llap variables were duplicated in the interfaces table 258 of MIB-II. 260 4.4. Changes 262 The IMPORTS list has been updated to reflect the current SNMP 263 documents. 265 New textual conventions have been defined. 267 Hyphens have been removed from enumeration strings. 269 Variables used as INDEXes to new tables have ACCESS not- 270 accessible. This is because the values of the INDEX variables 271 are contained in the object identifier for any of the other 272 variables in the table; therefore, it does not need to be 273 explicitly available as data. 275 The atportNetConfig and atportZoneConfig variables have been 276 changed from read-only to read-write. 278 The atportZone variable has be renamed to atportZoneDefault, 279 and its DESCRIPTION clause has been clarified. 281 The atportType, atportStatus, and kipType variables have had 282 more values added to their enumeration lists. 284 The DDP group has been split into two groups; one includes 285 variables that any AppleTalk node would implement and the 286 other includes variables only a router would implement. 288 The rtmpState variable now includes another enumeration, 289 invalid(5), which is used when deleting rows. 291 The variables rtmpRangeStart, rtmpRangeEnd, rtmpNextHop, 292 rtmpType, rtmpPort, and rtmpHops have been changed from read- 293 write to read-only. 295 The ZIP Group has been renamed the ZIP End Node Group. 297 The DESCRIPTION clause for zipZoneIndex has been clarified. 299 The variables zipZoneName, zipZoneNetStart, and zipZoneNetEnd 300 have been changed from read-write to read-only. 302 The nbpIndex variable has been changed from read-only to 303 read-write. 305 The nbpObject, nbpType, and nbpZone variables now suggest that 306 the agent reregister its service when any of these variables 307 is changed. 309 The nbpState variable includes new enumerations. 311 5. Objects 313 Managed objects are accessed via a virtual information store, 314 termed the Management Information Base or MIB. Objects in the 315 MIB are defined using the subset of Abstract Syntax Notation 316 One (ASN.1) [7] defined in the SMI. In particular, each 317 object has a name, a syntax, and an encoding. The name is an 318 object identifier, an administratively assigned name, which 319 specifies an object type. The object type together with an 320 object instance serves to uniquely identify a specific 321 instantiation of the object. For human convenience, we often 322 use a textual string, termed the OBJECT DESCRIPTOR, to also 323 refer to the object type. 325 The syntax of an object type defines the abstract data 326 structure corresponding to that object type. The ASN.1 327 language is used for this purpose. However, the SMI [3] 328 purposely restricts the ASN.1 constructs which may be used. 329 These restrictions are explicitly made for simplicity. 331 The encoding of an object type is simply how that object type 332 is represented using the object type's syntax. Implicitly 333 tied to the notion of an object type's syntax and encoding is 334 how the object type is represented when being transmitted on 335 the network. 337 The SMI specifies the use of the basic encoding rules of ASN.1 338 [8], subject to the additional requirements imposed by the 339 SNMP. 341 5.1. Format of Definitions 343 Section 7 contains the specification of all object types 344 contained in this MIB module. The object types are defined 345 using the conventions defined in the SMI, as amended by the 346 extensions specified in [9]. 348 6. Overview 350 AppleTalk is a protocol suite which features an open peer-to- 351 peer architecture that runs over a variety of transmission 352 media. AppleTalk is defined in [10]. This protocol suite 353 interoperates with the IP protocol suite through various 354 encapsulation methods. As large AppleTalk networks are built 355 that coexist with large IP networks, a method to manage the 356 AppleTalk networks with SNMP becomes necessary. This MIB 357 defines managed objects to be used for managing AppleTalk 358 networks. 360 6.1. Structure of MIB 362 The objects are arranged into the following groups: 364 - LLAP 365 - AARP 366 - ATPort 367 - DDP 368 - DDP Router 369 - RTMP 370 - RTMP Stub 371 - KIP 372 - ZIP Router 373 - ZIP End Node 374 - NBP 375 - ATEcho 376 - ATP 377 - PAP 378 - ASP 379 - ADSP 380 - ATPortPtoP 381 - Per Port Counters 383 These groups are the basic unit of conformance. If the 384 semantics of a group is applicable to an implementation, then 385 it must implement all objects in that group. For example, a 386 managed agent must implement the KIP group if and only if it 387 implements the KIP protocol. 389 These groups are defined to provide a method for managed 390 agents to know which objects they must implement. 392 6.2. The LocalTalk Link Access Protocol Group 394 The LocalTalk Link Access Protocol (LLAP) is a medium-speed 395 data-link protocol designed for low cost and plug-and-play 396 operation. The LLAP group is designed to manage all 397 interfaces on a managed device that use this protocol. 399 6.3. The AppleTalk Address Resolution Protocol Group 401 The AppleTalk Address Resolution Protocol (AARP) is used to 402 map between AppleTalk node addresses, used by the Datagram 403 Delivery Protocol, and the addresses of the underlying data 404 link layer. The AARP table allows for management of the 405 Address Mapping Table on the managed device. 407 6.4. The AppleTalk Port Group 409 An AppleTalk Port is a logical connection to a network over 410 which AppleTalk packets can be transmitted. The "network" 411 could be a tunnel, backbone network, point-to-point link, etc, 412 as well as a native AppleTalk network. This group allows the 413 management of the configuration of these AppleTalk ports. 415 6.5. The Datagram Delivery Protocol Group 417 The Datagram Delivery Protocol (DDP) is the network-layer 418 protocol that is responsible for the socket-to-socket delivery 419 of datagrams over the AppleTalk Internet. This group manages 420 the DDP layer on the managed device. 422 The DDP group contains statistical counters for the DDP 423 protocol, and a table describing the DDP sockets that have 424 protocol handlers registered. 426 6.6. The Datagram Delivery Protocol Router Group 428 Some variables relevant to the Datagram Delivery Protocol 429 (DDP) are only applicable to AppleTalk routers. These 430 variables are included in this group. 432 6.7. The Routing Table Maintenance Protocol Group 434 The Routing Table Maintenance Protocol (RTMP) is used by 435 AppleTalk routers to create and maintain the routing tables 436 that dictate the process of forwarding datagrams on the 437 AppleTalk internet. The RTMP group manages the RTMP protocol 438 as well as the routing tables generated by this protocol. 440 6.8. The Routing Table Maintenance Protocol Stub Group 442 The RTMP Stub process is implemented by end nodes in order to 443 maintain information about the routers on their networks. The 444 variables in this group apply to both routers and end nodes. 445 This group manages the RTMP stub process. 447 6.9. The Kinetics Internet Protocol Group 449 The Kinetics Internet Protocol (KIP) is a protocol for 450 encapsulating and routing AppleTalk datagrams over an IP 451 internet. This name is historical. The KIP group manages the 452 KIP routing protocol as well as the routing tables generated 453 by this protocol. 455 6.10. The Zone Information Protocol Router Group 457 The Zone Information Protocol (ZIP) is used to maintain a 458 mapping between networks and zone names to facilitate the name 459 lookup process performed by the Name Binding Protocol. Some 460 variables relevant to the Zone Information Protocol (ZIP) are 461 only applicable to AppleTalk routers. These variables are 462 included in this group. 464 6.11. The Zone Information Protocol End Node Group 466 The ZIP End Node group manages the variables relevant to the 467 Zone Information Protocol (ZIP) that are applicable to both 468 routers and end nodes. 470 6.12. The Name Binding Protocol Group 472 The Name Binding Protocol (NBP) is a transport-level protocol 473 that is used to convert human readable service names into the 474 numeric AppleTalk network addresses needed for communicating 475 across the AppleTalk network. The NBP group manages this 476 protocol and the NBP services that exist on the managed 477 device. 479 6.13. The AppleTalk Echo Protocol Group 481 The AppleTalk Echo Protocol is a transport-level protocol used 482 to test and verify the status of the AppleTalk internet. The 483 AtEcho group manages this protocol. 485 6.14. The AppleTalk Transaction Protocol Group 487 The AppleTalk Transaction Protocol (ATP) is a transport-level 488 protocol that is defined to support transaction based 489 communications. The ATP group manages this protocol. 491 6.15. The Printer Access Protocol Group 493 The Printer Access Protocol (PAP) is a session-level protocol 494 that enables communications between workstations and print 495 servers. The PAP group manages this protocol. 497 6.16. The AppleTalk Session Protocol Group 499 The AppleTalk Session Protocol (ASP) is a session-level 500 protocol that enables sequences of communications to occur. 501 ASP uses the services of the AppleTalk Transaction Protocol 502 (ATP), but extends these services into the session layer. The 503 ASP group manages this protocol. 505 6.17. The AppleTalk Data Stream Protocol Group 507 The AppleTalk Data Stream Protocol (ADSP) is a session-level 508 protocol that provides symmetric, connection-oriented, full- 509 duplex communication between two sockets on the AppleTalk 510 internet. In addition, ADSP handles flow-control and 511 reliability. The ADSP group manages this protocol. 513 6.18. The AppleTalk Port Point to Point Group 515 The AppleTalk Port Point to Point Group manages ports that 516 have one or more associated point-to-point connections. 518 6.19. The Per Port Counters Group 520 The Per Port Counters Group contains a set of counters which 521 are deemed useful on a per port basis. 523 6.20. Textual Conventions 525 New data types are introduced as textual conventions in this 526 MIB document. These textual conventions enhance the 527 readability of the specification and can ease comparison with 528 other specifications if appropriate. It should be noted that 529 the introduction of these textual conventions has no effect on 530 either the syntax or the semantics of any managed objects. 531 The use of this is merely an artifact of the explanatory 532 method used. Objects defined in terms of this method are 533 always encoded by means of the rules that define the primitive 534 type. Hence, no changes to the SMI or the SNMP are necessary 535 to accommodate these textual conventions which are adopted 536 merely for the convenience of readers and writers in pursuit 537 of the elusive goal of clear, concise, and unambiguous MIB 538 documents. 540 The new data types are: 542 ATNetworkNumber ::= -- 2 octets of network 543 -- number in network 544 -- byte order 545 OCTET STRING (SIZE (2)) 547 DdpNodeAddress ::= -- 2 octets of net number 548 -- in network byte order, 549 -- 1 octet of node number 550 OCTET STRING (SIZE (3)) 552 DdpSocketAddress ::= -- 2 octets of net number 553 -- in network byte order, 554 -- 1 octet of node number, 555 -- 1 octet of socket 556 -- number (0..255) 557 OCTET STRING (SIZE (4)) 559 ATName ::= -- 0 to 32 octets of 560 -- AppleTalk ASCII [10] 561 OCTET STRING (SIZE (0..32)) 563 7. Definitions 565 RFCxxxx-MIB DEFINITIONS ::= BEGIN 567 IMPORTS 568 experimental, Counter, IpAddress, TimeTicks 569 FROM RFC1155-SMI 570 DisplayString 571 FROM RFC1213-MIB 572 OBJECT-TYPE 573 FROM RFC-1212; 575 -- This MIB module uses the extended OBJECT-TYPE macro as 576 -- defined in RFC-1212. 578 -- The following reference is used in this MIB: 579 -- [Inside AppleTalk] 580 -- This refers to Gursharan S. Sidhu, Richard F. Andrews, and 581 -- Alan B. Oppenheimer, Inside AppleTalk, Second Edition, 582 -- Addison Wesley, (1990). 584 -- AppleTalk MIB 586 appletalk OBJECT IDENTIFIER ::= { experimental 17 } 588 ATNetworkNumber ::= -- 2 octets of network number 589 -- in network byte order 590 OCTET STRING (SIZE (2)) 592 DdpNodeAddress ::= -- 2 octets of net number 593 -- in network byte order, 594 -- 1 octet of node number 595 OCTET STRING (SIZE (3)) 597 DdpSocketAddress ::= -- 2 octets of net number 598 -- in network byte order, 599 -- 1 octet of node number, 600 -- 1 octet of socket number 601 -- (0..255) 602 OCTET STRING (SIZE (4)) 604 ATName ::= -- 0 to 32 octets of AppleTalk 605 -- ASCII [Inside AppleTalk] 606 OCTET STRING (SIZE (0..32)) 608 llap OBJECT IDENTIFIER ::= { appletalk 1 } 609 aarp OBJECT IDENTIFIER ::= { appletalk 2 } 610 atport OBJECT IDENTIFIER ::= { appletalk 3 } 611 ddp OBJECT IDENTIFIER ::= { appletalk 4 } 612 rtmp OBJECT IDENTIFIER ::= { appletalk 5 } 613 kip OBJECT IDENTIFIER ::= { appletalk 6 } 614 zipRouter OBJECT IDENTIFIER ::= { appletalk 7 } 615 nbp OBJECT IDENTIFIER ::= { appletalk 8 } 616 atecho OBJECT IDENTIFIER ::= { appletalk 9 } 617 atp OBJECT IDENTIFIER ::= { appletalk 10 } 618 pap OBJECT IDENTIFIER ::= { appletalk 11 } 619 asp OBJECT IDENTIFIER ::= { appletalk 12 } 620 adsp OBJECT IDENTIFIER ::= { appletalk 13 } 621 atportptop OBJECT IDENTIFIER ::= { appletalk 14 } 622 rtmpStub OBJECT IDENTIFIER ::= { appletalk 16 } 623 zipEndNode OBJECT IDENTIFIER ::= { appletalk 17 } 624 perPort OBJECT IDENTIFIER ::= { appletalk 18 } 626 -- The LLAP Group 627 -- 628 -- Implementation of this group is mandatory for all entities that 629 -- implement ALAP 630 -- 631 -- Notes for the interfaces group 632 -- 633 -- When implementing the Interfaces Group of MIB-II, it is suggested 634 -- that the following values be used for any LocalTalk interfaces: 635 -- ifMtu: 600 636 -- ifSpeed: 230000 637 -- ifPhysAddress: the one octet node number for the particular 638 -- interface 639 -- 640 -- Note also that LLAP control packets should not be included in 641 -- the Interfaces Group packet or octet counters. 642 -- 643 -- As an example, an instance of the llapOutPkts object 644 -- might be named llapOutPks.1 646 llapTable OBJECT-TYPE 647 SYNTAX SEQUENCE OF LlapEntry 648 ACCESS not-accessible 649 STATUS mandatory 650 DESCRIPTION 651 "The list of LLAP entries." 652 ::= { llap 1 } 654 llapEntry OBJECT-TYPE 655 SYNTAX LlapEntry 656 ACCESS not-accessible 657 STATUS mandatory 658 DESCRIPTION 659 "An LLAP entry containing objects for the LocalTalk Link 660 Access Protocol for a particular LocalTalk interface." 661 INDEX { llapIfIndex } 662 ::= { llapTable 1 } 664 LlapEntry ::= SEQUENCE { 665 llapIfIndex INTEGER, 666 llapInPkts Counter, 667 llapOutPkts Counter, 668 llapInNoHandlers Counter, 669 llapInLengthErrors Counter, 670 llapInErrors Counter, 671 llapCollisions Counter, 672 llapDefers Counter, 673 llapNoDataErrors Counter, 674 llapRandomCTSErrors Counter, 675 llapFCSErrors Counter 676 } 678 llapIfIndex OBJECT-TYPE 679 SYNTAX INTEGER 680 ACCESS read-only 681 STATUS mandatory 682 DESCRIPTION 683 "The LLAP interface to which this entry pertains. 684 The interface identified by a particular value of 685 this index is the same interface as identified 686 by the same value of ifIndex." 687 ::= { llapEntry 1 } 689 -- this object has been deprecated because it duplicates the 690 -- sum of the MIB-II variables ifInUcastPkts and ifInNUcastPkts 692 llapInPkts OBJECT-TYPE 693 SYNTAX Counter 694 ACCESS read-only 695 STATUS deprecated 696 DESCRIPTION 697 "The total number of good data packets received on this 698 LocalTalk interface." 699 ::= { llapEntry 2 } 701 -- this object has been deprecated because it duplicates the 702 -- sum of the MIB-II variables ifOutUcastPkts and ifOutNUcastPkts 704 llapOutPkts OBJECT-TYPE 705 SYNTAX Counter 706 ACCESS read-only 707 STATUS deprecated 708 DESCRIPTION 709 "The total number of data packets transmitted on this 710 LocalTalk interface." 711 ::= { llapEntry 3 } 713 -- this object has been deprecated because it duplicates the 714 -- MIB-II variable ifInUnknownProtos 715 llapInNoHandlers OBJECT-TYPE 716 SYNTAX Counter 717 ACCESS read-only 718 STATUS deprecated 719 DESCRIPTION 720 "The total number of good packets received on this 721 LocalTalk interface for which there was no protocol 722 handler." 723 ::= { llapEntry 4 } 725 llapInLengthErrors OBJECT-TYPE 726 SYNTAX Counter 727 ACCESS read-only 728 STATUS mandatory 729 DESCRIPTION 730 "The total number of packets received on this LocalTalk 731 interface whose actual length did not match the length 732 in the header." 733 ::= { llapEntry 5 } 735 -- this object has been deprecated because it duplicates the 736 -- MIB-II variable ifInErrors 738 llapInErrors OBJECT-TYPE 739 SYNTAX Counter 740 ACCESS read-only 741 STATUS deprecated 742 DESCRIPTION 743 "The total number of packets containing errors received 744 on this LocalTalk interface." 745 ::= { llapEntry 6 } 747 llapCollisions OBJECT-TYPE 748 SYNTAX Counter 749 ACCESS read-only 750 STATUS mandatory 751 DESCRIPTION 752 "The total number of collisions assumed on this 753 LocalTalk interface due to the lack of a lapCTS reply." 754 ::= { llapEntry 7 } 756 llapDefers OBJECT-TYPE 757 SYNTAX Counter 758 ACCESS read-only 759 STATUS mandatory 760 DESCRIPTION 761 "The total number of times this LocalTalk interface 762 deferred to other packets." 763 ::= { llapEntry 8 } 765 llapNoDataErrors OBJECT-TYPE 766 SYNTAX Counter 767 ACCESS read-only 768 STATUS mandatory 769 DESCRIPTION 770 "The total number of times this LocalTalk interface 771 received a lapRTS packet and expected a data packet, 772 but did not receive any data packet." 773 ::= { llapEntry 9 } 775 llapRandomCTSErrors OBJECT-TYPE 776 SYNTAX Counter 777 ACCESS read-only 778 STATUS mandatory 779 DESCRIPTION 780 "The total number of times this LocalTalk interface 781 received a lapCTS packet that was not solicited by a 782 lapRTS packet." 783 ::= { llapEntry 10 } 785 llapFCSErrors OBJECT-TYPE 786 SYNTAX Counter 787 ACCESS read-only 788 STATUS mandatory 789 DESCRIPTION 790 "The total number of times this LocalTalk interface 791 received a packet with an FCS (Frame Check Sequence) 792 error." 793 ::= { llapEntry 11 } 795 -- The AARP Group 796 -- 797 -- Implementation of this group is mandatory for all entities that 798 -- implement AARP 799 -- 800 -- As an example, an instance of the aarpPhysAddress object 801 -- might be named aarpPhysAddress.1.0.80.234 803 aarpTable OBJECT-TYPE 804 SYNTAX SEQUENCE OF AarpEntry 805 ACCESS not-accessible 806 STATUS mandatory 807 DESCRIPTION 808 "The AppleTalk Address Translation Table contains an 809 equivalence of AppleTalk Network Addresses to the link 810 layer physical address." 811 ::= { aarp 1 } 813 aarpEntry OBJECT-TYPE 814 SYNTAX AarpEntry 815 ACCESS not-accessible 816 STATUS mandatory 817 DESCRIPTION 818 "Each entry contains one AppleTalk Network Address to 819 physical address equivalence." 820 INDEX { aarpIfIndex, aarpNetAddress } 821 ::= { aarpTable 1 } 823 AarpEntry ::= SEQUENCE { 824 aarpIfIndex INTEGER, 825 aarpPhysAddress OCTET STRING, 826 aarpNetAddress DdpNodeAddress, 827 aarpStatus INTEGER 828 } 830 aarpIfIndex OBJECT-TYPE 831 SYNTAX INTEGER 832 ACCESS read-only 833 STATUS mandatory 834 DESCRIPTION 835 "The interface on which this entry's equivalence is 836 effective. The interface identified by a particular 837 value of this index is the same interface as identified 838 by the same value of ifIndex." 839 ::= { aarpEntry 1 } 841 aarpPhysAddress OBJECT-TYPE 842 SYNTAX OCTET STRING 843 ACCESS read-write 844 STATUS mandatory 845 DESCRIPTION 846 "The media-dependent physical address." 847 ::= { aarpEntry 2 } 849 aarpNetAddress OBJECT-TYPE 850 SYNTAX DdpNodeAddress 851 ACCESS read-only 852 STATUS mandatory 853 DESCRIPTION 854 "The AppleTalk Network Address corresponding to the 855 media-dependent physical address." 856 ::= { aarpEntry 3 } 858 aarpStatus OBJECT-TYPE 859 SYNTAX INTEGER { 860 valid(1), 861 invalid(2) 862 } 863 ACCESS read-write 864 STATUS mandatory 865 DESCRIPTION 866 "The status of this AARP entry. 868 Setting this object to the value invalid(2) has the 869 effect of invalidating the corresponding entry in the 870 aarpTable. That is, it effectively disassociates the 871 mapping identified with said entry. It is an 872 implementation-specific matter as to whether the agent 873 removes an invalidated entry from the table. 874 Accordingly, management stations must be prepared to 875 receive from agents tabular information corresponding 876 to entries not currently in use. Proper 877 interpretation of such entries requires examination 878 of the relevant aarpStatus object." 879 ::= { aarpEntry 4 } 881 aarpLookups OBJECT-TYPE 882 SYNTAX Counter 883 ACCESS read-only 884 STATUS mandatory 885 DESCRIPTION 886 "The number of times the AARP cache for this entity was 887 searched." 888 ::= { aarp 2 } 890 aarpHits OBJECT-TYPE 891 SYNTAX Counter 892 ACCESS read-only 893 STATUS mandatory 894 DESCRIPTION 895 "The number of times an entry was searched for and found 896 in the AARP cache for this entity." 897 ::= { aarp 3 } 899 -- The ATPort Group 900 -- 901 -- Implementation of this group is mandatory for all entities that 902 -- implement AppleTalk ports 903 -- 904 -- Note that to be compliant with this group, all variables 905 -- that have read-write access must be implemented as 906 -- read-write. 907 -- 908 -- As an example, an instance of the atportNetFrom object 909 -- might be named atportNetFrom.2 911 atportTable OBJECT-TYPE 912 SYNTAX SEQUENCE OF AtportEntry 913 ACCESS not-accessible 914 STATUS mandatory 915 DESCRIPTION 916 "A list of AppleTalk ports for this entity." 917 ::= { atport 1 } 919 atportEntry OBJECT-TYPE 920 SYNTAX AtportEntry 921 ACCESS not-accessible 922 STATUS mandatory 923 DESCRIPTION 924 "The description of one of the AppleTalk 925 ports on this entity." 926 INDEX { atportIndex } 927 ::= { atportTable 1 } 929 AtportEntry ::= SEQUENCE { 930 atportIndex INTEGER, 931 atportDescr DisplayString, 932 atportType INTEGER, 933 atportNetStart ATNetworkNumber, 934 atportNetEnd ATNetworkNumber, 935 atportNetAddress DdpNodeAddress, 936 atportStatus INTEGER, 937 atportNetConfig INTEGER, 938 atportZoneConfig INTEGER, 939 atportZoneDefault ATName, 940 atportIfIndex INTEGER, 941 atportNetFrom DdpNodeAddress, 942 atportZoneFrom DdpNodeAddress, 943 atportInPkts Counter, 944 atportOutPkts Counter, 945 atportHome INTEGER, 946 atportCurrentZone ATName, 947 atportConflictPhysAddr OCTET STRING 948 } 950 atportIndex OBJECT-TYPE 951 SYNTAX INTEGER 952 ACCESS read-only 953 STATUS mandatory 954 DESCRIPTION 955 "A unique value for each AppleTalk port. 956 Its value is between 1 and the total number of 957 AppleTalk ports. The value for each port must 958 remain constant at least from the re-initialization of 959 the entity's network management system to the next 960 re-initialization." 961 ::= { atportEntry 1 } 963 atportDescr OBJECT-TYPE 964 SYNTAX DisplayString 965 ACCESS read-write 966 STATUS mandatory 967 DESCRIPTION 968 "A text string containing information about the 969 port. This string is intended for presentation 970 to a human; it must not contain anything but printable 971 ASCII characters." 972 ::= { atportEntry 2 } 974 -- Several objects throughout the MIB key off of atportType to 975 -- determine the format of OCTET STRING addresses of peers. The 976 -- address formats are as follows: 977 -- localtalk, ethertalk1, ethertalk2, tokentalk, iptalk, 978 -- fdditalk, smdstalk, arctalk, and virtual take the format of 979 -- DdpNodeAddress 980 -- serialPPP: null OCTET STRING 981 -- serialNonstandard: vendor specific 982 -- aurp: see AURP MIB to determine format 983 -- frameRelay: 32 bit DLCI in network byte order 984 -- (OCTET STRING (SIZE (4))) 985 -- x25: X121Address (see RFC 1382) 986 -- ip: IP address (OCTET STRING (SIZE (4))) 987 -- osi: NSAP (OCTET STRING (SIZE (3..20))) 988 -- decnetIV: 6 bit area, 10 bit host in network byte order 989 -- (OCTET STRING (SIZE (2))) 990 -- arap: ??? 991 -- nonAppleTalk3Com: based on ifType 992 -- ipx: 32 bit network number in network byte order followed 993 -- by datalink address of host 994 -- arns: 32 bit ARNS header 995 -- hdlc: DdpNodeAddress or null OCTET STRING 997 atportType OBJECT-TYPE 998 SYNTAX INTEGER { 999 other(1), -- none of the following 1000 localtalk(2), 1001 ethertalk1(3), 1002 ethertalk2(4), 1003 tokentalk(5), 1004 iptalk(6), 1005 serialPPP(7), 1006 serialNonstandard(8), 1007 virtual(9), -- an internal interface 1008 fdditalk(10), 1009 arctalk(11), 1010 smdstalk(12), 1011 aurp(13), 1012 frameRelay(14), 1013 x25(15), 1014 ip(16), 1015 osi(17), 1016 decnetIV(18), 1017 arap(19), 1018 isdnInThePacketMode(20), 1019 nonAppleTalk3Com(21), 1020 ipx(22), 1021 arns(23), 1022 hdlc(24) 1023 } 1024 ACCESS read-write 1025 STATUS mandatory 1026 DESCRIPTION 1027 "The type of port, distinguished by the protocol 1028 immediately below DDP in the protocol stack." 1029 ::= { atportEntry 3 } 1031 atportNetStart OBJECT-TYPE 1032 SYNTAX ATNetworkNumber 1033 ACCESS read-write 1034 STATUS mandatory 1035 DESCRIPTION 1036 "The first AppleTalk network address in the range 1037 configured for this port. If this port is not a native 1038 AppleTalk port, this object shall have the value of 1039 two octets of zero." 1040 ::= { atportEntry 4 } 1042 atportNetEnd OBJECT-TYPE 1043 SYNTAX ATNetworkNumber 1044 ACCESS read-write 1045 STATUS mandatory 1046 DESCRIPTION 1047 "The last AppleTalk network address in the range 1048 configured for this port. If the network to which this 1049 AppleTalk port is connected is a non-extended network, 1050 or if it is not a native AppleTalk port, the value 1051 for atportNetEnd shall be two octets of zero." 1052 ::= { atportEntry 5 } 1054 atportNetAddress OBJECT-TYPE 1055 SYNTAX DdpNodeAddress 1056 ACCESS read-write 1057 STATUS mandatory 1058 DESCRIPTION 1059 "The AppleTalk network address configured for this 1060 port. In addition, this value may be used as a hint for an 1061 initial node number used during node-finding. If this port 1062 is not a native AppleTalk port, this object shall have the 1063 value of three octets of zero." 1064 ::= { atportEntry 6 } 1066 atportStatus OBJECT-TYPE 1067 SYNTAX INTEGER { 1068 routing(1), -- this port is fully configured and routing 1069 unconfigured(2), 1070 off(3), 1071 invalid(4), 1072 endNode(5), -- this port is acting as an end node 1073 offDueToConflict(6), -- port is off due to 1074 -- configuration conflict 1075 other(7) -- none of the states defined above 1076 } 1077 ACCESS read-write 1078 STATUS mandatory 1079 DESCRIPTION 1080 "The configuration status of this port. 1082 Setting this object to the value invalid(4) has the 1083 effect of invalidating the corresponding entry in the 1084 atportTable. That is, it effectively disassociates the 1085 mapping identified with said entry. It is an 1086 implementation-specific matter as to whether the agent 1087 removes an invalidated entry from the table. 1088 Accordingly, management stations must be prepared to 1089 receive from agents tabular information corresponding 1090 to entries not currently in use. Proper 1091 interpretation of such entries requires examination 1092 of the relevant atportStatus object." 1093 ::= { atportEntry 7 } 1095 atportNetConfig OBJECT-TYPE 1096 SYNTAX INTEGER { 1097 conflictOrientedSeed(1), -- use configured network range 1098 -- even if it conflicts with another AppleTalk device 1099 garnered(2), -- acquire from another AppleTalk device 1100 guessed(3), -- generate a "random" network range 1101 unconfigured(4), -- no other value applies 1102 conflictAverseSeed(5), -- use configured network range, 1103 -- but don't come up if it conflicts 1104 softSeed(6) -- attempt to use configured network range, 1105 -- but use network range from another router if our 1106 -- configuration conflicts 1107 } 1108 ACCESS read-write 1109 STATUS mandatory 1110 DESCRIPTION 1111 "The status of the network information for this port. If 1112 this port is not a native AppleTalk port, this object shall 1113 have the value unconfigured(4)." 1114 ::= { atportEntry 8 } 1116 atportZoneConfig OBJECT-TYPE 1117 SYNTAX INTEGER { 1118 conflictOrientedSeed(1), -- use configured zone information 1119 -- even if it conflicts with another AppleTalk device 1120 garnered(2), -- acquire from another AppleTalk device 1121 guessed(3), -- generate "random" zone information 1122 unconfigured(4), -- no other value applies 1123 conflictAverseSeed(5), -- use configured zone information, 1124 -- but don't come up if it conflicts 1125 softSeed(6) -- attempt to use configured zone information, 1126 -- but use zone information from another router if our 1127 -- configuration conflicts 1128 } 1129 ACCESS read-write 1130 STATUS mandatory 1131 DESCRIPTION 1132 "The status of the zone information for this port. If 1133 this port is not a native AppleTalk port, this object shall 1134 have the value unconfigured(4)." 1135 ::= { atportEntry 9 } 1137 atportZoneDefault OBJECT-TYPE 1138 SYNTAX ATName 1139 ACCESS read-write 1140 STATUS mandatory 1141 DESCRIPTION 1142 "The name of the default zone for this port. If this 1143 port only has one zone, that zone is represented here. 1144 If this port is not a native AppleTalk port, this object 1145 shall contain an octet string of zero length. 1147 When this value is changed in a router, the router must 1148 send a zipNotify packet on the associated network." 1149 ::= { atportEntry 10 } 1151 atportIfIndex OBJECT-TYPE 1152 SYNTAX INTEGER 1153 ACCESS read-write 1154 STATUS mandatory 1155 DESCRIPTION 1156 "The physical interface associated with this AppleTalk 1157 port. The interface identified by a particular 1158 value of this index is the same interface as identified 1159 by the same value of ifIndex." 1160 ::= { atportEntry 11 } 1162 atportNetFrom OBJECT-TYPE 1163 SYNTAX DdpNodeAddress 1164 ACCESS read-only 1165 STATUS mandatory 1166 DESCRIPTION 1167 "When atportNetConfig is set to garnered(2), this 1168 variable contains the DDP address of an entity from 1169 which the AppleTalk network number was garnered. 1171 When atportNetConfig is set to conflictOrientedSeed(1), 1172 conflictAverseSeed(5), or softSeed(6), this 1173 variable contains the DDP address of an entity which 1174 confirmed or supplied our AppleTalk network number, 1175 for example by replying to a ZIP GetNetInfo request. 1177 If atportNetConfig is set to guessed(3) or unconfigured(4), 1178 or if the entity has not received any network number 1179 confirmation, this variable should be set to three octets 1180 of zero." 1181 ::= { atportEntry 12 } 1183 atportZoneFrom OBJECT-TYPE 1184 SYNTAX DdpNodeAddress 1185 ACCESS read-only 1186 STATUS mandatory 1187 DESCRIPTION 1188 "When atportZoneConfig is set to garnered(2), this 1189 variable contains the DDP address of an entity from 1190 which the AppleTalk zone list was garnered. 1192 When atportZoneConfig is set to conflictOrientedSeed(1), 1193 conflictAverseSeed(5), or softSeed(6), this 1194 variable contains the DDP address of an entity which 1195 confirmed or supplied our AppleTalk zone information, 1196 for example by replying to a ZIP GetNetInfo request or 1197 a ZIP Query. 1199 If atportZoneConfig is set to guessed(3) or unconfigured(4), 1200 or if the entity has not received any zone confirmation, 1201 this variable should be set to three octets of zero." 1202 ::= { atportEntry 13 } 1204 atportInPkts OBJECT-TYPE 1205 SYNTAX Counter 1206 ACCESS read-only 1207 STATUS mandatory 1208 DESCRIPTION 1209 "The number of packets received by this entity on 1210 this port." 1211 ::= { atportEntry 14 } 1213 atportOutPkts OBJECT-TYPE 1214 SYNTAX Counter 1215 ACCESS read-only 1216 STATUS mandatory 1217 DESCRIPTION 1218 "The number of packets transmitted by this entity on 1219 this port." 1220 ::= { atportEntry 15 } 1222 atportHome OBJECT-TYPE 1223 SYNTAX INTEGER { 1224 home(1), 1225 notHome(2) 1226 } 1227 ACCESS read-only 1228 STATUS mandatory 1229 DESCRIPTION 1230 "An indication of whether or not the entity is 1231 homed on this port, that is to say, a port on which the 1232 entity could perform NBP registrations for services 1233 that it chooses to advertise." 1234 ::= { atportEntry 16 } 1236 -- note that modifications to the following variable do 1237 -- not affect the nbpTable 1239 atportCurrentZone OBJECT-TYPE 1240 SYNTAX ATName 1241 ACCESS read-write 1242 STATUS mandatory 1243 DESCRIPTION 1244 "The current zone for the port. In general, this is 1245 the zone name in which services on this port will 1246 be registered. If this port is not a native AppleTalk 1247 port, this object shall contain an octet string of 1248 zero length." 1249 ::= { atportEntry 17 } 1251 atportConflictPhysAddr OBJECT-TYPE 1252 SYNTAX OCTET STRING 1253 ACCESS read-only 1254 STATUS mandatory 1255 DESCRIPTION 1256 "The link-layer address of a device which caused this 1257 entity to set atportStatus to offDueToConflict(6). 1258 If this address is not available, or if the entity has 1259 not set atportStatus to offDueToConflict, this 1260 object shall be a zero length OCTET STRING." 1261 ::= { atportEntry 18 } 1263 -- The atportZoneTable stores information about the zones 1264 -- associated with each port. The default zone for each 1265 -- port is stored in the port's atportZoneDefault variable; 1266 -- all other zones for the port are listed in this table. 1267 -- If a port only has one zone, it should be stored in the 1268 -- port's atportZoneDefault variable, and this table should 1269 -- be empty. 1270 -- 1271 -- One of the indexes for this table is atportZoneName. Even 1272 -- though AppleTalk zone name matches are case-insensitive, this 1273 -- table will store zone names regardless of case. SNMP Get, 1274 -- GetNext and Set operations are performed on these 1275 -- (potentially) mixed case strings according to the normal 1276 -- SNMP rules with the following caveat: in processing a SET 1277 -- request, the agent shall perform a case-insensitive search 1278 -- and a case-sensitive search. If the case-insensitive 1279 -- search matches and the case-sensitive search does not match, 1280 -- the "equivalent" zone name exists in another entry with a 1281 -- different capitalization and the SET request shall fail due 1282 -- to the name being inconsistent (SNMPv1 should return a genErr.) 1283 -- This insures that only one version of a zone name 1284 -- will appear in each agent, at the expense of forcing a 1285 -- management station to query using that exact name. 1286 -- 1287 -- As an example, an instance of the atportZoneStatus object 1288 -- might be named 1289 -- atportZoneStatus.2.12.75.97.114.101.110.39.115.20.90.111.110.101 1291 atportZoneTable OBJECT-TYPE 1292 SYNTAX SEQUENCE OF AtportZoneEntry 1293 ACCESS not-accessible 1294 STATUS mandatory 1295 DESCRIPTION 1296 "The table of zone information for non-default 1297 zones on ports." 1298 ::= { atport 2 } 1300 atportZoneEntry OBJECT-TYPE 1301 SYNTAX AtportZoneEntry 1302 ACCESS not-accessible 1303 STATUS mandatory 1304 DESCRIPTION 1305 "An entry of zone information for a port." 1306 INDEX { atportZonePort, atportZoneName } 1307 ::= { atportZoneTable 1 } 1309 AtportZoneEntry ::= SEQUENCE { 1310 atportZonePort INTEGER, 1311 atportZoneName ATName (SIZE (1..32)), 1312 atportZoneStatus INTEGER 1313 } 1315 atportZonePort OBJECT-TYPE 1316 SYNTAX INTEGER 1317 ACCESS not-accessible 1318 STATUS mandatory 1319 DESCRIPTION 1320 "An integer representing the port to which this zone belongs. 1321 The port identified by a particular value of this object 1322 is the same port as identified by the same value of 1323 atportIndex." 1324 ::= { atportZoneEntry 1 } 1326 atportZoneName OBJECT-TYPE 1327 SYNTAX ATName (SIZE (1..32)) 1328 ACCESS not-accessible 1329 STATUS mandatory 1330 DESCRIPTION 1331 "A zone name configured for the AppleTalk port referred to in 1332 the corresponding entry of atportZonePort. 1334 When this value is changed in a router, the router must 1335 send a zipNotify packet on the associated network." 1336 ::= { atportZoneEntry 2 } 1338 atportZoneStatus OBJECT-TYPE 1339 SYNTAX INTEGER { 1340 valid(1), 1341 invalid(2) 1342 } 1343 ACCESS read-write 1344 STATUS mandatory 1345 DESCRIPTION 1346 "The status of this zone entry. 1348 Setting this object to the value invalid(2) has the 1349 effect of invalidating the corresponding entry in the 1350 atportZoneTable. That is, it effectively disassociates 1351 the mapping identified with said entry. It is an 1352 implementation-specific matter as to whether the agent 1353 removes an invalidated entry from the table. 1354 Accordingly, management stations must be prepared to 1355 receive from agents tabular information corresponding 1356 to entries not currently in use. Proper 1357 interpretation of such entries requires examination 1358 of the relevant atportZoneStatus object." 1359 ::= { atportZoneEntry 3 } 1361 -- The DDP Group 1362 -- 1363 -- Implementation of this group is mandatory for all entities that 1364 -- implement DDP 1365 -- 1366 -- This group consists of DDP variables that would be implemented 1367 -- by either a router or an end node. The following variables 1368 -- are included: 1369 -- ddpOutRequests 1370 -- ddpOutShorts 1371 -- ddpOutLongs 1372 -- ddpInReceives 1373 -- ddpInLocalDatagrams 1374 -- ddpNoProtocolHandlers 1375 -- ddpTooShortErrors 1376 -- ddpTooLongErrors 1377 -- ddpShortDDPErrors 1378 -- ddpChecksumErrors 1379 -- ddpListenerTable 1380 -- 1381 -- Note that the variables in this group are not numbered 1382 -- sequentially. This was done so that it was not necessary 1383 -- to deprecate variables from RFC 1243. 1385 ddpOutRequests OBJECT-TYPE 1386 SYNTAX Counter 1387 ACCESS read-only 1388 STATUS mandatory 1389 DESCRIPTION 1390 "The total number of DDP datagrams which were supplied 1391 to DDP by local DDP clients in requests for 1392 transmission. Note that this counter does not 1393 include any datagrams counted in ddpForwRequests." 1394 ::= { ddp 1 } 1396 ddpOutShorts OBJECT-TYPE 1397 SYNTAX Counter 1398 ACCESS read-only 1399 STATUS mandatory 1400 DESCRIPTION 1401 "The total number of short DDP datagrams which were 1402 transmitted from this entity." 1403 ::= { ddp 2 } 1405 ddpOutLongs OBJECT-TYPE 1406 SYNTAX Counter 1407 ACCESS read-only 1408 STATUS mandatory 1409 DESCRIPTION 1410 "The total number of long DDP datagrams which were 1411 transmitted from this entity." 1412 ::= { ddp 3 } 1414 ddpInReceives OBJECT-TYPE 1415 SYNTAX Counter 1416 ACCESS read-only 1417 STATUS mandatory 1418 DESCRIPTION 1419 "The total number of input datagrams received by DDP, 1420 including those received in error." 1421 ::= { ddp 4 } 1423 ddpInLocalDatagrams OBJECT-TYPE 1424 SYNTAX Counter 1425 ACCESS read-only 1426 STATUS mandatory 1427 DESCRIPTION 1428 "The total number of input DDP datagrams for which this 1429 entity was their final DDP destination." 1430 ::= { ddp 6 } 1432 ddpNoProtocolHandlers OBJECT-TYPE 1433 SYNTAX Counter 1434 ACCESS read-only 1435 STATUS mandatory 1436 DESCRIPTION 1437 "The total number of DDP datagrams addressed to this 1438 entity that were addressed to an upper layer protocol 1439 for which no protocol handler existed." 1440 ::= { ddp 7 } 1442 ddpTooShortErrors OBJECT-TYPE 1443 SYNTAX Counter 1444 ACCESS read-only 1445 STATUS mandatory 1446 DESCRIPTION 1447 "The total number of input DDP datagrams dropped because 1448 the received data length was less than the data length 1449 specified in the DDP header or the received data length 1450 was less than the length of the expected DDP header." 1452 ::= { ddp 9 } 1454 ddpTooLongErrors OBJECT-TYPE 1455 SYNTAX Counter 1456 ACCESS read-only 1457 STATUS mandatory 1458 DESCRIPTION 1459 "The total number of input DDP datagrams dropped because 1460 they exceeded the maximum DDP datagram size." 1461 ::= { ddp 10 } 1463 ddpShortDDPErrors OBJECT-TYPE 1464 SYNTAX Counter 1465 ACCESS read-only 1466 STATUS mandatory 1467 DESCRIPTION 1468 "The total number of input DDP datagrams dropped because 1469 this entity was not their final destination and their 1470 type was short DDP." 1471 ::= { ddp 12 } 1473 ddpChecksumErrors OBJECT-TYPE 1474 SYNTAX Counter 1475 ACCESS read-only 1476 STATUS mandatory 1477 DESCRIPTION 1478 "The total number of input DDP datagrams for which this 1479 DDP entity was their final destination, and which were 1480 dropped because of a checksum error." 1481 ::= { ddp 14 } 1483 -- As an example, an instance of the ddpListenerStatus object 1484 -- might be named ddpListenerStatus.0.80.220.1 1486 ddpListenerTable OBJECT-TYPE 1487 SYNTAX SEQUENCE OF DdpListenerEntry 1488 ACCESS not-accessible 1489 STATUS mandatory 1490 DESCRIPTION 1491 "The ddpListenerTable stores information for each DDP 1492 socket that has a listener." 1493 ::= { ddp 15 } 1495 ddpListenerEntry OBJECT-TYPE 1496 SYNTAX DdpListenerEntry 1497 ACCESS not-accessible 1498 STATUS mandatory 1499 DESCRIPTION 1500 "This ddpListenerEntry contains information about a 1501 particular socket that has a socket listener." 1502 INDEX { ddpListenerAddress } 1503 ::= { ddpListenerTable 1 } 1505 DdpListenerEntry ::= SEQUENCE { 1506 ddpListenerAddress DdpSocketAddress, 1507 ddpListenerInPkts Counter, 1508 ddpListenerStatus INTEGER 1509 } 1511 ddpListenerAddress OBJECT-TYPE 1512 SYNTAX DdpSocketAddress 1513 ACCESS not-accessible 1514 STATUS mandatory 1515 DESCRIPTION 1516 "The DDP address that this socket listener is bound to. 1517 If this socket listener isn't bound to a particular 1518 address, for instance if it is intended for all 1519 interfaces, this object shall have the value of three 1520 octets of zero followed by one octet of socket number. 1521 The socket number must not equal zero." 1522 ::= { ddpListenerEntry 1 } 1524 ddpListenerInPkts OBJECT-TYPE 1525 SYNTAX Counter 1526 ACCESS read-only 1527 STATUS mandatory 1528 DESCRIPTION 1529 "The number of packets received for this listener." 1530 ::= { ddpListenerEntry 2 } 1532 ddpListenerStatus OBJECT-TYPE 1533 SYNTAX INTEGER { 1534 valid(1), 1535 invalid(2) 1536 } 1537 ACCESS read-write 1538 STATUS mandatory 1539 DESCRIPTION 1540 "The status of this socket listener. 1542 Setting this object to the value invalid(2) has the 1543 effect of invalidating the corresponding entry in the 1544 ddpSocketTable. That is, it effectively disassociates 1545 the mapping identified with said entry. It is an 1546 implementation-specific matter as to whether the agent 1547 removes an invalidated entry from the table. 1548 Accordingly, management stations must be prepared to 1549 receive from agents tabular information corresponding 1550 to entries not currently in use. Proper 1551 interpretation of such entries requires examination 1552 of the relevant ddpSocketStatus object." 1553 ::= { ddpListenerEntry 3 } 1555 -- The DDP Router Group 1556 -- 1557 -- Implementation of this group is required for all routers which 1558 -- implement DDP 1559 -- 1560 -- This group consists of DDP variables that only a router would 1561 -- implement. The following variables are included: 1562 -- ddpForwRequests 1563 -- ddpOutNoRoutes 1564 -- ddpBroadcastErrors 1565 -- ddpHopCountErrors 1566 -- ddpForwardingTable 1567 -- 1568 -- Note that the variables in this group are not numbered 1569 -- sequentially. This was done so that variables from RFC 1243 1570 -- did not need to be deprecated. 1572 ddpForwRequests OBJECT-TYPE 1573 SYNTAX Counter 1574 ACCESS read-only 1575 STATUS mandatory 1576 DESCRIPTION 1577 "The number of input datagrams for which this entity was 1578 not their final DDP destination, as a result of which an 1579 attempt was made to find a route to forward them to that 1580 final destination." 1581 ::= { ddp 5 } 1583 ddpOutNoRoutes OBJECT-TYPE 1584 SYNTAX Counter 1585 ACCESS read-only 1586 STATUS mandatory 1587 DESCRIPTION 1588 "The total number of DDP datagrams dropped because a 1589 route could not be found to their final destination." 1590 ::= { ddp 8 } 1592 ddpBroadcastErrors OBJECT-TYPE 1593 SYNTAX Counter 1594 ACCESS read-only 1595 STATUS mandatory 1596 DESCRIPTION 1597 "The total number of input DDP datagrams dropped because 1598 this entity was not their final destination and they 1599 were addressed to the link level broadcast." 1601 ::= { ddp 11 } 1603 ddpHopCountErrors OBJECT-TYPE 1604 SYNTAX Counter 1605 ACCESS read-only 1606 STATUS mandatory 1607 DESCRIPTION 1608 "The total number of input DDP datagrams dropped because 1609 this entity was not their final destination and their 1610 hop count would exceed 15." 1611 ::= { ddp 13 } 1613 -- The ddpForwardingTable is a read-only table which shows the 1614 -- next hop that a datagram will take when being routed to a 1615 -- specific network. If a manager wishes to change data in this 1616 -- table via SNMP, he must change it in the MIB for the routing 1617 -- protocol itself (by incrementing hop counts, etc), rather than 1618 -- in this table. This table is derived by the managed entity 1619 -- from the information it receives from the routing protocols 1620 -- that it supports. 1621 -- 1622 -- This table also shows the routing table from which the next 1623 -- hop was derived. When a MIB is written for an AppleTalk 1624 -- routing protocol, it should include the definition of an 1625 -- object identifier which will be used in the ddpForwardingProto 1626 -- variable defined here. (For example, a value for RTMP is 1627 -- defined as { ddp-forw-proto-oids 1 } below.) 1628 -- 1629 -- To look for a specific net N in this table, it is suggested 1630 -- that the management station perform a get-next query for 1631 -- ddpForwardingNetEnd.(N-1). This will retrieve the correct 1632 -- row if it exists in the table. 1633 -- 1634 -- As an example, an instance of the ddpForwardingPort object 1635 -- might be named ddpForwardingPort.0.90 1637 ddpForwardingTable OBJECT-TYPE 1638 SYNTAX SEQUENCE OF DdpForwardingEntry 1639 ACCESS not-accessible 1640 STATUS mandatory 1641 DESCRIPTION 1642 "A table of forwarding entries for DDP. This table 1643 contains a route for each AppleTalk network currently 1644 known to the entity." 1645 ::= { ddp 16 } 1647 ddpForwardingEntry OBJECT-TYPE 1648 SYNTAX DdpForwardingEntry 1649 ACCESS not-accessible 1650 STATUS mandatory 1651 DESCRIPTION 1652 "A forwarding entry for a particular AppleTalk network." 1653 INDEX { ddpForwardingNetEnd } 1654 ::= { ddpForwardingTable 1 } 1656 DdpForwardingEntry ::= SEQUENCE { 1657 ddpForwardingNetEnd ATNetworkNumber, 1658 ddpForwardingNetStart ATNetworkNumber, 1659 ddpForwardingNextHop OCTET STRING, 1660 ddpForwardingProto OBJECT IDENTIFIER, 1661 ddpForwardingModifiedTime TimeTicks, 1662 ddpForwardingUseCounts Counter, 1663 ddpForwardingPort INTEGER 1664 } 1666 ddpForwardingNetEnd OBJECT-TYPE 1667 SYNTAX ATNetworkNumber 1668 ACCESS not-accessible 1669 STATUS mandatory 1670 DESCRIPTION 1671 "The last network number in the network range 1672 matched by this forwarding entry. This will not be 1673 zero even if this corresponds to a non-extended net." 1674 ::= { ddpForwardingEntry 1 } 1676 ddpForwardingNetStart OBJECT-TYPE 1677 SYNTAX ATNetworkNumber 1678 ACCESS read-only 1679 STATUS mandatory 1680 DESCRIPTION 1681 "The first network number in the network range 1682 matched by this forwarding entry." 1683 ::= { ddpForwardingEntry 2 } 1685 ddpForwardingNextHop OBJECT-TYPE 1686 SYNTAX OCTET STRING 1687 ACCESS read-only 1688 STATUS mandatory 1689 DESCRIPTION 1690 "The next hop in the route to this entry's destination 1691 network. The format of this address can be determined 1692 by examinating the atportType corresponding to this 1693 entry." 1694 ::= { ddpForwardingEntry 3 } 1696 ddpForwardingProto OBJECT-TYPE 1697 SYNTAX OBJECT IDENTIFIER 1698 ACCESS read-only 1699 STATUS mandatory 1700 DESCRIPTION 1701 "The routing mechanism by which this route was learned." 1702 ::= { ddpForwardingEntry 4 } 1704 ddpForwardingModifiedTime OBJECT-TYPE 1705 SYNTAX TimeTicks 1706 ACCESS read-only 1707 STATUS mandatory 1708 DESCRIPTION 1709 "The value of sysUpTime at the time of the last 1710 modification to this entry. The initial value of 1711 ddpForwardingModified time shall be the value of 1712 sysUpTime at the time the entry is created." 1713 ::= { ddpForwardingEntry 5 } 1715 ddpForwardingUseCounts OBJECT-TYPE 1716 SYNTAX Counter 1717 ACCESS read-only 1718 STATUS mandatory 1719 DESCRIPTION 1720 "The number of times this entry has been used to 1721 route a packet to the destination network. Note that 1722 this counter is not cleared when the corresponding 1723 ddpForwardingNextHop variable changes." 1724 ::= { ddpForwardingEntry 6 } 1726 ddpForwardingPort OBJECT-TYPE 1727 SYNTAX INTEGER 1728 ACCESS read-only 1729 STATUS mandatory 1730 DESCRIPTION 1731 "The AppleTalk port through which ddpForwardingNextHop 1732 is reached. The interface identified by a particular 1733 value of this variable is the same interface as identified 1734 by the same value of atportIndex." 1735 ::= { ddpForwardingEntry 7 } 1737 ddpForwProtoOids OBJECT IDENTIFIER ::= { ddp 17 } 1739 -- The value to be assigned to ddpForwardingProto when the routing 1740 -- protocol is RTMP. 1741 rtmpRoutingProto OBJECT IDENTIFIER ::= { ddpForwProtoOids 1 } 1743 -- The value to be assigned to ddpForwardingProto when the routing 1744 -- protocol is KIP. 1745 kipRoutingProto OBJECT IDENTIFIER ::= { ddpForwProtoOids 2 } 1747 ddpForwardingTableOverflows OBJECT-TYPE 1748 SYNTAX Counter 1749 ACCESS read-only 1750 STATUS mandatory 1751 DESCRIPTION 1752 "The number of times the entity attempted to add an 1753 entry to the forwarding table but failed due to 1754 overflow." 1755 ::= { ddp 18 } 1757 -- The RTMP Group 1758 -- 1759 -- Implementation of this group is required for all routers which 1760 -- implement RTMP 1761 -- 1762 -- As an example, an instance of the rtmpPort object 1763 -- might be named rtmpPort.0.80 1765 rtmpTable OBJECT-TYPE 1766 SYNTAX SEQUENCE OF RtmpEntry 1767 ACCESS not-accessible 1768 STATUS mandatory 1769 DESCRIPTION 1770 "A list of Routing Table Maintenance Protocol entries for 1771 this entity." 1772 ::= { rtmp 1 } 1774 rtmpEntry OBJECT-TYPE 1775 SYNTAX RtmpEntry 1776 ACCESS not-accessible 1777 STATUS mandatory 1778 DESCRIPTION 1779 "The route entry to a particular network range." 1780 INDEX { rtmpRangeStart } 1781 ::= { rtmpTable 1 } 1783 RtmpEntry ::= SEQUENCE { 1784 rtmpRangeStart ATNetworkNumber, 1785 rtmpRangeEnd ATNetworkNumber, 1786 rtmpNextHop OCTET STRING, 1787 rtmpType INTEGER, 1788 rtmpPort INTEGER, 1789 rtmpHops INTEGER, 1790 rtmpState INTEGER 1791 } 1793 rtmpRangeStart OBJECT-TYPE 1794 SYNTAX ATNetworkNumber 1795 ACCESS read-only 1796 STATUS mandatory 1797 DESCRIPTION 1798 "The first DDP network address in the network range 1799 to which this routing entry pertains. This is a two 1800 octet DDP network address in network byte order." 1801 ::= { rtmpEntry 1 } 1803 rtmpRangeEnd OBJECT-TYPE 1804 SYNTAX ATNetworkNumber 1805 ACCESS read-only 1806 STATUS mandatory 1807 DESCRIPTION 1808 "The last DDP network address in the network range 1809 to which this routing entry pertains. This is a two 1810 octet DDP network address in network byte order. If 1811 the network to which this routing entry pertains is a 1812 non-extended network, the value for rtmpRangeEnd 1813 shall be two octets of zero." 1814 ::= { rtmpEntry 2 } 1816 rtmpNextHop OBJECT-TYPE 1817 SYNTAX OCTET STRING 1818 ACCESS read-only 1819 STATUS mandatory 1820 DESCRIPTION 1821 "The next internet router in the route to this entry's 1822 destination network. The format of this address can be 1823 determined by examinating the atportType corresponding 1824 to this entry." 1825 ::= { rtmpEntry 3 } 1827 rtmpType OBJECT-TYPE 1828 SYNTAX INTEGER { 1829 other(1), 1830 appletalk(2), 1831 serialPPP(3), 1832 serialNonstandard(4) 1833 } 1834 ACCESS read-only 1835 STATUS mandatory 1836 DESCRIPTION 1837 "The type of network over which this route points." 1838 ::= { rtmpEntry 4 } 1840 rtmpPort OBJECT-TYPE 1841 SYNTAX INTEGER 1842 ACCESS read-only 1843 STATUS mandatory 1844 DESCRIPTION 1845 "The AppleTalk port over which this route points. The 1846 interface identified by a particular value of this 1847 variable is the same interface as identified by the same 1848 value of atportIndex." 1849 ::= { rtmpEntry 5 } 1851 rtmpHops OBJECT-TYPE 1852 SYNTAX INTEGER 1853 ACCESS read-only 1854 STATUS mandatory 1855 DESCRIPTION 1856 "The number of hops required to reach the destination 1857 network to which this routing entry pertains." 1858 ::= { rtmpEntry 6 } 1860 rtmpState OBJECT-TYPE 1861 SYNTAX INTEGER { 1862 good(1), 1863 suspect(2), 1864 badZero(3), 1865 badOne(4), 1866 invalid(5) 1867 } 1868 ACCESS read-write 1869 STATUS mandatory 1870 DESCRIPTION 1871 "The status of the information contained in this route 1872 entry. 1874 Setting this object to the value invalid(5) has the 1875 effect of invalidating the corresponding entry in the 1876 rtmpTable. That is, it effectively disassociates the 1877 mapping identified with said entry. It is an 1878 implementation-specific matter as to whether the agent 1879 removes an invalidated entry from the table. 1880 Accordingly, management stations must be prepared to 1881 receive from agents tabular information corresponding 1882 to entries not currently in use. Proper 1883 interpretation of such entries requires examination 1884 of the relevant rtmpState object." 1885 ::= { rtmpEntry 7 } 1887 rtmpInDataPkts OBJECT-TYPE 1888 SYNTAX Counter 1889 ACCESS read-only 1890 STATUS mandatory 1891 DESCRIPTION 1892 "A count of the number of good RTMP data packets 1893 received by this entity." 1894 ::= { rtmp 2 } 1896 rtmpOutDataPkts OBJECT-TYPE 1897 SYNTAX Counter 1898 ACCESS read-only 1899 STATUS mandatory 1900 DESCRIPTION 1901 "A count of the number of RTMP packets sent by this 1902 entity." 1903 ::= { rtmp 3 } 1905 rtmpInRequestPkts OBJECT-TYPE 1906 SYNTAX Counter 1907 ACCESS read-only 1908 STATUS mandatory 1909 DESCRIPTION 1910 "A count of the number of good RTMP Request packets 1911 received by this entity." 1912 ::= { rtmp 4 } 1914 rtmpNextIREqualChanges OBJECT-TYPE 1915 SYNTAX Counter 1916 ACCESS read-only 1917 STATUS mandatory 1918 DESCRIPTION 1919 "A count of the number of times RTMP changes the Next 1920 Internet Router in a routing entry because the hop count 1921 advertised in a routing tuple was equal to the current 1922 hop count for a particular network." 1923 ::= { rtmp 5 } 1925 rtmpNextIRLessChanges OBJECT-TYPE 1926 SYNTAX Counter 1927 ACCESS read-only 1928 STATUS mandatory 1929 DESCRIPTION 1930 "A count of the number of times RTMP changes the Next 1931 Internet Router in a routing entry because the hop count 1932 advertised in a routing tuple was less than the current 1933 hop count for a particular network." 1934 ::= { rtmp 6 } 1936 rtmpRouteDeletes OBJECT-TYPE 1937 SYNTAX Counter 1938 ACCESS read-only 1939 STATUS mandatory 1940 DESCRIPTION 1941 "A count of the number of times RTMP deletes a route because 1942 it was aged out of the table. This can help to detect 1943 routing problems." 1944 ::= { rtmp 7 } 1946 rtmpRoutingTableOverflows OBJECT-TYPE 1947 SYNTAX Counter 1948 ACCESS read-only 1949 STATUS mandatory 1950 DESCRIPTION 1951 "The number of times RTMP attempted to add a route 1952 to the RTMP table but failed due to lack of space." 1953 ::= { rtmp 8 } 1955 -- The RTMP Stub Group 1956 -- 1957 -- Implementation of this group is mandatory for all entities that 1958 -- implement RTMP 1959 -- 1960 -- It is intended that this group be implemented by routers and 1961 -- end nodes. 1963 rtmpOutRequestPkts OBJECT-TYPE 1964 SYNTAX Counter 1965 ACCESS read-only 1966 STATUS mandatory 1967 DESCRIPTION 1968 "A count of the number of RTMP Request packets sent 1969 by this entity." 1970 ::= { rtmpStub 1 } 1972 rtmpInVersionMismatches OBJECT-TYPE 1973 SYNTAX Counter 1974 ACCESS read-only 1975 STATUS mandatory 1976 DESCRIPTION 1977 "A count of the number of RTMP packets received by this 1978 entity that were rejected due to a version mismatch." 1979 ::= { rtmpStub 2 } 1981 rtmpInErrors OBJECT-TYPE 1982 SYNTAX Counter 1983 ACCESS read-only 1984 STATUS mandatory 1985 DESCRIPTION 1986 "A count of the number of RTMP packets received by this 1987 entity that were rejected for an error other than 1988 version mismatch." 1989 ::= { rtmpStub 3 } 1991 -- The KIP Group 1992 -- 1993 -- Implementation of this group is mandatory for all entities that 1994 -- implement KIP 1995 -- 1996 -- As an example, an instance of the kipCore object 1997 -- might be named kipCore.0.80 1999 kipTable OBJECT-TYPE 2000 SYNTAX SEQUENCE OF KipEntry 2001 ACCESS not-accessible 2002 STATUS mandatory 2003 DESCRIPTION 2004 "The table of routing information for KIP networks." 2005 ::= { kip 1 } 2007 kipEntry OBJECT-TYPE 2008 SYNTAX KipEntry 2009 ACCESS not-accessible 2010 STATUS mandatory 2011 DESCRIPTION 2012 "An entry in the routing table for KIP networks." 2013 INDEX { kipNetStart } 2014 ::= { kipTable 1 } 2016 KipEntry ::= SEQUENCE { 2017 kipNetStart ATNetworkNumber, 2018 kipNetEnd ATNetworkNumber, 2019 kipNextHop IpAddress, 2020 kipHopCount INTEGER, 2021 kipBCastAddr IpAddress, 2022 kipCore INTEGER, 2023 kipType INTEGER, 2024 kipState INTEGER, 2025 kipShare INTEGER, 2026 kipFrom IpAddress 2027 } 2029 kipNetStart OBJECT-TYPE 2030 SYNTAX ATNetworkNumber 2031 ACCESS read-only 2032 STATUS mandatory 2033 DESCRIPTION 2034 "The first AppleTalk network address in the range for 2035 this routing entry. This address is a two octet DDP 2036 network address in network byte order." 2037 ::= { kipEntry 1 } 2039 kipNetEnd OBJECT-TYPE 2040 SYNTAX ATNetworkNumber 2041 ACCESS read-write 2042 STATUS mandatory 2043 DESCRIPTION 2044 "The last AppleTalk network address in the range for 2045 this routing entry. This address is a two octet DDP 2046 network address in network byte order. If the network 2047 to which this AppleTalk port is connected 2048 is a non-extended network, the value for kipNetEnd 2049 shall be two octets of zero." 2050 ::= { kipEntry 2 } 2052 kipNextHop OBJECT-TYPE 2053 SYNTAX IpAddress 2054 ACCESS read-write 2055 STATUS mandatory 2056 DESCRIPTION 2057 "The IP address of the next hop in the route to this 2058 entry's destination network." 2059 ::= { kipEntry 3 } 2061 kipHopCount OBJECT-TYPE 2062 SYNTAX INTEGER 2063 ACCESS read-write 2064 STATUS mandatory 2065 DESCRIPTION 2066 "The number of hops required to reach the destination 2067 network to which this entry pertains." 2068 ::= { kipEntry 4 } 2070 kipBCastAddr OBJECT-TYPE 2071 SYNTAX IpAddress 2072 ACCESS read-write 2073 STATUS mandatory 2074 DESCRIPTION 2075 "The form of the IP address used to broadcast on this 2076 network." 2077 ::= { kipEntry 5 } 2079 kipCore OBJECT-TYPE 2080 SYNTAX INTEGER { 2081 core(1), 2082 notcore(2) 2083 } 2084 ACCESS read-write 2085 STATUS mandatory 2086 DESCRIPTION 2087 "The status of kipNextHop as a core gateway." 2088 ::= { kipEntry 6 } 2090 kipType OBJECT-TYPE 2091 SYNTAX INTEGER { 2092 kipRouter(1), 2093 net(2), 2094 host(3), 2095 other(4), 2096 async(5) 2097 } 2098 ACCESS read-write 2099 STATUS mandatory 2100 DESCRIPTION 2101 "The type of the entity that this route points to." 2102 ::= { kipEntry 7 } 2104 kipState OBJECT-TYPE 2105 SYNTAX INTEGER { 2106 configured(1), -- this entry is not aged 2107 learned(2), 2108 invalid(3) 2109 } 2110 ACCESS read-write 2111 STATUS mandatory 2112 DESCRIPTION 2113 "The state of this network entry. 2115 Setting this object to the value invalid(3) has the 2116 effect of invalidating the corresponding entry in the 2117 kipTable. That is, it effectively disassociates the 2118 mapping identified with said entry. It is an 2119 implementation-specific matter as to whether the agent 2120 removes an invalidated entry from the table. 2121 Accordingly, management stations must be prepared to 2122 receive from agents tabular information corresponding 2123 to entries not currently in use. Proper 2124 interpretation of such entries requires examination 2125 of the relevant kipState object." 2127 ::= { kipEntry 8 } 2129 kipShare OBJECT-TYPE 2130 SYNTAX INTEGER { 2131 shared(1), 2132 private(2) 2133 } 2134 ACCESS read-write 2135 STATUS mandatory 2136 DESCRIPTION 2137 "If the information in this entry is propagated to other 2138 routers as part of the AA routing protocol, the value of this 2139 variable is equal to shared(1). Otherwise its value is 2140 private(2)." 2141 ::= { kipEntry 9 } 2143 kipFrom OBJECT-TYPE 2144 SYNTAX IpAddress 2145 ACCESS read-only 2146 STATUS mandatory 2147 DESCRIPTION 2148 "The IP address from which the routing entry was learned 2149 via the AA protocol. If this entry was not created via 2150 the AA protocol, it should contain IP address 0.0.0.0." 2151 ::= { kipEntry 10 } 2153 -- The ZIP Router Group 2154 -- 2155 -- Implementation of this group is required for all routers which 2156 -- implement ZIP 2157 -- 2158 -- This group consists of ZIP variables that would be implemented 2159 -- by a router. 2160 -- 2161 -- As an example, an instance of the zipZoneState object 2162 -- might be named zipZoneState.0.80.4 2164 zipTable OBJECT-TYPE 2165 SYNTAX SEQUENCE OF ZipEntry 2166 ACCESS not-accessible 2167 STATUS mandatory 2168 DESCRIPTION 2169 "The table of zone information for reachable AppleTalk 2170 networks." 2171 ::= { zipRouter 1 } 2173 zipEntry OBJECT-TYPE 2174 SYNTAX ZipEntry 2175 ACCESS not-accessible 2176 STATUS mandatory 2177 DESCRIPTION 2178 "An entry of zone information for a particular zone and 2179 network combination." 2180 INDEX { zipZoneNetStart, zipZoneIndex } 2181 ::= { zipTable 1 } 2183 ZipEntry ::= SEQUENCE { 2184 zipZoneName ATName, 2185 zipZoneIndex INTEGER, 2186 zipZoneNetStart ATNetworkNumber, 2187 zipZoneNetEnd ATNetworkNumber, 2188 zipZoneState INTEGER, 2189 zipZoneFrom OCTET STRING, 2190 zipZonePort INTEGER 2191 } 2193 zipZoneName OBJECT-TYPE 2194 SYNTAX ATName 2195 ACCESS read-only 2196 STATUS mandatory 2197 DESCRIPTION 2198 "The zone name of this entry. This is stored in 2199 Mac ASCII format. If the full zone list for the 2200 entry is not known, the value for zipZoneName shall 2201 be a zero length octet string." 2202 ::= { zipEntry 1 } 2204 zipZoneIndex OBJECT-TYPE 2205 SYNTAX INTEGER 2206 ACCESS read-only 2207 STATUS mandatory 2208 DESCRIPTION 2209 "An integer that is unique to the zipZoneName that is 2210 present in this entry. For any given zone name, every 2211 zipEntry that has an equal zone name will have the same 2212 zipZoneIndex. When a zone name is discovered which is 2213 not currently in the table, it will be assigned an 2214 index greater than any previously assigned index." 2215 ::= { zipEntry 2 } 2217 zipZoneNetStart OBJECT-TYPE 2218 SYNTAX ATNetworkNumber 2219 ACCESS read-only 2220 STATUS mandatory 2221 DESCRIPTION 2222 "The network that starts the range for this entry. This 2223 address is a two octet DDP network address in network 2224 byte order." 2225 ::= { zipEntry 3 } 2227 zipZoneNetEnd OBJECT-TYPE 2228 SYNTAX ATNetworkNumber 2229 ACCESS read-only 2230 STATUS mandatory 2231 DESCRIPTION 2232 "The network that ends the range for this entry. This 2233 address is a two octet DDP network address in network 2234 byte order. If the network to which this zip entry 2235 pertains is a non-extended network, the value for 2236 zipZoneNetEnd shall be two octets of zero." 2237 ::= { zipEntry 4 } 2239 zipZoneState OBJECT-TYPE 2240 SYNTAX INTEGER { 2241 valid(1), 2242 invalid(2) 2244 } 2245 ACCESS read-write 2246 STATUS mandatory 2247 DESCRIPTION 2248 "The state of this zip entry. 2250 Setting this object to the value invalid(2) has the 2251 effect of invalidating the corresponding entry in the 2252 zipTable. That is, it effectively disassociates the 2253 mapping identified with said entry. It is an 2254 implementation-specific matter as to whether the agent 2255 removes an invalidated entry from the table. 2256 Accordingly, management stations must be prepared to 2257 receive from agents tabular information corresponding 2258 to entries not currently in use. Proper 2259 interpretation of such entries requires examination 2260 of the relevant zipZoneState object." 2261 ::= { zipEntry 5 } 2263 zipZoneFrom OBJECT-TYPE 2264 SYNTAX OCTET STRING 2265 ACCESS read-only 2266 STATUS mandatory 2267 DESCRIPTION 2268 "The address from which this zone name to network 2269 number mapping was learned. The format of this address 2270 can be determined by examining the atportType corresponding 2271 to this entry. When this mapping is learned from the 2272 entity itself, this object shall have the value of three 2273 octets of zero." 2274 ::= { zipEntry 6 } 2276 zipZonePort OBJECT-TYPE 2277 SYNTAX INTEGER 2278 ACCESS read-only 2279 STATUS mandatory 2280 DESCRIPTION 2281 "The AppleTalk port through which this zone name to network 2282 number mapping was learned. The interface identified 2283 by a particular value of this variable is the same 2284 interface as identified by the same value of atportIndex." 2285 ::= { zipEntry 7 } 2287 zipInZipQueries OBJECT-TYPE 2288 SYNTAX Counter 2289 ACCESS read-only 2290 STATUS mandatory 2291 DESCRIPTION 2292 "The number of ZIP Queries received by this entity." 2293 ::= { zipRouter 2 } 2295 zipInZipReplies OBJECT-TYPE 2296 SYNTAX Counter 2297 ACCESS read-only 2298 STATUS mandatory 2299 DESCRIPTION 2300 "The number of ZIP Replies received by this entity." 2301 ::= { zipRouter 3 } 2303 zipInZipExtendedReplies OBJECT-TYPE 2304 SYNTAX Counter 2305 ACCESS read-only 2306 STATUS mandatory 2307 DESCRIPTION 2308 "The number of ZIP Extended Replies received by this entity." 2309 ::= { zipRouter 4 } 2311 zipZoneConflictErrors OBJECT-TYPE 2312 SYNTAX Counter 2313 ACCESS read-only 2314 STATUS mandatory 2315 DESCRIPTION 2316 "The number of times a conflict has been detected between 2317 this entity's zone information and another entity's 2318 zone information." 2319 ::= { zipRouter 5 } 2321 zipInObsoletes OBJECT-TYPE 2322 SYNTAX Counter 2323 ACCESS read-only 2324 STATUS mandatory 2325 DESCRIPTION 2326 "The number of ZIP Takedown or ZIP Bringup packets received 2327 by this entity. Note that as the ZIP Takedown and ZIP 2328 Bringup packets have been obsoleted, the receipt of one of 2329 these packets indicates that a node sent it in error." 2330 ::= { zipRouter 6 } 2332 -- The zipRouterNetInfoTable is used to record information about 2333 -- zipGetNetInfo and zipGetNetInfo Reply packets that were received 2334 -- on each port for a router. This table augments the 2335 -- atportTable. 2336 -- 2337 -- As an example, an instance of the zipInGetNetInfos object 2338 -- might be named zipInGetNetInfos.2 2340 zipRouterNetInfoTable OBJECT-TYPE 2341 SYNTAX SEQUENCE OF ZipRouterNetInfoEntry 2342 ACCESS not-accessible 2343 STATUS mandatory 2344 DESCRIPTION 2345 "The table of Net Info packets received by each port 2346 on this entity." 2347 ::= { zipRouter 7 } 2349 zipRouterNetInfoEntry OBJECT-TYPE 2350 SYNTAX ZipRouterNetInfoEntry 2351 ACCESS not-accessible 2352 STATUS mandatory 2353 DESCRIPTION 2354 "The description of the Net Info packets received on 2355 a particular port on this entity. One such entry shall 2356 exist for each atport on this router entity." 2357 INDEX { atportIndex } 2358 ::= { zipRouterNetInfoTable 1 } 2360 ZipRouterNetInfoEntry ::= SEQUENCE { 2361 zipInGetNetInfos Counter, 2362 zipOutGetNetInfoReplies Counter, 2363 zipZoneOutInvalids Counter, 2364 zipAddressInvalids Counter 2365 } 2367 zipInGetNetInfos OBJECT-TYPE 2368 SYNTAX Counter 2369 ACCESS read-only 2370 STATUS mandatory 2371 DESCRIPTION 2372 "The number of ZIP GetNetInfo packets received on this 2373 port by this entity." 2374 ::= { zipRouterNetInfoEntry 1 } 2376 zipOutGetNetInfoReplies OBJECT-TYPE 2377 SYNTAX Counter 2378 ACCESS read-only 2379 STATUS mandatory 2380 DESCRIPTION 2381 "The number of ZIP GetNetInfo Reply packets sent out this 2382 port by this entity." 2383 ::= { zipRouterNetInfoEntry 2 } 2385 zipZoneOutInvalids OBJECT-TYPE 2386 SYNTAX Counter 2387 ACCESS read-only 2388 STATUS mandatory 2389 DESCRIPTION 2390 "The number of times this entity has sent a ZIP GetNetInfo 2391 Reply with the zone invalid bit set in response to a 2392 GetNetInfo Request with an invalid zone name." 2393 ::= { zipRouterNetInfoEntry 3 } 2395 zipAddressInvalids OBJECT-TYPE 2396 SYNTAX Counter 2397 ACCESS read-only 2398 STATUS mandatory 2399 DESCRIPTION 2400 "The number of times this entity had to broadcast a ZIP 2401 GetNetInfo Reply because the GetNetInfo Request had an 2402 invalid address." 2403 ::= { zipRouterNetInfoEntry 4 } 2405 -- The ZIP End Node Group 2406 -- 2407 -- Implementation of this group is mandatory for all entities that 2408 -- implement ZIP 2409 -- 2410 -- This group consists of ZIP variables that would be implemented 2411 -- by either a router or an end node. 2413 -- The zipNetInfoTable is used to record information about 2414 -- zipGetNetInfo and zipGetNetInfo Reply packets that were received 2415 -- on each port of an entity. This table augments the 2416 -- atportTable. 2417 -- 2418 -- As an example, an instance of the zipOutGetNetInfos object 2419 -- might be named zipOutGetNetInfos.2 2421 zipNetInfoTable OBJECT-TYPE 2422 SYNTAX SEQUENCE OF ZipNetInfoEntry 2423 ACCESS not-accessible 2424 STATUS mandatory 2425 DESCRIPTION 2426 "The table of Net Info packets received by each port 2427 on this entity." 2428 ::= { zipEndNode 1 } 2430 zipNetInfoEntry OBJECT-TYPE 2431 SYNTAX ZipNetInfoEntry 2432 ACCESS not-accessible 2433 STATUS mandatory 2434 DESCRIPTION 2435 "The description of the Net Info packets received on 2436 a particular port on this entity. One such entry shall 2437 exist for each atport on this entity." 2438 INDEX { atportIndex } 2439 ::= { zipNetInfoTable 1 } 2441 ZipNetInfoEntry ::= SEQUENCE { 2442 zipOutGetNetInfos Counter, 2443 zipInGetNetInfoReplies Counter, 2444 zipZoneInInvalids Counter 2445 } 2447 zipOutGetNetInfos OBJECT-TYPE 2448 SYNTAX Counter 2449 ACCESS read-only 2450 STATUS mandatory 2451 DESCRIPTION 2452 "The number of ZIP GetNetInfo packets sent out this port 2453 by this entity." 2454 ::= { zipNetInfoEntry 1 } 2456 zipInGetNetInfoReplies OBJECT-TYPE 2457 SYNTAX Counter 2458 ACCESS read-only 2459 STATUS mandatory 2460 DESCRIPTION 2461 "The number of ZIP GetNetInfo Reply packets received on 2462 this port by this entity." 2463 ::= { zipNetInfoEntry 2 } 2465 zipZoneInInvalids OBJECT-TYPE 2466 SYNTAX Counter 2467 ACCESS read-only 2468 STATUS mandatory 2469 DESCRIPTION 2470 "The number of times this entity has received a ZIP 2471 GetNetInfo Reply with the zone invalid bit set because 2472 the corresponding GetNetInfo Request had an invalid 2473 zone name." 2474 ::= { zipNetInfoEntry 3 } 2476 zipInErrors OBJECT-TYPE 2477 SYNTAX Counter 2478 ACCESS read-only 2479 STATUS mandatory 2480 DESCRIPTION 2481 "The number of ZIP packets received by this entity 2482 that were rejected for any error." 2483 ::= { zipEndNode 2 } 2485 -- The NBP Group 2486 -- 2487 -- Implementation of this group is mandatory for all entities that 2488 -- implement NBP 2489 -- 2490 -- As an example, an instance of the nbpZone object 2491 -- might be named nbpZone.2 2493 nbpTable OBJECT-TYPE 2494 SYNTAX SEQUENCE OF NbpEntry 2495 ACCESS not-accessible 2496 STATUS mandatory 2497 DESCRIPTION 2498 "The table of NBP services registered on this entity." 2499 ::= { nbp 1 } 2501 nbpEntry OBJECT-TYPE 2502 SYNTAX NbpEntry 2503 ACCESS not-accessible 2504 STATUS mandatory 2505 DESCRIPTION 2506 "The description of an NBP service registered on this 2507 entity." 2508 INDEX { nbpIndex } 2509 ::= { nbpTable 1 } 2511 NbpEntry ::= SEQUENCE { 2512 nbpIndex INTEGER, 2513 nbpObject ATName (SIZE (1..32)), 2514 nbpType ATName (SIZE (1..32)), 2515 nbpZone ATName, 2516 nbpState INTEGER, 2517 nbpAddress DdpSocketAddress, 2518 nbpEnumerator INTEGER (0..255) 2519 } 2521 nbpIndex OBJECT-TYPE 2522 SYNTAX INTEGER 2523 ACCESS read-write 2524 STATUS mandatory 2525 DESCRIPTION 2526 "The index of this NBP entry. This index is unique 2527 with respect to the indexes of all other NBP entries, 2528 and shall remain constant throughout the lifetime 2529 of this object." 2531 ::= { nbpEntry 1 } 2533 nbpObject OBJECT-TYPE 2534 SYNTAX ATName (SIZE (1..32)) 2535 ACCESS read-write 2536 STATUS mandatory 2537 DESCRIPTION 2538 "The name of the service described by this entity. 2539 When this variable is changed, the entity should 2540 perform an NBP registration using the new nbpObject." 2541 ::= { nbpEntry 2 } 2543 nbpType OBJECT-TYPE 2544 SYNTAX ATName (SIZE (1..32)) 2545 ACCESS read-write 2546 STATUS mandatory 2547 DESCRIPTION 2548 "The type of the service described by this entity. 2549 When this variable is changed, the entity should 2550 perform an NBP registration using the new nbpType." 2551 ::= { nbpEntry 3 } 2553 nbpZone OBJECT-TYPE 2554 SYNTAX ATName 2555 ACCESS read-write 2556 STATUS mandatory 2557 DESCRIPTION 2558 "The zone the service described by this entity is 2559 registered in. This must be the actual zone name, 2560 without any wildcard characters. When this variable 2561 is changed, the entity should perform an NBP registration 2562 using the new nbpZone." 2563 ::= { nbpEntry 4 } 2565 nbpState OBJECT-TYPE 2566 SYNTAX INTEGER { 2567 valid(1), 2568 registering(2), -- attempting to register the service 2569 registrationFailed(3), 2570 invalid(4) 2571 } 2572 ACCESS read-write 2573 STATUS mandatory 2574 DESCRIPTION 2575 "The state of this NBP entry. 2577 When the registration for an entry in the nbpTable 2578 fails, it is an implementation-specific matter as to 2579 how long the entry will remain in the 2580 registrationFailed(3) state before moving to the 2581 invalid(4) state. Note that the entry may pass 2582 immediately from the registrationFailed state to 2583 the invalid state. 2585 Setting this object to the value invalid(4) has the 2586 effect of invalidating the corresponding entry in the 2587 nbpTable. That is, it effectively disassociates the 2588 mapping identified with said entry. It is an 2589 implementation-specific matter as to whether the agent 2590 removes an invalidated entry from the table. 2591 Accordingly, management stations must be prepared to 2592 receive from agents tabular information corresponding 2593 to entries not currently in use. Proper 2594 interpretation of such entries requires examination 2595 of the relevant nbpState object." 2596 ::= { nbpEntry 5 } 2598 nbpAddress OBJECT-TYPE 2599 SYNTAX DdpSocketAddress 2600 ACCESS read-write 2601 STATUS mandatory 2602 DESCRIPTION 2603 "The DDP network, node, and socket number of this entity. 2604 If this is unspecified, for instance if the registration 2605 is on all ports of a multiport device, this object shall 2606 have the value of three octets of zero, followed by one 2607 octet of socket number." 2608 ::= { nbpEntry 6 } 2610 nbpEnumerator OBJECT-TYPE 2611 SYNTAX INTEGER (0..255) 2612 ACCESS read-only 2613 STATUS mandatory 2614 DESCRIPTION 2615 "The enumerator assigned to this entity." 2616 ::= { nbpEntry 7 } 2618 nbpInLookUpRequests OBJECT-TYPE 2619 SYNTAX Counter 2620 ACCESS read-only 2621 STATUS mandatory 2622 DESCRIPTION 2623 "The number of NBP LookUp Requests received." 2624 ::= { nbp 2 } 2626 nbpInLookUpReplies OBJECT-TYPE 2627 SYNTAX Counter 2628 ACCESS read-only 2629 STATUS mandatory 2630 DESCRIPTION 2631 "The number of NBP LookUp Replies received." 2632 ::= { nbp 3 } 2634 nbpInBroadcastRequests OBJECT-TYPE 2635 SYNTAX Counter 2636 ACCESS read-only 2637 STATUS mandatory 2638 DESCRIPTION 2639 "The number of NBP Broadcast Requests received." 2640 ::= { nbp 4 } 2642 nbpInForwardRequests OBJECT-TYPE 2643 SYNTAX Counter 2644 ACCESS read-only 2645 STATUS mandatory 2646 DESCRIPTION 2647 "The number of NBP Forward Requests received." 2648 ::= { nbp 5 } 2650 nbpOutLookUpReplies OBJECT-TYPE 2651 SYNTAX Counter 2652 ACCESS read-only 2653 STATUS mandatory 2654 DESCRIPTION 2655 "The number of NBP LookUp Replies sent." 2656 ::= { nbp 6 } 2658 nbpRegistrationFailures OBJECT-TYPE 2659 SYNTAX Counter 2660 ACCESS read-only 2661 STATUS mandatory 2662 DESCRIPTION 2663 "The number of times this node experienced a failure in 2664 attempting to register an NBP entity." 2665 ::= { nbp 7 } 2667 nbpInErrors OBJECT-TYPE 2668 SYNTAX Counter 2669 ACCESS read-only 2670 STATUS mandatory 2671 DESCRIPTION 2672 "The number of NBP packets received by this entity that were 2673 rejected for any error." 2674 ::= { nbp 8 } 2676 -- The ATEcho Group 2677 -- 2678 -- Implementation of this group is mandatory for all entities that 2679 -- implement ATEcho 2681 atechoRequests OBJECT-TYPE 2682 SYNTAX Counter 2683 ACCESS read-only 2684 STATUS mandatory 2685 DESCRIPTION 2686 "The number of AppleTalk Echo requests received." 2687 ::= { atecho 1 } 2689 atechoReplies OBJECT-TYPE 2690 SYNTAX Counter 2691 ACCESS read-only 2692 STATUS mandatory 2693 DESCRIPTION 2694 "The number of AppleTalk Echo replies sent." 2695 ::= { atecho 2 } 2697 atechoOutRequests OBJECT-TYPE 2698 SYNTAX Counter 2699 ACCESS read-only 2700 STATUS mandatory 2701 DESCRIPTION 2702 "The count of AppleTalk Echo requests sent." 2703 ::= { atecho 3 } 2705 atechoInReplies OBJECT-TYPE 2706 SYNTAX Counter 2707 ACCESS read-only 2708 STATUS mandatory 2709 DESCRIPTION 2710 "The count of AppleTalk Echo replies received." 2711 ::= { atecho 4 } 2713 -- The ATP Group 2714 -- 2715 -- Implementation of this group is mandatory for all entities that 2716 -- implement ATP 2718 atpInPkts OBJECT-TYPE 2719 SYNTAX Counter 2720 ACCESS read-only 2721 STATUS mandatory 2722 DESCRIPTION 2723 "The number of ATP packets received by this entity." 2724 ::= { atp 1 } 2726 atpOutPkts OBJECT-TYPE 2727 SYNTAX Counter 2728 ACCESS read-only 2729 STATUS mandatory 2730 DESCRIPTION 2731 "The number of ATP packets sent by this entity." 2732 ::= { atp 2 } 2734 atpTRequestRetransmissions OBJECT-TYPE 2735 SYNTAX Counter 2736 ACCESS read-only 2737 STATUS mandatory 2738 DESCRIPTION 2739 "The number of times that a timeout occurred and a 2740 Transaction Request packet needed to be retransmitted 2741 by this host." 2742 ::= { atp 3 } 2744 atpTResponseRetransmissions OBJECT-TYPE 2745 SYNTAX Counter 2746 ACCESS read-only 2747 STATUS mandatory 2748 DESCRIPTION 2749 "The number of times a timeout was detected and a 2750 Transaction Response packet needed to be retransmitted 2751 by this host." 2752 ::= { atp 4 } 2754 atpReleaseTimerExpiredCounts OBJECT-TYPE 2755 SYNTAX Counter 2756 ACCESS read-only 2757 STATUS mandatory 2758 DESCRIPTION 2759 "The number of times the release timer expired, as a result 2760 of which a Request Control Block had to be deleted." 2761 ::= { atp 5 } 2763 atpRetryCountExceededs OBJECT-TYPE 2764 SYNTAX Counter 2765 ACCESS read-only 2766 STATUS mandatory 2767 DESCRIPTION 2768 "The number of times the retry count was exceeded, and an 2769 error was returned to the client of ATP." 2770 ::= { atp 6 } 2772 -- As an example, an instance of the atpListenerStatus object 2773 -- might be named atpListenerStatus.0.80.220.3 2775 atpListenerTable OBJECT-TYPE 2776 SYNTAX SEQUENCE OF AtpListenerEntry 2777 ACCESS not-accessible 2778 STATUS mandatory 2779 DESCRIPTION 2780 "The atpListenerTable stores information for each ATP 2781 socket that has a listener." 2782 ::= { atp 7 } 2784 atpListenerEntry OBJECT-TYPE 2785 SYNTAX AtpListenerEntry 2786 ACCESS not-accessible 2787 STATUS mandatory 2788 DESCRIPTION 2789 "This atpListenerEntry contains information about a 2790 particular socket that has a socket listener." 2791 INDEX { atpListenerAddress } 2792 ::= { atpListenerTable 1 } 2794 AtpListenerEntry ::= SEQUENCE { 2795 atpListenerAddress DdpSocketAddress, 2796 atpListenerStatus INTEGER 2797 } 2799 atpListenerAddress OBJECT-TYPE 2800 SYNTAX DdpSocketAddress 2801 ACCESS not-accessible 2802 STATUS mandatory 2803 DESCRIPTION 2804 "The DDP address that this socket listener is bound to. 2805 If this socket listener isn't bound to a particular 2806 address, for instance if it is intended for all 2807 interfaces, this object shall have the value of three 2808 octets of zero followed by one octet of socket number." 2809 ::= { atpListenerEntry 1 } 2811 atpListenerStatus OBJECT-TYPE 2812 SYNTAX INTEGER { 2813 valid(1), 2814 invalid(2) 2815 } 2816 ACCESS read-write 2817 STATUS mandatory 2818 DESCRIPTION 2819 "The status of this socket. 2821 Setting this object to the value invalid(2) has the 2822 effect of invalidating the corresponding entry in the 2823 atpListenerTable. That is, it effectively disassociates 2824 the mapping identified with said entry. It is an 2825 implementation-specific matter as to whether the agent 2826 removes an invalidated entry from the table. 2827 Accordingly, management stations must be prepared to 2828 receive from agents tabular information corresponding 2829 to entries not currently in use. Proper 2830 interpretation of such entries requires examination 2831 of the relevant atpListenerStatus object." 2832 ::= { atpListenerEntry 2 } 2834 -- The PAP group 2835 -- 2836 -- Implementation of this group is mandatory for all entities that 2837 -- implement PAP 2839 papInOpenConns OBJECT-TYPE 2840 SYNTAX Counter 2841 ACCESS read-only 2842 STATUS mandatory 2843 DESCRIPTION 2844 "The number of PAP Open Connection requests received by 2845 this entity." 2846 ::= { pap 1 } 2848 papOutOpenConns OBJECT-TYPE 2849 SYNTAX Counter 2850 ACCESS read-only 2851 STATUS mandatory 2852 DESCRIPTION 2853 "The number of PAP Open Connection requests sent by 2854 this entity." 2855 ::= { pap 2 } 2857 papInDatas OBJECT-TYPE 2858 SYNTAX Counter 2859 ACCESS read-only 2860 STATUS mandatory 2861 DESCRIPTION 2862 "The number of PAP Data messages received by 2863 this entity." 2864 ::= { pap 3 } 2866 papOutDatas OBJECT-TYPE 2867 SYNTAX Counter 2868 ACCESS read-only 2869 STATUS mandatory 2870 DESCRIPTION 2871 "The number of PAP Data messages sent by 2872 this entity." 2873 ::= { pap 4 } 2875 papInCloseConns OBJECT-TYPE 2876 SYNTAX Counter 2877 ACCESS read-only 2878 STATUS mandatory 2879 DESCRIPTION 2880 "The number of PAP Close Connection requests received by 2881 this entity." 2882 ::= { pap 5 } 2884 papOutCloseConns OBJECT-TYPE 2885 SYNTAX Counter 2886 ACCESS read-only 2887 STATUS mandatory 2888 DESCRIPTION 2889 "The number of PAP Close Connection requests sent by 2890 this entity." 2891 ::= { pap 6 } 2893 papTickleTimeoutCloses OBJECT-TYPE 2894 SYNTAX Counter 2895 ACCESS read-only 2896 STATUS mandatory 2897 DESCRIPTION 2898 "The number of times the PAP entity on this node closed 2899 a connection because it didn't receive a Tickle message 2900 before its timer expired." 2901 ::= { pap 7 } 2903 -- As an example, an instance of the papServerStatus object 2904 -- might be named papServerStatus.1 2906 papServerTable OBJECT-TYPE 2907 SYNTAX SEQUENCE OF PapServerEntry 2908 ACCESS not-accessible 2909 STATUS mandatory 2910 DESCRIPTION 2911 "A list of servers on this entity that are accessible through 2912 the Printer Access Protocol." 2913 ::= { pap 8 } 2915 papServerEntry OBJECT-TYPE 2916 SYNTAX PapServerEntry 2917 ACCESS not-accessible 2918 STATUS mandatory 2919 DESCRIPTION 2920 "A set of information about a particular PAP server's 2921 configuration and performance." 2922 INDEX { papServerIndex } 2923 ::= { papServerTable 1 } 2925 PapServerEntry ::= SEQUENCE { 2926 papServerIndex INTEGER, 2927 papServerListeningSocket DdpSocketAddress, 2928 papServerStatus DisplayString, 2929 papServerCompletedJobs Counter, 2930 papServerBusyJobs INTEGER, 2931 papServerFreeJobs INTEGER, 2932 papServerAuthenticationFailures Counter, 2933 papServerAccountingFailures Counter, 2934 papServerGeneralFailures Counter, 2935 papServerState INTEGER, 2936 papServerLastStatusMsg DisplayString 2937 } 2939 papServerIndex OBJECT-TYPE 2940 SYNTAX INTEGER 2941 ACCESS not-accessible 2942 STATUS mandatory 2943 DESCRIPTION 2944 "An unique value for each Printer Access Protocol Server." 2945 ::= { papServerEntry 1 } 2947 papServerListeningSocket OBJECT-TYPE 2948 SYNTAX DdpSocketAddress 2949 ACCESS read-write 2950 STATUS mandatory 2951 DESCRIPTION 2952 "The Server Listening Socket that this PAP server is 2953 listening on." 2954 ::= { papServerEntry 2 } 2956 papServerStatus OBJECT-TYPE 2957 SYNTAX DisplayString 2958 ACCESS read-only 2959 STATUS mandatory 2960 DESCRIPTION 2961 "The status string of this server. This is the message as it 2962 would appear in a PAP Status Reply from this server." 2963 ::= { papServerEntry 3 } 2965 papServerCompletedJobs OBJECT-TYPE 2966 SYNTAX Counter 2967 ACCESS read-only 2968 STATUS mandatory 2969 DESCRIPTION 2970 "The number of jobs that have been accepted and successfully 2971 executed by this server." 2972 ::= { papServerEntry 4 } 2974 papServerBusyJobs OBJECT-TYPE 2975 SYNTAX INTEGER 2976 ACCESS read-only 2977 STATUS mandatory 2978 DESCRIPTION 2979 "The number of GetNextJob calls that have accepted and are 2980 currently executing a job." 2981 ::= { papServerEntry 5 } 2983 papServerFreeJobs OBJECT-TYPE 2984 SYNTAX INTEGER 2985 ACCESS read-only 2986 STATUS mandatory 2987 DESCRIPTION 2988 "The minimum number of GetNextJob calls that are currently 2989 waiting for a job." 2990 ::= { papServerEntry 6 } 2992 papServerAuthenticationFailures OBJECT-TYPE 2993 SYNTAX Counter 2994 ACCESS read-only 2995 STATUS mandatory 2996 DESCRIPTION 2997 "The number of times this PAP server rejected a job because 2998 the job was not correctly authenticated." 2999 ::= { papServerEntry 7 } 3001 papServerAccountingFailures OBJECT-TYPE 3002 SYNTAX Counter 3003 ACCESS read-only 3004 STATUS mandatory 3005 DESCRIPTION 3006 "The number of times this PAP server rejected a job because 3007 the job did not fit some accounting rule, such as exceeding 3008 a quota." 3009 ::= { papServerEntry 8 } 3011 papServerGeneralFailures OBJECT-TYPE 3012 SYNTAX Counter 3013 ACCESS read-only 3014 STATUS mandatory 3015 DESCRIPTION 3016 "The number of times this PAP server rejected a job for 3017 some reason other than authentication or accounting 3018 failures." 3019 ::= { papServerEntry 9 } 3021 papServerState OBJECT-TYPE 3022 SYNTAX INTEGER { 3023 valid(1), 3024 invalid(2) 3025 } 3026 ACCESS read-write 3027 STATUS mandatory 3028 DESCRIPTION 3029 "The state of this PAP Server entry. 3031 Setting this object to the value invalid(2) has the 3032 effect of invalidating the corresponding entry in the 3033 papServerTable. That is, it effectively disassociates 3034 the mapping identified with said entry. It is an 3035 implementation-specific matter as to whether the agent 3036 removes an invalidated entry from the table. 3037 Accordingly, management stations must be prepared to 3038 receive from agents tabular information corresponding 3039 to entries not currently in use. Proper 3040 interpretation of such entries requires examination 3041 of the relevant papServerState object." 3042 ::= { papServerEntry 10 } 3044 papServerLastStatusMsg OBJECT-TYPE 3045 SYNTAX DisplayString 3046 ACCESS read-only 3047 STATUS mandatory 3048 DESCRIPTION 3049 "The last status message that was transmitted by 3050 this server." 3051 ::= { papServerEntry 11 } 3053 -- The ASP Group 3054 -- 3055 -- Implementation of this group is mandatory for all entities that 3056 -- implement ASP 3058 aspInputTransactions OBJECT-TYPE 3059 SYNTAX Counter 3060 ACCESS read-only 3061 STATUS mandatory 3062 DESCRIPTION 3063 "The number of ASP requests and replies received by 3064 this entity. Note that this is not necessarily the 3065 number of packets containing ASP transactions." 3066 ::= { asp 1 } 3068 aspOutputTransactions OBJECT-TYPE 3069 SYNTAX Counter 3070 ACCESS read-only 3071 STATUS mandatory 3072 DESCRIPTION 3073 "The number of ASP requests and replies sent by this 3074 entity. Note that this is not necessarily the number 3075 of packets containing ASP transactions." 3076 ::= { asp 2 } 3078 aspInOpenSessions OBJECT-TYPE 3079 SYNTAX Counter 3080 ACCESS read-only 3081 STATUS mandatory 3082 DESCRIPTION 3083 "The number of ASP Open Session requests and replies 3084 received by this entity." 3085 ::= { asp 3 } 3087 aspOutOpenSessions OBJECT-TYPE 3088 SYNTAX Counter 3089 ACCESS read-only 3090 STATUS mandatory 3091 DESCRIPTION 3092 "The number of ASP Open Session requests and replies 3093 sent by this entity." 3094 ::= { asp 4 } 3096 aspInCloseSessions OBJECT-TYPE 3097 SYNTAX Counter 3098 ACCESS read-only 3099 STATUS mandatory 3100 DESCRIPTION 3101 "The number of ASP Close Session requests and replies 3102 received by this entity." 3103 ::= { asp 5 } 3105 aspOutCloseSessions OBJECT-TYPE 3106 SYNTAX Counter 3107 ACCESS read-only 3108 STATUS mandatory 3109 DESCRIPTION 3110 "The number of ASP Close Session requests and replies 3111 sent by this entity." 3112 ::= { asp 6 } 3114 aspNoMoreSessionsErrors OBJECT-TYPE 3115 SYNTAX Counter 3116 ACCESS read-only 3117 STATUS mandatory 3118 DESCRIPTION 3119 "The number of times an error condition was returned 3120 because this server implementation could not support 3121 another session." 3122 ::= { asp 7 } 3124 aspTickleTimeOutCloses OBJECT-TYPE 3125 SYNTAX Counter 3126 ACCESS read-only 3127 STATUS mandatory 3128 DESCRIPTION 3129 "The number of times the ASP entity on this node closed 3130 a connection because it didn't receive any messages 3131 from the remote end before its timer expired." 3132 ::= { asp 8 } 3134 -- As an example, an instance of the aspConnState object 3135 -- might be named aspConnState.0.80.220.135.0.80.239.119.12 3137 aspConnTable OBJECT-TYPE 3138 SYNTAX SEQUENCE OF AspConnEntry 3139 ACCESS not-accessible 3140 STATUS mandatory 3141 DESCRIPTION 3142 "A list of ASP connections on this entity." 3144 ::= { asp 9 } 3146 aspConnEntry OBJECT-TYPE 3147 SYNTAX AspConnEntry 3148 ACCESS not-accessible 3149 STATUS mandatory 3150 DESCRIPTION 3151 "A set of information describing an ASP connection." 3152 INDEX { aspConnLocalAddress, aspConnRemoteAddress, 3153 aspConnID } 3154 ::= { aspConnTable 1 } 3156 AspConnEntry ::= SEQUENCE { 3157 aspConnLocalAddress DdpSocketAddress, 3158 aspConnRemoteAddress DdpSocketAddress, 3159 aspConnID INTEGER (1..255), 3160 aspConnLastReqNum INTEGER (1..65535), 3161 aspConnServerEnd INTEGER, 3162 aspConnState INTEGER 3163 } 3165 aspConnLocalAddress OBJECT-TYPE 3166 SYNTAX DdpSocketAddress 3167 ACCESS not-accessible 3168 STATUS mandatory 3169 DESCRIPTION 3170 "The local address of this ASP connection." 3171 ::= { aspConnEntry 1 } 3173 aspConnRemoteAddress OBJECT-TYPE 3174 SYNTAX DdpSocketAddress 3175 ACCESS not-accessible 3176 STATUS mandatory 3177 DESCRIPTION 3178 "The remote address of this ASP connection. If 3179 this entry is in the listening mode, this object 3180 shall have a value of four octets of zero." 3181 ::= { aspConnEntry 2 } 3183 aspConnID OBJECT-TYPE 3184 SYNTAX INTEGER (1..255) 3185 ACCESS not-accessible 3186 STATUS mandatory 3187 DESCRIPTION 3188 "The remote Connection ID of this ASP connection. If 3189 this entry is in the listening mode, this object 3190 shall have a value of zero." 3191 ::= { aspConnEntry 3 } 3193 aspConnLastReqNum OBJECT-TYPE 3194 SYNTAX INTEGER (1..65535) 3195 ACCESS read-only 3196 STATUS mandatory 3197 DESCRIPTION 3198 "The last request number on this ASP connection. If 3199 this entry is in the listening mode, this object 3200 shall have a value of zero." 3201 ::= { aspConnEntry 4 } 3203 aspConnServerEnd OBJECT-TYPE 3204 SYNTAX INTEGER { 3205 sss(1), -- Server Session Socket 3206 wss(2), -- Workstation Session Socket 3207 sls(3) -- Server Listening Socket 3208 } 3209 ACCESS read-only 3210 STATUS mandatory 3211 DESCRIPTION 3212 "Specifies what mode the local session end is in." 3213 ::= { aspConnEntry 5 } 3215 aspConnState OBJECT-TYPE 3216 SYNTAX INTEGER { 3217 open(1), 3218 closed(2), 3219 invalid(3) 3220 } 3221 ACCESS read-write 3222 STATUS mandatory 3223 DESCRIPTION 3224 "The state of this ASP connection. 3226 Setting this object to the value invalid(3) has the 3227 effect of invalidating the corresponding entry in the 3228 aspConnTable. That is, it effectively disassociates 3229 the mapping identified with said entry. It is an 3230 implementation-specific matter as to whether the agent 3231 removes an invalidated entry from the table. 3232 Accordingly, management stations must be prepared to 3233 receive from agents tabular information corresponding 3234 to entries not currently in use. Proper 3235 interpretation of such entries requires examination 3236 of the relevant aspConnState object." 3237 ::= { aspConnEntry 6 } 3239 -- The ADSP Group 3240 -- 3241 -- Implementation of this group is mandatory for all entities that 3242 -- implement ADSP 3244 adspInPkts OBJECT-TYPE 3245 SYNTAX Counter 3246 ACCESS read-only 3247 STATUS mandatory 3248 DESCRIPTION 3249 "The number of ADSP packets received by this entity." 3250 ::= { adsp 1 } 3252 adspOutPkts OBJECT-TYPE 3253 SYNTAX Counter 3254 ACCESS read-only 3255 STATUS mandatory 3256 DESCRIPTION 3257 "The number of ADSP packets sent by this entity." 3258 ::= { adsp 2 } 3260 adspInOctets OBJECT-TYPE 3261 SYNTAX Counter 3262 ACCESS read-only 3263 STATUS mandatory 3264 DESCRIPTION 3265 "The number of data octets contained in ADSP packets 3266 received by this entity. Note that this does not 3267 include EOM bits." 3268 ::= { adsp 3 } 3270 adspOutOctets OBJECT-TYPE 3271 SYNTAX Counter 3272 ACCESS read-only 3273 STATUS mandatory 3274 DESCRIPTION 3275 "The number of data octets contained in ADSP packets 3276 sent by this entity. Note that this does not include 3277 EOM bits." 3278 ::= { adsp 4 } 3280 adspInDataPkts OBJECT-TYPE 3281 SYNTAX Counter 3282 ACCESS read-only 3283 STATUS mandatory 3284 DESCRIPTION 3285 "The number of ADSP data packets this entity has received." 3286 ::= { adsp 5 } 3288 adspOutDataPkts OBJECT-TYPE 3289 SYNTAX Counter 3290 ACCESS read-only 3291 STATUS mandatory 3292 DESCRIPTION 3293 "The number of ADSP data packets this entity has sent." 3294 ::= { adsp 6 } 3296 adspTimeoutErrors OBJECT-TYPE 3297 SYNTAX Counter 3298 ACCESS read-only 3299 STATUS mandatory 3300 DESCRIPTION 3301 "The number of times the ADSP on this entity detected 3302 an expired connection timer." 3303 ::= { adsp 7 } 3305 adspTimeoutCloseErrors OBJECT-TYPE 3306 SYNTAX Counter 3307 ACCESS read-only 3308 STATUS mandatory 3309 DESCRIPTION 3310 "The number of times the ADSP on this entity closed a 3311 connection because of too many timeouts." 3312 ::= { adsp 8 } 3314 -- As an example, an instance of the adspConnState object 3315 -- might be named adspConnState.0.80.220.7.0.80.239.142.31231 3317 adspConnTable OBJECT-TYPE 3318 SYNTAX SEQUENCE OF AdspConnEntry 3319 ACCESS not-accessible 3320 STATUS mandatory 3321 DESCRIPTION 3322 "A list of ADSP connections on this entity." 3323 ::= { adsp 9 } 3325 adspConnEntry OBJECT-TYPE 3326 SYNTAX AdspConnEntry 3327 ACCESS not-accessible 3328 STATUS mandatory 3329 DESCRIPTION 3330 "A set of information describing an ADSP connection." 3331 INDEX { adspConnLocalAddress, adspConnRemoteAddress, 3332 adspConnLocalConnID } 3333 ::= { adspConnTable 1 } 3335 AdspConnEntry ::= SEQUENCE { 3336 adspConnLocalAddress DdpSocketAddress, 3337 adspConnLocalConnID INTEGER (0..65535), 3338 adspConnRemoteAddress DdpSocketAddress, 3339 adspConnRemoteConnID INTEGER (0..65535), 3340 adspConnState INTEGER 3341 } 3343 adspConnLocalAddress OBJECT-TYPE 3344 SYNTAX DdpSocketAddress 3345 ACCESS not-accessible 3346 STATUS mandatory 3347 DESCRIPTION 3348 "The local DDP address of this ADSP connection." 3349 ::= { adspConnEntry 1 } 3351 adspConnLocalConnID OBJECT-TYPE 3352 SYNTAX INTEGER (0..65535) 3353 ACCESS not-accessible 3354 STATUS mandatory 3355 DESCRIPTION 3356 "The local Connection ID of this ADSP connection. If 3357 this entry specifies an ADSP listener, this value 3358 shall be zero." 3359 ::= { adspConnEntry 2 } 3361 adspConnRemoteAddress OBJECT-TYPE 3362 SYNTAX DdpSocketAddress 3363 ACCESS not-accessible 3364 STATUS mandatory 3365 DESCRIPTION 3366 "The remote DDP address of this ADSP connection. If 3367 this entry specifies an ADSP listener, this value 3368 shall be zero." 3369 ::= { adspConnEntry 3 } 3371 adspConnRemoteConnID OBJECT-TYPE 3372 SYNTAX INTEGER (0..65535) 3373 ACCESS read-only 3374 STATUS mandatory 3375 DESCRIPTION 3376 "The remote Connection ID of this ADSP connection. 3377 If this entry specifies an ADSP listener, this value 3378 shall be zero." 3379 ::= { adspConnEntry 4 } 3381 adspConnState OBJECT-TYPE 3382 SYNTAX INTEGER { 3383 open(1), 3384 localHalfOpen(2), 3385 remoteHalfOpen(3), 3386 listening(4), 3387 closed(5), 3388 invalid(6) 3389 } 3390 ACCESS read-write 3391 STATUS mandatory 3392 DESCRIPTION 3393 "The state of this ADSP connection. The state is open 3394 if both ends are established. If only one end is 3395 established, then the state is half-open. If neither 3396 end is established, then the state is closed. If an ADSP 3397 server is listening on a socket and is not yet connected, 3398 its state is set to listening, and the 3399 adspConnRemoteAddress, adspConnRemoteSocket, 3400 adspConnRemoteConnID, and adspConnRemoteWindowSize are 3401 all set to zero. 3403 Setting this object to the value invalid(6) has the 3404 effect of invalidating the corresponding entry in the 3405 adspConnTable. That is, it effectively disassociates 3406 the mapping identified with said entry. It is an 3407 implementation-specific matter as to whether the agent 3408 removes an invalidated entry from the table. 3409 Accordingly, management stations must be prepared to 3410 receive from agents tabular information corresponding 3411 to entries not currently in use. Proper 3412 interpretation of such entries requires examination 3413 of the relevant adspConnState object." 3414 ::= { adspConnEntry 5 } 3416 -- The ATPortPtoP Group 3417 -- 3418 -- Implementation of this group is mandatory for all entities that 3419 -- implement AppleTalk point-to-point links 3420 -- 3421 -- As an example, an instance of the atportPtoPRemoteAddress object 3422 -- might be named atportPtoPRemoteAddress.2 3424 atportPtoPTable OBJECT-TYPE 3425 SYNTAX SEQUENCE OF AtportPtoPEntry 3426 ACCESS not-accessible 3427 STATUS mandatory 3428 DESCRIPTION 3429 "A list of AppleTalk point-to-point connections for 3430 this entity." 3431 ::= { atportptop 1 } 3433 atportPtoPEntry OBJECT-TYPE 3434 SYNTAX AtportPtoPEntry 3435 ACCESS not-accessible 3436 STATUS mandatory 3437 DESCRIPTION 3438 "The description of one of the AppleTalk point-to-point 3439 connections on this entity." 3440 INDEX { atportPtoPIndex } 3441 ::= { atportPtoPTable 1 } 3443 AtportPtoPEntry ::= SEQUENCE { 3444 atportPtoPIndex INTEGER, 3445 atportPtoPProtocol OBJECT IDENTIFIER, 3446 atportPtoPRemoteName DisplayString, 3447 atportPtoPRemoteAddress OCTET STRING, 3448 atportPtoPPortIndex INTEGER, 3449 atportPtoPStatus INTEGER 3450 } 3452 atportPtoPIndex OBJECT-TYPE 3453 SYNTAX INTEGER 3454 ACCESS not-accessible 3455 STATUS mandatory 3456 DESCRIPTION 3457 "A unique value for each AppleTalk point-to-point 3458 connection. Its value is between 1 and the total 3459 number of AppleTalk point-to-point connections. The 3460 value for each connection must remain constant at 3461 least from the re-initialization of the entity's 3462 network management system to the next re-initialization." 3463 ::= { atportPtoPEntry 1 } 3465 atportPtoPProtocol OBJECT-TYPE 3466 SYNTAX OBJECT IDENTIFIER 3467 ACCESS read-write 3468 STATUS mandatory 3469 DESCRIPTION 3470 "The protocol type used over the point-to-point 3471 connection." 3472 ::= { atportPtoPEntry 2 } 3474 atportPtoPRemoteName OBJECT-TYPE 3475 SYNTAX DisplayString 3476 ACCESS read-write 3477 STATUS mandatory 3478 DESCRIPTION 3479 "A text string containing the network node name of the 3480 entity at the other end of the point-to-point link. 3481 If the name is unknown or undefined, then this string is 3482 zero length." 3483 ::= { atportPtoPEntry 3 } 3485 atportPtoPRemoteAddress OBJECT-TYPE 3486 SYNTAX OCTET STRING 3487 ACCESS read-write 3488 STATUS mandatory 3489 DESCRIPTION 3490 "The network address of the entity at the other end 3491 of the point-to-point link in network byte order. 3492 The format of this address can be determined 3493 by examinating the atportType corresponding to this 3494 entry. If the address is unknown or undefined, then this 3495 string is zero length." 3496 ::= { atportPtoPEntry 4 } 3498 atportPtoPPortIndex OBJECT-TYPE 3499 SYNTAX INTEGER 3500 ACCESS read-write 3501 STATUS mandatory 3502 DESCRIPTION 3503 "The AppleTalk port associated with this point-to-point 3504 connection. The interface identified by a particular 3505 value of this index is the same interface as identified 3506 by the same value of atportIndex." 3507 ::= { atportPtoPEntry 5 } 3509 atportPtoPStatus OBJECT-TYPE 3510 SYNTAX INTEGER { 3511 valid(1), 3512 invalid(2) 3513 } 3514 ACCESS read-write 3515 STATUS mandatory 3516 DESCRIPTION 3517 "The status of this entry in the atportPtoPTable. 3519 Setting this object to the value invalid(2) has the 3520 effect of invalidating the corresponding entry in the 3521 atportPtoPTable. That is, it effectively disassociates 3522 the mapping identified with said entry. It is an 3523 implementation-specific matter as to whether the agent 3524 removes an invalidated entry from the table. 3525 Accordingly, management stations must be prepared to 3526 receive from agents tabular information corresponding 3527 to entries not currently in use. Proper 3528 interpretation of such entries requires examination 3529 of the relevant atportPtoPStatus object." 3530 ::= { atportPtoPEntry 6 } 3532 atportPtoPProtoOids OBJECT IDENTIFIER ::= { atportptop 2 } 3534 -- A list of values to be used for the atportPtoPProtocol variable. 3535 -- When new protocols are defined, their oids may be defined in 3536 -- separate MIB documents in different branches of the tree. 3538 pToPProtoOther OBJECT IDENTIFIER ::= { atportPtoPProtoOids 1 } 3539 pToPProtoAurp OBJECT IDENTIFIER ::= { atportPtoPProtoOids 2 } 3540 pToPProtoCaymanUdp OBJECT IDENTIFIER ::= 3541 { atportPtoPProtoOids 3 } 3542 pToPProtoAtkvmsDecnetIV OBJECT IDENTIFIER ::= 3543 { atportPtoPProtoOids 4 } 3544 pToPProtoLiaisonUdp OBJECT IDENTIFIER ::= 3545 { atportPtoPProtoOids 5 } 3546 pToPProtoIpx OBJECT IDENTIFIER ::= { atportPtoPProtoOids 6 } 3547 pToPProtoShivaIp OBJECT IDENTIFIER ::= { atportPtoPProtoOids 7 } 3548 -- The Per Port Counters Group 3549 -- 3550 -- Implementation of this group is optional. 3551 -- 3552 -- As an example, an instance of the perPortAarpInProbes object 3553 -- might be named perPortAarpInProbes.2 3555 perPortTable OBJECT-TYPE 3556 SYNTAX SEQUENCE OF PerPortEntry 3557 ACCESS not-accessible 3558 STATUS mandatory 3559 DESCRIPTION 3560 "The table of per-port statistics for this entity." 3561 ::= { perPort 1 } 3563 perPortEntry OBJECT-TYPE 3564 SYNTAX PerPortEntry 3565 ACCESS not-accessible 3566 STATUS mandatory 3567 DESCRIPTION 3568 "The statistics available for a particular port on 3569 this entity." 3570 INDEX { atportIndex } 3571 ::= { perPortTable 1 } 3573 PerPortEntry ::= SEQUENCE { 3574 perPortAarpInProbes Counter, 3575 perPortAarpOutProbes Counter, 3576 perPortAarpInReqs Counter, 3577 perPortAarpOutReqs Counter, 3578 perPortAarpInRsps Counter, 3579 perPortAarpOutRsps Counter, 3580 perPortDdpInReceives Counter, 3581 perPortDdpInLocalDatagrams Counter, 3582 perPortDdpNoProtocolHandlers Counter, 3583 perPortDdpTooShortErrors Counter, 3584 perPortDdpTooLongErrors Counter, 3585 perPortDdpChecksumErrors Counter, 3586 perPortDdpForwRequests Counter, 3587 perPortRtmpInDataPkts Counter, 3588 perPortRtmpOutDataPkts Counter, 3589 perPortRtmpInRequestPkts Counter, 3590 perPortRtmpRouteDeletes Counter, 3591 perPortZipInZipQueries Counter, 3592 perPortZipInZipReplies Counter, 3593 perPortZipInZipExtendedReplies Counter, 3594 perPortZipZoneConflictErrors Counter, 3595 perPortZipInErrors Counter, 3596 perPortNbpInLookUpRequests Counter, 3597 perPortNbpInLookUpReplies Counter, 3598 perPortNbpInBroadcastRequests Counter, 3599 perPortNbpInForwardRequests Counter, 3600 perPortNbpOutLookUpReplies Counter, 3601 perPortNbpRegistrationFailures Counter, 3602 perPortNbpInErrors Counter, 3603 perPortEchoRequests Counter, 3604 perPortEchoReplies Counter 3605 } 3607 perPortAarpInProbes OBJECT-TYPE 3608 SYNTAX Counter 3609 ACCESS read-only 3610 STATUS mandatory 3611 DESCRIPTION 3612 "The total number of AARP Probe packets received 3613 by this entity on this port." 3614 ::= { perPortEntry 1 } 3616 perPortAarpOutProbes OBJECT-TYPE 3617 SYNTAX Counter 3618 ACCESS read-only 3619 STATUS mandatory 3620 DESCRIPTION 3621 "The total number of AARP Probe packets sent by 3622 this entity on this port." 3623 ::= { perPortEntry 2 } 3625 perPortAarpInReqs OBJECT-TYPE 3626 SYNTAX Counter 3627 ACCESS read-only 3628 STATUS mandatory 3629 DESCRIPTION 3630 "The total number of AARP Request packets received 3631 by this entity on this port." 3632 ::= { perPortEntry 3 } 3634 perPortAarpOutReqs OBJECT-TYPE 3635 SYNTAX Counter 3636 ACCESS read-only 3637 STATUS mandatory 3638 DESCRIPTION 3639 "The total number of AARP Request packets sent by 3640 this entity on this port." 3641 ::= { perPortEntry 4 } 3643 perPortAarpInRsps OBJECT-TYPE 3644 SYNTAX Counter 3645 ACCESS read-only 3646 STATUS mandatory 3647 DESCRIPTION 3648 "The total number of AARP Response packets received 3649 by this entity on this port." 3650 ::= { perPortEntry 5 } 3652 perPortAarpOutRsps OBJECT-TYPE 3653 SYNTAX Counter 3654 ACCESS read-only 3655 STATUS mandatory 3656 DESCRIPTION 3657 "The total number of AARP Response packets sent by 3658 this entity on this port." 3659 ::= { perPortEntry 6 } 3661 perPortDdpInReceives OBJECT-TYPE 3662 SYNTAX Counter 3663 ACCESS read-only 3664 STATUS mandatory 3665 DESCRIPTION 3666 "The total number of input datagrams received by DDP on 3667 this port, including those received in error." 3668 ::= { perPortEntry 7 } 3670 perPortDdpInLocalDatagrams OBJECT-TYPE 3671 SYNTAX Counter 3672 ACCESS read-only 3673 STATUS mandatory 3674 DESCRIPTION 3675 "The total number of input DDP datagrams on this port for 3676 which this entity was their final DDP destination." 3677 ::= { perPortEntry 8 } 3679 perPortDdpNoProtocolHandlers OBJECT-TYPE 3680 SYNTAX Counter 3681 ACCESS read-only 3682 STATUS mandatory 3683 DESCRIPTION 3684 "The total number of DDP datagrams addressed to this 3685 entity on this port that were addressed to an upper 3686 layer protocol for which no protocol handler existed." 3687 ::= { perPortEntry 9 } 3689 perPortDdpTooShortErrors OBJECT-TYPE 3690 SYNTAX Counter 3691 ACCESS read-only 3692 STATUS mandatory 3693 DESCRIPTION 3694 "The total number of input DDP datagrams on this port 3695 dropped because the received data length was less than 3696 the data length specified in the DDP header or the 3697 received data length was less than the length of the 3698 expected DDP header." 3699 ::= { perPortEntry 10 } 3701 perPortDdpTooLongErrors OBJECT-TYPE 3702 SYNTAX Counter 3703 ACCESS read-only 3704 STATUS mandatory 3705 DESCRIPTION 3706 "The total number of input DDP datagrams on this port 3707 dropped because they exceeded the maximum DDP datagram 3708 size." 3709 ::= { perPortEntry 11 } 3711 perPortDdpChecksumErrors OBJECT-TYPE 3712 SYNTAX Counter 3713 ACCESS read-only 3714 STATUS mandatory 3715 DESCRIPTION 3716 "The total number of input DDP datagrams on this port 3717 for which this DDP entity was their final destination, 3718 and which were dropped because of a checksum error." 3719 ::= { perPortEntry 12 } 3721 perPortDdpForwRequests OBJECT-TYPE 3722 SYNTAX Counter 3723 ACCESS read-only 3724 STATUS mandatory 3725 DESCRIPTION 3726 "The number of input datagrams on this port for which 3727 this entity was not their final DDP destination, as a 3728 result of which an attempt was made to find a route to 3729 forward them to that final destination." 3730 ::= { perPortEntry 13 } 3732 perPortRtmpInDataPkts OBJECT-TYPE 3733 SYNTAX Counter 3734 ACCESS read-only 3735 STATUS mandatory 3736 DESCRIPTION 3737 "A count of the number of good RTMP data packets 3738 received by this entity on this port." 3739 ::= { perPortEntry 14 } 3741 perPortRtmpOutDataPkts OBJECT-TYPE 3742 SYNTAX Counter 3743 ACCESS read-only 3744 STATUS mandatory 3745 DESCRIPTION 3746 "A count of the number of RTMP packets sent by this 3747 entity on this port." 3748 ::= { perPortEntry 15 } 3750 perPortRtmpInRequestPkts OBJECT-TYPE 3751 SYNTAX Counter 3752 ACCESS read-only 3753 STATUS mandatory 3754 DESCRIPTION 3755 "A count of the number of good RTMP Request packets 3756 received by this entity on this port." 3757 ::= { perPortEntry 16 } 3759 perPortRtmpRouteDeletes OBJECT-TYPE 3760 SYNTAX Counter 3761 ACCESS read-only 3762 STATUS mandatory 3763 DESCRIPTION 3764 "A count of the number of times RTMP deletes a route 3765 on this port because it was aged out of the table." 3766 ::= { perPortEntry 17 } 3768 perPortZipInZipQueries OBJECT-TYPE 3769 SYNTAX Counter 3770 ACCESS read-only 3771 STATUS mandatory 3772 DESCRIPTION 3773 "The number of ZIP Queries received by this entity 3774 on this port." 3775 ::= { perPortEntry 18 } 3777 perPortZipInZipReplies OBJECT-TYPE 3778 SYNTAX Counter 3779 ACCESS read-only 3780 STATUS mandatory 3781 DESCRIPTION 3782 "The number of ZIP Replies received by this entity 3783 on this port." 3784 ::= { perPortEntry 19 } 3786 perPortZipInZipExtendedReplies OBJECT-TYPE 3787 SYNTAX Counter 3788 ACCESS read-only 3789 STATUS mandatory 3790 DESCRIPTION 3791 "The number of ZIP Extended Replies received by this 3792 entity on this port." 3793 ::= { perPortEntry 20 } 3795 perPortZipZoneConflictErrors OBJECT-TYPE 3796 SYNTAX Counter 3797 ACCESS read-only 3798 STATUS mandatory 3799 DESCRIPTION 3800 "The number of times a conflict has been detected on 3801 this port between this entity's zone information and 3802 another entity's zone information." 3803 ::= { perPortEntry 21 } 3805 perPortZipInErrors OBJECT-TYPE 3806 SYNTAX Counter 3807 ACCESS read-only 3808 STATUS mandatory 3809 DESCRIPTION 3810 "The number of ZIP packets received by this entity 3811 on this port that were rejected for any error." 3812 ::= { perPortEntry 22 } 3814 perPortNbpInLookUpRequests OBJECT-TYPE 3815 SYNTAX Counter 3816 ACCESS read-only 3817 STATUS mandatory 3818 DESCRIPTION 3819 "The number of NBP LookUp Requests received on this 3820 port." 3821 ::= { perPortEntry 23 } 3823 perPortNbpInLookUpReplies OBJECT-TYPE 3824 SYNTAX Counter 3825 ACCESS read-only 3826 STATUS mandatory 3827 DESCRIPTION 3828 "The number of NBP LookUp Replies received on this port." 3829 ::= { perPortEntry 24 } 3831 perPortNbpInBroadcastRequests OBJECT-TYPE 3832 SYNTAX Counter 3833 ACCESS read-only 3834 STATUS mandatory 3835 DESCRIPTION 3836 "The number of NBP Broadcast Requests received on this 3837 port." 3838 ::= { perPortEntry 25 } 3840 perPortNbpInForwardRequests OBJECT-TYPE 3841 SYNTAX Counter 3842 ACCESS read-only 3843 STATUS mandatory 3844 DESCRIPTION 3845 "The number of NBP Forward Requests received on this port." 3846 ::= { perPortEntry 26 } 3848 perPortNbpOutLookUpReplies OBJECT-TYPE 3849 SYNTAX Counter 3850 ACCESS read-only 3851 STATUS mandatory 3852 DESCRIPTION 3853 "The number of NBP LookUp Replies sent on this port." 3854 ::= { perPortEntry 27 } 3856 perPortNbpRegistrationFailures OBJECT-TYPE 3857 SYNTAX Counter 3858 ACCESS read-only 3859 STATUS mandatory 3860 DESCRIPTION 3861 "The number of times this node experienced a failure in 3862 attempting to register an NBP entity on this port." 3863 ::= { perPortEntry 28 } 3865 perPortNbpInErrors OBJECT-TYPE 3866 SYNTAX Counter 3867 ACCESS read-only 3868 STATUS mandatory 3869 DESCRIPTION 3870 "The number of NBP packets received by this entity on this 3871 port that were rejected for any error." 3872 ::= { perPortEntry 29 } 3874 perPortEchoRequests OBJECT-TYPE 3875 SYNTAX Counter 3876 ACCESS read-only 3877 STATUS mandatory 3878 DESCRIPTION 3879 "The number of AppleTalk Echo requests received on this 3880 port." 3881 ::= { perPortEntry 30 } 3883 perPortEchoReplies OBJECT-TYPE 3884 SYNTAX Counter 3885 ACCESS read-only 3886 STATUS mandatory 3887 DESCRIPTION 3888 "The count of AppleTalk Echo replies received on this port." 3889 ::= { perPortEntry 31 } 3891 END 3892 8. Acknowledgments 3894 This document was produced by the IETF AppleTalk-IP Working 3895 Group: 3897 XXX 3899 In addition, the contribution of the following individuals is 3900 also acknowledged: 3902 Greg Minshall, Novell, Inc. 3903 Marshall T. Rose, PSI 3905 9. References 3907 [1] V. Cerf, IAB Recommendations for the Development of 3908 Internet Network Management Standards. Internet Working 3909 Group Request for Comments 1052. Network Information 3910 Center, SRI International, Menlo Park, California, 3911 (April, 1988). 3913 [2] V. Cerf, Report of the Second Ad Hoc Network Management 3914 Review Group, Internet Working Group Request for Comments 3915 1109. Network Information Center, SRI International, 3916 Menlo Park, California, (August, 1989). 3918 [3] M.T. Rose and K. McCloghrie, Structure and Identification 3919 of Management Information for TCP/IP-based internets, 3920 Internet Working Group Request for Comments 1155. 3921 Network Information Center, SRI International, Menlo 3922 Park, California, (May, 1990). 3924 [4] K. McCloghrie and M.T. Rose, Management Information Base 3925 for Network Management of TCP/IP-based internets, 3926 Internet Working Group Request for Comments 1156. 3927 Network Information Center, SRI International, Menlo 3928 Park, California, (May, 1990). 3930 [5] J.D. Case, M.S. Fedor, M.L. Schoffstall, and J.R. Davin, 3931 Simple Network Management Protocol, Internet Working 3932 Group Request for Comments 1157. Network Information 3933 Center, SRI International, Menlo Park, California, (May, 3934 1990). 3936 [6] M.T. Rose (editor), Management Information Base for 3937 Network Management of TCP/IP-based internets, Internet 3938 Working Group Request for Comments 1158. Network 3939 Information Center, SRI International, Menlo Park, 3940 California, (May, 1990). 3942 [7] Information processing systems - Open Systems 3943 Interconnection - Specification of Abstract Syntax 3944 Notation One (ASN.1), International Organization for 3945 Standardization. International Standard 8824, (December, 3946 1987). 3948 [8] Information processing systems - Open Systems 3949 Interconnection - Specification of Basic Encoding Rules 3950 for Abstract Notation One (ASN.1), International 3951 Organization for Standardization. International Standard 3952 8825, (December, 1987). 3954 [9] M.T. Rose, K. McCloghrie (editors), Concise MIB 3955 Definitions, Internet Working Group Request for Comments 3956 1212. Network Information Center, SRI International, 3957 Menlo Park, California, (March, 1991). 3959 [10] Gursharan S. Sidhu, Richard F. Andrews, and 3960 Alan B. Oppenheimer, Inside AppleTalk, Second Edition, 3961 Addison Wesley, (1990). 3963 Expiration Date: November 5, 1993 3964 9 References ............................................ 99