Reference record for OID 1.3.6.1.2.1.92.1.3.1


parent
1.3.6.1.2.1.92.1.3 (nlmLog)
node code
1
node name
nlmLogTable
dot oid
1.3.6.1.2.1.92.1.3.1
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)}
  • {iso(1) identified-organization(3) dod(6) internet(1) mgmt(2) mib(1) notificationLogMIB(92) notificationLogMIBObjects(1) nlmLog(3) nlmLogTable(1)}
  • {iso(1) org(3) dod(6) internet(1) mgmt(2) mib-2(1) notificationLogMIB(92) notificationLogMIBObjects(1) nlmLog(3) nlmLogTable(1)}
  • {iso(1) org(3) dod(6) internet(1) mgmt(2) mib(1) notificationLogMIB(92) notificationLogMIBObjects(1) nlmLog(3) nlmLogTable(1)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) mgmt(2) mib-2(1) notificationLogMIB(92) notificationLogMIBObjects(1) nlmLog(3) nlmLogTable(1)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) mgmt(2) mib(1) notificationLogMIB(92) notificationLogMIBObjects(1) nlmLog(3) nlmLogTable(1)}
  • iri oid
  • /iso/identified-organization/dod/internet/mgmt/mib-2/notificationLogMIB/notificationLogMIBObjects/nlmLog/nlmLogTable
  • /iso/identified-organization/dod/internet/mgmt/mib/notificationLogMIB/notificationLogMIBObjects/nlmLog/nlmLogTable
  • /iso/org/dod/internet/mgmt/mib-2/notificationLogMIB/notificationLogMIBObjects/nlmLog/nlmLogTable
  • /iso/org/dod/internet/mgmt/mib/notificationLogMIB/notificationLogMIBObjects/nlmLog/nlmLogTable
  • /iso/iso-identified-organization/dod/internet/mgmt/mib-2/notificationLogMIB/notificationLogMIBObjects/nlmLog/nlmLogTable
  • /iso/iso-identified-organization/dod/internet/mgmt/mib/notificationLogMIB/notificationLogMIBObjects/nlmLog/nlmLogTable
  • iri by oid_info
    /ISO/Identified-Organization/6/1/2/1/92/1/3/1

    Description by circitor

    A table of Notification log entries.

    It is an implementation-specific matter whether entries in this
    table are preserved across initializations of the management
    system. In general one would expect that they are not.

    Note that keeping entries across initializations of the
    management system leads to some confusion with counters and
    TimeStamps, since both of those are based on sysUpTime, which
    resets on management initialization. In this situation,
    counters apply only after the reset and nlmLogTime for entries
    made before the reset MUST be set to 0.

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

    Description by cisco_v1

    A table of Notification log entries.

    It is an implementation-specific matter whether entries in this
    table are preserved across initializations of the management
    system. In general one would expect that they are not.

    Note that keeping entries across initializations of the
    management system leads to some confusion with counters and
    TimeStamps, since both of those are based on sysUpTime, which
    resets on management initialization. In this situation,
    counters apply only after the reset and nlmLogTime for entries
    made before the reset MUST be set to 0.

    Description by oid_info

    nlmLogTable OBJECT-TYPE SYNTAX SEQUENCE OF NlmLogEntry
    MAX-ACCESS not-accessible
    STATUS current
    DESCRIPTION
    "A table of Notification log entries.
    It is an implementation-specific matter whether entries in this
    table are preserved across initializations of the management
    system. In general one would expect that they are not.
    Note that keeping entries across initializations of the
    management system leads to some confusion with counters and
    TimeStamps, since both of those are based on sysUpTime, which
    resets on management initialization. In this situation,
    counters apply only after the reset and nlmLogTime for entries
    made before the reset MUST be set to 0."

    View at oid-info.com

    Description by mibdepot

    A table of Notification log entries.

    It is an implementation-specific matter whether entries in this
    table are preserved across initializations of the management
    system. In general one would expect that they are not.

    Note that keeping entries across initializations of the
    management system leads to some confusion with counters and
    TimeStamps, since both of those are based on sysUpTime, which
    resets on management initialization. In this situation,
    counters apply only after the reset and nlmLogTime for entries
    made before the reset MUST be set to 0.

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

    Description by cisco

    A table of Notification log entries.

    It is an implementation-specific matter whether entries in this
    table are preserved across initializations of the management
    system. In general one would expect that they are not.

    Note that keeping entries across initializations of the
    management system leads to some confusion with counters and
    TimeStamps, since both of those are based on sysUpTime, which
    resets on management initialization. In this situation,
    counters apply only after the reset and nlmLogTime for entries
    made before the reset MUST be set to 0.

    Information by circitor

    nlmLogTable OBJECT-TYPE SYNTAX SEQUENCE OF NlmLogEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "A table of Notification log entries. It is an implementation-specific matter whether entries in this table are preserved across initializations of the management system. In general one would expect that they are not. Note that keeping entries across initializations of the management system leads to some confusion with counters and TimeStamps, since both of those are based on sysUpTime, which resets on management initialization. In this situation, counters apply only after the reset and nlmLogTime for entries made before the reset MUST be set to 0." ::= { nlmLog 1 }

    Information by cisco_v1

    nlmLogTable OBJECT-TYPE SYNTAX SEQUENCE OF NlmLogEntry ACCESS not-accessible STATUS mandatory DESCRIPTION "A table of Notification log entries. It is an implementation-specific matter whether entries in this table are preserved across initializations of the management system. In general one would expect that they are not. Note that keeping entries across initializations of the management system leads to some confusion with counters and TimeStamps, since both of those are based on sysUpTime, which resets on management initialization. In this situation, counters apply only after the reset and nlmLogTime for entries made before the reset MUST be set to 0." ::= { nlmLog 1 }

    Information by oid_info

    Automatically extracted from RFC3014

    Information by mibdepot

    nlmLogTable OBJECT-TYPE SYNTAX SEQUENCE OF NlmLogEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "A table of Notification log entries. It is an implementation-specific matter whether entries in this table are preserved across initializations of the management system. In general one would expect that they are not. Note that keeping entries across initializations of the management system leads to some confusion with counters and TimeStamps, since both of those are based on sysUpTime, which resets on management initialization. In this situation, counters apply only after the reset and nlmLogTime for entries made before the reset MUST be set to 0." ::= { nlmLog 1 }

    Information by cisco

    nlmLogTable OBJECT-TYPE SYNTAX SEQUENCE OF NlmLogEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "A table of Notification log entries. It is an implementation-specific matter whether entries in this table are preserved across initializations of the management system. In general one would expect that they are not. Note that keeping entries across initializations of the management system leads to some confusion with counters and TimeStamps, since both of those are based on sysUpTime, which resets on management initialization. In this situation, counters apply only after the reset and nlmLogTime for entries made before the reset MUST be set to 0." ::= { nlmLog 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

    Children (1)

    OIDNameSub childrenSub Nodes TotalDescription
    1.3.6.1.2.1.92.1.3.1.1 nlmLogEntry 9 9 A Notification log entry.

    Entries appear in this table when Notifications occur and pass
    filtering by nlmConfigLogFilterName and …

    Brothers (1)

    OIDNameSub childrenSub Nodes TotalDescription
    1.3.6.1.2.1.92.1.3.2 nlmLogVariableTable 1 13 A table of variables to go with Notification log entries.