CISCO-DOT3-OAM-MIB

        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.
    
Source file
CISCO-DOT3-OAM-MIB
Last revised
Identity
cdot3OamMIB
Base OID
1.3.6.1.4.1.9.10.136
Imported Objects
CISCO-SMI ciscoExperiment
HCNUM-TC CounterBasedGauge64
IF-MIB ifIndex
SNMPv2-CONF MODULE-COMPLIANCE (no object page) NOTIFICATION-GROUP (no object page) OBJECT-GROUP (no object page)
SNMPv2-SMI Counter32 Integer32 MODULE-IDENTITY (no object page) NOTIFICATION-TYPE (no object page) OBJECT-TYPE (no object page) Unsigned32
SNMPv2-TC MacAddress TEXTUAL-CONVENTION (no object page) TimeStamp TruthValue
Net-SNMP examples using the cisco MIB directory Show commands

These commands use the standard Observium installation path and load the selected MIB variant before the RFC and Net-SNMP directories.

Translate the module identity
/usr/bin/snmptranslate -Pud -Ir -On -m 'CISCO-DOT3-OAM-MIB' -M '/opt/observium/mibs/cisco:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'CISCO-DOT3-OAM-MIB::cdot3OamMIB'
Walk the MIB subtree
/usr/bin/snmpbulkwalk -v2c -c '<community>' -Pud -Ir -OQUs -m 'CISCO-DOT3-OAM-MIB' -M '/opt/observium/mibs/cisco:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'CISCO-DOT3-OAM-MIB::cdot3OamMIB'
How SNMP, Net-SNMP, MIB paths, and variants work
Objects (78)
.1.3.6.1.4.1.9.10.136
.1.3.6.1.4.1.9.10.136.0
.1.3.6.1.4.1.9.10.136.1
.1.3.6.1.4.1.9.10.136.1.1
.1.3.6.1.4.1.9.10.136.1.1.1
Enumeration
.1.3.6.1.4.1.9.10.136.1.1.1.1
Enumeration
.1.3.6.1.4.1.9.10.136.1.1.1.2
Enumeration
.1.3.6.1.4.1.9.10.136.1.1.1.3
octetsUnsigned32
.1.3.6.1.4.1.9.10.136.1.1.1.4
Unsigned32
.1.3.6.1.4.1.9.10.136.1.1.1.5
Bits
.1.3.6.1.4.1.9.10.136.1.1.1.6
.1.3.6.1.4.1.9.10.136.1.2
.1.3.6.1.4.1.9.10.136.1.2.1
.1.3.6.1.4.1.9.10.136.1.2.1.1
.1.3.6.1.4.1.9.10.136.1.2.1.2
.1.3.6.1.4.1.9.10.136.1.2.1.3
Enumeration
.1.3.6.1.4.1.9.10.136.1.2.1.4
octetsUnsigned32
.1.3.6.1.4.1.9.10.136.1.2.1.5
Unsigned32
.1.3.6.1.4.1.9.10.136.1.2.1.6
Bits
.1.3.6.1.4.1.9.10.136.1.2.1.7
.1.3.6.1.4.1.9.10.136.1.3
.1.3.6.1.4.1.9.10.136.1.3.1
Enumeration
.1.3.6.1.4.1.9.10.136.1.3.1.1
Enumeration
.1.3.6.1.4.1.9.10.136.1.3.1.2
.1.3.6.1.4.1.9.10.136.1.4
.1.3.6.1.4.1.9.10.136.1.4.1
.1.3.6.1.4.1.9.10.136.1.4.1.1
.1.3.6.1.4.1.9.10.136.1.4.1.10
.1.3.6.1.4.1.9.10.136.1.4.1.11
.1.3.6.1.4.1.9.10.136.1.4.1.12
.1.3.6.1.4.1.9.10.136.1.4.1.13
.1.3.6.1.4.1.9.10.136.1.4.1.14
.1.3.6.1.4.1.9.10.136.1.4.1.15
.1.3.6.1.4.1.9.10.136.1.4.1.16
.1.3.6.1.4.1.9.10.136.1.4.1.17
.1.3.6.1.4.1.9.10.136.1.4.1.2
.1.3.6.1.4.1.9.10.136.1.4.1.3
.1.3.6.1.4.1.9.10.136.1.4.1.4
.1.3.6.1.4.1.9.10.136.1.4.1.5
.1.3.6.1.4.1.9.10.136.1.4.1.6
.1.3.6.1.4.1.9.10.136.1.4.1.7
.1.3.6.1.4.1.9.10.136.1.4.1.8
.1.3.6.1.4.1.9.10.136.1.4.1.9
.1.3.6.1.4.1.9.10.136.1.5
.1.3.6.1.4.1.9.10.136.1.5.1
.1.3.6.1.4.1.9.10.136.1.5.1.1
.1.3.6.1.4.1.9.10.136.1.5.1.10
.1.3.6.1.4.1.9.10.136.1.5.1.11
tenths of a secondInteger32
.1.3.6.1.4.1.9.10.136.1.5.1.12
errored frame secondsInteger32
.1.3.6.1.4.1.9.10.136.1.5.1.13
.1.3.6.1.4.1.9.10.136.1.5.1.14
.1.3.6.1.4.1.9.10.136.1.5.1.15
.1.3.6.1.4.1.9.10.136.1.5.1.16
.1.3.6.1.4.1.9.10.136.1.5.1.2
.1.3.6.1.4.1.9.10.136.1.5.1.3
.1.3.6.1.4.1.9.10.136.1.5.1.4
.1.3.6.1.4.1.9.10.136.1.5.1.5
.1.3.6.1.4.1.9.10.136.1.5.1.6
.1.3.6.1.4.1.9.10.136.1.5.1.7
.1.3.6.1.4.1.9.10.136.1.5.1.8
tenths of a secondSNMPv2-SMIUnsigned32
.1.3.6.1.4.1.9.10.136.1.5.1.9
.1.3.6.1.4.1.9.10.136.1.6
.1.3.6.1.4.1.9.10.136.1.6.1
.1.3.6.1.4.1.9.10.136.1.6.1.1
.1.3.6.1.4.1.9.10.136.1.6.1.10
.1.3.6.1.4.1.9.10.136.1.6.1.11
.1.3.6.1.4.1.9.10.136.1.6.1.12
.1.3.6.1.4.1.9.10.136.1.6.1.2
.1.3.6.1.4.1.9.10.136.1.6.1.3
.1.3.6.1.4.1.9.10.136.1.6.1.4
Enumeration
.1.3.6.1.4.1.9.10.136.1.6.1.5
.1.3.6.1.4.1.9.10.136.1.6.1.6
.1.3.6.1.4.1.9.10.136.1.6.1.7
.1.3.6.1.4.1.9.10.136.1.6.1.8
.1.3.6.1.4.1.9.10.136.1.6.1.9
.1.3.6.1.4.1.9.10.136.2
.1.3.6.1.4.1.9.10.136.2.1
.1.3.6.1.4.1.9.10.136.2.2
Dependencies (8) 6 direct · 2 transitive Show tree and compile order Hide dependency details

