OID reference

dayPlanStatus

1.3.6.1.4.1.1206.4.2.6.3.3.6

Description

<Definition>This object indicates the current value of the active day PlanNumber-object. A value of zero (0) indicates that there is no dayPlanNumber that is currently active. <DescriptiveName>DayPlanTable.activeDayPlan:identifier <DataConceptType>Data Element

Full description and source information

Identification

Identifier and names

Parent
1.3.6.1.4.1.1206.4.2.6.3.3 (timebase, maxFontCharacters)
Node code
6
Node name
dayPlanStatus
Category
SNMP management object
Numeric OID
1.3.6.1.4.1.1206.4.2.6.3.3.6
URN notation
urn:oid:1.3.6.1.4.1.1206.4.2.6.3.3.6
ASN.1, OID-IRI and named path variants
ASN.1 notation

{1 3 6 1 4 1 1206 4 2 6 3 3 6}

  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) nema(1206) transportation(4) devices(2) global(6) globalTimeManagement(3) timebase(3) dayPlanStatus(6)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) nema(1206) transportation(4) devices(2) global(6) globalTimeManagement(3) maxFontCharacters(3) dayPlanStatus(6)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) nema(1206) transportation(4) devices(2) global(6) fontDefinition(3) timebase(3) dayPlanStatus(6)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) nema(1206) transportation(4) devices(2) global(6) fontDefinition(3) maxFontCharacters(3) dayPlanStatus(6)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) nema(1206) transportation(4) devices(2) dms(6) globalTimeManagement(3) timebase(3) dayPlanStatus(6)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) nema(1206) transportation(4) devices(2) dms(6) globalTimeManagement(3) maxFontCharacters(3) dayPlanStatus(6)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) nema(1206) transportation(4) devices(2) dms(6) fontDefinition(3) timebase(3) dayPlanStatus(6)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) nema(1206) transportation(4) devices(2) dms(6) fontDefinition(3) maxFontCharacters(3) dayPlanStatus(6)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) nema(1206) transportation(4) devices(2) global(6) globalTimeManagement(3) timebase(3) dayPlanStatus(6)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) nema(1206) transportation(4) devices(2) global(6) globalTimeManagement(3) maxFontCharacters(3) dayPlanStatus(6)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) nema(1206) transportation(4) devices(2) global(6) fontDefinition(3) timebase(3) dayPlanStatus(6)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) nema(1206) transportation(4) devices(2) global(6) fontDefinition(3) maxFontCharacters(3) dayPlanStatus(6)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) nema(1206) transportation(4) devices(2) dms(6) globalTimeManagement(3) timebase(3) dayPlanStatus(6)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) nema(1206) transportation(4) devices(2) dms(6) globalTimeManagement(3) maxFontCharacters(3) dayPlanStatus(6)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) nema(1206) transportation(4) devices(2) dms(6) fontDefinition(3) timebase(3) dayPlanStatus(6)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) nema(1206) transportation(4) devices(2) dms(6) fontDefinition(3) maxFontCharacters(3) dayPlanStatus(6)}
  • Additional combinations skipped.
OID-IRI notation
  • /1/3/6/1/4/1/1206/4/2/6/3/3/6
  • /ISO/Identified-Organization/6/1/4/1/1206/4/2/6/3/3/6
  • /ISO/3/6/1/4/1/1206/4/2/6/3/3/6
