cdot3OamErrFrameSecsEvNotifEnable - Cisco DOT3 Oam Error Frame Secs Event Notification Enable - CISCO-DOT3-OAM-MIB

MIBs list

With IPHost Network Monitor you can run simple snmp requests against a Cisco device in your network.

cdot3OamErrFrameSecsEvNotifEnable

Cisco DOT3 Oam Error Frame Secs Event Notification Enable
1.3.6.1.4.1.9.10.136.1.5.1.14

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 cdot3OamFunctionsSupported attribute), this value is ignored. ::= { cdot3OamEventConfigEntry 14 } SYNTAX TruthValue MAX-ACCESS read-write STATUS current DESCRIPTION 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 the cdot3OamFunctionsSupported attribute), this value is ignored. ::= { cdot3OamEventConfigEntry 15 } SYNTAX TruthValue MAX-ACCESS read-write STATUS current DESCRIPTION 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 cdot3OamFunctionsSupported attribute), this value is ignored. ::= { cdot3OamEventConfigEntry 16 } -- ************************************************************** -- -- Ethernet OAM Event Log group -- SYNTAX SEQUENCE OF Cdot3OamEventLogEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION This table records a history of the events that have occurred at the Ethernet OAM level. These events can include locally detected events, which may result in locally generated OAMPDUs, and remotely detected events, which are detected by the OAM peer entity and signaled to the local entity via Ethernet OAM. Ethernet OAM events can be signaled by Event Notification OAMPDUs or by the flags field in any OAMPDU. This table contains both threshold crossing events and non-threshold crossing events. The parameters for the threshold window, threshold value, and actual value (cdot3OamEventLogWindowXX, cdot3OamEventLogThresholdXX, cdot3OamEventLogValue) are only applicable to threshold crossing events, and are returned as all F's (2^32 - 1) for non-threshold crossing events. Entries in the table are automatically created when such events are detected. The size of the table is implementation dependent. When the table reaches its maximum size, older entries are automatically deleted to make room for newer entries. ::= { cdot3OamObjects 6 } SYNTAX Cdot3OamEventLogEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION An entry in the cdot3OamEventLogTable. Entries are automatically created whenever Ethernet OAM events occur at the local OAM entity, and when Event Notification OAMPDUs are received at the local OAM entity (indicating events have occurred at the peer OAM entity). The size of the table is implementation dependent, but when the table becomes full, older events are automatically deleted to make room for newer events. The table index cdot3OamEventLogIndex increments for each new entry, and when the maximum value is reached the value restarts at zero. INDEX { ifIndex, cdot3OamEventLogIndex } ::= { cdot3OamEventLogTable 1 } Cdot3OamEventLogEntry ::= SEQUENCE { cdot3OamEventLogIndex Unsigned32, cdot3OamEventLogTimestamp TimeStamp, cdot3OamEventLogOui Cdot3Oui, cdot3OamEventLogType Unsigned32, cdot3OamEventLogLocation INTEGER, cdot3OamEventLogWindowHi Unsigned32, cdot3OamEventLogWindowLo Unsigned32, cdot3OamEventLogThresholdHi Unsigned32, cdot3OamEventLogThresholdLo Unsigned32, cdot3OamEventLogValue CounterBasedGauge64, cdot3OamEventLogRunningTotal CounterBasedGauge64, cdot3OamEventLogEventTotal Unsigned32 } SYNTAX Unsigned32 MAX-ACCESS not-accessible STATUS current DESCRIPTION An arbitrary integer for identifying individual events within the event log.

Back to CISCO-DOT3-OAM-MIB MIB page.

IPHost Network monitor allows you to monitor cdot3OamErrFrameSecsEvNotifEnable on Cisco device via the SNMP protocol. Download IPHost Network Monitor (500 monitors for 30 days, 50 monitors free forever) to start monitoring Cisco mobile switches right now.

Easy monitoring of cdot3OamErrFrameSecsEvNotifEnable with IPHost tools

MIBs list