INTERNET-DRAFT EXPIRATION DATE: NOVEMBER 12 1997 Management Information Base for Frame Relay DTE Extensions for SVC's over Frame Relay Don Cochrane Cabletron Sys, Inc. 35E Industrial Way, 1st Floor Rochester New Hampshire, 03867 cochrane@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 Frame Relay DTE MIB. Please send comments the the author, copying iplpdn@cnri.reston.va.us. It expires November 1997. 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. This memo does not specify a standard for the Internet community. Cochrane [Page 1] Draft Frame Relay SVC DTE Extensions MIB May 1997 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 [Page 2] Draft Frame Relay SVC DTE Extensions MIB May 1997 4. Overview 4.1. Frame Relay Extensions for SVC's This MIB addresses the instances needed to be able to manage both the Frame Relay Forum's Implementation agreement for SVC's (FRF.4) as well as the ITU's X.36 Specification [10]. A copy of FRF.4 is available at www.frforum.com 5. Definitions FRAME-RELAY-DTE-SVC-MIB DEFINITIONS ::= BEGIN IMPORTS MODULE-IDENTITY, OBJECT-TYPE, Counter32, Integer32, NOTIFICATION-TYPE FROM SNMPv2-SMI TEXTUAL-CONVENTION, RowStatus, TimeStamp, DisplayString FROM SNMPv2-TC MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF frameRelayDTE, DLCI FROM RFC1315-MIB InterfaceIndex FROM IF-MIB; frameRelayDteSvc MODULE-IDENTITY LAST-UPDATED "9703250910Z" -- Monday 12 May, 0910 EDT 1997 ORGANIZATION "IETF frnetmib Working Group" CONTACT-INFO " Don Cochrane Cabletron Sys, Inc. 35E Industrial Way, 1st Floor Rochester New Hampshire, 03867 cochrane@ctron.com " DESCRIPTION " 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 DTE Switched Virtual Circuit's." ::= { frameRelayDTE 7 } frDteSvc OBJECT IDENTIFIER ::= { frameRelayDteSvc 1 } -- 5.1 Switched Virtual Circuit Link Connection Management Interface Table frSvcDlcmiTable OBJECT-TYPE SYNTAX SEQUENCE OF FrSvcDlcmiEntry MAX-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." ::= { frDteSvc 1 } frSvcDlcmiEntry OBJECT-TYPE SYNTAX FrSvcDlcmiEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "The information regarding a single switched Data Link Connection Management Interface." INDEX { frSvcDlcmiIfIndex } ::= { frSvcDlcmiTable 1 } -- Cochrane [Page 3] Draft Frame Relay SVC DTE Extensions MIB May 1997 FrSvcDlcmiEntry ::= SEQUENCE { -- -- Standard Interface Index parameter -- frSvcDlcmiIfIndex InterfaceIndex, frSvcDlcmiState INTEGER, -- -- Q.933 / X.36 Parameters -- frSvcDlcmiMaxNumCalls Integer32, frSvcDlcmiCallSetupTimer Integer32, frSvcDlcmiCallProceedingTimer Integer32, frSvcDlcmiCallDisconnectTimer Integer32, frSvcDlcmiCallReleaseTimer Integer32, frSvcDlcmiStatusEnquiryTimer Integer32, frSvcDlcmiErrorThreshold Integer32, frSvcDlcmiResetSentTimer Integer32, frSvcDlcmiResetAckTimer Integer32, -- -- Q.922 Parameters -- frSvcDlcmiIdleTimer Integer32, frSvcDlcmiRetransmissionTimer TimeTicks, frSvcDlcmiNumRetransmissions Integer32, frSvcDlcmiMaxInfoFieldSize Integer32, frSvcDlcmiMaxInfoFrames Integer32, frSvcDlcmiQ922State INTEGER } frSvcDlcmiIfIndex OBJECT-TYPE SYNTAX InterfaceIndex MAX-ACCESS read-only STATUS current DESCRIPTION "The ifIndex value of the corresponding ifEntry." ::= { frSvcDlcmiEntry 1 } Cochrane [Page 4] Draft Frame Relay SVC DTE Extensions MIB May 1997 frSvcDlcmiState OBJECT-TYPE SYNTAX INTEGER { q933SVC(1) -- Frame Relay Forum IA FRF.4 SVC implementation x.36(2) -- ITU Frame Relay implementation none(3) -- Implies no SVC Data Link Connection management on this interface } MAX-ACCESS read-write 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 Integer32 MAX-ACCESS read-only STATUS current DESCRIPTION "Indicates the maximum number of calls allowed on the interface." ::= { frSvcDlcmiEntry 3 } frSvcDlcmiCallSetupTimer OBJECT-TYPE SYNTAX Integer32 UNITS "seconds" MAX-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. The default value is 4 seconds." REFERENCE "ITU-T Standard Q.931, Section 9.2: Timer T303." DEFVAL { 4 } ::= { frSvcDlcmiEntry 4 } frSvcDlcmiCallProceedingTimer OBJECT-TYPE SYNTAX Integer32 UNITS "seconds" MAX-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. The default value is 10 seconds." REFERENCE "ITU-T Standard Q.931, Section 9.2: Timer T310." DEFVAL { 10 } ::= { frSvcDlcmiEntry 5 } Cochrane [Page 5] Draft Frame Relay SVC DTE Extensions MIB May 1997 frSvcDlcmiCallDisconnectTimer OBJECT-TYPE SYNTAX Integer32 UNITS "seconds" MAX-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. The default value for this timer is 30 seconds." REFERENCE "ITU-T Standard Q.931, Section 9.2: Timer T305." DEFVAL { 30 } ::= { frSvcDlcmiEntry 6 } frSvcDlcmiCallReleaseTimer OBJECT-TYPE SYNTAX Integer32 UNITS "seconds" MAX-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. The default value fo rthis timer is 4 seconds." REFERENCE "ITU-T Standard Q.931, Section 9.2: Timer T308." DEFVAL { 4 } ::= { frSvcDlcmiEntry 7 } Cochrane [Page 6] Draft Frame Relay SVC DTE Extensions MIB May 1997 frSvcDlcmiStatusEnquiryTimer OBJECT-TYPE SYNTAX Integer32 UNITS "seconds" MAX-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. The default value is 4 retries." REFERENCE "ITU-T Standard Q.931, Section 9.2: Timer T322." DEFVAL { 4 } ::= { frSvcDlcmiEntry 8 } frSvcDlcmiErrorThreshold OBJECT-TYPE SYNTAX Integer32 MAX-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 } frSvcDlcmiResetSentTimer OBJECT-TYPE SYNTAX Integer32 UNITS "seconds" MAX-ACCESS read-write STATUS current DESCRIPTION "This timer is started when a RESTART message is sent. If a RESTART ACKNOWLEDGEmessage is received, the timer will be stopped. If the Timer expires expires it may be retried one or more times until a RESTART ACKNOWLEDGE message is returned. Meanwhile No calls shall be placed or accepted over the interface by the originator of the RESTART message. The network shall limit the number of consecutive unsuccessful attempts to a default of 2. The default value for the Timer is 120 seconds" REFERENCE "ITU-T Standard Q.931, Section 9.2: Timer T316." DEFVAL { 120 } ::= { frSvcDlcmiEntry 10 } frSvcDlcmiResetAckTimer OBJECT-TYPE SYNTAX Integer32 UNITS "seconds" MAX-ACCESS read-write STATUS current DESCRIPTION "This timer is started when a RESTART message is received. At this time the receiving entity shall initiate the appropriate internal actions to return the specified interface to the idle condition and call references to the Null state. Upon expiry of the timer, a notification shall be made to the maintenance entity. NOTE: This Timer MUST be less than Timer T316. " REFERENCE "ITU-T Standard Q.931, Section 9.2: Timer T317." ::= { frSvcDlcmiEntry 11 } frSvcDlcmiIdleTimer OBJECT-TYPE SYNTAX Integer32 UNITS "seconds" MAX-ACCESS read-write STATUS current DESCRIPTION "This is the maximum time allowed without any frames being exchanged. The default for this timer is 30 seconds." REFERENCE "ITU-T Standard Q.921, Section 5.9 / Q.922 Section 5.9: Timer T203." DEFVAL { 30 } ::= { frSvcDlcmiEntry 12 } Cochrane [Page 7] Draft Frame Relay SVC DTE Extensions MIB May 1997 frSvcDlcmiRetransmissionTimer OBJECT-TYPE SYNTAX TimeTicks MAX-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 , it may be retried N200 times. When N200 times have been reached, a DL-RELEASE message will be sent to the Layer 3 entity. The default for this timer is 1.5 seconds." REFERENCE "ITU-T Standard Q.921, Section 5.9 / Q.922 Section 5.9: Timer T200." DEFVAL { 1500 } ::= { frSvcDlcmiEntry 13 } frSvcDlcmiNumRetransmissions OBJECT-TYPE SYNTAX Integer32 MAX-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. The default for this value is 3 retries." REFERENCE "ITU-T Standard Q.921, Section 5.9 / Q.922 Section 5.9: N200." DEFVAL { 3 } ::= { frSvcDlcmiEntry 14 } frSvcDlcmiInfoFieldSize OBJECT-TYPE SYNTAX Integer32 UNITS "octets" MAX-ACCESS read-write STATUS current DESCRIPTION "This value indicates the maximum number of octets in an Information field. The default value is 260 octets." REFERENCE "ITU-T Standard Q.921, Section 5.9 / Q.922 Section 5.9: N201." DEFVAL { 260 } ::= { frSvcDlcmiEntry 15 } -- Cochrane [Page 8] Draft Frame Relay SVC DTE Extensions MIB May 1997 frSvcDlcmiMaxIFrames OBJECT-TYPE SYNTAX Integer32 (1..127) MAX-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 (this is the default value), 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 16 } frSvcDlcmiQ922State OBJECT-TYPE SYNTAX INTEGER { teiUnassigned(1), assignAwaitingTei(2), establishingAwaitingTei(3), teiAssigned(4), awaitingEstablishment(5), awaitingRelease(6), multipleFrameEstablished(7), timerRecovery(8) } MAX-ACCESS read-only STATUS current DESCRIPTION "This value indicates the state of the Q.922 Point to Point Data Link Layer Negotiation. " REFERENCE "ITU-T Standard Q.922, Appendix B.2" ::= { frSvcDlcmiEntry 17 } Cochrane [Page 9] Draft Frame Relay SVC DTE Extensions MIB May 1997 -- 5.2 Switched Virtual Circuit Table -- The table describing the use of the DLCIs attached to -- each Switched Frame Relay Interface. frDteSvc OBJECT IDENTIFIER ::= { frameRelayDteSvc 2 } frSvcTable OBJECT-TYPE SYNTAX SEQUENCE OF FrSvcEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "A table containing information about specific Data Link Connection Identifiers and corresponding switched virtual circuits." ::= { frDteSvc 2 } frSvcEntry OBJECT-TYPE SYNTAX FrSvcEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "The information regarding a single switched Data Link Connection Identifier." INDEX { frSvcIfIndex, frSvcDlci } ::= { frSvcTable 1 } FrSvcEntry ::= SEQUENCE { -- -- Standard Circuit parameters -- frSvcIfIndex InterfaceIndex, frSvcDlci DLCI, frSvcReceivedFECNs Counter32, frSvcReceivedBECNs Counter32, frSvcSentFrames Counter32, frSvcSentOctets Counter32, frSvcReceivedFrames Counter32, frSvcReceivedOctets Counter32, frSvcCreationTime TimeTicks, Cochrane [Page 10] Draft Frame Relay SVC DTE Extensions MIB May 1997 -- -- Link Layer Core Parameters -- frSvcInFmifSize Integer32, frSvcOutFmifSize Integer32, frSvcInCommittedBurst Integer32, frSvcOutCommittedBurst Integer32, frSvcInExcessBurst Integer32, frSvcOutExcessBurst Integer32, frSvcInCIR Integer32, frSvcOutCIR Integer32, frSvcInMinCIR Integer32, frSvcOutMinCIR Integer32, -- -- Q.933 / X.36 Parameters -- frSvcState INTEGER, frSvcCallReferenceValue Integer32, frSvcCallingAddr Integer32, frSvcCallingSubAddr Integer32, frSvcCalledAddr Integer32, frSvcCalledSubAddr Integer32, frSvcConnectedAddr Integer32, frSvcConnectedSubAddr Integer32, frSvcCallSetup INTEGER, frSvcCallOrigination INTEGER } frSvcIfIndex OBJECT-TYPE SYNTAX InterfaceIndex MAX-ACCESS read-only STATUS current DESCRIPTION "The ifIndex Value of the ifEntry this virtual circuit is layered onto." ::= { frSvcEntry 1 } Cochrane [Page 11] Draft Frame Relay SVC DTE Extensions MIB May 1997 frSvcDlci OBJECT-TYPE SYNTAX DLCI MAX-ACCESS read-only STATUS current DESCRIPTION "The Data Link Connection Identifier for this virtual circuit." ::= { frSvcEntry 2 } frSvcReceivedFECNs OBJECT-TYPE SYNTAX Counter32 MAX-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 Counter32 MAX-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 Counter32 MAX-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 Counter32 UNITS "octets" MAX-ACCESS read-only STATUS current DESCRIPTION "The number of octets sent from this virtual circuit since it was created." ::= { frSvcEntry 6 } Cochrane [Page 12] Draft Frame Relay SVC DTE Extensions MIB May 1997 frSvcReceivedFrames OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "Number of frames received over this virtual circuit since it was created." ::= { frSvcEntry 7 } frSvcReceivedOctets OBJECT-TYPE SYNTAX Counter32 UNITS "octets" MAX-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 MAX-ACCESS read-only STATUS current DESCRIPTION "The value of sysUpTime when the virtual cir- cuit was created." ::= { frSvcEntry 9 } frSvcInMaxFmifSize OBJECT-TYPE SYNTAX Integer32 UNITS "octets" MAX-ACCESS read-write STATUS current DESCRIPTION "This variable indicates the maximum amount of end user data octets in a frame for in the direction of the calling user to the called user. The default value is 262 octets." REFERENCE "ITU-T Standard Q.933, Section 4.5.19" DEFVAL { 262 } ::= { frSvcEntry 10 } frSvcOutMaxFmifSize OBJECT-TYPE SYNTAX Integer32 UNITS "octets" MAX-ACCESS read-write STATUS current DESCRIPTION "This variable indicates the maximum amount of end user data octets in a frame for in the direction of the called user to the calling user. The default value is 262 octets." REFERENCE "ITU-T Standard Q.933, Section 4.5.19" DEFVAL { 262 } ::= { frSvcEntry 11 } Cochrane [Page 13] Draft Frame Relay SVC DTE Extensions MIB May 1997 frSvcInCommittedBurst OBJECT-TYPE SYNTAX Integer32 UNITS "bits" MAX-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. The default value is 0." REFERENCE "ITU-T Standard Q.933, Section 4.5.19" DEFVAL { 0 } -- the default indicates no commitment ::= { frSvcEntry 12 } frSvcOutCommittedBurst OBJECT-TYPE SYNTAX Integer32 UNITS "bits" MAX-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. The default value is 0." REFERENCE "ITU-T Standard Q.933, Section 4.5.19" DEFVAL { 0 } -- the default indicates no commitment ::= { frSvcEntry 13 } frSvcInExcessBurst OBJECT-TYPE SYNTAX Integer32 UNITS "bits" MAX-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 } Cochrane [Page 14] Draft Frame Relay SVC DTE Extensions MIB May 1997 frSvcOutExcessBurst OBJECT-TYPE SYNTAX Integer32 UNITS "bits" MAX-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 } frSvcInCIR OBJECT-TYPE SYNTAX Integer32 UNITS "bits per second" MAX-ACCESS read-write STATUS current DESCRIPTION "CIR 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. The default value is 0." REFERENCE "ITU-T Standard Q.933, Section 4.5.19" DEFVAL { 0 } -- the default value of CIR is -- "no commitment". ::= { frSvcEntry 16 } frSvcOutCIR OBJECT-TYPE SYNTAX Integer32 UNITS "bits per second" MAX-ACCESS read-write STATUS current DESCRIPTION "CIR 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. The default value is 0." REFERENCE "ITU-T Standard Q.933, Section 4.5.19" DEFVAL { 0 } -- the default value of CIR is -- "no commitment". ::= { frSvcEntry 17 } Cochrane [Page 15] Draft Frame Relay SVC DTE Extensions MIB May 1997 frSvcInMinCIR OBJECT-TYPE SYNTAX Integer32 UNITS "bits per second" MAX-ACCESS read-write STATUS current DESCRIPTION "Minimum Acceptable CIR 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. The default value is 0." REFERENCE "ITU-T Standard Q.933, Section 4.5.19" DEFVAL { 0 } -- the default value of CIR is -- "no commitment". ::= { frSvcEntry 18 } frSvcOutMinCIR OBJECT-TYPE SYNTAX Integer32 UNITS "bits per second" MAX-ACCESS read-write STATUS current DESCRIPTION "Minimum Acceptable CIR 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. The default value is 0." REFERENCE "ITU-T Standard Q.933, Section 4.5.19" DEFVAL { 0 } -- the default value of CIR is -- "no commitment". ::= { frSvcEntry 19 } frSvcState OBJECT-TYPE SYNTAX INTEGER { inProcess(1), complete(2) } MAX-ACCESS read-only STATUS current DESCRIPTION "Indicates whether the Connection has been completed and data can proceed (2), or if the call setup is still in process (1)." ::= { frSvcEntry 20 } Cochrane [Page 16] Draft Frame Relay SVC DTE Extensions MIB May 1997 frSvcCallReferenceValue OBJECT-TYPE SYNTAX Integer32 MAX-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 } frSvcCallingAddr OBJECT-TYPE SYNTAX DisplayString MAX-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 } frSvcCallingSubAddr OBJECT-TYPE SYNTAX DisplayString MAX-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 } frSvcCalledAddr OBJECT-TYPE SYNTAX DisplayString MAX-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 } Cochrane [Page 17] Draft Frame Relay SVC DTE Extensions MIB May 1997 frSvcCalledSubAddr OBJECT-TYPE SYNTAX DisplayString MAX-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 } frSvcCallSetup OBJECT-TYPE SYNTAX { setup(1), disconnect(2) } MAX-ACCESS read-write STATUS current DESCRIPTION "Indicates whether the call should be Setup or Disconnected." ::= { frSvcEntry 26 } frSvcCallOrigination OBJECT-TYPE SYNTAX INTEGER { remote(1), local(2) } MAX-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 } END Cochrane [Page 18] Draft Frame Relay SVC DTE Extensions MIB May 1997 6. Acknowledgements Special thanks to James Watt of Newbridge Networks and Bill Coutts of Cascade Commumications Corp for their assistance. 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] International Telegraph and Telephone Consultative Committee, "ISDN Data Link Layer Specification for Frame Mode Bearer Services", CCITT Recommendation Q.922, April 1991. [7] International Telegraph and Telephone Consultative Committee, "ISDN User-Network Interface-Datab Link Layer Specification ", CCITT Recommendation Q.921, April 1991. [8] International Telegraph and Telephone Consultative Committee, "Signalling Specification for Frame Mode Basic Call Control", CCITT Recommendation Q.933, March 1993. [9] International Telegraph and Telephone Consultative Committee, "ISDN User-Network Interface Layer 3 Specification for Basic Call Control", CCITT Recommendation Q.931, March 1993. [10] International Telegraph and Telephone Consultative Committee, "Draft Amendment 1", CCITT Recommendation X.36, April 1996. Cochrane [Page 19] Draft Frame Relay SVC DTE Extensions MIB May 1997 Table of Contents 1 Status of this Memo ................................... 1 2 Abstract .............................................. 1 3 The SNMPv2 Network Management Framework ............... 2 4 Overview .............................................. 3 4.1 Frame Relay SVC DTE Extensions for Switched Virtual Circuits ......................................................... 3 5 Definitions ........................................... 3 5.1 Switched Virtual Circuit Data Link Connection Management Interface ............................................... 3 5.2 Switched Virtual Circuit Table ...................... 10 6 Acknowledgements ...................................... 19 7 References ............................................ 19 Cochrane [Page 20]