INTERNET-DRAFT EXPIRATION DATE: DECEMBER 13 1996
Management Information Base for Frame Relay DTE Extensions for SVC's and
Data Compression over Frame Relay
draft-cochrane-frmib-dte-00.txt
Don Cochrane
Cabletron Sys, Inc.
35E Industrial Way, 1st Floor
Rochester New Hampshire, 03867
cochrane@ctron.com
Moji kashef
Cabletron Sys, Inc.
35E Industrial Way, 1st Floor
Rochester New Hampshire, 03867
kashef@ctron.com
1. Status of this Memo
This document is an Internet-Draft. Internet-Drafts are
working documents of the Internet Engineering Task Force
(IETF), its areas, and its working groups. Note that other
groups may also distribute working documents as Internet-
Drafts.
Internet-Drafts are draft documents valid for a maximum of six
months. Internet-Drafts may be updated, replaced, or
obsoleted by other documents at any time. It is not
appropriate to use Internet-Drafts as reference material or to
cite them other than as a ``working draft'' or ``work in
progress.''
To learn the current status of any Internet-Draft, please
check the 1id-abstracts.txt listing contained in the
Internet-Drafts Shadow Directories on ds.internic.net,
nic.nordu.net, ftp.nisc.sri.com, or munnari.oz.au.
This draft document will be submitted to the RFC editor as an
extension to the SNMP MIB. Please send comments to the
authors, copying iplpdn@cnri.reston.va.us. It expires Dec
1996.
Draft Frame Relay DTE Extensions MIB June 1996
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 Frame Relay Switched Virtual Circuit's and Data
Compression over a Frame Relay virtual circuit.
This memo does not specify a standard for the Internet
community.
3. The SNMPv2 Network Management Framework
The major components of the SNMPv2 Network Management
framework are described in the documents listed below.
o RFC 1902 [1] defines the Structure of Management
Information (SMI), the mechanisms used for describing and
naming objects for the purpose of management.
o STD 17, RFC 1213 [2] defines MIB-II, the core set of
managed objects (MO) for the Internet suite of protocols.
o RFC 1905 [3] defines the protocol used for network access
to managed objects.
o RFC 1315 [4] defines the protocol used for managing
Frame Relay DTE's.
The framework is adaptable/extensible by defining new MIBs to
suit the requirements of specific
applications/protocols/situations.
Managed objects are accessed via a virtual information store,
the MIB. Objects in the MIB are defined using the
subset of Abstract Syntax Notation One (ASN.1) defined in the
SMI. In particular, each object type is named by an OBJECT
IDENTIFIER, which is an administratively assigned name. The
object type together with an object instance serves to
uniquely identify a specific instantiation of the object.
For human convenience, often a textual string, termed the
descriptor, is used to refer to the object type.
Cochrane & Kashef [Page 2]
Draft Frame Relay DTE Extensions MIB June 1996
4. Overview
4.1. Frame Relay Extensions for SVC's and Data Compression
This MIB addresses the instances needed to be able to manage both the
Frame Relay Forum's Implementation agreements for SVC's (FRF.4)
and Data Compression (FRF.9).
5. Definitions
FRAME-RELAY-DTE-MIB DEFINITIONS ::= BEGIN
IMPORTS
MODULE-IDENTITY, OBJECT-TYPE, Counter32,
Integer32, NOTIFICATION-TYPE FROM SNMPv2-SMI
TEXTUAL-CONVENTION, RowStatus, TimeStamp FROM SNMPv2-TC
MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF
transmission FROM RFC1213-MIB
InterfaceIndex FROM IF-MIB;
Cochrane & Kashef [Page 3]
Draft Frame Relay DTE Extensions MIB June 1996
-- 5.1 Switched Virtual Circuit Link Connection Management Interface Table
frSvcDlcmiTable OBJECT-TYPE
SYNTAX SEQUENCE OF frSvcDlcmiEntry
ACCESS not-accessible
STATUS current
DESCRIPTION
"The Parameters for the Switched Virtual Circuit
Link Connection Management Interface
for the frame relay service on this
interface."
::= { frame-relay 7 }
frSvcDlcmiEntry OBJECT-TYPE
SYNTAX FrSvcDlcmiEntry
ACCESS not-accessible
STATUS current
DESCRIPTION
"The information regarding a single switched Data
Link Connection Management Interface."
INDEX { frSvcDlcmiIfIndex }
::= { frSvcDlcmiTable 1 }
FrSvcDlcmiEntry ::=
SEQUENCE {
--
-- Standard Interface Index parameter
--
frSvcDlcmiIfIndex
Index,
frSvcDlcmiState
INTEGER,
--
-- Q.933 Parameters
--
frSvcDlcmiMaxNumCalls
INTEGER,
frSvcDlcmiCallSetupTimer
INTEGER,
frSvcDlcmiCallProceedingTimer
INTEGER,
frSvcDlcmiCallDisconnectTimer
INTEGER,
frSvcDlcmiCallReleaseTimer
INTEGER,
frSvcDlcmiStatusEnquiryTimer
INTEGER,
frSvcDlcmiErrorThreshold
INTEGER,
Cochrane & Kashef [Page 4]
Draft Frame Relay DTE Extensions MIB June 1996
--
-- Q.922 Parameters
--
frSvcDlcmiQ922Enable
INTEGER,
frSvcDlcmiIdleTimer
INTEGER,
frSvcDlcmiRetransmissionTimer
TimeTicks,
frSvcDlcmiNumberOfRetransmissions
INTEGER,
frSvcDlcmiMaxInformationFieldSize
INTEGER,
frSvcDlcmiMaxOutstandingIFrames
INTEGER
}
frSvcDlcmiIfIndex OBJECT-TYPE
SYNTAX Index
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The ifIndex value of the corresponding ifEntry."
::= { frSvcDlcmiEntry 1 }
frSvcDlcmiStateOBJECT-TYPE
SYNTAX INTEGER {
Q.933 SVC(1) -- Std SVC implementation
}
ACCESS read-create
STATUS current
DESCRIPTION
"This variable states which Data Link Connection
Management scheme is on the Frame Relay
switched interface."
::= { frSvcDlcmiEntry 2 }
frSvcDlcmiMaxNumCalls OBJECT-TYPE
SYNTAX INTEGER
ACCESS read-only
STATUS current
DESCRIPTION
"Indicates the maximum number of calls
allowed on the interface."
::= { frSvcDlcmiEntry 3 }
Cochrane & Kashef [Page 5]
Draft Frame Relay DTE Extensions MIB June 1996
frSvcDlcmiCallSetupTimer OBJECT-TYPE
SYNTAX INTEGER
ACCESS read-write
STATUS current
DESCRIPTION
"This timer is started when the CALL SETUP
message is sent. The timer is stopped when
the sender receives a CALL PROCEEDING
message. If the timer, expressed in
seconds, expires, it is retried
once before the call is cleared."
REFERENCE
"ITU-T Standard Q.931,
Section 9.2: Timer T303."
DEFVAL {4}
::= { frSvcDlcmiEntry 4 }
frSvcDlcmiCallProceedingTimer OBJECT-TYPE
SYNTAX INTEGER
ACCESS read-write
STATUS current
DESCRIPTION
"This timer is started when the CALL
PROCEEDING message is sent. The timer
is stopped when the sender
receives a CALL CONNECT message. If
the timer, expressed in seconds,
expires, the call is cleared."
REFERENCE
"ITU-T Standard Q.931,
Section 9.2: Timer T310."
DEFVAL {10}
::= { frSvcDlcmiEntry 5 }
Cochrane & Kashef [Page 6]
Draft Frame Relay DTE Extensions MIB June 1996
frSvcDlcmiCallDisconnectTimer OBJECT-TYPE
SYNTAX INTEGER
ACCESS read-write
STATUS current
DESCRIPTION
"This timer is started when the
DISCONNECT message is sent. The timer
is stopped when the sender
receives a RELEASE message. The sender
then responds with a RELEASE COMPLETE
message. If the timer, expressed in
seconds, expires, the sender starts
up Timer T308, and sends a RELEASE
message."
REFERENCE
"ITU-T Standard Q.931,
Section 9.2: Timer T305."
DEFVAL {30}
::= { frSvcDlcmiEntry 6 }
frSvcDlcmiCallReleaseTimer OBJECT-TYPE
SYNTAX INTEGER
ACCESS read-write
STATUS current
DESCRIPTION
"This timer is started if timer
T305 expires. This timer
is stopped when the sender
receives a RELEASE message. If
the timer, expressed in seconds,
expires, the timer sequence is
reinitiated. If the timer
expires a second time the call is
cleared."
REFERENCE
"ITU-T Standard Q.931,
Section 9.2: Timer T308."
DEFVAL {4}
::= { frSvcDlcmiEntry 7 }
Cochrane & Kashef [Page 7]
Draft Frame Relay DTE Extensions MIB June 1996
frSvcDlcmiStatusEnquiryTimer OBJECT-TYPE
SYNTAX INTEGER
ACCESS read-write
STATUS current
DESCRIPTION
"This timer is started when a STATUS
ENQUIRY message is sent. If a STATUS
message is received, the timer will be
stopped. If the Timer expires it may be
retried an implementation specific number
(n) of times. Upon expiry of (n), the
call is cleared."
REFERENCE
"ITU-T Standard Q.931,
Section 9.2: Timer T322."
DEFVAL {4}
::= { frSvcDlcmiEntry 8 }
frSvcDlcmiErrorThreshold OBJECT-TYPE
SYNTAX INTEGER
ACCESS read-write
STATUS current
DESCRIPTION
"This is the implementation specific
number of times that the STATUS
ENQUIRY Timer, T322, will be retried.
REFERENCE
"ITU-T Standard Q.931, Section 9.2."
::= { frSvcDlcmiEntry 9 }
frSvcDlcmiQ922Enable OBJECT-TYPE
SYNTAX INTEGER {
Q.922 disabled(0)
Q.922 enabled(1)
}
ACCESS read-write
STATUS current
DESCRIPTION
"This turns the protocol stack on or off."
::= { frSvcDlcmiEntry 10 }
frSvcDlcmiIdleTimer OBJECT-TYPE
SYNTAX INTEGER
ACCESS read-write
STATUS current
DESCRIPTION
"This is the maximum time allowed
without any frames being exchanged."
REFERENCE
"ITU-T Standard Q.921,
Section 5.9 / Q.922 Section
5.9: Timer T203."
DEFVAL {30}
::= { frSvcDlcmiEntry 11 }
Cochrane & Kashef [Page 8]
Draft Frame Relay DTE Extensions MIB June 1996
frSvcDlcmiRetransmissionTimer OBJECT-TYPE
SYNTAX TimeTicks
ACCESS read-write
STATUS current
DESCRIPTION
"This is the re-transmission timer.
It is started upon transmission of
frames. When a response is received,
the timer will be shut down. If the
timer expires (1.5 seconds), it may
be retried N200 times. When N200
times have been reached, a
DL-RELEASE message will be sent to
the Layer 3 entity."
REFERENCE
"ITU-T Standard Q.921,
Section 5.9 / Q.922 Section
5.9: Timer T200."
DEFVAL {1500}
::= { frSvcDlcmiEntry 12 }
frSvcDlcmiNumberOfRetransmissions OBJECT-TYPE
SYNTAX INTEGER
ACCESS read-write
STATUS current
DESCRIPTION
"This value indicates the number of
times T200 timer will be retried.
When N200 times have been reached,
a DL-RELEASE message will be sent
to the Layer 3 entity."
REFERENCE
"ITU-T Standard Q.921,
Section 5.9 / Q.922 Section
5.9: N200."
DEFVAL {3}
::= { frSvcDlcmiEntry 13 }
frSvcDlcmiInformationFieldSize OBJECT-TYPE
SYNTAX INTEGER
ACCESS read-write
STATUS current
DESCRIPTION
"This value indicates the maximum
number of octets in an information field."
REFERENCE
"ITU-T Standard Q.921,
Section 5.9 / Q.922 Section
5.9: N201."
DEFVAL {260}
::= { frSvcDlcmiEntry 14 }
Cochrane & Kashef [Page 9]
Draft Frame Relay DTE Extensions MIB June 1996
frSvcDlcmiMaxOutstandingIFrames OBJECT-TYPE
SYNTAX INTEGER (1 .. 127)
ACCESS read-write
STATUS current
DESCRIPTION
"This value indicates the maximum
number of sequentially numbered I
frames that may be outstanding
(that is, unacknowledged) at any
given time. This number shall not
exceed 127. For a 16Kbps link: k =
3, 64Kbps: k = 7, 384Kbps: k = 32,
1.5Mbps/1.92Mbps: k = 40."
REFERENCE
"ITU-T Standard Q.921,
Section 5.9 / Q.922 Section
5.9: k."
DEFVAL {7}
::= { frSvcDlcmiEntry 15 }
-- 5.2 Switched Virtual Circuit Table
-- The table describing the use of the DLCIs attached to
-- each Switched Frame Relay Interface.
frSvcTable OBJECT-TYPE
SYNTAX SEQUENCE OF FrCircuitEntry
ACCESS not-accessible
STATUS current
DESCRIPTION
"A table containing information about specific Data
Link Connection Identifiers and corresponding switched
virtual circuits."
::= { frame-relay 8 }
frSvcEntry OBJECT-TYPE
SYNTAX FrSvcEntry
ACCESS not-accessible
STATUS current
DESCRIPTION
"The information regarding a single switched Data
Link Connection Identifier."
INDEX { frSvcIfIndex, frSvcDlci }
::= { frSvcTable 1 }
Cochrane & Kashef [Page 10]
Draft Frame Relay DTE Extensions MIB June 1996
FrSvcEntry ::=
SEQUENCE {
--
-- Standard Circuit parameters
--
frSvcIfIndex
Index,
frSvcDlci
DLCI,
frSvcReceivedFECNs
Counter,
frSvcReceivedBECNs
Counter,
frSvcSentFrames
Counter,
frSvcSentOctets
Counter,
frSvcReceivedFrames
Counter,
frSvcReceivedOctets
Counter,
frSvcCreationTime
TimeTicks,
--
-- Link Layer Core Parameters
--
frSvcIncomingFmifSize
INTEGER,
frSvcOutgoingFmifSize
INTEGER,
frSvcIncomingCommittedBurst
INTEGER,
frSvcOutgoingCommittedBurst
INTEGER,
frSvcIncomingExcessBurst
INTEGER,
frSvcOutgoingExcessBurst
INTEGER,
frSvcIncomingThroughput
INTEGER,
Cochrane & Kashef [Page 11]
Draft Frame Relay DTE Extensions MIB June 1996
frSvcOutgoingThroughput
INTEGER,
frSvcIncomingMinThroughput
INTEGER,
frSvcOutgoingMinThroughput
INTEGER,
--
-- Q.933 Parameters
--
frSvcState
INTEGER,
frSvcCallReferenceValue
INTEGER,
frSvcCallingAddress
INTEGER,
frSvcCallingSubAddress
INTEGER,
frSvcCalledAddress
INTEGER,
frSvcCalledSubAddress
INTEGER,
frSvcConnectedAddress
INTEGER,
frSvcConnectedSubAddress
INTEGER,
frSvcCallSetup
INTEGER,
frSvcCallOrigination
INTEGER
}
frSvcIfIndex OBJECT-TYPE
SYNTAX Index
ACCESS read-only
STATUS current
DESCRIPTION
"The ifIndex Value of the ifEntry this virtual
circuit is layered onto."
::= { frSvcEntry 1 }
frSvcDlci OBJECT-TYPE
SYNTAX DLCI
ACCESS read-only
STATUS current
DESCRIPTION
"The Data Link Connection Identifier for this
virtual circuit."
::= { frSvcEntry 2 }
Cochrane & Kashef [Page 12]
Draft Frame Relay DTE Extensions MIB June 1996
frSvcReceivedFECNs OBJECT-TYPE
SYNTAX Counter
ACCESS read-only
STATUS current
DESCRIPTION
"Number of frames received from the network in-
dicating forward congestion since the virtual
circuit was created."
REFERENCE
"Draft American National Standard T1.618-1991,
Section 3.3.3"
::= { frSvcEntry 3 }
frSvcReceivedBECNs OBJECT-TYPE
SYNTAX Counter
ACCESS read-only
STATUS current
DESCRIPTION
"Number of frames received from the network in-
dicating backward congestion since the virtual
circuit was created."
REFERENCE
"Draft American National Standard T1.618-1991,
Section 3.3.4"
::= { frSvcEntry 4 }
frSvcSentFrames OBJECT-TYPE
SYNTAX Counter
ACCESS read-only
STATUS current
DESCRIPTION
"The number of frames sent from this virtual
circuit since it was created."
::= { frSvcEntry 5 }
frSvcSentOctets OBJECT-TYPE
SYNTAX Counter
ACCESS read-only
STATUS current
DESCRIPTION
"The number of octets sent from this virtual
circuit since it was created."
::= { frSvcEntry 6 }
Cochrane & Kashef [Page 13]
Draft Frame Relay DTE Extensions MIB June 1996
frSvcReceivedFrames OBJECT-TYPE
SYNTAX Counter
ACCESS read-only
STATUS current
DESCRIPTION
"Number of frames received over this virtual
circuit since it was created."
::= { frSvcEntry 7 }
frSvcReceivedOctets OBJECT-TYPE
SYNTAX Counter
ACCESS read-only
STATUS current
DESCRIPTION
"Number of octets received over this virtual
circuit since it was created."
::= { frSvcEntry 8 }
frSvcCreationTime OBJECT-TYPE
SYNTAX TimeTicks
ACCESS read-only
STATUS current
DESCRIPTION
"The value of sysUpTime when the virtual cir-
cuit was created.
::= { frSvcEntry 9 }
frSvcIncomingMaxFmifSize OBJECT-TYPE
SYNTAX INTEGER
ACCESS read-write
STATUS current
DESCRIPTION
"This variable indicates the maximum amount of
end user data octets in a frame for in the calling
user to the called user direction."
REFERENCE
"ITU-T Standard Q.933,
Section 4.5.19"
DEFVAL { 262 }
::= { frSvcEntry 10 }
Cochrane & Kashef [Page 14]
Draft Frame Relay DTE Extensions MIB June 1996
frSvcOutgoingMaxFmifSize OBJECT-TYPE
SYNTAX INTEGER
ACCESS read-write
STATUS current
DESCRIPTION
"This variable indicates the maximum amount of
end user data octets in a frame for in the called
user to the calling user direction."
REFERENCE
"ITU-T Standard Q.933,
Section 4.5.19"
DEFVAL { 262 }
::= { frSvcEntry 11 }
frSvcIncomingCommittedBurst OBJECT-TYPE
SYNTAX INTEGER
ACCESS read-write
STATUS current
DESCRIPTION
"This variable indicates the maximum amount of
data, in bits, that the network agrees to
accept under normal conditions, during the
measurement interval."
REFERENCE
"ITU-T Standard Q.933,
Section 4.5.19"
DEFVAL { 0 } -- the default indicates no commitment
::= { frSvcEntry 12 }
frSvcOutgoingCommittedBurst OBJECT-TYPE
SYNTAX INTEGER
ACCESS read-write
STATUS current
DESCRIPTION
"This variable indicates the maximum amount of
data, in bits, that the network agrees to
transfer under normal conditions, during the
measurement interval."
REFERENCE
"ITU-T Standard Q.933,
Section 4.5.19"
DEFVAL { 0 } -- the default indicates no commitment
::= { frSvcEntry 13 }
Cochrane & Kashef [Page 15]
Draft Frame Relay DTE Extensions MIB June 1996
frSvcIncomingExcessBurst OBJECT-TYPE
SYNTAX INTEGER
ACCESS read-write
STATUS current
DESCRIPTION
"This variable indicates the maximum amount of
uncommitted data bits that the network will at-
tempt to receive over the measurement interval.
By default, if not configured when creating the
entry, the Excess Information Burst Size is set
to the value of ifSpeed."
REFERENCE
"ITU-T Standard Q.933,
Section 4.5.19"
::= { frSvcEntry 14 }
frSvcOutgoingExcessBurst OBJECT-TYPE
SYNTAX INTEGER
ACCESS read-write
STATUS current
DESCRIPTION
"This variable indicates the maximum amount of
uncommitted data bits that the network will at-
tempt to deliver over the measurement interval.
By default, if not configured when creating the
entry, the Excess Information Burst Size is set
to the value of ifSpeed."
REFERENCE
"ITU-T Standard Q.933,
Section 4.5.19"
::= { frSvcEntry 15 }
frSvcIncomingThroughput OBJECT-TYPE
SYNTAX INTEGER
ACCESS read-write
STATUS current
DESCRIPTION
"Throughput is the average number of 'Frame Re-
lay Information Field' bits received per
second across a user network interface to the
calling user, measured over the measurement inter-
val.
REFERENCE
"ITU-T Standard Q.933,
Section 4.5.19"
DEFVAL {0} -- the default value of Throughput is
-- "no commitment".
::= { frSvcEntry 16 }
Cochrane & Kashef [Page 16]
Draft Frame Relay DTE Extensions MIB June 1996
frSvcOutgoingThroughput OBJECT-TYPE
SYNTAX INTEGER
ACCESS read-write
STATUS current
DESCRIPTION
"Throughput is the average number of 'Frame Re-
lay Information Field' bits transferred per
second across a user network interface from the
calling user, measured over the measurement inter-
val.
REFERENCE
"ITU-T Standard Q.933,
Section 4.5.19"
DEFVAL {0} -- the default value of Throughput is
-- "no commitment".
::= { frSvcEntry 17 }
frSvcIncomingMinThroughput OBJECT-TYPE
SYNTAX INTEGER
ACCESS read-write
STATUS current
DESCRIPTION
"Minimum Acceptable Throughput is the lowest
throughput value, in the direction to the
calling user, expressed in bits per second,
that the calling user is willing to accept for
the call. If the network or the called user is
unable to support this throughput, the call
will be cleared."
REFERENCE
"ITU-T Standard Q.933,
Section 4.5.19"
DEFVAL {0} -- the default value of Throughput is
-- "no commitment".
::= { frSvcEntry 18 }
Cochrane & Kashef [Page 17]
Draft Frame Relay DTE Extensions MIB June 1996
frSvcOutgoingMinThroughput OBJECT-TYPE
SYNTAX INTEGER
ACCESS read-write
STATUS current
DESCRIPTION
"Minimum Acceptable Throughput is the lowest
throughput value, in the direction from the
calling user, expressed in bits per second,
that the calling user is willing to accept for
the call. If the network or the called user is
unable to support this throughput, the call
will be cleared."
REFERENCE
"ITU-T Standard Q.933,
Section 4.5.19"
::= { frSvcEntry 19 }
frSvcState OBJECT-TYPE
SYNTAX INTEGER{
inProcess(0)
complete(1),
}
ACCESS read-only
STATUS current
DESCRIPTION
"Indicates whether the Connection has
been completed and data can proceed (1),
or if the call setup is still in process (0)."
::= { frSvcEntry 20 }
frSvcCallReferenceValue OBJECT-TYPE
SYNTAX INTEGER
ACCESS read-only
STATUS current
DESCRIPTION
"Indicates the call identity number of the call
on the interface."
REFERENCE
"ITU-T Standard Q.931,
Section 4.5.6"
::= { frSvcEntry 21 }
Cochrane & Kashef [Page 18]
Draft Frame Relay DTE Extensions MIB June 1996
frSvcCallingAddress OBJECT-TYPE
SYNTAX INTEGER
ACCESS read-write
STATUS current
DESCRIPTION
"Indicates the address of the calling
party."
REFERENCE
"ITU-T Standard Q.931,
Section 4.5.9"
::= { frSvcEntry 22 }
frSvcCallingSubAddress OBJECT-TYPE
SYNTAX INTEGER
ACCESS read-write
STATUS current
DESCRIPTION
"Indicates the sub-address of the
calling party."
REFERENCE
"ITU-T Standard Q.931,
Section 4.5.10"
::= { frSvcEntry 23 }
frSvcCalledAddress OBJECT-TYPE
SYNTAX INTEGER
ACCESS read-write
STATUS current
DESCRIPTION
"Indicates the address of the called
party."
REFERENCE
"ITU-T Standard Q.931,
Section 4.5.7"
::= { frSvcEntry 24 }
frSvcCalledSubAddress OBJECT-TYPE
SYNTAX INTEGER
ACCESS read-write
STATUS current
DESCRIPTION
"Indicates the sub-address of the
called party."
REFERENCE
"ITU-T Standard Q.931,
Section 4.5.8"
::= { frSvcEntry 25 }
Cochrane & Kashef [Page 19]
Draft Frame Relay DTE Extensions MIB June 1996
frSvcCallSetup OBJECT-TYPE
SYNTAX INTEGER{
setup(1),
disconnect(2) }
ACCESS read-write
STATUS current
DESCRIPTION
"Indicates whether the call should
be Setup or Disconnected."
::= { frSvcEntry 26 }
frSvcCallOrigination OBJECT-TYPE
SYNTAX INTEGER{
remote(0),
local(1)
}
ACCESS read-only
STATUS current
DESCRIPTION
"Indicates the direction of the call.
identifies the circuit as the calling
(local) or the called side (remote)."
REFERENCE
"ITU-T Standard Q.931,
Section 4.5.9"
::= { frSvcEntry 27 }
-- 5.3 Extensions For Data Compression over Frame Relay Table
frDcpTable OBJECT-TYPE
SYNTAX SEQUENCE OF FrDcpEntry
ACCESS not-accessible
STATUS current
DESCRIPTION
"A table containing information about specific Data
Link Connection Identifiers and corresponding
virtual circuits in reference to Data Compression
over Frame Relay. "
::= { frame-relay 9 }
Cochrane & Kashef [Page 20]
Draft Frame Relay DTE Extensions MIB June 1996
frDcpEntry OBJECT-TYPE
SYNTAX FrDcpEntry
ACCESS not-accessible
STATUS current
DESCRIPTION
"The information regarding a single switched Data
Link Connection Identifier."
INDEX { frDcpIfIndex, frDcpDlci }
::= { frDcpTable 1 }
FrDcpEntry ::=
SEQUENCE {
--
-- Data Compression Circuit parameters
--
frDcpIfIndex
Index,
frDcpDlci
DLCI,
frDcpEnable
INTEGER,
frDcpStatus
INTEGER,
frDcpRatio
OCTET STRING
}
frDcpIfIndex OBJECT-TYPE
SYNTAX Index
ACCESS read-only
STATUS current
DESCRIPTION
"The ifIndex Value of the ifEntry this virtual
circuit is layered onto."
::= { frDcpEntry 1 }
Cochrane & Kashef [Page 21]
Draft Frame Relay DTE Extensions MIB June 1996
frDcpDlci OBJECT-TYPE
SYNTAX DLCI
ACCESS read-only
STATUS current
DESCRIPTION
"The Data Link Connection Identifier for this
virtual circuit."
::= { frDcpEntry 2 }
frDcpEnable OBJECT-TYPE
SYNTAX INTEGER {
on (1),
off (2) -- default
}
ACCESS read-write
STATUS mandatory
DESCRIPTION
"Indicates whether data compression should take place on
this particular end side virtual circuit.
::= { frDcpEntry 3 }
frDcpStatus OBJECT-TYPE
SYNTAX INTEGER {
on (1),
off (2)
}
ACCESS read-only
STATUS mandatory
DESCRIPTION
"On indicates that the compression has been successfully
negotiated and is operating. Off indicates that the
compression negotiation has failed and compression is not
operating at this time, or compression has been terminated
by either peer."
::= { frDcpEntry 4 }
frDcpRatio OBJECT-TYPE
SYNTAX OCTET STRING (SIZE (5))
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The ratio of uncompressed to compressed transmitted data. If
data compression status is off, 1:1 will be displayed"
::= { frDcpEntry 5 }
Cochrane & Kashef [Page 22]
Draft Frame Relay DTE Extensions MIB June 1996
6. Acknowledgements
Special thanks to James Watt of Newbridge Networks for his
fine suggestions.
7. References
[1] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M.,
and S. Waldbusser, "Structure of Management Information
for Version 2 of the Simple Network Management Protocol
(SNMPv2)", RFC 1902, January 1996.
[2] McCloghrie, K., and M. Rose, Editors, "Management
Information Base for Network Management of TCP/IP-based
internets: MIB-II", STD 17, RFC 1213, Hughes LAN Systems,
Performance Systems International, March 1991.
[3] Case, J., Fedor, M., Schoffstall, M., and J. Davin. " A
Simple Network Management Protocol (SNMP)", STD 15, RFC
1157, SNMP Research, Performance Systems International,
MIT Lab for Computer Science, May 1990.
[4] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M.,
and S. Waldbusser, "Protocol Operations for Version 2 of
the Simple Network Management Protocol (SNMPv2)", RFC
1905, January 1996.
[5] McCloghrie, K. and F. Kastenholz, "Evolution of the
Interfaces Group of MIB-II", RFC 1573, Hughes LAN
Systems, FTP Software, January 1994.
[6] T. Bradley, C. Brown, A. Malis, "Multiprotocol
Interconnect over Frame Relay", RFC 1490, 07/26/1993.
[7] International Telegraph and Telephone Consultative
Committee, "ISDN Data Link Layer Specification for Frame
Mode Bearer Services", CCITT Recommendation Q.922,
April 1991.
[8] International Telegraph and Telephone Consultative
Committee, "ISDN User-Network Interface-Datab Link
Layer Specification ", CCITT Recommendation Q.921,
April 1991.
[9] International Telegraph and Telephone Consultative
Committee, "Signalling Specification for Frame Mode
Basic Call Control", CCITT Recommendation Q.933,
March 1993.
Cochrane & Kashef [Page 23]
INTERNET-DRAFT EXPIRATION DATE: DECEMBER 13 1996
Draft Frame Relay DTE Extensions MIB June 1996
[10] International Telegraph and Telephone Consultative
Committee, "ISDN User-Network Interface Layer 3
Specification for Basic Call Control",
CCITT Recommendation Q.931,
March 1993.
Table of Contents
1 Status of this Memo ................................... 1
2 Abstract .............................................. 2
3 The SNMPv2 Network Management Framework ............... 2
4 Overview .............................................. 3
4.1 Frame Relay DTE Extensions for Switched Virtual Circuits
and Data Compression over Frame Relay ................... 3
5 Definitions ........................................... 3
5.1 Switched Virtual Circuit Data Link Connection Management
Interface ............................................... 4
5.2 Switched Virtual Circuit Table ...................... 10
5.3 Data Compression over Frame Relay Table ............. 20
6 Acknowledgements ...................................... 23
7 References ............................................ 23
Cochrane & Kashef [Page 24]