draft-ietf-hubmib-efm-mib-03.txt   draft-ietf-hubmib-efm-mib-04.txt 
Ethernet OAM MIB March 2006
Ethernet Interfaces and Hub MIB WG Ethernet Interfaces and Hub MIB WG
Internet Draft Matt Squire Internet Draft Matt Squire
Document: draft-ietf-hubmib-efm-mib-03.txt Hatteras Networks Document: draft-ietf-hubmib-efm-mib-04.txt Hatteras Networks
Expires: September 2005 March, 2005 Expires: September 2006 March, 2006
Ethernet in the First Mile (EFM) OAM MIB Definitions and Managed Objects for OAM Functions on Ethernet Like
Interfaces
draft-ietf-hubmib-efm-mib-04.txt
Status of this Memo Status of this Memo
This document is an Internet-Draft and is subject to all provisions By submitting this Internet-Draft, each author represents that any
of Section 3 of RFC 3667. Bu submitting this Internet-Draft, the applicable patent or other IPR claims of which he or she is aware
author represents that any applicable patent or other IPR claims of have been or will be disclosed, and any of which he or she becomes
which he or she is aware have been or will be disclosed, and any of aware will be disclosed, in accordance with Section 6 of BCP 79.
which he or she become aware will be disclosed, in accordance with
RFC 3668.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet other groups may also distribute working documents as Internet-
Drafts. Drafts.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt http://www.ietf.org/ietf/1id-abstracts.txt
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
This Internet-Draft will expire in September, 2005. This Internet-Draft will expire in September, 2006.
Abstract Abstract
This document defines objects for managing Operations, This document defines objects for managing Operations,
Administration, and Maintenance (OAM) capabilities on Ethernet like Administration, and Maintenance (OAM) capabilities on Ethernet like
interfaces conformant to the Ethernet OAM functionality defined in interfaces conformant to the Ethernet OAM functionality defined in
[802.3ah]. The Ethernet OAM functionality is complementary to SNMP [802.3ah]. The Ethernet OAM functionality is complementary to SNMP
management in that it is focused on a small set of link-specific management in that it is focused on a small set of link-specific
functions for directly connected Ethernet interfaces. This document functions for directly connected Ethernet interfaces. This document
defines objects for controlling those link OAM functions, and on defines objects for controlling those link OAM functions, and for
providing mechanisms to take status and input from Ethernet OAM and providing results and status of the OAM functions to management
feed it into a larger TCP/IP network management system. entities.
EFM OAM MIB March 2005 Ethernet OAM MIB March 2006
Conventions used in this document Conventions used in this document
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119 [RFC2119]. document are to be interpreted as described in RFC 2119 [RFC2119].
Table of Contents Table of Contents
1. Introduction...........................................2 1. Introduction...................................................2
2. The Internet-Standard Management Framework.................2 2. The Internet-Standard Management Framework.....................2
3. Overview..............................................3 3. Overview.......................................................3
3.1 Remote fault indication..............................4 3.1 Remote fault indication....................................4
3.2 Link monitoring.....................................4 3.2 Link monitoring............................................4
3.3 Remote loopback.....................................4 3.3 Remote loopback............................................5
4. Relation to the Other MIBs...............................5 3.4 Ethernet OAM Protocol Data Units...........................5
4.1 Relation to other SNMP MIBs..........................5 4. Relation to the Other MIB Modules..............................5
4.2 Relation to other EFM MIBs...........................5 4.1 Relation to other SNMP MIB Modules.........................5
4.3 IANA Considerations.................................6 4.2 Relation to other EFM MIB Modules..........................5
4.4 Mapping of IEEE 802.3ah Managed Objects................6 4.3 Mapping of IEEE 802.3ah Managed Objects....................6
5. MIB Structure..........................................7 5. MIB Structure..................................................7
6. MIB Definition.........................................8 6. MIB Definition.................................................8
7. Security Considerations.................................51 7. Security Considerations.......................................52
8. References.............................................53 8. IANA Considerations...........................................53
8.1 Normative References................................53 9. References....................................................54
8.2 Informative References...............................54 9.1 Normative References......................................54
9. Acknowledgments........................................54 9.2 Informative References....................................55
10. Author's Address.......................................55 10. Acknowledgments..............................................55
11. Intellectual Property Statement.........................55 11. Author's Address.............................................56
12. Copyright Statement....................................56 12. Intellectual Property Statement..............................56
13. Copyright Statement..........................................57
1. Introduction 1. Introduction
The IEEE 802.3ah Ethernet in the First Mile (EFM) task force added The IEEE 802.3ah Ethernet in the First Mile (EFM) task force added
new management capabilities to Ethernet like interfaces. These new management capabilities to Ethernet like interfaces. These
management capabilities were introduced to provide some basic OAM management capabilities were introduced to provide some basic OAM
function on Ethernet media. The defined functionality includes function on Ethernet media. The defined functionality includes
discovery, error signaling, loopback, and link monitoring. This memo discovery, error signaling, loopback, and link monitoring. This memo
defines a portion of the Management Information Base (MIB) for use defines a portion of the Management Information Base (MIB) for use
with network management protocols in the Internet community to manage with network management protocols in the Internet community to manage
these new EFM interface capabilities. these new Ethernet interface capabilities.
2. The Internet-Standard Management Framework 2. The Internet-Standard Management Framework
Ethernet OAM MIB March 2006
For a detailed overview of the documents that describe the current For a detailed overview of the documents that describe the current
Internet-Standard Management Framework, please refer to section 7 of Internet-Standard Management Framework, please refer to section 7 of
RFC 3410 [RFC3410]. RFC 3410 [RFC3410].
EFM OAM MIB March 2005
Managed objects are accessed via a virtual information store, termed Managed objects are accessed via a virtual information store, termed
the Management Information Base or MIB. MIB objects are generally the Management Information Base or MIB. MIB objects are generally
accessed through the Simple Network Management Protocol (SNMP). accessed through the Simple Network Management Protocol (SNMP).
Objects in the MIB are defined using the mechanisms defined in the Objects in the MIB are defined using the mechanisms defined in the
Structure of Management Information (SMI). This memo specifies a MIB Structure of Management Information (SMI). This memo specifies a MIB
module that is compliant to the SMIv2, which is described in STD 58, module that is compliant to the SMIv2, which is described in STD 58,
RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580
[RFC2580]. [RFC2580].
3. Overview 3. Overview
Ethernet networks have evolved over the past 30 years from simple Ethernet networks have evolved over the past 30 years from simple
LANs to a variety of other applications, including wide area LANs to a variety of other applications, including wide area
networks. To address some of these emerging markets, the IEEE networks. To address some of these emerging markets, the IEEE
802.3ah task force defined additional clauses for the IEEE 802.3 802.3ah task force defined additional clauses in [802.3ah] for the
standard [802.3-2002] to better address Ethernet deployments in the IEEE 802.3 standard [802.3-2002] to better address Ethernet
public access network. deployments in the public access network. Although Ethernet access
deployments were the primary motivation for the task force activity,
the results of the task force are not strictly limited to that
application.
The Ethernet in the First Mile (EFM) task force was focused on four The Ethernet in the First Mile (EFM) task force was focused on four
somewhat independent objectives to better address Ethernet access somewhat independent objectives to better address Ethernet access
deployments: optics, copper, Ethernet passive optical networks deployments: optics, copper, Ethernet passive optical networks
(Ethernet PON, or EPON), and operations, administration, and (Ethernet PON, or EPON), and operations, administration, and
maintenance (OAM). The optics sub-taskforce developed new optical maintenance (OAM). The optics sub-taskforce developed new optical
physical layers that better served the long-reach outside plant physical layers that better served the long-reach outside plant
networks typically found in the access network, including developing networks typically found in the access network, including developing
physical layers that operate up to 20Km and supporting the physical layers that operate up to 20Km and supporting the
environmental conditions of access deployments. The copper sub environmental conditions of access deployments. The copper sub
skipping to change at page 3, line 47 skipping to change at page 3, line 53
point-to-multipoint Ethernet physical layer, utilizing Ethernet point-to-multipoint Ethernet physical layer, utilizing Ethernet
framing natively over a time-division multiple-access (TDMA) framing natively over a time-division multiple-access (TDMA)
infrastructure. The OAM sub-taskforce introduced some basic infrastructure. The OAM sub-taskforce introduced some basic
management functionality into an Ethernet link to better monitor and management functionality into an Ethernet link to better monitor and
maintain Ethernet networks in geographically disparate networks. maintain Ethernet networks in geographically disparate networks.
This document defines the management objects necessary to integrate This document defines the management objects necessary to integrate
Ethernet OAM functionality into the SNMP management framework. Ethernet OAM functionality into the SNMP management framework.
Ethernet OAM is composed of a core set of functions, and a set of Ethernet OAM is composed of a core set of functions, and a set of
optional functional groups that are not required . The mandatory optional functional groups. The mandatory functions include
functions include discovery operations (determining if the other end Ethernet OAM MIB March 2006
of the link is OAM capable, and what OAM functions it supports),
state machine implementation, and some critical event flows. The
optional functional groups are for (a) link events, (b) remote
loopback, and (c) variable retrieval and response. Each optional
functional group is controlled by a separate MIB table(s).
EFM OAM MIB March 2005 discovery operations (determining if the other end of the link is OAM
capable, and what OAM functions it supports), state machine
implementation, and some critical event flows. The optional
functional groups are for (a) link events, (b) remote loopback, and
(c) variable retrieval and response. Each optional functional group
is controlled by a separate MIB table(s).
Ethernet OAM is complementary, not competitive, with SNMP management Ethernet OAM is complementary with SNMP management in that it
in that it provides some basic management functions at layer two, provides some basic management functions at layer two, rather than
rather than using layer three and above as required by SNMP over an using layer three and above as required by SNMP over an IP
IP infrastructure. Ethernet OAM provides single-hop functionality in infrastructure. Ethernet OAM provides single-hop functionality in
that it works only between two directly connected Ethernet stations. that it works only between two directly connected Ethernet stations.
SNMP can be used to manage the Ethernet OAM interactions of one SNMP can be used to manage the Ethernet OAM interactions of one
Ethernet station with another. Ethernet station with another.
Ethernet OAM has three functional objectives which are detailed in Ethernet OAM has three functional objectives which are detailed in
the following sections. the next three sections.
3.1 Remote fault indication 3.1 Remote fault indication
Remote fault indication provides a mechanism for one end of an Remote fault indication provides a mechanism for one end of an
Ethernet link to signal the other end that the receive path is non Ethernet link to signal the other end that the receive path is non
operational. Some Ethernet physical layers offer mechanisms to operational. Some Ethernet physical layers offer mechanisms to
signal this condition at the physical layer. Ethernet OAM added a signal this condition at the physical layer. Ethernet OAM added a
mechanism so that some Ethernet physical layers can operate in mechanism so that some Ethernet physical layers can operate in
unidirectional mode, allowing frames to be transmitted in one unidirectional mode, allowing frames to be transmitted in one
direction even when the other direction is non-operational. direction even when the other direction is non-operational.
skipping to change at page 4, line 40 skipping to change at page 4, line 46
conditions while still not allowing higher layer applications to be conditions while still not allowing higher layer applications to be
aware of the unidirectional capability. This document includes aware of the unidirectional capability. This document includes
mechanisms for capturing that fault information and reflecting such mechanisms for capturing that fault information and reflecting such
information in objects and notifications within the SNMP management information in objects and notifications within the SNMP management
framework. framework.
3.2 Link monitoring 3.2 Link monitoring
Ethernet OAM includes event signaling capability so that one end of Ethernet OAM includes event signaling capability so that one end of
an Ethernet link can indicate the occurrence of certain important an Ethernet link can indicate the occurrence of certain important
events to the other end of the link. This happens via a layer two events to the other end of the link. This happens via layer two
protocol. This document defines methods for incorporating the protocols. This document defines methods for incorporating the
occurrence of these layer two events, both at the local end and far occurrence of these layer two events, both at the local end and far
end of the link, into the SNMP management framework. end of the link, into the SNMP management framework.
Ethernet OAM also includes mechanisms for one Ethernet station to Ethernet OAM also includes mechanisms for one Ethernet station to
query another directly connected Ethernet station about the status of query another directly connected Ethernet station about the status of
its Ethernet interface variables and status. This document does not its Ethernet interface variables and status. This document does not
include mechanisms for controlling how one Ethernet endpoint may use include mechanisms for controlling how one Ethernet endpoint may use
Ethernet OAM MIB March 2006
this functionality to query the status or statistics of a peer this functionality to query the status or statistics of a peer
Ethernet entity. Ethernet entity.
3.3 Remote loopback 3.3 Remote loopback
Remote loopback is a link state where the peer Ethernet entity echoes Remote loopback is a link state where the peer Ethernet entity echoes
every received packet (without modifications) back onto the link. every received packet (without modifications) back onto the link.
EFM OAM MIB March 2005
Remote loopback is intrusive in that the other end of the link is not Remote loopback is intrusive in that the other end of the link is not
forwarding traffic from higher layers out over the link. This forwarding traffic from higher layers out over the link. This
document defines objects controlling loopback operation and reading document defines objects controlling loopback operation and reading
the status of the loopback state. the status of the loopback state.
3.4 Ethernet OAM Protocol Data Units
An Ethernet OAM protocol data unit is a valid Ethernet frame with a
destination MAC address equal to the reserved MAC address for Slow
Protocols (See 43B of [802.3ah], a lengthOrType field equal to the
reserved type for Slow Protocols, and a Slow Protocols subtype equal
to that of the subtype reserved for Ethernet OAM.
OAMPDU is used throughout this document as an abbreviation for
Ethernet OAM protocol data unit. OAMPDUs are the mechanism two
directly connected Ethernet interfaces exchange OAM information.
4. Relation to the Other MIB Modules 4. Relation to the Other MIB Modules
The definitions presented here are based on Clauses 30 and 57 of The definitions presented here are based on Clauses 30 and 57 of
[802.3ah]. Note that these clauses describe many of these variables [802.3ah]. Note that these clauses describe many of these variables
and their effects on the MAC layer. In some cases there is a one-to and their effects on the MAC layer. In some cases there is a one-to
one relationship between an object in this document and an object in one relationship between an object in this document and an object in
the Clause 30 MIB of [802.3ah]. In other cases, the objects of this the Clause 30 MIB of [802.3ah]. In other cases, the objects of this
document reflect a more complex entity and are reflected by more than document reflect a more complex entity and are reflected by more than
one object in the Clause 30 MIB of [802.3ah]. one object in the Clause 30 MIB of [802.3ah].
4.1 Relation to other SNMP MIB Modules 4.1 Relation to other SNMP MIB Modules
This objects defined in this document do not overlap with MIB-2 The objects defined in this document manage OAM functionality
[RFC1213], the interfaces MIB [RFC2863], or the Ethernet like introduced in [802.3ah] These objects do not overlap with the
interfaces MIB [RFC3635]. The objects defined here are defined for interfaces MIB [RFC2863], the Ethernet like interfaces MIB [RFC3635],
or any other MIB currently used to manage various aspects of an
Ethernet interface. The objects defined here are defined for
Ethernet like interfaces only and use the same ifIndex as the Ethernet like interfaces only and use the same ifIndex as the
associated Ethernet interface. Ethernet OAM can be implemented on associated Ethernet interface. Ethernet OAM can be implemented on
any Ethernet like interface managed via these MIBs. any Ethernet like interface.
4.2 Relation to other EFM MIB Modules 4.2 Relation to other EFM MIB Modules
Ethernet OAM MIB March 2006
The Ethernet OAM functionality and MIB Module is independent of the The Ethernet OAM functionality and MIB Module is independent of the
other functionality and MIB Modules derived from [802.3ah] for copper other functionality and MIB Modules derived from [802.3ah] for copper
[802.3ah-copper] and EPON [802.3ah-epon]. [802.3ah-copper] and EPON [802.3ah-epon]. Ethernet OAM may be
implemented (or not) on the new EFM interface types, just as it can
Ethernet OAM may be implemented on point-to-multipoint EFM EPON on any other Ethernet interface.
interfaces. However, because higher layer protocols that run over
Ethernet interfaces are not designed for the partial connectivity
provided by a point-to-multipoint interface, EPON provides a point
to-point emulation layer (see [802.3ah] and [802.3ah-epon]) whereby
the single EPON interface of 1-to-N connectivity is represented by N
point-to-point interfaces. Ethernet OAM, like any other protocol at
the Ethernet layer or above (for example, bridging), utilizes the
point-to-point emulation layer of EPON in that the EPON interface is
viewed as N point-to-point Ethernet interfaces. Thus OAM, and other
protocols, do not need to be altered for the EPON environment.
Ethernet OAM may be implemented on the 2BASE-TL and 10PASS-TS
Ethernet-over-copper interfaces defined in EFM [802.3ah]. 2BASE-TL
and 10PASS-TS can be aggregated interfaces, meaning that they can use
the ifStackTable of the Interfaces Group MIB [RFC2863] to manage a
set of N (1 <= N <= 32) physical layers into a single Ethernet
interface.
EFM OAM MIB March 2005
The other Ethernet interfaces introduced in EFM [802.3ah] are simply
new optical physical layers that are managed by minimal extensions to
the MAU MIB [RFC3636] defining new types of Ethernet interfaces.
4.3 IANA Considerations
The EFM OAM MIB requires the allocation of a single object identifier 4.3 Mapping of IEEE 802.3ah Managed Objects
for its MODULE-IDENTITY under the MIB-2 tree. IANA has not yet
allocated this object identifier.
This section contains the mapping between managed objects defined in
[802.3ah] Clause 30, and managed objects defined in this document. [802.3ah] Clause 30, and managed objects defined in this document.
IEEE 802.3 Managed Object Corresponding SNMP object IEEE 802.3 Managed Object Corresponding SNMP object
oOAM
.aOAMID IF-MIB ifIndex .aOAMID IF-MIB ifIndex
.aOAMAdminState dot3OamAdminState .aOAMAdminState dot3OamAdminState
.aOAMMode dot3OamMode .aOAMMode dot3OamMode
.aOAMDiscoveryState dot3OamOperStatus .aOAMDiscoveryState dot3OamOperStatus
.aOAMRemoteMACAddress dot3OamPeerMacAddress .aOAMRemoteMACAddress dot3OamPeerMacAddress
.aOAMLocalConfiguration dot3OamFunctionsSupported .aOAMLocalConfiguration dot3OamFunctionsSupported
.aOAMRemoteConfiguration dot3OamPeerFunctionsSupported, .aOAMRemoteConfiguration dot3OamPeerFunctionsSupported,
dot3OamPeerMode dot3OamPeerMode
.aOAMLocalPDUConfiguration dot3OamMaxOamPduSize .aOAMLocalPDUConfiguration dot3OamMaxOamPduSize
.aOAMRemotePDUConfiguration dot3OamPeerMaxOamPduSize .aOAMRemotePDUConfiguration dot3OamPeerMaxOamPduSize
.aOAMLocalFlagsField dot3OamOperStatus, .aOAMLocalFlagsField dot3OamOperStatus,
dot3OamEventLogEntry
.aOAMRemoteFlagsField dot3OamOperStatus, .aOAMRemoteFlagsField dot3OamOperStatus,
dot3OamEventLogEntry
.aOAMLocalRevision dot3OamConfigRevision .aOAMLocalRevision dot3OamConfigRevision
.aOAMRemoteRevision dot3OamPeerConfigRevision .aOAMRemoteRevision dot3OamPeerConfigRevision
.aOAMLocalState dot3OamLoopbackStatus .aOAMLocalState dot3OamLoopbackStatus
.aOAMRemoteState dot3OamLoopbackStatus .aOAMRemoteState dot3OamLoopbackStatus
.aOAMRemoteVendorOUI dot3OamPeerVendorOui .aOAMRemoteVendorOUI dot3OamPeerVendorOui
.aOAMRemoteVendorSpecificInfo dot3OamPeerVendorInfo .aOAMRemoteVendorSpecificInfo dot3OamPeerVendorInfo
.aOAMUnsupportedCodesTx dot3OamUnsupportedCodesTx .aOAMUnsupportedCodesTx dot3OamUnsupportedCodesTx
.aOAMUnsupportedCodesRx dot3OamUnsupportedCodesRx .aOAMUnsupportedCodesRx dot3OamUnsupportedCodesRx
.aOAMInformationTx dot3OamInformationTx .aOAMInformationTx dot3OamInformationTx
.aOAMInformationRx dot3OamInformationRx .aOAMInformationRx dot3OamInformationRx
.aOAMUniqueEventNotificationTx dot3OamUniqueEventNotificationTx .aOAMUniqueEventNotificationTx dot3OamUniqueEventNotificationTx
.aOAMUniqueEventNotificationRx dot3OamUniqueEventNotificationRx .aOAMUniqueEventNotificationRx dot3OamUniqueEventNotificationRx
.aOAMDuplicateEventNotificationTx .aOAMDuplicateEventNotificationTx
dot3OamDuplicateEventNotificationTx dot3OamDuplicateEventNotificationTx
.aOAMDuplicateEventNotificationRx .aOAMDuplicateEventNotificationRx
dot3OamDuplicateEventNotificationRx dot3OamDuplicateEventNotificationRx
skipping to change at page 7, line 4 skipping to change at page 6, line 51
.aOAMUnsupportedCodesRx dot3OamUnsupportedCodesRx .aOAMUnsupportedCodesRx dot3OamUnsupportedCodesRx
.aOAMInformationTx dot3OamInformationTx .aOAMInformationTx dot3OamInformationTx
.aOAMInformationRx dot3OamInformationRx .aOAMInformationRx dot3OamInformationRx
.aOAMUniqueEventNotificationTx dot3OamUniqueEventNotificationTx .aOAMUniqueEventNotificationTx dot3OamUniqueEventNotificationTx
.aOAMUniqueEventNotificationRx dot3OamUniqueEventNotificationRx .aOAMUniqueEventNotificationRx dot3OamUniqueEventNotificationRx
.aOAMDuplicateEventNotificationTx .aOAMDuplicateEventNotificationTx
dot3OamDuplicateEventNotificationTx dot3OamDuplicateEventNotificationTx
.aOAMDuplicateEventNotificationRx .aOAMDuplicateEventNotificationRx
dot3OamDuplicateEventNotificationRx dot3OamDuplicateEventNotificationRx
.aOAMLoopbackControlTx dot3OamLoopbackControlTx .aOAMLoopbackControlTx dot3OamLoopbackControlTx
EFM OAM MIB March 2005
.aOAMLoopbackControlRx dot3OamLoopbackControlRx .aOAMLoopbackControlRx dot3OamLoopbackControlRx
.aOAMVariableRequestTx dot3OamVariableRequestTx .aOAMVariableRequestTx dot3OamVariableRequestTx
.aOAMVariableRequestRx dot3OamVariableRequestRx .aOAMVariableRequestRx dot3OamVariableRequestRx
.aOAMVariableResponseTx dot3OamVariableResponseTx .aOAMVariableResponseTx dot3OamVariableResponseTx
Ethernet OAM MIB March 2006
.aOAMVariableResponseRx dot3OamVariableResponseRx .aOAMVariableResponseRx dot3OamVariableResponseRx
.aOAMOrganizationSpecificTx dot3OamOrgSpecificTx .aOAMOrganizationSpecificTx dot3OamOrgSpecificTx
.aOAMOrganizationSpecificRx dot3OamOrgSpecificTx .aOAMOrganizationSpecificRx dot3OamOrgSpecificTx
.aOAMLocalErrSymPeriodConfig dot3OamErrSymPeriodWindow, .aOAMLocalErrSymPeriodConfig dot3OamErrSymPeriodWindow,
dot3OamErrSymPeriodThreshold, dot3OamErrSymPeriodThreshold
dot3OamErrSymPeriodEvNotifEnable
.aOAMLocalErrSymPeriodEvent dot3OamEventLogEntry .aOAMLocalErrSymPeriodEvent dot3OamEventLogEntry
.aOAMLocalErrFrameConfig dot3OamErrFrameWindow, .aOAMLocalErrFrameConfig dot3OamErrFrameWindow,
dot3OamErrFrameThreshold, dot3OamErrFrameThreshold
dot3OamErrFrameEvNotifEnable
.aOAMLocalErrFrameEvent dot3OamEventLogEntry .aOAMLocalErrFrameEvent dot3OamEventLogEntry
.aOAMLocalErrFramePeriodConfig dot3OamErrFramePeriodWindow, .aOAMLocalErrFramePeriodConfig dot3OamErrFramePeriodWindow,
dot3OamErrFramePeriodThreshold, dot3OamErrFramePeriodThreshold
dot3OamErrFramePeriodEvNotifEnable
.aOAMLocalErrFramePeriodEvent dot3OamEventLogEntry .aOAMLocalErrFramePeriodEvent dot3OamEventLogEntry
.aOAMLocalErrFrameSecsSummaryConfig .aOAMLocalErrFrameSecsSummaryConfig
dot3OamErrFrameSecsSummaryWindow, dot3OamErrFrameSecsSummaryWindow,
dot3OamErrFrameSecsSummaryThreshold, dot3OamErrFrameSecssummaryThreshold
dot3OamErrFrameSecsSummaryEvNotifEnable
.aOAMLocalErrFrameSecsSummaryEvent .aOAMLocalErrFrameSecsSummaryEvent
dot3OamEventLogEntry dot3OamEventLogEntry
.aOAMRemoteErrSymPeriodEvent dot3OamEventLogEntry .aOAMRemoteErrSymPeriodEvent dot3OamEventLogEntry
.aOAMRemoteErrFrameEvent dot3OamEventLogEntry .aOAMRemoteErrFrameEvent dot3OamEventLogEntry
.aOAMRemoteErrFramePeriodEvent dot3OamEventLogEntry .aOAMRemoteErrFramePeriodEvent dot3OamEventLogEntry
.aOAMRemoteErrFrameSecsSummaryEvent .aOAMRemoteErrFrameSecsSummaryEvent
dot3OamEventLogEntry dot3OamEventLogEntry
.aFramesLostDueToOAmError .aFramesLostDueToOAmError dot3OamFramesLostDueToOam
.acOAmAdminControl dot3OamFramesLostDueToOam .acOAMAdminControl dot3OamAdminState
There are no IEEE 802.3ah managed objects that are not reflected in There are no IEEE 802.3ah managed objects that are not reflected in
this MIB Module in some manner. this MIB Module in some manner.
5. MIB Structure 5. MIB Structure
The common EFM MIB objects of this memo focus on the OAM capabilities The Ethernet OAM MIB objects of this memo focus on the OAM
introduced in IEEE 802.3ah. The MIB objects are partitioned into six capabilities introduced in [802.3ah]. The MIB objects are
different MIB groups. partitioned into six different MIB groups.
The dot3OamTable group manages the primary OAM objects of the The dot3OamTable group manages the primary OAM objects of the
Ethernet interface. This group controls the state and status of OAM Ethernet interface. This group controls the state and status of OAM
as well as the mode in which it operates. as well as the mode in which it operates.
The dot3OamPeerTable maintains the current information on the status The dot3OamPeerTable maintains the current information on the status
and configuration of the peer OAM entity on the Ethernet interface. and configuration of the peer OAM entity on the Ethernet interface.
Managed information includes the capabilities and function available Managed information includes the capabilities and function available
on the peer OAM entity. on the peer OAM entity.
EFM OAM MIB March 2005
The dot3OamLoopbackTable manages the loopback function introduced in The dot3OamLoopbackTable manages the loopback function introduced in
EFM [802.3ah]. This table controls enabling and disabling loopback, [802.3ah]. This table controls enabling and disabling loopback, as
as well as indicating the loopback status of Ethernet OAM on this well as indicating the loopback status of Ethernet OAM on this
interface. interface.
Ethernet OAM MIB March 2006
The dot3OamStatsTable maintains statistics on the number and type of The dot3OamStatsTable maintains statistics on the number and type of
Ethernet OAM frames being transmitted and received on the Ethernet Ethernet OAM frames being transmitted and received on the Ethernet
interface. interface.
The dot3OamEventConfigTable defines the objects for managing the The dot3OamEventConfigTable defines the objects for managing the
event notification capability available in Ethernet OAM. With EFM event notification capability available in Ethernet OAM. With
OAM, one device may send notifications to its peer devices whenever Ethernet OAM, one device may send notifications to its peer devices
an important event happens on the local device. This table provides whenever an important event happens on the local device. This table
management of which events result in notifications via EFM OAM provides management of which events result in notifications via
notifications and via SNMP notifications. Ethernet OAM notifications and/or via SNMP notifications.
The dot3OamEventLogTable manages the current status of local and The dot3OamEventLogTable manages the current status of local and
remote events detected via Ethernet OAM. This table is updated remote events detected via Ethernet OAM. This table is updated
whenever local events are detected by Ethernet OAM or whenever EFM whenever local events are detected by Ethernet OAM or whenever
OAM Event Notifications are received from the peer OAM entity. Ethernet OAM Event Notifications are received from the peer OAM
entity.
There are also a set of notifications (dot3OamNotifications) that
define alert conditions to management. The [802.3ah] Event
Notifications can each be implemented independently of any other, and
therefore each has their own conformance group.
6. MIB Definition 6. MIB Definition
EFM-COMMON-MIB DEFINITIONS ::= BEGIN DOT3-OAM-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
MODULE-IDENTITY, mib-2, OBJECT-TYPE, Counter32, Unsigned32, MODULE-IDENTITY, mib-2, OBJECT-TYPE, Counter32, Unsigned32,
Integer32, NOTIFICATION-TYPE Integer32, NOTIFICATION-TYPE
FROM SNMPv2-SMI FROM SNMPv2-SMI
TEXTUAL-CONVENTION, MacAddress, TimeStamp TEXTUAL-CONVENTION, MacAddress, TimeStamp, TruthValue
FROM SNMPv2-TC FROM SNMPv2-TC
CounterBasedGauge64 CounterBasedGauge64
FROM HCNUM-TC FROM HCNUM-TC
ifIndex ifIndex
FROM IF-MIB FROM IF-MIB
MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP
FROM SNMPv2-CONF; FROM SNMPv2-CONF;
efmOamMIB MODULE-IDENTITY dot3OamMIB MODULE-IDENTITY
LAST-UPDATED "200503220000Z" -- March 22, 2005" LAST-UPDATED "200603050000Z" -- March 5,2006"
ORGANIZATION ORGANIZATION
"IETF Ethernet Interfaces and Hub MIB Working Group" "IETF Ethernet Interfaces and Hub MIB Working Group"
CONTACT-INFO CONTACT-INFO
"WG Charter: "WG Charter:
http://www.ietf.org/html.charters/hubmib-charter.html http://www.ietf.org/html.charters/hubmib-charter.html
Mailing lists: Ethernet OAM MIB March 2006
EFM OAM MIB March 2005
Mailing lists:
General Discussion: hubmib@ietf.org General Discussion: hubmib@ietf.org
To Subscribe: hubmib-requests@ietf.org To Subscribe: hubmib-requests@ietf.org
In Body: subscribe your_email_address In Body: subscribe your_email_address
Chair: Dan Romascanu, Avaya Chair: Dan Romascanu, Avaya
Tel: +972-3-645-8414 Tel: +972-3-645-8414
Email: dromasca at avaya dot com Email: dromasca at avaya dot com
Editor: Matt Squire Editor: Matt Squire
Hatteras Networks Hatteras Networks
Tel: +1-919-991-5460 Tel: +1-919-991-5460
Fax: +1-919-991-0743 Fax: +1-919-991-0743
E-mail: msquire at hatterasnetworks dot com E-mail: msquire at hatterasnetworks dot com
" "
DESCRIPTION DESCRIPTION
"The MIB module for managing the new Ethernet OAM features "The MIB module for managing the new Ethernet OAM features
introduced by the Ethernet in the First Mile task force (IEEE introduced by the Ethernet in the First Mile task force (IEEE
802.3ah). The functionality presented here is based on IEEE 802.3ah). The functionality presented here is based on IEEE
802.3ah [802.3ah], released in October, 2004. 802.3ah [802.3ah], released in October, 2004. [802.3ah] was
prepared as an addendum to the standing version of IEEE 802.3
[802.3-2002] at the time. Since then, [802.3ah] has been
merged into the base IEEE 802.3 specification in [802.3-2005].
In particular, this MIB focused on the changes to Clause 30 of In particular, this MIB focuses on the new OAM functions
the draft that are not specific to any physical layer. These introduced in Clause 57 of [802.3ah]. The OAM functionality
changes are primarily reflected in the new OAM features of Clause 57 is controlled by new management attributes
developed under this project, that can be applied to any introduced in Clause 30 of [802.3ah]. The OAM functions are
Ethernet like interface. The OAM features are described in not specific to any particular Ethernet physical layer, and
Clause 57 of [802.3ah]. can be generically applied to any Ethernet interface of
[802.3-2002].
An Ethernet OAM protocol data unit is a valid Ethernet frame
with a destination MAC address equal to the reserved MAC
address for Slow Protocols (See 43B of [802.3ah]), a
lengthOrType field equal to the reserved type for Slow
Protocols, and a Slow Protocols subtype equal to that of the
subtype reserved for Ethernet OAM. OAMPDU is used throughout
this document as an abbreviation for Ethernet OAM protocol
data unit.
The following reference is used throughout this MIB module: The following reference is used throughout this MIB module:
[802.3ah] refers to: [802.3ah] refers to:
IEEE Std 802.3ah-2004: 'Draft amendment to - IEEE Std 802.3ah-2004: 'Draft amendment to -
Information technology - Telecommunications and Information technology - Telecommunications and
information exchange between systems - Local and information exchange between systems - Local and
metropolitan are networks - Specific requirements - Part metropolitan are networks - Specific requirements - Part
3: Carrier sense multiple access with collision detection 3: Carrier sense multiple access with collision detection
(CSMA/CD) access method and physical layer specifications (CSMA/CD) access method and physical layer specifications
- Media Access Control Parameters, Physical Layers and - Media Access Control Parameters, Physical Layers and
Ethernet OAM MIB March 2006
Management Parameters for subscriber access networks', Management Parameters for subscriber access networks',
October 2004. October 2004.
[802.3-2002] refers to:
IEEE Std 802.3-2002:
'Information technology - Telecommunications and
information exchange between systems - Local and
metropolitan are networks - Specific requirements - Part
3: Carrier sense multiple access with collision detection
(CSMA/CD) access method and physical layer specifications
- Media Access Control Parameters, Physical Layers and
Management Parameters for subscriber access networks',
March 2002.
[802.3-2005] refers to:
IEEE Std 802.3-2002:
'Information technology - Telecommunications and
information exchange between systems - Local and
metropolitan are networks - Specific requirements - Part
3: Carrier sense multiple access with collision detection
(CSMA/CD) access method and physical layer specifications
- Media Access Control Parameters, Physical Layers and
Management Parameters for subscriber access networks',
December 2005.
[802-2001] refers to: [802-2001] refers to:
'IEEE Standard for LAN/MAN (Local Area 'IEEE Standard for LAN/MAN (Local Area
Network/Metropolitan Area Network): Overview and Network/Metropolitan Area Network): Overview and
Architecture', IEEE 802, June 2001. Architecture', IEEE 802, June 2001.
Copyright (c) The Internet Society (2005). This version of Copyright (c) The Internet Society (2006). This version of
this MIB module is part of RFC XXXX; See the RFC itself for this MIB module is part of RFC XXXX; See the RFC itself for
full legal notices. " full legal notices. "
-- RFC Editor: Update XXXX to appropriate RFC number -- RFC Editor: Update XXXX to appropriate RFC number
-- RFC Editor: Remove these notes -- RFC Editor: Remove these notes
EFM OAM MIB March 2005
REVISION "200503220000Z" -- March 22, 2005" REVISION "200603050000Z" -- March 5, 2006"
DESCRIPTION "Initial version, published as RFC XXXX." DESCRIPTION "Initial version, published as RFC XXXX."
-- RFC Editor: Update XXXX to appropriate RFC number -- RFC Editor: Update XXXX to appropriate RFC number
-- RFC Editor: Remove these notes -- RFC Editor: Remove these notes
::= { mib-2 XXX } ::= { mib-2 XXX }
-- RFC Editor: Replace value with IANA assigned number -- RFC Editor: Replace value with IANA assigned number
-- RFC Editor: Remove these notes -- RFC Editor: Remove these notes
-- --
-- Sections of the EFM OAM MIB -- Sections of the Ethernet OAM MIB
Ethernet OAM MIB March 2006
-- --
dot3OamMIB OBJECT IDENTIFIER ::= { efmOamMIB 1 } dot3OamNotifications OBJECT IDENTIFIER ::= { dot3OamMIB 0 }
dot3OamConformance OBJECT IDENTIFIER ::= { efmOamMIB 2 } dot3OamObjects OBJECT IDENTIFIER ::= { dot3OamMIB 1 }
dot3OamConformance OBJECT IDENTIFIER ::= { dot3OamMIB 2 }
-- --
-- Textual conventions for OAM MIB -- Textual conventions for OAM MIB
-- --
Dot3Oui ::= TEXTUAL-CONVENTION Dot3Oui ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"24-bit Organizationally Unique Identifier. Information on "24-bit Organizationally Unique Identifier. Information on
OUIs can be found in IEEE 802-2001 [802-2001] Clause 9." OUIs can be found in IEEE 802-2001 [802-2001] Clause 9."
SYNTAX OCTET STRING(SIZE(3)) SYNTAX OCTET STRING(SIZE(3))
------------------------------------------------------------------ -- ***************************************************************
-- --
-- Ethernet OAM Control group -- Ethernet OAM Control group
-- --
dot3OamTable OBJECT-TYPE dot3OamTable OBJECT-TYPE
SYNTAX SEQUENCE OF Dot3OamEntry SYNTAX SEQUENCE OF Dot3OamEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Primary controls and status for the OAM capabilities of an "This table contains the primary controls and status for the
Ethernet like interface. There will be one row in this table OAM capabilities of an Ethernet like interface. There will be
for each Ethernet like interface in the system that supports one row in this table for each Ethernet like interface in the
the Ethernet OAM functions defined in [802.3ah]." system that supports the OAM functions defined in [802.3ah].
::= { dot3OamMIB 1 } "
::= { dot3OamObjects 1 }
dot3OamEntry OBJECT-TYPE dot3OamEntry OBJECT-TYPE
SYNTAX Dot3OamEntry SYNTAX Dot3OamEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
EFM OAM MIB March 2005
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry in the table, containing information on the Ethernet "An entry in the table, containing information on the Ethernet
OAM function for a single Ethernet like interface." OAM function for a single Ethernet like interface. Entries in
the table are created automatically for each interface
supporting Ethernet OAM. The status of the row entry can be
determined from dot3OamOperStatus.
A dot3OamEntry is indexed in the dot3OamTable by the ifIndex
object of the Interfaces MIB.
"
INDEX { ifIndex } INDEX { ifIndex }
Ethernet OAM MIB March 2006
::= { dot3OamTable 1 } ::= { dot3OamTable 1 }
Dot3OamEntry ::= Dot3OamEntry ::=
SEQUENCE { SEQUENCE {
dot3OamAdminState INTEGER, dot3OamAdminState INTEGER,
dot3OamOperStatus INTEGER, dot3OamOperStatus INTEGER,
dot3OamMode INTEGER, dot3OamMode INTEGER,
dot3OamMaxOamPduSize Integer32, dot3OamMaxOamPduSize Unsigned32,
dot3OamConfigRevision Unsigned32, dot3OamConfigRevision Unsigned32,
dot3OamFunctionsSupported BITS dot3OamFunctionsSupported BITS
} }
dot3OamAdminState OBJECT-TYPE dot3OamAdminState OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
disabled(1), disabled(1),
enabled(2) enabled(2)
} }
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object is used to provision the default administrative "This object is used to provision the default administrative
OAM mode for this interface. This object represents the OAM mode for this interface. This object represents the
desired state of OAM for this interface. desired state of OAM for this interface.
The dot3OamAdminState always starts in the disabled(1) state The dot3OamAdminState always starts in the disabled(1) state
until an explicity management action or configuration until an explicit management action or configuration
information retained by the system causes a transition to the information retained by the system causes a transition to the
enabled(2) state. enabled(2) state. When enabled(2), Ethernet OAM will attempt
to operate over this interface.
Note that the value of this object is ignored when the "
interface is not operating in full-duplex mode. OAM is not
supported on half-duplex links. "
REFERENCE "[802.3ah], 30.3.6.1.2" REFERENCE "[802.3ah], 30.3.6.1.2"
::= { dot3OamEntry 1 } ::= { dot3OamEntry 1 }
dot3OamOperStatus OBJECT-TYPE dot3OamOperStatus OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
disabled(1), disabled(1),
linkfault(2), linkFault(2),
passiveWait(3), passiveWait(3),
activeSendLocal(4), activeSendLocal(4),
sendLocalAndRemote(5), sendLocalAndRemote(5),
sendLocalAndRemoteOk(6), sendLocalAndRemoteOk(6),
EFM OAM MIB March 2005
oamPeeringLocallyRejected(7), oamPeeringLocallyRejected(7),
oamPeeringRemotelyRejected(8), oamPeeringRemotelyRejected(8),
operational(9) operational(9),
nonOperHalfDuplex(10)
} }
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
Ethernet OAM MIB March 2006
DESCRIPTION DESCRIPTION
"At initialization and failure conditions, two OAM entities on "At initialization and failure conditions, two OAM entities on
the same full-duplex Ethernet link begin a discovery phase to the same full-duplex Ethernet link begin a discovery phase to
determine what OAM capabilities may be used on that link. The determine what OAM capabilities may be used on that link. The
progress of this initialization is controlled by the OAM progress of this initialization is controlled by the OAM
sublayer. sublayer.
This value is always disabled(1) if OAM is disabled on this This value is always disabled(1) if OAM is disabled on this
interface via the dot3OamAdminState. interface via the dot3OamAdminState.
If the link has detected a fault and is transmitting OAMPDUs If the link has detected a fault and is transmitting OAMPDUs
with a link fault indication, the value is linkFault(2). with a link fault indication, the value is linkFault(2). Also,
if the interface is not operational (ifOperStatus is not
up(1)), linkFault(2) is returned. Note that the object
ifOperStatus may not be up(1) as a result of link failure or
administrative action (ifAdminState being down(2) or
testing(3)).
The passiveWait(3) state is returned only by OAM entities in The passiveWait(3) state is returned only by OAM entities in
passive mode (dot3OamMode) and reflects the state in which the passive mode (dot3OamMode) and reflects the state in which the
OAM entity is waiting to see if the peer device is OAM OAM entity is waiting to see if the peer device is OAM
capable. The activeSendLocal(4) is used by active mode capable. The activeSendLocal(4) value is used by active mode
devices (dot3OamMode) and reflects the OAM entity actively devices (dot3OamMode) and reflects the OAM entity actively
trying to discover whether the peer has OAM capability but has trying to discover whether the peer has OAM capability but has
not yet made that determination. not yet made that determination.
The state sendLocalAndRemote(5) reflects that the local OAM The state sendLocalAndRemote(5) reflects that the local OAM
entity has discovered the peer but has not yet accepted or entity has discovered the peer but has not yet accepted or
rejected the configuration of the peer. The local device can, rejected the configuration of the peer. The local device can,
for whatever reason, decide that the peer device is for whatever reason, decide that the peer device is
unacceptable and decline OAM peering. If the local OAM entity unacceptable and decline OAM peering. If the local OAM entity
rejects the peer OAM entity, the state becomes rejects the peer OAM entity, the state becomes
skipping to change at page 13, line 4 skipping to change at page 13, line 54
whether the local OAM client has actively rejected the peering whether the local OAM client has actively rejected the peering
or has just not indicated any decision yet. Whether a peering or has just not indicated any decision yet. Whether a peering
decision has been made is indicated via the local flags field decision has been made is indicated via the local flags field
in the OAMPDU (reflected in the aOAMLocalFlagsField of in the OAMPDU (reflected in the aOAMLocalFlagsField of
30.3.6.1.10). 30.3.6.1.10).
If the remote OAM entity rejects the peering, the state If the remote OAM entity rejects the peering, the state
becomes oamPeeringRemotelyRejected(8). Note that both the becomes oamPeeringRemotelyRejected(8). Note that both the
sendLocalAndRemoteOk(6) and oamPeeringRemotelyRejected(8) sendLocalAndRemoteOk(6) and oamPeeringRemotelyRejected(8)
states fall within the state SEND_LOCAL_REMOTE_OK of the states fall within the state SEND_LOCAL_REMOTE_OK of the
EFM OAM MIB March 2005
Discovery state diagram [802.3ah, Figure 57-5], with the Discovery state diagram [802.3ah, Figure 57-5], with the
Ethernet OAM MIB March 2006
difference being whether the remote OAM client has rejected difference being whether the remote OAM client has rejected
the peering or has just not yet decided. This is indicated the peering or has just not yet decided. This is indicated
via the remote flags field in the OAM PDU (reflected in the via the remote flags field in the OAM PDU (reflected in the
aOAMRemoteFlagsField of 30.3.6.1.11). aOAMRemoteFlagsField of 30.3.6.1.11).
When the local OAM entity learns that both it and the remote When the local OAM entity learns that both it and the remote
OAM entity have accepted the peering, the state moves to OAM entity have accepted the peering, the state moves to
operational(9) corresponding to the SEND_ANY state of the operational(9) corresponding to the SEND_ANY state of the
Discovery state diagram [802.3ah, Figure 57-5]. " Discovery state diagram [802.3ah, Figure 57-5].
Since Ethernet OAM functions are not designed to work
completely over half-duplex interfaces, the value
nonOperHalfDuplex(10) is returned whenever Ethernet OAM is
enabled (dot3OamAdminState is enabled(1)) but the interface is
in half-duplex operation.
"
REFERENCE "[802.3ah], 30.3.6.1.4, 30.3.6.1.10, 30.3.6.1.11" REFERENCE "[802.3ah], 30.3.6.1.4, 30.3.6.1.10, 30.3.6.1.11"
::= { dot3OamEntry 2 } ::= { dot3OamEntry 2 }
dot3OamMode OBJECT-TYPE dot3OamMode OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
active(1), active(1),
passive(2) passive(2)
} }
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
skipping to change at page 13, line 46 skipping to change at page 14, line 52
The default value of dot3OamMode is dependent on the type of The default value of dot3OamMode is dependent on the type of
system on which this Ethernet like interface resides. The system on which this Ethernet like interface resides. The
default value should be 'active(1)' unless it is known that default value should be 'active(1)' unless it is known that
this system should take on a subservient role to the other this system should take on a subservient role to the other
device connected over this interface. device connected over this interface.
Changing this value results in incrementing the configuration Changing this value results in incrementing the configuration
revision field of locally generated OAMPDUs (30.3.6.1.12) and revision field of locally generated OAMPDUs (30.3.6.1.12) and
potentially re-doing the OAM discovery process if the potentially re-doing the OAM discovery process if the
dot3OamOperStatus was already operational(9). " dot3OamOperStatus was already operational(9).
"
REFERENCE "[802.3ah], 30.3.6.1.3" REFERENCE "[802.3ah], 30.3.6.1.3"
Ethernet OAM MIB March 2006
::= { dot3OamEntry 3 } ::= { dot3OamEntry 3 }
dot3OamMaxOamPduSize OBJECT-TYPE dot3OamMaxOamPduSize OBJECT-TYPE
SYNTAX Integer32 (64..1522) SYNTAX Unsigned32 (64..1518)
UNITS "bytes" UNITS "octets"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
EFM OAM MIB March 2005
DESCRIPTION DESCRIPTION
"The largest OAMPDU that the OAM entity supports. OAM "The largest OAMPDU that the OAM entity supports. OAM
entities exchange maximum OAMPDU sizes and negotiate to use entities exchange maximum OAMPDU sizes and negotiate to use
the smaller of the two maximum OAMPDU sizes between the peers. the smaller of the two maximum OAMPDU sizes between the peers.
This value is determined by the local implementation. This value is determined by the local implementation.
" "
REFERENCE "[802.3ah], 30.3.6.1.8" REFERENCE "[802.3ah], 30.3.6.1.8"
::= { dot3OamEntry 4 } ::= { dot3OamEntry 4 }
dot3OamConfigRevision OBJECT-TYPE dot3OamConfigRevision OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32(0..65535)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The configuration revision of the OAM entity as reflected in "The configuration revision of the OAM entity as reflected in
the latest OAMPDU sent by the OAM entity. The config revision the latest OAMPDU sent by the OAM entity. The config revision
is used by OAM entities to indicate configuration changes have is used by OAM entities to indicate configuration changes have
occured which might require the peer OAM entity to re-evaluate occurred which might require the peer OAM entity to
whether the peering is allowed. See local_satisfied in re-evaluate whether OAM peering is allowed.
[802.3ah, 57.3.1.2]. " "
REFERENCE "[802.3ah], 30.3.6.1.12" REFERENCE "[802.3ah], 30.3.6.1.12"
::= { dot3OamEntry 5 } ::= { dot3OamEntry 5 }
dot3OamFunctionsSupported OBJECT-TYPE dot3OamFunctionsSupported OBJECT-TYPE
SYNTAX BITS { SYNTAX BITS {
unidirectionalSupport (0), unidirectionalSupport (0),
loopbackSupport(1), loopbackSupport(1),
eventSupport(2), eventSupport(2),
variableSupport(3) variableSupport(3)
} }
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The OAM functions supported on this Ethernet like interface. "The OAM functions supported on this Ethernet like interface.
OAM consists of separate functional sets beyond the basic OAM consists of separate functional sets beyond the basic
discovery process which is always required. These functional discovery process which is always required. These functional
groups can be supported independently by any implementation. groups can be supported independently by any implementation.
These values are communicated to the peer via the local These values are communicated to the peer via the local
configuration field of Information OAMPDUs. " configuration field of Information OAMPDUs.
Setting 'unidirectionalSupport(0)' indicates that the OAM
entity supports the transmission of OAMPDUs on links that are
Ethernet OAM MIB March 2006
operating in unidirectional mode (traffic flowing in one
direction only). Setting 'loopbackSupport(1)' indicates the
OAM entity can initiate and respond to loopback commands.
Setting 'eventSupport(2)' indicates the OAM entity can send
and receive Event Notification OAMPDUs. Setting
'variableSupport(3)' indicates the OAM entity can send and
receive Variable Request and Response OAMPDUs.
"
REFERENCE "[802.3ah], 30.3.6.1.6" REFERENCE "[802.3ah], 30.3.6.1.6"
::= { dot3OamEntry 6 } ::= { dot3OamEntry 6 }
------------------------------------------------------------------ -- ***************************************************************
-- --
-- Ethernet OAM Peer group -- Ethernet OAM Peer group
-- --
EFM OAM MIB March 2005
dot3OamPeerTable OBJECT-TYPE dot3OamPeerTable OBJECT-TYPE
SYNTAX SEQUENCE OF Dot3OamPeerEntry SYNTAX SEQUENCE OF Dot3OamPeerEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Information about the OAM peer for a particular Ethernet like "This table contains information about the OAM peer for a
interface. OAM entities communicate with a single OAM peer particular Ethernet like interface. OAM entities communicate
entity on full-duplex Ethernet links on which OAM is enabled with a single OAM peer entity on Ethernet links on which OAM
and operating properly. is enabled and operating properly. There is one entry in this
table for each entry in the dot3OamTable for which information
In certain states, the OAM peer information is not available. on the peer OAM entity is available.
Whether peer information is available is communicated via the "
dot3OamPeerStatus object. When this object is inactive, all ::= { dot3OamObjects 2 }
other information in the row is to be considered invalid. "
::= { dot3OamMIB 2 }
dot3OamPeerEntry OBJECT-TYPE dot3OamPeerEntry OBJECT-TYPE
SYNTAX Dot3OamPeerEntry SYNTAX Dot3OamPeerEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry in the table, containing information on the peer OAM "An entry in the table, containing information on the peer OAM
entity for a single Ethernet like interface. entity for a single Ethernet like interface.
Note that there is at most one OAM peer for each Ethernet like Note that there is at most one OAM peer for each Ethernet like
interface. There is exactly one row in this table for each interface. Entries are automatically created when information
Ethernet like interface supporting OAM. " about the OAM peer entity becomes available, and automatically
deleted when the OAM peer entity is no longer in
communication. Peer information is not available when
dot3OamOperStatus is disabled(1), linkFault(2),
passiveWait(3), activeSendLocal(4). or nonOperHalfDuplex(10)).
"
INDEX { ifIndex } INDEX { ifIndex }
Ethernet OAM MIB March 2006
::= { dot3OamPeerTable 1 } ::= { dot3OamPeerTable 1 }
Dot3OamPeerEntry ::= Dot3OamPeerEntry ::=
SEQUENCE { SEQUENCE {
dot3OamPeerStatus INTEGER,
dot3OamPeerMacAddress MacAddress, dot3OamPeerMacAddress MacAddress,
dot3OamPeerVendorOui Dot3Oui, dot3OamPeerVendorOui Dot3Oui,
dot3OamPeerVendorInfo Unsigned32, dot3OamPeerVendorInfo Unsigned32,
dot3OamPeerMode INTEGER, dot3OamPeerMode INTEGER,
dot3OamPeerMaxOamPduSize Integer32, dot3OamPeerMaxOamPduSize Unsigned32,
dot3OamPeerConfigRevision Unsigned32, dot3OamPeerConfigRevision Unsigned32,
dot3OamPeerFunctionsSupported BITS dot3OamPeerFunctionsSupported BITS
} }
dot3OamPeerStatus OBJECT-TYPE
SYNTAX INTEGER {
active(1),
inactive(2)
}
MAX-ACCESS read-only
EFM OAM MIB March 2005
STATUS current
DESCRIPTION
"This object indicates whether the information in this row
should be considered valid. When active(1), the information
is valid and represents the current peer of the OAM entity.
When inactive(2), the information in this row is invalid.
A value of inactive(2) is returned if the dot3OamOperStatus is
disabled, passiveWait, or activeSendLocal. For all other
values of dot3OamOperStatus, a value of active(1) is returned.
"
::= { dot3OamPeerEntry 1 }
dot3OamPeerMacAddress OBJECT-TYPE dot3OamPeerMacAddress OBJECT-TYPE
SYNTAX MacAddress SYNTAX MacAddress
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The MAC address of the peer OAM entity. The MAC address is "The MAC address of the peer OAM entity. The MAC address is
derived from the most recently received OAMPDU. This value is derived from the most recently received OAMPDU.
initialized to all zeros (0x000000000000). This value is "
invalid if the dot3OamPeerStatus is inactive.
An OAMPDU is indicated by a valid frame with (1) destination
MAC address equal to that of the reserved MAC address for Slow
Protocols (See 43B of [802.3ah]), (2) a lengthOrType field
equal to the reserved type for Slow Protocols, (3) and a Slow
Protocols subtype equal to that of the subtype reserved for
OAM. "
REFERENCE "[802.3ah], 30.3.6.1.5." REFERENCE "[802.3ah], 30.3.6.1.5."
::= { dot3OamPeerEntry 2 } ::= { dot3OamPeerEntry 1 }
dot3OamPeerVendorOui OBJECT-TYPE dot3OamPeerVendorOui OBJECT-TYPE
SYNTAX Dot3Oui SYNTAX Dot3Oui
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The OUI of the OAM peer as reflected in the latest "The OUI of the OAM peer as reflected in the latest
Information OAMPDU received with a Local Information TLV. The Information OAMPDU received with a Local Information TLV. The
OUI can be used to identify the vendor of the remote OAM OUI can be used to identify the vendor of the remote OAM
entity. This value is initialized to all zeros (0x000000). entity. This value is initialized to zero before any Local
This value is considered invalid if the dot3OamPeerStatus is Information TLV is received.
inactive. "
An Information OAMPDU is indicated by a valid frame with (1)
destination MAC address equal to that of the reserved MAC
address for Slow Protocols (See 43B of [802.3ah]), (2) a
lengthOrType field equal to the reserved type for Slow
EFM OAM MIB March 2005
Protocols, (3) a Slow Protocols subtype equal to that of the
subtype reserved for OAM, (4) a OAM code that equals the code
reserved for Information OAMPDUs. "
REFERENCE "[802.3ah], 30.3.6.1.16." REFERENCE "[802.3ah], 30.3.6.1.16."
::= { dot3OamPeerEntry 3 } ::= { dot3OamPeerEntry 2 }
dot3OamPeerVendorInfo OBJECT-TYPE dot3OamPeerVendorInfo OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The Vendor Info of the OAM peer as reflected in the latest "The Vendor Info of the OAM peer as reflected in the latest
Information OAMPDU received with a Local Information TLV. The Information OAMPDU received with a Local Information TLV. The
Ethernet OAM MIB March 2006
vendor information field is within the Local Information TLV, vendor information field is within the Local Information TLV,
and can be used to determine additional information about the and can be used to determine additional information about the
peer entity. The format of the vendor information is peer entity. The format of the vendor information is
unspecified within the 32-bit field. This value is intialized unspecified within the 32-bit field. This value is
to all zeros (0x00000000). This value is invalid if the initialized to zero before any Local Information TLV is
dot3OamPeerStatus is inactive. received.
"
An Information OAMPDU is indicated by a valid frame with (1)
destination MAC address equal to that of the reserved MAC
address for Slow Protocols (See 43B of [802.3ah]), (2) a
lengthOrType field equal to the reserved type for Slow
Protocols, (3) a Slow Protocols subtype equal to that of the
subtype reserved for OAM, and (4) a OAM code that equals the
code reserved for Information OAMPDUs. "
REFERENCE "[802.3ah], 30.3.6.1.17." REFERENCE "[802.3ah], 30.3.6.1.17."
::= { dot3OamPeerEntry 4 } ::= { dot3OamPeerEntry 3 }
dot3OamPeerMode OBJECT-TYPE dot3OamPeerMode OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
active(1), active(1),
passive(2), passive(2),
unknown(3) unknown(3)
} }
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The mode of the OAM peer as reflected in the latest "The mode of the OAM peer as reflected in the latest
Information OAMPDU received with a Local Information TLV. The Information OAMPDU received with a Local Information TLV. The
mode of the peer can be determined from the Configuration mode of the peer can be determined from the Configuration
field in the Local Information TLV of the last Information field in the Local Information TLV of the last Information
OAMPDU received from the peer. This value is initialized to OAMPDU received from the peer. The value is unknown(3)
unknown(3), and is not valid if the dot3OamPeerStatus is whenever no Local Information TLV has been received. The
inactive. values of active(1) and passive(2) are returned when a Local
Information TLV has been received indicating the peer is in
EFM OAM MIB March 2005 active or passive mode, respectively.
"
An Information OAMPDU is indicated by a valid frame with (1)
destination MAC address equal to that of the reserved MAC
address for Slow Protocols (See 43B of [802.3ah]), (2) a
lengthOrType field equal to the reserved type for Slow
Protocols, (3) a Slow Protocols subtype equal to that of the
subtype reserved for OAM, and (4) a OAM code that equals the
code reserved for Information OAMPDUs. "
REFERENCE "[802.3ah], 30.3.6.1.7." REFERENCE "[802.3ah], 30.3.6.1.7."
::= { dot3OamPeerEntry 5 } ::= { dot3OamPeerEntry 4 }
dot3OamPeerMaxOamPduSize OBJECT-TYPE dot3OamPeerMaxOamPduSize OBJECT-TYPE
SYNTAX Integer32 (64..1522) SYNTAX Unsigned32 (0..1518)
UNITS "bytes" UNITS "octets"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The maximum size of OAMPDU supported by the peer as reflected "The maximum size of OAMPDU supported by the peer as reflected
in the latest Information OAMPDU received with a Local in the latest Information OAMPDU received with a Local
Information TLV. Ethernet OAM on this interface must not use Information TLV. Ethernet OAM on this interface must not use
OAMPDUs that exceed this size. The maximum OAMPDU size can be OAMPDUs that exceed this size. The maximum OAMPDU size can be
determined from the PDU Configuration field of the Local determined from the PDU Configuration field of the Local
Information TLV of the last Information OAMPDU received from Information TLV of the last Information OAMPDU received from
the peer. This value is initialized to 64, and is invalid if the peer. A value of zero is returned if no Local Information
the dot3OamPeerStatus is inactive. TLV has been received. Otherwise, the value of the OAM peer's
maximum OAMPDU size is returned in this value.
An Information OAMPDU is indicated by a valid frame with (1) Ethernet OAM MIB March 2006
destination MAC address equal to that of the reserved MAC
address for Slow Protocols (See 43B of [802.3ah]), (2) a Note that the values 1..63 are invalid sizes for Ethernet
lengthOrType field equal to the reserved type for Slow frames and should never appear.
Protocols, (3) a Slow Protocols subtype equal to that of the "
subtype reserved for OAM, and (4) a OAM code that equals the
code reserved for Information OAMPDUs. "
REFERENCE "[802.3ah], 30.3.6.1.9." REFERENCE "[802.3ah], 30.3.6.1.9."
::= { dot3OamPeerEntry 6 } ::= { dot3OamPeerEntry 5 }
dot3OamPeerConfigRevision OBJECT-TYPE dot3OamPeerConfigRevision OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32(0..65535)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The configuration revision of the OAM peer as reflected in "The configuration revision of the OAM peer as reflected in
the latest OAMPDU. This attribute is changed by the peer the latest OAMPDU. This attribute is changed by the peer
whenever it has a local configuration change for Ethernet OAM whenever it has a local configuration change for Ethernet OAM
this interface. This value is initialized to all zeros this interface. The configuration revision can be determined
(0x00000000), and is invalid if the dot3OamPeerStatus is from the Revision field of the Local Information TLV of the
inactive. most recently received Information OAMPDU with a Local
Information TLV. A value of zero is returned if no Local
The configuration revision can be determined from the Revision Information TLV has been received.
EFM OAM MIB March 2005 "
field of the Local Information TLV of the most recently
received Information OAMPDU with a Local Information TLV.
An Information OAMPDU is indicated by a valid frame with (1)
destination MAC address equal to that of the reserved MAC
address for Slow Protocols (See 43B of [802.3ah]), (2) a
lengthOrType field equal to the reserved type for Slow
Protocols, (3) a Slow Protocols subtype equal to that of the
subtype reserved for OAM, and (4) a OAM code that equals the
code reserved for Information OAMPDUs. "
REFERENCE "[802.3ah], 30.3.6.1.13." REFERENCE "[802.3ah], 30.3.6.1.13."
::= { dot3OamPeerEntry 7 } ::= { dot3OamPeerEntry 6 }
dot3OamPeerFunctionsSupported OBJECT-TYPE dot3OamPeerFunctionsSupported OBJECT-TYPE
SYNTAX BITS { SYNTAX BITS {
unidirectionalSupport (0), unidirectionalSupport (0),
loopbackSupport(1), loopbackSupport(1),
eventSupport(2), eventSupport(2),
variableSupport(3) variableSupport(3)
} }
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The OAM functions supported on this Ethernet like interface. "The OAM functions supported on this Ethernet like interface.
OAM consists of separate functionality sets above the basic OAM consists of separate functionality sets above the basic
discovery process. This value indicates the capabilities of discovery process. This value indicates the capabilities of
the peer OAM entity with respect to these functions. This the peer OAM entity with respect to these functions. This
value is initialized so all bits are clear, and is invalid if value is initialized so all bits are clear.
the dot3OamPeerStatus is inactive.
The capbilities of the OAM peer can be determined from the If unidirectionalSupport(0) is set, then the peer OAM entity
supports sending OAM frames on Ethernet interfaces when the
receive path is known to be inoperable. If
loopbackSupport(1) is set, then the peer OAM entity can send
and receive OAM loopback commands. If eventSupport(2) is set,
then the peer OAM entity can send and receive event OAMPDUs to
signal various error conditions. If variableSupport(3) is set,
then the peer OAM entity can send and receive variable
Ethernet OAM MIB March 2006
requests to monitor attribute value as described in Clause 57
of [802.3ah].
The capabilities of the OAM peer can be determined from the
configuration field of the Local Information TLV of the most configuration field of the Local Information TLV of the most
recently received Information OAMPDU with a Local Information recently received Information OAMPDU with a Local Information
TLV. TLV. All zeros are returned if no Local Information TLV has
yet been received.
An Information OAMPDU is indicated by a valid frame with (1) "
destination MAC address equal to that of the reserved MAC
address for Slow Protocols (See 43B of [802.3ah]), (2) a
lengthOrType field equal to the reserved type for Slow
Protocols, (3) a Slow Protocols subtype equal to that of the
subtype reserved for OAM, and (4) a OAM code that equals the
code reserved for Information OAMPDUs. "
REFERENCE "[802.3ah], REFERENCE 30.3.6.1.7." REFERENCE "[802.3ah], REFERENCE 30.3.6.1.7."
::= { dot3OamPeerEntry 8 } ::= { dot3OamPeerEntry 7 }
------------------------------------------------------------------ -- ***************************************************************
-- --
EFM OAM MIB March 2005
-- Ethernet OAM Loopback group -- Ethernet OAM Loopback group
-- --
dot3OamLoopbackTable OBJECT-TYPE dot3OamLoopbackTable OBJECT-TYPE
SYNTAX SEQUENCE OF Dot3OamLoopbackEntry SYNTAX SEQUENCE OF Dot3OamLoopbackEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table contains methods to control the loopback state of "This table contains controls for the loopback state of the
the local link as well as indicating the status of the local link as well as indicating the status of the loopback
loopback function. function. There is one entry in this table for each entry in
dot3OamTable that supports loopback functionality (where
dot3OamFunctionsSupported includes the loopbackSupport bit
set).
Loopback can be used to place the remote OAM entity in a state Loopback can be used to place the remote OAM entity in a state
where every received frame (except OAMPDUs) are echoed back where every received frame (except OAMPDUs) is echoed back
over the same interface on which they were received. In this over the same interface on which they were received. In this
state, at the remote entity, 'normal' traffic is disabled as state, at the remote entity, 'normal' traffic is disabled as
only the looped back frames are transmitted on the interface. only the looped back frames are transmitted on the interface.
Loopback is thus an intrusive operation that prohibits normal Loopback is thus an intrusive operation that prohibits normal
data flow and should be used accordingly. " data flow and should be used accordingly. "
::= { dot3OamMIB 3 } ::= { dot3OamObjects 3 }
dot3OamLoopbackEntry OBJECT-TYPE dot3OamLoopbackEntry OBJECT-TYPE
SYNTAX Dot3OamLoopbackEntry SYNTAX Dot3OamLoopbackEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry in the table, containing information on the loopback "An entry in the table, containing information on the loopback
status for a single Ethernet like interface. There is an status for a single Ethernet like interface. Entries in the
entry in this table for every Ethernet like interface on which table are automatically created whenever the local OAM entity
supports OAM and loopback function within OAM (as indicated in Ethernet OAM MIB March 2006
dot3OamFunctionsSupported). "
supports loopback capabilities. The loopback status on the
interface can be determined from the dot3OamLoopbackStatus
object.
"
INDEX { ifIndex } INDEX { ifIndex }
::= { dot3OamLoopbackTable 1 } ::= { dot3OamLoopbackTable 1 }
Dot3OamLoopbackEntry ::= Dot3OamLoopbackEntry ::=
SEQUENCE { SEQUENCE {
dot3OamLoopbackCommand INTEGER,
dot3OamLoopbackStatus INTEGER, dot3OamLoopbackStatus INTEGER,
dot3OamLoopbackIgnoreRx INTEGER dot3OamLoopbackIgnoreRx INTEGER
} }
dot3OamLoopbackCommand OBJECT-TYPE
SYNTAX INTEGER {
noLoopback (1),
startRemoteLoopback (2),
stopRemoteLoopback (3)
}
MAX-ACCESS read-write
EFM OAM MIB March 2005
STATUS current
DESCRIPTION
"This attribute initiates or terminates remote loopback with
an OAM peer. Writing startRemoteLoopback(2) to this attribute
cause the local OAM client to send a loopback OAMPDU to the
OAM peer with the loopback enable flags set. Writing
stopRemoteLoopback(3) to this attribute will cause the local
OAM client to send a loopback OAMPDU to the OAM peer with the
loopback enable flags cleared. Writing noLoopback to this
attribute has no effect.
Writes to this attribute are ignored unless the OAM status of
this interface is 'operational' (dot3OamOperStatus).
The attribute always returns noLoopback on a read. To
determine the loopback status, use the attribute
dot3OamLoopbackStatus. "
REFERENCE "[802.3ah], 57.2.11"
::= { dot3OamLoopbackEntry 1 }
dot3OamLoopbackStatus OBJECT-TYPE dot3OamLoopbackStatus OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
-- all values, except where noted, can be read
-- but cannot be written
noLoopback (1), noLoopback (1),
-- initiatingLoopback can be read or written
initiatingLoopback (2), initiatingLoopback (2),
remoteLoopback (3), remoteLoopback (3),
-- terminatingLoopback can be read or written
terminatingLoopback (4), terminatingLoopback (4),
localLoopback (5), localLoopback (5),
unknown (6) unknown (6)
} }
MAX-ACCESS read-only MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The loopback status of the OAM entity. This status is "The loopback status of the OAM entity. This status is
determined by a combination of the local parser and determined by a combination of the local parser and
multiplexer states, the remote parser and multiplexer states, multiplexer states, the remote parser and multiplexer states,
as well as by the actions of the local OAM client. When as well as by the actions of the local OAM client. When
operating in normal mode with no loopback in progress, the operating in normal mode with no loopback in progress, the
status reads noLoopback(1). status reads noLoopback(1).
If the OAM client has sent an Loopback OAMPDU and is waiting The values initiatingLooopback(2) and terminatingLoopback(4)
for a response, where the local parser and multiplexer states can be read or written. The other values can only be read -
are DISCARD (see [802.3ah, 57.2.11.1]), the status is they can never be written. Writing initiatingLoopback causes
'initiatingLoopback'. In this case, the local OAM entity has the local OAM entity to start the loopback process with its
yet to receive any acknowledgement that the remote OAM entity peer. This value can only be written when the status is
has received its loopback command request. noLoopback(1). Writing the value initiatingLoopback(2) in any
other state has no effect. When in remoteLoopback(3), writing
terminatingLoopback(4) causes the local OAM entity to initiate
the termination of the loopback state. Writing
terminatingLoopack(4) in any other state has no effect.
If the OAM client initiates a looopback and has sent an
Ethernet OAM MIB March 2006
Loopback OAMPDU and is waiting for a response, where the local
parser and multiplexer states are DISCARD (see [802.3ah,
57.2.11.1]), the status is 'initiatingLoopback'. In this
case, the local OAM entity has yet to receive any
acknowledgement that the remote OAM entity has received its
loopback command request.
If the local OAM client knows that the remote OAM entity is in If the local OAM client knows that the remote OAM entity is in
loopback mode (via the remote state information as described loopback mode (via the remote state information as described
in [802.3ah, 57.2.11.1, 30.3.6.1.15]), the status is in [802.3ah, 57.2.11.1, 30.3.6.1.15]), the status is
EFM OAM MIB March 2005
remoteLoopback(3). If the local OAM client is in the process remoteLoopback(3). If the local OAM client is in the process
of terminating the remote loopback [802.3ah, 57.2.11.3, of terminating the remote loopback [802.3ah, 57.2.11.3,
30.3.6.1.14], with its local multiplexer and parser states in 30.3.6.1.14], with its local multiplexer and parser states in
DISCARD, the status is terminatingLoopback(4). If the remote DISCARD, the status is terminatingLoopback(4). If the remote
OAM client has put the local OAM entity in loopback mode as OAM client has put the local OAM entity in loopback mode as
indicated by its local parser state, the status is indicated by its local parser state, the status is
localLoopback(5). localLoopback(5).
The unknown(6) status indicates the parser and multiplexer The unknown(6) status indicates the parser and multiplexer
combination is unexpected. This status may be returned if the combination is unexpected. This status may be returned if the
skipping to change at page 22, line 31 skipping to change at page 22, line 41
value LclPrsr LclMux RmtPrsr RmtMux value LclPrsr LclMux RmtPrsr RmtMux
noLoopback FWD FWD FWD FWD noLoopback FWD FWD FWD FWD
initLoopback DISCARD DISCARD FWD FWD initLoopback DISCARD DISCARD FWD FWD
rmtLoopback DISCARD FWD LPBK DISCARD rmtLoopback DISCARD FWD LPBK DISCARD
tmtngLoopback DISCARD DISCARD LPBK DISCARD tmtngLoopback DISCARD DISCARD LPBK DISCARD
lclLoopback LPBK DISCARD DISCARD FWD lclLoopback LPBK DISCARD DISCARD FWD
unknown *** any other combination *** unknown *** any other combination ***
" "
REFERENCE "[802.3ah], REFERENCE 57.2.11, 30.3.61.14, REFERENCE "[802.3ah], REFERENCE 57.2.11, 30.3.61.14,
30.3.6.1.15" 30.3.6.1.15"
::= { dot3OamLoopbackEntry 2 } ::= { dot3OamLoopbackEntry 1 }
dot3OamLoopbackIgnoreRx OBJECT-TYPE dot3OamLoopbackIgnoreRx OBJECT-TYPE
SYNTAX INTEGER { ignore(1), process(2) } SYNTAX INTEGER { ignore(1), process(2) }
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Since OAM loopback is a distruptive operation (user traffic "Since OAM loopback is a disruptive operation (user traffic
does not pass), this attribute provides a mechanism to provide does not pass), this attribute provides a mechanism to provide
controls over whether received OAM loopback commands are controls over whether received OAM loopback commands are
processed or ignored. When the value is ignore(1), received processed or ignored. When the value is ignore(1), received
loopback commands are ignored. When the value is process(2), loopback commands are ignored. When the value is process(2),
OAM loopback commands are processed. The default value is to OAM loopback commands are processed. The default value is to
ignore loopback commands (ignore(1)). ignore loopback commands (ignore(1)).
The attribute has no meaning if the local OAM entity does not Ethernet OAM MIB March 2006
support the loopback function (as defined in
dot3OamFunctionsSupported). " "
REFERENCE "[802.3ah], REFERENCE 57.2.11, 30.3.61.14, REFERENCE "[802.3ah], REFERENCE 57.2.11, 30.3.61.14,
30.3.6.1.15" 30.3.6.1.15"
::= { dot3OamLoopbackEntry 3 } ::= { dot3OamLoopbackEntry 2 }
------------------------------------------------------------------
EFM OAM MIB March 2005
-- ***************************************************************
-- --
-- Ethernet OAM Statistics group -- Ethernet OAM Statistics group
-- --
dot3OamStatsTable OBJECT-TYPE dot3OamStatsTable OBJECT-TYPE
SYNTAX SEQUENCE OF Dot3OamStatsEntry SYNTAX SEQUENCE OF Dot3OamStatsEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Statistics for the OAM function on a particular Ethernet like "This table contains statistics for the OAM function on a
interface." particular Ethernet like interface. There is an entry in the
::= { dot3OamMIB 4 } table for every entry in the dot3OamTable.
The counters in this table are defined as 32-bit entries to
match the counter size as defined in [802.3ah]. Given the OAM
protocol is a slow protocol, the counters increment at a slow
rate.
"
::= { dot3OamObjects 4 }
dot3OamStatsEntry OBJECT-TYPE dot3OamStatsEntry OBJECT-TYPE
SYNTAX Dot3OamStatsEntry SYNTAX Dot3OamStatsEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry in the table, containing statistics information on "An entry in the table, containing statistics information on
the Ethernet OAM function for a single Ethernet like the Ethernet OAM function for a single Ethernet like
interface." interface. Entries are automatically created for every entry
in the dot3OamTable. Counters are maintained across
transitions in dot3OamOperStatus.
"
INDEX { ifIndex } INDEX { ifIndex }
::= { dot3OamStatsTable 1 } ::= { dot3OamStatsTable 1 }
Dot3OamStatsEntry ::= Dot3OamStatsEntry ::=
SEQUENCE { SEQUENCE {
dot3OamInformationTx Counter32, dot3OamInformationTx Counter32,
dot3OamInformationRx Counter32, dot3OamInformationRx Counter32,
dot3OamUniqueEventNotificationTx Counter32, dot3OamUniqueEventNotificationTx Counter32,
dot3OamUniqueEventNotificationRx Counter32, dot3OamUniqueEventNotificationRx Counter32,
dot3OamDuplicateEventNotificationTx Counter32, dot3OamDuplicateEventNotificationTx Counter32,
Ethernet OAM MIB March 2006
dot3OamDuplicateEventNotificationRx Counter32, dot3OamDuplicateEventNotificationRx Counter32,
dot3OamLoopbackControlTx Counter32, dot3OamLoopbackControlTx Counter32,
dot3OamLoopbackControlRx Counter32, dot3OamLoopbackControlRx Counter32,
dot3OamVariableRequestTx Counter32, dot3OamVariableRequestTx Counter32,
dot3OamVariableRequestRx Counter32, dot3OamVariableRequestRx Counter32,
dot3OamVariableResponseTx Counter32, dot3OamVariableResponseTx Counter32,
dot3OamVariableResponseRx Counter32, dot3OamVariableResponseRx Counter32,
dot3OamOrgSpecificTx Counter32, dot3OamOrgSpecificTx Counter32,
dot3OamOrgSpecificRx Counter32, dot3OamOrgSpecificRx Counter32,
dot3OamUnsupportedCodesTx Counter32, dot3OamUnsupportedCodesTx Counter32,
dot3OamUnsupportedCodesRx Counter32, dot3OamUnsupportedCodesRx Counter32,
dot3OamFramesLostDueToOam Counter32 dot3OamFramesLostDueToOam Counter32
} }
dot3OamInformationTx OBJECT-TYPE dot3OamInformationTx OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
EFM OAM MIB March 2005
UNITS "frames" UNITS "frames"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A count of the number of Information OAMPDUs transmitted on "A count of the number of Information OAMPDUs transmitted on
this interface. this interface.
An Information OAMPDU is indicated by a valid frame with (1)
destination MAC address equal to that of the reserved MAC
address for Slow Protocols (See 43B of [802.3ah]), (2) a
lengthOrType field equal to the reserved type for Slow
Protocols, (3) a Slow Protocols subtype equal to that of the
subtype reserved for OAM, and (4) an OAMPDU code equals the
OAM Information code.
Discontinuities of this counter can occur at re-initialization Discontinuities of this counter can occur at re-initialization
of the management system, and at other times as indicated by of the management system, and at other times as indicated by
the value of the ifCounterDiscontinuityTime. " the value of the ifCounterDiscontinuityTime. "
REFERENCE "[802.3ah], 30.3.6.1.20." REFERENCE "[802.3ah], 30.3.6.1.20."
::= { dot3OamStatsEntry 1 } ::= { dot3OamStatsEntry 1 }
dot3OamInformationRx OBJECT-TYPE dot3OamInformationRx OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
UNITS "frames" UNITS "frames"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A count of the number of Information OAMPDUs received on this "A count of the number of Information OAMPDUs received on this
interface. interface.
An Information OAMPDU is indicated by a valid frame with (1)
destination MAC address equal to that of the reserved MAC
address for Slow Protocols (See 43B of [802.3ah]), (2) a
lengthOrType field equal to the reserved type for Slow
Protocols, (3) a Slow Protocols subtype equal to that of the
subtype reserved for OAM, and (4) an OAMPDU code equals the
OAM Information code.
Discontinuities of this counter can occur at re-initialization Discontinuities of this counter can occur at re-initialization
of the management system, and at other times as indicated by of the management system, and at other times as indicated by
the value of the ifCounterDiscontinuityTime. " the value of the ifCounterDiscontinuityTime.
"
REFERENCE "[802.3ah], 30.3.6.1.21." REFERENCE "[802.3ah], 30.3.6.1.21."
::= { dot3OamStatsEntry 2 } ::= { dot3OamStatsEntry 2 }
dot3OamUniqueEventNotificationTx OBJECT-TYPE dot3OamUniqueEventNotificationTx OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
UNITS "frames" UNITS "frames"
Ethernet OAM MIB March 2006
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
EFM OAM MIB March 2005
DESCRIPTION DESCRIPTION
"A count of the number of unique Event OAMPDUs transmitted on "A count of the number of unique Event OAMPDUs transmitted on
this interface. Event notifications may be sent in duplicate this interface. Event notifications may be sent in duplicate
to increase the probability of successfully being received, to increase the probability of successfully being received,
given the possiblity that a frame may be lost in transit. given the possibility that a frame may be lost in transit.
Duplicate Event Notification transmissions are counted by
An Event Notification OAMPDU is indicated by a valid frame dot3OamDuplicateEventNotificationTx.
with (1) destination MAC address equal to that of the reserved
MAC address for Slow Protocols (See 43B of [802.3ah]), (2) a
lengthOrType field equal to the reserved type for Slow
Protocols, (3) a Slow Protocols subtype equal to that of the
subtype reserved for OAM, and (4) an OAMPDU code equals the
OAM Event code.
A unique Event Notification OAMPDU is indicated as an Event A unique Event Notification OAMPDU is indicated as an Event
Notification OAMPDU with a Sequence Number field that is Notification OAMPDU with a Sequence Number field that is
distinct from the previously transmitted Event Notification distinct from the previously transmitted Event Notification
OAMPDU Sequence Number. OAMPDU Sequence Number.
Discontinuities of this counter can occur at re-initialization Discontinuities of this counter can occur at re-initialization
of the management system, and at other times as indicated by of the management system, and at other times as indicated by
the value of the ifCounterDiscontinuityTime. " the value of the ifCounterDiscontinuityTime.
"
REFERENCE "[802.3ah], 30.3.6.1.22." REFERENCE "[802.3ah], 30.3.6.1.22."
::= { dot3OamStatsEntry 3 } ::= { dot3OamStatsEntry 3 }
dot3OamUniqueEventNotificationRx OBJECT-TYPE dot3OamUniqueEventNotificationRx OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
UNITS "frames" UNITS "frames"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A count of the number of unique Event OAMPDUs received on "A count of the number of unique Event OAMPDUs received on
this interface. Event notification OAMPDUs may be sent in this interface. Event notification OAMPDUs may be sent in
duplicate to increase the probability of successfully being duplicate to increase the probability of successfully being
received, given the possiblity that a frame may be lost in received, given the possibility that a frame may be lost in
transit. transit. Duplicate Event Notification receptions are counted
by dot3OamDuplicateEventNotificationRx.
An Event Notification OAMPDU is indicated by a valid frame
with (1) destination MAC address equal to that of the reserved
MAC address for Slow Protocols (See 43B of [802.3ah]), (2) a
lengthOrType field equal to the reserved type for Slow
Protocols, (3) a Slow Protocols subtype equal to that of the
subtype reserved for OAM, and (4) an OAMPDU code equals the
OAM Event code.
A unique Event Notification OAMPDU is indicated as an Event A unique Event Notification OAMPDU is indicated as an Event
Notification OAMPDU with a Sequence Number field that is Notification OAMPDU with a Sequence Number field that is
distinct from the previously received Event Notification distinct from the previously received Event Notification
EFM OAM MIB March 2005
OAMPDU Sequence Number. OAMPDU Sequence Number.
Discontinuities of this counter can occur at re-initialization Discontinuities of this counter can occur at re-initialization
of the management system, and at other times as indicated by of the management system, and at other times as indicated by
the value of the ifCounterDiscontinuityTime. " the value of the ifCounterDiscontinuityTime.
"
REFERENCE "[802.3ah], 30.3.6.1.24." REFERENCE "[802.3ah], 30.3.6.1.24."
::= { dot3OamStatsEntry 4 } ::= { dot3OamStatsEntry 4 }
dot3OamDuplicateEventNotificationTx OBJECT-TYPE dot3OamDuplicateEventNotificationTx OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
Ethernet OAM MIB March 2006
UNITS "frames" UNITS "frames"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A count of the number of duplicate Event OAMPDUs transmitted "A count of the number of duplicate Event OAMPDUs transmitted
on this interface. Event notification OAMPDUs may be sent in on this interface. Event notification OAMPDUs may be sent in
duplicate to increase the probability of successfully being duplicate to increase the probability of successfully being
received, given the possiblity that a frame may be lost in received, given the possibility that a frame may be lost in
transit. transit.
An Event Notification OAMPDU is indicated by a valid frame
with (1) destination MAC address equal to that of the reserved
MAC address for Slow Protocols (See 43B of [802.3ah]), (2) a
lengthOrType field equal to the reserved type for Slow
Protocols, (3) a Slow Protocols subtype equal to that of the
subtype reserved for OAM, and (4) an OAMPDU code equals the
OAM Event code.
A duplicate Event Notification OAMPDU is indicated as an Event A duplicate Event Notification OAMPDU is indicated as an Event
Notification OAMPDU with a Sequence Number field that is Notification OAMPDU with a Sequence Number field that is
identical to the previously transmitted Event Notification identical to the previously transmitted Event Notification
OAMPDU Sequence Number. OAMPDU Sequence Number.
Discontinuities of this counter can occur at re-initialization Discontinuities of this counter can occur at re-initialization
of the management system, and at other times as indicated by of the management system, and at other times as indicated by
the value of the ifCounterDiscontinuityTime. " the value of the ifCounterDiscontinuityTime.
"
REFERENCE "[802.3ah], 30.3.6.1.23." REFERENCE "[802.3ah], 30.3.6.1.23."
::= { dot3OamStatsEntry 5 } ::= { dot3OamStatsEntry 5 }
dot3OamDuplicateEventNotificationRx OBJECT-TYPE dot3OamDuplicateEventNotificationRx OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
UNITS "frames" UNITS "frames"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A count of the number of duplicate Event OAMPDUs received on "A count of the number of duplicate Event OAMPDUs received on
this interface. Event notification OAMPDUs may be sent in this interface. Event notification OAMPDUs may be sent in
duplicate to increase the probability of successfully being duplicate to increase the probability of successfully being
received, given the possiblity that a frame may be lost in received, given the possibility that a frame may be lost in
EFM OAM MIB March 2005
transit. transit.
An Event Notification OAMPDU is indicated by a valid frame
with (1) destination MAC address equal to that of the reserved
MAC address for Slow Protocols (See 43B of [802.3ah]), (2) a
lengthOrType field equal to the reserved type for Slow
Protocols, (3) a Slow Protocols subtype equal to that of the
subtype reserved for OAM, and (4) an OAMPDU code equals the
OAM Event code.
A duplicate Event Notification OAMPDU is indicated as an Event A duplicate Event Notification OAMPDU is indicated as an Event
Notification OAMPDU with a Sequence Number field that is Notification OAMPDU with a Sequence Number field that is
identical to the previously received Event Notification OAMPDU identical to the previously received Event Notification OAMPDU
Sequence Number. Sequence Number.
Discontinuities of this counter can occur at re-initialization Discontinuities of this counter can occur at re-initialization
of the management system, and at other times as indicated by of the management system, and at other times as indicated by
the value of the ifCounterDiscontinuityTime. " the value of the ifCounterDiscontinuityTime.
"
REFERENCE "[802.3ah], 30.3.6.1.25." REFERENCE "[802.3ah], 30.3.6.1.25."
::= { dot3OamStatsEntry 6 } ::= { dot3OamStatsEntry 6 }
dot3OamLoopbackControlTx OBJECT-TYPE dot3OamLoopbackControlTx OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
UNITS "frames" UNITS "frames"
Ethernet OAM MIB March 2006
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A count of the number of Loopback Control OAMPDUs transmitted "A count of the number of Loopback Control OAMPDUs transmitted
on this interface. on this interface.
An Loopback Conrol OAMPDU is indicated by a valid frame with
(1) destination MAC address equal to that of the reserved MAC
address for Slow Protocols (See 43B of [802.3ah]), (2) a
lengthOrType field equal to the reserved type for Slow
Protocols, (3) a Slow Protocols subtype equal to that of the
subtype reserved for OAM, and (4) an OAMPDU code equals the
OAM Loopback Control code.
Discontinuities of this counter can occur at re-initialization Discontinuities of this counter can occur at re-initialization
of the management system, and at other times as indicated by of the management system, and at other times as indicated by
the value of the ifCounterDiscontinuityTime. " the value of the ifCounterDiscontinuityTime.
"
REFERENCE "[802.3ah], 30.3.6.1.26." REFERENCE "[802.3ah], 30.3.6.1.26."
::= { dot3OamStatsEntry 7 } ::= { dot3OamStatsEntry 7 }
dot3OamLoopbackControlRx OBJECT-TYPE dot3OamLoopbackControlRx OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
UNITS "frames" UNITS "frames"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
EFM OAM MIB March 2005
DESCRIPTION DESCRIPTION
"A count of the number of Loopback Control OAMPDUs transmitted "A count of the number of Loopback Control OAMPDUs received
on this interface. on this interface.
An Loopback Control OAMPDU is indicated by a valid frame with
(1) destination MAC address equal to that of the reserved MAC
address for Slow Protocols (See 43B of [802.3ah]), (2) a
lengthOrType field equal to the reserved type for Slow
Protocols, (3) a Slow Protocols subtype equal to that of the
subtype reserved for OAM, and (4) an OAMPDU code equals the
OAM Loopback Control code.
Discontinuities of this counter can occur at re-initialization Discontinuities of this counter can occur at re-initialization
of the management system, and at other times as indicated by of the management system, and at other times as indicated by
the value of the ifCounterDiscontinuityTime. " the value of the ifCounterDiscontinuityTime.
"
REFERENCE "[802.3ah], 30.3.6.1.27." REFERENCE "[802.3ah], 30.3.6.1.27."
::= { dot3OamStatsEntry 8 } ::= { dot3OamStatsEntry 8 }
dot3OamVariableRequestTx OBJECT-TYPE dot3OamVariableRequestTx OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
UNITS "frames" UNITS "frames"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A count of the number of Variable Request OAMPDUs transmitted "A count of the number of Variable Request OAMPDUs transmitted
on this interface. on this interface.
An Variable Request OAMPDU is indicated by a valid frame with
(1) destination MAC address equal to that of the reserved MAC
address for Slow Protocols (See 43B of [802.3ah]), (2) a
lengthOrType field equal to the reserved type for Slow
Protocols, (3) a Slow Protocols subtype equal to that of the
subtype reserved for OAM, and (4) an OAMPDU code equals the
OAM Variable Request code.
Discontinuities of this counter can occur at re-initialization Discontinuities of this counter can occur at re-initialization
of the management system, and at other times as indicated by of the management system, and at other times as indicated by
the value of the ifCounterDiscontinuityTime. " the value of the ifCounterDiscontinuityTime.
"
REFERENCE "[802.3ah], 30.3.6.1.28." REFERENCE "[802.3ah], 30.3.6.1.28."
::= { dot3OamStatsEntry 9 } ::= { dot3OamStatsEntry 9 }
dot3OamVariableRequestRx OBJECT-TYPE dot3OamVariableRequestRx OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
UNITS "frames" UNITS "frames"
MAX-ACCESS read-only MAX-ACCESS read-only
Ethernet OAM MIB March 2006
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A count of the number of Variable Request OAMPDUs received on "A count of the number of Variable Request OAMPDUs received on
this interface. this interface.
EFM OAM MIB March 2005
An Variable Request OAMPDU is indicated by a valid frame with
(1) destination MAC address equal to that of the reserved MAC
address for Slow Protocols (See 43B of [802.3ah]), (2) a
lengthOrType field equal to the reserved type for Slow
Protocols, (3) a Slow Protocols subtype equal to that of the
subtype reserved for OAM, and (4) an OAMPDU code equals the
OAM Variable Request code.
Discontinuities of this counter can occur at re-initialization Discontinuities of this counter can occur at re-initialization
of the management system, and at other times as indicated by of the management system, and at other times as indicated by
the value of the ifCounterDiscontinuityTime. " the value of the ifCounterDiscontinuityTime.
"
REFERENCE "[802.3ah], 30.3.6.1.29." REFERENCE "[802.3ah], 30.3.6.1.29."
::= { dot3OamStatsEntry 10 } ::= { dot3OamStatsEntry 10 }
dot3OamVariableResponseTx OBJECT-TYPE dot3OamVariableResponseTx OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
UNITS "frames" UNITS "frames"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A count of the number of Variable Response OAMPDUs "A count of the number of Variable Response OAMPDUs
transmitted on this interface. transmitted on this interface.
An Variable Response OAMPDU is indicated by a valid frame with
(1) destination MAC address equal to that of the reserved MAC
address for Slow Protocols (See 43B of [802.3ah]), (2) a
lengthOrType field equal to the reserved type for Slow
Protocols, (3) a Slow Protocols subtype equal to that of the
subtype reserved for OAM, and (4) an OAMPDU code equals the
OAM Variable Response code.
Discontinuities of this counter can occur at re-initialization Discontinuities of this counter can occur at re-initialization
of the management system, and at other times as indicated by of the management system, and at other times as indicated by
the value of the ifCounterDiscontinuityTime. " the value of the ifCounterDiscontinuityTime.
"
REFERENCE "[802.3ah], 30.3.6.1.30." REFERENCE "[802.3ah], 30.3.6.1.30."
::= { dot3OamStatsEntry 11 } ::= { dot3OamStatsEntry 11 }
dot3OamVariableResponseRx OBJECT-TYPE dot3OamVariableResponseRx OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
UNITS "frames" UNITS "frames"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A count of the number of Variable Response OAMPDUs received "A count of the number of Variable Response OAMPDUs received
on this interface. on this interface.
An Variable Response OAMPDU is indicated by a valid frame with
(1) destination MAC address equal to that of the reserved MAC
EFM OAM MIB March 2005
address for Slow Protocols (See 43B of [802.3ah]), (2) a
lengthOrType field equal to the reserved type for Slow
Protocols, (3) a Slow Protocols subtype equal to that of the
subtype reserved for OAM, and (4) an OAMPDU code equals the
OAM Variable Response code.
Discontinuities of this counter can occur at re-initialization Discontinuities of this counter can occur at re-initialization
of the management system, and at other times as indicated by of the management system, and at other times as indicated by
the value of the ifCounterDiscontinuityTime. " the value of the ifCounterDiscontinuityTime.
"
REFERENCE "[802.3ah], 30.3.6.1.31." REFERENCE "[802.3ah], 30.3.6.1.31."
::= { dot3OamStatsEntry 12 } ::= { dot3OamStatsEntry 12 }
dot3OamOrgSpecificTx OBJECT-TYPE dot3OamOrgSpecificTx OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
UNITS "frames" UNITS "frames"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
Ethernet OAM MIB March 2006
DESCRIPTION DESCRIPTION
"A count of the number of Organization Specific OAMPDUs "A count of the number of Organization Specific OAMPDUs
transmitted on this interface. transmitted on this interface.
An Organization Specific OAMPDU is indicated by a valid frame
with (1) destination MAC address equal to that of the reserved
MAC address for Slow Protocols (See 43B of [802.3ah]), (2) a
lengthOrType field equal to the reserved type for Slow
Protocols, (3) a Slow Protocols subtype equal to that of the
subtype reserved for OAM, and (4) an OAMPDU code equals the
OAM Organization Specific code.
Discontinuities of this counter can occur at re-initialization Discontinuities of this counter can occur at re-initialization
of the management system, and at other times as indicated by of the management system, and at other times as indicated by
the value of the ifCounterDiscontinuityTime. " the value of the ifCounterDiscontinuityTime.
"
REFERENCE "[802.3ah], 30.3.6.1.32." REFERENCE "[802.3ah], 30.3.6.1.32."
::= { dot3OamStatsEntry 13 } ::= { dot3OamStatsEntry 13 }
dot3OamOrgSpecificRx OBJECT-TYPE dot3OamOrgSpecificRx OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
UNITS "frames" UNITS "frames"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A count of the number of Organization Specific OAMPDUs "A count of the number of Organization Specific OAMPDUs
received on this interface. received on this interface.
An Organization Specific OAMPDU is indicated by a valid frame
with (1) destination MAC address equal to that of the reserved
MAC address for Slow Protocols (See 43B of [802.3ah]), (2) a
lengthOrType field equal to the reserved type for Slow
EFM OAM MIB March 2005
Protocols, (3) a Slow Protocols subtype equal to that of the
subtype reserved for OAM, and (4) an OAMPDU code equals the
OAM Organization Specific code.
Discontinuities of this counter can occur at re-initialization Discontinuities of this counter can occur at re-initialization
of the management system, and at other times as indicated by of the management system, and at other times as indicated by
the value of the ifCounterDiscontinuityTime. " the value of the ifCounterDiscontinuityTime.
"
REFERENCE "[802.3ah], 30.3.6.1.33." REFERENCE "[802.3ah], 30.3.6.1.33."
::= { dot3OamStatsEntry 14 } ::= { dot3OamStatsEntry 14 }
dot3OamUnsupportedCodesTx OBJECT-TYPE dot3OamUnsupportedCodesTx OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
UNITS "frames" UNITS "frames"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A count of the number of OAMPDUs transmitted on this "A count of the number of OAMPDUs transmitted on this
interface with an unsupported op-code. interface with an unsupported op-code.
An unsupported opcode OAMPDU is indicated by a valid frame
with (1) destination MAC address equal to that of the reserved
MAC address for Slow Protocols (See 43B of [802.3ah]), (2) a
lengthOrType field equal to the reserved type for Slow
Protocols, (3) a Slow Protocols subtype equal to that of the
subtype reserved for OAM, and (4) an OAMPDU code equals the
opcode for a function that is not supported by the device.
Discontinuities of this counter can occur at re-initialization Discontinuities of this counter can occur at re-initialization
of the management system, and at other times as indicated by of the management system, and at other times as indicated by
the value of the ifCounterDiscontinuityTime. " the value of the ifCounterDiscontinuityTime.
"
REFERENCE "[802.3ah], 30.3.6.1.18." REFERENCE "[802.3ah], 30.3.6.1.18."
::= { dot3OamStatsEntry 15 } ::= { dot3OamStatsEntry 15 }
dot3OamUnsupportedCodesRx OBJECT-TYPE dot3OamUnsupportedCodesRx OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
UNITS "frames" UNITS "frames"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
Ethernet OAM MIB March 2006
"A count of the number of OAMPDUs received on this interface "A count of the number of OAMPDUs received on this interface
with an unsupported op-code. with an unsupported op-code.
An unsupported opcode OAMPDU is indicated by a valid frame
with (1) destination MAC address equal to that of the reserved
MAC address for Slow Protocols (See 43B of [802.3ah]), (2) a
lengthOrType field equal to the reserved type for Slow
Protocols, (3) a Slow Protocols subtype equal to that of the
subtype reserved for OAM, and (4) an OAMPDU code equals the
opcode for a function that is not supported by the device.
EFM OAM MIB March 2005
Discontinuities of this counter can occur at re-initialization Discontinuities of this counter can occur at re-initialization
of the management system, and at other times as indicated by of the management system, and at other times as indicated by
the value of the ifCounterDiscontinuityTime. " the value of the ifCounterDiscontinuityTime.
"
REFERENCE "[802.3ah], 30.3.6.1.19." REFERENCE "[802.3ah], 30.3.6.1.19."
::= { dot3OamStatsEntry 16 } ::= { dot3OamStatsEntry 16 }
dot3OamFramesLostDueToOam OBJECT-TYPE dot3OamFramesLostDueToOam OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
UNITS "frames" UNITS "frames"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A count of the number of frames that were dropped by the OAM "A count of the number of frames that were dropped by the OAM
multiplexer. Since the OAM mulitplexer has multiple inputs multiplexer. Since the OAM multiplexer has multiple inputs
and a single output, there may be cases where frames are and a single output, there may be cases where frames are
dropped due to transmit resource contention. This counter is dropped due to transmit resource contention. This counter is
incremented whenever a frame is dropped by the OAM layer. incremented whenever a frame is dropped by the OAM layer.
Note that any Ethernet frame, not just OAMPDUs, may be dropped
by the OAM layer. This can occur when an OAMPDU takes
precedence over a 'normal' frame resulting in the 'normal'
frame being dropped.
When this counter is incremented, no other counters in this When this counter is incremented, no other counters in this
MIB are incremented. MIB are incremented.
Discontinuities of this counter can occur at re-initialization Discontinuities of this counter can occur at re-initialization
of the management system, and at other times as indicated by of the management system, and at other times as indicated by
the value of the ifCounterDiscontinuityTime. " the value of the ifCounterDiscontinuityTime.
"
REFERENCE "[802.3ah], 30.3.6.1.46." REFERENCE "[802.3ah], 30.3.6.1.46."
::= { dot3OamStatsEntry 17 } ::= { dot3OamStatsEntry 17 }
------------------------------------------------------------------ -- ***************************************************************
-- --
-- Ethernet OAM Event Configuration group -- Ethernet OAM Event Configuration group
-- --
dot3OamEventConfigTable OBJECT-TYPE dot3OamEventConfigTable OBJECT-TYPE
SYNTAX SEQUENCE OF Dot3OamEventConfigEntry SYNTAX SEQUENCE OF Dot3OamEventConfigEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Ethernet OAM includes the ability to generate and receive "Ethernet OAM includes the ability to generate and receive
event notifications to indicate various link problems. This Ethernet OAM MIB March 2006
table contains the mechanisms to configure the thresholds to
generate the standard Ethernet OAM events.
These events are: Event Notification OAMPDUs to indicate various link problems.
This table contains the mechanisms to enable Event
Notifications and configure the thresholds to generate the
standard Ethernet OAM events. There is one entry in the table
for every entry in dot3OamTable that supports OAM events
(where dot3OamFunctionsSupported includes the eventSupport
bit set). The values in the table are maintained across
changes to dot3OamOperStatus.
The standard threshold crossing events are:
- Errored Symbol Period Event. Generated when the number of - Errored Symbol Period Event. Generated when the number of
symbol errors exceeds a threshold within a given window symbol errors exceeds a threshold within a given window
defined by a number of symbols (e.g. 1,000 symbols out of defined by a number of symbols (for example, 1,000 symbols
1,000,000 had errors). out of 1,000,000 had errors).
EFM OAM MIB March 2005
- Errored Frame Period Event. Generated when the number of - Errored Frame Period Event. Generated when the number of
frame errors exceeds a threshold within a given window frame errors exceeds a threshold within a given window
defined by a number of frames (e.g. 10 frames out of 1000 defined by a number of frames (for example, 10 frames out
had errors). of 1000 had errors).
- Errored Frame Event. Generated when the number of frame - Errored Frame Event. Generated when the number of frame
errors exceeds a threshold within a given window defined errors exceeds a threshold within a given window defined
by a period of time (e.g. 10 frames in 1 second had by a period of time (for example, 10 frames in 1 second
errors). had errors).
- Errored Frame Seconds Summary Event. Generated when the - Errored Frame Seconds Summary Event. Generated when the
number of errored frame seconds exceeds a threshold within number of errored frame seconds exceeds a threshold within
a given time period (e.g. 10 errored frame seconds within a given time period (for example, 10 errored frame seconds
the last 100 seconds). An errored frame second is defined within the last 100 seconds). An errored frame second is
as a 1 second interval which had >0 frame errors. defined as a 1 second interval which had >0 frame errors.
There are other events (dying gasp, critical events) that are
not threshold crossing events but which can be
enabled/disabled via this table.
" "
::= { dot3OamMIB 5 } ::= { dot3OamObjects 5 }
dot3OamEventConfigEntry OBJECT-TYPE dot3OamEventConfigEntry OBJECT-TYPE
SYNTAX Dot3OamEventConfigEntry SYNTAX Dot3OamEventConfigEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Event configuration information is available for every "Entries are automatically created and deleted from this
Ethernet like interface that supports OAM and the event table, and exist whenever the OAM entity supports Ethernet OAM
function of OAM as indicated in the dot3OamFunctionsSupported events (as indicated by the eventSupport bit in
attribute. dot3OamFunctionsSuppported). Values in the table are
maintained across changes to the value of dot3OamOperStatus.
Event configuration controls when the local management entity Event configuration controls when the local management entity
sends Event Notification OAMPDUs to its OAM peer. " sends Event Notification OAMPDUs to its OAM peer, and when
certain event flags are set or cleared in OAMPDUs.
"
INDEX { ifIndex } INDEX { ifIndex }
Ethernet OAM MIB March 2006
::= { dot3OamEventConfigTable 1 } ::= { dot3OamEventConfigTable 1 }
Dot3OamEventConfigEntry ::= Dot3OamEventConfigEntry ::=
SEQUENCE { SEQUENCE {
dot3OamErrSymPeriodWindowHi Unsigned32, dot3OamErrSymPeriodWindowHi Unsigned32,
dot3OamErrSymPeriodWindowLo Unsigned32, dot3OamErrSymPeriodWindowLo Unsigned32,
dot3OamErrSymPeriodThresholdHi Unsigned32, dot3OamErrSymPeriodThresholdHi Unsigned32,
dot3OamErrSymPeriodThresholdLo Unsigned32, dot3OamErrSymPeriodThresholdLo Unsigned32,
dot3OamErrSymPeriodEvNotifEnable INTEGER, dot3OamErrSymPeriodEvNotifEnable TruthValue,
dot3OamErrFramePeriodWindow Unsigned32, dot3OamErrFramePeriodWindow Unsigned32,
dot3OamErrFramePeriodThreshold Unsigned32, dot3OamErrFramePeriodThreshold Unsigned32,
dot3OamErrFramePeriodEvNotifEnable INTEGER, dot3OamErrFramePeriodEvNotifEnable TruthValue,
dot3OamErrFrameWindow Unsigned32, dot3OamErrFrameWindow Unsigned32,
dot3OamErrFrameThreshold Unsigned32, dot3OamErrFrameThreshold Unsigned32,
dot3OamErrFrameEvNotifEnable INTEGER, dot3OamErrFrameEvNotifEnable TruthValue,
dot3OamErrFrameSecsSummaryWindow Integer32, dot3OamErrFrameSecsSummaryWindow Integer32,
dot3OamErrFrameSecsSummaryThreshold Integer32, dot3OamErrFrameSecsSummaryThreshold Integer32,
dot3OamErrFrameSecsEvNotifEnable INTEGER, dot3OamErrFrameSecsEvNotifEnable TruthValue,
dot3OamDyingGaspEnable INTEGER, dot3OamDyingGaspEnable TruthValue,
dot3OamCriticalEventEnable INTEGER dot3OamCriticalEventEnable TruthValue
EFM OAM MIB March 2005
} }
dot3OamErrSymPeriodWindowHi OBJECT-TYPE dot3OamErrSymPeriodWindowHi OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
UNITS "2^32 symbols" UNITS "2^32 symbols"
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The two objects dot3OamErrSymPeriodWindowHi and "The two objects dot3OamErrSymPeriodWindowHi and
dot3OamErrSymPeriodLo together form an unsigned 64-bit dot3OamErrSymPeriodLo together form an unsigned 64-bit
skipping to change at page 34, line 29 skipping to change at page 32, line 49
dot3OamErrSymPeriodWindow = ((2^32)*dot3OamErrSymPeriodWindowHi) dot3OamErrSymPeriodWindow = ((2^32)*dot3OamErrSymPeriodWindowHi)
+ dot3OamErrSymPeriodWindowLo + dot3OamErrSymPeriodWindowLo
If dot3OamErrSymPeriodThreshold symbol errors occur within a If dot3OamErrSymPeriodThreshold symbol errors occur within a
window of dot3OamErrSymPeriodWindow symbols, an Event window of dot3OamErrSymPeriodWindow symbols, an Event
Notification OAMPDU should be generated with an Errored Symbol Notification OAMPDU should be generated with an Errored Symbol
Period Event TLV indicating the threshold has been crossed in Period Event TLV indicating the threshold has been crossed in
this window. this window.
The default value for dot3OamErrSymPeriodWindow is the number The default value for dot3OamErrSymPeriodWindow is the number
of symbols in one second for the underlying physical layer." of symbols in one second for the underlying physical layer.
"
REFERENCE "[802.3ah], 30.3.6.1.34" REFERENCE "[802.3ah], 30.3.6.1.34"
::= { dot3OamEventConfigEntry 1 } ::= { dot3OamEventConfigEntry 1 }
dot3OamErrSymPeriodWindowLo OBJECT-TYPE dot3OamErrSymPeriodWindowLo OBJECT-TYPE
Ethernet OAM MIB March 2006
SYNTAX Unsigned32 SYNTAX Unsigned32
UNITS "symbols" UNITS "symbols"
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The two objects dot3OamErrSymPeriodWindowHi and "The two objects dot3OamErrSymPeriodWindowHi and
dot3OamErrSymPeriodWindowLo together form an unsigned 64-bit dot3OamErrSymPeriodWindowLo together form an unsigned 64-bit
integer representing the number of symbols over which this integer representing the number of symbols over which this
threshold event is defined. This is defined as threshold event is defined. This is defined as
dot3OamErrSymPeriodWindow = ((2^32)*dot3OamErrSymPeriodWindowHi) dot3OamErrSymPeriodWindow = ((2^32)*dot3OamErrSymPeriodWindowHi)
+ dot3OamErrSymPeriodWindowLo + dot3OamErrSymPeriodWindowLo
If dot3OamErrSymPeriodThreshold symbol errors occur within a If dot3OamErrSymPeriodThreshold symbol errors occur within a
window of dot3OamErrSymPeriodWindow symbols, an Event window of dot3OamErrSymPeriodWindow symbols, an Event
Notification OAMPDU should be generated with an Errored Symbol Notification OAMPDU should be generated with an Errored Symbol
Period Event TLV indicating the threshold has been crossed in Period Event TLV indicating the threshold has been crossed in
this window. this window.
The default value for dot3OamErrSymPeriodWindow is the number The default value for dot3OamErrSymPeriodWindow is the number
of symbols in one second for the underlying physical layer. " of symbols in one second for the underlying physical layer.
EFM OAM MIB March 2005 "
REFERENCE "[802.3ah], 30.3.6.1.34" REFERENCE "[802.3ah], 30.3.6.1.34"
::= { dot3OamEventConfigEntry 2 } ::= { dot3OamEventConfigEntry 2 }
dot3OamErrSymPeriodThresholdHi OBJECT-TYPE dot3OamErrSymPeriodThresholdHi OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
UNITS "2^32 symbols" UNITS "2^32 symbols"
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The two objects dot3OamErrSymPeriodThresholdHi and "The two objects dot3OamErrSymPeriodThresholdHi and
skipping to change at page 35, line 33 skipping to change at page 34, line 4
((2^32) * dot3OamErrSymPeriodThresholdHi) ((2^32) * dot3OamErrSymPeriodThresholdHi)
+ dot3OamErrSymPeriodThresholdLo + dot3OamErrSymPeriodThresholdLo
If dot3OamErrSymPeriodThreshold symbol errors occur within a If dot3OamErrSymPeriodThreshold symbol errors occur within a
window of dot3OamErrSymPeriodWindow symbols, an Event window of dot3OamErrSymPeriodWindow symbols, an Event
Notification OAMPDU should be generated with an Errored Symbol Notification OAMPDU should be generated with an Errored Symbol
Period Event TLV indicating the threshold has been crossed in Period Event TLV indicating the threshold has been crossed in
this window. this window.
The default value for dot3OamErrSymPeriodThreshold is one The default value for dot3OamErrSymPeriodThreshold is one
symbol errors. " Ethernet OAM MIB March 2006
symbol errors. If the threshold value is zero, then an Event
Notification OAMPDU is sent periodically (at the end of every
window). This can be used as an asynchronous notification to
the peer OAM entity of the statistics related to this
threshold crossing alarm.
"
REFERENCE "[802.3ah], 30.3.6.1.34" REFERENCE "[802.3ah], 30.3.6.1.34"
::= { dot3OamEventConfigEntry 3 } ::= { dot3OamEventConfigEntry 3 }
dot3OamErrSymPeriodThresholdLo OBJECT-TYPE dot3OamErrSymPeriodThresholdLo OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
UNITS "symbols" UNITS "symbols"
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The two objects dot3OamErrSymPeriodThresholdHi and "The two objects dot3OamErrSymPeriodThresholdHi and
dot3OamErrSymPeriodThresholdLo together form an unsigned dot3OamErrSymPeriodThresholdLo together form an unsigned
64-bit integer representing the number of symbol errors that 64-bit integer representing the number of symbol errors that
must occur within a given window to cause this event. must occur within a given window to cause this event.
This is defined as This is defined as
dot3OamErrSymPeriodThreshold = dot3OamErrSymPeriodThreshold =
((2^32) * dot3OamErrSymPeriodThresholdHi) ((2^32) * dot3OamErrSymPeriodThresholdHi)
+ dot3OamErrSymPeriodThresholdLo + dot3OamErrSymPeriodThresholdLo
EFM OAM MIB March 2005
If dot3OamErrSymPeriodThreshold symbol errors occur within a If dot3OamErrSymPeriodThreshold symbol errors occur within a
window of dot3OamErrSymPeriodWindow symbols, an Event window of dot3OamErrSymPeriodWindow symbols, an Event
Notification OAMPDU should be generated with an Errored Symbol Notification OAMPDU should be generated with an Errored Symbol
Period Event TLV indicating the threshold has been crossed in Period Event TLV indicating the threshold has been crossed in
this window. this window.
The default value for dot3OamErrSymPeriodThreshold is one The default value for dot3OamErrSymPeriodThreshold is one
symbol error. " symbol error. If the threshold value is zero, then an Event
Notification OAMPDU is sent periodically (at the end of every
window). This can be used as an asynchronous notification to
the peer OAM entity of the statistics related to this
threshold crossing alarm.
"
REFERENCE "[802.3ah], 30.3.6.1.34" REFERENCE "[802.3ah], 30.3.6.1.34"
::= { dot3OamEventConfigEntry 4 } ::= { dot3OamEventConfigEntry 4 }
dot3OamErrSymPeriodEvNotifEnable OBJECT-TYPE dot3OamErrSymPeriodEvNotifEnable OBJECT-TYPE
SYNTAX INTEGER { enabled(1), disabled(2) } SYNTAX TruthValue
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Indicates whether the occurence of Errored Symbol Period "If true, the OAM entity should send an Event Notification
Events should result in Event Notification OAMPDUs generated OAMPDU when an Errored Symbol Period Event occurs.
by the OAM layer.
By default, this object should have the value enabled(1) for Ethernet OAM MIB March 2006
By default, this object should have the value true for
Ethernet like interfaces that support OAM. If the OAM layer Ethernet like interfaces that support OAM. If the OAM layer
does not support event notifications (as indicated via the does not support event notifications (as indicated via the
dot3OamFunctionsSupported attribute), this value is ignored. dot3OamFunctionsSupported attribute), this value is ignored.
" "
::= { dot3OamEventConfigEntry 5 } ::= { dot3OamEventConfigEntry 5 }
dot3OamErrFramePeriodWindow OBJECT-TYPE dot3OamErrFramePeriodWindow OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
UNITS "frames" UNITS "frames"
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of frames over which the threshold is defined. "The number of frames over which the threshold is defined.
The The default value of the window is the number of minimum size
default value of the window is the number of minimum size
Ethernet frames that can be received over the physical layer Ethernet frames that can be received over the physical layer
in in one second.
one second.
If dot3OamErrFramePeriodThreshold frame errors occur within a If dot3OamErrFramePeriodThreshold frame errors occur within a
window of dot3OamErrFramePeriodWindow frames, an Event window of dot3OamErrFramePeriodWindow frames, an Event
Notification OAMPDU should be generated with an Errored Frame Notification OAMPDU should be generated with an Errored Frame
Period Event TLV indicating the threshold has been crossed in Period Event TLV indicating the threshold has been crossed in
this window. " this window.
"
REFERENCE "[802.3ah], 30.3.6.1.38" REFERENCE "[802.3ah], 30.3.6.1.38"
::= { dot3OamEventConfigEntry 6 } ::= { dot3OamEventConfigEntry 6 }
EFM OAM MIB March 2005
dot3OamErrFramePeriodThreshold OBJECT-TYPE dot3OamErrFramePeriodThreshold OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
UNITS "frames" UNITS "frames"
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of frame errors that must occur for this event to "The number of frame errors that must occur for this event to
be triggered. The default value is one frame error. be triggered. The default value is one frame error. If the
threshold value is zero, then an Event Notification OAMPDU is
sent periodically (at the end of every window). This can be
used as an asynchronous notification to the peer OAM entity of
the statistics related to this threshold crossing alarm.
If dot3OamErrFramePeriodThreshold frame errors occur within a If dot3OamErrFramePeriodThreshold frame errors occur within a
window of dot3OamErrFramePeriodWindow frames, an Event window of dot3OamErrFramePeriodWindow frames, an Event
Notification OAMPDU should be generated with an Errored Frame Notification OAMPDU should be generated with an Errored Frame
Period Event TLV indicating the threshold has been crossed in Period Event TLV indicating the threshold has been crossed in
this window. " this window.
"
REFERENCE "[802.3ah], 30.3.6.1.38" REFERENCE "[802.3ah], 30.3.6.1.38"
::= { dot3OamEventConfigEntry 7 } ::= { dot3OamEventConfigEntry 7 }
Ethernet OAM MIB March 2006
dot3OamErrFramePeriodEvNotifEnable OBJECT-TYPE dot3OamErrFramePeriodEvNotifEnable OBJECT-TYPE
SYNTAX INTEGER { enabled(1), disabled(2) } SYNTAX TruthValue
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Indicates whether the occurence of an Errored Frame Period "If true, the OAM entity should send an Event Notification
Event should result in an Event Notification OAMPDU generated OAMPDU when an Errored Frame Period Event occurs.
by the OAM layer.
By default, this object should have the value enabled(1) for By default, this object should have the value true for
Ethernet like interfaces that support OAM. If the OAM layer Ethernet like interfaces that support OAM. If the OAM layer
does not support event notifications (as indicated via the does not support event notifications (as indicated via the
dot3OamFunctionsSupported attribute), this value is ignored. " dot3OamFunctionsSupported attribute), this value is ignored.
"
::= { dot3OamEventConfigEntry 8 } ::= { dot3OamEventConfigEntry 8 }
dot3OamErrFrameWindow OBJECT-TYPE dot3OamErrFrameWindow OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
UNITS "tenths of a second" UNITS "tenths of a second"
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The amount of time (in 100ms increments) over which the "The amount of time (in 100ms increments) over which the
threshold is defined. The default value is 10 (1 second). threshold is defined. The default value is 10 (1 second).
If dot3OamErrFrameThreshold frame errors occur within a window If dot3OamErrFrameThreshold frame errors occur within a window
of dot3OamErrFrameWindow seconds (measured in tenths of of dot3OamErrFrameWindow seconds (measured in tenths of
seconds), an Event Notification OAMPDU should be generated with seconds), an Event Notification OAMPDU should be generated
an Errored Frame Event TLV indicating the threshold has been with an Errored Frame Event TLV indicating the threshold has
crossed in this window. " been crossed in this window.
"
REFERENCE "[802.3ah], 30.3.6.1.36" REFERENCE "[802.3ah], 30.3.6.1.36"
::= { dot3OamEventConfigEntry 9 } ::= { dot3OamEventConfigEntry 9 }
EFM OAM MIB March 2005
dot3OamErrFrameThreshold OBJECT-TYPE dot3OamErrFrameThreshold OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
UNITS "frames" UNITS "frames"
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of frame errors that must occur for this event to "The number of frame errors that must occur for this event to
be triggered. The default value is one frame error. be triggered. The default value is one frame error. If the
threshold value is zero, then an Event Notification OAMPDU is
sent periodically (at the end of every window). This can be
used as an asynchronous notification to the peer OAM entity of
the statistics related to this threshold crossing alarm.
If dot3OamErrFrameThreshold frame errors occur within a window If dot3OamErrFrameThreshold frame errors occur within a window
Ethernet OAM MIB March 2006
of dot3OamErrFrameWindow (in tenths of seconds), an Event of dot3OamErrFrameWindow (in tenths of seconds), an Event
Notification OAMPDU should be generated with an Errored Frame Notification OAMPDU should be generated with an Errored Frame
Event TLV indicating the threshold has been crossed in this Event TLV indicating the threshold has been crossed in this
window. " window.
"
REFERENCE "[802.3ah], 30.3.6.1.36" REFERENCE "[802.3ah], 30.3.6.1.36"
::= { dot3OamEventConfigEntry 10 } ::= { dot3OamEventConfigEntry 10 }
dot3OamErrFrameEvNotifEnable OBJECT-TYPE dot3OamErrFrameEvNotifEnable OBJECT-TYPE
SYNTAX INTEGER { enabled(1), disabled(2) } SYNTAX TruthValue
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Indicates whether the occurence of an Errored Frame Event "If true, the OAM entity should send an Event Notification
should result in an Event Notification OAMPDU generated by the OAMPDU when an Errored Frame Event occurs.
OAM layer.
By default, this object should have the value enabled(1) for By default, this object should have the value true for
Ethernet like interfaces that support OAM. If the OAM layer Ethernet like interfaces that support OAM. If the OAM layer
does not support event notifications (as indicated via the does not support event notifications (as indicated via the
dot3OamFunctionsSupported attribute), this value is ignored. " dot3OamFunctionsSupported attribute), this value is ignored.
"
::= { dot3OamEventConfigEntry 11 } ::= { dot3OamEventConfigEntry 11 }
dot3OamErrFrameSecsSummaryWindow OBJECT-TYPE dot3OamErrFrameSecsSummaryWindow OBJECT-TYPE
SYNTAX Integer32 (100..9000) SYNTAX Integer32 (100..9000)
UNITS "tenths of a second" UNITS "tenths of a second"
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The amount of time (in 100ms intervals) over which the "The amount of time (in 100ms intervals) over which the
threshold is defined. The default value is 100 (10 seconds). threshold is defined. The default value is 100 (10 seconds).
If dot3OamErrFrameSecsSummaryThreshold frame errors occur If dot3OamErrFrameSecsSummaryThreshold frame errors occur
within a window of dot3OamErrFrameSecsSummaryWindow (in tenths within a window of dot3OamErrFrameSecsSummaryWindow (in tenths
of seconds), an Event Notification OAMPDU should be generated of seconds), an Event Notification OAMPDU should be generated
with an Errored Frame Seconds Summary Event TLV indicating the with an Errored Frame Seconds Summary Event TLV indicating the
threshold has been crossed in this window. " threshold has been crossed in this window.
"
REFERENCE "[802.3ah], 30.3.6.1.40" REFERENCE "[802.3ah], 30.3.6.1.40"
::= { dot3OamEventConfigEntry 12 } ::= { dot3OamEventConfigEntry 12 }
EFM OAM MIB March 2005
dot3OamErrFrameSecsSummaryThreshold OBJECT-TYPE dot3OamErrFrameSecsSummaryThreshold OBJECT-TYPE
SYNTAX Integer32 (1..900) SYNTAX Integer32 (1..900)
UNITS "errored frame seconds" UNITS "errored frame seconds"
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of errored frame seconds that must occur for this "The number of errored frame seconds that must occur for this
event to be triggered. The default value is one errored frame event to be triggered. The default value is one errored frame
second. Ethernet OAM MIB March 2006
second. If the threshold value is zero, then an Event
Notification OAMPDU is sent periodically (at the end of every
window). This can be used as an asynchronous notification to
the peer OAM entity of the statistics related to this
threshold crossing alarm.
If dot3OamErrFrameSecsSummaryThreshold frame errors occur If dot3OamErrFrameSecsSummaryThreshold frame errors occur
within a window of dot3OamErrFrameSecsSummaryWindow (in tenths within a window of dot3OamErrFrameSecsSummaryWindow (in tenths
of seconds), an Event Notification OAMPDU should be generated of seconds), an Event Notification OAMPDU should be generated
with an Errored Frame Seconds Summary Event TLV indicating the with an Errored Frame Seconds Summary Event TLV indicating the
threshold has been crossed in this window. " threshold has been crossed in this window.
"
REFERENCE "[802.3ah], 30.3.6.1.40" REFERENCE "[802.3ah], 30.3.6.1.40"
::= { dot3OamEventConfigEntry 13 } ::= { dot3OamEventConfigEntry 13 }
dot3OamErrFrameSecsEvNotifEnable OBJECT-TYPE dot3OamErrFrameSecsEvNotifEnable OBJECT-TYPE
SYNTAX INTEGER { enabled(1), disabled(2) } SYNTAX TruthValue
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Indicates whether the occurence of an Errored Frame Seconds "If true, the local OAM entity should send an Event
Summary Event should result in an Event Notification OAMPDU Notification OAMPDU when an Errored Frame Seconds Event
generated by the OAM layer. occurs.
By default, this object should have the value enabled(1) for By default, this object should have the value true for
Ethernet like interfaces that support OAM. If the OAM layer Ethernet like interfaces that support OAM. If the OAM layer
does not support event notifications (as indicated via the does not support event notifications (as indicated via the
dot3OamFunctionsSupported attribute), this value is ignored." dot3OamFunctionsSupported attribute), this value is ignored.
"
::= { dot3OamEventConfigEntry 14 } ::= { dot3OamEventConfigEntry 14 }
dot3OamDyingGaspEnable OBJECT-TYPE dot3OamDyingGaspEnable OBJECT-TYPE
SYNTAX INTEGER { enabled(1), disabled(2) } SYNTAX TruthValue
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Indicates whether the local device should attempt to indicate "If true, the local OAM entity should attempt to indicate a
a dying gasp fault via the OAMPDU flags field to its peer OAM dying gasp via the OAMPDU flags field to its peer OAM entity
entity. If the system does not support dying gasp capability, when a dying gasp event occurs. The exact definition of a
setting this object has no effect, and reading the object dying gasp event is implementation dependent. If the system
should always result in 'disabled(2)'. does not support dying gasp capability, setting this object
has no effect, and reading the object should always result in
'false'.
By default, this object should have the value enabled(1) for By default, this object should have the value true for
Ethernet like interfaces that support OAM. If the OAM layer Ethernet like interfaces that support OAM. If the OAM layer
does not support event notifications (as indicated via the does not support event notifications (as indicated via the
dot3OamFunctionsSupported attribute), this value is ignored." dot3OamFunctionsSupported attribute), this value is ignored.
EFM OAM MIB March 2005 "
Ethernet OAM MIB March 2006
::= { dot3OamEventConfigEntry 15 } ::= { dot3OamEventConfigEntry 15 }
dot3OamCriticalEventEnable OBJECT-TYPE dot3OamCriticalEventEnable OBJECT-TYPE
SYNTAX INTEGER { enabled(1), disabled(2) } SYNTAX TruthValue
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Indicates whether the local device should attempt to indicate "If true, the local OAM entity should attempt to indicate a
a critical event fault via the OAMPDU flags field to its peer critical event via the OAMPDU flags to its peer OAM entity
OAM entity. If the system does not support critical event when a critical event occurs. The exact definition of a
capability, setting this object has no effect, and reading the critical event is implementation dependent. If the system
object should always result in 'disabled(2)'. does not support critical event capability, setting this
object has no effect, and reading the object should always
result in 'false'.
By default, this object should have the value enabled(1) for By default, this object should have the value true for
Ethernet like interfaces that support OAM. If the OAM layer Ethernet like interfaces that support OAM. If the OAM layer
does not support event notifications (as indicated via the does not support event notifications (as indicated via the
dot3OamFunctionsSupported attribute), this value is ignored." dot3OamFunctionsSupported attribute), this value is ignored.
"
::= { dot3OamEventConfigEntry 16 } ::= { dot3OamEventConfigEntry 16 }
------------------------------------------------------------------ -- **************************************************************
-- --
-- Ethernet OAM Event Status group -- Ethernet OAM Event Log group
-- --
dot3OamEventLogTable OBJECT-TYPE dot3OamEventLogTable OBJECT-TYPE
SYNTAX SEQUENCE OF Dot3OamEventLogEntry SYNTAX SEQUENCE OF Dot3OamEventLogEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table records a history of the events that have occurred "This table records a history of the events that have occurred
at the Ethernet OAM level. These events can include locally at the Ethernet OAM level. These events can include locally
detected events, which may result in locally generated detected events, which may result in locally generated
OAMPDUs, and remotely detected events, which are detected by OAMPDUs, and remotely detected events, which are detected by
the OAM peer entity and signaled to the local entity via the OAM peer entity and signaled to the local entity via
Ethernet OAM. Ethernet OAM events can be signaled by Event Ethernet OAM. Ethernet OAM events can be signaled by Event
Notification OAMPDUs or by the flags field in any OAMPDU. " Notification OAMPDUs or by the flags field in any OAMPDU.
::= { dot3OamMIB 6 }
This table contains both threshold crossing events and
non-threshold crossing events. The parameters for the
threshold window, threshold value, and actual value
(dot3OamEventLogWindowXX, dot3OamEventLogThresholdXX,
dot3OamEventLogValue) are only applicable to threshold
crossing events, and are returned as all F's (2^32 - 1) for
non-threshold crossing events.
Ethernet OAM MIB March 2006
Entries in the table are automatically created when such
events are detected. The size of the table is implementation
dependent. When the table reaches its maximum size, older
entries are automatically deleted to make room for newer
entries.
"
::= { dot3OamObjects 6 }
dot3OamEventLogEntry OBJECT-TYPE dot3OamEventLogEntry OBJECT-TYPE
SYNTAX Dot3OamEventLogEntry SYNTAX Dot3OamEventLogEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION "An entry in the dot3OamEventLogTable." DESCRIPTION
"An entry in the dot3OamEventLogTable. Entries are
automatically created whenever Ethernet OAM events occur at
the local OAM entity, and when Event Notification OAMPDUs are
received at the local OAM entity (indicating events have
occurred at the peer OAM entity). The size of the table is
implementation dependent, but when the table becomes full,
older events are automatically deleted to make room for newer
events. The table index dot3OamEventLogIndex increments for
each new entry, and when the maximum value is reached the
value restarts at zero.
"
INDEX { ifIndex, dot3OamEventLogIndex } INDEX { ifIndex, dot3OamEventLogIndex }
::= { dot3OamEventLogTable 1 } ::= { dot3OamEventLogTable 1 }
Dot3OamEventLogEntry ::= Dot3OamEventLogEntry ::=
SEQUENCE { SEQUENCE {
EFM OAM MIB March 2005
dot3OamEventLogIndex Unsigned32, dot3OamEventLogIndex Unsigned32,
dot3OamEventLogTimestamp TimeStamp, dot3OamEventLogTimestamp TimeStamp,
dot3OamEventLogOui Dot3Oui, dot3OamEventLogOui Dot3Oui,
dot3OamEventLogType Unsigned32, dot3OamEventLogType Unsigned32,
dot3OamEventLogLocation INTEGER, dot3OamEventLogLocation INTEGER,
dot3OamEventLogWindowHi Unsigned32, dot3OamEventLogWindowHi Unsigned32,
dot3OamEventLogWindowLo Unsigned32, dot3OamEventLogWindowLo Unsigned32,
dot3OamEventLogThresholdHi Unsigned32, dot3OamEventLogThresholdHi Unsigned32,
dot3OamEventLogThresholdLo Unsigned32, dot3OamEventLogThresholdLo Unsigned32,
dot3OamEventLogValue CounterBasedGauge64, dot3OamEventLogValue CounterBasedGauge64,
dot3OamEventLogRunningTotal CounterBasedGauge64, dot3OamEventLogRunningTotal CounterBasedGauge64,
dot3OamEventLogEventTotal Unsigned32 dot3OamEventLogEventTotal Unsigned32
} }
dot3OamEventLogIndex OBJECT-TYPE dot3OamEventLogIndex OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An arbitrary integer for identifiying individual events Ethernet OAM MIB March 2006
"An arbitrary integer for identifying individual events
within the event log. " within the event log. "
::= { dot3OamEventLogEntry 1 } ::= { dot3OamEventLogEntry 1 }
dot3OamEventLogTimestamp OBJECT-TYPE dot3OamEventLogTimestamp OBJECT-TYPE
SYNTAX TimeStamp SYNTAX TimeStamp
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The value of sysUpTime at the time of the logged event. For "The value of sysUpTime at the time of the logged event. For
locally generated events, the time of the event can be locally generated events, the time of the event can be
skipping to change at page 42, line 4 skipping to change at page 41, line 36
::= { dot3OamEventLogEntry 2 } ::= { dot3OamEventLogEntry 2 }
dot3OamEventLogOui OBJECT-TYPE dot3OamEventLogOui OBJECT-TYPE
SYNTAX Dot3Oui SYNTAX Dot3Oui
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The OUI of the entity defining the object type. All IEEE "The OUI of the entity defining the object type. All IEEE
802.3 defined events (as appearing in [802.3ah] except for the 802.3 defined events (as appearing in [802.3ah] except for the
Organizationally Unique Event TLVs) use the IEEE 802.3 OUI of Organizationally Unique Event TLVs) use the IEEE 802.3 OUI of
EFM OAM MIB March 2005
0x0180C2. Organizations defining their own Event Notification 0x0180C2. Organizations defining their own Event Notification
TLVs include their OUI in the Event Notification TLV which TLVs include their OUI in the Event Notification TLV which
gets reflected here. " gets reflected here. "
::= { dot3OamEventLogEntry 3 } ::= { dot3OamEventLogEntry 3 }
dot3OamEventLogType OBJECT-TYPE dot3OamEventLogType OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The type of event that generated this entry in the event log. "The type of event that generated this entry in the event log.
When the OUI is the IEEE 802.3 OUI of 0x0180C2, the following When the OUI is the IEEE 802.3 OUI of 0x0180C2, the following
event types are defined: event types are defined:
erroredSymbolEvent(1), erroredSymbolEvent(1),
erroredFramePeriodEvent (2), erroredFramePeriodEvent (2),
erroredFrameEvent(3), erroredFrameEvent(3),
erroredFrameSecondsEvent(4), erroredFrameSecondsEvent(4),
Ethernet OAM MIB March 2006
linkFault(256), linkFault(256),
dyingGaspEvent(257), dyingGaspEvent(257),
criticalLinkEvent(258) criticalLinkEvent(258)
The first four are considered threshold crossing events as The first four are considered threshold crossing events as
they are generated when a metric exceeds a given value within they are generated when a metric exceeds a given value within
a specified window. The other three are not threshold a specified window. The other three are not threshold
crossing events. crossing events.
When the OUI is not 0x0180C2, then some other organization has When the OUI is not 71874 (0x0180C2 in hex), then some other
defined the event space. If event subtyping is known to the organization has defined the event space. If event subtyping
implementation, it may be reflected here. Otherwise, this is known to the implementation, it may be reflected here.
value should return all Fs (0xFFFFFFFF). Otherwise, this value should return all Fs (2^32 - 1).
" "
REFERENCE "[802.3ah], 30.3.6.1.10 and 57.5.3." REFERENCE "[802.3ah], 30.3.6.1.10 and 57.5.3."
::= { dot3OamEventLogEntry 4 } ::= { dot3OamEventLogEntry 4 }
dot3OamEventLogLocation OBJECT-TYPE dot3OamEventLogLocation OBJECT-TYPE
SYNTAX INTEGER { local(1), remote(2) } SYNTAX INTEGER { local(1), remote(2) }
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Whether this event occurred locally, or was received from the "Whether this event occurred locally (local(1)), or was
OAM peer via Ethernet OAM." received from the OAM peer via Ethernet OAM (remote(2)).
"
::= { dot3OamEventLogEntry 5 } ::= { dot3OamEventLogEntry 5 }
dot3OamEventLogWindowHi OBJECT-TYPE dot3OamEventLogWindowHi OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
EFM OAM MIB March 2005
"If the event represents a threshold crossing event, the two "If the event represents a threshold crossing event, the two
objects dot3OamEventWindowHi and dot3OamEventWindowLo form an objects dot3OamEventWindowHi and dot3OamEventWindowLo form an
unsigned 64-bit integer yielding the window over which the unsigned 64-bit integer yielding the window over which the
value was measured for the threshold crossing event (e.g. 5, value was measured for the threshold crossing event (for
when 11 occurrences happened in 5 seconds while the threshold example, 5, when 11 occurrences happened in 5 seconds while
was 10). The two objects are combined as: the threshold was 10). The two objects are combined as:
dot3OamEventLogWindow = ((2^32) * dot3OamEventLogWindowHi) dot3OamEventLogWindow = ((2^32) * dot3OamEventLogWindowHi)
+ dot3OamEventLogWindowLo + dot3OamEventLogWindowLo
Otherwise, this value is returned as all F's (0xFFFFFFFF) and Otherwise, this value is returned as all F's (2^32 - 1) and
adds no useful information. " adds no useful information.
"
REFERENCE "[802.3ah], 30.3.6.1.37 and 57.5.3.2." REFERENCE "[802.3ah], 30.3.6.1.37 and 57.5.3.2."
::= { dot3OamEventLogEntry 6 } ::= { dot3OamEventLogEntry 6 }
dot3OamEventLogWindowLo OBJECT-TYPE dot3OamEventLogWindowLo OBJECT-TYPE
Ethernet OAM MIB March 2006
SYNTAX Unsigned32 SYNTAX Unsigned32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"If the event represents a threshold crossing event, the two "If the event represents a threshold crossing event, the two
objects dot3OamEventWindowHi and dot3OamEventWindowLo form an objects dot3OamEventWindowHi and dot3OamEventWindowLo form an
unsigned 64-bit integer yielding the window over which the unsigned 64-bit integer yielding the window over which the
value was measured for the threshold crossing event (e.g. 5, value was measured for the threshold crossing event (for
when 11 occurrences happened in 5 seconds while the threshold example, 5, when 11 occurrences happened in 5 seconds while
was 10). The two objects are combined as: the threshold was 10). The two objects are combined as:
dot3OamEventLogWindow = ((2^32) * dot3OamEventLogWindowHi) dot3OamEventLogWindow = ((2^32) * dot3OamEventLogWindowHi)
+ dot3OamEventLogWindowLo + dot3OamEventLogWindowLo
Otherwise, this value is returned as all F's (0xFFFFFFFF) and Otherwise, this value is returned as all F's (2^32 - 1) and
adds no useful information. " adds no useful information.
"
REFERENCE "[802.3ah], 30.3.6.1.37 and 57.5.3.2." REFERENCE "[802.3ah], 30.3.6.1.37 and 57.5.3.2."
::= { dot3OamEventLogEntry 7 } ::= { dot3OamEventLogEntry 7 }
dot3OamEventLogThresholdHi OBJECT-TYPE dot3OamEventLogThresholdHi OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"If the event represents a threshold crossing event, the two "If the event represents a threshold crossing event, the two
objects dot3OamEventThresholdHi and dot3OamEventThresholdLo objects dot3OamEventThresholdHi and dot3OamEventThresholdLo
form an unsigned 64-bit integer yielding the value that was form an unsigned 64-bit integer yielding the value that was
crossed for the threshold crossing event (e.g. 10, when 11 crossed for the threshold crossing event (for example, 10,
occurrences happened in 5 seconds while the threshold was 10). when 11 occurrences happened in 5 seconds while the threshold
The two objects are combined as: was 10). The two objects are combined as:
dot3OamEventLogThreshold = ((2^32) * dot3OamEventLogThresholdHi) dot3OamEventLogThreshold = ((2^32) * dot3OamEventLogThresholdHi)
EFM OAM MIB March 2005
+ dot3OamEventLogThresholdLo + dot3OamEventLogThresholdLo
Otherwise, this value is returned as all F's (0xFFFFFFFF) and Otherwise, this value is returned as all F's (2^32 -1) and
adds no useful information. " adds no useful information.
"
REFERENCE "[802.3ah], 30.3.6.1.37 and 57.5.3.2." REFERENCE "[802.3ah], 30.3.6.1.37 and 57.5.3.2."
::= { dot3OamEventLogEntry 8 } ::= { dot3OamEventLogEntry 8 }
dot3OamEventLogThresholdLo OBJECT-TYPE dot3OamEventLogThresholdLo OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"If the event represents a threshold crossing event, the two "If the event represents a threshold crossing event, the two
objects dot3OamEventThresholdHi and dot3OamEventThresholdLo objects dot3OamEventThresholdHi and dot3OamEventThresholdLo
form an unsigned 64-bit integer yielding the value that was form an unsigned 64-bit integer yielding the value that was
crossed for the threshold crossing event (e.g. 10, when 11 Ethernet OAM MIB March 2006
occurrences happened in 5 seconds while the threshold was 10).
The two objects are combined as: crossed for the threshold crossing event (for example, 10,
when 11 occurrences happened in 5 seconds while the threshold
was 10). The two objects are combined as:
dot3OamEventLogThreshold = ((2^32) * dot3OamEventLogThresholdHi) dot3OamEventLogThreshold = ((2^32) * dot3OamEventLogThresholdHi)
+ dot3OamEventLogThresholdLo + dot3OamEventLogThresholdLo
Otherwise, this value is returned as all F's (0xFFFFFFFF) and Otherwise, this value is returned as all F's (2^32 - 1) and
adds no useful information. " adds no useful information.
"
REFERENCE "[802.3ah], 30.3.6.1.37 and 57.5.3.2." REFERENCE "[802.3ah], 30.3.6.1.37 and 57.5.3.2."
::= { dot3OamEventLogEntry 9 } ::= { dot3OamEventLogEntry 9 }
dot3OamEventLogValue OBJECT-TYPE dot3OamEventLogValue OBJECT-TYPE
SYNTAX CounterBasedGauge64 SYNTAX CounterBasedGauge64
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"If the event represents a threshold crossing event, this "If the event represents a threshold crossing event, this
value indicates the value of the parameter within the given value indicates the value of the parameter within the given
window that generated this event (e.g. 11, when 11 occurrences window that generated this event (for example, 11, when 11
happened in 5 seconds while the threshold was 10). occurrences happened in 5 seconds while the threshold was 10).
Otherwise, this value is returned as all F's Otherwise, this value is returned as all F's
(0xFFFFFFFFFFFFFFFF) and adds no useful information. (2^64 - 1) and adds no useful information.
" "
REFERENCE "[802.3ah], 30.3.6.1.37 and 57.5.3.2." REFERENCE "[802.3ah], 30.3.6.1.37 and 57.5.3.2."
::= { dot3OamEventLogEntry 10 } ::= { dot3OamEventLogEntry 10 }
dot3OamEventLogRunningTotal OBJECT-TYPE dot3OamEventLogRunningTotal OBJECT-TYPE
SYNTAX CounterBasedGauge64 SYNTAX CounterBasedGauge64
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This value respresents the total number of times this "Each Event Notification TLV contains a running total of the
EFM OAM MIB March 2005 number of times an event has occurred, as well as the number
of times an Event Notification for the event has been
transmitted. For non-threshold crossing events, the number of
events (dot3OamLogRunningTotal) and the number of resultant
Event Notifications (dot3OamLogEventTotal) should be
identical.
occurence has happened since the last reset (e.g. 3253, when For threshold crossing events, since multiple occurrences may
3253 symbol errors have occurred since the last reset, which be required to cross the threshold, these values are likely
has resulted in 51 symbol error threshold crossing events different. This value represents the total number of times
since the last reset). " this event has happened since the last reset (for example,
3253, when 3253 symbol errors have occurred since the last
reset, which has resulted in 51 symbol error threshold
crossing events since the last reset).
Ethernet OAM MIB March 2006
"
REFERENCE "[802.3ah], 30.3.6.1.37 and 57.5.3.2." REFERENCE "[802.3ah], 30.3.6.1.37 and 57.5.3.2."
::= { dot3OamEventLogEntry 11 } ::= { dot3OamEventLogEntry 11 }
dot3OamEventLogEventTotal OBJECT-TYPE dot3OamEventLogEventTotal OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This value respresents the total number of times one or ore "Each Event Notification TLV contains a running total of the
of these occurences have resulted in an event (e.g. 51 when number of times an event has occurred, as well as the number
3253 symbol errors have occurred since the last reset, which of times an Event Notification for the event has been
has resulted in 51 symbol error threshold crossing events transmitted. For non-threshold crossing events, the number of
since the last reset). " events (dot3OamLogRunningTotal) and the number of resultant
Event Notifications (dot3OamLogEventTotal) should be
identical.
For threshold crossing events, since multiple occurrences may
be required to cross the threshold, these values are likely
different. This value represents the total number of times
one or more of these occurrences have resulted in an Event
Notification (for example, 51 when 3253 symbol errors have
occurred since the last reset, which has resulted in 51 symbol
error threshold crossing events since the last reset).
"
REFERENCE "[802.3ah], 30.3.6.1.37 and 57.5.3.2." REFERENCE "[802.3ah], 30.3.6.1.37 and 57.5.3.2."
::= { dot3OamEventLogEntry 12 } ::= { dot3OamEventLogEntry 12 }
------------------------------------------------------------------ -- ***************************************************************
-- --
-- Ethernet OAM Notifications -- Ethernet OAM Notifications
-- --
dot3OamNotifs OBJECT IDENTIFIER ::= { dot3OamMIB 7 }
dot3OamNotifsPrefix OBJECT IDENTIFIER ::= {dot3OamNotifs 0}
dot3OamThresholdEvent NOTIFICATION-TYPE dot3OamThresholdEvent NOTIFICATION-TYPE
OBJECTS { ifIndex, OBJECTS { dot3OamEventLogTimestamp,
dot3OamEventLogTimestamp,
dot3OamEventLogOui, dot3OamEventLogOui,
dot3OamEventLogType, dot3OamEventLogType,
dot3OamEventLogLocation, dot3OamEventLogLocation,
dot3OamEventLogWindowHi, dot3OamEventLogWindowHi,
dot3OamEventLogWindowLo, dot3OamEventLogWindowLo,
dot3OamEventLogThresholdHi, dot3OamEventLogThresholdHi,
dot3OamEventLogThresholdLo, dot3OamEventLogThresholdLo,
dot3OamEventLogValue, dot3OamEventLogValue,
dot3OamEventLogRunningTotal, dot3OamEventLogRunningTotal,
dot3OamEventLogEventTotal dot3OamEventLogEventTotal
} }
STATUS current STATUS current
Ethernet OAM MIB March 2006
DESCRIPTION DESCRIPTION
"A dot3OamThresholdEvent notification is sent when a local or "A dot3OamThresholdEvent notification is sent when a local or
remote threshold crossing event is detected. A local remote threshold crossing event is detected. A local
threshold crossing event is detected by the local entity, threshold crossing event is detected by the local entity,
while a remote threshold crossing event is detected by the while a remote threshold crossing event is detected by the
EFM OAM MIB March 2005
reception of an Ethernet OAM Event Notification OAMPDU reception of an Ethernet OAM Event Notification OAMPDU
indicating a threshold event. indicating a threshold event.
This notification should not be sent more than once per This notification should not be sent more than once per
second. second.
The OAM entity can be derived from extracting the ifIndex from
the variable bindings. The objects in the notification
correspond to the values in a row instance of in the
dot3OamEventLogTable.
The management entity should periodically check The management entity should periodically check
dot3OamEventLogTable to detect any missed events." dot3OamEventLogTable to detect any missed events."
::= { dot3OamNotifsPrefix 1 } ::= { dot3OamNotifications 1 }
dot3OamNonThresholdEvent NOTIFICATION-TYPE dot3OamNonThresholdEvent NOTIFICATION-TYPE
OBJECTS { ifIndex, OBJECTS { dot3OamEventLogTimestamp,
dot3OamEventLogTimestamp,
dot3OamEventLogOui, dot3OamEventLogOui,
dot3OamEventLogType, dot3OamEventLogType,
dot3OamEventLogLocation, dot3OamEventLogLocation,
dot3OamEventLogEventTotal dot3OamEventLogEventTotal
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A dot3OamNonThresholdEvent notification is sent when a local "A dot3OamNonThresholdEvent notification is sent when a local
or remote non-threshold crossing event is detected. A local or remote non-threshold crossing event is detected. A local
event is detected by the local entity, while a remote event is event is detected by the local entity, while a remote event is
detected by the reception of an Ethernet OAM Event detected by the reception of an Ethernet OAM Event
Notification OAMPDU indicating a non-threshold crossing event. Notification OAMPDU indicating a non-threshold crossing event.
This notification should not be sent more than once per This notification should not be sent more than once per
second. second.
The OAM entity can be derived from extracting the ifIndex from
the variable bindings. The objects in the notification
correspond to the values in a row instance of the
dot3OamEventLogTable.
The management entity should periodically check The management entity should periodically check
dot3OamEventLogTable to detect any missed events." dot3OamEventLogTable to detect any missed events."
::= { dot3OamNotifsPrefix 2 } ::= { dot3OamNotifications 2 }
Ethernet OAM MIB March 2006
------------------------------------------------------------------ -- ***************************************************************
-- --
-- Ethernet OAM Compliance group -- Ethernet OAM Compliance group
-- --
dot3OamGroups OBJECT IDENTIFIER ::= { dot3OamConformance 1 } dot3OamGroups OBJECT IDENTIFIER ::= { dot3OamConformance 1 }
dot3OamCompliances OBJECT IDENTIFIER ::= { dot3OamConformance 2 } dot3OamCompliances OBJECT IDENTIFIER ::= { dot3OamConformance 2 }
-- Compliance statements -- Compliance statements
dot3OamCompliance MODULE-COMPLIANCE dot3OamCompliance MODULE-COMPLIANCE
STATUS current STATUS current
DESCRIPTION "The compliance statement for managed entities DESCRIPTION "The compliance statement for managed entities
EFM OAM MIB March 2005
supporting OAM on Ethernet like interfaces. supporting OAM on Ethernet like interfaces.
" "
MODULE -- this module MODULE -- this module
MANDATORY-GROUPS { dot3OamControlGroup, MANDATORY-GROUPS { dot3OamControlGroup,
dot3OamPeerGroup, dot3OamPeerGroup,
dot3OamStatsBaseGroup dot3OamStatsBaseGroup
} }
GROUP dot3OamLoopbackGroup GROUP dot3OamLoopbackGroup
DESCRIPTION DESCRIPTION
skipping to change at page 47, line 41 skipping to change at page 48, line 4
"This group is mandatory for all IEEE 802.3 OAM "This group is mandatory for all IEEE 802.3 OAM
implementations that support event functionality. " implementations that support event functionality. "
GROUP dot3OamErrFrameSecsSummaryEventGroup GROUP dot3OamErrFrameSecsSummaryEventGroup
DESCRIPTION DESCRIPTION
"This group is mandatory for all IEEE 802.3 OAM "This group is mandatory for all IEEE 802.3 OAM
implementations that support event functionality. " implementations that support event functionality. "
GROUP dot3OamFlagEventGroup GROUP dot3OamFlagEventGroup
DESCRIPTION DESCRIPTION
Ethernet OAM MIB March 2006
"This group is optional for all IEEE 802.3 OAM "This group is optional for all IEEE 802.3 OAM
implementations. The ability to send critical events or implementations. The ability to send critical events or dying
dying gasp events is not required in any system." gasp events is not required in any system."
GROUP dot3OamEventLogGroup GROUP dot3OamEventLogGroup
DESCRIPTION DESCRIPTION
"This group is optional for all IEEE 802.3 OAM "This group is optional for all IEEE 802.3 OAM
implementations. " implementations. Entries in this table are dependent on what
event functionality is supported in the local OAM
implementation. At least one type of event must be supported
for entries to appear in this table. "
GROUP dot3OamNotificationGroup GROUP dot3OamNotificationGroup
DESCRIPTION DESCRIPTION
"This group is optional for all IEEE 802.3 OAM "This group is optional for all IEEE 802.3 OAM
EFM OAM MIB March 2005 implementations. Since the information in the notifications
is dependent on the dot3OamEventLogTable, that table must be
implementations. " implemented for notifications. "
::= { dot3OamCompliances 1} ::= { dot3OamCompliances 1}
dot3OamControlGroup OBJECT-GROUP dot3OamControlGroup OBJECT-GROUP
OBJECTS { dot3OamAdminState, OBJECTS { dot3OamAdminState,
dot3OamOperStatus, dot3OamOperStatus,
dot3OamMode, dot3OamMode,
dot3OamMaxOamPduSize, dot3OamMaxOamPduSize,
dot3OamConfigRevision, dot3OamConfigRevision,
dot3OamFunctionsSupported dot3OamFunctionsSupported
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of objects providing the abilities, "A collection of objects providing the abilities,
configuration, and status of an Ethernet OAM entity. " configuration, and status of an Ethernet OAM entity. "
::= { dot3OamGroups 1 } ::= { dot3OamGroups 1 }
dot3OamPeerGroup OBJECT-GROUP dot3OamPeerGroup OBJECT-GROUP
OBJECTS { dot3OamPeerStatus, OBJECTS { dot3OamPeerMacAddress,
dot3OamPeerMacAddress,
dot3OamPeerVendorOui, dot3OamPeerVendorOui,
dot3OamPeerVendorInfo, dot3OamPeerVendorInfo,
dot3OamPeerMode, dot3OamPeerMode,
dot3OamPeerFunctionsSupported, dot3OamPeerFunctionsSupported,
dot3OamPeerMaxOamPduSize, dot3OamPeerMaxOamPduSize,
dot3OamPeerConfigRevision dot3OamPeerConfigRevision
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of objects providing the abilities, "A collection of objects providing the abilities,
configuration, and status of a peer Ethernet OAM entity. " configuration, and status of a peer Ethernet OAM entity. "
Ethernet OAM MIB March 2006
::= { dot3OamGroups 2 } ::= { dot3OamGroups 2 }
dot3OamStatsBaseGroup OBJECT-GROUP dot3OamStatsBaseGroup OBJECT-GROUP
OBJECTS { dot3OamInformationTx, OBJECTS { dot3OamInformationTx,
dot3OamInformationRx, dot3OamInformationRx,
dot3OamUniqueEventNotificationTx, dot3OamUniqueEventNotificationTx,
dot3OamUniqueEventNotificationRx, dot3OamUniqueEventNotificationRx,
dot3OamDuplicateEventNotificationTx, dot3OamDuplicateEventNotificationTx,
dot3OamDuplicateEventNotificationRx, dot3OamDuplicateEventNotificationRx,
dot3OamLoopbackControlTx, dot3OamLoopbackControlTx,
dot3OamLoopbackControlRx, dot3OamLoopbackControlRx,
dot3OamVariableRequestTx, dot3OamVariableRequestTx,
dot3OamVariableRequestRx, dot3OamVariableRequestRx,
dot3OamVariableResponseTx, dot3OamVariableResponseTx,
dot3OamVariableResponseRx, dot3OamVariableResponseRx,
dot3OamOrgSpecificTx, dot3OamOrgSpecificTx,
EFM OAM MIB March 2005
dot3OamOrgSpecificRx, dot3OamOrgSpecificRx,
dot3OamUnsupportedCodesTx, dot3OamUnsupportedCodesTx,
dot3OamUnsupportedCodesRx, dot3OamUnsupportedCodesRx,
dot3OamFramesLostDueToOam dot3OamFramesLostDueToOam
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of objects providing the statistics for the "A collection of objects providing the statistics for the
number of various transmit and recieve events for OAM on an number of various transmit and receive events for OAM on an
Ethernet like interface. Note that all of these counters must Ethernet like interface. Note that all of these counters must
be supported even if the related function (as described in be supported even if the related function (as described in
dot3OamFunctionsSupported) is not supported. " dot3OamFunctionsSupported) is not supported. "
::= { dot3OamGroups 3 } ::= { dot3OamGroups 3 }
dot3OamLoopbackGroup OBJECT-GROUP dot3OamLoopbackGroup OBJECT-GROUP
OBJECTS { dot3OamLoopbackCommand, OBJECTS { dot3OamLoopbackStatus,
dot3OamLoopbackStatus,
dot3OamLoopbackIgnoreRx dot3OamLoopbackIgnoreRx
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of objects for controlling the OAM remote "A collection of objects for controlling the OAM remote
loopback function. " loopback function. "
::= { dot3OamGroups 4 } ::= { dot3OamGroups 4 }
dot3OamErrSymbolPeriodEventGroup OBJECT-GROUP dot3OamErrSymbolPeriodEventGroup OBJECT-GROUP
OBJECTS { dot3OamErrSymPeriodWindowHi, OBJECTS { dot3OamErrSymPeriodWindowHi,
dot3OamErrSymPeriodWindowLo, dot3OamErrSymPeriodWindowLo,
dot3OamErrSymPeriodThresholdHi, dot3OamErrSymPeriodThresholdHi,
dot3OamErrSymPeriodThresholdLo, dot3OamErrSymPeriodThresholdLo,
dot3OamErrSymPeriodEvNotifEnable dot3OamErrSymPeriodEvNotifEnable
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
Ethernet OAM MIB March 2006
"A collection of objects for configuring the thresholds for an "A collection of objects for configuring the thresholds for an
Errored Symbol Period Event. Errored Symbol Period Event.
Each [802.3ah] defined Event Notification TLV has its own Each [802.3ah] defined Event Notification TLV has its own
conformance group because each event can be implemented conformance group because each event can be implemented
independently of any other. " independently of any other. "
::= { dot3OamGroups 5 } ::= { dot3OamGroups 5 }
dot3OamErrFramePeriodEventGroup OBJECT-GROUP dot3OamErrFramePeriodEventGroup OBJECT-GROUP
OBJECTS { dot3OamErrFramePeriodWindow, OBJECTS { dot3OamErrFramePeriodWindow,
dot3OamErrFramePeriodThreshold, dot3OamErrFramePeriodThreshold,
dot3OamErrFramePeriodEvNotifEnable dot3OamErrFramePeriodEvNotifEnable
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
EFM OAM MIB March 2005
"A collection of objects for configuring the thresholds for an "A collection of objects for configuring the thresholds for an
Errored Frame Period Event. Errored Frame Period Event.
Each [802.3ah] defined Event Notification TLV has its own Each [802.3ah] defined Event Notification TLV has its own
conformance group because each event can be implemented conformance group because each event can be implemented
independently of any other. " independently of any other. "
::= { dot3OamGroups 6 } ::= { dot3OamGroups 6 }
dot3OamErrFrameEventGroup OBJECT-GROUP dot3OamErrFrameEventGroup OBJECT-GROUP
OBJECTS { dot3OamErrFrameWindow, OBJECTS { dot3OamErrFrameWindow,
skipping to change at page 50, line 40 skipping to change at page 51, line 4
OBJECTS { dot3OamErrFrameSecsSummaryWindow, OBJECTS { dot3OamErrFrameSecsSummaryWindow,
dot3OamErrFrameSecsSummaryThreshold, dot3OamErrFrameSecsSummaryThreshold,
dot3OamErrFrameSecsEvNotifEnable dot3OamErrFrameSecsEvNotifEnable
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of objects for configuring the thresholds for an "A collection of objects for configuring the thresholds for an
Errored Frame Seconds Summary Event. Errored Frame Seconds Summary Event.
Each [802.3ah] defined Event Notification TLV has its own Each [802.3ah] defined Event Notification TLV has its own
Ethernet OAM MIB March 2006
conformance group because each event can be implemented conformance group because each event can be implemented
independently of any other. " independently of any other. "
::= { dot3OamGroups 8 } ::= { dot3OamGroups 8 }
dot3OamFlagEventGroup OBJECT-GROUP dot3OamFlagEventGroup OBJECT-GROUP
OBJECTS { dot3OamDyingGaspEnable, OBJECTS { dot3OamDyingGaspEnable,
dot3OamCriticalEventEnable dot3OamCriticalEventEnable
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of objects for configuring the sending OAMPDUs "A collection of objects for configuring the sending OAMPDUs
with the critical event flag or dying gasp flag enabled. " with the critical event flag or dying gasp flag enabled. "
::= { dot3OamGroups 9 } ::= { dot3OamGroups 9 }
dot3OamEventLogGroup OBJECT-GROUP dot3OamEventLogGroup OBJECT-GROUP
EFM OAM MIB March 2005
OBJECTS { dot3OamEventLogTimestamp, OBJECTS { dot3OamEventLogTimestamp,
dot3OamEventLogOui, dot3OamEventLogOui,
dot3OamEventLogType, dot3OamEventLogType,
dot3OamEventLogLocation, dot3OamEventLogLocation,
dot3OamEventLogWindowHi, dot3OamEventLogWindowHi,
dot3OamEventLogWindowLo, dot3OamEventLogWindowLo,
dot3OamEventLogThresholdHi, dot3OamEventLogThresholdHi,
dot3OamEventLogThresholdLo, dot3OamEventLogThresholdLo,
dot3OamEventLogValue, dot3OamEventLogValue,
dot3OamEventLogRunningTotal, dot3OamEventLogRunningTotal,
skipping to change at page 51, line 33 skipping to change at page 51, line 48
::= { dot3OamGroups 10 } ::= { dot3OamGroups 10 }
dot3OamNotificationGroup NOTIFICATION-GROUP dot3OamNotificationGroup NOTIFICATION-GROUP
NOTIFICATIONS { NOTIFICATIONS {
dot3OamThresholdEvent, dot3OamThresholdEvent,
dot3OamNonThresholdEvent dot3OamNonThresholdEvent
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of notifications used by Ethernet OAM to signal "A collection of notifications used by Ethernet OAM to signal
to a management entity that local or remote events have occured to a management entity that local or remote events have
occurred
on a specified Ethernet link." on a specified Ethernet link."
::= { dot3OamGroups 11 } ::= { dot3OamGroups 11 }
END END
Ethernet OAM MIB March 2006
7. Security Considerations 7. Security Considerations
The readable objects in this module can provide information about The readable objects in this module can provide information about
network traffic, and therefore may be considered sensitive. In network traffic, and therefore may be considered sensitive. In
particular, OAM provides mechanisms for reading the IEEE 802.3 Clause particular, OAM provides mechanisms for reading the IEEE 802.3 Clause
30 MIB attributes from a link partner via a specialized layer two 30 MIB attributes from a link partner via a specialized layer two
protocol. Unlike SNMP, IEEE P802.3ah OAM does not include encryption protocol. Unlike SNMP, IEEE P802.3ah OAM does not include encryption
or authorization mechanisms. It should be used in environments where or authorization mechanisms. It should be used in environments where
either this interface information is not considered sensitive, or either this interface information is not considered sensitive, or
where the facility terminations are protected. By default, OAM is where the facility terminations are protected. By default, OAM is
disabled on Ethernet like interfaces and is therefore not a risk. disabled on Ethernet like interfaces and is therefore not a risk.
EFM OAM MIB March 2005
IEEE 802.3ah OAM is designed to support deployment in access and IEEE 802.3ah OAM is designed to support deployment in access and
enterprise networks. In access networks, one end of a link is the enterprise networks. In access networks, one end of a link is the
CO-side, and the other is the CPE-side, and the facilities are often CO-side, and the other is the CPE-side, and the facilities are often
protected in wiring cages or closets. In such deployments, it is protected in wiring cages or closets. In such deployments, it is
often the case that the CO-side is protected from access from the CPE often the case that the CO-side is protected from access from the CPE
side. Within IEEE P802.3ah OAM, this protection from remote access side. Within IEEE P802.3ah OAM, this protection from remote access
is accomplished by configuring the CPE-side in passive mode using the is accomplished by configuring the CPE-side in passive mode using the
dot3OamMode attribute. This prevents the CPE from accessing dot3OamMode attribute. This prevents the CPE from accessing
functions and information at the CO-side of the connection. In functions and information at the CO-side of the connection. In
enterprise networks, read-only interface information is often enterprise networks, read-only interface information is often
skipping to change at page 52, line 41 skipping to change at page 53, line 4
attribute (dot3OamLoopbackIgnoreRx) was introduced to control whether attribute (dot3OamLoopbackIgnoreRx) was introduced to control whether
the local station processes or ignores received loopback commands. the local station processes or ignores received loopback commands.
The administrative state and mode are also read-write objects. The administrative state and mode are also read-write objects.
Disabling OAM can interrupt management activities between peer Disabling OAM can interrupt management activities between peer
devices, potentially causing serious problems. Setting the devices, potentially causing serious problems. Setting the
dot3OamMode to an undesired value can allow access to Ethernet dot3OamMode to an undesired value can allow access to Ethernet
monitoring, events, and functions that may not be acceptable in a monitoring, events, and functions that may not be acceptable in a
particular deployment scenario. In addition to loopback particular deployment scenario. In addition to loopback
functionality, Ethernet interface statistics and events can be functionality, Ethernet interface statistics and events can be
Ethernet OAM MIB March 2006
accessed via the OAM protocol, which may not be desired in some accessed via the OAM protocol, which may not be desired in some
circumstances. circumstances.
OAM event configuration also contains read-write objects. These OAM event configuration also contains read-write objects. These
objects control whether events are sent, and at what thresholds. objects control whether events are sent, and at what thresholds.
Note that the frequency of event communication is limited by the Note that the frequency of event communication is limited by the
frequency limits of Slow Protocols on Ethernet interfaces. Also, the frequency limits of Slow Protocols on Ethernet interfaces. Also, the
information available obtainable via OAM events is also available via information available obtainable via OAM events is also available via
OAM Variable Requests. Access to this information via either OAM OAM Variable Requests. Access to this information via either OAM
events or Variable Requests is controlled by the dot3OamAdminState events or Variable Requests is controlled by the dot3OamAdminState
and dot3OamMode objects. As mentioned previously, inadequate and dot3OamMode objects. As mentioned previously, inadequate
protection of these variables can result in access to link protection of these variables can result in access to link
information and functions. information and functions.
EFM OAM MIB March 2005
SNMP versions prior to SNMPv3 did not include adequate security. Even SNMP versions prior to SNMPv3 did not include adequate security. Even
if the network itself is secure (for example by using IPSec), even if the network itself is secure (for example by using IPSec), even
then, there is no control as to who on the secure network is allowed then, there is no control as to who on the secure network is allowed
to access and GET/SET (read/change/create/delete) the objects in this to access and GET/SET (read/change/create/delete) the objects in this
MIB module. MIB module.
It is RECOMMENDED that implementers consider the security features as It is RECOMMENDED that implementers consider the security features as
provided by the SNMPv3 framework (see [RFC3410], section 8), provided by the SNMPv3 framework (see [RFC3410], section 8),
including full support for the SNMPv3 cryptographic mechanisms (for including full support for the SNMPv3 cryptographic mechanisms (for
authentication and privacy). authentication and privacy).
Further, deployment of SNMP versions prior to SNMPv3 is NOT Further, deployment of SNMP versions prior to SNMPv3 is NOT
RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to
enable cryptographic security. It is then a customer/operator enable cryptographic security. It is then a customer/operator
responsibility to ensure that the SNMP entity giving access to an responsibility to ensure that the SNMP entity giving access to an
instance of this MIB module is properly configured to give access to instance of this MIB module is properly configured to give access to
the objects only to those principals (users) that have legitimate the objects only to those principals (users) that have legitimate
rights to indeed GET or SET (change/create/delete) them rights to indeed GET or SET (change/create/delete) them
8. References 8. IANA Considerations
8.1 Normative References The Ethernet OAM MIB requires the allocation of a single object
identifier for its MODULE-IDENTITY under the MIB-2 tree.
The MIB module in this document uses the following IANA-assigned
OBJECT IDENTIFIER values recorded in the SMI Numbers registry:
Descriptor OBJECT IDENTIFIER
---------- -----------------
dot3OamMIB { mib-2 XXX }
Editor's Note (to be removed prior to publication): the IANA is
requested to assign a value for "XXX" under the 'mib-2' subtree and
to record the assignment in the SMI Numbers registry. When the
assignment has been made, the RFC Editor is asked to replace "XXX"
Ethernet OAM MIB March 2006
(here and in the MIB module) with the assigned value and to remove
this note.
9. References
9.1 Normative References
[802.3ah] Institute of Electrical and Electronic Engineers, IEEE Std [802.3ah] Institute of Electrical and Electronic Engineers, IEEE Std
802.3ah-2004, "Part 3: Carrier Sense Multiple Access with Collision 802.3ah-2004, "Part 3: Carrier Sense Multiple Access with Collision
Detection (CSMA/CD) Access Method and Physical Layer Specifications Detection (CSMA/CD) Access Method and Physical Layer Specifications -
Amendment: Media Access Control Parameters, Physical Layers and Amendment: Media Access Control Parameters, Physical Layers and
Management Parameters for Subscriber Access Networks", October 2004. Management Parameters for Subscriber Access Networks", October 2004.
[802.3-2002] Institute of Electrical and Electronic Engineers, IEEE [802.3-2002] Institute of Electrical and Electronic Engineers, IEEE
Std 802.3-2003, "IEEE Standard for Carrier Sense Multiple Access with Std 802.3-2003, "IEEE Standard for Carrier Sense Multiple Access with
Collision Detection (CSMA/CD) Access Method and Physical Layer Collision Detection (CSMA/CD) Access Method and Physical Layer
Specifications - Draft amendment to Information technology - Specifications - Draft amendment to - Information technology -
Telecommunications and information exchange between systems - Local Telecommunications and information exchange between systems - Local
and metropolitan area networks - Specific requirements - Part 3: and metropolitan area networks - Specific requirements - Part 3:
Carrier sense multiple access with collision detection (CSMA/CD) Carrier sense multiple access with collision detection (CSMA/CD)
access method and physical layer specifications Media Access access method and physical layer specifications - Media Access
Control Parameters, Physical Layers and Management Parameters", March Control Parameters, Physical Layers and Management Parameters", March
2002. 2002.
[802.3-2005] Institute of Electrical and Electronic Engineers, IEEE
Std 802.3-2005, "IEEE Standard for Carrier Sense Multiple Access with
Collision Detection (CSMA/CD) Access Method and Physical Layer
Specifications - Draft amendment to - Information technology -
Telecommunications and information exchange between systems - Local
and metropolitan area networks - Specific requirements - Part 3:
Carrier sense multiple access with collision detection (CSMA/CD)
access method and physical layer specifications - Media Access
Control Parameters, Physical Layers and Management Parameters",
December 2005.
[802-2001] Institute of Electrical and Electronic Engineers, IEEE [802-2001] Institute of Electrical and Electronic Engineers, IEEE
Std 802-2001, "Standard for Local and Metropolitan Area Networks: Std 802-2001, "Standard for Local and Metropolitan Area Networks:
Architecture and Overview", March 2002. Architecture and Overview", March 2002.
[RFC2026] Bradner, S, "The Internet Standards Process -- Revision
3", BCP 9, RFC 2026, October 1996.
EFM OAM MIB March 2005
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997 Requirement Levels", BCP 14, RFC 2119, March 1997
[RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J.,
McCloghrie, K., Rose, M. and S. Waldbusser, "Structure of Management McCloghrie, K., Rose, M. and S. Waldbusser, "Structure of Management
Information Version 2 (SMIv2)", STD 58, RFC 2578, April 1999. Information Version 2 (SMIv2)", STD 58, RFC 2578, April 1999.
Ethernet OAM MIB March 2006
[RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J.,
McCloghrie, K., Rose, M. and S. Waldbusser, "Textual Conventions for McCloghrie, K., Rose, M. and S. Waldbusser, "Textual Conventions for
SMIv2", STD 58, RFC 2579, April 1999. SMIv2", STD 58, RFC 2579, April 1999.
[RFC2580] McCloghrie, K., Perkins, D. and J. Schoenwaelder, [RFC2580] McCloghrie, K., Perkins, D. and J. Schoenwaelder,
"Conformance Statements for SMIv2", STD 58, RFC 2580, April 1999. "Conformance Statements for SMIv2", STD 58, RFC 2580, April 1999.
[RFC3668] Bradner, S. "Intellectual Property Rights in IETF [RFC2586] Bierman, A., McCloghrie, K., Presuhn, R., "Textual
Technology", BCP 79, RFC 3668, February 2004. Conventions for Additional High Capacity Data Types", RFC 2856, June
2000.
8.2 Informative References
[802.3ah-copper] Beili, Ed, "Managed Objects for Ethernet Passive [RFC2863] McCloghrie, K., Kastenholz, F., "The Interfaces Group
Optical Networks", draft-ietf-hubmib-efm-epon-mib-02.txt, October MIB", RFC 2863, June 2000.
2004.
[802.3ah-epon] Khermosh, Lior, "Ethernet in the First Mile Copper 9.2 Informative References
(EFMCu) Interfaces MIB", draft-ietf-hubmib-efm-cu-mib-02.txt, October
2004.
[RFC2665] Flick, J. and Johnson J. "Definitions of Managed Objects [802.3ah-copper] Beili, Ed, "Ethernet in the First Mile Copper
for the Ethernet like Interface Types", STD 58, RFC 2580, April 1999. (EFMCu) Interfaces MIB", draft-ietf-hubmib-efm-cu-05.txt, March 2006.
[RFC2863] McCloghrie, K., Kastenholz, F., "The Interfaces Group [802.3ah-epon] Khermosh, Lior, "Managed Object of EPON", draft-ietf-
MIB", RFC 2863, June 2000. hubmib-efm-epon-mib-04.txt, February 2006.
[RFC3410] Case, J., Mundy, R., Partain, D., Stewart, B., [RFC3410] Case, J., Mundy, R., Partain, D., Stewart, B.,
"Introduction and Applicability Statements for Internet Standard "Introduction and Applicability Statements for Internet Standard
Management Framework", RFC 3410, December 2003. Management Framework", RFC 3410, December 2003.
[RFC3635] Flick, J., "Definitions of Managed Objects for the [RFC3635] Flick, J., "Definitions of Managed Objects for the
Ethernet like Interface Types", RFC 3635, September 2003. Ethernet like Interface Types", RFC 3635, September 2003.
[RFC3636] Flick, J., "Definitions of Managed Objects for IEEE 802.3 [RFC3636] Flick, J., "Definitions of Managed Objects for IEEE 802.3
Medium Attachment Units (MAUs)", RFC 3636, September 2003. Medium Attachment Units (MAUs)", RFC 3636, September 2003.
9. Acknowledgments 10. Acknowledgments
The author is grateful to all of the participants in the IEEE 802.3ah The author is grateful to all of the participants in the IEEE 802.3ah
EFM (Ethernet in the First Mile) taskforce. In particular, the EFM (Ethernet in the First Mile) taskforce. In particular, the
EFM OAM MIB March 2005
strong leadership and dedication of the following individuals is strong leadership and dedication of the following individuals is
noted: noted:
Kevin Daines (Editor, IEEE 802.3ah OAM clauses) Kevin Daines (Editor, IEEE 802.3ah OAM clauses)
Ben Brown (Editor, IEEE 802.3ah Logic clauses) Ben Brown (Editor, IEEE 802.3ah Logic clauses)
David Law (Editor, IEEE 802.3ah Management clauses) David Law (Editor, IEEE 802.3ah Management clauses)
Scott Simon (Editor, IEEE 802.3ah Clause 45) Scott Simon (Editor, IEEE 802.3ah Clause 45)
Howard Frazier (Chair, IEEE 802.3ah) Howard Frazier (Chair, IEEE 802.3ah)
Hugh Barass (Vice-Chair, IEEE 802.3ah) Hugh Barass (Vice-Chair, IEEE 802.3ah)
Wael Diab (Editor, IEEE 802.3ah) Wael Diab (Editor, IEEE 802.3ah)
Ethernet OAM MIB March 2006
Additionally, certain devoted attendees and contributors to the IEEE Additionally, certain devoted attendees and contributors to the IEEE
802.3ah OAM sub-taskforce deserve recognition. Although there were 802.3ah OAM sub-taskforce deserve recognition. Although there were
many contributors, the following individuals contributed heavily over many contributors, the following individuals contributed heavily over
a long period of time. a long period of time.
Brian Arnold Brian Arnold
Brad Booth Brad Booth
Al Braga Al Braga
Floyd Gerhardt Floyd Gerhardt
Bob Grow Bob Grow
Eric Lynskey Eric Lynskey
David Martin David Martin
John Messenger John Messenger
Dan Romascanu (Chair, IETF HUBMIB WG) Dan Romascanu (Chair, IETF HUBMIB WG)
Jonathan Thatcher Jonathan Thatcher
Geoff Thompson Geoff Thompson
10. Author's Address 11. Author's Address
Note: Author's email address is spelled out to help protect against Note: Author's email address is spelled out to help protect against
email address harvesting programs. email address harvesting programs.
Matt Squire Matt Squire
Hatteras Networks Hatteras Networks
639 Davis Drive, Suite 200 639 Davis Drive, Suite 200
Phone: +1-919-991-5460 Phone: +1-919-991-5460
Email: msquire at hatterasnetworks dot com Email: msquire at hatterasnetworks dot com
11. Intellectual Property Statement 12. Intellectual Property Statement
The IETF takes no position regarding the validity or scope of any The IETF takes no position regarding the validity or scope of any
Intellectual Property Rights or other rights that might be claimed to Intellectual Property Rights or other rights that might be claimed to
pertain to the implementation or use of the technology described in pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights this document or the extent to which any license under such rights
might or might not be available; nor does it represent that it has might or might not be available; nor does it represent that it has
made any independent effort to identify any such rights. Information made any independent effort to identify any such rights. Information
EFM OAM MIB March 2005
on the procedures with respect to rights in RFC documents can be on the procedures with respect to rights in RFC documents can be
found in BCP 78 and BCP 79. found in BCP 78 and BCP 79.
Copies of IPR disclosures made to the IETF Secretariat and any Copies of IPR disclosures made to the IETF Secretariat and any
assurances of licenses to be made available, or the result of an assurances of licenses to be made available, or the result of an
attempt made to obtain a general license or permission for the use of attempt made to obtain a general license or permission for the use of
such proprietary rights by implementers or users of this such proprietary rights by implementers or users of this
specification can be obtained from the IETF on-line IPR repository at specification can be obtained from the IETF on-line IPR repository at
http://www.ietf.org/ipr. http://www.ietf.org/ipr.
Ethernet OAM MIB March 2006
The IETF invites any interested party to bring to its attention any The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary copyrights, patents or patent applications, or other proprietary
rights that may cover technology that may be required to implement rights that may cover technology that may be required to implement
this standard. Please address the information to the IETF at ietf this standard. Please address the information to the IETF at
ipr@ietf.org. ietf-ipr@ietf.org.
The IETF has been notified of intellectual property rights claimed in The IETF has been notified of intellectual property rights claimed in
regard to some or all of the specification contained in this regard to some or all of the specification contained in this
document. For more information consult the online list of claimed document. For more information consult the online list of claimed
rights. rights.
12. Copyright Statement 13. Copyright Statement
Copyright (C) The Internet Society (2005). This document is subject Copyright (C) The Internet Society (2006).
to the rights, licenses and restrictions contained in BCP 78, and
except as set forth therein, the authors retain all their rights.
This document and the information contained herein are provided on an This document is subject to the rights, licenses and restrictions
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS contained in BCP 78, and except as set forth therein, the authors
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET retain all their rights.
ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE This document and the information contained herein are provided
INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED on an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND
THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES,
EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT
THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR
ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A
PARTICULAR PURPOSE.
Acknowledgement Acknowledgement
Funding for the RFC Editor function is currently provided by the Funding for the RFC Editor function is currently provided by the
Internet Society. Internet Society.
 End of changes. 320 change blocks. 
777 lines changed or deleted 819 lines changed or added

This html diff was produced by rfcdiff 1.29, available from http://www.levkowetz.com/ietf/tools/rfcdiff/