smilint output for ./EFM-COMMON-MIB
| Message Severities |
|---|
| Severity | Count |
|---|
| severe | 49 |
| error | 23 |
| minor error | 5 |
| change recommended | 12 |
| warning | 30 |
| Message Types |
|---|
| Type | Count |
|---|
| bad-identifier-case (error) | 10 |
| description-missing (error) | 3 |
| group-membership (change recommended) | 12 |
| import-unused (warning) | 1 |
| internal-flushing (warning) | 25 |
| internal-other (severe) | 25 |
| module-identity-missing (error) | 1 |
| node-implicit (warning) | 1 |
| notification-object-type (minor error) | 1 |
| object-identifier-not-prefix (error) | 4 |
| object-identifier-unknown (severe) | 24 |
| parent-row (error) | 3 |
| revision-missing (minor error) | 1 |
| sequence-no-column (minor error) | 3 |
| sequence-order (warning) | 3 |
| type-unknown (error) | 2 |
Messages:
EFM-COMMON-MIB
1: -- extracted from draft-ietf-hubmib-efm-mib-03.txt
2: -- at Fri Mar 25 06:23:19 2005
3:
4: EFM-COMMON-MIB DEFINITIONS ::= BEGIN
5: IMPORTS
6: MODULE-IDENTITY, mib-2, OBJECT-TYPE, Counter32, Unsigned32,
6: warning -
warning: identifier `mib-2' imported from module `SNMPv2-SMI' is never used
7: Integer32, NOTIFICATION-TYPE
8: FROM SNMPv2-SMI
9: TEXTUAL-CONVENTION, MacAddress, TimeStamp
10: FROM SNMPv2-TC
11: CounterBasedGauge64
12: FROM HCNUM-TC
13: ifIndex
14: FROM IF-MIB
15: MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP
16: FROM SNMPv2-CONF;
17:
18:
19: efmOamMIB MODULE-IDENTITY
20: LAST-UPDATED "200503220000Z" -- March 22, 2005"
21: ORGANIZATION
22: "IETF Ethernet Interfaces and Hub MIB Working Group"
23: CONTACT-INFO
24: "WG Charter:
25: http://www.ietf.org/html.charters/hubmib-charter.html
26: Mailing lists:
27: EFM OAM MIB March 2005
28:
29:
30: General Discussion: hubmib@ietf.org
31: To Subscribe: hubmib-requests@ietf.org
32: In Body: subscribe your_email_address
33: Chair: Dan Romascanu, Avaya
34: Tel: +972-3-645-8414
35: Email: dromasca at avaya dot com
36: Editor: Matt Squire
37: Hatteras Networks
38: Tel: +1-919-991-5460
39: Fax: +1-919-991-0743
40: E-mail: msquire at hatterasnetworks dot com
41: "
42: DESCRIPTION
43: "The MIB module for managing the new Ethernet OAM features
44: introduced by the Ethernet in the First Mile task force (IEEE
45: 802.3ah). The functionality presented here is based on IEEE
46: 802.3ah [802.3ah], released in October, 2004.
47:
48: In particular, this MIB focused on the changes to Clause 30 of
49: the draft that are not specific to any physical layer. These
50: changes are primarily reflected in the new OAM features
51: developed under this project, that can be applied to any
52: Ethernet like interface. The OAM features are described in
53: Clause 57 of [802.3ah].
54:
55: The following reference is used throughout this MIB module:
56:
57: [802.3ah] refers to:
58: IEEE Std 802.3ah-2004: 'Draft amendment to -
59: Information technology - Telecommunications and
60: information exchange between systems - Local and
61: metropolitan are networks - Specific requirements - Part
62: 3: Carrier sense multiple access with collision detection
63: (CSMA/CD) access method and physical layer specifications
64: - Media Access Control Parameters, Physical Layers and
65: Management Parameters for subscriber access networks',
66: October 2004.
67:
68: [802-2001] refers to:
69: 'IEEE Standard for LAN/MAN (Local Area
70: Network/Metropolitan Area Network): Overview and
71: Architecture', IEEE 802, June 2001.
72:
73: Copyright (c) The Internet Society (2005). This version of
74: this MIB module is part of RFC XXXX; See the RFC itself for
75: full legal notices. "
76: -- RFC Editor: Update XXXX to appropriate RFC number
77: -- RFC Editor: Remove these notes
78: EFM OAM MIB March 2005
78: minor error -
revision for last update is missing
78: severe -
syntax error, unexpected UPPERCASE_IDENTIFIER, expecting COLON_COLON_EQUAL
79:
80:
81:
82: REVISION "200503220000Z" -- March 22, 2005"
83: DESCRIPTION "Initial version, published as RFC XXXX."
84: -- RFC Editor: Update XXXX to appropriate RFC number
85: -- RFC Editor: Remove these notes
86:
87: ::= { mib-2 XXX }
87: warning -
warning: flushing recent incorrect declaration, see previous error(s)
88: -- RFC Editor: Replace value with IANA assigned number
89: -- RFC Editor: Remove these notes
90:
91:
92: --
93: -- Sections of the EFM OAM MIB
94: --
95: dot3OamMIB OBJECT IDENTIFIER ::= { efmOamMIB 1 }
95: severe -
unknown object identifier label `efmOamMIB'
96: dot3OamConformance OBJECT IDENTIFIER ::= { efmOamMIB 2 }
97:
98:
99: --
100: -- Textual conventions for OAM MIB
101: --
102: Dot3Oui ::= TEXTUAL-CONVENTION
103: STATUS current
104: DESCRIPTION
105: "24-bit Organizationally Unique Identifier. Information on
106: OUIs can be found in IEEE 802-2001 [802-2001] Clause 9."
107: SYNTAX OCTET STRING(SIZE(3))
108:
109:
110: ------------------------------------------------------------------
111: --
112: -- Ethernet OAM Control group
113: --
114:
115:
116: dot3OamTable OBJECT-TYPE
117: SYNTAX SEQUENCE OF Dot3OamEntry
118: MAX-ACCESS not-accessible
119: STATUS current
120: DESCRIPTION
121: "Primary controls and status for the OAM capabilities of an
122: Ethernet like interface. There will be one row in this table
123: for each Ethernet like interface in the system that supports
124: the Ethernet OAM functions defined in [802.3ah]."
125: ::= { dot3OamMIB 1 }
126:
127: dot3OamEntry OBJECT-TYPE
128: SYNTAX Dot3OamEntry
129: MAX-ACCESS not-accessible
130: EFM OAM MIB March 2005
130: severe -
syntax error, unexpected UPPERCASE_IDENTIFIER, expecting STATUS
131:
132:
133: STATUS current
134: DESCRIPTION
135: "An entry in the table, containing information on the Ethernet
136: OAM function for a single Ethernet like interface."
137: INDEX { ifIndex }
137: warning -
warning: flushing recent incorrect declaration, see previous error(s)
138: ::= { dot3OamTable 1 }
138: severe -
syntax error, unexpected COLON_COLON_EQUAL
138: warning -
warning: flushing recent incorrect declaration, see previous error(s)
139:
140: Dot3OamEntry ::=
141: SEQUENCE {
142: dot3OamAdminState INTEGER,
143: dot3OamOperStatus INTEGER,
143: severe -
unknown object identifier label `dot3OamOperStatus'
144: dot3OamMode INTEGER,
145: dot3OamMaxOamPduSize Integer32,
145: severe -
unknown object identifier label `dot3OamMaxOamPduSize'
146: dot3OamConfigRevision Unsigned32,
147: dot3OamFunctionsSupported BITS
148: }
149:
150:
151: dot3OamAdminState OBJECT-TYPE
152: SYNTAX INTEGER {
153: disabled(1),
154: enabled(2)
155: }
156: MAX-ACCESS read-write
157: STATUS current
158: DESCRIPTION
159: "This object is used to provision the default administrative
160: OAM mode for this interface. This object represents the
161: desired state of OAM for this interface.
162:
163: The dot3OamAdminState always starts in the disabled(1) state
164: until an explicity management action or configuration
165: information retained by the system causes a transition to the
166: enabled(2) state.
167:
168: Note that the value of this object is ignored when the
169: interface is not operating in full-duplex mode. OAM is not
170: supported on half-duplex links. "
171: REFERENCE "[802.3ah], 30.3.6.1.2"
172: ::= { dot3OamEntry 1 }
172: severe -
unknown object identifier label `dot3OamEntry'
173:
174: dot3OamOperStatus OBJECT-TYPE
175: SYNTAX INTEGER {
176: disabled(1),
177: linkfault(2),
178: passiveWait(3),
179: activeSendLocal(4),
180: sendLocalAndRemote(5),
181: sendLocalAndRemoteOk(6),
182: EFM OAM MIB March 2005
182: severe -
syntax error, unexpected UPPERCASE_IDENTIFIER, expecting LOWERCASE_IDENTIFIER
183:
184:
185: oamPeeringLocallyRejected(7),
186: oamPeeringRemotelyRejected(8),
187: operational(9)
188: }
188: warning -
warning: flushing recent incorrect declaration, see previous error(s)
189: MAX-ACCESS read-only
189: severe -
syntax error, unexpected MAX_ACCESS
190: STATUS current
191: DESCRIPTION
192: "At initialization and failure conditions, two OAM entities on
193: the same full-duplex Ethernet link begin a discovery phase to
194: determine what OAM capabilities may be used on that link. The
195: progress of this initialization is controlled by the OAM
196: sublayer.
197:
198: This value is always disabled(1) if OAM is disabled on this
199: interface via the dot3OamAdminState.
200:
201: If the link has detected a fault and is transmitting OAMPDUs
202: with a link fault indication, the value is linkFault(2).
203:
204: The passiveWait(3) state is returned only by OAM entities in
205: passive mode (dot3OamMode) and reflects the state in which the
206: OAM entity is waiting to see if the peer device is OAM
207: capable. The activeSendLocal(4) is used by active mode
208: devices (dot3OamMode) and reflects the OAM entity actively
209: trying to discover whether the peer has OAM capability but has
210: not yet made that determination.
211:
212: The state sendLocalAndRemote(5) reflects that the local OAM
213: entity has discovered the peer but has not yet accepted or
214: rejected the configuration of the peer. The local device can,
215: for whatever reason, decide that the peer device is
216: unacceptable and decline OAM peering. If the local OAM entity
217: rejects the peer OAM entity, the state becomes
218: oamPeeringLocallyRejected(7). If the OAM peering is allowed
219: by the local device, the state moves to
220: sendLocalAndRemoteOk(6). Note that both the
221: sendLocalAndRemote(5) and oamPeeringLocallyRejected(7) states
222: fall within the state SEND_LOCAL_REMOTE of the Discovery state
223: diagram [802.3ah, Figure 57-5], with the difference being
224: whether the local OAM client has actively rejected the peering
225: or has just not indicated any decision yet. Whether a peering
226: decision has been made is indicated via the local flags field
227: in the OAMPDU (reflected in the aOAMLocalFlagsField of
228: 30.3.6.1.10).
229:
230: If the remote OAM entity rejects the peering, the state
231: becomes oamPeeringRemotelyRejected(8). Note that both the
232: sendLocalAndRemoteOk(6) and oamPeeringRemotelyRejected(8)
233: states fall within the state SEND_LOCAL_REMOTE_OK of the
234: EFM OAM MIB March 2005
235:
236:
237: Discovery state diagram [802.3ah, Figure 57-5], with the
238: difference being whether the remote OAM client has rejected
239: the peering or has just not yet decided. This is indicated
240: via the remote flags field in the OAM PDU (reflected in the
241: aOAMRemoteFlagsField of 30.3.6.1.11).
242:
243: When the local OAM entity learns that both it and the remote
244: OAM entity have accepted the peering, the state moves to
245: operational(9) corresponding to the SEND_ANY state of the
246: Discovery state diagram [802.3ah, Figure 57-5]. "
247: REFERENCE "[802.3ah], 30.3.6.1.4, 30.3.6.1.10, 30.3.6.1.11"
248: ::= { dot3OamEntry 2 }
248: warning -
warning: flushing recent incorrect declaration, see previous error(s)
249:
250: dot3OamMode OBJECT-TYPE
251: SYNTAX INTEGER {
252: active(1),
253: passive(2)
254: }
255: MAX-ACCESS read-write
256: STATUS current
257: DESCRIPTION
258: "This object configures the mode of OAM operation for this
259: Ethernet like interface. OAM on Ethernet interfaces may be in
260: 'active' mode or 'passive' mode. These two modes differ in
261: that active mode provides additional capabilities to initiate
262: monitoring activities with the remote OAM peer entity, while
263: passive mode generally waits for the peer to initiate OAM
264: actions with it. As an example, an active OAM entity can put
265: the remote OAM entity in a loopback state, where a passive OAM
266: entity cannot.
267:
268: The default value of dot3OamMode is dependent on the type of
269: system on which this Ethernet like interface resides. The
270: default value should be 'active(1)' unless it is known that
271: this system should take on a subservient role to the other
272: device connected over this interface.
273:
274: Changing this value results in incrementing the configuration
275: revision field of locally generated OAMPDUs (30.3.6.1.12) and
276: potentially re-doing the OAM discovery process if the
277: dot3OamOperStatus was already operational(9). "
278: REFERENCE "[802.3ah], 30.3.6.1.3"
279: ::= { dot3OamEntry 3 }
280:
281: dot3OamMaxOamPduSize OBJECT-TYPE
282: SYNTAX Integer32 (64..1522)
283: UNITS "bytes"
284: MAX-ACCESS read-only
285: STATUS current
286: EFM OAM MIB March 2005
286: error -
description missing in object definition
286: severe -
syntax error, unexpected UPPERCASE_IDENTIFIER, expecting COLON_COLON_EQUAL
287:
288:
289: DESCRIPTION
290: "The largest OAMPDU that the OAM entity supports. OAM
291: entities exchange maximum OAMPDU sizes and negotiate to use
292: the smaller of the two maximum OAMPDU sizes between the peers.
293: This value is determined by the local implementation.
294: "
295: REFERENCE "[802.3ah], 30.3.6.1.8"
296: ::= { dot3OamEntry 4 }
296: warning -
warning: flushing recent incorrect declaration, see previous error(s)
297:
298: dot3OamConfigRevision OBJECT-TYPE
299: SYNTAX Unsigned32
300: MAX-ACCESS read-only
301: STATUS current
302: DESCRIPTION
303: "The configuration revision of the OAM entity as reflected in
304: the latest OAMPDU sent by the OAM entity. The config revision
305: is used by OAM entities to indicate configuration changes have
306: occured which might require the peer OAM entity to re-evaluate
307: whether the peering is allowed. See local_satisfied in
308: [802.3ah, 57.3.1.2]. "
309: REFERENCE "[802.3ah], 30.3.6.1.12"
310: ::= { dot3OamEntry 5 }
311:
312: dot3OamFunctionsSupported OBJECT-TYPE
313: SYNTAX BITS {
314: unidirectionalSupport (0),
315: loopbackSupport(1),
316: eventSupport(2),
317: variableSupport(3)
318: }
319: MAX-ACCESS read-only
320: STATUS current
321: DESCRIPTION
322: "The OAM functions supported on this Ethernet like interface.
323: OAM consists of separate functional sets beyond the basic
324: discovery process which is always required. These functional
325: groups can be supported independently by any implementation.
326: These values are communicated to the peer via the local
327: configuration field of Information OAMPDUs. "
328: REFERENCE "[802.3ah], 30.3.6.1.6"
329: ::= { dot3OamEntry 6 }
330:
331:
332: ------------------------------------------------------------------
333: --
334: -- Ethernet OAM Peer group
335: --
336: EFM OAM MIB March 2005
336: error -
`EFM' should start with a lower case letter
336: severe -
syntax error, unexpected UPPERCASE_IDENTIFIER, expecting OBJECT
337:
338:
339: dot3OamPeerTable OBJECT-TYPE
340: SYNTAX SEQUENCE OF Dot3OamPeerEntry
341: MAX-ACCESS not-accessible
342: STATUS current
343: DESCRIPTION
344: "Information about the OAM peer for a particular Ethernet like
345: interface. OAM entities communicate with a single OAM peer
346: entity on full-duplex Ethernet links on which OAM is enabled
347: and operating properly.
348:
349: In certain states, the OAM peer information is not available.
350: Whether peer information is available is communicated via the
351: dot3OamPeerStatus object. When this object is inactive, all
352: other information in the row is to be considered invalid. "
353: ::= { dot3OamMIB 2 }
353: warning -
warning: flushing recent incorrect declaration, see previous error(s)
354:
355: dot3OamPeerEntry OBJECT-TYPE
355: error -
row's parent node must be a table node
356: SYNTAX Dot3OamPeerEntry
357: MAX-ACCESS not-accessible
358: STATUS current
359: DESCRIPTION
360: "An entry in the table, containing information on the peer OAM
361: entity for a single Ethernet like interface.
362:
363: Note that there is at most one OAM peer for each Ethernet like
364: interface. There is exactly one row in this table for each
365: Ethernet like interface supporting OAM. "
366: INDEX { ifIndex }
367: ::= { dot3OamPeerTable 1 }
367: severe -
unknown object identifier label `dot3OamPeerTable'
368:
369:
370: Dot3OamPeerEntry ::=
370: minor error -
SEQUENCE element #1 `dot3OamPeerStatus' is not a child node under `dot3OamPeerEntry'
370: warning -
warning: SEQUENCE element #2 `dot3OamPeerMacAddress' does not match order of columnar objects under `dot3OamPeerEntry'
371: SEQUENCE {
372: dot3OamPeerStatus INTEGER,
372: severe -
unknown object identifier label `dot3OamPeerStatus'
373: dot3OamPeerMacAddress MacAddress,
374: dot3OamPeerVendorOui Dot3Oui,
375: dot3OamPeerVendorInfo Unsigned32,
376: dot3OamPeerMode INTEGER,
377: dot3OamPeerMaxOamPduSize Integer32,
378: dot3OamPeerConfigRevision Unsigned32,
379: dot3OamPeerFunctionsSupported BITS
380: }
381:
382: dot3OamPeerStatus OBJECT-TYPE
383: SYNTAX INTEGER {
384: active(1),
385: inactive(2)
386: }
387: MAX-ACCESS read-only
388: EFM OAM MIB March 2005
388: severe -
syntax error, unexpected UPPERCASE_IDENTIFIER, expecting STATUS
389:
390:
391: STATUS current
392: DESCRIPTION
393: "This object indicates whether the information in this row
394: should be considered valid. When active(1), the information
395: is valid and represents the current peer of the OAM entity.
396: When inactive(2), the information in this row is invalid.
397:
398: A value of inactive(2) is returned if the dot3OamOperStatus is
399: disabled, passiveWait, or activeSendLocal. For all other
400: values of dot3OamOperStatus, a value of active(1) is returned.
401: "
402: ::= { dot3OamPeerEntry 1 }
402: warning -
warning: flushing recent incorrect declaration, see previous error(s)
403:
404: dot3OamPeerMacAddress OBJECT-TYPE
405: SYNTAX MacAddress
406: MAX-ACCESS read-only
407: STATUS current
408: DESCRIPTION
409: "The MAC address of the peer OAM entity. The MAC address is
410: derived from the most recently received OAMPDU. This value is
411: initialized to all zeros (0x000000000000). This value is
412: invalid if the dot3OamPeerStatus is inactive.
413:
414: An OAMPDU is indicated by a valid frame with (1) destination
415: MAC address equal to that of the reserved MAC address for Slow
416: Protocols (See 43B of [802.3ah]), (2) a lengthOrType field
417: equal to the reserved type for Slow Protocols, (3) and a Slow
418: Protocols subtype equal to that of the subtype reserved for
419: OAM. "
420: REFERENCE "[802.3ah], 30.3.6.1.5."
421: ::= { dot3OamPeerEntry 2 }
422:
423:
424: dot3OamPeerVendorOui OBJECT-TYPE
425: SYNTAX Dot3Oui
426: MAX-ACCESS read-only
427: STATUS current
428: DESCRIPTION
429: "The OUI of the OAM peer as reflected in the latest
430: Information OAMPDU received with a Local Information TLV. The
431: OUI can be used to identify the vendor of the remote OAM
432: entity. This value is initialized to all zeros (0x000000).
433: This value is considered invalid if the dot3OamPeerStatus is
434: inactive.
435:
436: An Information OAMPDU is indicated by a valid frame with (1)
437: destination MAC address equal to that of the reserved MAC
438: address for Slow Protocols (See 43B of [802.3ah]), (2) a
439: lengthOrType field equal to the reserved type for Slow
440: EFM OAM MIB March 2005
441:
442:
443: Protocols, (3) a Slow Protocols subtype equal to that of the
444: subtype reserved for OAM, (4) a OAM code that equals the code
445: reserved for Information OAMPDUs. "
446: REFERENCE "[802.3ah], 30.3.6.1.16."
447: ::= { dot3OamPeerEntry 3 }
448:
449:
450: dot3OamPeerVendorInfo OBJECT-TYPE
451: SYNTAX Unsigned32
452: MAX-ACCESS read-only
453: STATUS current
454: DESCRIPTION
455: "The Vendor Info of the OAM peer as reflected in the latest
456: Information OAMPDU received with a Local Information TLV. The
457: vendor information field is within the Local Information TLV,
458: and can be used to determine additional information about the
459: peer entity. The format of the vendor information is
460: unspecified within the 32-bit field. This value is intialized
461: to all zeros (0x00000000). This value is invalid if the
462: dot3OamPeerStatus is inactive.
463:
464: An Information OAMPDU is indicated by a valid frame with (1)
465: destination MAC address equal to that of the reserved MAC
466: address for Slow Protocols (See 43B of [802.3ah]), (2) a
467: lengthOrType field equal to the reserved type for Slow
468: Protocols, (3) a Slow Protocols subtype equal to that of the
469: subtype reserved for OAM, and (4) a OAM code that equals the
470: code reserved for Information OAMPDUs. "
471: REFERENCE "[802.3ah], 30.3.6.1.17."
472: ::= { dot3OamPeerEntry 4 }
473:
474:
475: dot3OamPeerMode OBJECT-TYPE
476: SYNTAX INTEGER {
477: active(1),
478: passive(2),
479: unknown(3)
480: }
481: MAX-ACCESS read-only
482: STATUS current
483: DESCRIPTION
484: "The mode of the OAM peer as reflected in the latest
485: Information OAMPDU received with a Local Information TLV. The
486: mode of the peer can be determined from the Configuration
487: field in the Local Information TLV of the last Information
488: OAMPDU received from the peer. This value is initialized to
489: unknown(3), and is not valid if the dot3OamPeerStatus is
490: inactive.
491: EFM OAM MIB March 2005
492:
493:
494: An Information OAMPDU is indicated by a valid frame with (1)
495: destination MAC address equal to that of the reserved MAC
496: address for Slow Protocols (See 43B of [802.3ah]), (2) a
497: lengthOrType field equal to the reserved type for Slow
498: Protocols, (3) a Slow Protocols subtype equal to that of the
499: subtype reserved for OAM, and (4) a OAM code that equals the
500: code reserved for Information OAMPDUs. "
501: REFERENCE "[802.3ah], 30.3.6.1.7."
502: ::= { dot3OamPeerEntry 5 }
503:
504: dot3OamPeerMaxOamPduSize OBJECT-TYPE
505: SYNTAX Integer32 (64..1522)
506: UNITS "bytes"
507: MAX-ACCESS read-only
508: STATUS current
509: DESCRIPTION
510: "The maximum size of OAMPDU supported by the peer as reflected
511: in the latest Information OAMPDU received with a Local
512: Information TLV. Ethernet OAM on this interface must not use
513: OAMPDUs that exceed this size. The maximum OAMPDU size can be
514: determined from the PDU Configuration field of the Local
515: Information TLV of the last Information OAMPDU received from
516: the peer. This value is initialized to 64, and is invalid if
517: the dot3OamPeerStatus is inactive.
518:
519: An Information OAMPDU is indicated by a valid frame with (1)
520: destination MAC address equal to that of the reserved MAC
521: address for Slow Protocols (See 43B of [802.3ah]), (2) a
522: lengthOrType field equal to the reserved type for Slow
523: Protocols, (3) a Slow Protocols subtype equal to that of the
524: subtype reserved for OAM, and (4) a OAM code that equals the
525: code reserved for Information OAMPDUs. "
526: REFERENCE "[802.3ah], 30.3.6.1.9."
527: ::= { dot3OamPeerEntry 6 }
528:
529:
530: dot3OamPeerConfigRevision OBJECT-TYPE
531: SYNTAX Unsigned32
532: MAX-ACCESS read-only
533: STATUS current
534: DESCRIPTION
535: "The configuration revision of the OAM peer as reflected in
536: the latest OAMPDU. This attribute is changed by the peer
537: whenever it has a local configuration change for Ethernet OAM
538: this interface. This value is initialized to all zeros
539: (0x00000000), and is invalid if the dot3OamPeerStatus is
540: inactive.
541:
542: The configuration revision can be determined from the Revision
543: EFM OAM MIB March 2005
544:
545:
546: field of the Local Information TLV of the most recently
547: received Information OAMPDU with a Local Information TLV.
548:
549: An Information OAMPDU is indicated by a valid frame with (1)
550: destination MAC address equal to that of the reserved MAC
551: address for Slow Protocols (See 43B of [802.3ah]), (2) a
552: lengthOrType field equal to the reserved type for Slow
553: Protocols, (3) a Slow Protocols subtype equal to that of the
554: subtype reserved for OAM, and (4) a OAM code that equals the
555: code reserved for Information OAMPDUs. "
556: REFERENCE "[802.3ah], 30.3.6.1.13."
557: ::= { dot3OamPeerEntry 7 }
558:
559:
560: dot3OamPeerFunctionsSupported OBJECT-TYPE
561: SYNTAX BITS {
562: unidirectionalSupport (0),
563: loopbackSupport(1),
564: eventSupport(2),
565: variableSupport(3)
566: }
567: MAX-ACCESS read-only
568: STATUS current
569: DESCRIPTION
570: "The OAM functions supported on this Ethernet like interface.
571: OAM consists of separate functionality sets above the basic
572: discovery process. This value indicates the capabilities of
573: the peer OAM entity with respect to these functions. This
574: value is initialized so all bits are clear, and is invalid if
575: the dot3OamPeerStatus is inactive.
576:
577: The capbilities of the OAM peer can be determined from the
578: configuration field of the Local Information TLV of the most
579: recently received Information OAMPDU with a Local Information
580: TLV.
581:
582: An Information OAMPDU is indicated by a valid frame with (1)
583: destination MAC address equal to that of the reserved MAC
584: address for Slow Protocols (See 43B of [802.3ah]), (2) a
585: lengthOrType field equal to the reserved type for Slow
586: Protocols, (3) a Slow Protocols subtype equal to that of the
587: subtype reserved for OAM, and (4) a OAM code that equals the
588: code reserved for Information OAMPDUs. "
589: REFERENCE "[802.3ah], REFERENCE 30.3.6.1.7."
590: ::= { dot3OamPeerEntry 8 }
591:
592:
593: ------------------------------------------------------------------
594: --
595: EFM OAM MIB March 2005
595: error -
`EFM' should start with a lower case letter
595: severe -
syntax error, unexpected UPPERCASE_IDENTIFIER, expecting OBJECT
596:
597:
598: -- Ethernet OAM Loopback group
599: --
600:
601:
602: dot3OamLoopbackTable OBJECT-TYPE
603: SYNTAX SEQUENCE OF Dot3OamLoopbackEntry
604: MAX-ACCESS not-accessible
605: STATUS current
606: DESCRIPTION
607: "This table contains methods to control the loopback state of
608: the local link as well as indicating the status of the
609: loopback function.
610:
611: Loopback can be used to place the remote OAM entity in a state
612: where every received frame (except OAMPDUs) are echoed back
613: over the same interface on which they were received. In this
614: state, at the remote entity, 'normal' traffic is disabled as
615: only the looped back frames are transmitted on the interface.
616: Loopback is thus an intrusive operation that prohibits normal
617: data flow and should be used accordingly. "
618: ::= { dot3OamMIB 3 }
618: warning -
warning: flushing recent incorrect declaration, see previous error(s)
619:
620: dot3OamLoopbackEntry OBJECT-TYPE
620: error -
row's parent node must be a table node
621: SYNTAX Dot3OamLoopbackEntry
622: MAX-ACCESS not-accessible
623: STATUS current
624: DESCRIPTION
625: "An entry in the table, containing information on the loopback
626: status for a single Ethernet like interface. There is an
627: entry in this table for every Ethernet like interface on which
628: supports OAM and loopback function within OAM (as indicated in
629: dot3OamFunctionsSupported). "
630: INDEX { ifIndex }
631: ::= { dot3OamLoopbackTable 1 }
631: severe -
unknown object identifier label `dot3OamLoopbackTable'
632:
633: Dot3OamLoopbackEntry ::=
633: minor error -
SEQUENCE element #1 `dot3OamLoopbackCommand' is not a child node under `dot3OamLoopbackEntry'
633: warning -
warning: SEQUENCE element #2 `dot3OamLoopbackStatus' does not match order of columnar objects under `dot3OamLoopbackEntry'
634: SEQUENCE {
635: dot3OamLoopbackCommand INTEGER,
635: severe -
unknown object identifier label `dot3OamLoopbackCommand'
636: dot3OamLoopbackStatus INTEGER,
637: dot3OamLoopbackIgnoreRx INTEGER
638: }
639:
640: dot3OamLoopbackCommand OBJECT-TYPE
641: SYNTAX INTEGER {
642: noLoopback (1),
643: startRemoteLoopback (2),
644: stopRemoteLoopback (3)
645: }
646: MAX-ACCESS read-write
647: EFM OAM MIB March 2005
647: severe -
syntax error, unexpected UPPERCASE_IDENTIFIER, expecting STATUS
648:
649:
650: STATUS current
651: DESCRIPTION
652: "This attribute initiates or terminates remote loopback with
653: an OAM peer. Writing startRemoteLoopback(2) to this attribute
654: cause the local OAM client to send a loopback OAMPDU to the
655: OAM peer with the loopback enable flags set. Writing
656: stopRemoteLoopback(3) to this attribute will cause the local
657: OAM client to send a loopback OAMPDU to the OAM peer with the
658: loopback enable flags cleared. Writing noLoopback to this
659: attribute has no effect.
660:
661: Writes to this attribute are ignored unless the OAM status of
662: this interface is 'operational' (dot3OamOperStatus).
663:
664: The attribute always returns noLoopback on a read. To
665: determine the loopback status, use the attribute
666: dot3OamLoopbackStatus. "
667: REFERENCE "[802.3ah], 57.2.11"
668: ::= { dot3OamLoopbackEntry 1 }
668: warning -
warning: flushing recent incorrect declaration, see previous error(s)
669:
670: dot3OamLoopbackStatus OBJECT-TYPE
671: SYNTAX INTEGER {
672: noLoopback (1),
673: initiatingLoopback (2),
674: remoteLoopback (3),
675: terminatingLoopback (4),
676: localLoopback (5),
677: unknown (6)
678: }
679: MAX-ACCESS read-only
680: STATUS current
681: DESCRIPTION
682: "The loopback status of the OAM entity. This status is
683: determined by a combination of the local parser and
684: multiplexer states, the remote parser and multiplexer states,
685: as well as by the actions of the local OAM client. When
686: operating in normal mode with no loopback in progress, the
687: status reads noLoopback(1).
688:
689: If the OAM client has sent an Loopback OAMPDU and is waiting
690: for a response, where the local parser and multiplexer states
691: are DISCARD (see [802.3ah, 57.2.11.1]), the status is
692: 'initiatingLoopback'. In this case, the local OAM entity has
693: yet to receive any acknowledgement that the remote OAM entity
694: has received its loopback command request.
695:
696: If the local OAM client knows that the remote OAM entity is in
697: loopback mode (via the remote state information as described
698: in [802.3ah, 57.2.11.1, 30.3.6.1.15]), the status is
699: EFM OAM MIB March 2005
700:
701:
702: remoteLoopback(3). If the local OAM client is in the process
703: of terminating the remote loopback [802.3ah, 57.2.11.3,
704: 30.3.6.1.14], with its local multiplexer and parser states in
705: DISCARD, the status is terminatingLoopback(4). If the remote
706: OAM client has put the local OAM entity in loopback mode as
707: indicated by its local parser state, the status is
708: localLoopback(5).
709:
710: The unknown(6) status indicates the parser and multiplexer
711: combination is unexpected. This status may be returned if the
712: OAM loopback is in a transition state but should not persist.
713:
714: The values of this attribute correspond to the following
715: values of the local and remote parser and multiplexer states.
716:
717: value LclPrsr LclMux RmtPrsr RmtMux
718: noLoopback FWD FWD FWD FWD
719: initLoopback DISCARD DISCARD FWD FWD
720: rmtLoopback DISCARD FWD LPBK DISCARD
721: tmtngLoopback DISCARD DISCARD LPBK DISCARD
722: lclLoopback LPBK DISCARD DISCARD FWD
723: unknown *** any other combination ***
724: "
725: REFERENCE "[802.3ah], REFERENCE 57.2.11, 30.3.61.14,
726: 30.3.6.1.15"
727: ::= { dot3OamLoopbackEntry 2 }
728:
729: dot3OamLoopbackIgnoreRx OBJECT-TYPE
730: SYNTAX INTEGER { ignore(1), process(2) }
731: MAX-ACCESS read-write
732: STATUS current
733: DESCRIPTION
734: "Since OAM loopback is a distruptive operation (user traffic
735: does not pass), this attribute provides a mechanism to provide
736: controls over whether received OAM loopback commands are
737: processed or ignored. When the value is ignore(1), received
738: loopback commands are ignored. When the value is process(2),
739: OAM loopback commands are processed. The default value is to
740: ignore loopback commands (ignore(1)).
741:
742: The attribute has no meaning if the local OAM entity does not
743: support the loopback function (as defined in
744: dot3OamFunctionsSupported). "
745: REFERENCE "[802.3ah], REFERENCE 57.2.11, 30.3.61.14,
746: 30.3.6.1.15"
747: ::= { dot3OamLoopbackEntry 3 }
748:
749:
750: ------------------------------------------------------------------
751: EFM OAM MIB March 2005
751: error -
`EFM' should start with a lower case letter
751: severe -
syntax error, unexpected UPPERCASE_IDENTIFIER, expecting OBJECT
752:
753:
754: --
755: -- Ethernet OAM Statistics group
756: --
757:
758:
759: dot3OamStatsTable OBJECT-TYPE
760: SYNTAX SEQUENCE OF Dot3OamStatsEntry
761: MAX-ACCESS not-accessible
762: STATUS current
763: DESCRIPTION
764: "Statistics for the OAM function on a particular Ethernet like
765: interface."
766: ::= { dot3OamMIB 4 }
766: warning -
warning: flushing recent incorrect declaration, see previous error(s)
767:
768: dot3OamStatsEntry OBJECT-TYPE
768: error -
row's parent node must be a table node
769: SYNTAX Dot3OamStatsEntry
770: MAX-ACCESS not-accessible
771: STATUS current
772: DESCRIPTION
773: "An entry in the table, containing statistics information on
774: the Ethernet OAM function for a single Ethernet like
775: interface."
776: INDEX { ifIndex }
777: ::= { dot3OamStatsTable 1 }
777: severe -
unknown object identifier label `dot3OamStatsTable'
778:
779: Dot3OamStatsEntry ::=
779: minor error -
SEQUENCE element #1 `dot3OamInformationTx' is not a child node under `dot3OamStatsEntry'
779: warning -
warning: SEQUENCE element #2 `dot3OamInformationRx' does not match order of columnar objects under `dot3OamStatsEntry'
780: SEQUENCE {
781: dot3OamInformationTx Counter32,
781: severe -
unknown object identifier label `dot3OamInformationTx'
782: dot3OamInformationRx Counter32,
783: dot3OamUniqueEventNotificationTx Counter32,
783: severe -
unknown object identifier label `dot3OamUniqueEventNotificationTx'
784: dot3OamUniqueEventNotificationRx Counter32,
785: dot3OamDuplicateEventNotificationTx Counter32,
786: dot3OamDuplicateEventNotificationRx Counter32,
787: dot3OamLoopbackControlTx Counter32,
788: dot3OamLoopbackControlRx Counter32,
788: severe -
unknown object identifier label `dot3OamLoopbackControlRx'
789: dot3OamVariableRequestTx Counter32,
790: dot3OamVariableRequestRx Counter32,
791: dot3OamVariableResponseTx Counter32,
792: dot3OamVariableResponseRx Counter32,
793: dot3OamOrgSpecificTx Counter32,
794: dot3OamOrgSpecificRx Counter32,
795: dot3OamUnsupportedCodesTx Counter32,
796: dot3OamUnsupportedCodesRx Counter32,
797: dot3OamFramesLostDueToOam Counter32
798: }
799:
800:
801: dot3OamInformationTx OBJECT-TYPE
802: SYNTAX Counter32
803: EFM OAM MIB March 2005
803: severe -
syntax error, unexpected UPPERCASE_IDENTIFIER, expecting STATUS
804:
805:
806: UNITS "frames"
807: MAX-ACCESS read-only
808: STATUS current
809: DESCRIPTION
810: "A count of the number of Information OAMPDUs transmitted on
811: this interface.
812:
813: An Information OAMPDU is indicated by a valid frame with (1)
814: destination MAC address equal to that of the reserved MAC
815: address for Slow Protocols (See 43B of [802.3ah]), (2) a
816: lengthOrType field equal to the reserved type for Slow
817: Protocols, (3) a Slow Protocols subtype equal to that of the
818: subtype reserved for OAM, and (4) an OAMPDU code equals the
819: OAM Information code.
820:
821: Discontinuities of this counter can occur at re-initialization
822: of the management system, and at other times as indicated by
823: the value of the ifCounterDiscontinuityTime. "
824: REFERENCE "[802.3ah], 30.3.6.1.20."
825: ::= { dot3OamStatsEntry 1 }
825: warning -
warning: flushing recent incorrect declaration, see previous error(s)
826:
827: dot3OamInformationRx OBJECT-TYPE
828: SYNTAX Counter32
829: UNITS "frames"
830: MAX-ACCESS read-only
831: STATUS current
832: DESCRIPTION
833: "A count of the number of Information OAMPDUs received on this
834: interface.
835:
836: An Information OAMPDU is indicated by a valid frame with (1)
837: destination MAC address equal to that of the reserved MAC
838: address for Slow Protocols (See 43B of [802.3ah]), (2) a
839: lengthOrType field equal to the reserved type for Slow
840: Protocols, (3) a Slow Protocols subtype equal to that of the
841: subtype reserved for OAM, and (4) an OAMPDU code equals the
842: OAM Information code.
843:
844: Discontinuities of this counter can occur at re-initialization
845: of the management system, and at other times as indicated by
846: the value of the ifCounterDiscontinuityTime. "
847: REFERENCE "[802.3ah], 30.3.6.1.21."
848: ::= { dot3OamStatsEntry 2 }
849:
850: dot3OamUniqueEventNotificationTx OBJECT-TYPE
851: SYNTAX Counter32
852: UNITS "frames"
853: MAX-ACCESS read-only
854: STATUS current
855: EFM OAM MIB March 2005
855: error -
description missing in object definition
855: severe -
syntax error, unexpected UPPERCASE_IDENTIFIER, expecting COLON_COLON_EQUAL
856:
857:
858: DESCRIPTION
859: "A count of the number of unique Event OAMPDUs transmitted on
860: this interface. Event notifications may be sent in duplicate
861: to increase the probability of successfully being received,
862: given the possiblity that a frame may be lost in transit.
863:
864: An Event Notification OAMPDU is indicated by a valid frame
865: with (1) destination MAC address equal to that of the reserved
866: MAC address for Slow Protocols (See 43B of [802.3ah]), (2) a
867: lengthOrType field equal to the reserved type for Slow
868: Protocols, (3) a Slow Protocols subtype equal to that of the
869: subtype reserved for OAM, and (4) an OAMPDU code equals the
870: OAM Event code.
871:
872: A unique Event Notification OAMPDU is indicated as an Event
873: Notification OAMPDU with a Sequence Number field that is
874: distinct from the previously transmitted Event Notification
875: OAMPDU Sequence Number.
876:
877: Discontinuities of this counter can occur at re-initialization
878: of the management system, and at other times as indicated by
879: the value of the ifCounterDiscontinuityTime. "
880:
881: REFERENCE "[802.3ah], 30.3.6.1.22."
882: ::= { dot3OamStatsEntry 3 }
882: warning -
warning: flushing recent incorrect declaration, see previous error(s)
883:
884: dot3OamUniqueEventNotificationRx OBJECT-TYPE
885: SYNTAX Counter32
886: UNITS "frames"
887: MAX-ACCESS read-only
888: STATUS current
889: DESCRIPTION
890: "A count of the number of unique Event OAMPDUs received on
891: this interface. Event notification OAMPDUs may be sent in
892: duplicate to increase the probability of successfully being
893: received, given the possiblity that a frame may be lost in
894: transit.
895:
896: An Event Notification OAMPDU is indicated by a valid frame
897: with (1) destination MAC address equal to that of the reserved
898: MAC address for Slow Protocols (See 43B of [802.3ah]), (2) a
899: lengthOrType field equal to the reserved type for Slow
900: Protocols, (3) a Slow Protocols subtype equal to that of the
901: subtype reserved for OAM, and (4) an OAMPDU code equals the
902: OAM Event code.
903:
904: A unique Event Notification OAMPDU is indicated as an Event
905: Notification OAMPDU with a Sequence Number field that is
906: distinct from the previously received Event Notification
907: EFM OAM MIB March 2005
908:
909:
910: OAMPDU Sequence Number.
911:
912: Discontinuities of this counter can occur at re-initialization
913: of the management system, and at other times as indicated by
914: the value of the ifCounterDiscontinuityTime. "
915: REFERENCE "[802.3ah], 30.3.6.1.24."
916: ::= { dot3OamStatsEntry 4 }
917:
918: dot3OamDuplicateEventNotificationTx OBJECT-TYPE
919: SYNTAX Counter32
920: UNITS "frames"
921: MAX-ACCESS read-only
922: STATUS current
923: DESCRIPTION
924: "A count of the number of duplicate Event OAMPDUs transmitted
925: on this interface. Event notification OAMPDUs may be sent in
926: duplicate to increase the probability of successfully being
927: received, given the possiblity that a frame may be lost in
928: transit.
929:
930: An Event Notification OAMPDU is indicated by a valid frame
931: with (1) destination MAC address equal to that of the reserved
932: MAC address for Slow Protocols (See 43B of [802.3ah]), (2) a
933: lengthOrType field equal to the reserved type for Slow
934: Protocols, (3) a Slow Protocols subtype equal to that of the
935: subtype reserved for OAM, and (4) an OAMPDU code equals the
936: OAM Event code.
937:
938: A duplicate Event Notification OAMPDU is indicated as an Event
939: Notification OAMPDU with a Sequence Number field that is
940: identical to the previously transmitted Event Notification
941: OAMPDU Sequence Number.
942:
943: Discontinuities of this counter can occur at re-initialization
944: of the management system, and at other times as indicated by
945: the value of the ifCounterDiscontinuityTime. "
946: REFERENCE "[802.3ah], 30.3.6.1.23."
947: ::= { dot3OamStatsEntry 5 }
948:
949: dot3OamDuplicateEventNotificationRx OBJECT-TYPE
950: SYNTAX Counter32
951: UNITS "frames"
952: MAX-ACCESS read-only
953: STATUS current
954: DESCRIPTION
955: "A count of the number of duplicate Event OAMPDUs received on
956: this interface. Event notification OAMPDUs may be sent in
957: duplicate to increase the probability of successfully being
958: received, given the possiblity that a frame may be lost in
959: EFM OAM MIB March 2005
960:
961:
962: transit.
963:
964: An Event Notification OAMPDU is indicated by a valid frame
965: with (1) destination MAC address equal to that of the reserved
966: MAC address for Slow Protocols (See 43B of [802.3ah]), (2) a
967: lengthOrType field equal to the reserved type for Slow
968: Protocols, (3) a Slow Protocols subtype equal to that of the
969: subtype reserved for OAM, and (4) an OAMPDU code equals the
970: OAM Event code.
971:
972: A duplicate Event Notification OAMPDU is indicated as an Event
973: Notification OAMPDU with a Sequence Number field that is
974: identical to the previously received Event Notification OAMPDU
975: Sequence Number.
976:
977: Discontinuities of this counter can occur at re-initialization
978: of the management system, and at other times as indicated by
979: the value of the ifCounterDiscontinuityTime. "
980: REFERENCE "[802.3ah], 30.3.6.1.25."
981: ::= { dot3OamStatsEntry 6 }
982:
983: dot3OamLoopbackControlTx OBJECT-TYPE
984: SYNTAX Counter32
985: UNITS "frames"
986: MAX-ACCESS read-only
987: STATUS current
988: DESCRIPTION
989: "A count of the number of Loopback Control OAMPDUs transmitted
990: on this interface.
991:
992: An Loopback Conrol OAMPDU is indicated by a valid frame with
993: (1) destination MAC address equal to that of the reserved MAC
994: address for Slow Protocols (See 43B of [802.3ah]), (2) a
995: lengthOrType field equal to the reserved type for Slow
996: Protocols, (3) a Slow Protocols subtype equal to that of the
997: subtype reserved for OAM, and (4) an OAMPDU code equals the
998: OAM Loopback Control code.
999:
1000: Discontinuities of this counter can occur at re-initialization
1001: of the management system, and at other times as indicated by
1002: the value of the ifCounterDiscontinuityTime. "
1003: REFERENCE "[802.3ah], 30.3.6.1.26."
1004: ::= { dot3OamStatsEntry 7 }
1005:
1006: dot3OamLoopbackControlRx OBJECT-TYPE
1007: SYNTAX Counter32
1008: UNITS "frames"
1009: MAX-ACCESS read-only
1010: STATUS current
1011: EFM OAM MIB March 2005
1011: error -
description missing in object definition
1011: severe -
syntax error, unexpected UPPERCASE_IDENTIFIER, expecting COLON_COLON_EQUAL
1012:
1013:
1014: DESCRIPTION
1015: "A count of the number of Loopback Control OAMPDUs transmitted
1016: on this interface.
1017:
1018: An Loopback Control OAMPDU is indicated by a valid frame with
1019: (1) destination MAC address equal to that of the reserved MAC
1020: address for Slow Protocols (See 43B of [802.3ah]), (2) a
1021: lengthOrType field equal to the reserved type for Slow
1022: Protocols, (3) a Slow Protocols subtype equal to that of the
1023: subtype reserved for OAM, and (4) an OAMPDU code equals the
1024: OAM Loopback Control code.
1025:
1026: Discontinuities of this counter can occur at re-initialization
1027: of the management system, and at other times as indicated by
1028: the value of the ifCounterDiscontinuityTime. "
1029: REFERENCE "[802.3ah], 30.3.6.1.27."
1030: ::= { dot3OamStatsEntry 8 }
1030: warning -
warning: flushing recent incorrect declaration, see previous error(s)
1031:
1032: dot3OamVariableRequestTx OBJECT-TYPE
1033: SYNTAX Counter32
1034: UNITS "frames"
1035: MAX-ACCESS read-only
1036: STATUS current
1037: DESCRIPTION
1038: "A count of the number of Variable Request OAMPDUs transmitted
1039: on this interface.
1040:
1041: An Variable Request OAMPDU is indicated by a valid frame with
1042: (1) destination MAC address equal to that of the reserved MAC
1043: address for Slow Protocols (See 43B of [802.3ah]), (2) a
1044: lengthOrType field equal to the reserved type for Slow
1045: Protocols, (3) a Slow Protocols subtype equal to that of the
1046: subtype reserved for OAM, and (4) an OAMPDU code equals the
1047: OAM Variable Request code.
1048:
1049: Discontinuities of this counter can occur at re-initialization
1050: of the management system, and at other times as indicated by
1051: the value of the ifCounterDiscontinuityTime. "
1052: REFERENCE "[802.3ah], 30.3.6.1.28."
1053: ::= { dot3OamStatsEntry 9 }
1054:
1055: dot3OamVariableRequestRx OBJECT-TYPE
1056: SYNTAX Counter32
1057: UNITS "frames"
1058: MAX-ACCESS read-only
1059: STATUS current
1060: DESCRIPTION
1061: "A count of the number of Variable Request OAMPDUs received on
1062: this interface.
1063: EFM OAM MIB March 2005
1064:
1065:
1066:
1067: An Variable Request OAMPDU is indicated by a valid frame with
1068: (1) destination MAC address equal to that of the reserved MAC
1069: address for Slow Protocols (See 43B of [802.3ah]), (2) a
1070: lengthOrType field equal to the reserved type for Slow
1071: Protocols, (3) a Slow Protocols subtype equal to that of the
1072: subtype reserved for OAM, and (4) an OAMPDU code equals the
1073: OAM Variable Request code.
1074:
1075: Discontinuities of this counter can occur at re-initialization
1076: of the management system, and at other times as indicated by
1077: the value of the ifCounterDiscontinuityTime. "
1078: REFERENCE "[802.3ah], 30.3.6.1.29."
1079: ::= { dot3OamStatsEntry 10 }
1080:
1081: dot3OamVariableResponseTx OBJECT-TYPE
1082: SYNTAX Counter32
1083: UNITS "frames"
1084: MAX-ACCESS read-only
1085: STATUS current
1086: DESCRIPTION
1087: "A count of the number of Variable Response OAMPDUs
1088: transmitted on this interface.
1089:
1090: An Variable Response OAMPDU is indicated by a valid frame with
1091: (1) destination MAC address equal to that of the reserved MAC
1092: address for Slow Protocols (See 43B of [802.3ah]), (2) a
1093: lengthOrType field equal to the reserved type for Slow
1094: Protocols, (3) a Slow Protocols subtype equal to that of the
1095: subtype reserved for OAM, and (4) an OAMPDU code equals the
1096: OAM Variable Response code.
1097:
1098: Discontinuities of this counter can occur at re-initialization
1099: of the management system, and at other times as indicated by
1100: the value of the ifCounterDiscontinuityTime. "
1101: REFERENCE "[802.3ah], 30.3.6.1.30."
1102: ::= { dot3OamStatsEntry 11 }
1103:
1104: dot3OamVariableResponseRx OBJECT-TYPE
1105: SYNTAX Counter32
1106: UNITS "frames"
1107: MAX-ACCESS read-only
1108: STATUS current
1109: DESCRIPTION
1110: "A count of the number of Variable Response OAMPDUs received
1111: on this interface.
1112:
1113: An Variable Response OAMPDU is indicated by a valid frame with
1114: (1) destination MAC address equal to that of the reserved MAC
1115: EFM OAM MIB March 2005
1116:
1117:
1118: address for Slow Protocols (See 43B of [802.3ah]), (2) a
1119: lengthOrType field equal to the reserved type for Slow
1120: Protocols, (3) a Slow Protocols subtype equal to that of the
1121: subtype reserved for OAM, and (4) an OAMPDU code equals the
1122: OAM Variable Response code.
1123:
1124: Discontinuities of this counter can occur at re-initialization
1125: of the management system, and at other times as indicated by
1126: the value of the ifCounterDiscontinuityTime. "
1127: REFERENCE "[802.3ah], 30.3.6.1.31."
1128: ::= { dot3OamStatsEntry 12 }
1129:
1130: dot3OamOrgSpecificTx OBJECT-TYPE
1131: SYNTAX Counter32
1132: UNITS "frames"
1133: MAX-ACCESS read-only
1134: STATUS current
1135: DESCRIPTION
1136: "A count of the number of Organization Specific OAMPDUs
1137: transmitted on this interface.
1138:
1139: An Organization Specific OAMPDU is indicated by a valid frame
1140: with (1) destination MAC address equal to that of the reserved
1141: MAC address for Slow Protocols (See 43B of [802.3ah]), (2) a
1142: lengthOrType field equal to the reserved type for Slow
1143: Protocols, (3) a Slow Protocols subtype equal to that of the
1144: subtype reserved for OAM, and (4) an OAMPDU code equals the
1145: OAM Organization Specific code.
1146:
1147: Discontinuities of this counter can occur at re-initialization
1148: of the management system, and at other times as indicated by
1149: the value of the ifCounterDiscontinuityTime. "
1150: REFERENCE "[802.3ah], 30.3.6.1.32."
1151: ::= { dot3OamStatsEntry 13 }
1152:
1153: dot3OamOrgSpecificRx OBJECT-TYPE
1154: SYNTAX Counter32
1155: UNITS "frames"
1156: MAX-ACCESS read-only
1157: STATUS current
1158: DESCRIPTION
1159:
1160: "A count of the number of Organization Specific OAMPDUs
1161: received on this interface.
1162:
1163: An Organization Specific OAMPDU is indicated by a valid frame
1164: with (1) destination MAC address equal to that of the reserved
1165: MAC address for Slow Protocols (See 43B of [802.3ah]), (2) a
1166: lengthOrType field equal to the reserved type for Slow
1167: EFM OAM MIB March 2005
1168:
1169:
1170: Protocols, (3) a Slow Protocols subtype equal to that of the
1171: subtype reserved for OAM, and (4) an OAMPDU code equals the
1172: OAM Organization Specific code.
1173:
1174: Discontinuities of this counter can occur at re-initialization
1175: of the management system, and at other times as indicated by
1176: the value of the ifCounterDiscontinuityTime. "
1177: REFERENCE "[802.3ah], 30.3.6.1.33."
1178: ::= { dot3OamStatsEntry 14 }
1179:
1180: dot3OamUnsupportedCodesTx OBJECT-TYPE
1181: SYNTAX Counter32
1182: UNITS "frames"
1183: MAX-ACCESS read-only
1184: STATUS current
1185: DESCRIPTION
1186: "A count of the number of OAMPDUs transmitted on this
1187: interface with an unsupported op-code.
1188:
1189: An unsupported opcode OAMPDU is indicated by a valid frame
1190: with (1) destination MAC address equal to that of the reserved
1191: MAC address for Slow Protocols (See 43B of [802.3ah]), (2) a
1192: lengthOrType field equal to the reserved type for Slow
1193: Protocols, (3) a Slow Protocols subtype equal to that of the
1194: subtype reserved for OAM, and (4) an OAMPDU code equals the
1195: opcode for a function that is not supported by the device.
1196:
1197: Discontinuities of this counter can occur at re-initialization
1198: of the management system, and at other times as indicated by
1199: the value of the ifCounterDiscontinuityTime. "
1200: REFERENCE "[802.3ah], 30.3.6.1.18."
1201: ::= { dot3OamStatsEntry 15 }
1202:
1203: dot3OamUnsupportedCodesRx OBJECT-TYPE
1204: SYNTAX Counter32
1205: UNITS "frames"
1206: MAX-ACCESS read-only
1207: STATUS current
1208: DESCRIPTION
1209: "A count of the number of OAMPDUs received on this interface
1210: with an unsupported op-code.
1211:
1212: An unsupported opcode OAMPDU is indicated by a valid frame
1213: with (1) destination MAC address equal to that of the reserved
1214: MAC address for Slow Protocols (See 43B of [802.3ah]), (2) a
1215: lengthOrType field equal to the reserved type for Slow
1216: Protocols, (3) a Slow Protocols subtype equal to that of the
1217: subtype reserved for OAM, and (4) an OAMPDU code equals the
1218: opcode for a function that is not supported by the device.
1219: EFM OAM MIB March 2005
1220:
1221:
1222:
1223: Discontinuities of this counter can occur at re-initialization
1224: of the management system, and at other times as indicated by
1225: the value of the ifCounterDiscontinuityTime. "
1226: REFERENCE "[802.3ah], 30.3.6.1.19."
1227: ::= { dot3OamStatsEntry 16 }
1228:
1229: dot3OamFramesLostDueToOam OBJECT-TYPE
1230: SYNTAX Counter32
1231: UNITS "frames"
1232: MAX-ACCESS read-only
1233: STATUS current
1234: DESCRIPTION
1235: "A count of the number of frames that were dropped by the OAM
1236: multiplexer. Since the OAM mulitplexer has multiple inputs
1237: and a single output, there may be cases where frames are
1238: dropped due to transmit resource contention. This counter is
1239: incremented whenever a frame is dropped by the OAM layer.
1240: When this counter is incremented, no other counters in this
1241: MIB are incremented.
1242:
1243: Discontinuities of this counter can occur at re-initialization
1244: of the management system, and at other times as indicated by
1245: the value of the ifCounterDiscontinuityTime. "
1246: REFERENCE "[802.3ah], 30.3.6.1.46."
1247: ::= { dot3OamStatsEntry 17 }
1248:
1249:
1250: ------------------------------------------------------------------
1251: --
1252: -- Ethernet OAM Event Configuration group
1253: --
1254:
1255:
1256: dot3OamEventConfigTable OBJECT-TYPE
1257: SYNTAX SEQUENCE OF Dot3OamEventConfigEntry
1257: error -
unknown type `Dot3OamEventConfigEntry'
1258: MAX-ACCESS not-accessible
1259: STATUS current
1260: DESCRIPTION
1261: "Ethernet OAM includes the ability to generate and receive
1262: event notifications to indicate various link problems. This
1263: table contains the mechanisms to configure the thresholds to
1264: generate the standard Ethernet OAM events.
1265:
1266: These events are:
1267: - Errored Symbol Period Event. Generated when the number of
1268: symbol errors exceeds a threshold within a given window
1269: defined by a number of symbols (e.g. 1,000 symbols out of
1270: 1,000,000 had errors).
1271: EFM OAM MIB March 2005
1272:
1273:
1274: - Errored Frame Period Event. Generated when the number of
1275: frame errors exceeds a threshold within a given window
1276: defined by a number of frames (e.g. 10 frames out of 1000
1277: had errors).
1278: - Errored Frame Event. Generated when the number of frame
1279: errors exceeds a threshold within a given window defined
1280: by a period of time (e.g. 10 frames in 1 second had
1281: errors).
1282: - Errored Frame Seconds Summary Event. Generated when the
1283: number of errored frame seconds exceeds a threshold within
1284: a given time period (e.g. 10 errored frame seconds within
1285: the last 100 seconds). An errored frame second is defined
1286: as a 1 second interval which had >0 frame errors.
1287: "
1288: ::= { dot3OamMIB 5 }
1289:
1290: dot3OamEventConfigEntry OBJECT-TYPE
1291: SYNTAX Dot3OamEventConfigEntry
1292: MAX-ACCESS not-accessible
1293: STATUS current
1294: DESCRIPTION
1295: "Event configuration information is available for every
1296: Ethernet like interface that supports OAM and the event
1297: function of OAM as indicated in the dot3OamFunctionsSupported
1298: attribute.
1299:
1300: Event configuration controls when the local management entity
1301: sends Event Notification OAMPDUs to its OAM peer. "
1302: INDEX { ifIndex }
1303: ::= { dot3OamEventConfigTable 1 }
1304:
1305: Dot3OamEventConfigEntry ::=
1306: SEQUENCE {
1307: dot3OamErrSymPeriodWindowHi Unsigned32,
1308: dot3OamErrSymPeriodWindowLo Unsigned32,
1308: severe -
unknown object identifier label `dot3OamErrSymPeriodWindowLo'
1309: dot3OamErrSymPeriodThresholdHi Unsigned32,
1310: dot3OamErrSymPeriodThresholdLo Unsigned32,
1311: dot3OamErrSymPeriodEvNotifEnable INTEGER,
1312: dot3OamErrFramePeriodWindow Unsigned32,
1313: dot3OamErrFramePeriodThreshold Unsigned32,
1313: severe -
unknown object identifier label `dot3OamErrFramePeriodThreshold'
1314: dot3OamErrFramePeriodEvNotifEnable INTEGER,
1315: dot3OamErrFrameWindow Unsigned32,
1316: dot3OamErrFrameThreshold Unsigned32,
1316: severe -
unknown object identifier label `dot3OamErrFrameThreshold'
1317: dot3OamErrFrameEvNotifEnable INTEGER,
1318: dot3OamErrFrameSecsSummaryWindow Integer32,
1319: dot3OamErrFrameSecsSummaryThreshold Integer32,
1319: severe -
unknown object identifier label `dot3OamErrFrameSecsSummaryThreshold'
1320: dot3OamErrFrameSecsEvNotifEnable INTEGER,
1321: dot3OamDyingGaspEnable INTEGER,
1321: severe -
unknown object identifier label `dot3OamDyingGaspEnable'
1322: dot3OamCriticalEventEnable INTEGER
1323: EFM OAM MIB March 2005
1323: severe -
syntax error, unexpected UPPERCASE_IDENTIFIER, expecting '}' or ','
1324:
1325:
1326: }
1326: warning -
warning: flushing recent incorrect declaration, see previous error(s)
1327:
1328: dot3OamErrSymPeriodWindowHi OBJECT-TYPE
1329: SYNTAX Unsigned32
1330: UNITS "2^32 symbols"
1331: MAX-ACCESS read-write
1332: STATUS current
1333: DESCRIPTION
1334: "The two objects dot3OamErrSymPeriodWindowHi and
1335: dot3OamErrSymPeriodLo together form an unsigned 64-bit
1336: integer representing the number of symbols over which this
1337: threshold event is defined. This is defined as
1338:
1339: dot3OamErrSymPeriodWindow = ((2^32)*dot3OamErrSymPeriodWindowHi)
1340: + dot3OamErrSymPeriodWindowLo
1341:
1342: If dot3OamErrSymPeriodThreshold symbol errors occur within a
1343: window of dot3OamErrSymPeriodWindow symbols, an Event
1344: Notification OAMPDU should be generated with an Errored Symbol
1345: Period Event TLV indicating the threshold has been crossed in
1346: this window.
1347:
1348: The default value for dot3OamErrSymPeriodWindow is the number
1349: of symbols in one second for the underlying physical layer."
1350: REFERENCE "[802.3ah], 30.3.6.1.34"
1351: ::= { dot3OamEventConfigEntry 1 }
1352:
1353: dot3OamErrSymPeriodWindowLo OBJECT-TYPE
1354: SYNTAX Unsigned32
1355: UNITS "symbols"
1356: MAX-ACCESS read-write
1357: STATUS current
1358: DESCRIPTION
1359: "The two objects dot3OamErrSymPeriodWindowHi and
1360: dot3OamErrSymPeriodWindowLo together form an unsigned 64-bit
1361: integer representing the number of symbols over which this
1362: threshold event is defined. This is defined as
1363:
1364: dot3OamErrSymPeriodWindow = ((2^32)*dot3OamErrSymPeriodWindowHi)
1365: + dot3OamErrSymPeriodWindowLo
1366:
1367: If dot3OamErrSymPeriodThreshold symbol errors occur within a
1368: window of dot3OamErrSymPeriodWindow symbols, an Event
1369: Notification OAMPDU should be generated with an Errored Symbol
1370: Period Event TLV indicating the threshold has been crossed in
1371: this window.
1372:
1373: The default value for dot3OamErrSymPeriodWindow is the number
1374: of symbols in one second for the underlying physical layer. "
1375: EFM OAM MIB March 2005
1375: severe -
syntax error, unexpected UPPERCASE_IDENTIFIER, expecting COLON_COLON_EQUAL
1376:
1377:
1378: REFERENCE "[802.3ah], 30.3.6.1.34"
1379: ::= { dot3OamEventConfigEntry 2 }
1379: warning -
warning: flushing recent incorrect declaration, see previous error(s)
1380:
1381: dot3OamErrSymPeriodThresholdHi OBJECT-TYPE
1382: SYNTAX Unsigned32
1383: UNITS "2^32 symbols"
1384: MAX-ACCESS read-write
1385: STATUS current
1386: DESCRIPTION
1387: "The two objects dot3OamErrSymPeriodThresholdHi and
1388: dot3OamErrSymPeriodThresholdLo together form an unsigned
1389: 64-bit integer representing the number of symbol errors that
1390: must occur within a given window to cause this event.
1391:
1392: This is defined as
1393:
1394: dot3OamErrSymPeriodThreshold =
1395: ((2^32) * dot3OamErrSymPeriodThresholdHi)
1396: + dot3OamErrSymPeriodThresholdLo
1397:
1398:
1399: If dot3OamErrSymPeriodThreshold symbol errors occur within a
1400: window of dot3OamErrSymPeriodWindow symbols, an Event
1401: Notification OAMPDU should be generated with an Errored Symbol
1402: Period Event TLV indicating the threshold has been crossed in
1403: this window.
1404:
1405: The default value for dot3OamErrSymPeriodThreshold is one
1406: symbol errors. "
1407: REFERENCE "[802.3ah], 30.3.6.1.34"
1408: ::= { dot3OamEventConfigEntry 3 }
1409:
1410: dot3OamErrSymPeriodThresholdLo OBJECT-TYPE
1411: SYNTAX Unsigned32
1412: UNITS "symbols"
1413: MAX-ACCESS read-write
1414: STATUS current
1415: DESCRIPTION
1416: "The two objects dot3OamErrSymPeriodThresholdHi and
1417: dot3OamErrSymPeriodThresholdLo together form an unsigned
1418: 64-bit integer representing the number of symbol errors that
1419: must occur within a given window to cause this event.
1420:
1421: This is defined as
1422:
1423: dot3OamErrSymPeriodThreshold =
1424: ((2^32) * dot3OamErrSymPeriodThresholdHi)
1425: + dot3OamErrSymPeriodThresholdLo
1426:
1427: EFM OAM MIB March 2005
1428:
1429:
1430:
1431: If dot3OamErrSymPeriodThreshold symbol errors occur within a
1432: window of dot3OamErrSymPeriodWindow symbols, an Event
1433: Notification OAMPDU should be generated with an Errored Symbol
1434: Period Event TLV indicating the threshold has been crossed in
1435: this window.
1436:
1437: The default value for dot3OamErrSymPeriodThreshold is one
1438: symbol error. "
1439: REFERENCE "[802.3ah], 30.3.6.1.34"
1440: ::= { dot3OamEventConfigEntry 4 }
1441:
1442: dot3OamErrSymPeriodEvNotifEnable OBJECT-TYPE
1443: SYNTAX INTEGER { enabled(1), disabled(2) }
1444: MAX-ACCESS read-write
1445: STATUS current
1446: DESCRIPTION
1447: "Indicates whether the occurence of Errored Symbol Period
1448: Events should result in Event Notification OAMPDUs generated
1449: by the OAM layer.
1450:
1451: By default, this object should have the value enabled(1) for
1452: Ethernet like interfaces that support OAM. If the OAM layer
1453: does not support event notifications (as indicated via the
1454: dot3OamFunctionsSupported attribute), this value is ignored.
1455: "
1456: ::= { dot3OamEventConfigEntry 5 }
1457:
1458: dot3OamErrFramePeriodWindow OBJECT-TYPE
1458: change recommended -
warning: node `dot3OamErrFramePeriodWindow' must be contained in at least one conformance group
1459: SYNTAX Unsigned32
1460: UNITS "frames"
1461: MAX-ACCESS read-write
1462: STATUS current
1463: DESCRIPTION
1464: "The number of frames over which the threshold is defined.
1465: The
1466: default value of the window is the number of minimum size
1467: Ethernet frames that can be received over the physical layer
1468: in
1469: one second.
1470:
1471: If dot3OamErrFramePeriodThreshold frame errors occur within a
1472: window of dot3OamErrFramePeriodWindow frames, an Event
1473: Notification OAMPDU should be generated with an Errored Frame
1474: Period Event TLV indicating the threshold has been crossed in
1475: this window. "
1476: REFERENCE "[802.3ah], 30.3.6.1.38"
1477: ::= { dot3OamEventConfigEntry 6 }
1478: EFM OAM MIB March 2005
1478: error -
`EFM' should start with a lower case letter
1478: severe -
syntax error, unexpected UPPERCASE_IDENTIFIER, expecting OBJECT
1479:
1480:
1481: dot3OamErrFramePeriodThreshold OBJECT-TYPE
1482: SYNTAX Unsigned32
1483: UNITS "frames"
1484: MAX-ACCESS read-write
1485: STATUS current
1486: DESCRIPTION
1487: "The number of frame errors that must occur for this event to
1488: be triggered. The default value is one frame error.
1489:
1490: If dot3OamErrFramePeriodThreshold frame errors occur within a
1491: window of dot3OamErrFramePeriodWindow frames, an Event
1492: Notification OAMPDU should be generated with an Errored Frame
1493: Period Event TLV indicating the threshold has been crossed in
1494: this window. "
1495: REFERENCE "[802.3ah], 30.3.6.1.38"
1496: ::= { dot3OamEventConfigEntry 7 }
1496: warning -
warning: flushing recent incorrect declaration, see previous error(s)
1497:
1498: dot3OamErrFramePeriodEvNotifEnable OBJECT-TYPE
1498: change recommended -
warning: node `dot3OamErrFramePeriodEvNotifEnable' must be contained in at least one conformance group
1499: SYNTAX INTEGER { enabled(1), disabled(2) }
1500: MAX-ACCESS read-write
1501: STATUS current
1502: DESCRIPTION
1503: "Indicates whether the occurence of an Errored Frame Period
1504: Event should result in an Event Notification OAMPDU generated
1505: by the OAM layer.
1506:
1507: By default, this object should have the value enabled(1) for
1508: Ethernet like interfaces that support OAM. If the OAM layer
1509: does not support event notifications (as indicated via the
1510: dot3OamFunctionsSupported attribute), this value is ignored. "
1511: ::= { dot3OamEventConfigEntry 8 }
1512:
1513: dot3OamErrFrameWindow OBJECT-TYPE
1514: SYNTAX Unsigned32
1515: UNITS "tenths of a second"
1516: MAX-ACCESS read-write
1517: STATUS current
1518: DESCRIPTION
1519: "The amount of time (in 100ms increments) over which the
1520: threshold is defined. The default value is 10 (1 second).
1521:
1522: If dot3OamErrFrameThreshold frame errors occur within a window
1523: of dot3OamErrFrameWindow seconds (measured in tenths of
1524: seconds), an Event Notification OAMPDU should be generated with
1525: an Errored Frame Event TLV indicating the threshold has been
1526: crossed in this window. "
1527: REFERENCE "[802.3ah], 30.3.6.1.36"
1528: ::= { dot3OamEventConfigEntry 9 }
1529: EFM OAM MIB March 2005
1529: error -
`EFM' should start with a lower case letter
1529: severe -
syntax error, unexpected UPPERCASE_IDENTIFIER, expecting OBJECT
1530:
1531:
1532:
1533: dot3OamErrFrameThreshold OBJECT-TYPE
1534: SYNTAX Unsigned32
1535: UNITS "frames"
1536: MAX-ACCESS read-write
1537: STATUS current
1538: DESCRIPTION
1539: "The number of frame errors that must occur for this event to
1540: be triggered. The default value is one frame error.
1541:
1542: If dot3OamErrFrameThreshold frame errors occur within a window
1543: of dot3OamErrFrameWindow (in tenths of seconds), an Event
1544: Notification OAMPDU should be generated with an Errored Frame
1545: Event TLV indicating the threshold has been crossed in this
1546: window. "
1547: REFERENCE "[802.3ah], 30.3.6.1.36"
1548: ::= { dot3OamEventConfigEntry 10 }
1548: warning -
warning: flushing recent incorrect declaration, see previous error(s)
1549:
1550: dot3OamErrFrameEvNotifEnable OBJECT-TYPE
1551: SYNTAX INTEGER { enabled(1), disabled(2) }
1552: MAX-ACCESS read-write
1553: STATUS current
1554: DESCRIPTION
1555: "Indicates whether the occurence of an Errored Frame Event
1556: should result in an Event Notification OAMPDU generated by the
1557: OAM layer.
1558:
1559: By default, this object should have the value enabled(1) for
1560: Ethernet like interfaces that support OAM. If the OAM layer
1561: does not support event notifications (as indicated via the
1562: dot3OamFunctionsSupported attribute), this value is ignored. "
1563: ::= { dot3OamEventConfigEntry 11 }
1564:
1565: dot3OamErrFrameSecsSummaryWindow OBJECT-TYPE
1566: SYNTAX Integer32 (100..9000)
1567: UNITS "tenths of a second"
1568: MAX-ACCESS read-write
1569: STATUS current
1570: DESCRIPTION
1571: "The amount of time (in 100ms intervals) over which the
1572: threshold is defined. The default value is 100 (10 seconds).
1573:
1574: If dot3OamErrFrameSecsSummaryThreshold frame errors occur
1575: within a window of dot3OamErrFrameSecsSummaryWindow (in tenths
1576: of seconds), an Event Notification OAMPDU should be generated
1577: with an Errored Frame Seconds Summary Event TLV indicating the
1578: threshold has been crossed in this window. "
1579: REFERENCE "[802.3ah], 30.3.6.1.40"
1580: ::= { dot3OamEventConfigEntry 12 }
1581: EFM OAM MIB March 2005
1581: error -
`EFM' should start with a lower case letter
1581: severe -
syntax error, unexpected UPPERCASE_IDENTIFIER, expecting OBJECT
1582:
1583:
1584:
1585: dot3OamErrFrameSecsSummaryThreshold OBJECT-TYPE
1586: SYNTAX Integer32 (1..900)
1587: UNITS "errored frame seconds"
1588: MAX-ACCESS read-write
1589: STATUS current
1590: DESCRIPTION
1591: "The number of errored frame seconds that must occur for this
1592: event to be triggered. The default value is one errored frame
1593: second.
1594:
1595: If dot3OamErrFrameSecsSummaryThreshold frame errors occur
1596: within a window of dot3OamErrFrameSecsSummaryWindow (in tenths
1597: of seconds), an Event Notification OAMPDU should be generated
1598: with an Errored Frame Seconds Summary Event TLV indicating the
1599: threshold has been crossed in this window. "
1600: REFERENCE "[802.3ah], 30.3.6.1.40"
1601: ::= { dot3OamEventConfigEntry 13 }
1601: warning -
warning: flushing recent incorrect declaration, see previous error(s)
1602:
1603: dot3OamErrFrameSecsEvNotifEnable OBJECT-TYPE
1604: SYNTAX INTEGER { enabled(1), disabled(2) }
1605: MAX-ACCESS read-write
1606: STATUS current
1607: DESCRIPTION
1608: "Indicates whether the occurence of an Errored Frame Seconds
1609: Summary Event should result in an Event Notification OAMPDU
1610: generated by the OAM layer.
1611:
1612: By default, this object should have the value enabled(1) for
1613: Ethernet like interfaces that support OAM. If the OAM layer
1614: does not support event notifications (as indicated via the
1615: dot3OamFunctionsSupported attribute), this value is ignored."
1616: ::= { dot3OamEventConfigEntry 14 }
1617:
1618: dot3OamDyingGaspEnable OBJECT-TYPE
1619: SYNTAX INTEGER { enabled(1), disabled(2) }
1620: MAX-ACCESS read-write
1621: STATUS current
1622: DESCRIPTION
1623: "Indicates whether the local device should attempt to indicate
1624: a dying gasp fault via the OAMPDU flags field to its peer OAM
1625: entity. If the system does not support dying gasp capability,
1626: setting this object has no effect, and reading the object
1627: should always result in 'disabled(2)'.
1628:
1629: By default, this object should have the value enabled(1) for
1630: Ethernet like interfaces that support OAM. If the OAM layer
1631: does not support event notifications (as indicated via the
1632: dot3OamFunctionsSupported attribute), this value is ignored."
1633: EFM OAM MIB March 2005
1633: severe -
syntax error, unexpected UPPERCASE_IDENTIFIER, expecting COLON_COLON_EQUAL
1634:
1635:
1636: ::= { dot3OamEventConfigEntry 15 }
1636: warning -
warning: flushing recent incorrect declaration, see previous error(s)
1637:
1638: dot3OamCriticalEventEnable OBJECT-TYPE
1639: SYNTAX INTEGER { enabled(1), disabled(2) }
1640: MAX-ACCESS read-write
1641: STATUS current
1642: DESCRIPTION
1643: "Indicates whether the local device should attempt to indicate
1644: a critical event fault via the OAMPDU flags field to its peer
1645: OAM entity. If the system does not support critical event
1646: capability, setting this object has no effect, and reading the
1647: object should always result in 'disabled(2)'.
1648:
1649: By default, this object should have the value enabled(1) for
1650: Ethernet like interfaces that support OAM. If the OAM layer
1651: does not support event notifications (as indicated via the
1652: dot3OamFunctionsSupported attribute), this value is ignored."
1653: ::= { dot3OamEventConfigEntry 16 }
1654:
1655:
1656: ------------------------------------------------------------------
1657: --
1658: -- Ethernet OAM Event Status group
1659: --
1660:
1661: dot3OamEventLogTable OBJECT-TYPE
1662: SYNTAX SEQUENCE OF Dot3OamEventLogEntry
1662: error -
unknown type `Dot3OamEventLogEntry'
1663: MAX-ACCESS not-accessible
1664: STATUS current
1665: DESCRIPTION
1666: "This table records a history of the events that have occurred
1667: at the Ethernet OAM level. These events can include locally
1668: detected events, which may result in locally generated
1669: OAMPDUs, and remotely detected events, which are detected by
1670: the OAM peer entity and signaled to the local entity via
1671: Ethernet OAM. Ethernet OAM events can be signaled by Event
1672: Notification OAMPDUs or by the flags field in any OAMPDU. "
1673: ::= { dot3OamMIB 6 }
1674:
1675: dot3OamEventLogEntry OBJECT-TYPE
1676: SYNTAX Dot3OamEventLogEntry
1677: MAX-ACCESS not-accessible
1678: STATUS current
1679: DESCRIPTION "An entry in the dot3OamEventLogTable."
1680: INDEX { ifIndex, dot3OamEventLogIndex }
1681: ::= { dot3OamEventLogTable 1 }
1682:
1683: Dot3OamEventLogEntry ::=
1684: SEQUENCE {
1685: EFM OAM MIB March 2005
1685: severe -
syntax error, unexpected UPPERCASE_IDENTIFIER, expecting LOWERCASE_IDENTIFIER
1686:
1687:
1688: dot3OamEventLogIndex Unsigned32,
1689: dot3OamEventLogTimestamp TimeStamp,
1690: dot3OamEventLogOui Dot3Oui,
1691: dot3OamEventLogType Unsigned32,
1692: dot3OamEventLogLocation INTEGER,
1693: dot3OamEventLogWindowHi Unsigned32,
1694: dot3OamEventLogWindowLo Unsigned32,
1695: dot3OamEventLogThresholdHi Unsigned32,
1696: dot3OamEventLogThresholdLo Unsigned32,
1697: dot3OamEventLogValue CounterBasedGauge64,
1698: dot3OamEventLogRunningTotal CounterBasedGauge64,
1699: dot3OamEventLogEventTotal Unsigned32
1700: }
1700: warning -
warning: flushing recent incorrect declaration, see previous error(s)
1701:
1702: dot3OamEventLogIndex OBJECT-TYPE
1703: SYNTAX Unsigned32
1704: MAX-ACCESS not-accessible
1705: STATUS current
1706: DESCRIPTION
1707: "An arbitrary integer for identifiying individual events
1708: within the event log. "
1709: ::= { dot3OamEventLogEntry 1 }
1710:
1711: dot3OamEventLogTimestamp OBJECT-TYPE
1711: change recommended -
warning: node `dot3OamEventLogTimestamp' must be contained in at least one conformance group
1712: SYNTAX TimeStamp
1713: MAX-ACCESS read-only
1714: STATUS current
1715: DESCRIPTION
1716: "The value of sysUpTime at the time of the logged event. For
1717: locally generated events, the time of the event can be
1718: accurately retrieved from sysUpTime. For remotely generated
1719: events, the time of the event is indicated by the reception of
1720: the Event Notification OAMPDU indicating the event occurred on
1721: the peer. A system may attempt to adjust the timestamp value
1722: to more accurately reflect the time of the event at the peer
1723: OAM entity by using other information, such as that found in
1724: the timestamp found of the Event Notification TLVs, which
1725: provides an indication of the relative time between events at
1726: the peer entity. "
1727: ::= { dot3OamEventLogEntry 2 }
1728:
1729: dot3OamEventLogOui OBJECT-TYPE
1729: change recommended -
warning: node `dot3OamEventLogOui' must be contained in at least one conformance group
1730: SYNTAX Dot3Oui
1731: MAX-ACCESS read-only
1732: STATUS current
1733: DESCRIPTION
1734: "The OUI of the entity defining the object type. All IEEE
1735: 802.3 defined events (as appearing in [802.3ah] except for the
1736: Organizationally Unique Event TLVs) use the IEEE 802.3 OUI of
1737: EFM OAM MIB March 2005
1738:
1739:
1740: 0x0180C2. Organizations defining their own Event Notification
1741: TLVs include their OUI in the Event Notification TLV which
1742: gets reflected here. "
1743: ::= { dot3OamEventLogEntry 3 }
1744:
1745:
1746: dot3OamEventLogType OBJECT-TYPE
1746: change recommended -
warning: node `dot3OamEventLogType' must be contained in at least one conformance group
1747: SYNTAX Unsigned32
1748: MAX-ACCESS read-only
1749: STATUS current
1750: DESCRIPTION
1751: "The type of event that generated this entry in the event log.
1752:
1753: When the OUI is the IEEE 802.3 OUI of 0x0180C2, the following
1754: event types are defined:
1755: erroredSymbolEvent(1),
1756: erroredFramePeriodEvent (2),
1757: erroredFrameEvent(3),
1758: erroredFrameSecondsEvent(4),
1759: linkFault(256),
1760: dyingGaspEvent(257),
1761: criticalLinkEvent(258)
1762: The first four are considered threshold crossing events as
1763: they are generated when a metric exceeds a given value within
1764: a specified window. The other three are not threshold
1765: crossing events.
1766:
1767: When the OUI is not 0x0180C2, then some other organization has
1768: defined the event space. If event subtyping is known to the
1769: implementation, it may be reflected here. Otherwise, this
1770: value should return all Fs (0xFFFFFFFF).
1771: "
1772: REFERENCE "[802.3ah], 30.3.6.1.10 and 57.5.3."
1773: ::= { dot3OamEventLogEntry 4 }
1774:
1775: dot3OamEventLogLocation OBJECT-TYPE
1775: change recommended -
warning: node `dot3OamEventLogLocation' must be contained in at least one conformance group
1776: SYNTAX INTEGER { local(1), remote(2) }
1777: MAX-ACCESS read-only
1778: STATUS current
1779: DESCRIPTION
1780: "Whether this event occurred locally, or was received from the
1781: OAM peer via Ethernet OAM."
1782: ::= { dot3OamEventLogEntry 5 }
1783:
1784: dot3OamEventLogWindowHi OBJECT-TYPE
1785: SYNTAX Unsigned32
1786: MAX-ACCESS read-only
1787: STATUS current
1788: DESCRIPTION
1789: EFM OAM MIB March 2005
1789: severe -
syntax error, unexpected UPPERCASE_IDENTIFIER, expecting QUOTED_STRING
1790:
1791:
1792: "If the event represents a threshold crossing event, the two
1793: objects dot3OamEventWindowHi and dot3OamEventWindowLo form an
1794: unsigned 64-bit integer yielding the window over which the
1795: value was measured for the threshold crossing event (e.g. 5,
1796: when 11 occurrences happened in 5 seconds while the threshold
1797: was 10). The two objects are combined as:
1798:
1799: dot3OamEventLogWindow = ((2^32) * dot3OamEventLogWindowHi)
1800: + dot3OamEventLogWindowLo
1801:
1802:
1803: Otherwise, this value is returned as all F's (0xFFFFFFFF) and
1804: adds no useful information. "
1805: REFERENCE "[802.3ah], 30.3.6.1.37 and 57.5.3.2."
1806: ::= { dot3OamEventLogEntry 6 }
1806: warning -
warning: flushing recent incorrect declaration, see previous error(s)
1807:
1808: dot3OamEventLogWindowLo OBJECT-TYPE
1808: change recommended -
warning: node `dot3OamEventLogWindowLo' must be contained in at least one conformance group
1809: SYNTAX Unsigned32
1810: MAX-ACCESS read-only
1811: STATUS current
1812: DESCRIPTION
1813: "If the event represents a threshold crossing event, the two
1814: objects dot3OamEventWindowHi and dot3OamEventWindowLo form an
1815: unsigned 64-bit integer yielding the window over which the
1816: value was measured for the threshold crossing event (e.g. 5,
1817: when 11 occurrences happened in 5 seconds while the threshold
1818: was 10). The two objects are combined as:
1819:
1820: dot3OamEventLogWindow = ((2^32) * dot3OamEventLogWindowHi)
1821: + dot3OamEventLogWindowLo
1822:
1823: Otherwise, this value is returned as all F's (0xFFFFFFFF) and
1824: adds no useful information. "
1825: REFERENCE "[802.3ah], 30.3.6.1.37 and 57.5.3.2."
1826: ::= { dot3OamEventLogEntry 7 }
1827:
1828: dot3OamEventLogThresholdHi OBJECT-TYPE
1828: change recommended -
warning: node `dot3OamEventLogThresholdHi' must be contained in at least one conformance group
1829: SYNTAX Unsigned32
1830: MAX-ACCESS read-only
1831: STATUS current
1832: DESCRIPTION
1833: "If the event represents a threshold crossing event, the two
1834: objects dot3OamEventThresholdHi and dot3OamEventThresholdLo
1835: form an unsigned 64-bit integer yielding the value that was
1836: crossed for the threshold crossing event (e.g. 10, when 11
1837: occurrences happened in 5 seconds while the threshold was 10).
1838: The two objects are combined as:
1839:
1840: dot3OamEventLogThreshold = ((2^32) * dot3OamEventLogThresholdHi)
1841: EFM OAM MIB March 2005
1842:
1843:
1844: + dot3OamEventLogThresholdLo
1845:
1846: Otherwise, this value is returned as all F's (0xFFFFFFFF) and
1847: adds no useful information. "
1848: REFERENCE "[802.3ah], 30.3.6.1.37 and 57.5.3.2."
1849: ::= { dot3OamEventLogEntry 8 }
1850:
1851: dot3OamEventLogThresholdLo OBJECT-TYPE
1851: change recommended -
warning: node `dot3OamEventLogThresholdLo' must be contained in at least one conformance group
1852: SYNTAX Unsigned32
1853: MAX-ACCESS read-only
1854: STATUS current
1855: DESCRIPTION
1856: "If the event represents a threshold crossing event, the two
1857: objects dot3OamEventThresholdHi and dot3OamEventThresholdLo
1858: form an unsigned 64-bit integer yielding the value that was
1859: crossed for the threshold crossing event (e.g. 10, when 11
1860: occurrences happened in 5 seconds while the threshold was 10).
1861: The two objects are combined as:
1862:
1863: dot3OamEventLogThreshold = ((2^32) * dot3OamEventLogThresholdHi)
1864: + dot3OamEventLogThresholdLo
1865:
1866: Otherwise, this value is returned as all F's (0xFFFFFFFF) and
1867: adds no useful information. "
1868: REFERENCE "[802.3ah], 30.3.6.1.37 and 57.5.3.2."
1869: ::= { dot3OamEventLogEntry 9 }
1870:
1871: dot3OamEventLogValue OBJECT-TYPE
1871: change recommended -
warning: node `dot3OamEventLogValue' must be contained in at least one conformance group
1872: SYNTAX CounterBasedGauge64
1873: MAX-ACCESS read-only
1874: STATUS current
1875: DESCRIPTION
1876: "If the event represents a threshold crossing event, this
1877: value indicates the value of the parameter within the given
1878: window that generated this event (e.g. 11, when 11 occurrences
1879: happened in 5 seconds while the threshold was 10).
1880:
1881: Otherwise, this value is returned as all F's
1882: (0xFFFFFFFFFFFFFFFF) and adds no useful information.
1883: "
1884: REFERENCE "[802.3ah], 30.3.6.1.37 and 57.5.3.2."
1885: ::= { dot3OamEventLogEntry 10 }
1886:
1887: dot3OamEventLogRunningTotal OBJECT-TYPE
1887: change recommended -
warning: node `dot3OamEventLogRunningTotal' must be contained in at least one conformance group
1888: SYNTAX CounterBasedGauge64
1889: MAX-ACCESS read-only
1890: STATUS current
1891: DESCRIPTION
1892: "This value respresents the total number of times this
1893: EFM OAM MIB March 2005
1894:
1895:
1896: occurence has happened since the last reset (e.g. 3253, when
1897: 3253 symbol errors have occurred since the last reset, which
1898: has resulted in 51 symbol error threshold crossing events
1899: since the last reset). "
1900: REFERENCE "[802.3ah], 30.3.6.1.37 and 57.5.3.2."
1901: ::= { dot3OamEventLogEntry 11 }
1902:
1903: dot3OamEventLogEventTotal OBJECT-TYPE
1903: change recommended -
warning: node `dot3OamEventLogEventTotal' must be contained in at least one conformance group
1904: SYNTAX Unsigned32
1905: MAX-ACCESS read-only
1906: STATUS current
1907: DESCRIPTION
1908: "This value respresents the total number of times one or ore
1909: of these occurences have resulted in an event (e.g. 51 when
1910: 3253 symbol errors have occurred since the last reset, which
1911: has resulted in 51 symbol error threshold crossing events
1912: since the last reset). "
1913: REFERENCE "[802.3ah], 30.3.6.1.37 and 57.5.3.2."
1914: ::= { dot3OamEventLogEntry 12 }
1915:
1916:
1917: ------------------------------------------------------------------
1918: --
1919: -- Ethernet OAM Notifications
1920: --
1921:
1922: dot3OamNotifs OBJECT IDENTIFIER ::= { dot3OamMIB 7 }
1923: dot3OamNotifsPrefix OBJECT IDENTIFIER ::= {dot3OamNotifs 0}
1924:
1925: dot3OamThresholdEvent NOTIFICATION-TYPE
1925: minor error -
object `dot3OamEventLogWindowHi' of notification `dot3OamThresholdEvent' must be a scalar or column
1926: OBJECTS { ifIndex,
1927: dot3OamEventLogTimestamp,
1928: dot3OamEventLogOui,
1929: dot3OamEventLogType,
1930: dot3OamEventLogLocation,
1931: dot3OamEventLogWindowHi,
1931: severe -
unknown object identifier label `dot3OamEventLogWindowHi'
1932: dot3OamEventLogWindowLo,
1933: dot3OamEventLogThresholdHi,
1934: dot3OamEventLogThresholdLo,
1935: dot3OamEventLogValue,
1936: dot3OamEventLogRunningTotal,
1937: dot3OamEventLogEventTotal
1938: }
1939: STATUS current
1940: DESCRIPTION
1941: "A dot3OamThresholdEvent notification is sent when a local or
1942: remote threshold crossing event is detected. A local
1943: threshold crossing event is detected by the local entity,
1944: while a remote threshold crossing event is detected by the
1945: EFM OAM MIB March 2005
1946:
1947:
1948: reception of an Ethernet OAM Event Notification OAMPDU
1949: indicating a threshold event.
1950:
1951: This notification should not be sent more than once per
1952: second.
1953:
1954: The management entity should periodically check
1955: dot3OamEventLogTable to detect any missed events."
1956: ::= { dot3OamNotifsPrefix 1 }
1957:
1958:
1959: dot3OamNonThresholdEvent NOTIFICATION-TYPE
1960: OBJECTS { ifIndex,
1961: dot3OamEventLogTimestamp,
1962: dot3OamEventLogOui,
1963: dot3OamEventLogType,
1964: dot3OamEventLogLocation,
1965: dot3OamEventLogEventTotal
1966: }
1967: STATUS current
1968: DESCRIPTION
1969: "A dot3OamNonThresholdEvent notification is sent when a local
1970: or remote non-threshold crossing event is detected. A local
1971: event is detected by the local entity, while a remote event is
1972: detected by the reception of an Ethernet OAM Event
1973: Notification OAMPDU indicating a non-threshold crossing event.
1974:
1975: This notification should not be sent more than once per
1976: second.
1977:
1978: The management entity should periodically check
1979: dot3OamEventLogTable to detect any missed events."
1980: ::= { dot3OamNotifsPrefix 2 }
1981:
1982:
1983: ------------------------------------------------------------------
1984: --
1985: -- Ethernet OAM Compliance group
1986: --
1987:
1988:
1989: dot3OamGroups OBJECT IDENTIFIER ::= { dot3OamConformance 1 }
1990: dot3OamCompliances OBJECT IDENTIFIER ::= { dot3OamConformance 2 }
1991:
1992: -- Compliance statements
1993:
1994: dot3OamCompliance MODULE-COMPLIANCE
1995: STATUS current
1996: DESCRIPTION "The compliance statement for managed entities
1997: EFM OAM MIB March 2005
1998:
1999:
2000: supporting OAM on Ethernet like interfaces.
2001: "
2002: MODULE -- this module
2003: MANDATORY-GROUPS { dot3OamControlGroup,
2004: dot3OamPeerGroup,
2005: dot3OamStatsBaseGroup
2006: }
2007:
2008: GROUP dot3OamLoopbackGroup
2009: DESCRIPTION
2010: "This group is mandatory for all IEEE 802.3 OAM
2011: implementations that support loopback functionality. "
2012:
2013: GROUP dot3OamErrSymbolPeriodEventGroup
2014: DESCRIPTION
2015: "This group is mandatory for all IEEE 802.3 OAM
2016: implementations that support event functionality. "
2017:
2018: GROUP dot3OamErrFramePeriodEventGroup
2019: DESCRIPTION
2019: severe -
unknown object identifier label `dot3OamErrFramePeriodEventGroup'
2020: "This group is mandatory for all IEEE 802.3 OAM
2021: implementations that support event functionality. "
2022:
2023: GROUP dot3OamErrFrameEventGroup
2024: DESCRIPTION
2025: "This group is mandatory for all IEEE 802.3 OAM
2026: implementations that support event functionality. "
2027:
2028: GROUP dot3OamErrFrameSecsSummaryEventGroup
2029: DESCRIPTION
2030: "This group is mandatory for all IEEE 802.3 OAM
2031: implementations that support event functionality. "
2032:
2033: GROUP dot3OamFlagEventGroup
2034: DESCRIPTION
2035: "This group is optional for all IEEE 802.3 OAM
2036: implementations. The ability to send critical events or
2037: dying gasp events is not required in any system."
2038:
2039: GROUP dot3OamEventLogGroup
2040: DESCRIPTION
2040: severe -
unknown object identifier label `dot3OamEventLogGroup'
2041: "This group is optional for all IEEE 802.3 OAM
2042: implementations. "
2043:
2044: GROUP dot3OamNotificationGroup
2045: DESCRIPTION
2046: "This group is optional for all IEEE 802.3 OAM
2047: EFM OAM MIB March 2005
2048:
2049:
2050: implementations. "
2051:
2052: ::= { dot3OamCompliances 1}
2053:
2054:
2055: dot3OamControlGroup OBJECT-GROUP
2056: OBJECTS { dot3OamAdminState,
2057: dot3OamOperStatus,
2058: dot3OamMode,
2059: dot3OamMaxOamPduSize,
2060: dot3OamConfigRevision,
2061: dot3OamFunctionsSupported
2062: }
2063: STATUS current
2064: DESCRIPTION
2065: "A collection of objects providing the abilities,
2066: configuration, and status of an Ethernet OAM entity. "
2067: ::= { dot3OamGroups 1 }
2068:
2069: dot3OamPeerGroup OBJECT-GROUP
2070: OBJECTS { dot3OamPeerStatus,
2071: dot3OamPeerMacAddress,
2072: dot3OamPeerVendorOui,
2073: dot3OamPeerVendorInfo,
2074: dot3OamPeerMode,
2075: dot3OamPeerFunctionsSupported,
2076: dot3OamPeerMaxOamPduSize,
2077: dot3OamPeerConfigRevision
2078: }
2079: STATUS current
2080: DESCRIPTION
2081: "A collection of objects providing the abilities,
2082: configuration, and status of a peer Ethernet OAM entity. "
2083: ::= { dot3OamGroups 2 }
2084:
2085: dot3OamStatsBaseGroup OBJECT-GROUP
2086: OBJECTS { dot3OamInformationTx,
2087: dot3OamInformationRx,
2088: dot3OamUniqueEventNotificationTx,
2089: dot3OamUniqueEventNotificationRx,
2090: dot3OamDuplicateEventNotificationTx,
2091: dot3OamDuplicateEventNotificationRx,
2092: dot3OamLoopbackControlTx,
2093: dot3OamLoopbackControlRx,
2094: dot3OamVariableRequestTx,
2095: dot3OamVariableRequestRx,
2096: dot3OamVariableResponseTx,
2097: dot3OamVariableResponseRx,
2098: dot3OamOrgSpecificTx,
2099: EFM OAM MIB March 2005
2099: error -
`EFM' should start with a lower case letter
2099: error -
`OAM' should start with a lower case letter
2099: error -
Object identifier element `OAM' name only allowed as first element
2099: error -
`MIB' should start with a lower case letter
2099: error -
Object identifier element `MIB' name only allowed as first element
2099: error -
`March' should start with a lower case letter
2099: error -
Object identifier element `March' name only allowed as first element
2099: severe -
unknown object identifier label `EFM'
2099: severe -
unknown object identifier label `OAM'
2099: severe -
unknown object identifier label `MIB'
2099: severe -
unknown object identifier label `March'
2099: warning -
warning: implicit node definition
2100:
2101:
2102: dot3OamOrgSpecificRx,
2102: error -
Object identifier element `dot3OamOrgSpecificRx' name only allowed as first element
2103: dot3OamUnsupportedCodesTx,
2104: dot3OamUnsupportedCodesRx,
2105: dot3OamFramesLostDueToOam
2106: }
2107: STATUS current
2108: DESCRIPTION
2109: "A collection of objects providing the statistics for the
2110: number of various transmit and recieve events for OAM on an
2111: Ethernet like interface. Note that all of these counters must
2112: be supported even if the related function (as described in
2113: dot3OamFunctionsSupported) is not supported. "
2114: ::= { dot3OamGroups 3 }
2115:
2116: dot3OamLoopbackGroup OBJECT-GROUP
2117: OBJECTS { dot3OamLoopbackCommand,
2118: dot3OamLoopbackStatus,
2119: dot3OamLoopbackIgnoreRx
2120: }
2121: STATUS current
2122: DESCRIPTION
2123: "A collection of objects for controlling the OAM remote
2124: loopback function. "
2125: ::= { dot3OamGroups 4 }
2126:
2127: dot3OamErrSymbolPeriodEventGroup OBJECT-GROUP
2128: OBJECTS { dot3OamErrSymPeriodWindowHi,
2129: dot3OamErrSymPeriodWindowLo,
2130: dot3OamErrSymPeriodThresholdHi,
2131: dot3OamErrSymPeriodThresholdLo,
2132: dot3OamErrSymPeriodEvNotifEnable
2133: }
2134: STATUS current
2135: DESCRIPTION
2136: "A collection of objects for configuring the thresholds for an
2137: Errored Symbol Period Event.
2138:
2139: Each [802.3ah] defined Event Notification TLV has its own
2140: conformance group because each event can be implemented
2141: independently of any other. "
2142: ::= { dot3OamGroups 5 }
2143:
2144: dot3OamErrFramePeriodEventGroup OBJECT-GROUP
2145: OBJECTS { dot3OamErrFramePeriodWindow,
2146: dot3OamErrFramePeriodThreshold,
2147: dot3OamErrFramePeriodEvNotifEnable
2148: }
2149: STATUS current
2150: DESCRIPTION
2151: EFM OAM MIB March 2005
2151: severe -
syntax error, unexpected UPPERCASE_IDENTIFIER, expecting QUOTED_STRING
2152:
2153:
2154: "A collection of objects for configuring the thresholds for an
2155: Errored Frame Period Event.
2156:
2157: Each [802.3ah] defined Event Notification TLV has its own
2158: conformance group because each event can be implemented
2159: independently of any other. "
2160: ::= { dot3OamGroups 6 }
2160: warning -
warning: flushing recent incorrect declaration, see previous error(s)
2161:
2162: dot3OamErrFrameEventGroup OBJECT-GROUP
2163: OBJECTS { dot3OamErrFrameWindow,
2164: dot3OamErrFrameThreshold,
2165: dot3OamErrFrameEvNotifEnable
2166: }
2167: STATUS current
2168: DESCRIPTION
2169: "A collection of objects for configuring the thresholds for an
2170: Errored Frame Event.
2171:
2172: Each [802.3ah] defined Event Notification TLV has its own
2173: conformance group because each event can be implemented
2174: independently of any other. "
2175: ::= { dot3OamGroups 7 }
2176:
2177: dot3OamErrFrameSecsSummaryEventGroup OBJECT-GROUP
2178: OBJECTS { dot3OamErrFrameSecsSummaryWindow,
2179: dot3OamErrFrameSecsSummaryThreshold,
2180: dot3OamErrFrameSecsEvNotifEnable
2181: }
2182: STATUS current
2183: DESCRIPTION
2184: "A collection of objects for configuring the thresholds for an
2185: Errored Frame Seconds Summary Event.
2186:
2187: Each [802.3ah] defined Event Notification TLV has its own
2188: conformance group because each event can be implemented
2189: independently of any other. "
2190: ::= { dot3OamGroups 8 }
2191:
2192: dot3OamFlagEventGroup OBJECT-GROUP
2193: OBJECTS { dot3OamDyingGaspEnable,
2194: dot3OamCriticalEventEnable
2195: }
2196: STATUS current
2197: DESCRIPTION
2198: "A collection of objects for configuring the sending OAMPDUs
2199: with the critical event flag or dying gasp flag enabled. "
2200: ::= { dot3OamGroups 9 }
2201:
2202: dot3OamEventLogGroup OBJECT-GROUP
2203: EFM OAM MIB March 2005
2203: severe -
syntax error, unexpected UPPERCASE_IDENTIFIER, expecting OBJECTS
2204:
2205:
2206: OBJECTS { dot3OamEventLogTimestamp,
2207: dot3OamEventLogOui,
2208: dot3OamEventLogType,
2209: dot3OamEventLogLocation,
2210: dot3OamEventLogWindowHi,
2211: dot3OamEventLogWindowLo,
2212: dot3OamEventLogThresholdHi,
2213: dot3OamEventLogThresholdLo,
2214: dot3OamEventLogValue,
2215: dot3OamEventLogRunningTotal,
2216: dot3OamEventLogEventTotal
2217: }
2217: warning -
warning: flushing recent incorrect declaration, see previous error(s)
2218: STATUS current
2218: severe -
syntax error, unexpected STATUS
2219: DESCRIPTION
2220: "A collection of objects for configuring the thresholds for an
2221: Errored Frame Seconds Summary Event and maintaining the event
2222: information. "
2223: ::= { dot3OamGroups 10 }
2223: warning -
warning: flushing recent incorrect declaration, see previous error(s)
2224:
2225: dot3OamNotificationGroup NOTIFICATION-GROUP
2226: NOTIFICATIONS {
2227: dot3OamThresholdEvent,
2228: dot3OamNonThresholdEvent
2229: }
2230: STATUS current
2231: DESCRIPTION
2232: "A collection of notifications used by Ethernet OAM to signal
2233: to a management entity that local or remote events have occured
2234: on a specified Ethernet link."
2235: ::= { dot3OamGroups 11 }
2236:
2237:
2238: END
2238: error -
missing MODULE-IDENTITY clause in SMIv2 MIB
2239:
2240: --
2241: -- Copyright (C) The Internet Society (2005). This document is subject
2242: -- to the rights, licenses and restrictions contained in BCP 78, and
2243: -- except as set forth therein, the authors retain all their rights.
2244: --
2245: -- This document and the information contained herein are provided on an
2246: -- "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
2247: -- OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
2248: -- ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
2249: -- INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
2250: -- INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
2251: -- WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
2252: --
2253: --
2254: