OID reference

maxDaylightSavingEntries

1.3.6.1.4.1.1206.4.2.6.3.7.1

Description

<Definition> The maximum number of entries (begin and end date pairs) that the DST Table can contain within the device. As of July 2007, devices used within the United States only require 1 entry when using the generic begin and end date method. <Informative>It is expected that, for devices using the absolute date met…

Full description and source information

Identification

Identifier and names

Parent
1.3.6.1.4.1.1206.4.2.6.3.7 (daylightSavingNode)
Node code
1
Node name
maxDaylightSavingEntries
Category
SNMP management object
Numeric OID
1.3.6.1.4.1.1206.4.2.6.3.7.1
URN notation
urn:oid:1.3.6.1.4.1.1206.4.2.6.3.7.1
ASN.1, OID-IRI and named path variants
ASN.1 notation

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

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

SNMP properties

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

Definitions may combine these properties differently.

Compare 2 source variants

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

Value type
Integer32
Units
entries
Maximum access defined by MIB
read-only
Status in MIB
deprecated
Allowed ranges
1–100

Variant 2 — NTCIP published standard MIB annexes (reviewed modules)

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

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

Show 3 published definitions

maxDaylightSavingEntries · unconfirmed

maxDaylightSavingEntries OBJECT-TYPE
SYNTAX      Integer32(1..100)
UNITS       "entries"
MAX-ACCESS read-only
STATUS      deprecated
DESCRIPTION
   "<Definition> The maximum number of entries (begin and end date pairs) that
   the DST Table can contain within the device. As of July 2007, devices used
   within the United States only require 1 entry when using the generic begin
   and end date method.
  <Informative>It is expected that, for devices using the absolute date
  method, the device would need to support at least 1 entry per year
  programmed.
  For multi-step DST transitions, a minimum of 2 rows are required (see Annex
  A.2.1 Figure 6).
  More than one row may be required if absolute date method (see Section
  2.4.8.2.2) is used for more than one year, or if more than one time change
  is implemented in a given year.
  <Superseded by> ISO26048-1-Clock.fdClockDstMaxEntries (ISO 26048-1)
  <Informative> The replacement object has a range of Unsigned32
  <Object Identifier> 1.3.6.1.4.1.1206.4.2.6.3.7.1"
::= { daylightSavingNode 1 }

maxDaylightSavingEntries · deprecated

maxDaylightSavingEntries   OBJECT-TYPE
SYNTAX  Integer32(1..100)
UNITS   "entries"
MAX-ACCESS  read-only
STATUS      deprecated
DESCRIPTION 
   "<Definition> The maximum number of entries (begin and end date pairs) that
     the DST Table can contain within the device.
     
     As of July 2007, devices used within the United States only require 
     1 entry when using the generic begin and end date method.
     
     <informative>It is expected that, for devices using the absolute date 
     method, the device would need to support at least 1 entry per year 
     programmed. 
For multi-step DST transitions, a minimum of 2 rows are required (see Annex A.2.1 Figure 6). 
More than one row may be required if absolute date method (see Section 2.4.8.2.2) is used for more than one year, or if more than one time change is implemented in a given year. 
 
<Superseded by> CLOCK-MIB.fdClockDstMaxEntries (ISO 20684-7)
<Informative> The replacement object has a range of Unsigned32
     <Object Identifier> 1.3.6.1.4.1.1206.4.2.6.3.7.1"
::= { daylightSavingNode 1 }

maxDaylightSavingEntries · mandatory

maxDaylightSavingEntries      OBJECT-TYPE
SYNTAX INTEGER (1..100)
ACCESS read-only
STATUS mandatory
DESCRIPTION
    "<Definition> The maximum number of entries (begin and end date pairs) that
       the DST Table can contain within the device.

        As of July 2007, devices used within the United States only require
        1 entry when using the generic begin and end date method.

     <informative>It is expected that, for devices using the absolute date
     method, the device would need to support at least 1 entry per year
     programmed.
For multi-step DST transitions, a minimum of 2 rows are required (see Annex
A.2.1 Figure 6).
More than one row may be required if absolute date method (see Section
2.4.8.2.2) is used for more than one year, or if more than one time change is
implemented in a given year.

     <Object Identifier> 1.3.6.1.4.1.1206.4.2.6.3.7.1"
::= { daylightSavingNode 1 }

Meaning

Descriptions

3 unique

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

Description 1

<Definition> The maximum number of entries (begin and end date pairs) that the DST Table can contain within the device. As of July 2007, devices used within the United States only require 1 entry when using the generic begin and end date method. <Informative>It is expected that, for devices using the absolute date method, the device would need to support at least 1 entry per year programmed. For multi-step DST transitions, a minimum of 2 rows are required (see Annex A.2.1 Figure 6). More than one row may be required if absolute date method (see Section 2.4.8.2.2) is used for more than one year, or if more than one time change is implemented in a given year. <Superseded by> ISO26048-1-Clock.fdClockDstMaxEntries (ISO 26048-1) <Informative> The replacement object has a range of Unsigned32 <Object Identifier> 1.3.6.1.4.1.1206.4.2.6.3.7.1

