Reference record for OID 1.3.6.1.2.1.88.1.2.4.1.1



parent
1.3.6.1.2.1.88.1.2.4.1 (mteTriggerExistenceEntry)
node code
1
node name
mteTriggerExistenceTest
dot oid
1.3.6.1.2.1.88.1.2.4.1.1
type
OBJECT-TYPE
asn1 oid
  • {iso(1) identified-organization(3) dod(6) internet(1) mgmt(2) mib-2(1) dismanEventMIB(88) dismanEventMIBObjects(1) mteTrigger(2) mteTriggerExistenceTable(4) mteTriggerExistenceEntry(1) mteTriggerExistenceTest(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) mgmt(2) mib(1) dismanEventMIB(88) dismanEventMIBObjects(1) mteTrigger(2) mteTriggerExistenceTable(4) mteTriggerExistenceEntry(1) mteTriggerExistenceTest(1)}
  • {iso(1) org(3) dod(6) internet(1) mgmt(2) mib-2(1) dismanEventMIB(88) dismanEventMIBObjects(1) mteTrigger(2) mteTriggerExistenceTable(4) mteTriggerExistenceEntry(1) mteTriggerExistenceTest(1)}
  • {iso(1) org(3) dod(6) internet(1) mgmt(2) mib(1) dismanEventMIB(88) dismanEventMIBObjects(1) mteTrigger(2) mteTriggerExistenceTable(4) mteTriggerExistenceEntry(1) mteTriggerExistenceTest(1)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) mgmt(2) mib-2(1) dismanEventMIB(88) dismanEventMIBObjects(1) mteTrigger(2) mteTriggerExistenceTable(4) mteTriggerExistenceEntry(1) mteTriggerExistenceTest(1)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) mgmt(2) mib(1) dismanEventMIB(88) dismanEventMIBObjects(1) mteTrigger(2) mteTriggerExistenceTable(4) mteTriggerExistenceEntry(1) mteTriggerExistenceTest(1)}
    • iri oid
  • /iso/identified-organization/dod/internet/mgmt/mib-2/dismanEventMIB/dismanEventMIBObjects/mteTrigger/mteTriggerExistenceTable/mteTriggerExistenceEntry/mteTriggerExistenceTest
  • /iso/identified-organization/dod/internet/mgmt/mib/dismanEventMIB/dismanEventMIBObjects/mteTrigger/mteTriggerExistenceTable/mteTriggerExistenceEntry/mteTriggerExistenceTest
  • /iso/org/dod/internet/mgmt/mib-2/dismanEventMIB/dismanEventMIBObjects/mteTrigger/mteTriggerExistenceTable/mteTriggerExistenceEntry/mteTriggerExistenceTest
  • /iso/org/dod/internet/mgmt/mib/dismanEventMIB/dismanEventMIBObjects/mteTrigger/mteTriggerExistenceTable/mteTriggerExistenceEntry/mteTriggerExistenceTest
  • /iso/iso-identified-organization/dod/internet/mgmt/mib-2/dismanEventMIB/dismanEventMIBObjects/mteTrigger/mteTriggerExistenceTable/mteTriggerExistenceEntry/mteTriggerExistenceTest
  • /iso/iso-identified-organization/dod/internet/mgmt/mib/dismanEventMIB/dismanEventMIBObjects/mteTrigger/mteTriggerExistenceTable/mteTriggerExistenceEntry/mteTriggerExistenceTest
    • iri by oid_info
    /ISO/Identified-Organization/6/1/2/1/88/1/2/4/1/1

    Description by circitor

    The type of existence test to perform. The trigger fires
    when the object at mteTriggerValueID is seen to go from
    present to absent, from absent to present, or to have it's
    value changed, depending on which tests are selected:

    present(0) - when this test is selected, the trigger fires
    when the mteTriggerValueID object goes from absent to present.

    absent(1) - when this test is selected, the trigger fires
    when the mteTriggerValueID object goes from present to absent.
    changed(2) - when this test is selected, the trigger fires
    the mteTriggerValueID object value changes.

    Once the trigger has fired for either presence or absence it
    will not fire again for that state until the object has been
    to the other state.

    Parsed from file DISMAN-EVENT-MIB.mib
    Module: DISMAN-EVENT-MIB

    Description by cisco_v1

    The type of existence test to perform. The trigger fires
    when the object at mteTriggerValueID is seen to go from
    present to absent, from absent to present, or to have it's
    value changed, depending on which tests are selected:

    present(0) - when this test is selected, the trigger fires
    when the mteTriggerValueID object goes from absent to present.

    absent(1) - when this test is selected, the trigger fires
    when the mteTriggerValueID object goes from present to absent.
    changed(2) - when this test is selected, the trigger fires
    the mteTriggerValueID object value changes.

    Once the trigger has fired for either presence or absence it
    will not fire again for that state until the object has been
    to the other state.

    Description by oid_info

    mteTriggerExistenceTest OBJECT-TYPE SYNTAX BITS { present(0), absent(1), changed(2) }
    MAX-ACCESS read-write
    STATUS current
    DESCRIPTION
    "The type of existence test to perform. The trigger fires
    when the object at mteTriggerValueID is seen to go from
    present to absent, from absent to present, or to have its
    value changed, depending on which tests are selected:
    present(0) - when this test is selected, the trigger fires
    when the mteTriggerValueID object goes from absent to present.
    absent(1) - when this test is selected, the trigger fires
    when the mteTriggerValueID object goes from present to absent.
    changed(2) - when this test is selected, the trigger fires
    the mteTriggerValueID object value changes.
    Once the trigger has fired for either presence or absence it
    will not fire again for that state until the object has been
    to the other state. "
    DEFVAL { { present, absent } }
    View at oid-info.com

    Description by mibdepot

    The type of existence test to perform. The trigger fires
    when the object at mteTriggerValueID is seen to go from
    present to absent, from absent to present, or to have it's
    value changed, depending on which tests are selected:

    present(0) - when this test is selected, the trigger fires
    when the mteTriggerValueID object goes from absent to present.

    absent(1) - when this test is selected, the trigger fires
    when the mteTriggerValueID object goes from present to absent.
    changed(2) - when this test is selected, the trigger fires
    the mteTriggerValueID object value changes.

    Once the trigger has fired for either presence or absence it
    will not fire again for that state until the object has been
    to the other state.

    Parsed from file rfc2981-Event.mib.txt
    Company: None
    Module: DISMAN-EVENT-MIB

    Description by cisco

    The type of existence test to perform. The trigger fires
    when the object at mteTriggerValueID is seen to go from
    present to absent, from absent to present, or to have it's
    value changed, depending on which tests are selected:

    present(0) - when this test is selected, the trigger fires
    when the mteTriggerValueID object goes from absent to present.

    absent(1) - when this test is selected, the trigger fires
    when the mteTriggerValueID object goes from present to absent.
    changed(2) - when this test is selected, the trigger fires
    the mteTriggerValueID object value changes.

    Once the trigger has fired for either presence or absence it
    will not fire again for that state until the object has been
    to the other state.

    Information by circitor

    mteTriggerExistenceTest OBJECT-TYPE
    SYNTAX      BITS { present(0), absent(1), changed(2) }
    MAX-ACCESS  read-write
    STATUS      current
    DESCRIPTION
        "The type of existence test to perform.  The trigger fires
        when the object at mteTriggerValueID is seen to go from
        present to absent, from absent to present, or to have it's
        value changed, depending on which tests are selected:

        present(0) - when this test is selected, the trigger fires
        when the mteTriggerValueID object goes from absent to present.

        absent(1)  - when this test is selected, the trigger fires
        when the mteTriggerValueID object goes from present to absent.
        changed(2) - when this test is selected, the trigger fires
        the mteTriggerValueID object value changes.

        Once the trigger has fired for either presence or absence it
        will not fire again for that state until the object has been
        to the other state. "
    DEFVAL { { present, absent } }
    ::= { mteTriggerExistenceEntry 1 }

    Information by cisco_v1

    mteTriggerExistenceTest OBJECT-TYPE
    SYNTAX OCTET STRING(SIZE(1..2))
        
        
        
        
    ACCESS read-write
    STATUS mandatory
    DESCRIPTION
        "The type of existence test to perform.  The trigger fires
        when the object at mteTriggerValueID is seen to go from
        present to absent, from absent to present, or to have it's
        value changed, depending on which tests are selected:
        
        present(0) - when this test is selected, the trigger fires
        when the mteTriggerValueID object goes from absent to present.
        
        absent(1)  - when this test is selected, the trigger fires
        when the mteTriggerValueID object goes from present to absent.
        changed(2) - when this test is selected, the trigger fires
        the mteTriggerValueID object value changes.
        
        Once the trigger has fired for either presence or absence it
        will not fire again for that state until the object has been
        to the other state. "
    DEFVAL { 'c0'h }
    ::= { mteTriggerExistenceEntry 1 }

    Information by oid_info

    Automatically extracted from RFC2981

    Information by mibdepot

    mteTriggerExistenceTest OBJECT-TYPE
    SYNTAX      BITS { present(0), absent(1), changed(2) }
    MAX-ACCESS  read-write
    STATUS      current
    DESCRIPTION
        "The type of existence test to perform.  The trigger fires
        when the object at mteTriggerValueID is seen to go from
        present to absent, from absent to present, or to have it's
        value changed, depending on which tests are selected:

        present(0) - when this test is selected, the trigger fires
        when the mteTriggerValueID object goes from absent to present.

        absent(1)  - when this test is selected, the trigger fires
        when the mteTriggerValueID object goes from present to absent.
        changed(2) - when this test is selected, the trigger fires
        the mteTriggerValueID object value changes.

        Once the trigger has fired for either presence or absence it
        will not fire again for that state until the object has been
        to the other state. "
    DEFVAL { { present, absent } }
    ::= { mteTriggerExistenceEntry 1 }

    Information by cisco

    mteTriggerExistenceTest OBJECT-TYPE
    SYNTAX      BITS { present(0), absent(1), changed(2) }
    MAX-ACCESS  read-write
    STATUS      current
    DESCRIPTION
        "The type of existence test to perform.  The trigger fires
        when the object at mteTriggerValueID is seen to go from
        present to absent, from absent to present, or to have it's
        value changed, depending on which tests are selected:

        present(0) - when this test is selected, the trigger fires
        when the mteTriggerValueID object goes from absent to present.

        absent(1)  - when this test is selected, the trigger fires
        when the mteTriggerValueID object goes from present to absent.
        changed(2) - when this test is selected, the trigger fires
        the mteTriggerValueID object value changes.

        Once the trigger has fired for either presence or absence it
        will not fire again for that state until the object has been
        to the other state. "
    DEFVAL { { present, absent } }
    ::= { mteTriggerExistenceEntry 1 }

    First Registration Authority (recovered by parent 1.3.6)

    Defense Communication Agency

    Current Registration Authority (recovered by parent 1.3.6.1.2)

    Internet Assigned Numbers Authority

    Brothers (5)

    OIDNameSub childrenSub Nodes TotalDescription
    1.3.6.1.2.1.88.1.2.4.1.2 mteTriggerExistenceStartup 0 0 Control for whether an event may be triggered when this entry
    is first set to 'active' and the test specified by
    mteTriggerExiste…
    1.3.6.1.2.1.88.1.2.4.1.3 mteTriggerExistenceObjectsOwner 0 0 To go with mteTriggerExistenceObjects, the mteOwner of a
    group of objects from mteObjectsTable.
    1.3.6.1.2.1.88.1.2.4.1.4 mteTriggerExistenceObjects 0 0 The mteObjectsName of a group of objects from
    mteObjectsTable. These objects are to be added to any
    Notification resulting from …
    1.3.6.1.2.1.88.1.2.4.1.5 mteTriggerExistenceEventOwner 0 0 To go with mteTriggerExistenceEvent, the mteOwner of an event
    entry from the mteEventTable.
    1.3.6.1.2.1.88.1.2.4.1.6 mteTriggerExistenceEvent 0 0 The mteEventName of the event to invoke when mteTriggerType is
    'existence' and this trigger fires. A length of 0 indicates no
    ev…