Reference record for OID 1.3.6.1.4.1.9.10.136.1.5


parent
1.3.6.1.4.1.9.10.136.1 (cdot3OamObjects)
node code
5
node name
cdot3OamEventConfigTable
dot oid
1.3.6.1.4.1.9.10.136.1.5
type
OBJECT-TYPE
asn1 oid
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) cisco(9) ciscoExperiment(10) cdot3OamMIB(136) cdot3OamObjects(1) cdot3OamEventConfigTable(5)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) cisco(9) ciscoExperiment(10) cdot3OamMIB(136) cdot3OamObjects(1) cdot3OamEventConfigTable(5)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) cisco(9) ciscoExperiment(10) cdot3OamMIB(136) cdot3OamObjects(1) cdot3OamEventConfigTable(5)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) cisco(9) ciscoExperiment(10) cdot3OamMIB(136) cdot3OamObjects(1) cdot3OamEventConfigTable(5)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprise(1) cisco(9) ciscoExperiment(10) cdot3OamMIB(136) cdot3OamObjects(1) cdot3OamEventConfigTable(5)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprises(1) cisco(9) ciscoExperiment(10) cdot3OamMIB(136) cdot3OamObjects(1) cdot3OamEventConfigTable(5)}
  • iri oid
  • /iso/identified-organization/dod/internet/private/enterprise/cisco/ciscoExperiment/cdot3OamMIB/cdot3OamObjects/cdot3OamEventConfigTable
  • /iso/identified-organization/dod/internet/private/enterprises/cisco/ciscoExperiment/cdot3OamMIB/cdot3OamObjects/cdot3OamEventConfigTable
  • /iso/org/dod/internet/private/enterprise/cisco/ciscoExperiment/cdot3OamMIB/cdot3OamObjects/cdot3OamEventConfigTable
  • /iso/org/dod/internet/private/enterprises/cisco/ciscoExperiment/cdot3OamMIB/cdot3OamObjects/cdot3OamEventConfigTable
  • /iso/iso-identified-organization/dod/internet/private/enterprise/cisco/ciscoExperiment/cdot3OamMIB/cdot3OamObjects/cdot3OamEventConfigTable
  • /iso/iso-identified-organization/dod/internet/private/enterprises/cisco/ciscoExperiment/cdot3OamMIB/cdot3OamObjects/cdot3OamEventConfigTable
  • iri by oid_info
    /ISO/Identified-Organization/6/1/4/1/9/10/136/1/5

    Description by circitor

    Ethernet OAM includes the ability to generate and receive
    Event Notification OAMPDUs to indicate various link problems.
    This table contains the mechanisms to enable Event
    Notifications and configure the thresholds to generate the
    standard Ethernet OAM events. There is one entry in the table
    for every entry in cdot3OamTable that supports OAM events
    (where cdot3OamFunctionsSupported includes the eventSupport
    bit set). The values in the table are maintained across
    changes to cdot3OamOperStatus.

    The standard threshold crossing events are:
    - Errored Symbol Period Event. Generated when the number of
    symbol errors exceeds a threshold within a given window
    defined by a number of symbols (for example, 1,000 symbols
    out of 1,000,000 had errors).
    - Errored Frame Period Event. Generated when the number of
    frame errors exceeds a threshold within a given window
    defined by a number of frames (for example, 10 frames out
    of 1000 had errors).
    - Errored Frame Event. Generated when the number of frame
    errors exceeds a threshold within a given window defined
    by a period of time (for example, 10 frames in 1 second
    had errors).
    - Errored Frame Seconds Summary Event. Generated when the
    number of errored frame seconds exceeds a threshold within
    a given time period (for example, 10 errored frame seconds
    within the last 100 seconds). An errored frame second is
    defined as a 1 second interval which had >0 frame errors.
    There are other events (dying gasp, critical events) that are
    not threshold crossing events but which can be
    enabled/disabled via this table.

    Parsed from file CISCO-DOT3-OAM-MIB.mib
    Module: CISCO-DOT3-OAM-MIB

    Description by cisco_v1

    Ethernet OAM includes the ability to generate and receive
    Event Notification OAMPDUs to indicate various link problems.
    This table contains the mechanisms to enable Event
    Notifications and configure the thresholds to generate the
    standard Ethernet OAM events. There is one entry in the table
    for every entry in cdot3OamTable that supports OAM events
    (where cdot3OamFunctionsSupported includes the eventSupport
    bit set). The values in the table are maintained across
    changes to cdot3OamOperStatus.

    The standard threshold crossing events are:
    - Errored Symbol Period Event. Generated when the number of
    symbol errors exceeds a threshold within a given window
    defined by a number of symbols (for example, 1,000 symbols
    out of 1,000,000 had errors).
    - Errored Frame Period Event. Generated when the number of
    frame errors exceeds a threshold within a given window
    defined by a number of frames (for example, 10 frames out
    of 1000 had errors).
    - Errored Frame Event. Generated when the number of frame
    errors exceeds a threshold within a given window defined
    by a period of time (for example, 10 frames in 1 second
    had errors).
    - Errored Frame Seconds Summary Event. Generated when the
    number of errored frame seconds exceeds a threshold within
    a given time period (for example, 10 errored frame seconds
    within the last 100 seconds). An errored frame second is
    defined as a 1 second interval which had >0 frame errors.
    There are other events (dying gasp, critical events) that are
    not threshold crossing events but which can be
    enabled/disabled via this table.

    Description by mibdepot

    Ethernet OAM includes the ability to generate and receive
    Event Notification OAMPDUs to indicate various link problems.
    This table contains the mechanisms to enable Event
    Notifications and configure the thresholds to generate the
    standard Ethernet OAM events. There is one entry in the table
    for every entry in cdot3OamTable that supports OAM events
    (where cdot3OamFunctionsSupported includes the eventSupport
    bit set). The values in the table are maintained across
    changes to cdot3OamOperStatus.

    The standard threshold crossing events are:
    - Errored Symbol Period Event. Generated when the number of
    symbol errors exceeds a threshold within a given window
    defined by a number of symbols (for example, 1,000 symbols
    out of 1,000,000 had errors).
    - Errored Frame Period Event. Generated when the number of
    frame errors exceeds a threshold within a given window
    defined by a number of frames (for example, 10 frames out
    of 1000 had errors).
    - Errored Frame Event. Generated when the number of frame
    errors exceeds a threshold within a given window defined
    by a period of time (for example, 10 frames in 1 second
    had errors).
    - Errored Frame Seconds Summary Event. Generated when the
    number of errored frame seconds exceeds a threshold within
    a given time period (for example, 10 errored frame seconds
    within the last 100 seconds). An errored frame second is
    defined as a 1 second interval which had >0 frame errors.
    There are other events (dying gasp, critical events) that are
    not threshold crossing events but which can be
    enabled/disabled via this table.

    Parsed from file CISCO-DOT3-OAM-MIB.my.txt
    Company: None
    Module: CISCO-DOT3-OAM-MIB

    Description by cisco

    Ethernet OAM includes the ability to generate and receive
    Event Notification OAMPDUs to indicate various link problems.
    This table contains the mechanisms to enable Event
    Notifications and configure the thresholds to generate the
    standard Ethernet OAM events. There is one entry in the table
    for every entry in cdot3OamTable that supports OAM events
    (where cdot3OamFunctionsSupported includes the eventSupport
    bit set). The values in the table are maintained across
    changes to cdot3OamOperStatus.

    The standard threshold crossing events are:
    - Errored Symbol Period Event. Generated when the number of
    symbol errors exceeds a threshold within a given window
    defined by a number of symbols (for example, 1,000 symbols
    out of 1,000,000 had errors).
    - Errored Frame Period Event. Generated when the number of
    frame errors exceeds a threshold within a given window
    defined by a number of frames (for example, 10 frames out
    of 1000 had errors).
    - Errored Frame Event. Generated when the number of frame
    errors exceeds a threshold within a given window defined
    by a period of time (for example, 10 frames in 1 second
    had errors).
    - Errored Frame Seconds Summary Event. Generated when the
    number of errored frame seconds exceeds a threshold within
    a given time period (for example, 10 errored frame seconds
    within the last 100 seconds). An errored frame second is
    defined as a 1 second interval which had >0 frame errors.
    There are other events (dying gasp, critical events) that are
    not threshold crossing events but which can be
    enabled/disabled via this table.

    Information by circitor

    cdot3OamEventConfigTable OBJECT-TYPE SYNTAX SEQUENCE OF Cdot3OamEventConfigEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "Ethernet OAM includes the ability to generate and receive Event Notification OAMPDUs to indicate various link problems. This table contains the mechanisms to enable Event Notifications and configure the thresholds to generate the standard Ethernet OAM events. There is one entry in the table for every entry in cdot3OamTable that supports OAM events (where cdot3OamFunctionsSupported includes the eventSupport bit set). The values in the table are maintained across changes to cdot3OamOperStatus. The standard threshold crossing events are: - Errored Symbol Period Event. Generated when the number of symbol errors exceeds a threshold within a given window defined by a number of symbols (for example, 1,000 symbols out of 1,000,000 had errors). - Errored Frame Period Event. Generated when the number of frame errors exceeds a threshold within a given window defined by a number of frames (for example, 10 frames out of 1000 had errors). - Errored Frame Event. Generated when the number of frame errors exceeds a threshold within a given window defined by a period of time (for example, 10 frames in 1 second had errors). - Errored Frame Seconds Summary Event. Generated when the number of errored frame seconds exceeds a threshold within a given time period (for example, 10 errored frame seconds within the last 100 seconds). An errored frame second is defined as a 1 second interval which had >0 frame errors. There are other events (dying gasp, critical events) that are not threshold crossing events but which can be enabled/disabled via this table. " ::= { cdot3OamObjects 5 }

    Information by cisco_v1

    cdot3OamEventConfigTable OBJECT-TYPE SYNTAX SEQUENCE OF Cdot3OamEventConfigEntry ACCESS not-accessible STATUS mandatory DESCRIPTION "Ethernet OAM includes the ability to generate and receive Event Notification OAMPDUs to indicate various link problems. This table contains the mechanisms to enable Event Notifications and configure the thresholds to generate the standard Ethernet OAM events. There is one entry in the table for every entry in cdot3OamTable that supports OAM events (where cdot3OamFunctionsSupported includes the eventSupport bit set). The values in the table are maintained across changes to cdot3OamOperStatus. The standard threshold crossing events are: - Errored Symbol Period Event. Generated when the number of symbol errors exceeds a threshold within a given window defined by a number of symbols (for example, 1,000 symbols out of 1,000,000 had errors). - Errored Frame Period Event. Generated when the number of frame errors exceeds a threshold within a given window defined by a number of frames (for example, 10 frames out of 1000 had errors). - Errored Frame Event. Generated when the number of frame errors exceeds a threshold within a given window defined by a period of time (for example, 10 frames in 1 second had errors). - Errored Frame Seconds Summary Event. Generated when the number of errored frame seconds exceeds a threshold within a given time period (for example, 10 errored frame seconds within the last 100 seconds). An errored frame second is defined as a 1 second interval which had >0 frame errors. There are other events (dying gasp, critical events) that are not threshold crossing events but which can be enabled/disabled via this table. " ::= { cdot3OamObjects 5 }

    Information by oid_info

    Vendor: Cisco
    Module: CISCO-DOT3-OAM-MIB

    [Automatically extracted from oidview.com]

    Information by mibdepot

    cdot3OamEventConfigTable OBJECT-TYPE SYNTAX SEQUENCE OF Cdot3OamEventConfigEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "Ethernet OAM includes the ability to generate and receive Event Notification OAMPDUs to indicate various link problems. This table contains the mechanisms to enable Event Notifications and configure the thresholds to generate the standard Ethernet OAM events. There is one entry in the table for every entry in cdot3OamTable that supports OAM events (where cdot3OamFunctionsSupported includes the eventSupport bit set). The values in the table are maintained across changes to cdot3OamOperStatus. The standard threshold crossing events are: - Errored Symbol Period Event. Generated when the number of symbol errors exceeds a threshold within a given window defined by a number of symbols (for example, 1,000 symbols out of 1,000,000 had errors). - Errored Frame Period Event. Generated when the number of frame errors exceeds a threshold within a given window defined by a number of frames (for example, 10 frames out of 1000 had errors). - Errored Frame Event. Generated when the number of frame errors exceeds a threshold within a given window defined by a period of time (for example, 10 frames in 1 second had errors). - Errored Frame Seconds Summary Event. Generated when the number of errored frame seconds exceeds a threshold within a given time period (for example, 10 errored frame seconds within the last 100 seconds). An errored frame second is defined as a 1 second interval which had >0 frame errors. There are other events (dying gasp, critical events) that are not threshold crossing events but which can be enabled/disabled via this table. " ::= { cdot3OamObjects 5 }

    Information by cisco

    cdot3OamEventConfigTable OBJECT-TYPE SYNTAX SEQUENCE OF Cdot3OamEventConfigEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "Ethernet OAM includes the ability to generate and receive Event Notification OAMPDUs to indicate various link problems. This table contains the mechanisms to enable Event Notifications and configure the thresholds to generate the standard Ethernet OAM events. There is one entry in the table for every entry in cdot3OamTable that supports OAM events (where cdot3OamFunctionsSupported includes the eventSupport bit set). The values in the table are maintained across changes to cdot3OamOperStatus. The standard threshold crossing events are: - Errored Symbol Period Event. Generated when the number of symbol errors exceeds a threshold within a given window defined by a number of symbols (for example, 1,000 symbols out of 1,000,000 had errors). - Errored Frame Period Event. Generated when the number of frame errors exceeds a threshold within a given window defined by a number of frames (for example, 10 frames out of 1000 had errors). - Errored Frame Event. Generated when the number of frame errors exceeds a threshold within a given window defined by a period of time (for example, 10 frames in 1 second had errors). - Errored Frame Seconds Summary Event. Generated when the number of errored frame seconds exceeds a threshold within a given time period (for example, 10 errored frame seconds within the last 100 seconds). An errored frame second is defined as a 1 second interval which had >0 frame errors. There are other events (dying gasp, critical events) that are not threshold crossing events but which can be enabled/disabled via this table. " ::= { cdot3OamObjects 5 }

    First Registration Authority (recovered by parent 1.3.6.1.4.1.9)

    Greg Satz

    Current Registration Authority (recovered by parent 1.3.6.1.4.1.9)

    Cisco Systems, Inc.

    Children (1)

    OIDNameSub childrenSub Nodes TotalDescription
    1.3.6.1.4.1.9.10.136.1.5.1 cdot3OamEventConfigEntry 16 16 Entries are automatically created and deleted from this
    table, and exist whenever the OAM entity supports Ethernet OAM
    events (as…

    Brothers (5)

    OIDNameSub childrenSub Nodes TotalDescription
    1.3.6.1.4.1.9.10.136.1.1 cdot3OamTable 1 7 This table contains the primary controls and status for the
    OAM capabilities of an Ethernet like interface. There will be
    one ro…
    1.3.6.1.4.1.9.10.136.1.2 cdot3OamPeerTable 1 8 This table contains information about the OAM peer for a
    particular Ethernet like interface. OAM entities communicate
    with a sing…
    1.3.6.1.4.1.9.10.136.1.3 cdot3OamLoopbackTable 1 3 This table contains controls for the loopback state of the
    local link as well as indicating the status of the loopback
    function. …
    1.3.6.1.4.1.9.10.136.1.4 cdot3OamStatsTable 1 18 This table contains statistics for the OAM function on a
    particular Ethernet like interface. There is an entry in the
    table for e…
    1.3.6.1.4.1.9.10.136.1.6 cdot3OamEventLogTable 1 13 This table records a history of the events that have occurred
    at the Ethernet OAM level. These events can include locally
    detect…