OID reference

activityLogAcknowledge

1.3.6.1.4.1.2.3.51.2.23.4.5.1.1.3

Description

The acknowledgement of one Activity Log entry as corrected. This field allows the users to set a reminder next to certain events to indicate their awareness of the issue. Checking the acknowledge flag will not cause the event to be removed from the log or close the ticket at IBM support. This log is not cleared, so th…

Full description and source information

Identification

Identifier and names

Parent
1.3.6.1.4.1.2.3.51.2.23.4.5.1.1 (activityLogEntry)
Node code
3
Node name
activityLogAcknowledge
Category
SNMP management object
Numeric OID
1.3.6.1.4.1.2.3.51.2.23.4.5.1.1.3
URN notation
urn:oid:1.3.6.1.4.1.2.3.51.2.23.4.5.1.1.3
ASN.1, OID-IRI and named path variants
ASN.1 notation

{1 3 6 1 4 1 2 3 51 2 23 4 5 1 1 3}

  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) ibm(2) ibmAgents(3) netfinitySupportProcessorAgent(51) bladeCenterSnmpMIB(2) service(23) serviceAdvisor(4) activityLogs(5) activityLogTable(1) activityLogEntry(1) activityLogAcknowledge(3)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) atmMIBCompliance2(2) ibmAgents(3) netfinitySupportProcessorAgent(51) bladeCenterSnmpMIB(2) service(23) serviceAdvisor(4) activityLogs(5) activityLogTable(1) activityLogEntry(1) activityLogAcknowledge(3)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) ibm(2) ibmAgents(3) netfinitySupportProcessorAgent(51) bladeCenterSnmpMIB(2) service(23) serviceAdvisor(4) activityLogs(5) activityLogTable(1) activityLogEntry(1) activityLogAcknowledge(3)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) atmMIBCompliance2(2) ibmAgents(3) netfinitySupportProcessorAgent(51) bladeCenterSnmpMIB(2) service(23) serviceAdvisor(4) activityLogs(5) activityLogTable(1) activityLogEntry(1) activityLogAcknowledge(3)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) ibm(2) ibmAgents(3) netfinitySupportProcessorAgent(51) bladeCenterSnmpMIB(2) service(23) serviceAdvisor(4) activityLogs(5) activityLogTable(1) activityLogEntry(1) activityLogAcknowledge(3)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) atmMIBCompliance2(2) ibmAgents(3) netfinitySupportProcessorAgent(51) bladeCenterSnmpMIB(2) service(23) serviceAdvisor(4) activityLogs(5) activityLogTable(1) activityLogEntry(1) activityLogAcknowledge(3)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) ibm(2) ibmAgents(3) netfinitySupportProcessorAgent(51) bladeCenterSnmpMIB(2) service(23) serviceAdvisor(4) activityLogs(5) activityLogTable(1) activityLogEntry(1) activityLogAcknowledge(3)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) atmMIBCompliance2(2) ibmAgents(3) netfinitySupportProcessorAgent(51) bladeCenterSnmpMIB(2) service(23) serviceAdvisor(4) activityLogs(5) activityLogTable(1) activityLogEntry(1) activityLogAcknowledge(3)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) ibm(2) ibmAgents(3) netfinitySupportProcessorAgent(51) bladeCenterSnmpMIB(2) service(23) serviceAdvisor(4) activityLogs(5) activityLogTable(1) activityLogEntry(1) activityLogAcknowledge(3)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) atmMIBCompliance2(2) ibmAgents(3) netfinitySupportProcessorAgent(51) bladeCenterSnmpMIB(2) service(23) serviceAdvisor(4) activityLogs(5) activityLogTable(1) activityLogEntry(1) activityLogAcknowledge(3)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) ibm(2) ibmAgents(3) netfinitySupportProcessorAgent(51) bladeCenterSnmpMIB(2) service(23) serviceAdvisor(4) activityLogs(5) activityLogTable(1) activityLogEntry(1) activityLogAcknowledge(3)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) atmMIBCompliance2(2) ibmAgents(3) netfinitySupportProcessorAgent(51) bladeCenterSnmpMIB(2) service(23) serviceAdvisor(4) activityLogs(5) activityLogTable(1) activityLogEntry(1) activityLogAcknowledge(3)}
  • {iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) ibm(2) ibmAgents(3) netfinitySupportProcessorAgent(51) bladeCenterSnmpMIB(2) service(23) serviceAdvisor(4) activityLogs(5) activityLogTable(1) activityLogEntry(1) activityLogAcknowledge(3)}
  • {iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) atmMIBCompliance2(2) ibmAgents(3) netfinitySupportProcessorAgent(51) bladeCenterSnmpMIB(2) service(23) serviceAdvisor(4) activityLogs(5) activityLogTable(1) activityLogEntry(1) activityLogAcknowledge(3)}
  • {iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) ibm(2) ibmAgents(3) netfinitySupportProcessorAgent(51) bladeCenterSnmpMIB(2) service(23) serviceAdvisor(4) activityLogs(5) activityLogTable(1) activityLogEntry(1) activityLogAcknowledge(3)}
  • {iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) atmMIBCompliance2(2) ibmAgents(3) netfinitySupportProcessorAgent(51) bladeCenterSnmpMIB(2) service(23) serviceAdvisor(4) activityLogs(5) activityLogTable(1) activityLogEntry(1) activityLogAcknowledge(3)}
  • Additional combinations skipped.
