OID reference

maxDayPlanEvents

1.3.6.1.4.1.1206.4.2.6.3.3.4

Description

<Definition>The value of this object specifies the fixed number of different timebased Day Plan Events within each Day Plan supported by the device. The value of this object represents the number of rows (secondary key into the table) available within each of the day plans that are available in the timeBaseDayPlanTabl…

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
4
Node name
maxDayPlanEvents
Category
SNMP management object
Numeric OID
1.3.6.1.4.1.1206.4.2.6.3.3.4
URN notation
urn:oid:1.3.6.1.4.1.1206.4.2.6.3.3.4
ASN.1, OID-IRI and named path variants
ASN.1 notation

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

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

SNMP properties

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

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
Integer32
Units
DayPlanEvent
Maximum access defined by MIB
read-only
Status in MIB
deprecated
Allowed ranges
1–255

Variant 2 — 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
1–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.4.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

maxDayPlanEvents · deprecated

maxDayPlanEvents   OBJECT-TYPE
SYNTAX	Integer32(1..255)
UNITS       "DayPlanEvent"
MAX-ACCESS	read-only
STATUS	deprecated
DESCRIPTION
"<Definition>The value of this object specifies the fixed number of different timebased Day Plan Events within each Day Plan supported by the device.  The value of this object represents the number of rows (secondary key into the table) available within each of the day plans that are available in the timeBaseDayPlanTable.  All day plans shall have the same number of day plan events available for use. 
<Informative> The timeBaseDayPlanTable has been replaced with a dynamic table, which does not require an object indicating the maximum number of rows.
<Object Identifier> 1.3.6.1.4.1.1206.4.2.6.3.3.4"
::= { timebase 4 }

maxDayPlanEvents · mandatory

maxDayPlanEvents   OBJECT-TYPE
SYNTAX	INTEGER (1..255)
ACCESS	read-only
STATUS	mandatory
DESCRIPTION
"<Definition>The value of this object specifies the fixed number of different timebased Day Plan Events within each Day Plan supported by the device.  The value of this object represents the number of rows (secondary key into the table) available within each of the day plans that are available in the timeBaseDayPlanTable.  All day plans shall have the same number of day plan events available for use. 
<DescriptiveName>DayPlanTable.maxDayPlanEvents:quantity 
<DataConceptType>Data Element
<Unit>DayPlanEvent"
::= { timebase 4 }

maxDayPlanEvents · mandatory

maxDayPlanEvents    OBJECT-TYPE
SYNTAX       INTEGER (1..255)
ACCESS       read-only
STATUS       mandatory
DESCRIPTION
       "<Definition>The value of this object specifies the fixed number
       of different timebased Day Plan Events within each Day Plan
       supported by the device. The value of this object represents the
       number of rows (secondary key into the table) available within
       each of the day plans that are available in the
       timeBaseDayPlanTable. All day plans shall have the same number of
       day plan events available for use.
       <DescriptiveName>DayPlanTable.maxDayPlanEvents:quantity
       <DataConceptType>Data Element
      <Unit>DayPlanEvent"
::= { timebase 4 }

maxDayPlanEvents · mandatory

maxDayPlanEvents    OBJECT-TYPE
SYNTAX       INTEGER (1..255)
ACCESS       read-only
STATUS       mandatory
DESCRIPTION
       "<Definition>The value of this object specifies the fixed number
       of different timebased Day Plan Events within each Day Plan
       supported by the device. The value of this object represents the
       number of rows (secondary key into the table) available within
       each of the day plans that are available in the
       timeBaseDayPlanTable. All day plans shall have the same number of
       day plan events available for use.
       <Unit>DayPlanEvent
       <Object Identifier> 1.3.6.1.4.1.1206.4.2.6.3.3.4"
::= { timebase 4 }

maxDayPlanEvents · unconfirmed

