OID reference

ntpEntStatusDateTime

1.3.6.1.4.1.6339.100.25.1.2.10

Description

The current NTP date/time on the device, in 128-bit NTP date format. Ref: draft-ietf-ntp-ntpv4-proto-06, section 6: It includes a 64-bit signed seconds field spanning 584 billion years and a 64-bit fraction field resolving .05 attosecond (i.e. 0.5e-18). For convenience in mapping between formats, the seconds field is …

Full description and source information

Identification

Identifier and names

Parent
1.3.6.1.4.1.6339.100.25.1.2 (ntpEntStatus)
Node code
10
Node name
ntpEntStatusDateTime
Category
SNMP management object
Numeric OID
1.3.6.1.4.1.6339.100.25.1.2.10
URN notation
urn:oid:1.3.6.1.4.1.6339.100.25.1.2.10
ASN.1, OID-IRI and named path variants
ASN.1 notation

{1 3 6 1 4 1 6339 100 25 1 2 10}

  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) dcn(6339) os(100) ntpSnmpMIB(25) ntpSnmpMIBObjects(1) ntpEntStatus(2) ntpEntStatusDateTime(10)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) amer(6339) os(100) ntpSnmpMIB(25) ntpSnmpMIBObjects(1) ntpEntStatus(2) ntpEntStatusDateTime(10)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) dcn(6339) os(100) ntpSnmpMIB(25) ntpSnmpMIBObjects(1) ntpEntStatus(2) ntpEntStatusDateTime(10)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) amer(6339) os(100) ntpSnmpMIB(25) ntpSnmpMIBObjects(1) ntpEntStatus(2) ntpEntStatusDateTime(10)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) dcn(6339) os(100) ntpSnmpMIB(25) ntpSnmpMIBObjects(1) ntpEntStatus(2) ntpEntStatusDateTime(10)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) amer(6339) os(100) ntpSnmpMIB(25) ntpSnmpMIBObjects(1) ntpEntStatus(2) ntpEntStatusDateTime(10)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) dcn(6339) os(100) ntpSnmpMIB(25) ntpSnmpMIBObjects(1) ntpEntStatus(2) ntpEntStatusDateTime(10)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) amer(6339) os(100) ntpSnmpMIB(25) ntpSnmpMIBObjects(1) ntpEntStatus(2) ntpEntStatusDateTime(10)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) dcn(6339) os(100) ntpSnmpMIB(25) ntpSnmpMIBObjects(1) ntpEntStatus(2) ntpEntStatusDateTime(10)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) amer(6339) os(100) ntpSnmpMIB(25) ntpSnmpMIBObjects(1) ntpEntStatus(2) ntpEntStatusDateTime(10)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) dcn(6339) os(100) ntpSnmpMIB(25) ntpSnmpMIBObjects(1) ntpEntStatus(2) ntpEntStatusDateTime(10)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) amer(6339) os(100) ntpSnmpMIB(25) ntpSnmpMIBObjects(1) ntpEntStatus(2) ntpEntStatusDateTime(10)}
  • {iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) dcn(6339) os(100) ntpSnmpMIB(25) ntpSnmpMIBObjects(1) ntpEntStatus(2) ntpEntStatusDateTime(10)}
  • {iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) amer(6339) os(100) ntpSnmpMIB(25) ntpSnmpMIBObjects(1) ntpEntStatus(2) ntpEntStatusDateTime(10)}
  • {iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) dcn(6339) os(100) ntpSnmpMIB(25) ntpSnmpMIBObjects(1) ntpEntStatus(2) ntpEntStatusDateTime(10)}
  • {iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) amer(6339) os(100) ntpSnmpMIB(25) ntpSnmpMIBObjects(1) ntpEntStatus(2) ntpEntStatusDateTime(10)}
  • Additional combinations skipped.
OID-IRI notation
  • /1/3/6/1/4/1/6339/100/25/1/2/10
  • /ISO/Identified-Organization/6/1/4/1/6339/100/25/1/2/10
  • /ISO/3/6/1/4/1/6339/100/25/1/2/10
