Internet Draft IP over X.25 MIB February 1992 SNMP MIB extension for IP over X.25 February 24, 1992 Dean D. Throop Data General Corporation 62 Alexander Dr. Research Triangle Park, NC 27709 throop@dg-rtp.dg.com 1. Status of this Memo This document was produced by the x25mib working group. Eventually this document will be submitted to the RFC editor as an extension to the SNMP MIB. Distribution of this memo is unlimited. Please send comments to the x25mib working group at: x25mib@dg-rtp.dg.com 1.1. Revision History February 1992 The February 1992 release (Editor's Internal Reference Number 1.17) made the following changes: The ioxInfoDefaultParamId object was added to the ioxInfoTable. The ioxConX25Channel object was deleted from the ioxConTable and replaced with the ioxConX25CircuitId object. The ioxConX25Address object was added to the ioxConTable. D. Throop [Page 1] Internet Draft IP over X.25 MIB February 1992 The ioxConX25FcltyIndex, ioxConX25fcltyCcittIndex, and ioxConX25CallParamIndex objects were deleted from the ioxConTable and replaced with the ioxConX25CallParamId object. The ioxConEncapsulation and ioxConHoldDownTimer objects were added to the ioxConTable. The text at the beginning of the document was changed. The references were changed to match the new text. October 1991 The October 91 revision of this document (Editor's internal reference 1.14) had the following changes: The object ioxInfoAddressXlationFailures was split into ioxInfoIpToX25LookupFailures and ioxInfoX25ToIpLookupFailures. The objects ioxInfoLastFailedIpAddress and ioxInfoLastFailedX25Address were added. This provides information to allow for correction of errors as well as detection. The objects ioxConX25FcltyIndex, ioxConX25fcltyCcittIndex, and ioxConX25CallParamIndex were added. June 1991 The June revision of this document was synthesized from various ideas on how to manage IP over X.25. This initial release of this document serves as a basis of discussion in the X25mib working group. 2. Abstract This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP- based internets. In particular, it defines objects for managing IP traffic carried over X.25. The objects defined here, along with the objects in the "SNMP MIB extension for the Packet Layer of X.25"[10], "SNMP MIB extension for LAPB"[9], and the "Definitions of Managed Objects for RS-232- D. Throop [Page 2] Internet Draft IP over X.25 MIB February 1992 like Hardware Devices"[8], combine to allow management of IP traffic over an X.25 protocol stack. This memo does not specify a standard for the Internet community. D. Throop [Page 3] Internet Draft IP over X.25 MIB February 1992 3. The Network Management Framework The Internet-standard Network Management Framework consists of three components. These components give the rules for defining objects, the definitions of objects, and the protocol for manipulating objects. The network management framework structures objects in an abstract information tree. The branches of the tree name objects and the leaves of the tree contain the values manipulated to effect management. This tree is called the Management Information Base or MIB. The concepts of this tree are given in RFC 1155 "The Structure of Management Information" or SMI [1]. The SMI defines the trunk of the tree and the types of objects used when defining the leaves. RFC 1212, "Towards Concise MIB Definitions" [4], defines a more concise description mechanism that preserves all the principals of the SMI. The core MIB definitions for the Internet suite of protocols can be found in RFC 1156 [2] "Management Information Base for Network Management of TCP/IP-based internets". RFC 1213 [5] defines MIB-II, an evolution of MIB-I with changes to incorporate implementation experience and new operational requirements. RFC 1157 [3] defines the SNMP protocol itself. The protocol defines how to manipulate the objects in a remote MIB. The tree structure of the MIB allows new objects to be defined for the purpose of experimentation and evaluation. 4. Objects The definition of an object in the MIB requires an object name and type. Object names and types are defined using the subset of Abstract Syntax Notation One (ASN.1) [6] defined in the SMI [1]. Objects are named using ASN.1 object identifiers, administratively assigned names, to specify object types. The object name, together with an optional object instance, uniquely identifies a specific instance of an object. For human convenience, we often use a textual string, termed the OBJECT DESCRIPTOR, to also refer to objects. D. Throop [Page 4] Internet Draft IP over X.25 MIB February 1992 Objects also have a syntax that defines the abstract data structure corresponding to that object type. The ASN.1 language [6] provides the primitives used for this purpose. The SMI [1] purposely restricts the ASN.1 constructs which may be used for simplicity and ease of implementation. The encoding of an object type simply describes how to represent an object using ASN.1 encoding rules [7], for purposes of dealing with the SNMP protocol. 4.1. Format of Definitions Section 6 contains the specification of all object types contained in this MIB module. The object types are defined using the conventions defined in the SMI, as amended by the extensions specified in "Towards Concise MIB Definitions" [4]. D. Throop [Page 5] Internet Draft IP over X.25 MIB February 1992 5. Overview Instances of the objects defined below represent attributes of an X.25 interface used to carry IP traffic. X.25 interfaces are identified by an ifType object in the Internet-standard MIB [5] of ddn-x25 or rfc877-x25. The relationship between the objects defined here and an interface as defined in the context of the Internet-standard MIB [5] is one-to-one. As such, the value of an ifIndex object instance can be directly used to identify corresponding instances of the objects defined below. D. Throop [Page 6] Internet Draft IP over X.25 MIB February 1992 6. Definitions RFCiox-MIB DEFINITIONS ::= BEGIN -- (Editors Internal Reference 1.40) IMPORTS Counter, experimental, IpAddress FROM RFC1155-SMI OBJECT-TYPE FROM RFC-1212 X25address FROM RFCX25Pk-MIB; -- IP over X.25 MIB -- DO NOT USE THIS EXPERIMENTAL NUMBER. iox OBJECT IDENTIFIER ::= { experimental 12345678 } -- This experimental number is an -- invalid placeholder. -- DO NOT USE THIS EXPERIMENTAL NUMBER. ioxInfoTable OBJECT-TYPE SYNTAX SEQUENCE OF IoxInfoEntry ACCESS not-accessible STATUS mandatory DESCRIPTION "Status information and control variables for IP over X.25." ::= { iox 1 } ioxInfoEntry OBJECT-TYPE SYNTAX IoxInfoEntry ACCESS not-accessible STATUS mandatory DESCRIPTION "General values for a specific X.25 interface carrying IP packets." INDEX { ioxInfoIndex } ::= { ioxInfoTable 1 } IoxInfoEntry ::= SEQUENCE { D. Throop [Page 7] Internet Draft IP over X.25 MIB February 1992 ioxInfoIndex INTEGER, ioxInfoIpToX25LookupFailures Counter, ioxInfoLastFailedIpAddress IpAddress, ioxInfoX25ToIpLookupFailures Counter, ioxInfoLastFailedX25Address X25address, ioxInfoRefusedConnections Counter, ioxInfoConnectionMaximum INTEGER, ioxInfoDefaultParamId OBJECT IDENTIFIER } ioxInfoIndex OBJECT-TYPE SYNTAX INTEGER (1..65535) ACCESS read-only STATUS mandatory DESCRIPTION "An index value that uniquely identifies the X.25 interface carrying IP Packets. This value will match the ifIndex entry identifying the MIB-II ifTable objects for that interface." ::= { ioxInfoEntry 1 } ioxInfoIpToX25LookupFailures OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "The number of IP to X.25 address translation attempts for this interface that failed to find a corresponding X.25 address." ::= { ioxInfoEntry 2 } ioxInfoLastFailedIpAddress OBJECT-TYPE SYNTAX IpAddress ACCESS read-only STATUS mandatory D. Throop [Page 8] Internet Draft IP over X.25 MIB February 1992 DESCRIPTION "The last IP address that failed to find a corresponding X.25 address." ::= { ioxInfoEntry 3 } ioxInfoX25ToIpLookupFailures OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "The number of X.25 to IP address translation attempts for this interface that failed to find a corresponding IP address." ::= { ioxInfoEntry 4 } ioxInfoLastFailedX25Address OBJECT-TYPE SYNTAX X25address ACCESS read-only STATUS mandatory DESCRIPTION "The last X.25 address that failed to find a corresponding IP address." ::= { ioxInfoEntry 5 } ioxInfoRefusedConnections OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "The number of connections that were refused by this interface." ::= { ioxInfoEntry 6 } ioxInfoConnectionMaximum OBJECT-TYPE SYNTAX INTEGER (1..4096) ACCESS read-write STATUS mandatory DESCRIPTION "The maximum number of X.25 channels that can be open at one time for this interface." ::= { ioxInfoEntry 7 } ioxInfoDefaultParamId OBJECT-TYPE SYNTAX OBJECT IDENTIFIER ACCESS read-write D. Throop [Page 9] Internet Draft IP over X.25 MIB February 1992 STATUS mandatory DESCRIPTION "This identifies the instance of the index in the ioxConTable for the default parameters to use with this interface. The entry identified by this object may have an IP address of 0.0.0.0 and a zero length X.25 address. These default parameters are used with connections to such hosts that do not have entries in the ioxConTable. Such connections occur when using ddn-x25 IP-X.25 address mapping or when accepting connections from other hosts not in the ioxConTable." ::= { ioxInfoEntry 8 } ioxConTable OBJECT-TYPE SYNTAX SEQUENCE OF IoxConEntry ACCESS not-accessible STATUS mandatory DESCRIPTION "The information available about possible or existing X.25 connections carrying IP traffic for an interface. This table contains the IP to X.25 address mappings for rfc877-x25 interfaces. For ddn-x25 interfaces, it only contains entries for default parameters and existing connections." ::= { iox 2 } ioxConEntry OBJECT-TYPE SYNTAX IoxConEntry ACCESS not-accessible STATUS mandatory DESCRIPTION "Per connection information." INDEX { ioxConIfIndex } ::= { ioxConTable 1 } D. Throop [Page 10] Internet Draft IP over X.25 MIB February 1992 IoxConEntry ::= SEQUENCE { ioxConIfIndex INTEGER, ioxConIpAddress IpAddress, ioxConX25Address X25address, ioxConX25CircuitId OBJECT IDENTIFIER, ioxConMaximumIdleTimer INTEGER, ioxConMinimumOpenTimer INTEGER, ioxConHoldDownTimer INTEGER, ioxConX25CallParamId OBJECT IDENTIFIER, ioxConEncapsulation INTEGER } ioxConIfIndex OBJECT-TYPE SYNTAX INTEGER (1..65535) ACCESS read-write STATUS mandatory DESCRIPTION "An index value that distinguished one entry from another. This index is independent of any other index. A new group can be created in the table by setting the value of this index. The agent must not allow an already existing entry to be written." ::= { ioxConEntry 1 } ioxConIpAddress OBJECT-TYPE SYNTAX IpAddress ACCESS read-write STATUS mandatory DESCRIPTION "The IP address of the remote host mapped by this table entry. An IP address of 0.0.0.0 indicates the remote IP address is unknown or unspecified." D. Throop [Page 11] Internet Draft IP over X.25 MIB February 1992 ::= { ioxConEntry 2 } ioxConX25Address OBJECT-TYPE SYNTAX X25address ACCESS read-write STATUS mandatory DESCRIPTION "The X.25 address of the remote host mapped by this table entry. A zero length string indicates the X.25 address is unspecified." ::= { ioxConEntry 3 } ioxConX25CircuitId OBJECT-TYPE SYNTAX OBJECT IDENTIFIER ACCESS read-only STATUS mandatory DESCRIPTION "This object identifies the instance of the index for the X.25 circuit that connects to the remote host mapped by this table entry. A value of NULL {0 0} indicates no connection currently active. For multiple connections, this identifies the index of a multiplexing table entry for the connections." ::= { ioxConEntry 4 } ioxConMaximumIdleTimer OBJECT-TYPE SYNTAX INTEGER (1..2147483647) ACCESS read-write STATUS mandatory DESCRIPTION "The maximum time in milliseconds this host will let the connection be idle before closing the connection. A value of 2147483647 indicates no timer." ::= { ioxConEntry 5 } ioxConMinimumOpenTimer OBJECT-TYPE SYNTAX INTEGER (0..18000000) ACCESS read-write STATUS mandatory DESCRIPTION "The minimum time in milliseconds the host will keep the connection open before D. Throop [Page 12] Internet Draft IP over X.25 MIB February 1992 allowing it to be closed. A value of zero indicates no timer." ::= { ioxConEntry 6 } ioxConHoldDownTimer OBJECT-TYPE SYNTAX INTEGER (0..2147483647) ACCESS read-write STATUS mandatory DESCRIPTION "The hold down timer in milliseconds. This is the minimum amount of time to wait before trying another call to a host that was previously unsuccessful. A value of 2147483647 indicates the host will not be retried. " ::= { ioxConEntry 7 } ioxConX25CallParamId OBJECT-TYPE SYNTAX OBJECT IDENTIFIER ACCESS read-write STATUS mandatory DESCRIPTION "The instance of the index object in the x25CallParmTable for the X.25 call parameter used to communicate with the remote host. A value of NULL {0 0} indicates no call parameters specified." ::= { ioxConEntry 8 } ioxConEncapsulation OBJECT-TYPE SYNTAX INTEGER { snap(1), -- Hex 80 clnp(2), -- Hex 81 esEs(3), -- Hex 82 ip(4), -- Hex CC blacker(5), -- Hex C5 other(6) } ACCESS read-write STATUS mandatory DESCRIPTION "The encapsulation mechanism to be used to call the remote host. This is the value used to place calls, a call opened by the remote host may use a different encapsulation. The value of the call user D. Throop [Page 13] Internet Draft IP over X.25 MIB February 1992 data for any existing connection should be used to determine the encapsulation actually in use. This value will override any Call user data parameter in the Call Parameters." ::= { ioxConEntry 9 } -- ########################################################### END D. Throop [Page 14] Internet Draft IP over X.25 MIB February 1992 7. Acknowledgements This document was produced by the x25mib working group: Fred Baker, ACC Art Berggreen, ACC Frank Bieser Charles Carvalho, ACC Angela Chen, HP Tom Daniel, Spider Systems Chuck Davin, MIT Doug Geller, Data General Herve Goguely, LIR Corp Andy Goldthorpe, british-telecom David Gurevich, Richard Fox, Synoptics Steve Huston, Process Software Corporation Frank Kastenholz, Clearpoint Zbigniew Kiel Cheryl Krupezak, Georgia Tech Mats Lindstrom, Diab Data AB Andrew Malis, BBN Evan McGinnis, 3Com Gary (G.P.)Mussar, BNR Karen Quidley, Data General Randy Pafford, Data General Ragnar Paulson, The Software Group Limited Dave Perkins, Synoptics Walter Pinkarschewsky, DEC Paul S. Rarey, DHL Systems Inc. Jim Roche, Newbridge Research Philippe Roger, LIR Corp. Mike Shand, DEC Bob Stewart, Xyplex Tom Sullivan, Data General Rodney Thayer, Sable Technology Corporation Mark Therieau, Microcom Jane Thorn, Data General Dean Throop, Data General Mike Zendels, Data General In addition, the comments of the following individuals are also acknowledged: Andrew Malis D. Throop [Page 15] Internet Draft IP over X.25 MIB February 1992 8. References [1] M.T. Rose and K. McCloghrie, "Structure and Identification of Management Information for TCP/IP-based internets", RFC 1155, Network Information Center, SRI International, Menlo Park, California, (May, 1990). [2] K. McCloghrie and M.T. Rose, "Management Information Base for Network Management of TCP/IP-based internets", RFC 1156, Network Information Center, SRI International, Menlo Park, California, (May, 1990). [3] J.D. Case, M.S. Fedor, M.L. Schoffstall, and J.R. Davin, "Simple Network Management Protocol", RFC 1157, Network Information Center, SRI International, Menlo Park, California, (May, 1990). [4] M.T. Rose, K. McCloghrie (editors), "Towards Concise MIB Definitions", RFC 1212, Network Information Center, SRI International, Menlo Park, California, (March, 1991) [5] M.T. Rose (editor), "Management Information Base for Network Management of TCP/IP-based internets", RFC 1213. Network Information Center, SRI International, Menlo Park, California, (March, 1991). [6] "Information processing systems - Open Systems Interconnection - Specification of Abstract Syntax Notation One (ASN.1)", International Organization for Standardization. International Standard 8824, (December, 1987). [7] "Information processing systems - Open Systems Interconnection - Specification of Basic Encoding Rules for Abstract Notation One (ASN.1)", International Organization for Standardization. International Standard 8825, (December, 1987). [8] B. Stewart (editor), "Definitions of Managed Objects for RS-232-like Hardware Devices", Internet Draft, Internet Engineering Task Force, (December, 1990) [9] D. Throop (editor), "SNMP MIB extension for LAPB", Internet Draft, Internet Engineering Task Force, (February, 1992) D. Throop [Page 16] Internet Draft IP over X.25 MIB February 1992 [10] D.D. Throop (editor), "SNMP MIB extension for the Packet Layer of X.25", Internet Draft, Internet Engineering Task Force, (October, 1991). [11] A.G. Malis, D. Robinson, R.L. Ullmann "Multiprotocol Interconnect on X.25 and ISDN in the Packet Mode", Internet Draft, Internet Engineering Task Force, (February 14, 1992) D. Throop [Page 17] Internet Draft IP over X.25 MIB February 1992 Table of Contents 1 Status of this Memo ................................... 1 1.1 Revision History .................................... 1 February 1992 .......................................... 1 October 1991 ........................................... 2 June 1991 .............................................. 2 2 Abstract .............................................. 2 3 The Network Management Framework ...................... 4 4 Objects ............................................... 4 4.1 Format of Definitions ............................... 5 5 Overview .............................................. 6 6 Definitions ........................................... 7 7 Acknowledgements ...................................... 15 8 References ............................................ 16 D. Throop [Page 18]