This repository has been archived by the owner. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 39
/
Copy pathLAN-EMULATION-CLIENT-MIB
2528 lines (2146 loc) · 114 KB
/
LAN-EMULATION-CLIENT-MIB
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
-- *****************************************************************
-- LAN-EMULATION-CLIENT-MIB.my: LEC MIB file
--
-- July 1995, Andy Bierman
--
-- MIB for configuration, performance, and fault management of ATM
-- LAN Emulation Clients.
--
-- document:
-- atm94-0737R4.txt
--
-- Copyright (c) 1994-1996 by cisco Systems, Inc.
-- All rights reserved.
--
-- *****************************************************************
--
--
LAN-EMULATION-CLIENT-MIB DEFINITIONS ::= BEGIN
IMPORTS
MODULE-IDENTITY, OBJECT-TYPE,
enterprises, Counter32, Integer32 FROM SNMPv2-SMI
TEXTUAL-CONVENTION, MacAddress,
RowStatus, TruthValue, DisplayString FROM SNMPv2-TC
MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF
ifIndex FROM RFC1213-MIB;
-- this import causes too much grief for mosy
-- cloned from RFC 1271 instead (maybe temp)
--
-- OwnerString FROM RFC1271-MIB;
--
-- ------------------------------------------------------------ --
--
-- The following OBJECT IDENTIFIER definition should be moved to
-- some other location, to conform with the statement in RFC 1442
-- that the MODULE-IDENTITY section must appear immediately after
-- any IMPORTs or EXPORTs statements.
--
-- However, some MIB utilities don't like MODULE-IDENTITY OIDs of
-- the form { enterprises atmForum(353) ... 1 }. Separate OBJECT
-- IDENTIFIER definitions appear to be more widely accepted - so,
-- in the interests of compatibility, it remains.
--
-- ------------------------------------------------------------ --
-- The object identifier subtree for ATM Forum LAN Emulation MIBs
-- atmForum OBJECT IDENTIFIER ::= { enterprises 353 }
-- atmForumNetworkManagement OBJECT IDENTIFIER ::= { atmForum 5 }
-- atmfLanEmulation OBJECT IDENTIFIER ::= { atmForumNetworkManagement 3 }
atmfLanEmulation OBJECT IDENTIFIER ::= {
enterprises
atmForum(353)
atmForumNetworkManagement(5)
3
}
leClientMIB MODULE-IDENTITY
LAST-UPDATED "9505100000Z"
ORGANIZATION "ATM Forum LAN Emulation Sub-Working Group"
CONTACT-INFO
"
The ATM Forum
303 Vintage Park Drive
Foster City, CA 94404
United States of America
Tel: 415-578-6860
E-mail: [email protected]"
DESCRIPTION
"This module defines a portion of the management
information base (MIB) for managing ATM LAN Emulation
Client nodes. It is meant to be used in connection with
the AToM MIB and MIB-II / RFC 1573 'ifTable' entries
for each LEC / emulated 802.x network interface."
::= { atmfLanEmulation 1 }
leClientMIBObjects OBJECT IDENTIFIER ::= { leClientMIB 1 }
-- This MIB module consists of the following groups:
--
-- (1) LAN Emulation Client groups
-- (a) Configuration group
-- (b) Status group
-- (c) Statistics group
-- (d) Server VCC group
--
-- (2) LEC ATM Addresses group
--
-- (3) Registered LAN Destination groups
-- (a) MAC addresses group
-- (b) Route Descriptors group
--
-- (4) LE_ARP cache groups
-- (a) MAC address cache group
-- (b) Route descriptor cache group
--
-- (5) ifIndex mapping group
--
-- Security management objects have been explicitly omitted from
-- this MIB as being outside the scope of the V1.0 LAN Emulation
-- specification.
-- TEMP OwnerString cut-and-paste from RFC 1271
OwnerString ::= DisplayString
-- This data type is used to model an administratively
-- assigned name of the owner of a resource. This
-- information is taken from the NVT ASCII character set.
-- It is suggested that this name contain one or more
-- of the following:
-- IP address, management station name, network manager's
-- name, location, or phone number.
-- In some cases the agent itself will be the owner of
-- an entry. In these cases, this string shall be set
-- to a string starting with 'monitor'.
-- SNMP access control is articulated entirely in terms of
-- the contents of MIB views; access to a particular SNMP
-- object instance depends only upon its presence or
-- absence in a particular MIB view and never upon its
-- value or the value of related object instances. Thus,
-- objects of this type afford resolution of resource
-- contention only among cooperating managers; they
-- realize no access control function with respect
-- to uncooperative parties.
--
-- By convention, objects with this syntax are declared
-- as having
--
-- SIZE (0..127)
AtmLaneAddress ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"A twenty-octet binary string, containing a standard
ATM Forum address -- or the zero-length string,
indicating the absence of an address.
For LAN Emulation purposes, the eight-octet address
format is not used."
SYNTAX OCTET STRING ( SIZE( 0 | 20 ) )
VpiInteger ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"An integer large enough to hold a VPI."
SYNTAX INTEGER ( 0..255 )
VciInteger ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"An integer large enough to hold a VCI."
SYNTAX INTEGER ( 0..65535 )
LeConnectionInterface ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"A combination flag and ifTable index, indicating
whether a LAN Emulation circuit exists - and, if
so, which interface is associated with it at the
point where it connects to a LE Client.
Objects of this type are always defined as part of
a set that includes
fooInterface LeConnectionInterface
fooVpi VpiInteger
fooVci VciInteger
The interpretation of these objects is as follows.
1. If no connection exists, 'fooInterface' has a
value of 0. Because Interfaces table entries
always have 'ifIndex' values larger than 0,
'fooInterface' reliably serves as a 'connection
exists' flag.
In this case, 'fooVpi' and 'fooVci' are
meaningless, and have the value 0.
2. If a PVC or SVC exists, 'fooInterface' is defined
to have the value of the MIB-II/RFC 1573 'ifIndex'
of the 'atm' interface associated with the VCC.
'fooVpi' and 'fooVci' will contain its VPI/VCI.
Therefore, ('fooInterface', 'fooVpi', 'fooVci')
give you an index into the AToM MIB which allows
you to examine and play with the circuit further.
3. If a proprietary connection (such as an internal
data path between co-located components) exists,
this specification does not mandate how it should
be managed. One option is to set 'fooInterface'
to the value of the MIB-II/RFC 1573 'ifIndex' for
the LAN Emulation Client. This indicates that a
connection exists, but is not being managed in the
same fashion as an ATM VCC."
SYNTAX INTEGER ( 0..2147483647 )
LecState ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"An official protocol state of a LAN Emulation Client."
REFERENCE
"ATM Forum LAN Emulation Over ATM Specification, V1.0,
Section 2.3.1"
SYNTAX INTEGER {
initialState(1),
lecsConnect(2),
configure(3),
join(4),
initialRegistration(5),
busConnect(6),
operational(7)
}
LecDataFrameFormat ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"A 'LAN Type' value.
C2 LAN Type. The type of LAN that the LE Client is,
or wishes to become, a member of. This MUST be one
of Ethernet/IEEE 802.3, IEEE 802.5, or Unspecified."
REFERENCE
"ATM Forum LAN Emulation Over ATM Specification, V1.0,
Section 5.1.1"
SYNTAX INTEGER {
unspecified(1),
aflane8023(2),
aflane8025(3)
}
LecDataFrameSize ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"A 'Maximum Data Frame Size' value.
C3 Maximum Data Frame Size. The maximum AAL-5 SDU size
of a data frame that the LE Client wishes to send on
the Multicast Send VCC or to receive on the
Multicast Send VCC or Multicast Forward VCC. This
parameter also specifies the maximum AAL-5 SDU on
all of a LE Client's Data Direct VCCs. This MUST be
either 1516, 4544, 9234, or 18190 octets, or
Unspecified."
REFERENCE
"ATM Forum LAN Emulation Over ATM Specification, V1.0,
Section 5.1.1"
SYNTAX INTEGER {
unspecified(1),
max1516(2),
max4544(3),
max9234(4),
max18190(5)
}
LeArpTableEntryType ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"Indicates how a LE_ARP table entry was created and
whether it is subject to aging.
other(1)
The LE_ARP entry does not fall into one of
the categories defined below.
learnedViaControl(2)
This LE_ARP entry was learned by using the
LE_ARP_REQUEST / LE_ARP_RESPONSE protocol,
or by otherwise observing relevant traffic
on Control VCCs.
Entries of this type are aged.
learnedViaData(3)
This LE_ARP entry was learned by observing
incoming traffic on Data VCCs.
Entries of this type are aged.
staticVolatile(4)
This LE_ARP entry was created by management.
It will not be aged. On the other hand, it
will not survive a restart of the client.
If an agent permits LE_ARP entries of this
type to be created, it may require that the
LAN Emulation Client be in the 'operational'
state at the time.
staticNonVolatile(5)
This LE_ARP entry was created by management.
It will not be aged, and it will survive a
restart of the client.
The values 'learnedViaData' and 'learnedViaControl'
can be read, but may not be written."
SYNTAX INTEGER {
other(1),
learnedViaControl(2),
learnedViaData(3),
staticVolatile(4),
staticNonVolatile(5)
}
-- ------------------------------------------------------------- --
--
-- LAN Emulation Client configuration group
--
lecConfigTable OBJECT-TYPE
SYNTAX SEQUENCE OF LecConfigEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A table describing all of the LAN Emulation Clients
implemented by this host. Each LE Client has a row
in the MIB-II/RFC 1573 Interfaces table (describing
the emulated packet interface it presents to higher
layers). Each LE Client also has a row in this and
other LEC MIB tables (describing its interface with
other LAN Emulation components).
This table contains configuration variables. Three
extension tables contain client status, performance
statistics, and information about control/multicast
VCCs.
Unlike hardware ports, LE Clients can be created by
management. However, the RFC 1573 Interfaces table
does not directly support row creation. Therefore,
creating or deleting a row in the lecConfigTable is
defined to have the side effect of creating or
deleting corresponding rows in
- the MIB-II / RFC 1573 Interfaces table,
- the 'lecMappingTable',
- the 'lecStatusTable',
- the 'lecServerVccTable',
- the 'lecStatisticsTable', and
- any other dependent tables
New Interfaces table rows for LAN Emulation Clients
always have 'ifAdminStatus' set to 'down'.
A Note On Indexing:
-------------------
Most of the tables in this MIB are indexed in whole
or in part by 'lecIndex' - not by 'ifIndex'.
Why is there a separate index?
Traditionally, ifIndex values are chosen by agents,
and are permitted to change across restarts. Using
ifIndex to index lecConfigTable could complicate
row creation and/or cause interoperability problems
(if each agent had special restrictions on ifIndex).
Having a separate index avoids these problems. "
::= { leClientMIBObjects 1 }
lecConfigEntry OBJECT-TYPE
SYNTAX LecConfigEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Each table entry contains configuration information
for one LAN Emulation Client.
Most of the objects are derived from Initial State
Parameters in the LAN Emulation specification."
INDEX { lecIndex }
::= { lecConfigTable 1 }
LecConfigEntry ::=
SEQUENCE {
--
-- Row indices, creation, and deletion.
--
lecIndex INTEGER,
lecRowStatus RowStatus,
lecOwner OwnerString,
--
-- Key parameters for Configure / Join phase. Note that
-- these are not operational values - see lecStatusTable
-- for those.
--
lecConfigMode INTEGER,
lecConfigLanType LecDataFrameFormat,
lecConfigMaxDataFrameSize LecDataFrameSize,
lecConfigLanName OCTET STRING,
lecConfigLesAtmAddress AtmLaneAddress,
--
-- Other parameters. These may be changed either by the
-- network manager or by the LE Configuration Server.
--
lecControlTimeout INTEGER,
lecMaxUnknownFrameCount INTEGER,
lecMaxUnknownFrameTime INTEGER,
lecVccTimeoutPeriod Integer32,
lecMaxRetryCount INTEGER,
lecAgingTime INTEGER,
lecForwardDelayTime INTEGER,
lecExpectedArpResponseTime INTEGER,
lecFlushTimeOut INTEGER,
lecPathSwitchingDelay INTEGER,
lecLocalSegmentID INTEGER,
lecMulticastSendType INTEGER,
lecMulticastSendAvgRate Integer32,
lecMulticastSendPeakRate Integer32,
lecConnectionCompleteTimer INTEGER
}
lecIndex OBJECT-TYPE
SYNTAX INTEGER ( 1..2147483647 )
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A value which uniquely identifies this conceptual
row in the lecConfigTable.
If the conceptual row identified by this value of
lecIndex is recreated following an agent restart,
the same value of lecIndex must be used to identify
the recreated row. (However, the Interfaces table
index associated with the client may change.)"
::= { lecConfigEntry 1 }
lecRowStatus OBJECT-TYPE
SYNTAX RowStatus
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This object lets network managers create and delete
LAN Emulation Clients, on systems that support this
optional capability.
It does not control Joins and Terminations; they are
controlled by 'ifAdminStatus'. However, taking rows
out of service will have the side effect of changing
their 'ifAdminStatus' values to 'down', thus causing
any active emulated LAN connections to be terminated.
Within each conceptual lecConfigTable row, objects
which are writable may be modified regardless of the
value of lecRowStatus. It is not necessary to set a
row's status to 'notInService' first.
When creating a LAN Emulation Client, it is up to the
management station to determine a suitable 'lecIndex'.
To facilitate interoperability, agents should not put
any restrictions on the 'lecIndex' beyond the obvious
ones that it be valid and unused.
If you create a LAN Emulation Client via this object,
it will initially have
'ifAdminStatus' = 'down'
'ifOperStatus' = 'down'
'lecInterfaceState' = 'initialState' "
::= { lecConfigEntry 2 }
lecOwner OBJECT-TYPE
SYNTAX OwnerString( SIZE (0..127) )
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The entity that configured this entry and is therefore
using the resources assigned to it."
::= { lecConfigEntry 3 }
lecConfigMode OBJECT-TYPE
SYNTAX INTEGER {
automatic(1),
manual(2)
}
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Indicates whether this LAN Emulation Client should
auto-configure the next time it is (re)started.
In automatic(1) mode, a client uses a LAN Emulation
Configuration Server to learn the ATM address of its
LAN Emulation Server, and to obtain other parameters.
lecConfig{ LanType, MaxDataFrameSize, LanName } are
used in the Configure request. lecConfigLesAtmAddress
is ignored.
In manual(2) mode, management tells the client the
ATM address of its LAN Emulation Server and the
values of other parameters.
lecConfig{ LanType, MaxDataFrameSize, LanName } are
used in the Join request. lecConfigLesAtmAddress
tells the client which LES to call."
REFERENCE
"ATM Forum LAN Emulation Over ATM Specification, V1.0,
Sections 3.4.1.1 and 5.3"
DEFVAL { automatic }
::= { lecConfigEntry 4 }
lecConfigLanType OBJECT-TYPE
SYNTAX LecDataFrameFormat
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"C2 LAN Type.
The data frame format which this client will use the
next time it returns to the Initial State.
Auto-configuring clients use this parameter in their
Configure requests. Manually-configured clients use
it in their Join requests.
This MIB object will not be overwritten with the new
value from a LE_{JOIN,CONFIGURE}_RESPONSE. Instead,
lecActualLanType will be."
REFERENCE
"ATM Forum LAN Emulation Over ATM Specification, V1.0,
Section 5.1.1"
DEFVAL { unspecified }
::= { lecConfigEntry 5 }
lecConfigMaxDataFrameSize OBJECT-TYPE
SYNTAX LecDataFrameSize
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"C3 Maximum Data Frame Size.
The maximum data frame size which this client will
use the next time it returns to the Initial State.
Auto-configuring clients use this parameter in their
Configure requests. Manually-configured clients use
it in their Join requests.
This MIB object will not be overwritten with the new
value from a LE_{JOIN,CONFIGURE}_RESPONSE. Instead,
lecActualMaxDataFrameSize will be."
REFERENCE
"ATM Forum LAN Emulation Over ATM Specification, V1.0,
Section 5.1.1"
DEFVAL { unspecified }
::= { lecConfigEntry 6 }
lecConfigLanName OBJECT-TYPE
SYNTAX OCTET STRING (SIZE( 0..32 ))
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"C5 ELAN Name.
The ELAN Name this client will use the next time it
returns to the Initial State.
Auto-configuring clients use this parameter in their
Configure requests. Manually-configured clients use
it in their Join requests.
This MIB object will not be overwritten with the new
value from a LE_{JOIN,CONFIGURE}_RESPONSE. Instead,
lecActualLanName will be."
REFERENCE
"ATM Forum LAN Emulation Over ATM Specification, V1.0,
Section 5.1.1"
::= { lecConfigEntry 7 }
lecConfigLesAtmAddress OBJECT-TYPE
SYNTAX AtmLaneAddress
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"C9 LE Server ATM Address.
The LAN Emulation Server which this client will use
the next time it is started in manual configuration
mode.
When lecConfigMode is 'automatic', there is no need
to set this address, and no advantage to doing so.
The client will use the LECS to find a LES, putting
the auto-configured address in lecActualLesAtmAddress
while leaving lecConfigLesAtmAddress alone."
REFERENCE
"ATM Forum LAN Emulation Over ATM Specification, V1.0,
Section 5.1.1"
::= { lecConfigEntry 8 }
lecControlTimeout OBJECT-TYPE
SYNTAX INTEGER ( 10..300 )
UNITS "seconds"
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"C7 Control Time-out. Time out period used for
timing out most request/response control frame
interactions, as specified elsewhere [in the
LAN Emulation specification].
This time value is expressed in seconds."
REFERENCE
"ATM Forum LAN Emulation Over ATM Specification, V1.0,
Section 5.1.1"
DEFVAL { 120 }
::= { lecConfigEntry 9 }
lecMaxUnknownFrameCount OBJECT-TYPE
SYNTAX INTEGER ( 1..10 )
UNITS "frames"
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"C10 Maximum Unknown Frame Count. See the description
of lecMaxUnknownFrameTime below."
REFERENCE
"ATM Forum LAN Emulation Over ATM Specification, V1.0,
Section 5.1.1"
DEFVAL { 1 }
::= { lecConfigEntry 10 }
lecMaxUnknownFrameTime OBJECT-TYPE
SYNTAX INTEGER ( 1..60 )
UNITS "seconds"
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"C11 Maximum Unknown Frame Time. Within the period of
time defined by the Maximum Unknown Frame Time, a
LE Client will send no more than Maximum Unknown
Frame Count frames to the BUS for a given unicast
LAN Destination, and it must also initiate the
address resolution protocol to resolve that LAN
Destination.
This time value is expressed in seconds."
REFERENCE
"ATM Forum LAN Emulation Over ATM Specification, V1.0,
Section 5.1.1"
DEFVAL { 1 }
::= { lecConfigEntry 11 }
lecVccTimeoutPeriod OBJECT-TYPE
SYNTAX Integer32
UNITS "seconds"
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"C12 VCC Time-out Period. A LE Client SHOULD release
any Data Direct VCC that it has not used to
transmit or receive any data frames for the
length of the VCC Time-out Period. This parameter
is only meaningful for SVC Data Direct VCCs.
This time value is expressed in seconds. The default
value is 20 minutes. A value of 0 seconds means that
the timeout period is infinite. Negative values will
be rejected by the agent."
REFERENCE
"ATM Forum LAN Emulation Over ATM Specification, V1.0,
Section 5.1.1"
DEFVAL { 1200 }
::= { lecConfigEntry 12 }
lecMaxRetryCount OBJECT-TYPE
SYNTAX INTEGER( 0..2 )
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"C13 Maximum Retry Count. A LE CLient MUST not retry
a LE_ARP_REQUEST for a given frame's LAN
destination more than Maximum Retry Count times,
after the first LE_ARP_REQUEST for that same
frame's LAN destination."
REFERENCE
"ATM Forum LAN Emulation Over ATM Specification, V1.0,
Section 5.1.1"
DEFVAL { 1 }
::= { lecConfigEntry 13 }
lecAgingTime OBJECT-TYPE
SYNTAX INTEGER ( 10..300 )
UNITS "seconds"
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"C17 Aging Time. The maximum time that a LE Client
will maintain an entry in its LE_ARP cache in
the absence of a verification of that
relationship.
This time value is expressed in seconds."
REFERENCE
"ATM Forum LAN Emulation Over ATM Specification, V1.0,
Section 5.1.1"
DEFVAL { 300 }
::= { lecConfigEntry 14 }
lecForwardDelayTime OBJECT-TYPE
SYNTAX INTEGER ( 4..30 )
UNITS "seconds"
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"C18 Forward Delay Time. The maximum time that a LE
Client will maintain an entry for a non-local MAC
address in its LE_ARP cache in the absence of a
verification of that relationship, as long as the
Topology Change flag C19 is true.
lecForwardDelayTime SHOULD BE less than lecAgingTime.
When it is not, lecAgingTime governs LE_ARP aging.
This time value is expressed in seconds."
REFERENCE
"ATM Forum LAN Emulation Over ATM Specification, V1.0,
Section 5.1.1"
DEFVAL { 15 }
::= { lecConfigEntry 15 }
lecExpectedArpResponseTime OBJECT-TYPE
SYNTAX INTEGER ( 1..30 )
UNITS "seconds"
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"C20 Expected LE_ARP Response Time. The maximum time
that the LEC expects an LE_ARP_REQUEST/
LE_ARP_RESPONSE cycle to take. Used for retries
and verifies.
This time value is expressed in seconds."
REFERENCE
"ATM Forum LAN Emulation Over ATM Specification, V1.0,
Section 5.1.1"
DEFVAL { 1 }
::= { lecConfigEntry 16 }
lecFlushTimeOut OBJECT-TYPE
SYNTAX INTEGER ( 1..4 )
UNITS "seconds"
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"C21 Flush Time-out. Time limit to wait to receive a
LE_FLUSH_RESPONSE after the LE_FLUSH_REQUEST has
been sent before taking recovery action.
This time value is expressed in seconds."
REFERENCE
"ATM Forum LAN Emulation Over ATM Specification, V1.0,
Section 5.1.1"
DEFVAL { 4 }
::= { lecConfigEntry 17 }
lecPathSwitchingDelay OBJECT-TYPE
SYNTAX INTEGER ( 1..8 )
UNITS "seconds"
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"C22 Path Switching Delay. The time since sending a
frame to the BUS after which the LE Client may
assume that the frame has been either discarded
or delivered to the recipient. May be used to
bypass the Flush protocol.
This time value is expressed in seconds."
REFERENCE
"ATM Forum LAN Emulation Over ATM Specification, V1.0,
Section 5.1.1"
DEFVAL { 6 }
::= { lecConfigEntry 18 }
lecLocalSegmentID OBJECT-TYPE
SYNTAX INTEGER ( 0..4095 )
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"C23 Local Segment ID. The segment ID of the emulated
LAN. This is only required for IEEE 802.5 clients
that are Source Routing bridges."
REFERENCE
"ATM Forum LAN Emulation Over ATM Specification, V1.0,
Section 5.1.1"
::= { lecConfigEntry 19 }
lecMulticastSendType OBJECT-TYPE
SYNTAX INTEGER {
bestEffort(1),
variableBitRate(2),
constantBitRate(3)
}
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"C24 Multicast Send VCC Type. Signalling parameter
that SHOULD be used by the LE Client when
establishing the Multicast Send VCC.
This is the method to be used by the LE Client
when specifying traffic parameters when it sets
up the Multicast Send VCC for this emulated LAN."
REFERENCE
"ATM Forum LAN Emulation Over ATM Specification, V1.0,
Section 5.1.1"
::= { lecConfigEntry 20 }
lecMulticastSendAvgRate OBJECT-TYPE
SYNTAX Integer32
UNITS "cells per second"
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"C25 Multicast Send VCC AvgRate. Signalling parameter
that SHOULD be used by the LE Client when
establishing the Multicast Send VCC.
Forward and Backward Sustained Cell Rate to be
requested by LE Client when setting up Multicast
Send VCC, if using Variable bit rate codings."
REFERENCE
"ATM Forum LAN Emulation Over ATM Specification, V1.0,
Section 5.1.1"
::= { lecConfigEntry 21 }
lecMulticastSendPeakRate OBJECT-TYPE
SYNTAX Integer32
UNITS "cells per second"
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"C26 Multicast Send VCC PeakRate. Signalling parameter
that SHOULD be used by the LE Client when
establishing the Multicast Send VCC.
Forward and Backward Peak Cell Rate to be
requested by LE Client when setting up the
Multicast Send VCC when using either Variable or
Constant bit rate codings."
REFERENCE
"ATM Forum LAN Emulation Over ATM Specification, V1.0,
Section 5.1.1"
::= { lecConfigEntry 22 }
lecConnectionCompleteTimer OBJECT-TYPE
SYNTAX INTEGER ( 1..10 )
UNITS "seconds"
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"C28 Connection Complete Timer. Optional. In
Connection Establishment this is the time period
in which data or a READY_IND message is expected
from a Calling Party.
This time value is expressed in seconds."
REFERENCE
"ATM Forum LAN Emulation Over ATM Specification, V1.0,
Section 5.1.1"
DEFVAL { 4 }
::= { lecConfigEntry 23 }
-- ------------------------------------------------------------- --
--
-- LAN Emulation Client status group
--
lecStatusTable OBJECT-TYPE
SYNTAX SEQUENCE OF LecStatusEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A read-only table containing identification, status,
and operational information about the LAN Emulation
Clients this agent manages."
::= { leClientMIBObjects 2 }
lecStatusEntry OBJECT-TYPE
SYNTAX LecStatusEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Each table entry contains information about one LAN
Emulation Client."
-- AUGMENTS { lecConfigEntry }
INDEX { lecIndex }
::= { lecStatusTable 1 }
LecStatusEntry ::=
SEQUENCE {
--
-- Client identification
--
lecIfIndex Integer32,
lecPrimaryAtmAddress AtmLaneAddress,
lecID INTEGER,
--
-- Client status and protocol version
--
lecInterfaceState LecState,
lecLastFailureRespCode INTEGER,
lecLastFailureState LecState,
lecProtocol INTEGER,
lecVersion INTEGER,
lecTopologyChange TruthValue,
--
-- Operational parameters and their source
--
lecConfigServerAtmAddress AtmLaneAddress,
lecConfigSource INTEGER,
lecActualLanType LecDataFrameFormat,
lecActualMaxDataFrameSize LecDataFrameSize,
lecActualLanName OCTET STRING,
lecActualLesAtmAddress AtmLaneAddress,
lecProxyClient TruthValue
}
lecIfIndex OBJECT-TYPE
SYNTAX Integer32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object identifies the logical interface number
('ifIndex') assigned to this client, and is used to
identify corresponding rows in the Interfaces MIB.
Note that re-initialization of the management agent
may cause a client's 'lecIfIndex' to change."
::= { lecStatusEntry 1 }
lecPrimaryAtmAddress OBJECT-TYPE
SYNTAX AtmLaneAddress
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"C1 LE Client's ATM Addresses.
The primary ATM address of this LAN Emulation Client.
This address is used to establish the Control Direct
and Multicast Send VCCs, and may also be used to set
up Data Direct VCCs.
A client may have additional ATM addresses for use
with Data Direct VCCs. These addresses are readable
via the lecAtmAddressTable."
REFERENCE
"ATM Forum LAN Emulation Over ATM Specification, V1.0,
Section 5.1.1"
::= { lecStatusEntry 2 }
lecID OBJECT-TYPE
SYNTAX INTEGER( 0..65279 )
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"C14 LE Client Identifier. Each LE Client requires a
LE Client Identifier (LECID) assigned by the LE
Server during the Join phase. The LECID is placed
in control requests by the LE Client and MAY be
used for echo suppression on multicast data frames
sent by that LE Client. This value MUST NOT
change without terminating the LE Client and
returning to the Initial state. A valid LECID
MUST be in the range X'0001' through X'FEFF'.
The value of this object is only meaningful for a LEC
that is connected to a LES. For a LEC which does not
belong to an emulated LAN, the value of this object
is defined to be 0."
REFERENCE