Named path variants
  • /iso/identified-organization/dod/internet/private/enterprise/6339/os/ntpSnmpMIB/ntpSnmpMIBObjects/ntpEntStatus/ntpEntStatusDateTime
  • /iso/identified-organization/dod/internet/private/enterprise/dcn/os/ntpSnmpMIB/ntpSnmpMIBObjects/ntpEntStatus/ntpEntStatusDateTime
  • /iso/identified-organization/dod/internet/private/enterprise/amer/os/ntpSnmpMIB/ntpSnmpMIBObjects/ntpEntStatus/ntpEntStatusDateTime
  • /iso/identified-organization/dod/internet/private/enterprises/6339/os/ntpSnmpMIB/ntpSnmpMIBObjects/ntpEntStatus/ntpEntStatusDateTime
  • /iso/identified-organization/dod/internet/private/enterprises/dcn/os/ntpSnmpMIB/ntpSnmpMIBObjects/ntpEntStatus/ntpEntStatusDateTime
  • /iso/identified-organization/dod/internet/private/enterprises/amer/os/ntpSnmpMIB/ntpSnmpMIBObjects/ntpEntStatus/ntpEntStatusDateTime
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/6339/os/ntpSnmpMIB/ntpSnmpMIBObjects/ntpEntStatus/ntpEntStatusDateTime
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/dcn/os/ntpSnmpMIB/ntpSnmpMIBObjects/ntpEntStatus/ntpEntStatusDateTime
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/amer/os/ntpSnmpMIB/ntpSnmpMIBObjects/ntpEntStatus/ntpEntStatusDateTime
  • /iso/identified-organization/dod/internet/private/vendor-objects/6339/os/ntpSnmpMIB/ntpSnmpMIBObjects/ntpEntStatus/ntpEntStatusDateTime
  • /iso/identified-organization/dod/internet/private/vendor-objects/dcn/os/ntpSnmpMIB/ntpSnmpMIBObjects/ntpEntStatus/ntpEntStatusDateTime
  • /iso/identified-organization/dod/internet/private/vendor-objects/amer/os/ntpSnmpMIB/ntpSnmpMIBObjects/ntpEntStatus/ntpEntStatusDateTime
  • /iso/org/dod/internet/private/enterprise/6339/os/ntpSnmpMIB/ntpSnmpMIBObjects/ntpEntStatus/ntpEntStatusDateTime
  • /iso/org/dod/internet/private/enterprise/dcn/os/ntpSnmpMIB/ntpSnmpMIBObjects/ntpEntStatus/ntpEntStatusDateTime
  • /iso/org/dod/internet/private/enterprise/amer/os/ntpSnmpMIB/ntpSnmpMIBObjects/ntpEntStatus/ntpEntStatusDateTime
  • /iso/org/dod/internet/private/enterprises/6339/os/ntpSnmpMIB/ntpSnmpMIBObjects/ntpEntStatus/ntpEntStatusDateTime
  • Additional combinations skipped.

SNMP properties

Value type
NtpDateTime
Maximum access defined by MIB
read-only
Status in MIB
current

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

ntpEntStatusDateTime · current

ntpEntStatusDateTime OBJECT-TYPE
    SYNTAX      NtpDateTime
    MAX-ACCESS  read-only
    STATUS      current
    DESCRIPTION
        "The current NTP date/time on the device, in 128-bit
         NTP date format. Ref: draft-ietf-ntp-ntpv4-proto-06,
         section 6:
          It includes a 64-bit signed seconds field
          spanning 584 billion years and a 64-bit fraction
          field resolving .05 attosecond (i.e. 0.5e-18).
          For convenience in mapping between formats, the
          seconds field is divided into a 32-bit era field
          and a 32-bit timestamp field.

         If time is not syncronized this field shall be a
         zero-length string.

         This object can be used to timestamp events on this
         node and allow a management station to coorelate
         different time objects. For example, a management
         station could query this object and sysUpTime in
         the same operation to be able to relate sysUpTime
         to NTP time.

         This object is not to be used to set the time of
         the node querying this object. NTP should be used
         for this--or at least SNTP."
    ::= { ntpEntStatus 10 }

ntpEntStatusDateTime · current

ntpEntStatusDateTime OBJECT-TYPE
    SYNTAX      NtpDateTime
    MAX-ACCESS  read-only
    STATUS      current
    DESCRIPTION
        "The current NTP date/time on the device, in 128-bit
         NTP date format. Ref: draft-ietf-ntp-ntpv4-proto-06,
         section 6:
          It includes a 64-bit signed seconds field
          spanning 584 billion years and a 64-bit fraction
          field resolving .05 attosecond (i.e. 0.5e-18).
          For convenience in mapping between formats, the
          seconds field is divided into a 32-bit era field
          and a 32-bit timestamp field.

         If time is not syncronized this field shall be a
         zero-length string.

         This object can be used to timestamp events on this
         node and allow a management station to coorelate
         different time objects. For example, a management
         station could query this object and sysUpTime in
         the same operation to be able to relate sysUpTime
         to NTP time.

         This object is not to be used to set the time of
         the node querying this object. NTP should be used
         for this--or at least SNTP."
    ::= { ntpEntStatus 10 }

