OID reference
1.3.6.1.4.1.11.2.92.1.16
Current status of the clock. The value 'invalid' means time is meaninglesss, since it has not been manually configured, or achieved as a result of SNTP synchronization or set by RTC.
Identification
{1 3 6 1 4 1 11 2 92 1 16}
Definitions may combine these properties differently.
Numbers refer to source variants above. Each value is shown only for variants that define it.
| Value | Name | Source variants |
|---|---|---|
| 1 | invalid | 1, 2 |
| 2 | manuallySet | 1, 2 |
| 3 | synchronizedBySntp | 1, 2 |
| 4 | setByRtc | 1 |
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.11.2.92.1.16.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.
rlClockStatus OBJECT-TYPE
SYNTAX INTEGER {
invalid(1),
manuallySet(2),
synchronizedBySntp(3),
setByRtc(4)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION "Current status of the clock. The value 'invalid' means time is meaninglesss,
since it has not been manually configured, or achieved as a result
of SNTP synchronization or set by RTC."
::= {rlTimeSyncMethodMode 16 }rlClockStatus OBJECT-TYPE
SYNTAX INTEGER {
invalid(1),
manuallySet(2),
synchronizedBySntp(3)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION "Current status of the clock. The value 'invalid' means time is meaninglesss,
since it has neither been manually configured nor achieved as a result
of SNTP synchronization."
::= {rlTimeSyncMethodMode 16 }
Meaning
Identical descriptions are grouped. Different wording and device-specific notes are retained.
Description 1
Current status of the clock. The value 'invalid' means time is meaninglesss, since it has not been manually configured, or achieved as a result of SNTP synchronization or set by RTC.
HPE networking MIB copies (LibreNMS/Observium Community)HPE Instant On official MIBs
Description 2
Current status of the clock. The value 'invalid' means time is meaninglesss, since it has neither been manually configured nor achieved as a result of SNTP synchronization.
Evidence
Matching descriptions are grouped; open a group to compare definitions and supporting files.
Status in source: current.
Names: rlClockStatus
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"rlClockStatus",
"OBJECT-TYPE",
"SYNTAX",
"INTEGER",
"{",
"invalid",
"(",
"1",
")",
",",
"manuallySet",
"(",
"2",
")",
",",
"synchronizedBySntp",
"(",
"3",
")",
",",
"setByRtc",
"(",
"4",
")",
"}",
"MAX-ACCESS",
"read-only",
"STATUS",
"current",
"DESCRIPTION",
"\"Current status of the clock. The value 'invalid' means time is meaninglesss, since it has not been manually configured, or achieved as a result of SNTP synchronization or set by RTC.\"",
"::=",
"{",
"rlTimeSyncMethodMode",
"16",
"}"
],
"syntax_tree": [
[
"SimpleSyntax",
"INTEGER",
[
"enumSpec",
[
[
"invalid",
1
],
[
"manuallySet",
2
],
[
"synchronizedBySntp",
3
],
[
"setByRtc",
4
]
]
]
],
null,
[
"MaxAccessPart",
"read-only"
],
[
"Status",
"current"
],
[
"DESCRIPTION",
"Current status of the clock. The value 'invalid' means time is meaninglesss, since it has not been manually configured, or achieved as a result of SNTP synchronization or set by RTC."
],
null,
null,
null,
null
]
}Module: HPE-TIMESYNCHRONIZATION-MIB
See published definition above
{'IF-MIB': ['InterfaceIndex'], 'HPE-MIB': ['nm'], 'SNMPv2-TC': ['DisplayString', 'TEXTUAL-CONVENTION', 'RowStatus', 'TruthValue'], 'SNMPv2-SMI': ['Unsigned32', 'Integer32', 'IpAddress', 'MODULE-IDENTITY', 'OBJECT-TYPE'], 'INET-ADDRESS-MIB': ['InetAddressType', 'InetAddress']}Same file in HPE Instant On 1960 2.6.0.73.
Same file in HPE Instant On 1830 2.5.0.48.
Same file in HPE Instant On 1960 2.7.0.103.
Same file in HPE Instant On 1930 2.6.0.73.
Vendor MIB copy from the Observium Community archive. HPE networking support.
Module: HPE-TIMESYNCHRONIZATION-MIB
{'IF-MIB': ['InterfaceIndex'], 'HPE-MIB': ['nm'], 'SNMPv2-TC': ['DisplayString', 'TEXTUAL-CONVENTION', 'RowStatus', 'TruthValue'], 'SNMPv2-SMI': ['Unsigned32', 'Integer32', 'IpAddress', 'MODULE-IDENTITY', 'OBJECT-TYPE'], 'INET-ADDRESS-MIB': ['InetAddressType', 'InetAddress']}Related source files and packages:
Status in source: current.
Names: rlClockStatus
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"rlClockStatus",
"OBJECT-TYPE",
"SYNTAX",
"INTEGER",
"{",
"invalid",
"(",
"1",
")",
",",
"manuallySet",
"(",
"2",
")",
",",
"synchronizedBySntp",
"(",
"3",
")",
"}",
"MAX-ACCESS",
"read-only",
"STATUS",
"current",
"DESCRIPTION",
"\"Current status of the clock. The value 'invalid' means time is meaninglesss, since it has neither been manually configured nor achieved as a result of SNTP synchronization.\"",
"::=",
"{",
"rlTimeSyncMethodMode",
"16",
"}"
],
"syntax_tree": [
[
"SimpleSyntax",
"INTEGER",
[
"enumSpec",
[
[
"invalid",
1
],
[
"manuallySet",
2
],
[
"synchronizedBySntp",
3
]
]
]
],
null,
[
"MaxAccessPart",
"read-only"
],
[
"Status",
"current"
],
[
"DESCRIPTION",
"Current status of the clock. The value 'invalid' means time is meaninglesss, since it has neither been manually configured nor achieved as a result of SNTP synchronization."
],
null,
null,
null,
null
]
}Module: HPE-TIMESYNCHRONIZATION-MIB
See published definition above
{'IF-MIB': ['InterfaceIndex'], 'HPE-MIB': ['nm'], 'SNMPv2-TC': ['DisplayString', 'TEXTUAL-CONVENTION', 'RowStatus', 'TruthValue'], 'SNMPv2-SMI': ['Unsigned32', 'Integer32', 'IpAddress', 'MODULE-IDENTITY', 'OBJECT-TYPE'], 'INET-ADDRESS-MIB': ['InetAddressType', 'InetAddress']}Registration
| OID | Name | Direct children | Descendants | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.11.2.92.1.1 | rlTimeSyncMibVersion | 0 | 0 | |
| 1.3.6.1.4.1.11.2.92.1.2 | rndTimeSyncManagedTime | 0 | 0 | |
| 1.3.6.1.4.1.11.2.92.1.3 | rndTimeSyncManagedDate | 0 | 0 | |
| 1.3.6.1.4.1.11.2.92.1.4 | rndTimeSyncManagedDateTime | 0 | 0 | |
| 1.3.6.1.4.1.11.2.92.1.5 | rlTimeSyncMethod | 0 | 0 | |
| 1.3.6.1.4.1.11.2.92.1.6 | rlTimeZone | 0 | 0 | |
| 1.3.6.1.4.1.11.2.92.1.7 | rlTimeZoneCode | 0 | 0 | |
| 1.3.6.1.4.1.11.2.92.1.8 | rlDaylightSavingTimeMode | 0 | 0 | |
| 1.3.6.1.4.1.11.2.92.1.9 | rlDaylightSavingTimeStart | 0 | 0 | |
| 1.3.6.1.4.1.11.2.92.1.10 | rlDaylightSavingTimeEnd | 0 | 0 | |
| 1.3.6.1.4.1.11.2.92.1.11 | rlDaylightSavingTimeOffset | 0 | 0 | |
| 1.3.6.1.4.1.11.2.92.1.12 | rlDaylightSavingTimeCode | 0 | 0 | |
| 1.3.6.1.4.1.11.2.92.1.13 | rlTZDSTOffset | 0 | 0 | |
| 1.3.6.1.4.1.11.2.92.1.14 | rlTimeZoneName | 0 | 0 | |
| 1.3.6.1.4.1.11.2.92.1.15 | rlTimeZoneTable | 1 | 15 | |
| 1.3.6.1.4.1.11.2.92.1.17 | rlDhcpTimezoneOptionEnabled | 0 | 0 | |
| 1.3.6.1.4.1.11.2.92.1.18 | rlAutomaticClockSetFromPCEnabled | 0 | 0 | |
| 1.3.6.1.4.1.11.2.92.1.19 | rlTimeAndDateHaveBeenSet | 0 | 0 |