x25 MIB part 1
"Dean D. Throop" <throop@dg-rtp.dg.com> Tue, 25 February 1992 19:29 UTC
Received: from nri.reston.va.us by NRI.NRI.Reston.VA.US id aa18566; 25 Feb 92 14:29 EST
Received: from dg-rtp.rtp.dg.com by NRI.NRI.Reston.VA.US id aa18535; 25 Feb 92 14:29 EST
Received: from commtg3.rtp.dg.com by dg-rtp.dg.com (5.4/dg-rtp-proto) id AA23700; Tue, 25 Feb 1992 13:52:45 -0500
Received: by commtg3 (5.4.1/rtp-s04) id AA18056; Tue, 25 Feb 1992 13:52:44 -0500
Date: Tue, 25 Feb 1992 13:52:44 -0500
From: "Dean D. Throop" <throop@dg-rtp.dg.com>
Message-Id: <9202251852.AA18056@commtg3>
To: x25mib@dg-rtp.dg.com
Subject: x25 MIB part 1
Internet Draft X.25 Packet Layer MIB February 1992
SNMP MIB extension for the X.25 Packet Layer
February 24, 1992
Dean D. Throop
(editor)
Data General Corporation
62 Alexander Dr.
Research Triangle Park, NC 27709
throop@dg-rtp.dg.com
1. Status of this Memo
This is a draft document of the x25mib working group. The
working group intends to submit a revised version of this
document 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:
x25mib@dg-rtp.dg.com
1.1. Revision History
February 1992
The February release (Editor's Internal Reference Number 1.14)
made many changes.
Many of the tables were combined. For example, the
x25InfoTable, x25PktStatTable, and x25TmrStatTable were
combined into the x25PleTable. The x25ConInfoTable,
x25ConStatTable, and x25ConTimrTable were combined into
the x25CircuitTable.
D. Throop [Page 1]
Internet Draft X.25 Packet Layer MIB February 1992
The objects for call parameters were drastically
reworked. All call parameters were combined in the
x25CallParmTable. Any table, such as the x25PleTable or
x25CircuitTable, that needs to reference call parameters
identifies an entry in the new table. As part of this
the x25ConDefTable was deleted and replaced with the
x25PleDefCallParamId.
The x25PvcTable was deleted; the x25CircuitStatus object
provides similar information about PVCs.
The x25ClearedCircuitTable was added to record the status
code of cleared circuits.
Many object definitions were restructured. For example,
the time units for timers was changed from 1/100ths of a
second to milliseconds. Some indexes into tables were
replaced with object identifiers.
Much of the introductory text was changed and the
references were changed to match.
October 1992
The October release (Editor Internal Reference Number 1.10)
made the following changes:
Changed x25ConInfoStatus to clarify the description and
the pvcResetting(5) value was changed to pvcResetting(6)
to avoid a conflict with a previous use of the number 5.
The name of the counter object
x25TmrStatRetryCountsExceeded was changed to
x25TmrStatRetryCountExceededs.
The name of the counter object
x25TmrStatClearCountsExceeded was changed to
x25TmrStatClearCountExceededs.
All occurances of Guage were changed to Gauge.
Added the x25CallFcltyTable, x25CallFcltyCcittTable, and
x25CallParamTable.
D. Throop [Page 2]
Internet Draft X.25 Packet Layer MIB February 1992
June 1991
The June release corrected some syntax errors and cleaned up
some other minor things.
April 1991
The April 26 release of this document was the first release.
That version was derived from the ISO work on network layer
management as presented in ISO/IEC 10733 [11].
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 the Packet Layer of X.25. The objects defined here,
along with the objects in the "SNMP MIB extension for LAPB"
[9] and the "Definitions of Managed Objects for RS-232-like
Hardware Devices" [8], combine to allow management of an X.25
protocol stack.
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
D. Throop [Page 3]
Internet Draft X.25 Packet Layer MIB February 1992
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.
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
defined 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 4]
Internet Draft X.25 Packet Layer MIB February 1992
5. Overview
5.1. Informal Overview
This section describes how the objects defined below relate
with other MIBs. This section is only informational to help
understand how the pieces fit together.
The objects defined below are used in conjunction with MIB-II
and other MIBs such as the LAPB MIB [9]. A system with a
complete X.25 stack running over a synchronous line will have
at least two interfaces in the ifTable defined in MIB-II.
There will be an interface for LAPB and another interface for
the packet layer of X.25. There will also be objects defined
in the RS-232-like MIB for the physical sync line.
Each software interface identifies the layer below it used to
send and receive packets. The X.25 MIB object, defined below,
x25PleDataLinkId, specifies an instance of lapbParamIndex for
the LAPB interface under that X.25. The LAPB object,
lapbParamPortId, identifies an instance of the rs232PortIndex
for the the Sync line used by LAPB.
For X.25 running over LAPB over Ethernet, the lapbParamPortId
would identify the instance of ifIndex for the Ethernet
interface.
Each X.25 subnetwork will have separate entries in the
ifTable. Thus a system with two X.25 lines would have two
ifTable entries for the two X.25 packet layers and two other
entries for the two LAPB interfaces. Each X.25 Packet Layer
MIB would identify the instance of the LAPB MIB for the
interface below it. Each LAPB MIB would identify the Sync line
below it. The system would also have two entries for
rs232PortTable and rs232SyncPortTable for the two physical
lines.
Since the ifTable as defined in MIB-II is device independent,
it doesn't have anything specific for any type of interface.
The objects below define the X.25 packet layer specific
information for an interface of type X.25. Different X.25
interfaces can also be differentiated by matching the values
of ifIndex with x25PleIndex.
D. Throop [Page 5]
Internet Draft X.25 Packet Layer MIB February 1992
5.2. Textual Conventions
This MIB introduces a new data type as a textual convention
for use with X.25. This textual convention enhances the
readability of the specification and can ease comparison with
other specifications if appropriate. It should be noted that
the introduction of such textual conventions has no effect on
either the syntax nor the semantics of any managed objects.
These conventions are merely an artifact of the explanatory
method used. Objects defined in terms of one of these methods
are always encoded by means of the rules that define the
primitive type. Hence, no changes to the SMI or the SNMP are
necessary to accommodate these textual conventions which are
adopted merely for the convenience of readers and writers in
pursuit of the elusive goal of clear, concise, and unambiguous
MIB documents.
This MIB introduces the data type of:
X25address
5.3. Structure of MIB
Instances of the objects defined below represent attributes of
an X.25 Packet Layer interface. At present these interfaces
are identified by an ifType object in the Internet-standard
MIB [5] of:
ddn-x25(4), and
rfc887-x25(5).
For these interfaces, the value of the ifSpecific variable in
the MIB-II [5] has the OBJECT IDENTIFIER value:
x25 OBJECT IDENTIFIER ::= { To Be Assigned }
The objects defined below are similar to those defined in a
draft ISO document for X.25 management [11]. Some object
definitions also reference the ISO specification for X.25 [10]
to specify the section that will give the reader addition
information relative to the object. Access to those documents
maybe useful (but isn't essential) to understand the names and
semantics of some objects. The similarity of these objects
with the ISO objects minimizes the instrumentation required by
those systems that support both OSI and TCP/IP management
D. Throop [Page 6]
Internet Draft X.25 Packet Layer MIB February 1992
protocols.
Since the objects defined here are extensions to the Internet
Standard MIB [2] and thus also an extension of the second
version, MIB-II [5], the objects defined here explicitly do
not duplicate objects defined in existing standards. In some
instances clarification of how to apply those objects has been
given.
The relationship between an X.25 Packet Layer interface and an
interface 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 7]
Internet Draft X.25 Packet Layer MIB February 1992
6. Object Definitions
RFCX25Pk-MIB DEFINITIONS ::= BEGIN
-- Editors internal reference number 1.79
IMPORTS
experimental,
Counter,
Gauge,
TimeTicks
FROM RFC1155-SMI;
-- DO NOT USE THIS EXPERIMENTAL NUMBER!
x25 OBJECT IDENTIFIER ::= { experimental 1234567 }
-- This experimental number is
-- an invalid placeholder.
-- DO NOT USE THIS EXPERIMENTAL NUMBER!
X25address ::= OCTET STRING (SIZE(0..17))
-- 0 to 17 bytes in length containing the ASCII
-- characters [0-9], each octet contains one digit
-- of the address.
-- ###########################################################
-- X.25 Packet Level Entity (PLE) Table
-- ###########################################################
x25PleTable OBJECT-TYPE
SYNTAX SEQUENCE OF X25PleEntry
ACCESS not-accessible
STATUS mandatory
DESCRIPTION
"General information about this X.25 PLE."
::= { x25 1 }
x25PleEntry OBJECT-TYPE
SYNTAX X25PleEntry
ACCESS not-accessible
STATUS mandatory
DESCRIPTION
"Entries of x25PleTable."
INDEX { x25PleIndex }
::= { x25PleTable 1 }
D. Throop [Page 8]
Internet Draft X.25 Packet Layer MIB February 1992
X25PleEntry ::= SEQUENCE {
x25PleIndex
INTEGER,
x25PleProtocolVersionSupported
OBJECT IDENTIFIER,
x25PleLocalAddress
X25address,
x25PleInterfaceMode
INTEGER,
x25PleMaxActiveCircuits
INTEGER,
x25PleDataLinkId
OBJECT IDENTIFIER,
x25PlePacketSequencing
INTEGER,
x25PleInCalls
Counter,
x25PleInCallRefusals
Counter,
x25PleInProviderInitiatedClears
Counter,
x25PleInRemotelyInitiatedResets
Counter,
x25PleInProviderInitiatedResets
Counter,
x25PleInRestarts
Counter,
x25PleInDataPackets
Counter,
x25PleInAccusedOfProtocolErrors
Counter,
x25PleInInterrupts
Counter,
x25PleOutCallAttempts
Counter,
x25PleOutCallFailures
Counter,
x25PleOutInterrupts
Counter,
x25PleOutgoingConnections
Gauge,
x25PleIncomingConnections
Gauge,
x25PleTwowayConnections
Gauge,
D. Throop [Page 9]
Internet Draft X.25 Packet Layer MIB February 1992
x25PleRestartTimer
INTEGER,
x25PleMinimumRecallTimer
INTEGER,
x25PleRestartCount
INTEGER,
x25PleRegistrationRequestTimer
INTEGER,
x25PleRegistrationRequestCount
INTEGER,
x25PleCallTimeouts
Counter,
x25PleClearTimeouts
Counter,
x25PleResetTimeouts
Counter,
x25PleRestartTimeouts
Counter,
x25PleInterruptTimeouts
Counter,
x25PleDataRxmtTimeouts
Counter,
x25PleRetryCountExceededs
Counter,
x25PleClearCountExceededs
Counter,
x25PleClearEntriesRequested
INTEGER,
x25PleClearEntriesGranted
INTEGER,
x25PleDefCallParamId
OBJECT IDENTIFIER
}
x25PleIndex OBJECT-TYPE
SYNTAX INTEGER (1..65535)
ACCESS read-only
STATUS mandatory
DESCRIPTION
"A value that uniquely identifies the X.25
PLE subnetwork and matches its ifIndex
value."
::= { x25PleEntry 1 }
-- MIB-II also provides:
D. Throop [Page 10]
Internet Draft X.25 Packet Layer MIB February 1992
-- ifDescr:
-- On an X.25 interface this must include sufficient
-- information to enable the system's administrator
-- to determine the appropriate configuration
-- information on a system having multiple X.25
-- subnetworks.
-- ifType: ddn-x25 or rfc877-x25
-- an interface of type ddn-x25 will use an algorithm to
-- translate between X.121 address and IP addresses.
-- An interface of type rfc877-x25 will use a
-- configuration table to translate between X.121
-- addresses and IP addresses.
-- ifMtu: the maximum PDU a higher layer can pass to X.25 or
-- or receive from X.25
-- ifSpeed:
-- ifAdminStatus:
-- ifOperStatus
-- ifLastChange
x25PleProtocolVersionSupported OBJECT-TYPE
SYNTAX OBJECT IDENTIFIER
ACCESS read-write
STATUS mandatory
DESCRIPTION
"Identifies the version of X.25 this
interface supports. Object identifiers for
common versions are defined below in the
x25ProtocolVersion subtree."
REFERENCE "10733 5.9 protocolVersionSupported"
::= { x25PleEntry 2 }
x25PleLocalAddress OBJECT-TYPE
SYNTAX X25address
ACCESS read-write
STATUS mandatory
DESCRIPTION
"The local address for this PLE subnetwork."
REFERENCE "10733 5.9 localDTEAddress"
::= { x25PleEntry 3 }
D. Throop [Page 11]
Internet Draft X.25 Packet Layer MIB February 1992
x25PleInterfaceMode OBJECT-TYPE
SYNTAX INTEGER {
dte(1),
dce(2) }
ACCESS read-write
STATUS mandatory
DESCRIPTION
"Identifies DCE/DTE mode in which the
interface operates."
REFERENCE "10733 5.9 interfaceMode"
::= { x25PleEntry 4 }
x25PleMaxActiveCircuits OBJECT-TYPE
SYNTAX INTEGER (1..4096)
ACCESS read-write
STATUS mandatory
-- See ISO 8208, Section 3.7
DESCRIPTION
"Maximum number of circuits this PLE can
support."
REFERENCE "10733 5.9 maxActiveCircuits"
::= { x25PleEntry 5 }
x25PleDataLinkId OBJECT-TYPE
SYNTAX OBJECT IDENTIFIER
ACCESS read-only
STATUS mandatory
DESCRIPTION
"This identifies the instance of the index
object in the first table of the most device
specific MIB for the interface used by this
PLE."
::= { x25PleEntry 6 }
x25PlePacketSequencing OBJECT-TYPE
SYNTAX INTEGER {
modulo8(1),
modulo128(2) }
ACCESS read-write
STATUS mandatory
-- See ISO 8208 Section 7.1.1
DESCRIPTION
"The modulus of the packet sequence number
space."
REFERENCE "10733 extendedPacketSequencing"
D. Throop [Page 12]
Internet Draft X.25 Packet Layer MIB February 1992
::= { x25PleEntry 7 }
-- The following are the statistics part of the PLE.
-- MIB-II interfaces also contains:
-- ifInOctets: Number of data octets delivered to upper
-- layer entities.
-- ifInUcastPkts: Number of packets received from peer PLE and
-- delivered to upper layer entities.
-- ifDiscards: Number of packets dropped for lack of buffering
-- ifInErrors: Number of packets received containing errors
-- REFERENCE ProtocolErrorsDetectedLocally
-- ifInUnknownProtos: Number of packets with unknown circuit
-- identifier.
x25PleInCalls OBJECT-TYPE
SYNTAX Counter
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The number of incoming calls received."
::= { x25PleEntry 8 }
x25PleInCallRefusals OBJECT-TYPE
SYNTAX Counter
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The number of incoming calls refused."
::= { x25PleEntry 9 }
x25PleInProviderInitiatedClears OBJECT-TYPE
SYNTAX Counter
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The number of clear requests with a cause
code other than DTE initiated."
REFERENCE "10733 providerInitiatedDisconnect"
::= { x25PleEntry 10 }
D. Throop [Page 13]
Internet Draft X.25 Packet Layer MIB February 1992
x25PleInRemotelyInitiatedResets OBJECT-TYPE
SYNTAX Counter
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The number of reset requests received with
cause code DTE initiated."
REFERENCE "10733 remotelyInitiatedResets"
::= { x25PleEntry 11 }
x25PleInProviderInitiatedResets OBJECT-TYPE
SYNTAX Counter
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The number of reset requests received with
cause code other than DTE initiated."
REFERENCE "10733 ProviderInitiatedResets"
::= { x25PleEntry 12 }
x25PleInRestarts OBJECT-TYPE
SYNTAX Counter
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The number of remotely initiated (including
provider initiated) restarts experienced by
the PLE excluding the restart associated
with bringing up the PLE interface."
REFERENCE "10733 5.9 remotelyInitiatedRestarts"
::= { x25PleEntry 13 }
x25PleInDataPackets OBJECT-TYPE
SYNTAX Counter
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The number of data packets received."
REFERENCE "10733 5.9 dataPacketsReceived."
::= { x25PleEntry 14 }
x25PleInAccusedOfProtocolErrors OBJECT-TYPE
SYNTAX Counter
ACCESS read-only
STATUS mandatory
D. Throop [Page 14]
Internet Draft X.25 Packet Layer MIB February 1992
DESCRIPTION
"The number of packets received containing a
protocol error cause code. These include
clear, reset, restart, or diagnostic
packets."
REFERENCE "CD 10733 5.9 accusedOfProtocolError"
::= { x25PleEntry 15 }
x25PleInInterrupts OBJECT-TYPE
SYNTAX Counter
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The number of interrupt packets received by
the PLE or over the PVC/VC."
REFERENCE "10733 interruptPacketsReceived"
::= { x25PleEntry 16 }
-- ifOutOctets: Number of data octets delivered by
-- X.25 to upper layers.
-- ifOutUcastPkts: Number of packets sent to peer PLE.
x25PleOutCallAttempts OBJECT-TYPE
SYNTAX Counter
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The number of calls attempted."
REFERENCE "10733 5.9 callAttempts"
::= { x25PleEntry 17 }
x25PleOutCallFailures OBJECT-TYPE
SYNTAX Counter
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The number of calls attempts which failed."
::= { x25PleEntry 18 }
x25PleOutInterrupts OBJECT-TYPE
SYNTAX Counter
ACCESS read-only
STATUS mandatory
DESCRIPTION
D. Throop [Page 15]
Internet Draft X.25 Packet Layer MIB February 1992
"The number of interrupt packets send by the
PLE or over the PVC/VC."
REFERENCE "10733 InterruptPacketsSent"
::= { x25PleEntry 19 }
x25PleOutgoingConnections OBJECT-TYPE
SYNTAX Gauge
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The number of active outgoing connections.
This includes call requests sent but not yet
confirmed."
::= { x25PleEntry 20 }
x25PleIncomingConnections OBJECT-TYPE
SYNTAX Gauge
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The Number of active Incoming Connections.
This includes any call indications received
but not yet acknowledged."
::= { x25PleEntry 21 }
x25PleTwowayConnections OBJECT-TYPE
SYNTAX Gauge
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The number of active two-way connections.
This includes call requests sent but not yet
confirmed."
::= { x25PleEntry 22 }
-- X25 Timer Statistics section
x25PleRestartTimer OBJECT-TYPE
SYNTAX INTEGER (1..1800000)
ACCESS read-write
STATUS mandatory
-- See ISO 8208 Section 4.1, table 26
DESCRIPTION
"The T20 restart timer in milliseconds."
D. Throop [Page 16]
Internet Draft X.25 Packet Layer MIB February 1992
REFERENCE "10733 5.9 restartTime"
::= { x25PleEntry 23 }
x25PleMinimumRecallTimer OBJECT-TYPE
SYNTAX INTEGER (0..1800000)
ACCESS read-write
STATUS mandatory
DESCRIPTION
"Minimum time interval between call attempts
in milliseconds."
REFERENCE "10733 5.9 minimum RecallTimer"
::= { x25PleEntry 24 }
x25PleRestartCount OBJECT-TYPE
SYNTAX INTEGER (1..65535)
ACCESS read-write
STATUS mandatory
-- See ISO 8208 Section 4.1, table 27
DESCRIPTION
"The value of the R20 restart retransmission
count."
REFERENCE "10733 5.9 restartCount"
::= { x25PleEntry 25 }
x25PleRegistrationRequestTimer OBJECT-TYPE
SYNTAX INTEGER (0..1800000)
ACCESS read-write
STATUS mandatory
-- See ISO 8208 Section 13.1.1.1, table 26
DESCRIPTION
"The T28 registration timer in milliseconds.
A value of zero indicates no registration
timer in use."
REFERENCE "10733 5.8.1 registrationRequestTime (opt)"
::= { x25PleEntry 26 }
x25PleRegistrationRequestCount OBJECT-TYPE
SYNTAX INTEGER (0..65535)
ACCESS read-write
STATUS mandatory
-- See ISO 8208 Section 13.1.1.1, table 27
DESCRIPTION
"The R28 Registration retransmission Count.
A value of zero indicates no timer in use."
REFERENCE "10733 5.8.1 registrationRequestCount (opt)"
D. Throop [Page 17]
Internet Draft X.25 Packet Layer MIB February 1992
::= { x25PleEntry 27 }
x25PleCallTimeouts OBJECT-TYPE
SYNTAX Counter
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The number of times the T21 call timer
expired."
REFERENCE "10733 5.9 callTimeouts"
::= { x25PleEntry 28 }
x25PleClearTimeouts OBJECT-TYPE
SYNTAX Counter
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The number of times the T23 clear timer
expired."
REFERENCE "10733 5.9 clearTimeouts"
::= { x25PleEntry 29 }
x25PleResetTimeouts OBJECT-TYPE
SYNTAX Counter
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The number of times the T22 reset timer
expired."
REFERENCE "10733 5.9 resetTimeouts"
::= { x25PleEntry 30 }
x25PleRestartTimeouts OBJECT-TYPE
SYNTAX Counter
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The number of times the T20 restart timer
expired."
REFERENCE "10733 5.9 restartTimeouts"
::= { x25PleEntry 31 }
x25PleInterruptTimeouts OBJECT-TYPE
SYNTAX Counter
ACCESS read-only
D. Throop [Page 18]
Internet Draft X.25 Packet Layer MIB February 1992
STATUS mandatory
DESCRIPTION
"The number of times the T26 interrupt timer
expired."
REFERENCE "10733 5.9 interruptTimerExpires"
::= { x25PleEntry 32 }
x25PleDataRxmtTimeouts OBJECT-TYPE
SYNTAX Counter
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The number of times the T25 data timer
expired."
REFERENCE "10733 5.9 dataRetransmissionsTimerExpiries"
::= { x25PleEntry 33 }
x25PleRetryCountExceededs OBJECT-TYPE
SYNTAX Counter
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The number of times a retry counter was
exhausted."
REFERENCE "10733 5.9 retryCountsExceeded"
::= { x25PleEntry 34 }
x25PleClearCountExceededs OBJECT-TYPE
SYNTAX Counter
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The number of times the R23 clear count was
exceeded."
REFERENCE "10733 5.9 clearCountsExceeded"
::= { x25PleEntry 35 }
x25PleClearEntriesRequested OBJECT-TYPE
SYNTAX INTEGER (1..65535)
ACCESS read-write
STATUS mandatory
DESCRIPTION
"The requested number of entries this PLE
will keep in the x25ClearedCircuit table."
::= { x25PleEntry 36 }
D. Throop [Page 19]
Internet Draft X.25 Packet Layer MIB February 1992
x25PleClearEntriesGranted OBJECT-TYPE
SYNTAX INTEGER (1..65535)
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The number entries the agent will keep in
the x25ClearedCircuit Table."
::= { x25PleEntry 37 }
x25PleDefCallParamId OBJECT-TYPE
SYNTAX OBJECT IDENTIFIER
ACCESS read-write
STATUS mandatory
DESCRIPTION
"This identifies the instance of the
x25CallParmIndex for the entry in the
x25callParm table which contains the default
call parameters for this Ple."
::= { x25PleEntry 38 }
-- ###########################################################
-- X.25 Channel Table
-- ###########################################################
x25ChannelTable OBJECT-TYPE
SYNTAX SEQUENCE OF X25ChannelEntry
ACCESS not-accessible
STATUS mandatory
-- See ISO 8208, Section 3.7
DESCRIPTION
"These objects contain information about the
channel number configuration in an X.25
PLE."
::= { x25 2 }
x25ChannelEntry OBJECT-TYPE
SYNTAX X25ChannelEntry
ACCESS not-accessible
STATUS mandatory
DESCRIPTION
"Entries of x25ChannelTable."
-- REFERENCE This provides the information
-- available in logicalChannelAssignments.
D. Throop [Page 20]
Internet Draft X.25 Packet Layer MIB February 1992
INDEX { x25ChannelIndex }
::= { x25ChannelTable 1 }
X25ChannelEntry ::= SEQUENCE {
x25ChannelIndex
INTEGER,
x25ChannelLIC
INTEGER,
x25ChannelHIC
INTEGER,
x25ChannelLTC
INTEGER,
x25ChannelHTC
INTEGER,
x25ChannelLOC
INTEGER,
x25ChannelHOC
INTEGER
}
x25ChannelIndex OBJECT-TYPE
SYNTAX INTEGER (1..65535)
ACCESS read-only
STATUS mandatory
DESCRIPTION
"A value that uniquely identifies the X.25
PLE subnetwork and matches its ifIndex
value."
::= { x25ChannelEntry 1 }
x25ChannelLIC OBJECT-TYPE
SYNTAX INTEGER (1..4096)
ACCESS read-write
STATUS mandatory
DESCRIPTION
"Lowest Incoming channel."
::= { x25ChannelEntry 2 }
x25ChannelHIC OBJECT-TYPE
SYNTAX INTEGER (1..4096)
ACCESS read-write
STATUS mandatory
DESCRIPTION
"Highest Incoming channel."
::= { x25ChannelEntry 3 }
D. Throop [Page 21]
Internet Draft X.25 Packet Layer MIB February 1992
x25ChannelLTC OBJECT-TYPE
SYNTAX INTEGER (1..4096)
ACCESS read-write
STATUS mandatory
DESCRIPTION
"Lowest Two-way channel."
::= { x25ChannelEntry 4 }
x25ChannelHTC OBJECT-TYPE
SYNTAX INTEGER (1..4096)
ACCESS read-write
STATUS mandatory
DESCRIPTION
"Highest Two-way channel."
::= { x25ChannelEntry 5 }
x25ChannelLOC OBJECT-TYPE
SYNTAX INTEGER (1..4096)
ACCESS read-write
STATUS mandatory
DESCRIPTION
"Lowest outgoing channel."
::= { x25ChannelEntry 6 }
x25ChannelHOC OBJECT-TYPE
SYNTAX INTEGER (1..4096)
ACCESS read-write
STATUS mandatory
DESCRIPTION
"Highest outgoing channel."
::= { x25ChannelEntry 7 }
-- ###########################################################
-- X25 Per Connection Information Table
-- ###########################################################
x25CircuitTable OBJECT-TYPE
SYNTAX SEQUENCE OF X25CircuitEntry
ACCESS not-accessible
STATUS mandatory
DESCRIPTION
D. Throop [Page 22]
Internet Draft X.25 Packet Layer MIB February 1992
"These objects contain general information
about a specific connection of an X.25 PLE."
::= { x25 3 }
x25CircuitEntry OBJECT-TYPE
SYNTAX X25CircuitEntry
ACCESS not-accessible
STATUS mandatory
DESCRIPTION
"Entries of x25CircuitTable."
INDEX { x25CircuitIndex,
x25CircuitChannel }
::= { x25CircuitTable 1 }
X25CircuitEntry ::= SEQUENCE {
x25CircuitIndex
INTEGER,
x25CircuitChannel
INTEGER,
x25CircuitName
DisplayString,
x25CircuitEstablishTime
TimeTicks,
x25CircuitStatus
INTEGER,
x25CircuitDirection
INTEGER,
x25CircuitCallParamId
OBJECT IDENTIFIER,
x25CircuitRemoteDteAddress
X25Address,
x25CircuitCalledDteAddress
X25Address,
x25CircuitCallingDteAddress
X25Address,
x25CircuitOriginallyCalledAddress
X25Address,
x25CircuitInOctets
Counter,
x25CircuitInPdus
Counter,
x25CircuitInRemotelyInitiatedResets
Counter,
x25CircuitInProviderInitiatedResets
Counter,
D. Throop [Page 23]
Internet Draft X.25 Packet Layer MIB February 1992
x25CircuitInInterrupts
Counter,
x25CircuitOutOctets
Counter,
x25CircuitOutPdus
Counter,
x25CircuitOutInterrupts
Counter,
x25CircuitDataRetransmissionTimeouts
Counter,
x25CircuitResetTimeouts
Counter,
x25CircuitInterruptTimeouts
Counter
}
x25CircuitIndex OBJECT-TYPE
SYNTAX INTEGER (1..65535)
ACCESS read-only
STATUS mandatory
DESCRIPTION
"A value that uniquely identifies the X.25
PLE subnetwork and matches its ifIndex
value."
::= { x25CircuitEntry 1 }
x25CircuitChannel OBJECT-TYPE
SYNTAX INTEGER (1..4096)
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The channel number for this connection."
::= { x25CircuitEntry 2 }
x25CircuitName OBJECT-TYPE
SYNTAX DisplayString (SIZE (0..255))
ACCESS read-only
STATUS mandatory
DESCRIPTION
"A name associated with this connection."
::= { x25CircuitEntry 3 }
x25CircuitEstablishTime OBJECT-TYPE
SYNTAX TimeTicks
D. Throop [Page 24]
Internet Draft X.25 Packet Layer MIB February 1992
ACCESS read-only
STATUS mandatory
DESCRIPTION
"Value of sysUpTime when the channel was
associated with this connection."
::= { x25CircuitEntry 4 }
x25CircuitStatus OBJECT-TYPE
SYNTAX INTEGER { -- state table states
closed(1), -- (p1)
calling(2), -- (p2,p3,p5)
open(3), -- (p4)
clearing(4), -- (p6,p7)
pvc(5),
pvcResetting(6)}
ACCESS read-write
STATUS mandatory
-- See ISO 8208, table 33 for (p<n>) state table
DESCRIPTION
"The current status of this connection.
Setting the connection to closed closes the
connection (not for PVC, a PVC can not be
set to closed).
An entry in the closed state may be deleted
or reused at the agent's convence. If the
entry is kept in the closed state, the
values of the parameters associated with the
entry must be correct."
::= { x25CircuitEntry 5 }
x25CircuitDirection OBJECT-TYPE
SYNTAX INTEGER {
incoming(1),
outgoing(2) }
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The direction of the call that established
this connection."
REFERENCE "10733 direction"
::= { x25CircuitEntry 6 }
x25CircuitCallParamId OBJECT-TYPE
SYNTAX OBJECT IDENTIFIER
D. Throop [Page 25]
Internet Draft X.25 Packet Layer MIB February 1992
ACCESS read-write
STATUS mandatory
DESCRIPTION
"This identifies the instance of the
x25CallParmIndex for the entry in the
x25callParm table which contains the call
parameters in use with this call. The entry
referenced must contain the values that are
currently in use by the circuit rather than
proposed values."
::= { x25CircuitEntry 7 }
x25CircuitRemoteDteAddress OBJECT-TYPE
SYNTAX X25Address
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The address of the remote DTE for this
connection."
::= { x25CircuitEntry 8 }
x25CircuitCalledDteAddress OBJECT-TYPE
SYNTAX X25Address
ACCESS read-only
STATUS mandatory
DESCRIPTION
"Destination DTE address used when the call
was placed that established this
connection."
REFERENCE "10733 calledDTEAddress"
::= { x25CircuitEntry 9 }
x25CircuitCallingDteAddress OBJECT-TYPE
SYNTAX X25Address
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The calling DTE address from the call
packet. For outgoing calls, this will be
the address of the local DTE for this
connection."
REFERENCE "10733 callingDTEAddress"
::= { x25CircuitEntry 10 }
x25CircuitOriginallyCalledAddress OBJECT-TYPE
D. Throop [Page 26]
Internet Draft X.25 Packet Layer MIB February 1992
SYNTAX X25Address
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The originally called address."
REFERENCE "10733 originallyCalledAddress"
::= { x25CircuitEntry 11 }
-- X25 Circuit data flow statistics
x25CircuitInOctets OBJECT-TYPE
SYNTAX Counter
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The number of octets of user data delivered
to upper layer."
REFERENCE "5.11 octetsReceivedCounter"
::= { x25CircuitEntry 12 }
x25CircuitInPdus OBJECT-TYPE
SYNTAX Counter
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The number of PDUs received for this
connection."
REFERENCE "10733 5.11 dataPacketsReceived"
::= { x25CircuitEntry 13 }
x25CircuitInRemotelyInitiatedResets OBJECT-TYPE
SYNTAX Counter
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The number of Resets received for this
connection with cause code of DTE
initiated."
REFERENCE "10733 remotelyInitiatedResets"
::= { x25CircuitEntry 14 }
x25CircuitInProviderInitiatedResets OBJECT-TYPE
D. Throop [Page 27]
Internet Draft X.25 Packet Layer MIB February 1992
SYNTAX Counter
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The number of Resets received for this
connection with cause code other than DTE
initiated."
REFERENCE "10733 ProviderInitiatedResets"
::= { x25CircuitEntry 15 }
x25CircuitInInterrupts OBJECT-TYPE
SYNTAX Counter
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The number of interrupt packets received
for this connection."
REFERENCE "10733 interruptPacketsReceived"
::= { x25CircuitEntry 16 }
x25CircuitOutOctets OBJECT-TYPE
SYNTAX Counter
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The number of Octets of user data sent for
this connection."
REFERENCE "10733 5.11 octetsSentCounter"
::= { x25CircuitEntry 17 }
x25CircuitOutPdus OBJECT-TYPE
SYNTAX Counter
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The number of packets sent for this
connection."
REFERENCE "10733 5.11 dataPacketsSent"
::= { x25CircuitEntry 18 }
x25CircuitOutInterrupts OBJECT-TYPE
SYNTAX Counter
ACCESS read-only
STATUS mandatory
DESCRIPTION
D. Throop [Page 28]
Internet Draft X.25 Packet Layer MIB February 1992
"The number of interrupt packets sent on
this connection."
REFERENCE "10733 interruptPacketsSent"
::= { x25CircuitEntry 19 }
-- X25 Per Connection Timer Table
x25CircuitDataRetransmissionTimeouts OBJECT-TYPE
SYNTAX Counter
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The number of times the T25 data
retransmission timer expired for this
connection."
REFERENCE "10733 5.11 dataRetransmissionTimerExpiries"
::= { x25CircuitEntry 20 }
x25CircuitResetTimeouts OBJECT-TYPE
SYNTAX Counter
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The number of times the T22 reset timer
expired for this connection."
REFERENCE "10733 5.11 resetTimeouts"
::= { x25CircuitEntry 21 }
x25CircuitInterruptTimeouts OBJECT-TYPE
SYNTAX Counter
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The number of times the T26 Interrupt timer
expired for this connection."
REFERENCE "10733 interruptTimerExpiries"
::= { x25CircuitEntry 22 }
Dean Throop throop@dg-rtp.dg.com
- x25 MIB part 1 Dean D. Throop