OID reference
1.3.6.1.4.1.3052.10.2.8.1
Text string for date and time; e.g. 'SUN 01/02/98 12:34:27'. When setting this object, only the date and time are required; the unit will ignore a specified day of week because it is calculated from the date and time. When this object is included in a notification as a varbind, it represents the time that the triggeri…
Identification
{1 3 6 1 4 1 3052 10 2 8 1}
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.
clock OBJECT-TYPE
SYNTAX DisplayString
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"Text string for date and time;
e.g. 'SUN 01/02/98 12:34:27'. When setting
this object, only the date and time are
required; the unit will ignore a specified
day of week because it is calculated from
the date and time. When this object is included
in a notification as a varbind, it represents
the time that the triggering event occurred."
::= { time 1 }clock OBJECT-TYPE
SYNTAX DisplayString
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"Text string for date and time;
e.g. 'SUN 01/02/98 12:34:27'. When setting
this object, only the date and time are
required; the unit will ignore a specified
day of week because it is calculated from
the date and time. When this object is included
in a notification as a varbind, it represents
the time that the triggering event occurred."
::= { time 1 }
Meaning
Identical descriptions are grouped. Different wording and device-specific notes are retained.
Text string for date and time; e.g. 'SUN 01/02/98 12:34:27'. When setting this object, only the date and time are required; the unit will ignore a specified day of week because it is calculated from the date and time. When this object is included in a notification as a varbind, it represents the time that the triggering event occurred.
Multiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community)
Evidence
Matching descriptions are grouped; open a group to compare definitions and supporting files.
Status in source: current.
Names: clock
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"clock",
"OBJECT-TYPE",
"SYNTAX",
"DisplayString",
"MAX-ACCESS",
"read-write",
"STATUS",
"current",
"DESCRIPTION",
"\"Text string for date and time; e.g. 'SUN 01/02/98 12:34:27'. When setting this object, only the date and time are required; the unit will ignore a specified day of week because it is calculated from the date and time. When this object is included in a notification as a varbind, it represents the time that the triggering event occurred.\"",
"::=",
"{",
"time",
"1",
"}"
],
"syntax_tree": [
[
"row",
"DisplayString"
],
null,
[
"MaxAccessPart",
"read-write"
],
[
"Status",
"current"
],
[
"DESCRIPTION",
"Text string for date and time; e.g. 'SUN 01/02/98 12:34:27'. When setting this object, only the date and time are required; the unit will ignore a specified day of week because it is calculated from the date and time. When this object is included in a notification as a varbind, it represents the time that the triggering event occurred."
],
null,
null,
null,
null
]
}Vendor MIB copy from the LibreNMS archive.
Module: SITEBOSS-550-STD-MIB
See published definition above
{'SNMPv2-TC': ['DisplayString'], 'SNMPv2-SMI': ['IpAddress', 'TimeTicks', 'Integer32', 'MODULE-IDENTITY', 'NOTIFICATION-TYPE', 'OBJECT-TYPE'], 'ASENTRIA-ROOT-MIB': ['asentria']}Related source files and packages:
Vendor MIB copy from the Observium Community archive.
Module: SITEBOSS-550-STD-MIB
See published definition above
{'SNMPv2-TC': ['DisplayString'], 'SNMPv2-SMI': ['IpAddress', 'TimeTicks', 'Integer32', 'MODULE-IDENTITY', 'NOTIFICATION-TYPE', 'OBJECT-TYPE'], 'ASENTRIA-ROOT-MIB': ['asentria']}Related source files and packages:
Registration