OID-IRI notation
  • /1/3/6/1/4/1/2/3/51/2/23/4/5/1/1/3
  • /ISO/Identified-Organization/6/1/4/1/2/3/51/2/23/4/5/1/1/3
  • /ISO/3/6/1/4/1/2/3/51/2/23/4/5/1/1/3
Named path variants
  • /iso/identified-organization/dod/internet/private/enterprise/ibm/ibmAgents/netfinitySupportProcessorAgent/bladeCenterSnmpMIB/service/serviceAdvisor/activityLogs/activityLogTable/activityLogEntry/activityLogAcknowledge
  • /iso/identified-organization/dod/internet/private/enterprise/IBM/ibmAgents/netfinitySupportProcessorAgent/bladeCenterSnmpMIB/service/serviceAdvisor/activityLogs/activityLogTable/activityLogEntry/activityLogAcknowledge
  • /iso/identified-organization/dod/internet/private/enterprise/atmMIBCompliance2/ibmAgents/netfinitySupportProcessorAgent/bladeCenterSnmpMIB/service/serviceAdvisor/activityLogs/activityLogTable/activityLogEntry/activityLogAcknowledge
  • /iso/identified-organization/dod/internet/private/enterprises/ibm/ibmAgents/netfinitySupportProcessorAgent/bladeCenterSnmpMIB/service/serviceAdvisor/activityLogs/activityLogTable/activityLogEntry/activityLogAcknowledge
  • /iso/identified-organization/dod/internet/private/enterprises/IBM/ibmAgents/netfinitySupportProcessorAgent/bladeCenterSnmpMIB/service/serviceAdvisor/activityLogs/activityLogTable/activityLogEntry/activityLogAcknowledge
  • /iso/identified-organization/dod/internet/private/enterprises/atmMIBCompliance2/ibmAgents/netfinitySupportProcessorAgent/bladeCenterSnmpMIB/service/serviceAdvisor/activityLogs/activityLogTable/activityLogEntry/activityLogAcknowledge
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/ibm/ibmAgents/netfinitySupportProcessorAgent/bladeCenterSnmpMIB/service/serviceAdvisor/activityLogs/activityLogTable/activityLogEntry/activityLogAcknowledge
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/IBM/ibmAgents/netfinitySupportProcessorAgent/bladeCenterSnmpMIB/service/serviceAdvisor/activityLogs/activityLogTable/activityLogEntry/activityLogAcknowledge
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/atmMIBCompliance2/ibmAgents/netfinitySupportProcessorAgent/bladeCenterSnmpMIB/service/serviceAdvisor/activityLogs/activityLogTable/activityLogEntry/activityLogAcknowledge
  • /iso/identified-organization/dod/internet/private/vendor-objects/ibm/ibmAgents/netfinitySupportProcessorAgent/bladeCenterSnmpMIB/service/serviceAdvisor/activityLogs/activityLogTable/activityLogEntry/activityLogAcknowledge
  • /iso/identified-organization/dod/internet/private/vendor-objects/IBM/ibmAgents/netfinitySupportProcessorAgent/bladeCenterSnmpMIB/service/serviceAdvisor/activityLogs/activityLogTable/activityLogEntry/activityLogAcknowledge
  • /iso/identified-organization/dod/internet/private/vendor-objects/atmMIBCompliance2/ibmAgents/netfinitySupportProcessorAgent/bladeCenterSnmpMIB/service/serviceAdvisor/activityLogs/activityLogTable/activityLogEntry/activityLogAcknowledge
  • /iso/org/dod/internet/private/enterprise/ibm/ibmAgents/netfinitySupportProcessorAgent/bladeCenterSnmpMIB/service/serviceAdvisor/activityLogs/activityLogTable/activityLogEntry/activityLogAcknowledge
  • /iso/org/dod/internet/private/enterprise/IBM/ibmAgents/netfinitySupportProcessorAgent/bladeCenterSnmpMIB/service/serviceAdvisor/activityLogs/activityLogTable/activityLogEntry/activityLogAcknowledge
  • /iso/org/dod/internet/private/enterprise/atmMIBCompliance2/ibmAgents/netfinitySupportProcessorAgent/bladeCenterSnmpMIB/service/serviceAdvisor/activityLogs/activityLogTable/activityLogEntry/activityLogAcknowledge
  • /iso/org/dod/internet/private/enterprises/ibm/ibmAgents/netfinitySupportProcessorAgent/bladeCenterSnmpMIB/service/serviceAdvisor/activityLogs/activityLogTable/activityLogEntry/activityLogAcknowledge
  • Additional combinations skipped.

