X25 MIB part 2
"Dean D. Throop" <throop@dg-rtp.dg.com> Tue, 25 February 1992 19:30 UTC
Received: from nri.reston.va.us by NRI.NRI.Reston.VA.US id aa18615; 25 Feb 92 14:30 EST
Received: from dg-rtp.rtp.dg.com by NRI.NRI.Reston.VA.US id aa18569; 25 Feb 92 14:30 EST
Received: from commtg3.rtp.dg.com by dg-rtp.dg.com (5.4/dg-rtp-proto) id AA23853; Tue, 25 Feb 1992 13:54:26 -0500
Received: by commtg3 (5.4.1/rtp-s04) id AA18075; Tue, 25 Feb 1992 13:54:24 -0500
Date: Tue, 25 Feb 1992 13:54:24 -0500
From: "Dean D. Throop" <throop@dg-rtp.dg.com>
Message-Id: <9202251854.AA18075@commtg3>
To: x25mib@dg-rtp.dg.com
Subject: X25 MIB part 2
-- ###########################################################
-- The Cleared Circuit Table
-- ###########################################################
x25ClearedCircuitTable OBJECT-TYPE
SYNTAX SEQUENCE OF X25ClearedCircuitEntry
D. Throop [Page 29]
Internet Draft X.25 Packet Layer MIB February 1992
ACCESS not-accessible
STATUS mandatory
-- See ISO 8208 Section 12.2.3.1.1 and 12.2.3.1.2
DESCRIPTION
"A table of entries about closed circuits.
Entries must be made in this table when ever
circuits are closed and the close request or
close indication packet contains a clearing
cause other than DTE Originated or a
Diagnostic code field other than Higher
Layer Initiated disconnection-normal. An
agent may optionally make entries for normal
closes (to record closing facilities).
Agents will delete the oldest entry in the
table when adding a new entry would exceed
agent resources. Agents are required to
keep the last entry put in the table and may
keep more entries."
::= { x25 4 }
x25ClearedCircuitEntry OBJECT-TYPE
SYNTAX X25ClearedCircuitEntry
ACCESS not-accessible
STATUS mandatory
DESCRIPTION
"Information about a cleared circuit."
INDEX { x25ClearedCircuitIndex,
x25ClearedCircuitPleIndex }
::= { x25ClearedCircuitTable 1 }
X25ClearedCircuitEntry ::= SEQUENCE {
x25ClearedCircuitIndex
INTEGER,
x25ClearedCircuitPleIndex
INTEGER,
x25ClearedCircuitTimeCleared
TimeTicks,
x25ClearedCircuitChannel
INTEGER,
x25ClearedCircuitCodes
OCTET STRING,
x25ClearedCircuitCalledAddress
X25address,
D. Throop [Page 30]
Internet Draft X.25 Packet Layer MIB February 1992
x25ClearedCircuitCallingAddress
X25address,
x25ClearedCircuitClearFacilities
OCTET STRING
}
x25ClearedCircuitIndex OBJECT-TYPE
SYNTAX INTEGER (1..65535)
ACCESS read-only
STATUS mandatory
DESCRIPTION
"An index that uniquely distinguishes one
entry in the clearedCircuitTable from
another. This index will start at 65535 and
will decrease by one for each new entry
added to the table. Upon reaching one, the
index will reset to 65535. Because the
index starts at 65535 and decreases, a
manager may do a getnext on entry zero and
obtain the most recent entry (with a minor
exception when entry one is in use)."
::= { x25ClearedCircuitEntry 1 }
x25ClearedCircuitPleIndex OBJECT-TYPE
SYNTAX INTEGER (1..65535)
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The value of the x25PleIndex which cleared
the circuit that created the entry."
::= { x25ClearedCircuitEntry 2 }
x25ClearedCircuitTimeCleared OBJECT-TYPE
SYNTAX TimeTicks
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The value of sysUpTime when the circuit was
cleared."
::= { x25ClearedCircuitEntry 3 }
x25ClearedCircuitChannel OBJECT-TYPE
SYNTAX INTEGER (1..4096)
ACCESS read-only
D. Throop [Page 31]
Internet Draft X.25 Packet Layer MIB February 1992
STATUS mandatory
DESCRIPTION
"The channel number for the circuit that was
cleared."
::= { x25ClearedCircuitEntry 4 }
x25ClearedCircuitCodes OBJECT-TYPE
SYNTAX OCTET STRING (SIZE (2))
ACCESS read-only
STATUS mandatory
-- See ISO 8208 Section 12.2.3.1.1 and 12.2.3.1.2
DESCRIPTION
"The Clearing Cause and Diagnostic Code from
the clear request or clear indication packet
the cleared the circuit."
::= { x25ClearedCircuitEntry 5 }
x25ClearedCircuitCalledAddress OBJECT-TYPE
SYNTAX X25address
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The called address from the cleared
circuit."
::= { x25ClearedCircuitEntry 6 }
x25ClearedCircuitCallingAddress OBJECT-TYPE
SYNTAX X25address
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The calling address from the cleared
circuit."
::= { x25ClearedCircuitEntry 7 }
x25ClearedCircuitClearFacilities OBJECT-TYPE
SYNTAX OCTET STRING (SIZE (0..109))
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The facilities field from the clear request
or clear indication packet that cleared the
circuit. A size of zero indicates no
facilities were present."
::= { x25ClearedCircuitEntry 8 }
D. Throop [Page 32]
Internet Draft X.25 Packet Layer MIB February 1992
-- ###########################################################
-- The Call Parameter Table
-- ###########################################################
-- Default values for new connections
x25CallParmTable OBJECT-TYPE
SYNTAX SEQUENCE OF X25CallParmEntry
ACCESS not-accessible
STATUS mandatory
DESCRIPTION
"These objects contain the parameters that
can be varied between X.25 calls. The
entries in this table are independent of the
PLE. There exists only one of these tables
for the entire system. The indexes for the
entries are independent of any PLE or any
circuit. Other tables reference entries in
this table. Entries in this table can be
used for default PLE parameters, for
parameters to use to place/answer a call,
for the parameters currently in use for a
circuit, or parameters that were used by a
circuit."
::= { x25 5 }
x25CallParmEntry OBJECT-TYPE
SYNTAX X25CallParmEntry
ACCESS not-accessible
STATUS mandatory
DESCRIPTION
"Entries of x25CallParmTable."
INDEX { x25CallParmIndex }
::= { x25CallParmTable 1 }
X25CallParmEntry ::= SEQUENCE {
x25CallParmIndex
INTEGER,
x25CallParmCallTimer
INTEGER,
x25CallParmResetTimer
INTEGER,
x25CallParmClearTimer
INTEGER,
x25CallParmInterruptTime
D. Throop [Page 33]
Internet Draft X.25 Packet Layer MIB February 1992
INTEGER,
x25CallParmResetCount
INTEGER,
x25CallParmClearCount
INTEGER,
x25CallParmWindowTimer
INTEGER,
x25CallParmDataRxmtTimer
INTEGER,
x25CallParmDataRxmtCount
INTEGER,
x25CallParmRejectTimer
INTEGER,
x25CallParmRejectCount
INTEGER,
x25CallParmInPacketSize
INTEGER,
x25CallParmOutPacketSize
INTEGER,
x25CallParmInWindowSize
INTEGER,
x25CallParmOutWindowSize
INTEGER,
x25CallParmAcceptReverseCharging
INTEGER,
x25CallParmProposeReverseCharging
INTEGER,
x25CallParmFastSelect
INTEGER,
x25CallParmInThruPutClasSize
INTEGER,
x25CallParmOutThruPutClasSize
INTEGER,
x25CallParmCug
OCTET STRING,
x25CallParmCugoa
OCTET STRING,
x25CallParmBcug
OCTET STRING,
x25CallParmNui
DisplayString,
x25CallParmChargingInfo
INTEGER,
x25CallParmRpoa
OCTET STRING,
D. Throop [Page 34]
Internet Draft X.25 Packet Layer MIB February 1992
x25CallParmTrnstDly
INTEGER,
x25CallParmCallingExt
OCTET STRING,
x25CallParmCalledExt
OCTET STRING,
x25CallParmInMinThuPutCls
INTEGER,
x25CallParmOutMinThuPutCls
INTEGER,
x25CallParmEndTrnsDly
OCTET STRING,
x25CallParmPriority
OCTET STRING,
x25CallParmProtection
OCTET STRING,
x25CallParmExptData
INTEGER,
x25CallParmUserData
OCTET STRING,
x25CallParmCallingNetworkFacilities
OCTET STRING,
x25CallParmCalledNetworkFacilities
OCTET STRING
}
x25CallParmIndex OBJECT-TYPE
SYNTAX INTEGER (1..2147483647)
ACCESS read-write
STATUS mandatory
DESCRIPTION
"A value that distinguishes this entry from
another entry. Entries in this table are
referenced from other objects.
It is impossible to know what other objects
in the MIB reference entries in the table by
looking at this table. Because of this,
changes to parameters should be accomplished
by creating a new entry in this table and
then changing the referencing table to
identify the new entry.
Entries in this table that are not
referenced by any other object in the MIB
D. Throop [Page 35]
Internet Draft X.25 Packet Layer MIB February 1992
maybe deleted at the convence of the agent.
Care should be taken by the agent to give
the NMS sufficient time to create a
reference to newly created entries.
Entries in this table can be created by
setting a non-existent index instance. The
agent should not allow a set request to
modify an existing entry. This ensures two
agents trying to create new entries will not
over write each other. Two managers will
not be able to create the same entry at the
same time because, one will succeed and the
other will fail. Once an entry has been
created in this table, other objects can be
set to reference them."
::= { x25CallParmEntry 1 }
x25CallParmCallTimer OBJECT-TYPE
SYNTAX INTEGER (0..1800000)
ACCESS read-write
STATUS mandatory
-- The maximum time representable is 30 minutes.
-- See ISO 8208 Section Section 5.2.1, table 26
DESCRIPTION
"The T21 Call timer in milliseconds. A
value of zero means use the PLE default (the
PLE may not reference a zero valued entry)."
REFERENCE "10733 callTime"
::= { x25CallParmEntry 2 }
x25CallParmResetTimer OBJECT-TYPE
SYNTAX INTEGER (0..1800000)
ACCESS read-write
STATUS mandatory
-- See ISO 8208 Section 8.1, table 26
DESCRIPTION
"The T22 Reset timer in milliseconds. A
value of zero means use the PLE default (the
PLE may not reference a zero valued entry)."
REFERENCE "10733 resetTime"
::= { x25CallParmEntry 3 }
x25CallParmClearTimer OBJECT-TYPE
SYNTAX INTEGER (0..1800000)
D. Throop [Page 36]
Internet Draft X.25 Packet Layer MIB February 1992
ACCESS read-write
STATUS mandatory
-- See ISO 8208 Section 5.5.1, table 26
DESCRIPTION
"The T23 Clear timer in milliseconds. A
value of zero means use the PLE default (the
PLE may not reference a zero valued entry)."
REFERENCE "10733 clearTime"
::= { x25CallParmEntry 4 }
x25CallParmInterruptTime OBJECT-TYPE
SYNTAX INTEGER (0..2147483647)
ACCESS read-write
STATUS mandatory
-- See ISO 8208 Section 6.8.1, table 26
DESCRIPTION
"The T26 Interrupt timer milliseconds. A
value of zero means use the PLE default (the
PLE may not reference a zero valued entry).
A value of 2147483647 indicates interrupts
are not being used."
REFERENCE "10733 interruptTime"
::= { x25CallParmEntry 5 }
x25CallParmResetCount OBJECT-TYPE
SYNTAX INTEGER (0..65535)
ACCESS read-write
STATUS mandatory
-- See section ISO 8208 8.1, table 27
DESCRIPTION
"The r22 Reset retransmission count. A
value of zero means use the PLE default (the
PLE may not reference a zero valued entry)."
REFERENCE "10733 resetCount"
::= { x25CallParmEntry 6 }
x25CallParmClearCount OBJECT-TYPE
SYNTAX INTEGER (0..65535)
ACCESS read-write
STATUS mandatory
-- See ISO 8208 Section 5.5.1, table 27
DESCRIPTION
"The r23 Clear retransmission count. A
value of zero means use the PLE default (the
PLE may not reference a zero valued entry)."
D. Throop [Page 37]
Internet Draft X.25 Packet Layer MIB February 1992
REFERENCE "10733 clearCount"
::= { x25CallParmEntry 7 }
x25CallParmWindowTimer OBJECT-TYPE
SYNTAX INTEGER (0..2147483647)
ACCESS read-write
STATUS mandatory
-- See ISO 8208 Section 11.2.2, table 26
DESCRIPTION
"The T24 window status transmission timer
milliseconds. A value of zero means use the
PLE default (the PLE may not reference a
zero valued entry). A value of 2147483647
indicates no window timer in use."
REFERENCE "10733 5.10.1 windowTime (opt)"
::= { x25CallParmEntry 8 }
x25CallParmDataRxmtTimer OBJECT-TYPE
SYNTAX INTEGER (0..2147483647)
ACCESS read-write
STATUS mandatory
-- See ISO 8208 Section 11.2.1, table 26
DESCRIPTION
"The T25 Data Retransmission timer in
milliseconds. A value of zero means use the
PLE default (the PLE may not reference a
zero valued entry). A value of 2147483647
indicates no data retransmission timer in
use."
REFERENCE "10733 5.10.1 dataRetransmissionTime (opt)"
::= { x25CallParmEntry 9 }
x25CallParmDataRxmtCount OBJECT-TYPE
SYNTAX INTEGER (0..65535)
ACCESS read-write
STATUS mandatory
-- See ISO 8208 Section 11.2.1, table 27
DESCRIPTION
"The R25 Data retransmission count. A value
of zero means use the PLE default (the PLE
may not reference a zero valued entry). A
value of 65535 indicates no data
retransmission timer in use."
REFERENCE "10733 5.10.1 dataRetransmissionCount (opt)"
::= { x25CallParmEntry 10 }
D. Throop [Page 38]
Internet Draft X.25 Packet Layer MIB February 1992
x25CallParmRejectTimer OBJECT-TYPE
SYNTAX INTEGER (0..2147483647)
ACCESS read-write
STATUS mandatory
-- See ISO 8208 Section 13.4.1, table 26
DESCRIPTION
"The T27 Reject retransmission timer in
milliseconds. A value of zero means use the
PLE default (the PLE may not reference a
zero valued entry). A value of 2147483647
indicates no reject timer in use."
REFERENCE "10733 5.10.1 dataRejectTime (opt)"
::= { x25CallParmEntry 11 }
x25CallParmRejectCount OBJECT-TYPE
SYNTAX INTEGER (0..65535)
ACCESS read-write
STATUS mandatory
DESCRIPTION
"The R27 reject retransmission count. A
value of zero means use the PLE default (the
PLE may not reference a zero valued entry).
A value of 65535 indicates no reject timer
in use."
REFERENCE "10733 5.10.1 dataRejectCount (opt)"
::= { x25CallParmEntry 12 }
x25CallParmInPacketSize OBJECT-TYPE
SYNTAX INTEGER (0..4096)
ACCESS read-write
STATUS mandatory
-- See ISO 8208 Section 15.2.2.1.1
DESCRIPTION
"The maximum receive packet size in octets
for a connection. A size of zero means use
the default size. The default size for the
PLE default parameter is 128."
REFERENCE "10733 proposedPacketSize"
::= { x25CallParmEntry 13 }
x25CallParmOutPacketSize OBJECT-TYPE
SYNTAX INTEGER (0..4096)
ACCESS read-write
STATUS mandatory
-- See ISO 8208 Section 15.2.2.1.1
D. Throop [Page 39]
Internet Draft X.25 Packet Layer MIB February 1992
DESCRIPTION
"The maximum transmit packet size in octets
for a connection. A size of zero means use
the default size. The default size for the
PLE default parameter is 128."
REFERENCE "10733 proposedPacketSize"
::= { x25CallParmEntry 14 }
x25CallParmInWindowSize OBJECT-TYPE
SYNTAX INTEGER (0..127)
ACCESS read-write
STATUS mandatory
-- See ISO 8208 Section 15.2.2.1.2
DESCRIPTION
"The receive window size for a connection.
A size of zero means use the default size.
The default size for the PLE default
parameter is 2."
REFERENCE "10733 proposedWindowSize"
::= { x25CallParmEntry 15 }
x25CallParmOutWindowSize OBJECT-TYPE
SYNTAX INTEGER (0..127)
ACCESS read-write
STATUS mandatory
-- See ISO 8208 Section 15.2.2.1.2
DESCRIPTION
"The transmit window size for a connection.
A size of zero means use the default size.
The default size for the PLE default
parameter is 2."
REFERENCE "10733 proposedWindowSize"
::= { x25CallParmEntry 16 }
x25CallParmAcceptReverseCharging OBJECT-TYPE
SYNTAX INTEGER {
default(1),
accept(2),
refuse(3)}
ACCESS read-write
STATUS mandatory
DESCRIPTION
"An enumeration defining if the PLE will
accept or refuse charges. When used as the
D. Throop [Page 40]
Internet Draft X.25 Packet Layer MIB February 1992
default parameters for a PLE, the value of
default may not be used."
REFERENCE "10733 acceptReverseCharging"
::= { x25CallParmEntry 17 }
x25CallParmProposeReverseCharging OBJECT-TYPE
SYNTAX INTEGER {
default(1),
reverse(2),
local(3)}
ACCESS read-write
STATUS mandatory
-- See ISO 8208 Section 15.2.2.6
DESCRIPTION
"An enumeration defining if the PLE should
propose reverse or local charging. When
used as the default parameters of a PLE, the
default value may not be used."
REFERENCE "10733 proposedPacketSize"
::= { x25CallParmEntry 18 }
x25CallParmFastSelect OBJECT-TYPE
SYNTAX INTEGER {
default(1),
notSpecified(2),
fastSelect(3),
restrictedFastResponse(4),
noFastSelect(5)}
ACCESS read-write
STATUS mandatory
-- Sec ISO 8208 Section 15.2.2.6
DESCRIPTION
"Expresses preference for use of fast select
facility. When used as the default
parameters for a PLE, the default value may
not be used."
REFERENCE "10733 fastSelect"
::= { x25CallParmEntry 19 }
x25CallParmInThruPutClasSize OBJECT-TYPE
SYNTAX INTEGER {
tcReserved1 (1),
tcReserved2 (2),
tc75 (3),
D. Throop [Page 41]
Internet Draft X.25 Packet Layer MIB February 1992
tc150 (4),
tc300 (5),
tc600 (6),
tc1200 (7),
tc2400 (8),
tc4800 (9),
tc9600 (10),
tc19200 (11),
tc48000 (12),
tc64000 (13),
tcReserved14 (14),
tcReserved15 (15),
tcReserved0 (16),
tcNone (17),
tcDefault (18)
}
ACCESS read-write
STATUS mandatory
-- See ISO 8208 Section 15.2.2.2, table 18
DESCRIPTION
"The incoming throughput class to negotiate.
A value of tcDefault means use the PLE
default, the PLE may not use the tcDefault
value. A value of tcNone means no through
put class requested."
::= { x25CallParmEntry 20 }
x25CallParmOutThruPutClasSize OBJECT-TYPE
SYNTAX INTEGER {
tcReserved1 (1),
tcReserved2 (2),
tc75 (3),
tc150 (4),
tc300 (5),
tc600 (6),
tc1200 (7),
tc2400 (8),
tc4800 (9),
tc9600 (10),
tc19200 (11),
tc48000 (12),
tc64000 (13),
tcReserved14 (14),
tcReserved15 (15),
tcReserved0 (16),
D. Throop [Page 42]
Internet Draft X.25 Packet Layer MIB February 1992
tcNone (17),
tcDefault (18)
}
ACCESS read-write
STATUS mandatory
-- See ISO 8208 Section 15.2.2.2, table 18
DESCRIPTION
"The outgoing throughput class to negotiate.
A value of tcDefault means use the PLE
default, the PLE may not use the tcDefault
value. A value of tcNone means no through
put class requested."
::= { x25CallParmEntry 21 }
x25CallParmCug OBJECT-TYPE
SYNTAX OCTET STRING (SIZE(0..4))
ACCESS read-write
STATUS mandatory
-- See ISO 8208 Section 15.2.2.3
DESCRIPTION
"The Closed User Group to specify. This
consists of 2 or 4 octets containing the
characters 0 through 9. A zero length
string indicates no facility requested. A
string length of three containing the
characters DEF means use the PLE default,
(the PLE may not reference an entry of
DEF.)"
::= { x25CallParmEntry 22 }
x25CallParmCugoa OBJECT-TYPE
SYNTAX OCTET STRING (SIZE(0..4))
ACCESS read-write
STATUS mandatory
-- See ISO 8208 Section 15.2.2.4
DESCRIPTION
"The Closed User Group with Outgoing Access
to specify. This consists of 2 or 4 octets
containing the characters 0 through 9. A
string length of three containing the
characters DEF means use the PLE default
(the PLE may not reference an entry of DEF).
A zero length string indicates no facility
D. Throop [Page 43]
Internet Draft X.25 Packet Layer MIB February 1992
requested."
::= { x25CallParmEntry 23 }
x25CallParmBcug OBJECT-TYPE
SYNTAX OCTET STRING (SIZE(0..3))
ACCESS read-write
STATUS mandatory
-- See ISO 8208 Section 15.2.2.5
DESCRIPTION
"The Bilateral Closed User Group to specify.
This consists of 2 octets containing the
characters 0 through 9. A string length of
three containing the characters DEF means
use the PLE default (the PLE may not
reference an entry of DEF). A zero length
string indicates no facility requested."
::= { x25CallParmEntry 24 }
x25CallParmNui OBJECT-TYPE
SYNTAX DisplayString (SIZE(0..108))
ACCESS read-write
STATUS mandatory
-- See ISO 8208 Section 15.2.2.7
DESCRIPTION
"The Network User Identifier facility. A
zero length string indicates no facility
requested. This value is ignored for the
PLE default parameters entry."
::= { x25CallParmEntry 25 }
x25CallParmChargingInfo OBJECT-TYPE
SYNTAX INTEGER {
default(1),
noFacility(2),
noChargingInfo(3),
chargingInfo(4) }
ACCESS read-write
STATUS mandatory
-- See ISO 8208 Section 15.2.2.8
DESCRIPTION
"The charging Information facility. The
default PLE parameters entry may not use the
default value."
::= { x25CallParmEntry 26 }
D. Throop [Page 44]
Internet Draft X.25 Packet Layer MIB February 1992
x25CallParmRpoa OBJECT-TYPE
SYNTAX OCTET STRING (SIZE(0..108))
ACCESS read-write
STATUS mandatory
-- See ISO 8208, section 15.2.2.9
DESCRIPTION
"The RPOA facility. The octet string
contains n * 4 sequences of the characters
0-9 to specify a facility with n entries.
The octet string containing the 3 characters
DEF specifies use of the PLE default (the
entry for the PLE default may not contain
DEF). A zero length string indicates no
facility requested."
::= { x25CallParmEntry 27 }
x25CallParmTrnstDly OBJECT-TYPE
SYNTAX INTEGER (0..65537)
ACCESS read-write
STATUS mandatory
-- See ISO 8208, Section 15.2.2.13
DESCRIPTION
"The Transit Delay Selection and Indication
value. A value of 65536 indicates no
facility requested. A value of 65537 means
use the PLE default (the PLE default
parameters entry may not use the value
65537). The value 65535 may only be used to
indicate the value in use by a circuit."
::= { x25CallParmEntry 28 }
-- The following parameters are for CCITT facilities.
x25CallParmCallingExt OBJECT-TYPE
SYNTAX OCTET STRING (SIZE(0..43))
ACCESS read-write
STATUS mandatory
-- See ISO 8208 Section 15.3.2.1
DESCRIPTION
"The Calling Extension facility. This
contains one of the following:
The 3 characters PBD followed by up to 40
D. Throop [Page 45]
Internet Draft X.25 Packet Layer MIB February 1992
characters from the set 0-9; the numeric
characters are encoded in the facility using
a Preferred binary encoding of decimal.
The 3 characters PBB followed by up to 40
characters from the set 0-9; the numeric
characters are encoded in the facility using
a Preferred binary encoding of binary.
The 3 characters BCD followed by up to 40
characters from the set 0-9; the characters
are encoded in the facility as binary coded
decimal.
A value containing the three character DEF
means use the PLE default, (the entry for
the PLE default parameters may not use the
value DEF).
A zero length string indicates no facility
requested."
::= { x25CallParmEntry 29 }
x25CallParmCalledExt OBJECT-TYPE
SYNTAX OCTET STRING (SIZE(0..43))
ACCESS read-write
STATUS mandatory
-- See ISO 8208 Section 15.3.2.2
DESCRIPTION
"The Called Extension facility. This
contains one of the following:
The 3 characters PBD followed by up to 40
characters from the set 0-9; the numeric
characters are encoded in the facility using
a Preferred binary encoding of decimal.
The 3 characters PBB followed by up to 40
characters from the set 0-9; the numeric
characters are encoded in the facility using
a Preferred binary encoding of binary.
The 3 characters BCD followed by up to 40
characters from the set 0-9; the characters
are encoded in the facility as binary coded
D. Throop [Page 46]
Internet Draft X.25 Packet Layer MIB February 1992
decimal.
A value containing the three character DEF
means use the PLE default, (the entry for
the PLE default parameters may not use the
value DEF).
A zero length string indicates no facility
requested."
::= { x25CallParmEntry 30 }
x25CallParmInMinThuPutCls OBJECT-TYPE
SYNTAX INTEGER (0..17)
ACCESS read-write
STATUS mandatory
-- See ISO 8208 Section 15.3.2.3
DESCRIPTION
"The minimum input throughput Class. A
value of 16 means use the PLE default (the
PLE parameters entry may not use this
value). A value of 17 indicates no facility
requested."
::= { x25CallParmEntry 31 }
x25CallParmOutMinThuPutCls OBJECT-TYPE
SYNTAX INTEGER (0..17)
ACCESS read-write
STATUS mandatory
-- See ISO 8208 Section 15.3.2.3
DESCRIPTION
"The minimum output throughput Class. A
value of 16 means use the PLE default (the
PLE parameters entry may not use this
value). A value of 17 indicates no facility
requested."
::= { x25CallParmEntry 32 }
x25CallParmEndTrnsDly OBJECT-TYPE
SYNTAX OCTET STRING (SIZE(0..6))
ACCESS read-write
STATUS mandatory
-- See ISO 8208 Section 15.3.2.4
DESCRIPTION
"The End-to-End Transit Delay to negotiate.
An octet string of length 2, 4, or 6
D. Throop [Page 47]
Internet Draft X.25 Packet Layer MIB February 1992
contains the facility encoded as specified
in ISO/IEC 8208 section 15.3.2.4. An octet
string of length 3 containing the three
character DEF means use the PLE default (the
entry for the PLE default can not contain
the characters DEF). A zero length string
indicates no facility requested."
::= { x25CallParmEntry 33 }
x25CallParmPriority OBJECT-TYPE
SYNTAX OCTET STRING (SIZE(0..6))
ACCESS read-write
STATUS mandatory
-- See ISO 8208 Section 15.3.2.5
DESCRIPTION
"The priority facility to negotiate. The
octet string encoded as specified in ISO/IEC
8208 section 15.3.2.5. A zero length string
indicates no facility requested. The entry
for the PLE default parameters must be zero
length."
::= { x25CallParmEntry 34 }
x25CallParmProtection OBJECT-TYPE
SYNTAX OCTET STRING (SIZE(0..108))
ACCESS read-write
STATUS mandatory
-- See ISO 8208 Section 15.3.2.5
DESCRIPTION
"The OCTET STRING contains the following:
The first 3 octets of the string contain the
3 characters SRC, DST, or GBL to represent a
source-address specific, destination-address
specific, or globally unique protection
facility. Following that are a string of
the characters 0-9 containing the protection
level.
This may optionally be followed by the 3
characters MIN and another string of the
characters 0-9 contining the lowest
acceptable level.
D. Throop [Page 48]
Internet Draft X.25 Packet Layer MIB February 1992
An octet string containing the 3 characters
DEF means use the PLE default (the entry for
the PLE default parameters may not use the
value DEF).
A zero length string mean no facility
requested."
::= { x25CallParmEntry 35 }
x25CallParmExptData OBJECT-TYPE
SYNTAX INTEGER {
default(1),
noExpeditedData(2),
expeditedData(3) }
ACCESS read-write
STATUS mandatory
DESCRIPTION
"The Expedited Data facility to negotiate.
The entry for the PLE default parameters may
not have the value default."
::= { x25CallParmEntry 36 }
x25CallParmUserData OBJECT-TYPE
SYNTAX OCTET STRING (SIZE (0..128))
ACCESS read-write
STATUS mandatory
-- See ISO 8208 Section 12.2.1.1.6, 12.2.1.2
DESCRIPTION
"The call user data. A zero length string
indicates no call user data. The entry for
the PLE default parameters must be zero
length."
::= { x25CallParmEntry 37 }
x25CallParmCallingNetworkFacilities OBJECT-TYPE
SYNTAX OCTET STRING (SIZE (0..108))
ACCESS read-write
STATUS mandatory
-- See ISO 8206 Section 15.1, category b
DESCRIPTION
"The calling network facilities. The
facilities are encoded here exactly as
encoded in the call packet. These
D. Throop [Page 49]
Internet Draft X.25 Packet Layer MIB February 1992
facilities do not include the marker
facility code.
A zero length string in the entry for the
parameter to use when establishing a circuit
means use the PLE default. A zero length
string in the entry for PLE default
parameters indicates no default facilities."
::= { x25CallParmEntry 38 }
x25CallParmCalledNetworkFacilities OBJECT-TYPE
SYNTAX OCTET STRING (SIZE (0..108))
ACCESS read-write
STATUS mandatory
-- See ISO 8206 Section 15.1, category c
DESCRIPTION
"The called network facilities. The
facilities are encoded here exactly as
encoded in the call packet. These
facilities do not include the marker
facility code.
A zero length string in the entry for the
parameter to use when establishing a circuit
means use the PLE default. A zero length
string in the entry for PLE default
parameters indicates no default facilities."
::= { x25CallParmEntry 39 }
-- X.25 Protocol Version Identifiers
x25ProtocolVersion OBJECT IDENTIFIER
::= { x25 6 }
-- X.25 CCITT 1976 version.
x25protocolCcittV1976 OBJECT IDENTIFIER
::= { x25ProtocolVersion 1 }
-- X.25 CCITT 1980 version.
x25protocolCcittV1980 OBJECT IDENTIFIER
::= { x25ProtocolVersion 2 }
-- X.25 CCITT 1984 version.
D. Throop [Page 50]
Internet Draft X.25 Packet Layer MIB February 1992
x25protocolCcittV1984 OBJECT IDENTIFIER
::= { x25ProtocolVersion 3 }
-- X.25 CCITT 1988 version.
x25protocolCcittV1988 OBJECT IDENTIFIER
::= { x25ProtocolVersion 4 }
-- X.25 1987 version of ISO 8208.
x25protocolIso8208V1987 OBJECT IDENTIFIER
::= { x25ProtocolVersion 5 }
-- X.25 1989 version of ISO 8208.
x25protocolIso8208V1989 OBJECT IDENTIFIER
::= { x25ProtocolVersion 6 }
-- ###########################################################
END
D. Throop [Page 51]
Internet Draft X.25 Packet Layer MIB February 1992
7. Acknowledgements
This document was produced by the x25mib working group:
Fred Baker, ACC
Art Berggreen, ACC
Frank Bieser
Charles Carvalho, ACC
Angela Chen, HP
Tom Daniel, Spider Systems
Chuck Davin, MIT
Doug Geller, Data General
Herve Goguely, LIR Corp
Andy Goldthorpe, british-telecom
David Gurevich,
Richard Fox, Synoptics
Steve Huston, Process Software Corporation
Frank Kastenholz, Clearpoint
Zbigniew Kiel
Cheryl Krupezak, Georgia Tech
Mats Lindstrom, Diab Data AB
Andrew Malis, BBN
Evan McGinnis, 3Com
Gary (G.P.)Mussar, BNR
Karen Quidley, Data General
Randy Pafford, Data General
Ragnar Paulson, The Software Group Limited
Dave Perkins, Synoptics
Walter Pinkarschewsky, DEC
Paul S. Rarey, DHL Systems Inc.
Jim Roche, Newbridge Research
Philippe Roger, LIR Corp.
Mike Shand, DEC
Bob Stewart, Xyplex
Tom Sullivan, Data General
Rodney Thayer, Sable Technology Corporation
Mark Therieau, Microcom
Jane Thorn, Data General
Dean Throop, Data General
Mike Zendels, Data General
In addition, the contributions of the following individuals
are also acknowledged:
John Harper, DEC
D. Throop [Page 52]
Internet Draft X.25 Packet Layer MIB February 1992
Chairman of the ISO committee for
Network Level Management Information
D. Throop [Page 53]
Internet Draft X.25 Packet Layer MIB February 1992
8. References
[1] M.T. Rose and K. McCloghrie, "Structure and
Identification of Management Information for TCP/IP-based
internets", RFC 1155, Network Information Center, SRI
International, Menlo Park, California, (May, 1990).
[2] K. McCloghrie and M.T. Rose, "Management Information Base
for Network Management of TCP/IP-based internets", RFC
1156, Network Information Center, SRI International,
Menlo Park, California, (May, 1990).
[3] J.D. Case, M.S. Fedor, M.L. Schoffstall, and J.R. Davin,
"Simple Network Management Protocol", RFC 1157, Network
Information Center, SRI International, Menlo Park,
California, (May, 1990).
[4] M.T. Rose, K. McCloghrie (editors), "Towards Concise MIB
Definitions", RFC 1212, Network Information Center, SRI
International, Menlo Park, California, (March, 1991)
[5] M.T. Rose (editor), "Management Information Base for
Network Management of TCP/IP-based internets", RFC 1213.
Network Information Center, SRI International, Menlo
Park, California, (March, 1991).
[6] "Information processing systems - Open Systems
Interconnection - Specification of Abstract Syntax
Notation One (ASN.1)", International Organization for
Standardization. International Standard 8824, (December,
1987).
[7] "Information processing systems - Open Systems
Interconnection - Specification of Basic Encoding Rules
for Abstract Notation One (ASN.1)", International
Organization for Standardization. International Standard
8825, (December, 1987).
[8] B. Stewart (editor), "Definitions of Managed Objects for
RS-232-like Hardware Devices", Internet Draft, Internet
Engineering Task Force, (December, 1990)
[9] D. Throop (editor), "SNMP MIB extension for LAPB",
Internet Draft, Internet Engineering Task Force,
(February, 1992)
D. Throop [Page 54]
Internet Draft X.25 Packet Layer MIB February 1992
[10] "Information technology - - Data communication - X.25
Packet layer Protocol for Data Terminal Equipment",
International Organization for Standardization,
International Standard 8208 (March, 1990)
[11] "Information Technology - Telecommunications and
information exchange between systems - Elements of
Management Information Related to OSI network Layer
Standards", Committee Draft International Standard 10733,
(November, 1990)
D. Throop [Page 55]
Internet Draft X.25 Packet Layer MIB February 1992
Table of Contents
1 Status of this Memo ................................... 1
1.1 Revision History .................................... 1
February 1992 .......................................... 1
October 1992 ........................................... 2
June 1991 .............................................. 3
April 1991 ............................................. 3
2 Abstract .............................................. 3
3 The Network Management Framework ...................... 3
4 Objects ............................................... 4
4.1 Format of Definitions ............................... 4
5 Overview .............................................. 5
5.1 Informal Overview ................................... 5
5.2 Textual Conventions ................................. 6
5.3 Structure of MIB .................................... 6
6 Object Definitions .................................... 8
7 Acknowledgements ...................................... 52
8 References ............................................ 54
D. Throop [Page 56]
Dean Throop throop@dg-rtp.dg.com
- X25 MIB part 2 Dean D. Throop