maxDayPlanEvents OBJECT-TYPE
SYNTAX      Integer32(1..255)
UNITS       "DayPlanEvent"
MAX-ACCESS read-only
STATUS      deprecated
DESCRIPTION
   "<Definition>The value of this object specifies the fixed number of
   different timebased Day Plan Events within each Day Plan supported by the
   device. The value of this object represents the number of rows (secondary
   key into the table) available within each of the day plans that are
   available in the timeBaseDayPlanTable. All day plans shall have the same
   number of day plan events available for use.
  <Informative> The timeBaseDayPlanTable has been replaced with a dynamic
  table, which does not require an object indicating the maximum number of
  rows.
  <Object Identifier> 1.3.6.1.4.1.1206.4.2.6.3.3.4"
::= { timebase 4 }

maxDayPlanEvents · mandatory

maxDayPlanEvents OBJECT-TYPE
SYNTAX           INTEGER (1..255)
ACCESS           read-only
STATUS           mandatory
DESCRIPTION
"The value of this object specifies the maximum, fixed number of different timebased Day Plan Events
within each Day Plan supported by the device. The value of this object represents the number of rows
(secondary key into the table) available within each of the day plans that are available in the
timeBaseDayPlanTable."
::= { timebase 4 }

Meaning

Descriptions

4 unique

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

Description 1

<Definition>The value of this object specifies the fixed number of different timebased Day Plan Events within each Day Plan supported by the device. The value of this object represents the number of rows (secondary key into the table) available within each of the day plans that are available in the timeBaseDayPlanTable. All day plans shall have the same number of day plan events available for use. <Informative> The timeBaseDayPlanTable has been replaced with a dynamic table, which does not require an object indicating the maximum number of rows. <Object Identifier> 1.3.6.1.4.1.1206.4.2.6.3.3.4

Sources for this description

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

See 2 matching source records

Description 2

<Definition>The value of this object specifies the fixed number of different timebased Day Plan Events within each Day Plan supported by the device. The value of this object represents the number of rows (secondary key into the table) available within each of the day plans that are available in the timeBaseDayPlanTable. All day plans shall have the same number of day plan events available for use. <DescriptiveName>DayPlanTable.maxDayPlanEvents:quantity <DataConceptType>Data Element <Unit>DayPlanEvent

Sources for this description

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

See 1 matching source record

Description 3

<Definition>The value of this object specifies the fixed number of different timebased Day Plan Events within each Day Plan supported by the device. The value of this object represents the number of rows (secondary key into the table) available within each of the day plans that are available in the timeBaseDayPlanTable. All day plans shall have the same number of day plan events available for use. <Unit>DayPlanEvent <Object Identifier> 1.3.6.1.4.1.1206.4.2.6.3.3.4

Sources for this description

NTCIP published standard MIB annexes (reviewed modules)

See 1 matching source record

Description 4

The value of this object specifies the maximum, fixed number of different timebased Day Plan Events within each Day Plan supported by the device. The value of this object represents the number of rows (secondary key into the table) available within each of the day plans that are available in the timeBaseDayPlanTable.

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)2 records · 2 sources

Description 1

maxDayPlanEvents · deprecatedITE public NTCIP working repository MIBs1 source

Status in source: deprecated.

Names: maxDayPlanEvents

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "maxDayPlanEvents",
    "OBJECT-TYPE",
    "SYNTAX",
    "Integer32",
    "(",
    "1",
    ".",
    ".",
    "255",
    ")",
    "UNITS",
    [
      "literal",
      "22446179506c616e4576656e7422"
    ],
    "MAX-ACCESS",
    "read-only",
    "STATUS",
    "deprecated",
    "DESCRIPTION",
    "\"<Definition>The value of this object specifies the fixed number of different timebased Day Plan Events within each Day Plan supported by the device. The value of this object represents the number of rows (secondary key into the table) available within each of the day plans that are available in the timeBaseDayPlanTable. All day plans shall have the same number of day plan events available for use. <Informative> The timeBaseDayPlanTable has been replaced with a dynamic table, which does not require an object indicating the maximum number of rows. <Object Identifier> 1.3.6.1.4.1.1206.4.2.6.3.3.4\"",
    "::=",
    "{",
    "timebase",
    "4",
    "}"
  ],
  "syntax_tree": [
    [
      "SimpleSyntax",
      "Integer32",
      [
        "integerSubType",
        [
          [
            1,
            255
          ]
        ]
      ]
    ],
    [
      "UNITS",
      "DayPlanEvent"
    ],
    [
      "MaxAccessPart",
      "read-only"
    ],
    [
      "Status",
      "deprecated"
    ],
    [
      "DESCRIPTION",
      "<Definition>The value of this object specifies the fixed number of different timebased Day Plan Events within each Day Plan supported by the device. The value of this object represents the number of rows (secondary key into the table) available within each of the day plans that are available in the timeBaseDayPlanTable. All day plans shall have the same number of day plan events available for use. <Informative> The timeBaseDayPlanTable has been replaced with a dynamic table, which does not require an object indicating the maximum number of rows. <Object Identifier> 1.3.6.1.4.1.1206.4.2.6.3.3.4"
    ],
    null,
    null,
    null,
    null
  ]
}
maxDayPlanEvents · unconfirmedNTCIP published standard MIB annexes (reviewed modules)1 source