Named path variants
  • /iso/identified-organization/dod/internet/private/enterprise/1206/transportation/devices/global/globalTimeManagement/timebase/dayPlanStatus
  • /iso/identified-organization/dod/internet/private/enterprise/1206/transportation/devices/global/globalTimeManagement/maxFontCharacters/dayPlanStatus
  • /iso/identified-organization/dod/internet/private/enterprise/1206/transportation/devices/global/fontDefinition/timebase/dayPlanStatus
  • /iso/identified-organization/dod/internet/private/enterprise/1206/transportation/devices/global/fontDefinition/maxFontCharacters/dayPlanStatus
  • /iso/identified-organization/dod/internet/private/enterprise/1206/transportation/devices/dms/globalTimeManagement/timebase/dayPlanStatus
  • /iso/identified-organization/dod/internet/private/enterprise/1206/transportation/devices/dms/globalTimeManagement/maxFontCharacters/dayPlanStatus
  • /iso/identified-organization/dod/internet/private/enterprise/1206/transportation/devices/dms/fontDefinition/timebase/dayPlanStatus
  • /iso/identified-organization/dod/internet/private/enterprise/1206/transportation/devices/dms/fontDefinition/maxFontCharacters/dayPlanStatus
  • /iso/identified-organization/dod/internet/private/enterprise/nema/transportation/devices/global/globalTimeManagement/timebase/dayPlanStatus
  • /iso/identified-organization/dod/internet/private/enterprise/nema/transportation/devices/global/globalTimeManagement/maxFontCharacters/dayPlanStatus
  • /iso/identified-organization/dod/internet/private/enterprise/nema/transportation/devices/global/fontDefinition/timebase/dayPlanStatus
  • /iso/identified-organization/dod/internet/private/enterprise/nema/transportation/devices/global/fontDefinition/maxFontCharacters/dayPlanStatus
  • /iso/identified-organization/dod/internet/private/enterprise/nema/transportation/devices/dms/globalTimeManagement/timebase/dayPlanStatus
  • /iso/identified-organization/dod/internet/private/enterprise/nema/transportation/devices/dms/globalTimeManagement/maxFontCharacters/dayPlanStatus
  • /iso/identified-organization/dod/internet/private/enterprise/nema/transportation/devices/dms/fontDefinition/timebase/dayPlanStatus
  • /iso/identified-organization/dod/internet/private/enterprise/nema/transportation/devices/dms/fontDefinition/maxFontCharacters/dayPlanStatus
  • Additional combinations skipped.

SNMP properties

Value type
INTEGER, Integer32
Maximum access defined by MIB
read-only
Status in MIB
mandatory, deprecated

Definitions may combine these properties differently.

Compare 2 source variants

Variant 1 — ITE public NTCIP working repository MIBs, NTCIP published standard MIB annexes (reviewed modules)

Value type
INTEGER
Maximum access defined by MIB
read-only
Status in MIB
mandatory
Allowed ranges
0–255

Variant 2 — NTCIP published standard MIB annexes (reviewed modules), ITE public NTCIP working repository MIBs

Value type
Integer32
Maximum access defined by MIB
read-only
Status in MIB
deprecated
Allowed ranges
0–255

Using this OID with SNMP

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.6.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 6 distinct definitions; some records may not include a definition.

Show 6 published definitions

dayPlanStatus · mandatory

dayPlanStatus   OBJECT-TYPE
SYNTAX	INTEGER (0..255)
ACCESS	read-only
STATUS	mandatory
DESCRIPTION
"<Definition>This object indicates the current value of the active day PlanNumber-object.  A value of zero (0) indicates that there is no dayPlanNumber that is currently active. 
<DescriptiveName>DayPlanTable.activeDayPlan:identifier
<DataConceptType>Data Element"
::= { timebase 6 }

dayPlanStatus · mandatory

dayPlanStatus     OBJECT-TYPE
SYNTAX       INTEGER (0..255)
ACCESS       read-only
STATUS       mandatory
DESCRIPTION
        "<Definition>This object indicates the current value of the active
        day PlanNumber-object. A value of zero (0) indicates that there
        is no dayPlanNumber that is currently active.
        <DescriptiveName>DayPlanTable.activeDayPlan:identifier
      <DataConceptType>Data Element"
::= { timebase 6 }

dayPlanStatus · mandatory

dayPlanStatus OBJECT-TYPE
SYNTAX           INTEGER (0..255)
ACCESS           read-only
STATUS           mandatory
DESCRIPTION
"This object indicates the current value of the active day PlanNumber-object. A value of zero (0)
indicates that there is no dayPlanNumber that is currently active."
::= { timebase 6 }

