idnits 2.17.1 draft-ietf-x25mib-x25packet-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-25) 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 257 instances of weird spacing in the document. Is it really formatted ragged-right, rather than justified? ** The abstract seems to contain references ([2], [0-9], [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 42 has weird spacing: '... as the x25Pl...' == Line 249 has weird spacing: '...specify the s...' == Line 399 has weird spacing: '...ntifies the ...' == Line 400 has weird spacing: '...network and ...' == Line 436 has weird spacing: '...ntifies the ...' == (252 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 (February 24, 1992) is 11749 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? '11' on line 2328 looks like a reference -- Missing reference section? '9' on line 2319 looks like a reference -- Missing reference section? '8' on line 2315 looks like a reference -- Missing reference section? '1' on line 2279 looks like a reference -- Missing reference section? '4' on line 2294 looks like a reference -- Missing reference section? '2' on line 2284 looks like a reference -- Missing reference section? '5' on line 2298 looks like a reference -- Missing reference section? '3' on line 2289 looks like a reference -- Missing reference section? '6' on line 2303 looks like a reference -- Missing reference section? '7' on line 2309 looks like a reference -- Missing reference section? '10' on line 2323 looks like a reference -- Missing reference section? '0-9' on line 290 looks like a reference Summary: 16 errors (**), 0 flaws (~~), 8 warnings (==), 13 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Internet Draft X.25 Packet Layer MIB February 1992 4 SNMP MIB extension for the X.25 Packet Layer 6 February 24, 1992 8 Dean D. Throop 9 (editor) 11 Data General Corporation 12 62 Alexander Dr. 13 Research Triangle Park, NC 27709 15 throop@dg-rtp.dg.com 17 1. Status of this Memo 19 This is a draft document of the x25mib working group. The 20 working group intends to submit a revised version of this 21 document to the RFC editor as an extension to the SNMP MIB. 22 Distribution of this memo is unlimited. Please send comments 23 to the x25mib working group: 25 x25mib@dg-rtp.dg.com 27 1.1. Revision History 29 February 1992 31 The February release (Editor's Internal Reference Number 1.14) 32 made many changes. 34 Many of the tables were combined. For example, the 35 x25InfoTable, x25PktStatTable, and x25TmrStatTable were 36 combined into the x25PleTable. The x25ConInfoTable, 37 x25ConStatTable, and x25ConTimrTable were combined into 38 the x25CircuitTable. 40 The objects for call parameters were drastically 41 reworked. All call parameters were combined in the 42 x25CallParmTable. Any table, such as the x25PleTable or 43 x25CircuitTable, that needs to reference call parameters 44 identifies an entry in the new table. As part of this 45 the x25ConDefTable was deleted and replaced with the 46 x25PleDefCallParamId. 48 The x25PvcTable was deleted; the x25CircuitStatus object 49 provides similar information about PVCs. 51 The x25ClearedCircuitTable was added to record the status 52 code of cleared circuits. 54 Many object definitions were restructured. For example, 55 the time units for timers was changed from 1/100ths of a 56 second to milliseconds. Some indexes into tables were 57 replaced with object identifiers. 59 Much of the introductory text was changed and the 60 references were changed to match. 62 October 1992 64 The October release (Editor Internal Reference Number 1.10) 65 made the following changes: 67 Changed x25ConInfoStatus to clarify the description and 68 the pvcResetting(5) value was changed to pvcResetting(6) 69 to avoid a conflict with a previous use of the number 5. 71 The name of the counter object 72 x25TmrStatRetryCountsExceeded was changed to 73 x25TmrStatRetryCountExceededs. 75 The name of the counter object 76 x25TmrStatClearCountsExceeded was changed to 77 x25TmrStatClearCountExceededs. 79 All occurances of Guage were changed to Gauge. 81 Added the x25CallFcltyTable, x25CallFcltyCcittTable, and 82 x25CallParamTable. 84 June 1991 86 The June release corrected some syntax errors and cleaned up 87 some other minor things. 89 April 1991 91 The April 26 release of this document was the first release. 92 That version was derived from the ISO work on network layer 93 management as presented in ISO/IEC 10733 [11]. 95 2. Abstract 97 This memo defines a portion of the Management Information Base 98 (MIB) for use with network management protocols in TCP/IP- 99 based internets. In particular, it defines objects for 100 managing the Packet Layer of X.25. The objects defined here, 101 along with the objects in the "SNMP MIB extension for LAPB" 102 [9] and the "Definitions of Managed Objects for RS-232-like 103 Hardware Devices" [8], combine to allow management of an X.25 104 protocol stack. 106 3. The Network Management Framework 108 The Internet-standard Network Management Framework consists of 109 three components. These components give the rules for 110 defining objects, the definitions of objects, and the protocol 111 for manipulating objects. 113 The network management framework structures objects in an 114 abstract information tree. The branches of the tree name 115 objects and the leaves of the tree contain the values 116 manipulated to effect management. This tree is called the 117 Management Information Base or MIB. The concepts of this tree 118 are given in RFC 1155 "The Structure of Management 119 Information" or SMI [1]. The SMI defines the trunk of the tree 120 and the types of objects used when defining the leaves. RFC 121 1212, "Towards Concise MIB Definitions" [4], defines a more 122 concise description mechanism that preserves all the 123 principals of the SMI. 125 The core MIB definitions for the Internet suite of protocols 126 can be found in RFC 1156 [2] "Management Information Base for 127 Network Management of TCP/IP-based internets". RFC 1213 [5] 128 defines MIB-II, an evolution of MIB-I with changes to 129 incorporate implementation experience and new operational 130 requirements. 132 RFC 1157 [3] defines the SNMP protocol itself. The protocol 133 defines how to manipulate the objects in a remote MIB. 135 The tree structure of the MIB allows new objects to be defined 136 for the purpose of experimentation and evaluation. 138 4. Objects 140 The definition of an object in the MIB requires an object name 141 and type. Object names and types are defined using the subset 142 of Abstract Syntax Notation One (ASN.1) [6] defined in the SMI 143 [1]. Objects are named using ASN.1 object identifiers, 144 administratively assigned names, to specify object types. The 145 object name, together with an optional object instance, 146 uniquely identifies a specific instance of an object. For 147 human convenience, we often use a textual string, termed the 148 OBJECT DESCRIPTOR, to also refer to objects. 150 Objects also have a syntax that defines the abstract data 151 structure corresponding to that object type. The ASN.1 152 language [6] provides the primitives used for this purpose. 153 The SMI [1] purposely restricts the ASN.1 constructs which may 154 be used for simplicity and ease of implementation. The 155 encoding of an object type simply describes how to represent 156 an object using ASN.1 encoding rules [7], for purposes of 157 dealing with the SNMP protocol. 159 4.1. Format of Definitions 161 Section 6 contains the specification of all object types 162 defined in this MIB module. The object types are defined 163 using the conventions defined in the SMI, as amended by the 164 extensions specified in "Towards Concise MIB Definitions" [4]. 166 5. Overview 168 5.1. Informal Overview 170 This section describes how the objects defined below relate 171 with other MIBs. This section is only informational to help 172 understand how the pieces fit together. 174 The objects defined below are used in conjunction with MIB-II 175 and other MIBs such as the LAPB MIB [9]. A system with a 176 complete X.25 stack running over a synchronous line will have 177 at least two interfaces in the ifTable defined in MIB-II. 178 There will be an interface for LAPB and another interface for 179 the packet layer of X.25. There will also be objects defined 180 in the RS-232-like MIB for the physical sync line. 182 Each software interface identifies the layer below it used to 183 send and receive packets. The X.25 MIB object, defined below, 184 x25PleDataLinkId, specifies an instance of lapbParamIndex for 185 the LAPB interface under that X.25. The LAPB object, 186 lapbParamPortId, identifies an instance of the rs232PortIndex 187 for the the Sync line used by LAPB. 189 For X.25 running over LAPB over Ethernet, the lapbParamPortId 190 would identify the instance of ifIndex for the Ethernet 191 interface. 193 Each X.25 subnetwork will have separate entries in the 194 ifTable. Thus a system with two X.25 lines would have two 195 ifTable entries for the two X.25 packet layers and two other 196 entries for the two LAPB interfaces. Each X.25 Packet Layer 197 MIB would identify the instance of the LAPB MIB for the 198 interface below it. Each LAPB MIB would identify the Sync line 199 below it. The system would also have two entries for 200 rs232PortTable and rs232SyncPortTable for the two physical 201 lines. 203 Since the ifTable as defined in MIB-II is device independent, 204 it doesn't have anything specific for any type of interface. 205 The objects below define the X.25 packet layer specific 206 information for an interface of type X.25. Different X.25 207 interfaces can also be differentiated by matching the values 208 of ifIndex with x25PleIndex. 210 5.2. Textual Conventions 212 This MIB introduces a new data type as a textual convention 213 for use with X.25. This textual convention enhances the 214 readability of the specification and can ease comparison with 215 other specifications if appropriate. It should be noted that 216 the introduction of such textual conventions has no effect on 217 either the syntax nor the semantics of any managed objects. 218 These conventions are merely an artifact of the explanatory 219 method used. Objects defined in terms of one of these methods 220 are always encoded by means of the rules that define the 221 primitive type. Hence, no changes to the SMI or the SNMP are 222 necessary to accommodate these textual conventions which are 223 adopted merely for the convenience of readers and writers in 224 pursuit of the elusive goal of clear, concise, and unambiguous 225 MIB documents. 227 This MIB introduces the data type of: 229 X25address 231 5.3. Structure of MIB 233 Instances of the objects defined below represent attributes of 234 an X.25 Packet Layer interface. At present these interfaces 235 are identified by an ifType object in the Internet-standard 236 MIB [5] of: 238 ddn-x25(4), and 239 rfc887-x25(5). 241 For these interfaces, the value of the ifSpecific variable in 242 the MIB-II [5] has the OBJECT IDENTIFIER value: 244 x25 OBJECT IDENTIFIER ::= { To Be Assigned } 246 The objects defined below are similar to those defined in a 247 draft ISO document for X.25 management [11]. Some object 248 definitions also reference the ISO specification for X.25 [10] 249 to specify the section that will give the reader addition 250 information relative to the object. Access to those documents 251 maybe useful (but isn't essential) to understand the names and 252 semantics of some objects. The similarity of these objects 253 with the ISO objects minimizes the instrumentation required by 254 those systems that support both OSI and TCP/IP management 255 protocols. 257 Since the objects defined here are extensions to the Internet 258 Standard MIB [2] and thus also an extension of the second 259 version, MIB-II [5], the objects defined here explicitly do 260 not duplicate objects defined in existing standards. In some 261 instances clarification of how to apply those objects has been 262 given. 264 The relationship between an X.25 Packet Layer interface and an 265 interface in the context of the Internet-standard MIB [5] is 266 one-to-one. As such, the value of an ifIndex object instance 267 can be directly used to identify corresponding instances of 268 the objects defined below. 270 6. Object Definitions 272 RFCX25Pk-MIB DEFINITIONS ::= BEGIN 273 -- Editors internal reference number 1.79 275 IMPORTS 276 experimental, 277 Counter, 278 Gauge, 279 TimeTicks 280 FROM RFC1155-SMI; 282 -- DO NOT USE THIS EXPERIMENTAL NUMBER! 283 x25 OBJECT IDENTIFIER ::= { experimental 1234567 } 284 -- This experimental number is 285 -- an invalid placeholder. 286 -- DO NOT USE THIS EXPERIMENTAL NUMBER! 288 X25address ::= OCTET STRING (SIZE(0..17)) 289 -- 0 to 17 bytes in length containing the ASCII 290 -- characters [0-9], each octet contains one digit 291 -- of the address. 293 -- ########################################################### 294 -- X.25 Packet Level Entity (PLE) Table 295 -- ########################################################### 297 x25PleTable OBJECT-TYPE 298 SYNTAX SEQUENCE OF X25PleEntry 299 ACCESS not-accessible 300 STATUS mandatory 301 DESCRIPTION 302 "General information about this X.25 PLE." 303 ::= { x25 1 } 305 x25PleEntry OBJECT-TYPE 306 SYNTAX X25PleEntry 307 ACCESS not-accessible 308 STATUS mandatory 309 DESCRIPTION 310 "Entries of x25PleTable." 311 INDEX { x25PleIndex } 312 ::= { x25PleTable 1 } 314 X25PleEntry ::= SEQUENCE { 315 x25PleIndex 316 INTEGER, 317 x25PleProtocolVersionSupported 318 OBJECT IDENTIFIER, 319 x25PleLocalAddress 320 X25address, 321 x25PleInterfaceMode 322 INTEGER, 323 x25PleMaxActiveCircuits 324 INTEGER, 325 x25PleDataLinkId 326 OBJECT IDENTIFIER, 327 x25PlePacketSequencing 328 INTEGER, 329 x25PleInCalls 330 Counter, 331 x25PleInCallRefusals 332 Counter, 333 x25PleInProviderInitiatedClears 334 Counter, 335 x25PleInRemotelyInitiatedResets 336 Counter, 337 x25PleInProviderInitiatedResets 338 Counter, 339 x25PleInRestarts 340 Counter, 341 x25PleInDataPackets 342 Counter, 343 x25PleInAccusedOfProtocolErrors 344 Counter, 345 x25PleInInterrupts 346 Counter, 347 x25PleOutCallAttempts 348 Counter, 349 x25PleOutCallFailures 350 Counter, 351 x25PleOutInterrupts 352 Counter, 353 x25PleOutgoingConnections 354 Gauge, 355 x25PleIncomingConnections 356 Gauge, 357 x25PleTwowayConnections 358 Gauge, 360 x25PleRestartTimer 361 INTEGER, 362 x25PleMinimumRecallTimer 363 INTEGER, 364 x25PleRestartCount 365 INTEGER, 366 x25PleRegistrationRequestTimer 367 INTEGER, 368 x25PleRegistrationRequestCount 369 INTEGER, 370 x25PleCallTimeouts 371 Counter, 372 x25PleClearTimeouts 373 Counter, 374 x25PleResetTimeouts 375 Counter, 376 x25PleRestartTimeouts 377 Counter, 378 x25PleInterruptTimeouts 379 Counter, 380 x25PleDataRxmtTimeouts 381 Counter, 382 x25PleRetryCountExceededs 383 Counter, 384 x25PleClearCountExceededs 385 Counter, 386 x25PleClearEntriesRequested 387 INTEGER, 388 x25PleClearEntriesGranted 389 INTEGER, 390 x25PleDefCallParamId 391 OBJECT IDENTIFIER 392 } 394 x25PleIndex OBJECT-TYPE 395 SYNTAX INTEGER (1..65535) 396 ACCESS read-only 397 STATUS mandatory 398 DESCRIPTION 399 "A value that uniquely identifies the X.25 400 PLE subnetwork and matches its ifIndex 401 value." 402 ::= { x25PleEntry 1 } 404 -- MIB-II also provides: 406 -- ifDescr: 407 -- On an X.25 interface this must include sufficient 408 -- information to enable the system's administrator 409 -- to determine the appropriate configuration 410 -- information on a system having multiple X.25 411 -- subnetworks. 413 -- ifType: ddn-x25 or rfc877-x25 414 -- an interface of type ddn-x25 will use an algorithm to 415 -- translate between X.121 address and IP addresses. 416 -- An interface of type rfc877-x25 will use a 417 -- configuration table to translate between X.121 418 -- addresses and IP addresses. 420 -- ifMtu: the maximum PDU a higher layer can pass to X.25 or 421 -- or receive from X.25 423 -- ifSpeed: 425 -- ifAdminStatus: 427 -- ifOperStatus 429 -- ifLastChange 431 x25PleProtocolVersionSupported OBJECT-TYPE 432 SYNTAX OBJECT IDENTIFIER 433 ACCESS read-write 434 STATUS mandatory 435 DESCRIPTION 436 "Identifies the version of X.25 this 437 interface supports. Object identifiers for 438 common versions are defined below in the 439 x25ProtocolVersion subtree." 440 REFERENCE "10733 5.9 protocolVersionSupported" 441 ::= { x25PleEntry 2 } 443 x25PleLocalAddress OBJECT-TYPE 444 SYNTAX X25address 445 ACCESS read-write 446 STATUS mandatory 447 DESCRIPTION 448 "The local address for this PLE subnetwork." 449 REFERENCE "10733 5.9 localDTEAddress" 450 ::= { x25PleEntry 3 } 452 x25PleInterfaceMode OBJECT-TYPE 453 SYNTAX INTEGER { 454 dte(1), 455 dce(2) } 456 ACCESS read-write 457 STATUS mandatory 458 DESCRIPTION 459 "Identifies DCE/DTE mode in which the 460 interface operates." 461 REFERENCE "10733 5.9 interfaceMode" 462 ::= { x25PleEntry 4 } 464 x25PleMaxActiveCircuits OBJECT-TYPE 465 SYNTAX INTEGER (1..4096) 466 ACCESS read-write 467 STATUS mandatory 468 -- See ISO 8208, Section 3.7 469 DESCRIPTION 470 "Maximum number of circuits this PLE can 471 support." 472 REFERENCE "10733 5.9 maxActiveCircuits" 473 ::= { x25PleEntry 5 } 475 x25PleDataLinkId OBJECT-TYPE 476 SYNTAX OBJECT IDENTIFIER 477 ACCESS read-only 478 STATUS mandatory 479 DESCRIPTION 480 "This identifies the instance of the index 481 object in the first table of the most device 482 specific MIB for the interface used by this 483 PLE." 484 ::= { x25PleEntry 6 } 486 x25PlePacketSequencing OBJECT-TYPE 487 SYNTAX INTEGER { 488 modulo8(1), 489 modulo128(2) } 490 ACCESS read-write 491 STATUS mandatory 492 -- See ISO 8208 Section 7.1.1 493 DESCRIPTION 494 "The modulus of the packet sequence number 495 space." 496 REFERENCE "10733 extendedPacketSequencing" 498 ::= { x25PleEntry 7 } 500 -- The following are the statistics part of the PLE. 502 -- MIB-II interfaces also contains: 503 -- ifInOctets: Number of data octets delivered to upper 504 -- layer entities. 506 -- ifInUcastPkts: Number of packets received from peer PLE and 507 -- delivered to upper layer entities. 509 -- ifDiscards: Number of packets dropped for lack of buffering 511 -- ifInErrors: Number of packets received containing errors 512 -- REFERENCE ProtocolErrorsDetectedLocally 514 -- ifInUnknownProtos: Number of packets with unknown circuit 515 -- identifier. 517 x25PleInCalls OBJECT-TYPE 518 SYNTAX Counter 519 ACCESS read-only 520 STATUS mandatory 521 DESCRIPTION 522 "The number of incoming calls received." 523 ::= { x25PleEntry 8 } 525 x25PleInCallRefusals OBJECT-TYPE 526 SYNTAX Counter 527 ACCESS read-only 528 STATUS mandatory 529 DESCRIPTION 530 "The number of incoming calls refused." 531 ::= { x25PleEntry 9 } 533 x25PleInProviderInitiatedClears OBJECT-TYPE 534 SYNTAX Counter 535 ACCESS read-only 536 STATUS mandatory 537 DESCRIPTION 538 "The number of clear requests with a cause 539 code other than DTE initiated." 540 REFERENCE "10733 providerInitiatedDisconnect" 541 ::= { x25PleEntry 10 } 543 x25PleInRemotelyInitiatedResets OBJECT-TYPE 544 SYNTAX Counter 545 ACCESS read-only 546 STATUS mandatory 547 DESCRIPTION 548 "The number of reset requests received with 549 cause code DTE initiated." 550 REFERENCE "10733 remotelyInitiatedResets" 551 ::= { x25PleEntry 11 } 553 x25PleInProviderInitiatedResets OBJECT-TYPE 554 SYNTAX Counter 555 ACCESS read-only 556 STATUS mandatory 557 DESCRIPTION 558 "The number of reset requests received with 559 cause code other than DTE initiated." 560 REFERENCE "10733 ProviderInitiatedResets" 561 ::= { x25PleEntry 12 } 563 x25PleInRestarts OBJECT-TYPE 564 SYNTAX Counter 565 ACCESS read-only 566 STATUS mandatory 567 DESCRIPTION 568 "The number of remotely initiated (including 569 provider initiated) restarts experienced by 570 the PLE excluding the restart associated 571 with bringing up the PLE interface." 572 REFERENCE "10733 5.9 remotelyInitiatedRestarts" 573 ::= { x25PleEntry 13 } 575 x25PleInDataPackets OBJECT-TYPE 576 SYNTAX Counter 577 ACCESS read-only 578 STATUS mandatory 579 DESCRIPTION 580 "The number of data packets received." 581 REFERENCE "10733 5.9 dataPacketsReceived." 582 ::= { x25PleEntry 14 } 584 x25PleInAccusedOfProtocolErrors OBJECT-TYPE 585 SYNTAX Counter 586 ACCESS read-only 587 STATUS mandatory 589 DESCRIPTION 590 "The number of packets received containing a 591 protocol error cause code. These include 592 clear, reset, restart, or diagnostic 593 packets." 594 REFERENCE "CD 10733 5.9 accusedOfProtocolError" 595 ::= { x25PleEntry 15 } 597 x25PleInInterrupts OBJECT-TYPE 598 SYNTAX Counter 599 ACCESS read-only 600 STATUS mandatory 601 DESCRIPTION 602 "The number of interrupt packets received by 603 the PLE or over the PVC/VC." 604 REFERENCE "10733 interruptPacketsReceived" 605 ::= { x25PleEntry 16 } 607 -- ifOutOctets: Number of data octets delivered by 608 -- X.25 to upper layers. 610 -- ifOutUcastPkts: Number of packets sent to peer PLE. 612 x25PleOutCallAttempts OBJECT-TYPE 613 SYNTAX Counter 614 ACCESS read-only 615 STATUS mandatory 616 DESCRIPTION 617 "The number of calls attempted." 618 REFERENCE "10733 5.9 callAttempts" 619 ::= { x25PleEntry 17 } 621 x25PleOutCallFailures OBJECT-TYPE 622 SYNTAX Counter 623 ACCESS read-only 624 STATUS mandatory 625 DESCRIPTION 626 "The number of calls attempts which failed." 627 ::= { x25PleEntry 18 } 629 x25PleOutInterrupts OBJECT-TYPE 630 SYNTAX Counter 631 ACCESS read-only 632 STATUS mandatory 633 DESCRIPTION 634 "The number of interrupt packets send by the 635 PLE or over the PVC/VC." 636 REFERENCE "10733 InterruptPacketsSent" 637 ::= { x25PleEntry 19 } 639 x25PleOutgoingConnections OBJECT-TYPE 640 SYNTAX Gauge 641 ACCESS read-only 642 STATUS mandatory 643 DESCRIPTION 644 "The number of active outgoing connections. 645 This includes call requests sent but not yet 646 confirmed." 647 ::= { x25PleEntry 20 } 649 x25PleIncomingConnections OBJECT-TYPE 650 SYNTAX Gauge 651 ACCESS read-only 652 STATUS mandatory 653 DESCRIPTION 654 "The Number of active Incoming Connections. 655 This includes any call indications received 656 but not yet acknowledged." 657 ::= { x25PleEntry 21 } 659 x25PleTwowayConnections OBJECT-TYPE 660 SYNTAX Gauge 661 ACCESS read-only 662 STATUS mandatory 663 DESCRIPTION 664 "The number of active two-way connections. 665 This includes call requests sent but not yet 666 confirmed." 667 ::= { x25PleEntry 22 } 669 -- X25 Timer Statistics section 671 x25PleRestartTimer OBJECT-TYPE 672 SYNTAX INTEGER (1..1800000) 673 ACCESS read-write 674 STATUS mandatory 675 -- See ISO 8208 Section 4.1, table 26 676 DESCRIPTION 677 "The T20 restart timer in milliseconds." 679 REFERENCE "10733 5.9 restartTime" 680 ::= { x25PleEntry 23 } 682 x25PleMinimumRecallTimer OBJECT-TYPE 683 SYNTAX INTEGER (0..1800000) 684 ACCESS read-write 685 STATUS mandatory 686 DESCRIPTION 687 "Minimum time interval between call attempts 688 in milliseconds." 689 REFERENCE "10733 5.9 minimum RecallTimer" 690 ::= { x25PleEntry 24 } 692 x25PleRestartCount OBJECT-TYPE 693 SYNTAX INTEGER (1..65535) 694 ACCESS read-write 695 STATUS mandatory 696 -- See ISO 8208 Section 4.1, table 27 697 DESCRIPTION 698 "The value of the R20 restart retransmission 699 count." 700 REFERENCE "10733 5.9 restartCount" 701 ::= { x25PleEntry 25 } 703 x25PleRegistrationRequestTimer OBJECT-TYPE 704 SYNTAX INTEGER (0..1800000) 705 ACCESS read-write 706 STATUS mandatory 707 -- See ISO 8208 Section 13.1.1.1, table 26 708 DESCRIPTION 709 "The T28 registration timer in milliseconds. 710 A value of zero indicates no registration 711 timer in use." 712 REFERENCE "10733 5.8.1 registrationRequestTime (opt)" 713 ::= { x25PleEntry 26 } 715 x25PleRegistrationRequestCount OBJECT-TYPE 716 SYNTAX INTEGER (0..65535) 717 ACCESS read-write 718 STATUS mandatory 719 -- See ISO 8208 Section 13.1.1.1, table 27 720 DESCRIPTION 721 "The R28 Registration retransmission Count. 722 A value of zero indicates no timer in use." 723 REFERENCE "10733 5.8.1 registrationRequestCount (opt)" 725 ::= { x25PleEntry 27 } 727 x25PleCallTimeouts OBJECT-TYPE 728 SYNTAX Counter 729 ACCESS read-only 730 STATUS mandatory 731 DESCRIPTION 732 "The number of times the T21 call timer 733 expired." 734 REFERENCE "10733 5.9 callTimeouts" 735 ::= { x25PleEntry 28 } 737 x25PleClearTimeouts OBJECT-TYPE 738 SYNTAX Counter 739 ACCESS read-only 740 STATUS mandatory 741 DESCRIPTION 742 "The number of times the T23 clear timer 743 expired." 744 REFERENCE "10733 5.9 clearTimeouts" 745 ::= { x25PleEntry 29 } 747 x25PleResetTimeouts OBJECT-TYPE 748 SYNTAX Counter 749 ACCESS read-only 750 STATUS mandatory 751 DESCRIPTION 752 "The number of times the T22 reset timer 753 expired." 754 REFERENCE "10733 5.9 resetTimeouts" 755 ::= { x25PleEntry 30 } 757 x25PleRestartTimeouts OBJECT-TYPE 758 SYNTAX Counter 759 ACCESS read-only 760 STATUS mandatory 761 DESCRIPTION 762 "The number of times the T20 restart timer 763 expired." 764 REFERENCE "10733 5.9 restartTimeouts" 765 ::= { x25PleEntry 31 } 767 x25PleInterruptTimeouts OBJECT-TYPE 768 SYNTAX Counter 769 ACCESS read-only 771 STATUS mandatory 772 DESCRIPTION 773 "The number of times the T26 interrupt timer 774 expired." 775 REFERENCE "10733 5.9 interruptTimerExpires" 776 ::= { x25PleEntry 32 } 778 x25PleDataRxmtTimeouts OBJECT-TYPE 779 SYNTAX Counter 780 ACCESS read-only 781 STATUS mandatory 782 DESCRIPTION 783 "The number of times the T25 data timer 784 expired." 785 REFERENCE "10733 5.9 dataRetransmissionsTimerExpiries" 786 ::= { x25PleEntry 33 } 788 x25PleRetryCountExceededs OBJECT-TYPE 789 SYNTAX Counter 790 ACCESS read-only 791 STATUS mandatory 792 DESCRIPTION 793 "The number of times a retry counter was 794 exhausted." 795 REFERENCE "10733 5.9 retryCountsExceeded" 796 ::= { x25PleEntry 34 } 798 x25PleClearCountExceededs OBJECT-TYPE 799 SYNTAX Counter 800 ACCESS read-only 801 STATUS mandatory 802 DESCRIPTION 803 "The number of times the R23 clear count was 804 exceeded." 805 REFERENCE "10733 5.9 clearCountsExceeded" 806 ::= { x25PleEntry 35 } 808 x25PleClearEntriesRequested OBJECT-TYPE 809 SYNTAX INTEGER (1..65535) 810 ACCESS read-write 811 STATUS mandatory 812 DESCRIPTION 813 "The requested number of entries this PLE 814 will keep in the x25ClearedCircuit table." 815 ::= { x25PleEntry 36 } 817 x25PleClearEntriesGranted OBJECT-TYPE 818 SYNTAX INTEGER (1..65535) 819 ACCESS read-only 820 STATUS mandatory 821 DESCRIPTION 822 "The number entries the agent will keep in 823 the x25ClearedCircuit Table." 824 ::= { x25PleEntry 37 } 826 x25PleDefCallParamId OBJECT-TYPE 827 SYNTAX OBJECT IDENTIFIER 828 ACCESS read-write 829 STATUS mandatory 830 DESCRIPTION 831 "This identifies the instance of the 832 x25CallParmIndex for the entry in the 833 x25callParm table which contains the default 834 call parameters for this Ple." 835 ::= { x25PleEntry 38 } 837 -- ########################################################### 838 -- X.25 Channel Table 839 -- ########################################################### 841 x25ChannelTable OBJECT-TYPE 842 SYNTAX SEQUENCE OF X25ChannelEntry 843 ACCESS not-accessible 844 STATUS mandatory 845 -- See ISO 8208, Section 3.7 846 DESCRIPTION 847 "These objects contain information about the 848 channel number configuration in an X.25 849 PLE." 850 ::= { x25 2 } 852 x25ChannelEntry OBJECT-TYPE 853 SYNTAX X25ChannelEntry 854 ACCESS not-accessible 855 STATUS mandatory 856 DESCRIPTION 857 "Entries of x25ChannelTable." 858 -- REFERENCE This provides the information 859 -- available in logicalChannelAssignments. 861 INDEX { x25ChannelIndex } 862 ::= { x25ChannelTable 1 } 864 X25ChannelEntry ::= SEQUENCE { 865 x25ChannelIndex 866 INTEGER, 867 x25ChannelLIC 868 INTEGER, 869 x25ChannelHIC 870 INTEGER, 871 x25ChannelLTC 872 INTEGER, 873 x25ChannelHTC 874 INTEGER, 875 x25ChannelLOC 876 INTEGER, 877 x25ChannelHOC 878 INTEGER 879 } 881 x25ChannelIndex OBJECT-TYPE 882 SYNTAX INTEGER (1..65535) 883 ACCESS read-only 884 STATUS mandatory 885 DESCRIPTION 886 "A value that uniquely identifies the X.25 887 PLE subnetwork and matches its ifIndex 888 value." 889 ::= { x25ChannelEntry 1 } 891 x25ChannelLIC OBJECT-TYPE 892 SYNTAX INTEGER (1..4096) 893 ACCESS read-write 894 STATUS mandatory 895 DESCRIPTION 896 "Lowest Incoming channel." 897 ::= { x25ChannelEntry 2 } 899 x25ChannelHIC OBJECT-TYPE 900 SYNTAX INTEGER (1..4096) 901 ACCESS read-write 902 STATUS mandatory 903 DESCRIPTION 904 "Highest Incoming channel." 905 ::= { x25ChannelEntry 3 } 907 x25ChannelLTC OBJECT-TYPE 908 SYNTAX INTEGER (1..4096) 909 ACCESS read-write 910 STATUS mandatory 911 DESCRIPTION 912 "Lowest Two-way channel." 913 ::= { x25ChannelEntry 4 } 915 x25ChannelHTC OBJECT-TYPE 916 SYNTAX INTEGER (1..4096) 917 ACCESS read-write 918 STATUS mandatory 919 DESCRIPTION 920 "Highest Two-way channel." 921 ::= { x25ChannelEntry 5 } 923 x25ChannelLOC OBJECT-TYPE 924 SYNTAX INTEGER (1..4096) 925 ACCESS read-write 926 STATUS mandatory 927 DESCRIPTION 928 "Lowest outgoing channel." 929 ::= { x25ChannelEntry 6 } 931 x25ChannelHOC OBJECT-TYPE 932 SYNTAX INTEGER (1..4096) 933 ACCESS read-write 934 STATUS mandatory 935 DESCRIPTION 936 "Highest outgoing channel." 937 ::= { x25ChannelEntry 7 } 939 -- ########################################################### 940 -- X25 Per Connection Information Table 941 -- ########################################################### 943 x25CircuitTable OBJECT-TYPE 944 SYNTAX SEQUENCE OF X25CircuitEntry 945 ACCESS not-accessible 946 STATUS mandatory 947 DESCRIPTION 948 "These objects contain general information 949 about a specific connection of an X.25 PLE." 950 ::= { x25 3 } 952 x25CircuitEntry OBJECT-TYPE 953 SYNTAX X25CircuitEntry 954 ACCESS not-accessible 955 STATUS mandatory 956 DESCRIPTION 957 "Entries of x25CircuitTable." 958 INDEX { x25CircuitIndex, 959 x25CircuitChannel } 960 ::= { x25CircuitTable 1 } 962 X25CircuitEntry ::= SEQUENCE { 963 x25CircuitIndex 964 INTEGER, 965 x25CircuitChannel 966 INTEGER, 967 x25CircuitName 968 DisplayString, 969 x25CircuitEstablishTime 970 TimeTicks, 971 x25CircuitStatus 972 INTEGER, 973 x25CircuitDirection 974 INTEGER, 975 x25CircuitCallParamId 976 OBJECT IDENTIFIER, 977 x25CircuitRemoteDteAddress 978 X25Address, 979 x25CircuitCalledDteAddress 980 X25Address, 981 x25CircuitCallingDteAddress 982 X25Address, 983 x25CircuitOriginallyCalledAddress 984 X25Address, 985 x25CircuitInOctets 986 Counter, 987 x25CircuitInPdus 988 Counter, 989 x25CircuitInRemotelyInitiatedResets 990 Counter, 991 x25CircuitInProviderInitiatedResets 992 Counter, 994 x25CircuitInInterrupts 995 Counter, 996 x25CircuitOutOctets 997 Counter, 998 x25CircuitOutPdus 999 Counter, 1000 x25CircuitOutInterrupts 1001 Counter, 1002 x25CircuitDataRetransmissionTimeouts 1003 Counter, 1004 x25CircuitResetTimeouts 1005 Counter, 1006 x25CircuitInterruptTimeouts 1007 Counter 1008 } 1010 x25CircuitIndex OBJECT-TYPE 1011 SYNTAX INTEGER (1..65535) 1012 ACCESS read-only 1013 STATUS mandatory 1014 DESCRIPTION 1015 "A value that uniquely identifies the X.25 1016 PLE subnetwork and matches its ifIndex 1017 value." 1018 ::= { x25CircuitEntry 1 } 1020 x25CircuitChannel OBJECT-TYPE 1021 SYNTAX INTEGER (1..4096) 1022 ACCESS read-only 1023 STATUS mandatory 1024 DESCRIPTION 1025 "The channel number for this connection." 1026 ::= { x25CircuitEntry 2 } 1028 x25CircuitName OBJECT-TYPE 1029 SYNTAX DisplayString (SIZE (0..255)) 1030 ACCESS read-only 1031 STATUS mandatory 1032 DESCRIPTION 1033 "A name associated with this connection." 1034 ::= { x25CircuitEntry 3 } 1036 x25CircuitEstablishTime OBJECT-TYPE 1037 SYNTAX TimeTicks 1039 ACCESS read-only 1040 STATUS mandatory 1041 DESCRIPTION 1042 "Value of sysUpTime when the channel was 1043 associated with this connection." 1044 ::= { x25CircuitEntry 4 } 1046 x25CircuitStatus OBJECT-TYPE 1047 SYNTAX INTEGER { -- state table states 1048 closed(1), -- (p1) 1049 calling(2), -- (p2,p3,p5) 1050 open(3), -- (p4) 1051 clearing(4), -- (p6,p7) 1052 pvc(5), 1053 pvcResetting(6)} 1054 ACCESS read-write 1055 STATUS mandatory 1056 -- See ISO 8208, table 33 for (p) state table 1057 DESCRIPTION 1058 "The current status of this connection. 1059 Setting the connection to closed closes the 1060 connection (not for PVC, a PVC can not be 1061 set to closed). 1063 An entry in the closed state may be deleted 1064 or reused at the agent's convence. If the 1065 entry is kept in the closed state, the 1066 values of the parameters associated with the 1067 entry must be correct." 1068 ::= { x25CircuitEntry 5 } 1070 x25CircuitDirection OBJECT-TYPE 1071 SYNTAX INTEGER { 1072 incoming(1), 1073 outgoing(2) } 1074 ACCESS read-only 1075 STATUS mandatory 1076 DESCRIPTION 1077 "The direction of the call that established 1078 this connection." 1079 REFERENCE "10733 direction" 1080 ::= { x25CircuitEntry 6 } 1082 x25CircuitCallParamId OBJECT-TYPE 1083 SYNTAX OBJECT IDENTIFIER 1085 ACCESS read-write 1086 STATUS mandatory 1087 DESCRIPTION 1088 "This identifies the instance of the 1089 x25CallParmIndex for the entry in the 1090 x25callParm table which contains the call 1091 parameters in use with this call. The entry 1092 referenced must contain the values that are 1093 currently in use by the circuit rather than 1094 proposed values." 1095 ::= { x25CircuitEntry 7 } 1097 x25CircuitRemoteDteAddress OBJECT-TYPE 1098 SYNTAX X25Address 1099 ACCESS read-only 1100 STATUS mandatory 1101 DESCRIPTION 1102 "The address of the remote DTE for this 1103 connection." 1104 ::= { x25CircuitEntry 8 } 1106 x25CircuitCalledDteAddress OBJECT-TYPE 1107 SYNTAX X25Address 1108 ACCESS read-only 1109 STATUS mandatory 1110 DESCRIPTION 1111 "Destination DTE address used when the call 1112 was placed that established this 1113 connection." 1114 REFERENCE "10733 calledDTEAddress" 1115 ::= { x25CircuitEntry 9 } 1117 x25CircuitCallingDteAddress OBJECT-TYPE 1118 SYNTAX X25Address 1119 ACCESS read-only 1120 STATUS mandatory 1121 DESCRIPTION 1122 "The calling DTE address from the call 1123 packet. For outgoing calls, this will be 1124 the address of the local DTE for this 1125 connection." 1126 REFERENCE "10733 callingDTEAddress" 1127 ::= { x25CircuitEntry 10 } 1129 x25CircuitOriginallyCalledAddress OBJECT-TYPE 1130 SYNTAX X25Address 1131 ACCESS read-only 1132 STATUS mandatory 1133 DESCRIPTION 1134 "The originally called address." 1135 REFERENCE "10733 originallyCalledAddress" 1136 ::= { x25CircuitEntry 11 } 1138 -- X25 Circuit data flow statistics 1140 x25CircuitInOctets OBJECT-TYPE 1141 SYNTAX Counter 1142 ACCESS read-only 1143 STATUS mandatory 1144 DESCRIPTION 1145 "The number of octets of user data delivered 1146 to upper layer." 1147 REFERENCE "5.11 octetsReceivedCounter" 1148 ::= { x25CircuitEntry 12 } 1150 x25CircuitInPdus OBJECT-TYPE 1151 SYNTAX Counter 1152 ACCESS read-only 1153 STATUS mandatory 1154 DESCRIPTION 1155 "The number of PDUs received for this 1156 connection." 1157 REFERENCE "10733 5.11 dataPacketsReceived" 1158 ::= { x25CircuitEntry 13 } 1160 x25CircuitInRemotelyInitiatedResets OBJECT-TYPE 1161 SYNTAX Counter 1162 ACCESS read-only 1163 STATUS mandatory 1164 DESCRIPTION 1165 "The number of Resets received for this 1166 connection with cause code of DTE 1167 initiated." 1168 REFERENCE "10733 remotelyInitiatedResets" 1169 ::= { x25CircuitEntry 14 } 1171 x25CircuitInProviderInitiatedResets OBJECT-TYPE 1172 SYNTAX Counter 1173 ACCESS read-only 1174 STATUS mandatory 1175 DESCRIPTION 1176 "The number of Resets received for this 1177 connection with cause code other than DTE 1178 initiated." 1179 REFERENCE "10733 ProviderInitiatedResets" 1180 ::= { x25CircuitEntry 15 } 1182 x25CircuitInInterrupts OBJECT-TYPE 1183 SYNTAX Counter 1184 ACCESS read-only 1185 STATUS mandatory 1186 DESCRIPTION 1187 "The number of interrupt packets received 1188 for this connection." 1189 REFERENCE "10733 interruptPacketsReceived" 1190 ::= { x25CircuitEntry 16 } 1192 x25CircuitOutOctets OBJECT-TYPE 1193 SYNTAX Counter 1194 ACCESS read-only 1195 STATUS mandatory 1196 DESCRIPTION 1197 "The number of Octets of user data sent for 1198 this connection." 1199 REFERENCE "10733 5.11 octetsSentCounter" 1200 ::= { x25CircuitEntry 17 } 1202 x25CircuitOutPdus OBJECT-TYPE 1203 SYNTAX Counter 1204 ACCESS read-only 1205 STATUS mandatory 1206 DESCRIPTION 1207 "The number of packets sent for this 1208 connection." 1209 REFERENCE "10733 5.11 dataPacketsSent" 1210 ::= { x25CircuitEntry 18 } 1212 x25CircuitOutInterrupts OBJECT-TYPE 1213 SYNTAX Counter 1214 ACCESS read-only 1215 STATUS mandatory 1216 DESCRIPTION 1217 "The number of interrupt packets sent on 1218 this connection." 1219 REFERENCE "10733 interruptPacketsSent" 1220 ::= { x25CircuitEntry 19 } 1222 -- X25 Per Connection Timer Table 1223 x25CircuitDataRetransmissionTimeouts OBJECT-TYPE 1224 SYNTAX Counter 1225 ACCESS read-only 1226 STATUS mandatory 1227 DESCRIPTION 1228 "The number of times the T25 data 1229 retransmission timer expired for this 1230 connection." 1231 REFERENCE "10733 5.11 dataRetransmissionTimerExpiries" 1232 ::= { x25CircuitEntry 20 } 1234 x25CircuitResetTimeouts OBJECT-TYPE 1235 SYNTAX Counter 1236 ACCESS read-only 1237 STATUS mandatory 1238 DESCRIPTION 1239 "The number of times the T22 reset timer 1240 expired for this connection." 1241 REFERENCE "10733 5.11 resetTimeouts" 1242 ::= { x25CircuitEntry 21 } 1244 x25CircuitInterruptTimeouts OBJECT-TYPE 1245 SYNTAX Counter 1246 ACCESS read-only 1247 STATUS mandatory 1248 DESCRIPTION 1249 "The number of times the T26 Interrupt timer 1250 expired for this connection." 1251 REFERENCE "10733 interruptTimerExpiries" 1252 ::= { x25CircuitEntry 22 } 1254 -- ########################################################### 1255 -- The Cleared Circuit Table 1256 -- ########################################################### 1258 x25ClearedCircuitTable OBJECT-TYPE 1259 SYNTAX SEQUENCE OF X25ClearedCircuitEntry 1261 ACCESS not-accessible 1262 STATUS mandatory 1263 -- See ISO 8208 Section 12.2.3.1.1 and 12.2.3.1.2 1264 DESCRIPTION 1265 "A table of entries about closed circuits. 1266 Entries must be made in this table when ever 1267 circuits are closed and the close request or 1268 close indication packet contains a clearing 1269 cause other than DTE Originated or a 1270 Diagnostic code field other than Higher 1271 Layer Initiated disconnection-normal. An 1272 agent may optionally make entries for normal 1273 closes (to record closing facilities). 1275 Agents will delete the oldest entry in the 1276 table when adding a new entry would exceed 1277 agent resources. Agents are required to 1278 keep the last entry put in the table and may 1279 keep more entries." 1280 ::= { x25 4 } 1282 x25ClearedCircuitEntry OBJECT-TYPE 1283 SYNTAX X25ClearedCircuitEntry 1284 ACCESS not-accessible 1285 STATUS mandatory 1286 DESCRIPTION 1287 "Information about a cleared circuit." 1288 INDEX { x25ClearedCircuitIndex, 1289 x25ClearedCircuitPleIndex } 1290 ::= { x25ClearedCircuitTable 1 } 1292 X25ClearedCircuitEntry ::= SEQUENCE { 1293 x25ClearedCircuitIndex 1294 INTEGER, 1295 x25ClearedCircuitPleIndex 1296 INTEGER, 1297 x25ClearedCircuitTimeCleared 1298 TimeTicks, 1299 x25ClearedCircuitChannel 1300 INTEGER, 1301 x25ClearedCircuitCodes 1302 OCTET STRING, 1303 x25ClearedCircuitCalledAddress 1304 X25address, 1306 x25ClearedCircuitCallingAddress 1307 X25address, 1308 x25ClearedCircuitClearFacilities 1309 OCTET STRING 1310 } 1312 x25ClearedCircuitIndex OBJECT-TYPE 1313 SYNTAX INTEGER (1..65535) 1314 ACCESS read-only 1315 STATUS mandatory 1316 DESCRIPTION 1317 "An index that uniquely distinguishes one 1318 entry in the clearedCircuitTable from 1319 another. This index will start at 65535 and 1320 will decrease by one for each new entry 1321 added to the table. Upon reaching one, the 1322 index will reset to 65535. Because the 1323 index starts at 65535 and decreases, a 1324 manager may do a getnext on entry zero and 1325 obtain the most recent entry (with a minor 1326 exception when entry one is in use)." 1327 ::= { x25ClearedCircuitEntry 1 } 1329 x25ClearedCircuitPleIndex OBJECT-TYPE 1330 SYNTAX INTEGER (1..65535) 1331 ACCESS read-only 1332 STATUS mandatory 1333 DESCRIPTION 1334 "The value of the x25PleIndex which cleared 1335 the circuit that created the entry." 1336 ::= { x25ClearedCircuitEntry 2 } 1338 x25ClearedCircuitTimeCleared OBJECT-TYPE 1339 SYNTAX TimeTicks 1340 ACCESS read-only 1341 STATUS mandatory 1342 DESCRIPTION 1343 "The value of sysUpTime when the circuit was 1344 cleared." 1345 ::= { x25ClearedCircuitEntry 3 } 1347 x25ClearedCircuitChannel OBJECT-TYPE 1348 SYNTAX INTEGER (1..4096) 1349 ACCESS read-only 1351 STATUS mandatory 1352 DESCRIPTION 1353 "The channel number for the circuit that was 1354 cleared." 1355 ::= { x25ClearedCircuitEntry 4 } 1357 x25ClearedCircuitCodes OBJECT-TYPE 1358 SYNTAX OCTET STRING (SIZE (2)) 1359 ACCESS read-only 1360 STATUS mandatory 1361 -- See ISO 8208 Section 12.2.3.1.1 and 12.2.3.1.2 1362 DESCRIPTION 1363 "The Clearing Cause and Diagnostic Code from 1364 the clear request or clear indication packet 1365 the cleared the circuit." 1366 ::= { x25ClearedCircuitEntry 5 } 1368 x25ClearedCircuitCalledAddress OBJECT-TYPE 1369 SYNTAX X25address 1370 ACCESS read-only 1371 STATUS mandatory 1372 DESCRIPTION 1373 "The called address from the cleared 1374 circuit." 1375 ::= { x25ClearedCircuitEntry 6 } 1377 x25ClearedCircuitCallingAddress OBJECT-TYPE 1378 SYNTAX X25address 1379 ACCESS read-only 1380 STATUS mandatory 1381 DESCRIPTION 1382 "The calling address from the cleared 1383 circuit." 1384 ::= { x25ClearedCircuitEntry 7 } 1386 x25ClearedCircuitClearFacilities OBJECT-TYPE 1387 SYNTAX OCTET STRING (SIZE (0..109)) 1388 ACCESS read-only 1389 STATUS mandatory 1390 DESCRIPTION 1391 "The facilities field from the clear request 1392 or clear indication packet that cleared the 1393 circuit. A size of zero indicates no 1394 facilities were present." 1395 ::= { x25ClearedCircuitEntry 8 } 1397 -- ########################################################### 1398 -- The Call Parameter Table 1399 -- ########################################################### 1401 -- Default values for new connections 1403 x25CallParmTable OBJECT-TYPE 1404 SYNTAX SEQUENCE OF X25CallParmEntry 1405 ACCESS not-accessible 1406 STATUS mandatory 1407 DESCRIPTION 1408 "These objects contain the parameters that 1409 can be varied between X.25 calls. The 1410 entries in this table are independent of the 1411 PLE. There exists only one of these tables 1412 for the entire system. The indexes for the 1413 entries are independent of any PLE or any 1414 circuit. Other tables reference entries in 1415 this table. Entries in this table can be 1416 used for default PLE parameters, for 1417 parameters to use to place/answer a call, 1418 for the parameters currently in use for a 1419 circuit, or parameters that were used by a 1420 circuit." 1421 ::= { x25 5 } 1423 x25CallParmEntry OBJECT-TYPE 1424 SYNTAX X25CallParmEntry 1425 ACCESS not-accessible 1426 STATUS mandatory 1427 DESCRIPTION 1428 "Entries of x25CallParmTable." 1429 INDEX { x25CallParmIndex } 1430 ::= { x25CallParmTable 1 } 1432 X25CallParmEntry ::= SEQUENCE { 1433 x25CallParmIndex 1434 INTEGER, 1435 x25CallParmCallTimer 1436 INTEGER, 1437 x25CallParmResetTimer 1438 INTEGER, 1439 x25CallParmClearTimer 1440 INTEGER, 1441 x25CallParmInterruptTime 1442 INTEGER, 1443 x25CallParmResetCount 1444 INTEGER, 1445 x25CallParmClearCount 1446 INTEGER, 1447 x25CallParmWindowTimer 1448 INTEGER, 1449 x25CallParmDataRxmtTimer 1450 INTEGER, 1451 x25CallParmDataRxmtCount 1452 INTEGER, 1453 x25CallParmRejectTimer 1454 INTEGER, 1455 x25CallParmRejectCount 1456 INTEGER, 1457 x25CallParmInPacketSize 1458 INTEGER, 1459 x25CallParmOutPacketSize 1460 INTEGER, 1461 x25CallParmInWindowSize 1462 INTEGER, 1463 x25CallParmOutWindowSize 1464 INTEGER, 1465 x25CallParmAcceptReverseCharging 1466 INTEGER, 1467 x25CallParmProposeReverseCharging 1468 INTEGER, 1469 x25CallParmFastSelect 1470 INTEGER, 1471 x25CallParmInThruPutClasSize 1472 INTEGER, 1473 x25CallParmOutThruPutClasSize 1474 INTEGER, 1475 x25CallParmCug 1476 OCTET STRING, 1477 x25CallParmCugoa 1478 OCTET STRING, 1479 x25CallParmBcug 1480 OCTET STRING, 1481 x25CallParmNui 1482 DisplayString, 1483 x25CallParmChargingInfo 1484 INTEGER, 1485 x25CallParmRpoa 1486 OCTET STRING, 1488 x25CallParmTrnstDly 1489 INTEGER, 1490 x25CallParmCallingExt 1491 OCTET STRING, 1492 x25CallParmCalledExt 1493 OCTET STRING, 1494 x25CallParmInMinThuPutCls 1495 INTEGER, 1496 x25CallParmOutMinThuPutCls 1497 INTEGER, 1498 x25CallParmEndTrnsDly 1499 OCTET STRING, 1500 x25CallParmPriority 1501 OCTET STRING, 1502 x25CallParmProtection 1503 OCTET STRING, 1504 x25CallParmExptData 1505 INTEGER, 1506 x25CallParmUserData 1507 OCTET STRING, 1508 x25CallParmCallingNetworkFacilities 1509 OCTET STRING, 1510 x25CallParmCalledNetworkFacilities 1511 OCTET STRING 1512 } 1514 x25CallParmIndex OBJECT-TYPE 1515 SYNTAX INTEGER (1..2147483647) 1516 ACCESS read-write 1517 STATUS mandatory 1518 DESCRIPTION 1519 "A value that distinguishes this entry from 1520 another entry. Entries in this table are 1521 referenced from other objects. 1523 It is impossible to know what other objects 1524 in the MIB reference entries in the table by 1525 looking at this table. Because of this, 1526 changes to parameters should be accomplished 1527 by creating a new entry in this table and 1528 then changing the referencing table to 1529 identify the new entry. 1531 Entries in this table that are not 1532 referenced by any other object in the MIB 1534 maybe deleted at the convence of the agent. 1535 Care should be taken by the agent to give 1536 the NMS sufficient time to create a 1537 reference to newly created entries. 1539 Entries in this table can be created by 1540 setting a non-existent index instance. The 1541 agent should not allow a set request to 1542 modify an existing entry. This ensures two 1543 agents trying to create new entries will not 1544 over write each other. Two managers will 1545 not be able to create the same entry at the 1546 same time because, one will succeed and the 1547 other will fail. Once an entry has been 1548 created in this table, other objects can be 1549 set to reference them." 1550 ::= { x25CallParmEntry 1 } 1552 x25CallParmCallTimer OBJECT-TYPE 1553 SYNTAX INTEGER (0..1800000) 1554 ACCESS read-write 1555 STATUS mandatory 1556 -- The maximum time representable is 30 minutes. 1557 -- See ISO 8208 Section Section 5.2.1, table 26 1558 DESCRIPTION 1559 "The T21 Call timer in milliseconds. A 1560 value of zero means use the PLE default (the 1561 PLE may not reference a zero valued entry)." 1562 REFERENCE "10733 callTime" 1563 ::= { x25CallParmEntry 2 } 1565 x25CallParmResetTimer OBJECT-TYPE 1566 SYNTAX INTEGER (0..1800000) 1567 ACCESS read-write 1568 STATUS mandatory 1569 -- See ISO 8208 Section 8.1, table 26 1570 DESCRIPTION 1571 "The T22 Reset timer in milliseconds. A 1572 value of zero means use the PLE default (the 1573 PLE may not reference a zero valued entry)." 1574 REFERENCE "10733 resetTime" 1575 ::= { x25CallParmEntry 3 } 1577 x25CallParmClearTimer OBJECT-TYPE 1578 SYNTAX INTEGER (0..1800000) 1580 ACCESS read-write 1581 STATUS mandatory 1582 -- See ISO 8208 Section 5.5.1, table 26 1583 DESCRIPTION 1584 "The T23 Clear timer in milliseconds. A 1585 value of zero means use the PLE default (the 1586 PLE may not reference a zero valued entry)." 1587 REFERENCE "10733 clearTime" 1588 ::= { x25CallParmEntry 4 } 1590 x25CallParmInterruptTime OBJECT-TYPE 1591 SYNTAX INTEGER (0..2147483647) 1592 ACCESS read-write 1593 STATUS mandatory 1594 -- See ISO 8208 Section 6.8.1, table 26 1595 DESCRIPTION 1596 "The T26 Interrupt timer milliseconds. A 1597 value of zero means use the PLE default (the 1598 PLE may not reference a zero valued entry). 1599 A value of 2147483647 indicates interrupts 1600 are not being used." 1601 REFERENCE "10733 interruptTime" 1602 ::= { x25CallParmEntry 5 } 1604 x25CallParmResetCount OBJECT-TYPE 1605 SYNTAX INTEGER (0..65535) 1606 ACCESS read-write 1607 STATUS mandatory 1608 -- See section ISO 8208 8.1, table 27 1609 DESCRIPTION 1610 "The r22 Reset retransmission count. A 1611 value of zero means use the PLE default (the 1612 PLE may not reference a zero valued entry)." 1613 REFERENCE "10733 resetCount" 1614 ::= { x25CallParmEntry 6 } 1616 x25CallParmClearCount OBJECT-TYPE 1617 SYNTAX INTEGER (0..65535) 1618 ACCESS read-write 1619 STATUS mandatory 1620 -- See ISO 8208 Section 5.5.1, table 27 1621 DESCRIPTION 1622 "The r23 Clear retransmission count. A 1623 value of zero means use the PLE default (the 1624 PLE may not reference a zero valued entry)." 1626 REFERENCE "10733 clearCount" 1627 ::= { x25CallParmEntry 7 } 1629 x25CallParmWindowTimer OBJECT-TYPE 1630 SYNTAX INTEGER (0..2147483647) 1631 ACCESS read-write 1632 STATUS mandatory 1633 -- See ISO 8208 Section 11.2.2, table 26 1634 DESCRIPTION 1635 "The T24 window status transmission timer 1636 milliseconds. A value of zero means use the 1637 PLE default (the PLE may not reference a 1638 zero valued entry). A value of 2147483647 1639 indicates no window timer in use." 1640 REFERENCE "10733 5.10.1 windowTime (opt)" 1641 ::= { x25CallParmEntry 8 } 1643 x25CallParmDataRxmtTimer OBJECT-TYPE 1644 SYNTAX INTEGER (0..2147483647) 1645 ACCESS read-write 1646 STATUS mandatory 1647 -- See ISO 8208 Section 11.2.1, table 26 1648 DESCRIPTION 1649 "The T25 Data Retransmission timer in 1650 milliseconds. A value of zero means use the 1651 PLE default (the PLE may not reference a 1652 zero valued entry). A value of 2147483647 1653 indicates no data retransmission timer in 1654 use." 1655 REFERENCE "10733 5.10.1 dataRetransmissionTime (opt)" 1656 ::= { x25CallParmEntry 9 } 1658 x25CallParmDataRxmtCount OBJECT-TYPE 1659 SYNTAX INTEGER (0..65535) 1660 ACCESS read-write 1661 STATUS mandatory 1662 -- See ISO 8208 Section 11.2.1, table 27 1663 DESCRIPTION 1664 "The R25 Data retransmission count. A value 1665 of zero means use the PLE default (the PLE 1666 may not reference a zero valued entry). A 1667 value of 65535 indicates no data 1668 retransmission timer in use." 1669 REFERENCE "10733 5.10.1 dataRetransmissionCount (opt)" 1670 ::= { x25CallParmEntry 10 } 1672 x25CallParmRejectTimer OBJECT-TYPE 1673 SYNTAX INTEGER (0..2147483647) 1674 ACCESS read-write 1675 STATUS mandatory 1676 -- See ISO 8208 Section 13.4.1, table 26 1677 DESCRIPTION 1678 "The T27 Reject retransmission timer in 1679 milliseconds. A value of zero means use the 1680 PLE default (the PLE may not reference a 1681 zero valued entry). A value of 2147483647 1682 indicates no reject timer in use." 1683 REFERENCE "10733 5.10.1 dataRejectTime (opt)" 1684 ::= { x25CallParmEntry 11 } 1686 x25CallParmRejectCount OBJECT-TYPE 1687 SYNTAX INTEGER (0..65535) 1688 ACCESS read-write 1689 STATUS mandatory 1690 DESCRIPTION 1691 "The R27 reject retransmission count. A 1692 value of zero means use the PLE default (the 1693 PLE may not reference a zero valued entry). 1694 A value of 65535 indicates no reject timer 1695 in use." 1696 REFERENCE "10733 5.10.1 dataRejectCount (opt)" 1697 ::= { x25CallParmEntry 12 } 1699 x25CallParmInPacketSize OBJECT-TYPE 1700 SYNTAX INTEGER (0..4096) 1701 ACCESS read-write 1702 STATUS mandatory 1703 -- See ISO 8208 Section 15.2.2.1.1 1704 DESCRIPTION 1705 "The maximum receive packet size in octets 1706 for a connection. A size of zero means use 1707 the default size. The default size for the 1708 PLE default parameter is 128." 1709 REFERENCE "10733 proposedPacketSize" 1710 ::= { x25CallParmEntry 13 } 1712 x25CallParmOutPacketSize OBJECT-TYPE 1713 SYNTAX INTEGER (0..4096) 1714 ACCESS read-write 1715 STATUS mandatory 1716 -- See ISO 8208 Section 15.2.2.1.1 1718 DESCRIPTION 1719 "The maximum transmit packet size in octets 1720 for a connection. A size of zero means use 1721 the default size. The default size for the 1722 PLE default parameter is 128." 1723 REFERENCE "10733 proposedPacketSize" 1724 ::= { x25CallParmEntry 14 } 1726 x25CallParmInWindowSize OBJECT-TYPE 1727 SYNTAX INTEGER (0..127) 1728 ACCESS read-write 1729 STATUS mandatory 1730 -- See ISO 8208 Section 15.2.2.1.2 1731 DESCRIPTION 1732 "The receive window size for a connection. 1733 A size of zero means use the default size. 1734 The default size for the PLE default 1735 parameter is 2." 1736 REFERENCE "10733 proposedWindowSize" 1737 ::= { x25CallParmEntry 15 } 1739 x25CallParmOutWindowSize OBJECT-TYPE 1740 SYNTAX INTEGER (0..127) 1741 ACCESS read-write 1742 STATUS mandatory 1743 -- See ISO 8208 Section 15.2.2.1.2 1744 DESCRIPTION 1745 "The transmit window size for a connection. 1746 A size of zero means use the default size. 1747 The default size for the PLE default 1748 parameter is 2." 1749 REFERENCE "10733 proposedWindowSize" 1750 ::= { x25CallParmEntry 16 } 1752 x25CallParmAcceptReverseCharging OBJECT-TYPE 1753 SYNTAX INTEGER { 1754 default(1), 1755 accept(2), 1756 refuse(3)} 1757 ACCESS read-write 1758 STATUS mandatory 1759 DESCRIPTION 1760 "An enumeration defining if the PLE will 1761 accept or refuse charges. When used as the 1763 default parameters for a PLE, the value of 1764 default may not be used." 1765 REFERENCE "10733 acceptReverseCharging" 1766 ::= { x25CallParmEntry 17 } 1768 x25CallParmProposeReverseCharging OBJECT-TYPE 1769 SYNTAX INTEGER { 1770 default(1), 1771 reverse(2), 1772 local(3)} 1773 ACCESS read-write 1774 STATUS mandatory 1775 -- See ISO 8208 Section 15.2.2.6 1776 DESCRIPTION 1777 "An enumeration defining if the PLE should 1778 propose reverse or local charging. When 1779 used as the default parameters of a PLE, the 1780 default value may not be used." 1781 REFERENCE "10733 proposedPacketSize" 1782 ::= { x25CallParmEntry 18 } 1784 x25CallParmFastSelect OBJECT-TYPE 1785 SYNTAX INTEGER { 1786 default(1), 1787 notSpecified(2), 1788 fastSelect(3), 1789 restrictedFastResponse(4), 1790 noFastSelect(5)} 1791 ACCESS read-write 1792 STATUS mandatory 1793 -- Sec ISO 8208 Section 15.2.2.6 1794 DESCRIPTION 1795 "Expresses preference for use of fast select 1796 facility. When used as the default 1797 parameters for a PLE, the default value may 1798 not be used." 1799 REFERENCE "10733 fastSelect" 1800 ::= { x25CallParmEntry 19 } 1802 x25CallParmInThruPutClasSize OBJECT-TYPE 1803 SYNTAX INTEGER { 1804 tcReserved1 (1), 1805 tcReserved2 (2), 1806 tc75 (3), 1808 tc150 (4), 1809 tc300 (5), 1810 tc600 (6), 1811 tc1200 (7), 1812 tc2400 (8), 1813 tc4800 (9), 1814 tc9600 (10), 1815 tc19200 (11), 1816 tc48000 (12), 1817 tc64000 (13), 1818 tcReserved14 (14), 1819 tcReserved15 (15), 1820 tcReserved0 (16), 1821 tcNone (17), 1822 tcDefault (18) 1823 } 1824 ACCESS read-write 1825 STATUS mandatory 1826 -- See ISO 8208 Section 15.2.2.2, table 18 1827 DESCRIPTION 1828 "The incoming throughput class to negotiate. 1829 A value of tcDefault means use the PLE 1830 default, the PLE may not use the tcDefault 1831 value. A value of tcNone means no through 1832 put class requested." 1833 ::= { x25CallParmEntry 20 } 1835 x25CallParmOutThruPutClasSize OBJECT-TYPE 1836 SYNTAX INTEGER { 1837 tcReserved1 (1), 1838 tcReserved2 (2), 1839 tc75 (3), 1840 tc150 (4), 1841 tc300 (5), 1842 tc600 (6), 1843 tc1200 (7), 1844 tc2400 (8), 1845 tc4800 (9), 1846 tc9600 (10), 1847 tc19200 (11), 1848 tc48000 (12), 1849 tc64000 (13), 1850 tcReserved14 (14), 1851 tcReserved15 (15), 1852 tcReserved0 (16), 1854 tcNone (17), 1855 tcDefault (18) 1856 } 1857 ACCESS read-write 1858 STATUS mandatory 1859 -- See ISO 8208 Section 15.2.2.2, table 18 1860 DESCRIPTION 1861 "The outgoing throughput class to negotiate. 1862 A value of tcDefault means use the PLE 1863 default, the PLE may not use the tcDefault 1864 value. A value of tcNone means no through 1865 put class requested." 1866 ::= { x25CallParmEntry 21 } 1868 x25CallParmCug OBJECT-TYPE 1869 SYNTAX OCTET STRING (SIZE(0..4)) 1870 ACCESS read-write 1871 STATUS mandatory 1872 -- See ISO 8208 Section 15.2.2.3 1873 DESCRIPTION 1874 "The Closed User Group to specify. This 1875 consists of 2 or 4 octets containing the 1876 characters 0 through 9. A zero length 1877 string indicates no facility requested. A 1878 string length of three containing the 1879 characters DEF means use the PLE default, 1880 (the PLE may not reference an entry of 1881 DEF.)" 1882 ::= { x25CallParmEntry 22 } 1884 x25CallParmCugoa OBJECT-TYPE 1885 SYNTAX OCTET STRING (SIZE(0..4)) 1886 ACCESS read-write 1887 STATUS mandatory 1888 -- See ISO 8208 Section 15.2.2.4 1889 DESCRIPTION 1890 "The Closed User Group with Outgoing Access 1891 to specify. This consists of 2 or 4 octets 1892 containing the characters 0 through 9. A 1893 string length of three containing the 1894 characters DEF means use the PLE default 1895 (the PLE may not reference an entry of DEF). 1896 A zero length string indicates no facility 1898 requested." 1899 ::= { x25CallParmEntry 23 } 1901 x25CallParmBcug OBJECT-TYPE 1902 SYNTAX OCTET STRING (SIZE(0..3)) 1903 ACCESS read-write 1904 STATUS mandatory 1905 -- See ISO 8208 Section 15.2.2.5 1906 DESCRIPTION 1907 "The Bilateral Closed User Group to specify. 1908 This consists of 2 octets containing the 1909 characters 0 through 9. A string length of 1910 three containing the characters DEF means 1911 use the PLE default (the PLE may not 1912 reference an entry of DEF). A zero length 1913 string indicates no facility requested." 1914 ::= { x25CallParmEntry 24 } 1916 x25CallParmNui OBJECT-TYPE 1917 SYNTAX DisplayString (SIZE(0..108)) 1918 ACCESS read-write 1919 STATUS mandatory 1920 -- See ISO 8208 Section 15.2.2.7 1921 DESCRIPTION 1922 "The Network User Identifier facility. A 1923 zero length string indicates no facility 1924 requested. This value is ignored for the 1925 PLE default parameters entry." 1926 ::= { x25CallParmEntry 25 } 1928 x25CallParmChargingInfo OBJECT-TYPE 1929 SYNTAX INTEGER { 1930 default(1), 1931 noFacility(2), 1932 noChargingInfo(3), 1933 chargingInfo(4) } 1934 ACCESS read-write 1935 STATUS mandatory 1936 -- See ISO 8208 Section 15.2.2.8 1937 DESCRIPTION 1938 "The charging Information facility. The 1939 default PLE parameters entry may not use the 1940 default value." 1941 ::= { x25CallParmEntry 26 } 1943 x25CallParmRpoa OBJECT-TYPE 1944 SYNTAX OCTET STRING (SIZE(0..108)) 1945 ACCESS read-write 1946 STATUS mandatory 1947 -- See ISO 8208, section 15.2.2.9 1948 DESCRIPTION 1949 "The RPOA facility. The octet string 1950 contains n * 4 sequences of the characters 1951 0-9 to specify a facility with n entries. 1952 The octet string containing the 3 characters 1953 DEF specifies use of the PLE default (the 1954 entry for the PLE default may not contain 1955 DEF). A zero length string indicates no 1956 facility requested." 1957 ::= { x25CallParmEntry 27 } 1959 x25CallParmTrnstDly OBJECT-TYPE 1960 SYNTAX INTEGER (0..65537) 1961 ACCESS read-write 1962 STATUS mandatory 1963 -- See ISO 8208, Section 15.2.2.13 1964 DESCRIPTION 1965 "The Transit Delay Selection and Indication 1966 value. A value of 65536 indicates no 1967 facility requested. A value of 65537 means 1968 use the PLE default (the PLE default 1969 parameters entry may not use the value 1970 65537). The value 65535 may only be used to 1971 indicate the value in use by a circuit." 1972 ::= { x25CallParmEntry 28 } 1974 -- The following parameters are for CCITT facilities. 1976 x25CallParmCallingExt OBJECT-TYPE 1977 SYNTAX OCTET STRING (SIZE(0..43)) 1978 ACCESS read-write 1979 STATUS mandatory 1980 -- See ISO 8208 Section 15.3.2.1 1981 DESCRIPTION 1982 "The Calling Extension facility. This 1983 contains one of the following: 1985 The 3 characters PBD followed by up to 40 1987 characters from the set 0-9; the numeric 1988 characters are encoded in the facility using 1989 a Preferred binary encoding of decimal. 1991 The 3 characters PBB followed by up to 40 1992 characters from the set 0-9; the numeric 1993 characters are encoded in the facility using 1994 a Preferred binary encoding of binary. 1996 The 3 characters BCD followed by up to 40 1997 characters from the set 0-9; the characters 1998 are encoded in the facility as binary coded 1999 decimal. 2001 A value containing the three character DEF 2002 means use the PLE default, (the entry for 2003 the PLE default parameters may not use the 2004 value DEF). 2006 A zero length string indicates no facility 2007 requested." 2008 ::= { x25CallParmEntry 29 } 2010 x25CallParmCalledExt OBJECT-TYPE 2011 SYNTAX OCTET STRING (SIZE(0..43)) 2012 ACCESS read-write 2013 STATUS mandatory 2014 -- See ISO 8208 Section 15.3.2.2 2015 DESCRIPTION 2016 "The Called Extension facility. This 2017 contains one of the following: 2019 The 3 characters PBD followed by up to 40 2020 characters from the set 0-9; the numeric 2021 characters are encoded in the facility using 2022 a Preferred binary encoding of decimal. 2024 The 3 characters PBB followed by up to 40 2025 characters from the set 0-9; the numeric 2026 characters are encoded in the facility using 2027 a Preferred binary encoding of binary. 2029 The 3 characters BCD followed by up to 40 2030 characters from the set 0-9; the characters 2031 are encoded in the facility as binary coded 2033 decimal. 2035 A value containing the three character DEF 2036 means use the PLE default, (the entry for 2037 the PLE default parameters may not use the 2038 value DEF). 2040 A zero length string indicates no facility 2041 requested." 2042 ::= { x25CallParmEntry 30 } 2044 x25CallParmInMinThuPutCls OBJECT-TYPE 2045 SYNTAX INTEGER (0..17) 2046 ACCESS read-write 2047 STATUS mandatory 2048 -- See ISO 8208 Section 15.3.2.3 2049 DESCRIPTION 2050 "The minimum input throughput Class. A 2051 value of 16 means use the PLE default (the 2052 PLE parameters entry may not use this 2053 value). A value of 17 indicates no facility 2054 requested." 2055 ::= { x25CallParmEntry 31 } 2057 x25CallParmOutMinThuPutCls OBJECT-TYPE 2058 SYNTAX INTEGER (0..17) 2059 ACCESS read-write 2060 STATUS mandatory 2061 -- See ISO 8208 Section 15.3.2.3 2062 DESCRIPTION 2063 "The minimum output throughput Class. A 2064 value of 16 means use the PLE default (the 2065 PLE parameters entry may not use this 2066 value). A value of 17 indicates no facility 2067 requested." 2068 ::= { x25CallParmEntry 32 } 2070 x25CallParmEndTrnsDly OBJECT-TYPE 2071 SYNTAX OCTET STRING (SIZE(0..6)) 2072 ACCESS read-write 2073 STATUS mandatory 2074 -- See ISO 8208 Section 15.3.2.4 2075 DESCRIPTION 2076 "The End-to-End Transit Delay to negotiate. 2077 An octet string of length 2, 4, or 6 2079 contains the facility encoded as specified 2080 in ISO/IEC 8208 section 15.3.2.4. An octet 2081 string of length 3 containing the three 2082 character DEF means use the PLE default (the 2083 entry for the PLE default can not contain 2084 the characters DEF). A zero length string 2085 indicates no facility requested." 2086 ::= { x25CallParmEntry 33 } 2088 x25CallParmPriority OBJECT-TYPE 2089 SYNTAX OCTET STRING (SIZE(0..6)) 2090 ACCESS read-write 2091 STATUS mandatory 2092 -- See ISO 8208 Section 15.3.2.5 2093 DESCRIPTION 2094 "The priority facility to negotiate. The 2095 octet string encoded as specified in ISO/IEC 2096 8208 section 15.3.2.5. A zero length string 2097 indicates no facility requested. The entry 2098 for the PLE default parameters must be zero 2099 length." 2100 ::= { x25CallParmEntry 34 } 2102 x25CallParmProtection OBJECT-TYPE 2103 SYNTAX OCTET STRING (SIZE(0..108)) 2104 ACCESS read-write 2105 STATUS mandatory 2106 -- See ISO 8208 Section 15.3.2.5 2107 DESCRIPTION 2108 "The OCTET STRING contains the following: 2110 The first 3 octets of the string contain the 2111 3 characters SRC, DST, or GBL to represent a 2112 source-address specific, destination-address 2113 specific, or globally unique protection 2114 facility. Following that are a string of 2115 the characters 0-9 containing the protection 2116 level. 2118 This may optionally be followed by the 3 2119 characters MIN and another string of the 2120 characters 0-9 contining the lowest 2121 acceptable level. 2123 An octet string containing the 3 characters 2124 DEF means use the PLE default (the entry for 2125 the PLE default parameters may not use the 2126 value DEF). 2128 A zero length string mean no facility 2129 requested." 2130 ::= { x25CallParmEntry 35 } 2132 x25CallParmExptData OBJECT-TYPE 2133 SYNTAX INTEGER { 2134 default(1), 2135 noExpeditedData(2), 2136 expeditedData(3) } 2137 ACCESS read-write 2138 STATUS mandatory 2139 DESCRIPTION 2140 "The Expedited Data facility to negotiate. 2141 The entry for the PLE default parameters may 2142 not have the value default." 2143 ::= { x25CallParmEntry 36 } 2145 x25CallParmUserData OBJECT-TYPE 2146 SYNTAX OCTET STRING (SIZE (0..128)) 2147 ACCESS read-write 2148 STATUS mandatory 2149 -- See ISO 8208 Section 12.2.1.1.6, 12.2.1.2 2150 DESCRIPTION 2151 "The call user data. A zero length string 2152 indicates no call user data. The entry for 2153 the PLE default parameters must be zero 2154 length." 2155 ::= { x25CallParmEntry 37 } 2157 x25CallParmCallingNetworkFacilities OBJECT-TYPE 2158 SYNTAX OCTET STRING (SIZE (0..108)) 2159 ACCESS read-write 2160 STATUS mandatory 2161 -- See ISO 8206 Section 15.1, category b 2162 DESCRIPTION 2163 "The calling network facilities. The 2164 facilities are encoded here exactly as 2165 encoded in the call packet. These 2167 facilities do not include the marker 2168 facility code. 2170 A zero length string in the entry for the 2171 parameter to use when establishing a circuit 2172 means use the PLE default. A zero length 2173 string in the entry for PLE default 2174 parameters indicates no default facilities." 2175 ::= { x25CallParmEntry 38 } 2177 x25CallParmCalledNetworkFacilities OBJECT-TYPE 2178 SYNTAX OCTET STRING (SIZE (0..108)) 2179 ACCESS read-write 2180 STATUS mandatory 2181 -- See ISO 8206 Section 15.1, category c 2182 DESCRIPTION 2183 "The called network facilities. The 2184 facilities are encoded here exactly as 2185 encoded in the call packet. These 2186 facilities do not include the marker 2187 facility code. 2189 A zero length string in the entry for the 2190 parameter to use when establishing a circuit 2191 means use the PLE default. A zero length 2192 string in the entry for PLE default 2193 parameters indicates no default facilities." 2194 ::= { x25CallParmEntry 39 } 2196 -- X.25 Protocol Version Identifiers 2198 x25ProtocolVersion OBJECT IDENTIFIER 2199 ::= { x25 6 } 2201 -- X.25 CCITT 1976 version. 2202 x25protocolCcittV1976 OBJECT IDENTIFIER 2203 ::= { x25ProtocolVersion 1 } 2205 -- X.25 CCITT 1980 version. 2206 x25protocolCcittV1980 OBJECT IDENTIFIER 2207 ::= { x25ProtocolVersion 2 } 2209 -- X.25 CCITT 1984 version. 2211 x25protocolCcittV1984 OBJECT IDENTIFIER 2212 ::= { x25ProtocolVersion 3 } 2214 -- X.25 CCITT 1988 version. 2215 x25protocolCcittV1988 OBJECT IDENTIFIER 2216 ::= { x25ProtocolVersion 4 } 2218 -- X.25 1987 version of ISO 8208. 2219 x25protocolIso8208V1987 OBJECT IDENTIFIER 2220 ::= { x25ProtocolVersion 5 } 2222 -- X.25 1989 version of ISO 8208. 2223 x25protocolIso8208V1989 OBJECT IDENTIFIER 2224 ::= { x25ProtocolVersion 6 } 2226 -- ########################################################### 2228 END 2229 7. Acknowledgements 2231 This document was produced by the x25mib working group: 2233 Fred Baker, ACC 2234 Art Berggreen, ACC 2235 Frank Bieser 2236 Charles Carvalho, ACC 2237 Angela Chen, HP 2238 Tom Daniel, Spider Systems 2239 Chuck Davin, MIT 2240 Doug Geller, Data General 2241 Herve Goguely, LIR Corp 2242 Andy Goldthorpe, british-telecom 2243 David Gurevich, 2244 Richard Fox, Synoptics 2245 Steve Huston, Process Software Corporation 2246 Frank Kastenholz, Clearpoint 2247 Zbigniew Kiel 2248 Cheryl Krupezak, Georgia Tech 2249 Mats Lindstrom, Diab Data AB 2250 Andrew Malis, BBN 2251 Evan McGinnis, 3Com 2252 Gary (G.P.)Mussar, BNR 2253 Karen Quidley, Data General 2254 Randy Pafford, Data General 2255 Ragnar Paulson, The Software Group Limited 2256 Dave Perkins, Synoptics 2257 Walter Pinkarschewsky, DEC 2258 Paul S. Rarey, DHL Systems Inc. 2259 Jim Roche, Newbridge Research 2260 Philippe Roger, LIR Corp. 2261 Mike Shand, DEC 2262 Bob Stewart, Xyplex 2263 Tom Sullivan, Data General 2264 Rodney Thayer, Sable Technology Corporation 2265 Mark Therieau, Microcom 2266 Jane Thorn, Data General 2267 Dean Throop, Data General 2268 Mike Zendels, Data General 2270 In addition, the contributions of the following individuals 2271 are also acknowledged: 2273 John Harper, DEC 2274 Chairman of the ISO committee for 2275 Network Level Management Information 2277 8. References 2279 [1] M.T. Rose and K. McCloghrie, "Structure and 2280 Identification of Management Information for TCP/IP-based 2281 internets", RFC 1155, Network Information Center, SRI 2282 International, Menlo Park, California, (May, 1990). 2284 [2] K. McCloghrie and M.T. Rose, "Management Information Base 2285 for Network Management of TCP/IP-based internets", RFC 2286 1156, Network Information Center, SRI International, 2287 Menlo Park, California, (May, 1990). 2289 [3] J.D. Case, M.S. Fedor, M.L. Schoffstall, and J.R. Davin, 2290 "Simple Network Management Protocol", RFC 1157, Network 2291 Information Center, SRI International, Menlo Park, 2292 California, (May, 1990). 2294 [4] M.T. Rose, K. McCloghrie (editors), "Towards Concise MIB 2295 Definitions", RFC 1212, Network Information Center, SRI 2296 International, Menlo Park, California, (March, 1991) 2298 [5] M.T. Rose (editor), "Management Information Base for 2299 Network Management of TCP/IP-based internets", RFC 1213. 2300 Network Information Center, SRI International, Menlo 2301 Park, California, (March, 1991). 2303 [6] "Information processing systems - Open Systems 2304 Interconnection - Specification of Abstract Syntax 2305 Notation One (ASN.1)", International Organization for 2306 Standardization. International Standard 8824, (December, 2307 1987). 2309 [7] "Information processing systems - Open Systems 2310 Interconnection - Specification of Basic Encoding Rules 2311 for Abstract Notation One (ASN.1)", International 2312 Organization for Standardization. International Standard 2313 8825, (December, 1987). 2315 [8] B. Stewart (editor), "Definitions of Managed Objects for 2316 RS-232-like Hardware Devices", Internet Draft, Internet 2317 Engineering Task Force, (December, 1990) 2319 [9] D. Throop (editor), "SNMP MIB extension for LAPB", 2320 Internet Draft, Internet Engineering Task Force, 2321 (February, 1992) 2323 [10] "Information technology - - Data communication - X.25 2324 Packet layer Protocol for Data Terminal Equipment", 2325 International Organization for Standardization, 2326 International Standard 8208 (March, 1990) 2328 [11] "Information Technology - Telecommunications and 2329 information exchange between systems - Elements of 2330 Management Information Related to OSI network Layer 2331 Standards", Committee Draft International Standard 10733, 2332 (November, 1990) 2334 Table of Contents 2336 1 Status of this Memo ................................... 1 2337 1.1 Revision History .................................... 1 2338 February 1992 .......................................... 1 2339 October 1992 ........................................... 2 2340 June 1991 .............................................. 3 2341 April 1991 ............................................. 3 2342 2 Abstract .............................................. 3 2343 3 The Network Management Framework ...................... 3 2344 4 Objects ............................................... 4 2345 4.1 Format of Definitions ............................... 4 2346 5 Overview .............................................. 5 2347 5.1 Informal Overview ................................... 5 2348 5.2 Textual Conventions ................................. 6 2349 5.3 Structure of MIB .................................... 6 2350 6 Object Definitions .................................... 8 2351 7 Acknowledgements ...................................... 52 2352 8 References ............................................ 54