<Definition> The duration required to complete one entire flash cycle. The flash cycle zero-point shall be based on the previously occuring local midnight, if the local clock feature is supported, and midnight UTC if not. The plan cycle shall be a multiple of dmsBeaconFlashResolution. <Infomative> Longer flash cycles allow lights to flash in order across multiple beacons. Coordinating the flash cycles at local midnight allows coordinated flashing across multiple devices. It is recommended that the cycle length is a denominator of 86,400,000 to prevent cycle anomalies at midnight on a regular basis. Ideally, the cycle length should be a denominator of 1,000 to prevent anomailes under nearly all conditions (e.g., leap seconds). <Parameter Type> Configuration <Object Identifier> 1.3.6.1.4.1.1206.4.2.3.1.15.4.1.3
OID reference
dmsBeaconPlanCycle
1.3.6.1.4.1.1206.4.2.6.1.15.4.1.3
Description
<Definition> The duration required to complete one entire flash cycle. The flash cycle zero-point shall be based on the previously occuring local midnight, if the local clock feature is supported, and midnight UTC if not. The plan cycle shall be a multiple of dmsBeaconFlashResolution. <Infomative> Longer flash cycles …
Identification
Identifier and names
- Parent
- 1.3.6.1.4.1.1206.4.2.6.1.15.4.1 (dmsBeaconPlanEntry)
- Node code
- 3
- Node name
- dmsBeaconPlanCycle
- Category
- SNMP management object
- Numeric OID
- 1.3.6.1.4.1.1206.4.2.6.1.15.4.1.3
- URN notation
- urn:oid:1.3.6.1.4.1.1206.4.2.6.1.15.4.1.3
ASN.1, OID-IRI and named path variants
- ASN.1 notation
-
{1 3 6 1 4 1 1206 4 2 6 1 15 4 1 3}
- {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) nema(1206) transportation(4) devices(2) global(6) globalConfiguration(1) dmsBeacon(15) dmsBeaconPlanTable(4) dmsBeaconPlanEntry(1) dmsBeaconPlanCycle(3)}
- {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) nema(1206) transportation(4) devices(2) global(6) dmsSignCfg(1) dmsBeacon(15) dmsBeaconPlanTable(4) dmsBeaconPlanEntry(1) dmsBeaconPlanCycle(3)}
- {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) nema(1206) transportation(4) devices(2) dms(6) globalConfiguration(1) dmsBeacon(15) dmsBeaconPlanTable(4) dmsBeaconPlanEntry(1) dmsBeaconPlanCycle(3)}
- {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) nema(1206) transportation(4) devices(2) dms(6) dmsSignCfg(1) dmsBeacon(15) dmsBeaconPlanTable(4) dmsBeaconPlanEntry(1) dmsBeaconPlanCycle(3)}
- {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) nema(1206) transportation(4) devices(2) global(6) globalConfiguration(1) dmsBeacon(15) dmsBeaconPlanTable(4) dmsBeaconPlanEntry(1) dmsBeaconPlanCycle(3)}
- {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) nema(1206) transportation(4) devices(2) global(6) dmsSignCfg(1) dmsBeacon(15) dmsBeaconPlanTable(4) dmsBeaconPlanEntry(1) dmsBeaconPlanCycle(3)}
- {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) nema(1206) transportation(4) devices(2) dms(6) globalConfiguration(1) dmsBeacon(15) dmsBeaconPlanTable(4) dmsBeaconPlanEntry(1) dmsBeaconPlanCycle(3)}
- {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) nema(1206) transportation(4) devices(2) dms(6) dmsSignCfg(1) dmsBeacon(15) dmsBeaconPlanTable(4) dmsBeaconPlanEntry(1) dmsBeaconPlanCycle(3)}
- {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) nema(1206) transportation(4) devices(2) global(6) globalConfiguration(1) dmsBeacon(15) dmsBeaconPlanTable(4) dmsBeaconPlanEntry(1) dmsBeaconPlanCycle(3)}
- {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) nema(1206) transportation(4) devices(2) global(6) dmsSignCfg(1) dmsBeacon(15) dmsBeaconPlanTable(4) dmsBeaconPlanEntry(1) dmsBeaconPlanCycle(3)}
- {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) nema(1206) transportation(4) devices(2) dms(6) globalConfiguration(1) dmsBeacon(15) dmsBeaconPlanTable(4) dmsBeaconPlanEntry(1) dmsBeaconPlanCycle(3)}
- {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) nema(1206) transportation(4) devices(2) dms(6) dmsSignCfg(1) dmsBeacon(15) dmsBeaconPlanTable(4) dmsBeaconPlanEntry(1) dmsBeaconPlanCycle(3)}
- {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) nema(1206) transportation(4) devices(2) global(6) globalConfiguration(1) dmsBeacon(15) dmsBeaconPlanTable(4) dmsBeaconPlanEntry(1) dmsBeaconPlanCycle(3)}
- {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) nema(1206) transportation(4) devices(2) global(6) dmsSignCfg(1) dmsBeacon(15) dmsBeaconPlanTable(4) dmsBeaconPlanEntry(1) dmsBeaconPlanCycle(3)}
- {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) nema(1206) transportation(4) devices(2) dms(6) globalConfiguration(1) dmsBeacon(15) dmsBeaconPlanTable(4) dmsBeaconPlanEntry(1) dmsBeaconPlanCycle(3)}
- {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) nema(1206) transportation(4) devices(2) dms(6) dmsSignCfg(1) dmsBeacon(15) dmsBeaconPlanTable(4) dmsBeaconPlanEntry(1) dmsBeaconPlanCycle(3)}
- Additional combinations skipped.
- OID-IRI notation
- /1/3/6/1/4/1/1206/4/2/6/1/15/4/1/3
- /ISO/Identified-Organization/6/1/4/1/1206/4/2/6/1/15/4/1/3
- /ISO/3/6/1/4/1/1206/4/2/6/1/15/4/1/3
- Named path variants
- /iso/identified-organization/dod/internet/private/enterprise/1206/transportation/devices/global/globalConfiguration/dmsBeacon/dmsBeaconPlanTable/dmsBeaconPlanEntry/dmsBeaconPlanCycle
- /iso/identified-organization/dod/internet/private/enterprise/1206/transportation/devices/global/dmsSignCfg/dmsBeacon/dmsBeaconPlanTable/dmsBeaconPlanEntry/dmsBeaconPlanCycle
- /iso/identified-organization/dod/internet/private/enterprise/1206/transportation/devices/dms/globalConfiguration/dmsBeacon/dmsBeaconPlanTable/dmsBeaconPlanEntry/dmsBeaconPlanCycle
- /iso/identified-organization/dod/internet/private/enterprise/1206/transportation/devices/dms/dmsSignCfg/dmsBeacon/dmsBeaconPlanTable/dmsBeaconPlanEntry/dmsBeaconPlanCycle
- /iso/identified-organization/dod/internet/private/enterprise/nema/transportation/devices/global/globalConfiguration/dmsBeacon/dmsBeaconPlanTable/dmsBeaconPlanEntry/dmsBeaconPlanCycle
- /iso/identified-organization/dod/internet/private/enterprise/nema/transportation/devices/global/dmsSignCfg/dmsBeacon/dmsBeaconPlanTable/dmsBeaconPlanEntry/dmsBeaconPlanCycle
- /iso/identified-organization/dod/internet/private/enterprise/nema/transportation/devices/dms/globalConfiguration/dmsBeacon/dmsBeaconPlanTable/dmsBeaconPlanEntry/dmsBeaconPlanCycle
- /iso/identified-organization/dod/internet/private/enterprise/nema/transportation/devices/dms/dmsSignCfg/dmsBeacon/dmsBeaconPlanTable/dmsBeaconPlanEntry/dmsBeaconPlanCycle
- /iso/identified-organization/dod/internet/private/enterprises/1206/transportation/devices/global/globalConfiguration/dmsBeacon/dmsBeaconPlanTable/dmsBeaconPlanEntry/dmsBeaconPlanCycle
- /iso/identified-organization/dod/internet/private/enterprises/1206/transportation/devices/global/dmsSignCfg/dmsBeacon/dmsBeaconPlanTable/dmsBeaconPlanEntry/dmsBeaconPlanCycle
- /iso/identified-organization/dod/internet/private/enterprises/1206/transportation/devices/dms/globalConfiguration/dmsBeacon/dmsBeaconPlanTable/dmsBeaconPlanEntry/dmsBeaconPlanCycle
- /iso/identified-organization/dod/internet/private/enterprises/1206/transportation/devices/dms/dmsSignCfg/dmsBeacon/dmsBeaconPlanTable/dmsBeaconPlanEntry/dmsBeaconPlanCycle
- /iso/identified-organization/dod/internet/private/enterprises/nema/transportation/devices/global/globalConfiguration/dmsBeacon/dmsBeaconPlanTable/dmsBeaconPlanEntry/dmsBeaconPlanCycle
- /iso/identified-organization/dod/internet/private/enterprises/nema/transportation/devices/global/dmsSignCfg/dmsBeacon/dmsBeaconPlanTable/dmsBeaconPlanEntry/dmsBeaconPlanCycle
- /iso/identified-organization/dod/internet/private/enterprises/nema/transportation/devices/dms/globalConfiguration/dmsBeacon/dmsBeaconPlanTable/dmsBeaconPlanEntry/dmsBeaconPlanCycle
- /iso/identified-organization/dod/internet/private/enterprises/nema/transportation/devices/dms/dmsSignCfg/dmsBeacon/dmsBeaconPlanTable/dmsBeaconPlanEntry/dmsBeaconPlanCycle
- Additional combinations skipped.
SNMP properties
- Value type
- Unsigned32
- Units
- milliseconds
- Maximum access defined by MIB
- read-create
- Status in MIB
- current
- Default value
- 1000
- Allowed ranges
- 0–60000
Using this OID with SNMP
At least one MIB declaration places this object in a table row. A value belongs to a row instance; its suffix depends on the row's INDEX or AUGMENTS definition.
In NTCIP1203-Dms, the row index dmsBeaconPlanIndex is declared as Integer32. A non-negative index value is encoded as one numeric subidentifier. An instance has the form .1.3.6.1.4.1.1206.4.2.6.1.15.4.1.3.<dmsBeaconPlanIndex>. Use an index value actually present on the device and permitted by its MIB. Other definitions can differ.
snmpwalk [connection options] DEVICE .1.3.6.1.4.1.1206.4.2.6.1.15.4.1.3
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.
Published definition
The displayed source records contain one distinct definition. Compare its source records.
dmsBeaconPlanCycle OBJECT-TYPE
SYNTAX Unsigned32 (0..60000)
UNITS "milliseconds"
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"<Definition> The duration required to complete one entire flash cycle. The
flash cycle zero-point shall be based on the previously occuring local
midnight, if the local clock feature is supported, and midnight UTC if not.
The plan cycle shall be a multiple of dmsBeaconFlashResolution.
<Infomative> Longer flash cycles allow lights to flash in order across
multiple beacons. Coordinating the flash cycles at local midnight allows
coordinated flashing across multiple devices. It is recommended that the
cycle length is a denominator of 86,400,000 to prevent cycle anomalies at
midnight on a regular basis. Ideally, the cycle length should be a
denominator of 1,000 to prevent anomailes under nearly all conditions (e.g.,
leap seconds).
<Parameter Type> Configuration
<Object Identifier> 1.3.6.1.4.1.1206.4.2.3.1.15.4.1.3"
DEFVAL { 1000 }
::= { dmsBeaconPlanEntry 3 }
Meaning
Descriptions
Identical descriptions are grouped. Different wording and device-specific notes are retained.
Evidence
Source records
Matching descriptions are grouped; open a group to compare definitions and supporting files.
Records for description 1ITE public NTCIP working repository MIBs
dmsBeaconPlanCycle · unconfirmedITE public NTCIP working repository MIBs
Status in source: unconfirmed.
Names: dmsBeaconPlanCycle
Technical details
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"dmsBeaconPlanCycle",
"OBJECT-TYPE",
"SYNTAX",
"Unsigned32",
"(",
"0",
".",
".",
"60000",
")",
"UNITS",
[
"literal",
"226d696c6c697365636f6e647322"
],
"MAX-ACCESS",
"read-create",
"STATUS",
"current",
"DESCRIPTION",
"\"<Definition> The duration required to complete one entire flash cycle. The flash cycle zero-point shall be based on the previously occuring local midnight, if the local clock feature is supported, and midnight UTC if not. The plan cycle shall be a multiple of dmsBeaconFlashResolution. <Infomative> Longer flash cycles allow lights to flash in order across multiple beacons. Coordinating the flash cycles at local midnight allows coordinated flashing across multiple devices. It is recommended that the cycle length is a denominator of 86,400,000 to prevent cycle anomalies at midnight on a regular basis. Ideally, the cycle length should be a denominator of 1,000 to prevent anomailes under nearly all conditions (e.g., leap seconds). <Parameter Type> Configuration <Object Identifier> 1.3.6.1.4.1.1206.4.2.3.1.15.4.1.3\"",
"DEFVAL",
"{",
"1000",
"}",
"::=",
"{",
"dmsBeaconPlanEntry",
"3",
"}"
],
"syntax_tree": [
[
"ApplicationSyntax",
"Unsigned32",
[
"integerSubType",
[
[
0,
60000
]
]
]
],
[
"UNITS",
"milliseconds"
],
[
"MaxAccessPart",
"read-create"
],
[
"Status",
"current"
],
[
"DESCRIPTION",
"<Definition> The duration required to complete one entire flash cycle. The flash cycle zero-point shall be based on the previously occuring local midnight, if the local clock feature is supported, and midnight UTC if not. The plan cycle shall be a multiple of dmsBeaconFlashResolution. <Infomative> Longer flash cycles allow lights to flash in order across multiple beacons. Coordinating the flash cycles at local midnight allows coordinated flashing across multiple devices. It is recommended that the cycle length is a denominator of 86,400,000 to prevent cycle anomalies at midnight on a regular basis. Ideally, the cycle length should be a denominator of 1,000 to prevent anomailes under nearly all conditions (e.g., leap seconds). <Parameter Type> Configuration <Object Identifier> 1.3.6.1.4.1.1206.4.2.3.1.15.4.1.3"
],
null,
null,
null,
[
"DEFVAL",
1000
]
]
}- ITE public NTCIP working repository MIBs
· Publisher's source file: NTCIP-1203 — NTCIP1203-Dms.mib
Module: NTCIP1203-Dms
See published definition above
Module imports
{'SNMPv2-TC': ['TEXTUAL-CONVENTION', 'DisplayString', 'StorageType', 'RowStatus'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'OBJECT-IDENTITY', 'OBJECT-TYPE', 'Integer32', 'Unsigned32', 'Counter32', 'IpAddress'], 'SNMPv2-CONF': ['OBJECT-GROUP'], 'ISO26048-1-Srsa': ['fdSrsaTypeCode', 'fdSrsaPortIndex'], 'SNMP-FRAMEWORK-MIB': ['SnmpAdminString'], 'ISO26048-1-Global-TC': ['ITSDirection', 'ITSInteger8', 'ITSLatitude84', 'ITSLongitude84', 'ITSBitmap'], 'TRANSPORT-ADDRESS-MIB': ['TransportAddressType', 'TransportAddress'], 'NTCIP8004-Transportation': ['NtcipOwnerString', 'NtcipIntegerBitmap8', 'NtcipIntegerBitmap16', 'NtcipTwoColors', 'devices']}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: Published module-root disagreement: dms 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.3. All dependent assignments from this module require verification. No root number has been silently corrected.
Source data warning: Published source disagreement: this literal SMI assignment resolves to 1.3.6.1.4.1.1206.4.2.6.1.15.4.1.3, but its DESCRIPTION explicitly lists 1.3.6.1.4.1.1206.4.2.3.1.15.4.1.3. Both published numeric claims are retained as unconfirmed evidence. Neither value is presented as a verified correction or an independently confirmed registration; consult the original file and the applicable standard edition.
· Download NTCIP-1203 — NTCIP1203-Dms.mib
Registration
Registration authorities
First Registration Authority (inferred from ancestor 1.3.6.1.4.1.1206)
Siblings (4)
| OID | Name | Direct children | Descendants | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.1206.4.2.6.1.15.4.1.1 | dmsBeaconPlanIndex | 0 | 0 | |
| 1.3.6.1.4.1.1206.4.2.6.1.15.4.1.2 | dmsBeaconPlanDescr | 0 | 0 | |
| 1.3.6.1.4.1.1206.4.2.6.1.15.4.1.4 | dmsBeaconPlanStorageType | 0 | 0 | |
| 1.3.6.1.4.1.1206.4.2.6.1.15.4.1.5 | dmsBeaconPlanRowStatus | 0 | 0 |