dayPlanStatus · unconfirmed

dayPlanStatus OBJECT-TYPE
SYNTAX      Integer32(0..255)
MAX-ACCESS read-only
STATUS      deprecated
DESCRIPTION
   "<Definition>This object indicates the current value of the active
   dayPlanNumber-object.
  <Format> A value of zero (0) indicates that there is no dayPlanNumber that
  is currently active.
  <Supplanted by> ISO26048-1-DayPlan.fdDayPlanSchedulerCurrentDayPlan (ISO
  26048-1)
  <Object Identifier> 1.3.6.1.4.1.1206.4.2.6.3.3.6"
::= { timebase 6 }

dayPlanStatus · deprecated

dayPlanStatus   OBJECT-TYPE
  SYNTAX      Integer32(0..255)
  MAX-ACCESS  read-only
  STATUS      deprecated
  DESCRIPTION
"<Definition>This object indicates the current value of the active dayPlanNumber-object.  
<Format> A value of zero (0) indicates that there is no dayPlanNumber that is currently active. 
<Superseded by> DAY-PLAN-MIB.fdDayPlanSchedulerCurrentDayPlan (ISO 20684-3)
<Object Identifier> 1.3.6.1.4.1.1206.4.2.6.3.3.6"
::= { timebase 6 }

dayPlanStatus · mandatory

dayPlanStatus     OBJECT-TYPE
SYNTAX       INTEGER (0..255)
ACCESS       read-only
STATUS       mandatory
DESCRIPTION
       "<Definition>This object indicates the current value of the active
       dayPlanNumber-object. A value of zero (0) indicates that there is
       no dayPlanNumber that is currently active.
       <Object Identifier> 1.3.6.1.4.1.1206.4.2.6.3.3.6"
::= { timebase 6 }

Meaning

Descriptions

5 unique

Identical descriptions are grouped. Different wording and device-specific notes are retained.

Description 1

<Definition>This object indicates the current value of the active day PlanNumber-object. A value of zero (0) indicates that there is no dayPlanNumber that is currently active. <DescriptiveName>DayPlanTable.activeDayPlan:identifier <DataConceptType>Data Element

Sources for this description

ITE public NTCIP working repository MIBsNTCIP published standard MIB annexes (reviewed modules)

See 1 matching source record

Description 2

This object indicates the current value of the active day PlanNumber-object. A value of zero (0) indicates that there is no dayPlanNumber that is currently active.

Sources for this description

NTCIP published standard MIB annexes (reviewed modules)

See 1 matching source record

Description 3

<Definition>This object indicates the current value of the active dayPlanNumber-object. <Format> A value of zero (0) indicates that there is no dayPlanNumber that is currently active. <Supplanted by> ISO26048-1-DayPlan.fdDayPlanSchedulerCurrentDayPlan (ISO 26048-1) <Object Identifier> 1.3.6.1.4.1.1206.4.2.6.3.3.6

Sources for this description

NTCIP published standard MIB annexes (reviewed modules)

See 1 matching source record

Description 4

<Definition>This object indicates the current value of the active dayPlanNumber-object. <Format> A value of zero (0) indicates that there is no dayPlanNumber that is currently active. <Superseded by> DAY-PLAN-MIB.fdDayPlanSchedulerCurrentDayPlan (ISO 20684-3) <Object Identifier> 1.3.6.1.4.1.1206.4.2.6.3.3.6

Sources for this description

ITE public NTCIP working repository MIBs

See 1 matching source record

Description 5

<Definition>This object indicates the current value of the active dayPlanNumber-object. A value of zero (0) indicates that there is no dayPlanNumber that is currently active. <Object Identifier> 1.3.6.1.4.1.1206.4.2.6.3.3.6

Sources for this description

NTCIP published standard MIB annexes (reviewed modules)

See 1 matching source record

Evidence

Source records

5 records

Matching descriptions are grouped; open a group to compare definitions and supporting files.

