OID reference
1.3.6.1.4.1.1206.4.2.6.3.3.7
<Definition>This object indicates the number of the TimeBaseSchedule which is currently selected by the scheduling logic; the device may or may not be using the selected schedule. The value of zero (0) indicates that there is no timeBaseScheduleNumber that is currently selected. <Superseded by> DAY-PLAN-MIB.fdDayPlanS…
Identification
{1 3 6 1 4 1 1206 4 2 6 3 3 7}
Definitions may combine these properties differently.
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.1206.4.2.6.3.3.7.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 5 distinct definitions; some records may not include a definition.
timeBaseScheduleTableStatus OBJECT-TYPE
SYNTAX Integer32(0..65535)
MAX-ACCESS read-only
STATUS deprecated
DESCRIPTION
"<Definition>This object indicates the number of the TimeBaseSchedule
which is currently selected by the scheduling logic; the device may or
may not be using the selected schedule. The value of zero (0) indicates
that there is no timeBaseScheduleNumber that is currently selected.
<Superseded by> DAY-PLAN-MIB.fdDayPlanSchedulerSelectedRule (ISO 20684-3)
<Object Identifier> 1.3.6.1.4.1.1206.4.2.6.3.3.7"
::={timebase 7}timeBaseScheduleTableStatus OBJECT-TYPE
SYNTAX Integer32(0..65535)
MAX-ACCESS read-only
STATUS deprecated
DESCRIPTION
"<Definition>This object indicates the number of the TimeBaseSchedule which
is currently selected by the scheduling logic; the device may or may not be
using the selected schedule. The value of zero (0) indicates that there is
no timeBaseScheduleNumber that is currently selected.
<Supplanted by> ISO26048-1-DayPlan.fdDayPlanSchedulerSelectedRule (ISO
26048-1)
<Object Identifier> 1.3.6.1.4.1.1206.4.2.6.3.3.7"
::= { timebase 7 }timeBaseScheduleTableStatus OBJECT-TYPE
SYNTAX INTEGER (0..65535)
ACCESS read-only
STATUS mandatory
DESCRIPTION
"<Definition>This object indicates the number of the TimeBaseSchedule which
is currently selected by the scheduling logic; the device may or may not be
using the selected schedule. The value of zero (0) indicates that there is
no timeBaseScheduleNumber that is currently selected.
<Object Identifier> 1.3.6.1.4.1.1206.4.2.6.3.3.7"
::={timebase 7}timeBaseScheduleTableStatus OBJECT-TYPE
SYNTAX INTEGER (0..65535)
ACCESS read-only
STATUS mandatory
DESCRIPTION
"<Definition>This object indicates the number of the TimeBaseSchedule which is currently selected by the scheduling logic; the device may or may not be using the selected schedule. The value of zero (0) indicates that there is no timeBaseScheduleNumber that is currently selected.
<DescriptiveName>TimeBaseScheduleTable.status:identifier
<DataConceptType> Data Element"
::={timebase 7}timeBaseScheduleTableStatus OBJECT-TYPE
SYNTAX INTEGER (0..65535)
ACCESS read-only
STATUS mandatory
DESCRIPTION
"<Definition>This object indicates the number of the TimeBaseSchedule
which is currently selected by the scheduling logic; the device may or
may not be using the selected schedule. The value of zero (0) indicates
that there is no timeBaseScheduleNumber that is currently selected.
<DescriptiveName>TimeBaseScheduleTable.status:identifier
<DataConceptType> Data Element"
::={timebase 7}
Meaning
Identical descriptions are grouped. Different wording and device-specific notes are retained.
Description 1
<Definition>This object indicates the number of the TimeBaseSchedule which is currently selected by the scheduling logic; the device may or may not be using the selected schedule. The value of zero (0) indicates that there is no timeBaseScheduleNumber that is currently selected. <Superseded by> DAY-PLAN-MIB.fdDayPlanSchedulerSelectedRule (ISO 20684-3) <Object Identifier> 1.3.6.1.4.1.1206.4.2.6.3.3.7
Description 2
<Definition>This object indicates the number of the TimeBaseSchedule which is currently selected by the scheduling logic; the device may or may not be using the selected schedule. The value of zero (0) indicates that there is no timeBaseScheduleNumber that is currently selected. <Supplanted by> ISO26048-1-DayPlan.fdDayPlanSchedulerSelectedRule (ISO 26048-1) <Object Identifier> 1.3.6.1.4.1.1206.4.2.6.3.3.7
NTCIP published standard MIB annexes (reviewed modules)
Description 3
<Definition>This object indicates the number of the TimeBaseSchedule which is currently selected by the scheduling logic; the device may or may not be using the selected schedule. The value of zero (0) indicates that there is no timeBaseScheduleNumber that is currently selected. <Object Identifier> 1.3.6.1.4.1.1206.4.2.6.3.3.7
NTCIP published standard MIB annexes (reviewed modules)
Description 4
<Definition>This object indicates the number of the TimeBaseSchedule which is currently selected by the scheduling logic; the device may or may not be using the selected schedule. The value of zero (0) indicates that there is no timeBaseScheduleNumber that is currently selected. <DescriptiveName>TimeBaseScheduleTable.status:identifier <DataConceptType> Data Element
ITE public NTCIP working repository MIBsNTCIP published standard MIB annexes (reviewed modules)
Evidence
Matching descriptions are grouped; open a group to compare definitions and supporting files.
Status in source: deprecated.
Names: timeBaseScheduleTableStatus
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"timeBaseScheduleTableStatus",
"OBJECT-TYPE",
"SYNTAX",
"Integer32",
"(",
"0",
".",
".",
"65535",
")",
"MAX-ACCESS",
"read-only",
"STATUS",
"deprecated",
"DESCRIPTION",
"\"<Definition>This object indicates the number of the TimeBaseSchedule which is currently selected by the scheduling logic; the device may or may not be using the selected schedule. The value of zero (0) indicates that there is no timeBaseScheduleNumber that is currently selected. <Superseded by> DAY-PLAN-MIB.fdDayPlanSchedulerSelectedRule (ISO 20684-3) <Object Identifier> 1.3.6.1.4.1.1206.4.2.6.3.3.7\"",
"::=",
"{",
"timebase",
"7",
"}"
],
"syntax_tree": [
[
"SimpleSyntax",
"Integer32",
[
"integerSubType",
[
[
0,
65535
]
]
]
],
null,
[
"MaxAccessPart",
"read-only"
],
[
"Status",
"deprecated"
],
[
"DESCRIPTION",
"<Definition>This object indicates the number of the TimeBaseSchedule which is currently selected by the scheduling logic; the device may or may not be using the selected schedule. The value of zero (0) indicates that there is no timeBaseScheduleNumber that is currently selected. <Superseded by> DAY-PLAN-MIB.fdDayPlanSchedulerSelectedRule (ISO 20684-3) <Object Identifier> 1.3.6.1.4.1.1206.4.2.6.3.3.7"
],
null,
null,
null,
null
]
}Module: NTCIP1201-GlobalV1
See published definition above
{'SNMPv2-TC': ['AutonomousType', 'VariablePointer'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'OBJECT-TYPE', 'OBJECT-IDENTITY', 'Integer32', 'Unsigned32', 'zeroDotZero'], 'SNMPv2-CONF': ['OBJECT-GROUP'], 'NTCIP1201-Global': ['global'], 'NTCIP8004-Transportation': ['profiles']}Source data warning: This original is published in an ITE NTCIP working repository. Repository publication does not establish that this particular revision is an adopted standard. Consult its native revision history and the NTCIP published standards catalog before implementation. Copyright and distribution notices are retained in the downloadable original.
· Download NTCIP-1201 — ntcip1201-AuxIO.mibSame file in ntcip1201-SNMPConfig.mib.
Same file in ntcip1201-Security.mib.
Same file in ntcip1201-ProfilesSTMP.mib.
Same file in ntcip1201-NtcipTraps.mib.
Status in source: unconfirmed.
Names: timeBaseScheduleTableStatus
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"timeBaseScheduleTableStatus",
"OBJECT-TYPE",
"SYNTAX",
"Integer32",
"(",
"0",
".",
".",
"65535",
")",
"MAX-ACCESS",
"read-only",
"STATUS",
"deprecated",
"DESCRIPTION",
"\"<Definition>This object indicates the number of the TimeBaseSchedule which is currently selected by the scheduling logic; the device may or may not be using the selected schedule. The value of zero (0) indicates that there is no timeBaseScheduleNumber that is currently selected. <Supplanted by> ISO26048-1-DayPlan.fdDayPlanSchedulerSelectedRule (ISO 26048-1) <Object Identifier> 1.3.6.1.4.1.1206.4.2.6.3.3.7\"",
"::=",
"{",
"timebase",
"7",
"}"
],
"syntax_tree": [
[
"SimpleSyntax",
"Integer32",
[
"integerSubType",
[
[
0,
65535
]
]
]
],
null,
[
"MaxAccessPart",
"read-only"
],
[
"Status",
"deprecated"
],
[
"DESCRIPTION",
"<Definition>This object indicates the number of the TimeBaseSchedule which is currently selected by the scheduling logic; the device may or may not be using the selected schedule. The value of zero (0) indicates that there is no timeBaseScheduleNumber that is currently selected. <Supplanted by> ISO26048-1-DayPlan.fdDayPlanSchedulerSelectedRule (ISO 26048-1) <Object Identifier> 1.3.6.1.4.1.1206.4.2.6.3.3.7"
],
null,
null,
null,
null
]
}Module: NTCIP1201-Global
See published definition above
{'SNMPv2-TC': ['AutonomousType', 'VariablePointer'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'OBJECT-TYPE', 'OBJECT-IDENTITY', 'Integer32', 'Unsigned32', 'zeroDotZero'], 'NTCIP8004-Transportation': ['devices', 'profiles']}Source data warning: This record is transcribed from a published NTCIP MIB annex. The downloadable text is a derived transcription with page furniture and section headings masked; the unmodified original PDF is authoritative. Native definitions, DESCRIPTION and STATUS are retained. A published object definition does not establish support by any particular device.
Source data warning: Published module-root disagreement: global has an SMI assignment resolving to 1.3.6.1.4.1.1206.4.2.6, while its DESCRIPTION explicitly prints 1.3.6.1.4.1.1206.4.2.6.8. All dependent assignments from this module require verification. No root number has been silently corrected.
· Download 1201v4-0-0.pdf — NTCIP1201-Global (MIB transcription)Related source files and packages:
Status in source: mandatory.
Names: timeBaseScheduleTableStatus
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"timeBaseScheduleTableStatus",
"OBJECT-TYPE",
"SYNTAX",
"INTEGER",
"(",
"0",
".",
".",
"65535",
")",
"ACCESS",
"read-only",
"STATUS",
"mandatory",
"DESCRIPTION",
"\"<Definition>This object indicates the number of the TimeBaseSchedule which is currently selected by the scheduling logic; the device may or may not be using the selected schedule. The value of zero (0) indicates that there is no timeBaseScheduleNumber that is currently selected. <Object Identifier> 1.3.6.1.4.1.1206.4.2.6.3.3.7\"",
"::=",
"{",
"timebase",
"7",
"}"
],
"syntax_tree": [
[
"SimpleSyntax",
"INTEGER",
[
"integerSubType",
[
[
0,
65535
]
]
]
],
null,
[
"MaxAccessPart",
"read-only"
],
[
"Status",
"mandatory"
],
[
"DESCRIPTION",
"<Definition>This object indicates the number of the TimeBaseSchedule which is currently selected by the scheduling logic; the device may or may not be using the selected schedule. The value of zero (0) indicates that there is no timeBaseScheduleNumber that is currently selected. <Object Identifier> 1.3.6.1.4.1.1206.4.2.6.3.3.7"
],
null,
null,
null,
null
]
}Module: NTCIP1201-v03
See published definition above
{'RFC-1212': ['OBJECT-TYPE'], 'RFC1155-SMI': ['Opaque', 'Counter', 'Gauge', 'null'], 'RFC1213-MIB': ['DisplayString'], 'NTCIP8004v02': ['devices', 'Protocols', 'profiles', 'global']}Source data warning: Recovered from a file whose complete MIB does not parse. The original assignment and definition are preserved. Registration and implementation details may be inaccurate; consult the original file. Other damaged or unresolved declarations are not established registrations.
Source data warning: This record is transcribed from a published NTCIP MIB annex. The downloadable text is a derived transcription with page furniture and section headings masked; the unmodified original PDF is authoritative. Native definitions, DESCRIPTION and STATUS are retained. A published object definition does not establish support by any particular device.
Source data warning: Potentially inaccurate interpretation of historical NTCIP namespace references: NTCIP8004v02. These exact source files require the reviewed bindings shown below. The numeric roots used here are the explicit assignments in normative Annex A.2 of published NTCIP 8004 v02 (2010), physical pages 43–44. This does not establish that every historical module revision is identical. The annex also prints enterprise instead of RFC 1155 enterprises and declares Protocols while referencing protocols; those spelling interpretations are disclosed. The original IMPORTS, numeric suffixes and definitions remain unchanged. Verify both originals before implementation.
· Download NTCIP1201v0315r.pdf — NTCIP1201-v03 (MIB transcription)Related source files and packages:
Status in source: mandatory.
Names: timeBaseScheduleTableStatus
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"timeBaseScheduleTableStatus",
"OBJECT-TYPE",
"SYNTAX",
"INTEGER",
"(",
"0",
".",
".",
"65535",
")",
"ACCESS",
"read-only",
"STATUS",
"mandatory",
"DESCRIPTION",
"\"<Definition>This object indicates the number of the TimeBaseSchedule which is currently selected by the scheduling logic; the device may or may not be using the selected schedule. The value of zero (0) indicates that there is no timeBaseScheduleNumber that is currently selected. <DescriptiveName>TimeBaseScheduleTable.status:identifier <DataConceptType> Data Element\"",
"::=",
"{",
"timebase",
"7",
"}"
],
"syntax_tree": [
[
"SimpleSyntax",
"INTEGER",
[
"integerSubType",
[
[
0,
65535
]
]
]
],
null,
[
"MaxAccessPart",
"read-only"
],
[
"Status",
"mandatory"
],
[
"DESCRIPTION",
"<Definition>This object indicates the number of the TimeBaseSchedule which is currently selected by the scheduling logic; the device may or may not be using the selected schedule. The value of zero (0) indicates that there is no timeBaseScheduleNumber that is currently selected. <DescriptiveName>TimeBaseScheduleTable.status:identifier <DataConceptType> Data Element"
],
null,
null,
null,
null
]
}Module: NTCIP1201-2004
See published definition above
{'RFC-1212': ['OBJECT-TYPE'], 'RFC1155-SMI': ['Opaque', 'Counter', 'Gauge', 'null'], 'RFC1213-MIB': ['DisplayString'], 'NTCIP8004-A-2004': ['devices', 'protocols', 'profiles', 'global']}Source data warning: This original is published in an ITE NTCIP working repository. Repository publication does not establish that this particular revision is an adopted standard. Consult its native revision history and the NTCIP published standards catalog before implementation. Copyright and distribution notices are retained in the downloadable original.
Source data warning: Potentially inaccurate interpretation of historical NTCIP imports: the original references NTCIP8004-A-2004, which is absent from the public repository snapshot. The numeric roots used here are the explicit assignments in normative Annex A.2 of published NTCIP 8004 v02 (2010), physical pages 43–44. This does not establish that every historical module revision is identical. The annex also prints enterprise instead of RFC 1155 enterprises and declares Protocols while referencing protocols; those spelling interpretations are disclosed. The original IMPORTS, numeric suffixes and definitions remain unchanged. Verify both originals before implementation.
· Download NTCIP-1201 — NTCIP1201-Glo.mibModule: NTCIP1201-2004
See published definition above
{'RFC-1212': ['OBJECT-TYPE'], 'RFC1155-SMI': ['Opaque', 'Counter', 'Gauge', 'null'], 'RFC1213-MIB': ['DisplayString'], 'NTCIP8004-A-2004': ['devices', 'protocols', 'profiles', 'global']}Source data warning: Recovered from a file whose complete MIB does not parse. The original assignment and definition are preserved. Registration and implementation details may be inaccurate; consult the original file. Other damaged or unresolved declarations are not established registrations.
Source data warning: This record is transcribed from a published NTCIP MIB annex. The downloadable text is a derived transcription with page furniture and section headings masked; the unmodified original PDF is authoritative. Native definitions, DESCRIPTION and STATUS are retained. A published object definition does not establish support by any particular device.
Source data warning: Potentially inaccurate interpretation of historical NTCIP namespace references: NTCIP8004-A-2004. These exact source files require the reviewed bindings shown below. The numeric roots used here are the explicit assignments in normative Annex A.2 of published NTCIP 8004 v02 (2010), physical pages 43–44. This does not establish that every historical module revision is identical. The annex also prints enterprise instead of RFC 1155 enterprises and declares Protocols while referencing protocols; those spelling interpretations are disclosed. The original IMPORTS, numeric suffixes and definitions remain unchanged. Verify both originals before implementation.
· Download NTCIP1201v0232f.pdf — NTCIP1201-2004 (MIB transcription)Related source files and packages:
Registration
| OID | Name | Direct children | Descendants | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.1206.4.2.6.3.3.1 | maxTimeBaseScheduleEntries | 0 | 0 | |
| 1.3.6.1.4.1.1206.4.2.6.3.3.2 | timeBaseScheduleTable | 1 | 6 | |
| 1.3.6.1.4.1.1206.4.2.6.3.3.3 | maxDayPlans | 0 | 0 | |
| 1.3.6.1.4.1.1206.4.2.6.3.3.4 | maxDayPlanEvents | 0 | 0 | |
| 1.3.6.1.4.1.1206.4.2.6.3.3.5 | timeBaseDayPlanTable | 1 | 6 | |
| 1.3.6.1.4.1.1206.4.2.6.3.3.6 | dayPlanStatus | 0 | 0 |