OID reference

activityLogAttribute

1.3.6.1.4.1.2.3.51.3.8.5.1.1.4

Description

A string of data detailing one Activity Log entry's attribute. It contains states of both calling the Support Center and FTP/TFTP Server. A PENDING indicates that the system is preparing for the event to be called home by collecting data about the systems state. A SUCCESS state indicates that the problem was successfu…

Full description and source information

Identification

Identifier and names

Parent
1.3.6.1.4.1.2.3.51.3.8.5.1.1 (activityLogEntry)
Node code
4
Node name
activityLogAttribute
Category
SNMP management object
Numeric OID
1.3.6.1.4.1.2.3.51.3.8.5.1.1.4
URN notation
urn:oid:1.3.6.1.4.1.2.3.51.3.8.5.1.1.4
ASN.1, OID-IRI and named path variants
ASN.1 notation

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

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

SNMP properties

Value type
OCTET STRING
Maximum access defined by MIB
read-only
Status in MIB
mandatory

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 IMM-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.3.8.5.1.1.4.<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.3.8.5.1.1.4

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

activityLogAttribute · mandatory

activityLogAttribute OBJECT-TYPE
                  SYNTAX  OCTET STRING
                  ACCESS  read-only
                  STATUS  mandatory
                  DESCRIPTION
                  "
                  A string of data detailing one Activity Log entry's attribute. It contains states of both calling the Support Center and FTP/TFTP Server.
                  A PENDING indicates that the system is preparing for the event to be called home by collecting data about the systems state. A SUCCESS state
                  indicates that the problem was successfully transmitted to the Support Center or FTP/TFTP Server. A DISABLED state indicates that Service Advisor
                  has disabled calling the Support Center or FTP/TFTP Server while the hardware event is detected. A NOT SENT state indicates that the serviceable
                  event was not sent to prevent the same event from being sent repeatedly. The FAILED state indicates that the attempt
                  to transmit the event information was not successful. Additional information may be found in the Event Log.
                  The service number is similar to a ticket number that can be used as a reference to the issue reported by the machine
                  when contacting the Support Center. The event ID, event source, date and time are all information from the original entry in the event log.
                  The acknowledged as corrected field is a reminder to certain events to indicate their awareness of the issue.

                  For consistent results, view as a table and not as individual entries."
                  ::= { activityLogEntry 4 }

activityLogAttribute · mandatory

activityLogAttribute OBJECT-TYPE
                  SYNTAX  OCTET STRING
                  ACCESS  read-only
                  STATUS  mandatory
                  DESCRIPTION
                  "
                  A string of data detailing one Activity Log entry's attribute. It contains states of both calling IBM support and FTP/TFTP Server.
                  A PENDING indicates that the system is preparing for the event to be called home by collecting data about the systems state. A SUCCESS state
                  indicates that the problem was successfully transmitted to IBM support or FTP/TFTP Server. A DISABLED state indicates that Service Advisor
                  has disabled calling IBM Support or FTP/TFTP Server while the hardware event is detected. A NOT SENT state indicates that the serviceable
                  event was not sent to prevent the same event from being sent repeatedly. The FAILED state indicates that the attempt
                  to transmit the event information was not successful. Additional information may be found in the Event Log.
                  The service number is similar to a ticket number that can be used as a reference to the issue reported by the machine
                  when contacting IBM support. The event ID, event source, date and time are all information from the original entry in the event log.
                  The acknowledged as corrected field is a reminder to certain events to indicate their awareness of the issue.

                  For consistent results, view as a table and not as individual entries."
                  ::= { activityLogEntry 4 }

Meaning

Descriptions

2 unique

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

Description 1

A string of data detailing one Activity Log entry's attribute. It contains states of both calling the Support Center and FTP/TFTP Server. A PENDING indicates that the system is preparing for the event to be called home by collecting data about the systems state. A SUCCESS state indicates that the problem was successfully transmitted to the Support Center or FTP/TFTP Server. A DISABLED state indicates that Service Advisor has disabled calling the Support Center or FTP/TFTP Server while the hardware event is detected. A NOT SENT state indicates that the serviceable event was not sent to prevent the same event from being sent repeatedly. The FAILED state indicates that the attempt to transmit the event information was not successful. Additional information may be found in the Event Log. The service number is similar to a ticket number that can be used as a reference to the issue reported by the machine when contacting the Support Center. The event ID, event source, date and time are all information from the original entry in the event log. The acknowledged as corrected field is a reminder to certain events to indicate their awareness of the issue. 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

A string of data detailing one Activity Log entry's attribute. It contains states of both calling IBM support and FTP/TFTP Server. A PENDING indicates that the system is preparing for the event to be called home by collecting data about the systems state. A SUCCESS state indicates that the problem was successfully transmitted to IBM support or FTP/TFTP Server. A DISABLED state indicates that Service Advisor has disabled calling IBM Support or FTP/TFTP Server while the hardware event is detected. A NOT SENT state indicates that the serviceable event was not sent to prevent the same event from being sent repeatedly. The FAILED state indicates that the attempt to transmit the event information was not successful. Additional information may be found in the Event Log. The service number is similar to a ticket number that can be used as a reference to the issue reported by the machine when contacting IBM support. The event ID, event source, date and time are all information from the original entry in the event log. The acknowledged as corrected field is a reminder to certain events to indicate their awareness of the issue. For consistent results, view as a table and not as individual entries.

Sources for this description

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 · 2 sources

Description 1

activityLogAttribute · mandatoryIBM MIB copies (LibreNMS/Observium Community)2 sources