Records for description 1ITE public NTCIP working repository MIBs, NTCIP published standard MIB annexes (reviewed modules)1 record · 2 sources

Description 1

dayPlanStatus · mandatoryITE public NTCIP working repository MIBs, NTCIP published standard MIB annexes (reviewed modules)2 sources

Status in source: mandatory.

Names: dayPlanStatus

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "dayPlanStatus",
    "OBJECT-TYPE",
    "SYNTAX",
    "INTEGER",
    "(",
    "0",
    ".",
    ".",
    "255",
    ")",
    "ACCESS",
    "read-only",
    "STATUS",
    "mandatory",
    "DESCRIPTION",
    "\"<Definition>This object indicates the current value of the active day PlanNumber-object. A value of zero (0) indicates that there is no dayPlanNumber that is currently active. <DescriptiveName>DayPlanTable.activeDayPlan:identifier <DataConceptType>Data Element\"",
    "::=",
    "{",
    "timebase",
    "6",
    "}"
  ],
  "syntax_tree": [
    [
      "SimpleSyntax",
      "INTEGER",
      [
        "integerSubType",
        [
          [
            0,
            255
          ]
        ]
      ]
    ],
    null,
    [
      "MaxAccessPart",
      "read-only"
    ],
    [
      "Status",
      "mandatory"
    ],
    [
      "DESCRIPTION",
      "<Definition>This object indicates the current value of the active day PlanNumber-object. A value of zero (0) indicates that there is no dayPlanNumber that is currently active. <DescriptiveName>DayPlanTable.activeDayPlan:identifier <DataConceptType>Data Element"
    ],
    null,
    null,
    null,
    null
  ]
}
Records for description 2NTCIP published standard MIB annexes (reviewed modules)1 record · 1 source

Description 2

dayPlanStatus · mandatoryNTCIP published standard MIB annexes (reviewed modules)1 source

Status in source: mandatory.

Names: dayPlanStatus

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "dayPlanStatus",
    "OBJECT-TYPE",
    "SYNTAX",
    "INTEGER",
    "(",
    "0",
    ".",
    ".",
    "255",
    ")",
    "ACCESS",
    "read-only",
    "STATUS",
    "mandatory",
    "DESCRIPTION",
    "\"This object indicates the current value of the active day PlanNumber-object. A value of zero (0) indicates that there is no dayPlanNumber that is currently active.\"",
    "::=",
    "{",
    "timebase",
    "6",
    "}"
  ],
  "syntax_tree": [
    [
      "SimpleSyntax",
      "INTEGER",
      [
        "integerSubType",
        [
          [
            0,
            255
          ]
        ]
      ]
    ],
    null,
    [
      "MaxAccessPart",
      "read-only"
    ],
    [
      "Status",
      "mandatory"
    ],
    [
      "DESCRIPTION",
      "This object indicates the current value of the active day PlanNumber-object. A value of zero (0) indicates that there is no dayPlanNumber that is currently active."
    ],
    null,
    null,
    null,
    null
  ]
}
  • NTCIP published standard MIB annexes (reviewed modules) · Publisher's source file: NTCIP 1201:1996, Global Object Definitions Published December 2001 (superceded by NTCIP 1201 v02) — original PDF · Official record

    Module: GLOBAL

    See published definition above

    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: A typographic closing DESCRIPTION quotation delimiter occurs immediately at a native SMI field boundary. Normalize this delimiter only in the derived transcription; retain the literal published definition, full description and unchanged numeric assignments.

    Source data warning: A typographic closing quotation mark terminates a DESCRIPTION in this PDF. Normalize that delimiter only in the derived MIB transcription; preserve the literal published definition and unmodified PDF. No numeric assignment changes.

    Source data warning: A typographic opening DESCRIPTION quotation delimiter occurs immediately at a native SMI field boundary. Normalize this delimiter only in the derived transcription; retain the literal published definition, full description and unchanged numeric assignments.

    Source data warning: The GLOBAL moduleMake/moduleVersion assignment closes its explicitly opened brace with a parenthesis. Normalize only that delimiter in the derived parsing copy; retain the original definition and unchanged numeric expression.

    Source data warning: The historical GLOBAL security grouping explicitly prints the parent global and suffix 5 but omits assignment braces. Reuse two adjacent whitespace bytes for those braces in the parsing copy; retain the original expression and qualify this syntactic interpretation. No numeric arc is invented or replaced.

    Source data warning: Unconfirmed historical GLOBAL parent interpretation: the assignment names EventLogConfigTable, while its native table or entry declaration uses eventLogConfigTable. Interpret only this byte-pinned reference using that explicit local declaration. All numeric suffixes and the original published definition remain unchanged; verify the original before implementation.

    Source data warning: Unconfirmed historical GLOBAL parent interpretation: the assignment names EventLogEntry, while its native table or entry declaration uses eventLogEntry. Interpret only this byte-pinned reference using that explicit local declaration. All numeric suffixes and the original published definition remain unchanged; verify the original before implementation.

    Source data warning: Unconfirmed historical GLOBAL parent interpretation: the assignment names globalmoduleTable, while its native table or entry declaration uses globalModuleTable. Interpret only this byte-pinned reference using that explicit local declaration. All numeric suffixes and the original published definition remain unchanged; verify the original before implementation.

    Source data warning: Unconfirmed historical GLOBAL parent interpretation: the assignment names moduleTableEntry, while its native table or entry declaration uses moduleEntry. Interpret only this byte-pinned reference using that explicit local declaration. All numeric suffixes and the original published definition remain unchanged; verify the original before implementation.

    Source data warning: Potentially inaccurate interpretation of historical NTCIP namespace references: missing or unreadable imports of devices, profiles. 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 NTCIP1201v0110b.pdf — GLOBAL (MIB transcription)
