draft-ietf-hubmib-efm-mib-06.txt   rfc4878.txt 
INTERNET-DRAFT Matt Squire Network Working Group M. Squire
Document: draft-ietf-hubmib-efm-mib-06.txt Hatteras Networks Request for Comments: 4878 Hatteras Networks
Intended status: Proposed standard Definitions and Managed Objects for
Expires: August 2007 February 2007 Operations, Administration, and Maintenance (OAM) Functions on
Ethernet-Like Interfaces
Definitions and Managed Objects for OAM Functions on Ethernet Like
Interfaces
draft-ietf-hubmib-efm-mib-06.txt
Status of this Memo
By submitting this Internet-Draft, each author represents that any
applicable patent or other IPR claims of which he or she is aware
have been or will be disclosed, and any of which he or she becomes
aware will be disclosed, in accordance with Section 6 of BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet-
Drafts.
Internet-Drafts are draft documents valid for a maximum of six months Status of This Memo
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at This document specifies an Internet standards track protocol for the
http://www.ietf.org/ietf/1id-abstracts.txt Internet community, and requests discussion and suggestions for
improvements. Please refer to the current edition of the "Internet
Official Protocol Standards" (STD 1) for the standardization state
and status of this protocol. Distribution of this memo is unlimited.
The list of Internet-Draft Shadow Directories can be accessed at Copyright Notice
http://www.ietf.org/shadow.html.
This Internet-Draft will expire in August, 2007. Copyright (C) The IETF Trust (2007).
Abstract Abstract
This document defines objects for managing Operations, This document defines objects for managing Operations,
Administration, and Maintenance (OAM) capabilities on Ethernet like Administration, and Maintenance (OAM) capabilities on Ethernet-like
interfaces conformant to the Ethernet OAM functionality defined in interfaces conformant to the Ethernet OAM functionality defined in
the Ethernet in the First Mile (EFM) clauses of the Ethernet the Ethernet in the First Mile (EFM) clauses of the Ethernet
standards. The Ethernet OAM functionality is complementary to SNMP standards. The Ethernet OAM functionality is complementary to the
management in that it is focused on a small set of link-specific Simple Network Management Protocol (SNMP) in that it is focused on a
functions for directly connected Ethernet interfaces. This document small set of link-specific functions for directly connected Ethernet
defines objects for controlling those link OAM functions, and for interfaces. This document defines objects for controlling those link
providing results and status of the OAM functions to management OAM functions and for providing results and status of the OAM
entities. functions to management entities.
Conventions used in this document
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119 [RFC2119].
Table of Contents Table of Contents
1. Introduction...................................................2 1. Introduction ....................................................2
2. The Internet-Standard Management Framework.....................2 2. The Internet-Standard Management Framework ......................2
3. Overview.......................................................3 3. Overview ........................................................3
3.1 Remote fault indication....................................4 3.1. Remote Fault Indication ....................................4
3.2 Link monitoring............................................4 3.2. Link Monitoring ............................................4
3.3 Remote loopback............................................5 3.3. Remote Loopback ............................................5
3.4 Ethernet OAM Protocol Data Units...........................5 3.4. Ethernet OAM Protocol Data Units ...........................5
4. Relation to the Other MIB Modules..............................5 4. Relation to the Other MIB Modules ...............................5
4.1 Relation to other MIB Modules..............................5 4.1. Relation to Other MIB Modules ..............................5
4.2 Relation to other EFM MIB Modules..........................6 4.2. Relation to Other EFM MIB Modules ..........................6
4.3 Mapping of IEEE 802.3ah Managed Objects....................6 4.3. Mapping of IEEE 802.3ah Managed Objects ....................6
5. MIB Structure..................................................7 5. MIB Structure ...................................................7
6. MIB Definition.................................................8 6. MIB Definition ..................................................8
7. Security Considerations.......................................54 7. Security Considerations ........................................47
8. IANA Considerations...........................................56 8. IANA Considerations ............................................49
9. References....................................................56 9. References .....................................................49
9.1 Normative References......................................56 9.1. Normative References ......................................49
9.2 Informative References....................................57 9.2. Informative References ....................................50
10. Acknowledgments..............................................58 10. Acknowledgments ...............................................51
11. Author's Address.............................................58
12. Intellectual Property Statement..............................59
13. Copyright Statement..........................................59
1. Introduction 1. Introduction
The IEEE 802.3ah Ethernet in the First Mile (EFM) task force added The IEEE 802.3ah Ethernet in the First Mile (EFM) taskforce added new
new management capabilities to Ethernet like interfaces. These management capabilities to Ethernet-like interfaces. These
management capabilities were introduced to provide some basic OA management capabilities were introduced to provide some basic Ordered
function on Ethernet media. The defined functionality includes Aggregate (OA) function on Ethernet media. The defined functionality
discovery, error signaling, loopback, and link monitoring. This memo includes discovery, error signaling, loopback, and link monitoring.
defines a portion of the Management Information Base (MIB) for use This memo defines a portion of the Management Information Base (MIB)
with network management protocols in the Internet community to manage for use with network management protocols in the Internet community
these new Ethernet interface capabilities. to manage these new Ethernet interface capabilities.
Conventions Used in This Document
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119 [RFC2119].
2. The Internet-Standard Management Framework 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).
Objects in the MIB are defined using the mechanisms defined in the Objects in the MIB are defined using the mechanisms defined in the
Structure of Management Information (SMI). This memo specifies a MIB Structure of Management Information (SMI). This memo specifies a MIB
module that is compliant to the SMIv2, which is described in STD 58, module that is compliant to the SMIv2, which is described in STD 58,
RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580
[RFC2580]. [RFC2580].
3. Overview 3. Overview
Ethernet networks have evolved over the past 30 years from simple Ethernet networks have evolved over the past 30 years from simple
LANs to a variety of other applications, including wide area LANs to a variety of other applications, including wide-area
networks. To address some of these emerging markets, the IEEE networks. To address some of these emerging markets, the IEEE
802.3ah task force defined additional clauses in [802.3ah] for the 802.3ah task force defined additional clauses in [802.3ah] for the
IEEE 802.3 standard [802.3-2002] to better address Ethernet IEEE 802.3 standard [802.3-2002] to better address Ethernet
deployments in the public access network. Although Ethernet access deployments in the public-access network. Although Ethernet-access
deployments were the primary motivation for the task force activity, deployments were the primary motivation for the task force activity,
the results of the task force are not strictly limited to that the results of the task force are not strictly limited to that
application. Ethernet OAM can be implemented on Ethernet links that application. Ethernet OAM can be implemented on Ethernet links that
are not EFM. are not EFM.
The Ethernet in the First Mile (EFM) task force was focused on four The Ethernet in the First Mile (EFM) task force was focused on four
somewhat independent objectives to better address Ethernet access somewhat independent objectives to better address Ethernet access
deployments: optics, copper, Ethernet passive optical networks deployments: optics, copper, Ethernet passive optical networks
(Ethernet PON, or EPON), and operations, administration, and (Ethernet PON, or EPON), and operations, administration, and
maintenance (OAM). The optics sub-taskforce developed new optical maintenance (OAM). The optics sub-taskforce developed new optical
physical layers that better served the long-reach outside plant physical layers that better served the long-reach outside plant
networks typically found in the access network, including developing networks typically found in the access network, including developing
physical layers that operate up to 20Km and supporting the physical layers that operate up to 20Km and supporting the
environmental conditions of access deployments. The copper sub environmental conditions of access deployments. The copper sub-
taskforce developed two new physical layers that run Ethernet taskforce developed two new physical layers that run Ethernet
natively over existing twisted pair wires that have been supporting natively over existing twisted pair wires that have been supporting
voice services for decades. The EPON sub-taskforce developed a new voice services for decades. The EPON sub-taskforce developed a new
point-to-multipoint Ethernet physical layer, utilizing Ethernet point-to-multipoint Ethernet physical layer, utilizing Ethernet
framing natively over a time-division multiple-access (TDMA) framing natively over a time-division multiple-access (TDMA)
infrastructure. The OAM sub-taskforce introduced some basic infrastructure. The OAM sub-taskforce introduced some basic
management functionality into an Ethernet link to better monitor and management functionality into an Ethernet link to better monitor and
maintain Ethernet networks in geographically disparate networks. maintain Ethernet networks in geographically disparate networks.
This document defines the management objects necessary to integrate This document defines the management objects necessary to integrate
Ethernet OAM functionality into the SNMP management framework. Ethernet OAM functionality into the SNMP management framework.
Ethernet OAM is composed of a core set of functions, and a set of Ethernet OAM is composed of a core set of functions and a set of
optional functional groups. The mandatory functions include optional functional groups. The mandatory functions include
discovery operations (determining if the other end of the link is OA discovery operations (determining if the other end of the link is OA
capable, and what OAM functions it supports), state machine capable and what OAM functions it supports), state machine
implementation, and some critical event flows. The optional implementation, and some critical event flows. The optional
functional groups are for (a) link events, (b) remote loopback, and functional groups are for (a) link events, (b) remote loopback, and
(c) variable retrieval and response. Each optional functional group (c) variable retrieval and response. Each optional functional group
is controlled by a separate MIB table(s). is controlled by a separate MIB table(s).
Ethernet OAM is complementary with SNMP management in that it Ethernet OAM is complementary with SNMP management in that it
provides some basic management functions at layer two, rather than provides some basic management functions at layer two, rather than
using layer three and above as required by SNMP over an IP using layer three and above as required by SNMP over an IP
infrastructure. Ethernet OAM provides single-hop functionality in infrastructure. Ethernet OAM provides single-hop functionality in
that it works only between two directly connected Ethernet stations. that it works only between two directly connected Ethernet stations.
SNMP can be used to manage the Ethernet OAM interactions of one SNMP can be used to manage the Ethernet OAM interactions of one
Ethernet station with another. Ethernet station with another.
Ethernet OAM has three functional objectives which are detailed in Ethernet OAM has three functional objectives, which are detailed in
the next three sections. The definition of a basic Ethernet OA the next three sections. The definition of a basic Ethernet OA
protocol data unit is given in Section 3.4. protocol data unit is given in Section 3.4.
3.1 Remote fault indication 3.1. Remote Fault Indication
Remote fault indication provides a mechanism for one end of an Remote fault indication provides a mechanism for one end of an
Ethernet link to signal the other end that the receive path is non Ethernet link to signal the other end that the receive path is non-
operational. Some Ethernet physical layers offer mechanisms to operational. Some Ethernet physical layers offer mechanisms to
signal this condition at the physical layer. Ethernet OAM added a signal this condition at the physical layer. Ethernet OAM added a
mechanism so that some Ethernet physical layers can operate in mechanism so that some Ethernet physical layers can operate in
unidirectional mode, allowing frames to be transmitted in one unidirectional mode, allowing frames to be transmitted in one
direction even when the other direction is non-operational. direction even when the other direction is non-operational.
Traditionally, Ethernet PHYs do not allow frame transmission in one Traditionally, Ethernet PHYs do not allow frame transmission in one
direction if the other direction is not operational. Using this direction if the other direction is not operational. Using this
mode, Ethernet OAM allows frame-based signaling of remote fault mode, Ethernet OAM allows frame-based signaling of remote fault
conditions while still not allowing higher layer applications to be conditions while still not allowing higher-layer applications to be
aware of the unidirectional capability. This document includes aware of the unidirectional capability. This document includes
mechanisms for capturing that fault information and reflecting such mechanisms for capturing that fault information and reflecting such
information in objects and notifications within the SNMP management information in objects and notifications within the SNMP management
framework. framework.
3.2 Link monitoring 3.2. Link Monitoring
Ethernet OAM includes event signaling capability so that one end of Ethernet OAM includes event signaling capability so that one end of
an Ethernet link can indicate the occurrence of certain important an Ethernet link can indicate the occurrence of certain important
events to the other end of the link. This happens via layer two events to the other end of the link. This happens via layer two
protocols. This document defines methods for incorporating the protocols. This document defines methods for incorporating the
occurrence of these layer two events, both at the local end and far occurrence of these layer two events, both at the local end and far
end of the link, into the SNMP management framework. end of the link, into the SNMP management framework.
Ethernet OAM also includes mechanisms for one Ethernet station to Ethernet OAM also includes mechanisms for one Ethernet station to
query another directly connected Ethernet station about the status of query another directly connected Ethernet station about the status of
its Ethernet interface variables and status. This document does not its Ethernet interface variables and status. This document does not
include mechanisms for controlling how one Ethernet endpoint may use include mechanisms for controlling how one Ethernet endpoint may use
this functionality to query the status or statistics of a peer this functionality to query the status or statistics of a peer
Ethernet entity. Ethernet entity.
3.3 Remote loopback 3.3. Remote Loopback
Remote loopback is a link state where the peer Ethernet entity echoes Remote loopback is a link state where the peer Ethernet entity echoes
every received packet (without modifications) back onto the link. every received packet (without modifications) back onto the link.
Remote loopback is intrusive in that the other end of the link is not Remote loopback is intrusive in that the other end of the link is not
forwarding traffic from higher layers out over the link. This forwarding traffic from higher layers out over the link. This
document defines objects controlling loopback operation and reading document defines objects controlling loopback operation and reading
the status of the loopback state. the status of the loopback state.
3.4 Ethernet OAM Protocol Data Units 3.4. Ethernet OAM Protocol Data Units
An Ethernet OAM protocol data unit is a valid Ethernet frame with a An Ethernet OAM protocol data unit is a valid Ethernet frame with a
destination MAC address equal to the reserved MAC address for Slow destination Media Access Control (MAC) address equal to the reserved
Protocols (See 43B of [802.3ah]), a lengthOrType field equal to the MAC address for Slow Protocols (See 43B of [802.3ah]), a lengthOrType
reserved type for Slow Protocols, and a Slow Protocols subtype equal field equal to the reserved type for Slow Protocols, and a Slow
to that of the subtype reserved for Ethernet OAM. Protocols subtype equal to that of the subtype reserved for Ethernet
OAM.
OAMPDU is used throughout this document as an abbreviation for OAMPDU is used throughout this document as an abbreviation for
Ethernet OAM protocol data unit. OAMPDUs are the mechanism by which Ethernet OAM protocol data unit. OAMPDUs are the mechanism by which
two directly connected Ethernet interfaces to exchange OA two directly connected Ethernet interfaces exchange OA information.
information.
4. Relation to the Other MIB Modules 4. Relation to the Other MIB Modules
The definitions presented here are based on Clauses 30 and 57 of The definitions presented here are based on Clauses 30 and 57 of
[802.3ah]. Note that these clauses describe many of these variables [802.3ah]. Note that these clauses describe many of these variables
and their effects on the MAC layer. In some cases there is a one-to and their effects on the MAC layer. In some cases, there is a one-
one relationship between an object in this document and an object in to-one relationship between an object in this document and an object
the Clause 30 MIB of [802.3ah]. In other cases, the objects of this in the Clause 30 MIB of [802.3ah]. In other cases, the objects of
document reflect a more complex entity and are reflected by more than this document reflect a more complex entity and are reflected by more
one object in the Clause 30 MIB of [802.3ah]. than one object in the Clause 30 MIB of [802.3ah].
4.1 Relation to other MIB Modules 4.1. Relation to Other MIB Modules
The objects defined in this document manage OAM functionality The objects defined in this document manage OAM functionality
introduced in [802.3ah] These objects do not overlap with the introduced in [802.3ah] These objects do not overlap with the
interfaces MIB [RFC2863], the Ethernet like interfaces MIB [RFC3635], interfaces MIB [RFC2863], the Ethernet-like interfaces MIB [RFC3635],
or any other MIB currently used to manage various aspects of an or any other MIB currently used to manage various aspects of an
Ethernet interface. The objects defined here are defined for Ethernet interface. The objects defined here are defined for
Ethernet like interfaces only and use the same ifIndex as the Ethernet-like interfaces only and use the same ifIndex as the
associated Ethernet interface. Ethernet OAM can be implemented on associated Ethernet interface. Ethernet OAM can be implemented on
any Ethernet like interface. any Ethernet-like interface.
4.2 Relation to other EFM MIB Modules 4.2. Relation to Other EFM MIB Modules
The Ethernet OAM functionality and MIB Module is independent of the The Ethernet OAM functionality and MIB Module is independent of the
other functionality and MIB Modules derived from [802.3ah] for copper other functionality and MIB Modules derived from [802.3ah] for copper
[802.3ah-copper] and EPON [802.3ah-epon]. Ethernet OAM may be [802.3ah-copper] and EPON [802.3ah-epon]. Ethernet OAM may be
implemented (or not) on the new EFM interface types, just as it can implemented (or not) on the new EFM interface types, just as it can
on any other Ethernet interface. on any other Ethernet interface.
4.3 Mapping of IEEE 802.3ah Managed Objects 4.3. Mapping of IEEE 802.3ah Managed Objects
This section contains the mapping between managed objects defined in This section contains the mapping between managed objects defined in
[802.3ah] Clause 30, and managed objects defined in this document. [802.3ah] Clause 30, and managed objects defined in this document.
IEEE 802.3 Managed Object Corresponding SNMP object IEEE 802.3 Managed Object Corresponding SNMP object
oOA oOA
.aOAMID IF-MIB ifIndex .aOAMID IF-MIB ifIndex
.aOAMAdminState dot3OamAdminState .aOAMAdminState dot3OamAdminState
.aOAMMode dot3OamMode .aOAMMode dot3OamMode
skipping to change at page 9, line 17 skipping to change at page 9, line 7
FROM HCNUM-TC FROM HCNUM-TC
-- from [RFC2856] -- from [RFC2856]
ifIndex ifIndex
FROM IF-MIB FROM IF-MIB
-- from [RFC2863] -- from [RFC2863]
MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP
FROM SNMPv2-CONF; FROM SNMPv2-CONF;
-- from [RFC2580] -- from [RFC2580]
dot3OamMIB MODULE-IDENTITY dot3OamMIB MODULE-IDENTITY
LAST-UPDATED "200702140000Z" -- February 14,2007" LAST-UPDATED "200706140000Z" -- June 14,2007"
ORGANIZATION ORGANIZATION
"IETF Ethernet Interfaces and Hub MIB Working Group" "IETF Ethernet Interfaces and Hub MIB Working Group"
CONTACT-INFO CONTACT-INFO
"WG Charter: "WG Charter:
http://www.ietf.org/html.charters/hubmib-charter.html http://www.ietf.org/html.charters/hubmib-charter.html
Mailing lists: Mailing lists:
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: Bert Wijnen Chair: Bert Wijnen
skipping to change at page 9, line 40 skipping to change at page 9, line 30
Editor: Matt Squire Editor: Matt Squire
Hatteras Networks Hatteras Networks
E-mail: msquire at hatterasnetworks dot com E-mail: msquire at hatterasnetworks dot com
" "
DESCRIPTION DESCRIPTION
"The MIB module for managing the new Ethernet OAM features "The MIB module for managing the new Ethernet OAM features
introduced by the Ethernet in the First Mile task force (IEEE introduced by the Ethernet in the First Mile task force (IEEE
802.3ah). The functionality presented here is based on IEEE 802.3ah). The functionality presented here is based on IEEE
802.3ah [802.3ah], released in October, 2004. [802.3ah] was 802.3ah [802.3ah], released in October, 2004. [802.3ah] was
prepared as an addendum to the standing version of IEEE 802.3 prepared as an addendum to the standing version of IEEE 802.3
[802.3-2002] at the time. Since then, [802.3ah] has been [802.3-2002]. Since then, [802.3ah] has been
merged into the base IEEE 802.3 specification in [802.3-2005]. merged into the base IEEE 802.3 specification in [802.3-2005].
In particular, this MIB focuses on the new OAM functions In particular, this MIB focuses on the new OAM functions
introduced in Clause 57 of [802.3ah]. The OAM functionality introduced in Clause 57 of [802.3ah]. The OAM functionality
of Clause 57 is controlled by new management attributes of Clause 57 is controlled by new management attributes
introduced in Clause 30 of [802.3ah]. The OAM functions are introduced in Clause 30 of [802.3ah]. The OAM functions are
not specific to any particular Ethernet physical layer, and not specific to any particular Ethernet physical layer, and
can be generically applied to any Ethernet interface of can be generically applied to any Ethernet interface of
[802.3-2002]. [802.3-2002].
skipping to change at page 10, line 20 skipping to change at page 10, line 9
subtype reserved for Ethernet OAM. OAMPDU is used throughout subtype reserved for Ethernet OAM. OAMPDU is used throughout
this document as an abbreviation for Ethernet OAM protocol this document as an abbreviation for Ethernet OAM protocol
data unit. data unit.
The following reference is used throughout this MIB module: The following reference is used throughout this MIB module:
[802.3ah] refers to: [802.3ah] refers to:
IEEE Std 802.3ah-2004: 'Draft amendment to - IEEE Std 802.3ah-2004: 'Draft amendment to -
Information technology - Telecommunications and Information technology - Telecommunications and
information exchange between systems - Local and information exchange between systems - Local and
metropolitan are networks - Specific requirements - Part metropolitan area networks - Specific requirements - Part
3: Carrier sense multiple access with collision detection 3: Carrier sense multiple access with collision detection
(CSMA/CD) access method and physical layer specifications (CSMA/CD) access method and physical layer specifications
- Media Access Control Parameters, Physical Layers and - Media Access Control Parameters, Physical Layers and
Management Parameters for subscriber access networks', Management Parameters for subscriber access networks',
October 2004. October 2004.
[802.3-2002] refers to: [802.3-2002] refers to:
IEEE Std 802.3-2002: IEEE Std 802.3-2002:
'Information technology - Telecommunications and 'Information technology - Telecommunications and
information exchange between systems - Local and information exchange between systems - Local and
metropolitan are networks - Specific requirements - Part metropolitan area networks - Specific requirements - Part
3: Carrier sense multiple access with collision detection 3: Carrier sense multiple access with collision detection
(CSMA/CD) access method and physical layer specifications (CSMA/CD) access method and physical layer specifications
- Media Access Control Parameters, Physical Layers and - Media Access Control Parameters, Physical Layers and
Management Parameters for subscriber access networks', Management Parameters for subscriber access networks',
March 2002. March 2002.
[802.3-2005] refers to: [802.3-2005] refers to:
IEEE Std 802.3-2005: IEEE Std 802.3-2005:
'Information technology - Telecommunications and 'Information technology - Telecommunications and
information exchange between systems - Local and information exchange between systems - Local and
metropolitan are networks - Specific requirements - Part metropolitan area networks - Specific requirements - Part
3: Carrier sense multiple access with collision detection 3: Carrier sense multiple access with collision detection
(CSMA/CD) access method and physical layer specifications (CSMA/CD) access method and physical layer specifications
- Media Access Control Parameters, Physical Layers and - Media Access Control Parameters, Physical Layers and
Management Parameters for subscriber access networks', Management Parameters for subscriber access networks',
December 2005. December 2005.
[802-2001] refers to: [802-2001] refers to:
'IEEE Standard for LAN/MAN (Local Area 'IEEE Standard for LAN/MAN (Local Area
Network/Metropolitan Area Network): Overview and Network/Metropolitan Area Network): Overview and
Architecture', IEEE 802, June 2001. Architecture', IEEE 802, June 2001.
Copyright (c) The IETF Trust (2007). This version of Copyright (c) The IETF Trust (2007). This version of
this MIB module is part of RFC XXXX; See the RFC itself for this MIB module is part of RFC 4878; See the RFC itself for
full legal notices. " full legal notices. "
-- RFC Editor: Update XXXX to appropriate RFC number
-- RFC Editor: Remove these notes
REVISION "200702140000Z" -- February 14, 2007"
DESCRIPTION "Initial version, published as RFC XXXX."
-- RFC Editor: Update XXXX to appropriate RFC number
-- RFC Editor: Remove these notes
::= { mib-2 XXX } REVISION "200706140000Z" -- June 14, 2007"
-- RFC Editor: Replace value with IANA assigned number DESCRIPTION "Initial version, published as RFC 4878."
-- RFC Editor: Remove these notes ::= { mib-2 158 }
-- --
-- Sections of the Ethernet OAM MIB -- Sections of the Ethernet OAM MIB
-- --
dot3OamNotifications OBJECT IDENTIFIER ::= { dot3OamMIB 0 } dot3OamNotifications OBJECT IDENTIFIER ::= { dot3OamMIB 0 }
dot3OamObjects OBJECT IDENTIFIER ::= { dot3OamMIB 1 } dot3OamObjects OBJECT IDENTIFIER ::= { dot3OamMIB 1 }
dot3OamConformance OBJECT IDENTIFIER ::= { dot3OamMIB 2 } dot3OamConformance OBJECT IDENTIFIER ::= { dot3OamMIB 2 }
-- --
-- Textual conventions for OAM MIB -- Textual conventions for the OAM MIB
-- --
EightOTwoOui ::= TEXTUAL-CONVENTION EightOTwoOui ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"24-bit Organizationally Unique Identifier. Information on "24-bit Organizationally Unique Identifier. Information on
OUIs can be found in IEEE 802-2001 [802-2001] Clause 9." OUIs can be found in IEEE 802-2001 [802-2001], Clause 9."
SYNTAX OCTET STRING(SIZE(3)) SYNTAX OCTET STRING(SIZE(3))
-- *************************************************************** -- ***************************************************************
-- --
-- Ethernet OAM Control group -- Ethernet OAM Control group
-- --
dot3OamTable OBJECT-TYPE dot3OamTable OBJECT-TYPE
SYNTAX SEQUENCE OF Dot3OamEntry SYNTAX SEQUENCE OF Dot3OamEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table contains the primary controls and status for the "This table contains the primary controls and status for the
OAM capabilities of an Ethernet like interface. There will be OAM capabilities of an Ethernet-like interface. There will be
one row in this table for each Ethernet like interface in the one row in this table for each Ethernet-like interface in the
system that supports the OAM functions defined in [802.3ah]. system that supports the OAM functions defined in [802.3ah].
" "
::= { dot3OamObjects 1 } ::= { dot3OamObjects 1 }
dot3OamEntry OBJECT-TYPE dot3OamEntry OBJECT-TYPE
SYNTAX Dot3OamEntry SYNTAX Dot3OamEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry in the table, containing information on the Ethernet "An entry in the table that contains information on the
OAM function for a single Ethernet like interface. Entries in Ethernet OAM function for a single Ethernet like interface.
the table are created automatically for each interface Entries in the table are created automatically for each
supporting Ethernet OAM. The status of the row entry can be interface supporting Ethernet OAM. The status of the row
determined from dot3OamOperStatus. entry can be determined from dot3OamOperStatus.
A dot3OamEntry is indexed in the dot3OamTable by the ifIndex A dot3OamEntry is indexed in the dot3OamTable by the ifIndex
object of the Interfaces MIB. object of the Interfaces MIB.
" "
INDEX { ifIndex } INDEX { ifIndex }
::= { dot3OamTable 1 } ::= { dot3OamTable 1 }
Dot3OamEntry ::= Dot3OamEntry ::=
SEQUENCE { SEQUENCE {
dot3OamAdminState INTEGER, dot3OamAdminState INTEGER,
dot3OamOperStatus INTEGER, dot3OamOperStatus INTEGER,
dot3OamMode INTEGER, dot3OamMode INTEGER,
dot3OamMaxOamPduSize Unsigned32, dot3OamMaxOamPduSize Unsigned32,
dot3OamConfigRevision Unsigned32, dot3OamConfigRevision Unsigned32,
dot3OamFunctionsSupported BITS dot3OamFunctionsSupported BITS
} }
skipping to change at page 13, line 41 skipping to change at page 13, line 13
"At initialization and failure conditions, two OAM entities on "At initialization and failure conditions, two OAM entities on
the same full-duplex Ethernet link begin a discovery phase to the same full-duplex Ethernet link begin a discovery phase to
determine what OAM capabilities may be used on that link. The determine what OAM capabilities may be used on that link. The
progress of this initialization is controlled by the OA progress of this initialization is controlled by the OA
sublayer. sublayer.
This value is always disabled(1) if OAM is disabled on this This value is always disabled(1) if OAM is disabled on this
interface via the dot3OamAdminState. interface via the dot3OamAdminState.
If the link has detected a fault and is transmitting OAMPDUs If the link has detected a fault and is transmitting OAMPDUs
with a link fault indication, the value is linkFault(2). Also, with a link fault indication, the value is linkFault(2).
if the interface is not operational (ifOperStatus is not Also, if the interface is not operational (ifOperStatus is
up(1)), linkFault(2) is returned. Note that the object not up(1)), linkFault(2) is returned. Note that the object
ifOperStatus may not be up(1) as a result of link failure or ifOperStatus may not be up(1) as a result of link failure or
administrative action (ifAdminState being down(2) or administrative action (ifAdminState being down(2) or
testing(3)). testing(3)).
The passiveWait(3) state is returned only by OAM entities in The passiveWait(3) state is returned only by OAM entities in
passive mode (dot3OamMode) and reflects the state in which the passive mode (dot3OamMode) and reflects the state in which the
OAM entity is waiting to see if the peer device is OA OAM entity is waiting to see if the peer device is OA
capable. The activeSendLocal(4) value is used by active mode capable. The activeSendLocal(4) value is used by active mode
devices (dot3OamMode) and reflects the OAM entity actively devices (dot3OamMode) and reflects the OAM entity actively
trying to discover whether the peer has OAM capability but has trying to discover whether the peer has OAM capability but has
skipping to change at page 14, line 45 skipping to change at page 14, line 16
aOAMRemoteFlagsField of 30.3.6.1.11). aOAMRemoteFlagsField of 30.3.6.1.11).
When the local OAM entity learns that both it and the remote When the local OAM entity learns that both it and the remote
OAM entity have accepted the peering, the state moves to OAM entity have accepted the peering, the state moves to
operational(9) corresponding to the SEND_ANY state of the operational(9) corresponding to the SEND_ANY state of the
Discovery state diagram [802.3ah, Figure 57-5]. Discovery state diagram [802.3ah, Figure 57-5].
Since Ethernet OAM functions are not designed to work Since Ethernet OAM functions are not designed to work
completely over half-duplex interfaces, the value completely over half-duplex interfaces, the value
nonOperHalfDuplex(10) is returned whenever Ethernet OAM is nonOperHalfDuplex(10) is returned whenever Ethernet OAM is
enabled (dot3OamAdminState is enabled(1)) but the interface is enabled (dot3OamAdminState is enabled(1)), but the interface
in half-duplex operation. is in half-duplex operation.
" "
REFERENCE "[802.3ah], 30.3.6.1.4, 30.3.6.1.10, 30.3.6.1.11" REFERENCE "[802.3ah], 30.3.6.1.4, 30.3.6.1.10, 30.3.6.1.11"
::= { dot3OamEntry 2 } ::= { dot3OamEntry 2 }
dot3OamMode OBJECT-TYPE dot3OamMode OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
passive(1), passive(1),
active(2) active(2)
} }
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object configures the mode of OAM operation for this "This object configures the mode of OAM operation for this
Ethernet like interface. OAM on Ethernet interfaces may be in Ethernet-like interface. OAM on Ethernet interfaces may be in
'active' mode or 'passive' mode. These two modes differ in 'active' mode or 'passive' mode. These two modes differ in
that active mode provides additional capabilities to initiate that active mode provides additional capabilities to initiate
monitoring activities with the remote OAM peer entity, while monitoring activities with the remote OAM peer entity, while
passive mode generally waits for the peer to initiate OA passive mode generally waits for the peer to initiate OA
actions with it. As an example, an active OAM entity can put actions with it. As an example, an active OAM entity can put
the remote OAM entity in a loopback state, where a passive OA the remote OAM entity in a loopback state, where a passive OA
entity cannot. entity cannot.
The default value of dot3OamMode is dependent on the type of The default value of dot3OamMode is dependent on the type of
system on which this Ethernet like interface resides. The system on which this Ethernet-like interface resides. The
default value should be 'active(2)' unless it is known that default value should be 'active(2)' unless it is known that
this system should take on a subservient role to the other this system should take on a subservient role to the other
device connected over this interface. device connected over this interface.
Changing this value results in incrementing the configuration Changing this value results in incrementing the configuration
revision field of locally generated OAMPDUs (30.3.6.1.12) and revision field of locally generated OAMPDUs (30.3.6.1.12) and
potentially re-doing the OAM discovery process if the potentially re-doing the OAM discovery process if the
dot3OamOperStatus was already operational(9). dot3OamOperStatus was already operational(9).
" "
REFERENCE "[802.3ah], 30.3.6.1.3" REFERENCE "[802.3ah], 30.3.6.1.3"
skipping to change at page 16, line 10 skipping to change at page 15, line 27
REFERENCE "[802.3ah], 30.3.6.1.8" REFERENCE "[802.3ah], 30.3.6.1.8"
::= { dot3OamEntry 4 } ::= { dot3OamEntry 4 }
dot3OamConfigRevision OBJECT-TYPE dot3OamConfigRevision OBJECT-TYPE
SYNTAX Unsigned32(0..65535) SYNTAX Unsigned32(0..65535)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The configuration revision of the OAM entity as reflected in "The configuration revision of the OAM entity as reflected in
the latest OAMPDU sent by the OAM entity. The config revision the latest OAMPDU sent by the OAM entity. The config revision
is used by OAM entities to indicate configuration changes have is used by OAM entities to indicate that configuration changes
occurred which might require the peer OAM entity to have occurred, which might require the peer OAM entity to
re-evaluate whether OAM peering is allowed. re-evaluate whether OAM peering is allowed.
" "
REFERENCE "[802.3ah], 30.3.6.1.12" REFERENCE "[802.3ah], 30.3.6.1.12"
::= { dot3OamEntry 5 } ::= { dot3OamEntry 5 }
dot3OamFunctionsSupported OBJECT-TYPE dot3OamFunctionsSupported OBJECT-TYPE
SYNTAX BITS { SYNTAX BITS {
unidirectionalSupport (0), unidirectionalSupport (0),
loopbackSupport(1), loopbackSupport(1),
eventSupport(2), eventSupport(2),
variableSupport(3) variableSupport(3)
} }
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The OAM functions supported on this Ethernet like interface. "The OAM functions supported on this Ethernet-like interface.
OAM consists of separate functional sets beyond the basic OAM consists of separate functional sets beyond the basic
discovery process which is always required. These functional discovery process that is always required. These functional
groups can be supported independently by any implementation. groups can be supported independently by any implementation.
These values are communicated to the peer via the local These values are communicated to the peer via the local
configuration field of Information OAMPDUs. configuration field of Information OAMPDUs.
Setting 'unidirectionalSupport(0)' indicates that the OA Setting 'unidirectionalSupport(0)' indicates that the OA
entity supports the transmission of OAMPDUs on links that are entity supports the transmission of OAMPDUs on links that are
operating in undirectional mode (traffic flowing in one operating in unidirectional mode (traffic flowing in one
direction only). Setting 'loopbackSupport(1)' indicates the direction only). Setting 'loopbackSupport(1)' indicates that
OAM entity can initiate and respond to loopback commands. the OAM entity can initiate and respond to loopback commands.
Setting 'eventSupport(2)' indicates the OAM entity can send Setting 'eventSupport(2)' indicates that the OAM entity can
and receive Event Notification OAMPDUs. Setting send and receive Event Notification OAMPDUs. Setting
'variableSupport(3)' indicates the OAM entity can send and 'variableSupport(3)' indicates that the OAM entity can send
receive Variable Request and Response OAMPDUs. and receive Variable Request and Response OAMPDUs.
" "
REFERENCE "[802.3ah], 30.3.6.1.6" REFERENCE "[802.3ah], 30.3.6.1.6"
::= { dot3OamEntry 6 } ::= { dot3OamEntry 6 }
-- *************************************************************** -- ***************************************************************
-- --
-- Ethernet OAM Peer group -- Ethernet OAM Peer group
-- --
dot3OamPeerTable OBJECT-TYPE dot3OamPeerTable OBJECT-TYPE
SYNTAX SEQUENCE OF Dot3OamPeerEntry SYNTAX SEQUENCE OF Dot3OamPeerEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table contains information about the OAM peer for a "This table contains information about the OAM peer for a
particular Ethernet like interface. OAM entities communicate particular Ethernet-like interface. OAM entities communicate
with a single OAM peer entity on Ethernet links on which OA with a single OAM peer entity on Ethernet links on which OA
is enabled and operating properly. There is one entry in this is enabled and operating properly. There is one entry in this
table for each entry in the dot3OamTable for which information table for each entry in the dot3OamTable for which information
on the peer OAM entity is available. on the peer OAM entity is available.
" "
::= { dot3OamObjects 2 } ::= { dot3OamObjects 2 }
dot3OamPeerEntry OBJECT-TYPE dot3OamPeerEntry OBJECT-TYPE
SYNTAX Dot3OamPeerEntry SYNTAX Dot3OamPeerEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry in the table, containing information on the peer OA "An entry in the table containing information on the peer OA
entity for a single Ethernet like interface. entity for a single Ethernet-like interface.
Note that there is at most one OAM peer for each Ethernet like Note that there is at most one OAM peer for each Ethernet-like
interface. Entries are automatically created when information interface. Entries are automatically created when information
about the OAM peer entity becomes available, and automatically about the OAM peer entity becomes available, and automatically
deleted when the OAM peer entity is no longer in deleted when the OAM peer entity is no longer in
communication. Peer information is not available when communication. Peer information is not available when
dot3OamOperStatus is disabled(1), linkFault(2), dot3OamOperStatus is disabled(1), linkFault(2),
passiveWait(3), activeSendLocal(4), or nonOperHalfDuplex(10). passiveWait(3), activeSendLocal(4), or nonOperHalfDuplex(10).
" "
INDEX { ifIndex } INDEX { ifIndex }
::= { dot3OamPeerTable 1 } ::= { dot3OamPeerTable 1 }
skipping to change at page 18, line 36 skipping to change at page 17, line 49
REFERENCE "[802.3ah], 30.3.6.1.16." REFERENCE "[802.3ah], 30.3.6.1.16."
::= { dot3OamPeerEntry 2 } ::= { dot3OamPeerEntry 2 }
dot3OamPeerVendorInfo OBJECT-TYPE dot3OamPeerVendorInfo OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The Vendor Info of the OAM peer as reflected in the latest "The Vendor Info of the OAM peer as reflected in the latest
Information OAMPDU received with a Local Information TLV. Information OAMPDU received with a Local Information TLV.
The semantics of the vendor information field is proprietary The semantics of the Vendor Information field is proprietary
and specific to the vendor (identified by the and specific to the vendor (identified by the
dot3OamPeerVendorOui). This information could, for example, dot3OamPeerVendorOui). This information could, for example,
be used to identify a specific product or product family. be used to identify a specific product or product family.
This value is initialized to zero before any Local This value is initialized to zero before any Local
Information TLV is received. Information TLV is received.
" "
REFERENCE "[802.3ah], 30.3.6.1.17." REFERENCE "[802.3ah], 30.3.6.1.17."
::= { dot3OamPeerEntry 3 } ::= { dot3OamPeerEntry 3 }
dot3OamPeerMode OBJECT-TYPE dot3OamPeerMode OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
passive(1), passive(1),
active(2), active(2),
unknown(3) unknown(3)
} }
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The mode of the OAM peer as reflected in the latest "The mode of the OAM peer as reflected in the latest
skipping to change at page 19, line 20 skipping to change at page 18, line 27
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The mode of the OAM peer as reflected in the latest "The mode of the OAM peer as reflected in the latest
Information OAMPDU received with a Local Information TLV. The Information OAMPDU received with a Local Information TLV. The
mode of the peer can be determined from the Configuration mode of the peer can be determined from the Configuration
field in the Local Information TLV of the last Information field in the Local Information TLV of the last Information
OAMPDU received from the peer. The value is unknown(3) OAMPDU received from the peer. The value is unknown(3)
whenever no Local Information TLV has been received. The whenever no Local Information TLV has been received. The
values of active(2) and passive(1) are returned when a Local values of active(2) and passive(1) are returned when a Local
Information TLV has been received indicating the peer is in Information TLV has been received indicating that the peer is
active or passive mode, respectively. in active or passive mode, respectively.
" "
REFERENCE "[802.3ah], 30.3.6.1.7." REFERENCE "[802.3ah], 30.3.6.1.7."
::= { dot3OamPeerEntry 4 } ::= { dot3OamPeerEntry 4 }
dot3OamPeerMaxOamPduSize OBJECT-TYPE dot3OamPeerMaxOamPduSize OBJECT-TYPE
SYNTAX Unsigned32 (0 | 64..1518) SYNTAX Unsigned32 (0 | 64..1518)
UNITS "octets" UNITS "octets"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
skipping to change at page 19, line 44 skipping to change at page 19, line 4
Information TLV. Ethernet OAM on this interface must not use Information TLV. Ethernet OAM on this interface must not use
OAMPDUs that exceed this size. The maximum OAMPDU size can be OAMPDUs that exceed this size. The maximum OAMPDU size can be
determined from the PDU Configuration field of the Local determined from the PDU Configuration field of the Local
Information TLV of the last Information OAMPDU received from Information TLV of the last Information OAMPDU received from
the peer. A value of zero is returned if no Local Information the peer. A value of zero is returned if no Local Information
TLV has been received. Otherwise, the value of the OAM peer's TLV has been received. Otherwise, the value of the OAM peer's
maximum OAMPDU size is returned in this value. maximum OAMPDU size is returned in this value.
" "
REFERENCE "[802.3ah], 30.3.6.1.9." REFERENCE "[802.3ah], 30.3.6.1.9."
::= { dot3OamPeerEntry 5 } ::= { dot3OamPeerEntry 5 }
dot3OamPeerConfigRevision OBJECT-TYPE dot3OamPeerConfigRevision OBJECT-TYPE
SYNTAX Unsigned32(0..65535) SYNTAX Unsigned32(0..65535)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The configuration revision of the OAM peer as reflected in "The configuration revision of the OAM peer as reflected in
the latest OAMPDU. This attribute is changed by the peer the latest OAMPDU. This attribute is changed by the peer
whenever it has a local configuration change for Ethernet OA whenever it has a local configuration change for Ethernet OA
this interface. The configuration revision can be determined on this interface. The configuration revision can be
from the Revision field of the Local Information TLV of the determined from the Revision field of the Local Information
most recently received Information OAMPDU with a Local TLV of the most recently received Information OAMPDU with
Information TLV. A value of zero is returned if no Local a Local Information TLV. A value of zero is returned if
Information TLV has been received. no Local Information TLV has been received.
" "
REFERENCE "[802.3ah], 30.3.6.1.13." REFERENCE "[802.3ah], 30.3.6.1.13."
::= { dot3OamPeerEntry 6 } ::= { dot3OamPeerEntry 6 }
dot3OamPeerFunctionsSupported OBJECT-TYPE dot3OamPeerFunctionsSupported OBJECT-TYPE
SYNTAX BITS { SYNTAX BITS {
unidirectionalSupport (0), unidirectionalSupport (0),
loopbackSupport(1), loopbackSupport(1),
eventSupport(2), eventSupport(2),
variableSupport(3) variableSupport(3)
} }
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The OAM functions supported on this Ethernet like interface. "The OAM functions supported on this Ethernet-like interface.
OAM consists of separate functionality sets above the basic OAM consists of separate functionality sets above the basic
discovery process. This value indicates the capabilities of discovery process. This value indicates the capabilities of
the peer OAM entity with respect to these functions. This the peer OAM entity with respect to these functions. This
value is initialized so all bits are clear. value is initialized so all bits are clear.
If unidirectionalSupport(0) is set, then the peer OAM entity If unidirectionalSupport(0) is set, then the peer OAM entity
supports sending OAM frames on Ethernet interfaces when the supports sending OAM frames on Ethernet interfaces when the
receive path is known to be inoperable. If receive path is known to be inoperable. If
loopbackSupport(1) is set, then the peer OAM entity can send loopbackSupport(1) is set, then the peer OAM entity can send
and receive OAM loopback commands. If eventSupport(2) is set, and receive OAM loopback commands. If eventSupport(2) is set,
then the peer OAM entity can send and receive event OAMPDUs to then the peer OAM entity can send and receive event OAMPDUs to
signal various error conditions. If variableSupport(3) is set, signal various error conditions. If variableSupport(3) is
then the peer OAM entity can send and receive variable set, then the peer OAM entity can send and receive variable
requests to monitor attribute value as described in Clause 57 requests to monitor the attribute value as described in Clause
of [802.3ah]. 57 of [802.3ah].
The capabilities of the OAM peer can be determined from the The capabilities of the OAM peer can be determined from the
configuration field of the Local Information TLV of the most configuration field of the Local Information TLV of the most
recently received Information OAMPDU with a Local Information recently received Information OAMPDU with a Local Information
TLV. All zeros are returned if no Local Information TLV has TLV. All zeros are returned if no Local Information TLV has
yet been received. yet been received.
" "
REFERENCE "[802.3ah], REFERENCE 30.3.6.1.7." REFERENCE "[802.3ah], REFERENCE 30.3.6.1.7."
::= { dot3OamPeerEntry 7 } ::= { dot3OamPeerEntry 7 }
skipping to change at page 21, line 17 skipping to change at page 20, line 20
-- --
-- Ethernet OAM Loopback group -- Ethernet OAM Loopback group
-- --
dot3OamLoopbackTable OBJECT-TYPE dot3OamLoopbackTable OBJECT-TYPE
SYNTAX SEQUENCE OF Dot3OamLoopbackEntry SYNTAX SEQUENCE OF Dot3OamLoopbackEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table contains controls for the loopback state of the "This table contains controls for the loopback state of the
local link as well as indicating the status of the loopback local link as well as indicates the status of the loopback
function. There is one entry in this table for each entry in function. There is one entry in this table for each entry in
dot3OamTable that supports loopback functionality (where dot3OamTable that supports loopback functionality (where
dot3OamFunctionsSupported includes the loopbackSupport bit dot3OamFunctionsSupported includes the loopbackSupport bit
set). set).
Loopback can be used to place the remote OAM entity in a state Loopback can be used to place the remote OAM entity in a state
where every received frame (except OAMPDUs) are echoed back where every received frame (except OAMPDUs) is echoed back
over the same interface on which they were received. In this over the same interface on which they were received. In this
state, at the remote entity, 'normal' traffic is disabled as state, at the remote entity, 'normal' traffic is disabled as
only the looped back frames are transmitted on the interface. only the looped back frames are transmitted on the interface.
Loopback is thus an intrusive operation that prohibits normal Loopback is thus an intrusive operation that prohibits normal
data flow and should be used accordingly. " data flow and should be used accordingly.
"
::= { dot3OamObjects 3 } ::= { dot3OamObjects 3 }
dot3OamLoopbackEntry OBJECT-TYPE dot3OamLoopbackEntry OBJECT-TYPE
SYNTAX Dot3OamLoopbackEntry SYNTAX Dot3OamLoopbackEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry in the table, containing information on the loopback "An entry in the table, containing information on the loopback
status for a single Ethernet like interface. Entries in the status for a single Ethernet-like interface. Entries in the
table are automatically created whenever the local OAM entity table are automatically created whenever the local OAM entity
supports loopback capabilities. The loopback status on the supports loopback capabilities. The loopback status on the
interface can be determined from the dot3OamLoopbackStatus interface can be determined from the dot3OamLoopbackStatus
object. object.
" "
INDEX { ifIndex } INDEX { ifIndex }
::= { dot3OamLoopbackTable 1 } ::= { dot3OamLoopbackTable 1 }
Dot3OamLoopbackEntry ::= Dot3OamLoopbackEntry ::=
SEQUENCE { SEQUENCE {
skipping to change at page 22, line 45 skipping to change at page 21, line 45
can be read or written. The other values can only be read - can be read or written. The other values can only be read -
they can never be written. Writing initiatingLoopback causes they can never be written. Writing initiatingLoopback causes
the local OAM entity to start the loopback process with its the local OAM entity to start the loopback process with its
peer. This value can only be written when the status is peer. This value can only be written when the status is
noLoopback(1). Writing the value initiatingLoopback(2) in any noLoopback(1). Writing the value initiatingLoopback(2) in any
other state has no effect. When in remoteLoopback(3), writing other state has no effect. When in remoteLoopback(3), writing
terminatingLoopback(4) causes the local OAM entity to initiate terminatingLoopback(4) causes the local OAM entity to initiate
the termination of the loopback state. Writing the termination of the loopback state. Writing
terminatingLoopack(4) in any other state has no effect. terminatingLoopack(4) in any other state has no effect.
If the OAM client initiates a loopback and has sent an If the OAM client initiates a loopback and has sent a
Loopback OAMPDU and is waiting for a response, where the local Loopback OAMPDU and is waiting for a response, where the local
parser and multiplexer states are DISCARD (see [802.3ah, parser and multiplexer states are DISCARD (see [802.3ah,
57.2.11.1]), the status is 'initiatingLoopback'. In this 57.2.11.1]), the status is 'initiatingLoopback'. In this
case, the local OAM entity has yet to receive any case, the local OAM entity has yet to receive any
acknowledgement that the remote OAM entity has received its acknowledgment that the remote OAM entity has received its
loopback command request. loopback command request.
If the local OAM client knows that the remote OAM entity is in If the local OAM client knows that the remote OAM entity is in
loopback mode (via the remote state information as described loopback mode (via the remote state information as described
in [802.3ah, 57.2.11.1, 30.3.6.1.15]), the status is in [802.3ah, 57.2.11.1, 30.3.6.1.15]), the status is
remoteLoopback(3). If the local OAM client is in the process remoteLoopback(3). If the local OAM client is in the process
of terminating the remote loopback [802.3ah, 57.2.11.3, of terminating the remote loopback [802.3ah, 57.2.11.3,
30.3.6.1.14], with its local multiplexer and parser states in 30.3.6.1.14] with its local multiplexer and parser states in
DISCARD, the status is terminatingLoopback(4). If the remote DISCARD, the status is terminatingLoopback(4). If the remote
OAM client has put the local OAM entity in loopback mode as OAM client has put the local OAM entity in loopback mode as
indicated by its local parser state, the status is indicated by its local parser state, the status is
localLoopback(5). localLoopback(5).
The unknown(6) status indicates the parser and multiplexer The unknown(6) status indicates that the parser and
combination is unexpected. This status may be returned if the multiplexer combination is unexpected. This status may be
OAM loopback is in a transition state but should not persist. returned if the OAM loopback is in a transition state but
should not persist.
The values of this attribute correspond to the following The values of this attribute correspond to the following
values of the local and remote parser and multiplexer states. values of the local and remote parser and multiplexer states.
value LclPrsr LclMux RmtPrsr RmtMux value LclPrsr LclMux RmtPrsr RmtMux
noLoopback FWD FWD FWD FWD noLoopback FWD FWD FWD FWD
initLoopback DISCARD DISCARD FWD FWD initLoopback DISCARD DISCARD FWD FWD
rmtLoopback DISCARD FWD LPBK DISCARD rmtLoopback DISCARD FWD LPBK DISCARD
tmtngLoopback DISCARD DISCARD LPBK DISCARD tmtngLoopback DISCARD DISCARD LPBK DISCARD
lclLoopback LPBK DISCARD DISCARD FWD lclLoopback LPBK DISCARD DISCARD FWD
skipping to change at page 23, line 41 skipping to change at page 22, line 41
" "
REFERENCE "[802.3ah], REFERENCE 57.2.11, 30.3.61.14, REFERENCE "[802.3ah], REFERENCE 57.2.11, 30.3.61.14,
30.3.6.1.15" 30.3.6.1.15"
::= { dot3OamLoopbackEntry 1 } ::= { dot3OamLoopbackEntry 1 }
dot3OamLoopbackIgnoreRx OBJECT-TYPE dot3OamLoopbackIgnoreRx OBJECT-TYPE
SYNTAX INTEGER { ignore(1), process(2) } SYNTAX INTEGER { ignore(1), process(2) }
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Since OAM loopback is a distruptive operation (user traffic "Since OAM loopback is a disruptive operation (user traffic
does not pass), this attribute provides a mechanism to provide does not pass), this attribute provides a mechanism to provide
controls over whether received OAM loopback commands are controls over whether received OAM loopback commands are
processed or ignored. When the value is ignore(1), received processed or ignored. When the value is ignore(1), received
loopback commands are ignored. When the value is process(2), loopback commands are ignored. When the value is process(2),
OAM loopback commands are processed. The default value is to OAM loopback commands are processed. The default value is to
ignore loopback commands (ignore(1)). ignore loopback commands (ignore(1)).
" "
REFERENCE "[802.3ah], REFERENCE 57.2.11, 30.3.61.14, REFERENCE "[802.3ah], REFERENCE 57.2.11, 30.3.61.14,
30.3.6.1.15" 30.3.6.1.15"
::= { dot3OamLoopbackEntry 2 } ::= { dot3OamLoopbackEntry 2 }
skipping to change at page 24, line 17 skipping to change at page 23, line 15
-- --
-- Ethernet OAM Statistics group -- Ethernet OAM Statistics group
-- --
dot3OamStatsTable OBJECT-TYPE dot3OamStatsTable OBJECT-TYPE
SYNTAX SEQUENCE OF Dot3OamStatsEntry SYNTAX SEQUENCE OF Dot3OamStatsEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table contains statistics for the OAM function on a "This table contains statistics for the OAM function on a
particular Ethernet like interface. There is an entry in the particular Ethernet-like interface. There is an entry in the
table for every entry in the dot3OamTable. table for every entry in the dot3OamTable.
The counters in this table are defined as 32-bit entries to The counters in this table are defined as 32-bit entries to
match the counter size as defined in [802.3ah]. Given the OA match the counter size as defined in [802.3ah]. Given that
protocol is a slow protocol, the counters increment at a slow the OA protocol is a slow protocol, the counters increment at
rate. a slow rate.
" "
::= { dot3OamObjects 4 } ::= { dot3OamObjects 4 }
dot3OamStatsEntry OBJECT-TYPE dot3OamStatsEntry OBJECT-TYPE
SYNTAX Dot3OamStatsEntry SYNTAX Dot3OamStatsEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry in the table, containing statistics information on "An entry in the table containing statistics information on
the Ethernet OAM function for a single Ethernet like the Ethernet OAM function for a single Ethernet-like
interface. Entries are automatically created for every entry interface. Entries are automatically created for every entry
in the dot3OamTable. Counters are maintained across in the dot3OamTable. Counters are maintained across
transitions in dot3OamOperStatus. transitions in dot3OamOperStatus.
" "
INDEX { ifIndex } INDEX { ifIndex }
::= { dot3OamStatsTable 1 } ::= { dot3OamStatsTable 1 }
Dot3OamStatsEntry ::= Dot3OamStatsEntry ::=
SEQUENCE { SEQUENCE {
dot3OamInformationTx Counter32, dot3OamInformationTx Counter32,
skipping to change at page 26, line 9 skipping to change at page 24, line 50
REFERENCE "[802.3ah], 30.3.6.1.21." REFERENCE "[802.3ah], 30.3.6.1.21."
::= { dot3OamStatsEntry 2 } ::= { dot3OamStatsEntry 2 }
dot3OamUniqueEventNotificationTx OBJECT-TYPE dot3OamUniqueEventNotificationTx OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
UNITS "frames" UNITS "frames"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A count of the number of unique Event OAMPDUs transmitted on "A count of the number of unique Event OAMPDUs transmitted on
this interface. Event notifications may be sent in duplicate this interface. Event Notifications may be sent in duplicate
to increase the probability of successfully being received, to increase the probability of successfully being received,
given the possibility that a frame may be lost in transit. given the possibility that a frame may be lost in transit.
Duplicate Event Notification transmissions are counted by Duplicate Event Notification transmissions are counted by
dot3OamDuplicateEventNotificationTx. dot3OamDuplicateEventNotificationTx.
A unique Event Notification OAMPDU is indicated as an Event A unique Event Notification OAMPDU is indicated as an Event
Notification OAMPDU with a Sequence Number field that is Notification OAMPDU with a Sequence Number field that is
distinct from the previously transmitted Event Notification distinct from the previously transmitted Event Notification
OAMPDU Sequence Number. OAMPDU Sequence Number.
skipping to change at page 26, line 34 skipping to change at page 25, line 27
REFERENCE "[802.3ah], 30.3.6.1.22." REFERENCE "[802.3ah], 30.3.6.1.22."
::= { dot3OamStatsEntry 3 } ::= { dot3OamStatsEntry 3 }
dot3OamUniqueEventNotificationRx OBJECT-TYPE dot3OamUniqueEventNotificationRx OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
UNITS "frames" UNITS "frames"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A count of the number of unique Event OAMPDUs received on "A count of the number of unique Event OAMPDUs received on
this interface. Event notification OAMPDUs may be sent in this interface. Event Notification OAMPDUs may be sent in
duplicate to increase the probability of successfully being duplicate to increase the probability of successfully being
received, given the possibility that a frame may be lost in received, given the possibility that a frame may be lost in
transit. Duplicate Event Notification receptions are counted transit. Duplicate Event Notification receptions are counted
by dot3OamDuplicateEventNotificationRx. by dot3OamDuplicateEventNotificationRx.
A unique Event Notification OAMPDU is indicated as an Event A unique Event Notification OAMPDU is indicated as an Event
Notification OAMPDU with a Sequence Number field that is Notification OAMPDU with a Sequence Number field that is
distinct from the previously received Event Notification distinct from the previously received Event Notification
OAMPDU Sequence Number. OAMPDU Sequence Number.
skipping to change at page 27, line 4 skipping to change at page 25, line 44
Notification OAMPDU with a Sequence Number field that is Notification OAMPDU with a Sequence Number field that is
distinct from the previously received Event Notification distinct from the previously received Event Notification
OAMPDU Sequence Number. OAMPDU Sequence Number.
Discontinuities of this counter can occur at re-initialization Discontinuities of this counter can occur at re-initialization
of the management system, and at other times as indicated by of the management system, and at other times as indicated by
the value of the ifCounterDiscontinuityTime. the value of the ifCounterDiscontinuityTime.
" "
REFERENCE "[802.3ah], 30.3.6.1.24." REFERENCE "[802.3ah], 30.3.6.1.24."
::= { dot3OamStatsEntry 4 } ::= { dot3OamStatsEntry 4 }
dot3OamDuplicateEventNotificationTx OBJECT-TYPE dot3OamDuplicateEventNotificationTx OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
UNITS "frames" UNITS "frames"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A count of the number of duplicate Event OAMPDUs transmitted "A count of the number of duplicate Event OAMPDUs transmitted
on this interface. Event notification OAMPDUs may be sent in on this interface. Event Notification OAMPDUs may be sent in
duplicate to increase the probability of successfully being duplicate to increase the probability of successfully being
received, given the possibility that a frame may be lost in received, given the possibility that a frame may be lost in
transit. transit.
A duplicate Event Notification OAMPDU is indicated as an Event A duplicate Event Notification OAMPDU is indicated as an Event
Notification OAMPDU with a Sequence Number field that is Notification OAMPDU with a Sequence Number field that is
identical to the previously transmitted Event Notification identical to the previously transmitted Event Notification
OAMPDU Sequence Number. OAMPDU Sequence Number.
Discontinuities of this counter can occur at re-initialization Discontinuities of this counter can occur at re-initialization
skipping to change at page 27, line 35 skipping to change at page 26, line 28
REFERENCE "[802.3ah], 30.3.6.1.23." REFERENCE "[802.3ah], 30.3.6.1.23."
::= { dot3OamStatsEntry 5 } ::= { dot3OamStatsEntry 5 }
dot3OamDuplicateEventNotificationRx OBJECT-TYPE dot3OamDuplicateEventNotificationRx OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
UNITS "frames" UNITS "frames"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A count of the number of duplicate Event OAMPDUs received on "A count of the number of duplicate Event OAMPDUs received on
this interface. Event notification OAMPDUs may be sent in this interface. Event Notification OAMPDUs may be sent in
duplicate to increase the probability of successfully being duplicate to increase the probability of successfully being
received, given the possibility that a frame may be lost in received, given the possibility that a frame may be lost in
transit. transit.
A duplicate Event Notification OAMPDU is indicated as an Event A duplicate Event Notification OAMPDU is indicated as an Event
Notification OAMPDU with a Sequence Number field that is Notification OAMPDU with a Sequence Number field that is
identical to the previously received Event Notification OAMPDU identical to the previously received Event Notification OAMPDU
Sequence Number. Sequence Number.
Discontinuities of this counter can occur at re-initialization Discontinuities of this counter can occur at re-initialization
skipping to change at page 34, line 10 skipping to change at page 32, line 40
"The two objects dot3OamErrSymPeriodWindowHi and "The two objects dot3OamErrSymPeriodWindowHi and
dot3OamErrSymPeriodLo together form an unsigned 64-bit dot3OamErrSymPeriodLo together form an unsigned 64-bit
integer representing the number of symbols over which this integer representing the number of symbols over which this
threshold event is defined. This is defined as threshold event is defined. This is defined as
dot3OamErrSymPeriodWindow = ((2^32)*dot3OamErrSymPeriodWindowHi) dot3OamErrSymPeriodWindow = ((2^32)*dot3OamErrSymPeriodWindowHi)
+ dot3OamErrSymPeriodWindowLo + dot3OamErrSymPeriodWindowLo
If dot3OamErrSymPeriodThreshold symbol errors occur within a If dot3OamErrSymPeriodThreshold symbol errors occur within a
window of dot3OamErrSymPeriodWindow symbols, an Event window of dot3OamErrSymPeriodWindow symbols, an Event
Notification OAMPDU should be generated with an Errored Symbol Notification OAMPDU should be generated with an Errored Symbol
Period Event TLV indicating the threshold has been crossed in Period Event TLV indicating that the threshold has been
this window. crossed in this window.
The default value for dot3OamErrSymPeriodWindow is the number The default value for dot3OamErrSymPeriodWindow is the number
of symbols in one second for the underlying physical layer. of symbols in one second for the underlying physical layer.
" "
REFERENCE "[802.3ah], 30.3.6.1.34" REFERENCE "[802.3ah], 30.3.6.1.34"
::= { dot3OamEventConfigEntry 1 } ::= { dot3OamEventConfigEntry 1 }
dot3OamErrSymPeriodWindowLo OBJECT-TYPE dot3OamErrSymPeriodWindowLo OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
UNITS "symbols" UNITS "symbols"
skipping to change at page 34, line 36 skipping to change at page 33, line 18
dot3OamErrSymPeriodWindowLo together form an unsigned 64-bit dot3OamErrSymPeriodWindowLo together form an unsigned 64-bit
integer representing the number of symbols over which this integer representing the number of symbols over which this
threshold event is defined. This is defined as threshold event is defined. This is defined as
dot3OamErrSymPeriodWindow = ((2^32)*dot3OamErrSymPeriodWindowHi) dot3OamErrSymPeriodWindow = ((2^32)*dot3OamErrSymPeriodWindowHi)
+ dot3OamErrSymPeriodWindowLo + dot3OamErrSymPeriodWindowLo
If dot3OamErrSymPeriodThreshold symbol errors occur within a If dot3OamErrSymPeriodThreshold symbol errors occur within a
window of dot3OamErrSymPeriodWindow symbols, an Event window of dot3OamErrSymPeriodWindow symbols, an Event
Notification OAMPDU should be generated with an Errored Symbol Notification OAMPDU should be generated with an Errored Symbol
Period Event TLV indicating the threshold has been crossed in Period Event TLV indicating that the threshold has been
this window. crossed in this window.
The default value for dot3OamErrSymPeriodWindow is the number The default value for dot3OamErrSymPeriodWindow is the number
of symbols in one second for the underlying physical layer. of symbols in one second for the underlying physical layer.
" "
REFERENCE "[802.3ah], 30.3.6.1.34" REFERENCE "[802.3ah], 30.3.6.1.34"
::= { dot3OamEventConfigEntry 2 } ::= { dot3OamEventConfigEntry 2 }
dot3OamErrSymPeriodThresholdHi OBJECT-TYPE dot3OamErrSymPeriodThresholdHi OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
UNITS "2^32 symbols" UNITS "2^32 symbols"
skipping to change at page 35, line 19 skipping to change at page 33, line 47
This is defined as This is defined as
dot3OamErrSymPeriodThreshold = dot3OamErrSymPeriodThreshold =
((2^32) * dot3OamErrSymPeriodThresholdHi) ((2^32) * dot3OamErrSymPeriodThresholdHi)
+ dot3OamErrSymPeriodThresholdLo + dot3OamErrSymPeriodThresholdLo
If dot3OamErrSymPeriodThreshold symbol errors occur within a If dot3OamErrSymPeriodThreshold symbol errors occur within a
window of dot3OamErrSymPeriodWindow symbols, an Event window of dot3OamErrSymPeriodWindow symbols, an Event
Notification OAMPDU should be generated with an Errored Symbol Notification OAMPDU should be generated with an Errored Symbol
Period Event TLV indicating the threshold has been crossed in Period Event TLV indicating that the threshold has been
this window. crossed in this window.
The default value for dot3OamErrSymPeriodThreshold is one The default value for dot3OamErrSymPeriodThreshold is one
symbol errors. If the threshold value is zero, then an Event symbol errors. If the threshold value is zero, then an Event
Notification OAMPDU is sent periodically (at the end of every Notification OAMPDU is sent periodically (at the end of every
window). This can be used as an asynchronous notification to window). This can be used as an asynchronous notification to
the peer OAM entity of the statistics related to this the peer OAM entity of the statistics related to this
threshold crossing alarm. threshold crossing alarm.
" "
REFERENCE "[802.3ah], 30.3.6.1.34" REFERENCE "[802.3ah], 30.3.6.1.34"
::= { dot3OamEventConfigEntry 3 } ::= { dot3OamEventConfigEntry 3 }
skipping to change at page 36, line 5 skipping to change at page 34, line 32
This is defined as This is defined as
dot3OamErrSymPeriodThreshold = dot3OamErrSymPeriodThreshold =
((2^32) * dot3OamErrSymPeriodThresholdHi) ((2^32) * dot3OamErrSymPeriodThresholdHi)
+ dot3OamErrSymPeriodThresholdLo + dot3OamErrSymPeriodThresholdLo
If dot3OamErrSymPeriodThreshold symbol errors occur within a If dot3OamErrSymPeriodThreshold symbol errors occur within a
window of dot3OamErrSymPeriodWindow symbols, an Event window of dot3OamErrSymPeriodWindow symbols, an Event
Notification OAMPDU should be generated with an Errored Symbol Notification OAMPDU should be generated with an Errored Symbol
Period Event TLV indicating the threshold has been crossed in Period Event TLV indicating that the threshold has been
this window. crossed in this window.
The default value for dot3OamErrSymPeriodThreshold is one The default value for dot3OamErrSymPeriodThreshold is one
symbol error. If the threshold value is zero, then an Event symbol error. If the threshold value is zero, then an Event
Notification OAMPDU is sent periodically (at the end of every Notification OAMPDU is sent periodically (at the end of every
window). This can be used as an asynchronous notification to window). This can be used as an asynchronous notification to
the peer OAM entity of the statistics related to this the peer OAM entity of the statistics related to this
threshold crossing alarm. threshold crossing alarm.
" "
REFERENCE "[802.3ah], 30.3.6.1.34" REFERENCE "[802.3ah], 30.3.6.1.34"
::= { dot3OamEventConfigEntry 4 } ::= { dot3OamEventConfigEntry 4 }
dot3OamErrSymPeriodEvNotifEnable OBJECT-TYPE dot3OamErrSymPeriodEvNotifEnable OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"If true, the OAM entity should send an Event Notification "If true, the OAM entity should send an Event Notification
OAMPDU when an Errored Symbol Period Event occurs. OAMPDU when an Errored Symbol Period Event occurs.
By default, this object should have the value true for By default, this object should have the value true for
Ethernet like interfaces that support OAM. If the OAM layer Ethernet-like interfaces that support OAM. If the OAM layer
does not support event notifications (as indicated via the does not support Event Notifications (as indicated via the
dot3OamFunctionsSupported attribute), this value is ignored. dot3OamFunctionsSupported attribute), this value is ignored.
" "
::= { dot3OamEventConfigEntry 5 } ::= { dot3OamEventConfigEntry 5 }
dot3OamErrFramePeriodWindow OBJECT-TYPE dot3OamErrFramePeriodWindow OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
UNITS "frames" UNITS "frames"
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of frames over which the threshold is defined. "The number of frames over which the threshold is defined.
The default value of the window is the number of minimum size The default value of the window is the number of minimum size
Ethernet frames that can be received over the physical layer Ethernet frames that can be received over the physical layer
in one second. in one second.
If dot3OamErrFramePeriodThreshold frame errors occur within a If dot3OamErrFramePeriodThreshold frame errors occur within a
window of dot3OamErrFramePeriodWindow frames, an Event window of dot3OamErrFramePeriodWindow frames, an Event
Notification OAMPDU should be generated with an Errored Frame Notification OAMPDU should be generated with an Errored Frame
Period Event TLV indicating the threshold has been crossed in Period Event TLV indicating that the threshold has been
this window. crossed in this window.
" "
REFERENCE "[802.3ah], 30.3.6.1.38" REFERENCE "[802.3ah], 30.3.6.1.38"
::= { dot3OamEventConfigEntry 6 } ::= { dot3OamEventConfigEntry 6 }
dot3OamErrFramePeriodThreshold OBJECT-TYPE dot3OamErrFramePeriodThreshold OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
UNITS "frames" UNITS "frames"
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of frame errors that must occur for this event to "The number of frame errors that must occur for this event to
be triggered. The default value is one frame error. If the be triggered. The default value is one frame error. If the
threshold value is zero, then an Event Notification OAMPDU is threshold value is zero, then an Event Notification OAMPDU is
sent periodically (at the end of every window). This can be sent periodically (at the end of every window). This can be
used as an asynchronous notification to the peer OAM entity of used as an asynchronous notification to the peer OAM entity of
the statistics related to this threshold crossing alarm. the statistics related to this threshold crossing alarm.
If dot3OamErrFramePeriodThreshold frame errors occur within a If dot3OamErrFramePeriodThreshold frame errors occur within a
window of dot3OamErrFramePeriodWindow frames, an Event window of dot3OamErrFramePeriodWindow frames, an Event
Notification OAMPDU should be generated with an Errored Frame Notification OAMPDU should be generated with an Errored Frame
Period Event TLV indicating the threshold has been crossed in Period Event TLV indicating that the threshold has been
this window. crossed in this window.
" "
REFERENCE "[802.3ah], 30.3.6.1.38" REFERENCE "[802.3ah], 30.3.6.1.38"
::= { dot3OamEventConfigEntry 7 } ::= { dot3OamEventConfigEntry 7 }
dot3OamErrFramePeriodEvNotifEnable OBJECT-TYPE dot3OamErrFramePeriodEvNotifEnable OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"If true, the OAM entity should send an Event Notification "If true, the OAM entity should send an Event Notification
OAMPDU when an Errored Frame Period Event occurs. OAMPDU when an Errored Frame Period Event occurs.
By default, this object should have the value true for By default, this object should have the value true for
Ethernet like interfaces that support OAM. If the OAM layer Ethernet-like interfaces that support OAM. If the OAM layer
does not support event notifications (as indicated via the does not support Event Notifications (as indicated via the
dot3OamFunctionsSupported attribute), this value is ignored. dot3OamFunctionsSupported attribute), this value is ignored.
" "
::= { dot3OamEventConfigEntry 8 } ::= { dot3OamEventConfigEntry 8 }
dot3OamErrFrameWindow OBJECT-TYPE dot3OamErrFrameWindow OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
UNITS "tenths of a second" UNITS "tenths of a second"
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The amount of time (in 100ms increments) over which the "The amount of time (in 100ms increments) over which the
threshold is defined. The default value is 10 (1 second). threshold is defined. The default value is 10 (1 second).
If dot3OamErrFrameThreshold frame errors occur within a window If dot3OamErrFrameThreshold frame errors occur within a window
of dot3OamErrFrameWindow seconds (measured in tenths of of dot3OamErrFrameWindow seconds (measured in tenths of
seconds), an Event Notification OAMPDU should be generated seconds), an Event Notification OAMPDU should be generated
with an Errored Frame Event TLV indicating the threshold has with an Errored Frame Event TLV indicating that the threshold
been crossed in this window. has been crossed in this window.
" "
REFERENCE "[802.3ah], 30.3.6.1.36" REFERENCE "[802.3ah], 30.3.6.1.36"
DEFVAL { 10 } DEFVAL { 10 }
::= { dot3OamEventConfigEntry 9 } ::= { dot3OamEventConfigEntry 9 }
dot3OamErrFrameThreshold OBJECT-TYPE dot3OamErrFrameThreshold OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
UNITS "frames" UNITS "frames"
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
skipping to change at page 38, line 47 skipping to change at page 37, line 24
dot3OamErrFrameEvNotifEnable OBJECT-TYPE dot3OamErrFrameEvNotifEnable OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"If true, the OAM entity should send an Event Notification "If true, the OAM entity should send an Event Notification
OAMPDU when an Errored Frame Event occurs. OAMPDU when an Errored Frame Event occurs.
By default, this object should have the value true for By default, this object should have the value true for
Ethernet like interfaces that support OAM. If the OAM layer Ethernet-like interfaces that support OAM. If the OAM layer
does not support event notifications (as indicated via the does not support Event Notifications (as indicated via the
dot3OamFunctionsSupported attribute), this value is ignored. dot3OamFunctionsSupported attribute), this value is ignored.
" "
DEFVAL { true } DEFVAL { true }
::= { dot3OamEventConfigEntry 11 } ::= { dot3OamEventConfigEntry 11 }
dot3OamErrFrameSecsSummaryWindow OBJECT-TYPE dot3OamErrFrameSecsSummaryWindow OBJECT-TYPE
SYNTAX Integer32 (100..9000) SYNTAX Integer32 (100..9000)
UNITS "tenths of a second" UNITS "tenths of a second"
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
skipping to change at page 39, line 21 skipping to change at page 37, line 43
UNITS "tenths of a second" UNITS "tenths of a second"
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The amount of time (in 100ms intervals) over which the "The amount of time (in 100ms intervals) over which the
threshold is defined. The default value is 100 (10 seconds). threshold is defined. The default value is 100 (10 seconds).
If dot3OamErrFrameSecsSummaryThreshold frame errors occur If dot3OamErrFrameSecsSummaryThreshold frame errors occur
within a window of dot3OamErrFrameSecsSummaryWindow (in tenths within a window of dot3OamErrFrameSecsSummaryWindow (in tenths
of seconds), an Event Notification OAMPDU should be generated of seconds), an Event Notification OAMPDU should be generated
with an Errored Frame Seconds Summary Event TLV indicating the with an Errored Frame Seconds Summary Event TLV indicating
threshold has been crossed in this window. that the threshold has been crossed in this window.
" "
REFERENCE "[802.3ah], 30.3.6.1.40" REFERENCE "[802.3ah], 30.3.6.1.40"
DEFVAL { 100 } DEFVAL { 100 }
::= { dot3OamEventConfigEntry 12 } ::= { dot3OamEventConfigEntry 12 }
dot3OamErrFrameSecsSummaryThreshold OBJECT-TYPE dot3OamErrFrameSecsSummaryThreshold OBJECT-TYPE
SYNTAX Integer32 (1..900) SYNTAX Integer32 (1..900)
UNITS "errored frame seconds" UNITS "errored frame seconds"
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
skipping to change at page 39, line 45 skipping to change at page 38, line 19
event to be triggered. The default value is one errored frame event to be triggered. The default value is one errored frame
second. If the threshold value is zero, then an Event second. If the threshold value is zero, then an Event
Notification OAMPDU is sent periodically (at the end of every Notification OAMPDU is sent periodically (at the end of every
window). This can be used as an asynchronous notification to window). This can be used as an asynchronous notification to
the peer OAM entity of the statistics related to this the peer OAM entity of the statistics related to this
threshold crossing alarm. threshold crossing alarm.
If dot3OamErrFrameSecsSummaryThreshold frame errors occur If dot3OamErrFrameSecsSummaryThreshold frame errors occur
within a window of dot3OamErrFrameSecsSummaryWindow (in tenths within a window of dot3OamErrFrameSecsSummaryWindow (in tenths
of seconds), an Event Notification OAMPDU should be generated of seconds), an Event Notification OAMPDU should be generated
with an Errored Frame Seconds Summary Event TLV indicating the with an Errored Frame Seconds Summary Event TLV indicating
threshold has been crossed in this window. that the threshold has been crossed in this window.
" "
REFERENCE "[802.3ah], 30.3.6.1.40" REFERENCE "[802.3ah], 30.3.6.1.40"
DEFVAL { 1 } DEFVAL { 1 }
::= { dot3OamEventConfigEntry 13 } ::= { dot3OamEventConfigEntry 13 }
dot3OamErrFrameSecsEvNotifEnable OBJECT-TYPE dot3OamErrFrameSecsEvNotifEnable OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"If true, the local OAM entity should send an Event "If true, the local OAM entity should send an Event
Notification OAMPDU when an Errored Frame Seconds Event Notification OAMPDU when an Errored Frame Seconds Event
occurs. occurs.
By default, this object should have the value true for By default, this object should have the value true for
skipping to change at page 40, line 14 skipping to change at page 38, line 36
dot3OamErrFrameSecsEvNotifEnable OBJECT-TYPE dot3OamErrFrameSecsEvNotifEnable OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"If true, the local OAM entity should send an Event "If true, the local OAM entity should send an Event
Notification OAMPDU when an Errored Frame Seconds Event Notification OAMPDU when an Errored Frame Seconds Event
occurs. occurs.
By default, this object should have the value true for By default, this object should have the value true for
Ethernet like interfaces that support OAM. If the OAM layer Ethernet-like interfaces that support OAM. If the OAM layer
does not support event notifications (as indicated via the does not support Event Notifications (as indicated via the
dot3OamFunctionsSupported attribute), this value is ignored. dot3OamFunctionsSupported attribute), this value is ignored.
" "
DEFVAL { true } DEFVAL { true }
::= { dot3OamEventConfigEntry 14 } ::= { dot3OamEventConfigEntry 14 }
dot3OamDyingGaspEnable OBJECT-TYPE dot3OamDyingGaspEnable OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"If true, the local OAM entity should attempt to indicate a "If true, the local OAM entity should attempt to indicate a
dying gasp via the OAMPDU flags field to its peer OAM entity dying gasp via the OAMPDU flags field to its peer OAM entity
when a dying gasp event occurs. The exact definition of a when a dying gasp event occurs. The exact definition of a
dying gasp event is implementation dependent. If the system dying gasp event is implementation dependent. If the system
does not support dying gasp capability, setting this object does not support dying gasp capability, setting this object
has no effect, and reading the object should always result in has no effect, and reading the object should always result in
'false'. 'false'.
By default, this object should have the value true for By default, this object should have the value true for
Ethernet like interfaces that support OAM. If the OAM layer Ethernet-like interfaces that support OAM. If the OAM layer
does not support event notifications (as indicated via the does not support Event Notifications (as indicated via the
dot3OamFunctionsSupported attribute), this value is ignored. dot3OamFunctionsSupported attribute), this value is ignored.
" "
DEFVAL { true } DEFVAL { true }
::= { dot3OamEventConfigEntry 15 } ::= { dot3OamEventConfigEntry 15 }
dot3OamCriticalEventEnable OBJECT-TYPE dot3OamCriticalEventEnable OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"If true, the local OAM entity should attempt to indicate a "If true, the local OAM entity should attempt to indicate a
critical event via the OAMPDU flags to its peer OAM entity critical event via the OAMPDU flags to its peer OAM entity
when a critical event occurs. The exact definition of a when a critical event occurs. The exact definition of a
critical event is implementation dependent. If the system critical event is implementation dependent. If the system
does not support critical event capability, setting this does not support critical event capability, setting this
object has no effect, and reading the object should always object has no effect, and reading the object should always
result in 'false'. result in 'false'.
By default, this object should have the value true for By default, this object should have the value true for
Ethernet like interfaces that support OAM. If the OAM layer Ethernet-like interfaces that support OAM. If the OAM layer
does not support event notifications (as indicated via the does not support Event Notifications (as indicated via the
dot3OamFunctionsSupported attribute), this value is ignored. dot3OamFunctionsSupported attribute), this value is ignored.
" "
DEFVAL { true } DEFVAL { true }
::= { dot3OamEventConfigEntry 16 } ::= { dot3OamEventConfigEntry 16 }
-- ************************************************************** -- **************************************************************
-- --
-- Ethernet OAM Event Log group -- Ethernet OAM Event Log group
-- --
skipping to change at page 42, line 4 skipping to change at page 40, line 22
crossing events, and are returned as all F's (2^32 - 1) for crossing events, and are returned as all F's (2^32 - 1) for
non-threshold crossing events. non-threshold crossing events.
Entries in the table are automatically created when such Entries in the table are automatically created when such
events are detected. The size of the table is implementation events are detected. The size of the table is implementation
dependent. When the table reaches its maximum size, older dependent. When the table reaches its maximum size, older
entries are automatically deleted to make room for newer entries are automatically deleted to make room for newer
entries. entries.
" "
::= { dot3OamObjects 6 } ::= { dot3OamObjects 6 }
dot3OamEventLogEntry OBJECT-TYPE dot3OamEventLogEntry OBJECT-TYPE
SYNTAX Dot3OamEventLogEntry SYNTAX Dot3OamEventLogEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry in the dot3OamEventLogTable. Entries are "An entry in the dot3OamEventLogTable. Entries are
automatically created whenever Ethernet OAM events occur at automatically created whenever Ethernet OAM events occur at
the local OAM entity, and when Event Notification OAMPDUs are the local OAM entity, and when Event Notification OAMPDUs are
received at the local OAM entity (indicating events have received at the local OAM entity (indicating that events have
occurred at the peer OAM entity). The size of the table is occurred at the peer OAM entity). The size of the table is
implementation dependent, but when the table becomes full, implementation dependent, but when the table becomes full,
older events are automatically deleted to make room for newer older events are automatically deleted to make room for newer
events. The table index dot3OamEventLogIndex increments for events. The table index dot3OamEventLogIndex increments for
each new entry, and when the maximum value is reached the each new entry, and when the maximum value is reached, the
value restarts at zero. value restarts at zero.
" "
INDEX { ifIndex, dot3OamEventLogIndex } INDEX { ifIndex, dot3OamEventLogIndex }
::= { dot3OamEventLogTable 1 } ::= { dot3OamEventLogTable 1 }
Dot3OamEventLogEntry ::= Dot3OamEventLogEntry ::=
SEQUENCE { SEQUENCE {
dot3OamEventLogIndex Unsigned32, dot3OamEventLogIndex Unsigned32,
dot3OamEventLogTimestamp TimeStamp, dot3OamEventLogTimestamp TimeStamp,
dot3OamEventLogOui EightOTwoOui, dot3OamEventLogOui EightOTwoOui,
skipping to change at page 43, line 11 skipping to change at page 41, line 28
dot3OamEventLogTimestamp OBJECT-TYPE dot3OamEventLogTimestamp OBJECT-TYPE
SYNTAX TimeStamp SYNTAX TimeStamp
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The value of sysUpTime at the time of the logged event. For "The value of sysUpTime at the time of the logged event. For
locally generated events, the time of the event can be locally generated events, the time of the event can be
accurately retrieved from sysUpTime. For remotely generated accurately retrieved from sysUpTime. For remotely generated
events, the time of the event is indicated by the reception of events, the time of the event is indicated by the reception of
the Event Notification OAMPDU indicating the event occurred on the Event Notification OAMPDU indicating that the event
the peer. A system may attempt to adjust the timestamp value occurred on the peer. A system may attempt to adjust the
to more accurately reflect the time of the event at the peer timestamp value to more accurately reflect the time of the
OAM entity by using other information, such as that found in event at the peer OAM entity by using other information, such
the timestamp found of the Event Notification TLVs, which as that found in the timestamp found of the Event Notification
provides an indication of the relative time between events at TLVs, which provides an indication of the relative time
the peer entity. " between events at the peer entity. "
::= { dot3OamEventLogEntry 2 } ::= { dot3OamEventLogEntry 2 }
dot3OamEventLogOui OBJECT-TYPE dot3OamEventLogOui OBJECT-TYPE
SYNTAX EightOTwoOui SYNTAX EightOTwoOui
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The OUI of the entity defining the object type. All IEEE "The OUI of the entity defining the object type. All IEEE
802.3 defined events (as appearing in [802.3ah] except for the 802.3 defined events (as appearing in [802.3ah] except for the
Organizationally Unique Event TLVs) use the IEEE 802.3 OUI of Organizationally Unique Event TLVs) use the IEEE 802.3 OUI of
0x0180C2. Organizations defining their own Event Notification 0x0180C2. Organizations defining their own Event Notification
TLVs include their OUI in the Event Notification TLV which TLVs include their OUI in the Event Notification TLV that
gets reflected here. " gets reflected here. "
::= { dot3OamEventLogEntry 3 } ::= { dot3OamEventLogEntry 3 }
dot3OamEventLogType OBJECT-TYPE dot3OamEventLogType OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The type of event that generated this entry in the event log. "The type of event that generated this entry in the event log.
When the OUI is the IEEE 802.3 OUI of 0x0180C2, the following When the OUI is the IEEE 802.3 OUI of 0x0180C2, the following
event types are defined: event types are defined:
erroredSymbolEvent(1), erroredSymbolEvent(1),
erroredFramePeriodEvent (2), erroredFramePeriodEvent (2),
erroredFrameEvent(3), erroredFrameEvent(3),
erroredFrameSecondsEvent(4), erroredFrameSecondsEvent(4),
linkFault(256), linkFault(256),
dyingGaspEvent(257), dyingGaspEvent(257),
criticalLinkEvent(258) criticalLinkEvent(258)
The first four are considered threshold crossing events as The first four are considered threshold crossing events, as
they are generated when a metric exceeds a given value within they are generated when a metric exceeds a given value within
a specified window. The other three are not threshold a specified window. The other three are not threshold
crossing events. crossing events.
When the OUI is not 71874 (0x0180C2 in hex), then some other When the OUI is not 71874 (0x0180C2 in hex), then some other
organization has defined the event space. If event subtyping organization has defined the event space. If event subtyping
is known to the implementation, it may be reflected here. is known to the implementation, it may be reflected here.
Otherwise, this value should return all F's (2^32 - 1). Otherwise, this value should return all F's (2^32 - 1).
" "
REFERENCE "[802.3ah], 30.3.6.1.10 and 57.5.3." REFERENCE "[802.3ah], 30.3.6.1.10 and 57.5.3."
skipping to change at page 44, line 31 skipping to change at page 42, line 46
received from the OAM peer via Ethernet OAM (remote(2)). received from the OAM peer via Ethernet OAM (remote(2)).
" "
::= { dot3OamEventLogEntry 5 } ::= { dot3OamEventLogEntry 5 }
dot3OamEventLogWindowHi OBJECT-TYPE dot3OamEventLogWindowHi OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"If the event represents a threshold crossing event, the two "If the event represents a threshold crossing event, the two
objects dot3OamEventWindowHi and dot3OamEventWindowLo form an objects dot3OamEventWindowHi and dot3OamEventWindowLo, form
unsigned 64-bit integer yielding the window over which the an unsigned 64-bit integer yielding the window over which the
value was measured for the threshold crossing event (for value was measured for the threshold crossing event (for
example, 5, when 11 occurrences happened in 5 seconds while example, 5, when 11 occurrences happened in 5 seconds while
the threshold was 10). The two objects are combined as: the threshold was 10). The two objects are combined as:
dot3OamEventLogWindow = ((2^32) * dot3OamEventLogWindowHi) dot3OamEventLogWindow = ((2^32) * dot3OamEventLogWindowHi)
+ dot3OamEventLogWindowLo + dot3OamEventLogWindowLo
Otherwise, this value is returned as all F's (2^32 - 1) and Otherwise, this value is returned as all F's (2^32 - 1) and
adds no useful information. adds no useful information.
" "
skipping to change at page 48, line 13 skipping to change at page 46, line 21
dot3OamEventLogRunningTotal, dot3OamEventLogRunningTotal,
dot3OamEventLogEventTotal dot3OamEventLogEventTotal
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A dot3OamThresholdEvent notification is sent when a local or "A dot3OamThresholdEvent notification is sent when a local or
remote threshold crossing event is detected. A local remote threshold crossing event is detected. A local
threshold crossing event is detected by the local entity, threshold crossing event is detected by the local entity,
while a remote threshold crossing event is detected by the while a remote threshold crossing event is detected by the
reception of an Ethernet OAM Event Notification OAMPDU reception of an Ethernet OAM Event Notification OAMPDU
indicating a threshold event. that indicates a threshold event.
This notification should not be sent more than once per This notification should not be sent more than once per
second. second.
The OAM entity can be derived from extracting the ifIndex from The OAM entity can be derived from extracting the ifIndex from
the variable bindings. The objects in the notification the variable bindings. The objects in the notification
correspond to the values in a row instance of in the correspond to the values in a row instance in the
dot3OamEventLogTable. dot3OamEventLogTable.
The management entity should periodically check The management entity should periodically check
dot3OamEventLogTable to detect any missed events." dot3OamEventLogTable to detect any missed events."
::= { dot3OamNotifications 1 } ::= { dot3OamNotifications 1 }
dot3OamNonThresholdEvent NOTIFICATION-TYPE dot3OamNonThresholdEvent NOTIFICATION-TYPE
OBJECTS { dot3OamEventLogTimestamp, OBJECTS { dot3OamEventLogTimestamp,
dot3OamEventLogOui, dot3OamEventLogOui,
dot3OamEventLogType, dot3OamEventLogType,
dot3OamEventLogLocation, dot3OamEventLogLocation,
dot3OamEventLogEventTotal dot3OamEventLogEventTotal
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A dot3OamNonThresholdEvent notification is sent when a local "A dot3OamNonThresholdEvent notification is sent when a local
or remote non-threshold crossing event is detected. A local or remote non-threshold crossing event is detected. A local
event is detected by the local entity, while a remote event is event is detected by the local entity, while a remote event is
detected by the reception of an Ethernet OAM Event detected by the reception of an Ethernet OAM Event
Notification OAMPDU indicating a non-threshold crossing event. Notification OAMPDU that indicates a non-threshold crossing
event.
This notification should not be sent more than once per This notification should not be sent more than once per
second. second.
The OAM entity can be derived from extracting the ifIndex from The OAM entity can be derived from extracting the ifIndex from
the variable bindings. The objects in the notification the variable bindings. The objects in the notification
correspond to the values in a row instance of the correspond to the values in a row instance of the
dot3OamEventLogTable. dot3OamEventLogTable.
The management entity should periodically check The management entity should periodically check
skipping to change at page 49, line 22 skipping to change at page 47, line 28
-- --
dot3OamGroups OBJECT IDENTIFIER ::= { dot3OamConformance 1 } dot3OamGroups OBJECT IDENTIFIER ::= { dot3OamConformance 1 }
dot3OamCompliances OBJECT IDENTIFIER ::= { dot3OamConformance 2 } dot3OamCompliances OBJECT IDENTIFIER ::= { dot3OamConformance 2 }
-- Compliance statements -- Compliance statements
dot3OamCompliance MODULE-COMPLIANCE dot3OamCompliance MODULE-COMPLIANCE
STATUS current STATUS current
DESCRIPTION "The compliance statement for managed entities DESCRIPTION "The compliance statement for managed entities
supporting OAM on Ethernet like interfaces. supporting OAM on Ethernet-like interfaces.
" "
MODULE -- this module MODULE -- this module
MANDATORY-GROUPS { dot3OamControlGroup, MANDATORY-GROUPS { dot3OamControlGroup,
dot3OamPeerGroup, dot3OamPeerGroup,
dot3OamStatsBaseGroup dot3OamStatsBaseGroup
} }
GROUP dot3OamLoopbackGroup GROUP dot3OamLoopbackGroup
DESCRIPTION DESCRIPTION
"This group is mandatory for all IEEE 802.3 OA "This group is mandatory for all IEEE 802.3 OA
skipping to change at page 51, line 37 skipping to change at page 49, line 39
dot3OamVariableResponseRx, dot3OamVariableResponseRx,
dot3OamOrgSpecificTx, dot3OamOrgSpecificTx,
dot3OamOrgSpecificRx, dot3OamOrgSpecificRx,
dot3OamUnsupportedCodesTx, dot3OamUnsupportedCodesTx,
dot3OamUnsupportedCodesRx, dot3OamUnsupportedCodesRx,
dot3OamFramesLostDueToOam dot3OamFramesLostDueToOam
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of objects providing the statistics for the "A collection of objects providing the statistics for the
number of various transmit and recieve events for OAM on an number of various transmit and receive events for OAM on an
Ethernet like interface. Note that all of these counters must Ethernet-like interface. Note that all of these counters must
be supported even if the related function (as described in be supported even if the related function (as described in
dot3OamFunctionsSupported) is not supported. " dot3OamFunctionsSupported) is not supported. "
::= { dot3OamGroups 3 } ::= { dot3OamGroups 3 }
dot3OamLoopbackGroup OBJECT-GROUP dot3OamLoopbackGroup OBJECT-GROUP
OBJECTS { dot3OamLoopbackStatus, OBJECTS { dot3OamLoopbackStatus,
dot3OamLoopbackIgnoreRx dot3OamLoopbackIgnoreRx
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
skipping to change at page 54, line 4 skipping to change at page 51, line 50
dot3OamEventLogValue, dot3OamEventLogValue,
dot3OamEventLogRunningTotal, dot3OamEventLogRunningTotal,
dot3OamEventLogEventTotal dot3OamEventLogEventTotal
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of objects for configuring the thresholds for an "A collection of objects for configuring the thresholds for an
Errored Frame Seconds Summary Event and maintaining the event Errored Frame Seconds Summary Event and maintaining the event
information. " information. "
::= { dot3OamGroups 10 } ::= { dot3OamGroups 10 }
dot3OamNotificationGroup NOTIFICATION-GROUP dot3OamNotificationGroup NOTIFICATION-GROUP
NOTIFICATIONS { NOTIFICATIONS {
dot3OamThresholdEvent, dot3OamThresholdEvent,
dot3OamNonThresholdEvent dot3OamNonThresholdEvent
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of notifications used by Ethernet OAM to signal "A collection of notifications used by Ethernet OAM to signal
to a management entity that local or remote events have occured to a management entity that local or remote events have
on a specified Ethernet link. " occurred on a specified Ethernet link. "
::= { dot3OamGroups 11 } ::= { dot3OamGroups 11 }
END END
7. Security Considerations 7. Security Considerations
The readable objects in this module can provide information about The readable objects in this module can provide information about
network traffic, and therefore may be considered sensitive. In network traffic, and therefore may be considered sensitive. In
particular, OAM provides mechanisms for reading the IEEE 802.3 Clause particular, OAM provides mechanisms for reading the IEEE 802.3 Clause
30 MIB attributes from a link partner via a specialized layer two 30 MIB attributes from a link partner via a specialized layer two
protocol. Unlike SNMP, IEEE P802.3ah OAM does not include encryption protocol. Unlike SNMP, IEEE P802.3ah OAM does not include encryption
or authentication mechanisms. It should be used in environments or authentication mechanisms. It should be used in environments
where either this interface information is not considered sensitive, where either this interface information is not considered sensitive,
or where the facility terminations are protected. By default, OAM is or where the facility terminations are protected. By default, OAM is
disabled on Ethernet like interfaces and is therefore not a risk. disabled on Ethernet-like interfaces and is therefore not a risk.
IEEE 802.3ah OAM is designed to support deployment in access and IEEE 802.3ah OAM is designed to support deployment in access and
enterprise networks. In access networks, one end of a link is the enterprise networks. In access networks, one end of a link is the
CO-side, and the other is the CPE-side, and the facilities are often CO-side, and the other is the CPE-side, and the facilities are often
protected in wiring cages or closets. In such deployments, it is protected in wiring cages or closets. In such deployments, it is
often the case that the CO-side is protected from access from the CPE often the case that the CO-side is protected from access from the
side. Within IEEE P802.3ah OAM, this protection from remote access CPE-side. Within IEEE P802.3ah OAM, this protection from remote
is accomplished by configuring the CPE-side in passive mode using the access is accomplished by configuring the CPE-side in passive mode
dot3OamMode attribute. This prevents the CPE from accessing using the dot3OamMode attribute. This prevents the CPE from
functions and information at the CO-side of the connection. In accessing functions and information at the CO-side of the connection.
enterprise networks, read-only interface information is often In enterprise networks, read-only interface information is often
considered non-sensitive. considered non-sensitive.
The frequency of OAM PDUs on an Ethernet interface does not adversely The frequency of OAM PDUs 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 have limited effects with read-write or read-create MAX-ACCESS, they have limited effects
on user data. on user data.
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. Therefore an layer protocols such as bridging, IP, and SNMP. Therefore an
skipping to change at page 55, line 34 skipping to change at page 53, line 29
objects control whether events are sent, and at what thresholds. objects control whether events are sent, and at what thresholds.
Note that the frequency of event communication is limited by the Note that the frequency of event communication is limited by the
frequency limits of Slow Protocols on Ethernet interfaces. Also, the frequency limits of Slow Protocols on Ethernet interfaces. Also, the
information available via OAM events is also available via OA information available via OAM events is also available via OA
Variable Requests. Access to this information via either OAM events Variable Requests. Access to this information via either OAM events
or Variable Requests is controlled by the dot3OamAdminState and or Variable Requests is controlled by the dot3OamAdminState and
dot3OamMode objects. As mentioned previously, inadequate protection dot3OamMode objects. As mentioned previously, inadequate protection
of these variables can result in access to link information and of these variables can result in access to link information and
functions. functions.
SNMP versions prior to SNMPv3 did not include adequate security. Even SNMP versions prior to SNMPv3 did not include adequate security.
if the network itself is secure (for example by using IPSec), even Even if the network itself is secure (for example by using IPsec),
then, there is no control as to who on the secure network is allowed even then, there is no control as to who on the secure network is
to access and GET/SET (read/change/create/delete) the objects in this allowed to access and GET/SET (read/change/create/delete) the objects
MIB module. in this MIB module.
It is RECOMMENDED that implementers consider the security features as It is RECOMMENDED that implementers consider the security features as
provided by the SNMPv3 framework (see [RFC3410], section 8), provided by the SNMPv3 framework (see [RFC3410], section 8),
including full support for the SNMPv3 cryptographic mechanisms (for including full support for the SNMPv3 cryptographic mechanisms (for
authentication and privacy). authentication and privacy).
Further, deployment of SNMP versions prior to SNMPv3 is NOT Further, deployment of SNMP versions prior to SNMPv3 is NOT
RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to
enable cryptographic security. It is then a customer/operator enable cryptographic security. It is then a customer/operator
responsibility to ensure that the SNMP entity giving access to an responsibility to ensure that the SNMP entity giving access to an
instance of this MIB module is properly configured to give access to instance of this MIB module is properly configured to give access to
the objects only to those principals (users) that have legitimate the objects only to those principals (users) that have legitimate
rights to indeed GET or SET (change/create/delete) them rights to indeed GET or SET (change/create/delete) them.
8. IANA Considerations 8. IANA Considerations
The Ethernet OAM MIB requires the allocation of a single object The Ethernet OAM MIB requires the allocation of a single object
identifier for its MODULE-IDENTITY under the MIB-2 tree. identifier for its MODULE-IDENTITY under the MIB-2 tree.
The MIB module in this document uses the following IANA-assigned The MIB module in this document uses the following IANA-assigned
OBJECT IDENTIFIER values recorded in the SMI Numbers registry: OBJECT IDENTIFIER values recorded in the SMI Numbers registry:
Descriptor OBJECT IDENTIFIER Descriptor OBJECT IDENTIFIER
---------- ----------------- ---------- -----------------
dot3OamMIB { mib-2 XXX } dot3OamMIB { mib-2 158 }
Editor's Note (to be removed prior to publication): the IANA is
requested to assign a value for "XXX" under the 'mib-2' subtree and
to record the assignment in the SMI Numbers registry. When the
assignment has been made, the RFC Editor is asked to replace "XXX"
(here and in the MIB module) with the assigned value and to remove
this note.
9. References 9. References
9.1 Normative References 9.1. Normative References
[802.3ah] Institute of Electrical and Electronic Engineers, IEEE [802.3ah] Institute of Electrical and Electronic Engineers,
Std 802.3ah-2004, "Part 3: Carrier Sense Multiple Access IEEE Std 802.3ah-2004, "Part 3: Carrier Sense
with Collision Detection (CSMA/CD) Access Method and Multiple Access with Collision Detection (CSMA/CD)
Physical Layer Specifications - Amendment: Media Access Access Method and Physical Layer Specifications -
Control Parameters, Physical Layers and Management Amendment: Media Access Control Parameters,
Parameters for Subscriber Access Networks", October 2004. Physical Layers and Management Parameters for
Subscriber Access Networks", October 2004.
[802.3-2002] Institute of Electrical and Electronic Engineers, IEEE [802.3-2002] Institute of Electrical and Electronic Engineers,
Std 802.3-2003, "IEEE Standard for Carrier Sense Multiple IEEE Std 802.3-2003, "IEEE Standard for Carrier
Access with Collision Detection (CSMA/CD) Access Method Sense Multiple Access with Collision Detection
and Physical Layer Specifications - Draft amendment to - (CSMA/CD) Access Method and Physical Layer
Information technology - Telecommunications and Specifications - Draft amendment to - Information
information exchange between systems - Local and technology - Telecommunications and information
metropolitan area networks - Specific requirements - Part exchange between systems - Local and metropolitan
3: Carrier sense multiple access with collision detection area networks - Specific requirements - Part 3:
(CSMA/CD) access method and physical layer specifications Carrier sense multiple access with collision
- Media Access Control Parameters, Physical Layers and detection (CSMA/CD) access method and physical
Management Parameters", March 2002. layer specifications - Media Access Control
Parameters, Physical Layers and Management
Parameters", March 2002.
[802.3-2005] Institute of Electrical and Electronic Engineers, IEEE [802.3-2005] Institute of Electrical and Electronic Engineers,
Std 802.3-2005, "IEEE Standard for Carrier Sense Multiple IEEE Std 802.3-2005, "IEEE Standard for Carrier
Access with Collision Detection (CSMA/CD) Access Method Sense Multiple Access with Collision Detection
and Physical Layer Specifications - Draft amendment to - (CSMA/CD) Access Method and Physical Layer
Information technology - Telecommunications and Specifications - Draft amendment to - Information
information exchange between systems - Local and technology - Telecommunications and information
metropolitan area networks - Specific requirements - Part exchange between systems - Local and metropolitan
3: Carrier sense multiple access with collision detection area networks - Specific requirements - Part 3:
(CSMA/CD) access method and physical layer specifications Carrier sense multiple access with collision
- Media Access Control Parameters, Physical Layers and detection (CSMA/CD) access method and physical
Management Parameters", December 2005. layer specifications - Media Access Control
Parameters, Physical Layers and Management
Parameters", December 2005.
[802-2001] Institute of Electrical and Electronic Engineers, IEEE [802-2001] Institute of Electrical and Electronic Engineers,
Std 802-2001, "Standard for Local and Metropolitan Area IEEE Std 802-2001, "Standard for Local and
Networks: Architecture and Overview", March 2002. Metropolitan Area Networks: Architecture and
Overview", March 2002.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
[RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Requirement Levels", BCP 14, RFC 2119, March 1997.
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., [RFC2578] McCloghrie, K., Perkins, D., and J. Schoenwaelder,
McCloghrie, K., Rose, M. and S. Waldbusser, "Textual "Structure of Management Information Version 2
Conventions for SMIv2", STD 58, RFC 2579, April 1999. (SMIv2)", STD 58, RFC 2578, April 1999.
[RFC2580] McCloghrie, K., Perkins, D. and J. Schoenwaelder, [RFC2579] McCloghrie, K., Perkins, D., and J. Schoenwaelder,
"Conformance Statements for SMIv2", STD 58, RFC 2580, "Textual Conventions for SMIv2", STD 58, RFC 2579,
April 1999. April 1999.
[RFC2856] Bierman, A., McCloghrie, K., Presuhn, R., "Textual [RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder,
Conventions for Additional High Capacity Data Types", RFC "Conformance Statements for SMIv2", STD 58, RFC
2856, June 2000. 2580, April 1999.
[RFC2863] McCloghrie, K., Kastenholz, F., "The Interfaces Group [RFC2856] Bierman, A., McCloghrie, K., and R. Presuhn,
MIB", RFC 2863, June 2000. "Textual Conventions for Additional High Capacity
Data Types", RFC 2856, June 2000.
9.2 Informative References [RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces
Group MIB", RFC 2863, June 2000.
9.2. Informative References
[802.3ah-copper] Beili, Ed, "Ethernet in the First Mile Copper [802.3ah-copper] Beili, Ed, "Ethernet in the First Mile Copper
(EFMCu) Interfaces MIB", draft-ietf-hubmib-efm-cu-05.txt, (EFMCu) Interfaces MIB", Work in Progress, February
March 2006. 2007.
[802.3ah-epon] Khermosh, Lior, "Managed Object of EPON", draft-ietf [802.3ah-epon] Khermosh, L., "Managed Objects of Ethernet Passive
hubmib-efm-epon-mib-04.txt, February 2006. Optical Networks (EPON)", RFC 4837, June 2007.
[RFC3410] Case, J., Mundy, R., Partain, D., Stewart, B., [RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart,
"Introduction and Applicability Statements for Internet "Introduction and Applicability Statements for
Standard Management Framework", RFC 3410, December 2003. Internet-Standard Management Framework", RFC 3410,
December 2002.
[RFC3635] Flick, J., "Definitions of Managed Objects for the [RFC3635] Flick, J., "Definitions of Managed Objects for the
Ethernet like Interface Types", RFC 3635, September 2003. Ethernet-like Interface Types", RFC 3635, September
2003.
10. Acknowledgments 10. Acknowledgments
The author is grateful to all of the participants in the IEEE 802.3ah The author is grateful to all of the participants in the IEEE 802.3ah
EFM (Ethernet in the First Mile) taskforce. In particular, the EFM (Ethernet in the First Mile) taskforce. In particular, the
strong leadership and dedication of the following individuals is strong leadership and dedication of the following individuals is
noted: noted:
Kevin Daines (Editor, IEEE 802.3ah OAM clauses) Kevin Daines (Editor, IEEE 802.3ah OAM clauses)
Ben Brown (Editor, IEEE 802.3ah Logic clauses) Ben Brown (Editor, IEEE 802.3ah Logic clauses)
skipping to change at page 58, line 44 skipping to change at page 57, line 5
Al Braga Al Braga
Floyd Gerhardt Floyd Gerhardt
Bob Grow Bob Grow
Eric Lynskey Eric Lynskey
David Martin David Martin
John Messenger John Messenger
Dan Romascanu (Ex-Chair, IETF HUBMIB WG) Dan Romascanu (Ex-Chair, IETF HUBMIB WG)
Jonathan Thatcher Jonathan Thatcher
Geoff Thompson Geoff Thompson
11. Author's Address Author's Address
Note: Author's email address is spelled out to help protect against
email address harvesting programs.
Matt Squire Matt Squire
Hatteras Networks Hatteras Networks
529 Davis Drive 529 Davis Drive
Durham, NC 27713 Durham, NC 27713
Email: msquire at hatterasnetworks dot com EMail: msquire@hatterasnetworks.com
12. Intellectual Property Statement Full Copyright Statement
Copyright (C) The IETF Trust (2007).
This document is subject to the rights, licenses and restrictions
contained in BCP 78, and except as set forth therein, the authors
retain all their rights.
This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND
THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS
OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF
THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Intellectual Property
The IETF takes no position regarding the validity or scope of any The IETF takes no position regarding the validity or scope of any
Intellectual Property Rights or other rights that might be claimed to Intellectual Property Rights or other rights that might be claimed to
pertain to the implementation or use of the technology described in pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights this document or the extent to which any license under such rights
might or might not be available; nor does it represent that it has might or might not be available; nor does it represent that it has
made any independent effort to identify any such rights. Information made any independent effort to identify any such rights. Information
on the procedures with respect to rights in RFC documents can be on the procedures with respect to rights in RFC documents can be
found in BCP 78 and BCP 79. found in BCP 78 and BCP 79.
skipping to change at page 59, line 33 skipping to change at page 58, line 45
such proprietary rights by implementers or users of this such proprietary rights by implementers or users of this
specification can be obtained from the IETF on-line IPR repository at specification can be obtained from the IETF on-line IPR repository at
http://www.ietf.org/ipr. http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary copyrights, patents or patent applications, or other proprietary
rights that may cover technology that may be required to implement rights that may cover technology that may be required to implement
this standard. Please address the information to the IETF at this standard. Please address the information to the IETF at
ietf-ipr@ietf.org. ietf-ipr@ietf.org.
The IETF has been notified of intellectual property rights claimed in
regard to some or all of the specification contained in this
document. For more information consult the online list of claimed
rights.
13. Copyright Statement
Copyright (C) The IETF Trust (2007).
This document is subject to the rights, licenses and restrictions
contained in BCP 78, and except as set forth therein, the authors
retain all their rights.
This document and the information contained herein are provided
on an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE
REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE
IETF TRUST AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL
WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY
WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY
RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A
PARTICULAR PURPOSE.
Acknowledgement Acknowledgement
Funding for the RFC Editor function is currently provided by the Funding for the RFC Editor function is currently provided by the
Internet Society. Internet Society.
 End of changes. 137 change blocks. 
341 lines changed or deleted 316 lines changed or added

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