forked from taishin/vendor_mibs
-
Notifications
You must be signed in to change notification settings - Fork 0
/
IEEE8021-CFM-MIB.txt
3693 lines (3313 loc) · 132 KB
/
IEEE8021-CFM-MIB.txt
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
IEEE8021-CFM-MIB DEFINITIONS ::= BEGIN
-- ******************************************************************
-- IEEE P802.1ag(TM) CFM MIB
-- ******************************************************************
IMPORTS
MODULE-IDENTITY,
OBJECT-TYPE,
NOTIFICATION-TYPE,
Integer32, Counter32,
Unsigned32 FROM SNMPv2-SMI -- [RFC2578]
TEXTUAL-CONVENTION,
TimeInterval,
TimeStamp, RowStatus,
TruthValue, MacAddress,
TDomain, TAddress FROM SNMPv2-TC -- [RFC2579]
MODULE-COMPLIANCE,
OBJECT-GROUP,
NOTIFICATION-GROUP FROM SNMPv2-CONF -- [RFC2580]
InterfaceIndex,
InterfaceIndexOrZero FROM IF-MIB -- [RFC2863]
LldpChassisId,
LldpChassisIdSubtype,
LldpPortId,
LldpPortIdSubtype FROM LLDP-MIB -- [IEEExxx]
VlanIdOrNone, VlanId FROM Q-BRIDGE-MIB -- [RFC4363]
;
ieee8021CfmMib MODULE-IDENTITY
LAST-UPDATED "200810150000Z" -- October 15, 2008
ORGANIZATION "IEEE 802.1 Working Group"
CONTACT-INFO
"WG-URL: http://grouper.ieee.org/groups/802/1/index.html
WG-EMail: [email protected]
Contact: David Elie-Dit-Cosaque
Alcatel-Lucent
3400 W. Plano Pkwy.
Plano, TX 75075, USA
E-mail: [email protected]
Contact: Norman Finn
Cisco Systems
170 W. Tasman Drive
San Jose, CA 95134, USA
E-mail: [email protected]
"
DESCRIPTION
"Connectivity Fault Management module for managing IEEE 802.1ag
Unless otherwise indicated, the references in this MIB
module are to IEEE 802.1Q-2005 as amended by IEEE 802.1ad,
IEEE 802.1ak, IEEE 802.1ag and IEEE 802.1ah.
Copyright (C) IEEE.
This version of this MIB module is part of IEEE802.1Q;
see the draft itself for full legal notices."
REVISION "200810150000Z" -- October 15, 2008
DESCRIPTION
"The IEEE8021-CFM-MIB Module was originally included in IEEE
P802.1ag D8.1. Some objects in this module are deprecated and
replaced by objects in the IEEE8021-CFM-V2-MIB module
defined in 802.1ap.
This revision is included in IEEE 802.1ap"
REVISION "200706100000Z" -- 06/10/2007 00:00GMT
DESCRIPTION
"Included in IEEE P802.1ag Draft 8.1
Copyright (C) IEEE802.1."
::= { iso(1) org(3) ieee(111)
standards-association-numbered-series-standards (2)
lan-man-stds (802) ieee802dot1 (1) ieee802dot1mibs (1) 8 }
dot1agNotifications OBJECT IDENTIFIER ::= { ieee8021CfmMib 0 }
dot1agMIBObjects OBJECT IDENTIFIER ::= { ieee8021CfmMib 1 }
dot1agCfmConformance OBJECT IDENTIFIER ::= { ieee8021CfmMib 2 }
-- ******************************************************************
-- Groups in the CFM MIB Module
-- ******************************************************************
dot1agCfmStack OBJECT IDENTIFIER ::= { dot1agMIBObjects 1 }
dot1agCfmDefaultMd OBJECT IDENTIFIER ::= { dot1agMIBObjects 2 }
dot1agCfmVlan OBJECT IDENTIFIER ::= { dot1agMIBObjects 3 }
dot1agCfmConfigErrorList OBJECT IDENTIFIER ::= { dot1agMIBObjects 4 }
dot1agCfmMd OBJECT IDENTIFIER ::= { dot1agMIBObjects 5 }
dot1agCfmMa OBJECT IDENTIFIER ::= { dot1agMIBObjects 6 }
dot1agCfmMep OBJECT IDENTIFIER ::= { dot1agMIBObjects 7 }
-- ******************************************************************
-- Textual conventions
-- ******************************************************************
Dot1agCfmMaintDomainNameType ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"A value that represents a type (and thereby the format)
of a Dot1agCfmMaintDomainName. The value can be one of
the following:
ieeeReserved(0) Reserved for definition by IEEE 802.1
recommend to not use zero unless
absolutely needed.
none(1) No format specified, usually because
there is not (yet) a Maintenance
Domain Name. In this case, a zero
length OCTET STRING for the Domain
Name field is acceptable.
dnsLikeName(2) Domain Name like string, globally unique
text string derived from a DNS name.
macAddrAndUint(3) MAC address + 2-octet (unsigned) integer.
charString(4) RFC2579 DisplayString, except that the
character codes 0-31 (decimal) are not
used.
ieeeReserved(xx) Reserved for definition by IEEE 802.1
xx values can be [5..31] and [64..255]
ituReserved(xx) Reserved for definition by ITU-T Y.1731
xx values range from [32..63]
To support future extensions, the Dot1agCfmMaintDomainNameType
textual convention SHOULD NOT be sub-typed in object type
definitions. It MAY be sub-typed in compliance statements in
order to require only a subset of these address types for a
compliant implementation.
Implementations MUST ensure that Dot1agCfmMaintDomainNameType
objects and any dependent objects (e.g.,
Dot1agCfmMaintDomainName objects) are consistent. An
inconsistentValue error MUST be generated if an attempt to
change an Dot1agCfmMaintDomainNameType object would, for
example, lead to an undefined Dot1agCfmMaintDomainName value.
In particular,
Dot1agCfmMaintDomainNameType/Dot1agCfmMaintDomainName pairs
MUST be changed together if the nameType changes.
"
REFERENCE
"21.6.5, Table 21-19"
SYNTAX INTEGER {
none (1),
dnsLikeName (2),
macAddressAndUint (3),
charString (4)
}
Dot1agCfmMaintDomainName ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"Denotes a generic Maintenance Domain Name.
A Dot1agCfmMaintDomainName value is always interpreted within
the context of a Dot1agCfmMaintDomainNameType value. Every
usage of the Dot1agCfmMaintDomainName textual convention is
required to specify the Dot1agCfmMaintDomainNameType object
that provides the context. It is suggested that the
Dot1agCfmMaintDomainNameType object be logically registered
before the object(s) that use the Dot1agCfmMaintDomainName
textual convention, if they appear in the same logical row.
The value of a Dot1agCfmMaintDomainName object MUST always
be consistent with the value of the associated
Dot1agCfmMaintDomainNameType object. Attempts to set
an Dot1agCfmMaintDomainName object to a value inconsistent
with the associated Dot1agCfmMaintDomainNameType MUST fail
with an inconsistentValue error.
When this textual convention is used as the syntax of an
index object, there may be issues with the limit of 128
sub-identifiers specified in SMIv2, IETF STD 58. In this
case, the object definition MUST include a 'SIZE' clause
to limit the number of potential instance sub-identifiers;
otherwise the applicable constraints MUST be stated in
the appropriate conceptual row DESCRIPTION clauses, or
in the surrounding documentation if there is no single
DESCRIPTION clause that is appropriate.
A value of none(1) in the associated
Dot1agCfmMaintDomainNameType object means that no Maintenance
Domain name is present, and the contents of the
Dot1agCfmMaintDomainName object are meaningless.
See the DESCRIPTION of the Dot1agCfmMaintAssocNameType
TEXTUAL-CONVENTION for a discussion of the length limits on
the Maintenance Domain name and Maintenance Association name.
"
REFERENCE
"21.6.5"
SYNTAX OCTET STRING (SIZE(1..43))
Dot1agCfmMaintAssocNameType ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"A value that represents a type (and thereby the format)
of a Dot1agCfmMaintAssocName. The value can be one of
the following:
ieeeReserved(0) Reserved for definition by IEEE 802.1
recommend to not use zero unless
absolutely needed.
primaryVid(1) Primary VLAN ID.
12 bits represented in a 2-octet integer:
- 4 least significant bits of the first
byte contains the 4 most significant
bits of the 12 bits primary VID
- second byte contains the 8 least
significant bits of the primary VID
0 1 2 3 4 5 6 7 8
+-+-+-+-+-+-+-+-+
|0 0 0 0| (MSB) |
+-+-+-+-+-+-+-+-+
| VID LSB |
+-+-+-+-+-+-+-+-+
charString(2) RFC2579 DisplayString, except that the
character codes 0-31 (decimal) are not
used. (1..45) octets
unsignedInt16 (3) 2-octet integer/big endian
rfc2865VpnId(4) RFC 2685 VPN ID
3 octet VPN authority Organizationally
Unique Identifier followed by 4 octet VPN
index identifying VPN according to the OUI:
0 1 2 3 4 5 6 7 8
+-+-+-+-+-+-+-+-+
| VPN OUI (MSB) |
+-+-+-+-+-+-+-+-+
| VPN OUI |
+-+-+-+-+-+-+-+-+
| VPN OUI (LSB) |
+-+-+-+-+-+-+-+-+
|VPN Index (MSB)|
+-+-+-+-+-+-+-+-+
| VPN Index |
+-+-+-+-+-+-+-+-+
| VPN Index |
+-+-+-+-+-+-+-+-+
|VPN Index (LSB)|
+-+-+-+-+-+-+-+-+
ieeeReserved(xx) Reserved for definition by IEEE 802.1
xx values can be [5..31] and [64..255]
ituReserved(xx) Reserved for definition by ITU-T Y.1731
xx values range from [32..63]
To support future extensions, the Dot1agCfmMaintAssocNameType
textual convention SHOULD NOT be sub-typed in object type
definitions. It MAY be sub-typed in compliance statements in
order to require only a subset of these address types for a
compliant implementation.
Implementations MUST ensure that Dot1agCfmMaintAssocNameType
objects and any dependent objects (e.g.,
Dot1agCfmMaintAssocName objects) are consistent. An
inconsistentValue error MUST be generated if an attempt to
change an Dot1agCfmMaintAssocNameType object would, for
example, lead to an undefined Dot1agCfmMaintAssocName value.
In particular,
Dot1agCfmMaintAssocNameType/Dot1agCfmMaintAssocName pairs
MUST be changed together if the nameType changes.
The Maintenance Domain name and Maintenance Association name,
when put together into the CCM PDU, MUST total 48 octets or
less. If the Dot1agCfmMaintDomainNameType object contains
none(1), then the Dot1agCfmMaintAssocName object MUST be
45 octets or less in length. Otherwise, the length of
the Dot1agCfmMaintDomainName object plus the length of the
Dot1agCfmMaintAssocName object, added together, MUST total
less than or equal to 44 octets.
"
REFERENCE
"21.6.5.4, Table 21-20"
SYNTAX INTEGER {
primaryVid (1),
charString (2),
unsignedInt16 (3),
rfc2865VpnId (4)
}
Dot1agCfmMaintAssocName ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"Denotes a generic Maintenance Association Name. It is the
part of the Maintenance Association Identifier which is
unique within the Maintenance Domain Name and is appended
to the Maintenance Domain Name to form the Maintenance
Association Identifier (MAID).
A Dot1agCfmMaintAssocName value is always interpreted within
the context of a Dot1agCfmMaintAssocNameType value. Every
usage of the Dot1agCfmMaintAssocName textual convention is
required to specify the Dot1agCfmMaintAssocNameType object
that provides the context. It is suggested that the
Dot1agCfmMaintAssocNameType object be logically registered
before the object(s) that use the Dot1agCfmMaintAssocName
textual convention, if they appear in the same logical row.
The value of a Dot1agCfmMaintAssocName object MUST
always be consistent with the value of the associated
Dot1agCfmMaintAssocNameType object. Attempts to set
an Dot1agCfmMaintAssocName object to a value inconsistent
with the associated Dot1agCfmMaintAssocNameType MUST fail
with an inconsistentValue error.
When this textual convention is used as the syntax of an
index object, there may be issues with the limit of 128
sub-identifiers specified in SMIv2, IETF STD 58. In this
case, the object definition MUST include a 'SIZE' clause
to limit the number of potential instance sub-identifiers;
otherwise the applicable constraints MUST be stated in
the appropriate conceptual row DESCRIPTION clauses, or
in the surrounding documentation if there is no single
DESCRIPTION clause that is appropriate.
"
REFERENCE
"802.1ag clauses 21.6.5.4, 21.6.5.5, 21.6.5.6"
SYNTAX OCTET STRING (SIZE(1..45))
Dot1agCfmMDLevel ::= TEXTUAL-CONVENTION
DISPLAY-HINT "d"
STATUS current
DESCRIPTION
"Integer identifying the Maintenance Domain Level (MD Level).
Higher numbers correspond to higher Maintenance Domains,
those with the greatest physical reach, with the highest
values for customers' CFM PDUs. Lower numbers correspond
to lower Maintenance Domains, those with more limited
physical reach, with the lowest values for CFM PDUs
protecting single bridges or physical links.
"
REFERENCE
"802.1ag clauses 18.3, 21.4.1"
SYNTAX Integer32 (0..7)
Dot1agCfmMDLevelOrNone ::= TEXTUAL-CONVENTION
DISPLAY-HINT "d"
STATUS current
DESCRIPTION
"Integer identifying the Maintenance Domain Level (MD Level).
Higher numbers correspond to higher Maintenance Domains,
those with the greatest physical reach, with the highest
values for customers' CFM packets. Lower numbers correspond
to lower Maintenance Domains, those with more limited
physical reach, with the lowest values for CFM PDUs
protecting single bridges or physical links.
The value (-1) is reserved to indicate that no MA Level has
been assigned.
"
REFERENCE
"802.1ag clauses 18.3, 12.14.3.1.3:c"
SYNTAX Integer32 (-1 | 0..7)
Dot1agCfmMpDirection ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"Indicates the direction in which the Maintenance
association (MEP or MIP) faces on the bridge port:
down(1) Sends Continuity Check Messages away from the
MAC Relay Entity.
up(2) Sends Continuity Check Messages towards the
MAC Relay Entity.
"
REFERENCE
"802.1ag clauses 12.14.6.3.2:c"
SYNTAX INTEGER {
down (1),
up (2)
}
Dot1agCfmPortStatus ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"An enumerated value from he Port Status TLV from the last CCM
received from the last MEP. It indicates the ability of the
Bridge Port on which the transmitting MEP resides to pass
ordinary data, regardless of the status of the MAC
(Table 21-10).
psNoPortStateTLV(0) Indicates either that no CCM has been
received or that no port status TLV was
present in the last CCM received.
psBlocked(1) Ordinary data cannot pass freely through
the port on which the remote MEP resides.
Value of enableRmepDefect is equal to
false.
psUp(2): Ordinary data can pass freely through
the port on which the remote MEP resides.
Value of enableRmepDefect is equal to
true.
NOTE: A 0 value is used for psNoPortStateTLV, so that
additional code points can be added in a manner
consistent with the Dot1agCfmInterfaceStatus textual
convention.
"
REFERENCE
"12.14.7.6.3:f, 20.19.3 and 21.5.4"
SYNTAX INTEGER {
psNoPortStateTLV (0),
psBlocked (1),
psUp (2)
}
Dot1agCfmInterfaceStatus ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"An enumerated value from the Interface Status TLV from the
last CCM received from the last MEP. It indicates the status
of the Interface within which the MEP transmitting the CCM
is configured, or the next lower Interface in the Interface
Stack, if the MEP is not configured within an Interface.
isNoInterfaceStatusTLV(0) Indicates either that no CCM has been
received or that no interface status TLV
was present in the last CCM received.
isUp(1) The interface is ready to pass packets.
isDown(2) The interface cannot pass packets
isTesting(3) The interface is in some test mode.
isUnknown(4) The interface status cannot be determined
for some reason.
isDormant(5) The interface is not in a state to pass
packets but is in a pending state, waiting
for some external event.
isNotPresent(6) Some component of the interface is missing
isLowerLayerDown(7) The interface is down due to state of the
lower layer interfaces
NOTE: A 0 value is used for isNoInterfaceStatusTLV, so that
these code points can be kept consistent with new code
points added to ifOperStatus in the IF-MIB.
"
REFERENCE
"12.14.7.6.3:g, 20.19.4 and 21.5.5"
SYNTAX INTEGER {
isNoInterfaceStatusTLV (0),
isUp (1),
isDown (2),
isTesting (3),
isUnknown (4),
isDormant (5),
isNotPresent (6),
isLowerLayerDown (7)
}
Dot1agCfmHighestDefectPri ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"An enumerated value, equal to the contents of the variable
highestDefect (20.33.9 and Table 20-1), indicating the
highest-priority defect that has been present since the MEP
Fault Notification Generator State Machine was last in the
FNG_RESET state, either:
none(0) no defects since FNG_RESET
defRDICCM(1) DefRDICCM
defMACstatus(2) DefMACstatus
defRemoteCCM(3) DefRemoteCCM
defErrorCCM(4) DefErrorCCM
defXconCCM(5) DefXconCCM
The value 0 is used for no defects so that additional higher
priority values can be added, if needed, at a later time, and
so that these values correspond with those in
Dot1agCfmLowestAlarmPri.
"
REFERENCE
"20.1.2, 12.14.7.7.2:c and 20.33.9"
SYNTAX INTEGER {
none (0),
defRDICCM (1),
defMACstatus (2),
defRemoteCCM (3),
defErrorCCM (4),
defXconCCM (5)
}
Dot1agCfmLowestAlarmPri ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"An integer value specifying the lowest priority defect
that is allowed to generate a Fault Alarm (20.9.5), either:
allDef(1) DefRDICCM, DefMACstatus, DefRemoteCCM,
DefErrorCCM, and DefXconCCM;
macRemErrXcon(2) Only DefMACstatus, DefRemoteCCM,
DefErrorCCM, and DefXconCCM (default);
remErrXcon(3) Only DefRemoteCCM, DefErrorCCM,
and DefXconCCM;
errXcon(4) Only DefErrorCCM and DefXconCCM;
xcon(5) Only DefXconCCM; or
noXcon(6) No defects DefXcon or lower are to be
reported;
"
REFERENCE
"12.14.7.1.3:k and 20.9.5"
SYNTAX INTEGER {
allDef (1),
macRemErrXcon (2),
remErrXcon (3),
errXcon (4),
xcon (5),
noXcon (6)
}
Dot1agCfmMepId ::= TEXTUAL-CONVENTION
DISPLAY-HINT "d"
STATUS current
DESCRIPTION
"Maintenance association End Point Identifier (MEPID): A small
integer, unique over a given Maintenance Association,
identifying a specific MEP.
"
REFERENCE
"802.1ag clauses 3.19 and 19.2.1"
SYNTAX Unsigned32 (1..8191)
Dot1agCfmMepIdOrZero ::= TEXTUAL-CONVENTION
DISPLAY-HINT "d"
STATUS current
DESCRIPTION
"Maintenance association End Point Identifier (MEPID): A small
integer, unique over a given Maintenance Association,
identifying a specific MEP.
The special value 0 is allowed to indicate special cases, for
example that no MEPID is configured.
Whenever an object is defined with this SYNTAX, then the
DESCRIPTION clause of such an object MUST specify what the
special value of 0 means.
"
REFERENCE
"19.2.1"
SYNTAX Unsigned32 (0 | 1..8191)
Dot1agCfmMhfCreation ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"Indicates if the Management Entity can create MHFs.
The valid values are:
defMHFnone(1) No MHFs can be created for this VID.
defMHFdefault(2) MHFs can be created on this VID on any
Bridge port through which this VID can
pass.
defMHFexplicit(3) MHFs can be created for this VID only on
Bridge ports through which this VID can
pass, and only if a MEP is created at some
lower MD Level.
defMHFdefer(4) The creation of MHFs is determined by the
corresponding Maintenance Domain variable
(dot1agCfmMaCompMhfCreation).
"
REFERENCE
"12.14.5.1.3:c and 22.2.3"
SYNTAX INTEGER {
defMHFnone (1),
defMHFdefault (2),
defMHFexplicit (3),
defMHFdefer (4)
}
Dot1agCfmIdPermission ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"Indicates what, if anything, is to be included in the Sender
ID TLV transmitted in CCMs, LBMs, LTMs, and LTRs. The valid
values are:
sendIdNone(1) The Sender ID TLV is not to be sent.
sendIdChassis(2) The Chassis ID Length, Chassis ID
Subtype, and Chassis ID fields of the
Sender ID TLV are to be sent.
sendIdManage(3) The Management Address Length and
Management Address of the Sender ID TLV
are to be sent.
sendIdChassisManage(4) The Chassis ID Length, Chassis ID
Subtype, Chassis ID, Management Address
Length and Management Address fields are
all to be sent.
sendIdDefer(5) The contents of the Sender ID TLV are
determined by the corresponding
Maintenance Domain variable
(dot1agCfmMaCompIdPermission).
"
REFERENCE
"12.14.6.1.3:d and 21.5.3"
SYNTAX INTEGER {
sendIdNone (1),
sendIdChassis (2),
sendIdManage (3),
sendIdChassisManage (4),
sendIdDefer (5)
}
Dot1agCfmCcmInterval ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"Indicates the interval at which CCMs are sent by a MEP.
The possible values are:
intervalInvalid(0) No CCMs are sent (disabled).
interval300Hz(1) CCMs are sent every 3 1/3 milliseconds
(300Hz).
interval10ms(2) CCMs are sent every 10 milliseconds.
interval100ms(3) CCMs are sent every 100 milliseconds.
interval1s(4) CCMs are sent every 1 second.
interval10s(5) CCMs are sent every 10 seconds.
interval1min(6) CCMs are sent every minute.
interval10min(7) CCMs are sent every 10 minutes.
Note: enumerations start at zero to match the 'CCM Interval
field' protocol field.
"
REFERENCE
"802.1ag clauses 12.14.6.1.3:e, 20.8.1 and 21.6.1.3"
SYNTAX INTEGER {
intervalInvalid (0),
interval300Hz (1),
interval10ms (2),
interval100ms (3),
interval1s (4),
interval10s (5),
interval1min (6),
interval10min (7)
}
Dot1agCfmFngState ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"Indicates the diferent states of the MEP Fault Notification
Generator State Machine.
fngReset(1) No defect has been present since the
dot1agCfmMepFngResetTime timer
expired, or since the state machine
was last reset.
fngDefect(2) A defect is present, but not for a
long enough time to be reported
(dot1agCfmMepFngAlarmTime).
fngReportDefect(3) A momentary state during which the
defect is reported by sending a
dot1agCfmFaultAlarm notification,
if that action is enabled.
fngDefectReported(4) A defect is present, and some defect
has been reported.
fngDefectClearing(5) No defect is present, but the
dot1agCfmMepFngResetTime timer has
not yet expired.
"
REFERENCE
"12.14.7.1.3:f and 20.35"
SYNTAX INTEGER {
fngReset (1),
fngDefect (2),
fngReportDefect (3),
fngDefectReported (4),
fngDefectClearing (5)
}
Dot1agCfmRelayActionFieldValue ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"Possible values the Relay action field can take."
REFERENCE
"802.1ag clauses 12.14.7.5.3:g, 20.36.2.5, 21.9.5, and
Table 21-27"
SYNTAX INTEGER {
rlyHit (1),
rlyFdb (2),
rlyMpdb (3)
}
Dot1agCfmIngressActionFieldValue ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"Possible values returned in the ingress action field."
REFERENCE
"802.1ag clauses 12.14.7.5.3:g, 20.36.2.6, 21.9.8.1, and
Table 21-30
"
SYNTAX INTEGER {
ingNoTlv (0),
ingOk (1),
ingDown (2),
ingBlocked (3),
ingVid (4)
}
Dot1agCfmEgressActionFieldValue ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"Possible values returned in the egress action field"
REFERENCE
"802.1ag clauses 12.14.7.5.3:o, 20.36.2.10, 21.9.9.1, and
Table 21-32"
SYNTAX INTEGER {
egrNoTlv (0),
egrOK (1),
egrDown (2),
egrBlocked (3),
egrVid (4)
}
Dot1agCfmRemoteMepState::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"Operational state of the remote MEP state machine. This
state machine monitors the reception of valid CCMs from a
remote MEP with a specific MEPID. It uses a timer that
expires in 3.5 times the length of time indicated by the
dot1agCfmMaNetCcmInterval object.
rMepIdle(1) Momentary state during reset.
rMepStart(2) The timer has not expired since the
state machine was reset, and no valid
CCM has yet been received.
rMepFailed(3) The timer has expired, both since the
state machine was reset, and since a
valid CCM was received.
rMepOk(4) The timer has not expired since a
valid CCM was received.
"
REFERENCE
"802.1ag clauses 12.14.7.6.3:b, 20.22"
SYNTAX INTEGER {
rMepIdle (1),
rMepStart (2),
rMepFailed (3),
rMepOk (4)
}
Dot1afCfmIndexIntegerNextFree ::= TEXTUAL-CONVENTION
DISPLAY-HINT "d"
STATUS current
DESCRIPTION
"An integer which may be used as a new Index in a table.
The special value of 0 indicates that no more new entries can
be created in the relevant table.
When a MIB is used for configuration, an object with this
SYNTAX always contains a legal value (if non-zero) for an
index that is not currently used in the relevant table. The
Command Generator (Network Management Application) reads this
variable and uses the (non-zero) value read when creating a
new row with an SNMP SET. When the SET is performed, the
Command Responder (agent) MUST determine whether the value is
indeed still unused; Two Network Management Applications may
attempt to create a row (configuration entry) simultaneously
and use the same value. If it is currently unused, the SET
succeeds and the Command Responder (agent) changes the value
of this object, according to an implementation-specific
algorithm. If the value is in use, however, the SET fails.
The Network Management Application MUST then re-read this
variable to obtain a new usable value.
An OBJECT-TYPE definition using this SYNTAX MUST specify the
relevant table for which the object is providing this
functionality.
"
SYNTAX Unsigned32 (0..4294967295)
Dot1agCfmMepDefects ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"A MEP can detect and report a number of defects, and multiple
defects can be present at the same time. These defects are:
bDefRDICCM(0) A remote MEP is reported the RDI bit in its
last CCM.
bDefMACstatus(1) Either some remote MEP is reporting its
Interface Status TLV as not isUp, or all remote
MEPs are reporting a Port Status TLV that
contains some value other than psUp.
bDefRemoteCCM(2) The MEP is not receiving valid CCMs from at
least one of the remote MEPs.
bDefErrorCCM(3) The MEP has received at least one invalid CCM
whose CCM Interval has not yet timed out.
bDefXconCCM(4) The MEP has received at least one CCM from
either another MAID or a lower MD Level whose
CCM Interval has not yet timed out.
"
REFERENCE
"802.1ag clauses 12.14.7.1.3:o, 12.14.7.1.3:p, 12.14.7.1.3:q,
12.14.7.1.3:r, and 12.14.7.1.3:s."
SYNTAX BITS {
bDefRDICCM(0),
bDefMACstatus(1),
bDefRemoteCCM(2),
bDefErrorCCM(3),
bDefXconCCM(4)
}
Dot1agCfmConfigErrors ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"While making the MIP creation evaluation described in 802.1ag
clause 22.2.3, the management entity can encounter errors in
the configuration. These are possible errors that can be
encountered:
CFMleak(0) MA x is associated with a specific VID list,
one or more of the VIDs in MA x can pass through
the Bridge Port, no Down MEP is configured on
any Bridge Port for MA x, and some other MA y,
at a higher MD Level than MA x, and associated
with at least one of the VID(s) also in MA x,
does have a MEP configured on the Bridge Port.
conflictingVids(1) MA x is associated with a specific VID
list, an Up MEP is configured on MA x on the
Bridge Port, and some other MA y, associated
with at least one of the VID(s) also in MA x,
also has an Up MEP configured on some Bridge
Port.
ExcessiveLevels(2) The number of different MD Levels at
which MIPs are to be created on this port
exceeds the Bridge's capabilities (see
subclause 22.3).
OverlappedLevels(3) A MEP is created for one VID at one MD
Level, but a MEP is configured on another
VID at that MD Level or higher, exceeding
the Bridge's capabilities.
"
REFERENCE
"12.14.4.1.3:b and clauses 22.2.3 and 22.2.4"
SYNTAX BITS {
cfmLeak(0),
conflictingVids(1),
excessiveLevels(2),
overlappedLevels(3)
}
Dot1agCfmPbbComponentIdentifier
::= TEXTUAL-CONVENTION
DISPLAY-HINT "d"
STATUS current
DESCRIPTION
"A Provider Backbone Bridge (PBB) can comprise a number of
components, each of which can be managed in a manner
essentially equivalent to an 802.1Q bridge. In order to access
these components easily, an index is used in a number of
tables. If any two tables are indexed by
Dot1agCfmPbbComponentIdentifier, then entries in those tables
indexed by the same value of Dot1agCfmPbbComponentIdentifier
correspond to the same component.
"
REFERENCE
"12.3 l)"
SYNTAX Unsigned32 (1..4294967295)
-- ******************************************************************
-- The Stack Object. This group will contain all the MIBs objects
-- needed to access the Stack managed object.
-- ******************************************************************
-- ******************************************************************
-- The CFM Stack Table
-- ******************************************************************
dot1agCfmStackTable OBJECT-TYPE
SYNTAX SEQUENCE OF Dot1agCfmStackEntry
MAX-ACCESS not-accessible
STATUS deprecated
DESCRIPTION
"There is one CFM Stack table per bridge. It permits
the retrieval of information about the Maintenance Points
configured on any given interface.
**NOTE: this object is deprecated due to re-indexing of the
table.
"
REFERENCE
"802.1ag clauses 12.14.2"
::= { dot1agCfmStack 1 }
dot1agCfmStackEntry OBJECT-TYPE
SYNTAX Dot1agCfmStackEntry
MAX-ACCESS not-accessible
STATUS deprecated
DESCRIPTION
"The Stack table entry
**NOTE: this object is deprecated due to re-indexing of the
table.
"
INDEX { dot1agCfmStackifIndex, dot1agCfmStackVlanIdOrNone,
dot1agCfmStackMdLevel, dot1agCfmStackDirection
}
::= { dot1agCfmStackTable 1 }
Dot1agCfmStackEntry ::= SEQUENCE {
dot1agCfmStackifIndex InterfaceIndex,
dot1agCfmStackVlanIdOrNone VlanIdOrNone,
dot1agCfmStackMdLevel Dot1agCfmMDLevel,
dot1agCfmStackDirection Dot1agCfmMpDirection,
dot1agCfmStackMdIndex Unsigned32,
dot1agCfmStackMaIndex Unsigned32,
dot1agCfmStackMepId Dot1agCfmMepIdOrZero,
dot1agCfmStackMacAddress MacAddress
}
dot1agCfmStackifIndex OBJECT-TYPE
SYNTAX InterfaceIndex
MAX-ACCESS not-accessible
STATUS deprecated
DESCRIPTION
"This object represents the Bridge Port or aggregated port
on which MEPs or MHFs might be configured.
Upon a restart of the system, the system SHALL, if necessary,
change the value of this variable, and rearrange the
dot1agCfmStackTable, so that it indexes the entry in the
interface table with the same value of ifAlias that it
indexed before the system restart. If no such entry exists,
then the system SHALL delete all entries in the
dot1agCfmStackTable with the interface index.
**NOTE: this object is deprecated due to re-indexing of
the table.
**NOTE: this object is deprecated due to re-indexing of the
table.
"
REFERENCE
"12.14.2.1.2:a"
::= { dot1agCfmStackEntry 1 }
dot1agCfmStackVlanIdOrNone OBJECT-TYPE
SYNTAX VlanIdOrNone
MAX-ACCESS not-accessible
STATUS deprecated
DESCRIPTION
"VLAN ID to which the MP is attached, or 0, if none.
**NOTE: this object is deprecated due to re-indexing of the
table.
"
REFERENCE
"802.1ag clauses 12.14.2.1.2:d, 22.1.7"
::= { dot1agCfmStackEntry 2 }
dot1agCfmStackMdLevel OBJECT-TYPE
SYNTAX Dot1agCfmMDLevel
MAX-ACCESS not-accessible
STATUS deprecated
DESCRIPTION
"MD Level of the Maintenance Point.
**NOTE: this object is deprecated due to re-indexing of the
table.
"
REFERENCE
"12.14.2.1.2:b"
::= { dot1agCfmStackEntry 3 }
dot1agCfmStackDirection OBJECT-TYPE
SYNTAX Dot1agCfmMpDirection
MAX-ACCESS not-accessible
STATUS deprecated
DESCRIPTION
"Direction in which the MP faces on the Bridge Port
**NOTE: this object is deprecated due to re-indexing of the
table.
"
REFERENCE
"12.14.2.1.2:c"
::= { dot1agCfmStackEntry 4 }
dot1agCfmStackMdIndex OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS read-only
STATUS deprecated
DESCRIPTION
"The index of the Maintenance Domain in the dot1agCfmMdTable
to which the MP is associated, or 0, if none.