Records for description 3NTCIP published standard MIB annexes (reviewed modules)1 record · 1 source

Description 3

dayPlanStatus · unconfirmedNTCIP published standard MIB annexes (reviewed modules)1 source

Status in source: unconfirmed.

Names: dayPlanStatus

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "dayPlanStatus",
    "OBJECT-TYPE",
    "SYNTAX",
    "Integer32",
    "(",
    "0",
    ".",
    ".",
    "255",
    ")",
    "MAX-ACCESS",
    "read-only",
    "STATUS",
    "deprecated",
    "DESCRIPTION",
    "\"<Definition>This object indicates the current value of the active dayPlanNumber-object. <Format> A value of zero (0) indicates that there is no dayPlanNumber that is currently active. <Supplanted by> ISO26048-1-DayPlan.fdDayPlanSchedulerCurrentDayPlan (ISO 26048-1) <Object Identifier> 1.3.6.1.4.1.1206.4.2.6.3.3.6\"",
    "::=",
    "{",
    "timebase",
    "6",
    "}"
  ],
  "syntax_tree": [
    [
      "SimpleSyntax",
      "Integer32",
      [
        "integerSubType",
        [
          [
            0,
            255
          ]
        ]
      ]
    ],
    null,
    [
      "MaxAccessPart",
      "read-only"
    ],
    [
      "Status",
      "deprecated"
    ],
    [
      "DESCRIPTION",
      "<Definition>This object indicates the current value of the active dayPlanNumber-object. <Format> A value of zero (0) indicates that there is no dayPlanNumber that is currently active. <Supplanted by> ISO26048-1-DayPlan.fdDayPlanSchedulerCurrentDayPlan (ISO 26048-1) <Object Identifier> 1.3.6.1.4.1.1206.4.2.6.3.3.6"
    ],
    null,
    null,
    null,
    null
  ]
}
Records for description 4ITE public NTCIP working repository MIBs1 record · 1 source

Description 4

dayPlanStatus · deprecatedITE public NTCIP working repository MIBs1 source

Status in source: deprecated.

