Reference record for OID 1.3.6.1.2.1.92.1.3.1.1.5



parent
1.3.6.1.2.1.92.1.3.1.1 (nlmLogEntry)
node code
5
node name
nlmLogEngineTAddress
dot oid
1.3.6.1.2.1.92.1.3.1.1.5
type
OBJECT-TYPE
asn1 oid
  • {iso(1) identified-organization(3) dod(6) internet(1) mgmt(2) mib-2(1) notificationLogMIB(92) notificationLogMIBObjects(1) nlmLog(3) nlmLogTable(1) nlmLogEntry(1) nlmLogEngineTAddress(5)}
  • {iso(1) identified-organization(3) dod(6) internet(1) mgmt(2) mib(1) notificationLogMIB(92) notificationLogMIBObjects(1) nlmLog(3) nlmLogTable(1) nlmLogEntry(1) nlmLogEngineTAddress(5)}
  • {iso(1) org(3) dod(6) internet(1) mgmt(2) mib-2(1) notificationLogMIB(92) notificationLogMIBObjects(1) nlmLog(3) nlmLogTable(1) nlmLogEntry(1) nlmLogEngineTAddress(5)}
  • {iso(1) org(3) dod(6) internet(1) mgmt(2) mib(1) notificationLogMIB(92) notificationLogMIBObjects(1) nlmLog(3) nlmLogTable(1) nlmLogEntry(1) nlmLogEngineTAddress(5)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) mgmt(2) mib-2(1) notificationLogMIB(92) notificationLogMIBObjects(1) nlmLog(3) nlmLogTable(1) nlmLogEntry(1) nlmLogEngineTAddress(5)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) mgmt(2) mib(1) notificationLogMIB(92) notificationLogMIBObjects(1) nlmLog(3) nlmLogTable(1) nlmLogEntry(1) nlmLogEngineTAddress(5)}
    • iri oid
  • /iso/identified-organization/dod/internet/mgmt/mib-2/notificationLogMIB/notificationLogMIBObjects/nlmLog/nlmLogTable/nlmLogEntry/nlmLogEngineTAddress
  • /iso/identified-organization/dod/internet/mgmt/mib/notificationLogMIB/notificationLogMIBObjects/nlmLog/nlmLogTable/nlmLogEntry/nlmLogEngineTAddress
  • /iso/org/dod/internet/mgmt/mib-2/notificationLogMIB/notificationLogMIBObjects/nlmLog/nlmLogTable/nlmLogEntry/nlmLogEngineTAddress
  • /iso/org/dod/internet/mgmt/mib/notificationLogMIB/notificationLogMIBObjects/nlmLog/nlmLogTable/nlmLogEntry/nlmLogEngineTAddress
  • /iso/iso-identified-organization/dod/internet/mgmt/mib-2/notificationLogMIB/notificationLogMIBObjects/nlmLog/nlmLogTable/nlmLogEntry/nlmLogEngineTAddress
  • /iso/iso-identified-organization/dod/internet/mgmt/mib/notificationLogMIB/notificationLogMIBObjects/nlmLog/nlmLogTable/nlmLogEntry/nlmLogEngineTAddress
    • iri by oid_info
    /ISO/Identified-Organization/6/1/2/1/92/1/3/1/1/5

    Description by circitor

    The transport service address of the SNMP engine from which the
    Notification was received, formatted according to the corresponding
    value of nlmLogEngineTDomain. This is used to identify the source
    of an SNMPv1 trap, since an nlmLogEngineId cannot be extracted
    from the SNMPv1 trap pdu.

    This object MUST always be instantiated, even if the log
    can contain Notifications from only one engine.

    Please be aware that the nlmLogEngineTAddress may not uniquely
    identify the SNMP engine from which the Notification was received.
    For example, if an SNMP engine uses DHCP or NAT to obtain
    ip addresses, the address it uses may be shared with other
    network devices, and hence will not uniquely identify the
    SNMP engine.

    Parsed from file NOTIFICATION-LOG-MIB.mib
    Module: NOTIFICATION-LOG-MIB

    Description by cisco_v1

    The transport service address of the SNMP engine from which the
    Notification was received, formatted according to the corresponding
    value of nlmLogEngineTDomain. This is used to identify the source
    of an SNMPv1 trap, since an nlmLogEngineId cannot be extracted
    from the SNMPv1 trap pdu.

    This object MUST always be instantiated, even if the log
    can contain Notifications from only one engine.

    Please be aware that the nlmLogEngineTAddress may not uniquely
    identify the SNMP engine from which the Notification was received.
    For example, if an SNMP engine uses DHCP or NAT to obtain
    ip addresses, the address it uses may be shared with other
    network devices, and hence will not uniquely identify the
    SNMP engine.

    Description by oid_info

    nlmLogEngineTAddress OBJECT-TYPE SYNTAX TAddress
    MAX-ACCESS read-only
    STATUS current
    DESCRIPTION
    "The transport service address of the SNMP engine from which the
    Notification was received, formatted according to the corresponding
    value of nlmLogEngineTDomain. This is used to identify the source
    of an SNMPv1 trap, since an nlmLogEngineId cannot be extracted
    from the SNMPv1 trap pdu.
    This object MUST always be instantiated, even if the log
    can contain Notifications from only one engine.
    Please be aware that the nlmLogEngineTAddress may not uniquely
    identify the SNMP engine from which the Notification was received.
    For example, if an SNMP engine uses DHCP or NAT to obtain
    ip addresses, the address it uses may be shared with other
    network devices, and hence will not uniquely identify the
    SNMP engine."
    View at oid-info.com

    Description by mibdepot

    The transport service address of the SNMP engine from which the
    Notification was received, formatted according to the corresponding
    value of nlmLogEngineTDomain. This is used to identify the source
    of an SNMPv1 trap, since an nlmLogEngineId cannot be extracted
    from the SNMPv1 trap pdu.

    This object MUST always be instantiated, even if the log
    can contain Notifications from only one engine.

    Please be aware that the nlmLogEngineTAddress may not uniquely
    identify the SNMP engine from which the Notification was received.
    For example, if an SNMP engine uses DHCP or NAT to obtain
    ip addresses, the address it uses may be shared with other
    network devices, and hence will not uniquely identify the
    SNMP engine.

    Parsed from file NOTIFICATION-LOG-MIB.txt
    Company: None
    Module: NOTIFICATION-LOG-MIB

    Description by cisco

    The transport service address of the SNMP engine from which the
    Notification was received, formatted according to the corresponding
    value of nlmLogEngineTDomain. This is used to identify the source
    of an SNMPv1 trap, since an nlmLogEngineId cannot be extracted
    from the SNMPv1 trap pdu.

    This object MUST always be instantiated, even if the log
    can contain Notifications from only one engine.

    Please be aware that the nlmLogEngineTAddress may not uniquely
    identify the SNMP engine from which the Notification was received.
    For example, if an SNMP engine uses DHCP or NAT to obtain
    ip addresses, the address it uses may be shared with other
    network devices, and hence will not uniquely identify the
    SNMP engine.

    Information by circitor

    nlmLogEngineTAddress OBJECT-TYPE
    SYNTAX      TAddress
    MAX-ACCESS  read-only
    STATUS      current
    DESCRIPTION
     "The transport service address of the SNMP engine from which the
     Notification was received, formatted according to the corresponding
     value of nlmLogEngineTDomain. This is used to identify the source
     of an SNMPv1 trap, since an nlmLogEngineId cannot be extracted
     from the SNMPv1 trap pdu.

     This object MUST always be instantiated, even if the log
     can contain Notifications from only one engine.

     Please be aware that the nlmLogEngineTAddress may not uniquely
     identify the SNMP engine from which the Notification was received.
     For example, if an SNMP engine uses DHCP or NAT to obtain
     ip addresses, the address it uses may be shared with other
     network devices, and hence will not uniquely identify the
     SNMP engine."
    ::= { nlmLogEntry 5 }

    Information by cisco_v1

    nlmLogEngineTAddress OBJECT-TYPE
    SYNTAX TAddress

    ACCESS read-only
    STATUS mandatory
    DESCRIPTION
        "The transport service address of the SNMP engine from which the
        Notification was received, formatted according to the corresponding
        value of nlmLogEngineTDomain. This is used to identify the source
        of an SNMPv1 trap, since an nlmLogEngineId cannot be extracted
        from the SNMPv1 trap pdu.
        
        This object MUST always be instantiated, even if the log
        can contain Notifications from only one engine.
        
        Please be aware that the nlmLogEngineTAddress may not uniquely
        identify the SNMP engine from which the Notification was received.
        For example, if an SNMP engine uses DHCP or NAT to obtain
        ip addresses, the address it uses may be shared with other
        network devices, and hence will not uniquely identify the
        SNMP engine."
    ::= { nlmLogEntry 5 }

    Information by oid_info

    Automatically extracted from RFC3014

    Information by mibdepot

    nlmLogEngineTAddress OBJECT-TYPE
    SYNTAX      TAddress
    MAX-ACCESS  read-only
    STATUS      current
    DESCRIPTION
     "The transport service address of the SNMP engine from which the
     Notification was received, formatted according to the corresponding
     value of nlmLogEngineTDomain. This is used to identify the source
     of an SNMPv1 trap, since an nlmLogEngineId cannot be extracted
     from the SNMPv1 trap pdu.

     This object MUST always be instantiated, even if the log
     can contain Notifications from only one engine.

     Please be aware that the nlmLogEngineTAddress may not uniquely
     identify the SNMP engine from which the Notification was received.
     For example, if an SNMP engine uses DHCP or NAT to obtain
     ip addresses, the address it uses may be shared with other
     network devices, and hence will not uniquely identify the
     SNMP engine."
    ::= { nlmLogEntry 5 }

    Information by cisco

    nlmLogEngineTAddress OBJECT-TYPE
    SYNTAX      TAddress
    MAX-ACCESS  read-only
    STATUS      current
    DESCRIPTION
     "The transport service address of the SNMP engine from which the
     Notification was received, formatted according to the corresponding
     value of nlmLogEngineTDomain. This is used to identify the source
     of an SNMPv1 trap, since an nlmLogEngineId cannot be extracted
     from the SNMPv1 trap pdu.

     This object MUST always be instantiated, even if the log
     can contain Notifications from only one engine.

     Please be aware that the nlmLogEngineTAddress may not uniquely
     identify the SNMP engine from which the Notification was received.
     For example, if an SNMP engine uses DHCP or NAT to obtain
     ip addresses, the address it uses may be shared with other
     network devices, and hence will not uniquely identify the
     SNMP engine."
    ::= { nlmLogEntry 5 }

    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 (8)

    OIDNameSub childrenSub Nodes TotalDescription
    1.3.6.1.2.1.92.1.3.1.1.1 nlmLogIndex 0 0 A monotonically increasing integer for the sole purpose of
    indexing entries within the named log. When it reaches the
    maximum va…
    1.3.6.1.2.1.92.1.3.1.1.2 nlmLogTime 0 0 The value of sysUpTime when the entry was placed in the log. If
    the entry occurred before the most recent management system
    initi…
    1.3.6.1.2.1.92.1.3.1.1.3 nlmLogDateAndTime 0 0 The local date and time when the entry was logged, instantiated
    only by systems that have date and time capability.
    1.3.6.1.2.1.92.1.3.1.1.4 nlmLogEngineID 0 0 The identification of the SNMP engine at which the Notification
    originated.

    If the log can contain Notifications from only one en…
    1.3.6.1.2.1.92.1.3.1.1.6 nlmLogEngineTDomain 0 0 Indicates the kind of transport service by which a Notification
    was received from an SNMP engine. nlmLogEngineTAddress contains
    t…
    1.3.6.1.2.1.92.1.3.1.1.7 nlmLogContextEngineID 0 0 If the Notification was received in a protocol which has a
    contextEngineID element like SNMPv3, this object has that value.
    Other…
    1.3.6.1.2.1.92.1.3.1.1.8 nlmLogContextName 0 0 The name of the SNMP MIB context from which the Notification came.
    For SNMPv1 Traps this is the community string from the Trap.
    1.3.6.1.2.1.92.1.3.1.1.9 nlmLogNotificationID 0 0 The NOTIFICATION-TYPE object identifier of the Notification that
    occurred.