One document matched: draft-squire-hubmib-efm-mib-00.txt
Network Working Group
Internet Draft
Document: draft-squire-hubmib-efm-mib-00.txt
Matt Squire
Hatteras Networks
October 2003 Expires Apr 2004
Ethernet in the First Mile (EFM) Common MIB
Status of this Memo
This document is an Internet-Draft and is in full conformance with
all provisions of Section 10 of RFC2026 [1].
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 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
http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html.
Abstract
This memo defines a portion of the Management Information Base (MIB)
for use with network management protocols in the Internet community.
This document proposes an extension to the Ethernet-like Interfaces
MIB for the capability to manage Ethernet-in-the-First-Mile (EFM)
devices.
1 Introduction
New capabilities have been added to Ethernet like interfaces within
the PIEEE802.3ah project for Ethernet in the First Mile (EFM). This
memo defines a portion of the Management Information Base (MIB) for
use with network management protocols in the Internet community to
manage the new capabilities of EFM Ethernet interfaces.
1.1 Specification of Requirements
[Page 1]
draft-squire-hubmib-efm-mib-00.txt October 2003
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.
2 The Internet-Standard Management Framework
For a detailed overview of the documents that describe the current
Internet-Standard Management Framework, please refer to section 7 of
RFC 3410 [RFC3410].
Managed objects are accessed via a virtual information store, termed
the Management Information Base or MIB. MIB objects are generally
accessed through the Simple Network Management Protocol (SNMP).
Objects in the MIB are defined using the mechanisms defined in the
Structure of Management Information (SMI). This memo specifies a
MIB 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 [RFC2580].
3 Overview
Ethernet networks have evolved over time from an enterprise backbone
to a variety of other applications. The IEEE P802.3ah task force
has defined extensions to the Ethernet standard for Ethernet
deployments in the access space.
The Ethernet-in-the-First-Mile (EFM) task force has focused its
efforts into four categories: optics, copper, Ethernet passive
optical networks (Ethernet PON, or EPON), and operations,
administration, and maintenance (OAM).
Generally, one can categorize the changes developed by IEEE P802.3ah
as extending Ethernet with new physical layers (e.g. new optical
physical layers, new copper physical layers, EPON), or as adding new
common functionality applicable to many Ethernet physical layers
(e.g. OAM).
This memo focuses on the management extensions to the MIB for
Ethernet-like interfaces to address the new common Ethernet
functionality developed in IEEE P802.3ah. Other documents will
focus on detailed MIB extensions for new physical layers where
applicable.
4 MIB Structure
The common EFM MIB objects of this memo focus on the OAM
capabilities introduced in IEEE P802.3ah. The MIB objects are
partitioned into four (4) different MIB groups.
The dot3OamTable group manages the primary OAM objects of the
Ethernet interface. This group controls the state and status of OAM
as well as the mode in which it operates.
[Page 2]
draft-squire-hubmib-efm-mib-00.txt October 2003
The dot3OamStats table maintains statistics on the number and type
of Ethernet OAM frames being transmitted and received on the
Ethernet interface.
The dot3OamPeer table maintains the current information on the
status and configuration of the peer OAM entity on the Ethernet
interface. Managed information includes the capabilities and
function available on the peer OAM entity.
The dot3OamEvent table defines the management objects for the event
notification capability available in IEEE P802.3ah OAM. With IEEE
P802.3ah OAM, one device may send notifications to its peer devices
whenever an important event happens on the local device.
5 Definitions
EFM-COMMON-MIB DEFINITIONS ::= BEGIN
IMPORTS
MODULE-IDENTITY, mib-2, OBJECT-TYPE, Counter32,
Integer32, Unsigned32
FROM SNMPv2-SMI
RowStatus, TruthValue, MacAddress
FROM SNMPv2-TC
ifIndex
FROM IF-MIB
MODULE-COMPLIANCE, OBJECT-GROUP
FROM SNMPv2-CONF;
efmCommonMIB MODULE-IDENTITY
LAST-UPDATED "200310130000Z" -- October 13, 2003
ORGANIZATION "IETF Ethernet Interfaces and Hub MIB
Working Group"
CONTACT-INFO
"
WG Charter:
http://www.ietf.org/html.charters/hubmib-charter.html
Mailing lists:
General Discussion: hubmib@ietf.org
To Subscribe: hubmib-requests@ietf.org
In Body: subscribe your_email_address
Chair: Dan Romascanu
Avaya
Tel: +972-3-645-8414
Email: dromasca@avaya.com
Editor: Matt Squire
Hatteras Networks
Tel: +1-919-991-5460
Fax: +1-919-991-0743
E-mail: msquire@hatterasnetworks.com
"
[Page 3]
draft-squire-hubmib-efm-mib-00.txt October 2003
DESCRIPTION
"The MIB module for managing the new common Ethernet
features introduced by the Ethernet in the First
Mile task force (IEEE P802.3ah). The functionality
presented here is based on IEEE P802.3ah/D2.1,
released in October 2003.
In particular, this MIB focused on the changes to
Clause 30 of the draft that are not specific to any
physical layer.
The following reference is used throughout this MIB
module:
[802.3ah] refers to:
IEEE P802.3ah/D2.1
Copyright (c) The Internet Society (2003). This
version of this MIB module is part of RFC XXXX;
See the RFC itself for full legal notices. "
REVISION "200310130000Z" -- October 13, 2003
DESCRIPTION "Initial version, published as RFC XXXX."
::= { mib-2 XXX }
-- EditorsNote: Its unclear where in the existing MIB hierarchy
-- we wish to hang these new capabilities. For now, putting this
-- as separate from dot3, though I question if thatĘs the right
-- thing to do. If this is common Ethernet function, it should
-- probably go into the dot3 MIB.
--
dot3OamMIB OBJECT IDENTIFIER ::= { efmCommonMIB 1}
--
-- Ethernet OAM Control group
--
dot3OamTable OBJECT-TYPE
SYNTAX SEQUENCE OF Dot3OamEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION "Primary controls and status for the OAM
capabilities of an Ethernet like interface.
There will be one row in this table for each
Ethernet like interface in the system that
Supports the Ethernet OAM functions defined
IEEE 802.3ah."
::= { dot3OamMIB 1 }
dot3OamEntry OBJECT-TYPE
[Page 4]
draft-squire-hubmib-efm-mib-00.txt October 2003
SYNTAX Dot3OamEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION "An entry in the table, containing
information on the Ethernet OAM function for
a single Ethernet-like interface."
INDEX { ifIndex }
::= { dot3OamTable 1 }
Dot3OamEntry ::=
SEQUENCE {
dot3OamRowStatus RowStatus,
dot3OamAdminState INTEGER,
dot3OamMode INTEGER,
dot3OamOperStatus INTEGER,
dot3OamUnidirectionalSupport TruthValue,
dot3OamLoopbackSupport TruthValue,
dot3OamEventSupport TruthValue,
dot3OamVariableSupport TruthValue,
dot3OamMaxOamPduSize Unsigned32,
dot3OamConfigRevision Unsigned32,
dot3OamMultiplexorState INTEGER,
dot3OamParserState INTEGER
-- dot3OamErrSymPeriodWindowConfig Unsigned32,
-- dot3OamErrSymPeriodThresholdConfig Unsigned32,
-- dot3OamErrFrameWindowConfig Unsigned32,
-- dot3OamErrFrameThresholdConfig Unsigned32,
-- dot3OamErrFramePeriodWindowConfig Unsigned32,
-- dot3OamErrFramePeriodThresholdConfig Unsigned32,
-- dot3OamErrFrameSecsSummaryWindowConfig Unsigned32,
-- dot3OamErrFrameSecsSummaryThresholdConfig Unsigned32
}
dot3OamRowStatus OBJECT-TYPE
SYNTAX RowStatus
MAX-ACCESS read-create
STATUS current
DESCRIPTION "Implementation and activation of OAM is
optional, therefore creation of the row is
non-automatic.
"
REFERENCE "[802.3ah], 57.1.2 point d.1"
::= { dot3OamEntry 1}
dot3OamAdminState OBJECT-TYPE
SYNTAX INTEGER {
disabled(1),
enabled(2)
}
MAX-ACCESS read-write
STATUS current
DESCRIPTION "This object is used to configure the default
administrative OAM mode for this interface.
[Page 5]
draft-squire-hubmib-efm-mib-00.txt October 2003
This object represents the administratively
configured OAM state for this interface."
REFERENCE "[802.3ah], 30.11.1.1.2"
::= { dot3OamEntry 2 }
dot3OamMode OBJECT-TYPE
SYNTAX INTEGER {
active(1),
passive(2)
}
MAX-ACCESS read-write
STATUS current
DESCRIPTION "This object configures the mode of OAM
operation for this Ethernet like interface.
OAM on Ethernet interfaces may be in
active(1) mode or passive(2) mode. These two
modes differ in that active mode provides
additional capabilities to initiate
monitoring activities with the remote OAM
peer entity, while passive mode generally
waits for the peer to initiate OAM actions
with it."
REFERENCE "[802.3ah], 30.11.1.1.3"
::= { dot3OamEntry 3 }
dot3OamOperStatus OBJECT-TYPE
SYNTAX INTEGER {
passiveWait(1),
activeSendLocal(2),
sendLocalAndRemote1(3),
sendLocalAndRemote2(4),
oamPeeringLocallyRejected(5),
oamPeeringRemotelyRejected(6),
operational(7)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION "At initialization and failure conditions,
OAM entities on the same Ethernet link begin
a
discovery phase to determine what OAM
capabilities maybe used on that link. The
progress of the initialization is controlled
by the OAM layer. These progress is
reflected by the attributes .....
NEED TO ADD THINGS TO CLAUSE 30
"
REFERENCE "[802.3ah], REFERENCE TBD"
::= { dot3OamEntry 4 }
-- EditorsNote: Need to expose above in C30, not there
--
dot3OamUnidirectionalSupport OBJECT-TYPE
[Page 6]
draft-squire-hubmib-efm-mib-00.txt October 2003
SYNTAX TruthValue
MAX-ACCESS read-write
STATUS current
DESCRIPTION "Whether the OAM entity supports
unidirectional operation."
REFERENCE "[802.3ah], REFERENCE TBD"
::= { dot3OamEntry 5 }
-- EditorsNote: Likely not configurable depending
-- on the media type
dot3OamLoopbackSupport OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS read-write
STATUS current
DESCRIPTION "Whether the OAM entity adheres to loopback
command."
REFERENCE "[802.3ah], REFERENCE TBD"
::= { dot3OamEntry 6 }
dot3OamEventSupport OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS read-write
STATUS current
DESCRIPTION "Whether the OAM entity sends and interprets
link events."
REFERENCE "[802.3ah], REFERENCE TBD"
::= { dot3OamEntry 7 }
dot3OamVariableSupport OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS read-write
STATUS current
DESCRIPTION "Whether the OAM entity responds to variable
requests."
REFERENCE "[802.3ah], REFERENCE TBD"
::= { dot3OamEntry 8 }
dot3OamMaxOamPduSize OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS read-write
STATUS current
DESCRIPTION "The largest OAMPDU that the OAM entity
supports."
REFERENCE "[802.3ah], REFERENCE TBD"
::= { dot3OamEntry 9 }
dot3OamConfigRevision OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS read-only
STATUS current
DESCRIPTION "The configuration revision of the OAM entity
as reflected in the latest OAMPDU sent by the
OAM entity.
[Page 7]
draft-squire-hubmib-efm-mib-00.txt October 2003
"
REFERENCE "[802.3ah], REFERENCE TBD"
::= { dot3OamEntry 10 }
dot3OamMultiplexorState OBJECT-TYPE
SYNTAX INTEGER {
forward(1),
discard(2)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION "The state of the multiplexor function for
the OAM entity.
"
REFERENCE "[802.3ah], REFERENCE TBD"
::= { dot3OamEntry 11 }
dot3OamParserState OBJECT-TYPE
SYNTAX INTEGER {
forward(1),
loopback(2),
discard(3)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION "The state of the multiplexor function for
the OAM entity.
"
REFERENCE "[802.3ah], REFERENCE TBD"
::= { dot3OamEntry 12 }
--
-- Ethernet OAM Statistics group
--
dot3OamStatsTable OBJECT-TYPE
SYNTAX SEQUENCE OF Dot3OamStatsEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION "Statistics for the OAM function on a
particular Ethernet like interface."
::= { dot3OamMIB 2 }
dot3OamStatsEntry OBJECT-TYPE
SYNTAX Dot3OamStatsEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION "An entry in the table, containing statistics
information on the Ethernet OAM function for
a single Ethernet-like interface."
INDEX { ifIndex }
::= { dot3OamStatsTable 1 }
[Page 8]
draft-squire-hubmib-efm-mib-00.txt October 2003
Dot3OamStatsEntry ::=
SEQUENCE {
dot3OamPduTx Counter32,
dot3OamPduRx Counter32,
dot3OamInformationTx Counter32,
dot3OamInformationRx Counter32,
dot3OamEventNotificationTx Counter32,
dot3OamUniqueEventNotificationRx Counter32,
dot3OamDuplicateEventNotificationRx Counter32,
dot3OamLoopbackControlTx Counter32,
dot3OamLoopbackControlRx Counter32,
dot3OamVariableRequestTx Counter32,
dot3OamVariableRequestRx Counter32,
dot3OamVariableResponseTx Counter32,
dot3OamVariableResponseRx Counter32,
dot3OamOrgSpecificTx Counter32,
dot3OamOrgSpecificRx Counter32,
dot3OamUnsupportedCodesRx Counter32
}
dot3OamPduTx OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION "A count of the number of Ethernet OAM frames
transmitted on this interface."
REFERENCE "[802.3ah], 30.11.1.1.14."
::= { dot3OamStatsEntry 1 }
dot3OamPduRx OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION "A count of the number of Ethernet OAM frames
received on this interface."
REFERENCE "[802.3ah], 30.11.1.1.15."
::= { dot3OamStatsEntry 2 }
dot3OamInformationTx OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION "A count of the number of Information OAMPDUs
transmitted on this interface."
REFERENCE "[802.3ah], 30.11.1.1.17."
::= { dot3OamStatsEntry 3 }
dot3OamInformationRx OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION "A count of the number of Information OAMPDUs
[Page 9]
draft-squire-hubmib-efm-mib-00.txt October 2003
received on this interface."
REFERENCE "[802.3ah], 30.11.1.1.18."
::= { dot3OamStatsEntry 4 }
dot3OamEventNotificationTx OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION "A count of the number of Event OAMPDUs
transmitted on this interface."
REFERENCE "[802.3ah], 30.11.1.1.19."
::= { dot3OamStatsEntry 5 }
dot3OamUniqueEventNotificationRx OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION "A count of the number of unique Event
OAMPDUs received on this interface."
REFERENCE "[802.3ah], 30.11.1.1.20."
::= { dot3OamStatsEntry 6 }
dot3OamDuplicateEventNotificationRx OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION "A count of the number of duplicate Event
OAMPDUs received on this interface."
REFERENCE "[802.3ah], 30.11.1.1.21."
::= { dot3OamStatsEntry 7 }
dot3OamLoopbackControlTx OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION "A count of the number of Loopback OAMPDUs
transmitted on this interface."
REFERENCE "[802.3ah], 30.11.1.1.22."
::= { dot3OamStatsEntry 8 }
dot3OamLoopbackControlRx OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION "A count of the number of Loopback OAMPDUs
received on this interface."
REFERENCE "[802.3ah], 30.11.1.1.23."
::= { dot3OamStatsEntry 9 }
dot3OamVariableRequestTx OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
[Page 10]
draft-squire-hubmib-efm-mib-00.txt October 2003
DESCRIPTION "A count of the number of Variable Request
OAMPDUs transmitted on this interface."
REFERENCE "[802.3ah], 30.11.1.1.24."
::= { dot3OamStatsEntry 10 }
dot3OamVariableRequestRx OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION "A count of the number of Variable Request
OAMPDUs received on this interface."
REFERENCE "[802.3ah], 30.11.1.1.25."
::= { dot3OamStatsEntry 11 }
dot3OamVariableResponseTx OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION "A count of the number of Variable Response
OAMPDUs transmitted on this interface."
REFERENCE "[802.3ah], 30.11.1.1.26."
::= { dot3OamStatsEntry 12 }
dot3OamVariableResponseRx OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION "A count of the number of Variable Response
OAMPDUs received on this interface."
REFERENCE "[802.3ah], 30.11.1.1.27."
::= { dot3OamStatsEntry 13 }
dot3OamOrgSpecificTx OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION "A count of the number of Organizational
Specific OAMPDUs transmitted on this
interface."
REFERENCE "[802.3ah], 30.11.1.1.28."
::= { dot3OamStatsEntry 14 }
dot3OamOrgSpecificRx OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION "A count of the number of Organizational
Specific OAMPDUs received on this interface."
REFERENCE "[802.3ah], 30.11.1.1.29."
::= { dot3OamStatsEntry 15 }
dot3OamUnsupportedCodesRx OBJECT-TYPE
SYNTAX Counter32
[Page 11]
draft-squire-hubmib-efm-mib-00.txt October 2003
MAX-ACCESS read-only
STATUS current
DESCRIPTION "A count of the number of OAMPDUs with an
unrecognized type received on this
interface."
REFERENCE "[802.3ah], 30.11.1.1.16."
::= { dot3OamStatsEntry 16 }
--
-- Ethernet OAM Peer group
--
dot3OamPeerTable OBJECT-TYPE
SYNTAX SEQUENCE OF Dot3OamPeerEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION "Information about the OAM peer for a
particular Ethernet like interface."
::= { dot3OamMIB 3 }
dot3OamPeerEntry OBJECT-TYPE
SYNTAX Dot3OamPeerEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION "An entry in the table, containing statistics
information on the Ethernet OAM function for
a single Ethernet-like interface."
INDEX { ifIndex }
::= { dot3OamPeerTable 1 }
--
-- EditorsNote - Is this defined anywhere else?
Oui ::=
OCTET STRING(SIZE(3))
Dot3OamPeerEntry ::=
SEQUENCE {
dot3OamPeerRowStatus RowStatus,
dot3OamPeerMacAddress MacAddress,
dot3OamPeerVendorOui Oui,
dot3OamPeerVendorInfo Unsigned32,
dot3OamPeerMode INTEGER,
dot3OamPeerUnidirectionalSupport TruthValue,
dot3OamPeerLoopbackSupport TruthValue,
dot3OamPeerEventSupport TruthValue,
dot3OamPeerVariableSupport TruthValue,
dot3OamPeerMaxOamPduSize Integer32,
dot3OamPeerConfigRevision Integer32,
dot3OamPeerMultiplexorState INTEGER,
dot3OamPeerParserState INTEGER
}
dot3OamPeerRowStatus OBJECT-TYPE
[Page 12]
draft-squire-hubmib-efm-mib-00.txt October 2003
SYNTAX RowStatus
MAX-ACCESS read-create
STATUS current
DESCRIPTION "The peer row is only created when the
dot3OamOperStatus of this particular Ethernet
interface is not passiveWait or
activeSendLocal."
REFERENCE "N/A"
::= { dot3OamPeerEntry 1}
dot3OamPeerMacAddress OBJECT-TYPE
SYNTAX MacAddress
MAX-ACCESS read-only
STATUS current
DESCRIPTION "The MAC address of the remote OAM peer
entity."
REFERENCE "[802.3ah], 30.11.1.1.4."
::= { dot3OamPeerEntry 2 }
dot3OamPeerVendorOui OBJECT-TYPE
SYNTAX Oui
MAX-ACCESS read-only
STATUS current
DESCRIPTION "The OUI of the OAM peer as reflected in the
latest information OAMPDU."
REFERENCE "[802.3ah], 30.11.1.1.11."
::= { dot3OamPeerEntry 3 }
dot3OamPeerVendorInfo OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS read-only
STATUS current
DESCRIPTION "The Vendor Info of the OAM peer as reflected
in the latest information OAMPDU."
REFERENCE "[802.3ah], 30.11.1.1.12, 30.11.1.1.13"
::= { dot3OamPeerEntry 4 }
dot3OamPeerMode OBJECT-TYPE
SYNTAX INTEGER {
active(1),
passive(2)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION "The mode of the OAM peer as reflected in the
latest OAMPDU.
"
REFERENCE "[802.3ah], 30.11.1.1.5."
::= { dot3OamPeerEntry 5 }
dot3OamPeerUnidirectionalSupport OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS read-only
[Page 13]
draft-squire-hubmib-efm-mib-00.txt October 2003
STATUS current
DESCRIPTION "Whether the OAM peer supports unidirectional
operation as reflected in the latest OAMPDU.
"
REFERENCE "[802.3ah], 30.11.1.1.5."
::= { dot3OamPeerEntry 6 }
dot3OamPeerLoopbackSupport OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS read-only
STATUS current
DESCRIPTION "Whether the OAM peer supports loopback
operation as reflected in the latest OAMPDU.
"
REFERENCE "[802.3ah], 30.11.1.1.5."
::= { dot3OamPeerEntry 7 }
dot3OamPeerEventSupport OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS read-only
STATUS current
DESCRIPTION "Whether the OAM peer supports event
notification operation as reflected in the
latest OAMPDU.
"
REFERENCE "[802.3ah], 30.11.1.1.5."
::= { dot3OamPeerEntry 8 }
dot3OamPeerVariableSupport OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS read-only
STATUS current
DESCRIPTION "Whether the OAM peer supports variable
request operation as reflected in the latest
OAMPDU.
"
REFERENCE "[802.3ah], 30.11.1.1.5."
::= { dot3OamPeerEntry 9 }
dot3OamPeerMaxOamPduSize OBJECT-TYPE
SYNTAX Integer32
MAX-ACCESS read-only
STATUS current
DESCRIPTION "The maximum size of OAMPDU supported by the
peer as reflected in the latest OAMPDU.
Ethernet OAM on this interface must not
use OAMPDUs that exceed this size.
"
REFERENCE "[802.3ah], 30.11.1.1.6."
::= { dot3OamPeerEntry 10 }
dot3OamPeerConfigRevision OBJECT-TYPE
SYNTAX Integer32
[Page 14]
draft-squire-hubmib-efm-mib-00.txt October 2003
MAX-ACCESS read-only
STATUS current
DESCRIPTION "The configuration revision of the OAM peer
as reflected in the latest OAMPDU. This
attribute is changed by the peer whenever it
has a local configuration change for Ethernet
OAM this interface.
"
REFERENCE "[802.3ah], 30.11.1.1.9."
::= { dot3OamPeerEntry 11 }
dot3OamPeerMultiplexorState OBJECT-TYPE
SYNTAX INTEGER {
forward(1),
discard(2)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION "The state of the multiplexor function in the
OAM peer as reflected in the latest OAMPDU.
This value is changed based on loopback
actions by either the local or remote device.
The normal value for this attribute is
forward. When the performing loopback
operations, the value goes to discard.
"
REFERENCE "[802.3ah], 30.11.1.1.10."
::= { dot3OamPeerEntry 12 }
dot3OamPeerParserState OBJECT-TYPE
SYNTAX INTEGER {
forward(1),
loopback(2),
discard(3)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION "The state of the parser function in the
OAM peer as reflected in the latest OAMPDU.
This value is changed based on loopback
actions by either the local or remote
device. The normal value for this attribute
is forward.
When the performing loopback operations, the
value goes to discard (when traffic is
looped back at the peer) or loopback (when
traffic is looped back locally).
"
REFERENCE "[802.3ah], 30.11.1.1.10."
::= { dot3OamPeerEntry 13 }
--
-- Ethernet OAM Event group
[Page 15]
draft-squire-hubmib-efm-mib-00.txt October 2003
--
-- Needs to be filled in TBD TBD !!
--
-- Ethernet OAM Compliance group
--
-- Needs to be filled in TBD TBD !!
END
6 Security Considerations
7 References
8 Acknowledgments
9 Author's Addresses
Matt Squire
Hatteras Networks
639 Davis Drive
Suite 200
Research Triangle Park, NC 27709
Email: msquire@hatterasnetworks.com
[Page 16]| PAFTECH AB 2003-2026 | 2026-04-24 02:05:27 |