Each imported module is resolved in the importing module's source directory first, then through the normal default-variant rules.

Dependency tree
Dependency-first compile order
  1. SNMPv2-SMIrfc
  2. CISCO-SMIcisco
  3. SNMPv2-TCrfc
  4. HCNUM-TCrfc
  5. IANAifType-MIBrfc
  6. SNMPv2-CONFrfc
  7. SNMPv2-MIBrfc
  8. IF-MIBrfc
  9. CISCO-DOT3-OAM-MIBciscoselected
Type Definitions (1)
OctetString range: 3
Conformance Groups (11)
A collection of objects providing the abilities,
configuration, and status of an Ethernet OAM entity.
.1.3.6.1.4.1.9.10.136.2.1.1
A collection of objects providing the abilities,
configuration, and status of a peer Ethernet OAM entity.
.1.3.6.1.4.1.9.10.136.2.1.2
A collection of objects providing the statistics for the
number of various transmit and receive events for OAM on an
Ethernet like interface. Note that all of these counters must
be supported even if the related function (as described in
cdot3OamFunctionsSupported) is not supported.
.1.3.6.1.4.1.9.10.136.2.1.3
A collection of objects for controlling the OAM remote
loopback function.
.1.3.6.1.4.1.9.10.136.2.1.4
A collection of objects for configuring the thresholds for an
Errored Symbol Period Event.

