1
FRNETSERV-MIB DEFINITIONS ::= BEGIN
4
MODULE-IDENTITY, OBJECT-TYPE,
5
NOTIFICATION-TYPE, transmission,
6
Counter32, Integer32 FROM SNMPv2-SMI
7
TimeStamp, RowStatus FROM SNMPv2-TC
8
MODULE-COMPLIANCE, OBJECT-GROUP,
9
NOTIFICATION-GROUP FROM SNMPv2-CONF
10
InterfaceIndex, ifIndex FROM IF-MIB
11
SnmpAdminString FROM SNMP-FRAMEWORK-MIB;
13
frnetservMIB MODULE-IDENTITY
14
LAST-UPDATED "200009280000Z" -- September 28, 2000
15
ORGANIZATION "IETF Frame Relay Service MIB Working Group"
18
http://www.ietf.org/html.charters/frnetmib-charter
20
frnetmib@sunroof.eng.sun.com
24
frnetmib-request@sunroof.eng.sun.com
26
ftp://ftp.ietf.org/ietf-mail-archive/frnetmib
30
Email: Andy.Malis@vivacenetworks.com
32
WG editor: Kenneth Rehbehn
34
Email: krehbehn@megisto.com
36
Co-author: David Fowler
38
EMail: fowler@syndesis.com"
41
"The MIB module to describe generic objects for
42
Frame Relay Network Service."
47
REVISION "200009280000Z"
49
"Published as RFC 2954.
51
The major new features of this revision include:
53
o Support for read-write capability to
54
provision switch components providing service,
56
o Support for cross-connection via a frame relay
57
to ATM service interworking function,
59
o Support for frame relay fragmentation,
61
o Additional frame counters to track frame
64
Refer to Appendix A for a comprehensive list of
65
changes since RFC 1604."
67
REVISION "199311161200Z"
69
"Published as RFC 1604."
70
::= { transmission 44 }
74
OBJECT IDENTIFIER ::= { frnetservMIB 1 }
77
OBJECT IDENTIFIER ::= { frnetservMIB 2 }
80
OBJECT IDENTIFIER ::= { frnetservTraps 0 }
83
-- The Frame Relay Service Logical Port
85
frLportTable OBJECT-TYPE
86
SYNTAX SEQUENCE OF FrLportEntry
87
MAX-ACCESS not-accessible
90
"The Frame Relay Logical Port Information table is
91
an interface-specific addendum to the generic
92
ifTable of the Interface MIB."
93
::= { frnetservObjects 1 }
95
frLportEntry OBJECT-TYPE
97
MAX-ACCESS not-accessible
100
"An entry in the Frame Relay Logical Port
103
::= { frLportTable 1 }
107
frLportNumPlan INTEGER,
108
frLportContact SnmpAdminString,
109
frLportLocation SnmpAdminString,
111
frLportAddrDLCILen INTEGER,
112
frLportVCSigProtocol INTEGER,
113
frLportVCSigPointer OBJECT IDENTIFIER,
114
frLportDLCIIndexValue Integer32,
115
frLportTypeAdmin INTEGER,
116
frLportVCSigProtocolAdmin INTEGER,
117
frLportFragControl INTEGER,
118
frLportFragSize Integer32
123
frLportNumPlan OBJECT-TYPE
133
"The value of this object identifies the network
134
address numbering plan for this UNI/NNI logical
135
port. The network address is the object
136
ifPhysAddress. The value none(4) implies that
137
there is no ifPhysAddress. The FRS agent will
138
return an octet string of zero length for
139
ifPhysAddress. The value other(1) means that an
140
address has been assigned to this interface, but
141
the numbering plan is not enumerated here."
142
REFERENCE "E.164 [29]
144
::= { frLportEntry 1 }
146
frLportContact OBJECT-TYPE
147
SYNTAX SnmpAdminString
151
"The value of this object identifies the network
152
contact for this UNI/NNI logical port."
153
::= { frLportEntry 2 }
155
frLportLocation OBJECT-TYPE
156
SYNTAX SnmpAdminString
160
"The value of this object identifies the frame
161
relay network location for this UNI/NNI logical
163
::= { frLportEntry 3 }
165
frLportType OBJECT-TYPE
175
"The value of this object identifies the type of
176
network interface for this logical port."
177
::= { frLportEntry 4 }
179
frLportAddrDLCILen OBJECT-TYPE
182
threeOctets10Bits(2),
183
threeOctets16Bits(3),
191
"The value of this object identifies the Q.922
192
Address field length and DLCI length for this
193
UNI/NNI logical port."
194
REFERENCE "Q.922 [25]"
195
::= { frLportEntry 5 }
197
frLportVCSigProtocol OBJECT-TYPE
208
"The value of this object identifies the Local
209
In-Channel Signaling Protocol that is used for
210
this frame relay UNI/NNI logical port.
212
none(1): Interface does not use a PVC
215
lmi(2): Interface operates the Stratacom/
216
Nortel/DEC Local Management
217
Interface Specification protocol
219
ansiT1617D(3): Interface operates the ANSI T1.617
220
Annex D PVC status protocol
223
ansiT1617B(4): Interface operates the ANSI
227
ccittQ933A(5): Interface operates the ITU Q.933
228
Annex A PVC status protocol"
232
::= { frLportEntry 6 }
234
frLportVCSigPointer OBJECT-TYPE
235
SYNTAX OBJECT IDENTIFIER
239
"The value of this object is used as a pointer to
240
the table that contains the Local In-Channel
241
Signaling Protocol parameters and errors for this
242
UNI/NNI logical port.
244
This object has been deprecated to reflect the
245
fact that the local in-channel signaling
246
parameters are accessed from a single table
247
(frMgtVCSigTable) that includes parameters for all
248
possible signaling protocols. Early design
249
anticipated multiple tables, one for each
251
::= { frLportEntry 7 }
253
frLportDLCIIndexValue OBJECT-TYPE
254
SYNTAX Integer32 (16..4194303)
258
"This object contains a hint to be used for
259
frPVCEndptDLCIIndex when creating entries in the
260
frPVCEndptTable. The SYNTAX of this object
261
matches the SYNTAX of the frPVCEndptDLCIIndex - an
262
object that is restricted to legal Q.922 DLCI
263
values for the size of the address field.
265
The value 0 indicates that no unassigned entries
268
To obtain the frPVCEndptDLCIIndex value for a new
269
entry, the manager issues a management protocol
270
retrieval operation to obtain the current value of
273
this object. After each retrieval, the agent must
274
modify the value to the next unassigned index to
275
prevent assignment of the same value to multiple
278
A management system should repeat the read to
279
obtain a new value should an attempt to create the
280
new row using the previously returned hint fail."
281
REFERENCE "Q.922 [25]"
282
::= { frLportEntry 8 }
284
frLportTypeAdmin OBJECT-TYPE
289
MAX-ACCESS read-write
292
"The value of this object desired identifies the
293
type of network interface for this logical port."
294
::= { frLportEntry 9 }
296
frLportVCSigProtocolAdmin OBJECT-TYPE
304
MAX-ACCESS read-write
307
"The value of this object identifies the desired
308
Local In-Channel Signaling Protocol that is used
309
for this frame relay UNI/NNI logical port. This
310
value must be made the active protocol as soon as
311
possible on the device.
313
Refer to frLportVCSigProtocol for a description of
314
each signaling protocol choices."
318
::= { frLportEntry 10 }
320
frLportFragControl OBJECT-TYPE
327
MAX-ACCESS read-write
330
"This object controls the transmission and
331
reception of fragmentation frames for this UNI or
334
on(1) Frames are fragmented using the interface
336
Note: The customer side of the interface
337
must also be configured to fragment
340
off(2) Frames are not fragmented using the
341
interface fragmentation format."
342
REFERENCE "FRF.12 [21]"
344
::= { frLportEntry 11 }
346
frLportFragSize OBJECT-TYPE
347
SYNTAX Integer32 (0..4096)
349
MAX-ACCESS read-write
352
"The value of this object is the size in octets of
353
the maximum size of each fragment to be sent when
354
fragmenting. This object is only used by the
355
fragmentation transmitter, and the two sides of
356
the interface may differ. The fragment size
357
includes the octets for the frame relay header,
358
the UI octet, the NLPID, the fragmentation header,
359
and the fragment payload. If frLportFragControl is
360
set to off, this value should be zero."
361
REFERENCE "FRF.12 [21]"
363
::= { frLportEntry 12 }
366
-- Frame Relay Management VC Signaling
369
frMgtVCSigTable OBJECT-TYPE
370
SYNTAX SEQUENCE OF FrMgtVCSigEntry
373
MAX-ACCESS not-accessible
376
"The Frame Relay Management VC Signaling
377
Parameters and Errors table."
378
::= { frnetservObjects 2 }
380
frMgtVCSigEntry OBJECT-TYPE
381
SYNTAX FrMgtVCSigEntry
382
MAX-ACCESS not-accessible
385
"An entry in the Frame Relay Management VC
386
Signaling Parameters Errors table."
388
::= { frMgtVCSigTable 1 }
392
frMgtVCSigProced INTEGER,
393
frMgtVCSigUserN391 INTEGER,
394
frMgtVCSigUserN392 INTEGER,
395
frMgtVCSigUserN393 INTEGER,
396
frMgtVCSigUserT391 INTEGER,
397
frMgtVCSigNetN392 INTEGER,
398
frMgtVCSigNetN393 INTEGER,
399
frMgtVCSigNetT392 INTEGER,
400
frMgtVCSigNetnN4 INTEGER,
401
frMgtVCSigNetnT3 INTEGER,
402
frMgtVCSigUserLinkRelErrors Counter32,
403
frMgtVCSigUserProtErrors Counter32,
404
frMgtVCSigUserChanInactive Counter32,
405
frMgtVCSigNetLinkRelErrors Counter32,
406
frMgtVCSigNetProtErrors Counter32,
407
frMgtVCSigNetChanInactive Counter32,
408
frMgtVCSigProcedAdmin INTEGER,
409
frMgtVCSigUserN391Admin INTEGER,
410
frMgtVCSigUserN392Admin INTEGER,
411
frMgtVCSigUserN393Admin INTEGER,
412
frMgtVCSigUserT391Admin INTEGER,
413
frMgtVCSigNetN392Admin INTEGER,
414
frMgtVCSigNetN393Admin INTEGER,
415
frMgtVCSigNetT392Admin INTEGER,
416
frMgtVCSigNetnT3Admin INTEGER
419
frMgtVCSigProced OBJECT-TYPE
430
"The value of this object identifies the local
431
in-channel signaling procedural role that is used
432
for this UNI/NNI logical port. Bidirectional
433
procedures implies that both user-side and
434
network-side procedural roles are used.
436
u2nnet(1) Logical port operates user to network
437
procedure in the role of the network
440
bidirect(2) Logical port operates the
441
bidirectional procedure (both user
442
and network side roles)
444
u2nuser(3) Logical port operates user to network
445
procedure in the role of the user
447
REFERENCE "Q.933 Annex A [22],
449
::= { frMgtVCSigEntry 1 }
451
frMgtVCSigUserN391 OBJECT-TYPE
452
SYNTAX INTEGER (1..255)
457
"The value of this object identifies the User-side
458
N391 full status polling cycle value for this
459
UNI/NNI logical port. If the logical port is not
460
performing user-side (bidirectional) procedures,
461
then this object is not instantiated and an
462
attempt to read will result in the noSuchInstance
464
REFERENCE "Q.933 Annex A [22],
467
::= { frMgtVCSigEntry 2 }
469
frMgtVCSigUserN392 OBJECT-TYPE
470
SYNTAX INTEGER (1..10)
477
"The value of this object identifies the User-side
478
N392 error threshold value for this UNI/NNI
479
logical port. If the logical port is not
480
performing user-side (bidirectional) procedures,
481
then this object is not instantiated."
482
REFERENCE "Q.933 Annex A [22],
485
::= { frMgtVCSigEntry 3 }
487
frMgtVCSigUserN393 OBJECT-TYPE
488
SYNTAX INTEGER (1..10)
493
"The value of this object identifies the User-side
494
N393 monitored events count value for this UNI/NNI
495
logical port. If the logical port is not
496
performing user-side (bidirectional) procedures,
497
then this object is not instantiated."
498
REFERENCE "Q.933 Annex A [22],
501
::= { frMgtVCSigEntry 4 }
503
frMgtVCSigUserT391 OBJECT-TYPE
504
SYNTAX INTEGER (5..30)
509
"The value of this object identifies the User-side
510
T391 link integrity verification polling timer
511
value for this UNI/NNI logical port. If the
512
logical port is not performing user-side
513
procedures, then this object is not instantiated."
514
REFERENCE "Q.933 Annex A [22],
517
::= { frMgtVCSigEntry 5 }
519
frMgtVCSigNetN392 OBJECT-TYPE
520
SYNTAX INTEGER (1..10)
527
"The value of this object identifies the Network-
528
side N392 error threshold value (nN2 for LMI) for
529
this UNI/NNI logical port. If the logical port is
530
not performing network-side procedures, then this
531
object is not instantiated."
532
REFERENCE "Q.933 Annex A [22],
536
::= { frMgtVCSigEntry 6 }
538
frMgtVCSigNetN393 OBJECT-TYPE
539
SYNTAX INTEGER (1..10)
544
"The value of this object identifies the Network-
545
side N393 monitored events count value (nN3 for
546
LMI) for this UNI/NNI logical port. If the
547
logical port is not performing network-side
548
procedures, then this object is not instantiated."
549
REFERENCE "Q.933 Annex A [22],
553
::= { frMgtVCSigEntry 7 }
555
frMgtVCSigNetT392 OBJECT-TYPE
556
SYNTAX INTEGER (5..30)
561
"The value of this object identifies the Network-
562
side T392 polling verification timer value (nT2
563
for LMI) for this UNI/NNI logical port. If the
564
logical port is not performing network-side
565
procedures, then this object is not instantiated."
566
REFERENCE "Q.933 Annex A [22],
570
::= { frMgtVCSigEntry 8 }
573
frMgtVCSigNetnN4 OBJECT-TYPE
574
SYNTAX INTEGER (5..5)
579
"The value of this object identifies the Network-
580
side nN4 maximum status enquires received value
581
for this UNI/NNI logical port. If the logical
582
port is not performing network-side procedures or
583
is not performing LMI procedures, then this object
586
This object applies only to LMI and always has a
589
::= { frMgtVCSigEntry 9 }
591
frMgtVCSigNetnT3 OBJECT-TYPE
592
SYNTAX INTEGER (5 | 10 | 15 | 20 | 25 | 30)
597
"The value of this object identifies the Network-
598
side nT3 timer (for nN4 status enquires received)
599
value for this UNI/NNI logical port. If the
600
logical port is not performing network-side
601
procedures or is not performing LMI procedures,
602
then this object is not instantiated.
604
This object applies only to LMI."
607
::= { frMgtVCSigEntry 10 }
609
frMgtVCSigUserLinkRelErrors OBJECT-TYPE
615
"The number of user-side local in-channel
616
signaling link reliability errors (i.e., non-
617
receipt of Status/Status Enquiry messages or
618
invalid sequence numbers in a Link Integrity
619
Verification Information Element) for this UNI/NNI
620
logical port. If the logical port is not
623
performing user-side procedures, then this object
624
is not instantiated."
625
::= { frMgtVCSigEntry 11 }
627
frMgtVCSigUserProtErrors OBJECT-TYPE
633
"The number of user-side local in-channel
634
signaling protocol errors (i.e., protocol
635
discriminator, unnumbered information, message
636
type, call reference, and mandatory information
637
element errors) for this UNI/NNI logical port. If
638
the logical port is not performing user-side
639
procedures, then this object is not instantiated."
640
::= { frMgtVCSigEntry 12 }
642
frMgtVCSigUserChanInactive OBJECT-TYPE
648
"The number of times the user-side channel was
649
declared inactive (i.e., N392 errors in N393
650
events) for this UNI/NNI logical port. If the
651
logical port is not performing user-side
652
procedures, then this object is not instantiated."
653
::= { frMgtVCSigEntry 13 }
655
frMgtVCSigNetLinkRelErrors OBJECT-TYPE
661
"The number of network-side local in-channel
662
signaling link reliability errors (i.e., non-
663
receipt of Status/Status Enquiry messages or
664
invalid sequence numbers in a Link Integrity
665
Verification Information Element) for this UNI/NNI
667
::= { frMgtVCSigEntry 14 }
669
frMgtVCSigNetProtErrors OBJECT-TYPE
677
"The number of network-side local in-channel
678
signaling protocol errors (i.e., protocol
679
discriminator, message type, call reference, and
680
mandatory information element errors) for this
681
UNI/NNI logical port."
682
::= { frMgtVCSigEntry 15 }
684
frMgtVCSigNetChanInactive OBJECT-TYPE
690
"The number of times the network-side channel was
691
declared inactive (i.e., N392 errors in N393
692
events) for this UNI/NNI logical port."
693
::= { frMgtVCSigEntry 16 }
695
frMgtVCSigProcedAdmin OBJECT-TYPE
701
MAX-ACCESS read-write
704
"The value of this object identifies the local
705
in-channel signaling procedural role that is used
706
for this UNI/NNI logical port. Bidirectional
707
procedures implies that both user-side and
708
network-side procedural roles are used.
710
u2nnet(1) Logical port operates user to network
711
procedure in the role of the network
714
bidirect(2) Logical port operates the
715
bidirectional procedure (both user
716
and network side roles)
718
u2nuser(3) Logical port operates user to network
719
procedure in the role of the user
723
REFERENCE "Q.933 Annex A [22],
726
::= { frMgtVCSigEntry 17 }
728
frMgtVCSigUserN391Admin OBJECT-TYPE
729
SYNTAX INTEGER (1..255)
731
MAX-ACCESS read-write
734
"The value of this object identifies the desired
735
User-side N391 full status polling cycle value for
736
this UNI/NNI logical port. If the logical port is
737
not performing user-side (bidirectional)
738
procedures, then this object is not instantiated."
739
REFERENCE "Q.933 Annex A [22],
741
::= { frMgtVCSigEntry 18 }
743
frMgtVCSigUserN392Admin OBJECT-TYPE
744
SYNTAX INTEGER (1..10)
746
MAX-ACCESS read-write
749
"The value of this object identifies the desired
750
User-side N392 error threshold value for this
751
UNI/NNI logical port. If the logical port is not
752
performing user-side (bidirectional) procedures,
753
then this object is not instantiated."
754
REFERENCE "Q.933 Annex A [22],
756
::= { frMgtVCSigEntry 19 }
758
frMgtVCSigUserN393Admin OBJECT-TYPE
759
SYNTAX INTEGER (1..10)
761
MAX-ACCESS read-write
764
"The value of this object identifies the desired
765
User-side N393 monitored events count value for
766
this UNI/NNI logical port. If the logical port is
767
not performing user-side (bidirectional)
768
procedures, then this object is not instantiated."
769
REFERENCE "Q.933 Annex A [22],
773
::= { frMgtVCSigEntry 20 }
775
frMgtVCSigUserT391Admin OBJECT-TYPE
776
SYNTAX INTEGER (5..30)
778
MAX-ACCESS read-write
781
"The value of this object identifies the desired
782
User-side T391 link integrity verification polling
783
timer value for this UNI/NNI logical port. If the
784
logical port is not performing user-side
785
procedures, then this object is not instantiated."
786
REFERENCE "Q.933 Annex A [22],
788
::= { frMgtVCSigEntry 21 }
790
frMgtVCSigNetN392Admin OBJECT-TYPE
791
SYNTAX INTEGER (1..10)
793
MAX-ACCESS read-write
796
"The value of this object identifies the desired
797
Network-side N392 error threshold value (nN2 for
798
LMI) for this UNI/NNI logical port. If the
799
logical port is not performing network-side
800
procedures, then this object is not instantiated."
801
REFERENCE "Q.933 Annex A [22],
804
::= { frMgtVCSigEntry 22 }
806
frMgtVCSigNetN393Admin OBJECT-TYPE
807
SYNTAX INTEGER (1..10)
809
MAX-ACCESS read-write
812
"The value of this object identifies the desired
813
Network-side N393 monitored events count value
814
(nN3 for LMI) for this UNI/NNI logical port. If
815
the logical port is not performing network-side
816
procedures, then this object is not instantiated."
817
REFERENCE "Q.933 Annex A [22],
820
::= { frMgtVCSigEntry 23 }
823
frMgtVCSigNetT392Admin OBJECT-TYPE
824
SYNTAX INTEGER (5..30)
826
MAX-ACCESS read-write
829
"The value of this object identifies the desired
830
Network-side T392 polling verification timer value
831
(nT2 for LMI) for this UNI/NNI logical port. If
832
the logical port is not performing network-side
833
procedures, then this object is not instantiated."
834
REFERENCE "Q.933 Annex A [22],
837
::= { frMgtVCSigEntry 24 }
839
frMgtVCSigNetnT3Admin OBJECT-TYPE
840
SYNTAX INTEGER (5 | 10 | 15 | 20 | 25 | 30)
842
MAX-ACCESS read-write
845
"The value of this object identifies the desired
846
Network-side nT3 timer (for nN4 status enquires
847
received) value for this UNI/NNI logical port. If
848
the logical port is not performing network-side
849
procedures or is not performing LMI procedures,
850
then this object is not instantiated. This object
851
applies only to LMI."
853
::= { frMgtVCSigEntry 25 }
856
-- Frame Relay PVC End-points
859
frPVCEndptTable OBJECT-TYPE
860
SYNTAX SEQUENCE OF FrPVCEndptEntry
861
MAX-ACCESS not-accessible
864
"The Frame Relay PVC End-Point table. This table
865
is used to model a PVC end-point. This table
866
contains the traffic parameters and statistics for
869
This table is used to identify the traffic
870
parameters for a bi-directional PVC segment end-
873
point, and it also provides statistics for a PVC
876
A PVC segment end-point is identified by a UNI/NNI
877
logical port index value and DLCI index value.
879
If the frame relay service provider allows the
880
frame relay CNM subscriber to create, modify or
881
delete PVCs using SNMP, then this table is used to
882
identify and reserve the requested traffic
883
parameters of each PVC segment end-point. The
884
Connection table is used to 'connect' the end-
885
points together. Not all implementations will
886
support the capability of
887
creating/modifying/deleting PVCs using SNMP as a
888
feature of frame relay CNM service.
890
Uni-directional PVCs are modeled with zero valued
891
traffic parameters in one of the directions (In or
892
Out direction) in this table.
894
To create a PVC, the following procedures shall be
897
1) Create the entries for the PVC segment
898
endpoints in the frPVCEndptTable by specifying
899
the traffic parameters for the bi-directional
900
PVC segment endpoints. As shown in figure 2, a
901
point-to-point PVC has two endpoints, thus two
902
entries in this table. Uni-directional PVCs
903
are modeled with zero valued traffic
904
parameters in one direction; all the `In'
905
direction parameters for one frame relay PVC
906
End-point or all the `Out' direction
907
parameters for the other frame relay PVC
910
In _____________________________ Out
912
______| Frame Relay Network |________
914
<<<<<<|_____________________________|<<<<<<<<
915
Frame Relay Frame Relay
919
Figure 2, PVC Terminology
923
2) Go to the Frame Relay Connection Group."
924
::= { frnetservObjects 3 }
926
frPVCEndptEntry OBJECT-TYPE
927
SYNTAX FrPVCEndptEntry
928
MAX-ACCESS not-accessible
931
"An entry in the Frame Relay PVC Endpoint table."
932
INDEX { ifIndex, frPVCEndptDLCIIndex }
933
::= { frPVCEndptTable 1 }
937
frPVCEndptDLCIIndex Integer32,
938
frPVCEndptInMaxFrameSize Integer32,
939
frPVCEndptInBc Integer32,
940
frPVCEndptInBe Integer32,
941
frPVCEndptInCIR Integer32,
942
frPVCEndptOutMaxFrameSize Integer32,
943
frPVCEndptOutBc Integer32,
944
frPVCEndptOutBe Integer32,
945
frPVCEndptOutCIR Integer32,
946
frPVCEndptConnectIdentifier Integer32,
947
frPVCEndptRowStatus RowStatus,
948
frPVCEndptRcvdSigStatus INTEGER,
949
frPVCEndptInFrames Counter32,
950
frPVCEndptOutFrames Counter32,
951
frPVCEndptInDEFrames Counter32,
952
frPVCEndptInExcessFrames Counter32,
953
frPVCEndptOutExcessFrames Counter32,
954
frPVCEndptInDiscards Counter32,
955
frPVCEndptInOctets Counter32,
956
frPVCEndptOutOctets Counter32,
957
frPVCEndptInDiscardsDESet Counter32,
958
frPVCEndptInFramesFECNSet Counter32,
959
frPVCEndptOutFramesFECNSet Counter32,
960
frPVCEndptInFramesBECNSet Counter32,
961
frPVCEndptOutFramesBECNSet Counter32,
962
frPVCEndptInCongDiscards Counter32,
963
frPVCEndptInDECongDiscards Counter32,
964
frPVCEndptOutCongDiscards Counter32,
965
frPVCEndptOutDECongDiscards Counter32,
966
frPVCEndptOutDEFrames Counter32,
967
frPVCEndptAtmIwfConnIndex Integer32
973
frPVCEndptDLCIIndex OBJECT-TYPE
974
SYNTAX Integer32 (16..4194303)
975
MAX-ACCESS not-accessible
978
"The value of this object is equal to the DLCI
979
value for this PVC end-point.
981
The values are restricted to the legal range for
982
the size of address field supported by the logical
983
port (frLportAddrDLCILen)."
984
REFERENCE "Q.922 [25]"
985
::= { frPVCEndptEntry 1 }
987
frPVCEndptInMaxFrameSize OBJECT-TYPE
988
SYNTAX Integer32 (1..4096)
990
MAX-ACCESS read-create
993
"The value of this object is the size in octets of
994
the largest frame relay information field for this
995
PVC end-point in the ingress direction (into the
996
frame relay network). The value of
997
frPVCEndptInMaxFrameSize must be less than or
998
equal to the corresponding ifMtu for this frame
999
relay UNI/NNI logical port."
1000
REFERENCE "FRF.1 [31]
1004
::= { frPVCEndptEntry 2 }
1006
frPVCEndptInBc OBJECT-TYPE
1007
SYNTAX Integer32 (1..2147483647)
1009
MAX-ACCESS read-create
1012
"The value of this object is equal to the
1013
committed burst size (Bc) parameter (measured in
1014
bits) for this PVC end-point in the ingress
1015
direction (into the frame relay network).
1017
Note that the max value of this range is lower
1018
than the max value allowed by Q.933 (16383 *
1023
Note that the value is encoded in bits whilst the
1024
Q.933 Link layer core parameters information
1025
element encodes this information using octet
1027
REFERENCE "Q.933 [22]"
1028
::= { frPVCEndptEntry 3 }
1030
frPVCEndptInBe OBJECT-TYPE
1031
SYNTAX Integer32 (1..2147483647)
1033
MAX-ACCESS read-create
1036
"The value of this object is equal to the excess
1037
burst size (Be) parameter (measured in bits) for
1038
this PVC end-point in the ingress direction (into
1039
the frame relay network).
1041
Note that the max value of this range is lower
1042
than the max value allowed by Q.933 (16383 *
1045
Note that the value is encoded in bits whilst the
1046
Q.933 Link layer core parameters information
1047
element encodes this information using octet
1049
REFERENCE "Q.933 [22]"
1050
::= { frPVCEndptEntry 4 }
1052
frPVCEndptInCIR OBJECT-TYPE
1053
SYNTAX Integer32 (1..2147483647)
1054
UNITS "Bits per Second"
1055
MAX-ACCESS read-create
1058
"The value of this object is equal to the
1059
committed information rate (CIR) parameter
1060
(measured in bits per second) for this PVC end-
1061
point in the ingress direction (into the frame
1064
Note that the max value of this range is lower
1065
than the max value allowed by Q.933 (2047 *
1067
REFERENCE "Q.933 [22]"
1068
::= { frPVCEndptEntry 5 }
1070
frPVCEndptOutMaxFrameSize OBJECT-TYPE
1073
SYNTAX Integer32 (1..4096)
1075
MAX-ACCESS read-create
1078
"The value of this object is the size in octets of
1079
the largest frame relay information field for this
1080
PVC end-point in the egress direction (out of the
1081
frame relay network). The value of
1082
frPVCEndptOutMaxFrameSize must be less than or
1083
equal to the corresponding ifMtu for this frame
1084
relay UNI/NNI logical port."
1085
REFERENCE "FRF.1 [31]
1089
::= { frPVCEndptEntry 6 }
1091
frPVCEndptOutBc OBJECT-TYPE
1092
SYNTAX Integer32 (1..2147483647)
1094
MAX-ACCESS read-create
1097
"The value of this object is equal to the
1098
committed burst size (Bc) parameter (measured in
1099
bits) for this PVC end-point in the egress
1100
direction (out of the frame relay network).
1102
Note that the max value of this range is lower
1103
than the max value allowed by Q.933 (16383 *
1106
Note that the value is encoded in bits whilst the
1107
Q.933 Link layer core parameters information
1108
element encodes this information using octet
1110
REFERENCE "Q.933 [22]"
1111
::= { frPVCEndptEntry 7 }
1113
frPVCEndptOutBe OBJECT-TYPE
1114
SYNTAX Integer32 (1..2147483647)
1116
MAX-ACCESS read-create
1119
"The value of this object is equal to the excess
1120
burst size (Be) parameter (measured in bits) for
1123
this PVC end-point in the egress direction (out of
1124
the frame relay network).
1126
Note that the max value of this range is lower
1127
than the max value allowed by Q.933 (16383 *
1130
Note that the value is encoded in bits whilst the
1131
Q.933 Link layer core parameters information
1132
element encodes this information using octet
1134
REFERENCE "Q.933 [22]"
1135
::= { frPVCEndptEntry 8 }
1137
frPVCEndptOutCIR OBJECT-TYPE
1138
SYNTAX Integer32 (1..2147483647)
1139
UNITS "Bits per Second"
1140
MAX-ACCESS read-create
1143
"The value of this object is equal to the
1144
committed information rate (CIR) parameter
1145
(measured in bits per second) for this PVC end-
1146
point in the egress direction (out of the frame
1149
Note that the max value of this range is lower
1150
than the max value allowed by Q.933 (2047 *
1152
REFERENCE "Q.933 [22]"
1153
::= { frPVCEndptEntry 9 }
1155
frPVCEndptConnectIdentifier OBJECT-TYPE
1156
SYNTAX Integer32 (0..2147483647)
1157
MAX-ACCESS read-only
1160
"This object is used to associate PVC end-points
1161
as being part of one PVC segment connection. This
1162
value of this object is equal to the value of
1163
frPVCConnectIndex, which is used as one of the
1164
indices into the frPVCConnectTable.
1166
A connection that has been cross-connected via the
1167
FR/ATM PVC Service IWF cross-connect table will
1168
return the value zero when this object is read. In
1169
case of these interworked connections, the
1170
frPVCEndptAtmIwfConnIndex object must be accessed
1173
to select the entry in the FR/ATM PVC Service IWF
1174
cross-connect table.
1176
The value of this object is provided by the agent,
1177
after the associated entries in the
1178
frPVCConnectTable or frAtmIwfConnectionTable have
1180
::= { frPVCEndptEntry 10 }
1182
frPVCEndptRowStatus OBJECT-TYPE
1184
MAX-ACCESS read-create
1187
"This object is used to create new rows in this
1188
table, modify existing rows, and to delete
1189
existing rows. To create a new PVC, the entries
1190
for the PVC segment end-points in the
1191
frPVCEndptTable must first be created. Next, the
1192
frPVCConnectTable is used to associate the frame
1193
relay PVC segment end-points. In order for the
1194
manager to have the necessary error diagnostics,
1195
the frPVCEndptRowStatus object must initially be
1196
set to `createAndWait(5)'. While the
1197
frPVCEndptRowStatus object is in the
1198
`createAndWait(5)' state, the manager can set each
1199
columnar object and get the necessary error
1200
diagnostics. The frPVCEndptRowStatus object may
1201
not be set to `active(1)' unless the following
1202
columnar objects exist in this row:
1203
frPVCEndptInMaxFrameSize, frPVCEndptInBc,
1204
frPVCEndptInBe, frPVCEndptInCIR,
1205
frPVCEndptOutMaxFrameSize, frPVCEndptOutBc,
1206
frPVCEndptOutBe, and frPVCEndptOutCIR."
1207
::= { frPVCEndptEntry 11 }
1209
frPVCEndptRcvdSigStatus OBJECT-TYPE
1216
MAX-ACCESS read-only
1219
"The value of this object identifies the PVC
1220
status received via the local in-channel signaling
1223
procedures for this PVC end-point. This object is
1224
only pertinent for interfaces that perform the
1225
bidirectional procedures.
1227
Each value has the following meaning:
1228
deleted(1): This PVC is not listed in the full
1229
status reports received from the
1230
user device. The object retains
1231
this value for as long as the PVC
1232
is not listed in the full status
1235
active(2): This PVC is reported as active, or
1236
operational, by the user device.
1238
inactive(3): This PVC is reported as inactive,
1239
or non-operational, by the user
1242
none(4): This interface is only using the
1243
network-side in-channel signaling
1244
procedures, so this object does
1246
::= { frPVCEndptEntry 12 }
1248
frPVCEndptInFrames OBJECT-TYPE
1251
MAX-ACCESS read-only
1254
"The number of frames received by the network
1255
(ingress) for this PVC end-point. This includes
1256
any frames discarded by the network due to
1257
submitting more than Bc + Be data or due to any
1258
network congestion recovery procedures."
1259
::= { frPVCEndptEntry 13 }
1261
frPVCEndptOutFrames OBJECT-TYPE
1264
MAX-ACCESS read-only
1267
"The number of frames sent by the network (egress)
1268
regardless of whether they are Bc or Be frames for
1269
this PVC end-point."
1270
::= { frPVCEndptEntry 14 }
1273
frPVCEndptInDEFrames OBJECT-TYPE
1276
MAX-ACCESS read-only
1279
"The number of frames received by the network
1280
(ingress) with the DE bit set to (1) for this PVC
1282
::= { frPVCEndptEntry 15 }
1284
frPVCEndptInExcessFrames OBJECT-TYPE
1287
MAX-ACCESS read-only
1290
"The number of frames received by the network
1291
(ingress) for this PVC end-point which were
1292
treated as excess traffic. Frames which are sent
1293
to the network with DE set to zero are treated as
1294
excess when more than Bc bits are submitted to the
1295
network during the Committed Information Rate
1296
Measurement Interval (Tc). Excess traffic may or
1297
may not be discarded at the ingress if more than
1298
Bc + Be bits are submitted to the network during
1299
Tc. Traffic discarded at the ingress is not
1300
recorded in frPVCEndptInExcessFrames. Frames
1301
which are sent to the network with DE set to one
1302
are also treated as excess traffic."
1303
::= { frPVCEndptEntry 16 }
1305
frPVCEndptOutExcessFrames OBJECT-TYPE
1308
MAX-ACCESS read-only
1311
"The number of frames sent by the network (egress)
1312
for this PVC end-point which were treated as
1313
excess traffic. (The DE bit may be set to one.)"
1314
::= { frPVCEndptEntry 17 }
1316
frPVCEndptInDiscards OBJECT-TYPE
1319
MAX-ACCESS read-only
1324
"The number of frames received by the network
1325
(ingress) that were discarded due to traffic
1326
enforcement for this PVC end-point. Congestion
1327
discards are not counted in this object."
1328
::= { frPVCEndptEntry 18 }
1330
frPVCEndptInOctets OBJECT-TYPE
1333
MAX-ACCESS read-only
1336
"The number of octets received by the network
1337
(ingress) for this PVC end-point. This counter
1338
should only count octets from the beginning of the
1339
frame relay header field to the end of user data.
1340
If the network supporting frame relay can not
1341
count octets, then this count should be an
1343
::= { frPVCEndptEntry 19 }
1345
frPVCEndptOutOctets OBJECT-TYPE
1348
MAX-ACCESS read-only
1351
"The number of octets sent by the network (egress)
1352
for this PVC end-point. This counter should only
1353
count octets from the beginning of the frame relay
1354
header field to the end of user data. If the
1355
network supporting frame relay can not count
1356
octets, then this count should be an
1358
::= { frPVCEndptEntry 20 }
1360
frPVCEndptInDiscardsDESet OBJECT-TYPE
1363
MAX-ACCESS read-only
1366
"The number of frames received by the network
1367
(ingress) that were discarded with the DE bit set
1368
due to traffic enforcement for this PVC end-point.
1369
Congestion discards are not counted in this
1373
::= { frPVCEndptEntry 21 }
1375
frPVCEndptInFramesFECNSet OBJECT-TYPE
1378
MAX-ACCESS read-only
1381
"The number of frames received by the network
1382
(ingress) that have the FECN bit set for this PVC
1384
::= { frPVCEndptEntry 22 }
1386
frPVCEndptOutFramesFECNSet OBJECT-TYPE
1389
MAX-ACCESS read-only
1392
"The number of frames sent by the network (egress)
1393
that have the FECN bit set for this PVC end-
1395
::= { frPVCEndptEntry 23 }
1397
frPVCEndptInFramesBECNSet OBJECT-TYPE
1400
MAX-ACCESS read-only
1403
"The number of frames received by the network
1404
(ingress) that have the BECN bit set for this PVC
1406
::= { frPVCEndptEntry 24 }
1408
frPVCEndptOutFramesBECNSet OBJECT-TYPE
1411
MAX-ACCESS read-only
1414
"The number of frames sent by the network (egress)
1415
that have the BECN bit set for this PVC end-
1417
::= { frPVCEndptEntry 25 }
1419
frPVCEndptInCongDiscards OBJECT-TYPE
1424
MAX-ACCESS read-only
1427
"The number of frames received by the network
1428
(ingress) that were discarded due to input buffer
1429
congestion, rather than traffic enforcement, for
1430
this PVC end-point."
1431
::= { frPVCEndptEntry 26 }
1433
frPVCEndptInDECongDiscards OBJECT-TYPE
1436
MAX-ACCESS read-only
1439
"The number of frames counted by
1440
frPVCEndptInCongDiscards with the DE bit set to
1442
::= { frPVCEndptEntry 27 }
1444
frPVCEndptOutCongDiscards OBJECT-TYPE
1447
MAX-ACCESS read-only
1450
"The number of frames sent by the network (egress)
1451
that were discarded due to output buffer
1452
congestion for this PVC end-point."
1453
::= { frPVCEndptEntry 28 }
1455
frPVCEndptOutDECongDiscards OBJECT-TYPE
1458
MAX-ACCESS read-only
1461
"The number of frames counted by
1462
frPVCEndptOutCongDiscards with the DE bit set to
1464
::= { frPVCEndptEntry 29 }
1466
frPVCEndptOutDEFrames OBJECT-TYPE
1469
MAX-ACCESS read-only
1474
"The number of frames sent by the network (egress)
1475
with the DE bit set to (1) for this PVC end-
1477
::= { frPVCEndptEntry 30 }
1479
frPVCEndptAtmIwfConnIndex OBJECT-TYPE
1480
SYNTAX Integer32 (0..2147483647)
1481
MAX-ACCESS read-only
1484
"This object contains the index value of the
1485
FR/ATM cross-connect table entry used to link the
1486
frame relay PVC with an ATM PVC.
1488
Each row of the frPVCEndptTable that is not
1489
cross-connected with an ATM PVC must return the
1490
value zero when this object is read.
1492
The value of this object is initialized by the
1493
agent after the associated entries in the
1494
frAtmIwfConnectionTable have been created.
1496
The value of this object is reset to zero
1497
following destruction of the associated entry in
1498
the frAtmIwfConnectionTable"
1499
::= { frPVCEndptEntry 31 }
1502
-- Frame Relay PVC Connections
1505
frPVCConnectIndexValue OBJECT-TYPE
1506
SYNTAX INTEGER (0..2147483647)
1507
MAX-ACCESS read-only
1510
"This object returns a hint to be used for
1511
frPVCConnectIndex when creating entries in the
1514
The value 0 indicates that no unassigned entries
1517
To obtain the frPVCConnectIndex value for a new
1518
entry, the manager issues a management protocol
1519
retrieval operation to obtain the current value of
1520
this object. After each retrieval, the agent must
1523
modify the value to the next unassigned index to
1524
prevent assignment of the same value to multiple
1527
A management system should repeat the read to
1528
obtain a new value should an attempt to create the
1529
new row using the previously returned hint fail."
1530
::= { frnetservObjects 4 }
1532
frPVCConnectTable OBJECT-TYPE
1533
SYNTAX SEQUENCE OF FrPVCConnectEntry
1534
MAX-ACCESS not-accessible
1537
"The Frame Relay PVC Connect Table is used to
1538
model the bi-directional PVC segment flows
1539
including: point-to-point PVCs, point-to-
1540
multipoint PVCs, and multipoint-to-multipoint
1543
This table has read-create access and is used to
1544
associate PVC end-points together as belonging to
1545
one connection. The frPVCConnectIndex is used to
1546
associate all the bi-directional flows. Not all
1547
implementations will support the capability of
1548
creating/modifying/deleting PVCs using SNMP as a
1549
feature of frame relay CNM service.
1551
Once the entries in the frPVCEndptTable are
1552
created, the following step are used to associate
1553
the PVC end-points as belonging to one PVC
1556
1) Obtain a unique frPVCConnectIndex
1557
using the frPVCConnectIndexValue object.
1559
2) Connect the PVC segment endpoints together
1560
with the applicable frPVCConnectIndex value
1561
obtained via frPVCConnectIndexValue. The
1562
entries in this table are created by using
1563
the frPVCConnectRowStatus object.
1565
3) The agent will provide the value of the
1566
corresponding instances of
1567
frPVCEndptConnectIdentifier with the
1568
frPVCConnectIndex value.
1570
4) Set frPVCConnectAdminStatus to `active(1)' in
1573
all rows for this PVC segment to turn the
1576
For example, the Frame Relay PVC Connection Group
1577
models a bi-directional, point-to-point PVC
1578
segment as one entry in this table.
1580
Frame Relay Frame Relay
1583
__________________________________
1585
_____| >> from low to high PVC flow >> |_____
1586
| << from high to low PVC flow << |
1587
|__________________________________|
1589
The terms low and high are chosen to represent
1590
numerical ordering of a PVC segment's endpoints
1591
for representation in this table. That is, the
1592
endpoint with the lower value of ifIndex is termed
1593
'low', while the opposite endpoint of the segment
1594
is termed 'high'. This terminology is to provide
1595
directional information; for example the
1596
frPVCConnectL2hOperStatus and
1597
frPVCConnectH2lOperStatus as illustrated above.
1599
If the Frame Relay Connection table is used to
1600
model a unidirectional PVC, then one direction
1601
(either from low to high or from high to low) has
1602
its Operational Status equal to down.
1604
A PVC segment is a portion of a PVC that traverses
1605
one Frame Relay Network, and a PVC segment is
1606
identified by its two end-points (UNI/NNI logical
1607
port index value and DLCI index value) through one
1608
Frame Relay Network."
1609
::= { frnetservObjects 5 }
1611
frPVCConnectEntry OBJECT-TYPE
1612
SYNTAX FrPVCConnectEntry
1613
MAX-ACCESS not-accessible
1616
"An entry in the Frame Relay PVC Connect table.
1617
This entry is used to model a PVC segment in two
1619
INDEX { frPVCConnectIndex,
1620
frPVCConnectLowIfIndex,
1623
frPVCConnectLowDLCIIndex,
1624
frPVCConnectHighIfIndex,
1625
frPVCConnectHighDLCIIndex }
1626
::= { frPVCConnectTable 1 }
1628
FrPVCConnectEntry ::=
1630
frPVCConnectIndex Integer32,
1631
frPVCConnectLowIfIndex InterfaceIndex,
1632
frPVCConnectLowDLCIIndex Integer32,
1633
frPVCConnectHighIfIndex InterfaceIndex,
1634
frPVCConnectHighDLCIIndex Integer32,
1635
frPVCConnectAdminStatus INTEGER,
1636
frPVCConnectL2hOperStatus INTEGER,
1637
frPVCConnectH2lOperStatus INTEGER,
1638
frPVCConnectL2hLastChange TimeStamp,
1639
frPVCConnectH2lLastChange TimeStamp,
1640
frPVCConnectRowStatus RowStatus,
1641
frPVCConnectUserName SnmpAdminString,
1642
frPVCConnectProviderName SnmpAdminString
1645
frPVCConnectIndex OBJECT-TYPE
1646
SYNTAX Integer32 (0..2147483647)
1647
MAX-ACCESS not-accessible
1650
"The value of this object is equal to the
1651
frPVCConnectIndexValue obtained to uniquely
1652
identify this PVC segment connection."
1653
::= { frPVCConnectEntry 1 }
1655
frPVCConnectLowIfIndex OBJECT-TYPE
1656
SYNTAX InterfaceIndex
1657
MAX-ACCESS not-accessible
1660
"The value of this object is equal to IF-MIB
1661
ifIndex value of the UNI/NNI logical port for this
1662
PVC segment. The term low implies that this PVC
1663
segment end-point has the numerically lower
1664
ifIndex value than the connected/associated PVC
1667
RFC 1604 permitted a zero value for this object to
1668
identify termination at a non-frame relay
1669
interface. However, this cross-connect table is
1670
limited to frame relay connections. See the frame
1673
relay/ATM IWF MIB [28] for the cross-connect table
1674
used for those types of connections."
1675
::= { frPVCConnectEntry 2 }
1677
frPVCConnectLowDLCIIndex OBJECT-TYPE
1678
SYNTAX Integer32 (16..4194303)
1679
MAX-ACCESS not-accessible
1682
"The value of this object is equal to the DLCI
1683
value for this end-point of the PVC segment."
1684
REFERENCE "Q.922 [25]"
1685
::= { frPVCConnectEntry 3 }
1687
frPVCConnectHighIfIndex OBJECT-TYPE
1688
SYNTAX InterfaceIndex
1689
MAX-ACCESS not-accessible
1692
"The value of this object is equal to IF-MIB
1693
ifIndex value for the UNI/NNI logical port for
1694
this PVC segment. The term high implies that this
1695
PVC segment end-point has the numerically higher
1696
ifIndex value than the connected/associated PVC
1698
::= { frPVCConnectEntry 4 }
1700
frPVCConnectHighDLCIIndex OBJECT-TYPE
1701
SYNTAX Integer32 (16..4194303)
1702
MAX-ACCESS not-accessible
1705
"The value of this object is equal to the egress
1706
DLCI value for this end-point of the PVC segment."
1707
REFERENCE "Q.922 [25]"
1708
::= { frPVCConnectEntry 5 }
1710
frPVCConnectAdminStatus OBJECT-TYPE
1716
MAX-ACCESS read-create
1719
"The value of this object identifies the desired
1720
administrative status of this bi-directional PVC
1723
segment. The active(1) state means the PVC
1724
segment is currently operational; the inactive(2)
1725
state means the PVC segment is currently not
1726
operational; the testing(3) state means the PVC
1727
segment is currently undergoing a test. This
1728
state is set by an administrative entity. This
1729
value affects the PVC status indicated across the
1730
ingress NNI/UNI of both end-points of the bi-
1731
directional PVC segment. When a PVC segment
1732
connection is created using this table, this
1733
object is initially set to `inactive(2)'. After
1734
the frPVCConnectRowStatus object is set to
1735
`active(1)' (and the corresponding/associated
1736
entries in the frPVCEndptTable have their
1737
frPVCEndptRowStatus object set to `active(1)'),
1738
the frPVCConnectAdminStatus object may be set to
1739
`active(1)' to turn on the PVC segment
1741
::= { frPVCConnectEntry 6 }
1743
frPVCConnectL2hOperStatus OBJECT-TYPE
1750
MAX-ACCESS read-only
1753
"The value of this object identifies the current
1754
operational status of the PVC segment connection
1755
in one direction; (i.e., in the low to high
1756
direction). This value affects the PVC status
1757
indicated across the ingress NNI/UNI (low side) of
1762
active(1) - PVC is currently operational
1764
inactive(2) - PVC is currently not operational.
1765
This may be because of an underlying
1768
testing(3) - PVC is currently undergoing a test.
1769
This may be because of an underlying
1770
frLport or DS1 undergoing a test.
1773
unknown(4) - the status of the PVC currently can
1775
::= { frPVCConnectEntry 7 }
1777
frPVCConnectH2lOperStatus OBJECT-TYPE
1784
MAX-ACCESS read-only
1787
"The value of this object identifies the current
1788
operational status of the PVC segment connection
1789
in one direction; (i.e., in the high to low
1790
direction).. This value affects the PVC status
1791
indicated across the ingress NNI/UNI (high side)
1796
active(1) - PVC is currently operational
1798
inactive(2) - PVC is currently not operational.
1799
This may be because of an underlying
1802
testing(3) - PVC is currently undergoing a test.
1803
This may be because of an underlying
1804
frLport or DS1 undergoing a test.
1806
unknown(4) - the status of the PVC currently can
1808
::= { frPVCConnectEntry 8 }
1810
frPVCConnectL2hLastChange OBJECT-TYPE
1812
MAX-ACCESS read-only
1815
"The value of the Interface MIB's sysUpTime object
1816
at the time this PVC segment entered its current
1817
operational state in the low to high direction.
1818
If the current state was entered prior to the last
1819
re-initialization of the FRS agent, then this
1820
object contains a zero value."
1823
::= { frPVCConnectEntry 9 }
1825
frPVCConnectH2lLastChange OBJECT-TYPE
1827
MAX-ACCESS read-only
1830
"The value of the Interface MIB's sysUpTime object
1831
at the time this PVC segment entered its current
1832
operational state in the high to low direction.
1833
If the current state was entered prior to the last
1834
re-initialization of the FRS agent, then this
1835
object contains a zero value."
1836
::= { frPVCConnectEntry 10 }
1838
frPVCConnectRowStatus OBJECT-TYPE
1840
MAX-ACCESS read-create
1843
"The status of this entry in the
1844
frPVCConnectTable. This variable is used to
1845
create new connections for the PVC end-points and
1846
to change existing connections of the PVC end-
1847
points. This object must be initially set to
1848
`createAndWait(5)'. In this state, the agent
1849
checks the parameters in the associated entries in
1850
the frPVCEndptTable to verify that the PVC end-
1851
points can be connected (i.e., the In parameters
1852
for one PVC end-point are equal to the Out
1853
parameters for the other PVC end-point). This
1854
object can not be set to `active(1)' unless the
1855
following columnar object exists in this row:
1856
frPVCConnectAdminStatus. The agent also supplies
1857
the associated value of frPVCConnectIndex for the
1858
frPVCEndptConnectIdentifier instances. To turn on
1859
a PVC segment connection, the
1860
frPVCConnectAdminStatus is set to `active(1)'."
1861
::= { frPVCConnectEntry 11 }
1863
frPVCConnectUserName OBJECT-TYPE
1864
SYNTAX SnmpAdminString
1865
MAX-ACCESS read-create
1868
"This is a service user assigned textual
1869
representation of a PVC."
1870
::= { frPVCConnectEntry 12 }
1873
frPVCConnectProviderName OBJECT-TYPE
1874
SYNTAX SnmpAdminString
1875
MAX-ACCESS read-create
1878
"This is a system supplied textual representation
1879
of PVC. It is assigned by the service provider."
1880
::= { frPVCConnectEntry 13 }
1883
-- The Frame Relay Accounting
1886
frAccountPVCTable OBJECT-TYPE
1887
SYNTAX SEQUENCE OF FrAccountPVCEntry
1888
MAX-ACCESS not-accessible
1891
"The Frame Relay Accounting PVC table. This table
1892
is used to perform accounting on a PVC segment
1894
::= { frnetservObjects 6 }
1896
frAccountPVCEntry OBJECT-TYPE
1897
SYNTAX FrAccountPVCEntry
1898
MAX-ACCESS not-accessible
1901
"An entry in the Frame Relay Accounting PVC
1904
frAccountPVCDLCIIndex }
1905
::= { frAccountPVCTable 1 }
1907
FrAccountPVCEntry ::=
1909
frAccountPVCDLCIIndex Integer32,
1910
frAccountPVCSegmentSize Integer32,
1911
frAccountPVCInSegments Counter32,
1912
frAccountPVCOutSegments Counter32
1915
frAccountPVCDLCIIndex OBJECT-TYPE
1916
SYNTAX Integer32 (16..4194303)
1917
MAX-ACCESS not-accessible
1920
"The value of this object is equal to the DLCI
1923
value for this PVC segment end-point."
1924
REFERENCE "Q.922 [25]"
1925
::= { frAccountPVCEntry 1 }
1927
frAccountPVCSegmentSize OBJECT-TYPE
1930
MAX-ACCESS read-only
1933
"The value of this object is equal to the Segment
1934
Size for this PVC segment end-point."
1935
::= { frAccountPVCEntry 2 }
1937
frAccountPVCInSegments OBJECT-TYPE
1940
MAX-ACCESS read-only
1943
"The value of this object is equal to the number
1944
of segments received by this PVC segment end-
1946
::= { frAccountPVCEntry 3 }
1948
frAccountPVCOutSegments OBJECT-TYPE
1951
MAX-ACCESS read-only
1954
"The value of this object is equal to the number
1955
of segments sent by this PVC segment end-point."
1956
::= { frAccountPVCEntry 4 }
1959
-- Accounting on a Frame Relay Logical Port
1962
frAccountLportTable OBJECT-TYPE
1963
SYNTAX SEQUENCE OF FrAccountLportEntry
1964
MAX-ACCESS not-accessible
1967
"The Frame Relay Accounting Logical Port table.
1968
This table is used to perform accounting on a
1969
UNI/NNI Logical Port basis."
1970
::= { frnetservObjects 7 }
1973
frAccountLportEntry OBJECT-TYPE
1974
SYNTAX FrAccountLportEntry
1975
MAX-ACCESS not-accessible
1978
"An entry in the Frame Relay Accounting Logical
1981
::= { frAccountLportTable 1 }
1983
FrAccountLportEntry ::=
1985
frAccountLportSegmentSize
1987
frAccountLportInSegments
1989
frAccountLportOutSegments
1993
frAccountLportSegmentSize OBJECT-TYPE
1996
MAX-ACCESS read-only
1999
"The value of this object is equal to the Segment
2000
Size for this UNI/NNI logical port."
2001
::= { frAccountLportEntry 1 }
2003
frAccountLportInSegments OBJECT-TYPE
2006
MAX-ACCESS read-only
2009
"The value of this object is equal to the number
2010
of segments received by this UNI/NNI logical
2012
::= { frAccountLportEntry 2 }
2014
frAccountLportOutSegments OBJECT-TYPE
2017
MAX-ACCESS read-only
2020
"The value of this object is equal to the number
2023
of segments sent by this UNI/NNI logical port."
2024
::= { frAccountLportEntry 3 }
2027
-- Frame Relay Network Service Notifications
2030
frPVCConnectStatusChange NOTIFICATION-TYPE
2031
OBJECTS { frPVCConnectIndex,
2032
frPVCConnectLowIfIndex,
2033
frPVCConnectLowDLCIIndex,
2034
frPVCConnectHighIfIndex,
2035
frPVCConnectHighDLCIIndex,
2036
frPVCConnectL2hOperStatus,
2037
frPVCConnectH2lOperStatus,
2038
frPVCEndptRcvdSigStatus }
2041
"Refer to the description of the
2042
frPVCConnectStatusNotif notification that has
2043
replaced this notification. The notification is
2044
deprecated due to the incorrect inclusion of index
2045
values and to take advantage of the trap prefix
2046
for automatic conversion from SMIv2 to SMIv1 by
2047
making the one but last sub-ID a zero (i.e. the
2048
so-called trap prefix)."
2049
::= { frnetservTraps 1 }
2051
frPVCConnectStatusNotif NOTIFICATION-TYPE
2052
OBJECTS { frPVCConnectL2hOperStatus,
2053
frPVCConnectH2lOperStatus,
2054
frPVCEndptRcvdSigStatus }
2057
"This notification indicates that the indicated
2058
PVC has changed state.
2060
This notification is not sent if an FR-UNI changes
2061
state; a linkDown or linkUp notification should be
2062
sent instead. The first instance of
2063
frPVCEndptRcvdSigStatus is for the endpoint with
2064
LowIfIndex, LowDLCIIndex. The second instance of
2065
frPVCEndptRcvdSigStatus is for the endpoint with
2066
HighIfIndex, HighDLCIIndex"
2067
::= { frnetservTrapsPrefix 2 }
2069
-- Conformance Information
2073
frnetservConformance OBJECT IDENTIFIER
2074
::= { frnetservMIB 3 }
2076
frnetservGroups OBJECT IDENTIFIER
2077
::= { frnetservConformance 1 }
2078
frnetservCompliances OBJECT IDENTIFIER
2079
::= { frnetservConformance 2 }
2083
-- Service (Read-only) Modules
2085
frnetservCompliance2 MODULE-COMPLIANCE
2088
"The compliance statement for SNMP entities which
2089
have Frame Relay Network Service Interfaces.
2091
The distinction between 'service' and 'switch' is
2092
that a 'switch' is configured via this MIB.
2093
Hence, the various read/write objects have write
2094
capability. A 'service' represents a passive
2095
monitor-only customer network management
2096
interface. The various read/write objects are
2097
restricted to read-only capability."
2098
MODULE -- this module
2099
MANDATORY-GROUPS { frnetservLportGroup2,
2100
frnetservMgtVCSigGroup,
2101
frnetservPVCEndptGroup,
2102
frnetservPVCEndptGroup2,
2103
frnetservPVCConnectGroup,
2104
frnetservPVCConnectNamesGroup,
2105
frnetservPVCNotifGroup2 }
2107
GROUP frnetservAccountPVCGroup
2109
"This group is optional for frame relay
2110
interfaces. It is mandatory if and only if
2111
accounting is performed on a PVC basis this frame
2113
GROUP frnetservAccountLportGroup
2115
"This group is optional for frame relay
2116
interfaces. It is mandatory if and only if
2117
accounting is performed on a logical port basis
2118
this frame relay interface."
2120
OBJECT frPVCEndptInMaxFrameSize
2123
MIN-ACCESS read-only
2125
"Write access is not required."
2127
OBJECT frPVCEndptInBc
2128
MIN-ACCESS read-only
2130
"Write access is not required."
2132
OBJECT frPVCEndptInBe
2133
MIN-ACCESS read-only
2135
"Write access is not required."
2137
OBJECT frPVCEndptInCIR
2138
MIN-ACCESS read-only
2140
"Write access is not required."
2142
OBJECT frPVCEndptOutMaxFrameSize
2143
MIN-ACCESS read-only
2145
"Write access is not required."
2147
OBJECT frPVCEndptOutBc
2148
MIN-ACCESS read-only
2150
"Write access is not required."
2152
OBJECT frPVCEndptOutBe
2153
MIN-ACCESS read-only
2155
"Write access is not required."
2157
OBJECT frPVCEndptOutCIR
2158
MIN-ACCESS read-only
2160
"Write access is not required."
2162
OBJECT frPVCEndptRowStatus
2163
-- subset of RowStatus
2164
SYNTAX INTEGER { active(1) }
2165
MIN-ACCESS read-only
2167
"Write access is not required, and only one of the
2168
six enumerated values for the RowStatus textual
2169
convention need be supported, specifically:
2173
OBJECT frPVCConnectAdminStatus
2174
MIN-ACCESS read-only
2176
"Write access is not required."
2178
OBJECT frPVCConnectRowStatus
2179
-- subset of RowStatus
2180
SYNTAX INTEGER { active(1) }
2181
MIN-ACCESS read-only
2183
"Write access is not required, and only one of the
2184
six enumerated values for the RowStatus textual
2185
convention need be supported, specifically:
2188
OBJECT frLportFragControl
2189
MIN-ACCESS read-only
2191
"Write access is not required."
2193
OBJECT frLportFragSize
2194
MIN-ACCESS read-only
2196
"Write access is not required."
2198
OBJECT frPVCConnectUserName
2199
MIN-ACCESS read-only
2201
"Write access is not required."
2203
OBJECT frPVCConnectProviderName
2204
MIN-ACCESS read-only
2206
"Write access is not required."
2208
::= { frnetservCompliances 2 }
2211
-- Switch (Configuration) Compliance
2213
frnetSwitchCompliance MODULE-COMPLIANCE
2216
"The compliance statement for SNMP entities which
2217
have Frame Relay Network Switch objects.
2219
The distinction between 'service' and 'switch' is
2220
that a 'switch' is configured via this MIB.
2223
Hence, the various read/write objects have write
2224
capability. A 'service' represents a passive
2225
monitor-only customer network management
2226
interface. The various read/write objects are
2227
restricted to read-only capability."
2228
MODULE -- this module
2229
MANDATORY-GROUPS { frnetservLportGroup2,
2230
frnetservLportAdminGroup,
2231
frnetservMgtVCSigGroup,
2232
frnetservMgtVCSigAdminGroup,
2233
frnetservPVCEndptGroup,
2234
frnetservPVCEndptGroup2,
2235
frnetservPVCConnectGroup,
2236
frnetservPVCConnectNamesGroup,
2237
frnetservPVCNotifGroup2 }
2239
GROUP frnetservAccountPVCGroup
2241
"This group is optional for frame relay
2242
interfaces. It is mandatory if and only if
2243
accounting is performed on a PVC basis this frame
2245
GROUP frnetservAccountLportGroup
2247
"This group is optional for frame relay
2248
interfaces. It is mandatory if and only if
2249
accounting is performed on a logical port basis
2250
this frame relay interface."
2252
::= { frnetservCompliances 3 }
2255
-- Historical RFC 1604 Compliance Modules
2258
frnetservCompliance MODULE-COMPLIANCE
2261
"The compliance statement for SNMP entities which
2262
have Frame Relay Network Service Interfaces.
2264
This compliance statement has been deprecated in
2265
favor of frnetservCompliance2. The new compliance
2266
module expands the mandatory groups to include
2267
notification and other new objects."
2269
MODULE -- this module
2270
MANDATORY-GROUPS { frnetservLportGroup,
2273
frnetservMgtVCSigGroup,
2274
frnetservPVCEndptGroup,
2275
frnetservPVCConnectGroup }
2277
GROUP frnetservAccountPVCGroup
2279
"This group is optional for Frame Relay
2280
interfaces. It is mandatory if and only if
2281
accounting is performed on a PVC basis this Frame
2284
GROUP frnetservAccountLportGroup
2286
"This group is optional for Frame Relay
2287
interfaces. It is mandatory if and only if
2288
accounting is performed on a logical port basis
2289
this Frame Relay interface."
2291
OBJECT frPVCEndptInMaxFrameSize
2292
MIN-ACCESS read-only
2294
"Write access is not required."
2296
OBJECT frPVCEndptInBc
2297
MIN-ACCESS read-only
2299
"Write access is not required."
2300
OBJECT frPVCEndptInBe
2301
MIN-ACCESS read-only
2303
"Write access is not required."
2305
OBJECT frPVCEndptInCIR
2306
MIN-ACCESS read-only
2308
"Write access is not required."
2310
OBJECT frPVCEndptOutMaxFrameSize
2311
MIN-ACCESS read-only
2313
"Write access is not required."
2315
OBJECT frPVCEndptOutBc
2316
MIN-ACCESS read-only
2318
"Write access is not required."
2320
OBJECT frPVCEndptOutBe
2323
MIN-ACCESS read-only
2325
"Write access is not required."
2327
OBJECT frPVCEndptOutCIR
2328
MIN-ACCESS read-only
2330
"Write access is not required."
2332
OBJECT frPVCEndptRowStatus
2333
-- subset of RowStatus
2334
SYNTAX INTEGER { active(1) }
2335
MIN-ACCESS read-only
2337
"Write access is not required, and only one of the
2338
six enumerated values for the RowStatus textual
2339
convention need be supported, specifically:
2342
OBJECT frPVCConnectAdminStatus
2343
MIN-ACCESS read-only
2345
"Write access is not required."
2347
OBJECT frPVCConnectRowStatus
2348
-- subset of RowStatus
2349
SYNTAX INTEGER { active(1) }
2350
MIN-ACCESS read-only
2352
"Write access is not required, and only one of the
2353
six enumerated values for the RowStatus textual
2354
convention need be supported, specifically:
2356
::= { frnetservCompliances 1 }
2359
-- Frame Relay Service MIB Object Groups
2361
frnetservLportGroup OBJECT-GROUP
2362
OBJECTS { frLportNumPlan, frLportContact, frLportLocation,
2364
frLportAddrDLCILen, frLportVCSigProtocol,
2365
frLportVCSigPointer }
2368
"A collection of objects providing information
2369
applicable to a Frame Relay Logical Port. This
2370
group has been deprecated to eliminate reference
2373
to the object frLportVCSigPointer.
2375
Use the new group frnetservLportGroup2 as a
2376
replacement for this group."
2377
::= { frnetservGroups 1 }
2379
frnetservMgtVCSigGroup OBJECT-GROUP
2380
OBJECTS { frMgtVCSigProced,
2390
frMgtVCSigUserLinkRelErrors,
2391
frMgtVCSigUserProtErrors,
2392
frMgtVCSigUserChanInactive,
2393
frMgtVCSigNetLinkRelErrors,
2394
frMgtVCSigNetProtErrors,
2395
frMgtVCSigNetChanInactive }
2398
"A collection of objects providing information
2399
applicable to the Local In-Channel Signaling
2400
Procedures used for a UNI/NNI logical port."
2401
::= { frnetservGroups 2 }
2403
frnetservPVCEndptGroup OBJECT-GROUP
2404
OBJECTS { frPVCConnectIndexValue,
2405
frPVCEndptInMaxFrameSize,
2409
frPVCEndptOutMaxFrameSize,
2413
frPVCEndptConnectIdentifier,
2414
frPVCEndptRowStatus,
2415
frPVCEndptRcvdSigStatus,
2417
frPVCEndptOutFrames,
2418
frPVCEndptInDEFrames,
2419
frPVCEndptInExcessFrames,
2420
frPVCEndptOutExcessFrames,
2423
frPVCEndptInDiscards,
2425
frPVCEndptOutOctets }
2428
"A collection of objects providing information
2429
applicable to a Frame Relay PVC end-point."
2430
::= { frnetservGroups 3 }
2432
frnetservPVCConnectGroup OBJECT-GROUP
2433
OBJECTS { frPVCConnectAdminStatus,
2434
frPVCConnectL2hOperStatus,
2435
frPVCConnectH2lOperStatus,
2436
frPVCConnectL2hLastChange,
2437
frPVCConnectH2lLastChange,
2438
frPVCConnectRowStatus }
2441
"A collection of objects providing information
2442
applicable to a Frame Relay PVC connection."
2443
::= { frnetservGroups 4 }
2445
frnetservAccountPVCGroup OBJECT-GROUP
2446
OBJECTS { frAccountPVCSegmentSize,
2447
frAccountPVCInSegments,
2448
frAccountPVCOutSegments }
2451
"A collection of objects providing accounting
2452
information application to a Frame Relay PVC end-
2454
::= { frnetservGroups 5 }
2456
frnetservAccountLportGroup OBJECT-GROUP
2457
OBJECTS { frAccountLportSegmentSize,
2458
frAccountLportInSegments,
2459
frAccountLportOutSegments }
2462
"A collection of objects providing accounting
2463
information application to a Frame Relay logical
2465
::= { frnetservGroups 6 }
2467
frnetservLportGroup2 OBJECT-GROUP
2468
OBJECTS { frLportNumPlan,
2475
frLportVCSigProtocol,
2480
"A collection of objects providing information
2481
applicable to a Frame Relay Logical Port.
2483
This new version of the Logical Port Group
2484
eliminates the frLportVCSigPointer and adds
2485
support for fragmentation."
2486
::= { frnetservGroups 7 }
2488
frnetservPVCEndptGroup2 OBJECT-GROUP
2489
OBJECTS { frPVCEndptInDiscardsDESet,
2490
frPVCEndptInFramesFECNSet,
2491
frPVCEndptOutFramesFECNSet,
2492
frPVCEndptInFramesBECNSet,
2493
frPVCEndptOutFramesBECNSet,
2494
frPVCEndptInCongDiscards,
2495
frPVCEndptInDECongDiscards,
2496
frPVCEndptOutCongDiscards,
2497
frPVCEndptOutDECongDiscards,
2498
frPVCEndptOutDEFrames,
2499
frPVCEndptAtmIwfConnIndex }
2502
"Additions to the PVC end-point group. These
2503
additions provide new frame counters to track
2504
frame loss. In addition, the new FR/ATM IWF MIB
2505
cross-connect index is included."
2506
::= { frnetservGroups 8 }
2508
frnetservPVCConnectNamesGroup OBJECT-GROUP
2509
OBJECTS { frPVCConnectUserName,
2510
frPVCConnectProviderName }
2513
"Additions to the PVC Connect Group."
2514
::= { frnetservGroups 9 }
2516
frnetservLportAdminGroup OBJECT-GROUP
2517
OBJECTS { frLportDLCIIndexValue,
2519
frLportVCSigProtocolAdmin }
2524
"Administrative (R/W) objects for creating a
2525
switch logical port."
2526
::= { frnetservGroups 10 }
2528
frnetservMgtVCSigAdminGroup OBJECT-GROUP
2529
OBJECTS { frMgtVCSigProcedAdmin,
2530
frMgtVCSigUserN391Admin,
2531
frMgtVCSigUserN392Admin,
2532
frMgtVCSigUserN393Admin,
2533
frMgtVCSigUserT391Admin,
2534
frMgtVCSigNetN392Admin,
2535
frMgtVCSigNetN393Admin,
2536
frMgtVCSigNetT392Admin,
2537
frMgtVCSigNetnT3Admin }
2541
"A collection of objects providing information
2542
applicable to the Local In-Channel Signaling
2543
Procedures used for a UNI/NNI logical port."
2544
::= { frnetservGroups 11 }
2546
frnetservPVCNotifGroup NOTIFICATION-GROUP
2547
NOTIFICATIONS { frPVCConnectStatusChange }
2550
"Deprecated notification group. The
2551
frPVCConnectStatusChange notification was flawed
2552
because it included redundant indexes and was not
2553
properly encoded for SMIv1 conversion."
2554
::= { frnetservGroups 12 }
2556
frnetservPVCNotifGroup2 NOTIFICATION-GROUP
2557
NOTIFICATIONS { frPVCConnectStatusNotif }
2560
"A collection of notifications that apply to frame
2561
relay PVC Connections "
2562
::= { frnetservGroups 13 }