Meaning

Descriptions

1 unique

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

The current NTP date/time on the device, in 128-bit NTP date format. Ref: draft-ietf-ntp-ntpv4-proto-06, section 6: It includes a 64-bit signed seconds field spanning 584 billion years and a 64-bit fraction field resolving .05 attosecond (i.e. 0.5e-18). For convenience in mapping between formats, the seconds field is divided into a 32-bit era field and a 32-bit timestamp field. If time is not syncronized this field shall be a zero-length string. This object can be used to timestamp events on this node and allow a management station to coorelate different time objects. For example, a management station could query this object and sysUpTime in the same operation to be able to relate sysUpTime to NTP time. This object is not to be used to set the time of the node querying this object. NTP should be used for this--or at least SNTP.

Sources for this description

Multiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community)

See 1 matching source record

Evidence

Source records

1 records

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

Records for description 1Multiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community)1 record · 3 sources

Description 1

ntpEntStatusDateTime · currentMultiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community)3 sources

Status in source: current.

Names: ntpEntStatusDateTime

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "ntpEntStatusDateTime",
    "OBJECT-TYPE",
    "SYNTAX",
    "NtpDateTime",
    "MAX-ACCESS",
    "read-only",
    "STATUS",
    "current",
    "DESCRIPTION",
    "\"The current NTP date/time on the device, in 128-bit NTP date format. Ref: draft-ietf-ntp-ntpv4-proto-06, section 6: It includes a 64-bit signed seconds field spanning 584 billion years and a 64-bit fraction field resolving .05 attosecond (i.e. 0.5e-18). For convenience in mapping between formats, the seconds field is divided into a 32-bit era field and a 32-bit timestamp field. If time is not syncronized this field shall be a zero-length string. This object can be used to timestamp events on this node and allow a management station to coorelate different time objects. For example, a management station could query this object and sysUpTime in the same operation to be able to relate sysUpTime to NTP time. This object is not to be used to set the time of the node querying this object. NTP should be used for this--or at least SNTP.\"",
    "::=",
    "{",
    "ntpEntStatus",
    "10",
    "}"
  ],
  "syntax_tree": [
    [
      "row",
      "NtpDateTime"
    ],
    null,
    [
      "MaxAccessPart",
      "read-only"
    ],
    [
      "Status",
      "current"
    ],
    [
      "DESCRIPTION",
      "The current NTP date/time on the device, in 128-bit NTP date format. Ref: draft-ietf-ntp-ntpv4-proto-06, section 6: It includes a 64-bit signed seconds field spanning 584 billion years and a 64-bit fraction field resolving .05 attosecond (i.e. 0.5e-18). For convenience in mapping between formats, the seconds field is divided into a 32-bit era field and a 32-bit timestamp field. If time is not syncronized this field shall be a zero-length string. This object can be used to timestamp events on this node and allow a management station to coorelate different time objects. For example, a management station could query this object and sysUpTime in the same operation to be able to relate sysUpTime to NTP time. This object is not to be used to set the time of the node querying this object. NTP should be used for this--or at least SNTP."
    ],
    null,
    null,
    null,
    null
  ]
}

Registration

Registration authorities

First Registration Authority (inferred from ancestor 1.3.6.1.4.1.6339)

Jin Emily

Siblings (10)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.6339.100.25.1.2.1 ntpEntStatusCurrentMode00
1.3.6.1.4.1.6339.100.25.1.2.2 ntpEntStatusCurrentModeVal00
1.3.6.1.4.1.6339.100.25.1.2.3 ntpEntStatusStratum00
1.3.6.1.4.1.6339.100.25.1.2.4 ntpEntStatusActiveRefSourceId00
1.3.6.1.4.1.6339.100.25.1.2.5 ntpEntStatusActiveRefSourceName00
1.3.6.1.4.1.6339.100.25.1.2.7 ntpEntStatusNumberOfRefSources00
1.3.6.1.4.1.6339.100.25.1.2.13 ntpEntStatusInPkts00
1.3.6.1.4.1.6339.100.25.1.2.14 ntpEntStatusOutPkts00
1.3.6.1.4.1.6339.100.25.1.2.15 ntpEntStatusBadVersion00
1.3.6.1.4.1.6339.100.25.1.2.16 ntpEntStatusProtocolError00