As per Relevance of the word indicate, we have this rfc below:
Network Working Group D. Throop,
Request for Comments: 1382 Data General
November 1992
SNMP MIB Extension for the X.25 Packet
Status of this
This RFC specifies an IAB standards track protocol for the
community, and requests discussion and suggestions for improvements
Please refer to the current edition of the "IAB Official
Standards" for the standardization state and status of this protocol
Distribution of this memo is unlimited
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
X.25. The objects defined here, along with the objects in the "
MIB Extension for LAPB" [9] and the "Definitions of Managed
for RS-232-like Hardware Devices" [8], combine to allow management
an X.25 protocol stack
Table of
1. The Network Management Framework ....................... 2
2. Objects ................................................ 2
2.1 Format of Definitions ................................. 3
3. Overview ............................................... 3
3.1 Informal Overview ..................................... 3
3.2 Textual Conventions ................................... 4
3.3 Structure of MIB ...................................... 4
3.4 Tables ................................................ 5
3.5 Table Usage ........................................... 6
3.6 Conformance ........................................... 6
4. Object Definitions ..................................... 7
5. Appendix: Revision History ............................. 62
July 30 1992 ........................................... 62
June 26 1992 ........................................... 62
June 1992 .............................................. 63
April 1992 ............................................. 63
February 1992 .......................................... 65
October 1991 ........................................... 65
June 1991 .............................................. 66
April 1991 ............................................. 66
6. Acknowledgements ....................................... 66
Throop [Page 1]
RFC 1382 X.25 Packet Layer MIB November 1992
7. References ............................................. 67
8. Security Considerations ................................ 68
9. Author's Address ....................................... 69
1. The Network Management
The Internet-standard Network Management Framework consists of
components. These components give the rules for defining objects
the definitions of objects, and the protocol for
objects
The network management framework structures objects in an
information tree. The branches of the tree name objects and
leaves of the tree contain the values manipulated to
management. This tree is called the Management Information Base
MIB. The concepts of this tree are given in STD 16/RFC 1155, "
Structure of Management Information" or SMI [1]. The SMI defines
trunk of the tree and the types of objects used when defining
leaves. STD 16/RFC 1212, "Towards Concise MIB Definitions" [4],
defines a more concise description mechanism that preserves all
principals of the SMI
The core MIB definitions for the Internet suite of protocols can
found in RFC 1156 [2] "Management Information Base for
Management of TCP/IP-based internets". STD 17/RFC 1213 [5]
MIB-II, an evolution of MIB-I with changes to
implementation experience and new operational requirements
STD 15/RFC 1157 [3] defines the SNMP protocol itself. The
defines how to manipulate the objects in a remote MIB
The tree structure of the MIB allows new objects to be defined
the purpose of experimentation and evaluation
2.
The definition of an object in the MIB requires an object name
type. Object names and types are defined using the subset
Abstract Syntax Notation One (ASN.1) [6] defined in the SMI [1].
Objects are named using ASN.1 object identifiers,
assigned names, to specify object types. The object name,
with an optional object instance, uniquely identifies a
instance of an object. For human convenience, we often use a
string, termed the OBJECT DESCRIPTOR, to also refer to objects
Objects also have a syntax that defines the abstract data
corresponding to that object type. The ASN.1 language [6]
the primitives used for this purpose. The SMI [1]
Throop [Page 2]
RFC 1382 X.25 Packet Layer MIB November 1992
restricts the ASN.1 constructs which may be used for simplicity
ease of implementation. The encoding of an object type
describes how to represent an object using ASN.1 encoding rules [7],
for purposes of dealing with the SNMP protocol
2.1. Format of
Section 4 contains the specification of all object types defined
this MIB module. The object types are defined using the
defined in the SMI, as amended by the extensions specified
"Towards Concise MIB Definitions" [4].
3.
3.1. Informal
This section describes how the objects defined below relate
other MIBs. This section is only informational to help
how the pieces fit together
The objects defined below are used in conjunction with MIB-II
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
interfaces in the ifTable defined in MIB-II. There will be
interface for LAPB and another interface for the packet layer
X.25. There will also be objects defined in the RS-232-like MIB
the physical sync line
Each software interface identifies the layer below it used to
and receive packets. The X.25 MIB object, defined below
x25OperDataLinkId, specifies an instance of lapbAdmnIndex for
LAPB interface under that X.25. The LAPB object, lapbOperPortId
identifies an instance of the rs232PortIndex for the the Sync
used by LAPB
For X.25 running over LAPB over Ethernet, the lapbOperPortId
identify the instance of ifIndex for the Ethernet interface
Each X.25 subnetwork will have separate entries in the ifTable.
a system with two X.25 lines would have two ifTable entries for
two X.25 packet layers and two other entries for the two
interfaces. Each X.25 Packet Layer MIB would identify the instance
the LAPB MIB for the interface below it. Each LAPB MIB would
the Sync line below it. The system would also have two entries in
rs232PortTable and rs232SyncPortTable for the two physical lines
Since the ifTable as defined in MIB-II is device independent,
doesn't have anything specific for any type of interface.
Throop [Page 3]
RFC 1382 X.25 Packet Layer MIB November 1992
objects below define the X.25 packet layer specific information
an interface of type X.25. Different X.25 interfaces can also
differentiated by matching the values of ifIndex with x25AdmnIndex
3.2. Textual
This MIB introduces a new data type as a textual convention for
with X.25. This textual convention enhances the readability of
specification and can ease comparison with other specifications
appropriate. It should be noted that the introduction of
textual conventions has no effect on either the syntax nor
semantics of any managed objects. These conventions are merely
artifact of the explanatory method used. Objects defined in terms
one of these methods are always encoded by means of the rules
define the primitive type. Hence, no changes to the SMI or the
are necessary to accommodate these textual conventions which
adopted merely for the convenience of readers and writers in
of the elusive goal of clear, concise, and unambiguous MIB documents
This MIB introduces the data type of
X121
3.3. Structure of
Instances of the objects defined below represent attributes of
X.25 Packet Layer interface. At present these interfaces
identified by an ifType object in the Internet-standard MIB-II [5]
of
ddn-x25(4),
rfc887-x25(5).
For these interfaces, the value of the ifSpecific variable in
MIB-II [5] has the OBJECT IDENTIFIER value
x25 OBJECT IDENTIFIER ::= { transmission 5 }
The objects defined below are similar to those defined in a draft
document for X.25 management [11]. Some object definitions
reference the ISO specification for X.25 [10] to specify the
that will give the reader additional information about the object
Access to those documents maybe useful (but isn't essential)
understand the names and semantics of some objects. The
of these objects with the ISO objects minimizes the
required by those systems that support both OSI and TCP/IP
protocols
Throop [Page 4]
RFC 1382 X.25 Packet Layer MIB November 1992
Since the objects defined here are extensions to the
Standard MIB [2] and thus also an extension of the second version
MIB-II [5], the objects defined here explicitly do not
objects defined in existing standards. In some
clarification of how to apply those objects has been given
The relationship between an X.25 Packet Layer interface and
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
used to identify corresponding instances of the objects
below
3.4.
The objects below form several tables. These tables are
x25
x25
x25
x25
x25
x25
x25
The x25AdmnTable defines objects for the parameters of an X.25
interface which the administrator can read and set. These
are used at interface initialization time to start the interface
Once the interface has started, changes to the objects in
Administration table may not take affect until the interface is re
initialized
The x25OperTable defines objects that report the current
used by a running interface. These objects are read-only
The x25StatTable defines objects that report operational
for an X.25 interface. These are read-only counters of events
occurred at the interface
The x25ChannelTable defines objects to allow the administrator
manage the division of channel numbers
The x25CircuitTable defines objects that return information
existing X.25 circuits. These entries result from calls placed
answered by the PLE or from PVCs
The x25ClearedCircuitTable contains objects for recording
termination information from circuits that cleared abnormally
Throop [Page 5]
RFC 1382 X.25 Packet Layer MIB November 1992
The x25CallParmTable defines the call parameters used to call
systems. This table contains call parameter entries which
referenced by other tables. For example, the x25AdmnTable has
object that identifies the entry in the table for the default
parameters. The x25CircuitTable has one object that identifies
entry in the x25CallParmTable for the parameters in use by
circuit. Other MIBs may also reference entries to identify
parameters to use to make X.25 calls
3.5. Table
Different tables provide different functions. The administrator
the starting X.25 parameters in the x25AdmnTable for the X.25 PLE
these objects include a reference to the x25CallParmTable entry
identify the default call parameters for the PLE. Once all
parameters are set, the administrator initializes the interface.
part of initializing the interface, the operating parameters
copied into the interface from the x25AdmnTable; these parameters
viewable by getting the objects in the x25OperTable. (The
maybe started by setting the value of ifAdminStatus to up.) If
PVCs are configured, their parameters can be set in the
x25CircuitTable before initializing the interface; this should
done in conjunction with configuring higher layer entities to use
PVCs via the MIBs for those entities
Once the PLE completes initialization, it makes additional entries
the x25circuitTable for calls placed or answered. When a circuit
cleared, the status of the entry for the circuit is set to
and, if the clear is abnormal, an entry will also be made in
x25ClearedCircuitTable. An entry in the x25CircuitTable with
status of closed maybe deleted by the agent at its convenience.
closed entry will always be reused at the time the PLE re-
the channel number of the entry for another call. The
parameters used for a circuit can be found by looking in
x25CircuitTable and following the x25CircuitCallParamId pointer
the entry in the x25CallParmTable that contains the parameters
There are no mechanisms in the X.25 MIB for telling the PLE to
an X.25 call. Such mechanisms belong in the MIBs for the higher
entities that use the X.25 circuits
3.6.
All the objects defined here are mandatory. To claim conformance
this MIB an implementation must support all objects. However
objects pertain to features that are optional. There are
defined for those objects that indicate the implementation does
support the optional feature. The agent for such an
Throop [Page 6]
RFC 1382 X.25 Packet Layer MIB November 1992
must support reading the object and return the value that
the optional feature isn't supported and reject set requests
change the object
Some optional features have more than one object that pertain to
(window rotation has a timer, a count, and a counter for
runouts). In such case, any object which indicates the
feature isn't supported is sufficient to indicate the feature isn'
supported and the values of the other objects relative to
feature are undefined
4. Object
RFC1382-MIB DEFINITIONS ::=
Counter, Gauge,
FROM RFC1155-
OBJECT-
FROM RFC-1212
DisplayString,
FROM RFC1213-
TRAP-
FROM RFC-1215
FROM RFC1271-
PositiveInteger
FROM RFC1381-MIB
x25 OBJECT IDENTIFIER ::= { transmission 5 }
-- Support of the X25 subtree and all subtrees under
-- is mandatory for all agents of system that implement X.25.
X121Address ::= OCTET STRING (SIZE(0..17))
-- 0 to 17 bytes in length containing the
-- characters [0-9], each octet contains one
-- of the address
-- ###########################################################
-- X.25 Administration
-- ###########################################################
x25AdmnTable OBJECT-
Throop [Page 7]
RFC 1382 X.25 Packet Layer MIB November 1992
SYNTAX SEQUENCE OF X25
ACCESS not-
STATUS
"This table contains the
set configuration parameters for an X.25
Packet Level Entity (PLE).
Most of the objects in this table
corresponding objects in the x25OperTable
This table contains the values as last
by the administrator. The x25
contains the values actually in use by
X.25 PLE
Changing an administrative value may or
not change a current operating value.
operating value may not change until
interface is restarted.
implementations may change the
immediately upon changing the
table. All implementations are required
load the values from the
table when initializing a PLE."
::= { x25 1 }
x25AdmnEntry OBJECT-
SYNTAX X25
ACCESS not-
STATUS
"Entries of x25AdmnTable."
INDEX { x25AdmnIndex }
::= { x25AdmnTable 1 }
X25AdmnEntry ::= SEQUENCE {
x25
IfIndexType
x25
INTEGER
x25
INTEGER
x25
INTEGER
x25
PositiveInteger
x25
PositiveInteger
Throop [Page 8]
RFC 1382 X.25 Packet Layer MIB November 1992
x25
PositiveInteger
x25
PositiveInteger
x25
PositiveInteger
x25
PositiveInteger
x25
PositiveInteger
x25
PositiveInteger
x25
PositiveInteger
x25
PositiveInteger
x25
INTEGER
x25
INTEGER
x25
INTEGER
x25
INTEGER
x25
INTEGER
x25
INTEGER
x25
INTEGER
x25
OBJECT IDENTIFIER
x25
X121Address
x25
OBJECT
}
x25AdmnIndex OBJECT-
SYNTAX
ACCESS read-
STATUS
"The ifIndex value for the X.25 Interface."
::= { x25AdmnEntry 1 }
x25AdmnInterfaceMode OBJECT-
SYNTAX INTEGER {
Throop [Page 9]
RFC 1382 X.25 Packet Layer MIB November 1992
dte (1),
dce (2),
dxe (3)
}
ACCESS read-
STATUS
"Identifies DCE/DTE mode in which
interface operates. A value of
indicates the mode will be determined by
negotiation."
REFERENCE "10733 5.9 interfaceMode
::= { x25AdmnEntry 2 }
x25AdmnMaxActiveCircuits OBJECT-
SYNTAX INTEGER (0..4096)
ACCESS read-
STATUS
"The maximum number of circuits this PLE
support; including PVCs."
REFERENCE "10733 5.9 maxActiveCircuits
See ISO 8208, Section 3.7"
::= { x25AdmnEntry 3 }
x25AdmnPacketSequencing OBJECT-
SYNTAX INTEGER {
modulo8 (1),
modulo128 (2)
}
ACCESS read-
STATUS
"The modulus of the packet sequence
space."
REFERENCE "10733 extendedPacketSequencing
See ISO 8208 Section 7.1.1"
::= { x25AdmnEntry 4 }
x25AdmnRestartTimer OBJECT-
SYNTAX
ACCESS read-
STATUS
"The T20 restart timer in milliseconds."
REFERENCE "10733 5.9
See ISO 8208 Section 4.1, table 26"
::= { x25AdmnEntry 5 }
Throop [Page 10]
RFC 1382 X.25 Packet Layer MIB November 1992
x25AdmnCallTimer OBJECT-
SYNTAX
ACCESS read-
STATUS
"The T21 Call timer in milliseconds."
REFERENCE "10733 callTime
See ISO 8208 Section 5.2.1, table 26"
::= { x25AdmnEntry 6 }
x25AdmnResetTimer OBJECT-
SYNTAX
ACCESS read-
STATUS
"The T22 Reset timer in milliseconds."
REFERENCE "10733 resetTime
See ISO 8208 Section 8.1, table 26"
::= { x25AdmnEntry 7 }
x25AdmnClearTimer OBJECT-
SYNTAX
ACCESS read-
STATUS
"The T23 Clear timer in milliseconds."
REFERENCE "10733 clearTime
See ISO 8208 Section 5.5.1, table 26"
::= { x25AdmnEntry 8 }
x25AdmnWindowTimer OBJECT-
SYNTAX
ACCESS read-
STATUS
"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"
::= { x25AdmnEntry 9 }
x25AdmnDataRxmtTimer OBJECT-
SYNTAX
ACCESS read-
STATUS
"The T25 data retransmission timer
Throop [Page 11]
RFC 1382 X.25 Packet Layer MIB November 1992
milliseconds. A value of 2147483647
indicates no data retransmission timer
use."
REFERENCE "10733 5.10.1 dataRetransmissionTime (opt);
See ISO 8208 Section 11.2.1, table 26"
::= { x25AdmnEntry 10 }
x25AdmnInterruptTimer OBJECT-
SYNTAX
ACCESS read-
STATUS
"The T26 interrupt timer in milliseconds.
value of 2147483647 indicates no
timer in use."
REFERENCE "10733 interruptTime
See ISO 8208 Section 6.8.1, table 26"
::= { x25AdmnEntry 11 }
x25AdmnRejectTimer OBJECT-
SYNTAX
ACCESS read-
STATUS
"The T27 Reject retransmission timer
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-
SYNTAX
ACCESS read-
STATUS
"The T28 registration timer in milliseconds
A value of 2147483647 indicates
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-
SYNTAX
ACCESS read-
STATUS
Throop [Page 12]
RFC 1382 X.25 Packet Layer MIB November 1992
"Minimum time interval between
call attempts in milliseconds."
REFERENCE "10733 5.9 minimum RecallTimer
::= { x25AdmnEntry 14 }
x25AdmnRestartCount OBJECT-
SYNTAX INTEGER (0..65535)
ACCESS read-
STATUS
"The R20 restart retransmission count."
REFERENCE "10733 5.9 restartCount
See ISO 8208 Section 4.1, table 27"
::= { x25AdmnEntry 15 }
x25AdmnResetCount OBJECT-
SYNTAX INTEGER (0..65535)
ACCESS read-
STATUS
"The r22 Reset retransmission count."
REFERENCE "10733 resetCount
See section ISO 8208 8.1, table 27"
::= { x25AdmnEntry 16 }
x25AdmnClearCount OBJECT-
SYNTAX INTEGER (0..65535)
ACCESS read-
STATUS
"The r23 Clear retransmission count."
REFERENCE "10733 clearCount
See ISO 8208 Section 5.5.1, table 27"
::= { x25AdmnEntry 17 }
x25AdmnDataRxmtCount OBJECT-
SYNTAX INTEGER (0..65535)
ACCESS read-
STATUS
"The R25 Data retransmission count.
value is irrelevant if
x25AdmnDataRxmtTimer indicates no timer
use."
REFERENCE "10733 5.10.1 dataRetransmissionCount (opt
See ISO 8208 Section 11.2.1, table 27"
::= { x25AdmnEntry 18 }
Throop [Page 13]
RFC 1382 X.25 Packet Layer MIB November 1992
x25AdmnRejectCount OBJECT-
SYNTAX INTEGER (0..65535)
ACCESS read-
STATUS
"The R27 reject retransmission count.
value is irrelevant if
x25AdmnRejectTimer indicates no timer
use."
REFERENCE "10733 5.10.1 dataRejectCount (opt)"
::= { x25AdmnEntry 19 }
x25AdmnRegistrationRequestCount OBJECT-
SYNTAX INTEGER (0..65535)
ACCESS read-
STATUS
"The R28 Registration retransmission Count
This value is irrelevant if
x25AdmnRegistrationRequestTimer indicates
timer in use."
REFERENCE "10733 5.8.1 registrationRequestCount (opt);
See ISO 8208 Section 13.1.1.1, table 27"
::= { x25AdmnEntry 20 }
x25AdmnNumberPVCs OBJECT-
SYNTAX INTEGER (0..4096)
ACCESS read-
STATUS
"The number of PVC configured for this PLE
The PVCs use channel numbers from 1 to
number."
::= { x25AdmnEntry 21 }
x25AdmnDefCallParamId OBJECT-
SYNTAX OBJECT
ACCESS read-
STATUS
"This identifies the instance of
x25CallParmIndex for the entry in
x25CallParmTable which contains the
call parameters for this PLE."
::= { x25AdmnEntry 22 }
x25AdmnLocalAddress OBJECT-
SYNTAX X121
Throop [Page 14]
RFC 1382 X.25 Packet Layer MIB November 1992
ACCESS read-
STATUS
"The local address for this PLE subnetwork
A zero length address maybe returned by
that only support PVCs."
REFERENCE "10733 5.9 localDTEAddress
::= { x25AdmnEntry 23 }
x25AdmnProtocolVersionSupported OBJECT-
SYNTAX OBJECT
ACCESS read-
STATUS
"Identifies the version of the X.25
this interface should support.
identifiers for common versions are
below in the x25ProtocolVersion subtree."
REFERENCE "10733 5.9 protocolVersionSupported
::= { x25AdmnEntry 24 }
-- ###########################################################
-- X.25 Operational
-- ###########################################################
x25OperTable OBJECT-
SYNTAX SEQUENCE OF X25
ACCESS not-
STATUS
"The operation parameters in use by the X.25
PLE."
::= { x25 2 }
x25OperEntry OBJECT-
SYNTAX X25
ACCESS not-
STATUS
"Entries of x25OperTable."
INDEX { x25OperIndex }
::= { x25OperTable 1 }
X25OperEntry ::= SEQUENCE {
x25
IfIndexType
x25
Throop [Page 15]
RFC 1382 X.25 Packet Layer MIB November 1992
INTEGER
x25
INTEGER
x25
INTEGER
x25
PositiveInteger
x25
PositiveInteger
x25
PositiveInteger
x25
PositiveInteger
x25
PositiveInteger
x25
PositiveInteger
x25
PositiveInteger
x25
PositiveInteger
x25
PositiveInteger
x25
PositiveInteger
x25
INTEGER
x25
INTEGER
x25
INTEGER
x25
INTEGER
x25
INTEGER
x25
INTEGER
x25
INTEGER
x25
OBJECT IDENTIFIER
x25
X121Address
x25
OBJECT IDENTIFIER
x25
OBJECT
}
Throop [Page 16]
RFC 1382 X.25 Packet Layer MIB November 1992
x25OperIndex OBJECT-
SYNTAX
ACCESS read-
STATUS
"The ifIndex value for the X.25 interface."
::= { x25OperEntry 1 }
x25OperInterfaceMode OBJECT-
SYNTAX INTEGER {
dte (1),
dce (2),
dxe (3)
}
ACCESS read-
STATUS
"Identifies DCE/DTE mode in which
interface operates. A value of
indicates the role will be determined by
negotiation at the Link Layer and
negotiation has not yet taken place."
REFERENCE "10733 5.9 interfaceMode
::= { x25OperEntry 2 }
x25OperMaxActiveCircuits OBJECT-
SYNTAX INTEGER (0..4096)
ACCESS read-
STATUS
"Maximum number of circuits this PLE
support."
REFERENCE "10733 5.9
See ISO 8208, Section 3.7"
::= { x25OperEntry 3 }
x25OperPacketSequencing OBJECT-
SYNTAX INTEGER {
modulo8 (1),
modulo128 (2)
}
ACCESS read-
STATUS
"The modulus of the packet sequence
space."
REFERENCE "10733 extendedPacketSequencing
See ISO 8208 Section 7.1.1"
Throop [Page 17]
RFC 1382 X.25 Packet Layer MIB November 1992
::= { x25OperEntry 4 }
x25OperRestartTimer OBJECT-
SYNTAX
ACCESS read-
STATUS
"The T20 restart timer in milliseconds."
REFERENCE "10733 5.9 restartTime
See ISO 8208 Section 4.1, table 26"
::= { x25OperEntry 5 }
x25OperCallTimer OBJECT-
SYNTAX
ACCESS read-
STATUS
"The T21 Call timer in milliseconds."
REFERENCE "10733 callTime
See ISO 8208 Section 5.2.1, table 26"
::= { x25OperEntry 6 }
x25OperResetTimer OBJECT-
SYNTAX
ACCESS read-
STATUS
"The T22 Reset timer in milliseconds."
REFERENCE "10733 resetTime
See ISO 8208 Section 8.1, table 26"
::= { x25OperEntry 7 }
x25OperClearTimer OBJECT-
SYNTAX
ACCESS read-
STATUS
"The T23 Clear timer in milliseconds."
REFERENCE "10733 clearTime
See ISO 8208 Section 5.5.1, table 26"
::= { x25OperEntry 8 }
x25OperWindowTimer OBJECT-
SYNTAX
ACCESS read-
STATUS
"The T24 window status transmission
Throop [Page 18]
RFC 1382 X.25 Packet Layer MIB November 1992
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-
SYNTAX
ACCESS read-
STATUS
"The T25 Data Retransmission timer
milliseconds. A value of 2147483647
indicates no data retransmission timer
use."
REFERENCE "10733 5.10.1 dataRetransmissionTime (opt);
See ISO 8208 Section 11.2.1, table 26"
::= { x25OperEntry 10 }
x25OperInterruptTimer OBJECT-
SYNTAX
ACCESS read-
STATUS
"The T26 Interrupt timer in milliseconds.
value of 2147483647 indicates interrupts
not being used."
REFERENCE "10733 interruptTime
See ISO 8208 Section 6.8.1, table 26"
::= { x25OperEntry 11 }
x25OperRejectTimer OBJECT-
SYNTAX
ACCESS read-
STATUS
"The T27 Reject retransmission timer
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-
SYNTAX
ACCESS read-
STATUS
Throop [Page 19]
RFC 1382 X.25 Packet Layer MIB November 1992
"The T28 registration timer in milliseconds
A value of 2147483647 indicates
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-
SYNTAX
ACCESS read-
STATUS
"Minimum time interval between
call attempts in milliseconds."
REFERENCE "10733 5.9 minimum RecallTimer
::= { x25OperEntry 14 }
x25OperRestartCount OBJECT-
SYNTAX INTEGER (0..65535)
ACCESS read-
STATUS
"The R20 restart retransmission count."
REFERENCE "10733 5.9
See ISO 8208 Section 4.1, table 27"
::= { x25OperEntry 15 }
x25OperResetCount OBJECT-
SYNTAX INTEGER (0..65535)
ACCESS read-
STATUS
"The r22 Reset retransmission count."
REFERENCE "10733 resetCount
See section ISO 8208 8.1, table 27"
::= { x25OperEntry 16 }
x25OperClearCount OBJECT-
SYNTAX INTEGER (0..65535)
ACCESS read-
STATUS
"The r23 Clear retransmission count."
REFERENCE "10733 clearCount
See ISO 8208 Section 5.5.1, table 27"
::= { x25OperEntry 17 }
x25OperDataRxmtCount OBJECT-
Throop [Page 20]
RFC 1382 X.25 Packet Layer MIB November 1992
SYNTAX INTEGER (0..65535)
ACCESS read-
STATUS
"The R25 Data retransmission count.
value is undefined if
x25OperDataRxmtTimer indicates no timer
use."
REFERENCE "10733 5.10.1 dataRetransmissionCount (opt);
See ISO 8208 Section 11.2.1, table 27"
::= { x25OperEntry 18 }
x25OperRejectCount OBJECT-
SYNTAX INTEGER (0..65535)
ACCESS read-
STATUS
"The R27 reject retransmission count.
value is undefined if the x25
indicates no timer in use."
REFERENCE "10733 5.10.1 dataRejectCount (opt)"
::= { x25OperEntry 19 }
x25OperRegistrationRequestCount OBJECT-
SYNTAX INTEGER (0..65535)
ACCESS read-
STATUS
"The R28 Registration retransmission Count
This value is undefined if
x25OperREgistrationRequestTimer indicates
timer in use."
REFERENCE "10733 5.8.1 registrationRequestCount (opt);
See ISO 8208 Section 13.1.1.1, table 27"
::= { x25OperEntry 20 }
x25OperNumberPVCs OBJECT-
SYNTAX INTEGER (0..4096)
ACCESS read-
STATUS
"The number of PVC configured for this PLE
The PVCs use channel numbers from 1 to
number."
::= { x25OperEntry 21 }
x25OperDefCallParamId OBJECT-
SYNTAX OBJECT
Throop [Page 21]
RFC 1382 X.25 Packet Layer MIB November 1992
ACCESS read-
STATUS
"This identifies the instance of
x25CallParmIndex for the entry in
x25CallParmTable that contains the
call parameters for this PLE."
::= { x25OperEntry 22 }
x25OperLocalAddress OBJECT-
SYNTAX X121
ACCESS read-
STATUS
"The local address for this PLE subnetwork
A zero length address maybe returned by
that only support PVCs."
REFERENCE "10733 5.9 localDTEAddress
::= { x25OperEntry 23 }
x25OperDataLinkId OBJECT-
SYNTAX OBJECT
ACCESS read-
STATUS
"This identifies the instance of the
object in the first table of the most
specific MIB for the interface used by
PLE."
::= { x25OperEntry 24 }
x25OperProtocolVersionSupported OBJECT-
SYNTAX OBJECT
ACCESS read-
STATUS
"Identifies the version of the X.25
this interface supports. Object
for common versions are defined below in
x25ProtocolVersion subtree."
REFERENCE "10733 5.9 protocolVersionSupported
::= { x25OperEntry 25 }
-- MIB-II also provides
-- ifDescr
-- On an X.25 interface this must include
Throop [Page 22]
RFC 1382 X.25 Packet Layer MIB November 1992
-- information to enable the system's
-- to determine the appropriate
-- 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
-- translate between X.121 address and IP addresses
-- An interface of type rfc877-x25 will use
-- configuration table to translate between X.121
-- addresses and IP addresses
-- ifMtu: the maximum PDU a higher layer can pass to X.25
-- receive from X.25
-- ifSpeed
-- This will be the value of the local clock for this line
-- A value of zero indicates external clocking
-- ifAdminStatus
--
--
-- ###########################################################
-- X.25 Statistics
-- ###########################################################
x25StatTable OBJECT-
SYNTAX SEQUENCE OF X25
ACCESS not-
STATUS
"Statistics information about this X.25
PLE."
::= { x25 3 }
x25StatEntry OBJECT-
SYNTAX X25
ACCESS not-
STATUS
"Entries of the x25StatTable."
INDEX { x25StatIndex }
::= { x25StatTable 1 }
Throop [Page 23]
RFC 1382 X.25 Packet Layer MIB November 1992
X25StatEntry ::= SEQUENCE {
x25
IfIndexType
x25
Counter
x25
Counter
x25
Counter
x25
Counter
x25
Counter
x25
Counter
x25
Counter
x25
Counter
x25
Counter
x25
Counter
x25
Counter
x25
Counter
x25
Counter
x25
Gauge
x25
Gauge
x25
Gauge
x25
Counter
x25
Counter
x25
Counter
x25
Counter
x25
Counter
x25
Counter
x25
Throop [Page 24]
RFC 1382 X.25 Packet Layer MIB November 1992
Counter
x25
}
x25StatIndex OBJECT-
SYNTAX
ACCESS read-
STATUS
"The ifIndex value for the X.25 interface."
::= { x25StatEntry 1 }
x25StatInCalls OBJECT-
SYNTAX
ACCESS read-
STATUS
"The number of incoming calls received."
::= { x25StatEntry 2 }
x25StatInCallRefusals OBJECT-
SYNTAX
ACCESS read-
STATUS
"The number of incoming calls refused.
includes calls refused by the PLE and
higher layers. This also includes
cleared because of restricted fast select."
::= { x25StatEntry 3 }
x25StatInProviderInitiatedClears OBJECT-
SYNTAX
ACCESS read-
STATUS
"The number of clear requests with a
code other than DTE initiated."
REFERENCE "10733 providerInitiatedDisconnect
::= { x25StatEntry 4 }
x25StatInRemotelyInitiatedResets OBJECT-
SYNTAX
ACCESS read-
STATUS
"The number of reset requests received
Throop [Page 25]
RFC 1382 X.25 Packet Layer MIB November 1992
cause code DTE initiated."
REFERENCE "10733 remotelyInitiatedResets
::= { x25StatEntry 5 }
x25StatInProviderInitiatedResets OBJECT-
SYNTAX
ACCESS read-
STATUS
"The number of reset requests received
cause code other than DTE initiated."
REFERENCE "10733 ProviderInitiatedResets
::= { x25StatEntry 6 }
x25StatInRestarts OBJECT-
SYNTAX
ACCESS read-
STATUS
"The number of remotely initiated (
provider initiated) restarts experienced
the PLE excluding the restart
with bringing up the PLE interface.
only counts restarts received when the
already has an established connection
the remove PLE."
REFERENCE "10733 5.9 remotelyInitiatedRestarts
::= { x25StatEntry 7 }
x25StatInDataPackets OBJECT-
SYNTAX
ACCESS read-
STATUS
"The number of data packets received."
REFERENCE "10733 5.9 dataPacketsReceived."
::= { x25StatEntry 8 }
x25StatInAccusedOfProtocolErrors OBJECT-
SYNTAX
ACCESS read-
STATUS
"The number of packets received containing
procedure error cause code. These
clear, reset, restart, or
packets."
REFERENCE "CD 10733 5.9 accusedOfProtocolError
Throop [Page 26]
RFC 1382 X.25 Packet Layer MIB November 1992
::= { x25StatEntry 9 }
x25StatInInterrupts OBJECT-
SYNTAX
ACCESS read-
STATUS
"The number of interrupt packets received
the PLE or over the PVC/VC."
REFERENCE "10733 interruptPacketsReceived
::= { x25StatEntry 10 }
x25StatOutCallAttempts OBJECT-
SYNTAX
ACCESS read-
STATUS
"The number of calls attempted."
REFERENCE "10733 5.9 callAttempts
::= { x25StatEntry 11 }
x25StatOutCallFailures OBJECT-
SYNTAX
ACCESS read-
STATUS
"The number of call attempts which failed
This includes calls that were
because of restrictive fast select."
::= { x25StatEntry 12 }
x25StatOutInterrupts OBJECT-
SYNTAX
ACCESS read-
STATUS
"The number of interrupt packets send by
PLE or over the PVC/VC."
REFERENCE "10733 InterruptPacketsSent
::= { x25StatEntry 13 }
x25StatOutDataPackets OBJECT-
SYNTAX
ACCESS read-
STATUS
"The number of data packets sent by
PLE."
Throop [Page 27]
RFC 1382 X.25 Packet Layer MIB November 1992
REFERENCE "10733 dataPacketSent
::= { x25StatEntry 14 }
x25StatOutgoingCircuits OBJECT-
SYNTAX
ACCESS read-
STATUS
"The number of active outgoing circuits
This includes call requests sent but not
confirmed. This does not count PVCs."
::= { x25StatEntry 15 }
x25StatIncomingCircuits OBJECT-
SYNTAX
ACCESS read-
STATUS
"The number of active Incoming Circuits
This includes call indications received
not yet acknowledged. This does not
PVCs."
::= { x25StatEntry 16 }
x25StatTwowayCircuits OBJECT-
SYNTAX
ACCESS read-
STATUS
"The number of active two-way Circuits
This includes call requests sent but not
confirmed. This does not count PVCs."
::= { x25StatEntry 17 }
x25StatRestartTimeouts OBJECT-
SYNTAX
ACCESS read-
STATUS
"The number of times the T20 restart
expired."
REFERENCE "10733 5.9 restartTimeouts
::= { x25StatEntry 18 }
x25StatCallTimeouts OBJECT-
SYNTAX
ACCESS read-
STATUS
Throop [Page 28]
RFC 1382 X.25 Packet Layer MIB November 1992
"The number of times the T21 call
expired."
REFERENCE "10733 5.9 callTimeouts
::= { x25StatEntry 19 }
x25StatResetTimeouts OBJECT-
SYNTAX
ACCESS read-
STATUS
"The number of times the T22 reset
expired."
REFERENCE "10733 5.9 resetTimeouts
::= { x25StatEntry 20 }
x25StatClearTimeouts OBJECT-
SYNTAX
ACCESS read-
STATUS
"The number of times the T23 clear
expired."
REFERENCE "10733 5.9 clearTimeouts
::= { x25StatEntry 21 }
x25StatDataRxmtTimeouts OBJECT-
SYNTAX
ACCESS read-
STATUS
"The number of times the T25 data
expired."
REFERENCE "10733 5.9 dataRetransmissionsTimerExpiries
::= { x25StatEntry 22 }
x25StatInterruptTimeouts OBJECT-
SYNTAX
ACCESS read-
STATUS
"The number of times the T26 interrupt
expired."
REFERENCE "10733 5.9 interruptTimerExpires
::= { x25StatEntry 23 }
x25StatRetryCountExceededs OBJECT-
SYNTAX
Throop [Page 29]
RFC 1382 X.25 Packet Layer MIB November 1992
ACCESS read-
STATUS
"The number of times a retry counter
exhausted."
REFERENCE "10733 5.9 retryCountsExceeded
::= { x25StatEntry 24 }
x25StatClearCountExceededs OBJECT-
SYNTAX
ACCESS read-
STATUS
"The number of times the R23 clear count
exceeded."
REFERENCE "10733 5.9 clearCountsExceeded
::= { x25StatEntry 25 }
-- MIB-II also contains
-- ifInOctets: Number of data octets delivered to
-- layer entities
-- ifInUcastPkts: Number of packets with a clear M-
-- delivered to higher layer entities
-- ifDiscards: Number of packets dropped for lack of
-- ifInErrors: Number of packets received containing
-- REFERENCE
-- ifInUnknownProtos: Number of packets with unknown
-- identifier
-- ifOutOctets: Number of data octets delivered
-- X.25 to upper layers
-- ifOutUcastPkts: Number of packets with a clear M-
-- received from higher layer entities
-- ###########################################################
-- X.25 Channel
-- ###########################################################
x25ChannelTable OBJECT-
SYNTAX SEQUENCE OF X25
Throop [Page 30]
RFC 1382 X.25 Packet Layer MIB November 1992
ACCESS not-
STATUS
"These objects contain information about
channel number configuration in an X.25 PLE
These values are the configured values
changes in these values after the
has started may not be reflected in
operating PLE."
REFERENCE "See ISO 8208, Section 3.7"
::= { x25 4 }
x25ChannelEntry OBJECT-
SYNTAX X25
ACCESS not-
STATUS
"Entries of x25ChannelTable."
REFERENCE "This provides the information
in 10733 logicalChannelAssignments."
INDEX { x25ChannelIndex }
::= { x25ChannelTable 1 }
X25ChannelEntry ::= SEQUENCE {
x25
IfIndexType
x25
INTEGER
x25
INTEGER
x25
INTEGER
x25
INTEGER
x25
INTEGER
x25
}
x25ChannelIndex OBJECT-
SYNTAX
ACCESS read-
STATUS
"The ifIndex value for the X.25 Interface."
::= { x25ChannelEntry 1 }
Throop [Page 31]
RFC 1382 X.25 Packet Layer MIB November 1992
x25ChannelLIC OBJECT-
SYNTAX INTEGER (0..4095)
ACCESS read-
STATUS
"Lowest Incoming channel."
::= { x25ChannelEntry 2 }
x25ChannelHIC OBJECT-
SYNTAX INTEGER (0..4095)
ACCESS read-
STATUS
"Highest Incoming channel. A value of
indicates no channels in this range."
::= { x25ChannelEntry 3 }
x25ChannelLTC OBJECT-
SYNTAX INTEGER (0..4095)
ACCESS read-
STATUS
"Lowest Two-way channel."
::= { x25ChannelEntry 4 }
x25ChannelHTC OBJECT-
SYNTAX INTEGER (0..4095)
ACCESS read-
STATUS
"Highest Two-way channel. A value of
indicates no channels in this range."
::= { x25ChannelEntry 5 }
x25ChannelLOC OBJECT-
SYNTAX INTEGER (0..4095)
ACCESS read-
STATUS
"Lowest outgoing channel."
::= { x25ChannelEntry 6 }
x25ChannelHOC OBJECT-
SYNTAX INTEGER (0..4095)
ACCESS read-
STATUS
"Highest outgoing channel. A value of
Throop [Page 32]
RFC 1382 X.25 Packet Layer MIB November 1992
indicates no channels in this range."
::= { x25ChannelEntry 7 }
-- ###########################################################
-- X25 Per Circuits Information
-- ###########################################################
x25CircuitTable OBJECT-
SYNTAX SEQUENCE OF X25
ACCESS not-
STATUS
"These objects contain general
about a specific circuit of an X.25 PLE."
::= { x25 5 }
x25CircuitEntry OBJECT-
SYNTAX X25
ACCESS not-
STATUS
"Entries of x25CircuitTable."
INDEX { x25CircuitIndex
x25CircuitChannel }
::= { x25CircuitTable 1 }
X25CircuitEntry ::= SEQUENCE {
x25
IfIndexType
x25
INTEGER
x25
INTEGER
x25
TimeTicks
x25
INTEGER
x25
Counter
x25
Counter
x25
Counter
x25
Counter
Throop [Page 33]
RFC 1382 X.25 Packet Layer MIB November 1992
x25
Counter
x25
Counter
x25
Counter
x25
Counter
x25
Counter
x25
Counter
x25
Counter
x25
OBJECT IDENTIFIER
x25
X121Address
x25
X121Address
x25
X121Address
x25
}
x25CircuitIndex OBJECT-
SYNTAX
ACCESS read-
STATUS
"The ifIndex value for the X.25 Interface."
::= { x25CircuitEntry 1 }
x25CircuitChannel OBJECT-
SYNTAX INTEGER (0..4095)
ACCESS read-
STATUS
"The channel number for this circuit."
::= { x25CircuitEntry 2 }
x25CircuitStatus OBJECT-
SYNTAX INTEGER { -- state table
invalid (1),
closed (2), -- (p1)
calling (3), -- (p2,p3,p5)
open (4), -- (p4)
Throop [Page 34]
RFC 1382 X.25 Packet Layer MIB November 1992
clearing (5), -- (p6,p7)
pvc (6),
pvcResetting (7),
startClear (8), -- Close
startPvcResetting (9), -- Reset
other (10)
}
ACCESS read-
STATUS
"This object reports the current status
the circuit
An existing instance of this object can
be set to startClear, startPvcResetting,
invalid. An instance with the value
or open can only be set to startClear
that action will start clearing the circuit
An instance with the value PVC can only
set to startPvcResetting or invalid and
action resets the PVC or deletes the
respectively. The values startClear
startPvcResetting will never be returned
an agent. An attempt to set the status
an existing instance to a value other
one of these values will result in an error
A non-existing instance can be set to PVC
create a PVC if the implementation
dynamic creation of PVCs.
implementations may only allow creation
deletion of PVCs if the interface is down
Since the instance identifier will
the PLE index and the channel number
setting this object alone
sufficient information to create
instance. All the DEFVAL clauses for
other objects of this table are
for creating a PVC; PLEs creating
for placed or accepted calls will use
appropriate for the call rather than
value of the DEFVAL clause. Two
trying to create the same PVC can
from the return code which manager
and which failed (the failing manager
because it can not set a value of PVC for
existing object).
Throop [Page 35]
RFC 1382 X.25 Packet Layer MIB November 1992
An entry in the closed or invalid state
be deleted or reused at the agent'
convence. If the entry is kept in
closed state, the values of the
associated with the entry must be correct
Closed implies the values in the
table are correct
The value of invalid indicates the
values in the table are invalid.
agents may never return a value of
because they dynamically allocate and
unused table entries. An agent for
statically configured systems can
invalid to indicate the entry has not
been used so the counters contain
information."
REFERENCE "See ISO 8208,
table 33 for (p) state table
::= { x25CircuitEntry 3 }
x25CircuitEstablishTime OBJECT-
SYNTAX
ACCESS read-
STATUS
"The value of sysUpTime when the channel
associated with this circuit. For
SVCs, this is the time the first call
was sent. For incoming SVCs, this is
time the call indication was received.
PVCs this is the time the PVC was able
pass data to a higher layer entity
loss of data."
::= { x25CircuitEntry 4 }
x25CircuitDirection OBJECT-
SYNTAX INTEGER {
incoming (1),
outgoing (2),
pvc (3)
}
ACCESS read-
STATUS
"The direction of the call that
this circuit."
REFERENCE "10733 direction
Throop [Page 36]
RFC 1382 X.25 Packet Layer MIB November 1992
DEFVAL { pvc }
::= { x25CircuitEntry 5 }
-- X25 Circuit data flow
x25CircuitInOctets OBJECT-
SYNTAX
ACCESS read-
STATUS
"The number of octets of user data
to upper layer."
REFERENCE "5.11 octetsReceivedCounter
::= { x25CircuitEntry 6 }
x25CircuitInPdus OBJECT-
SYNTAX
ACCESS read-
STATUS
"The number of PDUs received for
circuit."
REFERENCE "10733 5.11 dataPacketsReceived
::= { x25CircuitEntry 7 }
x25CircuitInRemotelyInitiatedResets OBJECT-
SYNTAX
ACCESS read-
STATUS
"The number of Resets received for
circuit with cause code of DTE initiated."
REFERENCE "10733 remotelyInitiatedResets
::= { x25CircuitEntry 8 }
x25CircuitInProviderInitiatedResets OBJECT-
SYNTAX
ACCESS read-
STATUS
"The number of Resets received for
circuit with cause code other than
initiated."
REFERENCE "10733 ProviderInitiatedResets
::= { x25CircuitEntry 9 }
x25CircuitInInterrupts OBJECT-
SYNTAX
Throop [Page 37]
RFC 1382 X.25 Packet Layer MIB November 1992
ACCESS read-
STATUS
"The number of interrupt packets
for this circuit."
REFERENCE "10733 interruptPacketsReceived
::= { x25CircuitEntry 10 }
x25CircuitOutOctets OBJECT-
SYNTAX
ACCESS read-
STATUS
"The number of octets of user data sent
this circuit."
REFERENCE "10733 5.11 octetsSentCounter
::= { x25CircuitEntry 11 }
x25CircuitOutPdus OBJECT-
SYNTAX
ACCESS read-
STATUS
"The number of PDUs sent for this circuit."
REFERENCE "10733 5.11 dataPacketsSent
::= { x25CircuitEntry 12 }
x25CircuitOutInterrupts OBJECT-
SYNTAX
ACCESS read-
STATUS
"The number of interrupt packets sent
this circuit."
REFERENCE "10733 interruptPacketsSent
::= { x25CircuitEntry 13 }
-- X25 circuit timer
x25CircuitDataRetransmissionTimeouts OBJECT-
SYNTAX
ACCESS read-
STATUS
"The number of times the T25
retransmission timer expired for
circuit."
Throop [Page 38]
RFC 1382 X.25 Packet Layer MIB November 1992
REFERENCE "10733 5.11 dataRetransmissionTimerExpiries
::= { x25CircuitEntry 14 }
x25CircuitResetTimeouts OBJECT-
SYNTAX
ACCESS read-
STATUS
"The number of times the T22 reset
expired for this circuit."
REFERENCE "10733 5.11 resetTimeouts
::= { x25CircuitEntry 15 }
x25CircuitInterruptTimeouts OBJECT-
SYNTAX
ACCESS read-
STATUS
"The number of times the T26 Interrupt
expired for this circuit."
REFERENCE "10733 interruptTimerExpiries
::= { x25CircuitEntry 16 }
x25CircuitCallParamId OBJECT-
SYNTAX OBJECT
ACCESS read-
STATUS
"This identifies the instance of
x25CallParmIndex for the entry in
x25CallParmTable which contains the
parameters in use with this circuit.
entry referenced must contain the
that are currently in use by the
rather than proposed values. A value
NULL indicates the circuit is a PVC or
using all the default parameters."
DEFVAL { {0 0} }
::= { x25CircuitEntry 17 }
x25CircuitCalledDteAddress OBJECT-
SYNTAX X121
ACCESS read-
STATUS
"For incoming calls, this is the
address from the call indication packet
For outgoing calls, this is the
Throop [Page 39]
RFC 1382 X.25 Packet Layer MIB November 1992
address from the call confirmation packet
This will be zero length for PVCs."
REFERENCE "10733 calledDTEAddress
DEFVAL { ''h }
::= { x25CircuitEntry 18 }
x25CircuitCallingDteAddress OBJECT-
SYNTAX X121
ACCESS read-
STATUS
"For incoming calls, this is the
address from the call indication packet
For outgoing calls, this is the
address from the call confirmation packet
This will be zero length for PVCs."
REFERENCE "10733 callingDTEAddress
DEFVAL { ''h }
::= { x25CircuitEntry 19 }
x25CircuitOriginallyCalledAddress OBJECT-
SYNTAX X121
ACCESS read-
STATUS
"For incoming calls, this is the address
the call Redirection or Call
Notification facility if the call
deflected or redirected, otherwise it
be called address from the call
packet. For outgoing calls, this is
address from the call request packet.
will be zero length for PVCs."
REFERENCE "10733 originallyCalledAddress
DEFVAL { ''h }
::= { x25CircuitEntry 20 }
x25CircuitDescr OBJECT-
SYNTAX DisplayString (SIZE (0..255))
ACCESS read-
STATUS
"A descriptive string associated with
circuit. This provides a place for
agent to supply any descriptive
it knows about the use or owner of
circuit. The agent may return the
identifier and user name for the
Throop [Page 40]
RFC 1382 X.25 Packet Layer MIB November 1992
using the circuit. Alternative the
may return the name of the
entry that caused a bridge to establish
circuit. A zero length value indicates
agent doesn't have any
information."
DEFVAL { ''h }
::= { x25CircuitEntry 21 }
-- ###########################################################
-- The Cleared Circuit
-- ###########################################################
x25ClearedCircuitEntriesRequested OBJECT-
SYNTAX
ACCESS read-
STATUS
"The requested number of entries for
agent to keep in the x25
table."
::= { x25 6 }
x25ClearedCircuitEntriesGranted OBJECT-
SYNTAX
ACCESS read-
STATUS
"The actual number of entries the agent
keep in the x25ClearedCircuit Table."
::= { x25 7 }
x25ClearedCircuitTable OBJECT-
SYNTAX SEQUENCE OF X25
ACCESS not-
STATUS
"A table of entries about closed circuits
Entries must be made in this table
circuits are closed and the close request
close indication packet contains a
cause other than DTE Originated or
Diagnostic code field other than
Layer Initiated disconnection-normal.
agent may optionally make entries for
closes (to record closing facilities
Throop [Page 41]
RFC 1382 X.25 Packet Layer MIB November 1992
other information).
Agents will delete the oldest entry in
table when adding a new entry would
agent resources. Agents are required
keep the last entry put in the table and
keep more entries. The
x25OperClearEntriesGranted returns
maximum number of entries kept in
table."
REFERENCE "See ISO 8208 Section 12.2.3.1.1
and 12.2.3.1.2"
::= { x25 8 }
x25ClearedCircuitEntry OBJECT-
SYNTAX X25
ACCESS not-
STATUS
"Information about a cleared circuit."
INDEX { x25ClearedCircuitIndex }
::= { x25ClearedCircuitTable 1 }
X25ClearedCircuitEntry ::= SEQUENCE {
x25
PositiveInteger
x25
IfIndexType
x25
TimeTicks
x25
TimeTicks
x25
INTEGER
x25
INTEGER
x25
INTEGER
x25
Counter
x25
Counter
x25
X121Address
x25
X121Address
x25
OCTET
Throop [Page 42]
RFC 1382 X.25 Packet Layer MIB November 1992
}
x25ClearedCircuitIndex OBJECT-
SYNTAX
ACCESS read-
STATUS
"An index that uniquely distinguishes
entry in the clearedCircuitTable
another. This index will start
2147483647 and will decrease by one for
new entry added to the table. Upon
one, the index will reset to 2147483647.
Because the index starts at 2147483647
decreases, a manager may do a getnext
entry zero and obtain the most recent entry
When the index has the value of 1, the
entry will delete all entries in the
and that entry will be numbered 2147483647."
::= { x25ClearedCircuitEntry 1 }
x25ClearedCircuitPleIndex OBJECT-
SYNTAX
