Updated X.25 MIB part 1 of 2
"Dean D. Throop" <throop@dg-rtp.dg.com> Thu, 16 April 1992 17:16 UTC
Received: from nri.nri.reston.va.us by ietf.NRI.Reston.VA.US id aa02774; 16 Apr 92 13:16 EDT
Received: from nri.reston.va.us by NRI.Reston.VA.US id aa15219; 16 Apr 92 13:19 EDT
Received: from dg-rtp.rtp.dg.com by NRI.Reston.VA.US id aa15186; 16 Apr 92 13:19 EDT
Received: from walrus.rtp.dg.com by dg-rtp.dg.com (5.4/dg-rtp-proto) id AA11166; Thu, 16 Apr 1992 12:16:32 -0400
Received: by walrus (5.4.1/140.2) id AA08708; Thu, 16 Apr 1992 12:13:43 -0400
Date: Thu, 16 Apr 1992 12:13:43 -0400
From: "Dean D. Throop" <throop@dg-rtp.dg.com>
Message-Id: <9204161613.AA08708@walrus>
To: x25mib@dg-rtp
Subject: Updated X.25 MIB part 1 of 2
Here is the first part of the X.25 MIB updated with the comments
from the March working group meeting.
Internet Draft X.25 Packet Layer MIB April 1992
SNMP MIB extension for the X.25 Packet Layer
April 16, 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
April 1992
The April release (Editor's Internal Reference Number 2.8)
made many changes to incorporate the comments of the working
group meeting in March 1992.
All reference comments were changed to reference fields.
The type PositiveInteger was imported from the RFClapb-
MIB and used for all index and timer values.
D. Throop [Page 1]
Internet Draft X.25 Packet Layer MIB April 1992
The x25PleTable was split into the x25AdmnTable,
x25OperTable, and x25StatTable.
The timer and counter objects from the x25CircuitTable
were moved to the x25AdmnTable and replicated in the
x25OperTable
The objects in the x25CircuitTable were reordered to put
the non-integer objects at the end of the table for
easier implementation.
The called and calling extension character set was
extended to include a-f, and A-F.
Additional states were added to the x25CircuitStatus
object.
Additional values were added to x25CircuitDirection
x25CircuitCallParamId, and the addresses in the Circuit
Table for PVCs.
The length of the X25Address was changed to 0..15.
The objects x25ClearedCircuitTimeEstablished,
x25ClearedCircuitInPdus, and x25ClearedCircuitOutPdus
were added to the x25ClearedCircuitTable.
The name of the x25CircuitName was changed to
x25CircuitDescr and the description was expanded.
The access of the x25CircuitCallParamId was changed to
read-only.
The x25ClearedCircuitCodes object was split into the
x25ClearedCircuitClearingCause and
x25ClearedCircuitDiagnosticCode objects.
The semantics of the x25ClearedCircuitIndex was
redefined.
Some of the description clauses were changed in an
attempt to add clarity.
DEFVAL clauses were added to most objects in the
x25CallParmTable.
D. Throop [Page 2]
Internet Draft X.25 Packet Layer MIB April 1992
Additional text was added to the description section to
provide an overview of the tables of the MIB.
The minimum allowable value for maximum active circuits
was changed from one to zero.
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.
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 1991
The October release (Editor Internal Reference Number 1.10)
made the following changes:
D. Throop [Page 3]
Internet Draft X.25 Packet Layer MIB April 1992
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 occurrence of Guage was changed to Gauge.
Added the x25CallFcltyTable, x25CallFcltyCcittTable, and
x25CallParamTable.
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.
D. Throop [Page 4]
Internet Draft X.25 Packet Layer MIB April 1992
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.
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.
D. Throop [Page 5]
Internet Draft X.25 Packet Layer MIB April 1992
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 6]
Internet Draft X.25 Packet Layer MIB April 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,
x25OperDataLinkId, specifies an instance of lapbAdmnIndex for
the LAPB interface under that X.25. The LAPB object,
lapbOperPortId, identifies an instance of the rs232PortIndex
for the the Sync line used by LAPB.
For X.25 running over LAPB over Ethernet, the lapbOperPortId
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 in the
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 x25AdmnIndex.
D. Throop [Page 7]
Internet Draft X.25 Packet Layer MIB April 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:
X121Address
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-II [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 about 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 8]
Internet Draft X.25 Packet Layer MIB April 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.
5.4. Tables
The objects below form several tables. These tables are:
x25AdmnTable
x25OperTable
x25StatTable
x25ChannelTable
x25CircuitTable
x25ClearedCircuitTable
x25CallParmTable
The x25AdmnTable defines objects for the parameters of an X.25
interface which the administrator can read and set. These
objects are used at interface initialization time to start the
interface. Once the interface has started, changes to the
objects in the Administration table may not take affect until
the interface is re-initialized.
The x25OperTable defines objects that report the current
parameters used by a running interface. These objects are
read-only.
The x25StatTable defines objects that report operational
statistics for an X.25 interface. These are read-only
counters of events that occurred at the interface.
The x25ChannelTable defines objects to allow the administrator
to manage the division of channel numbers.
D. Throop [Page 9]
Internet Draft X.25 Packet Layer MIB April 1992
The x25CircuitTable defines objects that return information
about existing X.25 circuits. These entries result from calls
placed or answered by the PLE or from PVCs.
The x25ClearedCircuitTable contains objects for recording the
termination information from circuits that cleared abnormally.
The x25CallParmTable defines the call parameters used to call
other systems. This table contains call parameter entries
which are referenced by other tables. For example, the
x25AdmnTable has one objects that identifies the entry in the
table for the default PLE parameters. The x25CircuitTable has
one object that identifies the entry in the x25CallParmTable
for the parameters in use by that circuit. Other MIBs may
also reference entries to identify call parameters to use to
make X.25 calls.
5.5. Table Usage
Different tables provide different functions. The
administrator sets the starting X.25 parameters in the
x25AdmnTable for the X.25 PLE; these objects include a
reference to the x25CallParmTable entry to identify the
default call parameters for the PLE. Once all the parameters
are set, the administrator initializes the interface. As part
of initializing the interface, the operating parameters are
copied into the interface from the x25AdmnTable; these
parameters are viewable by getting the objects in the
x25OperTable. (The interface maybe started by setting the
value of ifAdminStatus to up.) If any PVCs are desired, they
should be configured in the the x25CircuitTable before
initializing the interface; this should be done in conjunction
with configuring higher layer entities to use the PVCs via the
MIBs for those entities.
Once the PLE completes initialization, it makes additional
entries in the x25circuitTable for calls placed or answered.
When a circuit is cleared, the status of the entry for the
circuit is set to closed and, if the clear is abnormal, an
entry will also be made in the x25ClearedCircuitTable. An
entry in the x25CircuitTable with a status of closed maybe
deleted by the agent at its convenience. A closed entry will
always be reused at the time the PLE re-allocates the channel
number of the entry for another call. The call parameters
used for a circuit can be found by looking in the
D. Throop [Page 10]
Internet Draft X.25 Packet Layer MIB April 1992
x25CircuitTable and following the x25CircuitCallParamId
pointer to the entry in the x25CallParmTable that contains the
parameters.
There are no mechanisms in the X.25 MIB for telling the PLE to
place an X.25 call. Such mechanisms belong in the MIBs for the
higher layer entities that use the X.25 circuits.
5.6. Conformance
All the objects defined here are mandatory. To claim
conformance with this MIB an implementation must support all
objects. However some objects pertain to features that are
optional. There are values defined for those objects that
indicate the implementation does not support the optional
feature. The agent for such an implementation must support
reading the object and return the value that indicates the
optional feature isn't supported and reject set requests to
change the object.
Some optional features have more than one object that pertain
to it (window rotation has a timer, a count, and a counter for
timer runouts). In such case, any object which indicates the
optional feature isn't supported is sufficient to indicate the
feature isn't supported and the values of the other objects
relative to that feature are undefined.
D. Throop [Page 11]
Internet Draft X.25 Packet Layer MIB April 1992
6. Object Definitions
RFCX25Pk-MIB DEFINITIONS ::= BEGIN
-- Editors internal reference number 2.30
IMPORTS
experimental,
Counter,
Gauge,
TimeTicks
FROM RFC1155-SMI
OBJECT-TYPE
FROM RFC-1212
TRAP-TYPE
FROM RFC-1215
EntryStatus
FROM RFC-1271-MIB
PostiveInteger
FROM RFClapb-MIB;
-- DO NOT USE THIS EXPERIMENTAL NUMBER!
x25 OBJECT IDENTIFIER ::= { experimental 1234567 }
-- This experimental number is
-- an invalid placeholder.
-- DO NOT USE THIS EXPERIMENTAL NUMBER!
X121Address ::= OCTET STRING (SIZE(0..15))
-- 0 to 15 bytes in length containing the ASCII
-- characters [0-9], each octet contains one digit
-- of the address.
-- ###########################################################
-- X.25 Administration Table
-- ###########################################################
x25AdmnTable OBJECT-TYPE
SYNTAX SEQUENCE OF X25AdmnEntry
ACCESS not-accessible
STATUS mandatory
DESCRIPTION
"This table contains the administratively
set configuration parameters for an X.25
PLE.
D. Throop [Page 12]
Internet Draft X.25 Packet Layer MIB April 1992
Most of the objects in this table have
corresponding objects in the x25OperTable.
This table contains the values as last set
by the administrator. The x25OperTable
contains the values actually in use by an
X.25 PLE.
Changing an administrative value may or may
not change a current operating value. The
operating value may not change until the
interface is restarted. Some
implementations may change the values
immediately upon changing the administrative
table. All implementations are required to
load the values from the administrative
table when initializing a PLE."
::= { x25 1 }
x25AdmnEntry OBJECT-TYPE
SYNTAX X25AdmnEntry
ACCESS not-accessible
STATUS mandatory
DESCRIPTION
"Entries of x25AdmnTable."
INDEX { x25AdmnIndex }
::= { x25AdmnTable 1 }
X25AdmnEntry ::= SEQUENCE {
x25AdmnIndex
PositiveInteger,
x25AdmnInterfaceMode
INTEGER,
x25AdmnMaxActiveCircuits
INTEGER,
x25AdmnPacketSequencing
INTEGER,
x25AdmnRestartTimer
PositiveInteger,
x25AdmnCallTimer
PositiveInteger,
x25AdmnResetTimer
PositiveInteger,
x25AdmnClearTimer
PositiveInteger,
x25AdmnWindowTimer
D. Throop [Page 13]
Internet Draft X.25 Packet Layer MIB April 1992
PositiveInteger,
x25AdmnDataRxmtTimer
PositiveInteger,
x25AdmnInterruptTimer
PositiveInteger,
x25AdmnRejectTimer
PositiveInteger,
x25AdmnRegistrationRequestTimer
PositiveInteger,
x25AdmnMinimumRecallTimer
PositiveInteger,
x25AdmnRestartCount
INTEGER,
x25AdmnResetCount
INTEGER,
x25AdmnClearCount
INTEGER,
x25AdmnDataRxmtCount
INTEGER,
x25AdmnRejectCount
INTEGER,
x25AdmnRegistrationRequestCount
INTEGER,
x25AdmnDefCallParamId
OBJECT IDENTIFIER,
x25AdmnLocalAddress
X121Address
}
x25AdmnIndex OBJECT-TYPE
SYNTAX PositiveInteger
ACCESS read-only
STATUS mandatory
DESCRIPTION
"A value that uniquely identifies the X.25
PLE subnetwork and matches its ifIndex
value. The object ifNumber specifies the
maximum value for this index."
::= { x25AdmnEntry 1 }
x25AdmnInterfaceMode OBJECT-TYPE
SYNTAX INTEGER {
dte(1),
dce(2) }
ACCESS read-write
D. Throop [Page 14]
Internet Draft X.25 Packet Layer MIB April 1992
STATUS mandatory
DESCRIPTION
"Identifies DCE/DTE mode in which the
interface operates."
REFERENCE "10733 5.9 interfaceMode"
::= { x25AdmnEntry 2 }
x25AdmnMaxActiveCircuits OBJECT-TYPE
SYNTAX INTEGER (0..4096)
ACCESS read-write
STATUS mandatory
DESCRIPTION
"The maximum number of circuits this PLE can
support; including PVCs."
REFERENCE "10733 5.9 maxActiveCircuits;
See ISO 8208, Section 3.7"
::= { x25AdmnEntry 3 }
x25AdmnPacketSequencing OBJECT-TYPE
SYNTAX INTEGER {
modulo8(1),
modulo128(2) }
ACCESS read-write
STATUS mandatory
DESCRIPTION
"The modulus of the packet sequence number
space."
REFERENCE "10733 extendedPacketSequencing;
See ISO 8208 Section 7.1.1"
::= { x25AdmnEntry 4 }
x25AdmnRestartTimer OBJECT-TYPE
SYNTAX PositiveInteger
ACCESS read-write
STATUS mandatory
DESCRIPTION
"The T20 restart timer in milliseconds."
REFERENCE "10733 5.9 restartTime
See ISO 8208 Section 4.1, table 26"
::= { x25AdmnEntry 5 }
x25AdmnCallTimer OBJECT-TYPE
SYNTAX PositiveInteger
ACCESS read-write
STATUS mandatory
D. Throop [Page 15]
Internet Draft X.25 Packet Layer MIB April 1992
DESCRIPTION
"The T21 Call timer in milliseconds."
REFERENCE "10733 callTime;
See ISO 8208 Section 5.2.1, table 26"
::= { x25AdmnEntry 6 }
x25AdmnResetTimer OBJECT-TYPE
SYNTAX PositiveInteger
ACCESS read-write
STATUS mandatory
DESCRIPTION
"The T22 Reset timer in milliseconds."
REFERENCE "10733 resetTime;
See ISO 8208 Section 8.1, table 26"
::= { x25AdmnEntry 7 }
x25AdmnClearTimer OBJECT-TYPE
SYNTAX PositiveInteger
ACCESS read-write
STATUS mandatory
DESCRIPTION
"The T23 Clear timer in milliseconds."
REFERENCE "10733 clearTime;
See ISO 8208 Section 5.5.1, table 26"
::= { x25AdmnEntry 8 }
x25AdmnWindowTimer OBJECT-TYPE
SYNTAX PositiveInteger
ACCESS read-write
STATUS mandatory
DESCRIPTION
"The T24 window status transmission timer in
milliseconds. A value of 2147483647
indicates no window timer in use."
REFERENCE "10733 5.10.1 windowTime (opt);
See ISO 8208 Section 11.2.2, table 26"
::= { x25AdmnEntry 9 }
x25AdmnDataRxmtTimer OBJECT-TYPE
SYNTAX PositiveInteger
ACCESS read-write
STATUS mandatory
DESCRIPTION
"The T25 data retransmission timer in
milliseconds. A value of 2147483647
D. Throop [Page 16]
Internet Draft X.25 Packet Layer MIB April 1992
indicates no data retransmission timer in
use."
REFERENCE "10733 5.10.1 dataRetransmissionTime (opt);
See ISO 8208 Section 11.2.1, table 26"
::= { x25AdmnEntry 10 }
x25AdmnInterruptTimer OBJECT-TYPE
SYNTAX PositiveInteger
ACCESS read-write
STATUS mandatory
DESCRIPTION
"The T26 interrupt timer in milliseconds. A
value of 2147483647 indicates no interrupt
timer in use."
REFERENCE "10733 interruptTime;
See ISO 8208 Section 6.8.1, table 26"
::= { x25AdmnEntry 11 }
x25AdmnRejectTimer OBJECT-TYPE
SYNTAX PositiveInteger
ACCESS read-write
STATUS mandatory
DESCRIPTION
"The T27 Reject retransmission timer in
milliseconds. A value of 2147483647
indicates no reject timer in use."
REFERENCE "10733 5.10.1 dataRejectTime (opt);
See ISO 8208 Section 13.4.1, table 26"
::= { x25AdmnEntry 12 }
x25AdmnRegistrationRequestTimer OBJECT-TYPE
SYNTAX PositiveInteger
ACCESS read-write
STATUS mandatory
DESCRIPTION
"The T28 registration timer in milliseconds.
A value of 2147483647 indicates no
registration timer in use."
REFERENCE "10733 5.8.1 registrationRequestTime (opt)
See ISO 8208 Section 13.1.1.1, table 26"
::= { x25AdmnEntry 13 }
x25AdmnMinimumRecallTimer OBJECT-TYPE
SYNTAX PositiveInteger
ACCESS read-write
D. Throop [Page 17]
Internet Draft X.25 Packet Layer MIB April 1992
STATUS mandatory
DESCRIPTION
"Minimum time interval between unsuccessful
call attempts in milliseconds."
REFERENCE "10733 5.9 minimum RecallTimer"
::= { x25AdmnEntry 14 }
x25AdmnRestartCount OBJECT-TYPE
SYNTAX INTEGER (0..65535)
ACCESS read-write
STATUS mandatory
DESCRIPTION
"The R20 restart retransmission count."
REFERENCE "10733 5.9 restartCount;
See ISO 8208 Section 4.1, table 27"
::= { x25AdmnEntry 15 }
x25AdmnResetCount OBJECT-TYPE
SYNTAX INTEGER (0..65535)
ACCESS read-write
STATUS mandatory
DESCRIPTION
"The r22 Reset retransmission count."
REFERENCE "10733 resetCount;
See section ISO 8208 8.1, table 27"
::= { x25AdmnEntry 16 }
x25AdmnClearCount OBJECT-TYPE
SYNTAX INTEGER (0..65535)
ACCESS read-write
STATUS mandatory
DESCRIPTION
"The r23 Clear retransmission count."
REFERENCE "10733 clearCount;
See ISO 8208 Section 5.5.1, table 27"
::= { x25AdmnEntry 17 }
x25AdmnDataRxmtCount OBJECT-TYPE
SYNTAX INTEGER (0..65535)
ACCESS read-write
STATUS mandatory
DESCRIPTION
"The R25 Data retransmission count."
REFERENCE "10733 5.10.1 dataRetransmissionCount (opt)
See ISO 8208 Section 11.2.1, table 27"
D. Throop [Page 18]
Internet Draft X.25 Packet Layer MIB April 1992
::= { x25AdmnEntry 18 }
x25AdmnRejectCount OBJECT-TYPE
SYNTAX INTEGER (0..65535)
ACCESS read-write
STATUS mandatory
DESCRIPTION
"The R27 reject retransmission count."
REFERENCE "10733 5.10.1 dataRejectCount (opt)"
::= { x25AdmnEntry 19 }
x25AdmnRegistrationRequestCount OBJECT-TYPE
SYNTAX INTEGER (0..65535)
ACCESS read-write
STATUS mandatory
DESCRIPTION
"The R28 Registration retransmission Count."
REFERENCE "10733 5.8.1 registrationRequestCount (opt);
See ISO 8208 Section 13.1.1.1, table 27"
::= { x25AdmnEntry 20 }
x25AdmnDefCallParamId OBJECT-TYPE
SYNTAX OBJECT IDENTIFIER
ACCESS read-write
STATUS mandatory
DESCRIPTION
"This identifies the instance of the
x25CallParmIndex for the entry in the
x25CallParmTable which contains the default
call parameters for this PLE."
::= { x25AdmnEntry 21 }
x25AdmnLocalAddress OBJECT-TYPE
SYNTAX X121Address
ACCESS read-write
STATUS mandatory
DESCRIPTION
"The local address for this PLE subnetwork.
A zero length address maybe returned by PLEs
that only support PVCs."
REFERENCE "10733 5.9 localDTEAddress"
::= { x25AdmnEntry 22 }
-- ###########################################################
D. Throop [Page 19]
Internet Draft X.25 Packet Layer MIB April 1992
-- X.25 Operational Table
-- ###########################################################
x25OperTable OBJECT-TYPE
SYNTAX SEQUENCE OF X25OperEntry
ACCESS not-accessible
STATUS mandatory
DESCRIPTION
"The operation parameters in use by the X.25
PLE."
::= { x25 2 }
x25OperEntry OBJECT-TYPE
SYNTAX X25OperEntry
ACCESS not-accessible
STATUS mandatory
DESCRIPTION
"Entries of x25OperTable."
INDEX { x25OperIndex }
::= { x25OperTable 1 }
X25OperEntry ::= SEQUENCE {
x25OperIndex
PositiveInteger,
x25OperInterfaceMode
INTEGER,
x25OperMaxActiveCircuits
INTEGER,
x25OperPacketSequencing
INTEGER,
x25OperRestartTimer
PositiveInteger,
x25OperCallTimer
PositiveInteger,
x25OperResetTimer
PositiveInteger,
x25OperClearTimer
PositiveInteger,
x25OperWindowTimer
PositiveInteger,
x25OperDataRxmtTimer
PositiveInteger,
x25OperInterruptTimer
PositiveInteger,
x25OperRejectTimer
D. Throop [Page 20]
Internet Draft X.25 Packet Layer MIB April 1992
PositiveInteger,
x25OperRegistrationRequestTimer
PositiveInteger,
x25OperMinimumRecallTimer
PositiveInteger,
x25OperRestartCount
INTEGER,
x25OperResetCount
INTEGER,
x25OperClearCount
INTEGER,
x25OperDataRxmtCount
INTEGER,
x25OperRejectCount
INTEGER,
x25OperRegistrationRequestCount
INTEGER,
x25OperDefCallParamId
OBJECT IDENTIFIER,
x25OperLocalAddress
X121Address,
x25OperDataLinkId
OBJECT IDENTIFIER,
x25OperProtocolVersionSupported
OBJECT IDENTIFIER
}
x25OperIndex OBJECT-TYPE
SYNTAX PositiveInteger
ACCESS read-only
STATUS mandatory
DESCRIPTION
"A value that uniquely identifies the X.25
PLE subnetwork and matches its ifIndex
value. The object ifNumber specifies the
maximum value for this index."
::= { x25OperEntry 1 }
x25OperInterfaceMode OBJECT-TYPE
SYNTAX INTEGER {
dte(1),
dce(2) }
ACCESS read-only
STATUS mandatory
DESCRIPTION
D. Throop [Page 21]
Internet Draft X.25 Packet Layer MIB April 1992
"Identifies DCE/DTE mode in which the
interface operates."
REFERENCE "10733 5.9 interfaceMode"
::= { x25OperEntry 2 }
x25OperMaxActiveCircuits OBJECT-TYPE
SYNTAX INTEGER (0..4096)
ACCESS read-only
STATUS mandatory
DESCRIPTION
"Maximum number of circuits this PLE can
support."
REFERENCE "10733 5.9 maxActiveCircuits
See ISO 8208, Section 3.7"
::= { x25OperEntry 3 }
x25OperPacketSequencing OBJECT-TYPE
SYNTAX INTEGER {
modulo8(1),
modulo128(2) }
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The modulus of the packet sequence number
space."
REFERENCE "10733 extendedPacketSequencing;
See ISO 8208 Section 7.1.1"
::= { x25OperEntry 4 }
x25OperRestartTimer OBJECT-TYPE
SYNTAX PositiveInteger
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The T20 restart timer in milliseconds."
REFERENCE "10733 5.9 restartTime;
See ISO 8208 Section 4.1, table 26"
::= { x25OperEntry 5 }
x25OperCallTimer OBJECT-TYPE
SYNTAX PositiveInteger
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The T21 Call timer in milliseconds."
D. Throop [Page 22]
Internet Draft X.25 Packet Layer MIB April 1992
REFERENCE "10733 callTime;
See ISO 8208 Section 5.2.1, table 26"
::= { x25OperEntry 6 }
x25OperResetTimer OBJECT-TYPE
SYNTAX PositiveInteger
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The T22 Reset timer in milliseconds."
REFERENCE "10733 resetTime;
See ISO 8208 Section 8.1, table 26"
::= { x25OperEntry 7 }
x25OperClearTimer OBJECT-TYPE
SYNTAX PositiveInteger
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The T23 Clear timer in milliseconds."
REFERENCE "10733 clearTime;
See ISO 8208 Section 5.5.1, table 26"
::= { x25OperEntry 8 }
x25OperWindowTimer OBJECT-TYPE
SYNTAX PositiveInteger
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The T24 window status transmission timer
milliseconds. A value of 2147483647
indicates no window timer in use."
REFERENCE "10733 5.10.1 windowTime (opt);
See ISO 8208 Section 11.2.2, table 26"
::= { x25OperEntry 9 }
x25OperDataRxmtTimer OBJECT-TYPE
SYNTAX PositiveInteger
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The T25 Data Retransmission timer in
milliseconds. A value of 2147483647
indicates no data retransmission timer in
use."
D. Throop [Page 23]
Internet Draft X.25 Packet Layer MIB April 1992
REFERENCE "10733 5.10.1 dataRetransmissionTime (opt);
See ISO 8208 Section 11.2.1, table 26"
::= { x25OperEntry 10 }
x25OperInterruptTimer OBJECT-TYPE
SYNTAX PositiveInteger
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The T26 Interrupt timer in milliseconds. A
value of 2147483647 indicates interrupts are
not being used."
REFERENCE "10733 interruptTime;
See ISO 8208 Section 6.8.1, table 26"
::= { x25OperEntry 11 }
x25OperRejectTimer OBJECT-TYPE
SYNTAX PositiveInteger
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The T27 Reject retransmission timer in
milliseconds. A value of 2147483647
indicates no reject timer in use."
REFERENCE "10733 5.10.1 dataRejectTime (opt);
See ISO 8208 Section 13.4.1, table 26"
::= { x25OperEntry 12 }
x25OperRegistrationRequestTimer OBJECT-TYPE
SYNTAX PositiveInteger
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The T28 registration timer in milliseconds.
A value of 2147483647 indicates no
registration timer in use."
REFERENCE "10733 5.8.1 registrationRequestTime (opt);
See ISO 8208 Section 13.1.1.1, table 26"
::= { x25OperEntry 13 }
x25OperMinimumRecallTimer OBJECT-TYPE
SYNTAX PositiveInteger
ACCESS read-only
STATUS mandatory
DESCRIPTION
D. Throop [Page 24]
Internet Draft X.25 Packet Layer MIB April 1992
"Minimum time interval between unsuccessful
call attempts in milliseconds."
REFERENCE "10733 5.9 minimum RecallTimer"
::= { x25OperEntry 14 }
x25OperRestartCount OBJECT-TYPE
SYNTAX INTEGER (0..65535)
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The R20 restart retransmission count."
REFERENCE "10733 5.9 restartCount
See ISO 8208 Section 4.1, table 27"
::= { x25OperEntry 15 }
x25OperResetCount OBJECT-TYPE
SYNTAX INTEGER (0..65535)
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The r22 Reset retransmission count."
REFERENCE "10733 resetCount;
See section ISO 8208 8.1, table 27"
::= { x25OperEntry 16 }
x25OperClearCount OBJECT-TYPE
SYNTAX INTEGER (0..65535)
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The r23 Clear retransmission count."
REFERENCE "10733 clearCount;
See ISO 8208 Section 5.5.1, table 27"
::= { x25OperEntry 17 }
x25OperDataRxmtCount OBJECT-TYPE
SYNTAX INTEGER (0..65535)
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The R25 Data retransmission count."
REFERENCE "10733 5.10.1 dataRetransmissionCount (opt);
See ISO 8208 Section 11.2.1, table 27"
::= { x25OperEntry 18 }
D. Throop [Page 25]
Internet Draft X.25 Packet Layer MIB April 1992
x25OperRejectCount OBJECT-TYPE
SYNTAX INTEGER (0..65535)
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The R27 reject retransmission count."
REFERENCE "10733 5.10.1 dataRejectCount (opt)"
::= { x25OperEntry 19 }
x25OperRegistrationRequestCount OBJECT-TYPE
SYNTAX INTEGER (0..65535)
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The R28 Registration retransmission Count."
REFERENCE "10733 5.8.1 registrationRequestCount (opt);
See ISO 8208 Section 13.1.1.1, table 27"
::= { x25OperEntry 20 }
x25OperDefCallParamId OBJECT-TYPE
SYNTAX OBJECT IDENTIFIER
ACCESS read-only
STATUS mandatory
DESCRIPTION
"This identifies the instance of the
x25CallParmIndex for the entry in the
x25CallParmTable that contains the default
call parameters for this PLE."
::= { x25OperEntry 21 }
x25OperLocalAddress OBJECT-TYPE
SYNTAX X121Address
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The local address for this PLE subnetwork.
A zero length address maybe returned by PLEs
that only support PVCs."
REFERENCE "10733 5.9 localDTEAddress"
::= { x25OperEntry 22 }
x25OperDataLinkId OBJECT-TYPE
SYNTAX OBJECT IDENTIFIER
ACCESS read-only
STATUS mandatory
D. Throop [Page 26]
Internet Draft X.25 Packet Layer MIB April 1992
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."
::= { x25OperEntry 23 }
x25OperProtocolVersionSupported OBJECT-TYPE
SYNTAX OBJECT IDENTIFIER
ACCESS read-only
STATUS mandatory
DESCRIPTION
"Identifies the version of the X.25 protocol
this interface supports. Object identifiers
for common versions are defined below in the
x25ProtocolVersion subtree."
REFERENCE "10733 5.9 protocolVersionSupported"
::= { x25OperEntry 24 }
-- MIB-II also provides:
-- 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
-- receive from X.25
-- ifSpeed:
-- ifAdminStatus:
-- ifOperStatus
D. Throop [Page 27]
Internet Draft X.25 Packet Layer MIB April 1992
-- ifLastChange
-- ###########################################################
-- X.25 Statistics Table
-- ###########################################################
x25StatTable OBJECT-TYPE
SYNTAX SEQUENCE OF X25StatEntry
ACCESS not-accessible
STATUS mandatory
DESCRIPTION
"Statistics information about this X.25
PLE."
::= { x25 3 }
x25StatEntry OBJECT-TYPE
SYNTAX X25StatEntry
ACCESS not-accessible
STATUS mandatory
DESCRIPTION
"Entries of the x25StatTable."
INDEX { x25StatIndex }
::= { x25StatTable 1 }
X25StatEntry ::= SEQUENCE {
x25StatIndex
PositiveInteger,
x25StatInCalls
Counter,
x25StatInCallRefusals
Counter,
x25StatInProviderInitiatedClears
Counter,
x25StatInRemotelyInitiatedResets
Counter,
x25StatInProviderInitiatedResets
Counter,
x25StatInRestarts
Counter,
x25StatInDataPackets
Counter,
x25StatInAccusedOfProtocolErrors
Counter,
x25StatInInterrupts
D. Throop [Page 28]
Internet Draft X.25 Packet Layer MIB April 1992
Counter,
x25StatOutCallAttempts
Counter,
x25StatOutCallFailures
Counter,
x25StatOutInterrupts
Counter,
x25StatOutgoingCircuits
Gauge,
x25StatIncomingCircuits
Gauge,
x25StatTwowayCircuits
Gauge,
x25StatNumberPvcs
Gauge,
x25StatRestartTimeouts
Counter,
x25StatCallTimeouts
Counter,
x25StatResetTimeouts
Counter,
x25StatClearTimeouts
Counter,
x25StatDataRxmtTimeouts
Counter,
x25StatInterruptTimeouts
Counter,
x25StatRetryCountExceededs
Counter,
x25StatClearCountExceededs
Counter
}
x25StatIndex OBJECT-TYPE
SYNTAX PositiveInteger
ACCESS read-only
STATUS mandatory
DESCRIPTION
"A value that uniquely identifies the X.25
PLE subnetwork and matches its ifIndex
value. The object ifNumber specifies the
maximum value for this index."
::= { x25StatEntry 1 }
x25StatInCalls OBJECT-TYPE
D. Throop [Page 29]
Internet Draft X.25 Packet Layer MIB April 1992
SYNTAX Counter
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The number of incoming calls received."
::= { x25StatEntry 2 }
x25StatInCallRefusals OBJECT-TYPE
SYNTAX Counter
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The number of incoming calls refused."
::= { x25StatEntry 3 }
x25StatInProviderInitiatedClears 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"
::= { x25StatEntry 4 }
x25StatInRemotelyInitiatedResets OBJECT-TYPE
SYNTAX Counter
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The number of reset requests received with
cause code DTE initiated."
REFERENCE "10733 remotelyInitiatedResets"
::= { x25StatEntry 5 }
x25StatInProviderInitiatedResets 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"
::= { x25StatEntry 6 }
D. Throop [Page 30]
Internet Draft X.25 Packet Layer MIB April 1992
x25StatInRestarts 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"
::= { x25StatEntry 7 }
x25StatInDataPackets OBJECT-TYPE
SYNTAX Counter
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The number of data packets received."
REFERENCE "10733 5.9 dataPacketsReceived."
::= { x25StatEntry 8 }
x25StatInAccusedOfProtocolErrors OBJECT-TYPE
SYNTAX Counter
ACCESS read-only
STATUS mandatory
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"
::= { x25StatEntry 9 }
x25StatInInterrupts 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"
::= { x25StatEntry 10 }
x25StatOutCallAttempts OBJECT-TYPE
SYNTAX Counter
D. Throop [Page 31]
Internet Draft X.25 Packet Layer MIB April 1992
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The number of calls attempted."
REFERENCE "10733 5.9 callAttempts"
::= { x25StatEntry 11 }
x25StatOutCallFailures OBJECT-TYPE
SYNTAX Counter
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The number of call attempts which failed."
::= { x25StatEntry 12 }
x25StatOutInterrupts OBJECT-TYPE
SYNTAX Counter
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The number of interrupt packets send by the
PLE or over the PVC/VC."
REFERENCE "10733 InterruptPacketsSent"
::= { x25StatEntry 13 }
x25StatOutgoingCircuits OBJECT-TYPE
SYNTAX Gauge
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The number of active outgoing circuits.
This includes call requests sent but not yet
confirmed. This does not count PVCs."
::= { x25StatEntry 14 }
x25StatIncomingCircuits OBJECT-TYPE
SYNTAX Gauge
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The Number of active Incoming Circuits.
This includes any call indications received
but not yet acknowledged. This does not
count PVCs."
::= { x25StatEntry 15 }
D. Throop [Page 32]
Internet Draft X.25 Packet Layer MIB April 1992
x25StatTwowayCircuits OBJECT-TYPE
SYNTAX Gauge
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The number of active two-way Circuits.
This includes call requests sent but not yet
confirmed. This does not count PVCs."
::= { x25StatEntry 16 }
x25StatNumberPvcs OBJECT-TYPE
SYNTAX Gauge
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The number of PVCs configured in this PLE."
::= { x25StatEntry 17 }
x25StatRestartTimeouts OBJECT-TYPE
SYNTAX Counter
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The number of times the T20 restart timer
expired."
REFERENCE "10733 5.9 restartTimeouts"
::= { x25StatEntry 18 }
x25StatCallTimeouts OBJECT-TYPE
SYNTAX Counter
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The number of times the T21 call timer
expired."
REFERENCE "10733 5.9 callTimeouts"
::= { x25StatEntry 19 }
x25StatResetTimeouts OBJECT-TYPE
SYNTAX Counter
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The number of times the T22 reset timer
expired."
D. Throop [Page 33]
Internet Draft X.25 Packet Layer MIB April 1992
REFERENCE "10733 5.9 resetTimeouts"
::= { x25StatEntry 20 }
x25StatClearTimeouts OBJECT-TYPE
SYNTAX Counter
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The number of times the T23 clear timer
expired."
REFERENCE "10733 5.9 clearTimeouts"
::= { x25StatEntry 21 }
x25StatDataRxmtTimeouts OBJECT-TYPE
SYNTAX Counter
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The number of times the T25 data timer
expired."
REFERENCE "10733 5.9 dataRetransmissionsTimerExpiries"
::= { x25StatEntry 22 }
x25StatInterruptTimeouts OBJECT-TYPE
SYNTAX Counter
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The number of times the T26 interrupt timer
expired."
REFERENCE "10733 5.9 interruptTimerExpires"
::= { x25StatEntry 23 }
x25StatRetryCountExceededs OBJECT-TYPE
SYNTAX Counter
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The number of times a retry counter was
exhausted."
REFERENCE "10733 5.9 retryCountsExceeded"
::= { x25StatEntry 24 }
x25StatClearCountExceededs OBJECT-TYPE
SYNTAX Counter
D. Throop [Page 34]
Internet Draft X.25 Packet Layer MIB April 1992
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The number of times the R23 clear count was
exceeded."
REFERENCE "10733 5.9 clearCountsExceeded"
::= { x25StatEntry 25 }
-- MIB-II 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.
-- ifOutOctets: Number of data octets delivered by
-- X.25 to upper layers.
-- ifOutUcastPkts: Number of packets sent to peer PLE.
-- ###########################################################
-- X.25 Channel Table
-- ###########################################################
x25ChannelTable OBJECT-TYPE
SYNTAX SEQUENCE OF X25ChannelEntry
ACCESS not-accessible
STATUS mandatory
DESCRIPTION
"These objects contain information about the
channel number configuration in an X.25
PLE."
REFERENCE "See ISO 8208, Section 3.7"
::= { x25 4 }
D. Throop [Page 35]
Internet Draft X.25 Packet Layer MIB April 1992
x25ChannelEntry OBJECT-TYPE
SYNTAX X25ChannelEntry
ACCESS not-accessible
STATUS mandatory
DESCRIPTION
"Entries of x25ChannelTable."
REFERENCE "This provides the information available
in 10733 logicalChannelAssignments."
INDEX { x25ChannelIndex }
::= { x25ChannelTable 1 }
X25ChannelEntry ::= SEQUENCE {
x25ChannelIndex
PositiveInteger,
x25ChannelLIC
INTEGER,
x25ChannelHIC
INTEGER,
x25ChannelLTC
INTEGER,
x25ChannelHTC
INTEGER,
x25ChannelLOC
INTEGER,
x25ChannelHOC
INTEGER
}
x25ChannelIndex OBJECT-TYPE
SYNTAX PositiveInteger
ACCESS read-only
STATUS mandatory
DESCRIPTION
"A value that uniquely identifies the X.25
PLE subnetwork and matches its ifIndex
value. The object ifNumber specifies the
maximum value for this index."
::= { x25ChannelEntry 1 }
x25ChannelLIC OBJECT-TYPE
SYNTAX INTEGER (1..4096)
ACCESS read-write
STATUS mandatory
DESCRIPTION
"Lowest Incoming channel."
D. Throop [Page 36]
Dean Throop throop@dg-rtp.dg.com
- Updated X.25 MIB part 1 of 2 Dean D. Throop