Names: dayPlanStatus

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "dayPlanStatus",
    "OBJECT-TYPE",
    "SYNTAX",
    "Integer32",
    "(",
    "0",
    ".",
    ".",
    "255",
    ")",
    "MAX-ACCESS",
    "read-only",
    "STATUS",
    "deprecated",
    "DESCRIPTION",
    "\"<Definition>This object indicates the current value of the active dayPlanNumber-object. <Format> A value of zero (0) indicates that there is no dayPlanNumber that is currently active. <Superseded by> DAY-PLAN-MIB.fdDayPlanSchedulerCurrentDayPlan (ISO 20684-3) <Object Identifier> 1.3.6.1.4.1.1206.4.2.6.3.3.6\"",
    "::=",
    "{",
    "timebase",
    "6",
    "}"
  ],
  "syntax_tree": [
    [
      "SimpleSyntax",
      "Integer32",
      [
        "integerSubType",
        [
          [
            0,
            255
          ]
        ]
      ]
    ],
    null,
    [
      "MaxAccessPart",
      "read-only"
    ],
    [
      "Status",
      "deprecated"
    ],
    [
      "DESCRIPTION",
      "<Definition>This object indicates the current value of the active dayPlanNumber-object. <Format> A value of zero (0) indicates that there is no dayPlanNumber that is currently active. <Superseded by> DAY-PLAN-MIB.fdDayPlanSchedulerCurrentDayPlan (ISO 20684-3) <Object Identifier> 1.3.6.1.4.1.1206.4.2.6.3.3.6"
    ],
    null,
    null,
    null,
    null
  ]
}
Records for description 5NTCIP published standard MIB annexes (reviewed modules)1 record · 1 source

Description 5

dayPlanStatus · mandatoryNTCIP published standard MIB annexes (reviewed modules)1 source

Status in source: mandatory.

Names: dayPlanStatus

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "dayPlanStatus",
    "OBJECT-TYPE",
    "SYNTAX",
    "INTEGER",
    "(",
    "0",
    ".",
    ".",
    "255",
    ")",
    "ACCESS",
    "read-only",
    "STATUS",
    "mandatory",
    "DESCRIPTION",
    "\"<Definition>This object indicates the current value of the active dayPlanNumber-object. A value of zero (0) indicates that there is no dayPlanNumber that is currently active. <Object Identifier> 1.3.6.1.4.1.1206.4.2.6.3.3.6\"",
    "::=",
    "{",
    "timebase",
    "6",
    "}"
  ],
  "syntax_tree": [
    [
      "SimpleSyntax",
      "INTEGER",
      [
        "integerSubType",
        [
          [
            0,
            255
          ]
        ]
      ]
    ],
    null,
    [
      "MaxAccessPart",
      "read-only"
    ],
    [
      "Status",
      "mandatory"
    ],
    [
      "DESCRIPTION",
      "<Definition>This object indicates the current value of the active dayPlanNumber-object. A value of zero (0) indicates that there is no dayPlanNumber that is currently active. <Object Identifier> 1.3.6.1.4.1.1206.4.2.6.3.3.6"
    ],
    null,
    null,
    null,
    null
  ]
}
  • NTCIP published standard MIB annexes (reviewed modules) · Publisher's source file: NTCIP 1201 v03.15 — Global Object (GO) Definitions, published March 2011 — original PDF · Official record

    Module: NTCIP1201-v03

    See published definition above

    Module imports
    {'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)

Registration

Registration authorities

First Registration Authority (inferred from ancestor 1.3.6.1.4.1.1206)

Schopp Bruce J.

Siblings (6)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.1206.4.2.6.3.3.1 maxTimeBaseScheduleEntries00
1.3.6.1.4.1.1206.4.2.6.3.3.2 timeBaseScheduleTable16
1.3.6.1.4.1.1206.4.2.6.3.3.3 maxDayPlans00
1.3.6.1.4.1.1206.4.2.6.3.3.4 maxDayPlanEvents00
1.3.6.1.4.1.1206.4.2.6.3.3.5 timeBaseDayPlanTable16
1.3.6.1.4.1.1206.4.2.6.3.3.7 timeBaseScheduleTableStatus00