Description 1
Entry index. Sinse only one entry exist, always must be 1.
OID reference
1.3.6.1.4.1.171.10.94.89.89.92.1.15.1.1
Entry index. Sinse only one entry exist, always must be 1.
Identification
{1 3 6 1 4 1 171 10 94 89 89 92 1 15 1 1}
Definitions may combine these properties differently.
At least one MIB declaration places this object in a table row. A value belongs to a row instance; its suffix depends on the row's INDEX or AUGMENTS definition.
In RADLAN-TIMESYNCHRONIZATION-MIB, the row index rlTimeZoneIndex is declared as INTEGER. A non-negative index value is encoded as one numeric subidentifier. An instance has the form .1.3.6.1.4.1.171.10.94.89.89.92.1.15.1.1.<rlTimeZoneIndex>. Use an index value actually present on the device and permitted by its MIB. Other definitions can differ.
A query example is omitted because the source variants do not establish compatible read access.
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.
rlTimeZoneIndex OBJECT-TYPE
SYNTAX INTEGER (1)
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION "Entry index. Sinse only one entry exist, always must be 1."
::= { rlTimeZoneEntry 1 }rlTimeZoneIndex OBJECT-TYPE
SYNTAX INTEGER (1..2)
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION "Entry index. A row with index 2 will be existing in case the DHCP
timezone is supported, and will contain Timezone and Summertime dynamic
values.
Using index 2 in SET operations is allowed only for SNMP
inner clients (SNMPServ users), on condition that DHCP timezone option
is supported."
::= { rlTimeZoneEntry 1 }
Meaning
Identical descriptions are grouped. Different wording and device-specific notes are retained.
Description 1
Entry index. Sinse only one entry exist, always must be 1.
Description 2
Entry index. A row with index 2 will be existing in case the DHCP timezone is supported, and will contain Timezone and Summertime dynamic values. Using index 2 in SET operations is allowed only for SNMP inner clients (SNMPServ users), on condition that DHCP timezone option is supported.
D-Link official switch MIBsD-Link MIB copies (LibreNMS/Observium Community)
Evidence
Matching descriptions are grouped; representative source files are shown for each definition.
Status in source: current.
Names: rlTimeZoneIndex
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"rlTimeZoneIndex",
"OBJECT-TYPE",
"SYNTAX",
"INTEGER",
"(",
"1",
")",
"MAX-ACCESS",
"not-accessible",
"STATUS",
"current",
"DESCRIPTION",
"\"Entry index. Sinse only one entry exist, always must be 1.\"",
"::=",
"{",
"rlTimeZoneEntry",
"1",
"}"
],
"syntax_tree": [
[
"SimpleSyntax",
"INTEGER",
[
"integerSubType",
[
[
1
]
]
]
],
null,
[
"MaxAccessPart",
"not-accessible"
],
[
"Status",
"current"
],
[
"DESCRIPTION",
"Entry index. Sinse only one entry exist, always must be 1."
],
null,
null,
null,
null
]
}Module: RADLAN-TIMESYNCHRONIZATION-MIB
See published definition above
{'SNMPv2-TC': ['DisplayString', 'TEXTUAL-CONVENTION', 'RowStatus', 'TruthValue'], 'RADLAN-MIB': ['rnd'], 'SNMPv2-SMI': ['Unsigned32', 'Integer32', 'IpAddress', 'MODULE-IDENTITY', 'OBJECT-TYPE'], 'INET-ADDRESS-MIB': ['InetAddressType', 'InetAddress']}Module: DLINK-3100-TIMESYNCHRONIZATION-MIB
{'SNMPv2-TC': ['DisplayString', 'TEXTUAL-CONVENTION', 'RowStatus', 'TruthValue'], 'SNMPv2-SMI': ['Unsigned32', 'Integer32', 'IpAddress', 'MODULE-IDENTITY', 'OBJECT-TYPE'], 'DLINK-3100-MIB': ['rnd'], 'INET-ADDRESS-MIB': ['InetAddressType', 'InetAddress']}Status in source: current.
Names: rlTimeZoneIndex
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"rlTimeZoneIndex",
"OBJECT-TYPE",
"SYNTAX",
"INTEGER",
"(",
"1",
".",
".",
"2",
")",
"MAX-ACCESS",
"not-accessible",
"STATUS",
"current",
"DESCRIPTION",
"\"Entry index. A row with index 2 will be existing in case the DHCP timezone is supported, and will contain Timezone and Summertime dynamic values. Using index 2 in SET operations is allowed only for SNMP inner clients (SNMPServ users), on condition that DHCP timezone option is supported.\"",
"::=",
"{",
"rlTimeZoneEntry",
"1",
"}"
],
"syntax_tree": [
[
"SimpleSyntax",
"INTEGER",
[
"integerSubType",
[
[
1,
2
]
]
]
],
null,
[
"MaxAccessPart",
"not-accessible"
],
[
"Status",
"current"
],
[
"DESCRIPTION",
"Entry index. A row with index 2 will be existing in case the DHCP timezone is supported, and will contain Timezone and Summertime dynamic values. Using index 2 in SET operations is allowed only for SNMP inner clients (SNMPServ users), on condition that DHCP timezone option is supported."
],
null,
null,
null,
null
]
}Module: DLINK-3100-TIMESYNCHRONIZATION-MIB
See published definition above
{'SNMPv2-TC': ['DisplayString', 'TEXTUAL-CONVENTION', 'RowStatus', 'TruthValue'], 'SNMPv2-SMI': ['Unsigned32', 'Integer32', 'IpAddress', 'MODULE-IDENTITY', 'OBJECT-TYPE'], 'DLINK-3100-MIB': ['rnd'], 'INET-ADDRESS-MIB': ['InetAddressType', 'InetAddress']}Registration
| OID | Name | Direct children | Descendants | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.171.10.94.89.89.92.1.15.1.2 | rlTimeZoneTimeSyncMethod | 0 | 0 | |
| 1.3.6.1.4.1.171.10.94.89.89.92.1.15.1.3 | rlTimeZoneTimeZoneOffset | 0 | 0 | |
| 1.3.6.1.4.1.171.10.94.89.89.92.1.15.1.4 | rlTimeZoneTimeZoneCode | 0 | 0 | |
| 1.3.6.1.4.1.171.10.94.89.89.92.1.15.1.5 | rlTimeZoneDaylightSavingTimeMode | 0 | 0 | |
| 1.3.6.1.4.1.171.10.94.89.89.92.1.15.1.6 | rlTimeZoneDaylightSavingTimeStart | 0 | 0 | |
| 1.3.6.1.4.1.171.10.94.89.89.92.1.15.1.7 | rlTimeZoneDaylightSavingTimeEnd | 0 | 0 | |
| 1.3.6.1.4.1.171.10.94.89.89.92.1.15.1.8 | rlTimeZoneDaylightSavingTimeOffset | 0 | 0 | |
| 1.3.6.1.4.1.171.10.94.89.89.92.1.15.1.9 | rlTimeZoneDaylightSavingTimeCode | 0 | 0 | |
| 1.3.6.1.4.1.171.10.94.89.89.92.1.15.1.10 | rlTimeZoneTZDSTOffset | 0 | 0 | |
| 1.3.6.1.4.1.171.10.94.89.89.92.1.15.1.11 | rlTimeZoneTimeZoneName | 0 | 0 | |
| 1.3.6.1.4.1.171.10.94.89.89.92.1.15.1.12 | rlTimeZoneDataType | 0 | 0 | |
| 1.3.6.1.4.1.171.10.94.89.89.92.1.15.1.13 | rlTimeZoneDataSourceIfIndex | 0 | 0 |