950 lines
40 KiB
Plaintext
950 lines
40 KiB
Plaintext
--***************** With RAD Modifications and additions **********************
|
|
--
|
|
--
|
|
--Title: Hub MIB
|
|
--Date: March 5, 2006
|
|
--ETH-OAM (IEEE 802.3ah) MIB
|
|
--
|
|
-- last update 27-April-06 By Orly Bachar
|
|
|
|
|
|
|
|
DOT3-OAM-R-MIB DEFINITIONS ::= BEGIN
|
|
|
|
IMPORTS
|
|
MODULE-IDENTITY, OBJECT-TYPE,
|
|
Counter32, Unsigned32 FROM SNMPv2-SMI
|
|
TEXTUAL-CONVENTION, MacAddress FROM SNMPv2-TC
|
|
-- CounterBasedGauge64 FROM HCNUM-TC
|
|
ifIndex FROM IF-MIB;
|
|
-- MODULE-COMPLIANCE, OBJECT-GROUP,
|
|
-- NOTIFICATION-GROUP FROM SNMPv2-CONF;
|
|
|
|
|
|
dot3OamMIBR MODULE-IDENTITY
|
|
LAST-UPDATED "200603050000Z" -- March 5,2006"
|
|
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 at avaya dot com
|
|
Editor: Matt Squire
|
|
Hatteras Networks
|
|
Tel: +1-919-991-5460
|
|
Fax: +1-919-991-0743
|
|
E-mail: msquire at hatterasnetworks dot com
|
|
"
|
|
DESCRIPTION
|
|
"The MIB module for managing the new Ethernet OAM features
|
|
introduced by the Ethernet in the First Mile task force (IEEE
|
|
802.3ah). The functionality presented here is based on IEEE
|
|
802.3ah [802.3ah], released in October, 2004. [802.3ah] was
|
|
prepared as an addendum to the standing version of IEEE 802.3
|
|
[802.3-2002] at the time. Since then, [802.3ah] has been
|
|
merged into the base IEEE 802.3 specification in [802.3-2005].
|
|
|
|
In particular, this MIB focuses on the new OAM functions
|
|
introduced in Clause 57 of [802.3ah]. The OAM functionality
|
|
of Clause 57 is controlled by new management attributes
|
|
introduced in Clause 30 of [802.3ah]. The OAM functions are
|
|
not specific to any particular Ethernet physical layer, and
|
|
can be generically applied to any Ethernet interface of
|
|
[802.3-2002].
|
|
|
|
An Ethernet OAM protocol data unit is a valid Ethernet frame
|
|
with a destination MAC address equal to the reserved MAC
|
|
address for Slow Protocols (See 43B of [802.3ah]), a
|
|
lengthOrType field equal to the reserved type for Slow
|
|
Protocols, and a Slow Protocols subtype equal to that of the
|
|
subtype reserved for Ethernet OAM. OAMPDU is used throughout
|
|
this document as an abbreviation for Ethernet OAM protocol
|
|
data unit.
|
|
|
|
The following reference is used throughout this MIB module:
|
|
|
|
[802.3ah] refers to:
|
|
IEEE Std 802.3ah-2004: 'Draft amendment to -
|
|
Information technology - Telecommunications and
|
|
information exchange between systems - Local and
|
|
metropolitan are networks - Specific requirements - Part
|
|
3: Carrier sense multiple access with collision detection
|
|
(CSMA/CD) access method and physical layer specifications
|
|
- Media Access Control Parameters, Physical Layers and
|
|
Management Parameters for subscriber access networks',
|
|
October 2004.
|
|
|
|
[802.3-2002] refers to:
|
|
IEEE Std 802.3-2002:
|
|
'Information technology - Telecommunications and
|
|
information exchange between systems - Local and
|
|
metropolitan are networks - Specific requirements - Part
|
|
3: Carrier sense multiple access with collision detection
|
|
(CSMA/CD) access method and physical layer specifications
|
|
- Media Access Control Parameters, Physical Layers and
|
|
Management Parameters for subscriber access networks',
|
|
March 2002.
|
|
|
|
[802.3-2005] refers to:
|
|
IEEE Std 802.3-2002:
|
|
'Information technology - Telecommunications and
|
|
information exchange between systems - Local and
|
|
metropolitan are networks - Specific requirements - Part
|
|
3: Carrier sense multiple access with collision detection
|
|
(CSMA/CD) access method and physical layer specifications
|
|
- Media Access Control Parameters, Physical Layers and
|
|
Management Parameters for subscriber access networks',
|
|
December 2005.
|
|
|
|
[802-2001] refers to:
|
|
'IEEE Standard for LAN/MAN (Local Area
|
|
Network/Metropolitan Area Network): Overview and
|
|
Architecture', IEEE 802, June 2001.
|
|
|
|
Copyright (c) The Internet Society (2006). This version of
|
|
this MIB module is part of RFC XXXX; See the RFC itself for
|
|
full legal notices. "
|
|
REVISION "200603050000Z" -- March 5, 2006"
|
|
DESCRIPTION
|
|
"This is a draft adopted under RAD MIB until an RFC will be published."
|
|
::= { radExperimental 7 }
|
|
|
|
|
|
radExperimental OBJECT IDENTIFIER ::= { iso (1) org (3) dod (6) internet (1) private (4) enterprises (1) rad (164) 20}
|
|
|
|
--
|
|
-- Sections of the Ethernet OAM MIB
|
|
|
|
--
|
|
-- Textual conventions for OAM MIB
|
|
--
|
|
Dot3Oui ::= TEXTUAL-CONVENTION
|
|
STATUS current
|
|
DESCRIPTION
|
|
"24-bit Organizationally Unique Identifier. Information on
|
|
OUIs can be found in IEEE 802-2001 [802-2001] Clause 9."
|
|
SYNTAX OCTET STRING(SIZE(3))
|
|
|
|
|
|
|
|
|
|
dot3OamObjectsR OBJECT IDENTIFIER ::= { dot3OamMIBR 1 }
|
|
|
|
-- ***************************************************************
|
|
--
|
|
-- Ethernet OAM Control group
|
|
--
|
|
|
|
|
|
dot3OamTableR OBJECT-TYPE
|
|
SYNTAX SEQUENCE OF Dot3OamEntryR
|
|
MAX-ACCESS not-accessible
|
|
STATUS current
|
|
DESCRIPTION
|
|
"This table contains the 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 OAM functions defined in [802.3ah].
|
|
"
|
|
::= { dot3OamObjectsR 1 }
|
|
|
|
dot3OamEntryR OBJECT-TYPE
|
|
SYNTAX Dot3OamEntryR
|
|
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. Entries in
|
|
the table are created automatically for each interface
|
|
supporting Ethernet OAM. The status of the row entry can be
|
|
determined from dot3OamOperStatusR.
|
|
|
|
A dot3OamEntryR is indexed in the dot3OamTableR by the ifIndex
|
|
object of the Interfaces MIB.
|
|
"
|
|
INDEX { ifIndex }
|
|
::= { dot3OamTableR 1 }
|
|
|
|
Dot3OamEntryR ::=
|
|
SEQUENCE {
|
|
dot3OamAdminStateR INTEGER,
|
|
dot3OamOperStatusR INTEGER,
|
|
dot3OamModeR INTEGER,
|
|
dot3OamMaxOamPduSizeR Unsigned32,
|
|
dot3OamConfigRevisionR Unsigned32,
|
|
dot3OamFunctionsSupportedR BITS
|
|
}
|
|
|
|
dot3OamAdminStateR OBJECT-TYPE
|
|
SYNTAX INTEGER {
|
|
disabled(1),
|
|
enabled(2)
|
|
}
|
|
MAX-ACCESS read-write
|
|
STATUS current
|
|
DESCRIPTION
|
|
"This object is used to provision the default administrative
|
|
OAM mode for this interface. This object represents the
|
|
desired state of OAM for this interface.
|
|
|
|
The dot3OamAdminStateR always starts in the disabled(1) state
|
|
until an explicit management action or configuration
|
|
information retained by the system causes a transition to the
|
|
enabled(2) state. When enabled(2), Ethernet OAM will attempt
|
|
to operate over this interface.
|
|
"
|
|
REFERENCE "[802.3ah], 30.3.6.1.2"
|
|
::= { dot3OamEntryR 1 }
|
|
|
|
dot3OamOperStatusR OBJECT-TYPE
|
|
SYNTAX INTEGER {
|
|
disabled(1),
|
|
linkFault(2),
|
|
passiveWait(3),
|
|
activeSendLocal(4),
|
|
sendLocalAndRemote(5),
|
|
sendLocalAndRemoteOk(6),
|
|
oamPeeringLocallyRejected(7),
|
|
oamPeeringRemotelyRejected(8),
|
|
operational(9),
|
|
nonOperHalfDuplex(10)
|
|
}
|
|
MAX-ACCESS read-only
|
|
STATUS current
|
|
DESCRIPTION
|
|
"At initialization and failure conditions, two OAM entities on
|
|
the same full-duplex Ethernet link begin a discovery phase to
|
|
determine what OAM capabilities may be used on that link. The
|
|
progress of this initialization is controlled by the OAM
|
|
sublayer.
|
|
|
|
This value is always disabled(1) if OAM is disabled on this
|
|
interface via the dot3OamAdminStateR.
|
|
|
|
If the link has detected a fault and is transmitting OAM PDUs
|
|
with a link fault indication, the value is linkFault(2). Also,
|
|
if the interface is not operational (ifOperStatus is not
|
|
up(1)), linkFault(2) is returned. Note that the object
|
|
ifOperStatus may not be up(1) as a result of link failure or
|
|
administrative action (ifAdminState being down(2) or
|
|
testing(3)).
|
|
|
|
The passiveWait(3) state is returned only by OAM entities in
|
|
passive mode (dot3OamMode) and reflects the state in which the
|
|
OAM entity is waiting to see if the peer device is OAM
|
|
capable. The activeSendLocal(4) value is used by active mode
|
|
devices (dot3OamMode) and reflects the OAM entity actively
|
|
trying to discover whether the peer has OAM capability but has
|
|
not yet made that determination.
|
|
|
|
The state sendLocalAndRemote(5) reflects that the local OAM
|
|
entity has discovered the peer but has not yet accepted or
|
|
rejected the configuration of the peer. The local device can,
|
|
for whatever reason, decide that the peer device is
|
|
unacceptable and decline OAM peering. If the local OAM entity
|
|
rejects the peer OAM entity, the state becomes
|
|
oamPeeringLocallyRejected(7). If the OAM peering is allowed
|
|
by the local device, the state moves to
|
|
sendLocalAndRemoteOk(6). Note that both the
|
|
sendLocalAndRemote(5) and oamPeeringLocallyRejected(7) states
|
|
fall within the state SEND_LOCAL_REMOTE of the Discovery state
|
|
diagram [802.3ah, Figure 57-5], with the difference being
|
|
whether the local OAM client has actively rejected the peering
|
|
or has just not indicated any decision yet. Whether a peering
|
|
decision has been made is indicated via the local flags field
|
|
in the OAMPDU (reflected in the aOAMLocalFlagsField of
|
|
30.3.6.1.10).
|
|
|
|
If the remote OAM entity rejects the peering, the state
|
|
becomes oamPeeringRemotelyRejected(8). Note that both the
|
|
sendLocalAndRemoteOk(6) and oamPeeringRemotelyRejected(8)
|
|
states fall within the state SEND_LOCAL_REMOTE_OK of the
|
|
Discovery state diagram [802.3ah, Figure 57-5], with the
|
|
difference being whether the remote OAM client has rejected
|
|
the peering or has just not yet decided. This is indicated
|
|
via the remote flags field in the OAM PDU (reflected in the
|
|
aOAMRemoteFlagsField of 30.3.6.1.11).
|
|
|
|
When the local OAM entity learns that both it and the remote
|
|
OAM entity have accepted the peering, the state moves to
|
|
operational(9) corresponding to the SEND_ANY state of the
|
|
Discovery state diagram [802.3ah, Figure 57-5].
|
|
|
|
Since Ethernet OAM functions are not designed to work
|
|
completely over half-duplex interfaces, the value
|
|
nonOperHalfDuplex(10) is returned whenever Ethernet OAM is
|
|
enabled (dot3OamAdminState is enabled(1)) but the interface is
|
|
in half-duplex operation.
|
|
"
|
|
REFERENCE "[802.3ah], 30.3.6.1.4, 30.3.6.1.10, 30.3.6.1.11"
|
|
::= { dot3OamEntryR 2 }
|
|
|
|
dot3OamModeR 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' mode or 'passive' 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. As an example, an active OAM entity can put
|
|
the remote OAM entity in a loopback state, where a passive OAM
|
|
entity cannot.
|
|
|
|
The default value of dot3OamMode is dependent on the type of
|
|
system on which this Ethernet like interface resides. The
|
|
default value should be 'active(1)' unless it is known that
|
|
this system should take on a subservient role to the other
|
|
device connected over this interface.
|
|
|
|
Changing this value results in incrementing the configuration
|
|
revision field of locally generated OAM PDUs (30.3.6.1.12) and
|
|
potentially re-doing the OAM discovery process if the
|
|
dot3OamOperStatus was already operational(9).
|
|
"
|
|
REFERENCE "[802.3ah], 30.3.6.1.3"
|
|
::= { dot3OamEntryR 3 }
|
|
|
|
dot3OamMaxOamPduSizeR OBJECT-TYPE
|
|
SYNTAX Unsigned32 (64..1518)
|
|
UNITS "octets"
|
|
MAX-ACCESS read-only
|
|
STATUS current
|
|
DESCRIPTION
|
|
"The largest OAMPDU that the OAM entity supports. OAM
|
|
entities exchange maximum OAM PDU sizes and negotiate to use
|
|
the smaller of the two maximum OAM PDU sizes between the peers.
|
|
This value is determined by the local implementation.
|
|
"
|
|
REFERENCE "[802.3ah], 30.3.6.1.8"
|
|
::= { dot3OamEntryR 4 }
|
|
|
|
dot3OamConfigRevisionR OBJECT-TYPE
|
|
SYNTAX Unsigned32(0..65535)
|
|
MAX-ACCESS read-only
|
|
STATUS current
|
|
DESCRIPTION
|
|
"The configuration revision of the OAM entity as reflected in
|
|
the latest OAM PDU sent by the OAM entity. The config revision
|
|
is used by OAM entities to indicate configuration changes have
|
|
occurred which might require the peer OAM entity to
|
|
re-evaluate whether OAM peering is allowed.
|
|
"
|
|
REFERENCE "[802.3ah], 30.3.6.1.12"
|
|
::= { dot3OamEntryR 5 }
|
|
|
|
dot3OamFunctionsSupportedR OBJECT-TYPE
|
|
SYNTAX BITS {
|
|
unidirectionalSupport (0),
|
|
loopbackSupport(1),
|
|
eventSupport(2),
|
|
variableSupport(3)
|
|
}
|
|
MAX-ACCESS read-only
|
|
STATUS current
|
|
DESCRIPTION
|
|
"The OAM functions supported on this Ethernet like interface.
|
|
OAM consists of separate functional sets beyond the basic
|
|
discovery process which is always required. These functional
|
|
groups can be supported independently by any implementation.
|
|
These values are communicated to the peer via the local
|
|
configuration field of Information OAM PDUs.
|
|
|
|
Setting 'unidirectionalSupport(0)' indicates that the OAM
|
|
entity supports the transmission of OAM PDUs on links that are
|
|
operating in unidirectional mode (traffic flowing in one
|
|
direction only). Setting 'loopbackSupport(1)' indicates the
|
|
OAM entity can initiate and respond to loopback commands.
|
|
Setting 'eventSupport(2)' indicates the OAM entity can send
|
|
and receive Event Notification OAM PDUs. Setting
|
|
'variableSupport(3)' indicates the OAM entity can send and
|
|
receive Variable Request and Response OAM PDUs.
|
|
"
|
|
REFERENCE "[802.3ah], 30.3.6.1.6"
|
|
::= { dot3OamEntryR 6 }
|
|
|
|
|
|
-- ***************************************************************
|
|
--
|
|
-- Ethernet OAM Peer group
|
|
--
|
|
|
|
dot3OamPeerTableR OBJECT-TYPE
|
|
SYNTAX SEQUENCE OF Dot3OamPeerEntryR
|
|
MAX-ACCESS not-accessible
|
|
STATUS current
|
|
DESCRIPTION
|
|
"This table contains information about the OAM peer for a
|
|
particular Ethernet like interface. OAM entities communicate
|
|
with a single OAM peer entity on Ethernet links on which OAM
|
|
is enabled and operating properly. There is one entry in this
|
|
table for each entry in the dot3OamTable for which information
|
|
on the peer OAM entity is available.
|
|
"
|
|
::= { dot3OamObjectsR 2 }
|
|
|
|
dot3OamPeerEntryR OBJECT-TYPE
|
|
SYNTAX Dot3OamPeerEntryR
|
|
MAX-ACCESS not-accessible
|
|
STATUS current
|
|
DESCRIPTION
|
|
"An entry in the table, containing information on the peer OAM
|
|
entity for a single Ethernet like interface.
|
|
|
|
Note that there is at most one OAM peer for each Ethernet like
|
|
interface. Entries are automatically created when information
|
|
about the OAM peer entity becomes available, and automatically
|
|
deleted when the OAM peer entity is no longer in
|
|
communication. Peer information is not available when
|
|
dot3OamOperStatus is disabled(1), linkFault(2),
|
|
passiveWait(3), activeSendLocal(4). or nonOperHalfDuplex(10)).
|
|
"
|
|
INDEX { ifIndex }
|
|
::= { dot3OamPeerTableR 1 }
|
|
|
|
|
|
Dot3OamPeerEntryR ::=
|
|
SEQUENCE {
|
|
dot3OamPeerMacAddressR MacAddress,
|
|
dot3OamPeerVendorOuiR Dot3Oui,
|
|
dot3OamPeerVendorInfoR Unsigned32,
|
|
dot3OamPeerModeR INTEGER,
|
|
dot3OamPeerMaxOamPduSizeR Unsigned32,
|
|
dot3OamPeerConfigRevisionR Unsigned32,
|
|
dot3OamPeerFunctionsSupportedR BITS
|
|
}
|
|
|
|
dot3OamPeerMacAddressR OBJECT-TYPE
|
|
SYNTAX MacAddress
|
|
MAX-ACCESS read-only
|
|
STATUS current
|
|
DESCRIPTION
|
|
"The MAC address of the peer OAM entity. The MAC address is
|
|
derived from the most recently received OAM PDU.
|
|
"
|
|
REFERENCE "[802.3ah], 30.3.6.1.5."
|
|
::= { dot3OamPeerEntryR 1 }
|
|
|
|
dot3OamPeerVendorOuiR OBJECT-TYPE
|
|
SYNTAX Dot3Oui
|
|
MAX-ACCESS read-only
|
|
STATUS current
|
|
DESCRIPTION
|
|
"The OUI of the OAM peer as reflected in the latest
|
|
Information OAM PDU received with a Local Information TLV. The
|
|
OUI can be used to identify the vendor of the remote OAM
|
|
entity. This value is initialized to zero before any Local
|
|
Information TLV is received.
|
|
"
|
|
REFERENCE "[802.3ah], 30.3.6.1.16."
|
|
::= { dot3OamPeerEntryR 2 }
|
|
|
|
dot3OamPeerVendorInfoR OBJECT-TYPE
|
|
SYNTAX Unsigned32
|
|
MAX-ACCESS read-only
|
|
STATUS current
|
|
DESCRIPTION
|
|
"The Vendor Info of the OAM peer as reflected in the latest
|
|
Information OAM PDU received with a Local Information TLV. The
|
|
vendor information field is within the Local Information TLV,
|
|
and can be used to determine additional information about the
|
|
peer entity. The format of the vendor information is
|
|
unspecified within the 32-bit field. This value is
|
|
initialized to zero before any Local Information TLV is
|
|
received.
|
|
"
|
|
REFERENCE "[802.3ah], 30.3.6.1.17."
|
|
::= { dot3OamPeerEntryR 3 }
|
|
|
|
dot3OamPeerModeR OBJECT-TYPE
|
|
SYNTAX INTEGER {
|
|
active(1),
|
|
passive(2),
|
|
unknown(3)
|
|
}
|
|
MAX-ACCESS read-only
|
|
STATUS current
|
|
DESCRIPTION
|
|
"The mode of the OAM peer as reflected in the latest
|
|
Information OAM PDU received with a Local Information TLV. The
|
|
mode of the peer can be determined from the Configuration
|
|
field in the Local Information TLV of the last Information
|
|
OAMPDU received from the peer. The value is unknown(3)
|
|
whenever no Local Information TLV has been received. The
|
|
values of active(1) and passive(2) are returned when a Local
|
|
Information TLV has been received indicating the peer is in
|
|
active or passive mode, respectively.
|
|
"
|
|
REFERENCE "[802.3ah], 30.3.6.1.7."
|
|
::= { dot3OamPeerEntryR 4 }
|
|
|
|
dot3OamPeerMaxOamPduSizeR OBJECT-TYPE
|
|
SYNTAX Unsigned32 (0..1518)
|
|
UNITS "octets"
|
|
MAX-ACCESS read-only
|
|
STATUS current
|
|
DESCRIPTION
|
|
"The maximum size of OAM PDU supported by the peer as reflected
|
|
in the latest Information OAM PDU received with a Local
|
|
Information TLV. Ethernet OAM on this interface must not use
|
|
OAMPDUs that exceed this size. The maximum OAM PDU size can be
|
|
determined from the PDU Configuration field of the Local
|
|
Information TLV of the last Information OAM PDU received from
|
|
the peer. A value of zero is returned if no Local Information
|
|
TLV has been received. Otherwise, the value of the OAM peer's
|
|
maximum OAM PDU size is returned in this value.
|
|
Note that the values 1..63 are invalid sizes for Ethernet
|
|
frames and should never appear.
|
|
"
|
|
REFERENCE "[802.3ah], 30.3.6.1.9."
|
|
::= { dot3OamPeerEntryR 5 }
|
|
|
|
dot3OamPeerConfigRevisionR OBJECT-TYPE
|
|
SYNTAX Unsigned32(0..65535)
|
|
MAX-ACCESS read-only
|
|
STATUS current
|
|
DESCRIPTION
|
|
"The configuration revision of the OAM peer as reflected in
|
|
the latest OAMPDU. This attribute is changed by the peer
|
|
whenever it has a local configuration change for Ethernet OAM
|
|
this interface. The configuration revision can be determined
|
|
from the Revision field of the Local Information TLV of the
|
|
most recently received Information OAMPDU with a Local
|
|
Information TLV. A value of zero is returned if no Local
|
|
Information TLV has been received.
|
|
"
|
|
REFERENCE "[802.3ah], 30.3.6.1.13."
|
|
::= { dot3OamPeerEntryR 6 }
|
|
|
|
dot3OamPeerFunctionsSupportedR OBJECT-TYPE
|
|
SYNTAX BITS {
|
|
unidirectionalSupport (0),
|
|
loopbackSupport(1),
|
|
eventSupport(2),
|
|
variableSupport(3)
|
|
}
|
|
MAX-ACCESS read-only
|
|
STATUS current
|
|
DESCRIPTION
|
|
"The OAM functions supported on this Ethernet like interface.
|
|
OAM consists of separate functionality sets above the basic
|
|
discovery process. This value indicates the capabilities of
|
|
the peer OAM entity with respect to these functions. This
|
|
value is initialized so all bits are clear.
|
|
|
|
If unidirectionalSupport(0) is set, then the peer OAM entity
|
|
supports sending OAM frames on Ethernet interfaces when the
|
|
receive path is known to be inoperable. If
|
|
loopbackSupport(1) is set, then the peer OAM entity can send
|
|
and receive OAM loopback commands. If eventSupport(2) is set,
|
|
then the peer OAM entity can send and receive event OAM PDUs to
|
|
signal various error conditions. If variableSupport(3) is set,
|
|
then the peer OAM entity can send and receive variable
|
|
requests to monitor attribute value as described in Clause 57
|
|
of [802.3ah].
|
|
|
|
The capabilities of the OAM peer can be determined from the
|
|
configuration field of the Local Information TLV of the most
|
|
recently received Information OAMPDU with a Local Information
|
|
TLV. All zeros are returned if no Local Information TLV has
|
|
yet been received.
|
|
"
|
|
REFERENCE "[802.3ah], REFERENCE 30.3.6.1.7."
|
|
::= { dot3OamPeerEntryR 7 }
|
|
|
|
-- ***************************************************************
|
|
--
|
|
-- {dot3OamObjects 3} is reserved for dot3OamLoopbackTable
|
|
--
|
|
|
|
|
|
-- ***************************************************************
|
|
--
|
|
-- Ethernet OAM Statistics group
|
|
--
|
|
|
|
dot3OamStatsTableR OBJECT-TYPE
|
|
SYNTAX SEQUENCE OF Dot3OamStatsEntryR
|
|
MAX-ACCESS not-accessible
|
|
STATUS current
|
|
DESCRIPTION
|
|
"This table contains statistics for the OAM function on a
|
|
particular Ethernet like interface. There is an entry in the
|
|
table for every entry in the dot3OamTable.
|
|
|
|
The counters in this table are defined as 32-bit entries to
|
|
match the counter size as defined in [802.3ah]. Given the OAM
|
|
protocol is a slow protocol, the counters increment at a slow
|
|
rate.
|
|
"
|
|
::= { dot3OamObjectsR 4 }
|
|
|
|
dot3OamStatsEntryR OBJECT-TYPE
|
|
SYNTAX Dot3OamStatsEntryR
|
|
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. Entries are automatically created for every entry
|
|
in the dot3OamTableR. Counters are maintained across
|
|
transitions in dot3OamOperStatusR.
|
|
"
|
|
INDEX { ifIndex }
|
|
::= { dot3OamStatsTableR 1 }
|
|
|
|
Dot3OamStatsEntryR ::=
|
|
SEQUENCE {
|
|
dot3OamInformationTxR Counter32,
|
|
dot3OamInformationRxR Counter32,
|
|
dot3OamUniqueEventNotificationTxR Counter32,
|
|
dot3OamUniqueEventNotificationRxR Counter32,
|
|
dot3OamDuplicateEventNotificationTxR Counter32,
|
|
dot3OamDuplicateEventNotificationRxR Counter32,
|
|
dot3OamLoopbackControlTxR Counter32,
|
|
dot3OamLoopbackControlRxR Counter32,
|
|
dot3OamVariableRequestTxR Counter32,
|
|
dot3OamVariableRequestRxR Counter32,
|
|
dot3OamVariableResponseTxR Counter32,
|
|
dot3OamVariableResponseRxR Counter32,
|
|
dot3OamOrgSpecificTxR Counter32,
|
|
dot3OamOrgSpecificRxR Counter32,
|
|
dot3OamUnsupportedCodesTxR Counter32,
|
|
dot3OamUnsupportedCodesRxR Counter32,
|
|
dot3OamFramesLostDueToOamR Counter32
|
|
}
|
|
|
|
dot3OamInformationTxR OBJECT-TYPE
|
|
SYNTAX Counter32
|
|
UNITS "frames"
|
|
MAX-ACCESS read-only
|
|
STATUS current
|
|
DESCRIPTION
|
|
"A count of the number of Information OAM PDUs transmitted on
|
|
this interface.
|
|
|
|
Discontinuities of this counter can occur at re-initialization
|
|
of the management system, and at other times as indicated by
|
|
the value of the ifCounterDiscontinuityTime. "
|
|
REFERENCE "[802.3ah], 30.3.6.1.20."
|
|
::= { dot3OamStatsEntryR 1 }
|
|
|
|
dot3OamInformationRxR OBJECT-TYPE
|
|
SYNTAX Counter32
|
|
UNITS "frames"
|
|
MAX-ACCESS read-only
|
|
STATUS current
|
|
DESCRIPTION
|
|
"A count of the number of Information OAM PDUs received on this
|
|
interface.
|
|
|
|
Discontinuities of this counter can occur at re-initialization
|
|
of the management system, and at other times as indicated by
|
|
the value of the ifCounterDiscontinuityTime.
|
|
"
|
|
REFERENCE "[802.3ah], 30.3.6.1.21."
|
|
::= { dot3OamStatsEntryR 2 }
|
|
|
|
dot3OamUniqueEventNotificationTxR OBJECT-TYPE
|
|
SYNTAX Counter32
|
|
UNITS "frames"
|
|
MAX-ACCESS read-only
|
|
STATUS current
|
|
DESCRIPTION
|
|
"A count of the number of unique Event OAM PDUs transmitted on
|
|
this interface. Event notifications may be sent in duplicate
|
|
to increase the probability of successfully being received,
|
|
given the possibility that a frame may be lost in transit.
|
|
Duplicate Event Notification transmissions are counted by
|
|
dot3OamDuplicateEventNotificationTx.
|
|
|
|
A unique Event Notification OAMPDU is indicated as an Event
|
|
Notification OAM PDU with a Sequence Number field that is
|
|
distinct from the previously transmitted Event Notification
|
|
OAMPDU Sequence Number.
|
|
|
|
Discontinuities of this counter can occur at re-initialization
|
|
of the management system, and at other times as indicated by
|
|
the value of the ifCounterDiscontinuityTime.
|
|
"
|
|
REFERENCE "[802.3ah], 30.3.6.1.22."
|
|
::= { dot3OamStatsEntryR 3 }
|
|
|
|
dot3OamUniqueEventNotificationRxR OBJECT-TYPE
|
|
SYNTAX Counter32
|
|
UNITS "frames"
|
|
MAX-ACCESS read-only
|
|
STATUS current
|
|
DESCRIPTION
|
|
"A count of the number of unique Event OAM PDUs received on
|
|
this interface. Event notification OAM PDUs may be sent in
|
|
duplicate to increase the probability of successfully being
|
|
received, given the possibility that a frame may be lost in
|
|
transit. Duplicate Event Notification receptions are counted
|
|
by dot3OamDuplicateEventNotificationRx.
|
|
|
|
A unique Event Notification OAM PDU is indicated as an Event
|
|
Notification OAM PDU with a Sequence Number field that is
|
|
distinct from the previously received Event Notification
|
|
OAMPDU Sequence Number.
|
|
|
|
Discontinuities of this counter can occur at re-initialization
|
|
of the management system, and at other times as indicated by
|
|
the value of the ifCounterDiscontinuityTime.
|
|
"
|
|
REFERENCE "[802.3ah], 30.3.6.1.24."
|
|
::= { dot3OamStatsEntryR 4 }
|
|
|
|
dot3OamDuplicateEventNotificationTxR OBJECT-TYPE
|
|
SYNTAX Counter32
|
|
UNITS "frames"
|
|
MAX-ACCESS read-only
|
|
STATUS current
|
|
DESCRIPTION
|
|
"A count of the number of duplicate Event OAM PDUs transmitted
|
|
on this interface. Event notification OAM PDUs may be sent in
|
|
duplicate to increase the probability of successfully being
|
|
received, given the possibility that a frame may be lost in
|
|
transit.
|
|
|
|
A duplicate Event Notification OAM PDU is indicated as an Event
|
|
Notification OAMPDU with a Sequence Number field that is
|
|
identical to the previously transmitted Event Notification
|
|
OAMPDU Sequence Number.
|
|
|
|
Discontinuities of this counter can occur at re-initialization
|
|
of the management system, and at other times as indicated by
|
|
the value of the ifCounterDiscontinuityTime.
|
|
"
|
|
REFERENCE "[802.3ah], 30.3.6.1.23."
|
|
::= { dot3OamStatsEntryR 5 }
|
|
|
|
dot3OamDuplicateEventNotificationRxR OBJECT-TYPE
|
|
SYNTAX Counter32
|
|
UNITS "frames"
|
|
MAX-ACCESS read-only
|
|
STATUS current
|
|
DESCRIPTION
|
|
"A count of the number of duplicate Event OAM PDUs received on
|
|
this interface. Event notification OAM PDUs may be sent in
|
|
duplicate to increase the probability of successfully being
|
|
received, given the possibility that a frame may be lost in
|
|
transit.
|
|
|
|
A duplicate Event Notification OAM PDU is indicated as an Event
|
|
Notification OAMPDU with a Sequence Number field that is
|
|
identical to the previously received Event Notification OAM PDU
|
|
Sequence Number.
|
|
|
|
Discontinuities of this counter can occur at re-initialization
|
|
of the management system, and at other times as indicated by
|
|
the value of the ifCounterDiscontinuityTime.
|
|
"
|
|
REFERENCE "[802.3ah], 30.3.6.1.25."
|
|
::= { dot3OamStatsEntryR 6 }
|
|
|
|
dot3OamLoopbackControlTxR OBJECT-TYPE
|
|
SYNTAX Counter32
|
|
UNITS "frames"
|
|
MAX-ACCESS read-only
|
|
STATUS current
|
|
DESCRIPTION
|
|
"A count of the number of Loopback Control OAM PDUs transmitted
|
|
on this interface.
|
|
|
|
Discontinuities of this counter can occur at re-initialization
|
|
of the management system, and at other times as indicated by
|
|
the value of the ifCounterDiscontinuityTime.
|
|
"
|
|
REFERENCE "[802.3ah], 30.3.6.1.26."
|
|
::= { dot3OamStatsEntryR 7 }
|
|
|
|
dot3OamLoopbackControlRxR OBJECT-TYPE
|
|
SYNTAX Counter32
|
|
UNITS "frames"
|
|
MAX-ACCESS read-only
|
|
STATUS current
|
|
DESCRIPTION
|
|
"A count of the number of Loopback Control OAM PDUs received
|
|
on this interface.
|
|
|
|
Discontinuities of this counter can occur at re-initialization
|
|
of the management system, and at other times as indicated by
|
|
the value of the ifCounterDiscontinuityTime.
|
|
"
|
|
REFERENCE "[802.3ah], 30.3.6.1.27."
|
|
::= { dot3OamStatsEntryR 8 }
|
|
|
|
dot3OamVariableRequestTxR OBJECT-TYPE
|
|
SYNTAX Counter32
|
|
UNITS "frames"
|
|
MAX-ACCESS read-only
|
|
STATUS current
|
|
DESCRIPTION
|
|
"A count of the number of Variable Request OAM PDUs transmitted
|
|
on this interface.
|
|
|
|
Discontinuities of this counter can occur at re-initialization
|
|
of the management system, and at other times as indicated by
|
|
the value of the ifCounterDiscontinuityTime.
|
|
"
|
|
REFERENCE "[802.3ah], 30.3.6.1.28."
|
|
::= { dot3OamStatsEntryR 9 }
|
|
|
|
dot3OamVariableRequestRxR OBJECT-TYPE
|
|
SYNTAX Counter32
|
|
UNITS "frames"
|
|
MAX-ACCESS read-only
|
|
STATUS current
|
|
DESCRIPTION
|
|
"A count of the number of Variable Request OAM PDUs received on
|
|
this interface.
|
|
|
|
Discontinuities of this counter can occur at re-initialization
|
|
of the management system, and at other times as indicated by
|
|
the value of the ifCounterDiscontinuityTime.
|
|
"
|
|
REFERENCE "[802.3ah], 30.3.6.1.29."
|
|
::= { dot3OamStatsEntryR 10 }
|
|
|
|
dot3OamVariableResponseTxR OBJECT-TYPE
|
|
SYNTAX Counter32
|
|
UNITS "frames"
|
|
MAX-ACCESS read-only
|
|
STATUS current
|
|
DESCRIPTION
|
|
"A count of the number of Variable Response OAM PDUs
|
|
transmitted on this interface.
|
|
|
|
Discontinuities of this counter can occur at re-initialization
|
|
of the management system, and at other times as indicated by
|
|
the value of the ifCounterDiscontinuityTime.
|
|
"
|
|
REFERENCE "[802.3ah], 30.3.6.1.30."
|
|
::= { dot3OamStatsEntryR 11 }
|
|
|
|
dot3OamVariableResponseRxR OBJECT-TYPE
|
|
SYNTAX Counter32
|
|
UNITS "frames"
|
|
MAX-ACCESS read-only
|
|
STATUS current
|
|
DESCRIPTION
|
|
"A count of the number of Variable Response OAM PDUs received
|
|
on this interface.
|
|
|
|
Discontinuities of this counter can occur at re-initialization
|
|
of the management system, and at other times as indicated by
|
|
the value of the ifCounterDiscontinuityTime.
|
|
"
|
|
REFERENCE "[802.3ah], 30.3.6.1.31."
|
|
::= { dot3OamStatsEntryR 12 }
|
|
|
|
dot3OamOrgSpecificTxR OBJECT-TYPE
|
|
SYNTAX Counter32
|
|
UNITS "frames"
|
|
MAX-ACCESS read-only
|
|
STATUS current
|
|
DESCRIPTION
|
|
"A count of the number of Organization Specific OAM PDUs
|
|
transmitted on this interface.
|
|
|
|
Discontinuities of this counter can occur at re-initialization
|
|
of the management system, and at other times as indicated by
|
|
the value of the ifCounterDiscontinuityTime.
|
|
"
|
|
REFERENCE "[802.3ah], 30.3.6.1.32."
|
|
::= { dot3OamStatsEntryR 13 }
|
|
|
|
dot3OamOrgSpecificRxR OBJECT-TYPE
|
|
SYNTAX Counter32
|
|
UNITS "frames"
|
|
MAX-ACCESS read-only
|
|
STATUS current
|
|
DESCRIPTION
|
|
"A count of the number of Organization Specific OAM PDUs
|
|
received on this interface.
|
|
|
|
Discontinuities of this counter can occur at re-initialization
|
|
of the management system, and at other times as indicated by
|
|
the value of the ifCounterDiscontinuityTime.
|
|
"
|
|
REFERENCE "[802.3ah], 30.3.6.1.33."
|
|
::= { dot3OamStatsEntryR 14 }
|
|
|
|
dot3OamUnsupportedCodesTxR OBJECT-TYPE
|
|
SYNTAX Counter32
|
|
UNITS "frames"
|
|
MAX-ACCESS read-only
|
|
STATUS current
|
|
DESCRIPTION
|
|
"A count of the number of OAM PDUs transmitted on this
|
|
interface with an unsupported op-code.
|
|
|
|
Discontinuities of this counter can occur at re-initialization
|
|
of the management system, and at other times as indicated by
|
|
the value of the ifCounterDiscontinuityTime.
|
|
"
|
|
REFERENCE "[802.3ah], 30.3.6.1.18."
|
|
::= { dot3OamStatsEntryR 15 }
|
|
|
|
dot3OamUnsupportedCodesRxR OBJECT-TYPE
|
|
SYNTAX Counter32
|
|
UNITS "frames"
|
|
MAX-ACCESS read-only
|
|
STATUS current
|
|
DESCRIPTION
|
|
"A count of the number of OAM PDUs received on this interface
|
|
with an unsupported op-code.
|
|
|
|
Discontinuities of this counter can occur at re-initialization
|
|
of the management system, and at other times as indicated by
|
|
the value of the ifCounterDiscontinuityTime.
|
|
"
|
|
REFERENCE "[802.3ah], 30.3.6.1.19."
|
|
::= { dot3OamStatsEntryR 16 }
|
|
|
|
dot3OamFramesLostDueToOamR OBJECT-TYPE
|
|
SYNTAX Counter32
|
|
UNITS "frames"
|
|
MAX-ACCESS read-only
|
|
STATUS current
|
|
DESCRIPTION
|
|
"A count of the number of frames that were dropped by the OAM
|
|
multiplexer. Since the OAM multiplexer has multiple inputs
|
|
and a single output, there may be cases where frames are
|
|
dropped due to transmit resource contention. This counter is
|
|
incremented whenever a frame is dropped by the OAM layer.
|
|
Note that any Ethernet frame, not just OAM PDUs, may be dropped
|
|
by the OAM layer. This can occur when an OAM PDU takes
|
|
precedence over a 'normal' frame resulting in the 'normal'
|
|
frame being dropped.
|
|
|
|
When this counter is incremented, no other counters in this
|
|
MIB are incremented.
|
|
|
|
Discontinuities of this counter can occur at re-initialization
|
|
of the management system, and at other times as indicated by
|
|
the value of the ifCounterDiscontinuityTime.
|
|
"
|
|
REFERENCE "[802.3ah], 30.3.6.1.46."
|
|
::= { dot3OamStatsEntryR 17 }
|
|
|
|
-- ***************************************************************
|
|
--
|
|
-- { dot3OamObjects 5 } is reserved for dot3OamEventConfigTable
|
|
-- { dot3OamObjects 6 } is reserved for dot3OamEventLogTable
|
|
--
|
|
END
|