idnits 2.17.1 draft-ietf-iplpdn-frmib-dte-09.txt: ** The Abstract section seems to be numbered Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Cannot find the required boilerplate sections (Copyright, IPR, etc.) in this document. Expected boilerplate is as follows today (2024-04-26) according to https://trustee.ietf.org/license-info : IETF Trust Legal Provisions of 28-dec-2009, Section 6.a: This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79. IETF Trust Legal Provisions of 28-dec-2009, Section 6.b(i), paragraph 2: Copyright (c) 2024 IETF Trust and the persons identified as the document authors. All rights reserved. IETF Trust Legal Provisions of 28-dec-2009, Section 6.b(i), paragraph 3: This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- ** Missing document type: Expected "INTERNET-DRAFT" in the upper left hand corner of the first page ** Missing expiration date. The document expiration date should appear on the first and last page. ** The document seems to lack a 1id_guidelines paragraph about Internet-Drafts being working documents. ** The document seems to lack a 1id_guidelines paragraph about 6 months document validity -- however, there's a paragraph with a matching beginning. Boilerplate error? ** The document seems to lack a 1id_guidelines paragraph about the list of current Internet-Drafts. ** The document seems to lack a 1id_guidelines paragraph about the list of Shadow Directories. == No 'Intended status' indicated for this document; assuming Proposed Standard Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an Introduction section. ** The document seems to lack a Security Considerations section. ** The document seems to lack an IANA Considerations section. (See Section 2.2 of https://www.ietf.org/id-info/checklist for how to handle the case when there are no actions for IANA.) ** There are 15 instances of too long lines in the document, the longest one being 8 characters in excess of 72. Miscellaneous warnings: ---------------------------------------------------------------------------- == Line 74 has weird spacing: '... suit the r...' == Line 78 has weird spacing: '...Objects in t...' == Line 84 has weird spacing: '... object type ...' == Line 85 has weird spacing: '...niquely ident...' == Line 87 has weird spacing: '...tor, is used ...' == (3 more instances...) -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date () is 739384 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) -- Missing reference section? '1' on line 1269 looks like a reference -- Missing reference section? '2' on line 1274 looks like a reference -- Missing reference section? '3' on line 1279 looks like a reference -- Missing reference section? '4' on line 1284 looks like a reference -- Missing reference section? '5' on line 1289 looks like a reference -- Missing reference section? '6' on line 1293 looks like a reference -- Missing reference section? '7' on line 1296 looks like a reference -- Missing reference section? '8' on line 1301 looks like a reference -- Missing reference section? '9' on line 1306 looks like a reference -- Missing reference section? '10' on line 1314 looks like a reference Summary: 12 errors (**), 0 flaws (~~), 7 warnings (==), 12 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 Management Information Base for Frame Relay DTEs 2 draft-ietf-iplpdn-frmib-dte-09.txt 4 Wed Dec 4 17:02:10 PST 1996 6 Caralyn Brown 8 Cadia Networks, Inc. 9 1 Corporate Drive 10 Andover, Massachusetts 01810 12 cbrown@cadia.com 14 Fred Baker 16 Cisco Systems 17 519 Lado Drive 18 Santa Barbara, California 93111 20 fred@cisco.com 22 1. Status of this Memo 24 This document is an Internet-Draft. Internet-Drafts are 25 working documents of the Internet Engineering Task Force 26 (IETF), its areas, and its working groups. Note that other 27 groups may also distribute working documents as Internet- 28 Drafts. 30 Internet-Drafts are draft documents valid for a maximum of six 31 months. Internet-Drafts may be updated, replaced, or 32 obsoleted by other documents at any time. It is not 33 appropriate to use Internet-Drafts as reference material or to 34 cite them other than as a ``working draft'' or ``work in 35 progress.'' 36 Draft Frame Relay DTE MIB December 1996 38 To learn the current status of any Internet-Draft, please 39 check the 1id-abstracts.txt listing contained in the 40 Internet-Drafts Shadow Directories on ds.internic.net, 41 nic.nordu.net, ftp.nisc.sri.com, or munnari.oz.au. 43 This draft document will be submitted to the RFC editor as an 44 extension to the SNMP MIB. Please send comments to the 45 authors, copying frs-mib@newbridge.com and ion@nexen.com. It 46 expires June 1997. 48 2. Abstract 50 This memo defines a portion of the Management Information Base 51 (MIB) for use with network management protocols in TCP/IP- 52 based internets. In particular, it defines objects for 53 managing Frame Relay interfaces on DTEs. 55 This memo does not specify a standard for the Internet 56 community. 58 3. The SNMPv2 Network Management Framework 60 The major components of the SNMPv2 Network Management 61 framework are described in the documents listed below. 63 o RFC 1902 [1] defines the Structure of Management 64 Information (SMI), the mechanisms used for describing and 65 naming objects for the purpose of management. 67 o STD 17, RFC 1213 [2] defines MIB-II, the core set of 68 managed objects (MO) for the Internet suite of protocols. 70 o RFC 1905 [3] defines the protocol used for network access 71 to managed objects. 73 The framework is adaptable/extensible by defining new MIBs to 74 suit the requirements of specific 75 applications/protocols/situations. 77 Managed objects are accessed via a virtual information store, 78 the MIB. Objects in the MIB are defined using the 79 subset of Abstract Syntax Notation One (ASN.1) defined in the 80 SMI. In particular, each object type is named by an OBJECT 81 Draft Frame Relay DTE MIB December 1996 83 IDENTIFIER, which is an administratively assigned name. The 84 object type together with an object instance serves to 85 uniquely identify a specific instantiation of the object. 86 For human convenience, often a textual string, termed the 87 descriptor, is used to refer to the object type. 89 Draft Frame Relay DTE MIB December 1996 91 4. Overview 93 4.1. Frame Relay Operational Model 95 For the purposes of understanding this document, Frame Relay 96 is viewed as a multi-access media, not as a group of point- 97 to-point connections. This model proposes that Frame Relay is 98 a single interface to the network (physical connection) with 99 many destinations or neighbors (virtual connections). This 100 view enables a network manager the ability to group all 101 virtual connections with their corresponding physical 102 connection thereby allowing simpler diagnostics and trouble 103 shooting. 105 With the extension of the interfaces MIB, it is possible to 106 configure frame relay DLCs as individual interfaces and create 107 ifTable entries for each. This is not recommended and is not 108 directly supported by this MIB. Additionally, in the presence 109 of demand circuits creation of individual ifEntries for each 110 is not possible. 112 Should the user wish to group DLCs together to associate them 113 with a higher layer, or to associate a DLC with an unnumbered 114 point-to-point service, the frame relay DTE MIB provides an 115 entry in the frCircuitEntry record. For example, suppose one 116 were to configure a company proprietary protocol to run above 117 several of the frame relay VCs. The basic layering would look 118 something like the following: 120 Draft Frame Relay DTE MIB December 1996 122 IP (ipaddrEntry 1 ) IP (ipaddrEntry 2) IP (ipaddrEntry 3) 123 | | | 124 | | | 125 | | proprietary protocol 126 | | layer (ifIndex 3) 127 | | | 128 | | | 129 DLCI 20 DLCI 30 DLCI 40/41/42 130 (ifIndex 2) (ifIndex 2) (ifIndex 2, 131 logical ifIndex 3) 132 | | | 133 | | | 134 |____________________|_____________________| 135 | 136 | 137 FR DLMCI (ifIndex.2) 138 | 139 | 140 Physical Interface (ifIndex.1) 142 A configuration which specified that DLCI 40, 41,and 42 were 143 associated with a proprietary protocol layer, while DLCI 20 144 and 30 were to run IP directly can now be expressed using a 145 combination of frCircuitIfIndex and frCircuitLogicalIfIndex. 146 In this particular case DLCIs 40, 41 and 42 would use 147 frCircuitIfIndex equal to the frame relay interface level (2) 148 while their frCircuitLogicalIfIndex would indicate the 149 proprietary protocol (3). DLCIs 20 and 30 would have both 150 instances set to the frame relay interface (2). 152 Object Meaning for Frame Relay Interface 153 ______ _____________________________________ 155 ifDescr As per DESCRIPTION in RFC 1573. 156 ifType The value allocated for Frame Relay 157 Interfaces - frameRelay (32). 159 ifMtu Set to maximum frame size in octets for 160 this frame relay interface. 162 ifSpeed The access rate for the frame relay 163 interface. This could be different from 164 the speed of the underlying physical 166 Draft Frame Relay DTE MIB December 1996 168 interface, e.g. in a fractional T1 case 169 the access rate could be 384 kbits/s (the 170 value reported in this object) whereas the 171 speed of the underlying interface would be 172 1.544 Mbits/s (the value reported in the 173 instance of ifSpeed for the ifEntry with 174 type ds1). 176 ifPhysAddress The primary address for this interface 177 assigned by the Frame Relay interface 178 provider. An octet string of zero length 179 if no address is used for this interface. 181 ifAdminStatus As per DESCRIPTION in RFC 1573. 183 ifOperStatus As per DESCRIPTION in RFC 1573. 185 ifLastChange As per DESCRIPTION in RFC 1573. 187 ifInOctets The number of received octets. This 188 includes not only the information field 189 (user data) but also the frame relay header 190 and CRC. 192 ifInUcastPkts The number of frames received on non- 193 multicast DLCIs 195 ifInDiscards The number of frames that were successfully 196 received but were discarded because of 197 format errors or because the VC was not 198 known. Format errors, in this case, are 199 any errors which would prevent the system 200 from recognizing the DLCI and placing the 201 error in the frCircuitDiscard category. 203 ifInErrors The number of received frames that are 204 discarded, because of an error. 205 Possible errors can be the following: the 206 frame relay frames were too long or were 207 too short, the frames had an invalid or 208 unrecognized DLCI values, or incorrect 209 header values. 211 ifInUnknownProtos Number of unknown or unsupported 212 upper layer protocol frames received 214 Draft Frame Relay DTE MIB December 1996 216 and discarded. 218 ifOutOctets The number of received octets. This 219 includes not only the information field 220 (user data) but also the frame relay header 221 and CRC. 223 ifOutUcastpkts The number of frames sent. 225 ifOutDiscards The number of frames discarded in the 226 transmit direction. 228 ifOutErrors The number of frames discarded in the 229 egress direction, because of errors. 231 ifName As per DESCRIPTION in RFC 1573. 233 ifInMulticastPkts The number of unerrored frames received 234 on a multicast DLCI. 236 ifInBroadcastPkts Always zero (0) as there are no broadcast 237 frames. 239 ifOutMulticastPkts The number of frames transmitted over a 240 multicast DLCI. 242 ifOutBroadcastPkts Always zero (0) as there are no broadcast 243 frames. 245 ifHCInOctets Only required when ifSpeed >= 155 Mbits/s. 246 See 247 details for ifInOctets. 249 ifHCOutOctets Only required when ifSpeed >= 155 Mbits/s. 250 See 251 details for ifInOctets. 253 ifLinkUpDownTrapEnble As per DESCRIPTION in RFC 1573. 255 ifHighSpeed The access rate of the frame relay interface 256 measured in Mbits/s. If the access rate is 257 less than 1 Mbits/s, this object returns 0. 259 ifPromiscuousMode Set to false(2). 261 Draft Frame Relay DTE MIB December 1996 263 ifConnectorPresent Set to false(2). 265 4.2. Textual Conventions 267 One new data type is introduced as a textual convention in 268 this MIB document. This textual convention enhances the 269 readability of the specification and can ease comparison with 270 other specifications if appropriate. It should be noted that 271 the introduction of this textual conventions has no effect on 272 either the syntax nor the semantics of any managed objects. 273 The use of this is merely an artifact of the explanatory 274 method used. Objects defined in terms of one of these methods 275 are always encoded by means of the rules that define the 276 primitive type. Hence, no changes to the SMI or the SNMP are 277 necessary to accommodate this textual conventions which is 278 adopted merely for the convenience of readers and writers in 279 pursuit of the elusive goal of clear, concise, and unambiguous 280 MIB documents. 282 The new data type is DLCI. DLCI refers to the range 283 0..DLCINumber, and is used to refer to the valid Data Link 284 Connection Indices. DLCINumber is, by definition, the largest 285 possible DLCI value possible under the configured Q.922 286 Address Format. 288 4.3. Structure of MIB 290 The MIB is composed of three groups, one defining the Data 291 Link Connection Management Interface (DLCMI), one describing 292 the Circuits, and a third describing errors. 294 During normal operation, Frame Relay virtual circuits will be 295 added, deleted and change availability. The occurrence of 296 such changes is of interest to the network manager and 297 therefore, one trap is defined, intended to be corollary to 298 the SNMP "Link Up" and "Link Down" traps. 300 Draft Frame Relay DTE MIB December 1996 302 5. Definitions 304 FRAME-RELAY-DTE-MIB DEFINITIONS ::= BEGIN 306 IMPORTS 307 MODULE-IDENTITY, OBJECT-TYPE, Counter32, 308 Integer32, NOTIFICATION-TYPE FROM SNMPv2-SMI 309 TEXTUAL-CONVENTION, RowStatus, TimeStamp FROM SNMPv2-TC 310 MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF 311 transmission FROM RFC1213-MIB 312 InterfaceIndex FROM IF-MIB; 314 -- Frame Relay DTE MIB 316 frameRelayDTE MODULE-IDENTITY 317 LAST-UPDATED "9612041702Z" -- Wed Dec 4 17:02:10 PST 1996 318 ORGANIZATION "IETF IPLPDN Working Group" 319 CONTACT-INFO 320 " Caralyn Brown 321 Postal: Cadia Networks, Inc. 322 1 Corporate Drive 323 Andover, Massachusetts 01810 324 Tel: +1 508 689 2400 x133 325 E-Mail: cbrown@cadia.com 327 Fred Baker 328 Postal: Cisco Systems 329 519 Lado Drive 330 Santa Barbara, California 93111 331 Tel: +1 408 526 4257 332 E-Mail: fred@cisco.com" 333 DESCRIPTION 334 "The MIB module to describe the use of a Frame Relay 335 interface by a DTE. This was converted from RFC 1315's 336 SMI-V1 to SMI-V2; therefore, indices are read-only 337 rather than being not-accessible." 338 ::= { transmission 32 } 340 -- 341 -- the range of a Data Link Connection Identifier 342 -- 343 DLCI ::= TEXTUAL-CONVENTION 344 STATUS current 345 DESCRIPTION 347 Draft Frame Relay DTE MIB December 1996 349 "The range of DLCI values. Note that this varies by 350 interface configuration; normally, interfaces may use 351 0..1023, but may be configured to use ranges as large 352 as 0..2^23." 353 SYNTAX INTEGER (0..8388607) 355 -- 356 Draft Frame Relay DTE MIB December 1996 358 -- Data Link Connection Management Interface 360 -- The variables that configure the DLC Management Interface. 362 frDlcmiTable OBJECT-TYPE 363 SYNTAX SEQUENCE OF FrDlcmiEntry 364 MAX-ACCESS not-accessible 365 STATUS current 366 DESCRIPTION 367 "The Parameters for the Data Link Connection Management 368 Interface for the frame relay service on this 369 interface." 370 REFERENCE 371 "American National Standard T1.617-1991, Annex D" 372 ::= { frameRelayDTE 1 } 374 frDlcmiEntry OBJECT-TYPE 375 SYNTAX FrDlcmiEntry 376 MAX-ACCESS not-accessible 377 STATUS current 378 DESCRIPTION 379 "The Parameters for a particular Data Link Connection 380 Management Interface." 381 INDEX { frDlcmiIfIndex } 382 ::= { frDlcmiTable 1 } 384 FrDlcmiEntry ::= 385 SEQUENCE { 386 frDlcmiIfIndex InterfaceIndex, 387 frDlcmiState INTEGER, 388 frDlcmiAddress INTEGER, 389 frDlcmiAddressLen INTEGER, 390 frDlcmiPollingInterval INTEGER, 391 frDlcmiFullEnquiryInterval INTEGER, 392 frDlcmiErrorThreshold INTEGER, 393 frDlcmiMonitoredEvents INTEGER, 394 frDlcmiMaxSupportedVCs DLCI, 395 frDlcmiMulticast INTEGER, 396 frDlcmiStatus INTEGER, 397 frDlcmiRowStatus RowStatus 398 } 400 frDlcmiIfIndex OBJECT-TYPE 401 Draft Frame Relay DTE MIB December 1996 403 SYNTAX InterfaceIndex 404 MAX-ACCESS read-only 405 STATUS current 406 DESCRIPTION 407 "The ifIndex value of the corresponding ifEntry." 408 ::= { frDlcmiEntry 1 } 410 frDlcmiState OBJECT-TYPE 411 SYNTAX INTEGER { 412 noLmiConfigured (1), 413 lmiRev1 (2), 414 ansiT1617D (3), -- ANSI T1.617 Annex D 415 ansiT1617B (4), -- ANSI T1.617 Annex B 416 itut933A (5), -- CCITT Q933 Annex A 417 ansiT1617D1994 (6) -- ANSI T1.617a-1994 Annex D 418 } 419 MAX-ACCESS read-create 420 STATUS current 421 DESCRIPTION 422 "This variable states which Data Link Connection 423 Management scheme is active (and by implication, what 424 DLCI it uses) on the Frame Relay interface." 425 REFERENCE 426 "American National Standard T1.617-1991, American 427 National Standard T1.617a-1994, ITU-T Recommendation 428 Q.933 (03/93)." 430 ::= { frDlcmiEntry 2 } 432 frDlcmiAddress OBJECT-TYPE 433 SYNTAX INTEGER { 434 q921 (1), -- 13 bit DLCI 435 q922March90 (2), -- 11 bit DLCI 436 q922November90 (3), -- 10 bit DLCI 437 q922 (4) -- Final Standard 438 } 439 MAX-ACCESS read-create 440 STATUS current 441 DESCRIPTION 442 "This variable states which address format is in use on 443 the Frame Relay interface." 444 ::= { frDlcmiEntry 3 } 446 Draft Frame Relay DTE MIB December 1996 448 frDlcmiAddressLen OBJECT-TYPE 449 SYNTAX INTEGER { 450 twoOctets (2), 451 threeOctets (3), 452 fourOctets (4) 453 } 454 MAX-ACCESS read-create 455 STATUS current 456 DESCRIPTION 457 "This variable states the address length in octets. In 458 the case of Q922 format, the length indicates the 459 entire length of the address including the control 460 portion." 461 ::= { frDlcmiEntry 4 } 463 frDlcmiPollingInterval OBJECT-TYPE 464 SYNTAX INTEGER (5..30) 465 UNITS "seconds" 466 MAX-ACCESS read-create 467 STATUS current 468 DESCRIPTION 469 "This is the number of seconds between successive 470 status enquiry messages." 471 REFERENCE 472 "American National Standard T1.617-1991, Section D.7 473 Timer T391." 474 DEFVAL { 10 } 475 ::= { frDlcmiEntry 5 } 477 frDlcmiFullEnquiryInterval OBJECT-TYPE 478 SYNTAX INTEGER (1..255) 479 MAX-ACCESS read-create 480 STATUS current 481 DESCRIPTION 482 "Number of status enquiry intervals that pass before 483 issuance of a full status enquiry message." 484 REFERENCE 485 "American National Standard T1.617-1991, Section D.7 486 Counter N391." 487 DEFVAL { 6 } 488 ::= { frDlcmiEntry 6 } 490 Draft Frame Relay DTE MIB December 1996 492 frDlcmiErrorThreshold OBJECT-TYPE 493 SYNTAX INTEGER (1..10) 494 MAX-ACCESS read-create 495 STATUS current 496 DESCRIPTION 497 "This is the maximum number of unanswered Status 498 Enquiries the equipment shall accept before declaring 499 the interface down." 500 REFERENCE 501 "American National Standard T1.617-1991, Section D.5.1 502 Counter N392." 503 DEFVAL { 3 } 504 ::= { frDlcmiEntry 7 } 506 frDlcmiMonitoredEvents OBJECT-TYPE 507 SYNTAX INTEGER (1..10) 508 MAX-ACCESS read-create 509 STATUS current 510 DESCRIPTION 511 "This is the number of status polling intervals over 512 which the error threshold is counted. For example, if 513 within 'MonitoredEvents' number of events the station 514 receives 'ErrorThreshold' number of errors, the 515 interface is marked as down." 516 REFERENCE 517 "American National Standard T1.617-1991, Section D.5.2 518 Counter N393." 519 DEFVAL { 4 } 520 ::= { frDlcmiEntry 8 } 522 frDlcmiMaxSupportedVCs OBJECT-TYPE 523 SYNTAX DLCI 524 MAX-ACCESS read-create 525 STATUS current 526 DESCRIPTION 527 "The maximum number of Virtual Circuits allowed for 528 this interface. Usually dictated by the Frame Relay 529 network. 531 In response to a SET, if a value less than zero or 532 higher than the agent's maximal capability is 533 configured, the agent should respond badValue" 534 ::= { frDlcmiEntry 9 } 536 Draft Frame Relay DTE MIB December 1996 538 frDlcmiMulticast OBJECT-TYPE 539 SYNTAX INTEGER { 540 nonBroadcast (1), 541 broadcast (2) 542 } 543 MAX-ACCESS read-create 544 STATUS current 545 DESCRIPTION 546 "This indicates whether the Frame Relay interface is 547 using a multicast service." 548 ::= { frDlcmiEntry 10 } 550 frDlcmiStatus OBJECT-TYPE 551 SYNTAX INTEGER { 552 running (1), -- init complete, system running 553 fault (2), -- error threshold exceeded 554 initializing (3) -- system start up 555 } 556 MAX-ACCESS read-only 557 STATUS current 558 DESCRIPTION 559 "This indicates the status of the Frame Relay interface 560 as determined by the performance of the dlcmi. If no 561 dlcmi is running, the Frame Relay interface will stay 562 in the running state indefinitely." 563 ::= { frDlcmiEntry 11 } 565 frDlcmiRowStatus OBJECT-TYPE 566 SYNTAX RowStatus 567 MAX-ACCESS read-create 568 STATUS current 569 DESCRIPTION 570 "SNMP Version 2 Row Status Variable." 571 ::= { frDlcmiEntry 12 } 572 -- 573 Draft Frame Relay DTE MIB December 1996 575 -- A Frame Relay service is a multiplexing service. Data 576 -- Link Connection Identifiers enumerate virtual circuits 577 -- (permanent or dynamic) which are layered onto the underlying 578 -- circuit, represented by ifEntry. Therefore, each of the entries 579 -- in the Standard MIB's Interface Table with an IfType of 580 -- Frame Relay represents a Q.922 interface. Zero or more 581 -- virtual circuits are layered onto this interface and provide 582 -- interconnection with various remote destinations. 583 -- Each such virtual circuit is represented by an entry in the 584 -- circuit table. The management virtual circuit (i.e. DLCI 0) 585 -- is a virtual circuit by this definition and will be represented 586 -- with an entry in the circuit table. 588 -- Circuit Table 590 -- The table describing the use of the DLCIs attached to 591 -- each Frame Relay Interface. 593 frCircuitTable OBJECT-TYPE 594 SYNTAX SEQUENCE OF FrCircuitEntry 595 MAX-ACCESS not-accessible 596 STATUS current 597 DESCRIPTION 598 "A table containing information about specific Data 599 Link Connections (DLC) or virtual circuits." 600 ::= { frameRelayDTE 2 } 602 frCircuitEntry OBJECT-TYPE 603 SYNTAX FrCircuitEntry 604 MAX-ACCESS not-accessible 605 STATUS current 606 DESCRIPTION 607 "The information regarding a single Data Link 608 Connection." 609 INDEX { frCircuitIfIndex, frCircuitDlci } 610 ::= { frCircuitTable 1 } 612 FrCircuitEntry ::= 613 SEQUENCE { 614 frCircuitIfIndex InterfaceIndex, 615 frCircuitDlci DLCI, 616 frCircuitState INTEGER, 617 frCircuitReceivedFECNs Counter32, 618 frCircuitReceivedBECNs Counter32, 620 Draft Frame Relay DTE MIB December 1996 622 frCircuitSentFrames Counter32, 623 frCircuitSentOctets Counter32, 624 frCircuitReceivedFrames Counter32, 625 frCircuitReceivedOctets Counter32, 626 frCircuitCreationTime TimeStamp, 627 frCircuitLastTimeChange TimeStamp, 628 frCircuitCommittedBurst Integer32, 629 frCircuitExcessBurst Integer32, 630 frCircuitThroughput Integer32, 631 frCircuitMulticast INTEGER, 632 frCircuitType INTEGER, 633 frCircuitDiscards Counter32, 634 frCircuitReceivedDEs Counter32, 635 frCircuitSentDEs Counter32, 636 frCircuitLogicalIfIndex InterfaceIndex, 637 frCircuitRowStatus RowStatus 638 } 640 frCircuitIfIndex OBJECT-TYPE 641 SYNTAX InterfaceIndex 642 MAX-ACCESS read-only 643 STATUS current 644 DESCRIPTION 645 "The ifIndex Value of the ifEntry this virtual circuit 646 is layered onto." 647 ::= { frCircuitEntry 1 } 649 frCircuitDlci OBJECT-TYPE 650 SYNTAX DLCI 651 MAX-ACCESS read-only 652 STATUS current 653 DESCRIPTION 654 "The Data Link Connection Identifier for this virtual 655 circuit." 656 REFERENCE 657 "American National Standard T1.618-1991, Section 3.3.6" 658 ::= { frCircuitEntry 2 } 660 frCircuitState OBJECT-TYPE 661 SYNTAX INTEGER { 662 invalid (1), 663 active (2), 665 Draft Frame Relay DTE MIB December 1996 667 inactive (3) 668 } 669 MAX-ACCESS read-create 670 STATUS current 671 DESCRIPTION 672 "Indicates whether the particular virtual circuit is 673 operational. In the absence of a Data Link Connection 674 Management Interface, virtual circuit entries (rows) 675 may be created by setting virtual circuit state to 676 'active', or deleted by changing Circuit state to 677 'invalid'. 679 Whether or not the row actually disappears is left to 680 the implementation, so this object may actually read as 681 'invalid' for some arbitrary length of time. It is 682 also legal to set the state of a virtual circuit to 683 'inactive' to temporarily disable a given circuit. 685 The use of 'invalid' is deprecated in this SNMP Version 686 2 MIB, in favor of frCircuitRowStatus." 687 DEFVAL { active } 688 ::= { frCircuitEntry 3 } 690 frCircuitReceivedFECNs OBJECT-TYPE 691 SYNTAX Counter32 692 MAX-ACCESS read-only 693 STATUS current 694 DESCRIPTION 695 "Number of frames received from the network indicating 696 forward congestion since the virtual circuit was 697 created. This occurs when the remote DTE sets the FECN 698 flag, or when a switch in the network enqueues the 699 frame to a trunk whose transmission queue is 700 congested." 701 REFERENCE 702 "American National Standard T1.618-1991, Section 3.3.3" 703 ::= { frCircuitEntry 4 } 705 frCircuitReceivedBECNs OBJECT-TYPE 706 SYNTAX Counter32 707 MAX-ACCESS read-only 708 STATUS current 709 DESCRIPTION 711 Draft Frame Relay DTE MIB December 1996 713 "Number of frames received from the network indicating 714 backward congestion since the virtual circuit was 715 created. This occurs when the remote DTE sets the BECN 716 flag, or when a switch in the network receives the 717 frame from a trunk whose transmission queue is 718 congested." 719 REFERENCE 720 "American National Standard T1.618-1991, Section 3.3.4" 721 ::= { frCircuitEntry 5 } 723 frCircuitSentFrames OBJECT-TYPE 724 SYNTAX Counter32 725 MAX-ACCESS read-only 726 STATUS current 727 DESCRIPTION 728 "The number of frames sent from this virtual circuit 729 since it was created." 730 ::= { frCircuitEntry 6 } 732 frCircuitSentOctets OBJECT-TYPE 733 SYNTAX Counter32 734 MAX-ACCESS read-only 735 STATUS current 736 DESCRIPTION 737 "The number of octets sent from this virtual circuit 738 since it was created. Octets counted are the full 739 frame relay header and the payload, but do not include 740 the flag characters or CRC." 741 ::= { frCircuitEntry 7 } 743 frCircuitReceivedFrames OBJECT-TYPE 744 SYNTAX Counter32 745 MAX-ACCESS read-only 746 STATUS current 747 DESCRIPTION 748 "Number of frames received over this virtual circuit 749 since it was created." 750 ::= { frCircuitEntry 8 } 752 frCircuitReceivedOctets OBJECT-TYPE 753 SYNTAX Counter32 755 Draft Frame Relay DTE MIB December 1996 757 MAX-ACCESS read-only 758 STATUS current 759 DESCRIPTION 760 "Number of octets received over this virtual circuit 761 since it was created. Octets counted include the full 762 frame relay header, but do not include the flag 763 characters or the CRC." 764 ::= { frCircuitEntry 9 } 766 frCircuitCreationTime OBJECT-TYPE 767 SYNTAX TimeStamp 768 MAX-ACCESS read-only 769 STATUS current 770 DESCRIPTION 771 "The value of sysUpTime when the virtual circuit was 772 created, whether by the Data Link Connection Management 773 Interface or by a SetRequest." 774 ::= { frCircuitEntry 10 } 776 frCircuitLastTimeChange OBJECT-TYPE 777 SYNTAX TimeStamp 778 MAX-ACCESS read-only 779 STATUS current 780 DESCRIPTION 781 "The value of sysUpTime when last there was a change in 782 the virtual circuit state" 783 ::= { frCircuitEntry 11 } 785 frCircuitCommittedBurst OBJECT-TYPE 786 SYNTAX Integer32 787 MAX-ACCESS read-create 788 STATUS current 789 DESCRIPTION 790 "This variable indicates the maximum amount of data, in 791 bits, that the network agrees to transfer under normal 792 conditions, during the measurement interval." 793 REFERENCE 794 "American National Standard T1.617-1991, Section 795 6.5.19" 796 DEFVAL { 0 } -- the default indicates no commitment 797 ::= { frCircuitEntry 12 } 799 Draft Frame Relay DTE MIB December 1996 801 frCircuitExcessBurst OBJECT-TYPE 802 SYNTAX Integer32 803 MAX-ACCESS read-create 804 STATUS current 805 DESCRIPTION 806 "This variable indicates the maximum amount of 807 uncommitted data bits that the network will attempt to 808 deliver over the measurement interval. 810 By default, if not configured when creating the entry, 811 the Excess Information Burst Size is set to the value 812 of ifSpeed." 813 REFERENCE 814 "American National Standard T1.617-1991, Section 815 6.5.19" 816 ::= { frCircuitEntry 13 } 818 frCircuitThroughput OBJECT-TYPE 819 SYNTAX Integer32 820 MAX-ACCESS read-create 821 STATUS current 822 DESCRIPTION 823 "Throughput is the average number of 'Frame Relay 824 Information Field' bits transferred per second across a 825 user network interface in one direction, measured over 826 the measurement interval. 828 If the configured committed burst rate and throughput 829 are both non-zero, the measurement interval 830 T=frCircuitCommittedBurst/frCircuitThroughput. 832 If the configured committed burst rate and throughput 833 are both zero, the measurement interval 834 T=frCircuitExcessBurst/ifSpeed." 835 REFERENCE 836 "American National Standard T1.617-1991, Section 837 6.5.19" 838 DEFVAL {0} -- the default value of Throughput is 839 -- "no commitment". 840 ::= { frCircuitEntry 14 } 842 frCircuitMulticast OBJECT-TYPE 843 SYNTAX INTEGER { 844 unicast (1), 846 Draft Frame Relay DTE MIB December 1996 848 oneWay (2), 849 twoWay (3), 850 nWay (4) 851 } 852 MAX-ACCESS read-create 853 STATUS current 854 DESCRIPTION 855 "This indicates whether this VC is used as a unicast VC 856 (i.e. not multicast) or the type of multicast service 857 subscribed to" 858 REFERENCE 859 "Frame Relay PVC Multicast Service and Protocol 860 Description Implementation: FRF.7 Frame Relay Forum 861 Technical Committe October 21, 1994" 862 DEFVAL {unicast} -- the default value of frCircuitMulticast is 863 -- "unicast" (not a multicast VC). 864 ::= { frCircuitEntry 15 } 866 frCircuitType OBJECT-TYPE 867 SYNTAX INTEGER { 868 static (1), 869 dynamic (2) 870 } 871 MAX-ACCESS read-only 872 STATUS current 873 DESCRIPTION 874 "Indication of whether the VC was manually created 875 (static), or dynamically created (dynamic) via the data 876 link control management interface." 877 ::= { frCircuitEntry 16 } 879 frCircuitDiscards OBJECT-TYPE 880 SYNTAX Counter32 881 MAX-ACCESS read-only 882 STATUS current 883 DESCRIPTION 884 "The number of inbound frames dropped because of format 885 errors, or because the VC is inactive." 886 ::= { frCircuitEntry 17 } 888 frCircuitReceivedDEs OBJECT-TYPE 889 SYNTAX Counter32 891 Draft Frame Relay DTE MIB December 1996 893 MAX-ACCESS read-only 894 STATUS current 895 DESCRIPTION 896 "Number of frames received from the network indicating 897 that they were eligible for discard since the virtual 898 circuit was created. This occurs when the remote DTE 899 sets the DE flag, or when in remote DTE's switch 900 detects that the frame was received as Excess Burst 901 data." 902 REFERENCE 903 "American National Standard T1.618-1991, Section 3.3.4" 904 ::= { frCircuitEntry 18 } 906 frCircuitSentDEs OBJECT-TYPE 907 SYNTAX Counter32 908 MAX-ACCESS read-only 909 STATUS current 910 DESCRIPTION 911 "Number of frames sent to the network in- dicating 912 that they were eligible for discard since the virtual 913 circuit was created. This occurs when the local DTE 914 sets the DE flag, indicating that during Network 915 congestion situations those frames should be discarded 916 in preference of other frames sent without the DE bit 917 set." 918 REFERENCE 919 "American National Standard T1.618-1991, Section 920 3.3.4" 921 ::= { frCircuitEntry 19 } 923 frCircuitLogicalIfIndex OBJECT-TYPE 924 SYNTAX InterfaceIndex 925 MAX-ACCESS read-create 926 STATUS current 927 DESCRIPTION 928 "Normally the same value as frDlcmiIfIndex, but 929 different when an implementation associates a virtual 930 ifEntry with a DLC or set of DLCs in order to associate 931 higher layer objects such as the ipAddrEntry with a 932 subset of the virtual circuits on a Frame Relay 933 interface. The type of such ifEntries is defined by the 934 higher layer object; for example, if PPP/Frame Relay is 935 implemented, the ifType of this ifEntry would be PPP. 936 If it is not so defined, as would be the case with an 938 Draft Frame Relay DTE MIB December 1996 940 ipAddrEntry, it should be of type Other." 941 ::= { frCircuitEntry 20 } 943 frCircuitRowStatus OBJECT-TYPE 944 SYNTAX RowStatus 945 MAX-ACCESS read-create 946 STATUS current 947 DESCRIPTION 948 " This object is used to create a new row or modify or 949 destroy an existing row in the manner described in the 950 definition of the RowStatus textual convention." 951 ::= { frCircuitEntry 21 } 952 -- 953 Draft Frame Relay DTE MIB December 1996 955 -- Error Table 957 -- The table describing errors encountered on each Frame 958 -- Relay Interface. 960 frErrTable OBJECT-TYPE 961 SYNTAX SEQUENCE OF FrErrEntry 962 MAX-ACCESS not-accessible 963 STATUS current 964 DESCRIPTION 965 "A table containing information about Errors on the 966 Frame Relay interface." 967 ::= { frameRelayDTE 3 } 969 frErrEntry OBJECT-TYPE 970 SYNTAX FrErrEntry 971 MAX-ACCESS not-accessible 972 STATUS current 973 DESCRIPTION 974 "The error information for a single frame relay 975 interface." 976 INDEX { frErrIfIndex } 977 ::= { frErrTable 1 } 979 FrErrEntry ::= 980 SEQUENCE { 981 frErrIfIndex InterfaceIndex, 982 frErrType INTEGER, 983 frErrData OCTET STRING, 984 frErrTime TimeStamp, 985 frErrFaults Counter32, 986 frErrFaultTime TimeStamp 987 } 989 frErrIfIndex OBJECT-TYPE 990 SYNTAX InterfaceIndex 991 MAX-ACCESS read-only 992 STATUS current 993 DESCRIPTION 994 "The ifIndex Value of the corresponding ifEntry." 995 ::= { frErrEntry 1 } 997 Draft Frame Relay DTE MIB December 1996 999 frErrType OBJECT-TYPE 1000 SYNTAX INTEGER { 1001 unknownError(1), 1002 receiveShort(2), 1003 receiveLong(3), 1004 illegalAddress(4), 1005 unknownAddress(5), 1006 dlcmiProtoErr(6), 1007 dlcmiUnknownIE(7), 1008 dlcmiSequenceErr(8), 1009 dlcmiUnknownRpt(9), 1010 noErrorSinceReset(10) 1011 } 1013 MAX-ACCESS read-only 1014 STATUS current 1015 DESCRIPTION 1016 "The type of error that was last seen on this interface: 1018 receiveShort: frame was not long enough to allow 1019 demultiplexing - the address field was incomplete, or for 1020 virtual circuits using Multiprotocol over Frame Relay, the protocol 1021 identifier was missing or incomplete. 1023 receiveLong: frame exceeded maximum length configured for this interface. 1025 illegalAddress: address field did not match configured format. 1027 unknownAddress: frame received on a virtual circuit which was not active 1028 or administratively disabled. 1030 dlcmiProtoErr: unspecified error occurred when attempting to interpret link 1031 maintenance frame. 1033 dlcmiUnknownIE: link maintenance frame contained an Information Element 1034 type which is not valid for the configured link maintenance 1035 protocol. 1037 dlcmiSequenceErr: link maintenance frame contained a sequence number 1038 number other than the expected value. 1040 dlcmiUnknownRpt: link maintenance frame contained a Report Type Information 1041 Element whose value was not valid for the configured 1042 link maintenance protocol. 1044 Draft Frame Relay DTE MIB December 1996 1046 noErrorSinceReset: no errors have been detected since the last 1047 cold start or warm start." 1048 ::= { frErrEntry 2 } 1050 frErrData OBJECT-TYPE 1051 SYNTAX OCTET STRING (SIZE(1..1600)) 1052 MAX-ACCESS read-only 1053 STATUS current 1054 DESCRIPTION 1055 "An octet string containing as much of the error packet 1056 as possible. As a minimum, it must contain the Q.922 1057 Address or as much as was delivered. It is desirable 1058 to include all header and demultiplexing information." 1059 ::= { frErrEntry 3 } 1061 frErrTime OBJECT-TYPE 1062 SYNTAX TimeStamp 1063 MAX-ACCESS read-only 1064 STATUS current 1065 DESCRIPTION 1066 "The value of sysUpTime at which the error was 1067 detected." 1068 ::= { frErrEntry 4 } 1070 frErrFaults OBJECT-TYPE 1071 SYNTAX Counter32 1072 MAX-ACCESS read-only 1073 STATUS current 1074 DESCRIPTION 1075 "The number of times the interface has gone down since 1076 it was initialized." 1077 ::= { frErrEntry 5 } 1079 frErrFaultTime OBJECT-TYPE 1080 SYNTAX TimeStamp 1081 MAX-ACCESS read-only 1082 STATUS current 1083 DESCRIPTION 1084 "The value of sysUpTime at the time when the interface 1085 was taken down due to excessive errors. Excessive 1086 errors is defined as the time when a DLCMI exceeds the 1088 Draft Frame Relay DTE MIB December 1996 1090 frDlcmiErrorThreshold number of errors within 1091 frDlcmiMonitoredEvents. See FrDlcmiEntry for further 1092 details." 1093 ::= { frErrEntry 6 } 1094 -- 1096 -- Frame Relay Trap Control 1098 frameRelayTrapControl OBJECT IDENTIFIER ::= { frameRelayDTE 4 } 1099 frameRelayTraps OBJECT IDENTIFIER ::= { frameRelayDTE 5 } 1101 frTrapState OBJECT-TYPE 1102 SYNTAX INTEGER { enabled(1), disabled(2) } 1103 MAX-ACCESS read-write 1104 STATUS current 1105 DESCRIPTION 1106 "This variable indicates whether the system produces 1107 the frDLCIStatusChange trap." 1108 DEFVAL { disabled } 1109 ::= { frameRelayTrapControl 1 } 1111 frTrapMaxRate OBJECT-TYPE 1112 SYNTAX INTEGER (0..3600000) 1113 MAX-ACCESS read-write 1114 STATUS current 1115 DESCRIPTION 1116 "This variable indicates the number of milliseconds 1117 that must elapse between trap emissions. If events 1118 occur more rapidly, the impementation may simply fail 1119 to trap, or may queue traps until an appropriate time." 1120 DEFVAL { 0 } -- no minimum elapsed period is specified 1121 ::= { frameRelayTrapControl 2 } 1123 -- Data Link Connection Management Interface Related Traps 1125 frDLCIStatusChange NOTIFICATION-TYPE 1126 OBJECTS { frCircuitState } 1127 STATUS current 1128 DESCRIPTION 1129 "This trap indicates that the indicated Virtual Circuit 1130 has changed state. It has either been created or 1131 invalidated, or has toggled between the active and 1132 inactive states. If, however, the reason for the state 1134 Draft Frame Relay DTE MIB December 1996 1136 change is due to the DLCMI going down, per-DLCI traps 1137 should not be generated." 1138 ::= { frameRelayTraps 1 } 1139 -- conformance information 1141 frConformance OBJECT IDENTIFIER ::= { frameRelayDTE 6 } 1143 frGroups OBJECT IDENTIFIER ::= { frConformance 1 } 1144 frCompliances OBJECT IDENTIFIER ::= { frConformance 2 } 1146 -- compliance statements 1148 frCompliance MODULE-COMPLIANCE 1149 STATUS current 1150 DESCRIPTION 1151 "The compliance statement " 1152 MODULE -- this module 1153 MANDATORY-GROUPS { frPortGroup, frCircuitGroup, frErrGroup } 1154 GROUP frTrapGroup 1155 DESCRIPTION 1156 "This group is optional, and is used for the management 1157 of asynchronous notifications by Frame Relay Systems." 1159 OBJECT frDlcmiRowStatus 1160 MIN-ACCESS read-only 1161 DESCRIPTION 1162 "Row creation is not required for the frDlcmiTable." 1164 OBJECT frCircuitRowStatus 1165 MIN-ACCESS read-only 1166 DESCRIPTION 1167 "Row creation is not required for the frCircuitTable." 1169 ::= { frCompliances 1 } 1171 -- units of conformance 1173 frPortGroup OBJECT-GROUP 1174 OBJECTS { 1175 frDlcmiIfIndex, frDlcmiState, frDlcmiAddress , 1176 frDlcmiAddressLen, frDlcmiPollingInterval, 1177 frDlcmiFullEnquiryInterval, frDlcmiErrorThreshold, 1178 frDlcmiMonitoredEvents, frDlcmiMaxSupportedVCs, 1179 frDlcmiMulticast, frDlcmiStatus, frDlcmiRowStatus 1180 } 1182 Draft Frame Relay DTE MIB December 1996 1184 STATUS current 1185 DESCRIPTION 1186 "The objects necessary to control the Link Management 1187 Interface for a Frame Relay Interface as well as 1188 maintain the error statistics on this interface." 1189 ::= { frGroups 1 } 1191 frCircuitGroup OBJECT-GROUP 1192 OBJECTS { 1193 frCircuitIfIndex, frCircuitDlci, frCircuitState, 1194 frCircuitReceivedFECNs, frCircuitReceivedBECNs, 1195 frCircuitSentFrames, frCircuitSentOctets, 1196 frCircuitReceivedFrames, frCircuitReceivedOctets, 1197 frCircuitCreationTime, frCircuitLastTimeChange, 1198 frCircuitCommittedBurst, frCircuitExcessBurst, 1199 frCircuitThroughput, frCircuitMulticast, frCircuitType, 1200 frCircuitDiscards, frCircuitReceivedDEs, 1201 frCircuitSentDEs, frCircuitLogicalIfIndex, 1202 frCircuitRowStatus 1203 } 1204 STATUS current 1205 DESCRIPTION 1206 "The objects necessary to control the Virtual Circuits 1207 layered onto a Frame Relay Interface." 1208 ::= { frGroups 2 } 1210 frTrapGroup OBJECT-GROUP 1211 OBJECTS { frTrapState, frTrapMaxRate } 1212 STATUS current 1213 DESCRIPTION 1214 "The objects necessary to control a Frame Relay 1215 Interface's notification messages." 1216 ::= { frGroups 3 } 1218 frErrGroup OBJECT-GROUP 1219 OBJECTS { 1220 frErrIfIndex, frErrType, frErrData, frErrTime, 1221 frErrFaults, frErrFaultTime 1222 } 1223 STATUS current 1224 DESCRIPTION 1225 "Objects designed to assist in debugging Frame Relay 1226 Interfaces." 1227 ::= { frGroups 4 } 1229 Draft Frame Relay DTE MIB December 1996 1231 END 1232 Draft Frame Relay DTE MIB December 1996 1234 6. Security Issues 1236 Security issues for this MIB are entirely covered by the SNMP 1237 Security Architecture, and have not been expanded within the 1238 contents of this MIB. 1240 7. Acknowledgments 1242 This document was originally produced by the IP Over Large 1243 Public Data Networks (IPLPDN) Working Group, and has since 1244 been carried on in the PPP Working Group, sort of. 1246 Special thanks to James Watt of Newbridge Networks for his 1247 fine suggestions and pastable text. 1249 8. Authors' Addresses 1251 Caralyn Brown 1252 Cadia Networks, Inc. 1253 1 Corporate Dirve 1254 Andover, Massachusetts 01810 1255 Telephone: +1 508 689 2400 x133 1256 E-Mail: cbrown@cadia.com 1258 Fred Baker 1259 Cisco Systems 1260 519 Lado Drive 1261 Santa Barbara, California 93111 1262 Telephone +1 408 526 4257 1263 E-Mail: fred@cisco.com 1265 Draft Frame Relay DTE MIB December 1996 1267 9. References 1269 [1] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., 1270 and S. Waldbusser, "Structure of Management Information 1271 for Version 2 of the Simple Network Management Protocol 1272 (SNMPv2)", RFC 1902, January 1996. 1274 [2] McCloghrie, K., and M. Rose, Editors, "Management 1275 Information Base for Network Management of TCP/IP-based 1276 internets: MIB-II", STD 17, RFC 1213, Hughes LAN Systems, 1277 Performance Systems International, March 1991. 1279 [3] Case, J., Fedor, M., Schoffstall, M., and J. Davin. " A 1280 Simple Network Management Protocol (SNMP)", STD 15, RFC 1281 1157, SNMP Research, Performance Systems International, 1282 MIT Lab for Computer Science, May 1990. 1284 [4] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., 1285 and S. Waldbusser, "Protocol Operations for Version 2 of 1286 the Simple Network Management Protocol (SNMPv2)", RFC 1287 1905, January 1996. 1289 [5] McCloghrie, K. and F. Kastenholz, "Evolution of the 1290 Interfaces Group of MIB-II", RFC 1573, Hughes LAN 1291 Systems, FTP Software, January 1994. 1293 [6] T. Bradley, C. Brown, A. Malis, "Multiprotocol 1294 Interconnect over Frame Relay", RFC 1490, 07/26/1993. 1296 [7] International Telegraph and Telephone Consultative 1297 Committee, "ISDN Data Link Layer Specification for Frame 1298 Mode Bearer Services", CCITT Recommendation Q.922, 19 1299 April 1991. 1301 [8] American National Standard For Telecommunications - 1302 Integrated Services Digital Network - Frame Relay Bearer 1303 Service - Architectural Framework and Service 1304 Description, ANSI T1.606-1991, 18 June 1991. 1306 [9] American National Standard For Telecommunications - 1307 Integrated Services Digital Network - Digital Subscriber 1308 Signalling System No. 1 - Signaling Specification for 1309 Frame Relay Bearer Service, ANSI T1.617-1991, 18 June 1310 1991. 1312 Draft Frame Relay DTE MIB December 1996 1314 [10] American National Standard For Telecommunications - 1315 Integrated Services Digital Network - Core Aspects of 1316 Frame Protocol for Use with Frame Relay Bearer Service, 1317 ANSI T1.618-1991, 18 June 1991. 1319 Draft Frame Relay DTE MIB December 1996 1321 Table of Contents 1323 1 Status of this Memo ................................... 1 1324 2 Abstract .............................................. 2 1325 3 The SNMPv2 Network Management Framework ............... 2 1326 4 Overview .............................................. 4 1327 4.1 Frame Relay Operational Model ....................... 4 1328 4.2 Textual Conventions ................................. 8 1329 4.3 Structure of MIB .................................... 8 1330 5 Definitions ........................................... 9 1331 5.1 Data Link Connection Management Interface ........... 11 1332 5.2 Circuit Table ....................................... 16 1333 5.3 Error Table ......................................... 25 1334 5.4 Trap Management ..................................... 28 1335 6 Security Issues ....................................... 32 1336 7 Acknowledgments ....................................... 32 1337 8 Authors' Addresses .................................... 32 1338 9 References ............................................ 33