SNMP properties

Value type
INTEGER
Maximum access defined by MIB
read-write
Status in MIB
mandatory

Enumerated values

ValueName
0no
1yes

Using this OID with SNMP

At least one MIB declaration places this object in a table row. A value belongs to a row instance; its suffix depends on the row's INDEX or AUGMENTS definition.

In BLADE-MIB, the row index activityLogIndex is declared as INTEGER. A non-negative index value is encoded as one numeric subidentifier. An instance has the form .1.3.6.1.4.1.2.3.51.2.23.4.5.1.1.3.<activityLogIndex>. Use an index value actually present on the device and permitted by its MIB. Other definitions can differ.

snmpwalk [connection options] DEVICE .1.3.6.1.4.1.2.3.51.2.23.4.5.1.1.3

Replace the placeholders with your connection and authentication options. Available permissions and device support can differ from the MIB.

Properties come from available MIB definitions. Actual device support and access can differ. See source records below for original files and qualifications.

Available source records contain 2 distinct definitions; some records may not include a definition.

Show 2 published definitions

activityLogAcknowledge · mandatory

activityLogAcknowledge OBJECT-TYPE
                  SYNTAX INTEGER{
                    no(0),
                    yes(1) }
                  ACCESS  read-write
                  STATUS  mandatory
                  DESCRIPTION
                  "The acknowledgement of one Activity Log entry as corrected. This field allows the users to set a reminder next to
                  certain events to indicate their awareness of the issue. Checking the acknowledge flag will not cause the event to be removed
                  from the log or close the ticket at IBM support. This log is not cleared, so the acknowledge flag can be used to indicate a problem
                  can be ignored. This field can be also used to override the 120 hour (5 day) filtering of reports via IBM Support or FTP/TFTP Server
                  of Service Data.
                  For consistent results, view as a table and not as individual entries."
                  ::= { activityLogEntry 3 }

activityLogAcknowledge · mandatory

activityLogAcknowledge OBJECT-TYPE
                  SYNTAX INTEGER{
                    no(0),
                    yes(1) }
                  ACCESS  read-write
                  STATUS  mandatory
                  DESCRIPTION
                  "The acknowledgement of one Activity Log entry as corrected. This field allows the users to set a reminder next to
                  certain events to indicate their awareness of the issue. Checking the acknowledge flag will not cause the event to be removed
                  from the log. This log is not cleared, so the acknowledge flag can be used to indicate a problem can be ignored. This field
                  can be also used to override the 120 hour (5 day) filtering of reports via FTP/TFTP Server of Service Data."
                  ::= { activityLogEntry 3 }

Meaning

Descriptions

2 unique

Identical descriptions are grouped. Different wording and device-specific notes are retained.

Description 1

The acknowledgement of one Activity Log entry as corrected. This field allows the users to set a reminder next to certain events to indicate their awareness of the issue. Checking the acknowledge flag will not cause the event to be removed from the log or close the ticket at IBM support. This log is not cleared, so the acknowledge flag can be used to indicate a problem can be ignored. This field can be also used to override the 120 hour (5 day) filtering of reports via IBM Support or FTP/TFTP Server of Service Data. For consistent results, view as a table and not as individual entries.

Sources for this description

IBM MIB copies (LibreNMS/Observium Community)

See 1 matching source record

Description 2

The acknowledgement of one Activity Log entry as corrected. This field allows the users to set a reminder next to certain events to indicate their awareness of the issue. Checking the acknowledge flag will not cause the event to be removed from the log. This log is not cleared, so the acknowledge flag can be used to indicate a problem can be ignored. This field can be also used to override the 120 hour (5 day) filtering of reports via FTP/TFTP Server of Service Data.

Sources for this description

IBM MIB copies (LibreNMS/Observium Community)IBM MIB copies (MibBrowser.online)

See 1 matching source record

Evidence

Source records

2 records

Matching descriptions are grouped; open a group to compare definitions and supporting files.