Status in source: mandatory.

Names: activityLogAttribute

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "activityLogAttribute",
    "OBJECT-TYPE",
    "SYNTAX",
    "OCTET",
    "STRING",
    "ACCESS",
    "read-only",
    "STATUS",
    "mandatory",
    "DESCRIPTION",
    "\" A string of data detailing one Activity Log entry's attribute. It contains states of both calling the Support Center and FTP/TFTP Server. A PENDING indicates that the system is preparing for the event to be called home by collecting data about the systems state. A SUCCESS state indicates that the problem was successfully transmitted to the Support Center or FTP/TFTP Server. A DISABLED state indicates that Service Advisor has disabled calling the Support Center or FTP/TFTP Server while the hardware event is detected. A NOT SENT state indicates that the serviceable event was not sent to prevent the same event from being sent repeatedly. The FAILED state indicates that the attempt to transmit the event information was not successful. Additional information may be found in the Event Log. The service number is similar to a ticket number that can be used as a reference to the issue reported by the machine when contacting the Support Center. The event ID, event source, date and time are all information from the original entry in the event log. The acknowledged as corrected field is a reminder to certain events to indicate their awareness of the issue. For consistent results, view as a table and not as individual entries.\"",
    "::=",
    "{",
    "activityLogEntry",
    "4",
    "}"
  ],
  "syntax_tree": [
    [
      "SimpleSyntax",
      "OCTET STRING"
    ],
    null,
    [
      "MaxAccessPart",
      "read-only"
    ],
    [
      "Status",
      "mandatory"
    ],
    [
      "DESCRIPTION",
      "A string of data detailing one Activity Log entry's attribute. It contains states of both calling the Support Center and FTP/TFTP Server. A PENDING indicates that the system is preparing for the event to be called home by collecting data about the systems state. A SUCCESS state indicates that the problem was successfully transmitted to the Support Center or FTP/TFTP Server. A DISABLED state indicates that Service Advisor has disabled calling the Support Center or FTP/TFTP Server while the hardware event is detected. A NOT SENT state indicates that the serviceable event was not sent to prevent the same event from being sent repeatedly. The FAILED state indicates that the attempt to transmit the event information was not successful. Additional information may be found in the Event Log. The service number is similar to a ticket number that can be used as a reference to the issue reported by the machine when contacting the Support Center. The event ID, event source, date and time are all information from the original entry in the event log. The acknowledged as corrected field is a reminder to certain events to indicate their awareness of the issue. For consistent results, view as a table and not as individual entries."
    ],
    null,
    null,
    null,
    null
  ]
}
Records for description 2IBM MIB copies (MibBrowser.online)1 record · 1 source

Description 2

activityLogAttribute · mandatoryIBM MIB copies (MibBrowser.online)1 source

Status in source: mandatory.

Names: activityLogAttribute

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "activityLogAttribute",
    "OBJECT-TYPE",
    "SYNTAX",
    "OCTET",
    "STRING",
    "ACCESS",
    "read-only",
    "STATUS",
    "mandatory",
    "DESCRIPTION",
    "\" A string of data detailing one Activity Log entry's attribute. It contains states of both calling IBM support and FTP/TFTP Server. A PENDING indicates that the system is preparing for the event to be called home by collecting data about the systems state. A SUCCESS state indicates that the problem was successfully transmitted to IBM support or FTP/TFTP Server. A DISABLED state indicates that Service Advisor has disabled calling IBM Support or FTP/TFTP Server while the hardware event is detected. A NOT SENT state indicates that the serviceable event was not sent to prevent the same event from being sent repeatedly. The FAILED state indicates that the attempt to transmit the event information was not successful. Additional information may be found in the Event Log. The service number is similar to a ticket number that can be used as a reference to the issue reported by the machine when contacting IBM support. The event ID, event source, date and time are all information from the original entry in the event log. The acknowledged as corrected field is a reminder to certain events to indicate their awareness of the issue. For consistent results, view as a table and not as individual entries.\"",
    "::=",
    "{",
    "activityLogEntry",
    "4",
    "}"
  ],
  "syntax_tree": [
    [
      "SimpleSyntax",
      "OCTET STRING"
    ],
    null,
    [
      "MaxAccessPart",
      "read-only"
    ],
    [
      "Status",
      "mandatory"
    ],
    [
      "DESCRIPTION",
      "A string of data detailing one Activity Log entry's attribute. It contains states of both calling IBM support and FTP/TFTP Server. A PENDING indicates that the system is preparing for the event to be called home by collecting data about the systems state. A SUCCESS state indicates that the problem was successfully transmitted to IBM support or FTP/TFTP Server. A DISABLED state indicates that Service Advisor has disabled calling IBM Support or FTP/TFTP Server while the hardware event is detected. A NOT SENT state indicates that the serviceable event was not sent to prevent the same event from being sent repeatedly. The FAILED state indicates that the attempt to transmit the event information was not successful. Additional information may be found in the Event Log. The service number is similar to a ticket number that can be used as a reference to the issue reported by the machine when contacting IBM support. The event ID, event source, date and time are all information from the original entry in the event log. The acknowledged as corrected field is a reminder to certain events to indicate their awareness of the issue. For consistent results, view as a table and not as individual entries."
    ],
    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.3.8.5.1.1.1 activityLogIndex00
1.3.6.1.4.1.2.3.51.3.8.5.1.1.2 activityLogString00
1.3.6.1.4.1.2.3.51.3.8.5.1.1.3 activityLogAcknowledge00