OID reference
1.3.6.1.4.1.11863.6.2.1.4.2
A date-time specification. For example, Saturday May 26, 2012 at 1:30:15 would be given as: 2012-05-26 01:30:15
Identification
{1 3 6 1 4 1 11863 6 2 1 4 2}
At least one MIB declaration places this object in a scalar group. A scalar instance uses the suffix .0.
snmpget [connection options] DEVICE .1.3.6.1.4.1.11863.6.2.1.4.2.0
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.
tpSysTimeTimeToSet OBJECT-TYPE
SYNTAX OCTET STRING(SIZE(19))
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"A date-time specification.
For example, Saturday May 26, 2012 at 1:30:15 would be
given as:
2012-05-26 01:30:15
"
::= { tpSysTimeManualTimeConfig 2 }tpSysTimeTimeToSet OBJECT-TYPE
SYNTAX OCTET STRING(SIZE(19))
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"A date-time specification.
For example, Saturday May 26, 2012 at 1:30:15 would be
given as:
2012-05-26 01:30:15
"
::= { tpSysTimeManualTimeConfig 2 }
Meaning
Identical descriptions are grouped. Different wording and device-specific notes are retained.
A date-time specification. For example, Saturday May 26, 2012 at 1:30:15 would be given as: 2012-05-26 01:30:15
Multiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community)Netdisco MIB archive copies
Evidence
Matching descriptions are grouped; open a group to compare definitions and supporting files.
Status in source: current.
Names: tpSysTimeTimeToSet
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"tpSysTimeTimeToSet",
"OBJECT-TYPE",
"SYNTAX",
"OCTET",
"STRING",
"(",
"SIZE",
"(",
"19",
")",
")",
"MAX-ACCESS",
"read-write",
"STATUS",
"current",
"DESCRIPTION",
"\"A date-time specification. For example, Saturday May 26, 2012 at 1:30:15 would be given as: 2012-05-26 01:30:15 \"",
"::=",
"{",
"tpSysTimeManualTimeConfig",
"2",
"}"
],
"syntax_tree": [
[
"SimpleSyntax",
"OCTET STRING",
[
"octetStringSubType",
[
[
19
]
]
]
],
null,
[
"MaxAccessPart",
"read-write"
],
[
"Status",
"current"
],
[
"DESCRIPTION",
"A date-time specification. For example, Saturday May 26, 2012 at 1:30:15 would be given as: 2012-05-26 01:30:15"
],
null,
null,
null,
null
]
}Vendor MIB copy from the Observium Community archive.
Module: TPLINK-SYSTIME-MIB
See published definition above
{'SNMPv2-SMI': ['MODULE-IDENTITY', 'OBJECT-TYPE', 'IpAddress'], 'TPLINK-MIB': ['tplinkMgmt']}Related source files and packages:
Vendor MIB copy from the Netdisco archive.
Module: TPLINK-SYSTIME-MIB
See published definition above
{'SNMPv2-SMI': ['MODULE-IDENTITY', 'OBJECT-TYPE', 'IpAddress'], 'TPLINK-MIB': ['tplinkMgmt']}Related source files and packages:
Registration
| OID | Name | Direct children | Descendants | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.11863.6.2.1.4.1 | tpSysTimeManualTimeStatus | 0 | 0 |