Status in source: unconfirmed.

Names: maxDayPlanEvents

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "maxDayPlanEvents",
    "OBJECT-TYPE",
    "SYNTAX",
    "Integer32",
    "(",
    "1",
    ".",
    ".",
    "255",
    ")",
    "UNITS",
    [
      "literal",
      "22446179506c616e4576656e7422"
    ],
    "MAX-ACCESS",
    "read-only",
    "STATUS",
    "deprecated",
    "DESCRIPTION",
    "\"<Definition>The value of this object specifies the fixed number of different timebased Day Plan Events within each Day Plan supported by the device. The value of this object represents the number of rows (secondary key into the table) available within each of the day plans that are available in the timeBaseDayPlanTable. All day plans shall have the same number of day plan events available for use. <Informative> The timeBaseDayPlanTable has been replaced with a dynamic table, which does not require an object indicating the maximum number of rows. <Object Identifier> 1.3.6.1.4.1.1206.4.2.6.3.3.4\"",
    "::=",
    "{",
    "timebase",
    "4",
    "}"
  ],
  "syntax_tree": [
    [
      "SimpleSyntax",
      "Integer32",
      [
        "integerSubType",
        [
          [
            1,
            255
          ]
        ]
      ]
    ],
    [
      "UNITS",
      "DayPlanEvent"
    ],
    [
      "MaxAccessPart",
      "read-only"
    ],
    [
      "Status",
      "deprecated"
    ],
    [
      "DESCRIPTION",
      "<Definition>The value of this object specifies the fixed number of different timebased Day Plan Events within each Day Plan supported by the device. The value of this object represents the number of rows (secondary key into the table) available within each of the day plans that are available in the timeBaseDayPlanTable. All day plans shall have the same number of day plan events available for use. <Informative> The timeBaseDayPlanTable has been replaced with a dynamic table, which does not require an object indicating the maximum number of rows. <Object Identifier> 1.3.6.1.4.1.1206.4.2.6.3.3.4"
    ],
    null,
    null,
    null,
    null
  ]
}
Records for description 2ITE public NTCIP working repository MIBs, NTCIP published standard MIB annexes (reviewed modules)1 record · 2 sources

Description 2

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

Status in source: mandatory.

Names: maxDayPlanEvents

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "maxDayPlanEvents",
    "OBJECT-TYPE",
    "SYNTAX",
    "INTEGER",
    "(",
    "1",
    ".",
    ".",
    "255",
    ")",
    "ACCESS",
    "read-only",
    "STATUS",
    "mandatory",
    "DESCRIPTION",
    "\"<Definition>The value of this object specifies the fixed number of different timebased Day Plan Events within each Day Plan supported by the device. The value of this object represents the number of rows (secondary key into the table) available within each of the day plans that are available in the timeBaseDayPlanTable. All day plans shall have the same number of day plan events available for use. <DescriptiveName>DayPlanTable.maxDayPlanEvents:quantity <DataConceptType>Data Element <Unit>DayPlanEvent\"",
    "::=",
    "{",
    "timebase",
    "4",
    "}"
  ],
  "syntax_tree": [
    [
      "SimpleSyntax",
      "INTEGER",
      [
        "integerSubType",
        [
          [
            1,
            255
          ]
        ]
      ]
    ],
    null,
    [
      "MaxAccessPart",
      "read-only"
    ],
    [
      "Status",
      "mandatory"
    ],
    [
      "DESCRIPTION",
      "<Definition>The value of this object specifies the fixed number of different timebased Day Plan Events within each Day Plan supported by the device. The value of this object represents the number of rows (secondary key into the table) available within each of the day plans that are available in the timeBaseDayPlanTable. All day plans shall have the same number of day plan events available for use. <DescriptiveName>DayPlanTable.maxDayPlanEvents:quantity <DataConceptType>Data Element <Unit>DayPlanEvent"
    ],
    null,
    null,
    null,
    null
  ]
}
Records for description 3NTCIP published standard MIB annexes (reviewed modules)1 record · 1 source