Sources for this description

NTCIP published standard MIB annexes (reviewed modules)

See 1 matching source record

Description 2

<Definition> The maximum number of entries (begin and end date pairs) that the DST Table can contain within the device. As of July 2007, devices used within the United States only require 1 entry when using the generic begin and end date method. <informative>It is expected that, for devices using the absolute date method, the device would need to support at least 1 entry per year programmed. For multi-step DST transitions, a minimum of 2 rows are required (see Annex A.2.1 Figure 6). More than one row may be required if absolute date method (see Section 2.4.8.2.2) is used for more than one year, or if more than one time change is implemented in a given year. <Superseded by> CLOCK-MIB.fdClockDstMaxEntries (ISO 20684-7) <Informative> The replacement object has a range of Unsigned32 <Object Identifier> 1.3.6.1.4.1.1206.4.2.6.3.7.1

Sources for this description

ITE public NTCIP working repository MIBs

See 1 matching source record

Description 3

<Definition> The maximum number of entries (begin and end date pairs) that the DST Table can contain within the device. As of July 2007, devices used within the United States only require 1 entry when using the generic begin and end date method. <informative>It is expected that, for devices using the absolute date method, the device would need to support at least 1 entry per year programmed. For multi-step DST transitions, a minimum of 2 rows are required (see Annex A.2.1 Figure 6). More than one row may be required if absolute date method (see Section 2.4.8.2.2) is used for more than one year, or if more than one time change is implemented in a given year. <Object Identifier> 1.3.6.1.4.1.1206.4.2.6.3.7.1

Sources for this description

NTCIP published standard MIB annexes (reviewed modules)

See 1 matching source record

Evidence

Source records

3 records

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

Records for description 1NTCIP published standard MIB annexes (reviewed modules)1 record · 1 source

Description 1

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

Status in source: unconfirmed.

Names: maxDaylightSavingEntries

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "maxDaylightSavingEntries",
    "OBJECT-TYPE",
    "SYNTAX",
    "Integer32",
    "(",
    "1",
    ".",
    ".",
    "100",
    ")",
    "UNITS",
    [
      "literal",
      "22656e747269657322"
    ],
    "MAX-ACCESS",
    "read-only",
    "STATUS",
    "deprecated",
    "DESCRIPTION",
    "\"<Definition> The maximum number of entries (begin and end date pairs) that the DST Table can contain within the device. As of July 2007, devices used within the United States only require 1 entry when using the generic begin and end date method. <Informative>It is expected that, for devices using the absolute date method, the device would need to support at least 1 entry per year programmed. For multi-step DST transitions, a minimum of 2 rows are required (see Annex A.2.1 Figure 6). More than one row may be required if absolute date method (see Section 2.4.8.2.2) is used for more than one year, or if more than one time change is implemented in a given year. <Superseded by> ISO26048-1-Clock.fdClockDstMaxEntries (ISO 26048-1) <Informative> The replacement object has a range of Unsigned32 <Object Identifier> 1.3.6.1.4.1.1206.4.2.6.3.7.1\"",
    "::=",
    "{",
    "daylightSavingNode",
    "1",
    "}"
  ],
  "syntax_tree": [
    [
      "SimpleSyntax",
      "Integer32",
      [
        "integerSubType",
        [
          [
            1,
            100
          ]
        ]
      ]
    ],
    [
      "UNITS",
      "entries"
    ],
    [
      "MaxAccessPart",
      "read-only"
    ],
    [
      "Status",
      "deprecated"
    ],
    [
      "DESCRIPTION",
      "<Definition> The maximum number of entries (begin and end date pairs) that the DST Table can contain within the device. As of July 2007, devices used within the United States only require 1 entry when using the generic begin and end date method. <Informative>It is expected that, for devices using the absolute date method, the device would need to support at least 1 entry per year programmed. For multi-step DST transitions, a minimum of 2 rows are required (see Annex A.2.1 Figure 6). More than one row may be required if absolute date method (see Section 2.4.8.2.2) is used for more than one year, or if more than one time change is implemented in a given year. <Superseded by> ISO26048-1-Clock.fdClockDstMaxEntries (ISO 26048-1) <Informative> The replacement object has a range of Unsigned32 <Object Identifier> 1.3.6.1.4.1.1206.4.2.6.3.7.1"
    ],
    null,
    null,
    null,
    null
  ]
}
Records for description 2ITE public NTCIP working repository MIBs1 record · 1 source

Description 2

maxDaylightSavingEntries · deprecatedITE public NTCIP working repository MIBs1 source