Records for description 1IBM MIB copies (LibreNMS/Observium Community)1 record · 1 source

Description 1

activityLogAcknowledge · mandatoryIBM MIB copies (LibreNMS/Observium Community)1 source

Status in source: mandatory.

Names: activityLogAcknowledge

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "activityLogAcknowledge",
    "OBJECT-TYPE",
    "SYNTAX",
    "INTEGER",
    "{",
    "no",
    "(",
    "0",
    ")",
    ",",
    "yes",
    "(",
    "1",
    ")",
    "}",
    "ACCESS",
    "read-write",
    "STATUS",
    "mandatory",
    "DESCRIPTION",
    "\"The acknowledgement of one Activity Log entry as corrected. This field allows the users to set a reminder next to certain events to indicate their awareness of the issue. Checking the acknowledge flag will not cause the event to be removed from the log or close the ticket at IBM support. This log is not cleared, so the acknowledge flag can be used to indicate a problem can be ignored. This field can be also used to override the 120 hour (5 day) filtering of reports via IBM Support or FTP/TFTP Server of Service Data. For consistent results, view as a table and not as individual entries.\"",
    "::=",
    "{",
    "activityLogEntry",
    "3",
    "}"
  ],
  "syntax_tree": [
    [
      "SimpleSyntax",
      "INTEGER",
      [
        "enumSpec",
        [
          [
            "no",
            0
          ],
          [
            "yes",
            1
          ]
        ]
      ]
    ],
    null,
    [
      "MaxAccessPart",
      "read-write"
    ],
    [
      "Status",
      "mandatory"
    ],
    [
      "DESCRIPTION",
      "The acknowledgement of one Activity Log entry as corrected. This field allows the users to set a reminder next to certain events to indicate their awareness of the issue. Checking the acknowledge flag will not cause the event to be removed from the log or close the ticket at IBM support. This log is not cleared, so the acknowledge flag can be used to indicate a problem can be ignored. This field can be also used to override the 120 hour (5 day) filtering of reports via IBM Support or FTP/TFTP Server of Service Data. For consistent results, view as a table and not as individual entries."
    ],
    null,
    null,
    null,
    null
  ]
}
Records for description 2IBM MIB copies (LibreNMS/Observium Community), IBM MIB copies (MibBrowser.online)1 record · 2 sources

Description 2

activityLogAcknowledge · mandatoryIBM MIB copies (LibreNMS/Observium Community), IBM MIB copies (MibBrowser.online)2 sources

Status in source: mandatory.

Names: activityLogAcknowledge

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "activityLogAcknowledge",
    "OBJECT-TYPE",
    "SYNTAX",
    "INTEGER",
    "{",
    "no",
    "(",
    "0",
    ")",
    ",",
    "yes",
    "(",
    "1",
    ")",
    "}",
    "ACCESS",
    "read-write",
    "STATUS",
    "mandatory",
    "DESCRIPTION",
    "\"The acknowledgement of one Activity Log entry as corrected. This field allows the users to set a reminder next to certain events to indicate their awareness of the issue. Checking the acknowledge flag will not cause the event to be removed from the log. This log is not cleared, so the acknowledge flag can be used to indicate a problem can be ignored. This field can be also used to override the 120 hour (5 day) filtering of reports via FTP/TFTP Server of Service Data.\"",
    "::=",
    "{",
    "activityLogEntry",
    "3",
    "}"
  ],
  "syntax_tree": [
    [
      "SimpleSyntax",
      "INTEGER",
      [
        "enumSpec",
        [
          [
            "no",
            0
          ],
          [
            "yes",
            1
          ]
        ]
      ]
    ],
    null,
    [
      "MaxAccessPart",
      "read-write"
    ],
    [
      "Status",
      "mandatory"
    ],
    [
      "DESCRIPTION",
      "The acknowledgement of one Activity Log entry as corrected. This field allows the users to set a reminder next to certain events to indicate their awareness of the issue. Checking the acknowledge flag will not cause the event to be removed from the log. This log is not cleared, so the acknowledge flag can be used to indicate a problem can be ignored. This field can be also used to override the 120 hour (5 day) filtering of reports via FTP/TFTP Server of Service Data."
    ],
    null,
    null,
    null,
    null
  ]
}

Registration

Registration authorities

First Registration Authority (inferred from ancestor 1.3.6.1.4.1.2)

Bob Moore

Siblings (3)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.2.3.51.2.23.4.5.1.1.1 activityLogIndex00
1.3.6.1.4.1.2.3.51.2.23.4.5.1.1.2 activityLogString00
1.3.6.1.4.1.2.3.51.2.23.4.5.1.1.4 activityLogAttribute00