Description 3

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

Status in source: mandatory.

Names: maxDayPlanEvents

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "maxDayPlanEvents",
    "OBJECT-TYPE",
    "SYNTAX",
    "INTEGER",
    "(",
    "1",
    ".",
    ".",
    "255",
    ")",
    "ACCESS",
    "read-only",
    "STATUS",
    "mandatory",
    "DESCRIPTION",
    "\"<Definition>The value of this object specifies the fixed number of different timebased Day Plan Events within each Day Plan supported by the device. The value of this object represents the number of rows (secondary key into the table) available within each of the day plans that are available in the timeBaseDayPlanTable. All day plans shall have the same number of day plan events available for use. <Unit>DayPlanEvent <Object Identifier> 1.3.6.1.4.1.1206.4.2.6.3.3.4\"",
    "::=",
    "{",
    "timebase",
    "4",
    "}"
  ],
  "syntax_tree": [
    [
      "SimpleSyntax",
      "INTEGER",
      [
        "integerSubType",
        [
          [
            1,
            255
          ]
        ]
      ]
    ],
    null,
    [
      "MaxAccessPart",
      "read-only"
    ],
    [
      "Status",
      "mandatory"
    ],
    [
      "DESCRIPTION",
      "<Definition>The value of this object specifies the fixed number of different timebased Day Plan Events within each Day Plan supported by the device. The value of this object represents the number of rows (secondary key into the table) available within each of the day plans that are available in the timeBaseDayPlanTable. All day plans shall have the same number of day plan events available for use. <Unit>DayPlanEvent <Object Identifier> 1.3.6.1.4.1.1206.4.2.6.3.3.4"
    ],
    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)
Records for description 4NTCIP published standard MIB annexes (reviewed modules)1 record · 1 source

Description 4

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

Status in source: mandatory.

Names: maxDayPlanEvents

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "maxDayPlanEvents",
    "OBJECT-TYPE",
    "SYNTAX",
    "INTEGER",
    "(",
    "1",
    ".",
    ".",
    "255",
    ")",
    "ACCESS",
    "read-only",
    "STATUS",
    "mandatory",
    "DESCRIPTION",
    "\"The value of this object specifies the maximum, fixed number of different timebased Day Plan Events within each Day Plan supported by the device. The value of this object represents the number of rows (secondary key into the table) available within each of the day plans that are available in the timeBaseDayPlanTable.\"",
    "::=",
    "{",
    "timebase",
    "4",
    "}"
  ],
  "syntax_tree": [
    [
      "SimpleSyntax",
      "INTEGER",
      [
        "integerSubType",
        [
          [
            1,
            255
          ]
        ]
      ]
    ],
    null,
    [
      "MaxAccessPart",
      "read-only"
    ],
    [
      "Status",
      "mandatory"
    ],
    [
      "DESCRIPTION",
      "The value of this object specifies the maximum, fixed number of different timebased Day Plan Events within each Day Plan supported by the device. The value of this object represents the number of rows (secondary key into the table) available within each of the day plans that are available in the timeBaseDayPlanTable."
    ],
    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)

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.5 timeBaseDayPlanTable16
1.3.6.1.4.1.1206.4.2.6.3.3.6 dayPlanStatus00
1.3.6.1.4.1.1206.4.2.6.3.3.7 timeBaseScheduleTableStatus00