draft-ietf-hubmib-efm-mib-05.txt   draft-ietf-hubmib-efm-mib-06.txt 
Ethernet OAM MIB October 2006 INTERNET-DRAFT Matt Squire
Document: draft-ietf-hubmib-efm-mib-06.txt Hatteras Networks
Ethernet Interfaces and Hub MIB WG Intended status: Proposed standard
Internet Draft Matt Squire Expires: August 2007 February 2007
Document: draft-ietf-hubmib-efm-mib-05.txt Hatteras Networks
Expires: April 2007 October, 2006
Definitions and Managed Objects for OAM Functions on Ethernet Like Definitions and Managed Objects for OAM Functions on Ethernet Like
Interfaces Interfaces
draft-ietf-hubmib-efm-mib-05.txt draft-ietf-hubmib-efm-mib-06.txt
Status of this Memo Status of this Memo
By submitting this Internet-Draft, each author represents that any By submitting this Internet-Draft, each author represents that any
applicable patent or other IPR claims of which he or she is aware applicable patent or other IPR claims of which he or she is aware
have been or will be disclosed, and any of which he or she becomes have been or will be disclosed, and any of which he or she becomes
aware will be disclosed, in accordance with Section 6 of BCP 79. aware will be disclosed, in accordance with Section 6 of BCP 79.
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, 2006. This Internet-Draft will expire in August, 2007.
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 the Ethernet in the First Mile (EFM) clauses of the Ethernet
standards. 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 for defines objects for controlling those link OAM functions, and for
providing results and status of the OAM functions to management providing results and status of the OAM functions to management
entities. entities.
Ethernet OAM MIB October 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............................................5 3.3 Remote loopback............................................5
3.4 Ethernet OAM Protocol Data Units...........................5 3.4 Ethernet OAM Protocol Data Units...........................5
4. Relation to the Other MIB Modules..............................5 4. Relation to the Other MIB Modules..............................5
4.1 Relation to other SNMP MIB Modules.........................5 4.1 Relation to other MIB Modules..............................5
4.2 Relation to other EFM MIB Modules..........................5 4.2 Relation to other EFM MIB Modules..........................6
4.3 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.......................................54
8. IANA Considerations...........................................53 8. IANA Considerations...........................................56
9. References....................................................54 9. References....................................................56
9.1 Normative References......................................54 9.1 Normative References......................................56
9.2 Informative References....................................55 9.2 Informative References....................................57
10. Acknowledgments..............................................55 10. Acknowledgments..............................................58
11. Author's Address.............................................56 11. Author's Address.............................................58
12. Intellectual Property Statement..............................56 12. Intellectual Property Statement..............................59
13. Copyright Statement..........................................57 13. Copyright Statement..........................................59
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 OA
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 Ethernet interface capabilities. these new Ethernet interface capabilities.
2. The Internet-Standard Management Framework 2. The Internet-Standard Management Framework
Ethernet OAM MIB October 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].
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,
skipping to change at page 3, line 29 skipping to change at page 3, line 27
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 in [802.3ah] for the 802.3ah task force defined additional clauses in [802.3ah] for the
IEEE 802.3 standard [802.3-2002] to better address Ethernet IEEE 802.3 standard [802.3-2002] to better address Ethernet
deployments in the public access network. Although Ethernet access deployments in the public access network. Although Ethernet access
deployments were the primary motivation for the task force activity, deployments were the primary motivation for the task force activity,
the results of the task force are not strictly limited to that the results of the task force are not strictly limited to that
application. application. Ethernet OAM can be implemented on Ethernet links that
are not EFM.
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 4, line 4 skipping to change at page 4, line 7
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. The mandatory functions include optional functional groups. The mandatory functions include
Ethernet OAM MIB October 2006 discovery operations (determining if the other end of the link is OA
discovery operations (determining if the other end of the link is OAM
capable, and what OAM functions it supports), state machine capable, and what OAM functions it supports), state machine
implementation, and some critical event flows. The optional implementation, and some critical event flows. The optional
functional groups are for (a) link events, (b) remote loopback, and functional groups are for (a) link events, (b) remote loopback, and
(c) variable retrieval and response. Each optional functional group (c) variable retrieval and response. Each optional functional group
is controlled by a separate MIB table(s). is controlled by a separate MIB table(s).
Ethernet OAM is complementary with SNMP management in that it Ethernet OAM is complementary with SNMP management in that it
provides some basic management functions at layer two, rather than provides some basic management functions at layer two, rather than
using layer three and above as required by SNMP over an IP using layer three and above as required by SNMP over an 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 next three sections. the next three sections. The definition of a basic Ethernet OA
protocol data unit is given in Section 3.4.
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 5, line 4 skipping to change at page 5, line 11
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 layer two events to the other end of the link. This happens via layer two
protocols. 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 October 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.
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 3.4 Ethernet OAM Protocol Data Units
An Ethernet OAM protocol data unit is a valid Ethernet frame with a An Ethernet OAM protocol data unit is a valid Ethernet frame with a
destination MAC address equal to the reserved MAC address for Slow destination MAC address equal to the reserved MAC address for Slow
Protocols (See 43B of [802.3ah], a lengthOrType field equal to the Protocols (See 43B of [802.3ah]), a lengthOrType field equal to the
reserved type for Slow Protocols, and a Slow Protocols subtype equal reserved type for Slow Protocols, and a Slow Protocols subtype equal
to that of the subtype reserved for Ethernet OAM. to that of the subtype reserved for Ethernet OAM.
OAMPDU is used throughout this document as an abbreviation for OAMPDU is used throughout this document as an abbreviation for
Ethernet OAM protocol data unit. OAMPDUs are the mechanism two Ethernet OAM protocol data unit. OAMPDUs are the mechanism by which
directly connected Ethernet interfaces exchange OAM information. two directly connected Ethernet interfaces to exchange OA
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 MIB Modules
The objects defined in this document manage OAM functionality The objects defined in this document manage OAM functionality
introduced in [802.3ah] These objects do not overlap with the introduced in [802.3ah] These objects do not overlap with the
interfaces MIB [RFC2863], the Ethernet like interfaces MIB [RFC3635], interfaces MIB [RFC2863], the Ethernet like interfaces MIB [RFC3635],
or any other MIB currently used to manage various aspects of an or any other MIB currently used to manage various aspects of an
Ethernet interface. The objects defined here are defined for 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. any Ethernet like interface.
4.2 Relation to other EFM MIB Modules 4.2 Relation to other EFM MIB Modules
Ethernet OAM MIB October 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]. Ethernet OAM may be [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 implemented (or not) on the new EFM interface types, just as it can
on any other Ethernet interface. on any other Ethernet interface.
4.3 Mapping of IEEE 802.3ah Managed Objects 4.3 Mapping of IEEE 802.3ah Managed Objects
This section contains the mapping between managed objects defined in 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 oOA
.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
skipping to change at page 7, line 4 skipping to change at page 7, line 15
.aOAMUniqueEventNotificationRx dot3OamUniqueEventNotificationRx .aOAMUniqueEventNotificationRx dot3OamUniqueEventNotificationRx
.aOAMDuplicateEventNotificationTx .aOAMDuplicateEventNotificationTx
dot3OamDuplicateEventNotificationTx dot3OamDuplicateEventNotificationTx
.aOAMDuplicateEventNotificationRx .aOAMDuplicateEventNotificationRx
dot3OamDuplicateEventNotificationRx dot3OamDuplicateEventNotificationRx
.aOAMLoopbackControlTx dot3OamLoopbackControlTx .aOAMLoopbackControlTx dot3OamLoopbackControlTx
.aOAMLoopbackControlRx dot3OamLoopbackControlRx .aOAMLoopbackControlRx dot3OamLoopbackControlRx
.aOAMVariableRequestTx dot3OamVariableRequestTx .aOAMVariableRequestTx dot3OamVariableRequestTx
.aOAMVariableRequestRx dot3OamVariableRequestRx .aOAMVariableRequestRx dot3OamVariableRequestRx
.aOAMVariableResponseTx dot3OamVariableResponseTx .aOAMVariableResponseTx dot3OamVariableResponseTx
Ethernet OAM MIB October 2006
.aOAMVariableResponseRx dot3OamVariableResponseRx .aOAMVariableResponseRx dot3OamVariableResponseRx
.aOAMOrganizationSpecificTx dot3OamOrgSpecificTx .aOAMOrganizationSpecificTx dot3OamOrgSpecificTx
.aOAMOrganizationSpecificRx dot3OamOrgSpecificTx .aOAMOrganizationSpecificRx dot3OamOrgSpecificTx
.aOAMLocalErrSymPeriodConfig dot3OamErrSymPeriodWindow, .aOAMLocalErrSymPeriodConfig dot3OamErrSymPeriodWindow,
dot3OamErrSymPeriodThreshold dot3OamErrSymPeriodThreshold
.aOAMLocalErrSymPeriodEvent dot3OamEventLogEntry .aOAMLocalErrSymPeriodEvent dot3OamEventLogEntry
.aOAMLocalErrFrameConfig dot3OamErrFrameWindow, .aOAMLocalErrFrameConfig dot3OamErrFrameWindow,
dot3OamErrFrameThreshold dot3OamErrFrameThreshold
.aOAMLocalErrFrameEvent dot3OamEventLogEntry .aOAMLocalErrFrameEvent dot3OamEventLogEntry
skipping to change at page 7, line 37 skipping to change at page 7, line 46
.aOAMRemoteErrFrameSecsSummaryEvent .aOAMRemoteErrFrameSecsSummaryEvent
dot3OamEventLogEntry dot3OamEventLogEntry
.aFramesLostDueToOAmError dot3OamFramesLostDueToOam .aFramesLostDueToOAmError dot3OamFramesLostDueToOam
.acOAMAdminControl dot3OamAdminState .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 Ethernet OAM MIB objects of this memo focus on the OAM The Ethernet OAM MIB objects of this memo focus on the OA
capabilities introduced in [802.3ah]. The MIB objects are capabilities introduced in [802.3ah]. The MIB objects are
partitioned into six 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 OA
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.
The dot3OamLoopbackTable manages the loopback function introduced in The dot3OamLoopbackTable manages the loopback function introduced in
[802.3ah]. This table controls enabling and disabling loopback, as [802.3ah]. This table controls enabling and disabling loopback, 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 October 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 event notification capability available in Ethernet OAM. With
Ethernet OAM, one device may send notifications to its peer devices Ethernet OAM, one device may send notifications to its peer devices
whenever an important event happens on the local device. This table whenever an important event happens on the local device. This table
provides management of which events result in notifications via provides management of which events result in notifications via
Ethernet OAM notifications and/or 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 whenever local events are detected by Ethernet OAM or whenever
Ethernet OAM Event Notifications are received from the peer OAM Ethernet OAM Event Notifications are received from the peer OA
entity. entity.
There are two notifications defined to report Ethernet OAM events There are two notifications defined to report Ethernet OAM events
(one for threshold crossing events, one for non-threshold crossing (one for threshold crossing events, one for non-threshold crossing
events). Both notifications are contained within the same events). Both notifications are contained within the same
conformance group. conformance group.
6. MIB Definition 6. MIB Definition
DOT3-OAM-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
-- from [RFC2578]
TEXTUAL-CONVENTION, MacAddress, TimeStamp, TruthValue TEXTUAL-CONVENTION, MacAddress, TimeStamp, TruthValue
FROM SNMPv2-TC FROM SNMPv2-TC
-- from [RFC2579]
CounterBasedGauge64 CounterBasedGauge64
FROM HCNUM-TC FROM HCNUM-TC
-- from [RFC2856]
ifIndex ifIndex
FROM IF-MIB FROM IF-MIB
-- from [RFC2863]
MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP
FROM SNMPv2-CONF; FROM SNMPv2-CONF;
-- from [RFC2580]
dot3OamMIB MODULE-IDENTITY dot3OamMIB MODULE-IDENTITY
LAST-UPDATED "200610200000Z" -- October 20,2006" LAST-UPDATED "200702140000Z" -- February 14,2007"
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: Mailing lists:
Ethernet OAM MIB October 2006
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: Bert Wijnen
Tel: +972-3-645-8414 Alcatel-Lucent
Email: dromasca at avaya dot com Email: bwijnen at alcatel-lucent dot com
Editor: Matt Squire Editor: Matt Squire
Hatteras Networks Hatteras Networks
Tel: +1-919-991-5460
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] was 802.3ah [802.3ah], released in October, 2004. [802.3ah] was
prepared as an addendum to the standing version of IEEE 802.3 prepared as an addendum to the standing version of IEEE 802.3
[802.3-2002] at the time. Since then, [802.3ah] has been [802.3-2002] at the time. Since then, [802.3ah] has been
merged into the base IEEE 802.3 specification in [802.3-2005]. merged into the base IEEE 802.3 specification in [802.3-2005].
skipping to change at page 10, line 4 skipping to change at page 10, line 25
[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
Management Parameters for subscriber access networks', Management Parameters for subscriber access networks',
Ethernet OAM MIB October 2006
October 2004. October 2004.
[802.3-2002] refers to: [802.3-2002] refers to:
IEEE Std 802.3-2002: IEEE Std 802.3-2002:
'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
Management Parameters for subscriber access networks', Management Parameters for subscriber access networks',
March 2002. March 2002.
[802.3-2005] refers to: [802.3-2005] refers to:
IEEE Std 802.3-2002: IEEE Std 802.3-2005:
'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
Management Parameters for subscriber access networks', Management Parameters for subscriber access networks',
December 2005. 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 (2006). This version of Copyright (c) The IETF Trust (2007). 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
REVISION "200610200000Z" -- October 20, 2006" REVISION "200702140000Z" -- February 14, 2007"
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 Ethernet OAM MIB -- Sections of the Ethernet OAM MIB
-- --
Ethernet OAM MIB October 2006
dot3OamNotifications OBJECT IDENTIFIER ::= { dot3OamMIB 0 } dot3OamNotifications OBJECT IDENTIFIER ::= { dot3OamMIB 0 }
dot3OamObjects OBJECT IDENTIFIER ::= { dot3OamMIB 1 } dot3OamObjects OBJECT IDENTIFIER ::= { dot3OamMIB 1 }
dot3OamConformance OBJECT IDENTIFIER ::= { dot3OamMIB 2 } dot3OamConformance OBJECT IDENTIFIER ::= { dot3OamMIB 2 }
-- --
-- Textual conventions for OAM MIB -- Textual conventions for OAM MIB
-- --
Dot3Oui ::= TEXTUAL-CONVENTION EightOTwoOui ::= 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
-- --
skipping to change at page 12, line 4 skipping to change at page 12, line 29
OAM function for a single Ethernet like interface. Entries in OAM function for a single Ethernet like interface. Entries in
the table are created automatically for each interface the table are created automatically for each interface
supporting Ethernet OAM. The status of the row entry can be supporting Ethernet OAM. The status of the row entry can be
determined from dot3OamOperStatus. determined from dot3OamOperStatus.
A dot3OamEntry is indexed in the dot3OamTable by the ifIndex A dot3OamEntry is indexed in the dot3OamTable by the ifIndex
object of the Interfaces MIB. object of the Interfaces MIB.
" "
INDEX { ifIndex } INDEX { ifIndex }
::= { dot3OamTable 1 } ::= { dot3OamTable 1 }
Ethernet OAM MIB October 2006
Dot3OamEntry ::= Dot3OamEntry ::=
SEQUENCE { SEQUENCE {
dot3OamAdminState INTEGER, dot3OamAdminState INTEGER,
dot3OamOperStatus INTEGER, dot3OamOperStatus INTEGER,
dot3OamMode INTEGER, dot3OamMode INTEGER,
dot3OamMaxOamPduSize Unsigned32, dot3OamMaxOamPduSize Unsigned32,
dot3OamConfigRevision Unsigned32, dot3OamConfigRevision Unsigned32,
dot3OamFunctionsSupported BITS dot3OamFunctionsSupported BITS
} }
skipping to change at page 12, line 28 skipping to change at page 13, line 6
enabled(1), enabled(1),
disabled(2) disabled(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(2) state
until an explicit 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(1) state. When enabled(1), Ethernet OAM will attempt enabled(1) state. When enabled(1), Ethernet OAM will attempt
to operate over this interface. to operate over this interface.
" "
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 {
skipping to change at page 13, line 4 skipping to change at page 13, line 31
sendLocalAndRemote(5), sendLocalAndRemote(5),
sendLocalAndRemoteOk(6), sendLocalAndRemoteOk(6),
oamPeeringLocallyRejected(7), oamPeeringLocallyRejected(7),
oamPeeringRemotelyRejected(8), oamPeeringRemotelyRejected(8),
operational(9), operational(9),
nonOperHalfDuplex(10) nonOperHalfDuplex(10)
} }
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
Ethernet OAM MIB October 2006
"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 OA
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). Also, with a link fault indication, the value is linkFault(2). Also,
if the interface is not operational (ifOperStatus is not if the interface is not operational (ifOperStatus is not
up(1)), linkFault(2) is returned. Note that the object up(1)), linkFault(2) is returned. Note that the object
ifOperStatus may not be up(1) as a result of link failure or ifOperStatus may not be up(1) as a result of link failure or
administrative action (ifAdminState being down(2) or administrative action (ifAdminState being down(2) or
testing(3)). 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 OA
capable. The activeSendLocal(4) value 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 OA
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
oamPeeringLocallyRejected(7). If the OAM peering is allowed oamPeeringLocallyRejected(7). If the OAM peering is allowed
by the local device, the state moves to by the local device, the state moves to
sendLocalAndRemoteOk(6). Note that both the sendLocalAndRemoteOk(6). Note that both the
sendLocalAndRemote(5) and oamPeeringLocallyRejected(7) states sendLocalAndRemote(5) and oamPeeringLocallyRejected(7) states
fall within the state SEND_LOCAL_REMOTE of the Discovery state fall within the state SEND_LOCAL_REMOTE of the Discovery state
skipping to change at page 14, line 4 skipping to change at page 14, line 33
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
Discovery state diagram [802.3ah, Figure 57-5], with the Discovery state diagram [802.3ah, Figure 57-5], with the
difference being whether the remote OAM client has rejected difference being whether the remote OAM client has rejected
Ethernet OAM MIB October 2006
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 Since Ethernet OAM functions are not designed to work
skipping to change at page 14, line 37 skipping to change at page 15, line 17
active(2) active(2)
} }
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object configures the mode of OAM operation for this "This object configures the mode of OAM operation for this
Ethernet like interface. OAM on Ethernet interfaces may be in Ethernet like interface. OAM on Ethernet interfaces may be in
'active' mode or 'passive' mode. These two modes differ in 'active' mode or 'passive' mode. These two modes differ in
that active mode provides additional capabilities to initiate that active mode provides additional capabilities to initiate
monitoring activities with the remote OAM peer entity, while monitoring activities with the remote OAM peer entity, while
passive mode generally waits for the peer to initiate OAM passive mode generally waits for the peer to initiate OA
actions with it. As an example, an active OAM entity can put actions with it. As an example, an active OAM entity can put
the remote OAM entity in a loopback state, where a passive OAM the remote OAM entity in a loopback state, where a passive OA
entity cannot. entity cannot.
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(2)' unless it is known that default value should be 'active(2)' 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"
::= { dot3OamEntry 3 } ::= { dot3OamEntry 3 }
Ethernet OAM MIB October 2006
dot3OamMaxOamPduSize OBJECT-TYPE dot3OamMaxOamPduSize OBJECT-TYPE
SYNTAX Unsigned32 (64..1518) SYNTAX Unsigned32 (64..1518)
UNITS "octets" UNITS "octets"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The largest OAMPDU that the OAM entity supports. OAM "The largest OAMPDU that the OAM entity supports. OA
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(0..65535) SYNTAX Unsigned32(0..65535)
MAX-ACCESS read-only MAX-ACCESS read-only
skipping to change at page 15, line 51 skipping to change at page 16, line 34
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 Setting 'unidirectionalSupport(0)' indicates that the OA
entity supports the transmission of OAMPDUs on links that are entity supports the transmission of OAMPDUs on links that are
operating in undirectional mode (traffic flowing in one operating in undirectional mode (traffic flowing in one
Ethernet OAM MIB October 2006
direction only). Setting 'loopbackSupport(1)' indicates the direction only). Setting 'loopbackSupport(1)' indicates the
OAM entity can initiate and respond to loopback commands. OAM entity can initiate and respond to loopback commands.
Setting 'eventSupport(2)' indicates the OAM entity can send Setting 'eventSupport(2)' indicates the OAM entity can send
and receive Event Notification OAMPDUs. Setting and receive Event Notification OAMPDUs. Setting
'variableSupport(3)' indicates the OAM entity can send and 'variableSupport(3)' indicates the OAM entity can send and
receive Variable Request and Response OAMPDUs. 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 }
skipping to change at page 16, line 28 skipping to change at page 17, line 13
-- Ethernet OAM Peer group -- Ethernet OAM Peer group
-- --
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
"This table contains information about the OAM peer for a "This table contains information about the OAM peer for a
particular Ethernet like interface. OAM entities communicate particular Ethernet like interface. OAM entities communicate
with a single OAM peer entity on Ethernet links on which OAM with a single OAM peer entity on Ethernet links on which OA
is enabled and operating properly. There is one entry in this is enabled and operating properly. There is one entry in this
table for each entry in the dot3OamTable for which information table for each entry in the dot3OamTable for which information
on the peer OAM entity is available. on the peer OAM entity is available.
" "
::= { dot3OamObjects 2 } ::= { dot3OamObjects 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 OA
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. Entries are automatically created when information interface. Entries are automatically created when information
about the OAM peer entity becomes available, and automatically about the OAM peer entity becomes available, and automatically
deleted when the OAM peer entity is no longer in deleted when the OAM peer entity is no longer in
communication. Peer information is not available when communication. Peer information is not available when
dot3OamOperStatus is disabled(1), linkFault(2), dot3OamOperStatus is disabled(1), linkFault(2),
passiveWait(3), activeSendLocal(4). or nonOperHalfDuplex(10)). passiveWait(3), activeSendLocal(4), or nonOperHalfDuplex(10).
" "
INDEX { ifIndex } INDEX { ifIndex }
::= { dot3OamPeerTable 1 } ::= { dot3OamPeerTable 1 }
Ethernet OAM MIB October 2006
Dot3OamPeerEntry ::= Dot3OamPeerEntry ::=
SEQUENCE { SEQUENCE {
dot3OamPeerMacAddress MacAddress, dot3OamPeerMacAddress MacAddress,
dot3OamPeerVendorOui Dot3Oui, dot3OamPeerVendorOui EightOTwoOui,
dot3OamPeerVendorInfo Unsigned32, dot3OamPeerVendorInfo Unsigned32,
dot3OamPeerMode INTEGER, dot3OamPeerMode INTEGER,
dot3OamPeerMaxOamPduSize Unsigned32, dot3OamPeerMaxOamPduSize Unsigned32,
dot3OamPeerConfigRevision Unsigned32, dot3OamPeerConfigRevision Unsigned32,
dot3OamPeerFunctionsSupported BITS dot3OamPeerFunctionsSupported BITS
} }
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. derived from the most recently received OAMPDU.
" "
REFERENCE "[802.3ah], 30.3.6.1.5." REFERENCE "[802.3ah], 30.3.6.1.5."
::= { dot3OamPeerEntry 1 } ::= { dot3OamPeerEntry 1 }
skipping to change at page 17, line 29 skipping to change at page 18, line 16
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. derived from the most recently received OAMPDU.
" "
REFERENCE "[802.3ah], 30.3.6.1.5." REFERENCE "[802.3ah], 30.3.6.1.5."
::= { dot3OamPeerEntry 1 } ::= { dot3OamPeerEntry 1 }
dot3OamPeerVendorOui OBJECT-TYPE dot3OamPeerVendorOui OBJECT-TYPE
SYNTAX Dot3Oui SYNTAX EightOTwoOui
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 OA
entity. This value is initialized to three octets of zero entity. This value is initialized to three octets of zero
before any Local Information TLV is received. before any Local Information TLV is received.
" "
REFERENCE "[802.3ah], 30.3.6.1.16." REFERENCE "[802.3ah], 30.3.6.1.16."
::= { dot3OamPeerEntry 2 } ::= { 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.
vendor information field is within the Local Information TLV, The semantics of the vendor information field is proprietary
Ethernet OAM MIB October 2006 and specific to the vendor (identified by the
dot3OamPeerVendorOui). This information could, for example,
and can be used to determine additional information about the be used to identify a specific product or product family.
peer entity. The format of the vendor information is This value is initialized to zero before any Local
unspecified within the 32-bit field. This value is Information TLV is received.
initialized to zero before any Local Information TLV is
received.
" "
REFERENCE "[802.3ah], 30.3.6.1.17." REFERENCE "[802.3ah], 30.3.6.1.17."
::= { dot3OamPeerEntry 3 } ::= { dot3OamPeerEntry 3 }
dot3OamPeerMode OBJECT-TYPE dot3OamPeerMode OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
passive(1), passive(1),
active(2), active(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
skipping to change at page 19, line 4 skipping to change at page 19, line 43
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. A value of zero is returned if no Local Information the peer. A value of zero is returned if no Local Information
TLV has been received. Otherwise, the value of the OAM peer's TLV has been received. Otherwise, the value of the OAM peer's
maximum OAMPDU size is returned in this value. maximum OAMPDU size is returned in this value.
" "
REFERENCE "[802.3ah], 30.3.6.1.9." REFERENCE "[802.3ah], 30.3.6.1.9."
Ethernet OAM MIB October 2006
::= { dot3OamPeerEntry 5 } ::= { dot3OamPeerEntry 5 }
dot3OamPeerConfigRevision OBJECT-TYPE dot3OamPeerConfigRevision OBJECT-TYPE
SYNTAX Unsigned32(0..65535) 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 OA
this interface. The configuration revision can be determined this interface. The configuration revision can be determined
from the Revision field of the Local Information TLV of the from the Revision field of the Local Information TLV of the
most recently received Information OAMPDU with a Local most recently received Information OAMPDU with a Local
Information TLV. A value of zero is returned if no Local Information TLV. A value of zero is returned if no Local
Information TLV has been received. Information TLV has been received.
" "
REFERENCE "[802.3ah], 30.3.6.1.13." REFERENCE "[802.3ah], 30.3.6.1.13."
::= { dot3OamPeerEntry 6 } ::= { dot3OamPeerEntry 6 }
dot3OamPeerFunctionsSupported OBJECT-TYPE dot3OamPeerFunctionsSupported OBJECT-TYPE
skipping to change at page 20, line 4 skipping to change at page 20, line 44
receive path is known to be inoperable. If receive path is known to be inoperable. If
loopbackSupport(1) is set, then the peer OAM entity can send loopbackSupport(1) is set, then the peer OAM entity can send
and receive OAM loopback commands. If eventSupport(2) is set, and receive OAM loopback commands. If eventSupport(2) is set,
then the peer OAM entity can send and receive event OAMPDUs to then the peer OAM entity can send and receive event OAMPDUs to
signal various error conditions. If variableSupport(3) is set, signal various error conditions. If variableSupport(3) is set,
then the peer OAM entity can send and receive variable then the peer OAM entity can send and receive variable
requests to monitor attribute value as described in Clause 57 requests to monitor attribute value as described in Clause 57
of [802.3ah]. of [802.3ah].
The capabilities of the OAM peer can be determined from the The capabilities of the OAM peer can be determined from the
Ethernet OAM MIB October 2006
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. All zeros are returned if no Local Information TLV has TLV. All zeros are returned if no Local Information TLV has
yet been received. yet been received.
" "
REFERENCE "[802.3ah], REFERENCE 30.3.6.1.7." REFERENCE "[802.3ah], REFERENCE 30.3.6.1.7."
::= { dot3OamPeerEntry 7 } ::= { dot3OamPeerEntry 7 }
-- *************************************************************** -- ***************************************************************
-- --
skipping to change at page 21, line 4 skipping to change at page 21, line 44
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. Entries in the status for a single Ethernet like interface. Entries in the
table are automatically created whenever the local OAM entity table are automatically created whenever the local OAM entity
supports loopback capabilities. The loopback status on the supports loopback capabilities. The loopback status on the
interface can be determined from the dot3OamLoopbackStatus interface can be determined from the dot3OamLoopbackStatus
object. object.
" "
Ethernet OAM MIB October 2006
INDEX { ifIndex } INDEX { ifIndex }
::= { dot3OamLoopbackTable 1 } ::= { dot3OamLoopbackTable 1 }
Dot3OamLoopbackEntry ::= Dot3OamLoopbackEntry ::=
SEQUENCE { SEQUENCE {
dot3OamLoopbackStatus INTEGER, dot3OamLoopbackStatus INTEGER,
dot3OamLoopbackIgnoreRx INTEGER dot3OamLoopbackIgnoreRx INTEGER
} }
dot3OamLoopbackStatus OBJECT-TYPE dot3OamLoopbackStatus OBJECT-TYPE
skipping to change at page 21, line 40 skipping to change at page 22, line 34
MAX-ACCESS read-write 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).
The values initiatingLooopback(2) and terminatingLoopback(4) The values initiatingLoopback(2) and terminatingLoopback(4)
can be read or written. The other values can only be read - can be read or written. The other values can only be read -
they can never be written. Writing initiatingLoopback causes they can never be written. Writing initiatingLoopback causes
the local OAM entity to start the loopback process with its the local OAM entity to start the loopback process with its
peer. This value can only be written when the status is peer. This value can only be written when the status is
noLoopback(1). Writing the value initiatingLoopback(2) in any noLoopback(1). Writing the value initiatingLoopback(2) in any
other state has no effect. When in remoteLoopback(3), writing other state has no effect. When in remoteLoopback(3), writing
terminatingLoopback(4) causes the local OAM entity to initiate terminatingLoopback(4) causes the local OAM entity to initiate
the termination of the loopback state. Writing the termination of the loopback state. Writing
terminatingLoopack(4) in any other state has no effect. terminatingLoopack(4) in any other state has no effect.
If the OAM client initiates a looopback and has sent an If the OAM client initiates a loopback and has sent an
Loopback OAMPDU and is waiting for a response, where the local Loopback OAMPDU and is waiting for a response, where the local
parser and multiplexer states are DISCARD (see [802.3ah, parser and multiplexer states are DISCARD (see [802.3ah,
57.2.11.1]), the status is 'initiatingLoopback'. In this 57.2.11.1]), the status is 'initiatingLoopback'. In this
Ethernet OAM MIB October 2006
case, the local OAM entity has yet to receive any case, the local OAM entity has yet to receive any
acknowledgement that the remote OAM entity has received its acknowledgement that the remote OAM entity has received its
loopback command request. 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
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
skipping to change at page 23, line 4 skipping to change at page 24, line 4
"Since OAM loopback is a distruptive operation (user traffic "Since OAM loopback is a distruptive 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)).
" "
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"
Ethernet OAM MIB October 2006
::= { dot3OamLoopbackEntry 2 } ::= { dot3OamLoopbackEntry 2 }
-- *************************************************************** -- ***************************************************************
-- --
-- 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
"This table contains statistics for the OAM function on a "This table contains statistics for the OAM function on a
particular Ethernet like interface. There is an entry in the particular Ethernet like interface. There is an entry in the
table for every entry in the dot3OamTable. table for every entry in the dot3OamTable.
The counters in this table are defined as 32-bit entries to The counters in this table are defined as 32-bit entries to
match the counter size as defined in [802.3ah]. Given the OAM match the counter size as defined in [802.3ah]. Given the OA
protocol is a slow protocol, the counters increment at a slow protocol is a slow protocol, the counters increment at a slow
rate. rate.
" "
::= { dot3OamObjects 4 } ::= { 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
skipping to change at page 24, line 4 skipping to change at page 25, line 6
Dot3OamStatsEntry ::= Dot3OamStatsEntry ::=
SEQUENCE { SEQUENCE {
dot3OamInformationTx Counter32, dot3OamInformationTx Counter32,
dot3OamInformationRx Counter32, dot3OamInformationRx Counter32,
dot3OamUniqueEventNotificationTx Counter32, dot3OamUniqueEventNotificationTx Counter32,
dot3OamUniqueEventNotificationRx Counter32, dot3OamUniqueEventNotificationRx Counter32,
dot3OamDuplicateEventNotificationTx Counter32, dot3OamDuplicateEventNotificationTx Counter32,
dot3OamDuplicateEventNotificationRx Counter32, dot3OamDuplicateEventNotificationRx Counter32,
dot3OamLoopbackControlTx Counter32, dot3OamLoopbackControlTx Counter32,
dot3OamLoopbackControlRx Counter32, dot3OamLoopbackControlRx Counter32,
Ethernet OAM MIB October 2006
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
} }
skipping to change at page 25, line 4 skipping to change at page 26, line 8
" "
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"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
Ethernet OAM MIB October 2006
"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 Duplicate Event Notification transmissions are counted by
dot3OamDuplicateEventNotificationTx. dot3OamDuplicateEventNotificationTx.
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
skipping to change at page 25, line 34 skipping to change at page 26, line 36
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. Duplicate Event Notification receptions are counted transit. Duplicate Event Notification receptions are counted
by dot3OamDuplicateEventNotificationRx. by dot3OamDuplicateEventNotificationRx.
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
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
skipping to change at page 25, line 49 skipping to change at page 27, line 4
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
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
UNITS "frames" UNITS "frames"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
Ethernet OAM MIB October 2006
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.
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.
skipping to change at page 27, line 4 skipping to change at page 28, line 12
" "
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"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
Ethernet OAM MIB October 2006
"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.
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 }
skipping to change at page 28, line 4 skipping to change at page 29, line 14
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
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
Ethernet OAM MIB October 2006
this interface. this interface.
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
skipping to change at page 29, line 5 skipping to change at page 30, line 18
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
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.
Ethernet OAM MIB October 2006
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"
skipping to change at page 30, line 5 skipping to change at page 31, line 18
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
"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.
Ethernet OAM MIB October 2006
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 OA
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 Note that any Ethernet frame, not just OAMPDUs, may be dropped
by the OAM layer. This can occur when an OAMPDU takes by the OAM layer. This can occur when an OAMPDU takes
precedence over a 'normal' frame resulting in the 'normal' precedence over a 'normal' frame resulting in the 'normal'
frame being dropped. 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.
skipping to change at page 31, line 4 skipping to change at page 32, line 18
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 Notification OAMPDUs to indicate various link problems. Event Notification OAMPDUs to indicate various link problems.
This table contains the mechanisms to enable Event This table contains the mechanisms to enable Event
Notifications and configure the thresholds to generate the Notifications and configure the thresholds to generate the
Ethernet OAM MIB October 2006
standard Ethernet OAM events. There is one entry in the table standard Ethernet OAM events. There is one entry in the table
for every entry in dot3OamTable that supports OAM events for every entry in dot3OamTable that supports OAM events
(where dot3OamFunctionsSupported includes the eventSupport (where dot3OamFunctionsSupported includes the eventSupport
bit set). The values in the table are maintained across bit set). The values in the table are maintained across
changes to dot3OamOperStatus. changes to dot3OamOperStatus.
The standard threshold crossing events are: 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 (for example, 1,000 symbols defined by a number of symbols (for example, 1,000 symbols
skipping to change at page 31, line 42 skipping to change at page 33, line 9
enabled/disabled via this table. enabled/disabled via this table.
" "
::= { dot3OamObjects 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
"Entries are automatically created and deleted from this "Entries are automatically created and deleted from this
table, and exist whenever the OAM entity supports Ethernet OAM table, and exist whenever the OAM entity supports Ethernet OA
events (as indicated by the eventSupport bit in events (as indicated by the eventSupport bit in
dot3OamFunctionsSuppported). Values in the table are dot3OamFunctionsSuppported). Values in the table are
maintained across changes to the value of dot3OamOperStatus. 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, and when sends Event Notification OAMPDUs to its OAM peer, and when
certain event flags are set or cleared in OAMPDUs. certain event flags are set or cleared in OAMPDUs.
" "
INDEX { ifIndex } INDEX { ifIndex }
::= { dot3OamEventConfigTable 1 } ::= { dot3OamEventConfigTable 1 }
Dot3OamEventConfigEntry ::= Dot3OamEventConfigEntry ::=
Ethernet OAM MIB October 2006
SEQUENCE { SEQUENCE {
dot3OamErrSymPeriodWindowHi Unsigned32, dot3OamErrSymPeriodWindowHi Unsigned32,
dot3OamErrSymPeriodWindowLo Unsigned32, dot3OamErrSymPeriodWindowLo Unsigned32,
dot3OamErrSymPeriodThresholdHi Unsigned32, dot3OamErrSymPeriodThresholdHi Unsigned32,
dot3OamErrSymPeriodThresholdLo Unsigned32, dot3OamErrSymPeriodThresholdLo Unsigned32,
dot3OamErrSymPeriodEvNotifEnable TruthValue, dot3OamErrSymPeriodEvNotifEnable TruthValue,
dot3OamErrFramePeriodWindow Unsigned32, dot3OamErrFramePeriodWindow Unsigned32,
dot3OamErrFramePeriodThreshold Unsigned32, dot3OamErrFramePeriodThreshold Unsigned32,
dot3OamErrFramePeriodEvNotifEnable TruthValue, dot3OamErrFramePeriodEvNotifEnable TruthValue,
dot3OamErrFrameWindow Unsigned32, dot3OamErrFrameWindow Unsigned32,
skipping to change at page 33, line 4 skipping to change at page 34, line 23
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
SYNTAX Unsigned32 SYNTAX Unsigned32
UNITS "symbols" UNITS "symbols"
MAX-ACCESS read-write MAX-ACCESS read-write
Ethernet OAM MIB October 2006
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
skipping to change at page 34, line 4 skipping to change at page 35, line 26
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. If the threshold value is zero, then an Event symbol errors. If the threshold value is zero, then an Event
Notification OAMPDU is sent periodically (at the end of every Notification OAMPDU is sent periodically (at the end of every
window). This can be used as an asynchronous notification to window). This can be used as an asynchronous notification to
Ethernet OAM MIB October 2006
the peer OAM entity of the statistics related to this the peer OAM entity of the statistics related to this
threshold crossing alarm. 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
skipping to change at page 35, line 4 skipping to change at page 36, line 28
dot3OamErrSymPeriodEvNotifEnable OBJECT-TYPE dot3OamErrSymPeriodEvNotifEnable OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"If true, the OAM entity should send an Event Notification "If true, the OAM entity should send an Event Notification
OAMPDU when an Errored Symbol Period Event occurs. OAMPDU when an Errored Symbol Period Event occurs.
By default, this object should have the value true 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
Ethernet OAM MIB October 2006
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
skipping to change at page 36, line 4 skipping to change at page 37, line 30
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 }
dot3OamErrFramePeriodEvNotifEnable OBJECT-TYPE dot3OamErrFramePeriodEvNotifEnable OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
Ethernet OAM MIB October 2006
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"If true, the OAM entity should send an Event Notification "If true, the OAM entity should send an Event Notification
OAMPDU when an Errored Frame Period Event occurs. OAMPDU when an Errored Frame Period Event occurs.
By default, this object should have the value true 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.
skipping to change at page 36, line 35 skipping to change at page 38, line 12
"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 seconds), an Event Notification OAMPDU should be generated
with an Errored Frame Event TLV indicating the threshold has with an Errored Frame Event TLV indicating the threshold has
been 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"
DEFVAL { 10 }
::= { dot3OamEventConfigEntry 9 } ::= { dot3OamEventConfigEntry 9 }
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. If the be triggered. The default value is one frame error. If the
threshold value is zero, then an Event Notification OAMPDU is threshold value is zero, then an Event Notification OAMPDU is
sent periodically (at the end of every window). This can be sent periodically (at the end of every window). This can be
used as an asynchronous notification to the peer OAM entity of used as an asynchronous notification to the peer OAM entity of
the statistics related to this threshold crossing alarm. the statistics related to this threshold crossing alarm.
If dot3OamErrFrameThreshold frame errors occur within a window If dot3OamErrFrameThreshold frame errors occur within a window
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
Ethernet OAM MIB October 2006
window. window.
" "
REFERENCE "[802.3ah], 30.3.6.1.36" REFERENCE "[802.3ah], 30.3.6.1.36"
DEFVAL { 1 }
::= { dot3OamEventConfigEntry 10 } ::= { dot3OamEventConfigEntry 10 }
dot3OamErrFrameEvNotifEnable OBJECT-TYPE dot3OamErrFrameEvNotifEnable OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"If true, the OAM entity should send an Event Notification "If true, the OAM entity should send an Event Notification
OAMPDU when an Errored Frame Event occurs. OAMPDU when an Errored Frame Event occurs.
skipping to change at page 37, line 23 skipping to change at page 39, line 4
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"If true, the OAM entity should send an Event Notification "If true, the OAM entity should send an Event Notification
OAMPDU when an Errored Frame Event occurs. OAMPDU when an Errored Frame Event occurs.
By default, this object should have the value true 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.
" "
DEFVAL { true }
::= { 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"
DEFVAL { 100 }
::= { dot3OamEventConfigEntry 12 } ::= { dot3OamEventConfigEntry 12 }
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. If the threshold value is zero, then an Event second. If the threshold value is zero, then an Event
Notification OAMPDU is sent periodically (at the end of every Notification OAMPDU is sent periodically (at the end of every
window). This can be used as an asynchronous notification to window). This can be used as an asynchronous notification to
Ethernet OAM MIB October 2006
the peer OAM entity of the statistics related to this the peer OAM entity of the statistics related to this
threshold crossing alarm. 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"
DEFVAL { 1 }
::= { dot3OamEventConfigEntry 13 } ::= { dot3OamEventConfigEntry 13 }
dot3OamErrFrameSecsEvNotifEnable OBJECT-TYPE dot3OamErrFrameSecsEvNotifEnable OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"If true, the local OAM entity should send an Event "If true, the local OAM entity should send an Event
Notification OAMPDU when an Errored Frame Seconds Event Notification OAMPDU when an Errored Frame Seconds Event
occurs. occurs.
By default, this object should have the value true for By default, this object should have the value true for
skipping to change at page 38, line 32 skipping to change at page 40, line 18
DESCRIPTION DESCRIPTION
"If true, the local OAM entity should send an Event "If true, the local OAM entity should send an Event
Notification OAMPDU when an Errored Frame Seconds Event Notification OAMPDU when an Errored Frame Seconds Event
occurs. occurs.
By default, this object should have the value true 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.
" "
DEFVAL { true }
::= { dot3OamEventConfigEntry 14 } ::= { dot3OamEventConfigEntry 14 }
dot3OamDyingGaspEnable OBJECT-TYPE dot3OamDyingGaspEnable OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"If true, the local OAM entity should attempt to indicate a "If true, the local OAM entity should attempt to indicate a
dying gasp via the OAMPDU flags field to its peer OAM entity dying gasp via the OAMPDU flags field to its peer OAM entity
when a dying gasp event occurs. The exact definition of a when a dying gasp event occurs. The exact definition of a
dying gasp event is implementation dependent. If the system dying gasp event is implementation dependent. If the system
does not support dying gasp capability, setting this object does not support dying gasp capability, setting this object
has no effect, and reading the object should always result in has no effect, and reading the object should always result in
'false'. 'false'.
By default, this object should have the value true 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.
" "
DEFVAL { true }
::= { dot3OamEventConfigEntry 15 } ::= { dot3OamEventConfigEntry 15 }
dot3OamCriticalEventEnable OBJECT-TYPE dot3OamCriticalEventEnable OBJECT-TYPE
Ethernet OAM MIB October 2006
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"If true, the local OAM entity should attempt to indicate a "If true, the local OAM entity should attempt to indicate a
critical event via the OAMPDU flags to its peer OAM entity critical event via the OAMPDU flags to its peer OAM entity
when a critical event occurs. The exact definition of a when a critical event occurs. The exact definition of a
critical event is implementation dependent. If the system critical event is implementation dependent. If the system
does not support critical event capability, setting this does not support critical event capability, setting this
object has no effect, and reading the object should always object has no effect, and reading the object should always
result in 'false'. result in 'false'.
By default, this object should have the value true 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.
" "
DEFVAL { true }
::= { dot3OamEventConfigEntry 16 } ::= { dot3OamEventConfigEntry 16 }
-- ************************************************************** -- **************************************************************
-- --
-- Ethernet OAM Event Log 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
skipping to change at page 40, line 4 skipping to change at page 41, line 44
This table contains both threshold crossing events and This table contains both threshold crossing events and
non-threshold crossing events. The parameters for the non-threshold crossing events. The parameters for the
threshold window, threshold value, and actual value threshold window, threshold value, and actual value
(dot3OamEventLogWindowXX, dot3OamEventLogThresholdXX, (dot3OamEventLogWindowXX, dot3OamEventLogThresholdXX,
dot3OamEventLogValue) are only applicable to threshold dot3OamEventLogValue) are only applicable to threshold
crossing events, and are returned as all F's (2^32 - 1) for crossing events, and are returned as all F's (2^32 - 1) for
non-threshold crossing events. non-threshold crossing events.
Entries in the table are automatically created when such Entries in the table are automatically created when such
events are detected. The size of the table is implementation events are detected. The size of the table is implementation
Ethernet OAM MIB October 2006
dependent. When the table reaches its maximum size, older dependent. When the table reaches its maximum size, older
entries are automatically deleted to make room for newer entries are automatically deleted to make room for newer
entries. entries.
" "
::= { dot3OamObjects 6 } ::= { 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 DESCRIPTION
"An entry in the dot3OamEventLogTable. Entries are "An entry in the dot3OamEventLogTable. Entries are
automatically created whenever Ethernet OAM events occur at automatically created whenever Ethernet OAM events occur at
the local OAM entity, and when Event Notification OAMPDUs are the local OAM entity, and when Event Notification OAMPDUs are
received at the local OAM entity (indicating events have received at the local OAM entity (indicating events have
occurred at the peer OAM entity). The size of the table is occurred at the peer OAM entity). The size of the table is
skipping to change at page 40, line 35 skipping to change at page 42, line 27
each new entry, and when the maximum value is reached the each new entry, and when the maximum value is reached the
value restarts at zero. value restarts at zero.
" "
INDEX { ifIndex, dot3OamEventLogIndex } INDEX { ifIndex, dot3OamEventLogIndex }
::= { dot3OamEventLogTable 1 } ::= { dot3OamEventLogTable 1 }
Dot3OamEventLogEntry ::= Dot3OamEventLogEntry ::=
SEQUENCE { SEQUENCE {
dot3OamEventLogIndex Unsigned32, dot3OamEventLogIndex Unsigned32,
dot3OamEventLogTimestamp TimeStamp, dot3OamEventLogTimestamp TimeStamp,
dot3OamEventLogOui Dot3Oui, dot3OamEventLogOui EightOTwoOui,
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(1..4294967295)
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An arbitrary integer for identifiying individual events "An arbitrary integer for identifying individual events
within the event log. " within the event log. "
::= { dot3OamEventLogEntry 1 } ::= { dot3OamEventLogEntry 1 }
Ethernet OAM MIB October 2006
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
accurately retrieved from sysUpTime. For remotely generated accurately retrieved from sysUpTime. For remotely generated
events, the time of the event is indicated by the reception of events, the time of the event is indicated by the reception of
the Event Notification OAMPDU indicating the event occurred on the Event Notification OAMPDU indicating the event occurred on
the peer. A system may attempt to adjust the timestamp value the peer. A system may attempt to adjust the timestamp value
to more accurately reflect the time of the event at the peer to more accurately reflect the time of the event at the peer
OAM entity by using other information, such as that found in OAM entity by using other information, such as that found in
the timestamp found of the Event Notification TLVs, which the timestamp found of the Event Notification TLVs, which
provides an indication of the relative time between events at provides an indication of the relative time between events at
the peer entity. " the peer entity. "
::= { dot3OamEventLogEntry 2 } ::= { dot3OamEventLogEntry 2 }
dot3OamEventLogOui OBJECT-TYPE dot3OamEventLogOui OBJECT-TYPE
SYNTAX Dot3Oui SYNTAX EightOTwoOui
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
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 }
skipping to change at page 42, line 4 skipping to change at page 43, line 49
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),
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
Ethernet OAM MIB October 2006
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 71874 (0x0180C2 in hex), then some other When the OUI is not 71874 (0x0180C2 in hex), then some other
organization has defined the event space. If event subtyping organization has defined the event space. If event subtyping
is known to the implementation, it may be reflected here. is known to the implementation, it may be reflected here.
Otherwise, this value should return all F's (2^32 - 1). Otherwise, this value should return all F's (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."
skipping to change at page 43, line 4 skipping to change at page 45, line 5
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
SYNTAX Unsigned32 SYNTAX Unsigned32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
Ethernet OAM MIB October 2006
"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 (for value was measured for the threshold crossing event (for
example, 5, when 11 occurrences happened in 5 seconds while example, 5, when 11 occurrences happened in 5 seconds while
the threshold 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
skipping to change at page 44, line 5 skipping to change at page 46, line 7
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 (for example, 10, crossed for the threshold crossing event (for example, 10,
when 11 occurrences happened in 5 seconds while the threshold when 11 occurrences happened in 5 seconds while the threshold
was 10). The two objects are combined as: was 10). The two objects are combined as:
Ethernet OAM MIB October 2006
dot3OamEventLogThreshold = ((2^32) * dot3OamEventLogThresholdHi) dot3OamEventLogThreshold = ((2^32) * dot3OamEventLogThresholdHi)
+ dot3OamEventLogThresholdLo + dot3OamEventLogThresholdLo
Otherwise, this value is returned as all F's (2^32 - 1) 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
skipping to change at page 45, line 4 skipping to change at page 47, line 8
For threshold crossing events, since multiple occurrences may For threshold crossing events, since multiple occurrences may
be required to cross the threshold, these values are likely be required to cross the threshold, these values are likely
different. This value represents the total number of times different. This value represents the total number of times
this event has happened since the last reset (for example, this event has happened since the last reset (for example,
3253, when 3253 symbol errors have occurred since the last 3253, when 3253 symbol errors have occurred since the last
reset, which has resulted in 51 symbol error threshold reset, which has resulted in 51 symbol error threshold
crossing events since the last reset). 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 11 } ::= { dot3OamEventLogEntry 11 }
Ethernet OAM MIB October 2006
dot3OamEventLogEventTotal OBJECT-TYPE dot3OamEventLogEventTotal OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Each Event Notification TLV contains a running total of the "Each Event Notification TLV contains a running total of the
number of times an event has occurred, as well as the number number of times an event has occurred, as well as the number
of times an Event Notification for the event has been of times an Event Notification for the event has been
transmitted. For non-threshold crossing events, the number of transmitted. For non-threshold crossing events, the number of
skipping to change at page 46, line 4 skipping to change at page 48, line 11
dot3OamEventLogThresholdLo, dot3OamEventLogThresholdLo,
dot3OamEventLogValue, dot3OamEventLogValue,
dot3OamEventLogRunningTotal, dot3OamEventLogRunningTotal,
dot3OamEventLogEventTotal dot3OamEventLogEventTotal
} }
STATUS current STATUS current
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,
Ethernet OAM MIB October 2006
while a remote threshold crossing event is detected by the while a remote threshold crossing event is detected by the
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 OAM entity can be derived from extracting the ifIndex from
the variable bindings. The objects in the notification the variable bindings. The objects in the notification
correspond to the values in a row instance of in the correspond to the values in a row instance of in the
skipping to change at page 47, line 4 skipping to change at page 49, line 13
dot3OamEventLogTable. 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."
::= { dot3OamNotifications 2 } ::= { dot3OamNotifications 2 }
-- *************************************************************** -- ***************************************************************
-- --
-- Ethernet OAM Compliance group -- Ethernet OAM Compliance group
-- --
Ethernet OAM MIB October 2006
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
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
"This group is mandatory for all IEEE 802.3 OAM "This group is mandatory for all IEEE 802.3 OA
implementations that support loopback functionality. " implementations that support loopback functionality. "
GROUP dot3OamErrSymbolPeriodEventGroup GROUP dot3OamErrSymbolPeriodEventGroup
DESCRIPTION DESCRIPTION
"This group is mandatory for all IEEE 802.3 OAM "This group is mandatory for all IEEE 802.3 OA
implementations that support event functionality. " implementations that support event functionality. "
GROUP dot3OamErrFramePeriodEventGroup GROUP dot3OamErrFramePeriodEventGroup
DESCRIPTION DESCRIPTION
"This group is mandatory for all IEEE 802.3 OAM "This group is mandatory for all IEEE 802.3 OA
implementations that support event functionality. " implementations that support event functionality. "
GROUP dot3OamErrFrameEventGroup GROUP dot3OamErrFrameEventGroup
DESCRIPTION DESCRIPTION
"This group is mandatory for all IEEE 802.3 OAM "This group is mandatory for all IEEE 802.3 OA
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 OA
implementations that support event functionality. " implementations that support event functionality. "
GROUP dot3OamFlagEventGroup GROUP dot3OamFlagEventGroup
DESCRIPTION DESCRIPTION
"This group is optional for all IEEE 802.3 OAM "This group is optional for all IEEE 802.3 OA
implementations. The ability to send critical events or dying implementations. The ability to send critical events or dying
gasp events is not required in any system." gasp events is not required in any system."
Ethernet OAM MIB October 2006
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 OA
implementations. Entries in this table are dependent on what implementations. Entries in this table are dependent on what
event functionality is supported in the local OAM event functionality is supported in the local OA
implementation. At least one type of event must be supported implementation. At least one type of event must be supported
for entries to appear in this table. " 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 OA
implementations. Since the information in the notifications implementations. Since the information in the notifications
is dependent on the dot3OamEventLogTable, that table must be is dependent on the dot3OamEventLogTable, that table must be
implemented for notifications. " implemented for notifications. "
::= { dot3OamCompliances 1} ::= { dot3OamCompliances 1}
dot3OamControlGroup OBJECT-GROUP dot3OamControlGroup OBJECT-GROUP
OBJECTS { dot3OamAdminState, OBJECTS { dot3OamAdminState,
dot3OamOperStatus, dot3OamOperStatus,
dot3OamMode, dot3OamMode,
skipping to change at page 49, line 4 skipping to change at page 51, line 17
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. "
::= { dot3OamGroups 2 } ::= { dot3OamGroups 2 }
dot3OamStatsBaseGroup OBJECT-GROUP dot3OamStatsBaseGroup OBJECT-GROUP
OBJECTS { dot3OamInformationTx, OBJECTS { dot3OamInformationTx,
Ethernet OAM MIB October 2006
dot3OamInformationRx, dot3OamInformationRx,
dot3OamUniqueEventNotificationTx, dot3OamUniqueEventNotificationTx,
dot3OamUniqueEventNotificationRx, dot3OamUniqueEventNotificationRx,
dot3OamDuplicateEventNotificationTx, dot3OamDuplicateEventNotificationTx,
dot3OamDuplicateEventNotificationRx, dot3OamDuplicateEventNotificationRx,
dot3OamLoopbackControlTx, dot3OamLoopbackControlTx,
dot3OamLoopbackControlRx, dot3OamLoopbackControlRx,
dot3OamVariableRequestTx, dot3OamVariableRequestTx,
dot3OamVariableRequestRx, dot3OamVariableRequestRx,
dot3OamVariableResponseTx, dot3OamVariableResponseTx,
skipping to change at page 50, line 4 skipping to change at page 52, line 19
dot3OamErrSymPeriodThresholdHi, dot3OamErrSymPeriodThresholdHi,
dot3OamErrSymPeriodThresholdLo, dot3OamErrSymPeriodThresholdLo,
dot3OamErrSymPeriodEvNotifEnable dot3OamErrSymPeriodEvNotifEnable
} }
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 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
Ethernet OAM MIB October 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 5 } ::= { dot3OamGroups 5 }
dot3OamErrFramePeriodEventGroup OBJECT-GROUP dot3OamErrFramePeriodEventGroup OBJECT-GROUP
OBJECTS { dot3OamErrFramePeriodWindow, OBJECTS { dot3OamErrFramePeriodWindow,
dot3OamErrFramePeriodThreshold, dot3OamErrFramePeriodThreshold,
dot3OamErrFramePeriodEvNotifEnable dot3OamErrFramePeriodEvNotifEnable
} }
STATUS current STATUS current
skipping to change at page 51, line 4 skipping to change at page 53, line 20
} }
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
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 }
Ethernet OAM MIB October 2006
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 }
skipping to change at page 52, line 4 skipping to change at page 54, line 19
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 occured
on a specified Ethernet link. " on a specified Ethernet link. "
::= { dot3OamGroups 11 } ::= { dot3OamGroups 11 }
END END
7. Security Considerations 7. Security Considerations
Ethernet OAM MIB October 2006
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 authentication mechanisms. It should be used in environments
either this interface information is not considered sensitive, or where either this interface information is not considered sensitive,
where the facility terminations are protected. By default, OAM is or 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.
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
skipping to change at page 53, line 4 skipping to change at page 55, line 25
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
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.
Ethernet OAM MIB October 2006
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 via OAM events is also available via OA
OAM Variable Requests. Access to this information via either OAM Variable Requests. Access to this information via either OAM events
events or Variable Requests is controlled by the dot3OamAdminState or Variable Requests is controlled by the dot3OamAdminState and
and dot3OamMode objects. As mentioned previously, inadequate dot3OamMode objects. As mentioned previously, inadequate protection
protection of these variables can result in access to link of these variables can result in access to link information and
information and functions. functions.
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
skipping to change at page 54, line 5 skipping to change at page 56, line 24
---------- ----------------- ---------- -----------------
dot3OamMIB { mib-2 XXX } dot3OamMIB { mib-2 XXX }
Editor's Note (to be removed prior to publication): the IANA is 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 requested to assign a value for "XXX" under the 'mib-2' subtree and
to record the assignment in the SMI Numbers registry. When the to record the assignment in the SMI Numbers registry. When the
assignment has been made, the RFC Editor is asked to replace "XXX" assignment has been made, the RFC Editor is asked to replace "XXX"
(here and in the MIB module) with the assigned value and to remove (here and in the MIB module) with the assigned value and to remove
this note. this note.
Ethernet OAM MIB October 2006
9. References 9. References
9.1 Normative References 9.1 Normative References
[802.3ah] Institute of Electrical and Electronic Engineers, IEEE Std [802.3ah] Institute of Electrical and Electronic Engineers, IEEE
802.3ah-2004, "Part 3: Carrier Sense Multiple Access with Collision Std 802.3ah-2004, "Part 3: Carrier Sense Multiple Access
Detection (CSMA/CD) Access Method and Physical Layer Specifications - with Collision Detection (CSMA/CD) Access Method and
Amendment: Media Access Control Parameters, Physical Layers and Physical Layer Specifications - Amendment: Media Access
Management Parameters for Subscriber Access Networks", October 2004. Control Parameters, Physical Layers and 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
Collision Detection (CSMA/CD) Access Method and Physical Layer Access with Collision Detection (CSMA/CD) Access Method
Specifications - Draft amendment to - Information technology - and Physical Layer Specifications - Draft amendment to -
Telecommunications and information exchange between systems - Local Information technology - Telecommunications and
and metropolitan area networks - Specific requirements - Part 3: information exchange between systems - Local and
Carrier sense multiple access with collision detection (CSMA/CD) metropolitan area networks - Specific requirements - Part
access method and physical layer specifications - Media Access 3: Carrier sense multiple access with collision detection
Control Parameters, Physical Layers and Management Parameters", March (CSMA/CD) access method and physical layer specifications
2002. - Media Access Control Parameters, Physical Layers and
Management Parameters", March 2002.
[802.3-2005] Institute of Electrical and Electronic Engineers, IEEE [802.3-2005] Institute of Electrical and Electronic Engineers, IEEE
Std 802.3-2005, "IEEE Standard for Carrier Sense Multiple Access with Std 802.3-2005, "IEEE Standard for Carrier Sense Multiple
Collision Detection (CSMA/CD) Access Method and Physical Layer Access with Collision Detection (CSMA/CD) Access Method
Specifications - Draft amendment to - Information technology - and Physical Layer Specifications - Draft amendment to -
Telecommunications and information exchange between systems - Local Information technology - Telecommunications and
and metropolitan area networks - Specific requirements - Part 3: information exchange between systems - Local and
Carrier sense multiple access with collision detection (CSMA/CD) metropolitan area networks - Specific requirements - Part
access method and physical layer specifications - Media Access 3: Carrier sense multiple access with collision detection
Control Parameters, Physical Layers and Management Parameters", (CSMA/CD) access method and physical layer specifications
December 2005. - 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
Architecture and Overview", March 2002. Networks: Architecture and Overview", March 2002.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
[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
Information Version 2 (SMIv2)", STD 58, RFC 2578, April 1999. Management Information Version 2 (SMIv2)", STD 58, RFC
2578, April 1999.
[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
SMIv2", STD 58, RFC 2579, April 1999. Conventions for 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.
Ethernet OAM MIB October 2006
[RFC2586] Bierman, A., McCloghrie, K., Presuhn, R., "Textual [RFC2856] Bierman, A., McCloghrie, K., Presuhn, R., "Textual
Conventions for Additional High Capacity Data Types", RFC 2856, June Conventions for Additional High Capacity Data Types", RFC
2000. 2856, June 2000.
[RFC2863] McCloghrie, K., Kastenholz, F., "The Interfaces Group [RFC2863] McCloghrie, K., Kastenholz, F., "The Interfaces Group
MIB", RFC 2863, June 2000. MIB", RFC 2863, June 2000.
9.2 Informative References 9.2 Informative References
[802.3ah-copper] Beili, Ed, "Ethernet in the First Mile Copper [802.3ah-copper] Beili, Ed, "Ethernet in the First Mile Copper
(EFMCu) Interfaces MIB", draft-ietf-hubmib-efm-cu-05.txt, March 2006. (EFMCu) Interfaces MIB", draft-ietf-hubmib-efm-cu-05.txt,
March 2006.
[802.3ah-epon] Khermosh, Lior, "Managed Object of EPON", draft-ietf [802.3ah-epon] Khermosh, Lior, "Managed Object of EPON", draft-ietf
hubmib-efm-epon-mib-04.txt, February 2006. 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
Management Framework", RFC 3410, December 2003. Standard 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
Medium Attachment Units (MAUs)", RFC 3636, September 2003.
10. 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
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)
skipping to change at page 56, line 4 skipping to change at page 58, line 34
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)
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
Ethernet OAM MIB October 2006
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 (Ex-Chair, IETF HUBMIB WG)
Jonathan Thatcher Jonathan Thatcher
Geoff Thompson Geoff Thompson
11. 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 529 Davis Drive
Phone: +1-919-991-5460 Durham, NC 27713
Email: msquire at hatterasnetworks dot com Email: msquire at hatterasnetworks dot com
12. 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
skipping to change at page 57, line 4 skipping to change at page 59, line 35
http://www.ietf.org/ipr. http://www.ietf.org/ipr.
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 this standard. Please address the information to the IETF at
ietf-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
Ethernet OAM MIB October 2006
document. For more information consult the online list of claimed document. For more information consult the online list of claimed
rights. rights.
13. Copyright Statement 13. Copyright Statement
Copyright (C) The Internet Society (2006). Copyright (C) The IETF Trust (2007).
This document is subject to the rights, licenses and restrictions This document is subject to the rights, licenses and restrictions
contained in BCP 78, and except as set forth therein, the authors contained in BCP 78, and except as set forth therein, the authors
retain all their rights. retain all their rights.
This document and the information contained herein are provided This document and the information contained herein are provided
on an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE on an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE
REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE
THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, IETF TRUST AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL
EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY
THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY
ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A
PARTICULAR PURPOSE. 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. 152 change blocks. 
254 lines changed or deleted 161 lines changed or added

This html diff was produced by rfcdiff 1.33. The latest version is available from http://tools.ietf.org/tools/rfcdiff/