Status in source: deprecated.

Names: maxDaylightSavingEntries

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "maxDaylightSavingEntries",
    "OBJECT-TYPE",
    "SYNTAX",
    "Integer32",
    "(",
    "1",
    ".",
    ".",
    "100",
    ")",
    "UNITS",
    [
      "literal",
      "22656e747269657322"
    ],
    "MAX-ACCESS",
    "read-only",
    "STATUS",
    "deprecated",
    "DESCRIPTION",
    "\"<Definition> The maximum number of entries (begin and end date pairs) that the DST Table can contain within the device. As of July 2007, devices used within the United States only require 1 entry when using the generic begin and end date method. <informative>It is expected that, for devices using the absolute date method, the device would need to support at least 1 entry per year programmed. For multi-step DST transitions, a minimum of 2 rows are required (see Annex A.2.1 Figure 6). More than one row may be required if absolute date method (see Section 2.4.8.2.2) is used for more than one year, or if more than one time change is implemented in a given year. <Superseded by> CLOCK-MIB.fdClockDstMaxEntries (ISO 20684-7) <Informative> The replacement object has a range of Unsigned32 <Object Identifier> 1.3.6.1.4.1.1206.4.2.6.3.7.1\"",
    "::=",
    "{",
    "daylightSavingNode",
    "1",
    "}"
  ],
  "syntax_tree": [
    [
      "SimpleSyntax",
      "Integer32",
      [
        "integerSubType",
        [
          [
            1,
            100
          ]
        ]
      ]
    ],
    [
      "UNITS",
      "entries"
    ],
    [
      "MaxAccessPart",
      "read-only"
    ],
    [
      "Status",
      "deprecated"
    ],
    [
      "DESCRIPTION",
      "<Definition> The maximum number of entries (begin and end date pairs) that the DST Table can contain within the device. As of July 2007, devices used within the United States only require 1 entry when using the generic begin and end date method. <informative>It is expected that, for devices using the absolute date method, the device would need to support at least 1 entry per year programmed. For multi-step DST transitions, a minimum of 2 rows are required (see Annex A.2.1 Figure 6). More than one row may be required if absolute date method (see Section 2.4.8.2.2) is used for more than one year, or if more than one time change is implemented in a given year. <Superseded by> CLOCK-MIB.fdClockDstMaxEntries (ISO 20684-7) <Informative> The replacement object has a range of Unsigned32 <Object Identifier> 1.3.6.1.4.1.1206.4.2.6.3.7.1"
    ],
    null,
    null,
    null,
    null
  ]
}
Records for description 3NTCIP published standard MIB annexes (reviewed modules)1 record · 1 source

Description 3

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

Status in source: mandatory.

Names: maxDaylightSavingEntries

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "maxDaylightSavingEntries",
    "OBJECT-TYPE",
    "SYNTAX",
    "INTEGER",
    "(",
    "1",
    ".",
    ".",
    "100",
    ")",
    "ACCESS",
    "read-only",
    "STATUS",
    "mandatory",
    "DESCRIPTION",
    "\"<Definition> The maximum number of entries (begin and end date pairs) that the DST Table can contain within the device. As of July 2007, devices used within the United States only require 1 entry when using the generic begin and end date method. <informative>It is expected that, for devices using the absolute date method, the device would need to support at least 1 entry per year programmed. For multi-step DST transitions, a minimum of 2 rows are required (see Annex A.2.1 Figure 6). More than one row may be required if absolute date method (see Section 2.4.8.2.2) is used for more than one year, or if more than one time change is implemented in a given year. <Object Identifier> 1.3.6.1.4.1.1206.4.2.6.3.7.1\"",
    "::=",
    "{",
    "daylightSavingNode",
    "1",
    "}"
  ],
  "syntax_tree": [
    [
      "SimpleSyntax",
      "INTEGER",
      [
        "integerSubType",
        [
          [
            1,
            100
          ]
        ]
      ]
    ],
    null,
    [
      "MaxAccessPart",
      "read-only"
    ],
    [
      "Status",
      "mandatory"
    ],
    [
      "DESCRIPTION",
      "<Definition> The maximum number of entries (begin and end date pairs) that the DST Table can contain within the device. As of July 2007, devices used within the United States only require 1 entry when using the generic begin and end date method. <informative>It is expected that, for devices using the absolute date method, the device would need to support at least 1 entry per year programmed. For multi-step DST transitions, a minimum of 2 rows are required (see Annex A.2.1 Figure 6). More than one row may be required if absolute date method (see Section 2.4.8.2.2) is used for more than one year, or if more than one time change is implemented in a given year. <Object Identifier> 1.3.6.1.4.1.1206.4.2.6.3.7.1"
    ],
    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 (1)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.1206.4.2.6.3.7.2 dstTable113