Each [802.3ah] defined Event Notification TLV has its own
conformance group because each event can be implemented
independently of any other.
.1.3.6.1.4.1.9.10.136.2.1.5
A collection of objects for configuring the thresholds for an
Errored Frame Period Event.

Each [802.3ah] defined Event Notification TLV has its own
conformance group because each event can be implemented
independently of any other.
.1.3.6.1.4.1.9.10.136.2.1.6
A collection of objects for configuring the thresholds for an
Errored Frame Event.

Each [802.3ah] defined Event Notification TLV has its own
conformance group because each event can be implemented
independently of any other.
.1.3.6.1.4.1.9.10.136.2.1.7
A collection of objects for configuring the thresholds for an
Errored Frame Seconds Summary Event.

Each [802.3ah] defined Event Notification TLV has its own
conformance group because each event can be implemented
independently of any other.
.1.3.6.1.4.1.9.10.136.2.1.8
A collection of objects for configuring the sending OAMPDUs
with the critical event flag or dying gasp flag enabled.
.1.3.6.1.4.1.9.10.136.2.1.9
A collection of objects for configuring the thresholds for an
Errored Frame Seconds Summary Event and maintaining the event
information.
.1.3.6.1.4.1.9.10.136.2.1.10
A collection of notifications used by Ethernet OAM to signal
to a management entity that local or remote events have
occurred on a specified Ethernet link.
.1.3.6.1.4.1.9.10.136.2.1.11
Compliance Statements (1)

OID .1.3.6.1.4.1.9.10.136.2.2.1
The compliance statement for managed entities
supporting OAM on Ethernet like interfaces.
Required groups
mandatory cdot3OamControlGroup
mandatory cdot3OamPeerGroup
mandatory cdot3OamStatsBaseGroup
optional cdot3OamLoopbackGroup This group is mandatory for all IEEE 802.3 OAM
implementations that support loopback functionality.
optional cdot3OamErrSymbolPeriodEventGroup This group is mandatory for all IEEE 802.3 OAM
implementations that support event functionality.
optional cdot3OamErrFramePeriodEventGroup This group is mandatory for all IEEE 802.3 OAM
implementations that support event functionality.
optional cdot3OamErrFrameEventGroup This group is mandatory for all IEEE 802.3 OAM
implementations that support event functionality.
optional cdot3OamErrFrameSecsSummaryEventGroup This group is mandatory for all IEEE 802.3 OAM
implementations that support event functionality.
optional cdot3OamFlagEventGroup This group is optional for all IEEE 802.3 OAM
implementations. The ability to send critical events or dying
gasp events is not required in any system.
optional cdot3OamEventLogGroup This group is optional for all IEEE 802.3 OAM
implementations. Entries in this table are dependent on what
event functionality is supported in the local OAM
implementation. At least one type of event must be supported
for entries to appear in this table.
optional cdot3OamNotificationGroup This group is optional for all IEEE 802.3 OAM
implementations. Since the information in the notifications
is dependent on the cdot3OamEventLogTable, that table must be
implemented for notifications.
Notifications / Traps (2)
NameOIDDescription
.1.3.6.1.4.1.9.10.136.0.1
A cdot3OamThresholdEvent notification is sent when a local or
remote threshold crossing event is detected. A local
threshold crossing event is detected by the local entity,
while a remote threshold crossing event is detected by the
reception of an Ethernet OAM Event Notification OAMPDU
indicating a threshold event.

This notification should not be sent more than once per
second.

The OAM entity can be derived from extracting the ifIndex from
the variable bindings. The objects in the notification
correspond to the values in a row instance of in the
cdot3OamEventLogTable.

The management entity should periodically check
cdot3OamEventLogTable to detect any missed events.
.1.3.6.1.4.1.9.10.136.0.2
A cdot3OamNonThresholdEvent notification is sent when a local
or remote non-threshold crossing event is detected. A local
event is detected by the local entity, while a remote event is
detected by the reception of an Ethernet OAM Event
Notification OAMPDU indicating a non-threshold crossing event.

This notification should not be sent more than once per
second.

The OAM entity can be derived from extracting the ifIndex from
the variable bindings. The objects in the notification
correspond to the values in a row instance of the
cdot3OamEventLogTable.

The management entity should periodically check
cdot3OamEventLogTable to detect any missed events.