draft-ietf-hubmib-efm-mib-00.txt   draft-ietf-hubmib-efm-mib-01.txt 
Ethernet Interfaces and Hub MIB WG Matt Squire Ethernet Interfaces and Hub MIB WG
Internet Draft Hatteras Networks Internet Draft Matt Squire
February 2004 Expires Aug 2004 Document: draft-ietf-hubmib-efm-mib-01.txt Hatteras Networks
Expires: December 2004 June, 2004
Ethernet in the First Mile (EFM) Common MIB Ethernet in the First Mile (EFM) OAM MIB
draft-ietf-hubmib-efm-mib-00.txt
Status of this Memo Status of this Memo
By submitting this Internet-Draft, I certify that any applicable
patent or other IPR claims of which I am aware have been disclosed,
and any of which I become aware will be disclosed, in accordance with
RFC 3668 [RFC3668].
This document is an Internet-Draft and is in full conformance with This document is an Internet-Draft and is in full conformance with
all provisions of Section 10 of RFC2026 [1]. all provisions of Section 10 of RFC 2026 [RFC2026].
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 other Task Force (IETF), its areas, and its working groups. Note that
groups may also distribute working documents as Internet-Drafts. other groups may also distribute working documents as Internet
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.
Abstract Abstract
This memo defines a portion of the Management Information Base (MIB) This document defines objects for managing Operations,
for use with network management protocols in the Internet community. Administration, and Maintenance (OAM) capabilities on Ethernet-like
This document proposes an extension to the Ethernet-like Interfaces interfaces conformant to the Ethernet OAM functionality defined in
MIB for the capability to manage Ethernet-in-the-First-Mile (EFM) [802.3ah]. The Ethernet OAM functionality is complementary to SNMP
devices. management in that it is focused on a small set of link-specific
functions for Ethernet interfaces. This document defines objects for
controlling those link OAM functions, and on providing mechanisms to
take status and input from Ethernet OAM and feed it into a larger
TCP/IP network management system.
1 Introduction Conventions used in this document
New capabilities have been added to Ethernet like interfaces within EFM OAM MIB June 2004
the IEEE P802.3ah project for Ethernet in the First Mile (EFM). This
memo defines a portion of the Management Information Base (MIB) for
use with network management protocols in the Internet community to
manage the new capabilities of EFM Ethernet interfaces.
1.1 Specification of Requirements The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
draft-ietf-hubmib-efm-mib-00.txt February 2004 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119 [RFC2119].
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL Table of Contents
NOT","SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in
this document are to be interpreted as described in RFC 2119.
2 The Internet-Standard Management Framework 1. Introduction...................................................2
2. The Internet-Standard Management Framework.....................2
3. Overview.......................................................3
3.1 Remote fault indication....................................4
3.2 Link monitoring............................................4
3.3 Remote loopback............................................4
4. Relation to the Other MIBs.....................................5
4.1 Relation to other SNMP MIBs................................5
4.2 IANA Considerations........................................5
4.3 Mapping of IEEE 802.3ah Managed Objects....................5
5. MIB Structure..................................................7
6. MIB Definition.................................................7
7. Security Considerations.......................................54
8. References....................................................55
8.1 Normative References......................................55
8.2 Informative References....................................56
9. Acknowledgments...............................................57
10. Author's Address.............................................57
11. Intellectual Property Statement..............................58
12. Copyright Statement..........................................58
1. Introduction
The IEEE 802.3ah Ethernet in the First Mile (EFM) task force added
new management capabilities to Ethernet like interfaces. These
management capabilities were introduced to provide some basic OAM
function on Ethernet media. The defined functionality includes
discovery, error signaling, loopback, and link monitoring. This memo
defines a portion of the Management Information Base (MIB) for use
with network management protocols in the Internet community to manage
these new EFM interface capabilities.
2. The Internet-Standard Management Framework
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).
EFM OAM MIB June 2004
Objects in the MIB are defined using the mechanisms defined in the Objects in the MIB are defined using the mechanisms defined in the
Structure of Management Information (SMI). This memo specifies a MIB Structure of Management Information (SMI). This memo specifies a MIB
module that is compliant to the SMIv2, which is described in STD 58, module that is compliant to the SMIv2, which is described in STD 58,
RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580
[RFC2580]. [RFC2580].
3 Overview 3. Overview
Ethernet networks have evolved over time from an enterprise backbone Ethernet networks have evolved over the past 30 years from simple
to a variety of other applications. The IEEE P802.3ah task force has LANs to a variety of other applications, including wide area
defined extensions to the Ethernet standard for Ethernet deployments networks. To address some of these emerging markets, the IEEE
in the access space. 802.3ah task force defined additional clauses for the IEEE 802.3
standard [802.3-2002] to better address Ethernet deployments in the
public access network.
The Ethernet-in-the-First-Mile (EFM) task force has focused its The Ethernet in the First Mile (EFM) task force was focused on four
efforts into four categories: optics, copper, Ethernet passive somewhat independent objectives to better address Ethernet access
optical networks (Ethernet PON, or EPON), and operations, deployments: optics, copper, Ethernet passive optical networks
administration, and maintenance (OAM). (Ethernet PON, or EPON), and operations, administration, and
maintenance (OAM). The optics sub-taskforce developed new optical
physical layers that better served the long-reach outside plant
networks typically found in the access network, including developing
physical layers that operate up to 20Km and supporting the
environmental conditions of outside deployments. The copper sub
taskforce developed two new physical layers that run Ethernet
natively over existing twisted pair wires that have been supporting
voice services for decades. The EPON sub-taskforce developed a new
point-to-multipoint Ethernet physical layer, utilizing Ethernet
framing natively over a time-division multiple-access (TDMA)
infrastructure. The OAM sub-taskforce introduced some basic
management functionality into an Ethernet link to better monitor and
maintain Ethernet networks in geographically disparate networks.
Generally, one can categorize the changes developed by IEEE P802.3ah This document defines the management objects necessary to integrate
as extending Ethernet with new physical layers (e.g. new optical Ethernet OAM functionality into the SNMP management framework.
physical layers, new copper physical layers, EPON), or as adding new
common functionality applicable to many Ethernet physical layers
(e.g. OAM).
This memo focuses on the management extensions to the MIB for Ethernet OAM is composed of a core set of functions and a set of
Ethernet-like interfaces to address the new common Ethernet optional functional groups that are not required to be implemented
functionality developed in IEEE P802.3ah. along with the core set. The mandatory functions include discovery
operations (determining if the other end of the link is OAM capable,
and what OAM functions it implements), state machine implementation,
and some critical event flows. The optional functional groups are
for (a) link events, (b) remote loopback, and (c) variable retrieval
and response. Each optional functional group is controlled by a
separate MIB table(s).
Two additional Ethernet MIB extensions are defined for IEEE P802.3ah. Ethernet OAM is complementary, not competitive, with SNMP management
The EFM Copper MIB [EFM-CU-MIB] and EFM P2MP MIB [EFM-P2MP-MIB] in that it provides some basic management functions at layer two,
address the new physical layers introduced by IEEE P802.3ah.
EdNote: Might want to expand this more. EFM OAM MIB June 2004
4 Relation to the Other MIBs rather than using layer three and above as required by SNMP over an
IP infrastructure. Ethernet OAM provides single-hop functionality in
that it works only between two directly connected Ethernet stations.
SNMP can be used to manage the Ethernet OAM interactions of one
Ethernet station with another.
EdNote: Need to fill this section in Ethernet OAM has three functional objectives which are detailed in
the following sections.
5 Mapping of IEEE 802.3ah Managed Objects 3.1 Remote fault indication
draft-ietf-hubmib-efm-mib-00.txt February 2004
Remote fault indication provides a mechanism for one end of an
Ethernet link to signal the other end that the receive path is non
operational. Some Ethernet physical layers offer mechanisms to
signal this condition at the physical layer. Ethernet OAM added a
mechanism so that some Ethernet physical layers can operate in
unidirectional mode, allowing frames to be transmitted in one
direction even when the other direction is non-operational.
Traditionally, Ethernet PHYs do not allow frame transmission in one
direction if the other direction is not operational. Using this
mode, Ethernet OAM allows frame-based signaling of remote fault
conditions while still not allowing higher layer applications to be
aware of the unidirectional capability. This document includes
mechanisms for capturing that information and reflecting such
information in objects and notifications into the SNMP management
framework.
3.2 Link monitoring
Ethernet OAM includes event signaling capability so that one end of
an Ethernet link can indicate the occurrence of certain important
events to the other end of the link. This happens via a layer two
protocol. This document defines methods for incorporating the
occurrence of these layer two events, both at the local end and far
end of the link, into the SNMP management framework.
Ethernet OAM also includes mechanisms for one Ethernet station to
query another directly connected Ethernet station about the status of
its Ethernet interface variables and status. This document DOES NOT
include mechanisms for controlling how one Ethernet endpoint may use
this functionality to query the status or statistics of a peer
Ethernet entity.
3.3 Remote loopback
Remote loopback is a link state where the peer Ethernet entity echoes
every received packet (without modifications) back onto the link.
Remote loopback is intrusive in that the other end of the link is not
forwarding traffic from higher layers out over the link. This
EFM OAM MIB June 2004
document defines objects controlling loopback operation and reading
the status of the loopback state.
4. Relation to the Other MIBs
The definitions presented here are based on Clauses 30 and 57 of
[802.3ah]. Note that these clauses describe many of these variables
and their affects on the MAC layer. In some cases there is a one-to
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
document reflect a more complex entity and are reflected by more than
one objectx in the Clause 30 MIB of [802.3ah].
4.1 Relation to other SNMP MIBs
This objects defined in this document do not overlap with MIB-2
[RFC1213], the interfaces MIB [RFC2863], or the Ethernet-like
interfaces MIB [RFC3635]. The objects defined here are defined for
Ethernet-like interfaces only and use the same ifIndex as the
associated Ethernet interface.
This document is independent of the other MIBs derived from [802.3ah]
for copper [802.3ah-copper] and EPON [802.3ah-epon].
4.2 IANA Considerations
The EFM OAM MIB requires the allocation of a single object identifier
for its MODULE-IDENTITY under the MIB-2 tree. IANA has not yet
allocated this object identifier.
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.
EdNote: Add mapping table here. IEEE 802.3 Managed Object Corresponding SNMP object
6 MIB Structure .aOAMID IF-MIB ifIndex
.aOAMAdminState dot3OamAdminState
.aOAMMode dot3OamMode
.aOAMDiscoveryState dot3OamOperStatus
.aOAMRemoteMACAddress dot3OamPeerMacAddress
.aOAMLocalConfiguration dot3OamFunctionsSupported
.aOAMRemoteConfiguration dot3OamPeerFunctionsSupported,
dot3OamPeerMode
.aOAMLocalPDUConfiguration dot3OamMaxOamPduSize
.aOAMRemotePDUConfiguration dot3OamPeerMaxOamPduSize
.aOAMLocalFlagsField dot3OamOperStatus,
EFM OAM MIB June 2004
dot3OamLclErrEventFlagsData
.aOAMRemoteFlagsField dot3OamOperStatus,
dot3OamRmtErrEventFlagsData
.aOAMLocalRevision dot3OamConfigRevision
.aOAMRemoteRevision dot3OamPeerConfigRevision
.aOAMLocalState dot3OamLoopbackStatus
.aOAMRemoteState dot3OamLoopbackStatus
.aOAMRemoteVendorOUI dot3OamPeerVendorOui
.aOAMRemoteVendorSpecificInfo dot3OamPeerVendorInfo
.aOAMUnsupportedCodesTx dot3OamUnsupportedCodesTx
.aOAMUnsupportedCodesRx dot3OamUnsupportedCodesRx
.aOAMInformationTx dot3OamInformationTx
.aOAMInformationRx dot3OamInformationRx
.aOAMUniqueEventNotificationTx dot3OamUniqueEventNotificationTx
.aOAMUniqueEventNotificationRx dot3OamUniqueEventNotificationRx
.aOAMDuplicateEventNotificationTx
dot3OamDuplicateEventNotificationTx
.aOAMDuplicateEventNotificationRx
dot3OamDuplicateEventNotificationRx
.aOAMLoopbackControlTx dot3OamLoopbackControlTx
.aOAMLoopbackControlRx dot3OamLoopbackControlRx
.aOAMVariableRequestTx dot3OamVariableRequestTx
.aOAMVariableRequestRx dot3OamVariableRequestRx
.aOAMVariableResponseTx dot3OamVariableResponseTx
.aOAMVariableResponseRx dot3OamVariableResponseRx
.aOAMOrganizationSpecificTx dot3OamOrgSpecificTx
.aOAMOrganizationSpecificRx dot3OamOrgSpecificTx
.aOAMLocalErrSymPeriodConfig dot3OamErrSymPeriodWindow,
dot3OamErrSymPeriodThreshold
.aOAMLocalErrSymPeriodEvent dot3OamLclErrSymPeriodData
.aOAMLocalErrFrameConfig dot3OamErrFrameWindow,
dot3OamErrFrameThreshold
.aOAMLocalErrFrameEvent dot3OamLclErrFrameData
.aOAMLocalErrFramePeriodConfig dot3OamErrFramePeriodWindow,
dot3OamErrFramePeriodThreshold
.aOAMLocalErrFramePeriodEvent dot3OamLclErrFramePeriodData
.aOAMLocalErrFrameSecsSummaryConfig
dot3OamErrFrameSecsSummaryWindow,
dot3OamErrFrameSecssummaryThreshold
.aOAMLocalErrFrameSecsSummaryEvent
dot3OamLclErrFrameSecsSumData
.aOAMRemoteErrSymPeriodEvent dot3OamRmtErrSymPeriodData
.aOAMRemoteErrFrameEvent dot3OamRmtErrFrameData
.aOAMRemoteErrFramePeriodEvent dot3OamRmtErrFramePeriodData
.aOAMRemoteErrFrameSecsSummaryEvent
dot3OamRmtErrFrameSecsSumData
EFM OAM MIB June 2004
.aFramesLostDueToOAmError
.acOAmAdminControl dot3OamFramesLostDueToOam
There are no IEEE 802.3ah managed objects that are not reflected in
this MIB in some way.
5. MIB Structure
The common EFM MIB objects of this memo focus on the OAM capabilities The common EFM MIB objects of this memo focus on the OAM capabilities
introduced in IEEE P802.3ah. The MIB objects are partitioned into introduced in IEEE 802.3ah. The MIB objects are partitioned into
four (4) different MIB groups. four (4) different MIB groups.
The dot3OamTable group manages the primary OAM objects of the The dot3OamTable group manages the primary OAM objects of the
Ethernet interface. This group controls the state and status of OAM Ethernet interface. This group controls the state and status of OAM
as well as the mode in which it operates. as well as the mode in which it operates.
The dot3OamStats table maintains statistics on the number and type of The dot3OamStats table 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 dot3OamPeer table maintains the current information on the status The dot3OamPeer table 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 dot3OamEvent table defines the management objects for the event The dot3OamEvent table defines the management objects for the event
notification capability available in IEEE P802.3ah OAM. With IEEE notification capability available in IEEE P802.3ah OAM. With IEEE
P802.3ah OAM, one device may send notifications to its peer devices P802.3ah OAM, one device may send notifications to its peer devices
whenever an important event happens on the local device. whenever an important event happens on the local device.
7 Definitions 6. MIB Definition
EFM-COMMON-MIB DEFINITIONS ::= BEGIN EFM-COMMON-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
MODULE-IDENTITY, mib-2, OBJECT-TYPE, Counter32, MODULE-IDENTITY, mib-2, OBJECT-TYPE, Counter32, Unsigned32,
Unsigned32, Integer32 Integer32, NOTIFICATION-TYPE
FROM SNMPv2-SMI FROM SNMPv2-SMI
TEXTUAL-CONVENTION, RowStatus, MacAddress TEXTUAL-CONVENTION, RowStatus, MacAddress, TimeStamp
FROM SNMPv2-TC FROM SNMPv2-TC
ifIndex ifIndex
FROM IF-MIB FROM IF-MIB
MODULE-COMPLIANCE, OBJECT-GROUP MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP
FROM SNMPv2-CONF; FROM SNMPv2-CONF;
efmCommonMIB MODULE-IDENTITY EFM OAM MIB June 2004
LAST-UPDATED "200402010000Z" -- February 1, 2004"
ORGANIZATION "IETF Ethernet Interfaces and Hub MIB efmOamMIB MODULE-IDENTITY
Working Group" LAST-UPDATED "200406010000Z" -- June 01, 2004"
ORGANIZATION
"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
draft-ietf-hubmib-efm-mib-00.txt February 2004
Mailing lists: Mailing lists:
General Discussion: hubmib@ietf.org General Discussion: hubmib@ietf.org
To Subscribe: hubmib-requests@ietf.org To Subscribe: hubmib-requests@ietf.org
In Body: subscribe your_email_address In Body: subscribe your_email_address
Chair: Dan Romascanu Chair: Dan Romascanu, Avaya
Avaya
Tel: +972-3-645-8414 Tel: +972-3-645-8414
Email: dromasca@avaya.com Email: dromasca@avaya.com
Editor: Matt Squire Editor: Matt Squire
Hatteras Networks Hatteras Networks
Tel: +1-919-991-5460 Tel: +1-919-991-5460
Fax: +1-919-991-0743 Fax: +1-919-991-0743
E-mail: msquire@hatterasnetworks.com E-mail: msquire@hatterasnetworks.com
" "
DESCRIPTION DESCRIPTION
"The MIB module for managing the new common Ethernet "The MIB module for managing the new Ethernet OAM features
features introduced by the Ethernet in the First introduced by the Ethernet in the First Mile task force (IEEE
Mile task force (IEEE P802.3ah). The functionality P802.3ah). The functionality presented here is based on IEEE
presented here is based on IEEE P802.3ah/D3.0 P802.3ah/D3.3 [802.3ah], released in April, 2004.
[802.3ah], released in December 2003.
In particular, this MIB focused on the changes to In particular, this MIB focused on the changes to Clause 30 of
Clause 30 of the draft that are not specific to any the draft that are not specific to any physical layer. These
physical layer. These changes are primarily changes are primarily reflected in the new OAM features
reflected in the new OAM features developed under developed under this project, that can be applied to any
this project, that can be applied to any Ethernet Ethernet like interface. The OAM features are described in
like interface. The Clause 57 of [802.3ah].
OAM features are described in Clause 57 of
[802.3ah].
The following reference is used throughout this MIB The following reference is used throughout this MIB module:
module:
[802.3ah] refers to: [802.3ah] refers to:
IEEE Draft P802.3ah/D3.0: 'Draft amendment to - IEEE Draft P802.3ah/D3.3: 'Draft amendment to -
Information technology - Telecommunications and Information technology - Telecommunications and
information exchange between systems - Local and information exchange between systems - Local and
metropolitan area networks - Specific metropolitan are networks - Specific requirements - Part
requirements - Part 3: Carrier sense multiple 3: Carrier sense multiple access with collision detection
access with collision detection (CSMA/CD) access (CSMA/CD) access method and physical layer specifications
method and physical layer specifications - Media - Media Access Control Parameters, Physical Layers and
Access Control Parameters, Physical Layers and Management Parameters for subscriber access networks',
Management Parameters for subscriber access April 2004.
networks', 05 December 2003. -- Editor's note - update this to normative reference when finalized
-- Editor's note - update this to normative
-- reference when finalized
Copyright (c) The Internet Society (2004). This [802-2001] refers to:
version of this MIB module is part of RFC XXXX; 'IEEE Standard for LAN/MAN (Local Area
See the RFC itself for full legal notices. "
EFM OAM MIB June 2004
Network/Metropolitan Area Network): Overview and
Architecture', IEEE 802, June 2001.
Copyright (c) The Internet Society (2004). This version of
this MIB module is part of RFC XXXX; See the RFC itself for
full legal notices. "
-- RFC Editor: Update XXXX to appropriate RFC number -- RFC Editor: Update XXXX to appropriate RFC number
-- RFC Editor: Remote these notes -- RFC Editor: Remove these notes
draft-ietf-hubmib-efm-mib-00.txt February 2004
REVISION "200402010000Z" -- February 3, 2004" REVISION "200406010000Z" -- June 01, 2004"
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: Remote these notes -- RFC Editor: Remove these notes
::= { mib-2 XXX } ::= { mib-2 XXX }
-- RFC Editor: Replace value with IANA assigned number -- RFC Editor: Replace value with IANA assigned number
-- RFC Editor: Remove these notes -- RFC Editor: Remove these notes
-- --
-- Sections of the EFM Common MIB -- Sections of the EFM OAM MIB
-- --
dot3OamMIB OBJECT IDENTIFIER ::= { efmCommonMIB 1} dot3OamMIB OBJECT IDENTIFIER ::= { efmOamMIB 1 }
-- Editor's Note: If only OAM content in this MIB, it dot3OamConformance OBJECT IDENTIFIER ::= { efmOamMIB 2 }
-- may be worthwhile to eliminate the Common
-- nomenclature and make this OAM only.
dot3OamConformance OBJECT IDENTIFIER ::= { efmCommonMIB 2 }
-- --
-- Textual conventions -- Textual conventions for OAM MIB
-- --
Dot3Oui ::= TEXTUAL-CONVENTION Dot3Oui ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION "24-bit Organizationally Unique Identifier. DESCRIPTION
Information on OUIs can be found in IEEE "24-bit Organizationally Unique Identifier. Information on
802-2001 [802-2001] Clause 9." OUIs can be found in IEEE 802-2001 [802-2001] Clause 9."
-- Editors Note - Include reference for [802-2001]
SYNTAX OCTET STRING(SIZE(3)) SYNTAX OCTET STRING(SIZE(3))
Dot3OamUnsigned64 ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"This convention represents a 64 bit unsigned integer. The
convention replaces the Counter64 type for objects requiring
read-write access."
SYNTAX OCTET STRING ( SIZE(8) )
Dot3OamEventTLVData ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"This convention represents the fields in an Event TLV in an
EFM OAM MIB June 2004
Event Notification OAMPDU. The datas is interpreted as a
sequence of six integer fields. Some fields are longer than is
required for specific TLVs, but since this convention will be
shared between all TLVs, the maximum size field is used.
In the list below, TYPE indicates one of Symbol, Frame, Frame
Period or Frame Seconds Summary. See [802.3ah], 57.5.3, for
details.
- The first field is 16 bit wide, and represents the
Event Time Stamp field.
- The second field is 64 bit wide, and represents the
Errored TYPE Window field.
- The third field is 64 bit wide, and represents the
Errored TYPE Threshold field.
- The fourth field is 64 bit wide, and represents the
Errored TYPE field.
- The fifth field is 64 bit wide, and represents the
Error Running Total field.
- The sixth field is 32 bit wide, and represents the
Event Running Total field.
Each integer field is encoded with the most important byte at
the lowest number octet. The first integer field starts at
location 0.
Values which do not use the whole field width, will be aligned
to the right, with zeros padded at the start of the field."
SYNTAX OCTET STRING ( SIZE (38) )
------------------------------------------------------------------
-- --
-- Ethernet OAM Control group -- Ethernet OAM Control group
-- --
dot3OamTable OBJECT-TYPE dot3OamTable OBJECT-TYPE
SYNTAX SEQUENCE OF Dot3OamEntry SYNTAX SEQUENCE OF Dot3OamEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION "Primary controls and status for the OAM DESCRIPTION
capabilities of an Ethernet like interface. "Primary controls and status for the OAM capabilities of an
There will be one row in this table for each Ethernet like interface. There will be one row in this table
Ethernet-like interface in the system that for each Ethernet-like interface in the system that supports
supports the Ethernet OAM functions defined the Ethernet OAM functions defined in [802.3ah]."
in [802.3ah]."
::= { dot3OamMIB 1 } ::= { dot3OamMIB 1 }
EFM OAM MIB June 2004
dot3OamEntry OBJECT-TYPE dot3OamEntry OBJECT-TYPE
SYNTAX Dot3OamEntry SYNTAX Dot3OamEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION "An entry in the table, containing DESCRIPTION
information on the Ethernet OAM function for "An entry in the table, containing information on the Ethernet
a single Ethernet-like interface." OAM function for a single Ethernet-like interface."
draft-ietf-hubmib-efm-mib-00.txt February 2004
INDEX { ifIndex } INDEX { ifIndex }
::= { dot3OamTable 1 } ::= { dot3OamTable 1 }
Dot3OamEntry ::= Dot3OamEntry ::=
SEQUENCE { SEQUENCE {
dot3OamRowStatus RowStatus, dot3OamRowStatus RowStatus,
dot3OamAdminState INTEGER, dot3OamAdminState INTEGER,
dot3OamOperStatus INTEGER, dot3OamOperStatus INTEGER,
dot3OamMode INTEGER, dot3OamMode INTEGER,
dot3OamMaxOamPduSize Integer32, dot3OamMaxOamPduSize Integer32,
dot3OamConfigRevision Unsigned32, dot3OamConfigRevision Unsigned32,
dot3OamFunctionsSupported BITS dot3OamFunctionsSupported BITS
} }
dot3OamRowStatus OBJECT-TYPE dot3OamRowStatus OBJECT-TYPE
SYNTAX RowStatus SYNTAX RowStatus
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION "Row creation is automatic for each Ethernet- DESCRIPTION
like interface that supports OAM functionality "Row creation is automatic for each Ethernet- like interface
as defined in [802.3ah]. that supports OAM functionality as defined in [802.3ah].
Note that implementation of OAM is not Note that implementation of OAM is not required for any
required for any Ethernet like interface. Ethernet like interface. "
"
REFERENCE "[802.3ah], 57.1.2 point d.1" REFERENCE "[802.3ah], 57.1.2 point d.1"
::= { dot3OamEntry 1} ::= { dot3OamEntry 1}
dot3OamAdminState OBJECT-TYPE dot3OamAdminState OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
disabled(1), disabled(1),
enabled(2) enabled(2)
} }
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION "This object is used to configure the default DESCRIPTION
administrative OAM mode for this interface. "This object is used to provision the default administrative
This object represents the administratively OAM mode for this interface. This object represents the
configured OAM state for this interface." desired state of OAM for this interface.
REFERENCE "[802.3ah], 30.11.1.1.2"
The dot3OamAdminState always starts in the disabled(1) state
until an explicity management action or configuration
information retained by the system causes a transition to the
EFM OAM MIB June 2004
enabled(2) state.
Note that the value of this object is ignored when the
interface is not operating in full-duplex mode. OAM is not
supported on half-duplex links. "
REFERENCE "[802.3ah], 30.3.6.1.2"
::= { dot3OamEntry 2 } ::= { dot3OamEntry 2 }
dot3OamOperStatus OBJECT-TYPE dot3OamOperStatus OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
disabled(1), disabled(1),
passiveWait(2), linkfault(2),
activeSendLocal(3), passiveWait(3),
sendLocalAndRemote1(4), activeSendLocal(4),
sendLocalAndRemote2(5), sendLocalAndRemote(5),
oamPeeringLocallyRejected(6), sendLocalAndRemoteOk(6),
oamPeeringRemotelyRejected(7), oamPeeringLocallyRejected(7),
operational(8) oamPeeringRemotelyRejected(8),
operational(9)
} }
draft-ietf-hubmib-efm-mib-00.txt February 2004
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION "At initialization and failure conditions, DESCRIPTION
OAM entities on the same Ethernet link begin "At initialization and failure conditions, two OAM entities on
a discovery phase to determine what OAM the same full-duplex Ethernet link begin a discovery phase to
capabilities maybe used on that link. The determine what OAM capabilities may be used on that link. The
progress of this initialization is controlled progress of this initialization is controlled by the OAM
by the OAM sublayer. This value is always sublayer.
'disabled' if OAM is disabled via the
dot3OamAdminState.
The 'passiveWait' state is returned This value is always disabled(1) if OAM is disabled on this
only by OAM entities in passive mode interface via the dot3OamAdminState.
(dot3OamMode) and reflects the state in which
the OAM entity is waiting to see if the peer
device is OAM capable. The 'activeSendLocal'
is used by active mode devices (dot3OamMode)
and reflects the OAM entity actively trying
to discover whether the peer has OAM ability
but has not yet made that determination.
The state 'sendLocalAndRemote1' reflects that If the link has detected a fault and is transmitting OAMPDUs
the local OAM entity has discovered the peer with a link fault indication, the value is linkFault(2).
but has not yet accepted or rejected the
configuration of the peer. The local device
can, for whatever reason, decide that the
peer device is unacceptable and decline OAM
peering. If the local OAM entity rejects the
peer OAM entity, the state becomes
'oamPeeringLocallyRejected'. If the OAM
peering is allowed by the local device, the
state moves to 'sendLocalAndRemote2'.
Note that both the 'sendLocalAndRemote1' and
'oamPeeringLocallyRejected' states fall
within the state SEND_LOCAL_REMOTE_1 of the
Discovery state diagram
[802.3ah, Figure 57-5], with the
difference being whether the local OAM client
has rejected the peering or just not decided
yet.
If the remote OAM entity rejects the peering, The passiveWait(3) state is returned only by OAM entities in
the state becomes passive mode (dot3OamMode) and reflects the state in which the
'oamPeeringRemotelyRejected'. OAM entity is waiting to see if the peer device is OAM
Note that both the 'sendLocalAndRemote2' and capable. The activeSendLocal(4) is used by active mode
'oamPeeringRemotelyRejected' states fall devices (dot3OamMode) and reflects the OAM entity actively
within the state SEND_LOCAL_REMOTE_2 of the trying to discover whether the peer has OAM capability but has
Discovery state diagram [802.3ah, not yet made that determination.
Figure 57-5], with the difference being
whether the remote OAM client has rejected
the peering or has just not yet decided.
When the local OAM entity learns that both it The state sendLocalAndRemote(5) reflects that the local OAM
draft-ietf-hubmib-efm-mib-00.txt February 2004 entity has discovered the peer but has not yet accepted or
rejected the configuration of the peer. The local device can,
for whatever reason, decide that the peer device is
unacceptable and decline OAM peering. If the local OAM entity
rejects the peer OAM entity, the state becomes
and the remote OAM entity have accepted the EFM OAM MIB June 2004
peering, the state moves to 'operational'.
" oamPeeringLocallyRejected(7). If the OAM peering is allowed
REFERENCE "[802.3ah], REFERENCE TBD" by the local device, the state moves to
sendLocalAndRemoteOk(6). Note that both the
sendLocalAndRemote(5) and oamPeeringLocallyRejected(7) states
fall within the state SEND_LOCAL_REMOTE of the Discovery state
diagram [802.3ah, Figure 57-5], with the difference being
whether the local OAM client has actively rejected the peering
or has just not indicated any decision yet. Whether a peering
decision has been made is indicated via the local flags field
in the OAMPDU (reflected in the aOAMLocalFlagsField of
30.3.6.1.10).
If the remote OAM entity rejects the peering, the state
becomes oamPeeringRemotelyRejected(8). Note that both the
sendLocalAndRemoteOk(6) and oamPeeringRemotelyRejected(8)
states fall within the state SEND_LOCAL_REMOTE_OK of the
Discovery state diagram [802.3ah, Figure 57-5], with the
difference being whether the remote OAM client has rejected
the peering or has just not yet decided. This is indicated
via the remote flags field in the OAM PDU (reflected in the
aOAMRemoteFlagsField of 30.3.6.1.11).
When the local OAM entity learns that both it and the remote
OAM entity have accepted the peering, the state moves to
operational(9) corresponding to the SEND_ANY state of the
Discovery state diagram [802.3ah, Figure 57-5]. "
REFERENCE "[802.3ah], 30.3.6.1.4, 30.3.6.1.10, 30.3.6.1.11"
::= { dot3OamEntry 3 } ::= { dot3OamEntry 3 }
-- Editor's Note: No C30 attribute in D3.0, should appear
in D3.1
dot3OamMode OBJECT-TYPE dot3OamMode OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
active(1), active(1),
passive(2) passive(2)
} }
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION "This object configures the mode of OAM DESCRIPTION
operation for this Ethernet like interface. "This object configures the mode of OAM operation for this
OAM on Ethernet interfaces may be in Ethernet like interface. OAM on Ethernet interfaces may be in
'active' mode or 'passive' mode. These two 'active' mode or 'passive' mode. These two modes differ in
modes differ in that active mode provides that active mode provides additional capabilities to initiate
additional capabilities to initiate monitoring activities with the remote OAM peer entity, while
monitoring activities with the remote OAM passive mode generally waits for the peer to initiate OAM
peer entity, while passive mode generally actions with it. As an example, an active OAM entity can put
waits for the peer to initiate OAM actions the remote OAM entity in a loopback state, where a passive OAM
with it. As an example, an active OAM entity entity cannot.
can put the remote OAM entity in a loopback
state, where a passive OAM entity cannot. Changing this value results in incrementing the configuration
" revision field of locally generated OAMPDUs (30.3.6.1.12) and
REFERENCE "[802.3ah], 30.11.1.1.3"
EFM OAM MIB June 2004
potentially re-doing the OAM discovery process if the
dot3OamOperStatus was already operational(9). "
REFERENCE "[802.3ah], 30.3.6.1.3"
::= { dot3OamEntry 4 } ::= { dot3OamEntry 4 }
dot3OamMaxOamPduSize OBJECT-TYPE dot3OamMaxOamPduSize OBJECT-TYPE
SYNTAX Integer32 (64..1522) SYNTAX Integer32 (64..1522)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION "The largest OAMPDU that the OAM entity DESCRIPTION
supports. OAM entities exchange maximum "The largest OAMPDU that the OAM entity supports. OAM
OAMPDU sizes and negotiate to use the smaller entities exchange maximum OAMPDU sizes and negotiate to use
of the two maximum OAMPDU sizes between the the smaller of the two maximum OAMPDU sizes between the peers.
peers.
" "
REFERENCE "[802.3ah], REFERENCE TBD" REFERENCE "[802.3ah], REFERENCE 30.3.6.1.8"
::= { dot3OamEntry 5 } ::= { dot3OamEntry 5 }
-- Editor's Note: No C30 attribute in D3.0, should appear
in D3.1
dot3OamConfigRevision OBJECT-TYPE dot3OamConfigRevision OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION "The configuration revision of the OAM entity DESCRIPTION
as reflected in the latest OAMPDU sent by the "The configuration revision of the OAM entity as reflected in
OAM entity. The config revision is used by the latest OAMPDU sent by the OAM entity. The config revision
draft-ietf-hubmib-efm-mib-00.txt February 2004 is used by OAM entities to indicate configuration changes have
occured which might require the peer OAM entity to re-evaluate
OAM entities to indicate configuration changes whether the peering is allowed. See local_satisfied in
have occured which might require the peer OAM [802.3ah, 57.3.1.2]. "
entity to re-evaluate whether the peering is REFERENCE "[802.3ah], 30.3.6.1.12"
allowed. See local_satisfied in
[802.3ah, 57.3.1.2].
"
REFERENCE "[802.3ah], REFERENCE TBD"
::= { dot3OamEntry 6 } ::= { dot3OamEntry 6 }
-- Editor's Note: No C30 attribute in D3.0, should appear
in D3.1
dot3OamFunctionsSupported OBJECT-TYPE dot3OamFunctionsSupported OBJECT-TYPE
SYNTAX BITS { SYNTAX BITS {
unidirectionalSupport (0), unidirectionalSupport (0),
loopbackSupport(1), loopbackSupport(1),
eventSupport(2), eventSupport(2),
variableSupport(3) variableSupport(3)
} }
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION "The OAM functions supported on this Ethernet- DESCRIPTION
like interface. OAM consists of separate "The OAM functions supported on this Ethernet- like interface.
functionality sets above the basic discovery OAM consists of separate functional sets beyond the basic
process. These functional groups can be discovery process which is always required. These functional
supported independently, and each is an groups can be supported independently by any implementation.
optional cability above the basic discovery These values are communicated to the peer via the local
function. configuration field of Information OAMPDUs. "
" REFERENCE "[802.3ah], 30.3.6.1.6"
REFERENCE "[802.3ah], REFERENCE TBD"
::= { dot3OamEntry 7 } ::= { dot3OamEntry 7 }
-- Editor's Note: No C30 attribute in D3.0, should appear
in D3.1
EFM OAM MIB June 2004
------------------------------------------------------------------
--
-- Ethernet OAM Peer group
--
dot3OamPeerTable OBJECT-TYPE
SYNTAX SEQUENCE OF Dot3OamPeerEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Information about the OAM peer for a particular Ethernet like
interface. OAM entities communicate with a single OAM peer
entity on full-duplex Ethernet links on which OAM is enabled
and operating properly. "
::= { dot3OamMIB 2 }
dot3OamPeerEntry OBJECT-TYPE
SYNTAX Dot3OamPeerEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry in the table, containing information on the peer OAM
entity for a single Ethernet like interface.
Note that there is at most one OAM peer for each Ethernet like
interface. "
INDEX { ifIndex }
::= { dot3OamPeerTable 1 }
Dot3OamPeerEntry ::=
SEQUENCE {
dot3OamPeerRowStatus RowStatus,
dot3OamPeerMacAddress MacAddress,
dot3OamPeerVendorOui Dot3Oui,
dot3OamPeerVendorInfo Unsigned32,
dot3OamPeerMode INTEGER,
dot3OamPeerMaxOamPduSize Integer32,
dot3OamPeerConfigRevision Unsigned32,
dot3OamPeerFunctionsSupported BITS
}
dot3OamPeerRowStatus OBJECT-TYPE
SYNTAX RowStatus
MAX-ACCESS read-create
STATUS current
EFM OAM MIB June 2004
DESCRIPTION
"The peer row is automatically created when the
dot3OamOperStatus of this particular Ethernet interface is not
'disabled', 'linkFault', 'passiveWait' or 'activeSendLocal'.
In such cases, the remote OAM entity has been identified and
its information and status can be made available.
This row is automatically deleted if the dot3OamOperStatus
changes to 'disabled', 'linkfault', 'passiveWait', or
'activeSendLocal'. "
REFERENCE "N/A"
::= { dot3OamPeerEntry 1}
dot3OamPeerMacAddress OBJECT-TYPE
SYNTAX MacAddress
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The MAC address of the peer OAM entity. The MAC address is
derived from the most recently received OAMPDU.
An OAMPDU is indicated by a valid frame with (1) destination
MAC address equal to that of the reserved MAC address for Slow
Protocols (See 43B of [802.3ah]), (2) a lengthOrType field
equal to the reserved type for Slow Protocols, (3) and a Slow
Protocols subtype equal to that of the subtype reserved for
OAM. "
REFERENCE "[802.3ah], 30.3.6.1.5."
::= { dot3OamPeerEntry 2 }
dot3OamPeerVendorOui OBJECT-TYPE
SYNTAX Dot3Oui
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The OUI of the OAM peer as reflected in the latest
Information OAMPDU received with a Local Information TLV. The
OUI can be used to identify the vendor of the remote OAM
entity.
An Information OAMPDU is indicated by a valid frame with (1)
destination MAC address equal to that of the reserved MAC
address for Slow Protocols (See 43B of [802.3ah]), (2) a
lengthOrType field equal to the reserved type for Slow
Protocols, (3) a Slow Protocols subtype equal to that of the
subtype reserved for OAM, (4) a OAM code that equals the code
reserved for Information OAMPDUs. "
REFERENCE "[802.3ah], 30.3.6.1.16."
EFM OAM MIB June 2004
::= { dot3OamPeerEntry 3 }
dot3OamPeerVendorInfo OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The Vendor Info of the OAM peer as reflected in the latest
Information OAMPDU received with a Local Information TLV. The
vendor information field is within the Local Information TLV,
and can be used to determine additional information about the
peer entity. The format of the vendor information is
unspecified within the 32-bit field.
An Information OAMPDU is indicated by a valid frame with (1)
destination MAC address equal to that of the reserved MAC
address for Slow Protocols (See 43B of [802.3ah]), (2) a
lengthOrType field equal to the reserved type for Slow
Protocols, (3) a Slow Protocols subtype equal to that of the
subtype reserved for OAM, and (4) a OAM code that equals the
code reserved for Information OAMPDUs. "
REFERENCE "[802.3ah], 30.3.6.1.17."
::= { dot3OamPeerEntry 4 }
dot3OamPeerMode OBJECT-TYPE
SYNTAX INTEGER {
active(1),
passive(2)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The mode of the OAM peer as reflected in the latest
Information OAMPDU received with a Local Information TLV. The
mode of the peer can be determined from the Configuration
field in the Local Information TLV of the last Information
OAMPDU received from the peer.
An Information OAMPDU is indicated by a valid frame with (1)
destination MAC address equal to that of the reserved MAC
address for Slow Protocols (See 43B of [802.3ah]), (2) a
lengthOrType field equal to the reserved type for Slow
Protocols, (3) a Slow Protocols subtype equal to that of the
subtype reserved for OAM, and (4) a OAM code that equals the
code reserved for Information OAMPDUs. "
REFERENCE "[802.3ah], 30.3.6.1.7."
::= { dot3OamPeerEntry 5 }
EFM OAM MIB June 2004
dot3OamPeerMaxOamPduSize OBJECT-TYPE
SYNTAX Integer32 (64..1522)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The maximum size of OAMPDU supported by the peer as reflected
in the latest Information OAMPDU received with a Local
Information TLV. Ethernet OAM on this interface must not use
OAMPDUs that exceed this size. The maximum OAMPDU size can be
determined from the PDU Configuration field of the Local
Information TLV of the last Information OAMPDU received from
the peer.
An Information OAMPDU is indicated by a valid frame with (1)
destination MAC address equal to that of the reserved MAC
address for Slow Protocols (See 43B of [802.3ah]), (2) a
lengthOrType field equal to the reserved type for Slow
Protocols, (3) a Slow Protocols subtype equal to that of the
subtype reserved for OAM, and (4) a OAM code that equals the
code reserved for Information OAMPDUs. "
REFERENCE "[802.3ah], 30.3.6.1.9."
::= { dot3OamPeerEntry 6 }
dot3OamPeerConfigRevision OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The configuration revision of the OAM peer as reflected in
the latest OAMPDU. This attribute is changed by the peer
whenever it has a local configuration change for Ethernet OAM
this interface.
The configuration revision can be determined from the Revision
field of the Local Information TLV of the most recently
received Information OAMPDU with a Local Information TLV.
An Information OAMPDU is indicated by a valid frame with (1)
destination MAC address equal to that of the reserved MAC
address for Slow Protocols (See 43B of [802.3ah]), (2) a
lengthOrType field equal to the reserved type for Slow
Protocols, (3) a Slow Protocols subtype equal to that of the
subtype reserved for OAM, and (4) a OAM code that equals the
code reserved for Information OAMPDUs. "
REFERENCE "[802.3ah], 30.3.6.1.13."
::= { dot3OamPeerEntry 7 }
EFM OAM MIB June 2004
dot3OamPeerFunctionsSupported OBJECT-TYPE
SYNTAX BITS {
unidirectionalSupport (0),
loopbackSupport(1),
eventSupport(2),
variableSupport(3)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The OAM functions supported on this Ethernet like interface.
OAM consists of separate functionality sets above the basic
discovery process. This value indicates the capabilities of
the peer OAM entity with respect to these functions.
The capbilities of the OAM peer can be determined from the
configuration field of the Local Information TLV of the most
recently received Information OAMPDU with a Local Information
TLV.
An Information OAMPDU is indicated by a valid frame with (1)
destination MAC address equal to that of the reserved MAC
address for Slow Protocols (See 43B of [802.3ah]), (2) a
lengthOrType field equal to the reserved type for Slow
Protocols, (3) a Slow Protocols subtype equal to that of the
subtype reserved for OAM, and (4) a OAM code that equals the
code reserved for Information OAMPDUs. "
REFERENCE "[802.3ah], REFERENCE 30.3.6.1.7."
::= { dot3OamPeerEntry 8 }
------------------------------------------------------------------
--
-- Ethernet OAM Loopback group
--
dot3OamLoopbackTable OBJECT-TYPE
SYNTAX SEQUENCE OF Dot3OamLoopbackEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This table contains methods to control the loopback state of
the local link as well as indicating the status of the
loopback function.
Loopback can be used to place the remote OAM entity in a state
where every received frame (except OAMPDUs) are echoed back
EFM OAM MIB June 2004
over the same interface on which they were received. In this
state, at the remote entity, 'normal' traffic is disabled as
only the looped back frames are transmitted on the interface.
Loopback is thus an intrusive operation that prohibits normal
data flow and should be used accordingly. "
::= { dot3OamMIB 3 }
dot3OamLoopbackEntry OBJECT-TYPE
SYNTAX Dot3OamLoopbackEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry in the table, containing information on the loopback
status for a single Ethernet like interface. There is an
entry in this table for every Ethernet-like interface on which
supports OAM and loopback function within OAM (as indicated in
dot3OamFunctionsSupported). "
INDEX { ifIndex }
::= { dot3OamLoopbackTable 1 }
Dot3OamLoopbackEntry ::=
SEQUENCE {
dot3OamLoopbackCommand INTEGER,
dot3OamLoopbackStatus INTEGER,
dot3OamLoopbackIgnoreRx INTEGER
}
dot3OamLoopbackCommand OBJECT-TYPE
SYNTAX INTEGER {
noLoopback (1),
startRemoteLoopback (2),
stopRemoteLoopback (3)
}
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"This attribute initiates or terminates remote loopback with
an OAM peer. Writing startRemoteLoopback(2) to this attribute
cause the local OAM client to send a loopback OAMPDU to the
OAM peer with the loopback enable flags set. Writing
stopRemoteLoopback(3) to this attribute will cause the local
OAM client to send a loopback OAMPDU to the OAM peer with the
loopback enable flags cleared. Writing noLoopback to this
attribute has no effect.
Writes to this attribute are ignored unless the OAM status of
this interface is 'operational' (dot3OamOperStatus).
The attribute always returns noLoopback on a read. To
EFM OAM MIB June 2004
determine the loopback status, use the attribute
dot3OamLoopbackStatus. "
REFERENCE "[802.3ah], 57.2.11"
::= { dot3OamLoopbackEntry 1 }
dot3OamLoopbackStatus OBJECT-TYPE
SYNTAX INTEGER {
noLoopback (1),
initiatingLoopback (2),
remoteLoopback (3),
terminatingLoopback (4),
localLoopback (5),
unknown (6)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The loopback status of the OAM entity. This status is
determined by a combination of the local parser and
multiplexer states, the remote parser and multiplexer states,
as well as by the actions of the local OAM client. When
operating in normal mode with no loopback in progress, the
status reads noLoopback(1).
If the OAM client has sent an Loopback OAMPDU and is waiting
for a response, where the local parser and multiplexer states
are DISCARD (see [802.3ah, 57.2.11.1]), the status is
'initiatingLoopback'. In this case, the local OAM entity has
yet to receive any acknowledgement that the remote OAM entity
has received its loopback command request.
If the local OAM client knows that the remote OAM entity is in
loopback mode (via the remote state information as described
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
of terminating the remote loopback [802.3ah, 57.2.11.3,
30.3.6.1.14], with its local multiplexer and parser states in
DISCARD, the status is terminatingLoopback(4). If the remote
OAM client has put the local OAM entity in loopback mode as
indicated by its local parser state, the status is
localLoopback(5).
The unknown(6) status indicates the parser and multiplexer
combination is unexpected. This status may be returned if the
OAM loopback is in a transition state but should not persist.
The values of this attribute correspond to the following
values of the local and remote parser and multiplexer states.
EFM OAM MIB June 2004
value LclPrsr LclMux RmtPrsr RmtMux
noLoopback FWD FWD FWD FWD
initLoopback DISCARD DISCARD FWD FWD
rmtLoopback DISCARD FWD LPBK DISCARD
tmtngLoopback DISCARD DISCARD LPBK DISCARD
lclLoopback LPBK DISCARD DISCARD FWD
unknown *** any other combination ***
"
REFERENCE "[802.3ah], REFERENCE 57.2.11, 30.3.61.14,
30.3.6.1.15"
::= { dot3OamLoopbackEntry 2 }
dot3OamLoopbackIgnoreRx OBJECT-TYPE
SYNTAX INTEGER { ignore(1), process(2) }
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"Since OAM loopback is a distruptive operation (user traffic
does not pass), this attribute provides a mechanism to provide
controls over whether received OAM loopback commands are
processed or ignored. When the value is ignore(1), received
loopback commands are ignored. When the value is process(2),
OAM loopback commands are processed. The default value is to
ignore loopback commands.
The attribute has no meaning if the local OAM entity does not
support the loopback function (as defined in
dot3OamFunctionsSupported). "
REFERENCE "[802.3ah], REFERENCE 57.2.11, 30.3.61.14,
30.3.6.1.15"
::= { dot3OamLoopbackEntry 3 }
------------------------------------------------------------------
-- --
-- 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 "Statistics for the OAM function on a DESCRIPTION
particular Ethernet like interface." "Statistics for the OAM function on a particular Ethernet like
::= { dot3OamMIB 2 } interface."
::= { dot3OamMIB 4 }
dot3OamStatsEntry OBJECT-TYPE dot3OamStatsEntry OBJECT-TYPE
EFM OAM MIB June 2004
SYNTAX Dot3OamStatsEntry SYNTAX Dot3OamStatsEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION "An entry in the table, containing statistics DESCRIPTION
information on the Ethernet OAM function for "An entry in the table, containing statistics information on
a single Ethernet-like interface." the Ethernet OAM function for a single Ethernet-like
interface."
INDEX { ifIndex } INDEX { ifIndex }
draft-ietf-hubmib-efm-mib-00.txt February 2004
::= { dot3OamStatsTable 1 } ::= { dot3OamStatsTable 1 }
Dot3OamStatsEntry ::= Dot3OamStatsEntry ::=
SEQUENCE { SEQUENCE {
dot3OamPduTx Counter32,
dot3OamPduRx Counter32,
dot3OamInformationTx Counter32, dot3OamInformationTx Counter32,
dot3OamInformationRx Counter32, dot3OamInformationRx Counter32,
dot3OamEventNotificationTx Counter32, dot3OamUniqueEventNotificationTx Counter32,
-- Editor's Note - This may change in D3.1
dot3OamUniqueEventNotificationRx Counter32, dot3OamUniqueEventNotificationRx Counter32,
dot3OamDuplicateEventNotificationTx Counter32,
dot3OamDuplicateEventNotificationRx Counter32, dot3OamDuplicateEventNotificationRx Counter32,
dot3OamLoopbackControlTx Counter32, dot3OamLoopbackControlTx Counter32,
dot3OamLoopbackControlRx Counter32, dot3OamLoopbackControlRx Counter32,
dot3OamVariableRequestTx Counter32, dot3OamVariableRequestTx Counter32,
dot3OamVariableRequestRx Counter32, dot3OamVariableRequestRx Counter32,
dot3OamVariableResponseTx Counter32, dot3OamVariableResponseTx Counter32,
dot3OamVariableResponseRx Counter32, dot3OamVariableResponseRx Counter32,
dot3OamOrgSpecificTx Counter32, dot3OamOrgSpecificTx Counter32,
dot3OamOrgSpecificRx Counter32, dot3OamOrgSpecificRx Counter32,
dot3OamUnsupportedCodesRx Counter32 dot3OamUnsupportedCodesTx Counter32,
dot3OamUnsupportedCodesRx Counter32,
dot3OamFramesLostDueToOam Counter32
} }
dot3OamPduTx OBJECT-TYPE dot3OamInformationTx OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION "A count of the number of Ethernet OAM frames DESCRIPTION
transmitted on this interface." "A count of the number of Information OAMPDUs transmitted on
REFERENCE "[802.3ah], 30.11.1.1.14." this interface.
An Information OAMPDU is indicated by a valid frame with (1)
destination MAC address equal to that of the reserved MAC
address for Slow Protocols (See 43B of [802.3ah]), (2) a
lengthOrType field equal to the reserved type for Slow
Protocols, (3) a Slow Protocols subtype equal to that of the
subtype reserved for OAM, and (4) an OAMPDU code equals the
OAM Information code.
Discontinuities of this counter can occur at re-initialization
EFM OAM MIB June 2004
of the management system, and at other times as indicated by
the value of the ifCounterDiscontinuityTime. "
REFERENCE "[802.3ah], 30.3.6.1.20."
::= { dot3OamStatsEntry 1 } ::= { dot3OamStatsEntry 1 }
dot3OamPduRx OBJECT-TYPE dot3OamInformationRx OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION "A count of the number of Ethernet OAM frames DESCRIPTION
received on this interface." "A count of the number of Information OAMPDUs received on this
REFERENCE "[802.3ah], 30.11.1.1.15." interface.
An Information OAMPDU is indicated by a valid frame with (1)
destination MAC address equal to that of the reserved MAC
address for Slow Protocols (See 43B of [802.3ah]), (2) a
lengthOrType field equal to the reserved type for Slow
Protocols, (3) a Slow Protocols subtype equal to that of the
subtype reserved for OAM, and (4) an OAMPDU code equals the
OAM Information code.
Discontinuities of this counter can occur at re-initialization
of the management system, and at other times as indicated by
the value of the ifCounterDiscontinuityTime. "
REFERENCE "[802.3ah], 30.3.6.1.21."
::= { dot3OamStatsEntry 2 } ::= { dot3OamStatsEntry 2 }
dot3OamInformationTx OBJECT-TYPE dot3OamUniqueEventNotificationTx OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION "A count of the number of Information OAMPDUs DESCRIPTION
transmitted on this interface." "A count of the number of unique Event OAMPDUs transmitted on
REFERENCE "[802.3ah], 30.11.1.1.17." this interface. Event notifications may be sent in duplicate
to increase the probability of successfully being received,
given the possiblity that a frame may be lost in transit.
An Event Notification OAMPDU is indicated by a valid frame
with (1) destination MAC address equal to that of the reserved
MAC address for Slow Protocols (See 43B of [802.3ah]), (2) a
lengthOrType field equal to the reserved type for Slow
Protocols, (3) a Slow Protocols subtype equal to that of the
subtype reserved for OAM, and (4) an OAMPDU code equals the
OAM Event code.
A unique Event Notification OAMPDU is indicated as an Event
Notification OAMPDU with a Sequence Number field that is
distinct from the previously transmitted Event Notification
OAMPDU Sequence Number.
EFM OAM MIB June 2004
Discontinuities of this counter can occur at re-initialization
of the management system, and at other times as indicated by
the value of the ifCounterDiscontinuityTime. "
REFERENCE "[802.3ah], 30.3.6.1.22."
::= { dot3OamStatsEntry 3 } ::= { dot3OamStatsEntry 3 }
dot3OamInformationRx OBJECT-TYPE dot3OamUniqueEventNotificationRx OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
draft-ietf-hubmib-efm-mib-00.txt February 2004
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION "A count of the number of Information OAMPDUs DESCRIPTION
received on this interface." "A count of the number of unique Event OAMPDUs received on
REFERENCE "[802.3ah], 30.11.1.1.18." this interface. Event notification OAMPDUs may be sent in
duplicate to increase the probability of successfully being
received, given the possiblity that a frame may be lost in
transit.
An Event Notification OAMPDU is indicated by a valid frame
with (1) destination MAC address equal to that of the reserved
MAC address for Slow Protocols (See 43B of [802.3ah]), (2) a
lengthOrType field equal to the reserved type for Slow
Protocols, (3) a Slow Protocols subtype equal to that of the
subtype reserved for OAM, and (4) an OAMPDU code equals the
OAM Event code.
A unique Event Notification OAMPDU is indicated as an Event
Notification OAMPDU with a Sequence Number field that is
distinct from the previously received Event Notification
OAMPDU Sequence Number.
Discontinuities of this counter can occur at re-initialization
of the management system, and at other times as indicated by
the value of the ifCounterDiscontinuityTime. "
REFERENCE "[802.3ah], 30.3.6.1.24."
::= { dot3OamStatsEntry 4 } ::= { dot3OamStatsEntry 4 }
dot3OamEventNotificationTx OBJECT-TYPE dot3OamDuplicateEventNotificationTx OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION "A count of the number of Event OAMPDUs DESCRIPTION
transmitted on this interface." "A count of the number of duplicate Event OAMPDUs transmitted
REFERENCE "[802.3ah], 30.11.1.1.19." on this interface. Event notification OAMPDUs may be sent in
duplicate to increase the probability of successfully being
received, given the possiblity that a frame may be lost in
transit.
EFM OAM MIB June 2004
An Event Notification OAMPDU is indicated by a valid frame
with (1) destination MAC address equal to that of the reserved
MAC address for Slow Protocols (See 43B of [802.3ah]), (2) a
lengthOrType field equal to the reserved type for Slow
Protocols, (3) a Slow Protocols subtype equal to that of the
subtype reserved for OAM, and (4) an OAMPDU code equals the
OAM Event code.
A duplicate Event Notification OAMPDU is indicated as an Event
Notification OAMPDU with a Sequence Number field that is
identical to the previously transmitted Event Notification
OAMPDU Sequence Number.
Discontinuities of this counter can occur at re-initialization
of the management system, and at other times as indicated by
the value of the ifCounterDiscontinuityTime. "
REFERENCE "[802.3ah], 30.3.6.1.23."
::= { dot3OamStatsEntry 5 } ::= { dot3OamStatsEntry 5 }
dot3OamUniqueEventNotificationRx OBJECT-TYPE dot3OamDuplicateEventNotificationRx OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION "A count of the number of unique Event DESCRIPTION
OAMPDUs received on this interface." "A count of the number of duplicate Event OAMPDUs received on
REFERENCE "[802.3ah], 30.11.1.1.20." this interface. Event notification OAMPDUs may be sent in
duplicate to increase the probability of successfully being
received, given the possiblity that a frame may be lost in
transit.
An Event Notification OAMPDU is indicated by a valid frame
with (1) destination MAC address equal to that of the reserved
MAC address for Slow Protocols (See 43B of [802.3ah]), (2) a
lengthOrType field equal to the reserved type for Slow
Protocols, (3) a Slow Protocols subtype equal to that of the
subtype reserved for OAM, and (4) an OAMPDU code equals the
OAM Event code.
A duplicate Event Notification OAMPDU is indicated as an Event
Notification OAMPDU with a Sequence Number field that is
identical to the previously received Event Notification OAMPDU
Sequence Number.
Discontinuities of this counter can occur at re-initialization
of the management system, and at other times as indicated by
the value of the ifCounterDiscontinuityTime. "
REFERENCE "[802.3ah], 30.3.6.1.25."
::= { dot3OamStatsEntry 6 } ::= { dot3OamStatsEntry 6 }
dot3OamDuplicateEventNotificationRx OBJECT-TYPE EFM OAM MIB June 2004
dot3OamLoopbackControlTx OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION "A count of the number of duplicate Event DESCRIPTION
OAMPDUs received on this interface." "A count of the number of Loopback Control OAMPDUs transmitted
REFERENCE "[802.3ah], 30.11.1.1.21." on this interface.
An Loopback Conrol OAMPDU is indicated by a valid frame with
(1) destination MAC address equal to that of the reserved MAC
address for Slow Protocols (See 43B of [802.3ah]), (2) a
lengthOrType field equal to the reserved type for Slow
Protocols, (3) a Slow Protocols subtype equal to that of the
subtype reserved for OAM, and (4) an OAMPDU code equals the
OAM Loopback Control code.
Discontinuities of this counter can occur at re-initialization
of the management system, and at other times as indicated by
the value of the ifCounterDiscontinuityTime. "
REFERENCE "[802.3ah], 30.3.6.1.26."
::= { dot3OamStatsEntry 7 } ::= { dot3OamStatsEntry 7 }
dot3OamLoopbackControlTx OBJECT-TYPE dot3OamLoopbackControlRx OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION "A count of the number of Loopback OAMPDUs DESCRIPTION
transmitted on this interface." "A count of the number of Loopback Control OAMPDUs transmitted
REFERENCE "[802.3ah], 30.11.1.1.22." on this interface.
An Loopback Control OAMPDU is indicated by a valid frame with
(1) destination MAC address equal to that of the reserved MAC
address for Slow Protocols (See 43B of [802.3ah]), (2) a
lengthOrType field equal to the reserved type for Slow
Protocols, (3) a Slow Protocols subtype equal to that of the
subtype reserved for OAM, and (4) an OAMPDU code equals the
OAM Loopback Control code.
Discontinuities of this counter can occur at re-initialization
of the management system, and at other times as indicated by
the value of the ifCounterDiscontinuityTime. "
REFERENCE "[802.3ah], 30.3.6.1.27."
::= { dot3OamStatsEntry 8 } ::= { dot3OamStatsEntry 8 }
dot3OamLoopbackControlRx OBJECT-TYPE dot3OamVariableRequestTx OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION "A count of the number of Loopback OAMPDUs DESCRIPTION
received on this interface."
REFERENCE "[802.3ah], 30.11.1.1.23."
::= { dot3OamStatsEntry 9 }
dot3OamVariableRequestTx OBJECT-TYPE EFM OAM MIB June 2004
draft-ietf-hubmib-efm-mib-00.txt February 2004
"A count of the number of Variable Request OAMPDUs transmitted
on this interface.
An Variable Request OAMPDU is indicated by a valid frame with
(1) destination MAC address equal to that of the reserved MAC
address for Slow Protocols (See 43B of [802.3ah]), (2) a
lengthOrType field equal to the reserved type for Slow
Protocols, (3) a Slow Protocols subtype equal to that of the
subtype reserved for OAM, and (4) an OAMPDU code equals the
OAM Variable Request code.
Discontinuities of this counter can occur at re-initialization
of the management system, and at other times as indicated by
the value of the ifCounterDiscontinuityTime. "
REFERENCE "[802.3ah], 30.3.6.1.28."
::= { dot3OamStatsEntry 9 }
dot3OamVariableRequestRx OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION "A count of the number of Variable Request DESCRIPTION
OAMPDUs transmitted on this interface." "A count of the number of Variable Request OAMPDUs received on
REFERENCE "[802.3ah], 30.11.1.1.24." this interface.
An Variable Request OAMPDU is indicated by a valid frame with
(1) destination MAC address equal to that of the reserved MAC
address for Slow Protocols (See 43B of [802.3ah]), (2) a
lengthOrType field equal to the reserved type for Slow
Protocols, (3) a Slow Protocols subtype equal to that of the
subtype reserved for OAM, and (4) an OAMPDU code equals the
OAM Variable Request code.
Discontinuities of this counter can occur at re-initialization
of the management system, and at other times as indicated by
the value of the ifCounterDiscontinuityTime. "
REFERENCE "[802.3ah], 30.3.6.1.29."
::= { dot3OamStatsEntry 10 } ::= { dot3OamStatsEntry 10 }
dot3OamVariableRequestRx OBJECT-TYPE dot3OamVariableResponseTx OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION "A count of the number of Variable Request DESCRIPTION
OAMPDUs received on this interface." "A count of the number of Variable Response OAMPDUs
REFERENCE "[802.3ah], 30.11.1.1.25." transmitted on this interface.
An Variable Response OAMPDU is indicated by a valid frame with
(1) destination MAC address equal to that of the reserved MAC
EFM OAM MIB June 2004
address for Slow Protocols (See 43B of [802.3ah]), (2) a
lengthOrType field equal to the reserved type for Slow
Protocols, (3) a Slow Protocols subtype equal to that of the
subtype reserved for OAM, and (4) an OAMPDU code equals the
OAM Variable Response code.
Discontinuities of this counter can occur at re-initialization
of the management system, and at other times as indicated by
the value of the ifCounterDiscontinuityTime. "
REFERENCE "[802.3ah], 30.3.6.1.30."
::= { dot3OamStatsEntry 11 } ::= { dot3OamStatsEntry 11 }
dot3OamVariableResponseTx OBJECT-TYPE dot3OamVariableResponseRx OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION "A count of the number of Variable Response DESCRIPTION
OAMPDUs transmitted on this interface." "A count of the number of Variable Response OAMPDUs received
REFERENCE "[802.3ah], 30.11.1.1.26." on this interface.
An Variable Response OAMPDU is indicated by a valid frame with
(1) destination MAC address equal to that of the reserved MAC
address for Slow Protocols (See 43B of [802.3ah]), (2) a
lengthOrType field equal to the reserved type for Slow
Protocols, (3) a Slow Protocols subtype equal to that of the
subtype reserved for OAM, and (4) an OAMPDU code equals the
OAM Variable Response code.
Discontinuities of this counter can occur at re-initialization
of the management system, and at other times as indicated by
the value of the ifCounterDiscontinuityTime. "
REFERENCE "[802.3ah], 30.3.6.1.31."
::= { dot3OamStatsEntry 12 } ::= { dot3OamStatsEntry 12 }
dot3OamVariableResponseRx OBJECT-TYPE dot3OamOrgSpecificTx OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION "A count of the number of Variable Response DESCRIPTION
OAMPDUs received on this interface." "A count of the number of Organization Specific OAMPDUs
REFERENCE "[802.3ah], 30.11.1.1.27." transmitted on this interface.
An Organization Specific OAMPDU is indicated by a valid frame
with (1) destination MAC address equal to that of the reserved
MAC address for Slow Protocols (See 43B of [802.3ah]), (2) a
lengthOrType field equal to the reserved type for Slow
Protocols, (3) a Slow Protocols subtype equal to that of the
subtype reserved for OAM, and (4) an OAMPDU code equals the
OAM Organization Specific code.
EFM OAM MIB June 2004
Discontinuities of this counter can occur at re-initialization
of the management system, and at other times as indicated by
the value of the ifCounterDiscontinuityTime. "
REFERENCE "[802.3ah], 30.3.6.1.32."
::= { dot3OamStatsEntry 13 } ::= { dot3OamStatsEntry 13 }
dot3OamOrgSpecificTx OBJECT-TYPE dot3OamOrgSpecificRx OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION "A count of the number of Organizational DESCRIPTION
Specific OAMPDUs transmitted on this
interface." "A count of the number of Organization Specific OAMPDUs
REFERENCE "[802.3ah], 30.11.1.1.28." received on this interface.
An Organization Specific OAMPDU is indicated by a valid frame
with (1) destination MAC address equal to that of the reserved
MAC address for Slow Protocols (See 43B of [802.3ah]), (2) a
lengthOrType field equal to the reserved type for Slow
Protocols, (3) a Slow Protocols subtype equal to that of the
subtype reserved for OAM, and (4) an OAMPDU code equals the
OAM Organization Specific code.
Discontinuities of this counter can occur at re-initialization
of the management system, and at other times as indicated by
the value of the ifCounterDiscontinuityTime. "
REFERENCE "[802.3ah], 30.3.6.1.33."
::= { dot3OamStatsEntry 14 } ::= { dot3OamStatsEntry 14 }
dot3OamOrgSpecificRx OBJECT-TYPE dot3OamUnsupportedCodesTx OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION "A count of the number of Organizational DESCRIPTION
Specific OAMPDUs received on this interface." "A count of the number of OAMPDUs transmitted on this
REFERENCE "[802.3ah], 30.11.1.1.29." interface with an unsupported op-code.
An unsupported opcode OAMPDU is indicated by a valid frame
with (1) destination MAC address equal to that of the reserved
MAC address for Slow Protocols (See 43B of [802.3ah]), (2) a
lengthOrType field equal to the reserved type for Slow
Protocols, (3) a Slow Protocols subtype equal to that of the
subtype reserved for OAM, and (4) an OAMPDU code equals the
opcode for a function that is not supported by the device.
Discontinuities of this counter can occur at re-initialization
of the management system, and at other times as indicated by
the value of the ifCounterDiscontinuityTime. "
EFM OAM MIB June 2004
REFERENCE "[802.3ah], 30.3.6.1.18."
::= { dot3OamStatsEntry 15 } ::= { dot3OamStatsEntry 15 }
draft-ietf-hubmib-efm-mib-00.txt February 2004
dot3OamUnsupportedCodesRx OBJECT-TYPE dot3OamUnsupportedCodesRx OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION "A count of the number of OAMPDUs with an DESCRIPTION
unrecognized type received on this "A count of the number of OAMPDUs received on this interface
interface." with an unsupported op-code.
REFERENCE "[802.3ah], 30.11.1.1.16."
An unsupported opcode OAMPDU is indicated by a valid frame
with (1) destination MAC address equal to that of the reserved
MAC address for Slow Protocols (See 43B of [802.3ah]), (2) a
lengthOrType field equal to the reserved type for Slow
Protocols, (3) a Slow Protocols subtype equal to that of the
subtype reserved for OAM, and (4) an OAMPDU code equals the
opcode for a function that is not supported by the device.
Discontinuities of this counter can occur at re-initialization
of the management system, and at other times as indicated by
the value of the ifCounterDiscontinuityTime. "
REFERENCE "[802.3ah], 30.3.6.1.19."
::= { dot3OamStatsEntry 16 } ::= { dot3OamStatsEntry 16 }
dot3OamFramesLostDueToOam OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"A count of the number of frames that were dropped by the OAM
multiplexer. Since the OAM mulitplexer has multiple inputs
and a single output, there may be cases where frames are
dropped due to transmit resource contention. This counter is
incremented whenever a frame is dropped by the OAM layer.
When this counter is incremented, no other counters in this
MIB are incremented.
Discontinuities of this counter can occur at re-initialization
of the management system, and at other times as indicated by
the value of the ifCounterDiscontinuityTime. "
REFERENCE "[802.3ah], 30.3.6.1.46."
::= { dot3OamStatsEntry 17 }
------------------------------------------------------------------
-- --
-- Ethernet OAM Peer group -- Ethernet OAM Event group
-- --
dot3OamPeerTable OBJECT-TYPE
SYNTAX SEQUENCE OF Dot3OamPeerEntry EFM OAM MIB June 2004
dot3OamEventConfigTable OBJECT-TYPE
SYNTAX SEQUENCE OF Dot3OamEventConfigEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION "Information about the OAM peer for a DESCRIPTION
particular Ethernet like interface." "Ethernet OAM includes the ability to generate and receive
::= { dot3OamMIB 3 } event notifications to indicate various link problems. This
table contains the mechanisms to configure the thresholds to
generate the standard Ethernet OAM events.
dot3OamPeerEntry OBJECT-TYPE These events are:
SYNTAX Dot3OamPeerEntry - Errored Symbol Period Event. Generated when the number of
symbol errors exceeds a threshold within a given window
defined by a number of symbols (e.g. 1,000 symbols out of
1,000,000 had errors).
- Errored Frame Period Event. Generated when the number of
frame errors exceeds a threshold within a given window
defined by a number of frames (e.g. 10 frames out of 1000
had errors).
- Errored Frame Event. Generated when the number of frame
errors exceeds a threshold within a given window defined
by a period of time (e.g. 10 frames in 1 second had
errors).
- Errored Frame Seconds Summary Event. Generated when the
number of errored frame seconds exceeds a threshold within
a given time period (e.g. 10 errored frame seconds within
the last 100 seconds). An errored frame second is defined
as a 1 second interval which had >0 frame errors.
"
::= { dot3OamMIB 5 }
dot3OamEventConfigEntry OBJECT-TYPE
SYNTAX Dot3OamEventConfigEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION "An entry in the table, containing information DESCRIPTION
on the peer OAM entity for a single Ethernet "Event configuration information is available for every
like interface. Ethernet like interface that supports OAM and the event
" function of OAM as indicated in the dot3OamFunctionsSupported
attribute.
Event configuration controls when the local management entity
sends Event Notification OAMPDUs to its OAM peer. "
INDEX { ifIndex } INDEX { ifIndex }
::= { dot3OamPeerTable 1 } ::= { dot3OamEventConfigTable 1 }
Dot3OamEventConfigEntry ::=
EFM OAM MIB June 2004
Dot3OamPeerEntry ::=
SEQUENCE { SEQUENCE {
dot3OamPeerRowStatus RowStatus, dot3OamErrSymPeriodWindow Dot3OamUnsigned64,
dot3OamPeerMacAddress MacAddress, dot3OamErrSymPeriodThreshold Dot3OamUnsigned64,
dot3OamPeerVendorOui Dot3Oui, dot3OamErrSymPeriodEvNotifEnable INTEGER,
dot3OamPeerVendorInfo Unsigned32, dot3OamErrFramePeriodWindow Unsigned32,
dot3OamPeerMode INTEGER, dot3OamErrFramePeriodThreshold Unsigned32,
dot3OamPeerMaxOamPduSize Integer32, dot3OamErrFramePeriodEvNotifEnable INTEGER,
dot3OamPeerConfigRevision Unsigned32, dot3OamErrFrameWindow Unsigned32,
dot3OamPeerFunctionsSupported BITS, dot3OamErrFrameThreshold Unsigned32,
dot3OamPeerMultiplexorState INTEGER, dot3OamErrFrameEvNotifEnable INTEGER,
dot3OamPeerParserState INTEGER dot3OamErrFrameSecsSummaryWindow Integer32,
dot3OamErrFrameSecsSummaryThreshold Integer32,
dot3OamErrFrameSecsEvNotifEnable INTEGER
} }
dot3OamPeerRowStatus OBJECT-TYPE dot3OamErrSymPeriodWindow OBJECT-TYPE
SYNTAX RowStatus SYNTAX Dot3OamUnsigned64
MAX-ACCESS read-create MAX-ACCESS read-write
STATUS current STATUS current
draft-ietf-hubmib-efm-mib-00.txt February 2004 DESCRIPTION
"The number of symbols over which the threshold is defined.
DESCRIPTION "The peer row is automatically created when If dot3OamErrSymPeriodThreshold symbol errors occur within a
the dot3OamOperStatus of this particular window of dot3OamErrSymPeriodWindow symbols, an Event
Ethernet interface is not 'disabled', Notification OAMPDU should be generated with an Errored Symbol
'passiveWait' or 'activeSendLocal'. Period Event TLV indicating the threshold has been crossed in
In such cases, the remote OAM entity has this window. "
been identified and its information and status REFERENCE "[802.3ah], 30.3.6.1.34"
can be made available. ::= { dot3OamEventConfigEntry 1 }
This row is automatically deleted if the dot3OamErrSymPeriodThreshold OBJECT-TYPE
dot3OamOperStatus changes to 'disabled', SYNTAX Dot3OamUnsigned64
'passiveWait', or 'activeSendLocal'. MAX-ACCESS read-write
STATUS current
DESCRIPTION
"The number of symbols errors that must occur for this event
to be triggered.
If dot3OamErrSymPeriodThreshold symbol errors occur within a
window of dot3OamErrSymPeriodWindow symbols, an Event
Notification OAMPDU should be generated with an Errored Symbol
Period Event TLV indicating the threshold has been crossed in
this window. "
REFERENCE "[802.3ah], 30.3.6.1.34"
::= { dot3OamEventConfigEntry 2 }
dot3OamErrSymPeriodEvNotifEnable OBJECT-TYPE
SYNTAX INTEGER { enabled(1), disabled(2) }
MAX-ACCESS read-write
EFM OAM MIB June 2004
STATUS current
DESCRIPTION
"Indicates whether the occurence of Errored Symbol Period
Events should result in Event Notification OAMPDUs generated
by the OAM layer.
By default, this object should have the value enabled(1) for
Ethernet like interfaces that support OAM. If the OAM layer
does not support event notifications (as indicated via the
dot3OamFunctionsSupported attribute), this value is ignored.
" "
REFERENCE "N/A" REFERENCE "N/A"
::= { dot3OamPeerEntry 1} ::= { dot3OamEventConfigEntry 3 }
dot3OamPeerMacAddress OBJECT-TYPE dot3OamErrFramePeriodWindow OBJECT-TYPE
SYNTAX MacAddress SYNTAX Unsigned32
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"The number of frames over which the threshold is defined.
If dot3OamErrFramePeriodThreshold frame errors occur within a
window of dot3OamErrFramePeriodWindow frames, an Event
Notification OAMPDU should be generated with an Errored Frame
Period Event TLV indicating the threshold has been crossed in
this window. "
REFERENCE "[802.3ah], 30.3.6.1.38"
::= { dot3OamEventConfigEntry 4 }
dot3OamErrFramePeriodThreshold OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"The number of frame errors that must occur for this event to
be triggered.
If dot3OamErrFramePeriodThreshold frame errors occur within a
window of dot3OamErrFramePeriodWindow frames, an Event
Notification OAMPDU should be generated with an Errored Frame
Period Event TLV indicating the threshold has been crossed in
this window. "
REFERENCE "[802.3ah], 30.3.6.1.38"
::= { dot3OamEventConfigEntry 5 }
dot3OamErrFramePeriodEvNotifEnable OBJECT-TYPE
SYNTAX INTEGER { enabled(1), disabled(2) }
MAX-ACCESS read-write
STATUS current
EFM OAM MIB June 2004
DESCRIPTION
"Indicates whether the occurence of an Errored Frame Period
Event should result in an Event Notification OAMPDU generated
by the OAM layer.
By default, this object should have the value enabled(1) for
Ethernet like interfaces that support OAM. If the OAM layer
does not support event notifications (as indicated via the
dot3OamFunctionsSupported attribute), this value is ignored. "
REFERENCE "N/A"
::= { dot3OamEventConfigEntry 6 }
dot3OamErrFrameWindow OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"The amount of time (in 100ms increments) over which the
threshold is defined.
If dot3OamErrFrameThreshold frame errors occur within a window
of dot3OamErrFrameWindow seconds (measured in tenths of
seconds), an Event Notification OAMPDU should be generated with
an Errored Frame Event TLV indicating the threshold has been
crossed in this window. "
REFERENCE "[802.3ah], 30.3.6.1.36"
::= { dot3OamEventConfigEntry 7 }
dot3OamErrFrameThreshold OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"The number of frame errors that must occur for this event to
be triggered.
If dot3OamErrFrameThreshold frame errors occur within a window
of dot3OamErrFrameWindow (in tenths of seconds), an Event
Notification OAMPDU should be generated with an Errored Frame
Event TLV indicating the threshold has been crossed in this
window. "
REFERENCE "[802.3ah], 30.3.6.1.36"
::= { dot3OamEventConfigEntry 8 }
dot3OamErrFrameEvNotifEnable OBJECT-TYPE
SYNTAX INTEGER { enabled(1), disabled(2) }
MAX-ACCESS read-write
STATUS current
EFM OAM MIB June 2004
DESCRIPTION
"Indicates whether the occurence of an Errored Frame Event
should result in an Event Notification OAMPDU generated by the
OAM layer.
By default, this object should have the value enabled(1) for
Ethernet like interfaces that support OAM. If the OAM layer
does not support event notifications (as indicated via the
dot3OamFunctionsSupported attribute), this value is ignored. "
REFERENCE "N/A"
::= { dot3OamEventConfigEntry 9 }
dot3OamErrFrameSecsSummaryWindow OBJECT-TYPE
SYNTAX Integer32 (100..9000)
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"The amount of time (in 100ms intervals) over which the
threshold is defined.
If dot3OamErrFrameSecsSummaryThreshold frame errors occur
within a window of dot3OamErrFrameSecsSummaryWindow (in tenths
of seconds), an Event Notification OAMPDU should be generated
with an Errored Frame Seconds Summary Event TLV indicating the
threshold has been crossed in this window. "
REFERENCE "[802.3ah], 30.3.6.1.40"
::= { dot3OamEventConfigEntry 10 }
dot3OamErrFrameSecsSummaryThreshold OBJECT-TYPE
SYNTAX Integer32 (1..900)
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"The number of errored frame seconds that must occur for this
event to be triggered.
If dot3OamErrFrameSecsSummaryThreshold frame errors occur
within a window of dot3OamErrFrameSecsSummaryWindow (in tenths
of seconds), an Event Notification OAMPDU should be generated
with an Errored Frame Seconds Summary Event TLV indicating the
threshold has been crossed in this window. "
REFERENCE "[802.3ah], 30.3.6.1.40"
::= { dot3OamEventConfigEntry 11 }
dot3OamErrFrameSecsEvNotifEnable OBJECT-TYPE
SYNTAX INTEGER { enabled(1), disabled(2) }
MAX-ACCESS read-write
STATUS current
DESCRIPTION
EFM OAM MIB June 2004
"Indicates whether the occurence of an Errored Frame Seconds
Summary Event should result in an Event Notification OAMPDU
generated by the OAM layer.
By default, this object should have the value enabled(1) for
Ethernet like interfaces that support OAM. If the OAM layer
does not support event notifications (as indicated via the
dot3OamFunctionsSupported attribute), this value is ignored."
REFERENCE "N/A"
::= { dot3OamEventConfigEntry 12 }
------------------------------------------------------------------
--
-- Ethernet OAM Event Status group
--
dot3OamEventStatusTable OBJECT-TYPE
SYNTAX SEQUENCE OF Dot3OamEventStatusEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"OAM event status information for a particular Ethernet-like
interface. These objects will contain the most recently
transmitted or received TLV event.
There is a strict one-to-one relation between entries in this
table and entries in the dot3OamTable. "
::= { dot3OamMIB 6 }
dot3OamEventStatusEntry OBJECT-TYPE
SYNTAX Dot3OamEventStatusEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION "An entry in the dot3OamEventStatusTable."
INDEX { ifIndex }
::= { dot3OamEventStatusTable 1 }
Dot3OamEventStatusEntry ::=
SEQUENCE {
-- Local events
dot3OamLclErrSymPeriodTime TimeStamp,
dot3OamLclErrSymPeriodData Dot3OamEventTLVData,
dot3OamLclErrFramePeriodTime TimeStamp,
dot3OamLclErrFramePeriodData Dot3OamEventTLVData,
dot3OamLclErrFrameTime TimeStamp,
dot3OamLclErrFrameData Dot3OamEventTLVData,
dot3OamLclErrFrameSecsSumTime TimeStamp,
dot3OamLclErrFrameSecsSumData Dot3OamEventTLVData,
EFM OAM MIB June 2004
dot3OamLclErrEventFlagsTime TimeStamp,
dot3OamLclErrEventFlagsData BITS,
dot3OamLclErrEventOtherTime TimeStamp,
dot3OamLclErrEventOtherData OCTET STRING,
-- Remote events
dot3OamRmtErrSymPeriodTime TimeStamp,
dot3OamRmtErrSymPeriodData Dot3OamEventTLVData,
dot3OamRmtErrFramePeriodTime TimeStamp,
dot3OamRmtErrFramePeriodData Dot3OamEventTLVData,
dot3OamRmtErrFrameTime TimeStamp,
dot3OamRmtErrFrameData Dot3OamEventTLVData,
dot3OamRmtErrFrameSecsSumTime TimeStamp,
dot3OamRmtErrFrameSecsSumData Dot3OamEventTLVData,
dot3OamRmtErrEventFlagsTime TimeStamp,
dot3OamRmtErrEventFlagsData BITS,
dot3OamRmtErrEventOtherTime TimeStamp,
dot3OamRmtErrEventOtherData OCTET STRING
}
dot3OamLclErrSymPeriodTime OBJECT-TYPE
SYNTAX TimeStamp
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION "The MAC address of the peer OAM entity. DESCRIPTION
" "The time at which the last Errored Symbol Period Event
REFERENCE "[802.3ah], 30.11.1.1.4." occurred locally. "
::= { dot3OamPeerEntry 2 } REFERENCE "[802.3ah], 30.3.6.1.35 and 57.5.3.1."
::= { dot3OamEventStatusEntry 1 }
dot3OamPeerVendorOui OBJECT-TYPE dot3OamLclErrSymPeriodData OBJECT-TYPE
SYNTAX Dot3Oui SYNTAX Dot3OamEventTLVData
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION "The OUI of the OAM peer as reflected in the DESCRIPTION
latest information OAMPDU. "A sequence of six integers corresponding to the respective
" fields in the most recently transmitted Errored Symbol Period
REFERENCE "[802.3ah], 30.11.1.1.11." Event TLV in an Event Notification OAMPDU. "
::= { dot3OamPeerEntry 3 } REFERENCE "[802.3ah], 30.3.6.1.35 and 57.5.3.1."
::= { dot3OamEventStatusEntry 2 }
dot3OamPeerVendorInfo OBJECT-TYPE dot3OamLclErrFramePeriodTime OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX TimeStamp
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION "The Vendor Info of the OAM peer as reflected DESCRIPTION
in the latest information OAMPDU. "The time at which the last Errored Frame Period Event
" occurred locally. "
REFERENCE "[802.3ah], 30.11.1.1.12, 30.11.1.1.13"
::= { dot3OamPeerEntry 4 }
dot3OamPeerMode OBJECT-TYPE EFM OAM MIB June 2004
SYNTAX INTEGER {
active(1), REFERENCE "[802.3ah], 30.3.6.1.39 and 57.5.3.3."
passive(2) ::= { dot3OamEventStatusEntry 3 }
}
dot3OamLclErrFramePeriodData OBJECT-TYPE
SYNTAX Dot3OamEventTLVData
MAX-ACCESS read-only MAX-ACCESS read-only
draft-ietf-hubmib-efm-mib-00.txt February 2004 STATUS current
DESCRIPTION
"A sequence of six integers corresponding to the respective
fields in the most recently transmitted Errored Frame Period
Event TLV in an Event Notification OAMPDU."
REFERENCE "[802.3ah], 30.3.6.1.39 and 57.5.3.3."
::= { dot3OamEventStatusEntry 4 }
dot3OamLclErrFrameTime OBJECT-TYPE
SYNTAX TimeStamp
MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION "The mode of the OAM peer as reflected in the DESCRIPTION
latest OAMPDU. "The time at which the last Errored Frame Event occurred
" locally. "
REFERENCE "[802.3ah], 30.11.1.1.5." REFERENCE "[802.3ah], 30.3.6.1.37 and 57.5.3.2."
::= { dot3OamPeerEntry 5 } ::= { dot3OamEventStatusEntry 5 }
dot3OamPeerMaxOamPduSize OBJECT-TYPE dot3OamLclErrFrameData OBJECT-TYPE
SYNTAX Integer32 (64..1522) SYNTAX Dot3OamEventTLVData
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION "The maximum size of OAMPDU supported by the DESCRIPTION
peer as reflected in the latest OAMPDU. "A sequence of six integers corresponding to the respective
Ethernet OAM on this interface must not fields in the most recently transmitted Errored Frame Event
use OAMPDUs that exceed this size. TLV in an Event Notification OAMPDU."
" REFERENCE "[802.3ah], 30.3.6.1.37 and 57.5.3.2."
REFERENCE "[802.3ah], 30.11.1.1.6." ::= { dot3OamEventStatusEntry 6 }
::= { dot3OamPeerEntry 6 }
dot3OamPeerConfigRevision OBJECT-TYPE dot3OamLclErrFrameSecsSumTime OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX TimeStamp
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION "The configuration revision of the OAM peer DESCRIPTION
as reflected in the latest OAMPDU. This "The time at which the last Errored Frame Seconds Summary
attribute is changed by the peer whenever it Event occurred locally. "
has a local configuration change for Ethernet REFERENCE "[802.3ah], 30.3.6.1.36 and 57.5.3.4."
OAM this interface. ::= { dot3OamEventStatusEntry 7 }
dot3OamLclErrFrameSecsSumData OBJECT-TYPE
SYNTAX Dot3OamEventTLVData
MAX-ACCESS read-only
STATUS current
EFM OAM MIB June 2004
DESCRIPTION
"A sequence of six integers corresponding to the respective
fields in the most recently transmitted Errored Frame Seconds
Summary Event TLV in an Event Notification OAMPDU."
REFERENCE "[802.3ah], 30.3.6.1.36 and 57.5.3.4."
::= { dot3OamEventStatusEntry 8 }
dot3OamLclErrEventFlagsTime OBJECT-TYPE
SYNTAX TimeStamp
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The time at which the flag field in outgoing OAMPDUs changed.
" "
REFERENCE "[802.3ah], 30.11.1.1.9." REFERENCE "[802.3ah], 30.3.6.1.10"
::= { dot3OamPeerEntry 7 } ::= { dot3OamEventStatusEntry 9 }
dot3OamPeerFunctionsSupported OBJECT-TYPE dot3OamLclErrEventFlagsData OBJECT-TYPE
SYNTAX BITS { SYNTAX BITS {
unidirectionalSupport (0), linkFault (0),
loopbackSupport(1), dyingGasp(1),
eventSupport(2), miscCritical(2)
variableSupport(3)
} }
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION "The OAM functions supported on this Ethernet DESCRIPTION
like interface. OAM consists of separate "The value of the OAM event flags on the most recently
functionality sets above the basic discovery generated OAMPDU. These flags are used to signal critical
process. events to an OAM peer entity. "
" REFERENCE "[802.3ah], 30.3.6.1.10"
REFERENCE "[802.3ah], REFERENCE 30.11.1.1.5" ::= { dot3OamEventStatusEntry 10 }
::= { dot3OamPeerEntry 8 }
dot3OamPeerMultiplexorState OBJECT-TYPE dot3OamLclErrEventOtherTime OBJECT-TYPE
SYNTAX INTEGER { SYNTAX TimeStamp
draft-ietf-hubmib-efm-mib-00.txt February 2004 MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The time at which the last non-802.3 define link event
occurred.
The 802.3ah OAM protocol allows for organization specific
events to be defined by any organization. Whenever a
non-802.3 defined link event occurs, this timestamp is updated
to reflect that occurrence. "
REFERENCE "[802.3ah], 57.5.3.5"
::= { dot3OamEventStatusEntry 11 }
dot3OamLclErrEventOtherData OBJECT-TYPE
SYNTAX OCTET STRING ( SIZE(3..255) )
EFM OAM MIB June 2004
forward(1),
discard(2)
}
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION "The state of the multiplexor function in the DESCRIPTION
OAM peer as reflected in the latest OAMPDU. "The value of the data field for the most recent Organization
This value is changed based on loopback Specific link event occuring on the interface. The
actions by either the local or remote device. information syntax is defined by the vendor specified in the
The normal value for this attribute is OUI field (the first 3 octets) of the data. "
'forward'. When transitioning into or out of REFERENCE "[802.3ah], 57.5.3.5"
a loopback state, the value goes to discard. ::= { dot3OamEventStatusEntry 12 }
"
REFERENCE "[802.3ah], 30.11.1.1.10."
::= { dot3OamPeerEntry 9 }
dot3OamPeerParserState OBJECT-TYPE dot3OamRmtErrSymPeriodTime OBJECT-TYPE
SYNTAX INTEGER { SYNTAX TimeStamp
forward(1),
loopback(2),
discard(3)
}
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION "The state of the parser function in the DESCRIPTION
OAM peer as reflected in the latest OAMPDU. "The time at which the last Errored Symbol Period TLV was
This value is changed based on loopback received in a unique Event Notification OAMPDU, indicating
actions by either the local or remote receipt of a notification about a remote Errored Symbol Period
device. The normal value for this attribute Event. "
is forward. REFERENCE "[802.3ah], 30.3.6.1.42 and 57.5.3.1."
::= { dot3OamEventStatusEntry 13 }
When the remote OAM entity is performing dot3OamRmtErrSymPeriodData OBJECT-TYPE
loopback operations with the local OAM entity, SYNTAX Dot3OamEventTLVData
the value goes to discard (when traffic is MAX-ACCESS read-only
looped back at the peer) or loopback (when STATUS current
traffic is looped back locally). DESCRIPTION
" "A sequence of six integers corresponding to the respective
REFERENCE "[802.3ah], 30.11.1.1.10." fields in the most recently received Errored Symbol Period
::= { dot3OamPeerEntry 10 } Event TLV in an Event Notification OAMPDU."
REFERENCE "[802.3ah], 30.3.6.1.42 and 57.5.3.1."
::= { dot3OamEventStatusEntry 14 }
-- dot3OamRmtErrFramePeriodTime OBJECT-TYPE
-- Ethernet OAM Loopback group SYNTAX TimeStamp
-- MAX-ACCESS read-only
dot3OamLoopbackTable OBJECT-TYPE
SYNTAX SEQUENCE OF Dot3OamLoopbackEntry
MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION "This table contains methods to control the DESCRIPTION
loopback state of the local link as well as "The time at which the last Errored Frame Period TLV was
indicating the status of the loopback received in a unique Event Notification OAMPDU, indicating
draft-ietf-hubmib-efm-mib-00.txt February 2004 receipt of a notification about a remote Errored Frame Period
Event. "
REFERENCE "[802.3ah], 30.3.6.1.44 and 57.5.3.3."
::= { dot3OamEventStatusEntry 15 }
function. dot3OamRmtErrFramePeriodData OBJECT-TYPE
" SYNTAX Dot3OamEventTLVData
::= { dot3OamMIB 4 } MAX-ACCESS read-only
STATUS current
dot3OamLoopbackEntry OBJECT-TYPE EFM OAM MIB June 2004
SYNTAX Dot3OamLoopbackEntry
MAX-ACCESS not-accessible DESCRIPTION
"A sequence of six integers corresponding to the respective
fields in the most recently received Errored Frame Period
Event TLV in an Event Notification OAMPDU."
REFERENCE "[802.3ah], 30.3.6.1.44 and 57.5.3.3."
::= { dot3OamEventStatusEntry 16 }
dot3OamRmtErrFrameTime OBJECT-TYPE
SYNTAX TimeStamp
MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION "An entry in the table, containing information DESCRIPTION
on the loopback status for a single Ethernet "The time at which the last Errored Frame TLV was received in
like interface. a unique Event Notification OAMPDU, indicating receipt of a
" notification about a remote Errored Frame Event. "
INDEX { ifIndex } REFERENCE "[802.3ah], 30.3.6.1.43 and 57.5.3.2."
::= { dot3OamLoopbackTable 1 } ::= { dot3OamEventStatusEntry 17 }
Dot3OamLoopbackEntry ::= dot3OamRmtErrFrameData OBJECT-TYPE
SEQUENCE { SYNTAX Dot3OamEventTLVData
dot3OamLoopbackCommand INTEGER, MAX-ACCESS read-only
dot3OamLoopbackStatus INTEGER STATUS current
} DESCRIPTION
"A sequence of six integers corresponding to the respective
fields in the most recently received Errored Frame Event TLV
in an Event Notification OAMPDU."
REFERENCE "[802.3ah], 30.3.6.1.43 and 57.5.3.2."
::= { dot3OamEventStatusEntry 18 }
dot3OamLoopbackCommand OBJECT-TYPE dot3OamRmtErrFrameSecsSumTime OBJECT-TYPE
SYNTAX INTEGER { SYNTAX TimeStamp
noLoopback (1), MAX-ACCESS read-only
startRemoteLoopback (2),
endRemoteLoopback (3)
}
MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION "This attribute initiates or terminates remote DESCRIPTION
loopback with an OAM peer. Writing "The time at which the last Errored Frame Seconds Summary TLV
'startRemoteLoopback' to this attribute cause was received in a unique Event Notification OAMPDU, indicating
the local OAM client to send a loopback OAMPDU receipt of a notification about a remote Errored Frame Seconds
to the OAM peer with the loopback enable flags Summary Event. "
set. Writing 'endRemoteLoopback' to this REFERENCE "[802.3ah], 30.3.6.1.45 and 57.5.3.4."
attribute will cause the local OAM client to ::= { dot3OamEventStatusEntry 19 }
send a loopback OAMPDU to the OAM peer with
the loopback enable flags cleared. Writing
noLoopback to this attribute has no effect.
The attribute always returns noLoopback on a dot3OamRmtErrFrameSecsSumData OBJECT-TYPE
read. To determine the loopback status, use SYNTAX Dot3OamEventTLVData
the attribute dot3OamLoopbackStatus. MAX-ACCESS read-only
" STATUS current
REFERENCE "[802.3ah], REFERENCE 57.2.11" DESCRIPTION
::= { dot3OamLoopbackEntry 1 } "A sequence of six integers corresponding to the respective
fields in the most recently received Errored Frame Seconds
Summary Event TLV in an Event Notification OAMPDU."
dot3OamLoopbackStatus OBJECT-TYPE EFM OAM MIB June 2004
SYNTAX INTEGER {
noLoopback (1),
initiatingLoopback (2),
remoteLoopback (3),
terminatingLoopback (4),
draft-ietf-hubmib-efm-mib-00.txt February 2004
localLoopback (5) REFERENCE "[802.3ah], 30.3.6.1.45 and 57.5.3.4."
::= { dot3OamEventStatusEntry 20 }
dot3OamRmtErrEventFlagsTime OBJECT-TYPE
SYNTAX TimeStamp
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The time at which the flags field in incoming OAMPDUs last
changed.
"
REFERENCE "[802.3ah], 30.3.6.1.10"
::= { dot3OamEventStatusEntry 21 }
dot3OamRmtErrEventFlagsData OBJECT-TYPE
SYNTAX BITS {
linkFault (0),
dyingGasp(1),
miscCritical(2)
} }
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION "The loopback status of the link. This status DESCRIPTION
is determined by a combination of the local "The value of the OAM event flags on the most recently
parser and multiplexer states, as well as by received OAMPDU. These flags are used to signal critical
the actions of the local OAM client. When events to an OAM peer entity. "
operating in normal mode with no loopback in REFERENCE "[802.3ah], 30.3.6.1.10"
progress, the status is 'noLoopback'. ::= { dot3OamEventStatusEntry 22 }
If the OAM client has sent an OAM loopback PDU dot3OamRmtErrEventOtherTime OBJECT-TYPE
and is waiting for a response, where the local SYNTAX TimeStamp
parser and multiplexer states are DISCARD (see MAX-ACCESS read-only
[802.3ah, 57.2.11.1]), the status is STATUS current
'initiatingLoopback'. DESCRIPTION
"The time at which the last non-802.3 defined link event
TLV was received.
If the local OAM client knows that the remote The 802.3ah OAM protocol allows for organization specific
OAM entity is in loopback mode (via the remote events to be defined by any organization. Whenever an
state information as described in [802.3ah, Organization Specific Link Event TLV is received in a Event
57.2.11.1]), the status is 'remoteLoopback'. OAMPDU, this timestamp is updated to reflect the occurrence."
If the local OAM client is in the process of REFERENCE "[802.3ah], 57.5.3.5"
terminating the remote loopback [802.3ah, ::= { dot3OamEventStatusEntry 23 }
57.2.11.3], with its local multiplexer and
parser states in DISCARD, the status is dot3OamRmtErrEventOtherData OBJECT-TYPE
'terminatingLoopback'. If the remote OAM SYNTAX OCTET STRING ( SIZE(3..255) )
client has put the local OAM entity in MAX-ACCESS read-only
loopback mode as indicated by its local parser STATUS current
state, the status is 'localLoopback'. DESCRIPTION
"
REFERENCE "[802.3ah], REFERENCE 57.2.11" EFM OAM MIB June 2004
::= { dot3OamLoopbackEntry 2 }
-- Editor's Note: No C30 attribute in D3.0, should appear
in D3.1
"The value of the data field for the most recent Organization
Specific Link Event TLV received on the interface. The
information syntax is defined by the vendor specified in the
OUI field (the first 3 octets) of the data. "
REFERENCE "[802.3ah], 57.5.3.5"
::= { dot3OamEventStatusEntry 24 }
------------------------------------------------------------------
-- --
-- Ethernet OAM Event group -- Ethernet OAM Notifications
-- --
dot3OamEventConfigTable OBJECT-TYPE
SYNTAX SEQUENCE OF Dot3OamEventConfigEntry dot3OamTraps OBJECT IDENTIFIER ::= { dot3OamMIB 7 }
MAX-ACCESS not-accessible dot3OamTrapsPrefix OBJECT IDENTIFIER ::= {dot3OamTraps 0}
dot3OamLclErrSymPeriod NOTIFICATION-TYPE
OBJECTS { ifIndex,
dot3OamLclErrSymPeriodData
}
STATUS current STATUS current
DESCRIPTION "Ethernet OAM includes the ability to generate DESCRIPTION
and receive event notifications to indicate "A dot3OamLclErrSymPeriod trap is sent when the value of the
various link problems. This table contains dot3OamLclErrSymPeriodTime changes for an Ethernet like
the mechanisms to configure the thresholds to interface supporting Ethernet OAM.
generate the standard Ethernet OAM events.
These events are:
- Errored Symbol Period Event. Generated
when the number of symbol errors exceeds a
threshold within a given window defined by
a number of symbols (e.g. 1,000 symbols out
draft-ietf-hubmib-efm-mib-00.txt February 2004
of 1,000,000 had errors). This trap can be utilized to indicate to a management system
- Errored Frame Period Event. Generated when that too many symbol errors have occured on the specified
the number of frame errors exceeds a interface, resulting in an Event Notification OAMPDU to a peer
threshold within a given window defined by and trap to the management entity.
a number of frames (e.g. 10 frames out of
1000 had errors).
- Errored Frame Event. Generated when the
number of frame errors exceeds a threshold
within a given window defined by a period
of time (e.g. 10 frames in 1 second had
errors).
- Errored Frame Seconds Summary Event.
GeneratedGenerated when the number of frame
errors exceeds a threshold within a given
window defined by a period of time (e.g. 10
frames in 1 second had errors).
- Errored Frame Seconds Summary Event.
Generated when the number of errored frame
seconds exceeds a threshold within a given
time period (e.g. 10 errored frame seconds
within the last 100 seconds). An errored
frame second is defined as a 1 second
interval which had >0 frame errors.
"
::= { dot3OamMIB 5 }
dot3OamEventConfigEntry OBJECT-TYPE The management entity should periodically check the value of
SYNTAX Dot3OamEventConfigEntry dog3LclErrSymPeriodTime to detect any missed
MAX-ACCESS not-accessible dot3OamErrSymPeriod trap-events. "
::= { dot3OamTrapsPrefix 1 }
dot3OamLclErrFramePeriod NOTIFICATION-TYPE
OBJECTS { ifIndex,
dot3OamLclErrFramePeriodData
}
STATUS current STATUS current
DESCRIPTION " DESCRIPTION
" "A dot3OamLclErrFramePeriod trap is sent when the value of the
INDEX { ifIndex } dot3OamLclErrFramePeriodTime changes for an Ethernet like
::= { dot3OamEventConfigTable 1 } interface supporting Ethernet OAM.
Dot3OamEventConfigEntry ::= This trap can be utilized to indicate to a management system
SEQUENCE { that too many frame errors have occured on the specified
dot3OamErrSymPeriodWindow Unsigned32, interface, resulting in an Event Notification OAMPDU to a peer
dot3OamErrSymPeriodThreshold Unsigned32,
dot3OamErrFramePeriodWindow Unsigned32, EFM OAM MIB June 2004
dot3OamErrFramePeriodThreshold Unsigned32,
dot3OamErrFrameWindow Integer32, and trap to the management entity.
dot3OamErrFrameThreshold Unsigned32,
dot3OamErrFrameSecsSummaryWindow Integer32, The management entity should periodically check the value of
dot3OamErrFrameSecsSummaryThreshold Integer32 dog3LclErrFramePeriodTime to detect any missed
dot3OamErrFramePeriod trap-events. "
::= { dot3OamTrapsPrefix 2 }
dot3OamLclErrFrame NOTIFICATION-TYPE
OBJECTS { ifIndex,
dot3OamLclErrFrameData
} }
STATUS current
DESCRIPTION
"A dot3OamLclErrFrame trap is sent when the value of the
dot3OamLclErrFrameTime changes for an Ethernet like interface
supporting Ethernet OAM.
dot3OamErrSymPeriodWindow OBJECT-TYPE This trap can be utilized to indicate to a management system
SYNTAX Unsigned32 that too many frame errors have occured on the specified
MAX-ACCESS read-write interface, resulting in an Event Notification OAMPDU to a peer
and trap to the management entity.
The management entity should periodically check the value of
dog3LclErrFrameTime to detect any missed dot3OamErrFrame
trap-events. "
::= { dot3OamTrapsPrefix 3 }
dot3OamLclErrFrameSecsSum NOTIFICATION-TYPE
OBJECTS { ifIndex,
dot3OamLclErrFrameSecsSumData
}
STATUS current STATUS current
DESCRIPTION "The number of symbols over which the DESCRIPTION
threshold is defined. If "A dot3OamLclErrFrameSecsSum trap is sent when the value of
the dot3OamLclErrFrameSecsSumTime changes for an Ethernet like
interface supporting Ethernet OAM.
draft-ietf-hubmib-efm-mib-00.txt February 2004 This trap can be utilized to indicate to a management system
that too many errored frame seconds have occured on the
specified interface, resulting in an Event Notification OAMPDU
to a peer and trap to the management entity.
dot3OamErrSymPeriodThreshold symbol errors The management entity should periodically check the value of
occur within a window of dog3LclErrFrameSecsSumTime to detect any missed
dot3OamErrSymPeriodWindow symbols, an Event dot3OamErrFrameSecsSum trap-events. "
Notification OAMPDU should be generated with
an Errored Symbol Period Event TLV indicating
the threshold has been crossed in this window
" ::= { dot3OamTrapsPrefix 4 }
REFERENCE "[802.3ah], 30.11.1.1.29"
::= { dot3OamEventConfigEntry 1 }
dot3OamErrSymPeriodThreshold OBJECT-TYPE dot3OamLclErrEventFlags NOTIFICATION-TYPE
SYNTAX Unsigned32
MAX-ACCESS read-write EFM OAM MIB June 2004
OBJECTS { ifIndex,
dot3OamLclErrEventFlagsData
}
STATUS current STATUS current
DESCRIPTION "The number of symbols errors that must occur DESCRIPTION
for this event to be triggered. If "A dot3OamLclErrEventFlags trap is sent when the value of
dot3OamErrSymPeriodThreshold symbol errors the dot3OamLclErrEventFlagsTime changes for an Ethernet like
occur within a window of interface supporting Ethernet OAM.
dot3OamErrSymPeriodWindow
symbols, an Event Notification OAMPDU should
be generated with an Errored Symbol Period
Event TLV indicating the threshold has been
crossed in this window.
"
REFERENCE "[802.3ah], 30.11.1.1.29"
::= { dot3OamEventConfigEntry 2 }
dot3OamErrFramePeriodWindow OBJECT-TYPE This trap can be utilized to indicate to a management system
SYNTAX Unsigned32 that a critical link event has been signaled by the sending
MAX-ACCESS read-write entity on the given interface. The value of the
dot3OamLclErrEventFlagsData provides additional details on the
critical event.
The management entity should periodically check the value of
dog3LclErrEventFlagsTime to detect any missed
dot3OamEventFlags trap-events. "
::= { dot3OamTrapsPrefix 5 }
dot3OamLclErrEventOther NOTIFICATION-TYPE
OBJECTS { ifIndex,
dot3OamLclErrEventOtherData
}
STATUS current STATUS current
DESCRIPTION "The number of frames over which the threshold DESCRIPTION
is defined. If dot3OamErrFramePeriodThreshold "A dot3OamLclErrEventOther trap is sent when the value of
frame errors occur within a window of the dot3OamLclErrEventOtherTime changes for an Ethernet like
dot3OamErrFramePeriodWindow frames, an Event interface supporting Ethernet OAM.
Notification OAMPDU should be generated with
an
Errored Frame Period Event TLV indicating the
threshold has been crossed in this window.
"
REFERENCE "[802.3ah], 30.11.1.1.33"
::= { dot3OamEventConfigEntry 3 }
dot3OamErrFramePeriodThreshold OBJECT-TYPE This trap can be utilized to indicate to a management system
SYNTAX Unsigned32 that an organization specific link event has occurred on the
MAX-ACCESS read-write specified interface. The value of the
dot3OamLclErrEventOtherData provides additional details on the
organization specific link event.
The management entity should periodically check the value of
dog3LclErrEventOtherTime to detect any missed
dot3OamEventOther trap-events. "
::= { dot3OamTrapsPrefix 6 }
dot3OamRmtErrSymPeriod NOTIFICATION-TYPE
OBJECTS { ifIndex,
dot3OamRmtErrSymPeriodData
}
STATUS current STATUS current
DESCRIPTION "The number of frame errors that must occur DESCRIPTION
for this event to be triggered. If "A dot3OamRmtErrSymPeriod trap is sent when the value of the
dot3OamErrFramePeriodThreshold frame errors dot3OamRmtErrSymPeriodTime changes for an Ethernet like
occur within a window of
dot3OamErrFramePeriodWindow frames, an Event
draft-ietf-hubmib-efm-mib-00.txt February 2004 EFM OAM MIB June 2004
Notification OAMPDU should be generated with interface supporting Ethernet OAM.
an Errored Frame Period Event TLV indicating
the threshold has been crossed in this window.
"
REFERENCE "[802.3ah], 30.11.1.1.33"
::= { dot3OamEventConfigEntry 4 }
dot3OamErrFrameWindow OBJECT-TYPE This trap can be utilized to indicate to a management system
SYNTAX Integer32 (10..600) that a Event Notification OAMPDU has been received on the
MAX-ACCESS read-write specified interface indicating an Errored Symbol Period Event
on the OAM peer entity.
The management entity should periodically check the value of
dog3RmtErrSymPeriodTime to detect any missed
dot3OamErrSymPeriod trap-events. "
::= { dot3OamTrapsPrefix 7 }
dot3OamRmtErrFramePeriod NOTIFICATION-TYPE
OBJECTS { ifIndex,
dot3OamRmtErrFramePeriodData
}
STATUS current STATUS current
DESCRIPTION "The amount of time over which the threshold DESCRIPTION
is defined. If dot3OamErrFrameThreshold "A dot3OamRmtErrFramePeriod trap is sent when the value of the
frame errors occur within a window of dot3OamRmtErrFramePeriodTime changes for an Ethernet like
dot3OamErrFrameWindow (in tenths of seconds), interface supporting Ethernet OAM.
an Event Notification OAMPDU should be
generated with an Errored Frame Event TLV
indicating the threshold has been crossed in
this window.
"
REFERENCE "[802.3ah], 30.11.1.1.31"
::= { dot3OamEventConfigEntry 5 }
dot3OamErrFrameThreshold OBJECT-TYPE This trap can be utilized to indicate to a management system
SYNTAX Unsigned32 that a Event Notification OAMPDU has been received on the
MAX-ACCESS read-write specified interface indicating an Errored Frame Period Event
on the OAM peer entity.
The management entity should periodically check the value of
dog3RmtErrFramePeriodTime to detect any missed
dot3OamErrFramePeriod trap-events. "
::= { dot3OamTrapsPrefix 8 }
dot3OamRmtErrFrame NOTIFICATION-TYPE
OBJECTS { ifIndex,
dot3OamRmtErrFrameData
}
STATUS current STATUS current
DESCRIPTION "The number of frame errors that must occur DESCRIPTION
for this event to be triggered. If "A dot3OamRmtErrFrame trap is sent when the value of the
dot3OamErrFrameThreshold frame errors occur dot3OamRmtErrFrameTime changes for an Ethernet like interface
within a window of dot3OamErrFrameWindow (in supporting Ethernet OAM.
tenths of seconds), an Event Notification
OAMPDU should be generated with an Errored
Frame Event TLV indicating the threshold has
been crossed in this window.
"
REFERENCE "[802.3ah], 30.11.1.1.31"
::= { dot3OamEventConfigEntry 6 }
dot3OamErrFrameSecsSummaryWindow OBJECT-TYPE This trap can be utilized to indicate to a management system
SYNTAX Integer32 (100..9000) that a Event Notification OAMPDU has been received on the
MAX-ACCESS read-write specified interface indicating an Errored Frame Event on the
OAM peer entity.
The management entity should periodically check the value of
dog3RmtErrFrameTime to detect any missed dot3OamErrFrame
EFM OAM MIB June 2004
trap-events. "
::= { dot3OamTrapsPrefix 9 }
dot3OamRmtErrFrameSecsSum NOTIFICATION-TYPE
OBJECTS { ifIndex,
dot3OamRmtErrFrameSecsSumData
}
STATUS current STATUS current
DESCRIPTION "The amount of time over which the threshold DESCRIPTION
is defined. If "A dot3OamRmtErrFrameSecsSum trap is sent when the value of
dot3OamErrFrameSecsSummaryThreshold frame the dot3OamRmtErrFrameSecsSumTime changes for an Ethernet like
errors occur within a window of interface supporting Ethernet OAM.
dot3OamErrFrameSecsSummaryWindow (in tenths of
seconds), an Event Notification OAMPDU should
be generated with an Errored Frame Seconds
Summary Event TLV indicating the threshold
has been crossed in this window.
"
draft-ietf-hubmib-efm-mib-00.txt February 2004 This trap can be utilized to indicate to a management system
that a Event Notification OAMPDU has been received on the
specified interface indicating an Errored Frame Seconds
Summary Event on the OAM peer entity.
REFERENCE "[802.3ah], 30.11.1.1.35" The management entity should periodically check the value of
::= { dot3OamEventConfigEntry 7 } dog3RmtErrFrameSecsSumTime to detect any missed
dot3OamErrFrameSecsSum trap-events. "
dot3OamErrFrameSecsSummaryThreshold OBJECT-TYPE ::= { dot3OamTrapsPrefix 10 }
SYNTAX Integer32 (1..900)
MAX-ACCESS read-write dot3OamRmtErrEventFlags NOTIFICATION-TYPE
OBJECTS { ifIndex,
dot3OamRmtErrEventFlagsData
}
STATUS current STATUS current
DESCRIPTION "The number of errored frame seconds that must DESCRIPTION
occur for this event to be triggered. If "A dot3OamRmtErrEventFlags trap is sent when the value of
dot3OamErrFrameSecsSummaryThreshold erroed the dot3OamRmtErrEventFlagsTime changes for an Ethernet like
seconds occur within a window of interface supporting Ethernet OAM.
dot3OamErrFrameSecsSummaryWindow (in
tenths of seconds), an Event Notification This trap can be utilized to indicate to a management system
OAMPDU should be generated with an Errored that a Event Notification OAMPDU has been received on the
Frame Seconds Summary Event TLV indicating the specified interface indicating a change in the critical event
threshold has been crossed in this window. flags carried in the Flags field of the OAMPDU.
"
REFERENCE "[802.3ah], 30.11.1.1.35" The management entity should periodically check the value of
::= { dot3OamEventConfigEntry 8 } dog3RmtErrEventFlagsTime to detect any missed
dot3OamEventFlags trap-events. "
::= { dot3OamTrapsPrefix 11 }
dot3OamRmtErrEventOther NOTIFICATION-TYPE
OBJECTS { ifIndex,
dot3OamRmtErrEventOtherData
}
STATUS current
EFM OAM MIB June 2004
DESCRIPTION
"A dot3OamRmtErrEventOther trap is sent when the value of
the dot3OamRmtErrEventOtherTime changes for an Ethernet like
interface supporting Ethernet OAM.
This trap can be utilized to indicate to a management system
that an organization specific link event has been received on
the speified interface indicating an Organization Specific
Link Event has occurred on the OAM Peer entity.
The management entity should periodically check the value of
dog3RmtErrEventOtherTime to detect any missed
dot3OamRmtErrEventOther trap-events. "
::= { dot3OamTrapsPrefix 12 }
------------------------------------------------------------------
-- --
-- Ethernet OAM Compliance group -- Ethernet OAM Compliance group
-- --
dot3OamGroups OBJECT IDENTIFIER ::= { dot3OamConformance 1 } dot3OamGroups OBJECT IDENTIFIER ::= { dot3OamConformance 1 }
dot3OamCompliances OBJECT IDENTIFIER ::= { dot3OamConformance 2 } dot3OamCompliances OBJECT IDENTIFIER ::= { dot3OamConformance 2 }
-- Compliance statements -- Compliance statements
dot3OamCompliance MODULE-COMPLIANCE dot3OamCompliance MODULE-COMPLIANCE
STATUS current STATUS current
DESCRIPTION "The compliance statement for managed entities DESCRIPTION "The compliance statement for managed entities
supporting OAM on Ethernet like interfaces. supporting OAM on Ethernet like interfaces.
" "
skipping to change at page 22, line 41 skipping to change at page 49, line 38
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, dot3OamPeerGroup, MANDATORY-GROUPS { dot3OamControlGroup,
dot3OamStatsBaseGroup } dot3OamPeerGroup,
dot3OamStatsBaseGroup
}
GROUP dot3OamLoopbackGroup GROUP dot3OamLoopbackGroup
DESCRIPTION "This group is mandatory for all IEEE 802.3 OAM DESCRIPTION
implementations that support loopback "This group is mandatory for all IEEE 802.3 OAM
functionality. implementations that support loopback functionality. "
"
GROUP dot3OamErrSymbolPeriodEventGroup GROUP dot3OamErrSymbolPeriodEventGroup
DESCRIPTION "This group is mandatory for all IEEE 802.3 OAM DESCRIPTION
implementations that support event functionality. "This group is mandatory for all IEEE 802.3 OAM
" implementations that support event functionality. "
GROUP dot3OamErrFramePeriodEventGroup
DESCRIPTION "This group is mandatory for all IEEE 802.3 OAM
implementations that support event functionality.
draft-ietf-hubmib-efm-mib-00.txt February 2004 EFM OAM MIB June 2004
" GROUP dot3OamErrFramePeriodEventGroup
DESCRIPTION
"This group is mandatory for all IEEE 802.3 OAM
implementations that support event functionality. "
GROUP dot3OamErrFrameEventGroup GROUP dot3OamErrFrameEventGroup
DESCRIPTION "This group is mandatory for all IEEE 802.3 OAM DESCRIPTION
implementations that support event functionality. "This group is mandatory for all IEEE 802.3 OAM
" implementations that support event functionality. "
GROUP dot3OamErrFrameSecsSummaryEventGroup GROUP dot3OamErrFrameSecsSummaryEventGroup
DESCRIPTION "This group is mandatory for all IEEE 802.3 OAM DESCRIPTION
implementations that support event functionality. "This group is mandatory for all IEEE 802.3 OAM
" implementations that support event functionality. "
--GROUP dot3OamVariableGroup GROUP dot3OamEventFlagsGroup
--DESCRIPTION "This group is mandatory for all IEEE 802.3 OAM DESCRIPTION
-- implementations that support variable retrieval "This group is mandatory for all IEEE 802.3 OAM
-- functionality. implementations that support criticle event functionality. "
-- "
GROUP dot3OamEventOtherGroup
DESCRIPTION
"This group is mandatory for all IEEE 802.3 OAM
implementations that support Organization Specific Event
signaling. "
GROUP dot3OamNotificationGroup
DESCRIPTION
"This group is mandatory for all IEEE 802.3 OAM
implementations that support criticle event functionality. "
::= { dot3OamCompliances 1} ::= { dot3OamCompliances 1}
dot3OamControlGroup OBJECT-GROUP dot3OamControlGroup OBJECT-GROUP
OBJECTS { dot3OamRowStatus, OBJECTS { dot3OamRowStatus,
dot3OamAdminState, dot3OamAdminState,
dot3OamOperStatus, dot3OamOperStatus,
dot3OamMode, dot3OamMode,
dot3OamMaxOamPduSize, dot3OamMaxOamPduSize,
dot3OamConfigRevision, dot3OamConfigRevision,
dot3OamFunctionsSupported dot3OamFunctionsSupported
} }
STATUS current STATUS current
DESCRIPTION "A collection of objects providing the abilities, DESCRIPTION
configuration, and status of an Ethernet OAM "A collection of objects providing the abilities,
entity. configuration, and status of an Ethernet OAM entity. "
"
::= { dot3OamGroups 1 } ::= { dot3OamGroups 1 }
EFM OAM MIB June 2004
dot3OamPeerGroup OBJECT-GROUP dot3OamPeerGroup OBJECT-GROUP
OBJECTS { dot3OamPeerRowStatus, OBJECTS { dot3OamPeerRowStatus,
dot3OamPeerMacAddress, dot3OamPeerMacAddress,
dot3OamPeerVendorOui, dot3OamPeerVendorOui,
dot3OamPeerVendorInfo, dot3OamPeerVendorInfo,
dot3OamPeerMode, dot3OamPeerMode,
dot3OamPeerFunctionsSupported, dot3OamPeerFunctionsSupported,
dot3OamPeerMaxOamPduSize, dot3OamPeerMaxOamPduSize,
dot3OamPeerConfigRevision, dot3OamPeerConfigRevision
dot3OamPeerMultiplexorState,
dot3OamPeerParserState
} }
STATUS current STATUS current
DESCRIPTION "A collection of objects providing the abilities, DESCRIPTION
configuration, and status of a peer Ethernet OAM "A collection of objects providing the abilities,
entity. configuration, and status of a peer Ethernet OAM entity. "
draft-ietf-hubmib-efm-mib-00.txt February 2004
"
::= { dot3OamGroups 2 } ::= { dot3OamGroups 2 }
dot3OamStatsBaseGroup OBJECT-GROUP dot3OamStatsBaseGroup OBJECT-GROUP
OBJECTS { OBJECTS { dot3OamInformationTx,
dot3OamPduTx,
dot3OamPduRx,
dot3OamInformationTx,
dot3OamInformationRx, dot3OamInformationRx,
dot3OamEventNotificationTx, dot3OamUniqueEventNotificationTx,
dot3OamUniqueEventNotificationRx, dot3OamUniqueEventNotificationRx,
dot3OamDuplicateEventNotificationTx,
dot3OamDuplicateEventNotificationRx, dot3OamDuplicateEventNotificationRx,
dot3OamLoopbackControlTx, dot3OamLoopbackControlTx,
dot3OamLoopbackControlRx, dot3OamLoopbackControlRx,
dot3OamVariableRequestTx, dot3OamVariableRequestTx,
dot3OamVariableRequestRx, dot3OamVariableRequestRx,
dot3OamVariableResponseTx, dot3OamVariableResponseTx,
dot3OamVariableResponseRx, dot3OamVariableResponseRx,
dot3OamOrgSpecificTx, dot3OamOrgSpecificTx,
dot3OamOrgSpecificRx, dot3OamOrgSpecificRx,
dot3OamUnsupportedCodesRx dot3OamUnsupportedCodesTx,
dot3OamUnsupportedCodesRx,
dot3OamFramesLostDueToOam
} }
STATUS current STATUS current
DESCRIPTION "A collection of objects providing the statistics DESCRIPTION
for the number of various OAMPDUs sent and "A collection of objects providing the statistics for the
received on an Ethernet like interface. number of various transmit and recieve events for OAM on an
" Ethernet like interface. Note that all of these counters must
be supported even if the related function (as described in
dot3OamFunctionsSupported) is not supported. "
::= { dot3OamGroups 3 } ::= { dot3OamGroups 3 }
dot3OamLoopbackGroup OBJECT-GROUP dot3OamLoopbackGroup OBJECT-GROUP
OBJECTS { dot3OamLoopbackCommand, OBJECTS { dot3OamLoopbackCommand,
dot3OamLoopbackStatus dot3OamLoopbackStatus,
dot3OamLoopbackIgnoreRx
} }
EFM OAM MIB June 2004
STATUS current STATUS current
DESCRIPTION "A collection of objects for controlling the OAM DESCRIPTION
remote loopback function. "A collection of objects for controlling the OAM remote
" loopback function. "
::= { dot3OamGroups 4 } ::= { dot3OamGroups 4 }
dot3OamErrSymbolPeriodEventGroup OBJECT-GROUP dot3OamErrSymbolPeriodEventGroup OBJECT-GROUP
OBJECTS { dot3OamErrSymPeriodWindow, OBJECTS { dot3OamErrSymPeriodWindow,
dot3OamErrSymPeriodThreshold dot3OamErrSymPeriodThreshold,
dot3OamErrSymPeriodEvNotifEnable,
dot3OamLclErrSymPeriodTime,
dot3OamLclErrSymPeriodData,
dot3OamRmtErrSymPeriodTime,
dot3OamRmtErrSymPeriodData
} }
STATUS current STATUS current
DESCRIPTION "A collection of objects for configuring the DESCRIPTION
thresholds for an Errored Symbol Period Event. "A collection of objects for configuring the thresholds for an
" Errored Symbol Period Event and maintaining the event
information. "
::= { dot3OamGroups 5 } ::= { dot3OamGroups 5 }
dot3OamErrFramePeriodEventGroup OBJECT-GROUP dot3OamErrFramePeriodEventGroup OBJECT-GROUP
OBJECTS { dot3OamErrFramePeriodWindow, OBJECTS { dot3OamErrFramePeriodWindow,
dot3OamErrFramePeriodThreshold dot3OamErrFramePeriodThreshold,
dot3OamErrFramePeriodEvNotifEnable,
dot3OamLclErrFramePeriodTime,
dot3OamLclErrFramePeriodData,
dot3OamRmtErrFramePeriodTime,
dot3OamRmtErrFramePeriodData
} }
draft-ietf-hubmib-efm-mib-00.txt February 2004
STATUS current STATUS current
DESCRIPTION "A collection of objects for configuring the DESCRIPTION
thresholds for an Errored Frame Period Event. "A collection of objects for configuring the thresholds for an
" Errored Frame Period Event and maintaining the event
information. "
::= { dot3OamGroups 6 } ::= { dot3OamGroups 6 }
dot3OamErrFrameEventGroup OBJECT-GROUP dot3OamErrFrameEventGroup OBJECT-GROUP
OBJECTS { dot3OamErrFrameWindow, OBJECTS { dot3OamErrFrameWindow,
dot3OamErrFrameThreshold dot3OamErrFrameThreshold,
dot3OamErrFrameEvNotifEnable,
dot3OamLclErrFrameTime,
dot3OamLclErrFrameData,
dot3OamRmtErrFrameTime,
dot3OamRmtErrFrameData
} }
STATUS current STATUS current
DESCRIPTION "A collection of objects for configuring the DESCRIPTION
thresholds for an Errored Frame Event.
" EFM OAM MIB June 2004
"A collection of objects for configuring the thresholds for an
Errored Frame Event and maintaining the event information. "
::= { dot3OamGroups 7 } ::= { dot3OamGroups 7 }
dot3OamErrFrameSecsSummaryEventGroup OBJECT-GROUP dot3OamErrFrameSecsSummaryEventGroup OBJECT-GROUP
OBJECTS { dot3OamErrFrameSecsSummaryWindow, OBJECTS { dot3OamErrFrameSecsSummaryWindow,
dot3OamErrFrameSecsSummaryThreshold dot3OamErrFrameSecsSummaryThreshold,
dot3OamErrFrameSecsEvNotifEnable,
dot3OamLclErrFrameSecsSumTime,
dot3OamLclErrFrameSecsSumData,
dot3OamRmtErrFrameSecsSumTime,
dot3OamRmtErrFrameSecsSumData
} }
STATUS current STATUS current
DESCRIPTION "A collection of objects for configuring the DESCRIPTION
thresholds for an Errored Frame Seconds Summary "A collection of objects for configuring the thresholds for an
Event. Errored Frame Seconds Summary Event and maintaining the event
" information. "
::= { dot3OamGroups 8 } ::= { dot3OamGroups 8 }
dot3OamEventFlagsGroup OBJECT-GROUP
OBJECTS { dot3OamLclErrEventFlagsTime,
dot3OamLclErrEventFlagsData,
dot3OamRmtErrEventFlagsTime,
dot3OamRmtErrEventFlagsData
}
STATUS current
DESCRIPTION
"A collection of objects for displayng the status of the event
flags (link fault, critical, dying gasp) in transmitted and
received OAMPDUs, reflecting the current status of critical
event information. "
::= { dot3OamGroups 9 }
dot3OamEventOtherGroup OBJECT-GROUP
OBJECTS { dot3OamLclErrEventOtherTime,
dot3OamLclErrEventOtherData,
dot3OamRmtErrEventOtherTime,
dot3OamRmtErrEventOtherData
}
STATUS current
DESCRIPTION
"A collection of objects for displayng the status of any
Organization Specific Events that have occurred on the
Ethernet-like interface. "
::= { dot3OamGroups 10 }
dot3OamNotificationGroup NOTIFICATION-GROUP
NOTIFICATIONS {
EFM OAM MIB June 2004
dot3OamLclErrSymPeriod,
dot3OamLclErrFramePeriod,
dot3OamLclErrFrame,
dot3OamLclErrFrameSecsSum,
dot3OamLclErrEventFlags,
dot3OamLclErrEventOther,
dot3OamRmtErrSymPeriod,
dot3OamRmtErrFramePeriod,
dot3OamRmtErrFrame,
dot3OamRmtErrFrameSecsSum,
dot3OamRmtErrEventFlags,
dot3OamRmtErrEventOther
}
STATUS current
DESCRIPTION
"A collection of notifications used by Ethernet OAM to signal
to a management entity that local or remote events have occured
on a specified Ethernet link."
::= { dot3OamGroups 11 }
END END
8 Security Considerations 7. Security Considerations
The readable objects in this module can provide information about The readable objects in this module can provide information about
network traffic, and therefore may be considered sensitive. In network traffic, and therefore may be considered sensitive. In
particular, OAM provides mechanisms for reading the IEEE 802.3 Clause particular, OAM provides mechanisms for reading the IEEE 802.3 Clause
30 MIB attributes from a link partner via a specialized layer two 30 MIB attributes from a link partner via a specialized layer two
protocol. Unlike SNMP, IEEE P802.3ah OAM does not include encryption protocol. Unlike SNMP, IEEE P802.3ah OAM does not include encryption
or authorization mechanisms. It should be used in environments where or authorization mechanisms. It should be used in environments where
either this interface information is not considered sensitive, or either this interface information is not considered sensitive, or
where the facility terminations are protected. where the facility terminations are protected. By default, OAM is
disabled on Ethernet-like interfaces and is therefore not a risk.
IEEE P802.3ah OAM is designed to support deployment in access and IEEE 802.3ah OAM is designed to support deployment in access and
enterprise networks. In access networks, one end of a link is the enterprise networks. In access networks, one end of a link is the
CO-side, and the other is the CPE-side, and the facilities are often CO-side, and the other is the CPE-side, and the facilities are often
protected in wiring cages or closets. In such deployments, it is protected in wiring cages or closets. In such deployments, it is
often the case that the CO-side is protected from access from the CPE often the case that the CO-side is protected from access from the CPE
side. Within IEEE P802.3ah OAM, this protection from remote access side. Within IEEE P802.3ah OAM, this protection from remote access
is accomplished by configuring the CPE-side in passive mode using the is accomplished by configuring the CPE-side in passive mode using the
dot3OamMode attribute. This prevents the CPE from accessing dot3OamMode attribute. This prevents the CPE from accessing
functions and information at the CO-side of the connection. In functions and information at the CO-side of the connection. In
draft-ietf-hubmib-efm-mib-00.txt February 2004
enterprise networks, read-only interface information is often enterprise networks, read-only interface information is often
considered non-sensitive. considered non-sensitive.
EFM OAM MIB June 2004
The operation of OAM on an Ethernet interface does not adversely The operation of OAM on an Ethernet interface does not adversely
affect data traffic as OAM is a slow protocol with very limited affect data traffic as OAM is a slow protocol with very limited
bandwidth potential, and it is not required for normal link bandwidth potential, and it is not required for normal link
operation. And although there are a number of objects in this module operation. And although there are a number of objects in this module
with read-write or read-create MAX-ACCESS, they only affect the with read-write or read-create MAX-ACCESS, they only affect the
operation of the OAM protocol itself and not user data traffic. operation of the OAM protocol itself and not user data traffic.
The loopback capability of OAM can have potentially disruptive The loopback capability of OAM can have potentially disruptive
effects in that the when enabling remote loopback, the remote station effects in that the when enabling remote loopback, the remote station
automatically transmits all received traffic back to the local automatically transmits all received traffic back to the local
station except for OAM traffic. This completely disrupts all higher station except for OAM traffic. This completely disrupts all higher
layer protocols such as bridging, IP, and SNMP. layer protocols such as bridging, IP, and SNMP. Therefore an
attribute (dot3OamLoopbackIgnoreRx) was introduced to control whether
the local station processes or ignores received loopback commands.
SNMP versions prior to SNMPv3 did not include adequate security. Even SNMP versions prior to SNMPv3 did not include adequate security. Even
if the network itself is secure (for example by using IPSec), even if the network itself is secure (for example by using IPSec), even
then, there is no control as to who on the secure network is allowed then, there is no control as to who on the secure network is allowed
to access and GET/SET (read/change/create/delete) the objects in this to access and GET/SET (read/change/create/delete) the objects in this
MIB module. MIB module.
It is RECOMMENDED that implementers consider the security features as It is RECOMMENDED that implementers consider the security features as
provided by the SNMPv3 framework (see [RFC3410], section 8), provided by the SNMPv3 framework (see [RFC3410], section 8),
including full support for the SNMPv3 cryptographic mechanisms (for including full support for the SNMPv3 cryptographic mechanisms (for
authentication and privacy). authentication and privacy).
Further, deployment of SNMP versions prior to SNMPv3 is NOT Further, deployment of SNMP versions prior to SNMPv3 is NOT
RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to
enable cryptographic security. It is then a customer/operator enable cryptographic security. It is then a customer/operator
responsibility to ensure that the SNMP entity giving access to an responsibility to ensure that the SNMP entity giving access to an
instance of this MIB module is properly configured to give access to instance of this MIB module is properly configured to give access to
the objects only to those principals (users) that have legitimate the objects only to those principals (users) that have legitimate
rights to indeed GET or SET (change/create/delete) them rights to indeed GET or SET (change/create/delete) them
9 References 8. References
9.1 Normative References 8.1 Normative References
[802.3ah] [802.3ah] Institute of Electrical and Electronic Engineers, IEEE
[802-2001] Draft 802.3ah-2002 Draft 3.3, "IEEE Standard for Carrier Sense
[RFC2119] Multiple Access with Collision Detection (CSMA/CD) Access Method and
[RFC2570] Physical Layer Specifications - Draft amendment to – Information
[RFC2578] technology - Telecommunications and information exchange between
[RFC2580] systems - Local and metropolitan area networks - Specific
[RFC3410] requirements - Part 3: Carrier sense multiple access with collision
detection (CSMA/CD) access method and physical layer specifications –
Media Access Control Parameters, Physical Layers and Management
Parameters", May 2004.
9.2 Informative References EFM OAM MIB June 2004
[RFC2863]
[RFC3635]
draft-ietf-hubmib-efm-mib-00.txt February 2004 [802.3-2002] Institute of Electrical and Electronic Engineers, IEEE
Std 802.3-2003, "IEEE Standard for Carrier Sense Multiple Access with
Collision Detection (CSMA/CD) Access Method and Physical Layer
Specifications - Draft amendment to – Information technology -
Telecommunications and information exchange between systems - Local
and metropolitan area networks - Specific requirements - Part 3:
Carrier sense multiple access with collision detection (CSMA/CD)
access method and physical layer specifications – Media Access
Control Parameters, Physical Layers and Management Parameters", March
2002.
10 Intellectual Property Statement [802-2001] Institute of Electrical and Electronic Engineers, IEEE
Std 802-2001, "Standard for Local and Metropolitan Area Networks:
Architecture and Overview", March 2002.
[RFC2026] Bradner, S, "The Internet Standards Process -- Revision
3", BCP 9, RFC 2026, October 1996.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997
[RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J.,
McCloghrie, K., Rose, M. and S. Waldbusser, "Structure of Management
Information Version 2 (SMIv2)", STD 58, RFC 2578, April 1999.
[RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J.,
McCloghrie, K., Rose, M. and S. Waldbusser, "Textual Conventions for
SMIv2", STD 58, RFC 2579, April 1999.
[RFC2580] McCloghrie, K., Perkins, D. and J. Schoenwaelder,
"Conformance Statements for SMIv2", STD 58, RFC 2580, April 1999.
[RFC3668] Bradner, S. "Intellectual Property Rights in IETF
Technology", BCP 79, RFC 3668, February 2004.
8.2 Informative References
[802.3ah-copper] Beili, Ed, "Managed Objects for Ethernet Passive
Optical Networks", draft-ietf-hubmib-efm-epon-mib-01.txt, April 2004.
[802.3ah-epon] Khermosh, Lior, "Ethernet in the First Mile Copper
(EFMCu) Interfaces MIB", draft-ietf-hubmib-efm-cu-mib-00.txt, January
2004.
[RFC2665] Flick, J. and Johnson J. "Definitions of Managed Objects
for the Ethernet-like Interface Types", STD 58, RFC 2580, April 1999.
EFM OAM MIB June 2004
[RFC2863] McCloghrie, K., Kastenholz, F., "The Interfaces Group
MIB", RFC 2863, June 2000.
[RFC3410] Case, J., Mundy, R., Partain, D., Stewart, B.,
"Introduction and Applicability Statements for Internet Standard
Management Framework", RFC 3410, December 2003.
[RFC3635] Flick, J., "Definitions of Managed Objects for the
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.
9. Acknowledgments
The author is grateful to all of the participants in the IEEE 802.3ah
EFM (Ethernet in the First Mile) taskforce. In particular, the
strong leadership and dedication of the following individuals is
noted:
Kevin Daines (Editor, IEEE 802.3ah OAM clauses)
Ben Brown (Editor, IEEE 802.3ah Logic clauses)
David Law (Editor, IEEE 802.3ah Management clauses)
Scott Simon (Editor, IEEE 802.3ah Clause 45)
Howard Frazier (Chair, IEEE 802.3ah)
Hugh Barass (Vice-Chair, IEEE 802.3ah)
Wael Diab (Editor, IEEE 802.3ah)
Additionally, certain devoted attendees and contributors to the IEEE
802.3ah OAM sub-taskforce deserve recognition. Although there were
many contributors, the following individuals contributed heavily over
a long period of time.
Brian Arnold
Brad Booth
Al Braga
Floyd Gerhardt
Bob Grow
Eric Lynskey
David Martin
John Messenger
Dan Romascanu (Chair, IETF HUBMIB WG)
Jonathan Thatcher
Geoff Thompson
10. Author's Address
EFM OAM MIB June 2004
Note: Author’s email address is spelled out to help protect against
email address harvesting programs.
Matt Squire
Hatteras Networks
639 Davis Drive, Suite 200
Phone: 919-991-5460
Email: msquire at hatterasnetworks dot com
11. 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 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; neither does it represent that it might or might not be available; nor does it represent that it has
has made any effort to identify any such rights. Information on the made any independent effort to identify any such rights. Information
IETF's procedures with respect to rights in standards-track and on the procedures with respect to rights in RFC documents can be
standards-related documentation can be found in BCP-11. Copies of found in BCP 78 and BCP 79.
claims of rights made available for publication and any assurances of
licenses to be made available, or the result of an attempt made to Copies of IPR disclosures made to the IETF Secretariat and any
obtain a general license or permission for the use of such assurances of licenses to be made available, or the result of an
proprietary rights by implementors or users of this specification can attempt made to obtain a general license or permission for the use of
be obtained from the IETF Secretariat. such proprietary rights by implementers or users of this
specification can be obtained from the IETF on-line IPR repository at
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 which may cover technology that may be required to practice rights that may cover technology that may be required to implement
this standard. Please address the information to the IETF Executive this standard. Please address the information to the IETF at ietf
Director. ipr@ietf.org.
11 Full Copyright Statement The IETF has been notified of intellectual property rights claimed in
regard to some or all of the specification contained in this
document. For more information consult the online list of claimed
rights.
Copyright (C) The Internet Society (2003). All Rights Reserved. This 12. Copyright Statement
document and translations of it may be copied and furnished to
others, and derivative works that comment on or otherwise explain it
or assist in its implementation may be prepared, copied, published
and distributed, in whole or in part, without restriction of any
kind, provided that the above copyright notice and this paragraph are
included on all such copies and derivative works. However, this
document itself may not be modified in any way, such as by removing
the copyright notice or references to the Internet Society or other
Internet organizations, except as needed for the purpose of
developing Internet standards in which case the procedures for
copyrights defined in the Internet Standards process must be
followed, or as required to translate it into languages other than
English.
The limited permissions granted above are perpetual and will not be Copyright (C) The Internet Society (2004). This document is subject
revoked by the Internet Society or its successors or assignees. to the rights, licenses and restrictions contained in BCP 78, and
except as set forth therein, the authors retain all their rights.
This document and the information contained herein is provided on an This document and the information contained herein are provided on an
"AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION
HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
12 Acknowledgments EFM OAM MIB June 2004
draft-ietf-hubmib-efm-mib-00.txt February 2004 ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
13 Author's Addresses Acknowledgement
Matt Squire Funding for the RFC Editor function is currently provided by the
Hatteras Networks Internet Society.
639 Davis Drive
Suite 200
Research Triangle Park, NC 27709
Email: msquire@hatterasnetworks.com
 End of changes. 

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