OID reference
1.3.6.1.4.1.1206.4.2.6.2.5
<Definition> Indicates the horizontal distance from the center of one pixel to the center of the neighboring pixel in millimeters. The horizontal pitch on a character matrix DMS does not apply to the spacing between characters but does apply to the distance between pixels within a character. <Parameter Type> Status <O…
Identification
{1 3 6 1 4 1 1206 4 2 6 2 5}
Definitions may combine these properties differently.
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.2.5.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 7 distinct definitions; some records may not include a definition.
vmsHorizontalPitch OBJECT-TYPE
SYNTAX Integer32 (0..255)
UNITS "millimeters"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"<Definition> Indicates the horizontal distance from the center of one pixel
to the center of the neighboring pixel in millimeters. The horizontal pitch
on a character matrix DMS does not apply to the spacing between characters
but does apply to the distance between pixels within a character.
<Parameter Type> Status
<Object Identifier> 1.3.6.1.4.1.1206.4.2.3.2.5"
::= { vmsCfg 5 }dbMakeID OBJECT-TYPE
SYNTAX Integer32(0..255)
MAX-ACCESS read-only
STATUS deprecated
DESCRIPTION
"<Definition> This object is used to create unique transaction ID's for management stations to use when starting transactions using the dbCreateTransaction object. This object will be incremented by one every time it is read, so that different values will be returned for each read. Management stations wishing to start a transaction should first read the dbCreateTransaction object to verify that it is in the Normal state. If so then the management shall GET dbMakeID to obtain a transaction ID to use, then SET dbCreateTransaction to startCmd and dbTransactionID to the value just received. If the response to the SET operation is 'noError' then the management station has started a transaction. If the response to the SET operation is 'genError' then the management station should read the dbCreateTransaction and dbTransactionID objects to ensure that the error was not due to a communications retry. If the dbCreateTransaction is in the Transaction state, and the dbTransactionID is the same value returned by the read of this object, then the management station is the owner of the transaction. If the dbTransactionID does not match the value originally returned by this object, then the management station is not the owner of the transaction and must wait until the dbCreateTransaction object returns to the Normal state before attempting to start the transaction.
<Informative> This object was deprecated in NTCIP 12012 v02
<Object Identifier> 1.3.6.1.4.1.1206.4.2.6.2.5"
::= { globalDBManagement 5 }dbMakeID OBJECT-TYPE
SYNTAX INTEGER (0..255)
ACCESS read-only
STATUS deprecated
DESCRIPTION
"This object is used to create unique transaction ID’s for management stations
to use when starting transactions using the dbCreateTransaction object. This
object will be incremented by one every time it is read, so that different
values will be returned for each read. Management stations wishing to start a
transaction should first read the dbCreateTransaction object to verify that it
is in the Normal state. If so then the management shall GET dbMakeID to
obtain a transaction ID to use, then SET dbCreateTransaction to startCmd and
dbTransactionID to the value just received. If the response to the SET
operation is ‘noError’ then the management station has started a transaction.
If the response to the SET operation is ‘genError’ then the management station
should read the dbCreateTransaction and dbTransactionID objects to ensure that
the error was not due to a communications retry. If the dbCreateTransaction
is in the Transaction state, and the dbTransactionID is the same value
returned by the read of this object, then the management station is the owner
of the transaction. If the dbTransactionID does not match the value
originally returned by this object, then the management station is not the
owner of the transaction and must wait until the dbCreateTransaction object
returns to the Normal state before attempting to start the transaction.
<Object Identifier> 1.3.6.1.4.1.1206.4.2.6.2.5"
::= { globalDBManagement 5 }dbMakeID OBJECT-TYPE
SYNTAX INTEGER (0..255)
ACCESS read-only
STATUS deprecated
DESCRIPTION
"This object is used to create unique transaction ID's for management stations to use when starting transactions using the dbCreateTransaction object. This object will be incremented by one every time it is read, so that different values will be returned for each read. Management stations wishing to start a transaction should first read the dbCreateTransaction object to verify that it is in the Normal state. If so then the management shall GET dbMakeID to obtain a transaction ID to use, then SET dbCreateTransaction to startCmd and dbTransactionID to the value just received. If the response to the SET operation is 'noError' then the management station has started a transaction. If the response to the SET operation is 'genError' then the management station should read the dbCreateTransaction and dbTransactionID objects to ensure that the error was not due to a communications retry. If the dbCreateTransaction is in the Transaction state, and the dbTransactionID is the same value returned by the read of this object, then the management station is the owner of the transaction. If the dbTransactionID does not match the value originally returned by this object, then the management station is not the owner of the transaction and must wait until the dbCreateTransaction object returns to the Normal state before attempting to start the transaction."
::= { globalDBManagement 5 }dbMakeID OBJECT-TYPE
SYNTAX Integer32(0..255)
MAX-ACCESS read-only
STATUS deprecated
DESCRIPTION
"<Definition> This object is used to create unique transaction ID's for
management stations to use when starting transactions using the
dbCreateTransaction object. This object will be incremented by one every
time it is read, so that different values will be returned for each read.
Management stations wishing to start a transaction should first read the
dbCreateTransaction object to verify that it is in the Normal state. If so
then the management shall GET dbMakeID to obtain a transaction ID to use,
then SET dbCreateTransaction to startCmd and dbTransactionID to the value
just received. If the response to the SET operation is 'noError' then the
management station has started a transaction. If the response to the SET
operation is 'genError' then the management station should read the
dbCreateTransaction and dbTransactionID objects to ensure that the error
was not due to a communications retry. If the dbCreateTransaction is in the
Transaction state, and the dbTransactionID is the same value returned by
the read of this object, then the management station is the owner of the
transaction. If the dbTransactionID does not match the value originally
returned by this object, then the management station is not the owner of
the transaction and must wait until the dbCreateTransaction object returns
to the Normal state before attempting to start the transaction.
<Informative> This object was deprecated in NTCIP 1201 v02
<Object Identifier> 1.3.6.1.4.1.1206.4.2.6.2.5"
::= { globalDBManagement 5 }dbMakeID OBJECT-TYPE
SYNTAX INTEGER (0..255)
ACCESS read-only
STATUS deprecated
DESCRIPTION
"This object is used to create unique transaction ID’s for management stations
to use when starting transactions using the dbCreateTransaction object. This
object will be incremented by one every time it is read, so that different
values will be returned for each read. Management stations wishing to start a
transaction should first read the dbCreateTransaction object to verify that it
is in the Normal state. If so then the management shall GET dbMakeID to
obtain a transaction ID to use, then SET dbCreateTransaction to startCmd and
dbTransactionID to the value just received. If the response to the SET
operation is ‘noError’ then the management station has started a transaction.
If the response to the SET operation is ‘genError’ then the management station
should read the dbCreateTransaction and dbTransactionID objects to ensure that
the error was not due to a communications retry. If the dbCreateTransaction
is in the Transaction state, and the dbTransactionID is the same value
returned by the read of this object, then the management station is the owner
of the transaction. If the dbTransactionID does not match the value
originally returned by this object, then the management station is not the
owner of the transaction and must wait until the dbCreateTransaction object
returns to the Normal state before attempting to start the transaction."
::= { globalDBManagement 5 }dbMakeID OBJECT-TYPE
SYNTAX INTEGER (0..255)
ACCESS read-only
STATUS deprecated
DESCRIPTION
"This object is used to create unique transaction ID’s for management stations to use when starting
transactions using the dbCreateTransaction object. This object will be incremented by one every time it
is read, so that different values will be returned for each read. Management stations wishing to start a
transaction should first read the dbCreateTransaction object to verify that it is in the Normal state. If so
then the management shall GET dbMakeID to obtain a transaction ID to use, then SET
dbCreateTransaction to startCmd and dbTransactionID to the value just received. If the response to the
SET operation is ‘noError’ then the management station has started a transaction. If the response to the
SET operation is ‘genError’ then the management station should read the dbCreateTransaction and
dbTransactionID objects to ensure that the error was not due to a communications retry. If the
dbCreateTransaction is in the Transaction state, and the dbTransactionID is the same value returned by
the read of this object, then the management station is the owner of the transaction. If the
dbTransactionID does not match the value originally returned by this object, then the management station
is not the owner of the transaction and must wait until the dbCreateTransaction object returns to the
Normal state before attempting to start the transaction."
::= { globalDBManagement 5 }
Meaning
Identical descriptions are grouped. Different wording and device-specific notes are retained.
Description 1
<Definition> Indicates the horizontal distance from the center of one pixel to the center of the neighboring pixel in millimeters. The horizontal pitch on a character matrix DMS does not apply to the spacing between characters but does apply to the distance between pixels within a character. <Parameter Type> Status <Object Identifier> 1.3.6.1.4.1.1206.4.2.3.2.5
Description 2
<Definition> This object is used to create unique transaction ID's for management stations to use when starting transactions using the dbCreateTransaction object. This object will be incremented by one every time it is read, so that different values will be returned for each read. Management stations wishing to start a transaction should first read the dbCreateTransaction object to verify that it is in the Normal state. If so then the management shall GET dbMakeID to obtain a transaction ID to use, then SET dbCreateTransaction to startCmd and dbTransactionID to the value just received. If the response to the SET operation is 'noError' then the management station has started a transaction. If the response to the SET operation is 'genError' then the management station should read the dbCreateTransaction and dbTransactionID objects to ensure that the error was not due to a communications retry. If the dbCreateTransaction is in the Transaction state, and the dbTransactionID is the same value returned by the read of this object, then the management station is the owner of the transaction. If the dbTransactionID does not match the value originally returned by this object, then the management station is not the owner of the transaction and must wait until the dbCreateTransaction object returns to the Normal state before attempting to start the transaction. <Informative> This object was deprecated in NTCIP 12012 v02 <Object Identifier> 1.3.6.1.4.1.1206.4.2.6.2.5
Description 3
This object is used to create unique transaction ID’s for management stations to use when starting transactions using the dbCreateTransaction object. This object will be incremented by one every time it is read, so that different values will be returned for each read. Management stations wishing to start a transaction should first read the dbCreateTransaction object to verify that it is in the Normal state. If so then the management shall GET dbMakeID to obtain a transaction ID to use, then SET dbCreateTransaction to startCmd and dbTransactionID to the value just received. If the response to the SET operation is ‘noError’ then the management station has started a transaction. If the response to the SET operation is ‘genError’ then the management station should read the dbCreateTransaction and dbTransactionID objects to ensure that the error was not due to a communications retry. If the dbCreateTransaction is in the Transaction state, and the dbTransactionID is the same value returned by the read of this object, then the management station is the owner of the transaction. If the dbTransactionID does not match the value originally returned by this object, then the management station is not the owner of the transaction and must wait until the dbCreateTransaction object returns to the Normal state before attempting to start the transaction. <Object Identifier> 1.3.6.1.4.1.1206.4.2.6.2.5
NTCIP published standard MIB annexes (reviewed modules)
Description 4
This object is used to create unique transaction ID's for management stations to use when starting transactions using the dbCreateTransaction object. This object will be incremented by one every time it is read, so that different values will be returned for each read. Management stations wishing to start a transaction should first read the dbCreateTransaction object to verify that it is in the Normal state. If so then the management shall GET dbMakeID to obtain a transaction ID to use, then SET dbCreateTransaction to startCmd and dbTransactionID to the value just received. If the response to the SET operation is 'noError' then the management station has started a transaction. If the response to the SET operation is 'genError' then the management station should read the dbCreateTransaction and dbTransactionID objects to ensure that the error was not due to a communications retry. If the dbCreateTransaction is in the Transaction state, and the dbTransactionID is the same value returned by the read of this object, then the management station is the owner of the transaction. If the dbTransactionID does not match the value originally returned by this object, then the management station is not the owner of the transaction and must wait until the dbCreateTransaction object returns to the Normal state before attempting to start the transaction.
Description 5
<Definition> This object is used to create unique transaction ID's for management stations to use when starting transactions using the dbCreateTransaction object. This object will be incremented by one every time it is read, so that different values will be returned for each read. Management stations wishing to start a transaction should first read the dbCreateTransaction object to verify that it is in the Normal state. If so then the management shall GET dbMakeID to obtain a transaction ID to use, then SET dbCreateTransaction to startCmd and dbTransactionID to the value just received. If the response to the SET operation is 'noError' then the management station has started a transaction. If the response to the SET operation is 'genError' then the management station should read the dbCreateTransaction and dbTransactionID objects to ensure that the error was not due to a communications retry. If the dbCreateTransaction is in the Transaction state, and the dbTransactionID is the same value returned by the read of this object, then the management station is the owner of the transaction. If the dbTransactionID does not match the value originally returned by this object, then the management station is not the owner of the transaction and must wait until the dbCreateTransaction object returns to the Normal state before attempting to start the transaction. <Informative> This object was deprecated in NTCIP 1201 v02 <Object Identifier> 1.3.6.1.4.1.1206.4.2.6.2.5
NTCIP published standard MIB annexes (reviewed modules)
Description 6
This object is used to create unique transaction ID’s for management stations to use when starting transactions using the dbCreateTransaction object. This object will be incremented by one every time it is read, so that different values will be returned for each read. Management stations wishing to start a transaction should first read the dbCreateTransaction object to verify that it is in the Normal state. If so then the management shall GET dbMakeID to obtain a transaction ID to use, then SET dbCreateTransaction to startCmd and dbTransactionID to the value just received. If the response to the SET operation is ‘noError’ then the management station has started a transaction. If the response to the SET operation is ‘genError’ then the management station should read the dbCreateTransaction and dbTransactionID objects to ensure that the error was not due to a communications retry. If the dbCreateTransaction is in the Transaction state, and the dbTransactionID is the same value returned by the read of this object, then the management station is the owner of the transaction. If the dbTransactionID does not match the value originally returned by this object, then the management station is not the owner of the transaction and must wait until the dbCreateTransaction object returns to the Normal state before attempting to start the transaction.
NTCIP published standard MIB annexes (reviewed modules)
Evidence
Matching descriptions are grouped; open a group to compare definitions and supporting files.
Status in source: unconfirmed.
Names: vmsHorizontalPitch
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"vmsHorizontalPitch",
"OBJECT-TYPE",
"SYNTAX",
"Integer32",
"(",
"0",
".",
".",
"255",
")",
"UNITS",
[
"literal",
"226d696c6c696d657465727322"
],
"MAX-ACCESS",
"read-only",
"STATUS",
"current",
"DESCRIPTION",
"\"<Definition> Indicates the horizontal distance from the center of one pixel to the center of the neighboring pixel in millimeters. The horizontal pitch on a character matrix DMS does not apply to the spacing between characters but does apply to the distance between pixels within a character. <Parameter Type> Status <Object Identifier> 1.3.6.1.4.1.1206.4.2.3.2.5\"",
"::=",
"{",
"vmsCfg",
"5",
"}"
],
"syntax_tree": [
[
"SimpleSyntax",
"Integer32",
[
"integerSubType",
[
[
0,
255
]
]
]
],
[
"UNITS",
"millimeters"
],
[
"MaxAccessPart",
"read-only"
],
[
"Status",
"current"
],
[
"DESCRIPTION",
"<Definition> Indicates the horizontal distance from the center of one pixel to the center of the neighboring pixel in millimeters. The horizontal pitch on a character matrix DMS does not apply to the spacing between characters but does apply to the distance between pixels within a character. <Parameter Type> Status <Object Identifier> 1.3.6.1.4.1.1206.4.2.3.2.5"
],
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.2.5, but its DESCRIPTION explicitly lists 1.3.6.1.4.1.1206.4.2.3.2.5. 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: deprecated.
Names: dbMakeID
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"dbMakeID",
"OBJECT-TYPE",
"SYNTAX",
"Integer32",
"(",
"0",
".",
".",
"255",
")",
"MAX-ACCESS",
"read-only",
"STATUS",
"deprecated",
"DESCRIPTION",
"\"<Definition> This object is used to create unique transaction ID's for management stations to use when starting transactions using the dbCreateTransaction object. This object will be incremented by one every time it is read, so that different values will be returned for each read. Management stations wishing to start a transaction should first read the dbCreateTransaction object to verify that it is in the Normal state. If so then the management shall GET dbMakeID to obtain a transaction ID to use, then SET dbCreateTransaction to startCmd and dbTransactionID to the value just received. If the response to the SET operation is 'noError' then the management station has started a transaction. If the response to the SET operation is 'genError' then the management station should read the dbCreateTransaction and dbTransactionID objects to ensure that the error was not due to a communications retry. If the dbCreateTransaction is in the Transaction state, and the dbTransactionID is the same value returned by the read of this object, then the management station is the owner of the transaction. If the dbTransactionID does not match the value originally returned by this object, then the management station is not the owner of the transaction and must wait until the dbCreateTransaction object returns to the Normal state before attempting to start the transaction. <Informative> This object was deprecated in NTCIP 12012 v02 <Object Identifier> 1.3.6.1.4.1.1206.4.2.6.2.5\"",
"::=",
"{",
"globalDBManagement",
"5",
"}"
],
"syntax_tree": [
[
"SimpleSyntax",
"Integer32",
[
"integerSubType",
[
[
0,
255
]
]
]
],
null,
[
"MaxAccessPart",
"read-only"
],
[
"Status",
"deprecated"
],
[
"DESCRIPTION",
"<Definition> This object is used to create unique transaction ID's for management stations to use when starting transactions using the dbCreateTransaction object. This object will be incremented by one every time it is read, so that different values will be returned for each read. Management stations wishing to start a transaction should first read the dbCreateTransaction object to verify that it is in the Normal state. If so then the management shall GET dbMakeID to obtain a transaction ID to use, then SET dbCreateTransaction to startCmd and dbTransactionID to the value just received. If the response to the SET operation is 'noError' then the management station has started a transaction. If the response to the SET operation is 'genError' then the management station should read the dbCreateTransaction and dbTransactionID objects to ensure that the error was not due to a communications retry. If the dbCreateTransaction is in the Transaction state, and the dbTransactionID is the same value returned by the read of this object, then the management station is the owner of the transaction. If the dbTransactionID does not match the value originally returned by this object, then the management station is not the owner of the transaction and must wait until the dbCreateTransaction object returns to the Normal state before attempting to start the transaction. <Informative> This object was deprecated in NTCIP 12012 v02 <Object Identifier> 1.3.6.1.4.1.1206.4.2.6.2.5"
],
null,
null,
null,
null
]
}Module: NTCIP1201-GlobalV1
See published definition above
{'SNMPv2-TC': ['AutonomousType', 'VariablePointer'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'OBJECT-TYPE', 'OBJECT-IDENTITY', 'Integer32', 'Unsigned32', 'zeroDotZero'], 'SNMPv2-CONF': ['OBJECT-GROUP'], 'NTCIP1201-Global': ['global'], 'NTCIP8004-Transportation': ['profiles']}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.
· Download NTCIP-1201 — ntcip1201-AuxIO.mibSame file in ntcip1201-SNMPConfig.mib.
Same file in ntcip1201-Security.mib.
Same file in ntcip1201-ProfilesSTMP.mib.
Same file in ntcip1201-NtcipTraps.mib.
Status in source: deprecated.
Names: dbMakeID
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"dbMakeID",
"OBJECT-TYPE",
"SYNTAX",
"INTEGER",
"(",
"0",
".",
".",
"255",
")",
"ACCESS",
"read-only",
"STATUS",
"deprecated",
"DESCRIPTION",
"\"This object is used to create unique transaction ID’s for management stations to use when starting transactions using the dbCreateTransaction object. This object will be incremented by one every time it is read, so that different values will be returned for each read. Management stations wishing to start a transaction should first read the dbCreateTransaction object to verify that it is in the Normal state. If so then the management shall GET dbMakeID to obtain a transaction ID to use, then SET dbCreateTransaction to startCmd and dbTransactionID to the value just received. If the response to the SET operation is ‘noError’ then the management station has started a transaction. If the response to the SET operation is ‘genError’ then the management station should read the dbCreateTransaction and dbTransactionID objects to ensure that the error was not due to a communications retry. If the dbCreateTransaction is in the Transaction state, and the dbTransactionID is the same value returned by the read of this object, then the management station is the owner of the transaction. If the dbTransactionID does not match the value originally returned by this object, then the management station is not the owner of the transaction and must wait until the dbCreateTransaction object returns to the Normal state before attempting to start the transaction. <Object Identifier> 1.3.6.1.4.1.1206.4.2.6.2.5\"",
"::=",
"{",
"globalDBManagement",
"5",
"}"
],
"syntax_tree": [
[
"SimpleSyntax",
"INTEGER",
[
"integerSubType",
[
[
0,
255
]
]
]
],
null,
[
"MaxAccessPart",
"read-only"
],
[
"Status",
"deprecated"
],
[
"DESCRIPTION",
"This object is used to create unique transaction ID’s for management stations to use when starting transactions using the dbCreateTransaction object. This object will be incremented by one every time it is read, so that different values will be returned for each read. Management stations wishing to start a transaction should first read the dbCreateTransaction object to verify that it is in the Normal state. If so then the management shall GET dbMakeID to obtain a transaction ID to use, then SET dbCreateTransaction to startCmd and dbTransactionID to the value just received. If the response to the SET operation is ‘noError’ then the management station has started a transaction. If the response to the SET operation is ‘genError’ then the management station should read the dbCreateTransaction and dbTransactionID objects to ensure that the error was not due to a communications retry. If the dbCreateTransaction is in the Transaction state, and the dbTransactionID is the same value returned by the read of this object, then the management station is the owner of the transaction. If the dbTransactionID does not match the value originally returned by this object, then the management station is not the owner of the transaction and must wait until the dbCreateTransaction object returns to the Normal state before attempting to start the transaction. <Object Identifier> 1.3.6.1.4.1.1206.4.2.6.2.5"
],
null,
null,
null,
null
]
}Module: NTCIP1201-v03
See published definition above
{'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)Related source files and packages:
Status in source: deprecated.
Names: dbMakeID
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"dbMakeID",
"OBJECT-TYPE",
"SYNTAX",
"INTEGER",
"(",
"0",
".",
".",
"255",
")",
"ACCESS",
"read-only",
"STATUS",
"deprecated",
"DESCRIPTION",
"\"This object is used to create unique transaction ID's for management stations to use when starting transactions using the dbCreateTransaction object. This object will be incremented by one every time it is read, so that different values will be returned for each read. Management stations wishing to start a transaction should first read the dbCreateTransaction object to verify that it is in the Normal state. If so then the management shall GET dbMakeID to obtain a transaction ID to use, then SET dbCreateTransaction to startCmd and dbTransactionID to the value just received. If the response to the SET operation is 'noError' then the management station has started a transaction. If the response to the SET operation is 'genError' then the management station should read the dbCreateTransaction and dbTransactionID objects to ensure that the error was not due to a communications retry. If the dbCreateTransaction is in the Transaction state, and the dbTransactionID is the same value returned by the read of this object, then the management station is the owner of the transaction. If the dbTransactionID does not match the value originally returned by this object, then the management station is not the owner of the transaction and must wait until the dbCreateTransaction object returns to the Normal state before attempting to start the transaction.\"",
"::=",
"{",
"globalDBManagement",
"5",
"}"
],
"syntax_tree": [
[
"SimpleSyntax",
"INTEGER",
[
"integerSubType",
[
[
0,
255
]
]
]
],
null,
[
"MaxAccessPart",
"read-only"
],
[
"Status",
"deprecated"
],
[
"DESCRIPTION",
"This object is used to create unique transaction ID's for management stations to use when starting transactions using the dbCreateTransaction object. This object will be incremented by one every time it is read, so that different values will be returned for each read. Management stations wishing to start a transaction should first read the dbCreateTransaction object to verify that it is in the Normal state. If so then the management shall GET dbMakeID to obtain a transaction ID to use, then SET dbCreateTransaction to startCmd and dbTransactionID to the value just received. If the response to the SET operation is 'noError' then the management station has started a transaction. If the response to the SET operation is 'genError' then the management station should read the dbCreateTransaction and dbTransactionID objects to ensure that the error was not due to a communications retry. If the dbCreateTransaction is in the Transaction state, and the dbTransactionID is the same value returned by the read of this object, then the management station is the owner of the transaction. If the dbTransactionID does not match the value originally returned by this object, then the management station is not the owner of the transaction and must wait until the dbCreateTransaction object returns to the Normal state before attempting to start the transaction."
],
null,
null,
null,
null
]
}Module: NTCIP1201-2004
See published definition above
{'RFC-1212': ['OBJECT-TYPE'], 'RFC1155-SMI': ['Opaque', 'Counter', 'Gauge', 'null'], 'RFC1213-MIB': ['DisplayString'], 'NTCIP8004-A-2004': ['devices', 'protocols', 'profiles', 'global']}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 NTCIP8004-A-2004, 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-1201 — NTCIP1201-Glo.mibStatus in source: unconfirmed.
Names: dbMakeID
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"dbMakeID",
"OBJECT-TYPE",
"SYNTAX",
"Integer32",
"(",
"0",
".",
".",
"255",
")",
"MAX-ACCESS",
"read-only",
"STATUS",
"deprecated",
"DESCRIPTION",
"\"<Definition> This object is used to create unique transaction ID's for management stations to use when starting transactions using the dbCreateTransaction object. This object will be incremented by one every time it is read, so that different values will be returned for each read. Management stations wishing to start a transaction should first read the dbCreateTransaction object to verify that it is in the Normal state. If so then the management shall GET dbMakeID to obtain a transaction ID to use, then SET dbCreateTransaction to startCmd and dbTransactionID to the value just received. If the response to the SET operation is 'noError' then the management station has started a transaction. If the response to the SET operation is 'genError' then the management station should read the dbCreateTransaction and dbTransactionID objects to ensure that the error was not due to a communications retry. If the dbCreateTransaction is in the Transaction state, and the dbTransactionID is the same value returned by the read of this object, then the management station is the owner of the transaction. If the dbTransactionID does not match the value originally returned by this object, then the management station is not the owner of the transaction and must wait until the dbCreateTransaction object returns to the Normal state before attempting to start the transaction. <Informative> This object was deprecated in NTCIP 1201 v02 <Object Identifier> 1.3.6.1.4.1.1206.4.2.6.2.5\"",
"::=",
"{",
"globalDBManagement",
"5",
"}"
],
"syntax_tree": [
[
"SimpleSyntax",
"Integer32",
[
"integerSubType",
[
[
0,
255
]
]
]
],
null,
[
"MaxAccessPart",
"read-only"
],
[
"Status",
"deprecated"
],
[
"DESCRIPTION",
"<Definition> This object is used to create unique transaction ID's for management stations to use when starting transactions using the dbCreateTransaction object. This object will be incremented by one every time it is read, so that different values will be returned for each read. Management stations wishing to start a transaction should first read the dbCreateTransaction object to verify that it is in the Normal state. If so then the management shall GET dbMakeID to obtain a transaction ID to use, then SET dbCreateTransaction to startCmd and dbTransactionID to the value just received. If the response to the SET operation is 'noError' then the management station has started a transaction. If the response to the SET operation is 'genError' then the management station should read the dbCreateTransaction and dbTransactionID objects to ensure that the error was not due to a communications retry. If the dbCreateTransaction is in the Transaction state, and the dbTransactionID is the same value returned by the read of this object, then the management station is the owner of the transaction. If the dbTransactionID does not match the value originally returned by this object, then the management station is not the owner of the transaction and must wait until the dbCreateTransaction object returns to the Normal state before attempting to start the transaction. <Informative> This object was deprecated in NTCIP 1201 v02 <Object Identifier> 1.3.6.1.4.1.1206.4.2.6.2.5"
],
null,
null,
null,
null
]
}Module: NTCIP1201-Global
See published definition above
{'SNMPv2-TC': ['AutonomousType', 'VariablePointer'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'OBJECT-TYPE', 'OBJECT-IDENTITY', 'Integer32', 'Unsigned32', 'zeroDotZero'], 'NTCIP8004-Transportation': ['devices', 'profiles']}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: Published module-root disagreement: global 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.6.8. All dependent assignments from this module require verification. No root number has been silently corrected.
· Download 1201v4-0-0.pdf — NTCIP1201-Global (MIB transcription)Related source files and packages:
Status in source: deprecated.
Names: dbMakeID
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"dbMakeID",
"OBJECT-TYPE",
"SYNTAX",
"INTEGER",
"(",
"0",
".",
".",
"255",
")",
"ACCESS",
"read-only",
"STATUS",
"deprecated",
"DESCRIPTION",
"\"This object is used to create unique transaction ID’s for management stations to use when starting transactions using the dbCreateTransaction object. This object will be incremented by one every time it is read, so that different values will be returned for each read. Management stations wishing to start a transaction should first read the dbCreateTransaction object to verify that it is in the Normal state. If so then the management shall GET dbMakeID to obtain a transaction ID to use, then SET dbCreateTransaction to startCmd and dbTransactionID to the value just received. If the response to the SET operation is ‘noError’ then the management station has started a transaction. If the response to the SET operation is ‘genError’ then the management station should read the dbCreateTransaction and dbTransactionID objects to ensure that the error was not due to a communications retry. If the dbCreateTransaction is in the Transaction state, and the dbTransactionID is the same value returned by the read of this object, then the management station is the owner of the transaction. If the dbTransactionID does not match the value originally returned by this object, then the management station is not the owner of the transaction and must wait until the dbCreateTransaction object returns to the Normal state before attempting to start the transaction.\"",
"::=",
"{",
"globalDBManagement",
"5",
"}"
],
"syntax_tree": [
[
"SimpleSyntax",
"INTEGER",
[
"integerSubType",
[
[
0,
255
]
]
]
],
null,
[
"MaxAccessPart",
"read-only"
],
[
"Status",
"deprecated"
],
[
"DESCRIPTION",
"This object is used to create unique transaction ID’s for management stations to use when starting transactions using the dbCreateTransaction object. This object will be incremented by one every time it is read, so that different values will be returned for each read. Management stations wishing to start a transaction should first read the dbCreateTransaction object to verify that it is in the Normal state. If so then the management shall GET dbMakeID to obtain a transaction ID to use, then SET dbCreateTransaction to startCmd and dbTransactionID to the value just received. If the response to the SET operation is ‘noError’ then the management station has started a transaction. If the response to the SET operation is ‘genError’ then the management station should read the dbCreateTransaction and dbTransactionID objects to ensure that the error was not due to a communications retry. If the dbCreateTransaction is in the Transaction state, and the dbTransactionID is the same value returned by the read of this object, then the management station is the owner of the transaction. If the dbTransactionID does not match the value originally returned by this object, then the management station is not the owner of the transaction and must wait until the dbCreateTransaction object returns to the Normal state before attempting to start the transaction."
],
null,
null,
null,
null
]
}Module: NTCIP1201-2004
See published definition above
{'RFC-1212': ['OBJECT-TYPE'], 'RFC1155-SMI': ['Opaque', 'Counter', 'Gauge', 'null'], 'RFC1213-MIB': ['DisplayString'], 'NTCIP8004-A-2004': ['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: 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 NTCIP1201v0232f.pdf — NTCIP1201-2004 (MIB transcription)Related source files and packages:
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)Related source files and packages:
Registration
| OID | Name | Direct children | Descendants | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.1206.4.2.6.2.1 | dbCreateTransaction, vmsCharacterHeightPixels | 0 | 0 | |
| 1.3.6.1.4.1.1206.4.2.6.2.2 | dbErrorType, vmsCharacterWidthPixels | 0 | 0 | |
| 1.3.6.1.4.1.1206.4.2.6.2.3 | dbErrorID, vmsSignHeightPixels | 0 | 0 | |
| 1.3.6.1.4.1.1206.4.2.6.2.4 | dbTransactionID, vmsSignWidthPixels | 0 | 0 | |
| 1.3.6.1.4.1.1206.4.2.6.2.6 | dbVerifyStatus, vmsVerticalPitch | 0 | 0 | |
| 1.3.6.1.4.1.1206.4.2.6.2.7 | dbVerifyError, monochromeColor | 0 | 0 |