The SNMP agent supports Get, Get-next, and Get-Bulk requests on the OAMDot3 MIB. SNMP SET requests are not supported.
The 802.3ah OAM MIB is defined here: https://tools.ietf.org/html/rfc4878 . This MIB defines objects for managing This MIB defines objects for managing Operations, Administration, and Maintenance (OAM) capabilities on Ethernet-like interfaces.
| MIB object , OID , Syntax, MAX-ACCESS | Description | Possible values | Supported (Yes/No) |
|---|---|---|---|
|
dot3OamAdminState OID: dot3OamEntry.1 SYNTAX: INTEGER MAX-ACCESS: Read Only |
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 dot3OamAdminState always starts in the disabled (2) state until an explicit management action or configuration information retained by the system causes a transition to the enabled (1) state. When enabled (1), Ethernet OAM will attempt to operate over this interface. |
enabled(1), disabled(2) |
Yes |
|
dot3OamAdminState OID: dot3OamEntry.2 SYNTAX: INTEGER MAX-ACCESS: Read Only |
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 OAsublayer. This value is always disabled (1) if OAM is disabled on this interface via the dot3OamAdminState.If the link has detected a fault and is transmitting OAMPDUs 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) ortesting(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 OA 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 hasnot yet made that determination. The state sendLocalAndRemote(5) reflects that the local OAentity 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 within the state SEND_LOCAL_REMOTE of the Discovery state diagram [802.3ah, Figure 57-5], with the difference beingwhether the local OAM client has actively rejected the peeringor 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 rejectedthe peering or has just not yet decided. This is indicated via the remote flags field in the OAMPDU (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. |
disabled(1), linkFault(2), passiveWait(3), activeSendLocal(4), sendLocalAndRemote(5), sendLocalAndRemoteOk(6), oamPeeringLocallyRejected(7), oamPeeringRemotelyRejected(8), operational(9), nonOperHalfDuplex(10 |
Yes |
|
dot3OamAdminState OID: dot3OamEntry.3 SYNTAX: INTEGER MAX-ACCESS: Read Only |
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 OA actions with it. |
passive(1), active(2) |
Yes |
|
dot3OamMaxOamPduSize OID: dot3OamEntry.4 SYNTAX: Unsigned32 MAX-ACCESS: Read Only |
The largest OAMPDU that the OAM entity supports. OA entities exchange maximum OAMPDU sizes and negotiate to use the smaller of the two maximum OAMPDU sizes between the peers. | 64..1518 | Yes |
|
dot3OamConfigRevision OID: dot3OamEntry.5 SYNTAX: Unsigned32 MAX-ACCESS: Read Only |
The configuration revision of the OAM entity as reflected in the latest OAMPDU sent by the OAM entity. The configuration revision is used by OAM entities to indicate that configuration changes have occurred, which might require the peer OAM entity to re-evaluate whether OAM peering is allowed. |
0..65535 | Yes |
|
dot3OamFunctionsSupported OID: dot3OamEntry.6 SYNTAX : BITS MAX-ACCESS: Read Only |
The OAM functions supported on this Ethernet-like interface. OAM consists of separate functional sets beyond the basic discovery process that 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 OAMPDUs.Setting 'unidirectionalSupport(0)' indicates that the OA entity supports the transmission of OAMPDUs on links that are operating in unidirectional mode (traffic flowing in one direction only). Setting 'loopbackSupport(1)' indicates that the OAM entity can initiate and respond to loopback commands. Setting 'eventSupport(2)' indicates that the OAM entity can send and receive Event Notification OAMPDUs. Setting 'variableSupport(3)' indicates that the OAM entity can send and receive Variable Request and Response OAMPDUs. |
unidirectionalSupport (0), loopbackSupport(1), eventSupport(2), variableSupport(3 |
Yes |
| MIB object , OID , Syntax , MAX-ACCESS | Description | Possible values | Supported (Yes/No) |
|---|---|---|---|
|
dot3OamPeerMacAddress OID: dot3OamPeerEntry.1 SYNTAX: MacAddress MAX-ACCESS: Read only |
The MAC address of the peer OAM entity. The MAC address is derived from the most recently received OAMPDU |
Yes |
|
|
dot3OamPeerVendorOui OID: dot3OamPeerEntry.2 SYNTAX: EightOTwoOui MAX-ACCESS: Read only |
The OUI of the OAM peer as reflected in the latest Information OAMPDU received with a Local Information TLV. The OUI can be used to identify the vendor of the remote OA entity. This value is initialized to three octets of zero before any Local Information TLV is received. |
Read only |
Yes |
|
dot3OamPeerVendorInfo OID: dot3OamPeerEntry.3 SYNTAX: Unsigned32 MAX-ACCESS: Read only |
The Vendor Info of the OAM peer as reflected in the latest Information OAMPDU received with a Local Information TLV. The semantics of the Vendor Information field is proprietary and specific to the vendor (identified by the dot3OamPeerVendorOui). This information could, for example, be used to identify a specific product or product family. This value is initialized to zero before any Local Information TLV is received. |
Read only |
Yes |
|
dot3OamPeerMode OID: dot3OamPeerEntry.4 SYNTAX: INTEGER MAX-ACCESS: Read only |
The mode of the OAM peer as reflected in the latest Information OAMPDU received with a Local Information TLV. The mode of the peer can be determined from the Configuration field in the Local Information TLV of the last Information OAMPDU received from the peer. |
passive(1), active(2), unknown(3) |
Yes |
|
dot3OamPeerMaxOamPduSize OID: dot3OamPeerEntry.5 SYNTAX: Unsigned32 MAX-ACCESS: Read only |
The maximum size of OAMPDU supported by the peer as reflected in the latest Information OAMPDU received with a Local Information TLV. |
0 | 64..1518 |
Yes |
|
dot3OamPeerConfigRevision OID: dot3OamPeerEntry.6 SYNTAX: Unsigned32 MAX-ACCESS: Read only |
The configuration revision of the OAM peer as reflected in latest OAMPDU |
0..65535 |
Yes |
|
dot3OamPeerFunctionsSupported OID: dot3OamPeerEntry.7 SYNTX: BITS MAX-ACCESS: Read only |
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 OAMPDUs to signal various error conditions. If variableSupport(3) is set, then the peer OAM entity can send and receive variable requests to monitor the attribute value |
unidirectionalSupport (0), loopbackSupport(1), eventSupport(2), variableSupport(3) |
Yes |
| MIB object , OID , Syntax , MAX-ACCESS | Description | Possible values | Supported (Yes/No) |
|---|---|---|---|
| dot3OamLoopbackStatus
OID: dot3OamLoopbackEntry.1 SYNTAX: INTEGER MAX-ACCESS: Read Only |
The loopback status of the OAM entity | noLoopback (1) initiatingLoopback (2) remoteLoopback (3)terminatingLoopback (4) localLoopback (5) unknown (6) | Yes |
| dot3OamLoopbackIgnoreRx
OID: dot3OamLoopbackEntry.2 SYNTAX: INTEGER MAX-ACCESS: RW |
When the value is ignore (1), received loopback commands are ignored. When the value is process (2), OAM loopback commands are processed. The default value is to ignore loopback commands | ignore(1), process(2) | Yes |
| MIB object , OID , Syntax , MAX-ACCESS | Description | Possible values | Supported (Yes/No) |
|---|---|---|---|
| dot3OamInformationTx
OID: dot3OamStatsEntry .1 SYNTAX: Counter32 MAX-ACCESS: Read Only |
A count of the number of Information OAMPDUs transmitted on this interface | Yes | |
| dot3OamInformationRx
OID: dot3OamStatsEntry .2 SYNTAX: Counter32 MAX-ACCESS: Read Only |
A count of the number of Information OAMPDUs received on this interface. | Yes | |
| dot3OamUniqueEventNotificationTx
OID: dot3OamStatsEntry .3 SYNTAX: Counter32 MAX-ACCESS: Read Only |
A count of the number of unique Event OAMPDUs transmitted on this interface | No , SLX-OS as well as MLX doesn't support sending this | |
| dot3OamUniqueEventNotificationRx OID: dot3OamStatsEntry .4SYNTAX: Counter32MAX-ACCESS: Read Only | A count of the number of unique Event OAMPDUs received on this interface | Yes ( Though SLX-OS and MLX doesn't send this they are capable to receive such PDU and update the counter) | |
| dot3OamDuplicateEventNotificationTx
OID: dot3OamStatsEntry .5 SYNTAX: Counter32 MAX-ACCESS: Read Only |
A count of the number of duplicate Event OAMPDUs transmitted on this interface | No, SLX-OS as well as MLX doesn't support sending this | |
| dot3OamDuplicateEventNotificationRx
OID: dot3OamStatsEntry .6 SYNTAX: Counter32 MAX-ACCESS: Read Only |
A count of the number of duplicate Event OAMPDUs received on this interface | Yes ( Though SLX-OS and MLX doesn't send this they are capable to receive such PDU and update the counter) | |
| dot3OamLoopbackControlTx
OID: dot3OamStatsEntry .7 SYNTAX: Counter32 MAX-ACCESS: Read Only |
A count of the number of Loopback Control OAMPDUs transmitted onthis interface | No ,SLX-OS as well as also MLX doesn't support sending this | |
| dot3OamLoopbackControlRx OID: dot3OamStatsEntry .8SYNTAX: Counter32MAX-ACCESS: Read Only | A count of the number of Loopback Control OAMPDUs received on this interface | Yes ( Though SLX-OS and MLX doesn't send this they are capable to receive such PDU and update the counter) | |
| dot3OamVariableRequestTx
OID: dot3OamStatsEntry .9 SYNTAX: Counter32 MAX-ACCESS: Read Only |
A count of the number of Variable Request OAMPDUs transmitted on this interface | No, SLX-OS as well as MLX doesn't support sending this | |
| dot3OamVariableRequestRx
OID: dot3OamStatsEntry .10 SYNTAX: Counter32 MAX-ACCESS: Read Only |
A count of the number of Variable Response OAMPDUs received on this interface | Yes ( Though SLX-OS and MLX doesn't send this they are capable to receive such PDU and update the counter) | |
| dot3OamVariableResponseTx
OID: dot3OamStatsEntry .11 SYNTAX: Counter32 MAX-ACCESS: Read Only |
A count of the number of Variable Response OAMPDUs transmitted on this interface | No, SLX OS as well as MLX doesn't support sending this | |
| dot3OamVariableResponseRx
OID: dot3OamStatsEntry .12 SYNTAX: Counter32 MAX-ACCESS: Read Only |
A count of the number of Variable Response OAMPDUs received on this interface | Yes ( Though SLX-OS and MLX doesn't send this they are capable to receive such PDU and update the counter) | |
| dot3OamOrgSpecificTx
OID: dot3OamStatsEntry .13 SYNTAX: Counter32 MAX-ACCESS: Read Only |
A count of the number of Organization Specific OAMPDUs Transmitted on this interface | No, SLX OS as well as MLX doesn't support sending this | |
| dot3OamOrgSpecificRx
OID: dot3OamStatsEntry .14 SYNTAX: Counter32 MAX-ACCESS: Read Only |
A count of the number of Organization Specific OAMPDUs received on this interface | Yes ( Though SLX-OS and MLX doesn't send this they are capable to receive such PDU and update the counter) | |
| dot3OamUnsupportedCodesTx
OID: dot3OamStatsEntry .15 SYNTAX: Counter32MAX-ACCESS: Read Only |
A count of the number of OAMPDUs transmitted on this interface with an unsupported op-code. | No , SLX-OS as well as MLX doesn't support sending this | |
| dot3OamUnsupportedCodesRx
OID: dot3OamStatsEntry .16 SYNTAX: Counter32 MAX-ACCESS: Read Only |
A count of the number of OAMPDUs received on this interface with an unsupported op-code. | Yes ( Though SLX-OS and MLX doesn't send this they are capable to receive such PDU and update the counter) | |
| dot3OamFramesLostDueToOam
OID: dot3OamStatsEntry .17 SYNTAX: Counter32 MAX-ACCESS: Read Only |
A count of the number of frames that were dropped by the OA multiplexer | Yes |
| MIB object , OID , Syntax , MAX-ACCESS | Description | Possible values | Supported (Yes/No) |
|---|---|---|---|
| dot3OamErrSymPeriodWindowHi
OID: dot3OamEventConfigEntry .1 SYNTAX: Unsigned32 MAX-ACCESS: Read Only |
The two objects dot3OamErrSymPeriodWindowHi anddot3OamErrSymPeriodLo together form an unsigned 64-bit integer representing the number of symbols over which this threshold event is defined. This is defined as dot3OamErrSymPeriodWindow = ((2^32)*dot3OamErrSymPeriodWindowHi)+ dot3OamErrSymPeriodWindowLoIf dot3OamErrSymPeriodThreshold symbol errors occur within a window of dot3OamErrSymPeriodWindow symbols, an Event Notification OAMPDU should be generated with an Errored SymbolPeriod Event TLV indicating that the threshold has been crossed in this window. The default value for dot3OamErrSymPeriodWindow is the number of symbols in one second for the underlying physical layer. | No | |
| dot3OamErrSymPeriodWindowLo
OID: dot3OamEventConfigEntry .2 SYNTAX: Unsigned32 MAX-ACCESS: Read Only |
The two objects dot3OamErrSymPeriodWindowHi anddot3OamErrSymPeriodWindowLo together form an unsigned 64-bit integer representing the number of symbols over which this threshold event is defined. This is defined asdot3OamErrSymPeriodWindow = ((2^32)*dot3OamErrSymPeriodWindowHi)+ dot3OamErrSymPeriodWindowLoIf dot3OamErrSymPeriodThreshold symbol errors occur within a window of dot3OamErrSymPeriodWindow symbols, an Event Notification OAMPDU should be generated with an Errored SymbolPeriod Event TLV indicating that the threshold has been crossed in this window. The default value for dot3OamErrSymPeriodWindow is the number of symbols in one second for the underlying physical layer. | No | |
| dot3OamErrSymPeriodThresholdHi
OID: dot3OamEventConfigEntry .3 SYNTAX: Unsigned32 MAX-ACCESS: Read Only |
The two objects dot3OamErrSymPeriodThresholdHi anddot3OamErrSymPeriodThresholdLo together form an unsigned 64-bit integer representing the number of symbol errors that must occur within a given window to cause this event. This is defined asdot3OamErrSymPeriodThreshold =((2^32) * dot3OamErrSymPeriodThresholdHi)+ dot3OamErrSymPeriodThresholdLoIf dot3OamErrSymPeriodThreshold symbol errors occur within a window of dot3OamErrSymPeriodWindow symbols, an Event Notification OAMPDU should be generated with an Errored SymbolPeriod Event TLV indicating that the threshold has been crossed in this window. The default value for dot3OamErrSymPeriodThreshold is one symbol errors. If the threshold value is zero, then an Event Notification OAMPDU is sent periodically (at the end of every window). This can be used as an asynchronous notification to the peer OAM entity of the statistics related to this threshold crossing alarm. | No | |
| dot3OamErrSymPeriodThresholdLo
OID: dot3OamEventConfigEntry .4 SYNTAX: Unsigned32 MAX-ACCESS: Read Only |
The two objects dot3OamErrSymPeriodThresholdHi and dot3OamErrSymPeriodThresholdLo together form an unsigned 64-bit integer representing the number of symbol errors that must occur within a given window to cause this event. This is defined asdot3OamErrSymPeriodThreshold =((2^32) * dot3OamErrSymPeriodThresholdHi)+ dot3OamErrSymPeriodThresholdLoIf dot3OamErrSymPeriodThreshold symbol errors occur within a window of dot3OamErrSymPeriodWindow symbols, an Event Notification OAMPDU should be generated with an Errored SymbolPeriod Event TLV indicating that the threshold has been crossed in this window. The default value for dot3OamErrSymPeriodThreshold is one symbol error. If the threshold value is zero, then an Event Notification OAMPDU is sent periodically (at the end of every window). This can be used as an asynchronous notification to the peer OAM entity of the statistics related to this threshold crossing alarm. | No | |
| dot3OamErrSymPeriodEvNotifEnable
OID: dot3OamEventConfigEntry .5 SYNTAX: TruthValue MAX-ACCESS: Read Only |
If true, the OAM entity should send an Event Notification OAMPDU when an Errored Symbol Period Event occurs.By default, this object should have the value true for Ethernet-like interfaces that support OAM. If the OAM layer does not support Event Notifications (as indicated via the dot3OamFunctionsSupported attribute), this value is ignored | No - with default value | |
| dot3OamErrFramePeriodWindow
OID: dot3OamEventConfigEntry .6 SYNTAX: Unsigned32 MAX-ACCESS: Read Only |
The number of frames over which the threshold is defined. The default value of the window is the number of minimum size Ethernet frames that can be received over the physical layer in one second. If dot3OamErrFramePeriodThreshold frame errors occur within a window of dot3OamErrFramePeriodWindow frames, an Event Notification OAMPDU should be generated with an Errored Frame Period Event TLV indicating that the threshold has been crossed in this window | No | |
| dot3OamErrFramePeriodThreshold
OID: dot3OamEventConfigEntry .7 SYNTAX: Unsigned32 MAX-ACCESS: Read Only |
The number of frame errors that must occur for this event to be triggered. The default value is one frame error. If the threshold value is zero, then an Event Notification OAMPDU is sent periodically (at the end of every window). This can be used as an asynchronous notification to the peer OAM entity of the statistics related to this threshold crossing alarm. If dot3OamErrFramePeriodThreshold frame errors occur within a window of dot3OamErrFramePeriodWindow frames, an Event Notification OAMPDU should be generated with an Errored Frame Period Event TLV indicating that the threshold has been crossed in this window. | No | |
| dot3OamErrFramePeriodEvNotifEnable
OID: dot3OamEventConfigEntry .8 SYNTAX: TruthValue MAX-ACCESS: Read Only |
If true, the OAM entity should send an Event Notification OAMPDU when an Errored Frame Period Event occurs.By default, this object should have the value true for Ethernet-like interfaces that support OAM. If the OAM layer not support Event Notifications (as indicated via the dot3OamFunctionsSupported attribute), this value is ignored | True(1) False(2) | No- with default value False |
| dot3OamErrFrameWindow
OID: dot3OamEventConfigEntry .9 SYNTAX: Unsigned32 MAX-ACCESS: Read Only |
The amount of time (in 100ms increments) over which the threshold is defined. The default value is 10 (1 second). If dot3OamErrFrameThreshold frame errors occur within a window of dot3OamErrFrameWindow seconds (measured in tenths of seconds), an Event Notification OAMPDU should be generated with an Errored Frame Event TLV indicating that the threshold has been crossed in this window | No | |
| dot3OamErrFrameThreshold
OID: dot3OamEventConfigEntry .10 SYNTAX: Unsigned32 MAX-ACCESS: Read Only |
A count of the number of Variable Response OAMPDUs received on this interface The number of frame errors that must occur for this event to be triggered. The default value is one frame error. If the threshold value is zero, then an Event Notification OAMPDU is sent periodically (at the end of every window). This can be used as an asynchronous notification to the peer OAM entity of the statistics related to this threshold crossing alarm. If dot3OamErrFrameThreshold frame errors occur within a window of dot3OamErrFrameWindow (in tenths of seconds), an Event Notification OAMPDU should be generated with an Errored Frame Event TLV indicating the threshold has been crossed in this window. | No | |
| dot3OamErrFrameEvNotifEnable
OID: dot3OamEventConfigEntry .11 SYNTAX: TruthValue MAX-ACCESS: Read Only |
If true, the OAM entity should send an Event Notification OAMPDU when an Errored Frame Event occurs. By default, this object should have the value true fo rEthernet-like interfaces that support OAM. If the OAM layer does not support Event Notifications (as indicated via the dot3OamFunctionsSupported attribute), this value is ignored. | True(1) False(2) | No with default value false |
| dot3OamErrFrameSecsSummaryWindow
OID: dot3OamEventConfigEntry .12 SYNTAX: Integer32 MAX-ACCESS: Read Only |
The amount of time (in 100 ms intervals) over which the threshold is defined. The default value is 100 (10 seconds).If dot3OamErrFrameSecsSummaryThreshold frame errors occur within a window of dot3OamErrFrameSecsSummaryWindow (in tenths of seconds), an Event Notification OAMPDU should be generated with an Errored Frame Seconds Summary Event TLV indicating that the threshold has been crossed in this window | No | |
| dot3OamErrFrameSecsSummaryThreshold
OID: dot3OamEventConfigEntry .13 SYNTAX: Integer32 MAX-ACCESS: Read Only |
The number of errored frame seconds that must occur for this event to be triggered. The default value is one errored frame second. If the threshold value is zero, then an Event Notification OAMPDU is sent periodically (at the end of every window). This can be used as an asynchronous notification to the peer OAM entity of the statistics related to this threshold crossing alarm. If dot3OamErrFrameSecsSummaryThreshold frame errors occur within a window of dot3OamErrFrameSecsSummaryWindow (in tenths of seconds), an Event Notification OAMPDU should be generated with an Errored Frame Seconds Summary Event TLV indicating that the threshold has been crossed in this window | No | |
| dot3OamErrFrameSecsEvNotifEnable
OID: dot3OamEventConfigEntry .14 SYNTAX: TruthValue MAX-ACCESS: Read Only |
If true, the local OAM entity should send an Event Notification OAMPDU when an Errored Frame Seconds Event occurs. By default, this object should have the value true for Ethernet-like interfaces that support OAM. If the OAM layer does not support Event Notifications (as indicated via the dot3OamFunctionsSupported attribute), this value is ignored | True(1) False(2) | No -with default value false |
| dot3OamDyingGaspEnable
OID: dot3OamEventConfigEntry .15 SYNTAX: TruthValue MAX-ACCESS: Read Only |
If true, the local OAM entity should attempt to indicate a dying gasp via the OAMPDU flags field to its peer OAM entity when a dying gasp event occurs. The exact definition of a dying gasp event is implementation dependent. If the system does not support dying gasp capability, setting this object has no effect, and reading the object should always result in 'false' By default, this object should have the value true for Ethernet-like interfaces that support OAM. If the OAM layer does not support Event Notifications (as indicated via thedot3OamFunctionsSupported attribute), this value is ignored | True(1) False(2) | Yes , and in the back end code its always set to True. There is no way to test False case of this |
| dot3OamCriticalEventEnable
OID: dot3OamEventConfigEntry .16 SYNTAX: TruthValue MAX-ACCESS: Read Only |
If true, the local OAM entity should attempt to indicate a critical event via the OAMPDU flags to its peer OAM entity when a critical event occurs. The exact definition of a critical event is implementation dependent. If the system does not support critical event capability, setting this object has no effect, and reading the object should always result in 'false'. By default, this object should have the value true for Ethernet-like interfaces that support OAM. If the OAM layer does not support Event Notifications (as indicated via the dot3OamFunctionsSupported attribute), this value is ignored. | True(1) False(2) | Yes , and in the back end code its always set to True.There is no way to test False case of this |
| MIB object , OID , Syntax, MAX-ACCESS | Description | Possible values | Supported (Yes/No) |
|---|---|---|---|
| dot3OamEventLogIndex
OID: dot3OamEventLogEntry .1 SYNTAX: Unsigned32 MAX-ACCESS: Read Only |
An arbitrary integer for identifying individual events within the event log | (1..4294967295) | Yes(Not Accessible) |
| dot3OamEventLogTimestamp
OID: dot3OamEventLogEntry .2 SYNTAX: TIMESTAMP MAX-ACCESS: Read Only |
The value of sysUpTime at the time of the logged event. For locally generated events, the time of the event can be accurately retrieved from sysUpTime .For remotely generated events, the time of the event is indicated by the reception of the Event Notification OAMPDU indicating that the event occurred on the peer. A system may attempt to adjust the timestamp value to more accurately reflect the time of the event at the peer OAM entity by using other information, such as that found in the timestamp found of the Event Notification TLVs, which provides an indication of the relative time between events at the peer entity. | Yes | |
| dot3OamEventLogOui
OID: dot3OamEventLogEntry .3 SYNTAX:EightOTwoOui MAX-ACCESS: Read Only |
The OUI of the entity defining the object type. All IEEE.3 defined events (as appearing in [802.3ah] except for the Organizationally Unique Event TLVs) use the IEEE 802.3 OUI of0x0180C2. Organizations defining their own Event NotificationTLVs include their OUI in the Event Notification TLV that gets reflected here. | Yes | |
| dot3OamEventLogType
OID: dot3OamEventLogEntry .4 SYNTAX:Unsigned32 MAX-ACCESS: Read Only |
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 types are defined:erroredSymbolEvent(1),erroredFramePeriodEvent(2),erroredFrameEvent(3),erroredFrameSecondsEvent(4),linkFault(256),dyingGaspEvent(257),criticalLinkEvent(258)The first four are considered threshold crossing events, as they are generated when a metric exceeds a given value within a specified window. The other three are not threshold crossing events. When the OUI is not 71874 (0x0180C2 in hex), then some other organization has defined the event space. If event subtyping is known to the implementation, it may be reflected here. Otherwise, this value should return all F's (2^32 - 1). | Yes. SLX-OS supports only 3 events in this. linkFault(256), dyingGaspEvent(257), criticalLinkEvent(258) | |
| dot3OamEventLogLocation
OID: dot3OamEventLogEntry .5 SYNTAX:INTEGER MAX-ACCESS: Read Only |
Whether this event occurred locally (local(1)), or was received from the OAM peer via Ethernet OAM (remote(2)) | local(1), remote(2) | Yes |
| dot3OamEventLogWindowHi
OID: dot3OamEventLogEntry .6 SYNTAX:Unsigned32 MAX-ACCESS: Read Only |
If the event represents a threshold crossing event, the two objects dot3OamEventWindowHi and dot3OamEventWindowLo, form an unsigned 64-bit integer yielding the window over which the value was measured for the threshold crossing event (for example, 5, when 11 occurrences happened in 5 seconds while the threshold was 10). The two objects are combined as: dot3OamEventLogWindow = ((2^32) * dot3OamEventLogWindowHi)+ dot3OamEventLogWindowLoOtherwise, this value is returned as all F's (2^32 - 1) and adds no useful information. | No | |
| dot3OamEventLogWindowLo
OID: dot3OamEventLogEntry .7 SYNTAX:Unsigned32 MAX-ACCESS: Read Only |
If the event represents a threshold crossing event, the two objects dot3OamEventWindowHi and dot3OamEventWindowLo form an unsigned 64-bit integer yielding the window over which the value was measured for the threshold crossing event (for example, 5, when 11 occurrences happened in 5 seconds while the threshold was 10). The two objects are combined as:dot3OamEventLogWindow = ((2^32) * dot3OamEventLogWindowHi)+ dot3OamEventLogWindowLoOtherwise, this value is returned as all F's (2^32 - 1) and no useful information. | No | |
| dot3OamEventLogThresholdHi
OID: dot3OamEventLogEntry .8 SYNTAX:Unsigned32 MAX-ACCESS: Read Only |
If the event represents a threshold crossing event, the two objects dot3OamEventThresholdHi and dot3OamEventThresholdLo form an unsigned 64-bit integer yielding the value that was crossed for the threshold crossing event (for example, 10, when 11 occurrences happened in 5 seconds while the threshold was 10). The two objects are combined as:dot3OamEventLogThreshold = ((2^32) * dot3OamEventLogThresholdHi)+ dot3OamEventLogThresholdLoOtherwise, this value is returned as all F's (2^32 -1) and adds no useful information. | No | |
| dot3OamEventLogThresholdLo
OID: dot3OamEventLogEntry .9 SYNTAX:Unsigned32 MAX-ACCESS: Read Only |
If the event represents a threshold crossing event, the two objects dot3OamEventThresholdHi and dot3OamEventThresholdLo form an unsigned 64-bit integer yielding the value that was crossed for the threshold crossing event (for example, 10, when 11 occurrences happened in 5 seconds while the threshold was 10). The two objects are combined as:dot3OamEventLogThreshold = ((2^32) * dot3OamEventLogThresholdHi)+ dot3OamEventLogThresholdLoOtherwise, this value is returned as all F's (2^32 - 1) and adds no useful information. | No | |
| dot3OamEventLogValue
OID: dot3OamEventLogEntry .10 SYNTAX:CounterBasedGauge64 MAX-ACCESS: Read Only |
If the event represents a threshold crossing event, this value indicates the value of the parameter within the given window that generated this event (for example, 11, when 11Occurrences happened in 5 seconds while the threshold was 10).Otherwise, this value is returned as all F's (2^64 - 1) and adds no useful information | Yes. SLX-OS supports only non-threshold events .For such events this MIB objects expects 1's in all bits | |
| dot3OamEventLogRunningTotal
OID: dot3OamEventLogEntry .11 SYNTAX:CounterBasedGauge64 MAX-ACCESS: Read Only |
Each Event Notification TLV contains a running total of the number of times an event has occurred, as well as the number of times an Event Notification for the event has been transmitted. For non-threshold crossing events, the number of events (dot3OamLogRunningTotal) and the number of resultant Event Notifications (dot3OamLogEventTotal) should be identical. For threshold crossing events, since multiple occurrences may be required to cross the threshold, these values are likely different. This value represents the total number of times this event has happened since the last reset (for example, 3253, when 3253 symbol errors have occurred since the last reset, which has resulted in 51 symbol error threshold crossing events since the last reset). | Yes.
Note: SLX-OS supports only non threshold events |
|
| dot3OamEventLogEventTotal
OID: dot3OamEventLogEntry .12 SYNTAX:Unsigned32 MAX-ACCESS: Read Only |
Each Event Notification TLV contains a running total of the number of times an event has occurred, as well as the number of times an Event Notification for the event has been transmitted. For non-threshold crossing events, the number of events (dot3OamLogRunningTotal) and the number of resultant Event Notifications (dot3OamLogEventTotal) should be identical. For threshold crossing events, since multiple occurrences may be required to cross the threshold, these values are likely different. This value represents the total number of timesone or more of these occurrences have resulted in an Event Notification (for example, 51 when 3253 symbol errors have occurred since the last reset, which has resulted in 51 symbolerror threshold crossing events since the last reset) | Yes.
Note: SLX-OS supports only non threshold events |
| Notification, OID | Object | Description | Supported (Yes/No) |
|---|---|---|---|
| dot3OamThresholdEvent
OID: 1.3.6.1.2.1.158.0.1 |
dot3OamEventLogTimestamp, dot3OamEventLogOui, dot3OamEventLogType, dot3OamEventLogLocation, dot3OamEventLogWindowHi, dot3OamEventLogWindowLo, dot3OamEventLogThresholdHi, dot3OamEventLogThresholdLo, dot3OamEventLogValue, dot3OamEventLogRunningTotal, dot3OamEventLogEventTotal | A dot3OamThresholdEvent 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 that indicates a threshold event. This notification should not be sent more than once perSecond. 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 in thedot3OamEventLogTable. | No |
| dot3OamNonThresholdEvent
OID: 1.3.6.1.2.1.158.0.2 |
dot3OamEventLogTimestamp, dot3OamEventLogOui, dot3OamEventLogType, dot3OamEventLogLocation, dot3OamEventLogEventTotal | A dot3OamNonThresholdEvent 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 that indicates 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 variable bindings. The objects in the notification correspond to the values in a row instance of the dot3OamEventLogTable. | Yes. SLX OS sends traps with the var binds mentioned in column 2 for only the below eventsremotelinkFault,remotedyingGaspEvent,remotecriticalLinkEventlocalDyingGaspEvent |