1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
1001
1002
1003
1004
1005
1006
1007
1008
1009
1010
1011
1012
1013
1014
1015
1016
1017
1018
1019
1020
1021
1022
1023
1024
1025
1026
1027
1028
1029
1030
1031
1032
1033
1034
1035
1036
1037
1038
1039
1040
1041
1042
1043
1044
1045
1046
1047
1048
1049
1050
1051
1052
1053
1054
1055
1056
1057
1058
1059
1060
1061
|
<pre>Network Working Group C. Brown
Request for Comments: 1315 Wellfleet Communications, Inc.
F. Baker
Advanced Computer Communications
C. Carvalho
Advanced Computer Communications
April 1992
<span class="h1">Management Information Base for Frame Relay DTEs</span>
Status of this Memo
This RFC specifies an IAB standards track protocol for the Internet
community, and requests discussion and suggestions for improvements.
Please refer to the current edition of the "IAB Official Protocol
Standards" for the standardization state and status of this protocol.
Distribution of this memo is unlimited.
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.
Table of Contents
<a href="#section-1">1</a>. The Network Management Framework ............................ <a href="#page-2">2</a>
<a href="#section-2">2</a>. Objects ..................................................... <a href="#page-2">2</a>
<a href="#section-2.1">2.1</a> Format of Definitions ...................................... <a href="#page-3">3</a>
<a href="#section-3">3</a>. Overview .................................................... <a href="#page-3">3</a>
<a href="#section-3.1">3.1</a> Frame Relay Operational Model .............................. <a href="#page-3">3</a>
<a href="#section-3.2">3.2</a> Textual Conventions ........................................ <a href="#page-3">3</a>
<a href="#section-3.3">3.3</a> Structure of MIB ........................................... <a href="#page-3">3</a>
<a href="#section-4">4</a>. Definitions ................................................. <a href="#page-4">4</a>
<a href="#section-4.1">4.1</a> Data Link Connection Management Interface .................. <a href="#page-4">4</a>
<a href="#section-4.2">4.2</a> Circuit Table .............................................. <a href="#page-9">9</a>
<a href="#section-4.3">4.3</a> Error Table ................................................ <a href="#page-14">14</a>
<a href="#section-5">5</a>. Acknowledgements ............................................ <a href="#page-17">17</a>
<a href="#section-6">6</a>. References .................................................. <a href="#page-17">17</a>
<a href="#section-7">7</a>. Security Considerations...................................... <a href="#page-18">18</a>
<a href="#section-8">8</a>. Authors' Addresses........................................... <a href="#page-19">19</a>
<span class="grey">Brown, Baker & Carvalho [Page 1]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span>
<span class="grey"><a href="./rfc1315">RFC 1315</a> Frame Relay DTE MIB April 1992</span>
<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. The Network Management Framework</span>
The Internet-standard Network Management Framework consists of three
components. They are:
<a href="./rfc1155">RFC 1155</a> which defines the SMI, the mechanisms used for describing
and naming objects for the purpose of management. <a href="./rfc1212">RFC 1212</a> defines a
more concise description mechanism, which is wholly consistent with
the SMI.
<a href="./rfc1156">RFC 1156</a> which defines MIB-I, the core set of managed objects for the
Internet suite of protocols. <a href="./rfc1213">RFC 1213</a> defines MIB-II, an evolution
of MIB-I based on implementation experience and new operational
requirements.
<a href="./rfc1157">RFC 1157</a> which defines the SNMP, the protocol used for network access
to managed objects.
The Framework permits new objects to be defined for the purpose of
experimentation and evaluation.
<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. Objects</span>
Managed objects are accessed via a virtual information store, termed
the Management Information Base or MIB. Objects in the MIB are
defined using the subset of Abstract Syntax Notation One (ASN.1) [<a href="#ref-7" title=" International Organization for Standardization">7</a>]
defined in the SMI. In particular, each object has a name, a syntax,
and an encoding. The name is an object identifier, an
administratively assigned name, which specifies an object type. The
object type together with an object instance serves to uniquely
identify a specific instantiation of the object. For human
convenience, we often use a textual string, termed the OBJECT
DESCRIPTOR, to also refer to the object type.
The syntax of an object type defines the abstract data structure
corresponding to that object type. The ASN.1 language is used for
this purpose. However, the SMI [<a href="#ref-3" title=""Structure and Identification of Management Information for TCP/IP-based internets"">3</a>] purposely restricts the ASN.1
constructs which may be used. These restrictions are explicitly made
for simplicity.
The encoding of an object type is simply how that object type is
represented using the object type's syntax. Implicitly tied to the
notion of an object type's syntax and encoding is how the object type
is represented when being transmitted on the network.
The SMI specifies the use of the basic encoding rules of ASN.1 [<a href="#ref-8" title=" International Standard 8825">8</a>],
subject to the additional requirements imposed by the SNMP.
<span class="grey">Brown, Baker & Carvalho [Page 2]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span>
<span class="grey"><a href="./rfc1315">RFC 1315</a> Frame Relay DTE MIB April 1992</span>
<span class="h3"><a class="selflink" id="section-2.1" href="#section-2.1">2.1</a>. Format of Definitions</span>
<a href="#section-4">Section 4</a> contains contains the specification of all object types
contained in this MIB module. The object types are defined using the
conventions defined in the SMI, as amended by the extensions
specified in [<a href="#ref-9" title=""Concise MIB Definitions"">9</a>,<a href="#ref-10" title=""A Convention for Defining Traps for use with the SNMP"">10</a>].
<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. Overview</span>
<span class="h3"><a class="selflink" id="section-3.1" href="#section-3.1">3.1</a>. Frame Relay Operational Model</span>
For the purposes of understanding this document, Frame Relay is
viewed as a multi-access media, not as a group of point-to-point
connections. This model proposes that Frame Relay is a single
interface to the network (physical connection) with many destinations
or neighbors (virtual connections). This view enables a network
manager the ability to group all virtual connections with their
corresponding physical connection thereby allowing simpler
diagnostics and trouble shooting.
<span class="h3"><a class="selflink" id="section-3.2" href="#section-3.2">3.2</a>. Textual Conventions</span>
Several new data types are introduced as a textual convention in this
MIB document. These textual conventions enhance the readability of
the specification and can ease comparison with other specifications
if appropriate. It should be noted that the introduction of the
these textual conventions has no effect on either the syntax nor the
semantics of any managed objects. The use of these is merely an
artifact of the explanatory method used. Objects defined in terms of
one of these methods are always encoded by means of the rules that
define the primitive type. Hence, no changes to the SMI or the SNMP
are necessary to accommodate these textual conventions which are
adopted merely for the convenience of readers and writers in pursuit
of the elusive goal of clear, concise, and unambiguous MIB documents.
The new data types are Index and DLCI. Index refers to the range
1..ifNumber, and is used to establish the correspondence between
ifEntries and Frame Relay Interfaces. DLCI refers to the range
0..DLCINumber, and is used to refer to the valid Data Link Connection
Indices. DLCINumber is, by definition, the largest possible DLCI
value possible under the configured Q.922 Address Format.
<span class="h3"><a class="selflink" id="section-3.3" href="#section-3.3">3.3</a>. Structure of MIB</span>
The MIB is composed of three groups, one defining the Data Link
Connection Management Interface (DLCMI), one describing the Circuits,
and a third describing errors.
<span class="grey">Brown, Baker & Carvalho [Page 3]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span>
<span class="grey"><a href="./rfc1315">RFC 1315</a> Frame Relay DTE MIB April 1992</span>
During normal operation, Frame Relay virtual circuits will be added,
deleted and change availability. The occurrence of such changes is
of interest to the network manager and therefore, one trap is
defined, intended to be corollary to the SNMP "Link Up" and "Link
Down" traps.
<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Definitions</span>
<a href="./rfc1315">RFC1315</a>-MIB DEFINITIONS ::= BEGIN
IMPORTS
OBJECT-TYPE
FROM <a href="./rfc1212">RFC-1212</a>
transmission
FROM <a href="./rfc1213">RFC1213</a>-MIB
TimeTicks
FROM <a href="./rfc1155">RFC-1155</a>
TRAP-TYPE
FROM <a href="./rfc1215">RFC-1215</a>;
-- Frame Relay DTE MIB
frame-relay OBJECT IDENTIFIER ::= { transmission 32 }
--
-- the range of ifIndex
--
Index ::= INTEGER -- 1..ifNumber
--
-- the range of a Data Link Connection Identifier
--
DLCI ::= INTEGER -- 0..DLCINumber
-- Data Link Connection Management Interface
-- The variables that configure the DLC Management Interface.
frDlcmiTable OBJECT-TYPE
SYNTAX SEQUENCE OF FrDlcmiEntry
ACCESS not-accessible
STATUS mandatory
DESCRIPTION
"The Parameters for the Data Link Connection Management
Interface for the frame relay service on this
interface."
REFERENCE
<span class="grey">Brown, Baker & Carvalho [Page 4]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span>
<span class="grey"><a href="./rfc1315">RFC 1315</a> Frame Relay DTE MIB April 1992</span>
"Draft American National Standard T1.617-1991, Annex D"
::= { frame-relay 1 }
frDlcmiEntry OBJECT-TYPE
SYNTAX FrDlcmiEntry
ACCESS not-accessible
STATUS mandatory
DESCRIPTION
"The Parameters for a particular Data Link Con-
nection Management Interface."
INDEX { frDlcmiIfIndex }
::= { frDlcmiTable 1 }
FrDlcmiEntry ::=
SEQUENCE {
frDlcmiIfIndex
Index,
frDlcmiState
INTEGER,
frDlcmiAddress
INTEGER,
frDlcmiAddressLen
INTEGER,
frDlcmiPollingInterval
INTEGER,
frDlcmiFullEnquiryInterval
INTEGER,
frDlcmiErrorThreshold
INTEGER,
frDlcmiMonitoredEvents
INTEGER,
frDlcmiMaxSupportedVCs
INTEGER,
frDlcmiMulticast
INTEGER
}
frDlcmiIfIndex OBJECT-TYPE
SYNTAX Index
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The ifIndex value of the corresponding ifEn-
try."
::= { frDlcmiEntry 1 }
<span class="grey">Brown, Baker & Carvalho [Page 5]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span>
<span class="grey"><a href="./rfc1315">RFC 1315</a> Frame Relay DTE MIB April 1992</span>
frDlcmiState OBJECT-TYPE
SYNTAX INTEGER {
noLmiConfigured (1),
lmiRev1 (2),
ansiT1-617-D (3), -- ANSI T1.617 Annex D
ansiT1-617-B (4) -- ANSI T1.617 Annex B
}
ACCESS read-write
STATUS mandatory
DESCRIPTION
"This variable states which Data Link Connec-
tion Management scheme is active (and by impli-
cation, what DLCI it uses) on the Frame Relay
interface."
REFERENCE
"Draft American National Standard T1.617-1991"
::= { frDlcmiEntry 2 }
frDlcmiAddress OBJECT-TYPE
SYNTAX INTEGER {
q921 (1), -- 13 bit DLCI
q922March90 (2), -- 11 bit DLCI
q922November90 (3), -- 10 bit DLCI
q922 (4) -- Final Standard
}
ACCESS read-write
STATUS mandatory
DESCRIPTION
"This variable states which address format is
in use on the Frame Relay interface."
::= { frDlcmiEntry 3 }
frDlcmiAddressLen OBJECT-TYPE
SYNTAX INTEGER {
two-octets (2),
three-octets (3),
four-octets (4)
}
ACCESS read-write
STATUS mandatory
DESCRIPTION
"This variable states which address length in
octets. In the case of Q922 format, the length
indicates the entire length of the address in-
cluding the control portion."
<span class="grey">Brown, Baker & Carvalho [Page 6]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span>
<span class="grey"><a href="./rfc1315">RFC 1315</a> Frame Relay DTE MIB April 1992</span>
::= { frDlcmiEntry 4 }
frDlcmiPollingInterval OBJECT-TYPE
SYNTAX INTEGER (5..30)
ACCESS read-write
STATUS mandatory
DESCRIPTION
"This is the number of seconds between succes-
sive status enquiry messages."
REFERENCE
"Draft American National Standard T1.617-1991,
Section D.7 Timer T391."
DEFVAL { 10 }
::= { frDlcmiEntry 5 }
frDlcmiFullEnquiryInterval OBJECT-TYPE
SYNTAX INTEGER (1..255)
ACCESS read-write
STATUS mandatory
DESCRIPTION
"Number of status enquiry intervals that pass
before issuance of a full status enquiry mes-
sage."
REFERENCE
"Draft American National Standard T1.617-1991,
Section D.7 Counter N391."
DEFVAL { 6 }
::= { frDlcmiEntry 6 }
frDlcmiErrorThreshold OBJECT-TYPE
SYNTAX INTEGER (1..10)
ACCESS read-write
STATUS mandatory
DESCRIPTION
"This is the maximum number of unanswered
Status Enquiries the equipment shall accept be-
fore declaring the interface down."
REFERENCE
"Draft American National Standard T1.617-1991,
Section D.5.1 Counter N392."
DEFVAL { 3 }
::= { frDlcmiEntry 7 }
<span class="grey">Brown, Baker & Carvalho [Page 7]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-8" ></span>
<span class="grey"><a href="./rfc1315">RFC 1315</a> Frame Relay DTE MIB April 1992</span>
frDlcmiMonitoredEvents OBJECT-TYPE
SYNTAX INTEGER (1..10)
ACCESS read-write
STATUS mandatory
DESCRIPTION
"This is the number of status polling intervals
over which the error threshold is counted. For
example, if within 'MonitoredEvents' number of
events the station receives 'ErrorThreshold'
number of errors, the interface is marked as
down."
REFERENCE
"Draft American National Standard T1.617-1991,
Section D.5.2 Counter N393."
DEFVAL { 4 }
::= { frDlcmiEntry 8 }
frDlcmiMaxSupportedVCs OBJECT-TYPE
SYNTAX INTEGER
ACCESS read-write
STATUS mandatory
DESCRIPTION
"The maximum number of Virtual Circuits allowed
for this interface. Usually dictated by the
Frame Relay network.
In response to a SET, if a value less than zero
or higher than the agent's maximal capability
is configured, the agent should respond bad-
Value"
::= { frDlcmiEntry 9 }
frDlcmiMulticast OBJECT-TYPE
SYNTAX INTEGER {
nonBroadcast (1),
broadcast (2)
}
ACCESS read-write
STATUS mandatory
DESCRIPTION
"This indicates whether the Frame Relay inter-
face is using a multicast service."
::= { frDlcmiEntry 10 }
<span class="grey">Brown, Baker & Carvalho [Page 8]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-9" ></span>
<span class="grey"><a href="./rfc1315">RFC 1315</a> Frame Relay DTE MIB April 1992</span>
-- A Frame Relay service is a multiplexing service. Data
-- Link Connection Identifiers enumerate virtual circuits
-- (permanent or dynamic) which are layered onto the underlying
-- circuit, represented by ifEntry. Therefore, each of the entries
-- in the Standard MIB's Interface Table with an IfType of
-- Frame Relay represents a Q.922 interface. Zero or more
-- virtual circuits are layered onto this interface and provide
-- interconnection with various remote destinations.
-- Each such virtual circuit is represented by an entry in the
-- circuit table.
-- Circuit Table
-- The table describing the use of the DLCIs attached to
-- each Frame Relay Interface.
frCircuitTable OBJECT-TYPE
SYNTAX SEQUENCE OF FrCircuitEntry
ACCESS not-accessible
STATUS mandatory
DESCRIPTION
"A table containing information about specific Data
Link Connection Identifiers and corresponding virtual
circuits."
::= { frame-relay 2 }
frCircuitEntry OBJECT-TYPE
SYNTAX FrCircuitEntry
ACCESS not-accessible
STATUS mandatory
DESCRIPTION
"The information regarding a single Data Link
Connection Identifier."
INDEX { frCircuitIfIndex, frCircuitDlci }
::= { frCircuitTable 1 }
FrCircuitEntry ::=
SEQUENCE {
frCircuitIfIndex
Index,
frCircuitDlci
DLCI,
frCircuitState
INTEGER,
frCircuitReceivedFECNs
Counter,
frCircuitReceivedBECNs
<span class="grey">Brown, Baker & Carvalho [Page 9]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-10" ></span>
<span class="grey"><a href="./rfc1315">RFC 1315</a> Frame Relay DTE MIB April 1992</span>
Counter,
frCircuitSentFrames
Counter,
frCircuitSentOctets
Counter,
frCircuitReceivedFrames
Counter,
frCircuitReceivedOctets
Counter,
frCircuitCreationTime
TimeTicks,
frCircuitLastTimeChange
TimeTicks,
frCircuitCommittedBurst
INTEGER,
frCircuitExcessBurst
INTEGER,
frCircuitThroughput
INTEGER
}
frCircuitIfIndex OBJECT-TYPE
SYNTAX Index
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The ifIndex Value of the ifEntry this virtual
circuit is layered onto."
::= { frCircuitEntry 1 }
frCircuitDlci OBJECT-TYPE
SYNTAX DLCI
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The Data Link Connection Identifier for this
virtual circuit."
REFERENCE
"Draft American National Standard T1.618-1991,
<a href="#section-3.3.6">Section 3.3.6</a>"
::= { frCircuitEntry 2 }
<span class="grey">Brown, Baker & Carvalho [Page 10]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-11" ></span>
<span class="grey"><a href="./rfc1315">RFC 1315</a> Frame Relay DTE MIB April 1992</span>
frCircuitState OBJECT-TYPE
SYNTAX INTEGER {
invalid (1),
active (2),
inactive (3)
}
ACCESS read-write
STATUS mandatory
DESCRIPTION
"Indicates whether the particular virtual cir-
cuit is operational. In the absence of a Data
Link Connection Management Interface, virtual
circuit entries (rows) may be created by set-
ting virtual circuit state to 'active', or
deleted by changing Circuit state to 'invalid'.
Whether or not the row actually disappears is
left to the implementation, so this object may
actually read as 'invalid' for some arbitrary
length of time. It is also legal to set the
state of a virtual circuit to 'inactive' to
temporarily disable a given circuit."
DEFVAL { active }
::= { frCircuitEntry 3 }
frCircuitReceivedFECNs OBJECT-TYPE
SYNTAX Counter
ACCESS read-only
STATUS mandatory
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,
<a href="#section-3.3.3">Section 3.3.3</a>"
::= { frCircuitEntry 4 }
frCircuitReceivedBECNs OBJECT-TYPE
SYNTAX Counter
ACCESS read-only
STATUS mandatory
DESCRIPTION
"Number of frames received from the network in-
dicating backward congestion since the virtual
circuit was created."
<span class="grey">Brown, Baker & Carvalho [Page 11]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-12" ></span>
<span class="grey"><a href="./rfc1315">RFC 1315</a> Frame Relay DTE MIB April 1992</span>
REFERENCE
"Draft American National Standard T1.618-1991,
<a href="#section-3.3.4">Section 3.3.4</a>"
::= { frCircuitEntry 5 }
frCircuitSentFrames OBJECT-TYPE
SYNTAX Counter
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The number of frames sent from this virtual
circuit since it was created."
::= { frCircuitEntry 6 }
frCircuitSentOctets OBJECT-TYPE
SYNTAX Counter
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The number of octets sent from this virtual
circuit since it was created."
::= { frCircuitEntry 7 }
frCircuitReceivedFrames OBJECT-TYPE
SYNTAX Counter
ACCESS read-only
STATUS mandatory
DESCRIPTION
"Number of frames received over this virtual
circuit since it was created."
::= { frCircuitEntry 8 }
frCircuitReceivedOctets OBJECT-TYPE
SYNTAX Counter
ACCESS read-only
STATUS mandatory
DESCRIPTION
"Number of octets received over this virtual
circuit since it was created."
::= { frCircuitEntry 9 }
<span class="grey">Brown, Baker & Carvalho [Page 12]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-13" ></span>
<span class="grey"><a href="./rfc1315">RFC 1315</a> Frame Relay DTE MIB April 1992</span>
frCircuitCreationTime OBJECT-TYPE
SYNTAX TimeTicks
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The value of sysUpTime when the virtual cir-
cuit was created, whether by the Data Link Con-
nection Management Interface or by a SetRe-
quest."
::= { frCircuitEntry 10 }
frCircuitLastTimeChange OBJECT-TYPE
SYNTAX TimeTicks
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The value of sysUpTime when last there was a
change in the virtual circuit state"
::= { frCircuitEntry 11 }
frCircuitCommittedBurst OBJECT-TYPE
SYNTAX INTEGER
ACCESS read-write
STATUS mandatory
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
"Draft American National Standard T1.617-1991,
<a href="#section-6.5.19">Section 6.5.19</a>"
DEFVAL { 0 } -- the default indicates no commitment
::= { frCircuitEntry 12 }
frCircuitExcessBurst OBJECT-TYPE
SYNTAX INTEGER
ACCESS read-write
STATUS mandatory
DESCRIPTION
"This variable indicates the maximum amount of
uncommitted data bits that the network will at-
<span class="grey">Brown, Baker & Carvalho [Page 13]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-14" ></span>
<span class="grey"><a href="./rfc1315">RFC 1315</a> Frame Relay DTE MIB April 1992</span>
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
"Draft American National Standard T1.617-1991,
<a href="#section-6.5.19">Section 6.5.19</a>"
::= { frCircuitEntry 13 }
frCircuitThroughput OBJECT-TYPE
SYNTAX INTEGER
ACCESS read-write
STATUS mandatory
DESCRIPTION
"Throughput is the average number of 'Frame Re-
lay Information Field' bits transferred per
second across a user network interface in one
direction, measured over the measurement inter-
val.
If the configured committed burst rate and
throughput are both non-zero, the measurement
interval
T=frCircuitCommittedBurst/frCircuitThroughput.
If the configured committed burst rate and
throughput are both zero, the measurement in-
terval
T=frCircuitExcessBurst/ifSpeed."
REFERENCE
"Draft American National Standard T1.617-1991,
<a href="#section-6.5.19">Section 6.5.19</a>"
DEFVAL {0} -- the default value of Throughput is
-- "no commitment".
::= { frCircuitEntry 14 }
-- Error Table
-- The table describing errors encountered on each Frame
-- Relay Interface.
frErrTable OBJECT-TYPE
SYNTAX SEQUENCE OF FrErrEntry
ACCESS not-accessible
<span class="grey">Brown, Baker & Carvalho [Page 14]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-15" ></span>
<span class="grey"><a href="./rfc1315">RFC 1315</a> Frame Relay DTE MIB April 1992</span>
STATUS mandatory
DESCRIPTION
"A table containing information about Errors on the
Frame Relay interface."
::= { frame-relay 3 }
frErrEntry OBJECT-TYPE
SYNTAX FrErrEntry
ACCESS not-accessible
STATUS mandatory
DESCRIPTION
"The error information for a single frame relay
interface."
INDEX { frErrIfIndex }
::= { frErrTable 1 }
FrErrEntry ::=
SEQUENCE {
frErrIfIndex
Index,
frErrType
INTEGER,
frErrData
OCTET STRING,
frErrTime
TimeTicks
}
frErrIfIndex OBJECT-TYPE
SYNTAX Index
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The ifIndex Value of the corresponding ifEn-
try."
::= { frErrEntry 1 }
frErrType OBJECT-TYPE
SYNTAX INTEGER {
unknownError(1),
receiveShort(2),
receiveLong(3),
<span class="grey">Brown, Baker & Carvalho [Page 15]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-16" ></span>
<span class="grey"><a href="./rfc1315">RFC 1315</a> Frame Relay DTE MIB April 1992</span>
illegalDLCI(4),
unknownDLCI(5),
dlcmiProtoErr(6),
dlcmiUnknownIE(7),
dlcmiSequenceErr(8),
dlcmiUnknownRpt(9),
noErrorSinceReset(10)
}
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The type of error that was last seen on this
interface."
::= { frErrEntry 2 }
frErrData OBJECT-TYPE
SYNTAX OCTET STRING
ACCESS read-only
STATUS mandatory
DESCRIPTION
"An octet string containing as much of the er-
ror packet as possible. As a minimum, it must
contain the Q.922 Address or as much as was
delivered. It is desirable to include all in-
formation up to the PDU."
::= { frErrEntry 3 }
frErrTime OBJECT-TYPE
SYNTAX TimeTicks
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The value of sysUpTime at which the error was
detected."
::= { frErrEntry 4 }
-- Frame Relay Globals
frame-relay-globals OBJECT IDENTIFIER ::= { frame-relay 4 }
frTrapState OBJECT-TYPE
SYNTAX INTEGER { enabled(1), disabled(2) }
ACCESS read-write
<span class="grey">Brown, Baker & Carvalho [Page 16]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-17" ></span>
<span class="grey"><a href="./rfc1315">RFC 1315</a> Frame Relay DTE MIB April 1992</span>
STATUS mandatory
DESCRIPTION
"This variable indicates whether the system
produces the frDLCIStatusChange trap."
DEFVAL { disabled }
::= { frame-relay-globals 1 }
-- Data Link Connection Management Interface Related Traps
frDLCIStatusChange TRAP-TYPE
ENTERPRISE frame-relay
VARIABLES { frCircuitIfIndex, frCircuitDlci, frCircuitState }
DESCRIPTION
"This trap indicates that the indicated Virtual
Circuit has changed state. It has either been
created or invalidated, or has toggled between
the active and inactive states."
::= 1
END
<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. Acknowledgements</span>
This document was produced by the IP Over Large Public Data Networks
(IPLPDN) Working Group.
The following people provided additional comments and suggestions:
Art Berggreen of Advanced Computer Communications, and Jim Philippou
of Xyplex Communications.
<span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. References</span>
[<a id="ref-1">1</a>] Cerf, V., "IAB Recommendations for the Development of Internet
Network Management Standards", <a href="./rfc1052">RFC 1052</a>, NRI, April 1988.
[<a id="ref-2">2</a>] Cerf, V., "Report of the Second Ad Hoc Network Management Review
Group", <a href="./rfc1109">RFC 1109</a>, NRI, August 1989.
[<a id="ref-3">3</a>] Rose M., and K. McCloghrie, "Structure and Identification of
Management Information for TCP/IP-based internets", <a href="./rfc1155">RFC 1155</a>,
Performance Systems International, Hughes LAN Systems, May 1990.
[<a id="ref-4">4</a>] McCloghrie K., and M. Rose, "Management Information Base for
Network Management of TCP/IP-based internets", <a href="./rfc1156">RFC 1156</a>, Hughes
LAN Systems, Performance Systems International, May 1990.
<span class="grey">Brown, Baker & Carvalho [Page 17]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-18" ></span>
<span class="grey"><a href="./rfc1315">RFC 1315</a> Frame Relay DTE MIB April 1992</span>
[<a id="ref-5">5</a>] Case, J., Fedor, M., Schoffstall, M., and J. Davin, "Simple
Network Management Protocol", <a href="./rfc1157">RFC 1157</a>, SNMP Research,
Performance Systems International, Performance Systems
International, MIT Laboratory for Computer Science, May 1990.
[<a id="ref-6">6</a>] McCloghrie K., and M. Rose, Editors, "Management Information Base
for Network Management of TCP/IP-based internets", <a href="./rfc1213">RFC 1213</a>,
Performance Systems International, March 1991.
[<a id="ref-7">7</a>] Information processing systems - Open Systems Interconnection -
Specification of Abstract Syntax Notation One (ASN.1),
International Organization for Standardization, International
Standard 8824, December 1987.
[<a id="ref-8">8</a>] Information processing systems - Open Systems Interconnection -
Specification of Basic Encoding Rules for Abstract Notation One
(ASN.1), International Organization for Standardization,
International Standard 8825, December 1987.
[<a id="ref-9">9</a>] Rose, M., and K. McCloghrie, Editors, "Concise MIB Definitions",
<a href="./rfc1212">RFC 1212</a>, Performance Systems International, Hughes LAN Systems,
March 1991.
[<a id="ref-10">10</a>] Rose, M., Editor, "A Convention for Defining Traps for use with
the SNMP", <a href="./rfc1215">RFC 1215</a>, Performance Systems International, March
1991.
<span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. Security Considerations</span>
Security issues are not discussed in this memo.
<span class="grey">Brown, Baker & Carvalho [Page 18]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-19" ></span>
<span class="grey"><a href="./rfc1315">RFC 1315</a> Frame Relay DTE MIB April 1992</span>
<span class="h2"><a class="selflink" id="section-8" href="#section-8">8</a>. Authors' Addresses</span>
Caralyn Brown
Wellfleet Communications, Inc.
15 Crosby Drive
Bedford, Massachusetts 01730
Phone: (617) 275-2400
EMail: cbrown@wellfleet.com
Fred Baker
Advanced Computer Communications
315 Bollay Drive
Sannta Barbara, California 93117
Phone: (805) 685-4455
EMail: fbaker@acc.com
Charles Carvalho
Advanced Computer Communications
315 Bollay Drive
Sannta Barbara, California 93117
Phone: (805) 685-4455
EMail: charles@acc.com
Brown, Baker & Carvalho [Page 19]
</pre>
|
