OID reference
1.3.6.1.4.1.7244.2.53.1.4.1.2
The starting day or days on which the configuration that referenced the time range starts going into effect. Same day can be set for both timeRangePeriodicStartDay and timeRangePeriodicEndDay objects
Identification
{1 3 6 1 4 1 7244 2 53 1 4 1 2}
| Bit position | Name |
|---|---|
| 1 | sunday |
| 2 | monday |
| 3 | tuesday |
| 4 | wednesday |
| 5 | thursday |
| 6 | friday |
| 7 | saturday |
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. The index encoding is not inferred here.
Published row index: timeRangeIndex, timeRangePeriodicEntryIndex.
snmpwalk [connection options] DEVICE .1.3.6.1.4.1.7244.2.53.1.4.1.2
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.
The displayed source records contain one distinct definition. Compare its source records.
timeRangePeriodicStartDay OBJECT-TYPE
SYNTAX BITS {
sunday(1),
monday(2),
tuesday(3),
wednesday(4),
thursday(5),
friday(6),
saturday(7)
}
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The starting day or days on which the configuration that
referenced the time range starts going into effect.
Same day can be set for both timeRangePeriodicStartDay and
timeRangePeriodicEndDay objects "
::= { timeRangePeriodicEntry 2 }
Meaning
Identical descriptions are grouped. Different wording and device-specific notes are retained.
The starting day or days on which the configuration that referenced the time range starts going into effect. Same day can be set for both timeRangePeriodicStartDay and timeRangePeriodicEndDay objects
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: timeRangePeriodicStartDay
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"timeRangePeriodicStartDay",
"OBJECT-TYPE",
"SYNTAX",
"BITS",
"{",
"sunday",
"(",
"1",
")",
",",
"monday",
"(",
"2",
")",
",",
"tuesday",
"(",
"3",
")",
",",
"wednesday",
"(",
"4",
")",
",",
"thursday",
"(",
"5",
")",
",",
"friday",
"(",
"6",
")",
",",
"saturday",
"(",
"7",
")",
"}",
"MAX-ACCESS",
"read-create",
"STATUS",
"current",
"DESCRIPTION",
"\"The starting day or days on which the configuration that referenced the time range starts going into effect. Same day can be set for both timeRangePeriodicStartDay and timeRangePeriodicEndDay objects \"",
"::=",
"{",
"timeRangePeriodicEntry",
"2",
"}"
],
"syntax_tree": [
[
"BITS",
[
[
"sunday",
1
],
[
"monday",
2
],
[
"tuesday",
3
],
[
"wednesday",
4
],
[
"thursday",
5
],
[
"friday",
6
],
[
"saturday",
7
]
]
],
null,
[
"MaxAccessPart",
"read-create"
],
[
"Status",
"current"
],
[
"DESCRIPTION",
"The starting day or days on which the configuration that referenced the time range starts going into effect. Same day can be set for both timeRangePeriodicStartDay and timeRangePeriodicEndDay objects"
],
null,
null,
null,
null
]
}Vendor MIB copy from the Observium Community archive.
Module: TIMERANGE-MIB
See published definition above
{'SNMPv2-TC': ['RowStatus', 'TEXTUAL-CONVENTION'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'OBJECT-TYPE', 'Integer32', 'Unsigned32'], 'RFC1213-MIB': ['DisplayString'], 'QUANTA-SWITCH-MIB': ['switch']}Related source files and packages:
Registration
| OID | Name | Direct children | Descendants | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.7244.2.53.1.4.1.1 | timeRangePeriodicEntryIndex | 0 | 0 | |
| 1.3.6.1.4.1.7244.2.53.1.4.1.3 | timeRangePeriodicStartTime | 0 | 0 | |
| 1.3.6.1.4.1.7244.2.53.1.4.1.4 | timeRangePeriodicEndDay | 0 | 0 | |
| 1.3.6.1.4.1.7244.2.53.1.4.1.5 | timeRangePeriodicEndTime | 0 | 0 | |
| 1.3.6.1.4.1.7244.2.53.1.4.1.6 | timeRangePeriodicStatus | 0 | 0 |