idnits 2.17.1 draft-ietf-x25mib-ipox25mib-04.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-24) 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. ** The abstract seems to contain references ([2], [3], [4], [5], [6], [7], [8], [9], [10], [11], [1]), which it shouldn't. Please replace those with straight textual mentions of the documents in question. Miscellaneous warnings: ---------------------------------------------------------------------------- == Line 62 has weird spacing: '...EncType wer...' == Line 162 has weird spacing: '...ailures and...' == Line 164 has weird spacing: '...Address and...' == 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 (January 11, 1993) is 11426 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 1132 looks like a reference -- Missing reference section? '4' on line 1148 looks like a reference -- Missing reference section? '2' on line 1137 looks like a reference -- Missing reference section? '5' on line 1152 looks like a reference -- Missing reference section? '3' on line 1142 looks like a reference -- Missing reference section? '6' on line 1156 looks like a reference -- Missing reference section? '7' on line 1162 looks like a reference -- Missing reference section? '11' on line 1180 looks like a reference -- Missing reference section? '8' on line 1168 looks like a reference -- Missing reference section? '9' on line 1172 looks like a reference -- Missing reference section? '10' on line 1176 looks like a reference Summary: 15 errors (**), 0 flaws (~~), 5 warnings (==), 12 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 SNMP MIB extension for Multiprotocol Interconnect over X.25 3 January 11, 1993 5 Dean D. Throop 7 Data General Corporation 8 62 Alexander Dr. 9 Research Triangle Park, NC 27709 11 throop@dg-rtp.dg.com 13 1. Status of this Memo 15 This document is an Internet Draft. Internet Drafts are 16 working documents of the Internet Engineering Task Force 17 (IETF), its Areas, and its Working Groups. Note that other 18 groups may also distribute working documents as Internet 19 Drafts). 21 Internet Drafts are draft documents valid for a maximum of six 22 months. Internet Drafts may be updated, replaced, or obsoleted 23 by other documents at any time. It is not appropriate to use 24 Internet Drafts as reference material or to cite them other 25 than as a "working draft" or "work in progress." 27 Please check the I-D abstract listing contained in each 28 Internet Draft directory to learn the current status of this 29 or any other Internet Draft. 31 This document was produced by the x25mib working group in 32 conjunction with the Large Public Data Networks Working Group. 33 Eventually this document will be submitted to the RFC editor 34 as an extension to the SNMP MIB. Distribution of this memo is 35 unlimited. Please send comments to the x25mib working group 36 at: 38 x25mib@dg-rtp.dg.com 40 1.1. Revision History 42 January 1993 44 The January 1993 release (Editor's Internal Reference Number 45 2.13) incorporated the following comments from the SNMP 46 directorate: 48 The overview section was expanded to have two subsections 49 to better state the relationship this MIB has with RFC 50 1356. The MIB Context subsection was added. 52 Object grouping was clarified by introducing the mioxPle 53 and mioxPeer object identifiers and text was added to 54 identify all objects as required. 56 A conformance statement was added for the mioxPeerStatus 57 object and the mioxPeerX25CircuitId object. 59 The descriptions of mioxPleRefusedConnections, 60 mioxPleEnAddrToX121LkupFlrs, mioxPleX121ToEnAddrLkupFlrs, 61 mioxPleCollisionRetryTimer, mioxPeerX25CallParamId, 62 mioxPeerX25CircuitId, mioxPeerEncType were changed to 63 improve clarity. 65 Obsolete references were updated to new references as 66 appropriate. 68 Some minor typographical errors were corrected. 70 June 1992 72 The June 1992 release (Editor's Internal Reference Number 2.4) 73 incorporated several comments of the mailing list. These 74 changes are as follows: 76 The range and description of mioxPleMaxCircuits was 77 expanded. 79 The following objects were added: 80 mioxPleEnAddrToX121LkupFlrTime, 81 mioxPleX121ToEnAddrLkupFlrTime, mioxPleQbitFailures, 82 mioxPleQbitFailureRemoteAddress, mioxPleQbitFailureTime, 83 mioxPleMinimumOpenTimer, mioxPleInactivityTimer, 84 mioxPleHoldDownTimer, mioxPleCollisionRetryTimer. 86 The following objects were deleted: 87 mioxPeerMinimumOpenTimer, mioxPeerHoldDownTimer, 88 mioxPeerQbitErrors. 90 May 1992 92 The April 1992 release (Editor's Internal Reference Number 93 2.2) incorporated the comments of the March working group 94 meeting. These changes are as follows: 96 The overview section was expanded to better explain the 97 relationship between the objects defined in this MIB and 98 other MIB extensions. 100 The name of the MIB was change from IP over X.25 to 101 Multiprotocol Interconnect over X.25. 103 All references to IP addresses were changed to 104 Encapsulation Addresses. 106 All references to X25Address were changed to X121Address. 108 The ioxInfoTable was renamed the mioxPleTable because it 109 contains information relative to a PLE. 111 The ioxConTable was renamed the mioxPeerTable. 113 The mioxPeerStatus object was added. 115 The mioxPeerMaxCircuits object was added. 117 The mioxPeerIfIndex object was added. 119 The mioxPeerQbitErrors object was added. 121 The mioxPeerConnectSeconds object was added. 123 The mioxPeerDescr object was added. 125 The mioxPeerEncTable was added. 127 Some objects were re-ordered and some descriptions were 128 expanded. 130 February 1992 132 The February 1992 release (Editor's Internal Reference Number 133 1.17) made the following changes: 135 The ioxInfoDefaultParamId object was added to the 136 ioxInfoTable. 138 The ioxConX25Channel object was deleted from the 139 ioxConTable and replaced with the ioxConX25CircuitId 140 object. 142 The ioxConX25Address object was added to the ioxConTable. 144 The ioxConX25FcltyIndex, ioxConX25fcltyCcittIndex, and 145 ioxConX25CallParamIndex objects were deleted from the 146 ioxConTable and replaced with the ioxConX25CallParamId 147 object. 149 The ioxConEncapsulation and ioxConHoldDownTimer objects 150 were added to the ioxConTable. 152 The text at the beginning of the document was changed. 154 The references were changed to match the new text. 156 October 1991 158 The October 91 revision of this document (Editor's internal 159 reference 1.14) had the following changes: 161 The object ioxInfoAddressXlationFailures was split into 162 ioxInfoIpToX25LookupFailures and 163 ioxInfoX25ToIpLookupFailures. The objects 164 ioxInfoLastFailedIpAddress and 165 ioxInfoLastFailedX25Address were added. This provides 166 information to allow for correction of errors as well as 167 detection. 169 The objects ioxConX25FcltyIndex, 170 ioxConX25fcltyCcittIndex, and ioxConX25CallParamIndex 171 were added. 173 June 1991 175 The June revision of this document was synthesized from 176 various ideas on how to manage IP over X.25. This initial 177 release of this document serves as a basis of discussion in 178 the X25mib working group. 180 2. Abstract 182 This memo defines a portion of the Management Information Base 183 (MIB) for use with network management protocols in TCP/IP- 184 based internets. In particular, it defines objects for 185 managing Multiprotocol Interconnect (including IP) traffic 186 carried over X.25. The objects defined here, along with the 187 objects in the "SNMP MIB extension for the Packet Layer of 188 X.25"[10], "SNMP MIB extension for LAPB"[9], and the 189 "Definitions of Managed Objects for RS-232-like Hardware 190 Devices"[8], combine to allow management of the traffic over 191 an X.25 protocol stack. 193 This memo does not specify a standard for the Internet 194 community. 196 3. The Network Management Framework 198 The Internet-standard Network Management Framework consists of 199 three components. These components give the rules for 200 defining objects, the definitions of objects, and the protocol 201 for manipulating objects. 203 The network management framework structures objects in an 204 abstract information tree. The branches of the tree name 205 objects and the leaves of the tree contain the values 206 manipulated to effect management. This tree is called the 207 Management Information Base or MIB. The concepts of this tree 208 are given in RFC 1155 "The Structure of Management 209 Information" or SMI [1]. The SMI defines the trunk of the tree 210 and the types of objects used when defining the leaves. RFC 211 1212, "Towards Concise MIB Definitions" [4], defines a more 212 concise description mechanism that preserves all the 213 principals of the SMI. 215 The core MIB definitions for the Internet suite of protocols 216 can be found in RFC 1156 [2] "Management Information Base for 217 Network Management of TCP/IP-based internets". RFC 1213 [5] 218 defines MIB-II, an evolution of MIB-I with changes to 219 incorporate implementation experience and new operational 220 requirements. 222 RFC 1157 [3] defines the SNMP protocol itself. The protocol 223 defines how to manipulate the objects in a remote MIB. 225 The tree structure of the MIB allows new objects to be defined 226 for the purpose of experimentation and evaluation. 228 4. Objects 230 The definition of an object in the MIB requires an object name 231 and type. Object names and types are defined using the subset 232 of Abstract Syntax Notation One (ASN.1) [6] defined in the SMI 233 [1]. Objects are named using ASN.1 object identifiers, 234 administratively assigned names, to specify object types. The 235 object name, together with an optional object instance, 236 uniquely identifies a specific instance of an object. For 237 human convenience, we often use a textual string, termed the 238 OBJECT DESCRIPTOR, to also refer to objects. 240 Objects also have a syntax that defines the abstract data 241 structure corresponding to that object type. The ASN.1 242 language [6] provides the primitives used for this purpose. 243 The SMI [1] purposely restricts the ASN.1 constructs which may 244 be used for simplicity and ease of implementation. The 245 encoding of an object type simply describes how to represent 246 an object using ASN.1 encoding rules [7], for purposes of 247 dealing with the SNMP protocol. 249 4.1. Format of Definitions 251 Section 6 contains the specification of all object types 252 contained in this MIB module. The object types are defined 253 using the conventions defined in the SMI, as amended by the 254 extensions specified in "Towards Concise MIB Definitions" [4]. 256 5. Overview 258 5.1. MIB Context 260 Instances of the objects defined below provide management 261 information for Multiprotocol Interconnect traffic on X.25 as 262 defined in RFC 1356 [11]. That RFC describes how X.25 can be 263 used to exchange IP or network level protocols. The 264 multiprotocol packets (IP, CLNP, ES-IS, or SNAP) are 265 encapsulated in X.25 frames for transmission between nodes. 266 All nodes that implement RFC 1356 must implement this MIB. 268 The objects in this MIB apply to the software in the node that 269 manages X.25 connections and performs the protocol 270 encapsulation. A node in this usage maybe the end node source 271 or destination host for the packet, or it may be a router or 272 bridge responsible for forwarding the packet. Since RFC 1356 273 requires X.25, nodes that implement RFC 1356 must also 274 implement the X.25 MIB, RFC 1382. 276 This MIB only applies to Multiprotocol Interconnect over X.25 277 service. It does not apply to other software that may also use 278 X.25 (for example PAD). Thus the presence, absence, or 279 operation of such software will not directly affect any of 280 these objects. (However connections in use by that software 281 will appear in the X.25 MIB). 283 5.2. Structure of MIB objects 285 The objects of this MIB are organized into three tables: the 286 mioxPleTable, the mioxPeerTable, and the mioxPeerEncTable. 287 All objects in all tables are mandatory for conformance with 288 this MIB. 290 The mioxPleTable defines information relative to an interface 291 used to carry Multiprotocol Interconnect traffic over X.25. 292 Such interfaces are identified by an ifType object in the 293 Internet-standard MIB [5] of ddn-x25 or rfc877-x25. 294 Interfaces of type ddn-x25 have a self contained algorithm for 295 translating between IP addresses and X.121 addresses. 296 Interfaces of type rfc877-x25 do not have such an algorithm. 297 Note that not all X.25 Interfaces will be used to carry 298 Multiprotocol Interconnect traffic. Those interfaces not 299 carrying such traffic will not have entries in the 300 mioxPleTable. The entries in the mioxPleTable are only for 301 interfaces that do carry Multiprotocol Interconnect traffic 302 over X.25. Interfaces that do have entries in the 303 mioxPleTable have mioxPleIndex object instance identifiers 304 that match the values of their respective ifIndex object 305 instance identifiers. This relationship allows the value of 306 an index object instance from the mioxPleTable below to be 307 directly used to identify the corresponding instances of the 308 objects for the interface to X.25. 310 The mioxPeerTable contains information needed to contact an 311 X.25 Peer to exchange packets. This includes information such 312 as the X.121 address of the peer and a pointer to the X.25 313 call parameters needed to place the call. The instance 314 identifiers used for the objects in this table are independent 315 of any interface or other tables defined outside this MIB. 316 This table contains the ifIndex value of the X.25 interface to 317 use to call a peer. 319 The mioxPeerEncTable contains information about the 320 encapsulation type used to communicate with a peer. This 321 table is an extension of the mioxPeerTable in its instance 322 identification. Each entry in the mioxPeerTable may have zero 323 or more entries in this table. This table will not have any 324 entries that do not have correspondent entries in 325 mioxPeerTable. 327 6. Definitions 329 RFCmiox-MIB DEFINITIONS ::= BEGIN 330 -- (Editors Internal Reference 2.42) 332 IMPORTS 333 Counter, 334 experimental, 335 TimeTicks 336 FROM RFC1155-SMI 337 OBJECT-TYPE 338 FROM RFC-1212 339 DisplayString 340 FROM RFC1213-MIB 341 X121Address 342 FROM RFC1382-MIB 343 PositiveInteger 344 FROM RFC1381-MIB; 346 -- IP over X.25 MIB 348 -- DO NOT USE THIS EXPERIMENTAL NUMBER. 349 miox OBJECT IDENTIFIER ::= { experimental 12345678 } 350 -- This experimental number is an 351 -- invalid placeholder. 352 -- DO NOT USE THIS EXPERIMENTAL NUMBER. 354 mioxPle OBJECT IDENTIFIER ::= { miox 1 } 355 mioxPeer OBJECT IDENTIFIER ::= { miox 2 } 357 -- ########################################################### 358 -- Ple Table 359 -- ########################################################### 361 -- Systems that implement RFC 1356 must also implement 362 -- all objects in this group. 364 mioxPleTable OBJECT-TYPE 365 SYNTAX SEQUENCE OF MioxPleEntry 366 ACCESS not-accessible 367 STATUS mandatory 368 DESCRIPTION 369 "This table contains information relative to 370 an interface to an X.25 Packet Level Entity 372 (PLE)." 373 ::= { mioxPle 1 } 375 mioxPleEntry OBJECT-TYPE 376 SYNTAX MioxPleEntry 377 ACCESS not-accessible 378 STATUS mandatory 379 DESCRIPTION 380 "These objects manage the encapsulation of 381 other protocols within X.25." 382 INDEX { mioxPleIndex } 383 ::= { mioxPleTable 1 } 385 MioxPleEntry ::= SEQUENCE { 386 mioxPleIndex 387 PositiveInteger, 388 mioxPleMaxCircuits 389 INTEGER, 390 mioxPleRefusedConnections 391 Counter, 392 mioxPleEnAddrToX121LkupFlrs 393 Counter, 394 mioxPleLastFailedEnAddr 395 OCTET STRING, 396 mioxPleEnAddrToX121LkupFlrTime 397 TimeTicks, 398 mioxPleX121ToEnAddrLkupFlrs 399 Counter, 400 mioxPleLastFailedX121Address 401 X121Address, 402 mioxPleX121ToEnAddrLkupFlrTime 403 TimeTicks, 404 mioxPleQbitFailures 405 Counter, 406 mioxPleQbitFailureRemoteAddress 407 X121Address, 408 mioxPleQbitFailureTime 409 TimeTicks, 410 mioxPleMinimumOpenTimer 411 PositiveInteger, 412 mioxPleInactivityTimer 413 PositiveInteger, 414 mioxPleHoldDownTimer 415 PositiveInteger, 416 mioxPleCollisionRetryTimer 417 PositiveInteger, 418 mioxPleDefaultPeerId 419 OBJECT IDENTIFIER 420 } 422 mioxPleIndex OBJECT-TYPE 423 SYNTAX PositiveInteger 424 ACCESS read-only 425 STATUS mandatory 426 DESCRIPTION 427 "An index value that uniquely identifies the 428 interface to X.25 used to send and receive 429 encapsulated Packets. This value will match 430 the ifIndex entry identifying the MIB-II 431 ifTable objects for that interface. This 432 value ranges between 1 and ifNumber." 433 ::= { mioxPleEntry 1 } 435 mioxPleMaxCircuits OBJECT-TYPE 436 SYNTAX INTEGER (0..2147483647) 437 ACCESS read-write 438 STATUS mandatory 439 DESCRIPTION 440 "The maximum number of X.25 circuits that 441 can be open at one time for this interface. 442 A value of zero indicates the interface will 443 not allow any additional circuits (as it may 444 soon be shutdown). A value of 2147483647 445 allows an unlimited number of circuits." 446 ::= { mioxPleEntry 2 } 448 mioxPleRefusedConnections OBJECT-TYPE 449 SYNTAX Counter 450 ACCESS read-only 451 STATUS mandatory 452 DESCRIPTION 453 "The number of X.25 calls from a remote 454 systems to this system that were cleared by 455 this system. The interface instance should 456 be that of the X.25 interface in call came 457 in on." 458 ::= { mioxPleEntry 3 } 460 mioxPleEnAddrToX121LkupFlrs OBJECT-TYPE 461 SYNTAX Counter 463 ACCESS read-only 464 STATUS mandatory 465 DESCRIPTION 466 "The number of times a translation from an 467 Encapsulated Address to an X.121 address 468 failed to find a corresponding X.121 469 address. Encapsulated addresses can be 470 looked up in the mioxPeerTable or translated 471 via an algorithm as for the DDN. Addresses 472 that are successfully recognized do not 473 increment this counter. Addresses that are 474 not recognized (reflecting an abnormal 475 packet delivery condition) increment this 476 counter. 478 If an address translation fails, it may be 479 difficult to determine which PLE entry 480 should count the failure. In such cases the 481 first likely entry in this table should be 482 selected. Agents should record the failure 483 even if they are unsure which PLE should be 484 associated with the failure." 485 ::= { mioxPleEntry 4 } 487 mioxPleLastFailedEnAddr OBJECT-TYPE 488 SYNTAX OCTET STRING (SIZE(2..128)) 489 ACCESS read-only 490 STATUS mandatory 491 DESCRIPTION 492 "The last Encapsulated address that failed 493 to find a corresponding X.121 address and 494 caused mioxPleEnAddrToX121LkupFlrs to be 495 incremented. The first octet of this object 496 contains the encapsulation type, the 497 remaining octets contain the address of that 498 type that failed. Thus for an IP address, 499 the length will be five octets, the first 500 octet will contain 204 (hex CC), and the 501 last four octets will contain the IP 502 address. For a snap encapsulation, the 503 first byte would be 128 (hex 80) and the 504 rest of the octet string would have the snap 505 header." 506 ::= { mioxPleEntry 5 } 508 mioxPleEnAddrToX121LkupFlrTime OBJECT-TYPE 509 SYNTAX TimeTicks 510 ACCESS read-only 511 STATUS mandatory 512 DESCRIPTION 513 "The most recent value of sysUpTime when the 514 translation from an Encapsulated Address to 515 X.121 address failed to find a corresponding 516 X.121 address." 517 ::= { mioxPleEntry 6 } 519 mioxPleX121ToEnAddrLkupFlrs OBJECT-TYPE 520 SYNTAX Counter 521 ACCESS read-only 522 STATUS mandatory 523 DESCRIPTION 524 "The number of times the translation from an 525 X.121 address to an Encapsulated Address 526 failed to find a corresponding Encapsulated 527 Address. Addresses successfully recognized 528 by an algorithm do not increment this 529 counter. This counter reflects the number 530 of times call acceptance encountered the 531 abnormal condition of not recognizing the 532 peer." 533 ::= { mioxPleEntry 7 } 535 mioxPleLastFailedX121Address OBJECT-TYPE 536 SYNTAX X121Address 537 ACCESS read-only 538 STATUS mandatory 539 DESCRIPTION 540 "The last X.121 address that caused 541 mioxPleX121ToEnAddrLkupFlrs to increase." 542 ::= { mioxPleEntry 8 } 544 mioxPleX121ToEnAddrLkupFlrTime OBJECT-TYPE 545 SYNTAX TimeTicks 546 ACCESS read-only 547 STATUS mandatory 548 DESCRIPTION 549 "The most recent value of sysUpTime when the 550 translation from an X.121 address to an 551 Encapsulated Address failed to find a 553 corresponding Encapsulated Address." 554 ::= { mioxPleEntry 9 } 556 mioxPleQbitFailures OBJECT-TYPE 557 SYNTAX Counter 558 ACCESS read-only 559 STATUS mandatory 560 DESCRIPTION 561 "The number of times a connection was closed 562 because of a Q-bit failure." 563 ::= { mioxPleEntry 10 } 565 mioxPleQbitFailureRemoteAddress OBJECT-TYPE 566 SYNTAX X121Address 567 ACCESS read-only 568 STATUS mandatory 569 DESCRIPTION 570 "The remote address of the most recent 571 (last) connection that was closed because of 572 a Q-bit failure." 573 ::= { mioxPleEntry 11 } 575 mioxPleQbitFailureTime OBJECT-TYPE 576 SYNTAX TimeTicks 577 ACCESS read-only 578 STATUS mandatory 579 DESCRIPTION 580 "The most recent value of sysUpTime when a 581 connection was closed because of a Q-bit 582 failure. This will also be the last time 583 that mioxPleQbitFailures was incremented." 584 ::= { mioxPleEntry 12 } 586 mioxPleMinimumOpenTimer OBJECT-TYPE 587 SYNTAX PositiveInteger 588 ACCESS read-write 589 STATUS mandatory 590 DESCRIPTION 591 "The minimum time in milliseconds this 592 interface will keep a connection open before 593 allowing it to be closed. A value of zero 594 indicates no timer." 595 DEFVAL { 0 } 596 ::= { mioxPleEntry 13 } 598 mioxPleInactivityTimer OBJECT-TYPE 599 SYNTAX PositiveInteger 600 ACCESS read-write 601 STATUS mandatory 602 DESCRIPTION 603 "The amount of time time in milliseconds 604 this interface will keep an idle connection 605 open before closing it. A value of 606 2147483647 indicates no timer." 607 DEFVAL { 10000 } 608 ::= { mioxPleEntry 14 } 610 mioxPleHoldDownTimer OBJECT-TYPE 611 SYNTAX PositiveInteger 612 ACCESS read-write 613 STATUS mandatory 614 DESCRIPTION 615 "The hold down timer in milliseconds. This 616 is the minimum amount of time to wait before 617 trying another call to a host that was 618 previously unsuccessful. A value of 619 2147483647 indicates the host will not be 620 retried." 621 DEFVAL { 0 } 622 ::= { mioxPleEntry 15 } 624 mioxPleCollisionRetryTimer OBJECT-TYPE 625 SYNTAX PositiveInteger 626 ACCESS read-write 627 STATUS mandatory 628 DESCRIPTION 629 "The Collision Retry Timer in milliseconds. 630 The time to delay between call attempts when 631 the maximum number of circuits is exceeded 632 in a call attempt." 633 DEFVAL { 0 } 634 ::= { mioxPleEntry 16 } 636 mioxPleDefaultPeerId OBJECT-TYPE 637 SYNTAX OBJECT IDENTIFIER 638 ACCESS read-write 639 STATUS mandatory 640 DESCRIPTION 641 "This identifies the instance of the index 643 in the mioxPeerTable for the default 644 parameters to use with this interface. 646 The entry identified by this object may have 647 a zero length Encapsulation address and a 648 zero length X.121 address. 650 These default parameters are used with 651 connections to hosts that do not have 652 entries in the mioxPeerTable. Such 653 connections occur when using ddn-x25 IP-X.25 654 address mapping or when accepting 655 connections from other hosts not in the 656 mioxPeerTable. 658 The mioxPeerEncTable entry with the same 659 index as the mioxPeerTable entry specifies 660 the call encapsulation types this PLE will 661 accept for peers not in the mioxPeerTable. 662 If the mioxPeerEncTable doesn't contain any 663 entries, this PLE will not accept calls from 664 entries not in the mioxPeerTable." 665 ::= { mioxPleEntry 17 } 667 -- ########################################################### 668 -- Peer Table 669 -- ########################################################### 671 -- Systems that implement RFC 1356 must also implement 672 -- all objects in this group. 674 mioxPeerTable OBJECT-TYPE 675 SYNTAX SEQUENCE OF MioxPeerEntry 676 ACCESS not-accessible 677 STATUS mandatory 678 DESCRIPTION 679 "This table contains information about the 680 possible peers this machine may exchange 681 packets with." 682 ::= { mioxPeer 1 } 684 mioxPeerEntry OBJECT-TYPE 685 SYNTAX MioxPeerEntry 686 ACCESS not-accessible 688 STATUS mandatory 689 DESCRIPTION 690 "Per peer information." 691 INDEX { mioxPeerIndex } 692 ::= { mioxPeerTable 1 } 694 MioxPeerEntry ::= SEQUENCE { 695 mioxPeerIndex 696 PositiveInteger, 697 mioxPeerStatus 698 INTEGER, 699 mioxPeerMaxCircuits 700 PositiveInteger, 701 mioxPeerIfIndex 702 PositiveInteger, 703 mioxPeerConnectSeconds 704 Counter, 705 mioxPeerX25CallParamId 706 OBJECT IDENTIFIER, 707 mioxPeerEnAddr 708 OCTET STRING, 709 mioxPeerX121Address 710 X121Address, 711 mioxPeerX25CircuitId 712 OBJECT IDENTIFIER, 713 mioxPeerDescr 714 DisplayString 715 } 717 mioxPeerIndex OBJECT-TYPE 718 SYNTAX PositiveInteger 719 ACCESS read-only 720 STATUS mandatory 721 DESCRIPTION 722 "An index value that distinguished one entry 723 from another. This index is independent of 724 any other index." 725 ::= { mioxPeerEntry 1 } 727 -- Systems can claim conformance with this MIB without 728 -- implementing sets to mioxPeerStatus with a value of 729 -- clearCall or makeCall. 730 -- All other defined values must be accepted. 731 -- Implementors should realize that allowing these values 732 -- provides richer system management and implementations 733 -- are encouraged to accept these values. 734 mioxPeerStatus OBJECT-TYPE 735 SYNTAX INTEGER { 736 valid (1), 737 createRequest (2), 738 underCreation (3), 739 invalid (4), 740 clearCall (5), 741 makeCall (6) 742 } 743 ACCESS read-write 744 STATUS mandatory 745 DESCRIPTION 746 "This reports the status of a peer entry. 748 A value of valid indicates a normal entry 749 that is in use by the agent. A value of 750 underCreation indicates a newly created 751 entry which isn't yet in use because the 752 creating management station is still setting 753 values. 755 The value of invalid indicates the entry is 756 no longer in use and the agent is free to 757 delete the entry at any time. A management 758 station is also free to use an entry in the 759 invalid state. 761 Entries are created by setting a value of 762 createRequest. Only non-existent or invalid 763 entries can be set to createRequest. Upon 764 receiving a valid createRequest, the agent 765 will create an entry in the underCreation 766 state. This object can not be set to a 767 value of underCreation directly, entries can 768 only be created by setting a value of 769 createRequest. Entries that exist in other 770 than the invalid state can not be set to 771 createRequest. 773 Entries with a value of underCreation are 774 not used by the system and the management 775 station can change the values of other 776 objects in the table entry. Management 778 stations should also remember to configure 779 values in the mioxPeerEncTable with the same 780 peer index value as this peer entry. 782 An entry in the underCreation state can be 783 set to valid or invalid. Entries in the 784 underCreation state will stay in that state 785 until 1) the agent times them out, 2) they 786 are set to valid, 3) they are set to 787 invalid. If an agent notices an entry has 788 been in the underCreation state for an 789 abnormally long time, it may decide the 790 management station has failed and invalidate 791 the entry. A prudent agent will understand 792 that the management station may need to wait 793 for human input and will allow for that 794 possibility in its determination of this 795 abnormally long period. 797 Once a management station has completed all 798 fields of an entry, it will set a value of 799 valid. This causes the entry to be 800 activated. 802 Entries in the valid state may also be set 803 to makeCall or clearCall to make or clear 804 X.25 calls to the peer. After such a set 805 request the entry will still be in the valid 806 state. Setting a value of makeCall causes 807 the agent to initiate an X.25 call request 808 to the peer specified by the entry. Setting 809 a value of clearCall causes the agent to 810 initiate clearing one X.25 call present to 811 the peer. Each set request will initiate 812 another call or clear request (up to the 813 maximum allowed); this means that management 814 stations that fail to get a response to a 815 set request should query to see if a call 816 was in fact placed or cleared before 817 retrying the request. Entries not in the 818 valid state can not be set to makeCall or 819 clearCall. 821 The values of makeCall an clearCall provide 822 for circuit control on devices which perform 824 Ethernet Bridging using static circuit 825 assignment without address recognition; 826 other devices which dynamically place calls 827 based on destination addresses may reject 828 such requests. 830 An agent that (re)creates a new entry 831 because of a set with createRequest, should 832 also (re)create a mioxPeerEncTable entry 833 with the mioxPeerEncPeerIndex that matches 834 the mioxPeerIndex, a mioxPeerEncEncIndex of 835 1, and a mioxPeerEncType of 204 (hex CC)." 836 ::= { mioxPeerEntry 2 } 838 mioxPeerMaxCircuits OBJECT-TYPE 839 SYNTAX PositiveInteger 840 ACCESS read-write 841 STATUS mandatory 842 DESCRIPTION 843 "The maximum number of X.25 circuits allowed 844 to this peer." 845 DEFVAL { 1 } 846 ::= { mioxPeerEntry 3 } 848 mioxPeerIfIndex OBJECT-TYPE 849 SYNTAX PositiveInteger 850 ACCESS read-write 851 STATUS mandatory 852 DESCRIPTION 853 "The value of the ifIndex object for the 854 interface to X.25 to use to call the peer." 855 DEFVAL { 1 } 856 ::= { mioxPeerEntry 4 } 858 mioxPeerConnectSeconds OBJECT-TYPE 859 SYNTAX Counter 860 ACCESS read-only 861 STATUS mandatory 862 DESCRIPTION 863 "The number of seconds a call to this peer 864 was active. This counter will be 865 incremented by one for every second a 866 connection to a peer was open. If two calls 867 are open at the same time, one second of 868 elapsed real time will results in two 870 seconds of connect time." 871 ::= { mioxPeerEntry 5 } 873 mioxPeerX25CallParamId OBJECT-TYPE 874 SYNTAX OBJECT IDENTIFIER 875 ACCESS read-write 876 STATUS mandatory 877 DESCRIPTION 878 "The instance of the index object in the 879 x25CallParmTable for the X.25 call 880 parameters used to communicate with the 881 remote host. The well know value {0 0} 882 indicates no call parameters specified." 883 DEFVAL { {0 0} } 884 ::= { mioxPeerEntry 6 } 886 mioxPeerEnAddr OBJECT-TYPE 887 SYNTAX OCTET STRING (SIZE (0..128)) 888 ACCESS read-write 889 STATUS mandatory 890 DESCRIPTION 891 "The Encapsulation address of the remote 892 host mapped by this table entry. A length 893 of zero indicates the remote IP address is 894 unknown or unspecified for use as a PLE 895 default. 897 The first octet of this object contains the 898 encapsulation type, the remaining octets 899 contain the address of that type that 900 failed. Thus for an IP address, the length 901 will be five octets, the first octet will 902 contain 204 (hex CC), and the last four 903 octets will contain the IP address. For a 904 snap encapsulation, the first byte would be 905 128 (hex 80) and the rest of the octet 906 string would have the snap header." 907 DEFVAL { ''h } 908 ::= { mioxPeerEntry 7 } 910 mioxPeerX121Address OBJECT-TYPE 911 SYNTAX X121Address 912 ACCESS read-write 913 STATUS mandatory 914 DESCRIPTION 915 "The X.25 address of the remote host mapped 916 by this table entry. A zero length string 917 indicates the X.25 address is unspecified 918 for use as the PLE default." 919 DEFVAL { ''h } 920 ::= { mioxPeerEntry 8 } 922 -- Systems can claim conformance to this MIB without 923 -- implementing sets to mioxPeerx25CircuitId. 924 -- However systems that use PVCs with RFC1356 925 -- are encouraged to implement sets. 926 mioxPeerX25CircuitId OBJECT-TYPE 927 SYNTAX OBJECT IDENTIFIER 928 ACCESS read-write 929 STATUS mandatory 930 DESCRIPTION 931 "This object identifies the instance of the 932 index for the X.25 circuit open to the peer 933 mapped by this table entry. The well knows 934 value {0 0} indicates no connection 935 currently active. For multiple connections, 936 this identifies the index of a multiplexing 937 table entry for the connections. This can 938 only be written to configure use of PVCs 939 which means the identified circuit table 940 entry for a write must be a PVC." 941 DEFVAL { {0 0} } 942 ::= { mioxPeerEntry 9 } 944 mioxPeerDescr OBJECT-TYPE 945 SYNTAX DisplayString (SIZE (0..255)) 946 ACCESS read-write 947 STATUS mandatory 948 DESCRIPTION 949 "This object returns any identification 950 information about the peer. An agent may 951 supply the comment information found in the 952 configuration file entry for this peer. A 953 zero length string indicates no information 954 available." 955 DEFVAL { ''h } 956 ::= { mioxPeerEntry 10 } 958 -- ########################################################### 959 -- Peer Encapsulation Table 960 -- ########################################################### 962 mioxPeerEncTable OBJECT-TYPE 963 SYNTAX SEQUENCE OF MioxPeerEncEntry 964 ACCESS not-accessible 965 STATUS mandatory 966 DESCRIPTION 967 "This table contains the list of 968 encapsulations used to communicate with a 969 peer. This table has two indexes, the first 970 identifies the peer, the second 971 distinguishes encapsulation types. 973 The peer index, mioxPeerEncPeerIndex, value 974 matches the value of the mioxPeerIndex entry 975 for the peer. The second index gives the 976 priority of the different encapsulations. 978 The encapsulation types are ordered in 979 priority order. For calling a peer, the 980 first entry (mioxPeerEncEncIndex of 1) is 981 tried first. If the call doesn't succeed 982 because the remote host clears the call due 983 to incompatible call user data, the next 984 entry in the list is tried. Each entry is 985 tried until the list is exhausted. 987 For answering a call, the encapsulation type 988 requested by the peer must be found the list 989 or the call will be refused. If there are 990 no entries in this table for a peer, all 991 call requests from the peer will be refused. 993 Objects in this table can only be set when 994 the mioxPeerStatus object with the same 995 index has a value of underCreation. When 996 that status object is set to invalid and 997 deleted, the entry in this table with that 998 peer index must also be deleted." 999 ::= { mioxPeer 2 } 1001 mioxPeerEncEntry OBJECT-TYPE 1002 SYNTAX MioxPeerEncEntry 1004 ACCESS not-accessible 1005 STATUS mandatory 1006 DESCRIPTION 1007 "Per connection information." 1008 INDEX { mioxPeerEncPeerIndex, mioxPeerEncEncIndex} 1009 ::= { mioxPeerEncTable 1 } 1011 MioxPeerEncEntry ::= SEQUENCE { 1012 mioxPeerEncPeerIndex 1013 PositiveInteger, 1014 mioxPeerEncEncIndex 1015 PositiveInteger, 1016 mioxPeerEncType 1017 INTEGER 1018 } 1020 mioxPeerEncPeerIndex OBJECT-TYPE 1021 SYNTAX PositiveInteger 1022 ACCESS read-only 1023 STATUS mandatory 1024 DESCRIPTION 1025 "An index value that matches the 1026 mioxPeerTable index of the peer to which 1027 these encapsulation types apply." 1028 ::= { mioxPeerEncEntry 1 } 1030 mioxPeerEncEncIndex OBJECT-TYPE 1031 SYNTAX PositiveInteger 1032 ACCESS read-only 1033 STATUS mandatory 1034 DESCRIPTION 1035 "The second index in the table which 1036 distinguishes different encapsulation 1037 types." 1038 ::= { mioxPeerEncEntry 2 } 1040 mioxPeerEncType OBJECT-TYPE 1041 SYNTAX INTEGER (0..256) 1042 ACCESS read-write 1043 STATUS mandatory 1044 DESCRIPTION 1045 "The value of the encapsulation type. For 1046 IP encapsulation this will have a value of 1047 204 (hex CC). For SNAP encapsulated 1048 packets, this will have a value of 128 (hex 1050 80). For CLNP, ISO 8473, this will have a 1051 value of 129 (hex 81). For ES-ES, ISO 9542, 1052 this will have a value of 130 (hex 82). A 1053 value of 197 (hex C5) identifies the Blacker 1054 X.25 encapsulation. A value of 0, 1055 identifies the Null encapsulation. 1057 This value can only be written when the 1058 matching mioxPeerStatus object has a value 1059 of underCreation. The mioxPeerStatus object 1060 that matches this entry has a mioxPeerIndex 1061 that matches the value of the 1062 mioxPeerEndPeerIndex of this entry. Setting 1063 this object to a value of 256 deletes this 1064 entry. All other entries in the 1065 mioxPeerEntTable with the same 1066 mioxPeerEncPeerIndex but with 1067 mioxPeerEncEncIndex-es higher then this 1068 entry will all have their 1069 mioxPeerEncEncIndex values decremented by 1070 one." 1071 ::= { mioxPeerEncEntry 3 } 1073 -- ########################################################### 1075 END 1076 7. Acknowledgements 1078 This document was produced by the x25mib working group: 1080 Fred Baker, ACC 1081 Art Berggreen, ACC 1082 Frank Bieser 1083 Gary Bjerke, Tandem 1084 Bill Bowman, HP 1085 Christopher Bucci, Datability 1086 Charles Carvalho, ACC 1087 Jeff Case, University of Tennessee at Knoxville 1088 Angela Chen, HP 1089 Carson Cheung, BNR 1090 Tom Daniel, Spider Systems 1091 Chuck Davin, MIT 1092 Billy Durham, Honeywell 1093 Richard Fox, Synoptics 1094 Doug Geller, Data General 1095 Herve Goguely, LIR Corp 1096 Andy Goldthorpe, british-telecom 1097 Walter D. Guilarte 1098 David Gurevich 1099 Steve Huston, Process Software Corporation 1100 Jon Infante, ICL 1101 Frank Kastenholz, FTP Software 1102 Zbigniew Kielczewski, Eicon 1103 Cheryl Krupezak, Georgia Tech 1104 Mats Lindstrom, Diab Data AB 1105 Andrew Malis, BBN 1106 Evan McGinnis, 3Com 1107 Gary (G.P.)Mussar, BNR 1108 Chandy Nilakantan, 3Com 1109 Randy Pafford, Data General 1110 Ragnar Paulson, The Software Group Limited 1111 Dave Perkins, Synoptics 1112 Walter Pinkarschewsky, DEC 1113 Karen Quidley, Data General 1114 Chris Ranch, Novell 1115 Paul S. Rarey, DHL Systems Inc. 1116 Jim Roche, Newbridge Research 1117 Philippe Roger, LIR Corp. 1118 Timon Sloane 1119 Mike Shand, DEC 1120 Brad Steina, Microcom 1121 Bob Stewart, Xyplex 1122 Tom Sullivan, Data General 1123 Rodney Thayer, Sable Technology Corporation 1124 Mark Therieau, Microcom 1125 Jane Thorn, Data General 1126 Dean Throop, Data General 1127 Maurice Turcotte, Racal Datacom 1128 Mike Zendels, Data General 1130 8. References 1132 [1] Rose M., and K. McCloghrie, "Structure and Identification 1133 of Management Information for TCP/IP-based internets", 1134 STD 16, RFC 1155, Performance Systems International, 1135 Hughes LAN Systems, May, 1990. 1137 [2] McCloghrie K., and M. Rose, "Management Information Base 1138 for Network Management of TCP/IP-based Internets", RFC 1139 1156, Hughes LAN Systems, Performance Systems 1140 International, May, 1990. 1142 [3] Case, J., M.S. Fedor, M.L. Schoffstall, and J. Davin, 1143 "Simple Network Management Protocol", STD 15, RFC 1157, 1144 SNMP Research, Performance Systems International, 1145 Performance Systems International, MIT Laboratory for 1146 Computer Science, May, 1990. 1148 [4] Rose, M. and K. McCloghrie, Editors, "Towards Concise MIB 1149 Definitions", STD 16, RFC 1212, Performance Systems 1150 International, Hughes LAN Systems, March, 1991. 1152 [5] Rose M., Editor, "Management Information Base for Network 1153 Management of TCP/IP-based internets", STD 17, RFC 1213. 1154 Performance Systems International, March, 1991. 1156 [6] "Information processing systems - Open Systems 1157 Interconnection - Specification of Abstract Syntax 1158 Notation One (ASN.1)", International Organization for 1159 Standardization. International Standard 8824, December, 1160 1987. 1162 [7] "Information processing systems - Open Systems 1163 Interconnection - Specification of Basic Encoding Rules 1164 for Abstract Notation One (ASN.1)", International 1165 Organization for Standardization. International Standard 1166 8825, December, 1987. 1168 [8] Stewart, B., Editor, "Definitions of Managed Objects for 1169 RS-232-like Hardware Devices", RFC 1317, Xyplex, Inc., 1170 April, 1992. 1172 [9] Throop, D., and F. Baker, "SNMP MIB extension for X.25 1173 LAPB", RFC 1381, Data General Corporation, Advanced 1174 Computer Communications, November, 1992. 1176 [10] Throop, D., Editor, "SNMP MIB extension for the X.25 1177 Packet Layer", RFC 1382, Data General Corporation, 1178 November, 1991. 1180 [11] Malis, A., D. Robinson, R. Ullmann "Multiprotocol 1181 Interconnect on X.25 and ISDN in the Packet Mode", RFC 1182 1356, BBN Communications, Computervision Systems 1183 Integration, Process Software Corporation, August, 1992. 1185 9. Authors' Addresses 1187 Dean D. Throop 1188 Data General Corporation 1189 62 Alexander Dr. 1190 Research Triangle Park, NC 27709 1192 Phone: (919) 248 6081 1193 EMail: throop@dg-rtp.dg.com 1195 Table of Contents 1197 1 Status of this Memo ................................... 1 1198 1.1 Revision History .................................... 2 1199 January 1993 ........................................... 2 1200 June 1992 .............................................. 2 1201 May 1992 ............................................... 3 1202 February 1992 .......................................... 4 1203 October 1991 ........................................... 4 1204 June 1991 .............................................. 5 1205 2 Abstract .............................................. 5 1206 3 The Network Management Framework ...................... 6 1207 4 Objects ............................................... 6 1208 4.1 Format of Definitions ............................... 7 1209 5 Overview .............................................. 8 1210 5.1 MIB Context ......................................... 8 1211 5.2 Structure of MIB objects ............................ 8 1212 6 Definitions ........................................... 10 1213 7 Acknowledgements ...................................... 27 1214 8 References ............................................ 29 1215 9 Authors' Addresses .................................... 30