OID reference
1.3.6.1.4.1.1206.4.2.3.5.8.1.9
<Definition> Indicates the current state of the message. This state-machine allows for defining a message, validating a message, and deleting a message. See Section 4.3.4 for additional details regarding the state-machine. <Object Identifier> 1.3.6.1.4.1.1206.4.2.3.5.8.1.9
Identification
{1 3 6 1 4 1 1206 4 2 3 5 8 1 9}
Definitions may combine these properties differently.
Numbers refer to source variants above. Each value is shown only for variants that define it.
| Value | Name | Source variants |
|---|---|---|
| 1 | notUsed | 1, 2 |
| 2 | modifying | 1, 2 |
| 3 | validating | 1, 2 |
| 4 | valid | 1, 2 |
| 5 | error | 1, 2 |
| 6 | modifyReq | 1, 2 |
| 7 | validateReq | 1, 2 |
| 8 | notUsedReq | 1, 2 |
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-v0305, the row index consists of these components in order:
dmsMessageMemoryType (INTEGER): one numeric subidentifier for the non-negative value.dmsMessageNumber (INTEGER): one numeric subidentifier for the non-negative value.An instance has the form .1.3.6.1.4.1.1206.4.2.3.5.8.1.9.<dmsMessageMemoryType>.<dmsMessageNumber>. Use values 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.3.5.8.1.9
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 4 distinct definitions; some records may not include a definition.
dmsMessageStatus OBJECT-TYPE
SYNTAX INTEGER {
notUsed (1),
modifying (2),
validating (3),
valid (4),
error (5),
modifyReq (6),
validateReq (7),
notUsedReq (8) }
ACCESS read-write
STATUS mandatory
DESCRIPTION
"<Definition> Indicates the current state of the message. This state-machine allows for defining a message, validating a message, and deleting a message. See Section 4.3.4 for additional details regarding the state-machine.
<Object Identifier> 1.3.6.1.4.1.1206.4.2.3.5.8.1.9"
::= { dmsMessageEntry 9 }dmsMessageStatus OBJECT-TYPE
SYNTAX INTEGER {
notUsed (1),
modifying (2),
validating (3),
valid (4),
error (5),
modifyReq (6),
validateReq (7),
notUsedReq (8) }
ACCESS read-write
STATUS mandatory
DESCRIPTION
"<Definition> Indicates the current state of the message. This state-machine
allows for defining a message, validating a message, and deleting a message.
See Section 4.3.4 for additional details regarding the state-machine.
<Object Identifier> 1.3.6.1.4.1.1206.4.2.3.5.8.1.9"
::= { dmsMessageEntry 9 }dmsMessageStatus OBJECT-TYPE
SYNTAX INTEGER {
notUsed (1),
modifying (2),
validating (3),
valid (4),
error (5),
modifyReq (6),
validateReq (7),
notUsedReq (8) }
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"<Definition> Indicates the current state of the message. This state-machine
allows for defining a message, validating a message, and deleting a message.
See Section 4.3.4 for additional details regarding the state-machine.
<Parameter Type> Configuration
<Object Identifier> 1.3.6.1.4.1.1206.4.2.3.5.8.1.9"
::= { dmsMessageEntry 9 }dmsMessageStatus OBJECT-TYPE
SYNTAX INTEGER {
notUsed (1),
modifying (2),
validating (3),
valid (4),
error (5),
modifyReq (6),
validateReq (7),
notUsedReq (8) }
ACCESS read-write
STATUS mandatory
DESCRIPTION “Indicates the current state of the message. This state-machine allows for defining a
message, validating a message, and freeing message use.”
--The enumerated values can be divided into two types, state values and command values. State
--values can only be read, a GenErr shall occur if a SET is attempted. Command values can be
--written to, and will cause a state change if accepted, and thus cannot be returned. The states
--and commands are defined as follows:
--notUsed: This is a state value and indicates that the row does not contain any valid
--message data. Controller memory may or may not be released to free memory pool in this
--state. Reading an object from a row when this object is set to notUsed in undetermined, i.e., last
--contents, or random data may be returned. Setting any object (except this object) for a row that
--is notUsed shall return a GenError. The only valid command in this state is modifyReq.
--modifying: This is a state value and indicates that the row is being modified to define
--a message. Modifying any objects (except this object) can only be done when the row is in this
--state, otherwise a GenError shall be returned. The valid commands in this state is validateReq
--and notUsedReq.
--validating: This is a state value and indicates that the controller is validating all of the message
--data for the row. When validation is complete, the controller will automatically change the state
--to either valid (message data is good), or error (some error found within the message data). The
--only valid command is the notUsedReq command, which shall set the state to notUsed or return
--a GenErr.
--valid: This is a state and indicates the message data is valid and the message can be
--activated. Activation of a message cannot occur in any other state. The valid commands in this
--state are notUsedReq and modifyReq.
--error: This is a state and indicates that an error was detected during the validation
--process. The valid commands in this state are modifyReq and notUsedReq.
--modifyReq: This is a command that indicates the user wishes to modify the row to define a
--message. A GenError may be returned if the controller is in the notUsed state and there is
--insufficient memory to define a new message. A successful request will change the state of the
--row to modifying. An unsuccessful request will leave the row in the same state as it was prior to
--the command. This command can be issued while in the notUsed, valid and error states.
--validateReq: This is a command that indicates the user wishes to validate the current message
--data. This command can only be issued while the row is in the modify state, else a GenError
--shall be returned. A successful request will change the state of the row to validating. An
--unsuccessful request will leave the row in the same state as it was prior to the command.
--notUsedReq: This is a command that indicates the user wishes to end use of the current
--message data. This command can be issued while the row is in the modify, validating, valid,
--and error states. A successful request will change the state of the row to notUsed. An
--unsuccessful request will leave the row in the same state as it was prior to the command.
::= {dmsMessageEntry 9}
Meaning
Identical descriptions are grouped. Different wording and device-specific notes are retained.
Description 1
<Definition> Indicates the current state of the message. This state-machine allows for defining a message, validating a message, and deleting a message. See Section 4.3.4 for additional details regarding the state-machine. <Object Identifier> 1.3.6.1.4.1.1206.4.2.3.5.8.1.9
ITE public NTCIP working repository MIBsNTCIP published standard MIB annexes (reviewed modules)
Description 2
<Definition> Indicates the current state of the message. This state-machine allows for defining a message, validating a message, and deleting a message. See Section 4.3.4 for additional details regarding the state-machine. <Parameter Type> Configuration <Object Identifier> 1.3.6.1.4.1.1206.4.2.3.5.8.1.9
Description 3
Indicates the current state of the message. This state-machine allows for defining a message, validating a message, and freeing message use.
NTCIP published standard MIB annexes (reviewed modules)
Evidence
Matching descriptions are grouped; open a group to compare definitions and supporting files.
Status in source: mandatory.
Names: dmsMessageStatus
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"dmsMessageStatus",
"OBJECT-TYPE",
"SYNTAX",
"INTEGER",
"{",
"notUsed",
"(",
"1",
")",
",",
"modifying",
"(",
"2",
")",
",",
"validating",
"(",
"3",
")",
",",
"valid",
"(",
"4",
")",
",",
"error",
"(",
"5",
")",
",",
"modifyReq",
"(",
"6",
")",
",",
"validateReq",
"(",
"7",
")",
",",
"notUsedReq",
"(",
"8",
")",
"}",
"ACCESS",
"read-write",
"STATUS",
"mandatory",
"DESCRIPTION",
"\"<Definition> Indicates the current state of the message. This state-machine allows for defining a message, validating a message, and deleting a message. See Section 4.3.4 for additional details regarding the state-machine. <Object Identifier> 1.3.6.1.4.1.1206.4.2.3.5.8.1.9\"",
"::=",
"{",
"dmsMessageEntry",
"9",
"}"
],
"syntax_tree": [
[
"SimpleSyntax",
"INTEGER",
[
"enumSpec",
[
[
"notUsed",
1
],
[
"modifying",
2
],
[
"validating",
3
],
[
"valid",
4
],
[
"error",
5
],
[
"modifyReq",
6
],
[
"validateReq",
7
],
[
"notUsedReq",
8
]
]
]
],
null,
[
"MaxAccessPart",
"read-write"
],
[
"Status",
"mandatory"
],
[
"DESCRIPTION",
"<Definition> Indicates the current state of the message. This state-machine allows for defining a message, validating a message, and deleting a message. See Section 4.3.4 for additional details regarding the state-machine. <Object Identifier> 1.3.6.1.4.1.1206.4.2.3.5.8.1.9"
],
null,
null,
null,
null
]
}Module: NTCIP1203-v0305
See published definition above
{'RFC-1212': ['OBJECT-TYPE'], 'RFC1155-SMI': ['IpAddress', 'Counter'], 'RFC1213-MIB': ['DisplayString'], 'NTCIP8004v02': ['OwnerString', 'dms']}Source data warning: This original is published in an ITE NTCIP working repository. Repository publication does not establish that this particular revision is an adopted standard. Consult its native revision history and the NTCIP published standards catalog before implementation. Copyright and distribution notices are retained in the downloadable original.
Source data warning: Potentially inaccurate interpretation of historical NTCIP imports: the original references NTCIP8004v02, which is absent from the public repository snapshot. The numeric roots used here are the explicit assignments in normative Annex A.2 of published NTCIP 8004 v02 (2010), physical pages 43–44. This does not establish that every historical module revision is identical. The annex also prints enterprise instead of RFC 1155 enterprises and declares Protocols while referencing protocols; those spelling interpretations are disclosed. The original IMPORTS, numeric suffixes and definitions remain unchanged. Verify both originals before implementation.
· Download NTCIP_1203 — v03/1203v03A-06g.mibRelated source files and packages:
Module: NTCIP1203-v03-05
See published definition above
{'RFC-1212': ['OBJECT-TYPE'], 'NTCIP8004': ['OwnerString', 'dms'], 'RFC1155-SMI': ['IpAddress', 'Counter'], 'RFC1213-MIB': ['DisplayString']}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: The PDF prints an invalid ASN.1 module label (NTCIP1203 v03.05). The derived transcription uses an equal-length internal parsing label; this is not an OID registration or an alteration of any numeric assignment. The original label and full PDF are retained.
Source data warning: Potentially inaccurate interpretation of historical NTCIP namespace references: NTCIP8004. 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 NTCIP1203v03f.pdf — NTCIP1203-v03-05 (MIB transcription)Module: NTCIP1203-2005
{'RFC-1212': ['OBJECT-TYPE'], 'RFC1155-SMI': ['IpAddress', 'Counter'], 'RFC1213-MIB': ['DisplayString'], 'NTCIP8004-A-2004': ['OwnerString', 'dms']}Source data warning: Recovered from a file whose complete MIB does not parse. The original assignment and definition are preserved. Registration and implementation details may be inaccurate; consult the original file. Other damaged or unresolved declarations are not established registrations.
Source data warning: This record is transcribed from a published NTCIP MIB annex. The downloadable text is a derived transcription with page furniture and section headings masked; the unmodified original PDF is authoritative. Native definitions, DESCRIPTION and STATUS are retained. A published object definition does not establish support by any particular device.
Source data warning: Potentially inaccurate interpretation of historical NTCIP namespace references: NTCIP8004-A-2004. These exact source files require the reviewed bindings shown below. The numeric roots used here are the explicit assignments in normative Annex A.2 of published NTCIP 8004 v02 (2010), physical pages 43–44. This does not establish that every historical module revision is identical. The annex also prints enterprise instead of RFC 1155 enterprises and declares Protocols while referencing protocols; those spelling interpretations are disclosed. The original IMPORTS, numeric suffixes and definitions remain unchanged. Verify both originals before implementation.
· Download NTCIP1203v02-35a.pdf — NTCIP1203-2005 (MIB transcription)Status in source: unconfirmed.
Names: dmsMessageStatus
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"dmsMessageStatus",
"OBJECT-TYPE",
"SYNTAX",
"INTEGER",
"{",
"notUsed",
"(",
"1",
")",
",",
"modifying",
"(",
"2",
")",
",",
"validating",
"(",
"3",
")",
",",
"valid",
"(",
"4",
")",
",",
"error",
"(",
"5",
")",
",",
"modifyReq",
"(",
"6",
")",
",",
"validateReq",
"(",
"7",
")",
",",
"notUsedReq",
"(",
"8",
")",
"}",
"MAX-ACCESS",
"read-write",
"STATUS",
"current",
"DESCRIPTION",
"\"<Definition> Indicates the current state of the message. This state-machine allows for defining a message, validating a message, and deleting a message. See Section 4.3.4 for additional details regarding the state-machine. <Parameter Type> Configuration <Object Identifier> 1.3.6.1.4.1.1206.4.2.3.5.8.1.9\"",
"::=",
"{",
"dmsMessageEntry",
"9",
"}"
],
"syntax_tree": [
[
"SimpleSyntax",
"INTEGER",
[
"enumSpec",
[
[
"notUsed",
1
],
[
"modifying",
2
],
[
"validating",
3
],
[
"valid",
4
],
[
"error",
5
],
[
"modifyReq",
6
],
[
"validateReq",
7
],
[
"notUsedReq",
8
]
]
]
],
null,
[
"MaxAccessPart",
"read-write"
],
[
"Status",
"current"
],
[
"DESCRIPTION",
"<Definition> Indicates the current state of the message. This state-machine allows for defining a message, validating a message, and deleting a message. See Section 4.3.4 for additional details regarding the state-machine. <Parameter Type> Configuration <Object Identifier> 1.3.6.1.4.1.1206.4.2.3.5.8.1.9"
],
null,
null,
null,
null
]
}Module: NTCIP1203-Dms
See published definition above
{'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.5.8.1.9, but its DESCRIPTION explicitly lists 1.3.6.1.4.1.1206.4.2.3.5.8.1.9. 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.mibStatus in source: mandatory.
Names: dmsMessageStatus
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"dmsMessageStatus",
"OBJECT-TYPE",
"SYNTAX",
"INTEGER",
"{",
"notUsed",
"(",
"1",
")",
",",
"modifying",
"(",
"2",
")",
",",
"validating",
"(",
"3",
")",
",",
"valid",
"(",
"4",
")",
",",
"error",
"(",
"5",
")",
",",
"modifyReq",
"(",
"6",
")",
",",
"validateReq",
"(",
"7",
")",
",",
"notUsedReq",
"(",
"8",
")",
"}",
"ACCESS",
"read-write",
"STATUS",
"mandatory",
"DESCRIPTION",
"“",
"Indicates",
"the",
"current",
"state",
"of",
"the",
"message",
".",
"This",
"state-machine",
"allows",
"for",
"defining",
"a",
"message",
",",
"validating",
"a",
"message",
",",
"and",
"freeing",
"message",
"use",
".",
"”",
"::=",
"{",
"dmsMessageEntry",
"9",
"}"
],
"syntax_tree": [
[
"SimpleSyntax",
"INTEGER",
[
"enumSpec",
[
[
"notUsed",
1
],
[
"modifying",
2
],
[
"validating",
3
],
[
"valid",
4
],
[
"error",
5
],
[
"modifyReq",
6
],
[
"validateReq",
7
],
[
"notUsedReq",
8
]
]
]
],
null,
[
"MaxAccessPart",
"read-write"
],
[
"Status",
"mandatory"
],
[
"DESCRIPTION",
"Indicates the current state of the message. This state-machine allows for defining a message, validating a message, and freeing message use."
],
null,
null,
null,
null
]
}Module: DMS-MIB
See published definition above
{'TMIB': ['OwnerString', 'devices'], 'NEMA_SMI': ['experimental'], 'RFC-1212': ['OBJECT-TYPE'], 'RFC1155-SMI': ['IpAddress', 'Counter'], 'RFC1213-MIB': ['DisplayString']}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 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: Potentially inaccurate interpretation of historical NTCIP namespace references: TMIB. 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.
Source data warning: Unconfirmed interpretation of a historical NTCIP import: NTCIP 1203:1997 imports experimental from NEMA_SMI, but the retained original NEMA_SMI defines nemaExperimental instead. Section 2.10 explicitly locates these auxiliary I/O objects under the nema-experimental node. Here only that imported spelling is interpreted as the explicitly assigned nemaExperimental value. The original exp-global suffix 1 and all child numbers are retained. The later NTCIP 1201 v03 compatibility discussion also compares the old experimental spelling with nemaExperimental, but prints expGlobal suffix 2; that disagreement is not silently corrected or treated as proof that both historical branches are registered. These entries may be inaccurate; verify the linked original editions and your device. Native SMI STATUS is preserved separately.
nema OBJECT IDENTIFIER ::= { enterprises 1206 }nemaExperimental OBJECT IDENTIFIER ::= { nema 2 }
Related source files and packages:
Registration
| OID | Name | Direct children | Descendants | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.1206.4.2.3.5.8.1.1 | dmsMessageMemoryType | 0 | 0 | |
| 1.3.6.1.4.1.1206.4.2.3.5.8.1.2 | dmsMessageNumber | 0 | 0 | |
| 1.3.6.1.4.1.1206.4.2.3.5.8.1.3 | dmsMessageMultiString | 0 | 0 | |
| 1.3.6.1.4.1.1206.4.2.3.5.8.1.4 | dmsMessageOwner | 0 | 0 | |
| 1.3.6.1.4.1.1206.4.2.3.5.8.1.5 | dmsMessageCRC | 0 | 0 | |
| 1.3.6.1.4.1.1206.4.2.3.5.8.1.6 | dmsMessageBeacon | 0 | 0 | |
| 1.3.6.1.4.1.1206.4.2.3.5.8.1.7 | dmsMessagePixelService | 0 | 0 | |
| 1.3.6.1.4.1.1206.4.2.3.5.8.1.8 | dmsMessageRunTimePriority | 0 | 0 |